> -----Original Message----- > From: Harry Reynolds [mailto:ha...@juniper.net] > Sent: Tuesday, March 17, 2009 1:46 PM > To: Eric Van Tol; juniper-nsp > Subject: RE: [j-nsp] Missing BGP Routes > > Normally an as path loop or other sanity check results in this state. > From the config below does not seem this is the case. Perhaps add > keep-all, restart/soft clear session, and then display hidden. Perhaps > something will jump out. > > Does tracing show any errors when the routes are processed? Unreachable > next hop normally is just hidden so does not seem the case here. Should > not matter, but I normally doe not specify peer-as for an int group. > Again should not break things but worth trying w/o.
I tried setting up tracing, and bouncing one of the routes so that it withdraws and readvertises, but nothing shows up in the trace file on edge01 that relate that route. I saw plenty of other updates, but nothing for 172.16.236.144/28. I would also imagine that if it was a cluster ID problem (I'm using a hierarchical RR scheme), that the routes would be dropped on the two other routers as well (core01 and core02). Maybe I'm mistaken, though. -evt _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp