3.1 Configuring a DHCP Server

Install a DHCP server on the Linux head node. Then, to configure the server, do the following:

  1. Configure the service to run on startup, and change the DHCP Server configuration file (typically located at /etc/dhcp3/dhcp.conf or /etc/dhcp.conf). For Red Hat and SLES, run the following command to configure the service to run on startup:
  2. > chkconfig --level 3 5 dhcpd on
  3. Open the dhcp.conf file and configure preferred options.
  4. Add a "host" configuration section for each host, or for larger ranges of machines or IP address pools, consult the documentation for the DHCP server (man dhcpd).

The following is a sample DHCP Server configuration file:

default-lease-time 600;
max-lease-time 7200;
ddns-update-style ad-hoc; 
subnet 192.168.0.0 netmask 255.255.255.0 {
interface eth0;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option domain-name-servers 192.168.0.1;
option domain-name-servers 192.168.0.1, 192.168.0.2;
option domain-name "server.example.com";
range 192.168.0.100 192.168.0.200;
} 
host node001 {
#hardware MAC address
 hardware ethernet 00:03:47:43:3F:73;
 # this is the unused IP address we will assign temporarily to the PXE client
 fixed-address 192.168.0.90;
#TFTP server address (should be same as Linux head node)
 next-server 192.168.0.1; 
 # path of the bootloader file, relative to tftpd's root (usu. /tftpboot)
 filename "pxelinux.0";
}
...
host nodeXXX {
  hardware ethernet 00:1F:29:C9:34:F6;
  fixed-address 192.168.0.99; 
  next-server 192.168.0.1;  
  filename "pxelinux.0";
}
Caution If your DNS configuration is pointing anywhere other than the Windows head node, you will see unexplained errors in your HPC/WMI configuration. If you intend to use any other DNS server (Windows or Linux), you must set up forwarding zones so lookups to the Windows Domain Controller are answered correctly.

Copyright © 2011 Adaptive Computing Enterprises, Inc.®