I have a 5516x ASA running version 9.5(2)10. I noticed recently that one of my static routes is including a next hop that doesn't belong on that interface. We have a VPN tunnel off of the outside2 interface which has a next hop of xxx.xxx.xxx.17. That is correct but it is also showing a next hop of xxx.xxx.xxx.33, which is NOT the next hop for traffic going out the outside2 interface, but is rather the next hop for the outside interface. When I attempt to delete the IP route to xxx.xxx.xxx.33 from the outside2 interface I get an error message stating "%No matching route to delete". It doesn't seem to be causing any routing issues, but it does not belong there and I want to get rid of it. Does any one know if this may be a bug in software version 9.5(2)10? We just upgraded to that version recently and I never saw this incorrect route before. I'm thinking that if I shut down the outside2 interface then I may be able to remove the incorrect route, but that is not an ideal situation. Does anyone know how I can get rid of this route without shutting down the interface, or if shutting down the interface will even work?
Here is a sample of my configuration:
S xxx.xxx.xxx.0 255.255.255.0 [1/0] via xxx.xxx.xxx.33, outside2
[1/0] via xxx.xxx.xxx.17, outside2
S* 0.0.0.0 0.0.0.0 [1/0] via xxx.xxx.xxx.33, outside
route outside 0.0.0.0 0.0.0.0 xx.xxx.xxx.33 1 track 1
route outside2 0.0.0.0 0.0.0.0 xx.xxx.x.17 100
MPIUA-ASA(config)# no route outside2 xxx.xxx.xxx.xxx 255.255.255.0 xxx.xxx.xxx.33
ERROR: %No matching route to delete
