Skip to main content

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 Updating the SPARC M12 System to Oracle Solaris 11.2


Notes on Updating the SPARC M12 System to Oracle Solaris 11.2
Notes on Enabling MPxIO
The device path name of an internal SAS disk or an SSD may be changed when Oracle Solaris 11.1 is updated to Oracle Solaris 11.2 or later. You can boot Oracle Solaris even when the device path name is changed. However, if any application or backup software specifies the device path name of the internal SAS disk or the SSD directly, the device path may not be available for reference.
Cause
The cause of this is that updating from Oracle Solaris 11.1 to Oracle Solaris 11.2 changes the default MPxIO setting of the internal SAS disk or the SSD from disabled to enabled. For the target internal SAS disks and SSDs, see Table 4-2. For an example of a device path change, see Table 4-3.
Table 4-2  Default MPxIO Setting on an Internal SAS Disk and SSD
Product Name Vendor Name Default 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 Disabled Disabled Enabled
SPME3A11*/
7105508, 7106318 (*1)
7105571, 7106322 (*2)		 MBF2600RC
AL13SEB600
AL13SEB600AL14SE
AL13SEB600AL15SE		      
900GB SAS
disk drive		 TOSHIBA Disabled Disabled Disabled
SPME3B11*/
7111257, 7111260 (*1)
7111261, 7111262 (*2)		 AL13SEB900
AL13SEB900AL14SE
AL13SEB900AL15SE		      
1.2TB SAS
disk drive		 TOSHIBA Disabled Disabled Disabled
SPME3C11*/
7120206, 7120207 (*1)
7120208, 7120209 (*2)		 AL15SE12NFUJ1.2T      
400GB SAS SSD TOSHIBA Disabled Disabled Disabled
SPME3Y32*/
7115093, 7115094 (*1)
7115095, 7115096 (*2)		 PX04SMB04FUJ400G      
400GB SAS SSD SEAGATE Disabled Disabled Disabled
SPME3Y33*/ 
7604145 (*1)
7604146 (*2)		 XS400ME70084      
800GB SAS SSD TOSHIBA Disabled Disabled Disabled
SPME3Y41*/
7119191, 7119192 (*1)
7119187, 7119188 (*2)		 PX04SMB08FUJ800G      
800GB SAS SSD SEAGATE Disabled Disabled Disabled
SPME3Y42*/ 
7604147 (*1)
7604148 (*2)		 XS800ME70084      
*1 These are factory default drives.
*2 These are used for expansion in the field.
Table 4-3  Example of the Device Path Change Before and After MPxIO Enabling
  Device Path Name Before MPxIO is Enabled Device Path Name After MPxIO is Enabled
Physical device path name /pci@8800/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000394281b5312,0 /scsi_vhci/disk@g50000394281b5310
Logical device path name /dev/rdsk/c2t50000394281B5312d0 /dev/rdsk/c0t50000394281b5310d0
Note that the device path name is not changed if MPxIO of an internal SAS disk or SSD of the SPARC M12 is enabled manually before the updating to Oracle Solaris 11.2.
Corrective Action
Take the following actions after updating to Oracle Solaris 11.2.
- When the physical device path name can be changed
Confirm the physical device path name by using the procedure shown in Procedure for Confirming the Device Path. Change the device path of the internal SAS disk or SSD directly specified in backup software or application programs to the confirmed device path name.
- When the physical device path name cannot be changed
Execute the following command and forcibly disable the MPxIO setting of the internal SAS disk and SSD.
# stmsboot -D mpt_sas -d
Procedure for Confirming the Device Path
In the following procedure, you can confirm the device path name, vendor name, product name, and enabled/disabled state of MPxIO of the internal SAS disk or SSD in the SPARC M12. If MPxIO is already enabled, the character string "scsi_vhci" appears in the physical device path name of the internal SAS disk or SSD.
- Display example when MPxIO for the internal SAS disk or SSD is enabled

The physical device path name includes the character string "scsi_vhci". So, MPxIO is enabled.

The format command omits a part of the logical device path name to display. The actual name of the logical device path is the path name with "/dev/rdsk" added.
# 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
- Display example when MPxIO for the internal SAS disk or SSD is not enabled

The physical device path name does not include the character string "scsi_vhci". So, MPxIO is disabled.

The format command omits a part of the logical device path name to display. The actual name of the logical device path is the path name with "/dev/rdsk" added.
# 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
/dev/chassis/FUJITSU-BBEXP. 500000e0e06d31bf/03N0_HDD00/disk
Notes on Boot Switching by beadm
Boot environment switching with the beadm command or with the pkg command may fail with the output of an error message where Oracle Solaris 11.1 or later is installed on the internal SAS disk or the SSD.
- Message example 1
# beadm activate S11U1SRU20B04-z_stress-2.10-1
Error while accessing "/dev/rdsk/c2t500003942823F352d0s0":
No such file or directory
Unable to activate S11U1SRU20B04-z_stress-2.10-1.
Error installing boot files.
- Message example 2
# beadm activate S11U1SRU20B04-z_stress-2.10-1
....
Error while accessing "/dev/rdsk/c2t500003942823F352d0s0":
No such file or directory
Unable to activate S11U1SRU20B04-z_stress-2.10-1.
Error installing boot files.
....
Cause
This occurred because the MPxIO device path is not properly inherited by beadm or pkg when the internal SAS disk or SSD is made into a multipath type (MPxIO).
Corrective Action
Execute the following command, and then execute the boot environment switching command again.
# /usr/sbin/zpool status

Top of Page