White Paper MPLS-TP in Mission Critical Systems

Download as pdf or txt
Download as pdf or txt
You are on page 1of 6

White Paper

MPLS-TP in Mission-Critical Systems

2015-10-22
KEYMILE 2015

White Paper
MPLS-TP in Mission-Critical Systems

Mission-Critical Systems
Security
Transportgrade
Technilogy

A Mission-Critical System (MCS) is a highly


reliable and secure network infrastructure that
provides critical applications for HV/MV Energy
& Distribution Grids, Oil & Gas Pipelines,
National/Urban Railways, High-speed Railway
Lines, Homeland Security, Public Safety, Air
Traffic Management & Control, essential to the
survival of a business or organization. When a
MCS fails or is interrupted, business operations
are significantly impacted.

Bandwidth
Flexibility

MPLS-TP

Lower
TCO

Figure 1: Main drivers for MPLS-TP

existing transport networks, the migration


towards PTNs is increasingly becoming a part
of the business strategy for many MCS business
organizations, replacing the existing (and
potentially more costly) TDM-based transport
networks.

Reliability is the most important aspect of a


MCS and new technologies are introduced only
if there are strong new requirements. Existing
TDM-based transport networks (e.g. SDH/
SONET) have proven to be highly reliable,
setting a high benchmark for future-proof
technologies.

Multiprotocol Label Switching


IP-based Multiprotocol Label Switching (IP/
MPLS) is a mature packet-based technology
generally adopted in core networks environments for connection-less services. It is
dependant of a control plane for dynamic
network behavior and unidirectional in nature.
As IP/MPLS is often deployed at the core,
consolidation of core and transport networks
onto a common MPLS-based infrastucture
becomes imperative. Although, IP/MPLS knows
explict routing it is still dependant of a control
plane to set-up all connections from/to a node.
Even more so during a power failure, where
control plane needs to be set-up again for all
nodes. IP/MPLS also knows fast reroute (FRR)
mechanisms, which could achieve sub-50 ms
protection switchover. However, the data plane
switches to a temporary (reroute) bypass path
and then (in a second step) calculates a new
unidirectional path (quite complex).

MCS network operations and service activation


require secure and careful planning and engineering. Therefore, operational simplicity and
security are key to minimize operational risks
and minimize threats to guarantee continuous
and optimum service performance.
As MCS networks are required to be more
cost-efficient, packet-based technology is
becoming economically attractive as it can
support fast-growing packet-based services at
lower costs and provides the means to take
advantage of more flexible data rates and
statistical multiplexing efficiency, compared to
the rigid SDH/SONET hierarchy.
As packet-based technologies are standardized
to support the capabilities and functionalities
needed for Packet-based Transport Networks
(PTNs) services and operations through combining state-of-the-art technology with the
operational experience and practices of

2015-10-22
KEYMILE 2015

MPLSbased

White Paper
MPLS-TP in Mission-Critical Systems

Glossar

The need for an MPLS Transport


Profile

Attribute

IP/MPLS

Connection
mode

Connection less

Connectionoriented

Label
switched path

Unidirectional

Uni/Bidirectional
(co-routed)

Control plane

Mandatory

Optional (NMS
provisioning
preferred)

OAM

Out-of-band OAM

In-band OAM

Protection
switching

Control plane
dependency
(> 50 ms)*

Data plane
switching
(< 50 ms)

Complexity
level

High

Low

Operational
skill set

Familiar to routing
engineers

Familiar to transport engineers

Standardization
body

IETF

IETF

MPLS Transport Profile (MPLS-TP), as defined


by IETF RFC 5921, supports the operational
models and capabilities of PTNs, including
explicit provisioned bidirectional connectionoriented paths, protection and restoration mechanisms, comprehensive Operations, Administration and Managent (OAM) functions and
network operation in the absence of a dynamic
control plane or IP forwarding support.
MPLS-TP main objectives, as a new standard,
are:
To enable MPLS to be deployed in a PTN

Figure 2: IP/MPLS vs. MPLS-TP



*IP/MPLS FRR mechanisms could achieve

sub-50 ms switchover but only for unidirectional

LSPs based on complex control protocols.

and operated in a similar manner to existing


TDM-based transport technologies (SDH,
SONET).
To enable MPLS to support packet transport

Therefore, not all IP/MPLS capabilities are


required or consistent with transport network
operations and, hence, there is a strong market
need to standardize an MPLS-based technology to meet the requirements for PTNs.

IP/MPLS
P
IP forwarding
P
Penultimate hop popping
P
Equal cost multi paths
P
Label merge

services (e.g. point-to-point, any-to-any) with


a similar degree of predictability, reliability
and OAM to that found in existing TDMbased transport networks.

TP EXTENSIONS

MPLS-TP
P
MPLS forwarding
P
Connection-oriented
P
Co-routed bidirectional LSP

Figure 3: MPLS-TP overview

2015-10-22
KEYMILE 2015

P
Static provisioning
P
In-band OAM
P
End-to-end OAM
driven protection switching
(sub-50 ms)

White Paper
MPLS-TP in Mission-Critical Systems

Data Plane
MPLS forwarding
Connection-oriented bidirectional P2P LSPs
Connection-oriented unidirectional P2MP LSPs
No Penultimate Hop Popping (PHP)
No LSP merging
Pseudo wire (SS-PW, MS-PW)
No routing required

Control Plane
NMS provisioning option (preferred)
GMPLS control plane option

MPLS-TP
OAM
In-band OAM channel (G-ACh)
Extended BFD proactive Connectivity Check (CC)
and Remote Defect Indicator (RDI)
On-demand Connectivity Verification (CV)
Alarm suppression/fault indication (AIS),
Performance monitoring (LM, DM)

Resiliency
Sub-50 ms protection switchover
Linear protection 1+1, 1:1, 1:N

Figure 4: MPLS-TP as a subset of IP/MPLS

Advantanges of MPLS-TP

addition, MPLS-TP supports the logical/physical


separation of the control and management
planes from the data plane. That is, the forwarding of data (including recovery actions) is
independent of the control or management
plane used to configure the MPLS-TP layer
network.

Being connection-oriented with predictable


behaviour, MPLS-TP is optimized for transport
networks with similar features as SDH/SONET.
It is less complex and more cost effective than
IP/MPLS as it allows operation without control
protocols. It is a subset of IP/MPLS but it brings
the following additional functionality:

Statically configured connections are a very


important aspect for a MCS. As MPLS-TP data
plane can operate normally (i.e. forwarding,
OAM, and protection) if the management plane
or control plane that configured the transport
paths fails and, as configuration is stored
non-volatile in each NE, there is no need for
management or control plane to re-configure
transport paths after a e.g. power failure.

Static provisioning (operation possible


without control plane) and co-routed
bidirectional paths.
In-band OAM, performance monitoring,
alarming.
End-to-end OAM driven protection switching.

In-band OAM

Static provisioning

For correct operation of OAM mechanisms, it is


important that OAM packets fate-share with
the data packets. MPLS-TP OAM packets follow
the same path as their corresponding data
packets, and make use of a Generic Associated
Channel (G-ACh) to support Fault, Configura-

MPLS-TP allows for a Pseudo-Wire (PW) or


Label-Switched Path (LSP) to be statically
configured without the support of a dynamic
control plane. This may be achieved by direct
configuration of the Network Element (NE) or
via a Network Management System (NMS). In

2015-10-22
KEYMILE 2015

White Paper
MPLS-TP in Mission-Critical Systems

One active and one standby path with guar-

tion, Accounting, Performance and Security


(FCAPS) functions by carrying packets related
to OAM, a protocol used to coordinate path
protection state, Signaling Communication
Channel (SCC), Management Communication
Channel (MCC) or other packet types in-band
over LSP, PWs or sections.

anteed bandwidth on both paths (1:1).


One active path and a standby path with
shared resources by one or more active
paths (shared protection).
The main characteristics of MPLS-TP resiliency
mechanisms can be summarized as follows:

MPLS-TP supports a comprehensive set of


OAM capabilities to perform fault management
(e.g. fault detection and localization) and
performance monitoring (e.g. packet delay and
loss measurement) for packet transport applications, equivalent to those provided in SDH.

Optimized for linear topologies.


Use in-band OAM mechanisms to detect and
localize network faults.
Include protection state coordination (PSC)
mechanisms to coordinate and trigger protection switching actions in the absence of a

Protection switching

control plane.

MPLS-TP is designed to be consistent with


existing transport network operations and
management models, while providing survivability mechanisms, such as protection switching
and restoration. The functionality provided is
intended to be similar to that found in established SDH/SONET networks that set a high
benchmark for service availability.

Support of revertive and non-revertive behavior


For example, MPLS-TP 1:1 linear protection
provides a fast and simple means to protect
co-routed bidirectional end-to-end LSPs by just
switching traffic to a pre-configured protecting
LSP (also co-routed bidirectional). In case of a
network failure, in-band OAM mechanisms
allow fast failure detection on network links and
PSC protocols ensures end-to-end coordination
of the protected LSP to achieve sub-50 ms
protection switchover. If revertive behavior is
required, a Wait-to-Restore (WTR) time would
trigger the PSC to switch back to the (restored)
working LSP.

Different protection schemes apply to different


deployment topologies and operational
considerations with different levels of resiliency:
Two concurrent traffic paths (1+1).

g
rkin
Wo P
LS

PE

PE
ng

i
tect
Pro P
LS

nt
Clieode
n

Pseudowire
Client signal

Figure 5: MPLS-TP 1:1 Linear protection

2015-10-22
KEYMILE 2015

nt
Clieode
n

White Paper
MPLS-TP in Mission-Critical Systems

Conclusion

Glossary
Abbreviation

Description

AIS

Alarm Indication Signal

BFD

Bidirectional Forwarding Detection

CC

Continuity Check

CV

Connectivity Verication

DM

Delay Measurement

FCAPS

Fault, Conguration, Accounting, Performance and Security

FRR

Fast Re-Route

G-ACh

Generic Associated Channel

MPLS-TP is an evolutionary step for the deployment of PTNs. It provides standardized state-

GMPLS

Generalized MPLS

IETF

Internet Engineering Task Force

of-the-art transport technology for MCS with


the highest reliability (sub-50 ms) and operational simplicity for deterministic usage of
network resources through highly secure and
centralized NMS.

IP

Internet Protocol

IP/MPLS

IP-based MPLS

LM

Loss Measurement

LSP

Label Switched Path

MCC

Management Communication Channel

MCS

Mission Critical System

MPLS

Multiprotocol Label Switching

MPLS-TP

Multiprotocol Label Switching Transport


Profile

MS-PW

Multi-Segment PW

NE

Network Element

NMS

Network Management System

OAM

Operations, Administration &


Management

PE

Provider Edge

PHP

Penultimate Hop Popping

PTN

Packet-based Transport Network

PW

Pseudo-Wire

SCC

Signaling Communication Channel

SDH

Synchronous Digital Hierarchy

SONET

Synchronous Optical Networking

SS-PW

Single-Segment PW

TCO

Total Cost of Ownership

TDM

Time-Division Multiplexing

RDI

Remote Defect Indicator

RFC

Request for Change

RSTP

Rapid Spanning Tree Protocol

TDM

Time-Division Multiplexing

WTR

Wait to Restore

As MCS business organizations plan their


business strategy towards PTNs, MPLS-TP
offers an attractive architectural approach
optimized for transport network operations
leveraging the benefits of existing TDM-based
transport networks while supporting the
growing demand of packet-based services at
lower costs.

2015-10-22
KEYMILE 2015

You might also like