(2013-05-25 10:13)robinsmidsrod Wrote:  You're using the Intel iSCSI boot support, not iPXE. You'll have to configure the root-path in your ISC DHCPd config according to "Intel iSCSI Remote Boot" specifications.

I found the Intel® iSCSI Remote Boot pages where I downloaded the User Guide (PROINFO.zip). I then unpacked that one and opened up APPS/iSCSI/index.htm which indeed shows that the Intel iSCSI Remote boot agent uses the same syntax for the root-path as iPXE.

You have configured in your dhcpd.conf to only give out the root-path option to iPXE clients. Intel iSCSI Remote Boot is not iPXE, so it sees no root-path option. Remove the conditional and you should be set. Also make sure you provide a hostname, as the Intel iSCSI Remote boot client seems to need that as well.

I do wonder why you're using the Intel iSCSI Remote Boot agent instead of iPXE, though. If you switch your Intel adapter firmware to PXE mode (instead of iSCSI) and chainload iPXE you'll get all the benefits of iPXE scripting AND iSCSI in one package. It's your call. Just don't confuse the two of them. They're different pieces of software (that does the same thing).

Quote:allow booting;
allow bootp;
ddns-update-style none;
log-facility local7;
default-lease-time -1;
max-lease-time 7200;
authoritative;
option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
option ipxe.keep-san code 8 = unsigned integer 8;
option ipxe.bus-id code 177 = string;

subnet 10.0.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
range 10.0.0.64 10.0.0.88;
#option routers 10.0.0.124;

option domain-name-servers 10.0.0.1;
option broadcast-address 10.0.255.255;
option root-path "10.0.0.124:/var/lib/tftpboot/";
next-server 10.0.0.124;
if not exists ipxe.bus-id {
filename "undionly.kpxe";
option routers 10.0.0.1;
} else {
filename "";
option root-path "iscsi:10.0.0.124:::0:iqn.2013-05.com.iscsi-server.host:windows";
option ipxe.keep-san 1;
option routers 0.0.0.0;
}
server-name "host";
server-identifier 10.0.0.124;
}