|
On Mon, 9 Oct 2000 02:22:09 -0400 (EDT)
Brad Benson <brad@xxxxxxxxxxx> wrote:
> On Mon, 9 Oct 2000, Michael Taubert wrote:
>
> > Date: Mon, 9 Oct 2000 08:15:13 +0200
> > From: Michael Taubert <taubert@xxxxxxxxxxxxxxxxxxxxx>
> > To: Brad Benson <brad@xxxxxxxxxxx>
> > Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: Re: IP alias failover problems
> >
> > On Mon, 9 Oct 2000 02:10:37 -0400 (EDT)
> > Brad Benson <brad@xxxxxxxxxxx> wrote:
> >
> > > >
> > > > did you set up the lvs-routing-table on the secondary router with
> > > > lvsadm ?
> > > >
> > >
> > > No, I'm copying ldirectord.cf over to the secondary router each time it's
> > > changed on the primary router. Then, when the secondary router sees that
> > > primary is down it fires up ldirectord.cf. Shouldn't that populate the
> > > lvs routing table correctly when it reads the config file at startup?
> > >
> >
> > sorry, but i dont know that configurationfile. my lvs-routers doesnt
> > have them. im using a script that heartbeat lets setup the ipvs-table on
> > each router.
>
its home-grown. you should be familiar with the 'ipvsadm'-command.
its just a simple script that set my lvs-routes. well, you may execute
# ipvsadm -S > <somefile>
on your first lvs-router to save the lvs-routing-table.
on the secondary router, you can restore it with
# echo <somefile> | ipvsadm -R
this you can put in a script, that will be executed by heartbeat.
--
gruss,
michael
|
