Page History

...

 There was a big improvement in the min RTT to IIU from all sites between Sep and Oct 2010. The reason is IIU's shift to PERN network. It's IP is 111.68.97.162 (IP addresses starting with 111 and 121 are on PERN network) so this confirms that it is now on PERN network. The reason for higher min RTT was basically due to IIU using the public/service-provider network. A screenshot of pingtable shows an observation of this change.

...

• LHR to LHR is good (green).
• PWR/NWFP to LHR is good (green). PWR and NWFP belong to the PWR (Peshawar) region. This traffic goes via ISB region.
• ISB shows miscellaneous patterns and this is due to nodes being on different networks and following different routes:
  • Nodes in ISB that are on PERN network show good performance (green). These are: pinger.pern.edu.pk (121.52.147.253), vle.iiu.edu.pk (111.68.97.162), pinger-ncp.ncp.edu.pk (111.68.99.142), www.pieas.edu.pk (111.68.99.199) and pinger.uaar.edu.pk (111.68.99.248).
  • Nodes not on PERN network show higher RTT (orange and red): SEECS maggie1, maggie2, monitor nodes and pinger.comsats.edu.pk (203.124.40.43).
• We do not fully understand why pinger.comsats.edu.pk (203.124.40.43) has lower min RTT to pinger.nwfpuet.edu.pk (121.52.148.71) and pinger.pwr.nu.edu.pk (121.52.148.110) than vle.iiu.edu.pk (111.68.97.162) or maggie1.niit.edu.pk (115.186.131.81) since COMSATS and NIIT are on public network and NWFPUET, PWR and IIU are on PERN network. However some explanations that come to mind are:
  • COMSATS node experiences higher packet loss for nodes at NIIT (around 6.6%) whereas a low packet loss for NWFPUET and PWR (0.48% and 0.40%). We send 10 packets every 30 minutes so this means it loses about 32 packets every day out of 480 for NIIT and only 2 are lost for IIU, NWFPUET and PWR. This is enough to impact the average minimum RTT for the day and consequently for the entire month.
  • NIIT node is on public network and also experiences a lot of traffic. Therefore there are higher delays and thus higher min RTTs.
  • Why COMSATS has higher min RTT to IIU is an anomaly since it has lower min RTT to other PERN connected nodes such as NWFPUET and PWR.
• PWR-PWR and PWR-NWFP is good (green). PWR and NWFP belong to PWR (Peshawar) region.
• TAX to LHR is better than TAX to LHR:
  • pinger.uettaxila.edu.pk (121.52.150.164) is on PERN network. Most nodes in Lahore are on PERN network: LSE (111.68.102.40), pinger.lcwu.edu.pk (111.68.103.135), pinger.nca.edu.pk (111.68.102.69), pinger.lhr.nu.edu.pk (111.68.102.125), pinger-itc.pu.edu.pk (111.68.103.29) and pinger.uet.edu.pk (111.68.102.14) but about half of the nodes in Islamabad such as SEECS maggie1, maggie2, monitor nodes and COMSATS are not on PERN network. However this doesn't fully explain why this is so.
  • Another inconsistency shown by stats is in inter-city routes. PERN network (shown above in Map of PERN2) is not fully deployed. In fact most of the inter-city routes aren't yet deployed. This is confirmed by the following two traceroutes of February 2, 2011.

 3  rwp44.pie.net.pk (202.125.148.157)  7.978 ms  7.978 ms  7.937 ms
 4  lhr63.pie.net.pk (221.120.254.2)  14.655 ms  15.388 ms  15.373 ms
 5  rwp44.pie.net.pk (221.120.252.226)  14.641 ms  15.355 ms  15.847 ms
 6  lhr63.pie.net.pk (221.120.216.198)  16.697 ms  14.582 ms  17.351 ms
 7  172.31.240.34 (172.31.240.34)  14.802 ms  14.559 ms  15.279 ms
 8  172.31.252.206 (172.31.252.206)  15.270 ms  14.144 ms  98.436 ms
 9  nca.edu.pk (111.68.102.69)  98.421 ms  14.677 ms  14.650 ms

 3  rwp44.pie.net.pk (202.125.148.157)  12.758 ms  7.817 ms  8.080 ms
 4  lhr63.pie.net.pk (221.120.254.2)  14.264 ms  15.546 ms  15.538 ms
 5  rwp44.pie.net.pk (221.120.252.226)  14.488 ms  14.991 ms  13.693 ms
 6  lhr63.pie.net.pk (221.120.216.198)  15.735 ms  20.109 ms  49.523 ms
 7  172.31.240.38 (172.31.240.38)  50.542 ms  50.788 ms  53.875 ms
 8  172.31.252.230 (172.31.252.230)  51.799 ms  46.953 ms  42.042 ms
 9  lhr-nu.edu.pk (111.68.102.125)  14.395 ms  14.163 ms  14.391 ms

RTT and Losses for 2010

...