* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Slides - TERENA> Events> tnc2006
Survey
Document related concepts
Distributed firewall wikipedia , lookup
Computer network wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Internet protocol suite wikipedia , lookup
Piggybacking (Internet access) wikipedia , lookup
Passive optical network wikipedia , lookup
Multiprotocol Label Switching wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Brocade Communications Systems wikipedia , lookup
List of wireless community networks by region wikipedia , lookup
Telephone exchange wikipedia , lookup
Airborne Networking wikipedia , lookup
Network tap wikipedia , lookup
Wake-on-LAN wikipedia , lookup
Transcript
A WAN-in-LAB for Protocol Development Netlab, Caltech George Lee, Lachlan Andrew, David Wei, Bartek Wydrowski, Cheng Jin, John Doyle, Steven Low, Harvey Newman Outline What and why WAN-in-Lab? Current projects Equipment Configuration External connections Future plans How can I get access to WAN-in-Lab? What is WAN-in-Lab? “Wide Area” Network in a laboratory • Real fibre delays • Carrier-class routers, switches, … Why -- Spectrum of tools cost ? UltraLight PlanetLab Abilene NLR LHCNet CENIC etc DummyNet EmuLab ModelNet NS2 WAIL SSFNet QualNet JavaSim Mathis formula Optimization Control theory Nonlinear model Stocahstic model abstraction live netwk WANinLab emulation simulation maths All scales are important– WAN-in-Lab fills a gap Wind Tunnel of Networking WAN in Lab • Capacity: 2.5 – 10 Gbps • Delay: 0 – 120 ms round trip Configurable & evolvable • Topology, rate, delays, route • Modular design stays up to date Breakable • Won’t take down real network Flexible, active debugging • Passive monitoring, AQM Integral part of R&A networks • Transition from theory, implementation, demonstration, deployment • Transition from lab to marketplace Global resource • Part of global infrastructure UltraLight led by Harvey Newman Projects TCP benchmarking FAST • Delay-based congestion control MaxNet • Explicit signalling congestion control MojaveFS • New distributed file system University of Pittsburg • TCP with small buffers University of Melbourne • Single-bit congestion marking Example project: MaxNet Hardware Router Hardware Router Hardware Router Hardware Router 14 ms delay 14 ms delay 8x400km OC-48 2.5Gbps 8x400km OC-48 2.5Gbps 1 Gbit/sec 1 Gbit/sec Bottleneck Router 1 Bottleneck Router 2 ` ` Host A ` Host B ` Host C Listening server Sample MaxNet results Achieves realistic delay at 1Gbit/s Equipment 4 Cisco 7609 routers with OC48 line cards 6 Cisco ONS 15454 switches A few dozen high speed servers 1G switch to routers/servers Calient switch for OC48 2,400 kilometres of fibre, optical amplifiers, dispersion compensation modules 63ms aggregate RTT delay, in two hops • 120ms using IP loopbacks External connections Will link to Ultralight, 10Gbps Physics WAN Smooth migration testing -> deployment Delay • longer • jitter Cross traffic Monitor data routed through WiL Configuration -- Delays Want maximum delay from limited fibre • Signals traverse fibre 16 times 4 WDM wavelengths 4 OC48 (2.5G) MUXed onto OC192 (10G) Lots of transponders • WDM amplifier joins 100km spools 200km Configuration – delays OC48 slot 16x200km -------WDM Wavelength-------- Bidirectional 100km Bidirectional 100km Amp Configuration – delays Delay varied by adjusting the number of OC48 hops traversed Calient optical switch selects required hops Hop lengths 200km up to 1600km • Maximise granularity given limited switch ports Switch Future plans Better control over capacities and buffers Saturating links • Current servers 1Gbps, links 2.5Gbps Creative ways to emulate more topologies Investigate cross-traffic generation • Harpoon currently installed Better monitoring Using WAN-in-Lab Contact me – lachlan at caltech . Edu Coarse timesharing • Some users set up experiments while others run experiments Software setup still being developed • Your chance to influence our directions to tailor it to your needs Conclusion WAN-in-Lab fills the gap between emulation and live network experiments Seeks to be as realistic as possible • Long links, simple topology Focus will be on TCP benchmarking We encourage people to use it