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

NE40E V800R010C10SPC500 Configuration Guide - IP Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - 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).
Configuring MVPN Extranet

Configuring MVPN Extranet

To enable a service provider on a VPN to provide multicast services for users on other VPNs, configure MVPN extranet.

Usage Scenario

MD 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, configure MVPN extranet.

Table 8-1 describes the usage scenarios of MVPN extranet.

Table 8-1 Usage scenarios of MVPN extranet

Usage Scenario

Description

Configuration

Remarks

Remote cross

The source and receiver VPN instances reside on different PEs.

Configure a source VPN instance on a receiver PE

Using this configuration option is recommended.

Configure a receiver VPN instance on a source PE

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.

-

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.

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.

Pre-configuration Tasks

Before configuring MVPN extranet, complete the following tasks:

  • Configure a unicast routing protocol to ensure that devices are reachable.

  • Configure a BGP/MPLS IP VPN and ensure that the unicast VPN is working properly.

  • Configure basic MVPN functions and ensure that they are working properly.

Configuration Description

Select the following required configuration steps to configure MVPN extranet based on usage scenarios:
  • Remote cross where a source VPN instance needs to be configured on a receiver PE: select steps 1, 2, and 3.

  • Remote cross where a receiver VPN instance needs to be configured on a source PE: select steps 1 and 2.

  • Local cross where the source and receiver VPN instances reside on the same PE: select steps 1 and 2.

  • Local cross where the multicast source belongs to the public network instance: select steps 1, 2, and 4.

Procedure

  1. Configure the same unicast routing policy on the receiver and source PEs so that the receiver VPN can import the routes to the source VPN. For detailed configurations, see Configuring a VPN Instance.
  2. Configure a private network RP to serve the MVPN extranet. For detailed configurations, see Configuring a Static RP. An RP is required only on a PIM-SM network.
  3. Configure a multicast routing policy.
    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run ipv4-family

      The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family 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, specifying that the upstream interface of the RPF route selected by the PIM entry corresponding to a multicast group address belongs to another VPN instance or the public network instance.

    5. Run commit

      The configuration is committed.

  4. Configure static routes to the public network multicast source and RP. For detailed configurations, see Configuring IPv4 Static Routes.

Checking the Configurations

  • 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 | vpn-instance vpn-instance-name | register | none } | mode { ssm | sm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ] command to check information about the PIM routing table.
  • Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] routing-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] | 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 | vpn-instance vpn-instance-name | register | none } ] * [ outgoing-interface-number [ number ] ] command to check information about the multicast routing table.
  • Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info source-address [ group-address ] [ rpt | spt ] command to check RPF routing information with a specified multicast source or source group.

# Run the display pim vpn-instance vpn-instance-name routing-table extranet source-vpn-instance vpn-instance-name command. The command output shows that the upstream interface of the RPF route of the PIM routing entry of VPN RED belongs to VPN BLUE. For example:

<HUAWEI> display pim vpn-instance RED routing-table extranet source-vpn-instance BLUE
 VPN-Instance: RED
 Total 1 (*, G) entry; 2 (S, G) entries
 
 Total matched 1 (*, G) entry; 1 (S, G) entry

 (*, 228.0.0.1)
     RP: 4.4.4.4 
     Protocol: pim-sm, Flag: WC 
     UpTime: 00:47:55
     Upstream interface: MCAST_Extranet(BLUE)
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/0
             Protocol: pim-sm, UpTime: 00:47:55, Expires: 00:02:34
 
 (10.1.1.2, 228.0.0.1)
     RP: 4.4.4.4 
     Protocol: pim-sm, Flag: SPT ACT 
     UpTime: 06:18:43
     Upstream interface: MCAST_Extranet(BLUE)
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/0
             Protocol: pim-sm, UpTime: 00:47:57, Expires: 00:02:32

The preceding command output shows that the upstream interface of the RPF route of the PIM entry with the group address 228.0.0.1 in VPN RED is a multicast extranet interface and belongs to VPN BLUE.

# Run the display pim vpn-instance vpn-instance-name routing-table extranet receive-vpn-instance vpn-instance-name command. The command output shows that the receiver of the PIM routing entry of VPN BLUE belongs to VPN RED. For example:

<HUAWEI> display pim vpn-instance BLUE routing-table extranet receive-vpn-instance RED
 VPN-Instance: BLUE
 Total 1 (*, G) entry; 1 (S, G) entry
 
 Total matched 1 (*, G) entry; 1 (S, G) entry

 (*, 228.0.0.1)
     RP: 4.4.4.4 
     Protocol: pim-sm, Flag: WC EXTRANET 
     UpTime: 00:06:27
     Upstream interface: MTunnel0
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information: none

     Extranet receiver(s): 1
        1: RED
 
 (10.1.1.2, 228.0.0.1)
     RP: 4.4.4.4 
     Protocol: pim-sm, Flag: SPT ACT EXTRANET 
     UpTime: 00:06:06
     Upstream interface: MTunnel0
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information: none

     Extranet receiver(s): 1
        1: RED

The preceding command output shows that the MVPN extranet receiver of VPN BLUE belongs to VPN RED.

# Run the display multicast vpn-instance vpn-instance-name routing-table extranet source-vpn-instance vpn-instance-name command. The command output shows that the upstream interface of the RPF route of the multicast routing entry of VPN RED belongs to VPN BLUE. For example:

<HUAWEI> display multicast vpn-instance RED routing-table extranet source-vpn-instance BLUE
Multicast routing table of VPN instance: RED
 Total 0 (*, G) entry; 1 (S, G) entry, 1 matched
 
 00001: (10.1.1.2, 228.0.0.1)
       Uptime: 00:42:23     
       Upstream Interface: MCAST_Extranet(BLUE)
       List of 1 downstream interface
           1: GigabitEthernet1/0/0

The preceding command output shows that the upstream interface of the RPF route of the entry (10.110.1.2, 228.0.0.1) in VPN RED is a multicast extranet interface and belongs to VPN BLUE.

# Run the display multicast vpn-instance vpn-instance-name routing-table extranet receive-vpn-instance vpn-instance-name command. The command output shows that the receiver of the multicast routing entry of VPN BLUE belongs to VPN RED. For example:

<HUAWEI> display multicast vpn-instance BLUE routing-table extranet receive-vpn-instance RED
Multicast routing table of VPN instance: BLUE
 Total 0 (*, G) entry; 1 (S, G) entry, 1 matched
 
 00001: (10.1.1.2, 228.0.0.1)
       Uptime: 00:01:20     
       Upstream Interface: GigabitEthernet1/0/0
       Extranet receivers: 1
           1: RED

The preceding command output shows that the MVPN extranet receiver of VPN BLUE belongs to VPN RED.

# Run the display multicast vpn-instance vpn-instance-name rpf-info source-address group-address command. The command output shows the RPF routing information with the multicast source address set to 10.1.1.2 in VPN RED. For example:

<HUAWEI> display multicast vpn-instance RED rpf-info 10.1.1.2 228.0.0.1
 VPN-Instance: RED
 RPF information about source 10.1.1.2 and group 228.0.0.1
     RPF interface: MCAST_Extranet
     RPF Source VPN-Instance: BLUE
     Referenced route/mask: 10.1.1.0/24
     Referenced route type: unicast
     Route selection rule: preference-preferred
     Load splitting rule: disable

The preceding command output shows that the upstream interface of the RPF route of the entry (10.1.1.2,228.0.0.1) in VPN RED is a multicast extranet interface, and the multicast source belongs to VPN BLUE.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44093

Downloads: 97

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