Supported Versions of Oracle Solaris OS, Firmware, and Software
Determining Oracle Solaris 11 OS Package Update Version
Determining Oracle Solaris 10 Patch Revision
Minimum Required Patchset for Oracle Solaris 10 08/11 OS
Minimum Required Patchset for Oracle Solaris 10 09/10 OS
Minimum Required Patchsets and SPARC Bundle for Oracle Solaris 10 10/09 OS
Rules for I/O Slot Use by Certain Cards
Up to Eight SSDs Can Now Be Installed In Any SPARC T3-1 Server
Minimum System Firmware for Valid devalias in Upper Disk Locations
Oracle Hardware Management Pack 2.1.1 and 2.2 Support SPARC Platforms
Disk Zone Management Using the zoningcli Command
ALOM CMT Compatibility Shell Not Supported
SAS Command Might Fail to Complete When Certain SAS Devices Are Put Under Heavy Load (CR 7088469)
Sun Type 6 Keyboards Are Not Supported By SPARC T3 Series Servers
Caution Needed When Removing a SATA Data Cable From a Backplane Connector
Caution Needed When Handling the Connector Board
Server Panics When Booting From a USB Thumbdrive Attached to the Front USB Ports (CR 6983185)
Cannot Boot Oracle Solaris 10 10/09 OS (U8) From the Internal DVD
When Two Or More NIU Devices Are Plumbed, Memory DR Remove Operations May Hang (6983286)
fault.memory.memlink-uc Fault Did Not Cause Panic as Stated by System Message (6940599)
Memory Allocation Issues With Emulex 8Gb HBAs In a Magma IO Expansion Box (6982072)
Spurious Error Message During Initial Oracle Solaris OS Installation (CR 6971896)
Spurious Interrupt Message in System Console (CR 6963563)
False nxge Warning Messages (CR 6938085)
Benign Error Message: mptsas request inquiry page 0x89 for SATA target :a failed (6986482)
Cold Reset Adds One Day to System Time (CR 7127740)
envtest May Issue Invalid Temperature Reports For Some Components (6975427)
System is Powered Off When Running reset /HOST/domain/control With Active Guest Domains (6987371)
Incorrect Handling of Out-of-Order Ctrl TDs Can Result in Applications Hanging (CR 7024581)
Missing Interrupt Causes USB Hub Hotplug Thread to Hang, Resulting In Process Hangs (6968801)
spconfig Names >36 Characters Give Communication eErrors for ldm add/rm-config Command (6987310)
Service Processor Locks Up With No Access (6985738)
SDIO: ereports Related to Sun Dual 10GbE SFP+ PCIe Cards On Reboots of the Primary Domain (6986960)
ereport.chassis.sp.unavailable Not Generated For a Degraded Service Processor (CR 6978171)
Part Number Provided to Oracle Solaris FMA Is Incorrect (6978447)
OpenBoot Command set-security-key Produces the False Warning: Unable to store security key (6986849)
If your SPARC T3-1 server has a sixteen-disk capacity backplane and uses the onboard SAS-2 controllers to manage the disks, you must apply patch 147034-01 to the LSI firmware on the disk backplane.
Caution - Be certain to back up any data stored on the disks before you apply the patch. You can restore the files after the patch is applied. |
Patch 147034-01 causes the backplane to be partitioned into two disk zones, which have the following characteristics:
Zone A consists of backplane slots 0 through 7. Disks in zone A are managed exclusively by onboard SAS-2 controller 0. They are visible only to each other and to controller 0. Disks in zone A are not visible to any devices in zone B.
Zone B consists of backplane slots 8 through 15. Disks in zone B are managed exclusively by onboard SAS-2 controller 1. They are visible only to each other and to controller 1. Disks in zone B not visible to any devices in zone A.
Note - When zoning is enabled, devalias for slots 8-15 will be incorrect unless the system firmware is updated to either 8.0.5.b (or a higher 8.0 level) or to 8.1.0 (or higher). See Minimum System Firmware for Valid devalias in Upper Disk Locations for more information.
These disk zone definitions are persistent. Their configuration cannot be modified and they remain in effect across power cycles and reboot operations. They must be active whenever the SAS-2 onboard controllers are used to manage disks in a sixteen-disk capable backplane.
However, if you use an internal PCIe RAID HBA instead of the onboard SAS-2 controllers, you must disable disk zoning. You do this with the following command:
# zoningcli disable zoning
The zoningcli command is contained in versions 2.1.1 and 2.2 of the Oracle Hardware Management Pack. See Oracle Hardware Management Pack 2.1.1 and 2.2 Support SPARC Platforms for more information.
The zoningcli command syntax also supports an enable subcommand, which you can use to re-enable disk zones A and B if they are ever disabled. For example, this step would be necessary if you remove an internal PCIe RAID HBA card and return control of the disks to the onboard SAS-2 controllers.
Because the zones are logically isolated from each other, RAID volumes created by controller 0 are restricted to disks in zone A. Likewise, RAID volumes created by controller 1 are restricted to disks in zone B.
Each onboard SAS-2 controller can create up to two hardware RAID volumes. That is, the maximum number of RAID volumes per disk zone is two.