Bug ID 1070357: GSLB monitors fail to work if Max Synchronous Monitor Requests Number is hit.

Last Modified: Nov 29, 2022

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:
17.0.0,,, 14.1.5, 13.1.5

Opened: Dec 27, 2021
Severity: 3-Major


After adding several new pools with monitors attached, newly found pools might fail, or existing pools might fail afterwards.


-- Inconsistent monitor status across BIG-IP DNS systems in a single sync group. -- Because some monitor instances don't have monitor traffic, if the instance fails, the BIG-IP DNS systems may not be aware of the failure.


GSLB Monitors fail to work if Max Synchronous Monitor Requests number is hit.


To mitigate the issue, run the following command to increase the value of Max Synchronous Monitor Requests: tmsh modify gtm global-settings metrics max-synchronous-monitor-requests <value - default is 20>

Fix Information


Behavior Change