Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

11
Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan Joe Mambretti, Director, (j- mambretti @northwestern. edu ) International Center for Advanced Internet Research ( www.icair.org ) Director, Metropolitan Research and Education Network ( www.mren.org ) Partner, StarLight/STAR TAP, PI-OMNINet ( www.icair.org/omninet ) OptIPuter Backplane Workshop OptIPuter AHM CalIT 2 January 19, 2006

description

Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan Joe Mambretti, Director, ( [email protected] ) International Center for Advanced Internet Research ( www.icair.org ) Director, Metropolitan Research and Education Network ( www.mren.org ) - PowerPoint PPT Presentation

Transcript of Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Page 1: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Joe Mambretti, Director, ([email protected])International Center for Advanced Internet Research (www.icair.org)

Director, Metropolitan Research and Education Network (www.mren.org)Partner, StarLight/STAR TAP, PI-OMNINet (www.icair.org/omninet)

OptIPuter Backplane Workshop

OptIPuter AHMCalIT2

January 19, 2006

Page 2: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Controller

Client Device

Client Controlle

r

Controller

ControllerControlle

r

Controller

Optical Control Plane

Client Layer Control Plane Optical Layer Control Plane

Client Layer Traffic Plane

Optical Layer – Switched Traffic Plane

UNI

I-UNI

CICICI

Page 3: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

IEEE L2 Scaling Enhancements

• Current Lack of Hierarchy• IEEE Developing Hierarchical Architecture• Network Partitioning (802.1q, vLAN tagging)• Multiple Spanning Trees (802.1s)• Segmentation (802.1ad, “Provider Bridges”)• Enables Subnets To be Characterized Differently Than Core• IETF – Architecture for Closer Integration With Ethernet

– GMPLS As Uniform Control Plane

– Generalized UNI for Subnets

– Link State Routing In Control Plane

– TTL Capability to Data Plane

– Pseudo – Wire Capabilities

Page 4: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

L1 10 Gbps

• 10 GE Node Compute Clsuters

• APIs

• Automated Switch Panels

• GMPLS

• IETF GMPLS UNI (vs ONI UNI, Implications for Restoration Reliability)

• 10 G Ports

• MEMs Based– Services

• Lightpaths with Attributes, Uni-directional, Bi-directional

• Highly Secure Paths

• OVPN

• Optical Multicast

• Protected Through Associated Groups

• ITU-T SG Generic VPN Architecture (Y.1311), Service Requirements (Y.1312), L1 VPN Architecture (Y.1313)

Page 5: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Chicago

Page 6: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Resource ResourceResource Resource

Physical Processing Monitoring and Adjustment

HP-PPFS HP-APP2 HP-APP3 HP-APP4

VS VS VS VS

ODIN ServerCreates/Deletes

LPs, Status Inquiry

tcptcp

AccessPolicy (AAA)

Process Registration

Discovery/ResourceManager, Incl Link Groups

Addresses

Previously OGSA/OGSI, Soon OGSA/OASIS WSRF

ProcessInstantiationMonitoring

ConfDB

Lambda Routing:

Topology discovery, DB of physical links

Create new path, optimize path selection

Traffic engineering

Constraint-based routing

O-UNI interworking and control integration

Path selection, protection/restoration tool - GMPLS

DataPlane

System ManagerDiscoveryConfigCommunicateInterlinkStop/Start ModuleResource BalanceInterface Adjustments

GMPLS ToolsLP Signaling for I-NNIAttribute Designation, egUni, Bi directionalLP LabelingLink Group designations

Control Channel monitoring, physical fault detection, isolation, adjustment, connection validation etc

OSM

UNI-N

Page 7: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Simple Path Control Protocol Specification

IETF Draft by D. Lillethun, J. Lange, J. Weinberger (iCAIR)(Ref:www.ietf.org)

• “The Simple Path Control Protocol (SPC) defined in this document is a new protocol defined to enable processes external to networks to establish, delete and monitor paths, including lightpaths. The architecture of this protocol establishes a method of providing messages, and procedures that allow such external processes to directly request network resources related to path provisioning.”

• “Various methods exist that allow paths, including lightpaths, to be established within a network. The Simple Path Control Protocol was developed

to enable external processes, including applications, to communicate messages that allow for such paths to be created, deleted and monitored. SPC defines a message that can be sent to a server that is capable of establishing a path on lower-layer network elements. After receiving such a request, the server is responsible for identifying the appropriate path through the controlled network topology and configuring it to fulfill the request. SPC also provides facilities for explicitly releasing a path when it is no longer needed, and for simple query facilities about the current network state.”

http://www.icair.org/spc/spc-internet-draft_august2004.html

Page 8: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

OMNInet Network Configuration 2006

10 GE

10 GE

To Ca*Net 4

710 Lake Shore

Photonic Node

600 S. Federal

Photonic Node

W Taylor 750 North Lake ShorePhotonic

Node10/100/GIGE

10/100/GIGE

10/100/GIGE

10/100/GIGE

10 GE

Optera5200

10Gb/sTSPR

Photonic Node

PP

8600

10 GEPP

8600

PP

8600

Optera5200

10Gb/sTSPR

10 GE

10 GE

Optera5200

10Gb/sTSPR

Optera5200

10Gb/sTSPR

1310 nm 10 GbEWAN PHY interfaces

10 GE

10 GE

PP

8600

Fiber

KM MI1* 35.3 22.02 10.3 6.43* 12.4 7.74 7.2 4.55 24.1 15.06 24.1 15.07* 24.9 15.58 6.7 4.29 5.3 3.3

NWUEN Link

Span Length

…CAMPUS

FIBER (16)

EVL/UICOM5200

LAC/UICOM5200

CAMPUSFIBER (4)

INITIALCONFIG:10 LAMBDA(all GIGE)

StarLightInterconnect

with otherresearchnetworks

10GE LAN PHY (Dec 03)

• 8x8x8 Scalable photonic switch• Trunk side – 10 G WDM

• OFA on all trunks

TECH/NU-EOM5200

CAMPUSFIBER (4)

INITIALCONFIG:10 LAMBDAS(ALL GIGE)

Optera Metro 5200 OFA

NWUEN-1

NWUEN-5

NWUEN-6NWUEN-2

NWUEN-3

NWUEN-4

NWUEN-8 NWUEN-9

NWUEN-7

Fiber in use

Fiber not in use

5200 OFA

5200 OFA

Optera 5200 OFA

5200 OFA

DOTClusters

Page 9: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

Optical Switch

Optical Switch

Optical Switch

Optical Switch

High Performance L2 Switch

High Performance L2 Switch

High Performance L2 Switch

High Performance L2 Switch

1 x 10G Wan

1x 10G Wan1 x 10G Wan

1 x 10G Wan

Trib ContentOC-192 – with TFEC 16OC-192 – without TFEC 12Ge 8OC-48 0

TFEC Link

Non - TFEC Link

Ge (x2)

Only TFEC link can support OC-192c (10G Wan) operation

Non -TFEC link used to transport Ge traffic

Ge (x2) Ge (x2)

Ge (x2)

Default configuration:

Tribs can be moved as needed

Could have 2 facing L2 SW

Default configuration:

Tribs can be moved as needed

Could have 2 facing L2 SW

TFEC = Out of band error correctionOMNInet 2005

750 North Lake Shore Drive710 North Lake Shore Drive

1890 W. Taylor

600 N. Federal

Page 10: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

710 NorthLake Shore Drive

600 South Federal

1940 WestTaylor

Core Testbed Site FiberSheridan, Evanston

350 E. Chicago

Core Node

111 North Canal

Page 11: Metro OptIPuter Backplane: Architecture, Research Plan, Implementation Plan

PNWGPSeattle

Pacific Wave

NLR

NLR

NASA Goddard2Level 3

Level 3

NASA JPL

NASA Ames

4

CalREN-XD

4

CENICSan DiegoGigaPOP

2

UCI

ISI CENICLos Angeles

GigaPOP

U Amsterdam

CERN

NetherLightAmsterdam

2

The OptIPuter LambdaGrid

UCSD

StarLightChicago

UIC EVL

NU

AmsterdamChicagoSeattle

San Diego

StarLight

Northwestern

UIC UoA

CERN

NASA Goddard

CENIC San Diego GigaPOP

UCSD

CENIC LA GigaPOP

NASA Ames

NASA JPL

ISI

UCI