Storage adapters show status as offline

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Navigate to Host > configure > Storage Adapters. FC adapters status show as "Offline".

  

• Run the command "esxcli storage core adapter list". Link State of all FC adapters will show as "link-down". However issue can also occur when the link state of the adapter is online.

  $ esxcli storage core adapter list

  HBA Name  Driver     Link State  UID                                     Capabilities         Description
--------  ---------  ----------  --------------------------------------  -------------------  --------------------------------------------------------------------------------
vmhba2    lpfc       link-down   fc.200070b7e42281b7:################    Second Level Lun ID  (0000:81:00.0) Emulex Corporation Emulex LPe35000/LPe36000 Fibre Channel Adapter
vmhba3    lpfc       link-down   fc.200070b7e42281b8:################    Second Level Lun ID  (0000:81:00.1) Emulex Corporation Emulex LPe35000/LPe36000 Fibre Channel Adapter 
vmhba64   lpfc       link-down   fc.200070b7e42281b7:################                         (0000:81:00.0) Emulex Corporation Emulex LPe35000/LPe36000 Fibre Channel Adapter
vmhba65   lpfc       link-down   fc.200070b7e42281b8:################                         (0000:81:00.1) Emulex Corporation Emulex LPe35000/LPe36000 Fibre Channel Adapter

• The Fibre Channel Adapter in the Hardware Console shows Link Status as "Down".

  

Environment

VMware vSphere ESXi

Cause

• This problem lies outside the ESXi host and necessitates assistance from the Storage/Switch vendor for further isolation.
  
  

• In "/var/run/log/vmkernel.log" , we will see below entries -

  2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu2:2099263) WARNING: ScsiPath: 830: Failed to fetch FC target attributes for path vmhba2:CO:TO: LO. Status = 195887105
2025-11-06T02:10:52.549Z In(182) vmkernel: cpu2:2099263) ScsiPath: 1260: Couldn't allocate path (vmhba2:CO: TO: LO) during scan: Failure


• In "/var/run/log/vmkwarning.log", you will see below entries -
  
   "Link Down Event" indicates that the Emulex (lpfc) driver has detected a physical link loss. This is why the LUNs are not visible. The error "Failed to fetch FC target attributes... Status = 195887105" occurs because the host can see a "path" exists in its configuration, but because the link is down, it cannot query the storage for device details (like the serial number or capacity).
  
  2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu0:2098677)WARNING: lpfc: lpfc_mbx_cmpl_read_topology:3696: vmhba2  1305 Link Down Event x2 received Data: x2 x20 x800220 x0
2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu0:2098677)WARNING: lpfc: lpfc_start_devloss:4565: vmhba2 3248 Start 10 sec devloss tmo WWPN 50:##:##:##:##:##:##:## NPort xc70160
2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu0:2098677)WARNING: lpfc: lpfc_start_devloss:4565: vmhba2 3248 Start 10 sec devloss tmo WWPN 50:##:##:##:##:##:##:## NPort xc726c0
2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu29:2098677)WARNING: lpfc: lpfc_cmpl_els_disc_cmd:3372: vmhba2 4650 ELS cmd x19 error: x9 x50000
2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu29:2098677)WARNING: lpfc: lpfc_notify_paths_available:4524: vmhba2 3274 ScsiNotifyPathStateChangeAsyncSAdapter Num x0 TID x1, DID xc726c0.
2025-11-06T02:10:52.549Z Wa(180) vmkwarning: cpu29:2098677)WARNING: lpfc: lpfc_notify_paths_available:4524: vmhba2 3274 ScsiNotifyPathStateChangeAsyncSAdapter Num x0 TID x0, DID xc70160.



• The error events recorded in the log suggest that the storage adapter is non-functional and that paths cannot be accessed.

Resolution

• Engage the Storage/Switch vendor to perform investigation of the Fiber Channel storage network. Ask your Fabric vendor to start the investigation by checking the following -

  • Check the SFP modules on both the ESXi host and the FC Switch. Ensure cables are seated correctly.
    
    
  • Ensure that the WWPNs (World Wide Port Names) seen in your logs are correctly zoned to the host HBAs on the switch.
    
    
  • Verify on the storage array that the LUNs are mapped to the correct Host Group and that the host's WWPNs are showing as "Logged In."