From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IP Failover
Date: Tue, 07 Oct 2003 22:08:03 +0000 [thread overview]
Message-ID: <marc-lartc-106556459018861@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106485798424125@msgid-missing>
On Tuesday 07 October 2003 21:55, John Klingler wrote:
> If anyone is interested, in my quest for a networking solution which
> provides IP Failover on heterogenous redundant networks, I have listed
> the solutions I found below. I would welcome comments from anyone who is
> familiar with these.
>
> 1. faild - I have included a description below of a program daemon
> which monitors the Ethernet connections and changes the routing
> tables when a failure is detected. IP Failover is all this simple
> program does. Being simple, however, makes it small and easy to port.
> 2. High Availability Linux Project (HAL) (http://linux-ha.org/) has
> code available for FreeBsd and Solaris (and probably reasonably
> portably to other UNIX platforms. It supports virtual (redundant)
> servers but could probably therefore be configured to support
> redundant LANs.
> 3. Advanced Network Services (ANS 2.3.x) for Linux* Operating
> Systems. which is available from Intel on both PCs and UNIX OS's.
> ANS provides IP Failover and much more, such as switch failover,
> load leveling, etc. See:
>
> http://www.intel.com/support/network/adapter/onlineguide/PRO1000/DOCS/SERVE
>R/index.htm.
>
> 4. Linux Virtual Server Project (LVS) - VRRPD, Virtual Router
> Redundancy Protocol (http://off.net/~jme/vrrpd/) which also
> provides IP Failover. It implements RFC2338 but is only available
> on Linux but may be portable. As with HAL, it is probably
> configureable to provide redundant LAN.
If I was you, I should go for keepalived. This is part of LVS but you can
also use it just for the ip Failover. Companies like IBM, RH, are using this
so I think it can be trusted.
http://freshmeat.net/projects/keepalived/
"In addition, it implements a VRRPv2 stack to handle director failover. "
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-07 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 17:36 [LARTC] IP Failover John Klingler
2003-09-29 17:42 ` Ben
2003-09-29 17:58 ` S Mohan
2003-09-30 5:40 ` Andrew Kozachenko
2003-09-30 10:52 ` Ronnie Garcia
2003-09-30 18:50 ` Jose Luis Domingo Lopez
2003-10-07 19:55 ` John Klingler
2003-10-07 22:08 ` Stef Coene [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-106556459018861@msgid-missing \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox