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

Configuring Multicast VPN Extranet

The VPN extranet function enables multicast flows to be distributed among VPNs.

Pre-configuration Tasks

Before configuring multicast VPN extranet, configure Basic Multicast VPN Functions to ensure normal operations of multicast VPN.

Context

Multicast VPN in multicast domain (MD) mode only supports intra-VPN multicast distribution and cannot distribute multicast flows among VPNs. In real-world application, however, 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. The VPN extranet function solves this problem.

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

Table 7-6 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 (recommended).

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

  • 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 belongs to the public network instance.

If the multicast source is on a public network whereas receivers are on a private network, you need to configure static routes from the receive VPN instance to the multicast source and source rendezvous point (RP) on the public network.

NOTE:
  • The group address range used for multicast VPN extranet cannot overlap the group address range used within the local VPN.
  • When the private network is running Protocol Independent Multicast Sparse Mode (PIM-SM) in the Any Source Multicast (ASM) model, an RP is required. Extranet entries of the source and receiver VPNs support only static 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.

Procedure

  • Remote crossing (configuring the source VPN on the receiver PE)
    1. Configure the same unicast routing policy on the receiver and source PEs to enable the receiver VPN to import routes of the source VPN. For the configuration procedure, see Configuring a VPN Instance on a PE Device.
    2. Configure a static RP on the private network to serve the multicast VPN extranet group. For the configuration procedure, see "Configuring a static RP" in Configuring an RP. You need to configure an RP only when the private network is running PIM-SM in the ASM model.
    3. Configure a multicast routing policy.

      1. Run the system-view command to enter the system view.
      2. Run the ip vpn-instance vpn-instance-name command to enter the VPN instance view.
      3. Run the ipv4-family command to enable the IPv4 address family of the VPN instance and enter the VPN instance IPv4 address family view.
      4. Run the multicast extranet select-rpf { vpn-instance vpn-instance-name | public } group group-address { group-mask | group-mask-length } command to configure a multicast routing policy that specifies another VPN instance or public network instance as the reverse path forwarding (RPF) upstream interface in the PIM entry for the specified group address range.
      5. Run the commit command to commit the configuration.

  • Remote crossing (configuring the receiver VPN on the source PE)
    1. Configure the same unicast routing policy on the receiver and source PEs to enable the receiver VPN to import routes of the source VPN. For the configuration procedure, see Configuring a VPN Instance on a PE Device.
    2. Configure a static RP on the private network to serve the multicast VPN extranet group. For the configuration procedure, see "Configuring a static RP" in Configuring an RP. You need to configure an RP only when the private network is running PIM-SM in the ASM model.
  • Local crossing (multicast source in the public network instance)
    1. Configure the same unicast routing policy on the receiver and source PEs to enable the receiver VPN to import routes of the source VPN. For the configuration procedure, see Configuring a VPN Instance on a PE Device.
    2. Configure a static RP on the private network to serve the multicast VPN extranet group. For the configuration procedure, see "Configuring a static RP" in Configuring an RP. You need to configure an RP only when the private network is running PIM-SM in the ASM model.
    3. Configure static routes to the multicast source and RP on the public network. For the configuration procedure, see Creating IPv4 Static Routes.
  • Local crossing (receiver and source VPNs on the same PE)
    1. Configure the same unicast routing policy on the receiver and source PEs to enable the receiver VPN to import routes of the source VPN. For the configuration procedure, see Configuring a VPN Instance on a PE Device.
    2. Configure a static RP on the private network to serve the multicast VPN extranet group. For the configuration procedure, see "Configuring a static RP" in Configuring an RP. You need to configure an RP only when the private network is running PIM-SM in the ASM model.

Verifying the Configuration

  • Run the display pim { vpn-instance vpn-instance-name | all-instance } routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | mode { ssm | sm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ] command to view the PIM routing table on a PE.
  • Run the display multicast { vpn-instance vpn-instance-name | all-instance } routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } ] * [ outgoing-interface-number [ number ] ] command to view the multicast routing table on a PE.
  • Run the display multicast { vpn-instance vpn-instance-name | all-instance } rpf-info source-address [ group-address ] [ rpt | spt ] command to check a source-specific or source/group-specific RPF route on a PE.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 37451

Downloads: 13

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