On Tue, 2009-03-17 at 10:46 -0700, Harry Reynolds wrote: > 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. Configuring peer-as for an iBGP group does not break anything. I think you agree with my suspicion that it is a cluster list loop or similar sanity check failure.
Eric's last post including some config is confusing, I think because both the "working" and "non-working" routers are called edge01, or more likely the paste is in error. I suggest pastebin. -- Jeff S Wheeler <j...@inconcepts.biz> +1-212-981-0607 Sr Network Operator / Innovative Network Concepts _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
