The reference network configuration described in Horizon Cloud with On-Premises Infrastructure Installation and Configuration uses the specific static IP addresses, host names, and DNS domains described here. Use these examples to determine the deployment settings appropriate for your organization's needs.

DNS and Your Horizon Cloud with On-Premises Infrastructure Environment

Deploying and configuring a Horizon Cloud with On-Premises Infrastructure environment involves deploying several virtual instances (virtual machines and virtual appliances) in an on-premises virtual infrastructure environment. These virtual instances get assigned static IP addresses. For proper configuration, some of the components also use a system name or hostname, and the best practice is to use a fully qualified domain name (FQDN) as the system name. The FQDN must be resolvable by your specified DNS server.

Examples:

  • Each ESXi host in the vSAN Ready Node cluster has a hostname and must have a fully qualified domain name (FQDN), because the hosts must be registered with the deployed vCenter Server Appliance instance using their FQDNs.

  • During installation of the vCenter Server Appliance, you specify the network address and system name in the network settings step of the installation screens. When you specify the network address as IP address 172.16.0.10 and the system name as vcenter.vrn.local, the virtual appliance is deployed with IP address 172.16.0.10 allocated to it and the system name is set to that vcenter.vrn.local FQDN.

  • When the Horizon Air Link deploys and configures the Horizon Cloud Node virtual appliance, it allocates an IP address from the desktop network IP addresses that you entered in the Horizon Cloud Node Setup user interface. This IP address is used for brokering the end-user connection from the end user's client device or browser and the pool of virtual desktops. For ease of use, rather than using a numeric IP address in the client device, the best practice is to match a memorable name, like desktops.example.com, to the numeric IP address, and provide that memorable name to your end users. You configure your organization's DNS records to match the memorable name to the numeric IP address.

For environments other than proof-of-concepts or labs, the general best practice is to update your organization's DNS configuration with records that associate an FQDN name with the allocated network IP address.

Example Configuration Values

Note:

The Horizon Cloud Node virtual appliance is listed in both of these networking tables for the management network and desktop network reference values. When the Horizon Air Link deploys and configures the virtual appliance, two IP addresses are assigned to the appliance: one from the management network and one from the desktop network. The IP address from the management network is used for the component that connects the virtual appliance to the cloud management plane. The IP address from the desktop network is used to broker the end-user connections to the pool of virtual desktops.

Table 1. Management Network for VLAN 1000

Host Name or System Name

IP Address

Domain

Description

vlan1000gw

172.16.0.1

vrn.local

Your gateway used for this management network and VLAN 1000.

horizon-air-link

172.16.0.5

vrn.local

The Horizon Air Link virtual appliance deployed in the vSAN cluster. In this example, the instance has an FQDN of horizon-air-link.vrn.local and an IP address of 172.16.0.5 assigned to one of the appliance's network interfaces, typically eth0. You provide the IP address when you deploy the OVA into the vSAN Ready Node cluster.

loghost

172.16.0.9

vrn.local

A network server to which you configure the ESXi Dump Collector and vSphere Syslog Collector on each ESXi host to redirect ESXi memory dumps and system logs. As described in the VMware vSAN documentation, it is a best practice to configure the ESXi Dump Collector and vSphere Syslog Collector to redirect ESXi memory dumps and system logs to a network server. Having this loghost destination avoids potential loss of log information for systems where you might not have enough local storage or datastore space left for persistent logging. See the vSphere Installation and Setup Guide at the vSphere 6 documentation page for steps on how to configure the redirection of ESXi memory dumps and system logs to a network server.

vcenter

172.16.0.10

vrn.local

The vCenter Server Appliance instance deployed in the vSAN Ready Node environment. In this example, the instance has a system name that is an FQDN (vcenter.vrn.local) and an IP address of 172.16.0.10 from the management network.

esxi-01

172.16.0.11

vrn.local

The first ESXi host in the vSAN cluster. In this example, the ESXi host has an FQDN of esxi-01.vrn.local and its vmk0 interface has IP address 172.16.0.11. This ESXi host is also called Node 1 in Horizon Cloud with On-Premises Infrastructure Installation and Configuration.

esxi-02

172.16.0.12

vrn.local

The second ESXi host in the vSAN cluster. In this example, the ESXi host has an FQDN of esxi-02.vrn.local and its vmk0 interface has IP address 172.16.0.12.

esxi-03

172.16.0.13

vrn.local

The third ESXi host in the vSAN cluster. In this example, the ESXi host has an FQDN of esxi-03.vrn.local and its vmk0 interface has IP address 172.16.0.13.

esxi-04

172.16.0.14

vrn.local

The fourth ESXi host in the vSAN cluster. In this example, the ESXi host has an FQDN of esxi-04.vrn.local and its vmk0 interface has IP address 172.16.0.14.

smartnode-sm1

172.16.0.28

{172.16.0.29}

vrn.local

The Horizon Cloud Node virtual appliance deployed in the vSAN cluster. The Horizon Air Link virtual appliance automatically creates, deploys, and configures this virtual appliance in the cluster. The deployed appliance has a host name that is generated by the system automatically by default. You can use the vSphere Web Client to connect to your vCenter Server environment and see the host name of the Horizon Cloud Node virtual appliance deployed in your environment.

When deployed, this virtual appliance is assigned two IP addresses: one from the range of management network IP addresses and one from the range of desktop network addresses that you entered in the Horizon Cloud Node Setup user interface. Additionally, the Horizon Air Link reserves another of the IP addresses from the set of management network IP addresses to later use for update purposes. That reserved IP address is listed here with braces, for example {172.16.0.29}. For information about the update process, see the Horizon Cloud with On-Premises Infrastructure Administration guide.

vrn-01-ipmi

172.16.0.41

vrn.local

The first ESXi host's IPMI connection.

vrn-02-ipmi

172.16.0.42

vrn.local

The second ESXi host's IPMI connection.

vrn-03-ipmi

172.16.0.43

vrn.local

The third ESXi host's IPMI connection.

vrn-04-ipmi

172.16.0.44

vrn.local

The fourth ESXi host's IPMI connection.

Table 2. Tenant or Desktop Network for VLAN 1001

Host Name or System Name

IP Address

Domain

Description

vlan1001gw

172.16.1.1

vrn.local

Your gateway used for this desktop network and VLAN 1001.

vrn-dc1

172.16.1.3

vrn.local

The DNS and NTP server.

unified-access-gw-app

172.16.1.9

vrn.local

The Unified Access Gateway appliance deployed when you install the Unified Access Gateway product. A best practice is to use Unified Access Gateway with a Horizon Cloud with On-Premises Infrastructure environment to provide end users with seamless HTML access to their desktops. For more information, see the Horizon Cloud with On-Premises Infrastructure Administration guide and the Unified Access Gateway documentation page.

smartnode-sm1

172.16.1.11

vrn.local

The Horizon Cloud Node virtual appliance deployed in the vSAN cluster. The Horizon Air Link virtual appliance automatically creates, deploys, and configures this virtual appliance in the cluster. The deployed appliance has a host name that is generated by the system automatically by default. You can use the vSphere Web Client to connect to your vCenter Server environment and see the host name of the Horizon Cloud Node virtual appliance deployed in your environment.

When deployed, this virtual appliance is assigned two IP addresses: one from the range of management network IP addresses and one from the range of desktop network addresses that you entered in the Horizon Cloud Node Setup user interface. The IP address here from the desktop network is used to broker the end-user connections to the pool of virtual desktops.

(DHCP start)

172.16.1.16

vrn.local

Start of the IP address range used for the end-user virtual desktops provided by this Horizon Cloud Node.

(DHCP end)

172.16.1.254

vrn.local

End of the IP address range used for the end-user virtual desktops provided by this Horizon Cloud Node.

Table 3. vSAN Private Network for VLAN 4001

IP Address

Node / ESXi Host

192.168.1.11

vrn-01

192.168.1.12

vrn-02

192.168.1.13

vrn-03

192.168.1.14

vrn-04

Table 4. vSphere vMotion Private Network for VLAN 4002

IP Address

Node / ESXi Host

192.168.2.11

vrn-01

192.168.2.12

vrn-02

192.168.2.13

vrn-03

192.168.2.14

vrn-04