The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
This chapter includes the following sections:
Before loading Cisco UCS Standlone C-Series server MIBs into an NMS, you must first load the prerequisite MIBs into the NMS. This enables you to receive the Cisco UCS Fault Traps in the NMS.
The MIBs in this section are required for all use cases and need to be loaded before other Cisco MIBs are loaded.
You should load the MIBs in the order listed to eliminate most of the load-order issues.
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
CISCO.TC.my
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 Cisco UCS Standalone C-Series MIBs. Several MIBs, including the CISCO-SMI MIB, must be loaded before other Cisco UCS Standalone C-Series MIBs. Attempting to load other Cisco UCS Standalone C-Series MIBs before the CISCO-SMI MIB generally results in a MIB compiler error stating that a MIB node has no parent node. |
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 that 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.
Cisco UCS Standalone C-Series software release 1.3 and later supports network MIBs and a series of MIBs to access all of the objects stored in the Cisco UCS Manager Standalone C-Series Management Information Tree.
All managed objects that can be accessed through the Cisco UCS Standalone C-Series XML API can also be retrieved through read-only SNMP GET operations.
You should load the MIBs in the order listed to eliminate most of the load-order issues.
If you want to receive Cisco UCS traps in your NMS, first load the prerequisite MIBs (see Prerequisite MIBs), then load the following Cisco 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 want to retrieve Cisco UCS managed objects using read-only SNMP GET operations, you need to load all additional Cisco UCS Standalone C-Series MIBs. The additional Cisco UCS Standalone C-Series MIBs are generally used to retrieve inventory and configuration information using SNMP GET operations. To learn more about all of the Cisco UCS Standalone C-Series MIBs, see Purpose of the MIBs.
Note | In environments running multiple versions of Cisco UCS Standalone C-Series servers, load the latest Cisco UCS Standalone C-Series MIBs in the NMS, because all Cisco UCS Standalone C-Series MIBs are developed to be backward-compatible with previous versions of Cisco UCS Standalone C-Series servers that support SNMP. |