From owner-freebsd-current@FreeBSD.ORG Thu May 26 20:25:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA4B8106564A for ; Thu, 26 May 2011 20:25:55 +0000 (UTC) (envelope-from jwd@SlowBlink.Com) Received: from nmail.slowblink.com (rrcs-24-199-145-34.midsouth.biz.rr.com [24.199.145.34]) by mx1.freebsd.org (Postfix) with ESMTP id 60C2F8FC08 for ; Thu, 26 May 2011 20:25:54 +0000 (UTC) Received: from nmail.slowblink.com (localhost [127.0.0.1]) by nmail.slowblink.com (8.14.3/8.14.3) with ESMTP id p4QKEBRw033451 for ; Thu, 26 May 2011 16:14:11 -0400 (EDT) (envelope-from jwd@nmail.slowblink.com) Received: (from jwd@localhost) by nmail.slowblink.com (8.14.3/8.14.3/Submit) id p4QKEAwm033450 for freebsd-current@freebsd.org; Thu, 26 May 2011 16:14:10 -0400 (EDT) (envelope-from jwd) Date: Thu, 26 May 2011 16:14:10 -0400 From: John To: freebsd-current@freebsd.org Message-ID: <20110526201410.GA33357@slowblink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Thu, 26 May 2011 21:12:34 +0000 Subject: hosta carp going down/up/down/up... on hostb reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 20:25:55 -0000 Hi Folks, I have a -current system as of May 9th. Between two systems I have a dedicated cross over network cable with two carp interfaces defined on it: hosta: ifconfig_bce1="inet 172.1.1.1 netmask 255.255.255.0" # cross-over cloned_interfaces="carp1 carp2" ifconfig_carp1="vhid 1 pass zfscarp1 advbase 1 advskew 100 172.1.1.101 netmask 255.255.255.0" ifconfig_carp2="vhid 2 pass zfscarp2 advbase 1 advskew 100 172.1.1.102 netmask 255.255.255.0" hostb: ifconfig_bce1="inet 172.1.1.2 netmask 255.255.255.0" # cross-over cloned_interfaces="carp1 carp2" ifconfig_carp1="vhid 1 pass zfscarp1 advbase 1 advskew 100 172.1.1.101 netmask 255.255.255.0" ifconfig_carp2="vhid 2 pass zfscarp2 advbase 1 advskew 100 172.1.1.102 netmask 255.255.255.0" When the primary system, hosta, is the MASTER for the carp interfaces, I reboot hostb. I've included the down/up sequence from /var/log/messages below. During the reboot, the carp interfaces on hosta go down and back up 5 times. Any ideas why is carp flipping back and forth while the opposing host is rebooting? This plays havoc with the associated scripts and thus resources controlled by the interfaces. While hosta & hostb are up, I can flip resources back and forth between the systems with carp 100%, perfect, no errors. Comments, ideas, or any other pointers are welcome. Thanks, John May 26 13:29:19 hosta root: start reboot hostb here May 26 13:29:45 hosta kernel: carp1: link state changed to DOWN May 26 13:29:45 hosta kernel: carp2: link state changed to DOWN May 26 13:29:47 hosta kernel: carp1: INIT -> BACKUP May 26 13:29:47 hosta kernel: carp2: INIT -> BACKUP May 26 13:29:47 hosta kernel: carp1: link state changed to DOWN May 26 13:29:47 hosta kernel: carp2: link state changed to DOWN May 26 13:29:47 hosta kernel: carp1: link state changed to DOWN May 26 13:29:47 hosta kernel: carp2: link state changed to DOWN May 26 13:29:50 hosta kernel: carp1: INIT -> BACKUP May 26 13:29:50 hosta kernel: carp2: INIT -> BACKUP May 26 13:29:50 hosta kernel: carp1: link state changed to DOWN May 26 13:29:50 hosta kernel: carp2: link state changed to DOWN May 26 13:29:59 hosta kernel: carp1: link state changed to UP May 26 13:29:59 hosta kernel: carp2: link state changed to UP May 26 13:30:08 hosta kernel: carp1: link state changed to DOWN May 26 13:30:08 hosta kernel: carp2: link state changed to DOWN May 26 13:30:11 hosta kernel: carp1: INIT -> BACKUP May 26 13:30:11 hosta kernel: carp2: INIT -> BACKUP May 26 13:30:11 hosta kernel: carp1: link state changed to DOWN May 26 13:30:11 hosta kernel: carp2: link state changed to DOWN May 26 13:30:11 hosta kernel: carp1: link state changed to DOWN May 26 13:30:11 hosta kernel: carp2: link state changed to DOWN May 26 13:30:14 hosta kernel: carp1: INIT -> BACKUP May 26 13:30:14 hosta kernel: carp2: INIT -> BACKUP May 26 13:30:14 hosta kernel: carp1: link state changed to DOWN May 26 13:30:14 hosta kernel: carp2: link state changed to DOWN May 26 13:30:23 hosta kernel: carp1: link state changed to UP May 26 13:30:23 hosta kernel: carp2: link state changed to UP May 26 13:30:49 hosta kernel: carp1: link state changed to DOWN May 26 13:30:49 hosta kernel: carp2: link state changed to DOWN May 26 13:30:51 hosta kernel: carp1: INIT -> BACKUP May 26 13:30:51 hosta kernel: carp2: INIT -> BACKUP May 26 13:30:51 hosta kernel: carp1: link state changed to DOWN May 26 13:30:51 hosta kernel: carp2: link state changed to DOWN May 26 13:31:00 hosta kernel: carp1: link state changed to UP May 26 13:31:00 hosta kernel: carp2: link state changed to UP May 26 13:32:35 hosta kernel: carp1: link state changed to DOWN May 26 13:32:35 hosta kernel: carp2: link state changed to DOWN May 26 13:32:37 hosta kernel: carp1: INIT -> BACKUP May 26 13:32:37 hosta kernel: carp2: INIT -> BACKUP May 26 13:32:37 hosta kernel: carp1: link state changed to DOWN May 26 13:32:37 hosta kernel: carp2: link state changed to DOWN May 26 13:32:47 hosta kernel: carp1: link state changed to UP May 26 13:32:47 hosta kernel: carp2: link state changed to UP May 26 13:32:52 hosta kernel: carp1: link state changed to DOWN May 26 13:32:52 hosta kernel: carp2: link state changed to DOWN May 26 13:32:54 hosta kernel: carp1: INIT -> BACKUP May 26 13:32:54 hosta kernel: carp2: INIT -> BACKUP May 26 13:32:54 hosta kernel: carp1: link state changed to DOWN May 26 13:32:54 hosta kernel: carp2: link state changed to DOWN May 26 13:33:03 hosta kernel: carp1: link state changed to UP May 26 13:33:03 hosta kernel: carp2: link state changed to UP May 26 13:34:37 hosta root: hostb reboot complete