736
Configuring MSDP
Configuring MSDP
To remove the default peer, use the no ip msdp default-peer ip-address | name global configuration command.
EXAMPLE
This example shows a partial configuration of Router A and Router C in Figure 93 on page 734. Each of these ISPs have
more than one customer (like the customer in Figure 93 on page 734) who use default peering (no BGP or MBGP). In that
case, they might have similar configurations. That is, they accept SAs only from a default peer if the SA is permitted by
the corresponding prefix list.
Router A
Router(config)# ip msdp default-peer 10.1.1.1
Router(config)# ip msdp default-peer 10.1.1.1 prefix-list site-a
Router(config)# ip prefix-list site-b permit 10.0.0.0/1
Router C
Router(config)# ip msdp default-peer 10.1.1.1 prefix-list site-a
Router(config)# ip prefix-list site-b permit 10.0.0.0/1
Caching Source-Active State
By default, the switch does not cache source/group pairs from received SA messages. When the switch forwards the
MSDP SA information, it does not store it in memory. Therefore, if a member joins a group soon after a SA message is
received by the local RP, that member needs to wait until the next SA message to hear about the source. This delay is
known as join latency.
If you want to sacrifice some memory in exchange for reducing the latency of the source information, you can configure
the switch to cache SA messages. This procedure is optional.
Note: An alternative to this command is the ip msdp sa-request global configuration command, which causes the switch
to send an SA request message to the MSDP peer when a new member for a group becomes active. For more
information, see the next section.
To Next Page
Loading...
Need help?
General
