Skip Navigation Links
Exit Print View
| SPARC T4-1 Server HTML Document Collection

Search Scope:

- This Document
- Entire Library

## Clear PSH-Detected Faults

When PSH detects faults, the faults are logged and displayed on the console. In most cases, after the fault is repaired, the server detects the corrected state and automatically repairs the fault. However, you should verify this repair. In cases where the fault condition is not automatically cleared, you must clear the fault manually.

1. After replacing a faulty FRU, power on the server.
2. At the host prompt, determine whether the replaced FRU still shows a faulty state.

       # fmadm faulty
       TIME            EVENT-ID                              MSG-ID         SEVERITY
       Aug 13 11:48:33 21a8b59e-89ff-692a-c4bc-f4c5cccca8c8  SUN4V-8002-6E  Major

       Platform    : sun4v     Chassis_id  :
       Product_sn  :

       Fault class : fault.cpu.generic-sparc.strand
       Affects     : cpu:///cpuid=**/serial=*********************
                         faulted and taken out of service
       FRU         : "/SYS/MB"
       (hc://:product-id=*****:product-sn=**********:server-id=***-******-*****:
       chassis-id=********:**************-**********:serial=******:revision=05/
       chassis=0/motherboard=0)
                         faulty

       Description : The number of correctable errors associated with this strand has
                     exceeded acceptable levels.
                     Refer to http://sun.com/msg/SUN4V-8002-6E for more information.

       Response    : The fault manager will attempt to remove the affected strand
                     from service.

       Impact      : System performance may be affected.

       Action      : Schedule a repair procedure to replace the affected resource, the
                     identity of which can be determined using 'fmadm faulty'.

   - If no fault is reported, you do not need to do anything else. Do not perform the subsequent steps.
   - If a fault is reported, continue to Step 3.
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, type the following Oracle Solaris command:

       # fmadm repair UUID

   For the UUID in the example shown in Step 2, type this command:

       # fmadm repair 21a8b59e-89ff-692a-c4bc-f4c5cccc

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

- PSH Overview

- PSH-Detected Fault Example

- Check for PSH-Detected Faults

Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |