Bug ID 760615: Virtual Server discovery may not work after a GTM device is removed from the sync group

Last Modified: Jun 06, 2024

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

Known Affected Versions:
12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,

Opened: Mar 06, 2019

Severity: 3-Major


LTM configuration does not auto-discover GTM-configured virtual servers.


Virtual servers are not discovered or added automatically.


-- GTM is deprovisioned on one or more GTM sync group members, or the sync group is reconfigured on one or more members. -- Those devices remain present in the GTM configuration as 'gtm server' objects. -- iQuery is connected to those members.


You can use either of the following workarounds: -- Manually add the desired GTM server virtual servers. -- Delete the 'gtm server' objects that represent the devices that are no longer part of the GTM sync group. These can then be recreated if the devices are operating as LTM-configured devices. Note that deleting a gtm server object will also remove any of its virtual servers from gtm pools.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips