https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904577#M24954 <P>FW/pri/act# sh failover history</P><P>==========================================================================</P><P>Group&nbsp;&nbsp;&nbsp;&nbsp; From State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reason</P><P>==========================================================================</P><P>16:17:43 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:17:57 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:17:57 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:20:20 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Sync Config&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:20 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:27 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:37 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:58 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp; &nbsp;&nbsp;Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>===================================================</P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P><PRE>sh failover state State Last Failure Reason Date/Time This host - Primary Group 1 Active Comm Failure 16:16:24 EEST Aug 5 2019 Group 2 Standby Ready Comm Failure 16:16:24 EEST Aug 5 2019 Other host - Secondary Group 1 Standby Ready None Group 2 Active None ====Configuration State=== Sync Done - STANDBY ====Communication State=== Mac set</PRE><P>&nbsp;</P> Wed, 07 Aug 2019 13:39:39 GMT kostasthedelegate 2019-08-07T13:39:39Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904496#M24952 <P>Hello,&nbsp;</P><P>&nbsp;</P><P>I have an active/ active pair of ASA with context enabled.&nbsp;</P><P>Suddenly, the failover switch to the secondary and then back to primary.&nbsp;</P><P>From show failover state, I see that the reason was "comm failure" on the primary.&nbsp;</P><P>&nbsp;</P><P>The failover cable is directly connected to each FW.&nbsp;</P><P>How could I determine why the failover occurred?</P><P>Could be sw or hw issue?</P><P>&nbsp;</P><P>Thanks and regards,&nbsp;</P><P>Konstantinos</P> Wed, 07 Aug 2019 11:28:40 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904496#M24952 kostasthedelegate 2019-08-07T11:28:40Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904569#M24953 <P>hi,</P><P>can you post a <STRONG>show failover state</STRONG> and <STRONG>show failover history</STRONG> output from the primary/active FW?</P> Wed, 07 Aug 2019 13:29:47 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904569#M24953 johnlloyd_13 2019-08-07T13:29:47Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904577#M24954 <P>FW/pri/act# sh failover history</P><P>==========================================================================</P><P>Group&nbsp;&nbsp;&nbsp;&nbsp; From State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reason</P><P>==========================================================================</P><P>16:17:43 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:17:57 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:17:57 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Detected an Active mate</P><P>16:20:20 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Sync Config&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:20 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Sync File System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:21 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Recovered from communication failure</P><P>16:20:27 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:37 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Bulk Sync&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No Error</P><P>16:20:58 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:20:59 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Standby Ready&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Just Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp; &nbsp;&nbsp;Active Drain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Active Applying Config&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>16:21:00 EEST Aug 5 2019</P><P>&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; Active Config Applied&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover state check</P><P>===================================================</P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P><PRE>sh failover state State Last Failure Reason Date/Time This host - Primary Group 1 Active Comm Failure 16:16:24 EEST Aug 5 2019 Group 2 Standby Ready Comm Failure 16:16:24 EEST Aug 5 2019 Other host - Secondary Group 1 Standby Ready None Group 2 Active None ====Configuration State=== Sync Done - STANDBY ====Communication State=== Mac set</PRE><P>&nbsp;</P> Wed, 07 Aug 2019 13:39:39 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904577#M24954 kostasthedelegate 2019-08-07T13:39:39Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904691#M24955 Having the cable directly connected between ASAs is a bad design because<BR />this won't allow you to find which ASA triggered the failover. Move this to<BR />connect ASAs failover link through L2 switch. This way you can find which<BR />ASA had comm failure.<BR /><BR />Comm Failed means that failover flapped. With L2 link between the ASAs you<BR />can tell which unit had the actual failure. With current design, if either<BR />ASA fails, it will show comms failure at both sides<BR /><BR />***** remember to rate useful posts<BR /> Wed, 07 Aug 2019 15:45:59 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3904691#M24955 Mohammed al Baqari 2019-08-07T15:45:59Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905055#M24956 <P>Hello Mohammed,&nbsp;</P><P>&nbsp;</P><P>I will have this point in mind for future deployments.&nbsp;</P><P>So right now I cannot tell which asa failed. The management connection is a L2.&nbsp;</P><P>&nbsp;</P><P>In failover state, only active asa shows comm failure. The secondary shows none.&nbsp;</P><P>&nbsp;</P><P>All in all, there is not a command in asa I could determine where the actual failure occurred(Hardware fault, software fault).&nbsp;</P><P>&nbsp;</P><P>Regards,&nbsp;</P><P>Konstantinos</P> Thu, 08 Aug 2019 06:27:19 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905055#M24956 kostasthedelegate 2019-08-08T06:27:19Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905706#M24957 <P>hi,</P><P>can you check for errors on the failover cable with a <STRONG>show interface g0/x</STRONG>?</P><P>most of our active-standby FW deployment have direct failover cable between them.</P><P>this will save switch ports and avoid design complexity and troubleshooting.</P><P>we have very few deployments via L2 switch or patch panels if the two FWs are in different racks..</P> Fri, 09 Aug 2019 01:08:32 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905706#M24957 johnlloyd_13 2019-08-09T01:08:32Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905791#M24958 <P>Hello,&nbsp;</P><P>&nbsp;</P><P>This is the output of the command&nbsp;</P><P>&nbsp;</P><P>Interface Ethernet1/16 "", is up, line protocol is up</P><P>&nbsp; Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAC address zzzz.zzzz.zzzz, MTU not set</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IP address unassigned</P><P>Interface Ethernet1/16.4001 "FAILOVER", is up, line protocol is up</P><P>&nbsp; Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; VLAN identifier 4001</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: LAN Failover Interface</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAC address zzzz.zzzz.zzzz, MTU 1500</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IP address xxx.xxx.xxx.xxx, subnet mask xxx.xxx.xxx.xxx</P><P>Interface Ethernet1/16.4002 "FOLINK", is up, line protocol is up</P><P>&nbsp; Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; VLAN identifier 4002</P><P>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Description: STATE Failover Interface</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAC address zzzz.zzzz.zzzz, MTU 1500</P><P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IP address xxx.xxx.xxx.xxx, subnet mask xxx.xxx.xxx.xxx</P><P>&nbsp;</P><P>&nbsp;</P><P>Is that any helpful?</P><P>&nbsp;</P><P>Regards,&nbsp;</P><P>Konstantinos</P> Fri, 09 Aug 2019 06:39:32 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3905791#M24958 kostasthedelegate 2019-08-09T06:39:32Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3906031#M24959 <P>Not really. I think we would like to see the output of each member of the cluster on their HA interface.</P><P>&nbsp;</P><P><A href="https://www.tunnelsup.com/understanding-cisco-asa-interface-counters-and-statistics/" target="_blank">https://www.tunnelsup.com/understanding-cisco-asa-interface-counters-and-statistics/</A></P> Fri, 09 Aug 2019 14:15:09 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3906031#M24959 steven_dolan7 2019-08-09T14:15:09Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3913875#M24960 <P>Hello,&nbsp;</P><P>&nbsp;</P><P>We have enabled collection of logs and if anything appears we will examine it.&nbsp;</P><P>&nbsp;</P><P>Thank you all for your help.</P><P>&nbsp;</P><P>Regards,&nbsp;</P><P>Konstantinos</P> Mon, 26 Aug 2019 07:21:01 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/3913875#M24960 kostasthedelegate 2019-08-26T07:21:01Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4599121#M1089508 <P>Hi&nbsp;<SPAN>Konstantinos</SPAN></P><P>I have similar trouble with ASA. Do you recollect whether you got it resolved? If yes.. Can you please brief me how?</P><P>&nbsp;</P><P>Regards</P><P>Hariz</P> Mon, 25 Apr 2022 10:32:23 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4599121#M1089508 harizmthaha 2022-04-25T10:32:23Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4601783#M1089623 <P>Hi bro</P><P>&nbsp; I have same issue failover history "<SPAN>Recovered from communication failure</SPAN>" , how troubshoot it?&nbsp;</P><P>&nbsp; two unit ping eachouther not any packet loss.</P> Thu, 28 Apr 2022 13:43:55 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4601783#M1089623 jadon 2022-04-28T13:43:55Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4601785#M1089624 <P>Hi bro&nbsp;</P><P>&nbsp; I have same too . have you&nbsp; find any resolution ?</P> Thu, 28 Apr 2022 13:46:23 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4601785#M1089624 jadon 2022-04-28T13:46:23Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4613163#M1090224 <P>Hi Jadon</P> <P>It is not yet resolved. Im still searching for the solution, please let me know if you find something.&nbsp;</P> Thu, 19 May 2022 14:57:48 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4613163#M1090224 harizmthaha 2022-05-19T14:57:48Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4614877#M1090306 <P>Hi&nbsp;<SPAN>harizmthaha</SPAN></P> <P>&nbsp; I found a&nbsp;temporay solution . you can try increase the HA poll time ,interface time.</P> <P>&nbsp; in my use case. the HA state&nbsp; comm failure due to HA pairs lost community , when HA pairs community lost packet .</P> Sun, 22 May 2022 06:45:43 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4614877#M1090306 jadon 2022-05-22T06:45:43Z https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4630525#M1090861 <P>Hi Jadon,</P> <P>Thanks for letting me know. we have planned for Rommon and IOS upgrade this week. I will update you if that permanently fixes this trouble.</P> Mon, 13 Jun 2022 05:55:44 GMT https://community.cisco.com/t5/network-security/asa-failover-reason/m-p/4630525#M1090861 harizmthaha 2022-06-13T05:55:44Z