cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1720
Views
5
Helpful
7
Replies

Cisco ASA5585 reboot unexpectedly.

Hi all,

We have ASA5585 in failover setup, as primary and secondary unit.

And my primary unit has reboot two times with unknow reason, no crashinfo file. The first occurred in February, and the second occurred last week.

I need to know the root cause of this case and prevent the device from rebooting again. Do you have any suggestions?

 

Current version: 9.12(4)38

Primary unit.

------------------ show failover history ------------------

==========================================================================
From State To State Reason
==========================================================================
16:53:19 ICT Apr 21 2022
Not Detected Negotiation No Error

16:53:23 ICT Apr 21 2022
Negotiation Cold Standby Detected an Active mate

16:53:25 ICT Apr 21 2022
Cold Standby Sync Config Detected an Active mate

16:54:26 ICT Apr 21 2022
Sync Config Sync File System Detected an Active mate

16:54:26 ICT Apr 21 2022
Sync File System Bulk Sync Detected an Active mate

16:54:40 ICT Apr 21 2022
Bulk Sync Standby Ready Detected an Active mate

==========================================================================

------------------ show environment ------------------


Cooling Fans:
-----------------------------------

Power Supplies:
--------------------------------
Left Slot (PS0): 5900 RPM - OK (Power Supply Fan)
Right Slot (PS1): 6000 RPM - OK (Power Supply Fan)

Power Supplies:
-----------------------------------
Power Supply Unit Redundancy: OK

Left Slot (PS0): Present
Right Slot (PS1): Present

Power Input:
--------------------------------
Left Slot (PS0): OK
Right Slot (PS1): OK

Temperature:
--------------------------------
Left Slot (PS0): 29 C - OK (Power Supply Temperature)
Right Slot (PS1): 28 C - OK (Power Supply Temperature)

Cooling Fans:
--------------------------------
Left Slot (PS0): 5900 RPM - OK (Power Supply Fan)
Right Slot (PS1): 6000 RPM - OK (Power Supply Fan)

Temperature:
-----------------------------------

Processors:
--------------------------------
Processor 1: 47.0 C - OK (CPU1 Core Temperature)

Chassis:
--------------------------------
Ambient 1: 32.0 C - OK (Chassis Front Temperature)
Ambient 2: 38.0 C - OK (Chassis Back Temperature)
Ambient 3: 31.0 C - OK (CPU1 Front Temperature)
Ambient 4: 32.25 C - OK (CPU1 Back Temperature)

IO Hub:
--------------------------------
Circuit Die: 53.0 C - OK (Circuit Die Temperature)

Power Supplies:
--------------------------------
Left Slot (PS0): 29 C - OK (Power Supply Temperature)
Right Slot (PS1): 28 C - OK (Power Supply Temperature)

Voltage:
-----------------------------------
Channel 1: 3.307 V - (3.3V (U142 VX1))
Channel 2: 1.490 V - (1.5V (U142 VX2))
Channel 3: 1.049 V - (1.05V (U142 VX3))
Channel 4: 3.337 V - (3.3V_STDBY (U142 VP1))
Channel 5: 11.665 V - (12V (U142 VP2))
Channel 6: 4.934 V - (5.0V (U142 VP3))
Channel 7: 6.630 V - (7.0V (U142 VP4))
Channel 8: 9.962 V - (IBV (U142 VH))
Channel 9: 1.045 V - (1.05VB (U209 VX2))
Channel 10: 1.211 V - (1.2V (U209 VX3))
Channel 11: 1.106 V - (1.1V (U209 VX4))
Channel 12: 1.004 V - (1.0V (U209 VX5))
Channel 13: 3.330 V - (3.3V STDBY (U209 VP1))
Channel 14: 2.495 V - (2.5V (U209 VP2))
Channel 15: 1.796 V - (1.8V (U209 VP3))
Channel 16: 1.901 V - (1.9V (U209 VP4))
Channel 17: 9.978 V - (IBV (U209 VH))
Channel 18: 2.048 V - (VTT CPU0 (U83 VX2))
Channel 19: 0.000 V - (VTT CPU1 (U83 VX3))
Channel 20: 2.048 V - (VCC CPU0 (U83 VX4))
Channel 21: 1.769 V - (VCC CPU1 (U83 VX5))
Channel 22: 1.516 V - (1.5VA (U83 VP1))
Channel 23: 0.001 V - (1.5VB (U83 VP2))
Channel 24: 8.937 V - (IBV (U83 VH))

ALARM CONTACT 1
Status: not asserted
Description: external alarm contact 1
Severity: minor
Trigger: closed

ALARM CONTACT 2
Status: not asserted
Description: external alarm contact 2
Severity: minor
Trigger: closed

 

 

 

Secondary unit.

------------------ show failover history ------------------

==========================================================================
From State To State Reason
==========================================================================
00:09:36 ICT Mar 19 2022
Not Detected Negotiation No Error

00:09:41 ICT Mar 19 2022
Negotiation Cold Standby Detected an Active mate

00:09:43 ICT Mar 19 2022
Cold Standby Sync Config Detected an Active mate

00:11:10 ICT Mar 19 2022
Sync Config Sync File System Detected an Active mate

00:11:10 ICT Mar 19 2022
Sync File System Bulk Sync Detected an Active mate

00:11:22 ICT Mar 19 2022
Bulk Sync Standby Ready Detected an Active mate

00:31:17 ICT Mar 19 2022
Standby Ready Just Active Set by the config command

00:31:17 ICT Mar 19 2022
Just Active Active Drain Set by the config command

00:31:17 ICT Mar 19 2022
Active Drain Active Applying Config Set by the config command

00:31:17 ICT Mar 19 2022
Active Applying Config Active Config Applied Set by the config command

00:31:17 ICT Mar 19 2022
Active Config Applied Active Set by the config command

01:14:35 ICT Mar 19 2022
Active Standby Ready Other unit wants me Standby

15:34:25 ICT Apr 19 2022
Standby Ready Failed Interface check
This host:1
single_vf: Internet
Other host:0

15:34:40 ICT Apr 19 2022
Failed Standby Ready Interface check
This host:0
Other host:0

16:51:27 ICT Apr 21 2022
Standby Ready Just Active HELLO not heard from mate

16:51:28 ICT Apr 21 2022
Just Active Active Drain HELLO not heard from mate

16:51:28 ICT Apr 21 2022
Active Drain Active Applying Config HELLO not heard from mate

16:51:28 ICT Apr 21 2022
Active Applying Config Active Config Applied HELLO not heard from mate

16:51:28 ICT Apr 21 2022
Active Config Applied Active HELLO not heard from mate

 

=============================================

Thank you,

7 Replies 7

can I see

show failover 
in both active and standby 

Thank you for responding, please see the output in attachment.

marce1000
Hall of Fame
Hall of Fame

 

 - Connect to (current) ASA trough SSH with : https://cway.cisco.com/cli , at the top left press or  run 'System Diagnostics'  and or the right you can also use 'Crash dump Analysis' , the latter may also be useful even if not crash dump can be found at first glance.

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Hello, Sir

Thank you for responding.

I analyzed the show-tech file with the Cisco CLI analyzer, the result as the attached.

Thank you,

 

            - There is no attachment , 

M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Sorry,

Please see the attachment.

 

 - The mentioned bug report at the beginning https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc91204  , should only be cosmetic and have no impact , for the rest I can't conclude further or give more items as feedback , you will have to create a ticket at Cisco (contact TAC) to further be able to resolve this. You may  then forward that analysis from CLI Analyzer  too.

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
Review Cisco Networking for a $25 gift card