Bug ID 598024: FastL4 profile with immediate idle timeout is not honored for ePVA offloaded flows

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1

Opened: Jun 08, 2016
Severity: 4-Minor

Symptoms

On ePVA platforms, if fastL4 profile is configured with immediate idle timeout and the flow was offloaded at embryonic, the server still acts as the flow has not timeout, and continues to send packets to client.

Impact

Some flows that should have timed-out and should no longer exist is still alive.

Conditions

Users have flows that passes through virtual IP with a "idle-timeout immediate" setting may not have the expected behaviors.

Workaround

Set "pva-acceleration" to "none" for the FastL4 profile.

Fix Information

Now all flows goes through the virtual IP configured with a fastL4 profile and has idle-timeout to immediate will timeout immediate as expected.

Behavior Change