# Help with B&R Redundant System (X20CP3684) – Modbus\_TCP\_Any and OPC UA Cluster IP Issues - AS version 6.1.1.14

**URL:** <https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861>\
**Category:** B&R Software & Runtime\
**Tags:** automation-studio, opc-ua, modbus\
**Created:** [October 31, 2025, 6:26am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861 "2025-10-31T06:26:46Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Win\_Lai\_Aung](https://avatars.discourse-cdn.com/v4/letter/w/FF8800/32.png) [@Win\_Lai\_Aung](https://community.br-automation.com/u/Win_Lai_Aung)\
**Post date:** [October 31, 2025, 6:26am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/1 "2025-10-31T06:26:46Z")

</div>

Hi everyone,

I’m new to B&R and currently setting up a redundant system using **X20CP3684** controllers. I’m facing two issues:

1. **Modbus\_TCP\_Any:** It only works on either the primary or the secondary controller — never both at the same time. When one is OK, the other reports an error.

2. **OPC UA Server:** I want to provide data points to another monitoring system (Tridium Niagara) using the **cluster IP** , but it only works when I enter the **primary IP**. It doesn’t seem to respond through the cluster IP.

Could this be due to a configuration issue, or is there something I’m missing in the redundancy setup?

Any guidance or examples would be greatly appreciated.  
Thank you for your help!

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/e/e43385613b58a794ed59e776a0b0391412df7202.png)

OPC Ua Configuration

ClientServerConfiguration   
OPC UA Client/Server Enabled   
Network   
TCP port number 4840   
Facets   
Auditing Server Facet Disabled   
MessageSecurity   
SecurityPolicies   
None Enabled   
Aes128 Sha256 Rsa Oaep Enabled   
Basic256 Sha256 Enabled   
Modes   
Sign Enabled   
Sign and encrypt Enabled   
Authentication   
SecurityPolicies   
Aes128 Sha256 Rsa Oaep Enabled   
Basic256 Sha256 Enabled   
Authentication Methods   
Anonymous Enabled   
Username Enabled

---

<div class="post-metadata">

**Author:** ![tommi.piiparinen](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/tommi.piiparinen/32/2183_2.png) [@tommi.piiparinen](https://community.br-automation.com/u/tommi.piiparinen)\
**Post date:** [November 7, 2025, 11:30am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/2 "2025-11-07T11:30:49Z")

</div>

1. The Modbus\_TCP\_Any is only executed on the active PLC, which is why the other one reports an error.

2. OPC UA server should be accessible through the cluster IP and should not need any specific configuration due to controller redundancy.

Can you access any other services on the PLCs through the cluster IP? System Diagnostics Manager for example?

---

<div class="post-metadata">

**Author:** ![Win\_Lai\_Aung](https://avatars.discourse-cdn.com/v4/letter/w/FF8800/32.png) [@Win\_Lai\_Aung](https://community.br-automation.com/u/Win_Lai_Aung)\
**Post date:** [November 23, 2025, 10:05am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/3 "2025-11-23T10:05:06Z")

</div>

Hi, yes i can access SDM via web with cluster IP and can ping as well

below image is how i set up to read from B&R, i have set up user in B&R. But it just gives me Device not initialized error.

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/7/781764faaa4fd1702c15c66f30cc841e3a92a30a.png)

---

<div class="post-metadata">

**Author:** ![kovarj](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/kovarj/32/537_2.png) [@kovarj](https://community.br-automation.com/u/kovarj)\
**Post date:** [December 17, 2025, 12:14pm UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/4 "2025-12-17T12:14:22Z")

</div>

Hi @Win_Lai_Aung, what is the status or solution of your topic? Can you update us?

---

<div class="post-metadata">

**Author:** ![aditya.shwetank](https://avatars.discourse-cdn.com/v4/letter/a/FF8800/32.png) [@aditya.shwetank](https://community.br-automation.com/u/aditya.shwetank)\
**Post date:** [July 13, 2026, 11:58pm UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/5 "2026-07-13T23:58:14Z")

</div>

Hi Guys,

Were you able to resolve this issue? I am experiencing a very similar problem with a B&R redundant PLC system.

Niagara can successfully connect to the OPC UA server using the individual Primary and Secondary PLC IP addresses. However, when I use the Cluster IP address, the connection fails with the following error:

`Failed to create session channel to server: opc.tcp://192.168.60.220:4840 [http://opcfoundation.org/UA/SecurityPolicy#None,None]`

Could you please share what configuration or settings you changed to make OPC UA communication work through the Cluster IP?

Any guidance would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![kovarj](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/kovarj/32/537_2.png) [@kovarj](https://community.br-automation.com/u/kovarj)\
**Post date:** [July 14, 2026, 5:08am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/6 "2026-07-14T05:08:10Z")

</div>

B&R’s redundancy docs say the cluster IP is used by the active CPU, but **OPC UA via cluster IP is not synchronized between the two rCPUs** and may need the client to **re-establish the connection** after a switchover. If you need stable access to both sides, B&R recommends **separate direct-IP connections to the primary and secondary PLCs** instead of relying on the cluster IP for OPC UA failover.

> **[B&R Online Help](https://help.br-automation.com/#/en/6/automationruntime/redundancy/general/limitations.html)**

If the cluster IP works for ping/SDM but not OPC UA, the network side is probably fine and the issue is client endpoint/session handling rather than a PLC redundancy configuration problem.

---

<div class="post-metadata">

**Author:** ![aditya.shwetank](https://avatars.discourse-cdn.com/v4/letter/a/FF8800/32.png) [@aditya.shwetank](https://community.br-automation.com/u/aditya.shwetank)\
**Post date:** [July 14, 2026, 7:51am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/7 "2026-07-14T07:51:56Z")

</div>

Hi Jaroslav,

Thank you for the clarification. I carried out an additional redundancy switchover test and observed something important.

Niagara was connected to the OPC UA server using the direct address:

opc.tcp://192.168.60.221:4840

Initially, the CPU at .221 was the active Primary CPU. I then performed a redundancy switch in Automation Studio, after which the CPU at .222 became active and the CPU at .221 became standby.

During the switchover, the Niagara OPC UA device briefly reported a communication fault. However, after approximately five seconds, the same OPC UA connection to .221 automatically returned to a healthy state and continued communicating, even though .221 was now the standby CPU.

Therefore, the direct IP OPC UA connection appears to remain available regardless of whether that particular rCPU is active or standby.

The unresolved issue is specifically the Cluster IP:

Direct IP .221:4840 connects successfully and automatically recovers after a redundancy switchover.  
Cluster IP .220:4840 cannot establish the initial OPC UA session at all.  
The Cluster IP is reachable through ping, SDM and Automation Studio.  
With SecurityPolicy None and either Anonymous or username/password authentication, Niagara reports:

Failed to create session channel to server: opc.tcp://192.168.60.220:4840 [SecurityPolicy#None,None]

Could you please confirm whether an initial OPC UA connection through the Cluster IP is expected to work?

---

<div class="post-metadata">

**Author:** ![kovarj](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/kovarj/32/537_2.png) [@kovarj](https://community.br-automation.com/u/kovarj)\
**Post date:** [July 14, 2026, 8:10am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/8 "2026-07-14T08:10:44Z")

</div>

I have never tested it. But based on this reply [Help with B&R Redundant System (X20CP3684) – Modbus\_TCP\_Any and OPC UA Cluster IP Issues - AS version 6.1.1.14 - #2 by tommi.piiparinen](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/2) yes. Since everything else is working, I think you will need to get in touch with your local support and provide/show them your project and configuration. This is something what we can not do here in community.

---

<div class="post-metadata">

**Author:** ![aditya.shwetank](https://avatars.discourse-cdn.com/v4/letter/a/FF8800/32.png) [@aditya.shwetank](https://community.br-automation.com/u/aditya.shwetank)\
**Post date:** [July 14, 2026, 1:03pm UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/9 "2026-07-14T13:03:47Z")

</div>

All good Jaroslav, thanks for the help. I got it working.

---

<div class="post-metadata">

**Author:** ![kovarj](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/kovarj/32/537_2.png) [@kovarj](https://community.br-automation.com/u/kovarj)\
**Post date:** [July 14, 2026, 1:14pm UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/10 "2026-07-14T13:14:23Z")

</div>

and what was the problem?

---

<div class="post-metadata">

**Author:** ![aditya.shwetank](https://avatars.discourse-cdn.com/v4/letter/a/FF8800/32.png) [@aditya.shwetank](https://community.br-automation.com/u/aditya.shwetank)\
**Post date:** [July 14, 2026, 1:47pm UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/11 "2026-07-14T13:47:04Z")

</div>

Hi Jaroslav,

- I configured a hostname for the B&R cluster, in addition to the cluster IP.
- On the Niagara server, I mapped that hostname to the cluster IP in the Windows.
- In Niagara, I used the hostname in the OPC UA endpoint instead of entering the cluster IP directly.
- For the initial setup, I used security mode as None with Anonymous authentication.
- In Automation Studio, I assigned the Anonymous user to an everyone role and enabled the required OPC UA browse/read permissions for that role.
- I also added the everyone role under the advanced OPC UA Anonymous Authorization settings.

After rebuilding and transferring the configuration to both redundant CPUs, Niagara connected successfully through the cluster hostname and the OPC UA points became available.

---

<div class="post-metadata">

**Author:** ![kovarj](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/kovarj/32/537_2.png) [@kovarj](https://community.br-automation.com/u/kovarj)\
**Post date:** [July 15, 2026, 5:45am UTC](https://community.br-automation.com/t/help-with-b-r-redundant-system-x20cp3684-modbus-tcp-any-and-opc-ua-cluster-ip-issues-as-version-6-1-1-14/8861/12 "2026-07-15T05:45:52Z")

</div>

thanks for sharing 🙂
