From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio M. Di Nitto Date: Thu, 05 Nov 2009 08:23:59 +0100 Subject: [Cluster-devel] SCTP versus OpenAIS/corosync time-outs In-Reply-To: <20091104212941.GD32760@suse.de> References: <20091031002025.GS14882@suse.de> <4AEE9B47.6060206@redhat.com> <20091104212941.GD32760@suse.de> Message-ID: <4AF27D8F.9090207@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Lars Marowsky-Bree wrote: > On 2009-11-02T08:41:43, Christine Caulfield wrote: > > A quite different trick for redundant networking would be to assign > static addresses to lo:X and run OSPF over all links, and having DLM > connect to the static IPs. That's quite trivial to setup, give us > "resilient" TCP (w/o needing to mess with SCTP, bonding, or anything). > > Comments? > OSPF timings to converge networks can be very long as it involves link UP/DOWN events, flapping protection and so on and so forth... IMHO, while the idea is valid, it introduces a new whole set of timeouts to take into account. IMHO it?s a lot simpler to do something like this: monitor the links status, if UP assign a static route with different metric so that one link is always preferred over another. On link DOWN event, remove the static route, flush the route cache (speed up kernel look ups into the new route with higher or lower metric), and traffic will flow very quickly again on the new link. I use a very similar setup using a patched version of vtun (we clearly don?t want or need that), and the response time is in the order of a couple of seconds (it could be a lot lower with proper trimming to the setup). Fabio