[c-nsp] Dual Homed Site with L2 Backup

[Arie Vayner]

One approach I can see to make it work consistently regardless what path it
takes is to use the overlay at all times, even when the primary path is up.

Basically you just make the layer 2 link routed (i.e. terminate it with
layer 3 ports on both ends), and run the VXLAN one hop before (or anywhere
it makes sense).

This way you just run a vxlan extension over a layer 3 redundant path.

On Sun, Dec 23, 2018, 02:48 Richard Clayton <sledge121 at gmail.com wrote:

> Hi Arie
>
> I did encounter the MTU requirement and configured the lab to allow for
> it.  VXLAN may be the future but this topology isn't really what it was
> intended for, due to the loop it creates (same with OTV).  I was still able
> to ceate a working design for both protocols regardless.
>
> Would interesting to see how others would meet the requirement with this
> particular set of constraints.
>
> Thanks
> Rick
>
> gamma.co.uk
>
>
>
> On Sat, 22 Dec 2018, 20:29 Arie Vayner <arievayner at gmail.com wrote:
>
>> Vxlan is the future... 😉
>> Be very careful with the mtu implications.
>>
>> Tnx, Arie
>>
>> On Sat, Dec 22, 2018, 03:25 Richard Clayton <sledge121 at gmail.com wrote:
>>
>>> Hi Guys
>>>
>>> Scenario
>>>
>>> Customer has dual homed geographically seperated site into mpls wan.
>>> They
>>> also have a single layer 2 circuit running between the two.  The
>>> requirement is to backup the layer 2 over the wan circuits.  The wan
>>> hardware at both sites is cisco 4k ios xe.
>>>
>>> I'm interested to know how you guys would achieve this.  I've had the
>>> luxury of 4 days in the lab testing VXLAN, OTV and L2TPV3 xconnect
>>> between
>>> the two 4k routers, also did JDSU throughout testing over the tunnel, was
>>> quite interesting.
>>> _______________________________________________
>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>