ASA 5555-X Rebooting

[sandeep.thawait]

I have one ASA 5555X Firewall. In which i am facing frequently rebooting problem. I have capture the console log as below.

Please suggest for resolution. 

Failed to send indication to guest VM no: 35251

ERROR - Failed to send indication to ex/asa/scripts/run_qemu_kvm.sh: line 120:  1659 Trace/breakpoint trap   (core dumped) /usr/bin/qemu-system-x86_64 -nographic -m $SYS_RAM -smp $NUM_CORES -hda $DISK_IMAGE $HDD_PARAM $ISO_IMAGE -enable-kvm -net nic,macaddr=$CP_MAC_ADDRESS,model=$DRIVER,vlan=1,name=cp,addr=$CP_BUS_ADDR -net tap,ifname=tap3,vlan=1,script=no,downscript=no -net nic,macaddr=$MGMT_MAC,model=$DRIVER,vlan=2,name=mgmt,addr=$MGT_BUS_ADDR -net tap,ifname=tap4,vlan=2,script=no,downscript=no -net nic,model=e1000,name=data,addr=$DATA_BUS_ADDR -serial pipe:$LOG_PIPE -serial unix:$CONSOLE_SOCKET,server,nowait -fdb $META_INFO -monitor /dev/null $IPS_NO_RRebooting... (status 0x9)

..

Deconfiguring network interfaces... done.

Sending all processes the TERM signal...

Sending all processes the KILL signal...

Deactivating swap...

Unmounting local filesystems...

Rebooting... 

[Jonathan Unger]

There are a few nasty reboot bugs going around affecting 5500X series ASAs with the FirePower module enabled.

A few questions:

1. Have you recently upgraded your ASA code?
2. Are you running the FirePOWER module?

I would recommend opening a TAC case to confirm exactly which BugID you are hitting and what workarounds are available for your situation.

[Malik Saqib]

I ran into the same exact issue after trying to re-image 5506-X to the new FTD image:

Rebooting... (status 0x9)
..
INIT: Sending processes the TERM signal
Deconfiguring network interfaces... done.
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Deactivating swap...
Unmounting local filesystems...
Rebooting...

After trying almost everything I ended up booting to the asa image from the tftp server and did an "erase disk0:" and finally got it working (erase disk from rommon didn't work for me. It went through the motions pretty quickly but didn't really do anything).

For those who might be new to this stuff, here are the steps:

Reload/power cycle the box, use BREAK or ESC to interrupt boot. Once in rommon mode, set the following:

rommon 6 > address 10.10.10.34
rommon 7 > netmask 255.255.255.0
rommon 8 > server 10.10.10.30
rommon 9 > gateway 10.10.10.1
rommon 10 > file asa971-4-lfbff-k8.SPA (or whichever image file you have)
rommon 11 > set
    ADDRESS=10.10.10.34
    NETMASK=255.255.255.0
    GATEWAY=10.10.10.1
    SERVER=10.10.10.30
    IMAGE=asa971-4-lfbff-k8.SPA
    CONFIG=
    PS1="rommon ! > "

rommon 12 > tftpdnld
             ADDRESS: 10.10.10.34
             NETMASK: 255.255.255.0
             GATEWAY: 10.10.10.1
              SERVER: 10.10.10.30
               IMAGE: asa971-4-lfbff-k8.SPA
             MACADDR: a4:6c:2a:99:fa:a7
           VERBOSITY: Progress
               RETRY: 40
          PKTTIMEOUT: 7200
             BLKSIZE: 1460
            CHECKSUM: Yes
                PORT: GbE/1
             PHYMODE: Auto Detect

Receiving asa971-4-lfbff-k8.SPA from 10.10.10.30!!!!!!!

File reception completed.

Once in the cli:

ciscoasa# erase disk0:
Erase operation may take a while. Continue? [confirm]
Erasing the disk0 filesystem will remove all files! Continue? [confirm]
Initializing partition - done!
Creating FAT32 filesystem
mkdosfs 2.11 (12 Mar 2005)
EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

System tables written to disk
Erase of disk0: complete

Took about 30 minutes or so for it to finish....will depend on the drive size.

ciscoasa# dir
Directory of disk0:/
No files in directory
7934787584 bytes total (7934754816 bytes free)

Copied the new new image and it worked like a champ.....if I could only get those two hours of my life back from Cisco :)