Greetings,
I have a "persistent" virtual-access interface that is associated wrongfully with a /28 network that already has a virtual-access interface associated with it. What's more, it seems that the buggy virtual-access is a member of the vtemplate recycle queue, so it gets used and has configuration added which messes up routing, since the /28 at that point has 2 virtual-access interfaces with 2 tunnel destinations:
atm-host-router#sh ip route 10.99.37.80
Routing entry for 10.99.37.80/28
Known via "static", distance 1, metric 0
Redistributing via eigrp 100
Advertised by eigrp 100 metric 1024 10 255 10 1500 route-map routes-ou
Routing Descriptor Blocks:
* directly connected, via Virtual-Access12 <---CORRECT ONE
Route metric is 0, traffic share count is 1
Route tag 2886781519
directly connected, via Virtual-Access80 <-- WRONG, MEMBER OF RECYCLE QUEUE
Route metric is 0, traffic share count is 1
Clearing ip route for 10.99.37.80/28, clearing crypto sessions, and clearing the virtual-access itself don't work..Any ideas?