Troubleshooting fibre channel storage connectivity

Products

• VMware vSphere ESXi

Issue/Introduction

This article guides you through the most common steps to identify a connectivity problem to a shared storage device.

Symptoms:

• No targets from an array can be seen by:
  • All of the ESXi hosts
  • All of the ESXi hosts on a specific fabric or connected through an ISL link
  • One ESXi host
• Targets on the storage array are visible, but one or more LUNs are not visible
• LUN not visible
• LUN cannot connect
• Connectivity issues to the storage array
• LUN is missing
• ESXi host initiators are not logging into the array
• You see one of these errors:
  • Unknown inaccessible
  • SCSI: 4506: "Cannot find a path to device vmhba1:0:8 in a good state"

Environment

• VMware vSphere ESXi 6.x
• VMware vSphere ESXi 7.x
• VMware vSphere ESXi 8.x

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.To troubleshoot connectivity issues to the fiber channel storage array:

1. Verify that none of the hosts can see any targets in a shared storage environment. For more information, see Obtaining LUN pathing information for ESXi hosts (broadcom.com) and Identifying Fibre Channel, iSCSI, and NFS storage issues on ESXi hosts (broadcom.com). 
2. Verify that a rescan does not restore visibility to all the targets or brings all the LUNs back. For more information, see Performing a rescan of the storage on an ESXi host (broadcom.com). 
3. Verify the connectivity to the LUNs. For more information, see Troubleshooting LUN connectivity issues on ESXi hosts (broadcom.com). 
4. Verify that the fiber switch zoning configuration permits the ESXi host to see the storage array. Consult your switch vendor if you require assistance. 
5. Verify that the fiber switch propagates RSCN messages to the ESXi hosts.  
6. Verify that the storage array is listed in the VMware Hardware Compatibility Guide. For more information on confirming hardware compatibility, see Confirming ESX/ESXi host hardware (System, Storage, and I/O) compatibility (broadcom.com). Note: Some array vendors have a minimum microcode/firmware version that is required to work with ESXi. Consult your array vendor.
7. Verify that the initiator is registered on the array, and that the storage array is configured correctly. You may need to contact your storage vendor for instructions on this procedure.  
8. Verify the physical hardware:
   • The storage processors on the array.
   • The fiber switch and the Gigabit Interface Converter (GBIC) units in the switch.
   • The fiber cables between the fiber switch and the array.
   • The array itself. 
   Partner with the hardware vendor to ensure that the array is properly configured.

Notes:

• A rescan is required after any change is made to see if the targets are detected.
• If your problem still exists after trying the steps in this article:
  • Gather VMware Support log bundles. For more information, see Collecting diagnostic information in a VMware Virtual Infrastructure Environment (broadcom.com).
  • File a support request with Broadcom Support