Method 1 - Source IP Affinity
- Last Updated: June 24, 2024
- 1 minute read
- LoadMaster
- LoadMaster GA
- Documentation
Method 1 is recommended for all environments where source IP address affinity is possible. Where it is not possible, then either method 2 or method 3 should be used.
Method 1 is the simplest configuration for a load balancer because it uses standard port numbers and a single load balanced VIP. It relies on the load balancer to route secondary protocols to the same Unified Access Gateway appliance as was selected for the primary Horizon protocol. It does this based on repeat connections coming from the same Horizon client IP address. Unfortunately, this method does not work in all situations. For example, with certain Network Service Providers or NAT devices, the source IP address is not available for this affinity configuration. If source IP affinity cannot be used in your environment, then one of the other two methods should be used as they do not rely on source IP affinity.
Unified Access Gateway Configuration for External URLs for this configuration is shown in the following table.
In our example, the Fully Qualified Domain Name (FQDN) https://uag.myco.com resolves to 10.10.10.154.
| Unified Access Gateway Appliance | Configuration Item | Value |
|---|---|---|
|
UAG01 |
tunnelExternalURL |
https://uag.myco.com:443 |
|
UAG01 |
blastExternalURL |
https://uag.myco.com:443 |
|
UAG01 |
pcoipExternalURL |
10.10.10.154:4172 |
|
UAG02 |
tunnelExternalURL |
https://uag.myco.com:443 |
|
UAG02 |
blastExternalURL |
https://uag.myco.com:443 |
|
UAG02 |
pcoipExternalURL |
10.10.10.154:4172 |
Advantages of Source IP Affinity
- Uses standard port numbers
- Does not require multiple public virtual IP addresses
Disadvantages of Source IP Affinity
- Relies on source IP address affinity, which is not always possible.