Goals and Symptoms

This article will list considerations for configuring multiple clusters in a single PowerLogic SCADA (PLS) project.

Causes and Fixes

1. The following names should be unique system-wide (across all Clusters):

• • Cluster names
  • Network Address names
  • Server (I/O, Alarm, Trend, Report) names
  • I/O Device names

• 
  5. Run the Computer Setup Wizard to assign each server component to the proper cluster. Each server component must belong to one cluster. Assign the Client to ALL clusters.
  • 
  6. Rules for Server Components:
  • • Each cluster can contain only one pair of redundant Alarm Servers. They need to reside on different machines.
    • Each cluster can contain only one pair of redundant Reports Servers. They need to reside on different machines.
    • Each cluster can contain only one pair of redundant Trends Servers. They need to reside on different machines.
    • Each cluster can contain an unlimited number of I/O Servers.
  
  6. Graphic Page names should be unique across all projects and the Cluster should be specified in the page properties for each screen.
  • Failure to do this could result in screens showing data only from one cluster (if tags are not being passed in the clusterName.tagName format).
  
  7. Cicode Function names should be unique across the system and function calls should pass the Cluster Name to the function.
  This is an optional parameter in single cluster systems, but required for multi-cluster.
  
  8. When passing tags to a function, genie, popup, etc., tags should be passed in the clusterName.TagName format.