Igmp Relay; Configuration Guidelines - Lenovo ThinkSystem NE2552E Application Manual

IGMP Relay

Configuration Guidelines

362
NE2552E Application Guide for ENOS 8.4
The NE2552E can act as an IGMP Relay (or IGMP Proxy) device that relays IGMP
multicast messages and traffic between an Mrouter and end stations. IGMP Relay
allows the NE2552E to participate in network multicasts with no configuration of
the various multicast routing protocols, so you can deploy it in the network with
minimal effort.
To an IGMP host connected to the NE2552E, IGMP Relay appears to be an IGMP
multicast router (Mrouter). IGMP Relay sends Membership Queries to hosts,
which respond by sending an IGMP response message. A host can also send an
unsolicited Join message to the IGMP Relay.
To a multicast router, IGMP Relay appears as a host. The Mrouter sends IGMP host
queries to IGMP Relay, and IGMP Relay responds by forwarding IGMP host
reports and unsolicited join messages from its attached hosts.
IGMP Relay also forwards multicast traffic between the Mrouter and end stations,
similar to IGMP Snooping.
You can configure up to two Mrouters to use with IGMP Relay. One Mrouter acts
as the primary Mrouter, and one is the backup Mrouter. The NE2552E uses ICMP
health checks to determine if the primary and backup mrouters are reachable.
Consider the following guidelines when you configure IGMP Relay:
IGMP Relay is supported in stand‐alone (non‐stacking) mode only.

 IGMP Relay and IGMP Snooping/Querier are mutually exclusive—if you enable
IGMP Relay, you must turn off IGMP Snooping/Querier.
 Add VLANs to the IGMP Relay list, using the following command:
NE2552E(config)# ip igmp relay vlan <VLAN ID>
 If IGMP hosts reside on different VLANs, you must:
Disable IGMP flooding.

NE2552E(config)# vlan <VLAN ID>
NE2552E(config-vlan)# no flood
Enable CPU forwarding to ensure that multicast data is forwarded across the

VLANs.
NE2552E(config)# vlan <VLAN ID>
NE2552E(config-vlan)# cpu