Users Guide

seq 5 permit ip host 23.64.0.5 any
seq 10 deny ip any any
In the previous example, the ClassAF1 does not classify traffic as intended. Traffic matching the first match
criteria is classified to Queue 1, but all other traffic is classified to Queue 0 as a result of CAM entry 20419.
When you remove the explicit “deny any” rule from all three ACLs, the CAM reflects exactly the desired
classification.
Create a QoS Policy
There are two types of QoS policies — input and output.
Input QoS policies regulate Layer 3 and Layer 2 ingress traffic. The regulation mechanisms for input QoS
policies are rate policing and setting priority values.
• Layer 3 — QoS input policies allow you to rate police and set a DSCP or dot1p value. In addition, you
can configure a drop precedence for incoming packets based on their DSCP value by using a DSCP
color map. For more information, see DSCP Color Maps.
• Layer 2 — QoS input policies allow you to rate police and set a dot1p value.
Output QoS policies regulate egress traffic. The regulation mechanisms for output QoS policies are
bandwidth percentage, scheduler strict, rate shaping and WRED.
NOTE: When changing a "service-queue" configuration in a QoS policy map, all QoS rules are deleted and
re-added automatically to ensure that the order of the rules is maintained. As a result, the Matched
Packets value shown in the show qos statistics command is reset.
Creating an Input QoS Policy
To create an input QoS policy, use the following steps.
1 Create a Layer 3 input QoS policy.
CONFIGURATION mode
qos-policy-input
Create a Layer 2 input QoS policy by specifying the keyword layer2 after the qos-policy-input
command.
2 After you create an input QoS policy, do one or more of the following:
Configuring Policy-Based Rate Policing
Setting a dot1p Value for Egress Packets
Configuring Policy-Based Rate Policing
To configure policy-based rate policing, use the following command.
• Configure rate police ingress traffic.
QOS-POLICY-IN mode
rate-police
Quality of Service (QoS) 755