I have a hub-and-spoke topology with a 3725 has my hub and a couple 1811s as the spokes.
Spokes are setup to use ezvpn to connect to the hub. Everything is working ok from each spoke to the hub (and equipment hanging off the hub).
The strange behaviour is in spoke-hub-spoke encrypted traffic. If I reset the tunnel spoke1-hub, then spoke2 can ping equiment behing spoke1. If I keep pinging, traffic stays up - however if I stop the ping something in the hub seems to time out after 60sec or so. Then pings from spoke2 to spoke1 no longer work. Traceroute reveals that the hub is trying to route my traffic using the default route rather than the VPN injected static route for spoke1.
This is only an issue for traffic going between spoke2-hub-spoke1. Everything else continues to work (spoke1-hub, spoke2-hub, hub-spoke1, hub-spoke2).
Any ideas on what is timing out my routes and more importantly how I can correct it?
Threat Response Basics
What is Threat Response and how can it help my organization?
What is the cost of Threat Response?
What are the deployment options for Threat Response?
Is Threat Response available outside of the United States?
Gartner has once again named Cisco a Leader in the Magic Quadrant for Network Firewalls. This distinction recognizes Cisco's ingenuity in redefining the firewall as the basis for an integrated security platform.
Find out how Cisco stands out from the comp...
Hi experts,I would like any suggestions on this topology. We are is the middle of replacing our old ASA5520 with the new FirePower. Our current firewall terminate our IPsec tunnels and the GRE is terminated on the first inside router's loopback on the sec...
Hi All, A customer wants to authenticate Anyconnect VPN users from an ASA using the client installed certificate and then with AD. i.e. Is this a corporate device?Would we recommend authenticating the cert on the ASA then passing the AD check to ISE ...
Hello Team, we are getting alert in FMC stating policy deployment failed, we are running on 6.2.0 version and not sure which version is stable version to re mediate this issue, in one event i have seen restart will resolve this issue but is it perman...