Bug ID 2025949: Configuring more than one mgmt aggregation interface may cause an aggregated management port to stop working

Last Modified: Oct 19, 2025

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

Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2

Opened: Aug 14, 2025

Severity: 3-Major

Symptoms

It is a documented restriction that only one user-defined aggregation interface is allowed to be configured in the System Controller ConfD configuration - the aggregation interface required to support management port aggregation. All subsequent user defined aggregation interfaces added to the System Controller ConfD configuration will be ignored by switchd. The management port aggregation may continue to function even after this configuration is performed since the switch trunk hardware is already programmed. However, after any event which requires reprogramming of the trunk hardware (ie. loss of trunk member or a system controller reboot), requests by LACP to update the trunk will be ignored by switchd and management connectivity will appear unreliable or completely non-existent.

Impact

You may experience unreliable or complete loss of chassis, partition and tenant management connectivity.

Conditions

Configuration of an additional System Controller aggregation interface followed by some event which requires switch hardware to be reprogrammed. Example: User upgrades the System Controller which causes the controllers to reboot.

Workaround

- Delete all but one of the user-defined aggregation interfaces and LACP interfaces of the same name from the System Controller ConfD configuration. - Make sure that SC management ports 1/mgmt0 and 2/mgmt0 ethernet aggregation-id are configured with the name of the aggregation interface that remains. - Reboot both system controllers.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips