Configuration Examples For Configuring Modular Qos Packet Classification On Cisco Ios Xr Software; Traffic Classes Defined: Example - Cisco ASR 9000 Series Configuration Manual

Configuration Examples for Configuring Modular QoS Packet Classification on Cisco IOS XR Software

Configuration Examples for Configuring Modular QoS Packet
Classification on Cisco IOS XR Software
This section contains the following examples:
•
•
•
•
•
•
•
•
•

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 101
exit
!
class-map class2
match access-group 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
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
QC-28
Configuring Modular Quality of Service Packet Classification on Cisco ASR 9000 Series Routers
D r a f t - C i s c o C o n f i d e n t i a l
Traffic Classes Defined: Example, page 28
Traffic Policy Created: Example, page 29
Traffic Policy Attached to an Interface: Example, page 29
Traffic Policy Attached to Multiple Subinterfaces: Example, page 29
Default Traffic Class Configuration: Example, page 29
class-map match-any Command Configuration: Example, page 30
Traffic Policy as a QoS Policy (Hierarchical Traffic Policies) Configuration: Example, page 30
Class-based, Unconditional Packet Marking Examples, page 31
Hierarchical Ingress Policing: Example, page 33
OL-17239-01