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).
Configuring a Multicast Routing Policy

Configuring a Multicast Routing Policy

After multicast VPN extranet is configured, receivers in a VPN instance can receive multicast data from the multicast sources in other VPN instances.


Multicast VPN extranet uses a multicast routing policy to specify another VPN as the upstream of the selected Reverse Path Forwarding (RPF) route to allow the multicast data transmission between VPNs.

Multicast VPN extranet applies to the following scenarios:
  • Different VPN instances connected to different PEs need to exchange multicast data. Such a scenario is called a remote-cross scenario. There are two configuration options available to provide multicast VPN extranet services in this scenario:
    • Configure the source VPN instance on the receiver PE and create a multicast routing policy.

    • Configure the receiver VPN instance on the source PE. No multicast routing policy is required. This option is applicable to the scenario where the receiver PE is a non-Huawei device and configuring the source VPN instance on the receiver PE is prohibited.

  • Different VPN instances connected to the same PE need to exchange multicast data or the multicast source belongs to the public network instance. Such a scenario is called a local-cross scenario.


  1. Run:


    The system view is displayed.

  2. Run:

    ip vpn-instance vpn-instance-name

    The VPN instance view is displayed.

  3. Run:


    The VPN instance IPv4 address family is enabled and its view is displayed.

  4. Run:

    multicast extranet select-rpf { vpn-instance vpn-instance-name | public } group group-address { group-mask | group-mask-length }

    A multicast routing policy is configured. with the upstream of the RPF route selected by the PIM entry corresponding to a multicast group address set to another VPN instance enabled with the IPv4 address family or the public network instance.

Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 21050

Downloads: 403

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