cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
784
Views
3
Helpful
8
Replies

Firepower 1010 (ASA image) random reboots

Chess Norris
Level 4
Level 4

Hello,

I have a customer reporting that multiple Firepower 1010 with ASA image randomly reboots. 

There is no crash dumps, but we found this in the log - 2023 Oct 29 11:05:43 PMLOG: Last reset cause: PowerOn (0x00000001)

According to the customer, those devices are located in different data centers and there has been no power outages. They just mysteriously reboots. Does anyone have experienced a similar issue?  

Thanks

/Chess

8 Replies 8

Thanks for the reply,

The bug seems related to quite old versions of FXOS and not mention which ASA versions the fix is implemented in.

Customer is running ASA version 9.16(4)42 with FXOS version 2.10.1.1611

Thanks

/Chess

 

Deepak Kumar
VIP Alumni
VIP Alumni

Known bug as mentioned above

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

Chess Norris
Level 4
Level 4

Just opened a TAC case on this and the engineer didn't think the issue was related to the abowe bug. The log output didn't match. Instead it seams like a bad batch of PSU:s and TAC created a RMA

Quote: "Since the reset cause is “power on”, am sure that the issue is a hardware issue, not a software"

/Chess

 

First you mention multiple not one 

Second the fpr 1k reboot  reason is not so accurate' there is also bug for it.

For fpr the fxos is based and then ftd or asa image come on.

I think it fxos issue.

But let say

Please keep update us.

MHM

Yes, it's multiple Firepower 1010 devices. About 3 out of 10 devices with the same issue. 

Firepower 1100 and 2000 series dont have separate FXOS (like 4100 and 9300 series). FXOS is already builtin in the ASA/FTD image. There is no mention on fixed ASA/FTD versions in the bug, so hard to say in which version they fixed this issue.

/Chess

Nope, the bug clearly says that the issue has been fixed in 9.16.1. It has also been fixed in 9.12.4.39 and 9.14.3. Affected versions are listed here: https://www.cisco.com/c/en/us/support/docs/field-notices/722/fn72282.html

So, the mentioned bug doesn't apply, but the root cause might be similar. To troubleshoot you probably need to permanently connect to FXOS console writing all output to a local file. If 2100 is running in platform mode, console is serviced by FXOS. If it is running in appliance mode, console is serviced by ASA and you need to "connect fxos admin" from there. Check "show fxos mode" in ASA.

 

Since it's FP1k, it can run in appliance mode only. Sorry for the confusion.

 

Review Cisco Networking for a $25 gift card