Re: UpdatedConfirmation of NLB
- From: "Ryan Sokolowski [MVP - Avanade]" <ryan@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Jul 2005 13:18:56 -0700
Peter,
There is no point in having both IP addresses from each server on the same
IP Subnet. It seems that you're intending the second NICs as the Heartbeat
NICs. Leave these as is (with no GW) and change the IP addressing on the
public side to 172.16.x.x or 10.x.x.x or whatever is correct for your
environment.
If your environment is using 192.168.80.x internally, then change the HB IPs
to 172.16.x.x or whatever...
Here are some step-by-step instructions I wrote to assist others:
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.
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:92F5FA27-5F8D-4724-960C-6D088A2F55FA@xxxxxxxxxxxxxxxx
> Sorry but i made a couple of mistakes when typing and not thinking
>
> I have changed the original text:
>
>
> "Peter" wrote:
>
>> Can somebody has a far better understanding than me of Network load
>> balance
>> clusters confirm my configuration before i go to a live environment
>> please:
>>
>> Configuration
>>
>> Two Windows 2003 Servers running IIS
>> Two NIC cards in each
>>
>> First Server
>>
>> 1st NIC - 192.168.80.20/24 Default Gateway 192.168.80.2
>> 2nd NIC - 192.168.80.200/24 No Default Gateway
>> Second Server
>>
>> 1st NIC - 192.168.80.10/24 Default Gateway 192.168.80.2
>> 2nd NIC - 192.168.80.100/24 No Default Gateway
>>
>> Cluster IP 192.168.80.250 & 251 /24
>>
>> Configured on both machines using 1st NIC as dedicated
>>
>> Is this a suitable setup if not what is going wrong
> Secondly what traffic is passed to the card that does not support NLB??
>
>>
>> Any help gratefully received
>>
>> Pete
>>
>>
.
- Follow-Ups:
- Re: UpdatedConfirmation of NLB
- From: Peter
- Re: UpdatedConfirmation of NLB
- References:
- Confirmation of NLB
- From: Peter
- UpdatedConfirmation of NLB
- From: Peter
- Confirmation of NLB
- Prev by Date: Re: DO NOT INSTALL Windows 2003 SP1 on MSCS!!!
- Next by Date: Re: /PAE with Windows 2003 Service Pack 1 Cluster
- Previous by thread: UpdatedConfirmation of NLB
- Next by thread: Re: UpdatedConfirmation of NLB
- Index(es):
Relevant Pages
|
