I have two ASA5520 devices running version 8.2(2)16. They are in active/standby mode. This issue is not happening all the time but the devices are failing over and I have worked with Cisco TAC on this but was not able to uncover the issue. Under the "sho failover history" it shows reason of "HELLO not heard from mate". The Cisco tech had me upgrade IOS on both units and change out the cables on the management ports but no luck. I have sent the crash logs to the tech also but still no luck on find why this is happing sometime and when I say sometimes it may be once to twice a week that it happens. Has anyone seen this happen to them and have a case number that they worked on this with a tech or notes on how they uncovered why this is happening?
Thank you for the reply. The devices are not crashing in the sense of them going down or stopping communicating from what I can see. They will both be up and running fine and then will just failover and in the history the message “HELLO not heard from mate” will be the reason. Then a few days will go bye and they will failover again. After reading you message I now think that the tech was looking in the wrong place for the issue. He was always looking at the crash logs but the devices where not crashing. Not sure where to look now but any ideas would be a big help.
If there was no reboot (up time in device will show it) then the crash files are irrelevant.
There could be reasons that we lost HELLOs from mate, like network/switch issues connecting them, too much traffic on the failover interface, collision etc, or maybe high cpu on the ASAs so that they can't process the HELLOs. So, these might be worth of investigation. If there is no crash you need to focus on why HELLOs are lost. Fover debugs, failover interface captures can help.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :