End-To-End Procedure - Cisco Firepower 1010 Getting Started Manual

End-to-End Procedure

ASA 5500-X Configuration
PAK License
Initial ASDM access
Interface IDs
boot system commands
The ASA 5500-X allows up to four boot system commands to
specify the booting image to use.
End-to-End Procedure
See the following tasks to deploy and configure the ASA on your chassis.
Cisco Firepower 1010 Getting Started Guide
162
Firepower 1010 Configuration
Smart License
PAK licensing is not applied when you copy and paste your
configuration. There are no licenses installed by default. Smart
Licensing requires that you connect to the Smart Licensing server
to obtain your licenses. Smart Licensing also affects ASDM or
SSH access (see below).
Remove any VPN or other strong encryption feature
configuration—even if you only configured weak encryption—if
you cannot connect to ASDM or register with the Smart Licensing
server.
You can reenable these features after you obtain the Strong
Encryption (3DES) license.
The reason for this issue is that the ASA includes 3DES capability
by default for management access only. If you enable a strong
encryption feature, then ASDM and HTTPS traffic (like that to
and from the Smart Licensing server) are blocked. The exception
to this rule is if you are connected to a management-only interface,
such as Management 1/1. SSH is not affected.
Make sure you change the interface IDs to match the new
hardware IDs. For example, the ASA 5525-X includes
Management 0/0, and GigabitEthernet 0/0 through 0/5. The
Firepower 1120 includes Management 1/1 and Ethernet 1/1
through 1/8.
The Firepower 1010 only allows a single boot system command,
so you should remove all but one command before you paste. You
actually do not need to have any boot system commands present
in your configuration, as it is not read at startup to determine the
booting image. The last-loaded boot image will always run upon
reload.
The boot system command performs an action when you enter
it: the system validates and unpacks the image and copies it to
the boot location (an internal location on disk0 managed by
FXOS). The new image will load when you reload the ASA.
ASA Deployment with ASDM