This chapter explains how to operate L-Servers.
L-Servers linked with configured physical servers or virtual machines can also be operated.
However, the operations which can be carried out differ depending on the configuration of the L-Server.
For how to link a configured physical server or a configured virtual machine to an L-Server, and the possible operations, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines".
Available Operations
L-Servers can perform the following operations:
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Starting an L-Server (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Refer to "17.1.1 Starting an L-Server". |
Stopping an L-Server (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | For details, refer to "17.1.2 Stopping an L-Server". |
Restarting an L-Server (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Refer to "17.1.3 Restarting an L-Server". |
Starting all L-Servers in a resource folder (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Refer to "Starting an L-Server in a Resource Folder" in "17.1.4 Batch Power Operation of L-Servers in Resource Folders". |
Stopping all L-Servers in a resource folder (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Refer to "Stopping an L-Server in a Resource Folder" in "17.1.4 Batch Power Operation of L-Servers in Resource Folders". |
Restarting all L-Servers in a resource folder (*1) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Refer to "Restarting an L-Server in a Resource Folder" in "17.1.4 Batch Power Operation of L-Servers in Resource Folders". |
*1: Configuration of server virtualization software is necessary depending on the functions. For details, refer to "9.2.1 Configuration Requirements" in the "Design Guide VE".
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Modifying specifications | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*1, *2) | Yes | Yes (*1, *2) | Yes (*3, *4) | Yes (*4, *5) | Refer to "17.2.1 Modifying Specifications". |
Modifying the basic information | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*1, *2) | Yes | Yes (*1, *2) | Yes | Yes | Refer to "17.2.2 Modifying the Basic Information". |
Attaching and detaching disks | Yes (*6) | Yes | Yes | Yes | Yes | Yes | No | Yes (*7) | Yes (*1) | Yes (*8) | Yes (*8) | Refer to "17.2.3 Attaching and Detaching Disks". |
Increasing disk capacity | No | Yes | Yes | No | No | No | No | No | No | No | No | Refer to "17.2.6 Increasing Disk Capacity". |
Sharing disks between L-Servers | Yes (*6) | No | No | Yes | No | No | No | No | No (*9) | No | No | Refer to "17.2.4 Sharing Disks Between L-Servers". |
Modifying network resource settings | Yes | Yes | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Yes (*10) | Refer to "17.2.5 Modifying Network Resource Settings". |
*1: When a VM host not managed with server management software is used, operation and changes are not possible.
*2: Registration of server management software is necessary.
*3: Modification of the following items cannot be performed using the ROR console, while powering on.
Number of CPUs
CPU Performance
Memory Size
*4: The OS type cannot be changed.
*5: Modification of the following items cannot be performed using the ROR console, while powering on.
Number of CPUs
Memory Size
*6: Only possible when using SAN boot.
*7: Detaching of disks is not possible. However, it is possible from the global zone.
Use the following procedure to detach disks from a global zone.
In the global zone, execute the following command:
#/usr/sbin/zonecfg -z VM_name "remove fs dir=Mount_point" <RETURN> |
In VM_name, specify the VM guest name that can be confirmed on the ROR console.
In Mount_point, specify the device path to the disk that can be confirmed as an attribute of the L-Server. (Example: /rcx/disk001)
Reboot the non-global zone corresponding to the L-Server.
In the global zone, execute the following command:
#/usr/sbin/zfs list <RETURN> |
In the global zone, execute the following command:
#/usr/sbin/zfs destroy File_system <RETURN> |
File_system can be confirmed using the following method.
The data set name is displayed in the NAME field output by the zfs list command.
The format of the data set name corresponding to the disk resource generated by Resource Orchestrator is the following part corresponding to the virtual storage:
zpool_name/rcx/VM_guest_name/disk_on_the_device_pathXXX
Specify the data set name corresponding to the disk of Resource Orchestrator as the file system.
*8: Attaching and detaching of disks cannot be performed using the ROR console, while powering on.
*9: Cannot set with this product. Set up the shared disk on the VM host, after creating the L-Server.
*10: IP addresses and network resources of virtual L-Servers can only be changed when the server's status is defined.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Using the L-Server console | Yes | Yes | Yes | No | No | No | No | No | No | No | No | Refer to "17.3 Using the L-Server Console". |
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Deleting an L-Server | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*1, *2) | Yes | Yes (*1, *2, *3) | Yes | Yes | Refer to "17.4 Deleting". |
*1: When a VM host not managed with server management software is used, operation and changes are not possible.
*2: Registration of server management software is necessary.
*3: An L-Server with a disk shared with another L-Server cannot be deleted.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Collecting cloning images | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | Yes | Yes (*1) | Refer to "17.5.1 Collecting and Registering". |
Viewing cloning images | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*2) | Yes | Yes (*2) | Yes | Yes | Refer to "17.5.2 Viewing". |
Unregistering cloning images | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*2) | Yes | Yes (*2) | Yes | Yes | Refer to "17.5.3 Unregistration". |
Deleting cloning images | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | Yes | Yes | Refer to "17.5.4 Deleting". |
*1: The image storage destination cannot be specified when collecting cloning images. The images are stored using the same virtual storage as the system disks of virtual L-Servers for collection.
*2: When a VM host not managed with server management software is used, operation and changes are not possible.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Collection of snapshots | No | Yes | Yes | No | No | No | No | No | No | Yes (*1, *2) | No | Refer to "Collection" of "17.6.1 Snapshot". |
Snapshot restoration | No | Yes | Yes | No | No | No | No | No | No | Yes | No | Refer to "Restoration" of "17.6.1 Snapshot". |
Snapshot deletion | No | Yes | Yes | No | No | No | No | No | No | Yes | No | Refer to "Deletion" of "17.6.1 Snapshot". |
System image backup | Yes | No | No | No | No | No | No | No | No | No | No | Refer to "Backup" of "17.6.2 Backup and Restore". |
System image restoration | Yes | No | No | No | No | No | No | No | No | No | No | Refer to "Restoration" of "17.6.2 Backup and Restore". |
System image deletion | Yes | No | No | No | No | No | No | No | No | No | No | Refer to "Deletion" of "17.6.2 Backup and Restore". |
*1: Single quotes (') cannot be used for comments.
*2: When virtual L-Servers are powered on, collection of snapshots of disks cannot be performed using the ROR console.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Moving L-Servers between VM hosts | No | Yes | Yes | Yes | Yes | Yes | Yes (*1, *2) | No | Yes (*1, *2) | Yes | Yes | Refer to "17.7 Migration between VM Hosts". |
*1: When a VM host not managed with server management software is used, operation and changes are not possible.
*2: Registration of server management software is necessary.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Allocating resources to L-Servers | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*) | Yes | Yes (*) | Yes | Yes | Refer to "17.8.2.1 Allocating Resources". |
Releasing resources from L-Servers | Yes | Yes | Yes | Yes | Yes | Yes | Yes (*) | Yes | Yes (*) | Yes | Yes | For details, refer to "17.8.2.2 Releasing Resources". |
* Note: When a VM host not managed with server management software is used, operation and changes are not possible.
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Changing physical server usage | Yes | No | No | No | No | No | No | No | No | No | No | Refer to "17.9 Changing Physical Server Usage". |
Operation | Physical L-Server | Virtual L-Server | Reference | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
VMware | Hyper-V | RHEL-Xen | OVM for x86 2.2 | RHEL-KVM | Solaris Zones | OVM for SPARC | Citrix XenServer | OVM for x86 3.x | ||||
Solaris 10 | Solaris 11 | |||||||||||
Exporting a virtual L-Server | No | Yes | No | No | No | No | No | No | No | No | No | |
Importing a virtual L-Server | No | Yes | No | No | No | No | No | No | No | No | No | |
Note
Operations for an L-Server included in an L-Platform using the ROR console and commands have limits. Use of the console and moving of an L-Server (migration) between VM hosts are only possible when using the ROR console. Use of commands and moving of an L-Server (migration) between VM hosts are only possible when using the ROR console.
When an L-Platform is included in a resource folder or a tenant, the L-Server under the L-Platform is not the target of batch power operations.
When operating a physical server or a VM guest related to an L-Server using the server tree on the ROR console or using commands, consider also the effects on L-Servers.
For virtual L-Servers with the OS type "Other", there is a possibility that the operation will not be reflected on the guest OS.
[OVM for SPARC]
Since a non-global zone constructed on the Solaris Zone is also influenced when power operations or migration 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.
