Cisco Catalyst 3750 - Including a Bordering PIM Dense-Mode Region in MSDP

32-17
Catalyst 3750 Metro Switch Software Configuration Guide
78-15870-01
Chapter 32 Configuring MSDP
Configuring MSDP
To bring the peer back up, use the no ip msdp shutdown {peer-name | peer address} global
configuration command. The TCP connection is reestablished
Including a Bordering PIM Dense-Mode Region in MSDP
You can configure MSDP on a switch that borders a PIM sparse-mode region with a dense-mode region.
By default, active sources in the dense-mode region do not participate in MSDP.
Note We do not recommend using the ip msdp border sa-address global configuration command. It is better
to configure the border router in the sparse-mode domain to proxy-register sources in the dense-mode
domain to the RP of the sparse-mode domain and have the sparse-mode domain use standard MSDP
procedures to advertise these sources.
Beginning in privileged EXEC mode, follow these steps to configure the border router to send SA
messages for sources active in the dense-mode region to the MSDP peers. This procedure is optional.
Note that the ip msdp originator-id global configuration command also identifies an interface to be
used as the RP address. If you configure both the ip msdp border sa-address and the ip msdp
originator-id global configuration commands, the address derived from the ip msdp originator-id
command determines the RP address.
To return to the default setting (active sources in the dense-mode region do not participate in MSDP),
use the no ip msdp border sa-address interface-id global configuration command.
Step 4
show running-config Verify your entries.
Step 5
copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Command Purpose
Step 1
configure terminal Enter global configuration mode.
Step 2
ip msdp border sa-address interface-id Configure the switch on the border between a dense-mode and
sparse-mode region to send SA messages about active sources in the
dense-mode region.
For interface-id, specify the interface from which the IP address is
derived and used as the RP address in SA messages.
The IP address of the interface is used as the Originator-ID, which is the
RP field in the SA message.
Step 3
ip msdp redistribute [list
access-list-name] [asn
aspath-access-list-number] [route-map
map]
Configure which (S,G) entries from the multicast routing table are
advertised in SA messages.
For more information, see the “Redistributing Sources” section on
page 32-9.
Step 4
end Return to privileged EXEC mode.
Step 5
show running-config Verify your entries.
Step 6
copy running-config startup-config (Optional) Save your entries in the configuration file.