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-1633233.1
Update Date:2017-10-11
Keywords:
Solution Type  Technical Instruction Sure

Solution  1633233.1 :   SPARC M5-32 and M6-32 Servers: How to locate internal disks  

Related Items 
    

  • SPARC M6-32
    •  
  • SPARC M5-32
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx-32
    •  






In this Document


Goal


Solution


References


Applies to:  

SPARC M6-32 - Version All Versions to All Versions [Release All Releases]
SPARC M5-32 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.



Goal


The goal of this document to provide several methods to identify and locate internal HDD/SSD on SPARC M5-32 and M6-32 Servers.



Explorer  8.15 and higher includes disks/croinfo.out (CR 25026006). This file may simplify determination of HDD/SSD as the Solaris command output includes the receptacle (i.e., chassis slot).
If unable to deduce the HDD/SSD receptacle you may consider asking the customer to upgrade Explorer version to 8.15 or higher or manually request the below example command output.


The latter overview and document reference information may be used to manually decode HDD/SSD disk slots.


Solution


HDD/SSD identification with two simple commands:


The following three example Solaris commands make HDD/SSD identification simple via command output.  You can read the 'croinfo' man page for further display fields or list them on the command line by typing 'croinfo -?'.




## format will provide a list of connected disks

~# echo | format 
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t5000CCA0162F53C0d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca0162f53c0
          /dev/chassis/SYS/IOU0/HDD0/disk
       1. c0t5000CCA0162D4C04d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca0162d4c04
          /dev/chassis/SYS/IOU0/HDD1/disk
       2. c0t5000CCA0162A2BF8d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca0162a2bf8
          /dev/chassis/SYS/IOU0/HDD2/disk
       3. c0t5000CCA01621E3E0d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca01621e3e0
          /dev/chassis/SYS/IOU0/HDD3/disk
       4. c0t5000CCA0162A1AECd0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca0162a1aec
          /dev/chassis/SYS/IOU0/HDD4/disk
       5. c0t5000CCA01611DF14d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca01611df14
          /dev/chassis/SYS/IOU0/HDD5/disk
       6. c0t5000CCA0160CFAB0d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca0160cfab0
          /dev/chassis/SYS/IOU0/HDD6/disk
       7. c0t5000CCA01625F308d0 <HITACHI-H109060SESUN600G-A31A-558.91GB>
          /scsi_vhci/disk@g5000cca01625f308
          /dev/chassis/SYS/IOU0/HDD7/disk




## this croinfo command is easily matched to the format output and provides the receptacle information (i.e., slot)

# /usr/sbin/croinfo -o cdRmfs -t disk
c:occupant-compdev     d:occupant-devices                         R:receptacle-name  m:occupant-mfg  f:occupant-firm  s:occupant-serial
---------------------  -----------------------------------------  -----------------  --------------  ---------------  ----------------------------
c0t5000CCA0162F53C0d0  /devices/scsi_vhci/disk@g5000cca0162f53c0  /SYS/IOU0/HDD0     HITACHI         A31A             001249BV0W5F--------KNGV0W5F
c0t5000CCA0162D4C04d0  /devices/scsi_vhci/disk@g5000cca0162d4c04  /SYS/IOU0/HDD1     HITACHI         A31A             001249BTX85F--------KNGTX85F
c0t5000CCA0162A2BF8d0  /devices/scsi_vhci/disk@g5000cca0162a2bf8  /SYS/IOU0/HDD2     HITACHI         A31A             001249BS5ZGF--------KNGS5ZGF
c0t5000CCA01621E3E0d0  /devices/scsi_vhci/disk@g5000cca01621e3e0  /SYS/IOU0/HDD3     HITACHI         A31A             001249BLMTHF--------KNGLMTHF
c0t5000CCA0162A1AECd0  /devices/scsi_vhci/disk@g5000cca0162a1aec  /SYS/IOU0/HDD4     HITACHI         A31A             001249BS4V8F--------KNGS4V8F
c0t5000CCA01611DF14d0  /devices/scsi_vhci/disk@g5000cca01611df14  /SYS/IOU0/HDD5     HITACHI         A31A             001249B9UPAF--------KNG9UPAF
c0t5000CCA0160CFAB0d0  /devices/scsi_vhci/disk@g5000cca0160cfab0  /SYS/IOU0/HDD6     HITACHI         A31A             001249B748SF--------KNG748SF
c0t5000CCA01625F308d0  /devices/scsi_vhci/disk@g5000cca01625f308  /SYS/IOU0/HDD7     HITACHI         A31A             001249BNVZVF--------KNGNVZVF





## this croinfo command will list all available disk paths, particularly useful for multi-ported HDD


# /usr/sbin/croinfo -o Rcp -t disk
R:receptacle-name  c:occupant-compdev     p:occupant-paths
-----------------  ---------------------  --------------------------------------------------------------------------------------
/SYS/IOU0/HDD0     c0t5000CCA0162F53C0d0  /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162f53c1,0
 :                  ;                     /devices/pci@400/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162f53c2,0
/SYS/IOU0/HDD1     c0t5000CCA0162D4C04d0  /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162d4c05,0
 :                  ;                     /devices/pci@400/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162d4c06,0
/SYS/IOU0/HDD2     c0t5000CCA0162A2BF8d0  /devices/pci@600/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162a2bfa,0
 :                  ;                     /devices/pci@500/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162a2bf9,0
/SYS/IOU0/HDD3     c0t5000CCA01621E3E0d0  /devices/pci@600/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca01621e3e2,0
 :                  ;                     /devices/pci@500/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca01621e3e1,0
/SYS/IOU0/HDD4     c0t5000CCA0162A1AECd0  /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162a1aee,0
 :                  ;                     /devices/pci@400/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162a1aed,0
/SYS/IOU0/HDD5     c0t5000CCA01611DF14d0  /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca01611df16,0
 :                  ;                     /devices/pci@400/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca01611df15,0
/SYS/IOU0/HDD6     c0t5000CCA0160CFAB0d0  /devices/pci@600/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0160cfab1,0
 :                  ;                     /devices/pci@500/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0160cfab2,0
/SYS/IOU0/HDD7     c0t5000CCA01625F308d0  /devices/pci@600/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca01625f309,0
 :                  ;                     /devices/pci@500/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca01625f30a,0





 


Overview :

The server supports 2.5 inch SAS-format HDDs and SATA-format SSDs mounted in Oracle drive carriers.

An IOU (I/O unit) holds four EMSs and up to eight drives. SAS-format controllers in the EMSs control the SAS-format HDDs and SATA-format SSDs.

HDDs and SSDs are controlled by EMSs.
A SAS-format HDD has two ports, allowing redundant access by two EMSs. 
A SATA-format SSD has one port, so it can be accessed by only one EMS.

For redundancy, each SAS-format drive can be accessed by two EMSs. For additional redundancy, each EMS is located in different halves of the same IOU so that disk access is maintained even if one of the two IOBs (I/O switch boards) fails in an IOU.

The illustration on the left shows the redundant access to each SAS-format HDD.  The illustration on the right shows the nonredundant access to SATA-format SSDs in HDDx slots.


 


HDDSSD



Additional information


The following table provides information about how to match the EMS port (matching phy-num) to the iport number as reported by some Solaris commands :


 




iport 



EMS port 









1




0








2




1








4




2








8




3









Also note that the EMS port used to access an HDD is different from one EMS to another EMS. Which means that the  target / PhyNum (EMS port) / iport (as reported in the probe-scsi-all output) to access each disk is different. This can be summarized as following :








Target/PhyNum / iport  



HDD0 



HDD1 



HDD2 



HDD3 



HDD4 



HDD5 



HDD6 



HDD7 









EMS4


 
 


b / 2 / 4




c / 3 / 8


 
 


9 / 0 / 1




a / 1 / 2








EMS3




b / 2 / 4




c / 3 / 8


 
 


9 / 0 / 1




a / 1 / 2


 
 






EMS2


 
 


9 / 0 / 1




a / 1 / 2


 
 


b / 2 / 4




c / 3 / 8








EMS1




9 / 0 / 1




a / 1 / 2


 
 


b / 2 / 4




c / 3 / 8


 
 






 



For more information about M5-32 M6-32 devices path, refer to SPARC M5-32 and M6-32 Servers: Device Paths (Doc ID 1540545.1).
Other references :


    

  • SPARC M5-32 and SPARC M6-32 Servers Service Manual - Servicing HDDs, SSDs - p197
    • 

  • SPARC M5-32 and SPARC M6-32 Servers Administration Guide - Understanding EMS SAS Paths to the Internal Drives - p35
    • 







From Solaris / explorer

The various command to identify and locate the HDD/SSD installed are :


    

  • format
    • 

  • croinfo / diskinfo
    • 

  • cfgadm
    • 

  • prtpicl
    • 

  • fmtopo
    • 

  • prtconf
    • 




When the devchassis service is properly running,


# svcs -l devchassis
fmri         svc:/system/devchassis:daemon
name         /dev/chassis namespace support service
enabled      true
state        online
next_state   none
state_time   Fri Mar 07 02:30:40 2014
logfile      /var/svc/log/system-devchassis:daemon.log
restarter    svc:/system/svc/restarter:default
contract_id  134 
manifest     /lib/svc/manifest/system/devchassis.xml
dependency   require_all/error svc:/system/fmd (online)
dependency   require_all/restart svc:/system/fmd (online)

fmri         svc:/system/devchassis:cleanstart
name         /dev/chassis namespace support service
enabled      true
state        online
next_state   none
state_time   Fri Mar 07 02:27:50 2014
alt_logfile  /system/volatile/system-devchassis:cleanstart.log
restarter    svc:/system/svc/restarter:default
manifest     /lib/svc/manifest/system/devchassis.xml
dependency   require_all/none svc:/system/filesystem/usr (online)



the disks topology is directly available from :


    

  • format
    • 

  • croinfo / diskinfo
    • 




From the format/croinfo/diskinfo command output, the name, location and device path can be easily identified.
It's then easy to also find the disks in the cfgadm command output and retrieve the different paths to access the disks.

Example from an M5-32 with 8 HDDs


# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t5000CCA0162F46F0d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162f46f0
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD0/disk
       1. c0t5000CCA0162F5FE0d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162f5fe0
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD1/disk
       2. c0t5000CCA0162F5B40d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162f5b40
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD2/disk
       3. c0t5000CCA0162F7A28d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162f7a28
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD3/disk
       4. c0t5000CCA01603A7D8d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca01603a7d8
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD4/disk
       5. c0t5000CCA0162F5B78d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162f5b78
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD5/disk
       6. c0t5000CCA0162D4CD8d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162d4cd8
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD6/disk
       7. c0t5000CCA0162D4EE4d0 <HITACHI-H109060SESUN600G-A31A cyl 64986 alt 2 hd 27 sec 668>  solaris
          /scsi_vhci/disk@g5000cca0162d4ee4
          /dev/chassis/SPARC_M5-32.AK00087872//SYS/IOU2/HDD7/disk

# croinfo -o cRp
c:occupant-compdev     R:receptacle-name  p:occupant-paths                                                                       
---------------------  -----------------  ---------------------------------------------------------------------------------------
c0t5000CCA0162F46F0d0  /SYS/IOU2/HDD0     /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162f46f1,0 
 :                      :                 /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162f46f2,0 
c0t5000CCA0162F5FE0d0  /SYS/IOU2/HDD1     /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162f5fe1,0 
 :                      :                 /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162f5fe2,0 
c0t5000CCA0162F5B40d0  /SYS/IOU2/HDD2     /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162f5b41,0 
 :                      :                 /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162f5b42,0 
c0t5000CCA0162F7A28d0  /SYS/IOU2/HDD3     /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162f7a29,0 
 :                      :                 /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162f7a2a,0 
c0t5000CCA01603A7D8d0  /SYS/IOU2/HDD4     /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca01603a7d9,0 
 :                      :                 /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca01603a7da,0 
c0t5000CCA0162F5B78d0  /SYS/IOU2/HDD5     /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162f5b79,0 
 :                      :                 /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162f5b7a,0 
c0t5000CCA0162D4CD8d0  /SYS/IOU2/HDD6     /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162d4cd9,0 
 :                      :                 /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162d4cda,0 
c0t5000CCA0162D4EE4d0  /SYS/IOU2/HDD7     /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162d4ee5,0 
 :                      :                 /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162d4ee6,0 


# cfgadm -alv
Ap_Id                          Receptacle   Occupant     Condition  Information
When         Type         Busy     Phys_Id
...
IOU2-EMS1                      connected    configured   ok         Location: IOU2-EMS1
Mar  7 02:28 pci-pci/hp   n        /devices/pci@b00/pci@1/pci@0/pci@c:IOU2-EMS1
IOU2-EMS2                      connected    configured   ok         Location: IOU2-EMS2
Mar  7 02:28 pci-pci/hp   n        /devices/pci@b80/pci@1/pci@0/pci@0:IOU2-EMS2
IOU2-EMS3                      connected    configured   ok         Location: IOU2-EMS3
Mar  7 02:28 pci-pci/hp   n        /devices/pci@e80/pci@1/pci@0/pci@c:IOU2-EMS3
IOU2-EMS4                      connected    configured   ok         Location: IOU2-EMS4
Mar  7 02:28 pci-pci/hp   n        /devices/pci@e00/pci@1/pci@0/pci@0:IOU2-EMS4
...
c27                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1:scsi
c27::w5000cca0162d4cd9,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4CD8d0s0(sd0)
unavailable  disk-path    n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1:scsi::w5000cca0162d4cd9,0
c28                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi
c28::w5000cca0162d4ee5,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4EE4d0s0(sd1)
unavailable  disk-path    n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi::w5000cca0162d4ee5,0
c29                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1:scsi
c29::w5000cca0162f5b41,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5B40d0s0(sd2)
unavailable  disk-path    n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@1:scsi::w5000cca0162f5b41,0
c30                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi
c30::w5000cca0162f46f1,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F46F0d0s0(sd3)
unavailable  disk-path    n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi::w5000cca0162f46f1,0
c31                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4:scsi
c31::w5000cca0162f5b42,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5B40d0s0(sd2)
unavailable  disk-path    n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4:scsi::w5000cca0162f5b42,0
c32                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi
c32::w5000cca0162f7a29,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F7A28d0s0(sd4)
unavailable  disk-path    n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi::w5000cca0162f7a29,0
c33                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi
c33::w5000cca01603a7d9,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA01603A7D8d0s0(sd5)
unavailable  disk-path    n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi::w5000cca01603a7d9,0
c34                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2:scsi
c34::w5000cca0162f5fe1,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5FE0d0s0(sd14)
unavailable  disk-path    n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2:scsi::w5000cca0162f5fe1,0
c35                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4:scsi
c35::w5000cca0162d4cda,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4CD8d0s0(sd0)
unavailable  disk-path    n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@4:scsi::w5000cca0162d4cda,0
c36                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2:scsi
c36::w5000cca0162f5b79,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5B78d0s0(sd15)
unavailable  disk-path    n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2:scsi::w5000cca0162f5b79,0
c37                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi
c37::w5000cca0162d4ee6,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4EE4d0s0(sd1)
unavailable  disk-path    n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi::w5000cca0162d4ee6,0
c38                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi
c38::w5000cca01603a7da,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA01603A7D8d0s0(sd5)
unavailable  disk-path    n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi::w5000cca01603a7da,0
c39                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi
c39::w5000cca0162f46f2,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F46F0d0s0(sd3)
unavailable  disk-path    n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi::w5000cca0162f46f2,0
c40                            connected    unconfigured unknown
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@v0:scsi
c41                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8:scsi
c41::w5000cca0162f5b7a,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5B78d0s0(sd15)
unavailable  disk-path    n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8:scsi::w5000cca0162f5b7a,0
c42                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8:scsi
c42::w5000cca0162f5fe2,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F5FE0d0s0(sd14)
unavailable  disk-path    n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@8:scsi::w5000cca0162f5fe2,0
c43                            connected    configured   unknown
unavailable  scsi-sas     n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi
c43::w5000cca0162f7a2a,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F7A28d0s0(sd4)
unavailable  disk-path    n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi::w5000cca0162f7a2a,0




For SSD, only one path per SSD is available


# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t5001517803D0EE40d0 <ATA-INTEL SSDSA2BZ30-0362 cyl 35769 alt 2 hd 128 sec 128>  solaris
          /scsi_vhci/disk@g5001517803d0ee40
          /dev/chassis/SPARC_M6-32.AK00136495//SYS/IOU0/HDD0/disk
       1. c0t5001517803D10CF2d0 <ATA-INTEL SSDSA2BZ30-0362 cyl 35769 alt 2 hd 128 sec 128>  solaris
          /scsi_vhci/disk@g5001517803d10cf2
          /dev/chassis/SPARC_M6-32.AK00136495//SYS/IOU0/HDD1/disk

# croinfo -o cRp
c:occupant-compdev     R:receptacle-name  p:occupant-paths                                                                      
---------------------  -----------------  --------------------------------------------------------------------------------------
c0t5001517803D0EE40d0  /SYS/IOU0/HDD0     /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5001517803d0ee40,0
c0t5001517803D10CF2d0  /SYS/IOU0/HDD1     /devices/pci@300/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2/disk@w5001517803d10cf2,0




If, for some reasons (ex 17471094 M6-32: Diskinfo output failed to report SSD disks from EMS2 and EMS3 boards), the disk topology is not available, it's possible to use other methods to locate the disks.

Also, when LDOMs are configured, depending on how the EMS have been assigned to IO/root/guest domain, it may not be possible to use some commands.

Note : the following examples come from an M5-32 Pdom with HDD drives installed. 
    Similar decoding can be applied to SSD drives for which only one path will be reported.


prtpicl

The 'prtpicl -v' output provides the path and phy-num for each drive.
From the path and phy-num, it's possible to decode the location (see the table above).


# prtpicl -v | egrep -i "obp-path|phy-num"
                  :obp-path      /pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/disk@w5000cca0162f46f1,0 
                  :phy-num       0 
                  :obp-path      /pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/disk@w5000cca0162f46f2,0 
                  :phy-num       0x2 
...
                  :obp-path      /pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/disk@w5000cca0162d4ee5,0 
                  :phy-num       0x1 
                  :obp-path      /pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/disk@w5000cca0162d4ee6,0 
                  :phy-num       0x3 


/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4 ==> IOU2/EMS1
IOU2/EMS1 - phy-num 0x0 ==> HDD0

/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4 ==> IOU2/EMS3
IOU2/EMS3- phy-num 0x2 ==> HDD0

/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4 ==> IOU2/EMS4
IOU2/EMS4 - phy-num 0x1 ==> HDD7

/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4 ==> IOU2/EMS2
IOU2/EMS2 - phy-num 0x3 ==> HDD7





prtconf / cfgadm / fmtopo

The prtconf, cfgadm and fmtopo commands outputs provide the path and iport number for each drive.
From the path and iport number, it's possible to decode the location (see the table above).


# prtconf -v | grep iport | grep Path
                Path 1: /pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1/disk@w5000cca0162f46f1,0
                Path 17: /pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4/disk@w5000cca0162f46f2,0
...
                Path 9: /pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2/disk@w5000cca0162d4ee5,0
                Path 14: /pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8/disk@w5000cca0162d4ee6,0


# cfgadm -alv | egrep -e '(scsi-sas|Device|disk-path)'

unavailable  scsi-sas     n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi
c28::w5000cca0162d4ee5,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4EE4d0s0(sd1)
unavailable  disk-path    n        /devices/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@2:scsi::w5000cca0162d4ee5,0
unavailable  scsi-sas     n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi
c30::w5000cca0162f46f1,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F46F0d0s0(sd3)
unavailable  disk-path    n        /devices/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1:scsi::w5000cca0162f46f1,0
unavailable  scsi-sas     n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi
c37::w5000cca0162d4ee6,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162D4EE4d0s0(sd1)
unavailable  disk-path    n        /devices/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4/scsi@0/iport@8:scsi::w5000cca0162d4ee6,0
unavailable  scsi-sas     n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi
c39::w5000cca0162f46f2,0       connected    configured   unknown    Client Device: /dev/dsk/c0t5000CCA0162F46F0d0s0(sd3)
unavailable  disk-path    n        /devices/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4:scsi::w5000cca0162f46f2,0


# /usr/lib/fm/fmd/fmtopo -V | egrep -e '(initiator-port-pm|devid|EMS|label)' | uniq | more
    initiator-port-pm string    v0
    label             string    IOU2-EMS1
    label             string    /SYS/IOU2/EMS1
    initiator-port-pm string    1
    devid             string    id1,sd@n5000cca0162f46f0
    initiator-port-pm string    2
    devid             string    id1,sd@n5000cca0162f5fe0
    initiator-port-pm string    4
    devid             string    id1,sd@n5000cca01603a7d8
    initiator-port-pm string    8
    devid             string    id1,sd@n5000cca0162f5b78
    initiator-port-pm string    v0
    label             string    IOU2-EMS2
    label             string    /SYS/IOU2/EMS2
    initiator-port-pm string    8
    devid             string    id1,sd@n5000cca0162d4ee4
    initiator-port-pm string    2
    devid             string    id1,sd@n5000cca0162f7a28
    initiator-port-pm string    1
    devid             string    id1,sd@n5000cca0162f5b40
    initiator-port-pm string    4
    devid             string    id1,sd@n5000cca0162d4cd8

IOU2-EMS1 iport 1 => IOU2-EMS1 port 0 => HDD0
IOU2-EMS1 iport 2 => IOU2-EMS1 port 1 => HDD1
IOU2-EMS1 iport 4 => IOU2-EMS1 port 2 => HDD4
IOU2-EMS1 iport 8 => IOU2-EMS1 port 3 => HDD5
IOU2-EMS2 iport 8 => IOU2-EMS2 port 3 => HDD7
IOU2-EMS2 iport 2 => IOU2-EMS2 port 1 => HDD3
IOU2-EMS2 iport 1 => IOU2-EMS2 port 0 => HDD2
IOU2-EMS2 iport 4 => IOU2-EMS2 port 2 => HDD6

/pci@b00/pci@1/pci@0/pci@c/pci@0/pci@4 ==> IOU2/EMS1
IOU2/EMS1 - iport@1 ==> HDD0

/pci@e80/pci@1/pci@0/pci@c/pci@0/pci@4 ==> IOU2/EMS3
IOU2/EMS3- iport@4 ==> HDD0

/pci@e00/pci@1/pci@0/pci@0/pci@0/pci@4 ==> IOU2/EMS4
IOU2/EMS4 - iport@2 ==> HDD7

/pci@b80/pci@1/pci@0/pci@0/pci@0/pci@4 ==> IOU2/EMS2
IOU2/EMS2 - iport@8 ==> HDD7







From ILOM

When Oracle Hardware Management Pack is installed on the Solaris domain, it allows to provide information about Storage attached to the Pdom; including the internal disks.

However, the following unfixed bug may provide incorrect information
    Bug 17157717 : ILOM REPORTS INCORRECT HDD DEVICE LOCATION AND WWN COMPARED TO SOLARIS OUTPUT
    BUG 16887879 - ilom still reports internal disk drive after it has been removed


 


-> show -t /Servers/PDomains/PDomain_3/System/Storage/Disks
Target                                 | Property                                     | Value                                                              
---------------------------------------+----------------------------------------------+--------------------------------------------------------------------
/Servers/PDomains/PDomain_3/System/    | health                                       | OK
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | health_details                               | -
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | part_number                                  | H109060SESUN600G
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | serial_number                                | 001249BV1D3F        KNGV1D3F
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | location                                     | IOU2/HDD0 (IO Unit 2 Disk 0)
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | type                                         | HDD
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | manufacturer                                 | HITACHI
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | capacity                                     | 558 GB
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | device_name                                  | 5000CCA0162F5B78
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | raid_disk                                    | false
 Storage/Disks/Disk_16                 |                                              | 
/Servers/PDomains/PDomain_3/System/    | wwn                                          | 0x5000cca0162f5b7a
 Storage/Disks/Disk_16                 |                                              | 
...



Note that the disks information is not available as soon as the domain has booted successfully. It may take some time for the information to be available.

You can check if OHMP is installed and fully available as following

Not installed or host is not running Solaris


-> show  /Servers/PDomains/PDomain_3/System primary_operating_system primary_operating_system_detail

  /Servers/PDomains/PDomain_3/System
    Properties:
            primary_operating_system = Not Available
        primary_operating_system_detail = Comprehensive System monitoring is not available. Ensure the host is running with the Hardware Management Pack. 
                                          For download details go to http://www.oracle.com/technetwork/server-storage/servermgmt/downloads/index.html



or


-> show  /Servers/PDomains/PDomain_3/System primary_operating_system primary_operating_system_detail
/Servers/PDomains/PDomain_3/System
    Properties:
        primary_operating_system = Not Available
        primary_operating_system_detail = -


When OHMP is properly installed

-> show  /Servers/PDomains/PDomain_3/System primary_operating_system primary_operating_system_detail

  /Servers/PDomains/PDomain_3/System
    Properties:
        primary_operating_system = Oracle Solaris 11.1 SPARC
        primary_operating_system_detail = -








Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback