Bug ID 426477: Maximum GTM monitor timeout is actually 65535, not 86400

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(all modules)

Known Affected Versions:
10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Jul 29, 2013
Severity: 4-Minor
Related Article:
K14716

Symptoms

If you specify a timeout greater than 65535 on a GTM monitor, it does not set the value as expected. Before saving the configuration, tmsh reports the value that was entered, but the wideip.conf file contains a value of 0. After the configuration is saved, the value returns to the default of 120 in both tmsh and wideip.conf.

Impact

If the timeout is set to greater than 65535 it does not work as expected. Instead the monitor timeout defaults to 120 seconds.

Conditions

Creating/Modifying a GTM monitor with a timeout greater than 65535.

Workaround

Specify a timeout less than 65536.

Fix Information

Setting the timeout now works as expected.

Behavior Change