Cookies persistency

That looks like a good start. Is there a reason that you're not using cookie insert persistence instead though? With cookie insert persistence LTM will manage this for you automatically without depending on an app-set cookie. Also, with any HTTP property based persistence, you'll want to enable a OneConnect profile on the virtual server. If you're using SNAT on the serverside connections you can use the default OneConnect profile with a /0 source mask. If you're not using serverside source address translation, you can create a custom OneConnect profile with a /32 source mask. See this article for details:

 

 

http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/oneconnect

 

 

Aaron