Multicast Optimization and IGMP Snooping in AV-over-IP

In modern enterprise and campus networks, AV-over-IP systems (like Crestron NVX or Just Add Power), Dante audio matrixes, and IPTV deployments rely heavily on multicast routing. Unlike unicast (one-to-one) or broadcast (one-to-all), multicast is a one-to-many architecture designed to stream a single payload to multiple interested receivers simultaneously.

However, without explicit protocol management at the switching layer, high-bandwidth multicast traffic will instantly degrade into a broadcast storm, saturating access-layer uplinks and entirely collapsing wireless airtime.

This guide details how to correctly implement Internet Group Management Protocol (IGMP) Snooping, Querier elections, and edge optimizations within a UniFi switching topology.

---

1. The Layer 2 Flooding Problem and MAC Mapping

At Layer 2, an Ethernet switch relies on the destination MAC address to forward frames. IPv4 multicast IP addresses (ranging from 224.0.0.0 to 239.255.255.255) are mapped to a specific block of multicast MAC addresses beginning with the Organizationally Unique Identifier (OUI) 01:00:5E.

Because multicast MAC addresses are never used as a source address, a switch can never dynamically learn them and populate its CAM (Content Addressable Memory) table. Consequently, a standard switch treats unknown multicast frames exactly like broadcast frames: it floods them out of every active port on the VLAN.

If a video encoder transmits a 900 Mbps 4K video stream into a 48-port access switch, unmanaged flooding will attempt to push that 900 Mbps stream out of all 47 remaining ports. This instantly saturates every 1 Gbps copper link on the hardware, dropping legitimate traffic and triggering network-wide spanning tree and ARP failures.

---

2. IGMP Snooping and the Forwarding Database

To prevent flooding, the network must transition from a "push" model to a "pull" model. Enabling IGMP Snooping instructs the UniFi switch's ASIC to intercept and inspect IGMP control packets flowing between the multicast router and the client hosts.

Instead of flooding, the switch acts as a passive listener to dynamically build a multicast forwarding database.

1. IGMP Join (Report): Client Registration. A client application (e.g., a VLC player or Dante receiver) sends an IGMPv2 Join message requesting traffic for 239.1.1.5. The UniFi switch intercepts this frame, reads the payload, and adds the client's physical port (e.g., Port 12) to the forwarding table for that specific multicast group.

2. Selective Transmission: Constrained Forwarding. When the multicast source begins streaming data to 239.1.1.5, the switch references its forwarding database and replicates the packets only out of Port 12, leaving the rest of the switch's backplane completely untouched.

3. IGMP Leave & Fast Leave: Graceful Teardown. When the client closes the stream, it transmits an IGMP Leave message. Under standard protocols, the switch waits for the next querier timeout to prune the port. If Fast Leave is enabled in the UniFi controller, the switch immediately drops the port from the group database, instantly freeing up the link's bandwidth.

Engineering Note on Fast Leave: In AV-over-IP environments where users "change channels" (switching between high-bandwidth video streams), enabling Fast Leave is mandatory. Without it, a client switching from Stream A to Stream B will temporarily receive both streams simultaneously until Stream A times out, easily exceeding a 1 Gbps port capacity and causing severe macro-blocking or link failure.

---

3. The IGMP Querier and Mrouter Port Topologies

A snooping switch is strictly a passive observer; it does not generate membership queries. If a host joins a group but is never asked to renew its membership, the switch's forwarding table will eventually age out, and the video stream will abruptly stop (a phenomenon known as "multicast black-holing").

To keep the database active, an IGMP Querier must exist on the VLAN. The Querier periodically broadcasts an IGMP General Query (usually every 60 to 125 seconds) to all hosts, prompting them to reply with an IGMP Report if they still want the stream.

UniFi Querier Election Mechanics

Historically, UniFi switches disabled querier elections by default, leading to chaotic scenarios where edge switches with slower links might randomly assume the querier role.

In modern UniFi Network OS versions, engineers can explicitly enforce the topology using the Create New Querier Switch function.

• Always assign the Querier role to the Core / Aggregation Switch at the center of the topology.
• This ensures that all IGMP Join and Leave messages traverse the network core, allowing all downstream edge switches to properly snoop the traffic and build their own local forwarding tables.

Multicast Router (Mrouter) Ports

Any port facing the active IGMP Querier or a live multicast source must be explicitly flagged as a Multicast Router Port in the UniFi Port Manager. This configuration forces the switch to forward all intercepted IGMP Join reports up to the querier, ensuring the core topology is aware of edge-level subscriptions.

---

4. Wireless Disruption and Multicast-to-Unicast Conversion

Pushing multicast traffic into a wireless footprint introduces severe physical layer penalties.

By default, the 802.11 standard requires wireless access points to transmit multicast frames at the lowest configured Basic Service Set (BSS) rate (often 1 Mbps or 6 Mbps) to guarantee that the weakest, furthest client in the cell can successfully decode the transmission. Furthermore, because the frame is addressed to a group, receiving clients do not transmit 802.11 Acknowledgement (ACK) frames.

If a 5 Mbps multicast audio stream leaks onto a UniFi Access Point, it will transmit at 6 Mbps without ACKs, consuming nearly 100% of the channel's available airtime and immediately crashing the wireless experience for all other users.

Mitigation Strategies in UniFi

To protect the RF environment:

1. VLAN Isolation: Keep AV-over-IP and Dante hardware on dedicated, wired-only VLANs that are entirely unassigned from any wireless SSIDs.
2. Enable Multicast Enhancement (IGMPv3): If multicast must cross the wireless boundary (e.g., for mDNS casting or wireless IPTV clients), enabling "Multicast Enhancement" on the SSID instructs the UniFi AP to perform Multicast-to-Unicast conversion. * The AP tracks which specific wireless clients joined the group. * It intercepts the multicast frame from the wired backbone. * It converts the frame into individual unicast frames directed at the specific clients. * This allows the AP to transmit the data at high-speed OFDM PHY rates (e.g., 800+ Mbps) and re-enables ACK tracking for reliability, preserving raw airtime capacity.

What breaks in production

Multicast is the only traffic class where a single misconfigured device can consume the whole campus uplink without sending a single packet to the internet.

• Querier election. Exactly one querier per VLAN. Two, and group membership flaps.
• mrouter ports. The uplink toward the multicast source must be statically or dynamically marked, or the switch prunes the source itself.
• Wireless multicast. Multicast on Wi-Fi is sent at the lowest basic rate to every associated client. A single 20 Mbps video wall stream becomes an airtime outage for the whole AP.
• IGMP version mismatch. v2 hosts on a v3-only querier silently stop receiving.

Checklist

1. One querier per VLAN, documented by name.
2. mrouter ports verified after any topology change.
3. Multicast-to-unicast conversion enabled on wireless for AV streams.
4. IGMP version is consistent across hosts, querier, and upstream router.