31-4
Catalyst 3560 Switch Software Configuration Guide
OL-8553-06
Chapter 31 Configuring SNMP
Understanding SNMP
The SNMP agent also sends unsolicited trap messages to notify an NMS that a significant event has
occurred on the agent. Examples of trap conditions include, but are not limited to, when a port or module
goes up or down, when spanning-tree topology changes occur, and when authentication failures occur.
SNMP Community Strings
SNMP community strings authenticate access to MIB objects and function as embedded passwords. In
order for the NMS to access the switch, the community string definitions on the NMS must match at least
one of the three community string definitions on the switch.
A community string can have one of these attributes:
• Read-only (RO)—Gives read access to authorized management stations to all objects in the MIB
except the community strings, but does not allow write access
• Read-write (RW)—Gives read and write access to authorized management stations to all objects in
the MIB, but does not allow access to the community strings
• When a cluster is created, the command switch manages the exchange of messages among member
switches and the SNMP application. The Network Assistant software appends the member switch
number (@esN, where N is the switch number) to the first configured RW and RO community
strings on the command switch and propagates them to the member switches. For more information,
see Chapter 6, “Clustering Switches” and see Getting Started with Cisco Network Assistant,
available on Cisco.com.
Using SNMP to Access MIB Variables
An example of an NMS is the CiscoWorks network management software. CiscoWorks 2000 software
uses the switch MIB variables to set device variables and to poll devices on the network for specific
information. The results of a poll can be displayed as a graph and analyzed to troubleshoot
internetworking problems, increase network performance, verify the configuration of devices, monitor
traffic loads, and more.
As shown in Figure 31-1, the SNMP agent gathers data from the MIB. The agent can send traps, or
notification of certain events, to the SNMP manager, which receives and processes the traps. Traps alert
the SNMP manager to a condition on the network such as improper user authentication, restarts, link
status (up or down), MAC address tracking, and so forth. The SNMP agent also responds to MIB-related
queries sent by the SNMP manager in get-request, get-next-request, and set-request format.
Figure 31-1 SNMP Network
For information on supported MIBs and how to access them, see Appendix A, “Supported MIBs.”
Get-request, Get-next-request,
Get-bulk, Set-request
Network device
Get-response, traps
43581
SNMP Manager
NMS
MIB
SNMP Agent