Information About Software |
This section includes the following sections:
This section describes specific software and firmware issues and workarounds. To obtain patches and to check for availability of new patches that fix these issues, go to:
TABLE 3 lists XCP issues and possible workarounds.
This section contains information about Solaris OS issues. TABLE 4, TABLE 5, TABLE 6, and TABLE 7 list issues you might encounter, depending upon which Solaris OS release you are using.
TABLE 4 lists Solaris OS issues that you might encounter in any supported release of Solaris OS.
TABLE 5 lists issues that have been fixed in Solaris 10 10/08 OS. You might encounter them in supported releases earlier than Solaris 10 10/08.
Memory translation warning messages might appear during boot if memory banks were disabled due to excessive errors. |
After the system is rebooted, the fmadm repair command can be used to prevent a recurrence of the problem on the next boot. |
|
When XSCF is low on system resources, DR deleteboard or moveboard operations that relocate permanent memory might fail with one or more of these errors: SCF busy DR parallel copy timeout This applies only to Quad-XSB configured System Boards hosting multiple domains. |
||
The system panics when DiskSuite cannot read the metadb during DR. This bug affects the following cards: |
Panic can be avoided when a duplicated copy of the metadb is accessible via another Host Bus Adaptor. |
|
The DR addboard command might cause a system hang if you are adding a Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-E HBA card (SG-XPCIE2FC-QF4) at the same time that an SAP process is attempting to access storage devices attached to this card. The chance of a system hang is increased if the following cards are used for heavy network traffic: |
||
Hot-plug of the X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP card in slot 1 might cause other network devices to fail. |
||
The DR deleteboard(8) and moveboard(8) operations might hang if any of the following conditions exist: The domain contains system boards with different memory size. |
For Solaris 10 5/08 or earlier, this has been fixed in patch 137111-01. Avoid performing DR operations if any of the following conditions exist:
|
|
fmd service on domain might fail to maintenance mode after DR operations. |
This has been fixed in patch 138050-01. Issue the following command on the domain: # svcadm clear fmd |
|
DR might cause the domain to hang if either of the following conditions exist: |
This has been fixed in patch 138397-01. set drmach:drmach_disable_mcopy = 1 |
|
DR operations involving the lowest number CPU might cause the domain to panic. |
Do not use DR to remove the system board that hosts the CPU with the lowest CPU ID. Use the Solaris prtdiag command to identify the CPU with the lowest CPU ID. |
|
If your domain is running one of the following versions of Solaris OS, the system might panic/trap during normal operation: |
Set the following parameter in the system specification file (/etc/system): set heaplp_use_stlb=0 |
TABLE 6 lists issues that have been fixed in Solaris 10 5/08 OS. You might encounter them in supported releases earlier than Solaris 10 5/08.
TABLE 7 lists issues that have been fixed in Solaris 10 8/07 OS. You might encounter them in Solaris 10 11/06.
This section contains late-breaking information that became known after the documentation set was published.
The corrections for Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF Reference Manual, if not otherwise specified, also apply to the man pages, which XSCF provides. And these corrections supersede the information on the man pages.
TABLE 8 lists known documentation corrections.
Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.