Deploying iSCSI Volumes: A Simple yet Mind-Bogglingly Easy Missed Step

As a seasoned IT professional with over 20 years of experience in deploying storage solutions, I recently encountered a frustrating issue while setting up a new SAN on my test network. Despite following all the standard procedures and troubleshooting steps, I was unable to present the storage volumes to my ESX hosts. The problem turned out to be an incredibly simple yet easily overlooked detail that had me and many others baffled for days. In this blog post, I will share my experience and the solution to this puzzle, hoping it will save some of you the same amount of time and frustration.

The Setup

I recently replaced my test network’s SAN with a new one, using direct cable connection (10Gbps iSCSI DAC). After creating vDisks and volumes, I presented those volumes to my ESX hosts. However, the hosts could not see the storage LUNS, even though they could see the SAN. The “Add Datastore” option in vSphere showed me no available storage.

Troubleshooting Efforts

I spent two days troubleshooting the issue, trying various solutions suggested by VMware and HPE documentation, as well as input from trusted colleagues and online forums. I manually changed the iQN names in VMware, proved connectivity from VM kernels to the storage array with vmping, updated the controller and card firmware, and even opened a question on Experts Exchange. However, none of these efforts resolved the issue.

The Hidden Gem

Finally, after trawling through old HPE and VMware forum posts, I found a link to a video that caught my attention. It was an Indian chap deploying some iSCSI volumes to a Windows server, even though I don’t speak Hindi, I thought “What the hell, I’ll watch it and make sure (once again) I had not done anything stupid.” As I watched the video, I noticed something so simple and mind-bogglingly easy to miss. When mapping a volume, he did something that no one I had spoken to had mentioned: he manually ticked the iSCSI ports for each LUN (in this example, LUN 10) before applying the rights.

The Key Takeaway

Here’s the key takeaway: when presenting iSCSI volumes, you must manually tick the iSCSI ports for each LUN before applying the rights. The green ticks over the iSCSI ports do not mean the storage is presented through those ports; they simply indicate there’s a working cable in those ports. To properly present the storage, you must go to each port and make sure it’s ticked.

The GUI Design Flaw

I cannot emphasize enough how mind-bogglingly easy it is to miss this step. The GUI design could be improved to draw more attention to this critical step or provide clearer indication that the ports need to be manually ticked. It’s a simple yet crucial detail that, once overlooked, can lead to hours of frustration and wasted time.

Conclusion

In conclusion, deploying iSCSI volumes is generally straightforward, but this seemingly minor detail can cause significant delays. By being aware of the importance of manually ticking the iSCSI ports for each LUN, you can avoid falling into the same trap I did and save yourself a significant amount of time and frustration. Remember that even with years of experience, it’s easy to overlook something as simple yet critical as this. Always double-check your work and consult multiple resources to ensure you haven’t missed anything crucial.