Re: [j-nsp] Route target configuration for L2VPN route instance

Monika, With vrf-target You and-up with only one RT for ingrass and egress. Stephane has right. But You can try with vrf-import/vrf-export instead. You will need to write regular policy-statement and communities under policy-option, and reference them in vrf-import/export. This way You should be

Re: [j-nsp] Route target configuration for L2VPN route instance

Hi Monica, I believe the more specific configuration always wins, so the import in your case is always target:100:5. Rdgs, Stephane. - >But juniper allows configuring more than one route targets (See the >example below). But with the below configuration, if a L2VPN NLR

[j-nsp] Route target configuration for L2VPN route instance

RFC 4761, Section 3.1.2: As it has been assumed that VPLSs are fully meshed, a single Route Target RT suffices for a given VPLS V, and in effect that RT is the identifier for VPLS V. But juniper allows configuring more than one route targets (See the example below). But with the below config