From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 8 20:34:52 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 621C7D0E for ; Mon, 8 Dec 2014 20:34:52 +0000 (UTC) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 355EDC8B for ; Mon, 8 Dec 2014 20:34:51 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id v10so5725027pde.26 for ; Mon, 08 Dec 2014 12:34:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=NhTN+I8bOWgtkowwPw04GUX+Sz3t0t9gLIJcVBaAXsM=; b=SU2uRF/Q1fcJ/4WNY6tTo3e/IjcWOncDusB/XD/kd9RplKC76PCe967KXRpqksdmyR d9RPrNaxy9W+ENeNdYIkIvHHDQ/TDqg13EFP69F5OcipQtKNJJbT9dUo92WvQlJ24MFr V/evyFDsJ7EB7SiRs4v4+eWFM6tJvOygSp8R0In0NrXjxuvk5Ai+HF3z125aE0ESQonW IEkHDP8vopETiuj032EoWtPTTlzpYb7+5jvZCW+bUTvMENUwdWXpllWnu+3Mbtwrpy2L 1qcETYbViduXP+gkDg1rG3bvowuVV5vrJ0ANE8BHPQAQqjZHzxIRwh1kXhI0AEdf/QG+ BFaA== X-Gm-Message-State: ALoCoQkN0G9zK0aSEwo1XlBH29GxIVIXpkRQ7L6/NggxwTHZ/isyXzSbDK3FZy/kHyPcZwqRar8B X-Received: by 10.66.65.202 with SMTP id z10mr53448814pas.104.1418069028906; Mon, 08 Dec 2014 12:03:48 -0800 (PST) Received: from [10.0.1.19] (dy2.sdf.com. [216.113.193.86]) by mx.google.com with ESMTPSA id b16sm37224613pdj.76.2014.12.08.12.03.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 12:03:48 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: multipath problem: active provider chosen on passive FC path? From: Tom Samplonius In-Reply-To: <23F06C2E-558A-4E68-AD35-B3CD49760DFE@patpro.net> Date: Mon, 8 Dec 2014 12:03:46 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <81548287-A118-4AFD-8AB5-F76CD3B060FF@samplonius.org> References: <23F06C2E-558A-4E68-AD35-B3CD49760DFE@patpro.net> To: patpro@patpro.net X-Mailer: Apple Mail (2.1993) Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 20:34:52 -0000 >=20 > I've installed FreeBSD 9.3 on two HP blade servers (G6), into an HP = C7000 chassis. This chassis uses two Brocade FC switches (active/passive = if I'm not mistaken). The blade servers use=20 > Unfortunately during boot, and during normal operation, the first = provider (da2 here) seems faulty: >=20 > isp0: Chan 0 Abort Cmd for N-Port 0x0008 @ Port 0x090a00 > (da2:isp0:0:2:0): Command Aborted > (da2:isp0:0:2:0): READ(6). CDB: 08 00 03 28 02 00=20 > (da2:isp0:0:2:0): CAM status: CCB request aborted by the host > (da2:isp0:0:2:0): Retrying command FC switches are typically active-active, as the FC switch fabric is = "intelligent" and doesn't have looping issues like ethernet. Your issue is probably on the storage array. Storage arrays typically = have an OS profile, and various advanced settings for how a LUN is = exported to a client. Storage arrays typically support SCSI = Reservations, where the LUN must be reserved before it can be used. = Also, storage arrays typically have multiple controller cards, and = typically an LUN is owned by one of the controllers at a time. The = storage array can signal to the client via SCSI that it wants to move = the the ownership to another controller. With proper client support, = migrating a LUN to another controller is typically hit-less.=20 In your case, the storage array is probably configured to use one = controller/path at a time. And it is probably expecting to see specific = SCSI messages between itself and the host. These type of settings are = typically set by the OS profile. Generally, storage arrays work best if you only send IO to one = controller at a time. And this involves co-ordination between the array = and the client using SCSI control messages. Though active-active paths = can usually be supported as well. Tom