Traceroute to test network connectivity:
firepower-boot>traceroute -n 10.100.100.1
traceroute to 10.100.100.1 (10.100.100.1), 30 hops max, 60 byte packets
1 10.123.123.1 0.937 ms 1.078 ms 1.154 ms^C
firepower-boot>
Step 9 To troubleshoot installation failures, see the following examples.
Example:
"Timed out" error
At the downloading stage, if the file server is not reachable, it will fail due to a time out.
...
Erasing disk0 ...
Verifying
timed out
Upgrade aborted
firepower-boot>
In this case, make sure the file server is reachable from the ASA. You can verify by pinging the file server.
"Package not found" error
If the file server is reachable, but the file path or name is wrong, the installation fails with a "Package not
found" error:
...
Erasing disk0 ...
Verifying
Package not found. Please correct the URL, which should include the full path including
package name.
Upgrade aborted.
firepower-boot>
In this case, make sure the FTD package file path and name is correct.
Installation failed with unknown error
When the installation occurs after the system software has been downloaded, the cause is generally displayed
as "Installation failed with unknown error". When this error happens, you can troubleshoot the failure by
viewing the installation log:
firepower-boot>support view logs
===View Logs===
============================
Directory: /var/log
----------sub-dirs----------
cisco
sa
-----------files------------
2015-09-24 19:56:33.150011 | 102668 | install.log
2015-09-24 19:46:28.400002 | 292292 | lastlog
2015-09-24 19:45:15.510001 | 250 | ntp.log
Cisco ASA and Firepower Threat Defense Reimage Guide
12
Cisco ASA and Firepower Threat Defense Reimage Guide
Reimage from ASA to Firepower Threat Defense
To Next Page
Loading...
Need help?
General
