Protocols and Standards
How MD-VPN Works
Share-MDT Established
n
A VPN corresponds to a unique MD, and an MD serves a unique VPN. There is a
one-to-one relationship between VPN, MD, MTI, share-group, and
switch-group-pool.
PIM neighboring relationships MD-VPN
Figure 371 PIM neighboring relationships MD-VPN
PE-P neighbors
PE-PE neighbors
PE-CE neighbors
CE 3
PIM neighboring relationships are established between two or more directly
interconnected devices on the same subnet. As shown in
three types of PIM neighboring relationships in MD-VPN, as follows:
PE-P neighboring relationship: PIM neighboring relationship established
■
between the public instance interface on a PE device and an interface on the P
device across the link.
PE-PE neighboring relationship: PIM neighboring relationship established after
■
a VPN instance on a PE device receives a PIM hello from a VPN instance on a
remote PE device through an MTI.
PE-CE neighboring relationship: PIM neighboring relationship established
■
between a VPN-instance-associated interface on a PE device and an interface
on a peer CE device.
The protocols/standards related to multicast VPN are as follows:
RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)
■
draft-rosen-vpn-mcast-08: Multicast in MPLS/BGP IP VPNs
■
For a VPN instance, multicast data transmission in the public network is
transparent. The seamless connection for VPN data transmission is completed at
CE 1
PE 1
P
PE 3
MD
How MD-VPN Works
PE 2
CE 2
Figure
371, there are
1285
Need help?
Do you have a question about the MSR 50 Series and is the answer not in the manual?
Questions and answers