Table Of Contents
Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Information About Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
How to Configure MDRR and WRED
Configuring WDRR and WRED with the Legacy CLI Configuration: Example
How to Configure Traffic Policing and Shaping for Frame Relay over MPLS
Configuring FRoMPLS Two-rate Three-color Policer
Two-rate Three-color Color-blind Policer: Example
Two-rate Three-color Color-blind Policer with Multiple Actions: Example
Two-rate Three-color Color-aware Policer with Multiple Actions: Example
Configuring FRoMPLS Traffic Shaping
Configuring FRoMPLS Per-VC Disposition Shaping
Configuring FRoMPLS Per-class Disposition Shaping
Configuring FRoMPLS Per-VC Imposition Shaping
Configuring FRoMPLS Per-Class Imposition Shaping
FRoMPLS Per-Class Imposition Shaping: Example
Configuration Examples for FRoMPLS Traffic Policing and Shaping
Attaching a Service Policy to Main Interface: Example
Attaching a Service Policy to Main Interface with Map-class: Example
Attaching a Service Policy to a Subinterface: Example
Frame Relay Customer-facing Interface: Example
Per-DLCI Egress Shaping: Example
How to Configure ATMoMPLS Traffic Policing
Variable Bit Rate —VBR.2 and VBR.3 Without Cell Tagging
Variable Bit Rate —VBR.3 with Cell Tagging
Policing Configuration Excluding OAM Cells
How to Configure ATMoMPLS Traffic Shaping
Configuring ATMoMPLS Per VC/VP Disposition Shaping
Configuring ATMoMPLS Per-class Imposition Shaping
Configuration Examples for ATMoMPLS
Attaching Service Policy to Permanent Virtual Circuit: Example
Matching on ATM OAM Cells: Example
How to Configure Traffic Policing and Shaping for EoMPLS
Configuring the EoMPLS One-Rate Two-Color Policer
Configuring the EoMPLS Two-Rate Three-Color Policer
Configuring EoMPLS Traffic Shaping
Configuring EoMPLS Per-VLAN Disposition Shaping
Configuring EoMPLS Per-VLAN Imposition Shaping
Configuring EoMPLS Per-Class Disposition Shaping
Configuring EoMPLS Per-Class Imposition Shaping
Configuration Examples for Ethernet over MPLS
Attaching Service Policy to the Main Interface (Port Mode): Example
Attaching Service Policy to Subinterface (VLAN): Example
EoMPLS Customer-facing Interface Configuration: Example
Attaching Service Policy to Main Interface (PPP or HDLCoMPLS): Example
Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
This document describes MPLS Quality of Service (QoS) implementations for Cisco 12000 Series line cards configured for Frame Relay over MPLS (FRoMPLS), ATM over MPLS (ATMoMPLS), and Ethernet over MPLS (EoMPLS). Local Switching features are noted but not discussed in this document.
Feature History for Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Information About Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
•
How to Configure MDRR and WRED
•
How to Configure Traffic Policing and Shaping for Frame Relay over MPLS
•
How to Configure ATMoMPLS Traffic Policing
•
How to Configure ATMoMPLS Traffic Shaping
•
How to Configure Traffic Policing and Shaping for EoMPLS
Information About Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Policing and shaping Layer 2 VPN traffic at the MPLS imposition and disposition interfaces permits the Service Provider to offer service level agreements (SLAs) to customers in terms that include bandwidth, delay, jitter, and packet-loss guarantees. At imposition, Frame Relay, Asynchronous Transfer Mode, or Ethernet QoS markers are mapped to MPLS experimental bits. The traffic can be classified by the MPLS experimental bit, then policed and shaped on the provider interfaces. For traffic traversing the Cisco 12000 Series Router, Modified Deficit Round Robin (MDRR) congestion management and Weighted Random Early Detection (WRED) congestion avoidance are now supported for MPLS packets with Layer 2 VPN payloads. Because packet queuing characteristics vary among the Cisco 12000 Series line cards, MDRR and WRED configurations can vary with the line card combinations used for MPLS imposition and disposition interfaces. Table 1 displays a summary of the Layer 2 QoS features introduced in Cisco Release 12.0(32)S, as well as those supported in previous Cisco IOS releases.
Layer 2 QoS features supported by the Cisco 12000 Series router and line cards for Cisco IOS Release 12.0(32)S are as follows:
For All Transport Types:
•
Per-class traffic shaping on egress (disposition) for all Cisco 12000 Series line cards
•
Per-class traffic shaping on ingress (imposition) for all Cisco 12000 Series line cards
Frame Relay Features
•
Support of Two-rate, Three-color policer for Cisco 12000 Series ISE Packet-over-SONET line cards, based on RFC-2698.
•
Support for marking MPLS experimental bits (EXP) as a policing action, in addition to setting the discard eligibility (DE) bits
•
Mapping and copying of Layer 2 Class of Service (CoS) DE bits to MPLS experimental bits at the ingress
•
Per-DLCI egress shaping on Engine 5
ATM Features
•
Support of AAL5 policing in Cisco 12000 Series ISE ATM line cards, based on the Generic Cell Rate Algorithm (GCRA) policer in the ATM Traffic Management Specification Version 4.1 (TM 4.1)
•
Support of Two-rate, Three-color policer for Cisco 12000 Series ATM line cards based on
GCRA for ATM and RFC-2698.•
Support for marking MPLS experimental bits as a policing action, in addition to setting Cell Loss Priority bits
•
Mapping and copying of Layer 2 Class of Service (CoS) Cell Loss Priority (CLP) bits to MPLS experimental bits at the ingress for all Cisco 12000 Series ATM line cards
•
Filtering and classification of control traffic for ATM line cards with match OAM command to permit OAM cells that are in sequence to be excluded from classification
•
Per-VC shaping for all Cisco 12000 Series ATM line cards
•
Support for the CLP thresholds (0/1) discard mechanism on Cisco 12000 Series ISE ATM line cards.
Ethernet Features
•
Support of Two-rate, Three-color policer for Cisco 12000 Series ISE Ethernet line cards, including VLANS, based on RFC-2698.
•
Support for marking MPLS experimental bits as a policing action, in addition to setting the 802.1p User Priority field (P-bits)
•
Mapping and copying of the Layer 2 class of service (COS) P-bits to MPLS experimental bits at the ingress
•
Mapping and copying of MPLS experimental bits to Layer 2 CoS P-bits at the egress.
•
Setting of Layer 2 CoS P-bits based on the VLAN ID at egress
•
Egress traffic shaping on all line cards.
HDLC/PPP Features
•
Exp marking
Miscellaneous Features
•
Support for MDRR/WRED (tofab and frfab) for MPLS packets with Layer 2 Virtual Private Network (L2VPN) payloads
•
Support for the set-qos-group and set-discard-class policer action options for the Cisco 12000 Series line cards based on Engine 3 and Engine 5.
•
Support for class-based QoS MQC MIBS relating to MPLS-based Layer 2 VPNs.
How to Configure MDRR and WRED
For configuration overview information on MDRR for the Cisco 12000 Series line cards, see Understanding and Configuring MDRR/WRED on the Cisco 12000 Series Internet Router at the following URL:
http://www.cisco.com/warp/public/63/mdrr_wred_overview.htmlFor WRED legacy CLI configuration information, examples, and command descriptions, see
Weighted Random Early Detection on the Cisco 12000 Series Router at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/wred_gs.htmOn the ToFab (Rx) side of the Cisco 12000 Series routers, you must use the legacy QoS CLI and the Modular Quality of Service CLI (MQC) configuration on the FrFab (Tx) side. The QoS policy for ToFab or the FrFab side can be applied on imposition and disposition routers.
On the ToFab side, the QoS policy is constructed based on the MPLS experimental bits. The keyword precedence implies EXP bits for MPLS packets, which covers AToM packets as well on the imposition Rx card. The correct output queue (OQ) or local output queue (LOQ) value is selected and a different WRED profile is applied based on the experimental bit settings.
On the FrFab side for imposition, QoS policy can be constructed using MQC to match on EXP bits. On the FrFab side for disposition, EXP value is conveyed to the Tx line card by the qos-group ID/discard-class and QoS policy can be constructed using MQC to match on qos-group ID bits to select the OQ/LOQ and discard-class to select WRED profile. This functionality is used to achieve egress shaping on EXP values. The QoS policy is created on a source-slot/destination-slot table basis.
Configuring WDRR and WRED with the Legacy CLI Configuration: Example
rx-cos-slot 0 slot0slot-table-cos slot0destination-slot 1 slot0-to-slot1cos-queue-group slot0-to-slot1precedence 0 queue low-latencyprecedence 1 queue 1precedence 1 random-detect-label 1precedence 2 queue 2precedence 2 random-detect-label 2precedence 3 queue 3precedence 3 random-detect-label 3random-detect-label 1 100 200 1random-detect-label 2 200 300 1random-detect-label 3 300 400 1queue 0 20queue 1 20queue 2 30queue 3 30queue low-latency strict-priorityHow to Configure Traffic Policing and Shaping for Frame Relay over MPLS
Configuring FRoMPLS Two-rate Three-color Policer
Table 2 displays the FroMPLS policer options supported in Release 12.0(32)S.
See Cisco IOS Quality of Service Solutions Command Reference, Release 12.3 at the following URL for further information on police policy-map configuration commands:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/qos_r/index.htm
Cisco IOS 12.0(30)S introduced support for the following Two-rate, Three-color policer in color-aware mode for FRoMPLS, with matching on Frame Relay discard eligible bit (match fr-de) as a color:
police {cir cir} [bc conform-burst] {pir pir} [be peak-burst] [conform-action action [exceed-action action [violate-action action]]]
The set-frde-transmit and set-mpls-exp-transmit value options can be used in multiple action mode.
The color-blind version of the Three-color policer was supported for Layer 2 VPNs in earlier Cisco IOS releases.
For further information on Two-rate, Three-color policers see QoS: Color-Aware Policer at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/12s_cap.htmFor further information on multiple actions policing, see Policer Enhancement — Multiple Actions at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftpolenh.htmRestrictions
Two-rate three-color color-blind policer is supported on Cisco 12000 Series line card with Engines 0, 2, 3 or 5 (ISE). Two-rate three-color color-aware policer is supported on Cisco 12000 Series line card with Engines 3 or 5 (ISE).
Two-rate Three-color Color-blind Policer: Example
The following color-blind configuration fragment sets the DE bit to 1 for packets in flows that exceed the committed information rate (CIR) but are less than or equal to the peak information rate (PIR). Packets in flows that exceed the PIR are discarded:
Router(config-pmap-c)# police cir 64000 bc 10000 pir 128000 be 20000 conform-action transmit exceed-action set-frde-transmit violate dropTwo-rate Three-color Color-blind Policer with Multiple Actions: Example
The following color-blind, multi-action configuration example sets the DE bit to 1 and the MPLS experimental value to 5 for packets in flows that exceed the committed information rate (CIR) but are less than or equal to the peak information rate (PIR). Packets in flows that exceed the PIR are discarded:
Router(config-pmap-c)# Police cir 64000 pir 128000Router(config-pmap-c-police)# conform-action transmitRouter(config-pmap-c-police)# exceed-action set-mpls-exp-transmit 5Router(config-pmap-c-police)# exceed-action set-frde-transmitRouter(config-pmap-c-police)# violate-action dropTwo-rate Three-color Color-aware Policer with Multiple Actions: Example
The following color-aware configuration fragment demonstrates the use of the discard eligibility bit as a color:
Router(config)# class-map frde_classRouter(config-cmap)# match fr-deRouter(config)# class-map no_frde_classRouter(config-cmap)# match not fr-deRouter (config)# policy-map color-aware-frRouter(config-pmap)# class kulur-awhereRouter(config-pmap-c)# police cir 64000 bc 10000 pir 128000 be 20000Router(config-pmap-c-police)# conform-color no_frde_class exceed-color frde-classRouter(config-pmap-c-police)# conform-action transmitRouter(config-pmap-c-police)# exceed-action set-frde-transmitRouter(config-pmap-c-police)# violate-action dropConfiguring FRoMPLS Traffic Shaping
In general Frame Relay allows two types of traffic shaping: Generic Traffic Shaping (GTS) and Frame-relay Traffic Shaping (FRTS). For FRoMPLS, GTS per-class disposition shaping and per-class imposition shaping are supported. Beginning with Engine 5, per-DLCI egress shaping also is supported.
The following sections on traffic shaping relate only to Cisco 12000 Series ISE line cards (Engine 3 and Engine 5):
•
Configuring FRoMPLS Per-VC Disposition Shaping
•
Configuring FRoMPLS Per-class Disposition Shaping
•
Configuring FRoMPLS Per-VC Imposition Shaping
•
Configuring FRoMPLS Per-Class Imposition Shaping
•
Configuring FRoMPLS Per-DLCI Egress Shaping, page 13
Table 3 lists the FRoMPLS policy-map configuration commands supported in Cisco IOS Release 12.0(32)S.
Note
For per-DLCI egress shaping the only supported instructions are match any, class-default, shape, queue-limit, and random-detect discard-class.
For further information on QoS commands, See Cisco IOS Quality of Service Solutions Command Reference, Release 12.3 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/qos_r/index.htmConfiguring FRoMPLS Per-VC Disposition Shaping
On Engine 5 line cards, output policy is attached to the FR interface or sub-interface using the map-class command. (The switched-dlci method, used in releases before 12.0(32)S, has now been retired). The switched-dlci method is also not supported on the SIP-400 linecard with SPA-4XcT3/DS0 running release12.0(31)S2.
The commands allowed are match-any and class-default.
The actions allowed are share, queue-limit, and random detect discard-class.
The following table shows how to configure per-dlci egress shaping.
Configuring FRoMPLS Per-class Disposition Shaping
For FRoMPLS per-class disposition traffic shaping, match on the MPLS experimental value on the ingress disposition card then set the qos-group and the discard-class (if necessary).
On the egress port on the disposition router, match and shape on the class represented by the qos-group. WRED can be applied on discard-class values.
The policy is attached in the output direction on the customer-facing main interface.
The following procedure demonstrates the steps recommended to configure FRoMPLS per-class disposition shaping:
Step 1
Define the classes for matching the MPLS experimental values.
class-map match-any exp1match mpls exp 1class-map match-any exp2match mpls exp 2Step 2
Define the ingress policy to be applied to the RX interface.
policy-map ingress-policyclass exp1set qos-group 1set discard-class 1class exp2set qos-group 2set discard-class 2Step 3
Define the classes for matching on qos-group on egress.
class-map match-all qos1match qos-group 1class-map match-all qos2match qos-group 2Step 4
Define the egress policy to be applied to TX interface.
Policy-map egress-policyClass qos1bandwidth percent 10shape average 64000000random-detect discard-class-basedrandom-detect discard-class 1 1000 2000random-detect discard-class 2 2000 3000
Configuring FRoMPLS Per-VC Imposition Shaping
Per-virtual circuit imposition shaping is not supported for FRoMPLS in Cisco IOS Release 12.0(32)S.
Configuring FRoMPLS Per-Class Imposition Shaping
To configure per-class imposition shaping for FRoMPLS, mark the packets with set experimental imposition on the Rx line card, then apply shaping on the Tx line card.
The policy is attached in the output direction on the core-facing interface.
FRoMPLS Per-Class Imposition Shaping: Example
In the following example, the map class labeled fr_set_exp1 is applied to the Rx interface, and the policy map labeled imposition_tx_shaping is applied as shown below to the Tx interface.
policy-map set_exp1class class-defaultset mpls experimental imposition 1map-class frame-relay fr_set_exp1service-policy input set_exp1class-map match-all match_exp1match mpls experimental 1policy-map imposition_tx_shapingclass match_exp1shape average 64000 32000queue-limit 200 packetsinterface POS0/0frame-relay interface-dlci 100 switchedclass fr_set_exp1interface POS1/0service-policy output imposition_tx_shapingConfiguration Examples for FRoMPLS Traffic Policing and Shaping
•
Attaching a Service Policy to Main Interface: Example
•
Attaching a Service Policy to Main Interface with Map-class: Example
•
Attaching a Service Policy to a Subinterface: Example
•
Frame Relay Customer-facing Interface: Example
•
Per-DLCI Egress Shaping: Example
Attaching a Service Policy to Main Interface: Example
interface POS0/0service-policy input ingress_policyconnect from101 POS0/0 101 l2transportxconnect 5.5.5.5 101 encapsulation mplsAttaching a Service Policy to Main Interface with Map-class: Example
interface POS0/0frame-relay interface-dlci 101 switchedclass dlci_101map-class frame-relay dlci_101service-policy input ingress_policyconnect from101 POS0/0 101 l2transportxconnect 5.5.5.5 101 encapsulation mplsAttaching a Service Policy to a Subinterface: Example
interface POS0/0.1 point-to-pointswitched-dlci 101service-policy input ingress_policyconnect from101 POS0/0 101 l2transportxconnect 5.5.5.5 101 encapsulation mpls

