Installation guide

14 Release Notes for Catalyst 6000 Family Software Release 5.x
Open and Resolved Caveats in Software Release 5.3(3)CSX
— set port qos 4/1 policy cops
— set port channel 4/1-8 des
The above sequence of steps causes the problem. The fix shown below ensures that you never
map different ACLs to different ports which might channel together, and later switch them to all
map to the same ACL.
As shown below, the fix involves performing an intermediate step, clearing the ACL mapping on
the ports which have a different ACL mapping than the other ports and mapping them to all have
the same ACL before trying to channel them together (it’s important to clear the older mapping
first).
— set port qos 4/1 policy local
— set qos acl map acl1 4/1
— set qos policy cops
— clear qos acl map acl1 4/1
— set port qos 4/1 policy cops
— set port channel 4/1-8 des
(CSCdp26277)
• Rapidly disabling and enabling QoS with policy source set to COPS might cause the switch to
reset. The workaround is to wait approximately 30 seconds after disabling QoS before reenabling
it when QoS policy source had been set to COPS. (CSCdp32467)
• Online diagnostic failures are experienced on modules during power up, online insertion, or
module reset if the QoS default-action MAC ACL is reconfigured to include an aggregate policer
with an action of drop. The system default does not include an aggregate policer in the
default-action MAC ACL. The likelihood of the diagnostics failures increases as the amount of
traffic being policed (dropped) by that aggregate policer increases. In general, that is as the rate
value specified in the policer decreases and/or the amount of traffic matching all ACLs specifying
that aggregate policer increases. (CSCdp15471)
• After setting the QoS policy source to local, you might need to wait approximately 20 seconds
before the QoS policy source can be set back to COPS. (CSCdp34367)
• After clearing a COPS role or all COPS roles, the console might hang for approximately 20
seconds before showing that the roles cleared. (CSCdp34381)
• 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)
• Occasionally, when a module is removed before it comes online (and before it is finished running
diagnostics), memory corruption might occur. To avoid this problem, do not remove or reinsert
a module during system power up and do not remove or reinsert a module before it comes online.
(CSCdp27673) (CSCdp27562)
• The clear configuration command on the MSM does not properly clear the configuration of the
trunk. Some of the trunk ports have VLAN 1 removed and some do not. This might prevent
setting the port-channel with other MSM ports. The workaround is to reset the MSM module.
(CSCdp11427)
• On Catalyst 6000 switches with redundant supervisor engines (MSFC and PFC), after power
cycling the system some modules might show LC_DNLD_VERIFY: Error - Checksum
verify fail
errors.