Audinate Dante Core Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

The Dante Core Integration Node discovers Dante devices through the server network interfaces that you select. Choose the interface layout that matches the Dante network design, and add Dante Domain Manager only when the Dante network is managed by it.

Configuration	What hi Sees	Use When
Dante Network Interfaces	Dante devices of the network behind the Primary Interface, and of the secondary network when you select a Secondary interface.	The Dante network is unmanaged. Use one interface for a single network, or two for a primary and a secondary network.
Dante Domain Manager	The domains of Dante Domain Manager that you select.	Dante Domain Manager manages the Dante network.

Caution

Dante Via is not supported. Perform firmware updates, AES67 mode, and QoS configuration with Audinate tools, not in hi.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the hiDante license and the minimum hi version in Required Configuration.
Confirm that each server interface that you select is connected to the Dante network. See Network Requirements.
For Dante Domain Manager, have its hostname or IP address, the port, and an account that can see every domain that hi should control.

Configure Dante Network Interfaces

Use this configuration for an unmanaged Dante network, with one interface or with a primary and a secondary interface.

Device Configuration

Commission the Dante network and confirm that the devices are visible in the Audinate tools. See the Audinate documentation for Dante Controller. Ad hoc Dante networks can use different discovery and connection settings from a Dante Domain Manager deployment.
Identify which server interface is connected to the primary Dante network and, if present, which one is connected to the secondary Dante network.

hi Configuration

Create the Dante Core Integration Node in Inventory. Only one Dante Core Integration Node can exist in a system. The Primary Interface and Secondary interface settings are not shown when you create the Node. Open the Node after creation to select them.
In Network interface, select the Primary Interface. This is the network interface of the server that is connected to the primary Dante network.
For a second Dante network, select the Secondary interface. Leave it unselected when there is no secondary network.
Save the Node and wait for it to initialize.

Settings Summary

Setting	Device Side	hi Side
Primary network	The primary Dante network	Primary Interface
Secondary network	The secondary Dante network if present	Secondary interface

Configure Dante Domain Manager

Use this configuration when Dante Domain Manager manages the Dante network. The Node settings of the interfaces stay the same.

Device Configuration

In Dante Domain Manager, provide a user account that hi can use and that can see every domain that hi should control. Follow the Audinate documentation for Dante Domain Manager.
Record the hostname or IP address and the port of Dante Domain Manager. Dante controllers connect to Dante Domain Manager on TCP ports 8001 and 8443.

hi Configuration

Open the Dante Core Integration Node and the Dante Domain Manager group.
Enter Host, Port, Login Name, and Password of Dante Domain Manager.
In Domain, select the domains that hi should control. The setting accepts several domains and defaults to Unmanaged.
Save the Node.

Settings Summary

Setting	Device Side	hi Side
Server address	Hostname or IP address of Dante Domain Manager	Host
Server port	Port of Dante Domain Manager	Port
Account	User account of Dante Domain Manager	Login Name and Password
Domain	Domain of Dante Domain Manager	Domain

Common Checks

Symptom	Check
Expected devices do not appear in hi.	Confirm in the Audinate tools that the devices are visible on the Dante network, and that the selected interface is the one connected to that network.
Devices appear in the Audinate tools but not in hi.	Dante devices announce themselves with multicast DNS (mDNS) on the local network. Confirm that the selected interface is on the same network segment as the devices and that multicast is not filtered.
A domain does not appear in the Domain list or is not controlled.	Confirm that the Dante Domain Manager account can see the domain.

Verify the Configuration

Confirm that the expected Dante transmit and receive channels appear in hi. Route one test channel and confirm the resulting subscription in the Audinate tools before you commission production routes.