Mpls Intro

5/21/2018 Mpls Intro

1/80


2/80

Introduction to MPLS

BRKMPL-1100

Jose Liste

Technical Marketing Engineer, Cisco

[email protected]


3/80

2014 Cisco and/or its affiliates. All rights reserved.BRKMPL-1100 Cisco Public

Session Goals

Understand history and business drivers for MPLS

Learn about MPLS customer and market segments

Understand the problems MPLS is addressing

Understand the major MPLS technology components

Understand typical MPLS applications

Understand benefits of deploying MPLS

Learn about MPLS futures; where MPLS is going

Objectives

3


4/80


Agenda

Introduction

MPLS Technology Basics

MPLS Layer-3 VPNs

MPLS Layer-2 VPNs

Advanced Topics

Summary

4


5/80

Introduction


6/80 2014 Cisco and/or its affiliates. All rights reserved.BRKMPL-1100 Cisco Public

What Is MPLS?

6

Multi Multi-Protocol: The ability to carry anypayload

Have: IPv4, IPv6, Ethernet, ATM, FR

Protocol

Label Uses Labels to tell a node what to dowith a packet; separates forwarding(hop by hop behavior) from routing(control plane)

Switching Routing == IPv4 or IPv6 lookup.Everything else is Switching.



What is MPLS?

Its all about labels

Use the best of both worlds Layer-2 (ATM/FR): efficient forwarding and traffic engineering

Layer-3 (IP): flexible and scalable

MPLS forwarding plane Use of labels for forwarding Layer-2/3 data traffic

Labeled packets are being switched instead of routed Leverage layer-2 forwarding efficiency

MPLS control/signaling plane Use of existing IP control protocols extensions + new protocols

to exchange label information Leverage layer-3 control protocol flexibility and scalability

Brief Summary

7



Technology ComparisonKey Characteristics of IP, Native Ethernet, and MPLS

8

IP Native Ethernet

Forwarding

Destination address based

Forwarding table learnedfrom control plane

TTL support

Destination address based

Forwarding table learnedfrom data plane

No TTL support

L

Forwardinc

T

Control Plane Routing ProtocolsEthernet Loop avoidanceand signaling protocols

Rou

MP

Packet Encapsulation IP Header 802.3 Header MPL

QoS 8 bit TOS field in IP header 3-bit 802.1p field in VLAN tag 3 bit

OAM IP ping, traceroute Ethernet OAM M



Evolution of MPLS

Evolved from tag switching in 1996 to full IETF

standard, covering over 130 RFCs Key application initially were Layer-3 VPNs,

followed by Traffic Engineering (TE),and Layer-2 VPNs

Technology Evolution and Main Growth Areas

9

1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2

Bring MPLS to Market

Complete base MPLS portfolio

Optimize MPLS for video

Optimize MPLS forpacket transport

O

fo

Cisco shipsMPLS

FirstL3VPNsDeployed

First MPLS TEDeployments

First L2VPNDeployments

Large ScaleL3VPN

Deployments

Large ScaleMPLS TE

Deployments

Large ScaleL2VPN

Deployments

First LSMDeployments

First MPLS TPDeployments


10/80

MPLS Technology Basics



Topics

MPLS reference architecture

MPLS Labels

MPLS signaling and forwardingoperations

MPLS Traffic Engineering

MPLS OAM

Basics of MPLS Signaling and Forwarding

11

Transport

MPLS Forwarding

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

Layer-3 VPNs Layer-2 VPNs

Service (Clients)



MPLS Reference Architecture

P (Provider) router

Label switching router (LSR) Switches MPLS-labeled packets

PE (Provider Edge) router Label edge router (LER)

Imposes and removes MPLS labels

CE (Customer Edge) router Connects customer network to MPLS

network

Different Type of Nodes in a MPLS Network

12

MPLS Domain

CE

CE

Label switched traffic

P

P

P

P

PE

PE



MPLS Labels

Labels used for making

forwarding decision

Multiple labels can be used forMPLS packet encapsulation No limit on the number of labels in a

stack

Outer label always used forswitching MPLS packets in network

Inner labels usually used forservices (e.g. L2/L3 VPN)

Label Definition and Encapsulation

13

TC = Traffic Class: 3 Bits; S = Bottom of Stack;

MPLS Label Stack Ent

MPLS Label Stack (1

MPLS Label Stack (2 l

Label = 20 bits T

LAN MAC Header Label, S=0

LAN MAC Header Label, S


14/80


MPLS QoS

MPLS label has 3 Traffic Class (TC) bits

Used for packet classification andprioritization Similar to Type of Service (ToS) field in IP

packet (DSCP values)

DSCP values of IP packet mapped intoTC bits of MPLS label

At ingress PE router

Most providers have defined 35 serviceclasses (TC values)

Different DSCP TC mappingschemes possible Uniform mode, pipe mode, and short pipe

mode

QoS Marking in MPLS Labels

14

MPLS HeaderLayer-2 Header La

MPLS DiffServ Markingin Traffic Class Bits IP

TC D


15/80


Basic MPLS Forwarding Operations

Label imposition (Push)

By ingress PE router; classify andlabel packets

Based on Forwarding EquivalenceClass (FEC)

Label swapping By P router; forward packets using

labels; indicates service class &destination

Label disposition (Pop) By egress PE router; remove label and

forward original packet to destinationCE

How Labels Are Being Used to Establish End-to-end Connectivity

15

CE

CE

PE

PE

Label Imposition

(Push)

Label Swap Label Swap

P

P

P

PL1

L2 L3


16/80


MPLS Path (LSP) Setup and Traffic Forward

LSP signaling protocols

Either LDP* or RSVP Leverages IP routing

Routing table (Routing InformationBaseRIB)

Exchange of labels Label bindings

Downstream MPLS node advertiseswhat label to use to send traffic tonode

MPLS forwarding MPLS Forwarding table (Forwarding

Information BaseFIB)

MPLS Traffic Forwarding and MPLS Path (LSP) Setup

IP

Forwarding

Destination addressbased

Forwarding table learnefrom control plane

TTL support

Control Plane OSPF, IS-IS, BGP

PacketEncapsulation

IP Header

QoS8 bit TOS field in IP

header

OAM IP ping, traceroute

16(*) LDP signaling assumed for next the ex


17/80


MPLS Path (LSP) Setup

LDP signaling

Leverages existing routing

RSVP signaling Aka MPLS RSVP / TE

Enables enhanced capabilities, suchas Fast ReRoute (FRR)

Can use both protocolssimultaneously They work differently, they solve

different problems

Dual-protocol deployments are verycommon

Signaling Options

LDP

Forwarding path LSP

Forwarding

Calculation

Based on IP routing database

Shortest-Path based

Packet

Encapsulation

Single label

Signaling

By each node independently

Uses existing routingprotocols/information

17


18/80


MPLS Path (LSP) Setup with LDP

Exchange of IP routes

OSPF, IS-IS, EIGRP, etc.

Establish IP reachability

Step 1: IP Routing (IGP) Convergence

18

1

1

InLabel

AddressPrefix

OutIface

128.89 1

171.69 1

OutLabel

InLabel

AddressPrefix

OutIface

128.89 0

171.69 1

OutLabel

InLa

You Can Reach 171.69 Thru Me

You Can Reach 128.89 and

171.69 Thru Me

Routing Updates

(OSPF, EIGRP, )

You C

Forwarding Table Forwarding Table

0

1


19/80


IP Packet Forwarding Example

IP routing information exchanged

between nodes Via IGP (e.g., OSFP, IS-IS)

Packets being forwarded based ondestination IP address Lookup in routing table (RIB)

Basic IP Packet Forwarding

19

0

1

1

128.89.25.4 Data

128.89.25.

128.89.25.4 Data

128.89

171.69

Address I/F

1

1

128.89

171.69

Address I/F

0

1

ForwardingTable ForwardingTable


20/80


MPLS Path (LSP) Setup with LDP

Local label mapping are sent to

connected nodes Receiving nodes update forwarding

table Out label

LDP label advertisement happens in

parallel (downstream unsolicited)

Step 2: Assignment of Remote Labels

20

1

01

Use Label 20 for 128.89 and

Use Label 21 for 171.69

Label Distribution

Protocol (LDP)(Downstream

Allocation)

Use Label 36 for 171

InLabel AddressPrefix

128.89

171.69

OutIface

1

1

OutLabel InLabel AddressPrefix

128.89

171.69

OutIface

0

1

OuLab

20

21

-

-

30

36

20

21

Forwarding Table Forwarding Table

1


21/80


MPLS Traffic Forwarding with LDP

Ingress PE node adds label to

packet (push) Via forwarding table

Downstream node use label forforwarding decision (swap) Outgoing interface

Out label

Egress PE removes label andforwards original packet (pop)

Hop-by-hop Traffic Forwarding Using Labels

21

1

0

128.89.25.4 Data 128.89.25.4 Data20

128.89.230

Forwarding based on

Label

In

Label

Address

Prefix

128.89

171.69

Out

Iface

1

1

Out

Label

In

Label

Address

Prefix

128.89

171.69

Out

Iface

0

1

Out

Label

In

Labe

20

21

-

-

30

36

20

21

30

Forwarding Table Forwarding Table Fo

1

1


22/80


MPLS Traffic Forwarding with LDP

Routing protocol distributes routes

LDP distributes labels that map to routes

Packets are forwarded using labels

So what?

MPLSs benefit shows up later, in two places: Divergence from IP routed shortest path

Payload-independent tunneling

Quick recap

22


23/80


MPLS Path (RSVP) Setup

MPLS-TE lets you deviate from the IGP shortest-cost path

This gives you lots of flexibility around how you send traffic across Three steps:

Information distribution

Path calculation

LSP signaling

23


24/80



Flood link characteristics in the IGP Reservable bandwidth, link colors,

other properties

24

IP/MPLS


25/80



IGP: Find shortest (lowest cost) pathto all nodes

TE: Per node, find the shortest(lowest cost) path which meetsconstraints

25

Link with ins

Link with su

n

n

Find

shortest

path to R8with 8Mbps

IP/MPLS

53

10

15

10

10

8

R1


26/80



Set up the calculated path usingRSVP (Resource ReSerVation

Protocol)

Once labels are learned, theyreprogrammed just like LDP labels At the forwarding level, you cant tell

whether your label came from RSVPor LDP

All the hard work is in the control plane No per-packet forwarding hit for any of

this

26

IP/MPLSHead end

PATH

RESV

L=16

Topic c


27/80


MPLS TE Fast ReRoute (FRR)

Steady state

Primary tunnel: A B D E

Backup tunnel: B C D (pre-provisioned)

Failure of link between router B andD

Traffic rerouted over backup tunnel

Recovery time 50 ms Actual Time VariesWell Below 50

ms in Lab Tests

Implementing Network Failure Protection Using MPLS RSVP/TE

27

Router D

Router C

Router A Router B

RoutRouter X

P

B

Topic c

BRKM


28/80


MPLS OAM

MPLS LSP Ping

Used for testing end-to-end MPLS connectivity similar to IP ping Can we used to validate reachability of LDP-signaled LSPs, TE tunnels, a

MPLS LSP Trace Used for testing hop-by-hop tracing of MPLS path similar to traceroute

Can we used for path tracing LDP-signaled LSPs and TE tunnels

MPLS LSP Multipath (ECMP) Tree Trace Used to discover of all available equal cost LSP paths between PEs

Unique capability for MPLS OAM; no IP equivalent!

Auto IP SLA Automated discovery of all available equal cost LSP paths between PEs

LSP pings are being sent over each discovered LSP path

Tools for Reactive and Proactive Trouble Shooting of MPLS Connec

28


29/80


Summary

MPLS networks consist of PE routers at in/egress and P routers in

Traffic is encapsulated with label(s) at ingress (PE router)

Labels are removed at egress (PE router)

MPLS forwarding operations include label imposition (PUSH), swapdisposition (POP)

LDP and RSVP can be used for signaling label mapping informatioend-to-end Label Switched Path (LSP)

RSVP label signaling enables setup of TE tunnels, supporting enhaengineering capabilities; traffic protection and path management

Key Takeaways

29


30/80

MPLS Virtual Private Networks


31/80


MPLS Virtual Private Networks

Definition of MPLS VPN service

Basic MPLS VPN deploymentscenario

Technology options

Topics

31

Transport

MPLS Forwarding



Service (Clients)


32/80


What Is a Virtual Private Network?

Set of sites which communicate with each other in a secure way

Typically over a shared public or private network infrastructure

Defined by a set of administrative policies Policies established by VPN customers themselves (DIY)

Policies implemented by VPN service provider (managed/unmanaged)

Different inter-site connectivity schemes possible

Full mesh, partial mesh, hub-and-spoke, etc.

VPN sites may be either within the same or in different organization VPN can be either intranet (same org) or extranet (multiple orgs)

VPNs may overlap; site may be in more than one VPN

Definition

32


33/80


MPLS VPN: Build vs Buy?

To some people, deploying MPLS VPN means building your own network

To some, it means buying MPLS-based VPN services from a prov

Most of the heavy lifting is in building your own

Buying may or may not have any impact on your network

33


34/80


MPLS VPN Example

VPN policies

Configured on PE routers (manualoperation)

VPN signaling Between PEs

Exchange of VPN policies

VPN traffic forwarding Additional VPN-related MPLS labelencapsulation

PE-CE link Connects customer network to MPLS

network; either layer-2 or layer-3

Basic Building Blocks

34

PE

PE

CE

PE-CE

Link

CE

VPN

Policy

VPN

Policy

BGP Route Reflector

VPN

Signaling


35/80


MPLS VPN Models

MPLS Layer-3 VPNs

Peering relationship between CE andPE

MPLS Layer-2 VPNs Interconnect of layer-2 Attachment

Circuits (ACs)

Technology Options

35

MPLS VPN Models

CE connecte

based conne

layer-2 type)

Static rou

PE-CE ro

eBGP, OS CE routing h

relationship

routers are p

routing

PE routers m

specific rout

exchange cu

routing infor

MPLS LMPLS Layer-2 VPNs

Point-to-PointLayer-2 VPNs

Multi-PointLayer-2 VPNs

CE

connected

to PE via L2(Eth, FR,

ATM, etc)

connection

CE-CE L2

p2p

connectivity

CE-CE

routing; no

SP

involvement

CE

connected to

PE Ethernetconnection

CE-CE L2

(Eth) mp

connectivity

CE-CE

routing; no

SP

involvement

Top


36/80

MPLS Layer-3 Virtual Private Networ

p

BR


37/80


MPLS Layer-3 Virtual Private Networks

Technology components

VPN control plane mechanisms

VPN forwarding plane

Deployment use cases Business VPN services

Network segmentation

Data Center access

Topics

37

Transport

MPLS Forwarding



Service (Clients)

MPLS L 3 VPN O i


38/80


MPLS Layer-3 VPN Overview

VPN policies

Separation of customer routing via virtual VPN routing table (VRF) In PE router, customer interfaces are connected to VRFs

VPN signaling Between PE routers: customer routes exchanged via BGP (MP-BGP)

VPN traffic forwarding

Separation of customer VPN traffic via additional VPN label VPN label used by receiving PE to identify VPN routing table

PE-CE link Can be any type of layer-2 connection (e.g., FR, Ethernet)

CE configured to route IP traffic to/from adjacent PE router

Variety of routing options; static routes, eBGP, OSPF, IS-IS

Technology Components

38

Vi t l R ti d F di I t


39/80


Virtual Routing and Forwarding Instance

Virtual routing and forwarding table

On PE router Separate instance of routing (RIB) and

forwarding table

Typically, VRF created for eachcustomer VPN Separates customer traffic

VRF associated with one or morecustomer interfaces

VRF has its own routing instance forPE-CE configured routing protocols E.g., eBGP

Virtual Routing Table and Forwarding to Separate Customer Traffic

39

VRF

Blue

VRF

Green

CE

PE

CE

VPN 2

VPN 1

VPN R t Di t ib ti


40/80


VPN Route Distribution

Full mesh of BGP sessions among

all PE routers Or BGP Route Reflector (common)

Multi-Protocol BGP extensions (MP-iBGP) to carry VPN policies

PE-CE routing options Static routes

eBGP

OSPF

IS-IS

EIGRP

Exchange of VPN Policies Among PE Routers

40

PE

PE

CE

PE-CE

Link

CE

Blue VRF

Red VRF

BGP Route Reflecto

VPN C t l Pl P i


41/80


VPN Control Plane Processing

Make customer routes unique: Route Distinguisher (RD):

8-byte field, VRF parameters; unique value to make VPN IP routes uniqu VPNv4 address: RD + VPN IP prefix

Selective distribute VPN routes: Route Target (RT):

8-byte field, VRF parameter, unique value to define the import/export ruleroutes

MP-iBGP: advertises VPNv4 prefixes + labels

41

VPN C t l Pl P i


42/80


Blue VPN

VPN Control Plane Processing

CE1 redistribute IPv4 route to PE1

via eBGP PE1 allocates VPN label for prefix

learnt from CE1 to create uniqueVPNv4 route

PE1 redistributes VPNv4 route intoMP-iBGP, it sets itself as a next hop

and relays VPN site routes to PE2

PE2 receives VPNv4 route and, viaprocessing in local VRF (green), itredistributes original IPv4 route toCE2

Interactions Between VRF and BGP VPN Signaling

42

BGP advertisement:

VPN-IPv4 Addr = RD:16.1/16

BGP Next-Hop = PE1

Route Target = 100:1Label=42

PE1

eBGP:

16.1/16

CE1

ip vrf blue-vpn

RD 1:100

route-target export

1:100

route-target import

1:100

VRF parameters:

Name = blue-vpn

RD = 1:100

Import Route-Target = 100:1

Export Route-Target = 100:1

VPN Forwarding Plane Processing


43/80


VPN Forwarding Plane Processing

CE2 forwards IPv4 packet to PE2

PE2 imposes pre-allocated VPN label toIPv4 packet received from CE2 Learned via MP-IBGP

PE2 imposes outer IGP label A (learnedvia LDP) and forwards labeled packet tonext-hop P-router P2

P-routers P1 and P2 swap outer IGPlabel and forward label packet to PE1 A->B (P2) and B->C (P1)

Router PE1 strips VPN label and IGPlabels and forwards IPv4 packet to CE1

Forwarding of Layer-3 MPLS VPN Packets

43

P1PE1 P2CE1

IPv4VPNv4Label

IGPLabel B

IPv4VPNv4Label

IGPLabel C

IPv4Packet

IPv4

Service Provider Deployment Scenario


44/80



Deployment Use Case

Delivery of IP VPN services tobusiness customers

Benefits Leverage same network for multiple

services and customers (CAPEX) Highly scalable

Service enablement only requiresedge node configuration (OPEX)

Different IP connectivity can be easilyconfigured; e.g., full/partial mesh

MPLS Layer-3 VPNs for Offering Layer-3 Business VPN Services

44

VPNCoreEdge Core

CPE

Managed VPN Service

Unmanaged VPN Servic

Enterprise Deployment Scenario


45/80


Enterprise Deployment Scenario

Deployment Use Case

Segmentation of enterprise network toprovide selective connectivity forspecific user groups and organizations

Benefits Network segmentation only requires

edge node configuration

Flexible routing; different IPconnectivity can be easily configured;e.g., full/partial mesh

MPLS Layer-3 VPNs for Implementing Network Segmentation

45

VPNCoreEdge Core

Access

MPLS VPNs for L3 Netw

Segmentation

Data Center Deployment Scenario


46/80


Data Center


Deployment Use Case

Segmented WAN Layer-3 at DataCenter edge

Layer-3 segmentation in Data Center

Benefits Only single Data Center edge node

needed for segmented layer-3 access

Enables VLAN/Layer-2 scale (> 4K)

MPLS Layer-3 VPNs for Segmented L3 Data Center Access and Inte

46

CoreDistribution CoAccess

Top Of Rack

MPLS V

MPLS L3 VPN: Build vs buy?


47/80


MPLS L3 VPN: Build vs buy?

Key consideration: bringing SP into the customers routing domain

Easy to solve with BGP, the worlds only political routing protocol!

Also works with static routes: no dynamic handoff, no potential for dmess

BGP and static are very popular

EIGRP, OSPF, RIP are also options

47

Summary


48/80


Summary

MPLS Layer-3 VPNs provide IP connectivity among CE sites

MPLS VPNs enable full-mesh, hub-and-spoke, and hybrid IP connectivity CE sites connect to the MPLS network via IP peering across PE-C

MPLS Layer-3 VPNs are implemented via VRFs on PE edge nodes VRFs providing customer routing and forwarding segmentation

BGP used for signaling customer VPN (VPNv4) routes between PE

To ensure traffic separation, customer traffic is encapsulated in an VPN label when forwarded in MPLS network

Key applications are layer-3 business VPN services, enterprise netsegmentation, and segmented layer-3 Data Center access

Key Takeaways

48

Topic co

BRKMP


49/80

MPLS Layer-2 Virtual Private Networ

BRKMP



50/80



L2VPN technology options

P2P services (VPWS) Overview & Technology Basics

VPN control plane

VPN forwarding plane

MP2MP services (VPLS / xEVPN)

Overview & Technology Basics VPN control / forwarding plane

Deployment use cases L2 Business VPN services

Data Center Interconnect

Topics

50

Transport

MPLS Forwarding



Service (Clients)



51/80


MPLS Layer 2 Virtual Private Networks

VPWS services Point-to-point

Referred to as Pseudowires (PWs)

VPLS services Multipoint

EVPN

Multipoint with BGP-based MAClearning

PBB-EVPN Combines scale tools from PBB (aka

MAC-in-MAC) with BGP-based MAClearning from EVPN

Technology Options

51

MPLS Layer-2 VPNs

Point-to-PointLayer-2 VPNs (VPWS)

Multipoint-to-Layer-2 V

VPLS

Virtual Private Wire Services (VPWS)


52/80


Virtual Private Wire Services (VPWS)

Based on IETFs Pseudo-Wire (PW)Reference Model

Enables transport of any Layer-2traffic over MPLS

PE-CE link is referred to asAttachment Circuit (AC)

Provides a p2p service Discovery: manual (config)

Signaling: LDP

Learning: none

Overview of Pseudowire (PW) Architecture

52

PE1

PE3

CE

Attachment

Circuit (AC)

CE

Pseudo-Wire 1

Pseudo-Wire 2

Emulated Layer-2 Service

Layer-2

Layer-2

VPWS Control Plane Processing


53/80


VPWS Control Plane Processing

(1)New Virtual Circuit (VC) cross-connectconnects customer L2 interface (AC) to

new PW via VC ID and remote PE ID

(2)New targeted LDP session betweenPE1 and PE2 is established, in case onedoes not already exist

(3)PE binds VC label with customer layer-2 interface and sends label-mapping to

remote PE

(4)Remote PE receives LDP label bindingmessage and matches VC ID with localconfigured VC cross-connect

Signaling of a New Pseudo-Wire

53

2 LDP sess

3 Label M

1

4

PE1CE1

Emulated Layer-2 Se

VPWS Forwarding Plane Processing


54/80


VPWS Forwarding Plane Processing

CE2 forwards L2 packet to PE2.

PE2 pushes VC (inner) label to L2 packetreceived from CE2

Optionally, a control word is added as well (notshown)

PE2 pushed outer (Tunnel) label and forwardspacket to P2

P2 and P1 forward packet using outer (tunnel)

label (swap) Router PE2 pops Tunnel label and, based on

VC label, L2 packet is forwarded to customerinterface to CE1, after VC label is removed In case control word is used, new layer-2 header is

generated first

Forwarding of Layer-2 Traffic Over PWs

54

P1PE1 P2CE1

IGPLabel A

EthPWLabel

IGPLabel B

EthPWLabel

IGPLabel C

EthernetFrame

Eth

Virtual Private LAN Services


55/80


Virtual Private LAN Services

VPLS network acts like a virtualswitch that emulates conventionalL2 bridge

Fully meshed or Hub-Spoketopologies supported

Provides a multipoint ethernetservice

Discovery: manual or auto (BGP)

Signaling: LDP or BGP (PW label)

Learning: data plane

Overview of VPLS Architecture

55

PE1

PE3

CE

Attachment

Circuit (AC)

CE

Pseudo-Wire

Emulated Virtual Switch

Eth

Eth

EVPN

ToB


56/80


EVPN

Ethernet VPN

Provides a multipoint ethernet

service

Discovery: BGP, using MPLS VPNmechanisms (RT)

Signaling: BGP (MAC prefixes)

Learning: Control plane (BGP) Allows for multihomed CEs

56

PE 1

PE 2

CE2

CE1


BGP RR

BGP advertisement:

L2VPN/EVPN Addr = CE1.MAC

BGP Next-Hop = PE1

Route Target = 100:1

Label=42

PBB-EVPN

ToB


57/80


Combines Provider BackboneBridging (MAC-in-MAC) with EVPN

Scales better than EVPN Removes the need to advertise

Customer MAC addresses in BGP

Provides multipoint ethernet service

Discovery: BGP, using MPLS VPNmechanisms (RT)

Signaling: BGP (B-MAC prefixes)

Learning: Control plane (BGP) andforwarding plane

Allows for multihomed CEs

57

PE 1

PE 2

CE2

CE1


BGP RR

BGP advertisement:

L2VPN/EVPN Addr = PE1.B-MAC

BGP Next-Hop = PE1

Route Target = 100:1

Label=42

CE-CE MAC addresses learned in the data pla

C-MAC = Customer MAC a

B-MAC = Backbone MAC a

B-MAC

B-MAC



58/80


p y

Deployment Use Case Delivery of E-LINE services to

business customers

Benefits Leverage same network for multiple

services and customers (CAPEX) Highly scalable

Service enablement only requiresedge node configuration (OPEX)

PWs for Offering Layer-2 Business VPN Services

58

PPE PCE

Layer-2 VPN Service



59/80


p y

Deployment Use Case E-LAN services for Data Center

interconnect

Benefits Single WAN uplink to connect to

multipleData Centers

Easy implementation of segmentedlayer-2 traffic between Data Centers

VPLS for Layer-2 Data Center Interconnect (DCI) Services

59

Core

Core

Edge

Core

Core

DCEdge

Data Center

Summary


60/80


y

L2VPNs enable transport of any Layer-2 traffic over MPLS network

L2 packets encapsulated into additional VC label Both LDP and BGP can be used Pseudowire (PW) signaling

PWs suited for implementing transparent point-to-point connectivityLayer-2 circuits (E-LINE services)

VPLS suited for implementing transparent point-to-multipoint conne

between Ethernet links/sites (E-LAN services)

EVPN / PBB-EVPN are next-generation L2VPN solutions based onplane for MAC distribution/learning over the core

Typical applications of L2VPNs are layer-2 business VPN servicesCenter interconnect

Key Takeaways

60

Topics co

BRKMP


61/80

Advanced Topics

MPLS And IPv6


62/80


MPLS allows IPv6 to be deployedas an edge-only service, no need to

run v6 in the core Easier to deploy

Security mechanism

6PE: All IPv6 can see each other(single VPN)

IPv6+label (no RD, no RT) 6VPE: Separate IPv6 VPNs

VPNv6, includes RD and RT

IPv6 Support for Native MPLS Deployments and MPLS Layer-3 Serv

62

P6PE PCE

IPv6 IPv4 MPLS

P6VPE PCE

IPv6 IPv4 MPLS

Label Switched Multicast (LSM)


63/80


What is Label Switched Multicast? MPLS extensions to provide

P2MP connectivity RSVP extensions and multicast LDP

Why Label-Switched Multicast? Enables MPLS capabilities, which can

not be applied to IP multicast traffic(e.g., FRR)

Benefits of Label-Switched Multicast Efficient IP multicast traffic forwarding

Enables MPLS traffic protection andBW control of IP multicast traffic

Point-to-Multi-Point MPLS Signaling and Connectivity

63

IP/MPLS

Uni-Direction

LSP

IP/MPLS

P2MP or MP

LSP Tree

MPLS /

IP

Label Switched

Multicast (LSM)

Segment Routing


64/80


Segment routing provides

Rich forwarding behaviors

Minimal forwarding state (encapsulated in packet)

Simple IS-IS / OSPF extensions programMPLS forwarding plane

IGP advertises Node segment id (label) per node (globally

significant)

Adjacency segment id (label) per link (locally

significant)

Packet with node segment id forwarded alongshortest path to destination

Packet with adjacency segment id forwardedover adjacency

Control Plane

64

A101

B102

C105

D104

203

202

203

202

201 201

Adjacency SegmentIdentifier (label)

Segment Routing


65/80


D(php)

Forwarding Plane

65

A B

C D

E103

103

Payload Payload

201

202

Payload

202

201

202

Payload

202

Payload Payload

C D

A B

E

202

202

201

102

202

Payload

A B

102

C D

C E C D EB C D(php

Node Path Adjacency Path Combi

Enhanced Path Computation for MPLS TE Lwith Path Computation Element (PCE)


66/80


SDN WAN

Path Reque

with Path Computation Element (PCE)

66

Application

PCEP

Stateful

PCC

StatelessPCC

Area 1 Area 2

Area 0

BGP-LS /

SNMP / CLI

Stateless PCE

TED

PCEP

PCE-initiated

LSP

PCC-initiated

LSP

Stateless PCC Area 1 Area 2

Area 0

Stateless PCE(ABR)

Stateless PCE(ABR)

PCEP

PCEP

PCC-initiated

LSP

Inter-Area MPLS TE

ABRs act as stateless PCEs

ABRs implement backward recursivePCE-Based Computation

Introduced in IOS XR 3.5.2

Out-of-network

PCE always in

Introduced in IO

Out-of-network, stateless PCE server

PCC initiates LSPs

Introduced in IOS XR 3.5.2

Stateful PCE

Futures


67/80


New MPLS Developments on the Horizon

67

MPLS Multilayer

OptimizationPCE/GMPLS

WAN OrchestrationPCE/SDN

Control Plane

SimplificationSegment Routing


68/80

Summary

Summary


69/80


Its all about labels

Label-based forwarding and protocol for label exchange

Best of both worlds L2 deterministic forwarding and scale/flexible L3 s

Key MPLS applications are end-to-end VPN services Secure and scalable layer 2 and 3 VPN connectivity

MPLS supports advanced traffic engineering capabilities QoS, bandwidth control, and failure protection

MPLS is a mature technology with widespread deployments De facto for most SPs, large enterprises, and increasingly in Data Center

Ongoing technology evolution Control-plane simplification (Segment Routing) and WAN orchestration (P

Key Takeaways

69

Consider MPLS When


70/80


Is there a need for network segmentation? Segmented connectivity for specific locations, users, applications, etc.

Is there a need for flexible connectivity? E.g., Flexible configuration of full-mesh or hub-and-spoke connectivity

Is there a need for implementing/supporting multiple (integrated) se Leverage same network for multiple services

Are there specific scale requirements? Large number of users, customer routes, etc.

Is there a need for optimized network availability and performance? Node/link protection, pro-active connectivity validation

Bandwidth traffic engineering and QoS traffic prioritization

Decision Criteria

70

MPLS Sessions at Cisco Live


71/80


BRKMPL-1100 Introduction to MPLS

BRKMPL-2100 Deploying MPLS Traffic Engineering

BRKMPL-2101 Deploying MPLS-based Layer 2 Virtual Private Networks

BRKMPL-2102 Deploying MPLS-based IP VPNs

BRKMPL-2108 Designing MPLS in Next Generation Data Center: A Case Study

BRKMPL-2333 E-VPN & PBB-EVPN: the Next Generation of MPLS-based L2VP

BRKMPL-3101 Advanced Topics and Future Directions in MPLS

LTRMPL-2102 Enterprise Network Virtualization using IP and MPLS Technolog

LTRMPL-3102 Enterprise Network Virtualization using IP and MPLS Technolog

TECMPL-3100 Unified MPLS - An architecture for Advanced IP NGN Scale

TECMPL-3200 SDN WAN Orchestration in MPLS and Segment Routing Networ

71

Terminology ReferenceA U d i MPLS R f A hit t


72/80


Acronyms Used in MPLS Reference Architecture

72

Terminology Description

AC Attachment Circuit. An AC Is a Point-to-Point, Layer 2 Circuit Between a CE and a PE.

AS Autonomous System (a Domain)CoS Class of Service

ECMP Equal Cost Multipath

IGP Interior Gateway Protocol

LAN Local Area Network

LDP Label Distribution Protocol, RFC 3036.

LER Label Edge Router. An Edge LSR Interconnects MPLS and non-MPLS Domains.

LFIB Labeled Forwarding Information Base

LSP Label Switched Path

LSR Label Switching Router

NLRI Network Layer Reachability Information

P Router An Interior LSR in the Service Provider's Autonomous System

PE Router An LER in the Service Provider Administrative Domain that Interconnects the Customer Network and the Back

PSN Tunnel Packet Switching Tunnel

Terminology ReferenceA U d i MPLS R f A hit t ( t )


73/80


Acronyms Used in MPLS Reference Architecture (cont.)

73

Terminology Description

Pseudo-Wire A Pseudo-Wire Is a Bidirectional Tunnel" Between Two Features on a Switching Path.

PWE3 Pseudo-Wire End-to-End Emulation

QoS Quality of Service

RD Route Distinguisher

RIB Routing Information Base

RR Route Reflector

RT Route Target

RSVP-TE Resource Reservation Protocol based Traffic Engineering

VPN Virtual Private Network

VFI Virtual Forwarding Instance

VLAN Virtual Local Area Network

VPLS Virtual Private LAN Service

VPWS Virtual Private WAN Service

VRF Virtual Route Forwarding Instance

VSI Virtual Switching Instance

Further ReadingMPLS R f t Ci P d i


74/80


http://www.cisco.com/go/mpls

http://www.ciscopress.com MPLS and VPN Architectures Cisco Press

Jim Guichard, Ivan Papelnjak

Traffic Engineering with MPLS Cisco Press Eric Osborne, Ajay Simha

Layer 2 VPN Architectures Cisco Press Wei Luo, Carlos Pignataro, Dmitry Bokotey, and Anthony Chan

MPLS QoS Cisco Press Santiago Alvarez

MPLS References at Cisco Press and cisco.com

74

Participate in the My Favorite Speaker ConPromote Your Favorite Speaker and You Could be a Winner
http://www.cisco.com/go/mplshttp://www.ciscopress.com/http://www.ciscopress.com/http://www.cisco.com/go/mpls


75/80


Promote your favorite speaker through Twitter and you could win $Press products (@CiscoPress)

Send a tweet and include Your favorite speakers Twitter handle @jliste2002

Two hashtags: #CLUS #MyFavoriteSpeaker

You can submit an entry for more than one of your favorite speak

Dont forget to follow @CiscoLive and @CiscoPress View the official rules at http://bit.ly/CLUSwin

Promote Your Favorite Speaker and You Could be a Winner

75

Complete Your Online Session Evaluation
http://bit.ly/CLUSwinhttp://bit.ly/CLUSwin


76/80


Give us your feedback and youcould win fabulous prizes. Winnersannounced daily.

Complete your session evaluationthrough the Cisco Live mobile appor visit one of the interactive kioskslocated throughout the conventioncenter.

Dont forget: Cisco Live sessionfor viewing on-demand after theCiscoLive.com/Online

76

Continue Your Education
https://www.ciscolive.com/onlinehttps://www.ciscolive.com/online


77/80


Demos in the Cisco Campus

Walk-in Self-Paced Labs

Table Topics

Meet the Engineer 1:1 meetings

77


78/80


79/80

MPLS Transport Profile (TP)Bi-Directional MPLS Tunnel Extensions For Transport Oriented Conn


80/80


What is MPLS TP? Point-to-point static LSPs which are co-

routed Bi-directional TP tunnel

Why MPLS TP? Migration of TDM legacy networks often

assume continuation of connection-orientedoperations model

MPLS TP enables packet-based transport

with connection-oriented connectivity

Benefits of MPLS TP Meets transport-oriented operations

requirements

Enables seamless migration to dynamicMPLS

Bi Directional MPLS Tunnel Extensions For Transport Oriented Conn

80

Transport

MPLS Forwarding

IP/MPLS

(LDP/RSVP-TE/BGP)

MPL

(Static/R

PPE PCE

Bi-Directional

MPLS TP Tunnel

Documents

Mpls Intro