Universal persistence using header values for multiple client IPs.

Hello Kai, thanks for the response.

Just a clarification:

"What is the reason to forward the backend connection to your F5 if the DST_IP is always the orginating SRC_IP?"

This is not the case, the only requirements are that the target pool member both be the same for the two separate connections from the client and the server. At present this is how the application has to work, but of course standard load balancing must distribute load.

I am now looking at adding a new header to the clients initial request to the server (containing the target node IP), then when the server request arrives with this header value use it to target the required node, but I would prefer to use universal persistence (persist lookup perhaps) if possible.

Kind Regards