irule to do smarter cookie persistance

Hi Mike,

 

 

I suggest troubleshooting the default cookie insert persistence as that's the simplest option and it should work.

 

 

With default cookie insert persistence using a session cookie (no timeout), LTM will only set the cookie when a new load balancing decision is made. If the client presents a persistence cookie and the pool member is available, LTM will not set the same session cookie again as the client already has it. Does this explain the behavior you were seeing?

 

 

You'll also need to add a OneConnect profile to ensure LTM does request based persistence instead of per-connection. If you're using SNAT of any kind on the connections to the pool members, you can use the default OneConnect profile with a source mask of /0. If you're not using SNAT, create a custom OneConnect profile with the source mask set to /32.

 

 

Aaron