...
Due to some unavoidable reasons, no smokeping graphs could be generated so far. Once we resolve the issue, we'll show smokeping graphs and traceroutes to support the improvement in network performance.
Traceroute were taken from PERN POP Islamabad to Uettaxila showing the RTT at each hop.
| Code Block |
|---|
Executing exec(traceroute, -m 30 -q 3 -f 3, 121.52.150.164, 140)
traceroute to 121.52.150.164 (121.52.150.164), 30 hops max, 140 byte packets
4 rwp44.pie.net.pk (221.120.254.5) 44.905 ms rwp44.pie.net.pk (221.120.251.29) 24.137 ms rwp44.pie.net.pk (221.120.254.5) 44.803 ms
5 rwp44.pie.net.pk (221.120.254.61) 45.150 ms 45.167 ms rwp44.pie.net.pk (221.120.254.13) 46.383 ms
6 rwp44.pie.net.pk (221.120.253.122) 45.073 ms 45.118 ms 45.168 ms
7 uettaxila.pie.net.pk (221.120.235.126) 58.911 ms 58.896 ms 58.880 ms
8 (121.52.150.164) 46.431 ms !X 46.175 ms !X 46.519 ms !X
|
It is observed that the route goes through the 3 interfaces named rwp44.pie.net.pk. Delay to reach rwp44.pie.net.pk is much longer which results in increased RTT for uettaxila. However, from there it takes only 13.8 ms to reach uettaxila.
Suggestions from improvement:
...
Reduced average RTT is a consequence of increased link capacity.
Unresolved Issue:
- Since Friday 5/13/11, I am unable to load SEECS pingtable and the smokeping graphs from SEECS pingtable. I need them for analysis. Can someone get this resolved so that I can make report as soon as possible.