background image
308 Chapter 10: Managing Network Performance with Queuing and Compression
Configuring Custom Queuing
As with priority queuing, the configuration of custom queuing involves the creation of a list and
associating a group with an interface. Traffic in the queues can be configured based on a specific
traffic type, protocol, or input interface. Access lists can be configured to place specific traffic
types into a particular queue, and traffic not designated to a particular queue can be placed in a
default queue.
NOTE
To implement custom queuing on a Frame Relay interface, Frame Relay traffic shaping must
be disabled.
The tasks involved in the configuration are as follows:
1
Define specific access lists (if they are to be used).
2
Create the queue list.
3
Apply the queue list to the interface.
4
Verify the queuing process.
Defining Specific Access Lists
If you want queue traffic to be based on a specific network address, protocol, or application,
access lists can be put in place to sort the traffic. Standard or extended access lists can be defined
to specify the traffic types that should be placed into a specific queue.
Access list configuration is not discussed in this book. For additional information on access
lists, check out www.cisco.com and perform a search on "access-list."
Creating the Queue List
The command structure for custom queuing is as follows:
RouterA(config)#queue-list list-number protocol protocol-name queue-number
queue-keyword keyword-value
The list-number argument can be an arbitrarily selected number from 1­16; however, all lines
for a particular queue list must have the same list-number to function properly. The queue-
keyword
and keyword-value arguments are utilized in the association of access lists with the
queue list. Example 10-7 shows a configuration example utilizing this command.