Forum Discussion
Samit_jadhav_33
Nimbostratus
Feb 19, 2019Issue 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 ...
RaghavendraSY_7
Cumulonimbus
Feb 19, 2019If 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.
RaghavendraSY_7
Cumulonimbus
Feb 19, 2019If 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.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects