1 / 24

NLR Layer2/Layer3 Users BOF NLR status update

NLR Layer2/Layer3 Users BOF NLR status update. Philadelphia Internet2 Member Meeting 19 September 2005 Brent Sweeny, Indiana University. SEA. POR. SYR. BOI. STA. NYC. PIT. OGD. DEN. CLE. KAN. CHI. SVL. SLC. WDC. RAL. LAX. ALB. TUL. PHO. ATL. SAN. DAL. ELP. PEN. JAC.

constancemoore
Download Presentation

NLR Layer2/Layer3 Users BOF NLR status update

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. NLR Layer2/Layer3 Users BOFNLR status update Philadelphia Internet2 Member Meeting 19 September 2005 Brent Sweeny, Indiana University

  2. SEA POR SYR BOI STA NYC PIT OGD DEN CLE KAN CHI SVL SLC WDC RAL LAX ALB TUL PHO ATL SAN DAL ELP PEN JAC BAT SAA HOU National LambdaRail design NLR owned fiber NLR WaveNet PoP NLR WaveNet & FrameNet PoP NLR WaveNet, FrameNet & PacketNet PoP NLR Layer2/Layer3 users BOF

  3. 15808 15454 6509 CRS-1 DWDM 10G wave, link or port 1G wave, link or port Generic NLR L1, L2 and L3 PoP Layout Colo West East NLR demarc NLR Layer2/Layer3 users BOF

  4. Cisco 15808 terminal Cisco 15808 OADM Cisco 15454 terminal Cisco 15454 OADM 8 8 4 4 NLR Layer 1 SEA 8 8 POR 8 BOI SYR 8 8 4 4 STA 4 4 NYC 4 4 4 OGD PIT 8 8 8 DEN KAN 8 8 CLE CLE 8 CHI 8 SVL 8 4 8 8 8 SLC 4 4 8 8 WDC 4 8 8 4 RAT RAL 4 8 LAX 8 4 TUL 4 PHO ALB 4 8 4 ATL 4 8 4 DAL 4 ELP 4 4 PEN 4 4 JAC 8 4 4 4 4 4 4 4 4 Level3 fiber WilTel fiber BAT 4 SAA 4 HOU NLR Layer2/Layer3 users BOF

  5. Cisco 15808 terminal Cisco 15808 OADM Cisco 15454 terminal Cisco 15454 OADM 8 8 4 4 Layer 1 Phase 2 Deployment SYR 4 4 4 NYC 4 4 OGD CLE DEN 4 KAN SLC 4 4 WDC 4 4 RAT LAX 4 4 TUL 4 PHO ALB 4 4 4 4 DAL 4 ELP 4 4 PEN 4 4 JAC 4 4 4 4 4 4 4 4 Level3 fiber WilTel fiber BAT 4 SAA 4 HOU NLR Layer2/Layer3 users BOF

  6. Layer 1 baseline • Opportunity to connect into lambda fabric • Point to point • Other endpoint could be anywhere • Early examples: • HOPI • Ultralight • iGRID • SC05 (Supercomputing) • Experiments support center (for all layers) NLR Layer2/Layer3 users BOF

  7. 10GE wave 10GE managed wave Yellow sites are done Cisco 6509 switch Layer 2 Network Design SEA CHI NYC PIT DEN CLE KAN SVL WDC RAL LAX ALB TUL ATL ELP JAC BAT HOU SVL NLR Layer2/Layer3 users BOF

  8. Layer 2 installation status Switch installations completed: Sunnyvale Denver Kansas City Chicago Cleveland Pittsburg Raleigh Washington DC Jacksonville Atlanta Los Angeles Tulsa El Paso Houston New York City scheduled for this week (Sept 20-21). Baton Rouge waiting for Katrina side-effects to calm down. (Was scheduled for the week of August 29, now tentatively Oct 11-12.) Albuquerque scheduled for mid-Oct. Interconnections being completed now. NLR Layer2/Layer3 users BOF

  9. Layer 2 service baseline • 1GE Connection into local 6500 • Access to “national peering VLAN” • Additional Options: • Dedicated point to point Etherrnet, Nx1GE • Best-effort point to multipoint (no dedicated bw) • Soon: • 10GE ports • Dedicated point-to-multipoint NLR Layer2/Layer3 users BOF

  10. Goal • Provide circuit-like options for users who can’t use, can’t afford, or don’t need, a 10G Layer1 wave via point-to-point layer2 VLANs. • Experiment with large-scale layer2 capabilities. NLR Layer2/Layer3 users BOF

  11. Dimensions of NLR Layer2 capabilities • point-to-point or multipoint • public or private • bandwidth guaranteed or best effort • resilient (spanning tree) or nailed up • temporary or permanent • experimental or stable/production-oriented Some of the above dimensions are either/or, some are more spectrum-like. The following slides show some expected uses of NLR layer 2, and how these dimensions may relate to each type of project. NLR Layer2/Layer3 users BOF

  12. National Peering Fabric • Multipoint, public, best-effort, resilient, permanent, stable • NLR allocated addresses, peer with any other member across the layer 2 fabric policy-free. • Possible to have more than one (say by MTU). • Ready to go today. • Backup connections to networks such as Abilene, commodity providers, etc. • Point-to-point, private, permanent, stable • Could be best-effort or guaranteed. • Could be nailed-up or resilient. • Load-balance or leave idle until needed. • Ready to go today, though we only have pricing for the guaranteed nailed-up case. NLR Layer2/Layer3 users BOF

  13. To enable a flexible topology for NLR layer3 • Best-effort, private, temporary, experimental • We have 8 layer3 nodes, but the topology between them can be made much more interesting by creating various connections over the layer2 network. • Enables layer3 experimentation. • To provide members with a second path into the NLR layer3 network • Point-to-point, private, permanent, experimental • Connect to a second node on the layer3 backbone. • Load-balance or leave idle until needed. • Included in membership. NLR Layer2/Layer3 users BOF

  14. Temporary connections for special projects • Guaranteed, private, temporary, stable • For remote instrumentation, where the member only has the remote resource reserved for a limited window. • For conferences, demos, and other special events. • Provides a low latency/jitter path if needed. • Nailed-up if latency is critical, probably resilient if not. • Could be point-to-point or multipoint. • Technically, this is possible today, but we have no pricing model for it. NLR Layer2/Layer3 users BOF

  15. Bootstrapping circuit-like research • Point-to-point, private, guaranteed, temporary, nailed-up, experimental • To enable a researcher to get started while waiting for funding or provisioning of a layer1 circuit. • Similar to a special event, but more experimental, a probably a stronger need for it to be nailed-up. • Technically, this is possible today, but we have no pricing model for it. • Provide control plane network for optical experiments • Permanent, resilient, experimental • A topology could be created for the oob management network needed for some dynamic optical networking experiments (GMPLS, etc.) NLR Layer2/Layer3 users BOF

  16. Cluster/Grid LAN • Multipoint, private, guaranteed, experimental • To enable remote clusters to appear on the same LAN. • It is not known if spanning tree would be wanted. • It could evolve into a more production-like requirement. • Technically, this is possible today, but we have no pricing model for it. • Experiment directly with Layer 2 • Could be of any type (experimental, obviously) • Web-based provisioning, direct user requests, etc. • Concern about interaction with more production-like requirements. NLR Layer2/Layer3 users BOF

  17. Cisco CRS-1 router 10GE wave Yellow sites are installed Layer 3 Network SEA CHI NYC DEN PIT WDC RAL LAX PHO TUL ALB ATL BAT JAC HOU LAX NLR Layer2/Layer3 users BOF

  18. Layer 3 installation status With the work this week in NYC, all layer3 router installations are complete. Waves are being built between routers and for layer3 backhaul now. NLR Layer2/Layer3 users BOF

  19. Layer3 service baseline • Each member gets two routed connections • “local” 10GE • VLAN backhauled to 2nd node • BGP peering with NLR L3 network • IPv4 unicast • IPv4 multicast (MBGP/PIM/MSDP) • IPv6 unicast (multicast later) • An ‘experimental’ (changeable, changing) L3 network NLR Layer2/Layer3 users BOF

  20. Layer 3 coming services • Likely eventual logical routers • More 1GE options • More 10G options • Pre-emptable connections • MPLS • More user control—scheduling, testing, etc • User access to measurement data NLR Layer2/Layer3 users BOF

  21. NLR Engineering/Support Organization A very distributed, coordinated organization: • Service desk at Indiana • Layer1 NOC and engineering at CENIC • Layer2/3 NOC and engineering at Indiana • Experiments support center at North Carolina NLR Layer2/Layer3 users BOF

  22. NLR User Resources • http://noc.nlr.net • info@nlr.net • research@nlr.net • esc@nlr.net NLR Layer2/Layer3 users BOF

  23. NLR Layer 2/3 - discussion What do users want/need? Tools? User groups? Instruction/workshops? Monitoring and measurement ability? Specify? Full routes? Control over route propagation? Control over protocols and timers? What would you do with logical routers? Direct access to login and configure routers? Commodity access or ISP collaboration? Collaboration with projects like PlanetLab and WAIL? Which others? NLR Layer2/Layer3 users BOF

  24. Summary from July ‘05 (Joint Techs BOF) • Costs • More deeply-technical descriptions of the architecture, service offerings • L2 and L3 service-design docs • Standardized interface into resources And some thoughts about possibilities: • "matchmaking" service, across all layers? • Logical routers: separate forwarding/control planes, possibly enabling customer logical networks (RONs) • Customer edge control • Native non-IP, non-Ethernet protocols? • Commodity internet peering? • What’s NLR trying to be? (“dancing-elephants or dancing-gerbils”, “facile/flexible”) NLR Layer2/Layer3 users BOF

More Related