Change IGMP version 3 to 2 & Switch interface doesn't reply to ping

Getting noticed

Change IGMP version 3 to 2 & Switch interface doesn't reply to ping

Dear Members,



1. How do I change IGMP protocol version 3 to 2?

2. Why interface with IP doesn't reply to ping?








Thanks in advance & Best regards

Kind of a big deal
Kind of a big deal

That would sound like a bug.  Can you give the switch a reboot to see if it resolves the issue?

Rebooting the switch didn't help.

This is the second site where I am facing this issue. 

Meraki Employee
Meraki Employee



This interface appears to be a pseudo interface (existing on an L2 switch), as the screenshot shows no field exists to configure a subnet mask.


Pseudo interfaces on L2 switches (MS120, MS220) are highly limited in scope of functionality. They only send or receive IGMP or DHCP packets and do not respond to ping/ICMP. For more details, see:


As for IGMP version for IGMP snooping purposes, you cannot configure the IGMP version. Only version 3 is supported. However, IGMPv3 is backward compatible with IGMPv2. The only real IGMP packets you'll see transmitted by a switch performing IGMP snooping will be IGMP general query packets.


IGMPv3 query packets are processed in a fully backward compatible manner by IGMPv2 hosts. The only difference between an IGMPv3 general query versus IGMPv2 is that the IGMP payload of the v3 packet has some additional fields present in it not used by IGMPv2 hosts.


These are the fields that extend the IGMP payload beyond 8 bytes. However, this extra data is simply ignored by an IGMPv2 host, per IGMPv2 RFC 2236:


2.5. Other fields

   Note that IGMP messages may be longer than 8 octets, especially
   future backwards-compatible versions of IGMP.  As long as the Type is
   one that is recognized, an IGMPv2 implementation MUST ignore anything
   past the first 8 octets while processing the packet.  However, the
   IGMP checksum is always computed over the whole IP payload, not just
   over the first 8 octets.


The Type field is set as 0x11 for both an IGMPv2 and an IGMPv3 query -- meaning the IGMPv2 host will process the IGMPv3 query and respond in the correct manner.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.