Front and Rear Panel Components
Plan Communication With the Server Module During Installation
Optional Component Installation
Modular System Chassis Preparation
Insert the Server Module Into the Chassis
Communicating With the Server Module During Startup
Monitor the Diagnostic Messages
Powering On the Server Module for the First Time
Initial Power-On Task Overview
Power On the System for the First Time
Install Oracle Solaris Software From the Network
Oracle Solaris Configuration Settings
Assign a Static IP Address to the Service Processor
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
Front and Rear Panel Components
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 Command Summary
Interpreting Log Files and System Messages
Check the Message Buffer (dmesg Command)
View the System Message Log Files
List FRU Status (prtdiag Command)
Managing Faults (Oracle Solaris PSH)
Oracle ILOM Properties That Affect POST Behavior
Managing Components (ASR Commands)
Checking if Oracle VTS Software Is Installed
Check if Oracle VTS Software Is Installed
Find the Modular System Serial Number
Find the Server Module Serial Number
Removing the Server Module From the Modular System for Service
Clear the Fault and Verify the Functionality of the Replacement DIMM
Servicing a Service Processor Card
Remove the Service Processor Card
Install the Service Processor Card
Replacing the Server Module Enclosure Assembly
Transfer Components to Another Enclosure Assembly
Returning the Server Module to Operation
The Oracle Solaris PSH technology enables the server module to diagnose problems while the Oracle Solaris OS is running and to 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 message ID (sometimes labeled MSG-ID). You can use the message ID to get additional information about the problem from the knowledge article database.
The PSH technology covers the following server module components:
CPU
Memory
I/O subsystem
The PSH console message provides the following information about each detected fault:
Type
Severity
Description
Automated response
Impact
Suggested action for system administrator
If the PSH facility 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.