Date: Sat, 23 Sep 2017 09:21:35 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: Steven Hartland <killing@multiplay.co.uk>, freebsd-net@freebsd.org Subject: Re: CARP under 10.3 - can't "ifconfig down" one or more VHIDs? Message-ID: <3F8D64F72B72084041550C1E@Mac-mini.local> In-Reply-To: <22f64f3e-5572-4324-5e4c-ab5680e8e612@multiplay.co.uk> References: <1183C95F3417890F2D0B1756@[10.12.30.106]> <22f64f3e-5572-4324-5e4c-ab5680e8e612@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 22 September 2017 at 20:16:25 +0100 Steven Hartland <killing@multiplay.co.uk> wrote: > CARP on 9 and 10 are very different its not a separate interface anymore, > its a property on the parent interface, so the behavior your described is > expected. > > If you want to disable carp just remove it, if however you want for fail > to the other virtual host, just bump the advskew or force the state > change. Ok, thanks for confirming that - bit of a shame 'ifconfig carpX down' was a very quick way of temporarily removing CARP (i.e. so the host didn't participate in the pool) for maintenance while leaving the base / parent interface available - and then putting it back 'as-was' with messing around with the other values. Do you know if there's any interoperability issues having some 9.x and some 10.x sharing the same CARP system? I'll probably replace with a script to store the skews, push them to a very high value, mark as 'BACKUP' all the VHID's - and something to undo it all again - though actually just removing it might be easier (providing adding it doesn't cause a moment of "I'm MASTER, uh, no, I'm BACKUP"). -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F8D64F72B72084041550C1E>