Bug ID 783289: PEM actions not applied in VE bigTCP.

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0, 14.1.3.1, 13.1.3.5

Opened: May 18, 2019

Severity: 3-Major

Symptoms

If PEM virtual server is configured using bigTCP, the return traffic from the server may not return to the same TMM. PEM policies do not get applied.

Impact

PEM policies do not get applied.

Conditions

-- BIG-IP Virtual Edition. -- bigTCP is configured (FastL4 with PEM/GPA hudfilters). -- Virtual server uses Source-NAT.

Workaround

To work around this, do the following: -- Configure bigTCP virtual server not to use source-NAT. -- Configure destination-IP for hashing in server-vlan (the external VLAN that has the virtual server).

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips