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

Last Modified: May 07, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4

Opened: Mar 06, 2019
Severity: 3-Major

Symptoms

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

Impact

Virtual servers are not discovered or added automatically.

Conditions

-- 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.

Workaround

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.

Fix Information

None

Behavior Change