94
NOTE:
The SNMP settings on the agent and the NMS must match.
3.
Verify the configuration:
# Try to get the MTU value of NULL0 interface from the agent. The attempt succeeds.
Send request to 1.1.1.1/161 ...
Protocol version: SNMPv1
Operation: Get
Request binding:
1: 1.3.6.1.2.1.2.2.1.4.135471
Response binding:
1: Oid=ifMtu.135471 Syntax=INT Value=1500
Get finished
# Use a wrong community name to get the value of a MIB node on the agent. You can see an
authentication failure trap on the NMS.
1.1.1.1/2934 V1 Trap = authenticationFailure
SNMP Version = V1
Community = public
Command = Trap
Enterprise = 1.3.6.1.4.1.43.1.16.4.3.50
GenericID = 4
SpecificID = 0
Time Stamp = 8:35:25.68
SNMPv3 in VACM mode configuration example
Network requirements
As shown in
, the NMS (1.1.1.2/24) uses SNMPv3 to monitor and manage the interface
status of the agent (1.1.1.1/24). The agent automatically sends notifications to report events to the
NMS.
The NMS and the agent perform authentication when they establish an SNMP session. The
authentication algorithm is SHA-1 and the authentication key is
123456TESTauth&!
. The NMS and
the agent also encrypt the SNMP packets between them by using the AES algorithm and the privacy
key
123456TESTencr&!
.
Figure 30 Network diagram
Configuration procedure
1.
Configure the agent:
# Configure the IP address of the agent, and make sure the agent and the NMS can reach each
other. (Details not shown.)
# Assign the NMS (SNMPv3 group
managev3group
) read and write access to the objects
under the
ifTable
node (OID 1.3.6.1.2.1.2.2), and deny its access to any other MIB object.
<Agent> system-view
