Click the Exhibit button.
Referring to the exhibit, anycast RP is implemented to ensure multicast service availability. The source is currently sending multicast traffic using group 239.1.1.1 and R3 is receiving PIM register messages, but R2 does not have active source information.
In this scenario, what are two methods to receive the active source information on R2? (Choose two.)
In this scenario, anycast RP is implemented to ensure multicast service availability. However, R2 is not receiving active source information. One method to address this is to configure MSDP (Multicast Source Discovery Protocol) between R2 and R3. MSDP enables the RPs to share information about active sources, ensuring that all RPs have a consistent view of the multicast source. Another method is to configure an RP set in PIM on R2 and R3, which allows the RPs to communicate and forward PIM register messages to each other in the set. This ensures that all RPs in the set are aware of the active sources. Together, these methods facilitate the distribution of source information among the RPs, ensuring efficient multicast routing.
MSDP or anycast-PIM with rp-set should be configured on all anycast RP routers. https://www.juniper.net/documentation/us/en/software/junos/multicast/topics/topic-map/mcast-pim-anycast-rp.html
Should be B and C.
Anycast RP uses Multicast Source Discovery Protocol (MSDP) to discover and maintain a consistent view of the active sources. nclude the anycast-pim statement to configure anycast RP without MSDP (for example, if IPv6 is used for multicasting). The other RP routers that share the same IP address are configured using the rp-set statement. https://www.juniper.net/documentation/us/en/software/junos/multicast/topics/topic-map/mcast-pim-anycast-rp.html
Configure a set of rendezvous point (RP) addresses for anycast RP. You can configure up to 15 RPs. The remaining statements are explained separately. See CLI Explorer. https://www.juniper.net/documentation/us/en/software/junos/multicast/topics/ref/statement/rp-set-edit-protocols-pim.html
b and c