This section explains the batch power operations of L-Servers in resource folders.
When performing batch power operation of L-Server in resource folders, configure the startup priority settings for L-Servers in advance.
For priority order settings, configure from [Startup priority] of the [Modify an L-Server] dialog, or [Server] tab of the [Create an L-Server] dialog.
For details, refer to "16.2 Creation of Physical L-Servers Using Parameters" or "16.3 Creation of Virtual L-Servers Using Parameters".
Note
The batch operations for an L-Server in a tenant are only available for Basic mode.
Users are advised to exclude virtual L-Servers on which Solaris zones have been created on a guest domain from the scope of batch power operations of L-Servers.
Since a non-global zone created on a Solaris Zone is also influenced when power operations are performed on the virtual L-Server on which a Solaris zone has been created on a guest domain, check the extent of impact before performing such operations.
When batch power operations of L-Servers are used in an environment where a Solaris zone has been created on a guest domain, set the priority of the virtual L-Server used to create the Solaris zone on the guest domain as higher than the priority of virtual L-Servers created in the Solaris zone. In addition, since it is carried out using the functions of virtual products, if a power operation fails, perform the power operation again for each L-Server.
Starting an L-Server in a Resource Folder
Use the following procedure to start an L-Server in a resource folder.
Right-click the target resource folder or tenant in the orchestration tree, and select [Power]-[ON] from the popup menu.
The [Power On L-Servers] dialog is displayed.
Point
A list of L-Servers that are targets of the power operation is displayed.
The display order is in descending order of priority.
Even if the list of L-Server is not displayed, the power supply can be operated.
Click the [OK] button.
L-Servers in a resource folder are started in the order of priority.
When all of the following conditions are met on an L-Server with a configuration definition already been created (defined), the L-Server will not be the target of powering on.
The cloning image is specified
Boot disks (system volumes) are dynamically created from virtual storage
The L-Server is a virtual L-Server on RHEL-KVM
When an L-Server uses resources in another tenant, the L-Server will not be the target of powering on.
From the command-line, execute rcxadm folder start.
For details on the rcxadm folder start command, refer to "3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE".
Stopping an L-Server in a Resource Folder
Use the following procedure to stop an L-Server in a resource folder.
Right-click the target resource folder or tenant in the orchestration tree, and select [Power]-[OFF] from the popup menu.
The [Power OFF L-Servers] dialog is displayed.
Point
A list of L-Servers that are targets of the power operation is displayed.
They are displayed in order with low priority.
Even if the list of L-Server is not displayed, the power supply can be operated.
Click the [OK] button.
L-Servers in a resource folder are stopped in the order of priority.
From the command line, execute rcxadm folder stop.
For details on the rcxadm folder stop command, refer to "3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE".
Restarting an L-Server in a Resource Folder
Use the following procedure to restart an L-Server in a resource folder.
Right-click the target resource folder or tenant in the orchestration tree, and select [Power]-[Reboot] from the popup menu.
The [Reboot L-Servers] dialog is displayed.
Point
A list of L-Servers that are targets of the power operation is displayed.
The display order is in descending order of priority.
Even if the list of L-Server is not displayed, the power supply can be operated.
Click the [OK] button.
L-Servers in a resource folder are restarted in the order of priority.
From the command-line, execute rcxadm folder restart.
For details on the rcxadm folder restart command, refer to "3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE".
