Installation guide

12 Release Notes for Catalyst 6000 Family Software Release 5.x
Open and Resolved Caveats in Software Release 5.3(4)CSX
• Occasionally, after a system reset or power on, you will see that the standby supervisor engine
shows 0 ports and the standby ports are not enabled. This problem might happen if one of the
supervisor engine is approximately 20 seconds later than the other to begin booting the runtime
image after a system reset or system power on. The workaround is to try to reset the standby
supervisor engine from the active supervisor engine’s console port. If that does not work or is not
allowed, you must remove and reinsert the standby supervisor engine. This problem is resolved
in software release 5.3(4)CSX. (CSCdp20622)
• When SPAN is configured with Etherchannel ports, the open sources might not be correct (based
on Etherchannel status). This problem is resolved in software release 5.3(4)CSX. CSCdp23958
• The GBIC link status between two supervisor engines changes continually between link up and
link down after a unidirectional link failure. This problem is resolved in software release
5.3(4)CSX. (CSCdp37412)
• The MSM Autostate feature is not shutting down MSM interfaces in a VLAN when the last
external interface in the VLAN is disconnected. This problem is resolved in software release
5.3(4)CSX. (CSCdp34155)
• No registration was received from removed modules after a supervisor engine switchover. This
problem is resolved in software release 5.3(4)CSX. (CSCdp34000)
• The routine GetNextUnicastEarlEntry() was designed to be used to search unicast MAC entries
and then return the module and port number from which the MAC entry was learned. In the case
of a multicast entry, or an entry having a flood index, you should skip the entry to avoid returning
an invalid module and port number that SNMP cannot handle. This problem is resolved in
software release 5.3(4)CSX. (CSCdp31964)
• The trunk is going up and down when the channel is in channel-on mode and the trunk is in
non-negotiate mode. This problem is resolved in software release 5.3(4)CSX. (CSCdp32703)
• The switch might experience unexpected behavior if you configure 1024 different VIPs,
producing a VACL with 4092 entries. A VACL of this size stresses the BDD library to the upper
limits of memory usage.This problem is resolved in software release 5.3(4)CSX. (CSCdp32519)
• HSRP failed to route traffic to the trunk on the redundant router for one of five VLANs
configured. This problem is resolved in software release 5.3(4)CSX. (CSCdp18397)
• If you add a new VLAN to the system, the CAM entries for this newly added VLAN for RSVP
are not created. As a result, RSVP PATH messages coming in over the new VLAN are dropped.
This problem is resolved in software release 5.3(4)CSX. CSCdp27505
• Gigabit Ethernet counters show incorrect values. This problem is resolved in software
release 5.3(4)CSX. (CSCdp22433)
• Attachment of a dynamic RSVP ACL might cause a system reset. This problem is resolved in
software release 5.3(4)CSX. (CSCdp31142)
• After modifying existing IP ACLs using a script to add a large number of ACEs, the microflow
policers might stop working. This problem is resolved in software release 5.3(4). (CSCdp38913)
• Inconsistent channel-forming behavior occurs in PagP for ports that support the strict priority
queue and ports that do not. This problem is resolved in software release 5.3(4)CSX.
(CSCdp34951)
• The LED light remains on indicating link speed even when the link is down. This problem is
resolved in software release 5.3(4)CSX. (CSCdp42337)
• The following sequence of events results in the loss of the ASLB configuration:
(a) Configuring ASLB