CARP preemption

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <misc@...>
Date: Friday, October 12, 2007 - 7:44 am

Hi,

carp(4) states:

"When the option is enabled and one of the carp enabled physical
interfaces goes down, advskew is changed to 240 on all carp interfaces."

in case preemption is enabled. Can anyone give me a hint why this is
limited to a failure of the physical interface?

I had some floods on my firewall which caused the external interfaces to
drop packets (including the carp packets I assume) which was leading to
a takeover of the external carp interface only.

This of course left the cluster in a non-functional state until
preemption switched back the external carp interface to the flooded host.

I wonder if this is intended?

regards

Tim

Config:

net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=1
net.inet.carp.arpbalance=0

carp0: flags=8843 mtu 1500
lladdr 00:00:5e:00:01:01
carp: MASTER carpdev em0 vhid 1 advbase 1 advskew 0
groups: carp egress
inet6 fe80::200:5eff:fe00:101%carp0 prefixlen 64 scopeid 0x7
inet 192.168.0.26 netmask 0xfffffffc broadcast 192.168.0.31
carp1: flags=8843 mtu 1500
lladdr 00:00:5e:00:01:fe
carp: MASTER carpdev em1 vhid 254 advbase 1 advskew 0
groups: carp
inet6 fe80::200:5eff:fe00:1fe%carp1 prefixlen 64 scopeid 0xa
inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.2.255

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
CARP preemption, Tim Evers, (Fri Oct 12, 7:44 am)