1 / 13

Integration of AMP & Tracenol

This project aims to integrate AMP & Tracenol for packet loss, throughput, and route information analysis. It provides a way to visualize traceroutes, report pathologies, and allow quick inspection for multiple routes, significant route changes, and more.

jtuck
Download Presentation

Integration of AMP & Tracenol

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. Integration of AMP&Tracenol By: Qasim Bilal Lone

  2. Introduction Project Detail AMP Tracenol (RTT) Packet loss Throughput Route information Multiple routes significant route changes Pathologies

  3. TRACENOL

  4. 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

  5. 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 Period (.) means no change

  6. Pathologies • Hop does not respond (*) • End host does not respond, i.e. 30 hops (|) • End host does not ping (turn red) • Stutters (“) • 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

  7. Pathologies Change but same AS No change Probe type End host not pingable Hop does not respond Stutter Multihomed ICMP checksum ! Annotation (!X)

  8. 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

  9. History Channel

  10. Availability • Tested on Linux • Mainly in Perl • Web server for CGI scripts (topology, archived data)

  11. Current Work • Installation of Traceanal in Linux machine • Installation and configuration of pre requisites • Perl • Apache • Configuration in the perl scripts of traceanal, i.e is setting up of the required variables. • Errors due to missing package of utills.

  12. Future Task • Find the desired package for installation. • Run traceanal as a separate module. • Documentation of work already done.

  13. References • http://www.slac.stanford.edu/comp/net/bandwidth-tests/hercules/tracesummaries/today.html

More Related