dhcp for all zones is coming (really soon), patches have been submitted on the pve-devel mailing list.
https://lore.proxmox.com/pve-devel/c51def21-662f-4384-aba3-4e5ca9a7f190@proxmox.com/
Thanks for the info !
Personnally, I'm using mellanox connect-x since multiple year with vxlan && bgp-evpn, and I never had problem with vxlan offloading
I don't trust intel && broadcom anymore, too much bugs in their drivers
It's mainly when you have a lot of (small) packets per second incoming. (If I remember, qemu is around 2millions pps with 1 core)
try an iperf3 with 64bytes packets (to simulate a syn flood for example)
cluster network is for osd->osd replication.
osd->monitor && osd->client is done on public network.
They are differents hearbeats, osd hearbeat between osd (on clusternetwork)
hearbeat from monitor-> osd (on public network)...
your pg number seem quite low, it could impact write performance with pg_lock.
try to set pg target ratio to 1.0 in your ceph pool
Also, verify in your bios that your server is set to max performance profile. (you want cpu always at their max frequency to lower latency)
the exit-node on proxmox is only to generate config with advertisement of the default type-5 route on proxmox node you want to use as exit-node.
as here, you want to use arista as exit-node, you don't need to define exit node
you can use "redistribute connected" for example
https://datacenteroverlords.com/2025/05/24/what-is-an-evpn-type-5-route-for-evpn-vxlan/
https://arista.my.site.com/AristaCommunity/s/article/Validated-Configuration-Layer-3-Leaf-Spine-with-VXLAN-EVPN-Symmetric-IRB