NLR Update: Backbone Upgrade Joint Techs July 2008

Size: px

Start display at page:

Download "NLR Update: Backbone Upgrade Joint Techs July 2008"

Gladys Smith
5 years ago
Views:

1 NLR Update: Backbone Upgrade Joint Techs July 2008 Dave Reese 1

2 National LambdaRail Infrastructure National LambdaRail, Inc. 2

3 NLR Backbone Upgrade Upgrade Phase 1 portion of NLR backbone Jacksonville to Los Angeles Vendor Selection process Phase 1 Vendor Review 1 representative from each NLR Member Presentations from 4 Vendors on optical plan for replacing s Ciena, Cisco, Infinera, Nortel Selected Cisco platform Criteria: Commitment to research Technical plan Maintenance and support plan Cost 3

4 Upgrade - Installation Vendor Selected Installation Vendor through RFP process. Responses were due by July 3rd, decision made by July 15th. Selected LightRiver Technologies Criteria: Technical Merit Qualifications Completeness Project Length Additional factors, including cost 4

5 Upgrade - Final Steps Finalize implementation plan Work with LightRiver, Cisco on outstanding issues Place equipment orders Finalize Build of Materials Expect to place equipment orders by 7/31/08 Finalize timeline August January

6 Implementation - Overview General principles 96 AMP sites and 16 Add/Drop sites Reduced regeneration sites to 7 LOSA, SEAT, ODGE, KANS, CHIC, WASH and JACK Added 1 Add/Drop site - St. Louis Added in order to support 1st generation 40 GE cards along the CHIC to KANS path. 6

7 Upgrade - Overview Phase 1 Backbone divided into 4 sections, with a total of 7 routes Circuits fall naturally into these sections Only 3 circuits cross these boundaries Routes within a section completed before starting the next section LightRiver Technologies Receive delivery of equipment Rack and test equipment Deliver equipment racks to sites Work with NLR staff and Level3 to install and test De-install and dispose of equipment 7

8 Implementation - General Backup Plans Additional fiber path LOSA to SEAT and JACK to WASH No outages expected for these sections. Layer2/Layer3 Will reroute automatically May see increased latency 10 GE and less than 4 Gb of traffic Temporarily reroute on Layer2 or Layer3 Leased waves from Level3 Augment Layer2 and Layer3 Reroute specific nodes - BOIS, ODGE, PITT Prolonged outages Typically research circuits, approved by end user(s). 8

9 Sections and Routes BOIS OGDE DENV KANS CHIC CLEV PITT SEAT PORT SUNN Rg A/D Rg Rg A/D A/D Rg A/D (10) Rg 9 4 A/D A/D (4) 26(2) 10 A/D A/D WASH RALE ATLA LOSA Rg Rg JACK 9

10 Implementation Timeline 10

11 Stage 1 - Jacksonville to Washington, DC Specific routes - Washington-Raleigh-Atlanta-Jacksonville Upgrade will begin by late August Spare fiber from MCNC to backup entire route Additional backup by re-routing FrameNet Atlanta to Chicago Jacksonville to Chicago - through Houston Minimal outages expected Limited to just cut over to other paths 11

12 Stage 1 Washington DC to Jacksonville

13 Stage 2 - Seattle to Los Angeles Specific Routes Los Angeles-Sunnyvale Sunnyvale-Portland-Seattle Upgrade will begin once JACK to WASH upgrade is completed Spare fiber from CENIC along the entire route Minimal outages Limited to cut over between fiber paths 13

14 Stage 2 - Seattle to Los Angeles

15 Stage 2.5 Re-route NASA wave along the Southern path Only wave that crosses multiple sections Re-routed along already upgraded sections Minimal outages Just during cutovers 15

16 Stage 2.5

17 Stage 3 - Chicago to Washington Specific route Chicago-Cleveland-Pittsburgh-Washington Upgrade expected to begin late October or early November time period Currently 18 circuits along this path Level3 Waves Chicago to Washington Pittsburgh to Washington Re-route FrameNet North through Boston and then to Chicago 17

18 Stage 3 - Chicago to Washington

19 Stage 4 - Seattle to Chicago Specific routes Seattle-Boise-Ogden Ogden-Denver-Kansas City Kansas City-Chicago Currently 24 waves along these routes Upgrade will begin after Stage 3 is completed Stage 4 expected to be completed end of January 2009 BoreasNet 2 Waves from Kansas City to Chicago Level3 Chicago to Seattle Ogden to Denver Denver to Kansas City 19

20 Stage 4 - Seattle to Chicago Re-route over FrameNet Chicago to Seattle - via the southern route Houston to Chicago - via Atlanta Shortest path will be used - New FrameNet path directly between Atlanta and Chicago 20

21 Stage 4 - Seattle to Chicago

22 Dynamic VLAN Service What is DVS? NLR service for dynamic VLANs on FrameNet What is Sherpa? Tool used for DVS Used for provisioning the dynamic VLANs on FrameNet Graphical Web-based interface (using RealTime Atlas maps) API is available for Programmatic Access Also used by GRNOC engineers to provision static VLANs Can I try it? Find out more? Live Demo interface link at noc. General DVS & API FAQ also available on noc. If all else fails, noc.

23 Dynamic VLAN Service

Update on National LambdaRail

GLIF 2007, Prague, September 17 th, 2007 Update on National LambdaRail John Silvester Special Advisor to CIO for High Performance Networking, Professor of Electrical Engineering, University of Southern