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

Configuration Guide - IP Multicast

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, multicast network management.
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

In real-world application, a service provider may need to provide multicast services to users in a different VPN than its own VPN. This requires inter-VPN multicast distribution. Multicast VPN extranet can solve this problem.

Multicast VPN extranet scenarios include remote crossing and local crossing, as described in Table 7-1.

Table 7-1 Multicast VPN extranet scenarios

Scenario

Definition

Description

Remote crossing

The receiver and source VPNs are connected to different PEs.

In this scenario, multicast VPN extranet can be configured in either of the following ways:
  • Configure the source VPN on the receiver PE.

    To use this method, you need to configure a multicast routing policy. This method is recommended.

  • Configure the receiver VPN on the source PE.

    This method does not require any multicast routing policies, but it may cause looping of multicast traffic on the source PE, leading to a waste of bandwidth. Therefore, this method is not recommended. Use this method when the receiver PE is from another vendor and does not support configuration of the source VPN.

Local crossing

The receiver and source VPNs are connected to the same PE or the multicast source is in the public network instance.

-
NOTE:
  • The group address range used for multicast VPN extranet cannot overlap the group address range used within the local VPN.
  • Extranet entries of the source and receiver VPNs support only static rendezvous point (RP) configuration, and the static RP address must belong to the source VPN instance. The receiver VPN must be configured with the same static RP address as the source VPN; otherwise, the two VPNs cannot create the same multicast routing entries.
  • If Source Specific Multicast (SSM) group addresses are used for multicast VPN extranet in the source and receiver VPNs, the same SSM group address range must be configured in the two VPNs.

Remote Crossing

  • Configure the source VPN on the receiver PE.

    As shown in Figure 7-13, PE1 has VPN Green configured and uses Share-Group G1 to encapsulate multicast packets from VPN Green; CE1 is connected to the multicast source of VPN Green. PE2 has VPN Blue configured and uses Share-Group G2 to encapsulate multicast packets from VPN Blue; CE2 is connected to the multicast source of VPN Blue. PE3 has VPN Blue configured and uses Share-Group G2 to encapsulate multicast packets from VPN Blue. A multicast distribution tree (MDT) is set up between PE3 and PE2 on the public network. Users in the site of CE3 require multicast data from both VPN Blue and VPN Green.

    Figure 7-13 VPN extranet networking diagram (configure the source VPN on the receiver PE)

    Configure VPN Green on the receiver PE (PE3) and configure a multicast routing policy on the receiver VPN Blue. Table 7-2 describes how multicast data is transmitted through multicast VPN Extranet after the configuration is complete.

    Table 7-2 Multicast VPN Extranet implementation (configure the source VPN on the receiver PE)

    Step

    Device

    Item

    1

    CE3

    The receiver sends an IGMP Report message to CE3, requesting it to forward multicast data from the multicast source in VPN Green. After CE3 receives the IGMP Report message, it sends a PIM Join message to PE3.

    2

    PE3

    After PE3 receives the PIM Join message from VPN Blue, it creates a multicast routing entry. In addition, PE3 finds that the upstream interface of the RPF route is in VPN Green, so it adds the extranet inbound interface to the routing entry.

    3

    PE3

    PE3 uses Share-Group address G1 of VPN Green to encapsulate the PIM Join message and sends the message to VPN Green on source PE (PE1) across the public network.

    4

    PE1

    The multicast source in VPN Green sends multicast data. PE1 uses the Share-Group address G1 of VPN Green to encapsulate the multicast data and forwards the multicast data to VPN Green on PE3.

    5

    PE3

    PE3 decapsulates the received multicast data, distributes the data to the receiver VPN Blue, and forwards the data to the receiver in VPN Blue.

  • Configure the receiver VPN on the source PE.

    The configuration is performed on the network shown in Figure 7-14, with the above mentioned prerequisites.

    Figure 7-14 VPN extranet networking diagram (configure the receiver VPN on the source PE)

    You need to configure the receiver VPN Blue on the source PE (PE1) and do not need to configure any multicast routing policies. Table 7-3 describes how multicast data is transmitted through multicast VPN Extranet after the configuration is complete.

    Table 7-3 Multicast VPN Extranet implementation (configure the receiver VPN on the source PE)

    Step

    Device

    Item

    1

    CE3

    The receiver sends an IGMP Report message to CE3, requesting it to forward multicast data from the multicast source in VPN Green. After CE3 receives the IGMP Report message, it sends a PIM Join message to PE3.

    2

    PE3

    After PE3 receives the PIM Join message from VPN Blue, it uses Share-Group address G2 of VPN Blue to encapsulate the PIM Join message and sends the message to VPN Blue on the source PE (PE1) across the public network.

    3

    PE1

    PE1 distributes the PIM Join message from VPN Blue to source VPN Green and creates a multicast routing entry in VPN Green. In addition, PE1 adds the extranet outbound interface to the routing entry and records receiver VPN Blue.

    4

    PE1

    When PE1 receives multicast data from the multicast source in VPN Green, it directs the multicast data to VPN Blue. PE1 then uses Share-Group address G2 to encapsulate the multicast data and sends it to VPN Blue on the receiver PE (PE3) across the public network.

    5

    PE3

    PE3 decapsulates the received multicast data and forwards it to the receiver in VPN Blue.

Local Crossing

As shown in Figure 7-15, PE1 is the source PE of VPN Blue; CE1 is connected to the multicast source in VPN Blue; CE4 is connected to the multicast source in VPN Green. Both CE3 and CE4 are connected to PE3. Users in the site of CE3 require multicast data from both VPN Blue and VPN Green.

Figure 7-15 Local crossing networking

Table 7-4 shows how multicast data is transmitted through multicast VPN extranet in local crossing scenario.

Table 7-4 Multicast VPN extranet implementation (local crossing)

Step

Device

Item

1

CE3

The receiver sends an IGMP Report message to CE3, requesting it to forward multicast data from the multicast source in VPN Green. After CE3 receives the IGMP Report message, it sends a PIM Join message to PE3.

2

PE3

After PE3 receives the PIM Join message from VPN Blue, it creates a multicast routing entry for VPN Blue. In addition, PE3 finds that the upstream interface of the RPF route is in VPN Green, so it distributes the PIM Join message to VPN Green.

3

PE3

After PE3 receives a PIM Join message from VPN Green, it creates a multicast routing entry and records receiver VPN Blue. PE3 then sends a PIM Join message for VPN Green to upstream device CE4.

4

PE3

When multicast data sent from the multicast source in VPN Green is forwarded to PE3 through CE4, PE3 directs the multicast data to receiver VPN Blue according to the multicast routing entry for VPN Green.

5

PE3

After multicast data from VPN Green is distributed to VPN Blue, PE3 forwards the data to CE3 according to the multicast routing entry in VPN Blue. CE3 then forwards the multicast data to the receiver.

NOTE:

If the multicast source is on the public network and the receiver is on a private network, you need to configure static routes to the multicast source and RP on the public network in the receiver VPN. The receiver PE then distributes PIM Join messages from the private network to the public network and creates multicast routing entries according to the PIM messages. Multicast data is distributed to the VPN through the public network and finally forwarded to receivers on the private network. Multicast protocol and data packets are forwarded without GRE encapsulation and decapsulation.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 40046

Downloads: 13

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