Configuring a Local SNMPv3 User on a Device to Communicate with an NMS

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.

Applicable Environment

AAA is an authentication, authorization, and accounting technique. AAA local users can be configured to log in to a device through FTP, Telnet, or SSH. However, SNMPv3 supports only SNMP users, which can be an inconvenience in unified network device management.

To resolve this issue, configure SNMP to support AAA users. AAA users can then access the NMS, and MIB node operation authorization can be performed based on tasks. The NMS does not distinguish AAA users and SNMP users.

Figure 1 shows the process of an AAA user logging in to the NMS through SNMP.

Figure 1 Process of an AAA user logging in to the NMS through SNMP

After completing the following configuration task, an NMS can communicate with a device to be managed. To perform refined management, refer to the follow-up configuration procedure.

Pre-configuration Tasks

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

Configuration Procedure

Figure 2 Flowchart for configuring a local SNMPv3 user on a device to communicate with an NMS

Configuring Basic SNMPv3 Functions: Basic SNMPv3 functions can be configured to allow an NMS to monitor and operate a managed device.

(Optional) Configuring SNMP 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 Local SNMPv3 User on a Device to Communicate with an NMS: After configuring basic SNMPv3 functions, verify the configuration.