Forum Discussion
Universal persistence using header values for multiple client IPs.
Hi ajohnson,
this setup will be somewhat complicated then and requires other/additional coding techniques than using
[persist] to team the instances.
What is the reason to forward the backend connection to your F5 if the DST_IP is always the orginating SRC_IP? It would be much easier if the service on 1.2.3.4:994 will always directly connect to 1.2.3.4:499 (aka. 127.0.0.1:499) and the service on 1.2.3.5:994 will always request to 1.2.3.5:499 (aka. 127.0.0.1:499 too)...
Beside of that, it would be good to know how your iRule/LTM Policy configuration selects the different backend pools based on the incomming HTTP requests?
Cheers, Kai
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