Greetings

I have setup the LVS based on LVS-NAT configuration. When outside host tries to access the Real Servers than they are going through the Virtual IP successfully. When Real Servers originate the traffic to the outside host than it is not going through the Virtual IP. On my router i see that the traffic is coming from the IP of Real Host. Does anyone help in this regard. I want the every traffic coming in or going out must go through the Virtual IP.

Mansoor

From: [EMAIL PROTECTED]
Reply-To: [email protected]
To: [email protected]
Subject: lvs-users Digest, Vol 50, Issue 11
Date: Mon, 12 Mar 2007 12:00:03 +0100 (CET)

Send lvs-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.in-addr.de/mailman/listinfo/lvs-users
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lvs-users digest..."


Today's Topics:

   1. Re: Quiescent server connections (Adrian Chapela)
   2. Re: Quiescent server connections (Janusz Krzysztofik)



From: Adrian Chapela <[EMAIL PROTECTED]>
Reply-To: "LinuxVirtualServer.org users mailing list."<[email protected]> To: "LinuxVirtualServer.org users mailing list."<[email protected]>
Subject: Re: Quiescent server connections
Date: Mon, 12 Mar 2007 08:36:54 +0100
Ben Hollingsworth escribió:
OK, so I've got my setup nailed down pretty well.  This is pair of squid
web proxies on a 2-host LVS running UltraMonkey / HB 2.0.7-8 on RHEL4
(2.6.9).  I'm struggling with one more thing, though.  With
quiescent=true, if I shut down squid on one box, connections from new
hosts fail over to the other box just fine, but connections from
persistent hosts keep going to the same, dead box.  I realize this is as


OK, to solve the problem there are two variables:

/proc/sys/net/ipv4/vs/expire_nodest_conn --> to expire connections before the protocol timeout. This is to solve the problem when a server goes down. For example in the UDP protocol the protocol timeout is too high.

/proc/sys/net/ipv4/vs/expire_quiescent_template --> this variable I think is the variable to solve your problem. With this you timeout your persistent template when a server goes down.

I don't know what them makes exactly but the first solve my problems. You could make a test.

Best regards.
intended.  If I set quiescent=false, all client communication with the
dead box ceases immediately, which includes cutting off active
connections at the knees.  That's not an issue if the squid actually
dies.  However, most of our failovers will be due to my own planned
maintenance.  In that case, I'd like to allow existing connections
(which may be lengthy downloads) to finish before sending new requests
(even from persistent clients) to the live box.  I can't find any way to
do this without hacking the kernel to match a 2-yr-old patch that Horms
published (assuming that even applies to my setup).  Most of the info
about this seems to have been written three years ago.  Is there a way
to make this work without a custom compile?

------------------------------------------------------------------------

_______________________________________________
LinuxVirtualServer.org mailing list - [email protected]
Send requests to [EMAIL PROTECTED]
or go to http://www.in-addr.de/mailman/listinfo/lvs-users







From: Janusz Krzysztofik <[EMAIL PROTECTED]>
Reply-To: "LinuxVirtualServer.org users mailing list."<[email protected]> To: "LinuxVirtualServer.org users mailing list."<[email protected]>
Subject: Re: Quiescent server connections
Date: Mon, 12 Mar 2007 11:33:39 +0100
Dnia sobota, 10 marca 2007 00:24, Ben Hollingsworth napisał:
> OK, so I've got my setup nailed down pretty well.  This is pair of squid
> web proxies on a 2-host LVS running UltraMonkey / HB 2.0.7-8 on RHEL4
> (2.6.9).  I'm struggling with one more thing, though.  With
> quiescent=3Dtrue, if I shut down squid on one box, connections from new
> hosts fail over to the other box just fine, but connections from
> persistent hosts keep going to the same, dead box.

I have one solution, but it works only in case of transparent proxy setup.
Instead of persistance, use lblc scheduler (without persistance). lblc itself gives you some kind of persistance of 6 minutes or more. If 6 minutes is not
enough for you, please look here:
http://kb.linuxvirtualserver.org/wiki/Talk:Locality-Based_Least-Connection_Scheduling

Cheers,
Janusz






_______________________________________________
lvs-users mailing list
[email protected]
http://www.in-addr.de/mailman/listinfo/lvs-users

_________________________________________________________________
MSN Hotmail is evolving - check out the new Windows Live Hotmail http://get.live.com/betas/mail_betas

_______________________________________________
LinuxVirtualServer.org mailing list - [email protected]
Send requests to [EMAIL PROTECTED]
or go to http://www.in-addr.de/mailman/listinfo/lvs-users

Reply via email to