Case Study 1: Implementing Multicast Support for MPLS VPNs

Case Study 1 Implementing Multicast Support for MPLS VPNs

Multicast VPN or an MPLS VPN capable of supporting multicast packet forwarding does not use MPLS forwarding or a control mechanism but uses MPLS VPN architecture and its associated Multicast Border Gateway Protocol (MBGP) route distribution process. This architecture requires that multicast routing be enabled in the SP core network. The multicast VPN solution provides a reduction in the amount of state information while retaining optimal routing. It maps all the particular VPN multicast groups to a single unique group called the Default Multicast Distribution Tree (Default MDT) in the provider network.

Control and low bandwidth data traffic flows through the default MDT. The solution allows the creation of additional distribution groups called Data Multicast Distribution Trees (Data MDTs) in the SP network to transport high bandwidth sources to points in the network that are signaled to receive traffic. This solution includes the support of multicast routing and forwarding in the context of VPN Routing and Forwarding (VRF) and the use of multicast tunnels over the provider network for control and data connectivity.

Routers in the customer sites that will be a part of the multicast tree will have to be enabled for multicast forwarding on the appropriate interfaces. The provider edge (PE) routers maintain PIM adjacency with the CE routers. The customer can run any multicast routing protocol (SSM or PIM) independent of the multicast protocol running in the provider network. PE routers build a per-VRF default MDT that will be used to distribute data packets and control messages for low bandwidth traffic.

Operation of Multicast MPLS VPN

The operation of a multicast MPLS VPN is as follows:

  1. Default MDT is enabled per customer VRF on every PE router that will forward multicast packets between customer sites. The VRF on the PE routers thus enabled for multicast forwarding is also called the multicast VRF (mVRF).
  2. Default MDT enables multicast forwarding for all PEs where the VRF resides.
  3. Control and data packets are transported per VRF over default MDT. Therefore, all low bandwidth data that is transported over the default MDT will be delivered to PEs where the VRFs reside. Hence, the default MDT is always present.
  4. A Data MDT for higher bandwidth sources can be created on the PE routers per VRF, and only routers that are part of the multicast tree for the high bandwidth source receive the multicast packets generated by the high bandwidth source. The data MDT is created on demand for mVPN (S, G) higher bandwidth traffic.

MDT group addresses are defined by the provider and are unrelated to the groups used by the customer. Access to the MDT is via a multicast tunnel interface on PE routers where the PE router always functions as the root of the MDT if it is connected to the CE router containing the multicast source.

Figure 14-1 shows an SP network with the default MDT and data MDT concepts highlighted.

Figure 14-1. Multicast MPLS VPN Support Concepts and Operation

As shown in Figure 14-1, Site 1 sources multicast packets for GroupA and GroupB where GroupA is a low bandwidth source and GroupB is a high bandwidth source. Sites 2 and 3 belonging to Customer A, as well as PE Routers PE2-AS1 and PE3-AS1, receive traffic destined for both groups. As shown in Figure 14-1, the default MDT is formed between all PE routers, and the data MDT is formed only with PE routers connected to sources/receivers of high bandwidth traffic.

Configuration of Multicast Support for MPLS VPN

Configuration to enable multicast support for MPLS VPN is shown in Figure 14-2. The configurations involve enabling multicast as well as a multicast protocol on the interfaces in the customer domain, as well as the provider domain, to forward multicast packets. In addition, the VRF mapping to the customer is enabled for multicast routing using the ip multicast-routing vrf command, and the default and data MDTs are configured under the VRF definition.

Figure 14-2. Multicast MPLS VPN Configuration Flowchart


Implementing Multicast Support for MPLS VPNs

Figure 14-3 shows a SP network providing MPLS VPN services to Customer A sites. Customer A, after prior deployment of intersite connectivity using MPLS VPN, would like to also have support for multicast traffic propagation to other sites with receivers that are members of a multicast group.

Figure 14-3. Case Study 1: Multicast MPLS VPN Topology

The additional complete configurations on the devices to enable multicast support for MPLS VPN are shown in Figure 14-4. Configurations for PE3-AS1 and PE4-AS1 have not been depicted for brevity and can be derived using the same process as the depicted PE router configurations. As illustrated, the default MDT is configured with a group address of, and the data MDT is configured with a group address range of to

Figure 14-4. Case Study 1: Multicast MPLS VPN Configuration


Verifications for Case Study 1

Figure 14-5 shows the verification for the implementation of multicast support for MPLS VPN by performing a show ip mroute on the appropriate devices. As shown in Figure 14-5, the multicast states are propagated via the MP-BGP backbone to CE2-A for the group due to a receiver being connected in Customer A Site 2 for the group.

Figure 14-5. Case Study 1: Multicast MPLS VPN Verification

MPLS Overview

Basic MPLS Configuration

Basic MPLS VPN Overview and Configuration

PE-CE Routing Protocol-Static and RIP

PE-CE Routing Protocol-OSPF and EIGRP

Implementing BGP in MPLS VPNs

Inter-Provider VPNs

Carrier Supporting Carriers

MPLS Traffic Engineering

Implementing VPNs with Layer 2 Tunneling Protocol Version 3

Any Transport over MPLS (AToM)

Virtual Private LAN Service (VPLS)

Implementing Quality of Service in MPLS Networks

MPLS Features and Case Studies

MPLS Configuration on Cisco IOS Software
MPLS Configuration on Cisco IOS Software
ISBN: 1587051990
EAN: 2147483647
Year: 2006
Pages: 130 © 2008-2020.
If you may any questions please contact us: