Knowledge Base

Validate that each troubleshooting step below is true for your environment. Each step will provide 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. Please do not skip a step.

To troubleshoot connectivity to iSCSI arrays using software initiator:

1. Verify that the ESX or ESXi host can see any targets on shared storage. For more information, see Obtaining LUN pathing information for ESX or ESXi hosts (1003973).
   
   
2. Verify that a rescan restores visibility to the targets. For more information, see Performing a rescan of the storage (1003988).
   
   
3. Verify that the virtual switch being used for storage has been configured correctly. See Networking Configuration for Software iSCSI Storage in the Server Configuration Guide.
   
   Note: Ensure that there are enough available ports on the virtual switch. For more information, see Network cable of a virtual machine appears unplugged (1004883) and No network connectivity if all ports are in use (1009103).
   
   
4. Log in to the ESX or ESXi host and verify that the host can vmkping the iSCSI targets with the command:
   
vmkping <target ip>

   If you are running on an ESX host, check that the iSCSI target is pingable:
   
   ping <target ip>

   For more information, see Testing network connectivity with the ping command (1003486) and Testing VMkernel network connectivity with the vmkping command (1003728).
   
   
5. Verify that the storage array is listed in the VMware Hardware Compatibility Guide and that the initiator is registered on the array. Consult your storage vendor for instructions on this procedure.
   
   
6. Verify that the array is configured correctly for use with ESX Server or ESXi hosts. Partner with your hardware vendor to ensure that the array is properly configured. For more information, see the iSCSI SAN Configuration Guide.
   
   
7. Verify that the physical hardware and physical network hardware are functioning correctly. You may have to contact your hardware vendor for information about verifying your hardware functions correctly.

Note: If your problem still exists after trying the steps in this article, please:

• Gather the VMware Support Script Data. For more information, see Collecting diagnostic information in a VMware Virtual Infrastructure Environment (1003689).
• File a support request with VMware Support and note this KB Article ID (1003952) in the problem description. For more information, see How to Submit a Support Request.