Synchronization across cluster nodes

All configurations on a NetScaler cluster are performed on the cluster IP address, which is the management address of the cluster. The cluster node owns the cluster IP address that is referred to as the cluster configuration coordinator (CCO) as shown in the following figure:

Cluster CCO

The configurations that are available on the CCO are automatically propagated to the other cluster nodes and therefore all cluster nodes have the same configurations.

  • NetScaler allows only a few configurations to be performed on individual cluster nodes through their NSIP address. In these cases, you must ensure configuration consistency manually across all nodes in the cluster. These configurations are not propagated across the other cluster nodes. For more information on operations supported on each cluster node, see Operations Supported on Individual Cluster Nodes.
  • The following commands when ran on the cluster IP address are not propagated to other cluster nodes:
    • shutdown. Shuts down only the configuration coordinator.
    • reboot. Reboots only the configuration coordinator.
    • rm cluster instance. Removes the cluster instance from the node that you are running the command on.
  • For a command to propagate to other cluster nodes:
    • The quorum must be configured on the cluster instance.
    • Most the cluster quorum with (n/2 + 1) of the cluster nodes must be active for the cluster to be operational.
    • A cluster can run with a minimum number of nodes when the majority rule (n/2 + 1) is relaxed.

When a node is added to a cluster, the configurations and the files (SSL certificates, licenses, DNS, and so on) that are available on the CCO are synchronized to the newly added cluster node. When an existing cluster node, that was intentionally disabled or that had failed, is once again added, the cluster compares the configurations available on the node with the configurations available on the CCO. If there is a mismatch in configurations, the node is synchronized by using one of the following:

  • Full synchronization. If the difference between configurations exceeds 255 commands, all the configurations of the CCO are applied to the node that is rejoining the cluster. The node remains operationally unavailable during the synchronization.
  • Incremental Synchronization. If the difference between configurations is less than or equal to 255 commands, only the configurations that are not available are applied to the node that is rejoining the cluster. The operational state of the node remains unaffected.


You can also manually synchronize the configurations and files. For more information, seeSynchronizing Cluster Configurations and Synchronizing Cluster Files.

Synchronization across cluster nodes

In this article