08-20-2008 08:49 AM - edited 03-11-2019 06:33 AM
My ASA continues to report route lookup issues for a number of networks on the outside interface, but if I attempt to ping these address, I can get to them, has anyone seen this?
08-20-2008 10:36 AM
those sorts of errors shouldn't be taken so literally. the pix/asa will give route lookup errors for other non-route-related issues, such as NAT misconfigurations.
08-20-2008 11:15 AM
Do you have a default route pointing towards the outside? Also what is the number of the syslog message?
This syslog does not always mean a route lookup failure, it can be fired for other reasons also.
Regards
Farrukh
08-20-2008 11:24 AM
Thanks guys for responding so quickly.
We do have a default route on the ASA. We receive this alert (from our mars box) atleast one an hour.
How can I go about troubleshooting this issue, what can I look for if it is NAT related?
Ideas?
08-20-2008 11:31 AM
Is the address it is reporting typically the source address of a remote access vpn user?
08-20-2008 11:45 AM
Yes they are. What does that mean?
08-20-2008 11:54 AM
Don't know, haha...I know it happens to me as well. Don't think it's anything to be concerned about.
08-20-2008 11:54 AM
LOL really?
08-20-2008 12:03 PM
Yes, I created a drop rule on my Mars because I was tired of seeing them and they are obviously not causing any issues with vpn clients.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: