Bug ID 1291305: LACP Mode is passive for a static trunk in tenants running r2800/r4800 platforms

Last Modified: Aug 01, 2024

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

Fixed In:
F5OS-A 1.7.0

Opened: Apr 20, 2023

Severity: 3-Major

Symptoms

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.

Impact

An LACPd daemon is running on R2800/R4800 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.

Conditions

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.

Workaround

There is no workaround for this behavior.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips