Last Modified: May 22, 2023
BIG-IP DNS, GTM
Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 18.104.22.168, 22.214.171.124, 16.1.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 17.0.0, 18.104.22.168, 22.214.171.124, 17.1.0, 126.96.36.199
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 192.168.1.1:*"). -- 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.