Basic SNMPv3 functions can be configured to allow an NMS to monitor and operate a managed device.
Before a local SNMPv3 user is configured on a device to communicate with an NMS, the user must be added to a user group at the AAA side, and the user group is associated with a specific task group. The task group consists of multiple tasks, and each task is mapped to a MIB object that is granted reading and writing permissions. Users assigned a specific task obtain the specified reading and writing permissions on MIB objects.
The system view is displayed.
AAA is enabled, and the AAA view is displayed.
A task group is created, and the task group view is displayed.
A task is added to the task group and granted permissions.
Each MIB object is associated with a specific task. Performing this step grants users permissions to MIB objects.
The AAA view is displayed.
A user group is created, and the user group view is displayed.
The user group is associated with a task group.
The AAA view is displayed.
A local user is created, and a password is set for the user to log in a device.
If an AAA user is configured as a local SNMP user, the user-name value is a string of 1 to 32 characters.
The local user is added to a user group.
A user group can be used by multiple local users. A local user belongs only to one user group.
The access type of the local user is set to SNMP.
The system view is displayed.
The SNMP agent function is enabled.
This step is optional because the SNMP agent function is enabled by running any snmp-agent command, irrespective of whether any parameter is specified.
The minimum SNMP password length is configured.
After this command is run, the length of a configured SNMP password must be longer than or equal to the minimum SNMP password length.
The port number monitored by the SNMP agent is changed.
The SNMP version is configured.
Local SNMP user information is configured.
The authentication password configured for an AAA user can be different from that for a local SNMP user. Deleting a local AAA user causes the local SNMP user to be also deleted. Deleting a local SNMP user, however, does not affect the local AAA user.
The priority of an SNMP USM user is higher than that of a local SNMP user. If an SNMP USM username is the same as a local SNMP username but different authentication and encryption passwords are configured for the users, the authentication and encryption passwords configured for the SNMP USM user are used for login.
By default, a device checks the complexity of the local users' authentication and encryption passwords. If the passwords fail the check, the user configuration fails. To disable the password complexity check, run the snmp-agent local-user password complexity-check disable command. It is recommended that the complexity check be enabled to ensure system security.
To improve system security, you are advised to configure different authentication and encryption passwords for a local SNMP user.
The device administrator contact information or location is configured.
This step is required for the NMS administrator to view contact information and locations of the device administrator when the NMS manages many devices. This helps the NMS administrator contact the device administrators for fault location and rectification.
The maximum size of an SNMP packet that the device can receive or send is set.
After the maximum size is set, the device discards any SNMP packet that is larger than the set size.
A source interface is configured for SNMP to receive and respond to NMS request packets.
All interfaces on the device are configured for SNMP to receive and respond to NMS request packets.
After the interface isolation attribute is set successfully, packets can be sent to the server only through the specified physical interface, and those sent through other interfaces are discarded.
An IPv6 source address is configured for SNMP to receive and respond to NMS request packets.
An isolated IPv6 source address is specified for the SNMP proxy to receive and respond to requests from the CCU.
All IPv6 addresses on the device are configured for SNMP to receive and respond to NMS request packets.
In scenarios such as interface unnumbered, if an isolated source interface and a common source interface (non-isolated source interface) are configured to listen to the same IP address and VPN instance, the common source interface takes effect. When the TCP listening mode is set to all-interface and an isolated source interface is configured, the isolated source interface takes effect if it is matched based on the 5-tuple matching rule; the all-interface configuration takes effect if the isolated source interface is not matched based on the 5-tuple matching rule. The source IP address specified for the isolated source interface does not need to be the interface's IP address.
An engine ID for the local SNMP entity is set.
To improve system security, run the snmp-agent packet contextengineid-check enable command to check whether the contextEngineID is consistent with the local engine ID.
The SET Response message caching function is enabled.
The SNMP IPv4 or IPv6 listening port is disabled.
After you disable the SNMP IPv4 or IPv6 listening port using the snmp-agent protocol server disable command, SNMP no longer processes SNMP packets. Exercise caution when you disable the SNMP IPv4 or IPv6 listening port.
The configuration is committed.