Forum Discussion

mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Mar 13, 2014

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.

 

mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Mar 14, 2014
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).