Dante Redundant vs Switched Mode: Wire Dual-Port Devices Correctly

TL;DR — In redundant mode, a supported Dante device sends the same media over separate primary and secondary networks so audio can continue after one network path fails. In switched mode, the second port acts as an extension of the primary connection and can support a daisy chain; it is not a backup network. Never join primary and secondary redundant networks. Confirm each device's capability and port mode, map both failure domains, match required link speeds, and test real cable and switch failures before relying on redundancy.

The second Dante port can have two very different jobs

Some Dante devices provide two Ethernet ports. In redundant mode, the ports connect to two separate networks. The device transmits the same Dante media on both paths, allowing supported endpoints to continue through the surviving network if one path fails.

In switched mode, the second port behaves as part of an internal network switch. It extends the same network to another device. This can reduce the number of external switch ports or support a short daisy chain, but both connectors remain inside one failure domain.

Not every dual-port product supports both modes, and some products expose specialist switch configurations. The device manual and controller status are authoritative. Do not infer redundancy from the presence of two RJ45 sockets.

Choose redundant mode for continuity across a real second network

Redundancy is useful when loss of a cable, switch, power feed, or network segment must not interrupt audio between endpoints that support duplicate paths. A proper design separates the primary and secondary failure domains as far as the production requires.

That can mean:

• separate primary and secondary switches;
• separate cables and patch-panel routes;
• independent switch power where the risk plan requires it;
• both ports connected on every redundant-capable device;
• non-redundant devices connected to the primary network only;
• a control computer connected so technicians can still diagnose the surviving network.

Primary and secondary networks must not be interconnected. Connecting both to the same network or joining their switches defeats the required separation and can create an invalid topology. Label every switch, trunk, patch point, and device port by network.

Redundancy covers only the duplicated part of the path. A console card, stage box, amplifier interface, power supply, or single cable beyond the Dante endpoint may still be a single point of failure. Draw the entire programme path rather than calling the system redundant because two switch stacks exist.

Choose switched mode for a deliberate single-network extension

Switched mode is appropriate when a device's second port is intended to continue one network to another endpoint and the production accepts that shared failure domain.

Possible uses include:

• two nearby devices connected where only one switch cable is available;
• a small non-critical setup with a short, documented chain;
• temporary control or playback systems where rapid deployment matters more than path redundancy;
• endpoints whose manufacturer explicitly supports the planned topology and bandwidth.

A chain has operational tradeoffs. Powering down or disconnecting an upstream device may isolate downstream equipment. Several devices share the same uplink. Cable troubleshooting becomes positional, and a loop created by careless reconnection can disrupt the network unless the wider switch design handles it correctly.

Keep chains short, record their order, and count the traffic that must cross each shared link. For a larger show, star connections to managed switches are usually easier to inspect and recover than an undocumented chain.

Separate port mode from subscription and clock configuration

Changing a device from switched to redundant mode changes the network role of its ports; it does not replace the Dante subscriptions. Redundant-capable devices normally carry the same configured media across both networks without a second set of routes. Confirm the actual product behavior before changing mode because some configuration changes require a reboot.

Dante clock synchronization also operates across the designed network. A redundant system must keep a valid timing reference through the surviving path, but that does not justify linking the two networks. The digital audio network rider covers clock leader, latency, sample rate, multicast, switch, and ownership fields in the wider network design.

Use distinct questions during commissioning:

1. Are transmitter-to-receiver subscriptions correct?
2. Are device sample rates and latency settings valid?
3. Is each port in the intended switched or redundant mode?
4. Are primary and secondary physically separate?
5. Which devices and services remain single-homed?

Map the failure domains before calling the design redundant

Audinate's guidance requires the primary and secondary interfaces of a redundant device to use the same link speed. Check negotiated speed rather than assuming matching switch-port labels guarantee it. Also verify VLAN, energy-saving, quality-of-service, multicast, and other switch settings against the equipment and network design.

Test redundancy by removing actual components

1. Save the known configuration

Export or record device names, port modes, subscriptions, sample rates, latency, clock status, firmware context, and switch configuration. Identify the approved baseline and the person allowed to change it.

2. Prove normal operation on both networks

With both paths connected, confirm every required transmitter and receiver, clock status, latency, errors, link speed, and audio destination. A green link light alone does not prove audio continuity.

3. Remove one primary cable

Disconnect a selected primary device link while monitoring audio at the real destination. Confirm the redundant endpoint continues without an audible interruption and that the controller reports the expected fault.

4. Restore, then remove the corresponding secondary cable

Allow the system to return to a healthy baseline before the second test. Verify the primary path carries the programme and that alarms are visible.

5. Test switch and power boundaries

Where authorized, remove power or uplink connectivity from one switch at a time. Confirm which devices, control functions, and non-redundant endpoints disappear. Do not perform destructive network tests during a live show.

6. Rehearse diagnosis and recovery

Have another technician identify the failed network from labels and monitoring, replace or repatch the fault, and confirm both paths return. Record expected recovery time and any step that can disrupt subscriptions or clock leadership.

Document ports, not just the word “redundant”

A useful Rider or advance note identifies device capability, mode, network names, switch ownership, physical paths, speed, addressing approach, control access, test window, and fallback. “Dual Dante” or “redundant Dante required” is not enough to build or verify the topology.

In Techrider.live, keep network endpoints and ownership aligned with the stage plot and signal notes, invite system and touring engineers to edit the same Rider, save the accepted topology, inspect history after a port-mode change, and export a dated PDF for load-in.

Dante port-mode checklist

• Every dual-port device's supported modes are confirmed from its documentation.
• Each device is set to the intended redundant or switched mode.
• Primary and secondary networks are physically separate and never interconnected.
• Both redundant interfaces use the required matching link speed.
• Non-redundant endpoints and other single points of failure are marked.
• Subscriptions, clock, latency, errors, and audio were verified on both paths.
• Cable, switch, power, control, recovery, and analog fallback tests are complete.

FAQ

What is the difference between Dante redundant and switched mode?

Redundant mode uses the two ports for separate primary and secondary networks carrying duplicate media. Switched mode places both ports on one network so the second port can extend that network. Switched mode is not a redundant path.

Can Dante primary and secondary networks use the same switch?

No. A redundant design requires separate primary and secondary networks, and they must not be interconnected. Use separate switching paths and label them clearly.

Does every Dante device support redundancy?

No. Support depends on the device implementation. Some dual-port devices offer switched mode only or specialist configurations. Confirm the device manual and controller settings; connect non-redundant devices to the primary network.

Can you daisy-chain Dante devices in redundant mode?

Not by using the primary and secondary ports as an in-and-out pair. In redundant mode those ports belong to separate networks. Daisy chaining may be available in switched mode when the device manufacturer supports it.

How do you test a redundant Dante network?

First confirm healthy audio, subscriptions, clock, latency, errors, and link speed. Then remove one primary component at a time, restore it, repeat on secondary, and test authorized switch or power failures while monitoring the real destination and controller alarms.

Make both network paths inspectable

Build one Rider that names each port, cable route, switch, power boundary, controller interface, failure test, owner, and fallback before the network reaches the stage.