This section explains how to startup an L-Server.
Use the following procedure to start an L-Server:
Right-click the target L-Server in the orchestration tree, and select [Power]-[ON] from the popup menu.
The confirmation dialog is displayed.
Click the [OK] button.
The L-Server is started.
On an L-Server for which only a configuration definition has been created (defined), server and disk resources will be allocated, and after image deployment is performed (when a cloning image has been specified), the L-Server will be started.
On an L-Server which has been released (preserved), server resources will be allocated and started.
For details on the statuses when configuration definitions have been created (defined), servers have been released (preserved), and resources have been allocated (allocated), refer to "17.8 Allocating and Releasing Resources to L-Servers".
From the command-line, execute rcxadm lserver start.
For details on the rcxadm lserver start command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
Point
When "Boot Location" of virtual L-Server is "Relocate at startup", for the selection condition of VM host of a start place, refer to "Selection of L-Server Deployment Location" in "2.2.3 L-Server" in the "Design Guide CE".
Note
From virtual L-Servers to which resources have been allocated (allocated) or from which servers have been released (preserved), a startup command is sent out to VM guests even in the following cases.
CPU or memory resources of the VM host on which VM guests are located are running out, and the destination VM host does not exist (When [Boot Location] is [Relocate at startup])
CPU or memory resources of the VM host on which VM guests are placed are running out (When [Boot Location] is [Fixed])
As sufficient CPU or memory resources cannot be secured on the VM host, an error will occur during L-Server startup. In this case, confirm the output message, and then take corrective action.
When using tenants to segregate resources, the startup of L-Servers may be limited.
For details, refer to "Chapter 21 Resource Folder Operations".
[VMware]
When starting the L-Server, sufficient overhead memory may not be secured, and starting of the L-Server may fail.
In this case, confirm the output message, and then take corrective action.
[OVM for SPARC]
When executing power operations of L-Servers, binding of resources is also executed.
This product carries out auto-save of the configuration information when an L-Server is started.
When you disable the auto-save function of configuration information in this product, add a definition to the definition file which configures the execution of configuration information preservation.
Refer to "8.8.1 Creating Definition Files" in the "Setup Guide CE".
