3. Clear the fault from all persistent fault records.
In some cases, even though the fault is cleared, persistent fault information
remains and results in erroneous fault messages at boot time. To ensure that these
messages are not displayed, run the following Oracle Solaris command:
# fmadm replaced /SYS/MB
For the component referenced in the example in
the following command:
# fmadm replaced ********-****-****-****-************
Note that you should use one of the following fmadm commands released with the
Oracle Solaris 10 05/09 OS based on whether you are replacing a component or
whether you have repaired the component in some way:
■
■
Note – The system generally detects new components when a new serial number is
introduced into the system, but in cases where fault information remains, the fmadm
replaced command will clear any faults that persist in the system after discovery.
4. Use the clear_fault_action property of the FRU to clear the fault.
-> set /SYS/MB clear_fault_action=True
Are you sure you want to clear /SYS/MB (y/n)? y
set 'clear_fault_action' to 'true
Related Information
"Oracle Solaris Predictive Self-Healing Technology Overview" on page 39
■
"PSH-Detected Fault Example" on page 40
■
44
SPARC T3-2 Server Service Manual • December 2013
Use fmadm repaired when a physical repair is performed to resolve a
problem with a faulted component. For example, use this command if you have
reinstalled a card after straightening a bent pin and reseating the card.
Use fmadm replaced when you install a new component to replace a faulted
component and the new component is not automatically discovered by the
system.
Refer to the fmadm man page for more information about these commands.
Step 2
(the motherboard) enter
Need help?
Do you have a question about the SPARC T3-2 and is the answer not in the manual?
Questions and answers