Web Servers - Do you know how to Setup NLB on Windows Server 2016? (aka Network Load Balancing)
Last updated byBrady Stroud [SSW]over 1 year ago.See history
Downtime occurs when you have a single server setup.
TODO: This is 2008 R2 – update to 2016Note: 2008 R2 was not as reliable as later versions. So it would be better to use failover cluster in Server 2012 R2 or 2016 for a more reliable infrastructure configuration.
Use NLB to allow load balancing and failover. On each of your Windows Servers, you will host your website.
You need to follow these steps to get it up and running:
On all nodes of the NBL cluster, the Network Load Balancing Feature needs to be installed.
Setup NLBFigure: Install the NLB Feature
Open the Network Load Balancing Manager from Administrative Tools
Setup NLBFigure: Under the Cluster menu item, click New
Enter the first node in the cluster in ‘Host’ and press ‘Connect’
Setup NLBFigure: Select the interface for the node
Enter a Priority as 1 (this is just a host identifier)
Setup NLBFigure: In 'Priority' enter '1'
Setup NLBFigure: Enter a virtual IP address for the cluster. eg. 192.168.1.12
Choose the IP address of your cluster from the dropdown list Set a Full Internet Name eg. spcluster.sydney.ssw.com.au.
Ensure the Multicast Cluster operation mode is selected.
Setup NLBFigure: Set the 3 cluster parameters
You want sticky sessions so you don’t mistakenly bounce between servers (and lose your state)
Setup NLBFigure: Leave the Port Rule as default. This will provide sticky sessionSetup NLBFigure: Success. The cluster configuration will show a green icon
Right click the name of the cluster eg. spcluster.sydney.ssw.com.au Click Add Host To Cluster
Setup NLBFigure: Add the 2nd web server with a priority of 2
Open a command prompt and type in wlbs query to verify the cluster:
Setup NLBFigure: Type in wlbs query to verify the cluster
Ping both nodes and the virtual IP address externally to verify they are all working