Configuring IGMP Snooping and MVR: IP Command Reference, Volume 3 of 3:multicast, Release 12.2
Configuring IGMP Snooping and MVR: IP Command Reference, Volume 3 of 3:multicast, Release 12.2
24
Note
For IP Version 6 (IPv6) traffic, Multicast Listener Discovery (MLD) snooping performs the same
function as IGMP snooping for IPv4 traffic. For information about MLD snooping, see Chapter 37,
Configuring IPv6 MLD Snooping.
Note
For complete syntax and usage information for the commands used in this chapter, see the switch
command reference for this release and the IP Multicast Routing Commands section in the Cisco IOS
IP Command Reference, Volume 3 of 3:Multicast, Release 12.2.
This chapter consists of these sections:
Note
You can either manage IP multicast group addresses through features such as IGMP snooping and MVR,
or you can use static IP addresses.
24-1
Chapter 24
Note
For more information on IP multicast and IGMP, see RFC 1112 and RFC 2236.
The multicast router (which could be a Catalyst 3750 switch with the IP services image (formerly known
as the enhanced multilayer image [EMI] on the stack master) sends out periodic general queries to all
VLANs. All hosts interested in this multicast traffic send join requests and are added to the forwarding
table entry. The switch creates one entry per VLAN in the IGMP snooping IP multicast forwarding table
for each group from which it receives an IGMP join request.
The switch supports IP multicast group-based bridging, rather than MAC-addressed based groups. With
multicast MAC address-based groups, if an IP address being configured translates (aliases) to a
previously configured MAC address or to any reserved multicast MAC addresses (in the range
224.0.0.xxx), the command fails. Because the switch uses IP multicast groups, there are no address
aliasing issues.
The IP multicast groups learned through IGMP snooping are dynamic. However, you can statically
configure multicast groups by using the ip igmp snooping vlan vlan-id static ip_address interface
interface-id global configuration command. If you specify group membership for a multicast group
address statically, your setting supersedes any automatic manipulation by IGMP snooping. Multicast
group membership lists can consist of both user-defined and IGMP snooping-learned settings.
You can configure an IGMP snooping querier to support IGMP snooping in subnets without multicast
interfaces because the multicast traffic does not need to be routed. For more information about the IGMP
snooping querier, see the Configuring the IGMP Snooping Querier section on page 24-15.
If a port spanning-tree, a port group, or a VLAN ID change occurs, the IGMP snooping-learned multicast
groups from this port on the VLAN are deleted.
These sections describe IGMP snooping characteristics:
24-2
OL-8550-01
Chapter 24
IGMP Versions
The switch supports IGMP Version 1, IGMP Version 2, and IGMP Version 3. These versions are
interoperable on the switch. For example, if IGMP snooping is enabled on an IGMPv2 switch and the
switch receives an IGMPv3 report from a host, the switch can forward the IGMPv3 report to the
multicast router.
Note
The switch supports IGMPv3 snooping based only on the destination multicast MAC address. It does not
support snooping based on the source MAC address or on proxy reports.
An IGMPv3 switch supports Basic IGMPv3 Snooping Support (BISS), which includes support for the
snooping features on IGMPv1 and IGMPv2 switches and for IGMPv3 membership report messages.
BISS constrains the flooding of multicast traffic when your network includes IGMPv3 hosts. It
constrains traffic to approximately the same set of ports as the IGMP snooping feature on IGMPv2 or
IGMPv1 hosts.
Note
IGMPv3 join and leave messages are not supported on switches running IGMP filtering or MVR.
An IGMPv3 switch can receive messages from and forward messages to a device running the Source
Specific Multicast (SSM) feature. For more information about source-specific multicast with IGMPv3
and IGMP, see the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtssm5t.htm
24-3
Chapter 24
Figure 24-1
Router A
1
IGMP report 224.1.2.3
VLAN
PFC
CPU
45750
Forwarding
table
2
Host 1
Host 2
Host 3
Host 4
Router A sends a general query to the switch, which forwards the query to ports 2 through 5, which are
all members of the same VLAN. Host 1 wants to join multicast group 224.1.2.3 and multicasts an IGMP
membership report (IGMP join message) to the group. The switch CPU uses the information in the IGMP
report to set up a forwarding-table entry, as shown in Table 24-1, that includes the port numbers
connected to Host 1 and the router.
Table 24-1
Destination Address
Type of Packet
Ports
224.1.2.3
IGMP
1, 2
The switch hardware can distinguish IGMP information packets from other packets for the multicast
group. The information in the table tells the switching engine to send frames addressed to the 224.1.2.3
multicast IP address that are not IGMP packets to the router and to the host that has joined the group.
24-4
OL-8550-01
Chapter 24
If another host (for example, Host 4) sends an unsolicited IGMP join message for the same group
(Figure 24-2), the CPU receives that message and adds the port number of Host 4 to the forwarding table
as shown in Table 24-2. Note that because the forwarding table directs IGMP messages only to the CPU,
the message is not flooded to other ports on the switch. Any known multicast traffic is forwarded to the
group and not to the CPU.
Figure 24-2
Router A
1
VLAN
PFC
CPU
45751
Forwarding
table
2
Host 1
Table 24-2
Host 2
Host 3
Host 4
Destination Address
Type of Packet
Ports
224.1.2.3
IGMP
1, 2, 5
24-5
Chapter 24
Immediate Leave
Immediate Leave is only supported on IGMP Version 2 hosts.
The switch uses IGMP snooping Immediate Leave to remove from the forwarding table an interface that
sends a leave message without the switch sending group-specific queries to the interface. The VLAN
interface is pruned from the multicast tree for the multicast group specified in the original leave message.
Immediate Leave ensures optimal bandwidth management for all hosts on a switched network, even
when multiple multicast groups are simultaneously in use.
Note
You should only use the Immediate Leave feature on VLANs where a single host is connected to each
port. If Immediate Leave is enabled in VLANs where more than one host is connected to a port, some
hosts might inadvertently be dropped.
For configuration steps, see the Enabling IGMP Immediate Leave section on page 24-11.
IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports.
This feature is not supported when the query includes IGMPv3 reports.
The switch uses IGMP report suppression to forward only one IGMP report per multicast router query
to multicast devices. When IGMP router suppression is enabled (the default), the switch sends the first
IGMP report from all hosts for a group to all the multicast routers. The switch does not send the
remaining IGMP reports for the group to the multicast routers. This feature prevents duplicate reports
from being sent to the multicast devices.
If the multicast router query includes requests only for IGMPv1 and IGMPv2 reports, the switch
forwards only the first IGMPv1 or IGMPv2 report from all hosts for a group to all the multicast routers.
If the multicast router query also includes requests for IGMPv3 reports, the switch forwards all IGMPv1,
IGMPv2, and IGMPv3 reports for a group to the multicast devices.
If you disable IGMP report suppression, all IGMP reports are forwarded to the multicast routers. For
configuration steps, see the Disabling IGMP Report Suppression section on page 24-16.
24-6
OL-8550-01
Chapter 24
Feature
Default Setting
IGMP snooping
Multicast routers
None configured
PIM-DVMRP
Disabled
Static groups
None configured
Disabled
24-7
Chapter 24
Table 24-3
Feature
Default Setting
Disabled
Enabled
Purpose
Step 1
configure terminal
Step 2
ip igmp snooping
Step 3
end
Step 4
To globally disable IGMP snooping on all VLAN interfaces, use the no ip igmp snooping global
configuration command.
Beginning in privileged EXEC mode, follow these steps to enable IGMP snooping on a VLAN interface:
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
Step 4
To disable IGMP snooping on a VLAN interface, use the no ip igmp snooping vlan vlan-id global
configuration command for the specified VLAN number.
24-8
OL-8550-01
Chapter 24
Snooping on IGMP queries, Protocol Independent Multicast (PIM) packets, and Distance Vector
Multicast Routing Protocol (DVMRP) packets
Listening to Cisco Group Management Protocol (CGMP) packets from other routers
Statically connecting to a multicast router port with the ip igmp snooping mrouter global
configuration command
You can configure the switch either to snoop on IGMP queries and PIM/DVMRP packets or to listen to
CGMP self-join or proxy-join packets. By default, the switch snoops on PIM/DVMRP packets on all
VLANs. To learn of multicast router ports through only CGMP packets, use the ip igmp snooping vlan
vlan-id mrouter learn cgmp global configuration command. When this command is entered, the router
listens to only CGMP self-join and CGMP proxy-join packets and to no other CGMP packets. To learn
of multicast router ports through only PIM-DVMRP packets, use the ip igmp snooping vlan vlan-id
mrouter learn pim-dvmrp global configuration command.
Note
If you want to use CGMP as the learning method and no multicast routers in the VLAN are CGMP
proxy-enabled, you must enter the ip cgmp router-only command to dynamically access the router. For
more information, see Chapter 40, Configuring IP Multicast Routing.
Beginning in privileged EXEC mode, follow these steps to alter the method in which a VLAN interface
dynamically accesses a multicast router:
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
Step 4
Step 5
To return to the default learning method, use the no ip igmp snooping vlan vlan-id mrouter learn cgmp
global configuration command.
24-9
Chapter 24
This example shows how to configure IGMP snooping to use CGMP packets as the learning method:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 1 mrouter learn cgmp
Switch(config)# end
Note
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
Step 4
show ip igmp snooping mrouter [vlan vlan-id] Verify that IGMP snooping is enabled on the VLAN interface.
Step 5
To remove a multicast router port from the VLAN, use the no ip igmp snooping vlan vlan-id mrouter
interface interface-id global configuration command.
This example shows how to enable a static connection to a multicast router:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 200 mrouter interface gigabitethernet1/0/2
Switch(config)# end
24-10
OL-8550-01
Chapter 24
Purpose
Step 1
configure terminal
Step 2
ip igmp snooping vlan vlan-id static ip_address Statically configure a Layer 2 port as a member of a multicast
interface interface-id
group:
Step 3
end
Step 4
Step 5
To remove the Layer 2 port from the multicast group, use the no ip igmp snooping vlan vlan-id static
mac-address interface interface-id global configuration command.
This example shows how to statically configure a host on a port:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 105 static 224.2.4.12 interface gigabitethernet1/0/1
Switch(config)# end
Note
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
24-11
Chapter 24
Command
Purpose
Step 4
Step 5
To disable IGMP Immediate Leave on a VLAN, use the no ip igmp snooping vlan vlan-id
immediate-leave global configuration command.
This example shows how to enable IGMP Immediate Leave on VLAN 130:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 130 immediate-leave
Switch(config)# end
The IGMP configurable leave time is only supported on hosts running IGMP Version 2.
The actual leave latency in the network is usually the configured leave time. However, the leave time
might vary around the configured time, depending on real-time CPU load conditions, network delays
and the amount of traffic sent through the interface.
Beginning in privileged EXEC mode, follow these steps to enable the IGMP configurable-leave timer:
Command
Purpose
Step 1
configure terminal
Step 2
ip igmp snooping
last-member-query-interval time
Configure the IGMP leave timer globally. The range is 100 to 5000
milliseconds. The default is 1000 seconds.
Step 3
(Optional) Configure the IGMP leave time on the VLAN interface. The
range is 100 to 5000 milliseconds.
Note
Step 4
end
Step 5
Step 6
To globally reset the IGMP leave timer to the default setting, use the no ip igmp snooping
last-member-query-interval global configuration command.
To remove the configured IGMP leave-time setting from the specified VLAN, use the no ip igmp
snooping vlan vlan-id last-member-query-interval global configuration command.
24-12
OL-8550-01
Chapter 24
Controlling the Multicast Flooding Time After a TCN Event, page 24-13
Purpose
Step 1
configure terminal
Step 2
Specify the number of IGMP general queries for which the multicast
traffic is flooded. The range is 1 to 10. By default, the flooding query
count is 2.
Step 3
end
Step 4
Step 5
To return to the default flooding query count, use the no ip igmp snooping tcn flood query count global
configuration command.
24-13
Chapter 24
Beginning in privileged EXEC mode, follow these steps to enable the switch to send the global leave
message whether or not it is the spanning-tree root:
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
Step 4
Step 5
To return to the default query solicitation, use the no ip igmp snooping tcn query solicit global
configuration command.
Purpose
Step 1
configure terminal
Step 2
interface interface-id
Step 3
Step 4
exit
Step 5
Step 6
To re-enable multicast flooding on an interface, use the ip igmp snooping tcn flood interface
configuration command.
24-14
OL-8550-01
Chapter 24
Configure an IP address on the VLAN interface. When enabled, the IGMP snooping querier uses the
IP address as the query source address.
If there is no IP address configured on the VLAN interface, the IGMP snooping querier tries to use
the configured global IP address for the IGMP querier. If there is no global IP address specified, the
IGMP querier tries to use the VLAN switch virtual interface (SVI) IP address (if one exists). If there
is no SVI IP address, the switch uses the first available IP address configured on the switch. The first
IP address available appears in the output of the show ip interface privileged EXEC command. The
IGMP snooping querier does not generate an IGMP general query if it cannot find an available IP
address on the switch.
When administratively enabled, the IGMP snooping querier moves to the nonquerier state if it
detects the presence of a multicast router in the network.
When it is administratively enabled, the IGMP snooping querier moves to the operationally disabled
state under these conditions:
IGMP snooping is disabled in the VLAN.
PIM is enabled on the SVI of the corresponding VLAN.
Beginning in privileged EXEC mode, follow these steps to enable the IGMP snooping querier feature in
a VLAN:
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
Step 4
Step 5
ip igmp snooping querier tcn query [count (Optional) Set the time between Topology Change Notification
count | interval interval]
(TCN) queries. The count range is 1 to 10. The interval range is 1 to
255 seconds.
Step 6
(Optional) Set the length of time until the IGMP querier expires.The
range is 60 to 300 seconds.
Step 7
(Optional) Select the IGMP version number that the querier feature
uses. Select 1 or 2.
Step 8
end
Step 9
Step 10
24-15
Chapter 24
This example shows how to set the IGMP snooping querier source address to 10.0.0.64:
Switch# configure terminal
Switch(config)# ip igmp snooping querier 10.0.0.64
Switch(config)# end
This example shows how to set the IGMP snooping querier maximum response time to 25 seconds:
Switch# configure terminal
Switch(config)# ip igmp snooping querier query-interval 25
Switch(config)# end
This example shows how to set the IGMP snooping querier timeout to 60 seconds:
Switch# configure terminal
Switch(config)# ip igmp snooping querier timeout expiry 60
Switch(config)# end
This example shows how to set the IGMP snooping querier feature to version 2:
Switch# configure terminal
Switch(config)# no ip igmp snooping querier version 2
Switch(config)# end
IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports.
This feature is not supported when the query includes IGMPv3 reports.
IGMP report suppression is enabled by default. When it is enabled, the switch forwards only one IGMP
report per multicast router query. When report suppression is disabled, all IGMP reports are forwarded
to the multicast routers.
Beginning in privileged EXEC mode, follow these steps to disable IGMP report suppression:
Command
Purpose
Step 1
configure terminal
Step 2
Step 3
end
Step 4
Step 5
To re-enable IGMP report suppression, use the ip igmp snooping report-suppression global
configuration command.
24-16
OL-8550-01
Chapter 24
To display IGMP snooping information, use one or more of the privileged EXEC commands in
Table 24-4.
Table 24-4
Command
Purpose
Display information about the IP address and receiving port for the
most-recently received IGMP query messages in the VLAN.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
For more information about the keywords and options in these commands, see the command reference
for this release.
24-17
Chapter 24
In compatible mode, multicast data received by MVR hosts is forwarded to all MVR data ports,
regardless of MVR host membership on those ports. The multicast data is forwarded only to those
receiver ports that MVR hosts have joined, either by IGMP reports or by MVR static configuration.
IGMP reports received from MVR hosts are never forwarded from MVR data ports that were
configured in the switch.
In dynamic mode, multicast data received by MVR hosts on the switch is forwarded from only those
MVR data and client ports that the MVR hosts have joined, either by IGMP reports or by MVR static
configuration. Any IGMP reports received from MVR hosts are also forwarded from all the MVR
data ports in the switch. This eliminates using unnecessary bandwidth on MVR data port links,
which occurs when the switch runs in compatible mode.
Only Layer 2 ports take part in MVR. You must configure ports as MVR receiver ports. Only one MVR
multicast VLAN per switch stack is supported.
Receiver ports and source ports can be on different switches in a switch stack. Multicast data sent on the
multicast VLAN is forwarded to all MVR receiver ports across the stack. When a new switch is added
to a stack, by default it has no receiver ports.
If a switch fails or is removed from the stack, only those receiver ports belonging to that switch will not
receive the multicast data. All other receiver ports on other switches continue to receive the multicast
data.
24-18
OL-8550-01
Chapter 24
Multicast VLAN
Cisco router
Multicast
server
SP
Switch B
SP
SP
SP
SP
SP
SP2
SP1
Multicast
data
Multicast
data
Switch A
RP1 RP2 RP3 RP4 RP5 RP6 RP7
Customer
premises
Hub
IGMP join
Set-top box
Set-top box
TV
data
TV
RP = Receiver Port
SP = Source Port
101364
PC
TV
Note: All source ports belong to
the multicast VLAN.
24-19
Chapter 24
Configuring MVR
When a subscriber changes channels or turns off the television, the set-top box sends an IGMP leave
message for the multicast stream. The switch CPU sends a MAC-based general query through the
receiver port VLAN. If there is another set-top box in the VLAN still subscribing to this group, that
set-top box must respond within the maximum response time specified in the query. If the CPU does not
receive a response, it eliminates the receiver port as a forwarding destination for this group.
Without Immediate Leave, when the switch receives an IGMP leave message from a subscriber on a
receiver port, it sends out an IGMP query on that port and waits for IGMP group membership reports. If
no reports are received in a configured time period, the receiver port is removed from multicast group
membership. With Immediate Leave, an IGMP query is not sent from the receiver port on which the
IGMP leave was received. As soon as the leave message is received, the receiver port is removed from
multicast group membership, which speeds up leave latency. Enable the Immediate-Leave feature only
on receiver ports to which a single receiver device is connected.
MVR eliminates the need to duplicate television-channel multicast traffic for subscribers in each VLAN.
Multicast traffic for all channels is only sent around the VLAN trunk onceonly on the multicast
VLAN. The IGMP leave and join messages are in the VLAN to which the subscriber port is assigned.
These messages dynamically register for streams of multicast traffic in the multicast VLAN on the
Layer 3 device. Switch B. The access layer switch, Switch A, modifies the forwarding behavior to allow
the traffic to be forwarded from the multicast VLAN to the subscriber port in a different VLAN,
selectively allowing traffic to cross between two VLANs.
IGMP reports are sent to the same IP multicast group address as the multicast data. The Switch A CPU
must capture all IGMP join and leave messages from receiver ports and forward them to the multicast
VLAN of the source (uplink) port, based on the MVR mode.
Configuring MVR
These sections contain this configuration information:
Feature
Default Setting
MVR
Multicast addresses
None configured
0.5 second
Multicast VLAN
VLAN 1
Mode
Compatible
24-20
OL-8550-01
Chapter 24
Table 24-5
Feature
Default Setting
Immediate Leave
Receiver ports can only be access ports; they cannot be trunk ports. Receiver ports on a switch can
be in different VLANs, but should not belong to the multicast VLAN.
The maximum number of multicast entries (MVR group addresses) that can be configured on a
switch (that is, the maximum number of television channels that can be received) is 256.
MVR multicast data received in the source VLAN and leaving from receiver ports has its
time-to-live (TTL) decremented by 1 in the switch.
Because MVR on the switch uses IP multicast addresses instead of MAC multicast addresses,
aliased IP multicast addresses are allowed on the switch. However, if the switch is interoperating
with Catalyst 3550 or Catalyst 3500 XL switches, you should not configure IP addresses that alias
between themselves or with the reserved IP multicast addresses (in the range 224.0.0.xxx).
MVR is not supported when multicast routing is enabled on a switch. If you enable multicast routing
and a multicast routing protocol while MVR is enabled, MVR is disabled, and you receive a warning
message. If you try to enable MVR while multicast routing and a multicast routing protocol are
enabled, the operation to enable MVR is cancelled, and you receive an error message.
MVR data received on an MVR receiver port is not forwarded to MVR source ports.
Note
For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
Beginning in privileged EXEC mode, follow these steps to configure MVR parameters:
Command
Purpose
Step 1
configure terminal
Step 2
mvr
24-21
Chapter 24
Configuring MVR
Command
Purpose
Step 3
Step 4
(Optional) Define the maximum time to wait for IGMP report memberships
on a receiver port before removing the port from multicast group membership.
The value is in units of tenths of a second. The range is 1 to 100, and the
default is 5 tenths or one-half second.
Step 5
(Optional) Specify the VLAN in which multicast data is received; all source
ports must belong to this VLAN. The VLAN range is 1 to 1001 and 1006 to
4094. The default is VLAN 1.
Step 6
mvr mode {dynamic | compatible} (Optional) Specify the MVR mode of operation:
end
Step 8
Step 9
copy running-config
startup-config
To return the switch to its default settings, use the no mvr [mode | group ip-address | querytime | vlan]
global configuration commands.
This example shows how to enable MVR, configure the group address, set the query time to 1 second
(10 tenths), specify the MVR multicast VLAN as VLAN 22, and set the MVR mode as dynamic:
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
mvr
mvr
mvr
mvr
mvr
end
group 228.1.23.4
querytime 10
vlan 22
mode dynamic
You can use the show mvr members privileged EXEC command to verify the MVR multicast group
addresses on the switch.
Purpose
Step 1
configure terminal
Step 2
mvr
24-22
OL-8550-01
Chapter 24
Command
Purpose
Step 3
interface interface-id
Step 4
mvr vlan vlan-id group [ip-address] (Optional) Statically configure a port to receive multicast traffic sent to the
multicast VLAN and the IP multicast address. A port statically configured as
a member of a group remains a member of the group until statically removed.
Note
Receiver ports can also dynamically join multicast groups by using IGMP
join and leave messages.
Step 6
mvr immediate
Step 7
end
Step 8
show mvr
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the interface to its default settings, use the no mvr [type | immediate | vlan vlan-id | group]
interface configuration commands.
This example shows how to configure a port as a receiver port, statically configure the port to receive
multicast traffic sent to the multicast group address, configure Immediate Leave on the port, and verify
the results.
Switch(config)# mvr
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr type receiver
Switch(config-if)# mvr vlan 22 group 228.1.23.4
Switch(config-if)# mvr immediate
Switch(config)# end
Switch# show mvr interface
Port
Type
Status
Immediate Leave
--------------------------Gi1/0/2 RECEIVER
ACTIVE/DOWN
ENABLED
24-23
Chapter 24
Command
Purpose
show mvr
Displays MVR status and values for the switchwhether MVR is enabled or disabled,
the multicast VLAN, the maximum (256) and current (0 through 256) number of
multicast groups, the query response time, and the MVR mode.
show mvr interface [interface-id] Displays all MVR interfaces and their MVR configurations.
[members [vlan vlan-id]]
When a specific interface is entered, displays this information:
TypeReceiver or Source
StatusOne of these:
Active means the port is part of a VLAN.
Up/Down means that the port is forwarding or nonforwarding.
Inactive means that the port is not part of any VLAN.
If the members keyword is entered, displays all multicast group members on this port or,
if a VLAN identification is entered, all multicast group members on the VLAN. The
VLAN ID range is 1 to 1001 and 1006 to 4094.
show mvr members [ip-address]
Displays all receiver and source ports that are members of any IP multicast group or the
specified IP multicast group IP address.
24-24
OL-8550-01
Chapter 24
IGMP filtering is applicable only to the dynamic learning of IP multicast group addresses, not static
configuration.
With the IGMP throttling feature, you can set the maximum number of IGMP groups that a Layer 2
interface can join. If the maximum number of IGMP groups is set, the IGMP snooping forwarding table
contains the maximum number of entries, and the interface receives an IGMP join report, you can
configure an interface to drop the IGMP report or to replace the randomly selected multicast entry with
the received IGMP report.
Note
IGMPv3 join and leave messages are not supported on switches running IGMP filtering.
These sections contain this configuration information:
Feature
Default Setting
IGMP filters
None applied
No maximum set
IGMP profiles
None defined
When the maximum number of groups is in forwarding table, the default IGMP throttling action is to
deny the IGMP report. For configuration guidelines, see the Configuring the IGMP Throttling Action
section on page 24-28.
deny: Specifies that matching addresses are denied; this is the default.
24-25
Chapter 24
range: Specifies a range of IP addresses for the profile. You can enter a single IP address or a range
with a start and an end address.
The default is for the switch to have no IGMP profiles configured. When a profile is configured, if
neither the permit nor deny keyword is included, the default is to deny access to the range of IP
addresses.
Beginning in privileged EXEC mode, follow these steps to create an IGMP profile:
Command
Purpose
Step 1
configure terminal
Step 2
Assign a number to the profile you are configuring, and enter IGMP
profile configuration mode. The profile umber range is 1 to 4294967295.
Step 3
permit | deny
Step 4
Step 5
end
Step 6
Step 7
To delete a profile, use the no ip igmp profile profile number global configuration command.
To delete an IP multicast address or range of IP multicast addresses, use the no range ip multicast
address IGMP profile configuration command.
This example shows how to create IGMP profile 4 allowing access to the single IP multicast address and
how to verify the configuration. If the action was to deny (the default), it would not appear in the show
ip igmp profile output display.
Switch(config)# ip igmp profile 4
Switch(config-igmp-profile)# permit
Switch(config-igmp-profile)# range 229.9.9.0
Switch(config-igmp-profile)# end
Switch# show ip igmp profile 4
IGMP Profile 4
permit
range 229.9.9.0 229.9.9.0
24-26
OL-8550-01
Chapter 24
Beginning in privileged EXEC mode, follow these steps to apply an IGMP profile to a switch port:
Command
Purpose
Step 1
configure terminal
Step 2
interface interface-id
Step 3
Step 4
end
Step 5
Step 6
To remove a profile from an interface, use the no ip igmp filter profile number interface configuration
command.
This example shows how to apply IGMP profile 4 to a port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip igmp filter 4
Switch(config-if)# end
Purpose
Step 1
configure terminal
Step 2
interface interface-id
Step 3
Set the maximum number of IGMP groups that the interface can join.
The range is 0 to 4294967294. The default is to have no maximum set.
Step 4
end
Step 5
Step 6
24-27
Chapter 24
To remove the maximum group limitation and return to the default of no maximum, use the no ip igmp
max-groups interface configuration command.
This example shows how to limit to 25 the number of IGMP groups that a port can join.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip igmp max-groups 25
Switch(config-if)# end
This restriction can be applied only to Layer 2 ports. You can use this command on a logical
EtherChannel interface but cannot use it on ports that belong to an EtherChannel port group.
When the maximum group limitation is set to the default (no maximum), entering the ip igmp
max-groups action {deny | replace} command has no effect.
If you configure the throttling action and set the maximum group limitation after an interface has
added multicast entries to the forwarding table, the forwarding-table entries are either aged out or
removed, depending on the throttling action.
If you configure the throttling action as deny, the entries that were previously in the forwarding
table are not removed but are aged out. After these entries are aged out and the maximum
number of entries is in the forwarding table, the switch drops the next IGMP report received on
the interface.
If you configure the throttling action as replace, the entries that were previously in the
forwarding table are removed. When the maximum number of entries is in the forwarding table,
the switch replaces a randomly selected entry with the received IGMP report.
To prevent the switch from removing the forwarding-table entries, you can configure the IGMP
throttling action before an interface adds entries to the forwarding table.
Beginning in privileged EXEC mode, follow these steps to configure the throttling action when the
maximum number of entries is in the forwarding table:
Command
Purpose
Step 1
configure terminal
Step 2
interface interface-id
Step 3
replaceReplace the existing group with the new group for which
the IGMP report was received.
24-28
OL-8550-01
Chapter 24
Command
Purpose
Step 4
end
Step 5
Step 6
To return to the default action of dropping the report, use the no ip igmp max-groups action interface
configuration command.
Command
Purpose
Displays the specified IGMP profile or all the IGMP profiles defined on the switch.
Displays the configuration of the specified interface or the configuration of all interfaces
on the switch, including (if configured) the maximum number of IGMP groups to which
an interface can belong and the IGMP profile applied to the interface.
24-29
Chapter 24
24-30
OL-8550-01