H3C Technologies H3C S10500 Series Switches - Manual (Page 129)

114
CAUTION:
If IGMPv3 is enabled on a VLAN interface of a switch, and if a port in that VLAN is configured as a
simulated host, the simulated host will send IGMPv3 reports even if you did not specify a multicast source
when configuring simulated joining with the igmp-snooping host-join command. In this case, the
corresponding multicast group will not be created based on the configured IGMP SSM mappings. For
more information about the igmp-snooping host-join command, see IP Multicast Command Reference.
Configuring IGMP proxying
Configuration prerequisites
Before you configure the IGMP proxying feature, complete the following tasks:
• Configure any unicast routing protocol so that all devices in the domain are interoperable at the
network layer
• Enable IP multicast routing
Enabling IGMP proxying
You can enable IGMP proxying on the interface in the direction toward the root of the multicast
forwarding tree to make the switch serve as an IGMP proxy.
Follow these steps to enable IGMP proxying:
To do… Use the command… Remarks
Enter system view system-view —
Enter interface view interface interface-type interface-number —
Enable the IGMP proxying
feature
igmp proxying enable
Required
Disabled by default.
NOTE:
•
Each switch can have only one interface serving as the proxy interface. In scenarios with multiple
instances, IGMP proxying is configured on only one interface per instance.
• You cannot enable IGMP on an interface with IGMP proxying enabled. Moreover, only the igmp
require-router-alert, igmp send-router-alert, and igmp version commands can take effect on such an
interface.
• You cannot enable other multicast routing protocols (such as PIM-DM or PIM-SM) on an interface with
IGMP proxying enabled, or vice versa. However, the source-lifetime, source-policy, and ssm-policy
commands configured in PIM view can still take effect. In addition, in IGMPv1, the designated router
(DR) is elected by the working multicast routing protocol (such as PIM) to serve as the IGMP querier.
Therefore, a downstream interface running IGMPv1 cannot be elected as the DR and thus cannot serve
as the IGMP querier.
• You cannot enable IGMP proxying on a VLAN interface with IGMP snooping enabled, or vice versa.