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

In FIPS mode, represents a view record. If

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 78 highlights

Step Command Remarks 6. (Optional.) Change the local snmp-agent local-engineid engine ID. engineid snmp-agent remote { ip-address | 7. (Optional.) Configure a remote ipv6 ipv6-address } [ vpn-instance engine ID. vpn-instance-name ] engineid engineid By default, the local engine ID is the company ID plus the device ID. IMPORTANT: After you change the local engine ID, the existing SNMPv3 users and encrypted keys become invalid, and you must re-configure them. By default, no remote engine ID is configured. To send informs to an SNMPv3 NMS, you must configure the SNMP engine ID of the NMS. By default, the MIB view ViewDefault is predefined. In this view, all the MIB objects in the iso subtree but the snmpUsmMIB, snmpVacmMIB, and snmpModules.18 subtrees are accessible. 8. (Optional.) Create or update a snmp-agent mib-view { excluded | MIB view. included } view-name oid-tree [ mask mask-value ] Each view-name oid-tree pair represents a view record. If you specify the same record with different MIB sub-tree masks multiple times, the most recent configuration takes effect. Except for the four sub-trees in the default MIB view, you can create up to 16 unique MIB view records. 9. Create an SNMPv3 group. • In non-FIPS mode: snmp-agent group v3 group-name [ authentication | privacy ] [ read-view view-name ] [ write-view view-name ] [ notify-view view-name ] [ acl acl-number | acl ipv6 ipv6-acl-number ] * • In FIPS mode: 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 exists. 72

  • 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
72
Step
Command
Remarks
6.
(Optional.) Change the local
engine ID.
snmp-agent local-engineid
engineid
By default, the local engine ID is
the company ID plus the device
ID.
IMPORTANT:
After you change the local engine
ID, the existing SNMPv3 users and
encrypted keys become invalid,
and you must re-configure them.
7.
(Optional.) Configure a remote
engine ID.
snmp-agent
remote
{
ip-address
|
ipv6
ipv6-address
} [
vpn-instance
vpn-instance-name
]
engineid
engineid
By default, no remote engine ID is
configured.
To send informs to an SNMPv3
NMS, you must configure the
SNMP engine ID of the NMS.
8.
(Optional.) Create or update a
MIB view.
snmp-agent mib-view
{
excluded
|
included
}
view
-
name
oid
-
tree
[
mask
mask-value
]
By default, the MIB view
ViewDefault
is predefined. In this
view, all the MIB objects in the
iso
subtree but the
snmpUsmMIB
,
snmpVacmMIB
, and
snmpModules.18
subtrees are
accessible.
Each
view-name oid-tree
pair
represents a view record. If you
specify the same record with
different MIB sub-tree masks
multiple times, the most recent
configuration takes effect. Except
for the four sub-trees in the default
MIB view, you can create up to
16 unique MIB view records.
9.
Create an SNMPv3 group.
•
In non-FIPS mode:
snmp-agent
group
v3
group-name
[
authentication
|
privacy
] [
read-view
view-name
] [
write-view
view-name
] [
notify-view
view-name
] [
acl
acl-number
|
acl
ipv6
ipv6-acl-number
] *
•
In FIPS mode:
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
exists.