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, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 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).
Configuring a Device to Communicate with an NMS by Running SNMPv2c

Configuring a Device to Communicate with an NMS by Running SNMPv2c


To allow a device to communicate with an NMS running SNMPv2c, configure SNMPv2c on the device. The SNMP parameters must be configured on both the managed device (agent) and NMS. This section describes only the SNMP configurations on the agent side. For details about SNMP configurations on an NMS, see the NMS operation guide.

A lack of authentication capabilities in SNMPv1 and SNMPv2c results in vulnerability to security threats, so SNMPv3 is recommended.

Pre-configuration Tasks

Before configuring a device to communicate with an NMS by running SNMPv2c, configure a routing protocol to ensure that at least one route exists between router and NMS.

Configuration Process

When you configure a device to communicate with the NMS using SNMPv2c, Configuring Basic SNMPv2c Functions is mandatory and optional steps can be performed in any sequence.

After the SNMP basic functions are configured, the router and NMS can communicate with each other.
  • The NMS using the specified community name can access the Viewdefault view. The internet MIB (OID: and the lagMIB (OID: 1.2.840.10006.300.43) can be operated in this view.

  • The managed device sends traps generated by the modules that are enabled by default to the NMS.

The following are more configurations related to SNMPv2c:
Updated: 2019-05-17

Document ID: EDOC1000174072

Views: 122421

Downloads: 372

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next