Bug ID 1469333: VELOS management LAG may bridge traffic between management interfaces during LACP negotiation

Last Modified: Jun 19, 2025

Affected Product(s):
F5OS F5OS-C, Velos(all modules)

Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.8.0

Fixed In:
F5OS-C 1.8.1

Opened: Dec 26, 2023

Severity: 3-Major

Symptoms

When the management interfaces of VELOS system controllers are configured in a LACP LAG, the VELOS system may incorrectly forward some ethernet frames ingressing one management interface out the other management interface. This behavior occurs during the period between when an interface links up and when the system completes LACP negotiation and adds the interface to the LAG. This can result in management switches incorrectly learning non-VELOS MAC addresses as being present on the VELOS management LAG interface.

Impact

VELOS management interfaces incorrectly forward non-VELOS frames from one management interface out the other, causing upstream switches to learn non-VELOS MAC addresses as being present on the VELOS management LAG interface.

Conditions

- VELOS system - Management interfaces configured in LACP LAG

Workaround

Configure the upstream switch to be an LACP lag first, then configure the VELOS system MGMT interfaces to use an LACP lag.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips