No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


MIB Reference

TE30, TE40, TE50, TE60, TX50, RP100, and RP200 V600R019C00

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
MIB Tree Structure

MIB Tree Structure

The MIB stores MOs in a tree structure. The leaf nodes of the tree are MOs. An object identifier (or object ID or OID) uniquely identifies a managed object in the MIB hierarchy.

Figure 1-3 MIB tree structure

An OID is a string of non-negative integers and represents the location of an MO in the MIB tree. The SMI ensures that each OID is unique within a MIB.

Once a MIB file is released, OIDs are bound to the defined MOs. The bindings cannot be modified. A node in the MIB tree cannot be deleted, but can be set to obsolete indicating that the node is not used.

In the tree structure shown in Figure 1-3, the MO mgmt is identified as { iso(1) org(3) dod(6) internet(1) mgmt(2) } or, which is an OID.

The NMS invokes objects in an agent by their OIDs.

Updated: 2019-05-31

Document ID: EDOC1100057237

Views: 9138

Downloads: 14

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next