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.


NE20E-S V800R010C10SPC500 Feature Description - IP Multicast 01

This is NE20E-S V800R010C10SPC500 Feature Description - IP Multicast
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).
Inter-domain Multicast Implemented by MVPN

Inter-domain Multicast Implemented by MVPN

Multicast Virtual Private Network (MVPN) requires a multicast backbone network (a core network or a public network) to support multicast functions.

  • A PIM instance that runs in a VPN instance bound to a PE is called a VPN-specific PIM instance or a PIM C-instance.

  • A PIM instance that runs in a public network instance bound to a PE is called a PIM P-instance.

Figure 7-1 MVPN networking

MVPN implements communication between PIM C-instances as follows:

  1. MVPN establishes a multicast tunnel (MT) between each two PIM C-instances.

  2. Each PIM C-instance creates a multicast tunnel interface (MTI) to connect to a specific MT.

  3. Each PIM C-instance joins a specific MT based on the configured share-group.

VPN instances with the same share-group address construct a multicast domain (MD).

On the network shown in Figure 7-1, VPN BLUE instances bound to PE1 and PE2 communicate through MD BLUE, and VPN RED instances bound to PE1 and PE2 communicate through MD RED. See Figure 7-2 and Figure 7-3.

Figure 7-2 MD-based VPN BLUE interworking

Figure 7-3 MD-based VPN RED interworking

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

The PIM C-instances send PIM protocol packets or multicast data packets to the MTIs and the MTIs encapsulate the received packets. The encapsulated packets are public network multicast data packets that are forwarded by PIM P-instances. Therefore, an MT is actually a multicast distribution tree on a public network.

  • VPNs use different MTs, and each MT uses a unique packet encapsulation mode, so multicast data is isolated between VPNs.

  • PIM C-instances on 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 a one-to-one relationship. The VPN, MD, MTI, and share-group are all in a one-to-one relationship.

Updated: 2019-01-03

Document ID: EDOC1100055119

Views: 12452

Downloads: 19

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