We have configured our system with server redundancy.
To allow OPC UA clients on other PCs to connect to the server, we reconfigured the OPC UA server settings.
After completing the configuration, we tested the redundancy setup by rebooting the master server. During the reboot, the OPC UA connection on the backup server showed a FAULTED status.
Once the master server finished rebooting, the OPC UA connection on the backup server automatically returned to CONNECTED status.
Please refer to the settings below and advise on how to resolve this issue.
error message:
java.lang.Exception: session inactive: id=NodeId{ns=1, id=Session:44605481-3992-4d00-b685-f9c46c2ce530} name=ignition[EPMS_SERVERA]_Ignition OPC UA Server_1748342702302
at com.inductiveautomation.ignition.gateway.opcua.client.connection.OpcUaConnection$MiloSessionActivityListener.onSessionInactive(OpcUaConnection.kt:499)
at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$null$39(SessionFsmFactory.java:611)
at java.base/java.util.concurrent.CopyOnWriteArrayList.forEach(Unknown Source)
at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$configureActiveState$40(SessionFsmFactory.java:611)
at com.digitalpetri.strictmachine.dsl.ActionBuilder$PredicatedTransitionAction.execute(ActionBuilder.java:119)
at com.digitalpetri.strictmachine.StrictMachine$PollAndEvaluate.lambda$run$0(StrictMachine.java:242)
at java.base/java.util.ArrayList.forEach(Unknown Source)
at com.digitalpetri.strictmachine.StrictMachine$PollAndEvaluate.run(StrictMachine.java:227)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
8.1.43 (b2024082010)
Azul Systems, Inc. 17.0.11
Try these OPC UA server settings:
Bind Address: 0.0.0.0
Backup Bind Address: 0.0.0.0
You can leave the addition of the IP address to the Endpoint Addresses and Backup Endpoint Addresses setting if the servers aren't picking up that IP address automatically for some reason.
Get rid of all your changes to the OPC UA Connections - they aren't necessary, the connections already point to localhost which is everything needed.
Restart both Gateways after making these changes.
1 Like
The server settings have been updated as follows.
I configured the OPC UA client as shown, but when I restart the master server, the OPC connections on the backup server still show as faulted.
Below are the connection endpoint settings for the OPC UA client.
You didn't use the bind addresses Kevin specified. 
2 Likes
Wasn't Kevin referring to setting the endpoint to the master IP 10.20.52.51 and the backup IP 10.20.52.53?
No. "Endpoint Address" and "Bind Address" two very different things. Kevin doesn't make terminology mistakes.
1 Like
Updated Bind Address settings
Updated Backup bind Address Settings
Isn't this the setting Kevin was referring to?
Yes. What do his instructions say to use?
{My Bold.}
Does he mean that the Bind Address and Backup Bind Address should be set to the same IP? I'm not sure where I made a mistake.
0.0.0.0 is the wildcard address. It means bind to (listen on) all IP addresses in the system.
This is documented.
You may need to have IA support looking over your shoulder.
Oh, you meant to set it to 0.0.0.0. I had thought it meant to set it to the specific IP address I was using.
I will reconfigure it and test once more.
We are trying to connect to this redundant PC via OPC connection from another workstation other than the redundant server itself. The current configuration is as follows:
In this case, the connection to the Master server (10.10.51.51) works fine, but when the Master server is shut down, the connection to the Backup server fails.
