Forum Discussion
GTM Sycnchronization group between Different physcial boxes
I hope you all well and hope you can assit with my question below
is it possible to have 4 F5 GTM in one synchronization group when two of them are hardware=1600 and the other two are the 4000 (all of them run the same code / HF)
is it a valid design
or are we better of breaking it in two sync groups one with the two 1600s and another sync group with the two 4000.
3 Replies
- Kevin_K_51432Historic F5 Account
Greetings, It appears identical hardware isn't a requirement:
K13734: BIG-IP DNS synchronization group requirements
https://support.f5.com/csp/article/K13734
Kevin
- ZeeSid_307015
Nimbostratus
Many thanks for the url
from a design perspective are we better of breaking it in two sync groups one with the two 1600s and another sync group with the two 4000.
IS it an exceptable design with two 1600 and two 4000 in the same sync group is any one using a simillar setup in prod or a simillar one.
Kind Regards, Zee
- martin_58353
Cirrus
Yes, it is possible to have different HW version (including VE platforms) for the same GTM sync group. All members must be running the same SW version and other (see https://support.f5.com/csp/article/K13734). For different SW version is possible run gtm_add script for 'manual sync' but it is not very clear solution.
You can also combine two 1600 and two 4000 platforms. It depends on expected load. For example 1600 has approximately up to 200.000 req per second (RPS), 4000 up to 400,000RPS. for more details see data sheet: https://www.f5.com/pdf/products/big-ip-dns-datasheet.pdf
it always depends on design. maybe better solution (depends on your situation) is reserve two 1600 for BIG-IP DNS, and more powerful 4000 for LTM. it's up to you.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com