13 1+1 redundancy (high availability), 1 what is high availability (ha) – Digigram Software for IQOYA SERV/LINK 88 (Upgrades from 8 Codecs to 16) User Manual
Page 143
![background image](/files/872155/content/doc143.png)
IQOYA SERV/LINK user manual
13 1+1 redundancy (High Availability)
IQOYA SERV/LINK supports 1+1 redundancy, meaning that two similar units can run together with one being a “hot” backup of the other.
This redundancy is available through a software option named “High Availability” which has to be installed on the two units working in
redundant mode.
13.1 What is High Availability (HA)?
High Availability is a network configuration ensuring that planned and unplanned outages do not interrupt significantly the IP
audio services. In a HA configuration, the IQOYA SERV/LINKs are deployed in pairs called HA pair. The devices of a HA pair
share a floating IP address (virtual IP address = VIP). Thanks to this VIP, the HA pair is seen as a single device. The VIP is
the IP address to be used to reach the HA pair.
Within the HA pair, one IQOYA SERV/LINK operates in the
active
mode and the other IQOYA SERV/LINK operates in the
standby
mode:
●
Active
: The active member of the HA pair is the system actively processing the audio signals. The active member
continuously monitors itself for internal processes health. If the active member detects a condition that can interrupt
the IP audio services, it hands over its role as the active member of the HA pair to the standby member.
●
Standby
: The standby member of the HA pair is the backup system. The standby member audio configuration is
fully synchronized with the active member configuration, but it does not actively process the audio signals.
Synchronization of the configuration is based on
the FTP protocol, which must be activated on both units
.
The standby member monitors the status of the active member and it can assume the active role without the active
143
Clocking considerations
●
AES67 mode on a Dante device enables both IEEE 1588 Precision Time Protocol (PTP) v1 and v2. A single clock domain
must be created across both PTP v1 and v2 devices:
●
Standard Dante devices support PTP v1 only
●
AES67-enabled Dante devices support PTP v1 and PTP v2
●
AES67 devices support PTP v2 only
●
PTP v1 and v2 are not inter-compatible. One AES67-enabled Dante device will act as the boundary clock between PTP v1
and v2, bridging the two clock domains
Enabling LX-DANTE as Master for both Dante and AES67.
●
Enable the Dante card “Preferred Master” status
●
Disable “Preferred Master” for all Dante devices that have AES67 disabled.
●
Disable “Sync to External” for all devices.
●
Assign a PTPv2 priority level of between 128 and 255 for all non-Dante devices
If another AES67 device (Grandmaster Clock, or another AES67 device) is the Master ,
●
Make sure the PTP v2 Master has a priority of between 1 and 100, and is using the “Media Profile” clock settings.
●
Disable “Preferred Master” and “Sync To External” for all Dante devices.
●
One AES67-enabled Dante device will automatically be selected as the Boundary clock, becoming the Dante Master.
●
Make sure the Master Clock device is set to use the “Media profile” (not the “Default profile” because Dante devices do not
support the Default profile.