Last Modified: Apr 20, 2026
Affected Product(s):
BIG-IP DNS
Known Affected Versions:
17.1.3, 17.1.3.1, 17.5.1.3, 17.5.1.4, 17.5.1.5, 21.0.0, 21.0.0.1
Opened: Mar 27, 2026 Severity: 3-Major
After adding/deleting unrelated virtual server on the LTM device object, disabled virtual server on the same LTM device object change its status from "available/disabled" (black circle icon on GUI) to "offline/disabled" (black rhombus icon on GUI). "no reply from big3d: timed out" error is thrown, despite there is no problem in iquery communication between DNS system and LTM system. bigipdns.local alert gtmd[21078]: 011ae0f2:1: Monitor instance /Common/bigip 10.1.1.192:80 UP --> DOWN from /Common/bigipdns (no reply from big3d: timed out) bigipdns.local alert gtmd[21078]: 011a6006:1: SNMP_TRAP: virtual server vs2 (ip:port=10.1.1.192:80) (Server /Common/bigipltm) state change green --> red ( Monitor /Common/bigip : no reply from big3d: timed out: disabled directly)
Disabled virtual server status change from "available/disabled" (black circle icon on GUI) to "offline/disabled" (black rhombus icon on GUI). Once this problem occurs on disabled virtual servers, even after re-enabling those affected virtual servers on LTM device, the affected virtual servers stayed at "offline/enabled" (red rhombus icon on GUI) status.
All of the following conditions need to be met. -- DNS system manages remote LTM device and its virtual servers. -- DNS system retrieves LTM virtual server monitor status from big3d running on remote LTM device via iquery. -- There are disabled virtual servers on LTM device object. -- "Monitor Disabled Object" parameter under "DNS >> Settings : GSLB : General" is unchecked (default). -- Changes to virtual server (i.e., adding / deleting) on LTM device object is performed on DNS system.
To rescue already affected virtual servers, on the DNS system, temporarily assign any monitor object to the affected virtual servers and revert it back to none. # tmsh modify gtm server bigipltm virtual-servers modify { vs1 { monitor gateway_icmp } vs2 { monitor gateway_icmp } } # tmsh modify gtm server bigipltm virtual-servers modify { vs1 { monitor none } vs2 { monitor none } } # tmsh save /sys config gtm-only Or alternatively, restarting gtmd on DNS system can also rescue affected virtual servers. # tmsh restart sys service gtmd To prevent issues from recurring in the future, you can change "gtm global-settings general monitor-disabled-objects" parameter to "yes". # tmsh modify /gtm global-settings general monitor-disabled-objects yes # tmsh save /sys config gtm-only
None