Configuring a Device to Communicate with an NMS Using SNMPv3 USM User

After SNMPv3 is configured, a managed device and an NMS can run SNMPv3 to communicate with each other. To ensure communication, you need to configure the agent and NMS. This section only describes the configuration on a managed device (the agent side). For details about configurations on an NMS, see the NMS operation guide.

Usage Scenario

The NMS manages a device by the following ways:

Sends requests to the managed device to perform the GetRequest, GetNextRequest, GetResponse, GetBulk, or SetRequest operation, obtaining data or setting values.
Receives alarms (traps or informs) from the managed device to locate and handle device faults based on the alarm information.

Pre-configuration Tasks

Before configuring a device to communicate with an NMS using SNMPv3 USM User, configure a routing protocol to ensure that at least one route exists between the router and NMS.

Configuration Procedures

Figure 1 Flowchart for configuring a device to communicate with an NMS using SNMPv3 USM User

Configuring Basic SNMPv3 Functions: After basic SNMP functions are configured, the NMS can perform basic operations, such as Get and Set operations on the managed device, and the managed device can send alarms to the NMS.

(Optional) Controlling the NMS's Access to the Device: This section describes how to specify an NMS and manageable MIB objects for SNMPv3-based communication between the NMS and managed device to improve communication security.

(Optional) Configuring the Trap Function: The device can be configured to send specified traps to the NMS, which facilitates fault locating. To enhance the trap transmission security, specify parameters for sending traps.

(Optional) Configuring the Inform Function: The router enabled with the SNMP agent function can generate two types of notifications: trap messages and Inform messages. Trap messages are messages alerting the NMS to a condition on the network. Inform messages are trap messages that include a request for confirmation of receipt from the NMS (Inform messages are resent until a reply is received). Inform messages are more reliable than trap messages.

(Optional) Configuring SNMPv3 Anti-Attack: To defense against a user's attack on other users' passwords, configuring the SNMPv3 blacklist function to improve security.

Verifying the Configuration for a Device to Communicate with an NMS Using SNMPv3 USM User: After configuring basic SNMPv3 functions, verify the configuration.