Simple sanhook failing due to 'has no suitable initiator IQN'

[sethcall]

Environment:
VMWare Fusion with IPXE 'modded' into adapter.

I've also defined two flags in my build
http://ipxe.org/buildcfg/console_vmware
http://ipxe.org/buildcfg/vmware_settings (but I'm not using this feature)
And this is how I built IPXE:
make bin/8086100f.mrom bin/808610d3.mrom bin/10222000.rom bin/15ad07b0.rom DEBUG=scsi:3,iscsi

The following sequence fails:

Code:

ifopen net0
dhcp
sanhook --drive 0x81 iscsi:192.168.1.101:::0:iqn.2001-04.com.example:storage.lun1

Error output upon issuing sanhook command is:

iSCSI 0x1d2a4 has no suitable initiator IQN
iSCSI 0x1d2a4 closed: Invalid argument (http://ipxe.org/1c0d6502)
Could not open SAN device: Invalid argument (http://ipxe.org/1c0d6502)

Issuing the command repeatedly causes the same error.

I've looked at the line of code failing but I don't really have enough context yet to understand what the underlying problem really is. I think somehow I've mistyped the iscsi URI, but I've checked it repeatedly.

Also, I have had this work *rarely*. I'll sometimes change my vmware adapter setting from bridged to NAT (just trying things), but usually I'll reboot at the same time (so I'm not sure if it's a adapter problem or 'ipxe intermittent' problem). And at my work network, I have seen it work work, but very rarely. I usually get it to work but then it fails after.. But at my home network, I haven't seen it work yet.

Finally, I can connect to the ISCSI target on a separate linux machine.

Any pointers? Thanks!
Seth

[Sedorox]

(2012-10-13 15:25)sethcall Wrote:  

Code:

ifopen net0
dhcp
sanhook --drive 0x81 iscsi:192.168.1.101:::0:iqn.2001-04.com.example:storage.lun1

If I'm understanding the command, you're attempting to hook to lun1, yet your specify lun0 in the command. My understanding is that the ...:0:iqn... is the LUN you want to connect to. I would either leave it out (which got it working for me and FreeNAS), or if it is indeed 1, try putting a 1 there.
Someone else may have better information, as I just starting playing around with iPXE and iSCSI booting (via FreeNAS, as mentioned).
I used:

Code:

sanhook iscsi:10.0.3.107::::iqn.2011-03.example.org.istgt:test

[robinsmidsrod]

The message you get and the pointer to http://ipxe.org/err/1c0d6502 seems to indicate that there is something wrong with your initiator-iqn. You might need to set it to something specific to connect properly to your target/volume. The link I just mentioned gives you a pointer to the initiator-iqn setting in iPXE and how you can modify it in a script.

[sethcall]

@robinsmidsrod

Thanks for the pointer; set initiator-iqn immediately made it work.

Code:

ifopen net0
dhcp
set initiator-iqn iqn.2001-04.com.example:storage.lun1
sanhook --drive 0x81 iscsi:193.168.1.101:::0:iqn.2001-04.com.example:storage.lun1

I'm not exactly sure why it's required--like I said in rare cases I don't need to. Need to read up.

@Sedorox: thanks--good pointer. In my case the iqn is correct (if misleading because of the :::0: and storage.lun1)

Seth

[robinsmidsrod]

@sethcall: You should also know that ifopen net0 is redundant. dhcp will automatically try to open all available interfaces in turn if called without any parameters. It will basically issue an ifopen without parameters if an interface was not already opened.