|
6440061
|
The domain console may display this message:
ipsec_check_inbound_policy: Policy
Failure for the incoming packet
(not secure)
|
This message can be safely ignored.
|
|
6449315
|
The Solaris OS cfgadm(1M) command does not unconfigure a DVD drive from a domain on a M8000/M9000 server.
|
Disable the Volume Management Daemon (vold) before unconfiguring a DVD drive with the cfgadm(1M) command. To disable vold, stop the daemon by issuing the command /etc/init.d/volmgt stop. After the device has been removed or inserted, restart the daemon by issuing the command /etc/init.d/volmgt start.
|
|
6459540
|
The DAT72 internal tape drive might time out during tape operations.
The device might also be identified by the system as a QIC drive.
|
Add the following definition to /kernel/drv/st.conf:
tape-config-list=
"SEAGATE DAT DAT72-000",
"SEAGATE_DAT____DAT72-000",
"SEAGATE_DAT____DAT72-000";
SEAGATE_DAT____DAT72-000=1,0x34,0,0x9639,4,0x00,0x8c,0x8c,
0x8c,3;
There are four spaces between SEAGATE DAT and DAT72-000.
|
|
6522017
|
Domains using the ZFS file system cannot use DR.
|
Set the maximum size of the ZFS ARC lower. For detailed assistance, contact your authorized service representative.
|
|
6531036
|
The error message network initialization failed appears repeatedly after a boot net installation.
|
There is no workaround.
|
|
6531668
|
System hangs when executing parallel hot-plug operation with SP DR in suspend phase.
|
There is no workaround.
|
|
6532215
|
volfs or dscp services might fail when a domain is booted.
|
Restart the service. To avoid the problem, issue the following commands.
# svccfg -s dscp setprop
start/timeout_seconds=count: 300
# svccfg -s volfs setprop
start/timeout_seconds=count: 300
# svcadm refresh dscp
# svcadm refresh volfs
|
|
6535018
|
In Solaris domains that include SPARC64 VII processors, workloads that make heavy use of the Solaris kernel might not scale as expected when you increase the thread count to a value greater than 256.
|
This has been fixed in patch 137111-01.
For Solaris domains that include SPARC64 VII processors, limit domains to a maximum of 256 threads.
|
|
6565553,
6674266
|
DR deleteboard(8) and moveboard(8) operations might fail.
Example for messages on domain:
drmach: WARNING: Device driver
failure: /pci
dcs: <xxxx> config_change_state:
Hardware specific failure:
unconfigure SB1: Device driver
failure: /pci
|
There is no workaround.
Try DR operations again.
|
|
6572827
|
The prtdiag -v command reports PCI bus types incorrectly. It reports “PCI” for PCI-X leaf devices and “UNKN” for legacy PCI devices.
|
There is no workaround.
|
|
6575970
|
DR and XSCF failover are not compatible.
|
|
|
6588555
|
Resetting the XSCF during a DR operation on permanent memory might cause domain panic.
|
Do not start an XSCF reset while a DR operation is underway. Wait for the DR operation to complete before starting the reset.
|
|
6588650
|
On occasion, the system is unable to DR after an XSCF failover to or from backup XSCF.
|
There is no workaround.
|
|
6589644
|
When XSCF switchover happens after the SB has been added using the addboard command, the console is no longer available.
|
The console can be recovered by pressing
Ctrl-q (the “Ctrl” key and the “q” key).
|
|
6592302
|
Unsuccessful DR operation leaves memory partially configured.
|
It might be possible to recover by adding the board back to the domain with an addboard -d command.
|
|
6619224
|
For Solaris domains that include SPARC 64 VII processors, a single domain of 256 threads or more might hang for an extended period of time under certain unusual situations. Upon recovery, the uptime command will show extremely high load averages.
|
This has been fixed in patch 137111-03.
For Solaris domains that include SPARC 64 VII processors, do not exceed a domain size of 256 virtual processors in a single Solaris domain. This means a maximum of 32 CPUs in a single domain configuration (maximum configuration for an M8000 server).
|
|
6623226
|
The Solaris command lockstat(1M) or the dtrace lockstat provider might cause a system panic.
|
This has been fixed in patch 140336-01.
[Workaround]
Do not use the Solaris lockstat(1M) command or the dtrace lockstat provider.
|
|
6625734
|
Systems with large number of processors in a single domain environment may have suboptimal performance with certain workloads.
|
Use processor sets to bind application processes or LWPs to groups of processors. Refer to the psrset(1M) man page for more information.
|
|
6660168
|
If a ubc.piowbeue-cpu error occurs on a domain, the Solaris Fault Management cpumem-diagnosis module might fail, causing an interruption in FMA service.
If this happens, you will see output similar to the following sample in the console log:
|
If fmd service fails, issue the following command on the domain to recover:
# svcadm clear fmd
Then restart cpumem-diagnosis:
# fmadm restart cpumem-diagnosis
|
|
|
SUNW-MSG-ID: FMD-8000-2K, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr 4 21:41:57 PDT
2008
PLATFORM: SUNW,SPARC-Enterprise, CSN:
2020642002, HOSTNAME: <hostname>
SOURCE: fmd-self-diagnosis, REV: 1.0
EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-
cb03a7dd77e3
DESC: A Solaris Fault Manager
component has experienced an error
that required the module to be
disabled. Refer to
http://sun.com/msg/FMD-8000-2K for
more information.
AUTO-RESPONSE: The module has been
disabled. Events destined for the
module will be saved for manual
diagnosis.
IMPACT: Automated diagnosis and
response for subsequent events
associated with this module will not
occur.
REC-ACTION: Use fmdump -v -u
<EVENT -ID> to locate the module. Use
fmadm reset <module> to reset the
module.
|
|
|
6668237
|
After DIMMs are replaced, the corresponding DIMM faults are not cleared on the domain.
|
Use the command fmadm repair fmri|uuid to record the repair. Then you can use the command fmadm rotate to clear out any leftover events.
|
|
6679370
|
The following message may be output on the console during the system booting, the External I/O Expansion Unit adding by hotplug, or the FMEMA operating by DR.
SUNW-MSG-ID: SUN4-8000-75, TYPE:
Fault, VER: 1, SEVERITY: Critical
...
DESC:
A problem was detected in the
PCIExpress subsystem.
Refer to http://sun.com/msg/SUN4-
8000-75 for more information.
...
|
Add the following to /etc/system, then reboot the domain.
set pcie_expected_ce_mask = 0x2001
|
|
6680733
|
Sun Quad-port Gigabit Ethernet Adapter UTP (QGC) & Sun Dual 10 GigE Fiber XFP Low Profile Adapter (XGF) NICs might panic under high load conditions.
|
This has been fixed in patch 139570-01.
|
|
6689757
|
Sun Dual 10 GigE Fiber XFP Low Profile Adapter (XGF) with a single or improperly installed XFP optical transceivers might cause the following error to show on the console:
The XFP optical transceiver is broken or missing.
|
This has been fixed in patch 139570-01.
[Workaround]
Check and make sure that both XFP optical transceivers are firmly seated in the housing.
Do not mix INTEL and Sun XFP optical transceivers in the same Adapter.
Do NOT plumb a port with the ifconfig command if the port does not contain an XFP optical transceiver or it contains one but the transceiver is not in use.
|
|
6707628
|
Scheduler decisions on Mx000 systems are occasionally unbalanced.
Sometimes two threads will be on one core (causing both to run at about half speed) while another core is idle. For many OpenMP and similar parallel applications, the application performance is limited by the speed of the slowest thread.
Uneven scheduling is not common, perhaps 1 in 50 or 1 in 100 decisions. But if there are 128 threads running, then the application might have at least one uneven schedule event.
|
Use processor sets to prevent uneven threads to core assignment.
|
|
6723202
|
The raidctl command cannot be used to create a hardware RAID using the onboard SAS/LSI controller on the M3000 server.
The raidctl command can be used to view disk/controller status, and can be used on any PCI Host Bus Adapter (HBA) installed in the system.
|
No workaround is available. This issue will not be fixed.
|
|
6745410
|
Boot program ignores the Kadb option which causes the system not to boot.
|
Use kmdb instead of kadb.
|
|
6794630
|
An attempt to use the GUI to install Solaris in a domain larger than 2TB might fail.
|
Use the Command Line Interface to install Solaris.
|
