Storage adapter (vmhba) status offline or down on ESXi
search cancel

Storage adapter (vmhba) status offline or down on ESXi

book

Article ID: 375567

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Troubleshoot storage adapter Offline or Down status within the VMware vSphere environment. This article provides steps to identify physical and logical layer failures when an HBA fails to present to the ESXi host.

Symptoms

  • Storage adapters show status Offline or Down in vCenter.
  • One port of a multi-port HBA shows offline in out-of-band management consoles (e.g., iDRAC, ILO) while other ports remain active.
  • HPE iLO/iDRAC management interface reports WWNN and WWPN for the adapter as Unknown
  • localcli storage san fc list indicates Port State: LINK DOWN and Speed: 0 Gbps.
  • A newly installed HBA card does not appear or remains offline.
  • RDM disks are invisible on the affected host but visible on other hosts in the same cluster.
  • On Cisco UCS environments, the HBA may show offline while targets and devices remain visible.
  • Storage rescans do not change the adapter status.
  • The following errors appear for frame drop and soft_context_reset loop failure  in /var/run/log/vmkernel.log:

WARNING: iodm: vmk_IodmEvent:194: vmhba6: FRAME DROP event has been observed 17 times in the last one minute.

ScsiDeviceIO: 4115: Cmd(...) failed H:0x2 D:0x0 P:0x0

WARNING: ScsiPath: 830: Failed to fetch FC target attributes for path vmhba4:C0:T4:L0.Status = 195887105

qedf:vmhba#:qedfc_link_update_handler:####:Info: ST(LINK): LINK_DOWN

qedf:vmhba#:soft_context_reset:####:Info: calling qedfc_ctx_soft_reset

 

Environment

  • VMware vSphere ESXi 8.x
  • VMware vCenter Server 8.x
  • VMware Cloud Foundation (VCF)
  • HPE ProLiant / Dell PowerEdge Servers

Cause

The "Offline" status typically indicates a logical or driver-layer disconnect, while "Down" indicates a physical link-layer failure (no light). Frame drops, H:0x2 errors, and Status 195887105 point to physical fabric congestion, faulty hardware, or link-layer issues outside the ESXi host.

Resolution

  1. Verify the physical link status via the hardware vendor's management console (e.g., iDRAC, ILO).
  2. Check driver and firmware versions against the VMware Compatibility Guide. See Determining Network/Storage firmware and driver version in ESXi (323110).
  3. Attempt a manual reset of the HBA via ESXi CLI: For FC: esxcli storage san fc reset -A vmhba# and For FCoE: esxcli storage san fcoe reset -A vmhba#
  4. Engage the fabric and hardware vendors to inspect physical cables, SFPs, and switch port statistics for CRC errors or frame drops. In some cases, disabling and re-enabling the corresponding port on the SAN switch may resolve the state.
  5. Reboot the impacted host once the fabric layer is confirmed healthy to refresh adapter states and regain access to datastores/LUNs.
  6. If the hardware and fabric are validated as healthy and the issue persists, contact Broadcom Support.

Additional Information