ESXi host no longer part of vDS after the failed ESXi upgrade

Products

• VMware vSphere ESXi

Issue/Introduction

• ESXi host upgrade got hung and the host was rebooted.
• The host has no network connectivity after reboot.
• Logging in as root through DCUI and checking the vDS configuration with "net-dvs -l" command gives the following error:
  

  # net-dvs -l
  failed to get config data: not initialized
  

• Checking vmkernel adapters settings you get the following error:

  # esxcli network ip interfaces list
  Unable to Get Proxy Portset Name: Status(bad0031)- Not Initialized

Cause

ESXi host data got corrupted due to a failed upgrade.

Resolution

As the host has corrupted data during the failed upgrade, the cleanest method to recover would be to reinstall ESXi host.

Additional Information

• Regarding the failed upgrade, please open a suport request for analysis.
• For more information, see Creating and managing Broadcom support cases.
• In case if you get "failed to get config data: not initialized" error but there was no failed upgrade:
  Adding an ESX host into a Distributed Virtual Switch fails with the error: Unable to Create Proxy DVS