Configuring QoS Policy Actions and Rules
Available Languages
Table Of Contents
Configuring QoS Policy Actions and Rules
Feature History for QoS Policies
Defining QoS Actions Using a Policy Map
Usage Guidelines for the policy-map Command
Input and Output Policy Actions
Policy Map Actions—Releases Prior to Cisco IOS Release 12.0(17)SL
Policy Map Actions—Cisco IOS Release 12.0(17)SL and Later Releases
Policy Map Actions—Cisco IOS Release 12.0(20)ST and Later Releases
Policy Map Actions—Cisco IOS Release 12.0(22)S and Later Releases
Policy Map Actions—Cisco IOS Release 12.2(31)SB2 and Later Releases
Traffic Subject to QoS Policies
ATM Virtual Circuits Without QoS Policies
Configuration Examples for Creating a Policy Map
Defining QoS Actions in a Policy Map
Verifying QoS Policy Configurations
Verification Example for Service Policies
Configuring QoS Policy Actions and Rules
The second step in creating a QoS service policy is to define how you want the router to handle the packets that match the classification rules you defined in Chapter 2, "Classifying Traffic." The Cisco 10000 series router supports a modular CLI element called a policy map to enable you to configure a QoS policy with the appropriate actions and rules.
This chapter describes how to create QoS policies that the Cisco 10000 series router applies to specific traffic classes. It includes the following topics:
•
Traffic Subject to QoS Policies
•
•
QoS Policies
After the Cisco 10000 series router classifies traffic based on the classification rules applied on an inbound or outbound interface, the router needs to know how to handle the traffic that meets the matching criteria. A modular quality of service command-line interface (MQC) element called a policy map enables you to create QoS policies that tell the router the QoS actions and rules to apply to packets belonging to a particular traffic class.
The following sections describe policy maps and QoS actions:
•
•
•
Feature History for QoS Policies
Defining QoS Actions Using a Policy Map
A policy map associates a traffic class with one or more QoS actions. When configuring a policy map, you specify the name of a class map and configure the actions you want the router to take on the matching traffic. Before you can create class policies in a policy map, the class must have classification criteria configured in a class map. The router supports QoS actions such as marking, policing, and bandwidth distribution.
A single policy map can be attached to multiple interfaces concurrently. 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.
Whenever you modify a class policy in an attached policy map, class-based weighted fair queuing (CBWFQ) is notified and the new classes are installed as part of the policy map in the CBWFQ system.
System Limits for Policy Maps
Table 2 lists the system limits for policy maps supported on the Cisco 10000 series router.
Table 2 System Limits for Policy Maps
Policy Map 2PRE1
All Releases prior to Release 12.0(17)SL
256
16
Release 12.0(17)SL
and later releases256
256
Release 12.0(25)SX
and later releases4096
32
PRE2
Release 12.2(15)BX
and later releases256
64
Release 12.3(7)XI
and later releases4096
127
Release 12.2(27)SBB
4096
64
PRE3
Release 12.2(31)SB2
and later releases4096
64
1 Depending on the complexity of your configuration
2 Including the class-default class
Each policy-map command counts as one policy map, which counts against the 4096 system limit. When a policy map includes percent-based policing, the router sometimes converts a single QoS policy to multiple policies and applies each one of the multiple policies to each interface to which percent-based policing is applied. In this case, each multiple policy counts against the 4096 limit. In complex configurations, however, the maximum number of policy maps can be as small as a few hundred.
policy-map Command
To create or modify a policy map, use the policy-map command in global configuration mode. Use the no form of the command to remove a policy map. This command has no default behavior or values.
policy-map policy-map-nameno policy-map policy-map-nameSyntax Description
policy-map-name
Is the name of the policy map. The name can be a maximum of 40 alphanumeric characters.
policy-map Command History
Usage Guidelines for the policy-map Command
You can configure class policies in a policy map only if the classes have match criteria defined for them in a class map using the class-map and match commands. Because you can configure a maximum of 64 class maps, no policy map can contain more than 64 class policies.
You can attach a single policy map to multiple interfaces concurrently. When you attempt to attach a policy map to an interface, the router denies the attempt if the available bandwidth on the interface cannot accommodate the total bandwidth requested by class policies that comprise the policy map. In this case, if the policy map is already attached to other interfaces, it is removed from them.
Types of QoS Actions
The following sections describe the QoS actions supported on the Cisco 10000 series router. These are the actions that you configure in a policy map for specific traffic classes.
•
•
•
•
•
Input and Output Policy Actions
The Cisco 10000 series router does not impose any restrictions on the classification definitions you include in a class map. However, it does limit the input and output policy actions that you can define in a policy map. These limitations are based on the type of interface on which you apply the service policy. As indicated in Table 3 and Table 4, the interface types are:
•
•
•
•
Table 3 lists the input policy actions that you can define in a policy map for specific interface types.
Note
Table 4 lists the output policy actions that you can define in a policy map for specific interface types.
Table 4 Output Policy Map Actions
Actionsbandwidth
Valid
Valid
Valid
(Applied to the VC, not the VAI)
Not Applicable
queue-limit
Valid
Valid
Not Available
Not Available
priority
Valid
Valid
Valid
(Applied to the VC, not the VAI)
Not Applicable
shape
Valid
Valid
Valid
(Applied to the VC, not the VAI)
Not Applicable
random-detect
Valid
Valid
Not Available
Not Available
set ip prec/dscp
Valid
Not Applicable
Valid
Valid
set qos-group
Not Applicable
Not Applicable
Not Applicable
Not Applicable
set atm-clp
Valid
Not Available
Not Available
Not Available
set cos
Valid1
Not Available
Valid2
Not Applicable
police
Valid
Valid
Valid
Valid
set mpls experimental
Not Applicable
Not Available
Not Applicable
Not Applicable
1 The interface must be an Ethernet interface that is configured for 802.1Q VLAN.
2 The virtual access interface must be using an 802.1Q VLAN interface.
Policy Map Actions—Releases Prior to Cisco IOS Release 12.0(17)SL
Table 5 lists the QoS action commands supported in all releases prior to Cisco IOS Release 12.0(17)SL. These actions are also available in later releases.
Table 5 Policy Map Actions—Releases Prior to Cisco IOS Release 12.0(17)SL
police bps [burst-normal | burst-excess] [conform-action action | exceed-action action]
Configures traffic policing in policy-map class configuration mode.
bps is the average rate in bits per second. Valid values are from 8,000 to 200,000,000.
(Optional) burst-normal is the normal burst size in bytes. Valid values are from 1,000 to 51,200,000.
(Optional) burst-excess is the excess burst size in bytes. Valid values are from 1,000 to 51,200,000.
conform-action action specifies the action to take on packets that conform to the rate limit. The default action is transmit.
exceed-action action specifies the action to take on packets that exceed the rate limit. The default action is drop.
Note
See Table 10 for a list of available policing actions.
queue-limit number-of-packets
Specifies or modifies the maximum number of packets that the queue can hold for this class.
For PRE1, number-of-packets is a number from 32 to 16,384; the number must be a power of 2. If the number you specify is not a power of 2, the router uses the nearest power of 2 to your number.
For Cisco IOS Release 12.2(15)BX and Release 12.2(16)BX, number-of-packets is a number from 32 to 16,384. The number does not need to be a power of 2.
For Cisco IOS Release 12.3(7)XI and later releases, if the interface speed is less than 500 MB, number-of-packets is a number from 8 to 4096; the number must be a power of 2. If the interface speed is greater than 500 MB, number-of-packets is a number from 128 to 64,000; the number must be a power of 2.
random-detect dscp dscpvalue min-threshold max-threshold drop-rate
Changes the minimum and maximum packet thresholds for the differentiated services code point (DSCP) value.
dscpvalue specifies the DSCP value, which is a number from 0 to 63, or one of the following keywords: EF, AFxy, or CS1 through CS7. For more information, see the "DSCP Per-Hop Behavior" section on page 7-6.
min-threshold is the minimum threshold. Valid values are from 32 to 16,384 (PRE1) or 1 to 16,384 (PRE2).
max-threshold is the maximum threshold. Valid values are from 32 to 16,384 (PRE1) or 1 to 16,384 (PRE2).
drop-rate is the drop probability and is a number from 1 to 65,535. For example, if you set this value to 256, 1 out of 256 packets is dropped when the average queue is at the maximum threshold.
Note
random-detect exponential-weight-constant value
Allows you to modify the default method that random-detect uses to calculate average queue size.
Random-detect determines the average queue size based on the current queue length and the last average queue length.
value is a number from 1 to 16. The default value is typically 9.
•
•
Note
random-detect precedence precedence min-threshold max-threshold drop-rate
Changes the minimum and maximum packet thresholds for the precedence level you specify.
precedence is a number from 0 to 7, where 0 typically represents low priority traffic that can be aggressively managed (dropped) and 7 represents high priority traffic. For more information, see the set ip precedence command in this table.
min-threshold is the minimum threshold. Valid values are from 32 to 16,384 (PRE1) or 1 to 16,384 (PRE2).
max-threshold is the maximum threshold. Valid values are from 32 to 16,384 (PRE1) or 1 to 16,384 (PRE2).
drop-rate is the drop probability and is a number from 1 to 65,535. For example, if you set this value to 256, 1 out of 256 packets is dropped when the average queue is at the maximum threshold.
Note
set atm-clp
Sets the cell loss priority (CLP) bit setting.
Configure this command as an output action only.
set ip dscp dscp-value
Marks a packet by setting the IP differentiated services code point (DSCP) in the type of service (TOS) byte.
dscp-value is a number from 0 to 63.
set ip precedence {number | name}
Sets the precedence value in the IP header.
number and the corresponding name are listed below from least important to most important (for example, 0—routine is the least important and 7—network is the most important).
0—routine, 1—priority, 2—immediate, 3—flash, 4—flash-override, 5—critical 6—internet, 7—network
set qos-group group-id
Sets a group ID that can be used later to classify packets. Configure this command as an input action only.
group-id is a number from 0 to 99.
Policy Map Actions—Cisco IOS Release 12.0(17)SL and Later Releases
Cisco IOS Release 12.0(17)SL adds support for the QoS action commands listed in Table 6. These commands are also available in later releases.
Table 6 Policy Map Actions—Cisco IOS Release 12.0(17)SL and Later Releases
bandwidth {bandwidth-kbps | percent percent}
Specifies or modifies the bandwidth allocated for a traffic class in a policy map.
bandwidth-kbps is the guaranteed minimum bandwidth (in kilobits per second) that you want to allocate. Valid values are from 8 to 2,488,320.
percent percent is the percentage of the available bandwidth that you want to allocate. Valid values are from 1 to 99.
priority {bandwidth-kbps | percent percent}1
Assigns a priority to a traffic class in a policy map. The priority class receives preference over other class queues.
bandwidth-kbps is the guaranteed minimum bandwidth (in kilobits per second) that you want to allocate for the priority queue. Valid values are from 8 to 2,000,000.
percent percent is the percentage of the available bandwidth that you want to allocate for the priority queue. Valid values are 1 to 99.
shape rate
Shapes traffic to the specified bit rate.
rate is a number from 8 to 2,488,320.
1 In Cisco IOS Release 12.0(23)SX1, Release 12.0(25)S, and Release 12.3(7)XI, and later releases, the syntax of the priority command changed to priority (without any arguments). For these later releases, use the priority command with the police command so that the priority class does not starve other traffic on a link. For more information, see the "Avoiding Bandwidth Starvation Due to Priority Services" section on page 6-21 and the "Bandwidth Starvation" section on page 8-3.
Policy Map Actions—Cisco IOS Release 12.0(20)ST and Later Releases
Cisco IOS Release 12.0(20)ST adds support for the QoS action command listed in Table 7. This command is also available in later releases.
Policy Map Actions—Cisco IOS Release 12.0(22)S and Later Releases
Cisco IOS Release 12.0(22)S adds support for the QoS action command listed in Table 8. This command is also available in later releases.
Policy Map Actions—Cisco IOS Release 12.2(31)SB2 and Later Releases
Cisco IOS Release 12.2(31)SB2 adds support for the QoS action command listed in Table 9. This command is also available in later 12.2 SB releases for the PRE3.
Policing Actions
The police command allows you to specify what you want the router to do when traffic meets, exceeds, or violates the policing parameters you specified. Table 10 describes the policing actions the router supports and the minimum Cisco IOS release required.
QoS Inheritance
The Cisco 10000 series router applies service policies using the following QoS inheritance rules:
•
For more information about the ATM service classes, see the "ATM Service Categories" section.
•
•
•
•
ATM Service Categories
The Cisco 10000 series router supports the following ATM service classes:
When operating in no atm pxf queuing mode, the router supports unshaped UBR PVCs, which do not specify a peak cell rate (PCR). The router can support a high number of VCs when you configure the no atm pxf queuing command on each port of the router. Point-to-Point Protocol over ATM (PPPoA) supports one session per VC and requires that you enable no atm pxf queuing to support 32,000 PPPoA sessions. Layer 2 Tunnel Protocol (L2TP) does not require that you enable no atm pxf queuing and Point-to-Point Protocol over Ethernet (PPPoE) sessions do not require that you enable this queuing mode because you can have 32,000 sessions on a single VC.
When operating in atm pxf queuing mode, the router supports the following ATM service classes:
•
•
•
•
If you specify a PCR value for UBR+, the router accepts the value, but does not use it, and it does not notify you when this occurs.
For information about how the ATM service classes inherit QoS service policies, see the "QoS Inheritance" section.
Constant Bit Rate
The constant bit rate (CBR) service class is a fixed bandwidth class, designed for ATM virtual circuits (VCs) requiring a specific amount of bandwidth to be continuously available throughout the duration of an active connection. CBR traffic is more time-dependent, less tolerant of delay, and generally more deterministic in bandwidth requirements. Voice, circuit emulation, and high-resolution video are typical examples of traffic utilizing this type of connection.
You define the required bandwidth in kbps by specifying a PCR. For example, the cbr 64 command creates a CBR PVC with a PCR of 64 kbps.
An ATM VC configured as CBR can transmit cells at peak cell rate (PCR) at any time and for any duration. It can also transmit cells at a rate less than the PCR or even emit no cells. CBR is characterized by PCR.
Unspecified Bit Rate
The unspecified bit rate (UBR) service class is intended for non-real-time applications that do not require any maximum boundary on the transfer delay or on the cell loss ratio. The router delivers UBR traffic only when there is spare bandwidth in the network. This behavior is enforced by setting the cell loss priority (CLP) bit on UBR traffic when it enters a port.
The router delivers UBR traffic out to the network only when no other traffic is waiting to be served first. The UBR traffic does not affect the trunk loading calculations performed by the switch software.
UBR is the default class of service running at the maximum line rate of the physical interface.
The router supports both unshaped (no PCR specified) and shaped UBRs.
Shaped UBR
Traffic shaping allows you to control the traffic going out an interface in order to match its flow to the speed of the remote target interface and to ensure that the traffic conforms to policies contracted for it. Traffic that adheres to a particular profile can be shaped to meet downstream requirements, thereby eliminating bottlenecks in topologies with data-rate mismatches.
The Cisco 10000 series router supports traffic shaping for unspecified bit rate (UBR) traffic. Traffic shaping is performed on a per-port basis and involves passing UBR traffic streams through VC queues for scheduled rate shaping. When traffic shaping is enabled, all traffic exiting the port out to the network is subject to VC scheduling based on the parameters you configure for the connection.
Configuring UBRs
To configure a UBR, enter the following commands in ATM VC configuration mode:
Variable Bit Rate
Variable bit rate (VBR) connections are classified as one of the following:
•
•
Configuring VBRs
To configure VBR-nrt, enter the following commands in ATM VC configuration mode:
Traffic Subject to QoS Policies
Table 11 lists the types of traffic on the Cisco 10000 series router that are subject to QoS policies.
Table 11 QoS Applicability
In-transit IP packets
Yes
Layer 2 signaling packets such as PPP or Frame Relay negotiation packets, status packets, and keepalive messages
No
Packets with IP precedence 6 or 7, which IP-based routing protocols typically use
No
All other locally destined traffic
Yes
Packets marked by Cisco IOS software as PAK_Priority
No
Packets marked as IP precedence 6 or 7
No1
All other locally originated traffic
Yes
1 IP precedence 6 and 7 are not subject to QoS in all releases prior to Cisco IOS Release 12.0(22)S and in Cisco IOS Release 12.3(7)XI2.
ATM Virtual Circuits Without QoS Policies
For all ATM virtual circuits (VCs) that do not have a class-default class configured with a shape service policy (the shape command is configured), the Cisco 10000 series router limits the transmission rate of the VC to the interface bandwidth minus the sum of the shape rates of other VCs on the interface that do have service policies.
For example, if you have two VCs on a 150-Mbps interface and VC1 has a shaped service policy of 90 Mbps and VC2 does not have a service policy, the router polices VC2 to 60 Mbps (150 minus 90).
You can change this default behavior by using a shaped service policy on either the VC or the interface:
•
By default, the router first allocates bandwidth to the VBR VCs and then allocates any bandwidth leftover to unshaped UBR VCs. To override this default behavior, apply a service policy to the unshaped UBR VC using an hierarchical shaping policy. For more information, see Chapter 12, "Defining QoS for Multiple Policy Levels."
•
QoS Performance
The parallel express forwarding (PXF) engine processes QoS traffic. Sometimes the PXF engine cannot finish processing a packet before the packet completes a single pass through the PXF; the packet requires additional processing. As a result, the packet is fed back through the PXF and processing continues. This is referred to as a feedback operation.
Packets that are subject to both inbound and outbound QoS policies require additional PXF processing, resulting in a feedback. However, packets subject to only one QoS policy (either inbound or outbound) require only one pass through the PXF; a feedback is not needed.
Extra PXF passes reduce the system forwarding capacity. For example, if x packets per second require y extra passes, the system forwarding capacity diminishes by xy—the system has xy fewer packets per second forwarding capacity than before. Although the forwarding capacity diminishes, system performance is not affected. Packet classification processing affects only the forwarding capacity of the system, not the speed. Packet delay due to additional PXF passes is negligible. Therefore, system performance degradation occurs only at high system utilization.
The following describes PXF requirements:
•
•
•
Configuring QoS Policies
To create a QoS policy, perform the following required tasks:
•
•
Creating a Policy Map
To create a policy map, enter the following commands beginning in global configuration mode:
Configuration Examples for Creating a Policy Map
Example 4 shows how to create two policy maps named bronze and gold. The bronze policy includes a class map named class1, which is configured with a bandwidth of 100 kbps. The gold policy includes two class maps named voice and vlan. The voice class is the priority class and is policed at 50 kbps. The vlan class has a bandwidth configuration of 20 percent of the link bandwidth.
Example 4 Assigning a Class to a Policy Map
Router(config)# policy-map bronzeRouter(config-pmap)# class class1Router(config-pmap-c)# bandwidth 100Router(config-pmap-c)# exitRouter(config-pmap-c)# exitRouter(config)# policy-map goldRouter(config-pmap)# class voiceRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police 50Router(config-pmap)# class vlanRouter(config-pmap-c)# bandwidth percent 20Example 5 shows how to configure the class-default class in the policy map named mypolicy. In this example, class-default has a bandwidth configuration of 128 kbps:
Example 5 Assigning the Default Class to a Policy Map
Router(config)# policy-map mypolicyRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth 128
Note
Defining QoS Actions in a Policy Map
To define QoS actions in a policy map, see the appropriate chapter in this guide.
Attaching Service Policies
Before the router can apply QoS service policies to packets, it needs to know which service policy to apply. By attaching a service policy to the appropriate interface or virtual circuit, the router can then apply the classification rules and QoS actions of the policy to the packets arriving at or leaving the router.
You can apply QoS service policies to:
•
•
•
•
•
•
•
•
•
•
For more information, see Chapter 4, "Attaching Service Policies."
Verifying QoS Policy Configurations
To verify a policy map configuration, enter any of the following commands in privileged EXEC mode:
Verification Example for Service Policies
Example 6 shows the information displayed when you enter the show policy-map interface command. In the example output, random early detection (RED) drop statistics display for each IP precedence.
Example 6 show policy-map interface Command
Router# show policy-map interface atm 7/0/0.1ATM7/0/0.1Service-policy output: wred_1 (21036)Class-map: prec_0_0 (match-all) (21037/2)1445 packets, 1502800 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: access-group 100 (21038)Output queue: 0/64; 1445/1502800 packets/bytes output, 0 dropsBandwidth: 75 kbps (Weight 50)Random-detect (precedence-based):Exponential weight: 3 (1/8)Current average queue length: 0 packets----------------------------------------Min Max Prob Rand-Drops Tail-Drops0 16 32 1/1 0 01 18 32 1/10 0 02 20 32 1/10 0 03 22 32 1/10 0 04 24 32 1/10 0 05 26 32 1/10 0 06 28 32 1/10 0 07 30 32 1/10 0 0Class-map: prec_0_1 (match-all) (21041/3)1417 packets, 1473680 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: access-group 101 (21042)Output queue: 0/64; 1417/1473680 packets/bytes output, 0 dropsBandwidth: 73 kbps (Weight 49)Random-detect (precedence-based):Exponential weight: 3 (1/8)Current average queue length: 0 packets----------------------------------------Min Max Prob Rand-Drops Tail-Drops0 16 32 1/1 0 01 18 32 1/10 0 02 20 32 1/10 0 03 22 32 1/10 0 04 24 32 1/10 0 05 26 32 1/10 0 06 28 32 1/10 0 07 30 32 1/10 0 0Class-map: class-default (match-any) (21045/0)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: any (21046)0 packets, 0 bytes5 minute rate 0 bpsOutput queue: 0/32; 0/0 packets/bytes output, 0 dropsRelated Documentation
This section provides hyperlinks to additional Cisco documentation for the features discussed in this chapter. To display the documentation, click the document title or a section of the document highlighted in blue. When appropriate, paths to applicable sections are listed below the documentation title.
Class maps
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2
Part 8: Modular Quality of Service Command-Line Interface > Configuring the Modular Quality of Service Command-Line Interface > Modular QoS CLI Configuration Task List > Creating a Traffic Class
Cisco IOS Quality of Service Solutions Command Reference, Release 12.2
access-list rate-limit -- fair-queue (WFQ) > class-map command
Constant Bit Rate (CBR) ATM service class
ATM Traffic Management, Understanding the CBR Service Category for ATM VCs
ATM Traffic Management, Understanding Router Support for ATM Real-Time Service Categories
Policy maps
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2
Part 8: Modular Quality of Service Command-Line Interface > Configuring the Modular Quality of Service Command-Line Interface > Modular QoS CLI Configuration Task List > Creating a Traffic Policy
Cisco IOS Quality of Service Solutions Command Reference, Release 12.2
policy map - qos preclassify > policy-map command
Policy map scaling
Release Notes for the Cisco 10000 Series Internet Router for Cisco IOS Release 12.0(25)SX
New Features in Cisco IOS Release 12.0(25)SX > Policy Map Scaling
QoS service policies
QoS Configuration and Monitoring, Creating Time-of-Day QoS Service Policies tech note
QoS Configuration and Monitoring, Monitoring Voice over IP Quality of Service tech note
Site-to-Site MPLS VPN Solution for Service Providers, Service Provider Quality-of-Service Overview tech note
Unspecified bit rate (UBR) ATM service class
ATM Traffic Management, Understanding the UBR Service Category for ATM Virtual Circuits
ATM Traffic Management, Understanding Router Support for ATM Real-Time Service Categories
Cisco 10000 Series Router Line Card Configuration Guide
ATM Line Cards > 1-Port OC-12 ATM Line Card Configuration > Commands > Interface and Subinterface Commands > Creating a PVC
ATM Line Cards > 4-Port OC-3/STM-1 ATM Line Card Configuration > ATM Commands > Interface and Subinterface Commands > Creating a PVC
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.00
Configuring ATM Connections > ATM Connection Flow > Traffic Shaping for CBR, rt-VBR, nrt-VBR, and UBR
Configuring ATM Connections > ATM Connection Configuration > Unspecified Bit Rate Connections
Variable bit rate (VBR) ATM service class
ATM Traffic Management, Understanding the VBR-nrt Service Category and Traffic Shaping for ATM VCs
ATM Traffic Management, Understanding Router Support for ATM Real-Time Service Categories
Understanding the VBR-nrt Service Category and Traffic Shaping for ATM VCs tech note
Cisco 10000 Series Router Line Card Configuration Guide
ATM Line Cards > 4-Port OC-3/STM-1 ATM Line Card Configuration > ATM Commands > ATM PVC Commands > Configuring VBR-nrt
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.00
Configuring ATM Connections > ATM Connection Flow > Traffic Shaping for CBR, rt-VBR, nrt-VBR, and UBR
Configuring ATM Connections > ATM Connection Configuration > Variable Bit Rate Connections
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.
© 2007 Cisco Systems, Inc. All rights reserved.
Feedback