Configuring Standard QoS
Default Mapping Table Configuration
The default CoS-to-DSCP map is shown in
The default IP-precedence-to-DSCP map is shown in
The default DSCP-to-CoS map is shown in
The default DSCP-to-DSCP-mutation map is a null map, which maps an incoming DSCP value to the
same DSCP value.
The default policed-DSCP map is a null map, which maps an incoming DSCP value to the same DSCP
value (no markdown).
Standard QoS Configuration Guidelines
Before beginning the QoS configuration, you should be aware of this information in these sections:
•
•
•
•
•
•
QoS ACL Guidelines
These are the guidelines with for configuring QoS with access control lists (ACLs):
•
•
•
IPv6 QoS ACL Guidelines
See
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
37-38
"QoS ACL Guidelines" section on page 37-38
"IPv6 QoS ACL Guidelines" section on page 37-38
"Applying QoS on Interfaces" section on page 37-39
"Configuring IPv6 QoS on Switch Stacks" section on page 37-39
"Policing Guidelines" section on page 37-40
"General QoS Guidelines" section on page 37-40
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.
Only one ACL per class map and only one match class-map configuration command per class map
are supported. The ACL can have multiple ACEs, which match fields against the contents of the
packet.
A trust statement in a policy map requires multiple hardware entries per ACL line. If an input service
policy map contains a trust statement in an ACL, the access list might be too large to fit into the
available QoS hardware memory, and an error can occur when you apply the policy map to a port.
Whenever possible, you should minimize the number of lines is a QoS ACL.
Chapter 36, "Configuring IPv6
Table 37-12 on page
Table 37-13 on page
Table 37-14 on page
ACLs.".
Chapter 37
Configuring QoS
37-75.
37-76.
37-78.
OL-13270-06