Last Modified: Jun 23, 2025
Affected Product(s):
F5OS F5OS, F5OS-A
Known Affected Versions:
F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3
Fixed In:
F5OS-A 1.7.0
Opened: Apr 20, 2023 Severity: 3-Major
LACP Mode set to active or passive mode causes a LAG to participate in negotiation whereas a static LAG configuration does not participate in negotiation. Hence lacp-mode does not make sense for static LAG interfaces.
An LACPd daemon is running on R2000/R4000 platforms which is responsible for running LACP protocol; the tenant is not dependent on LACP mode configurations and hence there will not be any impact. This is more of a display issue where one might confuse displaying LACP mode as passive for a static LAG interface.
When a static LAG is created on a platform, and a tenant is launched with a VLAN to which the static LAG interface is associated.
There is no workaround for this behavior.
None