Confirming Server and Site Specifications
Overcurrent Protection Requirements
DC Power Source, Power Connection, and Grounding Requirements
PCIe2 Expansion Slot Guidelines
Mounting the Server Into a 4-Post Rack
Mounting the Server Into a 2-Post Rack
Connecting Data and Management Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power On the Server 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
Power On the Server (Oracle ILOM)
Power Off the Server (Oracle ILOM)
Reset the Server (Oracle Solaris OS)
Reset the Server (Oracle ILOM)
Reset the SP to Default Values
Important Hardware RAID Guidelines
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 Data on FRU PROMs
Change System Identifier Information
Restore the Host Power State at Restart
Specify the Host Power State at Restart
Disable or Re-Enable the Host Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior (Keyswitch State)
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Display the IP Address of the SP
Using an In-band Connection to the SP
Configure the Host Boot Mode (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 OBP 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
Mapping WWN Values to Hard Drives (OBP probe-scsi-all Command)
Identify a Disk Slot Using prtconf (Oracle Solaris OS)
WWN Syntax in an OS Installation on an Individual Drive
WWN Syntax in an OS Installation on a RAID Volume
Power Supply, Hard Drive, and Rear Fan Module Locations
Motherboard, PCIe2 Cards, and SP Locations
Front Fans, Subchassis, Memory Riser, and DIMM Locations
Oracle ILOM Troubleshooting Overview
Display FRU Information (show Command)
Check for Faults (show faulty Command)
Check for Faults (fmadm faulty Command)
Clear Faults (clear_fault_action Property)
Service-Related Oracle ILOM Commands
Understanding Fault Management Commands
Power Supply Fault Example (show faulty Command)
Power Supply Fault Example (fmadm faulty Command)
POST-Detected Fault Example (show faulty Command)
PSH-Detected Fault Example (show faulty Command)
Interpreting Log Files and System Messages
Checking if Oracle VTS Is Installed
Check if Oracle VTS Is Installed
Oracle ILOM Properties That Affect POST Behavior
Component Service Task Reference
Removing Power From the Server
Locate a Faulty Front Fan Module
Determine if the DVD Drive Is Faulty
Determine if the Rear Fan Module Is Faulty
Locate a Faulty DIMM (Oracle ILOM)
Determine if the Battery Is Faulty
Install SAS Cable for Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
Determine if the ID PROM Is Faulty
Determine if the LED Board Is Faulty
Determine if the Motherboard Is Faulty
Servicing the Power Distribution Board
Determine if the Power Distribution Board Is Faulty
Remove the Power Distribution Board
Install the Power Distribution Board
Verify the Power Distribution Board
Servicing the Hard Drive Backplane
Determine if the Hard Drive Backplane Is Faulty
Remove the Hard Drive Backplane
Install the Hard Drive Backplane
Verify the Hard Drive Backplane
Returning the Server to Operation
Power On the Server (Oracle ILOM)
PSH enables the server to diagnose problems while the Oracle Solaris OS is running and mitigate many problems before they negatively affect operations.
The Oracle Solaris OS uses the fault manager daemon, fmd(1M), which starts at boot time and runs in the background to monitor the system. If a component generates an error, the daemon correlates the error with data from previous errors and other relevant information to diagnose the problem. Once diagnosed, the fault manager daemon assigns a UUID to the error. This value distinguishes this error across any set of systems.
When possible, the fault manager daemon initiates steps to self-heal the failed component and take the component offline. The daemon also logs the fault to the syslogd daemon and provides a fault notification with a MSGID. You can use the MSGID to get additional information about the problem from the knowledge article database.
The PSH technology covers these server components:
CPU
Memory
I/O subsystem
The PSH console message provides this information about each detected fault:
Type
Severity
Description
Automated response
Impact
Suggested action for a system administrator
If PSH detects a faulty component, use the fmadm faulty command to display information about the fault. Alternatively, you can use the Oracle ILOM command show faulty for the same purpose.