Minimum Supported Versions of the OS, Firmware, and Software
Required OS Patches and Package Updates
Oracle Solaris 11 OS Package Updates
Important Firmware Upgrade Required Prior to Mixing SAS-1 and SAS-2 Components
Identifying Drive Logical Device Names and Physical Locations
Correlate WWN Device Names With Physical Locations (diskinfo Command)
Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)
Sun Type 6 Keyboards are Not Supported by SPARC T4 Series Servers
PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard (CR 7031216)
2-Meter USB Cable Length Limit (7048419)
During a Reboot After an Unrecoverable Hardware Error, CPUs Might Not Start (CR 7075336)
Blue LED on Drive Does Not Light When the Drive is Ready to Remove (CR 7082700)
Firmware, OS, and Other Software Issues
fault.memory.memlink-uc Fault Did Not Cause Panic as Stated by System Message (CR 6940599)
Timestamp for an Oracle ILOM Fault/Critical Event Might Be off by One Hour (CR 6943957)
Fault Management Sometimes Sends Resolved Cases to the SP (CR 6983432)
Units Used to Define the MIB Power Management Time Limit are Reported in Seconds (CR 6993008)
Spurious Interrupt Message in System Console When Using Oracle VTS (CR 7038266)
Intermittent Link Training Timeout Displayed During Power Cycles (CR 7043201)
The cfgadm Command Might Fail on SG-SAS6-REM-Z or SGX-SAS6-REM-Z HBAs (CR 7044759)
Message From cpustat Refers to Processor Documentation Incorrectly (CR 7046898)
Using trapstat Might Cause a Panic (CR 7052070)
reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters (CR 7050975)
PCIe Correctable Errors Might Be Reported (CR 7051331)
Watchdog Timeouts Seen With Heavy Workloads and Maximum Memory Configurations (CR 7083001)
ereport.fm.fmd.module Generated During a Reboot of an SDIO Domain (CR 7085231)
Oracle VTS dtlbtest Hangs When CPU Threading Mode is Set to max-ipc (CR 7094158)
The Oracle Solaris OS now uses the worldwide number (WWN) in place of the target ID field (tn) in drive logical device names for SAS-2 storage controllers.This change affects how you correlate a drive's logical name with the drive's physical location.
These points are key to understanding the impact of this change:
Before the change to using WWNs, drives were known to the OS by a logical name such as c0t0d0. This logical name mapped to the drive's physical location.
With the change, the device identifier for drives now has this form: cntWWNdn, where WWN is a unique hexadecimal value.
An example of a logical device name is:
c0t5000C50033438DBBd0
This WWN value does not map in a predictable way to the physical location of the drive.
The OBP and the OS use different WWN numbers to identify a drive. This is explained further in Correlate WWN Device Names With Physical Locations (diskinfo Command).
Here are some examples of situations when you must correlate a logical device name with a drive's physical location:
When downloading the OS over a network, you must specify the logical device name of the drive in slot 0 (the default boot device). In addition, if you use Oracle Solaris Jumpstart, you must use a specific WWN syntax. See Oracle Solaris Jumpstart WWN Syntax.
If you run the format command, you must select one of the logical device names presented. To ensure you select the correct drive, you must correlate a logical device name with the physical drive.
If you view a system message that lists a drive's logical device name, you might need to identify the slot in which the drive is installed.
To correlate drive logical device names with physical locations or the other way around:
From the Oracle Solaris 10 8/10 OS, use the diskinfo command. See Correlate WWN Device Names With Physical Locations (diskinfo Command).
At the OBP ok prompt, use the probe-scsi-all command. See Correlate WWN Device Names With Physical Locations (probe-scsi-all Command).
The diskinfo command, a new disk and slot identification utility, was introduced in Oracle Solaris 10 8/11 OS and in the kernel patch 144500-19 (or later).
If you do not have access to the OS, for example, if the server module is not booted, see Correlate WWN Device Names With Physical Locations (probe-scsi-all Command).
If your OS does not provide the diskinfo command, refer to the SPARC and Netra SPARC T4 Series Servers Administration Guide for alternative methods.
# diskinfo -a Enclosure path: 1114BD0ACC-physical-hba-0 Chassis Serial Number: 1114BD0ACC-physical-hba-0 Chassis Model: ORCL,SPARC-T4-1B Label Disk name Vendor Product Vers ---------- ---------------------- -------- ---------------- ---- /SYS/HDD0 c0t5000C50033438DBBd0 SEAGATE ST930003SSUN300G 0B70 /SYS/HDD1 c0t5000C50005C15803d0 SEAGATE ST930003SSUN300G 0468
For this server module:
/SYS/HDD0 represents a drive in slot 0.
/SYS/HDD1 represents a drive in slot 1.
In this example, the drive installed in slot 0 has a logical device name of c0t5000C50033438DBBd0.
Note - The diskinfo command provides a variety of disk information depending on the command options you specify. For more information, type diskinfo -h and refer to the diskinfo(1M) man page.
If you have access to the OS, you might be able to use the diskinfo command instead. See Correlate WWN Device Names With Physical Locations (diskinfo Command).
{0} ok probe-scsi-all /pci@400/pci@1/pci@0/pci@c/LSI,sas@0 <===== SAS Controller FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c50033438dbb SASAddress 5000c50033438db9 PhyNum 0 <=HD,slot 0 Target b Unit 0 Disk SEAGATE ST930003SSUN300G 0468 585937500 Blocks, 300 GB SASDeviceName 5000c50005c15803 SASAddress 5000c50005c15801 PhyNum 1 <=HD,slot 1 Target c Unit 0 Encl Serv device SUN NEM Hydra II SOL 0308 SASAddress 5080020000bb193d PhyNum 24 /pci@400/pci@1/pci@0/pci@0/pci@0/usb@0,2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00
LSI,sas@0 – Controller (REM) on the server module.
SASDeviceName – WWN that the Oracle Solaris OS recognizes.
SASAddress – WWN that the OBP references.
PhyNum – Physical slot that the drive occupies.
This example is based on the previous output:
cn = c0
n is the SAS controller number, 0 in this example.
tn = t5000c50033438dbb
n is the SASDeviceName value.
dn = d0
n is 0 for all embedded SCSI devices.
The resulting logical device name is c0t5000c50033438dbbd0.
The Oracle Solaris syntax requires all WWN alpha characters to be capitalized.
Note - Only the WWN portion of the logical device name requires capitalized alpha characters. The c0 and d0 portion are not capitalized.
This Jumpstart profile example shows how to use the WWN syntax when installing the OS on a specific drive.
# install_type flash_install boot_device c0t5000C50033438DBBd0 preserve archive_location nfs 129.148.94.249:/export/install/media/solaris/builds/s10u9/flar/latest.flar # Disk layouts # partitioning explicit filesys rootdisk.s0 free / filesys rootdisk.s1 8192 swap
In an interactive installation, you are asked to specify one or more drives as the targets for the OS installation. This step ensures that sufficient storage capacity is provided for the installation. Specify the drive with the WWN value that corresponds to the drive on which you want to install the software.
These WWN values are illustrated in the following interactive example. The drive selected as the installation target is located in drive slot 0, the default boot location.
Note - If you prefer to use some other disk, specify it instead of the one in HDD slot 0.
_ Select Disks_________________________________________________________________ On this screen you must select the disks for installing Solaris software. Start by looking at the Suggested Minimum field; this value is the approximate space needed to install the software you've selected. Keep selecting disks until the Total Selected value exceeds the Suggested Minimum value. NOTE: ** denotes current boot disk Disk Device Available Space ============================================================================= [ ] c0t5000C50005C15803d0 286090 MB [X] c0t5000C50033438DBBd0 286090 MB (F4 to edit) Total Selected: 286090 MB Suggested Minimum: 5032 MB ______________________________________________________________________________ Esc-2_Continue F3_Go Back F4_Edit F5_Exit F6_Help
Note - You might need to label new and replacement drives using the format utility before you can install the OS on the drives.