AV-over-IP deployments now account for roughly 35 percent of new commercial installs tracked by rAVe this year, driven by NDI, Dante AV and SMPTE 2110 traffic that relies on multicast to keep bandwidth under control. The NETGEAR M4350-24G8F and M4350-48G8F models sit in many of these racks because their 1 Gbps copper ports and 10 Gbps SFP+ uplinks deliver acceptable port density at $2,800–$4,100 street price. Yet repeated integrator logs indicate IGMP snooping on these switches behaves unpredictably once a source stops answering General Queries or sends bursts above the 200 pps threshold the firmware expects.
In practice the switch stops pruning ports after two missed queries instead of the RFC-specified three, then re-floods the multicast group to every VLAN member. One Midwest house-of-worship project logged 14 percent packet loss on a 16-camera NDI feed after a single PTZ source powered down for three seconds; the M4350 required a full VLAN reset to restore selective forwarding. Similar behavior appears when encoders from two different manufacturers share the same VLAN without a dedicated querier, a common topology once budget AV racks grow past eight sources.
Daily Workflow Adjustments on the Job Site
Technicians now carry a pre-written startup script that forces the M4350 into querier mode on every AV VLAN and lowers the query interval from 125 s to 30 s. That script adds eight to twelve minutes per switch during first-turn-on, but it prevents the two-to-three-hour troubleshooting calls that used to occur when an encoder dropped offline overnight. Labor at prevailing AV tech rates of $145 per hour therefore rises $30–$45 per rack; on a 12-switch campus build the cumulative adder reaches $1,800 before any overtime.
Monitoring has also shifted. Instead of relying on the switch’s built-in IGMP counters, crews attach a laptop running Wireshark on a mirror port for the first 48 hours and watch for groups that exceed the 500-member limit the M4350 silently enforces. When that ceiling is hit, the switch stops reporting new joins and the stream simply disappears from downstream decoders. Several firms now stock an external PIM router or a Layer-3 switch from another vendor solely as the querier, adding $1,100–$1,600 to the bill of materials on every job above 24 sources.
Future firmware revisions may relax the query-miss threshold and expose per-port IGMP statistics through the existing web UI, but current owners must continue treating the M4350 as a multicast edge device that still needs an external querier for anything beyond simple single-vendor stacks. Integrators tracking 2025 refresh cycles are therefore budgeting an extra 15 percent contingency line for multicast management hardware until those changes ship.
One large-system integrator reported that a 48-source NDI deployment at a university lecture center required three separate M4350 chassis to stay under the per-VLAN join limit; when a fourth rack of decoders came online, the switches silently dropped new membership reports and forced a rolling reboot sequence that took 22 minutes. The same firm has since standardized on a mixed stack that places an inexpensive Layer-3 router in the core solely to generate queries, relegating the M4350s to edge transport only.
Training budgets have also increased. Several regional AV companies now run two-hour internal workshops on multicast troubleshooting, complete with packet captures that demonstrate the premature flood behavior. The added instruction time is billed internally at roughly $2,400 per technician, a line item that appears on every proposal above 16 sources. Meanwhile, rental houses have begun stocking spare querier appliances so that field teams can swap in a temporary fix without waiting for overnight shipping.
Until NETGEAR publishes updated firmware that matches the RFC timeout values and removes the undocumented 500-member cap, the M4350 remains a conditional choice for multicast-heavy rooms. Most project managers now list an external querier or competing switch as an alternate line item, allowing owners to decide whether the lower port cost justifies the operational overhead.
