Installation guide

Release Notes for Catalyst5000 Family Software Release4.x

OL-2306-01

Open and Resolved Caveats in Software Release4.2(1)

• In certain cases, if there are multiple ports assigned to the same TrCRF VLAN on different modules

in a Catalyst 5000 family switch, and an ATM LAN emulation client (LEC) is one of those ports,

Token Ring source-route switching might not forward data correctly.

Workaround: Disable the spanning tree for the parent TrBRF VLAN (using the set spantree

disable vlan_num command) and then reenable the TrBRF spanning tree (using the set spantree

enable vlan_num command). This problem is resolved in software release4.2(2). (CSCdk48854)

• In some cases, in a redundant supervisor engine configuration, communication between the two

supervisor engine modules might be lost when a broadcast storm occurs.

Workaround: Reset the switch. This problem is resolved in software release4.2(2). (CSCdk38130)

• In some cases, when a parity error occurs, the switch might reset without first validating the parity

error in hardware. This problem is resolved in software release4.2(2). (CSCdk47791)

• In some cases, configuring multiple default gateways on a Catalyst 5000 family switch can result in

poor performance over time (due to progressively reduced available memory).

Workaround: Remove non-primary gateways from the configuration using the clear ip route

default gateway command and reset the switch. This problem is resolved in software release4.2(2).

(CSCdk46384)

Open and Resolved Caveats in Software Release4.2(1)

These sections describe the open and resolved caveats in supervisor engine software release4.2(1):

• Open Caveats in Software Release4.2(1), page67

• Resolved Caveats in Software Release4.2(1), page69

Open Caveats in Software Release4.2(1)

Note For a description of caveats resolved in software release 4.2(1), see the “Resolved Caveats in

Software Release4.2(1)” section on page69.

This section describes open caveats in software release4.2(1).

• On the Gigabit EtherChannel module (WS-X5410), if a host allowed on one secured port is moved

to another, previously unused secured port on the same module, the host cannot connect to the

network on the second port.

Workaround: Disable port security on the first port, move the host to the second port, and then

reenable port security on the first port (if desired). (CSCdk31747)

• On the Gigabit EtherChannel module (WS-X5410), when the native VLAN of a trunk port is cleared

and then the trunk port is set to off, the port is placed in the inactive state but the Link LED for the

port still shows green. The correct behavior is that the LED for the port should show orange.

(CSCdk31985)

• In the “Designated Root Port” field of the show spantree command, a four-port channel on

ports4–8 of the Gigabit EtherChannel module (WS-X5410) is incorrectly shown as being a

five-port channel (ports5–9). (CSCdk25123)