HP 6125XLG R2306-HP 6125XLG Blade Switch Fundamentals Configuration Guide - Page 42

Configuring SNMPv1 or SNMPv2c access

Page 42 highlights

Step 5. Create an SNMPv3 user. Command Remarks 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 Step 1. Enter system view. 2. Enable the SNMP agent. 3. (Optional.) Create or update MIB view information. 4. Configure the SNMP access right. Command Remarks system-view N/A snmp-agent By default, the SNMP agent is disabled. snmp-agent mib-view { excluded | included } view-name oid-tree [ mask mask-value ] • (Method 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 ] * • (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 ] * 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. 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. 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155

35
Step
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
Step
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
} 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.