• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 498 views
  • Users 0 members are here
Options
Related

Running multiple clusters on a single server pairs on CitectSCADA 2018 R2

Chris

I had 3 clusters setup running fine in a test environment on V8.1 on the latest update. Today, I upgraded to v8.2, ever since, the alarms don't work, be the Example_SA project alarms work fine. I looked in the trace logs for the alarm server, there are countless errors with refused connections, the firewall is disabled on my machine too. It's not a privilege issue either.

2019-09-11 13:44:22.941 -07:00 21256 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57459 --> 127.0.0.1:2082 #1] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:2082
2019-09-11 13:44:25.168 -07:00 27936 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57472 --> 127.0.0.1:12082 #2] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:12082
2019-09-11 13:44:27.424 -07:00 15584 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57492 --> 127.0.0.1:22082 #3] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:22082

I had to manually define the port numbers 12080 and 22082 for cluster 2 and 3 respectfully. Again, this work perfectly in v8.1.

I also get a hardware alarm from each of the running Alarm servers - Data Not Ready.

Parents
  • I am using my local machine as a testing node for our upcoming deployment of a new SCADA system for our new site. Because we have two units (with identical tag names and screens) plus some common systems, we choose to go with three clusters. We will still only have two servers, physical nodes, on site once everything in in-place. So, I have setup the project to act like the primary server for all processes (I/O, Trend, Alarm, Report). SECVS002 in the primary server name and the network address is set to "localhost", SECVS004 is the secondary server and does not exist yet.

    The project configuration didn't change from testing on v8.1 to v8.2. I have in the past always set the Runtime to "Stand-Alone" in the Computer Setup Wizard, when I test/develop these new systems. When I run the project as "Stand-Alone", the Alarms don't work, as if the alarm server can't connect to the I/O server, this issue goes away when I run the project as "Networked". I don't have this issue when running the Example_SA project as "Stand-Alone".

    No IO problems, trending works fine, just no alarms. And I have discovered the PC name issue early on, so that was already remedied.
Reply
  • I am using my local machine as a testing node for our upcoming deployment of a new SCADA system for our new site. Because we have two units (with identical tag names and screens) plus some common systems, we choose to go with three clusters. We will still only have two servers, physical nodes, on site once everything in in-place. So, I have setup the project to act like the primary server for all processes (I/O, Trend, Alarm, Report). SECVS002 in the primary server name and the network address is set to "localhost", SECVS004 is the secondary server and does not exist yet.

    The project configuration didn't change from testing on v8.1 to v8.2. I have in the past always set the Runtime to "Stand-Alone" in the Computer Setup Wizard, when I test/develop these new systems. When I run the project as "Stand-Alone", the Alarms don't work, as if the alarm server can't connect to the I/O server, this issue goes away when I run the project as "Networked". I don't have this issue when running the Example_SA project as "Stand-Alone".

    No IO problems, trending works fine, just no alarms. And I have discovered the PC name issue early on, so that was already remedied.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.