34 SPARC Enterprise T5120 and T5220 Servers Product Notes • October 2007
1. The system is booted in the factory-default configuration.
2. The user changes an ldom-variable from the ok prompt or from Solaris.
3. The user saves an LDoms configuration.
4. The user then sets the variable back to its default value.
At this point the LDoms variable auto-boot? retains the default value of true
across reboot and reset events, but if the system is power-cycled, the variable returns
to the value it held immediately before the ldm set-spconfig command. This
action only affects variables that are being set to their default-values. If auto-boot?
was true before the LDoms configuration was saved, and then you changed its value
to false (non-default), then auto-boot? would retain the value of false, even across
power-cycles.
Workaround: To ensure that LDom variable changes persist across power cycles
resave the SP configuration after changing an LDoms variable. In this example, after
changing auto-boot? back to its default value, resave the SP configuration:
Alternatively, you could manually change the LDoms variables back to their default
values following a power cycle.
Occasional LDom Warning Message After POST (CR 6592934)
In the unlikely event that POST times out before completing its test cycle, the Virtual
Blade Server Control (VBSC) will issue the following message to the console:
ok setenv auto-boot? false
(or from Solaris)
# eeprom auto-boot?=false
# ldm set-spconfig my-new-config
ok set-default auto-boot?
(or from Solaris)
# eeprom auto-boot?=true
# ldm remove-spconfig my-new-config
# ldm add-spconfig my-new-config
ERROR: POST timed out. Not all system components tested.
