Table Of Contents
Custom Queueing Configuration Task List
Defining the Custom Queue List
Specifying the Maximum Size of the Custom Queues
Assigning Packets to Custom Queues
Custom Queueing Configuration Examples
Custom Queue List Defined Example
Maximum Specified Size of the Custom Queues Examples
Packets Assigned to Custom Queues Examples
Configuring Custom Queueing
This chapter describes the tasks for configuring QoS custom queueing (CQ) on a router.
For complete conceptual information, see the "Congestion Management Overview" module.
For a complete description of the CQ commands in this chapter, see the Cisco IOS Quality of Service Solutions Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
CQ is not supported on any tunnels.
Custom Queueing Configuration Task List
You must follow certain required, basic steps to enable CQ for your network. In addition, you can choose to assign packets to custom queues based on protocol type, interface where the packets enter the router, or other criteria you specify.
To configure CQ, perform the tasks described in the following sections. The tasks in first and third sections are required; the tasks in the remaining sections are optional.
•
Defining the Custom Queue List (Required)
•
Specifying the Maximum Size of the Custom Queues (Optional)
•
Assigning Packets to Custom Queues (Required)
•
Monitoring Custom Queue Lists (Optional)
See the end of this chapter for the section "Custom Queueing Configuration Examples."
Defining the Custom Queue List
To assign a custom queue list to an interface, use the following commands beginning in global configuration mode:
Note
Use the custom-queue-list command in place of the priority-list command. Only one queue list can be assigned per interface.
CQ allows a fairness not provided with priority queueing (PQ). With CQ, you can control the available bandwidth on an interface when it is unable to accommodate the aggregate traffic enqueued. Associated with each output queue is a configurable byte count, which specifies how many bytes of data should be delivered from the current queue by the system before the system moves on to the next queue. When a particular queue is being processed, packets are sent until the number of bytes sent exceeds the queue byte count defined by the queue-list queue byte-count command (see the following section "Specifying the Maximum Size of the Custom Queues"), or until the queue is empty.
Specifying the Maximum Size of the Custom Queues
You can specify the maximum number of packets allowed in each of the custom queues. The default is 20 entries.
You can also specify the approximate number of bytes to be forwarded from each queue during its turn in the cycle. The number is used as an average number, because whole packets must be forwarded.
To specify the approximate number of bytes to be forwarded from each queue during its turn in the cycle, use the following commands in global configuration mode, as needed:
Assigning Packets to Custom Queues
You can assign packets to custom queues based on the protocol type or interface where the packets enter the router. Additionally, you can set the default queue for packets that do not match other assignment rules. You can also specify multiple rules.
To define the CQ lists, use the following commands in global configuration mode, as needed:
All protocols supported by Cisco are allowed. The queue-keyword variable provides additional options, including byte count, TCP service and port number assignments, and AppleTalk, IP, IPX, VINES, or XNS access list assignments. Refer to the queue-list protocol command syntax description in the Cisco IOS Quality of Service Solutions Command Reference.
When you use multiple rules, remember that the system reads the queue-list commands in order of appearance. When classifying a packet, the system searches the list of rules specified by queue-list commands for a matching protocol or interface type. When a match is found, the packet is assigned to the appropriate queue. The list is searched in the order it is specified, and the first matching rule terminates the search.
Monitoring Custom Queue Lists
To display information about the input and output queues when CQ is enabled on an interface, use the following commands in EXEC mode, as needed:
Custom Queueing Configuration Examples
The following sections provide custom queueing examples:
•
Custom Queue List Defined Example
•
Maximum Specified Size of the Custom Queues Examples
•
Packets Assigned to Custom Queues Examples
For information on how to configure CQ, see the section "Custom Queueing Configuration Task List" in this chapter.
Custom Queue List Defined Example
The following example illustrates how to assign custom queue list number 3 to serial interface 0:
interface serial 0custom-queue-list 3Maximum Specified Size of the Custom Queues Examples
The following example specifies the maximum number of packets allowed in each custom queue. The queue length of queue 10 is increased from the default 20 packets to 40 packets.
queue-list 3 queue 10 limit 40The queue length limit is the maximum number of packets that can be enqueued at any time, with the range being from 0 to 32767 queue entries.
The following example decreases queue list 9 from the default byte count of 1500 to 1400 for queue number 10:
queue-list 9 queue 10 byte-count 1400The byte count establishes the lowest number of bytes the system allows to be delivered from a given queue during a particular cycle.
Packets Assigned to Custom Queues Examples
The following examples assign packets to custom queues by either protocol type or interface type, and the default assignment for unmatched packets.
Protocol Type
The following example assigns traffic that matches IP access list 10 to queue number 1:
queue-list 1 protocol ip 1 list 10The following example assigns Telnet packets to queue number 2:
queue-list 4 protocol ip 2 tcp 23The following example assigns User Datagram Protocol (UDP) Domain Name Service (DNS) packets to queue number 3:
queue-list 4 protocol ip 3 udp 53Interface Type
In this example, queue list 4 establishes queueing priorities for packets entering on serial interface 0. The queue number assigned is 10.
queue-list 4 interface serial 0 10Default Queue
You can specify a default queue for packets that do not match other assignment rules. In this example, the default queue for list 10 is set to queue number 2:
queue-list 10 default 2CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0804R)
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.

