Help! We have an ASA (7.2_4) that won't let go of a route it established.
Here's what happened: We did some testing this weekend to try and route a branch office's VOIP traffic over a dedicated T1 instead of the L2L VPN connection.
We concluded our testing, and reverted the changes, but now the ASA keeps trying to throw some specific UDP traffic over the T1 instead of back onto the VPN as it had before.
When I try to do a packet tracer, traffic to other IP addresses in that same target network are fine, but traffic to the specific IP address that's causing the problem throws an error of "Drop-reason: (no-adjacency) No valid adjacency"
As best I can tell, the ASA is still trying to route the traffic for that destination IP over the T1, and is unhappy because it can't figure out the next-hop MAC address at layer 2.
Might the timeouts have something to do with it? When I do a 'show conn' I do see that connection to the destination IP via the T1, even after clearing conn and rebooting ASA.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...