[c-nsp] Effect of IGMP version on IGMP Snooping

[Aaron Riemer]

I would get wireshark running on one of the hosts that tries to join a
multicast stream. Set IGMPv3 on the switch and monitor the subsequent IGMP
packets. i.e. Does an IGMPv3 query get sent out and do the hosts reply with
a join?

I would assume that swapping from IGMPv2 to IGMPv3 would clear out any
snooping information on the switch and thus would need to wait for
subsequent queries / membership reports?

Let us know what you find.

Cheers,

Aaron.


-----Original Message-----
From: John Neiberger [mailto:jneiberger at gmail.com] 
Sent: Tuesday, 25 January 2011 12:19 PM
To: Aaron Riemer
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Effect of IGMP version on IGMP Snooping

IGMPv3 is supposed to be 100% backward compatible. As far as I know,
this should have been transparent,but it wasn't Another weird thing is
that as soon as we reverted back to IGMPv2, the end devices started
working again. This behavior doesn't really make a lot of sense to me.

On Mon, Jan 24, 2011 at 8:46 PM, Aaron Riemer <ariemer at amnet.net.au> wrote:
> OK I am not able to test at the moment but will the switch respond to
IGMPv2
> join requests from the hosts if it is running IGMPv3?
>
> We had issues with another vendor switch that did not support IGMPv3 and
the
> hosts by default were running V3. The switch was unable to process the
> IGMPv3 join requests but obviously this is in reverse and I assume that
> IGMPv3 would be backward compatible with previous versions.
>
> Aaron.
>
> -----Original Message-----
> From: John Neiberger [mailto:jneiberger at gmail.com]
> Sent: Tuesday, 25 January 2011 11:37 AM
> To: Aaron
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Effect of IGMP version on IGMP Snooping
>
> The hosts are still running IGMPv2, but we will be upgrading them to
> v3 later. There is one particular piece of equipment that we will be
> replacing in the very near future that can only run v3, so we wanted
> to change the switch to v3.  To explain a bit more, this particular
> part of the network is really just one VLAN, no router, but IGMP
> snooping is enabled on the switch (multiple switches, actually.) So,
> my only thought is that switching to v3 in midstream while traffic was
> flowing somehow broke IGMP snooping even though we have verified that
> IGMP v3 snooping is enabled. We can't explain it, so we're sort of
> grasping for straws.
>
> We will be adding some additional monitoring and then conducting a
> test to see if we can spot the problem.
>
> On Mon, Jan 24, 2011 at 6:11 PM, Aaron <ariemer at amnet.net.au> wrote:
>> Did you enable IGMPv3 on the switch?
>>
>> How did you ensure all your hosts were running IGMPv3?
>>
>> From memory I had to registry hack the windows hosts to get it to run the
>> expected version.
>>
>> -----Original Message-----
>> From: cisco-nsp-bounces at puck.nether.net
>> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of John Neiberger
>> Sent: Tuesday, 25 January 2011 7:16 AM
>> To: cisco-nsp at puck.nether.net
>> Subject: [c-nsp] Effect of IGMP version on IGMP Snooping
>>
>> We have a flat layer two network with IGMP snooping turned on. We are
>> currently running IGMP v2 everywhere, but we need to enable v3. We
>> tested this a few nights ago and found that switching to v3 caused a
>> disruption. Everything started working again after we switched back to
>> v2. This doesn't make much sense to me.
>>
>> We have an interface acting as IGMP querier, so snooping seems to be
>> working. But why would changing IGMP versions cause any disruption?
>> And why would switching back to v2 suddenly make it work?
>>
>> If it matters, this is a Cisco 4948 running 12.2(25).
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>>
>
>