Auto-Provisioning Using the bootfile.bin Option
You can configure the image name with a .bin extension on the server.
- Once a lease is obtained from the server, the device uses the information from the DHCP server to contact the TFTP server to update the image file.
- The device compares the file name of the requested flash image with the image stored in flash memory. In a stacking configuration, the device compares the file name with the image stored in the Active Controller only.
- If the .bin file names match, then the DHCP client skips the flash image download. If auto-provisioning is enabled, the DHCP client proceeds with downloading the configuration files. If the .bin file names are different, the DHCP client downloads the new image from a TFTP server, and then writes the downloaded image to flash memory. In a stacking configuration, the device copies the flash image to flash in all stack member units.
- The code determines which flash (primary or secondary) to use based on how the device is booted or based on the location specified in option 67. Refer to DHCP Auto-Provisioning Enhancements for more details.
- In a stacking configuration, the member units use the same flash as the Active Controller. Once the flash is updated with the newer flash image, the device is reloaded and all member units in a stacking configuration are reloaded as well. If auto-provisioning is enabled, the DHCP client then proceeds to download the configuration files.
- If the DHCP client detects that the new image is older than the current running image, the device continues to reload after a syslog notification that the device is downgrading and may lose the configuration. The following example shows a syslog notification.