This section explains how to create an L-Server using an L-Server template to automatically select resources from a resource pool.
For details on how to manually install the operating system in the L-Server, refer to "5.1.1 Manual OS Installation".
For details on how to create an L-Server without using an L-Server template, or how to manually specify resources when creating an L-Server, see "Appendix D L-Server Parameter Details".
Use the following procedure to create an L-Server using an L-Server template:
Select the RC console orchestration tree. Select an L-Server template on the [Template List] tab of the Main Panel, and click <Create>.
The [L-Server Register] dialog is displayed.
On the [Basic Information] tab of the [L-Server Register] dialog, set the following items.
Enter a name for the L-Server.
Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), or hyphens ("-").
Specify an L-Server template created in "4.4 Creating an L-Server Template".
The L-Server template specified from [Template List] is displayed. Check the specifications (CPU performance, memory capacity, disk capacity (multiple)) for the L-Server to create.
For physical
Model name, disk capacity (multiple) are displayed.
For virtual
CPU performance, memory capacity, and disk capacity (multiple) are displayed.
Specify a cloning image to deploy. Cloning images can be selected from the available image pools. To manually install an operating system, select "None".
When "None" is selected, it is necessary to select the OS type on the [Server] tab.
For details, refer to "D.2 [Server] Tab".
If you specify a cloning image, the parameters for the operating system must also be specified. For details on the items that must be set, refer to "D.5 [OS] Tab".
Information
When a cloning image is specified, the sizes of system disks with the server type "VM" will be changed to that when the cloning image was deployed.
Select a network resource to connect to the NIC of the L-Server.
A list of the NICs defined in the L-Server template is displayed. Select the network to connect to each NIC from the "Network to Connect to" column.
When server model names have been described in the L-Server template, the number of NICs displayed will vary depending on the model name.
When the model name is BX series:
PRIMERGY BX620 series Number of NICs: 6 PRIMERGY BX920 series Number of NICs: 4 PRIMERGY BX922 series Number of NICs: 4 |
When the model name is something other than BX series:
The number of NICs will be 1, and <Add> and <Delete> buttons will be displayed in the network (NIC) parameters. Perform settings based on the physical server the L-Server will be located on.
Clicking <Add> adds a network.
Clicking <Delete> deletes the network in the last line of the list.
If the L-Server is a physical server, NIC number is the physical NIC number. The first NIC automatically becomes the admin LAN. Regardless of whether or not redundancy of the admin LAN is performed, network resources cannot be specified for the second NIC, so select "not connected".
A custom label can be defined for the L-Server. User-defined labels make it easier to identify the server.
Enter up to 32 alphanumeric characters or symbols.
A custom comment can be defined for the L-Server. For example, registering detailed work content, troubleshooting, and recovery procedures can speed up the recovery of affected applications when a problem occurs.
Enter up to 256 alphanumeric characters or symbols.
Click <OK>.
The L-Server is created.
Point
When manually installing the operating system in the L-Server or using the management console of server virtualization software, select the L-Server in the orchestration tree, and operate the VM for the VM_name displayed in [Resource Details].
The following name is automatically allocated for VM_name:
L-Server_name - Number
Number is automatically set by Resource Orchestrator to avoid a naming overlap on server virtualization software if an L-Server with the same name is created during "Appendix B Resource Folders" operations.
VM_name can be changed on server virtualization software. Even if VM_name is changed, L-Server and VM support are automatically maintained.
Note
When creating an L-Server, log off ETERNUSmgr of ETERNUS storage registered on ESC.
When operating NetApp storage in cluster environments and operating a partial system due to system trouble, perform operation after recovering the NetApp storage and returning the system to cluster operation.
When the status of the VM host and virtual storage is one other than "normal", the resource will be excluded from L-Server assignment regardless of its available space.
[Hyper-V]
When using the following SCVMM functions for the VM of the created L-Server, after this the L-Server will not be recognized or displayed in the orchestration tree, and operation of the L-Server becomes unavailable.
Saving in the library, deploying from the library
New Template
When "copying" is performed, the copied VM is not recognized as an L-Server.
Information
[Hyper-V]
VM guests created as L-Servers have the following configuration:
Connected to the primary channel (0) of IDE device
Connected to a SCSI adapter as data disk (*1)
Connected to the secondary channel (0) of IDE device
*1: Cannot be used on guest OS's without the integrated service. Only boot disks connected to the IDE adapter can be used.
When a guest OS that Hyper-V supports is specified, a converged network adapter will be used. When a different OS has been selected, an emulated network adapter will be added.
For details on the guest OS's supported by Hyper-V refer to the following Microsoft web site.
Microsoft web site
URL: http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx (As of November 2010) |
"1.00GHz Pentium III Xeon" (the SCVMM default value) is specified.
The CPU type is used for internal operations of SCVMM, and it does not indicate the CPU performance. It is also different from the information displayed for the computer information of the guest OS.
For cloning images, only system volumes are collected and deployed.
When registering a template created using SCVMM in the image pool of Resource Orchestrator, use a template created from a VM guest which has the system volume (a disk connected to primary channel (0) of the IDE device).
In other configurations, deploying using Resource Orchestrator will create VM guests without system volumes.
