Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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.brImage Removed

 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 :

...

This script is placed at /afs/slac.stanford.edu/g/www/cgi-wrap-bin/net/offsite_mon.

Example is

Panel

http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi?from=www-wanmon.slac.stanford.edu&to=www.uda.ad&date1=2011_08_28&date2=2011_11_04&date3=2012_01_09Image Removed

Note:

Difference is counted as per IP name and IP number(RTTs are excluded) between any two traceroutes.