Bug ID 715596: Connections are reset when TCP timestamp mirroring is enabled

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IP All(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, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 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

Fixed In:
14.1.0

Opened: Apr 18, 2018

Severity: 3-Major

Symptoms

When the bigdb variable tm.tcptimestampmirror is enabled, connections might get reset.

Impact

Some mirrored connections are reset.

Conditions

-- The tm.tcptimestampmirror variable is enabled (it is disabled by default). -- Connection mirroring enabled on a virtual server.

Workaround

None.

Fix Information

Fixed an issue with connection reset when tm.tcptimestampmirror is enabled. In addition, the default value of tm.tcptimestampmirror has been changed to enabled.

Behavior Change

Prior to version 14.1.0, tm.tcptimestampmirror had a default value of 'disabled'. The default value of tm.tcptimestampmirror is now 'enabled.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips