|
|
Hello
Here is my scenario. We currently have a web server that is running Windows
Server 2003 Standard R2. IIS see the settings as a local folder on this
server. For the sake of this email, here’s the config for this server
Server1 IP – 10.128.40.100
We need to include a second server (same OS – same subnet) and set up NLB
between these servers. Let’s use this config for the new server
Server2 IP – 10.128.40.102
Based on the limitations of the software (Standard edition), we cannot do a
true cluster, so the IIS data will be moved to Server2 and the existing
server (Server1) will point to a share on Server2 through a UNC path to
access the data.
My question is this…..what would be the best way to set up NLB between these
servers? Currently, IIS/DNS is pointing to 10.128.40.100 – I want to keep
this IP (10.128.40.100) as the VIP of the cluster so that I don’t run into a
DNS issue. What would the best setup when configuring these servers,
multicast or unicast? How would you set up the NICs when using either
configuration? Should two NICs be enabled for NLB or should I user 1 NIC for
NLB and the other NIC strictly for server to server communication?
Here is one scenario that I have layed out – any thoughts or comments would
be welcome. I was going to enable both NICs on the servers (dell 2950’s)
Server1 (current production server – the IP’s will need to change)
NIC1 – 10.128.40.104 (dedicated IP on NIC)
NIC2 – 10.128.40.105 (dedicated IP on NIC – NIC will be used for clustering
– VIP 10.128.40.100)
Server2 (added server)
NIC1 – 10.128.40.102 (dedicated IP on NIC)
NIC2 – 10.128.40.103 (dedicated IP on NIC – NIC will be used for clustering
– VIP 10.128.40.100)
I know that many of you have implemented NLB previously – any assistance
would be greatly appreciated.
Thanks in advance
Greg
|
|
|