Jonathan Schulz

I have two separate servers running v6.9.2. I just played with the ProCurve and was able to get the LACP ports set to passive. I set Unraid to 802.3ad and watched it change back to active-passive. The logs show the "no 802.3ad response" message, but the switch is showing a successful LACP connection. I finally found Ubiquiti commands to do the same, and it also appears to be functional. The uncertainty on the Unraid side worries me a bit, as it never really indicates that 802.3ad is correctly configured. I guess I'll let it run for a bit and see what happens.

I just confirmed that I have the same issue when setting up link aggregation using an HP ProCurve switch instead of Ubiquiti. I'm not sure where to go from here, as it appears to be an Unraid issue.

I played around with the link while reading the logs and I am getting "Warning: No 802.3ad response from the link partner for any adapters in the bond" when trying to set this up. It appears that my Ubiquiti switch is not doing what it is supposed to do, regardless of whether I configure it through command line or web interface.

Does Unraid perform a check when enabling 802.3ad? I would have expected that even if the link aggregation was not performing, it would still leave the 802.3ad setting turned on rather than switching back to active-passive.

I just ran across this same issue. I have a NIC with dual 10Gb ports and I want to set up LACP to a Ubiquity Edgeswitch 16XG. I have the two ports on the switch configured as a LAG. The Unraid side won't allow me to use 802.3ad. If I set the interface in Unraid to 802.3ad and hit apply, it goes back to active-passive. Does anyone know how to fix this? I've tried with the ports up and down, I rebooted, and tried a few other random things. It won't let me set any other modes but active-passive. I have two separate installs of Unraid v6.9.2 doing the same thing.