Measurements in Support of End-to-End Performance

1. Measurements in Support of End-to-End Performance Matt Zekauskas, matt@internet2.edu Campus Workshop San Diego, CA

2. Outline • What’s needed • Monitoring • Diagnostics • General plans • What is available today • What you can do today • [Spirent: one commercial platform]

3. My Bias • I once ran a (corporate) campus network • My recent focus: measurements • I have been helping solve some wide-area performance problems • Caveat: I haven’t been doing the fixing (My view is from the center)

4. We Need Your Help • I have probably missed something • Give us the benefit of your experience fixing problems

5. Vision I • Ongoing monitoring to test major elements, and (some, important) end-to-end paths. • Elements: gigaPoP links, peering, … • Utilization • Delay • Loss • Occasional throughput • Multicast connectivity

6. Vision II • There are many more paths end to end than can be monitored. • Diagnostic tools available on-demand (with authorization) • Show routes • Perform flow tests (perhaps app tests) • Parse/debug flows (a-la tcpdump or OCXmon with heuristic tools)

7. Problem Isolation via Divide and Conquer

8. Duke - Frankfurt Goal: 7 Mbps bi-directional UDP Duke Frankfurt Teleglobe ATM DFN NCREN Abilene 25 Broadway Dante WASH NYCM 60 Hudson = Surveyor node

9. The Duke-Frankfurt Problem Abilene to Dante Link Utilization http://monon.uits.iupui.edu/abilene/nycm/dante-bits.html

10. JPL/Caltech – GSFC • The situation • Using Abilene • Tuned hosts • Things work locally • Therefore it MUST be Abilene • Tests show good flows router-router • Intermediate tests point towards CA • Bad fiber connection!

11. In Process: Abilene • Abilene will be an exemplar • All measurements open • Tests possible to router nodes • Web-mediated on-demand measurements • Throughput tests routinely through backbone • …as well as existing utilization, etc.

12. Eventually • Tests available in automated fashion • Utilize existing measurement infrastructures • Spread to other backbones • Spread to gigaPoPs • Spread to campus edges • …available throughout Internet2 infrastructure • Portable monitoring toolkit

13. What Is Available Today • Measurement Infrastructures • Non-commercial tools • Commercial tools • Intermediate (within Abilene) throughput tests • Ad-hoc, contact matt@internet2.edu

14. What is Available: Infrastructure • Surveyor (one-way delay, loss, routing) • www.advanced.org/surveyor • On many Internet2 campuses (70 sites) • Abilene presence • AMP (round-trip delay, loss, routing) • moat.nlanr.net/AMP (and /PMA) • At even more Internet2 campuses (120 sites) • PingER • http://www-iepm.slac.stanford.edu/pinger/ • High-energy physics focus

15. Non-commercial Tools • (beside netperf/iperf/ttcp/mrtg/rrdtool/…) • Abilene NOC tools • www.abilene.iu.edu, operational • Pioneer • http://pelle.internet2.edu:8080/pioneer/ • Synthesis of existing infrastructure • Focus: video conferencing tests

16. What Is Available: Commercial • Caveat: only a partial list, give me more! • Spirent (Netcom/Adtech): building box for this purpose. See next talk! • NetIQ (Chariot/Pegasus) • Ixia (like SmartBits/Netcom) • Brix Networks (like Surveyor, for ‘QoS’)

17. What Can You Do • Export SNMP data • I can keep an “internet2 list”, would like it to be public • Performance test point at campus edge • Netperf or iperf, so can be from anywhere • Traceroute “looking glass” • Commercial (e.g., NetIQ) complements • I’m willing to keep a master list • Portable performance test point

18. Contact Information • Matt Zekauskas, matt@internet2.edu • Measurements Working Group undergoing recharter • http://www.internet2.edu/measurement/ • End-to-end interest list • listserv@internet2.edu • subscribe e2e-interest

19. www.internet2.edu