The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of multicast VPN.

Example: Configuring intra-AS MD VPN

Network requirements

As shown in Figure 1:

· Customer A has two branches that connect to the MPLS L3VPN network of a service provider.

· PIM-SM runs within the two branches.

· The multicast source and the receiver host are in different branches.

Configure intra-AS MD VPN so that the receiver host can receive the multicast data from the source.

Figure 1 Network diagram

Table 1 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
S 1	—	10.11.3.2/24	PE 2	VLAN-interface 3	192.168.2.2/24
PE 1	VLAN-interface 2	192.168.1.2/24	PE 2	VLAN-interface 12	10.11.2.1/24
PE 1	VLAN-interface 11	10.11.1.1/24	PE 2	Loopback 1	1.1.1.2/32
PE 1	Loopback 1	1.1.1.1/32	CE a1	VLAN-interface 10	10.11.3.1/24
P	VLAN-interface 2	192.168.1.1/24	CE a1	VLAN-interface 11	10.11.1.2/24
P	VLAN-interface 3	192.168.2.1/24	CE a1	Loopback 0	2.2.2.2/32
P	Loopback 1	3.3.3.3/32	CE a2	VLAN-interface 20	10.11.4.1/24
R 1	—	10.11.4.2/24	CE a2	VLAN-interface 12	10.11.2.2/24

Requirements analysis

To meet the network requirement, you must run PIM on the devices of the public network, and configure MD VPN on each PE. In addition, make sure the PIM protocol on the public network is independent from the PIM protocol for the VPN instance.

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you configure the intra-AS MD VPN, follow these restrictions and guidelines:

· The MTI interfaces take effect only after the default-group and the MD source interface are specified and the MD source interface obtains the public IP address.

· You must enable the same PIM mode on all interfaces that belong to the same VPN instance (including the interfaces associated with the VPN instance on the PEs).

· You must specify the same default-group for the same VPN instance on different PEs.

· The IP address of the MD source interface must be the same as the source address used for establishing BGP peer relationship. Otherwise, correct routing information cannot be obtained.

· By default, Ethernet interfaces, VLAN interfaces, and aggregate interfaces are shut down. You must use the undo shutdown command to bring them up. This example assumes that all these interfaces are already up.

Configuration procedures

1. Assign an IP address and subnet mask to each interface on CE a1 according to Table 1.

<CEa1> system-view

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] ip address 10.11.3.1 24

[CEa1-Vlan-interface10] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] ip address 2.2.2.2 32

[CEa1-LoopBack0] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] ip address 10.11.1.2 24

[CEa1-Vlan-interface11] quit

# Configure PE 1, P, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)

2. Configure a unicast routing protocol and basic MPLS VPN on all devices so that all devices are interoperable at the network layer. (Details not shown.)

For more information about configuring basic MPLS VPN, see MPLS Configuration Guide.

3. Enable IP multicast routing on the public network, and enable PIM-SM on the public network interfaces (including Loopback interfaces):

# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE1] multicast routing

[PE1-mrib] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] pim sm

[PE1-Vlan-interface2] quit

[PE1] interface loopback 1

[PE1-LoopBack1] pim sm

[PE1-LoopBack1] quit

# On P, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[P] multicast routing

[P-mrib] quit

[P] interface vlan-interface 2

[P-Vlan-interface2] pim sm

[P-Vlan-interface2] quit

[P] interface vlan-interface 3

[P-Vlan-interface3] pim sm

[P-Vlan-interface3] quit

[P] interface loopback 1

[P-LoopBack1] pim sm

[P-LoopBack1] quit

# Configure Loopback 1 as a C-BSR and a C-RP.

[P] pim

[P-pim] c-bsr 3.3.3.3

[P-pim] c-rp 3.3.3.3

[P-pim] quit

# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE2] multicast routing

[PE2-mrib] quit

[PE2] interface vlan-interface 3

[PE2-Vlan-interface3] pim sm

[PE2-Vlan-interface3] quit

[PE2] interface loopback 1

[PE2-LoopBack1] pim sm

[PE2-LoopBack1] quit

4. Enable IP multicast routing for the VPN instance, enable PIM-SM on the private network interfaces, and enable IGMP on interfaces that have receiver hosts attached:

# On CE a1, enable IP multicast routing, and enable PIM-SM on each interface.

[CEa1] multicast routing

[CEa1-mrib] quit

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] pim sm

[CEa1-Vlan-interface10] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] pim sm

[CEa1-Vlan-interface11] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] pim sm

[CEa1-LoopBack0] quit

# Configure Loopback 0 as a C-BSR and a C-RP.

[CEa1] pim

[CEa1-pim] c-bsr 2.2.2.2

[CEa1-pim] c-rp 2.2.2.2

[CEa1-pim] quit

# On CE a2, enable IP multicast routing, enable PIM-SM on VLAN-interface 12, and enable IGMP on the receiver-side interface VLAN-interface 20.

[CEa2] multicast routing

[CEa2-mrib] quit

[CEa2] interface vlan-interface 12

[CEa2-Vlan-interface12] pim sm

[CEa2-Vlan-interface12] quit

[CEa2] interface vlan-interface 20

[CEa2-Vlan-interface20] igmp enable

[CEa2-Vlan-interface20] quit

# On PE 1, create VPN instance customerA.

[PE1] ip vpn-instance customerA

[PE1-vpn-instance-customerA] route-distinguisher 100:1

[PE1-vpn-instance-customerA] vpn-target 111:1

[PE1-vpn-instance-customerA] quit

# Associate VLAN-interface 11 with VPN instance customerA.

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] ip binding vpn-instance customerA

[PE1-Vlan-interface11] quit

# Enable IP multicast routing for VPN instance customerA.

[PE1] multicast routing vpn-instance customerA

[PE1-mrib-customerA] quit

# Enable PIM-SM on VLAN-interface 11.

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] pim sm

[PE1-Vlan-interface11] quit

# On PE 2, create VPN instance customerA.

[PE2] ip vpn-instance customerA

[PE2-vpn-instance-customerA] route-distinguisher 100:1

[PE2-vpn-instance-customerA] vpn-target 111:1

[PE2-vpn-instance-customerA] quit

# Associate VLAN-interface 12 with VPN instance customerA.

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] ip binding vpn-instance customerA

[PE2-Vlan-interface12] quit

# Enable IP multicast routing for VPN instance customerA.

[PE2] multicast routing vpn-instance customerA

[PE2-mrib-customerA] quit

# Enable PIM-SM on VLAN-interface 12.

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] pim sm

[PE2-Vlan-interface12] quit

5. Configure the MD for the VPN instance:

# On PE 1, create an MD for VPN instance customerA, specify the default-group, MD source interface, and data-group range.

[PE1] multicast-domain vpn-instance customerA

[PE1-md-customerA] default-group 239.1.1.1

[PE1-md-customerA] source loopback 1

[PE1-md-customerA] data-group 225.2.2.0 28

[PE1-md-customerA] quit

# On PE 2, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group range.

[PE2] multicast-domain vpn-instance customerA

[PE2-md-customerA] default-group 239.1.1.1

[PE2-md-customerA] source loopback 1

[PE2-md-customerA] data-group 225.2.2.0 28

[PE2-md-customerA] quit

Verifying the configuration

# Verify the establishment of the default-MDT for the public network on PEs and P. The following example shows PIM routing table for the public network on P.

[P]display pim routing-table

Total 1 (*, G) entry; 2 (S, G) entry

(*, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 02:54:43

Upstream interface: Register

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface(s) information:

Total number of downstreams: 2

1: Vlan-interface2

Protocol: pim-sm, UpTime: 02:54:43, Expires: -

2: Vlan-interface3

Protocol: pim-sm, UpTime: 02:33:57, Expires: -

(1.1.1.1, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 01:57:13

Upstream interface: Vlan-interface2

Upstream neighbor: 192.168.1.2

RPF prime neighbor: 192.168.1.2

Downstream interface(s) information: None

(1.1.1.2, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 01:57:13

Upstream interface: Vlan-interface3

Upstream neighbor: 192.168.2.2

RPF prime neighbor: 192.168.2.2

Downstream interface(s) information: None

The output shows that an RPT for (*, 239.1.1.1), an SPT for (1.1.1.1, 239.1.1.1), and an SPT for (1.1.1.2, 239.1.1.1) have been established on the public network. The RPT and SPTs constitute the default-MDT for the public network.

Configuration files

· PE 1:

ip vpn-instance customerA

route-distinguisher 100:1

vpn-target 111:1 import-extcommunity

vpn-target 111:1 export-extcommunity

vlan 2

vlan 11

interface LoopBack1

ip address 1.1.1.1 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.2 255.255.255.0

pim sm

interface Vlan-interface11

ip binding vpn-instance customerA

ip address 10.11.1.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· PE 2:

ip vpn-instance customerA

route-distinguisher 100:1

vpn-target 111:1 import-extcommunity

vpn-target 111:1 export-extcommunity

vlan 3

vlan 12

interface LoopBack1

ip address 1.1.1.2 255.255.255.255

pim sm

interface Vlan-interface3

ip address 192.168.2.2 255.255.255.0

pim sm

interface Vlan-interface12

ip binding vpn-instance customerA

ip address 10.11.2.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· P:

vlan 2 to 3

interface LoopBack1

ip address 3.3.3.3 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.1 255.255.255.0

pim sm

interface Vlan-interface3

ip address 192.168.2.1 255.255.255.0

pim sm

multicast routing

pim

c-bsr 3.3.3.3

c-rp 3.3.3.3

· CE a1:

vlan 10 to 11

interface LoopBack0

ip address 2.2.2.2 255.255.255.255

pim sm

interface Vlan-interface10

ip address 10.11.3.1 255.255.255.0

pim sm

interface Vlan-interface11

ip address 10.11.1.2 255.255.255.0

pim sm

multicast routing

pim

c-bsr 2.2.2.2

c-rp 2.2.2.2

· CE a2:

vlan 12

vlan 20

interface Vlan-interface12

ip address 10.11.2.2 255.255.255.0

pim sm

interface Vlan-interface20

ip address 10.11.4.1 255.255.255.0

igmp enable

multicast routing

Example: Configuring inter-AS option A MD VPN

Network requirements

As shown in Figure 2:

· Customer A has two branches that separately connect to AS 100 and AS 200.

· ASBR-PE 1 and ASBR-PE 2 are interconnected by using the inter-AS option A solution.

· PIM-SM runs within the two branches.

· The multicast source and the receiver host are in different branches.

Configure inter-AS option A MD VPN so that the receiver host can receive the multicast data from the source.

Figure 2 Network diagram

Table 2 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
S 1	—	10.11.3.2/24	R 1	—	10.11.4.2/24
PE 1	VLAN-interface 2	192.168.1.2/24	ASBR-PE 2	VLAN-interface 4	192.168.3.2/24
PE 1	VLAN-interface 11	10.11.1.1/24	ASBR-PE 2	VLAN-interface 3	192.168.2.2/24
PE 1	Loopback 1	1.1.1.1/32	ASBR-PE 2	Loopback 1	1.1.1.3/32
ASBR-PE 1	VLAN-interface 2	192.168.1.1/24	ASBR-PE 2	Loopback 2	22.22.22.22/32
ASBR-PE 1	VLAN-interface 3	192.168.2.1/24	PE 2	VLAN-interface 4	192.168.3.1/24
ASBR-PE 1	Loopback 1	1.1.1.2/32	PE 2	VLAN-interface 12	10.11.2.1/24
ASBR-PE 1	Loopback 2	11.11.11.11/32	PE 2	Loopback 1	1.1.1.4/32
CE a1	VLAN-interface 10	10.11.3.1/24	CE a2	VLAN-interface 20	10.11.4.1/24
CE a1	VLAN-interface 11	10.11.1.2/24	CE a2	VLAN-interface 12	10.11.2.2/24
CE a1	Loopback 0	2.2.2.2/32

Requirements analysis

To meet the network requirement, you must create a separate MD for each AS.

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you configure the inter-AS option A MD VPN, follow these restrictions and guidelines:

· You must enable the same PIM mode for all interfaces that belong to the same VPN instance (including the interface associated with the VPN instance). You may enable different PIM modes for the public network in different ASs.

· You must specify the same default-group for the same VPN instance in the same AS. You may specify different default-groups for the same VPN instance in different ASs.

Configuration procedures

1. Assign an IP address and subnet mask to each interface on CE a1 according to Table 2.

<CEa1> system-view

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] ip address 10.11.3.1 24

[CEa1-Vlan-interface10] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] ip address 2.2.2.2 32

[CEa1-LoopBack0] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] ip address 10.11.1.2 24

[CEa1-Vlan-interface11] quit

# Configure PE 1, ASBR-PE 1, ASBR-PE2, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)

2. Configure a unicast routing protocol and MPLS L3VPN inter-AS option A on all devices so that all devices in the ASs are interoperable at the network layer. (Details not shown)

For more information about configuring basic MPLS VPN, see MPLS Configuration Guide.

3. Enable IP multicast routing on the public network, and enable PIM-SM on the public network interfaces (including Loopback interfaces):

# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE1] multicast routing

[PE1-mrib] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] pim sm

[PE1-Vlan-interface2] quit

[PE1] interface loopback 1

[PE1-LoopBack1] pim sm

[PE1-LoopBack1] quit

# On ASBR-PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[ASBR-PE1] multicast routing

[ASBR-PE1-mrib] quit

[ASBR-PE1] interface vlan-interface 2

[ASBR-PE1-Vlan-interface2] pim sm

[ASBR-PE1-Vlan-interface2] quit

[ASBR-PE1] interface loopback 1

[ASBR-PE1-LoopBack1] pim sm

[ASBR-PE1-LoopBack1] quit

[ASBR-PE1] interface loopback 2

[ASBR-PE1-LoopBack2] pim sm

[ASBR-PE1-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP.

[ASBR-PE1] pim

[ASBR-PE1-pim] c-bsr 11.11.11.11

[ASBR-PE1-pim] c-rp 11.11.11.11

[ASBR-PE1-pim] quit

# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE2] multicast routing

[PE2-mrib] quit

[PE2] interface vlan-interface 4

[PE2-Vlan-interface4] pim sm

[PE2-Vlan-interface4] quit

[PE2] interface loopback 1

[PE2-LoopBack1] pim sm

[PE2-LoopBack1] quit

# On ASBR-PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[ASBR-PE2] multicast routing

[ASBR-PE2-mrib] quit

[ASBR-PE2] interface vlan-interface 4

[ASBR-PE2-Vlan-interface4] pim sm

[ASBR-PE2-Vlan-interface4] quit

[ASBR-PE2] interface loopback 1

[ASBR-PE2-LoopBack1] pim sm

[ASBR-PE2-LoopBack1] quit

[ASBR-PE2] interface loopback 2

[ASBR-PE2-LoopBack2] pim sm

[ASBR-PE2-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP.

[ASBR-PE2] pim

[ASBR-PE2-pim] c-bsr 22.22.22.22

[ASBR-PE2-pim] c-rp 22.22.22.22

[ASBR-PE2-pim] quit

4. Enable IP multicast routing for the VPN instances, enable PIM-SM on the VPN instance interfaces, and enable IGMP on the interfaces that have receiver hosts attached:

NOTE:

The route targets for the same VPN instance on the ASBRs and PEs within the same AS must match. Those within different ASs do not need to match.

# On CE a1, enable IP multicast routing, enable PIM-SM on each interface.

[CEa1] multicast routing

[CEa1-mrib] quit

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] pim sm

[CEa1-Vlan-interface10] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] pim sm

[CEa1-Vlan-interface11] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] pim sm

[CEa1-LoopBack0] quit

# Configure Loopback 0 as a C-BSR and a C-RP.

[CEa1] pim

[CEa1-pim] c-bsr 2.2.2.2

[CEa1-pim] c-rp 2.2.2.2

[CEa1-pim] quit

# On CE a2, enable IP multicast routing, enable PIM-SM on VLAN-interface 12, and enable IGMP on VLAN-interface 20.

[CEa2] multicast routing

[CEa2-mrib] quit

[CEa2] interface vlan-interface 12

[CEa2-Vlan-interface12] pim sm

[CEa2-Vlan-interface12] quit

[CEa2] interface vlan-interface 20

[CEa2-Vlan-interface20] igmp enable

[CEa2-Vlan-interface20] quit

# On PE 1, create VPN instance customerA.

[PE1] ip vpn-instance customerA

[PE1-vpn-instance-customerA] route-distinguisher 100:1

[PE1-vpn-instance-customerA] vpn-target 100:1 both

[PE1-vpn-instance-customerA] quit

# Associate VLAN-interface 11 with VPN instance customerA.

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] ip binding vpn-instance customerA

[PE1-Vlan-interface11] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 11.

[PE1] multicast routing vpn-instance customerA

[PE1-mrib-customerA] quit

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] pim sm

[PE1-Vlan-interface11] quit

# On PE 2, create VPN instance customerA.

[PE2] ip vpn-instance customerA

[PE2-vpn-instance-customerA] route-distinguisher 12:12

[PE2-vpn-instance-customerA] vpn-target 3:3 import-extcommunity

[PE2-vpn-instance-customerA] vpn-target 3:3 export-extcommunity

[PE2-vpn-instance] quit

# Associate VLAN-interface 12 with VPN instance customerA.

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] ip binding vpn-instance customerA

[PE2-Vlan-interface12] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 12.

[PE2] multicast routing vpn-instance customerA

[PE2-mrib-customerA] quit

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] pim sm

[PE2-Vlan-interface12] quit

# On ASBR-PE 1, create VPN instance customerA.

[ASBR-PE1] ip vpn-instance customerA

[ASBR-PE1-vpn-instance-customerA] route-distinguisher 100:1

[ASBR-PE1-vpn-instance-customerA] vpn-target 100:1 both

[ASBR-PE1-vpn-instance-customerA] quit

# Associate VLAN-interface 3 with VPN instance customerA.

[ASBR-PE1] interface vlan-interface 3

[ASBR-PE1-Vlan-interface3] ip binding vpn-instance customerA

[ASBR-PE1-Vlan-interface3] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 3.

[ASBR-PE1] multicast routing vpn-instance customerA

[ASBR-PE1-mrib-customerA] quit

[ASBR-PE1] interface vlan-interface 3

[ASBR-PE1-Vlan-interface3] pim sm

[ASBR-PE1-Vlan-interface3] quit

# On ASBR-PE 2, create VPN instance customerA.

[ASBR-PE2] ip vpn-instance customerA

[ASBR-PE2-vpn-vpn-customerA] route-distinguisher 200:1

[ASBR-PE2-vpn-vpn-customerA] vpn-target 200:1 both

[ASBR-PE2-vpn-vpn-customerA] quit

# Associate VLAN-interface 3 with VPN instance customerA.

[ASBR-PE2] interface vlan-interface 3

[ASBR-PE2-Vlan-interface3] ip binding vpn-instance customerA

[ASBR-PE2-Vlan-interface3] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 3.

[ASBR-PE2] multicast routing vpn-instance customerA

[ASBR-PE2-mrib-customerA] quit

[ASBR-PE2] interface vlan-interface 3

[ASBR-PE2-Vlan-interface3] pim sm

[ASBR-PE2-Vlan-interface3] quit

5. Configure the MD for the VPN instance:

# On PE 1, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group range for the MD.

[PE1] multicast-domain vpn-instance customerA

[PE1-md-customerA] default-group 239.1.1.1

[PE1-md-customerA] source loopback 1

[PE1-md-customerA] data-group 225.2.2.0 28

[PE1-md-customerA] quit

# On ASBR-PE 1, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group range for the MD.

[ASBR-PE1] multicast-domain vpn-instance customerA

[ASBR-PE1-md-customerA] default-group 239.1.1.1

[ASBR-PE1-md-customerA] source loopback 1

[ASBR-PE1-md-customerA] data-group 225.2.2.0 28

[ASBR-PE1-md-customerA] quit

# On PE 2, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group range for the MD.

[PE2] multicast-domain vpn-instance customerA

[PE2-md-customerA] default-group 239.1.1.1

[PE2-md-customerA] source loopback 1

[PE2-md-customerA] data-group 225.2.2.0 28

[PE2-md-customerA] quit

# On ASBR-PE 2, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group range for the MD.

[ASBR-PE2] multicast-domain vpn-instance customerA

[ASBR-PE2-md-customerA] default-group 239.1.1.1

[ASBR-PE2-md-customerA] source loopback 1

[ASBR-PE2-md-customerA] data-group 225.2.2.0 28

[ASBR-PE2-md-customerA] quit

Verifying the configuration

# Verify that the default-MDT has been established on the public network in each AS on PEs and ASBR-PEs. The following example shows PIM routing table for the public network on ASBR-PE 1.

[ASBR-PE1]display pim routing-table

Total 1 (*, G) entry; 1 (S, G) entry

(*, 239.1.1.1)

RP: 11.11.11.11 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 02:54:43

Upstream interface: Register

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface(s) information:

Total number of downstreams: 1

1: Vlan-interface2

Protocol: pim-sm, UpTime: 02:54:43, Expires: -

(1.1.1.1, 239.1.1.1)

RP: 11.11.11.11 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 01:57:13

Upstream interface: Vlan-interface2

Upstream neighbor: 192.168.1.2

RPF prime neighbor: 192.168.1.2

Downstream interface(s) information: None

The output shows that an RPT for (*, 239.1.1.1) and an SPT for (1.1.1.1, 239.1.1.1) have been established on the public network. The RPT and SPT constitute the default-MDT for the public network.

Configuration files

· PE 1:

ip vpn-instance customerA

route-distinguisher 100:1

vpn-target 100:1 import-extcommunity

vpn-target 100:1 export-extcommunity

vlan 2

vlan 11

interface LoopBack1

ip address 1.1.1.1 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.2 255.255.255.0

pim sm

interface Vlan-interface11

ip binding vpn-instance customerA

ip address 10.11.1.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· PE 2:

ip vpn-instance customerA

route-distinguisher 200:2

vpn-target 200:2 import-extcommunity

vpn-target 200:2 export-extcommunity

vlan 4

vlan 12

interface LoopBack1

ip address 1.1.1.4 255.255.255.255

pim sm

interface Vlan-interface4

ip address 192.168.3.1 255.255.255.0

pim sm

interface Vlan-interface12

ip binding vpn-instance customerA

ip address 10.11.2.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· ASBR-PE 1:

ip vpn-instance customerA

route-distinguisher 100:1

vpn-target 100:1 import-extcommunity

vpn-target 100:1 export-extcommunity

vlan 2 to 3

interface LoopBack1

ip address 1.1.1.2 255.255.255.255

pim sm

interface LoopBack2

ip address 11.11.11.11 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.1 255.255.255.0

pim sm

interface Vlan-interface3

ip binding vpn-instance customerA

ip address 192.168.2.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

pim

c-bsr 11.11.11.11

c-rp 11.11.11.11

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· ASBR-PE 2:

ip vpn-instance customerA

route-distinguisher 200:1

vpn-target 200:1 import-extcommunity

vpn-target 200:1 export-extcommunity

vlan 3 to 4

interface LoopBack1

ip address 1.1.1.3 255.255.255.255

pim sm

interface LoopBack2

ip address 22.22.22.22 255.255.255.255

pim sm

interface Vlan-interface3

ip binding vpn-instance customerA

ip address 192.168.2.2 255.255.255.0

pim sm

interface Vlan-interface4

ip address 192.168.3.2 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

pim

c-bsr 22.22.22.22

c-rp 22.22.22.22

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· CE a1:

vlan 10 to 11

interface LoopBack0

ip address 2.2.2.2 255.255.255.255

pim sm

interface Vlan-interface10

ip address 10.11.3.1 255.255.255.0

pim sm

interface Vlan-interface11

ip address 10.11.1.2 255.255.255.0

pim sm

multicast routing

pim

c-bsr 2.2.2.2

c-rp 2.2.2.2

· CE a2:

vlan 12

vlan 20

interface Vlan-interface12

ip address 10.11.2.2 255.255.255.0

pim sm

interface Vlan-interface20

ip address 10.11.4.1 255.255.255.0

igmp enable

multicast routing

Example: Configuring inter-AS option C MD VPN

Network requirements

As shown in Figure 3:

· Customer A has two branches that separately connect to AS 100 and AS 200.

· ASBR-PE 1 and ASBR-PE 2 are interconnected by using the inter-AS option C solution.

· PIM-SM runs within the two branches.

· The multicast source and the receiver host are in different branches.

Configure inter-AS option C MD VPN so that the receiver host can receive the multicast data from the source.

Figure 3 Network diagram

Table 3 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
S 1	—	10.11.3.2/24	R 1	—	10.11.4.2/24
PE 1	VLAN-interface 2	192.168.1.2/24	ASBR-PE2	VLAN-interface 4	192.168.3.2/24
PE 1	VLAN-interface 11	10.11.1.1/24	ASBR-PE2	VLAN-interface 3	192.168.2.2/24
PE 1	Loopback 1	1.1.1.1/32	ASBR-PE2	Loopback 1	1.1.1.3/32
ASBR-PE1	VLAN-interface 2	192.168.1.1/24	ASBR-PE2	Loopback 2	22.22.22.22/32
ASBR-PE1	VLAN-interface 3	192.168.2.1/24	PE 2	VLAN-interface 4	192.168.3.1/24
ASBR-PE1	Loopback 1	1.1.1.2/32	PE 2	VLAN-interface 12	10.11.2.1/24
ASBR-PE1	Loopback 2	11.11.11.11/32	PE 2	Loopback 1	1.1.1.4/32
CE a1	VLAN-interface 10	10.11.3.1/24	CE a2	VLAN-interface 20	10.11.4.1/24
CE a1	VLAN-interface 11	10.11.1.2/24	CE a2	VLAN-interface 12	10.11.2.2/24
CE a1	Loopback 0	2.2.2.2/32

Requirements analysis

To meet the network requirement, you must perform the following tasks:

· Create the same MD for each AS.

· Establish MSDP peering relationships between the RPs in the ASs to share the multicast source information in different PIM-SM domains.

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you configure inter-AS option C MD VPN, follow these restrictions and guidelines:

· If the system operates in standard mode, you must specify a different reserved VLAN for each VPN instance. Otherwise, system exceptions might occur.

Do not change the reserved VLAN for a VPN instance. Otherwise, you must reconfigure the multicast VPN.

For more information about reserved VLANs, see MPLS Configuration Guide. For more information about system operating modes, see Fundamentals Configuration Guide.

Configuration procedures

1. Assign an IP address and subnet mask to each interface on CE a1 according to Table 3.

<CEa1> system-view

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] ip address 10.11.3.1 24

[CEa1-Vlan-interface10] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] ip address 2.2.2.2 32

[CEa1-LoopBack0] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] ip address 10.11.1.2 24

[CEa1-Vlan-interface11] quit

# Configure PE 1, ASBR-PE 1, ASBR-PE 2, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)

2. Configure a unicast routing protocol and basic MPLS VPN on all devices so that all devices are interoperable at the network layer. (Details not shown)

For more information about configuring basic MPLS VPN, see MPLS Configuration Guide.

3. Enable IP multicast routing on the public network in each AS, enable PIM-SM on the public network interfaces (including Loopback interfaces), and configure PIM-SM domain boarders:

# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE1] multicast routing

[PE1-mrib] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] pim sm

[PE1-Vlan-interface2] quit

[PE1] interface loopback 1

[PE1-LoopBack1] pim sm

[PE1-LoopBack1] quit

# On ASBR-PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[ASBR-PE1] multicast routing

[ASBR-PE1-mrib] quit

[ASBR-PE1] interface vlan-interface 2

[ASBR-PE1-Vlan-interface2] pim sm

[ASBR-PE1-Vlan-interface2] quit

[ASBR-PE1] interface vlan-interface 3

[ASBR-PE1-Vlan-interface3] pim sm

[ASBR-PE1-Vlan-interface3] quit

[ASBR-PE1] interface loopback 1

[ASBR-PE1-LoopBack1] pim sm

[ASBR-PE1-LoopBack1] quit

[ASBR-PE1] interface loopback 2

[ASBR-PE1-LoopBack2] pim sm

[ASBR-PE1-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP.

[ASBR-PE1] pim

[ASBR-PE1-pim] c-bsr 11.11.11.11

[ASBR-PE1-pim] c-rp 11.11.11.11

[ASBR-PE1-pim] quit

# Configure VLAN-interface 3 as a PIM-SM domain boarder.

[ASBR-PE1] interface vlan-interface 3

[ASBR-PE1-Vlan-interface3] pim bsr-boundary

[ASBR-PE1-Vlan-interface3] quit

# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[PE2] multicast routing

[PE2-mrib] quit

[PE2] interface vlan-interface 4

[PE2-Vlan-interface4] pim sm

[PE2-Vlan-interface4] quit

[PE2] interface loopback 1

[PE2-LoopBack1] pim sm

[PE2-LoopBack1] quit

# On ASBR-PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.

[ASBR-PE2] multicast routing

[ASBR-PE2-mrib] quit

[ASBR-PE2] interface vlan-interface 3

[ASBR-PE2-Vlan-interface3] pim sm

[ASBR-PE2-Vlan-interface3] quit

[ASBR-PE2] interface vlan-interface 4

[ASBR-PE2-Vlan-interface4] pim sm

[ASBR-PE2-Vlan-interface4] quit

[ASBR-PE2] interface loopback 1

[ASBR-PE2-LoopBack1] pim sm

[ASBR-PE2-LoopBack1] quit

[ASBR-PE2] interface loopback 2

[ASBR-PE2-LoopBack2] pim sm

[ASBR-PE2-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP.

[ASBR-PE2] pim

[ASBR-PE2-pim] c-bsr 22.22.22.22

[ASBR-PE2-pim] c-rp 22.22.22.22

[ASBR-PE2-pim] quit

# Configure VLAN-interface 3 as a PIM-SM domain boarder.

[ASBR-PE2] interface vlan-interface 3

[ASBR-PE2-Vlan-interface3] pim bsr-boundary

[ASBR-PE2-Vlan-interface3] quit

4. Establish MSDP peering relationships between the RPs on the public network in the ASs:

# On ASBR-PE 1, specify an MSDP peer.

[ASBR-PE1] msdp

[ASBR-PE1-msdp] encap-data-enable

[ASBR-PE1-msdp] peer 192.168.2.2 connect-interface vlan-interface 3

# On ASBR-PE 2, specify an MSDP peer.

[ASBR-PE2] msdp

[ASBR-PE2-msdp] encap-data-enable

[ASBR-PE2-msdp] peer 192.168.2.1 connect-interface vlan-interface 3

5. Enable IP multicast routing for the VPN instance, enable PIM-SM on the private network interfaces, and enable IGMP on the interfaces that have receiver hosts attached:

NOTE:

The route targets for the same VPN instance on the ASBRs and PEs within the same AS must match. Those within different ASs do not need to match.

# On CE a1, enable IP multicast routing, and enable PIM-SM on each interface.

[CEa1] multicast routing

[CEa1-mrib] quit

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] pim sm

[CEa1-Vlan-interface10] quit

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] pim sm

[CEa1-Vlan-interface11] quit

[CEa1] interface loopback 0

[CEa1-LoopBack0] pim sm

[CEa1-LoopBack0] quit

# Configure Loopback 0 as a C-BSR and a C-RP.

[CEa1] pim

[CEa1-pim] c-bsr 2.2.2.2

[CEa1-pim] c-rp 2.2.2.2

[CEa1-pim] quit

# On CE a2, enable IP multicast routing, enable PIM-SM on VLAN-interface 12, and enable IGMP on VLAN-interface 20.

[CEa2] multicast routing

[CEa2-mrib] quit

[CEa2] interface vlan-interface 12

[CEa2-Vlan-interface12] pim sm

[CEa2-Vlan-interface12] quit

[CEa2] interface vlan-interface 20

[CEa2-Vlan-interface20] igmp enable

[CEa2-Vlan-interface20] quit

# On PE 1, create VPN instance customerA.

[PE1] ip vpn-instance customerA

[PE1-vpn-instance-customerA] route-distinguisher 11:11

[PE1-vpn-instance-customerA] vpn-target 3:3 import-extcommunity

[PE1-vpn-instance-customerA] vpn-target 3:3 export-extcommunity

[PE1-vpn-instance-customerA] quit

# Associate VLAN-interface 11 with VPN instance customerA.

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] ip binding vpn-instance customerA

[PE1-Vlan-interface11] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 11.

[PE1] multicast routing vpn-instance customerA

[PE1-mrib-customerA] quit

[PE1] interface vlan-interface 11

[PE1-Vlan-interface11] pim sm

[PE1-Vlan-interface11] quit

# On PE 2, create VPN instance customerA.

[PE2] ip vpn-instance customerA

[PE2-vpn-instance-customerA] route-distinguisher 12:12

[PE2-vpn-instance-customerA] vpn-target 3:3 import-extcommunity

[PE2-vpn-instance-customerA] vpn-target 3:3 export-extcommunity

[PE2-vpn-instance] quit

# Associate VLAN-interface 12 with VPN instance customerA.

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] ip binding vpn-instance customerA

[PE2-Vlan-interface12] quit

# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on VLAN-interface 12.

[PE2] multicast routing vpn-instance customerA

[PE2-mrib-customerA] quit

[PE2] interface vlan-interface 12

[PE2-Vlan-interface12] pim sm

[PE2-Vlan-interface12] quit

6. Create the same MD for the ASs, and specify the default-group, MD source interface, and data-group for the MD:

# On PE 1, create an MD for the VPN instance customerA, and specify the default-group, MD source interface, and data-group.

[PE1] multicast-domain vpn-instance customerA

[PE1-md-customerA] default-group 239.1.1.1

[PE1-md-customerA] source loopback 1

[PE1-md-customerA] data-group 225.2.2.0 28

[PE1-md-customerA] quit

# On PE 2, create an MD for VPN instance customerA, and specify the default-group, MD source interface, and data-group.

[PE2] multicast-domain vpn-instance customerA

[PE2-md-customerA] default-group 239.1.1.1

[PE2-md-customerA] source loopback 1

[PE2-md-customerA] data-group 225.2.2.0 28

[PE2-md-customerA] quit

Verifying the configuration

# Verify that the default-MDT has been established on the public network in each AS on PEs and ASBR-PEs. The following example shows PIM routing table for the public network on ASBR-PE 1.

[ASBR-PE1]display pim routing-table

Total 1 (*, G) entry; 2 (S, G) entry

(*, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 02:54:43

Upstream interface: Register

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface(s) information:

Total number of downstreams: 1

1: Vlan-interface2

Protocol: pim-sm, UpTime: 02:54:43, Expires: -

(1.1.1.1, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 01:57:13

Upstream interface: Vlan-interface2

Upstream neighbor: 192.168.1.2

RPF prime neighbor: 192.168.1.2

Downstream interface(s) information: None

(1.1.1.4, 239.1.1.1)

RP: 3.3.3.3 (local)

Protocol: pim-sm, Flag: SPT LOC ACT

UpTime: 01:57:13

Upstream interface: Vlan-interface3

Upstream neighbor: 192.168.2.2

RPF prime neighbor: 192.168.2.2

Downstream interface(s) information: None

The output shows that an RPT for (*, 239.1.1.1), an SPT for (1.1.1.1, 239.1.1.1), and an SPT for (1.1.1.4, 239.1.1.1) have been established on the public network. The RPT and SPTs constitute the default-MDT for the public network.

Configuration files

· PE 1:

ip vpn-instance customerA

route-distinguisher 11:11

vpn-target 3:3 import-extcommunity

vpn-target 3:3 export-extcommunity

vlan 2

vlan 11

interface LoopBack1

ip address 1.1.1.1 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.2 255.255.255.0

pim sm

interface Vlan-interface11

ip binding vpn-instance customerA

ip address 10.11.1.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· PE 2:

ip vpn-instance customerA

route-distinguisher 12:12

vpn-target 3:3 import-extcommunity

vpn-target 3:3 export-extcommunity

vlan 4

vlan 12

interface LoopBack1

ip address 1.1.1.4 255.255.255.255

pim sm

interface Vlan-interface4

ip address 192.168.3.1 255.255.255.0

pim sm

interface Vlan-interface12

ip binding vpn-instance customerA

ip address 10.11.2.1 255.255.255.0

pim sm

multicast routing

multicast routing vpn-instance customerA

multicast-domain vpn-instance customerA

source LoopBack1

default-group 239.1.1.1

data-group 225.1.1.0 255.255.255.240

· ASBR-PE 1:

vlan 2 to 3

interface LoopBack1

ip address 1.1.1.2 255.255.255.255

pim sm

interface LoopBack2

ip address 11.11.11.11 255.255.255.255

pim sm

interface Vlan-interface2

ip address 192.168.1.1 255.255.255.0

pim sm

interface Vlan-interface3

ip address 192.168.2.1 255.255.255.0

pim sm

pim bsr-boundary

multicast routing

pim

c-bsr 11.11.11.11

c-rp 11.11.11.11

msdp

encap-data-enable

peer 192.168.2.2 connect-interface Vlan-interface3

· ASBR-PE 2:

vlan 3 to 4

interface LoopBack1

ip address 1.1.1.3 255.255.255.255

pim sm

interface LoopBack2

ip address 22.22.22.22 255.255.255.255

pim sm

interface Vlan-interface3

ip address 192.168.2.2 255.255.255.0

pim sm

pim bsr-boundary

interface Vlan-interface4

ip address 192.168.3.2 255.255.255.0

pim sm

multicast routing

pim

c-bsr 22.22.22.22

c-rp 22.22.22.22

msdp

encap-data-enable

peer 192.168.2.1 connect-interface Vlan-interface3

· CE a1:

vlan 10 to 11

interface LoopBack0

ip address 2.2.2.2 255.255.255.255

pim sm

interface Vlan-interface10

ip address 10.11.3.1 255.255.255.0

pim sm

interface Vlan-interface11

ip address 10.11.1.2 255.255.255.0

pim sm

multicast routing

pim

c-bsr 2.2.2.2

c-rp 2.2.2.2

· CE a2:

vlan 12

vlan 20

interface Vlan-interface12

ip address 10.11.2.2 255.255.255.0

pim sm

interface Vlan-interface20

ip address 10.11.4.1 255.255.255.0

igmp enable

multicast routing

06-IP Multicast Configuration Examples

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us