Forum Discussion
Andrew_Joyce_14
Nimbostratus
NimbostratusSharePoint 2013, F5 and SSL Offload
I have been struggling to get SharePoint Search to index the content of my SharePoint site using the F5 guide http://www.f5.com/pdf/deployment-guides/sharepoint-2010-iapp-dg.pdf.
We have split D...
Hi Andrew, IIRC it took some work to get search crawling up and running. I'll check my test lab here and get back to you on it.
Your other issues may or may not be related to AAMs. You say you are using split DNS-are you using two VIPs, one for each DNS zone? Have you tried configuring the iApp to not use any caching, compression, or OneConnect profiles to see if that helps (not that we'd do that permanently, but it would help identify the issue).
BTW, the SharePoint RC3 iApp was promoted to downloads.f5.com. I recommend using that one because it's officially supported.
Andrew_Joyce_14Thanks Mike. I will ask our F5 guru here to check the iApp template we are using but am sure it is RC3, though was downloaded before the promotion to downloads.f5.com, has it changed from that original release? As for the split DNS, my understanding is that clients access site from public URL that maps to external IP, and that external IP is NAT'd to internal virtual IP ... I think this is how it works.- Looking at my lab, I see that I had set up an internal virtual server to load balance requests from the SharePoint servers themselves to the SharePoint FQDN, using host entries on the web front-ends to point to that VIP. I configured that internal deployment for SSL offloading using the iApp, disabling all caching, compression, and OneConnect. I used the https:// FQDN of my SharePoint site(s) in the content sources in the search service configuration. If you can configure that, let me know if it helps, and also if disabling optimization on the client-side VIP helps with the functionality issues. I recommend opening a support case if they continue (if you PM me with the case number, I can track it as well).
