From owner-freebsd-scsi@FreeBSD.ORG Mon May 23 21:09:55 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F3FE106566B for ; Mon, 23 May 2011 21:09:55 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2498FC13 for ; Mon, 23 May 2011 21:09:55 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 72A1139828 for ; Tue, 24 May 2011 00:09:53 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id j66aXNcCKjJ9 for ; Tue, 24 May 2011 00:09:21 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id 477583985C; Tue, 24 May 2011 00:09:21 +0300 (EEST) Received: from 226.16.50.84.dyn.estpak.ee (226.16.50.84.dyn.estpak.ee [84.50.16.226]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Tue, 24 May 2011 00:09:21 +0300 Message-ID: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> Date: Tue, 24 May 2011 00:09:21 +0300 From: Toomas Aas To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 84.50.16.226 Subject: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 21:09:55 -0000 Now that I have basic iSCSI connection working with FreeBSD 7.3 (thanks Danny!) I'm looking at multipathing. My server has two dedicated interfaces for iSCSI traffic, each connected to a separate gigabit switch, and each switch in turn connected to a separate interface on my iSCSI target (EMC Celerra NX4). I can bring up either of the two connections with iscontrol, mount the partition from the target and use it to my heart's content. But how should I handle multipathing? My initial thought was to bring up both connections simultaneously and set up gmultipath across da0 and da1. However, as soon as I bring up both connections, it seems that they begin to constantly disconnecting and reconnecting: # iscontrol -c /etc/iscsi.conf -n celerra_path1 iscontrol[14277]: running iscontrol[14277]: (pass0:iscsi0:0:0:2): tagged openings now 0 # iscontrol -c /etc/iscsi.conf -n celerra_path2 iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect iscontrol[14309]: running iscontrol[14309]: (pass1:iscsi1:0:0:2): tagged openings now 0 iscontrol[14309]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14309]: sess flags=2000040d iscontrol[14309]: Reconnect iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect iscontrol[14309]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14309]: sess flags=2000040d iscontrol[14309]: Reconnect iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect Is there a way to avoid this constant disconnect/reconnect? How are other people handling multipathing on iSCSI? -- Toomas Aas