HP 6125G HP 6125G & 6125G/XG Blade Switches Fundamentals Configuration - Page 69

Configuring SNMPv1 or SNMPv2c settings

Page 69 highlights

Step 3. Configure an SNMP group and specify its access right. 4. Add a user to the SNMP group. Command snmp-agent group v3 group-name [ authentication | privacy ] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number | acl ipv6 ipv6-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 | acl ipv6 ipv6-acl-number ] * Remarks By default, no SNMP group is configured. N/A Configuring SNMPv1 or SNMPv2c settings Step 1. Enter system view. Command system-view Remarks N/A 2. Enable the SNMP agent. snmp-agent Optional. By default, the SNMP agent is disabled. You can enable SNMP agent with this command or any command that begins with snmp-agent. 3. Create or update MIB view information. snmp-agent mib-view { excluded | included } view-name oid-tree [ mask mask-value ] Optional. By default, the MIB view name is ViewDefault and OID is 1. 4. Configure SNMP NMS access right. • (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: Use either approach. The direct configuration approach is for SNMPv1 or SNMPv2c. The community name configured on the a. snmp-agent group { v1 | v2c } NMS should be consistent group-name [ read-view read-view ] with the username configured [ write-view write-view ] [ notify-view on the agent. notify-view ] [ acl acl-number | acl ipv6 ipv6-acl-number ] * The indirect configuration approach is for SNMPv3. b. snmp-agent usm-user { v1 | v2c } user-name group-name [ acl acl-number | acl ipv6 ipv6-acl-number ] * 63

  • 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

63
Step
Command
Remarks
3.
Configure an SNMP
group and specify its
access right.
snmp-agent
group
v3
group-name
[
authentication
|
privacy
]
[
read-view
read-view
] [
write-view
write-view
] [
notify-view
notify-view
] [
acl
acl-number
|
acl
ipv6
ipv6-acl-number
] *
By default, no SNMP group is
configured.
4.
Add a user to the SNMP
group.
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
|
acl
ipv6
ipv6-acl-number
] *
N/A
Configuring SNMPv1 or SNMPv2c settings
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable the SNMP agent.
snmp-agent
Optional.
By default, the SNMP agent
is disabled.
You can enable SNMP agent
with this command or any
command that begins with
snmp-agent
.
3.
Create or update MIB
view information.
snmp-agent mib-view
{
excluded
|
included
}
view
-
name
oid
-
tree
[
mask
mask-value
]
Optional.
By default, the MIB view
name is ViewDefault and
OID is 1.
4.
Configure SNMP NMS
access right.
(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
read-view
]
[
write-view
write-view
] [
notify-view
notify-view
] [
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 approach.
The direct configuration
approach is for SNMPv1 or
SNMPv2c. The community
name configured on the
NMS should be consistent
with the username configured
on the agent.
The indirect configuration
approach is for SNMPv3.