Cluster stretch workflow - Add ESX Host(s) to vSphere Distributed Switch

Products

• VMware SDDC Manager

Issue/Introduction

The purpose of this KB article is to address issues that arise during the cluster stretch workflow—specifically when the process fails at the step: "Add ESX Host(s) to vSphere Distributed Switch" with cause: "No available vmnic found on the host".

Environment

SDDC Manager, VCF Installer, VCF Download Tool

Resolution

To resolve the issue:

1. For the failed hosts (hosts being added to cluster as part of stretch operation), exit the hosts from the maintenance mode via vCenter and further remove the hosts from the vCenter.
2. Post the hosts are removed from the vCenter, remove the same hosts from the SDDC-Manager's cluster (cluster that was being stretched).
3. De-commission the failed ESXi hosts via SDDC-Manager.
4. Commission ESXi hosts to be used for stretch via SDDC-Manager. Note: Older failed hosts can be Re-used (by Re-commissioning) without a need to Re-Image the hosts.
5. Trigger a new API call to stretch the cluster ensuring correct vmnic to vSphere Distributed Switch mapping is provided for each of the hosts within the stretch cluster payload.

Example payload:
{
  ...
  "clusterStretchSpec": {
    "hostSpecs": [
      {
        "id": "<ESX host 1 ID>",
        "hostNetworkSpec": {
          "vmNics": [
            ======> Ensure correct vmnic to vSphere Distributed Switch mapping is provided
          ]
        }
      },
      ...
  }
  ...
 }

Please refer to KB for the details on Stretch a vSAN ESA or OSA Cluster Using the SDDC Manager API



If the above steps are not working, contact GSS for further assistance.

Additional Information

The ESX hosts that you are adding to availability zone 2 must use the same vmnic to vSphere Distributed Switch mapping as the existing hosts in availability zone 1.