Use this procedure to upgrade the ASA application image to a new version, or set the Firewall Threat Defense application image to a new startup version that will be used in a disaster recovery scenario.
When you change the startup version on a Firewall Threat Defense logical device using Firewall Chassis Manager or the FXOS CLI, the application does not immediately upgrade to the new version. The logical device startup version is the version that
Firewall Threat Defense reinstalls to in a disaster recovery scenario. After initial creation of a Firewall Threat Defense logical device, you do not upgrade the Firewall Threat Defense logical device using Firewall Chassis Manager or the FXOS CLI. To upgrade a Firewall Threat Defense logical device, you must use Firewall Management Center. See the System Release Notes for more information: http://www.cisco.com/c/en/us/support/security/defense-center/products-release-notes-list.html.
Also, note that any updates to the Firewall Threat Defense logical device will not be reflected on the and pages in Firewall Chassis Manager. On these pages, the version shown indicates the software version (CSP image) that was used to create the Firewall Threat Defense logical device.

Note
|
When you set the startup version for Firewall Threat Defense, startup version of the application gets updated. Hence, you must manually reinstall the application or reinitialize the
blade to apply the selected version. This procedure is not the equivalent of upgrading or downgrading the Firewall Threat Defense software, rather a complete reinstallation (reimage). Therefore, the application gets deleted and the existing configuration
gets lost.
|
When you change the startup version on an ASA logical device, the ASA upgrades to that version and all configuration is restored.
Use the following workflows to change the ASA startup version, depending on your configuration:

Note
|
When you set the startup version for ASA, the application gets automatically restarted. This procedure is the equivalent of
upgrading or downgrading the ASA software (existing configuration gets preserved).
|
ASA High Availability -
-
Change the logical device image version(s) on the standby unit.
-
Make the standby unit active.
-
Change the application version(s) on the other unit.
ASA Inter-Chassis Cluster -
-
Change the startup version on the data unit.
-
Make the data unit the control unit.
-
Change the startup version on the original control unit (now data).