|
Following the 'wipe' idea I found what the problem is. Using ipvs I
had my addresses use normal netmask (/27 in this case). Apparently
keepalived removed the whole range defined by that netmask. So if you
have 192.168.0.2/27 in keepalived.conf and you manually add
192.168.0.3/27 too then .3 will be removed too. Adding VIPs with /32
solves this problem.
Is this behavior made on purpose?
Regards
Bgs
Bgs wrote:
> I do want keepalived to remove the VIPs when I shut it down.
> ("do-release-ipvs"). My problem is that keepalived removed other IPs too
> that it's not supposed to handle...
>
> Or does 'release vips' mean wipe all addresses from interface?
>
> Graeme Fowler wrote:
>> On Fri, 2008-03-21 at 12:24 +0100, Bgs wrote:
>>> Any ideas? Bug or config error?
>> I hate to have to say this, but: man keepalived
>>
>> You need either or both of:
>>
>> --dont-release-vrrp, -V
>> leave (don’t remove) VRRP VIPs & VROUTEs on daemon stop.
>> --dont-release-ipvs, -I
>> Dont remove IPVS topology on daemon stop.
>>
>> Graeme
>>
>>
>> _______________________________________________
>> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
