06-29-2017 06:36 AM - edited 03-12-2019 02:38 AM
Hi,
The failover link between our active-standby ASA installation broke. The active remained active and the standby remained standby initially. After 90 minutes the standby ASA reloaded. There was no crash file generated, no logs stating a reason for the reload.
When the standby unit returned to service it could not detect the active ASA, assumed the active role and voilá, split brain.
Can anyone tell me if a reload is expected behaviour for an active-standby installation with a broken failover link?
Regards,
P Walsh
Solved! Go to Solution.
07-06-2017 01:27 AM
This is the expected behaviour after a reboot with broken failover link. I recommend you to set a standby IP address on at least one interface, that way the ASA can use the "normal" network link as a backup failover link, in case the failover cable has a fault.
See table 7.2 for details:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/ha_failover.html#81491
07-06-2017 01:27 AM
This is the expected behaviour after a reboot with broken failover link. I recommend you to set a standby IP address on at least one interface, that way the ASA can use the "normal" network link as a backup failover link, in case the failover cable has a fault.
See table 7.2 for details:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/ha_failover.html#81491
07-06-2017 03:17 AM
Thank you for that information. It verifies that with the failover link unavailable, both units are expected to be active after an unplanned reload.
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