Windows Server 2008 R2 Enterprise
Virtual Network –
Application Server 1
Application Server 2
Preparing Environment/Prerequisite’s –
First we need to Install Network Load Balancing on the Node 1 and Node 2 Servers. To do that go to Server Manager and direct to Features. click add feature and select Network load balancing on the add new feature wizard, then get it installed by following simple steps.
Installation of NLB feature on both NLB nodes
This should be done on ALL NODES in the NLB Cluster. In this case we are performing this installation on APP01 and APP02
Open Server Manager, you can open this several different ways in Windows Server 2008. Probably the quickest way to open Server Manager is to right click “My Computer” and choose “Manage”, another way is open “Control Panel” go to “Program and Features” and select “Turn Windows features on or off”. A third way to open it is “Server Manager” option under Administrative Tools.
Select “Features” from the Server Manager menu on the left
Press “Add Features”
Select the checkbox next to “Network Load Balancing”
Installation will proceed to install the necessary components
NOTE: Network Load Balancing may also be installed from a command prompt with elevated privileges (right click on the command prompt in the Start menu and select Run as administrator) by running the servermanagercmd -install nlb command.
C:\Windows\system32>servermanagercmd -install nlb
[Installation] Succeeded: [Network Load Balancing].
Success: Installation succeeded.
In this example both servers only have one network card. If you have multiple network cards you will still be able to load balance the 2 servers. You need to configure one NIC per server for NLB, both NIC’s should be on the same VLAN and be they should able to contact each other.
Once it installed, go to administrative tools and open up NLB on Node 1.
Right click on Network load balancing cluster and press New cluster.
In New Cluster Wizard you have to provide Host IP Address for the 1st Node of the cluster and press connect.
here I have used KFX-APP01 as Node 1.
In next box leave the priority as 1, also other areas as default.
Add New cluster from this window. Here we defining the Cluster IP which act as Central IP.
This will be the identification of the particular cluster
Across the network, so we have to provide an New IP for this guy.
so we have to provide an New IP for this guy and click OK.I used below IP as my Cluster IP.
This IP will use to identify the particular cluster By IP Across the network.
It will automatically pickup your Cluster IP, here needs an Full Internet Name for it.
Provide an Name for the cluster and select Operation Mode as well.
This name is used to identify the cluster by name Across the network as well.
It will show up completion summary window. click finish to complete.
We have now successfully added our 1st Node to our new cluster.
Give it a moment until status become converged .
Next to add our 2nd Node to cluster. For that simply right click and say “Add Host to Cluster”.
Provide the details for the Node 2 below areas as previously we done for Node 1. here I have used KFX-APP02 as my 2nd Node.
It will pickup priority automatically. So I’m leaving It to be 2nd. And click next
Click Finish to complete.
Give it a moment until new Host become converged in this stage also.
Both Servers are added successfully and our new guy is ready to rock and Roll !!!!!!.
Then we need to create an Host, Pointer (PTR) Records on DNS server for our new Cluster.
Expand your Domain as above and Right click on domain in Forward Lookup Zone. Press “New Host A (AAAA) to create a new Host Record and Check create associated PTR record box as well, Checking this box will automatically create Pointer PTR record in Reverse lookup Zone once you created
Host Record.(Provide the Cluster name and IP address you created in NLB creation earlier)
You will see PTR Record created at reverse lookup zones once you created your new host as below.
That’s all on Configuration
You can test the availability of the DNS Records across the network by pinging to the cluster IP/FQDN. (192.168.154.6 / KFX-APP.MSTEST.COM)
· Forward/Reverse Lookup zones to be created on DNS for particular Virtual network if you are Using Virtual network for the Virtual Machines,
I have done the same here.