反对figure a high-availability setup with Azure external and internal load balancers simultaneously

September 14, 2021

反对tributed by:

The high availability pair on Azure supports both external and internal load balancers simultaneously.

你有以下两个选项来配置high availability pair using both Azure external and internal load balancers:

Using two LB virtual servers on the Citrix ADC appliance.
Using one LB virtual server and an IP set. The single LB virtual server serves traffic to multiple IPs, which are defined by the IPset.

Perform the following steps to configure a high availability pair on Azure using both the external and internal load balancers simultaneously:

For Steps 1 and 2, use the Azure portal. For Steps 3 and 4, use the Citrix ADC VPX GUI or the CLI.

Step 1.反对figure an Azure load balancer, either an external load balancer or an internal load balancer.

For more information on configuring high-availability setup with Azure external load balancers, see反对figure a high-availability setup with multiple IP addresses and NIC.

For more information on configuring high-availability setup with Azure internal load balancers, see反对figure HA-INC nodes by using the Citrix high availability template with Azure ILB.

Step 2.Create an extra load balancer (ILB) in your resource group. In Step 1, if you have created an external load balancer, you now create an internal load balancer and conversely.

To create an internal load balancer, choose the load balancer type asInternal. For theSubnetfield, you must choose your Citrix ADC client subnet. You can choose to provide a static IP address in that subnet, provided there are no conflicts. Otherwise, choose the dynamic IP address.
To create an external load balancer, choose the load balancer type asPublicand create the public IP address here.

After you have created the Azure Load Balancer, navigate toFrontend IP configurationand note down the IP address shown here. You must use this IP address while creating the ADC load balancing virtual server as in Step 3.
In theAzure Load Balancer configurationpage, the ARM template deployment helps create the LB rule, back-end pools, and health probes.
Add the high availability pair client NICs to the backend pool for the ILB.
Create a health probe (TCP, 9000 port)
Create two load balancing rules:
- One LB rule for HTTP traffic (webapp use case) on port 80. The rule must also use the backend port 80. Select the created backend pool and the health probe. Floating IP must be enabled.
- Another LB rule for HTTPS or CVAD traffic on port 443. The process is the same as the HTTP traffic.

Step 3.On the primary node of Citrix ADC appliance, create a load balancing virtual server for ILB.

Add a load balancing virtual server.
```
add lb vserver   [] [] 
```
Example:
```
add lb vserver vserver_name HTTP 52.172.96.71 80 
```
Note:

Use the load balancer frontend IP address, which is associated with the additional Load balancer that you create in Step 2.

Bind a service to a load balancing virtual server.

bind lb vserver

Example:

bind lb vserver Vserver-LB-1 Service-HTTP-1

For more information, seeSet up basic load balancing

Step 4:As an alternative to Step 3, you can create a load balancing virtual server for ILB using IPsets.

Add an IP address of type virtual server IP (VIP).
```
add nsip  -type  
```
Example:
```
add nsip 52.172.96.71 -type vip 
```
Add an IPset on both primary and secondary nodes.
```
add ipset  
```
Example:
```
add ipset ipset1 
```

Bind IP addresses to the IP set.

bind ipset

Example:

bind ipset ipset1 52.172.96.71

Set the existing LB virtual server to use the IPset.

set lb vserver  -ipset

Example:

set lb vserver vserver_name -ipset ipset1

For more information, see反对figure a multi-IP virtual server.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

反对figure a high-availability setup with Azure external and internal load balancers simultaneously

September 14, 2021

反对tributed by:

September 14, 2021

反对tributed by:

反对figure a high-availability setup with Azure external and internal load balancers simultaneously

In this article