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

NLB clustering issues and how to test whether NLB is working

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

NLB clustering issues and how to test whether NLB is working

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

I actually posted this on sql server forum but was asked to post it here to be more specific.


I am trying to configure NLB cluster on my virtual machine's(node1, node2) so that I can install
my report servers on the nodes and do scale out deployment. I tired to create the NLB
cluster, Here are the steps I followed:


1. Enabled the NLB feature on 2008 OS on both the nodes.
2. Open NLB connection manager on NODE 1 and Right click on the cluster and create new.
I specified the same node1 as Host and entered it's dedicated IP address and click next
3. priority is 1 and default state is "started"
4. ADD new cluster address, specify cluster IP address, I used a new IP address
5. give full internet name and click next
6. Allow on all ports.
7. disabled firewalls on both the nodes.
8.check in the NETWORK Load balancing property on node 2, before adding it to the cluster.
network Connections--> right click on Local area connection -- properties
check NLB property.(this step did not go well, I had to reconfigure server several times
the remote connection to the server was lost several times(do not know why it happened, it only happened when I checked in the NLB property) and it worked at last).
7. Now, I added the NLB cluster IP address to the TCP/IP properties of the node2.
8.On node1,I added new host to the existing cluster, I was able to add the node but the status of the node 2 was "Unknown"(for node1 the status is "converged" but for node2 the status is "unknown")


Do not know why the status is unknown, is it something misconfigured?, I am sure the status has to be "converged". Interestingly, if the check the NLB status in the nlb manager on the other node both of them are converged but on node1 it is converged for one and unknown for the other(node2). Refreshed many times and droppped and added it back again, but still no change.


Also, I do not know how I can test the NLB cluster whether it is working or not. I install reporting services and made the changes the microsft has suggested to access the reports from the nlbcluster IP address, when I browse using NlBcluster IP address, it prompts me for username and password and after that it displays a white page. I do not know whether the NLB is working or not. how do I check it??Is there anyway to test whether NLB is working or not?


any help is greatly appreciated.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

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

Re: NLB clustering issues and how to test whether NLB is working

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

First of all I really recommend that you use Hyper-V instead of ESX...

Here is what I found for configuring ESX to work properly with Microsoft NLB:

Configuring Multicast Mode

You do not need to take any special steps to configure your ESX host when you are using multicast mode.

Configuring Unicast Mode

This procedure helps prevent RARP packet transmission for the virtual switch as a whole. This setting affects

all the port groups that use the switch. You can override this setting for individual port groups using the

instructions in



“To Prevent RARP Packet Transmission for a Port Group” on page 3.

To Prevent RARP Packet Transmission for a Virtual Switch

1 Log on to the VI Client and select the ESX host.

2 Click the



Configuration tab.

3 Choose




Networking and, for the virtual switch, select Properties.

4 On the




Ports tab, select the virtual switch and click Edit.

5 Click the




NIC Teaming tab, set Notify Switches to No.

6 Click




OK and close the vSwitch Properties dialog box.

Complete the following steps to prevent RARP packet transmission only for an individual port group. This

setting overrides the setting you make for the virtual switch.


To Prevent RARP Packet Transmission for a Port Group

1 Log on to the VI Client and select the ESX host.

2 Click the



Configuration tab.

3 Choose




Networking and, for the virtual switch, select Properties.

4 On the




Ports tab, select the port group and click Edit.

5 Click the




NIC Teaming tab, set Notify Switches to No.

6 Click




OK and close the vSwitch Properties dialog box.


--------------------------------------------------------------------------------
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

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


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: Google [Bot], Google Adsense [Bot] and 12 guests