Geo SCADA 2025 Gateway Redundancy Issue After Upgrade

[DHANUSH]

Hi,

We are facing an issue after upgrading our SCADA system from ClearSCADA 2017 to Geo SCADA 2025.

Previously, the gateway redundancy was working correctly. We are using a Sharing Type: Independent configuration with Preferred Line: A.

Issue Description:

• When Line A gateway communication fails, the system does not automatically switch to Line B as expected.
• Communication is restored only after we manually change the Preferred Line from A to B.
• Automatic failover between the primary and standby gateways is not working after the upgrade.

[sbeadle]

This question would need more detail for the community to comment. e.g. device type and protocol being used. 

It may be more suitable to contact SE support directly.

[BevanWeiss]

It does sound like Schneider Electric support is likely the best port of call.

Otherwise... you've used the word 'gateway' a lot.  What do you mean by this for each of your uses?  It's not really a GeoSCADA term.

If you have Line A AND Line B, they MUST both be directly usable from all servers involved in the server redundancy.

Are these outstations using Radio links for communications?  And the outstations all have access to both Line A and Line B connections?  Are the connections serial, or are they IP based?

There was a bit of a change with IP comms in GeoSCADA 2017->2023 around consolidating IP connections ("merging connections" I think it was called)... potentially this is causing some issues with the configuration that you have for the outstation set.

You might need to provide full details for some of your outstations, and outstation sets, and channels.