Diagnostics Process

The following flowchart illustrates the diagnostic process, using different diagnostic tools through a default sequence. See also the table that follows the flowchart.

Figure 44 Diagnostics Flowchart

image:Flowchart showing the flow of diagnostic tasks.

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 18 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 Components
Run the Oracle ILOM `show faulty` command to check for faults. (Flowchart item 2)	The `show faulty` command displays the following kinds of faults: E nvironmental and configuration faults Oracle Solaris Predictive Self-Healing (PSH) detected faults POST detected faults Faulty FRUs are identified in fault messages using the FRU name.	Oracle ILOM Properties Used to Manage POST Operations Check for Faults (`show` `faulty` Command)
Check the Oracle Solaris log files for fault information. (Flowchart item 3)	The Oracle 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 Oracle VTS report. (Flowchart item 4)	Interpreting Log Files and System Messages
Run Oracle VTS software. (Flowchart item 4)	Oracle VTS is an application you can run to exercise and diagnose FRUs. To run Oracle VTS, the server must be running the Oracle Solaris OS. If Oracle VTS reports a faulty device, replace the FRU. If Oracle VTS does not report a faulty device, run POST. (Flowchart item 5)	Checking if Oracle VTS Software Is Installed
Run POST. (Flowchart item 5)	POST performs basic tests of the server components and reports faulty FRUs.	Managing Faults (POST) Oracle ILOM Properties Used to Manage POST Operations
Determine if the fault was detected by the Oracle ILOM fault management software. (Flowchart item 6)	All Oracle ILOM-detected fault messages begin with the characters “SPT”. For additional information on the reported fault, including possible corrective action, go to this web site: http://www.sun.com/msg/message-ID Where `message-ID` is the message ID contained in the fault message. `show faulty` command.	Check for Faults (`show` `faulty` Command)
Determine if the fault was detected by PSH. (Flowchart item 7)	If the fault message does not begin with the characters “SPT”, the fault was detected by the Oracle Solaris Predictive Self-Healing (PSH) software. For additional information on the reported fault, including possible corrective action, go to this web site: http://www.sun.com/msg/message-ID Where `message-ID` is the message ID contained in the fault message. `show faulty` command.	Managing Faults (PSH) 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.	Managing Faults (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
	SPARC T3-1 Server HTML Document Collection