Forum Discussion
Multiple strategies for maintenance page
- Aug 01, 2019
Your irule is just missing the LB::reselect command. Pool on its own is not enough as the pool has already been selected and tried in the LB_FAILED event.
Some of my configuration requires the same; if the primary pool is down it is necessary to send the traffic to a standby server in a different pool. I do it without a lot of checks in the irule, using standard config instead.
The pool is configured to do a reselect to a different member if a x number of the other members are down.
Then the irule only includes the LB failed event:
when LB_FAILED { LB::reselect pool web-noname_standby_pool persist none }
: indeed, that was the issue. Thanks a lot !
: i was just referring to standard pool status, I should probably have said "status tracking". The loss of the last member of a pool triggers an explicit message "No members available for pool xyz" in logs, whereas just switching to the lowest priority group doesn't.
: is quite simpler 🙂
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