[j-nsp] Communities on l2vpn instances

Krasimir Avramski krasi at smartcom.bg
Tue Sep 27 08:16:01 EDT 2016


You can follow the vpls example (l2vpn/l3vpn/l2circuit traffic mapping is
the same):

install-nexthop <strict> lsp lsp-name: Use the "strict" option to enable
strict mode, which checks to see if any of the LSP next hops specified in
the policy are up. If none of the specified LSP next hops are up, the
policy installs the discard next hop.

Best Regards,

On 26 September 2016 at 16:43, Luis Balbinot <luis at luisbalbinot.com> wrote:

> Hi.
> It's possible to set communities at the "protocol l2vpn" level in a
> l2vpn routing-instance at three different places:
> set interface xxx community yyy
> set site xxx community yyy
> set site xxx interface yyy community zzz
> But these don't seem to change anything. Documentation on these
> commands is pretty much inexistent. Does anyone know how/if they work?
> My idea is to set communities to aggregate l2vpn instances and control
> which groups take different LSPs. All communities set from a VRF
> export policy are only sent on the BGP sessions and are not installed
> at the local l2vpn tables. Is there a way to set multiple communities
> locally on a l2vpn routing-instance?
> Luis
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

More information about the juniper-nsp mailing list