From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 15 20:01:11 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6D1E16A420 for ; Thu, 15 Dec 2005 20:01:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B4D743D5A for ; Thu, 15 Dec 2005 20:01:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-02.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jBFK14DL012155; Thu, 15 Dec 2005 15:01:06 -0500 (EST) Date: Thu, 15 Dec 2005 15:00:59 -0800 (PST) From: Brad Miele To: Sebastian Koehler In-Reply-To: <43A1B967.2010601@syncer.de> Message-ID: <20051215140240.X1010@payswan.miggles.org> References: <43A1B967.2010601@syncer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-scsi@freebsd.org Subject: Re: Help with HP MSA 1500cs and DL380 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: Thu, 15 Dec 2005 20:01:12 -0000 Sebastian, Thanks for the quick reply! On Thu, 15 Dec 2005, Sebastian Koehler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Brad, > > it seems that you use a direct attached SAN environment. There are no > switches are involved, right? correct > Is this a single or multipath setup? single > The > QLA2312 should have 2 FC-ports. What is the HP name for this HBA? > FC2214(DC)? the card has a single fc port, its HP name is: FCA2214 http://h18006.www1.hp.com/products/quickspecs/11711_na/11711_na.html > Please post some errors and lun assignment. the most common error that i see is this: Dec 14 13:48:15 bwayipn04 kernel: isp0: command timed out for 0.125.4 I get about 5 of these a day. the system seems to recover, but the attached FreeBSD server locks up briefly while it is working it out it seems. the other, rarer errors are: Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): READ(06). CDB: 8 0 1 1f 20 0 Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): CAM Status: SCSI Status Error Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): SCSI Status: Check Condition Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): UNIT ATTENTION asc:29,0 Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): Power on, reset, or bus device reset occurred Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): Retrying Command (per Sense Data) interestingly enough, da5 has no data on it yet, and the device was relatively inactive at 3am EST. here is the output from show units on one of the msa1500cs: Unit 1: In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1. Unit Identifier : nfsdata02 Device Identifier : 600508B3-00918B90-F30CB219-4D120000 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 13 Data Disk(s) used by lun 1: Disk101: Box 1, Bay 01, (B:T:L 0:00:00) Disk102: Box 1, Bay 02, (B:T:L 0:01:00) Disk103: Box 1, Bay 03, (B:T:L 0:02:00) Disk104: Box 1, Bay 04, (B:T:L 0:03:00) Disk105: Box 1, Bay 05, (B:T:L 0:04:00) Disk106: Box 1, Bay 06, (B:T:L 0:05:00) Disk107: Box 1, Bay 07, (B:T:L 0:08:00) Disk108: Box 1, Bay 08, (B:T:L 0:09:00) Disk109: Box 1, Bay 09, (B:T:L 0:10:00) Disk110: Box 1, Bay 10, (B:T:L 0:11:00) Disk111: Box 1, Bay 11, (B:T:L 0:12:00) Disk112: Box 1, Bay 12, (B:T:L 0:13:00) Disk113: Box 1, Bay 13, (B:T:L 0:14:00) Spare Disk(s) used by lun 1: Disk114: Box 1, Bay 14, (B:T:L 0:15:00) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,680,165MB Unit 2: In PDLA mode, Unit 2 is Lun 3; In VSA mode, Unit 2 is Lun 2. Unit Identifier : nfsdata03 Device Identifier : 600508B3-00918B90-80170E3B-73B20001 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 13 Data Disk(s) used by lun 2: Disk201: Box 2, Bay 01, (B:T:L 1:00:00) Disk202: Box 2, Bay 02, (B:T:L 1:01:00) Disk203: Box 2, Bay 03, (B:T:L 1:02:00) Disk204: Box 2, Bay 04, (B:T:L 1:03:00) Disk205: Box 2, Bay 05, (B:T:L 1:04:00) Disk206: Box 2, Bay 06, (B:T:L 1:05:00) Disk207: Box 2, Bay 07, (B:T:L 1:08:00) Disk208: Box 2, Bay 08, (B:T:L 1:09:00) Disk209: Box 2, Bay 09, (B:T:L 1:10:00) Disk210: Box 2, Bay 10, (B:T:L 1:11:00) Disk211: Box 2, Bay 11, (B:T:L 1:12:00) Disk212: Box 2, Bay 12, (B:T:L 1:13:00) Disk213: Box 2, Bay 13, (B:T:L 1:14:00) Spare Disk(s) used by lun 2: Disk214: Box 2, Bay 14, (B:T:L 1:15:00) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,680,165MB Unit 3: In PDLA mode, Unit 3 is Lun 4; In VSA mode, Unit 3 is Lun 3. Unit Identifier : Device Identifier : 600508B3-00918B90-FD923254-252D0005 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 3: Disk301: Box 3, Bay 01, (B:T:L 2:03:01) Disk302: Box 3, Bay 02, (B:T:L 2:03:02) Disk303: Box 3, Bay 03, (B:T:L 2:03:03) Disk304: Box 3, Bay 04, (B:T:L 2:03:04) Disk305: Box 3, Bay 05, (B:T:L 2:03:05) Disk306: Box 3, Bay 06, (B:T:L 2:03:06) Disk307: Box 3, Bay 07, (B:T:L 2:03:07) Spare Disk(s) used by lun 3: Disk308: Box 3, Bay 08, (B:T:L 2:03:08) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB Unit 4: In PDLA mode, Unit 4 is Lun 5; In VSA mode, Unit 4 is Lun 4. Unit Identifier : Device Identifier : 600508B3-00918B90-8DE42743-35F40006 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 4: Disk309: Box 3, Bay 09, (B:T:L 2:03:09) Disk310: Box 3, Bay 10, (B:T:L 2:03:10) Disk311: Box 3, Bay 11, (B:T:L 2:03:11) Disk312: Box 3, Bay 12, (B:T:L 2:03:12) Disk701: Box 7, Bay 01, (B:T:L 2:04:01) Disk702: Box 7, Bay 02, (B:T:L 2:04:02) Disk703: Box 7, Bay 03, (B:T:L 2:04:03) Spare Disk(s) used by lun 4: Disk704: Box 7, Bay 04, (B:T:L 2:04:04) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB Unit 5: In PDLA mode, Unit 5 is Lun 6; In VSA mode, Unit 5 is Lun 5. Unit Identifier : Device Identifier : 600508B3-00918B90-3C177166-9E2D0007 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 5: Disk705: Box 7, Bay 05, (B:T:L 2:04:05) Disk706: Box 7, Bay 06, (B:T:L 2:04:06) Disk707: Box 7, Bay 07, (B:T:L 2:04:07) Disk708: Box 7, Bay 08, (B:T:L 2:04:08) Disk709: Box 7, Bay 09, (B:T:L 2:04:09) Disk710: Box 7, Bay 10, (B:T:L 2:04:10) Disk711: Box 7, Bay 11, (B:T:L 2:04:11) Spare Disk(s) used by lun 5: Disk712: Box 7, Bay 12, (B:T:L 2:04:12) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB > You spoke about firmware versions. To prevent possible SCSI bus > resets/timeouts you need to use version 4.98 on MSA1500cs and 1.38 or > 1.40 on MSA20. here is the version output from one of the msa1500cs MSA1500 Firmware Revision: 4.98b401 (SGA0534040) MSA1500 Hardware Revision: 7 [AutoRev: 0x010000] Fibre Module AutoRev: 0x020000 SCSI I/O Module Bus 0 Revision: 2.02 SCSI I/O Module Bus 1 Revision: 2.02 SCSI I/O Module Bus 2 Revision: 2.02 SCSI I/O Module Bus 3 Revision: <> Fan Control Module A Revision: 2.36 Fan Control Module B Revision: 2.36 Box 1 PROLIANT 4LEE Rev: CP20 (Z8FNLMPX47) Box 2 PROLIANT 4LEE Rev: CP20 (Z8DYLMPX47) Box 3 PROLIANT 8LCE Rev: 1.40 (E05TMLJ15L) Box 3 Fan Control Module A Rev: 2.36 Box 3 Fan Control Module B Rev: 2.36 Box 7 PROLIANT 8LCE Rev: 1.40 (E048MLJ15L) Box 7 Fan Control Module A Rev: 2.36 Box 7 Fan Control Module B Rev: 2.36 > Use ACU-XE to set your FreeBSD hosts to Solaris or other. is ACU-XE something that i can run with FreeBSD attached hosts? I have been limited to using CLI connected via serial so far. what does the host setting do? the docs seem vague on its role. and between solaris and other, is there a preference? > Did you have the lastest firmware on the HBA, too? yes > > Best regards, > Sebastian thanks again! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFDoblnufwF6d+3vEURAhKnAJ4kjrVhtLJ8lJiWUpdrEqVy33VPagCgwUrP > U0HRXRh00Mr5mVSjBM8nmZk= > =qp3E > -----END PGP SIGNATURE----- > Brad ------------------------------------------------------------ Brad Miele IPNStock bmiele@ipnstock.com