Routing Measurements Matt Zekauskas, ITF Meeting 2006-Apr-24

Matt Zekauskas2 Pointer to this presentation Right now: SMM-ITF-Routing- Measurements.pdf Soon also on the meeting pages

Matt Zekauskas3 Overview Chris has provided motivation and some examples I’m going to go through some tools that can help, that we recommend installing if you do not already have them I’ll provide some other pointers to commercial tools I am aware of, but have no experience with

Matt Zekauskas4 RouteViews A project started at the University of Oregon In partnership with commercial carriers Original idea: low-cost Cisco router peers with as many other networks as possible Each network provides it’s own view of the routing table Thus, this central point has many views into the routing table – Route Views.

Matt Zekauskas5 RouteViews Today: multiple central servers, including the a Cisco system and some PCs running Zebra routing code Central implies BGP multi-hop, which means the central server only gets the best view of a given route from each source, and can’t get information about a disruption if the disruption also severs the link to the central collector

Matt Zekauskas6 RouteViews Placing servers out at networks to catch more routing anomalies and updates during network outages Additional work to see more than just the best route (Chris’ talk)

Matt Zekauskas7 RouteViews Chris has shown the usefulness More views => A better picture => More insight The central collectors have additional capacity to accept new peerings. Peer with a central collector – it’s easy and can be done quickly. Consider adding a local collector if you have the space and interest, but multi-hop BGP peer as a first step

Matt Zekauskas8 RouteViews Contact to create a peering or prepare for a local collector: IP Address AS Number Contact name & Any documentation on BGP communities Please let us know as well

Matt Zekauskas9 End-to-End Views RouteViews gives you snapshots of the routing table -- how one network gets to another. Sometimes you just want to know the router hops from one point to another Verification of RouteViews information Quickly understand what’s happening now Constant monitoring of important points

Matt Zekauskas10 End-to-End Views Two projects have been taking routing measurements for some time, in the form of traceroutes from measurement points AMP – general mesh among probes IEPM-BW – Mesh for high-energy physics In addition, the skitter project from CAIDA has been doing much larger point-to-multipoint measurements at low frequency for mapping /

Matt Zekauskas11 AMP Round-trip delay, loss Traceroute Many of you have AMP machines installed Currently the project is not emphasizing expansion However, still willing to add machines (you supply); there is also code available you could install yourself for points of interest

Matt Zekauskas12 AMP Example: new link In January, a TIEN2 link came up between AARnet and the APAN Tokyo XP.

Matt Zekauskas13

Matt Zekauskas14

Matt Zekauskas15 Week of 15-January-2006

Matt Zekauskas16

Matt Zekauskas17

Matt Zekauskas18 AMP Example: large route change Amp-korea to amp-hutfi (Taejon, KR/NOC to Helsinki, FI/Univ.) 16-April-2006 through 22-April-2006

Matt Zekauskas19

Matt Zekauskas20

Matt Zekauskas21

Matt Zekauskas22 AMP status Currently the main project is not focusing on deployment. If you supply a machine, they are willing to add it to one of the main meshes (general, international-only). Contact Tony McGregor,

Matt Zekauskas23 AMP Software You can also install your own mesh: The central collection software has not yet been released, but will be “soon” (will give out on request now) Tony also has some “gross change” detection code that he said may be available end-year.

Matt Zekauskas24 PingER (& IEPM-BW) Point-to-multipoint round-trip delay, loss But no traceroutes, for that IEPM-BW From beacons at major high-energy physics sites, to many other high-energy physics sites Including many that were originally not on “research networks”

Matt Zekauskas25 IEPM-BW A mesh of throughput tests for high-energy physics (think upcoming LHC experiments) One-to-many focus CERN, Brookhaven, Fermilab, SLAC, Caltech, and a site in Pakistan. In addition, takes traceroutes among the probe sites bw.slac.stanford.edu/slac_wan_bw_tests.html

Matt Zekauskas26 IEPM-BW Example

Matt Zekauskas27 On-Demand Tools Two tools are useful to understand routing right now Traceroute servers Routing from a given point, as detected by traceroute Looking glass servers Show a particular routing table entry right now Actual, versus inferred, network connectivity But only shows next hop

Matt Zekauskas28 Traceroute Servers Servers that provide on-demand traceroutes from specific points. Many networks have at least one Abilene allows traceroute from our routers via the IU ‘router proxy’

Matt Zekauskas29 Traceroute Servers List of HEP servers, pointer to decent server source code, and pointers to lots of other lists of servers: mon/traceroute-srv.html Lots of other servers: Presented graphically: ace/ The last two have both traceroute and looking glass lists.

Matt Zekauskas30 Traceroute Servers Very useful – install one of these and publish it’s location on your NOC page Unless, you install a looking glass server that also has traceroute functionality…

Matt Zekauskas31 Looking Glass Servers Similar, for routes at a particular point has a list and pointers to other lists & source code Often (always?) contains traceroute server functionality Again, the Abilene router proxy can be used in the same way Recommend installing one of these (as well), and publish its location

Matt Zekauskas32 Some Commercial Tools Mainly to help you understand your own network, don’t give a global view Packet Design’s RouteExplorer oducts.htm IPsum Networks’ Route Dynamics

Matt Zekauskas33 Communicate If you discover something odd, you would like to be able to understand and resolve the problem (if one exists) Place tools to help others Utility grows with the number of installations Publish tool links on your NOC pages If you see a problem, contact appropriate NOC Jim Williams, is interested in facilitating NOC-to-NOC communication

Matt Zekauskas34