Bug ID 1273017: LACPD restarts when changing aggregation lag-type through configuration utility webUI

Last Modified: Feb 08, 2024

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-A 1.0.0, F5OS-A 1.0.1, F5OS-A 1.1.0, F5OS-A 1.1.1, F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2, F5OS-A 1.4.0, F5OS-C 1.2.1, F5OS-C 1.2.2, F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1

Fixed In:
F5OS-A 1.7.0, F5OS-A 1.5.0

Opened: Mar 17, 2023

Severity: 3-Major

Symptoms

The Link Aggregation Control Protocol Daemon (LACPD) will restart. An LACP aggregation's interface can be permanently down, restricting traffic from passing on that interface.

Impact

One or more physical interfaces associated with an LACP aggregation can be erroneously marked down indefinitely, causing either degraded performance, or complete traffic failure. Performance degradation may not occur, but the LACPD process will always restart.

Conditions

-An aggregation interface's lag-type is set to static through configuration utility.

Workaround

- Toggle any affected interface to disable and then back to enable. - Toggle any affected aggregation interface to static and then back to LACP. - Reboot the system.

Fix Information

LACPD will not restart when an aggregation is configured to static through the configuration utility. Few warnings can be logged when this operation occurs. These warnings can be ignored if seen while changing an aggregation's lag-type through configuration utility.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips