Hi,
I have an ESXi 5.5.0 (build 1331820) host that I'm trying to roll out some new iSCSI LUNs to, but I'm having trouble with it that I'm hoping someone can help me resolve.
The iSCSI back-end server is running CentOS 6.5 with tgtd providing the iSCSI targets. There are four iSCSI targets in production, with an additional two being created and used here. When I re-scan the iSCSI environment after adding the two new targets, I still only see 4 disks in the Details pane of the iSCSI adapter under Configuration -> Storage Adapters.
Additionally, two of the LUNs stop working, and further inspection indicates that the new iSCSI targets are being considered as separate paths for the two broken LUNs. That is:
Existing LUNs:
iqn.2014-06.storage0.jonheese.local:datastore0
iqn.2014-06.storage1.jonheese.local:datastore1
iqn.2014-06.storage2.jonheese.local:datastore2
iqn.2014-06.storage3.jonheese.local:datastore3
New LUNs:
iqn.2014-06.storage4.jonheese.local:datastore4
iqn.2014-06.storage5.jonheese.local:datastore5
From the "Manage Paths" dialog for each of the disks found, I see that "datastore4" shows up as an additional path for "datastore0" and "datastore5" shows up as an additional path for "datastore1"-- even though the target names are clearly different.
So can anyone tell me why the vSphere iSCSI client is treating distinct iSCSI target LUNs as being multiple paths for the same target? I've compared the tgtd configuration between the original 4 LUNs and the 2 new LUNs, and everything looks correct. They are all tied back to different back-end disks (not that vSphere should know/care about that) and I've written all zeros to the new LUN back-end disks to make sure that there's nothing weird on the disk confusing the iSCSI client.
I can post whatever logs/config/information needed. Thanks in advance.
Regards,
Jon Heese