[afnog] vpls with LDP juniper

[Mark Tinka]

On Thursday, January 23, 2014 03:29:40 PM ibtisam jamal 
wrote:

> Managed to bring it up....

Good for you.

> 2.vpls -id has to be the same on both routers

Yes, the VPLS ID should be the same on all PE routers. This 
is how the router knows that traffic associated with a 
specific routing instance belongs to that routing instance, 
and not another.

> 3.No-tunnel-services was missing .

Yes, by default, VPLS on Juniper routers requires the 
presence of a Tunnel PIC. If you don't have one, "no-tunnel-
services" is required for the router to create "lsi-" 
interfaces encapsulate/decapsulate VPLS traffic from/to a 
routing instance. Otherwise, VPLS 
encapsulation/decapsulation takes place on a Tunnel PIC.

If you are running an MX Trio or the older MX DPC line 
cards, they come with an in-built Tunnel PIC. You just need 
to enable it under the [chassis] hierarchy.

> end config looks like this
> 
>  show configuration routing-instances X200_VPLS
> description "X2000 VPLS Instance";
> instance-type vpls;
> interface DDDDDDD.148;
> route-distinguisher 10.87.0.2:222;
> vrf-target target:64514:222;

For LDP-based VPLS, it should work without setting an RD or 
RT, as those are typically used for BGP-based VPLS.

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://afnog.org/pipermail/afnog/attachments/20140123/ae709262/attachment.sig>