Hi,
carpdemote is increased/decreased when the link state of the carpdev
is down/up. This behavior is not related to net.inet.carp.preempt since
"carpdemote" is introduced.
But the faq still says the "net.inet.carp.preempt" variable enables it.
I'd like to commit the diff.
ok or any comment is welcome.
Index: faq/pf/carp.html
===================================================================
RCS file: /cvs/www/faq/pf/carp.html,v
retrieving revision 1.65
diff -u -p -r1.65 carp.html
--- faq/pf/carp.html 5 May 2021 21:49:29 -0000 1.65
+++ faq/pf/carp.html 17 Apr 2023 11:32:46 -0000
@@ -191,8 +191,9 @@ As such, CARP is configured using
By default, all carp interfaces are added to the <code>carp</code> group.
Each group has a <code>carpdemote</code> counter affecting all carp
interfaces belonging to that group.
- As described below, it can be useful to group certain interfaces together
- for failover purposes.
+ If one physical CARP-enabled interface goes down, CARP will increase
+ the demotion counter by 1 on interface groups that the carp(4) interface is
+ a member of, in effect causing all group members to fail-over together.
<p>
<dt><code><i>ipaddress</i></code>
<dd>This is the shared IP address assigned to the redundancy group.
@@ -216,12 +217,6 @@ Further CARP behavior can be controlled
<dt><code>net.inet.carp.preempt</code>
<dd>Allow hosts within a redundancy group that have a better
<code>advbase</code> and <code>advskew</code> to preempt the master.
- In addition, this option also enables failing over a group of interfaces
- together in the event that one interface goes down.
- If one physical CARP-enabled interface goes down, CARP will increase
- the demotion counter, <code>carpdemote</code>, by 1 on interface groups
- that the carp(4) interface is a member of, in effect causing all group
- members to fail-over together.
<code>net.inet.carp.preempt</code> is 0 (disabled) by default.
<p>
<dt><code>net.inet.carp.log</code>
