• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1501
  • Last Modified:

Windows 2008 R2 Network Load Balancing and Exchange 2010

I'm try to setup my first NLB using Windows 2008 R2. I have setup a 2003 cluster before. Anyway, I have two servers that will be used to form my CAS Array.

I have two NIC teamed that are connected to the main lan

and One that directly connect to the other server via a cross over cable for use as the heart beat.

Here are my questions.

1) I have followed all of the online instrustions on how to setup a CAS Array.  If one of my cas server in the array were to fail. WOuld those users who's sessions were associated with that cas server lose there connection? Would they be able to reconnect through the other cas server

2) I cannot ping my Virtual NLB name or IP I made sure port forwardin is enabled on my LAN connection

3) how can I monitor how much load is one each NLB node

4) for a EXchagne 2010 I have ready the port affinity should be "SINGLE" is this correct
0
compdigit44
Asked:
compdigit44
  • 41
  • 33
1 Solution
 
compdigit44Author Commented:
If I remove my nodes and add them back in but make then all use my default LAN I can ip my virtual NLB name

How can I force all NLB heart beat traffic to go through my cross over NIC connection only?
0
 
compdigit44Author Commented:
Does my LAN and Heart beat Nic's have to be attached to the same network segment???

please help
0
 
AkhaterCommented:
Thats a lot of questions but I will try to help

A. I would advise you to break your teaming now, nlb and teamin is known to create problems so start with not teamed nics you can move to teamed later on

B. In the event of failure all ppl connected to the failing node will have to reconbect and will lose their session

C. What nlb did you use unicast or mulicast?

D. No you dont have to use single affinity

E. Heart beat IPs should be on a different subnet
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
compdigit44Author Commented:
Ok I broke my NIC team and setup on NIC for the cluster IP and the other for heart beat. Both NIC are on the same subnet and network segment. I removed the crossover cable heart beat cable I was using.

How when I try to add one or any of my node I keeping getting an "Misconfigured Adapter" message and my node has a yellow exclaim point

I have been workong on this for 4 hours so far and no luck

BTW..anyone using a LoadMaster 2200 from KempTechnologies for Exchange 2010 CAS NLB
0
 
AkhaterCommented:
Both NIC are on the same subnet and network segment.  ->>> They should be on DIFFERENT subnets


0
 
compdigit44Author Commented:
DOesn't matter no matter what I do same or different subnet I keep getting the misconfigurate NIC message
0
 
AkhaterCommented:
can u share a screenshot please
0
 
compdigit44Author Commented:
This is why I removed the crossover cable I was usiung as my heat beat for my NLB : Microsoft KB 242248
0
 
compdigit44Author Commented:
OK here is what I had to do to get my 2008 NLB to work

1) Break the NIC team and remove teaming software
2) setup static ip' for all NIC that are on the same subnet. Connect not get things to work with when using the cross over cable.
3) Righ tnow I can ping all of my NLB server by name and cluster IP

SO my two node NLB cost me 5 static ip address this is including the Virtual IP

BTW, how can I monitor how much load or traffic each node is handleing?

How can I be sure  no Cluster traffic is going arround what should be the heat beat NIC's
0
 
AkhaterCommented:
your HB ip should not be on the same subnet this is not the way they shld be


I am not aware of anyway to monitor how much traffic is handled by each server

for your last question you have to create the DNS record of your CAS array to point to the virtual ip
0
 
compdigit44Author Commented:
Thanks for the reply ..

I only have one subnet on my network.

If I directly connect the heart beat NIC's via a cross over cable I cannot PING the Cluster IP
0
 
AkhaterCommented:
when u connect them directly you are putting another range of IPs on the NIC s?
0
 
compdigit44Author Commented:
No I just type in a static ip and that's it
0
 
AkhaterCommented:
OK sorry let's go over this again shall we


Server 1 NIC1 connected to LAN: 192.168.0.20/24
Server 1 NIC2 CrossOver : 192.168.10.20/24

Server 2 NIC1 connected to LAN: 192.168.0.21/24
Server 2 NIC2 CrossOver : 192.168.10.21/24


is that it ??
0
 
compdigit44Author Commented:
Idea is correct
0
 
AkhaterCommented:
ok when u do this can u ping both NIC ? from both servers ?
0
 
compdigit44Author Commented:
yes
0
 
compdigit44Author Commented:
I can join the nodes to the cluster but even after adding the first node I cannot ping the virtual cluster ip
0
 
AkhaterCommented:
ok are you trying to ping the virtual ip from the same subnet or a differnt one?
0
 
compdigit44Author Commented:
I'm trying to ping the virtual ip from the same subnet all of my servers and workstations are on
0
 
AkhaterCommented:
what NLB type are you using? unicas or multicas ?
0
 
compdigit44Author Commented:
I have tried setting up a unicate and multicast both have the same result

I believe unicast is preferred though for a Exchange 2010 CAS array
0
 
AkhaterCommented:
are u enabling nlb for specific ports only?
0
 
compdigit44Author Commented:
No I leave the NLB port setting as default which is ALL for wide open
0
 
compdigit44Author Commented:
It seems like a routing issue?

I know A NLB and cluster behave different are you sure the heart beat network can be ona totaally different network that my regualr LAN. please note the heat beat cross over cable network is have accessable from my regalar lan
0
 
AkhaterCommented:
it cant be a routing issue on the same network.

In the nlb manager are both showing convergent?

Turn of one node and test again after 5 min can u ping the vip?

is it connected to a cisco switch?
0
 
compdigit44Author Commented:
both nodes are showing as converged.

I will try to power down one of the nodes as request

please note even after adding only the one noded "it self" I cannot ping the virtual ip
0
 
compdigit44Author Commented:
also we are not using cisco switch we use foundry
0
 
compdigit44Author Commented:
Here is what I did.
1) Removed all nodes from NLB
2) cleared, dns cache and arp cache on servers and workstations
3) Rebooted
4) Attached cross over cable
5) added One nodes it'sef to the NLB cluster. I joinged succesfully.
6) Waited 10 minutes and tried to ping the virtual ip and cannot ping it

0
 
compdigit44Author Commented:
I can ping the virtual ip and name from both Nodes though????
0
 
AkhaterCommented:
are these virtual servers
0
 
compdigit44Author Commented:
Two physical servers DL 360's
0
 
compdigit44Author Commented:
AV is installed on these servers
0
 
AkhaterCommented:
it doesnt make sense can u disable any firwall uninstall antivirus
0
 
compdigit44Author Commented:
just finishe uninstalling AV no change??

Could it be the network switches
0
 
AkhaterCommented:
r u on unicast now?
0
 
compdigit44Author Commented:
yes
0
 
AkhaterCommented:
r u on unicast now?
0
 
AkhaterCommented:
and u can ping froom the other nde even when it is not joined to the cluster?
0
 
compdigit44Author Commented:
I see what is happening..

When I setup the cluster... I noticed the cluster IP is assign a MAC address to my heart beat NIC which is not my LAN.. This is why I cann't ping and thing

if I manually set the mac address on one of ONE of my NODEs to the MAC of the cluster IP will this work

I know I cannot do this on both nodes becuase it will cause an ip conflict

Is this why hardware load balancers are better than software load balancers?
0
 
AkhaterCommented:
wait on which NIC are you enabling NLB ?

A virtual mac address will be assigned that's why i have been asking u about unicast or multicast, and yea hardware load balancers are better but from what your telling me you are setting NLB on the wrong nic
0
 
compdigit44Author Commented:
I have tried both unicast and multicast and both do not work
 Under NIC properties I see that the NLB function enable for the heat beat NIC which is connect via cross over cable and not my LAN connection.

When I break my NLB and setup by nodes so the NLB is enable on my LAN connection things still do not work

what the heck am I doing wrong
0
 
AkhaterCommented:
Not unicast and multicast, in the wizard where buillding your Nlb cluster on which nIC your enabling it ? can u share screenshots or something

I have done this about a couple of hundreds times
0
 
compdigit44Author Commented:
What a second are you telling me I have to setup unicast or mulitcast on the properties of the network card directly???
0
 
compdigit44Author Commented:
My NIC card is a muiltifunction HP Nc382i
0
 
AkhaterCommented:
No not at all...

what i mean is that, in the wizard, which NIC are you picking ? you said that the VIP is being added to the NIC that is not on your LAN, so it looks like you are enabling NLB on the HB nic
0
 
compdigit44Author Commented:
Here is my setup

NODE 1
LAN = 10.x.x.x
HeatBeat = 192.168.x.x

NODE 2
LAN = 10.x.x.x
HeartBeat = 192.168.x.x

The heat beat nic's are connect via an x-cable

In the NLB wizard, for the first sceen when adding NODE 1 I select the heart Beat network

THen on the cluster IP list in type in 10.x.x.x = static ip for virtual cluster ip

Port setting are set to default

When I do this I can ping the cluster ip from the cluster nodes only not other workstation can ping the cluster ip with this config
0
 
AkhaterCommented:
In the NLB wizard, for the first sceen when adding NODE 1 I select the heart Beat network



thei is what i mean on the wizard chose the LAN nic and not the Heart Beat one
0
 
compdigit44Author Commented:
I tried this but I still can not ping my virtual cluster IP I will try it again though
0
 
compdigit44Author Commented:
Which address NIC should I now select for the Cluster IP list
0
 
AkhaterCommented:
destroy your cluster and create it again and select your LAN nic add only one host till now. when you are done issue an ipconfig /all and give me the results
0
 
compdigit44Author Commented:
OK new cluster has been created as follows:

NODE 1
LAN = 10.x.x.x
HeatBeat = 192.168.x.x

NODE 2
LAN = 10.x.x.x
HeartBeat = 192.168.x.x


1) Added NODE1 to NLB using LAN NIC
2) Added Cluster IP to ip lister

I can ping the cluster name and Ip from other workstation - -WORKING but the heat beat is using the LAN connection
0
 
AkhaterCommented:
can u send me an ipconfig /all
0
 
compdigit44Author Commented:
UNfortuantly I can not

What do you need me to look for
0
 
AkhaterCommented:
Is the virtual ip on which nic ?
0
 
compdigit44Author Commented:
The virtual IP is a 10.x.x.x which is the same IP range for the LAN NIC on my NODE
0
 
AkhaterCommented:
ok so what is not working now ?
0
 
compdigit44Author Commented:
Everything is working...

The only problem is that my Heat beat NIC are not being used so the heart beat and cluster ip are using the same NIC's
0
 
AkhaterCommented:
what do you menan by this ?
0
 
AkhaterCommented:
your setup is correct now
0
 
compdigit44Author Commented:
but shouldn't I seperate my LAN and heart beat on two seperate nic

everything that I have read states this should be done yet I just cannot get it to work with to NIC on a software NLB
0
 
AkhaterCommented:
if u cross ur Heatbeat nic it won't work ?
0
 
compdigit44Author Commented:
correct!!!

I can only get the heat beat NIC to work I I give them a static ip on my the LAN subnet
0
 
AkhaterCommented:
you lost me in a previous message you said


OK new cluster has been created as follows:

NODE 1
LAN = 10.x.x.x
HeatBeat = 192.168.x.x

NODE 2
LAN = 10.x.x.x
HeartBeat = 192.168.x.x

0
 
compdigit44Author Commented:
sorry I was just trying to should you that my NLB is working but my Heat Beat cross Over connection is not beging used at all.

The cluster ip and heart beat are using the same nic using multicast which I have read can be done but is not recommend ant that 2 nic should be used

Yet I cannot get two nic to work . I can only get the heart beat nic's to work if I give them static ip's on the same LAN which mean's I will burn 4 static IP address on a two node NLB which is crazy!!!
0
 
AkhaterCommented:
THis is just the way it should be

just like i told you to do it
0
 
compdigit44Author Commented:
then why does Microsoft recommend having two NIC's?
0
 
AkhaterCommented:
well honestly you can remove the second NIC HeartBeat NIC are not longer a requirement since windows 2003 SP2
anyway if you want your HB traffic to go over the HB NIC you will need to edit the hosts files on the 2 servers so that each will resolve the name of the other on the private NIC
0
 
compdigit44Author Commented:
If I were to update the host file and rebuild by NLB would I chose the LAN or heart beat nic for the node's dedicated IP
0
 
AkhaterCommented:
i remove what i said last, the HB traffic will go over the NLB nic no matter what in windows 2008, so your other NIC is useless
0
 
compdigit44Author Commented:
for my own know ledge can so direct me to some articles that state what you mentioned above
0
 
AkhaterCommented:
yes of course sorry i should have linked

Heartbeat messages are transmitted over NLB Enabled NIC always whether you're operating cluster in Unicast or Multicast mode.

http://support.microsoft.com/kb/556067
0
 
compdigit44Author Commented:
So a single NIC that is not teamed it need for a 2008 NLB
0
 
AkhaterCommented:
Teamed should/would work however it is known to cause problems sometimes
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 41
  • 33
Tackle projects and never again get stuck behind a technical roadblock.
Join Now