To prevent source active (SA) messages from being cyclically transmitted between MSDP peers, MSDP peers perform a reverse path forwarding (RPF) check on received SA messages and discard any SA messages that fail the check.
Rule 1: If an SA message is sent from an MSDP peer that functions as a source rendezvous point (RP) constructing the SA message, the receiving multicast device permits the SA message.
Rule 2: If an SA message is sent from an MSDP peer that is a static RPF peer, the receiving multicast device permits the SA message. A receiving multicast device can set up MSDP peer relationships with multiple other multicast devices. You can specify one or more MSDP peers as static RPF peers.
Rule 3: If the receiving multicast device has only one MSDP peer, the peer automatically becomes an RPF peer. The receiving multicast device permits SA messages sent from this peer.
Rule 4: If an SA message is sent from an MSDP peer that is in the same mesh group as the receiving multicast device, the receiving multicast device permits the SA message. The receiving multicast device does not forward the SA message to MSDP peers in the mesh group but forwards it to all MSDP peers outside the mesh group.
Rule 5: If an SA message is sent from an MSDP peer that is a route advertiser or the next hop of a source RP, the receiving multicast device permits the SA message. If a network has multiple equal-cost routes to a source RP, the receiving multicast device permits SA messages sent from all MSDP peers on the equal-cost routes.
Rule 6: If a network has inter-AS routes to a source RP, the receiving multicast device permits SA messages sent from MSDP peers whose AS numbers are recorded in the AS-path.
If an RP address is a local address, an RPF check fails.