Date: Fri, 3 Jun 2011 00:10:36 +0200 From: Patrick Lamaiziere <patfbsd@davenulle.org> To: John <jwd@SlowBlink.Com> Cc: freebsd-fs@freebsd.org, freebsd-net@freebsd.org Subject: Re: Production use of carp? Message-ID: <20110603001036.5ad0ff8d@davenulle.org> In-Reply-To: <20110602203940.GA80549@slowblink.com> References: <20110602203940.GA80549@slowblink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Thu, 2 Jun 2011 16:39:40 -0400, John <jwd@SlowBlink.Com> a écrit : Hello, > However, if system A is the MASTER, and system B is rebooted, > the carp interface on system A will flip/flop going down and > coming back up which is not what I want. I saw this if the switch connecting the two systems takes some time to forward packets when a link is "up". This happens if the switch is doing some spanning tree protocol. (on cisco swith you should use an option "spanning tree port fast" on the switch port to avoid this) > This leads to my question, am I missing something simple about > using carp? Should I implement my own control interface on the > private network and not use carp? What are other folks doing? You may want to implement your own control because if the two hosts cannot communicate, you will have two masters. This can happen if the links on the both hosts are up, but none packet are forwarded (ie the switch connecting the two boxes is broken in some way). Instead writing your own script, you may use ifstated (in the ports tree). I've not tried FreeBSD with carp but we are very happy at $WORK with carp on OpenBSD. I guess that should work fine on FreeBSD too. Regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110603001036.5ad0ff8d>