Downloads |
Table Of Contents
IP to ATM CoS, per-VC WFQ and CBWFQ
Related Features and Technologies
Supported Standards, MIBs and RFCs
Configuring Class-Based Weighted Fair Queueing
Attaching a Service Policy and Enabling CBWFQ for a VC
Configuring a VC to Use Flow-Based WFQ
Monitoring Per-VC WFQ and CBWFQ
Enabling Logging of Error Messages to the Console
Per-VC WFQ and CBWFQ on a Standalone VC Example
Per VC WFQ and CBWFQ on Bundle-Member VCs Example
IP to ATM CoS, per-VC WFQ and CBWFQ
This feature module describes the IP to ATM Class of Service, per-Virtual Circuit Weighted Fair Queueing and Class-Based Weighted Fair Queueing (IP to ATM CoS, per-VC WFQ and CBWFQ) feature. It contains the following sections:
Feature Overview
The IP to ATM CoS, per-VC WFQ and CBWFQ feature allows you to apply CBWFQ functionality—normally applicable at the interface or subinterface levels only—to an individual VC configured for IP to ATM CoS. You can use this extension to the IP to ATM CoS feature to apply either class-based WFQ (CBWFQ) or flow-based WFQ on a per-VC basis.
Before you look at how IP to ATM CoS, per-VC WFQ and CBWFQ functions, consider the following summaries of CBWFQ and IP to ATM CoS.
About CBWFQ
CBWFQ extends the flow-based WFQ functionality to provide support for user-defined classes. CBWFQ allows you to define traffic classes that are based on certain match criteria such as access control lists, input interfaces names, protocols, and quality of service (QoS) labels. Once a class has been defined according to its match criteria, you can assign it characteristics. To characterize a class, you assign it bandwidth, weight, and maximum packet limit. The bandwidth assigned to a class is the minimum bandwidth delivered to the class during congestion. Also, to characterize a class, you specify the queue limit for that class, which is the maximum number of packets allowed to accumulate in its queue. Packets belonging to a class are subject to the bandwidth and queue limits that characterize the class.
After you define traffic classes, you can configure one or more of them in a policy map to be attached as a service policy. CBWFQ allows you to create policy maps and attach them to interfaces or subinterfaces as service policies. The IP to ATM CoS, per-VC WFQ and CBWFQ feature allows you to create a policy map using standard CBWFQ, then apply the map to a VC to be used as a service policy for that VC. For complete information on CBWFQ, refer to the Cisco IOS Release 12.0(5)T feature module titled Class-Based Weighted Fair Queueing.
About IP to ATM CoS
Before considering how per-VC WFQ and CBWFQ functions as part of IP to ATM CoS, it is helpful to have some understanding of the IP to ATM CoS feature itself, the main function of which is to provide for consistent QoS between IP and ATM interworked networks. IP to ATM CoS implements a solution for coarse-grained mapping of QoS characteristics between IP and ATM, using Cisco's PA-A3 ATM port adapters on Cisco 7200 series routers. (This category of coarse-grained QoS is often referred to as CoS.) The resulting feature makes it possible to support differential services in network service provider environments.
IP to ATM CoS is designed to provide a true working solution to class-based services, without the investment of new ATM network infrastructures. Now networks can offer different service classes (sometimes termed differential service classes) across the entire WAN, not just the routed portion. Mission-critical applications can be given exceptional service during periods of high network usage and congestion. In addition, noncritical traffic can be restricted in its network usage, which ensures greater QoS for more important traffic and user types. IP to ATM CoS supports configuration of both a single ATM VC and VC bundles. For complete information on IP to ATM CoS, refer to the 12.0(3)T feature module, IP to ATM Class of Service.
The IP to ATM CoS, per-VC WFQ and CBWFQ feature allows you to apply a policy map to a VC to specify a service policy for that VC so that all traffic sent on that VC is categorized according to the classes and their match criteria defined by the service policy. In other words, IP to ATM CoS, per-VC WFQ and CBWFQ takes the functionality defined for standard CBWFQ and makes it available for application and use at the discrete VC level.
IP to ATM CoS allows you to configure a single, standalone VC or individual VCs belonging to a bundle. You also can configure collectively all VCs belonging to a bundle. However, for per-VC WFQ and CBWFQ, you can configure individual VCs only. That is, you can configure a standalone VC or a VC that belongs to a bundle, but you cannot use per-VC WFQ and CBWFQ to configure a bundle of VCs collectively.
Per-VC WFQ and CBWFQ allows you to differentiate the use of individual VCs within a bundle. For instance, you can apply one service policy to one VC belonging to a VC bundle and apply a different service policy to another VC belonging to the same bundle. You can also apply the same policy map to multiple VCs—whether standalone or bundle members—but each VC can have only one service policy. To concatenate service policies, you must create a third policy map and include in it all the classes that you want to use from policy maps you would have concatenated.
The following is a summary of how you configure a VC to use CBWFQ:
•
You define traffic classes to specify the classification policy (class maps).
This process determines how many types of packets are to be differentiated from one another. (The Cisco IOS Release 12.0(5)T feature module titled Class-Based Weighted Fair Queueing explains how to do this.)
Note
•
•
To apply flow-based WFQ on a per-VC basis, you configure WFQ in the predefined CBWFQ default class, which is called class-default, but you do not ascribe bandwidth to the default class. How to configure the default class to specify flow-based fair queueing is explained in "Configuring a VC to Use Flow-Based WFQ" on page 6.
Benefits
Bandwidth Allocation
CBWFQ allows you to specify the exact amount of bandwidth to be allocated for a specific class of traffic. As long as the total bandwidth for all classes included in a service policy does not exceed 75 percent of the available bandwidth for the VC, you can configure up to 64 classes and control bandwidth distribution among them.
Coarser Granularity and Scalability
CBWFQ allows you to define what constitutes a class based on criteria that exceed the confines of flow. CBWFQ allows you to use access control lists and input interface names or protocols to define how traffic will be classified, thereby providing coarser granularity. You need not maintain traffic classification on a flow basis. The ability to apply a service policy specified by various classes at the VC level gives you greater control and differentiation over how traffic sent over the VC is classified and treated, distinguishing it from how traffic sent over other VCs is classified and treated.
Related Features and Technologies
This feature is an extension to the IP to ATM CoS feature. This feature includes use of the standard CBWFQ implementation. To use per-VC WFQ and CBWFQ, you must use the commands documented in this feature module and the standard CBWFQ commands documented in the feature module titled 12.0(5)T Class-Based Weighted Fair Queueing feature module; you use these commands to create classes and define policy maps to be attached to individual VCs as service policies.
Related Documents
For related information on this feature, refer to the following documents:
•
•
•
•
CBWFQ supports standard and extended numbered access lists only. For information on creating access lists, see the appropriate Cisco IOS Release 12.0 configuration guides and command references.
Supported Platforms
The IP to ATM CoS, per-VC WFQ and CBWFQ feature is supported on any Cisco 7200 series routers equipped with the following hardware:
•
•
Supported Standards, MIBs and RFCs
None
Prerequisites
The IP to ATM CoS feature requires ATM PVC management and Cisco Express Forwarding (CEF) switching functionality. It also requires that the remote router run a version of Cisco IOS software that supports IP to ATM CoS with VC bundle management.
To use the feature described in this feature module, you should be familiar with the following QoS features:
•
•
•
•
Documentation for these features can be found on the Documentation CD-ROM and on Cisco Connection Online (CCO).
To use this feature, you should also be able to install a port adapter in a Cisco 7200 series router and to configure the router.
Access Control Lists
Because you can specify a numbered access list as the match criterion for any class that you create, you should know how to configure access lists.
Configuration Tasks
See the following sections for configuration tasks for the IP to ATM CoS, per-VC WFQ and CBWFQ feature. The first two sections are required; the remaining sections are optional.
•
•
•
•
•
Configuring Class-Based Weighted Fair Queueing
Before configuring CBWFQ for a VC, you must perform the following tasks using standard CBWFQ commands:
•
•
Note
Attaching a Service Policy and Enabling CBWFQ for a VC
Because CBWFQ gives you minimum bandwidth guarantee, you can only apply CBWFQ to VCs having these classes of service: available bit rate (ABR) and variable bit rate (VBR). You cannot apply per-VC WFQ and CBWFQ to UBR and UBR+ VCs because both of these service classes are best-effort classes that do not guarantee minimum bandwidth. When CBWFQ is enabled for a VC, all classes configured as part of the service policy are installed in the fair queueing system.
To attach a policy map to a standalone VC to be used as its service policy and to enable CBWFQ on that VC, use the following command in VC submode:
Enables CBWFQ and attaches the specified service policy map to the VC being created or modified.
To attach a policy map to an individual VC bundle member to be used as its service policy and to enable CBWFQ on that VC, use the following command in bundle-vc configuration mode:
Router(config-if-atm-member)# service-policy output policy-map
Enables CBWFQ and attaches the specified service policy map to the VC being created or modified.
Note
Configuring a VC to Use Flow-Based WFQ
In addition to configuring CBWFQ at the VC level, the IP to ATM CoS feature allows you to configure flow-based WFQ at the VC level. Because flow-based WFQ gives you best-effort class of service—that is, it does not guarantee minimum bandwidth—you can configure per-VC WFQ for all types of CoS VC: ABR, VBR, UBR, and UBR+.
Per-VC WFQ uses the class-default class. Therefore, to configure per-VC WFQ, you must first create a policy map and configure the class-default class. (You need not create the class-default class, which is predefined, but you must configure it.) For per-VC WFQ, the class-default class must be configured with the fair-queue policy-map configuration command.
In addition to configuring the fair-queue policy-map class configuration command, you can configure the default class with either the queue-limit command or the random-detect command, but not both. Moreover, if you want the default class to use flow-based WFQ, you cannot configure the default class with the bandwidth policy-map class configuration command—to do so would disqualify the default class as flow-based WFQ, and therefore limit application of the service policy containing the class to ABR and VBR VCs.
To create a policy map and configure the class-default class, use the following commands beginning in global configuration mode:
For more information about creating a policy map and configuring the class-default class, see the 12.0(5)T feature module, Class-Based Weighted Fair Queueing.
By default—that is, even if you do not configure the class-default class with the fair-queue policy-map class configuration command and you do not configure it with the bandwidth policy-map class configuration command—the default class is defined as flow-based WFQ.
Note that you can include other classes in the same policy map as the one that contains the flow-based WFQ class. Packets not otherwise matched are selected by the default class-default class match criteria.
To attach the policy map containing the class-default class to a standalone VC so that it becomes the service policy enabling WFQ for that VC, use the following command in VC submode:
To attach the policy map containing the class-default class to an individual VC bundle member so that the policy map becomes the service policy enabling WFQ for that VC, use the following command in bundle-vc configuration mode:
Monitoring Per-VC WFQ and CBWFQ
To monitor per-VC WFQ and CBWFQ in your network, use one or more of the following commands in EXEC mode:
Enabling Logging of Error Messages to the Console
When you configure a VC in order to create or modify it, the router performs the task in interrupt mode. For this reason, the router cannot issue printf statements to inform you of error conditions, if errors occur. Rather, the router logs all error messages to the console. To accommodate these circumstances, you should enable logging of error messages to the console.
To enable logging of error messages to the console, use the following command in global configuration mode:
Router(config)# logging console level
Limits messages logged to the console based on severity.
For information on the logging console command, including configuration tasks and command syntax, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference.
Configuration Examples
This section provides the following configuration examples:
•
•
Per-VC WFQ and CBWFQ on a Standalone VC Example
The following example creates two class maps and defines their match criteria. For the first map class, called class1, the numbered access control list (ACL) 101 is used as the match criterion. For the second map class, called class2, the numbered ACL 102 is used as the match criterion.
Next, the example includes these classes in a policy map called policy1. For class1, the policy includes a minimum bandwidth allocation request of 500 Mbps and maximum packet count limit of 30 for the queue reserved for the class. For class2, the policy specifies only the minimum bandwidth allocation request of 1000 Mbps, so the default queue limit of 64 packets is assumed. Note that the sum of the bandwidth requests for the two classes comprising policy1 is 75 percent of the total amount of bandwidth (2000 Mbps) for PVC cisco to which the policy map is attached.
The example attaches the policy map called policy1 to the PVC called cisco. Once the policy map policy1 is attached to PVC cisco, its classes constitute the CBWFQ service policy for that PVC. Packets sent on this PVC will be checked for matching criteria against ACLs 101 and 102 and classified accordingly.
Because class-default is not explicitly configured for this policy map, all traffic that does not meet the match criteria of the two classes comprising the service policy is handled by the predefined class-default class, which provides best-effort flow-based WFQ.
class-map class1 match access-group 101class-map class2 match access-group 102
policy-map policy1 class class1 bandwidth 500queue-limit 30class class2 bandwidth 1000interface ATM1/1/0.46 multipointip address 200.126.186.2 255.255.255.0pvc cisco 46 vbr-nrt 2000 2000 encap aal5snap service policy output policy1Per VC WFQ and CBWFQ on Bundle-Member VCs Example
The following example shows a PVC bundle called san-francisco with members for which per-VC WFQ and CBWFQ are enabled and service policies configured. The example assumes that the classes included in the following policy maps have been defined and that the policy maps have been created: policy1, policy2, and policy4. For each PVC, the IP to ATM CoS pvc-bundle command is used to specify the PVC to which the specified policy map is to be attached.
Note that PVC 0/34 and 0/31 have the same policy map attached to them, policy2. Although you can assign the same policy map to multiple VCs, each VC can have only one policy map attached at an output PVC.
bundle san-francisco protocol ip 1.0.2.20 broadcastencapsulation aal5snappvc-bundle 0/35 service policy output policy1 vrt-nrt 5000 3000 500 precedence 4-7 pvc-bundle 0/34 service policy output policy2 vrt-nrt 5000 3000 500 precedence 2-3 pvc-bundle 0/33 vrt-nrt 4000 3000 500 precedence 2-3 service policy output policy4 pvc-bundle 0/31 service policy output policy2Command Reference
This section documents commands modified to support this feature. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications and the Cisco IOS Release 12.0(5)T feature modules.
•
pvc
Use the pvc interface configuration command to perform one or more of the following tasks:
•
•
•
•
To remove an ATM PVC, use the no form of this command.
pvc [name] vpi/vci [ilmi | qsaal | smds]
no pvc [name] vpi/vci [ilmi | qsaal | smds]Syntax Description
Defaults
No PVC is defined. When a PVC is defined, the global default of the encapsulation command applies (aal-encap = aal5snap).
Command Modes
Interface or subinterface configuration
Command History
Usage Guidelines
The pvc command replaces the atm pvc command, which, although still supported and available, will be obsoleted in the near future. Use the pvc command to configure a single ATM VC only, not a VC that is a bundle member. We recommend that you use the pvc command in conjunction with the encapsulation and random-detect attach commands instead of the atm pvc command.
The Cisco IOS software dynamically creates rate queues as necessary to satisfy the requests of the pvc commands.
The pvc command creates a PVC and attaches it to the VPI and VCI specified. Both vpi and vci cannot be simultaneously specified as 0; if one is 0, the other cannot be 0.
When configuring an SVC, use the pvc command to configure the PVC that handles SVC call setup and termination. In this case, specify the qsaal keyword. See the second example that follows.
Once you specify a name for a PVC, you can reenter the interface-ATM-VC configuration mode by simply entering pvc name. You can remove a PVC and any associated parameters by entering no pvc name or no pvc vpi/vci.
Note
If ilmi, qsaal, or smds encapsulation is not explicitly configured on the ATM PVC, the PVC inherits the following default configuration (listed in order of next highest precedence):
•
•
•
•
Examples
The following example creates a PVC with VPI 0 and VCI 16, and communication is set up with the ILMI:
pvc cisco 0/16 ilmiexitThe following example creates a PVC used for ATM signalling for an SVC. It specifies VPI 0 and VCI 5:
pvc cisco 0/5 qsaalexit
The following example configures the PVC called cisco to use CBWFQ. It attaches a policy map called policy1 to the PVC. The classes comprising policy1 determine the service policy for the PVC:pvc cisco 0/5 service-policy output policy1vbr-nrt 2000 2000 encap aal5snapRelated Commands
pvc-bundle
To add a virtual circuit (VC) to a bundle as a member of the bundle and enter bundle-vc configuration mode in order to configure that VC bundle member, use the pvc-bundle bundle configuration command. The no form of this command removes the VC from the bundle.
pvc-bundle pvc-name [vpi/] [vci]
no pvc-bundle pvc-name [vpi/] [vci]Syntax Description
Defaults
None
Command Modes
Bundle configuration
Command History
Usage Guidelines
Each bundle can contain multiple VCs having different quality of service (QoS) attributes. This command associates a VC with a bundle, making it a member of that bundle. Before you can add a VC to a bundle, the bundle must exist. Use the bundle command to create a bundle. You can also use this command to configure a VC that already belongs to a bundle. You enter the command in the same way, giving the name of the VC bundle member.
The pvc-bundle command enters into bundle-vc configuration mode in which you can specify VC-specific and VC class attributes for the VC.
Examples
The following example specifies an existing bundle named chicago, and enters into bundle configuration mode. Then, it adds two VCs to the bundle. For each added VC, bundle-vc mode is entered and a VC class is attached to the VC to configure it.
bundle chicago pvc-bundle chicago-control 207 class control-class pvc-bundle chicago-premium 206 class premium-classThe following example configures the PVC called chicago-control, an existing member of the bundle called chicago, to use Class-Based Weighted Fair Queueing (CBWFQ). The example configuration attaches the policy map policy1 to the PVC. Once the policy map is attached, the classes comprising policy1 determine the service policy for the PVC chicago-control.
bundle chicago pvc-bundle chicago-control 207 class control-class service-policy output policy1Related 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 global configuration 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 {input | output} policy-map
no service-policy {input | output}Syntax Description
Defaults
No service policy is specified.
Command Modes
Global configuration
VC submode (for a standalone VC)
Bundle-vc configuration (for ATM VC bundle members)
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.
Attaching a service policy and enabling CBWFQ on an interface renders ineffective any commands related to fancy queueing such as commands pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED). You can configure these features only after 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, is 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.
Examples
The following example attaches the service policy map called policy9 to the input interface Serial1:
interface Serial1service-policy input policy9The following example attaches the service policy map called policy9 to the input permanent virtual circuit (PVC) called cisco:
pvc cisco 0/34 service-policy input policy9vbr-nt 5000 3000 500 precedence 4-7
The following example attaches the policy called policy9 to the output interface serial1 to specify the service policy for the interface and enable CBWFQ on it:interface serial1service-policy output policy9The following example attaches 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-3Related Commands
policy-map
Specifies a policy map to be assigned to an interface.
show policy
Displays configuration of all classes for a policy map.
show policy interface
To display the configuration of all classes configured for all service policies on the specified interface or to display the classes for the service policy for a specific permanent virtual circuit (PVC) on the interface, use the show policy interface global configuration command.
show policy interface interface-name [vc [vpi/] vci ] ]
Syntax Description
Defaults
There is no default behavior.
Command Modes
Global configuration
Command History
Usage Guidelines
The show policy interface command displays the configuration for classes on the specified interface or the specified PVC only if a service policy has been attached to the interface or the PVC.
You can use the pvc-name argument to display output for a PVC only for PA-A3 ATM port adapters that support per-VC queueing.
Examples
The following example displays configurations for classes on the output interface e1/1:
Router# show policy interface output e1/1Ethernet1/1 output : po1Weighted Fair QueueingClass class1Output Queue: Conversation 264Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11548/0/0Class class2Output Queue: Conversation 265Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11546/0/0Class class3Output Queue: Conversation 266Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11546/0/0Class class4Output Queue: Conversation 267Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11702/0/0Class class5Output Queue: Conversation 268Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11701/0/0Class class6Output Queue: Conversation 269Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11702/0/0Class class7Output Queue: Conversation 270Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11857/0/0Class class8Output Queue: Conversation 271Bandwidth 937 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 11858/1/0The following example displays configurations for classes comprising the service policy for the output VC 0/101 on the output interface atm2/0.6:
qos4-72a#show policy interface atm2/0.6ATM2/0.6: VC 0/101 - output : p1Weighted Fair QueueingClass c-vc1-c1Output Queue: Conversation 264Bandwidth 31 (kbps)mean queue depth: 1drops: class random tail min-th max-th mark-prob0 0 0 100 200 1/101 0 0 105 200 1/102 0 0 110 200 1/103 0 0 115 200 1/104 0 0 120 200 1/105 0 0 125 200 1/106 0 0 130 200 1/107 0 0 135 200 1/10rsvp 0 0 140 200 1/10Class c-vc1-c2Output Queue: Conversation 265Bandwidth 54 (kbps)mean queue depth: 1drops: class random tail min-th max-th mark-prob0 0 0 60 100 1/101 0 0 65 100 1/102 0 0 70 100 1/103 0 0 75 100 1/104 0 0 80 100 1/105 0 0 83 100 1/106 0 0 85 100 1/107 0 0 87 100 1/10rsvp 0 0 90 100 1/10Class c-vc1-c3Output Queue: Conversation 266Bandwidth 77 (kbps)mean queue depth: 0drops: class random tail min-th max-th mark-prob0 0 0 1 10 1/101 0 0 2 10 1/102 0 0 3 10 1/103 0 0 4 10 1/104 0 0 5 10 1/105 0 0 6 10 1/106 0 0 7 10 1/107 0 0 7 10 1/10rsvp 0 0 7 10 1/10Class c-vc1-c4Output Queue: Conversation 267Bandwidth 100 (kbps)mean queue depth: 9drops: class random tail min-th max-th mark-prob0 0 0 1 10 1/101 9 220 2 10 1/102 24 645 3 10 1/103 22 844 4 10 1/104 0 0 5 10 1/105 23 351 6 10 1/106 28 213 7 10 1/107 59 540 7 10 1/10rsvp 0 0 7 10 1/10Class c-vc1-c5Output Queue: Conversation 268Bandwidth 123 (kbps)mean queue depth: 150drops: class random tail min-th max-th mark-prob0 120 1777 50 150 1/501 136 1549 60 150 1/502 88 2354 70 150 1/503 121 1569 80 150 1/504 122 1717 80 150 1/505 0 0 90 150 1/506 0 0 100 150 1/507 105 2058 110 150 1/50rsvp 0 0 120 150 1/50Class c-vc1-c6Output Queue: Conversation 269Bandwidth 146 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 50216/32696/0Class c-vc1-c7Output Queue: Conversation 270Bandwidth 216 (kbps) Max Threshold 64 (packets)(total/discards/tail drops) 74577/51994/0Class class-defaultFlow Based Fair QueueingNumber of Hashed Queues 256drops: class random tail min-th max-th mark-prob0 101 828 50 150 1/501 87 1154 60 150 1/502 115 476 70 150 1/503 116 444 80 150 1/504 123 338 80 150 1/505 92 1042 90 150 1/506 79 1068 100 150 1/507 110 740 110 150 1/50rsvp 0 0 120 150 1/50Related Commands
show queue
To list fair queueing configuration and statistics for a particular interface or a specific virtual circuit (VC) on an ATM interface, use the show queue privileged EXEC command.
show queue interface-name interface-number [vc [vpi/] vci ] ]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays statistics for interfaces or VCs configured with the fair queueing strategy.
You can use the vc keyword and its arguments to display output for a PVC only for PA-A3 ATM port adapters that support per-VC queueing.
Examples
The following is sample output from the show queue command. Two conversations are active on the serial 1 interface. Weighted fair queueing ensures that both of these IP data streams, one TCP and the other UDP, receive equal bandwidth on the interface while they have messages in the pipeline.
Router# show queue serial1Input queue: 0/75/0 (size/max/drops); Total output drops: 303628Queueing strategy: weighted fairOutput queue: 64/1000/64/303628 (size/max total/threshold/drops)Conversations 2/2/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)(depth/weight/discards/tail drops/interleaves) 45/4096/1123/0/0Conversation 244, linktype: ip, length: 50source: 55.1.1.1, destination: 66.1.1.2, id: 0x0000, ttl: 59,TOS: 0 prot: 6, source port 55, destination port 55(depth/weight/discards/tail drops/interleaves) 19/4096/302541/0/0Conversation 185, linktype: ip, length: 118source: 55.1.1.1, destination: 66.1.1.2, id: 0x0000, ttl: 59,TOS: 0 prot: 17, source port 20, destination port 20The following is sample output from the show queue command for PVC 33 on the atm2/0.33 ATM subinterface. Two conversations are active on the this interface. WFQ ensures that both data streams receive equal bandwidth on the interface while they have messages in the pipeline.
Router# show queue atm2/0.33 vc 33Interface ATM2/0.33 VC 0/33Queueing strategy: weighted fairTotal output drops per VC: 18149Output queue: 57/512/64/18149 (size/max total/threshold/drops)Conversations 2/2/256 (active/max active/max total)Reserved Conversations 3/3 (allocated/max allocated)(depth/weight/discards/tail drops/interleaves) 29/4096/7908/0/0Conversation 264, linktype: ip, length: 254source: 15.1.1.1, destination: 1.0.2.20, id: 0x0000, ttl: 59,TOS: 0 prot: 17, source port 1, destination port 1(depth/weight/discards/tail drops/interleaves) 28/4096/10369/0/0Conversation 265, linktype: ip, length: 254source: 15.1.1.1, destination: 1.0.2.20, id: 0x0000, ttl: 59,TOS: 32 prot: 17, source port 1, destination port 2describes the fields shown in this display.
.
show queueing interface
To show the queueing statistics of an interface or a virtual circuit (VC), use the show queueing interface privileged EXEC command.
show queueing interface interface-number [vc [[vpi/] vci]]
Syntax Description
Command Mode
Privileged EXEC
Command History
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1(22)CC.
Examples
The following is sample output from the show queueing interface command. It shows the WFQ configuration for PVC 0/101 on the ATM subinterface ATM2/0.6. Eight conversations are active on the interface. WFQ ensures that all of these data stream receive equal bandwidth on the interface while they have messages in the pipeline.
Router# show queueing interface atm2/0 serial1Interface ATM2/0.6 VC 0/101Queueing strategy: weighted fair
