To see the difference between the traceroute and rtt's for multiple days , we developed the traceroute archive. It can be accessed using teh traceroutearchive.cgi script. It displays traceroute from a monitor node to monitoring node for any three days (which can be selected from drop down menu). It checks loops within the traceroute and shows the changes observed in a link for the requested days. It is currently available from 5 PingER monitors including SLAC to world wide nodes monitored by SLAC at http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi
Apart from SLAC, Historical traceroutes are available from the following monitors, from Feb 2014 onwards:
- www-wanmon.slac.stanford.edu
- pinger.cern.ch
- maggie1.seecs.edu.pk
- pinger.ictp.it
- pinger.fsktm.um.edu.my
Traceroute Archive Flow At SLAC
Following are scripts used for the traceroute archive
1. Collection of Traceroutes
1.1 autotrace.pl
This script can be found at /afs/slac/package/pinger/autotrace.pl. It saves all traceroutes from the SLAC Pinger nodes to its monitored sites and runs as cron job once everyday on pinger.slac,stanford.edu.
It uses: http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=www.fapesp.br
It gets the list of hosts to traceroute to by using wget and pingtable.pl.
Output iis saved in /afs/slac/package/pinger/chktrace/2011_08_24/www-wanmon.slac.stanford.edu_to_www.ab.kg_2011_08_28 as :
Panel |
---|
2011_08_28 15:21:43 |
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
Panel |
---|
Note:
Difference is counted as per IP name and IP number(RTTs are excluded) between any two traceroutes.
Bandwidth needed
We estimated the bandwidth needed for historical traceroute.
- The packet sent is 140bytes and the TTL exceeded response is at least 36bytes.
- Assume an average of 20 hops and 3 tries per hop since the version of traceroute server is old and does not support options.
- Total targets is 700.
- The size of the http response page is about 5.5kb (assuming images are cached)
This totals to about 11.2 MBytes of bandwidth usage per day.