1 / 7

Midwest Tier 2 ATLAS Connectivity

Midwest Tier 2 ATLAS Connectivity. By Brent O’Keeffe. Current Connectivity. Dual 10GE Connections to Regional Networks MREN CIC OmniPOP Layer 2 Peer Mapping to Brookhaven National Labs for Tier 1 Indiana University for Midwest Tier 2

gemma-hinton
Download Presentation

Midwest Tier 2 ATLAS Connectivity

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. Midwest Tier 2 ATLAS Connectivity By Brent O’Keeffe

  2. Current Connectivity • Dual 10GE Connections to Regional Networks • MREN • CIC OmniPOP • Layer 2 Peer Mapping to • Brookhaven National Labs for Tier 1 • Indiana University for Midwest Tier 2 • Additional peering needed for new Midwest Tier2 member UI-UC • Dual Layer 3 peering to Internet 2 for fallback ATLAS connectivity

  3. UChicago Current Connectivity

  4. Future Architecture • Larger Data Flows • Bandwidth Availability • Campuses Beyond 10Gb / Up to 20Gb possibly? • MREN versus OMNIPOP • UChicago/UIUC Direct Physical Connection • 100Gb Roadmap • Upgrading Ciena DWDM to 100G Capable – Jan. 2012

  5. Standard Connectivity

  6. Investigating Layer 3 • Connect to LHCONE using two paths • Static mapped VLAN 3000 via MREN / Starlight • Dynamic mapped VLAN 3000 via DYNES (through CIC OmniPOP) • Routed border to LHCONE Network • Implement Optimized Edge Routing • Utilizing BGP Local Pref and AS Prepending to prefer one path vs. another • Decision may be based on many factors (Latency, jitter, probe data) • May require additional LHCONE IP Space • Advertise more granular CIDR ranges to distribute load

  7. Investigating Layer 3

More Related