To Run Openboot Commands; About Predictive Self-Healing - Sun Microsystems Sun Fire V445 Server Administration Manual

To Run OpenBoot Commands

1. Halt the system to reach the ok prompt.
How you do this depends on the system's condition. If possible, you should
warn users before you shut the system down.
2. Type the appropriate command at the console prompt.

About Predictive Self-Healing

In Solaris 10 systems, the Solaris Predictive Self-Healing (PSH) technology enables
Sun Fire V445 server to diagnose problems while the Solaris OS is running, and
mitigate many problems before they negatively affect operations.
The Solaris OS uses the fault manager daemon, fmd(1M), which starts at boot time
and runs in the background to monitor the system. If a component generates an
error, the daemon handles the error by correlating the error with data from previous
errors and other related information to diagnose the problem. Once diagnosed, the
fault manager daemon assigns the problem a Universal Unique Identifier (UUID)
that distinguishes the problem 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 message ID (MSGID). You can use message ID to
get additional information about the problem from Sun's knowledge article
database.
The Predictive Self-Healing technology covers the following Sun Fire V445 server
components:
UltraSPARC IIIi processors
Memory
I/O bus
The PSH console message provides the following information:
Type
Severity
Description
Automated Response
Impact
Suggested Action for System Administrator
If the Solaris PSH facility has detected a faulty component, use the fmdump
command (described in the following subsections) to identify the fault. Faulty FRUs
are identified in fault messages using the FRU name.
186 Sun Fire V445 Server Administration Guide • September 2007