Re: [Keepalived-devel] 2 questions on keepalived

[Dominik <po...@we...>]

And another thing to add:
I read about the "portfast" feature on some cisco Switches that was 
mentioned in a Thread about Fault to Master Transition early 2005 on 
this list.
Unfortunately, my switch does not support anything like this.

So has anyone tested that patch Dimitri posted back then?

http://sourceforge.net/mailarchive/forum.php?thread_id=6610566&forum_id=3211

The patch seems to be incomplete in the archive according to the end of 
the first post in the thread, so I cannot test it myself.

> A thing to add here:
> 
>> question 1 is about the option "preempt_delay" in keepalived.conf:
>>
>> During my tests I just unplugged the power of a switch that connects 
>> the MASTER director with the realservers. BACKUP takes over and as 
>> this one is connected to another switch, my service is available - good!
>>
>> When I plug the power back into the switch, MASTER falls back 
>> immediately. But as the switch needs about 2 minutes to boot up, this 
>> is how long none of my services are avaiable.
>>
>> So from reading keealived.conf's man page, I assumed that 
>> "preempt_delay 150" would tell BACKUP to wait 2 1/2 minutes until it 
>> hands over services to MASTER again.
>> Did I get this wrong? Because when I changed my conf and restarted 
>> keepalived, the same test did the exact same thing - services fell 
>> back to MASTER as soon as the link was up again.
>>
>> I made sure initial state of every vrrp_instance is BACKUP (as the 
>> manpage said).
>> But another thing about this just to make sure:
>> Does only BACKUP need the "preempt_delay" option or do both directors 
>> need it and both need to start in BACKUP state (just like if you want 
>> to use the nopreempt option)?
> 
> 
> I did some more testing on this:
> If I stop and start keepalived on MASTER, the delay works just fine. 
> This only seems to occur on link status change.