On Mar 22, 2019, at 9:25 PM, Crist Clark wrote:
>
> Maybe you should be looking at DHCPv6 if you want those kinds of logs.
We did. ;-) However, Google seems quite set on not supporting it on Android:
https://issuetracker.google.com/issues/36949085
Maybe you should be looking at DHCPv6 if you want those kinds of logs.
On Fri, Mar 22, 2019 at 2:19 PM Jason Healy wrote:
>
> We're starting to play around more with IPv6, and one thing we're missing is
> a log of who has which address. In IPv4 we have DHCP and can check the logs,
> but we're
On Fri, 22 Mar 2019, Vincent Bernat wrote:
❦ 22 mars 2019 13:39 -04, Rob Foehl :
I've got a few really large layer 2 domains that I'm looking to start
breaking up and stitching back together with EVPN+VXLAN in the middle,
on the order of a few thousand VLANs apiece. Trying to plan around
any
We're starting to play around more with IPv6, and one thing we're missing is a
log of who has which address. In IPv4 we have DHCP and can check the logs, but
we're using SLAAC for v6 so that's not an option.
I set up a quick trunk interface with all our VLANs as members and started
sniffing.
Hi Alexandre,
Did it pass frames without C-tag in Junos versions < 18?
Kind regards,
Andrey
Alexandre Snarskii писал 2019-03-22 13:03:
Hi!
Looks like JunOS 18.something introduced an incompatibility of native
vlan handling in QinQ scenario between ELS (qfx, ex2300) and non-ELS
switches: when
❦ 22 mars 2019 13:39 -04, Rob Foehl :
> I've got a few really large layer 2 domains that I'm looking to start
> breaking up and stitching back together with EVPN+VXLAN in the middle,
> on the order of a few thousand VLANs apiece. Trying to plan around
> any likely limitations, but specifics
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
Hi!
Looks like JunOS 18.something introduced an incompatibility of native
vlan handling in QinQ scenario between ELS (qfx, ex2300) and non-ELS
switches: when ELS switch forwards untagged frame to QinQ, it now adds
two vlan tags (one specified as native for interface and S-vlan) instead
of
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
One more question just came to mind: what routing protocol do you use
for underlay, eBGP/iBGP/IGP? Design guides show examples with eBGP but
looks like for deployment that's not very big ISIS could do everything
needed. What are pros and cons for BGP vs IGP?
Kind regards,
Andrey
Andrey
Thank you Sebastian for sharing your very valuable experience.
Kind regards,
Andrey
Sebastian Wiesinger писал 2019-03-22 04:39:
* 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.
* 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
12 matches
Mail list logo
