Forum Discussion

Samit_jadhav_33's avatar
Samit_jadhav_33
Icon for Nimbostratus rankNimbostratus
Feb 19, 2019

Issue in Failover of pool member

Scenario   2 pool members A & B behind ltm. Load balancing method .. Round robin No persistence Monitoring Probe used tcp_8443 Interval set to 2 sec Timeout 7 sec   Issue... Client experiences ...
application delivery
LTM
RaghavendraSY's avatar
RaghavendraSY
Icon for Altostratus rankAltostratus
Feb 19, 2019

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_jadhav's avatar
Samit_jadhav
Icon for Altostratus rankAltostratus
Feb 19, 2019

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...