Re: Strange carp issues

[Steven S]

Steven S wrote:
> It would appear my issues are related to timekeeping on these boxes
> (Compaq DL360 G1).
>
> If I bump advbase to '3' on each box everything is more stable.
> Given this, I now have a roughly 10 second fail-over time, but that
> is still acceptable.
>
> Since these are production boxes I'll probably wait until my
> 3.9 arrives to
> see if any of the kern_time/kern_clock changes help. I'll let
> everyone know more when I do.

For the archives...

I upgraded the backup firewall to 3.9-stable but it still appeared to have
the MASTER-MASTER issue (with primary at 3.8). Based on some other posts in
misc I tried using aliases on a single carp interface instead of multiple
carp interfaces on the same physical interface. I upgraded the primary to
3.9-stable and things seem to be operating as expected. I have not had any
MASTER<-->MASTER issues that weren't self inflicted. I guess I'm not 100%
sure if the cure was upgrading or migrating to aliases, but it's working.

The self inflicted issue came when I added an alias IP to FW1:carp0 but not
yet to FW2:carp0. Both FW1 and FW2 became master for the interface, until I
added the alias to FW2.

Thanks again for the pointers and the great OS!

-Steve S.

[Henning Brauer]

* Steven S <ssur...@engineered-net.com> [2006-06-03 02:01]:

> The self inflicted issue came when I added an alias IP to FW1:carp0 but not
> yet to FW2:carp0. Both FW1 and FW2 became master for the interface, until I
> added the alias to FW2.

that can lead to master-master situations unfortunately. not too much
we can do about it :(

--
BS Web Services, http://www.bsws.de/
OpenBSD-based Webhosting, Mail Services, Managed Servers, ...
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)