VCF cluster creation fails with "Failed to configure Vswitch to DVS vmknic migration on Host" due to vusb0 interface

Products

• VMware vSphere ESXi

Issue/Introduction

During VCF cluster creation or Workload Domain deployment, the task fails during the networking configuration phase. This typically occurs when an ESXi host contains a vusb0 (Virtual USB) interface, resulting in an odd number of total network interfaces.

Symptoms:

• SDDC Manager UI displays: failed to configure Vswitch to DVS vmknic migration on Host.
  
  
  
  

• The Switch Configuration page in the deployment wizard may fail to display available profiles or custom profiles may not function.

• Log files (/var/log/vmware/vcf/domainmanager/domainmanager.log) contain entries similar to:

  INFO [c.v.v.c.f.p.a.i.MigrateHostManagementVmknicsToDvsAction] Migrating Host <HOSTNAME_REDACTED> vmknics to DVS <DVS_REDACTED>
  Unable to migrate vmknic vmk0 -- retrying 1
  com.vmware.vim.binding.vmodl.fault.HostCommunication: An error occurred while communic

 

 

Environment

VMware Cloud Foundation 5.2

Cause

A product issue exists in the SDDC Manager inventory logic where the algorithm used to calculate and display virtual switch profiles fails if the total physical interface count is an odd number. The presence of the vusb0 interface often creates this odd-numbered count, interfering with the DVS migration logic during commissioning or cluster expansion.

Resolution

Currently, there is no permanent resolution. This issue is under investigation by Broadcom engineering.

If you encounter the symptoms outlined above, contact Broadcom Technical Support for further assistance, as the resolution involves modifying SDDC database instance, which should be performed with caution.