47-5
Catalyst 6500 Series Switch Software Configuration Guide—Release 8.7
OL-8978-04
Chapter 47 Configuring SNMP
Understanding How SNMPv1 and SNMPv2c Work
Note the following about the SNMPv3 objects:
•
Each user belongs to a group.
•
A group defines the access policy for a set of users.
•
SNMP objects access an access policy for reading, writing, and creating.
•
A group determines the list of notifications that its users can receive.
•
A group also defines the security model and security level for its users.
SNMP ifindex Persistence
The SNMP ifIndex persistence feature is always enabled. With ifIndex persistence, the ifIndex value of
the port and VLAN is always retained and used after these occurrences:
•
Switch reboot
•
High-availability switchover
•
Software upgrade
•
Module reset
•
Module removal and insertion of the same type of module
For Fast EtherChannel and Gigabit EtherChannel interfaces, the ifIndex value is only retained and used
after a high-availability switchover.
Understanding How SNMPv1 and SNMPv2c Work
The components of SNMPv1 and SNMPv2c network management fall into three categories:
•
Managed devices (such as a switch)
•
SNMP agents and MIBs, including the Remote Monitoring (RMON) MIBs, which run on managed
devices
•
SNMP network management applications, such as CiscoWorks2000, which communicate with the
agents to get the statistics and the alerts from the managed devices. See the
“Using
CiscoWorks2000” section on page 47-6
for more information on CiscoWorks2000.
Note
An SNMP management application, together with the computer it runs on, is called a
Network Management System (NMS).
Using Managed Devices
Catalyst 6500 series switches are managed devices that support the SNMP network management with
these features:
•
SNMP traps (see the
“Configuring SNMPv1 and SNMPv2c from the CLI” section on page 47-11
)
•
RMON in the supervisor engine software (see
Chapter 48, “Configuring RMON”
)
•
RMON and RMON2 on an external SwitchProbe device
