Packet Evolution in Trensport Networks Mpls-tp PacketEvolution_Webinar

7/27/2019 Packet Evolution in Trensport Networks Mpls-tp PacketEvolution_Webinar

1/61

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


2/61

[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-TPUse Cases

Network Management


3/61


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

A. Not familiarB. Learning the technology and assessing

applicability to my environmentC. Fairly familiar with it and considering potential

deployment in the future

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


4/61


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

Video

FileSharing

Web / OtherData

Data

Video/VoiceComm / Gaming

15 billion networkeddevices in 2015, up from 7billion in 2010

IP traffic will grow 4-foldfrom 2010 to 2015 (32%CAGR )

Mobile data traffic will grow26-fold from 2010 to 2015(92% CAGR )

IP traffic will reach anannual run rate of965.5Exabytes in 2015

(equivalent to 241 billionDVDs )

Mobile was 1% of total IPtraffic in 2010, and will be8% of total IP traffic in2015


5/61


Many transport networks still based on SONET/SDH (circuitswitching 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 forBandwidth efficiency (statistical multiplexing)

Bandwidth flexibility (bandwidth granularity, signaling)

Packet Network(MPLS-TP)

Transport Network(SONET/SDH)

Packet Network

(IP/MPLS)


6/61


Joint agreement between ITU-T and IETF to develop atransport profile based onMPLS

Packet transport requirementsbrought to IETF

MPLS forwarding, OAM,control plane, managementand survivability extended at

IETF

Requirements

MPLS transport

extensions

MPLS-TP


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

Connection-oriented packet-switching technology Point-to-point (P2P) and point-to-multipoint (P2MP)

transport paths

Separation of control and management planesfrom 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 ForwardingP2P / P2MP LSP

Pseudowire Architecture

OAMResilicency

GMPLS

MPLS

Newextensionsbased on

transportrequirements

Existing functionality meetingtransport requirementsExisting functionality

prior to MPLS Transportprofile

MP2P / MP2MP LSPIP forwarding

ECMP

Transport Profile

Extends MPLS to meet packet transportrequirements

Identifies subset of MPLS supportingtraditional transport requirements

Data planeBidrectional P2P and unidirectional P2MP LSP (noLSP Merging)

In-band associated channel (G-Ach / GAL)

Control planeStatic

Dynamic (GMPLS)

OAMIn-band

Continuity check, remote defect indication

Connectivity verification and route tracingFault OAM (AIS/LDI, LKR)

Performance management

Resiliency50ms 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

VPNVPMS VPWS VPLS



Applicability to Next Generation Network

Dark Fibre / CWDM / DWDM and ROADM

AggregationNetwork

Aggregation!

BNG

BusinessPE

Access! Edge!Aggregatio

n Node

DSL

Ethernet

Core

VoD

Content Network

TV SIP

EMS NMSPortal

AAA Service and Performance MgmtDHCP,DN

S

OAM Subsystem

Multiservice Core!

CoreNetwork

DistributionNode

STB

Corporate

STB

STB

Residential

Corporate

Corporat

e

Business

Business

Business

Residential

Residential

2G/3GNode

PON

MPLS-TPMPLS-TP IP/MPLS

Option 1: MPLS TP for Aggregation

Option 2: MPLS TP for Aggregation and Access



Bi-directional,co-routedLSPs

Static LSP QoS

CC/RDI On-demand

CV Route TracingAIS/LDI/LKR CFI (PW

Status)

Forwarding

Plane

OAM

Linearprotection (1:1,

1+1, 1:N) Reversion Wait-to-restore

timer

Protection

Ethernet/VLANATM TDM MS-PW

integration withIP/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-TPLSP

G-AChMPLS-TPTunnel


14/61


MPLS-TPTunnel

ProtectLSP

G-AChG-ACh

WorkingLSP

Tunnel holds a working LSP and aprotected LSP

Working

Protect (optional)

LSPs may be configured with a bandwidthallocation

Tunnel operationally UP if at least oneLSP operationally UP (and not locked out)

LSP operationally UP if OAM (ContinuityCheck) session operationally UP

LSP requires static configuration of LSPlabel imposition (output label and output

link) LSP requires static configuration of LSP

label disposition (input label)


15/61


Static configuration of forward and reverseLSP

LSP defined using LSP IDSource Node

Source tunnel number

Destination Node

Destination tunnel numberLSP number

Semantics of source/destination locallysignificant

Static configuration of label swapping(input label, output label and outputinterface)

Static bandwidth reservation (optional)

MPLS-TPLSP

G-AChMPLS-TPTunnel

LSPDirection

InputLabel

OutputLabel

OutputInterface

Forward 323111 334111 Gi2/1

Reverse 343111 111 Gi2/4


16/61


In-band OAM packets (fate sharing) OAM functions can operate on an MPLS-TP network without a

control plane

Extensible framework (fault and performance managementspecifications ratified already)

Independent of underlying technology Independent of PW emulated service


17/61


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

A G-ACh Label (GAL) acts as exception mechanism to identify maintenancepackets

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 AssociatedChannel Header(ACH)

ACH

OAMPayload

Label

PW Label0 0 0 1 Version

RFC 5586

RFC 5085

13 TC 11

Reserved0 0 0 1 Version Channel Type

LSP

G-ACh

PWG-AChReserved Channel Type


18/61


Checks paths continuity between endpoints (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 remotedefect 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)

P1PE1 PE2P2


19/61


Failure indication sent by local end point toremote 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 lastchange in session state on an end point

Label

ACH

BFD

GAL


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

P1PE1 PE2P2

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


20/61


Fault notifications to enable alarm suppressionand to trigger tunnel protection on end points

Three notificationsLink 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 serverlayer

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 alonger interval

P1PE1 PE2

Label

ACH

Fault(LKR)

GAL


P2

Oper

Down

Admin

Down

Label

ACH

Fault(LDI)

GAL

LKRLKR

LKR

LKR

LKR

LDILDI

LDI

LDI

LDI

1 per sec

1 per faultrefresh timer(default 20s)

X

X


21/61


UnidirectionalBlack hole

RDI

RDI

UnidirectionalFault

LDI

BidirectionalFault

LDILDI

UnidirectionalShutdown

LDILKR

OperDown

OperDownOperDown OperDown

OperDown

OperUp

OperUp

OperUp

OperDown

AdminDown

OperDown

OperDown

OperDown

OperDown

OperDown

OperDown

MPLS-TP LSPData link

XX

X

X

XX


22/61


Uses LSP Ping over G-ACh for both CVand route tracing

LSP Ping packets use IP/UDPencapsulation 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 tosend a request to a mid point (routetracing)

New FECs defined for static LSP andstatic pseudowire

CV can be performed on an LSPregardless of its state (up/down)

Label

ACH

LSPPing

GAL


LSP PingEcho Request

TTL=255

P1PE1 PE2P2

LSP Ping

Echo ReplyTTL=255

LSP PingEcho Request

TTL=255 LSP PingEcho ReplyTTL=255


23/61


Enables performance metrics for packet loss, delay and delay variation Defines two protocols

Loss Measurement (LM)

Delay Measurement (DM)

Measuring capabilitiesOne-way / two-way delay

Loss - Direct (actual data)

Loss - Inferred (test data)

Delay variation

Throughput

Supports NTP and IEEE 1588 timestamps


24/61


TDM / ATM OAM

MPLS Service OAM(VCCV/LSP Ping/BFD)

IETF MPLS-TP OAM

(LSP Ping, BFD, LDI/AIS/LKR, etc.)

PPE PEP PP PE

ATM/TDM

ATM/TDM PW

MPLS-TP IP/MPLS

IETF IP/MPLS OAM

(LSP Ping/BFD)

CommonOAM

framework

IETF Homogenous OAM frameworks at all layers

TDM / ATM OAM


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

IETF IP/MPLS OAM(LSP Ping/BFD)

PPE PEP PP 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

MobileBackhaul

(2G/3G)

Mobile

Backhaul(2G/3G

)


25/61


Relies on a disjoint working and adisjoint protect path between twonodes

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

Protection switching can betriggered byDetected 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 protectionstate coordination (PSC)

PE1 PE2

P2

P1

Working LSP(Up,Active)

ProtectLSP(Up, Standby)

PE1 PE2

P2

P1

Working LSP(Down, Standby)

ProtectLSP(Up,Active)

Working LSP(Up,Active)

ProtectLSP(Up, Standby)

Working LSP(Down, Standby)


Before Failure

During Failure


26/61


Revertive mode always selectsworking LSP as active path ifoperationally up

Wait-to-restore (WTR) timer delaysselection of working LSP as activepath after protection triggerdisappears (fault, lockout)

Timer prevent excessive swappingbetween working and protect LSPdue 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 packetloss

PE1 PE2

P2

P1

Working LSP(Up, Standby)


Working LSP(Up, Standby)


WRT timerWRT timer


27/61


MPLS-TP does not introduceany changes to MPLS QoS Coarse QoS Ingress node enforces contract

(conditioning) and performsaggregate marking onincoming traffic

Packet header encodes packetclass (code point)

Class indicates servicerequired at each hop (per-hopbehavior)

Shim Header

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

TC/ EXP 3 bitsLabel 20 bits

E-LSP

L-LSP

Traffic Conditioning

Classification Marking Policing Shaping

Per-Hop Behavior

Classification Queuing Queue Mgmt

P1PE1 PE2P2


28/61


MPLS-TP currentlyfocuses on

Layer-2/1services

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

MPLS-TP (Static / RSVP-TE)

MPLS Forwarding

IPv4 IPv6

Services (clients)

Transport

IPv4VPN

IPv6VPN

VPMS VPWS VPLS

Existing pseudowirearchitecture applies to MPLS-TP

LSPs typically aggregatemultiple services

As usual, pseudowires can besignaled or established viamanual configuration

LSP

PW1

PW2

PW3


29/61


Unmuxed UNI

Ethernet Private

Line (EPL)

Ethernet VirtualPrivate Line (EVPL)

Muxed UNI

Ethernet

Ethernet PrivateLAN (EPLAN)

Ethernet Virtual

Private LAN (EVPLAN)

MuxedUNI

UnmuxedUNI

ATM

Muxed UNI

AAL5 over Pseudowire

Cell Relay with Packingover Pseudowire

Muxed UNI

TDM

Muxed UNI

Circuit Emulation overPSN (CESoPSN)

Structure Agnostic TDMover Packet (SAToP)

Muxed UNI

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


30/61


If I were to deploy MPLS-TP, Id likely implement the followingservices

(multiple choice)

A. Point-to-Point Ethernet (E-LINE)B. Multipoint Ethernet (E-LAN)C. ATMD. TDME. Other


31/61



AggregationAccess

CoreAggregation 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 PWStatic Tunnel

Signaled PWSignaled Tunnel

Static PWStatic Tunnel


32/61


Static MPLS-TP provides asimpler migration path forlegacy transport networks

Generalized MPLS (GMPLS)offers a proven control plane

for MPLS-TP networksA control plane increases

network intelligenceDynamic servicesGreater efficiency, resiliency and

scalability GMPLS provides a generalized

control plane for hierarchicaltraffic engineering

Legacytransport

(circuitswitched)

Packettransport

(static / nocontrolplane)

Packettransport

(dynamiccontrol plane)


33/61


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

A. YesB. No, I'd rather operate a completely static

transport network


34/61

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


35/61


Access Aggregation Distribution/Edge

ASR903

7600

ASR9000

CPT 600 / 200 / 50

Cisco Prime

Underconsideration

NetworkManagementSystem


36/61


Area FunctionalityForwarding Static Bi-directional LSP

OAM

BFD CCOn 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 / QoSAdmission Control

MPLS DiffServ (E-LSP)

Services

Ethernet point-to-pointEthernet multipoint

ATMTDM

IP

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


37/61


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 PE1PE3

no ip address

no keepalive

tp bandwidth 100000tp destination 172.16.255.3

bfd DEFAULT

working-lsp

out-label 2100 out-link 201

in-label 321100

lsp-number 0

protect-lsp


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

!

Tunneldefinition

Working LSP

Protect LSP

TP LSP (Working)

TP LSP (Protect)

MPLS-TP

(tunnel-tp10)Static TP LSP

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

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

PE1 PE3

PE2

PE1


38/61


interface tunnel-tp10

description PE3PE1

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


!

!

rsvp

interface GigabitEthernet0/0/0/0

bandwidth 10000000

!!

mpls traffic-eng


tp link 700 next-hop ipv4 172.16.0.1

!

tp

node-id 172.16.255.2

!

!

PE3

Tunneldefinition

Working LSP

Protect LSP

TP LSP (Working)

TP LSP (Protect)

MPLS-TP



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

PE1 PE3

PE2


39/61



ip address 172.16.0.9 255.255.255.252

mpls tp link 201 ipv4 172.16.0.10


!


ip address 172.16.0.18 255.255.255.252

mpls tp link 202 ipv4 172.16.0.17


!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


!

Forward LSP

Reverse LSP


40/61


rsvp


bandwidth 10000000

!


bandwidth 10000000

!

!

mpls traffic-eng


tp link 700 next-hop ipv4 172.16.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


!

reverse-lsp

bandwidth 1000000


!

!

!

!

PE2

TP LSP (Working)

TP LSP (Protect)

MPLS-TP


PE1 PE3

PE2

Forward LSP

Reverse LSP




41/61


!

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/6description 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


42/61


!

interface GigabitEthernet0/0/0/18description 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 vlanpreferred-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)

Staticpseudowire

Pseudowire/Tunnel

association


43/61


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/MPLStransport with end-to-end status notification

using MS-PW

Cisco Prime Network monitoring


44/61



45/61



AggregationAccess 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 PacketCore

Mobile Backhaul

MPLS Extension to Access/Aggregation

RNCMME

SGW


46/61


IP/MPLSCore

IP/MPLSCore

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 basedTransport

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


47/61


If I were to deploy MPLS-TP, Id be migrating from(Multiple choice)

A. SONET/SDHB. ATMC. Native EthernetD. Other


48/61



49/61


Prime for IP Next Generation NetworkCisco Prime IP NGN SuitePrime CentralPrime FulfillmentPrime NetworkPrime OpticalPrime Performance Manager

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

ArchitecturesMPLS and Carrier Ethernet(Core, Distribution, Access)Ran BackhaulNext Generation IPv6Residential ServicesOptical Transport


50/61


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 andPhysical

Inventory

Fault Isolation

Service

View

ProactiveMonitoring

MPLS-TP CreationWizard

ASR 9000

7600ASR 903

CPT 50, CPT200,CTP600


51/61



52/61


Traffic growth, device proliferation and cloud driving demand forpacket services

MPLS emerging as technology of choice to implement packettransport

MPLS-TP extends MPLS to support operational model oftraditional 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


53/61


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 Networkshttp://cisco.com/go/prime

Cisco SP360: Service Provider Bloghttp://blogs.cisco.com/tag/mpls-tp/

Cisco ASR9000http://cisco.com/go/asr9000

Cisco ASR903http://cisco.com/en/US/products/ps11610/index.html

IETF MPLS TP General Definitions


54/61


General

Description Focus Area IETF RFC or WG documents

JWT document JWTReport on MPLS-TP Architectural

Considerations

First milestone on MPLS-TP Joint

work by IETF/ITU-T

RFC5317

IAB document Uncoordinated Protocol Dev.Considered Harmful

Inter-SDO coordination RFC5704General 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. RFC5654

MPLS-TP OAM Requirements RFC 5860

MPLS-TP Network Management Requirements RFC 5951

Frameworks MPLS-TP Architecture Framework RFC5921

MPLS-TP Network Management Framework RFC5950

MPLS-TP OAM Architecture Framework RFC4378

MPLS-TP Survivability Framework RFC6372

MPLS-TP Control Plane Framework RFC6373

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

IETF MPLS-TP General Definitions

IETF MPLS TP D t Pl P t ti D fi iti


55/61


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

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

RFC6370

MPLS Label Stack Entry:

"EXP" renamed to "Traffic Class"

RFC5462

MPLS Generic Associated Channel for In-bandOAM and control

RFC5586

In-Band Data Communication for the MPLS-TP RFC5718

MPLS TP Data Plane Architecture RFC5960

MPLS-TP UNI-NNI RFC6215

Protection MPLS-TP Linear Protection RFC6378

MPLS-TP MIB ManagementFunction 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

IETF MPLS TP OAM (FM d PM) D fi iti


56/61


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

Proactive FM OAM

FunctionsContinuity Check (CC) Bidirectional Forwarding Detection

(BFD) extensionsRFC6428

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

Alarm Indication Signal (AIS) AIS message under G-Ach RFC6427

Link Down Indication (LDI) Flag in AIS message

Lock Report (LKR) LKR message under G-AchConfig 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 RFC6426

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

RFC6435

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

IETF MPLS-TP OAM (FM and PM) Definitions

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

Proactive PM OAMFunctions

and

On demand PM

OAMFunctions

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


57/61



58/61


MPLS-TP

Global ID (operator)

4 octets (decimal) AS NumberDefault: 0 (non-global)Global scope

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

4 octets (decimal)scope: Node ID

Tunnel Number2 octets (decimal)Scope: Node ID

LSP Number2 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_NumScope: Global ID

Tunnel ID

Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_NumScope: Global ID


59/61


Static PWs require in-bandstatus notification (no LDPnotification

Existing PW Status TLV sentover G-ACh

Three messages sent at 1 persec to set/clear fault thencontinuous messages sent at alonger interval

BFD CC(Interval xMultiplier)

BFD CC(Interval xMultiplier)Label

ACH

OAM Msg(Status)


PPE PEPCE CE

1 per sec

1 per refreshtimer(default 30s)

Static PW StatusStatic PW StatusStatic PW Status

Static PW Status

Static PW Status


60/61


Ethernet Service OAM(CFM/Y.1731)


IETF MPLS-TP OAM

(LSP Ping, BFD, LDI/AIS/LKR, etc.)

PPE PEP PP PE

E-Line

Ethernet PW

MPLS-TP IP/MPLS

IETF IP/MPLS OAM

(LSP Ping/BFD)

CommonOAM

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)

IETF IP/MPLS OAM(LSP Ping/BFD)

PPE PEP PP PE

E-Line

Ethernet PW

MPLS-TP IP/MPLS

Operational

complexity /inefficiency

ITU-T Heterogeneous OAM frameworks at transport layer

LSP LSP

LSP LSP


61/61

Thank you.

Documents

Packet Evolution in Trensport Networks Mpls-tp PacketEvolution_Webinar