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 mplsFrame Relay Customer-facing Interface: Example
int p0/0frame-relay interface-dlci 100 switchedclass fr_100frame-relay interface-dlci 101 switchedclass fr_101frame-relay interface-dlci 102 switchedclass fr_102service output match-qos-discardint p0/0.200switched-dlci 200service input 2R3C_policer_color_blindint p0/0.201switched-dlci 201service input 2R3C_policer_color_awareint p0/0.202switched-dlci 202service input set_exp_from_frdemap-class frame-relay fr_100service input 2R3C_policer_color_blindmap-class frame-relay fr_101service input 2R3C_policer_color_awaremap-class frame-relay fr_102service input set_exp_from_frdePer-DLCI Egress Shaping: Example
policy-map shaper_16Kbpsclass class-defaultshape average 16000map-class frame-relay fr_100service-policy output shaper_16Kbpsint p0/0frame-relay interface-dlci 100 switchedclass fr_100How to Configure ATMoMPLS Traffic Policing
ATMoMPLS policing follows the ATM Forum Traffic Management specification version 4.0. The Generic Cell Rate Algorithm (GCRA) policer is implemented for the ATM service category conformances of CBR.1, VBR.1, VBR.2, VBR.3 and UBR.1. The GCRA policing complies with International Telecommunications Union Recommendation I.371. This section discusses AAL5oMPLS only.
Policer actions for AAL5 are like the GCRA implementation, except that the algorithm is cell-based. The following statements describe the policer actions of conform, exceed, and violate in terms of Peak Cell Rate (PCR) and Sustainable Cell Rate (SCR):
•
AAL5 Packet is conform: If all the cells in the AAL5 packet passed PCR and SCR bucket checks
•
AAL5 Packet is exceed: If at least one cell in the AAL5 packet has failed SCR bucket check
•
AAL5 Packet is violate: If at least one cell in the AAL5 packet has failed PCR bucket check
For AAL5 packet exceed, the Martini Control Word "C" bit is set. For AAL5 packet violate, the packet is dropped (if violate-action drop is configured). For example, if one cell in the AAL5 packet has violated the GCRA PCR check, the entire AAL5 packet is dropped.
OAM cells are subject to the same policing as user cells, that is, here is no special treatment to OAM cells while policing, if the policy is configured for a class-default class. OAM cells can be exempted from policing, if the policy is configured for a class which has match not atm oam-cell. However, all OAM types are treated alike.
Support is extended for set-mpls-exp-imposition-transmit and set-clp-transmit in conform action and multiple action modes.
ATMoMPLS supports cell-packing with the cell-packing criteria being OAM-based, CLP-based and policer-result based. If the MQC policer configuration contains set-mpls-exp-imposition-transmit, then a policer-result based cell-packing is chosen. This allows the MPLS packets with a specific EXP value to be packed into one packet. However OAM cells are still packed separately from the user cells.
Table 4 lists the ATMoMPLS policer commands and options supported in Cisco IOS Release 12.0(32)S.
For further information on OAM-based traffic policing and shaping see, QoS: Match ATM OAM at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/gsatmoam.htmFor further information on the ATM Cell-based Policer, see QoS:ATM Cell-Based Policer at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fscbp.htmFor further information on CLP-based traffic policing and shaping see, QoS: ATM CLP-Based Queue Limit at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12sqatcl.htmConfiguring ATMoMPLS Policer
•
Variable Bit Rate —VBR.2 and VBR.3 Without Cell Tagging
•
Variable Bit Rate —VBR.3 with Cell Tagging
•
Policing Configuration Excluding OAM Cells
Constant Bit Rate—CBR.1
CBR.1 is real-time traffic and only one rate is specified (PCR) to describe a CBR service category. All traffic exceeding the PCR is dropped. Please note that delay-tolerate (CDVT) needs to be specified for CBR conformance. Delay-tolerance is specified in microseconds.
policy CBR1class class-defaultpolice rate <PCR> cps delay-tolerance <CDVT> usconform-action set-mpls-exp-imposition- transmit <EXP value>exceed-action dropThe same policy can be represented as percentage of the interface rate units, as follows:
policy CBR1class class-defaultpolice rate <PCR in percent> percent delay-tolerance <CDVT> usconform-action set-mpls-exp-imposition-transmit <EXP value>exceed-action dropUnspecified Bit Rate—UBR.1
UBR.1 is non-real-time traffic and only one rate is specified (PCR) to describe a UBR service category. All traffic exceeding the PCR is dropped. Please note that delay-tolerate (CDVT) needs to be specified for UBR conformance, but it can much higher compared to the delay-tolerance specified for a CBR connection. Also, note that there is no difference as far as policing is concerned between CBR and UBR service. So the policy-maps remain same. An operator typically sets the EXP value differently between a CBR and UBR service. Delay-tolerance is specified in microseconds.
Variable Bit Rate —VBR.1
VBR.1 is real-time as well as non-real-time traffic and two rates are specified (PCR and SCR) to describe a VBR service category. All traffic exceeding the PCR is dropped. Delay-tolerate (CDVT) must be specified for VBR conformance. Delay-tolerance is specified in microseconds. In addition, atm-mbs can also be specified to represent the burst allowed on an SCR bucket.
policy VBR1class class-defaultpolice rate <SCR> cps atm-mbs <MBS in cells> peak-rate <PCR> delay-tolerance <CDVT> usconform-action set-mpls-exp-imposition- transmit <EXP value>exceed-action dropThe same policy can be represented as percentage of the interface rate units, as in the following example:
policy VBR1class class-defaultpolice rate <SCR in percent> percent atm-mbs <MBS in cells>peak-rate <PCR in percent> percent delay-tolerance <CDVT> usconform-action set-mpls-exp-imposition-transmit <EXP value>exceed-action dropVariable Bit Rate —VBR.2 and VBR.3 Without Cell Tagging
VBR.2 and VBR.3 are real-time as well as non-real-time traffic and two rates are specified (PCR and SCR) to describe a VBR service category. All traffic exceeding the PCR is dropped. Please note that delay-tolerate (CDVT) needs to be specified for VBR conformance. Delay-tolerance is specified in microseconds. In addition, atm-mbs can also be specified which represents the burst that can be allowed on an SCR bucket.
The significant difference between the VBR.2/VBR.3 and VBR.1 is that the SCR bucket check is made only for CLP0 cells, that means CLP1 cells are not passed through the GCRA algorithm.
class atm_not_clpmatch not atm clppolicy childclass atm_not_clp<any one form of the police below>police rate <SCR in cps> atm-mbs <MBS in cells>conform-action set-mpls-exp-imposition-transmit <EXP value>exceed-action droppolice rate <SCR in percent> percent atm-mbs <MBS in cells> usconform-action set-mpls-exp-imposition-transmitexceed-action droppolicy VBR2class class-default<any one form of the police below>police rate <PCR in cps> delay-tolerance <cdvt in us>conform-action transmitexceed-action droppolice rate <PCR in percent> percent delay-tolerance <cdvt in us> usconform-action transmitexceed-action dropservice-policy childVariable Bit Rate —VBR.3 with Cell Tagging
VBR.3 allows for tagging of the cells in case the SCR check failed.
class atm_not_clpmatch not atm clppolicy childclass atm_not_clp<any one form of the police below>police rate <SCR in cps> atm-mbs <MBS in cells>conform-action set-mpls-exp-imposition-transmit <EXP value>exceed-action set-clp-transmitexceed-action set-mpls-exp-imposition-transmit <EXP value>police rate <SCR in percent> percent atm-mbs <MBS in cells> usconform-action set-mpls-exp-imposition-transmitexceed-action set-clp-transmitexceed-action set-mpls-exp-imposition-transmit <EXP value>policy VBR3class class-default<any one form of the police below>police rate <PCR in cps> delay-tolerance <cdvt in us>conform-action transmitexceed-action droppolice rate <PCR in percent> percent delay-tolerance <cdvt in us> usconform-action transmitexceed-action dropservice-policy child
Note
The set-mpls-exp-imposition-transmit <EXP value> can only be set in the parent policy. When you set the set-mpls-exp-imposition-transmit <EXP value> in the parent policy the child conform-action set-mpls-exp-imposition-transmit <EXP value> automatically takes the same <EXP value>. Only conform-action transmit is supported in the child policy. If match not atm clp is not configured, attempting to configure a policy will trigger an error.
Policing Configuration Excluding OAM Cells
class match-all atm_not_clp_not_oammatch not atm clpmatch not atm oamclass match-all atm_not_oammatch not atm oampolicy childclass atm_not_clp_not_oam<any one form of the police below>police rate <SCR in cps> atm-mbs <MBS in cells>conform-action set-mpls-exp-imposition-transmit <EXP value>exceed-action set-clp-transmitexceed-action set-mpls-exp-imposition-transmit <EXP value>police rate <SCR in percent> percent atm-mbs <MBS in cells> usconform-action set-mpls-exp-imposition-transmitexceed-action set-clp-transmitexceed-action set-mpls-exp-imposition-transmit <EXP value>policy VBR3_non_OAMclass atm_not_oam<any one form of the police below>police rate <PCR in cps> delay-tolerance <cdvt in us>conform-action transmitexceed-action droppolice rate <PCR in percent> percent delay-tolerance <cdvt in us> usconform-action transmitexceed-action dropservice-policy childHow to Configure ATMoMPLS Traffic Shaping
The following sections on ATMoMPLS traffic shaping relate only to Cisco 12000 ISE ATM (Engine 3 and Engine 5) line cards.
•
Configuring ATMoMPLS Per VC/VP Disposition Shaping
•
Configuring ATMoMPLS Per-class Imposition Shaping
The match atm oam and the match atm clp commands are now supported for ATM over MPLS. Matching on OAM cells and setting the MPLS EXP value is implemented on the imposition router.
For further information on QoS: Match ATM OAM
Note
ATM over MPLS supports cell-packing with the criteria of OAM-based, CLP-based, or policer-result based packing. If the MQC policer configuration contains the set-mpls-exp-imposition-transmit policing action, then a policer-result based cell-packing is chosen. If the above configuration is present, the packing criteria is changed to CLP based packing. This will allow the MPLS packets with a specific EXP value and CLP to be packed into one packet. Please note that OAM cells will still be packed separately.
Table 5 lists the ATMoMPLS traffic shaping and WRED configuration commands supported in Cisco IOS Release 12.0(32)S.
Configuring ATMoMPLS Per VC/VP Disposition Shaping
Per-VC shaping is implemented in the SAR and includes support for CBR, UBR and VBR shaping. The CLI for ATM shaping is not implemented for the Modular Quality of Service CLI (MQC) in Cisco IOS Release 12.0(32)S.
Constant Bit Rate Shaping—CBR
For Constant bit rate (CBR) shaping you must specify Conformance Definitions for PCR as shown in the following example:
interface atm 1/0pvp 100 l2transportcbr <PCR 38 - 622000 kbps>Variable Bit Rate Real Time Shaping —VBR-rt
For Variable Bit Rate Real Time (VBR-rt) shaping you must specify Conformance Definitions for PCR and SCR, as shown in the following example:
interface atm 1/0pvc 1/50vbr-rt <PCR 38 - 622000 kbps> <SCR 38 - PCR kbps>Variable Bit Rate Non-Real Time Shaping—VBR-nrt
For Variable Bit Rate Non-Real Time (VBR-nrt) shaping you must specify Conformance Definitions for PCR and SCR, as shown in the following example:
interface atm 1/0pvc 1/50 l2transportvbr-nrt <PCR 38 - 622000 kbps> <SCR>Unspecified Bit Rate Shaping—UBR
For Unspecified Bit Rate Shaping (UBR) shaping you must specify Conformance Definitions for PCR, as shown in the following example:
interface atm 1/0pvc 1/50 l2transportubr <PCR 38 - 6220000 kbps>For further information see, QoS: ATM-CLP and Layer 2 CoS-Based WRED at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12swred.htmConfiguring ATMoMPLS Per-class Imposition Shaping
Per-class imposition shaping is not supported for ATMoMPLS in Cisco IOS Release 12.0(32)S.
Configuration Examples for ATMoMPLS
Attaching Service Policy to Permanent Virtual Circuit: Example
interface ATM1/0.1 point-to-pointpvc 1/101 l2transportxconnect 5.5.5.5 1145 encapsulation mplsservice-policy input ingress_policyMatching on ATM OAM Cells: Example
Class-map atm-oammatch atm oam-cellpolicy-map atm-oamclass atm-oamset mpls experimentalMatching on ATM CLP: Example
Class-map atm-clpMatch atm clpPolicy-map atsm-clpClass atm-clpSet mpls exp <EXP value>How to Configure Traffic Policing and Shaping for EoMPLS
•
Configuring EoMPLS Traffic Shaping
Configuring EoMPLS Policers
•
Configuring the EoMPLS One-Rate Two-Color Policer
•
Configuring the EoMPLS Two-Rate Three-Color Policer
EoMPLS Policer Restrictions
•
The color-aware policer feature is supported for E0MPLS on Engine 3 and Engine 5 based line cards for Cisco 12000 starting in 32S.
•
The one-rate two-color policer in color-blind mode is supported for EoMPLS on Engine 3 and Engine 5 based line cards for Cisco 12000.
•
Two-rate three-color policer cannot be used in hierarchical policy which matches on VLAN IDs.
Configuring the EoMPLS One-Rate Two-Color Policer
In the following example, packets that exceed the policer criteria are dropped:
police cir 64000 bc 10000 be 20000 conform-action transmit exceed-action dropConfiguring the EoMPLS Two-Rate Three-Color Policer
Two-rate three-color policing can be configured for EoMPLS, Ethernet Local switching, VLANS, and Interworking in either the color-blind or the color-aware mode.
In the following example, traffic that exceeds the committed information rate (CIR), but is less than or equal to the peak information rate (PIR) is set with an experimental bit value of 5. Traffic that exceeds the PIR is dropped.
police cir 64000 bc 10000 pir 128000 be 20000 conform transmit exceed-action set-experimental-transmit 5 violate-action dropTo make the policer color-aware .1p is used for color with the flexibility to use a single value of .1p COS or multiple values to represent the conform and exceed actions. For example:
class-map match-any greenmatch cos 5class-map match-any yellowmatch cos 4match cos 3policy-map 2R3C_CAclass class-defaultpolice cir 1600000 pir 3200000conform-color green exceed-color yellowconform-action set-mpls-exp-transmit 3exceed-action set-mpls-exp-transmit 4violate-action dropinterface Gi0/0.100service input 2R3C_policer_color_blindConfiguring 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
Table 7 lists the EoMPLS traffic shaping and WRED commands supported for EoMPLS in Cisco IOS Release 12.0(32)S.
Configuring EoMPLS Per-VLAN Disposition Shaping
Per-VLAN egress traffic shaping at disposition is supported as shown in the following hierarchical service policy:
policy-map parentclass-map class-defaultshape average 128000000service-policy childpolicy-map childclass match_qos3set cos 3shape average 160000000bandwidth percent 5class match_qos12set cos 1shape average 64000000random-detect discard-class-basedrandom-detect discard-class 1 500 packets 1000 packetsrandom-detect discard-class 2 1000 packets 2000 packetsbandwidth percent 10class class-defaultset cos 4shape average 2560000queue-limit 100 packetsbandwidth percent 1interface GigabitEthernet6/1no ip addressno ip directed-broadcastno negotiation autono cdp enableinterface GigabitEthernet6/1.1encapsulation dot1Q 601no ip directed-broadcastno cdp enablexconnect 8.8.8.8 601 encapsulation mplsservice-policy input set_exp2service-policy output match_qos_discard_cos_parentConfiguring EoMPLS Per-VLAN Imposition Shaping
Per-VLAN input traffic shaping on imposition for EoMPLS sub-interfaces can only match on CoS (802.1p bits) or class-default, as shown in the following configuration:
class-map match_cos1match cos 1policy-Map input_shaping_policyclass match_cos1shape average 128000000interface GigabitEthernet6/1.1encapsulation dot1Q 601no ip directed-broadcastno cdp enablexconnect 8.8.8.8 601 encapsulation mplsservice-policy input input_shaping_policyConfiguring EoMPLS Per-Class Disposition Shaping
For EoMPLS 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 following procedure demonstrates the steps recommended to configure EoMPLS 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 EoMPLS Per-Class Imposition Shaping
On the imposition side, it is possible to use a policy to match on p-bits and set the experimental bits accordingly. In Release 12.0(25)S, on the disposition side, the MPLS experimental bit is copied to p-bits by default. Since Cisco IOS Release 12.0(30)S, you can map any MPLS experimental bit to any p-bit value in the egress side of the disposition router. To do this, an input policy on the Rx disposition card should be created to carry EXP values into the qos-group values. On the Tx disposition card, an output policy should be created to perform a mapping between qos-group and p-bit values as shown in the following example:
Input Policy
policy-map set_qos_discardclass match_exp1set qos-group 1set discard-class 1class match_exp2set qos-group 2set discard-class 2class match_exp3set qos-group 3set discard-class 3Output Policy
policy-map set_cosclass match_qos1set cos 1class match_qos2set cos 2class match_qos3set cos 3Configuration Examples for Ethernet over MPLS
The following sample configurations are listed in this section:
•
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 the Main Interface (Port Mode): Example
int Gigaethernet4/0xconnect 5.5.5.5 1045 encapsulation mplsservice-policy input ingress_policyAttaching Service Policy to Subinterface (VLAN): Example
int Gigaethernet4/0.1encapsulation dot1Q 200xconnect 5.5.5.5 1045 encapsulation mplsservice-policy input ingress_policyEoMPLS Customer-facing Interface Configuration: Example
int Gi0/0service input match-vlan123int Gi0/0.100service input 2R3C_policer_color_blindservice output match_qos_discard_cos_parentint Gi0/0.101service input map_cos_to_expservice output match_qos_discard_cos_parentint Gi0/0.102service input shape_16mbpsservice output match_qos_discard_cos_parentAdditional Configuration Examples for Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Attaching Service Policy to Main Interface (PPP or HDLCoMPLS): Example
interface POS4/0xconnect 5.5.5.5 1045 encapsulation mplsservice-policy input ingress_policyExample Policy Templates
policy-map 2R3C_policer_color_blindclass class-defaultpolice cir ... pir ...policy-map 2R3C_policer_color_awareclass class-defaultpolice cir ... pir ...conform-color match-not-frde exceed-color match-frdepolicy-map 1R2C_policerclass class-defaultpolice cir ...policy-map set_exp_from_frdeclass match-fr-deset mpls exp imp 3class class-defaultset mpls exp imp 2policy-map match-qos-discardclass match_qos3bandwidth percent 5shape average 160000000class match_qos12shape average 64000000random-detect discard-class-basedrandom-detect discard-class 1 500 packets 1000 packetsrandom-detect discard-class 2 1000 packets 2000 packetsbandwidth percent 10class class-defaultshape average 64000000queue-limit 1000 packetsbandwidth percent 1policy-map shape_16mbpsclass class-defaultshape average 16000000policy-map match_qos_discard_cos_parentclass class-defaultshape average 128000000service-policy match_qos_discard_cospolicy-map match_qos_discard_cosclass match_qos3set cos 3shape average 160000000bandwidth percent 5class match_qos12set cos 1shape average 64000000random-detect discard-class-basedrandom-detect discard-class 1 500 packets 1000 packetsrandom-detect discard-class 2 1000 packets 2000 packetsbandwidth percent 10class class-defaultset cos 4shape average 2560000queue-limit 100 packetsbandwidth percent 1policy-map map_cos_to_expclass match_cos1set mpls experimental 1class match_cos2set mpls experimental 2class match_cos3set mpls experimental 1policy-map match-vlan123class match-vlan-1service-policy 2R3C_policer_color_blindclass match-vlan-2service-policy map_cos_to_expclass match-vlan-3service-policy shape_16mbpsAdditional References
The following sections provide references related to Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service):
Related Documents
Standards
MIBs
RFCs
RFCs TitleRFC-2697
A Single-Rate Three-Color Marker
RFC-2698
A Two-Rate Three-Color Marker
RFC 3032
MPLS Label Stack Encoding
RFC 3036
LDP Specification
Technical Assistance
Command Reference
There are no new Cisco IOS commands introduced with this feature.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Copyright © 2006 Cisco Systems, Inc. All rights reserved.
