Missing Network Driver/Host is down

Products

• VMware vSphere ESXi

Issue/Introduction

After removing the network VIB from and ESXi host because it was not compatible with the firmware according to the Broadcom Compatibility Guide, the host is rebooted. After the reboot, the host in inaccessible over the network and can only be accessed via the iLO/iDRAC.

Environment

ESXi 8.0

Cause

The manual removal of a boot-critical network driver VIB without the simultaneous installation or staging of a compatible replacement removes the VIB from the active boot bank. Upon reboot, the ESXi kernel lacks the necessary software modules to initialize and claim the physical network hardware.

Resolution

1. The ESXi host should be restarted via the iLO console.

2. Shift+R should be pressed during the hypervisor loading sequence to enter Recovery Mode.

3. The prompt to permanently replace the current build with the previous build (reverting the boot bank) should be accepted by pressing Y.

4. Connectivity should be verified once the host boots from the previous configuration where the driver is still present.

5. The compatible VIB should be staged to a local datastore.

6. Remove the old (incompatible) VIB with the following command:

esxcli software vib  remove --vibname=<vib_name>

7. Without rebooting, install the new vib with the following commnad:

esxcli software vib install -v /vmfs/volumes/[Datastore]/[Path]/[New_VIB].vib.

8. A reboot should be performed to ensure the new driver is correctly integrated and initialized.

9. Run the following command to ensure that the new VIB has been installed:

esxcli software vib list |grep -i <VIB_Name>