adva multi-layer control plane technologies for hybrid networks

7/30/2019 Adva Multi-Layer Control Plane Technologies for Hybrid Networks

1/15

Wes DoonanOFC/NFOEC

March 2012

Multi-Layer Control PlaneTechnologies for Hybrid Networks


2/15

2012 ADVA Optical Networking. All rights reserved.22

Packet + Optical Networks

Integrates multiple networking technologies

Packet Service Layer

IP Routers, MPLS LSRs

Provides various IP/MPLS services directly to clients

Provides IP/MPLS infrastructure to Cloud/CDN applications

Packet technology, Packet focus, Packet operational practice

Optical Transport Layer

WDM transport elements, ROADMs, regenerators, amplifiers

Provides point-to-point wavelength services to Packet layer

Enables optical bypass at router sites where needed

Optical technology, Optical focus, Optical operational practice

P-PCE

LAX

ORD

ATL

PHX DFW

DIA

O-PCE


3/15


Layering Concept

Server layer network

Client layer network

= serverconnections

= link

= elementConnections in Server layer networkcreate Links in Client layer network

= client connection


4/15


Virtual Network Topologies

Abstract representation of a real network Built from virtual components virtual links, virtual nodes

Purpose: Abstraction Represent multiple real components as a single virtual component

Example: represent domain A as single virtual node in domain B

Purpose: Adaptation

Represent server layer network capabilities in client layer network Example: expose a lambda connection as a link in a packet topology

Purpose: Activation Coordination activation of capabilities across layers, domains

Example: server layer connection activated during client layer signaling

Virtual Topologies are planned

VNTs created during application planning process Prior to service provisioning, ongoing over lifetime of network

Represent "potentialities" of the real network E.g. what real connectivity "can" be, when requested


5/15


Virtual Topology Concept

Server layer network

Client layer network

= serverconnections

= virtual link

Connections in Client network triggerConnection setup Server network

Planning

= link

= element

= client connection


6/15


Workflow

1. Plan Connectivity

Real

or Virtual?

2a. Provision Real Link

2b. Provision Virtual Link

3. Provision Packet LSP

4. Provision MPLS LSPs

Enough

Topology?

Enough

Topology?PCE

Y

N

N

Y

R

V


7/15 2012 ADVA Optical Networking. All rights reserved.77

Packet TEDB

Links Creation

Purpose: Identify potential or dedicated connectivity

Optical domain to provide connectivity across domain

Dedicated: DFW->ORD

Potential: 2 x LAX->DFW, LAX->ORD

Dedicated connectivity provided by real links

Connections provisioned in optical domain, resources activated, etc

Potential connectivity provided by virtual links

Links advertised to packet domain, paths computed in optical domain

Optical domain resources not activated until client link is used

LAX

ORD

ATL

PHXDFW

DIA

= Packet = Optical


8/15


Packet TEDB

Provision Packet LSPs

LAX

ORD

ATL

PHXDFW

DIA

P-PCE

Purpose: Interconnect Routers

Router requested to provision connections across Packet domain

Example: DFW->ORD, DFW->LAX

Normal LSP provisioning operations within Packet domain

P-PCE used to determine/qualify most optimal paths

Considers access links (P-O) and network links (O-O)

Uses traffic engineering data on links provided by Optical domain

P-PCE computes optimal connectivity for client applications

When complete, Router advertises links to client MPLS network

= Packet = Optical


9/15


Packet TEDB

Virtual Link Options

LAX

ORD

ATL

PHXDFW

DIA

P-PCE

Purpose: Utilize other potentialities of the network

Optical characteristics change

LAX->PHX->DFW becomes optically worse than LAX->DIA->DFW

LAX->DIA->DFW computable due to virtual link

Paths can be re-routed as desired

Client requirements change (e.g. want LAX->ORD now)

LAX->ORD computable due to virtual link

LAX->DFW re-routable to LAX->ORD as desired

= Packet = Optical


10/15


Packet TEDB

GMPLS Overlay

LAX

ORD

ATL

PHXDFW

DIA

= Packet = Optical

Mechanism for building multi-technology overlay networks

Uses existing technologies as building blocks

Multi-Layer operation

Virtual Links, Virtual Nodes, Virtual Topologies

PCEs paired with domains and/or layers

Identify domain and/or layer boundaries

Allows definition of policies at domain/layer boundaries

What path should a connection take in a server network?

How should clients be notified of server network activation?

Etc ...

UNI

UNI

UNI

UNI UNI


11/15


GMPLS Overlay

GMPLS User to Network Interface Interoperable service activation across layers and domains

Origin: RFC4208 Defines the overlay network model, concepts

Outlines multiple scenarios, options, mechanisms

Initially issued in 2005, considerable experience since then

Update: draft-beeram-ccamp-gmpls-uni-bcp Presents "best current practice" profile of RFC4208

Derived from specific experiences, lessons learned Multi-layer activation, use of virtual topologies

Label signaling across technologies

Coordinating administrative status

Routing updates to support virtual nodes

Handling of generic constraints

Codify real-world operational practices, experiences


12/15


Fate Sharing

Virtual Links must reflect diversity of server network Server network connections may share fate

Multiple wavelengths which share the same fiber

Path computations in client network may require diversity Virtual links must expose fate sharing of server network connections

Shared Risk Link Groups (SRLGs) Integer annotations to TE links, identifying fate-sharing groups

SRLGs are per-layer/domain, must be coordinated somehow Different approaches

Server layer SRLG accumulation, macro SRLGs, etc

SRLG =

SRLG =

SRLG =

SharingServer Layer Client Layer


13/15


Constrained Switching Support

Switching constraints at UNI boundaries Some networks impose switching constraints at nodes

Example: Optical element with fixed-fiber add/drop site (FOADM)

Server network connection may include constrained hardware

Client network will need to know if switching constraints exist

draft-ietf-ccamp-general-constraint-encode Outlines mechanism for advertising constraints between links

Informs PCEs which links can be cross-connected at a node Client network PCEs take as input to constraint calculations

Generalized, not specific to particular transport technology

Not always required, depends on layer networks

B

D

C

A

{ A x B; A ! C; A x D }


14/15


Summary

LAX

ORD

ATL

PHXDFW

DIAUNI

UNI

UNI

UNI UNI

Multi-layer, multi-domain networks are a Reality

Packet + Optical, other network technology mixes

Multi-layer control mechanisms are also real

Architectures defined, standards in place

Virtual Network Topologies enable inter-layer coordination

Existing methods and abstractions, extended across layers

Overlay networking manages client/server network interactions


15/15

[email protected]

Thank you

IMPORTANT NOTICEThe content of this presentation is strictly confidential. ADVA Optical Networking is the exclusive owner or licensee of the content,material, and information in this presentation. Any reproduction, publication or reprint, in whole or in part, is strictly prohibited.

The information in this presentation may not be accurate, complete or up to date, and is provided without warranties orrepresentations of any kind, either express or implied. ADVA Optical Networking shall not be responsible for and disclaims anyliability for any loss or damages, including without limitation, direct, indirect, incidental, consequential and special damages,alleged to have been caused by or in connection with using and/or relying on the information contained in this presentation.

Copyright for the entire content of this presentation: ADVA Optical Networking.
http://blog.advaoptical.com/http://www.facebook.com/pages/ADVA-Optical-Networking/37630238931?ref=tshttp://twitter.com/ADVAOpticalNewshttp://www.linkedin.com/groups?about=&gid=1194227&trk=anet_ug_grppro

adva multi-layer control plane technologies for hybrid networks

Documents