The Best Network Switches for Dante and AoIP

The Best Network Switches for Dante and AoIP

Dante and Audio-over-IP (AoIP) systems demand network switches that go beyond basic connectivity — they require predictable, low-latency performance under heavy multicast traffic. This guide explains the critical specifications that make a switch Dante-ready, from non-blocking backplanes and QoS to IGMP snooping and EEE disablement, and provides practical configuration steps for reliable audio transport.

Key takeaways

  • A non-blocking backplane is essential — switching capacity must be at least 2 Gbps per port for gigabit switches.
  • Enable IGMP snooping and configure QoS with strict priority for DSCP 46 (audio) to prevent multicast flooding and jitter.
  • Disable Energy-Efficient Ethernet (EEE) and flow control on all ports to avoid latency and clock drift.
  • Managed switches are strongly recommended for any professional Dante deployment; unmanaged switches lack critical controls.
  • Use fibre uplinks for long distances and redundant switches for critical systems; never cross-connect primary and secondary networks.
  • Always test with Dante Controller and a known-good configuration before deploying in a live environment.

What Makes a Switch Dante-Ready?

Dante operates on standard IP networks but imposes strict timing and bandwidth requirements. A Dante-ready switch must support a non-blocking backplane — meaning its internal switching capacity equals or exceeds the sum of all port speeds — to prevent packet loss under full load. For example, a 24-port gigabit switch needs at least 48 Gbps of backplane capacity.

Quality of Service (QoS) with DiffServ (DSCP) marking is essential. Dante prioritises audio packets by tagging them with DSCP value 46 (EF). The switch must honour these markings and map them to strict priority queues, ensuring audio traffic is never delayed by data bursts.

IGMP snooping prevents multicast audio streams from flooding all ports. The switch must actively listen to IGMP membership reports and forward streams only to ports that have requested them. Without IGMP snooping, every multicast packet is broadcast to every port, overwhelming the network.

Energy-Efficient Ethernet (EEE, IEEE 802.3az) must be disabled. EEE powers down idle links to save energy, but the wake-up latency (tens of microseconds) can cause clock drift and audio dropouts. All Dante guidelines mandate EEE off on every port.

Gigabit Ethernet (1000BASE-T) is the minimum speed. While Dante can run on 100 Mbps, the overhead of multicast, clocking, and redundancy requires gigabit for any system beyond a handful of channels. 10-gigabit uplinks are recommended for larger deployments.

Managed switches are strongly recommended over unmanaged. Managed switches allow configuration of VLANs, QoS, IGMP snooping, and port mirroring — all critical for troubleshooting and isolating Dante traffic. Unmanaged switches lack these controls and can cause unpredictable behaviour.

Non-Blocking Backplane and Throughput

The backplane is the internal fabric that moves data between ports. A non-blocking backplane ensures that every port can communicate at full wire speed simultaneously. For a 48-port gigabit switch, the minimum backplane capacity is 96 Gbps (48 ports × 2 for full-duplex). Many budget switches advertise 'switching capacity' that is lower, leading to dropped packets under load.

When evaluating switches, look for the switching capacity specification. Divide by the number of ports to verify it meets or exceeds 2 Gbps per port (full-duplex). For example, a 24-port switch with 48 Gbps capacity is non-blocking. Anything less is blocking and unsuitable for Dante.

For Dante systems with redundant networks (primary and secondary), each network must have its own non-blocking switch. The two switches operate independently, so the backplane requirement applies to each.

QoS and DiffServ Configuration

Dante uses DSCP value 46 for audio, 34 for PTP clocking, and 0 for other traffic. The switch must be configured to trust DSCP markings and map them to hardware priority queues. Most managed switches allow 8 queues; assign queue 5 or 6 (highest) to DSCP 46, queue 4 to DSCP 34, and queue 0-3 to best-effort.

Strict priority scheduling must be enabled for the audio queue. Weighted fair queuing can introduce jitter. Ensure that the audio queue is always serviced first, even if other queues are backlogged.

Some switches require enabling 'trust DSCP' globally or per port. Disable any 'trust CoS' if it overrides DSCP. Test with a Dante Controller to verify that audio packets are not re-marked or dropped.

IGMP Snooping and Multicast Management

IGMP snooping is mandatory for Dante networks with more than two devices. It reduces multicast load by forwarding streams only to ports that have subscribed. Without it, a 64-channel stream would be copied to every port, wasting bandwidth.

Enable IGMP snooping on the VLAN carrying Dante traffic. Configure the switch to use IGMPv2 or v3 (Dante uses v2). Set the querier to the switch itself or a dedicated device. Ensure the IGMP query interval is not too aggressive (default 125 seconds is fine).

Fast leave can be enabled to reduce latency when devices disconnect. However, on some switches, fast leave may cause brief interruptions if a device rejoins quickly. Test in your environment.

For redundant Dante networks, each switch handles its own multicast groups independently. Do not enable IGMP snooping across the redundant link — it should be blocked at Layer 2.

EEE, Flow Control, and Other Pitfalls

Energy-Efficient Ethernet (EEE) must be disabled on every port. On many managed switches, this is a per-port setting under 'power saving' or 'green Ethernet'. On unmanaged switches, it is often impossible to disable — another reason to avoid them.

Flow control (IEEE 802.3x) should be disabled on all ports. Dante's clocking relies on precise timing; flow control pauses can cause jitter and clock drift. Disable both transmit and receive flow control.

Spanning Tree Protocol (STP) must be configured carefully. For redundant Dante networks, use Rapid STP (RSTP) with portfast on edge ports to avoid delays when devices connect. Alternatively, disable STP on Dante VLANs if the topology is simple.

Broadcast storm control should be set high enough to allow Dante's multicast bursts. A threshold of 5000 packets per second is typical. Too low a threshold can drop legitimate audio packets.

Managed vs Unmanaged: Why Managed Wins

Unmanaged switches are plug-and-play but offer no control over QoS, IGMP, or EEE. They may work for very small Dante systems (2-4 devices) but are risky for any professional deployment. Packet loss, latency spikes, and clock issues are common.

Managed switches provide visibility and control. They allow VLAN segmentation to isolate Dante from office traffic, port mirroring for troubleshooting, and SNMP monitoring for proactive alerts. The upfront cost is higher, but the reliability and diagnostic capabilities are essential for live sound.

For large-scale installations, managed switches with Layer 3 capabilities (routing) can be used to interconnect multiple Dante subnets. However, Dante typically runs on a single Layer 2 domain; routing requires careful configuration of PTP boundary clocks.

PoE, Fibre Uplinks, and Redundancy

Power over Ethernet (PoE) is useful for Dante-enabled microphones, speakers, and small stage boxes. Ensure the switch provides sufficient PoE budget (e.g., 30W per port for PoE+). However, PoE adds heat and cost; use PoE injectors for devices that don't require it.

Fibre uplinks are recommended for long distances (over 100m) or between buildings. SFP ports supporting 1G or 10G fibre allow clean galvanic isolation and eliminate ground loops. Use single-mode fibre for runs over 300m.

Dante's redundant network topology requires two separate switches (primary and secondary) with no crossover. Each switch must be configured identically but on different subnets. Use separate VLANs and ensure no routing between them.

Frequently asked

Can I use a consumer gigabit switch for Dante?

Consumer switches often lack IGMP snooping, have poor QoS, and cannot disable EEE. They may work for very small setups but are not reliable for professional use. Use enterprise-grade managed switches.

Do I need a 10-gigabit switch for Dante?

Not for most systems. Gigabit is sufficient for up to 512 channels at 48kHz. 10-gigabit is only needed for very high channel counts (1024+) or when aggregating multiple Dante networks.

How do I configure QoS for Dante on a Cisco switch?

Enable 'mls qos trust dscp', create a class-map matching dscp 46, assign it to a priority queue, and apply the service-policy to all ports. Disable 'mls qos rewrite dscp' to preserve markings.

What is the maximum cable length for Dante?

Standard Ethernet: 100m (328 ft). For longer runs, use fibre with SFP modules. Dante supports up to 7 hops over a switched network, so daisy-chaining switches can extend reach.

Can I mix managed and unmanaged switches in a Dante network?

Avoid it. An unmanaged switch can still flood multicast and cause issues even if connected to a managed switch. For best results, all switches in the Dante VLAN should be managed and configured consistently.

Building or upgrading a system?

SSOUNDS engineers and manufactures professional PA worldwide — from a single room to stadium scale.

Talk to an engineer