1 / 27

Network Measurements Session Introduction

Network Measurements Session Introduction. Joe Metzger Network Engineering Group ESnet Eric Boyd Deputy Technology Officer Internet2. July 16 2007 Joint Techs at FERMI. Why is Network Measurement Important?. Users dependence on the network is increasing Distributed Applications

allayna
Download Presentation

Network Measurements Session Introduction

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. Network Measurements Session Introduction Joe Metzger Network Engineering Group ESnet Eric Boyd Deputy Technology Officer Internet2 July 16 2007 Joint Techs at FERMI

  2. Why is Network Measurement Important? • Users dependence on the network is increasing • Distributed Applications • Moving Larger Data Sets • The network is becoming a critical part of large science experiments • The network is growing much more complex • ESnet had 6 core devices in 05’, 25+ in 08’ • ESnet had 6 core links in 05’, 40+ in 08’, 80+ by 2010? • Dynamic Circuits • Network Security Issues • The community needs to better understand the network • Users must know what performance levels to expect. • Network Operators need to be able to demonstrate that the network meets or exceeds those expectations. • Application Developers must understand the ‘wizards gap’ and have access to tools that differentiate between network problems and application problems.

  3. Data Transfer times over R&E Networks RED: Something is broken! Usually TCP tuning or HW problems within 100 feet of end points. GREEN: Supported by R&E Backbones today (may have local campus challenges) WHITE: Requires special engineering.

  4. TCP Throughput Limits

  5. TCP Throughput Limits Gbps on Campus with any window size Need 1 MB Windows to Get 100 Mbps Cross country Default OS Window sizes. Is this enough For you?

  6. Scale of the Integration Challenge • Measurement infrastructure needs to: • Obey agreed-upon protocols (schema and semantics) • Be interoperable across administrative boundaries • Integrate with middleware (federated trust) infrastructure • Integrate with circuit provisioning software

  7. Scale of the Deployment Challenge • Universities, national labs, regionals, and national backbones are all autonomous • Measurement infrastructure needs to: • Be deployed widely (Metcalf’s Law) • Be locally controlled • Work well with existing local infrastructure • Integrate easily into local processes

  8. Internet2 Connectors CalREN-2 South NYSERNet Great Plains Network 3ROX Indiana GigaPoP MAGPI MREN Internet2 NoX Merit ESnet Oregon GigaPoP OARnet LONI Pacific Northwest GigaPoP SoX OmniPoP 8

  9. ESnet Connects SLAC (T2) Brookhaven National Lab (T1) Fermi National Accelerator Lab (T1) Lawrence Livermore National Lab (T3) Argonne National Lab (T3) ESnet Lawrence Berkeley National Lab (T3) 9

  10. Nine Universities Connect through CalREN-2 South UC Santa Cruz (T3) UC Irvine (T3) UC Davis (T2) UCLA (T3) University of Arizona (T3) UC Riverside (T3) CENIC UC San Diego(T3) California Institute of Technology (T2) UC Santa Barbara (T3) 10

  11. Universities Connecting through Oregon GigaPoP and Pacific NW GigaPoP University of Oregon (T3) University of Washington (T3) Oregon GigaPOP Pacific Northwest GigaPOP 11

  12. Four Universities Connect through LONI University of Texas, Dallas (T3) University of Texas, Arlington (T2) Southern Methodist University (T3) LONI University of Mississippi (T3) 12

  13. Seven Universities Connect through Great Plains Network University of Nebraska-Lincoln (T2) Kansas State University (T3) University of Kansas (T3) University of Oklahoma (T2) Great Plains Network University of Iowa (T3) Oklahoma State University (T3) Iowa State University (T3) 13

  14. Two Universities Connect through OmniPoP University of Wisconsin, Milwaukee (T2) University of Wisconsin, Madison (T3) OmniPoP 14

  15. Five Universities Connect through MREN University of Illinois at Chicago (T3) University of Chicago (T2) University of Notre Dame (T3) MREN Univ of Illinois, Urbana-Champaign (T3) Northwestern University (T3) 15

  16. Universities that Connect through Indiana GigaPoP and OARnet Purdue University (T2) Ohio State University (T3) Indiana University (T2) Indiana GigaPoP OARnet 16

  17. Two Universities Connect through Merit University of Michigan (T2) Michigan State University (T2) Merit 17

  18. Eight Universities Connect through SoX University of Florida (T2) Duke University (T3) Vanderbilt University (T3) Florida International University (T3) University of Puerto Rico (T3) SoX Florida State University (T3) University of South Carolina (T3) University of Tennessee (T3) 18

  19. Two Universities Connect through 3ROX University of Pittsburgh (T3) Carnegie Mellon University (T3) 3ROX 19

  20. Three Universities Connect through MAGPI University of Pennsylvania (T3) Princeton University (T3) Rutgers University (T3) MAGPI 20

  21. Seven Universities Connect through NYSERNet New York University (T3) Columbia University (T3) University of Rochester (T3) SUNY Albany (T3) NYSERNet SUNY Stony Brook (T3) SUNY Buffalo (T3) Cornell University (T3) 21

  22. Nine Universities Connect through NoX Harvard University (T2) Boston University (T2 and T3) Brandeis University (T3) Brown University (T3) MIT (T2 and T3) Yale University (T3) NoX U Mass, Amherst (T3) Tufts University (T3) Northeastern University (T3) 22

  23. LHC Measurement Requirements 1 • Monitor up/down status of cross domain circuits • Publish status via a web services interface • Provide tools to visualize state • Generate NOC alarms when circuits change states • Monitor Link/Circuit Capacity, Errors & Utilization • Publish statistics via a web services interface • Provide tools to visualize the data • Generate NOC alarms when thresholds are crossed

  24. LHC Measurement Requirements 2 • Continuously measure delay between participants • Manage multiple sparse meshs of continuous tests and store results in an MA • Publish results via a standardized web service interface • Provide a tool to visualize the data • Provide tools to automatically analyze data and generate NOC alarms • Make scheduled bandwidth measurements across paths of interest • Manage multiple regularly scheduled sparse meshes of tests and store results in an MA • Publish results via a standardized web service interface • Provide a tool to visualize the data • Provide tools to automatically analyze data and generate NOC alarms

  25. LHC Measurement Requirements 3 • Measure & Publish Topology of both primary and backup paths • Publish statistics via a web services interface • Provide tools to visualize the data over time

  26. Directions Forward • Deploy measurement tools • To quantify the service your receiving/delivering • Set User Expectations • 100 to 300 Mbps per stream • Educate your user base • So they know what is possible

  27. Questions? • Joe Metzger (metzger@es.net) • Eric Boyd (eboyd@internet2.edu)

More Related