To ensure complete system redundancy, the NSX Advanced Load Balancer Controller must be highly available. To provide high availability (HA) for the NSX Advanced Load Balancer Controller, add 2 additional NSX Advanced Load Balancer Controller nodes to create a 3-node NSX Advanced Load Balancer Controller cluster.

HA of the NSX Advanced Load Balancer Controller requires 3 separate Controller instances, configured as a 3-node cluster. Start with a single-node NSX Advanced Load Balancer Controller deployment and use the following steps to add 2 additional NSX Advanced Load Balancer Controller nodes to form a 3-node cluster.

Note:

If the cluster is already deployed and you want to modify its node membership or dismantle the cluster, click here instead.

Prerequisites for Cluster Deployment

Leader node

  • Leader can be any single node with configuration or without configuration.

  • Leader can have NSX Advanced Load Balancer Service Engines (SEs) connected.

  • The node must have a static IP address.

    • Using DHCP can cause issues when nodes reboot and their IP addresses change.

    • The current release does no support use of hostnames for cluster configuration.

Follower nodes

  • An NSX Advanced Load Balancer Controller cluster can have 3 nodes, 1 leader node and 2 follower nodes.

  • Follower nodes are expected to have no configuration, and no changes to the NSX Advanced Load Balancer login credentials.

  • Follower nodes are expected to be running the same NSX Advanced Load Balancer base+patch version as the leader.

  • Follower typically is a VM or Mesos container created from the the NSX Advanced Load Balancer Controller installation package.

  • Each follower node must have a static IP address.