Cisco ASA failover issue

Madhan Kumar · ‎08-27-2013

Hi Team,

We have three facilities where deployed Cisco 5520 in active/standby mode. In one facility (A) the management tool is showing out of sync for facilty A. But one difference is " sh failover state". Sync done - Standby is missing on the facility A. But sh failover is showing properly. Can anyone help what need to be done to resolve this issue. Below is the output of " sh failover State ".

No sync issue facility

sh failover state

               State          Last Failure Reason      Date/Time
This host -   Primary
               Active         None
Other host -   Secondary
               Standby Ready Comm Failure             09:59:18 IST Jul 20 2013

====Configuration State===
        Sync Done
        Sync Done - STANDBY
====Communication State===
        Mac set

Sync issue Facility: A

sh failover state

               State          Last Failure Reason      Date/Time
This host -   Primary
               Active         None
Other host -   Secondary
               Standby Ready None

====Configuration State===
Sync Done
====Communication State===
Mac set

Marvin Rhoads · ‎08-27-2013

I suspect at one time the primary unit at your first site was in standby mode and a cosmetic bug is not causing it to revert to the normally expected "sync done" state.

FYI here is an explanation of the output: Table 49-2

Madhan Kumar · ‎08-27-2013

Hi Marvin,

Thanks for your inputs. Can you suggest what needs to do to resolve this issue?. Still the NMS tool is showing out of sync for this facility. Some time back the firwalls are rebooted.

Madhan Kumar · ‎08-28-2013

Hi Marvin,

Also I am seeing one error on the scondary device.

sh failover history

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

From State To State Reason

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

18:09:13 IST Aug 27 2013
Standby Ready Cold Standby Configuration mismatch

18:09:15 IST Aug 27 2013
Cold Standby Sync Config Configuration mismatch

18:09:30 IST Aug 27 2013
Sync Config Sync File System Configuration mismatch

18:09:30 IST Aug 27 2013
Sync File System Bulk Sync Configuration mismatch

18:09:42 IST Aug 27 2013
Bulk Sync Standby Ready Configuration mismatch

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

Marvin Rhoads · ‎08-28-2013

That looks normal - it just shows the history and reason for the state being triggered. The final state is "Standby Ready" which was finally reached after the earlier indicated steps due to configuration not initially matching that on the Primary Active unit.