Multi-Instance Msdp; Protocols And Standards; Msdp Configuration Task List - 3Com MSR 50 Series Configuration Manual

Multi-Instance MSDP

Protocols and Standards

MSDP Configuration
Task List
from Source encapsulated in the SA message. When the SA message reaches RP 2,
RP 2 decapsulates the message.
4 Receivers receive the multicast data along the RPT and directly joins the SPT rooted
at the multicast 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 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.
c
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.
■
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 makes VPN multicast transmission between different
PIM-SM domains possible.
A multicast router running multiple MSDP instances maintains an independent set
of MSDP mechanism for each instance it supports, including SA cache, peering
connection, timers, sending cache, and cache for exchanging information with
PIM, while one instance is isolated from another; therefore, interoperabitity
between MSDP and PIM-SM is available only within the same instance.
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)
Complete these tasks to configure MSDP:
Task
"Configuring Basic Functions of
MSDP" on page 1138

MSDP Configuration Task List

"Enabling MSDP" on page
1138
"Creating an MSDP Peer
Connection" on page 1139
"Configuring a Static RPF
Peer" on page 1139
1137
Remarks
Required
Required
Optional