Installation guide

Release Notes for Catalyst5000 Family Software Release4.x

OL-2306-01

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

• In some cases, when you attempt to use the CiscoView Device Configuration window to modify the

IP routing table on a Catalyst 5000 family 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. (CSCdk34909)

• When you attempt to set a SPAN source that contains two FDDI ports, the command fails and

displays this message: “failed to configure span feature.”

Workaround: Set a single FDDI port as the SPAN source. (CSCdk37502)

• When you set a port on the 24-port 10/100BASE-TX Fast Ethernet module (WS-X5225R) as the

SPAN destination for receive traffic on an ISL trunk port, not all unicast and multicast frames are

seen on the SPAN destination port. (CSCdk31709)

• In some situations, when a port is removed from a VLAN configured as a SPAN source, the port

continues to appear as an “Oper Source” in the output of the show span command. (CSCdk32034)

• In some situations, a port set to autonegotiate speed and duplex on a 24-port 10/100BASE-TX Fast

Ethernet module (WS-X5225R) that is connected to a port on a 12-port 10/100BASE-TX RJ-45

module or a 12-port 10/100BASE-TX Fast EtherChannel module (WS-X5213A or WS-X5203) in

another switch incorrectly negotiates a half-duplex link when either of the switches is reset.

Workaround: Manually set the port speed and duplex using the set port speed and set port duplex

commands. (CSCdk37919)

• In some cases, the TACACS+ key is lost when you perform a switchover from the active to the

standby supervisor engine. (CSCdk33031)

Note CSCdk33031 has not been seen in later releases.

• In some cases, when you open a Telnet session to a Catalyst 5000 family switch from a Windows95

PC and then attempt to configure the switch using the configure network command, the Telnet

session hangs.

Workaround: Connect to the switch through the console port and then configure the switch from

the network using the configure network command. (CSCdk30576)

• In some situations, when you configure a four-port Fast EtherChannel bundle and then configure a

two-port bundle using the first two ports in the original bundle, the remaining two ports will not

participate in spanning tree.

Workaround: Turn channeling off on all four ports and then create the two-port Fast EtherChannel

bundle. (CSCdk37901)

• In some cases, when you initiate a switchover from the active supervisor engine in slot1 to the

standby supervisor engine in slot2, the Token Ring module (WS-X5030 and WS-X5031) fails to

come online. The output of the show module command shows the module status as “faulty.”

Workaround: Reset the Token Ring module. (CSCdk30906)

• In some cases, in a Catalyst 5000 family chassis with both a Supervisor Engine III module and a

Token Ring module (WS-X5030 and WS-X5031), the supervisor engine might generate an MCP

exception error periodically that resets the switch. The problem occurs more frequently if the switch

is processing many SNMP queries. (CSCdk34066)

• If two IEEE 802.1Q-capable peers are negotiating a trunk when a spanning tree loop or prolonged

line-rate traffic exists, a port inconsistency error might occur, causing an excessive number of

syslog messages to be sent to the console. (CSCdk29882)