locked
URL based load balancig for SharePoint WFE RRS feed

  • Question

  • Hi,

    We have a server farm with three WFEs

    1.SRV1

    2.SRV2

    3.SRV3

    I have created a web application with the named as  server1.xyz.com which is the FQDN of the server 1. After I create this web application called Portal then IIS server hosted on Server1 started listening the request  with host name binding of the web application server1.xyz.com. This results into the configuration where All WFEs have the same configuration replicated. Which means all of them have Portal Web Applications with binding server1.xyz.com.

    Now when I try to submit the request in SNOW tool for NLB it was required to submit the all the web urls. When I try to browse server1.xyz.com it works fine  but when I try to browse the same on server2 or server3 it does not work because  it will direct to server 1 only ..

    How can we help server2 and server3 to listen to the request and what will be the urls for these two servers

    I tried accessing the urls with http://server2/server1.xyz.com or http://server3/server1.xyz.com  the web application hosted in these servers does not respond.

    Can somebody help here ?

    Friday, September 16, 2016 6:40 PM

Answers

  • I solved the issue by creating web application at port 80 without host header. This way I was able to browse the SharePoint site with each Web servers by using http://localhostor http://servername/ . Now load balancer is able to use three urls:

    http://WFEServer1

    http://WFEServer2

    http://WFEServer3

     and thee of these urls are browsing.

    Regards

    Rajaniesh

       
    • Marked as answer by Rajaniesh Monday, September 26, 2016 12:31 PM
    Monday, September 26, 2016 12:30 PM

All replies

  • Change the Alternate Access Mapping and IIS Binding (of course) to a name that isn't the same as the computer name. The computer name itself is an A record that you (shouldn't) can't change as it is required for Active Directory. Use something like https://sharepoint.xyz.com instead.

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 9:04 PM
  • Thanks Seward for your answer.

    If I understood it correctly You mean to say this (Please confirm)

    1. I need to create A record called SharePoint which will point to VIP provided by NLB

    2.And then I need to change the AAM to sharepoint.xyz.com. So SharePoint Web application can be mapped to different URL.

    So if user browse sharepoint.xyz.com it will point to VIP which will point to one of the WFE. But how NLB will point to one of the WFE and what will be the URL?

    The fundamental question remains the same that how NLB will reference to this WFE servers to point to SharePoint sites?  Can you please explain step by step?

    Friday, September 16, 2016 10:35 PM
  • Correct. Also make sure your IIS Bindings are correct (e.g. sharepoint.xyz.com).

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 10:41 PM
  • sorry I am still not getting it... I need to create NLB request to obtain the VIP and there I  have to provide urls for both WFEs ? Can you please point me which URLs I can provide while submitting the request?  In order for VIP to point to WFEs they need to have the URL and I am not sure which URL this will be? I believe these URLs should be specific to WFEs 
    • Edited by Rajaniesh Friday, September 16, 2016 10:48 PM adding more details
    Friday, September 16, 2016 10:46 PM
  • A record of 'sharepoint' in the 'xyz.com' zone points to the VIP. VIP forwards HTTP and/or HTTPS requests to two or more SharePoint servers. These SharePoint servers have a Web Application using 'http://sharepoint.xyz.com' as the URL with a matching AAM and IIS Binding.

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 10:47 PM
  • So when VIP will point to 1st WFE it will use which url internally and if server 1 is down which url it will point to. Because all three WFEs will have same IIS bindings so how the request from VIP to WFE's IIS will translate to? Is this goint to be server1\sharepoint.xyz.com and server2\sharepoint.xyz.com? Please clarify 
    Friday, September 16, 2016 11:17 PM
  • It might be best if you read your load balancer documentation. This stuff is pretty clear and straightforward, with the generic setup being what I already provided.

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 11:29 PM
  • Even with generic setup NLB can not point to WFE if it does not know the  url and what is that URL we need to find it out and submit the request accordingly.
    Friday, September 16, 2016 11:36 PM
  • This is why I said read the documentation. NLBs don't use DNS, they use IP addresses. You point the NLB at the IP of the IIS site.

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 11:41 PM
  • I believe then I am near to finding my answer.. NLB will point to IP address of WFE server or server name resolved by DNS along with unique port number to uniquely identify the site it is trying to browse. So in this case is it possible  to browse the site with server IP address or Server name (because server name resolving to IP address autoimatically if we are not binding web site to IP addresses) + port something and browse it  --> http://server1/sharepoint   and http://server2/sharepoint ...In this case both should open the same site

    correct me if I am wrong

    Friday, September 16, 2016 11:51 PM
  • No. You can only browse for what IIS bindings exist. NLBs simply use the IP address of the servers to route traffic appropriately. The request header does not change.

    Again, this is a fairly fundamental concept your NLB documentation should have. You will need to read it *anyways* in order to configure it properly, so again, start with your NLB documentation.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, September 16, 2016 11:53 PM
  • ok So in case we want to host multiple web application with different host name but same port then How would you configure NLB address?
    Saturday, September 17, 2016 1:58 AM
  • I solved the issue by creating web application at port 80 without host header. This way I was able to browse the SharePoint site with each Web servers by using http://localhostor http://servername/ . Now load balancer is able to use three urls:

    http://WFEServer1

    http://WFEServer2

    http://WFEServer3

     and thee of these urls are browsing.

    Regards

    Rajaniesh

       
    • Marked as answer by Rajaniesh Monday, September 26, 2016 12:31 PM
    Monday, September 26, 2016 12:30 PM