Copyright 2004 National LambdaRail, Inc Connecting to National LambdaRail 6/23/2004 Debbie Montano Director, Development & Operations [email protected] [email protected]

Copyright 2004 National LambdaRail, Inc

Connecting to National LambdaRail

6/23/2004

Debbie MontanoDirector, Development & Operations

[email protected]

mailto:[email protected]


NLR Is…• Infrastructure for Research & Education• Multiple networks… to start:

– Owned fiber (20 years) nationwide– Layer 1 DWDM Optical Infrastructure (production) –

supporting up to 40 10 Gig lambdas– Layer 2 GigE network (production)– Layer 3 IP network (experimental? production?)– Lambdas to support additional Layer 2 and 3

experimental (or production) networks– Possibility of fiber to support additional experimental

Layer 1 infrastructure


Connecting to NLR

• NLR is multiple infrastructures/networks• Layer 1 Optical Infrastructure

– 10 Gig lambdas (10 GE or OC192)

• Layer 2 GigE Network– 1 GigE client ports– Utilized 10GE lambdas between switches

• Layer 3 IP Network– 10 GE port for each NLR member



Layer 1 Connection Points10 Gig waves can begin or terminate at any NLR optical terminal, optical add drop multiplexer

(OADM), or regeneration site. The complete list of such sites is:

Atlanta, GA Houston, TX Raleigh, NC

Albuquerque, NM Jacksonville, FL Salt Lake City, UT

Baton Rouge, LA Los Angeles, CA San Antonio, TX

Boise, ID Kansas City, MO San Diego, CA

Cleveland, OH New York, NY Seattle, WA

Chicago (NLR/L3), IL Ogden, UT Sunnyvale, CA

Chicago (Starlight), IL Pensacola, FL Tulsa, OK

Dallas, TX Phoenix, AZ Washington, DC

Denver, CO Pittsburgh, PA

El Paso, TX / Las Cruces, NM Portland, OR


Primary NLR Layer 1 Location by NLR Member

NLR Member Primary NLR Layer 1 Location(NLR MetaPOP)

CENIC Los Angeles, Sunnyvale

CIC Chicago, Cleveland, (Pittsburgh)

Cisco N/A

Cornell New York

Duke/North Carolina Raleigh

Florida LambdaRail (FLR) Jacksonville

Georgia Tech Atlanta

Internet2 N/A


Primary NLR Layer 1 Location by NLR Member(Continued)

NLR Member Primary NLR Layer 1 Location(NLR MetaPOP)

LEARN Houston

Louisiana Board of Regents Baton Rouge

MATP / Virginia Tech DC

Oklahoma State Board of Reg. Tulsa

PNWGP Seattle, Portland

PSC Pittsburgh

University of New Mexico Albuquerque

UCAR/FRGP Denver


Layer 1 - 10 Gig Lambdas• Framing:

– 10 Gigabit Ethernet LAN PHY – or OC192

• 15454 transponder cards configurable to 10GE or OC-192

• 15808 use dedicated 10GE or OC192 cards– (OC-192 require two slots vs 1 for 10GE)

• 10GE is “preferred” for NLR waves, but OC-192 can be ordered and supported.


HOU

TUL

ELP

KAN

PHO

BAT

LAXALB

PIT

WDC

CLE

ATL

RAL

CHINYC

DENSVL

SEA

JAC

Layer 2 – Proposed GigE Network Topology


Layer 2 - GigE

• 1 GigE “circuits”• Cisco 6509/7609 Ethernet switches • 10 Gig backbone connections between switches• Switches located at important location for each

member plus network intersection points• Modest additional charge for each 1 GigE path

dedicated to members use• Connect at any NLR GigE switch location

– Can have start and/or end of each 1 GigE circuit anywhere – does not have to be at the GigE switch in member’s territory


Layer 2 / GigE Connection Points

NLR Member NLR GigE Switch locations in each NLR Member’s region

CENIC Los Angeles, Sunnyvale

CIC Chicago, Cleveland, (Pittsburgh)

Cisco N/A

Cornell New York

Duke/North Carolina Raleigh

Florida LambdaRail (FLR) Jacksonville

Georgia Tech Atlanta

Internet2 N/A


Layer 2 / GigE Connection Points(Continued)

NLR Member NLR GigE Switch locations in each NLR Member’s region

LEARN Houston, El Paso

Louisiana Board of Regents Baton Rouge

MATP / Virginia Tech DC

Oklahoma State Board of Reg. Tulsa

PNWGP Seattle

PSC Pittsburgh

University of New Mexico Albuquerque, El Paso

UCAR/FRGP Denver

Undesignated Kansas City


Proposed IP Network(Draft)

ALB

BAT

RAL

JAC

TUL

PIT

LAX

WDC

ATL

CHINYC

DEN

SEA


Layer 3 -- IP Network

• Cisco Core routers• 10 Gig backbone lambdas• One 10GE port for each NLR member

– Included with NLR membership at no extra charge

• Connect at NLR router in territory or via NLR provided backhaul to nearest router (outside territory)


IP Network Connection PointsNLR Member NLR MetaPOP

where Member will Connect to NLR IP Network

NLR Router Location

CENIC Los Angeles Los Angeles

CIC Chicago Chicago

Cisco SVL/Raleigh ? LA & DC or Atlanta

Cornell New York New York

Duke/North Carolina Raleigh DC or Atlanta

Florida LambdaRail (FLR) Jacksonville Atlanta

Georgia Tech Atlanta Atlanta

Internet2 Chicago ? Chicago


IP Network Connection PointsNLR Member NLR MetaPOP

where Member will Connect to NLR IP Network

NLR Router Location

LEARN Houston Houston

Louisiana Board of Regents Baton Rouge Houston

MATP / Virginia Tech DC DC

Oklahoma State Board of Reg. Tulsa Houston (Chi or Den?)

PNWGP Seattle Seattle

PSC Pittsburgh DC

University of New Mexico Albuquerque Denver

UCAR/FRGP Denver Denver


Connecting to NLR

• Must come to NLR “MetaPOP” – Suite/colo in fiber provider POP (e.g. Level3)

• Can bring permanent fiber into the NLR suite– Examples: PNWGP in Seattle– Southern LambdaRail (SLR), aka Georgia Tech in

Atlanta

• Or simple fiber cross-connect


NLR Support• NLR Network Operations Center (NOC)

– [email protected]– 866-657-9283 (866-nlr-wave)– http://noc.nlr.net– http://www.nlr.net

• Debbie Montano – “member liaison”– Director, Development & Operations

• Steve Cotter– NLR Implementation Manager, [email protected]

• NLR Experiments Support Center– Mark Johnson, MCNC (under development)

• NLR Engineering Committee– Dave Reese, Chair, [email protected]


http://noc.nlr.net/

http://www.nlr.net/



Questions?

Thank You!

Debbie MontanoDirector, Development & Operations

[email protected]

www.nlr.netnoc.nlr.net


http://www.nlr.net/

Documents

Copyright 2004 National LambdaRail, Inc Connecting to National LambdaRail 6/23/2004 Debbie Montano Director, Development & Operations [email protected] [email protected]