When you want to isolate overlay network traffic, you can add a cluster with a shared NSX-T cluster and new vDS.

Prerequisites

  • Configure forward and reverse DNS settings for NSX-T and ESXi components.
  • Verify that the workload domain is provisioned.
  • Ensure that host configuration has a minimum of two active and unused vmnics.
  • Configure a DHCP server if the Host Overlay Network TEPs will use DHCP for IP allocation.
  • Download the Multi-Dvs-Script-master.zip file from https://code.vmware.com/samples?id=7481. Copy the Multi-Dvs-Script-master.zip file to the /home/vcf directory on the SDDC Manager VM and unzip it.
    Note: For a sample script, see the README.md file in the /home/vcf/Multi-Dvs-Script-master/Multi-Dvs-Automator directory.

Procedure

  1. Using SSH, log in to the SDDC Manager VM with the user name vcf and the password you specified in the deployment parameter sheet.
  2. To switch to the root account, run the su command.
  3. In the /home/vcf/Multi-Dvs-Script-master/Multi-Dvs-Automator directory, run the vxrailworkloadautomator.py script as python3 vxrailworkloadautomator.py.
  4. Enter the SSO user name and password.
  5. When prompted, select a workload domain to which you want to import the cluster.
  6. Select a cluster from the list of clusters that are ready to be imported.
  7. Enter passwords for the discovered hosts.
    • Enter a single password for all the discovered hosts.
    • Enter passwords individually for each discovered host.
  8. Create a new vSphere Distributed Switch (vDS).
    1. Select the option to create a new vDS.
    2. Enter the name of the vDS.
    3. Enter a comma-separated list of at least two physical NICs.
  9. Enter the Geneve VLAN ID.
  10. Provide the NSX-T Manager cluster details:
    1. Use an existing NSX-T instance.
    2. Enter VLAN ID for the NSX-T host overlay network.
    3. Select an existing NSX-T instance from the available list.
  11. Select the IP allocation method for the Host Overlay Network TEPs.
    Option Description
    DHCP With this option VMware Cloud Foundation uses DHCP for the Host Overlay Network TEPs.

    A DHCP server must be configured on the NSX-T host overlay (Host TEP) VLAN. When NSX creates TEPs for the VI workload domain, they are assigned IP addresses from the DHCP server.

    Static IP Pool With this option VMware Cloud Foundation uses a static IP pool for the Host Overlay Network TEPs. You can re-use an existing IP pool or create a new one.
    To create a new static IP Pool provide the following information:
    • Pool Name
    • Description
    • CIDR
    • IP Range.
    • Gateway IP
    Make sure the IP range includes enough IP addresses for the number of hosts that will use the static IP Pool. The number of IP addresses required depends on the number of pNICs on the ESXi hosts that are used for the vSphere Distributed Switch that handles host overlay networking. For example, a host with four pNICs that uses two pNICs for host overlay traffic requires two IP addresses in the static IP pool.
    Note: You cannot stretch a cluster that uses static IP addresses for the NSX-T Host Overlay Network TEPs.
  12. Enter and confirm the VxRail Manager root (mystic) password.
  13. Confirm the SSH thumbprints for VxRail Manager and the ESXi hosts.
  14. Select the license keys for VMware vSAN and NSX-T Data Center.
  15. Press Enter to begin the validation process.
  16. When validation succeeds, press Enter to import the cluster.