|
Hello,
On Wed, 27 Feb 2002, Michael Brannigan wrote:
> Julian,
>
> Thanks for this - I isolated it to some SQL flakiness, and I now have
> LVS/NAT directing 5 MSSQL boxes on Windows 2000, successfully....however...
> the connection times are very slow! if I have a realserver connect to
> another realserver, the connection happens in sub-second time.. however, a
> client machine on the other side of the LVS director experiences ~30 second
> connect times. What gives?
I'm not an expert in these apps but in the LVS history
the only known delays are from DNS resolutions and IDENT protocol
performed from the real servers.
30 seconds is an usual time for delay caused from IDENT.
OTOH, IDENT usually works with NAT if you correctly NAT all ports,
not only the port for the real service.
> RSs can ping client
> Client cannot ping RSs
> Director can ping both
> RSs trace to client via director
looks good
> Director kernel is 2.2.19, running ipvs 1.0.8
>
> Any ideas of things I should check for? Is my above scenario correct? I've
Looks correct
> followed the "quick" troubleshooters pretty carefully, but I'm still a linux
> newbie, so everytime I've twiddled things, I've broken the config and had to
> fallback on the configure script. Nothing is being saturated on the
> machine - bandwidth, ram, cpu -- all practically idle.
Try to trace all communications and to spot the problem,
may be there should be other traffic that is not handled.
> Thanks in advance,
>
> - Mike
Regards
--
Julian Anastasov <ja@xxxxxx>
|
