PSH enables the server to diagnose problems and mitigate many problems before they negatively affect operations. PSH uses the Fault Manager daemon, fmd(1M), which starts at boot time and runs in the background, to monitor all of the faults that are generated by the components in the server.
On the service processor, PSH works with Oracle ILOM to manage all of the components on the server. On the host, PSH works with POST and the Oracle Solaris OS to manage the components assigned to the host.
If a component generates a fault, the fmd(1M) daemon correlates the fault with data from previous faults and other relevant information to diagnose the problem. After diagnosis, the 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 MSGID. You can use the message ID to get additional information about the problem from the knowledge article database.
A PSH console message provides this information about each detected fault:
Suggested action for system administrator
If PSH detects a faulty component, use the fmadm faulty command to display information about the fault. See Check for Faults.