Vision Client Redundancy in Ignition 8.3

Ignition
,
1

I recently upgraded the Ignition Gateway, Designer Launcher, and Vision Client Launcher from version 8.1 to 8.3.4 The upgrade was performed by running the installer directly on the device without removing the old version. Our SCADA system has two IO servers: IO1 hosts the Ignition Master Gateway, and IO2 hosts the Ignition Backup Gateway. Designer Launcher and Vision Client Launcher are installed in different workstation.

After upgrading to Ignition 8.3, we encountered issues during gateway failover between the Master and Backup. Specifically, when launching the Vision Client connected to the Master Gateway, it fails to reconnect to the Backup Gateway if the Master is powered off or switched over. Both gateways show “Peer Connected” with synchronization status as good, but the Vision Client keeps searching for an available node. The same issue occurs when failing over from Backup to Master.

The behavior seems like that the Vision Client does not automatically reconnect to the active gateway during failover:

  1. Launch Vision Client → connected to Master Gateway (IO1).

  2. Failover to Backup Gateway (IO2) → Vision Client cannot connect.

  3. Re-launch Vision Client → connects successfully to Backup Gateway.

  4. Failover back to Master Gateway → Vision Client cannot connect again.

  5. Re-launch Vision Client → connects successfully to Master Gateway

Anyone facing similar issue in Ignition 8.3?

2

Have you tried re-creating the Vision client connection? The redundancy information is passed to the client when it's first setup.

3

This sounds like the opposite. Like, the saved launch settings have both servers correct, but the runtime update from the servers is wrong. The public HTTP address settings may be wrong, or the redundancy address configured in the master is only correct from the master's network environment.

(Master and Backup are supposed to be on the same subnet, along with critical clients and and the inbound route path from other subnets. Some restrictions can be avoided if using DNS names everywhere instead of IP addresses.)