The following prerequisites must be met before proceeding to a high availability configuration:

  • An Azure Resource Manager (ARM) (V2) Virtual Network added to Azure to place the LoadMaster VMs
  • Application VMs deployed in Azure in the Virtual Network
  • An Azure Internal Load Balancer deployed to create the high availability pair
  • Two LoadMaster VMs deployed on the same Virtual Network as the Application VMs
  • Both LoadMasters should be configured to be part of an availability set

The following diagram provides overview of the configuration described above:

To configure high availability using the LoadMaster, the following configuration must be in place:

  • Application VMs are installed and configured
  • LoadMaster for Azure VMs are installed and configured
  • Important: The HA Check Port must be set to the same port on both the active and standby units for HA to work correctly. The same port must be configured as the probe port on the Internal Load Balancer.
  • The following management Load Balanced NAT Rules may be needed to access the LoadMasters:
    • TCP Port 22 for SSH access
    • TCP Port 8443 for Management Web User Interface (WUI) access
    • Additional Load Balanced Rules for any traffic that is being transmitted through the LoadMaster
Note: If using Kemp 360 Central, you must configure special NAT rules.

Use this table to record the necessary information required to create the LoadMaster Pair in Azure:

Fields Required for creation of LoadMaster Pair

Primary LoadMaster Name

Secondary LoadMaster Name

Pricing Tier

Password for LoadMasters

Availability Service Name

Resource Group Name

Virtual Network

Internal Load Balancer Name

Internal Load Balancer Public IP Address (PIP), if required

Note: It is not possible to bond interfaces on Azure LoadMasters.