Installation guide

50
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release 4.5(1)
• The 64-bit Rx and Tx unicast packet counters are reported incorrectly for these modules:
– WS-X5005, WS-X5006, WS-X5009—Supervisor EngineI module uplink ports
– WS-X5010—24 port 10 BASE-T (Telco connector)
– WS-X5011—12-port 10BASE-FL MMF (ST connector)
– WS-X5013— 24 port 10BASE-T (RJ-45 connector)
– WS-X5113—12-port 100BASE-TX (RJ-45 connector)
This problem is resolved in software release4.5(1). (CSCdk92543)
• If you reconnect a Sun Gigabit Ethernet Card 2.0 to the Catalyst5000 family Gigabit EtherChannel
module (WS-X5410) after the link was broken (for example, by disabling the port or disconnecting
the cable), the output of the show port status command might indicate a “remfault” condition, even
though the link is operational. This problem is resolved in software release4.5(1). (CSCdk88589)
• In some cases, the switch might incorrectly discard HSRP Hello messages. This problem is resolved
in software release4.5(1). (CSCdm05087)
• In some cases, after upgrading the switch software in a chassis with three or more 12-port
100BASE-FX Fast EtherChannel modules (WS-X5201), those modules might fail the loopback tests
and will not come online. This problem is resolved in software release4.5(1). (CSCdm00601)
• In some cases, ports on the 12-port 10BASE-FL MMF module (WS-X5011) might stop transmitting
unicast and broadcast traffic if the connected device experiences a rapid power interruption. This
problem is resolved in software release4.5(1). (CSCdk86526)
• In some cases, when you change the VLAN membership of ports on a Token Ring module
(WS-X5030 or WS-X5031), the CAM table entries for the ports in the original VLAN are not
cleared. This problem is resolved in software release4.5(1). (CSCdk47938)
• In some cases, with clients connected to a Token Ring port, you might experience session timeouts
to servers in the same TrCRF/ELAN reached through an ATM cloud if spanning tree must
reconverge due to a network failure. The client sessions eventually recover after approximately four
minutes. This problem is resolved in software release4.5(1). (CSCdk72635)
• In some situations, a discrepancy can occur between the supervisor engine and the Token Ring
module (WS-X5030 or WS-X5031) CAM tables, causing connectivity problems for some hosts.
This problem is resolved in software release4.5(1) provided the Token Ring module is running
Token Ring software release3.2(5) or later. For more detailed information, see the “New Features”
section in the release notes for Token Ring software release 3.2(5). (CSCdk92278, CSCdm05881)
• In some cases, when you hot insert, reset, or load a new software image on a Token Ring module
(WS-X5030 or WS-X5031), when the module comes online, the spanning tree state for TrCRF
VLANs on the module might be blocking, preventing frame forwarding between TrCRF VLANs
(frame forwarding within a CRF works correctly). This problem is resolved in software
release4.5(1). (CSCdk83458)
• In some TR-LANE environments, All-Route Explorer frames might not be received on or
transmitted out blocking TrBRF VLAN ports. This problem is resolved in software release4.5(1)
with TR-LANE software release70.2(1) or later. (CSCdm07467)
• In some cases, when using a perl script to obtain a list of addresses in the CAM table on the switch,
the switch will issue an “mfree 2 panic” error message onscreen and then reset. This problem is
resolved in software release4.5(1). (CSCdm12707)