Chapter 4: SNMPv1 and SNMPv2c
90
Section I: Basic Operations
Community String Attributes
A community string has attributes for controlling who can use the string
and what the string will allow a network management to do on the switch.
The community string attributes are defined below:
Community
String Name
A community string must have a name of one to eight alphanumeric
characters. Spaces are allowed.
Access Mode
This attribute defines the permissions of a community string. There are
two access modes: Read and Read/Write. A community string with an
access mode of Read can only be used to view but not change the MIB
objects on a switch. A community string with a Read/Write access can be
used to both view the MIB objects and change them.
Operating Status
A community string can be enabled or disabled. When disabled, no one
can use it to access the switch. You might disable a community string if
you suspect someone is using it for unauthorized access to the device.
When a community string is enabled, then it is available for use.
Open or Closed
Access Status
This feature controls which management stations on your network can use
a community string. An open access status permits any network manager
who knows the community string to use it. A closed access status restricts
the string to those network managers who work at particular workstations,
identified by their IP addresses. You specify the workstations by assigning
the IP addresses of the workstations to the community string. A closed
community string can have up to eight IP addresses of management
workstations.
If you decide to activate SNMP management on the switch, it is a good
idea to assign a closed status to all community strings that have a Read/
Write access mode and then assign the IP addresses of your
management workstations to those strings. This helps reduce the chance
of someone gaining management access to a switch through a community
string and making unauthorized configuration changes.
Trap Receivers
A trap is a signal sent to one or more management workstations by the
switch to indicate the occurrence of a particular operating event on the
device. There are numerous operating events that can trigger a trap. For
instance, resetting the switch or the failure of a cooling fan are two
examples of occurrences that cause a switch to send a trap to the
management workstations. You can use traps to monitor activities on the
switch.
Trap receivers are the devices, typically management workstations or
servers, that you want to receive the traps sent by the switch. You specify
the trap receivers by their IP addresses. You assign the IP addresses to
Содержание AT-S63
Страница 14: ...Figures 14 ...
Страница 18: ...Tables 18 ...
Страница 28: ...28 Section I Basic Operations ...
Страница 58: ...Chapter 1 Overview 58 ...
Страница 76: ...Chapter 2 AT 9400Ts Stacks 76 Section I Basic Operations ...
Страница 96: ...Chapter 5 MAC Address Table 96 Section I Basic Operations ...
Страница 114: ...Chapter 8 Port Mirror 114 Section I Basic Operations ...
Страница 116: ...116 Section II Advanced Operations ...
Страница 146: ...Chapter 12 Access Control Lists 146 Section II Advanced Operations ...
Страница 176: ...Chapter 14 Quality of Service 176 Section II Advanced Operations ...
Страница 196: ...196 Section III Snooping Protocols ...
Страница 204: ...Chapter 18 Multicast Listener Discovery Snooping 204 Section III Snooping Protocols ...
Страница 216: ...Chapter 20 Ethernet Protection Switching Ring Snooping 216 Section III Snooping Protocols ...
Страница 218: ...218 Section IV SNMPv3 ...
Страница 234: ...234 Section V Spanning Tree Protocols ...
Страница 268: ...268 Section VI Virtual LANs ...
Страница 306: ...Chapter 27 Protected Ports VLANs 306 Section VI Virtual LANs ...
Страница 320: ...320 Section VII Internet Protocol Routing ...
Страница 360: ...Chapter 30 BOOTP Relay Agent 360 Section VII Routing ...
Страница 370: ...Chapter 31 Virtual Router Redundancy Protocol 370 Section VII Routing ...
Страница 372: ...372 Section VIII Port Security ...
Страница 402: ...Chapter 33 802 1x Port based Network Access Control 402 Section VIII Port Security ...
Страница 404: ...404 Section IX Management Security ...
Страница 436: ...Chapter 36 PKI Certificates and SSL 436 Section IX Management Security ...
Страница 454: ...Chapter 38 TACACS and RADIUS Protocols 454 Section IX Management Security ...
Страница 462: ...Chapter 39 Management Access Control List 462 Section IX Management Security ...
Страница 504: ...Appendix B SNMPv3 Configuration Examples 504 Security Model Security Level Storage Type SNMPv3 Parameters Continued ...
Страница 532: ...Appendix D MIB Objects 532 ...