Table of Contents
Advertisement
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):
•
•
•
•
Policing Guidelines
These are the policing guidelines:
•
•
Catalyst 2960 Switch Software Configuration Guide
28-32
"QoS ACL Guidelines" section on page 28-32
"Policing Guidelines" section on page 28-32
"General QoS Guidelines" section on page 28-33
If you use QoS ACLs for classification, you can use the sdm prefer qos global configuration
command to set the Switch Database Management (SDM) feature to the QoS template. SDM
configures system resources to support the maximum number of access control entries (ACEs). For
more information on the SDM templates, see
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 TCAM 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 TCAM and an error can occur when you apply the policy map to a port. Whenever
possible, you should minimize the number of lines in a QoS ACL.
The port ASIC device, which controls more than one physical port, supports 256 policers (255
user-configurable policers plus 1 policer reserved for system internal use). The maximum number
of user-configurable policers supported per port is 63. Policers are allocated on demand by the
software and are constrained by the hardware and ASIC boundaries. You cannot reserve policers per
port; there is no guarantee that a port will be assigned to any policer.
Only one policer is applied to a packet on an ingress port. Only the average rate and committed burst
parameters are configurable.
Table 28-12 on page
28-52.
Table 28-13 on page
Table 28-14 on page
28-55.
Chapter 7, "Configuring SDM Templates."
Chapter 28
Configuring QoS
28-53.
OL-8603-04
Advertisement
Chapters
Table of Contents
Troubleshooting
