dont forget the control planedont forget the control plane

7/30/2019 Dont Forget the Control PlaneDont Forget the Control Plane

1/17

MPLS-TP

Dont Forget the Control Plane!

Pat MooreMetaswitch Networks

Network Technologies Division

[email protected]

Visit us at stand 205
mailto:[email protected]://www.metaswitch.com/http://www.upperside.fr/mplsworld2011/mpls2011intro.htmmailto:[email protected]


2/17

Copyright Metaswitch Networks | www.metaswitch.com | 1

Metaswitch Expertise

Previously Data Connection Ltd. (DCL)

Network Protocol source code since 1983

1st portable GMPLS protocol solution

1st portable O-UNI protocol solution

1st

portable LMP protocol solution1st portable G.709 OTN protocol solution

1st portable MPLS-TP protocol solution

Customers
http://www.tellabs.com/http://www.foundrynetworks.com/http://www.force10networks.com/http://www.ecitele.com/http://www.nec.com/http://www.orckit.com/en/home/a/01/


3/17


Agenda

MPLS-TP management provisioned vs. control plane

The benefits of an MPLS-TP control plane

Where does it fit?


4/17


MPLS-TP Management Provisioned

Full centralized control of

Each LSP

Each hop of each LSP

Each backup LSP

Packet LSP and PW sublayers

Intelligence resides in the NOC

Simple and predictable

Works well in simple topologies


5/17


MPLS-TP with a Control Plane

As management provisioned Same OAM

Plus a control plane

Both modes can co-exist

One-touch provisions entire LSP

Intelligence resides in NEs Auto-discovery of NEs and topology

Auto-tracking of available capacity

Route calculation

Signalling of LSP

Automated operation

Reduced OPEX


6/17


Agenda



Where does it fit?


7/17Copyright Metaswitch Networks | www.metaswitch.com | 6

Automated Discovery

IGP (e.g. OSPF) used to auto-discover NEs and links

Opaque LSAs flood link attributes

Available bandwidth

Latency

Whatever is important in your network

Standard TE extensions to OSPF and IS-IS



Link Bundling

New link detected by local NEs

No change in network topology

IGP floods increased capacity on bundled link

Improved IGP scalability

Signalling chooses component link to use for each LSP



Automated LSP Setup

Ingress NE processes LSP setup request (egress, bandwidth, etc.)

OSPF-TE route calculation runs on ingress NE

GMPLS signalling sets up each NE on the MPLS-TP path

Standard GMPLS extensions to RSVP-TE Targeted LDP signalling used for PW layer


10/17


Automated Protection and Restoration

Various GMPLS protection and restoration schemes

Mesh Restoration and Segment Recovery defined

Linear and Ring Protection underway

Substantial automation Automated diverse route calculations for 1:N protection

Automated placement of branch and merge points

Automated reversion when primary LSP recovers

Intelligent use of backup LSP for low priority traffic


11/17


On-demand Provisioning

LSP Setup request does not have to come from NOC

E.g. router acting as client to MPLS-TP layer

Router requests extra network capacity at its attached NE

User-to-Network Interface (UNI)

Client-server model between network layers


12/17


Control Plane Extensions and Benefits

OAM signalling Enables NEs to agree what OAM mechanisms are to be used

No spurious alarms as OAM start is synchronized with end-to-end LSP activation

Reduced OPEX

Management Control Plane hand-off Management-established LSPs transitioned to control plane

and vice-versa

Facilitates network migration

Multi-segment pseudowire Adapting existing MS-PW to the MPLS-TP profile

Supports more diverse deployment scenarios

Standards baked


13/17


Agenda



Where does it fit?


14/17


Typical Deployment Scenario

Three MPLS-TP domains shown

Backbone uses control plane

Access uses management provisioning

MS-PW crosses domains to provide the end-to-end service

Access

MS-PW

Service

Backbone

S-PE

Access

S-PEStatic LSPSignalled LSPStatic

T-PE

Static

T-PE

Static LSP


15/17


Multiple layers can include MPLS-TP transport service sublayer (e.g. PW for L2 Ethernet service)

MPLS-TP transport sublayer

TDM layer (OTN ODU)

WDM layer (OTN OCh)

Each Carrier uses only the layers it needs

Only use a layer if it adds value Other layers possible

GMPLS is common

Commonality Across Network Layers


16/17


Conclusion: Dont Forget the Control Plane

MPLS-TP control plane is beneficial It brings significant automation and reduced OPEX

Management provisioned and control plane NEs will co-exist in many networks

Many vendors building NEs with both management and control plane provisioning

Standards are in place GMPLS has been around for years

Common GMPLS technology across layers Coherent management

Same look and feel

Come seeMetaswitch MPLS-TP at the

EANTC Live Demo
http://www.eantc.de/javaschttp://www.eantc.de/javasc


17/17

Thank [email protected]

Visit us at stand 205
http://www.metaswitch.com/http://www.upperside.fr/mplsworld2011/mpls2011intro.htm

dont forget the control planedont forget the control plane

Documents