From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 4 15:52:26 2015 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 87AE94F6 for ; Thu, 4 Jun 2015 15:52:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 4B8C718C2 for ; Thu, 4 Jun 2015 15:52:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by obbea3 with SMTP id ea3so35619100obb.0 for ; Thu, 04 Jun 2015 08:52:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=h4ft+Me1IA/vjS5Ev9ctn9x/W67+3GPKrJEQFngrbYQ=; b=HbliKT6ZcHH7uazGryyZvZCEEMnUIJ5GEyMGaR8D3MRvJhI/jNEy9x0K8Ryxe5KaJB XMDVRZT/+XLGzDq3fJ+C2ahEnzk6BXqLSBbNdcSP9woxYD9rDSRT1+t+y49cYLj3iu2T KfppTsfLobxpGUpVrgnlH6vxG7iVoe/GOZxUCTqBvr1w51KErY185oeuzR7Hkms2JAnj XwwJldNYr4E5b/nQy3ZafhBMNcEvRG7233ymLVn9pvMIw2LIg+OuqtXD/XGGX+K+aNso Kpu40+s/n50pmbXABgKqtyudTktzj88N6Ma4kSzOvQK02ZDWzxptIxn7ibmy+QjJUCWV WA4g== MIME-Version: 1.0 X-Received: by 10.182.16.161 with SMTP id h1mr12183384obd.49.1433433145563; Thu, 04 Jun 2015 08:52:25 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.107.3 with HTTP; Thu, 4 Jun 2015 08:52:25 -0700 (PDT) In-Reply-To: <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es> References: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es> Date: Thu, 4 Jun 2015 09:52:25 -0600 X-Google-Sender-Auth: CmgzcWRRJBHMOcKiFIPCesWL7FQ Message-ID: Subject: Re: LSI 3008 based HBA (mpr) and backplane slot identification From: Alan Somers To: Borja Marcos Cc: FreeBSD-scsi Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2015 15:52:26 -0000 On Thu, Jun 4, 2015 at 9:33 AM, Borja Marcos wrote: > > On Jun 4, 2015, at 5:23 PM, Alan Somers wrote: > >> I've never used sas3ircu or sas2ircu, but it's probably getting the >> slot number based on either the expander's SES Additional Element >> Status Page, or by the expander's SMP DISCOVER response. Both of >> those methods will give stable responses. Even if you swap drives, >> move them around, turn phys on and off, etc, both of those methods >> will still map the same physical slot to the same Slot # every time. >> Only an expander or HBA firmware upgrade can change it. However, the >> slot mapping may not make intuitive sense. You'll have to experiment >> to see what Slot # corresponds to what physical slot. > > Thank you very much. At least on the machines on which I am using it, the mapping is > stable and even intuitive. > > What I was wondering was it something could change the mapping unexpectedly. > Understood, a firmware update is a risk, but I was thinking about those static mappings > between target IDs and particular disks (I imagine, serial numbers) kept by the HBA. It > would be a tickling timebomb if, say, after four or five disk replacements numbers begun > to get shuffled. Nope. Slot stuff happens at a lower layer than bus/target/lun assignment. For each slot, the expander tells the host the SAS Address of the drive installed in that slot, if any. If you want to play around, install sysutils/sg3_utils and run "sg_ses -p 10 /dev/ses0". > >> When you need to replace a drive, your best option would be to use the >> "sas3ircu locate" command to turn on the slot's error LED. Then you >> won't need to consult a slot mapping diagram. > > Sorry, I didn't know that command. I haven't been exactly eager to try options to sas[23]ircu > because it's intended for IR firmware (or that I understand) and I am using IT. > > > > Thank you very much! > > > > > Borja. > Glad to help. -Alan