############################################################################## # # /etc/dhcpd.conf - configuration file for our DHCP/BOOTP server # Only the portion relevant to cluster node installation is shown. # ########################################################### # Global Paremeters # # Note that we use NIS within our clusters, as our cluster # jobs are typically not file intensive. This can scale # poorly and create a high network and server load -- some # folks instead distribute copies of e.g. /etc/passwd # instead. These options basically tell nodes where to # find dns servers, what their nis domain is, where to # find local ntp servers to remain time synchronized, # and where to log messages. ########################################################### option domain-name-servers 152.3.182.5, 152.3.182.3, 152.3.250.1; option nis-domain "mydomain.edu"; option ntp-servers 152.3.182.3, 152.3.182.4, 182.3.182.5; option log-servers 152.3.182.15; use-host-decl-names on; ########################################################### # Subnets ########################################################### # default lease time 12 hours (43200s) # maximum lease time 24 hours (86400s) ########################################################### # PHY-DUKE has many subnets -- only one (used for cluster # nodes) is shown here. This entry sets defaults used # for the entire cluster. Note that these are all # pxeclients and can boot and install via PXE. ########################################################### shared-network PHY-DUKE { 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.mydomain.edu"; option broadcast-address 192.168.182.255; next-server wanserver.mydomain.edu; option dhcp-class-identifier "PXEClient"; } } ########################################################### # A single bank of the many static IP addresses used in # the department using a private internal subnet (typical # in a cluster). Note that 192.168.x.x addresses do not # route across the Internet backbone and are at least # moderately secure on a WAN basis when used for a cluster # intranet. # # This is the "rama" minicluster -- 16 dual CPU nodes. # Note their very simple entries -- nothing but ethernet # and IP association. Everything else is set by default # for their subnet. rama pxe-installs. ########################################################### host r00 { hardware ethernet 00:e0:81:20:c9:20; fixed-address 192.168.182.50; } host r01 { hardware ethernet 00:e0:81:20:c9:04; fixed-address 192.168.182.51; } host r02 { hardware ethernet 00:e0:81:20:c9:11; fixed-address 192.168.182.52; } host r03 { hardware ethernet 00:e0:81:20:c9:0f; fixed-address 192.168.182.53; } host r04 { hardware ethernet 00:e0:81:20:c1:e5; fixed-address 192.168.182.54; } host r05 { hardware ethernet 00:e0:81:20:c9:78; fixed-address 192.168.182.55; } host r06 { hardware ethernet 00:e0:81:20:c9:76; fixed-address 192.168.182.56; } host r07 { hardware ethernet 00:e0:81:20:c8:d8; fixed-address 192.168.182.57; } host r08 { hardware ethernet 00:e0:81:20:f8:69; fixed-address 192.168.182.58; } host r09 { hardware ethernet 00:e0:81:20:c1:e3; fixed-address 192.168.182.59; } host r10 { hardware ethernet 00:e0:81:20:c9:7b; fixed-address 192.168.182.60; } host r11 { hardware ethernet 00:e0:81:20:c9:7a; fixed-address 192.168.182.61; } host r12 { hardware ethernet 00:e0:81:20:c9:10; fixed-address 192.168.182.62; } host r13 { hardware ethernet 00:e0:81:20:c9:1e; fixed-address 192.168.182.63; } host r14 { hardware ethernet 00:e0:81:21:62:63; fixed-address 192.168.182.64; } host r15 { hardware ethernet 00:e0:81:21:67:54; fixed-address 192.168.182.65; } ########################################################### # Nothing to it.... ###########################################################