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 Concepts

MIB Concepts

This section describes the MIB tree, MIB object, node, and MIB file.

MIB Tree Structure

MIB Tree Structure

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

Figure 3-2  MIB tree structure

An OID consists of positive integers and zeros, and uniquely identifies an MO in the MIB. The OIDs are distinguished from one another by Structure of Management Information (SMI).

Once an MIB file is released, each OID in the MIB file is bound to a corresponding MO and cannot be modified. An MO cannot be deleted, but you can set its state to obsolete indicating that the MO is not used.

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

The NMS references an MO by specifying its OID.

MIB Objects and Nodes

Figure 3-3 shows an IF-MIB. A MIB tree consists of table, row, and column objects. A table object consists of row objects, and a row object consists of a series of column objects.

Nodes in a MIB tree are classified into the following types:

  • Leaf node

    A leaf node does not have subnodes in a MIB tree. The leaf nodes are classified into scalar nodes and table nodes. To access a scalar node, add .0 to the OID of the scalar node. To access a table node, add .(index value) to the OID of the table node. For example, when you access the scalar node sysDescr (, the OID plus .0 is When you access the table node ifDescr ( and the index is 3, the OID plus .(index value) is

  • Non-leaf node

    A non-leaf node represents the association between subnodes, and cannot be accessed using the SNMP protocol.

Figure 3-3  MIB objects and nodes

In the MIB reference, the row object "Entry" is described as a prefix. For example, in description of "the OID prefix of this table is " in ifTable, corresponds to ifEntry.

Introduction to a MIB File


A MIB file is used to describe managed objects (MOs) in a MIB using Abstract Syntax Notation One (ASN.1). It accurately defines MOs in a MIB.


After MIB files are imported to the NMS software and the NMS connects to devices, you can perform operations for MIB objects to manage the devices.

Characteristics of a MIB File
  • A MIB file starts with DEFINITIONS ::= BEGIN and ends with END. The character string before DEFINITIONS ::= BEGIN is the base name. A base name seems like an object name and is unique.

  • You can use editors such as the Notepad and Wordpad to open and edit MIB files. The file name extension of a MIB file is .mib.

Updated: 2019-07-19

Document ID: EDOC1000174090

Views: 500601

Downloads: 49

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