The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To enable debugging of IP multicast routing, use the debug platform ip multicast command in EXEC mode. To disable debugging, use the no form of this command.
debug platform ip multicast { all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry | rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
no debug platform ip multicast { all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry | rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
all |
Displays all platform IP-multicast event debug messages.
|
||
mdb |
Displays IP-multicast debug messages for multicast distributed fast switching (MDFS) multicast descriptor block (mdb) events. |
||
mdfs-rp-retry |
Displays IP-multicast MDFS rendezvous point (RP) retry event debug messages. |
||
midb |
Displays IP-multicast MDFS multicast interface descriptor block (MIDB) debug messages. |
||
mroute-rp |
Displays IP-multicast RP event debug messages. |
||
resources |
Displays IP-multicast hardware resource debug messages. |
||
retry |
Displays IP-multicast retry processing event debug messages. |
||
rpf-throttle |
Displays IP-multicast reverse path forwarding (RPF) throttle event debug messages. |
||
snoop-events |
Displays IP-multicast IGMP snooping event debug messages. |
||
software-forward |
Displays IP-multicast software forwarding event debug messages. |
||
swidb-events |
Displays IP-multicast MDFS software interface descriptor block (swidb) or global event debug messages. |
||
vlan-locks |
Displays IP-multicast VLAN lock and unlock event debug messages. |
Debugging is disabled.
User EXEC
Privileged EXEC
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
The undebug platform ip multicast command is the same as the no debug platform ip multicast command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can start a session from the stack master by using the session switch-number EXEC command, and then enter the debug command at the command-line prompt of the stack member. You also can use the remote command stack-member-number LINE EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Command |
Description |
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To control whether or not all hosts on a Layer 2 interface can join one or more IP multicast groups by applying an Internet Group Management Protocol (IGMP) profile to the interface, use the ip igmp filter interface configuration command on the switch stack or on a standalone switch. To remove the specified profile from the interface, use the no form of this command.
ip igmp filter profile number
no ip igmp filter
profile number |
The IGMP profile number to be applied. The range is 1 to 4294967295. |
No IGMP filters are applied.
Interface configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
You can apply IGMP filters only to Layer 2 physical interfaces; you cannot apply IGMP filters to routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
An IGMP profile can be applied to one or more switch port interfaces, but one port can have only one profile applied to it.
This example shows how to configure IGMP profile 40 to permit the specified range of IP multicast addresses, then shows how to apply that profile to a port as a filter:
Switch(config)# ip igmp profile 40 Switch(config-igmp-profile)# permit Switch(config-igmp-profile)# range 233.1.1.1 233.255.255.255 Switch(config-igmp-profile)# exit Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# ip igmp filter 40
This example shows how to apply IGMP profile 22 to a port:
Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# ip igmp filter 22
You can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
Command | Description |
Configures and enters IGMP Filter Profile configuration mode. | |
show ip dhcp snooping statistics | Displays DHCP snooping statistics. |
To set the maximum number of Internet Group Management Protocol (IGMP) groups that a Layer 2 interface can join or to configure the IGMP throttling action when the maximum number of entries is in the forwarding table, use the ip igmp max-groups interface configuration command on the switch stack or on a standalone switch. To set the maximum back to the default, which is to have no maximum limit, or to return to the default throttling action, which is to drop the report, use the no form of this command.
ip igmp max-groups { max number | action { deny | replace} }
no ip igmp max-groups { max number | action}
max number |
The maximum number of IGMP groups that an interface can join. The range is 0 to 4294967294. The default is no limit. |
action deny |
Drops the next IGMP join report when the maximum number of entries is in the IGMP snooping forwarding table. This is the default action. |
action replace |
Replaces the existing group with the new group for which the IGMP report was received when the maximum number of entries is in the IGMP snooping forwarding table. |
The default maximum number of groups is no limit.
After the switch learns the maximum number of IGMP group entries on an interface, the default throttling action is to drop the next IGMP report that the interface receives and to not add an entry for the IGMP group to the interface.
Interface configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
You can use this command only on Layer 2 physical interfaces and on logical EtherChannel interfaces. You cannot set IGMP maximum groups for routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
Follow these guidelines when configuring the IGMP throttling action:
If you configure the throttling action as deny and set the maximum group limitation, the entries that were previously in the forwarding table are not removed but are aged out. After these entries are aged out, when the maximum number of entries is in the forwarding table, the switch drops the next IGMP report received on the interface.
If you configure the throttling action as replace and set the maximum group limitation, the entries that were previously in the forwarding table are removed. When the maximum number of entries is in the forwarding table, the switch replaces a randomly selected multicast entry with the received IGMP report.
When the maximum group limitation is set to the default (no maximum), entering the ip igmp max-groups {deny | replace} command has no effect.
This example shows how to limit to 25 the number of IGMP groups that a port can join:
Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# ip igmp max-groups 25
This example shows how to configure the switch to replace the existing group with the new group for which the IGMP report was received when the maximum number of entries is in the forwarding table:
Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# ip igmp max-groups action replace
You can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
To create an Internet Group Management Protocol (IGMP) profile and enter IGMP profile configuration mode, use the ip igmp profile global configuration command on the switch stack or on a standalone switch. From this mode, you can specify the configuration of the IGMP profile to be used for filtering IGMP membership reports from a switch port. To delete the IGMP profile, use the no form of this command.
ip igmp profile profile number
no ip igmp profile profile number
profile number |
The IGMP profile number being configured. The range is from 1 to 4294967295. |
No IGMP profiles are defined. When configured, the default action for matching an IGMP profile is to deny matching addresses.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
deny—Specifies that matching addresses are denied; this is the default condition.
exit—Exits from igmp-profile configuration mode.
no—Negates a command or resets to its defaults.
permit—Specifies that matching addresses are permitted.
range—Specifies a range of IP addresses for the profile. This can be a single IP address or a range with a start and an end address.
When entering a range, enter the low IP multicast address, a space, and the high IP multicast address.
You can apply an IGMP profile to one or more Layer 2 interfaces, but each interface can have only one profile applied to it.
This example shows how to configure IGMP profile 40 that permits the specified range of IP multicast addresses:
Switch(config)# ip igmp profile 40 Switch(config-igmp-profile)# permit Switch(config-igmp-profile)# range 233.1.1.1 233.255.255.255
You can verify your settings by using the show ip igmp profile privileged EXEC command.
Command | Description |
Applies IGMP profile to the interface. | |
Displays configured IGMP profiles specified by the command. |
To globally enable Internet Group Management Protocol (IGMP) snooping on the switch or to enable it on a per-VLAN basis, use the ip igmp snooping global configuration command on the switch stack or on a standalone switch. To return to the default setting, use the no form of this command.
ip igmp snooping [ vlan vlan-id]
no ip igmp snooping [ vlan vlan-id]
vlan vlan-id |
(Optional) Enables IGMP snooping on the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
IGMP snooping is globally enabled on the switch.
IGMP snooping is enabled on VLAN interfaces.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
When IGMP snooping is enabled globally, it is enabled in all of the existing VLAN interfaces. When IGMP snooping is globally disabled, it is disabled on all of the existing VLAN interfaces.
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
This example shows how to globally enable IGMP snooping:
Switch(config)# ip igmp snooping
This example shows how to enable IGMP snooping on VLAN 1:
Switch(config)# ip igmp snooping vlan 1
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Enables IGMP report suppression. | |
Displays IGMP snooping configurations. | |
Displays the IGMP snooping multicast table. | |
Displays the IGMP snooping multicast router ports. | |
Displays the configuration and operation information for the IGMP querier. |
To configure how often Internet Group Management Protocol (IGMP) snooping will send query messages in response to receiving an IGMP leave message, use the ip igmp snooping last-member-query-count command in global configuration mode. To set count to the default value, use the no form of the command.
ip igmp snooping [ vlan vlan-id] last-member-query-count count
no ip igmp snooping [ vlan vlan-id] last-member-query-count count
vlan vlan-id |
(Optional) Sets the count value on a specific VLAN ID. The range is from 1 to 1001. Do not enter leading zeroes. |
count |
The interval at which query messages are sent, in milliseconds. The range is from 1 to 7. The default is 2. |
A query is sent every 2 milliseconds.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
When a multicast host leaves a group, the host sends an IGMP leave message. To check if this host is the last to leave the group, IGMP query messages are sent when the leave message is seen until the last-member-query-interval timeout period expires. If no response to the last-member queries are received before the timeout period expires, the group record is deleted.
Use the ip igmp snooping last-member-query-interval command to configure the timeout period.
When both IGMP snooping immediate-leave processing and the query count are configured, immediate-leave processing takes precedence.
![]() Note | Do not set the count to 1 because the loss of a single packet (the query packet from the switch to the host or the report packet from the host to the switch) may result in traffic forwarding being stopped even if there is still a receiver. Traffic continues to be forwarded after the next general query is sent by the switch, but the interval during which a receiver may not receive the query could be as long as 1 minute (with the default query interval). |
The leave latency in Cisco IOS software may increase by up to one last-member-query-interval (LMQI) value when the switch is processing more than one leave within an LMQI. In this case, the average leave latency is determined by the (count + 0.5) * LMQI. The result is that the default leave latency can range from 2.0 to 3.0 seconds with an average of 2.5 seconds under a higher load of IGMP leave processing. The leave latency under load for the minimum LMQI value of 100 milliseconds and a count of 1 is from 100 to 200 milliseconds, with an average of 150 milliseconds. This is done to limit the impact of higher rates of IGMP leave messages.
The following example sets the last member query count to 5:
Switch(config)# ip igmp snooping last-member-query-count 5
To enable the Internet Group Management Protocol (IGMP) configurable-leave timer globally or on a per-VLAN basis, use the ip igmp snooping last-member-query-interval command in global configuration mode. Use the no form of the command to return to the default setting.
ip igmp snooping [ vlan vlan-id] last-member-query-interval time
no ip igmp snooping [ vlan vlan-id] last-member-query-interval time
vlan vlan-id |
(Optional) Enables IGMP snooping and the leave timer on the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
time |
Interval time out in seconds. The range is 100 to 32767 milliseconds. |
The default timeout setting is 1000 milliseconds.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
When IGMP snooping is globally enabled, IGMP snooping is enabled on all the existing VLAN interfaces. When IGMP snooping is globally disabled, IGMP snooping is disabled on all the existing VLAN interfaces.
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
Configuring the leave timer on a VLAN overrides the global setting.
The IGMP configurable leave time is only supported on devices running IGMP Version 2.
The configuration is saved in NVRAM.
This example shows how to globally enable the IGMP leave timer for 2000 milliseconds:
Switch(config)# ip igmp snooping last-member-query-interval 2000
This example shows how to configure the IGMP leave timer for 3000 milliseconds on VLAN 1:
Switch(config)# ip igmp snooping vlan 1 last-member-query-interval 3000
This example shows how to configure the IGMP leave timer for 3000 milliseconds on VLAN 1:
Switch(config)# ip igmp snooping vlan 1 last-member-query-interval 3000
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Enables IGMP snooping. | |
enables IGMPv2 immediate leave processing | |
Adds a multicast router port or configures the multicast learning method. | |
Enables IGMP snooping and statically adds a Layer 2 port. | |
Displays IGMP snooping configurations. |
To globally enable the Internet Group Management Protocol (IGMP) querier function in Layer 2 networks, use the ip igmp snooping querier global configuration command. Use the command with keywords to enable and configure the IGMP querier feature on a VLAN interface. To return to the default settings, use the no form of this command.
ip igmp snooping [ vlan vlan-id] querier [ address ip-address | max-response-time response-time | query-interval interval-count | tcn query { count count | interval interval} | timer expiry expiry-time | version version]
no ip igmp snooping [ vlan vlan-id] querier [ address | max-response-time | query-interval | tcn query { count | interval} | timer expiry | version]
vlan vlan-id |
(Optional) Enables IGMP snooping and the IGMP querier function on the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
address ip-address |
(Optional) Specifies a source IP address. If you do not specify an IP address, the querier tries to use the global IP address configured for the IGMP querier. |
max-response-time response-time |
(Optional) Sets the maximum time to wait for an IGMP querier report. The range is 1 to 25 seconds. |
query-interval interval-count |
(Optional) Sets the interval between IGMP queriers. The range is 1 to 18000 seconds. |
tcn query |
(Optional) Sets parameters related to Topology Change Notifications (TCNs). |
count count |
Sets the number of TCN queries to be executed during the TCN interval time. The range is 1 to 10. |
interval interval |
Sets the TCN query interval time. The range is 1 to 255. |
timer expiry expiry-time |
(Optional) Sets the length of time until the IGMP querier expires. The range is 60 to 300 seconds. |
version version |
(Optional) Selects the IGMP version number that the querier feature uses. Select 1 or 2. |
The IGMP snooping querier feature is globally disabled on the switch.
When enabled, the IGMP snooping querier disables itself if it detects IGMP traffic from a multicast router.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use this command to enable IGMP snooping to detect the IGMP version and IP address of a device that sends IGMP query messages, which is also called a querier.
By default, the IGMP snooping querier is configured to detect devices that use IGMP Version 2 (IGMPv2) but does not detect clients that are using IGMP Version 1 (IGMPv1). You can manually configure the max-response-time value when devices use IGMPv2. You cannot configure the max-response-time when devices use IGMPv1. (The value cannot be configured and is set to zero).
Non-RFC compliant devices running IGMPv1 might reject IGMP general query messages that have a non-zero value as the max-response-time value. If you want the devices to accept the IGMP general query messages, configure the IGMP snooping querier to run IGMPv1.
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
This example shows how to globally enable the IGMP snooping querier feature:
Switch(config)# ip igmp snooping querier
This example shows how to set the IGMP snooping querier maximum response time to 25 seconds:
Switch(config)# ip igmp snooping querier max-response-time 25
This example shows how to set the IGMP snooping querier interval time to 60 seconds:
Switch(config)# ip igmp snooping querier query-interval 60
This example shows how to set the IGMP snooping querier TCN query count to 25:
Switch(config)# ip igmp snooping querier tcn count 25
This example shows how to set the IGMP snooping querier timeout to 60 seconds:
Switch(config)# ip igmp snooping querier timer expiry 60
This example shows how to set the IGMP snooping querier feature to version 2:
Switch(config)# ip igmp snooping querier version 2
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Enables IGMP report suppression. | |
Displays IGMP snooping configurations. | |
Displays the IGMP snooping multicast table. |
To enable Internet Group Management Protocol (IGMP) report suppression, use the ip igmp snooping report-suppression global configuration command on the switch stack or on a standalone switch. To disable IGMP report suppression and to forward all IGMP reports to multicast routers, use the no form of this command.
ip igmp snooping report-suppression
no ip igmp snooping report-suppression
This command has no arguments or keywords.
IGMP report suppression is enabled.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports. This feature is not supported when the query includes IGMPv3 reports.
The switch uses IGMP report suppression to forward only one IGMP report per multicast router query to multicast devices. When IGMP report suppression is enabled (the default), the switch sends the first IGMP report from all hosts for a group to all the multicast routers. The switch does not send the remaining IGMP reports for the group to the multicast routers. This feature prevents duplicate reports from being sent to the multicast devices.
If the multicast router query includes requests only for IGMPv1 and IGMPv2 reports, the switch forwards only the first IGMPv1 or IGMPv2 report from all hosts for a group to all of the multicast routers. If the multicast router query also includes requests for IGMPv3 reports, the switch forwards all IGMPv1, IGMPv2, and IGMPv3 reports for a group to the multicast devices.
If you disable IGMP report suppression by entering the no ip igmp snooping report-suppression command, all IGMP reports are forwarded to all of the multicast routers.
This example shows how to disable report suppression:
Switch(config)# no ip igmp snooping report-suppression
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Displays IGMP snooping configurations. |
To configure the IGMP robustness variable globally or on a per-VLAN basis, use the ip igmp snooping robustness-variable command in global configuration mode. Use the no form of the command to return to the default setting.
ip igmp snooping [ vlan vlan-id] robustness-variable number
no ip igmp snooping [ vlan vlan-id] robustness-variable number
vlan vlan-id |
(Optional) Enables IGMP snooping and the leave timer on the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
number |
Robustness variable number. The range is 1 to 3. |
None
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
To enable IGMPv2 immediate leave processing, use the immediate-leave global configuration command on the switch stack or on a standalone switch. To return to the default settings, use the no form of this command.
ip igmp snooping vlan vlan-id immediate-leave
no ip igmp snooping vlan vlan-id immediate-leave
vlan-id |
Enables IGMPv2 immediate leave processing in the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
By default, IGMPv2 immediate leave processing is off.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
To add a multicast router port, use the ip igmp snooping mrouter global configuration command on the switch stack or on a standalone switch. To return to the default settings, use the no form of this command.
By default, there are no multicast router ports.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
The configuration is saved in NVRAM.
This example shows how to configure a port as a multicast router port:
Switch(config)# ip igmp snooping vlan 1 mrouter interface gigabitethernet1/0/2
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Enables IGMP report suppression. | |
Displays IGMP snooping configurations. | |
Displays the IGMP snooping multicast table. | |
Displays the IGMP snooping multicast router ports. | |
Displays the configuration and operation information for the IGMP querier. |
To enable Internet Group Management Protocol (IGMP) snooping and to statically add a Layer 2 port as a member of a multicast group, use the ip igmp snooping vlan static global configuration command on the switch stack or on a standalone switch. Use the no form of this command to remove ports specified as members of a static multicast group.
ip igmp snooping vlan vlan-id static ip-address interface interface-id
no ip igmp snooping vlan vlan-id static ip-address interface interface-id
vlan-id |
Enables IGMP snooping on the specified VLAN. The range is 1 to 1001 and 1006 to 4094. |
ip-address |
Adds a Layer 2 port as a member of a multicast group with the specified group IP address. |
interface interface-id |
|
By default, there are no ports statically configured as members of a multicast group.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
The configuration is saved in NVRAM.
This example shows how to statically configure a host on an interface:
Switch(config)# ip igmp snooping vlan 1 static 224.2.4.12 interface
gigabitEthernet1/0/1
Configuring port gigabitethernet1/0/1 on group 224.2.4.12
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Command | Description |
Enables IGMP report suppression. | |
Displays IGMP snooping configurations. | |
Displays the IGMP snooping multicast table. | |
Displays the IGMP snooping multicast router ports. | |
Displays the configuration and operation information for the IGMP querier. |
To support authentication, authorization, and accounting (AAA) enabling of IP multicast, use the ip multicast auto-enable command. This command allows multicast routing to be enabled dynamically on dialup interfaces using AAA attributes from a RADIUS server. To disable IP multicast for AAA, use the no form of the command.
ip multicast auto-enable
no ip multicast auto-enable
This command has no arguments or keywords.
None
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
This example shows how to enable authentication, authorization, and accounting (AAA) on IP multicast:
Switch(config)# ip multicast auto-enable
To configure a candidate rendezvous point (RP) switch to filter Protocol Independent Multicast (PIM) register messages, use the ip pim accept-register command in global configuration mode. To disable this function, use the no form of this command.
ip pim [ vrf vrf-name ] accept-register { list access-list}
no ip pim [ vrf vrf-name ] accept-register
vrf vrf-name |
(Optional) Configures a PIM register filter on candidate RPs for (S, G) traffic associated with the multicast Virtual Private Network (VPN) routing and forwarding (MVRF) instance specified for the vrf-name argument. |
list access-list |
Specifies the access-list argument as a number or name that defines the (S, G) traffic in PIM register messages to be permitted or denied. The range is 100 to 199 and an expanded range of 2000 to 2699. An IP-named access list can also be used. |
No PIM register filters are configured.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use this command to prevent unauthorized sources from registering with the RP. If an unauthorized source sends a register message to the RP, the RP will immediately send back a register-stop message.
The access list provided for the ip pim accept-register command should only filter on IP source addresses and IP destination addresses. Filtering on other fields (for example, IP protocol or UDP port number) will not be effective and may cause undesired traffic to be forwarded from the RP down the shared tree to multicast group members. If more complex filtering is desired, use the ip multicast boundary command instead.
The following example shows how to permit register packets for any source address sending to any group range, with the exception of source address 172.16.10.1 sending to the SSM group range (232.0.0.0/8). These are denied. These statements should be configured on all candidate RPs because candidate RPs will receive PIM registers from first hop routers or switches.
Switch(config)# ip pim accept-register list ssm-range Switch(config)# ip access-list extended ssm-range Switch(config-ext-nacl)# deny ip any 232.0.0.0 0.255.255.255 Switch(config-ext-nacl)# permit ip any any
To configure the switch to be a candidate BSR, use the ip pim bsr-candidate command in global configuration mode. To remove the switch as a candidate BSR, use the no form of this command.
ip pim [ vrf vrf-name] bsr-candidate interface-id [ hash-mask-length] [ priority]
no ip pim [ vrf vrf-name] bsr-candidate
vrf vrf-name | (Optional) Configures the switch to be a candidate BSR for the Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) instance specified for the vrf-name argument. |
interface-id |
ID of the interface on this switch from which the BSR address is derived to make it a candidate. This interface must be enabled for Protocol Independent Multicast (PIM) using the ip pim command. Valid interfaces include physical ports, port channels, and VLANs. |
hash-mask-length |
(Optional) Length of a mask (32 bits maximum) that is to be ANDed with the group address before the PIMv2 hash function is called. All groups with the same seed hash correspond to the same rendezvous point ( RP). For example, if this value is 24, only the first 24 bits of the group addresses matter. The hash mask length allows one RP to be used for multiple groups. The default hash mask length is 0. |
priority |
(Optional) Priority of the candidate BSR (C-BSR). The range is from 0 to 255. The default priority is 0. The C-BSR with the highest priority value is preferred. |
The switch is not configured to announce itself as a candidate BSR.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
The interface specified for this command must be enabled for Protocol Independent Multicast (PIM) using the ip pim command.
This command configures the switch to send BSR messages to all of its PIM neighbors, with the address of the designated interface as the BSR address.
This command should be configured on backbone switches that have good connectivity to all parts of the PIM domain.
The BSR mechanism is specified in RFC 2362. Candidate RP (C-RP) switches unicast C-RP advertisement packets to the BSR. The BSR then aggregates these advertisements in BSR messages, which it regularly multicasts with a TTL of 1 to the ALL-PIM-ROUTERS group address, 224.0.0.13. The multicasting of these messages is handled by hop-by-hop RPF flooding; so no preexisting IP multicast routing setup is required (unlike with AutoRP). In addition, the BSR does not preselect the designated RP for a particular group range (unlike AutoRP); instead, each switch that receives BSR messages will elect RPs for group ranges based on the information in the BSR messages.
Cisco switches always accept and process BSR messages. There is no command to disable this function.
A longest match lookup is performed on the group prefix that is announced by the BSR C-RPs.
If more than one BSR-learned C-RP are found by the longest match lookup, the C-RP with the lowest priority (configured with the ip pim rp-candidate command) is preferred.
If more than one BSR-learned C-RP have the same priority, the BSR hash function is used to select the RP for a group.
If more than one BSR-learned C-RP return the same hash value derived from the BSR hash function, the BSR C-RP with the highest IP address is preferred.
The following example shows how to configure the IP address of the switch on Gigabit Ethernet interface 1/0/0 to be a BSR C-RP with a hash mask length of 0 and a priority of 192:
Switch(config)# ip pim bsr-candidate GigabitEthernet1/0/1 0 192
Command | Description |
Configures the switch to advertise itself to the BSR as PIM C-RP. |
To enable Protocol Independent Multicast (PIM) dense mode (DM) fallback, use the ip pim dm-fallback command in global configuration mode. To prevent PIM dense mode fallback, use the no form of this command.
ip pim dm-fallback
no ip pim dm-fallback
This command has no arguments or keywords. |
PIM dense mode fallback is enabled for all interfaces on the switch that are configured with either the ip pim dense-mode or ip pim sparse-dense-mode commands.
Global configuration
Release | Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
If you use IP multicast in mission-critical networks, you should avoid the use of PIM-DM (dense mode).
Dense mode fallback describes the event of the PIM mode changing (falling back) from sparse mode (which requires an RP) to dense mode (which does not use an RP). Dense mode fallback occurs when RP information is lost.
If all interfaces are configured with the ip pim sparse-mode command, there is no dense mode fallback because dense mode groups cannot be created over interfaces configured for sparse mode.
Use the no ip pim dm-fallback command to disable PIM-DM flooding on sparse-dense interfaces.
Cause and Effect of Dense Mode Fallback
PIM determines whether a multicast group operates in PIM-DM or PIM-SM mode based solely on the existence of RP information in the group-to-RP mapping cache. If Auto-RP is configured or a bootstrap router (BSR) is used to distribute RP information, there is a risk that RP information can be lost if all RPs, Auto-RP, or the BSR for a group fails due to network congestion. This failure can lead to the network either partially or fully falling back into PIM-DM.
If a network falls back into PIM-DM and AutoRP or BSR is being used, dense mode flooding will occur. Switches that lose RP information will fallback into dense mode and any new states that must be created for the failed group will be created in dense mode.
Effects of Preventing Dense Mode Fallback
Prior to the introduction of PIM-DM fallback prevention, all multicast groups without a group-to-RP mapping would be treated as dense mode.
With the introduction of PIM-DM fallback prevention, the PIM-DM fallback behavior has been changed to prevent dense mode flooding. By default, if all of the interfaces are configured to operate in PIM sparse mode (using the ip pim sparse-mode command), there is no need to configure the no ip pim dm-fallback command (that is, the PIM-DM fallback behavior is enabled by default). If any interfaces are not configured using the ip pim sparse-mode command (for example, using the ip pim sparse-dense-mode command), then the PIM-DM fallback behavior can be explicitly disabled using the no ip pim dm-fallback command.
When the no ip pim dm-fallback command is configured or when ip pim sparse-mode is configured on all interfaces, any existing groups running in sparse mode will continue to operate in sparse mode but will use an RP address set to 0.0.0.0. Multicast entries with an RP address set to 0.0.0.0 will exhibit the following behavior:
Existing (S, G) states will be maintained.
No PIM Join or Prune messages for (*, G) or (S, G, RPbit) are sent.
Received (*, G) or (S, G, RPbit) Joins or Prune messages are ignored.
Received registers are answered with register stop.
Asserts are unchanged.
The (*, G) outgoing interface list (olist) is maintained only for the Internet Group Management Protocol (IGMP) state.
Multicast Source Discovery Protocol (MSDP) source active (SA) messages for RP 0.0.0.0 groups are still accepted and forwarded.
The following example shows how to disable PIM-DM fallback:
Switch(config)# no ip pim dm-fallback
To configure the switch to advertise itself to the BSR as a Protocol Independent Multicast (PIM) Version 2 (PIMv2) candidate rendezvous point (C-RP), use the ip pim rp-candidate command in global configuration mode. To remove this switch as a C-RP, use the no form of this command.
ip pim [ vrf vrf-name] rp-candidate interface-id [ group-list access-list-number]
no ip pim [ vrf vrf-name] rp-candidate interface-id [ group-list access-list-number]
vrf vrf-name |
(Optional) Configures the switch to advertise itself to the BSR as PIMv2 C-RP for the Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) instance specified for the vrf-name argument. |
interface-id |
ID of the interface whose associated IP address is advertised as a candidate RP address. Valid interfaces include physical ports, port channels, and VLANs. |
group-list access-list-number |
(Optional) Specifies the standard IP access list number that defines the group prefixes that are advertised in association with the RP address. |
The switch is not configured to announce itself to the BSR as a PIMv2 C-RP.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use this command to configure the switch to send PIMv2 messages so that it advertises itself as a candidate RP to the BSR.
This command should be configured on backbone switches that have good connectivity to all parts of the PIM domain.
The IP address associated with the interface specified by interface-id will be advertised as the C-RP address.
The interface specified for this command must be enabled for Protocol Independent Multicast (PIM) using the ip pim command.
If the optional group-list keyword and access-list-number argument are configured, the group prefixes defined by the standard IP access list will also be advertised in association with the RP address.
The following example shows how to configure the switch to advertise itself as a C-RP to the BSR in its PIM domain. The standard access list number 4 specifies the group prefix associated with the RP that has the address identified by Gigabit Ethernet interface 1/0/1.
Switch(config)# ip pim rp-candidate GigabitEthernet1/0/1 group-list 4
Command | Description |
Configures a switch to be a candidate BSR. |
To use Auto-RP to configure groups for which the switch will act as a rendezvous point (RP), use the ip pim send-rp-announce command in global configuration mode. To unconfigure this switch as an RP, use the no form of this command.
ip pim [ vrf vrf-name] send-rp-announce interface-id scope ttl-value [ group-list access-list-number] [ interval seconds]
no ip pim [ vrf vrf-name] send-rp-announce interface-id
vrf vrf-name |
(Optional) Uses Auto-RP to configure groups for which the switch will act as a rendezvous point (RP) for the vrf-name argument. |
interface-id |
Enter the interface ID of the interface that identifies the RP address. Valid interfaces include physical ports, port channels, and VLANs. |
scope ttl-value |
Specifies the time-to-live (TTL) value in hops that limits the number of Auto-RP announcements. Enter a hop count that is high enough so that the RP-announce messages reach all mapping agents in the network. There is no default setting. The range is 1 to 255. |
group-list access-list-number |
(Optional) Specifies the standard IP access list number that defines the group prefixes that are advertised in association with the RP address. Enter an IP standard access list number from 1 to 99. If no access list is configured, the RP is used for all groups. |
interval seconds |
(Optional) Specifies the interval between RP announcements in seconds. The total holdtime of the RP announcements is automatically set to three times the value of the interval. The default interval is 60 seconds. The range is 1 to 16383. |
Auto-RP is disabled.
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Enter this command on the switch that you want to be an RP. When you are using Auto-RP to distribute group-to-RP mappings, this command causes the router to send an Auto-RP announcement message to the well-known group CISCO-RP-ANNOUNCE (224.0.1.39). This message announces the router as a candidate RP for the groups in the range described by the access list.
The following example shows how to configure the switch to send RP announcements out all Protocol Independent Multicast (PIM)-enabled interfaces for a maximum of 31 hops. The IP address by which the switch wants to be identified as RP is the IP address associated with Gigabit Ethernet interface 1/0/1 at an interval of 120 seconds:
Switch(config)# ip pim send-rp-announce GigabitEthernet1/0/1 scope 31 group-list 5 interval 120
Command | Description |
Configures the switch to advertise itself to the BSR as PIM C-RP. |
To specify the threshold that must be reached before moving to shortest-path tree (spt), use the ip pim spt-threshold command in global configuration mode. To remove the threshold, use the no form of this command.
ip pim { kbps | infinity} [ group-list access-list]
no ip pim { kbps | infinity} [ group-list access-list]
kbps |
The threshold that must be reached before moving to shortest-path tree (spt). 0 is the only valid entry even though the range is 0 to 4294967. A 0 entry always switches to the source-tree. |
infinity |
Specifies that all sources for the specified group use the shared tree, never switching to the source tree. |
group-list access-list |
(Optional) Specifies an access list number or a specific access list that you have created by name. If the value is 0 or if the group-list access-list option is not used, the threshold applies to all groups. |
Switches to the PIM shortest-path tree (spt).
Global configuration
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
None
The following example makes all sources for access list 16 use the shared tree:
Switch(config)# ip pim spt-threshold infinity group-list 16
To query which neighboring multicast routers or multilayer switches are acting as peers, use the mrinfo command in user EXEC or privileged EXEC mode.
mrinfo [ vrf route-name] [ hostname | address] [ interface-id]
vrf route-name |
(Optional) Specifies the VPN routing or forwarding instance. |
hostname | address |
(Optional) The Domain Name System (DNS) name or IP address of the multicast router or multilayer switch to query. If omitted, the switch queries itself. |
interface-id |
(Optional) Specifies the interface ID. |
The command is disabled.
User EXEC
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
The mrinfo command is the original tool of the multicast backbone (MBONE) to determine which neighboring multicast routers or switches are peering with multicast routers or switches. Cisco routers have supported responding to mrinfo requests since Cisco IOS Release 10.2.
You can query a multicast router or multilayer switch using the mrinfo command. The output format is identical to the multicast routed version of the Distance Vector Multicast Routing Protocol (DVMRP). (The mrouted software is the UNIX software that implements DVMRP.)
The following is sample output from the mrinfo command:
Switch# mrinfo
vrf 192.0.1.0
192.31.7.37 (barrnet-gw.cisco.com) [version cisco 11.1] [flags: PMSA]:
192.31.7.37 -> 192.31.7.34 (sj-wall-2.cisco.com) [1/0/pim]
192.31.7.37 -> 192.31.7.47 (dirtylab-gw-2.cisco.com) [1/0/pim]
192.31.7.37 -> 192.31.7.44 (dirtylab-gw-1.cisco.com) [1/0/pim]
![]() Note |
To display Internet Group Management Protocol (IGMP) filter information, use the show ip igmp filter command in privileged EXEC command mode.
show ip igmp [ vrf vrf-name] filter
vrf vrf-name |
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance. |
IGMP filters are enabled by default.
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
The show ip igmp filter command displays information about all filters defined on the switch.
The following is sample output from the show ip igmp filter command:
Switch# show ip igmp filter
IGMP filter enabled
To display all configured Internet Group Management Protocol (IGMP) profiles or a specified IGMP profile, use the show ip igmp profile privileged EXEC command.
show ip igmp [ vrf vrf-name] profile [ profile number]
vrf vrf-name |
(Optional) Supports the multicast VPN routing and forwarding (VRF) instance. |
profile number |
(Optional) The IGMP profile number to be displayed. The range is 1 to 4294967295. If no profile number is entered, all IGMP profiles are displayed. |
IGMP profiles undefined by default.
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
None
The following example shows the output of the show ip igmp profile privileged EXEC command for profile number 40 on the switch:
Switch# show ip igmp profile 40
IGMP Profile 40
permit
range 233.1.1.1 233.255.255.255
This example shows the output of the show ip igmp profile privileged EXEC command for all profiles configured on the switch:
Switch# show ip igmp profile
IGMP Profile 3
range 230.9.9.0 230.9.9.0
IGMP Profile 4
permit
range 229.9.9.0 229.255.255.255
Command | Description |
Configures and enters IGMP Filter Profile configuration mode. |
To display the Internet Group Management Protocol (IGMP) snooping configuration of the switch or the VLAN, use the show ip igmp snooping command in user or privileged EXEC command mode.
show ip igmp snooping [ groups | mrouter | querier] [ vlan vlan-id] [ detail]
groups | (Optional) Displays the IGMP snooping multicast table. |
mrouter | (Optional) Displays the IGMP snooping multicast router ports. |
querier | (Optional) Displays the configuration and operation information for the IGMP querier. |
vlan vlan-id |
(Optional) Specifies a VLAN; the range is 1 to 1001 and 1006 to 4094. |
detail |
(Optional) Displays operational state information. |
None
User EXEC
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
This is an example of output from the show ip igmp snooping vlan 1 command. It shows snooping characteristics for a specific VLAN:
Switch# show ip igmp snooping vlan 1
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping (minimal) : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
Vlan 1:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
This is an example of output from the show ip igmp snooping command. It displays snooping characteristics for all VLANs on the switch:
Switch# show ip igmp snooping
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping (minimal) : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
Vlan 1:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
Vlan 2:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
<output truncated>
Command | Description |
Enables IGMP snooping. | |
Displays the IGMP snooping multicast table. | |
Displays the IGMP snooping multicast router ports. | |
Displays the configuration and operation information for the IGMP querier. |
To display the Internet Group Management Protocol (IGMP) snooping multicast table for the switch or the multicast information, use the show ip igmp snooping groups privileged EXEC command.
show ip igmp snooping groups [ vlan vlan-id ] [ [ dynamic | user ] [ count] | ip_address]
vlan vlan-id |
(Optional) Specifies a VLAN; the range is 1 to 1001 and 1006 to 4094. Use this option to display the multicast table for a specified multicast VLAN or specific multicast information. |
dynamic |
(Optional) Displays IGMP snooping learned group information. |
user |
(Optional) Displays user-configured group information. |
count |
(Optional) Displays the total number of entries for the specified command options instead of the actual entries. |
ip_address |
(Optional) Characteristics of the multicast group with the specified group IP address. |
Privileged EXEC
User EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
This is an example of output from the show ip igmp snooping groups command without any keywords. It displays the multicast table for the switch:
Switch# show ip igmp snooping groups
Vlan Group Type Version Port List
-------------------------------------------------------------
1 224.1.4.4 igmp Gi1/0/11
1 224.1.4.5 igmp Gi1/0/11
2 224.0.1.40 igmp v2 Gi1/0/15
104 224.1.4.2 igmp v2 Gi2/0/1, Gi2/0/2
104 224.1.4.3 igmp v2 Gi2/0/1, Gi2/0/2
This is an example of output from the show ip igmp snooping groups count command. It displays the total number of multicast groups on the switch:
Switch# show ip igmp snooping groups count
Total number of multicast groups: 2
This is an example of output from the show ip igmp snooping groups vlan vlan-id ip-address command. It shows the entries for the group with the specified IP address:
Switch# show ip igmp snooping groups vlan 104 224.1.4.2
Vlan Group Type Version Port List
-------------------------------------------------------------
104 224.1.4.2 igmp v2 Gi2/0/1, Gi1/0/15
Command | Description |
Enables IGMP snooping. | |
Displays IGMP snooping configurations. |
To display group and IP address entries, use the show ip igmp snooping igmpv2-tracking command in privileged EXEC mode.
![]() Note | The command displays group and IP address entries only for wireless multicast IGMP joins and not for wired joins. This command also displays output only if wireless multicast is enabled. |
show ip igmp snooping igmpv2-tracking
This command has no arguments or keywords.
None
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
To display the Internet Group Management Protocol (IGMP) snooping dynamically learned and manually configured multicast router ports for the switch or for the specified multicast VLAN, use the show ip igmp snooping mrouter privileged EXEC command.
show ip igmp snooping mrouter [ vlan vlan-id]
vlan vlan-id |
(Optional) Specifies a VLAN; the range is 1 to 1001 and 1006 to 4094. |
User EXEC
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
When multicast VLAN registration (MVR) is enabled, the show ip igmp snooping mrouter command displays MVR multicast router information and IGMP snooping information.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
This is an example of output from the show ip igmp snooping mrouter command. It shows how to display multicast router ports on the switch:
Switch# show ip igmp snooping mrouter
Vlan ports
---- -----
1 Gi2/0/1(dynamic)
Command | Description |
Enables IGMP snooping. | |
Displays IGMP snooping configurations. | |
Displays the IGMP snooping multicast table. |
To display the configuration and operation information for the IGMP querier configured on a switch, use the show ip igmp snooping querier user EXEC command.
show ip igmp snooping querier [ vlan vlan-id] [ detail ]
vlan vlan-id |
(Optional) Specifies a VLAN; the range is 1 to 1001 and 1006 to 4094. |
detail |
(Optional) Displays detailed IGMP querier information. |
User EXEC
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use the show ip igmp snooping querier command to display the IGMP version and the IP address of a detected device, also called a querier, that sends IGMP query messages. A subnet can have multiple multicast routers but has only one IGMP querier. In a subnet running IGMPv2, one of the multicast routers is elected as the querier. The querier can be a Layer 3 switch.
The show ip igmp snooping querier command output also shows the VLAN and the interface on which the querier was detected. If the querier is the switch, the output shows the Port field as Router. If the querier is a router, the output shows the port number on which the querier is learned in the Port field.
The show ip igmp snooping querier detail user EXEC command is similar to the show ip igmp snooping querier command. However, the show ip igmp snooping querier command displays only the device IP address most recently detected by the switch querier.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
This is an example of output from the show ip igmp snooping querier command:
Switch> show ip igmp snooping querier
Vlan IP Address IGMP Version Port
---------------------------------------------------
1 172.20.50.11 v3 Gi1/0/1
2 172.20.40.20 v2 Router
This is an example of output from the show ip igmp snooping querier detail command:
Switch> show ip igmp snooping querier detail Vlan IP Address IGMP Version Port ------------------------------------------------------------- 1 1.1.1.1 v2 Fa8/0/1 Global IGMP switch querier status -------------------------------------------------------- admin state : Enabled admin version : 2 source IP address : 0.0.0.0 query-interval (sec) : 60 max-response-time (sec) : 10 querier-timeout (sec) : 120 tcn query count : 2 tcn query interval (sec) : 10 Vlan 1: IGMP switch querier status -------------------------------------------------------- elected querier is 1.1.1.1 on port Fa8/0/1 -------------------------------------------------------- admin state : Enabled admin version : 2 source IP address : 10.1.1.65 query-interval (sec) : 60 max-response-time (sec) : 10 querier-timeout (sec) : 120 tcn query count : 2 tcn query interval (sec) : 10 operational state : Non-Querier operational version : 2 tcn query pending count : 0
Command | Description |
Enables IGMP snooping. | |
Globally enables the IGMP querier function. | |
Displays IGMP snooping configurations. |
To display information about the Protocol Independent Multicast (PIM) register encapsulation and decapsulation tunnels for all VRFs, use the show ip pim all-vrfs tunnel command in privileged EXEC mode.
show ip pim all-vrfs tunnel [ verbose | Tunnel tunnel-interface-number]
verbose |
(Optional) Provides additional information, such as the MAC encapsulation header and platform-specific information. |
Tunnel tunnel-interface-number |
(Optional) Displays tunnel information for a specific tunnel interface specified by tunnel-interface-number. |
Displays tunnel information for all VRFs on all tunnel interfaces.
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
If you use the show ip pim all-vrfs tunnel command without the optional keywords, information about the PIM register encapsulation and de-encapsulation tunnel interfaces for all VRFs is displayed.
The PIM encapsulation tunnel is the register tunnel. An encapsulation tunnel is created for every known rendezvous point (RP) on every switch. The PIM decapsulation tunnel is the register decapsulation tunnel. A decapsulation tunnel is created on the RP for the address that is configured to be the RP address.
To display global information about auto-rp, use the show ip pim autorp command in privileged EXEC mode.
show ip pim autorp
This command has no arguments or keywords.
auto-rp is enabled by default.
Privileged EXEC mode
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
This command displays whether auto-rp is enabled or disabled.
The following command output displays that auto-rp is enabled:
Switch# show ip pim autorp
AutoRP Information:
AutoRP is enabled.
RP Discovery packet MTU is 0.
224.0.1.40 is joined on GigabitEthernet1/0/1.
PIM AutoRP Statistics: Sent/Received
RP Announce: 0/0, RP Discovery: 0/0
To display information related to Protocol Independent Multicast (PIM) bootstrap router (BSR) protocol processing, use the show ip pim bsr-router command in user EXEC or privileged EXEC mode.
show ip pim bsr-router
This command has no arguments or keywords.
None
User EXEC
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
In addition to auto-rp, the BSR RP method can be configured. After the BSR RP method is configured, this command will display the BSR router information.
The following is sample output from the show ip pim bsr-router command:
Switch# show ip pim bsr-router
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 172.16.143.28
Uptime: 04:37:59, BSR Priority: 4, Hash mask length: 30
Next bootstrap message in 00:00:03 seconds
Next Cand_RP_advertisement in 00:00:03 seconds.
RP: 172.16.143.28(Ethernet0), Group acl: 6
To display information about the Protocol Independent Multicast (PIM) register encapsulation and decapsulation tunnels on an interface, use the show ip pim tunnel command.
show ip pim [ vrf vrf-name] tunnel [ Tunnel interface-number | verbose]
vrf vrf-name | (Optional) Specifies a virtual routing and forwarding (VRF) configuration. |
Tunnel interface-number |
(Optional) Specifies the tunnel interface number. |
verbose |
(Optional) Provides additional information, such as the MAC encapsulation header and platform-specific information. |
None
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use the show ip pim tunnel to display information about PIM tunnel interfaces.
PIM tunnel interfaces are used by the IPv4 Multicast Forwarding Information Base (MFIB) for the PIM sparse mode (PIM-SM) registration process. Two types of PIM tunnel interfaces are used by the the IPv4 MFIB:
The PIM Encap Tunnel is dynamically created whenever a group-to-rendezvous point (RP) mapping is learned (through auto-RP, bootstrap router (BSR), or static RP configuration). The PIM Encap Tunnel is used to encapsulate multicast packets sent by first-hop designated routers (DRs) that have directly connected sources.
Similar to the PIM Encap Tunnel, the PIM Decap Tunnel interface is dynamically created—but it is created only on the RP whenever a group-to-RP mapping is learned. The PIM Decap Tunnel interface is used by the RP to decapsulate PIM register messages.
![]() Note | PIM tunnels will not appear in the running configuration. |
The following syslog message appears when a PIM tunnel interface is created:
* %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel<interface_number>, changed state to up
The following is sample output from the show ip pim tunnel taken from an RP. The output is used to verify the PIM Encap and Decap Tunnel on the RP:
Switch# show ip pim tunnel
Tunnel0
Type : PIM Encap
RP : 70.70.70.1*
Source: 70.70.70.1
Tunnel1*
Type : PIM Decap
RP : 70.70.70.1*
Source: -R2#
![]() Note | The asterisk (*) indicates that the router is the RP. The RP will always have a PIM Encap and Decap Tunnel interface. |
To display platform-dependent IP multicast tables and other information, use the show platform ip multicast privileged EXEC command.
show platform ip multicast { acl-full-info | | counters | | groups | | hardware [detail] | interfaces | | locks | | mdfs-routes | | mroute-retry | | retry | | trace }
acl-full-info |
Displays IP multicast routing access control list (ACL) information, specifically the number of outgoing VLANs for which router ACLs at the output cannot be applied in hardware. |
counters |
Displays IP multicast counters and statistics. |
groups |
Displays IP multicast routes per group. |
hardware [detail] |
Displays IP multicast routes loaded into hardware. The optional detail keyword is used to show port members in the destination index and route index. |
interfaces |
Displays IP multicast interfaces. |
locks |
Displays IP multicast destination-index locks. |
mdfs-routes |
Displays multicast distributed fast switching (MDFS) IP multicast routes. |
mroute-retry |
Displays the IP multicast route retry queue. |
retry |
Displays the IP multicast routes in the retry queue. |
trace |
Displays the IP multicast trace buffer. |
Privileged EXEC
Release |
Modification |
---|---|
Cisco IOS 15.0(2)EX1 |
This command was introduced. |
Use this command only when you are working directly with a technical support representative while troubleshooting a problem. Do not use this command unless a technical support representative asks you to do so.
This example shows how to display platform IP multicast routes per group:
Switch# show platform ip multicast groups
Total Number of entries:3
MROUTE ENTRY vrf 0 (*, 224.0.0.0)
Token: 0x0000001f6 flags: C
No RPF interface.
Number of OIF: 0
Flags: 0x10 Pkts : 0
OIF Details:No OIF interface.
DI details
----------
Handle:0x603cf7f8 Res-Type:ASIC_RSC_DI Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
Hardware Indices/Handles: index0:0x51f6 index1:0x51f6
Cookie length 56
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x4 0xe0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Detailed Resource Information (ASIC# 0)
----------------------------------------
al_rsc_di
RM:index = 0x51f6
RM:pmap = 0x0
RM:cmi = 0x0
RM:rcp_pmap = 0x0
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f6
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
Detailed Resource Information (ASIC# 1)
----------------------------------------
al_rsc_di
RM:index = 0x51f6
RM:pmap = 0x0
RM:cmi = 0x0
RM:rcp_pmap = 0x0
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f6
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
==============================================================
RI details
----------
SI details
----------
RM:generic lbl = 0x0
RM:di_handle = 0x51f6
RM:fd const lbl = 0x0
RM:skipid_idx = 0x0
RM:rcp serviceid = 0x0
RM:dejavu prechken= 0x1
RM:local cpu = 0x0
RM:local data = 0x1
RM:remote cpu = 0x0
RM:remote data = 0x1
==============================================================
HTM details
-----------
Handle:0x5d604490 Res-Type:ASIC_RSC_STP_INDEX Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_IPV4_MCAST_ROUTE_STARG ref_count:1
Hardware Indices/Handles: handle0:0x5d604518 handle1:0x5d604580
Detailed Resource Information (ASIC# 0)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x5d604518)
KEY - grp_addr:224.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:240.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 4095 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 0 station_index: 164
capwap_mgid_present: 0 mgid 0
Detailed Resource Information (ASIC# 1)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x5d604580)
KEY - grp_addr:224.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:240.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 4095 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 0 station_index: 164
capwap_mgid_present: 0 mgid 0
==============================================================
MROUTE ENTRY vrf 0 (*, 224.0.1.40)
Token: 0x0000001f8 flags: C IC
RPF interface: Vl121(74238750229529173)): SVI
Token:0x00000021 flags: F IC NS
Number of OIF: 1
Flags: 0x10 Pkts : 0
OIF Details:
Vl121 F IC NS
DI details
----------
Handle:0x603d0000 Res-Type:ASIC_RSC_DI Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
Hardware Indices/Handles: index0:0x51f7 index1:0x51f7
Cookie length 56
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x20 0xe0 0x0 0x1 0x28 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Detailed Resource Information (ASIC# 0)
----------------------------------------
al_rsc_di
RM:index = 0x51f7
RM:pmap = 0x0
RM:cmi = 0x33f
RM:rcp_pmap = 0x0
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f7
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
Detailed Resource Information (ASIC# 1)
----------------------------------------
al_rsc_di
RM:index = 0x51f7
RM:pmap = 0x0
RM:cmi = 0x33f
RM:rcp_pmap = 0x0
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f7
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
==============================================================
RI details
----------
SI details
----------
RM:generic lbl = 0x0
RM:di_handle = 0x51f7
RM:fd const lbl = 0x8
RM:skipid_idx = 0x0
RM:rcp serviceid = 0x0
RM:dejavu prechken= 0x1
RM:local cpu = 0x0
RM:local data = 0x1
RM:remote cpu = 0x1
RM:remote data = 0x1
==============================================================
HTM details
-----------
Handle:0x603d0440 Res-Type:ASIC_RSC_STP_INDEX Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_IPV4_MCAST_ROUTE_STARG ref_count:1
Hardware Indices/Handles: handle0:0x603cfae0 sm handle 0:0x603d0590 handle1:0x603d0520
sm handle 1:0x603d1770
Detailed Resource Information (ASIC# 0)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x603cfae0)
KEY - grp_addr:224.0.1.40 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:0.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 6 station_index: 165
capwap_mgid_present: 0 mgid 0
Detailed Resource Information (ASIC# 1)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x603d0520)
KEY - grp_addr:224.0.1.40 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:0.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 6 station_index: 165
capwap_mgid_present: 0 mgid 0
==============================================================
MROUTE ENTRY vrf 0 (*, 239.255.255.250)
Token: 0x0000003b7d flags: C
No RPF interface.
Number of OIF: 1
Flags: 0x10 Pkts : 95
OIF Details:
Vl131 F NS
DI details
----------
Handle:0x606ffba0 Res-Type:ASIC_RSC_DI Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
Hardware Indices/Handles: index0:0x51f8 index1:0x51f8
Cookie length 56
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x20 0xef 0xff 0xff 0xfa 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Detailed Resource Information (ASIC# 0)
----------------------------------------
al_rsc_di
RM:index = 0x51f8
RM:pmap = 0x0
RM:cmi = 0x0
RM:rcp_pmap = 0x0
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f8
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
Detailed Resource Information (ASIC# 1)
----------------------------------------
al_rsc_di
RM:index = 0x51f8
RM:pmap = 0x0
RM:cmi = 0x0
RM:rcp_pmap = 0x1
RM:force data copy = 0
RM:remote cpu copy = 0
RM:remote data copy = 0
RM:local cpu copy = 0
RM:local data copy = 0
al_rsc_cmi
RM:index = 0x51f8
RM:cti_lo[0] = 0x0
RM:cti_lo[1] = 0x0
RM:cti_lo[2] = 0x0
RM:cpu_q_vpn[0] = 0x0
RM:cpu_q_vpn[1] = 0x0
RM:cpu_q_vpn[2] = 0x0
RM:npu_index = 0x0
RM:strip_seg = 0x0
RM:copy_seg = 0x0
==============================================================
RI details
----------
ASIC# 0
Replication list :
------------------
Total #ri : 0
start_ri : 15
common_ret : 0
ASIC# 1
Replication list :
------------------
Total #ri : 6
start_ri : 15
common_ret : 0
Replication entry rep_ri 0xF #elem = 1
0) ri[0]=50 port=58 dirty=0
ASIC# 2
Replication list :
------------------
Total #ri : 0
start_ri : 0
common_ret : 0
SI details
----------
RM:generic lbl = 0x0
RM:di_handle = 0x51f8
RM:fd const lbl = 0x8
RM:skipid_idx = 0x0
RM:rcp serviceid = 0x0
RM:dejavu prechken= 0x1
RM:local cpu = 0x0
RM:local data = 0x1
RM:remote cpu = 0x0
RM:remote data = 0x1
==============================================================
HTM details
-----------
Handle:0x606ff6f8 Res-Type:ASIC_RSC_STP_INDEX Asic-Num:255
Feature-ID:AL_FID_L3_MULTICAST_IPV4 Lkp-ftr-id:LKP_FEAT_IPV4_MCAST_ROUTE_STARG ref_count:1
Hardware Indices/Handles: handle0:0x606ff3e0 sm handle 0:0x60ab9160 handle1:0x606ff378
sm handle 1:0x60ab6cc0
Detailed Resource Information (ASIC# 0)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x606ff3e0)
KEY - grp_addr:239.255.255.250 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:0.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 0 station_index: 178
capwap_mgid_present: 0 mgid 0
Detailed Resource Information (ASIC# 1)
----------------------------------------
Number of HTM Entries: 1
Entry #0: (handle 0x606ff378)
KEY - grp_addr:239.255.255.250 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
MASK - grp_addr:0.0.0.0 decap_tunnel: 0 encap_tunnel: 0 vrf_id: 0 mtr_id: 0
AD: local_source_punt: 1 afd_label_or_clientid: 0 mcast_bridge_frame: 0 mcast_rep_frame: 0
rpf_valid: 1 rpf_le_ptr: 0 afd_client_flag: 0 dest_mod_bridge: 0 dest_mod_route: 1
cpp_type: 0 dest_mod_index: 0 rp_index: 0 priority: 3 rpf_le: 0 station_index: 178
capwap_mgid_present: 0 mgid 0
==============================================================