Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP TMOS
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
Fixed In:
13.0.0
Opened: Sep 09, 2015 Severity: 3-Major
Forwarded FastL4 profiles are not accelerated.
Forwarded FastL4 flows are not accelerated.
This occurs when any of the following conditions is met: -- Using a preserve-strict setting on a virtual server. -- Using the "snat" command in an iRule. -- Using CGNAT with few available endpoints.
None.
Flows for a FastL4 profile that are forwarded may now be accelerated. Observable behavior change would be that the tmctl 'snoop_cmp' stat will increase, as will accelerated flow counts, performance will be improved, and CPU utilization will decrease. For a forwarded flow, the system might see two accelerated flows instead of just one single forwarded flow. A few cases in which a flow would be forwarded include: using a preserve-strict setting on a virtual, using the "snat" command in an iRule, and using CGNAT with few available endpoints.
Flows for a FastL4 profile that are forwarded may now be accelerated. Observable behavior change is that the tmctl 'snoop_cmp' stat will increase as will accelerated flow counts, performance will be improved, and CPU utilization will decrease. For a forwarded flow, the system may see two accelerated flows instead of just a single forwarded flow. A few cases in which a flow might be forwarded include: -- Using a preserve-strict setting on a virtual server. -- Using the 'snat' command in an iRule. -- Using CGNAT with few available endpoints.t