Supported Versions of the OS, Firmware, and Software
Required OS Package and Patch Updates
Determining Oracle Solaris 11 OS Package Update Version
Correlate WWN Device Names With Physical Locations (diskinfo Command)
Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)
Oracle Solaris Jumpstart WWN Syntax
Interactive Installation Example
High-Altitude Mode Oracle ILOM Feature
Sun Type 6 Keyboards Are Not Supported by SPARC and Netra SPARC T4 Series Servers
Chassis CMM Does Not Allocate Enough Power to the Netra T4-1B Server Module (CR 7141886)
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)
sas2ircu Message That RAID Volume Sizes Other Than MAX Are Not Supported (CR 6983210)
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)
The 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 the 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 certain WWN syntax. See Oracle Solaris Jumpstart WWN Syntax.
If you plan to run the format command, you select one of the logical device names presented. To ensure you select the correct drive, you must correlate a logical device name with a 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).