Bug ID 1596625: BE2 GCI interface training failures during runtime results in failure to process networking traffic

Last Modified: Nov 02, 2024

Affected Product(s):
F5OS F5OS, F5OS-A(all modules)

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

Fixed In:
F5OS-A 1.8.0

Opened: Jun 14, 2024

Severity: 2-Critical

Symptoms

On particular rSeries appliances, one or more symptoms could occur during normal operation: -- High availability stops working -- Inbound traffic stops -- Platform.log contains 'DM Tx Action ring hung' This is similar to the symptoms in https://cdn.f5.com/product/bugtracker/ID1580489.html, except that this can be triggered during system operation.

Impact

The system stops delivering traffic from front-panel ports to the host, although egress traffic may continue to work. If a LACP LAG is configured, ports will be unable to join the LAG.

Conditions

-- rSeries r5000, r10000, or r12000-series appliance This issue does not affect r2000 or r4000-series appliances.

Workaround

There is no workaround for this issue. If an appliance has already locked up, rebooting it might restore network connectivity. If your system is running F5OS-A version 1.5.x, F5OS-A-1.5.2-29198.R5R10.EHF-4.iso is an Engineering Hot Fix (EHF) that contains a software fix, and is available at https://my.f5.com/manage/s/downloads?productFamily=F5OS&productLine=F5OS_Appliance_Software&version=1.5.2&container=1.5.2-EHF You can also upgrade to F5OS-A 1.8.0.

Fix Information

New FPGA bitstreams stabilize the interface between the ATSE and BE2 chip.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips