A university streams lectures in two PIM-SM domains joined over an inter-domain link, requiring local RP failover in each campus and shared active sources across domains without a single global RP. Which MSDP and anycast RP design supports RP redundancy and inter-domain sourcing?
Select an answer to reveal the explanation.
Short Explanation
Your campuses each want a home-team RP that still gossips about sources next door. Local anycast RP gives fast failover while MSDP shares active sources between domains. It is shared newsroom wires feeding separate anchors on air.
Full Explanation
Anycast RP uses the same RP address on multiple routers with MSDP between them to synchronize active-source state, providing fast local failover because PIM registers and joins reach the nearest RP while source information remains consistent; extending MSDP peering across domains exchanges Source Active messages so receivers in one domain can discover sources registered in another without requiring a single global RP or native multicast RPF across administrative boundaries. A single static RP creates a single point of failure and suboptimal paths plus no inter-domain discovery; anycast without MSDP breaks consistency because each RP would know only locally registered sources and PIM joins cannot discover unknown remote sources; MSDP-only with a single BSR conflates bootstrap scope and still leaves a single RP failure domain while BSR does not cross inter-domain boundaries reliably. Exam caveat is that MSDP is the companion to anycast RP for state sync and inter-domain sharing, not a replacement for PIM, and practically check MSDP SA counts, peer RPF rules, and that each receiver joins toward its local anycast address.