Bug ID 475074: Very large GTM monitoring configs can fail monitors.

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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.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, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Opened: Aug 08, 2014
Severity: 3-Major

Symptoms

When monitoring a very large number of virtuals, GTM can mark objects down. The log shows: alert gtmd[xxxx]: xxxxxxxx:x: Monitor instance /Common/bigip xx.xx.xx.xx:80 UP --> DOWN from /Common/xxxx (no reply from big3d: timed out)

Impact

Load balancing can be disrupted because the status of the virtual server is being marked unavailable.

Conditions

GTM monitors a very large number of virtuals with maximum synchronous monitor requests set very high.

Workaround

Set your gtm.global-settings.metrics.max-synchronous-monitor-requests to a value which does not overwhelm the big3d on the other box.

Fix Information

None

Behavior Change