I dont see these warnings in 17.3R3
It looks like you should configure it under routing-instance type
virtual-switch
https://www.juniper.net/documentation/en_US/junos/topics/concept/evpn-virtual-switch-overview.html
Nitzan
On Mon, Mar 25, 2019 at 12:01 PM Sebastian Wiesinger
wrote:
> * Rob Fo
* Rob Foehl [2019-03-22 18:40]:
> Huh, that's potentially bad... Can you elaborate on the config a bit more?
> Are you hitting a limit around ~16k bridge domains total?
Well we're just putting VLANs on LACP trunks like this:
ae0 {
mtu 9216;
esi {
00:00:00:00:00:0
* Richard McGovern via juniper-nsp [2019-03-22
17:53]:
> Sebastian, a couple of questions.
>
> 1. Your design is pure QFX5100 Leaf/Spine today? If yes, I assume
> you maybe only have 1 flat VXLAN network, that is you have no L3
> VXLAN, yes?
Exactly, the fabric is completely contained.
> 2.
On Fri, 22 Mar 2019, Sebastian Wiesinger wrote:
What did bother us was that you are limited (at least on QFX5100) in
the amount of "VLANs" (VNIs). We were testing with 30 client
full-trunk ports per leaf and with that amount you can only provision
around 500 VLANs before you get errors and basic
Sebastian, a couple of questions.
1. Your design is pure QFX5100 Leaf/Spine today? If yes, I assume you maybe
only have 1 flat VXLAN network, that is you have no L3 VXLAN, yes?
2. You stated you need 17.4 for improved LACP operation. Which exact 17.4 are
you using, and what version were you
* Andrey Kostin [2019-03-15 20:50]:
> I'm interested to hear about experience of running EVPN/VXLAN, particularly
> with QFX10k as L3 gateway and QFX5k as spine/leaves. As per docs, it should
> be immune to any single switch downtime, so might be a candidate to really
> redundant design.
All righ
6 matches
Mail list logo
