1 / 13

Traceanal: a tool for analyzing and representing traceroutes

Traceanal: a tool for analyzing and representing traceroutes. Les Cottrell , Connie Logg, Ruchi Gupta, Jiri Navratil SLAC, for the E2Epi BOF, Columbus Ohio, July 2004 www.slac.stanford.edu/grp/scs/net/talk03/e2ebof-jul04.ppt.

watsont
Download Presentation

Traceanal: a tool for analyzing and representing traceroutes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Traceanal: a tool for analyzing and representing traceroutes Les Cottrell, Connie Logg, Ruchi Gupta, Jiri Navratil SLAC, for the E2Epi BOF, Columbus Ohio, July 2004 www.slac.stanford.edu/grp/scs/net/talk03/e2ebof-jul04.ppt Partially funded by DOE/MICS Field Work Proposal on Internet End-to-end Performance Monitoring (IEPM), also supported by IUPAP

  2. Need • A way to visualize traceroutes taken at regular intervals to several tens of remote hosts • Report all the pathologies identified • Allow quick visual inspection for: • Multiple routes • Significant route changes • Pathologies • Drill down to more detailed information • Histories • Topologies • Related bandwidth & alerts • E.g. for AMP, PiPES, Surveyor, IEPM etc.

  3. Display many routes on single page • One row per host, one column per hour • Identify unique routes with a number • Be able to inspect the route associated with a route number • Use single character to ID a route that has not significantly changed • Character identifies pathology of route (usually period(.)= no change) Route # at start of day, gives idea of route stability Multiple route changes (due to GEANT), later restored to original route Period (.) means no change

  4. Pathologies • Hop does not respond (*) • End host does not respond, i.e. 30 hops (|) • End host does not ping (turn red) • Stutters (“) • Hop change only affects 4th octet (: ) • Hop change but address in same AS (a) • ICMP checksum (orange) • ! Annotation e.g. network unreachable, admin blocked • Multi-homed host • Probe type: UDP or ICMP

  5. Pathologies Change but same AS No change Probe type Change in only 4th octet End host not pingable Hop does not respond Stutter Multihomed ICMP checksum ! Annotation (!X)

  6. Navigation traceroute to CCSVSN04.IN2P3.FR (134.158.104.199), 30 hops max, 38 byte packets 1 rtr-gsr-test (134.79.243.1) 0.102 ms … 13 in2p3-lyon.cssi.renater.fr (193.51.181.6) 154.063 ms !X

  7. History Channel

  8. AS’ information

  9. Coming soon • Bandwidth & alerts Capacity Available bandwidth RTT X traffic

  10. … and Topology • Choose times and hosts and submit request Hour of day SLAC ESnet Alternate rt GEANT Alternate route JAnet Nodes colored by ISP Mouseover shows node names Click on node to see subroutes Click on end node to see its path back Also can get raw traceroutes with AS’ CESnet IN2P3 DL CLRC

  11. … and • Apply to AMP data

  12. Availability • Tested on Linux • Mainly in Perl, apart from topology • 2200 lines of Perl code; ? lines of C (topology) • Web server for CGI scripts (topology, archived data)

  13. More information • Example: • http://www.slac.stanford.edu/comp/net/bandwidth-tests/hercules/tracesummaries/today.html • Where to get it: • Topology: • http://pcgiga.cern.ch:8080/cgi-bin/pnets.pl • IEPM-BW home page • http://www-iepm.slac.stanford.edu/bw/ • ABwE lightweight bandwidth estimation • http://www-iepm.slac.stanford.edu/abing/

More Related