Table Of Contents
clear ip rtp header-compression
frame-relay ip rtp header-compression
frame-relay map ip rtp header-compression
ip dvmrp routehog-notification
ip igmp last-member-query-interval
ip igmp query-max-response-time
ip rtp compression-connections
show frame-relay ip rtp header-compression
show ip rtp header-compression
IP Multicast Routing Commands
This chapter describes the commands used to configure and monitor IP multicast routing. For IP multicast routing configuration information and examples, refer to the "Configuring IP Multicast Routing" chapter of the Cisco IOS IP and IP Routing Configuration Guide.
clear ip cgmp
To clear all group entries from the caches of Catalyst switches, use the clear ip cgmp EXEC command.
clear ip cgmp [type number]
Syntax Description
Command Modes
EXEC
Command History
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 cgmpRelated Commands
clear ip dvmrp route
To delete routes from the DVMRP routing table, use the clear ip dvmrp route EXEC command.
clear ip dvmrp route {* | route}
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
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.1clear ip igmp group
To delete entries from the Internet Group Management Protocol (IGMP) cache, use the clear ip igmp group EXEC command.
clear ip igmp group [group-name | group-address | type number]
Syntax Description
Defaults
When the command is used with no arguments, all entries are deleted from the IGMP cache.
Command Modes
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, 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.1Related Commands
clear ip mroute
To delete entries from the IP multicast routing table, use the clear ip mroute EXEC command.
clear ip mroute {* | group [source]}
Syntax Description
Command Modes
EXEC
Command History
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.0Related Commands
ip host
Defines a static host name-to-address mapping in the host cache.
Displays the contents of the IP multicast routing table.
clear ip pim auto-rp
To delete entries from the Auto-RP cache, use the clear pim auto-rp EXEC command.
clear ip pim auto-rp rp-address
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
Examples
The following example deletes all entries from the Auto-RP cache:
clear ip pim auto-rpclear ip rtp header-compression
To clear Real-Time Transport Protocol (RTP) header compression structures and statistics, use the clear ip rtp header-compression EXEC command.
clear ip rtp header-compression [type number]
Syntax Description
Command Modes
EXEC
Command History
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 0Related Commands
clear ip sdr
To delete a Session Directory Protocol (sdr) cache entry or the entire sdr cache, use the clear ip sdr EXEC command.
clear ip sdr [group-address | "session-name"]
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
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 sdrRelated Commands
Limits how long a sdr cache entry stays active in the cache.
Enables the Cisco IOS software to listen to session directory advertisements.
Displays the session directory cache.
frame-relay ip rtp header-compression
To enable Real-Time Transport Protocol (RTP) header compression for all Frame Relay maps on a physical interface, use the frame-relay ip rtp header-compression interface configuration command. To disable the compression, use the no form of this command.
frame-relay ip rtp header-compression [active | passive]
no frame-relay ip rtp header-compression [active | passive]
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
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-compressionRelated Commands
frame-relay map ip compress
To enable both Real-Time Transport Protocol (RTP) and TCP header compression on a link, use the frame-relay map ip compress interface configuration command. To disable both RTP and TCP header compression, use the no form of this command.
frame-relay map ip ip-address dlci [broadcast] compress
no frame-relay map ip ip-address dlci [broadcast] compress
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
Examples
The following example enables both RTP and TCP header compression on serial interface 1:
interface serial 1encapsulation frame-relayip address 131.108.175.110 255.255.255.0frame-relay map ip 131.108.175.220 180 compressRelated Commands
frame-relay map ip rtp header-compression
To enable Real-Time Transport Protocol (RTP) header compression per data-link connection identifier (DLCI), use the frame-relay map ip rtp header-compression interface configuration command. To disable the compression, use the no form of this command.
frame-relay map ip ip-address dlci rtp header-compression [active | passive]
no frame-relay map ip ip-address dlci rtp header-compression [active | passive]
Syntax Description
Defaults
Disabled.
If the command is configured, active is the default keyword.
Command Modes
Interface configuration
Command History
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 1encapsulation frame-relayip address 131.108.175.110 255.255.255.0frame-relay map ip 131.108.175.220 180 rtp header-compressionRelated Commands
ip cgmp
To enable Cisco Group Management Protocol (CGMP) on an interface of a router connected to a Catalyst 5000 switch, use the ip cgmp interface configuration command. To disable CGMP routing, use the no form of this command.
ip cgmp [proxy]
no ip cgmp
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
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.
•
Examples
The following example enables CGMP:
ip cgmpThe following example enables CGMP and CGMP proxy:
ip cgmp proxyip dvmrp accept-filter
To configure an acceptance filter for incoming Distance Vector Multicast Routing Protocol (DVMRP) reports, use the ip dvmrp accept-filter interface configuration command. To disable this filter, use the no form of this command.
ip dvmrp accept-filter access-list-number [distance | neighbor-list access-list-number]
no ip dvmrp accept-filter access-list-number [distance | neighbor-list access-list-number]
Syntax Description
Defaults
All destination reports are accepted with a distance of 0. Default settings accept reports from all neighbors.
Command Modes
Interface configuration
Command History
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.
By default, the administrative distance for DVMRP routes is 0. This means that they always take precedence over unicast routing table routes. If you have two paths to a source, one through unicast routing (using PIM as the multicast routing protocol) and another path using DVMRP (unicast and multicast routing), and if you want to use the PIM path, use the ip dvmrp accept-filter command to increase the administrative distance for DVMRP routes. For example, if the unicast routing protocol is Enhanced IGRP, which has a default administrative distance of 90, you could define and apply the following access list so the RPF interface used to accept multicast packets will be through the Enhanced IGRP/PIM path:
ip dvmrp accept-filter 1 100access-list 1 permit 0.0.0.0 255.255.255.255Examples
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.255access-list 57 permit 198.92.37.0 0.0.0.255access-list 57 deny 0.0.0.0 255.255.255.255ip dvmrp accept-filter 57 4Related Commands
ip dvmrp auto-summary
To enable Distance Vector Multicast Routing Protocol (DVMRP) auto summarization if it was disabled, use the ip dvmrp auto-summary interface configuration command. To disable the feature, use the no form of this command.
ip dvmrp auto-summary
no ip dvmrp auto-summary
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
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-summaryRelated Commands
ip dvmrp default-information
To advertise network 0.0.0.0 to Distance Vector Multicast Routing Protocol (DVMRP) neighbors on an interface, use the ip dvmrp default-information interface configuration command. To prevent the advertisement, use the no form of this command.
ip dvmrp default-information {originate | only}
no ip dvmrp default-information {originate | only}
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
Usage Guidelines
This command should only be used when the router is a neighbor to mrouted version 3.6 machines. The mrouted protocol is a public domain implementation of DVMRP.
You can use the ip dvmrp metric command with the ip dvmrp default-information command to tailor the metric used when advertising the default route 0.0.0.0. By default, metric 1 is used.
Examples
The following example configures the Cisco IOS software to advertise network 0.0.0.0, in addition to other networks, to DVMRP neighbors:
ip dvmrp default-information originateRelated Commands
ip dvmrp metric
To configure the metric associated with a set of destinations for Distance Vector Multicast Routing Protocol (DVMRP) reports, use the appropriate form of the ip dvmrp metric interface configuration command. To disable this function, use the appropriate no form of this command.
ip dvmrp metric metric [list access-list-number] [mbgp]
no ip dvmrp metric metric [list access-list-number] [mbgp]
ip dvmrp metric metric [list access-list-number] [[protocol process-id] | dvmrp]
no ip dvmrp metric metric [list access-list-number] [[protocol process-id] | dvmrp]
ip dvmrp metric metric route-map map-name [mbgp]
no ip dvmrp metric metric route-map map-name [mbgp]
Syntax Description
Defaults
No metric is preconfigured. Only directly connected subnets and networks are advertised to neighboring DVMRP routers.
Command Modes
Interface configuration
Command History
10.2
This command was introduced.
11.1
The route-map keyword was added.
12.1
The mbgp 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.255access-list 1 deny 0.0.0.0 255.255.255.255access-list 2 permit 0.0.0.0 255.255.255.255interface tunnel 0ip dvmrp metric 1 list 1ip dvmrp metric 0 list 2The following example redistributes IPv4 multicast routes into DVMRP neighbors with a metric of 1:
interface tunnel 0ip dvmrp metric 1 mbgpRelated Commands
debug ip dvmrp
Displays information on DVMRP packets received and sent.
Configures an acceptance filter for incoming DVMRP reports.
ip dvmrp metric-offset
To change the metrics of advertised Distance Vector Multicast Routing Protocol (DVMRP) routes and thus favor or not favor a certain route, use the ip dvmrp metric-offset interface configuration command. To restore the default values, use the no form of this command.
ip dvmrp metric-offset [in | out] increment
no ip dvmrp metric-offset
Syntax Description
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
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 10ip dvmrp output-report-delay
To configure an interpacket delay of a Distance Vector Multicast Routing Protocol (DVMRP) report, use the ip dvmrp output-report-delay interface configuration command. To restore the default values, use the no form of this command.
ip dvmrp output-report-delay milliseconds [burst]
no ip dvmrp output-report-delay milliseconds [burst]
Syntax Description
Defaults
milliseconds is 100 milliseconds
burst is 2 packets
Command Modes
Interface configuration
Command History
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 3ip dvmrp reject-non-pruners
To configure the router so that it will not peer with a Distance Vector Multicast Routing Protocol (DVMRP) neighbor if that neighbor does not support DVMRP pruning or grafting, use the ip dvmrp reject-non-pruners interface configuration command. To disable the function, use the no form of this command.
ip dvmrp reject-non-pruners
no ip dvmrp reject-non-pruners
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
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-prunersip dvmrp routehog-notification
To change the number of Distance Vector Multicast Routing Protocol (DVMRP) routes allowed before a syslog warning message is issued, use the ip dvmrp routehog-notification global configuration command. To restore the default value, use the no form of this command.
ip dvmrp routehog-notification route-count
no ip dvmrp routehog-notification
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
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 8000Related Commands
show ip igmp interface
Displays multicast-related information about an interface.
ip dvmrp route-limit
To change the limit on the number of Distance Vector Multicast Routing Protocol (DVMRP) routes that can be advertised over an interface enabled to run DVMRP, use the ip dvmrp route-limit global configuration command. To configure no limit, use the no form of this command.
ip dvmrp route-limit count
no ip dvmrp route-limit
Syntax Description
Defaults
7000 routes
Command Modes
Global configuration
Command History
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 5000Related Commands
ip dvmrp summary-address
To configure a DVMRP summary address to be advertised out the interface, use the ip dvmrp summary-address interface configuration command. To remove the summary address, use the no form of this command.
ip dvmrp summary-address address mask [metric value]
no ip dvmrp summary-address address mask [metric value]
Syntax Description
Defaults
metric value is 1
Command Modes
Interface configuration
Command History
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 1Related Commands
ip dvmrp unicast-routing
To enable Distance Vector Multicast Routing Protocol (DVMRP) unicast routing on an interface, use the ip dvmrp unicast-routing interface configuration command. To disable the feature, use the no form of this command.
ip dvmrp unicast-routing
no ip dvmrp unicast-routing
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
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-routingRelated Commands
Changes the limit on the number of DVMRP routes that can be advertised over an interface enabled to run DVMRP.
ip igmp access-group
To control the multicast groups that hosts on the subnet serviced by an interface can join, use the ip igmp access-group interface configuration command. To disable groups on an interface, use the no form of this command.
ip igmp access-group access-list-number version
no ip igmp access-group access-list-number version
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
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.0interface ethernet 0ip igmp access-group 1Related Commands
ip igmp helper-address
To cause the system to forward all Internet Group Management Protocol (IGMP) Host Reports and Leave messages received on the interface to the specified IP address, use the ip igmp helper-address interface configuration command. To disable such forwarding, use the no form of this command.
ip igmp helper-address ip-address
no ip igmp helper-address
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
Usage Guidelines
This command and the ip pim neighbor-filter command together enable stub multicast routing. The IGMP Host Reports and Leave messages are forwarded to the IP address specified. The reports are resent out the next-hop interface toward the IP address, with that interface's source address. This command enables a sort of "dense-mode" Join, allowing stub sites not participating in PIM to indicate membership in IP multicast groups.
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-routingip pim dense-modeip igmp helper-address 10.0.0.2Router B
ip multicast-routingip pim dense-mode : or ip pim sparse-modeip pim neighbor-filter 1access-list 1 deny 10.0.0.1Related Commands
Prevents a router from participating in PIM (for example, to configure stub multicast routing).
ip igmp immediate-leave
To minimize the leave latency of Internet Group Management Protocol (IGMP) memberships when IGMP Version 2 is used and only one receiver host is connected to each interface, use the ip igmp immediate-leave command in global or interface configuration mode. To disable this feature, use the no form of this command.
ip igmp immediate-leave group-list access-list
no ip igmp immediate-leave
Syntax Description
group-list access-list
Specifies a standard access list number or name that defines multicast groups in which the immediate leave feature is enabled.
Defaults
This command is disabled.
Command Modes
Global configuration
Interface configurationCommand History
Usage Guidelines
You cannot configure this command in both interface and global configuration mode.
When this command is not configured, the router will send an IGMP group-specific query message upon receipt of an IGMP Version 2 (IGMPv2) group leave message. The router will stop forwarding traffic for that group only if no host replies to the query within the timeout period. The timeout period is determined by the ip igmp last-member-query-interval command and the IGMP robustness variable, which is defined by the IGMP specification. By default, the timeout period in Cisco IOS software is approximately 2.5 seconds.
If this command is configured, the router assumes that only one host has joined the group and stops forwarding the group's traffic immediately upon receipt of an IGMPv2 group leave message.
Global Configuration Mode
When this command is configured in global configuration mode, it applies to all IGMP-enabled interfaces. Any existing configuration of this command in interface configuration mode will be removed from the configuration. Also, any new configuration of this command in interface configuration mode will be ignored.
Interface Configuration Mode
When this command is configured in interface configuration mode, it applies to an individual interface. Configure this command on an interface if only one IGMP-enabled neighbor is connected to the interface. The neighbor can be either a host or switch running IGMP Snooping. When the ip igmp immediate-leave command is enabled on an interface, the router will not send IGMP group-specific host queries when an IGMP Version 2 leave group message is received from that interface. Instead, the router will immediately remove the interface from the IGMP cache for that group and send Protocol Independent Multicast (PIM) prune messages toward sources if this interface was the last one to join that group.
Examples
The following example shows how to enable the immediate leave feature on all interfaces for all multicast groups:
Router(config)# ip multicast-routingRouter(config)# ip igmp immediate-leave group-list all-groupsRouter(config)# interface ethernet 0Router(config-if)# ip address 10.0.10.1 255.255.255.0Router(config-if)# ip pim sparse-dense modeRouter(config-if)# exitRouter(config)# ip access-list standard all-groupsRouter(config)# permit 224.0.0.0 15.255.255.255The following example shows how to enable the immediate leave feature on an interface for a specific range of multicast groups. In this example, the router assumes that the tv-groups access list consists of groups that have only one host membership at a time per interface:
Router(config)# ip multicast-routingRouter(config)# interface ethernet 0Router(config-if)# ip address 10.0.10.1 255.255.255.0Router(config-if)# ip pim sparse-dense-modeRouter(config-if)# ip igmp immediate-leave group-list tv-groupsRouter(config-if)# exitRouter(config)# ip access-list standard tv-groupsRouter(config)# permit 239.192.20.0 0.0.0.255Related Commands
ip igmp last-member-query-interval
Configures the frequency at which the router sends IGMP group-specific host query messages.
ip igmp join-group
To have the router join a multicast group, use the ip igmp join-group interface configuration command. To cancel membership in a multicast group, use the no form of this command.
ip igmp join-group group-address
no ip igmp join-group group-address
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
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.2Related Commands
ip igmp last-member-query-interval
To configure the frequency at which the router sends Internet Group Management Protocol (IGMP) group-specific host query messages, use the ip igmp last-member-query-interval command in interface configuration mode. To set this frequency to the default value, use the no form of this command.
ip igmp last-member-query-interval interval
no ip igmp last-member-query-interval interval
Syntax Description
interval
Frequency, in milliseconds, at which IGMP group-specific host query messages are sent. It can be a number from 100 to 65535.
Defaults
1000 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
When a router receives an IGMP Version 2 leave group message on an interface, it waits twice the query interval specified by the ip igmp last-member-query-interval command plus up to a 1 second response time (due to timer processing); after which, if no receiver has responded, the router drops the group membership on that interface.
There is no command to modify the leave latency on switches.
Examples
The following example changes the IGMP group-specific host query message interval to 2 seconds:
interface tunnel 0ip igmp last-member-query-interval 2000Related Commands
ip igmp immediate-leave
Minimizes the leave latency of IGMP memberships when IGMPv2 is used and only one receiver host is connected to each interface.
ip igmp query-interval
To configure the frequency at which the Cisco IOS software sends Internet Group Management Protocol (IGMP) host-query messages, use the ip igmp query-interval interface configuration command. To return to the default frequency, use the no form of this command.
ip igmp query-interval seconds
no ip igmp query-interval
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
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.
•
•
If the router hears no queries for the timeout period (controlled by the ip igmp query-timeout command), it becomes the querier.
Caution
Examples
The following example changes the frequency at which the designated router sends IGMP host-query messages to 2 minutes:
interface tunnel 0ip igmp query-interval 120Related Commands
Configures the frequency of PIM router-query messages.
Displays the multicast groups that are directly connected to the router and that were learned through IGMP.
ip igmp query-max-response-time
To configure the maximum response time advertised in Internet Group Management Protocol (IGMP) queries, use the ip igmp query-max-response-time interface configuration command. To restore the default value, use the no form of this command.
ip igmp query-max-response-time seconds
no ip igmp query-max-response-time
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
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
Examples
The following example configures a maximum response time of 8 seconds:
ip igmp query-max-response-time 8Related Commands
Configures the frequency of PIM router-query messages.
Displays the multicast groups that are directly connected to the router and that were learned through IGMP.
ip igmp query-timeout
To configure the timeout time before the router takes over as the querier for the interface, after the previous querier has stopped querying, use the ip igmp query-timeout interface configuration command. To restore the default value, use the no form of this command.
ip igmp query-timeout seconds
no ip igmp query-timeout
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
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 30Related Commands
Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
ip igmp static-group
To configure the router to be a statically connected member of the specified group on the interface, or to statically forward for a multicast group onto the interface, use the ip igmp static-group command in interface configuration mode. To remove the router as a member of the group, use the no form of this command.
ip igmp static-group {* | group-address [source {source-address | ssm-map}]}
no ip igmp static-group {* | group-address [source {source-address | ssm-map}]}
Syntax Description
Defaults
A router is not a statically connected member of an IP multicast group.
Command Modes
Interface configuration
Command History
11.2
This command was introduced.
12.3(2)T
The source and the ssm-map keywords were added.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
Usage Guidelines
When you configure the ip igmp static-group command, packets to the group are fast-switched out the interface, provided that packets were received on the correct reverse path forwarding (RPF) interface.
Configuring the ip igmp static-group command is unlike configuring the ip igmp join-group command, which allows the router to join the multicast group. This configuration of the ip igmp static-group command would cause the upstream routers to maintain the multicast routing table information for that group, which would ensure that all the paths to that multicast group are active.
If you configure the ip igmp join-group command 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.
The use of SSM mapping determines the source or sources associated with a specific source (S) and group (G) combination and puts the particular interface in the outging interface list (OIL) for that (S, G) entry. Traffic coming from source S destined toward group G will be forwarded out that interface regardless of a receiver joining the group on that interface.
Examples
The following example configures group address 192.168.2.2 on Ethernet interface 0:
interface ethernet 0ip igmp static-group 192.168.2.2The following example shows how to configure group address 192.168.2.3 to use SSM mapping for statically forwarded groups on Ethernet interface 0:
interface ethernet 0ip igmp static-group 192.168.2.3 source ssm-mapRelated Commands
ip igmp version
To configure which version of Internet Group Management Protocol (IGMP) the router uses, use the ip igmp version interface configuration command. To restore the default value, use the no form of this command.
ip igmp version {2 | 1}
no ip version
Syntax Description
Defaults
Version 2
Command Modes
Interface configuration
Command History
Usage Guidelines
All routers on the subnet must support the same version. The router does not automatically detect Version 1 routers and switch to Version 1 as did earlier releases of the Cisco IOS software. However, a mix of IGMP Version 1 and Version 2 hosts on the subnet is acceptable. IGMP Version 2 routers will always work correctly in the presence of IGMP Version 1 hosts.
Some commands require IGMP Version 2, such as the ip igmp query-max-response-time and ip igmp query-timeout commands.
Examples
The following example configures the router to use IGMP Version 1:
ip igmp version 1Related Commands
ip mroute
To configure a multicast static route (mroute), use the ip mroute global configuration command. To remove the route, use the no form of this command.
ip mroute source mask [protocol as-number] {rpf-address | type number} [distance]
no ip mroute source mask [protocol as-number] {rpf-address | type 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 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 0.0.0.0 tunnel0The following example configures all specific sources within a network number are 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 0.0.0.0 0.0.0.0 serial0 200ip multicast boundary
To configure an administratively scoped boundary, use the ip multicast boundary interface configuration command. To remove the boundary, use the no form of this command.
ip multicast boundary access-list-number
no ip multicast boundary
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
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.255access-list 1 permit 224.0.0.0 15.255.255.255interface ethernet 0ip multicast boundary 1Related 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 global configuration command. To remove the buffer, use the no form of this command.
ip multicast cache-headers [rtp]
no ip multicast cache-headers
Syntax Description
Defaults
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:
•
•
•
•
•
•
•
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-headers
Related Commands
Displays the contents of the circular cache-header buffer.
show ip mpacket quality
Displays an RTP data quality based on packets captured in the IP multicast cache header buffer.
ip multicast helper-map
To allow IP multicast routing in a multicast-capable internetwork between two broadcast-only internetworks, use the ip multicast helper-map interface configuration command. To disable this function, use the no form of this command.
ip multicast helper-map {group-address | broadcast} {broadcast-address | multicast-address} extended-access-list-number
no ip multicast helper-map {group-address | broadcast} {broadcast-address | multicast-address} extended-access-list-number
Syntax Description
Defaults
No conversion between broadcast and multicast occurs.
Command Modes
Interface configuration
Command History
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
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 0ip directed-broadcastip multicast helper-map broadcast 224.5.5.5 120ip pim dense-mode!access-list 120 permit any any udp 4000access-list 120 deny any any udpip forward-protocol udp 4000Last Hop Router
interface ethernet 1ip directed-broadcastip multicast helper-map 224.5.5.5 178.21.34.255 135ip pim dense-mode!access-list 135 permit any any udp 4000access-list 135 deny any any udpip forward-protocol udp 4000Related Commands
ip multicast rate-limit
To control the rate a sender from the source-list can send to a multicast group in the group-list, use the ip multicast rate-limit interface configuration command. To remove the control, use the no form of this command.
ip multicast rate-limit {in | out} [video | whiteboard] [group-list access-list] [source-list access-list] kbps
no ip multicast rate-limit {in | out} [video | whiteboard] [group-list access-list] [source-list access-list] kbps
Syntax Description
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
Usage Guidelines
This command limits the rate with which IP multicast traffic can be received or sent across an interface.
The in and out keywords apply the command to IP multicast packets being received (in) or sent (out) on the interface. Rate-limiting can be configured simultaneously for incoming and outgoing packets.
The kbps keyword selects the rate in kilobits per second to which matching traffic will be limited. The default value for kbps is 0, in which case all IP multicast packets matched by this command will be dropped. The ip multicast rate-limit command then works like an access list filtering out matching packets.
The group-list access-list and source-list access-list keywords select a set of routing table entries corresponding to a specific group and source (G,S) or a set of routing table entries with a specific group and coming from any source (G,*) to which the command is to be applied. If no such argument is given, the command limit will be applied to the aggregate amount of IP multicast traffic coming in or going out the interface, if the interface does not have a more specific ip multicast rate-limit command that has the group-list or source-list applied to it. If the group-list or source-list argument is specified, the configured limit is applied to each of the matching G, S and G,* multicast states independently. The configured limit in the command does not apply to the aggregate amount of traffic matched by the command, but to each covered multicast route individually.
The video and whiteboard keywords contain rate-limiting to video or whiteboard packets only. These keywords can only be entered in sessions in which the media (video or whiteboard) has been announced via Session Description Protocol (SDP). The ip sap listen command must also be enabled so that the port number can be obtained from the SAP cache. If the ip sap listen command is not enabled, or the group address is not in the Session Announcement Protocol (SAP) cache, no rate-limiting is done for the group.
Rate-limiting can be applied only once for each direction (incoming or outgoing) on an interface; however, multicast route limiting can be specified more than once on each direction on an interface. If a multicast route state is matched by more than one configured ip multicast rate-limit command, the commands will be searched and the first matching criteria will be used for the multicast route state. The order in which the configured ip multicast rate-limit commands are searched for matching a multicast route is the order in which the ip multicast rate-limit commands are entered.
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 0ip multicast rate-limit out group-list 1 source-list 2 64access-list 1 permit 0.0.0.0 255.255.255.255access-list 2 permit 171.69.0.0 0.0.255.255Related Commands
ip multicast ttl-threshold
To configure the time-to-live (TTL) threshold of packets being forwarded out an interface, use the ip multicast ttl-threshold interface configuration command. To return to the default TTL threshold, use the no form of this command.
ip multicast ttl-threshold ttl-value
no ip multicast ttl-threshold [ttl-value]
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
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 0ip multicast ttl-threshold 200ip multicast use-functional
To enable the mapping of IP multicast addresses to the Token Ring functional address 0xc000.0004.0000, use the ip multicast use-functional interface configuration command. To disable the function, use the no form of this command.
ip multicast use-functional
no ip multicast use-functional
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
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 0ip address 1.1.1.1 255.255.255.0ip pim dense-modeip multicast use-functionalip pim
To enable Protocol Independent Multicast (PIM) on an interface, use the ip pim interface configuration command. To disable PIM on the interface, use the no form of this command.
ip pim {dense-mode | sparse-mode | sparse-dense-mode}
no ip pim
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
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
•
•
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:
•
•
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.8interface tunnel 0ip pim sparse-modeThe following example enable dense-mode PIM on Ethernet interface 1:
interface ethernet 1ip pim dense-modeThe following example enables sparse-dense mode:
interface ethernet 1ip pim sparse-dense-modeRelated 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 accept-register {list access-list | route-map map-name}
no ip pim accept-register {list access-list | route-map map-name}
Syntax Description
list access-list
Defines the extended access list number or name.
route-map map-name
Defines the route map.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to prevent unauthorized sources from registering with the rendezvous point (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 Joins or Prunes destined for a specified rendezvous point (RP) and for a specific list of groups, use the ip pim accept-rp global configuration command. To remove that check, use the no form of this command.
ip pim accept-rp {address | auto-rp} [group-access-list-number]
no ip pim accept-rp {ip-address | auto-rp} [group-access-list-number]
Syntax Description
Defaults
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 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 3access-list 3 permit 224.2.2.2Related Commands
ip pim border
To configure the interface to be the Protocol Independent Multicast (PIM) domain border, use the ip pim border interface configuration command. To remove the border, use the no form of this command.
ip pim border
no ip pim border
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
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
Examples
The following example configures the interface to be the PIM domain border:
interface ethernet 1 ip pim borderRelated Commands
ip pim bsr-candidate
To configure the router to announce its candidacy as a bootstrap router (BSR), use the ip pim bsr-candidate global configuration command. To remove this router as a candidate for being a bootstrap router, use the no form of this command.
ip pim bsr-candidate type number [hash-mask-length] [priority]
no ip pim bsr-candidate
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
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 10Related Commands
ip pim message-interval
To configure the frequency at which a sparse-mode Protocol Independent Multicast (PIM) router sends periodic sparse-mode Join/Prune PIM messages, use the ip pim message-interval global configuration command. To return to the default interval, use the no form of this command.
ip pim message-interval seconds
no ip pim message-interval [seconds]
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
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
Examples
The following example changes the PIM message interval to 90 seconds:
ip pim message-interval 90Related Commands
Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
Configures the frequency of PIM router-query messages.
ip pim minimum-vc-rate
To configure the minimum traffic rate to keep virtual circuits from being idled, use the ip pim minimum-vc-rate interface configuration command. To restore the default value, use the no form of this command.
ip pim minimum-vc-rate pps
no ip pim minimum-vc-rate
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
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 2500Related Commands
ip pim multipoint-signalling
To enable Protocol Independent Multicast (PIM) to open ATM multipoint switched virtual circuits for each multicast group that a receiver joins, use the ip pim multipoint-signalling interface configuration command. To disable the feature, use the no form of this command.
ip pim multipoint-signalling
no ip pim multipoint-signalling
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
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-signallingRelated Commands
ip pim nbma-mode
To configure a multiaccess WAN interface to be in nonbroadcast multiaccess mode, use the ip pim nbma-mode interface configuration command. To disable this function, use the no form of this command.
ip pim nbma-mode
no ip pim nbma-mode
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
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-modeRelated Commands
ip pim neighbor-filter
To prevent a router from participating in Protocol Independent Multicast (PIM) (for example, to configure stub multicast routing), use the ip pim neighbor-filter interface configuration command. To remove the restriction, use the no form of this command.
ip pim neighbor-filter access-list-number
no ip pim neighbor-filter access-list-number
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
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-routingip pim dense-modeip igmp helper-address 10.0.0.2Router B
ip multicast-routingip pim dense-mode : or ip pim sparse-modeip pim neighbor-filter 1access-list 1 deny 10.0.0.1Related Commands
ip pim query-interval
To configure the frequency of Protocol Independent Multicast (PIM) router-query messages, use the ip pim query-interval interface configuration command. To return to the default interval, use the no form of this command.
ip pim query-interval seconds
no ip pim query-interval [seconds]
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
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 0ip pim query-interval 45Related Commands
Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
ip pim rp-address
To configure the address of a Protocol Independent Multicast (PIM) rendezvous point (RP) for a particular group, use the ip pim rp-address global configuration command. To remove an RP address, use the no form of this command.
ip pim rp-address ip-address [group-access-list-number] [override]
no ip pim rp-address ip-address [group-access-list-number]
Syntax Description
Defaults
No PIM RPs are preconfigured.
Command Modes
Global configuration
Command History
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.33The 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.0ip pim rp-address 147.106.6.22 1Related Commands
ip pim rp-announce-filter
To filter incoming Auto-RP announcement messages coming from the rendezvous point (RP), use the ip pim rp-announce-filter global configuration command. To remove the filter, use the no form of this command.
ip pim rp-announce-filter rp-list access-list-number group-list access-list-number
no ip pim rp-announce-filter rp-list access-list-number group-list access-list-number
Syntax Description
Defaults
All RP announcements are accepted.
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows you to configure policies on an AutoRP mapping agent router. These policies allow the mapping agent router to accept or reject incoming candidate RP announcement messages.
This command can be configured so that the AutoRP mapping agent router ignores RP announcement messages from specific or unknown routers. You can also filter RP announcement messages from an RP for specific group prefixes, which will restrict the AutoRP mapping agent router to be the candidate RP for the ranges not filtered on the mapping agent.
Note
If more than one AutoRP mapping agent router is present in the system, you must configure the same filters on all AutoRP mapping agent routers to avoid inconsistencies in AutoRP operations.
If no ip pim rp-announce-filter commands are configured, an AutoRP mapping agent router will accept any candidate RP announcement messages from any routers. Configure one or more ip pim rp-announce-filter commands on the mapping agents to filter out unwanted AutoRP announcement messages.
The group-list access-list keyword must always be defined when the ip pim rp-announce-filter command is used. Omitting this option permit all multicast groups, rendering the command useless.
Unlike the access-list command, you can enter the ip pim rp-announce-filter command in any desired order. A received RP announce message is only then accepted if it is not blocked by any of the configured ip pim rp-announce-filter commands.
Configure this command on the Protocol Independent Multicast (PIM) RP mapping agent. If more than one RP mapping agent is used, it is recommended to make the filters among them consistent so that there are no conflicts in the 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 15.255.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, use the ip pim rp-candidate global configuration command. To remove this router as a candidate for being an RP, use the no form of this command.
ip pim rp-candidate type number [group-list access-list-number]
no ip pim rp-candidate
Syntax Description
Defaults
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 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 4access-list 4 permit 239.0.0.0 0.255.255.255Related Commands
Configures the router to announce its candidacy as a BSR.
Filters incoming Auto-RP announcement messages coming from the RP.
ip pim send-rp-announce
To use Auto-RP to configure which groups the router is willing to act as rendezvous point (RP) for, use the ip pim send-rp-announce global configuration command. To deconfigure this router to be the RP, use the no form of this command.
ip pim send-rp-announce type number scope ttl group-list access-list-number
no ip pim send-rp-announce
Syntax Description
Defaults
Auto-RP is disabled.
Command Modes
Global configuration
Command History
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 5access-list 5 permit 224.0.0.0 15.255.255.255Related Commands
ip pim send-rp-discovery
To configure the router to be an rendezvous point (RP)-mapping agent, use the ip pim send-rp-discovery global configuration command. To restore the default value, use the no form of this command.
ip pim send-rp-discovery [type number] scope ttl
no ip pim send-rp-discovery
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 PIM domain.
When Auto-RP is used, the following steps occur:
1.
2.
3.
Examples
The following example limits Auto-RP RP Discovery messages to 20 hops:
ip pim send-rp-discovery ethernet0 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 global configuration command. To restore the default value, use the no form of this command.
ip pim spt-threshold {kbps | infinity} [group-list access-list-number]
no ip pim spt-threshold
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 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 4ip pim vc-count
To change the maximum number of virtual circuits that Protocol Independent Multicast (PIM) can open, use the ip pim vc-count interface configuration command. To restore the default value, use the no form of this command.
ip pim vc-count number
no ip pim vc-count
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
Examples
The following example allows PIM to open a maximum of 250 virtual circuits:
ip pim vc-count 250Related Commands
ip pim version
To configure the Protocol Independent Multicast (PIM) version of the interface, use the ip pim version interface configuration command. To restore the default value, use the no form of this command.
ip pim version [1 | 2]
no ip pim version
Syntax Description
Defaults
Version 2
Command Modes
Interface configuration
Command History
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 1ip rtp compression-connections
To specify the total number of Real-Time Transport Protocol (RTP) header compression connections that can exist on an interface, use the ip rtp compression-connections interface configuration command. To restore the default value, use the no form of this command.
ip rtp compression-connections number
no ip rtp compression-connections
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
Examples
The following example changes the number of RTP header compression connections supported to 150:
interface serial 0encapsulation pppip rtp header-compressionip rtp compression-connections 150Related Commands
ip rtp header-compression
To enable Real-Time Transport Protocol (RTP) header compression, use the ip rtp header-compression interface configuration command. To disable RTP header compression, use the no form of this command.
ip rtp header-compression [passive]
no ip rtp header-compression [passive]
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
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 0encapsulation pppip rtp header-compressionip rtp compression-connections 10Related Commands
ip sdr cache-timeout
To limit how long a Session Directory Protocol (sdr) cache entry stays active in the cache, use the ip sdr cache-timeout global configuration command. To restore the default value, use the no form of this command.
ip sdr cache-timeout minutes
no ip sdr cache-timeout
Syntax Description
Defaults
Disabled, which means entries are never deleted from the cache.
Command Modes
Global configuration
Command History
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 30Related Commands
Deletes an sdr cache entry or the entire sdr cache.
Displays the session directory cache.
ip sdr listen
To enable the Cisco IOS software to listen to session directory advertisements, use the ip sdr listen interface configuration command. To disable the function, use the no form of this command.
ip sdr listen
no ip sdr listen
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command replaces the ip sd listen command, which is obsolete.
Session Directory Protocol (sdr) is a multicast application for setting up desktop conferencing sessions. It allocates group addresses and allows the user to specify the scope of the group and whether audio, video, or whiteboard applications will be invoked when users open the session.
Use this command to store session advertisements sent to the group. The ip sdr listen command merely enables the software to listen to session directory advertisements. The router joins the default session directory group (group 224.2.127.254) on the interface. Use this command to get contact information.
Examples
The following example enables a router to listen to session directory advertisements:
ip sdr listenRelated Commands
Deletes an sdr cache entry or the entire sdr cache.
Displays the session directory cache.
show frame-relay ip rtp header-compression
To show Frame Relay Real-Time Transport Protocol (RTP) header compression statistics, use the show frame-relay ip rtp header-compression EXEC command.
show frame-relay ip rtp header-compression [interface type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show frame-relay ip rtp header-compression command:
Router# show frame-relay ip rtp header-compressionDLCI 17 Link/Destination info: ip 165.3.3.2Interface Serial0:Rcvd: 0 total, 0 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 6000 total, 5998 compressed,227922 bytes saved, 251918 bytes sent1.90 efficiency improvement factorConnect: 16 rx slots, 16 tx slots, 2 long searches, 2 misses99% hit ratio, five minute miss rate 0 misses/sec, 0 maxTable 100 describes the significant fields in the display.
Related Commands
show ip dvmrp route
To display the contents of the Distance Vector Multicast Routing Protocol (DVMRP) routing table, use the show ip dvmrp route EXEC command.
show ip dvmrp route [name | ip-address]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output of the show ip dvmrp route command:
Router# show ip dvmrp routeDVMRP Routing Table - 1 entry171.68.0.0/16 [100/11] uptime 07:55:50, expires 00:02:52via 137.39.3.93, Tunnel3Table 101 describes the fields shown in the display
Related Commands
show ip igmp groups
To display the multicast groups that are directly connected to the router and that were learned via Internet Group Management Protocol (IGMP), use the show ip igmp groups EXEC command.
show ip igmp groups [group-name | group-address | type number]
Syntax Description
Command Modes
EXEC
Command History
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 groupsIGMP Connected Group MembershipGroup Address Interface Uptime Expires Last Reporter224.0.255.1 Ethernet0 18:51:41 0:02:15 198.92.37.192224.2.226.60 Ethernet0 1:51:31 0:02:17 198.92.37.192224.2.127.255 Ethernet0 18:51:45 0:02:17 198.92.37.192226.2.2.2 Ethernet1 18:51:47 never 0.0.0.0224.2.0.1 Ethernet0 18:51:43 0:02:14 198.92.37.192225.2.2.2 Ethernet0 18:51:43 0:02:21 198.92.37.33225.2.2.2 Ethernet1 18:51:47 never 0.0.0.0225.2.2.4 Ethernet0 18:18:02 0:02:20 198.92.37.192225.2.2.4 Ethernet1 18:23:32 0:02:55 198.92.36.128Table 102 describes the fields shown in the display.
Related Commands
Configures the frequency at which the Cisco IOS software sends IGMP host-query messages.
show ip igmp interface
To display multicast-related information about an interface, use the show ip igmp interface EXEC command.
show ip igmp interface [type number]
Syntax Description
Command Modes
EXEC
Command 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 198.92.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 198.92.37.33No multicast groups joinedEthernet1 is up, line protocol is upInternet address is 198.92.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 198.92.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 103 describes the fields shown in the display.
Table 103 show ip igmp interface Field Descriptions
Ethernet0 is up, line protocol is up
Interface type, number, and status.
Internet address is...
subnet mask is...Internet address of the interface and subnet mask being applied to the interface, as specified with the ip address command.
IGMP is enabled on interface
Indicates whether IGMP has been enabled on the interface with the ip pim command.
IGMP query interval is 60 seconds
Interval at which the Cisco IOS software sends PIM router-query messages, as specified with the ip igmp query-interval command.
Inbound IGMP access group is not set
Indicates whether an IGMP access group has been configured with the ip igmp access-group command.
Multicast routing is enabled on interface
Indicates whether multicast routing has been enabled on the interface with the ip pim command.
Multicast TTL threshold is 0
Packet time-to-threshold, as specified with the ip multicast ttl-threshold command.
Multicast designated router (DR) is...
IP address of the designated router for this LAN segment (subnet).
Multicast groups joined:
No multicast groups joinedIndicates whether this interface is a member of any multicast groups and, if so, lists the IP addresses of the groups.
Related Commands
show ip mcache
To display the contents of the IP fast-switching cache, use the show ip mcache EXEC command.
show ip mcache [group [source]]
Syntax Description
Command Modes
EXEC
Command History
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-sourceIP Multicast Fast-Switching Cache(204.62.246.73/32, 224.2.143.24), Fddi0, Last used: 00:00:00Ethernet0 MAC Header: 01005E028F1800000C1883D30800Ethernet1 MAC Header: 01005E028F1800000C1883D60800Ethernet2 MAC Header: 01005E028F1800000C1883D40800Ethernet3 MAC Header: 01005E028F1800000C1883D70800Table 104 describes the significant fields in the display.
show ip mpacket
To display the contents of the circular cache-header buffer, use the show ip mpacket EXEC command.
show ip mpacket [source-address | name] [group-address | name] [detail]
Syntax Description
Command Modes
EXEC
Command History
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 smallgroupIP Multicast Header Cache - entry count:6, next index: 7Key: id/ttl timestamp (name) source groupD782/117 206416.908 (ABC-xy.company.com) 198.15.228.10 224.5.6.77302/113 206417.908 (school.edu) 147.12.2.17 224.5.6.76CB2/114 206417.412 (MSSRS.company.com) 154.2.19.40 224.5.6.7D782/117 206417.868 (ABC-xy.company.com) 198.15.228.10 224.5.6.7E2E9/123 206418.488 (Newman.com) 211.1.8.10 224.5.6.71CA7/127 206418.544 (teller.company.com) 192.4.6.10 224.5.6.7Table 105 describes the fields in the display.
Related Commands
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 table, use the show ip mroute EXEC command.
show ip mroute [group-name | group-address] [source] [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
EXEC
Command 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 source, group (S,G) entries from star, group (*,G) entries. The star 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, via Reverse Path Forwarding [RPF]).
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-audioIP Multicast Routing TableFlags: D - Dense, S - Sparse, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit setTimers: Uptime/ExpiresInterface 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: DCIncoming interface: Null, RPF neighbor 0.0.0.0, DvmrpOutgoing interface list:Ethernet0, Forward/Dense, 0:57:31/0:02:52Tunnel0, 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: 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, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit setTimers: Uptime/ExpiresInterface state: Interface, Next-Hop, State/Mode(*, 224.0.255.3), uptime 5:29:15, RP is 198.92.37.2, flags: SCIncoming interface: Tunnel0, RPF neighbor 10.3.35.1, DvmrpOutgoing 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: 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 VCD value, because an ATM interface with PIM multipoint signaling is enabled:
Router# show ip mroute 224.1.1.1IP Multicast Routing TableFlags: D - Dense, S - Sparse, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPTTimers: Uptime/ExpiresInterface state: Interface, Next-Hop or VCD, State/Mode(*, 224.1.1.1), 00:03:57/00:02:54, RP 130.4.101.1, flags: SJIncoming interface: Null, RPF nbr 0.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, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPTTimers: Uptime/ExpiresInterface 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: CLJTThe following is sample output from the show ip mroute command with the active keyword:
Router# show ip mroute activeActive IP Multicast Sources - sending >= 4 kbpsGroup: 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 97Source: 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 97Source: 130.129.52.160 (webcast3-e1.acm97.interop.net)Rate: 3 pps/31 kbps(1sec), 63 kbps(last 19 secs), 65 kbps(life avg)Table 106 describes the significant fields shown in the displays.
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 107 describes the significant fields shown in the display.
Related Commands
ip multicast-routing
Enables IP multicast routing or multicast distributed switching.
Enables PIM on an interface.
show ip pim bsr
To display the bootstrap router (BSR) information, use the show ip pim bsr EXEC command.
show ip pim bsr
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The output includes elected BSR information and information about the locally configured candidate 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: 171.69.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: 171.69.143.28(Ethernet0), Group acl: 6Table 108 describes the fields 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 EXEC command.
show ip pim interface [type number] [count]
Syntax Description
type
(Optional) Interface type.
number
(Optional) Interface number.
count
(Optional) Number of packets received and sent out the interface.
Command Modes
EXEC
Command History
Usage Guidelines
This command works only on interfaces that are configured for PIM.
Examples
The following is sample output from the show ip pim interface command:
Router# show ip pim interfaceAddress Interface Mode Neighbor Query DRCount Interval198.92.37.6 Ethernet0 Dense 2 30 198.92.37.33198.92.36.129 Ethernet1 Dense 2 30 198.92.36.13110.1.37.2 Tunnel0 Dense 1 30 0.0.0.0The following is sample output from the show ip pim interface command with the count keyword:
Router# show ip pim interface countAddress Interface FS Mpackets In/Out171.69.121.35 Ethernet0 * 548305239/13744856171.69.121.35 Serial0.33 * 8256/67052912198.92.12.73 Serial0.1719 * 219444/862191Table 109 describes the fields shown in the display.
Related Commands
Enables PIM on an interface.
Lists the PIM neighbors discovered by the Cisco IOS software.
show ip pim neighbor
To list the PIM neighbors discovered by the Cisco IOS software, use the show ip pim neighbor EXEC command.
show ip pim neighbor [type number]
Syntax Description
Command Modes
EXEC
Command 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 Address Interface Uptime Expires Mode198.92.37.2 Ethernet0 17:38:16 0:01:25 Dense198.92.37.33 Ethernet0 17:33:20 0:01:05 Dense (DR)198.92.36.131 Ethernet1 17:33:20 0:01:08 Dense (DR)198.92.36.130 Ethernet1 18:56:06 0:01:04 Dense10.1.22.9 Tunnel0 19:14:59 0:01:09 DenseTable 110 describes the 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 EXEC command.
show ip pim rp [group-name | group-address | mapping]
Syntax Description
Command Modes
EXEC
Command 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, first tries to send PIM version 2 register packets. If that 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: 224.2.240.30, RP: 171.69.10.13, v1, uptime 1d03h, expires 00:04:17Group: 224.1.127.255, RP: 171.69.10.13, v1, uptime 16:39:28, expires 00:04:05Group: 224.2.127.254, RP: 171.69.10.13, v1, uptime 4d01h, expires 00:03:42Group: 224.2.128.253, RP: 171.69.10.13, v1, uptime 12:06:25, expires 00:04:17Group: 224.2.182.251, RP: 171.69.10.13, v1, uptime 3d10h, expires 00:03:16The 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 RPThis system is an RP-mapping agentGroup(s) 224.0.1.39/32, uptime: 1w4d, expires: neverRP 171.69.10.13 (sj-eng-mbone.cisco.com)Info source: localGroup(s) 224.0.1.40/32, uptime: 1w4d, expires: neverRP 171.69.10.13 (sj-eng-mbone.cisco.com)Info source: localGroup(s) 239.255.0.0/16, uptime: 1d03h, expires: 00:02:28RP 171.69.143.25 (lwei-cisco-isdn.cisco.com), PIMv2 v1Info source: 171.69.143.25 (lwei-cisco-isdn.cisco.com)Group(s): 224.0.0.0/4, StaticRP: 171.69.10.13 (sj-eng-mbone.cisco.com)Table 111 describes the fields in the displays.
show ip pim rp-hash
To display which rendezvous points (RP) is being selected for a specified group, use the show ip pim rp-hash EXEC command.
show ip pim rp-hash group
Syntax Description
Command Modes
EXEC
Command 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.21.24.12 (mt1-47a.cisco.com), v2Info source: 172.21.24.12 (mt1-47a.cisco.com), via bootstrapUptime: 05:15:33, expires: 00:02:01Table 112 describes the fields in the display.
show ip pim vc
To display ATM VC status information for multipoint VCs opened by Protocol Independent Multicast (PIM), use the show ip pim vc EXEC command.
show ip pim vc [group-address | name] [type number]
Syntax Description
group-address | name
(Optional) IP multicast group or name. Displays only the single group.
type number
(Optional) Interface type and number. Displays only the single ATM interface.
Defaults
Displays VC status information for all ATM interfaces.
Command Modes
EXEC
Command History
Examples
The following is sample output for the show ip pim vc command:
Router# show ip pim vcIP Multicast ATM VC StatusATM0/0 VC count is 5, max is 200Group VCD Interface Leaf Count Rate224.2.2.2 26 ATM0/0 1 0 pps224.1.1.1 28 ATM0/0 1 0 pps224.4.4.4 32 ATM0/0 2 0 pps224.5.5.5 35 ATM0/0 1 0 ppsTable 113 describes the significant fields in the display.
Related Commands
Enables PIM to open ATM multipoint switched virtual circuits for each multicast group that a receiver joins.
show ip rpf
To display how IP multicast routing does Reverse-Path Forwarding (RPF), use the show ip rpf EXEC command.
show ip rpf {source-address | name}
Syntax Description
source-address | name
Source address or name of the host for which the RPF information is displayed.
Command Modes
EXEC
Command History
Usage Guidelines
The router can Reverse-Path Forward from multiple routing tables (that is, the unicast routing table, DVMRP routing table, or static mroutes). This command tells you where the information is retrieved from.
Examples
The following is sample output of the show ip rpf command:
Router# show ip rpf 171.69.10.13RPF information for sj-eng-mbone.cisco.com (171.69.10.13)RPF interface: BRI0RPF neighbor: eng-isdn-pri3.cisco.com (171.69.121.10)RPF route/mask: 171.69.0.0/255.255.0.0RPF type: unicastTable 114 describes the significant fields in the display.
show ip rtp header-compression
To show Real-Time Transport Protocol (RTP) header compression statistics, use the show ip rtp header-compression EXEC command.
show ip rtp header-compression [type number] [detail]
Syntax Description
type number
(Optional) Interface type and number.
detail
(Optional) Displays details of each connection.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip rtp header-compression command:
Router# show ip rtp header-compressionRTP/UDP/IP header compression statistics:Interface Serial1:Rcvd: 0 total, 0 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 430 total 429 compressed,15122 bytes saved, 139318 bytes sent1.10 efficiency improvement factorConnect: 16 rx slots, 16 tx slots, 1 long searches, 1 misses99% hit ratio, five minute miss rate 0 misses/sec, 0 max.Table 115 describes the significant fields in the display.
Related Commands
show ip sdr
To display the session directory cache, use the show ip sdr EXEC command.
show ip sdr [group | "session-name" | detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
If the router is configured to be a member of 224.2.127.254 (the default sd group), it will cache sdr announcements.
If no arguments or keywords are used with this command, the system displays a sorted list of session names.
Examples
The following is sample output of the show ip sdr command:
Router# show ip sdrSDR Cache - 198 entries !Cannes Film Festival Alan Kay: Georgia Tech Distinguished Lecture ANL TelePresence Microscopy Collaboratory ASC MSRC Ribbon Cutting Ceremony audio test Basler Fasnacht 1997 ! BayLISA meeting Bellcore testing Bellcore testing2 Bielsko-Biala calren2 - private Cannes Testing Cbay session CERN ATLAS CERN LEPC meeting CERN LHCC CILEA pre-test for Archaeonet cisco Beta cisco PIM users CMU CMU-UKA CRAY T3E (Course)Table 116 describes the fields in the display.
Table 116 show ip sdr Field Descriptions
SDR Cache - x entries
Number of entries (sessions) in the cache.
!Cannes Film Festival
Name of session.
Related Commands
