Forum Discussion
Issue in Failover of pool member
If cookie persistence is not there, then go with source based persistence with default Timeut value (300seconds). Please make sure your TCP profile timout and persistence timout has same values.
- Samit_jadhavFeb 19, 2019
Altostratus
But if the source based persistence is used then it may take 5 min to hit the client traffic on next available poolmember when the 1st pool member goes down and the requirement is clients traffic should switchover to next available pool member within 4 sec whenever the 1st pool member goes down...
- RaghavendraSY_7Feb 19, 2019
Cumulonimbus
If your requirement is failover traffic to pool member B only if pool member A goes down? If Yes to the question then you need to go with Ratio load balance method and no need to use persistence.
Ration method:
Pool A --100% Pool B --0%
Hope this helps.
- Samit_jadhavFeb 19, 2019
Altostratus
Thanks Raghvendra, but after setting lb method to ratio , will the Failover take place in 4 sec
anyways I'll set probe interval timings to 1 sec and probe timeout value to 4 sec , will this help me in achieving my target of Failover in 4 sec?
- RaghavendraSY_7Feb 19, 2019
Cumulonimbus
Yes. It should be immediately.
- Samit_jadhavFeb 19, 2019
Altostratus
Thanks Raghvendra.
- RaghavendraSY_7Feb 19, 2019
Cumulonimbus
np
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