Multi-Instance Msdp - HP A5500 SI Switch Series Configuration Manual

Figure 57 Typical network diagram of Anycast RP
The work process of Anycast RP is as follows:
The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with
1.
its multicast data encapsulated in the register message. When the register message arrives at RP 1,
RP 1 de-encapsulates the message.
Receivers send join messages to the nearest RP to join in the RPT rooted as this RP. In this example,
2.
Receiver joins the RPT rooted at RP 2.
RPs share the registered multicast information by means of SA messages. In this example, RP 1
3.
creates an SA message and sends it to RP 2, with the multicast data from Source encapsulated in
the SA message. When the SA message reaches RP 2, RP 2 de-encapsulates the message.
Receivers receive the multicast data along the RPT and directly join the SPT rooted at the multicast
4.
source. In this example, RP 2 forwards the multicast data down the RPT. When Receiver receives
the multicast data from Source, it directly joins the SPT rooted at Source.
The significance of Anycast RP is as follows:
Optimal RP path—A multicast source registers with the nearest RP so that an SPT with the optimal
•
path is built. A receiver joins the nearest RP so that an RPT with the optimal path is built.
Load balancing between RPs—Each RP maintains just part of the source/group information within
•
the PIM-SM domain and forward part of the multicast data, thereby achieving load balancing
between different RPs.
Redundancy backup between RPs—When an RP fails, the multicast source that previously
•
registered with the RP or the receivers that previously joined the RP will register with or join another
nearest RP, thereby achieving redundancy backup between RPs.
CAUTION:
Be sure to configure a 32-bit subnet mask—255.255.255.255—for the Anycast RP address. That is,
configure the Anycast RP address into a host address.
An MSDP peer address must be different from the Anycast RP address.

Multi-instance MSDP

MSDP peering relationship can be built between multicast-enabled interfaces that belong to the same
instance. Through exchanges of SA messages between MSDP peers, the MSDP mechanism enables VPN
multicast transmission between different PIM-SM domains.
RP 1
Router A
Source
PIM-SM
MSDP peers
SA message
RP 2
Router B
Receiver
194