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).
Introduction to Multicast VPN

Introduction to Multicast VPN


Multicast VPN (MVPN) implements multicast service transmission over MPLS/BGP VPNs. It is a solution based on the multicast domain (MD) scheme defined in RFC 6037.


MVPN implements multicast transmission on MPLS/BGP VPNs. It transmits multicast data and control messages of the PIM instances in private network over the public network to the remote sites of the VPN.

The PIM instances in the public network (PIM P-instances) need not know multicast data transmitted between the private networks and the PIM C-instances also need not know multicast routing information of the PIM P-instance. Therefore, isolating the PIM instances of the public network from those of the private networks is implemented.

Concepts in MVPN

  • MD

    MD is short for Multicast Domains. MD is the set of all the VPN instances that can transmit multicast packets on each Provider Edge (PE).Different VPN instances belong to different MDs. An MD serves a specific VPN. All private multicast data transmitted in the VPN is transmitted in the MD.

  • Share-Group

    Based on the MD principle, all the VPN instances on the PEs in the same MD must join a common group, called a Share-Group.

    Currently, one VPN instance can be configured with only one Share-Group, that is, one VPN instance can join only one MD.

  • Share-Multicast Distribution Tree

    Share-MDT is short for Share-Multicast Distribution Tree. Actually, it is set up when the PIM C-instances on the PEs join Share-Groups. A Share-MDT transmits the PIM protocol packets and data packets to other PEs within the same VPN. The Share-MDT is regarded as a multicast tunnel (MT) within an MD.

  • MTI

    MTI is short for Multicast Tunnel Interface. It is the outgoing interface or incoming interface of an MT. An MTI is equal to the outgoing interface or incoming interface of an MD. The local PE and remote PE send and receive VPN data through MTIs.

    The MTI is the channel through which the public network instance and VPN instances on PEs communicate. PEs are connected to an MT by using MTIs, which is equal to the situation that PEs are connected to a shared network segment. On each PE, VPN instances that belong to the MD set up the PIM neighbor relationship on MTIs.

  • Switch-Group

    It is a group to which all the VPN receivers of the PE join for establishing a Switch-MDT after a Share-MDT is established.

  • Switch-MDT

    Switch-MDT is short for Switch-Multicast Distribution Tree. It prevents multicast data packets from being transmitted to unnecessary PEs. After a Share-MDT is set up, all the PEs to which the receivers in the VPN are attached join an MDT set up based on Switch-Groups. A Switch-MDT can transmit high-rate data packets to other PEs in the same VPN.

Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 19868

Downloads: 401

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