602
Configuring QoS
Configuring QoS
If the number of internal QoS labels exceeds 256, you receive an error message.
Table maps are not supported for violate-action for aggregate policing unless you configure a table map for
exceed-action and no explicit action is configured for violate-action. For both individual and aggregate policers, if
you do not configure a violate-action, by default the violate class is assigned the same action as the exceed-action.
If double-tagged packets are received on a trunk or 802.1Q tunnel interface, these packets can be classified on
DSCP and IP precedence along with other parameters, but you cannot set DSCP or IP precedence on the outgoing
packets. You can set CoS on the outgoing packets.
See the configuration sections for specific QoS features for more configuration guidelines related to each feature.
Using ACLs to Classify Traffic
You can classify IP traffic by using IP standard or IP extended ACLs. You can classify IP and non-IP traffic by using Layer
2 MAC ACLs.
Follow these guidelines when configuring QoS ACLs:
You cannot 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.
The switch supports only one access group per class in an input policy map.
You cannot configure match-access group in an output policy map.
These sections describe how to create QoS ACLs:
Creating IP Standard ACLs, page 602
Creating IP Extended ACLs, page 603
Creating Layer 2 MAC ACLs, page 605
Creating IP Standard ACLs
Beginning in privileged EXEC mode, follow these steps to create an IP standard ACL for IP traffic:
To Next Page
Loading...
Need help?
General