Installation guide

66
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release4.2(2)
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 do not want to have ports disabled under these conditions, you can enter the set option
errport enable command to disable this feature (this command affects the entire switch). However,
because disabling this feature creates a risk that all ports on the module might stop transmitting and
receiving traffic when there is a port-duplex mismatch or when an out-of-specification cable is used,
we strongly recommend that you leave this feature disabled. The set option errport command is
available in software release 4.2(2) and later. (CSCdk44463)
• The Catalyst 5000 family switch might erroneously transmit a multicast frame on a blocked port
when the following conditions are met:
– A multicast MAC address is configured as a permanent content-addressable memory (CAM)
entry
– A port on a 48-port, 10BASE-T Ethernet module (WS-X5012) is enabled and disabled
– A frame with the MAC address in the CAM table originates from the port
This problem is resolved in software release 4.2(2). (CSCdk44560)
• In a chassis with redundant Supervisor Engine III modules with NFFCs and the 24-port
10/100BASE-TX Fast Ethernet module (WS-X5225R), you must have an uplink module installed
in the supervisor engine in slot2. Without an uplink module in the supervisor engine in slot2,
system diagnostics might fail, causing a variety of problems on the switch.
Workaround: Install an uplink module in the supervisor engine in slot 2. This problem is resolved
in software release4.2(2). (CSCdk41377)
• When you boot a Catalyst 5000 family switch with a supervisor engine installed in slot 2 and no
supervisor engine in slot 1, the DRiP protocol incorrectly initializes with a MAC address of all
zeros. The correct behavior is for DRiP to initialize with a MAC address in the MAC address range
of the supervisor engine.
Workaround: Install a supervisor engine in slot 1. This problem is resolved in software
release4.2(2). (CSCdk35223)
• Duplicate packets might be seen on an RSM VLAN interface after you move the interface from one
DMA channel to the other using the dma-channel interface configuration command.
Workaround: Enter the microcode reload global configuration command after entering or
removing a dma-channel command on RSM interfaces. This problem is resolved in software
release4.2(2). (CSCdk45657)
• If you enable distributed TrCRF VLANs using the set tokenring distrib-crf enable command while
DRiP is enabled, you still cannot configure a distributed TrCRF VLAN.
Workaround: Disable DRiP using the set tokenring reduction disable command. This problem is
resolved in software release4.2(2). (CSCdk36408)
• After a reset, an ATM module might not receive all of the configuration necessary (such as the DRiP
database) to properly forward traffic to and from a Token Ring LEC. This problem is resolved in
software release4.2(2). (CSCdk28968)