This section describes issues related to the system firmware.
On servers ordered with the Sun Storage 6 Gb SAS PCIe 8-Port Internal RAID HBA card preinstalled, the full device path to the boot drive must be specified in order to boot the Solaris OS.
Identify the RAID HBA controller and the drive(s) attached:
ok probe-scsi-all /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00/pci@400/pci@2/pci@0/pci@4/scsi@0FCode Version 1.00.61, MPT Version 2.00, Firmware Version 9.00.00.00Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0868 585937500 Blocks, 300 GB SASDeviceName 5000c5001d0963c3 SASAddress 5000c5001d0963c1 PhyNum 2 Target a Unit 0 Removable Read Only device TEAC DV-W28SS-V 1.0B SATA device PhyNum 6/pci@400/pci@1/pci@0/pci@4/scsi@0FCode Version 1.00.61, MPT Version 2.00, Firmware Version 9.00.00.00Target 381 Volume 0 Unit 0 Disk LSI Logical Volume 3000 583983104 Blocks, 298 GB VolumeDeviceName 3af2c4ccc00c2ba8 VolumeWWID 0af2c4ccc00c2ba8 /pci@400/pci@1/pci@0/pci@b/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00
In this example from a SPARC T4-1 sesrver, a RAID HBA volume is identified by the VolumeDeviceName definition. Another (non-RAID) drive is identified by the SASAddress definition.
Boot the server using one of the following methods:
Boot from the non-RAID device identified by the SASAddress definition, using the full device path:
ok boot /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@w5000C5001d0963c1,0:a
Boot from the RAID device identified by the VolumeDeviceName definition, using the full device path:
ok boot /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@w3af2c4ccc00c2ba8,0:a
In both cases, the path is derived from the probe-scsi-all command output in Step 1.
For more information about identifying entity name targets in probe-scsi-all output, see the SPARC and Netra SPARC T4 Series Servers Administration Guide.
Note - This issue was originally listed as CR 6968801.
When running Oracle VTS on SPARC T4 series platforms, it is possible (although rare) for an Oracle VTS test to hang. If this happens, it might cause other processes and commands to hang, including fmadm and prtconf. The hung processes cannot be killed.
Workaround: Reboot the system. If the problem repeats, contact your authorized service provider. Avoid running Oracle VTS in production environments.
Note - This issue was originally listed as CR 6993008.
The MIB should report the sunHwCtrlPowerMgmtBudgetTimelimit in milliseconds, but the value displayed is in seconds.
Workaround: Understand that the value reported for sunHwCtrlPowerMgmtBudgetTimelimit is in seconds.
Note - This issue was originally listed as CR 7046898.
Note - This issue is fixed in Oracle Solaris 11.
A message displayed by the cpustat command says:
See the “SPARC T4 User's Manual” for descriptions of these events. Documentation for Sun processors can be found at: http://www.sun.com/processors/manuals
This document and web site listed in this message are not available.
Note - This issue was originally listed as CR 7050975.
Note - This issue is fixed in Oracle Solaris 10 08/11.
REVIEWERS: Does Solaris 10 08/11 = S10U11?
When running the reboot disk command, extraneous characters are occasionally added to the disk argument before it reaches the OpenBoot PROM (OBP). This results in a failure to boot.
Recovery Action: Repeat the boot request.
Note - This issue was originally listed as CR 7082700.
When you attempt to unconfigure a drive for removal, the drive's blue LED that indicates the drive is ready for removal might not light. This happens after you place a drive in a slot in place of a drive that had a different WWID.
Workaround: If you inserted a drive after booting the server, realize that the blue LED will not perform this function until the server has booted again.
Note - This issue was originally listed as CR 7127740.
Note - This issue is fixed in System Firmware version 8.1.4.e.
REVIEWERS: David has this listed as fixed in FW 8.2.0.a. Can somebody confirm which FW version fixed this issue?
After a cold reset, the server might add one day to the Oracle Solaris OS date and time. This possible date change will only occur on the first cold reset after January 1, 2012. Once you set the correct date using the Oracle Solaris OS date(1) command, the corrected date and time will persist across future resets.
A cold reset is when you halt the OS and restart the service processor (SP). For example, you can use one of the following Oracle Solaris OS commands to halt the OS:
# shutdown -g0 -i0 -y
# uadmin 1 6
# init 5
Then, at the ILOM prompt, use the following commands to reset the host:
-> stop /SYS . . . -> start /SYS
Refer to the service manual, the administration guide, and the Oracle Solaris OS documentation for more information.
Workaround: After the first cold reset of the system, verify that the system date and time are correct. If the date has been impacted by this issue, use the Oracle Solaris OS date(1) command to set the correct date and time.
For example, to set the date and time to be February 26, 9:00am, 2012, type:
# date 022609002012
Refer to the date(1) man page and the Oracle Solaris OS documentation for more information.
Note - This issue was originally listed as CR 7146062.
Note - This issue is fixed in System Firmware version 8.1.5.
In some cases, the server could report a false VCORE_POK_GLITCH error, followed by a system shutdown. A line similar to the following appears in the ILOM ereport log prior to system shutdown:
Workaround: Install System Firmware 8.1.5 or later.
If the issue persists even after updating the system firmware, the server is encountering a real hardware error. Contact your authorized service provider.
Servers equipped with System Firmware 8.3.0.b might exhibit severe performance degradation due to thermal limiting of the Sun Flash Accelerator F40 PCIe Card.
Workaround: If your server is equipped with the Sun Flash Accelerator F40 PCIe Card, do not not upgrade to System Firmware 8.3.0.b. If you have already upgraded a server equipped with a Sun Flash Accelerator F40 PCIe Card to System Firmware 8.3.0.b and are encountering thermal-related performance degradation, downgrade to System Firmware 8.2.2.c.