[ LiB ]Practical Exercise: Configuring Priority Queuing Summary

Practical Exercise Solution

Example 11-24 shows the solution to the Practical Exercise, and Example 11-25 shows the output of show queueing priority.

Example 11-24. Solution to Practical Exercise
R1#show running-config
version 12.1
!
hostname R1
ip subnet-zero
!
!
interface Ethernet0/0
 ip address 172.16.100.1 255.255.255.0
 half-duplex
!
interface Ethernet0/1
 ip address 64.236.24.1 255.255.255.0
 half-duplex
!
interface Serial0/2
ip address 10.1.2.1 255.255.255.252
 priority-group 1
!
router ospf 1
 log-adjacency-changes
 network 10.1.2.0 0.0.0.3 area 0
 network 172.16.100.0 0.0.0.255 area 0
 network 64.236.24.0 0.0.0.255 area 0
!
ip classless
!
access-list 1 permit 64.236.24.0 0.0.0.255
priority-list 1 protocol ip high list 1
priority-list 1 protocol ip low tcp ftp-data
!
end

Example 11-25. Output of show queueing priority
R1#show queueing priority
Current DLCI priority queue configuration:
Current priority queue configuration:

List   Queue  Args
1      high   protocol ip          list 1
1      low    protocol ip          tcp port ftp-data

Example 11-26 shows the output of the debug priority command. Note that packets from network 64.236.24.0/24 are placed in the high-priority queue. You can also see that FTP traffic is being placed in the low-priority queue.

Example 11-26. Output of debug priority
R1#
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (s=64.236.24.25, d=172.16.101.26) -> high
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2: ip (tcp 20) -> low

Example 11-27 uses extended pings to verify queuing operation.

Example 11-27. Using Extended Pings to Verify Queuing Operation
R1#ping
Protocol [ip]:
Target IP address: 172.16.101.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.101.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms

R1#
4d02h: PQ: Serial0/2: ip (s=64.236.24.1, d=172.16.101.1) -> high
4d02h: PQ: Serial0/2 output (Pk size/Q 104/0)
4d02h: PQ: Serial0/2: ip (s=64.236.24.1, d=172.16.101.1) -> high
4d02h: PQ: Serial0/2 output (Pk size/Q 104/0)
4d02h: PQ: Serial0/2: ip (s=64.236.24.1, d=172.16.101.1) -> high
4d02h: PQ: Serial0/2 output (Pk size/Q 104/0)
4d02h: PQ: Serial0/2: ip (s=64.236.24.1, d=172.16.101.1) -> high
4d02h: PQ: Serial0/2 output (Pk size/Q 104/0)
4d02h: PQ: Serial0/2: ip (s=64.236.24.1, d=172.16.101.1) -> high
4d02h: PQ: Serial0/2 output (Pk size/Q 104/0)

R1#ping
Protocol [ip]:
Target IP address: 172.16.101.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.16.100.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.101.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms
R1#
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2 output (Pk size/Q 104/2)
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2 output (Pk size/Q 104/2)
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2 output (Pk size/Q 104/2)
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2 output (Pk size/Q 104/2)
4d02h: PQ: Serial0/2: ip (defaulting) -> normal
4d02h: PQ: Serial0/2 output (Pk size/Q 104/2)
4d02h: PQ: Serial0/2 output (Pk size/Q 24/0)

[ LiB ]Practical Exercise: Configuring Priority Queuing Summary