VPN traffic interruption on ASA5540 Running 8.3 code
Intermittently, L2L VPNs traversing a particular interface on my ASA 5540 get torn down and are not able to complete phase 1. These tunnels run for weeks with the exact config in the ASA, and then randomly stop passing traffic. Importantly, this affects only VPN related traffic. Additionally, we run SSL VPN through the same interface on the ASA and that stops allowing incoming connections as well. I also have L2L VPN tunnels built up to other interfaces on the ASA and they are not affected.
My ASAs are running in active/standby and I can force a failover to whatever unit is acting as the standby, and the issue is immediately cleared with no other intervention. Recently, this issue presented and I noticed that my dynamic ARP table had multiple erroneous interfaces bound to the MAC address of the interface that has issues with VPN traffic. Instead of performing a failover event, I cleared the dynamic arp entries and the issue was immediately resolved. I can only assume that the HA failover process also forces an arp cache clear, which explains why that resolved the issue previously.
I have had the same hardware running the same code for quite some time and this issue only recently cropped up. There were no config changes made to the ASA for some time prior to the first manifestation of the issue.
I have debug logging enabled and am send this info to a syslog server. I captured output from some of these events but haven’t been able to make heads or tails of it.
HIDoes anyone know if there is an easier way than the belowQ. I check connection events for IOC's when requested and sometimes i have to check many url's which i am presently doing one url at a time and is very time consuming, is there a way to check mult...
Cisco Identity Services Engine (ISE) gives you intelligent Integrated protection through intent-based policy and compliance solution. ISE supports external MDM vendor integration to help the customers to look for compliance of a dev...
This video provides the steps to configure the Cisco Threat Response (CTR) and ESA Integration.
This is live on the portal:https://video.cisco.com/video/6159336218001
And on YouTube:https://www.youtube.com/watch?v=UCKIdx5rdFg
I need to migrate from C170 to C190 and have already match to the same Firmware Version. I have a question. Is there any method that can export and import the configuration file instead of form cluster ?