|
Hello list,
As the subject mentioned, I'm trying to load balance a couple of Windows
Server 2008 web servers using LVS. I've read through the documentation for
setting up a load balanced setup on the LVS site and on the Ultramonkey
site. Most of the documents assume I'll be using NAT, which I am not. I need
the director and the web servers to be on the same network segment, so I'm
using direct routing.
I've read about the ARP issues on Windows systems, and have created the
loopback adapter on the Windows systems. The steps seem to be roughly the
same as Windows 2k and 2k3 were, with just a few small differences in the
IIS portion.
I believe I have a ldirectord.cf setup that should work, but thus far,
nothing is working. Here's the config I'm trying to use:
******************************************
checktimeout=10
checkinterval=2
## HTTP
virtual=192.168.108.252:80
real=192.168.108.245:80 gate
real=192.168.108.246:80 gate
service=http
checktype=connect
scheduler=rr
protocol=tcp
## HTTPS
virtual=192.168.108.252:443
real=192.168.108.245:443 gate
real=192.168.108.246:443 gate
service=https
checktype=connect
scheduler=rr
protocol=tcp
******************************************
I've tried to keep is as simple as possible. Once it's working, I'll change
the connecttype and scheduler settings around. For now, I just need to get
this working to test it out.
So, I have the director system set up as 192.168.108.252, and the 2 web
systems are 192.168.108.245 and 192.168.108.246. They both have loopbacks
set up and configured as 192.168.108.252 with a subnet of 255.255.255.255
(this seems to take on Windows 2008 now).
Running ipvsadm -ln on the director shows this output:
IP Virtual Server version 1.0.8 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.108.252:443 rr
-> 192.168.108.245:443 Route 1 0 0
-> 192.168.108.246:443 Route 1 0 0
TCP 192.168.108.252:80 rr
-> 192.168.108.245:80 Route 1 0 0
-> 192.168.108.246:80 Route 1 0 0
So, looks good. However, trying to connect to 192.168.108.252 results only
in a timeout. While waiting for it to connect, the output of the same
command looks like this:
IP Virtual Server version 1.0.8 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.108.252:443 rr
-> 192.168.108.245:443 Route 1 0 0
-> 192.168.108.246:443 Route 1 0 0
TCP 192.168.108.252:80 rr
-> 192.168.108.245:80 Route 1 0 0
-> 192.168.108.246:80 Route 1 0 1
So, it's trying to connect.. it's just not able to for some reason. I'm at a
loss on what to try next.
A few other notes:
- net.ipv4.ip_forward =1 is set in the sysctl.conf file on the director box.
- I've disabled the firewalls on both Windows systems.
- iptables is disabled on the director box, just in case.
- IIS is running on both web servers, and can be reached from the director
box just fine in a browser.
Any ideas on what I could try from here?
Thanks in advance!
~Brandon
--
View this message in context:
http://www.nabble.com/Load-balancing-with-LVS-and-Windows-2008-tp17537850p17537850.html
Sent from the LVS mailing list archive at Nabble.com.
|
