Forum Discussion
Miguel_Santos
Nimbostratus
Oct 18, 2013Persistence configuration - when node down all new connections permanently in the backup node, even if the previous one goes up again.
Hi,
I have the need to implement the following solution as follows:
The traffic can be balanced only for a member of the pool;
If the member becomes Down the traffic must pass to another p...
Sam_Richman_263
Oct 18, 2013Historic F5 Account
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.
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