Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1566852.1
Update Date:2018-03-12
Keywords:

Solution Type  Technical Instruction Sure

Solution  1566852.1 :   How To Determine the Firmware, Chipset and World Wide Port Number (wwpn) of the 8-Port 3Gbps SAS/SATA HBA (Pandora)  


Related Items
  • Sun Storage 3Gb SAS RAID HBA, External
  •  
  • Sun Storage J4400 Array
  •  
  • Sun Storage J4500 Array
  •  
  • Sun Storage 2530 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
  • Sun Storage J4200 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>HBA>SN-DK: SCSI SAS HBA
  •  




In this Document
Goal
Solution
References


Created from <SR 3-7403462391>

Applies to:

Sun Storage J4400 Array - Version Not Applicable and later
Sun Storage J4500 Array - Version Not Applicable and later
Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 2530-M2 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

When troubleshooting storage connectivity issues, it becomes important to investigate the attachment point at the server -- the host bus adapter (HBA). For the SAS family of storage products (Sun Storage J4200, J4400, J4500, 2530 and 2530-M2 Arrays), the 8-Port 3Gbps SAS/SATA HBA is used. This HBA is also referred to as Option SG-XPCIE8SAS-X. Its part number is 375-3487 or 7050793 and its internal codename is Pandora. This document explains how to identify the chipset, firmware and world wide port number (wwpn) of the HBA.

Solution

In the following example, there are two external SAS HBA's connected to two Sun Storage 2530 Arrays. You can use the output from prtpicl and mapthadm to see the chipset, firmware and wwpn of each HBA. Let's start with prtpicl -v.

The output from prtpicl -v is extremely verbose. You can narrow the search by looking for the unique subsystem-id of the HBA. This HBA has a subsystem-id of 0x3150. The number of occurrences of 0x3150 in output lets you know the number of Pandora HBA's installed.
You can see all HBA subsystem-ID's at the HBASupportMatrix.

# prtpicl -v > prtpicl.txt
# view prtpicl.txt 

Once the file is called up in an editor, you can search for 0x3150. Other important parameters are highlighted in the following example.

                  :devfs-path    /pci@1e,600000/pci@0/pci@2
                  :driver-name   pxb_plx
                  :binding-name  pciex10b5,8532
                  :bus-addr      2
                  :instance      2
                  :_class        pciex
                  :name  pci
                     LSILogic,sas (scsi-2, 9c00000539)
                      :_fru_parent       (9c00000f1aH)
                      :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
                      ..................Skipping..............................
                      :model     LSI,1068E
                      :compatible       (9c0000055bTBL)
                       | pci13e9,58 |
                       | pciex1000,58 |
                       | pci1000,58 |
                       | AAPL,MPT |
                      :assigned-addresses
                      .................Skipping................................
                      :pcie-capid-reg    0x1
                      :pcie-capid-pointer        0x68
                      :pcie-aer-pointer  0x100
                      :ddi-intr-weight   0xa
                      :mpxio-disable     no
                      :ddi-vhci-class    scsi_vhci
                      :fm-ereport-capable
                      :fm-errcb-capable
                      :fm-dmachk-capable
                      :fm-accchk-capable
                      :pm-components    (9c0000054bTBL)
                       | NAME=mpt0 |
                       | 0=Off (PCI D3 State) |
                       | 3=On (PCI D0 State) |
                      :firmware-version  1.17.4.db
                      :num-phys  0x8
                      :scsi-reset-delay  0xbb8
                      :scsi-tag-age-limit        0x2
                      :scsi-watchdog-tick        0xa
                      :scsi-options      0x107ff8
                      :scsi-selection-timeout    0xfa
                      :initiator-interconnect-type       SATA
                      :initiator-port    500605b00080be80
                      :devfs-path        /pci@1e,600000/pci@0/pci@2/LSILogic,sas@0
                      :driver-name       mpt
                      :binding-name      pciex1000,58
                      :bus-addr  0
                      :instance  0
                      :_class    scsi-2
                      :name      LSILogic,sas

 

  • We can see from this output that the HBA is in PCI slot /pci@1e,600000/pci@0/pci@2 of the server.  To see whic PCI Slot that is, see <Document 1005907.1> SPARC Platforms: Matrix of Recognized Device Paths. The Device Tree -to- PCI Slot maps are there for over 100 servers.
  • The vendor-id must be 0x1000. If not, then this is not an externally connected Pandora HBA.
  • The device-id  must be 0x58. If not, then this is not an externally connected Pandora HBA.
  • The revision-id identifies the chip set on the card. You cannot change a chipset with a firmware upgrade. You must replace the HBA. This becomes important as the B1 revision does not support the latest firmware.
    • '0x2': This is a B1 HBA. (375-3487-01)
    • '0x8': This is a B3 HBA. (375-3487-02 or 375-3487-04)
    • '0x10': This is a C0 HBA. (375-3487-05 or higher)
    • '0x4': This is actually an internal-facing SAS HBA to connect internal disks, not an external-facing HBA.
  • The World Wide Node Number (wwnn) of the HBA is 500605b00080be80. There are 8 subsequent wwpn's derived from here.

We can use mpathadm to reinforce some of the data observed in prtpicl.

# mpathadm list initiator-port
    Initiator Port:  5080020000002999  <- an internal mpt port
    Initiator Port:  iqn.1986-03.com.sun:01:00144f002f44.460bb178,4000002a00ff  <- used in iscsi
    Initiator Port:  500605b00080be80  <- external Pandora HBA
    Initiator Port:  500605b001b719f0   <- external Pandora HBA


# mpathadm show initiator-port 500605b001b719f0
        Initiator Port:  500605b001b719f0
        Transport Type:  unknown
        OS Device File:  /devices/pci@1e,600000/pci@0/pci@8/LSILogic,sas@0


# mpathadm show initiator-port 500605b00080be80
        Initiator Port:  500605b00080be80
        Transport Type:  unknown
        OS Device File:  /devices/pci@1e,600000/pci@0/pci@2/LSILogic,sas@0

 




Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback