I pass Source Specific Multicast (SSM) through a small Meraki switch withoutissues, so I can stream encrypted 4K videos. To do this, I ensure that IGMPv3 snooping is enabled. But the MX does not handle SSM, and there is no information as to when it might. As a workaround, I have ordered a router that does handle SSM to place ahead of the MX.
Ideally, I would have just put another MS switch ahead of the MX64 and used an IPv6 address, but my ISP has not fully rolled out IPv6 , yet and there are limitations as to what Meraki does with IPv6 presently.
The Cisco IOS software uses a default IGMP query interval of 60 seconds, which is different from the RFC standard default of 125 seconds. Using a lower default IGMP query interval of 60 seconds allows routers to stop forwarding traffic faster when a member crashes without sending leaves (in IGMPv2 or IGMPv3 environment), or if using IGMPv1: 3 * 60 seconds versus 3 * 125 seconds.
If a lower version IGMP-enabled interface (that is, an interface running IGMPv1 or v2) receives a higher version IGMP query (IGMPv3) with a different query interval, the following events will occur:
An error message in the following format will be displayed: %IGMP-3-QUERY_INT_MISMATCH: Received a non-matching query interval <interval in seconds>, from querier address <ip-address>
There is too much to copy everything, but it is illuminating to read up on it.