Msdp Support For Vpns; Protocols And Standards - HP 6125XLG Ip Multicast Configuration Manual

Figure 52 Intra-domain Anycast RP through MSDP
The operating process of Anycast RP through MSDP is as follows:
4. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP
1 in this example).
5. After receiving the IGMP report message from the receiver, the receiver-side DR sends a join
message toward the closest RP (RP 2 in this example). Therefore, an RPT rooted at this RP is
established.
6. The RPs share the registered multicast source information through SA messages. After getting the
multicast source information, RP 2 sends an (S, G) source-specific join message toward the source
to create an SPT.
7. When the multicast data reaches RP 2 along the SPT, the RP forwards the data along the RPT to the
receiver. After receiving the multicast data, the receiver-side DR determines whether to initiate an
RPT-to-SPT switchover process based on its configuration.

MSDP support for VPNs

Interfaces on the multicast routers in a VPN can set up MSDP peering relationships with each other. By
exchanging SA messages between MSDP peers, multicast data can be transmitted in a VPN across
different PIM-SM domains.
To support MSDP for VPNs, a multicast router that runs MSDP maintains an independent set of MSDP
mechanism for each VPN that it supports. These mechanisms include SA message cache, peering
connection, timers, sending cache, and cache for exchanging PIM messages.
One VPN is isolated from another, and MSDP and PIM-SM messages can be exchanged only within the
same VPN.

Protocols and standards

RFC 3618, Multicast Source Discovery Protocol (MSDP)
•
• RFC 3446, Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM)
and Multicast Source Discovery Protocol (MSDP)
144