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.


CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the basic concepts, configuration procedures, and configuration examples in different application scenarios of the network management feature supported by the device.
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).
SNMP Management Model

SNMP Management Model

An SNMP system consists of four key components: network management station (NMS), agent, management object, and Management Information Base (MIB).

The NMS manages network elements on a network.

Each managed device contains an agent process, MIB, and multiple management objects. The NMS interacts with the agent on a managed device. When receiving a command from the NMS, the agent performs operations on the MIB in the managed device.

Figure 1-1 shows an SNMP management model.

Figure 1-1  SNMP management model

The components in an SNMP-managed system are as follows:

  • NMS

    The NMS is a manager on a network that uses SNMP to monitor and control network devices. The NMS software runs on NMS servers to implement the following functions:

    • Send requests to agents on managed devices to query or modify variables.
    • Receive traps sent from agents on managed devices to learn device status.
  • Agent

    The agent is a process running on a managed device. The agent maintains data on the managed device, responds to request packets from the NMS, and returns management data to the NMS.

    • Upon receiving a request packet from the NMS, the agent performs the required operation on the MIB and sends the operation result to the NMS.
    • When a fault or an event occurs on the managed device, the agent sends a notification containing the current device status to the NMS.
  • Management object

    A management object is an object to be managed on a network device. A managed device contains multiple management objects, for example, a hardware component and parameters configured for the hardware or software (such as a route selection protocol).

  • MIB

    An MIB contains the variables that the managed device maintains and can be queried or set by the agent. MIB defines the attributes of the managed device, including the name, status, access rights, and data type of management objects.

    An agent can use the MIB to:

    • Learn device status.
    • Set device status.

    Similar to the Domain Name System (DNS), the SNMP MIB uses a tree structure with its root on the top without a name. Figure 1-2 shows a part of the MIB, called an object naming tree. Each object identifier (OID) maps a management object; for example, the system OID is and the interfaces OID is

    The OID tree facilitates information management and improves management efficiency. With the OID tree, the network administrator can query information in a batch.

    When configuring the agent, you can specify the MIB objects that the NMS can access in MIB views. An MIB view is a subset of an MIB.

    Figure 1-2  OID tree

Updated: 2019-03-06

Document ID: EDOC1100069336

Views: 33929

Downloads: 193

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