Forum Discussion

Andrew_Joyce_14's avatar
Andrew_Joyce_14
Icon for Nimbostratus rankNimbostratus
Mar 13, 2014

SharePoint 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 DNS environment

 

My set up is as follows:

 

SharePoint Enterprise Server 2013 (SP1)

 

Multi-tenant environment using host header site collections. The default "SharePoint - 80" web application URL is for arguments sake is https://company.com

 

2 sharepoint app servers & 2 sharepoint web servers

 

The SharePoint Web Application was set up on default port 80

 

I have set up the SharePoint Alternative Access Mappings as the guide suggests:

 

Internal URL:https://company.com

 

Zone:Default

 

Public URL:https://company.com

 

Internal URL:http://company.com

 

Zone:Default

 

Public URL:https://company.com

 

The search content access (crawl account) has read access to the web application.

 

We are using the F5 SharePoint 2013 iApp template RC3 found here: https://devcentral.f5.com/wiki/iApp.Microsoft-SharePoint-2013-iApp-Template.ashx

 

In DNS we have an A record for company.com pointing to F5 virtual server IP address (no host file additions on SharePoint servers)

 

In the search content sources I have used the default "Local SharePoint sites" content source and have just one "start address" which is:

 

https://company.com

 

I have performed an index reset and full crawl but get messages like:

 

"This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times."

 

This is still a test environment so no real load of any concern on servers.

 

Does any have any ideas what migh be going wrong? ALSO... I have disabled the Minimal Download Strategy feature but still have problems with some functionality when accessing the site using https.

 

e.g

 

Cannot modify list views

 

Cannot view eclipse drop down menu on list items, documents and so on.

 

All a bit baffling. Any help greatly appreciated!

 

4 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    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_14's avatar
      Andrew_Joyce_14
      Icon for Nimbostratus rankNimbostratus
      Thanks 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.
    • mikeshimkus_111's avatar
      mikeshimkus_111
      Historic F5 Account
      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).
  • Hi Mike, sorry for late response to your suggestions. I managed to get SSL Offload working and search working by using the new SharePoint 2013 cmdlet (Post March 2013 PU) Set-SPSiteURL on all host named site collections.

     

    http://technet.microsoft.com/en-us/library/jj219633%28v=office.15%29.aspx

     

    I was able to add an "internet" zone URL mapping by doing the following:

     

    Example only:

     

    Set-SPSiteURL -identity http://hostnamedsite.contoso.com -Url https://hostnamedsite.contoso.com -Zone Internet

     

    Our default zone URL was HTTP

     

    I then followed the F5 guide, adding the Web Application's default Public HTTPS url into the search content source address list.

     

    It now appears to work.

     

    Thanks for your help.