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:
If you load the MIBs in this order, you can eliminate most of the load-order issues.
The CISCO-SMI MIB defines the iso.org.dod.internet.private.enterprise.cisco.ciscoMgmt object (18.104.22.168.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.