This will be for Soap calls over HTTP. The traffic is intended for IBM Websphere application (Java based).
I just spoke with the developer. Forget the whole issue about having the destination IP address in the content. The traffic will be sent to a URL (VS IP address). What he was expecting to see the LTM to recognize the originating traffic coming from 10.10.10.20 and that the LTM would be able to send the traffic back to the same member of the pool 10.10.10.20. If 10.10.10.20 was not available, then push the traffic to the other member (10.10.10.21). This sounds like the issue with layer2/3.
Follow