Hello,
The switch my Proxmox node is hooked into only supports "static LAG," with no LACP/dynamic options. My Proxmox node has 2x2.5GbE ethernet ports.
I didn't realize the switch had this limitation until after I bought it; otherwise it's a great multigig switch that does everything else I need. I have no plans/budget to replace it right now, or in the near future.
Questions:
Thanks!
The switch my Proxmox node is hooked into only supports "static LAG," with no LACP/dynamic options. My Proxmox node has 2x2.5GbE ethernet ports.
I didn't realize the switch had this limitation until after I bought it; otherwise it's a great multigig switch that does everything else I need. I have no plans/budget to replace it right now, or in the near future.
Questions:
- What options do I have with "static LAG?" That is, what can it actually do? On my other switch with LACP/dynamic LAG, I bonded a couple of 2.5GbE ports on a NAS to get 5GbE of total bandwidth (with 2x2.5Gb full duplex lanes). I'm guessing I can't necessarily do the exact same thing on a switch that's static-only.
- The closest static option to LACP appears to be "ALB" load balancing. Is this supported under Proxmox? I know i can make the underlying Debian install do it, but from the Wiki it looks like Proxmox might only work with "active backup" bonding. I'm still unclear on this.
- Depending on the answer to Question 1 and 2, would I be better off without Link Aggregation?If so, what's the best way to make use of the second NIC?
- I suppose the easiest answer would be to use it as a second gateway (?) for higher traffic/higher priority VMs (e.g. to dedicate to VMs and containers I use via remote desktop and remoting into VPN).
- But, I've never done this before, so I'm curious what y'all would suggest.
Thanks!
Last edited:
