Hi Stephen, Are the routes you try to export to your iBGP peers, also learned from iBGP peers?
Because prefixes received from iBGP speakers are only advertised to eBGP speakers. If this is what you want you can consider a fully meshed network, use route-reflectors or confederations. Gr, Richard > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stephen Fulton > Sent: Sunday, July 01, 2007 6:42 AM > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] Problem exporting BGP routes. > > Hi all, > > I'm having an issue exporting routes to iBGP peers. I am > able to import routes from my iBGP peers fine, but not export. > > I have tried several variations on policy statements which > effect exactly what is being exported, but without the > intended result (exporting a full table). Below I have > included one that is now being used. The result is the > exporting of directly connected interface routes. > > -- Start -- > > policy-statement iBGP-ADVERTISE-FULL-ROUTING-TABLE { > term 1 { > from protocol ospf; > then reject; > } > term 2 { > then accept; > } > } > > -- End -- > > I am filtering routes learned from OSPF to simplify the > trouble shooting process. If I remove term 1, the OSPF > routes are re-advertised to my iBGP peers. I have tried adding: > > -- Start -- > > [...] > term 1.5 { > from protocol ospf; > then accept > } > > -- End -- > > Without success. > > Any ideas? > > -- Stephen. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
