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

For anyone who happens upon this same situation, my guess above turned out to be correct.  But in addition to renumbering the scsi_id of each of the LUNs, I also had to renumber the controller_tid field so the controllers on the second node would show up with unique ids.  Here's an example of the config stanza I used for each LUN:

 

<target iqn.2014-06.storage5.jonheese.local:datastore5>

    # backing device for the storage LUN

    backing-store /dev/drbd5

    # SCSI identifier for the storage LUN

    scsi_id IET     00050001

    # SCSI identifier for the controller LUN

    controller_tid 5

    # iSCSI initiator IP address(ed) allowed to connect

    initiator-address 192.168.24.0/24

</target>

 

So it was a tgtd configuration issue after all!  Thanks everyone for asking the questions that led me to the correct answer!

 

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>