You assign host names and IP address according to the VLAN setup and domain configuration for multiple availability zones in VMware Cloud Foundation. You can use an example configuration of IP subnets, VLAN IDs, and FQDNs in your environment.

Example IP Addresses and Host Names for the NSX-T Workload Domain

Verify that the static IP addresses and FQDNs for all components are allocated on the DNS server and are available for deployment.
Table 1. Example VLAN IDs and IP Subnets for Availability Zone 1 for the NSX-T Workload Domain

VLAN Function

VLAN ID

Subnet

Gateway

Management

1641 (Stretched Layer 2)

172.16.41.0/24

172.16.41.253

vSphere vMotion

1642

172.16.42.0/24

172.16.42.253

vSAN

1643

172.16.43.0/24

172.16.43.253

Host overlay

1644

172.16.44.0/24

172.16.44.253

Uplink01

1647

172.16.47.0/24

172.16.47.253

Uplink02

1648

172.16.48.0/24

172.16.48.253

Edge overlay

1649

172.16.49.0/24

172.16.49.253

Table 2. Example VLAN IDs and IP Subnets for Availability Zone 2 for the NSX-T Workload Domain

VLAN Function

VLAN ID

Subnet

Gateway

Management

1661

172.16.61.0/24

172.16.61.253

vSphere vMotion

1662

172.16.62.0/24

172.16.62.253

vSAN

1663

172.16.63.0/24

172.16.63.253

Host overlay

1664

172.16.64.0/24

172.16.64.253

Uplink01

1667

172.16.67.0/24

172.16.67.253

Uplink02

1668

172.16.68.0/24

172.16.68.253

Edge overlay

1669

172.16.69.0/24

172.16.69.253

Table 3. Example FQDNs and IP Addresses for the ESXi Hosts of the NSX-T Workload Domain

Availability Zone

ESXi Host

Management IP Address

NTP Server

Availability Zone 1

sfo01w01esx01.sfo01.rainpole.local

172.16.41.101

ntp.sfo01.rainpole.local

sfo01w01esx02.sfo01.rainpole.local

172.16.41.102

ntp.sfo01.rainpole.local

sfo01w01esx03.sfo01.rainpole.local

172.16.41.103

ntp.sfo01.rainpole.local

sfo01w01esx04.sfo01.rainpole.local

172.16.41.104

ntp.sfo01.rainpole.local

Availability Zone 2

sfo02w01esx01.sfo01.rainpole.local

172.16.61.101

ntp.sfo01.rainpole.local

sfo02w01esx02.sfo01.rainpole.local

172.16.61.102

ntp.sfo01.rainpole.local

sfo02w01esx03.sfo01.rainpole.local

172.16.61.103

ntp.sfo01.rainpole.local

sfo02w01esx04.sfo01.rainpole.local

172.16.61.104

ntp.sfo01.rainpole.local

Table 4. Example FQDNs and IP Addresses for NSX-T Manager in the Management Domain

Role

FQDN

IP Address

NSX-T Manager instances

sfo01wnsx01a.sfo01.rainpole.local

172.16.11.82

sfo01wnsx01b.sfo01.rainpole.local

172.16.11.83

sfo01wnsx01c.sfo01.rainpole.local

172.16.11.84

NSX-T Manager cluster sfo01wnsx01.sfo01.rainpole.local

172.16.11.81 (VIP)

Table 5. Example FQDNs and IP Addresses for the NSX-T Edge Nodes

Availability Zone

Role

FQDN

IP Address

Availability Zone 1

Edge Node 01

sfo01wesg01.sfo01.rainpole.local

172.16.41.21 (Management)

172.16.49.21 (Overlay)

172.16.47.2 (Uplink 1)

172.16.48.2 (Uplink 2)

Edge Node 02

sfo01wesg02.sfo01.rainpole.local

172.16.41.22 (Management)

172.16.49.21 (Overlay)

172.16.47.3 (Uplink 1)

172.16.48.3 (Uplink 2)

Availability Zone 2

Edge Node 01

sfo02wesg01.sfo01.rainpole.local

172.16.61.21 (Management)

172.16.69.21 (Overlay)

172.16.67.2 (Uplink 1)

172.16.68.2 (Uplink 2)

Edge Node 02

sfo02wesg02.sfo01.rainpole.local

172.16.61.22 (Management)

172.16.69.22 (Overlay)

172.16.67.3 (Uplink 1)

172.16.68.3 (Uplink 2)

Subnet mask

-

255.255.255.0

DNS

-

  • 172.16.11.5

  • 172.16.11.4

NTP

ntp.sfo01.rainpole.local

  • 172.16.11.251

  • 172.16.11.252

Example Host Names of in the Management Domain

Component

FQDN

IP Address

Management vCenter Server

sfo01m01vc01.sfo01.rainpole.local

172.16.11.62

vCenter Server for the NSX-T workload domain

sfo01w01vc01.sfo01.rainpole.local

172.16.11.64
SDDC Manager sfo01sddcm01.sfo01.rainpole.local 172.16.11.65

Third Location Components

Component

FQDN

IP Address

vCenter Server in the third location

lax01m01vc01.lax01.rainpole.local

172.17.11.62
vSAN witness host sfo03w01vsanw01.sfo01.rainpole.local
  • 172.17.11.203 (Management)
  • 172.17.13.203 (vSAN)

Example Naming Convention for Host and Object Names

In your environment, you can use an example naming convention where host and object names indicate the location and scope of the management components.
Table 6. Example Naming Convention for NSX- T Workload Domains
Component Type
  • Host names
  • Virtual machine names
<location><az-number><workload-domain><workload-domain-number><mgmt-component><mgmt-component-id>
  • Clusters
  • Virtual switches and port groups
  • Datastores
<location><az-number>-<workload-domain><workload-domain-number>-<object-name><object-number>-<sub-object>
  • Data centers
  • Resource pools
  • Virtual machine folders
<location><az-number>-<workload-domain><workload-domain-number><object-type>-<object-name><object-number>

The <location> segment represents an instance of VMware Cloud Foundation at a specific location, also called region. For example, you can use city airport codes, such as SFO or LAX.

  • Components with object names that begin with sfo01 are part of the SFO region and Availability Zone 1.

  • Components with object names that begin with sfo02 are part the SFO region and Availability Zone 2.

  • Components with object names that begin with lax01 are part the LAX region and Availability Zone 1.

  • Components with object names that begin with sfo without a number are part of the SFO region and both availability zones.

  • Components with object names that begin with sfo01w01 are part of the SFO region and the first workload domain.

  • The vSAN witness node is deployed in a third availability zone and its host name starts with the sfo03 prefix.