RPs Fail to Exchange Registration Information

In Anycast RP application, RPs fail to exchange locally registered (S, G) information with each other.

Anycast RP cannot work normally if the requirements are not met:

The address of an MSDP peer must be different from the Anycast RP address. The candidate bootstrap router (C-BSR) and candidate rendezvous point (C-RP) must be configured on two devices or interfaces.
An MSDP peer performs RPF checks on received SA messages and discards the messages from a remote RP with the same IP address as itself. To prevent this problem, run the originating-rp command on the Anycast RP to replace the RP address in SA messages with a specified interface address.

Check whether the two MSDP peers have learned ARP entries from each other.
Run the display arp all command to check ARP entries on the two devices.
Check whether the two devices have reachable unicast routes to each other.
Run the display ip routing-table command to check routing tables of the two MSDP peers.
Check whether the interface addresses used to set up MSDP peer relationships are correct.
Run the display current-configuration command to check whether the local interface address is the same as the remote MSDP peer address configured on the remote device.
Check whether the RP configuration is correct.
In Anycast RP application, configure RPs with the same address on multiple switches in a PIM-SM domain. Generally, configure a loopback interface on each switch and assign the same IP address to the loopback interfaces.
Check whether the originating-rp command has been configured.
The originating-rp command must be configured, and the interface address specified by this command must be the same as the address of the local interface connected to the MSDP peer.
Check the C-BSR address and the Anycast RP address, and ensure that the two addresses are different.