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

Reminder

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

upgrade

CLI-based Configuration Guide - IP Multicast

AR500, AR510, and AR530 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).
Multicast VPN Extranet

Multicast VPN Extranet

Applicable Environment

Multicast VPN extranet meets the following requirements:
  • Distributes multicast services among different enterprise users.

  • Enables service or contents providers to distribute multicast services to different enterprise users. The multicast data of a VPN can be provided for users in other VPNs to use.

Principles

Multicast VPN extranet is applicable to two scenarios: remote-cross scenario and local-cross scenario. The basic principles of multicast VPN extranet applied in the two scenarios are described as follows:

  • Remote-cross scenario

    Figure 7-13  Networking diagram of the remote-cross scenario of multicast VPN extranet

    As shown in Figure 7-13, VPN RED is configured on PE1; the address of the share-group is the address of G1; the site where CE1 resides is connected to the multicast source of VPN RED. VPN BLUE is configured on PE2; the address of the share-group is the address of G2; the site where CE2 resides is connected to the multicast source of VPN BLUE. Therefore, PE1 functions as the source PE of VPN RED, and PE2 functions as the source PE of VPN BLUE. VPN BLUE is configured on PE3; the address of the share-group is the address of G2; PE3 establishes an MDT with PE2 on the public network. A user at the site where CE3 resides needs to receive multicast data from both VPN BLUE and VPN RED. Therefore, PE3 functions as the receiver PE of VPN RED and VPN BLUE.

    In such a scenario, after configuring a VPN instance on the local PE, you need to establish a multicast tunnel between the VPN instance of the local PE and that of the remote PE. There are two configuration options available to provide multicast VPN extranet services:
    • Configure the source VPN on the PE where the receiver VPN resides. Based on the multicast domain (MD) to which the VPN to be accessed belongs, configure source VPN RED on PE3 and a multicast routing policy for the receiver VPN instance. Then, hosts in the receiver VPN instance can send Join messages to source VPN.

      PE3 then encapsulates multicast Join messages with the share-group address of VPN RED, and sends the multicast Join messages to PE1 over the public network. Finally, the multicast Join messages reach the multicast source of VPN RED. Similarly, the multicast source of VPN RED sends multicast traffic over the public network to VPN RED at the PE3 side. The multicast traffic is then imported to VPN BLUE, and finally reaches the user.

    • Configure the receiver VPN on the PE where the source VPN resides. Based on the MD to which the VPN to be accessed belongs, configure receiver VPN BLUE instance on PE1. Then, the source VPN instance and the receiver VPN instance can exchange unicast routes. Hosts in the receiver VPN instance send Join messages to the source VPN instance.

      PE3 then encapsulates multicast Join messages with the share-group address of VPN BLUE, and then sends the multicast Join messages to VPN BLUE on PE1 over the public network. PE1 then imports the multicast Join messages from VPN BLUE to VPN RED. Therefore, the multicast Join messages reach the multicast source of VPN RED. Similarly, after multicast traffic sent by the multicast source of VPN RED is imported by PE1 to receiver VPN BLUE, VPN BLUE encapsulates the multicast traffic with its share-group address, and then sends the multicast traffic to the local VPN instance of PE3. Finally, the multicast traffic is forwarded to the user on the associated VPN.

  • Local-cross scenario

    Figure 7-14  Networking diagram of the local-cross scenario of multicast VPN extranet

    As shown in Figure 7-14, users at the site where CE3-2 resides need to receive multicast data from both VPN BLUE and VPN RED. PE2 is the source PE of VPN BLUE. The site where CE2 resides is connected to the multicast source of VPN BLUE. The multicast source of VPN RED is connected to CE3-1. Both CE3-1 and CE3-2 are at the PE3 side.

    In the local-cross scenario, the receiver VPN and the source VPN are on the same PE, and multicast traffic enters the PE through a VPN instance and leaves the PE through another VPN instance. On PE3, the Import Route Target (IRT) of VPN BLUE needs to be configured to be the same as the Export Route Target (ERT) of VPN RED so that CE3-1 and CE3-2 can exchange VPN unicast routes. The process for a user to request and receive multicast data from VPN RED is as follows:
    1. A user at the site where CE3-2 resides requests multicast data from VPN RED. PE3 receives a PIM Join message from CE3-2, and then creates a multicast routing entry of VPN BLUE. Through the RPF check, PE3 finds that the upstream interface of the RPF route belongs to VPN RED. Then, PE3 sends a Join message to VPN RED.

    2. PE3 creates a multicast routing entry (which has the receiver list including receiver VPN BLUE) for VPN RED and then sends a PIM Join message to CE3-1.

    3. The multicast data of VPN RED reaches PE3 through CE3-1. PE3 then imports the multicast data to receiver VPN BLUE based on the multicast routing entries of VPN RED.

    4. After importing multicast data from VPN RED to VPN BLUE, PE3 sends the multicast data to CE3-2 based on multicast routing entries of VPN BLUE. CE3-2 then sends the required multicast data of VPN RED to the user.

NOTE:
A VPN extranet's multicast protocol and data packets are not encapsulated by GRE if the VPN extranet connects to multicast sources on a public network.
Translation
Download
Updated: 2019-06-12

Document ID: EDOC1000097280

Views: 10973

Downloads: 21

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