Forum Discussion
iRule cookie persistence and pool redirect
- May 10, 2024
Tests were done in the production LTM instead, by creating a temporary VIP with same pool members. A few users were able to test via the temporary VIP, and everything was working as expected. Yet, it wasn't working on the production VIP.
I end-up creating a PoolC containing nodeA1 ONLY for /beta/ URI ONLY. That way /beta/ URI would never reach nodeA2 when nodeA1 is down.
If PoolC/nodeA1 is UP, then PoolC will be used. Otherwise, it will hit the 2nd condition, redirecting /beta/ to PoolB. Problem solved.
Tests were done in the production LTM instead, by creating a temporary VIP with same pool members. A few users were able to test via the temporary VIP, and everything was working as expected. Yet, it wasn't working on the production VIP.
I end-up creating a PoolC containing nodeA1 ONLY for /beta/ URI ONLY. That way /beta/ URI would never reach nodeA2 when nodeA1 is down.
If PoolC/nodeA1 is UP, then PoolC will be used. Otherwise, it will hit the 2nd condition, redirecting /beta/ to PoolB. Problem solved.
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