Difference between revisions of "How to configure NLB for Windows Server"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
| Line 27: | Line 27: | ||
In order to configure the Network Load Balancer, proceed with the following steps : | In order to configure the Network Load Balancer, proceed with the following steps : | ||
| + | |||
1. On one of the node machines, call '''Start''' > '''Administrative Tools''' > '''Network Load Balancer Manager'''. Thereby, the service is activated on all node machines, which is necessary for cluster operation. | 1. On one of the node machines, call '''Start''' > '''Administrative Tools''' > '''Network Load Balancer Manager'''. Thereby, the service is activated on all node machines, which is necessary for cluster operation. | ||
Revision as of 13:52, 18 November 2014
How to install the Network Load Balancer
In the case where the Network Load Balancer is not pre-installed by the system :
1. Open Server Manager . In the Windows Start Menu select Start > Programs > Administrative Tools > Server Manager
2. Click on Features in the left-hand tree.Click Add Features to initiate the Add Features Wizard .
3. Select the Network Load Balancing checkbox.Click Next.
4. Proceed with the installation until you see the final screen.
5. Click on Finish.
The installation is complete.
Note :The Network Load Balancer should be installed-activated on all DLS Nodes.
NLB configuration
In order to configure the Network Load Balancer, proceed with the following steps :
1. On one of the node machines, call Start > Administrative Tools > Network Load Balancer Manager. Thereby, the service is activated on all node machines, which is necessary for cluster operation.
2. A tripartite configuration screen opens. To build a new cluster, go to Cluster > New in the menu or use the right-hand mouse key to call the context menu and select New Cluster.
NOTE: All members of the NLB cluster must be running on the same ESXi / ESX host.
