H3C Technologies H3C SecPath F1000-E - Manual (Page 68)

7
• Load balancing between RPs: Each RP just needs to maintain part of the source/group information
within the PIM-SM domain and forward part of the multicast data, thus achieving load balancing
between different RPs.
• Redundancy backup between RPs: When an RP fails, the multicast source previously registered on
it or the receivers previous joined it will register with or join another nearest RP, thus achieving
redundancy backup between RPs.
CAUTION:
•
Be sure to configure a 32-bit subnet mask (255.255.255.255) for the Anycast RP address,
namely configure the Anycast RP address into a host address.
• An MSDP peer address must be different from the Anycast RP address.
Protocols and Standards
MSDP is documented in the following specifications:
• RFC 3618 Multicast Source Discovery Protocol (MSDP)
• RFC 3446 Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM)
and Multicast Source Discovery Protocol (MSDP)
MSDP Configuration Task List
Complete these tasks to configure MSDP:
Task Remarks
Enabling MSDP Required
Creating an MSDP Peer Connection Required
Configuring Basic Functions
of MSDP
Configuring a Static RPF Peer Optional
Configuring MSDP Peer Description Optional
Configuring an MSDP Mesh Group Optional
Configuring an MSDP Peer
Connection
Configuring MSDP Peer Connection Control Optional
Configuring SA Message Content Optional
Configuring SA Request Messages Optional
Configuring SA Message Filtering Rules Optional
Configuring SA Messages
Related Parameters
Configuring the SA Cache Mechanism Optional
Configuring Basic Functions of MSDP
NOTE:
All the configuration tasks should be carried out on RPs in PIM-SM domains, and each of these RPs
acts as an MSDP peer.