In Cisco UCS, a fault is a mutable object that is managed by Cisco UCS Manager. Each fault represents a failure in the Cisco UCS instance or an alarm threshold that has been raised. During the life cycle of a fault, it can change from one state or severity
to another.
Each fault includes information about the operational state of the affected object at the time the fault was raised. If the
fault is transitional and the failure is resolved, then the object transitions to a functional state.
A fault remains in Cisco UCS Manager until the fault is cleared and deleted according to the settings in the fault collection policy.
The following table lists the Cisco UCS traps included in the CISCO-UNIFIED-COMPUTING-NOTIF-MIB.
Table 1. CISCO-UNIFIED-COMPUTING-NOTIF-MIB Traps
Trap
|
Description
|
cucsFaultActiveNotif
The OID for this SNMP trap is .1.3.6.1.4.1.9.9.719.0.1.
|
This notification is generated by a Cisco UCS instance whenever a fault is raised.
|
cucsFaultClearNotif
The OID for this SNMP trap is .1.3.6.1.4.1.9.9.719.0.2.
|
This notification is generated by a Cisco UCS instance whenever a fault is cleared.
|
All Cisco UCS Manager faults are available with SNMP using the cucsFaultTable table and the CISCO-UNIFIED-COMUTING-FAULT-MIB. The table contains
one entry for every fault instance. Each entry has variables to indicate the nature of a problem, such as its severity and
type. The same object is used to model all Cisco UCS fault types, including equipment problems, FSM failures, configuration or environmental issues, and connectivity issues.
The cucsFaultTable table includes all active faults (those that have been raised and need user attention), and all faults
that have been cleared but not yet deleted because of the retention interval.
The cucsFaultTable table has the same information as the <faultInst> objects that can be queried through the XML API. In the Cisco UCS Manager GUI, faults are available in from the Admin tab under .
The following table describes the attributes exposed by the cucsFaultTable.
Table 2. cucsFaultTable Attritubes
Attribute
|
Description
|
Fault Instance ID (Table Index)
|
A unique integer that identifies the fault.
|
Affected Object DN
|
The distinguished name of the mutable object that has the fault.
|
Affected Object OID
|
The Object identifier (OID) of the mutable object that has the fault.
|
Creation Time
|
The time that the fault was created, depicted in UTC format.
|
Last Modification
|
The time when any of the attributes were modified.
|
Code
|
A code that provides information specific to the nature of the fault.
|
Type
|
The fault type.
|
Cause
|
The probable cause of the fault.
|
Severity
|
The severity of the fault. Fault severity transitions throughout the lifecyle of the fault, so several different fault severities
can be reported during the lifecyle of a fault. These include:
-
Original severity reported when the fault was first detected
-
Current severity reported for the fault
-
Previous severity reported for the fault
-
Highest severity reported for the fault
|
Occurrence
|
The number of times that a fault has occurred since it was created.
|
Description
|
A human readable string that contains all information related to the fault.
|
In Release 1.3 and later, Cisco UCS Manager sends a cucsFaultActiveNotif event notification whenever a fault is raised. There is one exception to this rule: Cisco UCS Manager does not send event notifications for FSM faults. The trap variables indicate the nature of the problem, including the fault
type. Cisco UCS Manager sends a cucsFaultClearNotif event notification whenever a fault has been cleared. A fault is cleared when the underlying
issue has been resolved.
In Release 1.4 and later, the cucsFaultActiveNotif and cucsFaultClearNotif traps are defined in the CISCO-UNIFIED-COMPUTING-NOTIFS-MIB.
All faults can be polled using SNMP GET operations on the cucsFaultTable, which is defined in the CISO-UNIFIED-COMPUTING-FAULT-MIB.
For more details about Cisco UCS Manager faults, see Cisco UCS Faults and Error Messages Reference.