NLB; attempting to add 2nd host and only seeing 1 of 2 interfaces

[mlchris2]

I have two Windows 2003 Server Web Ed - SP1 servers. Server a and b have two interfaces, configured as such;

server a:
NLB interface:
ip: 10.0.3.7
mask: 255.255.255.0
gateway: 10.0.3.1
DNS: 10.0.3.3

non-NLB interface:
ip: 10.0.3.8
mask: 255.255.255.0
gateway: 10.0.3.1
DNS: 10.0.3.3

server b:
NLB interface:
ip: 10.0.3.9
mask: 255.255.255.0
gateway: 10.0.3.1
DNS: 10.0.3.3

non-NLB interface:
ip: 10.0.3.10
mask: 255.255.255.0
gateway: 10.0.3.1
DNS: 10.0.3.3

NLB is enabled on server a & B NLB interfaces. NLB properties are as follows;

cluster ip: 10.0.3.11
mask: 255.255.255.0
internet name: cluster.domain.com (changed for security purposes)
Operation mode: unicast
Host Params-Priority: server a = 1, server b = 2
dedicated IP: server a = 10.0.3.7, server b = 10.0.3.9
mask: both servers = 255.255.255.0
default state: both server = started

Port rules: both servers = default settings.

******

Here is where I'm running into problems. On server a, I started NLB Manager. I created a cluster by adding server a, all is well so far. Then I attempted to add a host to cluster, in the connect box, I point to either the DNS name of server or the IP of the NLB interface of server b and all that appears in the Interfaces list is the non-NLB interface on server b.

I have gone as far as removing all the NLB settings from server b, restarted and attempted to add as another host to cluster.


I appriciate any help or ideas you can offer.



Mark C.

 

[mlchris2]

one other thing I just tested....

If I create a cluster on server b, I am able to see the NLB interface and the non-NLB interface. when I attempt to add server a as a host to the new cluster, I only see the non-NLB interace in the interface list.

Mark C.

 

[mlchris2]

I finally called Microsoft after a week of messing with this. The so-called Engineer said that Post-SP1 & SP2, there is a hot fix needed to enable the use of multip-adapter clusters. I found this bogus, as most of the Microsoft /TechNet documentation said it's better to manage your NLB cluster with a dual-adapter system.

So after much thought... I figured this out! Here's more info to help those that might come across this.

I originally Ghosted Server A to create Server B. Aparently when you do this the registry contains the same UID info on hardware from the original server. Network Load Balancing manager doesnt like this. (sorry I dont have the details just yet, I just know the basics). I uninstalled the NIC adpaters on Server B, restarted, setup TCP/IP properties and created the cluster again.... BAM!!! the NLB adapter appeared in the list when I added Server B as a node to the cluster.

now I have to figure out my complex cluster design to see if it is possible or not.



Mark C.