In addition to the operations in "Chapter 8 Defining and Configuring the Server Environment", the following operations are necessary.
Configure VIOM or ISM
When using I/O virtualization, configuration of VIOM or ISM 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 on an L-Server, refer to "Appendix A Installing VM Hosts on Physical L-Servers" in the "Setup Guide CE".
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 |
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 performed in advance.
When using VMware HA admission control, set "Percentage of cluster resources reserved" or "Specify failover hosts" for the admission control policy.
When multiple VM hosts are set for "Specify failover hosts", or a policy other than the above is set, the L-Server may fail to start.
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" in "8.2.1 Creating Definition Files" in the "Setup Guide CE".
When using a console connection of an L-Server of VMware vSphere (VMware vSphere 5.1 or later)
The console connection of an L-Server of VMware vSphere communicates with the VM host on which the L-Server operates according to the proxy settings of the browser.
To use the console connection of an L-Server of VMware vSphere through the proxy server, connect a virtual switch of the admin LAN of the VM host to the proxy server.
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 |
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 A Installing VM Hosts on Physical L-Servers" in the "Setup Guide CE", 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 or ISM 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.
When Using VMware vSphere 6 or later as a VM Host
When estimating the memory size of the VM host, include the overhead memory size in the memory size of all VM guests that operate on the VM host.
When estimating the overhead memory size of VM guests, refer to the web site at the following URL.
VMware web site
URL: |
Configuring Console Connection of a Virtual L-Server of VMware vSphere Using VMware VSAN or VMware vSphere 6.5 or Later
Install VMware vSphere PowerCLI 6.0 or later, and confirm that VMware PowerCLI (32-bit) starts.
For details, refer to the manuals of VMware vSphere PowerCLI.
Note
If PowerCLI is installed after the admin server is configured, operation of PowerCLI using Resource Orchestrator may not function properly.
In this case, restart the admin server.
For details on how to start and stop the admin server, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
When the admin server is not connected to the Internet, it takes longer to load PowerCLI, which may inhibit the processes of this function.
For this reason, be sure to connect the admin server to the Internet.
When it is not possible to connect to the Internet, perform the following two procedures on the admin server:
Disable the "Microsoft Trusted Root Certificate Program"
Open the Local Group Policy Editor.
Select [Computer Configuration]-[Windows Settings]-[Security Settings]-[Public Key Policies].
Double-click [Certificate Path Validation Settings].
Click the [Network Retrieval] tab.
Check the [Define these policy settings] checkbox.
Clear the [Automatically update certificates in the Microsoft Root Certificate Program] checkbox.
Information
Leave the [Allow issuer certificate (AIA) retrieval during path validation] checkbox checked. This item affects how certificate chains are validated.
Validation of certificate chains
If necessary, download CA certificates other than the root certificate (intermediate certificates) based on the path described for authority information access (AIA) of certificates. Construct a certificate chain to the root CA certificate using these intermediate certificates.
Click [OK].
Restart the OS.
Disable the setting for checking certificate revocation
Open the Registry Editor.
Open the following registry key.
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing |
Modify the value of [State (REG_DWORD)] as follows.
Before modification | 0x00023c00: Enabled |
After modification | 0x00023e00: Disabled |
