Installation guide

Release Notes for Catalyst 6000 Family Software Release 5.x 37
Documentation Updates for Software Release 5.3
• In the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release
5.3, the section “Classification, Marking, and Policing with an L3 Switching Engine” has a note
that should be:
Note With an L3 Switching Engine, the Catalyst 6000 family switches provide QoS only for the
Ethertype field values shown in Table 35-2 in Ethernet_II and Ethernet_SNAP frames.
• In the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release
5.3, the last paragraph in the section “Internal DSCP Values” should be:
For trust-dscp and trust-ipprec IP traffic, QoS creates a ToS byte from the 6-bit DSCP value
(which may equal an IP precedence value) and, for trust-cos and trust-ipprectraffic, the original
two-least-significant bits from the received ToS byte, and sends the byte to the egress port to be
written into IP packets. The original two-least-significant bits from the received ToS byte are not
preserved except in trust-dscp or untrusted traffic.
• QoS supports IGMP classification using version 1 four-bit Type fields.
• QoS MAC ACLs that do not include an ethertype parameter match traffic with any value in the
ethertype field, which allows MAC-level QoS to be applied to any traffic.
• In the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release
5.3, the last note (“To avoid inconsistent results”) in the section “Policing Rules” should be:
Note You must configure all ACEs that include the same aggregate policing rule to use the same
ACE keyword: trust-dscp, trust-ipprec, trust-cos,ordscp. If the ACEs use the dscp keyword,
the DSCP value specified must be the same.
• The QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release
5.3, incorrectly documents a set qos bridged-packet-microflow-policing command. In all
cases, it should be set qos bridged-microflow-policing. In the “Enabling Microflow Policing of
Nonrouted Traffic” and “Disabling Microflow Policing of Nonrouted Traffic” sections, the vlan
parameter is shown as being optional, but it is not. The vlan parameter must always be supplied.
• For the set qos bridged-microflow-policing command, “routed traffic” only refers to traffic
being routed by the MSFC when MLS is enabled. To do microflow policing of traffic to and from
other routers, enable bridged microflow policing.
• For wildcards in masks, the QoS chapter of the Catalyst 6000 Family Software Configuration
Guide, Software Release 5.3, incorrectly states “Use zero bits, which need not be contiguous,
where you want wildcards.” The reverse is true. Use one bits, which need not be contiguous,
where you want wildcards.
• In the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release
5.3, in the “Deleting Named ACLs” section:
— The example command should be clear qos acl icmp_acl (there should not be a “1” at the
end).
— Ignore the “Note”. You can use the commit command on a deleted ACL while the ACL is
attached to ports and VLANs, in which case the commit command clears the attachments
and deletes the ACL.