Contents

• Loading Cisco UCS MIBs Into a Network Management System
• Loading Cisco UCS MIBs
• Loading Prerequisite MIBs
• MIB Loading Order
• Loading Cisco UCS 1.3 MIBs
• Loading Cisco UCS 1.4, 2.0 and later MIBs

Loading Cisco UCS MIBs Into a Network Management System

---

This chapter includes the following sections:

• Loading Cisco UCS MIBs
• Loading Prerequisite MIBs
• MIB Loading Order

Loading Cisco UCS MIBs

Prior to loading Cisco UCS MIBs into a NMS, you must first load the prerequisite MIBs into the NMS. This enables you to receive the Cisco UCS Fault Traps on the NMS.

Loading Prerequisite MIBs

The following is a list of MIBs from which many other MIBs import definitions:

• SNMPv2-SMI.my
• SNMPv2-TC.my
• SNMP-FRAMEWORK-MIB.my
• RFC1213-MIB.my
• IF-MIB.my
• CISCO-SMI.my
• CISCO-ST-TC.my
• ENTITY-MIB.my
• INET-ADDRESS-MIB

If you load the MIBs in this order, you can eliminate most of the load-order issues.

Note

The CISCO-SMI MIB defines the iso.org.dod.internet.private.enterprise.cisco.ciscoMgmt object (1.3.6.1.4.9.9), which is the parent node of all UCS Manager MIBs. As stated above, several MIBs, including the CISCO-SMI MIB, must be loaded before any Cisco UCS Manager MIBs. Attempting to load the Cisco UCS Manager MIBs without the CISCO-SMI MIB will generally result in a MIB compiler error stating that a MIB node has no parent node.

MIB Loading Order

Most of the MIB use definitions are defined in other MIBs. These definitions are listed in the IMPORTS section near the top of the MIB.

For example, if MIB B imports a definition from MIB A, some MIB compilers require you to load MIB A prior to loading MIB B. If you get the MIB loading order wrong, you might get an error message about a MIB is undefined or not listed in IMPORTS. If you receive an error message, look at the loading order of MIBs defined in the IMPORTS section. Ensure that you have the appropriate load order.

• Loading Cisco UCS 1.3 MIBs
• Loading Cisco UCS 1.4, 2.0 and later MIBs

Loading Cisco UCS 1.3 MIBs

Cisco UCS 1.3 supports network MIBs, Fibre Channel MIBs, and the CISCO-UNIFIED-COMPUTING-MIB, which specifies traps for UCS faults.

If you want to receive UCS traps in your NMS, you must first load the prerequisite MIBs and then load the CISCO-UNIFIED-COMPUTING- MIB.

The following table lists the Cisco UCS traps included in the CISCO-UNIFIED-COMPUTING-MIB.

Table 1 CISCO-UNIFIED-COMPUTING-MIB Traps

MIB	Type of Trap
cucsFaultActiveNotif	This notification is generated by a UCS instance whenever a fault is raised.
cucsFaultClearNotif	The notification is generated by a UCS instance whenever a fault is cleared.

Loading Cisco UCS 1.4, 2.0 and later MIBs

Cisco UCS 1.4, 2.0 and later supports network MIBs and a series of MIBs to access all of the objects stored in the UCSM Management Information Tree.

All Managed Objects that can be accessed through the UCSM XML API can also be retrieved through the read-only SNMP GET operations.

Note	Cisco UCS continues to support the traps for UCSM fault notifications.

If you want to receive UCS traps in your NMS, you must first load the prerequisite MIBs and then load the following MIBs:

• CISCO-UNIFIED-COMPUTING-MIB.my
• CISCO-UNIFIED-COMPUTING-TC-MIB.my
• CISCO-UNIFIED-COMPUTING-FAULT-MIB.my
• CISCO-UNIFIED-COMPUTING-NOTIFS-MIB.my

If you load the MIBs in this order, you can eliminate the load-order definition problems.

If you want to retrieve Cisco UCS Manager Managed Objects through the read-only SNMP GET Operations, you need to load all additional Cisco UCS MIBs.

Note	In the case of a mixed environment, you can load the Cisco UCS 1.4, 2.0 and later MIBs in the NMS because these MIBs have a backward compatibility with the Cisco UCS 1.3 CISCO-UNIFIED-COMPUTING-MIB.