Host commissioning fails with "vSphere standard switch vSwitch0 must have only one NIC as Uplink"

Products

• VMware SDDC Manager

Issue/Introduction

• Host commissioning from SDDC Manager or vCenter Server fails with the following error:

"vSphere standard switch vSwitch0 must have only one NIC as an uplink."

• In the var/log/vmware/vcf/operationmanager/operationmanager.log on SDDC Manager, you will find entries similar to:

YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,69bbbf23f408753b9395495d7f4c5375,f6f1] [c.v.v.h.f.v.s.i.HostHardwareValidator,om-exec-8] Host - <HOSTNAME> has 12 10Gig Physical NIC(s): [vmnic0, vmnic1, vmnic10, vmnic11, vmnic2, vmnic3, vmnic4, vmnic5, vmnic6, vmnic7, vmnic8, vmnic9]
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,69bbbf23f408753b9395495d7f4c5375,f6f1] [c.v.e.s.c.c.v.vsphere.VcManagerBase,om-exec-8] Finding host with fqdn <HOSTNAME>
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,69bbbf23f408753b9395495d7f4c5375,f6f1] [c.v.v.h.f.v.s.i.HostHardwareValidator,om-exec-8] Host - [HOSTNAME] vSphere Standard Switch: vSwitch0.
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,69bbbf23f408753b9395495d7f4c5375,f6f1] [c.v.v.h.f.v.s.i.HostHardwareValidator,om-exec-8] Host - [HOSTNAME] vmNic: [vmnic1] is an Uplink for vSphere Standard Switch : 'vSwitch0'
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,69bbbf23f408753b9395495d7f4c5375,f6f1] [c.v.v.h.f.v.s.i.HostHardwareValidator,om-exec-8] Host - [HOSTNAME>] vmNic: [vmnic10] is an Uplink for vSphere Standard Switch: 'vSwitch0'

Environment

• VMware Cloud Foundation 9.x
• VMware Cloud Foundation 5.x

Cause

This issue occurs when a vmnic with suffix more than one digit(such as vmnic10, vmnic11 and so on) is attached to vSwitch0,the validation workflow incorrectly interprets two vmnics as uplinks to vSwitch0

Example:

• When vmnic10 is connected as an uplink to vSwitch0, validation workflow incorrectly identifies vmnic1 and vminc10 as uplinks to vSwitch0 and the validation fails
• Similar behavior will be seen if vSwitch0 has vmnic11 or vmnic12 etc. as uplinks

Resolution

This issue is currently under review and is planned to be resolved in a future release.

Workaround

To workaround this issue, perform one of the following methods:

Method 1: Temporarily disable the incorrectly detected vmnic

1. Check the uplink assigned to the host by running the following command: esxcli network vswitch standard list

2. Review the Operations Manager logs to identify which vmnic is incorrectly matched to the host.

3. Temporarily disable the incorrectly detected vmnic using the following command: esxcli network nic down -n vmnicX (Where vmnicX is the incorrectly detected interface)

4. Complete the host commissioning workflow.

5. Re-enable the vmnic after the workflow completes successfully.

Method 2: Attach single-digit vmnics

• Ensure you attach only vmnics with a single-digit prefix (for example, vmnic1 or vmnic9) to the vSwitch during Host Commissioning to prevent the string match validation failure.