219
Figure 81 M6VPE network
IPv6 multicast traffic forwarding over the IPv4 public network is as follows:
1.
CE 1 forwards an IPv6 multicast packet for VPN instance
VPN A
to PE 1.
2.
PE 1 encapsulates the IPv6 multicast packet with an IPv4 packet header and transmits the IPv4
packet in the IPv4 backbone network.
3.
PE 2 decapsulates the IPv4 packet and forwards the IPv6 multicast packet to CE 2.
Multicast VPN configuration task list
Tasks at a glance
•
(Required.)
Enabling IP multicast routing for a VPN instance
•
(Required.)
Creating an MD for a VPN instance
•
(Required.)
•
(Required.)
•
(Required.)
Specifying the MD source interface
•
Configuring MDT switchover parameters
•
Configuring the RPF vector feature
•
Enabling data-group reuse logging
•
(Required.)
Configuring BGP MDT peers or peer groups
•
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 and the MD source interface are
specified and the MD source interface gets the public IP address.
•
To ensure correct MTI forwarding, create a service loopback group and specify the multicast
tunnel service 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 a minimum of 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.
CE 1
CE 2
P
PE 2
PE 1
Public network
VPN A
Site 1
VPN A
Site 2