This approach is ideal for load balancing of web servers where the same static web site data is stored on each node. In an alternative configuring, referred to as a pack the nodes in the cluster all access shared data. In this scenario the data is partitioned such that each node in the cluster is responsible for accessing different parts of the shared data. This is commonly used with database servers, with each node having access to different parts of the database data with no overlap a concept also known as shared nothing.
Windows Server Network Load Balancing clustering can be configured using either one or two network adapters in each node, although for maximum performance two adapters are recommended. In such a configuration one adapter is used for communication between cluster nodes the cluster adaptor and the other for communication with the outside network the dedicated adapter.
Network Load Balancing may be configured on a port by port basis or range of ports. For each port three options are available to control the forwarding of the traffic:. As such, the server application will typically maintain some form of session state during the client server transaction. Whilst this is not a problem in the case of a Single Host configuration described above, clearly problems may arise if a client is diverted to a different cluster node partway through a session since the new server will not have access to the session state.
Windows Server Network Load Balancing addresses this issue by providing a number of client affinity configuration options. Client affinity involves the tracking of both destination port and source IP address information to optionally ensure that all traffic to a specific port from a client is directed to the same server in the cluster. The available Client affinity settings are as follows:.
The first step in building a load balanced cluster is to install the Network Load Balancing feature on each server which is to become a member of the cluster. This can be achieved by starting the Server Manager tool, selecting Features from the left panel and then clicking on the Add Features link. In the list of available features, select Network Load Balancing and click on Next followed by Install.
Network Load Balancing may also be installed from a command prompt with elevated privileges right click on the command prompt in the Start menu and select Run as administrator by running the servermanagercmd -install nlb command. For example:. Once loaded, the manager will appear as shown in the following figure:. The Network Load Balancing Manager will now list the new cluster containing the single node as illustrated below:. With the cluster now configured and running, the next step is to add additional nodes to the cluster.
Before adding a new host to a cluster it is first necessary to install the Network Load Balancing feature on the new server as outlined previously in this chapter. If no cluster is currently listed, right click on Network Load Balancing Manager entry and select Connect to Existing. In the connection dialog enter the name or IP address of a node in the cluster or the IP address of the cluster itself and click on Connect.
Once the connection is established, click on Finish to return to the manager interface where the cluster will be listed in the left hand panel using the cluster's full internet name. To add a node, right click on the cluster name and select Add Host to Cluster. In the resulting dialog enter the name or IP address of the host to be added as a new cluster node and click on Connect.
Click Next to change any of the cluster port rule settings. Once finished, the new host will be listed in the manager screen with a status of Pending, followed by Converging and finally Converged.
Existing nodes in a cluster may be either suspended or removed. A suspended node may be resumed by selecting Resume from the same menu.
A deleted node must be added to the cluster once again using the steps outlined above. Jump to: navigation , search. Navigation menu Personal tools. Namespaces Page Discussion. Views Read View source View history. This page was last modified on 27 October , at Copyright Payload Media, Inc. So when users disconnected, either by mistake or due to some network interruption, upon reconnection the broker will redirect them to their session so that they can continue to work.
Other options for load balancing would be using NLB Step-by-step guide or a hardware loadbalancing appliance which would of course mean some extra investments and looking at the size of your environment that wouldn't make the best choice.
Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Notify me of new posts via email.
Blog at WordPress. Follow: RSS Twitter. Open HP-Teaming-Configuration: 5. Open the Properties of the Network Team 6. Like this: Like Loading Mohamed Arafa permalink. Leave a Reply Cancel reply Enter your comment here
0コメント