Installation guide

Release Notes for Catalyst 6000 Family Software Release 5.x 7
Usage Guidelines and Restrictions
When you change an IPX flow to destination-source, the show mls entry ipx destination
command used to specify a specific destination, displays all IPX Layer 3 entries rather than just
those for a specific destination IPX address. (CSCdm46984)
• The following bug was mistakenly listed as open in software release 5.3(3)CSX. This bug never
affected release 5.3(3)CSX or previous releases.
Bug description: SNMP: A system reset might occur when generating TopN reports with
portTopNMode set to portTopNForeground(1). The workaround is to set portTopNMode to
portTopNBackground(2) for all entries in portTopNControlTable. (CSCdp27013)
• Please note that the following caveat, listed as open in previous releases, will not be fixed:
Changing the console port baud rate from 19,200 to 38,400 incorrectly sets the console port to
9600 baud. After a reset, the console port baud rate is 38,400. Changing the rate to 38,400 from
any other setting works correctly. (CSCdk86876)
• Please note that the following caveat, listed as open in release 5.3(3)CSX will not be fixed:
You cannot use the tftpGrp MIB object to download Catalyst 6000 ATM software.
(CSCdp16574)
• Use the QoS strict-priority queues only for your highest-priority traffic. The strict-priority queues
are designed to accommodate only a limited volume of traffic. In switches with Supervisor
Engine WS-X6K-SUP1-2GE, if you overload the strict-priority-queues, the supervisor engine
cannot service the standard queues. (CSCdm90683)
• The following bug was mistakenly identified as having been fixed in software release
5.3(1a)CSX. This bug was actually fixed prior to the 5.1(1)CSX software release and
therefore was never an issue with Catalyst 6000 family switches.
Bug description: In some cases, a switch with redundant supervisor engines might reset as a
result of the change from Daylight Saving Time to Standard Time. This problem only occurs if
the Daylight Saving Time adjustment is enabled (using the set summertime enable command)
and the switch has not been reset or power-cycled since the change to Standard Time. This
problem is resolved in software release 5.3(1a)CSX. (CSCdk57762)
• You have to make sure that the redirect port defined in a VACL is on the same VLAN as the
“incoming” VLAN for the packet that is to be redirected. Otherwise, the redirected packet will
be dropped.
For example, a redirect VACL is defined on VLAN 5 and the redirect destination port is also on
VLAN 5. If an MLS entry is destined to VLAN 5, packets that are coming from VLAN 2 hit this
MLS entry and also hit the VACL redirect ACE (both VLAN 2 and VLAN 5 ACLs will be
checked) and are redirected in the incoming VLAN, VLAN 2. The redirect destination port will
drop them since it is on VLAN 5 rather than on VLAN 2.
• With QoS disabled, a Gigabit EtherChannel can contain ports with both strict-priority queues and
ports without strict-priority queues. With QoS enabled, a Gigabit EtherChannel cannot contain
both port types. If you enable QoS, ports drop out of any Gigabit EtherChannels that contain both
port types.
• When a multicast goes to both bridged and routed addresses and the multicast packets going to
the routed addresses are Layer 3 switched and the multicast matches an ACL such that QoS
should rewrite the ToS byte in the multicast packet, QoS rewrites the ToS byte for the multicast
packets that are Layer 3 switched, but does not rewrite the ToS byte for the multicast packets that
are bridged.
• To avoid the case where all traffic is out of profile, the burst size specified in a QoS policing rule
must be at least as large as the maximum packet size permissible in the traffic to which the rule
is applied.