Bug ID 705311: Separate ePVA offload timing configuration according to protocol

Last Modified: Nov 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Fixed In:
14.1.0

Opened: Feb 05, 2018
Severity: 2-Critical

Symptoms

BIG-IP supports ePVA offloading feature on two protocols: TCP and UDP. The timing when they are offloaded is under the same FastL4 profile option: pva-offload-state. The available timings are defined in alignment with the TCP 3-way handshake. UDP, then, mimics the definition of the TCP 3-way handshake on the first few packets on both direction traffic.

Impact

Separate the configuration of ePVA offload timing to TCP and UDP. The TCP offload timing uses the option 'tcp-pva-whento-offload' to replace the old option 'pva-offload-state', but still uses the 3-way handshake to determine the timing. The UDP ePVA offload timing is defined by packet counts. Options 'other-pva-clientpkts-threshold' and 'other-pva-serverpkts-threshold' is the user configurable threshold. Option 'other-pva-whento-offload' allows user to decide whether each side of the traffic is offloaded once the side passes the threshold or BIG-IP waits for both side of the traffic to pass the threshold and offload together. New option 'other-pva-offload-direction' allows user to set which direction of the traffic the user would like to allow offloading.

Conditions

On a ePVA supported platform. Some of the options will need UDP ePVA feature available.

Workaround

None.

Fix Information

ePVA offload timing configuration is now separate, according to protocol.

Behavior Change

Deprecate DB variables: pva.udpest.clientpkts.threshold, pva.udpest.serverpkts.threshold, pva.offload.uniflow. Deprecate LTM profile FastL4 option: pva-offload-state. Add LTM profile FastL4 options: tcp-pva-whento-offload, other-pva-whento-offload, other-pva-offload-direction, other-pva-clientpkts-threshold, other-pva-serverpkts-threshold