Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1005314.1 : Sun StorageTek 33x0 SCSI Array: How to verify SCSI HBA Connectivity.
PreviouslyPublishedAs 207423 Description The listed symptoms are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix. Symptoms : - Device disappeared - Cannot see device in format Purpose/Scope: This document assumes that either PCI Dual Ultra3 SCSI Adapter or PCI Dual Ultra3 SCSI Adapter 320 cards are installed. Steps to Follow Steps to follow NOTE : This Technical Instruction is a sub-set of <Document: 1008191.1> :"Troubleshooting Sun StorEdge [TM] SCSI Arrays from the OS . The steps below will help confirm that the HBA is visible to the OS and the device paths for the HBA have been built. Step 1 - Use the prtpicl command to verify HBA has been recognized. PCI Dual Ultra3 SCSI Adapter : # prtpicl -v -c scsi | grep ISP10160 :model QLGC,ISP10160 :model QLGC,ISP10160 PCI Dual Ultra3 SCSI Adapter 320 : # prtpicl -v -c scsi-2 | grep LSI,1030 :model LSI,1030 :model LSI,1030 If either command returns no output then verify hardware using probe-scsi from the ok prompt and replace card if necessary. Step 2 - Check to see if the module has been loaded into the kernel. Note : For Solaris[TM] 10 systems the qus and mpt drivers are included by default. PCI Dual Ultra3 SCSI Adapter : # modinfo | grep qus 29 13dc190 13402 241 1 qus (isp10160 HBA Driver 1.1) If the qus module is not loaded refer to <Document: 1018123.1> :Sun StorEdge[TM] PCI Dual Ultra3 SCSI Host Adapter Requirement PCI Dual Ultra3 SCSI Adapter 320 : # modinfo | grep mpt 38 102b8fec 28d14 211 1 mpt (MPT HBA Driver v1.7) If the mpt module is not loaded check for minimum OS and patch requirements. - The minimum operating system is Solaris 8 7/03, Solaris 9 12/03, or Solaris 9 8/03 x86. - Install Solaris 8 mpt driver patch 115275 - Install Solaris 9 kernel patch 118558 Step 3 - Check to make sure we have a device path built for the HBA. PCI Dual Ultra3 SCSI Adapter : # grep qus /etc/path_to_inst "/pci@1f,4000/pci@5/scsi@4" 0 "qus" "/pci@1f,4000/pci@5/scsi@5" 1 "qus" PCI Dual Ultra3 SCSI Adapter 320 : # grep mpt /etc/path_to_inst "/pci@1f,0/pci@1/scsi@1" 0 "mpt" "/pci@1f,0/pci@1/scsi@1,1" 1 "mpt" If the device paths do not show up in either instance then perform a reconfiguration reboot or attempt a devfsadm. The steps above confirm that the HBA is visible to the OS and the device paths for the HBA have been built. If there is still a problem return to <Document: 1008191.1> Troubleshooting Sun StorEdge [TM] SCSI Arrays from the OS. Product Sun StorageTek 3310 SCSI Array Sun StorageTek 3320 SCSI Array Internal Comments This document contains normalized content and is managed by the the ContentLead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below: Content Lead: [email protected] Feedback Alias: [email protected]
3310, 3320, hba connectivity, devfsadm, Jasper, Jasper 320, audited, normalized Previously Published As 89038 Change History Date: 2009-11-18 User Name: 79977 Action: Updated Comment: Currency check, [email protected], Volume disk content lead Date: 2007-07-03 User Name: 7058 Action: Approved Comment: Product code names are not allowed in Contract docs. Changed all instances of Jasper and Jasper 320 to PCI Dual Ultra3 SCSI Adapter and PCI Dual Ultra3 SCSI Adapter 320 respectively. Although the superset doc is still not ready for publication, I am going ahead with publication of this doc. Attachments This solution has no attachment |
||||||||||||
|