1. E2E piPES Project Russ Hobby, Internet2 HENP Working Group Meeting
Fall 2002 Internet2 Member Meeting
27 October, 2002

2. E2E piPES Overview
Project: End-to-End Performance Initiative Performance Environment System (E2E piPES)
Goal: To allow end-users and network operators to determine performance capabilities, locate problems, and contact the right person to get a problem resolved.
Approach: Collaborative project combining the best work of many organizations.
Introduced at Spring Member Meeting.
Have made good progress on architectural design.
Have made good progress on outreach to other organizations and initiating collaboration.
12/8/2018

3. The Measurement System
The New Abilene will have measurement devices as part of its structure
Abilene
PMP
PMP
PMP
PMP = Performance Measurement Point (at each Abilene Node)
12/8/2018

4. The Measurement System
Extend the System to Campuses
Campus X
Abilene
PMP
PMP
PMP
Campus PAS is a specified PC based computer ($2000 estimated) with a software load provided by Internet2
Campus Y
PMP
PMP
PMP at each Campus Border
12/8/2018

5. Performance Reporting
Perform regular tests to provide web based Performance
Reports across Abilene and for Campus-Abilene paths
Campus X
Abilene Capability
SNVA/DNVR – 10 Gbps
DNVR/IPLS – 10 Gbps
IPLS/NYCM – 10 Gbps
Abilene
PMP
PMP
PMP
At first test results will be reported on web pages. An end-user suspecting performance problems can check the reported performance from their campus to Abilene, across Abilene, and from Abilene to the destination campus. If there are no reported problems on any of these segments, the the end-user can suspect the campus networks on the ends, or the computer systems themselves.
Campus Y
Campus-Abilene Capability
Campus W – 155 Mbps
Campus X – 612 Mbps
Campus Y – 1000 Mbps
Campus Z – 2 Mbps
PMP
PMP
12/8/2018

6. Reaching the End-User
Provide a Testing Tool for the End-Users Computer
to test across campus and beyond
Campus X
Abilene
PMP
PMP
PMP
Host A
Host B
The tool will use test results stored in a data repository as much as possible to reduce the overall amount of active testing going on. The tools will probably be a JAVA Applet to make
it as portable as possible.
Campus Y
PMP
PMP
The tool reports performance of the path to a specified destination by using active tests
(like to the campus border) or using stored test results from regularly scheduled tests
12/8/2018

7. Adding Path Information
Add PMP along paths to provide additional detail
Campus X
Abilene
PMP
Gigapop S
Regional
Network M
PMP
PMP
PMP
Host A
PMP
Host B
PMP
E2Epi is looking for the Quilt to lead in the deployment at the Gigapops and Regional Networks. Ideally the system would have measurement information for each administrative domain along each path. For larger networks, multiple Path Measurement Points may be desireable.
Campus Y
PMP
PMP
PMP
Regional
Network J
Gigapop T
Regular tests are performed between adjacent PMP and stored in a Data Repository.
This information is used by the End-User tool to reduce the number or active tests needed.
12/8/2018

8. segment in the path appears to have a problem
Who You Gonna Call?
E2E piPES will provide contact information when a
segment in the path appears to have a problem
Campus X
Abilene
PMP
Gigapop S
Regional
Network M
PMP
PMP
PMP
Host A
PMP
Host B
PMP
E2Epi need input on how to make this work. There are operational and policy issues here.
piPES Test Analysis
Looks like a problem
In Gigapop T. Pass
these test result to:
Campus Y
PMP
PMP
PMP
Regional
Network J
Gigapop T
The test results obtained by the End-User will be passed on to the contact person
12/8/2018

9. Who is doing the work? A collaborative venture:
E2Epi will build on many of the measurement and data tools already developed by our community.
Several organizations have joined in this projects to provide parts of the architecture.
A white paper on the architecture is available:
If you would like to join in the project or want to discuss details, contact:
Eric Boyd
12/8/2018

10. Deployed E2E piPE
12/8/2018

11. E2E piPES Architecture
12/8/2018

12. Status of Project Modules
E2E Interface
Network Admin Interface
Testing Engine
Scheduler
PMP
Performance Database
Culprit Database
Culprit Interface
Authentication and Authorization
DAST - NLANR
High Level Overview
Design Doc Complete
Looking at SLAC code
Looking at UIC code
Looking at Shibboleth
12/8/2018

13. Status of Related Projects
Analysis Engine
- Application Family Characteristics (Merit, E2Epi, Measurement WG)
Database Schema
- Untouched
Operational Support
12/8/2018

14. Prototype E2E GUI DAST/NLANR Project
12/8/2018

15. Testing Engine
12/8/2018

16. Testing Engine Application Table
12/8/2018

17. Testing Engine: Decision Module
12/8/2018

18. Testing Engine Verification Sub-Module
12/8/2018

19. Testing Engine Link Sub-Module
1) UDP Traffic (one-way)
Problem: Throughput
Metric: Bandwidth, loss rate (OWPL)
Problem: Real time problem with acceptable throughput
Metric: Delay, delay jitter (one-way)
2) TCP Traffic
Metric: BW, RTT, OW loss rate, Window Size, Time-Out
12/8/2018

20. Scheduler Architecture (1)
12/8/2018

21. Scheduler Architecture (2)
12/8/2018

22. Scheduler Algorithm
12/8/2018

23. Scheduler Algorithm Example
12/8/2018