Forum Discussion
Fast failover in GTM.
To detect failed pool members faster, build a custom monitor and set the interval and timeout values very low to detect failures more quickly. Setting an interval of 5 seconds and a timeout of 16 will allow three failed health checks before a pool member is marked down which should give you some robustness against network congestion, but will ensure unreachable pool members will be removed in under 20 seconds.
The numbers can be tailored to whatever works best in your environment. My numbers were arbitrarily chosen.
- Cory_50405Jan 29, 2014
Noctilucent
Looking at your config again, your two GTM pool members are LTMs I take it based on the bigip monitor? The health checking from your LTMs to the destination servers may be the best place to modify your monitors in this case.
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