Re: [lvs-users] source hashing some times land on wrong server (with FTP

To: Phillip Moore <pdm@xxxxxxxxx>
Subject: Re: [lvs-users] source hashing some times land on wrong server (with FTP)
Cc: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Julian Anastasov <ja@xxxxxx>
Date: Wed, 6 Nov 2019 01:08:17 +0200 (EET)

On Mon, 4 Nov 2019, Phillip Moore wrote:

> We have a set of director hosts that are all active (running master and
> backup at the same time) BGP/anycasting their VIPS. Then using TUN mode to
> load balance separate real servers running the FTP server.
> It sounds to me from the documentation the backup_only is for when the real
> is the same server as director. But we aren't doing that.
> We had previously used WLC instead of SH for the lb agl but we had
> customers facing similar problems where connections to data channel would
> land on a different (and unprepared to handle it) FTP server. SH seemed a
> good fit since it only looked at the source IP so seemingly requests from
> the same client (regardless of src or dst port) would land on the same real
> FTP server for the data port.
> Thank you for your input and I would appreciate it if you can expand a
> little on if backup_only would help in this case.

        No, this flag helps the backup server to run as real server
by ignoring the steps that IPVS does to lookup and create connections.
The packets are simply passed to the local stack without any inspection.

        Note that if sh-fallback detects unavailable real server (even with
weight 0), the fallback is temporary - when this real server becomes
available again the traffic is switched back immediately, so at such
switching moments two commections can land in different servers.


Julian Anastasov <ja@xxxxxx>

Please read the documentation before posting - it's available at: mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to

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