Configuring Modular QoS Service Packet Classification and Marking on Cisco ASR 9000 Series Routers
Configuration Examples for Configuring Modular QoS Packet Classification and Marking on Cisco ASR 9000 Series
QC-33
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
OL-23108-02
Configuration Examples for Configuring Modular QoS Packet
Classification and Marking on Cisco
ASR 9000 Series Routers
This section contains the following examples:
• Traffic Classes Defined: Example, page 33
• Traffic Policy Created: Example, page 33
• Traffic Policy Attached to an Interface: Example, page 34
• Traffic Policy Attached to Multiple Subinterfaces: Example, page 34
• Traffic Policy Attached to a Bundle Interface: Example, page 34
• EFP Load Balancing with Shared Policy Instance: Example, page 35
• Default Traffic Class Configuration: Example, page 35
• class-map match-any Command Configuration: Example, page 35
• Class-based, Unconditional Packet Marking Examples, page 36
• In-Place Policy Modification: Example, page 38
Traffic Classes Defined: Example
In the following example, two traffic classes are created and their match criteria are defined. For the first
traffic class called class1, ACL 101 is used as the match criterion. For the second traffic class called
class2, ACL 102 is used as the match criterion. Packets are checked against the contents of these ACLs
to determine if they belong to the class.
class-map class1
match access-group ipv4 101
exit
!
class-map class2
match access-group ipv4 102
exit
Use the not keyword with the match command to perform a match based on the values of a field that are
not specified. The following example includes all packets in the class qos_example with a DSCP value
other than 4, 8, or 10.
class-map match-any qos_example
match not dscp 4 8 10
!
end
Traffic Policy Created: Example
In the following example, a traffic policy called policy1 is defined to contain policy specifications for
the two classes—class1 and class2. The match criteria for these classes were defined in the traffic classes
created in the
“Traffic Classes Defined: Example” section on page 33.
For class1, the policy includes a bandwidth allocation request and a maximum byte limit for the queue
reserved for the class. For class2, the policy specifies only a bandwidth allocation request.
policy-map policy1