• Replies 3 replies
  • Subscribers 584 subscribers
  • Views 153 views
  • Users 0 members are here
Options
Related

CitectScada 2018 R2 Clustering Scenarios

Steve

Hello,

I am hoping to get some assistance with clustering. I am trying to do some testing before fully deciding if and or how to cluster our system. We have a large alarm database and I have been told that putting our "SOE" events in their own cluster would be beneficial. 

I have done some testing and created a new cluster and added the SOE alarm records to the new cluster. The issue I have now is that the SOE digital alarm records are based on variable tags that I need to keep in the original cluster. 

Am I able to have a digital alarm in a different cluster than the variable tag its triggered off of? 

Hoping to get any help or advice possible.

Thanks,

Steve

Parents
  • Hi ,

    It is possible to link a digital alarm in ClusterX to a variable tag in ClusterY. No problem. Basically the alarm server in ClusterX will subscribe to the Variable Tag in ClusterY.

    When running the computer setup wizard, just ensure that each Server Process is connected to the relevant clusters. This is controlled by the Citect.ini parameter:
    [<ServerType>.<ClusterName>.<ServerName>]
    Clusters=<ClusterName1>,<ClusterName2>,...

    With regards to setting up a dedicated cluster, just to handle alarm (and SOE) processing, it depends. If your system size is quite large, it will start to make sense to split things up across clusters. It is usually best to keep logical areas of a system contained within their own Cluster (where possible). But it is also possible to share data across clusters. I guess it is really flexible and just depends on what will work best for you in terms of configuration and management.

    In my experience, I have found the sweet spot for the total number of alarms is 50,000 per cluster.

    Since the SOE is stored in a ClearSCADA database, there are some parameters which can be tuned to adjust the file granularity and performance of the DB. It is best to engage AVEVA Support to get help doing this. It will depend on the number of alarm tags, the rate of change, and a few other factors.

    Kind regards
    Olivier
Reply
  • Hi ,

    It is possible to link a digital alarm in ClusterX to a variable tag in ClusterY. No problem. Basically the alarm server in ClusterX will subscribe to the Variable Tag in ClusterY.

    When running the computer setup wizard, just ensure that each Server Process is connected to the relevant clusters. This is controlled by the Citect.ini parameter:
    [<ServerType>.<ClusterName>.<ServerName>]
    Clusters=<ClusterName1>,<ClusterName2>,...

    With regards to setting up a dedicated cluster, just to handle alarm (and SOE) processing, it depends. If your system size is quite large, it will start to make sense to split things up across clusters. It is usually best to keep logical areas of a system contained within their own Cluster (where possible). But it is also possible to share data across clusters. I guess it is really flexible and just depends on what will work best for you in terms of configuration and management.

    In my experience, I have found the sweet spot for the total number of alarms is 50,000 per cluster.

    Since the SOE is stored in a ClearSCADA database, there are some parameters which can be tuned to adjust the file granularity and performance of the DB. It is best to engage AVEVA Support to get help doing this. It will depend on the number of alarm tags, the rate of change, and a few other factors.

    Kind regards
    Olivier
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.