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-35
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
OL-23108-02
EFP Load Balancing with Shared Policy Instance: Example
The following examples show how to configure load balancing of an EFP when SPI is implemented. For
additional information on EFP load balancing on link bundles, see the Cisco
ASR 9000 Series
Aggregation Services Router Interface and Hardware Component Configuration Guide.
Configuring a Bundle Interface: Example
interface Bundle-Ether 50
interface gigabitethernet 0/1/0/5
bundle id 50 mode active
interface gigabitethernet 0/1/0/8
bundle id 50 mode active
Configuring Two Bundle EFPs with the Load Balance Options: Example
This example configures the traffic for two bundle EFPs go over the same physical member link.
interface Bundle-Ether 50.25 l2transport
encapsulation dot1q 25
bundle load-balance hash-select 2
!
interface Bundle-Ether 50.36 l2transport
encapsulation dot1q 36
bundle load-balance hash-select 2
Default Traffic Class Configuration: Example
The following example shows how to configure a traffic policy for the default class of the traffic policy
called policy1. The default class is named class-default, consists of all other traffic, and is being shaped
at 60 percent of the interface bandwidth.
policy-map policy1
class class-default
shape average percent 60
class-map match-any Command Configuration: Example
The following example illustrates how packets are evaluated when multiple match criteria exist. Only
one match criterion must be met for the packet in the class-map match-any command to be classified
as a member of the traffic class (a logical OR operator). In the example, protocol IP OR QoS group 4
OR access group 101 have to be successful match criteria:
class-map match-any class1
match protocol ipv4
match qos-group 4
match access-group ipv4 101
In the traffic class called class1, the match criteria are evaluated consecutively until a successful match
criterion is located. Each matching criterion is evaluated to see if the packet matches that criterion. If the
packet matches at least one of the specified criteria, the packet is classified as a member of the traffic
class.
To Next Page
Loading...
Need help?
General
