Cluster configuration rules

When we are configuring a cluster of ISAM appliances, consider the following rules that govern cluster configuration. General notes:

• Try to limit the number of changes that are made to the cluster configuration in a single policy update.
• After you save the policy changes, we must deploy the updates for the changes to take effect.

• Cluster architecture rules
  The architecture of a cluster, including the appointment of masters, is governed by numerous rules.
• Cluster node availability
  If a node is unavailable when you update the cluster configuration, it contacts the primary master to get the updated configuration information when it comes back online. If the primary master is offline at the same time as the secondary master, the primary master comes back online with read-only databases until the secondary master is available.
• First management interface
  In a clustered environment, the IP address of the first management interface is used as the node identifier. For this reason, a static IP address must be assigned to the first management interface of the appliance.
• Cluster registration
  Before you register or unregister a node in a cluster, consider these registration rules.
• Cluster ports
  When configuring an appliance cluster, we are required to specify the starting port number for a range of ports to be dedicated to the services that are provided by the cluster.

Parent topic: Cluster support