Quantcast
Channel: VMware Communities: Message List - vSphere™ Storage
Viewing all articles
Browse latest Browse all 5826

Re: iSCSI treating new target LUNs as additional paths for existing target LUNs

$
0
0

Thanks for the suggestions, guys.

 

However, I've looked in both the VI client and the Web client, and I don't see any naa IDs anywhere.  I've confirmed that all columns are being displayed, and I see naa IDs showing up for the local storage devices under "Identifier", but the iSCSI identifiers start with t10.

iscsi-devices.png

Also, I only see the four original (working) disks, each with its own controller device apparently, in that view.  When I click "Manage Paths" on datastore0 and datastore1, that's the only place I see the two new LUNs (datastore4 and datastore5):

datastore0.png

datastore1.png

You can see from those screen shots that I have "Round Robin" selected for my path selection algorithm, but I've tried changing that to each of the other options and it doesn't change the behavior at all.  Seems like path selection is the next step down the chain from the issue here-- i.e. this shouldn't be even considered as an additional path for this LUN, so how to select the paths is a moot point...

 

Also, I have removed and re-discovered these targets upwards of 10-20 times by now (after doing things like restarting the iscsi target daemon and changing target names, etc.), but it ends up with the same result each time.

 

Thanks again for any suggestions.

 

Regards,

Jon Heese


Viewing all articles
Browse latest Browse all 5826

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>