Sie sind auf Seite 1von 5

To create an NLB

cluster

Installing the Network Load Balancing Feature

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:

C:\Windows\system32>servermanagercmd -install nlb


......

Start Installation...
[Installation] Succeeded: [Network Load Balancing].
<100/100>

Success: Installation succeeded.

Once installation is complete both the graphical Network Load Balancing Manager and
the command line NLB Cluster Control Utility (nlbmgr.exe and nlb.exe respectively)
will be installed ready for use.

Building a Windows Server 2008 Network Load Balanced


Cluster

1. To open Network Load Balancing Manager, click Start,


click Administrative Tools, and then click Network Load
Balancing Manager. You can also open Network Load
Balancing Manager by typing Nlbmgr from a command
prompt.
2. Right-click Network Load Balancing Clusters and then
click New Cluster.

3. Connect to the host that is to be a part of the new cluster.


In Host, enter the name of the host, and then click Connect.

4. Select the interface that you want to use with the cluster,
and then click next. (The interface hosts the virtual IP address
and receives the client traffic to load balance.)

5. In Host Parameters, select a value in Priority (Unique


host identifier). This parameter specifies a unique ID for each
host. The host with the lowest numerical priority among the
current members of the cluster handles all of the cluster's
network traffic that is not covered by a port rule. You can
override these priorities or provide load balancing for specific
ranges of ports by specifying rules on the Port rules tab of the
Network Load Balancing Properties dialog box. Click Next
to continue.

6. In Cluster IP Addresses, click Add to enter the cluster IP


address that is shared by every host in the cluster. NLB adds
this IP address to the TCP/IP stack on the selected interface of
all hosts chosen to be part of the cluster. NLB doesn't support
Dynamic Host Configuration Protocol (DHCP). NLB disables
DHCP on each interface it configures, so the IP addresses must
be static. Click Next to continue.

7. In Cluster Parameters, type values in IP Address and


Subnet mask (for IPv6 addresses, subnet mask is not
needed). A full Internet name is not needed when using
NLB with Terminal Services.

8. In Cluster operation mode, click Unicast to specify that


a unicast media access control (MAC) address should be used
for cluster operations. In unicast mode, the MAC address of the
cluster is assigned to the network adapter of the computer,
and the built-in MAC address of the network adapter is not
used. It is recommended that you accept the unicast default
settings. Click Next to continue.

9. In Port Rules, click Edit to modify the default port rules.


Configure the rules as follows:

In Port Range, specify a range of 3389 to 3389 so that the


new rule applies only to RDP traffic.

In Protocols, select TCP as the specific TCP/IP protocol that a


port rule should cover. Only the network traffic for the
specified protocol is affected by the rule. Traffic not affected by
the port rule is handled by the default host.

In Filtering mode, select Multiple host, which specifies that


multiple hosts in the cluster handle network traffic for this port
rule.

In Affinity (which applies only for the Multiple host filtering


mode), select None if you are planning to use TS Session
Broker. Select Single if you are not planning to use TS Session
Broker.

10. Click Finish to create the cluster.

Simple scenario for setup the NLB

Node1 -

o "Public" NIC
* IP address: 10.10.10.11
* Subnet: 255.255.255.0
* Gateway: 10.10.10.1
* DNS: as appropriate

o "Admin" NIC
* IP address: 192.168.1.1
* Subnet: 255.255.255.0
* Gateway: N/A
* DNS: N/A

* Node2 -

o "Public" NIC
* IP address: 10.10.10.12
* Subnet: 255.255.255.0
* Gateway: 10.10.10.1
* DNS: as appropriate

o "Admin" NIC
* IP address: 192.168.1.2
* Subnet: 255.255.255.0
* Gateway: N/A
* DNS: N/A

2. On the "Public" NICs, click "Advanced" and add an additional IP


address
as the Virtual IP Address which clients will connect to from the Public
network (i.e. - 10.10.10.169)

3. Install "Network Load Balancing" as an additional service from the


"Public" adapter properties.
* Click "Install.." and then select "Service" in the upper-window and
click "Add."
* Select "Network Load Balancing" in the upper-window and click "OK"
* Answer any prompts and provide the correct path to installation
media (Windows 2000 installs only).

4. Once NLB is installed, return to the Properties page for the "Public"
NIC and select the check-box next to "Network Load Balancing." This
enables the service globally.

5. Next, select the item "Network Load Balancing" and click


"Properties"

6. Configure the NLB Cluster properties according to your parameters,


using the following example steps as a guide.

* Node1 -

o "Public" NLB Cluster Parameters tab


* Primary IP address: 10.10.10.169
* Subnet: 255.255.255.0
* Full Internet Name mail.clusterhelp.com

o "Public" NLB Host Parameters tab


* Priority: 1
* Dedicated IP address: 10.10.10.11
* Subnet: 255.255.255.0

* Node2 -

o "Public" NLB Cluster Parameters tab


* Primary IP address: 10.10.10.169
* Subnet: 255.255.255.0
* Full Internet Name mail.clusterhelp.com

o "Public" NLB Host Parameters tab


* Priority: 2
* Dedicated IP address: 10.10.10.12
* Subnet: 255.255.255.0

7. MultiCast support can be optional in this configuration, though I


would not recommend it.

8. You can also now take time to create a static Host record (A record)
in
your scenario's DNS infrastructure to provide appropriate name
resolution
to the NLB cluster name (i.e. - mail.clusterhelp.com or just mail).

9. Your NLB cluster should be up and running after the nodes


converge.

10. An external client should now be able to ping the IP address of the
NLB cluster (i.e. - 10.10.10.169) as well as each of the individual node
addresses (i.e. - 10.10.10.11 & 10.10.10.12).

11. Many good diagnostic commands can be found by typing "wlbs /?"
in a
command window. For example, "wlbs query" shows the status and
convergence state of the cluster.

Das könnte Ihnen auch gefallen