ASA Standby Switching to Failed state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 02:11 AM
We have two ASA application (9.8) Active/Standby on two Firepower 4110. We detected a failed state on the Standby ASA.
On the Active we are seen this message:
Number of interfaces on Active and Standby are not consistent.
If the problem persists, you should disable and re-enable failover on the Standby.
However the interface are exactly the same.
FW# sh failover state
State Last Failure Reason Date/Time
This host - Secondary
Bulk Sync MIO Heartbeat Failure 08:56:37 CET Jun 16 2020
Other host - Primary
Active Comm Failure 22:20:45 CET Jun 15 2020
====Configuration State===
Sync Done
Sync Done - STANDBY
====Communication State===
Mac set
Could any body help me with this ? This is going on and on for hours now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 02:41 AM
As per my experience
Find below mentioned steps which will help you
1. Check all interface of Primary and Secondary and check traffic .
if any interface showing inactive so refresh it by enable disable it
2. Once you done this check device up time - show version - it will give you information if device rebooted or not
show failover history
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 07:09 AM
Thank you for your reply, we double checked the interfaces, we even applied no monitor-interface on all the interface.. on all context, but still the same message:
If the problem persists, you should disable and re-enable failover on the Standby.
Number of interfaces on Active and Standby are not consistent.
