Modular QoS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

PDF

Modular QoS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

QoS support for VPWS traffic

Updated: September 11, 2026

Want to summarize with AI?

This section explains how QoS is applied to Virtual Private Wire Service (VPWS) traffic by using Layer 2 header fields for traffic classification and differentiation.

QoS support for Virtual Private Wire Service (VPWS) is a QoS feature that:

enables packet classification and remarking for VPWS traffic by using Layer 2 header fields
supports ingress classification on Layer 2 attachment circuits (ACs)
applies IEEE 802.1p Priority Code Point (PCP) and Drop Eligible Indicator (DEI) fields to differentiate traffic and allows QoS policies to be applied to VPWS traffic flows.

EVPN-VPWS is a BGP-based control-plane solution for point-to-point services that establishes an EVPN instance between a pair of provider edge (PE) routers and forwards traffic without requiring MAC address lookup.

Without QoS, VPWS traffic is handled using a best-effort service model, where packets are forwarded without guarantees for delay, throughput, or reliability.

Table 1. Feature History Table
Feature Name	Release Information	Feature Description
QoS Support for VPWS	Release 25.4.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only) This feature is supported on: 8011-32Y8L2H2FH 8011-12G12X4Y-A/D
QoS Support for VPWS	Release 25.1.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only) This feature is now supported on the Cisco 8011-4G24Y4H-I routers.
QoS Support for VPWS	Release 24.4.1	Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100])(select variants only); Modular Systems (8800 [LC ASIC: P100])(select variants only) *This feature is now supported on: 8212-48FH-M 8711-32FH-M 8712-MOD-M 88-LC1-36EH 88-LC1-52Y8H-EM 88-LC1-12TH24FH-E
QoS Support for VPWS	Release 7.7.1	Now, you can apply QoS packet classification on Layer 2 subinterfaces, and for VPWS traffic. This feature provides ingress classification support for L2 attachment circuit (AC) traffic based on the 802.1p field priority value. With this feature, you can use QoS policies on VPWS traffic in your network on Cisco 8000 Series routers.

VLAN tag–based classification for VPWS traffic

VLAN tag–based classification is a Layer 2 traffic classification mechanism that uses fields in the IEEE 802.1Q or 802.1ad VLAN header to differentiate traffic classes.

The VLAN tag includes:

A 3-bit Priority Code Point (PCP) field that identifies traffic priority values from 0 to 7.
A 1-bit Drop Eligible Indicator (DEI) field that marks frames as eligible for drop during congestion.

Modular QoS Configuration (MQC) supports class-map matching based on PCP and DEI values. This classification is supported on 802.1Q and 802.1ad interfaces and applies to:

Attachment circuit (AC) to AC traffic flows
Attachment circuit (AC) to pseudowire (PWE) traffic flows

Figure 1. IEEE 802.1Q VLAN Tag and 802.1p Priority Fields

Configure ingress QoS classification for VPWS

Use this task to configure ingress QoS classification and remarking for Virtual Private Wire Service (VPWS) traffic based on VLAN PCP and DEI fields.

Before you begin

VPWS must be configured on the router. See the L2VPN Configuration Guide for Cisco 8000 Series Routers.

Follow these steps to configure ingress QoS classification for VPWS traffic.

Procedure

Define class maps that match PCP and DEI values in the VLAN header.

Example:



Router# configure terminal 
Router(config)#class-map match-all CONTROL_PLANE  
Router(config-cmap)#match cos 7 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all VOIP  
Router(config-cmap)#match cos 6 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all VIDEO_STREAM  
Router(config-cmap)#match cos 5 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all TRANSACTIONAL_DATA  
Router(config-cmap)#match cos 4 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all DB_SYNC  
Router(config-cmap)#match cos 3 
Router(config-cmap)#match dei 1 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all BULK_DATA  
Router(config-cmap)#match cos 2 
Router(config-cmap)#match dei 1 
Router(config-cmap)#end-class-map 

Router(config)#class-map match-all SCAVENGER  
Router(config-cmap)#match cos 1  
Router(config-cmap)#match dei 1 
Router(config-cmap)#end-class-map 
Router(config)#commit

Associate the defined class maps with a policy map and set traffic-class values.

Example:


Router# configure terminal 
Router(config)# policy-map INGRESS_L2_AC  
Router(config-pmap)# class CONTROL_PLANE  
Router(config-pmap-c)# set traffic-class 7  
Router(config-pmap-c)# exit  

Router(config-pmap)# class VOIP  
Router(config-pmap-c)# set traffic-class 6 
Router(config-pmap-c)# exit 

Router(config-pmap)# class VIDEO_STREAM 
Router(config-pmap-c)# set traffic-class 5 
Router(config-pmap-c)# exit 

Router(config-pmap)# class TRANSACTIONAL_DATA 
Router(config-pmap-c)# set traffic-class 4 
Router(config-pmap-c)# exit 

Router(config-pmap)# class DB_SYNC 
Router(config-pmap-c)# set traffic-class 3 
Router(config-pmap-c)# exit 

Router(config-pmap)# class BULK_DATA 
Router(config-pmap-c)# set traffic-class 2 
Router(config-pmap-c)# exit 

Router(config-pmap)# class SCAVENGER 
Router(config-pmap-c)# set traffic-class 1 
Router(config-pmap-c)# exit 

Router(config-pmap)# class class-default 
Router(config-pmap-c)# exit  
Router(config-pmap)# end-policy-map  
Router(config)# commit

Configure ingress traffic remarking by setting CoS and DEI values for traffic classes as required.

Example:



Router# configure terminal 
Router(config)# policy-map INGRESS_L2_AC 
Router(config-pmap)# class CONTROL_PLANE 
Router(config-pmap-c)# set traffic-class 7 
Router(config-pmap-c)# exit 

Router(config-pmap)# class VOIP 
Router(config-pmap-c)# set traffic-class 6  
Router(config-pmap-c)# set cos 7 
Router(config-pmap-c)# exit 

Router(config-pmap)# class VIDEO_STREAM 
Router(config-pmap-c)# set traffic-class 5 
Router(config-pmap-c)# set cos 5 
Router(config-pmap-c)# exit 

Router(config-pmap)# class TRANSACTIONAL_DATA 
Router(config-pmap-c)# set traffic-class 4 
Router(config-pmap-c)# set cos 5 
Router(config-pmap-c)# exit 

Router(config-pmap)# class DB_SYNC 
Router(config-pmap-c)# set traffic-class 3 
Router(config-pmap-c)# set dei 0 
Router(config-pmap-c)# exit 

Router(config-pmap)# class BULK_DATA 
Router(config-pmap-c)# set traffic-class 2 
Router(config-pmap-c)# set cos 3 
Router(config-pmap-c)# set dei 0 
Router(config-pmap-c)# exit

Router(config-pmap)# class SCAVENGER 
Router(config-pmap-c)# set traffic-class 1 
Router(config-pmap-c)# exit 

Router(config-pmap)# class class-default 
Router(config-pmap-c)# set dei 1  
Router(config-pmap-c)# end-policy-map  
Router(config)# commit

Attach the ingress service policy to the Layer 2 subinterface.

Example:

Router(config)# interface hundredGigE 0/11/0/31.102 
Router(config-subif)# service-policy input INGRESS_L2_AC 
Router(config-subif)# commit

Verify application of ingress QoS policies and correct classification of traffic.

Example:

Router# show policy-map interface Hu0/11/0/31.102 input 
 
HundredGigE0/11/0/31.102 input: INGRESS_L2_AC
 
Class CONTROL_PLANE
  Classification statistics          (packets/bytes)     (rate - kbps)
 Matched             :             9813350/13738690000          936847
    Transmitted         :             9813350/13738690000          936847
    Total Dropped       :                   0/0                    0
Class VOIP
  Classification statistics          (packets/bytes)     (rate - kbps)
 Matched             :           117760245/164864343000         11242157
    Transmitted         :           117760245/164864343000         11242157
    Total Dropped       :                   0/0                    0
Class VIDEO_STREAM
  Classification statistics          (packets/bytes)     (rate - kbps)
 Matched             :            49066792/68693508800          4684233
    Transmitted         :            49066792/68693508800          4684233
    Total Dropped       :                   0/0                    0
Class TRANSACTIONAL_DATA
  Classification statistics          (packets/bytes)     (rate - kbps)
 Matched             :           225707344/315990281600         21547467
    Transmitted         :           225707344/315990281600         21547467
    Total Dropped       :                   0/0                    0
Class DB_SYNC
  Classification statistics          (packets/bytes)     (rate - kbps)
    Matched             :                   0/0                    0
    Transmitted         :                   0/0                    0
    Total Dropped       :                   0/0                    0
Class BULK_DATA
  Classification statistics          (packets/bytes)     (rate - kbps)
    Matched             :                   0/0                    0
    Transmitted         :                   0/0                    0
    Total Dropped       :                   0/0                    0
Class SCAVENGER
  Classification statistics          (packets/bytes)     (rate - kbps)
    Matched             :                   0/0                    0
    Transmitted         :                   0/0                    0
    Total Dropped       :                   0/0                    0
Class class-default
  Classification statistics          (packets/bytes)     (rate - kbps)
 Matched             :           500482413/700675378200         47779164
    Transmitted         :           500482413/700675378200         47779164
    Total Dropped       :                   0/0                    0
Policy Bag Stats time: 1657528790084  [Local Time: 07/11/22 08:39:50.084]

Ingress QoS classification and remarking are enabled for VPWS traffic on the specified subinterface.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.