I have been complaining here and elsewhere that some PIXen I mangage are emitting log messages like this:
Sep 10 06:15:10 pixinquestion %PIX-6-110001: No route to 10.2.167.2 from192.168.1.100
even though, when inspected, they do in fact have a route for the address in question. It turns out the real reason for these messages is that the *next hop* router does not have an appropriate route. So if I have on my PIX, say, the config line:
route vpnside 10.2.160.0 255.255.248.0 10.2.164.100 2
and the router at 10.2.164.100 does not know how to reach 10.2.167.2, the PIX will emit a message "No route to 10.2.167.2", which only seems to imply, wrongly, that it's the PIX itself which is lacking a route.
Hope that helps someone.