Pro AV Index Independent · Pro AV Reference

Switch Requirements for Dante Networks

Short answer A Dante network needs a managed switch with DiffServ QoS enabled, IGMP snooping with an active querier when multicast is used, Energy Efficient Ethernet disabled, and no more than three hops between any two devices at default latency. Unmanaged switches work only on small unicast-only systems.
Ethernet patch cables terminated into the front ports of a managed rack switch
Audio and IT traffic share the same copper. Everything below is about keeping them from interfering.Photo: Brett Sayles / Pexels

The four settings that matter

1. QoS — DiffServ, not 802.1p

Dante uses DSCP marking. Clock packets must land in the highest priority queue, audio one below, everything else in best effort.

TrafficDSCPQueue
PTP clock (event)56 (CS7)Highest
Audio46 (EF)High
Reserved8 (CS1)Medium
Other0Best effort

If clock and audio share a queue, the audio bursts delay the clock and the domain loses sync under load.

2. IGMP snooping — with a querier

Multicast flows without IGMP snooping are flooded to every port. On a 48-port switch, that turns eight multicast flows into a broadcast storm. Enable snooping, and make sure exactly one querier exists on the VLAN.

3. Energy Efficient Ethernet — off

Disable EEE (802.3az) on every port carrying audio.

If you fix one thing

Energy Efficient Ethernet is the single most common cause of intermittent, unreproducible dropouts on otherwise healthy audio networks. Turn it off before you troubleshoot anything else.

4. Hop count and latency

Default device latency of 1 ms covers three hops of gigabit switching. Count hops on the drawing, not on site.

HopsMinimum latency setting
1–31 ms
4–102 ms
Beyond, or 100 Mbps links5 ms

Commissioning checklist

Frequently asked

Can I use an unmanaged switch for Dante?

On a small system with only unicast flows and no other traffic, yes. Once you add multicast flows, a second switch, or shared IT traffic, you need a managed switch with QoS and IGMP snooping.

Why does Energy Efficient Ethernet break Dante?

EEE puts ports into low-power states between packets. The resulting jitter disturbs PTP clock recovery, which shows up as intermittent dropouts that are very hard to trace.

How many switch hops can Dante tolerate?

Three hops at the default 1 ms latency setting. Beyond that, raise the device latency setting rather than hoping it works.

Specifying a system right now? [邮箱位 · 待填] [电话位 · 待填]