Bug ID 1580489: BE2 GCI interface training issue results in failure to process networking traffic

Last Modified: Oct 23, 2024

Affected Product(s):
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: Apr 20, 2024

Severity: 2-Critical

Symptoms

Some particular rSeries systems fail to process networking traffic due to the BE2 GCI interfaces not training properly, resulting in an FPGA datapath lockup. One potential indication of this is the DMA agent detecting a DM Tx Action ring hang, which can be observed in velos.log / platform.log: dma-agent[13]: priority="Alert" version=1.0 msgid=0x4201000000000130 msg="Health monitor detected DM Tx Action ring hung." ATSE=0 DM=0 OQS=3

Impact

The system stops delivering traffic from front-panel ports to the host, although egress traffic may continue to work. If an 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

None, and F5 continues tracking the BE2 issue via ID1596625.

Fix Information

During system startup, FPGA manager now ensures that the BE2 GCI interfaces are brought up and trained properly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips