NG-MVPN mLDP-based Multicast Profiles and configuration rules
04.01 2023 | by massimilianoNG-MVPN mLDP-based Multicast Profiles La configurazione del protocollo mLDP (multipoint o multicast LDP) dipende dal tipo di architetettura di rete […]
NG-MVPN mLDP-based Multicast Profiles
La configurazione del protocollo mLDP (multipoint o multicast LDP) dipende dal tipo di architetettura di rete e requisiti:
P2MP LSP to global table transit multicast in-band signaling
P2MP or MP2MP LSP to MVPN based MI-PMSI (multidirectional inclusive provider multicast – rosen draft)
P2MP or MP2MP LSP to MVPN based MS-PMSI (multidirectional selective provider multicast – partitioned E-LAN).
Ci sono differenti Profili le caratterizzano l’implementazione di mLDP:
Profile 1 : Rosen-mLDP (no BGP A-D)
MP2MP mLDP tree used in core network
VPN-ID used as VRF Distinguisher
Configuration based on Default-MDT
Same Default-MDT core-tree used for IPv4 and IPv6
Data-MDT advertisement sent by PIM (over Default-MDT)
Multicast traffic can be SM or SSM
Inter-AS option A, B and C are supported; connector attribute is announced in VPN-IP routes
Profile 2 : MS-PMSI mLDP MP2MP (no BGP A-D)
MP2MP mLDP tree used in core network
Different MS-PMSI core-tree for IPv4 and IPv6
Multicast traffic can be SM or SSM
Extranet, Hub and Spoke are supported
Inter-AS option A, B and C are supported; connector attribute is announced in VPN-IP routes
Profile 3 : Rosen-GRE with BGP A-D
PIM tree used in core network (the encapsulation used is GRE)
SM, SSM or BiDir can be used in core network
Configuration based on Default-MDT
Multicast traffic can be SM or SSM
MoFRR (multicast only Fast Re-Route) in core network is supported
Extranet, Hub and Spoke, CsC, Customer RP-discovery (Embedded-RP, Auto-RP and BSR) are supported
Inter-AS option A, B and C are supported; VRF route-import EC is announced in VPN-IP routes
Profile 4 : MS-PMSI mLDP MP2MP with BGP A-D
MP2MP mLDP used in core network
Multicast traffic can be SM or SSM
Extranet, Hub and Spoke, CsC, Customer RP-discovery (Embedded-RP, Auto-RP and BSR) are supported
Inter-AS option A, C and C are supported; VRF route-import EC is announced in VPN-IP routes
Profile 5 : MS-PMSI mLDP P2MP with BGP A-D
P2MP mLDP used in core network
Multicast traffic can be SM or SSM
Extranet, Hub and Spoke, CsC, Customer RP-discovery (Embedded-RP, Auto-RP and BSR) are supported
Inter-AS option A, C and C are supported; VRF route-import EC is announced in VPN-IP routes
Profile 6 : VRF in-band signaling (no BGP A-D)
P2MP mLDP tree used in core network
MoFRR in core network is supported
There is one core tree built per-VRF S,G route (no *,G)
Multicast traffic can be SM, S-G, SSM
Profile 7 : Global in-band signaling
P2MP mLDP in-band tree in core network (no C-multicast routing)
Customer traffic can be SM, S,G or SSM
Support for global table S,G on PE node
Profile 8 : Global P2MP-TE
P2MP-TE tree with static destination list in core network (no C-multicast routing)
Static configuration of (S,G) required on Head-End PE node
Only C-SSM support on PE node
Support for global table S,G on PE node
Profile 9 : Rosen mLDP with BGP A-D
Single MP2MP mLDP core-tree as Default-MDT, with PIM C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDir (separate partioned mdt)
RIB-Extranet, RPL-Extranet, Hub and Spoke are supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Profile 10 : VRF Static P2MP with BGP A-D
P2MP-TE tree with static destination list in core network; no C-multicast routing
Static configuration of (S,G) required on Head-End PE node
Only C-SSM support on PE node
Support for IPv4 MVPN S,G on PE node; no support for IPv6 MVPN routes
Profile 11 : Rosen PIM/GRE with BGP C-multicast routing
PIM tree in core network, data encapsulation on GRE, BGP C-multicast routing
Static configuration of (S,G) required on Head-End PE node
For PIM-SSM and PIM-SM core tree with no spt-infinity
For PIM-SM core tree with spt-infinity, only SFS (Hightest PE or Hash-of-BGP paths) is supported
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDir (separate partioned mdt)
Inter-AS option A is supported , Option B and C are not supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 12 : Rosen mLDP P2MP with BGP C-multicast routing
Full Mesh P2MP mLDP core tree as Default-MDT with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDi r (separate partioned mdt)
RPL (Routing Policy Language) Tail-End Extranet supported
Inter-AS option A , Option B and C are supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 13 : Rosen mLDP MP2MP with BGP C-multicast routing
Single MP2MP mLDP core-tree as Default-MDT, with PIM C-multicast routing
Only SFS (Hightest PE or Hash-of-BGP paths) is supported; Hash of installed paths method is not supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDi r (separate partioned mdt)
RIB Tail-End Extranet, RPL Tail-End Extranet are supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A , Option B and C are supported; for option B and C has to be on PE node or the root-address reachability must be leaked across all autonomous system
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 14 : MP2MP mLDP P2MP with BGP C-multicast routing
Full Mesh P2MP mLDP core tree as Default-MDT with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDi r (separate partioned mdt)
RPL (Routing Policy) Tail-End Extranet supported
Inter-AS option A , Option B and C are supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 15 : MP2MP mLDP MP2MP with BGP C-multicast routing
Full Mesh MP2MP mLDP core tree as Default-MDT with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDi r (separate partioned mdt)
RPL (Routing Policy) Tail-End Extranet supported
Inter-AS option A , Option B and C are supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 16 : Rosen Static P2MP-TE with BGP C-multicast routing
Full Mesh or Static P2MP-TE core tree as Default-MDT with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM
RPL (Routing Policy) Tail-End Extranet supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A is supported , Option B and C are not supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 17 : Rosen mLDP P2MP-TE with BGP A-D/PIM C-multicast routing
Full Mesh of P2MP mLDP core tree as Default-MDT with PIM C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDi r (separate partioned mdt)
RPL (Routing Policy) Extranet, Hub & Spoke supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A, B and C are supported
Profile 18 : Rosen Static P2MP-TE with BGP A-D/PIM C-multicast routing
Full Mesh of P2MP mLDP core tree as Default-MDT with PIM C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT supported; Data-MDT not supported
Customer traffic can be SM, SSM
RPL (Routing Policy) Extranet, Hub & Spoke supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A supported,Option B and C not supported
Profile 20 : Rosen P2MP-TE with BGP A-D/PIM C-multicast routing
Dynamic P2MP-TE tunnels setup on demand with PIM C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM
RPL (Routing Policy) Extranet, Hub & Spoke supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A and C supported
Profile 22 : Rosen P2MP-TE with BGP C-multicast routing
Dynamic P2MP-TE tunnels with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDir
RIB Tail-End Extranet, RPL Tail-End Extranet supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A and C supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Profile 24 : Partitioned P2MP-TE with BGP A-D/PIM C-multicast routing
Dynamic P2MP-TE tunnels setup on demand with PIM C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM or BiDir
RPL Tail-End Extranet and Hub $ Spoke supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A and C supported
Profile 26 : Partitioned P2MP-TE with BGP C-multicast routing
Dynamic P2MP-TE tunnels with BGP C-multicast routing
All UHM (Upstream Multicast Hop) options supported
Default-MDT and Data-MDT supported
Customer traffic can be SM, SSM
RIB Tail-End Extranet, RPL Tail-End Extranet supported
Customer RP-discovery (Embedded-RP, AutoRP, BSR) is supported
Inter-AS option A and C supported
All Node PE must have a unique BGP RD value (Route Distinguisher)
Configuration Rules:
Rule for Rosen mGRE (3, 11)
All profiles required VPNv4 or VPNv6 unicast reachability
By default, encap to 1400 byte size is supported; however if the size is more large, use the command “mdt mtu <size> to encap ir decap larger packet size
Loopback configuration is required; use the command ” mdt source loopback0 “; other loopback can be used for different VRF but it is not recommended
Rule for Rosen mLDP (1, 9, 12, 13, 17)
mLDP must be enabled globally
VPN-ID is mandatory for Rosen mLDP MP2MP
Root node must be speciefid manually; multiple root nodes can be configured for Root Node Redundancy
If only profile 1 is configured, MVPN must be enabled under BGP
For BGP A-D profiles, the remote PE address is required
Rule for mLDP (2, 4, 5, 14, 15)
MVPN must be enabled under BGP, if only profile 2 is configured
Support only for static RP for customer RP
Rule for in-band mLDP (6, 7)
MVPN must be enabled under BGP for vrf in-band
Data-MDT is not supported
Backbone facing interface (bfi) must be enabled in Tail PE node
Source route SSM must be advertise to Tail PE by iBGP
Nota:
mLDP in-band signaling permette di creare stati di tipo (S,G) oppure (*,G) core network, senza l’impiego di out-of-band signaling come può essere BGP oppure PIM.
E’ supportato in VRF come pure in global context.
In mLDP in-band signaling è possibile configurare ACL range di multicast (S,G) e questi possono essere trasportati in mLDP LSP; ogni canale multicast (S,G) e mappato 1:1 per ogni albero in-band.
I (S,G) Join attraverso IGMP/MLD/PIM sono registrati in MRIB quale è client di mLDP.
mLDP in-band signaling supporta PIM (S,G) oppure (*,G) attraverso una rete core MPLS senza la necessità di un protocollo fuori-banda.
In-Band signaling è supportato solo per Shared Tree, anche conosciuto come Sparse-mode threshold infinity)
PIM SM non è supportato.
Profile |
Name | Opaque Value | BGP A-D | Data-MDT |
0 | Rosen GRE | N/A | N/A | PIM TLVs over default-MDT |
1 | Rosen mLDP |
Type 2 – Root Address: VPN-ID:0-n |
N/A | PIM TLVs over default-MDT |
2 | MS-PMSI (Partition) MLDP MP2MP |
Cisco Proprietary Source PE:RD:0 |
N/A | N/A |
3 | Rosen GRE with BGP A-D | N/A |
intra-AS MI-PMSI S-PMSI for Data-MDT |
PIM or BGP A-D (knob controlled) |
4 | MS-PMSI (Partition) MLDP MP2MP with BGP A-D |
Type 1 – Source PE:Global_ID |
I-PMSI with empty PTA MS-PMSI for partition mdt S-PMSI for data-mdt S-PMSI cust RP-discovery tree |
BGP A-D |
5 | MS-PMSI (Partition) MLDP P2MP with BGP A-D |
Type 1 – Source PE:Global_ID |
I-PMSI with empty PTA MS-PMSI for partition mdt S-PMSI for data-mdt S-PMSI cust RP-discovery tree |
BGP A-D |
6 | VRF In-Band MLDP | RD:S,G | N/A | N/A |
7 | Global In-Band | S,G | N/A | N/A |
8 | Global P2MP-TE | N/A | N/A | N/A |
9 | Rosen MLDP with BGP A-D |
Type 2 – Root Address: VPN-ID:0-n |
intra-AS MI-PMSI S-PMSI for data-mdt |
PIM or BGP A-D (knob controlled) |