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

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

Multicast VPN Extranet

Background

Rosen MVPN supports only intra-VPN multicast service distribution. To enable a service provider on a VPN to provide multicast services for users on other VPNs, use MVPN extranet.

Implementation

Table 7-2 describes the usage scenarios of MVPN extranet.

Table 7-2 Usage scenarios of MVPN extranet

Usage Scenario

Description

Remarks

Remote cross

The source and receiver VPN instances reside on different PEs.

Two configuration options are available for remote cross:
  • Configure a source VPN instance on a receiver PE (recommended)

    A multicast routing policy must be configured in this option.

  • Configure a receiver VPN instance on a source PE (not recommended)

    No multicast routing policy is required in this option. This option is not recommended because it may cause multicast traffic loopbacks on the source PE and waste bandwidth. However, when the receiver PE is a non-Huawei device that does not allow the source VPN instance configuration, this option can be used.

Local cross

The source and receiver VPN instances reside on the same PE, or the multicast source belongs to the public network instance.

-
NOTE:
  • The address range of multicast groups using the MVPN extranet service cannot overlap that of multicast groups using the intra-VPN service.
  • Only a static RP can be used in an MVPN extranet scenario, the same static RP address must be configured on the source and receiver VPN sides, and the static RP address must belong to the source VPN. If different RP addresses are configured, inconsistent multicast routing entries will be created on the two instances, causing service forwarding failures.
  • To provide an SSM service using MVPN extranet, the same SSM group address must be configured on the source and receiver VPN sides.

Remote Cross

  • Configure a source VPN instance on a receiver PE

    On the network shown in Figure 7-11, VPN GREEN is configured on PE1; PE1 encapsulates packets with the share-group G1 address; CE1 connects to the multicast source in VPN GREEN. VPN BLUE is configured on PE2; PE2 encapsulates packets with the share-group G2 address; CE2 connects to the multicast source in VPN BLUE. VPN BLUE is configured on PE3; PE3 encapsulates packets with the share-group G2 address; PE3 establishes a multicast distribution tree (MDT) with PE2 on the public network. Users connect to CE3 require to receive multicast data from both VPN BLUE and VPN GREEN.

    Figure 7-11 Configuring a source VPN instance on a receiver PE

    Configure source VPN GREEN on PE3 and a multicast routing policy for receiver VPN BLUE. Table 7-3 describes the implementation process.

    Table 7-3 Configuring a source VPN instance on a receiver PE

    Step

    Device

    Description

    1

    CE3

    CE3 receives an IGMP Report message from the receiver that requires data from the multicast source in VPN GREEN and forwards the Join message to PE3 through PIM.

    2

    PE3

    After PE3 receives the PIM Join message from CE3 in VPN BLUE, it creates a multicast routing entry. Through the RPF check, PE3 determines that the upstream interface of the RPF route belongs to VPN GREEN. Then, PE3 adds the upstream interface (serving as an extranet inbound interface) to the multicast routing table.

    3

    PE3

    PE3 encapsulates the PIM Join message with the share-group G1 address of VPN GREEN and sends the PIM Join message to PE1 in VPN GREEN over the public network.

    4

    PE1

    After PE1 receives the multicast data from the source in VPN GREEN, PE1 encapsulates the multicast data with the share-group G1 address of VPN GREEN and sends the data to PE3 in VPN GREEN over the public network.

    5

    PE3

    PE3 decapsulates and imports the received multicast data to receiver VPN BLUE and sends the data to CE3. Then, CE3 forwards the data to the receiver in VPN BLUE.

  • Configure a receiver VPN instance on a source PE

    On the network shown in Figure 7-12, the prerequisite configurations are the same as those in the first option.

    Figure 7-12 Configuring a receiver VPN instance on a source PE

    Configure receiver VPN BLUE on PE1. No multicast routing policy is required. Table 7-4 describes the implementation process.

    Table 7-4 Configuring a receiver VPN instance on a source PE

    Step

    Device

    Description

    1

    CE3

    CE3 receives an IGMP Report message from the receiver that requires data from the multicast source in VPN GREEN and forwards the Join message to PE3 through PIM.

    2

    PE3

    After PE3 receives the PIM Join message from CE3 in VPN BLUE, it encapsulates the PIM Join message with the share-group G2 address of VPN BLUE and sends the PIM Join message to PE1 in VPN BLUE over the public network.

    3

    PE1

    PE1 imports the PIM Join message for VPN BLUE to VPN GREEN, establishes a multicast routing entry in VPN GREEN, and adds the extranet outbound interface and receiver VPN BLUE to the multicast routing entry.

    4

    PE1

    PE1 imports the multicast data sent by the multicast source in VPN GREEN to receiver VPN BLUE, encapsulates the multicast data with the share-group G2 address of VPN BLUE, and sends the data to PE3 in VPN BLUE over the public network.

    5

    PE3

    PE3 decapsulates and sends the received data to CE3. Then, CE3 forwards the data to the receiver in VPN BLUE.

Local Cross

On the network shown in Figure 7-13, PE1 is the source PE of VPN BLUE. CE1 connects to the multicast source in VPN BLUE. CE4 connects to the multicast source in VPN GREEN. Both CE3 and CE4 reside on the same side of PE3. Users connect to CE3 require to receive multicast data from both VPN BLUE and VPN GREEN.

Figure 7-13 Local cross

Table 7-5 describes how MVPN extranet is implemented in the local crossing scenario.

Table 7-5 MVPN extranet implemented in the local crossing scenario

Step

Device

Description

1

CE3

CE3 receives an IGMP Report message from the receiver that requires data from the multicast source in VPN GREEN and forwards the Join message to PE3 through PIM.

2

PE3

After PE3 receives the PIM Join message, it creates a multicast routing entry of VPN BLUE. Through the RPF check, PE3 determines that the upstream interface of the RPF route belongs to VPN GREEN. PE3 then imports the PIM Join message to VPN GREEN.

3

PE3

PE3 creates a multicast routing entry in VPN GREEN, records receiver VPN BLUE in the entry, and sends the PIM Join message to CE4 in VPN GREEN.

4

PE3

After CE4 receives the PIM Join message, it sends the multicast data from VPN GREEN to PE3, PE3 imports the multicast data to receiver VPN BLUE based on the multicast routing entries of VPN GREEN.

5

PE3

PE3 sends the multicast data to CE3 based on the multicast routing entries of VPN BLUE. Then, CE3 forwards the data to the receiver in VPN BLUE.

NOTE:

In MVPN extranet scenarios where the multicast source resides on a public network and the receiver resides on a VPN, static routes to the multicast source and public network RP must be configured in the receiver VPN instance. After the device where the receiver VPN instance resides imports the PIM join message from the VPN instance to the public network instance and establishes a multicast routing entry, the device can send multicast data from the public network instance to the VPN instance, and then to the receivers. Multicast protocol and data packets can be directly forwarded to the receiver without the need to be encapsulated and decapsulated by GRE.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055119

Views: 12104

Downloads: 19

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