Thanks to all responders. To summarize request for further info: 1. We do *not* have any origin attributes contained in any inbound or outbound policy statements. We are filtering inbound from downstreams only by prefix. Outbound policy is a mix of as-path and prefix terms. In this case, first match would be on an as-path term.
2. We are receiving all advertisements from the downstream site, both origin-incomplete and origin-internal. 3. All routes are being advertised and received in IBGP ok. 4. After doing "show routes adv bgp" it does appear that we are announcing all prefixes including origin-incomplete. It's possible they are being rejected by our peers, although I'm pretty confident that most should be accepting them. Based on the fact that nobody has said "Yo dummy, JunOS never re-advertises prefixes with origin incomplete", I'm going to do more detailed checking on the looking glasses. > -----Original Message----- > From: Angel Bardarov [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 19, 2007 3:20 PM > To: Borchers, Mark M. > Cc: '[email protected]' > Subject: Re: [j-nsp] BGP Origin Issue > > > > > Borchers, Mark M. wrote: > > Thus, those nine appeared to us on an M20 as origin > > incomplete. None were advertised to other peers. > > > In that case the problematic routes are present in the > routing table of > your M20. Do you have export policies to you iBGP peers? Can you post > the output from "show route advertising-protocol bgp ..." > > Angel > NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
