02-21-2022 04:12 AM
Hi
I have 2 frp 4140 running ASA code.
We run multi-context with ~80 context and active/standby failover.
We shut down the standby unit and moved it to another DC.
During startup of the moved ASA we see some strange issues.
My Active ASA goes directly from Active to Cold standby due to Failover state check.
Does anyone know why this happens ?
Is there a list of scenarios, where i can see what triggers state from active to cold standby ?
Regards Henrik
02-21-2022 04:48 AM
Failover checks are outlined in the following:
With that many contexts and interfaces, a lot of things could influence failover. I would recommend opening a TAC case to have an engineer look at in directly with you.
02-21-2022 05:07 AM
Hi Marvin
I did look at that document, but it doesn´t mention anything about "cold standby".
I want to know what state that can get a ASA to go from "Active" to "Cold standby".
Regards Henrik
02-21-2022 12:08 PM
show failover history <-
any of ASA, and share output here we can after that know why the ASA go to cold standby.
check if the status is due to mismatch config?
02-21-2022 11:36 PM
Hi
hereby the "show failover history":
23:10:07 CET Feb 2 2022
Active Cold Standby Failover state check
23:10:09 CET Feb 2 2022
Cold Standby Sync Config Failover state check
23:37:54 CET Feb 2 2022
Sync Config Sync File System Failover state check
23:37:54 CET Feb 2 2022
Sync File System Bulk Sync Failover state check
23:38:06 CET Feb 2 2022
Bulk Sync Standby Ready Failover state check
02-22-2022 11:12 AM
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