The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 807 - File: showthread.php PHP 7.3.15 (Linux)
File Line Function
/showthread.php 807 errorHandler->error





Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Q: undionly.kpxe and sanhook to iSCSI target
2016-12-02, 17:51 (This post was last modified: 2016-12-02 18:12 by Andromeda_x.)
Post: #1
Q: undionly.kpxe and sanhook to iSCSI target
Hello,

I am attempting to gain access to iSCSI target and no success as of this moment and I am confused why it does not "attach" my target.

System configuration:
1. iSCSI target located on Debian 7 machine (moon.coguar.com 192.168.64) where I can access/attach/mount iSCSI locally
(what confirms that it works properly)
(iSCSI target also added in initiators.allow file for test computer)
2. test computer (192.168.0.30) boots from network (DHCP serves undionly.kext)

iSCSI configuration (Debian 7)
Code:
/etc/iet/iet.conf
....
....
Target iqn.2016-12.com.coguar.moon:storage.lun0
        IncomingUser netadmin NetSecret
        OutgoingUser netadmin NetSecret
        Lun 0 Path=/a/lun.img,Type=fileio
        Alias LUN0
        #MaxConnections 6

/etc/iet/initiators.allow
.....
.....
iqn.2016-12.com.coguar.moon:storage.lun0 192.168.0.30

I boot test computer and get into IPXE then I issue following command

Code:
iPXE> login
iPXE> sanhook iscsi:192.168.0.64::::iqn.2016-12.com.coguar.moon:storage.lun0
Could not open SAN device: No such device (http://ipxe.org/2c0d603d)
iPXE> sanhook iscsi:192.168.0.64:::0:iqn.2016-12.com.coguar.moon:storage.lun0
Could not open SAN device: No such device (http://ipxe.org/2c0d603d)

Snooping on the network traffic by tcpdump shows that computers talk to each other and I am not sure how to troubleshoot the communication

Code:
08:17:33.203150 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [S], seq 89673541, win 8192, options [nop,nop,TS val 1067792 ecr 0,mss 1460], length 0
08:17:33.203328 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [S.], seq 3768665367, ack 89673542, win 14480, options [mss 1460,nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.203446 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [.], ack 1, win 8192, options [nop,nop,TS val 1067792 ecr 260401078], length 0
08:17:33.203564 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [P.], seq 1:49, ack 1, win 8192, options [nop,nop,TS val 1067792 ecr 260401078], length 48
08:17:33.203683 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [.], ack 49, win 14480, options [nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.203834 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [P.], seq 49:178, ack 1, win 8192, options [nop,nop,TS val 1067792 ecr 260401078], length 129
08:17:33.203896 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [.], ack 178, win 15544, options [nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.204030 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [P.], seq 178:181, ack 1, win 8192, options [nop,nop,TS val 1067792 ecr 260401078], length 3
08:17:33.204095 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [.], ack 181, win 15544, options [nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.204407 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [P.], seq 1:49, ack 181, win 15544, options [nop,nop,TS val 260401078 ecr 1067792], length 48
08:17:33.204431 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [F.], seq 49, ack 181, win 15544, options [nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.204539 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [F.], seq 181, ack 49, win 8192, options [nop,nop,TS val 1067792 ecr 260401078], length 0
08:17:33.204637 IP moon.coguar.com.iscsi-target > 192.168.0.30.23941: Flags [.], ack 182, win 15544, options [nop,nop,TS val 260401078 ecr 1067792], length 0
08:17:33.216016 IP 192.168.0.30.23941 > moon.coguar.com.iscsi-target: Flags [.], ack 50, win 8192, options [nop,nop,TS val 1067793 ecr 260401078], length 0

I try to configure a system to net boot diskless test computer through DHCP into iPXE and then ipxe script kicks in to "sanhook" iSCSI target as 0x80 drive and after that to proceede with Windows installation.

Currently script is disabled and I try to find out how "sanhook" works and I am puzzled why I get the message "Can not open SAN device: No such device (http://ipxe.org/2c0d603b)

Code:
#!ipxe

login
sanhook iscsi:192.168.0.64::::iqn.2016-12.com.coguar.moon:storage.lun3

cpuid --ext 29 && set arch amd64 || set arch x86
kernel wimboot
initrd ${arch}/media/Boot/BCD          BCD
initrd ${arch}/media/Boot/boot.sdi     boot.sdi
initrd ${arch}/media/sources/boot.wim  boot.wim
boot

Where is my mistake? What am I doing wrong?

Andromeda X
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Q: undionly.kpxe and sanhook to iSCSI target - Andromeda_x - 2016-12-02 17:51



User(s) browsing this thread: 1 Guest(s)