Cisco IOS XE Multiprotocol Label Switching Configuration Guide, Release 2 - QoS Policy Support on L2VPN ATM PVPs [Cisco IOS XE Software]

Table Of Contents

QoS Policy Support on L2VPN ATM PVPs

Finding Feature Information

Contents

Prerequisites for QoS Policy Support on L2VPN ATM PVPs

Restrictions for QoS Policy Support on L2VPN ATM PVPs

Information About QoS Policy Support on L2VPN ATM PVPs

The MQC Structure

Elements of a Traffic Class

Elements of a Traffic Policy

How to Configure QoS Policy Support on L2VPN ATM PVPs

Enabling a Service Policy in ATM PVP Mode

Restrictions

Enabling Traffic Shaping in ATM PVP Mode

Enabling Matching of ATM VCIs

Restrictions

Configuration Examples for QoS Policy Support on L2VPN ATM PVPs

Enabling Traffic Shaping in ATM PVP Mode: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for QoS Policy Support on L2VPN ATM PVPs

QoS Policy Support on L2VPN ATM PVPs

First Published: February 27, 2009

Last Updated: May 4, 2009

This feature enables you to configure Quality of Service (QoS) service policies in ATM permanent virtual path (PVP) mode for Layer 2 Virtual Private Networks (L2VPNs).

Finding Feature Information

For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for QoS Policy Support on L2VPN ATM PVPs" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for QoS Policy Support on L2VPN ATM PVPs

•Restrictions for QoS Policy Support on L2VPN ATM PVPs

•Information About QoS Policy Support on L2VPN ATM PVPs

•How to Configure QoS Policy Support on L2VPN ATM PVPs

•Configuration Examples for QoS Policy Support on L2VPN ATM PVPs

•Additional References

•Feature Information for QoS Policy Support on L2VPN ATM PVPs

Prerequisites for QoS Policy Support on L2VPN ATM PVPs

Before configuring QoS policies on L2VPN ATM PVPs, you should understand the concepts and configuration instructions in the following documents:

•Any Transport over MPLS

•Applying QoS Features Using the MQC

Restrictions for QoS Policy Support on L2VPN ATM PVPs

The following restrictions apply to the QoS Policy Support on L2VPN ATM PVPs feature:

•Queueing-based policies are not supported in ATM PVP mode and virtual circuit (VC) mode at the same time under the same main interface. However, nonqueueing policies can be mixed. For example, you can configure a nonqueueing policy in PVP mode and configure queueing policies on in VC mode under the same main interface. Similarly, you can configure a queueing policy in PVP mode and configure nonqueueing policies in VC mode in the input or output direction.

•ATM PVP mode does not support sessions.

•When you enable a policy in PVP mode, do not configure ATM rates on the VCs that are part of the PVP. The VCs should be unspecified bit rate (UBR) VCs only.

•If VCs are part of a PVP that has a policy configured, you cannot configure ATM VC traffic shaping.

•You cannot configure a queueing policy on an ATM PVP with UBR.

•You cannot configure queueing-based policies with UBR traffic shaping.

Information About QoS Policy Support on L2VPN ATM PVPs

Before configuring the QoS Policy Support on L2VPN ATM PVPs feature, you should understand the following concepts:

•The MQC Structure

•Elements of a Traffic Class

•Elements of a Traffic Policy

The MQC Structure

The MQC structure allows you to define a traffic class, create a traffic policy, and attach the traffic policy to an interface.

The MQC structure consists of the following three high-level steps.

Step 1 Define a traffic class by using the class-map command. A traffic class is used to classify traffic.

Step 2 Create a traffic policy by using the policy-map command. (The terms traffic policy and policy map are often synonymous.) A traffic policy (policy map) contains a traffic class and one or more QoS features that will be applied to the traffic class. The QoS features in the traffic policy determine how to treat the classified traffic.

Step 3 Attach the traffic policy (policy map) to the interface by using the service-policy command.

Elements of a Traffic Class

A traffic class contains three major elements: a traffic class name, a series of match commands, and, if more than one match command is used in the traffic class, instructions on how to evaluate these match commands.

The match commands are used for classifying packets. Packets are checked to determine whether they meet the criteria specified in the match commands; if a packet meets the specified criteria, that packet is considered a member of the class. Packets that fail to meet the matching criteria are classified as members of the default traffic class.

Elements of a Traffic Policy

A traffic policy contains three elements: a traffic policy name, a traffic class (specified with the class command), and the command used to enable the QoS feature.

The traffic policy (policy map) applies the enabled QoS feature to the traffic class once you attach the policy map to the interface (by using the service-policy command).

Note A packet can match only one traffic class within a traffic policy. If a packet matches more than one traffic class in the traffic policy, the first traffic class defined in the policy will be used.

How to Configure QoS Policy Support on L2VPN ATM PVPs

The following sections explain how to configure QOS operations in ATM PVP mode.

•Enabling a Service Policy in ATM PVP Mode (required)

•Enabling Traffic Shaping in ATM PVP Mode (required)

•Enabling Matching of ATM VCIs (required)

Enabling a Service Policy in ATM PVP Mode

You can enable a service policy in ATM PVP mode. You can also enable a service policy on PVP on a multipoint subinterface.

Restrictions

The show policy-map interface command does not display service policy information for ATM interfaces.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atm slot/subslot/port[.subinterface]

4. atm pvp vpi l2transport

5. service-policy [input | output] policy-map-name

6. xconnect peer-router-id vcid encapsulation mpls

7. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atm slot/subslot/port[.subinterface]
Example:

Router(config)# interface atm1/0/0

Defines the interface and enters interface configuration mode.

Step 4

atm pvp vpi l2transport
Example:

Router(config-if)# atm pvp 1 l2transport

Specifies that the PVP is dedicated to transporting ATM cells and enters l2transport PVP configuration mode.

•The l2transport keyword indicates that the PVP is for cell relay. This mode is for Layer 2 transport only; it is not for regular PVPs.

Step 5

service-policy [input | output] policy-map-name
Example:

Router(config-if-atm-l2trans-pvp)# service policy input pol1

Enables a service policy on the specified PVP.

Step 6

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-if-atm-l2trans-pvp)# xconnect 10.0.0.1 123 encapsulation mpls

Binds the attachment circuit to a pseudowire VC.

•The syntax for this command is the same as for all other Layer 2 transports.

Step 7

end
Example:

Router(config-if-atm-l2trans-pvp)# end

Exits l2transport PVP configuration mode and returns to privileged EXEC mode.

Enabling Traffic Shaping in ATM PVP Mode

Traffic shaping commands are supported in PVP mode. For egress VP shaping, one configuration command is supported for each ATM service category. The supported service categories are constant bit rate (CBR), UBR, variable bit rate-nonreal time (VBR-NRT), and variable bit rate real-time(VBR-RT).

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atm slot/subslot/port[.subinterface]

4. atm pvp vpi l2transport

5. ubr pcr

or

cbr pcr

or

vbr-nrt pcr scr mbs

or

vbr-rt pcr scr mbs

6. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atm slot/subslot/port[.subinterface]
Example:

Router(config)# interface atm1/0/0

Defines the interface and enters interface configuration mode.

Step 4

atm pvp vpi l2transport
Example:

Router(config-if)# atm pvp 1 l2transport

Specifies that the PVP is dedicated to transporting ATM cells and enters l2transport PVP configuration mode.

•The l2transport keyword indicates that the PVP is for cell relay. This mode is for Layer 2 transport only; it is not for regular PVPs.

Step 5

ubr pcr
or
cbr pcr
or
vbr-nrt pcr scr mbs
or
vbr-rt pcr scr mbs
Example:

Router(config-if-atm-l2trans-pvp)# cbr 1000

Enables traffic shaping in ATM PVP mode.

•pcr = peak cell rate

•scr = sustain cell rate

•mbs = maximum burst size

Step 6

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-if-atm-l2trans-pvp)# xconnect 10.0.0.1 123 encapsulation mpls

Binds the attachment circuit to a pseudowire VC.

•The syntax for this command is the same as for all other Layer 2 transports.

Enabling Matching of ATM VCIs

You can match on an ATM VCI or range of VCIs, using the match atm-vci command in class-map configuration mode.

Restrictions

When you configure the match atm-vci command in class-map configuration mode, you can add this class map to a policy map that can be attached only to an ATM VP.

SUMMARY STEPS

1. enable

2. configure terminal

3. class-map class-map-name [match-all | match-any]

4. match atm-vci vc-id [- vc-id]

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

class-map class-map-name [match-all | match-any]
Example:

Router(config)# class-map class1

Creates a class map to be used for matching traffic to a specified class, and enters class-map configuration mode.

Step 4

match atm-vci vc-id [- vc-id]
Example:

Router(config-cmap)# match atm-vci 50

Enables packet matching on an ATM VCI or range of VCIs. The range is 32 to 65535.

Note You can use the match not command to remove the match criteria.

Step 5

end
Example:

Router(config-cmap)# end

(Optional) Returns to privileged EXEC mode.

Configuration Examples for QoS Policy Support on L2VPN ATM PVPs

The following section shows an example of the QoS Policy Support on L2VPN ATM PVPs feature:

•Enabling Traffic Shaping in ATM PVP Mode: Example

Enabling Traffic Shaping in ATM PVP Mode: Example

The following example enables traffic shaping in ATM PMP mode.
int atm 1/0/0
   atm pvp 100 l2transport
       ubr 1000
       xconnect 10.11.11.11 777 encapsulation mpls
   atm pvp 101 l2transport
       cbr 1000
       xconnect 10.11.11.11 888 encapsulation mpls
   atm pvp 102 l2transport
       vbr-nrt 1200 800 128
       xconnect 10.11.11.11 999 encapsulation mpls
Additional References

The following sections provide references related to the QoS Policy Support on L2VPN ATM PVPs feature.

Related Documents

Related Topic

Document Title

Description of commands associated with MPLS and MPLS applications

Cisco IOS Multiprotocol Label Switching Command Reference

Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC)

Applying QoS Features Using the MQC

Any Transport over MPLS

Any Transport over MPLS

Standards

Standard

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

—

MIBs

MIB

MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To locate and download MIBs for selected platforms, Cisco IOS XE software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFC

Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport

Feature Information for QoS Policy Support on L2VPN ATM PVPs

Table 1 lists the features in this module and provides links to specific configuration information.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

Table 1 Feature Information for QoS Policy Support on L2VPN ATM PVPs

Feature Name

Releases

Feature Information

QoS Policy Support on L2VPN ATM PVPs

Cisco IOS XE Release 2.3

This feature enables you to configure Quality of Service (QoS) service policies in ATM permanent virtual path (PVP) mode for Layer 2 Virtual Private Networks (L2VPNs).

The following sections provide information about this feature:

•Information About QoS Policy Support on L2VPN ATM PVPs

•How to Configure QoS Policy Support on L2VPN ATM PVPs

The following commands were introduced or modified: cbr, match atm-vci, service-policy, ubr, vbr-nrt, vbr-rt.

Cell-Based ATM Shaping per PVP

Cisco IOS XE Release 2.3

This feature was introduced for Cisco ASR 1000 Series Aggregation Services Routers.

The following sections provide information about this feature:

•Information About QoS Policy Support on L2VPN ATM PVPs

•How to Configure QoS Policy Support on L2VPN ATM PVPs

•Enabling Traffic Shaping in ATM PVP Mode

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0907R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2009 Cisco Systems, Inc. All rights reserved.