|
|
You can gather status information and statistical data using the console panels of the Catalyst 3900 or the command line interface of the Catalyst 5000. In addition, the Catalyst Token Ring switches support other forms of network management, including:
This chapter provides an overview of the network management support provided with the Catalyst Token Ring switches.
There are two methods that you can use to manage the Catalyst Token Ring switches; using SNMP-based managers and using RMON.
Most Token Ring switches, including the Catalyst Token Ring switches, can be managed using SNMP. There are a several SNMP MIB definitions for Token Ring information and switches. The Catalyst Token Ring switches support the following standard MIBs:
In addition, the Catalyst Token Ring switches support the following Cisco-defined private MIBs:
For SNMP-managed switches, it is possible to monitor and configure the switch from a network management application, which typically has a GUI that provides a simulated view of the front and rear panels of the switch.
Cisco provides SNMP-based network management applications that can be used to manage switches. For more information about these applications, see the"Configuring and Managing Token Ring Switches using Cisco's Network Management Products" chapter.
RMON is an industry-standard method for providing network statistics monitoring using SNMP. It also collects fault, performance, and configuration statistics. RMON can also be used to supplant traffic analyzers by providing packet capture or tracing data through the switch or on a ring.
In typical SNMP management, the SNMP client has to continuously poll the switch for fault, performance, and configuration information while waiting for the value to change. This causes increased traffic through the network. With RMON, you can have the switch monitor a particular statistic internally and when the statistic reaches a threshold the switch sends a trap to the client. This monitoring method reduces traffic between the SNMP client and the switch.
It is expensive to provide full-packet capture in a Token Ring switch because of the amount of memory required to store the information. Therefore, a solution is to use an internal RMON capability to gather traffic statistics and an external RMON probe for packet capture and higher-layer protocol analysis. The external RMON probe can be connected to the switch via a port mirroring port such as Cisco's SPAN ports.
As an option, the Catalyst Token Ring switches provide RMON support for statistics, history, alarms, and events. They also provide support for the following groups of the Token Ring extensions to the Remote Network Monitoring MIB (RFC 1513):
You can use an external RMON probe for full RMON support.
Access to RMON data is available only via an SNMP management application that supports RFC 1757 and RFC 1513. You cannot access RMON via the switch's console interface; however, the console statistics provide similar information. For full utilization of RMON data, you should use the traffic management services of CWSI. For more information about CWSI, see the "Configuring and Managing Token Ring Switches using Cisco's Network Management Products" chapter.
To aid in network management, Cisco developed the Cisco Discovery Protocol (CDP). CDP allows the Catalyst Token Ring switches to establish communication with other models of Cisco equipment. CDP support is provided as part of the Cisco IOS software that runs on many types of Cisco equipment.
CDP is a media- and protocol-independent protocol that is intended to be run on Cisco-manufactured equipment including routers, bridges, access servers, and switches. With CDP, Cisco's network management applications and Cisco devices can learn the device type and the SNMP agent address of neighboring devices. This enables applications to send SNMP queries to neighboring devices.
CDP runs on various media that support the SNAP, including LAN, Frame Relay, and ATM media. CDP runs over the data link layer only. Therefore, two systems that support different network-layer protocols can learn about each other.
All Cisco devices transmit CDP packets periodically. These packets advertise a time-to-live value in seconds, which indicates the length of time that the packet must be retained before it can be discarded. CDP packets are sent with a time-to-live value that is nonzero after an interface is enabled and with a time-to-live value of zero immediately before an interface is idled down. This provides for quick state discovery.
All Cisco devices receive CDP packets and cache the information in the packet. The cached information is available to network management. Cisco devices never forward a CDP packet. If any information changes from the last received packet, the new information is cached and the older information is discarded even if its time-to-live value has not yet expired.
CDP is assigned the Cisco HDLC protocol type value 0x2000. A Cisco-proprietary SNAP value enumerates HDLC protocol type values so CDP can run on all media that support SNAP, such as LAN media, Frame Relay, and ATM.
The SNAP format is as follows:
CDP sends packets on LANs using the multicast address 0100.0CCC.CCCC.
Because CDP does not run on top of any network layer, but rather runs only over the data link layer, two systems that support different network layer protocols can use CDP to learn about each other.
For more information about the format of CDP frames, see the "Frame Formats" appendix.
To aid with VLAN management, Cisco developed VTP. As explained in the "VLAN Trunking Protocol" section of the "Token Ring VLANs and Related Protocols" chapter, VTP is used to set up and manage VLANs across an entire management domain. Using VTP, you can configure and manage the VLANs within a management domain from a single switch that is configured to act as a VTP server.
In addition, Cisco provides the following SNMP-based network management applications that can be used to manage VLANs:
For more information about these applications, see the "Configuring and Managing Token Ring Switches using Cisco's Network Management Products" chapter.
To aid with traffic management, the Catalyst 3900 supports the SPAN.
With SPAN, traffic from any port on the switch can be mirrored or copied to another port, which is designated as the SPAN port. You can then connect the SPAN port to an external RMON probe.
This capability allows you to use the internal RMON to determine where problems might exist, and the external RMON to perform detailed problem analysis. For example, if the internal RMON statistics show high traffic on port 5, you can set up an external RMON probe remotely to capture data from port 5 to obtain more information.
Because forwarding to the SPAN port takes place independently of the normal forwarding, switch performance is not impacted.
As an alternative, you can establish a 16-Mbps monitor ring from the centralized data center that connects to all the SPAN ports on Token Ring switches. Then, you can connect the RMON probe or traffic analyzer at the data center, and via software control, the RMON probe can monitor any port on any switch in the network. Central control of remote monitoring is a powerful tool for the network manager.
On the Catalyst 3900, you can monitor traffic that is processed by an ISL or ATM port on a per-TrCRF basis (monitoring only one TrCRF at a time). You cannot, however, use an ISL or ATM port to monitor other ports.
 | Caution Using SPAN on more than one switch at a time may overload the monitoring ring. Also monitoring a TrCRF on a high-speed uplink, such as ATM or ISL, may overload the monitoring ring. |
Posted: Wed Oct 2 03:40:11 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.