test

Logical Domains 1.2 Administration Guide

Operating the Solaris OS With Logical Domains

This section describes the changes in behavior in using the Solaris OS that occur once a configuration created by the Logical Domains Manager is instantiated; that is, domaining is enabled.

Note –

Any discussion about whether domaining is enabled pertains only to Sun UltraSPARC T1–based platforms. Otherwise, domaining is always enabled.

OpenBoot Firmware Not Available After Solaris OS Has Started If Domaining Is Enabled

Domaining is enabled once a logical domains configuration created by the Logical Domains Manager is instantiated. If domaining is enabled, the OpenBoot firmware is not available after the Solaris OS has started, because it is removed from memory.

To reach the ok prompt from the Solaris OS, you must halt the domain. You can use the Solaris OS halt command to halt the domain.

Powercycling a Server

Whenever performing any maintenance on a system running LDoms software that requires powercycling the server, you must save your current logical domain configurations to the SP first.

ProcedureSave Your Current Logical Domain Configurations to the SP

  1. Use the following command.


    # ldm add-config config-name

Do Not Use the psradm(1M) Command on Active CPUs in a Power-Managed Domain

Do not attempt to change an active CPU's operational status in a power-managed domain by using the psradm(1M) command. This only applies if your platform supports power management.

Result of Solaris OS Breaks

    If domaining is not enabled, the Solaris OS normally goes to the OpenBoot prompt after a break is issued. The behavior described in this section is seen in two situations:

  1. You press the L1-A key sequence when the input device is set to keyboard.

  2. You enter the send break command when the virtual console is at the telnet prompt.

If domaining is enabled, you receive the following prompt after these types of breaks.


c)ontinue, s)ync, r)eset, h)alt?

Type the letter that represents what you want the system to do after these types of breaks.

Results From Halting or Rebooting the Control Domain

The following table shows the expected behavior of halting or rebooting the control (primary) domain.

Note –

The question in Table 9–1 regarding whether domaining is enabled pertains only to the Sun UltraSPARC T1 processors. Otherwise, domaining is always enabled.

Table 9–1 Expected Behavior of Halting or Rebooting the Control (primary) Domain

Command 

Domaining Enabled? 

Other Domain Configured? 

Behavior 

halt

Disabled 

N/A 

For Sun UltraSPARC T1 Processors:

Drops to the ok prompt.

 

Enabled 

Not Configured 

For Sun UltraSPARC T1 Processors:

System either resets and goes to the OpenBoot ok prompt or goes to the following prompt:

r)eset, o)k prompt, or h)alt?

For Sun UltraSPARC T2 Processors:

Host powered off and stays off until powered on at the SP. 

 

Enabled 

Configured 

Soft resets and boots up if the variable auto-boot?=true. Soft resets and halts at ok prompt if the variable auto-boot?=false.

reboot

Disabled 

N/A 

For Sun UltraSPARC T1 Processors:

Powers off and powers on the host. 

 

Enabled 

Not Configured 

For Sun UltraSPARC T1 Processors:

Powers off and powers on the host. 

For Sun UltraSPARC T2 Processors:

Reboots the host, no power off. 

 

Enabled 

Configured 

For Sun UltraSPARC T1 Processors:

Powers off and powers on the host. 

For Sun UltraSPARC T2 Processors:

Reboots the host, no power off. 

shutdown -i 5

Disabled 

N/A 

For Sun UltraSPARC T1 Processors:

Powers off the host. 

 

Enabled 

Not Configured 

Host powered off, stays off until powered on at the SP. 

 

Enabled 

Configured 

Soft resets and reboots.