Confirming Server Specifications
Optional Component Installation
Determine Correct Rackmount Hardware
Mark the Rackmounting Location
Install the Rackmount Hardware
Installing and Using the Shipping Bracket Assembly (Optional)
Front Panel Connectors and Ports
Rear Panel Connectors and Ports
Installing and Using the CMA (Optional)
Connect the Ethernet Network Cables
Powering On the Server for the First Time
Oracle ILOM System Console Overview
Connect a Terminal or Emulator to the SER MGT Port
Power On the Server for the First Time
Oracle Solaris OS Configuration Parameters
Assigning a Static IP Address to the Service Processor
Booting the Oracle Solaris Operating System
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
Access the Service Processor (ILOM)
Display FRU Information (show Command)
Check for Faults (show faulty Command)
Check for Faults (fmadm faulty Command)
Clear Faults (clear_fault_action Property)
Fault Managment Command Examples
Interpreting Log Files and System Messages
Using Oracle Solaris Predictive Self-Healing
ILOM Properties That Affect POST Behavior
Find the Chassis Serial Number
Understanding Component Replacement Categories
Removing Power From the System
Processor Module Configuration Reference
Replacing a Faulty Processor Module
Install a New Processor Module
Verify Processor Module Functionality
Memory Fault Handling Overview
Understanding DIMM Configurations
Locate a Faulty DIMM Using the DIMM Fault Remind Button
Locate a Faulty DIMM Using the show faulty Command
Increase System Memory With Additional DIMMs
Hard Drive Hot-Pluggable Capabilities
Hard Drive Configuration Reference
Verify Hard Drive Functionality
Power Supply and AC Power Connector Configuration Reference
Power Supply and AC Power Connector LEDs
Verify Power Supply Functionality
Servicing RAID Expansion Modules
Remove the RAID Expansion Module
Install the RAID Expansion Module
Servicing the Service Processor
Locate a Faulty Service Processor
Verify Service Processor Functionality
Fan Module Configuration Reference
Verify Fan Module Functionality
Express Module Configuration Reference
Locate a Faulty Express Module
Verify Express Module Functionality
Locate a Faulty Rear I/O Module
Verify Rear I/O Module Functionality
Servicing the System Configuration PROM
System Configuration PROM Overview
Remove the System Configuration PROM
Install the System Configuration PROM
Servicing the Front I/O Assembly
Install the Front I/O Assembly
Servicing the Storage Backplane
Servicing the Main Module Motherboard
Main Module Motherboard Overview
Locate a Faulty Main Module Motherboard
Remove the Main Module Motherboard
Install the Main Module Motherboard
Verify Main Module Motherboard Functionality
Servicing the Rear Chassis Subassembly
Rear Chassis Subassembly Overview
Remove the Rear Chassis Subassembly
Install the Rear Chassis Subassembly
Returning the Server to Operation
Connect Power Cords to the Server
Power On the Server (start /SYS Command)
The ILOM firmware enables you to remotely run diagnostics, such as POST, that would otherwise require physical proximity to the server's serial port. You can also configure ILOM to send email alerts of hardware failures, hardware warnings, and other events related to the server or to ILOM.
The service processor runs independently of the server, using the server's standby power. Therefore, ILOM firmware and software continue to function when the server OS goes offline or when the server is powered off.
Error conditions detected by ILOM, POST, and the Oracle Solaris PSH technology are forwarded to ILOM for fault handling.
Figure 18 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's 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 FRU has been replaced. 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 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 PSH 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 ILOM, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
For detailed information about ILOM features that are specific to this server, see the SPARC T3 Series Servers Administration Guide.