Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

how do you set Netwrok Load Balance with 2 NICS?

Status
Not open for further replies.

fpower

MIS
Aug 12, 2003
54
US
Hello all,
I am having some trouble with NLB and hope someone could help. I had an internal web server, (insideweb.mycomany.com, ip=10.120.1.53, one to be accessed from internal users only), that I needed to 'cluster', so I did the following.
1.since insideweb is an HP DL360 with raid 1, I pulled a drive and 'cloned' a new identical server in a new DL360.
2.renamed the 'cloned' server to web3 and ran changesid application, then uninstalled and reinstalled nics, ip=10.120.1.76
3.renamed insideweb to web2 with new ip=10.120.1.75 -- I did this b/c I need to keep the insideweb and IP 10.120.1.53 as the cluster.
4.tested access to the web servers before clustering and things worked fine -- i did this by manually accessing web apps on each individual web server
5.nic 1 on web2 has ip=10.120.1.75 and nic2 ip=172.0.0.1 -no default gateway
6.nic 1 on web3 has ip=10.120.1.76 and nic2 ip=172.0.0.1 -no default gateway
7.crossover cable connected to nic2 on both servers
8.now I started to configure cluster, I went to web2 and ran nlbmgr, then went to cluster, then NEW and entered the cluster IP info, 10.120.1.53 255.255.0.0 and full name, insideweb.mycompany.com
9.selected multicast, but NOT IGMP multicast
10. clicked next until I got to the Connect to one host that is to be part of the cluster screen, here I added the local server, (web2) ip address of 10.120.1.75 and then clicked connect
11. in the interfaces available box both interfaces were displayed, I selected 10.120.1.75 and gave it priority 1
12. tried to add the second server, web3, and looked good until the converging, when it said UNABLE TO COMMUNICATE WITH SERVER WEB3
13. pinged web3 from web2 and got a reply from the 172 nic, not the one all clients reach
14. added a host file to each server to point to 10.120.1.75 and 76, this allowed the nlbmgr to complete the convergace without the error UNABLE TO COMMUNICATE WITH SERVER

things seem to be working, but this can not be the correct way of doing it. I have looked through microsofts documentation and am becoming more confussed.

If anyone could please correct me where I made my mistake(S)... I am greatful for any assistance.

Thanks in advance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top