Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 305
  • Last Modified:

Load Balancing IIS on Windows 2003 Server

I have never done IIS load balancing before and would like to know how to get into setting this up using 2 x Windows 2003 servers.

Do I need special switch hardware or does the OS do everything itself? I have read something in a "Technical Overview of Clustering in Windows 2003 Server" doc from Microsoft - they write somehting about IGMP support that will do that only traffic for the NLB cluster is sent tot those servers and not all other servers in the same switch. Is this correct and should I be aware of somthing here?

How can I get startet here? I look forward hearing from anyone that has successfully done Windows 2003 Server NLB in real-life.
0
Jakob Adeltoft
Asked:
Jakob Adeltoft
  • 7
  • 6
1 Solution
 
Dave_DietzCommented:
OS does everything itself.

I would suggest plugging the Load Balanced NICs on the machines into a hub and them go from the hub to the switch.  This can avoid some issues with certain switches.

In any case, all you have to do is enable and configure Network Load balancing on both machines.

Please see the following articles for assistance in configuring NLB:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323431
http://support.microsoft.com/default.aspx?scid=kb;en-us;323437

Dave Dietz
0
 
Jakob AdeltoftAuthor Commented:
Thanks for the info. Should it be a hub and not a switch? Or does it matter?

Should the 2 servers be configured with the same IP address, or do they need to different IP addresses? In case of different IP adresses, how will www.domain.com know what server to contact? I could make a round-robin DNS, but then the NLB isn't of much use...

0
 
Dave_DietzCommented:
Hub will generally work better but a switch should also work.

They should have the same IP address.  :-)

Dave Dietz
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Jakob AdeltoftAuthor Commented:
A hub is best in NLB setup, right? But else we can agree that a switch is much better in assigning packages to each machine, right? A hub will send packages to all ports, even if itøs only intented for one machine...
0
 
Dave_DietzCommented:
You are correct.  In most cases a switch is actually preferable.

With load balancing there are some switches that get confused by having two (or more) ports with different MAC addresses showing the same IP address and can end up disabling one (or more) of the ports and rout all the traffic to only one machine.

Hubs happily forward packets to all downstream connections without question.

Dave Dietz
0
 
Jakob AdeltoftAuthor Commented:
Ok, then I'll find a hub to do the work :-)

I'm also running FTP application (not MS) on these 2003 servers. Can NLB also be done so uploads are distributed between the 2 servers or is this another solution approach? I'm using Serv-U.
0
 
Dave_DietzCommented:
As long as you have Single or Class C affinity configured FTP should do fine in a Load Balanced scenario.  :-)

Dave Dietz
0
 
Jakob AdeltoftAuthor Commented:
Can you explain that in English? I don't have a clue about what Single or Class C affinity are?
0
 
Dave_DietzCommented:
In the NLB properties in Port Rules Affinity is a property set to None, Single or Class C.

None - each request from a client on the same port is directed to the same server
  - A session for port 80 will always go to the same machine, but a new request to port 21 may go to a different server
Single - Each request from a given client to the same server
  - All sessions from this client will go to the same machine
Class C - Each request from a machine in the given Class C Subnet will go to the same machine
  - Same as single but for a Class C range instead of a single IP, usefule for clients behind proxy arrays where their proxy's IP may change

Dave Dietz
0
 
Jakob AdeltoftAuthor Commented:
Concerning "none" - How do the NLB know what users are the same? By IP, Mac address (not over Internet?), IIS Session (we don't use these)?

Why can't FTP work in "none" mode? I don't care if one upload is for server #1 and the seond upload is for server #2 as the uploaded files are stored the same place anyways...

With every solution (none, single, class c) the user are always stuck on the same server in one or another way - but what if the server does not respond - then I assume that all requests will aut. be redirected to another server, and the user will not experience anything?
0
 
Jakob AdeltoftAuthor Commented:
Hi Dave,
Have you had a chance to review my additional questions regarding to the Port Rules Affinity for NLB, that I did not understand?
0
 
Dave_DietzCommented:
Sorry, been busy.....

All affinity is based on IP addresses and Port numbers. I'll rephrase what I had above:

None - each request from a unique IP address on the same port is directed to the same server
  - A session for port 80 will always go to the same machine, but a new request to port 21 may go to a different server
Single - Each request from a unique IP addresses regardless of Port is sent to the same server
  - All sessions from this client will go to the same machine
Class C - Each request from an IP address in a given Class C Subnet regardless of port will go to the same machine
  - Same as single but for a Class C range instead of a single IP, useful for clients behind proxy arrays where their proxy's IP may change

The reason FTP won't work with none is that FTP depends on port 20 as the command channel and 21 (Active) or a port above 1024 (passive) as the data channel.  With None affinity these ports might end up on different servers which would fail.  You would have to use either Single or Class C to make sure that both ports used for FTP are assigned to the same server.

You are essentially correct on the third point.  You users might see a disruption if they are actively performing some sort of data transfer at the time of failure but their next request would be directed to a different server.

Dave Dietz
0
 
Jakob AdeltoftAuthor Commented:
This means that no matter what affinity I'm using, I'll have ALL users from same IP address on the same server? I deal with several large customers that uses our webbased system running on IIS. They are between 100-500 users behind the same IP address - they will all go to the same server, right? Then Windows 2003 NLB isn't of much use...Is this correctly understood?
0
 
harleyjdCommented:
Sorry for the ping guys - this is a bit over my head. I *think* the original question is answered, but I'd like to be sure...

Please let me know what you think...
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now