Bug ID 898377: Modifying idle timeout in fastl4 profile does not work as expected for VPN server side initiated traffic

Last Modified: Apr 17, 2024

Affected Product(s):
BIG-IP APM(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

Opened: Apr 13, 2020

Severity: 3-Major

Symptoms

Connections are closed after 300 seconds, even if the configured value is greater than or less than 300 seconds.

Impact

An idle timeout of 300 seconds occurs for server initiated traffic regardless of setting.

Conditions

This is encountered with the FastL4 profile idle timeout setting.

Workaround

1. mount -o remount,rw /usr 2. vi /usr/lib/tmm/tmm_base.tcl for example to set idle timeout 89876: profile bigproto _bigproto { tcp_server_time_wait_timeout 0 idle_timeout 89876 <<<< Added this field to the profile } 3. bigstart restart tmm

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips