Supported Versions of the OS, Firmware, and Software
Required OS Package and Patch Updates
Determining Oracle Solaris 11 OS Package Update Version
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)
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)
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)
If you attempt to create a RAID volume smaller than MAX, the following series of messages is returned:
You are about to create an IR volume. WARNING: Proceeding with this operation may cause data loss or data corruption. Are you sure you want to proceed (YES/NO)? yes WARNING: Volume created with size other than 'MAX' is not supported. Do you want to continue with volume creation (YES/NO)? n SAS2IRCU: you must answer "YES" or "yes" to proceed; operation aborted! SAS2IRCU: Error executing command CREATE.
RAID volumes smaller than MAX are not supported. However, if you want to create a volume below MAX size for nonproduction use, the software allows you to do so. This situation is not clear from the message.
Workaround: Ignore the messages and answer yes for the question “Do you want to continue with volume creation (YES/NO)?”.