vSphere 5.5 Web Client Workflows – Configure Software iSCSI

In our last article, we went through the workflow to add each host to our Distributed Virtual Switch, as well as adding the requisite VMkernel ports for each host. In this article, we’ll build upon that as we configure software iSCSI on our hosts.

Add the Software iSCSI Adapter

1. In the vSphere Web Client Home page, click on the Host and Clusters icon.

2. Click the Host you want to configure (1), Manage (2), then Storage (3).

3. Click the green + symbol (1), then Software iSCSI Adapter (2).

4. Click OK on the Add Software iSCSI Adapter popup.

5. You should now see the software iSCSI adapter, named vmhba33 or something similar.

Configure Network Adapters

Since we already added and configured the VMkernel adapters in an earlier article, there’s only one thing we need to do here – set each iSCSI distributed port group to use only a single uplink. Since this is the same procedure for both distributed port groups, I’ll only show it once.

1. In the vSphere Web Client Home page, click on the Networking icon.

2. Right-click on iSCSI1 (1), then click Edit Settings (2).

3. Click Teaming and failover, then move all uplinks but one into Unused uplinks. In this case, iSCSI1 will have Uplink 3 and iSCSI2 will have Uplink 4. Click OK.

Add the iSCSI Software Adapter Network Port Binding

1. Back in Hosts and Clusters > Host > Manage > Storage, click on vmhba33, Network Port Binding, then the green + to add binding.

2. Choose the first VMkernel adapter in the list, then click OK. Repeat these steps for the second VMkernel adapter.

3. Your Software iSCSI adapter should now show two unused VMkernel adapters.

Add New iSCSI Targets

1. On the iSCSI Software Adapter, click Targets, then Add.

2. Fill in the IP address or FQDN of your iSCSI target. Click OK. Repeat for each additional target.

3. Click Rescan to pick up the new block devices.

4. Click OK to scan for new devices and VMFS volumes.

5. We now see the expected LUNs…

Across both paths

6. Now, rinse and repeat for the other hosts in your cluster.

And that’s it for this article. Check back next time for when we actually do something with these LUNs.


  1. Charles says

    Hi Jason, I enjoy the workflows you’ve put together so far. I’m newbie trying to learn with vSphere 55. I am building a nested lab on VMware workstation 10.0.2 with 2 virtual host each with 2 wmnic just for management, however every time I power on the hosts they become unresponsive at vCenter Server. I have to manually remove the second vmnic, to get it back on business, thing is i then get “up-link redundancy lost”, so I have to add/remove the 2nd vmnic and restart the management network to get it work…. just wonder if there is an easier way to get the 2 vmnic to start without problems once I turn on the hosts. I would like to leave the nested lab powered on 24/7 but I just can’t, so every time I turn it back on to keep learning I get this annoying bug. I’ll appreciate any tips. Regards!

Leave a Reply