HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 76

Configuring SNMPv3 basic parameters, Table 12

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 76 highlights

Step 8. Configure the SNMP access right. Command Remarks Use either method. The username configured by using • (Method 1) Create an SNMP community: snmp-agent community { read | write } community-name [ mib-view view-name ] [ acl acl-number | acl ipv6 ipv6-acl-number ] * • (Method 2) Create an SNMPv1/v2c group, and add users to the group: a. snmp-agent group { v1 | v2c } group-name [ read-view view-name ] [ write-view method 1 is the same as that configured by using method 2. The username created by either method must be the same as the community name configured on the NMS. By default, no SNMP group exists. If the device starts up with the initial settings (or empty configuration), no SNMP community exists by default. view-name ] [ notify-view If the device starts up with the view-name ] [ acl acl-number | default configuration file (or acl ipv6 ipv6-acl-number ] * factory defaults), public is used as b. snmp-agent usm-user { v1 | v2c } user-name group-name [ acl acl-number | acl ipv6 the read-only community name and private is used as the read and write community name by default. ipv6-acl-number ] * For more information about the startup configuration, see Fundamentals Configuration Guide. 9. (Optional.) Configure the maximum SNMP packet size (in bytes) that the SNMP agent can handle. snmp-agent packet max-size byte-count The default is 1500 bytes. Configuring SNMPv3 basic parameters SNMPv3 users are managed in groups. All SNMPv3 users in a group share the same security model, but can use different authentication and privacy key settings. To implement a security model for a user and avoid SNMP communication failures, make sure the security model configuration for the group and the security key settings for the user are compliant with Table 12 and match the settings on the NMS. Table 12 Basic security setting requirements for different security models Security model Authentication with privacy Security model Security key settings keyword for the group for the user privacy Authentication key, privacy key Remarks If the authentication key or the privacy key is not configured, SNMP communication will fail. 70

  • 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
70
Step
Command
Remarks
8.
Configure the SNMP
access right.
•
(Method 1) Create an SNMP
community:
snmp-agent
community
{
read
|
write
}
community-name
[
mib-view
view-name
] [
acl
acl-number
|
acl
ipv6
ipv6-
acl-number
] *
•
(
Method 2) Create an SNMPv1/v2c
group, and add users to the 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 configured by using
method 1 is the same as that
configured by using method 2. The
username created by either
method must be the same as the
community name configured on the
NMS.
By default, no SNMP group exists.
If the device starts up with the initial
settings (or empty configuration),
no SNMP community exists by
default.
If the device starts up with the
default configuration file (or
factory defaults),
public
is used as
the read-only community name and
private
is used as the read and
write community name by default.
For more information about the
startup configuration, see
Fundamentals Configuration
Guide
.
9.
(Optional.) Configure
the maximum SNMP
packet size (in bytes)
that the SNMP agent
can handle.
snmp-agent packet max-size
byte
-
count
The default is 1500 bytes.
Configuring SNMPv3 basic parameters
SNMPv3 users are managed in groups. All SNMPv3 users in a group share the same security model, but
can use different authentication and privacy key settings. To implement a security model for a user and
avoid SNMP communication failures, make sure the security model configuration for the group and the
security key settings for the user are compliant with
Table 12
and match the settings on the NMS.
Table 12
Basic security setting requirements for different security models
Security model
Security model
keyword for the group
Security key settings
for the user
Remarks
Authentication with
privacy
privacy
Authentication key,
privacy key
If the authentication key or
the privacy key is not
configured, SNMP
communication will fail.