Installation guide

53
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release 4.4(1)
In some cases, after a switchover from the active (slot1) to the standby (slot2) supervisor engine,
the uplink ports on the previously active supervisor engine (slot1) fail to come online. You might
see this message:
%SYS-3-PORT_SSUPFAIL:Failed to bring up ports on standby supervisor
Workaround: Disable the standby ports using the set standbyports disable command and then
reenable them using the set standbyports enable command. If the ports still fail to come online,
reset the standby supervisor engine. (CSCdk73705)
If a Catalyst5000 family switch is configured as a VTP client and its only connection to the VTP
server is through a port on the Gigabit EtherChannel module (WS-X5410) that is configured as an
IEEE 802.1Q trunk with its native VLAN other than VLAN1, when the system is reset the trunk
port might fail to enter trunking mode after the system comes online (the show trunk command
output shows the trunk in the “inactive” state).
Workaround: Reset the module on which the trunk port is located or set the native VLAN of the
trunk port to VLAN1. (CSCdk77956)
In a Catalyst5000 family switch with redundant Supervisor EngineII modules and one or more
ATM modules, if you download a software image to an ATM module and the active supervisor
engine is reset before the ATM module comes online, the ATM image is corrupted and the output
of the show test command for the module shows “Flash-CheckSum Failure.” If you later reset the
ATM module again the system might generate this error message:
recv_data_active : errno = 60
followed by this error message every five seconds:
SYS-3:nvram_active unable to connect with standby
Workaround: Reset the system using the reset command and download the ATM image again.
(CSCdk79201)
On the Catalyst5000 family 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.
Workaround: Do not enter the set system modem enable command when no cable is attached to
the console port. (CSCdk69429)
If you connect to the switch through a Telnet session, execute the traceroute command, and then
terminate the Telnet session (before the traceroute process is complete or any time thereafter),
memory corruption can occur, causing an exception error and reset of the switch. (CSCdk91274)
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. (CSCdm43384)