7.0

option dhcp6.bootfile-url code 59 = string;
if exists user-class and option user-class = "iPXE" {
# Instruct iPXE to load mboot.efi as secondary bootloader
option dhcp6.bootfile-url "tftp://[xxxx:xxxx:xxxx:xxxx::xxxx]/mboot.efi";
} else {
# Load the snponly.efi configuration of iPXE as initial bootloader
option dhcp6.bootfile-url "tftp://[xxxx:xxxx:xxxx:xxxx::xxxx]/snponly.efi";
}
When a machine attempts to PXE boot, the DHCP server provides an IP address and the location
of the snponly.efi (iPXE) binary file on the TFTP server. iPXE then asks the DHCP server for
the next file to load, and this time the server returns mboot.efi as the filename. iPXE is resident
and the system has HTTP capability. As a result the system can load additional files from an HTTP
server.
Example of Booting Using UEFI HTTP with IPv4
This example shows how to configure an ISC DHCP server to boot ESXi by using native UEFI HTTP
over IPv4 from Web server www.example.com.
#
# ISC DHCP server configuration file snippet. This is not a complete
# configuration file; see the ISC server documentation for details on
# how to configure the DHCP server.
#
allow booting;
allow bootp;
option client-system-arch code 93 = unsigned integer 16;
class "httpclients" {
match if substring(option vendor-class-identifier, 0, 10) = "HTTPClient";
option vendor-class-identifier "HTTPClient";
if option client-system-arch = 00:10 {
# x86_64 UEFI HTTP client
filename = http://www.example.com/esxi/mboot.efi;
}
}
Example of Booting Using UEFI HTTP with IPv6
This example shows how to configure an ISC DHCPv6 server to boot ESXi by using native UEFI
HTTP over IPv6 from Web server www.example.com.
#
# ISC DHCPv6 server configuration file snippet. This is not a complete
# configuration file; see the ISC server documentation for details on
# how to configure the DHCP server.
#
allow booting;
allow bootp;
option dhcp6.bootfile-url code 59 = string;
VMware ESXi Installation and Setup
VMware, Inc. 110