Bind to multiple interfaces for redundancy failover

[Jules_Lalu]

Hi,

We are using a redundant Ignition setup with a master and backup.
Each Ignition instance has 2 network interfaces. We would like to fail over to the backup instance if one of the 2 network interfaces is unreachable on the main, but currently the failover happens only when the first network interface of the main is down.
We have seen that there was a parameter in Redundancy -> Network settings called "Network Bind Interface", however specifying both ip adresses of our interfaces with syntax "123.456.789.012,123.456.789.013" does not seem to work.

Is there a way to make this work ? Or at least a workaround ?

Thank you in advance for your help.

[pturmel]

@Jules_Lalu

We are using a redundant Ignition setup with a master and backup.
Each Ignition instance has 2 network interfaces.

Not a good plan.

See my answer here for a similar question:

Architecture for Distributed Control Center

Ignition redundancy is both latency sensitive and subject to split brain syndrome. If the comms goes down between sites, both servers will end up active and therefore numerous properties start to diverge. So let me amend my answer to: Ignition redundant servers must be installed on a common LAN with a robust network layout (preferably multi-path, like RTSP), such that any loss of comms also results in loss of comms to all clients and all devices and all databases. (Trunk port for multiple VL…

Related discussion:

Client connections to server with multiple NICs

That is a design error. The redundant gateway needs to be on the exact same networks as the primary gateway. And both primary and redundant gateways need to be set to use their names as their public addresses. If you are connecting remotely, put entries in your own /etc/hosts file with the appropriate names if you cannot make your local DNS provide them. (In most cases, there should not be a redundancy network. It can lead to "split brain" situations.)

[pturmel]

This is the key requirement:

@Architecture for Distributed Control Center

any loss of comms also results in loss of comms to all clients and all devices and all databases

Also, all clients should target main and backup servers via DNS name, not IP address, and the gateways should be publicly advertising their DNS names.