2010/4/23 <[email protected]> > Hi list, > > I found some traces of this 'issue' (if it actually is one, no idea), e.g. > here: > > http://www.pubbs.net/openbsd/200911/51706/ > > # sysctl |grep carp > net.inet.carp.allow=1 > net.inet.carp.preempt=1 >
I seem to recall that the above sysctl is creating that behaviour, along with the more expected "fail all carp interfaces if one goes down". > > However, if host A is MASTER (the 'usual' setup) and then reboots, host B > becomes MASTER -- perfect. However, if host A is back online again, it does > NOT become MASTER again. Host B stays MASTER (either until its rebooted or > the carp or underlying interfaces are shut down). > Is this a known behaviour? Is it wanted? Thanks for shedding light on this. > > -- To our sweethearts and wives. May they never meet. -- 19th century toast
