|
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.
|
|
6531036
|
The error ‘message network initialization failed’ appears repeatedly after a boot net installation.
|
No workaround is available. This message can be safely ignored.
|
|
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
|
|
6572827
|
The prtdiag -v command reports PCI bus types incorrectly. It reports “PCI” for PCI-X leaf devices and “UNKN” for legacy PCI devices.
|
No workaround is available.
|
|
6623226
|
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.
|
|
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:
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
|
If fmd service fails, issue the following command on the domain to recover:
# svcadm clear fmd
Then restart cpumem-diagnosis:
# fmadm restart cpumem-diagnosis
|
|
6668237
|
After DIMMs are replaced the corresponding DIMM faults are not cleared on the domain.
|
Use the following commands:
# fmadm repair fmri|uuid
# fmadm rotate
|
|
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 and 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.
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.
|
|
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.
|
|
6725885
|
cfgadm will display non-existent M3000 system boards (SB1 to SB15).
|
The cfgadm output for SB1-SB15 can be ignored.
|
|
6737039
|
WAN boot of M3000 servers fails intermittently with a panic early in the boot process. Sample output:
ERROR: Last Trap: Fast Data Access MMU Miss
%TL:1 %TT:68 %TPC:13aacc %TnPC:13aad0 %TSTATE:1605
%PSTATE:16 ( IE:1 PRIV:1 PEF:1 )
DSFSR:4280804b ( FV:1 OW:1 PR:1 E:1 TM:1 ASI:80 NC:1 BERR:1 )
DSFAR:fda6f000 DSFPAR:401020827000 D-TAG:6365206f66206000
|
Poweroff and poweron the chassis, then retry the operation.
|
|
6745410
|
Boot program ignores the Kadb option which causes the system not to boot.
|
Use kmdb instead of kadb.
|
|
6765239
|
If a SAS device containing multiple SAS targets is connected to the onboard external SAS interface, it will not work properly. The enumeration of target IDs within the device may change across reboots.
|
Do not connect a device containing multiple SAS targets to the onboard external SAS interface. Use a Sun StorageTek Host Bus Adaptor (SG-XPCIE8SAS-E-Z). Alternatively, check for the availability of a patch for this defect.
|
