Dear Community Members,
We are currently experiencing a technical issue that is affecting the ability to create new posts. Our team is actively investigating the root cause and working to resolve it as quickly as possible. We apologize for the inconvenience and appreciate your patience.
SE Community Team!
OPC UA on Duty Standby Servers Failover handling
Industry Automation and Control Forum
This forum is addressing industrial automation design & engineering, operations, asset performance, cyber security and digital transformation for Plants & Machines.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-06-1307:27 AM
OPC UA on Duty Standby Servers Failover handling
Hi there,
We have duty / standby servers running GeoSCADA with healthy OPC UA communications to the Turbines server. Everything is running smoothly with the communications until we reach the Duty / Standby checks.
If we shutdown Server A, Server B loses its connection to the Turbine server via the OPC UA. We believe that the Server B certificate and private key are still pointing to the Server A hence when the Server A is down Server B fails.
Is it possible to assign separate client certificates to A and B while they are accessing the same GeoSCADA database? If one fails, the other one picks its certificate and communicates with the Turbine Server.
If anyone happen to come across this situation, could someone kindly provide help?