Table of Contents
Advertisement
Step
4.
Add a user to the SNMP
group.
Configuring SNMPv1 or SNMPv2c settings
Step
1.
Enter system view.
2.
Enable the SNMP
agent.
3.
Create or update MIB
view information.
4.
Configure SNMP NMS
access right.
NMS login example
Network requirements
Configure the device and the NMS so you can remotely manage the device through SNMPv3.
Command
snmp-agent usm-user v3
user-name group-name [ [ cipher ]
authentication-mode { md5 |
sha } auth-password
[ privacy-mode { 3des | aes128 |
des56 } priv-password ] ] [ acl
acl-number | acl ipv6
ipv6-acl-number ] *
Command
system-view
snmp-agent
snmp-agent mib-view { excluded |
included } view-name oid-tree [ mask
mask-value ]
•
(Approach 1) Specify the SNMP NMS
access right directly by configuring an
SNMP community:
snmp-agent community { read |
write } community-name [ mib-view
view-name ] [ acl acl-number | acl ipv6
ipv6-acl-number ] *
•
(Approach 2) Configure an SNMP
group and add a user to the SNMP
group:
a. snmp-agent group { v1 | v2c }
group-name [ read-view
read-view ] [ write-view write-view ]
[ notify-view notify-view ] [ acl
acl-number | acl ipv6
ipv6-acl-number ] *
b. snmp-agent usm-user { v1 | v2c }
user-name group-name [ acl
acl-number | acl ipv6
ipv6-acl-number ] *
57
Remarks
N/A
Remarks
N/A
Optional.
By default, the SNMP agent
is disabled.
You can enable SNMP
agent with this command or
any command that begins
with snmp-agent.
Optional.
By default, the MIB view
name is ViewDefault and
OID is 1.
Use either approach.
The direct configuration
approach is for SNMPv1 or
SNMPv2c. The community
name configured on the
NMS should be consistent
with the username
configured on the agent.
The indirect configuration
approach is for SNMPv3.
Advertisement
Table of Contents
