B.2.4.2 fmdump -e command, B.2.5 using the fmadm faulty command, B.2.4.2 – FUJITSU SPARC M4000/M5000 User Manual

Page 63: B.2.5, Using the fmadm faulty

Advertising
background image

Appendix B

Fault Isolation

B-7

At least three lines of new output are delivered to the user with the -V option:

The first line is a summary of information you have seen before in the console
message but includes the timestamp, the UUID, and the Message-ID.

The second line is a declaration of the certainty of the diagnosis. In this case you
are 100 percent sure the failure is in the asic described. If the diagnosis might
involve multiple components you might see two lines here with 50 percent in each
(for example)

The ’FRU’ line declares the part which needs to be replaced to return the server to
a fully operational state.

The ’rsrc’ line describes which component was taken out of service as a result of
this fault.

B.2.4.2

fmdump -e

Command

To get information of the errors which caused this failure you can use the -e option,
as shown in the following example.

B.2.5

Using the fmadm faulty Command

The fmadm faulty command can be used by administrators and service personnel
to view and modify system configuration parameters that are maintained by the
Oracle Solaris Fault Manager. The fmadm faulty command is primarily used to
determine the status of a component involved in a fault, as shown in the following
example.

The PCI device is degraded and is associated with the same UUID as seen in the
preceding example. You might also see “faulted” states.

# fmdump -e

TIME CLASS

Nov 02 10:04:14.3008 ereport.io.fire.jbc.mb_per

# fmadm faulty

STATE RESOURCE / UUID

-------- -------------------------------------------------------------

degraded dev:////pci@1e,600000

0ee65618-2218-4997-c0dc-b5c410ed8ec2

Advertising