Configure the required network and load balancer settings for your Horizon Edge on vSphere deployments.
UAG VM-related Network Requirements
Three networks are required in which the portGroup requires static or reserved IPs on the corresponding VLAN. The minimum requirement IP range with 2 consecutive IPs to deploy a pair of UAGs. Specific requirements are listed below:
-
For the DMZ network, the portGroup on which the DMZ network interface of the UAG will be attached must be reachable from the network that the end users are connecting from. The Static IP Range minimum requirement is 2 consecutive IPs - for example, 10.202.155.30-10.202.155.39 - is required to support UAG cluster growth to 10.
-
For the Management network, the portGroup on which the Management network interface of the UAG is attached is also the portGroup on which the Edge VM will be deployed. The Static IP range minimum requirement is 2 consecutive IPs - for example, 172.20.241.30-172.202.155.39 - is required to support UAG cluster growth to 10.
-
For the Desktop network, the portGroup on which the Desktop network interface of the UAG is attached is the portGroup on which the desktop VMs are deployed on. The VMs must be able to reach the Edge VM and the Active Directory infrastructure. The Static IP range minimum requirement is 2 consecutive IPs - for example, 192.168.240.30-192.168.240.39 - is required to support UAG cluster growth to 10.
Note: You can use the Omnissa Edge URL Checker tool to verify the network requirements.
Additionally, a DNS entry must be created for the UAG FQDN that resolves itself to the load balancer VIP for scenarios in which a deployment contains multiple UAGs.
Edge VM-related Network Requirements
The Edge VM requires one static IP from the identified Management network for the Edge VM along with a resolvable FQDN, (a record in the DNS infrastructure) to allow the desktop VMs to access.
Additionally, the Edge VM needs all required URLs and ports to be allowedlisted and open in the network firewalls, as documented in Port and Protocol Requirements for Deploying a vSphere Edge.
Using the Capability to Facilitate Aggregate Connectivity Between Edge Gateway Appliance and Horizon Control Plane
You can enable the capability to use aggregated agent communication between the Horizon Edge Gateway Appliance and the Horizon Control Plane rather than having each agent make its own outbound internet call to the Horizon Control Plane.
This capability is provided and managed by the Horizon Agent Edge Gateway appliance. Using this method, the Horizon agent connects to the Edge Gateway that is deployed inside your network. The Edge Gateway then forwards the requested communication to the Horizon Control Plane. Only one device, the Edge Gateway Appliance, is required to make internet calls to the Horizon Control Plane for the agent to Control Plane communication..
Note: Ensure that the DNS settings used by your desktops are able to resolve public Azure DNS records.
If your Edge Gateway Appliance becomes reachable, you can point your agents to the Horizon Control Plane by using outbound internet calls. Should your Edge Gateway Appliance become unreachable, contact Omnissa Customer Connect to help ensure that your desktops are allowed to make outbound internet calls to the Horizon Control Plane.
For related information, see the VDI Ports and Protocols Requirements table in Port and Protocol Requirements for Deploying a vSphere Edge.
Load Balancing
You can add a customer-managed local load balancer of choice to configure in front of the UAG instances. For information about adding a load balancer, see Load Balancing Unified Access Gateway for Horizon in Omnissa Tech Zone.
Was this page helpful?