Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu SPARC M12 Product Notes for XCP 4010 - 4040 / XCP 3021 - XCP 3130 >
  9. Notes on Internal SAS Disks, SSDs, and Oracle Solaris MPxIO Settings

Contents

  1. Preface
  2. Chapter 1 Latest Information
    1.  Latest Information
    2.  Revision Information
  3. Chapter 2 Software Requirements
    1. Click Supported Firmware and Oracle Solaris Versions
    2.  Web Browser
    3.  Software Supporting Remote Storage
    4.  XCP and Oracle Solaris Version Supporting Power Aware Dispatcher Function
    5.  How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC
    6. Click Notes on Memory
    7. Click Notes on Mixing Different Hardware
    8.  Obtaining the SAS-2 Integrated RAID Configuration Utility
  4. Chapter 3 Information on XCP
    1. Click Latest Information on XCP
    2.  XCP Firmware Versions and Support Information
    3. Click Notes and Restrictions
    4. Click Problems With XCP and Workarounds
  5. Chapter 4 Information on Oracle Solaris
    1. Click Notes and Restrictions
    2. Click Problems With Oracle Solaris and Workarounds
  6. Chapter 5 Information on SPARC M12 System Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 Information on the PCI Expansion Unit
    1.  PCI Expansion Unit Firmware Versions and Support Information
    2. Click Direct I/O Function for the PCI Expansion Unit
    3. Click Problems With the PCI Expansion Unit and Workarounds
  8. Chapter 7 Information on SPARC M12 Manuals

Notes on Internal SAS Disks, SSDs, and Oracle Solaris MPxIO Settings


Notes on Internal SAS Disks, SSDs, and Oracle Solaris MPxIO Settings
We recommend using the internal SAS disks and SSDs of the SPARC M12 with the Oracle Solaris MPxIO setting enabled.
Cause
This can enhance redundancy because access continues even when the communication path between an internal SAS controller and an internal SAS disk or SSD is degraded due to a failure, etc.
Note that you can set MPxIO to enabled by using the bundled tool with Enhanced Support Facility 5.2 or later.
Note - Only SPARC M12 systems sold by Fujitsu in Japan support Enhanced Support Facility (ESF).
Target Internal SAS Disks and SSDs
Whether you need to make the Oracle Solaris MPxIO setting depends on the product name of the internal SAS disk or the SSD mounted in the SPARC M12, and the Oracle Solaris version, as shown in Table 4-1.
Table 4-1  Necessity of MPxIO Setting for an Internal SAS Disk or SSD
Product Name Vendor Name Necessity of MPxIO Setting
Fujitsu/Oracle Product ID Product Name Oracle Solaris
10 1/13		 Oracle Solaris
11.1		 Oracle Solaris
11.2 or Later
600GB SAS
disk drive		 TOSHIBA Required Required Not required(*1)
SPME3A11*/
7105508, 7106318 (*3)
7105571, 7106322 (*4)		 MBF2600RC (*5)
AL13SEB600 (*5)
AL13SEB600AL14SE
AL13SEB600AL15SE		      
900GB SAS
disk drive		 TOSHIBA Required Required Required
SPME3B11*/
7111257, 7111260 (*3)
7111261, 7111262 (*4)		 AL13SEB900 (*5)
AL13SEB900AL14SE
AL13SEB900AL15SE		      
1.2TB SAS
disk drive		 TOSHIBA Required Required Required
SPME3C11*/
7120206, 7120207 (*3)
7120208, 7120209 (*4)		 AL15SE12NFUJ1.2T (*5)      
400GB SAS SSD TOSHIBA Required Required Required
SPME3Y32*/
7115093, 7115094 (*3)
7115095, 7115096 (*4)		 PX04SMB04FUJ400G (*5)      
400GB SAS SSD SEAGATE Required Required Required
SPME3Y33*/ 
7604145 (*3)
7604146 (*4)		 XS400ME70084 (*5)      
800GB SAS SSD TOSHIBA Required Required Required
SPME3Y41*/
7119191, 7119192 (*3)
7119187, 7119188 (*4)		 PX04SMB08FUJ800G (*5)      
800GB SAS SSD SEAGATE Required Required Required
SPME3Y42*/ 
7604147 (*3)
7604148 (*4)		 XS800ME70084 (*5)      
When the internal hardware RAID is specified
   Not required(*2) Not required(*2) Not required(*2)
*1 MPxIO is enabled by default on Oracle Solaris. So, you need not to perform the setting.
*2 Since the internal hardware RAID is not subject to the MPxIO setting, it does not require the setting.
*3 These are factory default drives.
*4 These are used for expansion in the field.
*5 This is a product name set to the scsi_vhci.conf.
For 600 GB SAS disk drives, set both MBF2600RC and AL13SEB600 for the product names.
For other disk drives (not 600 GB SAS), set only the product name indicated at (*5).
Confirming the Product Name, Vendor Name, and MPxIO State of the Internal SAS Disk or SSD
To determine whether you need to make the MPxIO setting, confirm the product name, vendor name, and device path name of the internal SAS disk or SSD of the SPARC M12, and see Table 4-1.
If MPxIO is already enabled, the character string "scsi_vhci" appears in the device path name of the internal SAS disk or the SSD.

  1. When the MPxIO setting is enabled
    In the following example, "scsi_vhci" appears in the device path name. So, the MPxIO setting is enabled.
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t50000394281b5310d0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>

Logical device path name Vendor name Product name
/scsi_vhci/disk@g50000394281b5310
Physical device path name
/dev/chassis/FUJITSU-BBEXP. 500000e0e06d31bf/03N0_HDD00/disk
:
  1. When the MPxIO setting is disabled
    In the following example, "scsi_vhci" does not appear in the device path name. So, the MPxIO setting is disabled.
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c2t50000394281B5312d0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>

Logical device path name Vendor name Product name
/pci@8800/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000394281b5312,0
Physical device path name
:
Procedure for Enabling MPxIO
Log in as a user with administrator privileges to make this setting.
  1. Add the information (the vendor name and product name) of a disabled internal SAS disk or SSD.
  1. - For Oracle Solaris 11 and later
  1. Add the information (the vendor name and the product name) for the disabled internal SAS disk or SSD to the scsi_vhci.conf file in the /etc/driver/drv folder.
    If the /etc/driver/drv folder does not have the scsi_vhci.conf file, copy and use /kernel/drv/scsi_vhci.conf.
    For details on how to set the scsi_vhci.conf file, see the online manual.
scsi-vhci-failover-override ="TOSHIBA MBF2600RC", "f_sym",
Vendor name Product name
"TOSHIBA AL13SEB600", "f_sym";
Vendor name Product name
  1. - For Oracle Solaris 10
  1. Add the information (the vendor name and product name) of the disabled internal SAS disk or SSD to the /kernel/drv/scsi_vhci.conf file.
device-type-scsi-options-list ="TOSHIBA MBF2600RC", "sym-opt",
Vendor name Product name
"TOSHIBA AL13SEB600", "sym-opt";
Vendor name Product name
sym-opt = 0x1000000;
  1. Enable MPxIO with the stmsboot command.
    For details on the stmsboot command, see the online manual.
# stmsboot -D mpt_sas -e
  1. If the following message is output, continue by executing the stmsboot -u command.
# stmsboot -D mpt_sas -e
STMS is already enabled. No changes or reboots needed
# stmsboot -u
  1. Executing the stmsboot command restarts the system of the domain, and enables MPxIO of the internal SAS disk or the SSD. After the restart, the target device path name is changed.
    You need to change the device path name in application programs, etc., if they specify the name directly.
  1. Confirm that MPxIO is enabled.
    If MPxIO is enabled, the character string "scsi_vhci" appears in the device path name.
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t50000394281b5310d0 <TOSHIBA-MBF2600RC-...>

  Logical device path name Vendor name Product name
/scsi_vhci/disk@g50000394281b5310
  Physical device path name
  1. If the ZFS system volume is installed in an internal SAS disk or SSD of a multipath type (MPxIO), confirm that the volume status is normal.
# /usr/sbin/zpool status
...

Top of Page