Configuring the Azure load balancer - BlueCat Integrity - 26.1.0

Before creating an xHA pair with Azure DNS/DHCP Servers, you must first set up an Azure load balancer for directing traffic. With the Azure load balancer, we will configure frontend IP addresses that will serve as the client-facing services and management interfaces of the xHA pair. Traffic sent to frontend IP addresses (virtual interfaces for the xHA pair) is directed to backend pools (individual BDDS interfaces) based on load balancing rules.

1. From the Azure portal home page, select Create a resource.
2. Search Load Balancer, then select Create > Load Balancer on the panel for the Load Balancer Microsoft Azure Service.
3. On the Basics tabs, fill in the following parameters:
   1. Subscription—select your Azure subscription from the drop-down menu.
   2. Resource group—create a new Azure resource group or select an existing one.
   3. Name—enter a name for the load balancer instance.
   4. Region—select the geographic location for the load balancer instance.
   5. SKU—select Standard (Distribute traffic to backend resources).
   6. Type—select Internal.
4. On the Frontend IP configuration tab, configure the frontend IPv4/IPv6 address(es) that will operate as the client-facing address(es) of the xHA pair. If configuring xHA with dedicated management, you must also configure the frontend IPv4/IPv6 address for dedicated management. To start, select Add a frontend IP configuration, then fill in the following parameters:
   1. Name—enter a name for the frontend IP configuration.
   2. IP version—select the IP version for the frontend IP address, either IPv4 or IPv6.
   3. Virtual network and Subnet—select the Azure virtual network and associated subnet for the frontend IP address. Ensure that Address Manager is able to reach this network and subnet.
   4. Assignment—select Dynamic.
   5. Availability zone—select an appropriate availability zone option based on your network requirements. For more information, refer to https://learn.microsoft.com/en-us/azure/reliability/availability-zones-overview.
   Note: The number of frontend IP configurations you must create depends on the service (eth0) and management (eth2) address configuration of the DNS/DHCP Servers. Example: For a pair of IPv4-only DNS/DHCP Servers with dedicated management disabled, only one frontend IP configuration is required for the IPv4 eth0 interface. For a pair of DNS/DHCP Servers with dual-stack services interfaces and dedicated management enabled, three frontend IP configurations are required - one for IPv4 services, one for IPv6 services, and one for dedicated management.
5. On the Backend pools tab, designate the DNS/DHCP Server interfaces that will receive incoming network traffic. To start, select Add a backend pool, then fill in the following parameters:
   1. Name—enter a name for the backend pool.
   2. Backend Pool Configuration—select NIC.
   3. IP configurations—In the IP configurations table, add the service interface IPv4/IPv6 addresses (eth0 IP) for both DNS/DHCP Servers. If configuring xHA with dedicated management, add the dedicated management IPv4/IPv6 addresses (eth2 IP) for each server as well.
   Note: Following the early example, for a pair of IPv4-only DNS/DHCP Servers with dedicated management disabled, one backend pool is required containing the IPv4 eth0 addresses of the DNS/DHCP Servers. For a pair of DNS/DHCP Servers with dual-stack services interfaces and dedicated management enabled, three backend pools are required - one for the IPv4 eth0 addresses, one for the IPv6 eth0 addresses, and one for the dedicated management addresses.
6. On the Inbound rules tab, create load balancing rules for IPv4/IPv6 service requests and dedicated management access. To start, select Add a load balancing rule, then fill in the following parameters:
   1. Name—enter a name for the load balancing rule.
   2. IP version—select the IP version for the load balancing rule, either IPv4 or IPv6.
   3. Frontend IP address—Select the frontend IP address created previously in step 4.
   4. Backend pool—Select the associated backend pool created previously in step 5.
   5. High availability ports—Select this checkbox to enable.
   6. Health probe—create a new health probe. This health probe will be re-used in all the other load balancing rules we configure. To start, select Create new, then fill out the following parameters:
      • Name—enter a name for the health probe.
      • Protocol—select HTTP.
      • Port—enter 8888.
      • Path—enter /healthz.
      • Interval (seconds)—enter 5.
   7. Session persistence—select None.
   8. Idle timeout—enter 4.
   9. Enable TCP Reset—leave checkbox disabled.
   10. Enable Floating IP—select the checkbox to enable.
   Note: Following the early example, for a pair of IPv4-only DNS/DHCP Servers with dedicated management disabled, one load balancing rule is required for IPv4 services and management traffic. For a pair of DNS/DHCP Servers with dual-stack services interfaces and dedicated management enabled, three load balancing rules are required - one for the IPv4 services traffic, one for the IPv6 services traffic, and one for dedicated management.
7. The Outbound rules and Tags tabs are not required for xHA load balancer configuration.
8. On the Review + create tab, review the load balancer configuration details.
9. Select Create to create the load balancer.