Nlr.net © 2004 National LambdaRail, Inc NLR Update Jt. Techs, Madison July 17, 2006

nlr.net© 2004 National LambdaRail, Inc

NLR Update

Jt. Techs, MadisonJuly 17, 2006

nlr.net

© 2004 National LambdaRail, Inc

Topics

• Infrastructure Update• Uses• Hardening Update• SC06 Summary


Infrastructure Update

NLR owned fiber* NLR WaveNet, FrameNet & PacketNet PoPNLR WaveNet & FrameNet PoPNLR WaveNet PoP

PoP for primary connection point by a member (“MetaPoP”)PoP needed because of signal regeneration requirementsbut can also be used for secondary connection by a memberPoP established by NLR for members regional needsPoP established at exchange points

RATO

BATO

SAND

STAR

CHICSALT

HOUS

DALL

SYRA

TULS

PENSELPA

KANS

PHOE

LOSA

ALBU

PITT WASH

BOIS

CLEV

ATLA

PORT

RALE

NEWY

SANA

DENVSUNN

SEAT

JACK

OGDE

* Fiber on the SAND-LOSA-SUNN path belongs to CENIC

NLR Infrastructure Status - June 2006

NLR owned fiber* NLR WaveNet, FrameNet & PacketNet PoPNLR WaveNet & FrameNet PoPNLR WaveNet PoP

PoP for primary connection point by a member (“MetaPoP”)PoP needed because of signal regeneration requirementsbut can also be used for secondary connection by a memberPoP established by NLR for members regional needsPoP established at exchange points

RATO

BATO

SAND

STAR

CHICSALT

HOUS

DALL

SYRA

TULS

PENSELPA

KANS

PHOE

LOSA

ALBU

PITT WASH

BOIS

CLEV

ATLA

PORT

RALE

NEWY

SANA

DENVSUNN

SEAT

JACK

OGDE

* Fiber on the SAND-LOSA-SUNN path belongs to CENIC

NLR Allocated Waves - planned% used/Free

5%/19

20%/16

75%/5

30%/28

30%/28

30%/28 40%/24 50%/20

59%/13

50%/10

25%/15

40%/12

25%/3025%/15

30%/14

30%/14

28%/29

31%/22

25%/24

25%/24

25%/2422%/2528%/2328%/23

25%/2422%/25

34%/21

38%/2038%/20

31%/22

31%/2231%/22

22%/25

nlr.net


WaveNet Summary

• Adding 21 new circuits by August 1st• 77 new layer 1 segments

• Utilization• 24% April 2006• 32% expected by August 2006• Segments with 50% utilization or better

– SUNN to SEAT - 75%, CHIC to STAR - 59%, KANS to CHIC 50%, CHIC to CLEV 50%

nlr.net


FrameNet Summary

• Use of non-dedicated service is growing• TransitRail• UltraLight• Texas A&M University

• Interest by research groups• Collaborative multi-point projects• Non-dedicated service

• Understand utilization, then migrate to dedicated service.• New Services

• Investigation of on-demand dedicated services• Process for implementing - both backbone and RONS

nlr.net


PacketNet

• Connection Status• 12 out of 14 Members connected• 9 of the 12 have 10 GE

• 6 also have 1 GE secondary connections• 3 with GE or multiple GE

• Peering• USGS, StarLight,CA*Net,Ultralight• ESnet - at StarLight and MANLAN• DREN, NREN - pending completion of agreement

• Total routes - ~3500

nlr.net


NLR PacketNet Goals

• Meet the needs of the Network Research community and the Gigapop/RON community• AUP-free

• Allow each group to determine what traffic to send• Removes the need for some “stupid routing ticks”

• Full routing tables• Add some level of Commodity connectivity

• Real traffic environment• Allows for better testing of new network protocols

nlr.net


nlr.net


NLR Optical Switching Project

• Calient Switch• Three possible objectives

• Shared control between backbone and RON.• Fault Tolerance• GMPLS experimentation

• Engineering Committee • Subcommittee to make recommendation on

priorities and switch placement by end of June.

nlr.net


NLR Measurement Infrastructure

• Infrastructure to support both operation and research measurement needs

• Provides pre-GENI infrastructure• Data collection and dissemination points for NLR

services - PacketNet, FrameNet and possibly WaveNet.

• Process• Final review by Engineering committee• Submission to NNRC for review, comments and

recommendation• Positive review by NNRC, recommendation to

board for funding.


Operations - Sparing

nlr.net


Sparing

• Focusing on transponder outages• Goal is to reduce outage to <2 hours. • Use existing resources as much as possible

• 80-channel transponder cards• Availability of quickstart or spare wave• Remote hands to make changes

• Work with Layer1 NOC and Service desk to develop process and procedures

• Identify other components to spare


Projects

nlr.net


Cisco Research Wave Projects

• UltraLight• PI - Harvey Newman, Caltech• Collaboration of experimental physicists and network engineers

whose purpose is to provide the network advances required to enable petabyte-scale analysis of globally distributed data.

• Infrastructure - migrating to 10 GE PacketNet and 10 GE FrameNet

• TransLight• PI - John Silvester, Univ. of Southern California• Development of a distributed exchange facility on the west

coast to allow interconnection of international research and education networks in the US.

• Infrastructure - WaveNet Circuit

nlr.net


Cisco Research Wave Projects

• EnLightened• PI Gigi Karmous-Edwards, MCNC • Developing a dynamic, adaptive, coordinated and

optimized use of networks connecting geographically distributed high-end computing resources and scientific instrumentation.

• Infrastructure - WaveNet circuits

nlr.net


Research Projects

• CHEETAH• PI – Malathi Veeraraghavan, Uva• A high-performance, experimental, optical network infrastructure

capable of: (a) on-demand provisioning of end-to-end high-speed circuits, (b) stable transport to sustain control and streaming operations, and (c) middleware and application software to support data transfers, visualization, steering and control.

• Infrastructure - WaveNet circuit• VINI

• PI Larry Petersen/Jennifer Rexford• VINI is a virtual network infrastructure that allows network researchers

to evaluate their protocols and services in a realistic environment that provides a high degree of control over network conditions.

• Infrastructure - an overlay testbed using NLR co-location, FrameNet and PacketNet services.

nlr.net


Research Projects

• Cornell AnyCast• Case Western Reserve QoS• Optiputer• Lambda Switching Scheduler• NLR Optical Switching Project• Community Cyberinfrastructure for Advanced Marine

Microbial Ecology (CAMERA)• Extensible Terascale Facility• Pacific Wave• UltraScience


SC06 Plans

nlr.net


NLR SC06

• Layer 1• Infrastructure for Atlantic Wave

– Permanent, ordered in time for it to be implemented by SC06.

• Layer3 and Layer2• 10 GE from JACK to TAMPA, 10 GE from PENS to

TAMPA for each service• Assumes the PENS to TAMPA is for redundancy• Both will be delivered to the show floor

– CRS-1 and 65xx provided by Cisco to terminate service

• Assumes FLLR will provide backhaul to Tampa

nlr.net


NLR SC06

• Peering • Leverage existing connections

– PacificWave, StarLight, MANLAN• Provide transit for other networks. Example - ESnet.

• Investigate providing Quality of Service• At both Layer2 and Layer3

• Already received some application requirements• Integrated into NLR inquiry process

• General idea• Divide up links in terms of bandwidth and time of day

– Support demo requirements. Better use of the network

Documents

Nlr.net © 2004 National LambdaRail, Inc NLR Update Jt. Techs, Madison July 17, 2006