Forum Discussion
Gbps_31870
Nov 28, 2011Nimbostratus
Persistence Issue
Hi All,
From the subject, I assumed it's a persistance issue, but let me brief my issue below in details.
I have two pools associated with one VS as following:
1- Pool1 (default pool)
2- Pool2 (called in one iRule)
I used the default persistance as Cookie_based persistance and the fallback based on src_addr
I have many iRules linked to this VS, with one of them redirecting to pool2 as following:
when HTTP_REQUEST {
switch -glob [HTTP::path] {
"/xyz1*" -
"/xyz2*" -
"/xyz3*" {pool Pool2}
}
}
For the above iRule it's working fine, but when any request hit the above iRule, and then any subsequent requests coming from the same client, it still persist to Pool2, where it should go to Pool1, eventhough the redirection at F5 is working fine (other iRules) but the selcted servers/pool is incorrect. Note that, this is only happening on subsequent requests where the first request hit the above iRule.
Any thoughts to fix this issue, plz feel free to ask me any additional info.
Thanks in advance Gangs ,,
BR,
2 Replies
Sort By
- Hi Gbps,
when CLIENT_ACCEPTED { Save the name of the VS default pool before this iRule changes it set default_pool [LB::server] } when HTTP_REQUEST { switch -glob [HTTP::path] { "/xyz1*" - "/xyz2*" - "/xyz3*" { pool Pool2 } default { pool $default_pool } } }
- Hi Aaron/All,
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