HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 73

snmp-agent community

Page 73 highlights

Examples # Use the local engine and the MD5 algorithm to convert the plaintext key authkey to an encrypted key. system-view [Sysname] snmp-agent calculate-password authkey mode md5 local-engineid The secret key is: 09659EC5A9AE91BA189E5845E1DDE0CC snmp-agent community Syntax snmp-agent community { read | write } community-name [ mib-view view-name ] [ acl acl-number | acl ipv6 ipv6-acl-number ] * View undo snmp-agent community { read | write } community-name System view Default level 3: Manage level Parameters read: Assigns the specified community the read only access to MIB objects. A read-only community can only inquire MIB information. write: Assigns the specified community the read and write access to MIB objects. A read and write community can configure MIB information. community-name: Specifies the community name, a string of 1 to 32 characters. mib-view view-name: Specifies the MIB view available for the community. The view-name argument represents a MIB view name, which is a string of 1 to 32 characters. A MIB view represents a set of accessible MIB objects. If no MIB view is specified, the specified community can access the MIB objects in the default MIB view ViewDefault. To create a MIB view, use the snmp-agent mib-view command. acl acl-number: Specifies a basic ACL to filter NMSs by source IPv4 address. The acl-number argument represents a basic ACL number in the range of 2000 to 2999. Only the NMSs with the IP addresses permitted in the ACL can use the specified community name to access the SNMP agent. acl ipv6 ipv6-acl-number: Specifies a basic ACL to filter NMSs by source IPv6 address. The ipv6-acl-number argument represents a basic ACL number in the range of 2000 to 2999. Only the NMSs with the IPv6 addresses permitted in the ACL can use the community name to access the SNMP agent. Description Use snmp-agent community to configure an SNMP community. Use undo snmp-agent community to delete an SNMP community. This command is for SNMPv1 and SNMPv2c. A community comprises NMSs and SNMP agents, and is identified by a community name. When devices in a community communicate with each other, they use the community name for authentication. An NMS and an SNMP agent can access each other only when they are configured with the same community name. Typically, public is used as the read-only community name, and private is used as the read and write community name. To improve security, assign your SNMP communities a name other than public and private. 67

  • 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
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

67
Examples
# Use the local engine and the MD5 algorithm to convert the plaintext key
authkey
to an encrypted key.
<Sysname> system-view
[Sysname] snmp-agent calculate-password authkey mode md5 local-engineid
The secret key is: 09659EC5A9AE91BA189E5845E1DDE0CC
snmp-agent community
Syntax
snmp-agent community
{
read
|
write
}
community
-
name
[
mib-view
view-name
] [
acl
acl-number
|
acl
ipv6
ipv6-acl-number
] *
undo snmp-agent community
{
read
|
write
}
community
-
name
View
System view
Default level
3: Manage level
Parameters
read
: Assigns the specified community the read only access to MIB objects. A read-only community can
only inquire MIB information.
write
: Assigns the specified community the read and write access to MIB objects. A read and write
community can configure MIB information.
community
-
name
: Specifies the community name, a string of 1 to 32 characters.
mib-view
view-name
: Specifies the MIB view available for the community. The
view-name
argument
represents a MIB view name, which is a string of 1 to 32 characters. A MIB view represents a set of
accessible MIB objects. If no MIB view is specified, the specified community can access the MIB objects
in the default MIB view
ViewDefault
. To create a MIB view, use the
snmp-agent mib-view
command.
acl
acl-number
: Specifies a basic ACL to filter NMSs by source IPv4 address. The
acl-number
argument
represents a basic ACL number in the range of 2000 to 2999. Only the NMSs with the IP addresses
permitted in the ACL can use the specified community name to access the SNMP agent.
acl ipv6
ipv6-acl-number
: Specifies a basic ACL to filter NMSs by source IPv6 address. The
ipv6-acl-number
argument represents a basic ACL number in the range of 2000 to 2999. Only the NMSs
with the IPv6 addresses permitted in the ACL can use the community name to access the SNMP agent.
Description
Use
snmp-agent community
to configure an SNMP community.
Use
undo snmp-agent community
to delete an SNMP community.
This command is for SNMPv1 and SNMPv2c.
A community comprises NMSs and SNMP agents, and is identified by a community name. When
devices in a community communicate with each other, they use the community name for authentication.
An NMS and an SNMP agent can access each other only when they are configured with the same
community name. Typically,
public
is used as the read-only community name, and
private
is used as the
read and write community name. To improve security, assign your SNMP communities a name other than
public
and
private
.