Installation guide

Release Notes for Catalyst5000 Family Software Release4.x

OL-2306-01

Open and Resolved Caveats in Software Release 4.5(1)

• 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. This

problem is resolved in software release4.5(1). (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. This problem is resolved in software release4.5(1). (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. This problem is

resolved in software release4.5(1). (CSCdk91274)

• In some cases, when you upgrade the system software on Supervisor Engine I or II, some sectors of

the Flash memory might not be erased completely, causing the output of the show version command

to display the original version number in the McpSW version field and the upgrade version number

in the NmpSW version field. In most cases, this problem does not impact the functionality of the

switch. This problem is resolved in software release4.5(1). (CSCdk78704, CSCdk86788)

• In some cases, if a Telnet session to the switch closes abnormally while the switch is authenticating

a user with the TACACS+ server, the switch might not close the session to the server properly,

eventually causing the server to reach the maximum number of supported sessions. Subsequent

attempts to authenticate with the server will fail. This problem is resolved in software release4.5(1).

(CSCdk79831)

• If you configure an RMON alarm on an ATM module MIB, subsequently configuring an RMON

alarm on the switch might cause the switch to stop responding to SNMP requests.

Workaround: Avoid configuring RMON alarms on ATM module MIBs. This problem is resolved

in software release4.5(1). (CSCdk69513)

• In some cases, when you remove an NTP server using the clear ntp server command, the removed

server is not removed from the configuration.

Workaround: Reset the switch. This problem is resolved in software release4.5(1). (CSCdk84025)

• In some situations, attempts to create or modify a VLAN fail with this message:

Vlan configuration failed (41)

Workaround: Reset the switch. This problem is resolved in software release4.5(1). (CSCdk88280)