Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Configuring and troubleshooting basic software iSCSI setup
Symptoms
You are experiencing these issues with iSCSI targets:
- Targets are numbered out of sequence.
- Targets do not appear in VMware Infrastructure (VI) Client or VirtualCenter.
- Targets do not appear in vSphere Client or vCenter Server.
Purpose
This article provides basic software iSCSI setup, configuration and troubleshooting.
Resolution
Configuration
From vSphere Client/VMware Infrastructure (VI) Client or vCenter Server:
-
Ensure you have a separate vSwitch for iSCSI.
-
Add a VMKernel and Service Console portgroup and give them appropriate IPs.
Note: A service console may not be needed if working in ESX / ESXi 4.0. -
Log into the ESX host and ensure you can ping the iSCSI array. Run the following command:
# ping 10.1.10.100
PING 10.1.10.100 (10.1.10.100) 56(84) bytes of data.
64 bytes from 10.1.10.100: icmp_seq=0 ttl=64 time=0.766 ms
Note: You do not need to use ping when working with ESX / ESXi 4.0 hosts. -
Log into the ESX host and ensure you can vmkping the iSCSI array. Run the following command:
# vmkping 10.1.10.100
PING 10.1.10.100 (10.1.10.100): 56 data bytes
64 bytes from 10.1.10.100: icmp_seq=0 ttl=64 time=0.940 ms
If you are unable to ping or vmkping the array, you need to correct your network connectivity issue before iSCSI works. -
Log in to vCenter Server, click on the ESX host, and click Configuration.
-
Click Storage Adapters and click on the iSCSI Software Adapter.
-
In the Details pane, click Properties.
-
On the General tab, click Configure, select Enabled, then click OK. You notice that the Status is now enabled, and the iSCSI name has a valid IQN.
-
Configure the iSCSI array to use the IQN you have just created. Generally, you also need to assign storage to the ESX host from the array.
-
Click the Dynamic Discovery tab and click Add.
-
In the Add Send Targets Server area, add the iSCSI array IP to the iSCSI Server field and click OK.
-
After the iSCSI Server is added, click Close. This may take a significant amount of time.
-
Rescan the ESX host storage in the Storage Adapters section.
-
After the rescan has completed, click on the iSCSI initiator to see information about the SAN array, as well as one or more targets.
Troubleshooting
To troubleshoot your setup or re-number your targets for ESX 3.x:
-
Ensure that the array, and possibly each Service Processor, has an entry in each of the following files:
-
/etc/vmkiscsi.conf
Syntax: DiscoveryAddress=<Array_IP>:<iSCSI Port On Array>
For example, DiscoveryAddress=10.200.107.10:3260 -
/var/lib/iscsi/vmkbindings
Syntax: 0 0 <Array_IQN>
For example, 0 0 iqn.1992-08.com.company:sn.84259608
Note: This file is rebuilt on rescan and should be recreated if iSCSI target numbers are out sequence. -
/var/lib/iscsi/vmkdiscovery
Syntax: 0 0 <Array_IQN>
For example, 0 0 iqn.1992-08.com.company:sn.84259608
Note: This should be recreated if iSCSI target numbers are out sequence. The above commands do not apply to ESX 4.0.
-
-
Reboot the ESX host to have the changes take effect.
Note: If the vswitch is using NIC teaming, as a troubleshooting step, try disabling the second NIC and see if iSCSI functions.
For ESX 4.x to 5.x
The iSCSI daemon was updated significantly in ESX/ESXi 4.x and 5.0 and now uses a lite database backend. For more information on ESX 4.0 iSCSI logging, see Verbose logging and information for the software iSCSI initiator (1013283).
Note: If the vswitch is using NIC teaming as a troubleshooting step, try disabling the second NIC to see if iSCSI functions.
Additional Information
For more information on:
- Finding iSCSI targets, see Software iSCSI cannot find targets (8858900).
- Re-numbering iSCSI targets, see Changing the IQN target number on an ESX host (1004808) .
- NIC teaming, see NIC teaming in ESXi and ESX (1004088) and Optimizing iSCSI software initiator performance and NIC teaming (1001251).
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.
Actions
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

