On Azure cloud, the ILB is used to create the "Shared IP address" and to probe and route traffic to the LoadMaster instances. To allow 'public' access to the WUI of each LoadMaster, we recommend creating ILB NAT rules:

  • <SIP>:8441 maps to Node-1 port 8443
  • <SIP>:8442 maps to Node-2 port 8443
CAUTION: If using the HA pair awareness functionality in Kemp 360 Central, you must be able to probe the shared IP address on the WUI port (for example, <SIP>:8443). This requires an ILB inbound rule for 8443 to allow access to the back-end pool. However, the ILB does not allow a port used in a NAT rule to also be used in an inbound rule. Therefore, if you want to use the HA pair awareness in Kemp 360 Central, you must create a different set of NAT rules.

Inbound NAT rules provide a translation for management access into each of the LoadMasters in the back-end pool. Each LoadMaster does not require a Public IP Address (PIP). A unique port must be configured in an Inbound NAT rule for each LoadMaster. The example rules are the following:

Target

Port

Target Port

LoadMaster1 - WUI

8441

8443

LoadMaster1 – SSH

221

22

LoadMaster2 – WUI

8442

8443

LoadMaster2 – SSH

222

22

The LoadMaster uses port 22 and 8443 by default. The remaining port numbers listed above are recommended, but you can use other port numbers if needed.

To create the inbound NAT rules, continuing from the previous section follow the steps below:

  1. Click Add an inbound NAT rule.

  2. Under Add inbound NAT rule, complete the following fields:
    1. Enter a Name for the rule.
    2. Select Azure virtual machine as the Type.
    3. Select the Target virtual machine (in this example, the first LoadMaster is selected).
    4. Select the Network IP configuration.
    5. Select the Frontend IP address created earlier.
    6. Enter 8441 as the Frontend Port.
    7. Select Custom as the Service Tag.
    8. Enter 8443 as the Backend Port.
    9. Select TCP as the Protocol.
    10. Keep the remaining configuration as the default values and click Add.

  3. Create four inbound NAT rules based on the table provided earlier in this section.
  4. Click Next: Outbound Rule.
  5. Refer to the next section for details on setting up the outbound rules.