Diagnostics Tools Quick Reference

The following table provides brief descriptions of the troubleshooting actions shown in the flowchart. It also provides links to topics with additional information on each diagnostic action.

Table 39 Diagnostic Flowchart Reference Table

Diagnostic Action	Possible Outcome	Additional Information
Check Power OK and AC Present LEDs on the server. (Flowchart item 1)	The Power OK LED is located on the front and rear of the chassis. The AC Present LED is located on the rear of the server on each power supply. If these LEDs are not on, check the power source and power connections to the server.	Front Panel Controls and Indicators on Sun SPARC Enterprise T5140 Servers Front Panel Controls and Indicators on Sun SPARC Enterprise T5240 Servers
Run the ILOM `show faulty` command to check for faults. Flowchart item 2)	The `show faulty` command displays the following kinds of faults: E nvironmental faults Solaris Predictive Self-Healing (PSH) detected faults POST detected faults Faulty FRUs are identified in fault messages using the FRU name.	Service-Related Commands Faults Displayed by `show faulty`
Check the Solaris log files for fault information. (Flowchart item 3)	The Solaris message buffer and log files record system events, and provide information about faults. If system messages indicate a faulty device, replace the FRU. For more diagnostic information, review the SunVTS report. (Flowchart item 4)	Viewing Solaris OS Messages
Run SunVTS software. (Flowchart item 4)	SunVTS is an application you can run to exercise and diagnose FRUs. To run SunVTS, the server must be running the Solaris OS. If SunVTS reports a faulty device, replace the FRU. If SunVTS does not report a faulty device, run POST. (Flowchart item 5)	Detecting Faults Using SunVTS Software
Run POST. (Flowchart item 5)	POST performs basic tests of the server components and reports faulty FRUs.	Detecting Faults With POST ILOM Properties Used to Manage POST Operations
Check if the fault is environmental. (Flowchart item 6)	Determine if the fault is an environmental fault or a configuration fault. If the fault listed by the `show faulty` command displays a temperature or voltage fault, then the fault is an environmental fault. Environmental faults can be caused by faulty FRUs (power supply or fan), or by environmental conditions such as when computer room ambient temperature is too high, or the server airflow is blocked. When the environmental condition is corrected, the fault will automatically clear. If the fault indicates that a fan or power supply is bad, you can perform a hot-swap of the FRU. You can also use the fault LEDs on the server to identify the faulty FRU (fans and power supplies).	Faults Displayed by `show faulty`
Determine if the fault was detected by PSH. (Flowchart item 7)	If the fault displayed included a `uuid` and `sunw-msg--id` property, the fault was detected by the Solaris Predictive Self-Healing software. If the fault is a PSH detected fault, refer to the PSH Knowledge Article web site for additional information. The Knowledge Article for the fault is located at the following link: http://www.sun.com/msg/msg-ID At this site, select the `message-ID` is the value of the `sunw-msg-id` property displayed by the `show faulty` command. After the FRU is replaced, perform the procedure to clear PSH detected faults.	Managing Faults Using the PSH Feature Clear PSH-Detected Faults
Determine if the fault was detected by POST. (Flowchart item 8)	POST performs basic tests of the server components and reports faulty FRUs. When POST detects a faulty FRU, it logs the fault and if possible, takes the FRU offline. POST detected FRUs display the following text in the fault message: `Forced fail` `reason` In a POST fault message, `reason` is the name of the power-on routine that detected the failure.	Detecting Faults With POST Clear POST-Detected Faults
Contact technical support. (Flowchart item 9)	The majority of hardware faults are detected by the server’s diagnostics. In rare cases a problem might require additional troubleshooting. If you are unable to determine the cause of the problem, contact your service representative for support.

Skip Navigation Links
Exit Print View
	Sun SPARC Enterprise T5140 and T5240 Servers Topic Set