Installation guide
Release Notes for Catalyst 6000 Family Software Release 5.x 17
Resolved Caveats in Software Release 5.3(3)CSX
• The usage display for the clear qos acl map command is:
Usage: clear qos acl map <acl_name> <mod_num/port_num|vlan>
clear qos acl map <acl_name|mod_num/port_num|vlan|all>
The second syntax form fails when entered with multiple port numbers or multiple VLAN
numbers. This problem is resolved in software release 5.3(3)CSX. (CSCdm89542)
• Do not use Netflow Data Export (NDE) version 1 (the default NDE configuration is version 7).
This problem is resolved in software release 5.3(3)CSX. (CSCdm89362)
• After a supervisor engine switchover, a supervisor engine port might go into a state where the
port state is disabled in NVRAM. However, the firmware believes that the port is up and there is
a link on the port. This problem is resolved in software release 5.3(3)CSX. (CSCdm84809)
• When you configure DNS on the switch and specify a hostname for the COPS server, the switch
on reset prints the following to the console every time the COPS/RSVP connection manager tries
to initiate a connection to the COPS server (workgroup-pc is the COPS server in this example):
Translating "workgroup-pc.cisco.com"...domain server (171.69.2.132) (198.92.30.32)
(171.69.2.81) Host name lookup failure
Translating "workgroup-pc.cisco.com"...domain server (171.69.2.132) (198.92.30.32)
(171.69.2.81) Host name lookup failure
Translating "workgroup-pc.cisco.com"...domain server (171.69.2.132) (198.92.30.32) [OK]
This happens until the switch successfully connects to the COPS server. This problem is resolved
in software release 5.3(3)CSX. (CSCdm87215)
• An eight-port channel might stop forwarding traffic after a port in the channel is disabled. This
problem is resolved in software release 5.3(3)CSX. (CSCdm89990)
• Occasionally, after being turned off and back on several times, switches configured as VTP
clients stop accepting VTP updates. This problem is resolved in software release 5.3(3)CSX.
(CSCdm90300)
• After a switch reset, non-trunking ports are put to errdisabled on a VTP client when the VLAN
is activated. For example, the switch is a VTP client with an ISL trunk to a neighboring VTP
server. There is a non-trunk port, port 6/6, assigned to VLAN 13. It is configured for auto,
negotiate. The link connects to a port on another switch, which is also auto, negotiate. When the
VTP client switch is reset, the module (port 6/6) comes online and a link up is received. The port
state shows inactive because the native VLAN is not active. When the ISL trunk is up and the
VLANs are learned, port 6/6 joins the bridge but approximately 20 seconds later, a DTP link
down message is written to the console. This problem is resolved in software release 5.3(3)CSX.
(CSCdm82642)
• System might run out of memory if SNMP cseFlowMcastQueryEntry is repeatedly created and
deleted. This problem is resolved in software release 5.3(3)CSX. (CSCdp00531)
• Using Ctrl-R (command recall) at the initial password prompt displays any part of the password
already entered. For example, if the password is “worker” and you have typed the first three
characters of the password, a Ctrl-R will display a line reading: “Enter Password: wor.” If you
have entered the entire password and walked away, anyone can type Ctrl-R and reveal the
password. This affects both the physical console port and the telnet virtual console. Also, this is
with no TACACS server (local passwords only) using the default configuration. It also only
happens at the initial login password prompt - the enable command's password prompt does not
exhibit the problem. This problem is resolved in software release 5.3(3)CSX. (CSCdm92441)