[j-nsp] policy question

[Pedro Roque Marques]

Alexander,
I'm assuming that you are talking about a BGP export policy here.

Export policies cannot have different behaviour from different members
of a group... the definition of a BGP group is a set of peers w/ a
consistent export policy.

As such "to neighbor [...]" clauses are automatically ignored for BGP export
policies.

What you want to do here is define an ibgp group for regional-routers
and other for non regional... then each group can have a different
policy.

regards,
  Pedro.


Alexander Koch writes:

> Folks, I have a quick question, all about BGP.

> Imagine some fully- meshed iBGP group, and a certain region where
> you want to keep prefixes local. That iBGP group has a common policy
> outbound to basically put local /30 in iBGP with no-export, etc.

> The prefixes that are supposed to stay local are tagedd with a
> community, and now I thought that something like this would even
> work:

> --> (from the iBGP policy applied to that group) term keep-in-italy
> { from { community keep-local; policy ( ! regional-routers );
>     }
>     then reject;
> }
> <--

> --> policy regional-routers...  term region { to neighbor [ (lots of
> iBGP neighbors in that region ]; then accept;
> }
> then reject; <--

> That policy should evaluate the regional-routers policy and my dream
> is that this effectively rejects the set prefixes to the specified
> BGP neighbors only.

> Do I understand correctly that I basically need two terms for this
> to really work, one allowing and one not?

> Alexander

> _______________________________________________ juniper-nsp mailing
> list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp