iSCSI Authorization failure

Grievous wrote:
Yes, you need to add the IQN of every initiator that will be connecting. it is required for the iSCSI daemon on the ReadyNAS to use the persistent reservations needed to maintain multiple connections otherwise it'll just keep kicking the first client off once the second connects.

Hello,

In the meantime the device is in the datacenter. So I can configure and test it remotely.

-I created 1 target and 3 LUNs
-I added in the LUN configuration all the IQNs if the ESX servers connecting to the storage.
-On the ESX servers I added the IP address of the ReadyNAS to the iSCSI software initiator > Dynamic Discover.
-I let the ESX server do a rescan all
-After the rescan I see in the iSCSI software initiator on the ESX server in tab 'Static Discovery' the Target name of the ReadyNAS.
-But I don't see any storage volumes I can create a datastore on.

So the connection is there, otherwise the ESX servers would not see the name I configured on the ReadyNAS, but I dont have the LUNs available, although I configured the Access Control and added all the Initiator IQNs. (I used copy-paste so no typo's).


Anyone has an idea, all help is appreciated.