Configuring a Device to Communicate with an NMS by Running SNMPv2c
After SNMPv2c is configured, a managed device and an NMS can run SNMPv2c to communicate with each other. To ensure communication, you need to configure the agent and NMS. This section describes the configuration on a managed device (the agent side). For details about configuration on an NMS, see the pertaining NMS operation guide.
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 exist between switch and NMS.
Procedure
When you configure the device to communicate with the NMS using SNMPv2c, Configuring Basic SNMPv2c Functions is mandatory and optional steps can be performed in any sequence.
The access permission of the NMS that uses the configured community name is Viewdefault view. The internet MIB (OID: 1.3.6.1) 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 a specified NMS that uses the community name to manage specified objects on the device, follow the procedure described in Restricting Management Rights of the NMS.
To allow a specified module on the managed device to report traps to the NMS, follow the procedure described in Configuring the Trap/Inform Function.
If the NMS and managed device are both Huawei products, follow the procedure described in Enabling the SNMP Extended Error Code Function to allow the device to send more types of error codes. This allows more specific error identification and facilitates your fault location and rectification.
To make the index of an interface remain unchanged in the case of interface deletion or addition, system restart, or hardware or software configuration change, see Configuring the Constant Interface Index Feature.
