I'm still figuring out the evpn/vxlan thing for our data center. We're using Apstra 5.1, my spine switches are a pair QFX5120-32Cs and I have three racks each with a pair of QFX5120-48Ys as leafs (leaves?). In my old data center, I'm used to having my ToR switches in VC config and have had zero problems with LACP to Windows servers in that configuration.
I have three Dell PowerEdge servers (two R550s and one R350) that I would like to have in LACP configuration, if only because that's what I'm familiar with. Each has two 10G SFP ports, populated with 10G Dell DAC cables. A 'show chassis hardware' on the leaf switches shows them as "SFP+-10G-SR".
I have been able to configure the LAG as "Static LAG (no LACP)" in Apstra and "Static Teaming, Dynamic Load balancing mode" in Windows server 2022, and the link is up. I'm only using one side of the lag, though, and it only fails over if one of the DAC cables is physically removed. If I only disable one of the links on the server side, the link just goes down. I'd rather have full LACP.
If I switch to "LACP" Active on Apstra and "LACP Dynamic" on Windows, I get "Faulted LACP negotiation" on the Windows side, and the Apstra dashboard shows the xe ports aren't in the lag. on the switch, a "show lacp interfaces" shows the participating ports, but the mux state is 'detached'.
I saw on a Dell website somewhere (and now I can't find the link) that Windows has to be periodic slow, so I wrote a configlet to put the lag in periodic slow if it saw a specific tag. When I looked in the generated config on the leaf, it showed periodic slow on the ae interface, but I still got the "faulted LACP negotiation" on the Windows side.
I'm at a loss. I've never had this kind of problems with LACP. I understand that evpn/vxlan is a whole other beast and that maybe I need to back to school on this tech, but I didn't think Apstra would be THIS hard.
Any suggestions? Any help? Has *anybody* gotten LACP to work with Windows in an Apstra environment?
Thanks!