Packet Evolution in Transport Networks: MPLS Transport Profile (MPLS-TP) (IOS Advantage Webinar)

© 2010 Cisco and/or its affiliates. All rights reserved. 1

Packet Evolution in Transport Networks – MPLS Transport Profile (MPLS-TP) José Liste – [email protected] Hari Rakotoranto – [email protected] Santiago Álvarez – [email protected]

April 2012

[email protected] - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 2

•  Industry Dynamics and Motivations for Packet Transport

•  Technology Overview

•  Cisco MPLS-TP

•  Use Cases

•  Network Management


Before we dive in, how familiar am I with MPLS-TP?

A.  Not familiar

B.  Learning the technology and assessing applicability to my environment

C.  Fairly familiar with it and considering potential deployment in the future

D.  Fairly familiar with it, but not planning to deploy for now


Source: Cisco Visual Networkin Index (VNI) www.cisco.com/go/vni

Video

File Sharing

Web / Other Data

Data

Video/Voice Comm / Gaming

•  15 billion networked devices in 2015, up from 7 billion in 2010

•  IP traffic will grow 4-fold from 2010 to 2015 (32% CAGR )

•  Mobile data traffic will grow 26-fold from 2010 to 2015 (92% CAGR )

•  IP traffic will reach an annual run rate of 965.5 Exabytes in 2015 (equivalent to 241 billion DVDs )

•  Mobile was 1% of total IP traffic in 2010, and will be 8% of total IP traffic in 2015


•  Many transport networks still based on SONET/SDH (circuit switching technology)

•  Packet-based growing fast and dominating traffic mix (driven by Video, Mobile, Cloud, application migration to IP)

•  Increased changes in traffic patterns (mobility, cloud)

•  Transport networks migrating to packet switching for Bandwidth efficiency (statistical multiplexing) Bandwidth flexibility (bandwidth granularity, signaling)

Packet Network (MPLS-TP)

Transport Network (SONET/SDH)

Packet Network (IP/MPLS)


  Joint agreement between ITU-T and IETF to develop a transport profile based on MPLS

  Packet transport requirements brought to IETF

  MPLS forwarding, OAM, control plane, management and survivability extended at IETF

Requirements

MPLS transport extensions

MPLS-TP


•  Connection-oriented packet-switching technology

•  Point-to-point (P2P) and point-to-multipoint (P2MP) transport paths

•  Separation of control and management planes from data plane

•  Deployable with or without a control plane

•  Should retain similar operational model of traditional transport technologies

•  Multi-service (IP, MPLS, Ethernet, ATM, FR, etc)

•  Should support bandwidth reservation

•  Support for 1:1, 1:n, 1+1 protection with similar techniques to traditional transport technologies

•  Support for In-band OAM


MPLS Forwarding P2P / P2MP LSP

Pseudowire Architecture OAM

Resilicency GMPLS

MPLS

New extensions based on transport

requirements

Existing functionality meeting transport requirements Existing functionality

prior to MPLS Transport profile

MP2P / MP2MP LSP IP forwarding

ECMP

Transport Profile

•  Extends MPLS to meet packet transport requirements

•  Identifies subset of MPLS supporting traditional transport requirements

•  Data plane Bidrectional P2P and unidirectional P2MP LSP (no LSP Merging) In-band associated channel (G-Ach / GAL)

•  Control plane Static Dynamic (GMPLS)

•  OAM In-band Continuity check, remote defect indication Connectivity verification and route tracing Fault OAM (AIS/LDI, LKR) Performance management

•  Resiliency 50ms switchover Linear protection (1:1, 1+1, 1:N) Ring protection


IP/MPLS (LDP/RSVP-TE/BGP) MPLS-TP (Static/RSVP-TE)

MPLS Forwarding

IPv4 Multicast

IPv4 IPv6

Services (clients)

Transport

MPLS-TP currently focuses on Layer-2/1services

IPv4 VPN

IPv6 VPN VPMS VPWS VPLS


Applicability to Next Generation Network

Dark Fibre / CWDM / DWDM and ROADM

Aggregation Network

Aggregation!

BNG

Business PE

Access! Edge!Aggregatio

n Node

DSL

Ethernet

Core

VoD

Content Network

TV SIP

EMS NMS Portal

AAA Service and Performance Mgmt DHCP,DNS

OAM Subsystem

Multiservice Core!

Core Network

Distribution Node

STB

Corporate

STB

STB

Residential

Corporate

Corporate

Business

Business

Business

Residential

Residential

2G/3G Node

PON

MPLS-TP MPLS-TP IP/MPLS

Option 1: MPLS TP for Aggregation

Option 2: MPLS TP for Aggregation and Access

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 11


  Bi-directional, co-routed LSPs

  Static LSP   QoS

  CC/RDI   On-demand

CV   Route Tracing   AIS/LDI/LKR   CFI (PW

Status)

Forwarding Plane

OAM

  Linear protection (1:1, 1+1, 1:N)

  Reversion   Wait-to-restore

timer

Protection

  Ethernet/VLAN   ATM   TDM   MS-PW

integration with IP/MPLS

Services

  Static   Dynamic

(GMPLS)

Control Plane


•  Point to Point

•  Static or signaled

•  Bidirectional

•  Generally, co-routed (same forward and reverse paths)

•  In-band Generic Associated Channel (G-ACh)

•  Ultimate hop popping (no explicit/implicit null)

•  No equal cost multi-path (ECMP)

•  Contained within a tunnel MPLS-TP LSP

G-ACh MPLS-TP Tunnel


MPLS-TP Tunnel

Protect LSP

G-ACh G-ACh

Working LSP

•  Tunnel holds a working LSP and a protected LSP

Working Protect (optional)

•  LSPs may be configured with a bandwidth allocation

•  Tunnel operationally UP if at least one LSP operationally UP (and not locked out)

•  LSP operationally UP if OAM (Continuity Check) session operationally UP

•  LSP requires static configuration of LSP label imposition (output label and output link)

•  LSP requires static configuration of LSP label disposition (input label)


•  Static configuration of forward and reverse LSP

•  LSP defined using LSP ID Source Node

Source tunnel number Destination Node

Destination tunnel number

LSP number

•  Semantics of source/destination locally significant

•  Static configuration of label swapping (input label, output label and output interface)

•  Static bandwidth reservation (optional)

MPLS-TP LSP

G-ACh MPLS-TP Tunnel

LSP Direction

Input Label

Output Label

Output Interface

Forward 323111 334111 Gi2/1

Reverse 343111 111 Gi2/4


•  In-band OAM packets (fate sharing)

•  OAM functions can operate on an MPLS-TP network without a control plane

•  Extensible framework (fault and performance management specifications ratified already)

•  Independent of underlying technology

•  Independent of PW emulated service


•  OAM capabilities extended using a generic associated channel (G-ACh) based on RFC 5085 (VCCV)

•  A G-ACh Label (GAL) acts as exception mechanism to identify maintenance packets

•  GAL not required for pseudowires (first nibble as exception mechanism)

•  G-ACh used to implement FCAPS (OAM, automatic protection switching (APS), signaling communication channel, management communication channel, etc)

ACH OAM

Payload

GAL Label

Associated Channel Header Generic Associated Channel Label (GAL)

PW Associated Channel Header (ACH)

ACH OAM

Payload

Label PW Label

0 0 0 1 Version

RFC 5586

RFC 5085

13 TC 1 1 Reserved 0 0 0 1 Version Channel Type

LSP

G-ACh

PW G-ACh

Reserved Channel Type


•  Checks paths continuity between end points (no end point identity verification)

•  Uses Bidirectional Forwarding Detection (BFD) over G-ACh without IP/UDP headers

•  BFD operates in asynchronous mode

•  LSP is UP when BFD session is UP

•  Session initiation does not require bootstrapping (LSP Ping)

•  BFD diagnostics field provides remote defect indication (RDI) function

•  BFD initiated using slow start (1s interval, multiplier of 3) with poll/final sequence

BFD CC (Interval x Multiplier)

BFD CC (Interval x Multiplier) Label

ACH

BFD

GAL

Bi-directional, co-routed MPLS-TP LSP

BFD (Down)

BFD (Init)

BFD (Up/Poll)

BFD (Up/Final) BFD (Up)

BFD (Up) BFD (Up) BFD (Up)

P1 PE1 PE2 P2


•  Failure indication sent by local end point to remote end point

•  Sent on direction opposite to failure

•  Uses existing BFD diagnostics field 0 - No Diagnostic

1 - Control Detection Time Expired

3 - Neighbor Signaled Session Down

4 - Forwarding Plane Reset

5 - Path Down

7 - Administratively Down

•  Diagnostics field indicates reason for last change in session state on an end point

Label

ACH

BFD

GAL


BFD (Up / 0) BFD (Up / 0)

P1 PE1 PE2 P2

Oper Up

Oper Up

X

X

BFD (Up / 0) BFD (Up / 0) X BFD (Up / 0) X

BFD (Down / 1) BFD (Down / 3) X

BFD (Down / 1) BFD (Init / 3)

BFD (Down / 1) X


•  Fault notifications to enable alarm suppression and to trigger tunnel protection on end points

•  Three notifications Link Down Indication (LDI) Alarm Indication Signal (AIS)

Lock Report (LKR)

•  AIS signals a failure in the server layer

•  LDI flag in AIS message indicates a fatal/permanent failure in server layer

•  LKR signals an administrative lock on server layer

•  Fault messages generated by mid points

•  Fault messages processed by end points

•  Three messages sent at 1 per sec to set/clear fault then continuous messages sent at a longer interval

P1 PE1 PE2

Label

ACH Fault (LKR)

GAL


P2

Oper Down

AdminDown

Label

ACH Fault (LDI)

GAL

LKR LKR LKR

LKR

LKR

LDI LDI LDI

LDI

LDI

1 per sec

1 per fault refresh timer (default 20s)

X X


Unidirectional Black hole

RDI

RDI

Unidirectional Fault

LDI

Bidirectional Fault

LDI LDI

Unidirectional Shutdown

LDI LKR

Oper Down

Oper Down

Oper Down

Oper Down

Oper Down

Oper Up

Oper Up

Oper Up

Oper Down

AdminDown

Oper Down

Oper Down

Oper Down

Oper Down

Oper Down

Oper Down

MPLS-TP LSP Data link

X X

X

X

X X


•  Uses LSP Ping over G-ACh for both CV and route tracing

•  LSP Ping packets use IP/UDP encapsulation used in IP/MPLS

•  IP forwarding NOT required

•  Only reply mode via control channel (G-ACh - 4) possible

•  Only end points can send requests

•  End points and mid points can send replies

•  End points use MPLS TTL expiration to send a request to a mid point (route tracing)

•  New FECs defined for static LSP and static pseudowire

•  CV can be performed on an LSP regardless of its state (up/down)

Label

ACH LSP Ping

GAL


LSP Ping Echo Request

TTL=255

P1 PE1 PE2 P2

LSP Ping Echo Reply TTL=255

LSP Ping Echo Request

TTL=255 LSP Ping Echo Reply TTL=255


•  Enables performance metrics for packet loss, delay and delay variation

•  Defines two protocols Loss Measurement (LM) Delay Measurement (DM)

•  Measuring capabilities One-way / two-way delay Loss - Direct (actual data) Loss - Inferred (test data) Delay variation Throughput

•  Supports NTP and IEEE 1588 timestamps


TDM / ATM OAM

MPLS Service OAM (VCCV/LSP Ping/BFD)

IETF MPLS-TP OAM (LSP Ping, BFD, LDI/AIS/LKR, etc.)

P PE PE P P P PE

ATM/TDM

ATM/TDM PW

MPLS-TP IP/MPLS

IETF IP/MPLS OAM (LSP Ping/BFD)

Common OAM

framework IETF – Homogenous OAM frameworks at all layers

TDM / ATM OAM


ITU-T MPLS-TP OAM Proposal (G.8113.1/Gtpoam – Y.1731 based)


P PE PE P P P PE

ATM/TDM

ATM/TDM PW

MPLS-TP IP/MPLS

Operational complexity / inefficiency

ITU-T – Heterogeneous OAM frameworks at transport layer

LSP LSP

LSP LSP

BSC/RNC

BSC/RNC

Mobi

le Ba

ckha

ul (2

G/3G

) Mo

bile

Back

haul

(2G/

3G)


•  Relies on a disjoint working and a disjoint protect path between two nodes

•  Enables 1:1, 1:N, 1+1 protection

•  Protection switching can be triggered by

Detected defect condition (LDI/AIS, LKR) Administrative action (lockout) Far end request (lockout) Server layer defect indication (LOS) Revertive timer (wait-to-restore)

•  New protocol defined for protection state coordination (PSC)

PE1 PE2

P2

P1

Working LSP (Up, Active)

Protect LSP (Up, Standby)

PE1 PE2

P2

P1

Working LSP (Down, Standby)

Protect LSP (Up, Active)

Working LSP (Up, Active)

Protect LSP (Up, Standby)

Working LSP (Down, Standby)


Before Failure

During Failure


•  Revertive mode always selects working LSP as active path if operationally up

•  Wait-to-restore (WTR) timer delays selection of working LSP as active path after protection trigger disappears (fault, lockout)

•  Timer prevent excessive swapping between working and protect LSP due to intermittent defect

•  Large WTR timer can provide non-revertive behavior (maximum WTR timer ~68 years)

•  Restoration (selecting Working LSP as Active) should not result in packet loss

PE1 PE2

P2

P1

Working LSP (Up, Standby)


Working LSP (Up, Standby)


WRT timer WRT timer


•  MPLS-TP does not introduce any changes to MPLS QoS

•  Coarse QoS

•  Ingress node enforces contract (conditioning) and performs aggregate marking on incoming traffic

•  Packet header encodes packet class (code point)

•  Class indicates service required at each hop (per-hop behavior)

Shim Header

Traffic Class (TC) / Experimental (EXP) – 3 bits

TC/ EXP – 3 bits Label – 20 bits

E-LSP

L-LSP

Traffic Conditioning   Classification

  Marking

  Policing

  Shaping

Per-Hop Behavior   Classification

  Queuing

  Queue Mgmt

P1 PE1 PE2 P2


MPLS-TP currently focuses on

Layer-2/1services

IP/MPLS (LDP / RSVP-TE / BGP)

MPLS-TP (Static / RSVP-TE)

MPLS Forwarding

IPv4 IPv6

Services (clients)

Transport

IPv4 VPN

IPv6 VPN VPMS VPWS VPLS

•  Existing pseudowire architecture applies to MPLS-TP

•  LSPs typically aggregate multiple services

•  As usual, pseudowires can be signaled or established via manual configuration

LSP

PW1

PW2

PW3


PPP/HDLC

Unmuxed UNI

Ethernet Private Line (EPL)

Ethernet Virtual Private Line (EVPL)

Muxed UNI

Ethernet

Ethernet Private LAN (EPLAN)

Ethernet Virtual Private LAN (EVPLAN)

Muxed UNI

Unmuxed UNI

ATM

Muxed UNI

AAL5 over Pseudowire

Cell Relay with Packing over Pseudowire

Muxed UNI

TDM

Muxed UNI

Circuit Emulation over PSN (CESoPSN)

Structure Agnostic TDM over Packet (SAToP)

Muxed UNI

Virtual Private Wire Service (VPWS) Virtual Private LAN Service (VPLS)


If I were to deploy MPLS-TP, I’d likely implement the following services

(multiple choice)

A.  Point-to-Point Ethernet (E-LINE)

B.  Multipoint Ethernet (E-LAN)

C.  ATM

D.  TDM

E.  Other



Aggregation Access Core Aggregation Access

•  Multi-segment pseudowires (MS-PW) enable layer-2/-1 services over a combined MPLS-TP and IP/MPLS infrastructure

•  S-PE switches traffic between a static and a dynamic segment

•  MPLS-TP domain uses static LSP as PSN tunnel and static PW segment

•  IP/MPLS domain uses signaled LSP (LDP or RSVP-TE) as PSN tunnel and signaled PW segment

T-PE S-PE S-PE T-PE

Static PW Static Tunnel

Signaled PW Signaled Tunnel

Static PW Static Tunnel


•  Static MPLS-TP provides a simpler migration path for legacy transport networks

•  Generalized MPLS (GMPLS) offers a proven control plane for MPLS-TP networks

•  A control plane increases network intelligence

Dynamic services Greater efficiency, resiliency and scalability

•  GMPLS provides a generalized control plane for hierarchical traffic engineering

Legacy transport (circuit switched)

Packet transport (static / no control plane)

Packet transport (dynamic control plane)


Would I be interested in a dynamic control plane for a packet transport network?

A.  Yes

B.  No, I'd rather operate a completely static transport network



Access Aggregation Distribution/Edge

ASR903

7600

ASR9000

CPT 600 / 200 / 50

Cisco Prime

Under consideration

Network Management System


Area Functionality

Forwarding Static Bi-directional LSP

OAM

BFD CC On demand CV/Trace (LSP Ping Trace)

Fault OAM (AIS/LDI, LKR) Pseudowire status notification

VCCV (Ping/Trace)

Protection Linear (1:1)

Lockout Pseudowire redundancy

Bandwidth Management / QoS Admission Control MPLS DiffServ (E-LSP)

Services

Ethernet point-to-point Ethernet multipoint

ATM TDM

IP

Integration with IP/MPLS static/dynamic PW switching (MS-PW)


mpls tp router-id 172.16.255.1 ! bfd-template single-hop DEFAULT interval min-tx 10 min-rx 10 multiplier 3 ! interface Tunnel-tp10 description PE1<->PE3 no ip address no keepalive tp bandwidth 100000 tp destination 172.16.255.3 bfd DEFAULT working-lsp out-label 2100 out-link 201 in-label 321100 lsp-number 0 protect-lsp out-label 314101 out-link 204 in-label 341101 lsp-number 1 ! ! interface GigabitEthernet2/1 ip address 172.16.0.1 255.255.255.252 mpls tp link 201 ipv4 172.16.0.2 ip rsvp bandwidth percent 100 !

Tunnel definition

Working LSP

Protect LSP

TP LSP (Working)

TP LSP (Protect)

MPLS-TP

(tunnel-tp10) Static TP LSP

In label (w): 321100 Out label (w): 2100

In label (p): 341101 Out label (p): 314101

PE1 PE3

PE2

PE1


interface tunnel-tp10 description PE3<->PE1 bandwidth 100000 destination 172.16.255.4 bfd min-interval 15 multiplier 2 ! working-lsp in-label 2200 out-label 321100 out-link 701 ! protect-lsp in-label 2201 out-label 323201 out-link 700 ! ! rsvp interface GigabitEthernet0/0/0/0 bandwidth 10000000 ! ! mpls traffic-eng interface GigabitEthernet0/0/0/0 tp link 700 next-hop ipv4 172.16.0.1 ! tp node-id 172.16.255.2 ! !

PE3

Tunnel definition

Working LSP

Protect LSP

TP LSP (Working)

TP LSP (Protect)

MPLS-TP



In label (p): 2201 Out label (p): 323201

PE1 PE3

PE2


interface GigabitEthernet2/1 ip address 172.16.0.9 255.255.255.252 mpls tp link 201 ipv4 172.16.0.10 ip rsvp bandwidth percent 100 ! interface GigabitEthernet2/2 ip address 172.16.0.18 255.255.255.252 mpls tp link 202 ipv4 172.16.0.17 ip rsvp bandwidth percent 100 ! mpls tp lsp source 172.16.255.1 tunnel-tp 11 lsp protect destination 172.16.255.4 tunnel-tp 11 forward-lsp bandwidth 100000 in-label 323111 out-label 334111 out-link 201 reverse-lsp bandwidth 100000 in-label 343111 out-label 111 out-link 202 !

Forward LSP

Reverse LSP


rsvp interface GigabitEthernet0/0/0/0 bandwidth 10000000 ! interface GigabitEthernet0/0/0/1 bandwidth 10000000 ! ! mpls traffic-eng interface GigabitEthernet0/0/0/0 tp link 700 next-hop ipv4 172.16.0.1 ! interface GigabitEthernet0/0/0/1 tp link 701 next-hop ipv4 172.16.0.6 ! mid PE1-PE3 lsp-number 0 source 172.16.255.1 tunnel-id 10 destination 172.16.255.3 tunnel-id 10 forward-lsp bandwidth 1000000 in-label 321100 out-label 321100 out-link 700 ! reverse-lsp bandwidth 1000000 in-label 2200 out-label 321100 out-link 701 ! ! ! !

PE2

TP LSP (Working)

TP LSP (Protect)

MPLS-TP


PE1 PE3

PE2

Forward LSP

Reverse LSP




! pseudowire-static-oam class DEFAULT ! pseudowire-class PW-Tunnel-tp10 encapsulation mpls protocol none preferred-path interface Tunnel-tp10 status protocol notification static DEFAULT ! interface GigabitEthernet2/6 description CONNECTS TO CE1 no ip address service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric xconnect 172.16.255.3 10 encapsulation mpls \\ manual pw-class PW-Tunnel-tp10 mpls label 9110 9310 no mpls control-word ! !

MPLS-TP Ethernet

(tunnel-tp10)

Ethernet

E-LINE

PE PE Static pseudowire

E-LINE

PW Id 10

CE2

PE1 PE3

PE2

CE1

VLAN 10 VLAN 20

Local label: 9110

Local label: 9310

Static TP LSP

PE1

TP LSP (Working)

TP LSP (Protect)

Static pseudowire

Pseudowire/Tunnel

association


! interface GigabitEthernet0/0/0/18 description CONNECTS CE2 ! interface GigabitEthernet0/0/0/18.20 l2transport encapsulation dot1q 20 rewrite ingress tag pop 1 symmetric ! l2vpn pw-class SS-PW-Tunnel-tp10 encapsulation mpls transport-mode vlan preferred-path interface tunnel-tp 10 ! ! xconnect group PE3 p2p PE1-PE3 interface GigabitEthernet0/0/0/18.20 neighbor 172.16.255.1 pw-id 10 mpls static label local 9310 remote 9110 pw-class SS-PW-Tunnel-tp10 ! ! ! !

MPLS-TP Ethernet

(tunnel-tp10)

Ethernet

E-LINE

PE PE Static pseudowire

E-LINE

PW Id 10

CE2

PE1 PE3

PE2

CE1

VLAN 10 VLAN 20

Local label: 9110

Local label: 9310

Static TP LSP

TP LSP (Working)

TP LSP (Protect)

Static pseudowire

Pseudowire/Tunnel

association


•  Independent test report to be posted soon

•  ASR 9000, CPT 600 and 7600

•  Comprehensive OAM (CC/RDI, AIS/LDI, LKR, LSP Ping/Trace)

•  1:1 revertive linear protection with lockout

•  E-LINE over combined MPLS-TP and IP/MPLS transport with end-to-end status notification using MS-PW

•  Cisco Prime Network monitoring




Aggregation Access Core Aggregation Access

T-PE S-PE S-PE S-PE

MPLS-TP

Metro

PE PE

MPLS-TP PE PE

SONET/SDH Metro Replacement

NodeB / eNodeB

RAN Packet Core

Mobile Backhaul

MPLS Extension to Access/Aggregation

RNC MME

SGW


IP/ MPLS Core

IP/ MPLS Core

IP/MPLS

Residential

STB

Business

Corporate

Mobile 2G/3G / LTE

T1/E1 - STMx SONET/SDH

Residential

STB

Business

Corporate

Mobile 2G/3G / LTE

MPLS-TP

VPWS

•  TDM/ATM based access •  No statistical multiplexing •  Static Provisioning •  50-ms Resiliency •  Ring or Point to Point

topology •  NMS Management •  SONET/SDH phy stats

•  Ethernet Packet based Transport

•  Static Provisioning •  50-ms Resiliency •  Ring, Mesh, P2P topology •  NMS Management •  SONET/SDH phy stats on

IPoDWDM

SONET/SDH

MPLS-TP

ADMADM

ADMADM

ADMADM

L2/L3 VPN

IP/MPLS

L2/L3 VPN


If I were to deploy MPLS-TP, I’d be migrating from

(Multiple choice)

A.  SONET/SDH

B.  ATM

C.  Native Ethernet

D.  Other



Prime for IP Next Generation Network

Cisco Prime IP NGN Suite Prime Central Prime Fulfillment Prime Network Prime Optical Prime Performance Manager

Infrastructure Management Prime Address Management (Address Management and Configuration) Prime Network Registrar (IPv6 and scalable DNS and DHCP Servers) Prime Access Registrar (Authentication, Authorization, Accounting)

Architectures MPLS and Carrier Ethernet (Core, Distribution, Access) Ran Backhaul Next Generation IPv6 Residential Services Optical Transport


  Complete device management (Physical and Logical) including single-click upgrades   Support point-and-click provisioning for Packet Transport including TP Tunnel Path Computation   Alarm De-duplication, Alarm Reduction and Correlation   Advanced troubleshooting tools (overlay, service view) enable MTTR reduction   E-OAM Monitoring and Configuration for services running over MPLS-TP   Extensive collection of statistic including Y.1731 for Ethernet Performance Management   Support released every other month with updated hardware support and releases

Logical and Physical Inventory

Fault Isolation Service

View

Proactive Monitoring

MPLS-TP Creation Wizard

ASR 9000 7600

ASR 903

CPT 50, CPT200, CTP600



•  Traffic growth, device proliferation and cloud driving demand for packet services

•  MPLS emerging as technology of choice to implement packet transport

•  MPLS-TP extends MPLS to support operational model of traditional transport networks

•  New IETF extensions part of MPLS architecture

•  Cisco offers a complete solution for IP NGN aggregation with MPLS-TP as a transport alternative


•  Implementing MPLS Transport Profile (IOS XR) http://cisco.com/en/US/docs/routers/asr9000/software/asr9k_r4.2/mpls/configuration/guide/b_mpls_cg42asr9k_chapter_0110.html

•  MPLS Transport Profile Configuration Guide (IOS) http://cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_transport_profile.html

•  Cisco Prime for IP Next Generation Networks http://cisco.com/go/prime

•  Cisco SP360: Service Provider Blog http://blogs.cisco.com/tag/mpls-tp/

•  Cisco ASR9000 http://cisco.com/go/asr9000

•  Cisco ASR903 http://cisco.com/en/US/products/ps11610/index.html


General

Description Focus Area IETF RFC or WG documents

JWT document JWT Report on MPLS-TP Architectural Considerations

First milestone on MPLS-TP Joint work by IETF/ITU-T

RFC 5317

IAB document Uncoordinated Protocol Dev. Considered Harmful

Inter-SDO coordination RFC 5704

General MPLS-TP Terminologies Terminologies draft-ietf-mpls-tp-rosetta-stone

Requirements and Frameworks

Description and Focus Area IETF RFC or WG documents

Requirements

General MPLS-TP Requirements. RFC 5654

MPLS-TP OAM Requirements RFC 5860

MPLS-TP Network Management Requirements RFC 5951

Frameworks MPLS-TP Architecture Framework RFC 5921

MPLS-TP Network Management Framework RFC 5950

MPLS-TP OAM Architecture Framework RFC 4378

MPLS-TP Survivability Framework RFC 6372

MPLS-TP Control Plane Framework RFC 6373

MPLS-TP OAM Analysis draft-ietf-mpls-tp-oam-analysis

IETF MPLS-TP General Definitions


MPLS-TP Protocols for Forwarding and Protection Function IETF RFC or WG documents

Data Plane MPLS-TP Identifiers conformant to existing ITU and compatible with existing IP/MPLS

RFC 6370

MPLS Label Stack Entry: "EXP" renamed to "Traffic Class"

RFC 5462

MPLS Generic Associated Channel for In-band OAM and control

RFC 5586

In-Band Data Communication for the MPLS-TP

RFC 5718

MPLS TP Data Plane Architecture RFC 5960

MPLS-TP UNI-NNI RFC 6215

Protection MPLS-TP Linear Protection RFC 6378

MPLS-TP MIB Management Function IETF RFC or WG documents

Management MPLS-TP MIB management overview draft-ietf-mpls-tp-mib-management-overview

IETF MPLS-TP Data Plane, Protection Definitions


MPLS-TP Fault Management (FM) OAM Functions OAM Functions Protocol Definitions IETF WG documents

Proactive FM OAM Functions

Continuity Check (CC) Bidirectional Forwarding Detection (BFD) extensions

RFC 6428

Remote Defect Indication (RDI) Bidirectional Forwarding Detection (BFD) extensions

Alarm Indication Signal (AIS) AIS message under G-Ach RFC 6427 Link Down Indication (LDI) Flag in AIS message Lock Report (LKR) LKR message under G-Ach Config MPLS-TP OAM using LSP Ping LSP-Ping draft-ietf-mpls-lsp-ping-mpls-tp-

oam-conf

On demand FM OAM Functions

Continuity Verification (CV) LSP Ping and BFD Extensions RFC 6426

Loopback (LBM/LBR) 1) In-band Loopback in G-Ach or 2) LSP Ping extensions

RFC 6435

Lock Instruct (LI) In-band Lock messages in G-ACh

IETF MPLS-TP OAM (FM and PM) Definitions

MPLS-TP Performance Management (PM) OAM Functions OAM Functions Protocol definitions IETF WG documents

Proactive PM OAM Functions and On demand PM OAM Functions

Packet loss measurement (LM) LM and DM query messages RFC 6374 Packet delay measurement (DM) LM and DM query messages Throughput measurement Supported by LM Delay Variation measurement Supported by DM



MPLS-TP

Global ID (operator) 4 octets (decimal) – AS Number Default: 0 (non-global) Global scope

Router ID (Node ID) 4 octets (decimal) - Loopback scope: Global ID Link Number (Interface Number)

4 octets (decimal) scope: Node ID

Tunnel Number 2 octets (decimal) Scope: Node ID

LSP Number 2 octets (decimal) Default: 0 (Working), 1 (Protect) Scope: Tunnel ID

LSP ID Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num::LSP_Num Scope: Global ID

Tunnel ID Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num Scope: Global ID


•  Static PWs require in-band status notification (no LDP notification

•  Existing PW Status TLV sent over G-ACh

•  Three messages sent at 1 per sec to set/clear fault then continuous messages sent at a longer interval

BFD CC (Interval x Multiplier)

BFD CC (Interval x Multiplier) Label

ACH OAM Msg (Status)


P PE PE P CE CE

1 per sec

1 per refresh timer (default 30s)

Static PW Status Static PW Status Static PW Status

Static PW Status

Static PW Status


Ethernet Service OAM (CFM/Y.1731)


IETF MPLS-TP OAM (LSP Ping, BFD, LDI/AIS/LKR, etc.)

P PE PE P P P PE

E-Line

Ethernet PW

MPLS-TP IP/MPLS


Common OAM

framework IETF – Homogenous OAM frameworks at all layers

Ethernet Service OAM (CFM/Y.1731)


ITU-T MPLS-TP OAM Proposal (G.8113.1/Gtpoam – Y.1731 based)


P PE PE P P P PE

E-Line

Ethernet PW

MPLS-TP IP/MPLS

Operational complexity / inefficiency

ITU-T – Heterogeneous OAM frameworks at transport layer

LSP LSP

LSP LSP

Thank you.