SharePoint 2013 Cookie persistence

The persistent cookie option is really only relevant to SharePoint with Access Policy Manager (APM). You don't need it for a straight LTM deployment. As for persisting across VIPs, setting a domain attribute in a cookie persistence iRule would certainly be a good option.

I may be misunderstanding your question though. Are you saying that there are two SharePoint servers behind a single VIP, or that you have two VIPs (with the same pool members) and you want to persist to the same pool member across both VIPs?

4 sharepoint servers behind a vip with cookie persistence and standard VS config. http.

Then you don't need iRule-based cookie persistence. The built-in cookie persistence profile should work fine.

ok. so first question: sharepoint 2013 + cookie persistence => OK? No worries about the warning in the iApps/sharePoint manual ?

and no impact if I use cookie persistence?

I'm assuming here that you're referring to the statement pertaining to persistence:

Do not create this profile if using SharePoint 2013

I'm not 100% sure, but I think this is some weird wording. You should be able to use the built-in cookie persistence profile without any issues.

That is some ambiguous wording, we'll look into changing it in the guide.

It's fine to use cookie persistence with SharePoint 2013. Although in this case, wouldn't you create two pools and use an iRule to do pool assignment based on the host header? You'd need to do that to send the request to the correct server before applying persistence.