Installation guide

62
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release 4.3(1)
On Gigabit Ethernet ports, if autonegotiation is disabled and the link fails in only one direction, only
the port losing the receive (Rx) signal brings its link down; the other port incorrectly keeps the link
up. This problem is resolved in software release 4.3(1). (CSCdk48954)
Some counters might not restart at one again after reaching their maximum value. This problem is
resolved in software release 4.3(1). (CSCdk10989)
If you specify a metric value when you configure multiple default gateways, the primary gateway
appears in the output of the show ip route command but does not appear in the output of the show
config command. When you reset the switch, the primary gateway entry is lost. This problem is
resolved in software release 4.3(1). (CSCdk45487)
If you Telnet to a Catalyst 5000 family switch with a Supervisor Engine III from a workstation
running certain versions of SunOS, the output of the show spantree command shows that spanning
tree is disabled, even though spanning tree is still functioning normally. This problem is resolved in
software release 4.3(1). (CSCdk42809)
In some cases, on a Catalyst 5000 family switch with a Supervisor Engine III and multiple Token
Ring modules (WS-X5030 and WS-X5031), “MCP not responding” errors might appear on the
console, followed by a system reset. This problem is resolved in software release 4.3(1).
(CSCdk48291)
In certain configurations, an end station might be unable to communicate with an RSM. This
problem is resolved in software release 4.3(1). (CSCdk22895)
In some cases, when you configure ports as a Fast EtherChannel bundle, the configuration might fail
due to a speed/duplex mismatch even though the ports are not connected to another device. This
problem is resolved in software release 4.3(1). (CSCdk22225)
In a Catalyst 5000 family switch that has VMPS enabled and is configured so that most of the MAC
addresses are assigned to the fallback VLAN, after a significant period of time the system might
become unmanageable. This problem is resolved in software release 4.3(1). (CSCdk20131)
In some cases, when using a Token Ring VLAN as the management VLAN, the Catalyst5000
family switch might become unmanageable through Telnet or SNMP in the presence of continuous
explorer frames. This problem is resolved in software release 4.3(1). (CSCdk14657)
In some cases, on Catalyst5000 family modules that support Fast EtherChannel, the port with the
lowest port cost (the shortest path) is blocked. This problem is resolved in software release 4.3(1).
(CSCdk22886)
When you attempt to enable NTP on a switch with many active Telnet sessions established, the NTP
configuration might fail. This problem is resolved in software release 4.3(1). (CSCdk19605)
A Catalyst5000 family switch sends two traps when a rising or falling threshold is reached: the
generic RMON trap and the Enterprise-specific trap. The Enterprise-specific trap contains a
truncated Organizational Unique Identifier (OID) for the variable being monitored. This problem is
resolved in software release4.3(1). (CSCdk10594)
After prolonged SNMP usage, the Catalyst5000 family supervisor engine might become unable to
communicate with a module through some SNMP and CLI commands. To recover, reset the module.
This problem is resolved in software release4.3(1). (CSCdk21580, CSCdk26527)
When a personal computer is connected to a 48-port, 10BASE-T Ethernet module (WS-X5012) and
is booted, the WS-X5012 ports show carrier-sense errors. This problem is resolved in software
release4.3(1). (CSCdj73609)