Forum Discussion
Peter_Wohlers_7
Nimbostratus
Dec 28, 2006hash persistence based on source ip network
We have an application that requires persistence, but causes the client to initiate two near-simultaneous connections.
Initially I tried using a persistence profile:
profile persis...
Peter_Wohlers_7
Nimbostratus
Jan 02, 2007This worked beautifully!
Here's the final iteration of the rule:
rule persnickety_application {
when HTTP_REQUEST {
scan [IP::client_addr] "%u.%u.%u.%u" first second third fourth
pool temperamental_servers
set client_net [ crc32 [ concat $first $second $third ] ]
persist hash $client_net
}
}
It almost seems like a better way to do source address/network persistence since it doesn't rely upon the completion of an initial connection in order to fix a destination member server. Same network/host will always go to the same destination pool member.
Thanks again,
Peter
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