1 / 19

Internet2 End-to-End Performance Measurement Infrastructure (piPEs)

The piPEs project aims to enable end-users and operators to determine performance capabilities, locate problems, and resolve them efficiently. With various tools and phases, the project facilitates remote performance tests and data sharing while ensuring interoperability with other frameworks.

memert
Download Presentation

Internet2 End-to-End Performance Measurement Infrastructure (piPEs)

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. Internet2 E2E piPEs Project Eric L. Boyd

  2. Internet2 E2E piPEs Goals • Enable end-users & network operators to: • determine E2E performance capabilities • locate E2E problems • contact the right person to get an E2E problem resolved. • Enable remote initiation of partial path performance tests • Make partial path performance data publicly available • Interoperable with other performance measurement frameworks

  3. Measurement Infrastructure Components

  4. Project Phases • Phase 1: Tool Beacons • BWCTL (Complete), http://e2epi.internet2.edu/bwctl • OWAMP (Complete), http://e2epi.internet2.edu/owamp • NDT (Complete), http://e2epi.internet2.edu/ndt • Phase 2: Measurement Domain Support • General Measurement Infrastructure (Prototype) • Abilene Measurement Infrastructure Deployment (Complete), http://abilene.internet2.edu/observatory • Phase 3: Federation Support • AA (Prototype – optional AES key, policy file, limits file) • Discovery (Measurement Nodes, Databases) (Prototype – nearest NDT server, web page) • Test Request/Response Schema Support (Prototype – GGF NMWG Schema)

  5. piPEs Deployment

  6. Example piPEs Use Cases • Edge-to-Middle (On-Demand) • Automatic 2-Ended Test Set-up • Middle-to-Middle (Regularly Scheduled) • Raw Data feeds for 3rd-Party Analysis Tools • http://vinci.cacr.caltech.edu:8080/ • Quality Control of Network Infrastructure • Edge-to-Edge (Regularly Scheduled) • Quality Control of Application Communities • Edge-to-Campus DMZ (On-Demand) • Coupled with Regularly Scheduled Middle-to-Middle • End User determines who to contact about performance problem, armed with proof

  7. Abilene Measurement Domain • Part of the Abilene Observatory: http://abilene.internet2.edu/observatory • Regularly scheduled OWAMP (1-way latency) and BWCTL/Iperf (Throughput, Loss, Jitter) Tests • Web pages displaying: • Latest results http://abilene.internet2.edu/ami/bwctl_status.cgi/TCP/now “Weathermap” http://abilene.internet2.edu/ami/bwctl_status_map.cgi/TCP/now • Worst 10 Performing Links http://abilene.internet2.edu/ami/bwctl_worst_case.cgi/TCP/now • Data available via web service: http://abilene.internet2.edu/ami/webservices.html

  8. 3+3: Labs and ITECs • April, 2004: Demonstrated “working together” … OWAMP tests between LBL and NC State • July, 2004: Regularly scheduled OWAMP tests between LBL, Fermi, Brookhaven and ITECs (NC State, OSU, and SDSC) • Joe Metzger presented results • http://events.internet2.edu/2004/JointTechs/Columbus/sessionDetails.cfm?session=1510&event=218

  9. How Can You Participate? • Set up BWCTL, OWAMP, NDT Beacons • Set up a measurement domain • Place tool beacons “intelligently” • Determine locations • Determine policy • Determine limits • “Register” beacons • Install piPEs software • Run regularly scheduled tests • Store performance data • Make performance data available via web service • Make visualization CGIs available • Solve Problems / Alert us to Case Studies

  10. A Long Walk Down a Short Plank

  11. End-to-End Path

  12. Solving the First Mile Suggestion #1: Individual labs set up NDT servers “next to” gateway router. Suggestion #2: ESCC set up federation of NDT servers http://e2epi.internet2.edu/ndt

  13. Quality Control of the Network Backbone

  14. Quality Control of the Network Backbone Regularly Scheduled Tests: http://abilene.internet2.edu/observatory Web Service Access: http://abilene.internet2.edu/ami/webservices.html Analysis Tools (e.g MonALISA, NLANR / DAST Advisor

  15. Quality Control of Network Backbone Suggestion #3: Quality Control of ESnet using OWAMP (and BWCTL?)

  16. Quality Control of Peering Connections Suggestion #4: Quality Control of Abilene / ESnet Peering

  17. Whole Kit-and-Caboodle Suggestion #5: BWCTL on ESnet Backbone Suggestion #6: Quality Control along Entire E2E Path

  18. 3+3: Labs plus ITECs1+1: Abilene plus ESnet • Agreed to 3-6 month goal (by Supercomputing 2004) • Create an IPv4 OWAMP quality control infrastructure across ESnet / Abilene connections (and including SCInet, while it's up) using piPEs alpha (v0.1) and OWAMP. • ESnet, with support from Internet2, will evaluate piPEs infrastructure through above deployment. • ESnet, with support from Internet2, will evaluate and set up at least 1 BWCTL and 1 NDT for evaluation. • ITECs and ESnet may create OWAMP "directory pages,” part of the Global PMP Directory (http://e2epi.internet2.edu/pipes/pmp/pmp-dir.html).

More Related