On Sun Jul 01, 2007, Stephen Fulton wrote:
> 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:
If you remove term 1 then you will have an implicit "from" then because
term 2 has only a "then" action. The implicit "from" is from any
active route, therefore that include connected routes.
> -- 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
pgpIwKEfJjs8R.pgp
Description: PGP signature
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
