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 1 describes the usage scenarios of MVPN extranet.

**Table 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	-
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.

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 through IP routes.
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.

Context

Select the following required configuration steps to configure MVPN extranet based on usage scenarios:

Remote cross scenario where a source VPN instance needs to be configured on a receiver PE: select steps 1, 2, and 3.
Local cross scenario where the source and receiver VPN instances reside on the same PE: select steps 1 and 2.
Local cross scenario where the multicast source belongs to the public network instance: select steps 1, 2, and 4.

Procedure

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.
Configure a private network RP to serve the MVPN extranet. For details about how to configure an RP, see PIM Configuration > Configuring PIM-SM. An RP is required only on a PIM-SM network.
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.
Configure static routes to the public network multicast source and RP. For detailed configurations, see Configuring IPv4 Static Routes.

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 | 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.

# 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.

# 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.

# 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.

# 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.