HP Insight Control for Linux 7.1 Installation Guide

4.3 Configuring a DHCP server
This section describes the requirements and best practices for configuring a DHCP server for Insight
Control for Linux if you do not elect to configure a DHCP server on the CMS during the Insight
Control for Linux installation process.
4.3.1 DHCP minimum requirements
Serving managed systems with DHCP is an absolute requirement to use the Insight Control for Linux
deployment features, unless you plan on using virtual media to boot managed systems. Most DHCP
servers offer a variety of configuration options to meet the needs of your environment.
Table 10 lists the required DHCP settings for Insight Control for Linux. These settings are not optional.
Additional best practice DHCP configuration options are described in Section 4.3.2 (page 31).
Table 10 DHCP settings required for Insight Control for Linux
Required settingDescriptionOption
The IP address of the CMS management
interface
1
Defines the IP address used by a PXE-booted
host to obtain a network boot image through
TFTP
next-server or
boot-server name
pxelinux.binSpecifies the file name of the PXE binary to
be obtained from the TFTP server (the CMS)
Boot filename
Specify text as the data type.Two custom DHCP option 140 entries used
by SystemImager to obtain its files and scripts
through rsync
option 140
Specify the IP address of the CMS management
interface
Recommended values are
default-lease-time 1209600 seconds
Sets the minimum and maximum lease timesdefault-lease-time
and max-lease-time
(2 weeks) and max-lease-time 1814400
seconds (3 weeks).
HP recommends using fairly long lease times
to help prevent managed systems from having
their IP address changed.
1
The CMS management interface is the Ethernet adapter that is used for communication between the CMS and the
managed systems.
The Insight Control for Linux installation process provides the option to configure a DHCP server
on the CMS. If you answer yes, a basic DHCP server is configured using the configuration
information you specify and with the minimum requirements described in this section.
Example 2 shows the /etc/dhcpd.conf configuration file for a minimally-configured ISC DHCP
server. This is what the configuration file might look like on the CMS if you chose to configure the
CMS as a DHCP server. You could also use this configuration file on a minimally configured external
DHCP server.
NOTE: The settings required by Insight Control for Linux are shown in bold font in the example.
If you need more information about the required settings, see Table 10 (page 30).
Example 2 /etc/dhcpd.conf configuration file with minimum Insight Control for Linux
requirements
#
# DHCP Configuration modified for Insight Control for Linux
#
ddns-update-style interim;
ignore client-updates;
deny duplicates;
30 Configuring the network