• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 1 reply
  • Subscribers 583 subscribers
  • Views 75 views
  • Users 0 members are here
Options
Related

Question about Server Redundancy with SCADA 2018 and 2020R2

Alan

i am in the middle of upgrade Citect 2018 to Plant Scada 2020R2, i have rolled most of my clients out to 2020R2 a few to go.

Primary Server is running 2020R2 Backup server is Citect 2018. i am unsure if redundancy is correct and want to know what are the key things to check to ensure redundancy between servers on different versions in the interim phase. earliest version in the ini file is set to 8100 , what other parameters and setting do i need to check.

my question is

my primary server (2020R2) project network addresses are in the machine name format AB1CD234EFG whereas my Backup server( 2018) is in the IP address format 10.11.12.13 

i have noticed some odd behavior with alarm handling between servers and clients when the primary is running.

should i change the 2018 to reflect machine name format and will it compile? thanks in advance.

  • +1

     Hi  ,

    The 2020R2 release starts supporting IPv6 in communications between SCADA nodes while the 2018 release is limited to use IPv4. When the hostnames are used in he project, they need to be resolved in IPs via GetIPAddresses(string hostname) that will return a list of IPv6 and IPv4 addresses for the hostname. So, you need to select IPv4 Addresses Only on each 2020R2 node on Computer Setup Wizard. Otherwise, these nodes will attempt to use IPv6 if IPv6 addresses are returned on top of the list, which could cause a problem in communication with the 2018 node.

    Check Network Model for details.

© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.