Downloads the firmware on the local device.
By default, firmware download downloads the firmware to the system, reboots the system, and commits the firmware automatically. The user can specify noactivate to download the firmware to the system without activating it (the node is not rebooted). You can run the firmware activate command later to activate the firmware.
Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by default.
Privileged EXEC mode
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt traffic.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before beginning another firmware download.
The fullinstall option enables upgrading the firmware from a 32-bit version to a 64-bit version. Additionally, the fullinstall option enables downgrading the firmware from a 64-bit version to a 32-bit version. This feature assumes the device hardware is capable of supporting 64-bit architecture.
The fullinstall option preserves startup-config, SSH host keys, and licenses. However, though the startup-config is preserved, the system is designed to boot with the default-config. You must manually apply the configs that were preserved, if configurations are compatible. Manually copying the config file uses the copy flash://startup-config running-config command or the copy <file> running-config command.
It is recommended that you back up your running configuration before running the fullinstall command. Use one of the following commands to do so:
copy flash://<config> startup-config
copy scp/ftp/tftp:://<config> startup-config
copy running-config startup-config .
The system then can use the backed up configuration file to restore your configuration during full install.