|
"Bruno L. F. Cabral" wrote:
>
> good, it is the expected behaviour :)
good. :-)
> ok. I also figured out what I was doing wrong. Redhat 6.2 has TWO
> ipvsadm on the stock distribution.
this is starting to be a common problem ;-\
Horms,
You've changed the new LVS ipvsadm to complain bitterly if it's
working on the wrong ipvs?
> interaction for a few minutes, it will hang. is this normal?
> the commands that enable it
> ipvsadm -A -t 200.200.200.10:22 -s rr
> ipvsadm -a -t 200.200.200.10:22 -r 10.10.10.4:22 -m
telnet times out with lvs. If the problem with ssh has the same cause,
there's an idle timeout for tcpip connections, which you can change.
here's the posting from Julian
On Wed, 28 Jun 2000, Julian Anastasov wrote:
>
> Hello,
>
> On Wed, 28 Jun 2000, Dave Tyson wrote:
>
> > Hi,
> > I have just setup a LVS system to try and equalise the load of a group
> > of sun servers running Solaris 2.6. I have got LVS working fine (using
> > the 2.2.15 kernel and appropriate ipvs patch). I am using direct routing
> > with wlc and a weighting value to reflect the performance of each server.
> >
> > At present I am testing and have noticed that telnet sessions established
> > via LVS seem to timeout after about 15 minutes idle time. This does not
> > occur if I connect directly to one of the servers. There seems to be no
> > reference to this in the various FAQ's and notes. We definately would want
> > to alter this timeout value to something > 8 hours to avoid flak from
> > users.
>
> On the director:
>
> ipchains -M -S 36000 0 0
>
> 36000 is 10 hours TCP timeout. man ipchains. You can try
> with different value.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
