• Like
20030515-E2Epi-UCL.ppt
Upcoming SlideShare
Loading in...5
×
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
198
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This is a general overview presentation about Internet2. Internet2 is a consortium, led by US universities, which is recreating the partnership among academia, industry and government that fostered today’s Internet in its infancy.
  • BOF, feel free to ask questions, make comments.
  • Introduced at Spring Member Meeting. Have made good progress on architectural design. Have made good progress on outreach to other organizations and initiating collaboration.
  • Campus PAS is a specified PC based computer ($2000 estimated) with a software load provided by Internet2
  • 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.
  • 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.
  • 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.
  • E2Epi need input on how to make this work. There are operational and policy issues here.
  • * These are the values we are currently we are planning on using, but this is not set in stone.
  • For more information about Internet2, please see these web sites, or contact info@internet2.edu directly by email.

Transcript

  • 1. E2E piPEs / AMI / OWAMP Status Eric Boyd and Matt Zekauskas May 15, 2003
  • 2. Agenda
    • Motivation
    • piPEs / AMI Overview
    • piPEs / AMI Deployment Plan
    • OWAMP Release
    • Demo
  • 3. Context for E2E Performance
    • Even with high bandwidth network links, the Internet2 community often does not see expected performance.
  • 4. The Wizard Gap
  • 5. A Problem Applications Developer Applications Developer How do you solve a problem along a path? Hey, this is not working right! The computer Is working OK The network is lightly loaded All the lights are green We don’t see anything wrong Looks fine Others are getting in ok Not our problem System Administrator LAN Administrator Campus Networking Gigapop Gigapop Backbone Campus Networking LAN Administrator System Administrator Talk to the other guys Everything is AOK No other complaints
  • 6. Good Work Already Going On
    • Many projects and research is underway by others investigating performance on portions of the end-to-end path.
    • E2Epi seeks to bring these efforts together to look at the end-to-end path as a complete system.
  • 7. Can You Go Direct to the Problem?
    • How can you tell where is the problem?
    • Need a tool to tell you:
      • Where the problem is.
      • The type of problem
      • Who to contact to get it fixed
    • Terry Gray, University of Washington
      • “ We Need a Finger Pointing Tool”
  • 8. Gray Finger Pointing Tool Applications Developer Applications Developer Locate the Problem Gray Finger Pointing Tool Terry Gray University of Washington Finger Pointing Tool Time! System Administrator LAN Administrator Campus Networking Gigapop Gigapop Backbone Campus Networking LAN Administrator System Administrator
  • 9. Gray Finger Pointing Tool Applications Developer Applications Developer Finger Pointing Tool Time You ARE the Weakest Link! OK, I’ll fix it System Administrator LAN Administrator Campus Networking Gigapop Gigapop Backbone Campus Networking LAN Administrator System Administrator
  • 10. Agenda
    • Motivation
    • piPEs / AMI Overview
    • piPEs / AMI Deployment Plan
    • OWAMP Release
    • Demo
  • 11. BNI AMI
    • Project: BNI Abilene Measurement Infrastructure
    • Goal: Instrument Next Generation Abilene network with extensive performance measurement capabilities
    • Approach: Collaborative project among BNI, Engineering, and E2E.
  • 12. E2E piPES
    • 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.
  • 13. The Measurement System PMP PMP PMP PMP at each Campus Border Extend the System to Campuses Abilene PMP Campus X PMP Campus Y
  • 14. The Measurement System PMP PMP PMP PMP = Performance Measurement Point (at each Abilene Node) The New Abilene will have measurement devices as part of its structure Abilene
  • 15. Performance Reporting PMP PMP PMP Perform regular tests to provide web based Performance Reports across Abilene and for Campus-Abilene paths Abilene PMP Campus X PMP Campus Y Campus-Abilene Capability Campus W – 155 Mbps Campus X – 612 Mbps Campus Y – 1000 Mbps Campus Z – 2 Mbps Abilene Capability SNVA/DNVR – 10 Gbps DNVR/ IPLS – 10 Gbps IPLS/NYCM – 10 Gbps
  • 16. Reaching the End-User PMP PMP PMP Provide a Testing Tool for the End-Users Computer to test across campus and beyond Abilene PMP Campus X PMP Campus Y Host A Host B 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. It also performs tests on the host system to check host tuning parameters
  • 17. Adding Path Information PMP PMP PMP Add PMP along paths to provide additional detail Abilene PMP Campus X PMP Campus Y Host A Host B 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. PMP PMP Regional Network J PMP PMP Regional Network M Gigapop S Gigapop T
  • 18. Who You Gonna Call? PMP PMP PMP E2E piPES will provide contact information when a segment in the path appears to have a problem Abilene PMP Campus X PMP Campus Y Host A Host B The test results obtained by the End-User will be passed on to the contact person PMP PMP Regional Network J PMP PMP Regional Network M Gigapop S Gigapop T piPES Test Analysis Looks like a problem In Gigapop T. Pass these test result to: [email_address]
  • 19. E2E piPES Architecture
  • 20. Testing / Analysis Engine
    • Problem: Encode Matt Z.’s Brain
    • Open Questions:
    • What are measurement results are “acceptable” for a given application (family)?
    • What tools generate those results?
    • How do you handle incomplete data?
    • How do you rank multiple result-generators?
    • What is the iterative decision tree to understand E2E problem?
  • 21. Measurement Schema
    • Measurement Types?
    • e.g. BW, Latency, Loss, Jitter
    • Measurement Units?
    • e.g. Seconds vs. Microseconds
    • Map Tools to Measurements?
    • e.g. OWAMP -> 1-way Latency
    • Measurement Metadata?
    • Database Table Design?
  • 22. Access, Authentication, Authorization
    • Roles for Access
      • Standard End-User?
      • Near Neighbor (Test Buddy)?
      • NOC Staff / Network Engineer?
    • Shibboleth for Implementation
      • Each campus decides who in each role
      • Others trust campus designation
  • 23. Other R&D Issues
    • Design system to scale (eliminate centralization)?
    • How to “discover” PMPs?
    • How to insert On-Demand tests into Regularly-Scheduled test set
    • Balance centralization and distributed database requirements
  • 24. Agenda
    • Motivation
    • piPEs / AMI Overview
    • piPEs / AMI Deployment Plan
    • OWAMP Release
    • Demo
  • 25. E2E piPES Architecture v1.0
  • 26. piPEs / AMI Rollout
  • 27. piPEs / AMI Rollout
  • 28. piPEs / AMI Rollout
  • 29. piPEs / AMI Rollout
  • 30. piPEs / AMI Rollout
  • 31. piPEs / AMI Development & Testing Environment
  • 32. piPEs / AMI Internal Resources
    • Eric Boyd – piPEs development, project coordination
    • Jeff Boote – OWAMP, piPEs development
    • Prasad Calyam – piPEs development
    • Chris Heermann – AMI
    • Matt Zekauskas - AMI
    • Susan Evett - Documentation
    • Russ Hobby – Campus Deployment
    • George Brett – Schema, “Grid Service”
  • 33. Agenda
    • Motivation
    • piPEs / AMI Overview
    • piPEs / AMI Deployment Plan
    • OWAMP Release
    • Demo
  • 34. Latency Tests
    • Problem: Existing platforms are not interoperable (SURVEYOR,RIPE,…)
    • Solution: Standards
  • 35. OWAMP
    • One-Way-Active-Measurement-Protocol
      • Possible due to growing availability of good time sources
      • Wide deployment of “open” servers would allow measurement of one-way delay to become as commonplace as measurement of RTT using ICMP tools such as ping.
      • Current Draft: draft- ietf - ippm - owdp -05.txt
        • Shalunov,Teitelbaum,Zekauskas
      • Sample implementation under development
        • Beta Release: http://owamp.internet2.edu/
  • 36. OWAMP Implementation
    • Basically:
      • NTP system call interface
      • Multiple processes for recv/send loops
      • Written as an API to allow one-off implementations
  • 37. OWAMP implementation status
    • Sample implementation
    • http:// owamp .internet2. edu /
      • Beta Release:
        • No “policy”
        • No authentication/encryption
        • FreeBSD only
  • 38. Abilene OWAMP deployment
    • 2 overlapping full meshes (IPv4 & IPv6)
      • 11 measurement nodes = 220 ongoing tests
      • UDP singletons
      • Rate: 10 packets/second*
      • Packetsize: (32 byte payload)*
      • Results are continuously streamed back to “Measurement Portal” for long-term archive and data dissemination (Near real-time)
  • 39. Agenda
    • Motivation
    • piPEs / AMI Overview
    • piPEs / AMI Deployment Plan
    • OWAMP Release
    • Demo
  • 40. More Internet2 Information
    • On the Web
      • www.internet2.edu
      • e2epi.internet2.edu
    • Email
      • [email_address]
  • 41. Questions?
  • 42. www.internet2.edu