Configuring Snmpv1 Or Snmpv2C Access - HP 12500 Configuration Manual

Step
5. Create
SNMPv3 user.

Configuring SNMPv1 or SNMPv2c access

Step
1. Enter system view.
2. Enable
agent.
3. (Optional.) Create or
update
information.
4. Configure the SNMP
access right.
Command
snmp-agent usm-user v3 user-name
group-name [ remote { ip-address | ipv6
ipv6-address } [ vpn-instance
an
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 ] *
Command
system-view
the SNMP
snmp-agent
snmp-agent mib-view { excluded |
MIB view
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
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 ] *
Remarks
N/A
By default, the SNMP agent is
disabled.
By default, the device has four views,
all of which are named ViewDefault:
•
•
•
•
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.
By default, no SNMP group or SNMP
community exists.
56
Remarks
To send informs to an SNMPv3
NMS, you must use the remote
ip-address option to specify the IP
address of the NMS.
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.