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 configuration, if a L2VPN NLRI with route target 100:3 is received, it does not associate the received NLRI to the VPLS instance. Is it a bug in Juniper? In which scenario, we will need more than one route target ? instance-type vpls; interface fe-0/3/1.0; route-distinguisher 100:3; vrf-target { target:100:3; --> Both import and export import target:100:5; } protocols { vpls { site-range 10; site vplsSiteA { site-identifier 6; interface fe-0/3/1.0; } } } Regards, Monika _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp