Professional Documents
Culture Documents
Brkipm-3017 2
Brkipm-3017 2
mVPN Deployment
Models
#CLUS
Agenda
• Introduction
• mVPN Architecture
• Core trees
• Overlay Signaling
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
#CLUS © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Introduction
• Purpose
• Provide key takeaway’s
• Explain building blocks of classic mVPN and Next Generation (NG) mVPN
• No operating system/platform specifics (including release support)
• Little configuration
• Configure mVPN Profiles Within Cisco IOS
• Configure mVPN Profiles Within Cisco IOS-XR
• Provide guidance which mVPN profile to chose
• Before we start
• C- stands for customer
• P- stands for Provider
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
Basic Multicast Recap: SSM
(S1,G) IGMP
(S1,G) PIM join (S1,G) PIM join (S1,G) PIM join Report
RP
(*,G) (*,G)
PIM PIM
(*,G) PIM join (*,G) IGMP
Report
(*,G) PIM join
(*,G) (*,G) (*,G) (*,G)
PIM PIM
(*,G) IGMP
Report
(S,G) (*,G)
PIM PIM
PIM PIM
LDP Label
IP IP IP IP
MPLS =
• Without unicast, no multicast: RPF would fail • LDP
• MPLS TE
• Multicast forwarding in core? • Segment Routing MPLS
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
mVPN Architecture
BRKIPM-3017 12
Planes - Underlay
core plane
CE1 VRF PE1 PE3 VRF CE3
Receivers Receivers
P1
P1
• PIM
• mLDP
• P2MP TE
• IR
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
Planes - Overlay
VPN plane
CE1 VRF PE1 PE3 VRF CE3
Receivers Receivers
P1
Sources Sources
• PIM
or
• BGP
PIM PIM
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
Planes – Overlay Signaling
CE1
PE1
PE3
CE2 CE3
PE2
PE1
PE4 PE3
CE4
P1
PE2
PE4
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
Core Tree Types
Default MDT Data MDT Partitioned MDT
root
root
PE1
PE1 root
root PE3
PE3 PE2
PE2
PE4 PE4
root
} }
1.
2.
S,G 3. S,G 1.
…
∑ S,G = S,G = Data MDT
or Default MDT
or
1.
*,G 2. *,G 1.
3.
…
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
Core Tree Type Construction - mLDP
root
root
PE1
PE1 root
root PE3
PE3 PE2
PE2
PE4 PE4
root
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Core Tree Type Construction – P2MP TE
root
root
PE1
PE1 root
root PE3
PE3 PE2
PE2
PE4 PE4
root
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
Core Tree Type Construction – IR
root
root
PE1
PE1 root
root PE3
PE3 PE2
PE2
PE4 PE4
root
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
Encapsulation mcast
IP
PE1
GRE
PE3
PE2
PE1
mcast
IP
PE4
P PE3
PE2
PE4
MPLS Label
Stack
PE1
PE2
PE3 mcast
IP
PE1
PE4 PE3
PE2 P
PE4
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Core Trees
BRKIPM-3017 22
Core Trees
• PIM
• mLDP
• P2MP TE
• Ingress Replication
Core Tree - PIM
• PIM/IP Multicast as we know it
• Pretty complex, but well-known
• (*,G) and (S,G) / PIM Sparse Mode, PIM SSM, PIM BiDir
• PIM for core tree
• Used for Default Model / Rosen
• Replication of multicast on the core routers
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 24
Core Trees
• PIM
• mLDP
• P2MP TE
• Ingress Replication
Core Tree - mLDP
• Multipoint LDP = LDP + extensions
• P2MP tree - Receiver driven – Root learned from routing
• MP2MP tree – Configuration driven – Root configured
• Protection by MPLS TE or Loop-Free Alternate (LFA)
• No PHP – top label identifies the tree
• Replication of mcast on the core routers
• FEC elements holds: Type of tree + Root + Opaque value: (S,G), MDT
number, LSP ID, …
Label
Opaque
Mapping
TLV Element TLV
Message
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
mLDP Signaling and Packet forwarding
P2MP Tree MP2MP Tree
Root is ingress PE: Root is any P or PE:
automatic: BGP next-hop configured
PE1
Downstream Traffic
PE1
Downstream Traffic
Upstream Traffic
Label Map Label Map Label Map
P2MP MP2MP down MP2MP up
Root: PE1 Root: PE1 Root: PE1
Opaque Opaque Opaque
Label
Label Label
Label Map
P2MP Label Map
Label Map
Root: PE1 P2MP Label Map
MP2MP up
Opaque P Root: PE1
Opaque Root: PE1 MP2MP up
Label Opaque Root: PE1
Label P Opaque
Label
Label
Root 2 P2 P4 Root 2 P2 P4
10.1.1.1/31 10.1.1.2/32
IGP IGP
PE3 PE3
• One root address only • Multiple root addresses
• Both trees active at the same time
• Longest match routing
• PE router selects preferred root and sends onto that tree
• 10.1.1.1 can be phantom
only (no duplicate traffic), but receives from any tree
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 28
mLDP and Flex-Algo
• Flex-Algo uses Segment Routing
• Segment Routing
• Link-state protocol
• Flexible Algorithms
• Enforce traffic over a path with different constraints (than the shortest IGP path)
• Colored links define topologies
• Use-case: dual plane
• Defined by user
• For example:
1. minimum delay and avoid links with affinity green
2. minimum IGP metric and avoid links with affinity blue
• Is used for unicast
• Is used for multicast: by mLDP
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
IGP SR Algorithm
• Each node advertises definition of Flex-Algo
1 2 3 Algorithm : 128 -255
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Algorithm | Metric Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Metric Type
| Alg. Type | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0: IGP metric
| Sub-TLVs |
+ + 1: Min unidirectional link delay
| ... | 2: TE default metric
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
#CLUS © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 30
Link Delay – Probe Measurement
TX Timestamp T1 RX Timestamp T2
PM Query Packet
Local-end
1 2 Remote-end
PM Response Packet
RX Timestamp T4 TX Timestamp T3
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 31
Per-Link Latency Measurement
PE1 P1 P2 PE2
Sources
Receivers
P5 P6
Alg 129
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
mLDP-only SAC
• RFC 7473: State Advertisement Control for Non-negotiated LDP apps
• Have an LDP peer negotiate to advertise label bindings for certain MPLS
apps or not by means of capability exchange at LDP session establishment
• Configure LDP to negotiate the label advertisement for IPv4, IPv6, FEC128,
FEC129, and mLDP
• Request: run (m)LDP for advertisement of mLDP label bindings, but not for
unicast label bindings
• Use-case: Segment Routing network (no LDP for unicast needed)
RP/0/0/CPU0:PE(config-ldp)# capabilities sac ?
fec128-disable Disable exchanging PW FEC128 label bindings
fec129-disable Disable exchanging PW FEC129 label bindings
ipv4-disable Disable exchanging IPv4 prefix label bindings
ipv6-disable Disable exchanging IPv6 prefix label bindings
mldp-only Only exchange mLDP label bindings
<cr>
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 34
Core Trees
• PIM
• mLDP
• P2MP TE
• Ingress Replication
Core Tree – P2MP TE
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 36
P2MP TE
• P2MP tunnel signaled by RSVP, to multiple tail end routers
1
Configured tail end routers, or
learned through BGP
2
PE2
Calculate path to tail end routers
Path
3 PE1 P
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 37
P2MP TE - Tunnels
• Configure or discover the tail end routers of P2MP TE tunnels
configure/static discover/auto-tunnel
PE2 PE2
PE PE
PE3 PE3
PE4 PE4
• PIM
• mLDP
• P2MP TE
• Ingress Replication
Core Tree - IR
• No replication of multicast on the core routers
• Let’s not use a P2MP tree in the core
• Let’s re-use unicast MPLS Label Switched Paths (LSPs)
• Ingress replication!
• Protection by LFA/Ti-LFA
• Used when
• Routers do not understand P2MP TE, mLDP or other inter-op issues
• Simple solution is good enough: inter-as links
• Amount of traffic is low – could be used in certain part of the network
• Packets have extra MPLS label to differentiate unicast vs. multicast traffic on same LSP
• BGP AD is needed to transport mVPN MPLS label
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
IR Encapsulation
Unicast
MPLS Label
BGP Update mVPN MPLS
Label
Tunnel Type 1 – IR
mVPN Label
PE address
Data
used by egress PE to
identify mcast packet
C-PIM join
C-PIM join PE
Receiver
PE
Source C-PIM join
PE
Unicast LSP Receiver
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 41
Comparison Core Trees
PIM mLDP P2MP TE
Mature / Well known Enhancement to existing protocol Enhancement to existing protocol
Soft state (periodic refresh) Hard state (no periodic updates) Soft state (periodic refresh)
No Fast Restoration Fast Restoration (povided by LFA or MPLS TE) Fast Restoration
P2MP trees only P2MP and MP2MP trees P2MP trees only
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 42
Packet Forwarding Labeled Switched Multicast
P2MP • P2MP TE MP2MP
• MP2MP mLDP
• P2MP mLDP
19 19
P
Packet Eth2/0 P
Eth2/0
replication on 21
core routers 24
PE PE PE PE
PE PE
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
Overlay Signaling
BRKIPM-3017 46
Overlay Signaling Possibilities
PIM BGP
CE PE PE CE CE PE PE CE
Receiver Source Receiver
Source
S1,S2
MPLS cloud S1,S2 MPLS cloud
CE PE PE CE CE PE PE CE
Source Receiver Receiver
Source
S1,S2 MPLS cloud S1,S2
MPLS cloud
Static In-band
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
Overlay Signaling
• PE-CE mcast signaling is always PIM • PIM neighborship: one-hop between
PEs over Default (or Partitioned) MDT
• PIM signaling: Joins/Prunes/Asserts
PE1
one-hop over Default (Partitioned)
PE2
PE1 PIM PE3 MDT
PE3
• (*,G) or (S,G) over MDT
PE2 PE4
PE4
PE1
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 48
BGP Signaling
→ new procedures
!
address-family ipv4
mdt auto-discovery mldp
• New address family “IPv4 mVPN” mdt default mpls mldp p2mp
mdt overlay use-bgp
1. Signal Auto-Discovery (AD) route-target export 1:1
route-target import 1:1
2. Signal multicast information
• (*,G) or (S,G) router bgp 1
neighbor 10.100.1.7 remote-as 1
• Which tunnel to use (core tree protocol and tunnel type) neighbor 10.100.1.7 update-source Loopback0
!
address-family ipv4 mvpn
neighbor 10.100.1.7 activate
neighbor 10.100.1.7 send-community extended
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 49
A New Found Role for BGP
Auto-Discovery Multicast Signalling
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
BGP Address Family IPv4 mVPN
Signal multicast information
(*,G) (S,G) Tunnel information
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 51
BGP Signaling
I-PMSI (type 1) I-PMSI (type 1)
PIM
Relay PIM Join
driven CE PE MPLS cloud PE CE
Receiver
RP
PIM
Relay PIM Join
driven CE PE MPLS cloud PE CE
Receiver
Source
Data MDT
threshold crossed S-PMSI (type 3)
data
Build Data MDT
driven CE PE MPLS cloud PE CE
Receiver
Source
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 52
BGP Signaling
LSP Identifier is [*,*]
PEs routers indicate they are willing to
participate in the MS-PMSI (Partitioned
MDT)
MS-PMSI (type 3) MS-PMSI (type 3)
[*,*] [*,*]
config Partitioned
Type 3
driven MDT CE PE MPLS cloud PE CE
Receiver
Source
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
BGP IPv4 mVPN Prefix Example: Route-Type 1
Route-type 1 = Intra-AS I-PMSI A-D route
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 55
BGP Signaling for Sparse mode
RP 4
Registering
PE3
6
1 7
PIM (*,G) Join PIM (S,G) Join
9
PE1 Source Active A-D route (type 5) PE2
PE2
Receiver Source
(S1, G) (S,G) Traffic (S1, G)
10 creates (S,G) and
uses RPF peer PE2 8
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 56
VRF Static over P2MP TE
PE2
PE1 PE3
P2MP TE
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 57
mapping
In-band Signaling PIM Join LDP Label Mapping
Message
PIM Prune LDP Label Withdraw
Message
• No overlay signaling
• Method to stitch a PIM tree to a mLDP LSP without any additional signaling
• PIM (or IGMP) can be mapped to mLDP
RPF lookup to
get the root PIM → mLDP mLDP mLDP→ PIM
translation propagation translation
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 58
SAFI (Subsequent Address Family Identifier) 2
• SAFI 2 in VRF and SAFI 129 across the core
• Allows for different mcast vs unicast topologies across MPLS
• SAFI 129 = VPN mcast SAFI
• A PE can select an upstream mcast hop which is different than the unicast next hop (RPF is not
the unicast route)
router bgp 1
address-family vpnv4 unicast
multicast IPv6 2/2 mullticast vpnv6 2/129 multicast IPv6 2/2
address-family vpnv6 unicast
address-family vpnv4 multicast multicast IPv4 1/2 mullticast vpnv4 1/129 multicast IPv4 1/2
address-family vpnv6 multicast
unicast ipv6 2/1 unicast vpnv6 2/128 unicast ipv6 2/1
and
unicast ipv4 1/1 unicast vpnv4 1/128 unicast ipv4 1/1
address-family ipv4 unicast vrf vrf1
address-family ipv6 unicast vrf vrf1
address-family ipv4 multicast vrf vrf1 CE PE MPLS cloud PE CE
address-family ipv6 multicast vrf vrf1 Receiver
Source
S1,S2
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 59
Comparison Customer Signaling Protocols
PIM BGP
Older protocol, proven, well known New enhancement to existing protocol
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 60
mVPN Deployment
Models
BRKIPM-3017 61
Putting it all Together
Encapsulation MPLS
IP / GRE
/ Forwarding
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 62
Profiles
Service
Auto Discovery
Core Tree IPv4
IPv6 None
IPv4 VPN PIM
PIM BGP
IPv6 VPN
mLDP
P2MP TE
BIER
IR Profile # Name
0 Default MDT with PIM Model
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 63
mVPN Classic (aka Rosen / aka Default MDT)
• Since 2000
• It works everywhere: all platforms; all operating systems Encapsulation
IP
C-PIM PIM in overlay C-PIM VPN plane
PE
GRE
CE
VRF
PE PE
PE
VRF
CE
Core plane IP
PE no MPLS !
PIM in Core
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 64
Default MDT Recap
Default MDT
PIM-enabled Core
Default MDT connects all mVPN PE routers
and carries all PIM signaling and all mcast
traffic by default
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 65
Default MDT Recap
C-PIM neighbors across
1
Default MDT
Default MDT
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 66
Data MDT Recap Example
Default MDT: 232.0.0.1
Data MDT: 232.0.1.0 – 232.0.1.255
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 67
BGP Signaling for Data MDT
• BGP AD can also be used to discover set of PEs interested in a given C-group to
enable Data MDT creation
“Data MDT BGP IPv4 MVPN Update
Join”
Route Type 3
Join the Data MDT with
Core Tree signaling Tunnel type
FEC Element
I have receiver: I FEC Type
Join Data MDT
traffic rate > data Address Family
MDT threshold Root
PE VPN-ID
Receiver C-mcast data
PMSI Identifier
C-mcast data PE
Source
C-mcast data
C-mcast data
PE
I have no receiver: I
C-mcast data
don’t Join Data MDT
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 68
Why Labeled Switched Multicast (LSM)?
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 69
Default MDT / Rosen - mLDP
• Re-use all of the Rosen model:
• Default MDT
• Data MDT
• PIM Signaling
• Timers
automatically
P picked: ingress PE
PE PE Source
Source
PE
PE
MP2MP tree → Default MDT P2MP tree → Data MDT
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 70
Partitioned MDT
• Dynamic version of Default MDT model
• BGP AD is needed
Partitioned MDT
• MDT built on-demand when customer
PIM hello traffic is present
root
– Optimized for sources mostly co-located
PE1
PE3
in few sites
Source Receiver
– Supports Anycast sources
root PE4 – It is possible to have two different trees/roots
Receiver forwarding the same (S,G)
– With Default MDT → Asserts
PE2
PE5
Receiver
• Scalability: one-way PIM neighborship
Partitioned MDT
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 71
Partitioned MDT and PIM Sparse Mode (SM)
• C-PIM is SM or BiDir
• How do the PE & C-routers learn mapping BSR
RP? Partitioned MDT RP
agent
Receiver
PE3 CE3 (S1, G)
PE4 CE4
Receiver
• C-PIM Source CE2 PE2 (S1, G)
(S2, G)
(S2,G)
• Control-tree = additional P2MP tree
P2MP Control
• Only for RP discovery (AutoRP or Tree
BSR)
• Only for Partitioned MDT
• Automatic: when PE sees RP info (*,224.0.0.13) for BSR announcements
(*,224.0.1.39) for AutoRP-CRP announcements (ip pim send-rp-announce)
• BGP-AD (*,224.0.1.40) for AutoRP-MA announcements (ip pim send-rp-discovery)
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 72
Migration Core Tree Protocol
• Classic mVPN to NG mVPN On Egress PE
Flexible policy to do core tree selection
• Likely to be PIM to mLDP, P2MP TE, BIER
• Per multicast Group
Core migration: core-trees co-existence • Per multicast Source
• Per Source ingress router
• ...
PIM core tree
With RPL (Route
PE Policy Language) in
IOS-XR
I can chose
PE PE either one
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 73
Migration PIM to BGP Overlay Signaling
On Egress PE
Flexible policy to do overlay selection
Overlay migration: PIM BGP co-existence
• Per multicast Group
BGP overlay • Per multicast Source
• Per Source ingress router
• ...
RR
PE With RPL (Route
Policy Language) in
I can chose IOS-XR
PE PE either one
PE
PIM overlay
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 74
IPv6
• No core tree support for IPv6 (PIM, mLDP, P2MP TE, BIER)
router bgp 1
• IPv4 core tree re-used for IPv6 …
Encapsulation
• Note: Encapsulation of IPv6 over mLDP MPLS Label
mLDP : explicit null label at the
bottom to differentiate between IPv4 IPv6 Explicit NULL
Label (2)
& IPv6 mcast on the same MDT
Data
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 75
Complex mVPN Models
• Unified/Seamless MPLS
• Segmented mVPN
• Global Table Multicast
(GTM)
Seamless MPLS
• Better scalability
• Filtering routes on ABR
• ABRs are BGP Route Reflectors
iBGP + label (RFC 3107) iBGP + label (RFC 3107) iBGP + label (RFC 3107)
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 77
Seamless MPLS + mVPN
• Issue: Router in one area does not know PE loopback address in other area
area
mLDP
mLDP Label Mapping
Type F
Root = PE1 loopback E
BGP LU
BGP LU BGP LU Opaque C
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 78
Seamless MPLS + mVPN
• Issue: Router in one area does not know PE loopback address in other area
• Solution: PIM Vector or Recursive FEC (mLDP)
PE1 loopback
BGP LU
area mLDP
mLDP Label Mapping F
Recursive FEC
Root = ABR2 E
FEC (root = PE1) C
BGP LU BGP LU BGP LU
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 79
Segmented mVPN
non-segmented inter-as multicast tunnel non-segmented seamless multicast tunnel
RR RR
RR RR
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 80
Segmented mVPN
B applies to route-
types 1, 3, 4 & 5
I-PMSI/S-PMSI AD Route I-PMSI/S-PMSI AD Route
New PTA for
PMSI Tunnel Attr
G not for 6 & 7 Inter-area P2MP Next-Hop
PMSI Tunnel Attr
Inter-area P2MP Next-Hop
new Segment
(can be any
tunnel type)
P Extended Community Changed NH Extended Community
MPLS switching
dataplane
segments can be
mLDP, IR, MPLS segment 1 segment 2 segment n
P2MP TE type, mixed
...
PE P A(S)BR A(S)BR
or PE
PE can set color (new extended community)
Used to have downstream A(S)BR/PE select
the appropriate tunnel
regeneration of ipv4/6 mvpn routes
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 81
Global Table Multicast (GTM)
• Have all the profiles available without VRF (so global context)
• Core tree is LSM (Labeled Switched Multicast)
• Re-use all procedures from mVPN
• Multicast attributes (VRF Route-Import EC) will be attached to IPv4 unicast prefixes and all-zeros RD are used, to
mimic vpnv4 routes
• Unique Route-Target is used for IPv4 mvpn routes for GTM
MDT
no no
VRF VRF
PE PE
PIM LSM
mLDP core tree PIM
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 82
Inter-Autonomous
BRKIPM-3017 83
Inter-AS Option A
• Issue: none, each AS is completely separate
• Solution: no need for anything special
• Any AS : any core-tree protocol + any overlay protocol
back-to-back ASBR-PEs
IPv4
PIM
PIM Join
RPF to ASBR
BGP IPv4 MDT (S,G) = (PE1, MDT Group)
BGP vpnv4/6 RD / ASBR (Vector)
IPv4
PIM
P : interpret PIM Vector
one interface for MPLS
and IP Multicast PE : originate PIM Vector
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 85
Inter-AS Option C with PIM
• Issue: P does not know PE loopback address in other AS
• Solution: PIM Vector
BGP IPv4 MDT
BGP vpnv4/6 PIM Join
(S,G) = (PE1, MDT Group)
RPF to ASBR ASBR (Vector)
BGP IPv4
RR RR
IPv4
PIM
P : interpret PIM Vector
one interface for MPLS
and IP Multicast PE : originate PIM Vector
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 86
Inter-AS Option B with mLDP
• Issue: P does not know PE loopback address in other AS
• Solution: Recursive FEC (mLDP)
LDP Label Mapping LDP Label Mapping
mLDP mLDP
P2MP root FEC
P2MP root opaque FEC FEC
ASBR2
PE1
MPLS
mLDP
one interface for MPLS
Unicast and mLDP
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 87
Inter-AS Option C with mLDP
• Issue: P does not know PE loopback address in other AS
• Solution: Recursive FEC (mLDP)
LDP Label Mapping LDP Label Mapping
mLDP
mLDP P2MP root FEC
P2MP root opaque FEC
PE1
FEC ASBR2
BGP IPv4 MDT
BGP vpnv4/6
BGP IPv4
RR RR
BRKIPM-3017 89
Carrier’s Carrier (CsC) with PIM
PIM Vector needed (if not hierarchical CsC) Issue : CSC-PE routers do not run BGP
inside VRF and/or P routers do not run
BGP
Carrier’s Carrier
BGP carries the external CE routes
CSC-PE1 P CSC-PE2
RPF to PE2
CSC-CE1 CSC-CE2
Carrier sites
CsC = labeled
no
unicast on VRF
P P
VRF interface no
PIM Join VRF
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 90
Carrier’s Carrier (CsC) with mLDP
Recursive FEC needed Issue : CSC-PE routers do not run BGP inside
VRF and/or P routers do not run BGP
BGP carries the external CE routes
mLDP FEC
FEC root type
CSC-PE2
CSC-PE1 P CSC-PE2
CsC = labeled
no
unicast on VRF
P P
VRF interface no
VRF
BGP
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 91
BIER
BRKIPM-3017 92
What is the problem with Multicast
• Each Tree has its own unique receiver population
• To efficiently forward/replicate there is a tree per flow!
• This means that state is created in the network
• Impacts memory
• Impacts convergence/CPU
• Can be complex
S5
S4
S3
S2
S1
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 93
What is BIER?
• Bit Index Explicit Replication
• BIER is a new forwarding paradigm to forward and replicate multicast
packets through the network
• Convergence: as fast as unicast
• Simplicity: there is no core tree protocol and no core tree
• Packets are forwarded using a special header that is embedded into the
packet
• Routers build a special forwarding table to forward/replicate using the
BIER header
• BIER forwarding is stateless!
• “state” is now in the packet
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 94
How does BIER work?
Egress
Ingress 2
IP Multicast 1, 2, 3, 4
3
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 95
How does BIER work?
Egress
1 1 IP Multicast
1, 2
Ingress 2 IP Multicast
1, 2, 3, 4 2
IP Multicast
3 3 IP Multicast
3, 4
4 IP Multicast
4
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 96
How does BIER work?
• The smaller the identifier, the more we can fit into a single packet, how small can
C an identifier be?
O
R • A single Bit!!!
E • Advertised by the link-state protocol
• With BIER the Egress Identifier is a Bit Position
• We include a BitString of 256 bits into the packet
O • Manipulations of a BitString is much easier compared to including a list of
V numbers
E
R
L • Re-use overlay signaling (BGP) which is already used by mVPN
A
Y
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 97
How does BIER work?
• Each Egress BIER router has a unique Bit Position
• Routers maintain a forwarding table of Bitmask's
BIER Forwarding
Table
Nbr BM Egress
E 0011 0001
E IP Multicast
F 1100
Ingress 0010
IP Multicast
IP Multicast 1111
0100
F IP Multicast
1000
IP Multicast
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 98
Deployment and
Examples
BRKIPM-3017 99
Nothing
Which Profile to Chose? proprietary
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 100
Deployment Examples
1. TV distribution → P2MP TE
2. Railroad CCTV → mLDP + BGP
3. Migration of overlay signaling and core tree
4. Service Provider migration Rosen to mLDP, using GTM
5. Anycast Source
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 101
Example 1: Bandwidth reservation and Protection
• TV distribution • P2MP TE
• Disjoint paths
• Bandwidth reservation
• FRR protection
P2MP TE tunnel
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 102
Example 2: Scalability
• Railroad CCTV, 10,000 PEs
PE
Station x 1,000
PE
PE
R R
PE
HQ NOC
Rail crossing &
Overlay BGP signaling
platforms x 5,000
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 103
Example 3: Migration of Overlay Signaling and
Core Tree 7600
RPL
• Enable MDT (mLDP) on egress PE PIM → mLDP
PIM → BGP PE
mLDP P P
• Replace 7600 with ASR9K mLDP mLDP
Receivers
PE PE
• Pull multicast over new MDT (mLDP): RPL mLDP mLDP
Sources
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 104
Example 3: Migration of Overlay Signaling and
Core Tree - Notes
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 105
Example 4: SP: Migration Rosen to mLDP
• For example: Using GTM to expand mLDP in old PIM core
New inner
core
PE
PE PE PE PE PE PE
PE PE PE PE PE PE
Partitioned MDT
PE PE
Receiver
VRF Video
Source
PE PE
Receiver
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 107
Key Takeaways
• Default MDT (Rosen) is still ok
• Go LSM if you do not want/have to use PIM / IP Multicast routing in
the core
• Better manageability
• FRR
• More models, better fit of requirements to model
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 108
Complete your online session evaluation
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 109
Continue
your Demos in
the Cisco
Walk-in
self-paced
Meet the
engineer
Related
sessions
education campus labs 1:1
meetings
#CLUS BRKIPM-3017 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 110
Thank you
#CLUS
#CLUS