10/23/2020 Document

Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

How To Clear FMA FAULTS from Solaris[TM] and SC (System Controller) on T1000/T2000
T5120/T5220/T5140/T5240/T5440,T6320,T6340, T3-1/T3-2/T3-4, T4-1/T4-2/T4-4 (Doc ID
1004229.1)

APPLIES TO:

Sun SPARC Enterprise T1000 Server - Version All Versions to All Versions [Release All Releases]
Sun Blade T6320 Server Module - Version All Versions to All Versions [Release All Releases]
SPARC T3-2 - Version All Versions to All Versions [Release All Releases]
Sun Netra T5440 Server - Version All Versions to All Versions [Release All Releases]
Sun Blade T6300 Server Module - Version All Versions to All Versions [Release All Releases]
All Platforms

GOAL

Description
This document describes how to clear the FMA faults and error logs from Solaris and SC/ALOM or SP/ILOM level on Sun
Fire T1000/T2000, SPARC Enterprise T5x20/T5x40 and SPARC T3-x/T4-x servers

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

SOLUTION

Steps to Follow

Clearing faults from SP (the commands shown below are ALOM-CMT commands that can be issued only from ALOM
compatibility shell)(NOT USED FOR T3-X or T4-X):

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 <UUID> (UUID in this example is xxxxxxxx-1234-abcd-efg5-xxxxxxxxxxx)

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

sc> clearasrdb

Clearing faults from SP/ILOM:

See section C.1 in doc 1155200.1 for Using the ILOM Command Line Interface (CLI) to Clear the Faults.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=iltr2mb32_111 1/3
10/23/2020 Document

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

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

NOTE: There in no ALOM compatibility shell for the SPARC T3-x/T4-x and later platforms, and ILOM is the only available
shell. See doc 1012360.1
The SPARC T3-x (& newer) servers also support the ILOM Fault Management Shell (FM shell), which can
be accessed from SP through:

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n) ? y
faultmgmtsp>

The FM shell allows the FMA logs to be analyzed with fma commands similar to what is used with FMA in Solaris. Refer to
doc 1309092.1 for details. This will assist the Field in troubleshooting faults diagnosed by FMA. Note that in the case of
faults proxied from the host OS and cleared by way of the Fault Management Shell, they will be cleared ONLY from the
shell and ILOM but not Solaris. See FMA/PSH doc 1155200.1 for more details on using FM shell.

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/EVENT-ID listed in the 'fmadm faulty' run

# fmadm repair <uuid/event-id> example: #fmadm repair <UUID>

Starting with Solaris 10 update 7 there is an equivalent 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)

NOTE: For more details on FMA-based diagnosis and commands for clearing faults,
refer to article 1173733.1 (section C.1.2.4 Clearing All Faults)

NOTE: There is an issue (CR 6983432), which causes previously diagnosed and repaired PSH faults from the host to
reappear (to be replayed) in Oracle ILOM when the host reboots. It manifests itself as an incorrect report of a PSH-
diagnosed fault represented through the Oracle ILOM CLI, BUI, and fault LED. You can identify this defect by checking to
see if the same PSH fault was reported from the host as well.

The affected OS is Solaris 10 u10( 8/11) on all T3-x and T4-x platforms. The issue is fixed in patch 147790-01: SunOS
5.10: fmd patch.

See the workaround below:

# fmdump
TIME UUID SUNW-MSG-ID
Sep 16 08:38:19.5582 <UUID> SUN4V-8002-6E
Sep 16 08:40:47.8191 <UUID> FMD-8000-4M Repaired
Sep 16 08:40:47.8446 <UUID> FMD-8000-6U Resolved
#

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=iltr2mb32_111 2/3
10/23/2020 Document

# fmadm flush /SYS/MB

fmadm: flushed resource history for /SYS/MB
#
faultmgmtsp> fmadm repair /SYS/MB
faultmgmtsp> fmadm faulty
No faults found
faultmgmtsp>

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

REFERENCES

NOTE:1483194.1 - Commands to Run to Fully Clear ILOM/SP, Faultmgmt Shell, and FMA Faults on the T3-x, T4-x and T5-x
Servers
NOTE:2216293.1 - Commands To Clear FMA faults on the T5-x, T7-x, S7-x, T8-x, Mx-32, M7-x, M8-x Servers
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=iltr2mb32_111 3/3