Re: Web NLB
- From: "Rodney R. Fournier [MVP]" <rod@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Apr 2006 18:37:14 -0500
Glad you got past the first phase.
Set the balancing to even, that will distribute the load. Are you using SSL?
If so affinity will also need to be set.
Robocopy works great, free from the Windows Server 2003 Resource Kit.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dom" <Dom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B2FFA791-B350-43F2-B3B5-9EF678D87750@xxxxxxxxxxxxxxxx
Hello Rodney,
Don't know if you will ge this or not but thought that I would give it a
try.
I have moved out of a testing environment and have configured two servers
in
a load balance "cluster" using your instructions. Works great. If I shut
down
the primary node the second picks up the load and my websites are still
available. Thanks!
A couple quick questions...
I have just been informed that we need to distribute the load between the
two boxes. Any thoughts on how best to accomplish this?
Also, any way for changes that I make on one node to automatically be
pushed
to the second node?
Thanks for all of your help.
Dom
"Rodney R. Fournier [MVP]" wrote:
The second NIC is for internal management :)
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dom" <Dom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F369CFCE-9C35-444D-B2F2-99E28C21A938@xxxxxxxxxxxxxxxx
I have followed directions from enclosed hyperlink (great source of
information, by the way!) on a couple test servers and have a couple
issues.
Firstly, the NICs are labeled "public" and "NLB"
Lets's say my internal IP scheme is 10.0.1.* with a 255.0.0.0 subnet.
I have set up the "Public" NIC on each node as 10.0.1.47 and 10.0.1.48
with
a 255.0.0.0 subnet on each, along with the correct gateway and DNS
servers.
The second NIC on each node has been configured with IPs of 192.168.1.1
and
192.168.1.2, subnet of 255.255.255.0.
I installed Network Load Balancing on each of the "public" NICs and set
the
Cluster Parameter IP address on both nodes as 10.0.1.50 subnet
255.0.0.0.
Host Parameters on each reflect the "Public" NIC IP each each node with
priorities of 1 and 2, respectively. I have added 10.0.1.50 to my list
of
IPs
on each "Public" NIC.
I have created host records in DNS for both nodes and for the cluster.
From my workstation I can successfully ping 10.0.1.47 and 10.0.1.50 but
not
10.0.1.48.
I can successfully establish a remote desktop session with both
10.0.1.47
and 10.0.1.50. When I log onto 10.0.1.50 using a remote desktop
connection
I
notice that the actual node that I am logged onto is 10.0.1.47.
As stated above I cannot successfully ping or establish remote desktop
session with 10.0.1.48. IP DOES resolve to correct host name when
pinged
but
no reply.
I have missed something somewhere
I hope that this makes sense.
Question... Why the second NIC with 192.168.1.* IP?
"Rodney R. Fournier [MVP]" wrote:
One Nic and only one will be configured with NLB, add the IPs to that
NIC
:)
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dom" <Dom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F88AF57-44E7-449C-8EEC-893008A2D724@xxxxxxxxxxxxxxxx
Thanks Rodney!
One quick question:
When you say add as many IP as needed to the NLB NIc are you
reffering
to
the second NIC on each machine or the virtual NIC for the cluster?
Thanks for your help,
Dom
"Rodney R. Fournier [MVP]" wrote:
1. NLB is the way to go. If you are using the recommended two NICs
here
are
the steps -
http://msmvps.com/blogs/clustering/archive/2005/10/21/71893.aspx
2. Add as many IPs as are needed to the machines on the NLB NIC.
Create
additional port filtering rules as needed or assign the default
rule
to
all
IPs.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dom" <Dom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:96E5B3CB-E39B-43CF-A2E4-8DB9E4DFFCC3@xxxxxxxxxxxxxxxx
I am getting ready to implement two IIS servers in a NLB cluster
and
am
looking for a little insight before beginning this endeavor.
I have two issues that I will be addressing during this project
and
would
welcome any insight (or KB articles) from anyone who has done
this
before.
#1: I do NOT want servers to simply perform fail over but rather
share
the
traffic between the two. We have one site that gets absolutely
hammered
twice
a year and we would like to configure so that any session that is
established
will go to the least taxed server.
#2: This is the part that I am having trouble with...
We have roughly 20 sites that we host and each has it's own
dedicated
IP
address (both LAN and WAN). I can find no documentation anywhere
on
how
best
to assign the LAN IP addresses to the load balance NIC of the
cluster.
Any help at all appreciated!
Oh, by the way, we are using Server 2k3.
Thanks.
.
- References:
- Re: Web NLB
- From: Rodney R. Fournier [MVP]
- Re: Web NLB
- From: Rodney R. Fournier [MVP]
- Re: Web NLB
- From: Dom
- Re: Web NLB
- From: Rodney R. Fournier [MVP]
- Re: Web NLB
- From: Dom
- Re: Web NLB
- Prev by Date: Re: Web NLB
- Next by Date: Windows Server 2003 R2 Cluster
- Previous by thread: Re: Web NLB
- Next by thread: Re: Clustering with a Novell Netware 6.5 iSCSI target
- Index(es):
Relevant Pages
|