Bug ID 998433: HW/ePVA offload state is not migrated on upgrade

Last Modified: Apr 24, 2024

Affected Product(s):
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3

Opened: Mar 01, 2021

Severity: 3-Major

Symptoms

The FastL4 profile option pva-offload-state was deprecated in v14.1.0: https://cdn.f5.com/product/bugtracker/ID705311.html On upgrade from BIG-IP version 14.0.0 or earlier to version 14.1.0 or later, the pva-offload-state is not migrated properly to the new FastL4 options, if set to a non-default value. The new FastL4 profile options are tcp-pva-whento-offload and other-pva-whento-offload.

Impact

Hardware-accelerated flows (ePVA) are accelerated based on the new default values instead of the non-default value configured prior to upgrade. This can cause flows to be accelerated based on different constraints. In the case where the pva-offload-state was set to established (EST), it can cause flows to offload prematurely.

Conditions

A non-default setting of pva-offload-state in the FastL4 profile.

Workaround

Set the new FastL4 profile options to values that are equivalent to the non-default pva-offload-state setting. If pva-offload-state is set to establish (EST), then the following should be set for equivalent flow offloading behavior: tcp-pva-whento-offload = establish other-pva-whento-offload = after-packets-both-direction

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips