Disabling a dimm and resetting all (cr 6579390), Guest domain, Openboot prom variables cannot be modified by – FUJITSU SPARC ENTERPRISE T5120 User Manual

Page 41

Important Information About the SPARC Enterprise T5120 and T5220 Servers

OpenBoot PROM Banner Shows the Same Memory Number
After Disabling a DIMM and Resetting All (CR 6579390)

If you manually disable any CPU or memory resource with the system ASR
functionality (for example, with the disablecomponent command from the service
processor) while the host is powered on, then a host power cycle is required for the
change to take effect. If the host is rebooted without a power cycle, messages might
be printed on the host console stating that the resources have been disabled, even
though the resources are still present. These messages can be ignored, but to allow
Solaris to boot, set the LDoms variable auto-boot-on-error? to true.

Guest Domain wanboot miniroot Download Could Take
More Than 30 Minutes (CR 6543749)

During boot or installation over wide area networks, the time it takes to download
the miniroot could significantly increase when using a virtual network device. Early
tests showed the miniroot download to be five to six times slower compared to
similar boot or installation over physical network devices.

This performance degradation is relevant only when trying to boot or install over
wide area networks using a virtual network device. A similar boot or installation
using a physical network device works as expected, as does a traditional local area
net boot or installing from a virtual network device.

OpenBoot PROM Variables Cannot Be Modified by eeprom at
the OS Prompt When ldmd Is Running (CR 6540368)

LDom variables for a domain can be specified using any of the following methods:

■

At the OpenBoot prompt

■

Using the Solaris OS eeprom(1M) command

■

Using the Logical Domains Manager CLI (ldm)

■

Modifying, in a limited fashion, from the system processor (SP) using the
bootmode

command; that is, only certain variables, and only when in the factory-

default configuration.

The goal in all cases, is for variable updates made using any of these methods
always persist across reboots of the domain, and always reflect in any subsequent
logical domain configurations saved to the SP.

In Logical Domains 1.0 software, there are a few cases where variable updates do not
persist: