From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 8 21:33: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 2396CBF for ; Mon, 8 Dec 2014 21:33:52 +0000 (UTC) Received: from rack.patpro.net (rack.patpro.net [193.30.227.216]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "patpro.net", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9238316 for ; Mon, 8 Dec 2014 21:33:51 +0000 (UTC) Received: from [192.168.0.2] (boleskine.patpro.net [82.230.142.222]) by rack.patpro.net (Postfix) with ESMTPSA id 9D60F947; Mon, 8 Dec 2014 22:33:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=patpro.net; s=patpro; t=1418074426; bh=5YYZC52AQiJQlG5TDsp6ZGkQ6/9J2bzIlAdnO+YUKas=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=C64OC2ccQhfg9dvQgkEY2ZTmP/ccFocUbZ0hpwG+6txhFB2xHMiMrE9BjYHLjNYzJ 7jNwLexXHiw5Lu1fx4oCZbo1BbzXrkJmBeFsvFwn4ueVtJ0hMQMW0HXQZlGkt23uwo PhUPKNgFxJpB2MfKLe3BwjOdcS9paCzDL4cvZkSE= Subject: Re: multipath problem: active provider chosen on passive FC path? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=iso-8859-1 From: Patrick Proniewski In-Reply-To: <81548287-A118-4AFD-8AB5-F76CD3B060FF@samplonius.org> Date: Mon, 8 Dec 2014 22:33:46 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <23F06C2E-558A-4E68-AD35-B3CD49760DFE@patpro.net> <81548287-A118-4AFD-8AB5-F76CD3B060FF@samplonius.org> To: Tom Samplonius X-Mailer: Apple Mail (2.1085) 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 21:33:52 -0000 On 08 d=E9c. 2014, at 21:03, Tom Samplonius wrote: >>=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 >=20 >=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 >=20 >=20 > FC switches are typically active-active, as the FC switch fabric is = "intelligent" and doesn't have looping issues like ethernet. >=20 > 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 >=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. >=20 > 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. Thank you for your reply. The SAN is an EMC VNX 5300. By default it = presents LUNs using ALUA as failover mechanism. I though GEOM could not = handle ALUA properly, so I changed the failover setting for this LUN, = now the FreeBSD hang during boot. If I boot in single user mode, it = boots completely but the result is the same default active path is not = functioning correctly. Tomorrow, I'll try another failover setting (dubbed "legacy"). The SAN = also allows me to specify initiator type (default to Clariion), I'll dig = into this setting to see if something exists that is more adapted to = FreeBSD host. Any other idea is welcome... Patrick=