Bug ID 1137669: Potential mis-forwarding of packets caused by stale internal hardware acceleration configuration

Last Modified: May 29, 2024

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

Fixed In:
F5OS-C 1.6.0, F5OS-C 1.5.1, F5OS-A 1.4.0, F5OS-A 1.3.0

Opened: Aug 18, 2022

Severity: 3-Major

Symptoms

Because configuration entries added to the internal ePVA hardware acceleration tables may become stuck, packets arriving from front panel ports may be handled by stale entries resulting in unexpected forwarding behavior. The stale entries may also prevent TMM from offloading new connections to ePVA.

Impact

Packets may be forwarded to unexpected destinations, and/or new connections are unable to be offloaded to ePVA.

Conditions

The most likely cause for entries to become stuck is either a reboot of tenant or restart of TMM while it has active connections offloaded to ePVA without also rebooting the entire appliance.

Workaround

Don't reboot or restart TMM without also rebooting the entire appliance.

Fix Information

Packets are behaving as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips