remote install problem

On Tue, 18 Jun 2002, Greg MATTHEWS wrote:
> i've just inherited sysadmin duties for a new beowulf which isnt yet working
> properly and i'm having problems with pxe and remote install.
>> pxe seems to work ok in that it will load the kernel and initrd but wont boot
> the loaded kernel unless i interrupt each time and include the following boot
> paramter:
>> nfs:<master node ip address>/kickstart/
The kickstart stuff should be passed on via dhcp.
> without this the kernel will not even begin to boot. this means i have to have
> a keyboard and display plugged in to the node each time i want to install the
> system which is obviously a drawback.
>> my question is, how can include boot params to the kernel? is it an option in
> pxe.conf? if so i have been unable to find it any docs.
>> master node runs:
> dhcpd - serves ip info but not bootfile
a typical entry from our dhcpd.conf for a PXE-installed beowulf node
(one that uses a serial console, hence "beowulf_serial):
###########################################################
# Global Paremeters
###########################################################
option domain-name-servers 152.3.182.5, 152.3.182.3, 152.3.250.1;
option broadcast-address 152.3.183.255;
option nis-domain "phy.duke.edu";
option ntp-servers 152.3.182.3, 152.3.182.4, 182.3.182.5;
option font-servers 152.3.182.7;
option log-servers 152.3.182.10;
use-host-decl-names on;
###########################################################
# Subnets
###########################################################
subnet 192.168.182.0 netmask 255.255.255.0 {
default-lease-time 43200;
max-lease-time 86400;
option routers 192.168.182.1;
option subnet-mask 255.255.255.0;
option domain-name "beowulf.phy.duke.edu";
option broadcast-address 192.168.182.255;
next-server install.phy.duke.edu;
option dhcp-class-identifier "PXEClient";
}
}
....
host r00 {
hardware ethernet 00:e0:81:20:c9:20;
fixed-address 192.168.182.50;
filename "/export/install/linux/rh-7.2/ks/beowulf_serial";
}
where obviously you'll need to change things to match your setup.
install.phy.duke.edu exports the kickstart file via the path indicated,
most of the rest is automagic.
> pxe - proxy dhcp and file info etc
> tftpd
>> please forgive this seemingly simple question...
See if just using dhcp as above is enough. If not, you might need to
include your actual configuration files so people can see where you
might be leaving something out.
rgb
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb at phy.duke.edu