249
As shown in
, configure VPN instance A, create VPN instance B, and specify the
share-group on PE 1.
After the configuration, a share-MDT is established for VPN instance A and VPN instance B
respectively on the public network. After receiving multicast packets from Source 1, PE 1 duplicates
and encapsulates them, and forwards them to PE 2 and PE 3 along the share-MDT. PE 2 and PE 3
de-encapsulate and forward them to Receiver 1 and Receiver 2, respectively.
Receiver-side PE configuration
To implement multicast across VPNs, this configuration covers creating VPN instance that the
multicast source belongs to on the receiver-side PE, and configuring a share-group for the VPN
instance.
Figure 73 Receiver-side PE configuration
As shown in
, configure VPN instance B, create VPN instance A, and specify the
share-group on PE 3. Because PE 2 serves VPN A, create VPN instance A and specify the
share-group on PE 2. After the configuration, a share-MDT is established for VPN instance A. After
receiving multicast packets from Source 1, PE 1 encapsulates and forwards them to PE 2 and PE 3
along the share-MDT. PE 2 and PE 3 de-encapsulate and forward them to Receiver 1 and Receiver
2, respectively.
The following limitations apply to the source-side PE configuration and receiver-side PE
configuration schemes.
•
In the VPN to which the multicast sources belong and the VPNs to which the receivers belong,
PIM-SM, BIDIR-PIM, or PIM-SSM is supported, but PIM-DM is not supported.
•
The PIM modes, SSM group policies, and multicast source policies of the VPN to which the
multicast sources belong must be consistent with those of the VPNs to which the receivers
belong.
•
The RP must be in the same site of the same VPN as the multicast source.
•
Multicasting cannot be implemented along multiple VPNs. For example, the multicast data from
VPN A cannot be forwarded to VPN C by VPN B.
M6VPE
Multicast IPv6 VPN Provider Edge (M6VPE) is a transitional technology, which enables the carrier to
provide IPv6 multicast traffic exchange capability over the existing IPv4 public networks.