I'll post the step-by-step directions that I've put here a number of times
before - hope this helps you troubleshoot / rebuild to correct functioning
standards...
How-To: Configure Network Load Balancing (NLB) with Two Network Adapters
1. Assign appropriate IP addresses to each NIC, placing them in separate
subnets.
* Node1 -
o "Public" NIC
* IP address: 10.10.2.17
* Subnet: 255.255.255.0
* Gateway: 10.10.2.1
* DNS: as appropriate
o "NLB" 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.2.18
* Subnet: 255.255.255.0
* Gateway: 10.10.2.1
* DNS: as appropriate
o "NLB" 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.2.177)
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.
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.2.177
* Subnet: 255.255.255.0
* Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
* Priority: 1
* Dedicated IP address: 10.10.2.17
* Subnet: 255.255.255.0
* Node2 -
o "Public" NLB Cluster Parameters tab
* Primary IP address: 10.10.2.177
* Subnet: 255.255.255.0
* Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
* Priority: 2
* Dedicated IP address: 10.10.2.18
* Subnet: 255.255.255.0
7. MultiCast support can be optional in this configuration.
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.domain.com or just mail).
9. Your NLB cluster should be up and running.
10. An external client should now be able to ping the IP address of the NLB
cluster (i.e. - 10.10.2.177) as well as each of the individual node
addresses (i.e. - 10.10.2.17 & -.18).
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.
12. IMPORTANT NOTE: In this configuration, each individual node is NOT able
to ping the other node's Public physical IP address (i.e - 10.10.2.17 cannot
ping 10.10.2.18 and vice-versa). I believe this is expected behavior, as
the NLB cluster is now responding to requests on the Virtual Cluster address
(i.e. - 10.10.2.177).
--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP
Avanade
http://www.Avanade.com
"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."
This posting is provided "AS IS" with no warranties, and confers no rights.
"FireBrandCK" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Greetings,
>
> I'm seeking advice from a person who has successfully configured and
> tested a simple Windows Network Load Balancer (WNLB) configuration.
>
> Executive summary:
> The cluster is setup correctly (with some anomalies), however when host
> with priority 1 fails, the failover to the second host does not occur.
> The test bed is housed on a laptop using VMware 4.5.2 Workstation with
> a virtual TCP/IP network.
>
> Details:
>
> Image five command prompts pinging five IP addresses:
> window A pinging the virtual IP false
> window B pinging host A, NIC#1 true
> window C pinging host A, NIC#2 true
> window D pinging host B, NIC#1 true
> window E pinging host B, NIC#2 true
>
> - A new NLB cluster is created using the NLB manager. A new cluster is
> set to use the virtual IP, cluster operates in the unicast mode, port
> range set to max, and affinity set to none.
> - A host (A) is looked up using IP from NIC#1 and it is added to the
> new cluster using IP from NIC#2 with priority set to 1. Host converges
> successfully - NLB manager reports success. During this process
> virtual IP starts responding.
> Result:
> window A pinging the virtual IP true
> window B pinging host A, NIC#1 true
> window C pinging host A, NIC#2 true
> window D pinging host B, NIC#1 true
> window E pinging host B, NIC#2 true
>
> - A host (B) is looked up using IP from NIC#1 and it is added to the
> new cluster using IP from NIC#2 with priority set to 2. Host converges
> successfully - NLB manager reports success. During this process host
> B NIC#1 stops responding (this did not happen when host A was added).
> Result:
> window A pinging the virtual IP true
> window B pinging host A, NIC#1 true
> window C pinging host A, NIC#2 true
> window D pinging host B, NIC#1 false
> window E pinging host B, NIC#2 true
>
> - Shut down host A with expectation that host B will take control.
> Result:
> window A pinging the virtual IP false
> window B pinging host A, NIC#1 false
> window C pinging host A, NIC#2 false
> window D pinging host B, NIC#1 false
> window E pinging host B, NIC#2 true
>
> It appears that the failover does not occur because host B NIC#1
> becomes dysfunctional when host B is added to the cluster.
>
> If you've experienced a similar problem and found a resolution or can
> offer advice please call me 301 379 8676 or email me directly.
>
> Thank you in advance for your time,
>
> CK
>
Similar Threads
Linear Mode
