134
# 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 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 default UDP port 162 is used for SNMP notifications.
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 51
Network diagram
Configuration procedure
Configuring SNMPv3 in RBAC mode
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.)
# Create the user role
test
, and permit
test
to have read access to the
snmpMIB
node (OID
1.3.6.1.6.3.1), including the
linkUp
and
linkDown
objects..
<Agent> system-view
[Agent] role name test
[Agent-role-test] rule 1 permit read oid 1.3.6.1.6.3.1
# Assign user role
test
read-only access to the
system
node (OID: 1.3.6.1.2.1.1) and
read-write access to the
interfaces
node (OID: 1.3.6.1.2.1.2).
[Agent-role-test] rule 2 permit read oid 1.3.6.1.2.1.1
[Agent-role-test] rule 3 permit read write oid 1.3.6.1.2.1.2
[Agent-role-test] quit
# Create the SNMPv3 user
RBACtest
with the user role
test
, and enable the authentication
with privacy security model for the user. Set the authentication algorithm to
sha
, authentication
key to
123456TESTauth&!
, encryption algorithm to
aes128
, and privacy key to
123456TESTencr&!
.
Agent
1.1.1.1/24
NMS
1.1.1.2/24
