LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: After failover, why VIP is left in primary server?

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: After failover, why VIP is left in primary server?
From: Michael E Brown <michael_e_brown@xxxxxxxx>
Date: Mon, 22 Jan 2001 08:19:22 -0600 (CST)
On Mon, 22 Jan 2001, Sachie Shinohara wrote:

> Hi, I need help.
>
> I have an trouble with VIP.
> I'm using linux-2.2.18 kernel, ipvs-1.0.2-2.2.18, and piranha-0.4.17-6.

Try the redhat piranha lists...

>
> In failover test, ethernet was weird.

Please explain your methodology in performing your failover tests.

>
> I down the pulse deamon in primary Piranha server, then secondary
> Piranha server started.
> But, this thing happend.
> Primary server had still VIP(eth0:1, eth1:1), and secondary server had
> same VIP addresses as primary had. In this situation I could ping to

Depending on how you performed the failover test, this is normal. If you
cut all paths of communication between primary and secondary, then both
servers will have the VIP addresses.

> both IP, eth0:1&eth1:1, and even more virtual web server had been
> working fine.
>
> One thing I noticed was when stopping piranha, pulse was sending this
> message. 'pulse[****] : running command "/sbin/ifconfig" "eth1:1" "up"'
> and 'pulse[****] : running command "/sbin/ifconfig" "eth0:1" "up".'
> I am sure this message ran on stopping piranha.
>
> Is this thing normal? If so, I want to know why.
>


--
Michael Brown




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