24.3Configuration of the servers in the cluster
6.Set 192.168.1.1 (IP address of the cluster) as the IP address at default gateway for computers in the local network and, again, test availability of computers through the Internet.
HINT: If logging of corresponding connections is enabled (at both servers) in the WinRoute’s traffic rule for access to the Internet from the local network (see chap- ter 6.3), it is possible to use the Filter log to view how queries from a particular computer are distributed between both Internet connections.
24.3 Configuration of the servers in the cluster
NLB configuration for Server1
1.Select a connection to the local network and open a dialog where settings for this connection can be defined.
In the General tab, enable the Network Load Balancing component..
2.In the advanced configuration of the TCP/IP of the network interface connected to the local network, add the cluster’s IP address (192.168.1.1).
3.Open the dialog where properties of the Network Load Balancing component can be set.
In the Cluster Parameters tab, set the IP address of the virtual server (192.168.1.1) with a corresponding network mask and its full DNS name.
In the Cluster operation mode section, it is recommended to select the Multicast option. This will enable full traffic between individual servers in the cluster. This is important especially for the cluster administration (if the Unicast option was used, it would be inevitable to administer the cluster from a computer which is not included in the cluster).
4.In the Host Parameters tab, set priority of the server (the whole number 1 stands for the highest priority). Priority is also used as a unique identifier of the server for the cluster. It is also necessary to specify the server’s IP address (identical with the primary address of a corresponding network interface.
Note: In the Port Rules tab, specific rules for maintenance of the TCP and UDP traffic can be set. Only one rule is defined by default that determines that any traffic performed by these protocols will be equally distributed between all servers in the cluster.
HINT: Under Windows Server 2003, a wizard can be used to create the cluster (this wizard is included in the Network Load Balancing Administration tool).
