Figure 1: iPXE Bootloader Workflow 1. Bootloader sends a DHCP discover message, and when the server replies, the Bootloader sends a DHCP request. 2. The DHCP response includes the IP address and boot file name. The boot file name indicates that the boot image is to be retrieved from a TFTP server (tftp://server/filename), FTP server (ftp://userid:password@server/filename), or an HTTP server (http://server/filename). 3. Bootloader downloads and boots the image from the network source. 4. If no DHCP response is received, the bootloader keeps sending DHCP requests forever or for a specified period of time, based on the boot mode configured.
When a timeout occurs, the bootloader reverts to a device-based boot. The device sends DHCP requests forever only if the configured boot mode is ipxe-forever . If the ipxe-timeout boot mode command is configured, DHCP requests are sent for the specified amount of time, and when the timeout expires, device boot mode is activated. Because the current iPXE implementation works only via the management port (GigabitEthernet0/0), DHCP requests sent through the front panel ports are not supported. Note When using a static network configuration to network boot, ROMMON uses the following environment variables (and all of them are required): • BOOT—URLs separated by semicolon (;) to boot from.
• IP_ADDRESS—Statically assigned IP address of a device. • DEFAULT_GATEWAY—Default gateway of the device. • IP_SUBNET_MASK—IPv4 or IPv6 prefix information. IPv4—Subnet mask of the device in the format WWW.XXX.YYY.ZZZ eg. 255.255.255.0. Provisioning iPXE Overview Programmability Configuration Guide, Cisco IOS XE 17.16.x 87