The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS IGMP commands that begin with I.
To enable a route-map policy to control the multicast groups that hosts on the subnet serviced by an interface can join, use the ip igmp access-group command. To disable the route-map policy, use the no form of this command.
ip igmp access-group policy-name
no ip igmp access-group [ policy-name ]
Route-map policy name. The route map name can be a maximum of 100 alphanumeric characters. |
|
|
The ip igmp access-group command is an alias of the ip igmp report-policy command.
This example shows how to enable a route-map policy:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp access-group my_access_group_policy
switch(
config-if)#
This example shows how to disable a route-map policy:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp access-group
switch(
config-if)#
|
|
---|---|
To enable the enforce router alert option check for IGMPv2 and IGMPv3 packets, use the ip igmp enforce-router-alert command. To disable the option check, use the no form of this command.
no ip igmp enforce-router-alert
|
|
This example shows how to enable the enforce router alert option check:
switch(
config)#
ip igmp enforce-router-alert
This example shows how to disable the enforce router alert option check:
switch(
config)#
no ip igmp enforce-router-alert
|
|
---|---|
Displays information about the IGMP running-system configuration. |
To configure the size of the IGMP event history buffers, use the ip igmp event-history command. To revert to the default buffer size, use the no form of this command.
ip igmp event-history { cli | errors | group-debugs | group-events | ha | igmp-internal | interface-debugs | interface-events | msgs | mtrace | policy | statistics | vrf } size buffer-size
no ip igmp event-history { clis | errors | group-debugs | group-events | ha | igmp-internal | interface-debugs | interface-events | msgs | mtrace | policy | statistics | vrf } size buffer-size
network-admin
network-operator
vdc-admin
vdc-operator
|
|
This example shows how to configure the IGMP HA event history buffer size:
switch(config)#
ip igmp event-history ha size large
|
|
---|---|
Displays information about the IGMP running-system configuration. |
To remove routes when the IGMP process is restarted, use the ip igmp flush-routes command. To leave routes in place, use the no form of this command.
|
|
To display whether flush routes are configured, use this command line:
switch(
config)#
show running-config | include flush-routes
This example shows how to remove routes when the IGMP process is restarted:
switch(
config)#
ip igmp flush-routes
This example shows how to leave routes in place when the IGMP process is restarted:
switch(
config)#
no ip igmp flush-routes
|
|
---|---|
Displays information about the running-system configuration. |
To configure a group membership timeout for IGMPv2, use the ip igmp group-timeout command. To return to the default timeout, use the no form of this command.
no ip igmp group-timeout [ timeout ]
Timeout in seconds. The range is from 3 to 65,535. The default is 260. |
|
|
This example shows how to configure a group membership timeout:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp group-timeout 200
switch(
config-if)#
This example shows how to reset a group membership timeout to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp group-timeout
switch(
config-if)#
|
|
---|---|
To enable the device to remove the group entry from the multicast routing table immediately upon receiving a leave message for the group, use the ip igmp immediate-leave command. To disable the immediate leave option, use the no form of this command.
|
|
Use the ip igmp immediate-leave command only when there is one receiver behind the interface for a given group.
This example shows how to enable the immediate leave feature:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp immediate-leave
This example shows how to disable the immediate leave feature:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp immediate-leave
|
|
---|---|
To statically bind a multicast group to an interface, use the ip igmp join-group command. To remove a group binding, use the no form of this command.
ip igmp join-group { group [ source source ] | route-map policy-name }
no ip igmp join-group { group [ source source ] | route-map policy-name }
|
|
If you specify only the group address, the (*, G) state is created. If you specify the source address, the (S, G) state is created.
If you use the route map, the only match command that is read from the route map is the match ip multicast command. You can specify the group prefix and source prefix.
Note A source tree is built for the (S, G) state only if you enable IGMPv3.
This example shows how to statically bind a group to an interface:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp join-group 230.0.0.0
switch(
config-if)#
This example shows how to remove a group binding from an interface:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp join-group 230.0.0.0
switch(
config-if)#
|
|
---|---|
To configure the number of times that the software sends an IGMP query in response to a host leave message, use the ip igmp last-member-query-count command. To reset the query interval to the default, use the no form of this command.
ip igmp last-member-query-count count
no ip igmp last-member-query-count [ count ]
|
|
This example shows how to configure a query count:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp last-member-query-count 3
switch(
config-if)#
This example shows how to reset a query count to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp last-member-query-count
switch(
config-if)#
|
|
---|---|
To configure a query interval in which the software sends membership reports and then deletes the group state, use the ip igmp last-member-query-response-time command. To reset the query interval to the default, use the no form of this command.
ip igmp last-member-query-response-time interval
no ip igmp last-member-query-response-time [ interval ]
Query interval in seconds. The range is from 1 to 25. The default is 1. |
|
|
This example shows how to configure a query interval:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp last-member-query-response-time 3
switch(
config-if)#
This example shows how to reset a query interval to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp last-member-query-response-time
switch(
config-if)#
|
|
---|---|
To configure a querier timeout that the software uses when deciding to take over as the querier, use the ip igmp querier-timeout command. To reset to the querier timeout to the default, use the no form of this command.
ip igmp querier-timeout timeout
no ip igmp querier-timeout [ timeout ]
Timeout in seconds. The range is from 1 to 65,535. The default is 255. |
|
|
The ip igmp query-timeout command is an alternative form of this command.
This example shows how to configure a querier timeout:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp querier-timeout 200
switch(
config-if)#
This example shows how to reset a querier timeout to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp querier-timeout
switch(
config-if)#
|
|
---|---|
To configure a query interval used when the IGMP process starts up, use the ip igmp query-interval command. To reset the query interval to the default, use the no form of this command.
ip igmp query-interval interval
no ip igmp query-interval [ interval ]
Interval in seconds. The range is from 1 to 18,000. The default is 125. |
|
|
This example shows how to configure a query interval:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp query-interval 100
switch(
config-if)#
This example shows how to reset a query interval to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp query-interval
switch(
config-if)#
|
|
---|---|
To configure a query maximum response time that is advertised in IGMP queries, use the ip igmp query-max-response-time command. To reset the response time to the default, use the no form of this command.
ip igmp query-max-response-time time
no ip igmp query-max-response-time [ time ]
Query maximum response time in seconds. The range is from 1 to 25. The default is 10. |
|
|
This example shows how to configure a query maximum response time:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp query-max-response-time 15
switch(
config-if)#
This example shows how to reset a query maximum response time to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp query-max-response-time
switch(
config-if)#
|
|
---|---|
To configure a query timeout that the software uses when deciding to take over as the querier, use the ip igmp query-timeout command. To reset to the querier timeout to the default, use the no form of this command.
no ip igmp query-timeout [ timeout ]
Timeout in seconds. The range is from 1 to 65,535. The default is 255. |
|
|
The ip igmp querier-timeout command is an alternative form of this command.
This example shows how to configure a querier timeout:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp query-timeout 200
switch(
config-if)#
This example shows how to reset a querier timeout to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp query-timeout
switch(
config-if)#
|
|
---|---|
To enable IGMP to send reports for link-local groups, use the ip igmp report-link-local-groups command. To disable sending reports to link-local groups, use the no form of this command.
ip igmp report-link-local-groups
no ip igmp report-link-local-groups
|
|
This example shows how to enable sending reports to link-local groups:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp report-link-local-groups
This example shows how to disable sending reports to link-local groups:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp report-link-local-groups
|
|
---|---|
To enable an access policy that is based on a route-map policy for IGMP reports, use the ip igmp report-policy command. To disable the route-map policy, use the no form of this command.
ip igmp report-policy policy-name
no ip igmp report-policy [ policy-name ]
Route-map policy name. The route name is a maximum of 100 alphanumeric characters. |
|
|
Use the ip igmp report-policy command to filter incoming messages. You can configure the route map to prevent state from being created in the multicast routing table.
The ip igmp report-policy command is an alias of the ip igmp access-group command.
If you use the route map, the only match command that is read from the route map is the match ip multicast command. You can specify the group prefix, group range, and source prefix to filter messages.
This example shows how to enable an access policy for IGMP reports:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp report-policy my_report_policy
switch(
config-if)#
This example shows how to disable an access policy for IGMP reports:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp report-policy
switch(
config-if)#
|
|
---|---|
To configure a robustness count that you can tune to reflect expected packet loss on a congested network, use the ip igmp robustness-variable command. To reset the count to the default, use the no form of this command.
ip igmp robustness-variable count
no ip igmp robustness-variable [ count ]
Robustness count. The range is from 1 to 7. The default is 2. |
|
|
This example shows how to configure a robustness count:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp robustness-variable 3
switch(
config-if)#
This example shows how to reset a robustness count to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp robustness-variable
switch(
config-if)#
|
|
---|---|
To translate IGMPv1 or IGMPv2 membership reports to create the (S, G) state so that the router treats them as IGMPv3 membership reports, use the ip igmp ssm-translate command. To remove the translation, use the no form of this command.
ip igmp ssm-translate group source
no ip igmp ssm-translate group source
IPv4 multicast group range. By default, the group prefix range is 232.0.0.0/8. To modify the IPv4 Protocol Independent Multicast (PIM) SSM range, see the ip pim ssm range command. |
|
Global configuration mode
VRF configuration mode
|
|
To display SSM translation commands, use this command line:
switch(
config)#
show running-config | include ssm-translation
This example shows how to configure a translation:
switch#
configure terminal
switch(
config)#
ip igmp ssm-translate 232.0.0.0/8 10.1.1.1
This example shows how to remove a translation:
switch(
config)#
no ip igmp ssm-translate 232.0.0.0/8 10.1.1.1
|
|
---|---|
Displays information about the running-system configuration. |
To configure the query count used when the IGMP process starts up, use the ip igmp startup-query-count command. To reset the query count to the default, use the no form of this command.
ip igmp startup-query-count count
no ip igmp startup-query-count [ count ]
|
|
This example shows how to configure a query count:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp startup-query-count 3
switch(
config-if)#
This example shows how to reset a query count to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp startup-query-count
switch(
config-if)#
|
|
---|---|
To configure the query interval used when the IGMP process starts up, use the ip igmp startup-query-interval command. To reset the query interval to the default, use the no form of this command.
ip igmp startup-query-interval interval
no ip igmp startup-query-interval [ interval ]
Query interval in seconds. The range is from 1 to 18,000. The default is 31. |
|
|
This example shows how to configure a startup query interval:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp startup-query-interval 25
switch(
config-if)#
This example shows how to reset a startup query interval to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp startup-query-interval
switch(
config-if)#
|
|
---|---|
To configure the maximum states allowed, use the ip igmp state-limit command. To remove the state limit, use the no form of this command.
ip igmp state-limit max-states [ reserved reserve-policy max-reserved ]
no ip igmp state-limit [ max-states [ reserved reserve-policy max-reserved ]]
|
|
This example shows how to configure a state limit:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp state-limit 5000
switch(
config-if)#
This example shows how to remove a state limit:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp state-limit
switch(
config-if)#
|
|
---|---|
To statically bind a multicast group to the outgoing interface (OIF), which is handled by the device hardware, use the ip igmp static-oif command. To remove a static group, use the no form of this command.
ip igmp static-oif { group [ source source ] | route-map policy-name }
no ip igmp static-oif { group [ source source ] | route-map policy-name }
|
|
Before you use this command, make sure that you enable Protocol Independent Multicast (PIM) on the interface by using the ip pim sparse-mode command.
This example shows how to statically bind a group to the OIF:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no switchport
switch(
config-if)#
ip igmp static-oif 230.0.0.0
switch(
config-if)#
This example shows how to remove a static binding from the OIF:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no switchport
switch(
config-if)#
no ip igmp static oif 230.0.0.0
switch(
config-if)#
|
|
---|---|
To configure the IGMP version to use on an interface, use the ip igmp version command. To reset the IGMP version to the default, use the no form of this command.
no ip igmp version [ version ]
|
|
This example shows how to configure the IGMP version to use on an interface:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
ip igmp version 3
switch(
config-if)#
This example shows how to reset the IGMP version to the default:
switch(
config)#
interface ethernet 2/2
switch(
config-if)#
no ip igmp version
switch(
config-if)#
|
|
---|---|
To restart the IGMP process, use the restart igmp command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Review comment from Vishnu (vthumati), this command is not supported. |
This example shows how to restart the process:
switch(
config)#
restart igmp
|
|
---|---|