From owner-freebsd-stable@freebsd.org Fri Jun 29 17:18:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6312CEFFB60 for ; Fri, 29 Jun 2018 17:18:38 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C70AC732D9 for ; Fri, 29 Jun 2018 17:18:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id v25-v6so1954563wmc.0 for ; Fri, 29 Jun 2018 10:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=zlFTPlEK1kv20H+ev84Yn8gI22PvNekdMdpAHe+uYgg=; b=FjTs/hB2QG9p/lim/EXOxxOUZt4lmX8nyT9G+wS6MjxqlxJXO4e748I7eH3B/OoeBy tY5EYERqBf9CUvlsbGPQcI7cLshz+CxiIBXvTOuX+nk6lONbAmAA0MufF2KaxTITKWS3 l5VignMDZ5vwWYb8gbuEM+a5YoI9lycs2idOpTkDsL50POVw2KqPeh6sI/nIadCRdtkr DV99imUptG33+tnS5gYe0DZKpHe68UChW9DADmhNbrbS+rHaH9CXCl6KhcDGogB9vLir bxweT2w9lf4VxcBwGFee+sIgon3a9/xR+AeW33v3oIYmUsSxtzAvZM6BBY2++7ffpfYn MeSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=zlFTPlEK1kv20H+ev84Yn8gI22PvNekdMdpAHe+uYgg=; b=e5nHXLs9wuq6VCdmevyXXzX9EgsXRfQaoy9lTFOMJFlqb4OK1kZGFguL86RQ6Ag7cm 9opC8peeXY5G36VODTQqkk257RDjJR1JKA2TFzL8t6s8nanZhXW5lFvdg2pYqcmy3U2C OWuEkE1mf16TLEg2QPPtF39sH4llsNXVlY89a4w8QYBAzByGHhr/WSAYNTtd3HHa4e+M tMAu2uR08mmBGI3ZpdMCkSkubheZskUVChtKKkOiEQvn0n4AZ9DMjCO7BxVCLBM4HQNF lD7YjbEImyrSVNb2FezzloAC89VJ+sN9T1KkAww/u6s5GylDmLXjqtHdipNidIzLiqJs IfvA== X-Gm-Message-State: APt69E1hRUMbJDln+UWS/+1svGAmJ+x4M40PPQdnzj71w0wPgcMGcRXV l5SqS8Du0ZjFJLwzWmwCUb/1lQ== X-Google-Smtp-Source: AAOMgpeRC9fb9Wpn0VVMN3ezOqBf/J8ET07XJdKF1LZRhNwB6xWNwJYHX4cFer73oixtKa8ESnDDRg== X-Received: by 2002:a1c:58d1:: with SMTP id m200-v6mr2517314wmb.160.1530292716155; Fri, 29 Jun 2018 10:18:36 -0700 (PDT) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id j10-v6sm13549610wrr.47.2018.06.29.10.18.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jun 2018 10:18:35 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 29 Jun 2018 18:18:33 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: "Frank (lists)" Cc: FreeBSD Stable Subject: Re: iSCSI initiator multipath Message-ID: <20180629171833.GA1503@brick> Mail-Followup-To: "Frank (lists)" , FreeBSD Stable References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 17:18:38 -0000 On 0629T1330, Frank (lists) wrote: > Hi, > > I have a  HA setup with LIO on linux. The exact set up is can be found > here: http://docs.ceph.com/docs/mimic/rbd/iscsi-target-cli/ > > I'm trying to use FreeBSD as initiator for this, but I can't manage to > get it working. Is this kind of setup supported by the FreeBSD > initiator? From another mailinglist a response  was about multipath > probably not enabling ALUA. FreeBSD doesn't support ALUA. You can do multipathing in two ways: 1. Export your LUNs via two (or more) different paths (for example via two different target portal IP addresses), on the initiator side set up both iSCSI sessions in the usual way (like without multipathing), add kern.iscsi.fail_on_disconnection=1 to /etc/sysctl.conf, and set up gmultipath on top of LUNs reachable via those sessions 2. Set up the target so it redirects (sends "Target moved temporarily" login responses) to the target portal it considers active. Then set up the initiator (single session) to either one; the target will "bounce it" to the right place. You don't need gmultipath in this case, because from the initiator point of view there's only one iSCSI session at any time.