This section describes commands commonly used for service-related activities.
Before you can run ILOM commands, you must connect to the service processor in one of two ways:
Connect an ASCII terminal directly to the serial management port.
Use the ssh command to connect to the service processor through an Ethernet connection on the network management port.
To switch from the console output to the ALOM CMT CLI sc> prompt, type #. (Hash-Period).
To switch from the service processor prompt to the console, do one of the following:
From the ILOM -> prompt, type start /SP/console.
From the ALOM-CMT sc> prompt, type console.
Service-Related Commands describes the typical ALOM CMT CLI commands for servicing a server. For descriptions of all ALOM CMT CLI commands, issue the help command or refer to the Integrated Lights Out Management 2.0 User's Guide.
|
The ILOM show faulty command displays the following kinds of faults:
E nvironmental or configuration faults – System configuration faults, or temperature or voltage problems that might be caused by faulty FRUs (power supplies, fans, or blower), or by room temperature or blocked air flow to the server.
POST detected faults – Faults on devices detected by the power-on self-test diagnostics.
PSH detected faults – Faults detected by the Solaris Predictive Self-healing (PSH) technology
Use the show faulty command for the following reasons:
To see if any faults have been diagnosed in the system.
To verify that the replacement of a FRU has cleared the fault and not generated any additional faults.
The following show faulty command examples show the different kinds of output from the show faulty command:
Example of the show faulty command when no faults are present:
-> show faulty Target | Property | Value --------------------+------------------------+------------------------------- -----------------------------------------------------------------------------
Example of the show faulty command displaying an environmental fault:
-> show faulty Target | Property | Value --------------------+------------------------+------------------------------- /SP/faultmgmt/0 | fru | /SYS/FANBD0/FM0 /SP/faultmgmt/0 | timestamp | Dec 14 23:01:32 /SP/faultmgmt/0/ | timestamp | Dec 14 23:01:32 faults/0 /SP/faultmgmt/0/ | sp_detected_fault | TACH at /SYS/FANBD0/FM0/F0 has faults/0 | | exceeded low non-recoverable | | threshold.
Example showing a fault that was detected by POST. These kinds of faults are identified by the message Forced fail reason where reason is the name of the power-on routine that detected the failure.
-> show faulty Target | Property | Value --------------------+------------------------+-------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/CMP0/BR1/CH0/D0 /SP/faultmgmt/0 | timestamp | Dec 21 16:40:56 /SP/faultmgmt/0/ | timestamp | Dec 21 16:40:56 faults/0 | | /SP/faultmgmt/0/ | sp_detected_fault | /SYS/MB/CMP0/BR1/CH0/D0 faults/0 | Forced fail(POST)
Example showing a fault that was detected by the PSH technology. These kinds of faults are identified by the text Host detected fault and by a UUID.
-> show faulty Target | Property | Value --------------------+------------------------+-------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/CMP0/BR0/CH1/D0 /SP/faultmgmt/0 | timestamp | Dec 14 22:43:59 /SP/faultmgmt/0/ | sunw-msg-id | SUN4V-8000-DX faults/0 | | /SP/faultmgmt/0/ | uuid | 3aa7c854-9667-e176-efe5-e487e520 faults/0 | | 7a8a /SP/faultmgmt/0/ | timestamp | Dec 14 22:43:59 faults/0 | |