This section describes how to add a LoadMaster High Availability (HA) pair that operates behind NAT to LoadMaster 360 using pooled licensing.

Note: SPLA (Service Provider License Agreement) licenses are not supported for this workflow.

Ensure the following before starting:

  • You have three public NAT IP addresses mapped (1:1) to three internal IP addresses:

    • Shared IP address

    • HA1 (First Mode) IP address

    • HA2 (Second Mode) IP address

  • You know which HA mode each IP address is assigned. You can get this by logging in to the individual IP addresses, going to Local Administration > HA Parameters, and noting the HA mode. It will display as either HA (First) Mode or HA (Second) Mode.

  • Switch to Preferred Server is set to Prefer First HA.

  • If you are using Kemp 360 Central, remove the license from there before proceeding.

IP address mapping example

Use this table as a reference. Note the mapping between your internal and public NAT IP addresses.

LoadMaster Public NAT IP address Local IP address HA Status
Shared IP address 203.0.113.100 10.0.0.100
HA (First) Mode 203.0.113.101 10.0.0.101 Active
HA (Second) Mode 203.0.113.102 10.0.0.102 Standby

Step 1: Remove the existing license

Start with the standby device.

On the LoadMaster:

  1. Log in to the standby device.
  2. Go to System Configuration > System Administration > License Management.
  3. Remove the license:
    • Select Online Licensing from the drop-down list.

    • Enter your Progress ID credentials.

    • Click Kill License.

Step 2: Add the LoadMaster to LoadMaster 360 (using NAT)

To add the LoadMaster to LoadMaster 360, follow these steps:

  1. Log in to LoadMaster 360.
  2. Go to Infrastructure > Device Inventory.
  3. Click Add Device > Add LoadMaster.
  4. Click Activate a new LoadMaster.
  5. Select a Connector that has network reachability to the LoadMaster.
  6. Click Next.
  7. Under the LoadMaster tab, select LoadMaster type > LoadMaster Single.
  8. Enter a Name for the device (for example, LoadMaster HA NAT).
  9. Select NAT as the Interface Mode.
  10. Enter the required details:
    • IPv4 address (standby device)

    • Public IPv4 address for LoadMaster (NAT mapping)

    • Port (if not using default 443)

    • Public IPv4 address for Connector (Optional)

  11. Enter a new password in the Create password field for the bal administrator user.
    Note: The password must be at least 8 characters long.
    Note: The default administrator user on all LoadMasters is called bal.
  12. Re-enter the new password in the Confirm password text box.
  13. Use the Schedule enabled toggle to enable or disable backup scheduling for this LoadMaster.
  14. If backup scheduling is enabled, select either Every day or Custom schedule (for example, weekdays only), and set the backup execution time.
  15. Click Next.

Step 3: Initial provisioning

The device will be:

  • Onboarded

  • Licensed

  • Displayed as part of an HA pair under your chosen name

Note: At this stage, internal IP addresses will still be shown. Wait approximately 5 minutes to give the Connector time to configure the required settings on the LoadMaster. The status for these devices may continue to show as unreachable. After 5 minutes, continue with Step 4.

Step 4: Update the IP addresses to Public NAT IP addresses

This step explains how to update the internal LoadMaster IP addresses to their mapped Public NAT IP addresses in LoadMaster 360, ensuring proper device reachability and health status.

  1. Go to Infrastructure > Device Inventory.

  2. Select the device and click Edit.

  3. Modify the IP addresses, ensuring you enter the correct Public NAT address for each device. Refer to your mapping table and enter the Public NAT address for:
    • Shared IP address

    • HA first IP address

    • HA second IP address

  4. Enter the bal credentials, then click Next.

Wait for the device to show as reachable. This process may take several minutes.

After a short period:

  • Devices will return to a healthy state.

  • Public IP addresses will be reflected correctly.

Note: Reboot the standby device at this point to ensure the new license is correctly applied. Wait until the LoadMaster HA status shows as green/green from the LoadMaster Web User Interface (WUI) before proceeding.

Step 5: Force HA Failover

  1. Access the LoadMaster through the shared IP address.
  2. Log in.
  3. Go to System Configuration > HA Parameters.
  4. Set the standby device as the Preferred Master.
  5. Wait for both devices to show as healthy.

Step 6: Repeat for the second LoadMaster

Now repeat the process for the second LoadMaster (which is now in standby after the failover):

  1. Add the second LoadMaster in LoadMaster 360 using a different name.
  2. Repeat the steps in the Step 1, Step 2, and Step 3 sections above. You do not need to repeat the steps in Step 4.

If everything works correctly, you will see both devices as an HA pair within LoadMaster 360.

Verify the configuration

After completing all steps, confirm the following:

  • Both devices appear as a healthy HA pair in Infrastructure > Device Inventory.

  • Public NAT IP addresses are correctly displayed for all three addresses (Shared, HA First, HA Second).

  • The HA status shows green/green in the LoadMaster WUI.

  • Pooled licensing is active and both devices are consuming licenses from the pool.

Troubleshooting

Issue Possible cause Resolution
Device shows as "unreachable" after Step 3 Connector has not finished configuring the LoadMaster Wait 5 minutes and check again. Ensure the Connector has network reachability to the LoadMaster.
Public NAT IP addresses not reflected after Step 4 Incorrect IP address mapping entered Verify the mapping table. Edit the device and re-enter the correct Public NAT addresses.
License blob error SKU mismatch or unsupported LoadMaster version Verify the LoadMaster SKU and firmware version. Contact Support if the issue persists.
HA status not green/green after reboot The device is still applying the license Wait a few minutes. If the issue persists, verify the HA parameters on both devices in the WUI.