Operation Manual – Multicast
H3C S3600 Series Ethernet Switches-Release 1510 Chapter 8 MSDP Configuration
8-4
As described above, RPs exchange information among one another through MSDP, a
multicast source registers with the nearest RP, and receivers join the nearest RPT. In
this way, RP load balancing can be achieved. When an RP fails, the multicast source
and receivers previously registered to/joined it will register to or join another nearest RP
automatically, thus implementing RP redundancy backup.
8.1.1 MSDP Working Mechanism
I. Identifying a multicast source and receiving multicast data
A network contains four PIM-SM domains, PIM-SM1, PIM-SM2, PIM-SM3, and
PIM-SM4. An MSDP peering relationship is established between RPs in different
domains. Multicast group members exist in the PIM-SM1 and PIM-SM4 domains. See
Figure 8-3.
RP1
Source
RP2
RP4
RP3
PIM-SM 1
PIM-SM 2
PIM-SM 3
PIM-SM 4
user
(5)
(5)
DR
(1)
(2)
user
(3)
(4)
(4)
(4)
(4)
(4)
(5)
Flow
MSDP peers
Figure 8-3 Identifying the multicast source and receiving multicast data
The complete interoperation process between a multicast source S in the PIM-SM1
domain and receivers in the PIM-SM1 and PIM-SM4 domains is as follows:
1) The multicast source S in the PIM-SM1 domain begins to send data packets.
2) The designated router (DR) connected to the multicast source S encapsulates the
received data in a Register message, and then forwards the message to RP1 in
the PIM-SM1 domain.
3) RP1 in the PIM-SM1 domain decapsulates the Register message, and then
forwards the message to all the members in the domain along the RPT. The
members in the domain can select whether to switch to the SPT.
4) At the same time, RP1 in the PIM-SM1 domain generates an SA message and
sends the message to the corresponding MSDP peers (RPs in the PIM-SM2 and
PIM-SM3 domains). Finally, the SA message is forwarded to the RP in the
PIM-SM4 domain. The SA message contains the IP address of the multicast
To Next Page
Loading...
Need help?
General