1
The SA message identifies the source address, the group that the source is sending to, and the address or
the originator ID of the RP, if configured.
2
Each MSDP peer that receives the SA message floods the SA message to all of its peers downstream from
the originator. In some cases (such as the case with the RPs in PIM-SM domains B and C in the figure),
an RP may receive a copy of an SA message from more than one MSDP peer. To prevent looping, the RP
consults the BGP next-hop database to determine the next hop toward the originator of the SA message.
If both MBGP and unicast BGP are configured, MBGP is checked first, and then unicast BGP. That
next-hop neighbor is the RPF-peer for the originator. SA messages that are received from the originator
on any interface other than the interface to the RPF peer are dropped. The SA message flooding process,
therefore, is referred to as peer-RPF flooding. Because of the peer-RPF flooding mechanism, BGP or
MBGP must be running in conjunction with MSDP.
(M)BGP is not required in MSDP mesh group scenarios. For more information about MSDP mesh groups,
see the
Configuring an MSDP Mesh Group, on page 193
section.
Note
(M)BGP is not required in default MSDP peer scenarios or in scenarios where only one MSDP peer is
configured. For more information, see the
Configuring a Default MSDP Peer, on page 192
section.
Note
1
When an RP receives an SA message, it checks to see whether there are any members of the advertised
groups in its domain by checking to see whether there are interfaces on the group
’
s (*, G) outgoing interface
list. If there are no group members, the RP does nothing. If there are group members, the RP sends an (S,
G) join toward the source. As a result, a branch of the interdomain source tree is constructed across
autonomous system boundaries to the RP. As multicast packets arrive at the RP, they are then forwarded
down its own shared tree to the group members in the RP
’
s domain. The members
’
DRs then have the
option of joining the rendezvous point tree (RPT) to the source using standard PIM-SM procedures.
2
The originating RP continues to send periodic SA messages for the (S, G) state every 60 seconds for as
long as the source is sending packets to the group. When an RP receives an SA message, it caches the SA
message. Suppose, for example, that an RP receives an SA message for (172.16.5.4, 228.1.2.3) from
originating RP 10.5.4.3. The RP consults its mroute table and finds that there are no active members for
group 228.1.2.3, so it passes the SA message to its peers downstream of 10.5.4.3. If a host in the domain
then sends a join to the RP for group 228.1.2.3, the RP adds the interface toward the host to the outgoing
interface list of its (*, 224.1.2.3) entry. Because the RP caches SA messages, the device will have an entry
for (172.16.5.4, 228.1.2.3) and can join the source tree as soon as a host requests a join.
In all current and supported software releases, caching of MSDP SA messages is mandatory and cannot
be manually enabled or disabled. By default, when an MSDP peer is configured, the
ip multicast
cache-sa-state
command will automatically be added to the running configuration.
Note
MSDP Message Types
There are four basic MSDP message types, each encoded in their own Type, Length, and Value (TLV) data
format.
IP Multicast Routing Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3650 Switches)
172
OL-29890-01
Configuring MSDP
MSDP Message Types
