Preparing for the Installation
Confirming Server Specifications
Optional Component Installation
Stabilize the Rack for Installation
Install Server Into the Slide Rail Assemblies
Verify Operation of Slide Rails and CMA
Rear Panel Connectors and Ports
Connect the Ethernet Network Cables
Connect the Network Module Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power On the System for the First Time
Oracle Solaris OS Configuration Parameters
Assign a Static IP Address to the SP
Understanding System Administration Resources
Platform-Specific Oracle ILOM Features
Oracle VM Server for SPARC Overview
Hardware Management Pack Overview
Source for Downloading Hardware Management Pack Software
Hardware Management Pack Documentation
Display the Oracle ILOM -> Prompt
Reset the Server From the Oracle Solaris OS
Reset the Server From Oracle ILOM
Reset the SP to Default Values
Important Hardware RAID Guidelines
Disk Zones for SPARC T3-1 Servers With Sixteen-Disk Backplanes
Displaying Disk Zone Information
Enabling and Disabling Disk Zoning In the Field
Prepare to Use the FCode Utility
Hot Spare Drives in RAID Volumes (LSI)
Determining If a Drive Has Failed
RAID Drive Replacement Strategies
Changing Server Identification Information
Change Customer FRUdata Information
Change System Identifier Information
Restore Host Power State at Restart
Specify Host Power State at Restart
Disable or Re-Enable Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior With the Keyswitch State
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Using an In-band Connection to the SP
Configure the Host Boot Mode of Oracle VM Server for SPARC
Change the Host Boot Mode Behavior at Reset
Manage the Host Boot Mode Script
Display Host Boot Mode Expiration Date
Override OpenBoot PROM Settings to Reset the Server
Configuring Server Behavior at Restart
Specify Behavior When the Host Resets
Specify Behavior When the Host Stops Running
Specify Behavior at Boot Timeout
Specify Behavior if Restart Fails
Specify Maximum Restart Attempts
Enabling Automatic System Recovery
Identifying WWN-Designated SAS2 Devices
probe-scsi-all Output Example (SPARC T3-1, Eight-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-1, Sixteen-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-4)
Identify a Disk Slot Using probe-scsi-all (OBP)
Identify a Disk Slot Using prtconf (Oracle Solaris, Onboard Controllers)
Identify a Disk Slot Using prtconf (Oracle Solaris, Single Initiator)
WWN Syntax in an OS Installation on a Specific Device
WWN Syntax in an OS Installation on a RAID Volume
Infrastructure Boards in the Server
Front and Rear Panel System Controls and LEDs
Ethernet and Network Management Port LEDs
Access the Service Processor (Oracle ILOM)
Display FRU Information With the show Command
Check for Faults Using the show faulty Command
Check for Faults With the fmadm faulty Command
Clear Faults With the clear_fault_action Property
Fault Management Command Examples
Service-Related ILOM Command Summary
Interpreting Log Files and System Messages
View the System Message Log Files
Using the Oracle Solaris Predictive Self-Healing Feature
Oracle Solaris Predictive Self-Healing Technology Overview
ILOM Properties that Affect POST Behavior
Managing Components With Automatic System Recovery Commands
Automatic System Recovery Overview
Checking if SunVTS Software Is Installed
Check if SunVTS Software Is Installed
Find the Chassis Serial Number
Understanding Component Replacement Categories
Removing Power From the System
Positioning the System for Servicing
Attaching Devices to the Server
Locate a Faulty Hard Disk Drive
Remove a Hard Disk Drive Filler Panel
Install a Hard Disk Drive Filler Panel
Verify Hard Disk Drive Functionality
Verify Fan Module Functionality
Verify Power Supply Functionality
Servicing Memory Risers and DIMMs
Locate a Faulty DIMM (DIMM Fault Remind Button)
Locate a Faulty DIMM (show faulty Command)
Increase Server Memory With Additional DIMMs
Remove a Memory Riser Filler Panel
Install a Memory Riser Filler Panel
DIMM Configuration Error Messages
Remove a DVD Drive or Filler Panel
Install a DVD Drive or Filler Panel
Servicing the System Lithium Battery
Servicing Expansion (PCIe) Cards
Remove a PCIe Card Filler Panel
Cable an Internal SAS HBA PCIe Card
Install a PCIe Card Filler Panel
Verify Fan Board Functionality
Verify Motherboard Functionality
Servicing the Service Processor
Service Processor Firmware and Configuration
Verify Service Processor Functionality
Servicing the Hard Disk Drive Backplane
Remove the Hard Disk Drive Backplane
Install the Hard Disk Drive Backplane
Verify Hard Disk Drive Backplane Functionality
Servicing the Power Supply Backplane
Remove the Power Supply Backplane
Install the Power Supply Backplane
Verify Power Supply Backplane Functionality
Returning the Server to Operation
Return the Server to the Normal Rack Position
The Integrated Lights Out Manager (Oracle ILOM) firmware enables you to remotely run diagnostics, such as power-on self-test (POST), that would otherwise require physical proximity to the server's serial port.
The service processor runs independently of the server, using the server's standby power. Therefore, Oracle ILOM firmware and software continue to function when the server OS goes offline or when the server is powered off.
Error conditions detected by Oracle ILOM, POST, and the Oracle Solaris Predictive Self-Healing (PSH) technology are forwarded to Oracle ILOM for fault handling.
Figure 21 Fault Reporting Through the ILOM Fault Manager
The ILOM fault manager evaluates error messages it receives to determine whether the condition being reported should be classified as an alert or a fault.
Alerts -- When the fault manager determines that an error condition being reported does not indicate a faulty FRU, it classifies the error as an alert.
Alert conditions are often caused by environmental conditions, such as computer room temperature, which may improve over time. They may also be caused by a configuration error, such as the wrong DIMM type being installed.
If the conditions responsible for the alert go away, the fault manager will detect the change and will stop logging alerts for that condition.
Faults -- When the fault manager determines that a particular FRU has an error condition that is permanent, that error is classified as a fault. This causes the Service Required LEDs to be turned on, the FRUID PROMs updated, and a fault message logged. If the FRU has status LEDs, the Service Required LED for that FRU will also be turned on.
A FRU identified as having a fault condition must be replaced.
The service processor can automatically detect when a faulted FRU has been replaced by a good FRU. In many cases, it does this even if the FRU is removed while the system is not running (for example, if the system power cables are unplugged during service procedures). This function enables Oracle ILOM to sense that a fault, diagnosed to a specific FRU, has been repaired.
Note - ILOM does not automatically detect hard drive replacement.
The Oracle Solaris Predictive Self-Healing technology does not monitor hard drives for faults. As a result, the service processor does not recognize hard drive faults and will not light the fault LEDs on either the chassis or the hard drive itself. Use the Oracle Solaris message files to view hard drive faults.
For general information about Oracle ILOM, see the Sun Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
For detailed information about Oracle ILOM features that are specific to this server, see the SPARC T3 Series Servers Administration Guide.