What s MAX Production Been Up to Presentation to

What’s MAX Production Been Up to? Presentation to MAX membership Spring 07 Member Meeting Dan Magorian Director of Engineering & Operations

MAX Production topology 1. Original Zhone dwdm over Qwest fiber 2. Movaz dwdm over State Md fiber 3. Gige on HHMI dwdm over Abovenet fiber 4. Univ Sys Md MRV dwdm, various fiber BALT M 40 E Ring 4 R&E Nets CLPK National Internet 2 Lambda. Rail New. Net T 640 MCLN Ring 2 NGIX CLPK MCLN Ring 3 Qwest ISP ASHB T 640 Cogent ISP DCGW Ring 1 ARLG DCNE Qwest ISP Old Abilene

What has the Production Side of MAX been doing since the Fall member meeting? • Provisioned lambdas to help Internet 2 transition to Newnet & ESnet routers in Level 3 MCLN pop seamlessly. – Old Qwest router leaving for Kansas City Friday! • Designing new dwdm system for Baltimore BERnet – Uses “client dwdm”, lower end-to-end transponder costs. – Inexpensive idea usable anyone w/ local fiber, eg NOAA. – Interconnecting with new MIT pop in Baltimore at Level 3 • DWDM ring replacement: Phase 1 this FY – listening to vendor presentations now – TAC meetings for community input next month • New lab across hall MAX hdq (almost) done, tours welcome. • Buying advanced 1 G/10 G ethernet/sonet tester

Ongoing projects (con’t) • 10 G backbone upgrade underway, Juniper pics here soon • HHMI very generously providing 10 G protected lambda to Equinix Ashburn replacing 1 G. Thanks! • GWU provided old Juniper M 20 and M 10 routers for MAX lab. Thanks! Community welcome to use MAX test lab. • Provisioning Juniper VRFs for experimental service testing. • Ciena Core. Directors only took 9 months to buy (!), will be installed for NGIX & Internet 2 dynamic wave (DCS) fanout. • Want to convene community focus group to listen to member colo needs, mesh with what’s happening with I 2. • Atlantic. Wave: slowly going production, governance group service document work, MAX providing measurement pcs.

New Service: Layer 2 vlans • MAX has traditionally run Layer 1 (optical) and Layer 3 (routed IP) service. – Only NGIX/E exchange point is Layer 2 service. – Continues to be demand for non-routed L 2 service (vlans), similar to NLR’s Frame. Net service. – As replace old Luxn dwdm system and put in new, • quite economic to put in dwdm filters and 10 G ethernet switches with “colored” optics (XFPs) • This means that folks will be able to stretch private vlans from DC to Mclean to Baltimore over shared 10 G channel. • Also will be able to provision dedicated ethernet bandwidth – Haven’t figured out service costs yet. Will ask TAC.

New Service: Flow analysis • Turns out it would be useful to be able to characterize traffic flows passing thru MAX infrastructure. – So MAX buying Juniper hardware assists to do this. – Starting to look at open-source Flow Tools analysis. • Have in mind web interface where people put in AS #s – then look at flows to/from their institutions • By date range (yr), ASN, source & dest, traffic type. • The data is anonymized, packet contents not collected. • Have the cost for this one figured out: free! • Will ask TAC about details of what would like to see after have a prototype to comment on. • Also just heard about a local flow analysis workshop by expert kc claffey of CAIDA to be held at Loyola Columbia.

Flash: MIT is building Nortel dwdm system into Baltimore & offering to trade lambdas • They have well-funded DR initiative paying for ring build – from Boston to Albany and NYC, – spur down coast thru Philly to Baltimore Level 3 pop. • USM already has 2 fiber pairs 660 Redwood – 300 W Lexington, donating one for this (thanks!) • So now possibility of not just: – Baltimore lambdas south to MAX and Mclean to NLR and Internet 2, – But also north to NYC and Boston, eg NOX/Harvard – A bit like Atlantic. Wave “north” • MIT costs/lambda still under discussion, but eager to trade, may give us a shared 10 G in exchange.

Long-distance high-level diagram of new dwdm system (meeting MIT in Baltimore) MIT Nortel dwdm Albany MIT Nortel dwdm Boston MIT Nortel dwdm NYC Lambdas to Europe MIT Nortel dwdm BALT NLR and I 2 lambdas MAX dwdm MCLN BERnet Participants MAX dwdm CLPK BERnet dwdm 6 St Paul BERnet Participants

MAX view of current Baltimore L 1/L 3 topology (both lambdas pass thru CLPK router) BERnet Participants BALT M 40 e East & west OC 48 lambdas on USM MRV ring Internet 2 MCLN T 640 NLR MAX Movaz lambdas CLPK T 640

Proposed BERnet Production L 1/L 2 topology BERnet Participants Xconnect New BERnet Res DWDM USM F 10 Redwood St USM F 10 6 St Paul BERnet Participants USM MRV Xconnect New BERnet Res DWDM Participant Production lambdas MAX Movaz Dwdm New MAX F 10 MCLN BERnet Production 10 G lambdas MCLN T 640 USM MRV New MAX F 10 CLPK New DC ring CLPK T 640

High Level Regional Diagram of Balt Research Net JHU MIT 300 Lex. JHMI 40 wavelength MUX w ITU XFP’s Client Side Path UMBC 660 Redwood 6 St. Paul 40 wavelength Amplified Line Side Path One Transponder Pair to Pay for and Provision End to End MCLN NLR & I 2 College Park

Node Sites 6 St. Paul Three nodes and room for 40 10 Gbps channels ~ $130 K per site with Mclean Level 3 and College Park nodes being paid for by MAX. Pre Amplifiers at all three sites MCLN NLR & I 2 College Park

“Client” and “Line” dwdm provisioning example JHU Client-side: instead of “normal” 1310 optic, “colored” dwdm XFP pair on an assigned wavelength 40 km reach $6 K 660 Redwood 6 St. Paul Line side: Transponder Pair makes the 185 km reach with Amps and holds the client XFP $32 K MCLN NLR & I 2 College Park

More “Client Dwdm” examples between participants JHU switch DWDM XFP pairs on an assigned wavelengths on 40 channel dwdm filters (40 km reach $6 K). Red lambda is to DC, blue to NYC, green local to UMBC 6 St. Paul 660 Redwood DWDM 300 W Lexington DWDM UMBC All each participant fiber needs is filter pair, not full dwdm chassis

MAX will replace some dwdm nodes this FY (summer install) and some next FY • Phase 1: College Park, Mclean, Baltimore research net. – Since have protected ring, can cut one side, then other. – Balt research fiber is new (actually old Ciena OC 48). – Will select and procure vendor soon. • Phase 2: GWU and Qwest Eckington next FY – Replacing original Luxn dwdm ring – Demand for lambda services to Dc unknown • Have met with Qwest for comarketing to justify DCNE upgrade – Might do client dwdm with shared 10 G ethernet instead • This means that MAX working to unified new dwdm system! • Get involved with TAC to hear details: tac@maxgigapop. net

Closing thought: “Lots of lambdas in your future, what are you going to do about it? ” • This was the title of a BOF at the I 2 MM yesterday hosted by Joe St Sauver, U Oregon. • Idea was to get people thinking about the sea change happening in the community – appropriate campus strategies for fanout – to researcher high-bandwidth projects. • Not replacement of “regular” ip routing, but in addition • Circuit-like services for high-bandwidth low-latency projects • People may say, “I don’t have any of those apps right now” – But suddenly may have researchers with check in hand – Need to plan for how will deliver, just as BERnet doing – Eg, in planning phase now for DC ring, need to forecast. – Talk to us about what you’re doing and thinking!

Thanks!