Product and Software: This article applies to ArubaOS 3.4 and later.
Why is IGMP proxy useful?
IGMP proxy is useful in mobility environments where the client needs to subscribe to multicast streams from his home agent (HA) and foreign agents (FAs). Until version 3.3.2.x, ArubaOS supported only IGMP snooping, which is effective only as long as the client is in his home agent VLAN. Because of mobility, the client IP remains same even when it roams. The IGMP membership is not extended to his FA VLAN and so the client loses subscription to the multicast stream. IGMP proxy addresses this issue.
How does IGMP proxy work?
Whenever the client roams away from his HA to a FA, the HA communicates all current group memberships of the mobile client to the FA in the registration message.
The HA mobility process queries PIM for group membership and it receives a HA discovery message from the FA. After discovery, when the FA sends a registration request to the HA, the HA fills in all multicast groups in a registration reply.
FA mobility fetches group membership from the reply and pushes it to the local PIM process. The local PIM process performs a proxy join so that the mobility client can directly get downstream multicast traffic from the foreign network
The upstream router is not aware of the client memberships. The controller processes the IGMP control messages on behalf of the clients. It acts as host for all multicast groups that the client is interested in.
All mobility controllers must be connected to the upstream router. This way the multicast streams are flooded directly to the client in FA from the upstream router instead of going through IP-IP tunnel.
At maximum mobility, IGMP proxy supports eight multicast groups per host and a total of 256 multicast groups per controller.
Note: IGMP snooping and IGMP proxy cannot be enabled on an interface at the same time.
Configuration requires that you enable IGMP proxy on the VLAN interface with the controller uplink interface.
interface vlan 30
ip igmp proxy gigabitethernet 1/0
To check the IGMP proxy state for a VLAN, issue this command:
(ARUBA) #show ip igmp interface
IGMP Interface Table
VLAN Addr Netmask MAC Address IGMP Snooping Querier Destination IGMP Proxy
---- ---- ------- ----------- ---- -------- ------- ----------- ----------
16 184.108.40.206 255.255.255.0 00:0b:86:61:21:50 disabled disabled 220.127.116.11 CP disabled
400 18.104.22.168 255.255.255.0 00:0b:86:61:21:50 disabled disabled 22.214.171.124 CP enabled
211 172.24.211.1 255.255.255.0 00:0b:86:61:21:50 disabled disabled 172.24.211.1 CP disabled
140 172.25.140.1 255.255.255.0 00:0b:86:61:21:50 disabled disabled 172.25.140.1 CP disabled
300 126.96.36.199 255.255.255.0 00:0b:86:61:21:50 disabled disabled 188.8.131.52 CP enabled
To check the group information the controller has issued for a VLAN, say vlan1, issue this command:
(3200-1) #show ip igmp proxy-group vlan 1
IGMP Proxy Group Table
VLAN Addr Group Num Members
---- ---- ----- -----------
1 10.4.13.5 184.108.40.206 3
1 10.4.13.5 220.127.116.11 1
1 10.4.13.5 18.104.22.168 1
To display the group information for mobile clients that are away from the controller, issue this command:
(ARUBA)# show ip igmp proxy-mobility-group