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.
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).
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.
•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
•Feature Information 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:
•Applying QoS Features Using the MQC
•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.
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.
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.
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.
•Enabling a Service Policy in ATM PVP Mode (required)
•Enabling Traffic Shaping in ATM PVP Mode (required)
•Enabling Matching of ATM VCIs (required)
You can enable a service policy in ATM PVP mode. You can also enable a service policy on PVP on a multipoint subinterface.
The show policy-map interface command does not display service policy information for ATM interfaces.
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
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).
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
You can match on an ATM VCI or range of VCIs, using the match atm-vci command in class-map configuration mode.
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.
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
•Example: Enabling Traffic Shaping in ATM PVP Mode
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
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
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.
|
|
|
---|---|---|
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 |