Fault Management; Fault Clearing - Sun Oracle SPARC T3-1B Service Manual

Fault Management

Error conditions detected by Oracle ILOM, POST, and the Oracle Solaris PSH
technology are forwarded to Oracle ILOM for fault handling.
The Oracle ILOM fault manager evaluates error messages it receives to determine
whether the condition being reported should be classified as an alert or a fault.
Alerts – When the fault manager determines that an error condition being
■
reported does not indicate a faulty FRU, the fault manager classifies the error as
an alert.
Alert conditions are often caused by environmental conditions, such as computer
room temperature, which might improve over time. Conditions might also be
caused by a configuration error, such as the wrong DIMM type being installed.
If the conditions responsible for the alert go away, the fault manager will detect
the change and will stop logging alerts for that condition.
Faults – When the fault manager determines that a particular FRU has an error
■
condition that is permanent, that error is classified as a fault. This condition causes
the Service Action Required LEDs to be turned on, the FRUID PROMs updated,
and a fault message logged. If the FRU has status LEDs, the Service Action
Required LED for that FRU will also be turned on.
You must replace a FRU identified as having a fault condition.
In the event of a system fault, Oracle ILOM ensures that the Service Action Required
LED is turned on, FRUID PROMs are updated, the fault is logged, and alerts are
displayed. Faulty FRUs are identified in fault messages using the FRU name.

Fault Clearing

The SP can detect when a fault is no longer present. When this happens, it clears the
fault state in the FRU PROM and extinguishes the Service Action Required LED.
A fault condition can be removed in two ways:
Unaided recovery – Faults caused by environmental conditions can clear
■
automatically if the condition responsible for the fault is no longer present.
Detecting and Managing Faults 13