Configuring a Device to Communicate with an NMS by Running SNMPv2c
Context
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.
The NMS using the specified community name can access the Viewdefault view. The internet MIB (OID: 1.3.6.1) 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.
To allow an NMS that uses a specified community name to manage specified objects on the device, perform the operations in Restricting Management Rights of the NMS.
To allow a specified module on the managed device to report traps to the NMS, perform the operations in Configuring the Trap Function.
If the NMS and managed device are both Huawei products, perform the operations in Enabling the SNMP Extended Error Code Function to allow the managed device to send more types of error codes. More error codes facilitate your fault location and rectification.
Previous
