Guest

Cisco ASA 5500-X Series Next-Generation Firewalls

Upgrade to ASA 9.0 and ASDM 7.0

  • Viewing Options

  • PDF (259.6 KB)
  • EPUB (74.1 KB)
  • MOBI (111.2 KB)
  • Feedback

Table of Contents

Upgrade to ASA 9.0 and ASDM 7.0

Upgrading the Software

Upgrade Path

Configuration Migration in 9.0

IPv6 ACLs

Any Keyword

View Your Current Version

Download the Software from Cisco.com

Upgrade a Standalone Unit

Upgrade Using the CLI

(ASDM) Upgrade from Your Local Computer

(ASDM 6.3 or Later) Upgrade Using the Cisco.com Wizard

(ASDM 6.0 Through ASDM 6.2) Upgrade Using the Cisco.com Wizard

Upgrading a Failover Pair or ASACluster

Upgrade an Active/Standby Failover Pair

Upgrade an Active/Active Failover Pair

Upgrade an ASA Cluster

Upgrade to ASA 9.0 and ASDM 7.0

Released: August 21, 2014

 

Upgrading the Software

This section describes how to upgrade to the latest version and includes the following topics:

Upgrade Path

See the following table for the upgrade path for your version. Some versions require an interim upgrade before you can upgrade to the latest version. An important fix was added to Version 9.0(2) that make it possible to upgrade easily to later versions, so we recommend upgrading to 9.0(2) or later.


Note There are no special requirements for Zero Downtime Upgrades for failover and ASA clustering with the following exception. Upgrading ASA clustering from 9.0(1) to 9.0(2) or later: due to CSCue72961, hitless upgrading is not supported.


 

Current ASA Version
First Upgrade to:
Then Upgrade to:

8.2(x) and earlier

8.4(6)

9.0(2) or later

8.3(x)

8.4(6)

9.0(2) or later

8.4(x)

9.0(2) or later

8.5(1)

9.0(2) or later

8.6(1)

9.0(2) or later

9.0(1) or later

9.0(2) or later

Configuration Migration

Depending on your current version, you might experience one or more configuration migrations when you upgrade. For example, when upgrading from 8.0 to 9.4, you will experience all of these migrations:

Configuration Migration in 9.0

The following ACL configurations will be migrated when upgrading to Version 9.0.

IPv6 ACLs

IPv6 ACLs (ipv6 access-list) will be migrated to extended ACLs (access-list extended); IPv6 ACLs are no longer supported.

If IPv4 and IPv6 ACLs are applied on the same direction of an interface (access-group command), then the ACLs are merged:

  • If both IPv4 and IPv6 ACLs are not used anywhere other than the access-group, then the name of the IPv4 ACL is used for the merged ACL; the IPv6 access-list is removed.
  • If at least one of the ACLs is used in another feature, then a new ACL is created with the name IPv4-ACL-name _ IPv6-ACL-name ; the in-use ACL(s) continue to be used for other features. ACLs not in use are removed. If the IPv6 ACL is in use for another feature, it is migrated to an extended ACL of the same name.

Any Keyword

Now that ACLs support both IPv4 and IPv6, the any keyword now represents “all IPv4 and IPv6 traffic.” Any existing ACLs that use the any keyword will be changed to use the any4 keyword, which denotes “all IPv4 traffic.”

In addition, a separate keyword was introduced to designate “all IPv6 traffic”: any6.


Note The any4 and any6 keywords are not available for all commands that use the any keyword. For example, the NAT feature uses only the any keyword; any represents IPv4 traffic or IPv6 traffic depending on the context within the specific NAT command.


View Your Current Version

(CLI) Use the show version command to verify the software version of your ASA. (ASDM) The software version appears on the ASDM home page; view the home page to verify the software version of your ASA.

Download the Software from Cisco.com

If you are using the ASDM Upgrade Wizard, you do not have to pre-download the software. If you are manually upgrading, for example for a failover upgrade, download the images to your local computer.

If you have a Cisco.com login, you can obtain the OS and ASDM images from the following website:

http://www.cisco.com/cisco/software/navigator.html?mdfid=279513386

(CLI) This procedure assumes you put the images on a TFTP server, although other server types are supported.

Upgrade a Standalone Unit

This section describes how to install the ASDM and operating system (OS) images.


Note If the ASA is running Version 8.0 or later, then you can upgrade to the latest version of ASDM (and disconnect and reconnect to start running it) before upgrading the OS. The exception is for ASA versions that are not supported by the latest ASDM version; for example, ASA 8.5. In that case, follow the instructions for pre-8.0 versions (ASDM 5.2 and earlier).

If the ASA is running a version earlier than 8.0, then use the already installed version of ASDM to upgrade both the OS and ASDM to the latest versions, and then reload.


Upgrade Using the CLI

Procedure

This procedure uses TFTP. For FTP or HTTP, see the copy command.


Step 1 (If there is a configuration migration) Show the configuration on the terminal so that you can back up your configuration:

more system:running-config
 

Copy the output from this command, then paste the configuration in to a text file. For other methods of backing up, see the configuration guide.

Step 2 Copy the ASA software to the active unit flash memory:

copy tftp://server[/path]/asa_image_name {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname# copy tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

For other methods than TFTP, see the copy command.

Step 3 Copy the ASDM image to the active unit flash memory:

copy tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

hostname# copy tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 4 If you are not already in global configuration mode, access global configuration mode:

configure terminal
 

Step 5 Show the current boot images configured (up to 4):

show running-config boot system
 

Example:

hostname(config)# show running-config boot system
boot system disk0:/cdisk.bin
boot system disk0:/asa914-smp-k8.bin
 

The ASA uses the images in the order listed; if the first image is unavailable, the next image is used, and so on. You cannot insert a new image URL at the top of the list; to specify the new image to be first, you must remove any existing entries, and enter the image URLs in the order desired, according to Step 6 and Step 7.

Step 6 Remove any existing boot image configurations so that you can enter the new boot image as your first choice:

no boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# no boot system disk0:/cdisk.bin
hostname(config)# no boot system disk0:/asa914-smp-k8.bin
 

Step 7 Set the ASA image to boot (the one you just uploaded):

boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# boot system disk0://asa904-smp-k8.bin
 

Repeat this command for any backup images that you want to use in case this image is unavailable. For example, you can re-enter the images that you previously removed in Step 6.

Step 8 Set the ASDM image to use (the one you just uploaded):

asdm image {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

hostname(config)# asdm image disk0:/asdm-701.bin
 

You can only configure one ASDM image to use, so you do not need to first remove the existing configuration.

Step 9 Save the new settings to the startup configuration:

write memory
 

Step 10 Reload the ASA:

reload
 


 

(ASDM) Upgrade from Your Local Computer

The Upgrade Software from Local Computer tool lets you upload an image file from your computer to the flash file system to upgrade the ASA.

To upgrade software from your computer, perform the following steps.

Procedure


Step 1 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 2 In the main ASDM application window, choose Tools > Upgrade Software from Local Computer.

The Upgrade Software dialog box appears.

Step 3 From the Image to Upload drop-down list, choose ASDM.

Step 4 In the Local File Path field, enter the local path to the file on your computer or click Browse Local Files to find the file on your PC.

Step 5 In the Flash File System Path field, enter the path to the flash file system or click Browse Flash to find the directory or file in the flash file system.

Step 6 Click Upload Image. The uploading process might take a few minutes.

Step 7 Repeat Step 2 through Step 6, choosing ASA from the Image to Upload drop-down list. You can also use this procedure to upload other file types.

Step 8 Configure the ASA to use the new images.

a. Choose Configuration > Device Management > System/Image Configuration > Boot Image/Configuration.

b. In the Boot Configuration table, click Add to add the new image (if you have fewer than four images listed); or you can choose an existing image and click Edit to change it to the new one.

If you do not specify an image, the ASA searches the internal flash memory for the first valid image to boot; we recommend booting from a specific image.

c. Click Browse Flash, choose the OS image, and click OK.

d. Click OK to return to the Boot Image/Configuration pane.

e. Make sure the new image is the first image in the table by using the Move Up button as needed.

f. In the ASDM Image Configuration area, click Browse Flash, choose the ASDM image, and click OK.

g. Click Apply.

Step 9 Choose File > Save Running Configuration to Flash to save your configuration changes.

Step 10 Choose Tools > System Reload to reload the ASA.

A new window appears that asks you to verify the details of the reload. Click the Save the running configuration at the time of reload radio button, choose a time to reload (for example, Now), and click Schedule Reload.

Once the reload is in progress, a Reload Status window appears that indicates that a reload is being performed. An option to exit ASDM is also provided.

Step 11 After the ASA reloads, restart ASDM.


 

(ASDM 6.3 or Later) Upgrade Using the Cisco.com Wizard

The Upgrade Software from Cisco.com Wizard lets you automatically upgrade the ASDM and ASA to more current versions.

In this wizard, you can do the following:

  • Choose an ASA image file and/or ASDM image file to upgrade.

Note ASDM downloads the latest image version, which includes the build number. For example, if you are downloading 9.0(2), the dowload might be 9.0(2.8). This behavior is expected, so you may proceed with the planned upgrade.


  • Review the upgrade changes that you have made.
  • Download the image or images and install them.
  • Review the status of the installation.
  • If the installation completed successfully, restart the ASA to save the configuration and complete the upgrade.

Procedure


Step 1 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 2 Choose Tools > Check for ASA/ASDM Updates.

In multiple context mode, access this menu from the System.

The Cisco.com Authentication dialog box appears.

Step 3 Enter your assigned Cisco.com username and the Cisco.com password, and then click Login.

The Cisco.com Upgrade Wizard appears.


Note If there are no upgrade available, a dialog box appears. Click OK to exit the wizard.


Step 4 Click Next to display the Select Software screen.

The current ASA version and ASDM version appear.

Step 5 To upgrade the ASA version and ASDM version, perform the following steps:

a. In the ASA area, check the Upgrade to check box, and then choose an ASA version to which you want to upgrade from the drop-down list.

b. In the ASDM area, check the Upgrade to check box, and then choose an ASDM version to which you want to upgrade from the drop-down list.

Step 6 Click Next to display the Review Changes screen.

Step 7 Verify the following items:

    • The ASA image file and/or ASDM image file that you have downloaded are the correct ones.
    • The ASA image file and/or ASDM image file that you want to upload are the correct ones.
    • The correct ASA boot image has been selected.

Step 8 Click Next to start the upgrade installation.

You can then view the status of the upgrade installation as it progresses.

The Results screen appears, which provides additional details, such as the upgrade installation status (success or failure).

During the upgrade process from Version 8.2(1) to Version 8.3(1), the following files are automatically saved to flash memory:

    • The startup configuration
    • The per-context configuration
    • The bootup error log, which includes any migration messages

If there is insufficient memory to save the configuration files, an error message appears on the console of the ASA and is saved in the bootup error log file. All previously saved configuration files are also removed.

Step 9 If the upgrade installation succeeded, for the upgrade versions to take effect, check the Save configuration and reload device now check box to restart the ASA, and restart ASDM.

Step 10 Click Finish to exit the wizard and save the configuration changes that you have made.


Note To upgrade to the next higher version, if any, you must restart the wizard.



 

(ASDM 6.0 Through ASDM 6.2) Upgrade Using the Cisco.com Wizard

Procedure


Step 1 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 2 From the Tools menu, choose Tools > Upgrade Software from Cisco.com.

In multiple context mode, access this menu from the System.

The Upgrade Software from Cisco.com Wizard appears.

Step 3 Click Next.

The Authentication screen appears.

Step 4 Enter your Cisco.com username and password, and click Next.

The Image Selection screen appears.

Step 5 Check the Upgrade the ASA version check box and the Upgrade the ASDM version check box to specify the most current images to which you want to upgrade, and click Next.

The Selected Images screen appears.

Step 6 Verify that the image file you have selected is the correct one, and then click Next to start the upgrade.

The wizard indicates that the upgrade will take a few minutes. You can then view the status of the upgrade as it progresses.

The Results screen appears. This screen provides additional details, such as whether the upgrade failed or whether you want to save the configuration and reload the ASA.

If you upgraded the ASA version and the upgrade succeeded, an option to save the configuration and reload the ASA appears.

Step 7 Click Yes.

For the upgrade versions to take effect, you must save the configuration, reload the ASA, and restart ASDM.

Step 8 Click Finish to exit the wizard when the upgrade is finished.

Step 9 After the ASA reloads, restart ASDM.


 

Upgrading a Failover Pair or ASA Cluster

To perform a zero downtime upgrade, you need to upgrade each unit in a particular order.

Upgrade an Active/Standby Failover Pair

To upgrade the Active/Standby failover pair, perform the following steps.

Before You Begin

(CLI) Perform these steps on the active unit.

Procedure

For CLI:


Step 1 (If there is a configuration migration) Show the configuration on the terminal so that you can back up your configuration:

more system:running-config
 

Example:

active# more system:running-config
 

Copy the output from this command, then paste the configuration in to a text file. For other methods of backing up, see the configuration guide.

Step 2 Copy the ASA software to the active unit flash memory:

copy tftp://server[/path]/asa_image_name {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

active# copy tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

For other methods than TFTP, see the copy command.

Step 3 Copy the software to the standby unit; be sure to specify the same path as for the active unit:

failover exec mate copy /noconfirm tftp://server[/path]/filename {disk0:/ | disk1:/}[path/]filename
 

Example:

active# failover exec mate copy /noconfirm tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

Step 4 Copy the ASDM image to the active unit flash memory:

copy tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

active# copy tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 5 Copy the ASDM image to the standby unit; be sure to specify the same path as for the active unit:

failover exec mate copy /noconfirm tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

active# failover exec mate copy /noconfirm tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 6 If you are not already in global configuration mode, access global configuration mode:

configure terminal
 

Step 7 Show the current boot images configured (up to 4):

show running-config boot system
 

Example:

hostname(config)# show running-config boot system
boot system disk0:/cdisk.bin
boot system disk0:/asa847-smp-k8.bin
 

The ASA uses the images in the order listed; if the first image is unavailable, the next image is used, and so on. You cannot insert a new image URL at the top of the list; to specify the new image to be first, you must remove any existing entries, and enter the image URLs in the order desired, according to Step 8 and Step 9.

Step 8 Remove any existing boot image configurations so that you can enter the new boot image as your first choice:

no boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# no boot system disk0:/cdisk.bin
hostname(config)# no boot system disk0:/asa847-smp-k8.bin
 

Step 9 Set the ASA image to boot (the one you just uploaded):

boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# boot system disk0://asa904-smp-k8.bin
 

Repeat this command for any backup images that you want to use in case this image is unavailable. For example, you can re-enter the images that you previously removed in Step 8.

Step 10 Set the ASDM image to use (the one you just uploaded):

asdm image {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

hostname(config)# asdm image disk0:/asdm-701.bin
 

You can only configure one ASDM image to use, so you do not need to first remove the existing configuration.

Step 11 Save the new settings to the startup configuration:

write memory
 

Step 12 Reload the standby unit to boot the new image:

failover reload-standby
 

Wait for the standby unit to finish loading. Use the show failover command to verify that the standby unit is in the Standby Ready state.

Step 13 Force the active unit to fail over to the standby unit:

no failover active
 

Step 14 Reload the former active unit (now the new standby unit):

reload

 

If you want to restore this unit to be active after it reloads, enter the failover active command.


 

For ASDM:


Step 1 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 2 On the active unit, in the main ASDM application window, choose Tools > Upgrade Software from Local Computer.

The Upgrade Software dialog box appears.

Step 3 From the Image to Upload drop-down list, choose ASDM.

Step 4 In the Local File Path field, enter the local path to the file on your computer or click Browse Local Files to find the file on your PC.

Step 5 In the Flash File System Path field, enter the path to the flash file system or click Browse Flash to find the directory or file in the flash file system.

Step 6 Click Upload Image. The uploading process might take a few minutes.

Step 7 You are prompted to set this image as the ASDM image. Click Yes.

Step 8 You are reminded to exit ASDM and save the configuration. Click OK. You exit the Upgrade tool. Note: You will save the configuration and reload ASDM after you upgrade the ASA software.

Step 9 Repeat Step 2 through Step 8, choosing ASA from the Image to Upload drop-down list.

Step 10 Click the Save icon on the toolbar to save your configuration changes.

Step 11 Connect ASDM to the standby unit, and upload the ASA and ASDM software according to Step 2 through Step 9, using the same file locations you used on the active unit.

Step 12 Choose Tools > System Reload to reload the standby ASA.

A new window appears that asks you to verify the details of the reload.

a. Click the Save the running configuration at the time of reload radio button (the default).

b. Choose a time to reload (for example, Now, the default).

c. Click Schedule Reload.

Once the reload is in progress, a Reload Status window appears that indicates that a reload is being performed. An option to exit ASDM is also provided.

Step 13 After the standby ASA reloads, restart ASDM and connect to the standby unit to make sure it is running.

Step 14 Connect ASDM to the active unit again.

Step 15 Force the active unit to fail over to the standby unit by choosing Monitoring > Properties > Failover > Status, and clicking Make Standby.

Step 16 Choose Tools > System Reload to reload the (formerly) active ASA.

A new window appears that asks you to verify the details of the reload.

a. Click the Save the running configuration at the time of reload radio button (the default).

b. Choose a time to reload (for example, Now, the default).

c. Click Schedule Reload.

Once the reload is in progress, a Reload Status window appears that indicates that a reload is being performed. An option to exit ASDM is also provided.

After the ASA comes up, it will now be the standby unit.


 

Upgrade an Active/Active Failover Pair

To upgrade two units in an Active/Active failover configuration, perform the following steps.

Before You Begin

Perform these steps in the system execution space. (CLI) Also perform these steps on the primary unit.

Procedure

For CLI:


Step 1 (If there is a configuration migration) Show the configuration on the terminal so that you can back up your configuration:

more system:running-config
 

Copy the output from this command, then paste the configuration in to a text file. For other methods of backing up, see the configuration guide.

Step 2 Copy the ASA software to the primary unit flash memory:

copy tftp://server[/path]/asa_image_name {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

primary# copy tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

For other methods than TFTP, see the copy command.

Step 3 Copy the software to the secondary unit; be sure to specify the same path as for the primary unit:

failover exec mate copy /noconfirm tftp://server[/path]/filename {disk0:/ | disk1:/}[path/]filename
 

Example:

primary# failover exec mate copy /noconfirm tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

Step 4 Copy the ASDM image to the primary unit flash memory:

copy tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

primary# copy tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 5 Copy the ASDM image to the secondary unit; be sure to specify the same path as for the active unit:

failover exec mate copy /noconfirm tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

primary# failover exec mate copy /noconfirm tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 6 Make both failover groups active on the primary unit:

failover active group 1
failover active group 2
 

Step 7 If you are not already in global configuration mode, access global configuration mode:

configure terminal
 

Example:

primary(config)# configure terminal
 

Step 8 Show the current boot images configured (up to 4):

show running-config boot system
 

Example:

hostname(config)# show running-config boot system
boot system disk0:/cdisk.bin
boot system disk0:/asa847-smp-k8.bin
 

The ASA uses the images in the order listed; if the first image is unavailable, the next image is used, and so on. You cannot insert a new image URL at the top of the list; to specify the new image to be first, you must remove any existing entries, and enter the image URLs in the order desired, according to Step 9 and Step 10.

Step 9 Remove any existing boot image configurations so that you can enter the new boot image as your first choice:

no boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# no boot system disk0:/cdisk.bin
hostname(config)# no boot system disk0:/asa847-smp-k8.bin
 

Step 10 Set the ASA image to boot (the one you just uploaded):

boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# boot system disk0://asa904-smp-k8.bin
 

Repeat this command for any backup images that you want to use in case this image is unavailable. For example, you can re-enter the images that you previously removed in Step 9.

Step 11 Set the ASDM image to use (the one you just uploaded):

asdm image {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

hostname(config)# asdm image disk0:/asdm-701.bin
 

You can only configure one ASDM image to use, so you do not need to first remove the existing configuration.

Step 12 Save the new settings to the startup configuration:

write memory
 

Step 13 Reload the secondary unit to boot the new image:

failover reload-standby
 

Wait for the secondary unit to finish loading. Use the show failover command to verify that both failover groups are in the Standby Ready state.

Step 14 Force both failover groups to become active on the secondary unit:

no failover active group 1
no failover active group 2
 

Step 15 Reload the primary unit:

reload
 

If the failover groups are configured with the preempt command, they automatically become active on their designated unit after the preempt delay has passed. If the failover groups are not configured with the preempt command, you can return them to active status on their designated units using the failover active group command.


 

For ASDM:


Step 1 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 2 On the primary unit, in the main ASDM application window, choose Tools > Upgrade Software from Local Computer.

The Upgrade Software dialog box appears.

Step 3 From the Image to Upload drop-down list, choose ASDM.

Step 4 In the Local File Path field, enter the local path to the file on your computer or click Browse Local Files to find the file on your PC.

Step 5 In the Flash File System Path field, enter the path to the flash file system or click Browse Flash to find the directory or file in the flash file system.

Step 6 Click Upload Image. The uploading process might take a few minutes.

Step 7 You are prompted to set this image as the ASDM image. Click Yes.

Step 8 You are reminded to exit ASDM and save the configuration. Click OK. You exit the Upgrade tool. Note: You will save the configuration and reload ASDM after you upgrade the ASA software.

Step 9 Repeat Step 2 through Step 8, choosing ASA from the Image to Upload drop-down list.

Step 10 Click the Save icon on the toolbar to save your configuration changes.

Step 11 Make both failover groups active on the primary unit by choosing Monitoring > Failover > Failover Group #, where # is the number of the failover group you want to move to the primary unit, and clicking Make Active.

Step 12 Connect ASDM to the secondary unit, and upload the ASA and ASDM software according to Step 2 through Step 9, using the same file locations you used on the active unit.

Step 13 Choose Tools > System Reload to reload the secondary ASA.

A new window appears that asks you to verify the details of the reload.

a. Click the Save the running configuration at the time of reload radio button (the default).

b. Choose a time to reload (for example, Now, the default).

c. Click Schedule Reload.

Once the reload is in progress, a Reload Status window appears that indicates that a reload is being performed. An option to exit ASDM is also provided.

Step 14 Connect ASDM to the primary unit, and check when the secondary unit reloads by choosing Monitoring > Failover > System.

Step 15 After the secondary unit comes up, force the primary unit to fail over to the secondary unit by choosing Monitoring > Properties > Failover > System, and clicking Make Standby.

Step 16 Choose Tools > System Reload to reload the (formerly) active ASA.

A new window appears that asks you to verify the details of the reload.

a. Click the Save the running configuration at the time of reload radio button (the default).

b. Choose a time to reload (for example, Now, the default).

c. Click Schedule Reload.

Once the reload is in progress, a Reload Status window appears that indicates that a reload is being performed. An option to exit ASDM is also provided.

If the failover groups are configured with Preempt Enabled, they automatically become active on their designated unit after the preempt delay has passed. If the failover groups are not configured with Preempt Enabled, you can return them to active status on their designated units using the Monitoring > Failover > Failover Group # pane.


 

Upgrade an ASA Cluster

To upgrade all units in an ASA cluster, perform the following steps on the master unit. For multiple context mode, perform these steps in the system execution space.

Procedure

For CLI:


Step 1 (If there is a configuration migration) Back up your configuration file:

more system:running-config
 

Copy the output from this command, then paste the configuration in to a text file. For other methods of backing up, see the general operations configuration guide.

Step 2 Copy the ASA software to all units in the cluster:

cluster exec copy /noconfirm tftp://server[/path]/asa_image_name {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

master# cluster exec copy /noconfirm tftp://10.1.1.1/asa904-smp-k8.bin disk0:/asa904-smp-k8.bin
 

For other methods than TFTP, see the copy command.

Step 3 Copy the ASDM image to all units in the cluster:

cluster exec copy /noconfirm tftp://server[/path]/asdm_image_name {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

master# cluster exec copy /noconfirm tftp://10.1.1.1/asdm-701.bin disk0:/asdm-701.bin
 

Step 4 If you are not already in global configuration mode, access global configuration mode:

configure terminal
 

Step 5 Show the current boot images configured (up to 4):

show running-config boot system
 

Example:

hostname(config)# show running-config boot system
boot system disk0:/cdisk.bin
boot system disk0:/asa847-smp-k8.bin
 

The ASA uses the images in the order listed; if the first image is unavailable, the next image is used, and so on. You cannot insert a new image URL at the top of the list; to specify the new image to be first, you must remove any existing entries, and enter the image URLs in the order desired, according to Step 6 and Step 7.

Step 6 Remove any existing boot image configurations so that you can enter the new boot image as your first choice:

no boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# no boot system disk0:/cdisk.bin
hostname(config)# no boot system disk0:/asa847-smp-k8.bin
 

Step 7 Set the ASA image to boot (the one you just uploaded):

boot system {disk0:/ | disk1:/}[path/]asa_image_name
 

Example:

hostname(config)# boot system disk0://asa904-smp-k8.bin
 

Repeat this command for any backup images that you want to use in case this image is unavailable. For example, you can re-enter the images that you previously removed in Step 6.

Step 8 Set the ASDM image to use (the one you just uploaded):

asdm image {disk0:/ | disk1:/}[path/]asdm_image_name
 

Example:

hostname(config)# asdm image disk0:/asdm-701.bin
 

You can only configure one ASDM image to use, so you do not need to first remove the existing configuration.

Step 9 Save the new settings to the startup configuration:

write memory
 

Step 10 Reload each slave unit when you repeat this command for each unit name:

cluster exec unit slave-unit reload noconfirm
 

Example:

master# cluster exec unit unit2 reload noconfirm
 

To avoid connection loss and allow traffic to stabilize, wait for each unit to come back up (approximately 5 minutes) before reloading the next unit. To view member names, enter cluster exec unit ?, or enter the show cluster info command.

Step 11 Disable clustering on the master unit:

no enable
 

Wait for 5 minutes for a new master to be selected and traffic to stabilize. Do not enter write memory ; when the master unit reloads, you want clustering to be enabled on it.

Step 12 Reload the master unit:

reload noconfirm
 

A new election takes place for a new master unit. When the former master unit rejoins the cluster, it will be a slave.


 

For ASDM:


Step 1 Launch ASDM on the master unit.

Step 2 (If there is a configuration migration) In ASDM, back up your existing configuration using the Tools > Backup Configurations tool.

Step 3 In the main ASDM application window, choose Tools > Upgrade Software from Local Computer.

The Upgrade Software from Local Computer dialog box appears.

Step 4 Click the All devices in the cluster radio button.

The Upgrade Software dialog box appears.

Step 5 From the Image to Upload drop-down list, choose ASDM.

Step 6 In the Local File Path field, enter the local path to the file on your computer or click Browse Local Files to find the file on your PC.

Step 7 In the Flash File System Path field, enter the path to the flash file system or click Browse Flash to find the directory or file in the flash file system.

Step 8 Click Upload Image. The uploading process might take a few minutes.

Step 9 You are prompted to set this image as the ASDM image. Click Yes.

Step 10 You are reminded to exit ASDM and save the configuration. Click OK. You exit the Upgrade tool. Note: You will save the configuration and reload ASDM after you upgrade the ASA software.

Step 11 Repeat Step 3 through Step 10, choosing ASA from the Image to Upload drop-down list.

Step 12 Click the Save icon on the toolbar to save your configuration changes.

Step 13 Choose Tools > System Reload.

The System Reload dialog box appears.

Step 14 Reload each slave unit one at a time by choosing a slave unit name from the Device drop-down list, and then clicking Schedule Reload to reload the unit now.

To avoid connection loss and allow traffic to stabilize, wait for each unit to come back up (approximately 5 minutes) before reloading the next unit. To view when a unit rejoins the cluster, see the Monitoring > ASA Cluster > Cluster Summary pane.

Step 15 After all slave units have reloaded, disable clustering on the master unit by choosing Configuration > Device Management > High Availability and Scalability > ASA Cluster, uncheck the Participate in ASA cluster check box, and click Apply.

Wait for 5 minutes for a new master to be selected and traffic to stabilize. When the former master unit rejoins the cluster, it will be a slave.

Do not save the configuration; when the master unit reloads, you want clustering to be enabled on it.

Step 16 Choose Tools > System Reload and reload the master unit from the System Reload dialog box by choosing --This Device-- from the Device drop-down list.

Step 17 Quit and restart ASDM; you will reconnect to the new master unit.


 

Copyright © 2014 Cisco Systems, Inc. All rights reserved.