Re: kickstart not finding configuration file over simple network connection

extraspecialbitter wrote:
I'm having some difficulty initiating a RedHat kickstart install over
a simple network connection consisting of a
Linux laptop serving as the DHCP/TFTP server, a Proliant DL585 - the
PXE client - and a Netgear switch. The PXE
client gets an IP address from the DHCP server, loads vmlinuz and
initrd.img and then begins executing
/tftpboot/pxelinux.cfg/default. It seems to get stuck trying to
invoke kickstart, however. After loading all of
the modules - including network drivers tg3 and e1000 - I get dropped
into anaconda and prompted for network
information. The console output at this point follows:

[code]
* load module set done
* getting kickstart file
* sending dhcp request through device eth2
* waiting for link...
* 0 seconds.
* running dhcp for eth2
* pump told us: No DHCP reply received
[/code]

This seems bizarre, since DHCP did get me to the /tftpboot directory
on the DHCP server, but can't seem to find the Kickstart configuration
file, which is served up via NFS.

My dhcpd.conf looks like this:

[code]allow booting;
allow bootp;
ddns-update-style none;
deny unknown-clients;
authoritative;

subnet 192.168.37.0 netmask 255.255.255.0 {

group {
filename "pxelinux.0";
server-identifier 192.168.37.2;
next-server 192.168.37.2;

host clone {
hardware ethernet 00:10:18:10:67:CA;
fixed-address 192.168.37.3;
}
}
}
[/code]

and /tftpboot/pxelinux.cfg/default:

[code]say PXE kickstart configuration file
default ks
prompt 1
timeout 300
label linux
kernel vmlinuz
append initrd=initrd.img lang= devfs=nomount ramdisk_size=9216
label ks
kernel vmlinuz
append ksdevice=eth2 ks=nfs:192.168.37.3:/tftpboot/ha2_net.ks.cfg
initrd=initrd.img network=1
[/code]

Does your system have multiple network ports? The Anaconda installer and boot kernel sometimes get confused about which network port is which. If they're not all on the same subnet, and all configured with similar network setups, this can get nasty.

Also, I don't recommend NFS for this until you've got it all straightened out. Mounting and unmounting NFS directories can get very nasty for both the client and the server: stick with HTTP for the short term.
.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • Re: My Server is not anymore seen on network plese help ?
    ... here is the client ipconfig. ... wich as adress 192.168.1.102 which it is not reachable for some reason ... As you can see the DHCP ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)