[j-nsp] VPLS design - dual homed

[Luca Salvatore]

My topology is a bit different though... There is no 'service provider' cloud between my MX routers.
They are directly connected via dark fibre. Does the split horizon rule come into play here?

Luca


-----Original Message-----
From: chip [mailto:chip.gwyn at gmail.com] 
Sent: Tuesday, 30 October 2012 11:17 AM
To: Luca Salvatore
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] VPLS design - dual homed

In VPLS, loop avoidance is arranged by the following rule: A PE never forwards a frame received from a PE, to another PE. The use of a full mesh combined with split horizon forwarding guarantees a loop-free broadcast domain.

From: wikipedia
http://en.wikipedia.org/wiki/Virtual_Private_LAN_Service#Ethernet_emulation

So it's much like ibgp.

--chip

On Mon, Oct 29, 2012 at 7:19 PM, Luca Salvatore <Luca at ninefold.com> wrote:
> Hi Guys,
>
> I have a question regarding dual VPLS links.  My topology will look like this:
>
> MX1---------darkfibre----------MX2
>   |                             |
>   |                             |
> MX3---------darkfibre----------MX4
>
> So above you see that there are dual  links which will create a loop.
>
> How does VPLS handle these types of topologies?  Do I need to just use spanning tree and have one link in blocking?
> Or perhaps use MSTP and send some VLANs down one link and some down the other?
> I will be spanning around 1000 VLANs across these links. They are 10Gb links, so it seems a shame to have one in a blocking state.
>
> Any other recommendations?  Perhaps M-LAG?
> Thanks,
>
> Luca.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp



--
Just my $.02, your mileage may vary,  batteries not included, etc....