Forum Discussion
Persistence configuration - when node down all new connections permanently in the backup node, even if the previous one goes up again.
You could also configure the the pool to use priority group activation and the monitor on the pool to have the Manual Resume feature enabled. This would send all traffic to your designated primary pool member, and if that pool member goes down, the Manual Resume feature will prevent it from re-activating even if the service on that member comes back up.
The downside of this technique is that you will have to manually reactivate the first pool member, but it gives you pretty solid control over which pool member is receiving traffic.
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