HPE XP7 Automation Director User Manual page 327

A virtual server and its full set of configuration files
• Container server
A server that contains an exported virtual server to replicate
Usage guidelines
• If no virtual switch is specified, the connection-destination virtual switch information of the relevant NIC
is deleted. As a result, the NIC is disconnected from the virtual switch. Be sure to specify all necessary
virtual switches.
• For IP addresses to be set in the OS of the virtual server, enter only values that are treated as IP
addresses. For example, you must not specify special addresses such as a network address,
broadcast address, "0.0.0.0", or "255.255.255.255". If you enter such a special address, deployment of
the virtual server fails. In addition, for management-use IP addresses, enter IP addresses that allow
communication with the local server. If you enter an address that is correct but does not allow
communication with the local server, deployment might fail.
• While the virtual server is being deployed, make sure that other services do not operate the virtual
server. If other services operate the virtual server that is being deployed, deployment might fail. Direct
operation from the Hyper-V server is also prohibited.
• IP addresses are set as described in the Function Specifications. However, depending on the order in
which NICs are set in the OS of the virtual server, IP addresses might not be set as intended.
Therefore, after the virtual server has been created, check whether IP addresses are set as intended.
If IP addresses are not set as intended, correct the settings manually.
• Make sure that IP addresses set on the virtual server are not being used by other servers. If an IP
address that is set on another server is set, no NICs on the virtual server are enabled, sometimes
causing the task to terminate abnormally.
• Make sure that the settings to be specified during creation of the virtual server to be deployed have not
been set on the exported virtual server. If the computer name, host name, or IP address has already
been set on the exported virtual server, virtual server creation might fail (for example, an error occurs
in static-route related processing). If creation fails, delete the virtual server, re-create an exported
virtual server on which the computer name, host name, or IP address is not set, and then run this
service again.
• If deployment fails, the response file used to specify the initial OS settings and IP addresses on the
virtual server might remain on the system drive of the virtual server. If a response file remains, check
for the relevant response file in the task log, and delete the file. Alternatively, delete the virtual server.
• If folders in the specified import destination path do not exist, they are created.
• If virtual disk files remain in folders in the specified import destination path, the task terminates
abnormally. Check the folders in the specified path, and then delete them or specify another path.
• This service does not register virtual servers deployed for any services and applications of the failover
cluster manager. Register those servers manually according to the user operating requirements.
• When virtual disks on a virtual server are mounted to the Hyper-V server, available drive letters on the
Hyper-V server are temporarily locked. If there are no available drive letters, an error occurs when the
virtual disk is being mounted, and the task terminates abnormally. Before you run this service, make
sure that there are as many available drive letters on the Hyper-V server as the number of drives used
by the virtual disks on the exported virtual server.
• If the generation number of the exported virtual server is 2, for the hyperv.scsiDiskLocation property,
specify the location of the SCSI controller in which the virtual server's system disk is set. If the location
Additional service templates 327