Forum Discussion
ChrisJackel_103
Nimbostratus
Nov 30, 2007Persistence problem with multiple pools under one VIP
We have one VIP with two separate applications under it, with traffic segregated with an iRule like the following:
when HTTP_REQUEST {
if {[matchclass [string tolower [HTTP::uri]] start...
ChrisJackel_103
Nimbostratus
Nov 30, 2007Thanks for the response.
Something unexpected happens why trying to specify the profile.
The wiki suggests this is a valid option for persist:
persist
But when I try it I get an error if I don't explicitly specify 'persist cookie insert cookie_a2'. If I try to reference the profile name I get the error below.
when HTTP_REQUEST {
if {[matchclass [string tolower [HTTP::uri]] starts_with $::myURL] } {
pool app2
persist cookie_a2
} else {
pool app1
persist cookie insert cookie_a1
}
}
01070151:3: Rule [myrule_persist_test] error:
line 4: [invalid option "cookie_a2" must be: cookie none source_addr simple dest_addr sticky msrdp ssl uie universal hash add lookup delete] [cookie_a2]
So the first clause fails, but the other clauses work. cookie_a2 is a valid persistence profile. That error message doesn't seem to indicate that is an option.
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