A 1G AV-over-IP system works or fails at the switch. It needs a managed switch with IGMP snooping on a dedicated VLAN, one IGMP querier per VLAN, unregistered multicast dropped and fast leave on decoder ports — plus non-blocking capacity, uplinks sized to the streams that cross them, and a PoE budget for every powered endpoint.
Why does multicast flood without IGMP snooping?
Because, as RFC 4541 describes, a switch without snooping copies multicast into each of its other interfaces. One multicast stream can feed many decoders — and, unsnooped, every other device in the VLAN too. IGMP snooping listens to the membership reports decoders send when they join, and forwards each group only to the ports that asked. Snooping and querier must match the endpoints' IGMP version, 2 (RFC 2236) or 3 (RFC 3376); a version 2 query drops version 3 hosts to 2.
Why does IGMP snooping need a querier?
Because memberships expire. Hosts report when they join, then in answer to queries; a snooping switch drops a port when no report arrives within its membership timer — 260 seconds at RFC 2236's defaults. With nothing querying, entries age out and streams stop or fall back to flooding. Without a multicast router, a switch must act as querier. RFC 2236 elects one per network — the lowest IP address wins — so decide which switch it is for each AV VLAN, somewhere the uplinks can take the load: RFC 4541 says multicast data must also be forwarded on router ports, learned from where queries arrive.
What should the switch do with unregistered multicast?
Drop it. A stream nobody has joined — an encoder running before its decoders are patched — is unregistered, and RFC 4541 lets a switch default to forwarding unregistered packets on all ports: the very flood snooping exists to prevent. Enable the switch setting that drops it, or restricts it to router ports. Then test: with every decoder unplugged, no encoder traffic should reach an idle port.
Why does fast leave matter for switching speed?
When a decoder changes source, a switch without fast leave first checks whether anyone else on that port still wants the old group — two group-specific queries a second apart under RFC 2236's defaults; some switches document up to ten seconds. Meanwhile both streams can reach the port, and if each can use most of a gigabit link, two cannot share a 1G decoder port. Fast leave (or immediate leave) prunes the port the moment the Leave arrives. Enable it only on single-receiver ports.
Does AV-over-IP need its own VLAN?
Ideally, yes. Snooping is enabled per VLAN, and whatever still floods — unregistered streams, or non-IGMP traffic in 224.0.0.X, which RFC 4541 sends to all ports — stays inside its VLAN. A dedicated IEEE 802.1Q VLAN for the AV endpoints contains it and gives the IT team a clear boundary.
How much switch and uplink capacity is enough?
Two sums. The switch must be non-blocking — able to run every port at line rate at once: ports × speed × 2 for full duplex, so 48 Gbps for 24 gigabit ports and 96 Gbps for 48, before uplinks. Then each uplink: count the distinct multicast streams that must cross it at once — not the displays; towards the querier, every stream behind it — and multiply by the per-stream peak in the product documentation. At a hypothetical 900 Mbps a stream, 1G carries one; 10G carries ten.
How much PoE does each port and switch need?
Per port, IEEE 802.3at (Type 2, PoE+) supplies up to 30 W at the switch, with 25.5 W available to the device; 802.3af provides about 13 W to the device, 802.3bt 51 W (Type 3) or 71.3 W (Type 4). Per switch, the controller cannot allocate beyond the PoE budget. TC-IPE-HC, for instance, is an 802.3at powered device or runs from local 12 V; budgeted at 30 W a port, sixteen 802.3at endpoints reserve 480 W.
Are jumbo frames required?
Only if the product's documentation says so. Standard Ethernet carries IP datagrams of up to 1,500 octets; jumbo sizes are vendor-dependent, not part of the IEEE standard, and the MTU in use must not exceed what every switch in the path supports.
How should QoS be set when Dante shares the network?
Audinate recommends QoS in all Dante networks — DiffServ (DSCP) with strict priority. Dante hardware marks time-critical PTP events CS7 (DSCP 56) and audio EF (DSCP 46); serve those ahead of best-effort traffic, which on a shared uplink may include video. Audinate also advises disabling Energy Efficient Ethernet on ports carrying real-time Dante.
How far can the copper run?
100 metres, switch port to endpoint. 1000BASE-T was specified for 100 m of four-pair Category 5 cabling, and TC-IPE-HC is rated at 100 m over CAT6/6A/7 to the switch. Further needs a nearer switch or fibre, not a longer cable.
The pre-commissioning checklist
- IGMP snooping on, in the endpoints' IGMP version.
- One querier per AV VLAN, at a chosen address.
- Unregistered multicast dropped.
- Fast leave on single-receiver decoder ports only.
- Non-blocking fabric; uplinks sized to distinct streams.
- PoE checked per port and per switch.
- Jumbo frames only if documented.
- Where Dante shares the switches: DSCP strict priority, EEE off.
- No run over 100 m.
What to ask the IT team
Which switch hosts the system, and is it non-blocking? Who owns the AV VLAN's querier? Will unregistered multicast be dropped and fast leave allowed on decoder ports? What capacity links the switches? What PoE budget remains after the AV endpoints? For where the 1G tier sits, see the middle path: JPEG2000 at 1G; for the endpoints, the AV-over-IP range.
Questions, answered briefly
Does AV-over-IP need IGMP snooping?
For multicast, yes. Without IGMP snooping a switch forwards multicast to every port in the VLAN, so every stream reaches every device. With snooping, each stream goes only to the ports whose devices have joined it.
Why does IGMP snooping need an IGMP querier?
Hosts refresh their group memberships in answer to IGMP queries. Without a querier the reports stop, the switch's membership entries time out, and streams stop or start flooding. Where no multicast router is present, configure one active querier per VLAN.
How much power does an IEEE 802.3at (PoE+) port deliver?
IEEE 802.3at, Type 2, supplies up to 30 W at the switch port, with 25.5 W available to the powered device. Check the switch's total PoE budget as well as the class of each port.
Does AV-over-IP need jumbo frames?
Only if the product's documentation says so. Jumbo frame sizes are vendor-dependent and not part of the IEEE standard, and the MTU in use must not exceed what every switch in the path supports.