H3C S3600 Series Operation Manual page 434

Operation Manual – Multicast
H3C S3600 Series Ethernet Switches-Release 1510
source, the multicast group address, the address of the RP that has generated the
SA message, and the first multicast data received by the RP in the PIM-SM1
domain.
5) If group members (namely, receivers) exist in the PIM-SM domains where MSDP
peers of RP1 reside (for example, if group members exist in the PIM-SM4 domain),
RP4 decapsulates the multicast data in the SA message and distributes the
multicast data to receivers along the RPT. RP4 also sends a Join message to the
multicast source S at the same time.
6) To avoid SA loop, MSDP peers perform RPF check on the received SA message.
After the RPF path is established, the data from the multicast source S is directly
sent to RP4 in the PIM-SM4 domain. Then, RP4 forwards the data along the RPT
within the domain. Now, the last-hop router connected to group members in the
PIM-SM4 domain selects whether to switch to the SPT.
II. Forwarding messages between MSDP peers and performing RPF check
To establish an MSDP peering relationship between routers, you have to create routes
between routers for SA messages to travel.
Assume that three autonomous systems (ASs) exist. They are AS1, AS2, and AS3.
Each AS has a PIM-SM domain associated with it. Each PIM-SM domain contains at
least one RP. See Figure 8-4.
Source
Figure 8-4 Forwarding SA messages between MSDP peers
As shown above, RP1 belongs to AS1. RP2, RP3 and RP4 belong to AS2. RP5 and
RP6 belong to AS3. An MSDP peering relationship exists among these RPs. RP2, RP3,
and RP4 form a mesh group. These MSDP peers perform RPF check and process SA
messages forwarded to one another according to the following rules:
If an MSDP peer sending an SA message is an RP in the PIM-SM domain where
the multicast source resides (for example, when RP1 sends an SA message to
(1)
(2)
RP1
AS1
RP2
AS2
(4)
RP4
mesh group
(6)
RP3
RP6
MSDP peers
SA message
8-5
Chapter 8 MSDP Configuration
static peer
(3)
(5)
RP5
AS3