Understanding Diagnostics
When possible, PSH initiates steps to take the component offline. PSH also logs the fault to the
syslogd daemon and provides a fault notification with a message ID. You can use the message
ID to get additional information about the problem from the Knowledge Base article database.
A PSH console message provides this information about each detected fault:
Type
■
Severity
■
Description
■
Automated response
■
Impact
■
Suggested action for system administrator
■
If PSH detects a faulty component, use the fmadm faulty command to display information
about the fault. See
Related Information
"Diagnostics Process" on page 26
■
"Checking for Faults" on page 27
■
Diagnostics Process
This table describes the diagnostics process.
Step
Diagnostic Action
1.
Check the server for detected
faults using these tools:
■ System LEDs on the
front and rear panels.
■ fmadm faultycommand
from the Oracle Solaris
prompt or through the
Oracle ILOM fault
management shell.
2.
Check the log files for fault
information.
3.
Run POST to provide
additional low-level
26
SPARC T8-4 Server Service Manual • January 2022
"Check for Faults" on page
Possible Outcome
Determine the faulty component and replace it, or
continue to advanced troubleshooting.
If system messages indicate a faulty component, replace
it.
If POST indicates a faulty component, replace it.
33.
Links
"Checking for Faults" on page 27
"Interpreting Log Files and System
Messages" on page 35
"Configuring POST" on page 37