Next Generation mVPN Deployment

Models

Luc De Ghein
Technical Leader Services
Cisco
Agenda
• Introduction
• NG – mVPN Goals
• mVPN Old Style
• Core Protocols
• Core Trees
• End-to-end Signalling
• Models
• Conclusion

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
mVPN Next Generation - Goals
• Solution tailored to what you want
• Bring in MPLS
– Same encapsulation unicast and multicast
– Shared control plane with unicast In other words = no PIM/IP
– Shared forwarding plane with unicast Multicast in the core
– Fewer protocols
– Fast Restoration

• Keep traffic replication in the core

• Parity with IPv6
• While keeping support and future enhancements for the old model
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
 mVPN – The Old Style
• aka Rosen GRE
• One solution to rule them all
an MDT connecting all a MDT to leaf routers
Needed
leaf routers with multicast receivers
to carry
PIM
control
Default MDT

traffic

Data MDT
Used for
offloading
high rate
flows

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
MDT = Multicast Distribution Tree
mVPN – The Old Style

PIM PIM in overlay PIM VPN plane

PIM core plane

CE PE
PE CE

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
Core Protocols
• PIM/Multicast
– All PIM/Multicast as we know it
• mLDP
– Enhancement to LDP
• Point-to-Multipoint MPLS Traffic Engineering – P2MP TE
– Enhancement to TE
• Unicast MPLS + Ingress Replication
– Unicast MPLS LSP, but with additional signaling of MPLS label

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
mLDP

Point-to-Multipoint Tree Multipoint-to-Multipoint Tree

Allows for
bidirectional
traffic

Allows for
any leaf to
inject traffic
optimum for traffic into the tree
optimum for state
delivery

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
P2MP Traffic Engineering
• Setup driven by headend routers

Point-to-Multipoint Tree

Path message P2P technology in

Resv message the control plane

1. Tailend routers configured

2. Tailend routers learned by BGP Auto-Discovery MPLS TE Auto-Tunnels

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
Unicast MPLS + Ingress Replication

mVPN Label
Unicast Re-use existing unicast LSPs
LSP Label

• No extra signalling in the core

• Replication is on ingress PE
• mVPN label is added to packet
– BGP Auto-Discovery needed to advertise this label
unicast LSPs
• Usage is more for
– Interop
– Routers/segment with no other core tree support
– Inter-AS

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
 Core Tree Types
Multi-Directional Inclusive PMSI Selective PMSI Multidirectional Selective PMSI
MI-PMSI S-PMSI MS-PMSI

aka Default MDT aka Data MDT aka Partitioned MDT

Unidirectional – some Uni- or Bidirectional – some
All connected
connected connected

One MP2MP tree or

One P2MP tree One P2MP or MP2MP tree
Full mesh of P2MP trees

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
PMSI = Provider Multicast Service Interface
Core Replication – Applies to mLDP and P2MP TE
• P2MP in the data plane
LFIB
IN OUT
Label Label I/F

62 44 G0/0/1

33 G0/0/2 44
G
S
ta
Da
Data S G 62

Da
ta
S
G
33

P router
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
Comparisons Core Protocols
PIM mLDP P2MP TE
Mature enhancement to existing protocol enhancement to existing protocol
Well known
Soft state (periodic refresh) Hard state (no periodic updates) Soft state (periodic refresh)
GRE enacpsulation MPLS encapsulation MPLS encapsulation
No Fast Restoration Fast Restoration (povided by MPLS Fast Restoration
TE)
No bandwidth reservation No bandwidth reservation Bandwidth reservation
P2MP trees only P2MP and MP2MP trees P2MP trees only
High complexity Medium complexity High complexity
Medium core state Medium core state High core state
Follows unicast routing Follows unicast routing Allows explicit or bandwidth contraint
routing
Suitable for all mcast applications Suitable for all mcast applications Mostly suitable for video delivery
Best for many-to-many Best for few-to-many

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
Signalling Edge-to-Edge
PIM remains on the edge PE-CE
PIM BGP

PIM PIM PIM PIM

Source PE PE Receiver Sourc PE PE Receiver

S1,S2
MPLS cloud e
MPLS cloud
S1,S2

PIM in Overlay BGP in Overlay

mLDP → PIM PIM → mLDP

static map static map translation translation

PIM PIM PIM PIM

Source PE PE Receiver Sourc PE PE Receiver

MPLS cloud MPLS cloud
S1,S2 e
S1,S2

Static Inband
only with
mLDP
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
 A New Found Role for BGP

Auto-Discovery Multicast Signalling

Discoverying PE endpoints automatically Control plane replacing PIM

• Replacing manual configuration in case • Shared tree (*,G)
of MPLS TE • Source tree (S,G)
• Replacing some PIM signalling,
signalling Data MDT Joins, Prunes, Hellos

• New BGP address family

• Tunnel attribute information
• Describes the core tree (PIM, mLDP, MPLS TE, IR)
• Prefix
• Source, Group, Originator, Route Distinguisher

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
Comparison Overlay Signalling
• PIM versus BGP

PIM BGP

No changes to PIM New enhancement to existing

protocol
PIM adjacencies to all PE routers BGP adjacencies to all PE routers
but likely only to RRs

Medium scalability Very high scalability

Complex with ASM, but well known A lot of new behavior

Complex with ASM, not well known

Soft state (periodic refresh) Hard state (no periodic updates)

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
Models
overlay signalling
core protocol core tree
protocol

• Default MDT (Rosen)

• Inband Signalling
• Static Mapping – P2MP TE
• Partitioned MDT
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
Default MDT (Rosen) Default MDT

• Like Rosen GRE – see the slide 7

• Core tree Default MDT

– PIM/Multicast (Rosen GRE)
– mLDP
• MP2MP
• Full mesh P2MP
– Full mesh P2MP TE
– Ingress Replication
Data MDT
• Core tree Data MDT
– PIM/Multicast (Rosen GRE)
– mLDP P2MP
– P2MP TE
– Ingress Replication

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
Inband Signalling

mLDP Label mLDP Label mLDP Label

Mapping Mapping Mapping
mLDP → PIM PIM → mLDP
Message Message Message
translation translation

PIM Join PIM Join

Source Receiver

• All edge state is seen in the core!

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Static Mapping – P2MP TE
• No overlay signalling
Tailend routers statically
configured

Static mapping of (S,G)

onto P2MP TE tunnel

BGP AD: BGP Update advertises Multicast state is associated with

multicast state to tailend routers P2MP TE tunnel on tailend router

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
 Partitioned MDT
• Rosen-like, but more dynamic model
• Default MDT is between a set of PE
Receiver Receiver
routers, per Source
• Data MDT is possible
• Only with mLDP
Receiver
• MP2MP or P2MP
Source
• MDT is built on-demand only
– PIM PE-CE driven
– No core state at all if not C-mcast state
Receiver
Source
• Optimised when there are a few sources
• If PIM is used as overlay signalling in a few sites
– PIM neighborship is unidirectional
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
Deployment Models Overlay
Model Type core protocol signallng

mLDP inband mLDP none

signallng

Static Mapping P2MP TE static mapping

-P2MP TE

PIM Default is full mesh P2MP

PIM
Rosen models mLDP
Default is MP2MP
P2MP TE

Ingress Default is full mesh BGP

Replication unicast MPLS LSP

MP2MP PIM
mLDP P2MP
Partitioned MDT
Ingress BGP
Replication
NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Conclusion
• Many, many choices (27 mVPN models)
• The choice of model is per VPN (or even per Source/Group)!
• Core tree choice depends on source sites and application
• mLDP is the safe choice. mLDP is general purpose choice
– Inband signalling is for walled garden, limited scale deployment
– Partitioned MDT is for few sources/few sites with PIM as overlay
– P2MP TE is for bandwidth reservation and video distribution
– Rosen model is for anyone (else)

• PIM is still the PE-CE multicast signalling protocol

• PIM or BGP as overlay protocol (except for inband signalling and static mapping)
• BGP needed as overlay protocol when scale is needed
– Perhaps BGP is natural choice when already needed for Auto Discovery

• BGP is new for multicast signalling

NG mVPN © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 22