- we have 3 sites connected by MPLS VPN - ISP doesn't support mVPN for carrying IP multicast Requirement - - Consider CE3 as Hub Site, create a DMVPN overlay to carry IP multicast over MPLS VPN backbone between the three sites. For Unicast traffic use MPLS VPN. For Mulicast traffic use DMVPN over MPLS VPN. Take care of RPF. Topology -
Understanding Next-Generation MVPN Network Topology. Layer 3 BGP-MPLS virtual private networks (VPNs) are widely deployed in today’s networks worldwide. Multicast applications, such as IPTV, are rapidly gaining popularity as is the number of networks with multiple, media-rich services merging over a shared Multiprotocol Label Switching (MPLS) infrastructure. Abstract: Inter-AS Multicast VPN solution introduces some challenges in cases where peering systems implement BGP-free core. This post illustrates a known solution to this problem, implemented in Cisco IOS software. The solution involves the use of special MP-BGP and PIM extensions. In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual Private Network) to travel from one VPN site to another, special protocols and procedures must be implemented by the VPN Service Provider. These protocols and procedures are specified in this document. MPLS infrastructure. As such, the demand for delivering multicast service across a BGP-MPLS infrastructure in a scalable and reliable way is also increasing. RFC 4364 describes protocols and procedures for building unicast BGP-MPLS VPNs. However, there is no framework specified in the RFC for provisioning multicast VPN (MVPN) services. Up to This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in RFC 6513. [STANDARDS-TRACK] For the definition of Status , see RFC 2026 .
That’s what we need MP-BGP for. MP-BGP supports IPv4 unicast/multicast, IPv6 unicast/multicast and it has support for VPNv4 routes. To exchange VPNv4 routes, MP-BGP uses a new NLRI (Network Layer Reachability Information) format that has the following attributes:
The PE router has a Multicast aware VPN for the CE router, The interface to the CE router is in sparse dense mode, and in the Multicast VPN. The PE router also has the MDT tree configured as well. The Loopbacks are all enable on the MPLS backbone with sparse-dense-mode for BGP. All interface going from PE-P routers are in sparse mode.
Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs) M. Behringer: February 2006 : Informational: RFC 4382: ASCII, PDF, HTML, HTML with inline errata: MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base: T. Nadeau, Ed., H. van der Linde, Ed. February 2006: Errata: Proposed Standard: RFC 4384 a.k.a. BCP 114
The Multicast VPN—IP Multicast Support for MPLS VPNs feature allows a service provider to configure and support multicast traffic in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) environment. The PE router has a Multicast aware VPN for the CE router, The interface to the CE router is in sparse dense mode, and in the Multicast VPN. The PE router also has the MDT tree configured as well. The Loopbacks are all enable on the MPLS backbone with sparse-dense-mode for BGP. All interface going from PE-P routers are in sparse mode.