Table Of Contents
Distribution of Remaining Bandwidth Using Ratio
Prerequisites for Distribution of Remaining Bandwidth Using Ratio
Restrictions for Distribution of Remaining Bandwidth Using Ratio
Information About Distribution of Remaining Bandwidth Using Ratio
How to Configure Distribution of Remaining Bandwidth Using Ratio Feature
Configuring and Applying Bandwidth-Remaining Ratios to Subinterfaces
Configuring and Applying Bandwidth-Remaining Ratios to Class Queues
Configuration Examples for Distribution of Remaining Bandwidth Using Ratio
Configuring Bandwidth-Remaining Ratios on Ethernet Subinterfaces: Example
Configuring Bandwidth-Remaining Ratios on ATM Subinterfaces: Example
Configuring Bandwidth-Remaining Ratios on Class Queues: Example
Verifying Bandwidth Remaining Ratios: Example
Distribution of Remaining Bandwidth Using Ratio
First Published: November, 2006The Distribution of Remaining Bandwidth Using Ratio feature allows service providers to configure a bandwidth-remaining ratio on subinterfaces and class queues. This ratio specifies the relative weight of this subinterface or queue with respect to other subinterfaces or queues. During congestion, the router uses this bandwidth-remaining ratio to determine the amount of excess bandwidth (unused by priority traffic) to allocate to a class of non-priority traffic. The router allocates excess bandwidth relative to the other subinterface-level queues and class queues configured on the physical interface. By administering a bandwidth-remaining ratio, traffic priority is not based solely upon speed. Instead, the service provider can base priority on alternative factors such as service product, subscription rate, and so on.
History for the Distribution of Remaining Bandwidth Using Ratio Feature
Release
Modification
12.2(31)SB2
This feature was introduced and implemented on the Cisco 10000 series router for the PRE3.
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
•Prerequisites for Distribution of Remaining Bandwidth Using Ratio
•Restrictions for Distribution of Remaining Bandwidth Using Ratio
•Information About Distribution of Remaining Bandwidth Using Ratio
•How to Configure Distribution of Remaining Bandwidth Using Ratio Feature
•Configuration Examples for Distribution of Remaining Bandwidth Using Ratio
Prerequisites for Distribution of Remaining Bandwidth Using Ratio
You must configure traffic classes using the class-map command.
Restrictions for Distribution of Remaining Bandwidth Using Ratio
•Bandwidth-remaining ratios are only available on outbound interfaces.
•The bandwidth remaining ratio command cannot coexist with another bandwidth command in different traffic classes of the same policy map. For example, the following configuration is not valid and causes an error message to display:
policy-map Prec1class precedence_0bandwidth remaining ratio 10class precedence_2bandwidth 1000•The bandwidth remaining ratio command cannot coexist with another bandwidth command in the same class. For example, the following configuration is not valid and causes an error message to display:
policy-map Prec1class precedence_0bandwidth 1000bandwidth remaining ratio 10•In a hierarchical policy map in which the parent policy has only the class-default class defined with a child queuing policy applied, the router accepts only the bandwidth remaining ratio form of the bandwidth command in the class-default class of the parent policy.
•The bandwidth remaining ratio command cannot coexist with the priority command in the same class. For example, the following configuration is not valid and causes an error message to display:
policy-map Prec1class precedence_1priority percent 10bandwidth remaining ratio 10Information About Distribution of Remaining Bandwidth Using Ratio
The Distribution of Remaining Bandwidth Using Ratio feature allows service providers to prioritize subscriber traffic during periods of congestion. A bandwidth-remaining ratio is used to influence how the router allocates excess bandwidth (unused by priority traffic) to a class of non-priority traffic. Instead of using only bandwidth rate, the router considers configured minimum bandwidth rates, maximum bandwidth rates, and bandwidth-remaining ratios when determining excess bandwidth allocation. A bandwidth-remaining ratio adds more flexibility in prioritizing traffic and enables you to influence excess bandwidth allocation by basing the bandwidth-remaining ratio on factors other than speed.
When bandwidth-remaining ratios are not specified, the Hierarchical Queuing Framework (HQF) scheduler on the PRE3 does the following:
•Computes a default bandwidth-remaining ratio based on the subinterface speed—ATM interfaces
•Uses the minimum bandwidth-remaining ratio allowed (currently 1 on the PRE3)—Other interfaces such as VLANs and Frame Relay DLCIs
With bandwidth-remaining ratios, service providers have more flexibility in assigning priority to subinterfaces and queues during congestion. In addition to speed, you can base the bandwidth-remaining ratio on alternative factors, such as a service product or subscription rate. In this way, for example, you can give higher weight to subinterfaces carrying business services and lower weight to subinterfaces carrying residential services. The bandwidth-remaining ratio enables the HQF scheduler to service a subinterface with a low SCR but a high bandwidth-remaining ratio more frequently than servicing a subinterface with a high SCR but a low bandwidth-remaining ratio.
The Distribution of Remaining Bandwidth Using Ratio feature is available on outbound interfaces only.
Bandwidth-Remaining Ratio
A bandwidth-remaining ratio is a value from 1 to 1000 that is used to determine the amount of unused (excess) bandwidth to allocate to a class queue or subinterface-level queue during congestion. The router allocates excess bandwidth relative to the other class queues and subinterface-level queues configured on the physical interface. The bandwidth-remaining ratio value does not indicate a percentage. For example, a subinterface with a bandwidth-remaining ratio of 100 receives 10 times the unused (excess) bandwidth during congestion than a subinterface with a bandwidth-remaining ratio of 10.
Without bandwidth-remaining ratios, the router allocates excess bandwidth based on the following:
•Speed of the subinterface (for example, the configured SCR)—ATM subinterfaces
•Minimum bandwidth-remaining ratio allowed (currently 1 on the PRE3)—Interface types such as VLANs and Frame Relay DLCIs
With bandwidth-remaining ratios, excess bandwidth allocation can be based on factors other than the bandwidth rate (for example, service product or subscription rate).
How to Configure Distribution of Remaining Bandwidth Using Ratio Feature
You can apply bandwidth-remaining ratios to different subinterfaces and to different traffic queues within a single outbound interface or subinterface.
Use the following procedures to configure the Distribution of Remaining Bandwidth Using Ratio feature:
•Configuring and Applying Bandwidth-Remaining Ratios to Subinterfaces
•Configuring and Applying Bandwidth-Remaining Ratios to Class Queues
Configuring and Applying Bandwidth-Remaining Ratios to Subinterfaces
Use the following procedure to configure and apply bandwidth-remaining ratios to subinterfaces.
Note You can apply bandwidth-remaining ratios to outbound subinterfaces only.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map child-policy-name
4. class class-map-name
5. bandwidth bandwidth-kbps
6. exit
7. exit
8. policy-map parent-policy-name
9. class class-default
10. bandwidth remaining ratio ratio
11. shape {average | peak} cir [bc] [be]
12. service-policy child-policy-name
13. exit
14. exit
15. interface type slot/module/port.subinterface {point-to-point | multipoint}
16. service-policy {input | output} parent-policy-name
DETAILED STEPS
Configuring and Applying Bandwidth-Remaining Ratios to Class Queues
Use the following procedure to configure and apply bandwidth-remaining ratios to class queues.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map child-policy-name
4. class class-map-name
5. shape {average | peak} cir [bc] [be]
6. bandwidth remaining ratio ratio
7. exit
8. exit
9. policy-map parent-policy-name
10. class class-default
11. shape {average | peak} cir [bc] [be]
12. bandwidth remaining ratio ratio
13. service-policy child-policy-name
14. exit
15. exit
16. interface type slot/module/port.subinterface {point-to-point | multipoint}
17. service-policy {input | output} parent-policy-name
DETAILED STEPS
Configuration Examples for Distribution of Remaining Bandwidth Using Ratio
This section provides the following configuration examples:
•Configuring Bandwidth-Remaining Ratios on Ethernet Subinterfaces: Example
•Configuring Bandwidth-Remaining Ratios on ATM Subinterfaces: Example
•Configuring Bandwidth-Remaining Ratios on Class Queues: Example
•Verifying Bandwidth Remaining Ratios: Example
Configuring Bandwidth-Remaining Ratios on Ethernet Subinterfaces: Example
The following example shows how to configure bandwidth-remaining ratios on an Ethernet subinterface using a hierarchical policy. In the example, Gigabit Ethernet subinterface 1/0/0.1 is shaped to 100 Mbps. During congestion, the router uses the bandwidth-remaining ratio of 10 to determine the amount of excess bandwidth (unused by priority traffic) to allocate to the non-priority traffic on subinterface 1/0/0.1, relative to the other subinterface-level and class-level queues on the interface.
policy-map Childclass precedence_0bandwidth 10000class precedence_1shape average 100000bandwidth 100!policy-map Parentclass class-defaultbandwidth remaining ratio 10shape average 100000000service-policy Child!interface GigabitEthernet1/0/0.1encapsulation dot1Q 100ip address 10.1.0.1 255.255.255.0service-policy output ParentConfiguring Bandwidth-Remaining Ratios on ATM Subinterfaces: Example
The following example shows how to differentiate one ATM PVC from another during congestion by using bandwidth-remaining ratios. In the example, during periods of congestion in which the traffic on all PVCs on the interface exceeds the interface speed, the router uses the configured bandwidth-remaining ratio of 10 to determine the amount of excess (unused by priority traffic) bandwidth to allocate to non-priority traffic on PVC 0/200, relative to the other ATM PVCs configured on the interface.
policy-map Childclass precedence_0bandwidth 100class precedence_1bandwidth 10000!policy-map Parentclass class-defaultbandwidth remaining ratio 10service-policy Child!interface ATM2/0/3.200 point-to-pointip address 10.20.1.1 255.255.255.0pvc 0/200protocol ip 10.20.1.2vbr-nrt 50000encapsulation aal5snapservice-policy output Parent
Note If PVC 98/204 is configured on the same interface as PVC 0/200 and with a bandwidth-remaining ratio of 1, during times of congestion PVC 0/200 would have 10 times more bandwidth available to it for non-priority traffic than PVC 98/204 would have.
Configuring Bandwidth-Remaining Ratios on Class Queues: Example
In the following sample configuration, the vlan10_policy is applied on the subinterface Gigabit Ethernet 1/0/0.10 and the vlan20_policy is applied on the subinterface Gigabit Ethernet 1/0/0.20. During congestion on the interface, subinterface GE 1/0/0.20 has 10 times more available bandwidth than subinterface GE1/0/0.10 because the bandwidth-remaining ratio for subinterface GE 1/0/0.20 is 10 times more than the bandwidth-remaining ratio for subinterface 1/0/0.10: 100 on subinterface 1/0/0.20 and 10 on subinterface 1/0/0.10.
When congestion occurs within a subinterface level, the class queues receive bandwidth according to the class-level bandwidth-remaining ratios. In the example, the bandwidth for classes precedence_0, precedence_1, and precedence_2 is allocated based on the bandwidth-remaining ratios of the classes: 20, 40, and 60, respectively.
policy-map child-policyclass precedence_0shape average 500000bandwidth remaining ratio 20 <---- Class-level ratioclass precedence_1shape average 500000bandwidth remaining ratio 40 <---- Class-level ratioclass precedence_2shape average 500000bandwidth remaining ratio 60 <---- Class-level ratio!policy-map vlan10_policyclass class-defaultshape average 1000000bandwidth remaining ratio 10 <---- Subinterface-level ratioservice-policy child-policy!policy-map vlan20_policyclass class-defaultshape average 1000000bandwidth remaining ratio 100 <---- Subinterface-level ratioservice-policy child_policy!!interface GigabitEthernet 1/0/0.10encapsulation dot1q 10service-policy output vlan10_policy!interface GigabitEthernet 1/0/0.20encapsulation dot1q 20service-policy output vlan20_policyVerifying Bandwidth Remaining Ratios: Example
The following sample output from the show policy-map interface command indicates that bandwidth-remaining ratios are configured on class-level queues in the policy maps named vlan10_policy and child_policy, which are attached to the Gigabit Ethernet subinterface 1/0/0.10.
Router# show policy-map interface GigabitEthernet1/0/0.10Service-policy output: vlan10_policyClass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsQueueingqueue limit 250 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 1000000, bc 4000, be 4000target shape rate 1000000bandwidth remaining ratio 10Service-policy : child_policyClass-map: precedence_0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 20Class-map: precedence_1 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 40Class-map: precedence_2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 60Class-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0The following sample output from the show policy-map interface command indicates that bandwidth-remaining ratios are configured on class-level queues in the policy maps named vlan20_policy and child_policy, which are attached to the Gigabit Ethernet subinterface 1/0/0.20.
Router# show policy-map interface GigabitEthernet1/0/0.20Service-policy output: vlan20_policyClass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsQueueingqueue limit 250 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 1000000, bc 4000, be 4000target shape rate 1000000bandwidth remaining ratio 100Service-policy : child_policyClass-map: precedence_0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 20Class-map: precedence_1 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 40Class-map: precedence_2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 60Class-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0The following sample output from the show policy-map command indicates that a bandwidth-remaining ratio of 10 is configured on the parent class-default class of the policy map named vlan10_policy.
Router# show policy-map vlan10_policyPolicy Map vlan10_policyClass class-defaultAverage Rate Traffic Shapingcir 1000000 (bps)bandwidth remaining ratio 10service-policy child_policyThe following sample output from the show policy-map command indicates that a bandwidth-remaining ratio of 100 is configured on the parent class-default class of the policy map named vlan20_policy. During congestion, the scheduler allocates the subinterface Gigabit Ethernet 1/0/0.20 10 times the bandwidth that it allocates subinterface Gigabit Ethernet 1/0/0.10.
Router# show policy-map vlan20_policyPolicy Map vlan20_policyClass class-defaultAverage Rate Traffic Shapingcir 1000000 (bps)bandwidth remaining ratio 100service-policy child_policyThe following sample output from the show policy-map command indicates that a bandwidth-remaining ratio of 20, 40, and 60 is configured on the class queues precedence_0, precedence_1, and precedence_2, respectively.
Router# show policy-map child_policyPolicy Map child_policyClass precedence_0Average Rate Traffic Shapingcir 500000 (bps)bandwidth remaining ratio 20Class precedence_1Average Rate Traffic Shapingcir 500000 (bps)bandwidth remaining ratio 40Class precedence_2Average Rate Traffic Shapingcir 500000 (bps)bandwidth remaining ratio 60Additional References
The following sections provide references related to Distribution of Remaining Bandwidth Using Ratio.
Related Documents
Related Topic Document TitleBandwidth
Cisco 10000 Series Router Quality of Service Configuration Guide
Hierarchical policies
Cisco 10000 Series Router Quality of Service Configuration Guide
Policy maps
Cisco 10000 Series Router Quality of Service Configuration Guide
Shaping traffic
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2
Part 4: Policing and Shaping > Configuring Class-Based Shaping
Part 4: Policing and Shaping > Policing and Shaping Overview > Traffic Shaping > Class-Based Shaping
Traffic policing and shaping
Comparing Traffic Policing and Traffic Shaping for Bandwidth Limiting
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents new and modified commands only.
•
bandwidth remaining ratio
To specify a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to non-priority queues, use the bandwidth remaining ratio command in policy-map class configuration mode. To remove the bandwidth-remaining ratio, use the no form of this command.
bandwidth remaining ratio ratio
no bandwidth remaining ratio ratio
Syntax Description
ratio
Specifies the relative weight of this subinterface or queue with respect to other subinterfaces or queues. Valid values are from 1 to 1000. The default value is platform dependent.
Command Default
Cisco 10000 Series Router
When using default bandwidth-remaining ratios at the subinterface level, the Cisco 10000 series router distinguishes between interface types. At the subinterface level, the default bandwidth-remaining ratio is 1 for VLAN subinterfaces and Frame Relay DLCIs. For ATM subinterfaces, the router computes the default bandwidth-remaining ratio based on the subinterface speed.
When using default bandwidth-remaining ratios at the class level, the Cisco 10000 series router makes no distinction between interface types. At the class level, the default bandwidth-remaining ratio is 1.
Command Modes
Policy-map class
Command History
Release Modification12.2(31)SB
This command was introduced and implemented on the Cisco 10000 series router for the PRE3.
Usage Guidelines
Cisco 10000 Series Router
The scheduler uses the ratio specified in the bandwidth remaining ratio command to determine the amount of excess bandwidth (unused by priority traffic) to allocate to a class-level queue or a subinterface-level queue during periods of congestion. The scheduler allocates the unused bandwidth relative to other queues or subinterfaces.
The bandwidth remaining ratio command cannot coexist with another bandwidth command in different traffic classes of the same policy map. For example, the following configuration is not valid and causes an error message to display:
policy-map Prec1class precedence_0bandwidth remaining ratio 10class precedence_2bandwidth 1000For the PRE2, the bandwidth remaining ratio command can coexist with another bandwidth command in the same class of a policy map. On the PRE3, the bandwidth remaining ratio command cannot coexist with another bandwidth command in the same class. For example, the following configuration is not valid on the PRE3 and causes an error message to display:
policy-map Prec1class precedence_0bandwidth 1000bandwidth remaining ratio 10In a hierarchical policy map in which the parent policy has only the class-default class defined with a child queuing policy applied, the router accepts only the bandwidth remaining ratio form of the bandwidth command in the class-default class.
The bandwidth remaining ratio command cannot coexist with the priority command in the same class. For example, the following configuration is not valid and causes an error message to display:
policy-map Prec1class precedence_1prioritypolice percent 30bandwidth remaining ratio 10All of the queues for which the bandwidth remaining ratio command is not specified receive the platform-specified minimum bandwidth-remaining ratio. The router determines the minimum committed information rate (CIR) based on the configuration.
Examples
The following example shows how to configure a bandwidth-remaining ratio on an ATM subinterface. In the example, the router guarantees a peak cell rate of 50 Mbps for the variable bit rate-non-real time (VBR-nrt) PVC 0/200. During periods of congestion, the subinterface receives a share of excess bandwidth (unused by priority traffic) based on the bandwidth-remaining ratio of 10, relative to the other subinterfaces configured on the physical interface.
policy-map Childclass precedence_0bandwidth 10000class precedence_1shape average 100000bandwidth 100!policy-map Parentclass class-defaultbandwidth remaining ratio 10shape average 20000000service-policy Child!interface ATM2/0/3.200 point-to-pointip address 10.20.1.1 255.255.255.0pvc 0/200protocol ip 10.20.1.2vbr-nrt 50000encapsulation aal5snapservice-policy output ParentThe following example shows how to configure bandwidth remaining ratios for individual class queues. Some of the classes configured have bandwidth guarantees and a bandwidth-remaining ratio explicitly specified. When congestion occurs within a subinterface level, the class queues receive excess bandwidth (unused by priority traffic) based on their class-level bandwidth-remaining ratios: 20, 30, 120, and 100, respectively for the precedence_0, precedence_1, precedence_2, and precedence_5 classes. Normally, the precedence_3 class (without a defined ratio) would receive bandwidth based on the bandwidth-remaining ratio of the class-default class defined in the Child policy. However, in the example, the Child policy does not define a class-default bandwidth remaining ratio, therefore, the router uses a ratio of 1 to allocate excess bandwidth to precedence_3 traffic.
policy-map Childclass precedence_0shape average 100000bandwidth remaining ratio 20class precedence_1shape 10000bandwidth remaining ratio 30class precedence_2shape average 200000bandwidth remaining ratio 120class precedence_3set ip precedence 3class precedence_5set ip precedence 5bandwidth remaining ratio 100policy-map Parentclass class-defaultbandwidth remaining ratio 10service-policy Child!interface GigabitEthernet 2/0/1.10encapsulation dot1q 10service-policy output ParentRelated Commands
show policy-map
To display the configuration of all classes for a specified service policy map or all classes for all existing policy maps, use the show policy-map command in EXEC mode.
show policy-map [policy-map]
Syntax Description
policy-map
(Optional) Name of the service policy map whose complete configuration is to be displayed.
Command Default
All existing policy map configurations are displayed.
Command Modes
EXEC
Command History
Usage Guidelines
The show policy-map command displays the configuration of a service policy map created using the policy-map command. You can use the show policy-map command to display all class configurations comprising any existing service policy map, whether or not that service policy map has been attached to an interface. The command output includes bandwidth-remaining ratio configuration and statistical information, if configured and used to determine the amount of unused (excess) bandwidth to allocate to a class queue during periods of congestion.
Examples
The following is sample output from the show policy-map command. This sample output displays the contents of a policy map called "policy1." In policy 1, traffic policing on the basis of a committed information rate (CIR) of 20 percent has been configured, and the bc and be have been specified in milliseconds. As part of the traffic policing configuration, optional conform, exceed, and violate actions have been specified.
Router# show policy-map policy1Policy Map policy1Class class1police cir percent 20 bc 300 ms pir percent 40 be 400 msconform-action transmitexceed-action dropviolate-action dropTable 1 describes the significant fields shown in the display.
Bandwidth-Remaining Ratio Example
The following sample output for the show policy-map command indicates that the class-default class of the policy map named vlan10_policy has a bandwidth-remaining ratio of 10. When congestion occurs, the scheduler allocates class-default traffic 10 times the unused bandwidth allocated in relation to other subinterfaces.
Router# show policy-map vlan10_policyPolicy Map vlan10_policyClass class-defaultAverage Rate Traffic Shapingcir 1000000 (bps)bandwidth remaining ratio 10service-policy child_policyATM Overhead Accounting Example
The following sample output for the show policy-map command indicates that ATM overhead accounting is enabled for the class-default class. The BRAS-DSLAM encapsulation is dot1q and the subscriber encapsulation is snap-rbe for the AAL5 service.
Policy Map unit-testClass class-defaultAverage Rate Traffic Shapingcir 10% account dot1q aal5 snap-rbeTable 2 describes the significant fields shown in the display.
Related Commands
show policy-map interface
To display the packet statistics of all classes and all priority levels configured for all service policies either on the specified interface or subinterface or on a specific permanent virtual circuit (PVC) on the interface, use the show policy-map interface command in privileged EXEC mode.
show policy-map interface [type access-control] interface-name [vc [vpi/] vci] [dlci dlci]
[input | output]ATM Shared Port Adapter
show policy-map interface atm slot/subslot/port[.subinterface]
Syntax Description
Defaults
The absence of both the forward slash (/) and a vpi value defaults the vpi value to 0. If this value is omitted, information for all virtual circuits (VCs) on the specified ATM interface or subinterface is displayed.
ATM Shared Port Adapter
When used with the ATM shared port adapter, this command has no default behavior or values.
Command Modes
Privileged EXEC
ATM Shared Port Adapter
When used with the ATM shared port adapter, EXEC or privileged EXEC.
Command History
Usage Guidelines
The show policy-map interface command displays the packet statistics for classes and priority levels on the specified interface or the specified PVC only if a service policy has been attached to the interface or the PVC. The command output includes bandwidth-remaining ratios configured on traffic classes.
You can use the interface-name argument to display output for a PVC only for enhanced ATM port adapters (for example, the PA-A3) that support per-VC queueing.
The counters displayed after the show policy-map interface command is entered are updated only if congestion is present on the interface.
The show policy-map interface command displays policy information about Frame Relay PVCs only if Frame Relay Traffic Shaping (FRTS) is enabled on the interface.
The show policy-map interface command displays ECN marking information only if ECN is enabled on the interface.
To determine if shaping is active with the hierarchical queuing framework (HQF), check the queue depth field of the "(queue depth/total drops/no-buffer drops)" line in the show policy-map interface command output.
Examples
Example of Multiple Priority Queues on Serial Interface
The following sample output from the show policy-map interface command shows the types of statistical information that displays when multiple priority queues are configured. Depending upon the interface in use and the options enabled, the output you see may vary slightly from the output shown below.
Router# show policy-map interfaceSerial2/1/0Service-policy output: P1Queue statistics for all priority classes:...Class-map: Gold (match-all)0 packets, 0 bytes /*Updated for each priority level configured.*/5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Priority: 0 kbps, burst bytes 1500, b/w exceed drops: 0Priority Level 4:0 packets, 0 bytesExample of Bandwidth-Remaining Ratios
The following sample output from the show policy-map interface command indicates that bandwidth-remaining ratios are configured for class queues. As shown in the example, the classes precedence_0, precedence_1, and precedence_2 have bandwidth-remaining ratios of 20, 40, and 60, respectively.
Router# show policy-map interface GigabitEthernet1/0/0.10Service-policy output: vlan10_policyClass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsQueueingqueue limit 250 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 1000000, bc 4000, be 4000target shape rate 1000000bandwidth remaining ratio 10
Service-policy : child_policyClass-map: precedence_0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 20Class-map: precedence_1 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 40Class-map: precedence_2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 60Class-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0Related Commands
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, 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, Follow Me Browsing, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, 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. (0609R)
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.
© 2006 Cisco Systems, Inc. All rights reserved.