Configuring The File To Boot As The Startup Configuration; Performing Zero Downtime Upgrades For Failover Pairs - Cisco PIX 500 Series Configuration Manual

Configuring the File to Boot as the Startup Configuration

Configuring the File to Boot as the Startup Configuration
By default, the security appliance boots from a startup configuration that is a hidden file. You can
alternatively set any configuration to be the startup configuration by entering the following command:
hostname(config)# boot config {flash:/ | disk0:/ | disk1:/}[ path /] filename
The flash:/ keyword represents the internal Flash memory on the PIX 500 series security appliance. You
can enter flash:/ or disk0:/ for the internal Flash memory on the ASA 5500 series adaptive security
appliance. The disk1:/ keyword represents the external Flash memory on the ASA.

Performing Zero Downtime Upgrades for Failover Pairs

The two units in a failover configuration should have the same major (first number) and minor (second
number) software version. However, you do not need to maintain version parity on the units during the
upgrade process; you can have different versions on the software running on each unit and still maintain
failover support. To ensure long-term compatibility and stability, we recommend upgrading both units
to the same version as soon as possible.
Table 41-1
Table 41-1
Type of Upgrade
Maintenance Release
Minor Release
Major Release
For more details about upgrading the software on a failover pair, refer to the following topics:
•
•
Cisco Security Appliance Command Line Configuration Guide
41-6
shows the supported scenarios for performing zero-downtime upgrades on a failover pair.
Zero-Downtime Upgrade Support
Upgrading an Active/Standby Failover Configuration, page 41-7
Upgrading and Active/Active Failover Configuration, page 41-7
Chapter 41
Support
You can upgrade from any maintenance release to any other
maintenance release within a minor release.
For example, you can upgrade from 7.0(1) to 7.0(4) without first
installing the maintenance releases in between.
You can upgrade from a minor release to the next minor release. You
cannot skip a minor release.
For example, you can upgrade from 7.0 to 7.1. Upgrading from 7.0
directly to 7.2 is not supported for zero-downtime upgrades; you must
first upgrade to 7.1.
You can upgrade from the last minor release of the previous version to
the next major release.
For example, you can upgrade from 7.9 to 8.0, assuming that 7.9 is the
last minor version in the 7.x release.
Managing Software, Licenses, and Configurations
OL-12172-03