LSI (Engenio) RAID Engines

Top  Previous  Next

LSI (previously Engenio Information Technologies, Inc.) sells RAID subsystems both under the LSI brand, as well as into the channel where other manufacturers (or VARs) re brand it as their own.  As such, you might have a RAID subsystem that uses a supported LSI engine and might not know it.

 

The dump below is from an IBM 1742 RAID subsystem, which has a supported LSI engine. As is the case with the Infortrend RAID engine, entering the -I+ will report extended SCSI inquiry information along with vendor-unique information which describes the device in more detail.  If you just send the -I command for basic inquiry information, the software will not attempt to discern whether or not device you selected has an LSI RAIDengine, and Infortrend RAID engine, or some other RAID device.

 

The -z option sends the vendor-unique commands to query the subsystem and report information on the physical disks in the subsystem. The example below shows the data returned by the -z portion in RED. The -I+ results are in blue.  The data in black will be returned regardless of the engine type (assuming the device is fibre channel, SCSI, or USB host-attach interface).  You can choose to enter the -I+ without the -z or the -z without the I+.

 

Usage

smartmon-ux -I+ -z

 

Example

# ./smartmon-ux -z -I+ /dev/sg3

SMARTMon-ux [Release 1.27, Build 06-JUN-2004] - Copyright 2003 SANtools, Inc. http://www.SANtools.com

Discovered IBM 1742 S/N "1T99995658" on /dev/sg3 [SES] (Not Enabling SMART)(1326998 MB)

Inquiry Text Page Data - ANSI defined fields

  Device Type:                         disk

  Peripheral Qualifier:                Connected to this LUN

  Removable Device:                    NO

  ANSI Version:                        3 (SPC ANSI X3.301:1997)

  Vendor Identification:               IBM

  Product Identification:              1742

  Firmware Revision:                   0520

  Async event reporting: (AERC)        NO

  Terminate task supported:            NO

  Response data format:                2

  Relative addressing supported:       NO

  Supports request/ACK data transfer:  NO

  Normal ACA Supported:                YES

  Enclosure services available:        YES

  Multi-ported device:                 NO

  Medium-changer attached: (removable) NO

  Linked commands supported:           NO

  Command queuing supported:           YES

  VS bit (byte #6/bit #5 set):         NO

  VS bit (byte #7/bit #0 set):         NO

  Total grown defects:                 0

  Total Primary (factory) defects:     0

  RAID Controller Information:

   Number of channels:                 4

   Processor memory:                   128 MB

   Board name:                         Series 4 Disk Array Controller

   Board part number:                  348-0046200

   Schematic number:                   348-0044310

   Schematic revision number:

   Board serial number:                1T99995658

   Date of manufacture:                09/08/02

   Board revision:

   Board identifier:                   4884

   Partition #0 type:                  Bootware

   Firmware revision:                  5.30.00

   Firmware date:                      09/05/02

   Partition #1 type:                  Application

   Firmware revision:                  5.30.12

   Firmware date:                      05/06/03

   Auto volume transfer supported:     YES

   DCE/DRM/DSS/DVE supported:          YES

   Multiple sub-enclosures supported:  YES

   Series 3 functionality supported:   YES

   Dual active controllers supported:  YES

   Maximum drives per LUN:             30

   Maximum global hot spares:          15

   Firmware download disabled:         NO

   System identifier:

   Subsystem revision level:           10.0

   Slot ID of this controller:         01

  Storage Array WWN:                  60:0a:0b:80:00:0f:0b:4f:00:00:00:00:3e:88:88:88

   Host Interface Number (*=This):     1*

   FC-0 topology:                      100-??-??-?

   FC part / chip type:                HPFC-5200

   FC part revision level:             11

   FC topology:                         Fabric

   Controller host ID switch setting:  0

   Host Interface Number (*=This):     2

  FC-0 topology:                      100-??-??-?

   FC part / chip type:                HPFC-5200

   FC part revision level:             11

   FC topology:                        Fabric

   Controller host ID switch setting:  0

 Inquiry Page Hex Dump:

  0000: 00 00 03 32 1F 00 40 32 49 42 4D 20 20 20 20 20    ...2..@2IBM

  0010: 31 37 34 32 20 20 20 20 20 20 20 20 20 20 20 20    1742

  0020: 30 35 32                                           052

 Inquiry EVPD Page #80h (Serial Number Page)

  0000: 00 80 00 10 31 54 32 33 33 35 35 36 35 38 20 20    ....1T99995658

  0010: 20 20 20 20

 Inquiry EVPD Page #83h (Device Identification Page)

  0000: 00 83 00 14 01 03 00 10 60 0A 0B 80 00 0F 0B 4F    ........`......O

  0010: 00 00 00 2C 3E F1 31 04                            ...,>.1.

 Inquiry EVPD Page #C0h

  0000: 00 C0 00 9A 68 77 72 34 04 01 80 00 00 00 00 00    ....hwr4........

  0010: 53 65 72 69 65 73 20 34 20 44 69 73 6B 20 41 72    Series 4 Disk Ar

  0020: 72 61 79 20 43 6F 6E 74 72 6F 6C 6C 65 72 20 20    ray Controller

  0030: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

  0040: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

  0050: 33 34 38 2D 30 30 34 36 32 30 30 20 20 20 20 20    348-0046200

  0060: 33 34 38 2D 30 30 34 34 33 31 30 20 20 20 20 20    348-0044310

  0070: 31 54 32 33 33 35 35 36 35 38 20 20 20 20 20 20    1T99995658

  0080: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

  0090: 30 39 2F 30 38 2F 30 32 20 20 34 38 38 34          09/08/02  4884

 Inquiry EVPD Page #C1h

  0000: 00 C1 00 2C 66 77 72 34 05 30 00 09 05 02 00 00    ...,fwr4.0......

  0010: 2E 42 57 20 05 30 00 00 09 05 02 00 00 F0 00 00    .BW .0..........

  0020: 2E 41 50 20 05 30 12 00 05 06 03 00 07 91 72 98    .AP .0........r.

 Inquiry EVPD Page #C2h

  0000: 00 C2 00 2C 73 77 72 34 05 30 12 05 06 03 1F 1F    ...,swr4.0......

  0010: 2E 42 57 20 05 30 00 00 09 05 02 00 00 F0 00 00    .BW .0..........

  0020: 2E 41 50 20 05 30 12 00 05 06 03 00 07 91 72 98    .AP .0........r.

 Inquiry EVPD Page #C3h

  0000: 00 C3 00 2C 70 72 6D 34 1E 0F 00 9F 00 00 00 00    ...,prm4........

  0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

 Inquiry EVPD Page #C4h

  0000: 00 C4 00 1C 73 75 62 73 20 20 20 20 20 20 20 20    ....subs

  0010: 20 20 20 20 20 20 20 20 31 30 2E 30 30 31 00 00            10.001..

 Inquiry EVPD Page #C5h

  0000: 00 C5 00 44 68 69 6E 66 81 03 00 1C 31 30 30 2D    ...Dhinf....100-

  0010: 3F 3F 2D 3F 3F 2D 3F 20 48 50 46 43 2D 35 32 30    ??-??-? HPFC-520

  0020: 30 20 20 20 31 31 02 00 02 03 00 1C 31 30 30 2D    0   11......100-

  0030: 3F 3F 2D 3F 3F 2D 3F 20 48 50 46 43 2D 35 32 30    ??-??-? HPFC-520

  0040: 30 20 20 20 31 31 02 00                            0   11..

 Inquiry EVPD Page #C6h

  0000: 00 C6 00 60 44 47 4D 50 02 00 00 00 81 10 02 00    ...`DGMP........

  0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0060: 00 00 00 00                                        ....

 Inquiry EVPD Page #C7h

  0000: 00 C7 00 44 68 69 6E 32 81 03 00 1C 20 02 00 A0    ...Dhin2.... ...

  0010: B8 0F 0B 50 20 02 00 A0 B8 0F 0B 4F FF 5C 10 00    ...P ......O.\..

  0020: 00 00 00 00 00 00 00 00 02 03 00 1C 20 02 00 A0    ............ ...

  0030: B8 0F 0B 51 20 02 00 A0 B8 0F 0B 4F FF 5D 10 00    ...Q ......O.]..

  0040: 00 00 00 00 00 00 00 00                            ........

 Inquiry EVPD Page #C8h

  0000: 00 C8 00 AB 65 64 69 64 01 03 00 10 60 0A 0B 80    ....edid....`...

  0010: 00 0F 0B 4F 00 00 00 2C 3E F1 31 04 3C 00 73 00    ...O...,>.1.<.s.

  0020: 69 00 63 00 61 00 30 00 30 00 32 00 5F 00 4E 00    i.c.a.0.0.2._.N.

  0030: 41 00 53 00 31 00 00 00 00 00 00 00 00 00 00 00    A.S.1...........

  0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0050: 00 00 00 00 00 00 00 00 00 10 60 0A 0B 80 00 0F    ..........`.....

  0060: 0B 4F 00 00 00 00 3E C3 53 FE 3C 00 53 00 41 00    .O....>.S.<.S.A.

  0070: 4E 00 5F 00 41 00 53 00 44 00 00 00 00 00 00 00    N._.A.S.D.......

  0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       ...............

 Inquiry EVPD Page #C9h

  0000: 00 C9 00 2C 76 61 63 63 81 01 00 00 00 00 00 00    ...,vacc........

  0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

  0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

 Inquiry EVPD Page #CAh

  0000: 00 CA 00 16 73 6E 62 69 00 00 00 00 00 00 00 00    ....snbi........

  0010: 00 00 00 00 00 00 00 00 00 00                      ..........

 Inquiry EVPD Page #D0h

  0000: 00 D0 00 14 01 03 00 10 60 0A 0B 80 00 0F 0B 4F    ........`......O

  0010: 00 00 00 00 3E 88 88 88                            ....>.S.

   Physical disk device state:

   Disk at Channel:ID 00:01 [Optimal]

   Disk at Channel:ID 00:02 [Optimal]

   Disk at Channel:ID 00:03 [Optimal]

   Disk at Channel:ID 00:04 [Optimal]

   Disk at Channel:ID 00:05 [Optimal]

   Disk at Channel:ID 00:06 [Reserved-Status]

   Disk at Channel:ID 00:07 [Optimal]

   Disk at Channel:ID 00:08 [Optimal]

   Disk at Channel:ID 00:09 [Optimal]

   Disk at Channel:ID 00:10 [Optimal]

   Disk at Channel:ID 00:11 [Optimal]

    Disk at Channel:ID 00:12 [Failed-WriteFailure]

   Disk at Channel:ID 00:13 [Optimal]

   Disk at Channel:ID 00:14 [Optimal]

   Disk at Channel:ID 00:15 [Optimal]

   Disk at Channel:ID 01:00 [Optimal]

   Disk at Channel:ID 01:01 [Optimal]

   Disk at Channel:ID 01:02 [Optimal]

   Disk at Channel:ID 01:03 [Optimal]

   Disk at Channel:ID 01:04 [Optimal]

   Disk at Channel:ID 01:05 [Optimal]

   Disk at Channel:ID 01:06 [Optimal]

   Disk at Channel:ID 01:07 [Optimal]

   Disk at Channel:ID 01:08 [Optimal]

   Disk at Channel:ID 01:09 [Optimal]

   Disk at Channel:ID 01:10 [Optimal]

   Disk at Channel:ID 01:11 [Optimal]

   Disk at Channel:ID 01:12 [Optimal]

   Disk at Channel:ID 01:13 [Optimal]

   Disk at Channel:ID 01:14 [Optimal]

   Disk at Channel:ID 01:15 [Optimal]

   Disk at Channel:ID 02:00 [Optimal]

   Disk at Channel:ID 02:01 [Optimal]

   Disk at Channel:ID 02:02 [Optimal]

   Disk at Channel:ID 02:03 [Optimal]

   Disk at Channel:ID 02:04 [Optimal]

   Disk at Channel:ID 02:05 [Optimal]

   Disk at Channel:ID 02:06 [Optimal]

   Disk at Channel:ID 02:07 [Optimal]

   Disk at Channel:ID 02:08 [Optimal]

   Disk at Channel:ID 02:09 [Optimal]

   Disk at Channel:ID 02:10 [Optimal]

 

If the selected device is a LUN that is presented by a RAID subsystem with an Infortrend controller in it, you will get the output that is highlighted in Blue.  If it is not an Infortrend controller, the software will report the EVPD data described in the Inquiry Page Viewersection.

 

Additional Information

Unless you (or your RAID provider) has configured the engine otherwise, you can query this RAID engine by sending the -I+ and -z command to any LUN.
Significantly  more information will be made available in future releases.
RAID subsystem manufacturers and VARs/OEMs mask the make & model of RAID engine they are using by changing the make and model fields. You may have a LSI-based subsystem and not know it.
By design, our software does NOT allow you to change any configurable parameters except for mode pages. You cannot use our software as a "configurator".
If you send the -z command to a device which is not a logical disk associated with a Mylex (or Infortrend) RAID engine, the device will reject the command and our software will just reject the command.
We support reporting all LSI defined physical device states.  The values that may be returned are shown in the LSI Drive Status Definitions table below. The state is shown between braces, so a drive in Optimal state will be reported as [Optimal] and Out of Service will be reported as [Out-of-Service].

 

LSI Drive Status Definitions

Status String

Meaning

Optimal

The drive is in good condition and is currently configured as part of a LUN or global hot spare.

Unassigned

The controller has detected a drive present, but the drive is not part of a configured logical unit.

Failed-CauseUnknown

Failed by alternate controller for reasons unknown. You must replace the drive.

Replaced

The controller has detected the replacement of a failed drive through a hot swap or an action from the host management software.

Wrong Drive Removed

The controller detected that a drive location which previously had an optimal drive now does not have a drive installed. Although there are other cases that can cause this error, the most likely is that the incorrect drive was removed or replaced by the user.

Out-of-Service

The drive was in a drive group that experienced an error during interrupted write processing that caused the LUN to transition to a DEAD state. Drives in the group that are in this state did not experience the error.

Failed-ReadFailure

Failed due to inability of drive to satisfy the read. You must replace the drive.

Wrong-Block-Size

The mode page for block size is improperly set. You may be able to resolve this with SANtools' mode page editor function.

Reserved-Status

Reserved for future use by RAID engine.

Failed-or-Missing

The drive does not respond. You must replace the drive.

Capacity<Minimum

The replaced drive does not have sufficient capacity to accommodate all of the LUNs in the drive group.

Failed-FormatFailure

Write error while formatting. You must replace the drive.

Failed-WriteFailure

Write error. You must replace the drive.

Failed-ByUser

Failed due to user command.

Offline-ByUser

The drive was in a drive group that has been marked offline by the user. The LUN will transition to the DEAD state. All of the drives in the group will report this status.

Failed-ControllerStorage

Failed by controller. You must replace the drive.

Non-Existent

Note: Drives in this state are ignored by SANtools. Nothing will be reported for the Channel/ID combination.