Bug ID 1049737: F5OS: Some members in LACP trunks may not stand up

Last Modified: Aug 25, 2022

Bug Tracker

Affected Product:  See more info
F5OS F5OS, Velos(all modules)

Known Affected Versions:
1.3.0, 1.3.1, 1.3.2

Fixed In:
1.5.0

Opened: Sep 24, 2021
Severity: 3-Major

Symptoms

When configuring an LACP trunk (aggregate link), if the trunk has interfaces on multiple blades, some members of the trunk may not join the trunk, and the peer layer-2 switch may produce warnings stating that the LACP members are not all on the same remote device. In addition, after enabling debug logging for the lacpd daemon, messages will be seen from both blades that indicate the value of "actor_oper_key". These values should be the same for all the ports within the same LACP trunk, but in this situation, the debug output may show different values for ports on different blades.

Impact

One or more ports in the LACP trunk (aggregate link) will not be able to join the trunk.

Conditions

- VELOS chassis - LACP trunk with member interfaces on multiple blades

Workaround

Restart the lacpd container on each blade in the affected partition. For example, if the partition consists of slots 1 and 2, log in as root to the controller, and run the following command: for i in 1 2; do ssh blade-$i docker restart lacpd ; done

Fix Information

None

Behavior Change