[j-nsp] IP Fabric EVPN/VXLAN

[Guillermo Fernando Cotone]

Hi William,

We run into a similar issue by running a mix of pre/post 17.4R1 in our
network. Support for mac-mobility extended community was added in that
release.
Basically, VTEPs running < 17.4 will simply ignore the attached
mac-mobility community (if present) and when a MAC is migrated behind them,
the rt-2 UPDATE will be sent without it. On the other hand, remote VTEPs
(>17.4) will ignore the update due to mac-mobility absence(seq. number of
the old leaf will be higher).

The solution was upgrading everything to > 17.4R1.

Best,
Guillermo

On Mon, May 20, 2019 at 5:52 AM Jackson, William <
william.jackson at gibtele.com> wrote:

> Hi
>
> Just want to throw this one out there:
>
> What are other peoples experiences with the IP Fabric EVPN/VXLAN scenario.
>
> I have leaf and spine on qfx5100 with 17.3R3-S3 and MX edge gateways using
> :
>
> I have gone through in order
> *18.3R1-S1
>         Disk Space consumption bug
> *18.3R1-S3
>         EVPN BGP update BUG
> *18.3R2 *********
>         <<<BOOOOOOOM>>>
> *18.2R2-S3
>         Memory Leak BUG
>         MAC addresses don’t age out BUG
>
> For me this has been a nightmare, bug after bug after bug.
> When the IT guys migrate a VM, it breaks.
> I have had JTAC case after JTAC case.
>
> regards
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>