[c-nsp] Weird Traceroute Issue to Specific Destination

Heath Jones hj1980 at gmail.com
Tue Sep 21 16:28:40 EDT 2010


> I put a static route at our Internet edge - we redistribute static into OSPF
> so now this /32 destination is able to be seen in the routing table (other
> than the default originated route).

That really does suggest that the routing information is incorrect. I
mentioned previously about routing networks behind some customers dsl
links (can't remember the attribute - framed-route or something)..
This could explain the intermittent connectivity, combined with some
policy routing or vrf seperation would explain the traceroute results.

Others have suggested policy routing also. I'm thinking that you don't
have 1x routing table - are you using vrf's or doing some vlan
trickery?

Its either:
- The output previously for cef has led us astray.
- The routing for this customer isnt the same as what we were looking
at with the cef output.
- Bug (unlikely, rebooted already, fixed with static).

Either way I'm labbing this up to see if I can actually create a
similar problem..

> I pulled the static out and same problem re-occurs... any thoughts?
Head explodes now :)


More information about the cisco-nsp mailing list