Configuring NG MVPN Extranet

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

Usage Scenario

In real-world NG MVPN 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. To enable a service provider on a VPN to provide multicast services for users on other VPNs, configure NG MVPN extranet.

NG MVPN extranet can be used in local or remote cross scenarios.

The address range of multicast groups using the NG MVPN extranet service cannot overlap that of multicast groups using the intra-VPN service.
Only a static RP can be used in an NG 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 NG MVPN extranet, the same SSM group address must be configured on the source and receiver VPN sides.
The MVPN target extended community attribute configured in the VPN instance IPv4 address family MVPN view cannot be the same as the VPN target extended community attribute configured in the VPN instance IPv4 address family view.

Pre-configuration Tasks

Before configuring NG MVPN extranet, complete the following tasks:

Configure a unicast routing protocol to ensure that devices are reachable through IP routes.
Configure BGP/MPLS IP VPN and ensure that unicast VPN services are properly transmitted.
Configure basic NG MVPN functions and ensure that they are working properly.

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 NG 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 routing-enable
  Multicast routing is enabled for the VPN instance IPv4 address family.
5. Run mvpn
  The VPN instance IPv4 address family MVPN view is displayed.
6. 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.
7. Run commit
  The configuration is committed.
(Optional) Configure the extranet to forward multicast traffic through a QinQ/dot1q VLAN tag termination sub-interface, or VBDIF interface or BAS interface if the outbound interface used by NG MVPN extranet is any of the preceding interfaces.
1. Run system-view
  The system view is displayed.
2. Run multicast extranet traffic-forward type { vlanif | qinq | vbdif | bas igmp }
  The extranet is enabled to forward multicast traffic through the VLANIF outbound, QinQ/dot1q VLAN tag termination outbound, BAS, or VBDIF interface.
3. Run commit
  The configuration is committed.

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.