Bug ID 1409493: PVA dedicated mode connections are not re-accelerated after a failover.

Last Modified: Oct 04, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 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, 15.1.10.5, 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, 16.1.5, 16.1.5.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4

Opened: Dec 01, 2023

Severity: 3-Major

Symptoms

After a failover, not all PVA-accelerated flows using the dedicated mode may be accelerated on the new peer.

Impact

After a failover, some flows may not be accelerated. This would cause higher-than-expected latency for those flows.

Conditions

HA mirroring on a FastL4 VIP with PVA-acceleration set to "dedicated. sys turboflex profile-config set to "turboflex-low-latency" This type of configuration is commonly used for hardware-optimized FIX low-latency electronic trading traffic.

Workaround

Delete the affected flows and then cause them to be re-created. Disable HA mirroring.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips