...
Looking at the raw data read from NIIT for UETAXILA it confirms RTT os ~ 5ms.
| Code Block |
|---|
58cottrell@pinger:~>grep monitor /tmp/average_rtt-100-by-node-2011-05-01.txt \| grep uettax
monitor.niit.edu.pk pinger.uettaxila.edu.pk 3.590 4.021 4.021 4.226 5.036 6.491 7.223 6.147 6.389 7.042 7.042 5.601 5.601 6.365 6.365 6.588 4.592 4.951 5.030 7.237 6.474 5.321 4.780 4.739 monitor.niit.edu.pk pinger.uettaxila.edu.pk
pinger.uettaxila.edu.pk monitor.niit.edu.pk . 4.438 4.438 5.706 5.235 6.316 6.521 7.613 5.898 6.036 6.036 6.088 6.088 5.835 5.835 6.321 6.665 6.665 6.280 7.356 9.075 5.183 4.605 4.654 pinger.uettaxila.edu.pk monitor.niit.edu.pk
|
The drop in RTT is also confirmed looking at the FNAL graph:
Looking at the traceroutes from monitor.niit.edu.pk to uettaxila on one of the days of low Avg_RTT (here 5/1/2011) one gets the following message:
| Code Block |
|---|
traceroute server busy at the moment. Please try again later. See The Naming System for information on host.domain and Addresses for information on Internet addresses.
|
To get a better view of the situation, we try to look at the reverse route i.e from pinger.uettaxila.edu.pk to monitor.niit.edu.pk. The smokeping graph thus obtained is: 
Looking at the traceroutes from pinger.uettaxila.edu.pk to monitor.niit.edu.pk on one of the days of low Avg_RTT (here 5/1/2011) following output is observed:
| Code Block |
|---|
Executing exec(traceroute, -m 30 -q 3 -f 3, 115.186.131.81, 140)
traceroute to 115.186.131.81 (115.186.131.81), 30 hops max, 140 byte packets
3 rwp44.pie.net.pk (221.120.253.121) 5.457 ms 5.444 ms 5.435 ms
4 rwp44.pie.net.pk (221.120.254.62) 6.247 ms 7.673 ms 7.667 ms
5 rwp44.pie.net.pk (221.120.253.10) 4.555 ms 4.556 ms 4.547 ms
6 rwp44.pie.net.pk (221.120.237.102) 4.538 ms 4.534 ms 4.529 ms
7 58-65-175-206.nayatel.pk (58.65.175.206) 4.506 ms 4.500 ms 4.726 ms
8 * 115-186-128-178.nayatel.pk (115.186.128.178) 6.589 ms 6.587 ms
9 115-186-131-81.nayatel.pk (115.186.131.81) 6.429 ms 4.927 ms 4.914 ms
|