Page 354

328 Chapter 10: Managing Network Performance with Queuing and Compression

Example 10-16 includes the necessary configuration for this task. The default queue is
configured last.

Scenario 10-3 Answers

To meet the needs specified by this scenario, a priority queuing implementation is
necessary.

Example 10-17 details the configuration for this task. DNS, FTP, Telnet, TFTP, and HTTP
are placed into the high-priority queue.

Example 10-17 details the configuration for this task. The remaining IP traffic is placed
into the medium queue to meet the requirement that it be a high priority, but not as high
as the protocols mentioned in Task 2.

Example 10-17 details the configuration for this task. IPX and AppleTalk are placed into
the normal queue so that they are serviced when all IP has been dispatched.

Example 10-17 details the configuration for this task. The default queue is set to low. Any
traffic not specified in the list is placed there.

Example 10-16

Scenario Configuration for the San Mateo Router

queue-list 1 protocol ip 1 tcp 20
queue-list 1 protocol ip 1 tcp 21
queue-list 1 protocol ip 1 tcp 23
queue-list 1 protocol ip 1 tcp 80
queue-list 1 protocol ip 1 udp 69
queue-list 1 protocol ip 2
queue-list 1 protocol ipx 3
queue-list 1 protocol appletalk 4
queue-list 1 queue-limit 100
queue-list 1 byte-count 7500
queue-list 1 default 5
interface serial 0
custom-queue-list 1

Example 10-17

Scenario Configuration for the Atlanta Router

priority-list 4 protocol ip high tcp 53
priority-list 4 protocol ip high udp 53
priority-list 4 protocol ip high tcp 20
priority-list 4 protocol ip high tcp 21
priority-list 4 protocol ip high udp 69
priority-list 4 protocol ip high tcp 80
priority-list 4 protocol ip medium
priority-list 4 protocol ipx normal
priority-list 4 protocol appletalk normal
priority-list 4 default low
interface serial 0
priority-group 4