Forum Discussion
Client request sent to Single server
- Oct 24, 2018
Are you only dealing with 2 servers (one active and one passive)? if so, you don't need to use a persistence profile. I'd also consider enabling manual resume on your primary server so that it doesn't come back online automatically after it's gone down in the pool. That way you can manage it back in without having a split brain situation.
Are you only dealing with 2 servers (one active and one passive)? if so, you don't need to use a persistence profile. I'd also consider enabling manual resume on your primary server so that it doesn't come back online automatically after it's gone down in the pool. That way you can manage it back in without having a split brain situation.
You can create priority groups, assign one priority group to each server (e.g. the primary server has a priority group of 100 and the standby server has a priority of 50) and set priority activation to be less than 1 available members. Traffic should only be sent to the higher priority group (with your primary server in it) until it fails and the second priority group takes over.
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