LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Problems With LVS-TUN and Windows 2000 Realserver... is it possible?

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Problems With LVS-TUN and Windows 2000 Realserver... is it possible?
Cc: bshellrude@xxxxxxxxx
From: Roberto Nibali <ratz@xxxxxxxxxxxx>
Date: Mon, 14 Jan 2002 12:26:10 +0100
Hi Ben,

> Basically this was the best solution I could find out there to try,
> if anyone has any suggestions if there's maybe a more suitable
> project for the situation, please let me know.

I'll try.

> The client wants to have a firewall running in front of this windows
> 2000 box.   But, they also have a co-located box running from

It's too cold in Manitoba to run W2k anyways.

> another connection somewhere else in Canada.  They want the box we
> host to be the primary server, and that in the event that it fails,
> for the director to redirect requests to the secondary box.
>> From what I've read this can be achieved using the wlc algorythm,
>> Tunneling
> and setting a huge weight on the primary system. What I am having

No, setting a huge weight is not a very good idea, specially not if you're using persistency. Once the server get's the hit (latest after 65535 requests) the next packet will travel all through Canada to the spare system you actually only wanted to use in case of an emergency. And as others said, tunneling is not feasable with Win2k.

> troubles with is getting the requests to get past the director to
> the windows box, from what I've read I'm not even sure that this is
> possible? I have set up the following, once it works I will be
> putting the real server behind the director on non routable network
> with extra interface attached to the public side, but for the time
> being I just need to get it working.

Let's take another approach. Can you tell me how your requirements for knowing when the first system is not reachable anymore and how much the maximal sytem downtime and failover to the new system can be? I think of writing a little (100 lines of code or so) shell script to flush the table in case of a down status, flush the original table and set up the new one. Can be done really fast, believe me. It's cheating but works and the customer doesn't know that.

> Show's the connection as being inactive. I'm assuming that my
> problem lies with the Windows box. But there must be a patch or
> project somewhere out there or someone who's dealt with a similar
> problem before.
>
> If someone could help it would be GRRRRREATT!

No problem, eh? Haven't the Brandon Wheat Kings frozen to death yet? :)

Best regards,
Roberto Nibali, ratz




<Prev in Thread] Current Thread [Next in Thread>