Forum Discussion
GTM: avoiding flapping DNS answers with RTT method
- Apr 23, 2014
The only solution I could see in your situation is to break your single pool into three pools, and either stick with RTT and enable persistence at the wide IP, or switch to topology. Either one should get you some more consistency.
You can apply topology based load balancing at the wide IP level to select a pool. You can then apply RTT load balancing at the pool level to select a member. So they can be used in conjunction depending on your setup.
If your pools are built according to data center, then topology could send users from a certain country/state/etc. to a certain pool. The pool could then use RTT to send you to the lowest latency pool member.
In your example, I don't see a way for GTM to accomplish what you wish to do.
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