4 node cluster not accepting DHCP leases. CentOS 5

cchristm · 07-11-2008, 12:01 AM

Ok, so here's the deal. I'm setting up a 4 diskless-node cluster, attached to a headnode, in order to run computations. Each node has been set to discover DHCP addresses at boot.

I set up the headnode to broadcast DHCP, via eth1, and give each node a static IP address. After viewing /var/log/messages, I see that the OFFER is given to the right machine, with the right IP address, but the node rejects it. I'm posting the DHCP config file code, the NIC config file for eth1, and the log entry.

/etc/dhcpd.conf says:

ddns-update-style interim;
ignore client-updates;

subnet 10.10.10.0 netmask 255.255.255.0 {
range 10.10.10.1 10.10.10.255;
option subnet-mask 255.255.255.0;
option broadcast-address 10.10.10.255;
option routers 10.10.10.1;
option domain-name "rocketcalc";
option domain-name-servers (has a name server specified);
default-lease-time 21600;
max-lease-time 43200;
}

host rocket1 {
hardware ethernet 00:30:48:73:97:3A;
fixed-address 10.10.10.101;
option host-name "rocket1";
}

/etc/sysconfig/network-scripts/ifcfg-eth1 says:

DEVICE=eth1
BOOTPROTO=static
HWADDR=00:02:B3:E8:CD:BA
ONBOOT=yes
IPADDR=10.10.10.1
NETMASK=255.255.255.0
GATEWAY=10.10.10.1

/var/log/messages says:

Jul 11 00:50:24 mike dhcpd: DHCPDISCOVER from 00:30:48:73:97:3a via eth1
Jul 11 00:50:24 mike dhcpd: DHCPOFFER on 10.10.10.101 to 00:30:48:73:97:3a via eth1
Jul 11 00:50:32 mike dhcpd: DHCPDISCOVER from 00:30:48:73:97:3a via eth1
Jul 11 00:50:32 mike dhcpd: DHCPOFFER on 10.10.10.101 to 00:30:48:73:97:3a via eth1

That's all that happens, and the nodes respond "No boot-filename received". Any help would be great! Cheers!

brianmcgee · 07-11-2008, 02:50 AM

You need to setup a tftp server and propagate the boot file to use. In the tftp-root you should have a pxelinux.0 file and pxelinux.cfg config dir where for example a file like 01-00-1A-AA-BB-CC-DD configures the boot options for server6.

Code:

host server6 {
  filename "/pxelinux.0";
  server-name "192.168.42.6";
  hardware ethernet 00:1A:AA:BB:CC:DD;
  fixed-address 192.168.42.6;
  next-server 192.168.42.1;
}

Code:

# File: 01-00-1A-AA-BB-CC-DD
# This configuration is used to boot the RHEL4 boot image
DEFAULT /bootimages/rhel/5/x86_64/vmlinuz
APPEND lang=en_US keymap=de-latin1 ksdevice=eth0 ip=dhcp method=http://192.168.42.1/yum/rhel/5/latest/x86_64 
initrd=/bootimages/rhel/5/x86_64/initrd.img console=ttyS0,115200

cchristm · 08-11-2008, 12:42 PM

OK, I got a TFTPboot server running, and I'm going to point it to mount /home and read/write and / as read-only. Thanks for your reply. Sorry for the delay, was moving and had no Internet.

Cheers!