zaro

What is MSDP used for?

Published in Multicast Routing 2 mins read

MSDP is primarily used for enabling inter-domain multicast routing and providing redundancy for Rendezvous Points in IPv4 PIM Sparse-Mode networks.

Understanding MSDP's Purpose

Multicast Source Discovery Protocol (MSDP) plays a crucial role in environments where multiple independent multicast routing domains need to exchange information about active multicast sources. This is particularly relevant in IPv4 PIM Sparse-Mode (PIM-SM) networks.

Based on RFC 4611, MSDP serves the following key functions:

  • Interconnecting Multiple PIM-SM Domains: MSDP acts as a bridge between different PIM-SM administrative domains. Each domain typically manages its own Rendezvous Point (RP), which is central to how sources and receivers discover each other in PIM-SM.
  • Enabling Inter-Domain Multicasting: By connecting these domains, MSDP allows multicast sources in one domain to be discovered by receivers in other domains. This makes it possible for multicast traffic originating in one part of the network to reach interested parties across organizational or geographical boundaries defined by separate PIM-SM domains.
  • Providing Rendezvous Point (RP) Redundancy: In a single PIM-SM domain, an RP can be a single point of failure. When interconnecting multiple domains via MSDP, information about sources is shared between RPs. This shared information allows receivers to potentially locate sources even if their local RP fails, provided another RP in an MSDP-connected domain knows about the source. This contributes significantly to the resilience of multicast services.

MSDP operates using TCP as its transport protocol, establishing peering sessions between MSDP speakers (typically the RPs or devices near them) in different domains to exchange Source-Active (SA) messages. These SA messages inform other RPs about active sources within their domain.

In essence, while each multicast tree in PIM-SM needs an RP, MSDP facilitates the communication between these RPs across different domains, making global multicast distribution and RP failover possible.