
Chapter 1
| Initial Switch Configuration
Enabling SNMP Management Access
– 68 –
To configure a community string, complete the following steps:
1.
From the Privileged Exec level global configuration mode prompt, type “snmp-
server community
string
mode
,” where “string” is the community access string
and “mode” is
rw
(read/write) or
ro
(read only). Press <Enter>. (Note that the
default mode is read only.)
2.
To remove an existing string, simply type “no snmp-server community
string
,”
where “string” is the community access string to remove. Press <Enter>.
Console(config)#snmp-server community admin rw
Console(config)#snmp-server community private
Console(config)#
Note:
If you do not intend to support access to SNMP version 1 and 2c clients, we
recommend that you delete both of the default community strings. If there are no
community strings, then SNMP management access from SNMP v1 and v2c clients
is disabled.
Trap Receivers
You can also specify SNMP stations that are to receive traps from the switch. To
configure a trap receiver, use the “snmp-server host” command. From the
Privileged Exec level global configuration mode prompt, type:
“snmp-server host
host-address
community-string
[version {1 | 2c | 3 {auth |
noauth | priv}}]”
where “host-address” is the IP address for the trap receiver, “community-string”
specifies access rights for a version 1/2c host, or is the user name of a version 3 host,
“version” indicates the SNMP client version, and “auth | noauth | priv” means that
authentication, no authentication, or authentication and privacy is used for v3
clients. Then press <Enter>. For a more detailed description of these parameters,
see the
command. The following example creates a trap host for
each type of SNMP client.
Console(config)#snmp-server host 10.1.19.23 batman
Console(config)#snmp-server host 10.1.19.98 robin version 2c
Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth
Console(config)#
Configuring Access for SNMP Version 3 Clients
To configure management access for SNMPv3 clients, you need to first create a
view that defines the portions of MIB that the client can read or write, assign the
view to a group, and then assign the user to a group. The following example creates
one view called “mib-2” that includes the entire MIB-2 tree branch, and then
Summary of Contents for AS5700-54X
Page 42: ...Contents 42...
Page 44: ...Figures 44...
Page 52: ...Tables 52...
Page 54: ...Section I Getting Started 54...
Page 80: ...Chapter 1 Initial Switch Configuration Setting the System Clock 80...
Page 210: ...Chapter 6 Remote Monitoring Commands 210...
Page 358: ...Chapter 9 Access Control Lists ACL Information 358...
Page 418: ...Chapter 12 Port Mirroring Commands RSPAN Mirroring Commands 418...
Page 436: ...Chapter 15 UniDirectional Link Detection Commands 436...
Page 442: ...Chapter 16 Address Table Commands 442...
Page 506: ...Chapter 18 VLAN Commands Configuring VXLAN Tunneling 506...
Page 526: ...Chapter 19 Class of Service Commands Priority Commands Layer 3 and 4 526...
Page 544: ...Chapter 20 Quality of Service Commands 544...
Page 652: ...Chapter 22 Multicast Filtering Commands MLD Proxy Routing 652...
Page 680: ...Chapter 23 LLDP Commands 680...
Page 722: ...Chapter 24 CFM Commands Delay Measure Operations 722...
Page 732: ...Chapter 25 Domain Name Service Commands 732...
Page 790: ...Chapter 27 IP Interface Commands ND Snooping 790...
Page 1072: ...Section III Appendices 1072...
Page 1102: ...List of CLI Commands 1102...
Page 1115: ......
Page 1116: ...AS5700 54X AS6700 32X E032016 ST R02 149100000198A...