· Provider edge (PE) device—Edge device on the public network. A PE device directly connects to one or more customer edge (CE) devices and processes VPN routing.

· CE device—Edge device on a customer network. A CE device implements route distribution on the customer network. The device can be a router, a switch, or a host.

As shown in Figure 1, the network that runs multicast VPN provides independent multicast services for the public network, VPN A, and VPN B. The multicast device PE supports multiple VPN instances and acts as multiple independent multicast devices. Each VPN forms a plane, and all these planes are isolated from each other. For example, in Figure 1, PE 1 supports the public network, VPN A, and VPN B. You can consider these instances on PE 1 to be independent virtual devices, which are PE 1', PE 1", and PE 1'". Each virtual device works on a plane, as shown in Figure 2.

Figure 2 Multicast in multiple VPN instances

Through multicast VPN, multicast data of VPN A for a multicast group can only arrive at receiver hosts in Site 1, Site 3, and Site 5 of VPN A. The stream is multicast in these sites and on the public network.

The prerequisites for implementing multicast VPN are as follows:

1. Within each site, multicast for a single VPN instance is supported.

2. On the public network, multicast for the public network is supported.

3. The PE devices support multiple VPN instances as follows:

¡ Connecting with different sites through VPN instances and supporting multicast for each VPN instance.

¡ Connecting with the public network and supporting multicast for the public network.

¡ Supporting information exchange and data conversion between the public network and VPNs.

The device implements multicast VPN by using the multicast domain (MD) method. This multicast VPN implementation is referred to as MD VPN.

The most significant advantage of MD VPN is that it requires only the PE devices to support multiple VPN instances. There is no need to upgrade CE devices and P devices or change their original PIM configurations. Therefore, the MD VPN solution is transparent to CE devices and P devices.

MD VPN overview

The basic MD VPN concepts are described in Table 1.

Table 1 Basic MD VPN concepts

Concept	Description
Multicast domain (MD)	An MD is a set of PE devices that are in the same VPN instance. Each MD uniquely corresponds to a VPN instance.
Multicast distribution tree (MDT)	An MDT is a multicast distribution tree constructed by all PE devices in the same VPN. MDT types include default-MDT and data-MDT.
Multicast tunnel (MT)	An MT is a tunnel that interconnects all PEs in an MD for delivering VPN traffic within the MD.
Multicast tunnel interface (MTI)	An MTI is the entrance or exit of an MT, equivalent to an entrance or exit of an MD. PE devices use the MTI to access the MT. An MTI handles only multicast packets, not unicast packets. The MTI interfaces are automatically created when the MD for the VPN instance is created.
Default-group	On the public network, each MD is assigned a unique multicast address, called a default-group. A default-group is the unique identifier of an MD on the public network. It helps build the default-MDT for an MD on the public network.
Default-MDT	A default-MDT uses a default-group address as its group address. In a VPN, the default-MDT is uniquely identified by the default-group. A default-MDT is automatically created after the default-group is specified and will always exist on the public network, regardless of the presence of any multicast services on the public network or the VPN.
Data-group	When the multicast traffic of a VPN reaches or exceeds a threshold, the ingress PE device assigns it an independent multicast address called data-group. It also notifies other PE devices that they must use this address to forward the multicast traffic for that VPN. This initiates the switchover to the data-MDT.
Data-MDT	A data-MDT is an MDT that uses a data-group as it group address. At MDT switchover, PE devices with downstream receivers join a data-group, building a data-MDT. The ingress PE forwards the encapsulated VPN multicast traffic along the data-MDT over the public network.

Introduction to MD VPN

The main points in MD VPN implementation are as follows:

· The public network of the service provider supports multicast:

¡ The PE devices must support the public network and multiple VPN instances.

¡ Each instance runs PIM independently.

VPN multicast traffic between the PE devices and the CE devices is transmitted on a per-VPN-instance basis. However, the public network multicast traffic between the PE devices and the P devices is transmitted through the public network.

· An MD logically defines the transmission boundary of the multicast traffic of a specific VPN over the public network. It also physically identifies all the PE devices that support that VPN instance on the public network. Different VPN instances correspond to different MDs.

As shown in Figure 2, the ellipse area in the center of each VPN instance plane represents an MD that provides services for a particular VPN instance. All the VPN multicast traffic in that VPN is transmitted within that MD.

· Inside an MD, all the private traffic is transmitted through the MT. The process of multicast traffic transmission through an MT is as follows:

a. The local PE device encapsulates a VPN multicast packet into a public network multicast packet.

b. The encapsulated multicast packet is sent by the PE device and travels over the public network.

c. After receiving the multicast packet, the remote PE device decapsulates the multicast packet to get the original VPN multicast packet.

· The local PE device sends VPN data out of the MTI. The remote PE devices receive the private data from their MTI interfaces.

As shown in Figure 3, you can think of an MD as a private data transmission pool and an MTI as an entrance or exit of the pool. The local PE device puts the private data into the transmission pool (MD) through the entrance (MTI). The transmission pool automatically duplicates the private data and transmits the data to each exit (MTI) of the transmission pool. Then, a remote PE device that needs the data can get it from its exit (MTI).

Figure 3 Relationship between PIM on the public network and an MD in a VPN instance

· Each VPN instance is assigned a unique default-group address. The VPN data is transparent to the public network.

A PE device encapsulates a VPN multicast packet (a multicast protocol packet or a multicast data packet) into a public network multicast packet. The default-group address is used as the public network multicast group. Then, the PE sends this multicast packet to the public network.

· A default-group corresponds to a unique MD. For each default-group, a unique default-MDT is constructed through the public network resources for multicast data forwarding. All the VPN multicast packets transmitted in this VPN are forwarded along this default-MDT, regardless of which PE device they used to enter the public network.

· An MD is assigned a unique data-group address range for MDT switchover. When the rate of a VPN multicast stream that entered the public network at a PE device reaches or exceeds the switchover threshold, the PE does the following:

¡ Selects an address that is least referenced from the data-group address range.

¡ Uses the address to encapsulate the multicast packets for that VPN.

· All the PE devices on the network monitor the forwarding rate on the default-MDT.

a. When the rate of a VPN multicast stream that entered the public network at a specific PE device exceeds the threshold, the PE device creates an MDT switchover message. The message travels to the downstream along the default-MDT. This causes a data-MDT to be built by using the data-group between that PE device and the remote PE devices with downstream receivers.

b. After a data-delay period has passed, an MDT switchover process starts. All VPN multicast packets that have entered the public network through that PE device are not encapsulated with the default-group address. They are encapsulated into public network multicast packets with the data-group address. Then they are switched from the default-MDT to the data-MDT.

For more information about MDT switchover, see "MDT switchover."

NOTE:

A VPN uniquely corresponds to an MD and an MD provides services for only one VPN, which is called a one-to-one relationship. Such a relationship exists between VPN, MD, MTI, default-group, and the data-group address range.

PIM neighboring relationships in MD VPN

Figure 4 PIM neighboring relationships in MD VPN

PIM neighboring relationships are established between two or more directly interconnected devices on the same subnet. As shown in Figure 4, the following types of PIM neighboring relationships exist in MD VPN:

· PE-P PIM neighboring relationship—Established between the public network interface on a PE device and the peer interface on the P device over the link.

· PE-PE PIM neighboring relationship—Established between PE devices that are in the same VPN instance after they receive the PIM hello packets.

· PE-CE PIM neighboring relationship—Established between a PE interface that is bound with the VPN instance and the peer interface on the CE device over the link.

Protocols and standards

RFC 6037, Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs

How MD VPN works

This section describes default-MDT establishment, multicast traffic delivery based on the default-MDT, and inter-AS MD VPN implementation.

For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE. This implements the seamless transmission of the VPN data over the public network. However, the multicast data transmission process (the MDT transmission process) over the public network is very complicated.

Default-MDT establishment

The multicast routing protocol running on the public network can be PIM-DM, PIM-SM, or PIM-SSM. The process of creating a default-MDT is different in these PIM modes.

In multicast VPN applications, the public network does not support BIDIR-PIM. For more information about BIDIR-PIM, see "Configuring PIM."

Default-MDT establishment in a PIM-DM network

Figure 5 Default-MDT establishment in a PIM-DM network

As shown in Figure 5, PIM-DM is enabled on the network, and all the PE devices support the VPN instance A. The process of establishing a default-MDT is as follows:

1. To establish PIM neighboring relationships with PE 2 and PE 3 through the MTI in VPN instance A, PE 1 performs the following actions:

a. Encapsulates the PIM protocol packet of the private network into a public network multicast data packet. PE 1 does this by specifying the source address as the IP address of the MD source interface and the multicast group address as the default-group address.

b. Sends the multicast data packet to the public network.

This action triggers a flood-prune process on the public network. Other PE devices that belong to VPN instance A are members of the default group. Each device along the transmission path of the packet on the public network creates an (11.1.1.1, 239.1.1.1) state entry. This forms an SPT with PE 1 as the root, and PE 2 and PE 3 as leaves.

2. At the same time, PE 2 and PE 3 separately initiate a similar flood-prune process.

Finally, three independent SPTs are established in the MD, constituting a default-MDT in the PIM-DM network.

Default-MDT establishment in a PIM-SM network

Figure 6 Default-MDT establishment in a PIM-SM network

As shown in Figure 6, PIM-SM is enabled on the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows:

1. PE 1 initiates a join to the public network RP by specifying the multicast group address as the default-group address in the join message. A (*, 239.1.1.1) state entry is created on each device along the path on the public network.

2. At the same time, PE 2 and PE 3 separately initiate a similar join process.

Finally, an RPT is established in the MD, with the public network RP as the root and PE 1, PE 2, and PE 3 as leaves.

3. To establish PIM neighboring relationships with PE 2 and PE 3 through the MTI in VPN instance A, PE 1 performs the following actions:

b. Sends the multicast data packet to the public network.

This action triggers the registration of the multicast source with the public network RP. Then, the public network RP initiates a join to PE 1. An (11.1.1.1, 239.1.1.1) state entry is created on each device along the path on the public network.

4. At the same time, PE 2 and PE 3 separately initiate a similar register process.

Finally, three SPTs between the PE devices and the RP are established in the MD.

In the PIM-SM network, the RPT, or the (*, 239.1.1.1) tree, and the three independent SPTs constitute a default-MDT.

Default-MDT establishment in a PIM-SSM network

Figure 7 Default-MDT establishment in a PIM-SSM network

As shown in Figure 7, PIM-SSM runs on the public network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows:

1. PE 1, PE 2, and PE 3 exchange MDT route information (including BGP interface address and the default-group address) through BGP.

2. PE 1 sends a subscribe message to PE 2 and PE 3. Each device along the transmission path on the public network creates an (11.1.1.1, 239.1.1.1) state entry. An SPT is established in the MD with PE 1 as the root and PE 2 and PE 3 as the leaves.

At the same time, PE 2 and PE 3 separately initiate a similar process, and establish an SPT with itself as the root and the other PEs as the leaves.

3. The three independent SPTs constitute the default-MDT in the PIM-SSM network.

In PIM-SSM, the term "subscribe message" refers to a join message.

Default-MDT characteristics

No matter which PIM mode is running on the public network, the default-MDT has the following characteristics:

· All PE devices that support the same VPN instance join the default-MDT.

· All multicast packets that belong to this VPN are forwarded along the default-MDT to every PE device on the public network, even if no active downstream receivers exist.

Default-MDT-based delivery

The default-MDT delivers multicast protocol packets and multicast data packets differently.

Multicast protocol packet delivery

To forward the multicast protocol packets of a VPN over the public network, the local PE device encapsulates them into public network multicast data packets. These packets are transmitted along the default-MDT and are then decapsulated on the remote PE device to go into the normal protocol procedure. Finally a distribution tree is established across the public network.

The following describes how multicast protocol packets are forwarded in different circumstances:

· If the VPN network runs PIM-DM or PIM-SSM:

¡ Hello packets are forwarded through MTI interfaces to establish PIM neighboring relationships.

¡ A flood-prune process (in PIM-DM) or a join process (in PIM-SSM) is initiated across the public network to establish an SPT across the public network.

· If the VPN network runs PIM-SM:

¡ Hello packets are forwarded through MTI interfaces to establish PIM neighboring relationships.

¡ If the receivers and the VPN RP are in different sites, a join process is initiated across the public network to establish an RPT.

¡ If the multicast source and the VPN RP are in different sites, a registration process is initiated across the public network to establish an SPT.

NOTE:

PIM mode must be the same for all interfaces that belong to the same VPN, including those interfaces that are bound with the VPN instance and the MTI interfaces on PE devices.

As shown in Figure 8:

· PIM-SM is running in both the public network and the VPN network.

· Receiver for the VPN multicast group G (225.1.1.1) in Site 2 is attached to CE 2.

· CE 1 of Site 1 acts as the RP for group G (225.1.1.1).

· The default-group address used to forward public network data is 239.1.1.1.

Figure 8 Transmission of multicast protocol packets

The multicast protocol packet is delivered as follows:

1. Receiver sends an IGMP report to CE 2 to join the multicast group G. CE 2 creates a local state entry (*, 225.1.1.1) and sends a join message to the VPN RP (CE 1).

2. After receiving the join message from CE 2, the VPN instance on PE 2 creates a state entry (*, 225.1.1.1) and specifies the MTI interface as the upstream interface. The VPN instance on PE 2 considers the join message to have been sent out of the MTI interface, because step 3 is transparent to the VPN instance.

3. PE 2 encapsulates the join message into a public network multicast data packet (11.1.2.1, 239.1.1.1) by using the GRE method. In this multicast data packet, the source address is the MD source interface IP address 11.1.2.1, and the destination address is the default-group address 239.1.1.1. PE 2 then forwards this packet to the public network.

4. The default-MDT forwards the multicast data packet (11.1.2.1, 239.1.1.1) to the public network instance on all the PE devices. After receiving this packet, every PE device decapsulates it to get the original join message to be sent to the VPN RP. Then, each PE device examines the VPN RP address in the join message. If the VPN RP is in the site to which a PE device is connected, the PE passes the join message to the VPN instance on the PE. Otherwise, the PE discards the join message.

5. When receiving the join message, the VPN instance on PE 1 considers the received message to be from the MTI. PE 1 creates a local state entry (*, 225.1.1.1), with the downstream interface being the MTI and the upstream interface being the one that leads to CE 1. At the same time, the VPN instance sends a join message to CE 1, which is the VPN RP.

6. After receiving the join message from the VPN instance on PE 1, CE 1 creates a local state entry (*, 225.1.1.1) or updates the entry if the entry already exists.

By now, the construction of an RPT across the public network is completed.

Multicast data packet delivery

After the default-MDT is established, the multicast source forwards the VPN multicast data to the receivers in each site along the default-MDT. The VPN multicast packets are encapsulated into public network multicast packets on the local PE device, and transmitted along the default-MDT. Then, they are decapsulated on the remote PE device and transmitted in that VPN site.

VPN multicast data packets are forwarded across the public network differently in the following circumstances:

· If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data packets to the receivers along the VPN SPT across the public network.

· When PIM-SM is running in the VPN:

¡ Before the RPT-to-SPT switchover, if the multicast source and the VPN RP are in different sites, the VPN multicast data packets travel to the VPN RP along the VPN SPT across the public network. If the VPN RP and the receivers are in different sites, the VPN multicast data packets travel to the receivers along the VPN RPT over the public network.

¡ After the RPT-to-SPT switchover, if the multicast source and the receivers are in different sites, the VPN multicast data packets travel to the receivers along the VPN SPT across the public network.

· When BIDIR-PIM is running in the VPN, if the multicast source and the VPN RP are in different sites, the multicast source sends multicast data to the VPN RP across the public network along the source-side RPT. If the VPN RP and the receivers are in different sites, the multicast data packets travel to the receivers across the public network along the receiver-side RPT.

For more information about RPT-to-SPT switchover, see "Configuring PIM."

The following example explains how multicast data packets are delivered based on the default-MDT when PIM-DM is running in both the public network and the VPN network.

As shown in Figure 9:

· PIM-DM is running in both the public network and the VPN sites.

· Receiver of the VPN multicast group G (225.1.1.1) in Site 2 is attached to CE 2.

· Source in Site 1 sends multicast data to multicast group (G).

· The default-group address used to forward public network multicast data is 239.1.1.1.

Figure 9 Multicast data packet delivery

A VPN multicast data packet is delivered across the public network as follows:

1. Source sends a VPN multicast data packet (192.1.1.1, 225.1.1.1) to CE 1.

2. CE 1 forwards the VPN multicast data packet along an SPT to PE 1, and the VPN instance on PE 1 examines the MVRF.

If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data packet as described in step 3. The VPN instance on PE 1 considers the VPN multicast data packet to have been sent out of the MTI, because step 3 is transparent to it.

3. PE 1 encapsulates the VPN multicast data packet into a public network multicast packet (11.1.1.1, 239.1.1.1) by using the GRE method. The source IP address of the packet is the MD source interface 11.1.1.1, and the destination address is the default-group address 239.1.1.1. PE 1 then forwards it to the public network.

4. The default-MDT forwards the multicast data packet (11.1.1.1, 239.1.1.1) to the public network instance on all the PE devices. After receiving this packet, every PE device decapsulates it to get the original VPN multicast data packet, and passes it to the corresponding VPN instance. If a PE device has a downstream interface for an SPT, it forwards the VPN multicast packet down the SPT. Otherwise, it discards the packet.

5. The VPN instance on PE 2 looks up the MVRF and finally delivers the VPN multicast data to Receiver.

By now, the process of transmitting a VPN multicast data packet across the public network is completed.

MDT switchover

Switching from default-MDT to data-MDT

When a multicast packet of a VPN is transmitted through the default-MDT on the public network, the packet is forwarded to all PE devices that support that VPN instance. This occurs whether or not any active receivers exist in the attached sites. When the rate of the multicast traffic of that VPN is high, multicast data might get flooded on the public network. This increases the bandwidth use and brings extra burden on the PE devices.

To optimize multicast transmission of large VPN multicast traffic that enters the public network, the MD solution introduces a dedicated data-MDT. The data-MDT is built between the PE devices that connect VPN multicast receivers and multicast sources. When specific network criteria are met, a switchover from the default-MDT to the data-MDT occurs to forward VPN multicast traffic to receivers.

The process of default-MDT to data-MDT switchover is as follows:

1. The source-side PE device (PE 1, for example) periodically examines the forwarding rate of the VPN multicast traffic. The default-MDT switches to the data-MDT only when the following criteria are both met:

¡ The VPN multicast data has passed the ACL rule filtering for default-MDT to data-MDT switchover.

¡ The traffic rate of the VPN multicast stream has exceeded the switchover threshold and stayed higher than the threshold for a certain length of time.

2. PE 1 selects a least-referenced address from the data-group address range. Then, it sends an MDT switchover message to all the other PE devices down the default-MDT. This message contains the VPN multicast source address, the VPN multicast group address, and the data-group address.

3. Each PE device that receives this message examines whether it interfaces with a VPN that has receivers of that VPN multicast stream.

If so, it joins the data-MDT rooted at PE 1. Otherwise, it caches the message and will join the data-MDT when it has attached receivers.

4. After sending the MDT switchover message, PE 1 waits a certain length of time (known as the data-delay period). Then, it starts using the default-group address to encapsulate the VPN multicast data. The multicast data is then forwarded down the data-MDT.

5. After the multicast traffic is switched from the default-MDT to the data-MDT, PE 1 continues sending MDT switchover messages periodically. Subsequent PE devices with attached receivers can then join the data-MDT. When a downstream PE device no longer has active receivers attached to it, it leaves the data-MDT.

For a given VPN instance, the default-MDT and the data-MDT are both forwarding tunnels in the same MD. A default-MDT is uniquely identified by a default-group address, and a data-MDT is uniquely identified by a data-group address. Each default-group is uniquely associated with a data-group address range.

Backward switching from data-MDT to default-MDT

After the VPN multicast traffic is switched to the data-MDT, the multicast traffic conditions might change and no longer meet the switchover criterion. In this case, PE 1, as in the preceding example, initiates a backward MDT switchover process when any of the following criteria are met:

· The traffic rate of the VPN multicast data has dropped below the switchover threshold. In addition, the traffic rate has stayed lower than the threshold for a certain length of time (known as the data-holddown period).

· The associated data-group address range is changed, and the data-group address for encapsulating the VPN multicast data is out of the new address range.

· The ACL rule for controlling the switchover from the default-MDT to the data-MDT has changed, and the VPN multicast data fails to pass the new ACL rule.

Inter-AS MD VPN

In an inter-AS VPN networking scenario, VPN sites are located in multiple ASs. These sites must be interconnected. Inter-AS VPN provides the following solutions:

· VRF-to-VRF connections between ASBRs—This solution is also called inter-AS option A.

· EBGP redistribution of labeled VPN-IPv4 routes between ASBRs—ASBRs advertise VPN-IPv4 routes to each other through MP-EBGP. This solution is also called inter-AS option B.

The switch does no support inter-AS option B.

· Multihop EBGP redistribution of labeled VPN-IPv4 routes between PE routers—PEs advertise VPN-IPv4 routes to each other through MP-EBGP. This solution is also called inter-AS option C.

For more information about the three inter-AS VPN solutions, see "Configuring MPLS L3VPN."

Based on these solutions, the following ways are available to implement inter-AS MD VPN:

· MD VPN inter-AS option A

· MD VPN inter-AS option C

MD VPN inter-AS option A

As shown in Figure 10:

· Two VPN instances are in AS 1 and AS 2.

· PE 3 and PE 4 are ASBRs for AS 1 and AS 2, respectively.

· PE 3 and PE 4 are interconnected through their respective VPN instance and treat each other as a CE device.

Figure 10 MD VPN inter-AS option A

To implement MD VPN inter-AS option A, a separate MD must be created in each AS. VPN multicast data is transmitted between the VPNs in different ASs through the MDs.

A multicast packet of VPN instance 1 is delivered as follows:

1. CE 1 forwards the multicast packet of VPN instance 1 to PE 1.

2. PE 1 encapsulates the multicast packet into a public network packet and forwards it to PE 3 through the MTI interface in MD 1.

3. PE 3 treats PE 4 as a CE device of VPN instance 1, so PE 3 forwards the multicast packet to PE 4.

4. PE 4 treats PE 3 as a CE device of VPN instance 2, so it forwards the multicast packet to PE 2 through the MTI interface in MD 2 on the public network.

5. PE 2 forwards the multicast packet to CE 2.

Because only VPN multicast data is forwarded between ASBRs, different PIM modes can run within different ASs. However, the same PIM mode must run on all interfaces that belong to the same VPN (including interfaces with VPN bindings on ASBRs).

MD VPN inter-AS option C

As shown in Figure 11:

· A VPN network involves AS 1 and AS 2.

· PE 3 and PE 4 are the ASBRs for AS 1 and AS 2, respectively.

· PE 3 and PE 4 are interconnected through MP-EBGP and treat each other as a P device.

· PEs in different ASs establish a multihop MP-EBGP session to advertise VPN-IPv4 routes to each other.

Figure 11 MD VPN inter-AS option C

To implement MD VPN inter-AS option C, only one MD needs to be created for the two ASs. Multicast data is transmitted between the two ASs through the MD.

A multicast packet of the VPN instance is delivered as follows:

1. CE 1 forwards the VPN multicast packet to PE 1.

2. PE 1 encapsulates the VPN multicast packet into a public network multicast packet and forwards it to PE 3 through the MTI interface on the public network.

3. PE 3 and PE 4 are interconnected through MP-EBGP, so PE 3 forwards the public network multicast packet to PE 4 along the VPN IPv4 route.

4. The public network multicast packet arrives at the MTI interface of PE 2 in AS 2. PE 2 decapsulates the public network multicast packet and forwards the VPN multicast packet to CE 2.

Multicast VPN configuration task list

Task at a glance
Configuring MD VPN: · (Required.) Enabling IP multicast routing in a VPN instance · (Required.) Creating an MD for a VPN instance · (Required.) Specifying the default-group · (Required.) Specifying the MD source interface · (Optional.) Configuring MDT switchover parameters · (Optional.) Enabling data-group reuse logging
Configuring BGP MDT: · (Required.) Enabling BGP MDT peers or peer groups · (Optional.) Configuring a BGP MDT route reflector

Task at a glance

Configuring MD VPN:

· (Required.) Enabling IP multicast routing in a VPN instance

· (Required.) Creating an MD for a VPN instance

· (Required.) Specifying the default-group

· (Required.) Specifying the MD source interface

· (Optional.) Configuring MDT switchover parameters

· (Optional.) Enabling data-group reuse logging

Configuring BGP MDT:

· (Required.) Enabling BGP MDT peers or peer groups

· (Optional.) Configuring a BGP MDT route reflector

The MTI interfaces are automatically created and bound with the VPN instance when you create an MD for the VPN instance. Follow these guidelines to make sure the MTI interfaces are correctly created.

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

· To ensure the correct MTI forwarding, you must configure the service type of the service loopback group as multicast tunnel by using the service-loopback group command. For more information about this command, see Layer 2—LAN Switching Command Reference.

· The PIM mode on the MTI must be the same as the PIM mode running on the VPN instance to which the MTI belongs. When at least one interface on the VPN instance is enabled with PIM, the MTI is enabled with PIM accordingly. When all interfaces on the VPN instance are PIM-disabled, PIM is also disabled on the MTI.

Configuring MD VPN

This section describes how to configure MD VPN.

Configuration prerequisites

Before you configure MD VPN, complete the following tasks:

· Configure a unicast routing protocol on the public network.

· Configure MPLS L3VPN on the public network.

· Configure PIM-DM, PIM-SM, or PIM-SSM on the public network.

· Determine the VPN instance names and RDs.

· Determine the default-groups.

· Determine the source address for establishing BGP peers.

· Determine the data-group range and the default-MDT to data-MDT switchover criterion.

· Determine the data-delay period.

Enabling IP multicast routing in a VPN instance

Before you configure any MD VPN functionality for a VPN, you must create a VPN instance and enable IP multicast routing in this VPN instance.

Perform this task on PE devices.

To enable IP multicast routing in a VPN instance:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a VPN instance and enter VPN instance view.	ip vpn-instance vpn-instance-name	By default, VPN instances do not exist on the device. For more information about this command, see MPLS Command Reference.
3. Configure an RD for the VPN instance.	route-distinguisher route-distinguisher	By default, a VPN instance is not configured with an RD. For more information about this command, see MPLS Command Reference.
4. Return to system view.	quit	N/A
5. Enable IP multicast routing for the VPN instance and enter MRIB view of this VPN instance.	multicast routing vpn-instance vpn-instance-name	Disabled by default.

Creating an MD for a VPN instance

You can create one or multiple MDs to provide services for their associated VPN instances on the PE device. When you create an MD for a VPN instance, the system automatically create MTI interfaces and bind them with the VPN instance.

Perform this task on PE devices.

To create an MD for a VPN instance:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an MD for the VPN instance and enter MD view.	multicast-domain vpn-instance vpn-instance-name	By default, a VPN instance is not configured with an MD.

Specifying the default-group

The MTI uses the default-group as the destination address to encapsulate VPN multicast packets.

Configuration restrictions and guidelines

When you specify the default group, follow these restrictions and guidelines:

· Perform this task on PE devices.

· You must specify the same default-group on all PE devices that belong to the same VPN instance.

· The default-group for a VPN instance must be different from the default-group and the data-group used by any other VPN instance.

Configuration procedure

To specify the default-group:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MD view.	multicast-domain vpn-instance vpn-instance-name	N/A
3. Specify the default-group.	default-group group-address	By default, an MD is not configured with a default-group.

Specifying the MD source interface

The MTI uses the IP address of the MD source interface as the source address to encapsulate the VPN multicast packets. 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.

Perform this task on PE devices.

To specify the MD source interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MD view.	multicast-domain vpn-instance vpn-instance-name	N/A
3. Specify the MD source interface.	source interface-type interface-number	By default, an MD source interface does not exist.

Configuring MDT switchover parameters

To decrease traffic interruption caused by frequent default-MDT to data-MDT switchovers, you can specify a data-delay period. The switchover occurs a data-delay period after the VPN multicast data first arrives, regardless of whether VPN multicast data keeps arriving during the period.

Perform this task on PE devices.

To configure MDT switchover parameters:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MD view.	multicast-domain vpn-instance vpn-instance-name	N/A
3. Configure the data-group range and the default-MDT to data-MDT switchover criterion.	data-group group-address { mask-length \| mask } \| acl acl-number ]	By default, the data-group range is not configured. The default-MDT to data-MDT switchover never takes place.
4. Set the data-delay period.	data-delay delay	The default setting is 3 seconds.

Enabling data-group reuse logging

For a given VPN, the number of VPN multicast streams to be switched to data-MDTs might exceed the number of addresses in the data-group address range. In this case, the VPN instance on the source-side PE device can reuse the addresses in the address range. With data-group reuse logging enabled, the address reuse information will be logged.

Attributed to the MD module, the group address reuse logging information has a severity level informational. For more information about the logging information, see Network Management and Monitoring Configuration Guide.

Perform this task on PE devices.

To enable data-group reuse logging:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MD view.	multicast-domain vpn-instance vpn-instance-name	N/A
3. Enable data-group reuse logging.	log data-group-reuse	By default, data-group reuse logging is disabled.

Configuring BGP MDT

If PIM-SSM is running on the public network, you must configure BGP MDT.

Configuration prerequisites

Before you configure BGP MDT, complete the following tasks:

· Configure MPLS L3VPN on the public network.

· Configure basic BGP functions on the public network.

· Configure the PIM-SSM on the public network.

· Determine the IP addresses of the MDT peers.

· Determine the cluster IDs of the route reflectors.

Enabling BGP MDT peers or peer groups

Configure a BGP MDT peer or peer group on a PE router in BGP IPv4 MDT address family view. Then, the PE router can exchange MDT information with the BGP peer or peer group. MDT information includes the IP address of the PE and the default-group to which the PE belongs. On a public network running PIM-SSM, the multicast VPN establishes a default-MDT rooted at the PE (multicast source) based on the MDT information.

Perform this task on PE devices.

To configure BGP MDT peers or peer groups:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Create a BGP IPv4 MDT address family and enter its view.	address-family ipv4 mdt	By default, BGP IPv4 address families do not exist.
4. Enable the MDT routing information exchanging capability between local routers and their BGP peers or peer groups.	peer { group-name \| ip-address [ mask-length ] } enable	By default, local routers cannot exchange BGP MDT routing information with their peers or peer groups. IMPORTANT: Before you configure this command, you must create BGP peers or peer groups in BGP view. For more information, see Layer 3—IP Routing Configuration Guide.

Configuring a BGP MDT route reflector

BGP MDT peers in the same AS must be fully meshed to maintain connectivity. However, when many BGP MDT peers exist in an AS, connection establishment among them might result in increased costs. To reduce connections between them, you can configure one of them as a route reflector and specify other routers as clients.

When clients establish BGP MDT connections with the route reflector, the route reflector forwards (or reflects) BGP MDT routing information between clients. The clients are not required to be fully meshed. To save bandwidth if the clients have been fully meshed, you can disable the routing reflection between clients by using the undo reflect between-clients command. The route reflector and its clients form a cluster. In general, a cluster has only one route reflector whose router ID identifies the cluster. However, you can configure several route reflectors in a cluster to improve network reliability. You must configure the same cluster ID for them to avoid routing loops.

Perform this task on PE devices. For more information about the commands in this task, see Layer 3—IP Routing Command Reference.

To configure a BGP MDT route reflector:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter BGP IPv4 MDT address family view.	address-family ipv4 mdt	N/A
4. Configure the device as a route reflector and specify its peers or peer groups as clients.	peer { group-name \| ip-address [ mask-length ] } reflect-client	By default, neither route reflectors nor clients exist.
5. (Optional.) Disable route reflection between clients.	undo reflect between-clients	By default, route reflection between clients is disabled.
6. (Optional.) Configure the cluster ID of the route reflector.	reflector cluster-id { cluster-id \| ip-address }	By default, a route reflector uses its router ID as the cluster ID.

Displaying and maintaining multicast VPN

Execute display commands in any view and reset commands in user view.

Task	Command
Display BGP MDT peer group information.	display bgp group ipv4 mdt [ group-name group-name ]
Display information about BGP MDT peers or peer groups.	display bgp peer ipv4 mdt [ ip-address mask-length \| { ip-address \| group-name group-name } log-info \| [ ip-address ] verbose ]
Display BGP MDT routing information.	display bgp routing-table ipv4 mdt [ route-distinguisher route-distinguisher ] [ ip-address [ advertise-info ] ]
Display information about BGP update groups for the BGP IPv4 MDT address family.	display bgp update-group ipv4 mdt [ ip-address ]
Display data-group information received by a VPN instance in the MD.	display multicast-domain vpn-instance vpn-instance-name data-group receive [ brief \| [ active \| group group-address \| sender source-address \| vpn-source-address [ mask { mask-length \| mask } ] \| vpn-group-address [ mask { mask-length \| mask } ] ] * ]
Display data-group information sent by a VPN instance in the MD.	display multicast-domain vpn-instance vpn-instance-name data-group send [ group group-address \| reuse interval \| vpn-source-address [ mask { mask-length \| mask } ] \| vpn-group-address [ mask { mask-length \| mask } ] ] *
Display default-group information.	display multicast-domain [ vpn-instance vpn-instance-name ] default-group
Reset the BGP sessions for the BGP IPv4 MDT address family.	reset bgp { as-number \| ip-address [ mask-length ] \| all \| external \| group group-name \| internal } ipv4 mdt

For more information about the display bgp group, display bgp peer, display bgp update-group, and reset bgp commands, see Layer 3—IP Routing Command Reference.

Multicast VPN configuration examples

This section provides examples of configuring multicast VPN on switches.

Intra-AS MD VPN configuration example

Network requirements

Item	Network requirements
Multicast sources and receivers	· In VPN instance a, S 1 is a multicast source, and R 1, R 2 and R 3 are receivers. · In VPN instance b, S 2 is a multicast source, and R 4 is a receiver. · For VPN instance a, the default-group is 239.1.1.1, and the data-group range is 225.2.2.0 to 225.2.2.15. · For VPN instance b, the default-group is 239.2.2, and the data-group range is 225.4.4.0 to 225.4.4.15.
VPN instances to which PE interfaces belong	· PE 1: VLAN-interface 11 and VLAN-interface 20 belong to VPN instance a. VLAN-interface 12 and Loopback 1 belong to the public network instance. · PE 2: VLAN-interface 13 belongs to VPN instance b. VLAN-interface 14 belongs to VPN instance a. VLAN-interface 15 and Loopback 1 belong to the public network instance. · PE 3: VLAN-interface 17 belongs to VPN instance a. VLAN-interface 18 and Loopback 2 belong to VPN instance b. VLAN-interface 19 and Loopback 1 belong to the public network instance.
Unicast routing protocols and MPLS	· Configure OSPF on the public network, and configure RIP between the PEs and CEs. · Establish BGP peer connections between PE 1, PE 2, and PE 3 on their respective Loopback 1. · Configure MPLS on the public network.
IP multicast routing	· Enable IP multicast routing on the P device. · Enable IP multicast routing on the public network on PE 1, PE 2, and PE 3. · Enable IP multicast routing for VPN instance a on PE 1, PE 2, and PE 3. · Enable IP multicast routing for VPN instance b on PE 2 and PE 3. · Enable IP multicast routing on CE a1, CE a2, CE a3, CE b1, and CE b2.
IGMP	· Enable IGMPv2 on VLAN-interface 20 of PE 1. · Enable IGMPv2 on VLAN-interface 40 of CE a2, VLAN-interface 50 of CE a3, and VLAN-interface 60 of CE b2.
PIM	Enable PIM-SM on the public network and for VPN instances a and b: · Enable PIM-SM on all interfaces of the P device. · Enable PIM-SM on all public and private network interfaces of PE 1, PE 2, and PE 3. · Enable PIM-SM on all interfaces that have no receiver hosts connected of CE a1, CE a2, CE a3, CE b1, and CE b2. · Configure Loopback 1 of P as a C-BSR and a C-RP for the public network to provide services for all multicast groups. · Configure Loopback 1 of CE a2 as a C-BSR and a C-RP for VPN instance a to provide services for all multicast groups. · Configure Loopback 2 of PE 3 as a C-BSR and a C-RP for VPN instance b to provide services for all multicast groups.

Figure 12 Network diagram

Table 2 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
S 1	—	10.110.7.2/24	PE 3	Vlan-int19	192.168.8.1/24
S 2	—	10.110.8.2/24	PE 3	Vlan-int17	10.110.5.1/24
R 1	—	10.110.1.2/24	PE 3	Vlan-int18	10.110.6.1/24
R 2	—	10.110.9.2/24	PE 3	Loop1	1.1.1.3/32
R 3	—	10.110.10.2/24	PE 3	Loop2	33.33.33.33/32
R 4	—	10.110.11.2/24	CE a1	Vlan-int10	10.110.7.1/24
P	Vlan-int12	192.168.6.2/24	CE a1	Vlan-int11	10.110.2.2/24
P	Vlan-int15	192.168.7.2/24	CE a2	Vlan-int40	10.110.9.1/24
P	Vlan-int19	192.168.8.2/24	CE a2	Vlan-int14	10.110.4.2/24
P	Loop1	2.2.2.2/32	CE a2	Vlan-int16	10.110.12.1/24
PE 1	Vlan-int12	192.168.6.1/24	CE a2	Loop1	22.22.22.22/32
PE 1	Vlan-int20	10.110.1.1/24	CE a3	Vlan-int50	10.110.10.1/24
PE 1	Vlan-int11	10.110.2.1/24	CE a3	Vlan-int17	10.110.5.2/24
PE 1	Loop1	1.1.1.1/32	CE a3	Vlan-int16	10.110.12.2/24
PE 2	Vlan-int15	192.168.7.1/24	CE b1	Vlan-int30	10.110.8.1/24
PE 2	Vlan-int13	10.110.3.1/24	CE b1	Vlan-int13	10.110.3.2/24
PE 2	Vlan-int14	10.110.4.1/24	CE b2	Vlan-int60	10.110.11.1/24
PE 2	Loop1	1.1.1.2/32	CE b2	Vlan-int18	10.110.6.2/24

Configuration procedure

1. Configure PE 1:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE1> system-view

[PE1] router id 1.1.1.1

[PE1] multicast routing

[PE1-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE1] mpls lsr-id 1.1.1.1

[PE1] mpls ldp

[PE1-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE1] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE1] interface gigabitethernet 1/0/5

[PE1-GigabitEthernet1/0/5] port link-mode bridge

[PE1-GigabitEthernet1/0/5] port service-loopback group 1

[PE1-GigabitEthernet1/0/5] quit

# Create a VPN instance named a and configure an RD and route target attributes for the instance.

[PE1] ip vpn-instance a

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

[PE1-vpn-instance-a] vpn-target 100:1 export-extcommunity

[PE1-vpn-instance-a] vpn-target 100:1 import-extcommunity

[PE1-vpn-instance-a] quit

# Enable IP multicast routing for VPN instance a.

[PE1] multicast routing vpn-instance a

[PE1-mrib-a] quit

# Create an MD for VPN instance a, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE1] multicast-domain vpn-instance a

[PE1-md-a] default-group 239.1.1.1

[PE1-md-a] source loopback 1

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

[PE1-md-a] quit

# Assign an IP address to VLAN-interface 12, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE1] interface vlan-interface 12

[PE1-Vlan-interface12] ip address 192.168.6.1 24

[PE1-Vlan-interface12] pim sm

[PE1-Vlan-interface12] mpls enable

[PE1-Vlan-interface12] mpls ldp enable

[PE1-Vlan-interface12] quit

# Bind VLAN-interface 20 with VPN instance a, assign an IP address to VLAN-interface 20, and enable IGMP on the interface.

[PE1] interface vlan-interface 20

[PE1-Vlan-interface20] ip binding vpn-instance a

[PE1-Vlan-interface20] ip address 10.110.1.1 24

[PE1-Vlan-interface20] igmp enable

[PE1-Vlan-interface20] quit

# Bind VLAN-interface 11 with VPN instance a, assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.

[PE1] interface vlan-interface 11

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

[PE1-Vlan-interface11] ip address 10.110.2.1 24

[PE1-Vlan-interface11] pim sm

[PE1-Vlan-interface11] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[PE1] interface loopback 1

[PE1-LoopBack1] ip address 1.1.1.1 32

[PE1-LoopBack1] pim sm

[PE1-LoopBack1] quit

# Configure BGP.

[PE1] bgp 100

[PE1-bgp] group vpn-g internal

[PE1-bgp] peer vpn-g connect-interface loopback 1

[PE1-bgp] peer 1.1.1.2 group vpn-g

[PE1-bgp] peer 1.1.1.3 group vpn-g

[PE1–bgp] ip vpn-instance a

[PE1-bgp-a] address-family ipv4

[PE1-bgp-ipv4-a] import-route rip 2

[PE1-bgp-ipv4-a] import-route direct

[PE1-bgp-ipv4-a] quit

[PE1-bgp-a] quit

[PE1–bgp] address-family vpnv4

[PE1–bgp-vpnv4] peer vpn-g enable

[PE1–bgp-vpnv4] quit

[PE1–bgp] quit

# Configure OSPF.

[PE1] ospf 1

[PE1-ospf-1] area 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Configure RIP.

[PE1] rip 2 vpn-instance a

[PE1-rip-2] network 10.110.1.0 0.0.0.255

[PE1-rip-2] network 10.110.2.0 0.0.0.255

[PE1-rip-2] import-route bgp

[PE1-rip-2] return

2. Configure PE 2:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE2> system-view

[PE2] router id 1.1.1.2

[PE2] multicast routing

[PE2-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE2] mpls lsr-id 1.1.1.2

[PE2] mpls ldp

[PE2-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE2] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE2] interface gigabitethernet 1/0/5

[PE2-GigabitEthernet1/0/5] port link-mode bridge

[PE2-GigabitEthernet1/0/5] port service-loopback group 1

[PE2-GigabitEthernet1/0/5] quit

# Create a VPN instance named b and configure an RD and route target attributes for the instance.

[PE2] ip vpn-instance b

[PE2-vpn-instance-b] route-distinguisher 200:1

[PE2-vpn-instance-b] vpn-target 200:1 export-extcommunity

[PE2-vpn-instance-b] vpn-target 200:1 import-extcommunity

[PE2-vpn-instance-b] quit

# Enable IP multicast routing for VPN instance b.

[PE2] multicast routing vpn-instance b

[PE2-mrib-b] quit

# Create an MD for VPN instance b, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE2] multicast-domain vpn-instance b

[PE2-md-b] default-group 239.2.2.2

[PE2-md-b] source loopback 1

[PE2-md-b] data-group 225.4.4.0 28

[PE2-md-b] quit

# Create a VPN instance named a and configure an RD and route target attributes for the instance.

[PE2] ip vpn-instance a

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

[PE2-vpn-instance-a] vpn-target 100:1 export-extcommunity

[PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity

[PE2-vpn-instance-a] quit

# Enable IP multicast routing for VPN instance a.

[PE2] multicast routing vpn-instance a

[PE2-mrib-a] quit

# Create an MD for VPN instance a, and specify the default-group, the MD source interface, and the data-group address range for the MD.

[PE2] multicast-domain vpn-instance a

[PE2-md-a] default-group 239.1.1.1

[PE2-md-a] source loopback 1

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

[PE2-md-a] quit

# Assign an IP address to VLAN-interface 15, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE2] interface vlan-interface 15

[PE2-Vlan-interface15] ip address 192.168.7.1 24

[PE2-Vlan-interface15] pim sm

[PE2-Vlan-interface15] mpls enable

[PE2-Vlan-interface15] mpls ldp enable

[PE2-Vlan-interface15] quit

# Bind VLAN-interface 13 with VPN instance b, assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface.

[PE2] interface vlan-interface 13

[PE2-Vlan-interface13] ip binding vpn-instance b

[PE2-Vlan-interface13] ip address 10.110.3.1 24

[PE2-Vlan-interface13] pim sm

[PE2-Vlan-interface13] quit

# Bind VLAN-interface 14 with VPN instance a, assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface.

[PE2] interface vlan-interface 14

[PE2-Vlan-interface14] ip binding vpn-instance a

[PE2-Vlan-interface14] ip address 10.110.4.1 24

[PE2-Vlan-interface14] pim sm

[PE2-Vlan-interface14] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[PE2] interface loopback 1

[PE2-LoopBack1] ip address 1.1.1.2 32

[PE2-LoopBack1] pim sm

[PE2-LoopBack1] quit

# Configure BGP.

[PE2] bgp 100

[PE2-bgp] group vpn-g internal

[PE2-bgp] peer vpn-g connect-interface loopback 1

[PE2-bgp] peer 1.1.1.1 group vpn-g

[PE2-bgp] peer 1.1.1.3 group vpn-g

[PE2–bgp] ip vpn-instance a

[PE2-bgp-a] address-family ipv4

[PE2-bgp-ipv4-a] import-route rip 2

[PE2-bgp-ipv4-a] import-route direct

[PE2-bgp-ipv4-a] quit

[PE2-bgp-a] quit

[PE2–bgp] ip vpn-instance b

[PE2-bgp-b] address-family ipv4

[PE2-bgp-ipv4-b] import-route rip 3

[PE2-bgp-ipv4-b] import-route direct

[PE2-bgp-ipv4-b] quit

[PE2-bgp-b] quit

[PE2–bgp] address-family vpnv4

[PE2–bgp-vpnv4] peer vpn-g enable

[PE2–bgp-vpnv4] quit

[PE2–bgp] quit

# Configure OSPF.

[PE2] ospf 1

[PE2-ospf-1] area 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Configure RIP.

[PE2] rip 2 vpn-instance a

[PE2-rip-2] network 10.110.3.0 0.0.0.255

[PE2-rip-2] import-route bgp

[PE2-rip-2] quit

[PE2] rip 3 vpn-instance b

[PE2-rip-3] network 10.110.4.0 0.0.0.255

[PE2-rip-3] import-route bgp

[PE2-rip-3] return

3. Configure PE 3:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE3> system-view

[PE3] router id 1.1.1.3

[PE3] multicast routing

[PE3-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE3] mpls lsr-id 1.1.1.3

[PE3] mpls ldp

[PE3-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE3] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE3] interface gigabitethernet 1/0/5

[PE3-GigabitEthernet1/0/5] port link-mode bridge

[PE3-GigabitEthernet1/0/5] port service-loopback group 1

[PE3-GigabitEthernet1/0/5] quit

# Create a VPN instance named a and configure an RD and route target attributes for the instance.

[PE3] ip vpn-instance a

[PE3-vpn-instance-a] route-distinguisher 100:1

[PE3-vpn-instance-a] vpn-target 100:1 export-extcommunity

[PE3-vpn-instance-a] vpn-target 100:1 import-extcommunity

[PE3-vpn-instance-a] quit

# Enable IP multicast routing for VPN instance a.

[PE3] multicast routing vpn-instance a

[PE3-mrib-a] quit

# Create an MD for VPN instance a, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE3] multicast-domain vpn-instance a

[PE3-md-a] default-group 239.1.1.1

[PE3-md-a] source loopback 1

[PE3-md-a] data-group 225.2.2.0 28

[PE3-md-a] quit

# Create a VPN instance named b and configure an RD and route target attributes for the instance.

[PE3] ip vpn-instance b

[PE3-vpn-instance-b] route-distinguisher 200:1

[PE3-vpn-instance-b] vpn-target 200:1 export-extcommunity

[PE3-vpn-instance-b] vpn-target 200:1 import-extcommunity

[PE3-vpn-instance-b] quit

# Enable IP multicast routing for VPN instance b.

[PE3] multicast routing vpn-instance b

[PE3-mrib-b] quit

# Create an MD for VPN instance b, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE3] multicast-domain vpn-instance b

[PE3-md-b] default-group 239.2.2.2

[PE3-md-b] source loopback 1

[PE3-md-b] data-group 225.4.4.0 28

[PE3-md-b] quit

# Assign an IP address to VLAN-interface 19, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE3] interface vlan-interface 19

[PE3-Vlan-interface19] ip address 192.168.8.1 24

[PE3-Vlan-interface19] pim sm

[PE3-Vlan-interface19] mpls enable

[PE3-Vlan-interface19] mpls ldp enable

[PE3-Vlan-interface19] quit

# Bind VLAN-interface 17 with VPN instance a, assign an IP address to VLAN-interface 17, and enable PIM-SM on the interface.

[PE3] interface vlan-interface 17

[PE3-Vlan-interface17] ip binding vpn-instance a

[PE3-Vlan-interface17] ip address 10.110.5.1 24

[PE3-Vlan-interface17] pim sm

[PE3-Vlan-interface17] quit

# Bind VLAN-interface 18 with VPN instance b, assign an IP address to VLAN-interface 18, and enable PIM-SM on the interface.

[PE3] interface vlan-interface 18

[PE3-Vlan-interface18] ip binding vpn-instance b

[PE3-Vlan-interface18] ip address 10.110.6.1 24

[PE3-Vlan-interface18] pim sm

[PE3-Vlan-interface18] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[PE3] interface loopback 1

[PE3-LoopBack1] ip address 1.1.1.3 32

[PE3-LoopBack1] pim sm

[PE3-LoopBack1] quit

# Bind Loopback 2 with VPN instance b, assign an IP address to Loopback 2, and enable PIM-SM on the interface.

[PE3] interface loopback 2

[PE3-LoopBack2] ip binding vpn-instance b

[PE3-LoopBack2] ip address 33.33.33.33 32

[PE3-LoopBack2] pim sm

[PE3-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP for VPN instance b.

[PE3] pim vpn-instance b

[PE3-pim-b] c-bsr 33.33.33.33

[PE3-pim-b] c-rp 33.33.33.33

[PE3-pim-b] quit

# Configure BGP.

[PE3] bgp 100

[PE3-bgp] group vpn-g internal

[PE3-bgp] peer vpn-g connect-interface loopback 1

[PE3-bgp] peer 1.1.1.1 group vpn-g

[PE3-bgp] peer 1.1.1.2 group vpn-g

[PE3–bgp] ip vpn-instance a

[PE3-bgp-a] address-family ipv4

[PE3-bgp-ipv4-a] import-route rip 2

[PE3-bgp-ipv4-a] import-route direct

[PE3-bgp-ipv4-a] quit

[PE3-bgp-a] quit

[PE3–bgp] ip vpn-instance b

[PE3-bgp-b] address-family ipv4

[PE3-bgp-ipv4-b] import-route rip 3

[PE3-bgp-ipv4-b] import-route direct

[PE3-bgp-ipv4-b] quit

[PE3-bgp-b] quit

[PE3–bgp] address-family vpnv4

[PE3–bgp-vpnv4] peer vpn-g enable

[PE3–bgp-vpnv4] quit

[PE3–bgp] quit

# Configure OSPF.

[PE3] ospf 1

[PE3-ospf-1] area 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255

[PE3-ospf-1-area-0.0.0.0] quit

[PE3-ospf-1] quit

# Configure RIP.

[PE3] rip 2 vpn-instance a

[PE3-rip-2] network 10.110.5.0 0.0.0.255

[PE3-rip-2] import-route bgp

[PE3-rip-2] quit

[PE3] rip 3 vpn-instance b

[PE3-rip-3] network 10.110.6.0 0.0.0.255

[PE3-rip-3] network 33.33.33.33 0.0.0.0

[PE3-rip-3] import-route bgp

[PE3-rip-3] return

4. Configuring the P switch:

# Enable IP multicast routing on the public network.

<P> system-view

[P] multicast routing

[P-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[P] mpls lsr-id 2.2.2.2

[P] mpls ldp

[P-ldp] quit

# Assign an IP address to VLAN-interface 12, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[P] interface vlan-interface 12

[P-Vlan-interface12] ip address 192.168.6.2 24

[P-Vlan-interface12] pim sm

[P-Vlan-interface12] mpls enable

[P-Vlan-interface12] mpls ldp enable

[P-Vlan-interface12] quit

# Assign an IP address to VLAN-interface 15, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[P] interface vlan-interface 15

[P-Vlan-interface15] ip address 192.168.7.2 24

[P-Vlan-interface15] pim sm

[P-Vlan-interface15] mpls enable

[P-Vlan-interface15] mpls ldp enable

[P-Vlan-interface15] quit

# Assign an IP address to VLAN-interface 19, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[P] interface vlan-interface 19

[P-Vlan-interface19] ip address 192.168.8.2 24

[P-Vlan-interface19] pim sm

[P-Vlan-interface19] mpls enable

[P-Vlan-interface19] mpls ldp enable

[P-Vlan-interface19] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[P] interface loopback 1

[P-LoopBack1] ip address 2.2.2.2 32

[P-LoopBack1] pim sm

[P-LoopBack1] quit

# Configure Loopback 1 as a C-BSR and a C-RP on the public network.

[P] pim

[P-pim] c-bsr 2.2.2.2

[P-pim] c-rp 2.2.2.2

[P-pim] quit

# Configure OSPF.

[P] ospf 1

[P-ospf-1] area 0.0.0.0

[P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[P-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255

5. Configure CE a1:

# Enable IP multicast routing.

<CEa1> system-view

[CEa1] multicast routing

[CEa1-mrib] quit

# Assign an IP address to VLAN-interface 10, and enable PIM-SM on the interface.

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] ip address 10.110.7.1 24

[CEa1-Vlan-interface10] pim sm

[CEa1-Vlan-interface10] quit

# Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] ip address 10.110.2.2 24

[CEa1-Vlan-interface11] pim sm

[CEa1-Vlan-interface11] quit

# Configure RIP.

[CEa1] rip 2

[CEa1-rip-2] network 10.110.2.0 0.0.0.255

[CEa1-rip-2] network 10.110.7.0 0.0.0.255

6. Configure CE b1:

# Enable IP multicast routing.

<CEb1> system-view

[CEb1] multicast routing

[CEb1-mrib] quit

# Assign an IP address to VLAN-interface 30, and enable PIM-SM on the interface.

[CEb1] interface vlan-interface 30

[CEb1-Vlan-interface30] ip address 10.110.8.1 24

[CEb1-Vlan-interface30] pim sm

[CEb1-Vlan-interface30] quit

# Assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface.

[CEb1] interface vlan-interface 13

[CEb1-Vlan-interface13] ip address 10.110.3.2 24

[CEb1-Vlan-interface13] pim sm

[CEb1-Vlan-interface13] quit

# Configure RIP.

[CEb1] rip 3

[CEb1-rip-3] network 10.110.3.0 0.0.0.255

[CEb1-rip-3] network 10.110.8.0 0.0.0.255

7. Configure CE a2:

# Configure CE a2:

<CEa2> system-view

[CEa2] multicast routing

[CEa2-mrib] quit

# Assign an IP address to VLAN-interface 40, and enable IGMP on the interface.

[CEa2] interface vlan-interface 40

[CEa2-Vlan-interface40] ip address 10.110.9.1 24

[CEa2-Vlan-interface40] igmp enable

[CEa2-Vlan-interface40] quit

# Assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface.

[CEa2] interface vlan-interface 14

[CEa2-Vlan-interface14] ip address 10.110.4.2 24

[CEa2-Vlan-interface14] pim sm

[CEa2-Vlan-interface14] quit

# Assign an IP address to VLAN-interface 16, and enable PIM-SM on the interface.

[CEa2] interface vlan-interface 16

[CEa2-Vlan-interface16] ip address 10.110.12.1 24

[CEa2-Vlan-interface16] pim sm

[CEa2-Vlan-interface16] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[CEa2] interface loopback 1

[CEa2-LoopBack1] ip address 22.22.22.22 32

[CEa2-LoopBack1] pim sm

[CEa2-LoopBack1] quit

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

[CEa2] pim

[CEa2-pim] c-bsr 22.22.22.22

[CEa2-pim] c-rp 22.22.22.22

[CEa2-pim] quit

# Configure RIP.

[CEa2] rip 2

[CEa2-rip-2] network 10.110.4.0 0.0.0.255

[CEa2-rip-2] network 10.110.9.0 0.0.0.255

[CEa2-rip-2] network 10.110.12.0 0.0.0.255

[CEa2-rip-2] network 22.22.22.22 0.0.0.0

8. Configure CE a3:

# Enable IP multicast routing.

<CEa3> system-view

[CEa3] multicast routing

[CEa3-mrib] quit

# Assign an IP address to VLAN-interface 50, and enable IGMP on the interface.

[CEa3] interface vlan-interface 50

[CEa3-Vlan-interface50] ip address 10.110.10.1 24

[CEa3-Vlan-interface50] igmp enable

[CEa3-Vlan-interface50] quit

# Assign an IP address to VLAN-interface 17, and enable PIM-SM on the interface.

[CEa3] interface vlan-interface 17

[CEa3-Vlan-interface17] ip address 10.110.5.2 24

[CEa3-Vlan-interface17] pim sm

[CEa3-Vlan-interface17] quit

# Assign an IP address to VLAN-interface 16, and enable PIM-SM on the interface.

[CEa3] interface vlan-interface 16

[CEa3-Vlan-interface16] ip address 10.110.12.2 24

[CEa3-Vlan-interface16] pim sm

[CEa3-Vlan-interface16] quit

# Configure RIP.

[CEa3] rip 2

[CEa3-rip-2] network 10.110.5.0 0.0.0.255

[CEa3-rip-2] network 10.110.10.0 0.0.0.255

[CEa3-rip-2] network 10.110.12.0 0.0.0.255

9. Configure CE b2:

# Enable IP multicast routing.

<CEb2> system-view

[CEb2] multicast routing

[CEb2-mrib] quit

# Assign an IP address to VLAN-interface 60, and enable IGMP on the interface.

[CEb2] interface vlan-interface 60

[CEb2-Vlan-interface60] ip address 10.110.11.1 24

[CEb2-Vlan-interface60] igmp enable

[CEb2-Vlan-interface60] quit

# Assign an IP address to VLAN-interface 18, and enable PIM-SM on the interface.

[CEb2] interface vlan-interface 18

[CEb2-Vlan-interface18] ip address 10.110.6.2 24

[CEb2-Vlan-interface18] pim sm

[CEb2-Vlan-interface18] quit

# Configure RIP.

[CEb2] rip 3

[CEb2-rip-3] network 10.110.6.0 0.0.0.255

[CEb2-rip-3] network 10.110.11.0 0.0.0.255

Verifying the configuration

# Display information about local default-groups in VPN instances on PE 1.

[PE1] display multicast-domain default-group local

MD local default-group information:

Group address Source address Interface VPN instance

239.1.1.1 1.1.1.1 MTunnel0 a

# Display information about local default-groups in VPN instances on PE 2.

[PE2] display multicast-domain default-group local

MD local default-group information:

Group address Source address Interface VPN instance

239.1.1.1 1.1.1.2 MTunnel0 a

239.1.1.1 1.1.1.2 MTunnel1 b

# Display information about local default-groups in VPN instances on PE 3.

[PE3] display multicast-domain default-group local

MD local default-group information:

Group address Source address Interface VPN instance

239.1.1.1 1.1.1.3 MTunnel0 a

239.2.2.2 1.1.1.3 MTunnel1 b

MD VPN inter-AS option C configuration example

Network requirements

Item	Network requirements
Multicast sources and receivers	· In VPN instance a, S 1 is a multicast source, and R 2 is a receiver. · In VPN instance b, S 2 is a multicast source, and R 1 is a receiver. · For VPN instance a, the default-group is 239.1.1.1, and the data-group range is 225.1.1.0 to 225.1.1.15. · For VPN instance b, the default-group is 239.4.4.4, and the data-group range is 225.4.4.0 to 225.4.4.15.
VPN instances to which PE devices belong	· PE 1: VLAN-interface 11 belongs to VPN instance b. VLAN-interface 12 belongs to VPN instance a. VLAN-interface 2 and Loopback 1 belong to the public network instance. · PE 2: VLAN-interface 2, VLAN-interface 3, Loopback 1, and Loopback 2 belong to the public network instance. · PE 3: VLAN-interface 3, VLAN-interface 4, Loopback 1, and Loopback 2 belong to the public network instance. · PE 4: VLAN-interface 13 belongs to VPN instance a. VLAN-interface 14 belongs to VPN instance b. VLAN-interface 4 and Loopback 1 belong to the public network instance.
Unicast routing protocols and MPLS	· Configure OSPF separately in AS 100 and AS 200, and configure OSPF between the PEs and CEs. · Establish BGP peer connections between PE 1, PE 2, PE 3, and PE 4 on their respective Loopback 1 to exchange VPN routes. · Configure MPLS separately in AS 100 and AS 200.
IP multicast routing	· Enable IP multicast routing on the public network on PE 1, PE 2, PE 3, and PE 4. · Enable IP multicast routing for VPN instance a on PE 1 and PE 4. · Enable IP multicast routing for VPN instance b on PE 1 and PE 4. · Enable IP multicast routing on CE a1, CE a2, CE b1, and CE b2.
IGMP	· Enable IGMPv2 on VLAN-interface 30 of CE a2. · Enable IGMPv2 on VLAN-interface 40 of CE b2.
PIM	Enable PIM-SM on the public network and for VPN instances a and b: · Enable PIM-SM on all public network interfaces of PE 2 and PE 3. · Enable PIM-SM on all public and private network interfaces of PE 1 and PE 4. · Enable PIM-SM on all interfaces that do not have attached receiver hosts of CE a1, CE a2, CE b1, and CE b2. · Configure Loopback 2 of PE 2 and PE 3 as a C-BSR and a C-RP for their own AS to provide services for all multicast groups. · Configure Loopback 0 of CE a1 as a C-BSR and a C-RP for VPN instance a to provide services for all multicast groups. · Configure Loopback 0 of CE b1 as a C-BSR and a C-RP for VPN instance b to provide services for all multicast groups.
MSDP	Establish an MSDP peering relationship between PE 2 and PE 3 on their Loopback 1.

Figure 13 Network diagram

Table 3 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
S 1	—	10.11.5.2/24	R 1	—	10.11.8.2/24
S 2	—	10.11.6.2/24	R 2	—	10.11.7.2/24
PE 1	Vlan-int2	10.10.1.1/24	PE 3	Vlan-int4	10.10.2.1/24
PE 1	Vlan-int11	10.11.1.1/24	PE 3	Vlan-int3	192.168.1.2/24
PE 1	Vlan-int12	10.11.2.1/24	PE 3	Loop1	1.1.1.3/32
PE 1	Loop1	1.1.1.1/32	PE 3	Loop2	22.22.22.22/32
PE 2	Vlan-int2	10.10.1.2/24	PE 4	Vlan-int4	10.10.2.2/24
PE 2	Vlan-int3	192.168.1.1/24	PE 4	Vlan-int13	10.11.3.1/24
PE 2	Loop1	1.1.1.2/32	PE 4	Vlan-int14	10.11.4.1/32
PE 2	Loop2	11.11.11.11/32	PE 4	Loop1	1.1.1.4/32
CE a1	Vlan-int10	10.11.5.1/24	CE b1	Vlan-int20	10.11.6.1/24
CE a1	Vlan-int11	10.11.1.2/24	CE b1	Vlan-int12	10.11.2.2/24
CE a1	Loop0	2.2.2.2/32	CE b2	Vlan-int40	10.11.8.1/24
CE a2	Vlan-int30	10.11.7.1/24	CE b2	Vlan-int14	10.11.4.2/24
CE a2	Vlan-int13	10.11.3.2/24	CE b2	Loop0	3.3.3.3/32

Configuration procedure

1. Configure PE 1:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE1> system-view

[PE1] router id 1.1.1.1

[PE1] multicast routing

[PE1-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE1] mpls lsr-id 1.1.1.1

[PE1] mpls ldp

[PE1-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE1] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE1] interface gigabitethernet 1/0/5

[PE1-GigabitEthernet1/0/5] port link-mode bridge

[PE1-GigabitEthernet1/0/5] port service-loopback group 1

[PE1-GigabitEthernet1/0/5] quit

# Create a VPN instance named a and configure an RD and route target attributes for the instance.

[PE1] ip vpn-instance a

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

[PE1-vpn-instance-a] vpn-target 100:1 export-extcommunity

[PE1-vpn-instance-a] vpn-target 100:1 import-extcommunity

[PE1-vpn-instance-a] quit

# Enable IP multicast routing for VPN instance a.

[PE1] multicast routing vpn-instance a

[PE1-mrib-a] quit

# Create an MD for VPN instance a, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE1] multicast-domain vpn-instance a

[PE1-md-a] default-group 239.1.1.1

[PE1-md-a] source loopback 1

[PE1-md-a] data-group 225.1.1.0 28

[PE1-md-a] quit

# Create a VPN instance named b and configure an RD and route target attributes for the instance.

[PE1] ip vpn-instance b

[PE1-vpn-instance-b] route-distinguisher 200:1

[PE1-vpn-instance-b] vpn-target 200:1 export-extcommunity

[PE1-vpn-instance-b] vpn-target 200:1 import-extcommunity

[PE1-vpn-instance-b] quit

# Enable IP multicast routing for VPN instance b.

[PE1] multicast routing vpn-instance b

[PE1-mrib-b] quit

# Create an MD for VPN instance b, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE1] multicast-domain vpn-instance b

[PE1-md-b] default-group 239.4.4.4

[PE1-md-b] source loopback 1

[PE1-md-b] data-group 225.4.4.0 28

[PE1-md-b] quit

# Assign an IP address to VLAN-interface 2, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] ip address 10.10.1.1 24

[PE1-Vlan-interface2] pim sm

[PE1-Vlan-interface2] mpls enable

[PE1-Vlan-interface2] mpls ldp enable

[PE1-Vlan-interface2] quit

# Bind VLAN-interface 11 with VPN instance a, assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.

[PE1] interface vlan-interface 11

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

[PE1-Vlan-interface11] ip address 10.11.1.1 24

[PE1-Vlan-interface11] pim sm

[PE1-Vlan-interface11] quit

# Bind VLAN-interface 12 with VPN instance b, assign an IP address to VLAN-interface 12, and enable PIM-SM on the interface.

[PE1] interface vlan-interface 12

[PE1-Vlan-interface12] ip binding vpn-instance b

[PE1-Vlan-interface12] ip address 10.11.2.1 24

[PE1-Vlan-interface12] pim sm

[PE1-Vlan-interface12] quit

# Assign an IP address to Loopback 1, and enable PIM-SM.

[PE1] interface loopback 1

[PE1-LoopBack1] ip address 1.1.1.1 32

[PE1-LoopBack1] pim sm

[PE1-LoopBack1] quit

# Configure BGP.

[PE1] bgp 100

[PE1-bgp] group pe1-pe2 internal

[PE1-bgp] peer pe1-pe2 connect-interface loopback 1

[PE1-bgp] peer 1.1.1.2 group pe1-pe2

[PE1-bgp] group pe1-pe4 external

[PE1-bgp] peer pe1-pe4 as-number 200

[PE1-bgp] peer pe1-pe4 ebgp-max-hop 255

[PE1-bgp] peer pe1-pe4 connect-interface loopback 1

[PE1-bgp] peer 1.1.1.4 group pe1-pe4

[PE1–bgp] ip vpn-instance a

[PE1-bgp-a] address-family ipv4

[PE1-bgp-ipv4-a] import-route ospf 2

[PE1-bgp-ipv4-a] import-route direct

[PE1-bgp-ipv4-a] quit

[PE1-bgp-a] quit

[PE1–bgp] ip vpn-instance b

[PE1-bgp-b] address-family ipv4

[PE1-bgp-ipv4-b] import-route ospf 3

[PE1-bgp-ipv4-b] import-route direct

[PE1-bgp-ipv4-b] quit

[PE1-bgp-b] quit

[PE1–bgp] address-family ipv4

[PE1-bgp-ipv4] peer pe1-pe2 enable

[PE1-bgp-ipv4] peer pe1-pe2 label-route-capability

[PE1-bgp-ipv4] quit

[PE1–bgp] address-family vpnv4

[PE1–bgp-vpnv4] peer pe1-pe4 enable

[PE1–bgp-vpnv4] quit

[PE1–bgp] quit

# Configure OSPF.

[PE1] ospf 1

[PE1-ospf-1] area 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

[PE1] ospf 2 vpn-instance a

[PE1-ospf-2] import-route bgp

[PE1-ospf-2] area 0.0.0.0

[PE1-ospf-2-area-0.0.0.0] network 10.11.1.0 0.0.0.255

[PE1-ospf-2-area-0.0.0.0] quit

[PE1-ospf-2] quit

[PE1] ospf 3 vpn-instance b

[PE1-ospf-3] import-route bgp

[PE1-ospf-3] area 0.0.0.0

[PE1-ospf-3-area-0.0.0.0] network 10.11.2.0 0.0.0.255

[PE1-ospf-3-area-0.0.0.0] quit

[PE1-ospf-3] quit

2. Configure PE 2:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE2> system-view

[PE2] router id 1.1.1.2

[PE2] multicast routing

[PE2-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE2] mpls lsr-id 1.1.1.2

[PE2] mpls ldp

[PE2-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE2] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE2] interface gigabitethernet 1/0/5

[PE2-GigabitEthernet1/0/5] port link-mode bridge

[PE2-GigabitEthernet1/0/5] port service-loopback group 1

[PE2-GigabitEthernet1/0/5] quit

# Assign an IP address to VLAN-interface 2, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE2] interface vlan-interface 2

[PE2-Vlan-interface2] ip address 10.10.1.2 24

[PE2-Vlan-interface2] pim sm

[PE2-Vlan-interface2] mpls enable

[PE2-Vlan-interface2] mpls ldp enable

[PE2-Vlan-interface2] quit

# Assign an IP address to VLAN-interface 3, and enable PIM-SM and MPLS on the interface.

[PE2] interface vlan-interface 3

[PE2-Vlan-interface3] ip address 192.168.1.1 24

[PE2-Vlan-interface3] pim sm

[PE2-Vlan-interface3] mpls enable

[PE2-Vlan-interface3] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[PE2] interface loopback 1

[PE2-LoopBack1] ip address 1.1.1.2 32

[PE2-LoopBack1] pim sm

[PE2-LoopBack1] quit

# Assign an IP address to Loopback 2, and enable PIM-SM on the interface.

[PE2] interface loopback 2

[PE2-LoopBack2] ip address 11.11.11.11 32

[PE2-LoopBack2] pim sm

[PE2-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP for the public network instance.

[PE2] pim

[PE2-pim] c-bsr 11.11.11.11

[PE2-pim] c-rp 11.11.11.11

[PE2-pim] quit

# Configure a BSR message boundary.

[PE2] interface vlan-interface 3

[PE2-Vlan-interface3] pim bsr-boundary

[PE2-Vlan-interface3] quit

# Establish an MSDP peering relationship.

[PE2] msdp

[PE2-msdp] encap-data-enable

[PE2-msdp] peer 1.1.1.3 connect-interface loopback 1

# Configure a static route.

[PE2] ip route-static 1.1.1.3 32 vlan-interface 3 192.168.1.2

# Configure BGP.

[PE2] bgp 100

[PE2-bgp] group pe2-pe1 internal

[PE2-bgp] peer pe2-pe1 connect-interface loopback 1

[PE2-bgp] peer 1.1.1.1 group pe2-pe1

[PE2-bgp] group pe2-pe3 external

[PE2-bgp] peer pe2-pe3 as-number 200

[PE2-bgp] peer pe2-pe3 connect-interface loopback 1

[PE2-bgp] peer 1.1.1.3 group pe2-pe3

[PE2-bgp] address-family ipv4

[PE2-bgp-ipv4] peer pe2-pe1 enable

[PE2-bgp-ipv4] peer pe2-pe1 route-policy map2 export

[PE2-bgp-ipv4] peer pe2-pe1 label-route-capability

[PE2-bgp-ipv4] peer pe2-pe3 enable

[PE2-bgp-ipv4] peer pe2-pe3 route-policy map1 export

[PE2-bgp-ipv4] peer pe2-pe3 label-route-capability

[PE2-bgp-ipv4] import-route ospf 1

[PE2-bgp-ipv4] quit

[PE2–bgp] quit

# Configure OSPF.

[PE2] ospf 1

[PE2-ospf-1] area 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 11.11.11.11 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Configure a routing policy.

[PE2] route-policy map1 permit node 10

[PE2-route-policy-map1-10] apply mpls-label

[PE2-route-policy-map1-10] quit

[PE2] route-policy map2 permit node 10

[PE2-route-policy-map2-10] if-match mpls-label

[PE2-route-policy-map2-10] apply mpls-label

[PE2-route-policy-map2-10] quit

3. Configure PE 3:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE3> system-view

[PE3] router id 1.1.1.3

[PE3] multicast routing

[PE3-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE3] mpls lsr-id 1.1.1.3

[PE3] mpls ldp

[PE3-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE3] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE3] interface gigabitethernet 1/0/5

[PE3-GigabitEthernet1/0/5] port link-mode bridge

[PE3-GigabitEthernet1/0/5] port service-loopback group 1

[PE3-GigabitEthernet1/0/5] quit

# Assign an IP address to VLAN-interface 4, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE3] interface vlan-interface 4

[PE3-Vlan-interface4] ip address 10.10.2.1 24

[PE3-Vlan-interface4] pim sm

[PE3-Vlan-interface4] mpls enable

[PE3-Vlan-interface4] mpls ldp enable

[PE3-Vlan-interface4] quit

# Assign an IP address to VLAN-interface 3, and enable PIM-SM and MPLS on the interface.

[PE3] interface vlan-interface 3

[PE3-Vlan-interface3] ip address 192.168.1.2 24

[PE3-Vlan-interface3] pim sm

[PE3-Vlan-interface3] mpls enable

[PE3-Vlan-interface3] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[PE3] interface loopback 1

[PE3-LoopBack1] ip address 1.1.1.3 32

[PE3-LoopBack1] pim sm

[PE3-LoopBack1] quit

# Assign an IP address to Loopback 2, and enable PIM-SM on the interface.

[PE3] interface loopback 2

[PE3-LoopBack2] ip address 22.22.22.22 32

[PE3-LoopBack2] pim sm

[PE3-LoopBack2] quit

# Configure Loopback 2 as a C-BSR and a C-RP for the public network instance.

[PE3] pim

[PE3-pim] c-bsr 22.22.22.22

[PE3-pim] c-rp 22.22.22.22

[PE3-pim] quit

# Configure a BSR message boundary.

[PE3] interface vlan-interface 3

[PE3-Vlan-interface3] pim bsr-boundary

[PE3-Vlan-interface3] quit

# Establish an MSDP peering relationship.

[PE3] msdp

[PE3-msdp] encap-data-enable

[PE3-msdp] peer 1.1.1.2 connect-interface loopback 1

# Configure a static route.

[PE3] ip route-static 1.1.1.2 32 vlan-interface 3 192.168.1.1

# Configure BGP.

[PE3] bgp 200

[PE3-bgp] group pe3-pe4 internal

[PE3-bgp] peer pe3-pe4 connect-interface loopback 1

[PE3-bgp] peer 1.1.1.4 group pe3-pe4

[PE3-bgp] group pe3-pe2 external

[PE3-bgp] peer pe3-pe2 as-number 100

[PE3-bgp] peer pe3-pe2 connect-interface loopback 1

[PE3-bgp] peer 1.1.1.2 group pe3-pe2

[PE3-bgp] address-family ipv4

[PE3-bgp-ipv4] peer pe3-pe4 enable

[PE3-bgp-ipv4] peer pe3-pe4 route-policy map2 export

[PE3-bgp-ipv4] peer pe3-pe4 label-route-capability

[PE3-bgp-ipv4] peer pe3-pe2 enable

[PE3-bgp-ipv4] peer pe3-pe2 route-policy map1 export

[PE3-bgp-ipv4] peer pe3-pe2 label-route-capability

[PE3-bgp-ipv4] import-route ospf 1

[PE3-bgp-ipv4] quit

[PE3–bgp] quit

# Configure OSPF.

[PE3] ospf 1

[PE3-ospf-1] area 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] network 10.10.2.0 0.0.0.255

[PE3-ospf-1-area-0.0.0.0] quit

[PE3-ospf-1] quit

# Configure a routing policy.

[PE3] route-policy map1 permit node 10

[PE3-route-policy-map1-10] apply mpls-label

[PE3-route-policy-map1-10] quit

[PE3] route-policy map2 permit node 10

[PE3-route-policy-map2-10] if-match mpls-label

[PE3-route-policy-map2-10] apply mpls-label

[PE3-route-policy-map2-10] quit

4. Configure PE 4:

# Configure a global router ID, and enable IP multicast routing on the public network.

<PE4> system-view

[PE4] router id 1.1.1.4

[PE4] multicast routing

[PE4-mrib] quit

# Configure an MPLS LSR ID, and enable the LDP capability.

[PE4] mpls lsr-id 1.1.1.4

[PE4] mpls ldp

[PE4-ldp] quit

# Create service group 1 and specify the multicast tunnel service for the group.

[PE4] service-loopback group 1 type multicast-tunnel

# Assign GigabitEthernet 1/0/5 to service group 1.

[PE4] interface gigabitethernet 1/0/5

[PE4-GigabitEthernet1/0/5] port link-mode bridge

[PE4-GigabitEthernet1/0/5] port service-loopback group 1

[PE4-GigabitEthernet1/0/5] quit

# Create a VPN instance named a and configure an RD and route target attributes for the instance.

[PE4] ip vpn-instance a

[PE4-vpn-instance-a] route-distinguisher 100:1

[PE4-vpn-instance-a] vpn-target 100:1 export-extcommunity

[PE4-vpn-instance-a] vpn-target 100:1 import-extcommunity

[PE4-vpn-instance-a] quit

# Enable IP multicast routing for VPN instance a.

[PE4] multicast routing vpn-instance a

[PE4-mrib-a] quit

# Create an MD for VPN instance a, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE4] multicast-domain vpn-instance a

[PE4-md-a] default-group 239.1.1.1

[PE4-md-a] source loopback 1

[PE4-md-a] data-group 225.1.1.0 28

[PE4-md-a] quit

# Create a VPN instance named b and configure an RD and route target attributes for the instance.

[PE4] ip vpn-instance b

[PE4-vpn-instance-b] route-distinguisher 200:1

[PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity

[PE4-vpn-instance-b] vpn-target 200:1 import-extcommunity

[PE4-vpn-instance-b] quit

# Enable IP multicast routing for VPN instance b.

[PE4] multicast routing vpn-instance b

[PE4-mrib-b] quit

# Create an MD for VPN instance b, and specify the default-group, the MD source interface, and the data-group range for the MD.

[PE4] multicast-domain vpn-instance b

[PE4-md-b] default-group 239.4.4.4

[PE4-md-b] source loopback 1

[PE4-md-b] data-group 225.4.4.0 28

[PE4-md-b] quit

# Assign an IP address to VLAN-interface 4, and enable PIM-SM, MPLS capability, and LDP capability on the interface.

[PE4] interface vlan-interface 4

[PE4-Vlan-interface4] ip address 10.10.2.2 24

[PE4-Vlan-interface4] pim sm

[PE4-Vlan-interface4] mpls enable

[PE4-Vlan-interface4] mpls ldp enable

[PE4-Vlan-interface4] quit

# Bind VLAN-interface 13 with VPN instance a, assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface.

[PE4] interface vlan-interface 13

[PE4-Vlan-interface13] ip binding vpn-instance a

[PE4-Vlan-interface13] ip address 10.11.3.1 24

[PE4-Vlan-interface13] pim sm

[PE4-Vlan-interface13] quit

# Bind VLAN-interface 14 with VPN instance b, assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface.

[PE4] interface vlan-interface 14

[PE4-Vlan-interface14] ip binding vpn-instance b

[PE4-Vlan-interface14] ip address 10.11.4.1 24

[PE4-Vlan-interface14] pim sm

[PE4-Vlan-interface14] quit

# Assign an IP address to Loopback 1, and enable PIM-SM.

[PE4] interface loopback 1

[PE4-LoopBack1] ip address 1.1.1.4 32

[PE4-LoopBack1] pim sm

[PE4-LoopBack1] quit

# Configure BGP.

[PE4] bgp 200

[PE4-bgp] group pe4-pe3 internal

[PE4-bgp] peer pe4-pe3 connect-interface loopback 1

[PE4-bgp] peer 1.1.1.3 group pe4-pe3

[PE4-bgp] group pe4-pe1 external

[PE4-bgp] peer pe4-pe1 as-number 100

[PE4-bgp] peer pe4-pe1 ebgp-max-hop 255

[PE4-bgp] peer pe4-pe1 connect-interface loopback 1

[PE4-bgp] peer 1.1.1.1 group pe4-pe1

[PE4–bgp] ip vpn-instance a

[PE4-bgp-a] address-family ipv4

[PE4-bgp-ipv4-a] import-route ospf 2

[PE4-bgp-ipv4-a] import-route direct

[PE4-bgp-ipv4-a] quit

[PE4-bgp-a] quit

[PE4–bgp] ip vpn-instance b

[PE4-bgp-b] address-family ipv4

[PE4-bgp-ipv4-b] import-route ospf 3

[PE4-bgp-ipv4-b] import-route direct

[PE4-bgp-ipv4-b] quit

[PE4-bgp-b] quit

[PE4–bgp] address-family ipv4

[PE4-bgp-ipv4] peer pe4-pe3 enable

[PE4-bgp-ipv4] peer pe4-pe3 label-route-capability

[PE4-bgp-ipv4] quit

[PE4–bgp] address-family vpnv4

[PE4–bgp-vpnv4] peer pe4-pe1 enable

[PE4–bgp-vpnv4] quit

[PE4–bgp] quit

# Configure OSPF.

[PE4] ospf 1

[PE4-ospf-1] area 0.0.0.0

[PE4-ospf-1-area-0.0.0.0] network 1.1.1.4 0.0.0.0

[PE4-ospf-1-area-0.0.0.0] network 10.10.2.0 0.0.0.255

[PE4-ospf-1-area-0.0.0.0] quit

[PE4-ospf-1] quit

[PE4] ospf 2 vpn-instance a

[PE4-ospf-2] import-route bgp

[PE4-ospf-2] area 0.0.0.0

[PE4-ospf-2-area-0.0.0.0] network 10.11.3.0 0.0.0.255

[PE4-ospf-2-area-0.0.0.0] quit

[PE4-ospf-2] quit

[PE4] ospf 3 vpn-instance b

[PE4-ospf-3] import-route bgp

[PE4-ospf-3] area 0.0.0.0

[PE4-ospf-3-area-0.0.0.0] network 10.11.4.0 0.0.0.255

[PE4-ospf-3-area-0.0.0.0] quit

[PE4-ospf-3] quit

5. Configure CE a1:

# Enable IP multicast routing.

<CEa1> system-view

[CEa1] multicast routing

[CEa1-mrib] quit

# Assign an IP address to VLAN-interface 10, and enable PIM-SM on the interface.

[CEa1] interface vlan-interface 10

[CEa1-Vlan-interface10] ip address 10.11.5.1 24

[CEa1-Vlan-interface10] pim sm

[CEa1-Vlan-interface10] quit

# Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.

[CEa1] interface vlan-interface 11

[CEa1-Vlan-interface11] ip address 10.11.1.2 24

[CEa1-Vlan-interface11] pim sm

[CEa1-Vlan-interface11] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

[CEa1] interface loopback 1

[CEa1-LoopBack1] ip address 2.2.2.2 32

[CEa1-LoopBack1] pim sm

[CEa1-LoopBack1] quit

# Configure Loopback 1 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

# Configure OSPF.

[CEa1] ospf 1

[CEa1-ospf-1] area 0.0.0.0

[CEa1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[CEa1-ospf-1-area-0.0.0.0] network 10.11.1.0 0.0.0.255

[CEa1-ospf-1-area-0.0.0.0] network 10.11.5.0 0.0.0.255

[CEa1-ospf-1-area-0.0.0.0] quit

[CEa1-ospf-1] quit

6. Configure CE b1:

# Enable IP multicast routing.

<CEb1> system-view

[CEb1] multicast routing

[CEb1-mrib] quit

# Assign an IP address to VLAN-interface 20, and enable PIM-SM on the interface.

[CEb1] interface vlan-interface 20

[CEb1-Vlan-interface20] ip address 10.11.6.1 24

[CEb1-Vlan-interface20] pim sm

[CEb1-Vlan-interface20] quit

# Assign an IP address to VLAN-interface 12, and enable PIM-SM on the interface.

[CEb1] interface vlan-interface 12

[CEb1-Vlan-interface12] ip address 10.11.2.2 24

[CEb1-Vlan-interface12] pim sm

[CEb1-Vlan-interface12] quit

# Configure OSPF.

[CEb1] ospf 1

[CEb1-ospf-1] area 0.0.0.0

[CEb1-ospf-1-area-0.0.0.0] network 10.11.2.0 0.0.0.255

[CEb1-ospf-1-area-0.0.0.0] network 10.11.6.0 0.0.0.255

[CEb1-ospf-1-area-0.0.0.0] quit

[CEb1-ospf-1] quit

7. Configure CE a2:

# Enable IP multicast routing.

<CEa2> system-view

[CEa2] multicast routing

[CEa2-mrib] quit

# Assign an IP address to VLAN-interface 30, and enable IGMP on the interface.

[CEa2] interface vlan-interface 30

[CEa2-Vlan-interface30] ip address 10.11.7.1 24

[CEa2-Vlan-interface30] igmp enable

[CEa2-Vlan-interface30] quit

# Assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface.

[CEa2] interface vlan-interface 13

[CEa2-Vlan-interface13] ip address 10.11.3.2 24

[CEa2-Vlan-interface13] pim sm

[CEa2-Vlan-interface13] quit

# Configure OSPF.

[CEa2] ospf 1

[CEa2-ospf-1] area 0.0.0.0

[CEa2-ospf-1-area-0.0.0.0] network 10.11.3.0 0.0.0.255

[CEa2-ospf-1-area-0.0.0.0] network 10.11.7.0 0.0.0.255

[CEa2-ospf-1-area-0.0.0.0] quit

[CEa2-ospf-1] quit

8. Configure CE b2:

# Enable IP multicast routing.

<CEb2> system-view

[CEb2] multicast routing

[CEb2-mrib] quit

# Assign an IP address to VLAN-interface 40, and enable IGMP on the interface.

[CEb2] interface vlan-interface 40

[CEb2-Vlan-interface40] ip address 10.11.8.1 24

[CEb2-Vlan-interface40] igmp enable

[CEb2-Vlan-interface40] quit

# Assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface.

[CEb2] interface vlan-interface 14

[CEb2-Vlan-interface14] ip address 10.11.4.2 24

[CEb2-Vlan-interface14] pim sm

[CEb2-Vlan-interface14] quit

# Assign an IP address to Loopback 1, and enable PIM-SM on this interface.

[CEb2] interface loopback 1

[CEb2-LoopBack1] ip address 3.3.3.3 32

[CEb2-LoopBack1] pim sm

[CEb2-LoopBack1] quit

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

[CEb2] pim

[CEb2-pim] c-bsr 3.3.3.3

[CEb2-pim] c-rp 3.3.3.3

[CEb2-pim] quit

# Configure OSPF.

[CEb2] ospf 1

[CEb2-ospf-1] area 0.0.0.0

[CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0

[CEb2-ospf-1-area-0.0.0.0] network 10.11.4.0 0.0.0.255

[CEb2-ospf-1-area-0.0.0.0] network 10.11.8.0 0.0.0.255

[CEb2-ospf-1-area-0.0.0.0] quit

[CEb2-ospf-1] quit

Verifying the configuration

# Display information about local default-groups in VPN instances on PE 1.

[PE1] display multicast-domain default-group local

MD local default-group information:

Group address Source address Interface VPN instance

239.1.1.1 1.1.1.1 MTunnel0 a

239.4.4.4 1.1.1.1 MTunnel1 b

# Display information about local default-groups in VPN instances on PE 4.

[PE4] display multicast-domain default-group local

MD local default-group information:

Group address Source address Interface VPN instance

239.1.1.1 1.1.1.4 MTunnel0 a

239.4.4.4 1.1.1.4 MTunnel1 b

Troubleshooting MD VPN

This section describes common MD VPN problems and how to troubleshoot them.

A default-MDT cannot be established

Symptom

The default-MDT cannot be established. PIM neighboring relationship cannot be established between PE devices' interfaces that are in the same VPN instance.

Solution

1. Use the display interface command to examine the MTI interface state and address encapsulation on the MTI.

2. Use the display multicast-domain default-group command to verify that the same default-group address has been configured for the same VPN instance on different PE devices.

3. Use the display pim interface command to verify the following:

¡ PIM is enabled on at least one interface of the same VPN on different PE devices.

¡ The same PIM mode is running on all the interfaces of the same VPN instance on different PE devices and on all the interfaces of the P router.

4. Use the display ip routing-table command to verify that a unicast route exists from the VPN instance on the local PE device to the same VPN instance on each remote PE device.

5. Use the display bgp peer command to verify that the BGP peer connections have been correctly configured.

6. If the problem persists, contact H3C Support.

An MVRF cannot be created

Symptom

A VPN instance cannot create an MVRF correctly.

Solution

1. Use the display pim bsr-info command to verify that the BSR information exists on the public network and the VPN instance. If it does not, verify that a unicast route exists to the BSR.

2. Use the display pim rp-info command to examine the RP information. If no RP information is available, verify that a unicast route exists to the RP. Use the display pim neighbor command to verify that the PIM adjacencies have been correctly established on the public network and the VPN.

3. Use the ping command to examine the connectivity between the VPN DR and the VPN RP.

4. If the problem persists, contact H3C Support.

07-IP Multicast Configuration Guide

Introduction to MD VPN

PIM neighboring relationships in MD VPN

Default-MDT establishment in a PIM-DM network

Default-MDT establishment in a PIM-SM network

Default-MDT establishment in a PIM-SSM network

Default-MDT characteristics

Multicast protocol packet delivery

Multicast data packet delivery

Switching from default-MDT to data-MDT

Backward switching from data-MDT to default-MDT

MD VPN inter-AS option A

Configuring MD VPN

Configuration restrictions and guidelines

Configuration procedure

Configuring MDT switchover parameters

Configuring BGP MDT

Enabling BGP MDT peers or peer groups

Configuring a BGP MDT route reflector

Multicast VPN configuration examples

Intra-AS MD VPN configuration example

Network requirements

Configuration procedure

Verifying the configuration

MD VPN inter-AS option C configuration example

Network requirements

Configuration procedure

Verifying the configuration

Troubleshooting MD VPN

A default-MDT cannot be established

Symptom

Solution

An MVRF cannot be created

Symptom

Solution

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us