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.


eSight V300R009C00 Operation Guide 10

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).
Function Overview

Function Overview

This topic describes the MIB principles, including Simple Network Management Protocol (SNMP) management model, MIB tree-structured hierarchy, MIB classification, and MIB management home page and common functions.

SNMP Management Model

An SNMP system consists of four parts: network management system (NMS), agent, managed object, and MIB. As the network management center, the NMS manages devices on the network. A managed device includes an agent that resides on the device, a MIB, and multiple managed objects. The NMS interacts with an agent that resides on a managed device, instructing the agent to perform operations on the MIB of the managed device. Figure 12-14 shows the SNMP management model.

Figure 12-14 SNMP management model

The following describes the four parts in an SNMP system:

  • NMS

    The NMS runs on the NMS server to manage and monitor network devices using SNMP.

    • The NMS sends requests to the agent of a managed device for querying or modifying one or more parameters.
    • The NMS receives trap information actively sent from the agent of a managed device to obtain the status of the managed device.
  • Agent

    An agent is a process that runs on a managed device for maintaining data of the managed device, responding to the requests sent from the NMS, and sending management data to the NMS.

    • An agent receives requests from the NMS, performs related operations on the MIB tables, and sends the operation results to the NMS.
    • When a device encounters a fault event or any other exceptions, the device actively reports its status change to the NMS through the agent.
  • Management object

    A managed object is an object that is managed by the NMS. It can be a piece of hardware (for example, an interface board) on a device or a collection of hardware or software (for example, a routing selection protocol) and associated configuration parameters. A device may have multiple managed objects.

  • MIB

    A MIB is a database that specifies variables (information that can be queried and set by an agent) maintained by a managed device. It defines a series of attributes for a managed device, including the object name, object status, object access rights, and object data type. The NMS communicates with the agent of a managed device using SNMP, instructing the agent to perform MIB operations. In this way, the NMS is able to monitor and manage the device.

    The MIB hierarchy can be depicted as a tree with a nameless root in the uppermost, and its tree structure is similar to that of a domain name system (DNS). A MIB is also called an object naming tree. Figure 12-15 shows a part of the MIB. An object identifier (OID) identifies a managed object on the tree. For example, the OID of system on the tree is and the OID of interface is

    Such an OID tree enables users to efficiently manage the stored management information and to conveniently query information in batches.

    During agent configuration, a MIB view can be used to limit the MIB objects that the NMS can access. A MIB view is a MIB subset.

Figure 12-15 OID tree structure

MIB Classification

MIBs can be classified into two types: public MIB and proprietary MIB.

  • Public MIB: generally defined by the Requirement For Comments (RFC) for structured design and interface standardization processing for various public protocols. For example, OSPF-MIB (RFC1850) and BGP4-MIB (RFC1657) are typical public MIBs. Most of the equipment vendors provide RFC-compliant SNMP interfaces.
  • Proprietary MIB: a necessary supplement to public MIBs. When equipment vendors develop their own proprietary protocols or unique functions, proprietary MIBs can be used to improve the management functions of SNMP interfaces. In addition, proprietary MIBs enable third-party NMS software to manage devices that use proprietary protocols or have unique functions.

MIB Management Home Page


Parameter setting area


Shortcut operation area


Operation status display area


Operation result display area


Search area


MIB tree navigation area


Right-click menu


Node attribute display area

MIB Management Function

  • Verifies the connectivity between the device and eSight through MIB management.
  • Manages MIB files, including compiling and loading MIB files.
  • Supports common operations for obtaining MIB node data, including Get, GetNext, Walk, TableView, and Stop.
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 314876

Downloads: 637

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