Use the following procedure to use a virtual machine as a virtual L-Server:
In the ROR console orchestration tree, right-click a VM host in the registered VM pool, and select [Convert to L-Server] from the popup menu.
The [Convert to L-Server] dialog is displayed.
Enter the following items:
Select a resource folder or a tenant to store L-Servers.
If omitted, the L-Server is stored in the root folder of the user that executed linking between the virtual machine and the L-Server.
Displays virtual machines that were created on the specified VM host, that have not been linked to L-Servers. In addition to the virtual machine name, the OS type, L-Server name, and destination folder are displayed.
When the virtual machine name starts with an alphanumeric character (upper or lower case) and consists of 64 or less characters, including alphanumeric characters (upper or lower case), underscores ("_"), hyphens ("-"), or periods("."), the virtual machine name is displayed as the default L-Server name.
Select a virtual machine to use as a virtual L-Server.
To use all virtual machines registered on the specified VM host, click the [Select all] button.
Set the L-Server name, label, comment, and destination folder.
Clicking the [Details] button displays the [VM Guest Setting] dialog.
For the information that can be specified for each item, refer to "18.4.2 For Physical Servers".
For the L-Server name, enter up to 64 characters beginning with an alphabetical character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-").
Enter the desired items and click [OK] to reflect the settings on the items displayed in the VM guest list.
Click the [OK] button.
The virtual machine becomes manageable as a virtual L-Server.
[VMware]
When the function to import an IP address allocated to a virtual machine is enabled, check that the IP address is displayed in the network information on the L-Server.
[VMware] [Hyper-V]
When an IP address is not displayed, an IP address can be set using the rcxadm lserver modify command.
For details on the rcxadm lserver modify command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
From the command-line, execute rcxadm lserver convert.
For details on the rcxadm lserver convert command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
Note
When operating an admin server on a virtual machine on VMware or Hyper-V environment, do not link that virtual machine to an L-Server.
VMware FT secondary virtual machines cannot be linked with L-Servers.
For a virtual L-Server linked with a configured virtual machine, a hyphen ("-") is displayed for [Usage] in the [Disk Information] displayed on the [Resource Details] tab on the ROR console.
[VMware]
When the limit values of CPU/memory of a virtual machine linked with an L-Server have been set to "Unlimited", different methods are used for calculating the number of possible L-Servers and modifying L-Server specifications.
For details on the calculation method, refer to "Max. Number of Possible L-Servers View" in "20.6 Viewing".
For details on modifying specifications, refer to "18.5 Changing Configuration".
[Hyper-V]
When a virtual machine with a network adapter that has never been started before is linked with an L-Server, the MAC address the L-Server uses on the network might be set to "00:00:00:00:00:00". In that case, cancel the link between the virtual machine and L-Server and assign a static MAC address to that virtual machine using VM management software, or start the virtual machine, wait for 3 minutes, and then create the link with the L-Server.
[Solaris Zones]
When the cap values of CPU/memory of a virtual machine linked with an L-Server have not been specified, a different method is used for calculating the number of possible L-Servers.
For details on the calculation method, refer to "Max. Number of Possible L-Servers View" in "20.6 Viewing".
When importing a Solaris Zone related to an L-Server into L-Platform management functions, it is necessary to add NIC information to the L-Server. Create a network resource if necessary, and then add NIC information.
Confirm the information of the VLAN and subnet of the network to which the NIC of the VM guest is to be imported. If the network resource corresponding to the combination of the VLAN and subnet already exists, there is no need to create a new network resource.
Otherwise, create a new network resource using the following procedure.
In the ROR console orchestration tree, right-click the target network pool, and select [Create Network Resource].
When creating a new resource, select [New].
When creating a network resource using an already registered admin LAN subnet, select [Using existing admin subnet].
The [Create a network resource] dialog is displayed.
Enter the necessary items to create the network resource.
VLAN ID
When using a VLAN, enter its value. Otherwise, specify an arbitrary LAN which is not and will not be used by other existing network resources.
Uplink port
Do not specify anything.
Detail configuration
Do not configure anything.
For details on how to add NIC information to L-Servers, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
[OVM for SPARC]
For details on the CPU performance and the number of CPUs, refer to "Display of CPU Performance and the Number of CPUs for L-Servers" in "8.8.8 Advisory Notes for OVM for SPARC Usage" in the "Setup Guide CE".
When importing an L-Server into L-Platform management functions, it is necessary to add NIC information to the L-Server. Create a network resource if necessary, and then add NIC information.
When Solaris zones are constructed on the guest domain and the guest domain is registered as a VM host, virtual L-Servers linked with the guest domain cannot be imported to the L-Platform.
The administrator (supervisor or dual-role administrators) who manages the entire system needs to manage the virtual L-Server which created the Solaris zone on the guest domain.
Configurations which share a disk between multiple L-Servers cannot be performed using this product. Set up the disk to share, on the VM host.
[Citrix Xen]
When the CPU performance of the L-Server converted from a configured virtual machine on XenCenter is a hyphen ("-"), different methods are used for calculating the number of possible L-Servers.
For details on the calculation method, refer to "Max. Number of Possible L-Servers View" in "20.6 Viewing".
