Symptoms:
An ESXi host experiences a sudden and total loss of storage connectivity.
VMware ESXi 8.x
The root cause is a physical or fabric-layer connection drop impacting multiple active Fibre Channel adapters simultaneously.
When independent HBAs (e.g., vmhba0 and vmhba1) record physical link-down events within the same millisecond window, it indicates a failure in a shared upstream component. This is typically caused by:
/var/run/log/vmkernel.log for the following pattern to verify if the issue is upstream from the ESXi host: WARNING: lpfc: lpfc_mbx_cmpl_read_topology:3696: vmhba0 1305 Link Down Event x2 received WARNING: lpfc: lpfc_mbx_cmpl_read_topology:3696: vmhba1 1305 Link Down Event x2 received lpfc: lpfc_els_rcv_rscn:7909: vmhba0 0214 RSCN received Data: x800220 x0 x8 x2 lpfc: lpfc_els_rcv_rscn:7916: vmhba0 5973 RSCN received event x0 : Address format x00 : DID x0802003. Device Loss Timeouts:
The driver initiates a 10-second timer to wait for fabric recovery:
WARNING: lpfc: lpfc_start_devloss:4565: vmhba0 3248 Start 10 sec devloss tmo WWPN ##:##:##:##:##:##:##:## NPort x0xxxxx WARNING: lpfc: lpfc_start_devloss:4565: vmhba1 3248 Start 10 sec devloss tmo WWPN ##:##:##:##:##:##:##:## NPort x0xxxxx
StorageApdHandlerEv: 106: Device [naa.xxx] has entered the All Paths Down state.1. Provide the exact timestamp of the Link Down events to your SAN/Fabric team.
2. Audit Switch Logs: Request an audit of Cisco MDS or Brocade switch logs for any Registered State Change Notifications (RSCNs) or reboot events.
3. Inspect Physical Layer: Check SFPs, optical cabling, and patch panels for any signs of structural defect or signal degradation (low light levels).
4. Host Reboot: If the host remains sluggish or management agents are hung after fabric recovery, a reboot of the ESXi host may be required to clear residual APD references.