Getting all set to boot from gPXE

While booting servers to PXE and then gPXE, some NICs may fail with an error, as shown in Figure 1.

You might wonder why you need to again request for a DHCP IP, since it has already got one at the beginning? The reason is that when the chain loaded gPXE starts up (the PXEenabled NICs download gPXE via TFTP), it issues a fresh DHCP request because it does not see the previous DHCP IP issued for the legacy PXE. The DHCP connection time-out is due to a timing issue with respect to the NIC firmware when the chain load of gPXE occurs.