Forum Discussion
CirrusRestore configuration to GTM Sync Group device
Your approach looks reasonable to me.
If it were me, I’d also include gtm_add in the rollback procedure.
Taking the UCS while the device is temporarily out of the GTM sync group is a good way to avoid any unintended sync during restore. Then, if rollback is needed, I’d restore the config on that device first and run gtm_add from the restored device toward the existing device that has the desired config / higher commit-id, so it pulls the GSLB config back in a controlled way.
So overall, I think your plan makes sense — I’d just add gtm_add as part of the backout steps as well.
https://my.f5.com/manage/s/article/K14044
CirrusIgnore the questions above - I have just found the following F5 article which explains what AMI_MJ was saying: Force sync config to a specific GTM / DNS device
Thanks all for the assistance. 😁
