Adding Frontend Redundancy - Vision Client experience?

I’ve just configured redundancy on a frontend gateway and noticed that the Vision clients are unable to launch while the backup is active. I have to open the Vision Client Launcher, “manage” the connection, and save it without changes. Then I am able to launch it while the backup is active.

This leads me to the question:

When you create a connection, in Vision Client Launcher and Perspective Workstation, what information is cached/saved to that connection? It would seem at least for the Vision Client connection, that the redundancy configuration is stored. I would have hoped that this would be pulled down from the configured gateway when you go to launch it.

The information needed to launch redundantly needs to be present when the application is set up in the launcher. If you set them all up when the frontend wasn't redundant, I don't see how it could be different. The launcher is not going to arbitrarily redo your config.

And if the master is done, there is nothing to contact to fix it, anyways.

Agreed here, but the master was just inactive, so I would have thought it could be contacted to retrieve the config :person_shrugging:

1 Like