Create a cluster
We can configure multiple appliances into a cluster that shares configuration information and runtime information. Use the Cluster Configuration management page to administer cluster support for the appliance.
The Cluster Configuration page is not available in the LMI when the appliance runs in a Docker environment.
In a cluster, we must designate one of the appliances as the primary master. You can designate up to three subordinate masters, which are called the secondary, tertiary, and quaternary masters. The cluster services can fail over between these masters. The remaining appliances serve as nodes.
We must activate the primary and secondary masters of the cluster at the highest level of all the nodes in the cluster. For example, if any of the nodes have been activated with the Advanced Access Control module, the primary and secondary masters must also be activated for Advanced Access Control. Activation levels are validated when:
- A node joins the cluster. Validation ensures the primary and secondary masters are activated to at least the same level.
- A new primary or secondary master is set to ensure the activation level of the new master is at least at the same level of the current primary master.
By default, every appliance operates as a stand-alone cluster with only a single node. We can optionally configure a group of appliances into a cluster with multiple nodes.
For detailed information about clusters, see Cluster support.
Steps
- Select an appliance to be the primary master. We can choose any appliance as the primary master if it is not a member of another cluster. If the selected appliance is in another cluster, we must unregister it before we can appoint it as the primary master of a new cluster.
- On the General tab of the Cluster Configuration page:
- Select the Multinode option.
- Click Create Cluster.
- In the Create Cluster window, configure the Cluster Identifier, and then click Create Cluster.
For information about the Cluster Identifier, see Cluster general configuration reference.
- Save and deploy this update. The chosen appliance is configured as the primary master of a cluster that can contain multiple nodes.
- Export the cluster signature file on the primary master. The cluster signature file contains configuration information so that cluster members can identify and communicate with the primary master.
- Join appliances to the cluster by importing the cluster signature file on each appliance to become a cluster member. The process of joining an appliance to the cluster is a registration.
- Update the cluster configuration on the primary master. As part of the cluster configuration, we can define more masters from the pool of registered nodes. For information, see Failover in a cluster.
- Save and deploy the configuration changes. As a rule, try to limit the number of changes that are made to the cluster configuration in a single policy update.
Parent topic: Network Settings
Related reference