1 / 24

Transatlantic Performance Monitoring Workshop 2004

Transatlantic Performance Monitoring Workshop 2004. Eric L. Boyd (& Nicolas Simar). March 17, 2004 CERN, Switzerland Hosted by: Internet2 E2Epi DANTE / GEANT2 EGEE Overview: E2E piPEs GEANT2 JRA1 Demo GGF NMWG Perf. Meas. Arch. WS. Tools OWAMP BWCTL IPPM SCAMPI CNM Consumers

jbyfield
Download Presentation

Transatlantic Performance Monitoring Workshop 2004

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. Transatlantic Performance Monitoring Workshop 2004 Eric L. Boyd (& Nicolas Simar)

  2. March 17, 2004 CERN, Switzerland Hosted by: Internet2 E2Epi DANTE / GEANT2 EGEE Overview: E2E piPEs GEANT2 JRA1 Demo GGF NMWG Perf. Meas. Arch. WS Tools OWAMP BWCTL IPPM SCAMPI CNM Consumers Advisor MonALISA EGEE Group Discussion Transatlantic Performance Monitoring Workshop 2004

  3. 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. Measurement Infrastructure Components

  5. Sample piPEs Deployment

  6. Europe Hawaii OSU NC State UCSD 1) Abilene Backbone Deployment (Complete) 2) Hawaii Campus Deployment (Complete) 3) In Progress Campus and European Deployment (Q1 2004) piPEs Deployment

  7. Abilene Measurement Domain • Part of the Abilene Observatory: http://abilene.internet2.edu/observatory • Regularly scheduled OWAMP (1-way latency) and BWCTL (Iperf wrapper) 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. GN2 JRA1 - Performance Monitoring and Management • 3 year project, starting in September 2004 (15 European NRENs and DANTE involved). • Development of a Performance Monitoring infrastructure operating across multiple domains • User can access data from different domains in a uniform way and start on-demand tests.

  9. GN2 JRA1 Goals • Make network management and performance information from different domains available to various authorised user communities • GÉANT, NRENs, Regional networks NOCs • PERT - Performance Enhancement Response Team • high data volume transfer users (as GRID) • end-user who would like to see or understand the E2E behaviour of R&D networks.

  10. GN2 JRA1 Goals • Multi-domain focus, interoperable with other frameworks. • Tailor data representation for a subset of users. • Modify existing tools and integrate them within the infrastructure.

  11. GN2 Framework Layers

  12. GN2 JRA1 MeasurementPoints and Metrics • Activity will focus in five areas: • One-way delay, IPDV and traceroute • Available Bandwidth (IP for sure, TCP/UDP less sure) • Flow Based Traffic Measurement • Passive Monitoring • Network Equipment information • Quite IP-centric.

  13. GN2 JRA1 Starting Point • Starts from GN1 Performance Monitoring framework (data retrieval, storage and export using a well define interface) and take into account other experiences. • Uses NRENs experience in tool development. • Need to take into account the variety of tools and metric existing across the NRENs

  14. American/European Collaboration Goals • Awareness of ongoing Measurement Framework Efforts / Sharing of Ideas (Good / Not Sufficient) • Interoperable Measurement Frameworks (Minimum) • Common means of data extraction • Partial path analysis possible along transatlantic paths • Open Source Shared Development (Possibility, In Whole or In Part) • End-to-end partial path analysis for transatlantic research communities • VLBI: Onsala, Sweden  Haystack, Mass. • HENP: CERN, Switzerland  Caltech, Calif.

  15. American/European Demonstration Goals • Demonstrate ability to do partial path analysis between “Caltech” (Los Angeles Abilene router) and CERN. • Demonstrate ability to do partial path analysis involving nodes in the GEANT network. • Compare and contrast measurement of a “lightpath” versus a normal IP path. • Demonstrate interoperability of piPEs and analysis tools such as Advisor and MonALISA

  16. Demonstration Details • Path 1: Default route between LA and CERN is across Abilene to Chicago, then across Datatag circuit to CERN • Path 2: Announced addresses so that route between LA and CERN traverses GEANT via London node • Path 3: “Lightpath” (discussed earlier by Rick Summerhill) • Each measurement “node” consists of a BWCTL box and an OWAMP box “next to” the router.

  17. All Roads Lead to Geneva

  18. Results • BWCTL: http://abilene.internet2.edu/ami/bwctl_status_eu.cgi/BW/14123130651515289600_14124243902743445504 • OWAMP: http://abilene.internet2.edu/ami/owamp_status_eu.cgi/14123130651515289600_14124243902743445504 • MONALISA • NLANR Advisor

  19. Insights (1) • Even with shared source and a single team of developer-installers, inter-administrative domain coordination is difficult. • Struggled with basics of multiple paths. • IP addresses, host configuration, software (support source addresses, etc.) • Struggled with cross-domain administrative coordination issues. • AA (accounts), routes, port filters, MTUs, etc. • Struggled with performance tuning measurement nodes. • host tuning, asymmetric routing, MTUs

  20. Insights (2) • Connectivity takes a large amount of coordination and effort; performance takes even more of the same. • Current measurement approaches have limited visibility into “lightpaths.” • Having hosts participate in the measurement is one possible solution.

  21. Insights (3) • Consider interaction with security; lack of end-to-end transparency is problematic. • Security filters are set up based on expected traffic patterns • Measurement nodes create new traffic • Lightpaths bypass expected ingress points

  22. Status Update • We can do partial path analysis, although making sense of the results is still a big issue. • We can speak the same measurement language, although it’s still evolving. • We are working together in growing numbers, but we need critical mass (become de facto standard). • We need to be able to find each other. • We need to be able to verify each other’s identity.

  23. Summary • Presentations found here: • http://people.internet2.edu/~eboyd/program.html • You are welcome to join mailing list • Sub-groups beginning work on areas of common interest • American / European collaboration proceeding full steam ahead

More Related