39
Ste
Command
Remarks
5. Create an
SNMPv3 user.
snmp-agent usm-user v3 user-name
group-name [ remote { ip-address | ipv6
ipv6-address } [ vpn-instance
vpn-instance-name ] ] [ { cipher | simple }
authentication-mode { md5 | sha }
auth-password [ privacy-mode { aes128 |
des56 } priv-password ] ] [ acl acl-number | acl
ipv6 ipv6-acl-number ] *
To send informs to an SNMPv3
NMS, you must use the remote
ip-address option to specify the IP
address of the NMS.
Configuring SNMPv1 or SNMPv2c access
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Enable the SNMP
agent.
snmp-agent
By default, the SNMP agent is
disabled.
3. (Optional.) Create or
update MIB view
information.
snmp-agent mib-view { excluded |
included } view-name oid-tree [ mask
mask-value ]
By default, the device has four views,
all of which are named ViewDefault:
• View 1 includes MIB subtree iso.
• View 2 does not include subtree
snmpUsmMIB.
• View 3 does not include subtree
snmpVacmMIB.
• View 4 does not include subtree
snmpModules.18.
4. Configure the SNMP
access right.
• (Method 1) Specify the SNMP NMS
access right directly by configuring
an SNMP community:
snmp-agent community { read |
write } [ simple | cipher ]
community-name [ mib-view
view-name ] [ acl acl-number | acl
ipv6 ipv6-acl-number ] *
• (Method 2) Configure an SNMP
group and add a user to the SNMP
group:
a. snmp-agent group { v1 | v2c }
group-name [ read-view
view-name ] [ write-view
view-name ] [ notify-view
view-name ] [ 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 ] *
Use either method.
The username in method 2 is
equivalent to the community name
used in method 1, and must be the
same as the community name
configured on the NMS.
By default, no SNMP group or SNMP
community exists.