M6Vpe - HP MSR1002-4 Configuration Manual

When PE 1 joins the SPT rooted at PE 1, PE 2 also initiates a join process to the SPT rooted at PE 1.
A MDT is established when the two SPTs are finished.
MD VPN inter-AS option C
As shown in
•
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 69 MD VPN inter-AS option C
Public instance
CE 1
VPN instance
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.
Multicast packets are delivered as follows:
1. CE 1 forwards the VPN instance multicast packet to PE 1.
2. PE 1 encapsulates the 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.

M6VPE

The multicast IPv6 VPN provider edge (M6VPE) feature enables PE devices to transmit IPv6
multicast traffic of a VPN instance over the public network. Only the IPv4 network is available for the
backbone network.
As shown in
IPv6 multicast protocols. To transmit IPv6 multicast traffic between CE 1 and CE 2, configure M6VPE
on the PE devices.
Figure 69:
PE 1' P 1
AS 1
MTI
PE 1"
Figure 70, the public network runs IPv4 protocols, and sites of VPN instance VPN A run
ASBR ASBR
PE 3 PE 4 P 2
AS 2
MT
MD
192
PE 2'
MTI
PE 2" CE 2