Cisco Firepower 1010 Getting Started Manual page 169

ASA Deployment with ASDM
Is This Chapter for You?
To see all available operating systems and managers, see
You?, on page 1. This chapter applies to ASA using ASDM.
This chapter does not cover the following deployments, for which you should refer to the
guide:
• Failover
• CLI configuration
This chapter also walks you through configuring a basic security policy; if you have more advanced
requirements, refer to the configuration guide.
About the Firewall
The hardware can run either threat defense software or ASA software. Switching between threat defense and
ASA requires you to reimage the device. You should also reimage if you need a different software version
than is currently installed. See
The firewall runs an underlying operating system called the Secure Firewall eXtensible Operating System
(FXOS). The firewall does not support the FXOS Secure Firewall chassis manager; only a limited CLI is
supported for troubleshooting purposes. See the
1000/2100 Series Running Firepower Threat Defense
Privacy Collection Statement-The firewall does not require or actively collect personally-identifiable
information. However, you can use personally-identifiable information in the configuration, for example for
usernames. In this case, an administrator might be able to see this information when working with the
configuration or when using SNMP.
• About the ASA, on page 168
• End-to-End Procedure, on page 170
• Review the Network Deployment and Default Configuration, on page 172
• Cable the Device, on page 175
• Power On the Firewall, on page 176
• (Optional) Change the IP Address, on page 177
• Log Into the ASDM, on page 178
• Configure Licensing, on page 179
• Configure the ASA, on page 183
• Access the ASA and FXOS CLI, on page 185
C H A P T E R
Which Operating System and Manager is Right for
Reimage the Cisco ASA or Firepower Threat Defense
Cisco FXOS Troubleshooting Guide for the Firepower
for more information.
Cisco Firepower 1010 Getting Started Guide
6
ASA configuration
Device.
167