-
Cisco ASR 9000 Series Aggregation Services Router Multicast Command Reference
-
Preface
-
IGMP Commands on Cisco ASR 9000 Series Routers
-
Multicast Source Discovery Protocol Commands on Cisco ASR 9000 Series Routers
-
Multicast Routing and Forwarding Commands on Cisco ASR 9000 Series Routers
-
IGMP Snooping Commands on Cisco ASR 9000 Series Routers
-
Multicast PIM Commands on Cisco ASR 9000 Series Routers
-
Multicast Tool and Utility Commands on Cisco ASR 9000 Series Routers
-
Video Monitoring Commands on Cisco ASR 9000 Series Routers
-
Index
-
Feedback
Table Of Contents
IGMP Snooping Commands on Cisco ASR 9000 Series Routers
access-group (IGMP snooping profile)
clear igmp snooping bridge-domain
clear l2vpn forwarding bridge-domain mroute
internal-querier max-response-time
internal-querier query-interval
internal-querier robustness-variable
internal-querier tcn query count
internal-querier tcn query interval
show igmp snooping bridge-domain
show l2vpn forwarding bridge-domain mroute
IGMP Snooping Commands on Cisco ASR 9000 Series Routers
This chapter describes the commands used to configure and monitor IGMP snooping on Cisco ASR 9000 Series Aggregation Services Routers.
For detailed information about IGMP snooping concepts, configuration tasks, and examples, refer to the Implementing Layer 2 Multicast Using IGMP Snooping on Cisco ASR 9000 Series Routers module in the Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide.
access-group (IGMP snooping profile)
To instruct IGMP snooping to apply the specified access list filter to received membership reports, use the access-group command in IGMP snooping profile configuration mode. To discontinue membership report filtering, use the no form of this command.
access-group acl-name
no access-group
Syntax Description
Defaults
Membership reports are not filtered by default.
Command Modes
IGMP snooping profile configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Task ID
Examples
The following examples shows how to configure an ACL to filter membership reports:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# access-group acl-nameRelated Commands
clear igmp snooping bridge-domain
To clear IGMP snooping information at the bridge domain level, use the clear igmp snooping bridge-domain command in EXEC mode.
clear igmp snooping bridge-domain [bridge-domain-name] statistics [include-ports]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
In Release 3.7.2, the only items available for clearing are counters and statistics. You have the option to clear statistics for one or all bridge domains. You also have the option to clear only bridge domain statistics, or bridge domain statistics plus all statistics for all ports under the cleared bridge domains.
Task ID
Examples
The following example clears IGMP snooping statistics for all bridge domains on the router:
RP/0/RSP0/CPU0:router# clear igmp snooping bridge-domain statisticsThe following example clears IGMP snooping statistics for one bridge domain and all ports under it:
RP/0/RSP0/CPU0:router# clear igmp snooping bridge-domain bd-1 statistics include-portsRelated Commands
Displays IGMP snooping configuration information and statistics for bridge domains.
clear igmp snooping group
To clear IGMP snooping group states, use the clear igmp snooping group command in EXEC mode.
clear igmp snooping group [group-address]
[port {interface-name | neighbor ipaddr pw-id id} | bridge-domain bridge-domain]Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
IGMP snooping propagates the request to clear group information through the L2FIB to the forwarding plane. After this command is issued, IGMP snooping relearns group information by snooping packets as they are received from the network.
Use the address keyword to clear one group, identified by address. Otherwise, all groups are cleared. You can clear the named group from all ports or bridges, or from a specifically identified port or bridge.
Use the bridge-domain keyword to clear groups only for a named bridge domain. Use the port keyword to clear groups for a named port. A port can be an access interface or a pseudowire. The bridge-domain and port keywords are mutually exclusive.
Task ID
Examples
The following example clears all group membership information from the forwarding tables:
RP/0/RSP0/CPU0:router# clear igmp snooping groupThe following example clears one group from the forwarding table for one identified access circuit:
RP/0/RSP0/CPU0:router# clear igmp snooping group port GigabitEthernet0/1/1/1The following example clears all group membership information from the forwarding table for one identified pseudowire:
RP/0/RSP0/CPU0:router# clear igmp snooping group port neighbor 10.5.5.5 pw-id 5The following example clears one group from the forwarding table for one identified pseudowire:
RP/0/RSP0/CPU0:router# clear igmp snooping group 10.10.10.1 port neighbor 10.5.5.5 pw-id 5Related Commands
Displays IGMP snooping configuration information and statistics by group address.
clear igmp snooping port
To clear IGMP snooping port information, use the clear igmp snooping port command in EXEC mode.
clear igmp snooping port
[interface-name | neighbor ipaddr pw-id id | bridge-domain bridge-domain-name] statisticsSyntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
You can use this command to clear IGMP snooping information at the port level for:
•
All ports on the router
•
•
•
Task ID
Examples
The following example clears IGMP snooping port-level counters for all ports on the router.
RP/0/RSP0/CPU0:router# clear igmp snooping port statisticsThe following example clears IGMP snooping counters for one AC.
RP/0/RSP0/CPU0:router# clear igmp snooping port GigabitEthernet 0/1/1/1 statisticsThe following example clears IGMP snooping counters for one PW.
RP/0/RSP0/CPU0:router# clear igmp snooping port neighbor 10.5.5.5 pw-id 5 statisticsRelated Commands
Clears IGMP snooping information at the bridge level.
Displays IGMP snooping configuration information and statistics by port.
clear igmp snooping summary
To clear IGMP snooping summary counters, use the clear igmp snooping summary command in EXEC mode.
clear igmp snooping summary statistics
Syntax Description
statistics
Clears counters and other statistics. In Release 3.7.2, this is the only keyword available and it is required.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command clears summary level statistics about IGMP snooping. This command does not affect statistics at the bridge domain level or the port level.
Task ID
Examples
The following example clears all IGMP snooping statistics.
RP/0/RSP0/CPU0:router# clear igmp snooping summary statisticsRelated Commands
Displays IGMP snooping configuration and traffic statistics at a summary level for the router.
clear l2vpn forwarding bridge-domain mroute
To clear multicast routes from the Layer-2 forwarding tables, use the clear l2vpn forwarding bridge-domain mroute command in EXEC mode.
clear l2vpn forwarding bridge-domain [bg:bd] mroute [ipv4][location rack/slot/module]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command removes multicast routes in the Layer-2 forwarding information base (l2fib) tables. If you issue the command without a specific bridge group and bridge domain, information for all bridge groups and domains is cleared.
Note
Task ID
Examples
The following example clears all multicast routes across all bridge domains on one module.
RP/0/RSP0/CPU0:router# clear l2vpn forwarding mroute location 0/5/CPU0group limit
To specify the maximum number of groups or source-groups that may be joined on a port, use the group limit command in IGMP snooping profile configuration mode. By default, each group or source-group contributes a weight of 1 towards this limit. To remove the group limit, use the no form of this command.
group limit group-limit-value
no group limit group-limit-value
Note
Syntax Description
Command Default
No group limit
Command Modes
IGMP snooping profile configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
No new group or source group will be accepted if its contributed weight would cause this limit to be exceeded.
Task ID
Examples
The following example shows how to set the group limit of a port for weighting:
RP/0/RSP0/CPU0:router# configureRP/0/RSP0/CPU0:router(config)# igmp snooping profileRP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# group limit 699
Related Commands
group policy
To instruct IGMP snooping to use the specified route policy to determine the weight contributed by a new <*,G> or <S,G> membership request, use the group policy command in IGMP snooping profile configuration mode. To remove the group weight route policy from the profile and use the default group weight of 1 for all groups, use the no form of this command.
group policy policy-name
no group policy
Syntax Description
policy-name
Name of the route policy that should determine the weight contributed by a new <*,G> or <S,G> membership request.
Defaults
Default weight for all groups is 1. By default, no route policy is configured to determine the weight of new <*,G> or <S,G> membership requests.
Command Modes
IGMP snooping profile configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
To limit the number of IGMP v2/v3 groups, in which the maximum number of concurrently allowed multicast channels must be configurable on a per EFP-basis and per PW-basis, configure group weighting.
IGMP snooping limits the membership on a bridge port to a configured maximum limit. This feature also supports IGMPv3 source groups and allows different weights to be assigned to individual groups or source groups. This enables the IPTV provider, for example, to associate standard and high- definition IPTV streams, as appropriate, to specific subscribers.
This feature does not limit the actual multicast bandwidth that may be transmitted on a port. Rather, it limits the number of IGMP groups and source-groups, of which a port can be a member. It is the responsibility of the IPTV operator to configure subscriber membership requests to the appropriate multicast flows.
Task ID
Examples
The following example shows how to configure a group route policy for weighting new <*,G> or <S,G>membership requests:
RP/0/RSP0/CPU0:router# configureRP/0/RSP0/CPU0:router(config)# igmp snooping profileRP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# group policy policy nameRelated Commands
igmp snooping profile
To create or change an IGMP snooping profile, or to attach an IGMP snooping profile to a bridge or a port, use the igmp snooping profile command in the appropriate configuration mode. To detach a profile from a bridge domain or port, use the no form of this command. To delete a profile from the database, use the no form of this command in global configuration mode.
igmp snooping profile profile-name
no igmp snooping
Syntax Description
Defaults
IGMP snooping is inactive on a bridge domain until a profile is attached to the bridge domain.
Command Modes
Global configuration
L2 VPN bridge group bridge domain configuration
L2 VPN bridge group bridge domain interface configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command accomplishes different tasks depending on the configuration mode you are in when you issue it.
•
•
•
Creating Profiles
Use the igmp snooping profile command in global configuration mode to create a new IGMP snooping profile or to change an existing profile. The command enters you into IGMP snooping profile configuration mode, from which you can issue commands that configure IGMP snooping.
The minimum configuration is an empty profile. An empty profile enables IGMP snooping with a default configuration.
Enabling and Disabling IGMP Snooping
To enable IGMP snooping on a bridge domain, you must attach a profile to the bridge domain. To disable IGMP snooping on a bridge domain, detach the profile from the bridge domain.
Attaching a Profile to a Bridge Domain
To attach a profile to a bridge domain, use the igmp snooping profile command in Layer-2 VPN bridge group bridge domain configuration mode. At the bridge domain level, only one IGMP snooping profile can be attached to a bridge.
If a profile attached to a bridge domain contains port-specific configuration options, the values apply to all of the ports under the bridge, unless a port-specific profile is attached to one of the ports. In that case, the port with the attached profile is configured using only the commands in the port profile, and any port configurations in the bridge profile are ignored.
Attaching a Profile to a Port
Optionally, profiles can be attached to specific ports under a bridge domain. To attach a profile to a port, use the igmp snooping profile command in Layer-2 VPN bridge group bridge domain interface configuration mode. Each port can have only one port-specific profile attached to it.
IGMP snooping must be enabled on the bridge domain for any port-specific configurations to take effect. When a profile is attached to a port, IGMP snooping reconfigures that port, disregarding any port configurations that may exist in the bridge-level profile.
Detaching Profiles
To detach a profile from a bridge domain, use the no form of this command in Layer-2 VPN bridge group bridge domain configuration mode. To detach a profile from a port, use the no form of this command in the interface configuration mode under the bridge domain.
When you detach a profile from a bridge domain or a port, the profile still exists and is available for use at a later time.
Detaching a profile has the following results:
•
•
Changing Profiles
An active profile is one that is currently attached.
If you need to change an active profile, you must detach it from all bridges or ports, change it, and reattach it. An alternate procedure is to create a new profile incorporating the desired changes, detach the existing one, and immediately attach the new one.
To access an existing profile, use the igmp snooping profile command with the existing profile-name in global configuration mode. The command enters you into IGMP snooping profile configuration mode, from which you can issue commands to add to the current configuration or enter the no form of existing commands to delete them from the configuration.
Deleting a Profile
To delete a profile from the router database, use the no form of this command in global configuration mode.
Task ID
Examples
The following example shows how to create a new IGMP snooping profile or edit an existing profile:
router(config)# igmp snooping profile Profile-1router(config-igmp-snooping-profile)#The following example attaches a profile to the bridge domain ISP1:
RP/0/RSP0/CPU0:router(config)# l2vpnRP/0/RSP0/CPU0:router(config-l2vpn)# bridge group GRP1RP/0/RSP0/CPU0:router(config-l2vpn-bg)# bridge-domain ISP1RP/0/RSP0/CPU0:router(config-l2vpn-bg-bd)# igmp snooping profile profile-1The following example attaches a profile to the GigabitEthernet 0/1/1/1 port:
RP/0/RSP0/CPU0:router(config)# l2vpn
RP/0/RSP0/CPU0:router(config-l2vpn)# bridge group GRP1
RP/0/RSP0/CPU0:router(config-l2vpn-bg)# bridge-domain ISP1
RP/0/RSP0/CPU0: router(config-l2vpn-bg-bd)# interface GigabitEthernet 0/1/1/1
RP/0/RSP0/CPU0:router(config-l2vpn-bg-bd-if)# igmp snooping profile mrouter-port-profile
RP/0/RSP0/CPU0:router(config-l2vpn-bg-bd-if)# commit
immediate-leave
To configure fast leave processing on a port for IGMPv2 queriers, use the immediate-leave command in IGMP snooping profile configuration mode. To remove the functionality, use the no form of this command.
immediate-leave
no immediate-leave
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Immediate leave is an optional port-level configuration parameter. Immediate leave processing causes IGMP snooping to remove a Layer-2 interface from the forwarding table entry immediately, without first sending IGMP group-specific queries to the interface. Upon receiving an IGMP leave message, IGMP snooping immediately removes the interface from the Layer-2 forwarding table entry for that multicast group, unless a multicast router was learned on the port.
Immediate leave processing improves leave latency but is appropriate only when one receiver is configured on a port. For example, immediate leave is appropriate in the following situations:
•
•
Caution
Immediate leave processing is a port-level option. You can configure this option explicitly per port in port profiles or in the bridge domain profile, in which case it applies to all ports under the bridge.
Note
Task ID
Examples
The following example shows how to add immediate leave to a profile:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# immediate-leaveRelated Commands
internal-querier
To configure an internal IGMP querier on a bridge domain, use the internal-querier command in IGMP snooping profile configuration mode. To disable the internal querier, use the no form of this command.
internal-querier
no internal-querier
Syntax Description
This command has no arguments or keywords.
Defaults
The internal querier is disabled by default.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to configure an IGMP querier in a bridge domain where no external querier exists. An internal querier injects query packets into the bridge domain.
In a network where IP multicast routing is configured, the IP multicast router acts as the IGMP querier. In situations when no mrouter port exists in the bridge domain (because the multicast traffic does not need to be routed), but local multicast sources exist, you must configure an internal querier to implement IGMP snooping. The internal querier solicits membership reports from hosts in the bridge domain so that IGMP snooping can build constrained multicast forwarding tables for the multicast traffic within the bridge domain.
An internal querier might also be useful when there are interoperability issues that prevent IGMP snooping from working correctly with an external querier. In this case, you can:
1.
2.
3.
The minimum configuration for an internal querier is as follows. Both of the following commands are required.
•
•
You can disable the internal querier (using the no form of the internal-querier command) without removing any other internal querier commands. The additional internal querier commands are ignored in that case.
The scope for the internal-querier command is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
The local IGMP snooping process responds to the internal querier's general queries. In particular, the IGMPv3 proxy (if enabled) generates a current-state report and forwards it to all mrouters. For IGMPv2 or when the IGMPv3 proxy is disabled, IGMP snooping generates current-state reports for static group state only.
Task ID
Examples
The following example activates an internal querier with default configuration values:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# system-ip-address 10.1.1.1
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier
Related Commands
internal-querier max-response-time
To configure the maximum response time advertised by the internal querier, use the internal-querier max-response-time command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier max-response-time seconds
no internal-querier max-response-time
Syntax Description
seconds
Configures the maximum response time included in queries from the internal querier. Valid values are from 1 to 25 (seconds).
Defaults
10 (seconds)
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
The maximum response time (MRT) is the amount of time during which receivers are required to report their membership state.
In addition, the maximum response time is used in the calculation of the Group Management Interval (GMI). GMI controls when IGMP snooping expires stale group membership states. See the "Implementing IGMP Snooping on Cisco ASR 9000 Series Routers" module in the Cisco ASR 9000 Series Aggregation Services Routers Multicast Configuration Guide for more information about the GMI.
The maximum response time is advertised in general queries issued by the internal querier.
Task ID
Examples
The following example configures a maximum response time for the internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier max-response-time 5Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables an internal querier in the bridge domain.
internal-querier query-interval
To configure the time between general queries issued by the internal querier, use the internal-querier query-interval command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier query-interval seconds
no internal-querier query-interval
Syntax Description
seconds
Configures the number of seconds between general queries for membership reports issued by the internal querier. Valid values are from 1 to 18000 (seconds).
Defaults
60 (seconds). This is a nonstandard default value.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
When the internal querier is the active querier in the domain, it solicits membership reports by sending IGMP general queries at the interval specified by this command on every active port in the bridge domain.
Note
Task ID
Examples
The following example sets a query interval for the internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier query-interval 125Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables an internal querier in the bridge domain.
internal-querier robustness-variable
To configure the robustness variable for the internal querier, use the internal-querier robustness-variable command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier robustness-variable number
no internal-querier robustness-variable
Syntax Description
Defaults
2
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to set the internal querier's robustness variable to a value other than the default configuration value. If the internal querier is running IGMPv3, it advertises the robustness variable in its general queries.
In addition, the robustness variable is used in the calculation of the Group Management Interval (GMI). GMI controls when IGMP snooping expires stale group membership states. See the "Implementing IGMP Snooping on Cisco ASR 9000 Series Routers" module in the Cisco ASR 9000 Series Aggregation Services Routers Multicast Configuration Guide for more information about GMI.
Task ID
Examples
The following example configures the robustness variable for an internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier robustness-variable 3Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables an internal querier in the bridge domain.
internal-querier tcn query count
To configure the number of queries the internal querier sends after receiving a group leave from IGMP snooping, use the internal-querier tcn query count command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier tcn query count number
no internal-querier tcn query count
Syntax Description
Defaults
2
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
IGMP snooping reacts to Spanning Tree Protocol (STP) topology change notifications (TCNs) by flooding all multicast traffic and sending group leaves to expedite relearning. When the internal querier receives a group leave, it sends queries to solicit membership reports. This command configures the number of queries to send. The time between queries is controlled by the internal-querier tcn query interval command.
If you set internal-querier tcn query count to 0, the internal querier does not respond to group leaves.
Task ID
Examples
The following example configures the tcn query count for an internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier tcn query count 3Related Commands
internal-querier tcn query interval
To configure the time between queries that the internal querier sends after receiving a group leave from IGMP snooping, use the internal-querier tcn query interval command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier tcn query interval seconds
no internal-querier tcn query interval
Syntax Description
Defaults
10
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
IGMP snooping reacts to STP topology change notifications by flooding all multicast traffic and sending group leaves to expedite relearning. When the internal querier receives the group leave, it sends queries to solicit membership reports. This command configures the time between queries.
Task ID
Examples
The following example configures the tcn query interval for an internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier tcn query interval 100Related Commands
internal-querier timer expiry
To configure the time IGMP snooping waits to receive messages from an external querier before making the internal querier the active querier, use the internal-querier timer expiry command in IGMP snooping profile configuration configuration mode. To return to the default value, use the no form of this command.
internal-querier timer expiry seconds
no internal-querier timer expiry
Syntax Description
seconds
The time IGMP snooping waits to receive messages from an external querier before making the internal querier the active querier. Valid values are from 60 to 300 (seconds).
Defaults
125 (seconds), as defined in RFC-3376, Section 8.5:
(robustness-variable * query-interval) + ½(max-response-time)
Using the default values for all components:
(2 * 60) + ½ (10) = 125
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
A bridge domain can have only one active querier at a time. If the internal querier receives queries from another querier in a bridge domain, it performs querier election. The lowest IP address wins. If the internal querier is the election loser, IGMP snooping sets a timer to the internal-querier timer expiry value. If this timer expires before another query is received from the election winner, the internal querier becomes the active querier.
Task ID
Examples
The following example configures the timer expiry value for an internal querier, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier timer expiry 100Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables an internal querier in the bridge domain.
internal-querier version
To configure the IGMP version of the internal querier, use the internal-querier version command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
internal-querier version version
no internal-querier version
Syntax Description
version
Controls whether the internal querier sends IGMPv2 or IGMPv3 queries. Valid values are 2 or 3, representing IGMPv2 or IGMPv3.
Defaults
3
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
The internal querier sends IGMP queries on the bridge domain. This command sets the internal querier to run as either an IGMPv2 or IGMPv3 querier.
Task ID
Examples
The following example configures the internal querier to send IGMPv2 queries, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# internal-querier version 2Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables an internal querier in the bridge domain.
last-member-query count
To configure the number of group-specific queries IGMP snooping sends in response to a leave message, use the last-member-query count command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
last-member-query count number
no last-member-query count
Syntax Description
number
Specifies the number of queries IGMP snooping sends in response to a leave message. Valid values are from 1 to 7.
Defaults
2
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Last member query is the default group leave processing method used by IGMP snooping. With last member query processing, IGMP snooping processes leave messages as follows:
•
–
–
•
•
Task ID
Examples
The following example configures the number of queries that IGMP snooping sends in response to a leave, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# last-member-query count 1Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Configures the time between queries sent in response to an IGMP leave.
last-member-query interval
To configure the amount of time between group-specific queries, use the last-member-query interval command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
last-member-query interval milliseconds
no last-member-query interval
Syntax Description
milliseconds
Specifies the time between queries that IGMP snooping sends in response to a leave message. Valid values are from 100 to 5000 (milliseconds).
Defaults
1000 (milliseconds)
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Last member query is the default group leave processing method used by IGMP snooping. With last member query processing, IGMP snooping processes leave messages as follows:
•
–
–
•
•
Task ID
Examples
The following example configures the interval between queries that IGMP snooping sends in response to a leave, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# last-member-query interval 2000Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Configures the number of queries sent in response to an IGMP leave.
minimum-version
To change the IGMP versions supported by IGMP snooping, use the minimum-version command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
minimum-version number
no minimum-version
Syntax Description
Defaults
2 (supporting IGMPv2 and IGMPv3)
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
The minimum-version command controls which IGMP versions are supported by IGMP snooping in the bridge domain.
•
•
The scope for this configuration option is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example configures IGMP snooping to support only IGMPv3 and to ignore IGMPv2 reports and queries:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# minimum-version 3Related Commands
mrouter
To statically configure a port to receive query packets, use the mrouter command in IGMP snooping profile configuration mode. To remove the configuration, use the no form of this command.
mrouter
no mrouter
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
You can statically configure a port as an mrouter port with the mrouter command.
You can use the router-guard and the mrouter commands on the same port to configure a guarded port as a static mrouter. For example:
•
•
If you are using the router guard feature because there is an incompatible IGMP router on the port, you should also configure the mrouter command on the port to ensure that the router receives IGMP reports and multicast flows.
The scope of this command is port level. If you use this command in a profile attached to a bridge domain, you are configuring all ports as mrouter ports.
Task ID
Examples
The following example shows how to add static mrouter configuration to a profile:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# mrouterRelated Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Sets a port to send query packets to bridge domain ports.
Blocks query packets on the port.
querier query-interval
To configure the query interval for processing IGMPv2 membership states, use the querier query-interval command in IGMP snooping profile configuration mode. To return to the default setting, use the no form of this command.
querier query-interval seconds
no querier query-interval
Syntax Description
Defaults
60 (seconds). This is a nonstandard default value.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Query interval is the interval between general queries and is used in the calculated group management interval (GMI). GMI controls when IGMP snooping expires stale group membership states. For more information about GMI, see the "Implementing IGMP Snooping on Cisco ASR 9000 Series Routers" module in the Cisco ASR 9000 Series Aggregation Services Routers Multicast Configuration Guide.
If the querier is running IGMPv2, IGMP snooping uses the IGMP snooping configured values for robustness variable and query interval. These parameter values must match the configured values for the querier. In most cases, if you are interacting with other Cisco routers, you should not need to explicitly configure these values—the default values for IGMP snooping should match the default values of the querier. If they do not, use the querier robustness-variable and querier query-interval commands to configure matching values.
Note
Note
The scope for this command is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to add the command to a profile that configures the query interval:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# querier query-interval 1500Related Commands
querier robustness-variable
To configure the robustness variable for processing IGMPv2 membership states, use the querier robustness-variable command in IGMP snooping profile configuration mode. To return to the default setting, use the no form of this command.
querier robustness-variable robustness-number
no querier robustness-variable
Syntax Description
Defaults
2
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Robustness variable is an integer used to influence the calculated GMI. GMI controls when IGMP snooping expires stale group membership states. For more information about GMI, see the "Implementing IGMP Snooping on Cisco ASR 9000 Series Routers" module in the Cisco ASR 9000 Series Aggregation Services Routers Multicast Configuration Guide.
If the querier is running IGMPv2, IGMP snooping uses the IGMP snooping configured values for robustness variable and query interval. These parameter values must match the configured values for the querier. In most cases, if you are interacting with other Cisco routers, you should not need to explicitly configure these values—the default values for IGMP snooping should match the default values of the querier. If they do not, use the querier robustness-variable and querier query-interval commands to configure matching values.
Note
The scope for this command is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to add the command to a profile that configures the robustness variable:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# querier robustness-variable 1Related Commands
report-suppression disable
To disable IGMPv2 report suppression or IGMPv3 proxy reporting, use the report-suppression disable command in IGMP snooping profile configuration mode. To enable report suppression or proxy reporting functionality, use the no form of this command.
report-suppression disable
no report-suppression disable
Syntax Description
This command has no arguments or keywords.
Defaults
Report suppression and proxy reporting, whichever is appropriate, are enabled by default
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to disable report suppression for IGMPv2 queriers and proxy reporting for IGMPv3 queriers.
Both features are enabled by default, with the following results:
•
•
These features are enabled and disabled per bridge domain. This command is ignored if it appears in a profile attached to a port.
Task ID
Examples
The following example shows how to add the command to a profile to turn off report suppression and proxy reporting:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# report-suppression disableRelated Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Configures an IP address used by IGMP snooping.
router-alert-check disable
To disable the IGMP snooping check for the presence of the router alert option in the IP packet header, use the router-alert-check disable command in IGMP snooping profile configuration mode. To enable this functionality after a disable, use the no form of this command.
router-alert-check disable
no router-alert-check disable
Syntax Description
This command has no arguments or keywords.
Defaults
The router alert check feature is enabled by default.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
By default, IGMP snooping checks for the presence of the router alert option in the IP packet header of the IGMP message and drops packets that do not include this option. If your network performs this validation elsewhere, you can disable this IGMP snooping validation.
You can disable this check using the router-alert-check disable command, in which case IGMP snooping does perform the validation before processing the message.
The scope for this configuration option is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to add the command to a profile that turns off the router alert check:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# router-alert-check disableRelated Commands
router-guard
To block a port from receiving query packets, use the router-guard command in IGMP snooping profile configuration mode. To remove the restriction, use the no form of this command.
router-guard
no router-guard
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Router guard is a security feature that prevents malicious users from making a host port into an mrouter port. (This undesirable behavior is known as spoofing.) When a port is protected with the router-guard command, it cannot be dynamically discovered as an mrouter. When router guard is on a port, IGMP snooping filters protocol packets sent to the port and discards any that are multicast router control packets.
Caution
You can use the router-guard and the mrouter commands on the same port to configure a guarded port as a static mrouter. For example:
•
•
If you are using the router guard feature because there is an incompatible IGMP router on the port, you should also configure the mrouter command on the port to ensure that the router receives IGMP reports and multicast flows.
Task ID
Examples
The following example shows how to add the command to a profile that prevents a port from being dynamically discovered as an mrouter:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# router-guardRelated Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Sets a port to send query packets to bridge domain ports.
Sets a port to receive query packets.
show igmp snooping bridge-domain
To display IGMP snooping configuration information and traffic statistics for bridge domains, use the show igmp snooping bridge-domain command in EXEC mode.
show igmp snooping bridge-domain [bridge-domain-name] [detail [statistics [include-zeroes]]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command displays IGMP snooping information by bridge domain. Use the command without any keywords to display summary information about all bridge domains, in a single line per bridge domain.
Use optional keywords to request additional details and traffic statistics per bridge domain. You can also limit the display to a single bridge domain.
The statistics keyword displays IGMP traffic information, including IGMP queries, reports, and leaves. The three columns in the statistics section of the display are:
•
•
•
Task ID
Examples
The following example shows the basic command without any keywords.
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domainBridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-1 profile1 Y v2 8 2 5 0Group1:BD-2 N -- 0 0 0 0Group1:BD-3 profile1 Y v3 6 3 2 2Group1:BD-4 N -- 0 0 0 0Group1:BD-5 profile1 Y v3 2 1 1 0The following example shows the summary line for a named bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domain Group1:BD-1Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-1 profile1 Y v2 8 2 5 0The following example shows detailed information about all bridge domains:
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domain detailBridge Domains: 5IGMP Snooping Bridge Domains: 3Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-1 profile1 Y v2 8 2 5 0Profile Configured Attributes:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledQuerier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Querier:IP Address: 192.1.1.10Port: GigabitEthernet0/2/0/10.1Version: v2Query Interval: 60 secondsRobustness: 2Max Resp Time: 1.0 secondsTime since last G-Query: 8 secondsMrouter Ports: 2Dynamic: GigabitEthernet0/2/0/10.1Static: GigabitEthernet0/2/0/10.2STP Forwarding Ports: 0Groups: 5Member Ports: 9V3 Source Groups: 0Static/Include/Exclude: 0/0/0Member Ports (Include/Exclude): 0/0Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-2 N -- 0 0 0 0Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-3 profile1 Y v3 6 3 2 2Profile Configured Attributes:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledQuerier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Querier:IP Address: 192.1.1.10Port: GigabitEthernet0/2/0/10.11Version: v3Query Interval: 60 secondsRobustness: 2Max Resp Time: 10.0 secondsTime since last G-Query: 7 secondsMrouter Ports: 3Dynamic: GigabitEthernet0/2/0/10.11Dynamic: GigabitEthernet0/2/0/10.10Dynamic: GigabitEthernet0/2/0/10.9STP Forwarding Ports: 0Groups: 2Member Ports: 7V3 Source Groups: 2Static/Include/Exclude: 0/1/1Member Ports (Include/Exclude): 5/6Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-4 N -- 0 0 0 0Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-5 profile1 Y v3 2 1 1 0Profile Configured Attributes:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledQuerier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Querier:IP Address: 192.1.1.10Port: GigabitEthernet0/2/0/10.15Version: v3Query Interval: 60 secondsRobustness: 2Max Resp Time: 10.0 secondsTime since last G-Query: 6 secondsMrouter Ports: 1Dynamic: GigabitEthernet0/2/0/10.15STP Forwarding Ports: 0Groups: 1Member Ports: 2V3 Source Groups: 0Static/Include/Exclude: 0/0/0Member Ports (Include/Exclude): 0/0The following example displays traffic statistics with detailed information. The display omits many statistics whose values are zero.
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domain Group1:BD-1 detail statisticsBridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-1 profile1 Y v2 8 2 5 0Profile Configured Attributes:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledQuerier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Querier:IP Address: 192.1.1.10Port: GigabitEthernet0/2/0/10.1Version: v2Query Interval: 60 secondsRobustness: 2Max Resp Time: 1.0 secondsTime since last G-Query: 3 secondsMrouter Ports: 2Dynamic: GigabitEthernet0/2/0/10.1Static: GigabitEthernet0/2/0/10.2STP Forwarding Ports: 0Groups: 5Member Ports: 9V3 Source Groups: 0Static/Include/Exclude: 0/0/0Member Ports (Include/Exclude): 0/0Traffic Statistics (elapsed time since last cleared 00:32:04):Received Reinjected GeneratedMessages: 473 236 236IGMP General Queries: 237 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 236 236 236IGMP V3 Reports: 0 0 0IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 236Packets Consumed: 237Rx Errors:NoneTx Errors:NoneThe following example shows details for all statistics regardless of whether their values are zero.
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domain Group1:BD-1 detail statistics include-zeroesBridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs------------- ------- --- --- ------ ------ ----- ----Group1:BD-1 profile1 Y v2 8 2 5 0Profile Configured Attributes:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledQuerier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Querier:IP Address: 192.1.1.10Port: GigabitEthernet0/2/0/10.1Version: v2Query Interval: 60 secondsRobustness: 2Max Resp Time: 1.0 secondsTime since last G-Query: 3 secondsMrouter Ports: 2Dynamic: GigabitEthernet0/2/0/10.1Static: GigabitEthernet0/2/0/10.2STP Forwarding Ports: 0Groups: 5Member Ports: 9V3 Source Groups: 0Static/Include/Exclude: 0/0/0Member Ports (Include/Exclude): 0/0Traffic Statistics (elapsed time since last cleared 00:32:52):Received Reinjected GeneratedMessages: 486 243 242IGMP General Queries: 243 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 243 243 242IGMP V3 Reports: 0 0 0IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 243Packets Consumed: 243Reports Suppressed: 0IGMP Blocks Ignored in V2 Compat Mode: 0IGMP EX S-lists Ignored in V2 Compat Mode: 0Rx Errors:Packets On Inactive Bridge Domain: 0Packets On Inactive Port: 0Packets Martian: 0Packets Bad Protocol: 0Packets DA Not Multicast: 0Packets Missing Router Alert: 0Packets Missing Router Alert Drop: 0Packets Bad IGMP Checksum: 0Packets TTL Not One: 0Packets TTL Not One Drop: 0Queries Too Short: 0V1 Reports Too Short: 0V2 Reports Too Short: 0V3 Reports Too Short: 0V2 Leaves Too Short: 0IGMP Messages Unknown: 0IGMP Messages GT Max Ver: 0IGMP Messages LT Min Ver: 0Queries Bad Source: 0Queries Dropped by S/W Router Guard: 0General Queries DA Not All Nodes: 0GS-Queries Invalid Group: 0GS-Queries DA Not Group: 0GS-Queries Not From Querier: 0GS-Queries Unknown Group: 0Reports Invalid Group: 0Reports Link-Local Group: 0Reports DA Not Group: 0Reports No Querier: 0Leaves Invalid Group: 0Leaves DA Not All Routers: 0Leaves No Querier: 0Leaves Non-Member: 0Leaves Non-Dynamic Member: 0Leaves Non-V2 Member: 0V3 Reports Invalid Group: 0V3 Reports Link-Local Group: 0V3 Reports DA Not All V3 Routers: 0V3 Reports No Querier: 0V3 Reports Older Version Querier: 0V3 Reports Invalid Group Record Type: 0V3 Reports No Sources: 0V3 Leaves Non-Member: 0PIM Msgs Dropped by S/W Router Guard: 0Tx Errors:V3 Sources Not Reported: 0The detail statistics display shows the following new bridge-domain counters:
RP/0/RSP0/CPU0:router# show igmp snooping bridge-domain Group1:BD-1 detail statistics#Access Group Permits#Access Group Denials#Group Limits ExceededRelated Commands
show igmp snooping group
To display IGMP group membership information, use the show igmp snooping group command in EXEC mode.
show igmp snooping group
[summary [group-address]
[bridge-domain bridge-domain-name | port {interface-name | neighbor ipaddr pw-id id}]]
|
[[group-address]
[bridge-domain bridge-domain-name | port {interface-name | neighbor ipaddr pw-id id}]
[source source-address] [detail]]Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to display information about group membership in the Layer -2 forwarding tables. The display includes indicators identifying whether the group information was obtained dynamically (for example, snooped) or statically configured.
The command offers the following levels of detail:
•
•
•
Task ID
Examples
The following example shows group membership information by groups within bridge domains.
RP/0/RSP0/CPU0:router# show igmp snooping groupKey: GM=Group Filter Mode, PM=Port Filter ModeFlags Key: S=Static, D=Dynamic, E=Explicit TrackingBridge Domain Group1:BD-1Group Ver GM Source PM Port Exp Flg----- --- -- ------ -- ---- --- ---225.1.1.1 V2 - - - GigabitEthernet0/2/0/10.1 never S238.1.1.1 V2 - - - GigabitEthernet0/2/0/10.1 71 D238.1.1.1 V2 - - - GigabitEthernet0/2/0/10.5 103 D238.1.1.2 V2 - - - GigabitEthernet0/2/0/10.2 79 D238.1.1.2 V2 - - - GigabitEthernet0/2/0/10.6 111 D238.1.1.3 V2 - - - GigabitEthernet0/2/0/10.3 87 D238.1.1.3 V2 - - - GigabitEthernet0/2/0/10.7 119 D238.1.1.4 V2 - - - GigabitEthernet0/2/0/10.4 95 D238.1.1.4 V2 - - - GigabitEthernet0/2/0/10.8 63 DBridge Domain Group1:BD-3Group Ver GM Source PM Port Exp Flg----- --- -- ------ -- ---- --- ---227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.10 - D227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.11 - D227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.12 - D227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.13 - D227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.14 - D227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.9 - D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.10 123 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.11 83 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.12 91 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.13 99 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.14 107 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.9 115 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.10 121 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.11 129 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.12 89 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.13 97 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.14 105 D227.1.1.2 V3 EX * EX GigabitEthernet0/2/0/10.9 124 DBridge Domain Group1:BD-5Group Ver GM Source PM Port Exp Flg----- --- -- ------ -- ---- --- ---227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.15 114 D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.16 122 DThe following example shows group membership information by group within a specific bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping group bridge-domain Group1:BD-1Key: GM=Group Filter Mode, PM=Port Filter ModeFlags Key: S=Static, D=Dynamic, E=Explicit TrackingBridge Domain Group1:BD-1Group Ver GM Source PM Port Exp Flg----- --- -- ------ -- ---- --- ---225.1.1.1 V2 - - - GigabitEthernet0/2/0/10.1 never S238.1.1.1 V2 - - - GigabitEthernet0/2/0/10.1 84 D238.1.1.1 V2 - - - GigabitEthernet0/2/0/10.5 116 D238.1.1.2 V2 - - - GigabitEthernet0/2/0/10.2 92 D238.1.1.2 V2 - - - GigabitEthernet0/2/0/10.6 60 D238.1.1.3 V2 - - - GigabitEthernet0/2/0/10.3 100 D238.1.1.3 V2 - - - GigabitEthernet0/2/0/10.7 68 D238.1.1.4 V2 - - - GigabitEthernet0/2/0/10.4 108 D238.1.1.4 V2 - - - GigabitEthernet0/2/0/10.8 76 DThe following example shows group membership information by groups within a specific port.
RP/0/RSP0/CPU0:router# show igmp snooping group port GigabitEthernet 0/2/0/10.10Key: GM=Group Filter Mode, PM=Port Filter ModeFlags Key: S=Static, D=Dynamic, E=Explicit TrackingBridge Domain Group1:BD-3Group Ver GM Source PM Port Exp Flg----- --- -- ------ -- ---- --- ---227.1.1.1 V3 EX 10.1.1.1 EX GigabitEthernet0/2/0/10.10 - D227.1.1.1 V3 EX * EX GigabitEthernet0/2/0/10.10 111 D227.1.1.2 V3 EX 10.2.3.4 IN GigabitEthernet0/2/0/10.10 109 DThe following example summarizes each group's membership information into a single line.
RP/0/RSP0/CPU0:router# show igmp snooping group summaryBridge Domain Group1:BD-1#Mem #Inc #ExcGroup Source Ver GM Ports Ports Ports----- ------ --- -- ----- ----- -----225.1.1.1 - V2 - 1 - -238.1.1.1 - V2 - 2 - -238.1.1.2 - V2 - 2 - -238.1.1.3 - V2 - 2 - -238.1.1.4 - V2 - 2 - -Bridge Domain Group1:BD-3#Mem #Inc #ExcGroup Source Ver GM Ports Ports Ports----- ------ --- -- ----- ----- -----227.1.1.1 10.1.1.1 V3 EX - 0 6227.1.1.1 * V3 EX 6 - -227.1.1.1 * V3 EX 6 - -227.1.1.2 10.2.3.4 V3 EX - 5 0227.1.1.2 * V3 EX 1 - -227.1.1.2 * V3 EX 1 - -Bridge Domain Group1:BD-5#Mem #Inc #ExcGroup Source Ver GM Ports Ports Ports----- ------ --- -- ----- ----- -----227.1.1.1 * V3 EX 2 - -The following example shows detail information about each group.
RP/0/RSP0/CPU0:router# show igmp snooping group detailBridge Domain Group1:BD-1Group Address: 225.1.1.1Version: V2Uptime: 00:42:13Port Count: 1GigabitEthernet0/2/0/10.1:Uptime: 00:42:13Persistence: staticExpires: neverGroup Address: 238.1.1.1Version: V2Uptime: 00:41:38Port Count: 2GigabitEthernet0/2/0/10.1:Uptime: 00:41:38Persistence: dynamicExpires: 119GigabitEthernet0/2/0/10.5:Uptime: 00:41:06Persistence: dynamicExpires: 87Group Address: 238.1.1.2Version: V2Uptime: 00:41:30Port Count: 2GigabitEthernet0/2/0/10.2:Uptime: 00:41:30Persistence: dynamicExpires: 63GigabitEthernet0/2/0/10.6:Uptime: 00:40:58Persistence: dynamicExpires: 95Group Address: 238.1.1.3Version: V2Uptime: 00:41:22Port Count: 2GigabitEthernet0/2/0/10.3:Uptime: 00:41:22Persistence: dynamicExpires: 71GigabitEthernet0/2/0/10.7:Uptime: 00:40:50Persistence: dynamicExpires: 103Group Address: 238.1.1.4Version: V2Uptime: 00:41:14Port Count: 2GigabitEthernet0/2/0/10.4:Uptime: 00:41:14Persistence: dynamicExpires: 79GigabitEthernet0/2/0/10.8:Uptime: 00:40:42Persistence: dynamicExpires: 111Bridge Domain Group1:BD-3Group Address: 227.1.1.1Version: V3Uptime: 00:41:35Group Filter Mode: ExcludeSource Count: 1Static/Include/Exclude Source Count: 0/0/1Source: 10.1.1.1Static/Include/Exclude Port Count: 0/0/6Exclude Port Count: 6GigabitEthernet0/2/0/10.10:Uptime: 00:41:27Persistence: dynamicExpires: -GigabitEthernet0/2/0/10.11:Uptime: 00:41:19Persistence: dynamicExpires: -GigabitEthernet0/2/0/10.12:Uptime: 00:41:11Persistence: dynamicExpires: -GigabitEthernet0/2/0/10.13:Uptime: 00:41:03Persistence: dynamicExpires: -GigabitEthernet0/2/0/10.14:Uptime: 00:40:55Persistence: dynamicExpires: -GigabitEthernet0/2/0/10.9:Uptime: 00:41:35Persistence: dynamicExpires: -Source: *Exclude Port Count: 6GigabitEthernet0/2/0/10.10Uptime: 00:41:27Persistence: dynamicExpires: 91GigabitEthernet0/2/0/10.11Uptime: 00:41:19Persistence: dynamicExpires: 99GigabitEthernet0/2/0/10.12Uptime: 00:41:11Persistence: dynamicExpires: 107GigabitEthernet0/2/0/10.13Uptime: 00:41:03Persistence: dynamicExpires: 115GigabitEthernet0/2/0/10.14Uptime: 00:40:55Persistence: dynamicExpires: 123GigabitEthernet0/2/0/10.9Uptime: 00:41:35Persistence: dynamicExpires: 83Group Address: 227.1.1.2Version: V3Uptime: 00:41:37Group Filter Mode: ExcludeSource Count: 1Static/Include/Exclude Source Count: 0/1/0Source: 10.2.3.4Static/Include/Exclude Port Count: 0/5/0Include Port Count: 5GigabitEthernet0/2/0/10.10:Uptime: 00:41:29Persistence: dynamicExpires: 89GigabitEthernet0/2/0/10.11:Uptime: 00:41:21Persistence: dynamicExpires: 97GigabitEthernet0/2/0/10.12:Uptime: 00:41:13Persistence: dynamicExpires: 105GigabitEthernet0/2/0/10.13:Uptime: 00:41:05Persistence: dynamicExpires: 113GigabitEthernet0/2/0/10.14:Uptime: 00:40:57Persistence: dynamicExpires: 121Source: *Exclude Port Count: 1GigabitEthernet0/2/0/10.9Uptime: 00:41:34Persistence: dynamicExpires: 124Bridge Domain Group1:BD-5Group Address: 227.1.1.1Version: V3Uptime: 00:41:36Group Filter Mode: ExcludeSource: *Exclude Port Count: 2GigabitEthernet0/2/0/10.15Uptime: 00:41:36Persistence: dynamicExpires: 114GigabitEthernet0/2/0/10.16Uptime: 00:41:28Persistence: dynamicExpires: 122If a group limit is configured on an output port, the detail display shows the group weight value associated with each group or source group on that port:
RP/0/RSP0/CPU0:router# show igmp snooping port group detailBridge Domain bg1:bd1Port: GigabitEthernet0/2/0/10.2Group Address: 232.0.0.1Version: V3Uptime: 00:01:58Persistence: dynamicWeight: 21Expires: neverSource: 10.0.0.1Uptime: 00:00:29Persistence: dynamicWeight: 7Expires: 101Source: 10.0.0.2Uptime: 00:00:29Persistence: dynamicWeight: 7Expires: 101Source: 10.0.0.3Uptime: 00:00:29Persistence: dynamicWeight: 7Expires: 101Related Commands
show igmp snooping port
To display IGMP snooping configuration information and traffic counters by router interface port, use the show igmp snooping port command in EXEC mode.
show igmp snooping port
[interface-name | neighbor ipaddr pw-id id | bridge-domain bridge-domain-name]
[detail [statistics [include-zeroes] |[group [group-address] [source source-address] [detail]] ]Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command displays IGMP snooping information organized by IGMP snooping port. Use the command without any keywords to display summary information about all ports, in a single line per port.
Use optional arguments and keywords to request the following:
•
•
•
Note
•
•
The statistics keyword displays IGMP traffic information, including IGMP queries, reports, and leaves. The three columns in the statistics section of the display are:
•
•
•
Task ID
Examples
The following example shows summary information per port:
RP/0/RSP0/CPU0:router# show igmp snooping portBridge Domain Group1:BD-1Port State #Grps #SGs---- ----- ----- ----GigabitEthernet0/2/0/10.1 Up 2 0GigabitEthernet0/2/0/10.2 Up 1 0GigabitEthernet0/2/0/10.3 Up 1 0GigabitEthernet0/2/0/10.4 Up 1 0GigabitEthernet0/2/0/10.5 Up 1 0GigabitEthernet0/2/0/10.6 Up 1 0GigabitEthernet0/2/0/10.7 Up 1 0GigabitEthernet0/2/0/10.8 Up 1 0Bridge Domain Group1:BD-3Port State #Grps #SGs---- ----- ----- ----GigabitEthernet0/2/0/10.10 Up 2 2GigabitEthernet0/2/0/10.11 Up 2 2GigabitEthernet0/2/0/10.12 Up 2 2GigabitEthernet0/2/0/10.13 Up 2 2GigabitEthernet0/2/0/10.14 Up 2 2GigabitEthernet0/2/0/10.9 Up 2 1Bridge Domain Group1:BD-5Port State #Grps #SGs---- ----- ----- ----GigabitEthernet0/2/0/10.15 Up 1 0GigabitEthernet0/2/0/10.16 Up 1 0The following example shows summary information for a specific port.
RP/0/RSP0/CPU0:router# show igmp snooping port GigabitEthernet 0/2/0/10.10Bridge Domain Group1:BD-3Port State #Grps #SGs---- ----- ----- ----GigabitEthernet0/2/0/10.10 Up 2 2The following information shows summary information for all ports under a specific bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping port bridge-domain Group1:BD-1Bridge Domain Group1:BD-1Port State #Grps #SGs---- ----- ----- ----GigabitEthernet0/2/0/10.1 Up 2 0GigabitEthernet0/2/0/10.2 Up 1 0GigabitEthernet0/2/0/10.3 Up 1 0GigabitEthernet0/2/0/10.4 Up 1 0GigabitEthernet0/2/0/10.5 Up 1 0GigabitEthernet0/2/0/10.6 Up 1 0GigabitEthernet0/2/0/10.7 Up 1 0GigabitEthernet0/2/0/10.8 Up 1 0The following example shows detail information about a specified port.
RP/0/RSP0/CPU0:router# show igmp snooping port GigabitEthernet 0/2/0/10.1 detailGigabitEthernet0/2/0/10.1 is UpBridge Domain: Group1:BD-1IGMP Snoop Profile: profile2Dynamic Mrouter Port: Querier(192.1.1.10)Expires: 116 secondsIGMP Groups: 2Static/Dynamic: 1/1IGMP Source Groups: 0Static/Include/Exclude: 0/0/0The following example shows detail information that includes the total group weight accumulated by all groups and source groups on the port and the configured limit—Admitted Weight: 12/16:
RP/0/RSP0/CPU0:router# show igmp snooping port gigabitEthernet 0/2/0/10.2 detail
GigabitEthernet0/2/0/10.2 is Up
Bridge Domain: bg1:bd1
IGMP Groups: 4
Static/Dynamic: 0/4
IGMP Source Groups: 0
Static/Include/Exclude: 0/0/0
Admitted Weight: 33/36
The following example shows detail, including statistics, for a specified port.
RP/0/RSP0/CPU0:router# show igmp snooping port GigabitEthernet 0/2/0/10.1 detail statisticsGigabitEthernet0/2/0/10.1 is UpBridge Domain: Group1:BD-1IGMP Snoop Profile: profile2Dynamic Mrouter Port: Querier(192.1.1.10)Expires: 117 secondsIGMP Groups: 2Static/Dynamic: 1/1IGMP Source Groups: 0Static/Include/Exclude: 0/0/0Access Group PermitsAccess Group DenialsGroup Limits ExceededTraffic Statistics (elapsed time since last cleared 01:19:32):Received Reinjected GeneratedMessages: 668 75 0IGMP General Queries: 593 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 75 75 0IGMP V3 Reports: 0 0 0IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 75Packets Consumed: 593Rx Errors:NoneTx Errors:NoneThe following example shows all statistics, even those with zero values, for a specified port.
RP/0/RSP0/CPU0:router# show igmp snooping port GigabitEthernet 0/2/0/10.1 detail statistics include-zeroesGigabitEthernet0/2/0/10.1 is UpBridge Domain: Group1:BD-1IGMP Snoop Profile: profile2Dynamic Mrouter Port: Querier(192.1.1.10)Expires: 120 secondsIGMP Groups: 2Static/Dynamic: 1/1IGMP Source Groups: 0Static/Include/Exclude: 0/0/0Traffic Statistics (elapsed time since last cleared 01:20:42):Received Reinjected GeneratedMessages: 678 76 0IGMP General Queries: 602 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 76 76 0IGMP V3 Reports: 0 0 0IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 76Packets Consumed: 602Reports Suppressed: 0IGMP Blocks Ignored in V2 Compat Mode: 0IGMP EX S-lists Ignored in V2 Compat Mode: 0Rx Errors:Packets On Inactive Bridge Domain: 0Packets On Inactive Port: 0Packets Martian: 0Packets Bad Protocol: 0Packets DA Not Multicast: 0Packets Missing Router Alert: 0Packets Missing Router Alert Drop: 0Packets Bad IGMP Checksum: 0Packets TTL Not One: 0Packets TTL Not One Drop: 0Queries Too Short: 0V1 Reports Too Short: 0V2 Reports Too Short: 0V3 Reports Too Short: 0V2 Leaves Too Short: 0IGMP Messages Unknown: 0IGMP Messages GT Max Ver: 0IGMP Messages LT Min Ver: 0Queries Bad Source: 0Queries Dropped by S/W Router Guard: 0General Queries DA Not All Nodes: 0GS-Queries Invalid Group: 0GS-Queries DA Not Group: 0GS-Queries Not From Querier: 0GS-Queries Unknown Group: 0Reports Invalid Group: 0Reports Link-Local Group: 0Reports DA Not Group: 0Reports No Querier: 0Leaves Invalid Group: 0Leaves DA Not All Routers: 0Leaves No Querier: 0Leaves Non-Member: 0Leaves Non-Dynamic Member: 0Leaves Non-V2 Member: 0V3 Reports Invalid Group: 0V3 Reports Link-Local Group: 0V3 Reports DA Not All V3 Routers: 0V3 Reports No Querier: 0V3 Reports Older Version Querier: 0V3 Reports Invalid Group Record Type: 0V3 Reports No Sources: 0V3 Leaves Non-Member: 0PIM Msgs Dropped by S/W Router Guard: 0Tx Errors:V3 Sources Not Reported: 0The following information shows summary information for all port groups under a specific bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping port bridge-domain Group1:BD-1 groupKey: GM=Group Filter Mode, PM=Port Filter ModeFlags Key: S=Static, D=Dynamic, E=Explicit TrackingBridge Domain Group1:BD-1Port PM Group Ver GM Source Exp Flg---- -- ----- --- -- ------ --- ---GigabitEthernet0/2/0/10.1 - 225.1.1.1 V2 - - never SGigabitEthernet0/2/0/10.1 - 238.1.1.1 V2 - - 77 DGigabitEthernet0/2/0/10.2 - 238.1.1.2 V2 - - 85 DGigabitEthernet0/2/0/10.3 - 238.1.1.3 V2 - - 93 DGigabitEthernet0/2/0/10.4 - 238.1.1.4 V2 - - 101 DGigabitEthernet0/2/0/10.5 - 238.1.1.1 V2 - - 109 DGigabitEthernet0/2/0/10.6 - 238.1.1.2 V2 - - 117 DGigabitEthernet0/2/0/10.7 - 238.1.1.3 V2 - - 61 DGigabitEthernet0/2/0/10.8 - 238.1.1.4 V2 - - 69 DThe following information shows detail information for all port groups under a specific bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping port bridge-domain Group1:BD-1 group detailBridge Domain Group1:BD-1Port: GigabitEthernet0/2/0/10.1Group Address: 225.1.1.1Version: V2Uptime: 01:27:20Persistence: staticExpires: neverGroup Address: 238.1.1.1Version: V2Uptime: 01:26:45Persistence: dynamicExpires: 100Port: GigabitEthernet0/2/0/10.2Group Address: 238.1.1.2Version: V2Uptime: 01:26:37Persistence: dynamicExpires: 108Port: GigabitEthernet0/2/0/10.3Group Address: 238.1.1.3Version: V2Uptime: 01:26:29Persistence: dynamicExpires: 116Port: GigabitEthernet0/2/0/10.4Group Address: 238.1.1.4Version: V2Uptime: 01:26:21Persistence: dynamicExpires: 60Port: GigabitEthernet0/2/0/10.5Group Address: 238.1.1.1Version: V2Uptime: 01:26:13Persistence: dynamicExpires: 68Port: GigabitEthernet0/2/0/10.6Group Address: 238.1.1.2Version: V2Uptime: 01:26:05Persistence: dynamicExpires: 76Port: GigabitEthernet0/2/0/10.7Group Address: 238.1.1.3Version: V2Uptime: 01:25:57Persistence: dynamicExpires: 84Port: GigabitEthernet0/2/0/10.8Group Address: 238.1.1.4Version: V2Uptime: 01:25:49Persistence: dynamicExpires: 92Related Commands
show igmp snooping profile
To display IGMP snooping profile information, use the show igmp snooping profile command in EXEC mode.
show igmp snooping profile [summary] |
[profile-name] [detail [include-defaults]]
[references [bridge-domain [bridge-domain-name] ] | port [ {interface-name | neighbor ipaddr pw-id id}] ]Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to display the contents of profiles and to see associations of profiles with bridge-domains and ports.
The summary keyword lists profile names and summarizes their usage on bridge domains and ports. No other keywords can be used with summary.
Use the details keyword with a profile name to show the contents of a specific profile. Without a profile name, the detail keyword shows the contents of all profiles.
Use the references keyword to list the relationships between profiles and bridge domains or profiles and ports. You have the following options:
•
•
•
•
•
•
Task ID
Examples
The following example lists profile names and shows summary level profile usage.
RP/0/RSP0/CPU0:router# show igmp snooping profileProfile Bridge Domain Port------- ------------- ----profile1 3 0profile2 0 1profile3 0 1The following example shows summary level profile usage for a named profile.
RP/0/RSP0/CPU0:router# show igmp snooping profile profile1Profile Bridge Domain Port------- ------------- ----profile1 3 0The following example shows the contents of each profile.
RP/0/RSP0/CPU0:router# show igmp snooping profile detailIGMP Snoop Profile profile1:Bridge Domain References: 3Port References: 0IGMP Snoop Profile profile2:Static Groups: 225.1.1.1Bridge Domain References: 0Port References: 1IGMP Snoop Profile profile3:Static Mrouter: EnabledBridge Domain References: 0Port References: 1The following example shows output reflecting the access-group, group limit, and tcn flood disable parameters:
RP/0/RSP0/CPU0:router# show igmp snooping profile detailIGMP Snoop Profile profile:Querier LMQ Count: 2Access Group ACL: iptv-white-listGroup Policy: iptv-group-weightsGroup Limit: 16Immediate Leave: EnabledTCN Flood: DisabledBridge Domain References: 1Port References: 0The following example shows the contents of a named profile. In this example, the profile is empty.
RP/0/RSP0/CPU0:router# show igmp snooping profile profile1 detailIGMP Snoop Profile profile1:Bridge Domain References: 3Port References: 0The following example shows the contents of a named profile and the implied default configurations:
RP/0/RSP0/CPU0:router# show igmp snooping profile profile1 detail include-defaultsIGMP Snoop Profile profile1:System IP Address: 0.0.0.0Minimum Version: 2Report Suppression: EnabledTCN Query Solicit: DisabledTCN Flood Query Count: 2Router Alert Check: EnabledTTL Check: EnabledInternal Querier Support: DisabledInternal Querier Version: 3Internal Querier Timeout: 0 (seconds)Internal Querier Interval: 60 (seconds)Internal Querier Max Response Time: 10 (seconds)Internal Querier TCN Query Interval: 10 (seconds)Internal Querier TCN Query Count: 2Internal Querier Robustness: 2Querier Query Interval: 60 (seconds)Querier LMQ Interval: 1000 (milliseconds)Querier LMQ Count: 2Querier Robustness: 2Immediate Leave: DisabledExplicit Tracking: DisabledStatic Mrouter: DisabledRouter Guard: DisabledBridge Domain References: 3Port References: 0The following command shows a summary of profile usage, by profile name.
RP/0/RSP0/CPU0:router# show igmp snooping profile summaryNumber of profiles: 3Number of bridge domain references: 3Number of port references: 2The following command lists all IGMP snooping profiles and shows which bridge domains and ports are configured to use each profile.
RP/0/RSP0/CPU0:router# show igmp snooping profile referencesProfile: profile1Bridge Domains: Group1:BD-5Group1:BD-3Group1:BD-1No Port ReferencesProfile: profile2No Bridge Domain ReferencesPorts: GigabitEthernet0/2/0/10.1Profile: profile3No Bridge Domain ReferencesPorts: GigabitEthernet0/2/0/10.2The following command lists all bridges or ports that are configured to use the profile named profile1.
RP/0/RSP0/CPU0:router# show igmp snooping profile profile1 referencesProfile: profile1Bridge Domains: NonePorts: GigabitEthernet 0/1/0/0GigabitEthernet 0/1/0/1GigabitEthernet 0/1/0/2GigabitEthernet 0/1/0/3GigabitEthernet 0/1/0/4GigabitEthernet 0/1/0/5(... missing lines)GigabitEthernet 0/3/3/1109GigabitEthernet 0/3/3/1110GigabitEthernet 0/3/3/1111The following example shows the profile attached to a specific bridge domain.
RP/0/RSP0/CPU0:router# show igmp snooping profile references bridge-domain Group1:BD-1Profile: profile1Bridge Domains: Group1:BD-1The following example shows the profile attached to a specific port.
RP/0/RSP0/CPU0:router# show igmp snooping profile references port GigabitEthernet 0/2/0/10.1Profile: profile2Ports: GigabitEthernet0/2/0/10.1Related Commands
Creates or edits a profile.
Shows profile names associated with the bridge domain and its ports.
show igmp snooping summary
To display summary information about IGMP snooping configuration and traffic statistics for the router, use the show igmp snooping summary command in EXEC mode.
show igmp snooping summary [statistics [include-zeroes]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
Three new fields were added to the output for the statistics display.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command summarizes the number of bridge domains, mrouter ports, host ports, groups, and sources configured on the router.
The statistics keyword displays IGMP traffic information, including IGMP queries, reports, and leaves. The three columns in the statistics section of the display are:
•
•
•
Task ID
Examples
The following example summarizes IGMP snooping configuration on the router:
RP/0/RSP0/CPU0:router# show igmp snooping summaryBridge Domains: 5IGMP Snooping Bridge Domains: 3Ports: 16IGMP Snooping Ports: 16Mrouters: 6STP Forwarding Ports: 0IGMP Groups: 8Member Ports: 18IGMP Source Groups: 2Static/Include/Exclude: 0/1/1Member Ports (Include/Exclude): 5/6The following example summarizes IGMP snooping configuration on the router and includes non-zero traffic statistics:
RP/0/RSP0/CPU0:router# show igmp snooping summary statisticsBridge Domains: 5IGMP Snooping Bridge Domains: 3Ports: 16IGMP Snooping Ports: 16Mrouters: 6STP Forwarding Ports: 0IGMP Groups: 8Member Ports: 18IGMP Source Groups: 2Static/Include/Exclude: 0/1/1Member Ports (Include/Exclude): 5/6Access Group PermitsAccess Group DenialsGroup Limits ExceededTraffic Statistics (elapsed time since last cleared 02:08:21):Received Reinjected GeneratedMessages: 7150 894 2381IGMP General Queries: 2682 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 1787 894 893IGMP V3 Reports: 2681 0 1488IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 894Packets Consumed: 6256Rx Errors:NoneTx Errors:NoneThe following example shows all summary statistics, including those whose value is zero.
RP/0/RSP0/CPU0:router# show igmp snooping summary statistics include-zeroesBridge Domains: 5IGMP Snooping Bridge Domains: 3Ports: 16IGMP Snooping Ports: 16Mrouters: 6STP Forwarding Ports: 0IGMP Groups: 8Member Ports: 18IGMP Source Groups: 2Static/Include/Exclude: 0/1/1Member Ports (Include/Exclude): 5/6Traffic Statistics (elapsed time since last cleared 02:08:56):Received Reinjected GeneratedMessages: 7185 898 2395IGMP General Queries: 2695 0 0IGMP Group Specific Queries: 0 0 0IGMP G&S Specific Queries: 0 0 0IGMP V2 Reports: 1796 898 898IGMP V3 Reports: 2694 0 1497IGMP V2 Leaves: 0 0 0IGMP Global Leaves: 0 - 0PIM Hellos: 0 0 -Rx Packet Treatment:Packets Flooded: 0Packets Forwarded To Members: 0Packets Forwarded To Mrouters: 898Packets Consumed: 6287Reports Suppressed: 0IGMP Blocks Ignored in V2 Compat Mode: 0IGMP EX S-lists Ignored in V2 Compat Mode: 0Rx Errors:Packets On Inactive Bridge Domain: 0Packets On Inactive Port: 0Packets Martian: 0Packets Bad Protocol: 0Packets DA Not Multicast: 0Packets Missing Router Alert: 0Packets Missing Router Alert Drop: 0Packets Bad IGMP Checksum: 0Packets TTL Not One: 0Packets TTL Not One Drop: 0Queries Too Short: 0V1 Reports Too Short: 0V2 Reports Too Short: 0V3 Reports Too Short: 0V2 Leaves Too Short: 0IGMP Messages Unknown: 0IGMP Messages GT Max Ver: 0IGMP Messages LT Min Ver: 0Queries Bad Source: 0Queries Dropped by S/W Router Guard: 0General Queries DA Not All Nodes: 0GS-Queries Invalid Group: 0GS-Queries DA Not Group: 0GS-Queries Not From Querier: 0GS-Queries Unknown Group: 0Reports Invalid Group: 0Reports Link-Local Group: 0Reports DA Not Group: 0Reports No Querier: 0Leaves Invalid Group: 0Leaves DA Not All Routers: 0Leaves No Querier: 0Leaves Non-Member: 0Leaves Non-Dynamic Member: 0Leaves Non-V2 Member: 0V3 Reports Invalid Group: 0V3 Reports Link-Local Group: 0V3 Reports DA Not All V3 Routers: 0V3 Reports No Querier: 0V3 Reports Older Version Querier: 0V3 Reports Invalid Group Record Type: 0V3 Reports No Sources: 0V3 Leaves Non-Member: 0PIM Msgs Dropped by S/W Router Guard: 0Tx Errors:V3 Sources Not Reported: 0
show igmp snooping trace
To display IGMP snooping process activity, use the show igmp snooping trace command in EXEC mode.
show igmp snooping trace [all | error | packet-error]
Syntax Description
all
(Optional) Displays all IGMP snooping process activity.
error
(Optional) Displays only error tracepoints.
packet-error
(Optional) Displays packet error tracepoints.
Defaults
The all keyword is the default when no keywords are used.
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Use this command to research IGMP snooping process activity.
Task ID
Examples
The following example shows IGMP snooping process status during a restart and a new profile configuration.
RP/0/RSP0/CPU0:router# show igmp snooping summary trace all51 wrapping entries (1024 possible, 0 filtered, 51 total)Feb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP001:Feb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP002: ******** IGMP SNOOP PROCESS RESTART ********Feb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP001:Feb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP286: initialize profile wavl treeFeb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP185: initialize bd wavl treeFeb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP230: initialize port wavl treeFeb 2 14:30:24.902 igmpsn/all 0/5/CPU0 t1 TP019: entered init_chkptFeb 2 14:30:24.934 igmpsn/all 0/5/CPU0 t1 TP165: igmpsn_init_l2fib enteredFeb 2 14:30:24.934 igmpsn/all 0/5/CPU0 t1 TP611: l2fib_restart_timer_initFeb 2 14:30:24.935 igmpsn/all 0/5/CPU0 t1 TP680: igmpsn_pd_mgid_api_init enteredFeb 2 14:30:24.937 igmpsn/all 0/5/CPU0 t1 TP681: failed to open libl2mc_snoop_mgid_client_pd.dllFeb 2 14:30:24.937 igmpsn/all 0/5/CPU0 t1 TP683: l2mc_snoop_pd_mgid funcs are stubbedFeb 2 14:30:25.037 igmpsn/all 0/5/CPU0 t1 TP080: socket open succeededFeb 2 14:30:25.037 igmpsn/all 0/5/CPU0 t1 TP031: connection open for socketFeb 2 14:30:25.037 igmpsn/all 0/5/CPU0 t1 TP614: igmpsn_l2fib_restart_timer_start, 300 secsFeb 2 14:30:25.038 igmpsn/all 0/5/CPU0 t1 TP555: IGMP SNOOP PROCESS READYFeb 2 14:30:25.038 igmpsn/all 0/5/CPU0 t1 TP017: entered event loopFeb 2 14:30:25.038 igmpsn/all 0/5/CPU0 t1 TP112: sysdb register verificationFeb 2 14:30:25.038 igmpsn/all 0/5/CPU0 t1 TP286: initialize profile wavl treeFeb 2 14:30:25.040 igmpsn/all 0/5/CPU0 t1 TP110: sysdb event verify func (CREATE & SET, profile/profile1/enter)Feb 2 14:30:25.040 igmpsn/all 0/5/CPU0 t1 TP287: create profile profile1Feb 2 14:30:25.040 igmpsn/all 0/5/CPU0 t1 TP534: profile profile1 (0x4826b838): initialized static_group tree(... missing lines)show l2vpn forwarding bridge-domain mroute
To display multicast routes in the forwarding tables, use the show l2vpn forwarding bridge-domain mroute command in EXEC mode.
show l2vpn forwarding bridge-domain [bridge-group-name:
bridge-domain-name] mroute [ipv4] location rack/slot/moduleSyntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
This command displays multicast routes as they are converted into the forwarding plane forwarding tables. The source for the conversion is the multicast routes configured in the control plane with IGMP snooping configuration commands. If the routes displayed by this command are not as expected, check the control plane configuration and correct the corresponding IGMP snooping profiles.
Use optional arguments to limit the display to a specific bridge domain.
Task ID
Examples
The following example displays high-level statistics about routes for one bridge domain:
RP/0/RSP0/CPU0:router# show l2vpn forwarding bridge-domain bg1:bg1_BD1 mroute ipv4 location 0/5/CPU0Bridge-Domain: bg1:bg1_BD1, ID: 252(0.0.0.0,224.0.0.0/4)IngressForwarded (Packets/Bytes): 2129283957/127757096820Received (Packets/Bytes): 533277430/31996645800Punted (Packets/Bytes): 0/0Dropped (Packets/Bytes): 0/0Neighbor 10.2.2.2, pw-id 200, Xconnect id: 0xfffc0049Bridge-Domain: bg1:bg1_BD1, ID: 252(0.0.0.0,225.1.1.1/32)IngressForwarded (Packets/Bytes): 345092440/20705546400Received (Packets/Bytes): 86368278/5182096680Punted (Packets/Bytes): 0/0Dropped (Packets/Bytes): 0/0GigabitEthernet0/5/0/0, Xconnect id: 0x1c402d1Neighbor 10.2.2.2, pw-id 200, Xconnect id: 0xfffc0049static group
To configure static group membership entries in the Layer-2 forwarding tables, use the static group command in IGMP snooping profile configuration mode. To remove a static group entry from the forwarding tables, use the no form of this command.
static group group-addr [source source-addr]
no static group group-addr [source source-addr]
Syntax Description
group-addr
IP multicast group address.
source source-addr
(Optional) Statically forwards an (S, G) channel out of the port.
Defaults
No default behavior or values
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
IGMP snooping learns Layer-2 multicast groups dynamically. You can also statically configure Layer-2 multicast groups.
You can use the static group command in profiles intended for bridge domains or ports. I f you configure this option in a profile attached to a bridge domain, it applies to all ports under the bridge.
A profile can contain multiple static groups. You can define different source addresses for the same group address. Using the source keyword, you can configure IGMPv3 source groups.
Static group membership supersedes any dynamic manipulation by IGMP snooping. Multicast group membership lists can contain both static and dynamic group definitions.
When you configure a static group or source group on a port, IGMP snooping adds the port as an outgoing port to the corresponding <S/*,G> forwarding entry and sends an IGMPv2 join or IGMPv3 report to all mrouter ports. IGMP snooping continues to send the membership report in response to general queries for as long as the static group remains configured on the port.
The scope of this command can be either bridge domain level or port level. If you use this command in a profile attached to a bridge domain, the static group membership applies to all ports under the bridge. If you use the command in a profile attached to a port, the static group membership applies only to that port.
Task ID
Examples
The following examples show how to add static group membership configuration into an IGMP snooping profile:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# static group 10.1.1.1RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# static group 10.1.1.1 source 10.1.12.0Related Commands
system-ip-address
To configure an IP address for the internal querier, use the system-ip-address command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
system-ip-address ip-address
no system-ip-address
Syntax Description
Defaults
0.0.0.0
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
The system-ip-address command configures an IP address for IGMP snooping use. If not explicitly configured, the default address is 0.0.0.0. The default is adequate except in the following circumstances:
•
•
IGMP snooping uses the value set by the system-ip-address command in the following ways:
•
•
•
Task ID
Examples
The following example assigns a system IP address, overriding the default value:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# system-ip-address 10.1.1.1Related Commands
tcn flood disable
To disable Spanning Tree Protocol (STP) port flooding during a topology change, use the tcn flood disable command in IGMP snooping profile configuration mode. To reenable STP port flooding, use the no form of this command.
tcn flood disable
no tcn flood disable
Syntax Description
This command has no arguments or keywords.
Defaults
TCN flooding is enabled by default.
Command Modes
IGMP snooping profile configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Task ID
Examples
This example illustrates how to disable TCN flooding:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# tcn flood disable
Related Commands
tcn flood query count
To configure how long IGMP snooping floods all routes in response to topology changes, use the tcn flood query count command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
tcn flood query count number
no tcn flood query count
Syntax Description
Defaults
2
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
In a Spanning Tree Protocol (STP) topology, a topology change notification (TCN) indicates that an STP topology change has occurred. As a result of a topology change, mrouters and hosts reporting group membership may migrate to other STP ports under the bridge domain. Mrouter and membership states must be relearned after a TCN.
IGMP snooping reacts to TCNs in the following way:
1.
2.
Note
3.
IGMP snooping default behavior is that the STP root bridge always issues a global leave in response to a TCN, and the non-root bridges do not issue global leaves.
With the tcn query solicit command, you can enable a bridge to always issue a global leave in response to TCNs, even when it is not the root bridge. In that case, the root bridge and the non-root bridge would issue the global leave and both would solicit general queries in response to a TCN. Use the no form of the command to turn off soliciting when the bridge is not the root.
The root bridge always issues a global leave in response to a TCN. This behavior can not be disabled.
The internal querier has its own set of configuration options that control its reactions to TCNs.
The scope for this configuration option is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to configure the tcn flood query count in an IGMP snooping profile, overriding the default:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# tcn flood query count 5Related Commands
Creates or edits a profile, and attaches a profile to a bridge domain or port.
Enables global leave messaging on non-root bridges in response to STP topology changes.
tcn query solicit
To enable global leave messaging on non-root bridges in response to STP topology changes, use the tcn query solicit command in IGMP snooping profile configuration mode. To disable this functionality (on non-root bridges), use the no form of this command.
tcn query solicit
no tcn query solicit
Syntax Description
This command has no arguments or keywords.
Defaults
It is disabled by default.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
In a Spanning Tree Protocol (STP) topology, a topology change notification (TCN) indicates that an STP topology change has occurred. As a result of a topology change, mrouters and hosts reporting group membership may migrate to other STP ports under the bridge domain. Mrouter and membership states must be relearned after a TCN.
IGMP snooping reacts to TCNs in the following way:
1.
2.
Note
3.
IGMP snooping default behavior is that the STP root bridge always issues a global leave in response to a TCN, and the non-root bridges do not issue global leaves.
With the tcn query solicit command, you can enable a bridge to always issue a global leave in response to TCNs, even when it is not the root bridge. In that case, the root bridge and the non-root bridge would issue the global leave and both would solicit general queries in response to a TCN. Use the no form of the command to turn off soliciting when the bridge is not the root.
The root bridge always issues a global leave in response to a TCN. This behavior can not be disabled.
The internal querier has its own set of configuration options that control its reactions to TCNs.
The scope for this configuration option is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to ensure that a bridge will always issue a global leave in response to a TCN, even when it is not the STP root bridge:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# tcn query solicitRelated Commands
ttl-check disable
To disable the IGMP snooping check on the time-to-live (TTL) field in the IGMP header, use the ttl-check disable command in IGMP snooping profile configuration mode. To enable this functionality after a disable, use the no form of this command.
ttl-check disable
no ttl-check disable
Syntax Description
This command has no arguments or keywords.
Defaults
It is enabled by default.
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
By default, IGMP snooping examines the time-to-live (TTL) field in the IGMP header and processes packets as follows:
•
•
When the IGMP snooping TTL check feature is disabled, IGMP snooping processes all packets without examining the TTL field in the IGMP header.
The scope for this configuration option is per bridge domain. If the command appears in profiles attached to ports, it has no effect.
Task ID
Examples
The following example shows how to turn off the check on the ttl field:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# ttl-check disable5Related Commands
unsolicited-report-interval
To set the length of time that IGMP snooping has to send state change reports for IGMPv3 queriers when proxy reporting is enabled, use the unsolicited-report-interval command in IGMP snooping profile configuration mode. To return to the default value, use the no form of this command.
unsolicited-report-interval timer-value
no unsolicited-report-interval
Syntax Description
timer-value
Specifies the length of time that IGMP snooping can take to send state change reports for IGMPv3 queriers.
Valid values are integers from 100 to 5000 (milliseconds).
Defaults
1000 (milliseconds)
Command Modes
IGMP snooping profile configuration
Command History
Release 3.7.2
This command was introduced on Cisco ASR 9000 Series Routers.
Release 3.9.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
If a bridge domain querier is running IGMPv3 and proxy reporting is enabled, IGMP snooping acts as a proxy, generating reports from the proxy reporting address. As insurance against lost reports, IGMP snooping generates and forwards state change reports robustness-variable times, where the robustness-variable is the QRV value in the querier's general query. IGMP snooping forwards the reports at random intervals within the timeframe configured with the unsolicited-report-timer command.
Proxy reporting is enabled by default. To disable proxy reporting, use the report-suppression disable command.
Task ID
Examples
The following example shows how to configure the unsolicited report interval:
RP/0/RSP0/CPU0:router(config-igmp-snooping-profile)# unsolicited-report-interval 2000Related Commands
Disables IGMPv2 report suppression and IGMPv3 proxy reporting.
Configures the proxy reporting address.
