Recently I was given a Cisco ASA 5508-X Firepower Threat Defense appliance to deploy. While these are the same hardware platform as the tried-true Cisco ASA 5508 firewalls, these run Cisco’s new ‘unified’ SourceFire linux based operating system (asa-ftd), which is essentially an operating system combining the SourceFire FirePower functionality with Cisco’s conventional firewalling capabilities. It’s Cisco’s new direction for combining these two platforms in to one hardware solution.
Without getting in to uber nerd verbosity, after unboxing the new unit and attempting to patch the OS to a new upgrade (version 6.0.2 -> 6.2.2), I was presented with a failed upgrade due to a corrupt MySQL database. Seriously ? This is why I loved the regular Cisco ASA in the first place, minimal OS running from flash memory, upgrades typically only require putting the new firmware in place, telling the Cisco ASA to boot the new firmware and reboot. The new SourceFire OS – it’s a full blown linux OS using MySQL for its backend, sigh… Since it was a new deployment and I couldn’t repair the tables or database I figured I’d go ahead and reach out to the Cisco TAC for insight.
The Cisco TAC advised that since the unit was not a “production” appliance currently, the best recourse would be to manually wipe and reimage the appliance with the intended version of the OS, version 6.2.2. I don’t disagree with that assessment, it makes sense – but the fact that I’m re-imageing a firewall appliance fresh out of the box due to a corrupt MySQL database – doesn’t give me high confidence in the product to be honest.
Cisco provides good documentation of this process here, but I figured I’d capture some of my real world experience doing so.
BEFORE proceeding complete the steps Cisco recommends:
Before You Begin
To ease the process of reimaging back to an ASA, do the following:
Perform a complete system backup using the backup command.
See the configuration guide for more information, and other backup techniques:
Copy and save the current activation key(s) so you can reinstall your licenses using the show activation-key command.
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, and 5516-X, 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.
First off I rebooted the appliance and hit ESC to get the ronmon boot prompt.
<br /> Use BREAK or ESC to interrupt boot.<br /> Use SPACE to begin boot immediately.<br /> Boot interrupted.<br />
At this point I figured I’d manually erase the disk myself to be sure all was gone.
<br /> rommon 5 > erase disk0:<br /> erase: Erasing 7039 MBytes ....................................................................................................................<br />
Now it’s time to get the image online with basic connectivity so we can grab the ‘boot’ image. Here’s my config with IPs ‘X’ out:
<br /> rommon 14 > address 10.x.x.x<br /> rommon 15 > server 10.x.x.x<br /> rommon 16 > gateway 10.x.x.x<br /> rommon 17 > file ftd-boot-184.108.40.206.lfbff<br /> rommon 18 > set<br /> ADDRESS=10.x.x.x<br /> NETMASK=255.255.255.0<br /> GATEWAY=10.x.x.x<br /> SERVER=10.x.x.x<br /> IMAGE=ftd-boot-220.127.116.11.lfbff<br /> CONFIG=<br /> PS1="rommon ! > "
rommon 19 > sync
All set, time to tell it to download that ‘boot’ image:
<br /> rommon 20 > tftpdnld<br /> ADDRESS: 10.x.x.x<br /> NETMASK: 255.255.255.0<br /> GATEWAY: 10.x.x.x<br /> SERVER: 10.x.x.x<br /> IMAGE: ftd-boot-18.104.22.168.lfbff<br /> VERBOSITY: Progress<br /> RETRY: 40<br /> PKTTIMEOUT: 7200<br /> BLKSIZE: 1460<br /> CHECKSUM: Yes<br /> PORT: GbE/1<br /> PHYMODE: Auto Detect
Receiving ftd-boot-22.214.171.124.lfbff from 10.x.x.x!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
File reception completed.
Boot buffer bigbuf=348bd018
Boot image size = 104813248 (0x63f52c0) bytes
[image size] 104813248
[MD5 signaure] 914afb2d31d061910d22933d679aabb3
LFBFF signature verified.
INIT: version 2.88 booting
Some more cool boot init stuff will blow by until you get to the basic boot CLI environment:
<br /> Cisco FTD Boot 6.0.0 (126.96.36.199)<br /> Type ? for list of commands<br /> firepower-boot>?<br /> show => Display system information. Enter show ? for options<br /> system => Control system operation<br /> setup => System Setup Wizard<br /> support => Support information for TAC<br /> delete => Delete files<br /> ping => Ping a host to check reachability<br /> traceroute => Trace the route to a remote host<br /> exit => Exit the session<br /> help => Get help on command syntax<br />
At this stage we issue the setup command to get the boot-image appliance on the network so it can grab, download and extract the actual operating system image it will install on the appliance:
<br /> firepower-boot>setup
Welcome to Cisco FTD Setup
[hit Ctrl-C to abort]
Default values are inside 
Enter a hostname [firepower]:
Do you want to configure IPv4 address on management interface?(y/n) [Y]:
Do you want to enable DHCP for IPv4 address assignment on management interface?(y/n) [Y]:
Do you want to configure static IPv6 address on management interface?(y/n) [N]:
Do you want to enable the NTP service? [Y]:
Please review the final configuration:
Management Interface Configuration
IPv4 Configuration: dhcp
IPv6 Configuration: Stateless autoconfiguration
You have selected DHCP. The system will stop functioning correctly if DHCP
changes the assigned address due to lease expiration or other reasons.
We suggest you use static addressing instead.
You have selected IPv6 stateless autoconfiguration, which assigns a global address
based on network prefix and a device identifier. Although this address is unlikely
to change, if it does change, the system will stop functioning correctly.
We suggest you use static addressing instead.
Apply the changes?(y,n) [Y]:
Configuration saved successfully!
Restarting network services…
Press ENTER to continue…
PING 188.8.131.52 (184.108.40.206) 56(84) bytes of data.
64 bytes from 220.127.116.11: icmp_seq=1 ttl=59 time=7.65 ms
64 bytes from 18.104.22.168: icmp_seq=2 ttl=59 time=7.67 ms
64 bytes from 22.214.171.124: icmp_seq=3 ttl=59 time=7.66 ms
— 126.96.36.199 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 7.650/7.665/7.679/0.101 ms
And here we go with the actual reimage, CAUTION – this part will take about 45-60 minutes to complete and then reboot.
<br /> firepower-boot> system install noconfirm http://x.x.x.x/cisco/ftd-6.2.2-81
######################## WARNING ############################
# The content of disk0: will be erased during installation! #
Do you want to continue? [y/N] y
Erasing disk0 …
Description: Cisco ASA-FTD 6.2.2-81 System Install
Requires reboot: Yes
Warning: Please do not interrupt the process or turn off the system.
Doing so might leave system in unusable state.
Starting upgrade process …
Populating new system image
Broadcast message from root@firepower (ttyS1) (Thu Sep 28 14:17:58 2017):
The system is going down for reboot NOW!
If all goes well you’re now rebooted back in to a freshly installed Cisco ASA FirePower Threat Defense appliance.
——————-[ firepower ]——————–
Model : Cisco ASA5508-X Threat Defense (75) Version 6.2.2 (Build 81)
Good Luck !!