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

Search Scope:

- This Document
- Entire Library

##### Power Supply Fault Example (`fmadm` `faulty` Command)

The following is an example of the `fmadm` `faulty` command reporting on the same power supply fault as shown in the `show` `faulty` example. See `show` `faulty` Example of a Power Supply Fault. Both examples show the same UUID value.

The `fmadm` `faulty` command was run from within the Oracle ILOM `faultmgmt` shell.

Note - The characters SPT at the beginning of the message ID indicate that the fault was detected by Oracle ILOM.

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

    faultmgmtsp> fmadm faulty
    ------------------- ------------------------------------ -------------- -------
    Time                UUID                                 msgid          Severity
    ------------------- ------------------------------------ -------------- -------
    2010-08-11/14:54:23 ********-****-****-****-************ SPT-8000-LC    Critical

    Fault class : fault.chassis.power.volt-fail

    Description : A Power Supply voltage level has exceeded acceptible limits.

    Response    : The service required LED on the chassis and on the affected
                  Power Supply may be illuminated.

    Impact      : Server will be powered down when there are insufficient
                  operational power supplies

    Action      : The administrator should review the ILOM event log for
                  additional information pertaining to this diagnosis.  Please
                  refer to the Details section of the Knowledge Article for
                  additional information.

    faultmgmtsp> exit

##### Related Information

- Fault Managment Command Examples

- `show` `faulty` Example of a Power Supply Fault

- `show` `faulty` Example of a POST-Detected Fault

- `show` `faulty` Example of a PSH-Detected Fault

- Service-Related Oracle ILOM Command Summary

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