Note: This lab was a collaborative effort with Jeff Baier
It is important to not load the TGN traffic generator configuration as previously done in labs 4.1 and 4.2
Output for NQR configuration:
fastethernet0/0
add tcp
send 1000
rate 60
length random 200 to 1000
l2-dest 0014.a969.1070
l3-src 172.16.10.4
l3-dest 172.16.20.4
l4-dest 23
fastethernet0/1 capture
add clone-of 1
l4-dest 21
add clone-of 1
l4-dest 119
add clone-of 1
l4-dest 22
add clone-of 1
When we first tried the lab, we had 9 traffic streams, compared to 5 in the lab manual. The rest of the lab would then not work. After checking we realized we had pasted in the NQR configuration incorrectly. We scrubbed the pod and started over, this time with the correct NQR config and now it is working right, and there are only 5 traffic streams.
After running the start send command, time will pass, and then the router will inform you when all packets have been sent. The “Time will pass” meant only about 15 seconds for us.
FIFO is on by default when no other queueing types are enabled.
TrafGen(NQR:OFF,Fa0/0:5/5)#sh pkt-seq-drop-stats
Summary of packet sequence/drop stats of traffic streams
ts# template interface sent recvd dropped out-of-seq max-seq
1 TCP Fa0/0 1000 85 915 37 27
2 TCP Fa0/0 1000 144 856 33 50
3 TCP Fa0/0 1000 142 858 29 47
4 TCP Fa0/0 1000 149 851 26 59
5 TCP Fa0/0 1000 64 936 29 27
TrafGen(NQR:OFF,Fa0/0:5/5)#sh delay
Summary of delay-stats of traffic streams
ts# template interface min-delay max-delay avg-delay stdev-delay
1 TCP Fa0/0 0.057936 0.803841 0.390446 0.125760
2 TCP Fa0/0 0.008399 0.420713 0.323438 0.089587
3 TCP Fa0/0 0.019842 0.449999 0.329806 0.107765
4 TCP Fa0/0 0.030354 0.437458 0.310051 0.103980
5 TCP Fa0/0 0.037837 0.772656 0.406740 0.144821
TrafGen(NQR:OFF,Fa0/0:5/5)#sh jitter
Summary of jitter-stats of traffic streams
ts# template interface min-jitter max-jitter avg-jitter stdev-jitter
1 TCP Fa0/0 0.000169 0.399956 0.080740 0.101643
2 TCP Fa0/0 0.007366 0.182717 0.083387 0.035971
3 TCP Fa0/0 0.010463 0.242322 0.094656 0.054160
4 TCP Fa0/0 0.000168 0.181835 0.098233 0.036947
5 TCP Fa0/0 0.001478 0.352950 0.107737 0.103940
After WFQ On both serial interfaces:
TrafGen(NQR:OFF,Fa0/0:5/5)#sh pkt-seq-drop-stats
Summary of packet sequence/drop stats of traffic streams
ts# template interface sent recvd dropped out-of-seq max-seq
1 TCP Fa0/0 1000 62 938 28 29
2 TCP Fa0/0 1000 157 843 36 50
3 TCP Fa0/0 1000 165 835 33 82
4 TCP Fa0/0 1000 165 835 30 52
5 TCP Fa0/0 1000 102 898 50 30
TrafGen(NQR:OFF,Fa0/0:5/5)#sh delay
Summary of delay-stats of traffic streams
ts# template interface min-delay max-delay avg-delay stdev-delay
1 TCP Fa0/0 0.012909 0.802448 0.411571 0.167596
2 TCP Fa0/0 0.025648 0.452551 0.330156 0.115428
3 TCP Fa0/0 0.022489 0.449449 0.302500 0.113113
4 TCP Fa0/0 0.017471 0.451252 0.337060 0.101554
5 TCP Fa0/0 0.008788 0.803437 0.425355 0.134657
TrafGen(NQR:OFF,Fa0/0:5/5)#sh jitter
Summary of jitter-stats of traffic streams
ts# template interface min-jitter max-jitter avg-jitter stdev-jitter
1 TCP Fa0/0 0.000712 0.393095 0.118065 0.126037
2 TCP Fa0/0 0.000562 0.247177 0.100784 0.058709
3 TCP Fa0/0 0.008739 0.187170 0.103791 0.046940
4 TCP Fa0/0 0.000087 0.221418 0.089329 0.050680
5 TCP Fa0/0 0.000159 0.385631 0.083481 0.110551
To setup Custom Queueing
Cisco instructions to setup custom queueing or look at appendix in lab for an example of how to setup custom queueing.
TrafGen(NQR:WAIT,Fa0/0:5/5)#sh pkt-seq-drop-stats
WARNING: Traffic generation Currently on.
The packets in transit are counted as dropped
Summary of packet sequence/drop stats of traffic streams
ts# template interface sent recvd dropped out-of-seq max-seq
1 TCP Fa0/0 1000 354 646 262 17
2 TCP Fa0/0 1000 723 277 202 64
3 TCP Fa0/0 1000 729 271 187 65
4 TCP Fa0/0 1000 725 275 188 80
5 TCP Fa0/0 1000 364 636 261 16
TrafGen(NQR:WAIT,Fa0/0:5/5)#
TrafGen(NQR:OFF,Fa0/0:5/5)#sh delay-stats
Summary of delay-stats of traffic streams
ts# template interface min-delay max-delay avg-delay stdev-delay
1 TCP Fa0/0 0.003821 0.563391 0.474184 0.078021
2 TCP Fa0/0 0.008626 0.562538 0.451431 0.076181
3 TCP Fa0/0 0.009091 0.601371 0.442814 0.088573
4 TCP Fa0/0 0.004680 0.616352 0.442122 0.099195
5 TCP Fa0/0 0.009104 0.598018 0.476281 0.077497
TrafGen(NQR:OFF,Fa0/0:5/5)#sh jitter-stats
Summary of jitter-stats of traffic streams
ts# template interface min-jitter max-jitter avg-jitter stdev-jitter
1 TCP Fa0/0 0.000782 0.252218 0.060681 0.051143
2 TCP Fa0/0 0.000033 0.284539 0.058684 0.049382
3 TCP Fa0/0 0.000116 0.331612 0.060187 0.065775
4 TCP Fa0/0 0.000124 0.301200 0.081352 0.057493
5 TCP Fa0/0 0.000660 0.261888 0.060208 0.050835
Try making one of the queues have a size of 10000. How does this affect all of
the traffic flows?
It allows steams 1 and 5 to almost not drop any, while the other streams got worse and dropped a lot more.
After applying priority queueing
TrafGen(NQR:OFF,Fa0/0:5/5)#sh pkt-seq-drop-stats
Summary of packet sequence/drop stats of traffic streams
ts# template interface sent recvd dropped out-of-seq max-seq
1 TCP Fa0/0 1000 1000 0 0 1000
2 TCP Fa0/0 1000 850 150 109 164
3 TCP Fa0/0 1000 81 919 0 81
4 TCP Fa0/0 1000 61 939 0 61
5 TCP Fa0/0 1000 1000 0 0 1000
TrafGen(NQR:OFF,Fa0/0:5/5)#sh delay-stats
Summary of delay-stats of traffic streams
ts# template interface min-delay max-delay avg-delay stdev-delay
1 TCP Fa0/0 0.007056 0.030114 0.017861 0.004088
2 TCP Fa0/0 0.009582 1.004727 0.714964 0.200605
3 TCP Fa0/0 0.014017 0.014017 0.014017 N/A
4 TCP Fa0/0 0.009314 0.009314 0.009314 N/A
5 TCP Fa0/0 0.007834 0.032614 0.019193 0.004371
TrafGen(NQR:OFF,Fa0/0:5/5)#sh jitter-stats
Summary of jitter-stats of traffic streams
ts# template interface min-jitter max-jitter avg-jitter stdev-jitter
1 TCP Fa0/0 0.000012 0.012252 0.003326 0.002402
2 TCP Fa0/0 0.000062 0.432661 0.173587 0.101557
3 TCP Fa0/0 N/A N/A N/A N/A
4 TCP Fa0/0 N/A N/A N/A N/A
5 TCP Fa0/0 0.000019 0.013464 0.003540 0.002599
How does the packet loss with PQ compare to that of previous queuing
strategies?
The normal and low priorities had lots of packets dropped, while the higher priority streams almost got all their traffic through.
What would happen if you put all the streams in the high priority queue?
It would have the same results as FIFO queueing, because they would all be competing again.
Note of interest:
*Mar 13 20:49:49.187: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 172.16.10.1 (FastEthernet0/0) is down: holding time expired
*Mar 13 20:49:52.071: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 172.16.10.1 (FastEthernet0/0) is up: new adjacency
Since we are filling the queues with generated traffic, routing updates from EIGRP are not getting through. We keep seeing the above 2 messages because the hold down timers expire, and then later the routing updates get through and EIGRP sees the interface as a new adjacency.
ip route 172.16.20.0 255.255.255.0 Serial0/0/0
