Bug ID 1492625: Tenant may misreport trunk status after multiple interfaces go down concurrently

Last Modified: Jul 02, 2025

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

Known Affected Versions:
F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.7.0

Opened: Jan 19, 2024

Severity: 3-Major

Symptoms

On r2000-series and r4000-series appliances, if multiple external links in a trunk go down simultaneously, the trunk status may be reported incorrectly inside a BIG-IP tenant. - The system reports the trunk as "up", but with no available bandwidth. - The underlying interfaces are reported as down. - HA group score may not be correctly calculated (since the BIG-IP tenant reports the as "up")

Impact

Incorrect reporting of trunk state within the tenant. HA group failover based on the trunk may not occur as expected.

Conditions

- r2000-series or r4000-series appliance - Multiple external links in a trunk - Multiple interfaces are disabled or unplugged simultaneously - Is observed both for static and LACP trunks This appears to be a relatively rare occurrence.

Workaround

To recover a system that has encountered this issue, either reboot the appliance, or restart the API service gateway container by logging into the system and running the command: docker restart system_api_svc_gateway

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips