Default cookie persistence

You don't need to enable SNAT to use cookie persistence or OneConnect. If you don't need SNAT, then you can create a custom OneConnect profile with a /32 source mask. Assign that OneConnect profile to both virtual servers. This ensures that serverside connections are only reused for the same client IP.

 

 

If you do not enable SNAT and have a /0 source mask OneConnect profile enabled on the VS, TMM can reuse one client's serverside connection for a different client IP. This will cause the server logs to show the wrong source IP and can also lead to app session mixing issues if the app makes assumptions about the client session based on the source IP address.

 

 

Is that the information you were looking for? If not, can you clarify?

 

 

Thanks, Aaron