tlamonia,
From the information I have been able to gather, NLB works by sending traffic to a virtual IP shared between the NLB member servers, but the session state is based on the source IP address. If all of the users connecting to my web servers are all NAT'd at source to a single IP address, the first server that they are sent to as they pass through NLB will then be the server that everything from that IP address is sent to.
If that server dies, NLB will handle that and send all subsequent sessions to another server in the NLB pool, but the same thing will happen - the first server that the first connection hits will be the same server that all subsequent connections are sent to.
This setup gives me resilience in the event of server failure, but what it doesn't give me is any form of load balancing whatsover. It doesn't matter how many servers I have in my NLB pool, only one is ever being used which removes my ability for capacity management.
Please let me know if any of my assumptions here are incorrect, but nothing I've been able to find either via information sourced on the Net, or as a result of all of the testing I have done, has shown me anything other than the above - once an IP address hits one server under NLB that's the server any subsequent traffic from that same address will go to.
Thanks.
Main Topics
Browse All Topics





by: tlamoniaPosted on 2007-09-29 at 19:04:44ID: 19985941
Rob,
Sounds like your NLB config is not setup correctly. The source IP shouldn't matter, it's the NLB virtual IP that matters in this case. Please reply with more info about your NLB setup.
-Todd