End-to-End Performance Initiative

1. End-to-End Performance Initiative Network Measurement Matt Zekauskas, matt@internet2.edu Fall 2001 Internet2 Member Meeting

2. The Network View • “Wall jack to wall jack” • Long term: plug in and network works • Short term: • Measurement infrastructure • Analysis tools • Best Current Practice documents Enable segmental end-to-end measurement, monitoring, analysis E2Epi: Network Measurement

3. Campus Backbone 1 Backbone 2 Campus GigaPoP A GigaPoP B The Network View Wall Jack P P Wall Jack E2Epi: Network Measurement

4. Measurement Architecture • Permanently installed machines • Standard measurements on pre-determined basis • Active measurements • Diagnostic tools (in conjunction with (application) reflectors/reference servers) • Passive measurements • Portable machines E2Epi: Network Measurement

5. Reference Servers • H.323 conferencing • Goal: portable machines that tell you if system likely to work (and if not, why?) • Moderate-rate UDP of interest • E.g., ViDeNet Scout, http://scout.video.unc.edu/ • (TCP) Performance debugging • Conjecture: 80% of problems related to • Host tuning (mostly buffers) • Duplex mismatch [path] • Other physical connection problem [path] • “Hard” data from Claudia DeLuna, JPL; also hearsay E2Epi: Network Measurement

6. TCP Performance Tester • Connect from suspect host via Web • Example: http://www.dslreports.com/tweaks • Host tuning • See Web100 talk • Duplex Mismatch / Bad Physical Conn • Low to moderate UDP tests, view loss • Step functions: duplex • Constant rate loss: bad physical • Collocated traceroute server E2Epi: Network Measurement

7. Packet Reflector • Idea by Matt Mathis (good stuff his, bad mine) • Test application with both ends in your lab, but packets get full “Internet experience” (delay, loss, jitter) • Example: app machine is pointed at a router that tunnels packets to remote location, then routed normally back to other app machine • Benefit: not application or transport dependent E2Epi: Network Measurement

8. Measurement Architecture • Uniform access to schedule tests, retrieve results • Results in uniform format • Security (DoS potential) and Privacy considered • Synchronization/Scheduling so tests don’t interfere with themselves or environment E2Epi: Network Measurement

9. Implementation Considerations • Define standard tests • Not tied to one platform • Capitalize on existing metrics, tools, infrastructure • Consider commercial products, how to influence vendors (longer-term) • Rigorously document E2Epi: Network Measurement

10. One Commercial Partnership • Spirent Communications, an Internet2 corporate partner, is interested in this problem. • Working with End-to-End Performance Initiative staff, ITECs, on developing machine for end-to-end measurement point. E2Epi: Network Measurement

11. Initial Measurement Support Matt Zekauskas,* Internet2 Ronn Ritke,* NLANR/MOAT Tony McGregor, U Waikato & MOAT * we were both on the design team…

12. “Phase 0” Measurement • Placing equipment is hard and time consuming • Active measurement targets most useful to start • Two infrastructures deployed in community: • AMP and Surveyor • Can we leverage them? • NOTE: This is NOT meant to be exclusive! E2Epi: Network Measurement

13. Phase 0 Measurement Goals • Leverage existing measurement infrastructures • Get something up quickly over perfection • Learn what’s missing • Feedback to improve infrastructure E2Epi: Network Measurement

14. AMP and Surveyor • We have access to these infrastructures • Both are currently designed to continuously take low-bandwidth measurements • Coverage overlaps somewhat; AMP is more widely deployed (no GPS requirement) • Placement goals different and complementary • AMP: on typical university LAN • Surveyor: at campus edge + Abilene backbone E2Epi: Network Measurement

15. Hurdles (Challenges?) • Both placed with low-bandwidth in mind • But we desire throughput tests, too • Additional tests may interfere with existing tests • Scheduling important • Secure access desirable • Can’t be denial-of-service platforms • Some machines may not be available E2Epi: Network Measurement

16. Initial Steps • Abilene Surveyors will be throughput targets • Work on PKI authentication mechanism • Work on Scheduling • Both platforms deploy traceroute observatories • Common listing of both sites • AMP allows occasional throughput by local campus personnel only – looking to develop common mechanism with Surveyor • Looking to future tests being common E2Epi: Network Measurement

17. What do you need? • Comments? Questions? Desires? • (Feel free to send questions/comments/desires to matt@internet2.edu and rdhobby@internet2.edu ) E2Epi: Network Measurement

18. www.internet2.edu