Command Reference, Cisco IOS XE Bengaluru 17.4.x (Catalyst 9400 Switches)

clear ip mfib counters

To clear all the active IPv4 Multicast Forwarding Information Base (MFIB) traffic counters, use the clear ip mfib counters command in privileged EXEC mode.

clear ip mfib [ global | vrf *] counters [ group-address] [ hostname | source-address]

Syntax Description


global	(Optional) Resets the IP MFIB cache to the global default configuration.
vrf *	(Optional) Clears the IP MFIB cache for all VPN routing and forwarding instances.
`group-address`	(Optional) Limits the active MFIB traffic counters to the indicated group address.
`hostname`	(Optional) Limits the active MFIB traffic counters to the indicated host name.
`source-address`	(Optional) Limits the active MFIB traffic counters to the indicated source address.

Command Default

None

Command Modes

Privileged EXEC (#)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

The following example shows how to reset all the active MFIB traffic counters for all the multicast tables:

Device# clear ip mfib counters

The following example shows how to reset the IP MFIB cache counters to the global default configuration:

Device# clear ip mfib global counters

The following example shows how to clear the IP MFIB cache for all the VPN routing and forwarding instances:

Device# clear ip mfib vrf * counters

clear ip mroute

To delete the entries in the IP multicast routing table, use the clear ip mroute command in privileged EXEC mode.

clear ip mroute [ vrf vrf-name] { * | ip-address | group-address} [ hostname | source-address]

Syntax Description


vrf `vrf-name`	(Optional) Specifies the name that is assigned to the multicast VPN routing and forwarding (VRF) instance.
*	Specifies all Multicast routes.
`ip-address`	Multicast routes for the IP address.
`group-address`	Multicast routes for the group address.
`hostname`	(Optional) Multicast routes for the host name.
`source-address`	(Optional) Multicast routes for the source address.

Command Default

None

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

The group-address variable specifies one of the following:

Name of the multicast group as defined in the DNS hosts table or with the ip host command.
IP address of the multicast group in four-part, dotted notation.

If you specify a group name or address, you can also enter the source argument to specify a name or address of a multicast source that is sending to the group. A source does not need to be a member of the group.

Examples

The following example shows how to delete all the entries from the IP multicast routing table:

Device# clear ip mroute *

The following example shows how to delete all the sources on the 228.3.0.0 subnet that are sending to the multicast group 224.2.205.42 from the IP multicast routing table. This example shows how to delete all sources on network 228.3, not individual sources:

Device# clear ip mroute 224.2.205.42 228.3.0.0

clear ip pim snooping vlan

To delete the Protocol Independent Multicast (PIM) snooping entries on a specific VLAN, use the clear ip pim snooping vlan command in user EXEC or privileged EXEC mode.

clear ip pim snooping vlan vlan-id [neighbor | statistics | mroute [source-ip | group-ip]]

Syntax Description


vlan `vlan-id`	VLAN ID. Valid values are from 1―4094.
neighbor	Deletes all the neighbors.
statistics	Deletes information about the VLAN statistics.
mroute `group-addr` `src-addr`	Deletes the mroute entries in the specified group and the source IP address.

Command Default

This command has no default settings.

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

This example shows how to clear the IP PIM-snooping entries on a specific VLAN:


Router# clear ip pim snooping vlan 1001

Related Commands


Command	Description
ip pim snooping	Enables PIM snooping globally.
show ip pim snooping	Displays information about IP PIM snooping.

debug condition vrf

To limit debug output to a specific virtual routing and forwarding (VRF) instance, use the debug condition vrf command in privileged EXEC mode. To remove the debug condition, use the no form of the command.

debug condition vrf {default | global | green | name {vrf-name | green}}

no debug condition vrf {default | global | green | name {vrf-name | green}}

Syntax Description


Syntax	Description
default	Specifies the default routing table.
global	Specifies the global routing table.
green	Specifies the VRF name.
name `vrf-name`	Specifies the name of the routing table.

Command Modes

Privileged EXEC mode (#)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Use this command to limit debug output to a single VRF.

Caution

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use the debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. It is best to use the debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

Example

The following example shows how to limit debugging output to VRF red:

Device# debug condition vrf red

debug ip pim

To display PIM packets received and transmitted, as well as PIM related events, use the debug ip pim command in privileged EXEC mode. To disable the debug output, use the no form of the command.

Syntax Description


Syntax	Description
vrf `vrf-name`	(Optional) Specifies the VPN Routing and Forwarding instance. This keyword overrides debugging of any VRFs specified in the debug condition vrf `vrf-name` command.
`ip-address`	(Optional) Specifies the IP group address.
atm	(Optional) Displays debugging information about PIM ATM signalling activity.
auto-rp	(Optional) Displays debugging information about Auto-RP information.
bfd	(Optional) Displays debugging information about BFD configuration.
bsr	(Optional) Displays debugging information about PIM Candidate-RP and BSR activity.
crimson	(Optional) Displays debugging information about Crimson database activity.
df `rp-address`	(Optional) Displays debugging information about PIM RP designated forwarder election activity.
drlb	(Optional) Displays debugging information about PIM designated router load-balancing activity.
hello	(Optional) Displays debugging information about PIM Hello packets received and sent.
timers	(Optional) Displays debugging information about PIM timer events.

Command Modes

Privileged EXEC mode (#)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Caution

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use the debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. It is best to use the debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

You can debug a maximum of 8 VRFs in a PIM at a time. To debug multiple VRFs at the same time, perform the following sequence of steps:

debug condition vrf vrf-name1
debug condition vrf vrf-name2
.
.
.
debug condition vrf vrf-name8
debug ip pim

Example

The following example shows how to display the Crimson database activity:

Device# debug ip pim crimson

The following example shows how to debug the two VRFs red and green in a PIM at the same time:

Device# debug condition vrf red
Device# debug condition vrf green
Device# debug ip pim

debug ipv6 pim

To enable debugging on Protocol Independent Multicast (PIM) protocol activity, use the debug ipv6 pim command in privileged EXEC mode. To restore the default value, use the no form of this command.

Syntax Description


Syntax	Description
vrf `vrf-name`	(Optional) Specifies the VPN Routing and Forwarding instance. This keyword overrides debugging of any VRFs specified in the debug condition vrf `vrf-name` command.
bfd	(Optional) Displays debugging information about BFD configuration.
bsr	(Optional) Displays debugging information about PIM Candidate-RP and BSR sent and received.
crimson	(Optional) Displays debugging information about Crimson database activity.
df-election	(Optional) Displays debugging information about PIM designated forwarder election activity.
drlb	(Optional) Displays debugging information about PIM designated router load-balancing activity.
group `group-address`	(Optional) Displays debugging information about group-related activity.
interface	(Optional) Displays debugging information about protocol activity of the specified interface.
limit	(Optional) Displays debugging information about interface limits.
neighbor	(Optional) Displays debugging information about PIM Hello messages received and sent.
`interface-type interface-number`	(Optional) Displays debugging information about the specified interface.
rp `rp-address`	(Optional) Displays debugging information about the specified RP.

Command Modes

Privileged EXEC mode (#)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Caution

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use the debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. It is best to use the debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

You can debug a maximum of 8 VRFs in a PIM at a time. To debug multiple VRFs at the same time, perform the following sequence of steps:

debug condition vrf vrf-name1
debug condition vrf vrf-name2
.
.
.
debug condition vrf vrf-name8
debug ip pim

Example

The following example shows how to display the Crimson database activity:

Device# debug ipv6 pim crimson

The following example shows how to debug VRF red:

Device# debug vrf red ipv6 pim

ip igmp filter

To control whether or not all the 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 device stack or on a standalone device. To remove the specified profile from the interface, use the no form of this command.

ip igmp filter profile number

no ip igmp filter

Syntax Description


`profile number`	IGMP profile number to be applied. The range is 1—4294967295.

Command Default

No IGMP filters are applied.

Command Modes

Interface configuration (config-if)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 device port interfaces, but one port can have only one profile applied to it.

Examples

You can verify your setting by using the show running-config command in privileged EXEC mode and by specifying an interface.

ip igmp max-groups

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 device stack or on a standalone device. 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}

Syntax Description


`max number`	Maximum number of IGMP groups that an interface can join. The range is 0—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.

Command Default

The default maximum number of groups is no limit.

After the device 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.

Command Modes

Interface configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 limit, 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 device 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 device 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.

Examples

The following example shows how to limit the number of IGMP groups that a port can join to 25:

Device(config)# interface gigabitethernet1/0/2
Device(config-if)# ip igmp max-groups 25

The following example shows how to configure the device 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:

Device(config)# interface gigabitethernet2/0/1
Device(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.

ip igmp profile

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 device stack or on a standalone device. 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

Syntax Description


`profile number`	The IGMP profile number being configured. The range is from 1—4294967295.

Command Default

No IGMP profiles are defined. When configured, the default action for matching an IGMP profile is to deny matching addresses.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

When you are in IGMP profile configuration mode, you can create a profile by using these commands:

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.

Examples

The following example shows how to configure IGMP profile 40, which permits the specified range of IP multicast addresses:

Device(config)# ip igmp profile 40
Device(config-igmp-profile)# permit
Device(config-igmp-profile)# range 233.1.1.1 233.255.255.255

You can verify your settings by using the show ip igmp profile command in privileged EXEC mode.

ip igmp snooping

To globally enable Internet Group Management Protocol (IGMP) snooping on the device or to enable it on a per-VLAN basis, use the ip igmp snooping global configuration command on the device stack or on a standalone device. 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]

Syntax Description


vlan `vlan-id`	(Optional) Enables IGMP snooping on the specified VLAN. Ranges are 1—1001 and 1006—4094.

Command Default

IGMP snooping is globally enabled on the device.

IGMP snooping is enabled on VLAN interfaces.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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.

Examples

The following example shows how to globally enable IGMP snooping:

Device(config)# ip igmp snooping

The following example shows how to enable IGMP snooping on VLAN 1:

Device(config)# ip igmp snooping vlan 1

You can verify your settings by entering the show ip igmp snooping command in privileged EXEC mode.

ip igmp snooping last-member-query-count

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 this command.

ip igmp snooping [ vlan vlan-id] last-member-query-count count

no ip igmp snooping [ vlan vlan-id] last-member-query-count count

Syntax Description


vlan `vlan-id`	(Optional) Sets the count value on a specific VLAN ID. The range is from 1―1001. Do not enter leading zeroes.
`count`	Interval at which query messages are sent, in milliseconds. The range is from 1―7. The default is 2.

Command Default

A query is sent every 2 milliseconds.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 is received to the last-member queries 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 device to the host or the report packet from the host to the device) may result in traffic forwarding being stopped even if the receiver is still there. Traffic continues to be forwarded after the next general query is sent by the device, 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 1 last-member query interval (LMQI) value when the device is processing more than one leave within an LMQI. In such a scenario, 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.

Examples

The following example shows how to set the last member query count to 5:


Device(config)# ip igmp snooping last-member-query-count 5

ip igmp snooping querier

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]

Syntax Description


vlan `vlan-id`	(Optional) Enables IGMP snooping and the IGMP querier function on the specified VLAN. Ranges are 1—1001 and 1006—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—25 seconds.
query-interval `interval-count`	(Optional) Sets the interval between IGMP queriers. The range is 1—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—10.
interval `interval`	Sets the TCN query interval time. The range is 1—255.
timer expiry `expiry-time`	(Optional) Sets the length of time until the IGMP querier expires. The range is 60—300 seconds.
version `version`	(Optional) Selects the IGMP version number that the querier feature uses. Select either 1 or 2.

Command Default

The IGMP snooping querier feature is globally disabled on the device.

When enabled, the IGMP snooping querier disables itself if it detects IGMP traffic from a multicast router.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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―1005 are reserved for Token Ring and FDDI VLANs, and cannot be used in IGMP snooping.

Examples

The following example shows how to globally enable the IGMP snooping querier feature:

Device(config)# ip igmp snooping querier

The following example shows how to set the IGMP snooping querier maximum response time to 25 seconds:

Device(config)# ip igmp snooping querier max-response-time 25

The following example shows how to set the IGMP snooping querier interval time to 60 seconds:

Device(config)# ip igmp snooping querier query-interval 60

The following example shows how to set the IGMP snooping querier TCN query count to 25:

Device(config)# ip igmp snooping querier tcn count 25

The following example shows how to set the IGMP snooping querier timeout value to 60 seconds:

Device(config)# ip igmp snooping querier timer expiry 60

The following example shows how to set the IGMP snooping querier feature to Version 2:

Device(config)# ip igmp snooping querier version 2

You can verify your settings by entering the show ip igmp snooping privileged EXEC command.

ip igmp snooping report-suppression

To enable Internet Group Management Protocol (IGMP) report suppression, use the ip igmp snooping report-suppression global configuration command on the device stack or on a standalone device. 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

Syntax Description

This command has no arguments or keywords.

Command Default

IGMP report suppression is enabled.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 device 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 device sends the first IGMP report from all the hosts for a group to all the multicast routers. The device 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 device forwards only the first IGMPv1 or IGMPv2 report from all the hosts for a group to all of the multicast routers. If the multicast router query also includes requests for IGMPv3 reports, the device 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.

Examples

The following example shows how to disable report suppression:

Device(config)# no ip igmp snooping report-suppression

You can verify your settings by entering the show ip igmp snooping command in privileged EXEC mode.

ip igmp snooping vlan mrouter

To add a multicast router port, use the ip igmp snooping mrouter global configuration command on the device stack or on a standalone device. To return to the default settings, use the no form of this command.

Command Default

By default, there are no multicast router ports.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

VLAN IDs 1002―1005 are reserved for Token Ring and FDDI VLANs, and cannot be used in IGMP snooping.

The configuration is saved in NVRAM.

Examples

The following example shows how to configure a port as a multicast router port:

Device(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.

ip igmp snooping vlan static

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 device stack or on a standalone device. To remove the port specified as members of a static multicast group, use the no form of this command.

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

Syntax Description


`vlan-id`	Enables IGMP snooping on the specified VLAN. Ranges are 1—1001 and 1006—4094.
`ip-address`	Adds a Layer 2 port as a member of a multicast group with the specified group IP address.
interface `interface-id`	Specifies the interface of the member port. The `interface-id` has these options: fastethernet interface number—A Fast Ethernet IEEE 802.3 interface. gigabitethernet interface number—A Gigabit Ethernet IEEE 802.3z interface. tengigabitethernet interface number—A 10-Gigabit Ethernet IEEE 802.3z interface. port-channel interface number—A channel interface. The range is 0—128.

Command Default

By default, no ports are statically configured as members of a multicast group.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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.

Examples

The following example shows how to statically configure a host on an interface:

Device(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 command in privileged EXEC mode.

ip multicast auto-enable

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 this command.

ip multicast auto-enable

no ip multicast auto-enable

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

The following example shows how to enable AAA on IP multicast:

Device(config)# ip multicast auto-enable

ip multicast-routing

To enable IP multicast routing, use the ip multicast-routing command in global configuration mode. To disable IP multicast routing, use the no form of this command.

ip multicast-routing [ vrf vrf-name]

no ip multicast-routing [ vrf vrf-name]

Syntax Description


vrf `vrf-name`	(Optional) Enables IP multicast routing for the Multicast VPN routing and forwarding (MVRF) instance specified for the `vrf-name` argument.

Command Default

IP multicast routing is disabled.

Command Modes

Global configuration (config)

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

When IP multicast routing is disabled, the Cisco IOS XE software does not forward any multicast packets.

Note

For IP multicast, after enabling IP multicast routing, PIM must be configured on all interfaces. Disabling IP multicast routing does not remove PIM; PIM still must be explicitly removed from the interface configurations.

Examples

The following example shows how to enable IP multicast routing:

Device> enable
Device# configure terminal
Device(config)# ip multicast-routing

The following example shows how to enable IP multicast routing on a specific VRF:


Device(config)# ip multicast-routing vrf vrf1

Related Commands


Command	Description
ip pim	Enables PIM on an interface.

ip pim accept-register

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

Syntax Description


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—199 and the expanded range is 2000—2699. An IP-named access list can also be used.

Command Default

No PIM register filters are configured.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Use this command to prevent unauthorized sources from registering with the RP. If an unauthorized source sends a register message to the RP, the RP will immediately send back a register-stop message.

The access list provided for the ip pim accept-register command should only filters 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 required, use the ip multicast boundary command instead.

Examples

The following example shows how to permit register packets for a 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.

Device(config)# ip pim accept-register list ssm-range
Device(config)# ip access-list extended ssm-range
Device(config-ext-nacl)# deny ip any 232.0.0.0 0.255.255.255
Device(config-ext-nacl)# permit ip any any

ip pim bidir-enable

To enable bidirectional Protocol Independent Multicast (bidirectional PIM), use the ip pim bidir-enable command in global configuration mode. To disable bidirectional PIM, use the no form of this command.

ip pim bidir-enable

no ip pim bidir-enable

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.12.1	This command was introduced.

Command Default

The command is enabled.

Command Modes

Global configuration (config)

Usage Guidelines

When bidirectional PIM is disabled, the router will behave similarly to a router without bidirectional PIM support. The following conditions will apply:

PIM hello messages sent by the router will not contain the bidirectional mode option.
The router will not send designated forwarder (DF) election messages and will ignore DF election messages it receives.
The ip pim rp-address , ip pim send-rp-announce , and ip pim rp-candidate global configuration commands will be treated as follows:
- If these commands are configured when bidirectional PIM is disabled, bidirectional mode will not be a configuration option.
- If these commands are configured with the bidirectional mode option when bidirectional PIM is enabled and then bidirectional PIM is disabled, these commands will be removed from the command-line interface (CLI). In this situation, these commands must be configured again with the bidirectional mode option when bidirectional PIM is reenabled.
The df keyword for the show ip pim interface user EXEC or privileged EXEC command and debug ip pim privileged EXEC command is not supported.

Examples

The following example shows how to enable bidirectional PIM:

Device# enable
Device# configure terminal
Device(config)# ip pim bidir-enable

ip pim bsr-candidate

To configure the Device 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

Syntax Description


vrf `vrf-name`	(Optional) Configures the Device 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 the Device 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.

Command Default

The Device is not configured to announce itself as a candidate BSR.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

The interface specified for this command must be enabled for Protocol Independent Multicast (PIM) using the ip pim command.

This command configures the Device 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 Devices 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 pre-existing 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 Device always accept and process BSR messages. There is no command to disable this function.

Cisco Device perform the following steps to determine which C-RP is used for a group:

A long match lookup is performed on the group prefix that is announced by the BSR C-RPs.
If more than one BSR-learned C-RP is 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 has the same priority, the BSR hash function is used to select the RP for a group.
If more than one BSR-learned C-RP returns the same hash value derived from the BSR hash function, the BSR C-RP with the highest IP address is preferred.

Examples

The following example shows how to configure the IP address of theDevice 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:

Device(config)# ip pim bsr-candidate GigabitEthernet1/0/1 0 192

ip pim rp-address

To statically configure the address of a Protocol Independent Multicast (PIM) rendezvous point (RP) for multicast groups, use the ip pim rp-address command in global configuration mode. To remove an RP address, use the no form of this command.

ip pim [ vrf vrf-name] rp-address rp-address [ access-list] [ override ] [ bidir]

no ip pim [ vrf vrf-name] rp-address rp-address [ access-list] [ override ] [ bidir]

Syntax Description

vrf vrf-name

(Optional) Specifies that the static group-to-RP mapping be associated with the Multicast Virtual Private Network (MVPN) routing and forwarding (MVRF) instance specified for the vrf-name argument.

rp-address rp-address

IP address of the RP to be used for the static group-to-RP mapping. This is a unicast IP address in four-part dotted-decimal notation.

access-list

(Optional) Number or name of a standard access list that defines the multicast groups to be statically mapped to the RP.

Note

If no access list is defined, the RP will map to all multicast groups

override

(Optional) Specifies that if dynamic and static group-to-RP mappings are used together and there is an RP address conflict, the RP address configured for a static group-to-RP mapping will take precedence.

Note

If the override keyword is not specified and there is RP address conflict, dynamic group-to-RP mappings will take precedence over static group-to-RP mappings.

bidir

(Optional) Specifies that the static group-to-RP mapping be applied to a bidirectional PIM RP.

If the command is configured without the bidir keyword, the groups will operate in sparse mode.

Note

The bidir keyword is available as an optional keyword only if bidirectional PIM has been enabled using the ip pim bidir-enable command.

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.12.1	This command was introduced.

Command Default

No PIM static group-to-RP mappings are configured.

Command Modes

Global configuration (config)

Usage Guidelines

Under PIM, multicast groups in sparse mode (PIM-SM) or bidirectional mode (bidirectional PIM) use RPs to connect sources and receivers. All routers in a PIM domain need to have a consistent configuration for the mode and RP addresses of the multicast groups.

The Cisco IOS software learns the mode and RP addresses of multicast groups through the following three mechanisms: static group-to-RP mapping configurations, Auto-RP, and bootstrap router (BSR).

Use the ip pim rp-address command to statically define the RP address for PIM-SM or bidirectional PIM groups (an ip pim rp-address command configuration is referred to as a static group-to-RP mapping).

You can configure a single RP for more than one group using an access list. If no access list is specified, the static RP will map to all multicast groups.

You can configure multiple RPs, but only one RP per group range.

If multiple ip pim rp-address commands are configured, the following rules apply:

Highest RP IP address selected regardless of reachability: If a multicast group is matched by the access list of more than one configured ip pim rp-addres s command, then the RP for the group is determined by the RP with the highest RP address configured.
One RP address per command: If multiple ip pim rp-address commands are configured, each static group-to-RP mapping must be configured with a unique RP address (if not, it will be overwritten).This restriction also means that only one RP address can be used to provide RP functions for either sparse mode or bidirectional mode groups. If you want to configure static group-to-RP mappings for both bidirectional and sparse mode, the RP addresses must be unique for each mode.
One access list per command: If multiple ip pim rp-address commands are configured, only one access list can be configured per static group-to-RP mapping. An access list cannot be reused with other static group-to-RP mappings configured on a router.

If dynamic and static group-to-RP mappings are used together, the following rule applies to a multicast group: Dynamic group-to-RP mappings take precedence over static group-to-RP mappings--unless the override keyword is used.

Examples

The following example shows how to set the bidirectional PIM RP address to 172.16.0.2 for the multicast range 239/8:

Device(config)# access list 10 239.0.0.0 0.255.255.255
Device(config)# ip pim rp-address 172.16.0.2 10 bidir

ip pim rp-candidate

To configure the Device 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 the Device 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]

Syntax Description


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.

Command Default

The Device is not configured to announce itself to the BSR as a PIMv2 C-RP.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Use this command to configure the Device to send PIMv2 messages so that it advertises itself as a candidate RP to the BSR.

This command should be configured on backbone Devices 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.

Examples

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.

Device(config)# ip pim rp-candidate GigabitEthernet1/0/1 group-list 4

ip pim send-rp-announce

To use Auto-RP to configure groups for which the device will act as a rendezvous point (RP), use the ip pim send-rp-announce command in global configuration mode. To unconfigure the device 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] [ bidir]

no ip pim [ vrf vrf-name] send-rp-announce interface-id

Syntax Description


vrf `vrf-name`	(Optional) Uses Auto-RP to configure groups for which the device 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 to ensure that the RP-announce messages reach all the mapping agents in the network. There is no default setting. The range is 1—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—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 hold time 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—16383.
bidir	(Optional) Indicates that the multicast groups specified by the access-listargument are to operate in bidirectional mode. If the command is configured without this keyword, the groups specified will operate in Protocol Independent Multicast sparse mode (PIM-SM).

Command Default

Auto-RP is disabled.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.
Cisco IOS XE Gibraltar 16.12.1	This command was modified. The bidir keyword was added.

Usage Guidelines

Enter this command on the device 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.

Use this command with the bidir keyword when you want bidirectional forwarding and you are using Auto-RP to distribute group-to-RP mappings. Other options are as follows:

If you are using the PIM Version 2 bootstrap router (PIMv2 BSR) mechanism to distribute group-to-RP mappings, use the bidir keyword with the ip pim rp-candidate command.
If you are not distributing group-to-RP mappings using either Auto-RP or the PIMv2 BSR mechanism, use the bidir keyword with the ip pim rp-address command.

Examples

The following example shows how to configure the device 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:

Device(config)# ip pim send-rp-announce GigabitEthernet1/0/1 scope 31 group-list 5 interval 120

ip pim snooping

To enable Protocol Independent Multicast (PIM) snooping globally, use the ip pim snooping command in global configuration mode. To disable PIM snooping globally, use the no form of this command.

ip pim snooping

no ip pim snooping

Syntax Description

This command has no arguments or keywords.

Command Default

PIM snooping is not enabled.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

PIM snooping is not supported on groups that use the reserved MAC address range, for example, 0100.5e00.00xx, as an alias.

When you disable PIM snooping globally, PIM snooping is disabled on all the VLANs.

Examples

The following example shows how to enable PIM snooping globally:

ip pim snooping

The following example shows how to disable PIM snooping globally:

no ip pim snooping

Related Commands


Command	Description
clear ip pim snooping	Deletes PIM snooping on an interface.
show ip pim snooping	Displays information about IP PIM snooping.

ip pim snooping dr-flood

To enable flooding of packets to the designated router, use the ip pim snooping dr-flood command in global configuration mode. To disable the flooding of packets to the designated router, use the no form of this command.

ip pim snooping dr-flood

no ip pim snooping dr-flood

Syntax Description

This command has no arguments or keywords.

Command Default

The flooding of packets to the designated router is enabled by default.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

PIM snooping is not supported on groups that use the reserved MAC address range, for example, 0100.5e00.00xx, as an alias.

Enter the no ip pim snooping dr-flood command only on switches that have no designated routers attached.

The designated router is programmed automatically in the (S,G) O-list.

Examples

The following example shows how to enable flooding of packets to the designated router:

ip pim snooping dr-flood

The following example shows how to disable flooding of t packets to the designated router:

no ip pim snooping dr-flood

Related Commands


Command	Description
clear ip pim snooping	Deletes PIM snooping on an interface.
show ip pim snooping	Displays information about IP PIM snooping.

ip pim snooping vlan

To enable Protocol Independent Multicast (PIM) snooping on an interface, use the ip pim snoopingvlan command in global configuration mode. To disable PIM snooping on an interface, use the no form of this command.

ip pim snooping vlan vlan-id

no ip pim snooping vlan vlan-id

Syntax Description


`vlan-id`	VLAN ID value. The range is 1—1001. Do not enter leading zeroes.

Command Default

PIM snooping is disabled on an interface.

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

PIM snooping is not supported on groups that use the reserved MAC address range, for example, 0100.5e00.00xx, as an alias.

This command automatically configures the VLAN if it is not already configured. The configuration is saved in NVRAM.

Examples

This example shows how to enable PIM snooping on a VLAN interface:

Router(config)# ip pim snooping vlan 2

This example shows how to disable PIM snooping on a VLAN interface:

Router(config)# no ip pim snooping vlan 2

Related Commands


Command	Description
clear ip pim snooping	Deletes PIM snooping on an interface.
ip pim snooping	Enables PIM snooping globally.
show ip pim snooping	Displays information about IP PIM snooping.

ip pim spt-threshold

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]

Syntax Description


`kbps`	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 the 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 the groups.

Command Default

Switches to the PIM shortest-path tree (spt).

Command Modes

Global configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

The following example shows how to make all the sources for access list 16 use the shared tree:

Device(config)# ip pim spt-threshold infinity group-list 16

match message-type

To set a message type to match a service list, use the match message-type command.

match message-type {announcement | | any | | query}

Syntax Description


announcement	Allows only service advertisements or announcements for the Device.
any	Allows any match type.
query	Allows only a query from the client for a certain Device in the network.

Command Default

None

Command Modes

Service list configuration.

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Multiple service maps of the same name with different sequence numbers can be created, and the evaluation of the filters will be ordered on the sequence number. Service lists are an ordered sequence of individual statements, with each one having a permit or deny result. The evaluation of a service list consists of a list scan in a predetermined order, and an evaluation of the criteria of each statement that matches. A list scan is stopped once the first statement match is found and a permit/deny action associated with the statement match is performed. The default action after scanning through the entire list is to deny.

Note

It is not possible to use the match command if you have used the service-list mdns-sd service-list-name query command. The match command can be used only for the permit or deny option.

Examples

The following example shows how to set the announcement message type to be matched:

Device(config-mdns-sd-sl)# match message-type announcement

match service-type

To set the value of the mDNS service type string to match, use the match service-type command.

match service-type line

Syntax Description


`line`	Regular expression to match the service type in packets.

Command Default

None

Command Modes

Service list configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

It is not possible to use the match command if you have used the service-list mdns-sd service-list-name query command. The match command can be used only for the permit or deny option.

Examples

The following example shows how to set the value of the mDNS service type string to match:

Device(config-mdns-sd-sl)# match service-type _ipp._tcp

match service-instance

To set a service instance to match a service list, use the match service-instance command.

match service-instance line

Syntax Description


`line`	Regular expression to match the service instance in packets.

Command Default

None

Command Modes

Service list configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

It is not possible to use the match command if you have used the service-list mdns-sd service-list-name query command. The match command can be used only for the permit or deny option.

Examples

The following example shows how to set the service instance to match:

Device(config-mdns-sd-sl)# match service-instance servInst 1

mrinfo

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]

Syntax Description


vrf `route-name`	(Optional) Specifies the VPN routing or forwarding instance.
`hostname` `\|` `address`	(Optional) 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) Interface ID.

Command Default

The command is disabled.

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 supports mrinfo requests from 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.)

Examples

The following is the sample output from the mrinfo command:

Device# 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

The flags indicate the following:

P: prune-capable
M: mtrace-capable
S: Simple Network Management Protocol-capable
A: Auto RP capable

service-policy-query

To configure the service-list query periodicity, use the service-policy-query command. To delete the configuration, use the no form of this command.

service-policy-query [ service-list-query-name service-list-query-periodicity]

no service-policy-query

Syntax Description


`service-list-query-name service-list-query-periodicity`	(Optional) Service-list query periodicity.

Command Default

Disabled.

Command Modes

mDNS configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

Since there are devices that do not send unsolicited announcements and to force such devices the learning of services and to keep them refreshed in the cache, this command contains an active query feature that ensures that the services listed in the active query list are queried.

Examples

This example shows how to configure service list query periodicity:

Device(config-mdns)# service-policy-query sl-query1 100

service-policy

To apply a filter on incoming or outgoing service-discovery information on a service list, use the service-policy command. To remove the filter, use the no form of this command.

service-policy service-policy-name { IN | OUT}

no service-policy service-policy-name { IN | OUT}

Syntax Description


IN	Applies a filter on incoming service-discovery information.
OUT	Applies a filter on outgoing service-discovery information.

Command Default

Disabled.

Command Modes

mDNS configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

The following example shows how to apply a filter on incoming service-discovery information on a service list:

Device(config-mdns)#  service-policy serv-pol1 IN

show ip igmp filter

To display Internet Group Management Protocol (IGMP) filter information, use the show ip igmp filter command in privileged EXEC mode.

show ip igmp [ vrf vrf-name] filter

Syntax Description


vrf `vrf-name`	(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.

Command Default

IGMP filters are enabled by default.

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

The show ip igmp filter command displays information about all filters defined on the device.

Examples

The following example shows the sample output from the show ip igmp filter command:

Device# show ip igmp filter

IGMP filter enabled

show ip igmp profile

To display all the configured Internet Group Management Protocol (IGMP) profiles or a specified IGMP profile, use the show ip igmp profile command in privileged EXEC mode.

show ip igmp [ vrf vrf-name] profile [ profile number]

Syntax Description


vrf `vrf-name`	(Optional) Supports the multicast VPN routing and forwarding (VRF) instance.
`profile number`	(Optional) IGMP profile number to be displayed. The range is 1 to 4294967295. If no profile number is entered, all the IGMP profiles are displayed.

Command Default

IGMP profiles are undefined by default.

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

None

Examples

The following example shows the output of the show ip igmp profile command for profile number 40 on the device:

Device# show ip igmp profile 40
IGMP Profile 40
    permit
    range 233.1.1.1 233.255.255.255

The following example shows the output of the show ip igmp profile command for all the profiles configured on the device:

Device# 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

show ip igmp snooping

To display the Internet Group Management Protocol (IGMP) snooping configuration of the device or the VLAN, use the show ip igmp snooping command in user EXEC or privileged EXEC mode.

show ip igmp snooping [ groups | mrouter | querier] [ vlan vlan-id] [ detail]

Syntax Description


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.

Command Default

None

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

VLAN IDs 1002―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.

Examples

The following is a sample output from the show ip igmp snooping vlan 1 command. It shows snooping characteristics for a specific VLAN:

Device# 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

The following is a sample output from the show ip igmp snooping command. It displays snooping characteristics for all the VLANs on the device:

Device# 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
-
.
.
.

show ip igmp snooping groups

To display the Internet Group Management Protocol (IGMP) snooping multicast table for the device or the multicast information, use the show ip igmp snooping groups command in privileged EXEC mode.

Command Modes

Privileged EXEC

User EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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.

Examples

The following is a sample output from the show ip igmp snooping groups command without any keywords. It displays the multicast table for the device.

Device# 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

The following is a sample output from the show ip igmp snooping groups count command. It displays the total number of multicast groups on the device.

Device# show ip igmp snooping groups count

Total number of multicast groups: 2

The following is a sample 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:

Device# 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

show ip igmp snooping mrouter

To display the Internet Group Management Protocol (IGMP) snooping dynamically learned and manually configured multicast router ports for the device or for the specified multicast VLAN, use the show ip igmp snooping mrouter command in privileged EXEC mode.

show ip igmp snooping mrouter [ vlan vlan-id]

Syntax Description


vlan `vlan-id`	(Optional) Specifies a VLAN; Ranges are from 1―1001 and 1006―4094.

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

VLAN IDs 1002―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.

Examples

The following is a sample output from the show ip igmp snooping mrouter command. It shows how to display multicast router ports on the device:

Device# show ip igmp snooping mrouter

Vlan    ports
----    -----
   1    Gi2/0/1(dynamic)

show ip igmp snooping querier

To display the configuration and operation information for the IGMP querier that is configured on a device, use the show ip igmp snooping querier command in user EXEC mode.

show ip igmp snooping querier [ vlan vlan-id] [ detail ]

Syntax Description


vlan `vlan-id`	(Optional) Specifies a VLAN; Ranges are from 1―1001 and 1006―4094.
detail	(Optional) Displays detailed IGMP querier information.

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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 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 device.

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 device, the output shows the Port field as Router. If the querier is a router, the output shows the port number on which the querier was detected 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 device querier.

The show ip igmp snooping querier detail command displays the device IP address most recently detected by the device querier and this additional information:

The elected IGMP querier in the VLAN
The configuration and operational information pertaining to the device querier (if any) that is configured in the VLAN

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.

Examples

The following is a sample output from the show ip igmp snooping querier command:

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

The following is a sample output from the show ip igmp snooping querier detail command:

Device> show ip igmp snooping querier detail

Vlan      IP Address     IGMP Version   Port
-------------------------------------------------------------
1         1.1.1.1        v2             Fa8/0/1 
Global IGMP device 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 device 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

show ip pim autorp

To display global information about auto-rp, use the show ip pim autorp command in privileged EXEC mode.

show ip pim autorp

Syntax Description

This command has no arguments or keywords.

Command Default

Auto RP is enabled by default.

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

This command displays whether auto-rp is enabled or disabled.

Examples

The following command output shows that Auto RP is enabled:

Device# 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

show ip pim bsr-router

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

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

In addition to Auto RP, the BSR RP method can be configured. After the BSR RP method is configured, this command displays the BSR router information.

Examples

The following is sample output from the show ip pim bsr-router command:

Device# 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

show ip pim bsr

To display information related to Protocol Independent Multicast (PIM) bootstrap router (BSR) protocol processing, use the show ip pim bsr command in user EXEC or privileged EXEC mode.

show ip pim bsr

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

In addition to Auto RP, the BSR RP method can be configured. After the BSR RP method is configured, this command displays the BSR router information.

Examples

The following is sample output from the show ip pim bsr command:

Device# show ip pim bsr

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

show ip pim interface df

To display information about the elected designated forwarder (DF) for each rendezvous point (RP) on an interface configured for Bidirectional Protocol Independent Multicast (PIM), use the show ip pim interface df command in user EXEC or privileged EXEC mode.

show ip pim [ vrf vrf-name] interface [ interface-type| interface-name] df [ rp-address]


vrf `vrf-name`	(Optional) Specifies the multicast VPN routing and forwarding (VRF) instance.
interface `[` `interface-type\|` `interface-name]`	Specifies the interface type or the interface number.
`rp-address`	(Optional) Specifies the RP IP address.

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.12.1	This command was introduced.

Command Default

If no interface is specified, all interfaces are displayed.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Examples

The following is sample output from the show ip pim interface df command:


Device# show ip pim interface df
Interface          RP               DF Winner        Metric          Uptime
Ethernet3/3        10.10.0.2        10.4.0.2         0               00:03:49
                   10.10.0.3        10.4.0.3         0               00:01:49
                   10.10.0.5        10.4.0.4         409600          00:01:49
Ethernet3/4        10.10.0.2        10.5.0.2         0               00:03:49
                   10.10.0.3        10.5.0.2         409600          00:02:32
                   10.10.0.5        10.5.0.2         435200          00:02:16
Loopback0          10.10.0.2        10.10.0.2        0               00:03:49
                   10.10.0.3        10.10.0.2        409600          00:02:32
                   10.10.0.5        10.10.0.2        435200          00:02:16

The following is sample output from the show ip pim interface df command when an interface is specified:

Device# show ip pim interface Ethernet3/3 df 10.10.0.3
Designated Forwarder election for Ethernet3/3, 10.4.0.2, RP 10.10.0.3
  State                           Non-DF
  Offer count is                  0
  Current DF ip address           10.4.0.3
  DF winner up time               00:02:33
  Last winner metric preference   0
  Last winner metric              0

The following table gives the output field descriptions for the show ip pim interface df command:


Field	Description
RP	IP address of the RP.
DF Winner	IP address of the elected DF.
Metric	Unicast routing metric to the RP announced by the DF.
Uptime	Length of time the RP has been up, in days and hours. If less than 1 day, time is shown in hours:minutes:seconds.
State	Indicates whether the specified interface is an elected DF.
Offer count is	Number of PIM DF election offer messages that the router has sent out the interface during the current election interval.
Current DF IP address	IP address of the current DF.
DF winner uptime	Length of time the current DF has been up, in days and hours. If less than 1 day, time is shown in hours:minutes:seconds.
Last winner metric preference	The preference value used for selecting the unicast routing metric to the RP announced by the DF.
Last winner metric	Unicast routing metric to the RP announced by the DF.

show ip pim rp

To display active rendezvous points ( RPs) that are cached with associated multicast routing entries, use the show ip pim rp command in user EXEC or privileged EXEC mode.

show ip pim [ vrf vrf-name] rp [ mapping[ elected| in-use ] | metric] [ rp-address]

Syntax Description


vrf `vrf-name`	(Optional) Specifies the multicast VPN routing and forwarding (VRF) instance.
mapping`[` elected`\|` in-use `]`	(Optional) Displays all group-to-RP mappings of which the router is aware. (either configured or learned from Auto-RP) elected - Displays elected Auto RPs. in-use - Displays learned RPs in-use.
metric	(Optional) Displays the unicast routing metric to the RPs configured statically or learned via Auto-RP or the bootstrap router (BSR).
`rp-address`	(Optional) Specifies the RP IP address.

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.12.1	This command was introduced.

Command Default

If no RP is specified, all active RPs are displayed.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Usage Guidelines

The Protocol Independent Multicast (PIM) version known for an RP influences the type of PIM register messages (Version 1 or Version 2) that the router sends when acting as the designated router (DR) for an active source. If an RP is statically configured, the PIM version of the RP is not set and the router, if required to send register packets, tries to send PIM Version 2 register packets. If sending PIM Version 2 packets fails, the router sends PIM Version 1 register packets.

The version of the RP displayed in the show ip pim rp command output can change according to the operations of the router. When the group is created, the version shown is for the RP in the RP mapping cache. Later, the version displayed by this command may change. If this router is acting as a DR for an active source, the router sends PIM register messages. The PIM register messages are answered by the RP with PIM register stop messages. The router learns from these PIM register stop messages the actual PIM version of the RP. Once the actual PIM version of the RP is learned, this command displays only this version. If the router is not acting as a DR for active sources on this group, then the version shown for the RP of the group does not change. In this case, the PIM version of the RP is irrelevant to the router because the version of the RP influences only the PIM register messages that this router must send.

When you enter the show ip pim rp mapping command, the version of the RP displayed in the output is determined only by the method through which an RP is learned. If the RP is learned from Auto-RP then the RP displayed is either “v1” or “v2, v1.” If the RP is learned from a static RP definition, the RP version is undetermined and no RP version is displayed in the output. If the RP is learned from the BSR, the RP version displayed is “v2.”

Examples

The following is sample output from the show ip pim rp command:

Device# show ip pim rp
Group:227.7.7.7, RP:10.10.0.2, v2, v1, next RP-reachable in 00:00:48

The following is sample output from the show ip pim rp command when the mapping keyword is specified:

Device# show ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent
Group(s) 227.0.0.0/8
  RP 10.10.0.2 (?), v2v1, bidir
    Info source:10.10.0.2 (?), via Auto-RP
         Uptime:00:01:42, expires:00:00:32
Group(s) 228.0.0.0/8
  RP 10.10.0.3 (?), v2v1, bidir
    Info source:10.10.0.3 (?), via Auto-RP
         Uptime:00:01:26, expires:00:00:34
Group(s) 229.0.0.0/8
  RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidir
    Info source:10.10.0.5 (mcast1.cisco.com), via Auto-RP
         Uptime:00:00:52, expires:00:00:37
Group(s) (-)230.0.0.0/8
  RP 10.10.0.5 (mcast1.cisco.com), v2v1, bidir
    Info source:10.10.0.5 (mcast1.cisco.com), via Auto-RP
         Uptime:00:00:52, expires:00:00:37

The following is sample output from the show ip pim rp command when the metric keyword is specified:

Device# show ip pim rp metric
RP Address      Metric Pref    Metric       Flags   RPF Type   Interface
10.10.0.2       0              0              L     unicast    Loopback0
10.10.0.3       90             409600         L     unicast    Ethernet3/3
10.10.0.5       90             435200         L     unicast    Ethernet3/3

show ip pim snooping

To display the information about IP PIM snooping, use the show ip pim snooping command in user EXEC or privileged EXEC mode.

Global Status

show ip pim snooping

VLAN Status

show ip pim snooping vlan vlan-id [neighbor | statistics | mroute [source-ip | group-ip]]

Syntax Description


vlan `vlan-id`	Displays information for a specific VLAN; Valid values are from 1―4094.
neighbor	(Optional) Displays information about the neighbor database.
statistics	(Optional) Displays information about the VLAN statistics.
mroute	(Optional) Displays information about the mroute database.
`source-ip`	(Optional) Source IP address.
`group-ip`	(Optional) Group IP address.

Command Default

This command has no default settings.

Command Modes

User EXEC Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Examples

The following example shows how to display information about the global status:


Router# show ip pim snooping

Global runtime mode: Enabled
Global admin mode  : Enabled
DR Flooding status : Disabled
SGR-Prune Suppression: Enabled
Number of user enabled VLANs: 1
User enabled VLANs: 1001

This example shows how to display information about a specific VLAN:


Router# show ip pim snooping vlan 1001

4 neighbors (0 DR priority incapable, 4 Bi-dir incapable)
5000 mroutes, 0 mac entries
DR is 10.10.10.4
RP DF Set:
QinQ snooping : Disabled

This example shows how to display information about the neighbor database for a specific VLAN:


Router# show ip pim snooping vlan 1001 neighbor 

IP Address       Mac address     Port            Uptime/Expires    Flags
VLAN 1001: 3 neighbors
10.10.10.2        000a.f330.344a  Po128           02:52:27/00:01:41 
10.10.10.1        000a.f330.334a  Hu1/0/7         04:54:14/00:01:38 
10.10.10.4        000a.f330.3c00  Hu1/0/1         04:53:45/00:01:34 DR

This example shows how to display the detailed statistics for a specific VLAN:


Router# show ip pim snooping vlan 1001 statistics 

PIMv2 statistics:
Total                                           : 56785
Process Enqueue                                 : 56785
Process PIMv2 input queue current outstanding   : 0
Process PIMv2 input queue max size reached      : 110
Error - Global Process State not RUNNING        : 0
Error - Process Enqueue                         : 0
Error - Drops                                   : 0
Error - Bad packet floods                       : 0
Error - IP header generic error                 : 0
Error - IP header payload len too long          : 0
Error - IP header payload len too short         : 0
Error - IP header checksum                      : 0
Error - IP header dest ip not 224.0.0.13        : 0
Error - PIM header payload len too short        : 0
Error - PIM header checksum                     : 0
Error - PIM header checksum in Registers        : 0
Error - PIM header version not 2                : 0

This example shows how to display information about the mroute database for all the mrouters in a specific VLAN:


Router# show ip pim snooping vlan 10 mroute 

Flags: J/P - (*,G) Join/Prune, j/p - (S,G) Join/Prune
       SGR-P - (S,G,R) Prune

VLAN 1001: 5000 mroutes
(*, 225.0.1.0), 00:14:54/00:02:59
  10.10.10.120->10.10.10.105, 00:14:54/00:02:59, J
  Downstream ports: Po128 
  Upstream   ports: Hu1/0/7 
  Outgoing   ports: Hu1/0/7 Po128 

(11.11.11.10, 225.0.1.0), 00:14:54/00:02:59
  10.10.10.130->10.10.10.120, 00:14:54/00:02:59, SGR-P
  Downstream ports: 
  Upstream   ports: Hu1/0/7 
  Outgoing   ports: 

(*, 225.0.5.0), 00:14:53/00:02:57
  10.10.10.105->10.10.10.10, 00:14:53/00:02:57, J
  Downstream ports: Po128 
  Upstream   ports: Hu1/0/7 
  Outgoing   ports: Hu1/0/7 Po128 

(11.11.11.10, 225.0.5.0), 00:14:53/00:02:57
  10.10.10.105->10.10.10.130, 00:14:53/00:02:57, SGR-P
  Downstream ports: 
  Upstream   ports: Hu1/0/7 
  Outgoing   ports: 
Number of matching mroutes found: 4

This example shows how to display information about the PIM mroute for a specific source address:


Router# show ip pim snooping vlan 10 mroute 172.16.100.100

(*, 172.16.100.100), 00:16:36/00:02:36
  10.10.10.1->10.10.10.2, 00:16:36/00:02:36, J
  Downstream ports: 3/12 
  Upstream   ports: 3/13 
  Outgoing   ports: 3/12 3/13

This example shows how to display information about the PIM mroute for a specific source and group address:


Router# show ip pim snooping vlan 10 mroute 192.168.0.0 172.16.10.10

(192.168.0.0, 172.16.10.10), 00:03:04/00:00:25
  10.10.10.1->10.10.10.2, 00:03:04/00:00:25, j
  Downstream ports: 3/12 
  Upstream   ports: 3/13 
  Outgoing   ports: 3/12 3/13

The table below describes the significant fields shown in the display.

Table 1. show ip pim snooping Field Descriptions
Field	Description
Downstream ports	Ports on which PIM joins were received.
Upstream ports	Ports towards RP and source.
Outgoing ports	List of all upstream and downstream ports for the multicast flow.

Related Commands


Command	Description
clear ip pim snooping vlan	Deletes PIM snooping on an interface.
ip pim snooping	Enables PIM snooping globally.
ip pim snooping vlan	Enables PIM snooping on an interface.

show ip pim tunnel

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]

Syntax Description


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.

Command Default

None

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.6.1	This command was introduced.

Usage Guidelines

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:

A PIM encapsulation tunnel (PIM Encap Tunnel)
A PIM decapsulation tunnel (PIM Decap Tunnel)

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

Examples

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:

Device# 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.

show platform software fed ip multicast groups

To display platform-dependent IP multicast groups information, use the show platform software fed ip multicast groups command in privileged EXEC mode.

show platform software fed { active | standby } ip multicast groups [ vrf-id vrf-id | vrf-name vrf-name ] [ group-address [ source source-address] [ detail] | count | summary ]

Syntax Description


`{` active `\|` standby `}`	The device for which you want to display information. active —Displays information for the active switch. standby —Displays information for the standby switch, if available.
vrf `vrf-id`	(Optional) Specifies the multicast Virtual Routing and Forwarding (VRF) ID.
vrf `vrf-name`	(Optional) Specifies the multicast Virtual Routing and Forwarding (VRF) name.
`group-address`	(Optional) Specifies the IP Multicast Group Address.
source `source-address`	(Optional) Specifies the IP Multicast Source Address
detail	(Optional) Specifies the IP Multicast group detail.
count	(Optional) Specifies the IP Multicast group count.
summary	(Optional) Specifies the Multicast group summary.

Command History


Release	Modification
	This command was introduced

Command Modes

Privileged EXEC (#)

Usage Guidelines

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.

show platform software fed active ip multicast

To display platform-dependent IP multicast tables and other information, use the show platform software fed active ip multicast command in privileged EXEC mode.

show platform software fed {active | standby} ip multicast {groups | [detail] | interfaces | retry}

Syntax Description


`{` active `\|` standby `}`	The device for which you want to display information. active —Displays information for the active switch. standby —Displays information for the standby switch, if available.
groups	Displays the IP multicast routes per group.
interfaces	Displays the IP multicast interfaces.
retry	Displays the IP multicast routes in the retry queue.

Command Modes

Privileged EXEC

Command History


Release	Modification
	This command was introduced.

Usage Guidelines

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.

Examples

The following example shows how to display platform IP multicast routes per group:


Device# show platform software fed active 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

==============================================================

<output truncated>

show platform software fed ip multicast df

To display information about platform-dependent IP multicast designated forwarders (DF), use the show platform software fed ip multicast df command in privileged EXEC mode.

show platform software fed {active | standby} ip multicast df [vrf-id | vrf-id | vrf-name | vrf-name] [df-index]

Syntax Description


`{` active `\|` standby `}`	The device for which you want to display information. active —Displays information for the active switch. standby —Displays information for the standby switch, if available.
vrf-id `vrf-id`	(Optional) Specifies the multicast Virtual Routing and Forwarding (VRF) ID.
vrf `vrf-name`	(Optional) Specifies the multicast Virtual Routing and Forwarding (VRF) name.
`df-index`	(Optional) Specifies the DF index.

Command Modes

Privileged EXEC (#)

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.12.1	This command was introduced.

Usage Guidelines

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.

Examples

The following is sample output from the show platform software fed ip multicast df command:

Device# show platform software fed active ip multicast df 
VRF-ID  DF-Index        Ref-Count       DF Set
================================================
2       1               1               Vlan254
                                        Vlan186
                                        Vlan305
                                        Vlan135
                                        Tunnel4
                                        Null0

Bias-Free Language

Results

Chapter: IP Multicast Routing Commands

IP Multicast Routing Commands

clear ip mfib counters

Syntax Description

Command Default

Command Modes

Command History

Examples

clear ip mroute

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

clear ip pim snooping vlan

Syntax Description

Command Default

Command Modes

Command History

Examples

Related Commands

debug condition vrf

Syntax Description

Command Modes

Command History

Usage Guidelines

Example

debug ip pim

Syntax Description

Command Modes

Command History

Usage Guidelines

Example

debug ipv6 pim

Syntax Description

Command Modes

Command History

Usage Guidelines

Example

ip igmp filter

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

ip igmp max-groups

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

ip igmp profile

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

ip igmp snooping

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

ip igmp snooping last-member-query-count

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

ip igmp snooping querier

Syntax Description