Bug ID 674595: Monitor timeout may increment by (interval+timeout) rather than (timeout)

Last Modified: Sep 14, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,

Opened: Jul 18, 2017

Severity: 3-Major


Monitors may reach "time-out-deadline" based on (interval+timeout) duration, rather than (timeout) duration, because the first probe may be sent anytime during the first timeout period. For example, an interval of 5 seconds with a timeout of 16 seconds may reach deadline at up to 21 seconds (interval+timeout). This may be noticeable for long intervals (e.g., interval of "hours"), and is different from in-TMM monitors which timeout based on (timeout) alone.


The monitor deadline will timeout at (interval+timeout), rather than (timeout) alone.


A monitor (other than in-TMM monitor) is configured with interval and timeout durations.


No workaround

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips