Hello
I have a pair of ASAs in HA mode. Primary active, secondary standby ready.
But since September 1, the secondary has become active and the primary has become standby ready.
When I connect in ssh on the interface:
ASA/act# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: bckfail GigabitEthernet1/8 (up)
Reconnect timeout 0:00:00
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 2 of 410 maximum
MAC Address Move Notification Interval not set
failover replication http
Version: Ours 9.16(4)14, Mate 9.16(4)14
Serial Number: Ours JAD24330TGU, Mate JAD24330TA2
Last Failover at: 13:30:44 CEDT Sep 1 2023
This host: Secondary - Active
Active time: 873756 (sec)
slot 1: ASA5516 hw/sw rev (3.4/9.16(4)14) status (Up Sys)
Interface Outside (89.90.218.155): Normal (Monitored)
Interface Inside (10.39.6.5): Normal (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
Other host: Primary - Standby Ready
Active time: 14668767 (sec)
slot 1: ASA5516 hw/sw rev (3.4/9.16(4)14) status (Up Sys)
Interface Outside (89.90.218.154): Normal (Monitored)
Interface Inside (10.39.6.50): Normal (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
ASA/act#sh failover history
==========================================================================
From State To State Reason
==========================================================================
17:55:15 CEST Mar 15 2023
Not Detected Negotiation No Error
17:55:19 CEST Mar 15 2023
Negotiation Cold Standby Detected an Active mate
17:55:20 CEST Mar 15 2023
Cold Standby Sync Config Detected an Active mate
17:55:40 CEST Mar 15 2023
Sync Config Sync File System Detected an Active mate
17:55:40 CEST Mar 15 2023
Sync File System Bulk Sync Detected an Active mate
17:55:56 CEST Mar 15 2023
Bulk Sync Standby Ready Detected an Active mate
13:30:43 CEDT Sep 1 2023
Standby Ready Just Active Interface check
This host:0
Other host:0
13:30:44 CEDT Sep 1 2023
Just Active Active Drain Interface check
This host:0
Other host:0
13:30:44 CEDT Sep 1 2023
Active Drain Active Applying Config Interface check
This host:0
Other host:0
13:30:44 CEDT Sep 1 2023
Active Applying Config Active Config Applied Interface check
This host:0
Other host:0
13:30:44 CEDT Sep 1 2023
Active Config Applied Active Interface check
This host:0
Other host:0
If i do the same on the second :
ASA/act#failover exec standby sh failover
Last Failover at: 13:30:43 CEDT Sep 1 2023
This host: Primary - Standby Ready
Active time: 14668767 (sec)
slot 1: ASA5516 hw/sw rev (3.4/9.16(4)14) status (Up Sys)
Interface Outside (89.90.218.154): Normal (Monitored)
Interface Inside (10.39.6.50): Normal (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
Other host: Secondary - Active
Active time: 874152 (sec)
slot 1: ASA5516 hw/sw rev (3.4/9.16(4)14) status (Up Sys)
Interface Outside (89.90.218.155): Normal (Monitored)
Interface Inside (10.39.6.5): Normal (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
slot 2: SFR5516 hw/sw rev (N/A/6.2.2-81) status (Up/Up)
ASA FirePOWER, 6.2.2-81, Up, (Monitored)
ASA/act#failover exec standby sh failover history
==========================================================================
From State To State Reason
==========================================================================
17:48:47 CEST Mar 15 2023
Not Detected Negotiation No Error
17:48:51 CEST Mar 15 2023
Negotiation Cold Standby Detected an Active mate
17:48:52 CEST Mar 15 2023
Cold Standby Sync Config Detected an Active mate
17:49:12 CEST Mar 15 2023
Sync Config Sync File System Detected an Active mate
17:49:12 CEST Mar 15 2023
Sync File System Bulk Sync Detected an Active mate
17:49:27 CEST Mar 15 2023
Bulk Sync Standby Ready Detected an Active mate
17:51:42 CEST Mar 15 2023
Standby Ready Just Active Other unit wants me Active
17:51:42 CEST Mar 15 2023
Just Active Active Drain Other unit wants me Active
17:51:42 CEST Mar 15 2023
Active Drain Active Applying Config Other unit wants me Active
17:51:42 CEST Mar 15 2023
Active Applying Config Active Config Applied Other unit wants me Active
17:51:42 CEST Mar 15 2023
Active Config Applied Active Other unit wants me Active
13:30:43 CEDT Sep 1 2023
Active Failed Interface check
This host:0
Other host:0
13:37:27 CEDT Sep 1 2023
Failed Standby Ready Interface check
This host:0
Other host:0
13:38:15 CEDT Sep 1 2023
Standby Ready Cold Standby Configuration mismatch
13:38:16 CEDT Sep 1 2023
Cold Standby Sync Config Configuration mismatch
13:39:00 CEDT Sep 1 2023
Sync Config Sync File System Configuration mismatch
13:39:00 CEDT Sep 1 2023
Sync File System Bulk Sync Configuration mismatch
13:39:15 CEDT Sep 1 2023
Bulk Sync Standby Ready Configuration mismatch
==========================================================================
Could someone explain the mismatch configuration to me at the end?
and what do the different lines dated September 1st mean?
The "failover lan unit primary" line is on the primary (standby)
And I would like to put it back in the correct order. Let the primary become active again, and the secondary, stand by.
I believe i must use the command “no failover active” on the active firewall , Correct?
Or "failover active" on the standby?
