Dante Domain Manager v1.7.1.6083

Dante Domain Manager (DDM) 1.7 offers a migration plan away from two critical components that are or will be End of Life.


Important: Existing DDM installations cannot be updated to v1.7 via the online update feature in the DDM user interface. For installation instructions, please see the DDM 1.7 Installation Guide.


DDM 1.7 is provided on a Rocky 9 platform, and OpenSSL has been updated to v3.0.

There are also a number of other improvements:

  • A review to ensure the language is inclusive
  • Increased default logging levels to enable better support for fault diagnosis
  • Improved reliability of install and High Availability
  • Support for Dante Connect
What's New: 

New features since v1.5:

  • Platform updated from CentOS to Rocky 9
  • OpenSSL updated from v1.1.1 to v3.0
  • A review to ensure the language is inclusive
  • Increased default logging levels to enable better support for fault diagnosis
  • Improved reliability of install and High Availability
  • Support for Dante Connect

See the DDM user guide for more information about new DDM features.

See the Managed API User Guide for more information about the API.

Notes: 

See Dante Domain Manager Support for documentation and other resources.

Version: 
1.7.1.6083
Release Date: 
Tuesday, February 27, 2024

 

Get Update Notifications

Bug Fixes: 
  • ETS-4041: DMM browser login expires earlier than the timeout value
Known Issues: 

New known issues

  • DDM-811: After installation or disbanding a HA cluster the network interface may be disabled. Workaround: Configure the network interface on the appliance menu to be static or dynamic, then reboot the appliance.
  • CLOUD-1303: Legacy devices cannot be configured via the GraphQL API. Workaround: Continue to configure legacy devices via Dante Controller.

Pre-existing known issues (from DDM 1.5)

  • DDM-430: Selecting a different number of records to show in the audit log fails. The second attempt at selecting a different number of records to show will succeed.
  • DDM-432: The branding feature is available only when the Main node is active. It is not available for the backup (auxiliary) node. The branding feature will be restored once the Main node is again active.
  • DDM-428 / DDM-429: Long API key descriptions may overlap with other page elements. Workaround: Restrict the API key description to approx. 35 characters, inc. spaces.
  • MIL-4635: High latency settings for a device, that are only available with Dante Domain Manager, remain when the device is unenrolled. Workaround: Manually change the latency to one that is better suited for local unmanaged network operation.
  • MIL-5452: Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller. Workaround: A pre v4.x Dante firmware device does not have the necessary communications to permit this. Please select another device as the preferred leader.

 

Audinate’s Support for Inclusive Language

To our customers: some of the terminology used in Dante products has been changed to align with modern usage. Specifically, areas related to Dante clocking now refer to “Primary Leader Clock”, “Leader Clocks” and “Follower Clocks” to describe the functions of each role more clearly.