Search the VMware Knowledge Base (KB)
View by Article ID
Troubleshooting ESXi/ESX connectivity to iSCSI arrays using software initiators (1003952)
- One ESXi/ESX host cannot see any targets from all storage arrays.
- The array does not report the HBA of the ESXi/ESX host as being logged in.
- The array cannot ping the software initiator on the ESXi/ESX host.
- The ESXi/ESX host cannot ping the storage processor on the array.
- The ESXi/ESX host cannot vmkping the storage processor on the array.
This article guides you through the most common steps to identify a connectivity problem from an ESXi/ESX host to an iSCSI shared storage device using the software initiator.
To troubleshoot connectivity to iSCSI arrays using the software initiator:
- Verify that the ESXi/ESX host can see any targets on shared storage. For more information, see Obtaining LUN pathing information for ESX or ESXi hosts (1003973).
- Verify that a rescan restores visibility to the targets. For more information, see Performing a rescan of the storage on an ESXi/ESX host (1003988).
- Verify that the virtual switch being used for storage has been configured correctly. For more information, 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).
- Log in to the ESXi/ESX host and verify that the host can vmkping the iSCSI targets with the command:
# vmkping target_ip
Note: Ensure that the mapped iSCSI initiator name on the SAN array exactly matches (including upper and lower case) the name listed in the properties of the iSCSI initiator on the ESXi/ESX host to avoid any connectivity issues. If you have jumbo frames configured on the iSCSI network, ensure that you do the testing with the vmkping command. For help on using the vmkping command, run vmkping -h.
If you are running on an ESX host, check that you are able to
pingthe iSCSI target:
# 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).
nc) to verify whether you can reach the iSCSI TCP port (default 3260) on the storage array from the host. For example:
# nc -z 10.1.10.100 3260
Connection to 10.1.10.100 3260 port [tcp/http] succeeded!
Note: The netcat command is available with ESX 4.x and ESXi 4.1 and later.
- 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.
- Verify that the array is configured correctly for use with your ESXi/ESX hosts. Partner with your hardware vendor to ensure that the array is properly configured. For more information, see the iSCSI SAN Configuration Guide.
- Verify that the physical hardware and physical network hardware are functioning correctly. You may have to contact your hardware vendor for information on verifying that your hardware functions correctly.
Note: If your problem still exists after trying the steps in this article:
- 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 Knowledge Base article ID (1003952) in the problem description. For more information, see Filing a Support Request in My VMware (2006985).
- Troubleshooting ESX and ESXi connectivity to iSCSI arrays using hardware initiators (1003951)
- Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts (1003659)
- Configuring and troubleshooting basic software iSCSI setup (1008083)
For translated versions of this article, see:
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.