Table of Contents
Release Notes for Catalyst 5000 Series Software Releases 3.x, 2.4(x), 2.3(x), and 2.2(x)
Current Release (October 4, 1999)
3.2(8) - General Deployment Release
Previous Releases
3.2(7), 3.2(6), 3.2(5), 3.2(4), 3.2(3), 3.2(2), 3.2(1b), 3.2(1), 3.1(2a), 3.1(2), 3.1(1), 2.4(5), 2.4(4), 2.4(3), 2.4(2), 2.4(1), 2.3(1), 2.2(2), 2.2(1)
These release notes describe the features, modifications, and caveats for Catalyst 5000 series supervisor engine software releases 3.x, 2.4(x), 2.3(x), and 2.2(x). The current version is software release 3.2(8). These release notes apply to Catalyst 5000 series as well as to Catalyst 2926 series switches running Catalyst 5000 series supervisor engine software.
Note On December 11, 1998, software release 3.2(4) became the General Deployment (GD) release for Catalyst 5000 series switches, replacing software release 2.1(12). The current GD release is software release 3.2(8).
Note Although the software image in a new Catalyst 5000 series switch operates 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 Cisco Connection Online for the latest released software image. For more information, see the "Cisco Connection Online" section.
Note Release notes for prior software releases were accurate at the time of release. However, for information on the latest caveats and updates to previously released software releases, refer to the release notes for the latest maintenance release in your software release train. You can access the latest software release notes at the World Wide Web locations listed in the "Cisco Connection Online" section.
These release notes contain the following 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/public/752/2000/
 | Caution
Supervisor engine software release 3.2(3) was deferred due to caveat CSCdk47393. In a switch with Supervisor Engine II and SNMP polling enabled, the system might erroneously report that modules were removed. The modules do not appear in the output of show module, show port, show mac, and other commands. In some cases, spanning-tree loops can occur, resulting in broadcast storms. This problem is resolved in software release 3.2(4). Additional instrumentation (CSCdk71101) was added in release 3.2(5) to log any reoccurrence of the event. |
If you are running software release 3.2(3), we recommend upgrading to software release 3.2(4) or later.
Release 3.x Memory Requirements
These memory restrictions apply when running supervisor engine software release 3.x:
- If you are using the new 20-MB Flash PC card (Cisco product number MEM-S3-FLC20MA) for the Supervisor Engine III, you must use software release 3.2(8) or later. The old 20-MB Flash PC card (MEM-S3-FLC20M) is supported in all 3.x releases.
- For releases 3.2(3) and later, you must have at least 16-MB DRAM installed on your supervisor engine.
- For releases 3.1(1) through 3.2(2), we recommend you have a minimum of 16-MB dynamic RAM (DRAM) installed on your supervisor engine. Supervisor Engine I modules with 8-MB DRAM do support these releases; however, you must use the 8-MB version of the software image (see Table 3) and you must run a minimal configuration. For more information, see the "Usage Guidelines, Restrictions, and Troubleshooting" section.
| Caution
As a precaution, always back up the switch configuration file before upgrading or downgrading the switch software to protect against losing all or part of the configuration stored in nonvolatile RAM (NVRAM). Use the write network command (Supervisor Engine I or II) or the copy config tftp command (Supervisor Engine III) to back up your configuration to a Trivial File Transfer Protocol (TFTP) server. Use the copy config flash command on a Supervisor Engine III to back up the configuration to a Flash device. |
Catalyst 5000 series supervisor engine software image files are available in the Software Center on Cisco Connection Online (CCO), Cisco's WWW site (software downloads are available to registered CCO users only):
- http://www.cisco.com/kobayashi/sw-center/switching/cat2900-5000-planner.shtml
To upgrade to software release 3.x from a version earlier than 2.4(3), you must first upgrade to software release 2.4(5) and then upgrade from 2.4(5) to software release 3.x.
| Caution
If you are running software release 2.4(3) through 2.4(5) on a Supervisor Engine I with only 8-MB DRAM, do not upgrade to any release later than 3.2(2). Doing so could corrupt the Flash on the supervisor engine. Add at least an additional 8-MB DRAM (16-MB DRAM total) before upgrading to releases later than 3.2(2). |
Catalyst 5000 series switches support these supervisor engine modules in software releases 3.x:
- Supervisor Engine I
- Supervisor Engine II
- Supervisor Engine III
Some supervisor engine types are not supported in certain switch chassis. Table 1 shows which supervisor engine types are supported in which Catalyst 5000 series switch chassis.
In addition, the supervisor engines are compatible with specific software releases. For more information, see the "Product and Software Version Matrix" section.
Table 1: Supervisor Engine Matrix
| Switch
| Supervisor Engine I
| Supervisor Engine II
| Supervisor Engine III
|
|---|
Catalyst 2900
| Fixed
| N/A
| N/A
|
Catalyst 2926
| N/A
| Fixed
| N/A
|
Catalyst 5002
| Yes
| Yes
| No
|
Catalyst 5002 with PFC1
| Yes
| Yes
| Yes
|
Catalyst 5000
| Yes
| Yes
| Yes
|
Catalyst 5505
| No
| Yes
| Yes
|
Catalyst 5500
| No
| Yes
| Yes
|
1PFC=power factor correction
|
This section contains configuration matrixes to help you order Catalyst 5000 series products. Table 2 lists the minimum supervisor engine version and the current recommended/default supervisor engine version for Catalyst 5000 series modules and chassis.
Note There might be additional minimum software version requirements for intelligent modules (those that run an additional, separate software image). Refer to the software release notes for the module type for more information.
Table 2: Product/Supervisor Engine Software Version Matrix
| Product Number
append with "=" for spares
| Product Description
| Minimum Supervisor Software Version
| Recommended Supervisor Software Version
|
|---|
| Supervisor Engine I
|
WS-X5005
| Supervisor Engine I, dual-port 100BaseFX SMF uplinks
| 1.1
| 3.2(7)
|
WS-X5006
| Supervisor Engine I, dual-port 100BaseFX MMF 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(7)
|
WS-X5506
| Supervisor Engine II, dual-port 100BaseFX MMF uplinks
|
WS-X5509
| Supervisor Engine II, dual-port 100BaseTX RJ-45/MII uplinks
|
| Supervisor Engine II G
|
WS-X5540
| Supervisor Engine II G base module
| 5.1(1a)
| 5.1(1a)
|
| Supervisor Engine III
|
WS-X5530-E1
| Supervisor Engine III base module
| 3.1(1)
| 3.2(7)
|
WS-X5530-E2
| Supervisor Engine III base module with NFFC
| 4.1(1)
| 4.5(3)
|
WS-X5530-E3
| Supervisor Engine III base module with NFFC II
| 4.3(1a)
| 4.5(3)
|
| Supervisor Engine III F
|
WS-X5534-E1-GESX
| Supervisor Engine III FSX, dual-port 1000BaseSX uplinks
| 4.3(1a)
| 4.5(3)
|
WS-X5536-E1-GELX
| Supervisor Engine III FLX, dual-port 1000BaseLX/LH uplinks
|
| Supervisor Engine III G
|
WS-X5550
| Supervisor Engine III G, dual-port 1000BaseX uplinks
| 5.1(1a)
| 5.1(1a)
|
| Supervisor Engine Uplink Modules
|
WS-U5531-FETX
| Dual-port 10/100BaseTX Fast Ethernet uplink module
| 3.1(1)
| 4.5(3)
|
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(1a)
| 4.5(3)
|
WS-U5534-GESX
| Dual-port 1000BaseSX Gigabit Ethernet uplink module
| 4.1(1)
| 4.5(3)
|
WS-U5536-GELX
| Dual-port 1000BaseLX/LH Gigabit Ethernet uplink module
|
WS-U5538-FEFX-MMF
| 4-port 100BaseFX MMF MT-RJ Fast EtherChannel uplink module
| 4.5(1)
| 4.5(3)
|
| Supervisor Engine III Feature Cards
|
WS-F5521=
| NetFlow Feature Card (NFFC)
| 4.1(1)
| 4.5(3)
|
WS-F5531=
| NFFC II
| 4.3(1a)
| 4.5(3)
|
WS-F5541=
| Route Switch Feature Card (RSFC)
| 5.1(1a)
| 5.1(1a)
|
| Ethernet, Fast Ethernet, and Gigabit Ethernet
|
WS-X5010
| 24-port 10BaseT Ethernet Telco
| 1.1
| 3.2(7)
|
WS-X5011
| 12-port 10BaseFL Ethernet MMF ST
| 1.2
|
WS-X5012
| 48-port 10BaseT Ethernet
| 2.4(1)
| 3.2(7)
|
WS-X5012A
| 48-port 10BaseT Ethernet Telco
| 4.2(1)
| 4.5(3)
|
WS-X5013
| 24-port 10BaseT Ethernet RJ-45
| 2.2(1)
| 3.2(7)
|
WS-X5014
| 48-port, 2-slot 10BaseT Ethernet
| 4.2(1)
| 4.5(3)
|
WS-X5015-MT
| 24-port 10BaseFL Ethernet MT-RJ
| 5.1(1)
| 5.1(1)
|
WS-X5020
| 48-port, 4-segment 10BaseT Ethernet Telco
| 2.1(1)
| 3.2(7)
|
WS-X5111
| 12-port 100BaseFX Fast Ethernet MMF SC
| 1.4
|
WS-X5113
| 12-port 100BaseTX Fast Ethernet RJ-45
| 1.2
|
WS-X5114
| 12-port (6-port SMF, 6-port MMF) 100BaseFX Fast Ethernet SC
| 2.1(5)
|
WS-X5201
| 12-port 100BaseFX Fast EtherChannel SC
| 2.3(1)
|
WS-X5201R
| 12-port 100BaseFX backbone Fast Ethernet SC
| 4.1(2)
| 4.5(3)
|
WS-X5203
| 12-port 10/100BaseTX Fast EtherChannel RJ-45
| 2.3(1)
| 3.2(7)
|
WS-X52131
| 12-port 10/100BaseTX Fast Ethernet RJ-45
| 1.5(4)
|
WS-X5213A
| 12-port 10/100BaseTX Fast Ethernet RJ-45
| 2.1(7)
|
WS-X5223
| 24-port, 3-segment 100BaseTX Fast Ethernet RJ-45
| 2.2(1)
|
WS-X5224
| 24-port 10/100BaseTX RJ-45
| 2.4(2)
|
WS-X5225R
| 24-port 10/100BaseTX Fast Ethernet RJ-45
| 4.1(2)
| 4.5(3)
|
WS-X5234-RJ45
| 24-port 10/100BaseTX Fast Ethernet RJ-45
| 4.5(1)
| 4.5(3)
|
WS-X5236-FX-MT
| 24-port 100BaseFX Fast Ethernet MT-RJ
|
WS-X5239-RJ21
| 36-port 10/100BaseTX Fast Ethernet Telco
| 5.1(2a)
| 5.1(2a)
|
WS-X5403
| 3-port 1000BaseX Gigabit Ethernet module
| 4.1(1)
| 4.5(3)
|
WS-X5410
| 9-port, 2-slot 1000BaseX Gigabit EtherChannel module2
| 4.2(1)
|
| Gigabit Interface Converters (GBICs)
|
WS-G5484=
| 1000BaseSX GBIC
| 4.1(1)
| 4.5(3)
|
WS-G5486=
| 1000BaseLX/LH GBIC
|
WS-G5487=
| 1000BaseZX GBIC
| 4.5(1)
|
| Token Ring
|
WS-X5030
| 16-port Token Ring module, UTP/FTP, RJ-45
| 3.1(1)
| 4.5(3)
|
WS-X5031
| 16-port Token Ring module, Volition, VF-45
|
| FDDI/CDDI
|
WS-X5101
| 1 Dual-attach Multimode FDDI MIC
| 1.3
| 3.2(7)
|
WS-X5103
| 1 Dual-attach CDDI RJ-45
|
WS-X5104
| 1 Dual-attach Single-Mode FDDI ST
|
WS-X5105
| 1 Dual-attach Multimode FDDI SC
|
| ATM
|
WS-X51531
| 1-port OC-3 UTP RJ-45
| 1.4
| 3.2(7)
|
WS-X51541
| 1-port OC-3 Single-Mode SC
|
WS-X51551
| 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, MPOA/LANE
| 3.2(1)
| 4.5(3)
|
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(7)
|
| Fabric Integration Modules
|
WS-X5165
| ATM fabric integration module
| 4.3(1a)
| 4.5(3)
|
WS-X5305
| Layer 3 fabric integration module
| 4.4(1)
|
| Network Analysis Module
|
WS-X5380
| Network Analysis Module
| 4.3(1a)
| 4.5(3)
|
| Modular Chassis
|
WS-C5000
| Catalyst 5000 chassis (5-slot)
| 1.1
| 3.2(7)
|
WS-C5002
| Catalyst 5002 chassis (2-slot)
| 2.2(1)
| 3.2(7)
|
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.5(3)
|
| Fixed-Configuration Chassis
|
WS-C2901
| Catalyst 2900 with two 100BaseTX uplinks and 12 10/100BaseTX ports
| 2.1(1)
| 3.2(7)
|
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)
|
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(1a)
| 4.5(3)
|
WS-C2926GL
| Catalyst 2926G with NFFC, two 1000BaseLX/LH uplinks, and 24 10/100BaseTX ports
|
Table 3 lists the software versions and applicable ordering information for the Catalyst 5000 series supervisor engine software.
Table 3: Software Version/Orderable Product Number Matrix
| Software Version
| Filename
| Orderable Product Number
Flash on System
| Orderable Product Number
Spare Upgrade (Floppy Media)
|
|---|
| Supervisor Engine I and II
|
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)
| 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
|
| Supervisor Engine 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(4)
| cat5000-sup.3-2-4.bin
| SFC5K-SUP-3.2.4
| SWC5K-SUP-3.2.4=
|
3.2(5)
| cat5000-sup.3-2-5.bin
| SFC5K-SUP-3.2.5
| SWC5K-SUP-3.2.5=
|
3.2(6)
| cat5000-sup.3-2-6.bin
| SFC5K-SUP-3.2.6
| SWC5K-SUP-3.2.6=
|
3.2(7)
| cat5000-sup.3-2-7.bin
| SFC5K-SUP-3.2.7
| SWC5K-SUP-3.2.7=
|
3.2(8)
| cat5000-sup.3-2-8.bin
| SFC5K-SUP-3.2.8
| SWC5K-SUP-3.2.8=
|
| Supervisor Engine III
|
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(4)
| cat5000-sup3.3-2-4.bin
| SFC5K-SUP3-3.2.4
| SWC5K-SUP-3.2.4=
|
3.2(5)
| cat5000-sup3.3-2-5.bin
| SFC5K-SUP3-3.2.5
| SWC5K-SUP-3.2.5=
|
3.2(6)
| cat5000-sup3.3-2-6.bin
| SFC5K-SUP3-3.2.6
| SWC5K-SUP-3.2.6=
|
3.2(7)
| cat5000-sup3.3-2-7.bin
| SFC5K-SUP3-3.2.7
| SWC5K-SUP-3.2.7=
|
3.2(8)
| cat5000-sup3.3-2-8.bin
| SFC5K-SUP3-3.2.8
| SWC5K-SUP-3.2.8=
|
This section describes the new features for software release 3.2(8).
This section describes the new features for software release 3.2.
- Intermodule Switched Port Analyzer (SPAN) for Token Ring ports—You previously could only use SPAN on the same module. In software release 3.2, this is no longer a restriction. However, Token Ring ports can only monitor other Token Ring ports. Additionally, when using the Concentrator Relay Function (CRF) type of virtual LAN (VLAN), only one source port is allowed if you are monitoring in the transmit direction. Token Ring modules do not support the inpkts option.
- New hardware supported:
- ATM dual physical sublayer (PHY) OC-3 switching module, single mode fiber (SMF) multiprotocol over ATM/LAN emulation (MPOA/LANE)—Runs permanent virtual connection (PVC) traffic-shaping software at speeds up to 155 Mbps. (WS-X5167)
- ATM dual PHY OC-3 switching module, multimode fiber (MMF) MPOA/LANE—Runs PVC traffic-shaping software at speeds up to 155 Mbps. (WS-X5168)
- ATM dual PHY OC-12 switching module, SMF MPOA/LANE—Runs PVC traffic-shaping software at speeds up to 622 Mbps. (WS-X5162)
- ATM dual PHY OC-12 switching module, MMF MPOA/LANE—Runs PVC traffic-shaping software at speeds up to 622 Mbps. (WS-X5161)
This section describes the new features for software release 3.1.
- Two new commands for the Route Switch Module have been added to software release 3.1(2):
- set rsmautostate {enable | disable}
- Enables and disables line protocol state determination of the RSM due to Catalyst port state changes.
- Displays the current status of RSM line protocol state determination (either enabled or disabled).
- Fast Redundant Switchover allows a Supervisor Engine II or III to switch over to another supervisor engine of the same type installed on the same switch faster than previous releases (supported in software version 3.1(2) only).
- FDDI Fast Switchover support with FDDI software release 3.1(1) and later (supported in software release 3.1(2a) and later).
- Fast EtherChannel enhancements, such as Spanning-Tree over Fast EtherChannel, and the new Port Aggregation Protocol (PAgP) that provides fully automated configuration of Fast EtherChannel bundles, scalable from 200 Mbps to 800 Mbps.
- Spanning-Tree Protocol enhancements:
- Uplink Fast Convergence provides rapid switchover to a redundant uplink for wiring closet switches when the spanning-tree root port fails or when the spanning-tree topology is recalculated.
- Uplink Load Balancing by VLAN enables traffic load balancing across uplinks by providing direct control over the spanning-tree port cost for VLANs on a trunking port.
- Mini-Remote Monitoring (RMON) agents for Fast EtherChannel and Token Ring provide the following:
- RFC 1757 statistics, history, alarms and events, standard RMON applications to monitor Fast EtherChannel traffic, and valuable RMON capabilities extension to a logical Fast EtherChannel.
- Standards-based RFC 1757 and RFC 1513 RMON for Catalyst 5000 series Token Ring ports that provides a complete Token Ring mini-RMON agent for monitoring traffic statistics.
- RMON alarm thresholds on any Management Information Base (MIB) object provides an effective notification mechanism through Simple Network Management Protocol (SNMP) traps for any user-definable events in a Catalyst 5000 series switch that has a MIB object.
- Multiple source port selection for the SPAN feature that enables monitoring of multiple Ethernet ports from a single Fast Ethernet probe or analyzer on the SPAN destination port.
- SNMPv2c agent provides 64-bit counters for monitoring high-speed interfaces, and Get_Bulk, which provides faster response for users and eliminates unnecessary SNMP traffic on the network.
- VTP Version 2, an extension to VLAN Trunk Protocol (VTP). VTP version 2 supports Token Ring LAN switching and ensures the consistency of VLAN configuration across a LAN switch fabric.
- CISCO-FLASH-MIB helps to administer and manage a Flash memory-based file system. The CISCO-FLASH-MIB provides the capability for the Supervisor Engine III module to upload, download, and manage multiple supervisor engine software images.
- New hardware supported:
- Supervisor Engine III supports a 3.6-Gbps backplane in the Catalyst 5505 and 5500 switch chassis and the use of Flash memory PC cards; features include modular uplink port modules, redundant supervisor engines, an R4700 RISC CPU running at 150 MHz, and 32-MB DRAM.
- ATM DS3 dual PHY module, which is a 45-Mbps ATM DS3 (digital signal level 3) interface support; dual, redundant PHY port.
- 16-port Token Ring module.
This section contains new features for software release 2.4.
- Support for the Catalyst 2926 switch, which is a fixed-configuration, 26-port, 10/100-Mbps autosensing LAN switch that provides high-performance switching solutions between workstations, servers, switches, and routers using the same architecture and software as the Catalyst 5000 series switches. The Catalyst 2926 switch supports all Catalyst 5000 series software features, with the exception that no modular daughter card alternatives (Multilayer Switching) are supported.
- For installation and configuration information on the Catalyst 2926 switch, refer to the Catalyst 2926 Series Installation Guide. For online access to quick, expert hardware installation and software configuration information, link to the Catalyst 2926 Quick Start, located on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com. You can access the Catalyst 2926 Quick Start from the Documentation area of the Service and Support page, or from the Catalyst 2900 Product page.
- Support for the 10/100-Mbps Workgroup Fast Ethernet switching module (10/100BaseTX 24 port)—WS-X5224
This section contains new features for Catalyst 5000 series supervisor engine software release 2.3.
- Fast EtherChannel allows two or four Fast Ethernet links to be grouped together to enable higher bandwidth channels for improved network performance.
- Dynamic VLAN assignment allows the Catalyst 5000 series switch to assign ports to a VLAN dynamically, based on the Media Access Control (MAC) address of the host connected to that port.
- Virtual Management Policy Server (VMPS) allows network administrators to define the VLAN membership policies for their network in a central database so that the Catalyst 5000 series switch fabric automatically configures user ports to the correct VLAN.
- VTP pruning optimizes network trunk bandwidth by reducing unnecessary broadcast, multicast, and flooded-unicast traffic. VTP allows the Catalyst 5000 series switch fabric to prune the VLAN forwarding tree automatically to contain traffic from each defined VLAN to only those switches that require the traffic.
- Cisco Group Management Protocol (CGMP) Fast Leave Processing detects leave messages from Internet Group Management Protocol (IGMP) version 2 hosts and immediately prunes ports from the specified multicast forwarding tree to reduce processing latency for nodes leaving a multicast group.
- IP Permit List allows network administrators to create a list of IP addresses or subnets permitted to access the system console via Telnet and SNMP agent services.
- RMON agent enhancements automatically restore the last configuration of the embedded RMON agent for each port after a system reset and send all RMON traps to all trap hosts configured in the Catalyst 5000 series console trap-receiver table.
- Support for new hardware including the following:
- Catalyst 5505 switch
- Ethernet switching module (10BaseT 48 port)—WS-X5012
- Fast EtherChannel switching module (100BaseFX 12 port)—WS-X5201
- 10/100-Mbps Fast EtherChannel switching module (10/100BaseTX 12 port)—WS-X5203
- Route Switch Module (RSM) (Catalyst 5000 and Catalyst 5500 switches only)—WS-X5302
- The RSM is a Route Switch Processor 2 (RSP2)-class router module for the Catalyst 5000 series switches. The RSM provides high-performance, Multilayer Switching and routing services between switched VLANs and emulated LANs (ELANs). Initial protocol support includes IP, IPX, AppleTalk, and DECnet. For more information, refer to the Catalyst 5000 Series Switch Route Switch Module Installation and Configuration Note (documentation part number 78-4058-01).
This section contains new features for Catalyst 5000 series supervisor engine software release 2.2.
- Supervisor Resilience. The Catalyst 5500 switch offers the option of using two supervisor engine modules to provide fault tolerance in mission-critical environments and to ensure switching resilience.
Note The Supervisor Resilience feature is available on Supervisor Engine II only.
- Broadcast/Multicast Suppression allows you to limit broadcast traffic from any port and prevent a switched port from being disrupted by a broadcast storm.
- CGMP manages multicast traffic in Catalyst 5000 series switches by allowing directed switching of IP multicast traffic within a network at maximum performance.
- Secure Port Filtering allows Ethernet and Fast Ethernet switching modules to block input to an Ethernet or Fast Ethernet port when the MAC address of a station attempting to access the port is different from the configured or learned MAC address.
- Terminal Access Controller Access Control System Plus (TACACS+) Protocol controls access to the supervisor engine module and determines the identity of a user by verifying a username with a password.
- System Message Logs allow you to send system messages from the supervisor engine module to syslog servers.
- Network Time Protocol (NTP) time-synchronizes Catalyst 5000 series switches through the NTP protocol from an NTP server.
- Domain Name System (DNS) allows the resolution of host names through the DNS protocol from a DNS server.
- Login Banner allows you to create a single-line or multiline message banner that appears on your screen before session login.
- Multiple Module Download allows you to perform a single Trivial File Transfer Protocol (TFTP) download that updates all modules of the same type on a Catalyst 5000 series switch.
- New hardware supported:
- Supervisor engine software release 2.2 supports the following hardware features:
- Supervisor Engine II
- Catalyst 5002 switch
- Catalyst 5500 switch
- WS-X5223 group switching Fast Ethernet switching module (100BaseTX, 24 port)
- WS-X5013 Ethernet switching module (10BaseT, 24 port, RJ-45)
These sections describe open and resolved caveats in supervisor engine software release 3.2(8):
Note For a description of caveats resolved in software release 3.2(8), see the "Resolved Caveats in Software Release 3.2(8)" section.
There are no open caveats in software release 3.2(8).
Note For a description of open caveats in software release 3.2(8), see the "Open Caveats in Software Release 3.2(8)" section.
This section describes caveats resolved in software release 3.2(8):
- If you configure multiple RMON alarmEntry's, the RMON alarm might stop sampling the alarm variable and fails to generate an alarm trap when the alarm threshold is reached. This problem is resolved in software release 3.2(8). (CSCdm50428)
- If you specify an invalid Flash device name (MIB object ciscoFLashCopyDestinationName) when you attempt to copy a file to the Flash file system using SNMP, the switch might reset. This problem is resolved in software release 3.2(8). (CSCdm54460)
These sections describe open and resolved caveats in supervisor engine software release 3.2(7):
Note For a description of caveats resolved in software release 3.2(7), see the "Resolved Caveats in Software Release 3.2(7)" section.
This section describes open caveats in software release 3.2(7).
If you configure multiple RMON alarmEntry's, the RMON alarm might stop sampling the alarm variable and fails to generate an alarm trap when the alarm threshold is reached. (CSCdm50428)
Note For a description of open caveats in software release 3.2(7), see the "Open Caveats in Software Release 3.2(7)" section.
This section describes caveats resolved in software release 3.2(7):
- In some cases, when using SPAN on the Token Ring modules (WS-X5030 or WS-X5031), receive (Rx) traffic is not mirrored to the SPAN destination port. This problem is resolved in software release 3.2(7). (CSCdk78241)
- If a large number of spanning-tree topology changes occur on the switch, the switch might generate an "STP loop - channel mod_num/port_list is disable" message and place an EtherChannel port bundle into an "errdisable" state. The workaround is to use the set spantree portfast enable command on ports connected to a single host to reduce the number of topology changes that occur on the switch. This problem is resolved in software release 3.2(7). (CSCdm30811)
- In some cases, entering the show cdp neighbors detail command causes the switch to generate "alignment correction" syslog messages. These messages do not affect the functionality of the switch. This problem is resolved in software release 3.2(7). (CSCdk85671)
- In some cases, if you configure a port as a SPAN source port and subsequently configure the same port as the SPAN destination, the SPAN destination port might be unable to receive traffic if any other SPAN-related commands are executed on the port. To avoid the problem, disable SPAN before changing the SPAN configuration. If the problem occurs, reset the module with the problem SPAN port. This problem is resolved in software release 3.2(7). (CSCdm43384)
- If you set the port duplex and speed to fixed values on some ports and then you configure autonegotiation on those ports, the ports might not form an EtherChannel if you configure them in on mode. The workaround is to manually configure the same duplex mode on the ports before enabling autonegotiation. This problem is resolved in software release 3.2(7). (CSCdm32145)
- If you install an uplink module in a Supervisor Engine III running software that does not support that uplink module, the supervisor engine does not function correctly when the switch boots. The correct behavior is that the supervisor engine operates normally but the uplink module ports do not function. This problem is resolved in software release 3.2(7). (CSCdm22188)
- In some cases, in a switch with redundant supervisor engines, the system cannot modify the BOOT environment variable in the standby supervisor engine if the bootstring is very long. This problem is resolved in software release 3.2(7). (CSCdm45329)
- In some cases, the firmware version displayed by the show version command does not display the complete boot ROM version number. This problem is resolved in software release 3.2(7). (CSCdm49598)
- In some cases, after a switch reset, the show port command shows "connected" for Token Ring ports but the show spantree command shows "not-connected," and the ports do not transmit traffic. This problem is resolved in software release 3.2(7). (CSCdk35029)
- In a complex network environment, removing and adding trunks continuously can cause the switch to reset. In some cases, the reset is preceded by the formation of spanning-tree loops in the network. This problem is resolved in software release 3.2(7). (CSCdm30175)
- In some cases, the switch resets after downloading the VMPS configuration file. This problem is resolved in software release 3.2(7). (CSCdm20649)
These sections describe open and resolved caveats in supervisor engine software release 3.2(6):
Note For a description of caveats resolved in software release 3.2(6), see the "Resolved Caveats in Software Release 3.2(6)" section.
This section describes open caveats in software release 3.2(6).
In some cases, when using SPAN on the Token Ring modules (WS-X5030 or WS-X5031), receive (Rx) traffic is not mirrored to the SPAN destination port. (CSCdk78241)
Note For a description of open caveats in software release 3.2(6), see the "Open Caveats in Software Release 3.2(5)" section.
This section describes caveats resolved in software release 3.2(6):
- If you configure an RMON alarm on an ATM module MIB, subsequently configuring an RMON alarm on the switch might cause the switch to stop responding to SNMP requests. The workaround is to avoid configuring RMON alarms on ATM module MIBs. This problem is resolved in software release 3.2(6). (CSCdk69513)
- On the Token Ring modules (WS-X5030 or WS-X5031), if you move the SPAN destination from port to port, the ports might stop forwarding traffic. This problem is resolved in software release 3.2(6). (CSCdk88229)
- In some situations, attempts to create or modify a VLAN using SNMP fail with this message:
Vlan configuration failed (41)
- The workaround is to create or modify the VLAN using the switch CLI. This problem is resolved in software release 3.2(6). (CSCdk88280)
- In some cases, in a switch with a Supervisor Engine I or II and an ATM module, the ATM module might not receive VTP updates from the VTP server after the switch or the module is reset. The workaround is to session to the ATM module, shut down the ATM interface (using the shutdown command), wait five seconds, and then bring the interface back up (using the no shutdown command). This problem is resolved in software release 3.2(6). (CSCdk80168)
- The 64-bit Rx and Tx Unicast Packets counters are reported incorrectly for these modules:
- WS-X5005, WS-X5006, WS-X5009—Supervisor Engine I module uplink ports
- WS-X5010—24 port 10BaseT (Telco connector)
- WS-X5011—12-port 10BaseFL MMF (ST connector)
- WS-X5013— 24 port 10BaseT (RJ-45 connector)
- WS-X5113—12-port 100BaseTX (RJ-45 connector)
- This problem is resolved in software release 3.2(6). (CSCdk92543)
- Under some circumstances, several ports might incorrectly be assigned the same ifIndex value (you can see the ifIndex values for ports using the show port command). If multiple ports share an ifIndex value, when you change the configuration on one port other ports with the same ifIndex value might be affected. If this problem occurs, clear the entire switch configuration using the clear config all command (make sure you back up your switch configuration before entering this command or your configuration will be lost) and reset the switch. This problem is resolved in software release 3.2(6). (CSCdk74506)
- Under some rare conditions, the switch attempts to free a memory buffer that was previously released, causing the switch to reset. This problem is resolved in software release 3.2(6). (CSCdk91385)
- If you reset the switch with certain transceivers connected to a supervisor engine MII port, the transceiver indicates the port is faulty. The workaround is to disconnect the transceiver, reset the switch, and reconnect the transceiver after the switch boots. This problem is resolved in software release 3.2(6). (CSCdk70113)
- In some cases, setting a MIB object in the fddimibSMTTable using SNMP causes an exception error, resetting the switch. The workaround is to avoid issuing SNMP set requests on MIB objects in fddimibSMTTable. This problem is resolved in software release 3.2(6). (CSCdm05169)
- In some cases, installing the RMON alarm configuration in TrafficDirector causes the switch to reset if there are two or more trap receivers configured in the NetScout trap admin table. The workaround is to make sure you do not use TrafficDirector from more than one host to install RMON alarms for a single switch. This problem is resolved in software release 3.2(6). (CSCdm11221)
These sections describe open and resolved caveats in supervisor engine software release 3.2(5):
Note For a description of caveats resolved in software release 3.2(5), see the "Resolved Caveats in Software Release 3.2(5)" section.
This section describes open caveats in software release 3.2(5).
If you configure an RMON alarm on an ATM module MIB, subsequently configuring an RMON alarm on the switch might cause the switch to stop responding to SNMP requests. The workaround is to avoid configuring RMON alarms on ATM module MIBs. (CSCdk69513)
Note For a description of open caveats in software release 3.2(5), see the "Open Caveats in Software Release 3.2(5)" section.
This section describes caveats resolved in software release 3.2(5).
- Additional instrumentation was added to log any reoccurrence of the event that caused CSCdk47393. (CSCdk71101)
- If you change the console baud rate on a Supervisor Engine III module to a value other than 9600, console input and output might fail after the switch is reset. The workaround is to reconfigure the connected terminal baud rate back to 9600. This problem is resolved in software release 3.2(5). (CSCdk32962)
- In a system with redundant Supervisor Engine III modules, after a switchover from the active to the standby supervisor engine, any 48-port, 10BaseT Ethernet modules (WS-X5012) installed in the system might reset. The expected behavior is that the modules stay online. This problem is resolved in software release 3.2(5). (CSCdk72006)
- In some cases, when you initiate a TFTP download of a configuration file that contains the set interface command, SNMP queries to the switch will fail. The workaround is to remove the set interface command in the configuration file. This problem is resolved in software release 3.2(5). (CSCdk67081)
- On some switch ports, if you enable port security on the port before the port is in the spanning-tree forwarding state, port security might shut the port down. This problem occurs only if BPDUs, broadcast packets, or other traffic is received on the port before the port enters the forwarding state. This problem affects these products:
- WS-C2926—Catalyst 2926 switch
- WS-X5223—24 port 3 segment 100BaseTX (RJ-45 connector)
- WS-X5224— 24 port 10/100BaseTX (RJ-45 connector)
- WS-X5020—48 port 4 segment 10BaseT (Telco connector)
- WS-X5010—24 port 10BaseT (Telco connector)
- WS-X5014—48 port 10BaseT (RJ-45 connector)
- WS-X5012—48 port 10BaseT (Telco connector)
- WS-X5012a—48 port 10BaseT (Telco connector)
- WS-X5013— 24 port 10BaseT (RJ-45 connector)
- The workaround is to enable the port security feature after the port is in the forwarding state (use the show spantree mod_num/port_num command to verify the spanning-tree state). This problem is resolved in software release 3.2(5). (CSCdk73206)
- In a system with Supervisor Engine III, if you configure the in-band (sc0) interface IP address such that the last byte of the address is 54, the NVRAM on the switch might become corrupted. The workaround is to not configure an IP address with the last byte set to 54. This problem is resolved in software release 3.2(5). (CSCdk79235)
- In some cases, when you upgrade the system software on Supervisor Engine I or II, some sectors of the Flash memory might not be erased completely, causing the output of the show version command to display the original version number in the McpSW version field and the upgrade version number in the NmpSW version field. In most cases, this problem does not impact the functionality of the switch. This problem is resolved in software release 3.2(5). (CSCdk78704, CSCdk86788)
- In some cases, if a Telnet session to the switch closes abnormally while the switch is authenticating a user with the TACACS+ server, the switch might not close the session to the server properly, eventually causing the server to reach the maximum number of supported sessions. Subsequent attempts to authenticate with the server will fail. This problem is resolved in software release 3.2(5). (CSCdk79831)
- In some cases, when a Watchdog timeout NMI occurs on the switch, the event is displayed on the console but the information is not written to the system log (the event does not appear in the output of the show log command). This problem is resolved in software release 3.2(5). (CSCdk42794)
- In some cases, the switch might reset if you disconnect a Telnet session while the system is printing a syslog message to that Telnet session. This problem is resolved in software release 3.2(5). (CSCdk70499)
- If you enter the set rsmautostate enable command, the command entry does not appear in the switch configuration file. This problem is resolved in software release 3.2(5). (CSCdk70557)
- On the Catalyst 5000 series Supervisor Engine III, make sure you have a cable attached to the console port before entering the set system modem enable command. If you enter the command with no cable attached, the switch might stop sending frames (including BPDUs) the next time an event is reported to the console log. This might result in a broadcast storm, spanning-tree loops, or other problems. The workaround is to not enter the set system modem enable command when no cable is attached to the console port. This problem is resolved in software release 3.2(5). (CSCdk69429)
These sections describe open and resolved caveats in supervisor engine software release 3.2(4):
Note For a description of caveats resolved in software release 3.2(4), see the "Resolved Caveats in Software Release 3.2(4)" section.
This section describes open caveats in software release 3.2(4).
If you change the console baud rate on a Supervisor Engine III module to a value other than 9600, console input and output might fail after the switch is reset. The workaround is to reconfigure the connected terminal baud rate back to 9600. (CSCdk32962)
Note For a description of open caveats in software release 3.2(4), see the "Open Caveats in Software Release 3.2(4)" section.
This section describes caveats resolved in software release 3.2(4).
- In a switch with Supervisor Engine II and SNMP polling enabled, the system might erroneously report that modules were removed. The modules do not appear in the output of show module, show port, show mac, and other commands. In some cases, spanning-tree loops can occur, resulting in broadcast storms. This problem is resolved in software release 3.2(4). (CSCdk47393)
- In a switch with Supervisor Engine II and SNMP polling enabled, the system might erroneously report that certain modules (such as WS-X5010 and WS-X5224) were removed. The modules do not appear in the output of show module, show port, and other commands. In some cases, spanning-tree loops can occur, resulting in broadcast storms. This problem is resolved in software release 3.2(4). (CSCdk71101)
- If you configure Fast EtherChannel on the Supervisor Engine III dual-port fiber-optic uplink module (WS-U5533-FEFX-MMF or WS-U5535-FEFX-SMF) and the link in one direction on one of the ports fails so that receive (Rx) traffic is no longer received on that port, that port incorrectly continues to transmit traffic. The correct behavior is that the port should be disabled, allowing all traffic to be transmitted over the second link in the bundle. This problem is resolved in software release 3.2(4). (CSCdk49184)
- Some counters might not restart at one again after reaching their maximum value. This problem is resolved in software release 3.2(4). (CSCdk10989)
- In some cases, an ATM module might not receive any traffic even though the show spantree command output shows that the port is connected. This problem is resolved in software release 3.2(4). (CSCdk50047)
- SNMP queries might take an unusually long amount of time on a Catalyst 5000 series switch with a LANE module installed, especially when you attempt to enable RMON alarms on the device. This problem is resolved in software release 3.2(4). (CSCdk22392)
- In some cases, under heavy traffic (close to 99%), the system might generate a Switching Bus Timeout error, causing the switch to reset. This problem is resolved in software release 3.2(4). (CSCdk56528)
- In some cases, in a Token Ring environment with more than 50 rings, IEEE spanning-tree ports on the Token Ring modules (WS-X5030 and WS-X5031) might remain in listening mode instead of transitioning to forwarding or blocking mode. This problem is resolved in software release 3.2(4). (CSCdk53090)
- In some cases, a Catalyst 5000 series switch continues to send authentication failure traps to the trap receiver when the switch is polled with the incorrect community string, even when you have entered the set snmp trap disable auth command. This problem is resolved in software release 3.2(4). (CSCdk31799)
- In some cases, a Catalyst 5000 series switch with redundant supervisor engines might reset as a result of the change from Daylight Saving Time to Standard Time. This problem only occurs if the Daylight Saving Time adjustment is enabled (using the set summertime enable command) and the switch has not been reset or power-cycled since the change to Standard Time. This problem is resolved in software release 3.2(4). (CSCdk57762)
- In some cases, VMPS client switches might reset when an end station is moved from a static port to a dynamic port. This problem is resolved in software release 3.2(4). (CSCdk56145)
- When a station attached to the 48-port, 10BaseT Ethernet module (WS-X5012) is powered off or disconnected, the ifOutOctets counter value for the port (shown in the output of the show counters command) is changed to whatever the current ifInOctets counter value is for that port. This problem is resolved in software release 3.2(4). (CSCdk58207)
- In some cases, in a Catalyst 5000 series switch with an EARL1+ daughter card and one or more 12-port 100BaseFX Ethernet (WS-X5201R) or 24-port 10/100BaseTX Ethernet (WS-X5225R) modules, a switching bus timeout might occur. This problem is resolved in software release 3.2(4). (CSCdk61818)
- The 80-character length limit on syslog messages might cause truncation of important information (such as the entire IP address of a station making unauthorized attempts to Telnet to the switch). This problem is resolved in software release 3.2(4). (CSCdk59351)
- When you attempt to configure the switch using the configure network command, the switch might reset. The problem only occurs when you specify the DNS host name instead of the dotted decimal IP address of the TFTP server. This problem is resolved in software release 3.2(4). (CSCdk66599)
- The sysDescr MIB object does not contain the software version information. This problem is resolved in software release 3.2(4). (CSCdk63651)
- On a VMPS client switch attached to an ATM cloud, MAC addresses reachable over the ATM link might incorrectly be interpreted by the VMPS client as connected to a local Ethernet port. If the VMPS server is configured to deny VLAN membership to MAC addresses that are not contained in the VMPS database, communication with devices located out the ATM link is lost. This problem is resolved in software release 3.2(4). (CSCdk61813)
- After a topology change occurs in a Token Ring environment, when STP reconverges, source-routed frames originating from a Catalyst 5000 series Token Ring module (WS-X5030 or WS-X5031) are not forwarded across an ISL trunk link to another switch. Non-source-routed frames are forwarded correctly. The workaround is to enter the clear cam dynamic command on the affected switches. This problem is resolved in software release 3.2(4). (CSCdk63561)
- In some cases, on Catalyst 5000 series switches with Supervisor Engine III, configuring the port priority level to high (using the set port level mod_num/port_num high command) on certain modules can cause a switching bus timeout, resetting the switch. The problem only occurs on modules with EPLD-based arbiters. Use the show test command to check whether a particular module is affected. Modules that display "N" in the SAMBA field are affected. The workaround is to configure the port priority level to normal on the affected module. This problem is resolved in software release 3.2(4). (CSCdk69662)
| Caution
Supervisor engine software release 3.2(3) was deferred due to caveat CSCdk47393. If you are running release 3.2(3), we recommend upgrading to release 3.2(4) or later. For more information, see the "Deferred Software Releases" section. |
These sections describe open and resolved caveats in supervisor engine software release 3.2(3):
Note For a description of caveats resolved in software release 3.2(3), see the "Resolved Caveats in Software Release 3.2(3)" section.
| Caution
Supervisor engine software release 3.2(3) was deferred due to caveat CSCdk47393. If you are running release 3.2(3), we recommend upgrading to release 3.2(4) or later. For more information, see the "Deferred Software Releases" section. |
This section describes open caveats in software release 3.2(3).
- In a switch with Supervisor Engine II and SNMP polling enabled, the system might erroneously report that modules were removed. The modules do not appear in the output of show module, show port, show mac, and other commands. In some cases, spanning-tree loops can occur, resulting in broadcast storms. This problem is resolved in software release 3.2(4). (CSCdk47393)
- If you change the console baud rate on a Supervisor Engine III module to a value other than 9600, console input and output might fail after the switch is reset. The workaround is to reconfigure the connected terminal baud rate back to 9600. (CSCdk32962)
Note For a description of open caveats in software release 3.2(3), see the "Open Caveats in Software Release 3.2(3)" section.
| Caution
Supervisor engine software release 3.2(3) was deferred due to caveat CSCdk47393. If you are running release 3.2(3), we recommend upgrading to release 3.2(4) or later. For more information, see the "Deferred Software Releases" section. |
This section describes caveats resolved in software release 3.2(3).
- In some cases, ports on a 12-port, 10/100-Mbps Fast Ethernet module (WS-X5213A or WS-X5203) connected to ports on a 24-port, 10/100-Mbps Fast Ethernet module (WS-X5225R) might autonegotiate to half duplex rather than full duplex. To recover, specify a fixed port speed, or disable and reenable the port. This problem is resolved in software release 3.2(3). (CSCdk08385)
- In some cases, when you access a Catalyst 5000 series switch containing a Supervisor Engine III module from a Windows 95/NT machine using Microsoft Telnet, some commands cannot be completed. This problem is resolved in software release 3.2(3). (CSCdk18934)
- After prolonged SNMP usage, the Catalyst 5000 supervisor engine might lose communication with a module for some SNMP and CLI commands. To recover, reset the module. This problem is resolved in software release 3.2(3). (CSCdk21580, CSCdk26527)
- In some cases after a switchover, Catalyst 5000 series 10/100-Mbps ports whose port speed is set to 100 Mbps and whose duplex is set to full duplex lose their duplex setting and are set to half duplex. As a workaround, disable and reenable the affected ports. This problem is resolved in software release 3.2(3). (CSCdk32209)
- On a Catalyst 5000 series switch with a Supervisor Engine III, if the "System Uptime" (shown in the output of the show version command) reaches 49 days, 17 hours, and 3 minutes (232 seconds), some switching modules might reset. This problem is resolved in software release 3.2(3). (CSCdk32229)
- In some cases, when you configure ports as a Fast EtherChannel bundle, the configuration might fail due to a speed/duplex mismatch even though the ports are not connected to another device. This problem is resolved in software release 3.2(3). (CSCdk22225)
- When you open a Telnet session to a Catalyst 5000 series switch with a Supervisor Engine III, TACACS+ might allow more than the configured number of login attempts. This problem is resolved in software release 3.2(3). (CSCdk24291)
- In certain situations, a switch with both an RSM and a Fast EtherChannel-capable module installed might reset when a channel goes down. This problem is resolved in software release 3.2(3). (CSCdk32840)
- The value of the ifConnectorPresent MIB object for Fast EtherChannel ports should be FALSE, but the SNMP agent returns a TRUE value. This problem is resolved in software release 3.2(3). (CSCdk32212)
- When you attempt to enable NTP on a switch with many active Telnet sessions established, the NTP configuration might fail. This problem is resolved in software release 3.2(3). (CSCdk19605)
- In some situations, when you change the default system logging levels (using the set logging level facility severity default command), the changes are not saved after the switch is reset. This problem is resolved in software release 3.2(3). (CSCdk19476)
- When a switchover from the active to the standby supervisor engine occurs, a trunk port on the 24-port, 10/100-Mbps Fast Ethernet module (WS-X5225R) might not autonegotiate the correct port speed and duplex settings. The workaround is to set the port speed and duplex manually. This problem is resolved in software release 3.2(3). (CSCdk29421)
- In some cases, certain devices connected to a 12-port, 10/100-Mbps Fast Ethernet module (WS-X5203) module do not detect an active link after the module is reset. This problem is resolved in software release 3.2(3). (CSCdk21908)
- In some situations, excessive "alignment correction" messages might be sent to the switch console. This problem is resolved in software release 3.2(3). (CSCdj62415, CSCdk08604)
- When Connectionless Network Service/Intermediate System-to-Intermediate System (CLNS/ISIS) routing is enabled on a neighboring router, the Catalyst 5000 series switch might drop CDP packets, preventing some neighboring devices from appearing in the show cdp neighbors command output. This problem is resolved in software release 3.2(3). (CSCdk34032)
- On 10BaseT Ethernet modules, if a port is assigned to a particular VLAN and is configured as the SPAN source, when you change the VLAN assignment for that port, the port might stop transmitting traffic. This problem is resolved in software release 3.2(3). (CSCdk25510)
- The 48-port, 10BaseT Ethernet module (WS-X5012) incorrectly drops valid frames with dribble bits (extra bits added to frames by some end stations and transceivers). This problem is resolved in software release 3.2(3). (CSCdk32984)
- In some cases, when you attempt to use the CiscoView Device Configuration window to modify the IP routing table on a Catalyst 5000 series switch, the change is not made on the switch correctly. If you attempt to change the ipRouteNextHop, the value is not changed. If you attempt to change the ipRouteDest, a new table entry is added instead of the old value being changed. This problem is resolved in software release 3.2(3). (CSCdk34909)
- If you enable NTP on a Catalyst 5000 series switch with redundant Supervisor Engine III modules, the standby supervisor engine might not boot when the primary supervisor engine fails (the standby supervisor engine remains in ROM monitor mode). This problem is resolved in software release 3.2(3). (CSCdk39840)
- When the Catalyst 5000 series switch generates a Cold Start SNMP trap, the source IP address contained in the trap is incorrectly set to 0.0.0.0 rather than the IP address of the switch. This problem is resolved in software release 3.2(3). (CSCdk35617)
- In some cases, RMON traps contain incorrect utilization values, and utilization threshold alarms are generated for ports that are disabled or are not connected. This problem is resolved in software release 3.2(3). (CSCdk31934)
- In some circumstances, VLANs that are not allowed on a trunk port are listed incorrectly as "Vlans in spanning tree forwarding state and not pruned" in the output of the show trunk command. This problem is resolved in software release 3.2(3). (CSCdk31784)
- When enabling hardware broadcast suppression (using the set port broadcast mod_num/port_num threshold% command) after enabling software broadcast suppression (using the set port broadcast mod_num/port_num threshold_in_pps command) on a module that supports both, software broadcast suppression is still enabled even though the output of the show port command indicates that hardware suppression is enabled. The workaround is to disable software suppression using the set port broadcast mod_num/port_num 0 command and then reissuing the command to enable hardware suppression. This problem is resolved in software release 3.2(3). (CSCdk40580)
- If you have a device connected to a 48-port 10BaseT Telco module (WS-X5012) that is sending frames to a multicast MAC address configured as a permanent content-addressable memory (CAM) entry, the frames might be sent out blocked ports as well as forwarding ports. One workaround is to assign the port to a different VLAN, and then reassign the port to the original VLAN using the set vlan vlan_num mod_num/port_list command. Another workaround is to remove the permanent multicast CAM entry using the clear cam permanent vlan_num command. This problem is resolved in software release 3.2(3). (CSCdk44560)
- In some situations, spanning tree reconvergence might not be optimal after a failure when you configure parallel Fast EtherChannel trunks for VLAN load-balancing using the set spantree portvlanpri command. If one of the links in a channel fails (causing all VLAN traffic to pass over the remaining channel) and is later reestablished, spanning tree will converge but load-balancing does not occur. The second channel is placed in blocking mode. This problem is resolved in software release 3.2(3). (CSCdk40289)
These sections describe open and resolved caveats in supervisor engine software release 3.2(2):
Note For a description of caveats resolved in software release 3.2(2), see the "Resolved Caveats in Software Release 3.2(2)" section.
This section describes open caveats in software release 3.2(2).
- In some cases, ports on a 12-port, 10/100-Mbps Fast Ethernet module (WS-X5213A or WS-X5203) connected to ports on a 24-port, 10/100-Mbps Fast Ethernet module (WS-X5225R) might autonegotiate to half duplex rather than full duplex. To recover, specify a fixed port speed, or disable and reenable the port. (CSCdk08385)
- In some cases, when you access a Catalyst 5000 series switch containing a Supervisor Engine III module from a Windows 95/NT machine using Microsoft Telnet, some commands cannot be completed. (CSCdk18934)
- After prolonged SNMP usage, the Catalyst 5000 supervisor engine might lose communication with a module for some SNMP and CLI commands. To recover, reset the module. (CSCdk21580)
- In some cases after a switchover, Catalyst 5000 series 10/100-Mbps ports whose port speed is set to 100 Mbps and whose duplex is set to full duplex lose their duplex setting and are set to half duplex. As a workaround, disable and reenable the affected ports. (CSCdk32209)
Note For a description of open caveats in software release 3.2(2), see the "Open Caveats in Software Release 3.2(2)" section.
This section describes caveats resolved in software release 3.2(2).
- When a personal computer is connected to a 48-port, 10BaseT Ethernet module (WS-X5012) and is booted, the WS-X5012 ports show carrier-sense errors. This problem is resolved in software release 3.2(2). (CSCdj73609)
- Under heavy traffic conditions, ports 1-24 (or ports 25-48) of the 48-port, 10BaseT Ethernet module (WS-X5012) might lock up, with the transmit counters not incrementing while receive counters are incrementing. This problem is resolved in software release 3.2(2). (CSCdj82035)
- When using CiscoView to access a Catalyst 5000 series switch that has at least one ATM module installed, after several hours the switch might become unmanageable through Telnet or SNMP. This problem is resolved in software release 3.2(2). (CSCdj83053)
- If the sc0 interface is configured on VLAN N, but no other ports are configured in that VLAN, the Route Switch Module (RSM) VLAN N interface is down. This problem is resolved in software release 3.2(2). (CSCdj92353)
- Under certain conditions, a Catalyst 5000 series switch stops sending syslog output to the logging server. This problem is resolved in software release 3.2(2). (CSCdj93539)
- A Catalyst 5000 series switch containing a Supervisor Engine III module experiences an exception when an ATM OC-12 module comes online. This problem is resolved in software release 3.2(2). (CSCdk02347)
- In some cases, the Spanning-Tree Protocol does not resolve properly because the bridge relay function (BRF) spanning-tree state is not sent to the ATM Line Card (ALC) properly. This problem is resolved in software release 3.2(2). (CSCdk02425)
- On a Catalyst 5500 switch, RMON history causes the switch to reboot if the number of bucket samples is too large (for example, 40000). This problem is resolved in software release 3.2(2). (CSCdk02714)
- When both TACACS+ and local authentication are enabled on a Catalyst 5000 series switch, if TACACS+ denies you access to the switch, local authentication allows you access. This problem is resolved in software release 3.2(2). (CSCdk03266)
- In some cases, after power cycling a Catalyst 5500 switch with a Supervisor Engine III and an RSM installed, the RSM does not come up fully. This problem is resolved in software release 3.2(2). (CSCdk03377)
- In some cases, the link LEDs on some ports of the 10/100-Mbps Workgroup Fast Ethernet module (WS-X5224) are lit green even though no devices are connected to the ports. This problem is resolved in software release 3.2(2). (CSCdk04520)
- In some cases, ping commands directed across a trunk link fail. This problem is resolved in software release 3.2(2). (CSCdk04770)
- In some cases, when using a Token Ring VLAN as the management VLAN, after continually learning MAC addresses over several days, the Catalyst 5000 series switch might become unmanageable through Telnet or SNMP. This problem is resolved in software release 3.2(2). (CSCdk05195)
- In some cases, the switch password is displayed on the monitor after the Catalyst 5000 series switch is reset. This problem is resolved in software release 3.2(2). (CSCdk07486)
- During startup, a Catalyst 5000 series switch containing dual power supplies and a Supervisor Engine I or II module running software release 3.x might fail if the chassis trap is enabled and one of the power supplies changes state (on or off). This problem is resolved in software release 3.2(2). (CSCdk07566)
- On the 48-port, 10BaseT Ethernet module (WS-X5012) with no ports connected, if the spanning-tree portfast option is enabled on a port, and then the port is disabled and reenabled, the transmit broadcast and multicast counters increment. This problem is resolved in software release 3.2(2). (CSCdk07684)
- In some cases, moving a host from one secure Catalyst 5000 series port to another does not shut down the port. This problem is resolved in software release 3.2(2). (CSCdk09449)
- A Catalyst 5000 series switch running software release 3.1(2a) sends two traps when a rising or falling threshold is reached: the generic RMON trap and the enterprise-specific trap. The Enterprise-specific trap contains a truncated Organizational Unique Identifier (OID) for the variable being monitored. This problem is resolved in software release 3.2(2). (CSCdk10594)
- In some cases, the port speed of Token Ring module ports is not displayed in the Catalyst 5000 series configuration file. This problem is resolved in software release 3.2(2). (CSCdk10971)
- In some cases, when you enter commands that affect several ports at once, the Catalyst 5000 series switch does not execute all the commands completely. This problem is resolved in software release 3.2(2). (CSCdk12440)
- After the Catalyst 5000 series switch is reset, the VMPS reconfirmation interval is in seconds instead of minutes. This problem is resolved in software release 3.2(2). (CSCdk13301)
- In some cases, using TFTP to copy a configuration file to a Catalyst 5000 series switch generates an "Argument too long" error, and the command with the offending argument is not included in the copied configuration file. This problem is resolved in software release 3.2(2). (CSCdk13949)
- In some cases, you cannot remove a UGHD (up, gateway, host, dynamic) route from the Catalyst 5000 series switch IP routing table. This problem is resolved in software release 3.2(2). (CSCdk14130)
- In some cases, when using a Token Ring VLAN as the management VLAN, the Catalyst 5000 series switch might become unmanageable through Telnet or SNMP in the presence of continuous explorer frames. This problem is resolved in software release 3.2(2). (CSCdk14657)
- When using VTP with ATM Token Ring LANE in a Catalyst 5500 switch containing Token Ring switching modules, the communication across the ATM cloud might not be reestablished after the VLAN configuration is changed. This problem is resolved in software release 3.2(2). (CSCdk15966)
- In a Catalyst 5000 series switch that has VMPS enabled and is configured so that most of the MAC addresses are assigned to the fallback VLAN, after a significant period of time the system might become unmanageable. This problem is resolved in software release 3.2(2). (CSCdk20131)
- If you enable spanning-tree PortFast on a trunk-capable port that is not in trunk mode, it may take from 10-15 seconds for the Catalyst 5000 series switch to begin switching packets on that port after the link comes up. This problem is resolved in software release 3.2(2). (CSCdk21024)
- In some cases, on Catalyst 5000 series modules that support Fast EtherChannel, the port with the lowest port cost (the shortest path) is blocked. This problem is resolved in software release 3.2(2). (CSCdk22886)
- In certain configurations, an end station might be unable to communicate with an RSM. This problem is resolved in software release 3.2(2). (CSCdk22895)
These sections describe open and resolved caveats in supervisor engine software release 3.2(1b):
This section describes open caveats in software release 3.2(1).
- Under certain conditions, a Catalyst 5000 series switch stops sending syslog output to the logging server. The workaround is to reset the switch. (CSCdj93539)
- When a personal computer is connected to a 48-port, 10BaseT Ethernet module (WS-X5012) and is booted, the WS-X5012 port shows carrier sense errors. These can safely be ignored. (CSCdj73609)
- If the sc0 interface is configured on VLAN N, but no other ports are configured in that VLAN, the RSM VLAN N interface is down. The workaround is to enter set rsmautostate disable at the console prompt. (CSCdj92353)
- If you enable spanning-tree PortFast on a trunk-capable port that is not in trunk mode, it may take from 10-15 seconds for the Catalyst 5000 series switch to begin switching packets on that port after the link comes up. (CSCdk21024)
This section describes caveats resolved in software release 3.2(1b).
- Under certain conditions, MAC and port counters on the Token Ring module are not reset in response to the clear counters command. This problem is resolved in software release 3.2(1). (CSCdj75479)
- If an ATM module is the only other port in a VLAN, the RSM interface might be down. The workaround is to enter set rsmautostate disable at the console prompt. This problem is resolved in software release 3.2(1). (CSCdj81147)
- In software release 3.1(2), the Token Ring RMON tables, tokenRingPStatsTable and tokenRingMLStatsTable, are not supported. This problem is resolved in software release 3.2(1). (CSCdj77337)
- Under certain conditions, there is a delay before the local VLAN table is updated after a port becomes trunk. During this period, if VTP learns a new VLAN, it will not be able to add it to the trunk port. This problem is resolved in software release 3.2(1). (CSCdj78188)
- When both TACACS+ and local login authentication are enabled on a Catalyst 5000 series switch, and when the TCP connection to the TACACS+ server is broken, the login will not work once you close the session. This problem is resolved in software release 3.2(1). (CSCdj78159)
- Under certain conditions, the Supervisor Engine III resets when you enter the set rsmauto command through a Telnet connection. This problem is resolved in software release 3.2(1). (CSCdj85120)
- Under certain conditions, when you enter the show station ordertable command, the message "Time out while communicating to module (x)" is displayed. This problem is resolved in software release 3.2(1). (CSCdj68373)
- Under certain conditions, the SNMP counters are not accurate for Fast EtherChannel. This problem is resolved in software release 3.2(1). (CSCdj86668)
- Under certain conditions, no reply is sent for an SNMP MIB query. This problem is resolved in software release 3.2(1)—in most cases, a reply is sent in less than 10 seconds. (CSCdj82002)
- On a Catalyst 5500 with a Supervisor Engine III, you cannot use SPAN if the destination port is not on the same bus as the source port. This problem is resolved in software release 3.2(1). (CSCdj86533)
- When there is a port duplex mismatch, 24 ports of the 48-port, 10BaseT Ethernet module (WS-X5012) might spontaneously stop transmitting traffic. This problem is resolved in software release 3.2(1). (CSCdj75461)
- Under heavily loaded conditions, the 48-port, 10BaseT Ethernet module (WS-X5012) might have a lot of cyclic redundancy check (CRC) errors in any other outbound port. This problem is resolved in software release 3.2(1). (CSCdj58933)
- When spanning-tree is disabled, after you disable SPAN, the destination port is not able to be used for switching. This problem is resolved in software release 3.2(1). (CSCdj87151)
- If you use CiscoView to set a TACACS+ key, and you enter the show configure command, a Catalyst 5000 series switch displays a "Display Truncated" message. This problem is resolved in software release 3.2(1). (CSCdj62208)
- If you have upgraded to software release 3.1(2) from software release 2.4 or earlier, the syslog severity of PAgP is not set to the default of 5 (notification) automatically. Instead, it is set to 2 (critical). In software release 3.2(1), this is not an issue. (CSCdj79494)
- The Catalyst 5000 series switch can hang or experience a reset if it receives a Token Ring frame larger than 1500 bytes in end-station mode. This problem is resolved in software release 3.2(1a). (CSCdj80899)
- In some cases, the Catalyst 5000 series switch does not send GS Queries to the host and, as a result, the host port is not deleted and CGMP leave processing does not work. This problem is resolved in software release 3.2(1a). (CSCdk00919)
- With newer versions of the Netcom AST application, you may 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 resolved in software release 3.2(1b). (CSCdk00502)
These sections describe open and resolved caveats in supervisor engine software release 3.1(2a):
Note For a description of caveats resolved in software release 3.1(2a), see the "Resolved Caveats in Software Release 3.1(2a)" section.
This section describes open caveats in software release 3.1(2a).
- When downgrading the supervisor engine software from release 4.3 to release 3.1(2a), 3.1(2), or 3.1(1), a minor hardware error (loopback failure) might occur. Power cycle the switch after downgrading to resolve the problem. (CSCdk67913)
- If you have upgraded to software release 3.1(2) from software release 2.4 or earlier, the syslog severity of PAgP is not set to the default of 5 (notification) automatically. Instead it is set to 2 (critical). To fix this problem, enter set logging level pagp 5 default at the console prompt. (CSCdj79494)
- Under certain conditions, MAC and port counters on the Token Ring module are not reset in response to the clear counters command. (CSCdj75479)
- If an ATM module is the only other port in a VLAN, the RSM interface might be down. The workaround is to enter set rsmautostate disable at the console prompt. (CSCdj81147)
- Token Ring RMON tables, tokenRingPStatsTable, and tokenRingMLStatsTable are not supported. (CSCdj77337)
Note For a description of open caveats in software release 3.1(2a), see the "Open Caveats in Software Release 3.1(2a)" section.
This section describes caveats resolved in software release 3.1(2a).
If you attempt to Telnet into any "non-responsive" device from a Catalyst 5000 series switch running supervisor engine software release 3.1(2) and type in any character sequence other than Ctrl-C, the switch might reset. This problem is resolved in software release 3.1(2a). (CSCdj82467)
These sections describe open and resolved caveats in supervisor engine software release 3.1(2):
Note For a description of caveats resolved in software release 3.1(2), see the "Resolved Caveats in Software Release 3.1(2)" section.
This section describes open caveats in software release 3.1(2).
- When downgrading the supervisor engine software from release 4.3 to release 3.1(2a), 3.1(2), or 3.1(1), a minor hardware error (loopback failure) might occur. Power cycle the switch after downgrading to resolve the problem. (CSCdk67913)
- If you have upgraded to software release 3.1(2) from software release 2.4 or earlier, the syslog severity of PAgP is not set to the default of 5 (notification) automatically. Instead it is set to 2 (critical). To fix this problem, enter set logging level pagp 5 default at the console prompt. (CSCdj79494)
- Under certain conditions, MAC and port counters on the Token Ring module are not reset in response to the clear counters command. (CSCdj75479)
- If an ATM module is the only other port in a VLAN, the RSM interface might be down. The workaround is to enter set rsmautostate disable at the console prompt. (CSCdj81147)
- Token Ring RMON tables, tokenRingPStatsTable, and tokenRingMLStatsTable are not supported. (CSCdj77337)
Note For a description of open caveats in software release 3.1(2), see the "Open Caveats in Software Release 3.1(2)" section.
This section describes caveats resolved in software release 3.1(2).
- In software release 3.1(1), when you reload an RSM, there can be a long delay before the RSM VLAN interfaces become active after the reload. This problem is resolved in software release 3.1(2). (CSCdj77892)
- The RSM VLAN interface fails to remain line protocol "up" even though there is still an FDDI interface participating in that VLAN. This problem is resolved in software release 3.1(2). (CSCdj75778)
- If you move a port from one VLAN to another when its port security is enabled, the port does not work properly. This problem is resolved in software release 3.1(2). (CSCdj78498)
- Under certain conditions, unidirectional links (which have either the transmission wire or the receiver wire connected, a condition usually found in fiber links) might cause the channel to be unchanneled, and these links are only detected if channel mode is set to desirable. This problem is resolved in software release 3.1(2). (CSCdj74709)
- Under certain conditions, incoming BRF BPDUs are not flooded to the corresponding TrCRF. This problem is resolved in software release 3.1(2). (CSCdj77863)
- Under certain conditions, configuring the IEEE spanning tree multicast address for a TrBRF VLAN causes a broadcast storm. This problem is resolved in software release 3.1(2). (CSCdj68494)
- In some cases, trying to set MIB object CISCO-STACK-MIB/monitorDestinationModule to a nonexistent module number (for example setting it to 11 in a 5 slot chassis) might cause the switch to reset. This problem is resolved in software release 3.1(2). (CSCdj70018)
- Setting the ciscoFlashCopyCommand MIB object to copyFromFlash(3) does not work. This problem is resolved in software release 3.1(2). (CSCdj70084)
- At random intervals, a group on the WS-X5223 (24-port group switching module) indicates that all ports within the group are in a "notconnect" state even though clients are connected and were previously working. This problem is resolved in software release 3.1(2). (CSCdj51141)
- When the first two ports in an EBC group are connected to one device and the last two in the group are connected to another and they are supposed to form two 2-port channels, there is a chance that one of them will not appear to be channeling, although both channels are actually formed and have spanning-tree enabled. This problem is resolved in software release 3.1(2). (CSCdj65082)
- In some cases, performing an SNMP GET-NEXT operation on multiple MIB objects on an empty table causes a timeout on a network management application. This problem is resolved in software release 3.1(2). (CSCdj52786)
- One or more ports on the WS-X5011 become disabled and unable to forward traffic even though the LED is on. This problem is resolved in software release 3.1(2). (CSCdj55124)
- When there are no active ports for a VLAN, other than the RSM, the supervisor engine should disable the VLAN interface on the RSM, so the RSM will not advertise a route to a dead-end subnet. This problem is resolved in software release 3.1(2). (CSCdj37830)
- A non-supervisor port on a Catalyst 2926 switch, or a port on a WS-X5224 module connected to an end station at a fixed speed using a UTP cable 50 meters or longer, displays "faulty" port status after it is reset. This problem is resolved in software release 3.1(2). (CSCdj72820)
- Under certain conditions, when using Telnet to connect to a switch running TACACS+, the switch appends an extra character to the password before it sends to the TACACS+ server for authentication. This problem is resolved in software release 3.1(2). (CSCdj48912)
- When there are two 2-port channels formed on the same EBC and one port goes down, the software mistakenly groups the rest of the ports in a bundle. This problem is resolved in software release 3.1(2). (CSCdj74145)
- Under certain PC configurations, the PC might not be unable to connect to an IPX server. This problem is resolved in software release 3.1(2). (CSCdj68668)
- With CGMP enabled on the Catalyst 5000 switch, reloading RSM through the RSM console or dynamically removing the RSM module and hot inserting it can cause duplicate multicast traffic on a single port. This problem is resolved in software release 3.1(2). (CSCdj76988)
These sections describe open and resolved caveats in supervisor engine software release 3.1(1):
Note For a description of caveats resolved in software release 3.1(1), see the "Resolved Caveats in Software Release 3.1(1)" section.
This section describes open caveats in software release 3.1(1).
- When downgrading the supervisor engine software from release 4.3 to release 3.1(2a), 3.1(2), or 3.1(1), a minor hardware error (loopback failure) might occur. Power cycle the switch after downgrading to resolve the problem. (CSCdk67913)
- Under certain PC configurations, it is possible for the PC to be unable to connect to an Internet Packet Exchange (IPX) server. (CSCdj68668)
- Token Ring RMON tables, tokenRingPStatsTable and tokenRingMLStatsTable, are not supported. (CSCdj77337)
- With supervisor engine 3.1(1) software, when an RSM is reloaded, there can be a long delay before the RSM VLAN interfaces become active after the reload. The length of the delay depends on the number of VLAN interfaces that were active on the RSM before the reload. The delay is about three seconds for each previously active VLAN, so an RSM with a large number of VLAN interfaces can experience a several minute delay before its VLAN interfaces become active. (CSCdj75778, CSCdj77892)
- In some cases, MIB objects that access a Catalyst 5000 series ATM module, might be lost. To recover, reset the ATM module. (CSCdj36835)
- In some cases, performing an SNMP GET-NEXT operation on multiple MIB objects on an empty LANE table causes a timeout on a network management application. (CSCdj52786)
- In some cases, a switch has invalid information for a Fast EtherChannel interface in ifTable, ifxTable, and ifStackTable. (CSCdj69259)
- Under certain conditions, the message "Cannot open device after interrupting autoboot with send brk" is displayed. If this message is displayed in ROMMON mode, the workaround is to reset the switch. (CSCdj53388)
- In some cases, the destination port still sees monitored traffic after you disable SPAN. The workaround is to disable and then reenable the port. (CSCdj67568)
- Traps defined in CISCO-FLASH-MIB are not supported. (CSCdj70312)
- Under certain conditions, image files are not copied to the TFTP server. (CSCdj70084)
- Trying to set MIB object CISCO-STACK-MIB/monitorDestinationModule to a nonexistent module number (for example, setting it to 11 in a 5-slot chassis) might reset the switch. Do not set monitorDestinationModule to an invalid module number. (CSCdj70018)
- When the VTP domain does not have Domain Name configured, you cannot set the managementDomainPruningState properly if the SNMP set request contains both managementDomainName and managementDomainPruningState in the same SNMP PDU. (CSCdj69411)
- In certain PC configurations, the PC might be unable to connect to an 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 a Windows 95-based PC using 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.
- Under certain conditions, Fast EtherChannel can fail to channel the ports together. This can occur when a four-port group is split into two channels connected to different switches and the ports are configured with auto or desirable channel state. The workaround is to disable and reenable the ports that failed to channel. (CSCdj65082)
- In the Catalyst 5000 Series Command Reference publication, there are two corrections to the set span command. The command usage sentence should read:
- Use the set span command to enable or disable SPAN, and to set up the port and VLAN analyzer.
- The Syntax Description table should read:
enable
| Keyword that enables SPAN.
|
disable
| Keyword that disables SPAN.
|
src_mod
| Monitored module (source).
|
src_ports
| Monitored port(s) (source).
|
src_vlan
| Monitored VLAN (source).
|
dest_mod
| Monitoring module (destination).
|
dest_port
| Monitoring port (destination).
|
rx
| (Optional) Keyword that specifies that information received at the source is monitored.
|
tx
| (Optional) Keyword that specifies that information transmitted from the source is monitored.
|
both
| (Optional) Keyword that specifies that information both transmitted from the source and received at the source is monitored.
|
- In the Catalyst 5000 Series Command Reference publication, there is one correction to the show version command. The display output for this command has changed. The new Example should read:
Console> (enable) show version
WS-C5000 Software, Version McpSW: 2.3(120) NmpSW: 2.3(120)
Copyright (c) 1995,1996 by Cisco Systems
NMP S/W compiled on May 12 1997, 06:50:40
MCP S/W compiled on May 12 1997, 07:06:41
System Bootstrap Version: 2.2(2)
Hardware Version: 2.0 Model: WS-C5000 Serial #: 004993621
Module Ports Model Serial # Hw Fw Fw1 Sw
------ ----- ---------- --------- ------ ------- ------- --------------------
1 2 WS-X5009 004993621 2.0 2.2(2) 2.2(1) 2.3(120)
2 12 WS-X5213 003630659 1.2 1.4 2.3(120)
3 2 WS-X5101 003389357 1.1 1.1 1.3 2.2(208)
4 2 WS-X5101 002615824 1.0 1.146 1.3 2.1(704)
5 2 WS-X5158 004348990 1.0 1.3 1.3 3.2(3)
DRAM FLASH NVRAM
Module Total Used Free Total Used Free Total Used Free
------ ------- ------ ------ ----- ---- ---- ----- ---- ----
2 32640K 11605K 21035K 8192K 8119K 73K 512K 138K 374K
Note For a description of open caveats in software release 3.1(1), see the "Open Caveats in Software Release 3.1(1)" section.
This section describes caveats resolved in software release 3.1(1).
- If you set an RMON alarm on a non-RMON MIB object, the set is accepted but the alarm never goes off. Software releases up to and including release 2.4 do not support alarms on a non-RMON MIB object. This feature is now supported in software release 3.1(1). (CSCdj38267)
- The Threshold Manager application cannot be used to delete RMON events from the Catalyst 5000 switch. This problem is resolved in software release 3.1(1). (CSCdj19603)
- A sustained traffic load consisting of small packets (for example, 64 bytes) can cause the Catalyst 5000 RSM to stop receiving packets. This problem is resolved in software release 3.1(1). (CSCdj21750)
- The Network Time Protocol (NTP) client does not sync up with a Sun Microsystems NTP server. This problem is resolved in software release 3.1(1). (CSCdj57267)
- On power-up, some Supervisor Engine I modules with early hardware versions fail the Enhanced Address Recognition Logic (EARL) trap test, preventing the modules in the switch from coming online. This problem is resolved in software release 3.1(1). (CSCdj57439)
- The Catalyst 5000 series switches are vulnerable to the LAND.C Denial of Service Attack program. This problem has been resolved in Catalyst 5000 series release 3.1. For additional information on this issue, see the following URL:
http://www.cisco.com/warp/public/770/land-pub.shtml#catalyst
- The Catalyst 5500 switch does not send coldstart traps to all trap receivers configured. This problem is resolved in software release 3.1(1). (CSCdj54907)
- The set cam permanent command is not additive. This problem is resolved in software release 3.1(1). (CSCdj61870)
- In some cases, VMPS might fail to assign a MAC address to a VLAN. This problem is resolved in software release 3.1(1). (CSCdj64167)
- In some cases, when using a faulty cable, the Fast EtherChannel feature might fail to switch over to another functional port in the bundle. This problem is resolved in software release 3.1(1). (CSCdj25111)
- Under certain conditions, adding a VLAN might reset the Catalyst 5000 series switch. This problem is resolved in software release 3.1(1). (CSCdk22373)
- If 60 or more varbinds are included in a single SNMP request, an exception might occur causing the switch to reset. This problem is resolved in software release 3.1(1). (CSCdk61750)
These sections describe open and resolved caveats in supervisor engine software release 2.4(5):
Note For a description of caveats resolved in software release 2.4(5), see the "Resolved Caveats in Software Release 2.4(5)" section.
There are no known caveats in software release 2.4(5).
Note For a description of open caveats in software release 2.4(5), see the "Open Caveats in Software Release 2.4(5)" section.
This section describes caveats resolved in software release 2.4(5).
- The RSM VLAN interface fails to remain line protocol "up" even though there is still an FDDI interface participating in that VLAN. This problem is resolved in software release 2.4(5). (CSCdj75778)
- Under certain PC configurations, the PC might not be unable to connect to an IPX server. This problem is resolved in software release 2.4(5). (CSCdj68668)
- When there is a port duplex mismatch, 24 ports of the WS-X5012 (48-port 10BaseT) switch module might spontaneously stop transmitting traffic. This problem is resolved in software release 2.4(5). (CSCdj75461)
- Under heavily loaded conditions, the WS-X5012 (48-port 10BaseT) switch module may have a lot of CRC errors in any other outbound port. This problem is resolved in software release 2.4(5). (CSCdj58933)
- With CGMP enabled on the Catalyst 5000 switch, reloading RSM through the RSM console or dynamically removing the RSM module and hot inserting it can cause duplicate multicast traffic on a single port. This problem is resolved in software release 2.4(5). (CSCdj76988)
- With newer versions of the Netcom AST application, you may 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 resolved in software release 2.4(5). (CSCdk00502)
- Under certain conditions, a Catalyst 5000 series switch stops sending syslog output to the logging server. This problem is resolved in software release 2.4(5). (CSCdj93539)
- If you close a Telnet session while the Catalyst 5000 series switch is printing output through that session, the switch may experience a memory corruption. This problem is resolved in software release 2.4(5). (CSCdj87441)
- In some cases, if you have more than one RSM installed in a Catalyst 5000 series chassis and you reset the system, some ports on certain modules may fail power-on diagnostics. This problem is resolved in software release 2.4(5). (CSCdj93929)
- When both TACACS and local authentication are enabled on a Catalyst 5000 series switch, if TACACS denies you access to the switch, local authentication allows you access. This problem is resolved in software release 2.4(5). (CSCdk03266)
- In some cases when an ATM module is installed in a Catalyst 5000 series switch, the CAM table shows a learned MAC address on an incorrect module and port number. This problem is resolved in software release 2.4(5). (CSCdj83408)
These sections describe open and resolved caveats in supervisor engine software release 2.4(4):
Note For a description of caveats resolved in software release 2.4(4), see the "Resolved Caveats in Software Release 2.4(4)" section.
This section describes open caveats in software release 2.4(4).
- In some cases, when using a faulty cable, the Fast EtherChannel feature may fail to switch over to another functional port in the bundle. (CSCdj25111)
- If you are using MII connectors, the Fast EtherChannel feature does not work on the 100BaseTX, RJ-45 supervisor engine module (WS-X5509). (CSCdj36182)
- Supervisor Engine I with hardware revision 1.3 does not support software version 2.4(2). Modules do not come online. (CSCdj57439)
- At random intervals a group on the WS-X5223 (24-port Group Switching Module) for the Catalyst 5000 will go into a hung state for unknown reasons. The show port command will indicate that all ports within the group are in a "notconnect" state even though clients are connected and were previously working. (CSCdj51141)
- To verify that this is the issue, do the following:
- Use the command reset module mod_num, where mod_num is the number of the affected module.
- Use the following SNMP command:
- snmpset -c private@5/17 10.20.1.233.1.3.6.1.2.1.22.1.1.4.0 integer 2
- In some cases, performing an SNMP GET-NEXT operation on multiple MIB objects on an empty table causes a timeout on a network management application. (CSCdj52786)
- If you set an RMON alarm on a non-RMON MIB object, the set is accepted but the alarm will never go off. Software releases up to and including release 2.4 do not support alarms on non-RMON MIB object. (CSCdj38267)
- In some cases, when a Catalyst 5000 series switch resets and logs a switching-bus timeout, the exception date may not appear in the system log, and the version information may be incorrect. (CSCdj52946)
- Under certain conditions, the RSM VLAN interface fails to maintain line protocol "up" even though there is still an FDDI interface participating in that VLAN. This can occur when the native VLAN on the FDDI interface is set to a VLAN to which no other Catalyst 5000 ports are assigned (it is the only other port in the VLAN besides the RSM). The RSM will fail to see line protocol changes on the FDDI port (including the transition from down to up at boot time) and will consequently ignore the FDDI port for line protocol determination for the corresponding RSM VLAN interface. To recover, disable the RSM line protocol feature (using the set rsmautostate disable command) and reset the NMP. (CSCdj75778)
Note For a description of open caveats in software release 2.4(4), see the "Open Caveats in Software Release 2.4(4)" section.
This section describes caveats resolved in software release 2.4(4).
- A non-supervisor port on a Catalyst 2926, or a port on a WS-X5224 module connected to an end station at a fixed speed using a UTP cable 50 meters or longer, will display "faulty" port status after it is reset. This problem is resolved in software release 2.4(4). (CSCdj72820)
- In some cases, performing an SNMP GET-NEXT operation on multiple MIB objects on empty table causes a timeout on a network management application This problem is resolved in software release 2.4(4). (CSCdj52786)
- In 2.4(3) and pre-release, the RMON agent does not send the RMON alarm trap to the trap receivers configured in sysTrapReceiverTable if the corresponding event entry is not configured from TrafficDirector application. This problem is resolved in software release 2.4(4). (CSCdj69545)
- The functionality of VMPS in 2.4(3) was unstable. This problem is resolved in software release 2.4(4). (CSCdj69321)
- Under certain conditions, using the config net command sends an "argument too long" message. This problem is resolved in software release 2.4(4). (CSCdj70215)
- The Catalyst 5000 series switches are vulnerable to the LAND.C Denial of Service Attack program. This problem has been resolved in Catalyst 5000 series release 2.4(4). (CSCdj62723)
These sections describe open and resolved caveats in supervisor engine software release 2.4(3):
Note For a description of caveats resolved in software release 2.4(3), see the "Resolved Caveats in Software Release 2.4(3)" section.
This section describes open caveats in software release 2.4(3).
- In some cases, when using a faulty cable, the Fast EtherChannel feature might fail to switch over to another functional port in the bundle. (CSCdj25111)
- In some cases, MIB objects that access a Catalyst 5000 series ATM module might be lost. To recover, reset the ATM module. (CSCdj36835)
- If you set an RMON alarm on a non-RMON MIB object, the set is accepted but the alarm never goes off. Software releases up to and including release 2.4 do not support alarms on a non-RMON MIB object. (CSCdj38267)
- In some cases, when a Catalyst 5000 series switch resets and logs a switching-bus timeout, the exception date might not appear in the system log, and the version information might be incorrect. (CSCdj52946)
- In some cases, performing an SNMP GET-NEXT operation on multiple MIB objects on an empty LANE table causes a timeout on a network management application. (CSCdj52786)
Note For a description of open caveats in software release 2.4(3), see the "Open Caveats in Software Release 2.4(3)" section.
This section describes caveats resolved in software release 2.4(3).
- In some cases, after a switchover to the standby supervisor engine in a Catalyst 5500 switch, the supervisor MAC addresses might change. This problem is resolved in software release 2.4(3). (CSCdj40936)
- An SNMP set request with multiple set varbinds to an ATM module does not work and might cause the ATM module to reset if it is running ATM software release 3.2(4) or earlier. This problem is resolved in software release 2.4(3). (CSCdj33860)
- If all switches in a VTP domain do not have identical VTP passwords, excessive VTP messages might be generated. This problem is resolved in software release 2.4(3). (CSCdj37167)
- If you are using a full-duplex port in a 48-port, 10BaseT Ethernet module (WS-X5012) as the destination SPAN port and then you disable SPAN, the port incorrectly stays in blocking mode. This problem is resolved in software release 2.4(3). (CSCdj40560)
- In some cases, when you set the SPAN feature from a source port to a destination port that is not yet connected to an analyzer, and then you connect the destination port, the SPAN feature might not operate correctly. This problem is resolved in software release 2.4(3). (CSCdj44407)
- In some cases, adding a port via a Telnet session to a VLAN that does not exist might reset the switch. This problem is resolved in software release 2.4(3). (CSCdj44840)
- If you configure bridge domains on a router connected to a Catalyst 5000 series switch, loops might occur on the Catalyst 5000 series switch. This problem is resolved in software release 2.4(3). (CSCdj47798)
- ATM-related CAM entries are missing from the bridge table. This problem is resolved in software release 2.4(3). (CSCdj47859)
- In previous software releases 2.2(1) through 2.4(2), some configuration information might be lost after power cycling the switch or after redundancy switchover occurs. This problem is resolved in software release 2.4(3). (CSCdj45423)
- The SPAN functionality does not work in software release 2.4(2) with WS-X5224 and WS-X5213A modules with speed set to auto. This problem is resolved in software release 2.4(3). (CSCdj50595)
- The output of the show configuration and write terminal commands contains a line that might interfere with some SMTP implementations, if the command output is included in an e-mail message. This problem is resolved in software release 2.4(3). (CSCdj49834)
- In some cases, transmitting a packet on a 48-port, 10BaseT Ethernet module (WS-X5012) might cause the dot3StatsSQETestErrors counter to increment. This problem is resolved in software release 2.4(3). (CSCdj52900)
- In some cases, if you press Ctrl-C during a show log display, the switch might reset. This problem is resolved in software release 2.4(3). (CSCdj54864)
- In some cases, during download of a VMPS file, the switch might reset. This problem is resolved in software release 2.4(3). (CSCdj53300)
- The ATM module on a Catalyst 5000 series switch transmits packets on the wrong VC. This problem is resolved in software release 2.4(3). (CSCdj48920)
These sections describe open and resolved caveats in supervisor engine software release 2.4(2):
Note For a description of caveats resolved in software release 2.4(2), see the "Resolved Caveats in Software Release 2.4(2)" section.
This section describes open caveats in software release 2.4(2).
- In some cases, adding a port via a Telnet session to a VLAN that does not exist might cause the switch to reset. (CSCdj44840)
- SNMP does not return ifXTable values for ATM modules. (CSCdj34775)
- In some cases, when using a faulty cable, the Fast EtherChannel feature might fail to switch over to another functional port in the bundle. (CSCdj25111)
- If you are using MII connectors, the Fast EtherChannel feature does not work on the 100BaseTX, RJ-45 supervisor engine module (WS-X5509). (CSCdj36182)
- An SNMP set request with multiple set varbinds to an ATM module does not work and might cause the ATM module to reset if it is running ATM software release 3.2(4) or earlier. (CSCdj33860)
- In some cases, ifTable loses ATM objects. (CSCdj36835)
- If you set an RMON alarm on a non-RMON MIB object, the set is accepted but the alarm never goes off. Software release 2.4(2) does not support alarms on a non-RMON MIB object. (CSCdj38267)
- If all switches in a VTP domain do not have identical VTP passwords, excessive VTP messages might be generated. As a workaround, make sure that all VTP passwords are identical across all switches in the VTP domain. (CSCdj37167)
- In some cases, after a switchover to the standby supervisor engine in a Catalyst 5500 switch, the supervisor MAC addresses might change. (CSCdj40936)
- If you are using a full-duplex port in a 48-port, 10BaseT Ethernet module (WS-X5012) as the destination SPAN port and then you disable SPAN, the port incorrectly stays in blocking mode. To recover, disable and reenable the port. (CSCdj40560)
Note For a description of open caveats in software release 2.4(2), see the "Open Caveats in Software Release 2.4(2)" section.
This section describes caveats resolved in software release 2.4(2).
- On a Catalyst 2926 series switch running software release 2.4(1), spurious CRC or frame check sequence (FCS) errors might appear in the switch counters while the 10/100-Mbps autosensing ports equalize to either 10 Mbps or 100 Mbps. These errors do not increase after the ports equalize to either 10 Mbps or 100 Mbps. This problem is resolved in software release 2.4(2). (CSCdj38146)
- The Catalyst 5500 DC power supply type (WS-C5568) is not displayed properly by the show system command. This problem is resolved in software release 2.4(2). (CSCdj37964)
- In some cases, you cannot disable the SPAN feature on a Catalyst 5000 series switch. This problem is resolved in software release 2.4(2). (CSCdj37083)
- When changing port speeds by entering the set port speed command, the link goes down temporarily. This problem is resolved in software release 2.4(2). (CSCdj37394)
- When you configure a port as a nontrunk, the linkfail counter does not increment when you disconnect and reconnect the port several times. This problem is resolved in software release 2.4(2). (CSCdj33547)
- If you enable the modem control lines on the console port by entering the set system modem enable command when a modem is not connected to the console, random characters might display on the terminal attached to the console port. This problem is resolved in software release 2.4(2). (CSCdj37043)
- When a link fails on a user-configured router port that has the portfast feature enabled, and the link is then reestablished, the port is not added back to the existing list of multicast entries. This problem is resolved in software release 2.4(2). (CSCdj39020)
- In rare cases, while trying to set a management VLAN you might see this error message:
Interface sc0 vlan set failed.
- This problem is resolved in software release 2.4(2). (CSCdj40412)
These sections describe open and resolved caveats in supervisor engine software release 2.4(1):
Note For a description of caveats resolved in software release 2.4(1), see the "Resolved Caveats in Software Release 2.4(1)" section.
This section describes open caveats in software release 2.4(1).
- SNMP does not return ifXTable values for ATM modules. (CSCdj34775)
- In some cases, when using a faulty cable, the Fast EtherChannel feature might fail to switch over to another functional port in the bundle. (CSCdj25111)
- If you are using MII connectors, the Fast EtherChannel feature does not work on the 100BaseTX, RJ-45 supervisor engine module (WS-X5509). (CSCdj36182)
- If you enable the modem control lines on the console port by entering the set system modem enable command when a modem is not connected to the console, random characters might display on the terminal attached to the console port. As a workaround, disable the modem by entering the set system modem disable command, and then reset the system. (CSCdj37043)
- An SNMP set request and multiple set varbinds cause the ATM module to reset. (CSCdj33860)
- On a Catalyst 2926 series switch running software release 2.4(1), spurious CRC or FCS errors might appear in the switch counters while the 10/100-Mbps autosensing ports are equalizing to either 10 or 100 Mbps. These errors do not increase after the ports equalize to either 10 or 100 Mbps. (CSCdj38146)
- If you set an RMON alarm on a non-RMON MIB object, the set is accepted but the alarm never goes off. Software release 2.4(2) does not support alarms on a non-RMON MIB object. (CSCdj38267)
- If all switches in a VTP domain do not have identical VTP passwords, excessive VTP messages might be generated. As a workaround, make sure that all VTP passwords are identical across all switches in the VTP domain. (CSCdj37167)
- In some cases, after a switchover to the standby supervisor engine in a Catalyst 5500 switch, the supervisor MAC addresses might change. (CSCdj40936)
- If you are using a full-duplex port in a 48-port, 10BaseT Ethernet module (WS-X5012) as the destination SPAN port and then you disable SPAN, the port incorrectly stays in blocking mode. To recover, disable and reenable the port. (CSCdj40560)
Note For a description of open caveats in software release 2.4(1), see the "Open Caveats in Software Release 2.4(1)" section.
This section describes caveats resolved in software release 2.4(1).
- In some cases, if you upload/download software images through SNMP by entering a host name instead of an IP address, the SNMP agent might return a status of "In Progress" for the "tftpResult" MIB object indefinitely, which might prevent you from using SNMP to perform further uploads/downloads. This problem is resolved in software release 2.4(1). (CSCdj24275)
- In some cases, enabling a port immediately after it has been shut down by the port security feature can result in a temporary loss of system memory. This problem is resolved in software release 2.4(1). (CSCdj24844)
- In some cases, the broadcast suppression rate might vary from the set rate, depending on the size and transmission rate of the packets. This problem is resolved in software release 2.4(1). (CSCdj25623)
- In some cases, when continuous multicast packets are received on a port that has the port security feature enabled, the port security feature might stop an active communication process. This problem is resolved in software release 2.4(1). (CSCdj22723)
- In a Catalyst 5500 switch with redundant Supervisor Engine II modules, if you change the time zone offset (by entering the set timezone command), the correct time might not be stored on the secondary Supervisor Engine II module, which can cause an invalid time value to be reported each time there is a switchover from one Supervisor Engine II module to the other. This problem is resolved in software release 2.4(1). (CSCdj17407)
- In some instances, Address Resolution Protocol (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 resolved in software release 2.4(1). (CSCdj12715)
- In some cases, moving a link connection from a dynamic port on one Catalyst 5000 series switch to a dynamic port on another switch across an ATM cloud might fail to assign a VLAN until the LE-ARP and CAM entries age out. This problem is resolved in software release 2.4(1). (CSCdj26287)
- In some cases, CAM entries are not purged immediately in the WS-X5020 group switching Ethernet module. This problem is resolved in software release 2.4(1). (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 resolved in software release 2.4(1). (CSCdj26896)
- When using the software broadcast suppression feature, only broadcast packets (with a MAC address of FFFFFFFFFFFF) are counted for triggering the suppression; multicasts are not counted for triggering the suppression. This problem is resolved in software release 2.4(1). (CSCdj27026)
- In some cases, the WS-X5010 Ethernet switching module (10BaseT, 24-port, Telco) fails to come online when the supervisor engine module is in boot mode and has a 1.1 boot ROM. This problem is resolved in software release 2.4(1). (CSCdj31100)
- In some cases, a SPAN destination port shows traffic from a previously configured VLAN as well as traffic from the currently configured VLAN. This problem is resolved in software release 2.4(1). (CSCdj25517)
- In some cases, packets leak through a previously disabled dynamic port after the module containing the disabled port is reset. This problem is resolved in software release 2.4(1). (CSCdj33083)
- In some cases, when you enable both TACACS and local authentication on a Catalyst 5000 series switch, if TACACS denies login access, local authentication authenticates the login. This problem is resolved in software release 2.4(1). (CSCdj32657)
- The WS-X5213A 10/100-Mbps Fast Ethernet switching module might fail to reinitialize an autonegotiating port after a fixed-speed device connected to the port is rebooted or power-cycled. This problem is resolved in software release 2.4(1). (CSCdj29827)
- Under certain conditions, when two Catalyst 5000 series switches in trunking mode are connected using external Media Independent Interface (MII) transceivers and you reset one of the switches, the trunk might take up to two minutes to reestablish. This problem is resolved in software release 2.4(1). (CSCdj27918)
- If you enter the set system modem enable command and reboot the Catalyst 5000 series switch, the system continually resets until you plug a terminal or modem into the CONSOLE port. This problem is resolved in software release 2.4(1). (CSCdi87786)
- In some cases, the MIB objects for the multicast router ports are not being updated appropriately. This problem is resolved in software release 2.4(1). (CSCdj36333)
- The 48-port, 10BaseT Ethernet module (WS-X5012) increments the Rcv-Err and In-Lost counters for runt errors, CRC errors, and alignment errors. This problem is resolved in software release 2.4(1). (CSCdj29491)
- Under certain conditions, removing and reinserting some Ethernet modules repeatedly might cause a switching-bus timeout. This problem is resolved in software release 2.4(1). (CSCdj29969)
- If you reset an FDDI module that has spanning-tree disabled, the FDDI module might stop switching packets. This problem is resolved in software release 2.4(1). (CSCdj34400)
- If you close a Telnet session repeatedly while the show config command is running, the Catalyst 5000 series switch might lose some memory (clusters). This problem is resolved in software release 2.4(1). (CSCdj29687)
- If you connect a multicast router to any segment other than the first segment of a repeater module, IP multicast traffic for that segment is disrupted. This problem is resolved in software release 2.4(1). (CSCdj36516)
These sections describe open and resolved caveats in supervisor engine software release 2.3(1):
Note For a description of caveats resolved in software release 2.3(1), see the "Resolved Caveats in Software Release 2.3(1)" section.
This section describes open caveats in software release 2.3(1).
- In some cases, if you upload or download software images through SNMP by entering a host name instead of an IP address, the SNMP agent might return a status of "In Progress" for the tftpResult MIB indefinitely, which might prevent you from using SNMP to perform further uploads and downloads. To recover, initiate a tftp upload or download through the command-line interface. (CSCdj24275)
- In some cases, enabling a port immediately after it has been shut down by the port security feature can result in a temporary loss of system memory. As a workaround, wait one minute after a port is shut down before reenabling that port. (CSCdj24844)
- In some cases, the broadcast suppression rate might vary from the set rate, depending on the size and transmission rate of the packets. (CSCdj25623)
- In some cases, when using a faulty cable, the Fast EtherChannel feature might fail to switch over to another functional port in the bundle. (CSCdj25111)
- In some cases, when continuous multicast packets are received on a port that has the port security feature enabled, the port security feature might stop an active communication process. To recover, disable port security. (CSCdj22723)
- In a Catalyst 5500 switch with redundant Supervisor Engine II modules, if you change the timezone offset (by entering the set timezone command), the correct time might not be stored on the secondary Supervisor Engine II module, which can cause an invalid time value to be reported each time there is a switchover from one Supervisor Engine II module to the other. (CSCdj17407)
- In some instances, 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. To recover, clear the ARP table by entering the clear arp all command. (CSCdj12715)
- In some cases, moving a link connection from a dynamic port on one Catalyst 5000 series switch to a dynamic port on another switch across an ATM cloud might result in failure to assign a VLAN until the LE-ARP and CAM entries age out. As a workaround, manually clear the entries as follows:
- Enter the session command to establish a connection to the ATM module, and then enter the clear LANE LE-ARP int ATM0.vlan_num command.
- On the supervisor engine module, enter the clear cam dynamic command.
- (CSCdj26287)
Note For a description of open caveats in software release 2.3(1), see the "Open Caveats in Software Release 2.3(1)" section.
This section describes caveats resolved in software release 2.3(1).
- If you hot insert a second supervisor engine module into a Catalyst 5500 switch and the second supervisor engine's baud rate differs from that of the first supervisor engine, the supervisors might not synchronize. This problem has been resolved in software release 2.3(1). (CSCdj04916)
- Software download to the ATM LANE and FDDI modules might fail the checksum calculation with software release 2.2(1) installed on the supervisor engine. This problem has been resolved in software release 2.3(1). (CSCdj06084)
- In some instances, the Catalyst 5000 series BOOTP address is not broadcast correctly. This problem has been resolved in software release 2.3(1). (CSCdj16296)
- Under certain conditions, you might be unable to create more than 300 RMON history control entries. This problem has been resolved in software release 2.3(1). (CSCdj17341)
- In some cases, after the Catalyst 5000 series switch is reset, ports on the WS-X5213 module that are connected to 10BaseT ports fail autonegotiation and enter the not-connected state, even though their link LEDs indicate that the link is up and connected. This problem has been resolved in software release 2.3(1). (CSCdj17794)
- In some cases, after the Catalyst 5000 series switch experiences an exception error, the error might not be reported in the output of the show log command. This problem has been resolved in software release 2.3(1). (CSCdj20498)
- In some cases, after a power supply failure, the counter showing the number of power supply failures might not increment. This problem has been resolved in software release 2.3(1). (CSCdj22425)
- In some cases involving a Catalyst 5500 switch with a redundant Supervisor Engine II module in slot 2, the output of the show portreg command for ports 2/1 or 2/2 claims that the redundant supervisor feature is not supported in module 2. This problem has been resolved in software release 2.3(1). CSCdj21895)
- If you enable the SPAN and designate any of the ports on the supervisor engine module as the SPAN destination port, any system reset (for example, a switchover from the primary to standby Supervisor Engine II module, or single supervisor engine module reset) results in the Catalyst 5000 series switch not coming online. This problem has been resolved in software release 2.3(1). (CSCdj19342).
These sections describe open and resolved caveats in supervisor engine software release 2.2(2):
Note For a description of caveats resolved in software release 2.2(2), see the "Resolved Caveats in Software Release 2.2(2)" section.
This section describes open caveats in software release 2.2(2).
- If you hot insert a second supervisor engine module into a Catalyst 5500 series switch and the second supervisor engine's baud rate differs from that of the first supervisor engine, the supervisor engines might not synchronize. To recover, reset the system. (CSCdj04916)
- Software download to the ATM LANE and FDDI modules might fail the checksum calculation with software release 2.2(1) installed on the supervisor engine. To recover, use the download command instead of the copy command. (CSCdj06084)
- In some instances, the Catalyst 5000 series BOOTP address is not broadcast correctly. (CSCdj16296)
- In some cases, enabling a port immediately after it has been shut down by the port security feature can result in a temporary loss of system memory. As a workaround, wait one minute after a port is shut down before reenabling that port. (CSCdj24844)
- In some cases, when continuous multicast packets are received on a port that has the port security feature enabled, the port security feature might stop an active communication process. To recover, disable port security. (CSCdj22723)
- In a Catalyst 5500 switch with redundant Supervisor Engine II modules, if you change the timezone offset (by entering the set timezone command), the correct time might not be stored on the secondary Supervisor Engine II module, which can cause an invalid time value to be reported each time there is a switchover from one Supervisor Engine II module to the other. (CSCdj17407)
- In some instances, 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. To recover, clear the ARP table by entering the clear arp all command. (CSCdj12715)
Note For a description of open caveats in software release 2.2(2), see the "Open Caveats in Software Release 2.2(2)" section.
This section describes caveats resolved in software release 2.2(2).
- Under certain conditions when you open a Telnet session to a Catalyst 5000 series switch and then close the Telnet session while the system is expecting input for a specific command, the switch might reset. This problem is resolved in software release 2.2(2). (CSCdj04792)
- Under certain conditions, when you reset the Catalyst 5500 switch, it might not recognize some of the modules. To recover, remove and reinstall the affected modules. This problem is resolved in software release 2.2(2). (CSCdj00513)
- When the dynamic CAM table contains more than 10,000 CAM entries and when you enter the show cam dynamic command from the console with the screen length set to 0, BPDU packet generation might be affected. This problem is resolved in software release 2.2(2). (CSCdj01037)
- When a WS-X5213A module port is connected to the supervisor engine module and the speed is changed from 100 (Mbps) to auto, the 10/100-Mbps WS-X5213A port might toggle continuously between trunking and nontrunking. This problem is resolved in software release 2.2(2). (CSCdj03973)
- When more than four ATM modules are in the Catalyst 5000 series system, SNMP might fail to support all of the ATM modules for all MIBs. This problem is resolved in software release 2.2(2). (CSCdj04023)
- If the Catalyst 5000 series switch contains two ATM modules and if you reset one of the ATM modules while the other ATM module is in the process of coming online, the system might run out of some memory resources. This problem is resolved in software release 2.2(2). (CSCdj04060)
- Under certain conditions, interrupting the show cam static command before all output screens displayed causes the command to display "Total Matching CAM entries = 1," even though the CAM table contains more than one entry. This problem is resolved in software release 2.2(2). (CSCdj04065)
- Under certain conditions, when you enter the clear config all command, the system might experience an exception. This problem is resolved in software release 2.2(2). (CSCdj05005)
- In some instances, while configuring multiple ELANs through an ATM LANE module, the system might experience an exception. This problem is resolved in software release 2.2(2). (CSCdj03853)
- When running more than 600 instances of Spanning-Tree Protocol, adding a new VLAN might cause Spanning-Tree Protocol instability. This problem is resolved in software release 2.2(2). (CSCdj05658)
- Under some conditions, CGMP might fail to add that ATM port to the multicast group. This problem is resolved in software release 2.2(2). (CSCdj05914)
- If you assign a permanent multicast address to an FDDI module in a Catalyst 5000 series switch, initiating a software reset might cause the permanent CAM entry to be lost. This problem is resolved in software release 2.2(2). (CSCdj03882)
- In some instances, when you upgrade a Catalyst 5000 series switch containing an FDDI module to software release 2.2, a checksum-fail message might be reported in the message log. This problem is resolved in software release 2.2(2). (CSCdi92604)
- In some instances, an SNMP walk of the bridge MIB repeatedly loops though the same set of objects. This problem is resolved in software release 2.2(2). (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 resolved in software release 2.2(2). (CSCdj04820)
- If, after enabling NTP, you set the time or date locally, the local setting might take precedence over NTP updates. This problem is resolved in software release 2.2(2). (CSCdj05034)
- In some instances, the output of the show multicast group command might report that, in a specific VLAN, a number of ports are included as destination ports, despite the fact that these ports are not assigned to that VLAN. This problem is resolved in software release 2.2(2). (CSCdj08764)
- After upgrading to the supervisor engine software, the FDDI configuration might not be saved. This problem is resolved in software release 2.2(2). (CSCdj09762)
- In some instances, accessing an ATM module by entering the session command might cause an exception. This problem is resolved in software release 2.2(2). (CSCdj05145)
- 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 resolved in software release 2.2(2). (CSCdj13046)
- In some instances, after resetting the Catalyst 5000 series switch with port security enabled, the system might report a minor hardware error. This problem is resolved in software release 2.2(2). (CSCdj09016)
- If you repeatedly exit a Telnet session while the system displays a --More-- prompt, the system might eventually crash. This problem is resolved in software release 2.2(2). (CSCdj14053)
- When an SNMP query is made for the repeater MIB object, rptrPortOctets, the Catalyst 5000 series switch might experience an exception. This problem is resolved in software release 2.2(2). (CSCdj14056)
- 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 resolved in software release 2.2(2). (CSCdj13639)
- In some cases after a switchover from the primary supervisor engine module to the standby supervisor engine module in a Catalyst 5500 switch, the show spantree command reports the Port-State as disabled rather than not-connected for the ports on the standby supervisor engine module. This problem is resolved in software release 2.2(2). (CSCdj14589)
- In some instances with CGMP enabled, the CGMP system entry is not found in the CAM table. This problem is resolved in software release 2.2(2). (CSCdj13218)
- In some instances, if you reset multiple modules simultaneously, accessing the interface MIB might provide only partial information on the modules. This problem is resolved in software release 2.2(2). (CSCdj16310)
- In some instances, resetting multiple Catalyst 5000 series modules while performing multiple MIB-walks might cause an exception. This problem is resolved in software release 2.2(2). (CSCdj16505)
- In certain cases when using the WS-X5010 module or the WS-X5013 module, if you disable a port 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 resolved in software release 2.2(2). (CSCdj16744)
- The default TACACS+ enable mode has been changed from check-level 1 to check-level 15 to match the levels used in routers, which avoids the need for additional configuration of the TACACS+ servers. For backward compatibility, if authentication with check-level 15 fails, then authentication is retried with check-level 1. (CSCdj17174)
- In some cases, show commands might not display information for all of the modules in the chassis, even though the system continues to recognize the modules. This problem is resolved in software release 2.2(2). (CSCdj16966 and CSCdj03379)
This section describes open caveats in software release 2.2(1).
- Under certain conditions when you open a Telnet session to a Catalyst 5000 series switch and then close the Telnet session before entering any input at the Telnet prompt, the switch might reset. The workaround is to not close a Telnet session without entering any input at the Telnet prompt. (CSCdj04792)
- Under certain conditions, when you reset the Catalyst 5500 switch, it does not recognize some of the modules. To recover, remove and reinstall the affected modules. (CSCdj00513)
- When the dynamic CAM table is populated with a number of CAM entries and the show cam dynamic command is entered from the console with the length of the display set to 0, the BPDU packets coming from the root switch are skewed by as much as 18 seconds for the entire duration of the table display. (CSCdj01037)
- When a WS-X5213A module port is connected to the supervisor engine module and the speed is changed from 100 (Mbps) to auto, the 10/100-Mbps WS-X5213A port might toggle continuously between trunking and nontrunking. (CSCdj03973)
- When more than four ATM modules are in the Catalyst 5000 series system, SNMP fails. (CSCdj04023)
- While running LANE tests with three Catalyst 5000 switches connected through ATM links, one switch that had the cluster in the test bed went down to 0 and did not recover until the Catalyst 5000 switch was rebooted. (CSCdj04060)
- Under certain conditions, interrupting the show cam static command before all output screens have been displayed causes the command to display "Total Matching CAM entries = 1," even though the CAM table contains more than one entry. (CSCdj04065)
- In some cases, enabling a port immediately after it has been shut down by the port security feature can result in a temporary loss of system memory. As a workaround, wait one minute after a port is shut down before reenabling that port. (CSCdj24844)
- In some cases, when continuous multicast packets are received on a port that has the port security feature enabled, the port security feature might stop an active communication process. To recover, disable port security. (CSCdj22723)
- In a Catalyst 5500 switch with redundant Supervisor Engine II modules, if you change the timezone offset (by entering the set timezone command), the correct time might not be stored on the secondary Supervisor Engine II module, which can cause an invalid time value to be reported each time there is a switchover from one Supervisor Engine II module to the other. (CSCdj17407)
- In some instances, 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. To recover, clear the ARP table by entering the clear arp all command. (CSCdj12715)
These sections provide usage guidelines, restrictions, and troubleshooting information for Catalyst 5000 family switch hardware and software:
This section contains usage guidelines, restrictions, and troubleshooting information that apply to the supervisor engine and to the switch at the system level.
- If you attempt to boot a Catalyst 5000 family switch and the switch generates continuous MCP exception errors (and possibly fails to boot), make sure that the supervisor engine has the correct software version for all of the hardware in your configuration. For information on the minimum and recommended software versions for Catalyst 5000 family hardware, see the "Product and Software Version Matrix" section.
| Caution
Before powering up a Catalyst 5500 (WS-C5500) switch with redundant power supplies, install at least two modules in the chassis. If you power up a Catalyst 5500 switch with redundant power supplies with less than two modules installed, the red OUTPUT FAIL LED on one of the power supplies might light, even though the supply is not faulty. |
- After downloading a new Flash image, the next reboot might take longer than normal if Erasable Programmable Logic Devices (EPLDs) on the supervisor engine module need to be reprogrammed. Whether this happens depends on which software version was running on the supervisor engine module before the download and which software version is downloaded. This can add up to 15 minutes to the normal reboot time the first time you reboot with the new image.
- All Catalyst 5000 series supervisor engine modules with at least 16 MB of DRAM fully support all software releases in the 3.x release train.
- On Supervisor Engine I, we recommend you have at least 16-MB DRAM installed to run release 3.x images prior to release 3.2(3). You must have at least 16-MB DRAM to run software release 3.2(3) or later.
- If you are running a release 3.x image prior to software release 3.2(3) on a Supervisor Engine I with 8-MB DRAM, you must use a minimal configuration. Follow these configuration guidelines when using a Supervisor Engine I with 8-MB DRAM:
- Configure 15 or fewer VLANs
- Do not enable RMON
- Do not configure the switch as a VMPS server
- As you enable features, you should carefully monitor the amount of free memory. You can do this by entering the show version command. The amount of free DRAM should be 400K or greater. If this number falls below 400K, disable some features or upgrade memory.
Note If you are using a Supervisor Engine I with 8 MB of DRAM, use the Supervisor Engine I 8-MB images listed in Table 3.
- 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.
- Under certain conditions, inserting a second supervisor engine module into a running Catalyst 5500 switch might cause the switch to reset.
- If a Catalyst 5000 series switch contains 2.1 Software Memory Upgrade Kit SIMMs and is running a software release prior to software release 2.1, the command show version displays only 4 MB of memory. You must install software release 2.1 or higher to allow the show version command to recognize 2.1 Software Memory Upgrade Kit SIMMs, and to display the total memory.
- With a Supervisor Engine II whose boot ROM is not at version 3.1, you cannot use TFTP to upload a new image to a Supervisor Engine II running 3.1 or greater. Instead, you must use Kermit over the console port.
- Under certain conditions, Clock Module:B is Active after boot. This does not indicate any failure of Clock Module:A. It is related to fluctuations in the boot sequence that select Clock Module:B over Clock Module:A. All standard error query and notification processes accurately reflect the status of the primary and standby clock modules.
- If your configuration produces thousands of content-addressable memory (CAM) entries, ensure that your screen length is set to a value greater than 0 before entering the show cam dynamic command.
- The LrnDiscard counter (displayed by entering 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. The counter value is not maintained for each port; instead, the value is maintained for the entire switch.
- The CLI command show cam dynamic and the SNMP query "getmany community@vlan dot1dTpFdbAddress" are sometimes out of sync.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to modules and switch ports.
- When inserting a module into a Catalyst 5000 family chassis, be sure to use the ejector levers on the front of the module to seat the backplane pins properly. Incorrectly inserting a module can cause unexpected behavior. For proper module installation instructions, refer to the Catalyst 5000 Series Module Installation Guide.
- 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, enter the command clear config mod_num to clear the module configuration information in the supervisor engine module and obtain the correct spanning-tree parameters.
- If a module fails to come online, reset the module by entering the reset mod_num command.
- On a Catalyst 5000 family switch with a Supervisor Engine I or II, if you attempt to download a new supervisor engine software image file before one or more modules come online, those modules might fail to come online. Once the download is complete and you reset the switch, the modules should come online correctly.
- If a port fails the physical-medium-dependent (PMD) loopback test (port LED is flashing orange) after the Catalyst 5000 family switch is reset, you must reset the affected module to recover.
- If the Catalyst 5000 family switch detects a port-duplex misconfiguration, the misconfigured switch port is disabled and placed in the "errdisable" state. Reconfigure the port-duplex setting and use the set port enable command to reenable the port.
- In Catalyst 5000 family supervisor engine software release 3.2(2) and later, when the 48-port 10BaseT Telco module (WS-X5012) detects excessive/late collisions on a port, that port is automatically disabled. The show port command output shows the state of the disabled port as "errdisable."
- These errors can occur when there is a port-duplex misconfiguration (both ends of the link are not configured for the same duplex mode) or when the attached cable is not to specification (too long or of the wrong type). If a port has been automatically disabled, make sure the duplex configuration is the same on both ends of the link, verify that the cable is within specification, and then reenable the port using the set port enable command.
- If you have a port whose port speed is set to auto connected to another port whose speed is set to a fixed value, configure the port whose speed is set to a fixed value for half duplex. Alternately, you can configure both ports to a fixed-value port speed and full duplex.
- Whenever you connect a Catalyst 5000 family port that is set to autonegotiate to an end station or another networking device, make sure that the other device is configured for autonegotiation as well. If the other device is not set to autonegotiate, the Catalyst 5000 family port will remain in half-duplex mode, which can cause a duplex mismatch resulting in packet loss, late collisions, and line errors on the link.
- 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 family switch discards because the frames were destined for the local segment.)
- Under heavy traffic conditions, and with a duplex mismatch between connected ports, the following Catalyst 5000 family modules might transmit frames with bad CRC values:
- 48-port 10BaseT Telco Ethernet module (WS-X5012)
- 48-port 10BaseT Telco Ethernet module (WS-X5012A)
- Two-slot 48-port 10BaseT RJ-45 Ethernet module (WS-X5014)
- If you are using FDDI modules in your Catalyst 5000 family switch, we recommend that you run FDDI software release 2.1(7) or later.
- Serial download is supported for downloading Flash code to the supervisor engine module, but not to the switching modules.
- 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 manually.
- Alignment and frame check sequence (FCS) errors are detected when 3Com 3c595 and 3c905 cards are attached to a Catalyst 5000 family switch. (CSCdj01465)
- You cannot disable an ATM module by entering the set module disable command. The workaround is to session to the ATM module and shut down the ATM interface using the shutdown interface configuration command.
- If you have a LECS or LES/BUS configured on an ATM module and you replace the supervisor engine module (on Catalyst 5000 series switches only) or move the ATM module from one slot to another, the ATM addresses (NSAPs) are modified. Be sure to update the LECS database configuration with the new NSAP values.
- A Catalyst 5000 series switch that contains an ATM LANE module might have large SNMP latencies, especially when RMON alarms are enabled on the device. As a workaround, increase the number of SNMP retries and timeouts on the management station.
- 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 software release 2.1(5) or higher.
- A maximum of seven ATM modules or RSMs, in any combination, can be installed in a Catalyst 5500 switch.
| Caution
If you plan to run both the Ethernet LANE software and the Token Ring LANE software, you must run them on separate ATM LANE modules. |
- ATM modules do not generate link up/down traps.
- UplinkFast is not supported over ATM.
- In a 10Base2 network, incorrect termination can cause the port to hang. To recover, disable and then reenable the port.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to transceivers.
- If you experience trouble with a port that has an 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 family switch might stop transmitting data. To recover, reseat the MII transceiver so that it is not seated at an angle. If the Catalyst 5000 family switch still cannot transmit data, disable and then reenable the port.
- If you are using MII transceivers, make sure that you are using compliant MII transceivers. Enter the show portreg command for each MII port to ensure that the value 2100 appears in the first column of output, as shown in the following example:
Console> (enable) show portreg 1/1
Port/PHY registers for 1/1
0x00: 2100 780F 2000 5C00 0081 0000 0000 0000
.
.
.
Console> (enable)
- If you see a value of 0xffff instead of 2100, do not use the MII transceiver. An MII transceiver whose value is set to 0xffff can prevent the Catalyst 5000 family 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 at which the link comes up). A value other than 0 indicates a physical layer problem (most likely a problem with the transceiver).
The Spanning-Tree Protocol (STP) blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, the Catalyst 5000 family switch receives spanning-tree bridge protocol data units (BPDUs) periodically from its neighboring Catalyst 5000 family switch. You can configure the frequency with which BPDUs are received by entering the set spantree hello command (the default frequency is set to two seconds). If a Catalyst 5000 family 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, the learning state, and to the forwarding state. As it transitions, the Catalyst 5000 family 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.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to spanning tree.
- Ensure that the total number of logical ports across all instances of spanning-tree for different VLANs does not exceed the maximum number supported for each supervisor engine type and memory configuration.
- You can use this formula to compute the sum of logical ports on the switch:
- (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
- The sum of all logical ports, as calculated with the formula above, should be less than or equal to:
- 200 for Supervisor Engine I (with 8 MB DRAM)
- 400 for Supervisor Engine I (with 20 MB DRAM)
- 1500 for Supervisor Engine II
- 4000 for Supervisor Engine III
| Caution
If you enable numerous memory-intensive features concurrently (such as VTP pruning, VMPS, EtherChannel, and RMON), or if there is switched data traffic on the management VLAN, the maximum number of supported logical ports is reduced. |
Note Count each port in an EtherChannel port bundle independently (do not count the bundle as a single port).
- A Catalyst family 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, Catalyst family switches reset blocked ports. To ensure recovery, all Catalyst family switches in the network should perform this function at the same time by sending synchronization packets on VLAN 1. These synchronization packets are only sent by a Catalyst family switch if it is the root bridge.
- Use the most-powerful possible supervisor engine version for the root node (for example, Supervisor Engine III instead of Supervisor Engine II).
- Use these commands to monitor blocked spanning-tree ports:
- show port—Check to see if the port has registered a lot of alignment, FCS, or any other type of line errors. If these errors are incrementing continuously, the port might drop input BPDUs.
- show mac—If the Inlost counter is incrementing continuously, the port is losing input packets because of a lack of receive buffers. This problem can also cause the port to drop incoming BPDUs.
- On a blocked spanning-tree port, make sure that the Rcv-Frms and Rcv-Multi counters are incrementing continuously. If the Rcv-Frms counter stops incrementing, the port is not receiving any frames, including 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 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 the neighboring device.
- 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.
- Do not use spanning-tree PortFast on a trunk port. Although the show spantree command displays PortFast as enabled on a trunk port, PortFast has no effect on trunk ports.
- IEEE STP between a Cisco router and Catalyst 5000 family ATM LANE module over RFC 1483 PVCs does not function properly.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to VTP, VLANs, and VLAN trunks.
- If you upgrade to Catalyst 5000 series supervisor engine software release 2.2(1) 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 upgrade 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 automatically added 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.
- Although Dynamic Inter-Switch Link (DISL) is a point-to-point protocol, some internetworking devices might forward DISL frames. To avoid connectivity problems, follow these guidelines:
- For ports connected to non-Catalyst family devices in which trunking is not being used, configure trunk-capable Catalyst 5000 family switch ports to off by entering the set trunk mod_num/port_num off command.
- When trunking to a Cisco router, use the set trunk mod_num/port_num nonegotiate command. The nonegotiate keyword transitions a link into trunking mode without sending DISL frames. The nonegotiate keyword is available in software release 2.4(3) and later.
- To use the dynamic port VLAN assignment feature in a Catalyst 5000 series switch that contains a Supervisor Engine I module, the Supervisor Engine I module must be at hardware revision 1.7 or higher. All hardware revision levels of Supervisor Engine II modules support the dynamic port VLAN assignment feature.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to Fast and Gigabit EtherChannel.
- When using Fast EtherChannel, if a "SPANTREE-2: Channel misconfig - x/x-x will be disabled" or similar syslog message is displayed, it indicates a mismatch of Fast EtherChannel modes on the connected ports. We recommend that you correct the configuration and reenable the ports by entering the set port enable command. Valid EtherChannel configurations include:
| Port Channel Mode
| Valid Neighbor Port Channel Mode(s)
|
|---|
desirable
| desirable or auto
|
auto
| desirable or auto1
|
on
| on
|
off
| off
|
1If both the local and neighbor ports are in auto mode, an EtherChannel bundle will not form.
|
- If you are using media-independent interface (MII) connectors, Fast EtherChannel does not work on the 100BaseTX, RJ-45 supervisor engine module (WS-X5509).
- With a large number of channels, trunks, or VLANs, or a change of channel configuration (for example, off to auto), or upon Fast EtherChannel module reboot, ports might take up to five minutes to form a channel and to participate in spanning tree. (During this interval, the port does not appear in show spantree command output.) If it takes more than ten minutes for a channel to form and appear on spanning tree, disable and reenable the ports. In addition, it might take up to two minutes to unbundle a channel after changing the channel mode.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to the Switch Port Analyzer (SPAN).
- If the SPAN destination port is connected to another device, the port always receives incoming packets for the VLAN it is assigned to but does not participate in the spanning tree for that VLAN. To avoid creating spanning-tree loops, assign the SPAN destination port to an unused VLAN.
- A SPAN destination port receives flooded unicasts and broadcasts for the VLAN of the source SPAN port.
- The RSM does not support SPAN.
This section contains usage guidelines, restrictions, and troubleshooting information that apply to multicast protocols and traffic on the switch.
- Due to a conflict with the Hot Standby Router Protocol (HSRP), Cisco Group Management Protocol (CGMP) leave processing is disabled by default.
- To enable CGMP leave processing, enter the set cgmp leave enable command.
Note If both HSRP and CGMP leave processing are enabled, you might experience some unicast packet flooding.
- When CGMP leave processing is enabled, the Catalyst 5000 family switch learns router ports through PIM-v1, HSRP, and CGMP self-join messages. When CGMP leave processing is disabled, the Catalyst 5000 family switch learns router ports through CGMP self-join messages only.
- CGMP does not prune multicast traffic for any IP multicast address that maps into the Media Access Control (MAC) address range of 01-00-5E-00-00-00 to 01-00-5E-00-00-FF. The reserved IP multicast addresses, in the range 224.0.0.0 to 224.0.0.255, are used to forward local IP multicast traffic in a single Layer 3 hop.
The following documents are available for the Catalyst 5000 series switch:
- Catalyst 5000 Series Quick Installation and Software Configuration
- Catalyst 5000 Series Installation Guide
- Catalyst 5000 Series Module Installation Guide
- Catalyst 5000 Series Software Configuration Guide
- Catalyst 5000 Series Command Reference
- Catalyst 5000 Series System Message and Recovery Guide
- Enterprise MIB User Quick Reference (online only)
Note Release notes for prior software releases were accurate at the time of release. However, for information on the latest caveats and updates to previously released software releases, refer to the release notes for the latest maintenance release in your software release train. You can access the latest software release notes at the World Wide Web locations listed in the "Cisco Connection Online" section.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and 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:22:05 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
