How to Determine Which 8-Port 3Gbps SAS Host Bus Adapter(HBA) Is Attached to a Sun Storage J4000 Array

Asset ID:	1-71-1567092.1
Update Date:	2013-09-04
Keywords:

Solution Type Technical Instruction Sure

Solution 1567092.1 : How to Determine Which 8-Port 3Gbps SAS Host Bus Adapter(HBA) Is Attached to a Sun Storage J4000 Array

Applies to:

Sun Storage J4400 Array - Version Not Applicable and later
Sun Storage J4500 Array - Version Not Applicable and later
Sun Storage 3Gb SAS PCI-X HBA - Version Not Applicable and later
Sun Storage J4200 Array - Version Not Applicable and later
Sun Storage 3Gb SAS RAID HBA, External - Version Not Applicable and later
Information in this document applies to any platform.

Goal

Oracle has qualified two different 8-Port, 3Gbps, SAS Host Bus Adapters (HBA's) for the Sun Storage J4000 Arrays. Each HBA may be referred to in several ways:

PCI Express 8-Port Host Adapter, Option SG-XPCIE8SAS-E-Z, P/N 7050793 or 375-3487, Code Name Pandora
8-Port SAS RAID External HBA (External), Option SGXPCIESAS-R-EXT-Z, P/N 375-3537, Code name Prometheus

In order to diagnose and repair problems with the J4000 array, it is important to know the attachment point on the server. This document will help identify which HBA is connected to the J4000 for Solaris hosts. Pandora provides connectivity to the J4000 arrays as a simple JBOD device ("just a bunch of disks"). Prometheus is a hardware RAID HBA.

Regardless of which HBA is used, you will still be able to register and administer your J4000 with Common Array Manager (CAM)

Solution

The best method to determine which HBA is attached to the J4000 is to look at output from prtpicl -v output from the Solaris server the HBA is installed in. As the output is very verbose, searching for the unique subsystem-id associated with each HBA is best.

The Pandora HBA has a subsystem ID of 0x3150.
The Prometheus HBA has a subsystem ID of 0x287.

More information on all HBA subsystem ID's at HBASupportMatrix.

The sample output below shows that there is a Prometheus HBA at /pci@7c0/pci@0/pci@9. To identify which PCI slot that is, see <Document 1005907.1> SPARC Platforms: Matrix of Recognized Device Paths.

                  :devfs-path    /pci@7c0/pci@0/pci@9
                  :driver-name   pcieb
                  :binding-name pciexclass,060400
                  :bus-addr      9
                  :instance      11
                  :_class        pciex
                  :name pci
                     scsi (scsi-2, ab00001563)
                      :Label     PCIE2
                      :DeviceID 0
                      :UnitAddress       0
                      :vendor-id         0x9005
                      :device-id         0x285
                      :revision-id       0x9
                      :subsystem-vendor-id       0x108e
                      :subsystem-id      0x287
                      :class-code        0x10400
                      :cache-line-size   0x10
                      :interrupts        00 00 00 01
                      :fcode-rom-offset 0x11800
                      :device_type       scsi-2
                      :wide      0x10
                      :version   0.00.01
                      :reg

The Pandora HBA will display subsystem-id 0x3150. <Document 1566852.1> How To Determine the Firmware, Chipset and World Wide Port Number (wwpn) of the 8-Port 3Gbps SAS/SATA HBA is a good reference to learn more about this HBA.

                 :devfs-path    /pci@780/pci@0/pci@8
                  :driver-name   pcieb
                  :binding-name pciexclass,060400
                  :bus-addr      8
                  :instance      3
                  :_class        pciex
                  :name pci
                     LSILogic,sas (scsi-2, ab00000318)
                      :Label     PCIE0
                      :DeviceID 0
                      :UnitAddress       0
                      :vendor-id         0x1000
                      :device-id         0x58
                      :revision-id       0x8
                      :subsystem-vendor-id       0x1000
                      :subsystem-id      0x3150
                      :class-code        0x10000
                      :cache-line-size   0x10
                      :interrupts        00 00 00 01
                      :fcode-rom-offset 0xb400
                      :device_type       scsi-2
                      :wide      0x10
                      :version   1.00.49
                      :reg

Although the prtpicl -v method is bit cumbersome, it is always correct. Other quicker verification techniques are helpful and usually correct, but there may be exceptions. To further verify a Prometheus HBA, view the output of the format command. If the output reads STKRAIDEXT in the inquiry string for the virtual disk, this is a Prometheus HBA. If the strings reads STKRAIDINT, then this is NOT a Prometheus HBA.

102. c7t1d0 <Sun-STKRAIDEXT-V1.0 cyl 36417 alt 2 hd 255 sec 63>
/pci@7c0/pci@0/pci@9/scsi@0/disk@1,0

The Pandora HBA will typically report an inquiry string with the disk manufacturer's name. For example:

99. c5t46d0 <ATA-HITACHI HUA7250S-AC5A-465.76GB>
/pci@7c0/pci@0/pci@8/LSILogic,sas@0/sd@2e,0

Lastly, the Prometheus HBA is a hardware RAID HBA and has its own interface. If the arcconf command generates information about the HBA, then it is a Prometheus.

# /opt/StorMan/arcconf GETVERSION
Controllers found: 1
Controller #1
==============
Firmware           : 5.2-0 (17757)
Staged Firmware    : 5.2-0 (17757)
BIOS               : 5.2-0 (17757)
Driver             : 2.2-3 (1)
Boot Flash         : 5.2-0 (17757)
Command completed successfully.

Attachments

This solution has no attachment