Cisco ASA and Firepower Threat Defense Reimage Guide

Console Port Access Required

To perform the reimage, you must connect your computer to the console port.

For the Firepower 2100, ASA 5512-X, 5515-X, 5525-X, 5545-X, and 5555-X, you might need to use a third party serial-to-USB cable to make the connection. Other models include a Mini USB Type B console port, so you can use any mini USB cable. For Windows, you may need to install a USB-serial driver from software.cisco.com. See the hardware guide for more information about console port options and driver requirements: http://www.cisco.com/go/asa5500x-install

Use a terminal emulator set for 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control.

Supported Models

The following models support either ASA software or Firepower Threat Defense Software. For ASA and Firepower Threat Defense version support, see the ASA compatibility guide or Firepower compatibility guide.

  • ASA 5506-X

  • ASA 5506W-X

  • ASA 5506H-X

  • ASA 5508-X

  • ASA 5512-X

  • ASA 5515-X

  • ASA 5516-X

  • ASA 5525-X

  • ASA 5545-X

  • ASA 5555-X

  • ISA 3000

  • Firepower 2100


Note

The Firepower 4100 and 9300 also support either the ASA or Firepower Threat Defense, but they are installed as logical devices; see the FXOS configuration guides for more information.



Note

For the Firepower Threat Defense on the ASA 5512-X through 5555-X, you must install a Cisco solid state drive (SSD). For more information, see the ASA 5500-X hardware guide. For the ASA, the SSD is also required to use the ASA FirePOWER module. (The SSD is standard on the ASA 5506-X, 5508-X, and 5516-X.)


Reimage the ASA 5500-X or ISA 3000

Download Software

Obtain Firepower Threat Defense software, or ASA, ASDM, and ASA FirePOWER module software. The procedures in this document require you to put software on a TFTP server for the initial download. Other images can be downloaded from other server types, such as HTTP or FTP. For the exact software package and server type, see the procedures.


Note

A Cisco.com login and Cisco service contract are required.


Table 1. Firepower Threat Defense Software

Firepower Threat Defense Model

Download Location

Packages

ASA 5506-X, ASA 5508-X, and ASA 5516-X

See: http://www.cisco.com/go/asa-firepower-sw.

Note 

You will also see patch files ending in .sh; the patch upgrade process is not covered in this document.

Boot image

Choose your model > Firepower Threat Defense Software > version.

The boot image has a filename like ftd-boot-9.6.2.0.lfbff.

System software install package

Choose your model > Firepower Threat Defense Software > version.

The system software install package has a filename like ftd-6.1.0-330.pkg.

ASA 5512-X through ASA 5555-X

See: http://www.cisco.com/go/asa-firepower-sw.

Note 

You will also see patch files ending in .sh; the patch upgrade process is not covered in this document.

Boot image

Choose your model > Firepower Threat Defense Software > version.

The boot image has a filename like ftd-boot-9.6.2.0.cdisk.

System software install package

Choose your model > Firepower Threat Defense Software > version.

The system software install package has a filename like ftd-6.1.0-330.pkg.

ISA 3000

See: http://www.cisco.com/go/isa3000-software

Note 

You will also see patch files ending in .sh; the patch upgrade process is not covered in this document.

Choose your model > Firepower Threat Defense Software > version.

The boot image has a filename like ftd-boot-9.9.2.0.lfbff.

Choose your model > Firepower Threat Defense Software > version.

The system software install package has a filename like ftd-6.2.3-330.pkg.

Table 2. ASA Software

ASA Model

Download Location

Packages

ASA 5506-X, ASA 5508-X, and ASA 5516-X

http://www.cisco.com/go/asa-firepower-sw

ASA Software

Choose your model > Adaptive Security Appliance (ASA) Software > version.

The ASA software file has a filename like asa962-lfbff-k8.SPA.

ASDM Software

Choose your model > Adaptive Security Appliance (ASA) Device Manager > version.

The ASDM software file has a filename like asdm-762.bin.

REST API Software

Choose your model > Adaptive Security Appliance REST API Plugin > version.

The API software file has a filename like asa-restapi-132-lfbff-k8.SPA. To install the REST API, see the API quick start guide

ROMMON Software

Choose your model > ASA Rommon Software > version.

The ROMMON software file has a filename like asa5500-firmware-1108.SPA.

ASA 5512-X through ASA 5555-X

http://www.cisco.com/go/asa-software

ASA Software

Choose your model > Software on Chassis > Adaptive Security Appliance (ASA) Software > version.

The ASA software file has a filename like asa962-smp-k8.bin.

ASDM Software

Choose your model > Software on Chassis > Adaptive Security Appliance (ASA) Device Manager > version.

The ASDM software file has a filename like asdm-762.bin.

REST API Software

Choose your model > Software on Chassis > Adaptive Security Appliance REST API Plugin > version.

The API software file has a filename like asa-restapi-132-lfbff-k8.SPA. To install the REST API, see the API quick start guide

ASA Device Package for Cisco Application Policy Infrastructure Controller (APIC)

Choose your model > Software on Chassis > ASA for Application Centric Infrastructure (ACI) Device Packages > version.

For APIC 1.2(7) and later, choose either the Policy Orchestration with Fabric Insertion, or the Fabric Insertion-only package. The device package software file has a filename like asa-device-pkg-1.2.7.10.zip. To install the ASA device package, see the “Importing a Device Package” chapter of the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide.

ISA 3000

http://www.cisco.com/go/isa3000-software

ASA Software

Choose your model > Adaptive Security Appliance (ASA) Software > version.

The ASA software file has a filename like asa962-lfbff-k8.SPA.

ASDM Software

Choose your model > Adaptive Security Appliance (ASA) Device Manager > version.

The ASDM software file has a filename like asdm-762.bin.

REST API Software

Choose your model > Adaptive Security Appliance REST API Plugin > version.

The API software file has a filename like asa-restapi-132-lfbff-k8.SPA. To install the REST API, see the API quick start guide.

Upgrade the ROMMON Image (ASA 5506-X, 5508-X, and 5516-X)

Follow these steps to upgrade the ROMMON image for the ASA 5506-X series, ASA 5508-X, and ASA 5516-X. The ROMMON version on your system must be 1.1.8 or greater.


Note

You cannot upgrade the ROMMON image after you reimage to Firepower Threat Defense.


Before you begin

You can only upgrade to a new version; you cannot downgrade. To see your current version, enter the show module command and look at the Fw Version in the output for Mod 1 in the MAC Address Range table:


ciscoasa# show module
[...]
Mod  MAC Address Range                 Hw Version   Fw Version   Sw Version     
---- --------------------------------- ------------ ------------ ---------------
   1 7426.aceb.ccea to 7426.aceb.ccf2  0.3          1.1.5        9.4(1)
 sfr 7426.aceb.cce9 to 7426.aceb.cce9  N/A          N/A          

Procedure


Step 1

Obtain the new ROMMON image from Cisco.com, and put it on a server to copy to the ASA. This procedure shows a TFTP copy.

Step 2

Copy the ROMMON image to the ASA flash memory:

copy tftp:// server_ip/asa5500-firmware- xxxx.SPA disk0:asa5500-firmware- xxxx.SPA

Step 3

Upgrade the ROMMON image:

upgrade rommon disk0:asa5500-firmware- xxxx.SPA

Example:


ciscoasa# upgrade rommon disk0:asa5500-firmware-1108.SPA
Verifying file integrity of disk0:/asa5500-firmware-1108.SPA

Computed Hash   SHA2: d824bdeecee1308fc64427367fa559e9
                      eefe8f182491652ee4c05e6e751f7a4f
                      5cdea28540cf60acde3ab9b65ff55a9f
                      4e0cfb84b9e2317a856580576612f4af
                      
Embedded Hash   SHA2: d824bdeecee1308fc64427367fa559e9
                      eefe8f182491652ee4c05e6e751f7a4f
                      5cdea28540cf60acde3ab9b65ff55a9f
                      4e0cfb84b9e2317a856580576612f4af
                      

Digital signature successfully validated
File Name                     : disk0:/asa5500-firmware-1108.SPA
Image type                    : Release
    Signer Information
        Common Name           : abraxas
        Organization Unit     : NCS_Kenton_ASA
        Organization Name     : CiscoSystems
    Certificate Serial Number : 553156F4
    Hash Algorithm            : SHA2 512
    Signature Algorithm       : 2048-bit RSA
    Key Version               : A
Verification successful.
Proceed with reload? [confirm]

Step 4

Confirm to reload the ASA when you are prompted.

The ASA upgrades the ROMMON image, and then reloads the ASA OS.


Reimage from ASA to Firepower Threat Defense

To reimage the ASA to Firepower Threat Defense software, you must access the ROMMON prompt. In ROMMON, you must use TFTP on the Management interface to download the Firepower Threat Defense boot image; only TFTP is supported. The boot image can then download the Firepower Threat Defense system software install package using HTTP or FTP. The TFTP download can take a long time; ensure that you have a stable connection between the ASA and the TFTP server to avoid packet loss.

Before you begin

To ease the process of reimaging back to an ASA, do the following:

  1. Perform a complete system backup using the backup command.

    See the configuration guide for more information, and other backup techniques.

  2. Copy and save the current activation key(s) so you can reinstall your licenses using the show activation-key command.

Procedure


Step 1

Download the Firepower Threat Defense boot image (see Download Software) to a TFTP server accessible by the ASA on the Management interface.

For the ASA 5506-X, 5508-X, 5516-X, ISA 3000: You must use the Management 1/1 port to download the image. For the other models, you can use any interface.

Step 2

Download the Firepower Threat Defense system software install package (see Download Software) to an HTTP or FTP server accessible by the ASA on the Management interface.

Step 3

From the console port, reload the ASA:

reload

Example:


ciscoasa# reload
Step 4

Press Esc during the bootup when prompted to reach the ROMMON prompt.

Pay close attention to the monitor.

Example:


[...]
Booting from ROMMON

Cisco Systems ROMMON Version (2.1(9)8) #1: Wed Oct 26 17:14:40 PDT 2011

Platform ASA 5555-X with SW, 8 GE Data, 1 GE Mgmt

Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.
Boot in   7 seconds. 

Press Esc at this point.

If you see the following message, then you waited too long, and must reload the ASA again after it finishes booting:


Launching BootLoader...
Boot configuration file contains 2 entries.
[...]

Step 5

Set the network settings, and load the boot image using the following ROMMON commands:

  1. interface —(ASA 5512-X, 5515-X, 5525-X, 5545-X, and 5555-X only) Management interface ID. Other models always use the Management 1/1 interface.

  2. address —Management interface IP address

  3. server —TFTP server IP address

  4. gateway —If the server is on the same network, set this IP address to be the same as the TFTP server IP address

  5. file —TFTP file path and name

  6. set —(Optional) View the network settings. You can also use the ping command to verify connectivity to the server

  7. sync —(Optional) Save the network settings

  8. tftpdnld —Load the boot image

Example:

Example for the ASA 5555-X:


rommon #0> interface gigabitethernet0/0
rommon #1> address 10.86.118.4
rommon #2> server 10.86.118.21
rommon #3> gateway 10.86.118.21
rommon #4> file ftd-boot-latest.cdisk
rommon #5> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.3
  SERVER=10.86.118.21
  GATEWAY=10.86.118.21
  PORT=GigabitEthernet0/0
  VLAN=untagged
  IMAGE=ftd-boot-latest.cdisk
  CONFIG=
  LINKTIMEOUT=20
  PKTTIMEOUT=4
  RETRY=20

rommon #6> sync

Updating NVRAM Parameters... 

rommon #7> tftpdnld

Example for the ASA 5506-X:


rommon #0> address 10.86.118.4
rommon #1> server 10.86.118.21
rommon #2> gateway 10.86.118.21
rommon #3> file ftd-boot-latest.lfbff
rommon #4> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.3
  SERVER=10.86.118.21
  GATEWAY=10.86.118.21
  VLAN=untagged
  IMAGE=ftd-boot-latest.lfbff
  CONFIG=
  LINKTIMEOUT=20
  PKTTIMEOUT=4
  RETRY=20

rommon #5> sync

Updating NVRAM Parameters... 

rommon #6> tftpdnld

The Firepower Threat Defense boot image downloads and boots up to the boot CLI.

Step 6

Type setup , and configure network settings for the Management interface to establish temporary connectivity to the HTTP or FTP server so that you can download and install the system software package. For example:

  • Hostname: ftd1

  • IPv4 address: 10.86.118.4

  • Netmask: 255.255.252.0

  • Gateway: 10.86.116.1

  • DNS servers: 10.86.116.5

  • Ntp server: ntp.example.com

Step 7

Download the Firepower Threat Defense system software install package. This step shows an HTTP installation.

system install [noconfirm ] url

Example:


> system install noconfirm http://10.86.118.21/ftd-6.0.1-949.pkg

Include the noconfirm option if you do not want to respond to confirmation messages.

Step 8

When installation is complete, choose Yes when the device reboot option is displayed.

Reboot takes upwards of 30 minutes, and could take much longer. Upon reboot, you will be in the Firepower Threat Defense CLI.

Step 9

You can use either Firepower Device Manager or Firepower Management Center to manage your device. See the Quick Start Guide for your model and your manager to continue setup: http://www.cisco.com/go/ftd-asa-quick


Reimage from Firepower Threat Defense to ASA

To reimage the Firepower Threat Defense to ASA software, you must access the ROMMON prompt. In ROMMON, you must erase the disks, and then use TFTP on the Management interface to download the ASA image; only TFTP is supported. After you reload the ASA, you can configure basic settings and then load the FirePOWER module software.

Before you begin

  • Ensure that you have a stable connection between the ASA and the TFTP server to avoid packet loss.

Procedure


Step 1

If you are managing the Firepower Threat Defense device from the Firepower Management Center, delete the device from the Management Center.

Step 2

If you are managing the Firepower Threat Defense device using Firepower Device Manager, be sure to unregister the device from the Smart Software Licensing server, either from the Firepower Device Manager or from the Smart Software Licensing server.

Step 3

Download the ASA image (see Download Software) to a TFTP server accessible by the Firepower Threat Defense device on the Management interface.

For the ASA 5506-X, 5508-X, 5516-X, ISA 3000: You must use the Management 1/1 port to download the image. For the other models, you can use any interface.

Step 4

At the console port, reboot the Firepower Threat Defense device.

Example:


> reboot
This command will reboot the system.  Continue?
Please enter 'YES' or 'NO': yes

Enter yes to reboot.

Step 5

Press Esc during the bootup when prompted to reach the ROMMON prompt.

Pay close attention to the monitor.

Example:


[...]
Booting from ROMMON

Cisco Systems ROMMON Version (2.1(9)8) #1: Wed Oct 26 17:14:40 PDT 2011

Platform ASA 5555-X with SW, 8 GE Data, 1 GE Mgmt

Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.
Boot in   7 seconds. 

Press Esc at this point.

If you see the following message, then you waited too long, and must reboot the Firepower Threat Defense device again after it finishes booting:


Launching BootLoader...
Boot configuration file contains 2 entries.
[...]

Step 6

Erase all disk(s) on the Firepower Threat Defense device. The internal flash is called disk0. If you have an external USB drive, it is disk1.

Example:


Example:
rommon #0> erase disk0:

About to erase the selected device, this will erase
all files including configuration, and images.
Continue with erase? y/n [n]: y

Erasing Disk0:
.......................
[...]

This step erases Firepower Threat Defense files so that the ASA does not try to load an incorrect configuration file, which causes numerous errors.

Step 7

Set the network settings, and load the ASA image using the following ROMMON commands.

interface interface_id

address management_ip_address

server tftp_ip_address

gateway gateway_ip_address

file path/ filename

set

sync

tftpdnld

The ASA image downloads and boots up to the CLI.

See the following information:

  • interface —(ASA 5512-X, 5515-X, 5525-X, 5545-X, and 5555-X only) Specifies the interface ID. Other models always use the Management 1/1 interface.

  • gateway —Sets the gateway address to be the same as the server IP address if they’re on the same network.

  • set —Shows the network settings. You can also use the ping command to verify connectivity to the server.

  • sync —Saves the network settings.

  • tftpdnld —Loads the boot image..

Example:

Example for the ASA 5555-X:


rommon #2> interface gigabitethernet0/0
rommon #3> address 10.86.118.4
rommon #4> server 10.86.118.21
rommon #5> gateway 10.86.118.21
rommon #6> file asalatest-smp-k8.bin
rommon #7> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.3
  SERVER=10.86.118.21
  GATEWAY=10.86.118.21
  PORT=GigabitEthernet0/0
  VLAN=untagged
  IMAGE=asalatest-smp-k8.bin
  CONFIG=
  LINKTIMEOUT=20
  PKTTIMEOUT=4
  RETRY=20

rommon #8> sync

Updating NVRAM Parameters... 

rommon #9> tftpdnld

Example for the ASA 5506-X:


rommon #2> address 10.86.118.4
rommon #3> server 10.86.118.21
rommon #4> gateway 10.86.118.21
rommon #5> file asalatest-lfbff-k8.SPA
rommon #6> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.3
  SERVER=10.86.118.21
  GATEWAY=10.86.118.21
  VLAN=untagged
  IMAGE=asalatest-lfbff-k8.SPA
  CONFIG=
  LINKTIMEOUT=20
  PKTTIMEOUT=4
  RETRY=20

rommon #7> sync

Updating NVRAM Parameters... 

rommon #8> tftpdnld

Step 8

Configure network settings and prepare the disks.

When the ASA first boots up, it does not have any configuration on it. you can either follow the interactive prompts to configure the Management interface for ASDM access, or you can paste a saved configuration or, if you do not have a saved configuration, the recommended configuration (below).

If you do not have a saved configuration, we suggest pasting the recommended configuration if you are planning to use the ASA FirePOWER module. The ASA FirePOWER module is managed on the Management interface and needs to reach the internet for updates. The simple, recommended network deployment includes an inside switch that lets you connect Management (for FirePOWER management only), an inside interface (for ASA management and inside traffic), and your management PC to the same inside network. See the quick start guide for more information about the network deployment:

  1. At the ASA console prompt, you are prompted to provide some configuration for the Management interface.

    
    Pre-configure Firewall now through interactive prompts [yes]?
    
    

    If you want to paste a configuration or create the recommended configuration for a simple network deployment, then enter no and continue with the procedure.

    If you want to configure the Management interface so you can connect to ASDM, enter yes, and follow the prompts.

  2. At the console prompt, access privileged EXEC mode.

    enable

    The following prompt appears:

    
    Password:
    
    
  3. Press Enter. By default, the password is blank.

  4. Access global configuration mode.

    configure terminal

  5. If you did not use the interactive prompts, copy and paste your configuration at the prompt.

    If you do not have a saved configuration, and you want to use the simple configuration described in the quick start guide, copy the following configuration at the prompt, changing the IP addresses and interface IDs as appropriate. If you did use the prompts, but want to use this configuration instead, clear the configuration first with the clear configure all command.

    
    interface gigabitethernetn/n
       nameif outside
       ip address dhcp setroute
       no shutdown
    interface gigabitethernetn/n
       nameif inside
       ip address ip_address netmask
       security-level 100
       no shutdown
    interface managementn/n
       no shutdown
    object network obj_any
       subnet 0 0
       nat (any,outside) dynamic interface
    http server enable
    http inside_network netmask inside
    dhcpd address inside_ip_address_start-inside_ip_address_end inside
    dhcpd auto_config outside
    dhcpd enable inside
    logging asdm informational
    
    

    For the ASA 5506W-X, add the following for the wifi interface:

    
    same-security-traffic permit inter-interface
    interface GigabitEthernet 1/9
    security-level 100
    nameif wifi
    ip address ip_address netmask
    no shutdown
    http wifi_network netmask wifi
    dhcpd address wifi_ip_address_start-wifi_ip_address_end wifi
    dhcpd enable wifi
    
    
  6. Reformat the disks:

    format disk0:

    format disk1:

    The internal flash is called disk0. If you have an external USB drive, it is disk1. If you do not reformat the disks, then when you try to copy the ASA image, you see the following error:

    
    %Error copying ftp://10.86.89.125/asa971-smp-k8.bin (Not enough space on device)
    
    
  7. Save the new configuration:

    write memory

Step 9

Install the ASA and ASDM images.

Booting the ASA from ROMMON mode does not preserve the system image across reloads; you must still download the image to flash memory. You also need to download ASDM to flash memory.

  1. Download the ASA and ASDM images (see Download Software) to a server accessible by the ASA. The ASA supports many server types. See the copy command for more information: http://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/c4.html#pgfId-2171368.

  2. Copy the ASA image to the ASA flash memory. This step shows an FTP copy.

    copy ftp:// user: password@ server_ip/ asa_file disk0: asa_file

    Example:

    
    ciscoasa# copy ftp://admin:test@10.86.118.21/asa961-smp-k8.bin disk0:asa961-smp-k8.bin
    
    
  3. Copy the ASDM image to the ASA flash memory. This step shows an FTP copy.

    copy ftp:// user: password@ server_ip/ asdm_file disk0: asdm_file

    Example:

    
    ciscoasa# copy ftp://admin:test@10.86.118.21/asdm-761.bin disk0:asdm-761.bin
    
    
  4. Reload the ASA:

    reload

    The ASA reloads using the image in disk0.

Step 10

(Optional) Install the ASA FirePOWER module software.

You need to install the ASA FirePOWER boot image, partition the SSD, and install the system software according to this procedure.

  1. Copy the boot image to the ASA. Do not transfer the system software; it is downloaded later to the SSD. This step shows an FTP copy.

    copy ftp:// user: password@ server_ip/ firepower_boot_file disk0: firepower_boot_file

    Example:

    
    ciscoasa# copy ftp://admin:test@10.86.118.21/asasfr-5500x-boot-6.0.1.img disk0:/asasfr-5500x-boot-6.0.1.img
    
    
  2. Download the ASA FirePOWER services system software install package from Cisco.com to an HTTP, HTTPS, or FTP server accessible from the Management interface. Do not download it to disk0 on the ASA.

  3. Set the ASA FirePOWER module boot image location in ASA disk0:

    sw-module module sfr recover configure image disk0: file_path

    Example:

    
    ciscoasa# sw-module module sfr recover configure image disk0:asasfr-5500x-boot-6.0.1.img
    
    
  4. Load the ASA FirePOWER boot image:

    sw-module module sfr recover boot

    Example:

    
    ciscoasa# sw-module module sfr recover boot
    
    Module sfr will be recovered. This may erase all configuration and all data
    on that device and attempt to download/install a new image for it. This may take
    several minutes.
    
    Recover module sfr? [confirm] y
    Recover issued for module sfr.
    
    
  5. Wait a few minutes for the ASA FirePOWER module to boot up, and then open a console session to the now-running ASA FirePOWER boot image. You might need to press Enter after opening the session to get to the login prompt. The default username is admin and the default password is Admin123.

    Example:

    
    ciscoasa# session sfr console
    Opening console session with module sfr.
    Connected to module sfr. Escape character sequence is 'CTRL-^X'.
    
    asasfr login: admin
    Password: Admin123
    
    

    If the module boot has not completed, the session command will fail with a message about not being able to connect over ttyS1. Wait and try again.

  1. Configure the system so that you can install the system software install package.

    setup

    You are prompted for the following. Note that the management address and gateway, and DNS information, are the key settings to configure.

    • Host name—Up to 65 alphanumeric characters, no spaces. Hyphens are allowed.

    • Network address—You can set static IPv4 or IPv6 addresses, or use DHCP (for IPv4) or IPv6 stateless autoconfiguration.

    • DNS information—You must identify at least one DNS server, and you can also set the domain name and search domain.

    • NTP information—You can enable NTP and configure the NTP servers, for setting system time.

    Example:

    
    asasfr-boot> setup
    
                     Welcome to Cisco FirePOWER Services Setup
                              [hit Ctrl-C to abort]
                            Default values are inside []
    
    
  1. Install the system software install package:

    system install [noconfirm ] url

    Include the noconfirm option if you do not want to respond to confirmation messages. Use an HTTP, HTTPS, or FTP URL; if a username and password are required, you will be prompted to supply them. This file is large and can take a long time to download, depending on your network.

    When installation is complete, the system reboots. The time required for application component installation and for the ASA FirePOWER services to start differs substantially: high-end platforms can take 10 or more minutes, but low-end platforms can take 60-80 minutes or longer. (The show module sfr output should show all processes as Up.)

    Example:

    
    asasfr-boot> system install http://admin:pa$$wd@upgrades.example.com/packages/asasfr-sys-6.0.1-58.pkg
    Verifying
    Downloading
    Extracting
    Package Detail
            Description:                    Cisco ASA-FirePOWER 6.0.1-58 System Install
            Requires reboot:                Yes
    
    Do you want to continue with upgrade? [y]: y
    Warning: Please do not interrupt the process or turn off the system.
    Doing so might leave system in unusable state.
    
    Upgrading
    Starting upgrade process ...
    Populating new system image
    
    Reboot is required to complete the upgrade. Press 'Enter' to reboot the system. [type Enter]
    Broadcast message from root (ttyS1) (Mon Feb 17 19:28:38 2016):
    
    The system is going down for reboot NOW!
    Console session with module sfr terminated.
    
    
  1. If you need to install a patch release, you can do so later from your manager: ASDM or the Firepower Management Center.

Step 11

Obtain a Strong Encryption license and other licenses for an existing ASA for which you did not save the activation key: see http://www.cisco.com/go/license. In the Manage > Licenses section you can re-download your licenses.

To use ASDM (and many other features), you need to install the Strong Encryption (3DES/AES) license. If you saved your license activation key from this ASA before you previously reimaged to the Firepower Threat Defense device, you can re-install the activation key. If you did not save the activation key but own licenses for this ASA, you can re-download the license. For a new ASA, you will need to request new ASA licenses.

Step 12

Obtain licenses for a new ASA.

  1. Obtain the serial number for your ASA by entering the following command:

    show version | grep Serial

    This serial number is different from the chassis serial number printed on the outside of your hardware. The chassis serial number is used for technical support, but not for licensing.

  2. See http://www.cisco.com/go/license, and click Get Other Licenses.

    Figure 1. Get Other Licenses
  3. Choose IPS, Crypto, Other.

    Figure 2. IPS, Crypto, Other
  4. In the Search by Keyword field, enter asa, and select Cisco ASA 3DES/AES License.

    Figure 3. Cisco ASA 3DES/AES License
  5. Select your Smart Account, Virtual Account, enter the ASA Serial Number, and click Next.

    Figure 4. Smart Account, Virtual Account, and Serial Number
  6. Your Send To email address and End User name are auto-filled; enter additional email addresses if needed. Check the I Agree check box, and click Submit.

    Figure 5. Submit
  7. You will then receive an email with the activation key, but you can also download the key right away from the Manage > Licenses area.

  8. If you want to upgrade from the Base license to the Security Plus license, or purchase an AnyConnect license, see http://www.cisco.com/go/ccw. After you purchase a license, you will receive an email with a Product Authorization Key (PAK) that you can enter on http://www.cisco.com/go/license. For the AnyConnect licenses, you receive a multi-use PAK that you can apply to multiple ASAs that use the same pool of user sessions. The resulting activation key includes all features you have registered so far for permanent licenses, including the 3DES/AES license. For time-based licenses, each license has a separate activation key.

Step 13

Apply the activation key.

activation-key key

Example:


ciscoasa(config)# activation-key 7c1aff4f e4d7db95 d5e191a4 d5b43c08 0d29c996
Validating activation key. This may take a few minutes...
Failed to retrieve permanent activation key.
Both Running and Flash permanent activation key was updated with the requested key.

Because this ASA did not yet have an activation key installed, you see the “Failed to retrieve permanent activation key.” message. You can ignore this message.

You can only install one permanent key, and multiple time-based keys. If you enter a new permanent key, it overwrites the already installed one. If you ordered additional licenses after you installed the 3DES/AES license, the combined activation key includes all licenses plus the 3DES/AES license, so you can overwrite the 3DES/AES-only key.

Step 14

The ASA FirePOWER module uses a separate licensing mechanism from the ASA. No licenses are pre-installed, but depending on your order, the box might include a PAK on a printout that lets you obtain a license activation key for the following licenses:

  • Control and Protection. Control is also known as “Application Visibility and Control (AVC)” or “Apps”. Protection is also known as “IPS”. In addition to the activation key for these licenses, you also need “right-to-use” subscriptions for automated updates for these features.

    The Control (AVC) updates are included with a Cisco support contract.

    The Protection (IPS) updates require you to purchase the IPS subscription from http://www.cisco.com/go/ccw. This subscription includes entitlement to Rule, Engine, Vulnerability, and Geolocation updates. Note: This right-to-use subscription does not generate or require a PAK/license activation key for the ASA FirePOWER module; it just provides the right to use the updates.

If you did not buy an ASA 5500-X that included the ASA FirePOWER services, then you can purchase an upgrade bundle to obtain the necessary licenses. See the Cisco ASA with FirePOWER Services Ordering Guide for more information.

Other licenses that you can purchase include the following:

  • Advanced Malware Protection (AMP)

  • URL Filtering

These licenses do generate a PAK/license activation key for the ASA FirePOWER module. See the Cisco ASA with FirePOWER Services Ordering Guide for ordering information. See also the Cisco Firepower System Feature Licenses.

To install the Control and Protection licenses and other optional licenses, see the ASA quick start guide for your model.


Reimage the Firepower 2100 Series

The Firepower 2100 series supports either Firepower Threat Defense or ASA software.

Download Software

Obtain Firepower Threat Defense software or ASA software. The procedures in this document require you to put software on a TFTP server for the initial download. Other images can be downloaded from other server types, such as HTTP or FTP. For the exact software package and server type, see the procedures.


Note

A Cisco.com login and Cisco service contract are required.


Table 3. Firepower Threat Defense Software

Firepower Threat Defense Model

Download Location

Packages

Firepower 2100 series

See: https://www.cisco.com/go/ftd-software

Firepower Threat Defense package

Choose your model > Firepower Threat Defense Software > version.

The package has a filename like cisco-ftd-fp2k.6.2.2.SPA.

Table 4. ASA Software

ASA Model

Download Location

Packages

Firepower 2100 series

See: https://www.cisco.com/go/asa-firepower-sw

ASA package

Choose your model > Adaptive Security Appliance (ASA) Software > version.

The package has a filename like cisco-asa-fp2k.9.8.2.SPA. This package includes ASA, ASDM, FXOS, and the Firepower Chassis Manager.

ASDM software (upgrade)

To upgrade to a later version of ASDM using your current ASDM or the ASA CLI, choose your model > Adaptive Security Appliance (ASA) Device Manager > version.

The ASDM software file has a filename like asdm-782.bin.

Reimage from ASA to Firepower Threat Defense

To reimage the ASA on the Firepower 2100 to Firepower Threat Defense software, you must access the ROMMON prompt. In ROMMON, you must erase the disks, and then use TFTP on the Management 1/1 interface to load FXOS from the Firepower Threat Defense package; only TFTP is supported. After initially booting FXOS, you then configure network settings, download the Firepower Threat Defense package (from a server of your choice), and then reboot again.

Procedure


Step 1

Unregister the ASA from the Smart Software Licensing server, either from the ASA CLI/ASDM or from the Smart Software Licensing server.

Step 2

Download the Firepower Threat Defense image (see Download Software) to a TFTP server accessible by the ASA on the Management 1/1 interface.

Step 3

At the console port, log in to FXOS as admin, and reformat the system.

connect local-mgmt

format everything


firepower-2110# connect local-mgmt 
firepower-2110(local-mgmt)# format everything
All configuration and bootable images will be lost.
Do you still want to format? (yes/no):yes

Enter yes, and the Firepower 2100 reboots.

Step 4

Press Esc during the bootup when prompted to reach the ROMMON prompt. Pay close attention to the monitor.

Example:


*******************************************************************************
Cisco System ROMMON, Version 1.0.03, RELEASE SOFTWARE
Copyright (c) 1994-2017  by Cisco Systems, Inc.
Compiled Thu 04/06/2017 12:16:16.21 by builder
*******************************************************************************

Current image running: Boot ROM0
Last reset cause: ResetRequest
DIMM_1/1 : Present
DIMM_2/1 : Present

Platform FPR-2130 with 32768 MBytes of main memory
BIOS has been successfully locked !!
MAC Address: 0c:75:bd:08:c9:80

Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.

Press Esc at this point. If you miss the interrupt prompt, the Firepower 2100 attempts to reboot 3 times; because there is no image on the device, only ROMMON is available.

Step 5

Set the network settings for Management 1/1, and load FXOS (part of the Firepower Threat Defense package) using the following ROMMON commands.

address management_ip_address

netmask subnet_mask

server tftp_ip_address

gateway gateway_ip_address

file path/ filename

set

sync

tftp -b

The FXOS image downloads and boots up to the CLI.

See the following information:

  • gateway —Set the gateway address to be the same as the server IP address if they’re on the same network.

  • set —Shows the network settings. You can also use the ping command to verify connectivity to the server.

  • sync —Saves the network settings.

  • tftp -b —Loads FXOS.

Example:


rommon 1> address 10.86.118.4
rommon 2> netmask 255.255.252.0
rommon 3> server 10.86.118.21
rommon 4> gateway 10.86.118.21
rommon 5> file cisco-ftd-fp2k.6.2.2.SPA
rommon 6> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.4
  NETMASK=255.255.252.0
  GATEWAY=10.86.118.21
  SERVER=10.86.118.21
  IMAGE=cisco-ftd-fp2k.6.2.2.SPA
  CONFIG=
  PS1="rommon ! > "

rommon 7> sync
rommon 8> tftp -b
Enable boot bundle: tftp_reqsize = 268435456

             ADDRESS: 10.86.118.4
             NETMASK: 255.255.252.0
             GATEWAY: 10.86.118.21
              SERVER: 10.86.118.21
               IMAGE: cisco-asa-fp2k.9.8.2.SPA
             MACADDR: d4:2c:44:0c:26:00
           VERBOSITY: Progress
               RETRY: 40
          PKTTIMEOUT: 7200
             BLKSIZE: 1460
            CHECKSUM: Yes
                PORT: GbE/1
             PHYMODE: Auto Detect

link up
Receiving cisco-ftd-fp2k.6.2.2.SPA from 10.86.118.21!!!!!!!!
[…]

Step 6

Log in to FXOS using the default username: admin and password: Admin123.

After the device boots up into FXOS, the Management IP address that you set in ROMMON is erased and set to the default: 192.168.45.45. You will need to set the correct IP address and other related settings for your network in FXOS before you can download the Firepower Threat Defense package from the server.

Step 7

Disable the DHCP server.

scope system

scope services

disable dhcp-server

Before you can change the management IP address, you must disable the DHCP server.

Example:


firepower-2110# scope system
firepower-2110 /system # scope services
firepower-2110 /system/services # disable dhcp-server

Step 8

Configure an IPv4 management IP address, and optionally the gateway.

scope fabric-interconnect a

set out-of-band static ip ip_address netmask network_mask gw gateway_ip_address

commit-buffer

To keep the currently-set gateway (by default 0.0.0.0, which represents the Firepower Threat Defense data interfaces), omit the gw keyword. If your download server is not on the local Management 1/1 network, then change the gateway IP address; the Firepower Threat Defense data interfaces do not exist yet, so you cannot reach any remote servers with the default setting.

Example:


firepower-2110*# scope fabric-interconnect a
firepower-2110 /fabric-interconnect* #
firepower-2100 /fabric-interconnect* # set out-of-band static ip 10.86.118.4 netmask 255.255.255.0 
Warning: When committed, this change may disconnect the current CLI session
firepower-2100 /fabric-interconnect* # commit-buffer
firepower-2100 /fabric-interconnect #

Step 9

Download and boot the Firepower Threat Defense package.

  1. Download the package.

    scope firmware

    download image url

    show download-task

    You can download the package from the same TFTP server you used earlier, or another server reachable on Management 1/1.

    Example:

    
    firepower-2110# scope firmware
    firepower-2110 /firmware # download image tftp://10.86.118.21/cisco-ftd-fp2k.6.2.2.SPA
    Please use the command 'show download-task' or 'show download-task detail' to check download progress.
    firepower-2110 /firmware # show download-task
    Download task:
        File Name Protocol Server          Port       Userid          State
        --------- -------- --------------- ---------- --------------- -----
        cisco-ftd-fp2k.6.2.2.SPA
                  Tftp     10.88.29.21             0                 Downloaded
    
    
  2. When the package finishes downloading (Downloaded state), boot the package.

    show package

    scope auto-install

    install security-pack version version

    In the show package output, copy the Package-Vers value for the security-pack version number. The chassis installs the Firepower Threat Defense image and reboots.

    Example:

    
    firepower 2110 /firmware # show package
    Name                                          Package-Vers
    --------------------------------------------- ------------
    cisco-ftd-fp2k.6.2.2.SPA                      6.2.2
    firepower 2110 /firmware # scope auto-install
    firepower 2110 /firmware/auto-install # install security-pack version 6.2.2
    The system is currently installed with security software package not set, which has:
       - The platform version: not set
    If you proceed with the upgrade 6.2.2, it will do the following:
       - upgrade to the new platform version 2.2.2.52
       - install with CSP ftd version 6.2.2
    During the upgrade, the system will be reboot
    
    Do you want to proceed ? (yes/no):yes
    
    This operation upgrades firmware and software on Security Platform Components
    Here is the checklist of things that are recommended before starting Auto-Install
    (1) Review current critical/major faults
    (2) Initiate a configuration backup
    
    Attention:
       If you proceed the system will be re-imaged. All existing configuration will be lost,
       and the default configuration applied.
    Do you want to proceed? (yes/no):yes
    
    Triggered the install of software package version 6.2.2
    Install started. This will take several minutes.
    For monitoring the upgrade progress, please enter 'show' or 'show detail' command.
    
    
Step 10

Wait for the chassis to finish rebooting (5-10 minutes), and log in to FXOS using the default username: admin and password: Admin123.

Although FXOS is up, you still need to wait for the Firepower Threat Defense to come up (30 minutes). Wait until you see the following messages:


[…]
User enable_1 logged in to firepower
Logins over the last 1 days: 1.
Failed logins since the last login: 0.
Type help or '?' for a list of available commands.
firepower> Aug 26 01:31:48 firepower port-manager: Alert: Ethernet1/2 link changed to DOWN
Aug 26 01:31:48 firepower port-manager: Alert: Ethernet1/1 link changed to DOWN

firepower#        

After the rest of the Firepower Threat Defense startup messages show, you can return to the FXOS prompt.

Step 11

Connect to the Firepower Threat Defense CLI.

connect ftd

Step 12

You are prompted to accept the EULA; press Enter, and then the Space bar at the More prompt until you see:


Please enter 'YES' or press <ENTER> to AGREE to the EULA:

Enter yes.

Step 13

You are prompted to change the password and perform the initial setup. See the Firepower Device Manager or Firepower Management Center quick start guide to configure your system.


Reimage from Firepower Threat Defense to ASA

To reimage the Firepower Threat Defense on the Firepower 2100 to ASA software, you must access the ROMMON prompt. In ROMMON, you must erase the disks, and then use TFTP on the Management 1/1 interface to load FXOS from the ASA package; only TFTP is supported. After initially booting FXOS, you then configure network settings, download the ASA package (from a server of your choice), and then reboot again.

Procedure


Step 1

If you are managing the Firepower Threat Defense device from the Firepower Management Center, delete the device from the Management Center.

Step 2

If you are managing the Firepower Threat Defense device using Firepower Device Manager, be sure to unregister the device from the Smart Software Licensing server, either from the Firepower Device Manager or from the Smart Software Licensing server.

Step 3

Download the ASA image (see Download Software) to a TFTP server accessible by the Firepower Threat Defense device on the Management 1/1 interface.

Step 4

At the console port, log in to FXOS as admin, and reformat the system.

connect local-mgmt

format everything


firepower-2110# connect local-mgmt 
firepower-2110(local-mgmt)# format everything
All configuration and bootable images will be lost.
Do you still want to format? (yes/no):yes

Enter yes, and the Firepower 2100 reboots.

Step 5

Press Esc during the bootup when prompted to reach the ROMMON prompt. Pay close attention to the monitor.

Example:


*******************************************************************************
Cisco System ROMMON, Version 1.0.03, RELEASE SOFTWARE
Copyright (c) 1994-2017  by Cisco Systems, Inc.
Compiled Thu 04/06/2017 12:16:16.21 by builder
*******************************************************************************

Current image running: Boot ROM0
Last reset cause: ResetRequest
DIMM_1/1 : Present
DIMM_2/1 : Present

Platform FPR-2130 with 32768 MBytes of main memory
BIOS has been successfully locked !!
MAC Address: 0c:75:bd:08:c9:80

Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.

Press Esc at this point. If you miss the interrupt prompt, the Firepower 2100 attempts to reboot 3 times; because there is no image on the device, only ROMMON is available.

Step 6

Set the network settings for Management 1/1, and load FXOS (part of the ASA package) using the following ROMMON commands.

address management_ip_address

netmask subnet_mask

server tftp_ip_address

gateway gateway_ip_address

file path/ filename

set

sync

tftp -b

The FXOS image downloads and boots up to the CLI.

See the following information:

  • gateway —Sets the gateway address to be the same as the server IP address if they’re on the same network.

  • set —Shows the network settings. You can also use the ping command to verify connectivity to the server.

  • sync —Saves the network settings.

  • tftp -b —Loads FXOS.

Example:


rommon 1> address 10.86.118.4
rommon 2> netmask 255.255.252.0
rommon 3> server 10.86.118.21
rommon 4> gateway 10.86.118.21
rommon 5> file cisco-asa-fp2k.9.8.2.SPA
rommon 6> set
ROMMON Variable Settings:
  ADDRESS=10.86.118.4
  NETMASK=255.255.252.0
  GATEWAY=10.86.118.21
  SERVER=10.86.118.21
  IMAGE=cisco-asa-fp2k.9.8.2.SPA
  CONFIG=
  PS1="rommon ! > "

rommon 7> sync
rommon 8> tftp -b
Enable boot bundle: tftp_reqsize = 268435456

             ADDRESS: 10.86.118.4
             NETMASK: 255.255.252.0
             GATEWAY: 10.86.118.21
              SERVER: 10.86.118.21
               IMAGE: cisco-asa-fp2k.9.8.2.SPA
             MACADDR: d4:2c:44:0c:26:00
           VERBOSITY: Progress
               RETRY: 40
          PKTTIMEOUT: 7200
             BLKSIZE: 1460
            CHECKSUM: Yes
                PORT: GbE/1
             PHYMODE: Auto Detect

link up
Receiving cisco-asa-fp2k.9.8.2.SPA from 10.86.118.21!!!!!!!!
[…]

Step 7

Log in to FXOS using the default username: admin and password: Admin123.

After the device boots up into FXOS, the Management IP address that you set in ROMMON is erased and set to the default: 192.168.45.45. You will need to set the correct IP address and other related settings for your network in FXOS before you can download the ASA package from the server.

Step 8

Disable the DHCP server.

scope system

scope services

disable dhcp-server

commit-buffer

Before you can change the management IP address, you must disable the DHCP server. You can reenable DHCP using new client IP addresses after you change the management IP address.

Example:


firepower-2110# scope system
firepower-2110 /system # scope services
firepower-2110 /system/services # disable dhcp-server
firepower-2110 /system/services* # commit-buffer

Step 9

Configure an IPv4 management IP address, and optionally the gateway.

scope fabric-interconnect a

set out-of-band static ip ip_address netmask network_mask gw gateway_ip_address

To keep the currently-set gateway (by default 0.0.0.0, which represents the ASA data interfaces), omit the gw keyword. If your download server is not on the local Management 1/1 network, then change the gateway IP address; the ASA data interfaces do not exist yet, so you cannot reach any remote servers with the default setting.

Example:


firepower-2110# scope fabric-interconnect a
firepower-2110 /fabric-interconnect #
firepower-2110 /fabric-interconnect # set out-of-band static ip 10.86.118.4 netmask 255.255.255.0 
Warning: When committed, this change may disconnect the current CLI session
firepower-2110 /fabric-interconnect* # 

Step 10

Delete and add new access lists for HTTPS, SSH, and SNMP to allow management connections from the new network.

  1. Set the scope for system/services.

    scope system

    scope services

    Example:

    
    firepower-2110# scope system
    firepower-2110 /system # scope services
    
    
  2. View the current access lists.

    show ip-block

    Example:

    
    firepower-2110 /system/services # show ip-block
    
    Permitted IP Block:
        IP Address      Prefix Length Protocol
        --------------- ------------- --------
        192.168.45.0               24 https
        192.168.45.0               24 ssh
    firepower-2140 /system/services #             
    
    
  3. Add new access lists.

    For IPv4:

    enter ip-block ip_address prefix [http | snmp | ssh ]

    For IPv6:

    enter ipv6-block ipv6_address prefix [https | snmp | ssh ]

    For IPv4, enter 0.0.0.0 and a prefix of 0 to allow all networks. For IPv6, enter :: and a prefix of 0 to allow all networks. You can also add access lists in the Firepower Chassis Manager at Platform Settings > Access List.

    Example:

    
    firepower-2110 /system/services # enter ip-block 192.168.4.0 24 https
    firepower-2110 /system/services/ip-block* # exit
    firepower-2110 /system/services* # enter ip-block 192.168.4.0 24 ssh
    firepower-2110 /system/services/ip-block* # exit
    firepower-2110 /system/services* # 
    
    
  1. Delete the old access lists.

    For IPv4:

    delete ip-block ip_address prefix [http | snmp | ssh ]

    For IPv6:

    delete ipv6-block ipv6_address prefix [https | snmp | ssh ]

    Example:

    
    firepower-2110 /system/services # delete ip-block 192.168.45.0 24 https
    firepower-2110 /system/services* # delete ip-block 192.168.45.0 24 ssh
    firepower-2110 /system/services* # 
    
    
Step 11

(Optional) Reenable the IPv4 DHCP server.

scope system

scope services

enable dhcp-server start_ip_address end_ip_address

Example:


firepower-2110# scope system
firepower-2110 /system # scope services
firepower-2110 /system/services # enable dhcp-server 10.86.118.10 10.86.118.20

Step 12

Save the configuration.

commit-buffer

Example:


firepower-2110 /system/services* # commit-buffer

Step 13

Download and boot the ASA package.

  1. Download the package.

    scope firmware

    download image url

    show download-task

    You can download the package from the same TFTP server you used earlier, or another server reachable on Management 1/1.

    Example:

    
    firepower-2110# scope firmware
    firepower-2110 /firmware # download image tftp://10.86.118.21/cisco-asa-fp2k.9.8.2.SPA
    Please use the command 'show download-task' or 'show download-task detail' to check download progress.
    firepower-2110 /firmware # show download-task
    Download task:
        File Name Protocol Server          Port       Userid          State
        --------- -------- --------------- ---------- --------------- -----
        cisco-asa-fp2k.9.8.2.SPA
                  Tftp     10.88.29.21             0                 Downloaded
    
    
  2. When the package finishes downloading (Downloaded state), boot the package.

    show package

    scope auto-install

    install security-pack version version

    In the show package output, copy the Package-Vers value for the security-pack version number. The chassis installs the ASA image and reboots.

    Example:

    
    firepower 2110 /firmware # show package
    Name                                          Package-Vers
    --------------------------------------------- ------------
    cisco-asa-fp2k.9.8.2.SPA                      9.8.2
    firepower 2110 /firmware # scope auto-install
    firepower 2110 /firmware/auto-install # install security-pack version 9.8.2
    The system is currently installed with security software package not set, which has:
       - The platform version: not set
    If you proceed with the upgrade 9.8.2, it will do the following:
       - upgrade to the new platform version 2.2.2.52
       - install with CSP asa version 9.8.2
    During the upgrade, the system will be reboot
    
    Do you want to proceed ? (yes/no):yes
    
    This operation upgrades firmware and software on Security Platform Components
    Here is the checklist of things that are recommended before starting Auto-Install
    (1) Review current critical/major faults
    (2) Initiate a configuration backup
    
    Attention:
       If you proceed the system will be re-imaged. All existing configuration will be lost,
       and the default configuration applied.
    Do you want to proceed? (yes/no):yes
    
    Triggered the install of software package version 9.8.2
    Install started. This will take several minutes.
    For monitoring the upgrade progress, please enter 'show' or 'show detail' command.
    
    
Step 14

Wait for the chassis to finish rebooting (5-10 minutes), and log in to FXOS using the default username: admin and password: Admin123.

Although FXOS is up, you still need to wait for the ASA to come up (5 minutes). Wait until you see the following messages:


firepower-2110# 
Cisco ASA: CMD=-install, CSP-ID=cisco-asa.9.8.2__asa_001_JAD20280BW90MEZR11, FLAG=''
Verifying signature for cisco-asa.9.8.2 ...
Verifying signature for cisco-asa.9.8.2 ... success

Cisco ASA: CMD=-start, CSP-ID=cisco-asa.9.8.2__asa_001_JAD20280BW90MEZR11, FLAG=''
Cisco ASA starting ...
Registering to process manager ...
Cisco ASA started successfully. 
[…]

After the rest of the ASA startup messages show, you can return to the FXOS prompt.

Step 15

If you changed the FXOS Management 1/1 address in this procedure, you should change the ASA address to be on the correct network. The default ASA Management 1/1 interface IP address is 192.168.45.1.

  1. From the console, connect to the ASA CLI and access global configuration mode.

    connect asa

    enable

    configure terminal

    The enable password is blank by default.

    Example:

    
    firepower-2110# connect asa
    Attaching to Diagnostic CLI ... Press 'Ctrl+a then d' to detach.
    Type help or '?' for a list of available commands.
    ciscoasa> enable
    Password: <blank>
    ciscoasa# configure terminal
    ciscoasa(config)# 
    
    
  2. Change the Management 1/1 IP address.

    interface management1/1

    ip address ip_address mask

    Example:

    
    ciscoasa(config)# interface management1/1
    ciscoasa(config-ifc)# ip address 10.86.118.4 255.255.255.0
    
    
  3. Change the network that can access ASDM.

    no http 192.168.45.0 255.255.255.0 management

    http ip_address mask management

    Example:

    
    ciscoasa(config)# no http 192.168.45.0 255.255.255.0 management
    ciscoasa(config)# http 10.86.118.0 255.255.255.0 management
    
    
  4. Save the configuration.

    write memory

  5. To return to the FXOS console, enter Ctrl+a, d.

Step 16

See the ASA for Firepower 2100 Series Getting Started Guide to configure your system.


What’s Next?