Vpls And Vpws Qos: Example - Cisco ASR 9000 Series Configuration Manual

Modular QoS Deployment Scenarios
These guidelines apply to the VPLS and VPWS QoS feature:
• Supported on ingress Layer 2 bundle and nonbundle subinterfaces.
• Not supported on Layer 3 subinterfaces, but supported on ports with port inheritance policy. The system
• Match VPLS <control | multicast | broadcast> and match ethertype arp can be applied on a Layer 2
VPLS and VPWS QoS, on page 198
pseudowires (PWs) interconnected to bridge domains in the routers. Each of the provider edge (PE) routers
has a bridge domain. Each PW is a bridge port into the bridge domain. The customer edge (CE) connection
into each PE router is an attachment circuit (AC) bridge port into the same bridge domain. QoS configuration
commands are applied to the AC that connects to the CE router on the one end and the bridge domain of the
PE router on the other.
Figure 13: Typical VPLS Network Topology

VPLS and VPWS QoS: Example

This section contains a configuration example based on the components shown in
on page
The policy-map and PE-to-CE connection are configured as follows on the PE1 router:
class c1
match vpls multicast
!
class c2
VPLS-specific and VPWS-specific classification are performed only in the ingress
Note
direction.
ignores VPLS classification on Layer 3 subinterfaces associated with the port.
interface regardless of the Layer 2 service type, however VPLS <control | multicast | broadcast>
classification is ignored on a non-VPLS Layer 2 interface type.
198, and explains how the network matches packets based on the configured values.
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide, Release 6.1.x
illustrates a typical VPLS topology. The VPLS network is a mesh of
VPLS and VPWS QoS: Example
VPLS and VPWS QoS,
199