VMs on an ESXi 8.x host lose network connectivity (ping loss) and appear disconnected in vCenter Server. The ESXi host may show as "Not Responding" in vCenter, but remains accessible via the Direct Console User Interface (DCUI). In the DCUI, all physical NICs associated with the Emulex adapter may appear in a disconnected state.
Review of vmkernel.log reveals the following signatures:
WARNING: Uplink: #####: Queue 0 of device vmnic0 stuck, resetting the deviceWARNING: elxnet: elxnet_txComplClean:####: [vmnic0] #### pending tx-completions on txo[0]WARNING: elxnet: elxnet_mccWaitCompl:####: [vmnic0] MCC poll timed out!WARNING: elxnet: elxnet_detectDumpUe:###: [vmnic3] UE Detected!!WARNING: elxnet: elxnet_detectDumpUe:###: [vmnic3] UE hi: LPCMEMHOST bit setError in Card Detected! Cannot allocate WRBs hw_error:0|fw_timeout:1
ESXi 8.0 Update 3
The Emulex network adapter enters an Unrecoverable Error (UE) state due to a firmware or hardware lockup. This prevents the elxnet driver from allocating Work Queue Request Blocks (WRBs) through the mailbox interface, resulting in a transmit (TX) hang.
To recover a host currently in this state:
How to download and install async drivers in VMware ESXi
To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.
Download Broadcom products, patches and software