User Guide

Chapter 2 Sun Blade T6320 Server Module Diagnostics 2-45
1. After replacing a faulty FRU, boot the system.
2. Type fmadm faulty:
3. Clear the fault from all persistent fault records.
In some cases, even though the fault is cleared, some persistent fault information
remains and results in erroneous fault messages at boot time. To ensure that these
messages are not displayed, perform the following command:
fmadm repair UUID
For example:
Note – You can also use the FRU fault UUID instead of the Fault Management
Resource Identifier (FMRI).
Typing fmadm faulty after the repair command verifies that there are no more
faults.
2.7.3 Clearing the PSH Fault From the ILOM Logs
When the Solaris PSH facility detects faults, the faults are also logged by the ILOM
software.
Note – If you clear the faults using Solaris PSH, you do not have to clear the faults
in ILOM. If you clear the faults in ILOM, you do not also have to clear them with
Solaris PSH.
Note – If you are diagnosing or replacing faulty DIMMs, do not follow this
procedure. Instead, perform the procedure in Section 4.3.2, “Replacing the DIMMs”
on page 4-14.
# fmdadm faulty
STATE RESOURCE /UUID
faulted cpu:///cpuid=8/serial=FAC006AE4515C47
8856153f-6f9b-47c6-909a-b05180f53c07
# fmadm repair cpu:///cpuid=8/serial=FAC006AE4515C47
fmadm: recorded repair to cpu:///cpuid=8/serial=FAC006AE4515C47
# fmadm faulty
STATE RESOURCE/UUID