No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - IP Multicast

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document describes the principles and configurations of IP multicast, and provides configuration examples.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Basic Implantation Principles

Basic Implantation Principles

The MVPN solution is applicable to a multicast-supported backbone network (core network or public network) of a service provider (SP).

  • The PIM instance running in a VPN instance on a PE is a PIM customer instance (C-instance).

  • The PIM instance running at the public network side of the PE is a PIM provider instance (P-instance).

Figure 7-2  MVPN network diagram

In the MVPN solution, communication between PIM C-instances is implemented on a PE as follows:

  1. A virtual MT is established between PIM C-instances.

  2. Each PIM C-instance creates a Multicast Tunnel Interface (MTI) to connect to the MT.

  3. Each VPN instance joins the corresponding MT based on the configured Share-Groups.

In this manner, the VPN instances with the same Share-Group address form a multicast domain (MD).

As shown in Figure 7-2, VPN BLUE instances bound to PE1 and PE2 communicate through the MD BLUE and similarly, VPN RED instances bound to PE1 and PE2 communicate through the MD RED, as shown in Figure 7-3 and Figure 7-4.

Figure 7-3  MD-based VPN BLUE interworking

Figure 7-4  MD-based VPN RED interworking

The PIM C-instance on the PE considers the MTI as a LAN interface and sets up the PIM neighbor relationship with the remote PIM C-instance through MTIs. The PIM C-instances then use MTIs to perform DR election, send Join/Prune messages, and forward and receive multicast data.

The PIM C-instance sends PIM protocol packets or multicast data packets to the MTI and the MTI encapsulates the received packets. The packets after encapsulation are public network multicast data packets and therefore are forwarded by the PIM P-instances on the network. In conclusion, an MT is actually a multicast distribution tree on the public network.

  • Different VPNs use different topologies and each topology uses a unique packet encapsulation mode. In this manner, multicast data in different VPNs is isolated from each other.

  • The PIM C-instances on the PEs in the same VPN use the same MT and communicate through this MT.


A VPN uniquely defines an MD. An MD serves only one VPN. This relationship is called one-to-one relationship. The VPN, MD, MTI, Share-Group, and Switch-group-pool are all in one-to-one relationship.

Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 21121

Downloads: 403

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next