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 Access Process

MIB Access Process

This section describes the MIB access process.

MIB Access Process

Before accessing MIB objects, ensure that the following conditions are met:

  1. All NMS- and device-side parameters have been configured.

    For details on how to set device-side parameters, see Configuring a Device to Communicate with an NMS Using SNMP. For details on how to set NMS-side parameters, see the NMS operation manual.

  2. MIB files have been compiled in the MIB Browser and loaded to the MIB file list.


    This document uses the MG-SOFT MIB Browser as the NMS software to illustrate the operations. If you use other NMS software, refer to documentation of the specified software.

    MG-SOFT MIB Browser is an open source software. You can download related documents at

You can perform operations for the MIB objects that have been imported in the MIB Browser. The agent uses UDP port 161 to receive Request packets from the NMS and return Response packets. After the NMS receives the Response packets, the NMS displays the return values corresponding to the operations. When the status of the managed device changes, for example, link failure or load exceeding the threshold, the agent on the managed device can send trap messages to the NMS to report exceptions.

Updated: 2019-07-19

Document ID: EDOC1000174090

Views: 483781

Downloads: 48

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