NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jrsmith
Nov 22, 2013Tutor
ReadyNAS Pro 4.2.24, iSCSI and VMware vSphere ESXi 5.5
I just upgraded to VMware vSphere ESXi 5.5 and I tried to access an iSCSI target (LUN) that was originally created with ESXi 5.0. I added the new initiator IQN to the access control list for the iSCSI...
jrsmith
Nov 23, 2013Tutor
Thanks Chirpa. I realize my ReadyNAS Pro is not on the VMware HCL for ESXi 5.5 yet, but I would not expect to have a problem moving from 5.1U1 to 5.5. I'm pretty sure the problem was related to the iqn length or format that VMware generated. I had only configured my ESXi server with a static IP address and I had not yet given it a hostname or configured DNS when I attempted to configure iSCSI.
Here's the iqn that VMware generated when my server had no hostname
iqn.1998-01.com.vmware:5290ef73-38f4-78e0-4fee-5cf3fc57918a-082e1a10
as soon as I changed the iqn to this
iqn.1998-01.com.vmware:esx55
I could see the LUNs and format them with VMFS.
Here's the iqn that VMware generated when my server had no hostname
iqn.1998-01.com.vmware:5290ef73-38f4-78e0-4fee-5cf3fc57918a-082e1a10
as soon as I changed the iqn to this
iqn.1998-01.com.vmware:esx55
I could see the LUNs and format them with VMFS.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!