Date: Fri, 22 Sep 2017 20:16:25 +0100 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-net@freebsd.org Subject: Re: CARP under 10.3 - can't "ifconfig down" one or more VHIDs? Message-ID: <22f64f3e-5572-4324-5e4c-ab5680e8e612@multiplay.co.uk> In-Reply-To: <1183C95F3417890F2D0B1756@[10.12.30.106]> References: <1183C95F3417890F2D0B1756@[10.12.30.106]>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Regards Steve On 22/09/2017 14:21, Karl Pielorz wrote: > > Hi, > > We've been using CARP for a long time - initially under FreeBSD 9.x. > > We're just looking at setting it up on some 10.3 boxes, and have hit a > snag. Some of the syntax for setting it up has changed, but that's Ok, > we've read up and got it working. > > The issue we've got is if I want to "disable CARP" on one of the 9.x > boxes, temporarily I can do: > > ifconfig carp0 down > ifconfig carp1 down > ifconfig carp2 down > > > The host's base NIC IP address (i.e. non-vhid) address is left usable, > and intact - but all the CARP interfaces get set as "INIT" - so > they're still there, but they're not going to participate in CARP, > until you do a "ifconfig carpX up" on them. > > > If I try this under 10.3 - e.g. with a NIC with 3 vhid's setup: > > carp: BACKUP vhid 1 advbase 1 advskew 100 > carp: BACKUP vhid 2 advbase 1 advskew 100 > carp: BACKUP vhid 3 advbase 1 advskew 100 > > So, I do: > > ifconfig em0 vhid 1 down > > And, they *all* go to INIT: > > carp: INIT vhid 1 advbase 1 advskew 100 > carp: INIT vhid 2 advbase 1 advskew 100 > carp: INIT vhid 3 advbase 1 advskew 100 > > And, worse - em0 is now also down. > > Trying to set the 'state' to "INIT" on an individual vhid doesn't work > either (no error, but it does nothing). > > Is there a way under 10.3 to "disable" (i.e. set to INIT) the CARP > vhid's - without disabling the underlying NIC? > > We tend to do this for maintenance where we're taking services down, > and don't want the host to 'accidentally' pickup stray CARP vhid's > from other boxes (because there's no service running). > > Thanks, > > -Karl > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22f64f3e-5572-4324-5e4c-ab5680e8e612>