09-28-2024 10:43 PM
I have ASA with Active/Standby configuration. I can see the primary is active and the secondary is standby ready. also, the configuration is replicated.
When I try the command "no failover active" to make the active work as standby, in order to go with the upgrade steps. It does not work as expected. I can see the SSH session terminated. But when I connect to the session again I can see there is no changes from the active/standby wise. The active ASA remains active and the standby stays standby.
09-28-2024 11:14 PM
There is issue with failover link
Do you connect failover link back to back or via SW?
MHM
09-28-2024 11:27 PM
Directly connected.
09-28-2024 11:48 PM
Share
Show failover
Show failover state
Before run command abd after for both unit
MHM
09-28-2024 11:53 PM
Sorry, it is connected over the network.
Should I collect the same outputs?
09-29-2024 12:01 AM
So it not direct?
İf yes
Share output of above and also share
Show interface IP brief
MHM
09-29-2024 03:23 AM
- Before the command:
-After applying the command:
09-29-2024 01:50 AM
Before the command:
09-29-2024 02:57 AM
May be worth post what ASA code running, some failover outputs.
check my blog some testing's - if all ok.
10-02-2024 02:20 AM
Based on the output you shared it seems to work as expected?
- Before the command:
show failover
Failover On
Failover unit Primary
Failover LAN Interface: Failover GigabitEthernet1/8 (up)
Reconnect timeout 0:00:00
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 3 seconds, holdtime 15 seconds
Interface Policy 1
Monitored Interfaces 1 of 160 maximum
MAC Address Move Notification Interval not set
Version: Ours 9.8(2)20, Mate 9.8(2)20
Serial Number: Ours JAD1948072L, Mate JAD2003056A
Last Failover at: 10:30:00 AST Sep 29 2024
This host: Primary - Active
-After applying the command:
sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: Failover GigabitEthernet1/8 (up)
Reconnect timeout 0:00:00
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 3 seconds, holdtime 15 seconds
Interface Policy 1
Monitored Interfaces 1 of 160 maximum
MAC Address Move Notification Interval not set
Version: Ours 9.8(2)20, Mate 9.8(2)20
Serial Number: Ours JAD2003056A, Mate JAD1948072L
Last Failover at: 10:59:23 AST Sep 29 2024
This host: Secondary - Active
After you applied the "no failover active" command, the output shows that the local active firewall is actually the secondary firewall which has also a different serial number.
One command can be handy with ASA failover is "prompt hostname priority state". If you apply this command, you can then see the hostname and the failover state on CLI.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide