Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

How to properly configure NLB cluster in Windows 2008

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

How to properly configure NLB cluster in Windows 2008

Postby guest » Thu Jan 12, 2012 1:11 pm

I have just tried to configure 2 node Windows 2008 NLB cluster and I run into problem.
Until now I have successfully installed Windows Server 2003 NLB clusters. I used 2 nic per node and unicast mode.

For example

Node1 Node2
Pub Interface (default) Pub Interface (default)
IP:192.168.1.11/24 IP:192.168.1.12/24
GW: 192.168.1.1 GW: 192.168.1.1


NLB Interface* NLB Interface*
IP:192.168.1.12/24 IP: 192.168.1.13/24
GW:- GW:-

*DNS registration, File Share client and server, NetBIOS over TCP/IP disabled on this interface.

After configuring IP addresses I would run NLB manager and configure cluster in unicast mode.


When I tried this on Windows Server 2008, I could not access NLB address outside local subnet. Only when I configure DEFAULT GATEWAY on both NIC's, NLB started working.

When I run network monitor I notices that in this configuration, Windows 2003 would always respond using Public LAN (source MAC address would be from public NIC), no matter if i tried to connect to Public or NLB IP address.

In Windows 2008 if I tried to connect to Public IP, response packet would had source MAC address from Public NIC and when I accessed NLB address then source MAC would be from NLB NIC. For me this looks like change from 2003.

So how do we correctly configure unicast NLB cluster with 2 NIC's in Windows Server 2008? Do we just add default gateway to NLB NIC?
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9508
Joined: Mon Nov 27, 2006 1:10 pm

Re: How to properly configure NLB cluster in Windows 2008

Postby guest » Thu Jan 12, 2012 1:12 pm

After some research on the Internet, reading, thinking and long hours of playing with settings, I found only ONE configuration that works for me!

Actually, we faced two troubles with NLB since the beginning of testing:
1) "could not access NLB address outside local subnet"
2) could not access NLB at all when two nodes were off and then we enable one on windows 2008



Key points of working configuration:

•Specify gateway on the dedicated network interface for NLB on Windows Server 2008 node
•When using Hyper-V and Windows Server 2003 as a Child Partition, use Legacy Network Adapter with static MAC address of NLB Virtual IP


If you are interested in our setup, please find all details below.


In terms of hardware, we use two HP Proliant DL 380 G5 with two E5310 CPU and 4GB each. These boxes have 2 network adapters on board (NIC1, NIC2 for the first box and NIC3, NIC4 for the second one).

As for software, we installed Windows Server 2008 Standard 64 bit with Hyper-V role on both machines. Now in Microsoft (MS) terminology we should refer to Windows Server 2008 instances as to Parent Partitions (PP1 for the first box and PP2 for the second one). We created a Virtual Machine (VM) with Windows Server 2003 R2 Standard 32 bit and run it as a Child Partition on every server (CP1 on PP1 and CP2 on PP2). In total, there are two Windows Server 2008 PP and two Windows Server 2003 R2 CP.

We configured CP with 4 virtual CPU and 2 GB of RAM. All latest MS updates are installed. HP teaming is not present on PP.

Final working network configuration is as follows (network part of IPv4 addresses. IPv6 and MAC address except last digits were removed):



xx - single Class C subnet

DIP – Dedicated IP for NLB NIC

VIP – Virtual IP of NLB cluster

>ipconfig /all on PP1

Ethernet adapter Virtual LAN-V and LAN (xx.103 and xx.107):



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter #2 - Virtual Network

Physical Address. . . . . . . . . : xx-F6

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : xx::xx(Preferred)

IPv4 Address. . . . . . . . . . . : xx.103(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : xx.107(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : xx.1

DNS Servers . . . . . . . . . . . : xx.101

xx.111

NetBIOS over Tcpip. . . . . . . . : Enabled



Ethernet adapter FE NLB1 LAN (DIP xx.127 and VIP xx.117 with gw):

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter

Physical Address. . . . . . . . . : xx-75

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : xx.127(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : xx.117(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : xx.1

NetBIOS over Tcpip. . . . . . . . : Disabled



Note: The second hardware NIC HP NC373i Multifunction Gigabit Server Adapter #2 was used to create a bridge for virtual NIC HP NC373i Multifunction Gigabit Server Adapter #2 - Virtual Network to run CP1 (external connection type in Virtual Network Manager). Because we dedicated the first hardware NIC to NLB Unicast, we decided to share second hardware NIC for PP1 communications inside LAN and CP1 virtual network - that’s why we called it like Virtual LAN-V and LAN (xx.103 and xx.107). This trick is done by enabling only one bidding on the second hardware NIC – Microsoft Virtual Switch Protocol and configuring normal IPv4 bidding on NIC HP NC373i Multifunction Gigabit Server Adapter #2 - Virtual Network that is used as external connection type in Virtual Network Manager for CP1 as well. Legacy Network Adapter was used for CP1.



>ipconfig /all on PP2

Ethernet adapter LAN 10.110.62.101:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter
Physical Address. . . . . . . . . : xx-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : xx::xx(Preferred)
IPv4 Address. . . . . . . . . . . : xx.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : xx.1
DNS Servers . . . . . . . . . . . : ::1
127.0.0.1
xx.10
xx.123
NetBIOS over Tcpip. . . . . . . . : Enabled

Note: The second hardware NIC HP NC373i Multifunction Gigabit Server Adapter #2 is dedicated to CP2 and used as a bridge (we call it LAN-V Bridge) for virtual NIC HP NC373i Multifunction Gigabit Server Adapter #2 - Virtual Network (external connection type in Virtual Network Manager). So, only one bidding is configured on this hardware NIC – Microsoft Virtual Switch Protocol. To create dedicated virtual NIC, we un-ticked all bindings on NIC HP NC373i Multifunction Gigabit Server Adapter #2 - Virtual Network – so it can’t be used by host PP2! Legacy Network Adapter was used for CP2, as well.


FYI Please find good explanation of virtual networking with Hyper-V here - http://blogs.technet.com/jhoward/archiv ... works.aspx


>ipconfig /all on CP2

Ethernet adapter LAN xx.105:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
Physical Address. . . . . . . . . : xx-03
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : xx.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : xx.1
DNS Servers . . . . . . . . . . . : xx.101
xx.111

Ethernet adapter FE NLB2 LAN (DIP xx.128 and VIP xx.117): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Generic) Physical Address. . . . . . . . . : xx-75 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : xx.117 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : xx.128 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled

We installed web server (IIS) on all server instances, but we have special design requirement regarding NLB: need to load balance IIS7 on PP1 with IIS6 on CP2.

To sum up, we are configuring 2-nodes unicast NLB cluster with 2 NIC's on each server instance. One node is Windows Server 2008 Standard 64 bit Parent Partition (PP1) with Hyper-V role installed, another one - Windows Server 2003 Standard 32 bit running as a Child Partition (CP2) on another Windows Server 2008 Standard 64 bit Parent Partition (PP2) with Hyper-V box. We installed NLB feature on PP1 and NLB component on CP2.

Procedure of creating working NLB for thus particular scenario is as follows:

Using NLB Manager on PP1 we create standard unicast NLB with cluster Virtual IP - VIP xx.117. Take a note of the network address (MAC) of the cluster (xx-75) – we will use it to configure Legacy NIC for CP2. Then we connect to the 1st master node (PP1), select Ethernet adapter FE NLB1 LAN (DIP xx.127 and VIP xx.117 with gw) for NLB, then assign 1st host priority and dedicated IP - DIP xx.127. When the host is converged, we go to the properties of FE NLB1 LAN (DIP xx.127 and VIP xx.117 with gw) on PP1 and change them manually in the following way:

•Un-tick all bindings, leave only NLB and TCP/IPv4
•Specify gateway on the TCP/IPv4 properties (xx.1)
•On Advanced Settings, IP Settings tab un-tick Automatic metric and assign 20 as Interface metric
•On Advanced Settings, WINS tab Disable NETBIOS over TCP-IP
Go to TCP/IPv4 properties of the Ethernet adapter Virtual LAN-V and LAN (xx.103 and xx.107) on PP1 and un-tick
Automatic metric as well - assign 1 as Interface metric.

Shut down CP2 and go to settings of this VM on PP2. Go to Legacy Network Adaptor settings and change MAC address
from Dynamic to Static – specify it as network address (MAC) of the NLB cluster. Start CP2.

Then in NLB Manager on PP1 we add the second node – CP2. Select Add Host to the cluster and connect to the CP2, select Ethernet adapter FE NLB2 LAN (DIP xx.128 and VIP xx.117)for NLB, assign 2nd host priority and dedicated IP - DIP xx.128. When the host is converged, we go to the properties ofFE NLB2 LAN (DIP xx.128 and VIP xx.117) on CP2 and change them manually in the following way: •Un-tick all bindings, leave only NLB and TCP/IP
•On Advanced Settings, IP Settings tab un-tick Automatic metric and assign 20 as Interface metric
•On Advanced Settings, WINS tab Disable NETBIOS over TCP-IP
Go to TCP/IPv4 properties of the Ethernet adapter LAN xx.105 on CP2 and un-tick Automatic metric as well - assign 1 as Interface metric.



OK, it’s done now!

I tested connectivity using simple ping command from workstation on the same and different subnets – everything worked.

Testing – my scenario:

•disable NLB NIC on PP1 or CP2, and still can ping VIP (active node replies)
•disable remaining NLB NIC , and cannot ping VIP (both nodes are down)
•enable PP1 or CP2 (test both), starts pinging VIP (active node replies)
Hope my post could help someone with NLB on Windows Server 2008 and beyond :-)
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9508
Joined: Mon Nov 27, 2006 1:10 pm


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: Google [Bot] and 3 guests