Configuration Guidelines - Cisco WS-C3550-12G Software Configuration Manual

Configuring QoS

Configuration Guidelines

Before beginning the QoS configuration, you should be aware of this information:
•
•
•
•
•
•
•
•
•
•
Catalyst 3550 Multilayer Switch Software Configuration Guide
20-20
If you have EtherChannel ports configured on your switch, you must configure QoS classification,
policing, mapping, and queueing on the individual physical ports that comprise the EtherChannel.
You must decide whether the QoS configuration should match on all ports in the EtherChannel.
You configure QoS only on physical ports; there is no support for it on the VLAN or switch virtual
interface level.
It is not possible to match IP fragments against configured IP extended ACLs to enforce QoS. IP
fragments are sent as best-effort. IP fragments are denoted by fields in the IP header.
You can match IP options against configured IP extended ACLs to enforce QoS. These packets are
sent to the CPU and processed by software. IP options are denoted by fields in the IP header.
Control traffic (such as spanning-tree bridge protocol data units [BPDUs] and routing update
packets) received by the switch are subject to all ingress QoS processing.
You must disable the IEEE 802.3X flowcontrol on all ports before enabling QoS on the switch. To
disable it, use the flowcontrol receive off and flowcontrol send off interface configuration
commands.
Only one ACL per class map and only one match class-map configuration command per class map
are supported. The ACL can have multiple access control entries, which are commands that match
fields against the contents of the packet.
Use only the match ip dscp dscp-list class-map configuration command in a policy map that is
attached to an egress interface.
Policy maps with ACL classification in the egress direction are not supported and cannot be attached
to an interface by using the service-policy output policy-map-name interface configuration
command. Policy maps containing set or trust policy-map class configuration commands cannot be
attached to an egress interface; instead, you can use the police policy-map class configuration
command to mark down (reduce) the DSCP value at the egress interface.
You can create an aggregate policer that is shared by multiple traffic classes within the same policy
map. However, you cannot use the aggregate policer across different policy maps or interfaces.
Chapter 20 Configuring QoS
78-11194-03