How To Clear FMA faults from Solaris[TM] and SC (System Controller) on T1000/T2000 T5120/T5220/T5140/T5240/T5440

Asset ID:	1-71-1004229.1
Update Date:	2012-10-15
Keywords:

Solution Type Technical Instruction Sure

Solution 1004229.1 : How To Clear FMA faults from Solaris[TM] and SC (System Controller) on T1000/T2000 T5120/T5220/T5140/T5240/T5440

Applies to:

Sun SPARC Enterprise T5120 Server - Version Not Applicable and later
Sun SPARC Enterprise T1000 Server - Version Not Applicable and later
Sun SPARC Enterprise T2000 Server - Version Not Applicable and later
Sun SPARC Enterprise T5140 Server - Version Not Applicable and later
Sun SPARC Enterprise T5220 Server - Version Not Applicable and later
All Platforms

Goal

Description
This document describes how to clear the FMA faults and error logs from Solaris[TM] and SC/ALOM or SP/ILOM level on Sun Fire[TM] T1000/T2000 and SPARC Enterprise[TM] T5x20/T5x40.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Coolthread Servers

Fix

Steps to Follow

Clearing faults from SP:
a) Show the faults on the system controller

sc> showfaults -v

b) For each fault listed run clearfault followed by the UUID obtained from above.

sc> clearfault 6f6b149a-2206-c967-ebd4-a3c52be6bed0  (UUID in this example is 6f6b149a-2206-c967-ebd4-a3c52be6bed0)

c) If there are any disabled components run NOTE: this step is not typically needed

sc> clearasrdb

d) Clear ereports NOTE: this step is not typically needed

sc> setsc sc_servicemode true
sc> showfmerptlog1 -v
sc> showfmerptlog2 -v
sc> clearereports -y  (if you want to clear them and start with a clean slate)
sc> setsc sc_servicemode false
sc> resetsc

Clearing faults from SP/ILOM:

a) Refer to the T5120/T5220 Service Manual for detailed steps
b) Refer to the T5140/T5240 Service Manual for detailed steps

To clear the FMA faults and error logs from Solaris:

a) Show faults in FMA

# fmadm faulty

NOTE: Do not use 'fmadm faulty -a' in this step. When you specify the -a option
all resource information cached by the Fault Manager is listed, including 
faults, which have already been corrected or where no recovery action is needed
(see 'fmadm' man page). The listing also include information for resources,
that may no longer be present in the system

b) For each fault UUID listed in the 'fmadm faulty' run

# fmadm repair <uuid> example: #fmadm repair 6f6b149a-2206-c967-ebd4-a3c52be6bed0

Starting with Solaris 10 update 7 there is an equivelent syntax that can also be used

#fmadm repaired <fmri | label> example: #fmadm repaired /SYS/MB

# fmadm faulty     (to make sure the output is clean after repair)

Product
Sun Fire T1000 Server
Sun Fire T2000 Server
SPARC Enterprise T5120 Server
SPARC Enterprise T5220 Server
SPARC Enterprise T5140 Server
SPARC Enterprise T5140 Server

Internal Comments
This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
contact the domain engineers that are managing this document via the "Document
Feedback" alias(es) listed below:

Domain Lead: [email protected]
[email protected]

normalized, FMA, fault, error log, SC, fmadm, showfaults, T1000, T2000, T5x20, T5x40
Previously Published As
88049

Change History
Date: 2011-02-01
User Name: Dencho Kojucharov
Action: Updated
Comment: process comments, audited by Entry-Level SPARC Content lead
Date: 2009-11-18
User Name: Anthony Rulli
Action: Updated
Comment: currency check, audited by Anthony Rulli, Entry Level SPARC Content team

Attachments

This solution has no attachment