IP Multicast Routing Commands

Syntax Description

type number

(Optional) Interface type and number.

Command Modes

EXEC

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command sends a Cisco Group Management Protocol (CGMP) Leave message with a group address of 0000.0000.0000 and a unicast address of 0000.0000.0000. This message instructs the switches to clear all group entries they have cached.

If an interface type and number are specified, the Leave message is sent only on that interface. Otherwise, it is sent on all CGMP-enabled interfaces.

Examples

The following example clears the CGMP cache:

clear ip cgmp

Related Commands

Command	Description
ip cgmp	Enables CGMP on an interface of a router connected to a Catalyst 5000 switch.

Syntax Description

*	Clears all routes from the DVMRP table.
route	Clears the longest matched route. Can be an IP address, a network number, or an IP DNS name.

Command Modes

EXEC

Command History

Release	Modification
11.0	This command was introduced.

Examples

The following example deletes route 10.1.1.1 from the Distance Vector Multicast Routing Protocol (DVMRP) routing table:

clear ip dvmrp route 10.1.1.1

Syntax Description

group-name	(Optional) Name of the multicast group, as defined in the DNS hosts table or with the ip host command.
group-address	(Optional) Address of the multicast group. This is a multicast IP address in four-part, dotted notation.
type number	(Optional) Interface type and number.

Defaults

When the command is used with no arguments, all entries are deleted from the IGMP cache.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

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, it 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:

clear ip igmp group 224.0.255.1

Related Commands

Command	Description
ip host	Defines a static host name-to-address mapping in the host cache.
show ip igmp groups	Displays the multicast groups that are directly connected to the router and that were learned through IGMP.
show ip igmp interface	Displays multicast-related information about an interface.

Syntax Description

*	Deletes all entries from the IP multicast routing table.
group	Can be either one of the following: Name of the multicast group, as defined in the DNS hosts table or with the ip host command. IP address of the multicast group. This is a multicast IP address in four-part, dotted notation.
source	(Optional) If you specify a group name or address, you can also specify a name or address of a multicast source that is transmitting to the group. A source does not need to be a member of the group.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example deletes all entries from the IP multicast routing table:

clear ip mroute *
 

The following example deletes from the IP multicast routing table all sources on the 10.3.0.0 subnet that are transmitting to the multicast group 224.2.205.42. Note that this example deletes all sources on network 10.3, not individual sources.

clear ip mroute 224.2.205.42 10.3.0.0

Related Commands

Command	Description
ip host	Defines a static host name-to-address mapping in the host cache.
show ip mroute	Displays the contents of the IP multicast routing table.

Syntax Description

rp-address

Clears only the entries related to the RP at this address. If this argument is omitted, the entire Auto-RP cache is cleared.

Command Modes

EXEC

Command History

Release	Modification
11.3	This command was introduced.

Examples

The following example deletes all entries from the Auto-RP cache:

clear ip pim auto-rp

Syntax Description

type number

(Optional) Interface type and number.

Command Modes

EXEC

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

If this command is used without an interface type and number, it clears all RTP header compression structures and statistics.

Examples

The following example clears RTP header compression structures and statistics for serial interface 0:

clear ip rtp header-compression serial 0

Related Commands

Command	Description
ip rtp header-compression	Enables RTP header compression.

Syntax Description

group-address	(Optional) Deletes all sessions associated with the IP group address.
"session-name"	(Optional) Deletes only the sdr cache entry with the specified name.

Command Modes

EXEC

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

If no arguments or keywords are used with this command, the system deletes the entire sdr cache.

Examples

The following example clears the sdr cache:

clear ip sdr

Related Commands

Command	Description
ip sdr cache-timeout	Limits how long a sdr cache entry stays active in the cache.
ip sdr listen	Enables the Cisco IOS software to listen to session directory advertisements.
show ip sdr	Displays the session directory cache.

Syntax Description

active	(Optional) Compresses all outgoing RTP packets. This is the default.
passive	(Optional) Compresses the outgoing RTP/UDP/IP header only if an incoming packet had a compressed header.

Defaults

Disabled.

If the command is configured, active is the default keyword.

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

When this command is used on the physical interface, all the interface maps inherit the command; that is, all maps will perform IP/UDP/RTP header compression.

Examples

The following example enables RTP header compression for all Frame Relay maps on a physical interface:

frame-relay ip rtp header-compression

Related Commands

Command	Description
show frame-relay ip rtp header-compression	Displays RTP header compression statistics for Frame Relay.

Syntax Description

ip-address	IP address of the destination or next hop.
dlci	DLCI number.
broadcast	(Optional) Forwards broadcasts to the specified IP address.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Examples

The following example enables both RTP and TCP header compression on serial interface 1:

interface serial 1
 encapsulation frame-relay
 ip address 131.108.175.110 255.255.255.0
 frame-relay map ip 131.108.175.220 180 compress

Related Commands

Command	Description
show frame-relay ip rtp header-compression	Displays RTP header compression statistics for Frame Relay.

Syntax Description

ip-address	IP address of the destination or next hop.
dlci	DLCI number.
active	(Optional) All outgoing RTP packets are compressed. This is the default.
passive	(Optional) Compresses the outgoing RTP/UDP/IP header only if an incoming packet had a compressed header.

Defaults

Disabled.

If the command is configured, active is the default keyword.

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

When this command is configured, the specified maps inherit RTP header compression. You can have multiple Frame Relay maps, with and without RTP header compression.

Examples

The following example enables RTP header compression on serial interface 1:

interface serial 1
 encapsulation frame-relay
 ip address 131.108.175.110 255.255.255.0
 frame-relay map ip 131.108.175.220 180 rtp header-compression

Related Commands

Command	Description
show frame-relay ip rtp header-compression	Displays RTP header compression statistics for Frame Relay.

Syntax Description

proxy

(Optional) Enables CGMP and the CGMP proxy function.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

When enabled on an interface, this command triggers a CGMP Join message. This command should be used only on 802 media (that is, Ethernet, FDDI or Token Ring) or ATM. When a no ip cgmp command is issued, a triggered CGMP Leave message is sent for the router's MAC address on the interface for group 0000.0000.0000 (all groups). CGMP can run on an interface only if PIM is configured on the same interface.

A Cisco router will send CGMP Join messages in response to receiving IGMP reports from IGMP-capable members. Only the CGMP querier Cisco router sends these CGMP Join messages on behalf of hosts.

When the proxy keyword is specified, the CGMP proxy function is also enabled. That is, any router that is not CGMP-capable will be advertised by the proxy router. The proxy router advertises the existence of other non CGMP-capable routers by sending a CGMP Join message with the non-CGMP-capable router's MAC address and a group address of 0000.0000.0000.

Initially supported is DVMRP proxying. If a DVMRP Report is received from a router that is not a PIM router, a Cisco IGMP querier will advertise the MAC address of the DVMRP router in a CGMP Join with group address 0000.0000.0000.

To perform CGMP proxy, a Cisco router must be the IGMP querier. If you configure the ip cgmp proxy command, you must manipulate the IP addresses so that a Cisco router will be the IGMP querier, which might be the highest or lowest IP address, depending on which version of IGMP is being run on the network. An IGMP Version 2 querier is selected based on the lowest IP addressed router on the interface. An IGMP Version 1 querier is selected based on the multicast routing protocol used on the interface.

When multiple Cisco routers are connected to a switched network and the ip cgmp [proxy] command is needed, it is recommended that all of them be configured in the following manner:

• With the same CGMP option.

• To have precedence of becoming IGMP querier over non-Cisco routers.

Examples

The following example enables CGMP:

ip cgmp
 

The following example enables CGMP and CGMP proxy:

ip cgmp proxy

Syntax Description

access-list-number	Number of a standard IP access list. This can be a number from 0 to 99. A value of 0 means that all sources are accepted with the configured distance.
distance	(Optional) Administrative distance to the destination.
neighbor-list access-list number	Number of a neighbor list. DVMRP reports are accepted only by those neighbors on the list.

Defaults

All destination reports are accepted with a distance of 0. Default settings accept reports from all neighbors.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.
11.2	The neighbor-list keyword and access-list-number argument were added.

Usage Guidelines

Any sources that match the access list are stored in the DVMRP routing table with distance.

The distance is used to compare with the same source in the unicast routing table. The route with the lower distance (either the route in the unicast routing table or that in the DVMRP routing table) takes precedence when computing the Reverse Path Forwarding (RPF) interface for a source of a multicast packet.

 ip dvmrp accept-filter 1 100
access-list 1 permit 0.0.0.0 255.255.255.255

Examples

The following example applies access list 57 to the interface and sets a distance of 4:

access-list 57 permit 131.108.0.0 0.0.255.255
access-list 57 permit 198.92.37.0 0.0.0.255
access-list 57 deny 0.0.0.0 255.255.255.255
 ip dvmrp accept-filter 57 4

Related Commands

Command	Description
distance (IP)	Defines an administrative distance.
ip dvmrp metric	Configures the metric associated with a set of destinations for DVMRP reports.
show ip dvmrp route	Displays the contents of the DVMRP routing table.
tunnel mode	Sets the encapsulation mode for the tunnel interface.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

DVMRP auto summarization occurs when a unicast subnet route is collapsed into a classful network number route. This occurs when the subnet is a different network number than the IP address of the interface (or tunnel) over which the advertisement is sent. If the interface is unnumbered, the network number of the numbered interface the unnumbered interface points to is compared.

You might want to disable this feature if the information you want to send using the ip dvmrp summary-address command is the same as the information that would be sent using DVMRP auto-summarization.

Examples

The following example disables DVMRP auto summarization:

no ip dvmrp auto-summary

Related Commands

Command	Description
ip dvmrp summary-address	Configures a DVMRP summary address to be advertised out the interface.

Syntax Description

originate	Other routes more specific than 0.0.0.0 can also be advertised.
only	No DVMRP routes other than 0.0.0.0 are advertised.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Syntax Description

metric	Metric associated with a set of destinations for DVMRP reports. It can be a value from 0 to 32. A value of 0 means that the route is not advertised. A value of 32 is equivalent to infinity (unreachable).
list access-list-number	(Optional) Number of an access list. If you specify this argument, only the multicast destinations that match the access list are reported with the configured metric. Any destinations not advertised because of split horizon do not use the configured metric.
protocol	(Optional) Name of unicast routing protocol, such as bgp, eigrp, igrp, isis, ospf, rip, or static or dvmrp. If you specify these arguments, only routes learned by the specified routing protocol are advertised in DVMRP report messages.
process-id	(Optional) Process ID number of the unicast routing protocol.
dvmrp	(Optional) Allows routes from the DVMRP routing table to be advertised with the configured metric or filtered.
route-map map-name	Unicast routes are subject to route-map conditions before being injected into DVMRP. Route-maps cannot be used for DVMRP routes.

Defaults

No metric is preconfigured. Only directly connected subnets and networks are advertised to neighboring DVMRP routers.

Command Modes

Interface configuration

Command History

Release	Modification
10.2	This command was introduced.
11.1	The route-map keyword was added.

Usage Guidelines

When Protocol Independent Multicast (PIM) is configured on an interface and DVMRP neighbors are discovered, the Cisco IOS software sends DVMRP report messages for directly connected networks. The ip dvmrp metric command enables DVMRP report messages for multicast destinations that match the access list. Usually, the metric for these routes is 1. Under certain circumstances, you might want to tailor the metric used for various unicast routes. This command lets you configure the metric associated with a set of destinations for Report messages sent out this interface.

You can use the access-list-number argument in conjunction with the protocol process-id arguments to selectively list the destinations learned from a given routing protocol.

To display DVMRP activity, use the debug ip dvmrp command.

Examples

The following example connects a PIM cloud to a DVMRP cloud. Access list 1 permits the sending of DVMRP reports to the DVMRP routers advertising all sources in the 198.92.35.0 network with a metric of 1. Access list 2 permits all other destinations, but the metric of 0 means that no DVMRP reports are sent for these destinations.

access-list 1 permit 198.92.35.0 0.0.0.255
access-list 1 deny 0.0.0.0 255.255.255.255
access-list 2 permit 0.0.0.0 255.255.255.255
interface tunnel 0
 ip dvmrp metric 1 list 1
 ip dvmrp metric 0 list 2

Related Commands

Command	Description
ip dvmrp accept-filter	Configures an acceptance filter for incoming DVMRP reports.

Syntax Description

in	(Optional) The increment value is added to incoming DVMRP reports and is reported in mrinfo replies. The default for in is 1.
out	(Optional) The increment value is added to outgoing DVMRP reports for routes from the DVMRP routing table. The default for out is 0.
increment	Value added to the metric of a DVMRP route advertised in a Report message.

Defaults

If neither in nor out is specified, in is the default.

The default for in is 1.

The default for out is 0.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

Use this command to influence which routes are used, as you prefer. The DVMRP metric is in hop count.

Examples

The following example adds 10 to the incoming DVMRP reports:

ip dvmrp metric-offset 10

Syntax Description

milliseconds	Number of milliseconds that elapse between transmissions of a set of DVMRP report packets. The number of packets in the set is determined by the burst argument. The default number of milliseconds is 100 milliseconds.
burst	(Optional) The number of packets in the set being transmitted. The default is 2 packets.

Defaults

milliseconds is 100 milliseconds

burst is 2 packets

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

The delay is the number of milliseconds that elapse between transmissions of sets of packets that constitute a report. The number of packets in the set is determined by the burst value.

You might want to change the default values, depending on the CPU and buffering of the mrouted machine.

Examples

The following example sets the interpacket delay to 200 milliseconds and the burst size to 3 packets. Therefore, at the periodic DVMRP report interval, if 6 packets are built, 3 packets will be sent, then a delay of 200 milliseconds occurs, then the next 3 packets are sent.

ip dvmrp output-report-delay 200 3

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

By default, the router accepts all DVMRP neighbors as peers, regardless of their DVMRP capability or lack thereof.

Use this command to prevent a router from peering with a DVMRP neighbor if that neighbor does not support DVMRP pruning or grafting. If the router receives a DVMRP Probe or Report message without the Prune-Capable flag set, the router logs a syslog message and discards the message.

Note that this command prevents peering with neighbors only. If there are any non-pruning routers multiple hops away (downstream toward potential receivers) that are not rejected, then a non-pruning DVMRP network might still exist.

Examples

The following example configures the router not to peer with DVMRP neighbors that do not support pruning or grafting:

ip dvmrp reject-non-pruners

Syntax Description

route-count

Number of routes allowed before a syslog message is triggered. The default is 10,000 routes.

Defaults

10,000 routes

Command Modes

Global configuration

Command History

Release	Modification
10.2	This command was introduced.

Usage Guidelines

This command configures how many DVMRP routes are accepted on each interface within an approximate one-minute interval before a syslog message is issued, warning that there might be a route surge occurring. The warning is typically used to detect quickly when people have misconfigured their routers to inject a large number of routes into the MBONE.

The show ip igmp interface command displays a running count of routes. When the count is exceeded, an "*** ALERT ***" is appended to the line.

Examples

The following example lowers the threshold to 8000 routes:

ip dvmrp routehog-notification 8000

Related Commands

Command	Description
show ip igmp interface	Displays multicast-related information about an interface.

Syntax Description

count

Number of DVMRP routes that can be advertised. The default is 7000 routes.

Defaults

7000 routes

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

Interfaces enabled to run DVMRP include a DVMRP tunnel, an interface where a DVMRP neighbor has been discovered, or an interface configured to run the ip dvmrp unicast-routingcommand.

The ip dvmrp route-limit command is automatically generated to the configuration file when at least one interface is enabled for multicast routing. This command is necessary to prevent misconfigured ip dvmrp metric commands from causing massive route injection into the multicast backbone (MBONE).

Examples

The following example changes the limit to 5000 DVMRP routes allowed to be advertised:

ip dvmrp route-limit 5000

Related Commands

Command	Description
ip dvmrp unicast-routing	Enables DVMRP unicast routing on an interface.

Syntax Description

address	Summary IP address that is advertised instead of the more specific route.
mask	Mask on the summary IP address.
metric value	(Optional) Metric that is advertised with the summary address. The default is 1.

Defaults

metric value is 1

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

If there is at least a single, more specific route in the unicast routing table that matches the specified address and mask arguments, the summary is advertised. Routes in the DVMRP routing table are not candidates for summarization.

When the metric keyword is specified, the summary is advertised with that metric value.

Multiple summary address can be configured on an interface. When multiple overlapping summary addresses are configured on an interface, the one with the longest mask takes preference.

Examples

The following example configures the DVMRP summary address 171.69.0.0 to be advertised out the interface:

ip dvmrp summary-address 171.69.0.0 255.255.0.0 metric 1

Related Commands

Command	Description
ip dvmrp auto-summary	Enables DVMRP auto summarization if it was disabled.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Enabling DVMRP unicast routing means that routes in DVMRP Report messages are cached by the router in a DVMRP routing table. When PIM is running, these routes may get preference over routes in the unicast routing table. This allows PIM to run on the MBONE topology when it is different from the unicast topology.

DVMRP unicast routing can run on all interfaces, including GRE tunnels. On DVMRP tunnels, it runs by virtue of DVMRP multicast routing. This command does not enable DVMRP multicast routing among Cisco routers. However, if there is a DVMRP-capable multicast router, the Cisco router will do PIM/DVMRP multicast routing interaction.

Examples

The following example enables DVMRP unicast routing:

ip dvmrp unicast-routing

Related Commands

Command	Description
ip dvmrp route-limit	Changes the limit on the number of DVMRP routes that can be advertised over an interface enabled to run DVMRP.

Syntax Description

access-list-number	Number of a standard IP access list. This can be a number from 1 to 99.
version	Changes IGMP version. Default is version 2.

Defaults

All groups are allowed on an interface.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

In the following example, hosts serviced by Ethernet interface 0 can join the group 225.2.2.2 only:

access-list 1 225.2.2.2 0.0.0.0
interface ethernet 0
 ip igmp access-group 1

Related Commands

Command	Description
ip igmp join-group	Causes the router to join a multicast group.

Syntax Description

ip-address

IP address to which IGMP Host Reports and Leave messages are forwarded. Specify the IP address of an interface on the central router.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.2 F	This command was introduced.

Usage Guidelines

Examples

The following example enables stub multicast routing on Router A, which has an outgoing interface with IP address 10.0.0.1. Router B is a central router with an incoming interface with address 10.0.0.2. Access list 1 filters PIM messages from the source (stub Router A).

Router A

ip multicast-routing
 ip pim dense-mode
 ip igmp helper-address 10.0.0.2

Router B

ip multicast-routing
 ip pim dense-mode : or ip pim sparse-mode
 ip pim neighbor-filter 1
access-list 1 deny 10.0.0.1

Related Commands

Command	Description
ip pim neighbor-filter	Prevents a router from participating in PIM (for example, to configure stub multicast routing).

Syntax Description

group-address

Address of the multicast group. This is a multicast IP address in four-part, dotted notation.

Defaults

No multicast group memberships are predefined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

IP packets that are addressed to the group address are passed to the IP client process in the Cisco IOS software.

If all the multicast-capable routers and access servers that you administer are members of a multicast group, pinging that group causes all routers to respond. This can be a useful administrative and debugging tool.

Another reason to have a router join a multicast group is when other hosts on the network have a bug in IGRP that prevents them from correctly answering IGMP queries. Having the router join the multicast group causes upstream routers to maintain multicast routing table information for that group and keep the paths for that group active.

Examples

In the following example, the router joins multicast group 225.2.2.2:

ip igmp join-group 225.2.2.2

Related Commands

Command	Description
ip igmp access-group	Controls the multicast groups that hosts on the subnet serviced by an interface can join.
ping (privileged)	Diagnoses basic network connectivity on Apollo, AppleTalk, CLNS, DECnet, IP, Novell IPX, VINES, or XNS networks.
ping (user)	Diagnoses basic network connectivity on AppleTalk, CLNS, IP, Novell, Apollo, VINES, DECnet, or XNS networks.

Syntax Description

seconds

Frequency, in seconds, at which to send IGMP host-query messages. It can be a number from 0 to 65535. The default is 60 seconds.

Defaults

60 seconds

Command Modes

Interface configuration

Command History

Release	Modification
10.2	This command was introduced.

Usage Guidelines

Multicast routers send host membership query messages (host-query messages) to discover which multicast groups have members on the router's attached networks. Hosts respond with IGMP report messages indicating that they wish to receive multicast packets for specific groups (that is, indicating that the host wants to become a member of the group). Host-query messages are addressed to the all-hosts multicast group, which has the address 224.0.0.1, and has an IP TTL value of 1.

The designated router for a LAN is the only router that sends IGMP host-query messages.

• For IGMP Version 1, the designated router is elected according to the multicast routing protocol that runs on the LAN.

• For IGMP Version 2, the designated querier is the lowest IP-addressed multicast router on the subnet.

If the router hears no queries for the timeout period (controlled by the ip igmp query-timeout command), it becomes the querier.

Caution Changing this value may severely impact multicast forwarding.

Examples

The following example changes the frequency at which the designated router sends IGMP host-query messages to 2 minutes:

interface tunnel 0
 ip igmp query-interval 120

Related Commands

Command	Description
ip pim query-interval	Configures the frequency of PIM router-query messages.
show ip igmp groups	Displays the multicast groups that are directly connected to the router and that were learned through IGMP.

Syntax Description

seconds

Maximum response time, in seconds, advertised in IGMP queries. The default value is 10 seconds.

Defaults

10 seconds

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command is valid only when IGMP Version 2 is running.

This command controls how long the responder has to respond to an IGMP Query message before the router deletes the group. Configuring a value less than 10 seconds enables the router to prune groups faster.

Note   If the hosts do not respond fast enough, they might be pruned when you don't want them to be. Therefore, the hosts must know to respond faster than 10 seconds (or the value you configure).

Examples

The following example configures a maximum response time of 8 seconds:

ip igmp query-max-response-time 8

Related Commands

Command	Description
ip pim query-interval	Configures the frequency of PIM router-query messages.
show ip igmp groups	Displays the multicast groups that are directly connected to the router and that were learned through IGMP.

Syntax Description

seconds

Number of seconds that the router waits after the previous querier has stopped querying and before it takes over as the querier.

Defaults

2 times the query interval

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command requires IGMP Version 2.

By default, the router waits twice the query interval specified by the ip igmp query-interval command, after which, if it has heard no queries, it becomes the querier. By default, the ip igmp query-interval defaults to 30 seconds, which means the ip igmp query-timeout defaults to 60 seconds.

Examples

The following example configures the router to wait 30 seconds from the time it received the last query before it takes over as the querier for the interface:

ip igmp query-timeout 30

Related Commands

Command	Description
ip igmp query-interval	Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.

Syntax Description

group-address

IP multicast group address of a group that the router is a member of.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

When this command is configured, packets to the group are fast-switched out this interface, provided that packets were received on the correct RPF interface. This is unlike configuring the ip igmp join-group command, which also causes packets to be passed up to the process level.

If the ip igmp join-group command is configured for the same group address as the ip igmp static-group command, the ip igmp join-group command takes precedence, and the group behaves like a locally joined group.

Examples

The following example configures 239.100.100.101 on Ethernet interface 0:

interface ethernet 0
 ip igmp static-group 239.100.100.101

Related Commands

Command	Description
ip igmp join-group	Causes the router to join a multicast group.

Syntax Description

2	IGMP Version 2.
1	IGMP Version 1.

Defaults

Version 2

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

All systems on the subnet must support the same version. The router does not automatically detect Version 1 systems and switch to Version 1, as did prior releases of the Cisco IOS software.

Configure Version 1 if your hosts do not support Version 2.

Syntax Description

source	IP address of the multicast source.
mask	Mask on the IP address of the multicast source.
protocol	(Optional) Unicast routing protocol that you are using.
as-number	(Optional) Autonomous system number of the routing protocol you are using, if applicable.
rpf-address	Incoming interface for the mroute. If the Reverse Path Forwarding address rpf-address is a Protocol Independent Multicast (PIM) neighbor, PIM Joins, Grafts, and Prunes are sent to it. The rpf-address argument can be a host IP address of a directly connected system or a network/subnet number. When it is a route, a recursive lookup is done from the unicast routing table to find a directly connected system. If the rpf-address argument is not specified, the interface type number is used as the incoming interface.
type number	Interface type and number for the mroute.
distance	(Optional) Determines whether a unicast route, a DVMRP route, or a static mroute should be used for the RPF lookup. The lower distances have better preference. If the static mroute has the same distance as the other two RPF sources, the static mroute will take precedence. The default is 0.

Defaults

distance: 0

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

This command allows you to statically configure where multicast sources are located (even though the unicast routing table says 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 0.0.0.0 255.255.255.255 tunnel0
 

The following example configures all specific sources within a network number are reachable through 171.68.10.13:

ip mroute 171.69.0.0 255.255.0.0 171.68.10.13
 

The following example causes this multicast static route to take effect if the unicast routes for any given destination go away:

ip mroute 0.0.0.0 255.255.255.255 serial0 200

Syntax Description

access-list-number

Standard IP access list number identifying an access list that controls the range of group addresses affected by the boundary.

Defaults

There is no boundary.

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

You might set up a boundary to keep multicast packets from being forwarded.

Examples

The following example sets up a boundary for all administratively scoped addresses:

access-list 1 deny 239.0.0.0 0.255.255.255
access-list 1 permit 224.0.0.0 15.255.255.255
interface ethernet 0
 ip multicast boundary 1

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

You can store IP multicast packet headers in a cache and then display them to determine the following:

• Who is sending IP multicast packets to what groups

• Inter-packet delay

• Duplicate IP multicast packets (if any)

• Multicast forwarding loops in your network (if any)

• Scope of the group

• UDP port numbers

• Packet length

Note   This feature allocates a circular buffer of approximately 32 kilobytes. Do not configure this feature if you are low on memory.

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-headers

Related Commands

Command	Description
show ip mpacket	Displays the contents of the circular cache-header buffer.

Syntax Description

group-address	Multicast group address of traffic to be converted to broadcast traffic. Use this with the broadcast-address.
broadcast	Specifies the traffic is being converted from broadcast to multicast. Use this with the multicast-address.
broadcast-address	Address to which broadcast traffic is sent. Use this with the group-address.
multicast-address	Specifies the IP multicast address to which the converted traffic is directed. Use this with the broadcast keyword.
extended-access-list-number	IP extended access list that controls which broadcast packets are translated, based on the UDP port number.

Defaults

No conversion between broadcast and multicast occurs.

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

When a multicast-capable internetwork is between two broadcast-only internetworks, you can convert broadcast traffic to multicast at the first hop router, and convert it back to broadcast at the last hop router before delivering the packets to the broadcast clients. Thus, you can take advantage of the multicast capability of the intermediate multicast internetwork. This feature prevents unnecessary replication at the intermediate routers and allows multicast fast switching in the multicast internetwork.

You must configure the ip directed-broadcast command on any interface where the ip multicast helper-map command is configured.

Note   On the last hop router, the ip multicast helper-map command introduces the ip igmp join-group command on that interface. That command must remain for this feature to work. If you remove the ip igmp join-group command, the feature fails. You can move the ip igmp join-group command to another interface on the same router.

Examples

The following example illustrates how a helper address on two routers converts from broadcast to multicast and back to broadcast.

The configuration on the first hop router converts a broadcast stream arriving at incoming interface Ethernet interface 0 destined to UDP port 4000 to a multicast stream. The access list denies other traffic from being forwarded into the multicast cloud. The traffic is sent to group address 224.5.5.5. Because fast switching does not perform such a conversion, the ip forward-protocol command causes the proper process level to perform the conversion.

The configuration on the last hop router converts the multicast stream at incoming interface Ethernet interface 1 back to broadcast. Again, all multicast traffic emerging from the multicast cloud is not supposed to be converted to broadcast, only the traffic destined for UDP port 4000.

First Hop Router

interface ethernet 0
 ip directed-broadcast
 ip multicast helper-map broadcast 224.5.5.5 120
 ip pim dense-mode
!
access-list 120 permit any any udp 4000
access-list 120 deny any any udp
 ip forward-protocol udp 4000

Last Hop Router

interface ethernet 1
 ip directed-broadcast
 ip multicast helper-map 224.5.5.5 178.21.34.255 135
 ip pim dense-mode
!
access-list 135 permit any any udp 4000
access-list 135 deny any any udp
 ip forward-protocol udp 4000

Related Commands

Command	Description
ip directed-broadcast	Enables the translation of directed broadcast to physical broadcasts.
ip forward-protocol	Specifies which protocols and ports the router forwards when forwarding broadcast packets.

Syntax Description

in	Only packets at the rate of kbps or slower are accepted on the interface.
out	Only a maximum of kbps will be transmitted on the interface.
video	(Optional) Rate limiting is performed based on the UDP port number used by video traffic. Video traffic is identified by consulting the sdr cache.
whiteboard	(Optional) Rate limiting is performed based on the UDP port number used by whiteboard traffic. Whiteboard traffic is identified by consulting the sdr cache.
group-list access-list	(Optional) Specifies the access list number that controls which multicast groups are subject to the rate limit.
source-list access-list	(Optional) Specifies the access list number that controls which senders are subject to the rate limit.
kbps	Kilobits-per-second transmission rate. Any packets sent at greater than this value are silently discarded. If this command is configured, the default value is 0, meaning that no traffic is permitted. Therefore, set this to a positive value if you use this command.

Defaults

If this command is not configured, there is no rate limit.

If this command is configured, kbps defaults to 0, meaning that no traffic is permitted.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

If a router receives a packet and in the last second the user has sent over the limit, the packet is dropped; otherwise, it is forwarded.

For the video or whiteboard keyword to work, the ip sdr listen command must be enabled so the port number can be obtained from the sdr cache. If the ip sdr listen command is not enabled, or the group address is not in the sdr cache, no rate-limiting is done for the group.

Examples

In the following example, packets to any group from sources in network 171.69.0.0 will have their packets rate-limited to 64 kbps:

interface serial 0
 ip multicast rate-limit out group-list 1 source-list 2 64
access-list 1 permit 0.0.0.0 255.255.255.255
access-list 2 permit 171.69.0.0 0.0.255.255

Related Commands

Command	Description
ip sdr listen	Enables the Cisco IOS software to listen to session directory advertisements.

Syntax Description

ttl-value

Time-to-live value, in hops. It can be a value from 0 to 255. The default value is 0, which means that all multicast packets are forwarded out the interface.

Defaults

0, which means that all multicast packets are forwarded out the interface.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

Only multicast packets with a TTL value greater than the threshold are forwarded out the interface.

You should configure the TTL threshold only on border routers. Conversely, routers on which you configure a TTL threshold value automatically become border routers.

This command replaces the ip multicast-threshold command, which is obsolete.

Examples

The following example sets the TTL threshold on a border router to 200, which is a very high value. This means that multicast packets must have a TTL greater than 200 in order to be forwarded out this interface. Multicast applications generally set this value well below 200. Therefore, setting a value of 200 means that no packets will be forwarded out the interface.

interface tunnel 0
 ip multicast ttl-threshold 200

Syntax Description

This command has no arguments or keywords.

Defaults

IP multicast address are mapped to the MAC-layer address 0xFFFF.FFFF.FFFF.

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command is accepted only on a Token Ring interface.

Neighboring devices on the Token Ring on which this feature is used should also use the same functional address for IP multicast traffic.

Because there are a limited number of Token Ring functional addresses, it is possible there are other protocols assigned to the Token Ring functional address 0xc000.0004.0000. Therefore, not every frame sent to the functional address is necessarily an IP multicast frame.

Examples

The following example configures any IP multicast packets going out Token Ring interface 0 to be mapped to MAC address 0xc000.0004.0000:

interface token 0
 ip address 1.1.1.1 255.255.255.0
 ip pim dense-mode
 ip multicast use-functional

Syntax Description

dense-mode	Enables dense mode of operation.
sparse-mode	Enables sparse mode of operation.
sparse-dense-mode	The interface is treated in the mode in which the group operates.

Defaults

IP multicast routing is disabled on all interfaces.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.
11.1	The sparse-dense-mode keyword was added.

Usage Guidelines

Enabling PIM on an interface also enables Internet Group Management Protocol (IGMP) operation on that interface. An interface can be configured to be in dense mode, sparse mode, or sparse-dense mode. The mode describes how the Cisco IOS software populates its multicast routing table and how the software forwards multicast packets it receives from its directly connected LANs. In populating the multicast routing table, dense-mode interfaces are always added to the table. Sparse-mode interfaces are added to the table only when periodic join messages are received from downstream routers, or there is a directly connected member on the interface.

Dense Mode

Initially, a dense-mode interface forwards multicast packets until the router determines that there are group members or downstream routers, or until a prune message is received from a downstream router. Then, the dense-mode interface periodically forwards multicast packets out the interface until the same conditions occur. Dense mode assumes that there are multicast group members present. Dense-mode routers never send a join message. They do send prune messages as soon as they determine they have no members or downstream PIM routers. A dense-mode interface is subject to multicast flooding by default.

Sparse Mode

A sparse-mode interface is used for multicast forwarding only if a join message is received from a downstream router or if there are group members directly connected to the interface. Sparse mode assumes that there are no other multicast group members present. When sparse-mode routers want to join the shared path, they periodically send join messages toward the rendezvous point (RP). When sparse-mode routers want to join the source path, they periodically send join messages toward the source; they also send periodic prune messages toward to RP to prune the shared path.

Sparse-Dense Mode

An alternative to choosing just dense mode or just sparse mode is to run PIM in a single region in sparse mode for some groups and dense mode for other groups.

In sparse-dense mode, if the group is in dense mode, the interface will be treated as dense mode. If the group is in sparse mode, the interface will be treated in sparse mode. The group is "sparse" if the router knows about an RP for that group.

When an interface is treated in dense mode, it is populated in a multicast routing table's outgoing integrated list when either

• There are members or DVMRP neighbors on the interface.

• Any of the PIM neighbors on the interface have not pruned for the group.

When an interface is treated in sparse mode, it is populated in a multicast routing table's outgoing interface when either of the following is true:

• There are members or DVMRP neighbors on the interface.

• A PIM neighbor on the interface has received an explicit Join.

Examples

The following example enables sparse-mode PIM on tunnel interface 0 and sets the address of the RP router to 226.0.0.8:

ip pim rp-address 226.0.0.8
interface tunnel 0
 ip pim sparse-mode
 

The following example enable dense-mode PIM on Ethernet interface 1:

interface ethernet 1
 ip pim dense-mode
 

The following example enables sparse-dense mode:

interface ethernet 1
 ip pim sparse-dense-mode

Related Commands

Command	Description
ip multicast-routing	Enables IP multicast routing or multicast distributed switching.
ip pim rp-address	Configures the address of a PIM RP for a particular group.
show ip pim interface	Displays information about interfaces configured for PIM.

Syntax Description

address	RP address of the RP allowed to send Join messages to groups in the range specified by the group access list.
auto-rp	Join and Register messages are accepted only for RPs that are in the Auto-RP cache.
group-access-list-number	(Optional) Access list that defines which groups are subject to the check.

Defaults

Disabled, so all Join messages and Prune messages are processed.

Command Modes

Global configuration

Command History

Release	Modification
10.2	This command was introduced.

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 address argument is one of the system's addresses, 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 100.1.1.1 for the multicast group 224.2.2.2:

ip pim accept-rp 100.1.1.1 3
access-list 3 permit 224.2.2.2

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.3 T	This command was introduced.

Usage Guidelines

When this command is configured on an interface, no bootstrap message can pass through this border in either direction. This command effectively partitions the network into regions using different bootstrap routers. Other PIM messages can pass the domain border.

Note   This command does not set up multicast boundaries. It only sets up a PIM bootstrap message boundary.

Examples

The following example configures the interface to be the PIM domain border:

interface ethernet 1
ip pim border

Related Commands

Command	Description
ip pim bsr-candidate	Configures the router to announce its candidacy as a BSR.

Syntax Description

type number	Interface type and number on this router from which the bootstrap router address is derived, to make it a candidate. This interface must be enabled with PIM.
hash-mask-length	Length of a mask (32 bits maximum) that is to be "ANDed" with the group address before the hash function is called. All groups with the same seed hash (correspond) to the same RP. For example, if this value is 24, only the first 24 bits of the group addresses matter. This fact allows you to get one RP for multiple groups.
priority	(Optional) Integer from 0 to 255. The bootstrap router with the larger priority is preferred. If the priority values are the same, the router with the larger IP address is the bootstrap router. The default value is 0.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release	Modification
11.3 T	This command was introduced.

Usage Guidelines

This command causes the router to send bootstrap messages to all its Protocol Independent Multicast (PIM) neighbors, with the designated interface's address 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 address or better, 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 another candidate BSR's message saying 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 router's IP address on Ethernet interface 0 to be a candidate bootstrap router with priority of 10:

ip pim bsr-candidate ethernet 0 10

Related Commands

Command	Description
ip pim border	Configures the interface to be the PIM domain border.
ip pim rp-candidate	Configures the router to advertise itself as a PIM Version 2 candidate RP to the BSR.
ip pim send-rp-discovery	Configures the router to be an RP-mapping agent.
show ip pim bsr	Displays the BSR information.
show ip pim rp	Displays active RPs that are cached with associated multicast routing entries.

Syntax Description

seconds

Interval, in seconds, at which periodic sparse-mode Join and Prune PIM messages are sent. It can be a number from 1 to 65535. The default is 60 seconds.

Defaults

60 seconds

Command Modes

Global configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The join-and-prune message interval should be the same for all routers in the network.

A router is pruned from a group if a Join message is not heard from it in three times the message interval specified by the seconds argument. By default, this is 3 minutes.

Note   Changing this value may severely impact multicast forwarding.

Examples

The following example changes the PIM message interval to 90 seconds:

ip pim message-interval 90

Related Commands

Command	Description
ip igmp query-interval	Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
ip pim query-interval	Configures the frequency of PIM router-query messages.

Syntax Description

pps	Rate, in packets per second, below which a VC is eligible for idling. The default value is 0, which means all VCs are eligible for idling. The range is from 0 to 4294967295.

Defaults

0 pps, which indicates all VCs are eligible for idling.

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

This command applies to an ATM interface only and also requires IP PIM sparse mode.

An idling policy uses the ip pim vc-count number command to limit the number of VCs created by PIM. When the router stays at or below this number, no idling policy is in effect. When the next VC to be opened will exceed the number, an idling policy is exercised. Any virtual circuits with a traffic rate lower than the ip pim minimum-vc-rate command are subject to the idling policy, which is described in the section "Limit the Number of Virtual Circuits" in the "Configuring IP Multicast Routing" chapter of the Cisco IOS IP and IP Routing Configuration Guide.

Examples

The following example configures a minimum rate of 2500 pps over a VC, below which the VC is eligible for idling:

ip pim minimum-vc-rate 2500

Related Commands

Command	Description
ip pim vc-count	Changes the maximum number of virtual circuits that PIM can open.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled. All multicast traffic goes to the static map multipoint VC as long as the atm multipoint-signalling command is configured.

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

This command is accepted only on an ATM interface. It allows optimal multicast trees to be built down to ATM switch granularity. This command can enhance router performance and link utilization because packets are not replicated and sent multiple times over the ATM interface.

Examples

The following example enables PIM to open ATM multipoint switched virtual circuits for each multicast group that is joined:

ip pim multipoint-signalling

Related Commands

Command	Description
atm multipoint-signalling	Enables point-to-multipoint signalling to the ATM switch.
ip pim minimum-vc-rate	Configures the minimum traffic rate to keep VCs from being idled.
ip pim vc-count	Changes the maximum number of VCs that PIM can open.
show ip pim vc	Displays ATM virtual circuit status information for multipoint VCs opened by PIM.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

Use this command on Frame Relay, Switched Multimegabit Data Service (SMDS), or ATM only, especially when these media do not have native multicast available. Do not use this command on multicast-capable LANs such as Ethernet or FDDI.

When this command is configured, each Protocol Independent Multicast (PIM) Join message is kept track of in the outgoing interface list of a multicast routing table entry. Therefore, only PIM WAN neighbors that have joined for the group will get packets sent as data link unicasts. This command should only be used when the ip pim sparse-mode command is configured on the interface. This command is not recommended for LANs that have natural multicast capabilities.

Examples

The following example configures an interface to be in nonbroadcast multiaccess mode:

ip pim nbma-mode

Related Commands

Command	Description
ip pim	Enables PIM on an interface.

Syntax Description

access-list-number

Standard IP access list that denies PIM packets from a source.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Examples

The following example enables stub multicast routing on Router A, which has an outgoing interface with IP address 10.0.0.1. Router B is a central router with an incoming interface with address 10.0.0.2. Access list 1 filters PIM messages from the source (stub Router A).

Router A

ip multicast-routing
ip pim dense-mode
ip igmp helper-address 10.0.0.2

Router B

ip multicast-routing
 ip pim dense-mode : or ip pim sparse-mode
 ip pim neighbor-filter 1
access-list 1 deny 10.0.0.1

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.
ip igmp helper-address	Causes the system to forward all IGMP Host Reports and Leave messages received on the interface to the specified IP address.

Syntax Description

seconds

Interval, in seconds, at which periodic PIM router-query messages are sent. It can be a number from 1 to 65535. The default is 30 seconds.

Defaults

30 seconds

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Routers configured for IP multicast send PIM router-query messages to determine which router will be the designated router for each LAN segment (subnet). The designated router is responsible for sending Internet Group Management Protocol (IGMP) host-query messages to all hosts on the directly connected LAN. When operating in sparse mode, the designated router is responsible for sending source registration messages to the RP. The designated router is the router with the largest IP address.

Examples

The following example changes the PIM router-query message interval to 45 seconds:

interface tunnel 0
 ip pim query-interval 45

Related Commands

Command	Description
ip igmp query-interval	Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.

Syntax Description

ip-address	IP address of a router to be a PIM RP. This is a unicast IP address in four-part, dotted notation.
group-access-list-number	(Optional) Number of an access list that defines for which multicast groups the RP should be used. This is a standard IP access list. The number can be from 1 to 100.
override	(Optional) Indicates that if there is a conflict between the RP configured with this command and one learned by Auto-RP, the RP configured with this command prevails.

Defaults

No PIM RPs are preconfigured.

Command Modes

Global configuration

Command History

Release	Modification
10.2	This command was introduced.

Usage Guidelines

You must configure the IP address of RPs on all routers (including the RP router).

First-hop routers send register packets to the RP address on behalf of source multicast hosts. Routers also use this address on behalf of multicast hosts that want to become members of a group. These routers send Join and Prune messages towards the RP. The RP must be a PIM router; however, it does not require any special configuration to recognize that it is the RP. Also, RPs are not members of the multicast group; rather, they serve as a "meeting place" for multicast sources and group members.

You can configure the Cisco IOS software to use a single RP for more than one group. The conditions specified by the access list determine which groups the RP can be used for. If no access list is configured, the RP is used for all groups.

A PIM router can use multiple RPs, but only one per group.

If there is no RP configured for a group, the router will treat the group as dense using the dense-mode PIM techniques.

If the RP for a group is learned through a dynamic mechanism, such as Auto-RP, then this command might not be required. If there is a conflict between the RP configured with this command and one learned by Auto-RP, the Auto-RP information is used, unless the override keyword is specified.

Examples

The following example sets the PIM RP address to 198.92.37.33 for all multicast groups:

ip pim rp-address 198.92.37.33
 

The following example sets the PIM RP address to 147.106.6.22 for the multicast group 225.2.2.2 only:

access list 1 225.2.2.2 0.0.0.0
 ip pim rp-address 147.106.6.22 1

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.

Syntax Description

rp-list access-list-number	Standard access list of RP addresses that are allowable for the group ranges supplied in the group-list access-list-number.
group-list access-list-number	Standard access list that describes the multicast groups the RPs serve.

Defaults

All RP announcements are accepted.

Command Modes

Global configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

Configure this command on the PIM RP-mapping agent. If you are going to 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 2
access-list 1 permit 10.0.0.1
access-list 1 permit 10.0.0.2
access-list 2 permit 224.0.0.0 15.255.255.255

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.

Syntax Description

type number	IP address associated with this interface type and number on this router is advertised as a candidate RP address.
group-list access-list-number	(Optional) Standard IP access list number that defines the group prefixes that are advertised in association with the RP address.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release	Modification
11.3 T	This command was introduced.

Usage Guidelines

This command causes the router to send a PIM Version 2 message advertising itself as a candidate RP to the bootstrap router. 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 it is responsible for.

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.

Examples

The following example configures the router to advertise itself as a candidate RP to the bootstrap router 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 4
access-list 4 permit 239.0.0.0 0.255.255.255

Related Commands

Command	Description
ip pim bsr-candidate	Configures the router to announce its candidacy as a BSR.
ip pim rp-announce-filter	Filters incoming Auto-RP announcement messages coming from the RP.

Syntax Description

type number	Interface type and number that identify the RP address.
scope ttl	Time-to-live value that limits the announcements.
group-list access-list-number	Access list that describes the group ranges for which this router is the RP.

Defaults

Auto-RP is disabled.

Command Modes

Global configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

Use this command in the router you want to be an RP. 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.

Examples

The following example sends RP announcements out all PIM-enabled interfaces for a maximum of 31 hops. The IP address the router wants to be identified by as RP is the IP address associated with Ethernet interface 0. Access-list 5 describes for which groups this router serves as RP.

ip pim send-rp-announce ethernet0 scope 31 group-list 5
access-list 5 permit 224.0.0.0 15.255.255.255

Related Commands

Command	Description
access-list (IP standard)	Defines a standard IP access list.

Syntax Description

scope ttl

Time-to-live value in the IP header that keeps the discovery messages within this number of hops.

Defaults

The router is not an RP mapping agent.

Command Modes

Global configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

Configure this command on the router designated as an RP-mapping agent. Specify a TTL large enough to cover your PIM domain.

When Auto-RP is used, the following steps occur:

1. The RP-mapping agent listens on well-known group address CISCO-RP-ANNOUNCE (224.0.1.39), which candidate RPs send to.

2. The RP-mapping agent sends RP-to-group mappings in an Auto-RP RP discovery message to the well-known group CISCO-RP-DISCOVERY (224.0.1.40). The TTL value limits how many hops the message can take.

3. PIM designated routers listen to this group and use the RPs they learn about from the discovery message.

Examples

The following example limits Auto-RP RP Discovery messages to 20 hops:

ip pim send-rp-discovery scope 20

Syntax Description

kbps	Traffic rate in kilobits per second.
infinity	Causes all sources for the specified group to use the shared-tree.
group-list access-list-number	(Optional) Indicates what groups the threshold applies to. Must be a standard IP access list number. If the value is 0 or is omitted, the threshold applies to all groups.

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

Release	Modification
11.1	This command was introduced.

Usage Guidelines

If a source sends at a rate greater than or equal to 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 what groups the threshold applies to.

If the traffic rate from the source drops below the threshold kbps value, the leaf router will, after some amount of time, 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 4

Syntax Description

number

Maximum number of virtual circuits that PIM can open. The default is 200 virtual circuits. The range is from 1 to 65535.

Defaults

200 virtual circuits per ATM interface or subinterface

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Examples

The following example allows PIM to open a maximum of 250 virtual circuits:

ip pim vc-count 250

Related Commands

Command	Description
ip pim minimum-vc-rate	Configures the minimum traffic rate to keep VCs from being idled.
ip pim multipoint-signalling	Enables PIM to open ATM multipoint switched VCs for each multicast group that a receiver joins.
ip pim	Enables PIM on an interface.
show ip pim vc	Displays ATM virtual circuit status information for multipoint VCs opened by PIM.

Syntax Description

1	(Optional) Configures PIM Version 1.
2	(Optional) Configures PIM Version 2.

Defaults

Version 2

Command Modes

Interface configuration

Command History

Release	Modification
11.3 T	This command was introduced.

Usage Guidelines

An interface in Version 2 mode automatically downgrades to Version 1 mode if that interface has a PIM Version 1 neighbor. The interface returns to Version 2 mode after all Version 1 neighbors disappear (that is, they are shut down or upgraded).

Examples

The following example configures the interface to operate in PIM Version 1 mode:

interface ethernet 0
 ip address 1.1.1.1 255.0.0.0
 ip pim sparse-dense-mode
 ip pim version 1

Syntax Description

number

Number of RTP header compression connections the cache supports, in the range from 3 to 1000. The default is 32 connections (16 calls).

Defaults

32 connections

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.
12.0(7)T	For PPP and High-Level Data Link Control (HDLC) encapsulation, the maximum number of connections increased from 256 to 1000. For Frame Relay encapsulation, the maximum number of connections increased to 256. The maximum value for Frame Relay is fixed, not configurable.

Examples

The following example changes the number of RTP header compression connections supported to 150:

interface serial 0
 encapsulation ppp
 ip rtp header-compression
 ip rtp compression-connections 150

Related Commands

Command	Description
frame-relay ip rtp header-compression	Enables RTP header compression for all Frame Relay maps on a physical interface.
frame-relay map ip rtp header-compression	Enables RTP header compression per DLCI.
ip rtp header-compression	Enables RTP header compression.
ip tcp header-compression	Enables TCP header compression.
show ip rtp header-compression	Displays RTP header compression statistics.

Syntax Description

passive

(Optional) Compresses outgoing RTP packets only if incoming RTP packets on the same interface are compressed.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

If you use this command without the passive keyword, the software compresses all RTP traffic.

You can compress IP/User Datagram Protocol (UDP)/RTP headers to reduce the size of your packets. Compressing headers is especially useful for RTP, because RTP payload can be as small as 20 bytes, and the uncompressed header is 40 bytes.

RTP header compression is supported on serial lines using Frame Relay, High-Level Data Link Control (HDLC), or PPP encapsulation. You must enable compression on both ends of a serial connection.

This feature can compress unicast or multicast RTP packets, and hence MBONE traffic can also be compressed over slow links. The compression scheme is beneficial only when you have small payload sizes, as in audio traffic.

Examples

The following example enables RTP header compression on serial interface 0 and limits the number of RTP header compression connections to 10:

interface serial 0
 encapsulation ppp
 ip rtp header-compression
 ip rtp compression-connections 10

Related Commands

Command	Description
clear ip rtp header-compression	Clears RTP header compression structures and statistics.
ip rtp compression-connections	Specifies the total number of RTP header compression connections that can exist on an interface.
show ip rtp header-compression	Displays RTP header compression statistics.

Syntax Description

minutes

Time, in minutes, that an sdr cache entry is active in the cache.

Defaults

Disabled, which means entries are never deleted from the cache.

Command Modes

Global configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

You might want to limit how long sdr cache entries remain active because, otherwise, the source might stop advertising sdr entries. You do not want to keep old advertisements needlessly.

Examples

The following example causes sdr cache entries to remain in the cache for only 30 minutes:

ip sdr cache-timeout 30

Related Commands

Command	Description
clear ip sdr	Deletes an sdr cache entry or the entire sdr cache.
show ip sdr	Displays the session directory cache.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command replaces the ip sd listen command, which is obsolete.

Examples

The following example enables a router to listen to session directory advertisements:

ip sdr listen

Related Commands

Command	Description
clear ip sdr	Deletes an sdr cache entry or the entire sdr cache.
show ip sdr	Displays the session directory cache.

Syntax Description

interface type number

(Optional) Interface type and number.

Command Modes

EXEC

Command History

Release	Modification
11.3	This command was introduced.

Examples

The following is sample output from the show frame-relay ip rtp header-compression command:

Router# show frame-relay ip rtp header-compression 
 
DLCI 17 	 Link/Destination info: ip 165.3.3.2 
  Interface Serial0:
    Rcvd:    0 total, 0 compressed, 0 errors
             0 dropped, 0 buffer copies, 0 buffer failures
    Sent:    6000 total, 5998 compressed, 
             227922 bytes saved, 251918 bytes sent
             1.90 efficiency improvement factor
    Connect: 16 rx slots, 16 tx slots, 2 long searches, 2 misses
             99% hit ratio, five minute miss rate 0 misses/sec, 0 max
 

Related Commands

Command	Description
frame-relay ip rtp header-compression	Enables RTP header compression for all Frame Relay maps on a physical interface.
frame-relay map ip compress	Enables both RTP and TCP header compression on a link.
frame-relay map ip rtp header-compression	Enables RTP header compression per DLCI.
show ip rtp header-compression	Displays RTP header compression statistics.

Syntax Description

name | ip-address

(Optional) Name or IP address of an entry in the DVMRP routing table.

Command Modes

EXEC

Command History

Release	Modification
10.3	This command was introduced.

Examples

The following is sample output of the show ip dvmrp route command:

Router# show ip dvmrp route
 
DVMRP Routing Table - 1 entry
171.68.0.0/16 [100/11] uptime 07:55:50, expires 00:02:52
    via 137.39.3.93, Tunnel3
 

Related Commands

Command	Description
ip dvmrp accept-filter	Configures an acceptance filter for incoming DVMRP reports.

Syntax Description

group-name	(Optional) Name of the multicast group, as defined in the DNS hosts table.
group-address	(Optional) Address of the multicast group. This is a multicast IP address in four-part, dotted notation.
type	(Optional) Interface type.
number	(Optional) Interface number.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

If you omit all optional arguments, the show ip igmp groups command displays by group address and interface type and number all directly connected multicast groups.

Examples

The following is sample output from the show ip igmp groups command:

Router# show ip igmp groups
 
IGMP Connected Group Membership
Group Address    Interface       Uptime    Expires   Last Reporter
224.0.255.1      Ethernet0       18:51:41  0:02:15   198.92.37.192
224.2.226.60     Ethernet0       1:51:31   0:02:17   198.92.37.192
224.2.127.255    Ethernet0       18:51:45  0:02:17   198.92.37.192
226.2.2.2        Ethernet1       18:51:47  never     0.0.0.0
224.2.0.1        Ethernet0       18:51:43  0:02:14   198.92.37.192
225.2.2.2        Ethernet0       18:51:43  0:02:21   198.92.37.33
225.2.2.2        Ethernet1       18:51:47  never     0.0.0.0
225.2.2.4        Ethernet0       18:18:02  0:02:20   198.92.37.192
225.2.2.4        Ethernet1       18:23:32  0:02:55   198.92.36.128
 

Related Commands

Command	Description
ip igmp query-interval	Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.

Syntax Description

type	(Optional) Interface type.
number	(Optional) Interface number.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

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 interface
 
Ethernet0 is up, line protocol is up
  Internet address is 198.92.37.6, subnet mask is 255.255.255.0
  IGMP is enabled on interface
  IGMP query interval is 60 seconds
  Inbound IGMP access group is not set
  Multicast routing is enabled on interface
  Multicast TTL threshold is 0
  Multicast designated router (DR) is 198.92.37.33
  No multicast groups joined
Ethernet1 is up, line protocol is up
  Internet address is 198.92.36.129, subnet mask is 255.255.255.0
  IGMP is enabled on interface
  IGMP query interval is 60 seconds
  Inbound IGMP access group is not set
  Multicast routing is enabled on interface
  Multicast TTL threshold is 0
  Multicast designated router (DR) is 198.92.36.131
  Multicast groups joined: 225.2.2.2 226.2.2.2
Tunnel0 is up, line protocol is up
  Internet address is 10.1.37.2, subnet mask is 255.255.0.0
  IGMP is enabled on interface
  IGMP query interval is 60 seconds
  Inbound IGMP access group is not set
  Multicast routing is enabled on interface
  Multicast TTL threshold is 0
  No multicast groups joined
 

Related Commands

Command	Description
ip address	Sets a primary or secondary IP address for an interface.
ip igmp access-group	Controls the multicast groups that hosts on the subnet serviced by an interface can join.
ip igmp query-interval	Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
ip multicast ttl-threshold	Configures the TTL threshold of packets being forwarded out an interface.
ip pim	Enables PIM on an interface.

Syntax Description

group	(Optional) Displays the fast-switching cache for the single group. The group argument can be either a Class D IP address or a DNS name.
source	(Optional) If source is also specified, displays a single multicast cache entry. The source argument can be either a unicast IP address or a DNS name.

Command Modes

EXEC

Command History

Release	Modification
11.0	This command was introduced.

Examples

The following is sample output from the show ip mcache command. This entry shows a specific source (wrn-source 204.62.246.73) sending to the World Radio Network group (224.2.143.24).

Router> show ip mcache wrn wrn-source
 
IP Multicast Fast-Switching Cache 
(204.62.246.73/32, 224.2.143.24), Fddi0, Last used: 00:00:00  
  Ethernet0       MAC Header: 01005E028F1800000C1883D30800 
  Ethernet1       MAC Header: 01005E028F1800000C1883D60800 
  Ethernet2       MAC Header: 01005E028F1800000C1883D40800 
  Ethernet3       MAC Header: 01005E028F1800000C1883D70800
 

Syntax Description

source-address | name	(Optional) Displays cache headers matching the specified source address or name.
group-address | name	(Optional) Displays cache headers matching the specified group address or group name.
detail	(Optional) In addition to the summary information, displays the rest of the IP header fields on an additional line, plus the first 8 bytes after the IP header (usually the UDP port numbers).

Command Modes

EXEC

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command is only applicable 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, TTL, source and destination IP addresses, and a local timestamp when the packet was received.

The two arguments and one keyword can be used in the same command in any combination.

Examples

The following is sample output of the show ip mpacket command with the group-name argument:

Router # show ip mpacket smallgroup
IP Multicast Header Cache - entry count:6, next index: 7
Key: id/ttl timestamp (name) source group
 
D782/117 206416.908 (ABC-xy.company.com) 198.15.228.10 224.5.6.7
7302/113 206417.908 (school.edu) 147.12.2.17 224.5.6.7
6CB2/114 206417.412 (MSSRS.company.com) 154.2.19.40 224.5.6.7
D782/117 206417.868 (ABC-xy.company.com) 198.15.228.10 224.5.6.7
E2E9/123 206418.488 (Newman.com) 211.1.8.10 224.5.6.7
1CA7/127 206418.544 (teller.company.com) 192.4.6.10 224.5.6.7
 
 

Related Commands

Command	Description
ip multicast cache-headers	Allocates a circular buffer to store IP multicast packet headers that the router receives.

Syntax Description

group-name | group-address	(Optional) IP address, name, or interface of the multicast group as defined in the DNS hosts table.
source	(Optional) IP address or name of a multicast source.
summary	(Optional) Displays a one-line, abbreviated summary of each entry in the IP multicast routing table.
count	(Optional) Displays statistics about the group and source, including number of packets, packets per second, average packet size, and bits per second.
active kbps	(Optional) Displays the rate that active sources are sending to multicast groups. Active sources are those sending at a rate of kbps or higher. The kbps argument defaults to 4 kbps.

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

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

If you omit all optional arguments and keywords, the show ip mroute command displays all entries in the IP multicast routing table.

Examples

The following is sample output from the show ip mroute command for a router operating in dense mode. This command displays the contents of the IP multicast routing table for the multicast group named cbone-audio.

Router# show ip mroute cbone-audio
 
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
       R - RP-bit set, F - Register flag, T - SPT-bit set
Timers: Uptime/Expires
Interface state: Interface, Next-Hop, State/Mode
 
(*, 224.0.255.1), uptime 0:57:31, expires 0:02:59, RP is 0.0.0.0, flags: DC
  Incoming interface: Null, RPF neighbor 0.0.0.0, Dvmrp
  Outgoing interface list:
    Ethernet0, Forward/Dense, 0:57:31/0:02:52
    Tunnel0, Forward/Dense, 0:56:55/0:01:28
 
(198.92.37.100/32, 224.0.255.1), uptime 20:20:00, expires 0:02:55, flags: C
  Incoming interface: Tunnel0, RPF neighbor 10.20.37.33, Dvmrp
  Outgoing interface list:
    Ethernet0, Forward/Dense, 20:20:00/0:02:52
 

The following is sample output from the show ip mroute command for a router operating in sparse mode:

Router# show ip mroute
 
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
       R - RP-bit set, F - Register flag, T - SPT-bit set
Timers: Uptime/Expires
Interface state: Interface, Next-Hop, State/Mode
 
(*, 224.0.255.3), uptime 5:29:15, RP is 198.92.37.2, flags: SC
  Incoming interface: Tunnel0, RPF neighbor 10.3.35.1, Dvmrp
  Outgoing interface list:
    Ethernet0, Forward/Sparse, 5:29:15/0:02:57
 
(198.92.46.0/24, 224.0.255.3), uptime 5:29:15, expires 0:02:59, flags: C
  Incoming interface: Tunnel0, RPF neighbor 10.3.35.1
  Outgoing interface list:
    Ethernet0, Forward/Sparse, 5:29:15/0:02:57
 

The following is sample output from the show ip mroute command that shows the VCD value, because an ATM interface with PIM multipoint signaling is enabled:

Router# show ip mroute 224.1.1.1
 
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
       R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
 
(*, 224.1.1.1), 00:03:57/00:02:54, RP 130.4.101.1, flags: SJ
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    ATM0/0, VCD 14, Forward/Sparse, 00:03:57/00:02:53
 

The following is sample output from the show ip mroute command with the summary keyword:

Router# show ip mroute summary
 
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
       R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, Next-Hop, State/Mode
 
(*, 224.255.255.255), 2d16h/00:02:30, RP 171.69.10.13, flags: SJPC
 
(*, 224.2.127.253), 00:58:18/00:02:00, RP 171.69.10.13, flags: SJC
 
(*, 224.1.127.255), 00:58:21/00:02:03, RP 171.69.10.13, flags: SJC
 
(*, 224.2.127.254), 2d16h/00:00:00, RP 171.69.10.13, flags: SJCL
  (128.9.160.67/32, 224.2.127.254), 00:02:46/00:00:12, flags: CLJT
  (129.48.244.217/32, 224.2.127.254), 00:02:15/00:00:40, flags: CLJT
  (130.207.8.33/32, 224.2.127.254), 00:00:25/00:02:32, flags: CLJT
  (131.243.2.62/32, 224.2.127.254), 00:00:51/00:02:03, flags: CLJT
  (140.173.8.3/32, 224.2.127.254), 00:00:26/00:02:33, flags: CLJT
  (171.69.60.189/32, 224.2.127.254), 00:03:47/00:00:46, flags: CLJT
 

The following is sample output from the show ip mroute command with the active keyword:

Router# show ip mroute active
 
Active IP Multicast Sources - sending >= 4 kbps
 
Group: 224.2.127.254, (sdr.cisco.com)
   Source: 146.137.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 97
   Source: 130.129.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 97
   Source: 130.129.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 with the count keyword:

Router# show ip mroute count
 
IP Multicast Statistics - Group count: 8, Average sources per group: 9.87
Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
 
Group: 224.255.255.255, Source count: 0, Group pkt count: 0
  RP-tree: 0/0/0/0
 
Group: 224.2.127.253, Source count: 0, Group pkt count: 0
  RP-tree: 0/0/0/0
 
Group: 224.1.127.255, Source count: 0, Group pkt count: 0
  RP-tree: 0/0/0/0
 
Group: 224.2.127.254, Source count: 9, Group pkt count: 14
  RP-tree: 0/0/0/0
  Source: 128.2.6.9/32, 2/0/796/0
  Source: 128.32.131.87/32, 1/0/616/0
  Source: 128.125.51.58/32, 1/0/412/0
  Source: 130.207.8.33/32, 1/0/936/0
  Source: 131.243.2.62/32, 1/0/750/0
  Source: 140.173.8.3/32, 1/0/660/0
  Source: 146.137.28.69/32, 1/0/584/0
  Source: 171.69.60.189/32, 4/0/447/0
  Source: 204.162.119.8/32, 2/0/834/0
 
Group: 224.0.1.40, Source count: 1, Group pkt count: 3606
  RP-tree: 0/0/0/0
  Source: 171.69.214.50/32, 3606/0/48/0, RPF Failed: 1203
 
Group: 224.2.201.241, Source count: 36, Group pkt count: 54152
  RP-tree: 7/0/108/0
  Source: 13.242.36.83/32, 99/0/123/0
  Source: 36.29.1.3/32, 71/0/110/0
  Source: 128.9.160.96/32, 505/1/106/0
  Source: 128.32.163.170/32, 661/1/88/0
  Source: 128.115.31.26/32, 192/0/118/0
  Source: 128.146.111.45/32, 500/0/87/0
  Source: 128.183.33.134/32, 248/0/119/0
  Source: 128.195.7.62/32, 527/0/118/0
  Source: 128.223.32.25/32, 554/0/105/0
  Source: 128.223.32.151/32, 551/1/125/0
  Source: 128.223.156.117/32, 535/1/114/0
  Source: 128.223.225.21/32, 582/0/114/0
  Source: 129.89.142.50/32, 78/0/127/0
  Source: 129.99.50.14/32, 526/0/118/0
  Source: 130.129.0.13/32, 522/0/95/0
  Source: 130.129.52.160/32, 40839/16/920/161
  Source: 130.129.52.161/32, 476/0/97/0
  Source: 130.221.224.10/32, 456/0/113/0
  Source: 132.146.32.108/32, 9/1/112/0