Pre-setup preparations are required to create and manage VMware virtual machines as L-Servers of Resource Orchestrator.
For details on pre-setup preparations for VMware environments, refer to the VMware manual.
Preparations for Servers
In addition to the operations in "4.1.1.1 Preparations for Server Environments", the following operations are necessary.
Configure VIOM
When using I/O virtualization, configuration of VIOM is necessary.
Install and configure VMware ESX
When installing an OS on a physical server, refer to the server virtualization software manual.
When installing a VM host in an L-Server, refer to "Appendix F Installation of VM Hosts on Physical L-Servers".
Install and configure VMware vCenter Server
Necessary for management of VM hosts and L-Servers.
It is necessary to install the Microsoft Sysprep tools for VMware vCenter Server to enable collection of L-Server cloning images. For details on how to install the Microsoft Sysprep tools, refer to the installation section of "vSphere Basic System Administration" of VMware.
Refer to the relevant version of document, referring to the following URL:
vSphere Basic System Administration
URL: http://www.vmware.com/support/pubs/vs_pubs.html (As of February 2012) |
Configure VMware clusters
When performing movement between servers (migration), register the source and destination VM hosts for migration in the same cluster.
When not performing redundancy of L-Servers, it is not necessary to enable VMware HA or VMware DRS.
Design and configure VMware HA
When performing redundancy of L-Servers, VMware HA configuration must be done in advance.
Design and configure VMware DPM, VMware DRS, VMware FT, and VMware Storage VMotion
When using VMware DPM, VMware DRS, VMware FT, or VMware Storage VMotion, configure them in advance using VMware vCenter Server.
When setting configuration of VMware DRS or VMware DPM to "Manual", startup of L-Servers and VM guests may fail. For details, refer to "When using VMware DRS or VMware DPM".
When using VMware DRS or VMware DPM
It is necessary to configure the following settings beforehand, when moving L-Servers between VM hosts on VMware DRS or when turning on a VM host during an L-Server startup.
Configure VMware DRS and VMware DPM
Refer to VMware manuals and configure VMware DRS as "partly automatic" or "full automatic", or configure VMware DPM as "off" or "automatic".
When setting configuration of VMware DRS or VMware DPM to "Manual" and enabling the power control configuration of VMware DRS or DPM, startup of the L-Server may fail. In this case, start the L-Server from VM management software.
Configure power control for VMware DRS and DPM
When configuring power control for VMware DRS or DPM, specify "true", referring to "Server Virtualization Software Definition File" of "E.2.4 Configuration after Installation".
For details, refer to the VMware manual.
Information
When performing inter-cluster movement (migration), for VMware this means inter-resource pool movement (migration). Moving an L-Server (migration) is only possible in the same cluster (the same resource pool) because resource pools of VMware are not managed in Resource Orchestrator. For details on resource pools of VMware, refer to the "vSphere Resource Management Guide" of VMware.
Refer to the relevant version of the document, referring to the following web site:
URL: http://www.vmware.com/support/pubs/vs_pubs.html (As of February 2012) |
When Deploying VM Hosts Using Auto Deploy
Setup the Auto Deploy Server
Setup the Auto Deploy server.
For details, refer to the manual of server virtualization software.
Configure the DHCP Server
Prepare a server other than admin server, and configure the DHCP server to be used by the Auto Deploy function.
Perform configuration so the DHCP server assigns IP addresses only to VM hosts that have been configured using network boot services that use DHCP protocols such as Auto Deploy.
For details, refer to the manual of the server used as the DHCP server.
Configure the TFT Server
Prepare a server other than admin server, and configure the TFTP server to be used by the Auto Deploy function.
For details, refer to the manual of the server used as the TFTP server.
Setup a VM Host
Setup a VM host for a physical L-Server.
Refer to "Appendix F Installation of VM Hosts on Physical L-Servers" and set up VM hosts.
Point
When creating an L-Server, prepare a disk for the dump area.
At least one disk should be prepared specifying a disk that is not shared with other L-Servers.
On that disk, create a dump area for VMware ESXi.
For the first L-Server that uses Auto Deploy, prepare the necessary number of disks with the disk capacity necessary for storing VM guests to share with other L-Servers.
When there are two or more L-Servers, prepare the disk for storing VM guests connected to the first L-Server.
On that disk, create an area for VMFS to use as a datastore.
When configuring a VM host using Auto Deploy, use VIOM for I/O virtualization.
Note
As HBA address rename requires PXE boot, use in combination with Auto Deploy using the same PXE boot is not possible.
Storage Preparations
Check the following:
Volumes to allocate to VMware ESX have been already created
Zoning and affinity have been set
VMware ESX has been configured to recognize a VMFS datastore
Network Preparations
Check the following:
The configuration for the admin and public LANs has been designed
The network environment for the admin LAN is configured
The virtual switch to connect to the admin LAN has been designed and configured
When Using IBP
When using virtual L-Servers, connect the IBP uplink sets used for the public LAN and admin LAN to the VM host regardless of VIOM, after creating each IBP uplink set.
It is not necessary to use the same name for the uplink set and the name of the network resource.
Point
For VMware virtual switches, configuration is not necessary as they are automatically configured by Resource Orchestrator.
When performing movement between servers (migration), configure the VMkernel port group for VMotion on each VM host.
For details on how to configure the VMkernel port group, refer to the information in "vSphere Basic System Administration" of VMware.
Refer to the relevant version of the document, referring to the following web site:
vSphere Basic System Administration
URL: http://www.vmware.com/support/pubs/vs_pubs.html (As of February 2012) |
When Using Distributed Virtual Switch (VMware vDS)
In Resource Orchestrator, the NICs of VM guests and port groups can be connected to the port groups of a distributed virtual switch (VMware vDS). The port groups of the distributed virtual switch should be configured beforehand manually.
When using VMware vDS, the following preparation is necessary:
Create Port Groups of the Distributed Virtual Switch
Refer to the VMware manual, and create them manually.
Define the Correspondence of the Port Groups of the Distributed Virtual Switch and VLAN IDs
Create the distributed virtual network definition file shown below, and associate the port groups and the VLAN IDs:
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
vnetwork_vmware.rcxprop
Describe the distributed virtual network definition file in individual lines in the following format:
"Port_group_name_of_Distributed_Virtual_Switch"=VLAN ID[,VLAN ID...] |
For the VLAN ID, an integer between 1 and 4094 can be specified. When specifying a sequence of numbers, use a hyphen ("-") such as in "1-4094".
Example
"Network A"=10 |
Blank spaces before and after equal signs ("=") and commas (",") are ignored.
Describe the port group name of the distributed virtual switch correctly, as entry is case-sensitive.
Use the UTF-8 character code.
When there are multiple lines with the same distributed virtual switch port group name, all specified lines are valid.
When the same VLAN ID is used in lines where the port group names of different distributed virtual switches are described, the VLAN ID in the first line is valid.
Place the Distributed Virtual Switch Usage Configuration File
Place the distributed virtual switch use configuration file. Create the following folder and place an empty file in it.
[Windows]
Installation_folder\Manager\etc\vm
[Linux]
/etc/opt/FJSVrcvmr/vm
vds_vc
When Using the Definition for Port Groups Excluded from the Selections for Automatic Network Configuration
If the names of the port groups to be excluded from automatic network configuration have been specified in the VMware excluded port group definition file, creation of L-Servers is possible, even if the VLAN set for the service console or VMkernel network and the one set for the port group on the virtual switch is the same.
When using a VMware excluded port group definition, the following preparation is necessary:
On the managed server, create a port group of the service console (or VMkernel) and the virtual switch that use the same VLAN ID.
Refer to the VMware manual, and create them manually.
Create a VMware excluded port group definition file, and define the name of the service console created at 1. as the port group name to be excluded.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
vnetwork_excluded_vmware.rcxprop
Describe the VMware excluded port group definition file in individual lines in the following format:
Port_group_name_to_be_excluded |
Example
Service Console |
Lines starting with "#" are regarded as comments, and ignored.
Blank lines are ignored.
Describe Port_group_name_to_be_excluded correctly, as the entry is case-sensitive.
Use the UTF-8 character code.
For the Port_group_name_to_be_excluded, from the front of the line to the line break code in each line is regarded as a single name.
When there are multiple lines with the same Port_group_name_to_be_excluded, all specified lines are valid.
Note
When using the definition of the port groups excluded from the selections for automatic network configuration, take note of the following points:
The VLAN of the service console and VMkernel network is the admin LAN. As this configuration allows a public LAN using the same VLAN, security risks increase.
For these reasons, that this configuration is for users using the same VLAN in the system configuration. The infrastructure administrator should determine if these directions can be used or not, taking possible security risks into account.
When Performing Alive Monitoring (Heartbeat Monitoring) for L-Server
For Resource Orchestrator alive monitoring functions, "VM Monitoring" functions for VMware HA are used. Therefore, configure the following settings:
Configure VMware clusters
Configure VMware clusters in a VM host operating an L-Server.
Configure VMware HA
Enable VMware HA in VMware clusters configured in 1.
When using Console Connections from Public LAN
Use the following procedure when using console connections from the public LAN. For details on the configuration method, refer to the VM management software manual.
Create a virtual switch to connect with the public LAN on VM management software.
Create a Service Console or port group for VMKernel on the created virtual switch on VM management.software.
When using VMware ESX
Create a port group for Service Console.
When using VMware ESXi
Create a port group for VMKernel.
When creating port groups for Service Console or VMkernel, configure IP addresses and VLAN IDs for the VM host to match to the settings of the public LAN which is the destination for connection. When using multiple network resources as public LANs, create port groups for Service Console or VMKernel corresponding to each resource, and configure the IP addresses and VLAN IDs appropriately.
Configure port groups excluded from the selection for automatic network configuration in Resource Orchestrator.
The VLAN ID for network resources corresponding to the public LAN and the VLAN ID for Service Console or VMKernel may be the same. Therefore, define the port group for the Service Console or VMKernel created in 2. for the port group to be excluded from selection for automatic network configuration.
For details, refer to "When Using the Definition for Port Groups Excluded from the Selections for Automatic Network Configuration".
Configure the IP addresses to exclude from allocation in Resource Orchestrator.
Set the IP address of the VM host configured for public LANs in 2., in the network corresponding to the public LAN, to be excluded from allocation.
For details, refer to the following:
"3.6 Modifying Network Resource Specifications" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"7.3.1 Creating New Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
