Step
3.
Configure an SNMP
group and specify its
access right.
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 the SNMP
access right.
Command
snmp-agent group v3 group-name
[ authentication | privacy ]
[ read-view read-view ] [ write-view
write-view ] [ notify-view
notify-view ] [ acl acl-number ]
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 ]
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 [ acl acl-number |
mib-view view-name ] *
•
(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 ]
snmp-agent usm-user { v1 | v2c }
b.
user-name group-name [ acl
acl-number ]
51
Remarks
By default, no SNMP group is
configured.
If you specify the cipher keyword, the
values for the auth-password and
priv-password arguments are
considered cipher text.
Remarks
N/A
Optional.
By default, the SNMP agent
is disabled.
You can enable SNMP agent
with any command that
begins with snmp-agent,
except for the snmp-agent
calculate-password
command.
Optional.
By default, the MIB view
name is ViewDefault and
OID is 1.
Use either approach.
The username in approach 2
is equivalent to the
community name used in
approach 1, and must be the
same as the community name
configured on the NMS.