[j-nsp] Practical VPLS examples (SRX and J series)

[Chris Kawchuk]

In Juniper's BGP-based VPLS, you do not need to create pseudowires in-between the VPLS instances. As long as you have one "master" LSP (usuallyan RSVP one) in-between two PEs, BGP will then (by detecting which VPLS instance is announced from which device), automatically build an "inner tunnel" between the PEs to echange the VPLS traffic.

In order to have this work automatically, we need to reserve a series of 'inner labels' (effectively) which can be used to differentiate sites and VPLS instances. (so when PE#1 sends traffic to PE#2, the latter devvice knows which VPLS domain it should go into).

Contrast this with LDP-based VPLS, which requires manually configuring each neighbour in the VPLS domain by hand.

- Chris.



On 2011-11-12, at 7:01 AM, Jack Bates wrote:

> 
> 
> On 11/11/2011 11:42 AM, Mike Williams wrote:
>> So. VPLS. Point-to-multiple-point. Virtual LAN. Brilliant!
>> I haven't yet found any documentation that I can actually understand though.
>> "Note: The site range value must be greater than the largest site identifier."
>> is especially confusing. "Range" is one number, bigger than any other, hmm.
> 
> I believe this is because of the BGP auto-detection of sites. My guess is the logic actually runs up the numbers to range, so defining it to something reasonable speeds up the setup process.
> 
> I'm still waiting on power for my lab to test vpls w/ BGP signalling, as it might screw up my production network and I'd like to see if I can shift to l2 signaling without dropping the peers. :)
> 
> 
> Jack
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp