Internet2 E2E piPEs Project Eric L. Boyd 27 April 2019

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 4/27/2019

Measurement Infrastructure Components For any given “partial path” segment (dotted black line) … We might run regularly scheduled tests and/or on-demand tests. This means, we require the ability to make a test request, have test results stored in a database, request those test resutls, and retrieve the test results. 4/27/2019

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) 4/27/2019

piPEs Deployment 4/27/2019

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 4/27/2019

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 The E2E team is building the piPEs measurement framework. Internet2 has deployed an instance of that framework, the Abilene Measurement Domain (AMD). AMD is part of the Abilene Observatory. Currently, the AMD consists of regularly scheduled OWAMP and BWCTL tests, plus the ability of a user “on the edge” to test “to the middle” (a crude divide-and-conquer approach to diagnosis E2E problems). Network Monitoring is live (a prototype that will eventually be released) that allows simple analysis of network monitoring data across the backbone. In addition, we’ve made that data available via a web service (conforming to the schemata of the GGF NMWG). Other tools, such as NLANR’s Advisor and the HENP community’s MonALISA tool can now consume that data. 4/27/2019

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 4/27/2019

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 4/27/2019

A Long Walk Down a Short Plank 4/27/2019

End-to-End Path 4/27/2019

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 4/27/2019

Quality Control of the Network Backbone 4/27/2019

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 4/27/2019

Quality Control of Network Backbone Suggestion #3: Quality Control of ESnet using OWAMP (and BWCTL?) 4/27/2019

Quality Control of Peering Connections Suggestion #4: Quality Control of Abilene / ESnet Peering 4/27/2019

Whole Kit-and-Caboodle Suggestion #5: BWCTL on ESnet Backbone Suggestion #6: Quality Control along Entire E2E Path 4/27/2019

3+3: Labs plus ITECs 1+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). 4/27/2019

4/27/2019