topic Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable) in Network Security

Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Skander27 — Tue, 07 Apr 2020 14:01:05 GMT

Hi i had to reimage a FTD because it's upgrade (6.2.0 to 6.2.3) from FMC went wrong...

So while reimaging precisely after the image has been downloaded with FTP, the extraction of the file is interrupted with no clear reason! This is the content of the /var/log/error file from Cisco FTD Boot 6.0.0 (9.7.1.) :

ftd-boot>support view logs

===View Logs===

============================
Directory: /var/log
----------sub-dirs----------
cisco
sa
-----------files------------
2005-01-01 01:13:34.765047 | 1903 | error
2005-01-01 01:03:05.265047 | 292292 | lastlog
2005-01-01 01:13:34.765047 | 61735 | messages
2005-01-01 01:04:27.855047 | 1370 | ntp.log
2005-01-01 01:03:05.265047 | 4608 | wtmp

([b] to go back or [s] to select a file to view, [Ctrl+C] to exit)
Type a sub-dir name to list its contents: s

Type the name of the file to view ([b] to go back, [Ctrl+C] to exit)
> error
Jan 1 01:03:04 ciscoasa kernel: [ 2.747417] Failed to execute /init
Jan 1 01:03:04 ciscoasa kernel: [ 2.913476] watchdog: iTCO_wdt: cannot regis
ter miscdev on minor=130 (err=-16).
Jan 1 01:03:04 ciscoasa kernel: [ 2.913476] watchdog: iTCO_wdt: a legacy wat
chdog module is probably present.
Jan 1 01:03:04 ciscoasa kernel: [ 4.549417] sd 6:0:0:0: [sdb] No Caching mod
e page found
Jan 1 01:03:04 ciscoasa kernel: [ 4.549421] sd 6:0:0:0: [sdb] Assuming drive
cache: write through
Jan 1 01:03:04 ciscoasa kernel: [ 4.558550] sd 6:0:0:0: [sdb] No Caching mod
e page found
Jan 1 01:03:04 ciscoasa kernel: [ 4.558555] sd 6:0:0:0: [sdb] Assuming drive
cache: write through
Jan 1 01:03:04 ciscoasa kernel: [ 4.567810] sd 6:0:0:0: [sdb] No Caching mod
e page found
Jan 1 01:03:04 ciscoasa kernel: [ 4.567815] sd 6:0:0:0: [sdb] Assuming drive
cache: write through
Jan 1 01:04:04 ciscoasa syslog-ng[1900]: Connection failed; fd='15', server='AF
_INET(127.128.254.1:514)', local='AF_INET(0.0.0.0:0)', error='Network is unreach
able (101)'
Jan 1 01:04:04 ciscoasa syslog-ng[1900]: Initiating connection failed, reconnec
ting; time_reopen='60'
Jan 1 01:09:46 ciscoasa kernel: [ 413.631575] Out of memory: Kill process 1990
(python) score 24 or sacrifice child
Jan 1 01:09:46 ciscoasa kernel: [ 413.631578] Killed process 1990 (python) tot
al-vm:511940kB, anon-rss:48176kB, file-rss:2336kB
Jan 1 01:13:33 ciscoasa kernel: [ 640.703473] Out of memory: Kill process 2018
(python) score 11 or sacrifice child
Jan 1 01:13:33 ciscoasa kernel: [ 640.703475] Killed process 2018 (python) tot
al-vm:485632kB, anon-rss:21872kB, file-rss:2312kB
Jan 1 01:13:34 ciscoasa kernel: [ 642.345091] Out of memory: Kill process 2065
(python) score 9 or sacrifice child
Jan 1 01:13:34 ciscoasa kernel: [ 642.345093] Killed process 2066 (python) tot
al-vm:86656kB, anon-rss:17104kB, file-rss:696kB

I have many FTD to manage and 3 FMCs but this is the first time this happen and there is no similar case on the internet, i hope this copy paste can help.

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Marvin Rhoads — Tue, 07 Apr 2020 15:29:58 GMT

Assuming you've already verified the image's file hash, I'd open a TAC case for this one.

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

imed.jlailia — Wed, 08 Apr 2020 18:33:54 GMT

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Skander27 — Wed, 08 Apr 2020 18:38:31 GMT

I found the problem the BIOS is detecting 2GB instead of 4GB

Now i have to find out if the problem is coming from the motherboard or the modules.

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

apapa — Fri, 10 Apr 2020 14:20:49 GMT

Hi,

I am having the same issue . Did you figure this out ?

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

imed.jlailia — Fri, 10 Apr 2020 18:00:13 GMT

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Skander27 — Fri, 10 Apr 2020 18:08:42 GMT

Yes as i said the problem is that BIOS is detecting 2GB instead of 4GB.

Here is the output after:

Cisco BIOS Version:9B2C111A

Build Date:10/06/2016 07:47:37

CPU Type: Intel(R) Pentium(R) CPU G6950 @ 2.80GHz, 2793 MHz

Total Memory:2048 MB(DDR3 1066)

System memory:619 KB, Extended Memory:2037 MB

*************************************************************

I tried dims from another FTD and I think that there is a defect in the PSU that caused an irrevocable failure in the motherboard.

who knows maybe upgrading the ROMMON fix it.

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

apapa — Sat, 11 Apr 2020 00:43:45 GMT

You were able to upgrade the rommon on asa-5512-X ?
How did you do that ?
Is there a rommon image for that ?If there is please sent me the url

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Skander27 — Sat, 11 Apr 2020 09:15:59 GMT

i never tried it but it depends on your model this link describe the upgrade steps for ASA 5506-X, 5508-X, and 5516-X:
https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200884-installing-and-upgrading-firepower-threa.html#anc8

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

apapa — Sat, 11 Apr 2020 11:27:46 GMT

Yes , i know its possible for these models ASA 5506-X, 5508-X, and 5516-X but not the 5512-x.

I thought your model was a 5512-x

Re: Extracting FTD image while reimaging ASA 5512 interrupted (Unexpected error: Upgrade status unavailable)

Skander27 — Sat, 11 Apr 2020 16:10:21 GMT

My model is 5512 if you have this line Total Memory:2048 MB(DDR3 1066) in BIOS startup then try to put another DIMM if you have and see if it's a dimm or motherboard issue, if it's not the dimm you have to open a TAC case you don't have any other choice i believe.