topic The most common cause would in Network Security

Failover - Getting Comm Failure for Secondary asa5525

prakhar_srivastava7 — Tue, 12 Mar 2019 09:25:47 GMT

I am not able to join firewall pair in failover.

Pri# sh failover state

State Last Failure Reason Date/Time
This host - Primary
Active None
Other host - Secondary
Failed Comm Failure 19:17:09 UTC May 26 2017

====Configuration State===
====Communication State===

sh fail history
==========================================================================
From State To State Reason
==========================================================================
19:16:07 UTC May 26 2017
Not Detected Negotiation No Error

19:16:53 UTC May 26 2017
Negotiation Just Active No Active unit found

19:16:53 UTC May 26 2017
Just Active Active Drain No Active unit found

19:16:53 UTC May 26 2017
Active Drain Active Applying Config No Active unit found

19:16:53 UTC May 26 2017
Active Applying Config Active Config Applied No Active unit found

19:16:53 UTC May 26 2017
Active Config Applied Active No Active unit found

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

The most common cause would

Marvin Rhoads — Mon, 29 May 2017 02:35:58 GMT

The most common cause would be a problem with the failover link. Please check the cable. If there's a switch in between, try bypassing it.

hi,

johnlloyd_13 — Mon, 29 May 2017 06:39:55 GMT

hi,

are you able to SSH or console to the standby FW and issue below and post here:

show failover

show failover state

show failover history

you can use debug fover cable and would see the below error/log:

Failover LAN Failed

Failover LAN became OK

you could also try a reload the standby unit and see if it would help.