Multicast VPN--IP Multicast Support for MPLS VPNs
Available Languages
Table Of Contents
Multicast VPN—IP Multicast Support for MPLS VPNs
Prerequisites for Multicast VPN—IP Multicast Support for MPLS VPNs
Restrictions for Multicast VPN—IP Multicast Support for MPLS VPNs
Information About Multicast VPN—IP Multicast Support for MPLS VPNs
IP Multicast Functionality for VRFs
IP Multicast VPN Routing and Forwarding and Multicast Domains
Multicast Distributed Switching Support
How to Configure Multicast VPN—IP Multicast Support for MPLS VPNs
Enabling a VPN for Multicast Routing
Fast Switching and IP Multicast
Sample Output for the show ip msdp peer Command
Sample Output for the show ip msdp summary Command
Sample Output for the show ip pim mdt bgp Command
Sample Output for the show ip pim mdt receive detail Command
Sample Output for the show ip pim mdt send Command
Sample Output for the show ip pim mdt history Command
Sample Output for the show ip mds mgid-table Command
Sample Output for the show ip hardware-mdfs mgid Command
Configuration Examples for Multicast VPN—IP Multicast Support for MPLS VPNs
Enabling a VPN for Multicast Routing: Example
Configuring the Multicast Group Address Range for Data MDT Groups: Example
Configuring the IP Source Address of Register Messages: Example
Storing IP Multicast Packet Headers: Example
Configuring an MSDP Peer: Example
Limiting the Number of Multicast Routes: Example
Multicast VPN—IP Multicast Support for MPLS VPNs
The Multicast VPN—IP Multicast Support for MPLS VPNs feature allows a service provider to configure and support multicast traffic in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) environment. This feature supports routing and forwarding of multicast packets for each individual VPN routing and forwarding (VRF) instance, and it also provides a mechanism to transport VPN multicast packets across the service provider backbone.
History for the Multicast VPN—IP Multicast Support for MPLS VPNs Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for Multicast VPN—IP Multicast Support for MPLS VPNs
•
•
•
•
Prerequisites for Multicast VPN—IP Multicast Support for MPLS VPNs
Service providers must have a multicast-enabled core in order to use the Cisco Multicast VPN feature. Refer to the "IP Multicast" part of the Cisco IOS IP Configuration Guide, Release 12.2 for more information.
Restrictions for Multicast VPN—IP Multicast Support for MPLS VPNs
•
•
•
•
•
•
•
•
•
•
Information About Multicast VPN—IP Multicast Support for MPLS VPNs
To configure the Multicast VPN—IP Multicast Support for MPLS VPNs feature, you must understand the following concepts:
•
•
•
•
IP Multicast VPNs
The Multicast VPN feature in Cisco IOS software provides the ability to support the multicast feature over a Layer 3 VPN. As enterprises extend the reach of their multicast applications, service providers can accommodate these enterprises over their MPLS core network. IP multicast is used to stream video, voice, and data to an MPLS VPN network core.
A VPN is network connectivity across a shared infrastructure, such as an Internet service provider (ISP). Its function is to provide the same policies and performance as a private network, at a reduced cost of ownership, thus creating many opportunities for cost savings through operations and infrastructure.
Historically, IP in IP generic routing encapsulation (GRE) tunnels was the only way to connect through a service provider network. Although such tunneled networks tend to have scalability issues, they represent the only means of passing IP multicast traffic through a VPN.
MPLS was derived from tag switching and various other vendor methods of IP-switching support enhancements in the scalability and performance of IP-routed networks by combining the intelligence of routing with the high performance of switching. MPLS is now used for VPNs, which is an appropriate combination because MPLS decouples information used for forwarding of the IP packet (the label) from the information carried in the IP header.
A Multicast VPN allows an enterprise to transparently interconnect its private network across the network backbone of a service provider. The use of a Multicast VPN to interconnect an enterprise network in this way does not change the way that enterprise network is administered, nor does it change general enterprise connectivity.
Because MPLS VPNs support only unicast traffic connectivity, deploying the Multicast VPN feature in conjunction with MPLS VPN allows service providers to offer both unicast and multicast connectivity to MPLS VPN customers.
Benefits of IP Multicast VPNs
•
•
•
IP Multicast Functionality for VRFs
IP multicast features are available for VRFs. These features have the same functionality as they do for non-VRF situations. Many command-line interface (CLI) commands have been enhanced through addition of the vrf vrf-name keyword and attribute to include support for VRFs.
Table 1 provides information about Cisco IOS commands that have been enhanced to provide functionality for VRFs. For additional configuration information about the commands described in Table 1, refer to the "Configuring IP Multicast Routing" chapter in the "IP Multicast" part in the Cisco IOS IP Configuration Guide, Release 12.2.
For more information about the following commands, see the "Command Reference" section.
Table 2 provides information about Cisco IOS commands that have been enhanced to provide functionality for VRFs. For additional configuration information about the commands described in Table 2 refer to the "Configuring Multicast Source Discovery Protocol" chapter in the "IP Multicast" part in the Cisco IOS IP Configuration Guide, Release 12.2.
For more information about the following commands, see the "Command Reference" section.
Table 3 provides information about Cisco IOS commands that have been enhanced to provide functionality for VRFs. For more information about the following commands see the "Command Reference" section.
Table 3 IP Multicast Functionality for VRFs—Other IP Multicast Configurations
ip mroute
Configures a multicast static route (mroute).
"Configuring an IP Multicast Static Route" section in "Configuring IP Multicast Routing" chapter.
ip pim accept-register
Configures a candidate RP router to filter PIM register messages.
ip pim ssm
Defines the SSM range of IP multicast addresses.
ip pim bidir-enable
Enables bidir-PIM.
"Configuring Bidirectional PIM" chapter
IP Multicast VPN Routing and Forwarding and Multicast Domains
Multicast VPN introduces multicast routing information to the VPN routing and forwarding table. When a PE router receives multicast data or control packets from a customer edge (CE) router, forwarding is performed according to the information in the Multicast VRF (MVRF).
A set of Multicast VPN Routing and Forwarding (VRF) instances that can send multicast traffic to each other constitutes a multicast domain. For example, the multicast domain for a customer that wanted to send certain types of multicast traffic to all global employees would consist of all CE routers associated with that enterprise.
Multicast Distribution Trees
Multicast VPN establishes a static default MDT for each multicast domain. The default MDT defines the path used by PE routers to send multicast data and control messages to every other PE router in the multicast domain.
Multicast VPN also supports the dynamic creation of MDTs for high-bandwidth transmission. Data MDTs are a feature unique to Cisco IOS software. Data MDTs are intended for high-bandwidth sources such as full-motion video inside the VPN to ensure optimal traffic forwarding in the MPLS VPN core. The threshold at which the data MDT is created can be configured on a per-router or a per-VRF basis. When the multicast transmission exceeds the defined threshold, the sending PE router creates the data MDT and sends a User Datagram Protocol (UDP) message that contains information about the data MDT to all routers in the default MDT. The statistics to determine whether a multicast stream has exceeded the data MDT threshold are examined once every 10 seconds. If multicast distributed switching is configured, the time period can be up to twice as long.
Data MDTs are created only for (S, G) multicast route entries within the VRF multicast routing table. They are not created for (*, G) entries regardless of the value of the individual source data rate.
In the following example, a service provider has a multicast customer with offices in San Jose, New York, and Dallas. A one-way multicast presentation is occurring in San Jose. The service provider network supports all three sites associated with this customer, in addition to the Houston site of a different enterprise customer.
The default MDT for the enterprise customer consists of provider routers P1, P2, and P3 and their associated PE routers. PE4 is not part of the default MDT, because it is associated with a different customer. Figure 1 shows that no data flows along the default MDT, because no one outside of San Jose has joined the multicast.
Figure 1 Default Multicast Distribution Tree Overview
An employee in New York joins the multicast session. The PE router associated with the New York site sends a join request that flows across the default MDT for the multicast domain of the customer whether it is configured to use Sparse Mode, Bidir or SSM within a VRF which contains both the Dallas and the San Jose sites. PE1, the PE router associated with the multicast session source, receives the request. Figure 2 depicts that the PE router forwards the request to the CE router associated with the multicast source (CE1a).
Figure 2 Initializing the Data MDT
The CE router (CE1a) begins to send the multicast data to the associated PE router (PE1), which sends the multicast data along the default MDT. Immediately after sending the multicast data, PE1 recognizes that the multicast data exceeds the bandwidth threshold at which a data MDT should be created. Therefore, PE1 creates a data MDT, sends a message to all routers using the default MDT that contains information about the data MDT, and, three seconds later, begins sending the multicast data for that particular stream using the data MDT. Only PE2 has interested receivers for this source, so only PE2 will join the data MDT and receive traffic on it.
PE routers maintain a PIM relationship with other PE routers over the default MDT, and a PIM relationship with its directly attached PE routers.
Figure 3 depicts the final flow of multicast data sourced from the multicast sender in San Jose to the multicast client in New York. Multicast data sent from the multicast sender in San Jose is delivered in its original format to its associated PE router (PE1) using sparse mode, bidir, or SSM. PE1 then encapsulates the multicast data and sends it across the data MDT using the configured MDT data groups. The mode used to deliver the multicast data across the data MDT is determined by the service provider and has no direct correlation with the mode used by the customer. The PE router in New York (PE2) receives the data along the data MDT. The PE2 router deencapsulates the packet and forwards it in its original format toward the multicast client using the mode configured by the customer.
Figure 3 Multicast Distribution Tree with VRFs
Multicast Tunnel Interface
For every multicast domain of which an MVRF is a part, the PE router creates a multicast tunnel interface. A multicast tunnel interface is an interface the MVRF uses to access the multicast domain. It can be thought of as a conduit that connects an MVRF and the global MVRF. One tunnel interface is created per multicast VRF.
Multicast Distributed Switching Support
Multicast distributed switching (MDS) is supported for Multicast VPN on the Cisco 7500 series, Cisco 10000 series, and Cisco 12000 series routers. When MDS is configured, ensure that all interfaces enabled for IP multicast have MDS enabled correctly—verify that no interface has the no ip mroute-cache command configured (including loopback interfaces).
Use the following commands to enable MDS for a particular VRF:
•
•
How to Configure Multicast VPN—IP Multicast Support for MPLS VPNs
This section contains the following procedures:
•
Enabling a VPN for Multicast Routing
This task enables a VPN for multicast routing.
PIM
PIM can operate in dense mode or sparse mode. It is possible for the router to handle both sparse groups and dense groups at the same time.
In dense mode, a router assumes that all other routers want to forward multicast packets for a group. If a router receives a multicast packet and has no directly connected members or PIM neighbors present, a prune message is sent back to the source. Subsequent multicast packets are not flooded to this router on this pruned branch. PIM builds source-based multicast distribution trees.
In sparse mode, a router assumes that other routers do not want to forward multicast packets for a group, unless there is an explicit request for the traffic. When hosts join a multicast group, the directly connected routers send PIM join messages toward the rendezvous point. The rendezvous point keeps track of multicast groups. Hosts that send multicast packets are registered with the rendezvous point by the first hop router of that host. Then the rendezvous point sends join messages toward the source. At this point, packets are forwarded on a shared distribution tree. If the multicast traffic from a specific source is sufficient, the first hop router of the host may send join messages toward the source to build a source-based distribution tree.
Fast Switching and IP Multicast
Fast switching of IP multicast packets is enabled by default on all interfaces (including GRE and Distance Vector Multicast Routing Protocol [DVMRP] tunnels), with one exception; it is disabled and not supported over X.25 encapsulated interfaces. Note the following properties of fast switching:
•
•
Disable fast switching if you want to log debug messages, because when fast switching is enabled, debug messages are not logged.
Note
Prerequisites
You must enable PIM sparse mode on the interface that is used for BGP peering. Configure PIM on all interfaces used for IP multicast. We recommend configuring PIM sparse mode on all physical interfaces of PE routers connecting to the backbone. We also recommend configuring PIM sparse mode on all loopback interfaces if they are used for BGP peering or if their IP address is used as an RP address for PIM.
In order to be able to use Auto-RP within a VRF, the interface facing the CE must be configured for PIM sparse-dense mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
or
ip pim sparse-dense-mode
6.
7.
8.
DETAILED STEPS
What to Do Next
Proceed to the "Configuring MDT " section.
Configuring MDT
This task configures MDT.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
What to Do Next
Proceed to the "Customizing IP Multicast VPN" section to configure additional, optional IP multicast VPN tasks. Proceed to the "Verifying IP Multicast VPN" section to verify the IP multicast VPN configuration.
Customizing IP Multicast VPN
This task configures additional, optional tasks for IP multicast VPN.
Register Messages
Register messages are unicast messages sent by the designated router (DR) to the rendezvous point router when a multicast packet needs to be sent on a rendezvous point tree (RPT). By default, the IP source address of the register message is set to the address of the outgoing interface of the DR leading toward the RP. To configure the IP source address of a register message to an interface address other than the outgoing interface address of the DR leading toward the RP, use the ip pim register-source command in global configuration mode. The optional vrf vrf-name keyword and argument combination has been added to the ip pim register-source command to define the VPN routing instance by assigning a VRF name.
IP Multicast Headers Storage
You can store IP multicast packet headers in a cache and then display them to determine any of the following information:
•
•
•
•
•
•
•
To allocate a circular buffer to store IP multicast packet headers that the router receives, use the ip multicast cache-headers command in global configuration mode.
Note
The optional vrf vrf-name keyword and argument combination has been added to the ip multicast cache-header command to define the VPN routing instance by assigning a VRF name.
MSDP Peers
MSDP is a mechanism to connect multiple PIM sparse mode (PIM-SM) domains. MSDP allows multicast sources for a group to be known to all RPs in different domains. Each PIM-SM domain uses its own RPs and need not depend on RPs in other domains. An RP runs MSDP over TCP to discover multicast sources in other domains.
An RP in a PIM-SM domain has an MSDP peering relationship with MSDP-enabled routers in another domain. The peering relationship occurs over a TCP connection, where primarily a list of sources sending to multicast groups is exchanged. The TCP connections between RPs are achieved by the underlying routing system. The receiving RP uses the source lists to establish a source path.
The purpose of this topology is to have domains discover multicast sources in other domains. If the multicast sources are of interest to a domain that has receivers, multicast data is delivered over the normal, source-tree building mechanism in PIM-SM.
MSDP is also used to announce sources sending to a group. These announcements must originate at the RP of the domain.
MSDP depends heavily on BGP or multiprotocol BGP (MBGP) for interdomain operation. We recommend that you run MSDP in RPs in your domain that are RPs for sources sending to global groups to be announced to the Internet.
For more information about configuring MSDP, refer to the section "Configuring Multicast Source Discover Protocol" in the "IP Multicast" part of the Cisco IOS IP Configuration Guide, Release 12.2.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying IP Multicast VPN" section.
Verifying IP Multicast VPN
The following task verifies the IP multicast VPN configuration, including information about the MSDP peer and MDT default and data groups.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Examples
This section provides the following output examples:
•
•
•
•
•
•
•
•
Sample Output for the show ip msdp peer Command
In the following example, detailed information about the MSDP peer for VRF v252 is displayed:
Router# show ip msdp vrf v252 peerMSDP Peer 10.109.3.1 (?), AS ?Description:Connection status:State:Up, Resets:0, Connection source:FastEthernet2/0.252(10.115.3.1)Uptime(Downtime):00:00:42, Messages sent/received:1/2Output messages discarded:0Connection and counters cleared 00:01:00 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:0Input queue size:0, Output queue size:0Sample Output for the show ip msdp summary Command
In the following example, summary information about the MSDP peer for VRF v252 is displayed:
Router# show ip msdp vrf v252 summaryMSDP Peer Status SummaryPeer Address AS State Uptime/ Reset SA Peer NameDowntime Count Count10.109.3.1 ? Up 00:01:38 0 0 ?Sample Output for the show ip pim mdt bgp Command
In the following example, information about the BGP advertisement of the route distinguisher (RD) for the MDT default group is displayed:
Router# show ip pim mdt bgpMDT-default group 232.2.1.4rid:1.1.1.1 next_hop:1.1.1.1Sample Output for the show ip pim mdt receive detail Command
In the following example, detailed information about the data MDT advertisements received by a specified router is displayed:
Router# show ip pim vrf vpn8 mdt receive detailJoined MDT-data groups for VRF:vpn8group:232.2.8.0 source:10.0.0.100 ref_count:13(10.101.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:26, OIF count:1, flags:TY(10.102.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:27, OIF count:1, flags:TYSample Output for the show ip pim mdt send Command
In the following example, the MDT advertisements that a specified router has made are displayed:
Router# show ip pim mdt sendMDT-data send list for VRF:vpn8(source, group) MDT-data group ref_count(10.100.8.10, 225.1.8.1) 232.2.8.0 1(10.100.8.10, 225.1.8.2) 232.2.8.1 1(10.100.8.10, 225.1.8.3) 232.2.8.2 1(10.100.8.10, 225.1.8.4) 232.2.8.3 1(10.100.8.10, 225.1.8.5) 232.2.8.4 1(10.100.8.10, 225.1.8.6) 232.2.8.5 1(10.100.8.10, 225.1.8.7) 232.2.8.6 1(10.100.8.10, 225.1.8.8) 232.2.8.7 1(10.100.8.10, 225.1.8.9) 232.2.8.8 1(10.100.8.10, 225.1.8.10) 232.2.8.9 1Sample Output for the show ip pim mdt history Command
In the following example, the data MDTs that have been reused during the past configured interval of 20 minutes are displayed:
Router# show ip pim vrf vrf1 mdt history interval 20MDT-data send history for VRF - vrf1 for the past 20 minutesMDT-data group Number of reuse10.9.9.8 310.9.9.9 2Sample Output for the show ip mds mgid-table Command
The following is sample output from the show ip mds mgid-table command executed on the line card in slot 2:
Router# execute-on slot 2 show ip mds mgid-table========= Line Card (Slot 2) =========MDFS MGID Table EntriesMGID ID VRFx VRF0 Encap String------- --- ---- ---- ------------0x0007C 1 Y N 45000001 00000000 FF2F0000 02020204 E8000001 000008000x0007D 1 Y N0x0007E 1 Y N0x00080 1 Y N 42424242 42424242 42424242 42424242 42424242 42424242Sample Output for the show ip hardware-mdfs mgid Command
The following is sample output from the show ip hardware-mdfs mgid command for a line card in slot 2:
Router# execute-on slot 2 show ip hardware-mdfs mgid 125 both-tables========= Line Card (Slot 2) =========0x7D:vrf tbl base=0x20030C00, vrfx=y vrf0=n0x7D:encap = 00066830000000007819A0C0000000000000007D00000002Configuration Examples for Multicast VPN—IP Multicast Support for MPLS VPNs
This section provides the following configuration examples:
•
•
•
•
•
•
Enabling a VPN for Multicast Routing: Example
In the following example, multicast routing is enabled for a VPN routing instance named vrf1. Ethernet interface 1/0/1 is configured for PIM sparse-dense mode and fast switching is explicitly enabled for Fast Ethernet interface 1/0/0.
ip multicast-routing vrf vrf1interface ethernet1/0/1ip pim sparse-dense-modeexitinterface fastethernet1/0/0
ip-mroute-cacheConfiguring the Multicast Group Address Range for Data MDT Groups: Example
In the following example, the VPN routing instance is assigned a VRF name of vrf1. The MDT default group for a VPN VRF is 239.1.1.1, and the multicast group address range for MDT groups is 239.1.2.0 with wildcard bits of 0.0.0.3:
ip vrf vrf1rd 55:1111route-target both 55:1111mdt default 239.1.1.1mdt data 239.1.2.0 0.0.0.3endRouter# show ip vrf vrf1Name Default RD Interfacesvrf1 55:1111Configuring the IP Source Address of Register Messages: Example
In the following example, the IP source address of the register message is configured to the Ethernet interface 1/0/0 of a DR:
ip pim register-source ethernet1/0/1Router# show running-config | include registerip pim register-source Ethernet1/0/1Storing IP Multicast Packet Headers: Example
In the following example, a circular buffer is allocated to store IP multicast packet headers that the router receives. The VPN routing instances in this example are named vrf1 and vrf2.
ip multicast vrf vrf1 cache-headersip multicast vrf vrf2 cache-headersRouter# show running-configBuilding configuration...Current configuration :3552 bytes!! Last configuration change at 16:52:30 UTC Fri May 31 2002!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryptionno service single-slot-reload-enable!hostname Router!...ip vrf vrf1rd 55:111route-target export 55:111route-target import 55:111mdt default 232.1.1.1!ip vrf vrf2rd 55:112route-target export 55:112route-target import 55:112mdt default 232.2.2.2!ip multicast-routing distributedip multicast-routing vrf vrf1 distributedip multicast-routing vrf vrf2 distributedip multicast vrf vrf1 cache-headersip multicast vrf vrf2 cache-headersip cef distributed...interface Ethernet 1/0/3.1encapsulation dot1Q 1 nativeip vrf forwarding vrf1ip address 20.1.1.1 255.255.255.0no ip redirectsno ip proxy-arpip pim sparse-dense-modeno keepaliveno cdp enable!interface Ethernet 1/0/3.2encapsulation dot1Q 2ip vrf forwarding vrf2ip address 20.1.1.2 255.255.255.0no ip redirectsno ip proxy-arpip pim sparse-dense-modeno keepaliveno cdp enable...address-family ipv4 vrf vrf2redistribute connectedredistribute staticredistribute rip metric 50no auto-summaryno synchronizationexit-address-family!address-family ipv4 vrf vrf1redistribute connectedredistribute staticredistribute rip metric 50no auto-summaryno synchronizationexit-address-family...endConfiguring an MSDP Peer: Example
In the following example, an MSDP peer is configured with a VPN routing instance named vrf1 and a source of 10.10.0.1 from Ethernet interface 1/0/1:
ip msdp vrf vrf1 peer 10.10.0.1 connect-source ethernet 1/0/1Limiting the Number of Multicast Routes: Example
In the following example, the number of multicast routes that can be added in to a multicast routing table is set to 200,000 and the threshold value of the number of mroutes that will cause a warning message to occur is set to 20,000:
Router# show running-configip multicast-routing distributedip multicast-routing vrf cisco distributedip multicast cache-headersip multicast route-limit 200000 20000ip multicast vrf cisco route-limit 200000 20000no mpls traffic-eng auto-bw timers frequency 0!.Where to Go Next
If you want to configure other IP multicast features for a VRF, see the "IP Multicast Functionality for VRFs" section for more information.
Additional References
The following sections provide references related to the Multicast VPN—IP Multicast Support for MPLS VPNs feature.
Related Documents
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2T command reference publications.
clear ip igmp group
To delete entries from the Internet Group Management Protocol (IGMP) cache, use the clear ip igmp group command in privileged EXEC mode.
clear ip igmp [vrf vrf-name] group [group-name | group-address | interface-type interface-number]
Syntax Description
Defaults
When this command is used with no arguments, all entries are deleted from the IGMP cache.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The IGMP cache contains a list of the multicast groups of which hosts on the directly connected LAN are members. If the router has joined a group, that group is also listed in the cache.
To delete all entries from the IGMP cache, specify the clear ip igmp group command with no arguments.
Examples
The following example clears entries for the multicast group 224.0.255.1 from the IGMP cache:
Router# clear ip igmp group 224.0.255.1Related Commands
clear ip mroute
To delete entries from the IP multicast routing table, use the clear ip mroute command in privileged EXEC mode.
clear ip mroute [vrf vrf-name] {* | group} [source]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example deletes all entries from the IP multicast routing table:
Router# clear ip mroute *The following example deletes from the IP multicast routing table all sources on the 228.3.0.0 subnet that are sending to the multicast group 224.2.205.42. Note that this example deletes all sources on network 228.3, not individual sources.
Router# clear ip mroute 224.2.205.42 228.3.0.0Related Commands
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 privileged EXEC mode.
clear ip msdp [vrf vrf-name] peer {peer-address | peer-name}
Syntax Description
Command Modes
Privileged 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 224.15.9.8:
Router# clear ip msdp peer 224.15.9.8Related 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 privileged EXEC mode.
clear ip msdp [vrf vrf-name] sa-cache [group-address | group-name]
Syntax Description
Command Modes
Privileged 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 224.5.6.7 from the cache:
Router# clear ip msdp sa-cache 224.5.6.7Related 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 privileged EXEC mode.
clear ip msdp [vrf vrf-name] statistics [peer-address | peer-name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the counters for the peer named peer1:
Router# clear ip msdp statistics peer1clear ip pim auto-rp
To delete entries from the Auto-RP cache, use the clear ip pim auto-rp command in privileged EXEC mode.
clear ip pim [vrf vrf-name] auto-rp rp-address
Syntax Description
Command Modes
Privileged EXEC
Command History
11.3
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.
Examples
The following example deletes all entries from the Auto-RP cache:
Router# clear ip pim auto-rp 224.5.6.7debug ip igmp
To display Internet Group Management Protocol (IGMP) packets received and sent, and IGMP-host related events, use the debug ip igmp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip igmp [vrf vrf-name] [group-address]
no debug ip igmp [vrf vrf-name] [group-address]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command helps discover whether the IGMP processes are functioning. In general, if IGMP is not working, the router process never discovers that another host is on the network that is configured to receive multicast packets. In dense mode, this situation will result in packets being delivered intermittently (a few every 3 minutes). In sparse mode, packets will never be delivered.
Use this command in conjunction with the debug ip pim and debug ip mrouting commands to observe additional multicast activity and to learn the status of the multicast routing process, or why packets are forwarded out of particular interfaces.
When SSM mapping is enabled, a debug message is displayed to indicate that the router is converting an IGMP version 2 report from the group (G) into an IGMP version 3 join. After SSM mapping has generated the appropriate IGMP version 3 report, any debug output that follows is seen as if the router had received the same IGMP version 3 report directly.
Examples
The following is sample output from the debug ip igmp command:
Router# debug ip igmpIGMP: Received Host-Query from 172.16.37.33 (Ethernet1)IGMP: Received Host-Report from 172.16.37.192 (Ethernet1) for 224.0.255.1IGMP: Received Host-Report from 172.16.37.57 (Ethernet1) for 224.2.127.255IGMP: Received Host-Report from 172.16.37.33 (Ethernet1) for 225.2.2.2The messages displayed by the debug ip igmp command show query and report activity received from other routers and multicast group addresses.
The following is sample output from the debug ip igmp command when SSM is enabled. Because IGMP version 3 lite (IGMP v3lite) requires the host to send IGMP version 2 (IGMPv2) packets, IGMPv2 host reports also will be displayed in response to the router IGMPv2 queries. If SSM is disabled, the word "ignored" will be displayed in the debug ip igmp command output.
IGMP:Received v3-lite Report from 10.0.119.142 (Ethernet3/3), group count 1IGMP:Received v3 Group Record from 10.0.119.142 (Ethernet3/3) for 232.10.10.10IGMP:Update source 224.1.1.1IGMP:Send v2 Query on Ethernet3/3 to 224.0.0.1IGMP:Received v2 Report from 10.0.119.142 (Ethernet3/3) for 232.10.10.10IGMP:Update source 224.1.1.1The following is sample output from the debug ip igmp command when SSM static mapping is enabled. The following output indicates that the router is converting an IGMP version 2 join for group (G) into an IGMP version 3 join:
IGMP(0): Convert IGMPv2 report (*,232.1.2.3) to IGMPv3 with 2 source(s) using STATIC.The following is sample output from the debug ip igmp command when SSM DNS-based mapping is enabled. The following output indicates that a DNS lookup has succeeded:
IGMP(0): Convert IGMPv2 report (*,232.1.2.3) to IGMPv3 with 2 source(s) using DNS.The following is sample output from the debug ip igmp command when SSM DNS-based mapping is enabled and a DNS lookup has failed:
IGMP(0): DNS source lookup failed for (*, 232.1.2.3), IGMPv2 report failedRelated Commands
debug ip mcache
To display IP multicast fast-switching events, use the debug ip mcache command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip mcache [vrf vrf-name] [hostname | group-address]
no debug ip mcache [vrf vrf-name] [hostname | group-address]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when multicast fast switching appears not to be functioning.
Examples
The following is sample output from the debug ip mcache command when an IP multicast route is cleared:
Router# debug ip mcacheIP multicast fast-switching debugging is onRouter# clear ip mroute *MRC: Build MAC header for (172.31.60.185/32, 224.2.231.173), Ethernet0MRC: Fast-switch flag for (172.31.60.185/32, 224.2.231.173), off -> on, caller ip_mroute_replicate-1MRC: Build MAC header for (172.31.191.10/32, 224.2.127.255), Ethernet0MRC: Build MAC header for (172.31.60.152/32, 224.2.231.173), Ethernet0Table 8 describes the significant fields shown in the display.
Related Commands
debug ip mpacket
To display IP multicast packets received and sent, use the debug ip mpacket command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip mpacket [vrf vrf-name] [detail | fastswitch] [access-list] [group]
no debug ip mpacket [vrf vrf-name] [detail | fastswitch] [access-list] [group]
Syntax Description
Defaults
The debug ip mpacket command displays all IP multicast packets switched at the process level.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays information for multicast IP packets that are forwarded from this router. Use the access-list or group argument to limit the display to multicast packets from sources described by the access list or a specific multicast group.
Use this command with the debug ip packet command to display additional packet information.
Note
Examples
The following is sample output from the debug ip mpacket command:
Router# debug ip mpacket 224.2.0.1IP: s=10.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforwardIP: s=10.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforwardIP: s=10.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforwardIP: s=10.162.3.27 (Ethernet1), d=224.2.0.1 (Tunnel0), len 68, mforwardTable 5 describes the significant fields shown in the display.
Related Commands
debug ip mrouting
To display changes to the multicast route (mroute) table, use the debug ip mrouting command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip mrouting [vrf vrf-name] [rpf-events] [group]
no debug ip mrouting [vrf vrf-name] [rpf-events] [group]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command indicates when the router has made changes to the mroute table. Use the debug ip pim and debug ip mrouting commands consecutively to obtain additional multicast routing information. In addition, use the debug ip igmp command to learn why an mroute message is being displayed.
This command generates a substantial amount of output. Use the optional group argument to limit the output to a single multicast group.
Examples
The following is sample output from the debug ip mrouting command:
Router# debug ip mrouting 224.2.0.1MRT: Delete (10.0.0.0/8, 224.2.0.1)MRT: Delete (10.4.0.0/16, 224.2.0.1)MRT: Delete (10.6.0.0/16, 224.2.0.1)MRT: Delete (10.9.0.0/16, 224.2.0.1)MRT: Delete (10.16.0.0/16, 224.2.0.1)MRT: Create (*, 224.2.0.1), if_input NULLMRT: Create (224.69.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 224.69.61.15MRT: Create (224.69.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 0.0.0.0MRT: Create (10.0.0.0/8, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.4.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.6.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0The following lines show that multicast IP routes were deleted from the routing table:
MRT: Delete (10.0.0.0/8, 224.2.0.1)MRT: Delete (10.4.0.0/16, 224.2.0.1)MRT: Delete (10.6.0.0/16, 224.2.0.1)The (*, G) entries are generally created by receipt of an Internet Group Management Protocol (IGMP) host report from a group member on the directly connected LAN or by a Protocol Independent Multicast (PIM) join message (in sparse mode) that this router receives from a router that is sending joins toward the RP. This router will in turn send a join toward the Route Processor (RP) that creates the shared tree (or RP tree).
MRT: Create (*, 224.2.0.1), if_input NULLThe following lines are an example of creating an (S, G) entry that shows that an IP multicast packet (mpacket) was received on Ethernet interface 0. The second line shows a route being created for a source that is on a directly connected LAN. The RPF means "Reverse Path Forwarding," whereby the router looks up the source address of the multicast packet in the unicast routing table and determines which interface will be used to send a packet to that source.
MRT: Create (224.69.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 224.69.61.15MRT: Create (224.69.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 224.0.0.0The following lines show that multicast IP routes were added to the routing table. Note the 224.0.0.0 as the RPF, which means the route was created by a source that is directly connected to this router.
MRT: Create (10.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0If the source is not directly connected, the neighbor address shown in these lines will be the address of the router that forwarded the packet to this router.
The shortest path tree state maintained in routers consists of source (S), multicast address (G), outgoing interface (OIF), and incoming interface (IIF). The forwarding information is referred to as the multicast forwarding entry for (S, G).
An entry for a shared tree can match packets from any source for its associated group if the packets come through the proper incoming interface as determined by the RPF lookup. Such an entry is denoted as
(*, G). A (*, G) entry keeps the same information a (S, G) entry keeps, except that it saves the rendezvous point address in place of the source address in sparse mode or as 24.0.0.0 in dense mode.Table 6 describes the significant fields shown in the display.
Table 6 debug ip mrouting Field Descriptions
MRT
Multicast route table.
RPF
Reverse Path Forwarding.
nbr
Neighbor.
Related Commands
debug ip msdp
To debug Multicast Source Discovery Protocol (MSDP) activity, use the debug ip msdp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip msdp [vrf vrf-name] [peer-address | name] [detail] [routes]
no debug ip msdp [vrf vrf-name] [peer-address | name] [detail] [routes]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug ip msdp command:
Router# debug ip msdpMSDP debugging is onRouter#MSDP: 224.150.44.254: Received 1388-byte message from peerMSDP: 224.150.44.254: SA TLV, len: 1388, ec: 115, RP: 172.31.3.92MSDP: 224.150.44.254: Peer RPF check passed for 172.31.3.92, used EMBGP peerMSDP: 224.150.44.250: Forward 1388-byte SA to peerMSDP: 224.150.44.254: Received 1028-byte message from peerMSDP: 224.150.44.254: SA TLV, len: 1028, ec: 85, RP: 172.31.3.92MSDP: 224.150.44.254: Peer RPF check passed for 172.31.3.92, used EMBGP peerMSDP: 224.150.44.250: Forward 1028-byte SA to peerMSDP: 224.150.44.254: Received 1388-byte message from peerMSDP: 224.150.44.254: SA TLV, len: 1388, ec: 115, RP: 172.31.3.111MSDP: 224.150.44.254: Peer RPF check passed for 172.31.3.111, used EMBGP peerMSDP: 224.150.44.250: Forward 1388-byte SA to peerMSDP: 224.150.44.250: Received 56-byte message from peerMSDP: 224.150.44.250: SA TLV, len: 56, ec: 4, RP: 205.167.76.241MSDP: 224.150.44.250: Peer RPF check passed for 205.167.76.241, used EMBGP peerMSDP: 224.150.44.254: Forward 56-byte SA to peerMSDP: 224.150.44.254: Received 116-byte message from peerMSDP: 224.150.44.254: SA TLV, len: 116, ec: 9, RP: 172.31.3.111MSDP: 224.150.44.254: Peer RPF check passed for 172.31.3.111, used EMBGP peerMSDP: 224.150.44.250: Forward 116-byte SA to peerMSDP: 224.150.44.254: Received 32-byte message from peerMSDP: 224.150.44.254: SA TLV, len: 32, ec: 2, RP: 172.31.3.78MSDP: 224.150.44.254: Peer RPF check passed for 172.31.3.78, used EMBGP peerMSDP: 224.150.44.250: Forward 32-byte SA to peerTable 7 describes the significant fields shown in the display.
Table 7 debug ip msdp Field Descriptions
MSDP
Protocol being debugged.
224.150.44.254:
IP address of the MSDP peer.
Received 1388-byte message from peer
MSDP event.
debug ip msdp resets
To debug Multicast Source Discovery Protocol (MSDP) peer reset reasons, use the debug ip msdp resets command in privileged EXEC mode.
debug ip msdp [vrf vrf-name] resets
Syntax Description
vrf
(Optional) Supports the Multicast Virtual Private Network (VPN) routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
debug ip pim
To display Protocol Independent Multicast (PIM) packets received and sent, and to display PIM-related events, use the debug ip pim command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip pim [vrf vrf-name] [group | df [rp-address]] [hello]
no debug ip pim [vrf vrf-name] [group | df [rp-address]] [hello]
Syntax Description
Defaults
All PIM packets are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
PIM uses Internet Group Management Protocol (IGMP) packets to communicate with routers and advertise reachability information.
Use this command with the debug ip igmp and debug ip mrouting commands to display additional multicast routing information.
Examples
The following is sample output from the debug ip pim command:
Router# debug ip pim 224.2.0.1PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received RP-Reachable on Ethernet1 from 172.16.20.31PIM: Update RP expiration timer for 224.2.0.1PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Prune-list (10.221.196.51/32, 224.2.0.1)PIM: Set join delay timer to 2 seconds for (10.221.0.0/16, 224.2.0.1) on Ethernet1PIM: Received Join/Prune on Ethernet1 from 172.16.37.6PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Join-list: (*, 224.2.0.1) RP 172.16.20.31PIM: Add Tunnel0 to (*, 224.2.0.1), Forward statePIM: Join-list: (10.0.0.0/8, 224.2.0.1)PIM: Add Tunnel0 to (10.0.0.0/8, 224.2.0.1), Forward statePIM: Join-list: (10.4.0.0/16, 224.2.0.1)PIM: Prune-list (172.16.84.16/28, 224.2.0.1) RP-bit set RP 172.16.84.16PIM: Send Prune on Ethernet1 to 172.16.37.6 for (172.16.84.16/28, 224.2.0.1), RPPIM: For RP, Prune-list: 10.9.0.0/16PIM: For RP, Prune-list: 10.16.0.0/16PIM: For RP, Prune-list: 10.49.0.0/16PIM: For RP, Prune-list: 10.84.0.0/16PIM: For RP, Prune-list: 10.146.0.0/16PIM: For 10.3.84.1, Join-list: 172.16.84.16/28PIM: Send periodic Join/Prune to RP via 172.16.37.6 (Ethernet1)The following lines appear periodically when PIM is running in sparse mode and indicate to this router the multicast groups and multicast sources in which other routers are interested:
PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33The following lines appear when a rendezvous point (RP) message is received and the RP timer is reset. The expiration timer sets a checkpoint to make sure the RP still exists. Otherwise, a new RP must be discovered.
PIM: Received RP-Reachable on Ethernet1 from 172.16.20.31PIM: Update RP expiration timer for 224.2.0.1PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0The prune message in the following line states that this router is not interested in the Source-Active (SA) information. This message tells an upstream router to stop forwarding multicast packets from this source.
PIM: Prune-list (10.221.196.51/32, 224.2.0.1)In the following line, a second router on the network wants to override the prune message that the upstream router just received. The timer is set at a random value so that if additional routers on the network still want to receive multicast packets for the group, only one will actually send the message. The other routers will receive the join message and then suppress sending their own message.
PIM: Set join delay timer to 2 seconds for (10.221.0.0/16, 224.2.0.1) on Ethernet1In the following line, a join message is sent toward the RP for all sources:
PIM: Join-list: (*, 224.2.0.1) RP 172.16.20.31In the following lines, the interface is being added to the outgoing interface (OIF) of the (*, G) and
(S, G) multicast route (mroute) table entry so that packets from the source will be forwarded out that particular interface:PIM: Add Tunnel0 to (*, 224.2.0.1), Forward statePIM: Add Tunnel0 to (10.0.0.0/8, 224.2.0.1), Forward stateThe following line appears in sparse mode only. There are two trees on which data may be received: the RP tree and the source tree. In dense mode there is no RP. After the source and the receiver have discovered one another at the RP, the first-hop router for the receiver will usually join to the source tree rather than the RP tree.
PIM: Prune-list (172.16.84.16/28, 224.2.0.1) RP-bit set RP 172.16.84.16The send prune message in the next line shows that a router is sending a message to a second router saying that the first router should no longer receive multicast packets for the (S, G). The RP at the end of the message indicates that the router is pruning the RP tree and is most likely joining the source tree, although the router may not have downstream members for the group or downstream routers with members of the group. The output shows the specific sources from which this router no longer wants to receive multicast messages.
PIM: Send Prune on Ethernet1 to 172.16.37.6 for (172.16.84.16/28, 224.2.0.1), RPThe following lines indicate that a prune message is sent toward the RP so that the router can join the source tree rather than the RP tree:
PIM: For RP, Prune-list: 10.9.0.0/16PIM: For RP, Prune-list: 10.16.0.0/16PIM: For RP, Prune-list: 10.49.0.0/16In the following line, a periodic message is sent toward the RP. The default period is once per minute. Prune and join messages are sent toward the RP or source rather than directly to the RP or source. It is the responsibility of the next hop router to take proper action with this message, such as continuing to forward it to the next router in the tree.
PIM: Send periodic Join/Prune to RP via 172.16.37.6 (Ethernet1)Table 8 describes the significant fields shown in the display.
Table 8 debug ip pim Field Descriptions
PIM
Protocol Independent Multicast.
10.221.196.51/32
Host route with 32 bits of mask.
Related Commands
debug ip pim auto-rp
To display the contents of each Protocol Independent Multicast (PIM) packet used in the automatic discovery of group-to-rendezvous point (RP) mapping and the actions taken on the address-to-RP mapping database, use the debug ip pim auto-rp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip pim auto-rp [vrf vrf-name]
no debug ip pim auto-rp [vrf vrf-name]
Syntax Description
vrf
(Optional) Supports the Multicast Virtual Private Network (VPN) routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug ip pim auto-rp command:
Router# debug ip pim auto-rpAuto-RP: Received RP-announce, from 172.16.214.66, RP_cnt 1, holdtime 180 secsAuto-RP: update (192.168.248.0/24, RP:172.16.214.66)Auto-RP: Build RP-Discovery packetAuto-RP: Build mapping (192.168.248.0/24, RP:172.16.214.66),Auto-RP: Build mapping (192.168.250.0/24, RP:172.16.214.26).Auto-RP: Build mapping (192.168.254.0/24, RP:172.16.214.2).Auto-RP: Send RP-discovery packet (3 RP entries)Auto-RP: Build RP-Announce packet for 172.16.214.2Auto-RP: Build announce entry for (192.168.254.0/24)Auto-RP: Send RP-Announce packet, IP source 172.16.214.2, ttl 8The first two lines show a packet received from 172.16.214.66 announcing that it is the RP for the groups in 192.168.248.0/24. This announcement contains one RP address and is valid for 180 seconds. The RP-mapping agent then updates its mapping database to include the new information.
Auto-RP: Received RP-announce, from 172.16.214.66, RP_cnt 1, holdtime 180 secsAuto-RP: update (192.168.248.0/24, RP:172.16.214.66)In the next five lines, the router creates an RP-discovery packet containing three RP mapping entries. The packet is sent to the well-known CISCO-RP-DISCOVERY group address (224.0.1.40).
Auto-RP: Build RP-Discovery packetAuto-RP: Build mapping (192.168.248.0/24, RP:172.16.214.66),Auto-RP: Build mapping (192.168.250.0/24, RP:172.16.214.26).Auto-RP: Build mapping (192.168.254.0/24, RP:172.16.214.2).Auto-RP: Send RP-discovery packet (3 RP entries)The final three lines show the router announcing that it intends to be an RP for the groups in 192.168.254.0/24. Only routers inside the scope "ttl 8" receive the advertisement and use the RP for these groups.
Auto-RP: Build RP-Announce packet for 172.16.214.2Auto-RP: Build announce entry for (192.168.254.0/24)Auto-RP: Send RP-Announce packet, IP source 172.16.214.2, ttl 8The following is sample output from the debug ip pim auto-rp command when a router receives an update. In this example, the packet contains three group-to-RP mappings, which are valid for 180 seconds. The RP-mapping agent then updates its mapping database to include the new information.
Router# debug ip pim auto-rpAuto-RP: Received RP-discovery, from 172.16.214.17, RP_cnt 3, holdtime 180 secsAuto-RP: update (192.168.248.0/24, RP:172.16.214.66)Auto-RP: update (192.168.250.0/24, RP:172.16.214.26)Auto-RP: update (192.168.254.0/24, RP:172.16.214.2)ip mroute
To configure a multicast static route (mroute), use the ip mroute command in global configuration mode. To remove the route, use the no form of this command.
ip mroute [vrf vrf-name] source-address mask [protocol as-number] {rpf-address | interface-type interface-number} [distance]
no ip mroute [vrf vrf-name] source-address mask [protocol as-number] {rpf-address | interface-type interface-number} [distance]
Syntax Description
Defaults
distance: 0
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows you to statically configure where multicast sources are located (even though the unicast routing table shows something different).
When a source range is specified, the rpf-address argument applies only to those sources.
Examples
The following example configures all sources via a single interface (in this case, a tunnel):
ip mroute 224.0.0.0 255.255.255.255 tunnel0The following example configures all specific sources within a network number to be reachable through 172.30.10.13:
ip mroute 172.16.0.0 255.255.0.0 172.30.10.13The following example causes this multicast static route to take effect if the unicast routes for any given destination go away:
ip mroute 224.0.0.0 255.255.255.255 serial0 200ip 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 [vrf vrf-name] border sa-address interface-type interface-number
no ip msdp [vrf vrf-name] border sa-address interface-type interface-number
Syntax Description
Defaults
The active sources in the dense mode region will not participate in MSDP.
Command Modes
Global configuration
Command 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
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
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-sa-state
To have the router create the 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. For more MSDP configuration examples, refer to the "Configuring Multicast Source Discovery Protocol" chapter in the Cisco IOS IP Configuration Guide.
...ip classlessip msdp peer 224.168.1.2 connect-source Loopback0ip msdp peer 224.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 [vrf vrf-name] default-peer {peer-address | peer-name} [prefix-list list]
no ip msdp [vrf vrf-name] 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) specified 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 named router.cisco.com as the default peer to the local router:
ip msdp peer 224.12.2.3ip msdp peer 224.13.4.5ip msdp default-peer router.cisco.com !At a stub siteThe following example configures two default peers:
ip msdp peer 224.12.2.3ip msdp peer 224.13.4.5ip msdp default-peer 224.12.2.3 prefix-list site-cip prefix-list site-a permit 224.12.0.0/16ip msdp default-peer 224.13.4.5 prefix-list site-aip prefix-list site-a permit 224.13.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 [vrf vrf-name] description {peer-name | peer-address} text
no ip msdp [vrf vrf-name] description {peer-name | peer-address}
Syntax Description
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 displayed in the output of the show ip msdp peer command.
Examples
The following example configures the router at the IP address 224.107.5.4 with a description indicating it is a router at customer A:
ip msdp description 224.107.5.4 router at customer aRelated Commands
ip 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 [vrf vrf-name] filter-sa-request {peer-address | peer-name} [list access-list]
no ip msdp [vrf vrf-name] 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 224.69.2.2 list 1access-list 1 permit 228.4.22.0 0.0.0.255Related 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 [vrf vrf-name] mesh-group mesh-name {peer-address | peer-name}
no ip msdp [vrf vrf-name] mesh-group mesh-name {peer-address | peer-name}
Syntax Description
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 224.1.1.1 to be a member of the mesh group named internal:
ip msdp mesh-group internal 224.1.1.1ip 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 [vrf vrf-name] originator-id interface-type interface-number
no ip msdp [vrf vrf-name] originator-id interface-type interface-number
Syntax Description
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 sa-address and ip msdp originator-id commands are configured 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 [vrf vrf-name] peer {peer-name | peer-address} [connect-source interface-type interface-number] [remote-as as-number]
no ip msdp [vrf vrf-name] 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 224.108.1.2 as an MSDP peer to the local router. The neighbor belongs to autonomous system 109.
ip msdp peer 224.108.1.2 connect-source ethernet 0router bgp 110network 224.108.0.0neighbor 224.108.1.2 remote-as 109neighbor 224.108.1.2 update-source ethernet 0The following example configures the router named router.cisco.com as an MSDP peer to the local router:
ip msdp peer router.cisco.comThe following example configures the router named router.cisco.com to be an MSDP peer in autonomous system 109. The primary address of Ethernet interface 0 is used as the source address for the TCP connection.
ip msdp peer router.cisco.com connect-source ethernet0 remote-as 109Related Commands
ip msdp default-peer
Defines a default peer from which to accept all MSDP SA messages.
neighbor remote-as
Adds an entry to the BGP neighbor table.
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 [vrf vrf-name] redistribute [list access-list-name] [asn as-access-list-number] [route-map map-name]
no ip msdp [vrf vrf-name] 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 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 [vrf vrf-name] sa-filter in {peer-address | peer-name} [list access-list-name] [route-map map-name]
no ip msdp [vrf vrf-name] sa-filter in {peer-address | peer-name} [list access-list-name] [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 route-map keywords are used, all conditions specified by these keywords 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 named router.cisco.com:
ip msdp peer router.cisco.com connect-source ethernet 0ip msdp sa-filter in router.cisco.comRelated 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 [vrf vrf-name] sa-filter out {peer-address | peer-name} [list access-list-name] [route-map map-name]
no ip msdp [vrf vrf-name] sa-filter out {peer-address | peer-name} [list access-list-name] [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 route-map keywords are used, all conditions specified by these keywords 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 named router.cisco.com:
ip msdp peer router.cisco.com connect-source ethernet 0ip msdp sa-filter out router.cisco.com list 100access-list 100 permit ip 224.69.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-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 [vrf vrf-name] sa-request {peer-address | peer-name}
no ip msdp [vrf vrf-name] sa-request {peer-address | peer-name}
Syntax Description
Defaults
The router does not send SA request messages to the MSDP peer.
Command Modes
Global configuration
Command 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, 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 224.69.1.1:
ip msdp sa-request 224.69.1.1Related 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 [vrf vrf-name] shutdown {peer-address | peer-name}
no ip msdp [vrf vrf-name] 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 224.5.7.20:
ip msdp shutdown 224.5.7.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 [vrf vrf-name] ttl-threshold {peer-address | peer-name} ttl-value
no ip msdp [vrf vrf-name] 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-value 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 224.5.7.20 8Related Commands
ip multicast cache-headers
To allocate a circular buffer to store IP multicast packet headers that the router receives, use the ip multicast cache-headers command in global configuration mode. To remove the buffer, use the no form of this command.
ip multicast [vrf vrf-name] cache-headers [rtp]
no ip multicast [vrf vrf-name] cache-headers [rtp]
Syntax Description
Defaults
The command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You can store IP multicast packet headers in a cache and then display them to determine the following information:
•
•
•
•
•
•
•
Note
Use the show ip mpacket command to display the buffer.
Examples
The following example allocates a buffer to store IP multicast packet headers:
ip multicast cache-headersRelated Commands
ip multicast mrinfo-filter
To filter multicast router information (mrinfo) request packets, use the ip multicast mrinfo-filter command in global configuration mode. To remove the filter on mrinfo requests, use the no form of this command.
ip multicast mrinfo-filter access-list
no ip multicast mrinfo-filter access-list
Syntax Description
access-list
IP standard numbered or named access list that determines which networks or hosts can query the local multicast router with the mrinfo command.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The ip multicast mrinfo-filter command filters the mrinfo request packets from all of the sources permitted by the specified access list. That is, if the access list permits a source, that source's mrinfo requests are filtered. For all sources that the access list explicitly or implicitly denies, the mrinfo requests are allowed to proceed.
Examples
The following example specifies that mrinfo request packets from all hosts on network 192.178.1.0 are not allowed to be processed the router:
ip multicast mrinfo-filter 4access-list 4 permit 192.178.1.0 0.0.0.255Related Commands
mrinfo
Queries a multicast router about which neighboring multicast routers are peering with it.
ip multicast multipath
To enable load splitting of IP multicast traffic across multiple equal-cost paths, use the ip multicast multipath command in global configuration mode. To disable this configuration, use the no form of this command.
ip multicast [vrf vrf-name] multipath
no ip multicast [vrf vrf-name] multipath
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
By default, if multiple equal-cost paths exist, multicast traffic will not be load split across these paths.
Command Modes
Global configuration
Command History
Usage Guidelines
If the ip multicast multipath command is configured and multiple equal-cost paths exist, load splitting will occur across the equal-cost paths for multicast traffic from different sources to the same multicast group, but not for traffic from the same source to different multicast groups. Because this command changes the way a Reverse Path Forwarding (RPF) neighbor is selected, it must be configured consistently on all routers in a redundant topology to avoid looping.
Examples
The following example shows how to configure the ip multicast multipath command:
ip multicast multipathRelated Commands
ip multicast route-limit
To limit the number of multicast routes (mroutes) that can be added to a multicast routing table, use the ip multicast route-limit command in global configuration mode. To disable this configuration, use the no form of this command.
ip multicast [vrf vrf-name] route-limit limit [threshold]
no ip multicast [vrf vrf-name] route-limit limit [threshold]
Syntax Description
Defaults
limit: 2147483647
Command Modes
Global configuration
Command History
Usage Guidelines
The ip multicast route-limit command limits the number of multicast routes that can be added to a router and generates an error message when the limit is exceeded. If the user sets the threshold argument, a threshold error message is generated when the threshold is exceeded, and the message continues to occur until the number of mroutes reaches the limit set by the limit argument.
The mroute warning threshold must not exceed the mroute limit.
Examples
The following example sets the mroute limit at 200,000 and the threshold at 20,000 for a VRF instance named cisco:
ip multicast vrf cisco route-limit 200000 20000ip multicast-routing
To enable IP multicast routing, use the ip multicast-routing command in global configuration mode. To disable IP multicast routing, use the no form of this command.
ip multicast-routing [vrf vrf-name] [distributed]
no ip multicast-routing [vrf vrf-name]
Syntax Description
Defaults
IP multicast routing is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When IP multicast routing is disabled, the Cisco IOS software does not forward any multicast packets.
Examples
The following example shows how to enable IP multicast routing:
Router(config)# ip multicast-routingRelated Commands
ip pim accept-register
To configure a candidate rendezvous point (RP) router to filter Protocol Independent Multicast (PIM) register messages, use the ip pim accept-register command in global configuration mode. To disable this function, use the no form of this command.
ip pim [vrf vrf-name] accept-register {list access-list | route-map map-name}
no ip pim [vrf vrf-name] accept-register {list access-list | route-map map-name}
Syntax Description
Defaults
The command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to prevent unauthorized sources from registering with the RP. If an unauthorized source sends a register message to the RP, the RP will immediately send back a register-stop message.
Examples
The following example shows how to restrict the RP from allowing sources in the Source Specific Multicast (SSM) range of addresses to register with the RP. These statements need to be configured only on the RP.
ip pim accept-register list no-ssm-rangeip access-list extended no-ssm-rangedeny ip any 232.0.0.0 0.255.255.255permit ip any anyip pim accept-rp
To configure a router to accept join or prune messages destined for a specified rendezvous point (RP) and for a specific list of groups, use the ip pim accept-rp command in global configuration mode. To remove that check, use the no form of this command.
ip pim [vrf vrf-name] accept-rp {rp-address | auto-rp} [access-list]
no ip pim [vrf vrf-name] accept-rp {rp-address | auto-rp} [access-list]
Syntax Description
Defaults
The command is disabled, so all join messages and prune messages are processed.
Command Modes
Global configuration
Command History
Usage Guidelines
This command causes the router to accept only (*, G) join messages destined for the specified RP address. Additionally, the group address must be in the range specified by the access list.
When the rp-address argument is one of the addresses of the system, the system will be the RP only for the specified group range specified by the access list. When the group address is not in the group range, the RP will not accept join or register messages and will respond immediately to register messages with register-stop messages.
Examples
The following example states that the router will accept join or prune messages destined for the RP at address 172.17.1.1 for the multicast group 224.2.2.2:
ip pim accept-rp 172.17.1.1 3access-list 3 permit 224.2.2.2Related Commands
ip pim bidir-enable
To enable bidirectional Protocol Independent Multicast (bidir-PIM), use the ip pim bidir-enable command in global configuration mode. To disable bidir-PIM, use the no form of this command.
ip pim [vrf vrf-name] bidir-enable
no ip pim [vrf vrf-name] bidir-enable
Syntax Description
vrf
(Optional) Supports the multicast Virtual Private Network (VPN) routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
The command is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Bidir-PIM is disabled by default to ensure complete backward compatibility when upgrading a router to Cisco IOS Release 12.0(18)ST or a later release.
When bidir-PIM is disabled, the router will behave similarly to a router without bidir-PIM support. The following conditions will apply:
•
•
•
–
–
•
Examples
The following example shows how to configure a rendezvous point (RP) for both sparse mode and bidirectional mode groups: 224/8 and 227/8 are bidirectional groups, 226/8 is sparse mode, and 225/8 is dense mode. The RP must be configured to use different IP addresses for the sparse mode and bidirectional mode operations. Two loopback interfaces are used to allow this configuration. The addresses of these loopback interfaces must be routed throughout the PIM domain such that the other routers in the PIM domain can receive Auto-RP announcements and communicate with the RP.
ip multicast-routing !Enable IP multicast routingip pim bidir-enable !Enable bidir-PIM!interface loopback 0description One Loopback adddress for this routers Bidir Mode RP functionip address 10.0.1.1 255.255.255.0ip pim sparse-dense-mode!interface loopback 1description One Loopback adddress for this routers Sparse Mode RP functionip address 10.0.2.1 255.255.255.0ip pim sparse-dense-modeip pim send-rp-announce Loopback0 scope 10 group-list 45 bidirip pim send-rp-announce Loopback1 scope 10 group-list 46ip pim send-rp-discovery scope 10access-list 45 permit 224.0.0.0 0.255.255.255access-list 45 permit 227.0.0.0 0.255.255.255access-list 45 deny 225.0.0.0 0.255.255.255access-list 46 permit 226.0.0.0 0.255.255.255Related Commands
ip pim bsr-candidate
To configure the router to announce its candidacy as a bootstrap router (BSR), use the ip pim bsr-candidate command in global configuration mode. To remove this router as a candidate for being a bootstrap router, use the no form of this command.
ip pim [vrf vrf-name] bsr-candidate interface-type interface-number [hash-mask-length] [priority]
no ip pim [vrf vrf-name] bsr-candidate interface-type interface-number [hash-mask-length] [priority]
Syntax Description
Defaults
The command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command causes the router to send bootstrap messages to all its PIM neighbors, with the address of the designated interface as the BSR address. Each neighbor compares the BSR address with the address it had from previous bootstrap messages (not necessarily received on the same interface). If the current address is the same or higher address, it caches the current address and forwards the bootstrap message. Otherwise, it drops the bootstrap message.
This router continues to be the BSR until it receives a bootstrap message from another candidate BSR saying that it has a higher priority (or if the same priority, a higher IP address).
Use this command only in backbone routers that have good connectivity to all parts of the PIM domain. That is, a stub router that relies on an on-demand dialup link to connect to the rest of the PIM domain is not a good candidate BSR.
Examples
The following example configures the IP address of the router on Ethernet interface 0 to be a candidate BSR with priority of 10:
ip pim bsr-candidate ethernet 0 10Related Commands
ip pim register-rate-limit
To set a limit on the maximum number of Protocol Independent Multicast sparse mode (PIM-SM) register messages sent per second for each (S, G) routing entry, use the ip pim register-rate-limit command in global configuration mode. To disable this limit, use the no form of this command.
ip pim [vrf vrf-name] register-rate-limit rate
no ip pim [vrf vrf-name] register-rate-limit rate
Syntax Description
Defaults
No limit is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to limit the number of register messages that the designated router (DR) will allow for each (S, G) entry. Enabling this command will limit the load on the DR and RP at the expense of dropping those register messages that exceed the set limit. Receivers may experience data packet loss within the first second in which register messages are sent from bursty sources.
If the ip pim dense-mode proxy-register command is configured, then the ip pim register-rate-limit command must be configured because of the potentially large number of sources from the dense mode area that may send data into the sparse mode region (and thus need registering in the border router).
This command applies only to sparse mode (S, G) multicast routing entries.
Examples
The following example shows how to configure the ip pim register-rate-limit command with a maximum rate of two register messages per second:
ip pim register-rate-limit 2Related Commands
ip pim register-source
To configure the IP source address of a register message to an interface address other than the outgoing interface address of the designated router (DR) leading toward the rendezvous point (RP), use the ip pim register-source command in global configuration mode. To disable this configuration, use the no form of this command.
ip pim [vrf vrf-name] register-source interface-type interface-number
no ip pim [vrf vrf-name] register-source interface-type interface-number
Syntax Description
Defaults
By default, the IP address of the outgoing interface of the DR leading toward the RP is used as the IP source address of a register message.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is required only when the IP source address of a register message is not a uniquely routed address to which the RP can send packets. This situation may occur if the source address is filtered such that packets sent to it will not be forwarded or if the source address is not unique to the network. In these cases, the replies sent from the RP to the source address will fail to reach the DR, resulting in Protocol Independent Multicast sparse mode (PIM-SM) protocol failures.
If no IP source address is configured or if the configured source address is not in service, the IP address of the outgoing interface of the DR leading toward the RP is used as the IP source address of the register message. Therefore, we recommend using a loopback interface with an IP address that is uniquely routed throughout the PIM-SM domain.
Examples
The following example shows how to configure the IP source address of the register message to the loopback 3 interface of a DR:
ip pim register-source loopback 3ip pim rp-announce-filter
To filter incoming Auto-RP announcement messages coming from the rendezvous point (RP), use the ip pim rp-announce-filter command in global configuration mode. To remove the filter, use the no form of this command.
ip pim [vrf vrf-name] rp-announce-filter rp-list access-list group-list access-list
no ip pim [vrf vrf-name] rp-announce-filter rp-list access-list group-list access-list
Syntax Description
Defaults
All RP announcements are accepted.
Command Modes
Global configuration
Command History
Usage Guidelines
Configure this command on the Protocol Independent Multicast (PIM) RP mapping agent. We recommend that if you use more than one RP mapping agent, make the filters among them consistent so that there are no conflicts in mapping state when the announcing agent goes down.
Examples
The following example configures the router to accept RP announcements from RPs in access list 1 for group ranges described in access list 2:
ip pim rp-announce-filter rp-list 1 group-list 2access-list 1 permit 10.0.0.1access-list 1 permit 10.0.0.2access-list 2 permit 224.0.0.0 192.168.255.255Related Commands
ip pim rp-candidate
To configure the router to advertise itself as a Protocol Independent Multicast (PIM) Version 2 candidate rendezvous point (RP) to the bootstrap router (BSR), use the ip pim rp-candidate command in global configuration mode. To remove this router as an RP candidate, use the no form of this command.
ip pim [vrf vrf-name] rp-candidate interface-type interface-number [bidir] [group-list access-list] [interval seconds] [priority value]
no ip pim [vrf vrf-name] rp-candidate
Syntax Description
Defaults
The command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command causes the router to send a PIM Version 2 message advertising itself as a candidate RP to the BSR. The addresses allowed by the access list, together with the router identified by the type and number, constitute the RP and its range of addresses for which it is responsible.
Use this command only in backbone routers that have good connectivity to all parts of the PIM domain. That is, a stub router that relies on an on-demand dialup link to connect to the rest of the PIM domain is not a good candidate RP.
Use this command with the bidir keyword when you want bidirectional forwarding and you are using the PIM Version 2 BSR mechanism to distribute group-to-RP mappings. Other options are as follows:
•
•
Examples
The following example configures the router to advertise itself as a candidate RP to the BSR in its PIM domain. Standard access list number 4 specifies the group prefix associated with the RP that has the address identified by Ethernet interface 2. That RP is responsible for the groups with the prefix 239.
ip pim rp-candidate ethernet 2 group-list 4access-list 4 permit 239.0.0.0 0.255.255.255Related Commands
ip pim send-rp-announce
To use Auto-RP to configure groups for which the router will act as a rendezvous point (RP), use the ip pim send-rp-announce command in global configuration mode. To unconfigure this router as an RP, use the no form of this command.
ip pim [vrf vrf-name] send-rp-announce interface-type interface-number scope ttl-value [group-list access-list] [interval seconds] [bidir]
no ip pim [vrf vrf-name] send-rp-announce interface-type interface-number scope ttl-value [group-list access-list] [interval seconds] [bidir]
Syntax Description
Defaults
Auto-RP is disabled.
seconds: 60Command Modes
Global configuration
Command History
Usage Guidelines
Use this command in the router you want to be an RP. When you are using Auto-RP to distribute group-to-RP mappings, this command causes the router to send an Auto-RP announcement message to the well-known group CISCO-RP-ANNOUNCE (224.0.1.39). This message announces the router as a candidate RP for the groups in the range described by the access list.
Use this command with the bidir keyword when you want bidirectional forwarding and you are using Auto-RP to distribute group-to-RP mappings. Other options are as follows:
•
•
Examples
The following example sends RP announcements out all Protocol Independent Multicast (PIM)-enabled interfaces for a maximum of 31 hops. The IP address by which the router wants to be identified as RP is the IP address associated with Ethernet interface 0. Access list 5 describes the groups for which this router serves as RP.
ip pim send-rp-announce ethernet0 scope 31 group-list 5access-list 5 permit 224.0.0.0 15.255.255.255Related Commands
ip pim send-rp-discovery
To configure the router to be a rendezvous point (RP) mapping agent, use the ip pim send-rp-discovery command in global configuration mode. To restore the default value, use the no form of this command.
ip pim [vrf vrf-name] send-rp-discovery [interface-type interface-number] scope ttl-value
no ip pim [vrf vrf-name] send-rp-discovery [interface-type interface-number] scope ttl-value
Syntax Description
Defaults
The router is not an RP mapping agent.
Command Modes
Global configuration
Command History
Usage Guidelines
Configure this command on the router designated as an RP mapping agent. Specify a TTL large enough to cover your Protocol Independent Multicast (PIM) domain.
When Auto-RP is used, the following events occur:
1.
2.
3.
Examples
The following example limits Auto-RP RP discovery messages to 20 hops:
ip pim send-rp-discovery scope 20ip pim spt-threshold
To configure when a Protocol Independent Multicast (PIM) leaf router should join the shortest path source tree for the specified group, use the ip pim spt-threshold command in global configuration mode. To restore the default value, use the no form of this command.
ip pim [vrf vrf-name] spt-threshold {kbps | infinity} [group-list access-list]
no ip pim [vrf vrf-name] spt-threshold {kbps | infinity} [group-list access-list]
Syntax Description
Defaults
When this command is not used, the PIM leaf router joins the shortest path tree immediately after the first packet arrives from a new source.
Command Modes
Global configuration
Command History
Usage Guidelines
If a source sends at a rate greater than or equal to traffic rate (the kbps value), a PIM join message is triggered toward the source to construct a source tree.
If the infinity keyword is specified, all sources for the specified group will use the shared tree. Specifying a group list access list indicates the groups to which the threshold applies.
If the traffic rate from the source drops below the threshold traffic rate, the leaf router will switch back to the shared tree and send a prune message toward the source.
Examples
The following example sets a threshold of 4 kbps, above which traffic to a group from a source will cause the router to switch to the shortest path tree to that source:
ip pim spt-threshold 4ip pim ssm
To define the Source Specific Multicast (SSM) range of IP multicast addresses, use the ip pim ssm command in global configuration mode. To disable the SSM range, use the no form of this command.
ip pim [vrf vrf-name] ssm {default | range access-list}
no ip pim [vrf vrf-name] ssm {default | range access-list}
Syntax Description
Defaults
The command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When an SSM range of IP multicast addresses is defined by the ip pim ssm command, no Multicast Source Discovery Protocol (MSDP) Source-Active (SA) messages will be accepted or originated in the SSM range.
Examples
The following example shows how to configure SSM service for the IP address range defined by access list 4:
access-list 4 permit 224.2.151.141ip pim ssm range 4Related Commands
ip pim state-refresh disable
To disable the processing and forwarding of PIM dense mode state refresh control messages on a Protocol Independent Multicast (PIM) router, use the ip pim state-refresh disable command in global configuration mode. To reenable the processing and forwarding of PIM dense mode state refresh control messages, use the no form of this command.
ip pim [vrf vrf-name] state-refresh disable
no ip pim [vrf vrf-name] state-refresh disable
Syntax Description
vrf
(Optional) Supports the multicast Virtual Private Network (VPN) routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Defaults
The processing and forwarding of PIM dense mode state refresh control messages is enabled on PIM routers that are running a Cisco IOS software release that supports the PIM dense mode state refresh feature.
Command Modes
Global configuration
Command History
Usage Guidelines
Configuring this command removes PIM dense mode state refresh information from PIM hello messages.
Examples
The following example disables the periodic forwarding of the PIM dense mode state refresh control message down a source-based IP multicast distribution tree:
ip pim state-refresh disableRelated Commands
mdt data
To configure the multicast group address range for data multicast distribution tree (MDT) groups, use the mdt data command in VRF configuration mode. To disable this function, use the no form of this command.
mdt data group-address-range wildcard-bits [threshold threshold-value] [list access-list]
no mdt data group-address-range wildcard-bits [threshold threshold-value] [list access-list]
Syntax Description
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
Usage Guidelines
A data MDT group can include a maximum of 256 multicast groups per Virtual Private Network (VPN). Multicast groups used to create the data MDT group are dynamically chosen from a pool of configured IP addresses.
This command configures a range of alternative multicast destination addresses for the tunnel header. The destination address chosen depends on the traffic profile (that is, the source and destination match the specified access list and the rate of the traffic has exceeded the bandwidth threshold value).
Examples
In the following example, Protocol Independent Multicast (PIM) Source Specific Multicast (SSM) is configured in the backbone. Therefore, the default and data MDT groups are configured within the SSM range of IP addresses. Inside the VPN, PIM sparse mode (PIM-SM) is configured and only the Auto-RP announcements are accepted.
ip vrf vrf1rd 1:1route-target export 1:1route-target import 1:1mdt default 232.0.0.1mdt data 232.0.1.0 0.0.0.255 threshold 500 list 101!ip pim ssm defaultip pim vrf vrf1 accept-rp auto-rpRelated Commands
mdt default
To configure a default multicast distribution tree (MDT) group for a Virtual Private Network (VPN) routing and forwarding (VRF) instance, use the mdt default command in VRF configuration mode. To disable this function, use the no form of this command.
mdt default group-address
no mdt default group-address
Syntax Description
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
Usage Guidelines
The default MDT group must be the same group configured on all PE routers that belong to the same VPN.
If Source Specific Multicast (SSM) is used as the protocol for the default MDT, the source IP address will be the address used to source the Border Gateway Protocol (BGP) sessions.
A tunnel interface is created as a result of this command. By default, the destination address of the tunnel header is the group-address argument.
Examples
In the following example, Protocol Independent Multicast (PIM) SSM is configured in the backbone. Therefore, the default and data MDT groups are configured within the SSM range of IP addresses. Inside the VPN, PIM sparse mode (PIM-SM) is configured and only the Auto-RP announcements are accepted.
Router(config)# ip vrf redRouter(config-vrf)# rd 1:1Router(config-vrf)# route-target export 1:1Router(config-vrf)# route-target import 1:1Router(config-vrf)# mdt default 232.0.0.1Router(config-vrf)# mdt data 232.0.1.0 0.0.0.255 threshold 500 list 101Router(config-vrf)# exitRouter(config)# ip pim ssm defaultRouter(config)# ip pim vrf red accept-rp auto-rpRelated Commands
mdt log-reuse
To enable the recording of data multicast distribution tree (MDT) reuse, use the mdt log-reuse command in VRF configuration mode. To disable this function, use the no form of this command.
mdt log-reuse
no mdt log-reuse
Syntax Description
This command has no arguments or keywords.
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
Usage Guidelines
The mdt log-reuse command generates a syslog message whenever a data MDT is reused.
Examples
In the following example, the MDT log reuse function is enabled.
mdt log-reuseRelated Commands
mdt data
Configures the multicast group address range for data MDT groups.
mdt default
Configures a default MDT group for a VPN VRF.
show ip hardware-mdfs mgid
To display the mapping between a multicast group ID (MGID) and the information stored in the line card hardware memory, use the show ip hardware-mdfs mgid command in user EXEC or privileged EXEC mode.
execute-on slot slot-number show ip hardware-mdfs mgid mgid-number {both-tables | encap-string | path-bits}
Syntax Description
Defaults
No default behaviors or values
Command Modes
User EXEC
Privileged EXECCommand History
12.0(26)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series router.
Usage Guidelines
Use this command with the show ip mds mgid-table command to verify that all entries in the Cisco IOS software table have corresponding entries in the line card hardware table.
You can execute this command only on Engine 3 line cards, because FastPath forwarding of multicast VPN (MVPN) packets upon encapsulation and decapsulation is supported only on Engine 3. Use this command to display information about the hardware memory used for MVPN.
Note
Examples
The following is sample output from the show ip hardware-mdfs mgid command for a line card in slot 2:
Router# execute-on slot 2 show ip hardware-mdfs mgid 125 both-tables========= Line Card (Slot 2) =========0x7D:vrf tbl base=0x20030C00, vrfx=y vrf0=n0x7D:encap = 00066830000000007819A0C0000000000000007D00000002Table 9 describes the significant fields shown in the display.
Related Commands
show ip mds mgid-table
Displays the information stored in the MGID mapping table of a line card.
show ip igmp groups
To display the multicast groups with receivers that are directly connected to the router and that were learned through Internet Group Management Protocol (IGMP), use the show ip igmp groups command in user EXEC or privileged EXEC mode.
show ip igmp [vrf vrf-name] groups [group-name | group-address | interface-type interface-number] [detail]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If you omit all optional arguments and keywords, the show ip igmp groups command displays by group address, interface type, and interface number all directly connected multicast groups.
Examples
The following is sample output from the show ip igmp groups command:
Router# show ip igmp groupsIGMP Connected Group MembershipGroup Address Interface Uptime Expires Last Reporter239.255.255.254 Ethernet3/1 1w0d 00:02:19 172.21.200.159224.0.1.40 Ethernet3/1 1w0d 00:02:15 172.21.200.1224.0.1.40 Ethernet3/3 1w0d never 172.16.214.251224.0.1.1 Ethernet3/1 1w0d 00:02:11 172.21.200.11224.9.9.2 Ethernet3/1 1w0d 00:02:10 172.21.200.155232.1.1.1 Ethernet3/1 5d21h stopped 172.21.200.206The following is sample output from the show ip igmp groups command with the group-address argument and detail keyword:
Router# show ip igmp groups 232.1.1.1 detailInterface: Ethernet3/2Group: 232.1.1.1Uptime: 01:58:28Group mode: INCLUDELast reporter: 10.0.119.133CSR Grp Exp: 00:02:38Group source list: (C - Cisco Src Report, U - URD, R - RemoteS- Static, M - SSM Mapping)Source Address Uptime v3 Exp CSR Exp Fwd Flags172.16.214.1 01:58:28 stopped 00:02:31 Yes CTable 10 describes the significant fields shown in the displays.
Related Commands
show ip igmp interface
To display multicast-related information about an interface, use the show ip igmp interface command in user EXEC or privileged EXEC mode.
show ip igmp [vrf vrf-name] interface [interface-type interface-number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If you omit the optional arguments, the show ip igmp interface command displays information about all interfaces.
This command also displays information about dynamically learned Distance Vector Multicast Routing Protocol (DVMRP) routers on the interface.
Examples
The following is sample output from the show ip igmp interface command:
Router# show ip igmp interfaceEthernet0 is up, line protocol is upInternet address is 192.168.37.6, subnet mask is 255.255.255.0IGMP is enabled on interfaceIGMP query interval is 60 secondsInbound IGMP access group is not setMulticast routing is enabled on interfaceMulticast TTL threshold is 0Multicast designated router (DR) is 192.168.37.33No multicast groups joinedEthernet1 is up, line protocol is upInternet address is 192.168.36.129, subnet mask is 255.255.255.0IGMP is enabled on interfaceIGMP query interval is 60 secondsInbound IGMP access group is not setMulticast routing is enabled on interfaceMulticast TTL threshold is 0Multicast designated router (DR) is 192.168.36.131Multicast groups joined: 225.2.2.2 226.2.2.2Tunnel0 is up, line protocol is upInternet address is 10.1.37.2, subnet mask is 255.255.0.0IGMP is enabled on interfaceIGMP query interval is 60 secondsInbound IGMP access group is not setMulticast routing is enabled on interfaceMulticast TTL threshold is 0No multicast groups joinedTable 11 describes the significant fields shown in the display.
Related Commands
show ip mcache
To display the contents of the IP fast-switching cache, use the show ip mcache command in user EXEC or privileged EXEC mode.
show ip mcache [vrf vrf-name] [group-address | group-name] [source-address | source-name]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show ip mcache user EXEC command. This entry shows a specific source (group1-source 239.1.1.1) sending to the group1 group (239.2.2.2).
Router> show ip mcache group1 group1-sourceIP Multicast Fast-Switching Cache(239.1.1.1/32, 239.2.2.2), Fddi0, Last used: 00:00:00Ethernet0 MAC Header: 01005E028F1800000C1883D30800Ethernet1 MAC Header: 01005E028F1800000C1883D60800Ethernet2 MAC Header: 01005E028F1800000C1883D40800Ethernet3 MAC Header: 01005E028F1800000C1883D70800The following is sample output from the show ip mcache privileged EXEC command when multicast distributed switching (MDS) is in effect:
Router# show ip mcacheIP Multicast Fast-Switching Cache(*, 239.2.3.4), Fddi3/0/0, Last used: mdsTunnel3 MAC Header: 5000602F9C150000603E473F60AAAA030000000800 (Fddi3/0/0)Tunnel0 MAC Header: 5000602F9C150000603E473F60AAAA030000000800 (Fddi3/0/0)Tunnel1 MAC Header: 5000602F9C150000603E473F60AAAA030000000800 (Fddi3/0/0)Table 12 describes the significant fields shown in the display.
show ip mds interface
To display Multicast Distributed Switching (MDS) information for all the interfaces on the line card, use the show ip mds interface command in user EXEC or privileged EXEC mode.
show ip mds interface [vrf vrf-name]
Syntax Description
vrf
(Optional) Supports the Multicast Virtual Private Network (VPN) routing/forwarding instance (VRF).
vrf-name
(Optional) Name assigned to the VRF.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show ip mds interface command.
Router# show ip mds interfaceInterface SW-Index HW-Index HW IDB FS Vector VRFEthernet1/0/0 2 1 0x60C2DB40 0x602FB7A4 defaultEthernet1/0/1 3 2 0x60C32280 0x603D52B8 defaultEthernet1/0/2 4 3 0x60C35E40 0x602FB7A4 defaultEthernet1/0/3 5 4 0x60C39E60 0x603D52B8 defaultEthernet1/0/4 6 5 0x60C3D780 0x602FB7A4 defaultEthernet1/0/5 7 6 0x60C41140 0x602FB7A4 defaultEthernet1/0/6 8 7 0x60C453A0 0x602FB7A4 defaultEthernet1/0/7 9 8 0x60C48DC0 0x602FB7A4 defaultPOS2/0/0 10 9 0x0 defaultPOS3/0/0 11 10 0x0 defaultVirtual-Access1 13 11 0x0 defaultLoopback0 14 12 0x0 defaultTunnel0 15 23 0x61C2E480 0x603D52B8 vrf1Tunnel1 16 24 0x61C267E0 0x603D52B8 vrf2Ethernet1/0/3.1 17 4 0x60C39E60 0x603D52B8 vrf1Ethernet1/0/3.2 18 4 0x60C39E60 0x603D52B8 vrf2Table 13 describes the significant fields shown in the display.
show ip mds mgid-table
To display the information stored in the multicast group ID (MGID) mapping table of a line card, use the show ip mds mgid-table command in user EXEC or privileged EXEC mode.
execute-on slot slot-number show ip mds mgid-table
Syntax Description
execute-on slot
Executes this show command on a particular line card.
slot-number
Slot number of the line card on which to execute this command.
Defaults
No default behaviors or values
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use this command to display the mapping table stored in the line card CPU memory. This table displays, for each global MGID, the VPN routing and forwarding instance (VRF), used for the decapsulation of the generic routing encapsulation (GRE) header, and the encapsulation string, used for encapsulation of the GRE header.
Note
Examples
The following is sample output from the show ip mds mgid-table command executed on the line card in slot 2:
Router# execute-on slot 2 show ip mds mgid-table========= Line Card (Slot 2) =========MDFS MGID Table EntriesMGID ID VRFx VRF0 Encap String------- --- ---- ---- ------------0x0007C 1 Y N 45000001 00000000 FF2F0000 02020204 E8000001 000008000x0007D 1 Y N0x0007E 1 Y N0x00080 1 Y N 42424242 42424242 42424242 42424242 42424242 42424242Table 14 describes the significant fields shown in the display.
Related Commands
show ip hardware-mdfs mgid
Displays the mapping between an MGID and the information stored in the line card hardware memory.
show ip mpacket
To display the contents of the circular cache-header buffer, use the show ip mpacket command in privileged EXEC mode.
show ip mpacket [vrf vrf-name] [group-address | group-name] [source-address | source-name] [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is applicable only when the ip multicast cache-headers command is in effect.
Each time this command is entered, a new buffer is allocated. The summary display (when the detail keyword is omitted) shows the IP packet identifier, time-to-live (TTL) value, source and destination IP addresses, and a local time stamp when the packet was received.
The three arguments and two keywords can be used in the same command in any combination.
Examples
The following is sample output from the show ip mpacket command with the group-name argument:
Router# show ip mpacket smallgroupIP Multicast Header Cache - entry count:6, next index: 7Key: id/ttl timestamp (name) source groupD782/117 206416.908 (company1.company.com) 192.168.228.10 224.5.6.77302/113 206417.908 (school.edu) 172.16.2.17 224.5.6.76CB2/114 206417.412 (company2.company.com) 172.16.19.40 224.5.6.7D782/117 206417.868 (company1.company.com) 192.168.228.10 224.5.6.7E2E9/123 206418.488 (company3.com) 239.1.8.10 224.5.6.71CA7/127 206418.544 (company4.company.com) 192.168.6.10 224.5.6.7Table 15 describes the significant fields shown in the display.
Related Commands
ip multicast cache-headers
Allocates a circular buffer to store IP multicast packet headers that the router receives.
show ip mroute
To display the contents of the IP multicast routing (mroute) table, use the show ip mroute command in user EXEC or privileged EXEC mode.
show ip mroute [vrf vrf-name] [group-address | group-name] [source-address | source-name] [interface-type interface-number] [summary] [count] [active kbps]
Syntax Description
Defaults
The show ip mroute command displays all groups and sources.
The show ip mroute active command displays all sources sending at a rate greater than or equal to 4 kbps.Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If you omit all optional arguments and keywords, the show ip mroute command displays all entries in the IP multicast routing table.
The Cisco IOS software populates the multicast routing table by creating (S, G) entries from (*, G) entries. The asterisk (*) refers to all source addresses, the "S" refers to a single source address, and the "G" is the destination multicast group address. In creating (S, G) entries, the software uses the best path to that destination group found in the unicast routing table (that is, through Reverse Path Forwarding [RPF]).
The output for the show ip mroute command with the active keyword will display either positive or negative numbers for the rate PPS. The router displays negative numbers when RPF packets fail or when the router observes RPF packets with an interfaces out (OIF) list. This type of activity may indicate a multicast routing problem.
Examples
The following is sample output from the show ip mroute command for a router operating in dense mode. This output displays the contents of the IP multicast routing table for the multicast group named cbone-audio.
Router# show ip mroute cbone-audioIP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,Y - Joined MDT-data group, y - Sending to MDT-data groupTimers: Uptime/ExpiresInterface state: Interface, Next-Hop, State/Mode(*, 224.0.255.1), uptime 0:57:31, expires 0:02:59, RP is 224.0.0.0, flags: DCIncoming interface: Null, RPF neighbor 224.0.0.0, DvmrpOutgoing interface list:Ethernet0, Forward/Dense, 0:57:31/0:02:52Tunnel0, Forward/Dense, 0:56:55/0:01:28(192.168.37.100/32, 224.0.255.1), uptime 20:20:00, expires 0:02:55, flags: CIncoming interface: Tunnel0, RPF neighbor 10.20.37.33, DvmrpOutgoing interface list:Ethernet0, Forward/Dense, 20:20:00/0:02:52The following is sample output from the show ip mroute command for a router operating in sparse mode:
Router# show ip mrouteIP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,Y - Joined MDT-data group, y - Sending to MDT-data groupTimers: Uptime/ExpiresInterface state: Interface, Next-Hop, State/Mode(*, 224.0.255.3), uptime 5:29:15, RP is 192.168.37.2, flags: SCIncoming interface: Tunnel0, RPF neighbor 10.3.35.1, DvmrpOutgoing interface list:Ethernet0, Forward/Sparse, 5:29:15/0:02:57(192.168.46.0/24, 224.0.255.3), uptime 5:29:15, expires 0:02:59, flags: CIncoming interface: Tunnel0, RPF neighbor 10.3.35.1Outgoing interface list:Ethernet0, Forward/Sparse, 5:29:15/0:02:57The following is sample output from the show ip mroute command that shows the virtual circuit descriptor (VCD) value, because an ATM interface with Protocol Independent Multicast (PIM) multipoint signaling is enabled:
Router# show ip mroute 224.1.1.1IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,Y - Joined MDT-data group, y - Sending to MDT-data groupTimers: Uptime/ExpiresInterface state: Interface, Next-Hop or VCD, State/Mode(*, 224.1.1.1), 00:03:57/00:02:54, RP 172.16.0.0, flags: SJIncoming interface: Null, RPF nbr 224.0.0.0224.0.0.0Outgoing interface list:ATM0/0, VCD 14, Forward/Sparse, 00:03:57/00:02:53The following is sample output from the show ip mroute command with the summary keyword:
Router# show ip mroute summaryIP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,Y - Joined MDT-data group, y - Sending to MDT-data groupTimers: Uptime/ExpiresInterface state: Interface, Next-Hop, State/Mode(*, 224.255.255.255), 2d16h/00:02:30, RP 172.16.10.13, flags: SJPC(*, 224.2.127.253), 00:58:18/00:02:00, RP 172.16.10.13, flags: SJC(*, 224.1.127.255), 00:58:21/00:02:03, RP 172.16.10.13, flags: SJC(*, 224.2.127.254), 2d16h/00:00:00, RP 172.16.10.13, flags: SJCL(172.16.160.67/32, 224.2.127.254), 00:02:46/00:00:12, flags: CLJT(172.16.244.217/32, 224.2.127.254), 00:02:15/00:00:40, flags: CLJT(172.16.8.33/32, 224.2.127.254), 00:00:25/00:02:32, flags: CLJT(172.16.2.62/32, 224.2.127.254), 00:00:51/00:02:03, flags: CLJT(172.16.8.3/32, 224.2.127.254), 00:00:26/00:02:33, flags: CLJT(172.16.60.189/32, 224.2.127.254), 00:03:47/00:00:46, flags: CLJTThe following is sample output from the show ip mroute command with the active keyword:
Router# show ip mroute active 4Active IP Multicast Sources - sending >= 4 kbpsGroup: 224.2.127.254, (sdr.cisco.com)Source: 192.168.28.69 (mbone.ipd.anl.gov)Rate: 1 pps/4 kbps(1sec), 4 kbps(last 1 secs), 4 kbps(life avg)Group: 224.2.201.241, ACM 97Source: 192.168.52.160 (webcast3-e1.acm97.interop.net)Rate: 9 pps/93 kbps(1sec), 145 kbps(last 20 secs), 85 kbps(life avg)Group: 224.2.207.215, ACM 97Source: 192.168.52.160 (webcast3-e1.acm97.interop.net)Rate: 3 pps/31 kbps(1sec), 63 kbps(last 19 secs), 65 kbps(life avg)The following is sample output from the show ip mroute command for a router supporting SSM services. The IP multicast group address is specified as 232.6.6.6.
Router# show ip mroute 232.6.6.6IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,Y - Joined MDT-data group, y - Sending to MDT-data groupOutgoing interface flags:H - Hardware switchedTimers:Uptime/ExpiresInterface state:Interface, Next-Hop or VCD, State/Mode(*, 232.6.6.6), 00:01:20/00:02:59, RP 224.0.0.0, flags:sSJPIncoming interface:Null, RPF nbr 224.0.0.0Outgoing interface list:Null(10.2.2.2, 232.6.6.6), 00:01:20/00:02:59, flags:CTIIncoming interface:Ethernet3/3, RPF nbr 224.0.0.0Outgoing interface list:Ethernet3/1, Forward/Sparse-Dense, 00:00:36/00:02:35Table 16 describes the significant fields shown in the display.
The following is sample output from the show ip mroute command with the count keyword:
Router# show ip mroute countIP Multicast Statistics4045 routes using 2280688 bytes of memory41 groups, 97.65 average sources per groupForwarding Counts:Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per secondOther counts:Total/RPF failed/Other drops(OIF-null, rate-limit etc)Group:239.0.18.1, Source count:200, Packets forwarded:348232, Packets received:348551RP-tree:Forwarding:12/0/218/0, Other:12/0/0Source:10.1.1.1/32, Forwarding:1763/1/776/9, Other:1764/0/1Source:10.1.1.2/32, Forwarding:1763/1/777/9, Other:1764/0/1Source:10.1.1.3/32, Forwarding:1763/1/783/10, Other:1764/0/1Source:10.1.1.4/32, Forwarding:1762/1/789/10, Other:1763/0/1Source:10.1.1.5/32, Forwarding:1762/1/768/10, Other:1763/0/1Source:10.1.1.6/32, Forwarding:1793/1/778/10, Other:1794/0/1Source:10.1.1.7/32, Forwarding:1793/1/763/10, Other:1794/0/1Source:10.1.1.8/32, Forwarding:1793/1/785/10, Other:1794/0/1Source:10.1.1.9/32, Forwarding:1793/1/764/9, Other:1794/0/1Source:10.1.1.10/32, Forwarding:1791/1/774/10, Other:1792/0/1Source:10.1.2.1/32, Forwarding:1689/1/780/10, Other:1691/0/2Source:10.1.2.2/32, Forwarding:1689/1/782/10, Other:1691/0/2Source:10.1.2.3/32, Forwarding:1689/1/776/9, Other:1691/0/2...Group:239.0.18.132, Source count:0, Packets forwarded:8810, Packets received:8810RP-tree:Forwarding:8810/7/780/49, Other:8810/0/0Group:239.0.17.132, Source count:0, Packets forwarded:704491, Packets received:704491RP-tree:Forwarding:704491/639/782/4009, Other:704491/0/0Group:239.0.17.133, Source count:0, Packets forwarded:704441, Packets received:704441RP-tree:Forwarding:704441/639/782/3988, Other:704441/0/0Group:239.0.18.133, Source count:0, Packets forwarded:8810, Packets received:8810RP-tree:Forwarding:8810/8/786/49, Other:8810/0/0Group:239.0.18.193, Source count:0, Packets forwarded:0, Packets received:0Group:239.0.17.193, Source count:0, Packets forwarded:0, Packets received:0Group:239.0.18.134, Source count:0, Packets forwarded:8803, Packets received:8803RP-tree:Forwarding:8803/8/774/49, Other:8803/0/0
Note
Table 17 describes the significant fields shown in the display.
Related 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 user EXEC or privileged EXEC mode.
show ip msdp [vrf vrf-name] count [as-number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 from the show ip msdp count command:
Router# show ip msdp countSA State per Peer Counters, <Peer>: <# SA learned>224.135.250.116: 24172.16.240.253: 3964172.16.253.19: 10172.16.170.110: 11SA State per ASN Counters, <asn>: <# sources>/<# groups>Total entries: 4009?: 192/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 18 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 user EXEC or privileged EXEC mode.
show ip msdp [vrf vrf-name] peer [peer-address | peer-name] [accepted-sas | advertised-sas]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show ip msdp peer command:
Router# show ip msdp peer 224.135.250.116MSDP Peer 224.135.250.116 (rtp5-rp1.cisco.com), AS 109 (configured AS)Description:Connection status:State: Up, Resets: 9, Connection source: Loopback2 (228.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 19 describes the significant fields shown in the display.
Related Commands
show ip msdp sa-cache
To display (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
Usage Guidelines
State is cached only if the ip msdp cache-sa-state command is configured.
When the show ip msdp sa-cache command is enabled with the rejected-sa keyword or with both the rejected-sa and detail keywords, the cache is emptied. When the read-only keyword is added to the command string, the cache is not emptied.
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 20 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 user EXEC or privileged EXEC mode.
show ip msdp [vrf vrf-name] summary
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show ip msdp summary command:
Router# show ip msdp summaryMSDP Peer Status SummaryPeer Address AS State Uptime/ Reset SA Peer NameDowntime Count Count224.135.250.116 109 Up 1d10h 9 111 rtp5-rp1*172.20.240.253 1239 Up 14:24:00 5 4010 sl-rp-stk172.16.253.19 109 Up 12:36:17 5 10 shinjuku-rp1172.16.170.110 109 Up 1d11h 9 12 ams-rp1Table 21 describes the significant fields shown in the display.
show ip pim mdt bgp
To show detailed Border Gateway Protocol (BGP) advertisement of the route distinguisher (RD) for the multicast distribution tree (MDT) default group, use the show ip pim mdt bgp command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] mdt bgp
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use this command to show detailed BGP advertisement of the RD for the MDT default group.
Examples
The following is sample output from the show ip pim mdt bgp command:
Router# show ip pim mdt bgpMDT-default group 232.2.1.4rid:10.1.1.1 next_hop:10.1.1.1Table 22 describes the significant fields shown in the display.
show ip pim mdt history
To provide information on data multicast distribution trees (MDTs) that have been reused, use the show ip pim mdt history command in privileged EXEC mode.
show ip pim [vrf vrf-name] mdt history interval {minutes}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show ip pim mdt history command displays the data MDTs that have been reused during the past configured interval.
Examples
The following is sample output from the show ip pim mdt history command with the interval configured to be 20 minutes:
Router# show ip pim vrf vrf1 mdt history interval 20MDT-data send history for VRF - vrf1 for the past 20 minutesMDT-data group Number of reuse10.9.9.8 310.9.9.9 2Table 23 describes the significant fields shown in the display.
show ip pim mdt receive
To display the data multicast distribution tree (MDT) advertisements received by a specified router, use the show ip pim mdt receive command in privileged EXEC mode.
show ip pim [vrf vrf-name] mdt receive [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When a router wants to switch over from the default MDT to a data MDT, it advertises the VRF source, the group pair, and the global multicast address over which the traffic will be sent. If the remote router wants to receive this data, then it will join this global address multicast group.
Examples
The following is sample output from the show ip pim mdt receive command using the detail keyword for further information:
Router# show ip pim vrf vpn8 mdt receive detailJoined MDT-data groups for VRF:vpn8group:172.16.8.0 source:10.0.0.100 ref_count:13(10.101.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:26, OIF count:1, flags:TY(10.102.8.10, 225.1.8.1), 1d13h/00:03:28/00:02:27, OIF count:1, flags:TYTable 24 describes the significant fields shown in the display.
show ip pim mdt send
To show the data multicast distribution tree (MDT) advertisements that a specified router has made, use the show ip pim mdt send command in privileged EXEC mode.
show ip pim [vrf vrf-name] mdt send
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to show the data MDT advertisements that a specified router has made.
Examples
The following is sample output from the show ip pim mdt send command:
Router# show ip pim mdt sendMDT-data send list for VRF:vpn8(source, group) MDT-data group ref_count(10.100.8.10, 225.1.8.1) 232.2.8.0 1(10.100.8.10, 225.1.8.2) 232.2.8.1 1(10.100.8.10, 225.1.8.3) 232.2.8.2 1(10.100.8.10, 225.1.8.4) 232.2.8.3 1(10.100.8.10, 225.1.8.5) 232.2.8.4 1(10.100.8.10, 225.1.8.6) 232.2.8.5 1(10.100.8.10, 225.1.8.7) 232.2.8.6 1(10.100.8.10, 225.1.8.8) 232.2.8.7 1(10.100.8.10, 225.1.8.9) 232.2.8.8 1(10.100.8.10, 225.1.8.10) 232.2.8.9 1Table 25 describes the significant fields shown in the display.
show ip pim bsr
To display the bootstrap router (BSR) information, use the show ip pim bsr command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] bsr
Syntax Description
vrf
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name assigned to the VRF.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The output includes elected BSR information and information about the locally configured candidate rendezvous point (RP) advertisement.
Examples
The following is sample output from the show ip pim bsr command:
Router# show ip pim bsrPIMv2 Bootstrap informationThis system is the Bootstrap Router (BSR)BSR address: 172.16.143.28Uptime: 04:37:59, BSR Priority: 4, Hash mask length: 30Next bootstrap message in 00:00:03 secondsNext Cand_RP_advertisement in 00:00:03 seconds.RP: 172.16.143.28(Ethernet0), Group acl: 6Table 26 describes the significant fields shown in the display.
Related Commands
show ip pim interface
To display information about interfaces configured for Protocol Independent Multicast (PIM), use the show ip pim interface command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] interface [interface-type interface-number] [df | count] [rp-address] [detail]
Syntax Description
Defaults
If no interface is specified, all interfaces are displayed.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command works only on interfaces that are configured for PIM.
Use the show ip pim interface count command to display switching counts for Multicast Distributed Switching (MDS) and other fast-switching statistics. For more information on MDS, refer to the "Configuring Multicast Distributed Switching" chapter in the Release 12.2 Cisco IOS Switching Services Configuration Guide.
Examples
The following is sample output from the show ip pim interface command:
Router# show ip pim interfaceAddress Interface Mode Neighbor Query DRCount Interval192.168.37.6 Ethernet0 Dense 2 30 192.168.37.33192.168.36.129 Ethernet1 Dense 2 30 192.168.36.13110.1.37.2 Tunnel0 Dense 1 30 224.0.0.0The following is sample output from the show ip pim interface command when an interface is specified:
Router# show ip pim interface Ethernet1/0Address Interface Ver/ Nbr Query DR DRMode Count Intvl Prior172.16.1.4 Ethernet1/0 v2/S 1 100 ms 1 172.16.1.4The following is sample output from the show ip pim interface command when the count keyword is specified:
Router# show ip pim interface countAddress Interface FS Mpackets In/Out172.16.121.35 Ethernet0 * 548305239/13744856172.16.121.35 Serial0.33 * 8256/67052912192.168.12.73 Serial0.1719 * 219444/862191The following is sample output from the show ip pim interface command when the count keyword is specified and IP MMLS is enabled. The example lists the PIM interfaces that are fast switched and process switched, and the packet counts for these interfaces. The flag "H" is added to interfaces where IP MMLS is enabled.
Router# show ip pim interface countStates: FS - Fast Switched, H - Hardware SwitchedAddress Interface FS Mpackets In/Out192.168.10.2 Vlan10 * H 40886/0192.168.11.2 Vlan11 * H 0/40554192.168.12.2 Vlan12 * H 0/40554192.168.23.2 Vlan23 * 0/0192.168.24.2 Vlan24 * 0/0The following are two sample outputs from the show ip pim interface command when the df keyword is specified:
Router# show ip pim interface dfInterface RP DF Winner Metric UptimeEthernet3/3 10.10.0.2 10.4.0.2 0 00:03:4910.10.0.3 10.4.0.3 0 00:01:4910.10.0.5 10.4.0.4 409600 00:01:49Ethernet3/4 10.10.0.2 10.5.0.2 0 00:03:4910.10.0.3 10.5.0.2 409600 00:02:3210.10.0.5 10.5.0.2 435200 00:02:16Loopback0 10.10.0.2 10.10.0.2 0 00:03:4910.10.0.3 10.10.0.2 409600 00:02:3210.10.0.5 10.10.0.2 435200 00:02:16Router# show ip pim interface Ethernet3/3 df 10.10.0.3Designated Forwarder election for Ethernet3/3, 10.4.0.2, RP 10.10.0.3State Non-DFOffer count is 0Current DF ip address 10.4.0.3DF winner up time 00:02:33Last winner metric preference 0Last winner metric 0Table 27 describes the significant fields shown in the displays.
The following is sample output from the show ip pim interface command with the detail keyword for Fast Ethernet interface 0/1:
Router# show ip pim interface fastethernet 0/1 detailFastEthernet0/1 is up, line protocol is upInternet address is 172.16.8.1/24Multicast switching:processMulticast packets in/out:0/0Multicast boundary:not setMulticast TTL threshold:0PIM:enabledPIM version:2, mode:densePIM DR:172.16.8.1 (this system)PIM neighbor count:0PIM Hello/Query interval:30 secondsPIM State-Refresh processing:enabledPIM State-Refresh origination:enabled, interval:60 secondsPIM NBMA mode:disabledPIM ATM multipoint signalling:disabledPIM domain border:disabledMulticast Tagswitching:disabledTable 28 describes the significant fields shown in the display.
Related Commands
show ip pim neighbor
To list the Protocol Independent Multicast (PIM) neighbors discovered by the Cisco IOS software, use the show ip pim neighbor command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] neighbor [interface-type interface-number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use this command to determine which routers on the LAN are configured for PIM.
Examples
The following is sample output from the show ip pim neighbor command:
Router# show ip pim neighborPIM Neighbor TableNeighbor Interface Uptime/Expires Ver DRAddress Prio/Mode172.16.1.3 Ethernet1/0 00:03:41/250 msec v2 1 / STable 29 describes the significant fields shown in the display.
Related Commands
show ip pim rp
To display active rendezvous points (RPs) that are cached with associated multicast routing entries, use the show ip pim rp command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] rp [mapping | metric] [rp-address]
Syntax Description
Defaults
If no RP is specified, all active RPs are displayed.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The Protocol Independent Multicast (PIM) version known for an RP influences the type of PIM register messages (Version 1 or Version 2) that the router sends when acting as the designated router (DR) for an active source. If an RP is statically configured, the PIM version of the RP is not set and the router, if required to send register packets, tries to send PIM Version 2 register packets. If sending PIM Version 2 packets fails, the router sends PIM Version 1 register packets.
The version of the RP displayed in the show ip pim rp command output can change according to the operations of the router. When the group is created, the version shown is for the RP in the RP mapping cache. Later, the version displayed by this command may change. If this router is acting as a DR for an active source, the router sends PIM register messages. The PIM register messages are answered by the RP with PIM register stop messages. The router learns from these PIM register stop messages the actual PIM version of the RP. Once the actual PIM version of the RP is learned, this command displays only this version. If the router is not acting as a DR for active sources on this group, then the version shown for the RP of the group does not change. In this case, the PIM version of the RP is irrelevant to the router because the version of the RP influences only the PIM register messages that this router must send.
When you enter the show ip pim rp mapping command, the version of the RP displayed in the output is determined only by the method through which an RP is learned. If the RP is learned from Auto-RP then the RP displayed is either "v1" or "v2, v1." If the RP is learned from a static RP definition, the RP version is undetermined and no RP version is displayed in the output. If the RP is learned from the BSR, the RP version displayed is "v2."
Examples
The following is sample output from the show ip pim rp command:
Router# show ip pim rpGroup:227.7.7.7, RP:10.10.0.2, v2, v1, next RP-reachable in 00:00:48The following is sample output from the show ip pim rp command when the mapping keyword is specified:
Router# show ip pim rp mappingPIM Group-to-RP MappingsThis system is an RP (Auto-RP)This system is an RP-mapping agentGroup(s) 227.0.0.0/8RP 10.10.0.2 (?), v2v1, bidirInfo source:10.10.0.2 (?), via Auto-RPUptime:00:01:42, expires:00:00:32Group(s) 228.0.0.0/8RP 10.10.0.3 (?), v2v1, bidirInfo source:10.10.0.3 (?), via Auto-RPUptime:00:01:26, expires:00:00:34Group(s) 229.0.0.0/8RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidirInfo source:10.10.0.5 (mcast1.cisco.com), via Auto-RPUptime:00:00:52, expires:00:00:37Group(s) (-)230.0.0.0/8RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidirInfo source:10.10.0.5 (mcast1.cisco.com), via Auto-RPUptime:00:00:52, expires:00:00:37The following is sample output from the show ip pim rp command when the metric keyword is specified:
Router# show ip pim rp metricRP Address Metric Pref Metric Flags RPF Type Interface10.10.0.2 0 0 L unicast Loopback010.10.0.3 90 409600 L unicast Ethernet3/310.10.0.5 90 435200 L unicast Ethernet3/3Table 30 describes the significant fields shown in the displays.
show ip pim rp-hash
To display which rendezvous point (RP) is being selected for a specified group, use the show ip pim rp-hash command in user EXEC or privileged EXEC mode.
show ip pim [vrf vrf-name] rp-hash {group-address | group-name}
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command displays which RP was selected for the group specified. It also shows whether this RP was selected by Auto-RP or the PIM Version 2 bootstrap mechanism.
Examples
The following is sample output from the show ip pim rp-hash command with the group address 239.1.1.1 specified:
Router# show ip pim rp-hash 239.1.1.1RP 172.16.24.12 (mt1-47a.cisco.com), v2Info source: 172.16.24.12 (mt1-47a.cisco.com), via bootstrapUptime: 05:15:33, expires: 00:02:01Table 31 describes the significant fields shown in the display.
show ip rpf
To display how IP multicast routing does Reverse Path Forwarding (RPF), use the show ip rpf command in privileged EXEC mode.
show ip rpf [vrf vrf-name] {source-address | source-name} [metric]
Syntax Description
Defaults
If no source is specified, all sources are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The router can reverse path forward from multiple routing tables (that is, the unicast routing table, Distance Vector Multicast Routing Protocol [DVMRP] routing table, or static multicast routes). This command tells you the source of the retrieved information.
Examples
The following is sample output from the show ip rpf command:
Router# show ip rpf 172.16.10.13RPF information for host1 (172.16.10.13)RPF interface: BRI0RPF neighbor: sj1.cisco.com (172.16.121.10)RPF route/mask: 172.16.0.0/255.255.0.0RPF type: unicastRPF recursion count: 0Doing distance-preferred lookups across tablesThe following is sample output from the show ip rpf command when the metric keyword is specified:
Router# show ip rpf 172.16.10.13 metricRPF information for host1.cisco.com (172.16.10.13)RPF interface: BRI0RPF neighbor: neighbor.cisco.com (172.16.121.10)RPF route/mask: 172.16.0.0/255.255.0.0RPF type: unicastRPF recursion count: 0Doing distance-preferred lookups across tablesMetric preference: 110Metric: 11Table 32 describes the significant fields shown in the display.
Glossary
BSR—bootstrap router. A router that provides a fault-tolerant, automated rendezvous point (RP) discovery and distribution mechanism. Thus, routers dynamically learn the group-to-RP mappings.
IGMP—Internet Group Management Protocol. Used by IP hosts to report their multicast group memberships to an adjacent multicast router.
multicast distribution tree (MDT)—Defines the path used by PE routers to send multicast data and control messages to every other PE router in the multicast domain.
multicast router—Router used to send IGMP query messages on their attached local networks. Host members of a multicast group respond to a query by sending IGMP reports noting the multicast groups to which they belong. The multicast router takes responsibility for forwarding multicast datagrams from one multicast group to all other networks that have members in the group.
PE—provider edge. Router that is part of a service provider's network and is connected to a customer edge (CE) router.
PIM—Protocol Independent Multicast. An IP multicast routing protocol used for routing multicast data packets to multicast groups. PIM is unicast routing protocol-independent and can operate in different modes such as sparse mode and dense mode.
PIM dense mode—One of the two PIM operational modes. PIM dense mode is data-driven and resembles typical multicast routing protocols. Packets are forwarded on all outgoing interfaces until pruning and truncation occurs. In dense mode, receivers are densely populated, and it is assumed that the downstream networks want to receive and will probably use the datagrams that are forwarded to them. The cost of using dense mode is its default flooding behavior. Sometimes called dense mode PIM or PIM DM.
PIM sparse mode—One of the two PIM operational modes. PIM sparse mode tries to constrain data distribution so that a minimal number of routers in the network receive it. Packets are sent only if they are explicitly requested at the RP (rendezvous point). In sparse mode, receivers are widely distributed, and the assumption is that downstream networks will not necessarily use the datagrams that are sent to them. The cost of using sparse mode is its reliance on the periodic refreshing of explicit join messages and its need for RPs. Sometimes called sparse mode PIM or PIM SM.
Protocol Independent Multicast—See PIM.
RP—rendezvous point. The multicast router that is the root of the PIM-SM shared multicast distribution tree.
RPF—Reverse Path Forwarding. Multicasting technique in which a multicast datagram is forwarded out of all but the receiving interface if the receiving interface is the one used to forward unicast datagrams to the source of the multicast datagram.
Note
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0601R)
Copyright © 2006 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)