- Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
Feedback
Table Of Contents
Multicast Source Discovery Protocol Commands
Multicast Source Discovery Protocol Commands
Use the commands in this chapter to configure and monitor Multicast Source Discovery Protocol (MSDP). For configuration information and examples of MSDP, refer to the "Configuring Multicast Source Discovery Protocol" chapter of the Cisco IOS IP Configuration Guide.
clear ip msdp peer
To clear the TCP connection to the specified Multicast Source Discovery Protocol (MSDP) peer, use the clear ip msdp peer command in EXEC mode.
clear ip msdp peer {peer-address | peer-name}
Syntax Description
peer-address | peer-name
IP address or name of the MSDP peer to which the TCP connection is cleared.
Command Modes
EXEC
Command History
Usage Guidelines
This command closes the TCP connection to the peer, resets all the MSDP peer statistics, and clears the input and output queues to and from the MSDP peer.
Examples
The following example clears the TCP connection to the MSDP peer at 10.3.32.154:
Router# clear ip msdp peer 10.3.32.154Related Commands
clear ip msdp sa-cache
To clear Multicast Source Discovery Protocol (MSDP) Source-Active (SA) cache entries, use the clear ip msdp sa-cache command in EXEC mode.
clear ip msdp sa-cache [group-address | group-name]
Syntax Description
group-address | group-name
(Optional) Multicast group address or name for which Source-Active entries are cleared from the Source-Active cache.
Command Modes
EXEC
Command History
Usage Guidelines
In order to have any SA entries in the cache to clear, SA caching must have been enabled with the ip msdp cache-sa-state command
If no multicast group is identified by group address or name, all SA cache entries are cleared.
Examples
The following example clears the SA entries for the multicast group 10.3.53.154 from the cache:
Router# clear ip msdp sa-cache 10.3.53.154Related Commands
ip msdp cache-sa-state
Enables the router to create SA state.
show ip msdp sa-cache
Displays (S,G) state learned from MSDP peers.
clear ip msdp statistics
To clear statistics counters for one or all of the Multicast Source Discovery Protocol (MSDP) peers without resetting the sessions, use the clear ip msdp statistics command in EXEC mode.
clear ip msdp statistics [peer-address | peer-name]
Syntax Description
peer-address | peer-name
(Optional) Address or name of the MSDP peers whose statistics counters, reset count, and input/output count are cleared.
Command Modes
EXEC
Command History
Examples
The following example clears the counters for the peer named sanjose:
Router# clear ip msdp statistics sanjoseip msdp border
To configure a router that borders a Protocol Independent Multicast (PIM) sparse mode region and dense mode region to use Multicast Source Discovery Protocol (MSDP), use the ip msdp border command in global configuration mode. To prevent this action, use the no form of this command.
ip msdp border sa-address type number
no ip msdp border sa-address type number
Syntax Description
Defaults
The active sources in the dense mode region will not participate in MSDP.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command if you want the router to send SA messages for sources active in the PIM dense mode region to MSDP peers.
Note
We recommend configuring the border router in the sparse mode domain to proxy-register sources in the dense mode domain, and have the sparse mode domain use standard MSDP procedures to advertise these sources.
Note
Note
Examples
In the following example, the local router is not an RP. It borders a PIM sparse mode region with a dense mode region. It uses the IP address of Ethernet interface 0 as the "RP" address in SA messages.
ip msdp border sa-address ethernet0Related Commands
ip msdp cache-rejected-sa
To cache Source-Active (SA) request messages rejected from Multicast Source Discovery Protocol (MSDP) peers, use the ip msdp cache-rejected-sa command in global configuration mode. To stop tracking SA request messages, use the no form of this command.
ip msdp cache-rejected-sa number-of-entries
no ip msdp cache-rejected-sa number-of-entries
Syntax Description
Defaults
Rejected SA request messages are not stored.
Command Modes
Global configuration
Command History
12.0(22)S
This command was introduced.
12.1E
This command was integrated into Cisco IOS Release 12.1E.
12.2
This command was integrated into Cisco IOS Release 12.2.
Usage Guidelines
Use the ip msdp cache-rejected-sa command to configure the router to store SA messages that have been recently received from an MSDP peer but were rejected. Once this command is enabled, the router will maintain a rejected SA cache that stores the most recent rejected SA messages. The number of rejected SA message entries to be stored in the rejected SA cache is configured with the number-of-entries argument. If the rejected SA cache overflows, entries are overwritten, starting from the first entry.
Note
Use the show ip msdp sa-cache command with the rejected-sa keyword to display SA messages rejected from MSDP peers.
Examples
The following example shows how to enable the router to store a maximum of 200 messages rejected from MSDP peers:
Router(config)# ip msdp cache-rejected-sa 200Related Commands
ip msdp cache-sa-state
To have the router create Source-Active (SA) state, use the ip msdp cache-sa-state command in global configuration mode.
ip msdp cache-sa-state [vrf vrf-name]
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
The router creates SA state for all Multicast Source Discovery Protocol (MSDP) SA messages it receives.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is automatically configured if at least one MSDP peer is configured. It cannot be disabled.
If you are running a version of Cisco IOS software prior to Release 12.1(7), we recommend enabling the ip msdp cache-sa-state command.
Examples
The following example shows how the ip msdp cache-sa-state command is enabled when an MSDP peer is configured:
...ip classlessip msdp peer 192.168.1.2 connect-source Loopback0ip msdp peer 192.169.1.7ip msdp mesh-group outside-test 192.168.1.2ip msdp cache-sa-stateip msdp originator-id Loopback0...Related Commands
ip msdp default-peer
To define a default peer from which to accept all Multicast Source Discovery Protocol (MSDP) Source-Active (SA) messages, use the ip msdp default-peer command in global configuration mode. To remove the default peer, use the no form of this command.
ip msdp default-peer {peer-address | peer-name} [prefix-list list]
no ip msdp default-peer
Syntax Description
Defaults
No default MSDP peer exists.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip msdp default-peer command if you do not want to configure your MSDP peer to be a BGP peer also.
If only one MSDP peer is configured (with the ip msdp peer command), it will be used as a default peer. Therefore, you need not configure a default peer with this command.
If the prefix-list list keyword and argument are not specified, all SA messages received from the configured default peer are accepted.
Remember to configure a BGP prefix list if you intend to configure the prefix-list list keyword and argument with the ip msdp default-peer command.
If the prefix-list list keyword and argument are specified, SA messages originated from rendezvous points (RPs) covered by the prefix-list list keyword and argument will be accepted from the configured default peer. If the prefix-list list keyword and argument are specified but no prefix list is configured, the default peer will be used for all prefixes.
You can enter multiple ip msdp default-peer commands, with or without the prefix-list keyword, as follows. However, all commands must either have the keyword or all must not have the keyword.
•
•
Examples
The following example configures the router at IP address 192.168.1.3 as the default peer to the local router:
ip msdp peer 192.168.1.3ip msdp peer 192.168.3.5ip msdp default-peer 192.168.1.3The following example configures two default peers:
ip msdp peer 172.18.2.3ip msdp peer 172.19.3.5ip msdp default-peer 172.18.2.3 prefix-list site-cip prefix-list site-a permit 172.18.0.0/16ip msdp default-peer 172.19.3.5 prefix-list site-aip prefix-list site-c permit 172.19.0.0/16Related Commands
ip msdp description
To add descriptive text to the configuration for a Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp description command in global configuration mode. To remove the description, use the no form of this command.
ip msdp description {peer-name | peer-address} text
no ip msdp description {peer-name | peer-address}
Syntax Description
peer-name | peer-address
Peer name or address to which this description applies.
text
Description of the MSDP peer.
Defaults
No description is associated with an MSDP peer.
Command Modes
Global configuration
Command History
Usage Guidelines
Configure a description to make the MSDP peer easier to identify. This description is visible in the output of the show ip msdp peer command.
Examples
The following example configures the router at the IP address 172.17.1.2 with a description indicating it is a router at customer A:
ip msdp description 172.17.1.2 router at customer aip msdp filter-sa-request
To configure the router to send Source-Active (SA) request messages to the Multicast Source Discovery Protocol (MSDP) peer when a new joiner from a group becomes active, use the ip msdp filter-sa-request command in global configuration mode. To prevent this action, use the no form of this command.
ip msdp filter-sa-request {peer-address | peer-name} [list access-list]
no ip msdp filter-sa-request {peer-address | peer-name}
Syntax Description
Defaults
If this command is not configured, all SA request messages are honored. If this command is configured but no access list is specified, all SA request messages are ignored.
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the router honors all SA request messages from peers. Use this command if you want to control exactly which SA request messages the router will honor.
If no access list is specified, all SA request messages are ignored. If an access list is specified, only SA request messages from those groups permitted will be honored, and all others will be ignored.
Examples
The following example configures the router to filter SA request messages from the MSDP peer at 172.16.2.2. SA request messages from sources on the network 192.168.22.0 pass access list 1 and will be honored; all others will be ignored.
ip msdp filter sa-request 172.16.2.2 list 1access-list 1 permit 192.4.22.0 0.0.0.255Related Commands
ip msdp keepalive
To adjust the interval at which a Multicast Source Discovery Protocol (MSDP) peer will send keepalive messages and the interval at which the MSDP peer will wait for keepalive messages from other peers before declaring them down, use the ip msdp keepalive command in global configuration mode. To restore the default values, use the no form of this command.
ip msdp [vrf vrf-name] keepalive {peer-address | peer-name} keepalive-interval hold-time-interval
no ip msdp [vrf vrf-name] keepalive {peer-address | peer-name}
Syntax Description
Command Default
An MSDP peer sends keepalives messages at an interval of once every 60 seconds. The hold-time interval for an MSDP peer is set to 75 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip msdp keepalive command to adjust the interval at which an MSDP peer will send keepalive messages and the interval at which the MSDP peer will wait for keepalive messages from other peers before declaring them down.
Once an MSDP peering session is established, each side of the connection sends a keepalive message and sets a keepalive timer. If the keepalive timer expires, the local MSDP peer sends a keepalive message and restarts its keepalive timer; this interval is referred to as the keepalive interval. Use the keepalive-interval argument to adjust the interval for which keepalive messages will be sent. The keepalive timer is set to the value specified for the keepalive-interval argument when the peer comes up. The keepalive timer is reset to the value of the keepalive-interval argument whenever an MSDP keepalive message is sent to the peer and reset when the timer expires. The keepalive timer is deleted when an MSDP peering session is closed. By default, the keepalive timer is set to 60 seconds.
Note
The hold-time timer is initialized to the value of the hold-time-interval argument whenever an MSDP peering connection is established, and is reset to value of the hold-time-interval argument whenever an MSDP keepalive message is received. The hold-time timer is deleted whenever an MSDP peering connection is closed. By default, the hold-time interval is set to 75 seconds.
Use the hold-time-interval argument to adjust the interval at which the MSDP peer will wait for keepalive messages from other peers before declaring them down. By default, it may take as long as 75 seconds for an MSDP peer to detect that a peering session with another MSDP peer has gone down. In network environments with redundant MSDP peers, decreasing the hold-time interval (by lowering the value for hold-time-interval argument from the default of 75 seconds) can expedite the reconvergence time of MSDP peers in the event that an MSDP peer fails.
Note
Examples
The following example shows how to set the keepalive interval to 40 seconds and the hold-time interval to 55 seconds for the MSDP peer at 172.16.100.10:
ip msdp keepalive 172.16.100.10 40 55Related Commands
ip msdp mesh-group
To configure a Multicast Source Discovery Protocol (MSDP) peer to be a member of a mesh group, use the ip msdp mesh-group command in global configuration mode. To remove an MSDP peer from a mesh group, use the no form of this command.
ip msdp mesh-group mesh-name {peer-address | peer-name}
no ip msdp mesh-group mesh-name {peer-address | peer-name}
Syntax Description
mesh-name
Name of the mesh group.
peer-address | peer-name
IP address or name of the MSDP peer to be a member of the mesh group.
Defaults
The MSDP peers do not belong to a mesh group.
Command Modes
Global configuration
Command History
Usage Guidelines
A mesh group is a group of MSDP speakers that have fully meshed MSDP connectivity among themselves. Source-Active (SA) messages received from a peer in a mesh group are not forwarded to other peers in the same mesh group.
Mesh groups can be used to achieve two goals:
•
•
Examples
The following example configures the MSDP peer at address 192.168.1.3 to be a member of the mesh group named internal:
ip msdp mesh-group internal 192.168.1.3ip msdp originator-id
To allow a Multicast Source Discovery Protocol (MSDP) speaker that originates a Source-Active (SA) message to use the IP address of the interface as the rendezvous point (RP) address in the SA message, use the ip msdp originator-id command in global configuration mode. To prevent the RP address from being derived in this way, use the no form of this command.
ip msdp originator-id type number
no ip msdp originator-id type number
Syntax Description
type number
Interface type and number on the local router, whose IP address is used as the RP address in SA messages.
Defaults
The RP address is used as the originator ID.
Command Modes
Global configuration
Command History
Usage Guidelines
The ip msdp originator-id command identifies an interface type and number to be used as the RP address in an SA message.
Use this command if you want to configure a logical RP. Because only RPs and MSDP border routers originate SAs, there are times when it is necessary to change the ID used for this purpose.
If both the ip msdp border and the ip msdp originator-id commands are configured, the latter command prevails. That is, the address derived from the ip msdp originator-id command determines the address of the RP to be used in the SA message.
Examples
The following example configures the IP address of Ethernet interface 1 as the RP address in SA messages:
ip msdp originator-id ethernet1Related Commands
ip msdp border
Configures a router that borders a PIM sparse mode region and dense mode region to use MSDP.
ip msdp peer
To configure a Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp peer command in global configuration mode. To remove the peer relationship, use the no form of this command.
ip msdp peer {peer-name | peer-address} [connect-source type number] [remote-as as-number]
no ip msdp peer {peer-name | peer-address}
Syntax Description
Defaults
No MSDP peer is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
The router specified should also be configured as a BGP neighbor.
If you are also BGP peering with this MSDP peer, you should use the same IP address for MSDP as you do for BGP. However, you are not required to run BGP or multiprotocol BGP with the MSDP peer, as long as there is a BGP or MBGP path between the MSDP peers. If there is no path, you must configure the ip msdp default-peer command.
Examples
The following example configures the router at the IP address 192.168.1.2 as an MSDP peer to the local router. The neighbor belongs to autonomous system 109.
ip msdp peer 192.168.1.2 connect-source ethernet 0/0router bgp 110network 192.168.0.0neighbor 192.168.1.2 remote-as 109neighbor 192.168.1.2 update-source ethernet 0/0The following example configures the router at the IP address 192.168.1.3 as an MSDP peer to the local router:
ip msdp peer 192.168.1.3The following example configures the router at the IP address 192.168.1.4 to be an MSDP peer in autonomous system 109. The primary address of Ethernet interface 0/0 is used as the source address for the TCP connection.
ip msdp peer 192.168.1.4 connect-source ethernet 0/0 remote-as 109Related Commands
ip msdp redistribute
To configure which (S, G) entries from the multicast routing table are advertised in Source-Active (SA) messages originated to Multicast Source Discovery Protocol (MSDP) peers, use the ip msdp redistribute command in global configuration mode. To remove the filter, use the no form of this command.
ip msdp redistribute [list access-list] [asn as-access-list] [route-map map-name]
no ip msdp redistribute
Syntax Description
Defaults
If no portion of this command is configured, only local sources are advertised, provided they send to groups for which the router is a rendezvous point (RP).
If no portion of this command is configured and if the ip msdp border sa-address command is configured, all local sources are advertised.
If the ip msdp redistribute command is configured with no keywords, no multicast sources are advertised.
Command Modes
Global configuration
Command History
Usage Guidelines
This command affects SA message origination, not SA message forwarding. If you want to filter which SA messages are forwarded to MSDP peers, use the ip msdp sa-filter in or ip msdp sa-filter out command.
The ip msdp redistribute command controls which (S, G) pairs the router advertises from the multicast routing table. By default, only sources within the local domain are advertised. Use the following guidelines for the ip msdp redistribute command:
•
•
•
•
•
Examples
The following example configures which (S, G) entries from the multicast routing table are advertised in SA messages originated to MSDP peers:
ip msdp redistribute route-map customer-sourcesroute-map customer-sources permitmatch as-path customer-asip as-path access-list ^109$Related Commands
ip as-path
Defines a BGP-related access list.
ip msdp border
Configures a router that borders a PIM sparse mode region and dense mode region to use MSDP.
ip msdp sa-filter in
To configure an incoming filter list for Source-Active (SA) messages received from the specified Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp sa-filter in command in global configuration mode. To remove the filter, use the no form of this command.
ip msdp sa-filter in {peer-address | peer-name} [list access-list] [route-map map-name]
no ip msdp sa-filter in {peer-address | peer-name} [list access-list] [route-map map-name]
Syntax Description
Defaults
If this command is not configured, no incoming messages are filtered; all SA messages are accepted from the peer.
If the command is configured, but no access list or route map is specified, all source/group pairs from the peer are filtered.
If both the list and the route-map keywords are used, all conditions must be true to pass any (S, G) pair in incoming SA messages.
Command Modes
Global configuration
Command History
Examples
The following example configures the router to filter all SA messages from the peer at 192.168.1.3:
ip msdp peer 192.168.1.3 connect-source Ethernet0/0ip msdp sa-filter in 192.168.1.3Related Commands
ip msdp peer
Configures an MSDP peer.
ip msdp sa-filter out
Configures an outgoing filter list for SA messages sent to the specified MSDP peer.
ip msdp sa-filter out
To configure an outgoing filter list for Source-Active (SA) messages sent to the specified Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp sa-filter out command in global configuration mode. To remove the filter, use the no form of this command.
ip msdp sa-filter out {peer-address | peer-name} [list access-list] [route-map map-name]
no ip msdp sa-filter out {peer-address | peer-name} [list access-list] [route-map map-name]
Syntax Description
Defaults
If this command is not configured, no outgoing messages are filtered; all SA messages received are forwarded to the peer.
If the command is configured, but no access list or route map is specified, all source/group pairs are filtered.
If both the list and the route-map keywords are used, all conditions must be true to pass any (S, G) pairs in outgoing SA messages.
Command Modes
Global configuration
Command History
Examples
The following example allows only (S, G) pairs that pass access list 100 to be forwarded in an SA message to the peer at the IP address 192.168.1.5:
ip msdp peer 192.168.1.5 connect-source ethernet 0/0ip msdp sa-filter out 192.168.1.5 list 100access-list 100 permit ip 172.1.0.0 0.0.255.255 224.2.0.0 0.0.255.255Related Commands
ip msdp peer
Configures an MSDP peer.
ip msdp sa-filter in
Configures an incoming filter list for SA messages received from the specified MSDP peer.
ip msdp sa-limit
To limit the number of Source-Active (SA) messages from a Multicast Source Discovery Protocol (MSDP) peer that the router will allow in the SA cache, use the ip msdp sa-limit command in global configuration mode. To remove this limit, use the no form of this command.
ip msdp sa-limit {peer-name | peer-address} sa-limit
no ip msdp sa-limit {peer-name | peer-address} sa-limit
Syntax Description
peer-name | peer-address
Domain Name System (DNS) name or IP address of the router that is to be the MSDP peer.
sa-limit
Maximum number of SA messages from an MSDP peer allowed in the SA cache.
Defaults
By default, no SA message limit is set.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to prevent distributed denial of service attacks. We recommend configuring this command on all MSDP peer connections.
The output of the show ip msdp count, show ip msdp peer, and show ip msdp summary commands will display the number of SA messages from each MSDP peer that is in the SA cache. If the ip msdp sa-limit command is configured, the output of the show ip msdp peer command will also display the value of the SA message limit for each MSDP peer.
Examples
The following example configures the SA message limit to 100 for the MSDP peer with IP address 172.16.10.2:
ip msdp sa-limit 172.16.10.2 100Related Commands
ip msdp sa-request
To configure the router to send Source-Active (SA) request messages to the Multicast Source Discovery Protocol (MSDP) peer when a new joiner from the group becomes active, use the ip msdp sa-request command in global configuration mode. To prevent this action, use the no form of this command.
ip msdp sa-request {peer-address | peer-name}
no ip msdp sa-request {peer-address | peer-name}
Syntax Description
peer-address | peer-name
IP address or name of the MSDP peer from which the local router requests SA messages when a new joiner for the group becomes active.
Defaults
The router does not send SA request messages to the MSDP peer.
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the router does not send any SA request messages to its MSDP peers when a new member joins a group and wants to receive multicast traffic. The new member waits to receive any SA messages that eventually arrive.
Use this command if you want a new member of a group to learn the current, active multicast sources in a connected Protocol Independent Multicast sparse mode (PIM-SM) domain that are sending to a group. The router will send SA request messages to the specified MSDP peer when a new member joins a group. The peer replies with the information in its SA cache. If the peer does not have a cache configured, this command provides nothing.
An alternative to this command is using the ip msdp cache-sa-state command to have the router cache messages.
Examples
The following example configures the router to send SA request messages to the MSDP peer at 172.16.10.2:
ip msdp sa-request 172.16.10.2Related Commands
ip msdp cache-sa-state
Enables the router to create SA state.
ip msdp peer
Configures an MSDP peer.
ip msdp shutdown
To administratively shut down a configured Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp shutdown command in global configuration mode. To bring the peer back up, use the no form of this command.
ip msdp shutdown {peer-address | peer-name}
no ip msdp shutdown {peer-address | peer-name}
Syntax Description
Defaults
No action is taken to shut down an MSDP peer.
Command Modes
Global configuration
Command History
Examples
The following example shuts down the MSDP peer at IP address 192.168.7.20:
ip msdp shutdown 192.168.7.20Related Commands
ip msdp timer
To adjust the interval at which Multicast Source Discovery Protocol (MSDP) peers will wait after peering sessions are reset before attempting to reestablish the peering sessions, use the ip msdp timer command in global configuration mode. To restore the default value, use the no form of this command.
ip msdp [vrf vrf-name] timer connection-retry-interval
no ip msdp [vrf vrf-name] timer
Syntax Description
Command Default
An MSDP peer will wait 30 seconds after a peering session is reset before attempting to reestablish the peering session with any peer.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip msdp timer command to adjust the interval at which all MSDP peers will wait after peering sessions are reset before attempting to reestablish the peering sessions. This interval is referred to as the connection-retry interval. By default, MSDP peers will wait 30 seconds after is session is reset before attempting to reestablish sessions with other peers. When the ip msdp timer command is configured, the configured connection-retry interval applies to all MSDP peering sessions on the router.
In network environments where fast recovery of Source-Active (SA) messages is required (such as in trading floor network environments), you may want to decrease the connection-retry interval to a time value less than the default value of 30 seconds.
Examples
The following example shows how to set the connection-retry interval for all MSDP peers to 20 seconds:
ip msdp timer 20Related Commands
ip msdp ttl-threshold
To limit which multicast data packets are sent in Source-Active (SA) messages to a Multicast Source Discovery Protocol (MSDP) peer, use the ip msdp ttl-threshold command in global configuration mode. To restore the default value, use the no form of this command.
ip msdp ttl-threshold {peer-address | peer-name} ttl-value
no ip msdp ttl-threshold {peer-address | peer-name}
Syntax Description
Defaults
ttl-value: 0
Command Modes
Global configuration
Command History
Usage Guidelines
This command limits which multicast data packets are sent in data-encapsulated SA messages. Only multicast packets with an IP header TTL greater than or equal to the ttl argument are sent to the MSDP peer specified by the IP address or name.
Use this command if you want to use TTL to scope your multicast data traffic. For example, you could limit internal traffic to a TTL of 8. If you want other groups to go to external locations, you would need to send those packets with a TTL greater than 8.
Examples
The following example configures a TTL threshold of 8 hops:
ip msdp ttl-threshold 192.168.1.5 8Related Commands
show ip msdp count
To display the number of sources and groups originated in Multicast Source Discovery Protocol (MSDP) Source-Active (SA) messages and the number of SA messages from an MSDP peer in the SA cache, use the show ip msdp count command in EXEC mode.
show ip msdp count [as-number]
Syntax Description
as-number
(Optional) Displays the number of sources and groups originated in SA messages from the specified autonomous system number.
Command Modes
EXEC
Command History
12.0(7)T
This command was introduced.
12.1(7)
This command was modified to display information about the number of SA messages from each MSDP peer in the SA cache.
Usage Guidelines
The ip msdp cache-sa-state command must be configured for this command to have any output.
Examples
The following is sample output of the show ip msdp count command:
Router# show ip msdp countSA State per Peer Counters, <Peer>: <# SA learned>192.135.250.116: 24144.228.240.253: 3964172.17.253.19: 10172.17.170.110: 11SA State per ASN Counters, <asn>: <# sources>/<# groups>Total entries: 4009?: 198/98, 9: 1/1, 14: 107/57, 17: 7/518: 4/3, 25: 23/17, 26: 39/27, 27: 2/232: 19/7, 38: 2/1, 52: 4/4, 57: 1/168: 4/4, 73: 12/8, 81: 19/1, 87: 9/6...Table 21 describes the significant fields shown in the display.
Related Commands
show ip msdp peer
To display detailed information about the Multicast Source Discovery Protocol (MSDP) peer, use the show ip msdp peer command in EXEC mode.
show ip msdp peer [peer-address | peer-name] [accepted-sas | advertised-sas]
Syntax Description
Command Modes
EXEC
Command History
12.0(7)T
This command was introduced.
12.1(7)
This command was modified to display information about the SA message limit configured using the the ip msdp sa-limit command.
Examples
The following is sample output of the show ip msdp peer command:
Router# show ip msdp peer 192.135.250.116MSDP Peer 192.135.250.116 (rtp5-rp1.cisco.com), AS 109 (configured AS)Description:Connection status:State: Up, Resets: 9, Connection source: Loopback2 (204.69.199.17)Uptime(Downtime): 1d10h, Messages sent/received: 436765/429062Output messages discarded: 0Connection and counters cleared 1w2d agoSA Filtering:Input (S,G) filter: none, route-map: noneInput RP filter: none, route-map: noneOutput (S,G) filter: none, route-map: noneOutput RP filter: none, route-map: noneSA-Requests:Input filter: noneSending SA-Requests to peer: disabledPeer ttl threshold: 0SAs learned from this peer: 32, SAs limit: 500Input queue size: 0, Output queue size: 0Table 22 describes the significant fields shown in the display.
Related Commands
show ip msdp sa-cache
To display the (S,G) state learned from Multicast Source Discovery Protocol (MSDP) peers, use the show ip msdp sa-cache command in user EXEC or privileged EXEC mode.
show ip msdp [vrf vrf-name] sa-cache [group-address | source-address | group-name | source-name] [group-address | source-address | group-name | source-name] [as-number] [rejected-sa [detail] [read-only]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
12.0(7)T
This command was introduced.
12.0(23)S
The vrf keyword and vrf-name argument were added.
12.2(13)T
The vrf keyword and vrf-name argument were added.
Usage Guidelines
By default, (S,G) state is cached.
Rejected SA messages are cached only if the ip msdp cache-rejected-sa command is configured.
Use the show ip msdp sa-cache with the optional rejected-sa keyword to display SA messages stored in the rejected SA cache. When the detail keyword is added to the command string, the output includes the IP address of the MSDP peer router that sent the SA message and the reason that the SA message was rejected.
When the optional read-only keyword is added to the command string, the router checkpoints the rejected SA cache, which ensures that a consistent snapshot of the rejected SA cache is displayed in the output. After being checkpointed, the rejected SA cache is cleared.
Note
When the optional read-only keyword is not added to the command string, the router displays rejected MSDP SA messages out of the active rejected SA cache, which could result in inconsistent display output if rejected SA message entries are overwritten by rejected SA message entries that are captured as the output is being processed for display.
Examples
The following is sample output from the show ip msdp sa-cache command:
Router# show ip msdp sa-cacheMSDP Source-Active Cache - 2398 entries(172.16.41.33, 238.105.148.0), RP 172.16.3.111, MBGP/AS 704, 2d10h/00:05:33(172.16.112.8, 224.2.0.1), RP 192.168.200.65, MBGP/AS 10888, 00:03:21/00:02:38(172.16.10.13, 227.37.32.1), RP 192.168.3.92, MBGP/AS 704, 05:22:20/00:03:32(172.16.66.18, 233.0.0.1), RP 192.168.3.111, MBGP/AS 704, 2d10h/00:05:35(172.16.66.148, 233.0.0.1), RP 192.168.3.111, MBGP/AS 704, 2d10h/00:05:35(172.16.10.13, 227.37.32.2), RP 192.168.3.92, MBGP/AS 704, 00:44:30/00:01:31(172.16.70.203, 224.2.236.2), RP 192.168.253.7, MBGP/AS 3582, 02:34:16/00:05:49(172.18.42.104, 236.195.56.2), RP 192.168.3.92, MBGP/AS 704, 04:21:13/00:05:22(172.16.10.13, 227.37.32.3), RP 192.168.3.92, MBGP/AS 704, 00:44:30/00:02:31(172.18.15.43, 224.0.92.3), RP 192.168.200.65, MBGP/AS 10888, 6d09h/00:05:35(172.18.15.111, 224.0.92.3), RP 192.168.200.65, MBGP/AS 10888, 16:18:08/00:05:35(172.18.21.45, 224.0.92.3), RP 192.168.200.65, MBGP/AS 10888, 16:18:08/00:05:35(172.18.15.75, 224.0.92.3), RP 192.168.200.65, MBGP/AS 10888, 08:40:52/00:05:35(172.18.15.100, 224.0.92.3), RP 192.168.200.65, MBGP/AS 10888, 08:40:52/00:05:35(172.16.10.13, 227.37.32.6), RP 192.168.3.92, MBGP/AS 704, 00:45:30/00:05:31(172.18.41.33, 224.247.228.10), RP 192.168.3.111, MBGP/AS 704, 2d10h/00:05:35(172.18.222.210, 224.2.224.13), RP 192.168.3.92, MBGP/AS 704, 01:51:53/00:05:22(172.18.41.33, 229.231.124.13), RP 192.168.3.111, MBGP/AS 704, 2d10h/00:05:33(172.18.32.138, 224.2.200.23), RP 192.168.253.7, MBGP/AS 3582, 21:33:40/00:05:49(172.18.75.244, 224.2.200.23), RP 192.168.253.7, MBGP/AS 3582, 21:33:40/00:05:49Table 23 describes the significant fields shown in the display.
The following is sample output from the show ip msdp sa-cache command with the rejected, detail, and read-only keywords specified:
Router# show ip msdp sa-cache rejected detail read-onlyMSDP Rejected SA Cache35 rejected SAs received over 02:50:01, cache size: 50 entriesTimestamp (source, group)2832.248, (10.10.10.4, 227.7.7.12), RP: 10.10.10.4, Peer: 10.10.10.4,Reason: sa-limit-exceeded2915.232, (10.10.10.8, 224.1.1.1), RP: 10.11.11.11, Peer: 10.10.10.8,Reason: in-filter3509.584, (10.12.12.2, 225.5.5.5), RP: 10.15.15.1, Peer: 10.12.12.2,Reason: rpf-fail...Table 24 describes the significant fields shown in the display.
Related Commands
clear ip msdp sa-cache
Clears MSDP SA cache entries.
ip msdp cache-sa-state
Enables the router to create SA state.
show ip msdp summary
To display Multicast Source Discovery Protocol (MSDP) peer status, use the show ip msdp summary command in EXEC mode.
show ip msdp summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
12.0(7)T
This command was introduced.
12.1(7)
This command was modified to display information about the number of SA messages from each MSDP peer in the SA cache.
Examples
The following is sample output of the show ip msdp summary command:
Router# show ip msdp summaryMSDP Peer Status SummaryPeer Address AS State Uptime/ Reset SA Peer NameDowntime Count Count192.135.250.116 109 Up 1d10h 9 111 rtp5-rp1*144.228.240.253 1239 Up 14:24:00 5 4010 sl-rp-stk172.17.253.19 109 Up 12:36:17 5 10 shinjuku-rp1172.17.170.110 109 Up 1d11h 9 12 ams-rp1Table 25 describes the significant fields shown in the display.
