Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP DNS
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
Fixed In:
13.0.0, 12.1.2 HF1
Opened: Dec 16, 2016 Severity: 3-Major Related Article:
K10608314
Some GTM topology records may silently not be synchronized to other devices in the sync group.
Other devices in the GTM sync group will have an incomplete set of topology records, so the returned DNS answers may differ from the expected values.
One known case occurs when topology records have overlapping subnet specifiers (such as 1.0.0.0/8 and 1.0.0.0/9). It is possible that there are other conditions that might cause this issue.
After updating topology records, run the following command to force a push of all GTM objects: run cm config-sync force-full-load-push to-group gtm. This can be performed from tmshell or bash. tmshell: --------- (/Common)(tmos)# run cm config-sync force-full-load-push to-group gtm Force a full load sync? (y/n)y bash: --------- tmsh run cm config-sync force-load-push to-group gtm Note: This command executes and returns to bash with no feedback. To determine the outcome, you can check /var/log/gtm for 'success'.
Some GTM topology records may have silently not been synchronized to other devices in the sync group. This is now resolved; all topology objects will be synchronized to all expected devices.