[ipxe-devel] [gPXE] Help: sanboot with gpxe-1.0.1-gpxe.kpxe
Lee Eric
openlinuxsource at gmail.com
Tue Oct 16 15:32:18 UTC 2012
Hi mate,
Following is the whole dhcpd.conf content. My question is can I still
use root-path in dhcpd.conf? Because I don't want to create another
file to hold gpxe script.
subnet 192.168.122.0 netmask 255.255.255.0 {
option routers 192.168.122.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.122.255;
option domain-name "garfield.internal";
option domain-name-servers 192.168.122.2, 192.168.122.3;
option ntp-servers 192.168.122.2;
next-server service.garfield.internal;
filename "pxelinux.0";
range 192.168.122.21 192.168.122.50;
range dynamic-bootp 192.168.122.51 192.168.122.70;
}
group base {
host storage.garfield.internal {
hardware ethernet 52:54:00:B9:6B:E5;
option host-name "storage.garfield.internal";
fixed-address storage.garfield.internal;
}
host server.garfield.internal {
hardware ethernet 52:54:00:A5:78:2F;
option host-name "server.garfield.internal";
fixed-address server.garfield.internal;
}
}
group clients {
host sanboot.garfield.internal {
if exists user-class and option user-class = "gPXE" {
option root-path
"iscsi:storage.garfield.internal:6:3260:1:iqn.2012-10.internal.garfield:sanboot";
} else {
filename "gpxe-1.0.1-gpxe.kpxe";
}
hardware ethernet 52:54:00:7B:7E:A7;
option host-name "sanboot.garfield.internal";
fixed-address sanboot.garfield.internal;
}
}
On Tue, Oct 16, 2012 at 11:16 PM, Michael Brown <mbrown at fensystems.co.uk> wrote:
> On 16/10/12 16:04, Lee Eric wrote:
>>
>> host sanboot.garfield.internal {
>> if exists user-class and option user-class = "gPXE" {
>> filename "sanboot.gpxe";
>> } else {
>> filename "gpxe-1.0.1-gpxe.kpxe";
>> }
>> hardware ethernet 52:54:00:7B:7E:A7;
>> option host-name "sanboot.garfield.internal";
>> fixed-address sanboot.garfield.internal;
>> }
>>
>> sanboot.gpxe:
>>
>> #!gpxe
>> sanboot
>> iscsi:storage.garfield.internal:6:3260:1:iqn.2012-10.internal.garfield:sanboot
>>
>> Is that okay?
>
>
> Change all the "gPXE" references to "iPXE", and it looks fine.
>
> Michael
>
More information about the ipxe-devel
mailing list