We've recently added our new BIG IP DNS i2600 servers to our current sync group in order to ensure all configurations are in-sync before cutting over to them as the primary NS.
What is the best way to go about updating the sync group so that the new DNS servers are primary for config sync? My thought is to update the sync group name on one of them and then re-run the gtm_add script on the second appliance, pointing it to the server with the new sync group name. This would separate the sync groups into old appliances and new appliances. If this works, would we need to run anything on the new primary?
I don't think there is an option a device to be primary for GTM sync as on which you make changes will update the others.
You can also check this article:
First I think better stop the synhronization as if you are doing an upgrade of an F5 GTM device, then change the sync group name and then do the rest as if the sync group names don't match the gtm_add will not work also because you have already done gtm_add maybe after you disable the synchronization and change the sync group name and again enable the synchronization there will be no need to run gtm_add as the device ssl certificates are already exchanged.
Can someone extra confirm this as I haven't done DNS splitting myself?
Thanks for the info! I was looking for something like the first link - which clearly outlines what needs to be done - but wasn't able to come up with anything. I think a removal of the legacy appliance from the sync group is the best path forward.