Configuring a DHCP server on Linux
The BMC Server Automation provisioning process requires a DHCP server, which gives the computer being provisioned an IP address and (in a single-database environment) the location of the Application Server. This topic provides instructions for configuring a DHCP server on Linux.
The topic includes the following sections:
Overview of the requirement
BMC Server Automation requires a Linux DHCP server to be running at least version 3.0p2 of the Internet Software Consortium (ISC) DHCP. The ISC provides a freely redistributable version of DHCP. Earlier versions of ISC DHCP are not compatible with the BMC Server Automation provisioning system.
When you configure a DHCP server on Linux, you must configure the dhcpd.conf file. In that file, you enter values for a standard DHCP server configuration, including the definition of a scope, which sets a start and end of the range of IP addresses being distributed. This range determines the number of servers that can simultaneously access the DHCP server. In addition to the standard configuration, you must include required statements for the BMC Server Automation provisioning process.
To install and configure the ISC DHCP
The following procedure describes how to install and configure the ISC DHCP.
- Download ISC DHCP version 3.0p2 or later from http://www.isc.org/software/dhcp and compile the executable or use a package manager (such as YUM, YaST, or Zypper) to install the dhcpd package.
Edit the dhcpd.conf file, (typically /etc/dhcpd.conf) to match the following example. The lines in red highlight entries that are required or recommended for BMC Server Automation provisioning.
option bl-server code 211 = ip-address;
option bl-port code 212 = unsigned integer 16;
subnet 192.168.4.0 netmask 255.255.255.0
range 192.168.4.200 192.168.4.220;
option subnet-mask 255.255.255.0;
option routers 192.168.4.1;
option domain-name-servers 10.20.21.3;
option netbios-name-servers 10.20.21.3;
option domain-name "netboot.customer.com";
option vendor-class-identifier "PXEClient";
option bl-server 192.168.4.100;
option bl-port 9831;
If you plan to use Unified Extensible Firmware Interface (UEFI), instead of BIOS, for booting hardware over the network during provisioning, perform the additional edits described in Preparing for UEFI booting.
Restart the DHCP server.
Additional notes for required options
The following table provides some additional information for the options highlighted in red in the above example.
|Option||Additional notes for required options|
|allow duplicates||Ensure option is enabled.|
|always-broadcast on||Ensure option is enabled.|
|option bl-server code 211 = ip-address||If you are setting up a multidatabase environment, do not add the statements for options 211 and 212. Instead, specify the IP address or host name of the Application Server as described in Configuring the PXE and TFTP servers. If you are changing from a single-database environment to a multidatabase environment, you must remove the statements for options 211 and 212 from dhcpd.conf.|
|option bl-port code 212 = unsigned integer 16||If you are setting up a multidatabase environment, do not add the statements for options 211 and 212. Instead, specify the IP address or host name of the Application Server as described in Configuring the PXE and TFTP servers. If you are changing from a single-database environment to a multidatabase environment, you must remove the statements for options 211 and 212 from dhcpd.conf.|
|option routers 192.168.4.1|
|option vendor-class-identifier "PXEClient"|
Note: Use the PXEClient option (only if the DHCP and PXE servers are installed on the same system; otherwise, omit that line.
|option bl-server 192.168.4.100|
|option bl-port 9831||The |