HP A6600 Configuration Manual page 177

When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source,
it no longer relies on RPs in other PIM-SM domains. The receivers can override the RPs in other domains
and directly join the multicast source-based SPT.
RPF check rules for SA messages
As shown in
on routers within each AS and BGP or MBGP as the interoperation protocol among different ASs. Each
AS contains at least one PIM-SM domain, and each PIM-SM domain contains one ore more RPs. MSDP
peering relationships have been established among different RPs. RP 3, RP 4, and RP 5 are in an MSDP
mesh group. On RP 7, RP 6 is configured as its static RPF peer.
If only one MSDP peer exists in a PIM-SM domain, this PIM-SM domain is also called a stub domain. For
example, AS 4 in
MSDP peers at the same time. You can configure one or more remote MSDP peers as static RPF peers.
When an RP receives an SA message from a static RPF peer, the RP accepts the SA message and
forwards it to other peers without performing an RPF check.
Figure 52 Diagram for RPF check for SA messages
RP 1
(1)
RP 2
As illustrated in
check rules:
When RP 2 receives an SA message from RP 1
Because the source-side RP address carried in the SA message is the same as the MSDP peer address,
which means that the MSDP peer where the SA is from is the RP that has created the SA message, RP 2
accepts the SA message and forwards it to its other MSDP peer (RP 3).
When RP 3 receives the SA message from RP 2
Because the SA message is from an MSDP peer (RP 2) in the same AS, and the MSDP peer is the next hop
on the optimal path to the source-side RP, RP 3 accepts the message and forwards it to other peers (RP 4
and RP 5).
When RP 4 and RP 5 receive the SA message from RP 3
Because the SA message is from an MSDP peer (RP 3) in the same mesh group, RP 4 and RP 5 both
accept the SA message, but they do not forward the message to other members in the mesh group.
Instead, they forward it to other MSDP peers (RP 6 in this example) out of the mesh group.
When RP 6 receives the SA messages from RP 4 and RP 5 (suppose RP 5 has a higher IP address)
Figure 52, the autonomous systems in the network are AS 1 through AS 5, with IGP enabled
Figure 52 is a stub domain. The MSDP peer in a stub domain can have multiple remote
Source
AS 1
(3)
(2)
Mesh group
RP 3
AS 2
(3)
MSDP peers
Static RPF peers
SA message
Figure 52, these MSDP peers dispose of SA messages according to the following RPF
RP 5 RP 9
(4)
AS 3
(4)
RP 4 RP 6
166
RP 8
(7)
AS 5
(6)
(5)
RP 7
AS 4