[j-nsp] Interconnecting spines in spine & leaf networks [ was Re: Opinions on fusion provider edge ]

[Giuliano C. Medalha]

We are testing right now in our lab the new qfx5120

We are only waiting the official software release ...

The box is here already

The specs only shows L2circuit ... but we are waiting to see flexible ethernet encapsutation ( no vpls we already know ) to use vlan and mpls at the same interface.

But the main ideia is to use it with evpn/vxlan configuration and try qinq in vtep

After that we can post the results here

Att

Giuliano C. Medalha
WZTECH NETWORKS
+55 (17) 98112-5394
giuliano at wztech.com.br

________________________________
From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> on behalf of Aaron1 <aaron1 at gvtc.com>
Sent: Friday, November 16, 2018 13:14
To: adamv0025 at netconsultings.com
Cc: rmcgovern at juniper.net; Juniper List
Subject: Re: [j-nsp] Interconnecting spines in spine & leaf networks [ was Re: Opinions on fusion provider edge ]

Geez, sounds horrible , thanks Adam

We are buying QFX-5120’s for our new DC build. How good is the MPLS services capability of the QFX-5120?

Aaron

On Nov 16, 2018, at 5:12 AM, <adamv0025 at netconsultings.com> <adamv0025 at netconsultings.com> wrote:

>> Of Aaron1
>> Sent: Thursday, November 15, 2018 4:23 PM
>>
>> Well, I’m a data center rookie, so I appreciate your patience
>>
>> I do understand that layer 2 emulation is needed between data centers, if I
>> do it with traditional mechanisms like VPLS or l2circuit martini, I’m just afraid
>> if I make too many connections between spine and leaves that I might create
>> a loop
>>
>> However, I’m beginning to think that EVPN may take care of all that stuff,
>> again, still learning some of the stuff that data centers due
>>
>>
> Hey Aaron,
>
> My advice would be if you're building a new DC build it as part of your MPLS network (yes no boundaries).
>
> Rant//
> The whole networking industry got it very wrong with the VXLAN technology, that was one of the industry's biggest blunders.
> The VXLAN project of DC folks is a good example of short sighted goals and desire to reinvent the wheel (SP folks had VPLS around for years when VXLAN came to be).
> SP folks then came up with EVPN as a replacement for VPLS and DC folks then shoehorned it on top of VXLAN.
> Then micro-segmentation buzzword came along and DC folks quickly realized that there's no field in the VXLAN header to indicate common access group nor the ability to stack VXLAN headers on top of each other (or some tried with custom VXLAN spin offs) so DC folks came up with a brilliant idea -let's maintain access lists! -like it's 90's again. As an SP guy I'm just shaking my head thinking did these guys ever heard of L2-VPNs which were around since inception of MPLS? (so yes not telling people about mac addresses they should not be talking to is better than telling everyone and then maintaining ACLs) in SP sector we learned that in 90s.
> Oh and then there's the Traffic-Engineering requirement to route mice flows around elephant flows in the DC, not mentioning the ability to seamlessly steer traffic flows right from VMs then across DC and MPLS core which is impossible with VXLAN islands in form of DCs hanging off of MPLS core.
> Rant\\
>
>
>
> adam
>
> netconsultings.com
> ::carrier-class solutions for the telecommunications industry::
>

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

WZTECH is registered trademark of WZTECH NETWORKS.
Copyright © 2018 WZTECH NETWORKS. All Rights Reserved.

IMPORTANTE:
As informações deste e-mail e o conteúdo dos eventuais documentos anexos são confidenciais e para conhecimento exclusivo do destinatário. Se o leitor desta mensagem não for o seu destinatário, fica desde já notificado de que não poderá divulgar, distribuir ou, sob qualquer forma, dar conhecimento a terceiros das informações e do conteúdo dos documentos anexos. Neste caso, favor comunicar imediatamente o remetente, respondendo este e-mail ou telefonando ao mesmo, e em seguida apague-o.

CONFIDENTIALITY NOTICE:
The information transmitted in this email message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies.

WZTECH is registered trademark of WZTECH NETWORKS.
Copyright © 2018 WZTECH NETWORKS. All Rights Reserved.

IMPORTANTE:
As informações deste e-mail e o conteúdo dos eventuais documentos anexos são confidenciais e para conhecimento exclusivo do destinatário. Se o leitor desta mensagem não for o seu destinatário, fica desde já notificado de que não poderá divulgar, distribuir ou, sob qualquer forma, dar conhecimento a terceiros das informações e do conteúdo dos documentos anexos. Neste caso, favor comunicar imediatamente o remetente, respondendo este e-mail ou telefonando ao mesmo, e em seguida apague-o.

CONFIDENTIALITY NOTICE:
The information transmitted in this email message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies.