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

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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

All the MOs in a network compose the tree structure of the MIB. The leaf nodes of the tree are managed objects. An MO is identified by the set of nodes along the path from the root to the leaf node. Such a path is called object identifier (OID).

Figure 2-3 shows the MIB tree structure.

Figure 2-3  MIB tree structure

An OID consists of positive integers and zero, and it is used to uniquely identify an MO in the MIB. The SMI ensures that each OID is unique within a MIB.

Once the MIB file is released, OIDs are bound to the MOs. The binding cannot be modified. The MOs in the MIB cannot be deleted, but can be set to obsolete indicating that the MO is not used.

In the tree structure shown in Figure 2-3, the MO mgmt is represented by { iso(1) org(3) dod(6) internet(1) mgmt(2) } or that is called OID.

The NMS refers to an MO by specifying the OID.

Updated: 2019-07-19

Document ID: EDOC1000174090

Views: 499509

Downloads: 49

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