Check IGMP Snooping Before Blaming an AV Receiver

When multicast AV traffic works briefly and then disappears, inspect receiver membership and the VLAN's querier before changing the endpoint. IGMP snooping limits forwarding according to learned interest; it is not multicast routing. Verify behavior after membership aging and switch restart, and use the switch's exact platform documentation rather than a generic command copied from another model.

Separate control from the multicast payload

First identify the group address and UDP port associated with the failing function. Discovery, audio transport and device control may use different conversations. A receiver visible in a management tool does not prove that its media group is forwarded correctly, and a working unicast command does not validate multicast distribution.

RFC 4541 discusses snooping switch behavior and interoperability considerations. Cisco's multicast configuration guide provides a concrete platform reference for membership and querier configuration. Apply its commands only to supported software and hardware after the network owner reviews them.

Collect forwarding evidence

Ask the switch administrator for the VLAN identifier, multicast group table, receiving ports, router ports and querier state. Note the time and endpoint state with each snapshot. If the table changes when the receiver starts or stops, correlate those changes with application events and packet captures.

A membership entry alone is insufficient. It may represent another receiver behind the same downstream switch or access point. Verify which physical device and port the entry actually describes.

Run a timed test

• Save the switch configuration and relevant state before changing it.

• Start one source and one receiver with documented settings.

• Confirm the intended multicast group at the source and receiver observation points.

• Record joins, queries and reports during a period longer than the configured membership aging interval.

• Stop and restart the receiver, checking leave and rejoin behavior.

• Repeat across the actual uplink path and after a controlled switch restart.

If the VLAN has no multicast router, determine whether the switch provides a supported snooping querier and how it participates with other queriers. Do not assume every vendor elects or implements queriers identically. The appropriate design is an agreed operational arrangement for the VLAN, not several independently enabled features with no documented owner.

Avoid broad fixes that hide the failure

Disabling snooping can flood traffic to ports that never requested it. That may temporarily restore a receiver while overloading unrelated links. Treat such a change, if approved for a short diagnostic comparison, as evidence gathering rather than the final solution. Restore the intended configuration and verify the root cause.

Also keep routed multicast separate. Extending a group between VLANs needs a deliberate Layer 3 design and policy; snooping alone does not create it. Wireless distribution introduces additional controller and access point behavior that must be tested on its own.

Accept the network when the intended receiver continues receiving over the agreed observation period, rejoin works after interruption, and unrelated ports avoid unnecessary traffic. Save group addresses, timing settings and state snapshots in the handover.

Use Dante Controller troubleshooting when the application is Dante, while treating this guide as a general network investigation rather than a claim that all AV protocols share the same multicast requirements.