Bug ID 1108237: Incorrect 'No reply from big3d: timed out' result for certain destinations monitored by GTM.

Last Modified: Dec 07, 2023

Affected Product(s):
BIG-IP DNS, GTM(all modules)

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 17.0.0,,, 17.1.0,,,

Fixed In:
17.1.1, 16.1.4

Opened: May 20, 2022

Severity: 3-Major


It is possible for monitor probes to a certain destination to be owned by no GTM device in the sync-group. As a result, no monitoring of the destination will be performed, and the monitored object will be incorrectly marked down with reason "no reply from big3d: timed out".


Monitored GTM objects may have an incorrect status.


-- GTM sync-group with multiple GTM devices (including a sync-group that contains only a single GTM server with more than one GTM device in it). -- Monitors specifying an explicit destination to connect to (e.g. with the property "destination*"). -- The destination of a monitored object (e.g. the IP address of the gtm server) is different from the destination explicitly defined in a monitor assigned to the object. -- The two mismatching destination values are assigned to different GTM devices in the sync-group for monitoring.



Fix Information

All monitor probes are not correctly assigned to a GTM device.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips