ESXi no managment connetion but VM still runnning

In our environment 1 Host stopped responding. You cannot reach it over vCenter, Host Client, SSH, DCUI. You cannot login to the ESXi but all VMs are still running. Bad news: you have to restart your host hard but you can shutdown the VM over the Guest system so no dirty shutdown ;).

First VMware Ticket => this happens sometimes restart host …

A few days later second host the same symptoms. After reopening the Ticket they found an internal knowledge-base article. The reason was the “Active Directory Service” of the ESXi. ESXi uses “Likewise” to authenticate again the Active Direcorty. In our case the Likewise cache ran out of memory and the management of the ESXi became unavailable.

So the resultion from VMware was extend the Likewise Cache…

Edit:
Happend again :/ now we actived likewise logging and have to wait for the next crash

Edit:

After a few VMware-Tickets now there is an offical knowledge base artikel with a workaround but at the moment no resolution:

https://kb.vmware.com/s/article/78968

ESXi 6.7U3 qfle3 PSOD

You use Qlogic network card and the qfle driver maybe your ESXi-Host will run into a PSOD. In may case it was the qfle3f driver and the hosts ran serveral times into a PSOD. The version of the driver does not matter in this case. If you the FCoE adapters in hosts then the hosts will always send some communication over thes adapters. In some cases there happens a PSOD because nobody is answering.

If you install the driver you always install a driver package which includes 4 drivers.

-qfle3 => Network driver
-qfle3f => Fibre-Channel over Ethernet
-qfle3i => iSCSI
-qcnic => other network driver (don’t know the exact usage)

After a few cases with VMware I get the tip: “When you don’t use iSCSI/FCoE why don’t you remove it?”

If you remove the drivers and your storage is connected over iSCSI,FCoE you will lose storage connection! Always put your host into maintance mode before changes!
So if you don’t use the protocols/modules here how to remove them:

FCoE:
# esxcli software vib remove –vibname=qfle3f

iSCSI:
# esxcli software vib remove –vibname=qfle3i

Network drivers:

First check which drivers you are using because if you remove the you are using your ESXi-Host is disconnected from network after the reboot

Check network adapters and drivers:
# esxcli network nic list

# esxcli software vib remove –vibname=qcnic

# esxcli software vib remove –vibname=qfle3

After you have removed the modules reboot your hosts and you are done 🙂