Table of Contents
Release Notes for Catalyst 5000 Series Software Release 2.1(x)
Current Release
2.1(12)
Previous Releases
2.1(11), 2.1(10), 2.1(9), 2.1(8), 2.1(7), 2.1(6), 2.1(5), 2.1(4), 2.1(3), 2.1(2), 2.1(1)
These release notes describe the features, modifications, and caveats for Catalyst 5000 series supervisor engine software release 2.1(x) and all 2.1(x) maintenance releases. The current 2.1(x) release is supervisor engine software release 2.1(12).
 | Caution
Always back up the switch configuration file before upgrading or downgrading the switch software to avoid losing all or part of the configuration stored in nonvolatile RAM (NVRAM). Use the write network command to back up your configuration to a Trivial File Transfer Protocol (TFTP) server. |
Note Although the software image in a new Catalyst 5000 series switch will operate correctly, later software images containing the latest upgrades and modifications are released regularly to provide you with the most optimized software available. We strongly recommend that you check the Cisco Connection Online World Wide Web URL http://www.cisco.com for the latest released software image.
This document consists of these sections:
The Catalyst 5000, 5002, and 5500 switches are Year 2000 compliant with the following supervisor engine software releases:
- Software releases 2.1(9) through 2.1(12)
- Software release 2.3(1) and later
The Catalyst 5505 and 5509, the Catalyst 2926G series, and the Catalyst 2926 series switches are Year 2000 compliant with all software releases in which these products are supported (for more information, see the "Product and Software Version Matrix" section).
The Catalyst 5000 series ATM LANE modules are Year 2000 compliant in ATM software release 3.1 and later.
The Catalyst 5000 series FDDI and CDDI modules are Year 2000 compliant in all software releases (all time related functions are in the supervisor engine software).
For more information on Cisco's Year 2000 compliance, visit this URL:
- http://www.cisco.com/warp/customer/752/2000/
Catalyst 5000 series software release 2.1 requires more memory than previous software releases. To use software release 2.1 you must have one of the following configurations:
- A single in-line memory module (SIMM) upgrade kit (product number is MEM-C5K-4M-V2) designed only for supervisor engine module hardware versions up to an including version 1.6X and hardware module revision numbers up to and including 73-1414-08, Revision A0.
- Supervisor engine module revision number 73-1414-09 or above. (Supervisor engine module revision numbers 73-1414-09 and above do not require this SIMM upgrade to run 2.1 software; they are preconfigured with the required SIMM.)
 | Caution
Catalyst 5000 series software release 2.1 fails to load without the proper memory configuration. Additionally, the single in-line memory module in the SIMM upgrade kit is a custom module that is not interchangeable with other SIMM modules. |
This section contains configuration matrixes to help you order Catalyst 5000 series products. Table 1 lists the minimum supervisor engine version and the current recommended/default supervisor engine version for Catalyst 5000 series modules and chassis.
Table 1: Product/Supervisor Engine Software Version Matrix
| Product Number
append with "=" for spares
| Product Description
| Minimum Supervisor Software Version
| Recommended/Default Supervisor Software Version
|
| Supervisor Engine I
|
WS-X5005
| Supervisor Engine I, dual-port 100BaseFX SMF1 uplinks
| 1.1
| 2.1(11) or 3.2(1b)
|
WS-X5006
| Supervisor Engine I, dual-port 100BaseFX MMF2 uplinks
|
WS-X5009
| Supervisor Engine I, dual-port 100BaseTX RJ-45/MII uplinks
|
| Supervisor Engine II
|
WS-X5505
| Supervisor Engine II, dual-port 100BaseFX SMF uplinks
| 2.2(1)
| 3.2(1b)
|
WS-X5506
| Supervisor Engine II, dual-port 100BaseFX MMF uplinks
|
WS-X5509
| Supervisor Engine II, dual-port 100BaseTX RJ-45/MII uplinks
|
| Supervisor Engine III FSX and FLX
|
WS-X5534-E1-GESX
| Supervisor Engine III FSX, dual-port 1000BaseSX uplinks
| 4.3(1)
| 4.3(1)
|
WS-X5536-E1-GELX
| Supervisor Engine III FLX, dual-port 1000BaseLX/LH uplinks
|
| Supervisor Engine III
|
WS-X5530-E1
| Supervisor Engine III Base Module
| 3.1(1)
| 4.2(1)
|
WS-X5530-E2
| Supervisor Engine III Base Module with NFFC3
| 4.1(1)
| 4.2(1)
|
WS-X5530-E3
| Supervisor Engine III base module with NFFC II
| 4.3(1)
| 4.3(1)
|
| Supervisor Engine III Uplink Modules
|
WS-U5531-FETX
| Dual-port 10/100BaseTX Fast Ethernet uplink module
| 3.1(1)
| 4.2(1)
|
WS-U5533-FEFX-MMF
| Dual-port 100BaseFX MMF Fast Ethernet uplink module
|
WS-U5535-FEFX-SMF
| Dual-port 100BaseFX SMF Fast Ethernet uplink module
|
WS-U5537-FETX
| 4-port 10/100BaseTX Fast EtherChannel uplink module
| 4.3(1)
| 4.3(1)
|
WS-U5534-GESX
| Dual-port 1000BaseSX Gigabit Ethernet uplink module
| 4.1(1)
| 4.2(1)
|
WS-U5534-GELX
| Dual-port 1000BaseLX/LH Gigabit Ethernet uplink module
|
| Supervisor Engine III Feature Cards
|
WS-F5521=
| NetFlow Feature Card (NFFC)
| 4.1(1)
| 4.2(1)
|
WS-F5531=
| NFFC II
| 4.3(1)
| 4.3(1)
|
| Ethernet, Fast Ethernet, and Gigabit Ethernet
|
WS-X5010
| 24-port 10BaseT Telco
| 1.1
| 2.1(11) or 3.2(3)
|
WS-X5011
| 12-port 10BaseFL Multimode ST
| 1.2
|
WS-X5012
| 48-port 10BaseT
| 2.4(1)
| 3.2(3)
|
WS-X5012A
| 48-port 10BaseT Telco
| 4.2(1)
| 4.2(1)
|
WS-X5013
| 24-port 10BaseT RJ-45
| 2.2(1)
| 3.2(3)
|
WS-X5014
| 48-port, 2-slot 10BaseT
| 4.2(1)
| 4.2(1)
|
WS-X5020
| 48-port, 4-segment 10BaseT Telco
| 2.1(1)
| 2.1(11) or 3.2(3)
|
WS-X5111
| 12-port 100BaseFX Multimode SC
| 1.4
|
WS-X5113
| 12-port 100BaseTX RJ-45
| 1.2
|
WS-X5114
| 6-port SM, 6-port Multimode 100BaseFX SC
| 2.1(5)
|
WS-X5201
| 12-port 100BaseFX Fast EtherChannel
| 2.3(1)
| 3.2(3)
|
WS-X5201R
| 12-port 100BaseFX Ethernet Module
| 4.1(2)
| 4.2(2)
|
WS-X5203
| 12-port 10/100BaseTX Fast EtherChannel
| 2.3(1)
| 3.2(3)
|
WS-X52134
| 12-port 10/100BaseTX RJ-45
| 1.5(4)
| 2.1(11) or 3.2(3)
|
WS-X5213A
| 12-port 10/100BaseTX RJ-45
| 2.1(7)5
|
WS-X5223
| 24-port, 3 segment 100BaseTX RJ-45
| 2.2(1)
| 3.2(3)
|
WS-X5224
| 24-port 10/100BaseTX RJ-45
| 2.4(2)
|
WS-X5225R
| 24-port 10/100BaseTX Ethernet Module
| 4.1(2)
| 4.2(2)
|
WS-X5403
| 3-port Gigabit Ethernet Module
| 4.1(1)
| 4.2(1)
|
WS-X5410
| 9-port, 2-slot Gigabit EtherChannel Module6
| 4.2(1)
| 4.2(1)
|
| Token Ring
|
WS-X5030
| 16-port Token Ring module, UTP/STP7, RJ-45
| 3.1(1)
| 4.2(1)
|
WS-X5031
| 16-port Token Ring module, Volition, VF-45
|
| FDDI/CDDI
|
WS-X5101
| 1 Dual-attach Multimode FDDI8 MIC
| 1.3
| 2.1(11) or 3.2(3)
|
WS-X5103
| 1 Dual-attach CDDI9 RJ-45
|
WS-X5104
| 1 Dual-attach Single-Mode FDDI ST
|
WS-X5105
| 1 Dual-attach Multimode FDDI SC
|
| ATM
|
WS-X51534
| 1-port OC-3 UTP RJ-45
| 1.4
| 2.1(11) or 3.2(3)
|
WS-X51544
| 1-port OC-3 Single-Mode SC
|
WS-X51554
| 1-port OC-3 Multimode SC
|
WS-X5156
| 1 Dual PHY OC-3 UTP RJ-45
| 2.1(5)
|
WS-X5157
| 1 Dual PHY OC-3 Single-Mode SC
|
WS-X5158
| 1 Dual PHY OC-3 Multimode SC
|
WS-X5161
| 1 Dual PHY OC-12 MMF SC, MPOA10/LANE11
| 3.2(1)
| 4.2(1)
|
WS-X5162
| 1 Dual PHY OC-12 SC, MPOA/LANE
|
WS-X5166
| 1 Dual PHY DS3, BNC connectors
| 3.1(1)
|
WS-X5167
| 1 Dual PHY OC-3 MMF SC, MPOA/LANE
| 3.2(1)
|
WS-X5168
| 1 Dual PHY OC-3 SMF SC, MPOA/LANE
|
| Route Switch Module
|
WS-X5302
| Route Switch Module
| 2.3(1)
| 3.2(3)
|
| Fabric Integration Module
|
WS-X5165
| ATM-fabric integration module
| 4.3(1)
| 4.3(1)
|
| Network Analysis Module
|
WS-X5380
| Network Analysis Module
| 4.3(1)
| 4.3(1)
|
| Modular Chassis
|
WS-C5000
| Catalyst 5000 chassis (5-slot)
| 1.1
| 2.1(11) or 3.2(3)
|
WS-C5002
| Catalyst 5002 chassis (2-slot)
| 2.2(1)
| 3.2(3)
|
WS-C5500
| Catalyst 5500 chassis (13-slot)
|
WS-C5505
| Catalyst 5505 chassis (5-slot)
| 2.3(1)
|
WS-C5509
| Catalyst 5509 chassis (9-slot)
| 4.2(1)
| 4.2(1)
|
| Fixed-Configuration Chassis
|
WS-C2901
| Catalyst 2900 with two 100BaseTX uplinks and 12 10/100BaseTX ports
| 2.1(1)
| 2.1(11) or 3.2(3)
|
WS-C2902
| Catalyst 2900 with two 100BaseTX uplinks and 12 10/100BaseFX ports
|
WS-C2926T
| Catalyst 2926 with two 100BaseTX uplinks and 24 10/100BaseTX ports
| 2.4(2)
| 3.2(3)
|
WS-C2926F
| Catalyst 2926 with two 100BaseFX uplinks and 24 10/100BaseTX ports
|
WS-C2926GS
| Catalyst 2926G with NFFC, two 1000BaseSX uplinks, and 24 10/100BaseTX ports
| 4.3(1)
| 4.3(1)
|
WS-C2926GL
| Catalyst 2926G with NFFC, two 1000BaseLX/LH uplinks, and 24 10/100BaseTX ports
|
1SMF=single-mode fiber
2MMF=multimode fiber
3NFFC=NetFlow Feature Card
4The WS-X5213, WS-X5153, WS-X5154, and WS-X5155 modules have been moved to end-of-life (EOL) status.
5Software releases 1.5(6) and 2.1(502) also support the WS-X5213A module.
6The Gigabit EtherChannel module (WS-X5410) is supported only in a Catalyst 5505, 5509, or 5500 chassis with a Supervisor Engine III, III FSX, or III FLX module. Supervisor Engines I and II, and the Catalyst 5000 chassis, have not yet been tested and approved for use with this module.
7UTP/STP=unshielded twisted-pair/shielded twisted-pair
8FDDI=Fiber Distributed Data Interface
9CDDI=Copper Distributed Data Interface
10MPOA=Multiprotocol over ATM
11LANE=LAN Emulation
|
Table 2 lists the software versions and applicable ordering information for the Catalyst 5000 series supervisor engine software.
Table 2: Software Version/Orderable Product Number Matrix
| Software Version
| Filename
| Orderable Product Number
Flash on System
| Orderable Product Number
Spare Upgrade (Floppy Media)
|
| Supervisor I and II
|
2.1(8)
| cat5000-sup.2-1-8.bin
| SFC5K-SUP-2.1.8
| SWC5K-SUP-2.1.8=
|
2.1(9)
| cat5000-sup.2-1-9.bin
| SFC5K-SUP-2.1.9
| SWC5K-SUP-2.1.9=
|
2.1(10)
| cat5000-sup.2-1-10.bin
| SFC5K-SUP-2.1.10
| SWC5K-SUP-2.1.10=
|
2.1(11)1
| cat5000-sup.2-1-11.bin
| SFC5K-SUP-2.1.11
| SWC5K-SUP-2.1.11=
|
2.1(12)
| cat5000-sup.2-1-12.bin
| SFC5K-SUP-2.1.12
| SWC5K-SUP-2.1.12=
|
2.2(2)
| cat5000-sup.2-2-2.bin
| SFC5K-SUP-2.2.2
| SWC5K-SUP-2.2.2=
|
2.3(1)
| cat5000-sup.2-3-1.bin
| SFC5K-SUP-2.3.1
| SWC5K-SUP-2.3.1=
|
2.4(3)2
| cat5000-sup.2-4-3.bin
| SFC5K-SUP-2.4.3
| SWC5K-SUP-2.4.3=
|
2.4(4)
| cat5000-sup.2-4-4.bin
| SFC5K-SUP-2.4.4
| SWC5K-SUP-2.4.4=
|
2.4(5)
| cat5000-sup.2-4-5.bin
| SFC5K-SUP-2.4.5
| SWC5K-SUP-2.4.5=
|
| Supervisor I (8 MB)
|
3.1(1)
| cat5000-sup8m.3-1-1.bin
| N/A
| SWC5K-SUP-3.1.1=
|
3.1(2a)
| cat5000-sup8m.3-1-2a.bin
| N/A
| SWC5K-SUP-3.1.2=
|
3.2(1b)
| cat5000-sup8m.3-2-1b.bin
| N/A
| SWC5K-SUP-3.2.1=
|
3.2(2)
| cat5000-sup8m.3-2-2.bin
| N/A
| N/A
|
3.2(3)
| cat5000-sup8m.3-2-3.bin
| N/A
| N/A
|
| Supervisor I and II (16 MB minimum)
|
3.1(1)
| cat5000-sup.3-1-1.bin
| SFC5K-SUP-3.1.1
| SWC5K-SUP-3.1.1=
|
3.1(2a)
| cat5000-sup.3-1-2a.bin
| SFC5K-SUP-3.1.2
| SWC5K-SUP-3.1.2=
|
3.2(1b)
| cat5000-sup.3-2-1b.bin
| SFC5K-SUP-3.2.1
| SWC5K-SUP-3.2.1=
|
3.2(2)
| cat5000-sup.3-2-2.bin
| N/A
| N/A
|
3.2(3)
| cat5000-sup.3-2-3.bin
| SFC5K-SUP-3.2.3
| SWC5K-SUP-3.2.3=
|
3.2(4)
| cat5000-sup.3-2-4.bin
| SFC5K-SUP-3.2.4
| SWC5K-SUP-3.2.4=
|
4.1(2)
| cat5000-sup.4-1-2.bin
| SFC5K-SUP-4.1.2
| SWC5K-SUP-4.1.2=
|
4.1(3)
| cat5000-sup.4-1-3.bin
| SFC5K-SUP-4.1.3
| SWC5K-SUP-4.1.3=
|
4.2(1)
| cat5000-sup.4-2-1.bin
| SFC5K-SUP-4.2.1
| SWC5K-SUP-4.2.1=
|
4.2(2)
| cat5000-sup.4-2-2.bin
| SFC5K-SUP-4.2.2
| SWC5K-SUP-4.2.2=
|
4.3(1a)
| cat5000-sup.4-3-1a.bin
| SFC5K-SUP-4.3.1
| SWC5K-SUP-4.3.1=
|
| Supervisor III, III FSX, III FLX
|
3.1(1)
| cat5000-sup3.3-1-1.bin
| N/A
| N/A
|
3.1(2a)
| cat5000-sup3.3-1-2a.bin
| N/A
| N/A
|
3.2(1b)
| cat5000-sup3.3-2-1b.bin
| N/A
| N/A
|
3.2(2)
| cat5000-sup3.3-2-2.bin
| N/A
| N/A
|
3.2(3)
| cat5000-sup3.3-2-3.bin
| SFC5K-SUP3-3.2.3
| SWC5K-SUP-3.2.3=
|
3.2(4)
| cat5000-sup3.3-2-4.bin
| SFC5K-SUP3-3.2.4
| SWC5K-SUP-3.2.4=
|
4.1(2)
| cat5000-sup3.4-1-2.bin
| N/A
| N/A
|
4.1(3)
| cat5000-sup3.4-1-3.bin
| N/A
| N/A
|
4.2(1)
| cat5000-sup3.4-2-1.bin
| SFC5K-SUP3-4.2.1
| SWC5K-SUP-4.2.1=
|
4.2(2)
| cat5000-sup3.4-2-2.bin
| SFC5K-SUP3-4.2.2
| SWC5K-SUP-4.2.2=
|
4.3(1a)
| cat5000-sup3.4-3-1a.bin
| SFC5K-SUP3-4.3.1
| SWC5K-SUP-4.3.1=
|
1Default version for Catalyst 5000 switches only
2Default version for Catalyst 5002 and Catalyst 5500 switches only
|
The Catalyst 5000 Series Supervisor Engine Module Software Release 2.1(501) supports the simultaneous operation of both the WS-X5213 and WS-X5213A 10/100-Mbps Fast Ethernet 12-port switching modules. The new WS-X5213A module reflects a minor component change only and does not reflect a change in the features, functions, or form of this product. There are no restrictions on how these two modules can be combined within a single system.
This section lists the Catalyst 5000 series software release 2.1 new features. Refer to the Catalyst 5000 Series Installation Guide and Catalyst 5000 Series Configuration Guide and Command Reference publications for implementation instructions.
- Catalyst 5000 Network Management Processor (NMP) IP address mobilityIn previous software releases, IP address of a Catalyst 5000 series switch NMP was restricted to VLAN 1 only; the IP address can now be assigned to any VLAN. Only one IP address can be assigned to a Catalyst 5000 series switch; therefore, if the IP address is reassigned to a different VLAN, the previous IP address assignment to a VLAN is no longer valid.
- Dynamic Inter-Switch Link (DISL) ProtocolDISL Protocol dynamically configures trunk ports between Catalyst 5000 series switches. This protocol synchronizes the configuration of two interconnected Fast Ethernet interfaces into an ISL trunk or non-trunk. DISL Protocol minimizes VLAN trunk configuration procedures because only one end of a link needs to be configured as a trunk or non-trunk.
- Load sharingCatalyst 5000 series software release 2.1 supports load sharing, allowing VLAN traffic on parallel trunks to be split between multiple trunks. By setting Spanning Tree Protocol (STP) port VLAN priority parameters on a VLAN basis, you can define which VLANs have priority access to a trunk and which are to use the trunk as a backup when another trunk fails.
- Spanning Tree Protocol (STP) portfastYou can configure ports to immediately enter STP forwarding mode when a connection is made, instead of the usual sequence of blocking, listening, learning, and then forwarding. Portfast mode is useful in situations where immediate access to a server is required, but should be used by individual workstations ports only; it is not recommended for ports connected to switches or other devices that forward packets.
- VLAN Trunk Protocol (VTP)Catalyst 5000 series software release 2.1 supports VLAN Trunk Protocol (VTP). When new VLANs are added to a Catalyst 5000 series switch in a management domain, VTP automatically propagates the VLAN configuration information on all trunks to other devices in the same management domain. This allows both VLAN consistency and connectivity between all devices in the domain. VTP packets are propagated on all trunk connections, including inter-switch link (ISL), ATM LAN emulation (LANE), and 802.10 protocol.
- TelnetCatalyst 5000 series software release 2.1 provides outgoing Telnet functionality from the command line interface; this feature allows a network manager to use Telnet from the command line interface of the switch to access other devices on the network.
- Embedded Remote Monitoring (RMON)Catalyst 5000 series software release 2.1 provides support for RMON of Ethernet and Fast Ethernet ports. Embedded RMON provides you with visibility into network activity. It enables you to access and remotely monitor the RMON specification RFC 1757 groupings of statistics, historical information, alarms, and events for any Ethernet port through Cisco's TrafficDirector Management application or any other RMON application.
- Enhanced switched port analyzer (SPAN)SPAN enables you to monitor traffic on any port for analysis by a sniffer or RMON probe. It also enables you to monitor traffic from a VLAN (multiple ports) to a port for analysis. The SPAN redirects traffic from an Ethernet, Fast Ethernet, or FDDI port or VLAN to an Ethernet or Fast Ethernet monitor port for detailed analysis and troubleshooting. You can monitor a single port or VLAN using a dedicated analyzer, such as a Network General Sniffer, or a remote monitoring (RMON) probe, such as a Cisco SwitchProbe.
- Ethernet Group Switching ModuleCatalyst 5000 series software release 2.1 provides support for the Ethernet Group Switching module (10BaseT 48 port), which provides connection to 48 10-Mbps (10BaseT) Ethernet ports in four switched segments of 12 ports each. The Ethernet Group Switching Module has four Telco RJ-21 connectors on the front panel (12 ports per connector).
The following features are available with Catalyst 5000 series FDDI software release 2.1 and above only.
- 802.10 protocol on FDDICatalyst 5000 series software release 2.1 multiplexes multiple VLANs between switches and routers using 802.10 protocol on FDDI.
- Rejecting MAC address learning (fddicheck)An FDDI interface can reject the learning of MAC addresses that it previously learned from an Ethernet interface using the fddicheck user-configurable option. This feature prevents FDDI modules from incorrectly learning MAC addresses when the following two conditions simultaneously exist:
- Spurious VOID frames are present on the FDDI ring
- The MAC addresses have previously been learned by Ethernet interfaces
- Disabling Automatic Packet Recognition and Translation (APART)To increase throughput performance, you can disable the software content-addressable memory (CAM) of the FDDI module. The CAM stores Internet packet exchange (IPX) translation information to support automatic packet recognition and translation (APART). The Catalyst 5000 EARL CAM continues to provide packet forwarding functionality after APART is disabled using default IPX translations. Note that there are some drawbacks to disabling the FDDI software CAM, as described in the chapter "Defining the Catalyst 5000 Series Switch" of the Catalyst 5000 Series Installation Guide.
Note For a description of caveats in software release 2.1(12), see the "Caveats in Software Release 2.1(12)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(11) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(12).
- When an FDDI port is in blocking mode and both FDDI ports (A and B) are connected, if one FDDI port is disabled, traffic might be forwarded across the other FDDI port, causing network instability. This problem is fixed in software release 2.1(12). (CSCdj72892)
- Under certain PC configurations, the PC might not be unable to connect to an IPX server. This problem is fixed in software release 2.1(12). (CSCdj68668)
- With newer versions of the Netcom AST application, you might experience high packet loss while running the X-treme test. (See the Netcom Systems World Wide Web page for details on the differences in AST software versions.) This problem is fixed in software release 2.1(12). (CSCdk00502)
- In a Catalyst 5000 series switch with redundant Supervisor Engine II modules, transmit traffic from the active supervisor might be interrupted after repeated switchovers between the supervisors. This problem is fixed in software release 2.1(12). (CSCdj77367)
Note For a description of caveats in software release 2.1(11), see the "Caveats in Software Release 2.1(11)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(10) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(11).
- The ATM module on a Catalyst 5000 series switch transmits packets on the wrong virtual connection (VC). This problem is fixed in Catalyst 5000 series supervisor engine software release 2.1(11) and Catalyst 5000 ATM module software release 3.2(6). (CSCdj48920)
- In a Catalyst 5000 series switch, if spanning tree is disabled and the link to an ATM module goes down or the ATM module is reset, all the entries in the CAM pointing to that ATM module are not cleared and never time out. This problem is fixed in software release 2.1(11). (CSCdj56995)
- Catalyst 5000 series switches were vulnerable to the LAND.C Denial of Service Attack program. This problem is fixed in software release 2.1(11). (CSCdj62723)
- Under heavy traffic conditions and with an unreliable physical connection, port(s) on the 10BaseFL Ethernet switching module (WS-X5011) might become disabled and might be unable to forward traffic. This problem is fixed in software release 2.1(11). (CSCdj55124)
- The set cam permanent command is not additive. This problem is fixed in software release 2.1(11). (CSCdj61870)
Note For a description of caveats in software release 2.1(10), see the "Caveats in Software Release 2.1(10)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(9) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(10).
- In some cases, a Switched Port Analyzer (SPAN) destination port receives traffic from a previously configured VLAN as well as traffic from the currently configured VLAN. This problem is fixed in software release 2.1(10). (CSCdj25517)
- If all switches in a VTP domain do not have identical VTP passwords, excessive VTP messages might be generated. This problem is fixed in software release 2.1(10). (CSCdj37167)
- In some cases, ATM-related CAM entries are missing from the bridge table. This problem is fixed in software release 2.1(10). (CSCdj47859)
- In some cases, the Catalyst 5000 series software might display misleading error messages if a defective switching module is detected during the boot process. This problem is fixed in software release 2.1(10). (CSCdj39557)
Note For a description of caveats in software release 2.1(9), see the "Caveats in Software Release 2.1(9)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(8) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(9).
- In some cases, issuing the set port enable | disable command to the Group Switching Ethernet module (WS-X5020) did not enable/disable the ports. This problem is fixed in software release 2.1(9). (CSCdj15935)
- In rare cases, after frequent topology changes in a configuration that includes ATM modules, the Catalyst 5000 series switch might experience a reset. This problem is fixed in software release 2.1(9). (CSCdj14380)
- ARP entries in the Catalyst 5000 series switch are not aged out when the ARP aging time is set to a value of 300 or higher, including the default value of 1200. This problem is fixed in software release 2.1(9). (CSCdj12715)
- In some cases, if you attempt to monitor a VLAN using the SPAN and the VLAN only has trunk ports, the destination port might become faulty or disabled. This problem is fixed in software release 2.1(9). (CSCdj19747)
- In some cases, the SPAN destination port cannot be set to trunking mode even after disabling spanning tree. This problem is fixed in software release 2.1(9). (CSCdj21848)
- In some cases, when hosts are disconnected from a Group Switching Ethernet module (WS-X5020), CAM entries are not purged immediately from the module. This problem is fixed in software release 2.1(9). (CSCdj25923)
- In some cases, in the presence of an external FDDI-to-Ethernet translating bridge, certain packets received by an FDDI module might cause the FDDI port spanning-tree state to change continuously. This problem is fixed in software release 2.1(9). (CSCdj26896)
Note For a description of caveats in software release 2.1(8), see the "Caveats in Software Release 2.1(8)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(7) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(8).
- The Catalyst 5000 series switch might experience a reset when you repeatedly open and immediately close Telnet sessions. This problem has been fixed in software release 2.1(8). (CSCdi92608)
- Under certain conditions, the CAM table will not clear entries for five minutes after a port has been disconnected. This problem has been fixed in software release 2.1(8). (CSCdj00074)
- After downloading FDDI software, the Catalyst 5000 series switch might become disabled, or further software downloads might fail. This problem has been fixed in software release 2.1(8). (CSCdj01346)
- After being disabled and then reenabled, the WS-X5223 module might stop receiving packets. This problem has been fixed in software release 2.1(8). (CSCdi91966)
- In some instances when trying to establish a connection to an ATM module over Telnet, an exception might occur. This problem has been fixed in software release 2.1(8). (CSCdj00035)
- Opening a Telnet session from a Catalyst 5000 series switch to a Sun Solaris machine might cause the session to hang. This problem has been fixed in software release 2.1(8). (CSCdi92006)
- In some instances, the MII port monitor test might fail. This problem has been fixed in software release 2.1(8). (CSCdj08145)
- In some instances, an SNMP walk of the bridge MIB will repeatedly loop though the same set of objects. This problem is fixed in software release 2.1(8). (CSCdj04822)
- In some instances when the Catalyst 5000 series contains FDDI modules, the bridge MIB might return the wrong port value for some MAC addresses. This problem is fixed in software release 2.1(8). (CSCdj04820)
- If you repeatedly exit a Telnet session while the system is displaying a --More-- prompt, the system might eventually crash. This problem is fixed in software release 2.1(8). (CSCdj14053)
- Catalyst 5000 series software releases 2.1(6), 2.1(7), and 2.2(1) did not support IMC external MII transceivers. This problem is fixed in software release 2.1(8). (CSCdj13639)
- In some instances, the set spantree portfast command might not work properly when applied only to the second segment (ports 13-24) of a Catalyst 5000 series switching module. This problem is fixed in software release 2.1(8). (CSCdj13046)
- Under certain conditions, while the Catalyst 5000 series switch continues to switch traffic, console, IP processes, and Spanning-Tree Protocol might appear to be hung. This problem has been fixed in software release 2.1(8). (CSCdi91949)
- In certain cases when using the WS-X5010 module, if a port is disabled either manually or by the port security feature while it is switching traffic, the module might freeze and stop responding to system commands. This problem is fixed in software release 2.1(8). (CSCdj16744)
Note For a description of caveats in software release 2.1(7), see the "Caveats in Software Release 2.1(7)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(6) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(7).
- If you continuously open and close Telnet sessions into a Catalyst 5000 series switch and enter ATM commands during the sessions, some memory might be lost each time and, eventually, the system might run out of memory. (CSCdi92171)
- If a Telnet session to the Catalyst 5000 series switch is terminated abnormally during a Trivial File Transfer Protocol (TFTP) operation, the TFTP flag is not cleared and the user cannot issue write, copy, or reset commands. (CSCdi90472)
- TFTP errors might occur when using an ATM port to upload/download configuration data to and from the supervisor engine module. (CSCdi74908)
- The Catalyst 5000 series switch might experience a reset when you use an out-of-range VLAN number with the show vlan command. (CSCdi91936)
- The Catalyst 5000 series switch might experience an exception if you enter the show fddi or the set fddi command with a large value (for example, show fddi 1111111111111111111). (CSCdi91999)
- In some instances during power up, a port that uses an MII transceiver might fail the power-up diagnostics. (CSCdi90359)
- In certain configurations, a cable-length problem might cause the autonegotiation feature to fail on the WS-X5213A 10/100-Mbps Fast Ethernet module (10/100Base TX, 12 Port). (CSCdi91789)
- The show version command displays version number 514.1 for 2.2(1) boot firmware. (CSCdj01716)
- When accessing the Catalyst 5000 series switch over Telnet, entering any show command that produces lengthy output (such as show port) while continuously pressing the Return key might cause the Catalyst 5000 series switch to reset. (CSCdj04254)
- The permanent CAM entry assigned to an FDDI module in the Catalyst 5000 series switch is lost after a reset or power cycle. (CSCdj03882)
- Under certain conditions, if you open a Telnet session to a Catalyst 5000 series switch and then break the Telnet session, the switch might reset. (CSCdj04792)
- If a Telnet session to the Catalyst 5000 series switch is terminated abnormally during the execution of a write terminal command, the TFTP flag is not cleared and the user cannot issue write, copy, or reset commands. To recover, power-cycle the switch. (CSCdi90472)
- Under certain conditions, the physical link between a trunking supervisor port and a port on the WS-X5213A 10/100-Mbps Fast Ethernet module toggles continuously. (CSCdj03973)
Note For a description of caveats in software release 2.1(6), see the "Caveats in Software Release 2.1(6)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(5) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(6).
- When you configure specific VLANs on a trunk using first the clear trunk command and then the set trunk vlan command, the clear trunk command is not copied to the TFTP server when the configuration is stored. When the configuration is then copied back to a Catalyst 5000 series switch with the default trunk configuration, all the active VLANs are allowed on all of the defined trunks. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi75581)
- The Catalyst 5000 series switch might experience a reset when the wake-up counter increments to a very large value (billions). This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi72732)
- If a port is moved dynamically from one VLAN to another, the port becomes disconnected until you disable and reenable the port using the set port command. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70234)
- In a dual-attach FDDI configuration, disabling one port on a Catalyst 5000 series switch also disables the second port on the switch. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70986)
- If you enter the set span disable command for a port that already has SPAN disabled, the port becomes inoperable until you disable and reenable the port using the set port command. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi72352)
- After a change in the spanning-tree topology, CAM entries are not aged out in 15 seconds. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi72671)
- Changing the spanning-tree priority value simultaneously on multiple VLANs can slow the convergence of spanning tree. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi74383)
- The Catalyst 5000 series switch always returns a value of 0 when executing a query for the snmpOutPkts object. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi74517)
- The Catalyst 5000 series switch might experience a reset when you configure up to 50 trunks. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi73777)
- Under some conditions, a problem with redundant-trunking configurations might cause the Catalyst 5000 series switch to experience a reset. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi72376)
- The Catalyst 5000 series switch might experience an exception while configuring and attaching a Frontier/Cisco Remote Monitoring (RMON) probe to a SPAN port. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi74310)
- When using the VlanDirector application, the Catalyst 5000 series switch might experience an exception when executing an SNMP query for VLAN/Bridge status. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi74310)
- In a redundant Ethernet topology, an unstable physical link can create a broadcast storm. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi75418)
- After the Catalyst 5000 series switch is reset, network control program (NCP) messages are not sent at the proper time, preventing the RMON configuration from being reinstalled properly. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi76088)
- Undersized packets with good cyclic redundancy checks (CRCs) are not represented in the output of the show port and show mac commands. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi76063)
- If SPAN is disabled on a Catalyst 5000 series switch and you issue a write network command to save the configuration, both the set span enable and set span disable commands are present in the configuration file. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi75955)
- The output of the show port command displays a dash rather than a value under the heading for Giants. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi75302)
- On a Catalyst 5000 series switch configured with multiple trunking ports, adding additional trunking ports causes a previously configured trunking port to become a nontrunk port. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70629)
- If you have two power supplies in a Catalyst 5000 series switch and one is inactive, a system reset causes the supervisor ports to fail to transmit until you disable and reenable the ports using the set port command. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi69090 and CSCdi70411)
- There is a typographical error in the MIB ifTable entry interfaces.ifTable.ifEntry.ifDescr.297. The entry shows
multi mode filber fddi instead of multi mode fiber fddi. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi71508)
- The Catalyst 5000 series switch cannot detect and recover when the switching bus locks up. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi71386)
- An attempt to disable a nonexistent Catalyst 5000 series module can be mistaken as an attempt to disable the supervisor engine module, causing the Catalyst 5000 series switch to fail. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi69169)
- The configuration file does not accept tab characters as word delimiters. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi72439)
- There is a typographical error in the output of the show help command. The output for the show span command displays
Show switch port analyzer informatio instead of Show switch port analyzer information. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi69177)
- The show config command displays incorrect values for spantree portcost and spantree portvlanpri. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70213)
- Under certain conditions, the show port command shows that a port is inactive while the show trunk command shows that same port to be trunking. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi69351)
- The show cdp neighbors detail command displays AppleTalk addresses in hexadecimal rather than decimal. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi69550)
- If the status of the supervisor engine module is reported as faulty, the port and Spanning-Tree Protocol states can become inconsistent. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70411)
- Using the show port command, you cannot remotely determine if an RJ-45/MII connector is used on the supervisor engine module. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70584)
- The SNMP agent does not report the correct module status for the supervisor LED. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi71159)
- In some instances, the IPG value was out-of-sync on some Catalyst 5000 series line cards. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70631)
- When adding a VLAN through SNMP in VTP transparent mode, the mode changes to VTP server mode. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi70932)
- In a redundant topology consisting of two Catalyst 5000 series switches configured in VTP transparent mode and a third Catalyst 5000 series switch configured in VTP server mode, VTP packets will loop indefinitely. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi71426)
- On a Catalyst 5000 series switch with the CAM aging time set to 0, an SNMP query could produce a reset. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi81669)
- Under certain conditions during a broadcast storm, the Catalyst 5000 series switch might not recover. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi66330)
- Performance problems occur when the Catalyst 5000 series switch is used for InterVLAN bridging on an AppleTalk network. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi77241)
- When a flash-erase download process is in progress over a Telnet session, closing the Telnet session can interrupt the download before it is completed and terminate the Telnet session. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi81995)
- The Catalyst 5000 series switch accepts service data unit (SDU) sizes other than 1516 in the setup message, despite the fact that the LANE specification states that SDU sizes other than 1516 should be rejected. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi73155)
- When you execute the show log command, the traffic high switch count is higher than the reset count. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi79015)
- When you have an MII transceiver connected to the supervisor module and you initiate a hard reset, once the Catalyst 5000 series switch comes back up the show test command reports a PMD loopback failure even though the link is up. If you then initiate a soft reset, PMD loopback passes. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi79025)
- Under some conditions, ports on the WS-X5020 segmenting switch module show a level status of "other." This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi80585)
- While disabled, the FDDI module still becomes a trunk. This problem is fixed in the Catalyst 5000 series supervisor engine module software release 2.1(6). (CSCdi81466)
Note For a description of caveats in software release 2.1(5), see the "Caveats in Software Release 2.1(5)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1(4) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(5).
- When you remove or hot swap an ATM module while the system is operating, the slot and virtual circuit number in the CAM table become invalid. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi42681)
- You cannot use the session command for an ATM card if the supervisor engine module IP address is not set (that is, if the supervisor engine module IP address is set to 0.0.0.0). This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi44641)
- The command clear cam dyn mac_addr deletes a MAC address from the supervisor engine module CAM but not from the FDDI module CAM. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi60839)
- The command set trunk does not support ATM modules. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi62362)
- The Catalyst 5000 series switch does not recognize the ATM Dual PHY module. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi63180)
- When there are continuous spanning-tree topology changes under heavy traffic conditions, a Catalyst 5000 series switch might remain accessible through ping and telnet but stop responding to SNMP requests. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi64759)
- The Catalyst 5000 series switch allows you to add ports to a VLAN with the type FDDI. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi65189)
- ATM ports cannot be set as a destination port for a static multicast entry. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi66054)
- If you connect a 2511 communication server to a Catalyst 5000 console, the Catalyst 5000 series switch might reset. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi66347)
- The Catalyst 5000 series switch reports single and multiple collisions as part of ifOutErrors. This problem has been corrected in Catalyst 5000 series switch series supervisor engine module software release 2.1(5). (CSCdi66677)
- If a Catalyst 5000 series switch has a permanent multicast entry in its CAM table, some modules might not come online when the switch is powered up. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi66772)
- When FDDI trunking is enabled, an FDDI port cannot be moved to an Ethernet VLAN that has a defined translation. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi67228)
- The rptrMonitorPortReadableFrames MIB object is not supported. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(5). (CSCdi67765)
- If you delete a a static multicast entry that is pointing to both Ethernet ports and an ATM port, the entry is deleted only from the Ethernet ports. In Catalyst 5000 series supervisor engine module software release 2.1(5), this problem has been corrected. (CSCdi68243)
In some instances, when using the autonegotiating functions of either the WS-X5213 or WS-X5213A 10/100-Mbps Fast Ethernet 12-port switching modules to connect to another autonegotiating Ethernet or Fast Ethernet device over a cable distance of 98 to 131 feet (30 to 40 meters), the duplex mode and port speed may be incorrectly negotiated. In this case, the link between the devices cannot be established and the port speed and duplex mode has to be set manually before the link can be established. This problem is corrected in software release 2.1(502).
Note For a description of caveats in software release 2.1(3), see the "Caveats in Software Release 2.1(3)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1 and 2.1(2) caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(3).
- The Catalyst 5000 series switch might report alignment errors on the receiving side of supervisor MII ports that are configured as trunks. In Catalyst 5000 series supervisor engine module software release 2.1(3), this problem has been corrected. (CSCdi54628)
- When an LEC on an ATM module continuously goes up and down, a memory leak might occur. This leak can cause the Catalyst 5000 series switch to run out of memory buffers and stop responding to ping, telnet, or SNMP requests. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(3). (CSCdi61865)
- Under certain conditions, the session command to an ATM card becomes inoperable. In Catalyst 5000 series supervisor engine module software release 2.1(3), this problem has been corrected. (CSCdi62970)
- If you configure MII ports for trunking when MII transceivers are present, under heavy traffic conditions the trunking status of the ports might toggle between trunking and nontrunking. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(3). (CSCdi64353)
- FDDI modules might not come online after you upgrade to Catalyst 5000 series FDDI software release 2.1(2). To bring the FDDI module online, reset the FDDI module using the reset mod_num command. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(3). (CSCdi64572)
- The Catalyst 5000 series switch will first attempt to autonegotiate port speed, even if the speed of a 10/100 Mbps Fast Ethernet Switching module port is set to 10 Mbps or 100 Mbps. This might prevent a link from being made to some end stations. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(3). (CSCdi65030)
- Using the fiber supervisor engine module under extremely heavy traffic conditions, the system might experience a switching bus timeout and subsequently crash. In Catalyst 5000 series supervisor engine module software release 2.1(3), this problem has been corrected. (CSCdi65055)
- If a FDDI module is present in a Catalyst 5000 series switch chassis and all the ports of two adjacent modules are configured to be in a VLAN other than 1, some modules in the chassis might not come online after a switch power-up. In Catalyst 5000 series supervisor engine module software release 2.1(3), this problem has been corrected. (CSCdi65472)
- If you use the command set span to dynamically change the source port of a SPAN configuration from one port to another, the Catalyst 5000 series switch still "spans" the traffic from the previous source port. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(3). (CSCdi65620)
Note For a description of caveats in software release 2.1(2), see the "Caveats in Software Release 2.1(2)" section.
This section describes the Catalyst 5000 series supervisor engine module software release 2.1 caveats that were resolved in Catalyst 5000 series supervisor engine module software release 2.1(2).
- When you enable or disable FDDI ports on an FDDI module, the set port enable and set port disable commands for both ports 1 and 2port A (port 1) and port B (port 2) on the FDDI moduleare treated as two different ports. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(2). (CSCdi57956)
- A Catalyst 5000 series switch might time out if several SNMP applications are running concurrently. Limit the number of SNMP applications to one at a time. Alternatively, increase the timeout value for manager applications. In Catalyst 5000 series supervisor engine module software release 2.1(2), this problem has been corrected. (CSCdi58669)
- When you view the etherStats for an Ethernet port using an RMON application such as TrafficDirector, the Catalyst 5000 series switch reports oversize frames even though oversize packets have not been received on the port. Ignore messages of this type and continue normal operation. This problem is fixed in Catalyst 5000 series supervisor engine module software release 2.1(2). (CSCdi59442)
Note For a description of caveats fixed in software release 2.1(12), see the "Differences Between Software Releases 2.1(11) and 2.1(12)" section.
There are no known caveats for the Catalyst 5000 series supervisor engine module software release 2.1(12).
Note For a description of caveats fixed in software release 2.1(11), see the "Differences Between Software Releases 2.1(10) and 2.1(11)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(11). The caveats listed here describe only serious problems.
When an FDDI port is in blocking mode and both FDDI ports (A and B) are connected, if one FDDI port is disabled, traffic might be forwarded across the other FDDI port, causing network instability. As a workaround, disable both FDDI ports (A and B) at the same time. (CSCdj72892)
Note For a description of caveats fixed in software release 2.1(10), see the "Differences Between Software Releases 2.1(9) and 2.1(10)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(10). The caveats listed here describe only serious problems.
- The ATM module on a Catalyst 5000 series switch transmits packets on the wrong virtual circuit (VC). (CSCdj48920)
- In a Catalyst 5000 series switch, if spanning tree is disabled and the link to an ATM module goes down or the ATM module is reset, all the entries in the CAM pointing to that ATM module are not cleared and will never time out. (CSCdj56995)
- Catalyst 5000 series switches are vulnerable to the LAND.C Denial of Service Attack program. (CSCdj62723)
- Under heavy traffic conditions and with an unreliable physical connection, port(s) on the 10BaseFL Ethernet switching module (WS-X5011) might become disabled and unable to forward traffic. (CSCdj55124)
- The set cam permanent command is not additive. (CSCdj61870)
Note For a description of caveats fixed in software release 2.1(9), see the "Differences Between Software Releases 2.1(8) and 2.1(9)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(9). The caveats listed here describe only serious problems.
- In some cases, a SPAN destination port receives traffic from a previously configured VLAN as well as traffic from the currently configured VLAN. To recover, use the set span command to monitor transmit traffic, or both transmit and receive traffic, on the previously configured VLAN. (CSCdj25517)
- If all switches in a VTP domain do not have identical VTP passwords, excessive VTP messages might be generated. (CSCdj37167)
Note For a description of caveats fixed in software release 2.1(8), see the "Differences Between Software Releases 2.1(7) and 2.1(8)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(8). The caveats listed here describe only serious problems.
- In some instances, the Catalyst 5000 series switch does not age out ARP entries correctly if aging is set to greater than 300 seconds. (CSCdj12715)
- If the Switch Port Analyzer (SPAN) function of a Catalyst 5000 series switch is enabled with port x/y as the destination and the SPAN function is disabled, or a different destination port is specified with the set span command, port x/y might stop sending and receiving traffic. To recover, disable and then reenable the port using the set port command. (CSCdj15003)
- In some instances, the CAM table in the Catalyst 5000 series switch is learning MAC addresses from ports that are blocked by the Spanning-Tree Protocol. To recover, disable Cisco Discovery Protocol (CDP) on the device that is connected to the blocked ports. (CSCdi91812)
Note For a description of caveats fixed in software release 2.1(7), see the "Differences Between Software Releases 2.1(6) and 2.1(7)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(7). The caveats listed here describe only serious problems.
- The Catalyst 5000 series switch might experience a reset when you repeatedly open and immediately close Telnet sessions. (CSCdi92608)
- If you disable a port on a WS-X5020 Group Switching Ethernet Module and then reset the Catalyst 5000 series switch, you cannot reenable the previously disabled ports. To recover, enter the clear config mod_num command, where mod_num is the WS-X5020 module number. (CSCdi90797)
- In some instances, the CAM table in the Catalyst 5000 series switch is learning MAC addresses from ports that are blocked by the Spanning-Tree Protocol. To recover, disable Cisco Discovery Protocol (CDP) on the device that is connected to the blocked ports. (CSCdi91812)
- If you open a Telnet session to a Catalyst 5000 series switch that is running low on memory, the switch might reset. (CSCdj02060)
- Under certain conditions, the CAM table will not clear entries for five minutes after a port has been disconnected. To recover, lower the CAM aging time to five seconds. (CSCdj00074)
- After downloading FDDI software to the Catalyst 5000 series switch, the TFTP flag might not reset. This error causes the tftp session to hang, preventing both further software downloads and resets of the switch. (CSCdj01346)
Note For a description of caveats fixed in software release 2.1(6), see the "Differences Between Software Releases 2.1(5) and 2.1(6)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(6). The caveats listed here describe only serious problems.
- The Catalyst 5000 series switch might experience a reset when you repeatedly open and immediately close Telnet sessions. (CSCdi92608)
- If a Telnet session to the Catalyst 5000 series switch is terminated abnormally during the execution of a write terminal command, the TFTP flag is not cleared and you cannot issue write, copy, or reset commands. To recover, power-cycle the switch. (CSCdi90472)
- If you disable a port on a WS-X5020 Group Switching Ethernet Module and then reset the Catalyst 5000 series switch, you cannot reenable the previously disabled ports. To recover, enter the clear config mod_num command, where mod_num is the WS-X5020 module number. (CSCdi90797)
- In some instances, the CAM table in the Catalyst 5000 series switch is learning MAC addresses from ports that are blocked by the Spanning-Tree Protocol. To recover, disable CDP on the device that is connected to the blocked ports. (CSCdi91812)
- In some instances, opening a Telnet session from a Catalyst 5000 series switch to a remote device that does not respond causes the console port on the Catalyst 5000 series switch to lock up. To recover, enter Ctrl-C or the following command sequence: (CSCdi92006)
Ctrl-]
telnet> send escape
telnet> quit
Console > (enable)
- If you receive a memory error message, such as "out of malloc space," power-cycle the switch. (CSCdi92171)
- TFTP errors might occur when using an ATM port to upload/download configuration data to and from the supervisor engine module. (CSCdi74908)
- In some instances, the show log command does not display the time of a show bus timeout exception. (CSCdi87950)
- Between instances of a switch reset, you cannot add more than 256 permanent or static entries. (CSCdi90802)
- When the fan module on the Catalyst 5000 series switch chassis is removed, the FAN LED on the WS-X5006 Supervisor Engine Module might remain green instead of indicating a problem. (CSCdi91184)
- The Catalyst 5000 series switch learns the MAC address 00-00-00-00-00-00 and stores it in the CAM table. (CSCdi89535)
- When you power on/off redundant power supplies, the Catalyst 5000 series switch might display erroneous messages. (CSCdi78463)
- Under heavy traffic conditions, the CAM tables on the FDDI module can fill up, making the FDDI counters inaccessible. Once the traffic decreases, the counters are again accessible. (CSCdi63030)
- Under maximum traffic conditions (wire-speed traffic on the port with smallest packet sizes), a 10/100-Mbps Ethernet port might fail to come up after changing the speed from 10Mbps to auto. To recover, disable and then reenable the port or unplug and then plug in the port. (CSCdj00409)
Note For a description of caveats fixed in software release 2.1(5), see the "Differences Between Software Releases 2.1(4) and 2.1(5)" section.
This section describes possible unexpected behavior and other caveats for the Catalyst 5000 series supervisor engine module software release 2.1(5). The caveats listed here describe only serious problems.
- SNMP applications might temporarily slow down or timeout if you are using an SNMPWALK, mibwalk, or CiscoView session on a Catalyst 5000 series switch during an FDDI or ATM download. (CSCdi54102)
- Use the reset command at the boot prompt to load the Flash image. Do not use the command execflash to load the Flash image from the boot PROM. (CSCdi57385)
- If you attempt to enter an incorrect Flash image for the supervisor engine module, the error message might not be immediately obvious. For example, if you accidentally tried to download ATM software to the supervisor engine module, the following message would appear:
Console> (enable) download 199.133.219.189 atm_21.cbi
Download image atm_21.cbi from 199.133.219.189 to Module 1 FLASH (y/n) [n]? y
-
Finished network download. (1950240 bytes)
ERROR: ocs hdr: csum=0x41e4ecb7 ocsp->csum=0x4c
Download failed
- (CSCdi58607)
- If you upgrade the Catalyst 5000 series supervisor engine module software release 2.1(5) while the FDDI software is a release prior to 2.1 (such as Catalyst 5000 series FDDI software release 1.5), the FDDI module might fail to come online. To recover from this error, reset the module using the command reset mod_num. (CSCdi60282)
- If a Catalyst 5000 series switch is configured as a nonroot bridge with multiple blocked spanning-tree instances on trunk ports, SNMP speed performance might be impaired. To recover from this problem, adjust the spanning-tree parameters to reduce the number of blocked spanning-tree instances on trunk ports. (CSCdi65020)
- If the supervisor engine module receives a continuous stream of IP broadcasts, supervisor module spanning-tree operation might be affected. To recover from this problem, move the IP address of the Catalyst 5000 series switch to a management domain with fewer broadcasts. (CSCdi66330)
- The command show span tree shows a trunk port in some VLANs as not connected even though it is physically connected. (CSCdi66789)
- If you reset a Catalyst 5000 module while it is actively switching traffic between ports, the switch might display an error message similar to the following:
Cat5000_1> (enable) reset 4
Resetting module 4...
Cat5000_1> (enable) SYNFIG: CBL0, CBL1, or CBL2 Error
ATE0
ATS0=1
Power Up Diagnostics
Init NVRAM Log
....
....
- If this error occurs, the switch might experience a reset. To prevent this problem from occurring, do not reset a module while it is actively switching traffic between workstations connected to a Group Ethernet Switching module. (CSCdi67387)
- Currently the Catalyst 5000 series switch allows you to create static entries in the CAM table and specify invalid destination ports. (CSCdi68222)
- Under heavy broadcast conditions or under heavy management traffic, memory resources on the supervisor engine module might be reduced, affecting your ability to create a session on an ATM module; you might also not be able to Telnet to or ping the Catalyst 5000 series switch. This situation is temporary and the switch will recover as soon as the broadcast or heavy management traffic ends. (CSCdi68745)
- If you connect the console port of a Catalyst 5000 series switch to a 2511 terminal server, ensure that the "no exec" line appears in the configuration of each of the terminal server ports. If this line is not present, a module might fail to come online. (CSCdi69293)
- An ATM module running Catalyst 5000 series ATM module software release 1.1 fails to come online on a Catalyst 5000 series switch running Catalyst 5000 series supervisor engine module software release 2.1(5). To recover from this error, reset the ATM module using the command reset mod_num. We recommend that you install the ATM software release 2.2 or above.
Note For a description of caveats fixed in software release 2.1(3), see the "Differences Between Software Releases 2.1(2) and 2.1(3)" section.
This section describes possible, unexpected behavior and other miscellaneous caveats for the Catalyst 5000 series supervisor engine module software release 2.1(3). The caveats listed here describe only serious problems.
- Under certain conditions, a Catalyst 5000 10 Mbps Ethernet module port might stop learning MAC addresses even though the command show mac indicates the port is still receiving frames. To correct this problem, disable the port using the command set port disable mod_num/port_num and reenable the port using the command set port enable mod_num/port_num. (CSCdi60452)
- When there are continuous spanning-tree topology changes under heavy traffic conditions, a Catalyst 5000 series switch might remain accessible through ping and telnet but stop responding to SNMP requests. To correct this problem, reset the switch. (CSCdi64759)
- Occasionally some LECs that are configured on an ATM module might not come up after you reset a Catalyst 5000 Series switch. To recover from this problem, reconfigure the LECs that failed to come up on the ATM module. (CSCdi65004)
- Bidirectional file transfers between workstations occur more slowly using a Group Switching Ethernet module than using a Catalyst 5000 series Ethernet (10BaseT 24 port) module. Performance can be improved by adjusting the TCP timeout values on the work stations. (CSCdi65606)
- If a Catalyst 5000 series switch has a permanent multicast entry in its CAM table, some modules might not come online when the switch powers up. To recover from this problem, remove and reinsert the modules that fail to come online. (CSCdi66772)
- If the supervisor engine module receives a continuous stream of IP broadcasts, supervisor module spanning-tree operation might be affected. (CSCdi66330)
Note For a description of caveats fixed in software release 2.1(2), see the "Differences Between Software Releases 2.1 and 2.1(2)" section.
This section describes possible unexpected behavior and other miscellaneous caveats for the Catalyst 5000 series supervisor engine module software release 2.1(2). The caveats listed here describe only serious problems.
- Currently, the show mac command displays the InDiscard counter value as zero, instead of the actual counter value for Ethernet ports. (The InDiscard counter tracks the number of frames that the Catalyst 5000 series switch discards because it was destined for the local segment.) (CSCdi39812)
- The LrnDiscard counter (displayed using the show mac command) indicates the number of times a CAM entry is replaced with a newly learned address when the CAM table is full. In Catalyst 5000 series supervisor engine module software releases 1.3 and 1.4, the counter value is not maintained for each port; instead, the value is maintained for the entire switch. (CSCdi39883)
- Serial download is supported for downloading Flash code to the supervisor engine module, but not to the switching modules. (CSCdi41103)
- Although the show spantree command displays the fast-start feature as enabled on a trunk port, the spanning-tree portfast mode has no effect on trunk ports, such as ISL, ATM, or FDDI. Do not use the set portfast command on a trunk port. In addition, designating a port as a trunk port ignores the portfast feature for the port. When you hot swap an FDDI or ATM module, use the set portfast disable command to disable the fast-start feature for any ports that are using it. (CSCdi55205)
- Use the reset command at the boot prompt to load the Flash image. Do not use the command execflash to load the Flash image from the boot PROM. (CSCdi57385)
- Sometimes the command show module indicates that the status LED of an Ethernet module is green even if some module ports fail the PMD loopback test during power-up. The status LED of an Ethernet module is orange or red only when all of the module ports fail the PMD loopback test. Use the show test command to view PMD loopback test results for a module. To correct this error, reset the module using the reset mod_num command. If the failure persists, replace the module. (CSCdi57908)
- If you attempt to enter an incorrect Flash image for the supervisor engine module, the error message might not be immediately obvious. For example, if you accidentally tried to download ATM software to the supervisor engine module, the following message would appear:
Console> (enable) download 199.133.219.189 atm_21.cbi
Download image atm_21.cbi from 199.133.219.189 to Module 1 FLASH (y/n) [n]? y
-
Finished network download. (1950240 bytes)
ERROR: ocs hdr: csum=0x41e4ecb7 ocsp->csum=0x4c
Download failed
- (CSCdi58607)
- If the MAC address of a module has not been correctly configured, the module will fail to come online. The following output is displayed if this type of error occurs:
Catalyst 5000 Power Up Diagnostics
Init NVRAM Log
LED Test
ROM CHKSUM
DUAL PORT RAM r/w
RAM r/w
RAM address test
Byte/Word Enable test
EARL test
EARL test Done
BOOTROM Version 1.5, Dated Mar 8 1996 16:24:38
BOOT date: 07/30/96 BOOT time: 17:44:58
SIMM RAM address test
SIMM Ram r/w 55aa
SIMM Ram r/w aa55
Uncompressing image. This will take a minute...
Module 1 SPROM has invalid MAC address...module will remain offline
Minor hardware problem in Module # 1
Cisco Systems Console
Enter password:
c5-qa-5>
Mon Jul 30 1996, 17:46:07 Module 1 is online.
Syndiags failed on Module Number 4
c5-qa-5>
Mon Jul 30 1996, 17:46:18 Module 4 failed to come online.
Syndiags failed on Module Number 3
c5-qa-5>
Mon Jul 30 1996, 17:46:30 Module 3 failed to come online.
:wq
- (CSCdi59106)
- If a Catalyst 5000 series switch is configured as a nonroot bridge with multiple blocked spanning-tree instances on trunk ports, SNMP speed performance might be impaired. To recover from this problem, adjust the spanning-tree parameters to reduce the number of blocked spanning-tree instances on trunk ports. (CSCdi65020)
- An ATM module running Catalyst 5000 series ATM module software release 1.1 fails to come online on a Catalyst 5000 series switch running Catalyst 5000 series supervisor engine module software releases 2.1 or 2.1(2). To recover from this error, reset the ATM module using the command reset mod_num. We recommend that you install the ATM software release 2.2.
- When you disable a trunk on a fast Ethernet port using the command set trunk mod_num/port_num off, wait for a confirmation statement from the Catalyst 5000 series switch before reenabling the trunk. This prevents the trunk from going into an undesired state. If this error occurs, use the set port command to disable and then reenable the port.
- You cannot disable an ATM module using the set module disable command. However, you can disable other module types.
This section describes features, warnings, and cautions about using Catalyst 5000 series supervisor engine module software release 2.1.
Any module, including the supervisor module, that does not have its Media Access Control (MAC) address correctly programmed will fail to come online. If this occurs, contact the Cisco Technical Assistance Center (TAC) to replace the module or to apply an immediate workaround solution. The following output is displayed if a module does not have its MAC address correctly programmed:
Catalyst 5000 Power Up Diagnostics
Init NVRAM Log
LED Test
ROM CHKSUM
DUAL PORT RAM r/w
RAM r/w
RAM address test
Byte/Word Enable test
EARL test
EARL test Done
BOOTROM Version 1.5, Dated Mar 8 1996 16:24:38
BOOT date: 07/30/96 BOOT time: 17:44:58
SIMM RAM address test
SIMM Ram r/w 55aa
SIMM Ram r/w aa55
Uncompressing image. This will take a minute...
Module 1 SPROM has invalid MAC address...module will remain offline
Minor hardware problem in Module # 1
The remainder of this section describes the effects of an unprogrammed MAC address. The Catalyst 5000 series switch currently uses these types of MAC addresses for its modules:
00-40-0b-XX-XX-XX
00-60-09-XX-XX-XX
00-60-3e-XX-XX-XX
Module MAC addresses are programmed when the modules are brought online during the manufacturing process. Unique MAC address ranges are assigned to each module. If a module is incorrectly programmed, it reverts to this default MAC address:
00-40-0b-ff-00-00
If you are using Catalyst 5000 series supervisor engine module software release 2.1(2) or above, the Catalyst 5000 series switch performs a check during power-up to determine if any module has a MAC address range that contains ff-00-00 in the last three bytes. If the Catalyst 5000 series switch finds this condition, it displays the output shown above to indicate that an unprogrammed module is present. The message signifies that the SPROM on the module is not programmed, and the module will not come online.
If the default MAC address appears on any module other than the supervisor engine module, the module will not come online.
Note If the default MAC address appears on the supervisor engine module, the entire Catalyst 5000 series switch will not come online.
This section describes considerations regarding the Catalyst 5000 series switch configuration and is divided into the following subsections:
This section contains troubleshooting guidelines for system-level problems.
- If you attempt to boot a Catalyst 5000 series switch and the switch generates continuous MCP exception errors (and possibly fails to boot), make sure that the supervisor engine has the correct version of software for all of the hardware in your configuration.
- After initiating a switchover from the active supervisor engine to the standby supervisor engine, or when inserting a redundant supervisor engine in an operating switch, always wait until the supervisor engines have synchronized and all modules are online before removing or inserting modules or supervisor engines, or performing another switchover.
- If a Catalyst 5000 series switch contains 2.1 Software Memory Upgrade Kit single in-line memory modules (SIMMs) and is running a software release prior to 2.1 (such as release 1.5), the command show version displays only 4 MB of memory. You must install software release 2.1 or above to allow the command show version to recognize 2.1 Software Memory Upgrade Kit SIMMs, and to display the total memory.
- The show mac command displays the InDiscard counter value as zero, instead of the actual counter value for Ethernet ports. (The InDiscard counter tracks the number of frames that the Catalyst 5000 series switch discards because the frames were destined for the local segment.)
- The LrnDiscard counter (displayed using the show mac command) indicates the number of times a content-addressable memory (CAM) entry is replaced with a newly learned address when the CAM table is full. The counter value is not maintained for each port; instead, the value is maintained for the entire switch.
- Although the show spantree command displays the fast-start feature as enabled on a trunk port, the spanning-tree portfast mode has no effect on trunk ports, such as Inter-Switch Link (ISL), ATM, or FDDI. Do not use the set portfast command on a trunk port. In addition, designating a port as a trunk port ignores the portfast feature for the port. When you hot swap an FDDI or ATM module, use the set portfast disable command to disable the fast-start feature for any ports that are using it.
- Sometimes the command show module indicates that the status LED of an Ethernet module is green even if some module ports fail the physical medium-dependent (PMD) loopback test during power up; the status LED of an Ethernet module is orange or red only when all of the module ports fail the PMD loopback test. To correct this error, use the show test command to view PMD loopback test results for a module, and then reset the module using the reset mod_num command. If the failure persists, replace the module.
- You cannot disable an ATM module using the set module disable command. However, you can disable other module types. To recover from this problem, open an ATM session and shut down the ATM interface using the shutdown command.
- If you downgrade your Catalyst 5000 series switch from 2.1(5) or higher to a previous release, save your configuration. Your previous configuration will be erased as a result of the downgrade.
- If you have a LAN Emulation Configuration Server (LECS), LAN Emulation Server (LES), or broadcast and unknown server (BUS) configured on an ATM module, and you replace the supervisor engine module or move the ATM module from one slot to another, the ATM addresses (NSAPs) become modified. Be sure to update the LECS database configuration with new NSAP values.
- The CLI command show cam dynamic and the Simple Network Management Protocol (SNMP) query getmany community@vlan dot1dTpFdbAddress are sometimes out of sync.
- In a 10Base2 network, incorrect termination can cause the port to hang. To recover, disable and then reenable the port.
- In some instances, opening a Telnet session from a Catalyst 5000 series switch to a remote device that does not respond causes the console port on the Catalyst 5000 series switch to lock up. To recover, enter Ctrl-C or the following command sequence:
Ctrl-]
telnet> send escape
telnet> quit
Console > (enable)
- When you enter the clear counters command on Catalyst 5000 series switches, all port and MAC counters on both the command-line interface (CLI) and SNMP are cleared. This command might also affect management applications, which might temporarily show invalid results.
- We recommend that, for any port that will become a trunk port, you assign that port to VLAN 1 before enabling trunking on that port for the following reasons:
- If a VLAN assigned to an Ethernet port is inactive, that port cannot transition into trunking state.
- All VLANs except VLAN 1 are inactive on a VLAN Trunking Protocol (VTP) client until a connection to the VTP server is established, and a connection to a VTP server can happen only across a trunk.
- Any ports that are on a VLAN other than VLAN 1 will never be able to establish a connection to a VTP server because the ports cannot transition to trunking state.
- In certain PC configurations, the PC might be unable to connect to an Internetwork Packet Exchange (IPX) server. All of the following conditions must be present for this problem to occur:
- The PC must be a relatively fast machine.
- The PC must be Win95-based and use the Microsoft IPX/SPX-compatible protocol (with or without the Microsoft Client for NetWare Networks).
- The IPX frame type must be set to auto.
- No other protocol stacks can be loaded on the PC.
- The local IPX server to which the PC is connected must not use frame type 802.2. Or, if there is no local server, the local IPX router must not use frame type 802.2.
- To recover, take any of the following actions:
- Change the client PC from auto frame type to the same frame type the server is using.
- Add the 802.2 frame type to the server configuration.
- Add the 802.2 frame type to the router as an IPX subinterface.
- Load another protocol stack (such as TCP/IP) onto the PC in addition to the IPX/SPX-compatible protocol.
This section contains troubleshooting guidelines for module problems.
- If you are running Catalyst 5000 Series ATM module software release 3.1 or higher, we recommend that you run Catalyst 5000 series supervisor engine module software release 2.1(5) or higher.
- The Catalyst 5000 series supervisor engine module software release 2.1(5) or higher supports the following hardware modules:
- 100BaseFX Fast Ethernet switching module with six multimode fiber-optic and six single-mode fiber-optic ports (WS-X5114)
- Catalyst 5000 ATM LAN Emulation module Dual PHY with two UTP ports (WS-X5156)
- Catalyst 5000 ATM LAN Emulation module Dual PHY with two single-mode fiber-optic SC ports (WS-X5157)
- Catalyst 5000 ATM LAN Emulation module Dual PHY with two multimode fiber-optic SC ports (WS-X5158)
- Previous software releases do not correctly recognize these modules.
- When you replace a module (other than the supervisor engine module) with a module of a different type, or when you insert a module (other than the supervisor engine module) in an empty slot, use the command clear config mod_num to clear the module configuration information in the supervisor engine module and obtain the correct spanning-tree parameters. Perform this command from the supervisor engine module command prompt.
- Serial download is supported for downloading Flash code to the supervisor engine module, but not to the switching modules.
- If a module fails to come online, reset the module.
- In some instances, when using the autonegotiating functions of either the WS-X5213 or WS-X5213A 10/100-Mbps Fast Ethernet 12-port switching modules to connect to another autonegotiating Ethernet or Fast Ethernet device over a cable distance of 98 to 131 feet (30 to 40 meters), the duplex mode and port speed might be incorrectly negotiated. In this case, the link between the devices cannot be established. To recover from this situation, manually set the port speed and duplex mode on the Catalyst 5000 series switch. Set the port speed to either 10 or 100 Mbps and the duplex mode to either full or half duplex. The link is established when both devices have the same port speed and duplex mode settings.
- Alignment and frame check sequence (FCS) errors are detected when you plug 3Com 3c595 and 3c905 cards into a Catalyst 5000 series switch. (CSCdj01465)
If you experience trouble with a port that has a Media-Independent Interface (MII) transceiver attached to it, check that the transceiver jumpers are set properly.
If an MII transceiver is plugged in at an angle, the Catalyst 5000 series switch might stop transmitting data. To recover, reseat the MII transceiver so that is not seated at an angle. If the Catalyst 5000 series switch still cannot transmit data, disable and reenable the port.
This section contains troubleshooting guidelines for VLAN problems.
- If you upgrade to Catalyst 5000 series supervisor engine module software release 2.1(5) or higher from software release 1.5 or below, the default VTP mode is set to transparent. In transparent mode, new VLANs are not automatically advertised in the VTP domain. To allow a VLAN to be advertised, specify a unique name for the VTP domain and set the VTP mode to server before creating new VLANs.
- If you are upgrading from Catalyst 5000 series supervisor engine software release 1.5 or below, your allowed VLAN configuration for each trunk remains the same after the upgrade. Therefore, if you create VLANs outside the allowed VLAN range, those VLANs become active but are not added automatically to the trunk. For example, if you create VLAN 12 when VLANs 1 through 10 are configured as allowed on the trunk, VLAN 12 becomes active but is not added to the trunk.
- You can configure 256 VLANs on a Catalyst 5000 series switch. However, the VLAN ID configuration number has a range from 1 to 1000.
The Spanning-Tree Protocol blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, the Catalyst 5000 series switch should receive spanning-tree bridge protocol data units (BPDUs) periodically from its neighboring Catalyst 5000 switch. You can configure the frequency with which BPDUs are received using the set spantree hello command (the default frequency is set to two seconds). If a Catalyst 5000 series switch does not receive a BPDU in the time period defined by the set spantree maxage command (20 seconds by default), the blocked port transitions to the listening state, to the learning state, and finally to the forwarding state. As it transitions, the Catalyst 5000 series switch waits for the time period specified by the set spantree fwddelay command (15 seconds by default) in each of these intermediate states. Therefore, a blocked spanning-tree port moves into the forwarding state if it does not receive BPDUs from its neighbor within approximately 50 seconds.
Use the following guidelines to debug Spanning-Tree Protocol problems:
- Track all blocked spanning-tree ports in each Catalyst 5000 series switch in your network.
- For each blocked spanning-tree port, track the output of these commands:
- From the output of the show port command, check if the port has registered numerous alignment, FCS, or any other kind of line errors. If these errors are going up continuously, there is a possibility that this port might drop BPDUs on the input side.
- From the output of the show mac command, if the Inlost counter is going up continuously, the port is losing packets on the input side because of a lack of receive buffers. This problem can also cause the incoming BPDUs to be dropped.
- On the Catalyst 5000 series switch that has blocked ports, use the enable command to enter privileged mode and then check the output of the show biga command for resource errors (
RscrcErrors) on the BIGA Receive side. If these resource errors go up continuously, then there is a significant amount of broadcast/multicast traffic in the management VLAN, which is affecting the supervisor engine's ability to receive BPDUs.
- On a blocked spanning-tree port, check the duplex configuration to ensure that the port duplex is set to the same type as the port of its neighboring Catalyst 5000 series switch.
- On trunk ports, make sure that the trunk configuration is set properly on both sides of the link.
- On trunk ports, make sure that the duplex is set to full on both sides of the link to prevent any collisions under heavy traffic conditions.
- If you are using external MII transceivers, make sure that you are using compliant MII transceivers. Use the enable command to enter privileged mode and then enter the show portreg command for each of the MII ports to ensure that the basic mode control register (BMCR) is not set to 0xffff. The following example shows the BMCR register set to 0x2100:
c5-qa-6(enable) show portreg 1/2
Port/PHY registers for 1/2
0x00 BMCR RW = 0x2100
- If you see a value of 0xffff in this register, do not use the MII transceiver. An MII transceiver whose BMCR value is set to 0xffff can prevent the Catalyst 5000 series switch from receiving on this MII port, which can cause spanning-tree loops.
- Check the Disconnect Counter Register (DCR) and the False Carrier Sense Counter register (FCSCR). These registers should remain at 0 (except for the moment the link comes up). A value other than 0 indicates a physical layer problem, most likely with the transceiver.
- On a blocked spanning-tree port, make sure that the Rcv-Frms and Rcv-Multi counter is incrementing continuously. If the Rcv-Frms counter stops incrementing, the port is not receiving any frames or BPDUs. If the Rcv-Frms counter is incrementing but the Rcv-Multi counter is not, then this port is receiving non-multicast frames but is not receiving any BPDUs.
- Make sure that the sum of the logical ports across all instances of spanning-tree for different VLANs does not exceed the number allowed for each supervisor engine type and memory configuration. Refer to the following formula to compute this sum.
- The sum of all logical ports
- <=200 for Supervisor Engine I (with 8 MB)
<=400 for Supervisor Engine I (with 20 MB)
- where the sum of all logical ports =
(number of non-ATM trunks on the switch * number of active VLANs on that trunk)
+ (number of ATM trunks on the switch * number of active VLANs on that trunk * 2)
+ number of nontrunking ports on the switch
Note An ATM trunk is an ATM interface with a LAN Emulation Client (LEC) or an RFC 1483 PVC.

| Caution We recommend that you keep switched traffic off of the management VLAN.
|
- A Catalyst 5000 series switch should be the root for all VLANs, especially VLAN 1. In order to recover from an extended broadcast storm caused by a faulty device in a network, the Catalyst 5000 series switch resets blocked ports. To ensure recovery, all Catalyst 5000 series switches in the network should perform this function at the same time by sending synchronization packets on VLAN 1. These synchronization packets are sent only by the Catalyst 5000 series switch if it is the root bridge.
- The spanning-tree maxage value should not be less than 10 seconds. You might see BDPU hello packets on VLAN 1 as far as 6.1 seconds apart once every 2 minutes. This frequency depends on the number of trunks configured on the Catalyst 5000 series switch. This restriction will be lifted in a later software release.
The following documents are available for the Catalyst 5000 series switch:
- Catalyst 5000 Series Installation Guide
- Catalyst 5000 Series Configuration Guide and Command Reference
Cisco documentation and additional literature are available on a CD called Cisco Connection Documentation, Enterprise Series. The CD is updated and shipped monthly, so it might be more up to date than printed documentation. To order the Cisco Connection Documentation, Enterprise Series CD, contact your local sales representative or call Customer Service. The CD is available both as a single CD and as an annual subscription. You can also access Cisco technical documentation on the World Wide Web URL http://www.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the tool bar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.








Posted: Mon Sep 25 09:21:12 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.