Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Jan 2000 12:04:10 -0800
From:      Alfred Perlstein <bright@wintelcom.net>
To:        Jack Rusher <jar@rci.net>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: downed IP addresses/redundancy
Message-ID:  <20000128120410.G7157@fw.wintelcom.net>
In-Reply-To: <3891B307.620A684F@rci.net>; from jar@rci.net on Fri, Jan 28, 2000 at 10:17:27AM -0500
References:  <20000128045440.F7157@fw.wintelcom.net> <3891B307.620A684F@rci.net>

next in thread | previous in thread | raw e-mail | index | archive | help
* Jack Rusher <jar@rci.net> [000128 07:42] wrote:
> Alfred Perlstein wrote:
> > 
> > Does anyone particularly like/hate this idea?  Just wanted to
> > share, and possibly get better suggestions.
> 
> I usually do that like this:
> 
> HostA -> Address1, Alias1
> HostB -> Address2
> 
> ...where Host A and Host B talk to each other through the pair of
> "real" addresses, while the service network uses the address referred
> to above as "alias 1".  When Host A goes away, Host B does an
> ifconfig <if> alias <Alias1> to bring up the service net address on
> Host B.
> 
>   We just completed a full n-way local and wide area application
> level failover product that runs under FreeBSD 3.x.  It does a lot of
> this for you, including maintaining heartbeat links, starting and
> stopping services, and the rest of the stuff you would expect from
> such a beast.  Oh, and it runs cross platform; you can fail an Apache
> (or whatever) instance between Solaris, Linux and FreeBSD.  Go check
> out the press release at the URL below.

Definetly a cool product, still the problem is that if you tell
a daemon to bind to a particular IP address, let's take this
scenario:

You have multiple customers on two boxes, each customer gets 2
IP address and you lolad balance between the two.

Some customers may wish to run thier own sql servers, they should
only bind to the IP address on each machine that they own.

Once you tell an application to bind to a particular IP address
I'm pretty sure most don't have an option to bind another listen
socket.

The customer can't fail over properly because even when the alias
for the box that dies comes up, thier daemon won't get requests on
the added IP.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000128120410.G7157>