Forum Discussion
daboochmeister
Jul 27, 2017Cirrus
Existing connections with Priority Group Activation - minimizing client impact, timeouts, etc.
Hi, we're using PGA for an active/standby config, with an either/or relationship between the groups (activation set to < 1 server).
We're finding that when the higher priority group is reactivat...
jaikumar_f5
Jul 29, 2017MVP
Did you check this article.
Beginning in BIG-IP 11.0.0, newly-available pool members in a priority group are not counted toward the minimum-up member requirement for a pool until after the Slow Ramp Time for the pool member has expired.
This means, your pool member A which had the highest priority would not be considered here. Slow ramp is enabled by default with 10 sec. Try disabling the slow ramp setting.
Slow ramp is a feature where the newly available member should not be bombarded with traffic immediately but instead till the slow ramp time is reached.
Also persistence do come into picture - Refer Article.
When a virtual server references a priority group pool, persistence may cause traffic to persist to a node in a lower priority group even after a higher priority group is reactivated.
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