To see the difference between traceroute and rtt's for multiple days , we developed traceroute archive. It can be accessed using traceroutearchive.cgi script. It displays traceroute from a monitor node to the monitoring node for any three days (which can be selected from drop down menu). It checks loops within traceroute and shows the changes observed in a link for the requested days. It is currently available from SLAC to world wide nodes monitored by SLAC at http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi and also from pingER Seecs to all monitored sites within Pakistan at http://pinger.seecs.edu.pk/cgi-bin/traceroutearchive.cgi
Traceroute Archive Flow At SLAC
Following are scripts used for traceroute archive
?1. Collection of Traceroutes
1.1 autotrace.pl
This script can be found at /afs/slac/package/pinger. It saves traceroutes from all SLAC Pinger nodes to its monitored sites and runs as cron job once everyday.
Input = http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=www.fapesp.br
Output = it is saved in /afs/slac.stanford.edu/package/pinger/Traceroutes/www-wanmon.slac.stanford.edu/www-wanmon.slac.stanford.edu_to_www.fapesp.br_2011_08_24 as :
2011_08_24 11:48:0
Executing exec(traceroute, -m 30 -q 3, 143.108.10.6, 140)
traceroute to 143.108.10.6 (143.108.10.6), 30 hops max, 140 byte packets
1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) 0.554 ms 0.606 ms 0.768 ms
2 rtr-core2-p2p-servcore1.slac.stanford.edu (134.79.252.162) 0.417 ms 0.453 ms 0.504 ms
3 rtr-border1-p2p-core2.slac.stanford.edu (134.79.252.137) 0.582 ms 0.636 ms 0.767 ms
Traceroutes of all the nodes for a day are collected in date folders.
2. Display of traceroutes
2.1 traceroutearchive.cgi
This script is placed at /afs/slac.stanford.edu/g/www/cgi-wrap-bin/net/offsite_mon.
Example is
Note:
Difference is counted as per IP name and IP number(RTTs are excluded) between any two traceroutes.