{Project} manages DHCP reservations through a DHCP {SmartProxy}.
{Project} also sets the next-server
and filename
DHCP options.
The next-server
option provides the IP address of the TFTP server to boot from.
This option is not set by default and must be set for each TFTP {SmartProxy}.
You can use the {foreman-installer}
command with the --foreman-proxy-tftp-servername
option to set the TFTP server in the /etc/foreman-proxy/settings.d/tftp.yml
file:
# {foreman-installer} --foreman-proxy-tftp-servername 1.2.3.4
Each TFTP {SmartProxy} then reports this setting through the API and {Project} can retrieve the configuration information when it creates the DHCP record.
When the PXE loader is set to none
, {Project} does not populate the next-server
option into the DHCP record.
If the next-server
option remains undefined, {Project} uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems:
-
DNS timeouts during provisioning
-
Querying of incorrect DNS server. For example, authoritative rather than caching
-
Errors about incorrect IP address for the TFTP server. For example,
PTR record was invalid
If you encounter these problems, check the DNS setup on both {Project} and {SmartProxy}, specifically the PTR record resolution.
The filename
option contains the full path to the file that downloads and executes during provisioning.
The PXE loader that you select for the host or host group defines which filename
option to use.
When the PXE loader is set to none
, {Project} does not populate the filename
option into the DHCP record.
Depending on the PXE loader option, the filename
changes as follows:
PXE loader option | filename entry | Notes |
---|---|---|
PXELinux BIOS |
|
|
PXELinux UEFI |
|
|
iPXE Chain BIOS |
|
|
PXEGrub2 UEFI |
|
x64 can differ depending on architecture |
iPXE UEFI HTTP |
|
Requires the |
Grub2 UEFI HTTP |
|
Requires the |