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-1559430.1
Update Date:2015-06-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1559430.1 :   Fujitsu M10-1/M10-4/M10-4S Disk Naming Scheme When Installing a Solaris 11 PPAR  


Related Items
  • Fujitsu M10-4
  •  
  • Fujitsu M10-4S
  •  
  • Fujitsu M10-1
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Fujitsu M10
  •  




In this Document
Goal
Solution
References


Applies to:

Fujitsu M10-1 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

The goal of this document is to explain how to map the disk device names used by Solaris 11 on a M10-4S PPAR to a physical device

Solution

When Solaris 11 is being installed onto M10-4S PPAR it will present the possible disks to be used for install during an interactive install using the following device name scheme.  This is unlike previous versions of Solaris that presented disk name using the traditional cxtxdx format.

scsi        558.9       029F_HDD00                  TOSHIBA
scsi        558.9       029F_HDD01                  TOSHIBA

These disk names are generated by the devchassis filesystem that is used on Solaris 11 which in turn is using device names presented to it by FMD. 

If you want to map these disks to a physical disk with an M10-4S building block some extra steps are required.   There are a few possible method that can be used.

 

Method 1

Check the disk name against the output of the showhardconf output on the XSCF.  This output has been cropped, but you'll notice that the serial number of the CMUL is PP1237029F is this example. 

SPARC M10-4S;

    + Serial:2081225002; Operator_Panel_Switch:Locked;
    + System_Power:On; System_Phase:Cabinet Power On;
    Partition#0 PPAR_Status:Running;
    BB#00 Status:Normal; Role:Master; Ver:2041h; Serial:2081225002;
        + FRU-Part-Number:CA07361-D202 A0                         ;
        + Power_Supply_System: ;
        + Memory_Size:256 GB;
        CMUL Status:Normal; Ver:0101h; Serial:PP1237029F  ;
            + FRU-Part-Number:CA07361-D941 C3   /7060911              ;
            + Memory_Size:128 GB;

 

scsi        558.9       029F_HDD00                  TOSHIBA
scsi        558.9       029F_HDD01                  TOSHIBA

If you compare the last four characters of the CMUL serial number to the disk device present by Solaris we can see that disks 029F_HDD00 and 029F_HDD01 are located physically in BB#00

Method 2

Prior to starting the Solaris install you can start a shell using option 3 and the use the croinfo, diskinfo or format commands to check the disk configuration.

This croinfo output has been cropped, but it's straight forward to match the devchassis name to the SAS address of the disk shown in probe-scsi-all and the ok prompt. 
For example:-

# croinfo
D:devchassis-path                                        t:occupant-type  c:occupant-compdev
----------------------------------------------------------- ---------------  ---------------------
/dev/chassis/SYS/BB0/CMUL/HDD0                               -       -
/dev/chassis/SYS/BB0/CMUL/HDD1                               -      -
<snip>
/dev/chassis/FUJITSU-BBEXP.500000e0e06d457f/029F_HDD00/disk  disk c2t5000039428285ADEd0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d457f/029F_HDD01/disk  disk c2t50000394083211FEd0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d457f/029F_HDD02       -  -
<snip>

{0} ok probe-scsi-all
/pci@8000/pci@4/pci@0/pci@0/scsi@0

FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00

Target a
  Unit 0   Disk   TOSHIBA  MBF2600RC        3706    1172123568 Blocks,
600 GB
  SASDeviceName 5000039428285adc  SASAddress 5000039428285ade  PhyNum 0
Target b
  Unit 0   Disk   TOSHIBA  MBF2600RC        3706    1172123568 Blocks,
600 GB
  SASDeviceName 50000394083211fc  SASAddress 50000394083211fe  PhyNum 1
Target c
  Unit 0   Encl Serv device   FUJITSU  BBEXP            0d32
  SASAddress 500000e0e06d457d  PhyNum 14

You can see from the above output that 029F_HDD00 maps to the "Target a" disk.  It is then possible to use doc id 1543194.1 to map the physical device path /pci@8000/pci@4/pci@0/pci@0/scsi@0 to the relevant LSB which is turn should allow you to get to the physical BB id.


Method 3

Once again using option 3 to start a shell before going into the Solaris 11 install.  Use the output of the /usr/lib/fm/fmd/fmtopo -x command to map the devchassis disk name to the serial number of CMUL.  You can see that the last four character of "fru-serial" variable match the devchassis disk name as shown in method 1.

<propval name='FRU' type='fmri'
value='hc://:chassis-mfg=unknown:chassis-name=ORCL,SPARC64-X:chassis-part=CA07
361-D202 A0
:chassis-serial=2081225002:fru-serial=PP1237029F:fru-part=7060911/chassis=
0/cpuboard=0' />
<propval name='label' type='string' value='/BB0/CMUL' />
</propgroup>
<propgroup name='authority' name-stability='Private'
data-stability='Private' version='1' >
<propval name='chassis-mfg' type='string' value='unknown' />
<propval name='chassis-name' type='string' value='ORCL,SPARC64-X' />
<propval name='chassis-part' type='string' value='CA07361-D202 A0
                  ' />
<propval name='chassis-serial' type='string' value='2081225002' />
</propgroup>

 

References

<NOTE:1543194.1> - Fujitsu M10-1, M10-4 and M10-4s Device Paths

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