Feedback
About Cisco UCS MIB Files
This chapter includes the following sections:
Cisco UCS MIB Files
Cisco UCS MIB files are a set of objects that are private extensions to the IETF standard MIB II. MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II. Portions of MIB-II have been updated since RFC 1213. See the IETF website http://www.ietf.org for the latest updates to this MIB.
If your NMS cannot get requested information from a fabric interconnect, then the MIB that allows that specific data collection might be missing. Typically, if an NMS cannot retrieve a particular MIB variable, either the NMS does not recognize the MIB variable, or the agent does not support the MIB variable. If the NMS does not recognize a specified MIB variable, you might need to load the MIB into the NMS, usually with a MIB compiler. For example, you might need to load the Cisco UCS private MIB or the supported RFC MIB into the NMS to execute the specified data collection. If the agent does not support a specified MIB variable, you must find out what version of system software that you are running. Different software releases support different MIBs.
Note
Cisco and IETF MIBs are updated frequently. You should download the latest MIBs from Cisco.com whenever you upgrade the Cisco UCS software versions.
Cisco UCS Manager Faults
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.
All Cisco UCS Manager faults are available through SNMP using the cucsFaultTable table, which contains one entry for every fault instance. Each entry has variables to indicate the nature of the problem, such as the severity and type. The same object is used to model all Cisco UCS fault types, including equipment issues (memory, CPU), FSM failures, configuration issues, environment issues (thermal, power), and connectivity issues. The cucsFaultTable table includes all active faults (faults that are raised and need user attention), as well as faults that have been cleared but not deleted yet 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, the faults are available through the Admin tab under .
In Release 1.3 and later, Cisco UCS Manager sends a cucsFaultActiveNotif trap whenever a fault is raised in Cisco UCS Manager. As an exception to this rule, Cisco UCS Manager does not send traps for FSM faults. The trap variables indicate the nature of the problem, including the fault type, such as memory or configuration issue. Cisco UCS Manager sends a cucsFaultClearNotif trap whenever a fault has been cleared. A fault is cleared when the underlying issue has been resolved.
In Release 1.3, the cucsFaultActiveNotif and cucsFaultClearNotif traps are defined in the CISCO-UNIFIED-COMPUTING-MIB MIB.
In Release 1.4, 2.0 and later, the cucsFaultActiveNotif and cucsFaultClearNotif traps are defined in the CISCO-UNIFIED-COMPUTING-NOTIFS-MIB MIB. All faults can be polled using SNMP GET through cucsFaultTable, which is defined in the CISO-UNIFIED-COMPUTING-FAULT-MIB.
For more details on the Cisco UCS Manager Faults, see Cisco UCS Faults and Error Messages Reference.
The following table describes the attributes exposed by the cucsFaultTable.
Table 1 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.
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.
Occurrence
The number of times that a fault has occurred since it was created.
Description
A human readable string that provides all information related to the fault.
Types of MIBs
The Cisco UCS Management is based on the XML over HTTP model, that provides a rich data model to configure and monitor the system. This model includes polices, service profiles, configuration and monitoring data, and statistics.
To simplify the integration of Cisco UCS with SNMP based NMS, Cisco UCS Manager exposes the model through SNMP, based on the following Cisco UCS releases:
- In Release 1.0 and later, IETF networking MIBs, such as the IF-MIB and the ENTITY-MIB are implemented.
- In Release 1.3 and later, Cisco UCS can send SNMP traps whenever a fault is raised or cleared in Cisco UCS Manager.
- In Release 1.4, 2.0 and later, the entire Cisco UCS Manager data model is exposed through the read-only Cisco UCS MIBs. All objects that can be retrieved through the Cisco UCS Manager XML API can also be retrieved through Cisco UCS Manager MIBs.
NoteEach release maintains complete coverage of the XML API model via private MIBs.
Cisco UCS provides the following two systems:
The following table lists the different types of Cisco UCS MIBs, along with the locations for downloading the MIBs:
MIB Type Location Network MIBs
ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-manager-supportlist.html
Cisco UCS Manager MIBs
ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-manager-supportlist.html
C-Series Standalone Rack Server MIBs
ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-C-supportlist.html
