Re: why nopreempt do not work in keepalived?

[email protected]
Newsgroups gmane.linux.keepalived.devel
Message-ID <[email protected]>
There is a difference of more that 50 ‎in the priorities that means hard fail over to the one with the higher priority. That behavior is stated in the VRRP RFC's

From: [email protected]

Sent: Tuesday, August 4, 2015 02:32

To: keepalived-devel

Reply To: [email protected]

Subject: [Keepalived-devel] why nopreempt do not work in keepalived?

Hi all,

It has taken several days to build LVS+keepalived environment, but it cannot meets the demand. My configuration is as followed:

Server-A:
State - BACKUP
priority - 200
nopreempt
Server-B:
State - BACKUP
priority - 100

First of all, VIP is at Server-A.
Then I plug out Server-A's cable, so VIP is at Server-B.
Finally I plug in Server-A's cable, and Server-A preempt the VIP.

Questions:
1. It seems that the flag 'nopreempt' doesn't work, WHY?

2. What can I do if I want to forbid Server-A from preempting the VIP?

Thanks in advance.

------------------------------------------------------------------------------

_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.