Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

NLB issue

Posted on 2009-04-14
9
Medium Priority
?
2,424 Views
Last Modified: 2012-05-06
We have two nodes on NLB, pub ip is 203.38.180.208 and 209. The cluster IP is 203.38.180.219. The management (local) IPs are 10.0.12.41 and 42 respectively.

When I connect to the NLB, i get the error "Host unreachable, error connecting to "uwc-web2", which is 10.0.12.42. When I try to ping this IP from 10.0.12.41, i get timed out error messages. Is this normal or should they be able to ping each other?

How can I confirm if NLB is doing load balancing?
0
Comment
Question by:Network_Padawan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 26

Expert Comment

by:lnkevin
ID: 24208133
....Is this normal or should they be able to ping each other?
You should be able to ping from one to other with the management IP or DNS name if DNS is set up. If not, try to ping the 10.0.12.42 and vice versa

If your host don't see each other, some thing goes wrong with the switch and connections. You can try to open Network Load balancing manager, right click on the cluster --> Control Hosts --> Stop then Start.

How can I confirm if NLB is doing load balancing?
On the two nodes, open performance manager and add network performance manager for the NICs that host 203.38.180...

From a client in the network, open command line and type:
ping 203.38.180.219 -L 10000

Analyze the performance monitor, you will see the load will be splited to the two nodes, each carries 5000

K
0
 

Author Comment

by:Network_Padawan
ID: 24213656
Thanks Inkevin, ill check that out
0
 

Author Comment

by:Network_Padawan
ID: 24238870
Okay, the switchports were incorrectly set. I can now ping both server from the management IPS,

10.0.12.41 and .42 and visa versa.

On the server 203.38.180.209, it sees both nodes successfully.

On the other server, 203.38.180.208, no luck. Still says it can not see the other node. Restarted...no luck. It can ping both IP and hostname.

What else can I try?
0
Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

 

Author Comment

by:Network_Padawan
ID: 24239034
"On the two nodes, open performance manager and add network performance manager for the NICs that host 203.38.180..."

Did you mean performance monitor??? How do I access performance manager?
0
 
LVL 26

Expert Comment

by:lnkevin
ID: 24241026
Performance Monitor, I meant.

K
0
 
LVL 26

Expert Comment

by:lnkevin
ID: 24241066
On the other server, 203.38.180.208, no luck. Still says it can not see the other node...

Since you can ping it, what do you mean cannot see...?
Can you open NLB Manager on .208? If you can open NLB, try to add other node. It rarely sees other node by default. You must add it on NLB every time. If you have 3 or 4 nodes, you just need to add one node and others will show up automatically. It's a bug from MS.

K
0
 

Author Comment

by:Network_Padawan
ID: 24246602
Hi Inkevin,

Therein lies my issue. I can ping it from both ends no problem. on the .209, i can successfully add the other node.

On .208, it says it can not find the other node. Its wierd.

Im thinking about rebooting the server completely and see if that does the trick, cause the stop and start commands do not help.
0
 
LVL 26

Accepted Solution

by:
lnkevin earned 2000 total points
ID: 24250790
After reboot your servers, on the .208 when you successfully added the other node, right click on the cluster node look in the options for Control hosts and stop then start. Make sure you always reboot one physical add a time and wait until it comes up successfully before reboot the other. If you have to schedule an automatic reboot, make sure they are 15 minutes apart. You still have to stop and start the nodes in NBL clustering manager to ensure all nodes are available. I have learned a great experience from doing this.

K
0
 

Author Comment

by:Network_Padawan
ID: 24275906
Thanks Inkevin Ill do that and post back what happened
0

Featured Post

Q2 2017 - Latest Malware & Internet Attacks

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out our latest Quarterly Internet Security Report!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

INTRODUCTION The purpose of this document is to demonstrate the Installation and configuration, of the HP EVA 4400 SAN Storage. The name , IP and the WWN ID’s used here are not the real ones. ABOUT THE STORAGE For most of you reading this, you …
In this article, we’ll look at how to deploy ProxySQL.
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question