# Pointing OPC UA tags at the primary CPU of a Hot Standby pair wheneach rack has its own OPC UA server

**URL:** <https://forum.inductiveautomation.com/t/pointing-opc-ua-tags-at-the-primary-cpu-of-a-hot-standby-pair-wheneach-rack-has-its-own-opc-ua-server/117865>\
**Category:** Ignition\
**Created:** [November 17, 2026, 11:54am UTC](https://forum.inductiveautomation.com/t/pointing-opc-ua-tags-at-the-primary-cpu-of-a-hot-standby-pair-wheneach-rack-has-its-own-opc-ua-server/117865 "2026-11-17T11:54:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![davi.soares](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@davi.soares](https://forum.inductiveautomation.com/u/davi.soares)\
**Post date:** [November 17, 2026, 11:54am UTC](https://forum.inductiveautomation.com/t/pointing-opc-ua-tags-at-the-primary-cpu-of-a-hot-standby-pair-wheneach-rack-has-its-own-opc-ua-server/117865/1 "2026-11-17T11:54:26Z")

</div>

Ignition 8.1.49, redundant gateway pair.

We have a redundant PLC pair (Hot Standby). The CPU has a floating IP that  
follows the primary, so anything talking straight to the CPU rides through a  
switchover without noticing. The OPC UA server, though, is a module sitting  
in each rack, and those modules do not share that floating IP — each has its  
own fixed IP and its own endpoint. Ignition connects to the modules.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/a/ca2107baf7cc0bc6d6c6e6ea94e7ec73c549ea0a.png)

Reads work against either server. Writes only work against the one in the  
rack holding the primary CPU. So the gateway has to keep its tags pointed at  
the right server, and which one is right changes on every switchover.

Configuring the second endpoint as the failover of a single connection  
covers the loss of a module, but not the case where both servers are healthy  
and only the primary role moved.

What we ended up doing:

- Two independent OPC UA connections, one per server, no failover between  
them.
- Tags reading the Hot Standby status from each server.
- An expression tag that resolves which connection should be in use.
- A parameter in every UDT holding the OPC server name, with every OPC  
member tag binding its OPC Server property to that parameter.
- A reference tag in each UDT that follows the expression tag and writes the  
resolved name into its own instance parameter on value change.

It works, but it means that on every switchover around 1,200 UDT instances  
rewrite a configuration parameter at runtime, reconfiguring something like  
27,000 tags. The writes are asynchronous with no confirmation and no retry.

It ran clean for about a year. Recently we had two events where part of the  
tag tree stayed on the standby server even though the expression tag had  
already resolved correctly — values visible, commands dead. Restarting the  
tag and both connections brought it back.

What we would really want is to express this at the connection level. The  
server module reports a ServiceLevel of 255 when it is the primary and lower  
when it is the standby, so something along the lines of "fail over when  
ServiceLevel \< 255" would let the driver pick the endpoint and leave the  
tags alone. ServiceLevel is just the angle we thought of — any approach that  
avoids changing tag configuration at runtime would do.

Has any of you run into a similar problem? Curious how others handle  
redundant PLC pairs where the OPC UA server does not follow the primary.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 17, 2026, 1:05pm UTC](https://forum.inductiveautomation.com/t/pointing-opc-ua-tags-at-the-primary-cpu-of-a-hot-standby-pair-wheneach-rack-has-its-own-opc-ua-server/117865/2 "2026-11-17T13:05:44Z")

</div>

My Integration Toolkit offers a partial solution with its [Read Substitution Tag Action](https://www.automation-pros.com/toolkit/doc/actors.html#read-substitution-action), which avoids the tag reconfiguration via a live data path switch. (You would have a primary and fallback tags, and the fallback value would flow through the primary based on your chosen boolean condition.)

I've been contemplating making a fully writable version.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [November 17, 2026, 3:18pm UTC](https://forum.inductiveautomation.com/t/pointing-opc-ua-tags-at-the-primary-cpu-of-a-hot-standby-pair-wheneach-rack-has-its-own-opc-ua-server/117865/3 "2026-11-17T15:18:53Z")

</div>

Ignition 2027 has a new, dedicated OPC UA connection type for servers that support OPC UA redundancy.

This will be the only truly supported mechanism for connecting to OPC UA servers that support OPC UA redundancy. Anything else will continue to be scripted workarounds.
