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

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
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 Overview

MIB Overview

This section describes the concept, functions, and classifications of Management Information Base (MIB).

Introduction to MIB

As the network scale expands increasingly and more devices are deployed, how to efficiently manage the increasingly complex network and provide high-quality network services becomes a great challenge for network management.

A network administrator's efficiency is affected by factors such as the time, venue, and device quantity. Delivering the configuration and maintenance commands in command line mode can improve the efficiency, but causes many complex and redundant operations in some situations. In addition, command line-based operations cannot implement specific functions.

Network management based on the Simple Network Management Protocol (SNMP) is widely used on TCP/IP networks to solve the preceding problems.

An SNMP-based network management system consists of the following components:

  • Network management station (NMS)

    An NMS is often an independent device that runs network management applications. A network management program provides at least one human-machine interface on which network administrators can perform most of network management operations.

  • SNMP agent

    An agent is the software installed on a managed device. It receives and handles requests from the NMS, and returns responses to the NMS. Upon discovering an emergency, the agent sends a trap to the NMS.

  • SNMP

    As an application layer protocol in the TCP/IP suite, SNMP enables management message exchange between an NMS and a managed device.

  • MIB

    The MIB is a collection of managed objects (MOs). It enables an NMS to communicate with the agent on managed devices. Each agent maintains a MIB, in which the NMS can get or set the value of an object contained in an MIB.

Figure 3-1  SNMP-based network management

Figure 3-1 shows the relationship between the components:

  • The NMS communicates with the agent through SNMP. The NMS reads or modifies the objects in the MIB to monitor and manage devices running the agent.

  • SNMP is responsible for communication between the NMS and the agent. Data is encapsulated in the SNMP protocol data units (PDUs). SNMP packets are transferred over a transport layer protocol, such as UDP.

  • An agent is a process running on a managed device. The agent interoperates with the NMS and maintains the MIB to manage and monitor modules on the managed device.

  • The MIB stores information about each module of a managed device. The NMS reads or modifies the objects in the MIB to monitor and manage devices.

The MIB enables an NMS to monitor and control system resources by querying and modifying object values through SNMP.

MIB Classification

MIBs fall into public and proprietary MIBs:

  • Defined by RFCs, public MIBs, for example, OSPF-MIB and BGP4-MIB, are used for structural design and interface standardization for standard protocols. Manufacturers offer SNMP interfaces according to RFC-defined specifications.

  • Proprietary MIBs are the supplement to public MIBs. Enterprises can design proprietary MIBs for proprietary protocols or special functions. Proprietary MIBs also enable third-party NMSs to manage devices.

Public and proprietary MIBs are independent. That is, public and proprietary MIB objects cannot coexist in a MIB.

Updated: 2019-06-05

Document ID: EDOC1000097213

Views: 99499

Downloads: 652

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