Table Of Contents
MQC Policy Map Support on Configured VC Range
Information About MQC Policy Map Support on Configured VC Range
How to Configure Policy Maps on ATM VC Ranges
Attaching QoS Policies to an ATM PVC Range
Attaching QoS Policies to an Individual PVC within an ATM PVC Range
Configuration Examples for Policy Map Support on Configured VC Range
Attaching QoS Service Policies to a Range of ATM PVCs: Example
Attaching QoS Service Policies to an Individual PVC Within a Range of ATM PVCs: Example
MQC Policy Map Support on Configured VC Range
First Published: February 28, 2006Contents
•Information About MQC Policy Map Support on Configured VC Range
•How to Configure Policy Maps on ATM VC Ranges
•Configuration Examples for Policy Map Support on Configured VC Range
Information About MQC Policy Map Support on Configured VC Range
The MQC Policy Map Support on Configured VC Range feature simplifies the configuration of ATM VC ranges by allowing you to attach policy maps on a range of ATM VCs or on a specific VC within a range of VCs.
How to Configure Policy Maps on ATM VC Ranges
To configure MQC policy maps on ATM VC ranges, perform the following configuration task:
•Attaching QoS Policies to an ATM PVC Range
•Attaching QoS Policies to an Individual PVC within an ATM PVC Range
Attaching QoS Policies to an ATM PVC Range
Use the following configuration task to attach a QoS policy to a range of ATM PVCs.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm slot/module/port
4. range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
5. service-policy [input | output] policy-map-name
DETAILED STEPS
Attaching QoS Policies to an Individual PVC within an ATM PVC Range
Use the following configuration task to attach a QoS policy to an individual PVC within a range of ATM PVCs.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm slot/module/port
4. range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
5. pvc-in-range [pvc-name] vpi/vci
6. service-policy [input | output] policy-map-name
DETAILED STEPS
Configuration Examples for Policy Map Support on Configured VC Range
This section provides the following configuration examples:
•Attaching QoS Service Policies to a Range of ATM PVCs: Example
•Attaching QoS Service Policies to an Individual PVC Within a Range of ATM PVCs: Example
Attaching QoS Service Policies to a Range of ATM PVCs: Example
The following example configuration shows how to attach policy maps to a range of ATM PVCs. In the example, the service policy named voice is attached to the range of ATM PVCs 1/32 to 1/34. The router applies the service policy to all of the PVCs within the PVC range.
Router(config)# interface atm 2/0/0Router(config-if)# range pvc 1/32 1/34Router(config-if-atm-range)# service-policy input voiceAttaching QoS Service Policies to an Individual PVC Within a Range of ATM PVCs: Example
The following example configuration shows how to attach policy maps to a specific PVC within a PVC range. In the example, the service policy named data is attached to PVC 1/33 within the PVC range 1/32 to 1/34. The router applies the service policy to only PVC 1/33.
Router(config)# interface atm 2/0/0Router(config-if)# range pvc 1/32 1/34Router(config-if-atm-range)# service-policy input voiceRouter(config-if-atm-range)# pvc-in-range 1/33Router(config-if-atm-range-vc)# service-policy input dataAdditional References
The following sections provide references related to MQC Policy Map Support on VC Range.
Related Documents
Related Topic Document TitleMQC policy maps
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2
MIBs
Technical Assistance
Command Reference
This feature uses no new or modified commands.
service-policy
To attach a policy map to an input interface or virtual circuit (VC), or an output interface or VC, to be used as the service policy for that interface or VC, use the service-policy command. To remove a service policy from an input or output interface or input or output VC, use the no form of this command.
service-policy [type access-control] {input | output} policy-map-name
no service-policy [type access-control] {input | output} policy-map-name
Syntax Description
Defaults
No service policy is specified.
Command Modes
Interface configuration
VC submode (for a standalone VC)
Bundle-vc configuration (for ATM VC bundle members)
PVC range subinterface configuration (for a range of ATM PVCs)
PVC-in-range configuration (for an individual PVC within a PVC range)
Map-class configuration (for Frame Relay VCs)Command History
Usage Guidelines
You can attach a single policy map to one or more interfaces or one or more VCs to specify the service policy for those interfaces or VCs.
Currently a service policy specifies class-based weighted fair queueing (CBWFQ). The class policies comprising the policy map are then applied to packets that satisfy the class map match criteria for the class.
To successfully attach a policy map to an interface or a VC, the aggregate of the configured minimum bandwidths of the classes comprising the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC.
To enable LLQ for Frame Relay (priority queueing (PQ)/CBWFQ), you must first enable Frame Relay Traffic Shaping (FRTS) on the interface using the frame-relay traffic-shaping command in interface configuration mode. You then attach an output service policy to the Frame Relay VC using the service-policy command in map-class configuration mode.
To successfully attach a policy map to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC. For a Frame Relay VC, the total amount of bandwidth allocated must not exceed the minimum committed information rate (CIR) configured for the VC less any bandwidth reserved by the frame-relay voice bandwidth or frame-relay ip rtp priority map-class commands. If not configured, the minimum CIR defaults to half of the CIR.
Configuring CBWFQ on a physical interface is only possible if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use WFQ by default. Other interfaces use FIFO by default. Enabling CBWFQ on a physical interface overrides the default interface queueing method. Enabling CBWFQ on an ATM permanent virtual circuit (PVC) does not override the default queueing method.
When you attach a service policy with CBWFQ enabled to an interface, commands related to fancy queueing such as commands pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED) are available using the modular quality of service command line interface (MQC). However, you cannot configure these features directly on the interface until you remove the policy map from the interface.
You can modify a policy map attached to an interface or a VC, changing the bandwidth of any of the classes comprising the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amounts for all classes comprising the policy map, including the modified class bandwidth, less than or equal to 75 percent of the interface bandwidth or the VC bandwidth. If the new aggregate bandwidth amount exceeds 75 percent of the interface bandwidth or VC bandwidth, the policy map is not modified.
Cisco 10000 Series Router Usage Guidelines
The Cisco 10000 series router does not support applying CBWFQ policies to unspecified bit rate (UBR) VCs.
To successfully attach a policy map to an interface or a VC, the aggregate of the configured minimum bandwidths of the classes comprising the policy map must be less than or equal to 99 percent of the interface bandwidth or the bandwidth allocated to the VC. If you attempt to attach a policy map to an interface when the sum of the bandwidth assigned to classes is greater than 99 percent of the available bandwidth, the router logs a warning message and does not allocate the requested bandwidth to all of the classes. If the policy map is already attached to other interfaces, it is removed from them.
The total bandwidth is the speed (rate) of the ATM layer of the physical interface. The router converts the minimum bandwidth that you specify to the nearest multiple of 1/255 (ESR-PRE1) or 1/65535 (ESR-PRE2) of the interface speed. When you request a value that is not a multiple of 1/255 or 1/65535, the router chooses the nearest multiple.
The bandwidth percentage is based on the interface bandwidth. In a hierarchical policy, the bandwidth percentage is based on the nearest parent shape rate.
By default, a minimum bandwidth guaranteed queue has buffers for up to 50 milliseconds of 256-byte packets at line rate, but not less than 32 packets.
For Cisco IOS Release 12.0(22)S and later releases, to enable LLQ for Frame Relay (priority queueing (PQ)/CBWFQ) on the Cisco 10000 series router, first create a policy map and then assign priority to a defined traffic class using the priority command. For example, the following sample configuration shows how to configure a priority queue with a guaranteed bandwidth of 8000 kbps. In the example, the Business class in the policy map named Gold is configured as the priority queue. The Gold policy also includes the Non-Business class with a minimum bandwidth guarantee of 48 kbps. The Gold policy is attached to serial interface 2/0/0 in the outbound direction.
class-map Businessmatch ip precedence 3policy-map Goldclass Businessprioritypolice 8000class Non-Businessbandwidth 48interface serial 2/0/0frame-relay encapsulationservice-policy output GoldExamples
The following example shows how to attach the service policy map called policy9 to data-link connection identifier (DLCI) 100 on output serial subinterface 1 and enable LLQ for Frame Relay:
interface Serial1/0.1 point-to-pointframe-relay interface-dlci 100class fragment!
map-class frame-relay fragmentservice-policy output policy9The following example shows how to attach the service policy map called policy9 to input serial interface 1:
interface Serial1service-policy input policy9The following example shows how to attach the service policy map called policy9 to the input PVC called cisco:
pvc cisco 0/34 service-policy input policy9vbr-nt 5000 3000 500 precedence 4-7The following example shows how to attach the policy called policy9 to output serial interface 1 to specify the service policy for the interface and enable CBWFQ on it:
interface serial1service-policy output policy9The following example shows how to attach the service policy map called policy9 to the output PVC called cisco:
pvc cisco 0/5 service-policy output policy9 vbr-nt 4000 2000 500 precedence 2-3Cisco 10000 Series Router Examples
The following example shows how to attach the service policy named user_policy to data link connection identifier (DLCI) 100 on serial subinterface 1/0/0.1 for outbound packets.
interface serial 1/0/0.1 point-to-pointframe-relay interface-dlci 100service-policy output user_policy
Note You must be running Cisco IOS Release 12.0(22)S or later releases to attach a policy to a DLCI in this way. If you are running a release prior to Cisco IOS Release 12.0(22)S, attach the service policy as described in the previous configuration examples using the Frame Relay legacy commands.
The following example shows how to attach a QoS service policy named bronze to PVC 0/101 on the ATM subinterface 3/0/0.1 for inbound traffic.
interface atm 3/0/0
atm pxf queuinginterface atm 3/0/0.1
pvc 0/101service-policy input bronze
The following example shows how to attach a service policy named myQoS to the physical Gigabit Ethernet interface 1/0/0 for inbound traffic. VLAN 4, configured on the GigabitEthernet subinterface 1/0/0.3, inherits the service policy of the physical Gigabit Ethernet interface 1/0/0.
interface GigabitEthernet 1/0/0
service-policy input myQoS
interface GigabitEthernet 1/0/0.3encapsulation dot1q 4The following example shows how to apply the policy map named policy1 to the virtual template named virtual-template1 for all inbound traffic. In this example, the virtual template configuration also includes CHAP authentication and point-to-point protocol (PPP) authorization and accounting.
interface virtual-template1ip unnumbered Loopback1no peer default ip addressppp authentication chap vpn1ppp authorization vpn1ppp accounting vpn1service-policy policy1The following example shows how to attach the service policy map called voice to ATM VC 2/0/0 within a PVC range of a total of 3 PVCs and enable PVC range configuration mode where a point-to-point subinterface is created for each PVC in the range. Each PVC created as part of the range has the voice service policy attached to it.
configure terminalinterface atm 2/0/0range pvc 1/50 1/52service-policy input voiceThe following example shows how to attach the service policy map called voice to ATM VC 2/0/0 within a PVC range, where every VC created as part of the range has the voice service policy attached to it. The exception is PVC 1/51, which is configured as an individual PVC within the range and has a different service policy called data attached to it in PVC-in-range configuration mode.
configure terminalinterface atm 2/0/0range pvc 1/50 1/52service-policy input voicepvc-in-range 1/51service-policy input dataRelated Commands
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, 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, 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, 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. (0601R)
Copyright © 2006 Cisco Systems, Inc. All rights reserved.