ESXi creates standard switch vSwitchBMC with uplink vusb0 automatically after upgrading to 8.0.3 version
search cancel

ESXi creates standard switch vSwitchBMC with uplink vusb0 automatically after upgrading to 8.0.3 version

book

Article ID: 376173

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Starting with vSphere 8.0, in both Integrated Dell Remote Access Controller (iDRAC) and HP Integrated Lights Out (ILO), when you have a USB interface enabled, vUSB or vNIC respectively, an additional standard switch vSwitchBMC with uplink vusb0 gets created on the ESXi host.

After upgrading to ESXi 8.0.3 version, it will show follow configuration and error:

  1. ESXi creates standard switch vSwitchBMC with uplink vusb0 automatically.
  2. ESXi adds uplink vusb0 on standard switch and creates a new vmk on vSwitch automatically which will make related standard switch become exception.
    • The related standard switch will not create/delete vmk or port group normally.
    • The new vmk doesn't have an IP address.

Environment

VMware vSphere ESXi 

Cause

This is expected, in view of the introduction of data processing units (DPUs) on some servers but might cause the VMware Cloud Foundation Bring-Up process to fail.

Resolution

Workaround:

Before vSphere 8.0 installation, disable the USB interface in the remote management application that you use by following vendor documentation.

After vSphere 8.0 installation, use the ESXCLI command esxcfg-advcfg -s 0 /Net/BMCNetworkEnable to prevent the creation of a virtual switch vSwitchBMC and associated portgroups on the next reboot of host.

See this script as an example:

~# esxcfg-advcfg -s 0 /Net/BMCNetworkEnable

The value of BMCNetworkEnable is 0 and the service is disabled.

~# reboot

On host reboot, no virtual switch, PortGroup and VMKNIC are created in the host related to remote management application network.

Additional Information