43-3
Cisco ME 3400 Ethernet Access Switch Software Configuration Guide
OL-9639-07
Chapter 43 Configuring MSDP
Configuring MSDP
join reaches the source’s DR, a branch of the source tree has been built from the source to the RP in the
remote domain. Multicast traffic can now flow from the source across the source tree to the RP and then
down the shared tree in the remote domain to the receiver.
MSDP Benefits
MSDP has these benefits:
• It breaks up the shared multicast distribution tree. You can make the shared tree local to your
domain. Your local members join the local tree, and join messages for the shared tree never need to
leave your domain.
• PIM sparse-mode domains can rely only on their own RPs, decreasing reliance on RPs in another
domain. This increases security because you can prevent your sources from being known outside
your domain.
• Domains with only receivers can receive data without globally advertising group membership.
• Global source multicast routing table state is not required, saving memory.
Configuring MSDP
• Default MSDP Configuration, page 43-3
• Configuring a Default MSDP Peer, page 43-3 (required)
• Caching Source-Active State, page 43-6 (optional)
• Requesting Source Information from an MSDP Peer, page 43-7 (optional)
• Controlling Source Information that Your Switch Originates, page 43-8 (optional)
• Controlling Source Information that Your Switch Forwards, page 43-10 (optional)
• Controlling Source Information that Your Switch Receives, page 43-12 (optional)
• Configuring an MSDP Mesh Group, page 43-14 (optional)
• Shutting Down an MSDP Peer, page 43-14 (optional)
• Including a Bordering PIM Dense-Mode Region in MSDP, page 43-15 (optional)
• Configuring an Originating Address other than the RP Address, page 43-16 (optional)
Default MSDP Configuration
MSDP is not enabled, and no default MSDP peer exists.
Configuring a Default MSDP Peer
In this software release, because BGP and MBGP are not supported, you cannot configure an MSDP peer
on the local switch by using the ip msdp peer global configuration command. Instead, you define a
default MSDP peer (by using the ip msdp default-peer global configuration command) from which to
accept all SA messages for the switch. The default MSDP peer must be a previously configured MSDP
peer. Configure a default MSDP peer when the switch is not BGP- or MBGP-peering with an MSDP
peer. If a single MSDP peer is configured, the switch always accepts all SA messages from that peer.
To Next Page
Loading...
Need help?
General
