Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
ASA 5525X, Active/Active, Site to Site VPN - Failover fails
Hi
I have a new pair of 5525X ASA's operating in an Active/Active Multiple Context Mode and everything is working fine, in terms of network traffic flow and failover, however site to site VP...
HI
I have recently built a fresh PI 3.1 (due to issues with a 2.2 upgrade) and then re imported devices and maps.
Now, email alerts are not working and I cannot figure out how to make them work!!!...
> I have filled out the SMTP server details an...
HiI have created a System Call Handler in Unity, but when I try to forward calls on certain extensions, I get the Unity menu prompt (as though the dialled number is not registered against the Call Handler).
However, when I call the DN associated to t...
Hi
I have an issue with DHCP over a mobility group/anchor which I have set up at my site and a remote site, to allow our clients to roam.
I’ve tried I think everything but I cannot get the remote client (one of our laptops) to get a DHCP address in...
Hi I am trying to install a device pack on the CUCM Publisher but when I choose 'Software Upgrades', 'Install/Upgrade', it gets stuck on "Loading, Please Wait'. I've come away and gone back 12 hours later and it's the same! As such I am unable to i...
Sorry, I am bombarding you!!
OK, so now I have cleared (logout) the VPN on both the active and standby ASA's (within the context) and the VPN has now come up by itself and is incrementing (viewing on the standby ASA where the context is active)........
I am actually receiving the following log messages on the standby firewall, admin context:
720012 (VPN-Secondary) Failed to update IPSec failover runtime data on the standby unit
http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-n...
Thank you Marvin.
Apologies, I should have confirmed, IOS is 9.2(2)4
Strangely, no logging is appearing after failing over (so the context logging is not carried over, although you can ASDM to it)
Will have a look at setting up a capture...
