{"id":2862,"date":"2014-11-03T07:53:24","date_gmt":"2014-11-03T13:53:24","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=2862"},"modified":"2015-04-24T14:59:52","modified_gmt":"2015-04-24T19:59:52","slug":"configuring-network-load-balancing-in-windows-server","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/configuring-network-load-balancing-in-windows-server\/","title":{"rendered":"Configuring Network Load Balancing in Windows Server"},"content":{"rendered":"

\"NetworkServices and applications that are affected by high load require technologies to address this issue. Network Load Balancing is a technology that allows system administrators to configure clusters that distribute traffic between several servers. Suppose you have a website that receives a large number of requests and cannot be handled by one server. In this case you would configure a NLB cluster to distribute traffic across multiple web servers and thus ensuring that the website can serve all requests.<\/span><\/p>\n

In this article I will show you how to configure Network Load Balancing (NLB)<\/i> within your Windows Server infrastructure<\/a>. For this tutorial I will be using two virtual machines hosted in my VMWare testing environment. Without any delays let\u2019s open up the Server Manager<\/i> console and install the Network Load Balancing<\/i> feature. Note that this feature must be installed on both servers. Click on Add roles and features<\/i> button and skip all pages until you reach the Features<\/i> section. From the features list select Network Load Balancing<\/i> and proceed with the installation. Note that Powershell support for NLB will also be installed:<\/span><\/p>\n

\"Network<\/span><\/p>\n

Once the install operation is completed, open the Network Load Balancing Manager<\/i> console from Administrative Tools<\/i><\/a>.<\/span><\/p>\n

Within the NLB<\/i> console<\/i>, click on Cluster<\/i> from the upper menu and select New<\/i>. Now enter the local server IP address and click on Connect<\/i>. Select one of the available network interfaces that will be part of the NLB process and proceed with the following section. I\u2019ve added one of my two servers to the cluster, you will need to add the second machine afterwards.<\/span><\/p>\n

\"New<\/span><\/p>\n

In the following section we\u2019ll need to configure the priority of the specified server and the initial host state. Note that you can add multiple IP addresses<\/a> for one host. Continue the wizard by pressing the Next<\/i> button. We\u2019ll need to assign an IP address for the load balancing cluster that is shared between all nodes. This IP address is not physically assigned to a network card and instead a virtual network adapter is created. Note that you can add multiple IPs for load balancing, but the first one will be considered the primary address. For testing purposes I will add a random IP address:<\/span><\/p>\n

\"NLB<\/span><\/p>\n

The next section is used to configure cluster parameters. Enter the cluster full internet name (in my example cluster1.ppscu.com<\/i>) and the cluster\u2019s operation mode. A NLB cluster must operate in one of the following modes:<\/span><\/p>\n

Unicast<\/i> \u2013 the MAC address of the cluster virtual network adapter is shared with all cluster nodes. If your servers have only one network adapter then the MAC address of the VNA replaces the MAC address of the physical interface. By using only one network adapter on each server, communication will be made only with devices that are part of the same subnet as the given node. It\u2019s recommended that you use two network adapters for each node, one used for load balancing and the other one for server management.<\/span><\/p>\n

Multicast<\/i> \u2013 the server will retain its original MAC and IP address while also using the MAC and IP address of the cluster\u2019s virtual network adapter. All devices from all subnets can communicate with the node, but multicasting is used for cluster communication.<\/span><\/p>\n

IGMP Multicast<\/i> \u2013 uses the IGMP<\/i> protocol (Internet Group Management Protocol<\/i>) to increase network performance by using multicast clients registered to a IGMP multicast server.<\/span><\/p>\n

From the three available options, choose multicast and proceed with the next section:<\/span><\/p>\n

\"NLB<\/span><\/p>\n

From the port rules section we configure how traffic is managed on the NLB cluster. By specifying the designated port or port range you filter packets so that only desired traffic is received by the NLB cluster:<\/span><\/p>\n

\"NLB<\/span><\/p>\n

Rules can be created on each of the cluster\u2019s IP address. By pressing the Edit<\/i> button we configure the port range<\/i>, protocol<\/i> (TCP<\/i> or UDP<\/i>) and the filtering mode<\/i>. There are three available filtering methods, as follows:<\/span><\/p>\n

Multiple host<\/i> \u2013 used to configure all nodes within the NLB cluster to respond to requests. The node\u2019s affinity determines which of the cluster\u2019s servers handles the traffic. There are three options available here:<\/span><\/p>\n

\u00b7 None<\/i> \u2013 traffic is distributed between all cluster nodes<\/span><\/p>\n

\u00b7 Single<\/i> \u2013 uses all nodes to handle NLB traffic, but a node will receive all traffic for a specific request. This is used when stateful connections are used and is the default option. The timeout parameter is configured to discard connections once a connection passes a certain period of time.<\/span><\/p>\n

\u00b7 Network<\/i> \u2013 redirects client requests to the closest available node. Just like netmask ordering, requests are sent to the appropriate node based on the subnet of the client.<\/span><\/p>\n

Single host<\/i> \u2013 in this mode the traffic that matches a filtering rule will be handled by one node only.<\/span><\/p>\n

Disable this port range<\/i> \u2013 this mode is used to block the traffic sent on the specified ports.<\/span><\/p>\n

\"NLB<\/span><\/p>\n

The newly created node will appear in the NLB Manager console. We will add the second server by right clicking<\/i> the cluster and selecting Add Host to Cluster:<\/i><\/span><\/p>\n

\"NLB<\/span><\/p>\n

Now you will need to follow the same procedure as we did earlier for the first node. Once the wizard is completed, the second node will be added to the NLB cluster.<\/span><\/p>\n

\"NLB<\/span><\/p>\n

With this NLB cluster we can now distribute traffic destined for our applications between these two hosts. I\u2019ve used this type of configuration when balancing traffic between two IIS servers<\/a>. The port rules where handling only HTTP (port 80) and HTTPS (port 443) traffic. Most enterprises use dedicated network devices for load balancing such as Netscaler, Cisco Ace, etc, but it\u2019s good to remember that Windows Server Editions can support this feature as well. Hope this article will serve you well in understanding how this technology works and how to install and configure NLB clusters. For any questions don\u2019t hesitate to use our comments section and I will respond as soon as possible. Wish you a great day and stay tuned for the following articles.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Services and applications that are affected by high load require technologies to address this issue. Network Load Balancing is a technology that allows system administrators to configure clusters that distribute traffic between several servers. Suppose you have a website that receives a large number of requests and cannot be handled by one server. In this […]<\/p>\n","protected":false},"author":4,"featured_media":2879,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,9,8],"tags":[],"class_list":["post-2862","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-technical","category-windows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/2862","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=2862"}],"version-history":[{"count":5,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/2862\/revisions"}],"predecessor-version":[{"id":3452,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/2862\/revisions\/3452"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/2879"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=2862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=2862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=2862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}