1 / 25

E2E piPES Project

Explore E2E.piPES creating a performance system for end-users and network operators to identify and resolve issues efficiently. Discover how the measurement system works and provides enhanced reporting capabilities. Learn about the collaborative project and how to get involved!

brownsharon
Download Presentation

E2E piPES Project

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. 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.

  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)

  4. The Measurement System Extend the System to Campuses Campus X Abilene PMP PMP PMP Campus Y PMP PMP PMP at each Campus Border

  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 Campus Y PMP Campus-Abilene Capability Campus W – 155 Mbps Campus X – 612 Mbps Campus Y – 1000 Mbps Campus Z – 2 Mbps PMP

  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 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

  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 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.

  8. 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 Campus Y piPES Test Analysis Looks like a problem In Gigapop T. Pass these test result to: Joe@gigapopT.net PMP PMP PMP Regional Network J GigapopT The test results obtained by the End-User will be passed on to the contact person

  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: http://e2epi.internet2.edu • If you would like to join in the project or want to discuss details, contact: • Eric Boyd <eboyd@internet2.edu>

  10. Deployed E2E piPE

  11. E2E piPES Architecture

  12. Status of Project Modules

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

  14. Prototype E2E GUIDAST/NLANR Project

  15. Testing Engine

  16. Testing Engine Application Table

  17. Testing Engine: Decision Module

  18. Testing EngineVerification Sub-Module

  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 • Problem: Throughput • Metric: BW, RTT, OW loss rate, Window Size, Time-Out

  20. Scheduler Architecture (1)

  21. Scheduler Architecture (2)

  22. Scheduler Algorithm

  23. Scheduler Algorithm Example

  24. www.internet2.edu

  25. www.internet2.edu

More Related