Why does Software Management sometimes leave behind image files in the tftpboot directory after an upgrade?
A. Software Management removes the image files from the tftpboot directory after the upgrade unless the tftp fallback job option is set. If the tftp fallback option is set, Software Management uploads the image from the device and leaves it in the tftpboot directory for fallback. Software Management also modifies the boot system commands on the device to add a fallback command to boot from the original image on the Essentials TFTP server if the upgraded image does not boot.
Software Management removes the image files from the tftpboot directory after the upgrade unless the tftp fallback job option is set. If the tftp fallback option is set, Software Management uploads the image from the device and leaves it in the tftpboot directory for fallback. Software Management also modifies the boot system commands on the device to add a fallback command to boot from the original image on the Essentials TFTP server if the upgraded image does not boot.
Related Questions
- After an upgrade, why does Software Management sometimes leave behind image files in the tftpboot directory?
- Why does Software Management sometimes leave behind image files in the tftpboot directory after an upgrade?
- After an upgrade, why does SWIM sometimes leave behind image files in the tftpboot directory?