Display Information About Alerts

An alert is information of interest that is neither a fault nor a defect. An alert might report a problem or might be simply informational. A problem that is reported by an alert is a misconfiguration or other problem that the administrator can resolve without assistance from a response agent. An example of this type of problem is a DIMM plugged into the wrong slot. An example of an informational message reported by an alert is a message that a shadow migration has completed.

The following list provides examples of alert messages:

  • Threshold alerts – Temperature is high, storage is at capacity, a quota is exceeded, the path count to a chassis or disk has changed. These kinds of alerts can predict a performance impact.

  • Configuration checks – A FRU has been added or removed, SAS cabling is incorrect, a DIMM is plugged into the wrong slot, a datalink changed, a link went up or down, Oracle ILOM is misconfigured, MTU (Maximum Transmission Unit - TCP/IP) is misconfigured.

  • Interesting events – A reboot occurred, file system events occurred, firmware has been upgraded, save core failed.

Alerts can be in one of the following states:

  • active – The alert has not been cleared.

  • cleared – The alert has been cleared. The cleared state for alerts can be compared to the resolved state for faults and defects. See the following description of persistent and transient alerts for more information about clearing an alert.

Alerts can be persistent or transient.

  • A persistent alert is active until it is manually cleared as shown in fmadm clear Command.

  • A transient alert clears after a specified timeout period or is cleared by a service such as a network monitor.

  1. Become an administrator.
  2. To display information about the components, enter the command:

    fmadm list-alert

    Tip:

    Base your administrative action on output from the fmadm list-alert command. Log files output by the fmdump command contain a historical record of events and do not necessarily present active or open diagnoses. Log files output by fmdump -i are a historical record of telemetry and might not have been diagnosed into alerts.

    See the following example for a description of the text generated.

Example 2-4 fmadm list-alert Output

Use the fmadm list-alert command to list all alerts that have not been cleared. The following alert shows that Top Level Identifier information (TLI) for the system is missing or corrupted. The Problem Status has the value open, which is an active state. Problem Status can be open, isolated, repaired, or resolved. The Problem class indicates that the chassis TLI is invalid. The Impact indicates how the system might be impacted by the issue. Perhaps the most useful piece of information in this output is the MSG-ID. Follow the instructions in the Action at the end of the alert to access more information about SPX86A-8006-5T.

# fmadm list-alert
------------------- ------------------------------------ -------------- --------
Time                UUID                                 msgid          Severity
------------------- ------------------------------------ -------------- --------
2000-06-01/08:40:14 5f252c60-0668-e32a-f0de-b3e9f24228df SPX86A-8006-5T Critical

Problem Status           : open [injected]
Diag Engine              : fdd 1.0
System                 
   Manufacturer          : Oracle Corporation
   Name                  : ORACLE SERVER X7-2L
   Part_Number           : 1234567
   Serial_Number         : 1234567

System Component       
   Firmware_Manufacturer : Oracle Corporation
   Firmware_Version      : (ILOM)4.0.0.0
   Firmware_Release      : (ILOM)2017.06.02

----------------------------------------
Suspect 1 of 1
   Problem class  : alert.memory.intel.dimm.mismatch
   Certainty      : 100%
   Affects        : /SYS
   Status         : faulted

   FRU                
      Status            : Active
      Location          : /SYS
      Manufacturer      : Oracle Corporation
      Name              : ORACLE SERVER X7-2L
      Part_Number       : 1234567
      Serial_Number     : X7-2L_014
      Chassis         
         Manufacturer   : Oracle Corporation
         Name           : ORACLE SERVER X7-2L
         Part_Number    : 1234567
         Serial_Number  : X7-2L_014

Description : DIMMs of different types were detected.

Response    : The chassis wide service-required LED will be illuminated.

Impact      : The system is unable to power on.

Action      : Please refer to the associated reference document at
              http://support.oracle.com/msg/SPX86A-8006-5T for the latest
              service procedures and policies regarding this diagnosis.