• Replies 1 reply
  • Subscribers 583 subscribers
  • Views 233 views
  • Users 0 members are here
Options
Related

Multiple Citect SCADA 2016 Cluster Data Paths

Craig

Hi Aveva Support,

I have a PC on site that is configured as the Standby I/O. Trend, Report and Alarm Server for two separate Citect SCADA 2016 (Nov 2018 Patch) Clusters. The issue that I have got is that the Standby Trend Server for the 2nd Cluster does not log trend data when the 2nd Cluster Primary Trend Server is shut down. FYI, the 2nd Cluster Standby I/O, Alarm & Report (not used) Servers processes take over without problem when the 2nd Cluster Primary processes are shutdown. I suspect that issue with the 2nd Cluster Standby Trend Server process is that I cannot see (and please correct me if i am wrong) how i can define the 2nd Cluster Trend Server Primary and Standby data paths as this is obviously different for the 2nd Cluster. Is there a way of defining the Primary and Standby Trend Server Process data paths for the 2nd Cluster (or on a per Cluster basis) by manually editing the INI file. I cannot find a data path parameter where is can define this? Cheers Craig K.   

Parents
  • Hi Craig,
    If you are confident you have configured the 2nd Cluster Standby Trend Server correctly, then it could indeed be a setting which is stopping this Server from making connections to other Servers. Also check in Citect Studio the Topology > Computers to give you a nice overview of where the processes reside. Check that the ports you have defined are in fact open and not blocked by firewall or other network issues.
    You define which Clusters a Trend Server can connect to via the Citect.ini parameter [Trend]Clusters=Cluster1,Cluster2,etc...
    Also check that you have defined the same Server Password between each machine (configured during Computer Setup Wizard).
    The Kernel Window (you can access this via Runtime Manager, right click on 2nd Cluster Trend process, and select 'Kernel') can also help you diagnose which Client and Servers the particular Trend Server is connected to. From the main window of the Kernel, type "Page Table Tran". This will list all Connections for this Server. Check the state of each connection.
    Hope this information helps.
    Kind regards
    Olivier
Reply
  • Hi Craig,
    If you are confident you have configured the 2nd Cluster Standby Trend Server correctly, then it could indeed be a setting which is stopping this Server from making connections to other Servers. Also check in Citect Studio the Topology > Computers to give you a nice overview of where the processes reside. Check that the ports you have defined are in fact open and not blocked by firewall or other network issues.
    You define which Clusters a Trend Server can connect to via the Citect.ini parameter [Trend]Clusters=Cluster1,Cluster2,etc...
    Also check that you have defined the same Server Password between each machine (configured during Computer Setup Wizard).
    The Kernel Window (you can access this via Runtime Manager, right click on 2nd Cluster Trend process, and select 'Kernel') can also help you diagnose which Client and Servers the particular Trend Server is connected to. From the main window of the Kernel, type "Page Table Tran". This will list all Connections for this Server. Check the state of each connection.
    Hope this information helps.
    Kind regards
    Olivier
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.