Load Cisco FXOS MIBs
Before loading FXOS MIBs into an NMS, you must first load the prerequisite MIBs into the NMS. This enables you to receive the FXOS Fault Traps in the NMS.
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.
This chapter includes the following sections:
Before loading FXOS MIBs into an NMS, you must first load the prerequisite MIBs into the NMS. This enables you to receive the FXOS 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.
Important |
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
ENTITY-MIB.my
INET-ADDRESS-MIB.my
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 FXOS MIBs. Several MIBs, including the CISCO-SMI MIB, must be loaded before other Cisco FXOS MIBs. Attempting to load other Cisco FXOS 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 before 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.
FXOS supports network MIBs and a series of MIBs to access all of the objects stored in the FXOS Management Information Tree.
All managed objects that can be accessed through the FXOS XML API can also be retrieved through read-only SNMP GET operations.
Important |
You should load the MIBs in the order listed to eliminate most of the load-order issues. |
If you want to receive Cisco FXOS traps in your NMS, first load the prerequisite MIBs (see Prerequisite MIBs), then load the following Cisco MIBs:
CISCO-FIREPOWER-MIB.my
CISCO-FIREPOWER-TC-MIB.my
CISCO-FIREPOWER-FAULT-MIB.my
CISCO-FIREPOWER-NOTIFS-MIB.my
If you want to retrieve FXOS managed objects using read-only SNMP GET operations, you need to load all additional Cisco FXOS MIBs. The additional FXOS MIBs are generally used to retrieve inventory and configuration information using SNMP GET operations. To learn more about all of the FXOS MIBs, see Purpose of the Cisco FXOS MIBs.
Note |
In environments running multiple versions of FXOS, load the latest FXOS MIBs in the NMS, because all FXOS MIBs are developed to be backward-compatible with previous versions. |