Controller Based WLANs

Clients are unable to join multicast
Problem:

When ip igmp proxy is enabled, clients are unable to join the multicast group:

 

1. The multicast server supports only IGMPv2 and customer has only windows 8 clients in the network.
2. With ip igmp snooping enabled, clients are able to autodetect and fallback to IGMPv2 and able to join the multicast group.
3. With ip igmp proxy enabled, clients are unable to join the multicast group.
4. Controller receives only IGMPv3 query from the clients and clients are not falling back to IGMPv2.
 

 


Diagnostics:

Below debugging need to be enabled on the controller

Config t

logging level debugging system process pim.

With igmp proxy, need to check the IGMPv3 received by the controller.

Jun 9 12:12:29 :204201:  <DBUG> |pim|  Received IGMP 3 QUERY from 10.4.220.253 on VLAN 704
Jun 9 12:12:29 :204273:  <DBUG> |pim|  RECEIVED QUERY 3 UPSTREAM IP 10.4.220.253 VLAN 704 
Jun 9 12:12:29 :204201:  <DBUG> |pim|  Received IGMP 3 QUERY from 10.4.212.253 on VLAN 705
Jun 9 12:12:29 :204273:  <DBUG> |pim|  RECEIVED QUERY 3 UPSTREAM IP 10.4.212.253 VLAN 705 
Jun 9 12:12:29 :204201:  <DBUG> |pim|  Received IGMP 3 QUERY from 10.4.218.253 on VLAN 702
Jun 9 12:12:29 :204273:  <DBUG> |pim|  RECEIVED QUERY 3 UPSTREAM IP 10.4.218.253 VLAN 702 

7. With igmp snooping, we can see clients fallback to IGMPv2.
Jun 9 09:46:38 :204202:  <DBUG> |pim|  Received IGMP 2 REPORT from 10.4.212.126 on VLAN 705
Jun 9 09:46:38 :204274:  <DBUG> |pim|  GSR for group 224.0.0.251 created in vlan 705
Jun 9 09:46:38 :204274:  <DBUG> |pim|  Processing v2/v1 report for Group 224.0.0.251, from Client 74:81:14:86:bf:4d, in Dest Tunnel Tunnel 13 and vlan 705
 


Solution
This is expected.

1. When snooping is enabled, controller just snoops IGMP packets flowing across
   it. Clients will report in the version of the IGMP query from router.
   In this topology the router sends query using V2, probably the router doesn't
   support version v3 and hence clients also report using version 2

2. When proxy is enabled, controller will send queries downstream. Controller
   will start with IGMPv3 query. As long as all clients report with IGMPv3,
   controller will continue in IGMPv3 mode. If controller sees atlest 1 client
   who reports in version V2, controller will fall back to V2 mode for all
   clients by start sending V2 queries.
   IGMPv3 support has been added in controller 6.4+ releases
 
Version history
Revision #:
2 of 2
Last update:
‎07-06-2015 05:07 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.