Win2003 Server configure NLB on HP DL320 G5

[Maaax]

Hi,
I've got a problem while trying to create NLB multicast cluster on 2 HP DL320G5 (2 NICs onboard).
When I'm adding second (remote) node to the cluster, I've _instantly_ got a message - there are now available interfaces to create cluster.

Node1 configuration
Public interface:
IP - 10.0.19.3
Mask - 255.255.255.240
GW - 10.0.19.1
DNS - 10.0.19.3

Private interface:
IP - 192.168.2.1
Mask - 255.255.255.240
GW - none
DNS - none

Node2 configuration
Public interface:
IP - 10.0.19.4
Mask - 255.255.255.240
GW - 10.0.19.1
DNS - 10.0.19.3

Private interface:
IP - 192.168.2.2
Mask - 255.255.255.240
GW - none
DNS - none

NLB IP - 10.0.19.2
Mask - 255.255.255.240

Private interfaces are interconnected through X-over cable.
Public interfaces are interconnected through Cisco 3750 switch.

Both public interfaces are in one VLAN. Static MAC for NLB IP address had setup on Cisco switch.

Can you help me to find out the root of the issue?
It's in Cisco, HP server, Windows or just a misconfiguration?

[Paul Slijkhuis]

Not clear what your error message is; available interfaces - isn't that what you wish to have?
I do not recommend DNS server to be part of the cluster (node 1=DNS). Yuo should check if everything resolves okay. Also check that the network interface priority is set correctly. Just follow any Windows cluster config guide and you should be fine.

- Paul

[Rune J. Winje]

Hi,
I think you have misunderstood something here.

A Windows Server cluster (MSCS) is 2-8 nodes connected to the public LAN and also having a private (heartbeat) LAN. In the case of only two nodes one can use a crossover cable for the private LAN.

A NLB cluster on the other hand has 1-32 nodes but does not use the same type of private LAN. It instead has a dedicated IP for management purpose that normally should be reachable from a managent PC, and one or more public IP addresses that are load balanced between these servers. Typically used for web services, terminal services or media streaming. NLBMGR is the preferred tool to configure NLB clusters.

http://support.microsoft.com/kb/323437


Also I wonder about the "static MAC for NLB IP address" ? Be aware that changing from unicast to multicast will change the MAC address... so this static config may be a contributing problem.

Also make sure you do not have network teaming on any interfaces, since the heartbeat of the NIC team will often be in conflict with NLB heartbeats.


Cheers,
Rune

[Rune J. Winje]

See also the end of this sample book chapter I found for NLB setup step by step

http://www.syngress.com/book_catalog/301_BD_W2k3/sample.pdf


Cheers,
Rune