The section describes information to be aware of in using Advanced Lights Out Manager (ALOM) chip multithreading (CMT) with the Logical Domains Manager. For more information about using the ALOM CMT software, refer to the Advanced Lights Out Management (ALOM) CMT v1.3 Guide.
The ALOM CMT documentation only refers to one domain, the primary domain. So, you must be aware that the Logical Domains environment is introducing multiple domains. Say you have a primary domain that is being used as a service domain to provide virtual device services to other domains. In this case, if the primary domain is restarted, these client domains appear to freeze during the reboot process. After the primary domain has fully restarted, the domains resume normal operation. You only need to shut down all domains when power is going to be removed from the entire server.
An additional option is available to the existing ALOM CMT command.
The config=”config-name” option enables you to set the configuration on the next power on to another configuration, including the factory-default shipping configuration.
You can invoke the command whether the host is powered on or off. It takes effect on the next host reset or power on.
Reset the logical domain configuration on the next power on to the default shipping configuration by executing this command in ALOM CMT software.
sc> bootmode config=”factory-default”
You also can select other configurations that have been created with the Logical Domains Manager using the ldm add-config command and stored on the service processor (SP). The name you specify in the Logical Domains Manager ldm add-config command can be used to select that configuration with the ALOM CMT bootmode command. For example, assume you stored the configuration with the name ldm-config1.
sc> bootmode config=”ldm-config1”
Now, you must powercycle the system to load the new configuration.
Refer to the ldm(1M) man page for more information about the ldm add-config command.