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

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
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.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, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3

Opened: Jul 18, 2017
Severity: 3-Major

Symptoms

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.

Impact

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

Conditions

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

Workaround

No workaround

Fix Information

None

Behavior Change