Documente Academic
Documente Profesional
Documente Cultură
NANOG 49
Agenda
Motivation
Multicast Solutions
TE introduction P2MP TE Overview P2MP TE sample config LDP introduction
mLDP Overview
Reference Q and A
NANOG 49
Motivation
Service Providers using MPLS infrastructure want to offer Multicast Services to their customers using the same data plane used to offer unicast services.
Simplify service/operational maintenance of MPLS core by removing PIM configuration requirements from within MPLS core. Route Multicast traffic on a non-optimal path using TE. Leverage Fast Re-route Capability (FRR) for multicast traffic.
NANOG 49
Multicast Solutions
IPv4 M U L T I C A S T
IPv6 M U L T I C A S T
IPv4 M U L T I C A S T
IPv6 M U L T I C A S T
m V P N
6PE / 6 V P E
IPv4 M U L T I C A S T
IPv6 M U L T I C A S T
m V P N
6PE / 6 V P E
IPv4
GRE Based
mLDP
Native Solution
NANOG 49
IPv4 M U L T I C A S T
IPv6 M U L T I C A S T
m V P N
6PE / 6 V P E
m V P N
6PE / 6 V P E
mLDP
NANOG 49
TE Introduction
NANOG 49
HEADEND
MIDPOINT
TAILEND
Upstream
Tunnel Direction
Downstream
NANOG 49
NANOG 49
Tailend
R9 R4
10 30
R2
15
Pop
32
Not enough BW
40 60 50 70
RESV message
27
R6
80 100
R7
R6
22
80
RSVP PATH: R1 R2 R6 R7 R4 R9 RSVP RESV: Returns labels and reserves bandwidth on each link Bandwidth available
Rajendra and Utpal
10
P2MP TE Overview
NANOG 49
11
P2MP TE overview
RSVP-TE based LSPs are built from the head end router in MPLS core to the tail end(s) router (s) with one head end and one or more tail ends Control Plane and Forwarding Plane mechanisms for P2MP TE are the same as P2P TE No PIM required in the core. PIM is needed only at the edge of the MPLS network.
Multicast Groups (S,G) are mapped onto P2MP-TE tunnels. One or more (S, G) can be mapped onto the same P2MP Tunnel
With PIM working at edge of the MPLS network, the overall flow would look like:
NANOG 49
12
Head End
Tail End
CE Receiver
. S2L sub-LSP: The path from the source to one specific leaf. S2PL sub-LSP: The path from the source to a set of leaves.
Leaf LSR - L
B2AL sub-LSP: The path from a branch LSR to all downstream leaves. X2X sub-LSP: A component of the P2MP LSP that is a simple path that does not branch.
NANOG 49
13
P2MP TE Architecture
PIM Enabled PIM Free Core PIM Enabled PIM Adjacency
PE-West
PE-North
CE Receiver
PE-South
CE
PIM Adjacency
Receiver
NANOG 49
14
ID: 100 SubID: 1 ERO: PE-North RSVP PATH ID: 100 SubID: 1 ERO: P-Middle PE-North
PE-West
Path
Tail End
CE Receiver
PE-North P-Middle
Path
PATH
PE-South
MPLS Core
Tail End
RSVP PATH
CE Receiver
NANOG 49
15
P2MP TE Signalling
label used 101 Is same
RSVP RESV RSVP RESV ID: 100 SubID: 1 LABEL: 201
CE Tail End
Resv
PE-North P-Middle
Receiver
CE
Head End
Resv
RSVP RESV
PE-West
PE-South
Source
LABEL: 101
Tail End
RSVP RESV
CE Receiver
16
Data S G
Head End S0 S1
Tail End
CE Receiver
PE-North
CE Source
PE-West
Data S G 101
S2
PE-South
MPLS Core
Tail End
CE Receiver
17
RPF Check
RPF Check is done at TE Tail end routers on inbound interfaces
Since Sub LSP tail has no interface, LSP virtual interfaces (LSP-VIF) are created automatically to represent the inbound Sub LSPs
RPF check modified to use LSP-VIF for source Every Tail end router will have one LSP-VIF for the corresponding head-end router.
One LSP-VIF may represent one or more Sub LSP from the same head end
NANOG 49
18
RPF Check
Source (S1,S2)
SubLSP A1 SubLSP A2
(S1, G1)
(S2, G2)
(S3, G3)
Receiver
RPF Interface: Lspvif1
(S3, G3)
19
NANOG 49
20
NANOG 49
21
router-id 1.1.1.1
area 0 mpls traffic-eng interface Loopback0
interface TenGigE0/2/0/0
mpls traffic-eng router-id Loopback0 !
NANOG 49
22
P2MP TE branch : RP/0/RP0/CPU0:ellora#show mpls forwarding p2mp Local Outgoing Label Label 101 201 401 Prefix Outgoing Interface PO0/9/0/3 Te0/2/2/0 9.1.11.2 47.47.43.2 Next Hop Bytes or ID P2MP TE:1 P2MP TE:1 Switched 0 0
NANOG 49
23
P2MP TE config is similar to P2P Midpoint router configuration. Midpoint LSR must support P2MP signaling extensions
NANOG 49
24
router ospf 1 router-id 1.1.1.3 area 0 mpls traffic-eng interface Loopback0 ! interface GigabitEthernet0/1/1/2 ! ! interface TenGigE0/1/0/0 ! ! mpls traffic-eng router-id Loopback0 !
multicast-routing address-family ipv4 core-tree-protocol rsvp-te ssm range ssm interface all enable ! router igmp interface GigabitEthernet0/1/1/2 !
NANOG 49
25
NANOG 49
26
A combination of both
NANOG 49
27
PE-North
R1 (Head)
Backup LSP
PE-West
R2
P-Middle
R3 (Tail)
PE-South
Primary Path
Backup Path
Rajendra and Utpal
28
NANOG 49
29
LDP Introduction
NANOG 49
30
LDP is a protocol defined to distribute labels between two peers (called LSRs) for prefixes advertised by unicast routing protocols like OSPF, IS-IS, EIGRP, etc..
These labels help create Label Switched Paths or LSPs whose endpoints can be either the directly attached neighbors just like IP next-hop or remote neighbors (called targetted ldp peers) LDP associates a Forwarding Equivalence Class (FEC) [RFC 3031] with each LSP it creates and maps packets onto that LSP
NANOG 49
31
NANOG 49
32
LDP Messages
LDP protocol exchange various kinds of messages like Hello, Initialize, Label Mapping etc. Messages may carry additional information in the form of TLVs
Example: Label Mapping Message carries FEC TLV, Label TLV etc.
FEC TLVs carry information regarding which data packets get mapped onto LSPs
NANOG 49
33
10.2.1.1
Eth0
CE
PE-North
PE-West
Use Label 16LSP for 10.2.1.1 And 17 for 10.4.1.1
Eth1
PE-South
10.4.1.1
CE
NANOG 49
34
In Address Out Out Label Prefix Iface Label 40 10.2.1.1 Eth1 16 41 10.4.1.1 Eth1 17
Eth0
CE Data
PE-West
10.2.1.1
Pop Labels
PE-South
Push Labels
10.4.1.1
CE
Swap Labels
Rajendra and Utpal
NANOG 49
35
mLDP Overview
NANOG 49
36
Capabilities are advertised through LDP message TLVs during LDP Initialisation/LDP session Establishment phase
NANOG 49
37
...
Parameters Tree Type Address Family Address Length Root Node Address Opaque Value
NANOG 49
Description P2MP, MP2MP Up, MP2MP Down Root node address format (IPv4 =1 or IPv6 = 2) Number of octets in root address (IPv4 = 4, IPv6 = 16) Host address of MP LSP root (within MPLS core) One or more TLVs uniquely identifying MP LSP within the in context of the root
Rajendra and Utpal
38
mLDP Signalling discovers the FEC for an LSP, and assigns multicast flow to the LSP.
Two types of signalling are used: In-Band Signalling We discuss this model here! Out-Of-Band or Overlay Signalling FEC uniquely identifies the MP LSP for both methods
NANOG 49
39
mLDP Architecture
Upstream control plane signalling (towards root) PIM Enabled PIM Free Core (No Native Multicast) PIM Enabled PIM Adjacency LSP PIM Adjacency LSP MPLS Core
Tail End
PE-West
PE-North
CE Receiver
PE-South
Tail End
40
Head End
CE
101
Tail End
PE-North P-Middle
CE
Receiver
PE-West
MPLS Core Source Tail End
TLV
PE-South
CE
Label Map Message
Receiver
Type = P2MP
FEC: Root = PE-West Opaque = 200 LABEL: 401
41
Data S G
Tail End
CE Receiver
PE-North P-Middle
CE Head End Source
Data S G 101
PE-West
MPLS Core
PE-South
Tail End
CE Receiver
PE-West sends Multicast Data Traffic (S, G) on MP-LSP Branch LSR (P-Middle) replicates and swaps out two different labels: (towards PE-North) and 101->401 (towards PE-South)
NANOG 49
101->201
42
Conclusion
Currently Multicast Services offered by MPLS based Service providers
Require
enabling multicast in their MPLS core which demands non-trivial re-engineering of their existing MPLS network . Cannot leverage high availability features of unicast services such as TE-FRR.
P2MP TE and mLDP based solutions address the above limitation with MPLS based service provider.
Applications:
RSVP TE based solution has high potential for Triple Play Video services & content distribution mLDP will be more attractive for applications that demand Multipoint to Multipoint such as Telepresence etc
NANOG 49
43
Reference
RSVP-TE
RFC 4461 & RFC 4875
LDP
RFC 3031 , RFC 3035 & RFC 3036 draft-ietf-mpls-ldp-capabilities-04 draft-ietf-mpls-ldp-p2mp-09.txt Apr. 30, 2010
CCO Documentation
Acknowledgement
Jeff Apcar
NANOG 49
44
NANOG 49
45