Start Of Fma Service May Not Complete (Cr 6886045) - Fujitsu SPARC Enterprise T2000 Product Notes

Specific Issues for the SPARC Enterprise T2000 Server (6 of 6)
TABLE 1
CR ID Description
6781815 After the ALOM reset or the power cable removal
and insertion, when the server powered on, Solaris
OS startup at the ok prompt of OBP (OpenBoot
PROM) using the boot command may fail.
Error output example:
{0} ok boot
ERROR: All device paths in boot-device
have failed. (*)
{0} ok
It cannot refer to the device paths that configured in
the OBP environmental variable boot-device and
fails to start Solaris OS.
6886045 Start of the FMA (Fault Management Architecture)
service may not complete. And due to the derived
event, the Solaris OS shutdown may not terminate.
For details, see
Complete (CR 6886045)" on page
6875992 During system operation, an event may repeatedly
occur that the server internal fan shows the failed
state (log: "SYS_FAN at FT0/FMx has FAILED.")
and then gets back to normal (log: "SYS_FAN at
FT0/FM1 is OK.") one second later. For details, see
"Repeatedly Occurs an Event of Internal Fan Status
Error Which Gets Back to Normal One Second Later
(CR 6875992)" on page

Start of FMA Service May Not Complete (CR 6886045)

This issue has been fixed in System Firmware 6.7.8 or later.
Start of the FMA (Fault Management Architecture) service may not complete. And
due to the derived event, the Solaris OS shutdown may not terminate.
Event 1)
Start of the Fault Management Architecture (FMA) service may not complete. When
you executed the svcs(1M) command and the FMA service is offline, and if there
exist two fmd processes as the ps(1M) command execution result, this event has
been occurred.
"Start of FMA Service May Not
13.
14.
Important Information About the SPARC Enterprise T2000 Server
Workaround
Note - Fixed in System Firmware 6.7.5 or later.
After the ALOM reset or the power cable removal
and insertion, when you power on the server,
check the OBP environmental variable. Especially,
in case the OBP environmental variable use-
nvramrc? has been set to true, it is necessary in
advance of starting the OS to see the ok prompt
and check that use-nvramrc? has been set to
true and then execute the boot command.
Confirmation example:
{0} ok printenv use-nvramrc?
use-nvramrc? = true
{0} ok
Note - Fixed in System Firmware 6.7.8 or later.
None.
Note - Fixed in System Firmware 6.7.8 or later.
Ignore the output message.
13