4.6.3 673XX Series

This section explains the 673XX message series.

67302

FJSVrcx:ERROR:67302:path:system file not found

Description

The file or directory specified for path was not found.

Corrective Action

Check that the manager package is correctly installed.

In a clustered manager configuration, there is a chance that setup of the cluster service for the manager has not been performed successfully. Refer to the directory displayed for path and "C.3 Configuration" in the "Setup Guide VE", and check if the setup of the cluster service for the manager has been performed successfully.

67305

FJSVrcx:ERROR:67305:file:invalid configuration

Description

The configuration file indicated for file is invalid.

Corrective Action

Check the system log, resolve the problem, and execute the command again.

If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output

67313

FJSVrcx:ERROR:67313:failed to check configuration

Description

A configuration check failed.

Corrective Action

Check the system log, resolve the problem and execute the command again.

If an error message regarding the disk or file system has been output

67320

FJSVrcx:ERROR:67320:power control error. target=target detail=detail

Description

An error occurred during power control operation for target.
Take corrective action for the content displayed for detail.

When detail is "duplicate resource name"
When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "duplicate resource name": The power state of the VM guest cannot be controlled because multiple VM names on the VM host conflict. Change the names so that they differ because there is an error in the VM host settings.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "16"

A VM host was not found. There are the following two possibilities:

Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

[Hyper-V]

There is a possibility that Hyper-V has not been installed or that role has not been enabled.
Check that Hyper-V has been installed and the role has been enabled.

When error_number is "17": A VM guest was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM guest has been deleted.
Use the VM management console and check that the VM guest is not configured to move when its power status changes.

When error_number is "101", "110", "111", "112", "114", or "116": Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "113"

Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details on the values for login account information, refer to the following:

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" or "9.6 Changing VM Management Software Settings" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "100" or "115": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host or VM management software.
For details, refer to "9.1.7 Changing VM Host Login Account Information" or "9.6 Changing VM Management Software Settings" in the "User's Guide VE".

When error_number is "104", "105", "135", or "136": Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.

When error_number is "122"

Perform one of the following corrective actions:

The VM maintenance mode is set for the VM host. Perform the operation again after disabling the VM maintenance mode for the VM host.
The server is inoperable due to its power status. Check the status of the VM guest.

When error_number is "123": There is a chance that settings for VM guest power operation, which must be performed in advance, have not been performed. For the settings for VM guest power operation that must be performed in advance, refer to "9.2.1 Configuration Requirements" in the "Design Guide VE".

When error_number is "124"

There are the following possibilities:

There is a chance that settings for VM guest power operation, which must be performed in advance, have not been performed.
Check that settings for VM guest power operation have been performed in advance. If they have not been performed, make the necessary settings and then perform the operation again.
For the settings for VM guest power operation that must be performed in advance, refer to "9.2.1 Configuration Requirements" in the "Design Guide VE".
The VM host or VM management software license necessary for operation may not be possessed.
Check the license status using the VM management software.
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host or VM management software.
For details on the values for login account information, refer to the following:
- For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" or "9.6 Changing VM Management Software Settings" in the "User's Guide VE".
- For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "125": Processing of other tasks is being executed on the VM host. Check if operations are not performing from other clients at the same time, and then perform the operation.

When error_number is "127"

Power control processing of the VM guest failed. There are the following two possibilities:

Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.

[Hyper-V]

Check whether a virtual machine OS has been installed and if the OS has been started.
If an OS has not been installed on a virtual machine, install and start one.
If the OS is not running on the virtual machine, perform the operation after starting up the OS.

When error_number is "400"

Processing of a VM host remote command failed.
There are the following possibilities:

There are problems in the operating status or the network settings of the VM host
Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.
The status of the specified VM guest is not appropriate
When target is the VM guest, the status of the specified VM guest may not be appropriate.
Check the status of the VM guest.
The execution conditions of power operations are not fulfilled
The execution condition of power operation may not be fulfilled.
Refer to the manual of the server virtualization software or "14.1 Server Power Control" in the "User's Guide VE" for execution conditions of operations.

[Solaris Zones]
Check if the disk that contains the non-global zone is mounted on the global zone and can be accessed from the file system.

[OVM for SPARC]
When the function is not supported by OVM for SPARC, stopping and rebooting of the VM guest cannot be performed.
Based on the virtual machine status, either directly operate the virtual machine, or perform a forced stop or forced reboot.

When error_number is "547"

The following might apply:

VM host/VM management software may not meet the requirements necessary for starting the target VM guest.
Use SCVMM to check whether the VM host/VM management software meet the requirements.
When using System Center 2016 Virtual Machine Manager, powering on a VM guest for which start order priority is configured may cause an error in Resource Orchestrator due to a problem with SCVMM.
Ignore this error, as the VM guest will still be powered on as intended.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

An error occurred during power control operation for target.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
If detail is "VM guest detected on multiple VM hosts (server_name1,server_name2,...)"
When detail is "(xm create::Error: VM name 'VM_guest_name' already in use by domain number ,vmerrno=400,ip=IP_address)" or "(xm shutdown::Error: Domain 'VM_guest_name' does not exist.,vmerrno=400,ip=IP_address)"

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "17" or "104"

The VM guest could not be found. Check the following:

Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted.
Check whether the VM guest is set to be moved when its power status is changed using the VM management console.

The following causes are possible:

Migration has been performed on VMware.
VMware DRS has been enabled.
VMware DPM has been enabled and a VM host in standby mode exists in the same cluster as the target VM host of L-Server creation.

For a. and b.:
In the ROR console orchestration tree, right-click the target L-Server, and select [Update] from the popup menu. Check if the resource status of the updated L-Server is normal.
For c:
Start the L-Server from VM management software.

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "100" or "115": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on the values for login account information, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "104", "105", "135", or "136"

Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
When the CPU or memory to be allocated to a VM guest is insufficient, depending on your environment, either migrate the VM guest to another VM host, or stop the VM guest.

[VMware]
When VMware DPM is enabled and there is a VM host in standby mode in a VMware cluster with a VM guest, start the VM guest from VM management software.

If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

When error_number is "123"

The error may be the result of one of the following:

There is a chance that settings for VM guest power operation, which must be performed in advance, have not been performed. For the settings for VM guest power operation that must be performed in advance, refer to "9.2.1 Configuration Requirements" in the "Design Guide VE".
The software required for power control on the VM guest may not have been started. Perform the operation again after referring to the server virtualization software manual and checking whether the required software has been started.

When error_number is "400"

Processing of a VM host remote command failed.
There are the following possibilities:

There are problems in the operating status or the network settings of the VM host
Check the operation status and network settings of the VM host. If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.
The status of the specified VM guest is not appropriate
When target is the VM guest, the status of the specified VM guest may not be appropriate.
Check the status of the VM guest.
The execution condition of power operation is not fulfilled
The execution condition of power operation may not be fulfilled.
Refer to the manual of the server virtualization software or "Chapter 8 Configuration when Creating Virtual L-Servers" in the "Setup Guide CE" for execution conditions of operations.

[Solaris Zones]
Check if the disk that contains the non-global zone is mounted on the global zone and can be accessed from the file system.
Check if the disk storing the VM guest corresponding to the L-Server that is the target of the operation is accessible from the file system mounted on the VM host.

When there are multiple L-Servers (guest domains) that share a specific disk on the same host, those L-Servers cannot be started simultaneously.

Take one of the following actions:

Start the L-Server after migrating the L-Server to another VM host.
Start the L-Server after migrating the L-Server that is sharing the disk to another VM host.
Start the L-Server after stopping the L-Server that is sharing the disk.

When error_number is "547"

The following might apply:

VM host/VM management software may not meet the requirements necessary for starting the target VM guest.
Use SCVMM to check whether the VM host/VM management software meet the requirements.
When using System Center 2016 Virtual Machine Manager, powering on a VM guest for which start order priority is configured may cause an error in Resource Orchestrator due to a problem with SCVMM.
Ignore this error, as the VM guest will still be powered on as intended.
If Key Storage Drive or encryption has been enabled for the VM guest, startup may fail.
Confirm the Key Storage Drive and encryption settings of the target VM guest.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

If detail is "VM guest detected on multiple VM hosts (server_name1,server_name2,...)"

[KVM]
The relevant VM guest may exist on multiple VM hosts. In this case, data referred to from the VM guest may be damaged when the VM guest is powered on.
Check whether the following message is repeatedly output in the event log.

FJSVrcx:INFO:21163:obj:VM guest is migrated.

If the message is repeatedly output
Request an infrastructure administrator of Resource Orchestrator to take corrective action.
For corrective actions, refer to "Configuration for L-Server Live Migration" in "8.6.9 Advisory Notes for RHEL-KVM Usage" in the "Setup Guide CE".
If the message is not repeatedly output
Update the information displayed in the ROR console, and then perform the operation again.
To update the information, right-click the target server in the server resource tree of the ROR console, and select [Update] from the displayed menu. It takes several tens of seconds to be updated.
Update the information for all servers displayed for server_name.

When detail is "(xm create::Error: VM name 'VM_guest_name' already in use by domain number ,vmerrno=400,ip=IP_address)" or "(xm shutdown::Error: Domain 'VM_guest_name' does not exist.,vmerrno=400,ip=IP_address)": If system failure occurs on the manager after L-Server power operations (power on or off, or reboot), restoring the manager automatically performs the power operation, and it may fail.
As a power operation is being performed on the L-Server, ignore the error.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67321

FJSVrcx:ERROR:67321:image not found.

Description

The cloning image image was not found.

Corrective Action

Check that the specified cloning image or the specified version of the cloning image exists.
Check the version using the rcxadm image list command.

For details, refer to the following:

For Virtual Edition, refer to "4.1 rcxadm image" in the "Reference Guide (Command) VE".
For Cloud Edition, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE".

After checking the image exists, specify the correct cloning image, and then perform the operation again.

In some cases, the image file may not have been synchronized.
Refer to the following:

Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE", and restart the manager service.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE", and restart the manager service.

67322

FJSVrcx:ERROR:67322:agent is not registered. target=target

Description

The command cannot be executed because an agent has not been registered for the physical server target.

Corrective Action

An agent has not been registered for the specified physical server.
After registering an agent, perform the operation again.

67324

FJSVrcx:ERROR:67324:product-key is not set. target=target

Description

The Windows product key was not specified when installing an agent on the physical server target.

Corrective Action

The Windows product key was not specified when installing an agent on the specified physical server. Correct the license information file.
For details, refer to the following:

For Virtual Edition, refer to "17.2 Collecting" in the "User's Guide VE".
For Cloud Edition, refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

67325

FJSVrcx:ERROR:67325:illegal IP address. target=target, IP=ip

Description

The IP address ip set when installing the agent on the physical server target is invalid.

Corrective Action

Check if ip is the admin LAN IP address of the admin server.
If it is not the IP address of the admin server, set the admin LAN IP address of the admin server for the module for image file operation.
For the IP address settings for the module for image file operation, refer to "4.1 An Error Occurs When Performing Backup and Restore of System Images or Collection and Deployment of Cloning Images. [Physical Servers] [Hyper-V]" in "Troubleshooting".
When "-" is displayed for ip, no values have been set.

67326

FJSVrcx:ERROR:67326:illegal hostname. target=target, hostname=hostname

Description

The server name hostname set when installing the agent on the physical server target is invalid.

Corrective Action

Check the following:

hostname is the admin server name.
The admin server IP address used on the managed server can be resolved using the server name.
If it is not the admin server name, in the IP address settings for the module for image file operation set the host name or IP address of the admin server to enable it to be resolved using the admin LAN.
For the IP address settings for the module for image file operation, refer to "4.1 An Error Occurs When Performing Backup and Restore of System Images or Collection and Deployment of Cloning Images. [Physical Servers] [Hyper-V]" in "Troubleshooting".
If the host name cannot be resolved, review the settings concerning the resolution of host names such as the DNS.

67328

FJSVrcx:ERROR:67328:failed to set hostname. target=target

Description

Setting of the host name during cloning image deployment failed.
Or the ServerView Agents may not have been able to obtain the host name after it was set.
Deployment of the cloning image has been completed, but setting and post-processing of the host name and public LAN has failed.

Corrective Action

ServerView Agents may have failed due to excessive load on the network or the server.
Check using the following procedure and recover the managed server the image was deployed to.
When a single cloning image was being deployed to multiple managed servers, take corrective action for all of the managed servers.

Log in to the managed server and check that the specified host name has been set.
- When it has not been set
  Change the host name following the procedure for the OS.
  If ServerView Agents is stopped, start it.
  [Linux]
  When using SUSE Linux Enterprise Server, if server names including periods (".") are configured for post-deployment server names of cloning images, configuration may fail.
  Specify post-deployment server names of cloning images that do not include periods (".").
- When it has been set
  Obtaining information from the ServerView Agents failed.
  Restart the ServerView Agents.
Based on the registration status of the agent prior to deployment, perform one of the following:
- When an agent has already been registered
  Update the server from the GUI, and check if the changed host name is displayed on the GUI.
- When an agent has not been registered
  Register an agent.
For Virtual Edition, When using the network parameter auto-configuration function, refer to "17.6.1 Operation Checks and Preparations" in the "User's Guide VE" and manually execute the network parameter setup command.
If releasing the server from maintenance mode was specified for after deployment, manually release the server from maintenance mode.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67329

FJSVrcx:ERROR:67329:image is already in use.

Description

The cloning image image is in use.

Corrective Action

After the operation using the specified cloning image is completed, perform the operation again.

67330

FJSVrcx:ERROR:67330:illegal operation specified for spare server. target=target

Description

An invalid operation was specified for the spare server target.

Corrective Action

The specified operation cannot be performed on the spare server.
Release the settings of the spare server, and then perform the operation again.

67331

FJSVrcx:ERROR:67331:too many versions of cloning image exist. image=name

Description

name exceeds the maximum number of versions that can be stored.

Corrective Action

When the number of collected cloning images exceeds the maximum number of versions that can be stored
Refer to the following, and delete excess cloning images so there are less than the maximum.
- For Virtual Edition, refer to "16.5 Deleting" in the "User's Guide VE".
- For Cloud Edition, refer to "17.5.4 Deleting" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When collection of a cloning image with the same name is performed multiple times
After completing the collections performed simultaneously, perform the operation again.

67333

FJSVrcx:ERROR:67333:failed to get information from vmhost. detail=detail

[Cloud Edition]

Description

Information could not be obtained from a VM host.

In vmhost, the VM host name is displayed.
"OS list" is displayed in detail.
The list information of operating systems that can be specified could not be retrieved when creating a VM guest.

Corrective Action

Refer to the management screen of the server virtualization software, and check whether the VM host displayed in vmhost is set to the VM maintenance mode. If the VM host is set to the VM maintenance mode, disable the maintenance mode.

67334

FJSVrcx:ERROR:67334:failed to restore image. detail=detail

[Cloud Edition]

Description

Failed to restore a VM guest.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "17"
  The VM guest/image could not be found. Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest/image has been deleted.
- When error_number is "19"
  The image could not be found. Wait for around three minutes and then repeat the operation.
- When error_number is "99"
  Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
  Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", "116", or "148"
  Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "104", "105", "135", "136", or "508"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
  Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
- When error_number is "113"
  Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "141", "143", "144", "145", "146", or "147"
  The VM guest could not be restored using an image. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "142"
  Failed to restore an image because another operation was performed on the VM guest to restore. Perform the operation again after waiting a while.
- When error_number is "400" [Citrix Xen] [OVM for x86 3.x]
  Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
  If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67335

FJSVrcx:ERROR:67335 : registering VM guest failed. detail=detail

Description

Registration of a VM guest has failed.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
When error_number is "6", "7", "8", or "9"
Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
When error_number is "15"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When error_number is "16"
A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
When error_number is "100" or "115"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When error_number is "101", "110", "111", "112", "114", or "116"
Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
When error_number is "104", "105", "135", or "136"
Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software.
When operation is not possible using VM management software, there is a problem with the VM host or VM management software.
Resolve the problem with the VM host or VM management software, and then perform the operation.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
When error_number is "113"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software.
The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67336

FJSVrcx:ERROR:67336 : unregistering VM guest failed. detail=detail

Description

Unregistration of a VM guest has failed.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
When error_number is "6", "7", "8", or "9"
Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
When error_number is "15"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When error_number is "100" or "115"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When error_number is "101", "110", "111", "112", "114", or "116"
Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
When error_number is "104"
Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software.
When operation is not possible using VM management software, there is a problem with the VM host or VM management software.
Resolve the problem with the VM host or VM management software, and then perform the operation.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
When error_number is "113"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software.
The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67337

FJSVrcx:ERROR: 67337: registering cloning image with VM management software failed. detail= detail

Description

Registration of the cloning image with the VM software.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from the IP address. Take corrective action based on the error number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "16"
  A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
  Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "104", "105", "135", or "136"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software.
  When operation is not possible using VM management software, there is a problem with the VM host or VM management software.
  Resolve the problem with the VM host or VM management software, and then perform the operation.
  Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
- When error_number is "113"
  Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software.
  The login account information may have been changed after the VM host or VM management software was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67338

FJSVrcx:ERROR: 67338: unregistering cloning image from VM management software failed. detail=detail

Description

Unregistration of the cloning image from the VM software failed.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from the IP address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "16"
  A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
  Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "104", "105", "135", or "136"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software.
  When operation is not possible using VM management software, there is a problem with the VM host or VM management software.
  Resolve the problem with the VM host or VM management software, and then perform the operation.
  Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
- When error_number is "113"
  Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software.
  The login account information may have been changed after the VM host or VM management software was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67340

FJSVrcx:ERROR:67340:manager program still starting

Description

Startup of the manager has not been completed.

Corrective Action

Check whether the "Related Services" have been started on the admin server.

If they have not been started
Stop the "Manager Services" and then start the "Related Services". After that, restart the "Manager Services".
For details on how to stop and start managers, refer to the following:
- Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
- Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
If they have been started
Wait a couple of minutes and then execute the command again.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67350

FJSVrcx:ERROR:67350:configuration error. target=target

Description

There may be a problem in the setting file for communicating with target.

Corrective Action

Collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

There may be a problem in the setting file for communicating with target.

Corrective Action

Take corrective action based on the content of target.

"storage unit"
Refer to "7.1.1 Creating Definition Files Combining Ports of SAN Storage" in the "Setup Guide CE" and correctly describe the port combination definition file of the SAN storage.
Cases other than the above
Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.

67351

FJSVrcx:ERROR:67351:SSL certification error. target=target

Description

The SSL certifications of the target and manager may be different.

Corrective Action

For details on how to check and take corrective actions, refer to "4.2 An Error Occurs during Cloning after the Manager is Reinstalled." in "Troubleshooting".
When this message is displayed during deployment of a cloning image, deployment has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".

67352

FJSVrcx:ERROR:67352:connection timeout. target=target

[Virtual Edition]

Description

Communication may have failed temporarily because there is a problem in the network environment or the load of the server target is high.
When target is the IP address of the managed server, communication with the agent may have failed.

Corrective Action

Check the corrective action for "Message number 67356", resolve the problem, and then perform the operation again.
When this message is displayed during deployment of a cloning image, deployment has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".

When target is the IP address of the managed server, also check the corrective action of "Message number 67355".

If this does not resolve the problem, changing the timeout value may resolve the problem.

Collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Corrective Action

When the managed server is VMwareESXi and another vendor's server, the definition file may not exist or the target managed server may not have been defined in the definition file.

Confirm that there is no error in the filename or content of the definition file, referring to "8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE".

When target is the IP address of the managed server, also check the corrective action of "Message number 67355".

If this does not resolve the problem, changing the timeout value may resolve the problem.
Collect troubleshooting information and contact Fujitsu technical staff.

67353

FJSVrcx:ERROR:67353:read timeout. target=target

Description

Communication may have failed temporarily because the load of the server target is high.

Corrective Action

Check the following:

For Virtual Edition, this message is also displayed when collecting or deploying cloning images fails because incorrect automatic settings such as the following were made using the network parameter auto-configuration function for cloning images.
For the network parameter auto-configuration function that can be defined for cloning images, refer to "17.6 Network Parameter Auto-Configuration for Cloning Images" in the "User's Guide VE".
- Automatic settings were performed for the admin LAN
- Automatic settings for the public LAN were performed using an IP address of the same subnet as the admin LAN IP address
Log in to the managed server for which collection or deployment of cloning images failed, and check the definition file of the network parameter auto-configuration function to see whether incorrect settings such as those above were performed.
When automatic settings were performed, perform the operation again using the following procedures:
- Recovery of the failed managed server
  Execute the rcxadm lanctl unset command and release the automatic settings.
  For details on the rcxadm lanctl unset command, refer to "5.9 rcxadm lanctl" in the "Reference Guide (Command) VE".
  When the admin LAN IP address has not been set on the managed server, set it manually. If the status of the managed server does not change to "normal", refer to the corrective action of "Message number 67192".
- Re-collection of cloning images
  Correct the definition file of the network parameter auto-configuration function on the managed server from which a cloning image is to be collected, and then collect the image again.
  When deployment of a cloning image fails, collect and then deploy a cloning image to the managed server again.
  If any cloning images were not collected or deployed successfully, delete them.
Changing the timeout value may resolve the problem.
Collect troubleshooting information and contact Fujitsu technical staff.
If this error occurs when executing the rcxadm vmmgr refresh command, the cause may be that VM management software has not been registered.
Register the VM management software and perform the operation again.
If not registering VM management software, delete the following two files and perform the operation again.
[Windows Manager]
Installation_folder\SVROR\Manager\var\update_time
- vm_mgmt_soft_begin
- vm_mgmt_soft_end

67354

FJSVrcx:ERROR:67354:write timeout. target=target

Description

Communication with the server target might not be possible or have failed temporarily because the load is high.

Corrective Action

Check "Check the network route", resolve the problem, and perform the operation again.

Check the network route

How to Check
Execute the ping command on the server where a manager is installed to check the network status. Check if it is possible to communicate with the server target.

[Windows]

>ping the_IP_addresses_of_managed_servers <RETURN>

<Example: Normal communication>

Pinging ipaddr with 32 bytes of data:

Reply from ipaddr: bytes=32 time<1ms TTL=128
Reply from ipaddr: bytes=32 time<1ms TTL=128
Reply from ipaddr: bytes=32 time<1ms TTL=128
Reply from ipaddr: bytes=32 time<1ms TTL=128

Ping statistics for ipaddr: Packets: Sent = 4, Received = 4, Lost = 0(0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum =0ms, Average = 0ms

<Example: Abnormal communication>

Pinging ipaddr with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for ipaddr: Packets: Sent = 4, Received = 0, Lost = 4(100% loss),

[Linux]

# ping the_IP_addresses_of_managed_servers <RETURN>

<Example: Normal communication>

PING host name (ipaddr) 56(84) bytes of data.
64 bytes from ipaddr: icmp_seq=1 ttl=64 time=2.18 ms
64 bytes from ipaddr: icmp_seq=2 ttl=64 time=0.171 ms
64 bytes from ipaddr: icmp_seq=3 ttl=64 time=0.191 ms

<Example: Abnormal communication>

PING host name (ipaddr) 56(84) bytes of data.
From ipaddr icmp_seq=1 Destination Host Unreachable
From ipaddr icmp_seq=2 Destination Host Unreachable
From ipaddr icmp_seq=3 Destination Host Unreachable

Corrective Action
Check the following items:

For <Example: Normal communication>

For <Example: Abnormal communication>

target checks: Check if the server target is running. The network connection function of the server target may have stopped during communication. Check if the network connection function has been stopped before or after the error occurred, and then perform the operation again.

Firewall checks

Check the settings of firewall software set between the admin server and managed servers or in managed servers.

Assign permission for communication to the necessary ports, referring to the following:

Refer to "Appendix A Port List" in the "Design Guide VE".
Refer to "Appendix A Port List" in the "Design Guide CE".

IP address checks: Check if the IP address displayed in the error message is correct and if necessary specify the correct IP address, and then perform the operation again.

LAN network checks: Check if the network cable is connected to the server target.

Certificate checks between the manager and the agent: When the SSL certificates of the manager and the agent do not match, initialize the certificates.

When this message is displayed during deployment of a cloning image, deployment has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".

If this does not resolve the problem, changing the timeout value may resolve the problem.
Collect troubleshooting information and contact Fujitsu technical staff.

67355

FJSVrcx:ERROR:67355:connection error. target=target

Description

The program of target may not have been started.

Corrective Action

After checking if the destination server for communication has been started by referring to the following manuals, resolve the problem, and then perform the operation again.

Check the communication destination
For Virtual Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide VE", and start the destination server for communication.
For Cloud Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE", and start the destination server for communication.
- When target is the name of external software
  Refer to the manual of the software and start the service of the external software.
- When target is "Task Manager"
  Collect troubleshooting information and contact Fujitsu technical staff.
  [OVM for SPARC]
  - If the change function of "auto-boot?" is enabled when migration of a virtual L-Server or a VM guest is performed, the saving of the configuration information during the migration process has failed.
    Save configuration information after checking the preset value of "auto-boot?"" with reference to the "Procedure that restores the preset value of "auto-boot?"" of "Message number 67375".
  - When it matches the following conditions, the serial L-Server creation process has failed.
    - When multiple L-Servers with a Solaris 11 image specified are created simultaneously
    - "true" is specified in the "Operation mode definition file for when simultaneously creating multiple L-Servers with a Solaris 11 image specified" in "8.8.1 Creating Definition Files" in the "Setup Guide CE".
    When the created guest domain is not deleted, delete it referring to "Deletion procedure for guest domains" given in "Message number 67373".
- When target is "Resource Coordinator Manager"
  Check the status of the manager services. If they have not been started, start them.
  - For Virtual Edition
    Refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide VE".
  - For Cloud Edition
    Refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE".
Port number checks
Check the port numbers of the admin server and managed servers. If there are any mistakes, change the port number to the right one.
- For Virtual Edition
  - For how to change port numbers, refer to "Appendix A Port List" in the "Design Guide VE".
  - For how to change port numbers, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
- For Cloud Edition
  - For how to change port numbers, refer to "Appendix A Port List" in the "Design Guide CE".
  - For how to change port numbers, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Perform the following corrective action:

When this message is displayed during deployment of a cloning image
Deployment of the cloning image has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".
When operating managers in clusters
There is a chance that the shared disk for managers is not mounted.
Mount the shared disk for managers on the node the operation was performed on and perform the operation again.
When registering the rack mount or tower servers on VMware ESXi
Clear the [Register agent] checkbox, and register the agent after completing server registration.
When reconfiguring the hardware information of rack mount or tower servers on VMware ESXi
Power off the server and then reconfigure the hardware information.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

[Cloud Edition]

Description

The program of target may not have been started.

Corrective Action

After checking if the destination server for communication has been started by referring to the following manuals, resolve the problem, and then perform the operation again.

Check the communication destination
Refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE", and start the destination server for communication.
- When target is 127.0.0.1
  The services of Resource Coordinator Manager on the admin server may not have been started. Start the services.
Port number checks
Check the port numbers of the admin server and managed servers.
If there are any mistakes, change the port number to the right one.
For how to check port numbers, refer to "Appendix A Port List" in the "Design Guide CE".
For how to change port numbers, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

67356

FJSVrcx:ERROR:67356:no route to host. target=target

Description

There may be a problem with the network environment.

Corrective Action

Check "Check the network route", resolve the problem, and perform the operation again.

Check the network route

How to Check
Execute the ping command on the server where a manager is installed to check the network status. Check if communication with the agent is possible.

[Windows Manager]

>ping the_IP_addresses_of_managed_servers <RETURN>

<Example: Normal communication>

<Example: Abnormal communication>

Pinging ipaddr with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for ipaddr: Packets: Sent = 4, Received = 0, Lost = 4(100% loss),

[Linux Manager]

# ping the_IP_addresses_of_managed_servers <RETURN>

<Example: Normal communication>

<Example: Abnormal communication>

Corrective Action
Check the following items:

For <Example: Normal communication>

For <Example: Abnormal communication>

target checks: Check if the server target is running. The network connection function of the server target may have stopped during communication. Check if the network connection function has been stopped before or after the error occurred, and then perform the operation again.

Firewall checks

Check the settings of firewall software set between the admin server and managed servers or in managed servers.

For Virtual Edition, give the permission for communication to ports listed in "Appendix A Port List" in the "Design Guide VE".
For Cloud Edition, give the permission for communication to ports listed in "Appendix A Port List" in the "Design Guide CE".

IP address checks: Check if the IP address displayed in the error message is correct and if necessary specify the correct IP address, and then perform the operation again.

LAN network checks: Check if the network cable is connected to the server target.

Perform the following corrective action:

When this message is displayed during deployment of a cloning image: Deployment of the cloning image has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67357

FJSVrcx:ERROR:67357:IO error. target=target detail=detail

Description

An IO error has occurred during communication.

Corrective Action

After checking if the destination server for communication has been started by referring to the following manuals, resolve the problem, and then perform the operation again.

Check the communication destination
Refer to the following:
- Refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide VE", and start the destination server for communication.
- Refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE", and start the destination server for communication.
However, when target is the name of external software, refer to the manual of the software and start the service of the external software.

Perform the following corrective action:

When this message is displayed during deployment of a cloning image
Deployment of the cloning image has been completed, but setting and post-processing of the host name and public LAN has failed. Refer to the corrective action of "Message number 67328".
When operating managers in clusters
There is a chance that the shared disk for managers is not mounted.
Mount the shared disk for managers on the node the operation was performed on and perform the operation again.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67358

FJSVrcx:ERROR:67358:internal error. target=target detail=detail

Description

An internal error has occurred.

Corrective Action

Collect troubleshooting information and contact Fujitsu technical staff.

67359

FJSVrcx:ERROR:67359:obj: VM host registration failed detail=detail

Description

Registration of the VM host obj failed, because an error has occurred in control of the VM host.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.
When detail is "VMGuest's name / host is invalid."

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "4" or "15"

For the requests from the admin server, the response from VM host timed out.
Check the operation status and network settings of the VM host.
There may be an error in the authentication information of the VM host.
Check the authentication information of the VM host.
There may be a mistake in the software requirements of the VM host.
Refer to "6.1.1 Software Requirements (Virtual Edition)" in the "Overview".
There may be an error in the settings of the VM host.
Check "9.2 Configuring Server Virtualization Software" in the "Design Guide VE".

When error_number is "16"

A VM host was not found. There are the following two possibilities:

Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

[Hyper-V]

There is a possibility that Hyper-V has not been installed or that role has not been enabled.
Check that Hyper-V has been installed and the role has been enabled.

When error_number is "101", "110", "111", "112", "114", or "116": Communication between the admin server and the VM host failed. Check the operating status and network settings of the admin server and the VM host.

When error_number is "113": Communication with the VM host is not possible using the login account information entered when registering the VM host.
Change the entered values (user name and password) for the login account information to the correct values.

When error_number is "100" or "115": The necessary authority may not have been granted in the VM host login account information that was registered.
Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host.

When error_number is "400"

Processing of a VM host remote command failed. There are the following possibilities:

The VM host is not running correctly
The network settings of the VM host are incorrect
Setup of the Global zone has not been performed
The resource pool service is disabled

If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When detail is "VMGuest's name / host is invalid.": Check if it is possible to use the management window of the server virtualization software to confirm the status of the VM guest on the VM host where the problem occurred.
If the status cannot be confirmed, check the storage configuration of the VM host, return it to a state in which it can be accessed and then perform server registration again.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Registration of the VM host obj failed, because an error has occurred in control of the VM host.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "4" or "15"

For the requests from the admin server, the response from VM host timed out.
Check the operation status and network settings of the VM host.
There may be an error in the authentication information of the VM host.
Check the authentication information of the VM host.
There may be a mistake in the software requirements of the VM host.
Refer to "6.1.2 Software Requirements (Cloud Edition)" in the "Overview".
There may be an error in the settings of the VM host.
Check "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".

When this type of error occurs during execution of DR, the error status in which an OS service has not operated correctly for a certain period may have continued, after starting a physical L-Server.
Start the target physical L-Server using Resource Orchestrator and check if the OS service is operating correctly.
If the OS service is operating correctly, execute DR again.

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "101", "110", "111", "112", "114", or "116": Communication between the admin server and the VM host failed. Check the operating status and network settings of the admin server and the VM host.
When this type of error occurs during execution of DR, the error status in which an OS service has not operated correctly for a certain period may have continued, after starting a physical L-Server.
Start the target physical L-Server using Resource Orchestrator and check if the OS service is operating correctly.
If the OS service is operating correctly, execute DR again.

When error_number is "113": Communication with the VM host is not possible using the login account information entered when registering the VM host.
Change the entered values (user name and password) for the login account information to the correct values.
When this type of error occurs during execution of DR, the error status in which an OS service has not operated correctly for a certain period may have continued, after starting a physical L-Server.
Start the target physical L-Server using Resource Orchestrator and check if the OS service is operating correctly.
If the OS service is operating correctly, execute DR again.

When error_number is "400"

Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
When detail contains "poolstat", check whether the resource pools service corresponding to the managed resource pool for Solaris Zones have been enabled.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

[Xen]
When registering an RHEL-Xen agent, registration of the agent may fail.
The parameters set for the following file in the VM host for registration may be incorrect:

/etc/xen/xend-config.sxp

Open the file and check that parameters are correct.

For details on the parameters, refer to the "Red Hat Enterprise Linux 5 Virtualization Guide".

Red Hat Enterprise Linux 5 Virtualization Guide

URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/index.html

Example

Check that the following parameter in the VM host, defining the minimum amount of memory to reserve, is described using the required format.

(dom0-min-mem Memory_capacity)

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67360

FJSVrcx:ERROR:67360:stopping spare server failed target=target detail=detail

Description

Stopping of the spare server target failed.
Take corrective action for the content displayed for detail.

"not supported HA type"
"not available VM Host"
"VMware maintenance mode, enter, vmerrno=error_number" or "VM maintenance mode, enter, vmerrno=error_number"
Take corrective actions based on error_number, and then perform the operation again.

Corrective Action

"not supported HA type": The server switchover method is not supported by the spare server of the VM host.
Specify another spare server as the destination of switching.

"not available VM Host"

The spare server cannot be used as the destination of server switchover.
Check that the status of the spare server is not something other than "normal" or "warning".
Check that the VM guest is not on the VM host. Check the status of communication between the admin server and the VM host, and the operating status and settings of the VM host.

[Citrix Xen]
When the spare server is a Citrix XenServer, check that the Citrix XenServer pool master has not been set as the spare server.

"VMware maintenance mode, enter, vmerrno=error_number" or "VM maintenance mode, enter, vmerrno=error_number"

When error_number is "15": For the requests from the admin server, the response from VM host timed out. Check the operation status and network settings of the VM host.

When error_number is "16"

A VM host was not found. There are the following two possibilities:

Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

[Hyper-V]

There is a possibility that Hyper-V has not been installed or that role has not been enabled.
Check that Hyper-V has been installed and the role has been enabled.

When error_number is "101", "110", "111", "112", "114", or "116": Communication between the admin server and the VM host failed. Check the operating status and network settings of the admin server and the VM host.

When error_number is "113"

Communication with the VM host is not possible using the login account information entered when registering the VM host. The login account information may have been changed after the VM host was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to the following:

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "100", "115", or "132"

The necessary authority may not have been granted in the VM host login account information that was registered.
Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host.
For details, refer to the following:

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "104", "105", "135", or "136": Processing of VM host tasks failed. Check the operation status and network settings of the VM host. When operation is not possible using VM management software, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When error_number is "130": The VM host has already been set into VM maintenance mode. Check that the spare server is not being operated by another administrator.

When error_number is "131" or "133": Setting the VM host into VM maintenance mode failed. Check the operation status and network settings of the VM host.

When error_number is "400": Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When error_number is "401"

[Xen] [Citrix Xen]
The spare server cannot be used as the destination of server switchover.

[Citrix Xen]
When the spare server is a Citrix XenServer, check that the Citrix XenServer pool master has not been set as the spare server.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Stopping of the spare server target failed.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
Take corrective actions based on error_number, and then perform the operation again.
- When error_number is "6", "7", "8", or "9"
- When error_number is "99"

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67363

FJSVrcx:ERROR:67363:obj:changing VM host login account information failed detail=detail

Description

Registration of the login account information of the VM host obj failed because an error occurred during communication with the VM host.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.
- When error_number is "4" or "15"
  For the requests from the admin server, the response from VM host timed out. Check the operation status and network settings of the VM host.
- When error_number is "16"
  A VM host was not found. There are the following two possibilities:
  - Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
  [Hyper-V]
  - There is a possibility that Hyper-V has not been installed or that role has not been enabled.
    Check that Hyper-V has been installed and the role has been enabled.
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM host failed. Check the operating status and network settings of the admin server and the VM host.
- When error_number is "113"
  Communication with the VM host is not possible using the login account information entered when registering the VM host. The login account information may have been changed after the VM host was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM host login account information that was changed.
  Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host.
- When error_number is "400"
  Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
  If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Registration of the login account information of the VM host obj failed because an error occurred during communication with the VM host.

Corrective Action

Take corrective action for the content displayed for detail.

When error_number is "6", "7", "8", or "9"
Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
When error_number is "99"
Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

67364

FJSVrcx:ERROR:67364:The last system image of a server in switchover state cannot be deleted.

Description

As a system image is necessary to perform failback when the server switchover method is backup and restore, it is not possible to delete all system images.

Corrective Action

Perform the operation again after performing failback or continuation.

67365

FJSVrcx:ERROR:67365:An invalid Windows activation setting was detected in the configuration file. target=target

Description

A problem was detected in the following license information file on target.

Installation_folder\Agent\scw\SeparateSetting\ipadj\activation.dat

Corrective Action

Check the following, resolve the cause of the problem, and execute the command again.
There is a license information file on target

The content of the license information file on target is correct

For details, refer to the following:

For Virtual Edition, refer to "17.2 Collecting" in the "User's Guide VE".
For Cloud Edition, refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

67366

FJSVrcx:ERROR:67366:Registry access failed. detail

Description

Accessing the registry failed.

Corrective Action

Check the following, resolve the cause of the problem, and execute the command again.

Setup of the server might not be complete.
Check if an error was displayed during agent setup.
When an error was displayed, resolve the problem and perform agent setup again.
For details on setup, refer to the following:
- Refer to "2.2 Agent Installation" in the "Setup Guide VE".
- Refer to "2.2 Agent Installation" in the "Setup Guide CE".

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67367

FJSVrcx:ERROR:67367:command failed to return valid result. command=command, code=code

Description

command returned the result code and terminated abnormally.

Corrective Action

Collect troubleshooting information and contact Fujitsu technical staff.

67368

FJSVrcx:ERROR:67368:obj:entering VM host maintenance mode failed. detail=detail

Description

Setting the VM host obj into VM maintenance mode failed.
If this message and "Message number 67369" are both displayed between the start and finish of backup or restoration of VM hosts, or server switchover or failback using backup or restore, then no action is necessary.
Take corrective action for the content displayed for detail.

When detail is "timeout occurred"
When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "timeout occurred": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "16": A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

When error_number is "101", "110", "111", "112", "114", "116", "132", or "133": Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "104"

When the target VM host is using functions of VM management software or other coordinated software, check the configuration and operating status of the coordinated software. When using functions of VM management software, also check the registration status of the VM management software on the Resource Orchestrator admin server.

[Hyper-V]
If Key Storage Drive or encryption has been enabled for the VM guest, migration of the VM guest during setting of VM maintenance mode may fail.
Confirm the Key Storage Drive and encryption settings of the VM guests on the target VM host.

When error_number is "113": Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".

When error_number is "100" or "115"

The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host or VM management software.
For details, refer to the following:

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "104", "105", "131", "135", or "136": Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
When the target VM host is using functions of VM management software or other coordinated software, check the configuration and operating status of the coordinated software. When using functions of VM management software, also check the registration status of the VM management software on the Resource Orchestrator admin server.

When error_number is "130"

VM maintenance mode has already been set. Check the status of VM maintenance mode using the VM management software. If VM maintenance mode has not been set, perform the operation again.

[Citrix Xen]
When the VM host is a Citrix XenServer and settings to migrate VM guests have not been configured, check that there are no VM guests operating.

When error_number is "400": Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When error_number is "401": [Citrix Xen]
Setting and release of VM maintenance mode for Citrix XenServer pool masters is not supported.
When the VM host is a Citrix XenServer, check that the VM host is not configured as the pool master.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "101", "110", "111", "112", "114", "116", "132", or "133": Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "104"

[Hyper-V]

If Key Storage Drive or encryption has been enabled for the VM guest, migration of the VM guest during setting of VM maintenance mode may fail. Confirm the Key Storage Drive and encryption settings of the VM guests on the target VM host.

When error_number is "113": Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "534": Check if the target VM host name is correct.

When error_number is "535": Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact your network administrator.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

67369

FJSVrcx:ERROR:67369:obj:exiting VM host maintenance mode failed. detail=detail

Description

Releasing the VM host obj from VM maintenance mode failed.
If this message and "Message number 67368" are both displayed between the start and finish of backup or restoration of VM hosts, or server switchover or failback using backup or restore, then no action is necessary.
Take corrective action for the content displayed for detail.

When detail is "timeout occurred"
When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
This message may be displayed at the end of backup or restoration of VM hosts, or server switchover or failback using backup or restore. In such cases, check the status of VM maintenance mode using the VM management software.
When VM maintenance mode has not been released, release VM maintenance mode.

Corrective Action

When detail is "timeout occurred": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
This message may be displayed at the end of backup or restoration of VM hosts, or server switchover or failback using backup or restore. In such cases, check the status of VM maintenance mode using the VM management software.
When VM maintenance mode has not been released, release VM maintenance mode.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "16": A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

When error_number is "101", "110", "111", "112", "114", "116", "132", or "133": Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "113"

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "100" or "115"

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "104", "105", "131", "135", or "136": Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.

When error_number is "130": VM maintenance mode has already been released. Check the status of VM maintenance mode using the VM management software. If VM maintenance mode has not been released, perform the operation again.

When error_number is "400": Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When error_number is "401": [Citrix Xen]
Setting and release of VM maintenance mode for Citrix XenServer pool masters is not supported.
When the VM host is a Citrix XenServer, check that the VM host is not configured as the pool master.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
This message may be displayed at the end of backup or restoration of VM hosts, or server switchover or failback using backup or restore. In such cases, check the status of VM maintenance mode using the VM management software.
When VM maintenance mode has not been released, release VM maintenance mode.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "534": Check if the target VM host name is correct.

When error_number is "535": Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact your network administrator.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

67370

FJSVrcx:ERROR:67370:target:executing interface failed in external_software. code=code, message=message

Description

Failed to execute the command interface with the external software external_software.

The name of the resource that is that target of the operation is displayed in target.
The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.
One of the following problems may have occurred during the operation.
Occurred Problems
- System failure, or reboot of the admin server or manager
- Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67371

FJSVrcx:ERROR:67371:obj:does not have a CD/DVD drive.

[Cloud Edition]

Description

As the VM guest obj does not have a CD/DVD drive, connection of the VM guest tool is not possible.

Corrective Action

Add a CD/DVD drive using the VM management software.

67372

FJSVrcx:ERROR:67372:obj:failed to connect to VM guest tool. detail=detail

[Cloud Edition]

Description

Connection of the VM guest obj to the VM guest tool failed.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  As the manager was restarted during processing, the process has failed. Check that the manager has started properly, and then perform the operation again.
  For details on how to check the running state of the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "16"
  A VM host was not found. On the management software tree of the ROR console, select the VM management software used to manage the VM host, and perform [Update].
  After that, display the server resource tree, and check whether the VM guest has been moved to another VM host.
- When error_number is "17"
  A VM guest was not found. Check the following:
  - On the management software tree of the ROR console, select the VM management software used to manage the VM host, and perform [Update].
    After that, display the server resource tree, and check whether the VM guest has been deleted.
  - Check whether the VM guest is set to be moved when its power status is changed using the VM management console.
- When error_number is "101", "110", "111", "112", "114", "116", or "473"
  Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "113"
  Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "100", "115", or "471"
  The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
  Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "104", "105", "135", or "136"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
  Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
- When error_number is "472"
  Due to the occurrence of an error on the VM host or VM management software, connection with the VM guest tool was not possible.
  Check the cause of the error in the VM host/VM management software, and resolve the error.
If detail is "timeout occurred"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67373

FJSVrcx:ERROR:67373:target:VM guest creation failed in external_software. code=code, message=message

Description

Failed to create the VM guest target with the external software external_software.

The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.

[Solaris Zones]

Check if the virtual package corresponding to the specified virtual image resource is registered in BladeLogic.
When a virtual package has not been registered, register it in BladeLogic, and then install it in Resource Orchestrator.
For details, refer to "8.7.3 Registering Resources in Resource Pools" in the "Setup Guide CE".
Check that a network interface used by another zone has not been specified on the VM host.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
Check the storage environment and the mount settings.
For details, refer to "E.6.3 Storage Preparations" in the "Design Guide CE".
Check that no files have been created on the disk resource to use.
If there are any files, delete them, and then perform the operation again.
Check the corrective action for the following situation, described in "Message number 62597".
"When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain."

[OVM for SPARC]
When the created guest domain remains, delete it using the following procedure.

Deletion procedure for guest domains

For the VM host for which creation of the guest domain failed, perform the following procedure.

Check that the guest domain has stopped.
Execute the following commands and check that the "STATE" of the guest domain is "inactive".
# ldm list-domain domain_name <RETURN>
When the "STATE" of a guest domain is not "inactive", stop the guest domain using the following procedures, based on the value of "STATE".
- When the "STATE" of the guest domain is "active"
  # ldm stop-domain -f domain_name <RETURN>
  # ldm unbind-domain domain_name <RETURN>
- When the "STATE" of the guest domain is "bound"
  # ldm unbind-domain domain_name <RETURN>
Delete the guest domain.
Execute the following command and delete the guest domain.
# ldm remove-domain domain_name <RETURN>

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67374

FJSVrcx:ERROR:67374:target:OS installation to VM guest failed in external_software. code=code, message=message

Description

Failed to install an OS on the VM guest target with the external software external_software.

The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.

[OVM for SPARC]

Check whether the system package corresponding to the specified virtual image resource is registered with BladeLogic.
When the system package is not registered, register it with BladeLogic and then load it into Resource Orchestrator.
The installation server may not have started.
Check whether the installation server has started.
Moreover, if the installation server fails during creation of an L-Server, and the job of BladeLogic is canceled according to the procedure in "Troubleshooting", this message is output.
This error message is output when the following conditions are met.
- When multiple L-Servers with a Solaris 11 image specified are created simultaneously
- - "true" is not specified in the "Operation mode definition file for when simultaneously creating multiple L-Servers with a Solaris 11 image specified" in "8.8.1 Creating Definition Files" in the "Setup Guide CE".
When performing the operation again, ensure that multiple L-Servers are not created simultaneously.

When the created guest domain is not deleted, delete it referring to "Deletion procedure for guest domains" given in "Message number 67373".
In addition, the provisioning job for a guest domain may be performed using BladeLogic Server Automation.
Therefore, check the run state of jobs referring to the "Procedure for checking the run state of a job in BladeLogic Server Automation" in "Message number 67390".

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67375

FJSVrcx:ERROR:67375:target:VM guest modification failed in external_software. code=code, message=message

Description

Failed to modify configurations on the VM guest target with the external software external_software.

The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.
Check whether the execution condition of operation in server virtualization software is fulfilled.
Refer to the manual of the server virtualization software or "Chapter 8 Configuration when Creating Virtual L-Servers" in the "Setup Guide CE" for execution conditions of operations.

[Solaris Zones]

Check that the configurations have not been modified while an L-Server has been operating.
For the following item, modify the configuration after stopping an L-Server.
- L-Server Name

[OVM for SPARC]
Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the ldmd service of the VM host is online.
When modification of the CPU or memory resources fails, check whether sufficient CPU and memory resources have been secured for the VM host
When addition or deletion of a disk goes wrong, check the following.
- Check that the specified disk exists, and is registered with the virtual disk service
- Check whether the specified disk is used by other VM guests
- Check whether the virtual disk named vdiskN exists
  The disk number specified at the time of disk extension is shown for N.
  When the above-mentioned virtual disk name exists, change a disk name using the following procedure.
  The procedure for changing a disk name
  Perform the following procedure on the VM host for which disk extension failed.
  1. Stop the guest domain
    Execute the following commands and stop the guest domain.
    # ldm stop-domain domain_name <RETURN>
    # ldm unbind-domain domain_name <RETURN>
  2. Delete the virtual disk which has had its name changed, from the guest domain
    Execute the following commands and delete the virtual disk that has had its name changed, from the guest domain.
    # ldm remove-vdisk vdisk_name domain_name <RETURN>
  3. Add the virtual disk deleted in step 2 to a guest domain using a different name.
    Execute the following commands and add the virtual disk using a different name.
    # ldm add-vdisk vdisk_name volume_name@service_name domain_name <RETURN>
When this error message is output during creation of an L-Server, the configuration change after installing the OS in a guest domain has failed.
Check the status of the VM host and whether the ldmd service is operating.
In addition, when the created guest domain is not deleted, delete it referring to "Deletion procedure for guest domains" given in "Message number 67373".
When this error message is output during VM guest or L-Server migration
The process which changes the value of "auto-boot?" before and after migration failed.
Check the following corrective action and remove the cause of the problem.
After that, perform the "Procedure that restores the preset value of "auto-boot?"" and restore. After restoration is complete, perform the operation again.
- Check the status of the VM host and whether the ldmd service is operating.
- The following may have occurred during migration.
  Occurred Problems
  - System failure or rebooting of an admin server
  - System failure or reboot of a manager
  - Server switchover in which managers are operating using the HA function of cluster software or server virtualization software
  Procedure that restores the preset value of "auto-boot?"
  Return the value of "auto-boot?" set for the guest domain to the original value using the following procedure.
  1. Check the preset value of "auto-boot?".
    Execute the following command on the VM host on which the guest domain exists, and check the preset value of "auto-boot?".
    # ldm list-variable auto-boot? domain_name <RETURN>
    When the preset values of "auto-boot?" differs from when it was migrated, perform step 2 and change the preset value.
    In addition, after creating an L-Server using this product, when the value of "auto-boot?" is not changed, the following values are set for "auto-boot?".
    When an L-Server is created without an image specified
    Since "false" is set for "auto-boot?", the value of "auto-boot?" is not changed when migration is performed.
    Therefore, it is not the target of this restoration procedure.
    When an L-Server was created with an image specified
    As "true" is set for "auto-boot?", the value of "auto-boot?" is changed when migration is performed.
  2. Change the preset value of "auto-boot?".
    Execute the following command and change the preset value of "auto-boot?".
    # ldm set-variable auto-boot?=true|false guest_domain_name <RETURN>
  3. Save configuration information.
    Save configuration information referring to the restoration procedure given in "Message number 41127.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67376

FJSVrcx:ERROR:67376:target: VM guest deletion failed in external_software. code=code, message=message

Description

Failed to delete the VM guest target with the external software external_software.

The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.

[Solaris Zones]

Check the storage environment and the mount settings.
For details, refer to "E.6.3 Storage Preparations" in the "Design Guide CE".
Check if there is a "lost+found" file in the zone path of the VM guest that is the target of deletion.
If there is no file, execute the following procedure, and then perform the operation again.
1. On VM host, delete the non-global zone which is the target of deletion.
2. Unmount the disk mounted on the zone path of the deleted non-global zone.
3. Perform step 2 to create a file system on the unmounted disk again.
Make sure that the VM guest has not already been deleted.
If it has already been deleted, check that the VM guest is no longer displayed on the server tree on the ROR console, and then perform the operation again.
Make sure that no VM guests are operating.
If there are VM guests operating, stop them and then perform the operation again.
When one of the following problems occurs during deletion of an L-Server, deletion fails and VM guests being deleted on server virtualization software may remain.
Perform the operation again, and then check whether the VM guests still remain. If they do remain, delete them.
Occurred Problems
- System failure, or reboot of the admin server or manager
- Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

[OVM for SPARC]

Make sure that the VM guest has not already been deleted.
If it has already been deleted, check that the VM guest is no longer displayed on the server tree on the ROR console, and then perform the operation again.
Make sure that no VM guests are operating.
If there are VM guests operating, stop them and then perform the operation again.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67377

FJSVrcx:ERROR:67377:target:VM guest migration failed in external_software. code=code, message=message

Description

Failed to migrate the VM guest target with the external software external_software.
The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.
For VM guests on Solaris Zones, perform the "Recovery Procedure" before performing the operation again.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
Check that the BladeLogic service is running on the VM host or the VM host using BladeLogic.
Check that communication with the VM host is possible.
There is a chance the VM guest does not exist, or its power status has been changed.
Check the status of the VM guest.
Check whether the execution condition of operation in server virtualization software is fulfilled.
Refer to the manual of the server virtualization software or "Chapter 8 Configuration when Creating Virtual L-Servers" in the "Setup Guide CE" for execution conditions of operations.

[Solaris Zones]

Check the following corrective actions, resolve the cause, perform the recovery procedure, and then perform the operation again.

Check that a network interface that does not exist on the VM host has not been specified.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
Check that a network interface used by another zone has not been specified on the VM host.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
Check the storage environment and the mount settings.
For details, refer to "E.6.3 Storage Preparations" in the "Design Guide CE".
There is a chance that one of the following problems may have occurred during L-Server migration.
Occurred Problems
- System failure, or reboot of the admin server or manager
- Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

Recovery Procedure

Check the error status
- Check on the migration target VM host
  1. Execute the following command to check the status of the non-global zone.
    # zoneadm list -vc <RETURN>
    When the status of the non-global zone is "configured", perform the procedure from step a of "Recovery on the migration target VM host" in "2. Recovery".
    When the status of the non-global zone is "installed", recovery is not necessary.
    When the non-global zone is not displayed, proceed to the next step.
  2. Execute the following command, and check that the disk used for the non-global zone is mounted.
    # mount <RETURN>
    If it has not been mounted, perform the procedure in "Check on the migration source VM host".
    If it has been mounted, perform the procedure from step c of "Recovery on the migration target VM host" in "2. Recovery".
- Check on the migration source VM host
  1. Execute the following command, and check that the disk used for the non-global zone is mounted.
    # mount <RETURN>
    If it has not been mounted, perform the procedure from step a of "Recovery on the migration source VM host" in "2. Recovery".
    If it has been mounted, proceed to the next step.
  2. Execute the following command to check the status of the non-global zone.
    # zoneadm list -vc <RETURN>
    When the status of the non-global zone is "configured", perform the procedure from step e. of "Recovery on the migration source VM host" in "2. Recovery".
    When the status of the non-global zone is "installed", recovery is not necessary.
    When the non-global zone is not displayed, perform the procedure from step c of "Recovery on the migration source VM host" in "2. Recovery".
Recovery
- Recovery on the migration target VM host
  1. Execute the following command to delete the non-global zone.
    # zonecfg -z zonename delete <RETURN>
  2. Execute the following command to check if the non-global zone is displayed.
    # zoneadm list -vc <RETURN>
  3. Execute the following command and unmount the disk used by the non-global zone.
    # umount zonepath <RETURN>
  4. Execute the following command, and check that the disk used for the non-global zone is not mounted.
    # mount <RETURN>
- Recovery on the migration source VM host
  1. Execute the following command to mount the physical disk.
    # mount zonepath <RETURN>
  2. Execute the following command, and check that the disk used for the non-global zone is mounted.
    # mount <RETURN>
  3. Execute the following command to create the non-global zone.
    # zonecfg -z zonename create -a zonepath <RETURN>
  4. Execute the following command and check that the status of the created non-global zone is "configured".
    # zoneadm list -vc <RETURN>
  5. Execute the following command to add the non-global zone. Specify the -u option if necessary.
    # zoneadm -z zonename attach <RETURN>
  6. Execute the following command and check that the status of the added non-global zone is "installed".
    # zoneadm list -vc <RETURN>

[OVM for SPARC]
Resolve the problem referring to the details displayed for message, and then perform the operation again.
Also, when the "auto-boot?" change function is enabled when migration is performed, check whether the value of "auto-boot?" set for the guest domain has reverted to the value from before migration.
When the preset value of "auto-boot?" differs from the value before migration execution, perform the "Procedure that restores the preset value of "auto-boot?"" of "Message number 67375", and revert the value of "auto-boot?".

Check whether sufficient CPU and memory resources have been secured on the destination VM host.
Check whether sufficient ports have been secured on the VM host that is the migration destination, for console connection.
Check that there is no VM guest with the same name on the VM host that is the migration destination.
Check the condition of the VM host and VM guest.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67378

FJSVrcx:ERROR:67378:target:failed to obtain information from external_software. code=code, message=message

Description

Failed to obtain information from the external software external_software.

The registration name of the external software is displayed for target.
The value returned from the external software is displayed in code.
The error message notified by the external software is displayed in message.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
Check that no mistakes were made in the preparation of the managed server.
For details, refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
One of the following problems may have occurred during the operation.
Occurred Problems
- System failure, or reboot of the admin server or manager
- Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67379

FJSVrcx:ERROR:67379:target:updating configuration failed in external_software. code=code, message=message

Description

Failed to upgrade the configuration information with the external software external_software.

Corrective Action

Resolve the problem referring to the details displayed for message, and then perform the operation again.

Check that the BladeLogic service is running on the server that BladeLogic is operating on.
Check that communication with the server that BladeLogic is operating on is possible.
One of the following problems may have occurred during the operation.
Occurred Problems
- System failure, or reboot of the admin server or manager
- Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.

67380

FJSVrcx:ERROR:67380:obj:VM management software registration failed. detail=detail

Description

Registration of the VM management software obj failed, because an error has occurred in control of the VM management software.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "4" or "15"
  For the requests from the admin server, the response from VM management software timed out. Check the operating status and network settings of the VM management software.
- When error_number is "16"
  VM management software was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM management software has been deleted.
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM management software failed. Check the operating status and network settings of the admin server and the VM management software.
- When error_number is "113"
  Communication with the VM management software is not possible using the login account information of the specified VM management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM management software login account information that was specified.
  Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM management software.
When detail is "ip address:invalid format / name:invalid format / product name:invalid format."
The value entered for IP address/VM management software name/VM management software type cannot be used. Change the value to a valid one.
When detail is "product:already registered."
The specified VM management software is already registered.
When detail is "user name:invalid format / password:invalid format."
The values entered for login account information (user name and password) cannot be used. Change the login account information to the correct information.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Registration of the VM management software obj failed, because an error has occurred in control of the VM management software.

Corrective Action

Take corrective action for the content displayed for detail.

When error_number is "6", "7", "8", or "9"
Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
When error_number is "99"
Due to temporary inconsistencies in the information held by VM host/ VM management software resulting from multiple operations, obtaining of information from VM host/ VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

67381

FJSVrcx:ERROR:67381:obj:changing VM management software information failed. detail=detail

[Virtual Edition]

Description

Changing settings of the VM management software obj failed, because an error has occurred in control of the VM management software.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "4" or "15"
  For the requests from the admin server, the response from VM management software timed out. Check the operating status and network settings of the VM management software.
- When error_number is "16"
  VM management software was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM management software has been deleted.
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM management software failed. Check the operating status and network settings of the admin server and the VM management software.
- When error_number is "113"
  Communication with the VM management software is not possible using the login account information of the specified VM management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM management software login account information that was specified.
  Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM management software.
When detail is "ip address:invalid format / name:invalid format / product name:invalid format."
The value entered for IP address/VM management software name/VM management software type cannot be used. Change the value to a valid one.
When detail is "product:already registered."
The specified VM management software is already registered.
When detail is "user name:invalid format / password:invalid format."
The values entered for login account information (user name and password) cannot be used. Change the login account information to the correct information.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Changing settings of the VM management software obj failed, because an error has occurred in control of the VM management software.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "4" or "15"
  For the requests from the admin server, the response from VM management software timed out. Check the operating status and network settings of the VM management software.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "16"
  VM management software was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM management software has been deleted.
- When error_number is "99"
  Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
- When error_number is "101", "110", "111", "112", "114", or "116"
  Communication between the admin server and the VM management software failed. Check the operating status and network settings of the admin server and the VM management software.
- When error_number is "113"
  Communication with the VM management software is not possible using the login account information of the specified VM management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "100" or "115"
  The necessary authority may not have been granted in the VM management software login account information that was specified.
  Check the granted authority using the VM management software. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM management software.
When detail is "ip address:invalid format / name:invalid format / product name:invalid format."
The value entered for IP address/VM management software name/VM management software type cannot be used. Change the value to a valid one.
When detail is "product:already registered."
The specified VM management software is already registered.
When detail is "user name:invalid format / password:invalid format."
The values entered for login account information (user name and password) cannot be used. Change the login account information to the correct information.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67382

FJSVrcx:ERROR:67382:obj:external_software registration failed. detail=detail

[Cloud Edition]

Description

Registration of external_software obj failed, because an error has occurred in control of external_software.

Corrective Action

Take corrective action for the content displayed for detail.

"name: invalid format."
The value entered for the management software name cannot be used. Change the value to a valid one.
"product: already registered."
The specified external_software cannot be newly registered, as it has already been registered.

67383

FJSVrcx:ERROR:67383:obj:VDI management software registration failed. detail=detail

[Cloud Edition]

Description

Registration of the VDI management software obj failed, because an error has occurred in control of the VDI management software.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VDI management software from IP_address. Take corrective action based on error_number.
- When error_number is "101"
  Communication between the admin server and the VDI management software failed. Check the operating status and network settings of the admin server and the VDI management software.
- When error_number is "104"
  The VMware scripts are not located in the VDI management server. Check if the file configuration is correct, and perform the operation again.
  For details, refer to "K.1.2 Preparations for Servers" in the "Design Guide CE".
- When error_number is "113"
  Communication with the VDI management software is not possible using the login account information of the specified VDI management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "548"
  Calling of the PowerShell module of Active Directory from the VDI management server has failed.
  Check if the Active Directory module of Windows Powershell is installed on the VDI management server.
- When error_number is "860"
  Connection with the VMware Horizon View service failed. Check if the VMware Horizon View service of the VDI management server has been started.
"name: invalid format."
The value entered for the management software name is invalid. Change the value to a valid one.
"ip address:invalid format"
The value entered for the IP address is invalid. Change the value to a valid one.
"product name:invalid format"
The value entered for the management software type is invalid. Change the value to a valid one.
"user name:invalid format"
The value entered for the user name is invalid. Change the value to a valid one.
"password:invalid format"
The value entered for the password is invalid. Change the value to a valid one.
"connect info:invalid format"
The value entered for the connection information is invalid. Change the value to a valid one.
"VM management software:invalid vm type"
The specified type of VM management software is not linked to the VDI management software. Change it to another VM management software.
"VM management software:invalid format"
The specification of VM management software is invalid. Specify one or more VM management software.
"VM management software:not found"
The specified VM management software is not registered with Resource Orchestrator. Register the specified VM management software with Resource Orchestrator.
"VM management software:already registered"
The specified VM management software is linked to other VDI management software. Specify other VM management software.
"product:already registered"
The same type of VDI management software with the same IP address is already registered. Check the VDI management software registered with Resource Orchestrator.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67384

FJSVrcx:ERROR:67384:obj: changing of VDI management software information failed. detail=detail

[Cloud Edition]

Description

Changing of the settings of the VDI management software obj failed, because an error has occurred in control of the VDI management software.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VDI management software from IP_address. Take corrective action based on error_number.
- When error_number is "101"
  Communication between the admin server and the VDI management software failed. Check the operating status and network settings of the admin server and the VDI management software.
- When error_number is "104"
  The VMware scripts are not located in the VDI management server. Check if the file configuration is correct, and perform the operation again.
  For details, refer to "K.1.2 Preparations for Servers" in the "Design Guide CE".
- When error_number is "113"
  Communication with the VDI management software is not possible using the login account information of the specified VDI management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "548"
  Calling of the PowerShell module of Active Directory from the VDI management server has failed.
  Check if the Active Directory module of Windows Powershell is installed on the VDI management server.
- When error_number is "860"
  Connection with the VMware Horizon View service failed. Check if the VMware Horizon View service of the VDI management server has been started.
"ip address:invalid format"
The value entered for the IP address is invalid. Change the value to a valid one.
"user name:invalid format"
The value entered for the user name is invalid. Change the value to a valid one.
"password:invalid format"
The value entered for the password is invalid. Change the value to a valid one.
"connect info:invalid format"
The value entered for the connection information is invalid. Change the value to a valid one.
"VM management software:invalid vm type"
The specified type of VM management software is not linked to the VDI management software. Change it to another VM management software.
"VM management software:invalid format"
The specification of VM management software is invalid. Specify one or more VM management software.
"VM management software:not found"
The specified VM management software is not registered with Resource Orchestrator. Register the specified VM management software with Resource Orchestrator.
"VM management software:already registered"
The specified VM management software is linked to other VDI management software. Specify other VM management software.
"product:already registered"
The same type of VDI management software with the same IP address is already registered. Check the VDI management software registered with Resource Orchestrator.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67385

FJSVrcx:ERROR:67385:migrating VM guest failed. vmguest migrate from vmhost1 to vmhost2. detail=detail

Description

Migration of the VM guest vmguest failed. The server vmhost1 is the migration source and the server vmhost2 is the migration target.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "16": A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

When error_number is "17": A VM guest was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM guest has been deleted.
Use the VM management console and check that the VM guest is not configured to move when its power status changes.

When error_number is "101", "110", "111", "112", "114", "116", "153", or "162": Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "113"

For Virtual Edition, refer to "9.1.7 Changing VM Host Login Account Information" or "9.6 Changing VM Management Software Settings" in the "User's Guide VE".
For Cloud Edition, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "100" or "115": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host or VM management software.
For details, refer to "9.1.7 Changing VM Host Login Account Information" or "9.6 Changing VM Management Software Settings" in the "User's Guide VE".

When error_number is "104", "105", "135", or "136"

Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using the VM management console, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
Migration of a VM guest that is in a server other than the cluster configured in VM management software may have been attempted. Migrate the VM guest from VM management software.
When operation is not possible using the VM management console, there is a problem with the VM host or VM management software. Perform the operation after solving problems related to VM hosts and VM management software.

[OVM for x86 3.3 or later]
When a VM host with [Inbound Migration Locked] configured is selected as the destination host of the L-Server, L-Server migration will fail.
After performing one of the following corrective actions, perform the operation again.

Configure another VM host as the destination host of the L-Server
Release the [Inbound Migration Locked] configured on the VM host

When error_number is "150" or "151"

An error was detected during pre-migration checks. Migration between the servers cannot be performed. Check the following configurations, operating statuses, and registration statuses with the admin server of Resource Orchestrator.

VM guest
Migration source VM host
Migration target VM host

Also, when the server virtualization software requires VM management software for migration, check the following:

That VM management software has been registered on the admin server
That the registered VM management software is managing the VM hosts that are the migration source and migration target

If there are no problems with the operating status, registration status, or management status, check the cause of the error on the VM host or VM management software and resolve it.

When error_number is "155", "157", "158", "159", "160", or "310": An error occurred during control of migration. Check the cause of the error on the VM host or VM management software and correct it.

When error_number is "152", "161", or "222": An error occurred during migration. Check that there are no errors in the values specified when executing migration. If there are no errors in the specified values, check the cause of the error on the VM host or VM management software and correct it.

When error_number is "216": There are no VM hosts that can be used for migration. Check the operating status of the VM host.

When error_number is "156", "300", or "316": An error occurred during control of migration. Check the operating status and network settings of the VM host or VM management software. If there is no problem with the operating status or network settings, check the cause of the error on the VM host or VM management software and resolve it.

When error_number is "164": The migration target VM host is not suitable. Specify a VM host other than the migration source.

When error_number is "400"

Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

[KVM]
The conditions for migration may not be satisfied.
For details on the configuration conditions to use migration, refer to "VM Guest Migration" in "9.2.2 Functional Differences between Products" in the "Design Guide VE".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

[Cloud Edition]

Description

Migration of the VM guest vmguest failed. The server vmhost1 is the migration source and the server vmhost2 is the migration target.
Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.

Corrective Action

When detail is "(Message,vmerrno=error_number,ip=IP_address)"

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "17"

A VM guest was not found. Check the following:

Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted.
Check whether the VM guest is set to be moved when its power status is changed using the VM management console.

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "100" or "115": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If authority has not been granted, change the login account information (user name and password) to that of a user with administrator authority for the VM host or VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "104", "152", or "551"

Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.

[Hyper-V]
If Key Storage Drive or encryption has been enabled for the VM guest, migration may fail.
Confirm the Key Storage Drive and encryption settings of the target VM guest.

When error_number is "150" or "151"

VM guest
Migration source VM host
Migration target VM host

Also, when the server virtualization software requires VM management software for migration, check the following:

That VM management software has been registered on the admin server
That the registered VM management software is managing the VM hosts that are the migration source and migration target

If there are no problems with the operating status, registration status, or management status, check the cause of the error on the VM host or VM management software and resolve it.
When error_number is "150", check the following and "When error_number is "150" or "164"".

[VMware]
After starting an L-Server operating on a VMware VM host, when migration between servers is performed before completion of starting of the OS, migration fails.
Perform the operation again after starting of the L-Server's OS is complete.

Check the physical CPU performance of the VM host on which the VM guest is operating using the ROR console and the VM management window.
When CPU performance values for the VM host registered in a VM pool and for the VM host registered in VM management software differ, refer to "3.10 Migration of a Virtual L-Server between Servers or Modification of Specifications Fails." in "Troubleshooting".

When error_number is "150" or "164"

The VM host specified as the destination does not meet the requirements for the migration destination of VM guests. Specify a VM host that meets the requirements for the destination.
When error_number is "164", also check the following.

The migration target VM host is not suitable. Specify a VM host other than the migration source.

When using an environment with overcommit enabled, also refer to the advisory notes in "17.7 Migration between VM Hosts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on overcommit, refer to the "Overcommit" section of the server virtualization software to use in "Chapter 8 Configuration when Creating Virtual L-Servers" in the "Setup Guide CE".

When error_number is "155", "157", "158", "159", "160", or "310": An error occurred during control of migration. Check the cause of the error on the VM host or VM management software and correct it.

When error_number is "216": There are no VM hosts that can be used for migration. Check the operating status of the VM host.

When error_number is "222"

An error occurred during migration. Check whether the value specified when migration between servers was performed was correct. If the specified value was correct, check the cause of the error on the VM host or VM managed products, and remove the cause.

[OVM for SPARC]
When the "auto-boot?" change function was enabled at the time of migration, preservation of the configuration information from before migration may have failed.
The prerequisites for saving configuration information may not have been fulfilled.
Check that this product can save configuration information referring to the corrective action given in "Message number 41127".
Also, when the value of "auto-boot?" set as the guest domain differs from the value before migration, perform the "Procedure that restores the preset value of "auto-boot?"" of "Message number 67375", and revert the value of "auto-boot?".

When error_number is "400"

[KVM]

The conditions for migration may not be satisfied.
For details on the configuration conditions to use migration, refer to "VM Guest Migration" in "9.2.2 Functional Differences between Products" in the "Design Guide VE".

When detail is "Temporary failure in name resolution" or "Cannot recv data: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). : Connection reset by peer": Check the host configuration for the live migration.
For details, refer to "Configuration for L-Server Live Migration" in "8.6.9 Advisory Notes for RHEL-KVM Usage" in the "Setup Guide CE".
When performing VM live migration using the command provided with Red Hat Enterprise Linux 6 on a VM host, make sure to specify both --undefinesource and --persistent, which are the virsh migrate command options.
When performing live migration using Virtual Machine Manager, confirm that the guest OS on the source host has been moved to the destination host, stop the guest OS on the destination, and then start the guest OS on the destination.
When not performing the procedure above, the virtual L-Server may not be managed properly in Resource Orchestrator.

When "Error: libvirt-0.9.4-23.el6_2.4 or later is needed." is displayed in detail: This means the version of libvirt package installed on VM host in the migration destination is older than 0.9.4-23.el6_2.4.
As there are non-compatible functions that can lead to security vulnerabilities, upgrade the libvirt package to 0.9.4-23.el6_2.4 or a later version.

When "Unmatch VM-host release." is displayed in detail: The kernel versions of the VM hosts are different.
If the kernel versions, including the minor release numbers are different, live migration cannot be performed.
Check the kernel version of the VM host using the uname or related commands.
For details on the configuration conditions for live migration, refer to "Prerequisites for L-Server Migration" in "E.5.2 Preparations for Servers" in the "Design Guide CE".

When "Unmatch VM-host machine." is displayed in detail: The CPU architectures of the VM hosts are different. Migrations are performed either between Intel64 or x86 servers. Check the CPU architectures of VM hosts using the /proc/cpuinfo information.
For details on the configuration conditions for live migration, refer to "Prerequisites for L-Server Migration" in "E.5.2 Preparations for Servers" in the "Design Guide CE".

When "Unmatch VM-host model name." is displayed in detail: The CPU model names of the VM hosts are different. If the CPU model names are different, live migration cannot be performed. Check the CPU model name of VM hosts using the /proc/cpuinfo information.
For details on the configuration conditions for live migration, refer to "Prerequisites for L-Server Migration" in "E.5.2 Preparations for Servers" in the "Design Guide CE".

When "Not exist disk Disk_name in dest host" is displayed in detail: The disk with the name Disk_name cannot be accessed from the destination VM host.
Review the storage environment configuration.
For details on the configuration conditions for live migration, refer to "Prerequisites for L-Server Migration" in "E.5.2 Preparations for Servers" in the "Design Guide CE".

When "Not exist bridge Virtual_bridge_name in dest host" is displayed in detail: The virtual bridge with the name Virtual_bridge_name has not been defined for the destination VM host.
Review the network environment configuration.
For details on the configuration conditions for live migration, refer to "Prerequisites for L-Server Migration" in "E.5.2 Preparations for Servers" in the "Design Guide CE".

When a message including "Recover it manually." is displayed for detail.

The processing of a snapshot for a migration operation has failed.
The version numbers of snapshots retained in a virtual L-Server and a VM guest are different.
Define the snapshot for a VM guest again and restore it manually.

- If "Import snapshot failed. Recover it manually." is displayed for detail when performing live migration or cold migration
Redefinition of a VM guest snapshot on the migration source VM host has failed.

- If "Migration succeeded but import snapshot failed. Recover it manually." is displayed for detail when performing live migration or cold migration
Redefinition of a VM guest snapshot on the migration target VM host has failed.

- If "Import snapshot failed. Recover it manually." is displayed for detail when performing forced migration
Redefinition of a VM guest snapshot on the migration target VM host has failed.

Use the following procedure to perform recovery.

1. View the snapshot information retained in the VM guest.
For details on how to view snapshot information, refer to the following in the "Virtualization Administration Guide".
- 14.13. Managing snapshots

URL:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html

The format of the snapshot name is as follows:

RCX_{VM_guest_name}@version_number

Example

[root@KVM root]# virsh snapshot-list vm111-668 <RETURN>

Name                 Creation Time             State
------------------------------------------------------
RCX_vm11-668@1       2014-04-01 19:21:40 +0900 shutoff

2. Check the difference of the version numbers retained in the virtual L-Server and the VM guest.

3. Redefine the insufficient versions of snapshots manually.
For details on how to redefine snapshots, refer to the following in the "Virtualization Administration Guide".
- 14.13. Managing snapshots

URL:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html

The snapshot with the information defined is necessary to redefine the snapshot definition. In Resource Orchestrator, the files are stored in the following location:

The location to store the configuration files necessary for redefining snapshots
1. Identify the disk resource used as the system volume of the virtual L-Server.
2. Identify the virtual storage with the disk resource identified in step 1.
3. Identify the storage pool for libvirt for the virtual storage identified in step 2.
4. Identify the NFS public directory specified in the storage pool for libvirt specified in step 3.
5. The VM guest name can be referred to in the NFS public directory identified in step 4.
The files with the snapshot information defined are stored in the directory.
The format of the file name is as follows:

RCX_{VM_guest_name}@version_number.xml

[OVM for SPARC]
When the "auto-boot?" change function was enabled when migration was performed, one of the following processes may have failed.

The change process of "auto-boot?"
The preservation process of the composition information performed before migration

Therefore, check the following.

Check that you can execute the ldm command on the VM host.
Check that this product can save configuration information referring to the corrective action given in "Message number 41127."

Check whether the value of "auto-boot?" set for the guest domain has been returned to the value before migration.
When the preset value of "auto-boot?" differs from the value before migration, perform the "Procedure that restores the preset value of "auto-boot?"" of "Message number 67375", and revert the value of "auto-boot?".

When error_number is "534": Check if the target VM host name is correct.

When error_number is "535": Check whether the server specified as the destination has a configuration that allows migration referring to "9.2 Configuring Server Virtualization Software" in the "Design Guide VE". Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact your network administrator.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

67388

FJSVrcx:ERROR:67388:vmguest in lserver is registered as a VM Host(vmhost).

[Cloud Edition]

Description

A VM guest currently assigned to L-Server for deletion is registered as a VM host.
The name of the L-Server for deletion is displayed in lserver.
The name of the VM guest currently assigned to lserver is displayed on vmguest.
The name of the registered VM host is displayed in vmhost.

Corrective Action

Perform deletion of lserver after canceling VM host's registration to vmguest.

67389

FJSVrcx:ERROR:67389:value is already in use on obj

Description

When value is "Server Role(Manager)"
The specified server role (Manager) is already configured in obj.
The name of the VM guest is displayed for obj.

Corrective Action

When value is "Server Role(Manager)"
After cancelling the settings of obj, perform the operation again.

[Cloud Edition]

Description

When value is "image"
The specified cloning image name image is already in use by another VM management software obj.
When value is "Address"
The specified address is already in use on obj.
When value is "Network_resource_name (Network_interface_name)"
The network interface corresponding to the specified network resource is already in use on obj.
The name of a VM host or VM guest is displayed for obj.
When value is the role name
The specified role name has already been used.
In obj, the user name or the user group name is displayed.

Corrective Action

When value is "image"
Perform the operation again after specifying another cloning image name.
When value is "Address"
Specify another address, and then perform the operation again.
When value is "Network_resource_name (Network_interface_name)"
Either specify a different network resource, or check and correct the virtual network definition file, and then perform the operation again.
When value is the role name
Check the user or the user group obj that uses the specified role.
Perform one of the following corrective actions:
- If obj is required, allocate another role.
- If obj is not required, delete it.
The user or the user group name can be checked using a command.
For details, refer to "7.1 rcxadm user" or "7.2 rcxadm usergroup" in the "Reference Guide (Command/XML) CE".

67390

FJSVrcx:ERROR:67390:creating VM guest failed. detail=detail

[Cloud Edition]

Description

Failed to create a VM guest.
Take corrective action for the content displayed for detail.
If this message is displayed when creating an L-Server, and the operation fails, the VM guests being created on server virtualization software may remain. For the corrective action, refer to "Corrective Action".

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host, VM management software, VDI management server, or VDI management software from IP_address. Take corrective action based on error_number.
If detail is displayed in the "invalid parameter:parameter:value" format
If detail is "timeout occurred"
When detail is "(repositoryId: repository not found,vmerrno=244,ip=IP_address,host= VM_host_IP_address)"
When detail is "(ftp error:Error_msg., vmerrno=820,ip=IP_address,host=VM_host_IP_address)"
When detail is "(ftp error: 550 Failed to change directory.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)
When detail is "(ftp error: 550 Permission denied.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"
When detail is "(timeout occurred while executing the customizing process.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"
When detail is "( PowerShell script execution error : Error_Msg,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"
When detail is one of the following:
- The "(vmware remote error,vmerrno=101,ip=IP_address)" format
- The "(logout failed(remote error),vmerrno=116,ip=IP_address)" format
- "timeout occurred"
If detail is "invalid parameter:memory size:Memory_size_in_the_unit_of_MB"
When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243] is displayed in the system event log
For the following OSs, allocation of the OS memory size, which is referred to as the desktop heap, failed.
- Windows Server 2008
- Windows Server 2012
- Windows Server 2016

Corrective Action

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "9", "104", or "105"

When detail is the following, and one of the problems below occurs during L-Server creation or startup, creating or starting of the L-Server fails, but VM guests being created on server virtualization software may remain.

detail

The "(message,vmerrno=9,ip=IP_address)" format
The "(PowerShell script execution error : create_vmguest:task result error,vmerrno=104,ip=IP_address, host=VM_host_IP_address)" format
The "(PowerShell script execution error : create_vmguest:task result timeout,vmerrno=105,ip=IP_address, host=VM_host_IP_address)" format
The "(clone image_name:task result error,vmerrno=104,ip=IP_address)" format
The "(create VM_guest_name:task result error,vmerrno=104,ip=IP_address)" format
The "(Message:task result error,vmerrno=104,ip=IP_address, host=VM_host_IP_address)" format
The "(PowerShell script execution error : create_vmguest:VM guest already exists,vmerrno=603,ip=IP_address, host=VM_host_IP_address)" format

Occurred Problems

System failure, or reboot of the admin server or manager
Job cancel or time out on VM management software
Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

Corrective Action: Make sure that the manager is running, and use the following procedure for restoration:

When using VDI coordination, execute the following procedure on the View Administrator console of the VDI management server.

a. Delete the user qualifications assigned to the VM guest.
b. Release the VM guest registration from the VDI pool.
c. Shut down the VM guest.
Execute the following command from the VMware vSphere PowerCLI of the VDI management server.

>Connect-VIServer -Server vCenter_IP_address -User User_name -Password Password <RETURN>
>Get-VM -Name VM_guest_name | Shutdown-VMGuest -Confirm:$false <RETURN>
>Disconnect-VIServer -Confirm:$false <RETURN>

d. Delete the user qualifications assigned to the VDI pool.
e. When no VMs are registered in the VDI pool, delete the VDI pool.

Check the VM guest name related to the error message above with the event log on the ROR console.
The VM guest name is displayed for the resource name in the event log.
Display the VM management console, and check if the VM guest checked in step 1 exists.
Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached in step 2, detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in step 2, delete it from the VM management console. For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in step 1 does not exist, create or start the L-Server again.

When error_number is "11"

[KVM]

When detail is "invalid format key:val.", the value of key is invalid. After changing the "val" you entered, perform the operation again.
For how to check, refer to "8.6.8 [OS] Tab Configuration" in the "Setup Guide CE".
When detail is "invalid value time_zone:val" The value of time_zone is invalid, please check the time zone value in the XML file which used by L-Server Create command.
When detail is "invalid format of password" The value of password is invalid. Please check and correct the "password" you entered, and retry the operation.

When error_number is "13"

Accessing the file which is displayed in message failed.
Check the relevant file settings on the admin server.

[Solaris Zones]
Review the configuration of the relevant file, and perform the operation again.
For details on the image file storage location, refer to "8.7.5 Creating and Importing Cloning Images" in the "Setup Guide CE".

When error_number is "15"

The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

[Solaris Zones]
A timeout has occurred in starting the OS of the VM guest.
Check the operation status and network settings of the VM host. When the settings are configured for using the custom script for the initial boot of an image, check that there are no incorrect descriptions in the custom script.
For details on the custom scripts for the first boot, refer to the Solaris OS manuals.

Also check the corrective action for the following situation, described in "Message number 62597".

When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain.

[OVM for SPARC]
The shutdown process after installing the OS in a guest domain may have timed out.
Perform the operation again.
When the created guest domain is not deleted, delete it referring to "Deletion procedure for guest domains" given in "Message number 67373".

When error_number is "16": A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

When error_number is "17"

The image could not be found.
The virtual cloning images of the operation targets may have been deleted from the VM management software.
The tenant administrator or the tenant user must notify the infrastructure administrator of the message details, and the cloning image name and the version of the operation target.
The infrastructure administrator should check that maintenance mode is not configured for the virtual cloning image.

When the maintenance mode of the virtual cloning image is released: Based on the notified information, check if the virtual cloning image of the operation target (image_name_number@version_image) exists on the VM management software and Resource Orchestrator.
When the image does not exist, inform the notifier that the virtual cloning image has already been deleted.
When there are images on VM management software, collect troubleshooting information and contact Fujitsu technical staff.

When the maintenance mode of the virtual cloning image has been configured: Based on the notified information, check if the virtual cloning image of the operation target (image_name_number@version_image) exists on VM management software.
When the image does not exist, request the notifier to delete the virtual cloning image of the operation target from Resource Orchestrator.
When there are virtual cloning images on VM management software, collect troubleshooting information and contact Fujitsu technical staff.

[OVM for SPARC] [Solaris Zones]
The created VM guest was not found. Check if the created VM guest exits on the VM host.

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/ VM management software resulting from multiple operations, obtaining of information from VM host/ VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "100", "115", "178", "337", or "381": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "101", "110", "111", "112", "114", "116", "181", "249", "341", or "382 "

Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
When using VDI coordination, communication between the admin server and the VDI management software has failed. Check the operating status and network settings of the admin server and the VDI management software.

[Solaris Zones]

Transfer of the image file may have failed due to a lack of access authority. Check the VM guest name of the creation target in the event logs, and then check the access authority of the image file stored in the image file storage directory (/ror_zones/VM_guest_name) on the VM host. When the VM host status cannot be updated by the user that registered the VM host, modify the settings to be updated.
Processing that the admin server requested from a VM host has timed out.
There is a possibility the OS installation process took a long time due to the configuration (CPU, memory, etc.) of the virtual L-Server used for deployment, the response time of the repository server, the number of installation packages, the processing time of the initial boot service, etc.
Use the following definition file to change the timeout time for OS installation.
- The value of ZONE_INSTALL_TIMEOUT in the definition file for SPARC-specific functions
For details on the definition file, refer to "8.7.1 Creating Definition Files" in the "Setup Guide CE".
Check the corrective action for the following situation, described in "Message number 62597".
"When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain."

When error_number is "104"

On VMware, an L-Server was created by specifying a Windows image

- Sysprep is not located on VMware vCenter Server.

If the OS type for the VM guest is Windows, installation of Sysprep is required.
Locate Sysprep on VMware vCenter Server.

- The Sysprep located on VMware vCenter Server is incorrect.

The correct Sysprep file, determined by the OS version of the VM guest and the CPU architecture (x86 and x64) is necessary.
When using Windows Server 2008 or later, Sysprep is not required because it is set up in the OS.
Confirm the OS version for the VM guest and CPU architecture, and locate Sysprep on VMware vCenter Server.

For details on the location for Sysprep, refer to the description for the Microsoft Sysprep tool in the "vSphere Virtual Machine Administration Guide" manual released by VMware, Inc.
Refer to the relevant version of document, referring to the following URL:

URL: http://www.vmware.com/support/pubs/vs_pubs.html

The OS type specified for images when creating L-Servers and the OS type of the installed OS are different: The OS type specified for images when creating L-Servers and the OS type of the installed OS may be different.
The OS type for images is inherited from the L-Server that is the source of image collection. Check if the OS type of the L-Server that is the source of collection and the installed OS type are the same.
If the OS types are not the same, collect images again after configuring the correct OS type of L-Server as the source for collection, and create an L-Server.
However, the type of OS for an L-Server created specifying images cannot be changed. When the OS type of the L-Server cannot be changed, use server virtualization software to collect images again after configuring the correct OS type for the VM guest, and then create the L-Server.
Delete collected images that have the wrong configurations.
For details on how to change the OS type of an L-Server, refer to "17.2.1 Modifying Specifications" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on how to change the OS types of VM guests using server virtualization software, refer to the server virtualization software manual.

When error_number is "104", "105", "135", "136", "178", "509", "510", "511", "512", "513", "519", "520", "521", "531", "532 ", "550", or "556"

Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
If an image has been specified when executing the operation, the OS customization process may have failed. Check that the device path to the system disk of the specified image is the following:

[Hyper-V]
IDE:0:0
[VMware]
SCSI:0:0

When using a device other than the above, change the disk configuration of the image, and then perform the operation again. For details on how to change disk configurations, refer to the manual of the VM management software.

When domain participation has been specified, the domain participation process may have failed because the specified information is invalid. Check if the specified information is correct.
Check if the Active Directory can be connected to in the network configuration after L-Server deployment.
Windows OS versions before Windows Server 2003 are not supported.
DHCP servers may be required for the network which can be accessed from the guest OS.

[Hyper-V]
If error_number is "104", and the guest OS type is Windows, the product key may not be correct. Check that the correct product key has been specified. The product key cannot be omitted.

[VMware]
If the error number is "104" and the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

[OVM for x86 3.2]
The Virtual NICs created using Oracle VM Manager may be insufficient. Check whether the Virtual NICs created using Oracle VM Manager are sufficient.

[OVM for x86 3.3 or later]
The range of MAC addresses defined in Oracle VM Manager may be insufficient. Check whether the range of MAC addresses defined in Oracle VM Manager is sufficient.

When a VM host with [Inbound Migration Locked] configured is selected as the destination host for L-Server deployment, L-Server creation will fail.
After performing one of the following corrective actions, perform the operation again.

Configure another VM host as the destination host of the L-Server
Release the [Inbound Migration Locked] configured on the VM host

When using VDI coordination, processing of VDI management software tasks has failed.
As an inconsistency exists between the information held by Resource Orchestrator and the information held by the VDI management software, operation of the VM management software may have failed. Resolve the problem caused by the inconsistency, and then perform the operation.

When error_number is "113": Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using VDI coordination, communication with the VDI management software using the login account information of the VDI management software is not possible.
Change the entered values (user name and password) for the login account information to the correct values.

When error_number is "170", "171", "172", "173", "174", "175", "176", "177", "179", or "180 ": The VM guest could not be created using an image. Check the cause of the error in the VM host/VM management software, and resolve the error.

When error_number is "222"

Check if there are any errors in the values used when creating an L-Server. When there are no problems in the setting values, check the operating status and network settings of the admin server, the VM host, and the VM management software.

[OVM for SPARC]
Check the following and then perform the operation again.

There may be a guest domain with the same name as the one for creation on the VM host where the guest domain is to be created. Check whether a guest domain with the same name exists.
The virtual switch specified as the virtual network definition file (vnetwork_ovmforsparc.rcxprop) may not exist. Check whether there is a virtual switch on the service domain.
The disk added when creating the L-Server may no longer exist. Check that the target disk exists on the service domain.

In addition, if the manager fails during creation of an L-Server, this error number is output after the manager is restarted.
In that case, take the following corrective action.

Check whether the created guest domain has been deleted.
If it is not deleted, delete the guest domain referring to "Deletion procedure for guest domains" given in "Message number 67373".
In BladeLogic Server Automation, there is possibility a provisioning job is being performed for a guest domain.
Check the run state of provisioning jobs referring to the "Procedure for checking the run state of a job in BladeLogic Server Automation" given in "When error_number is "400"".
If a job is being performed, cancel the job.

When error_number is "240", "335", or "603": Failed to create a VM guest because the VM guest name is already in use. Change the VM guest name or the destination VM host.

When error_number is "241", "242", "244", or "332": Could not create a VM guest in the definition file storage location of the VM guest. Check the status of the definition file storage location of the VM guest.

When error_number is "245": The VM guest name is invalid. Change the VM guest name.

When error_number is "246": The specified VM host cannot create a VM guest. Change the destination VM host.

When error_number is "330", "331", "333", "334", "336", "340", or "342": Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.

When error_number is "338": Failed to modify the configuration because another operation was performed on the created VM guest. Perform the operation again after waiting a while.

When error_number is "339": Too many devices were specified for creation in the VM guest. Perform the operation again after decreasing the numbers of disks or NIC.

When error_number is "380": Failed to set the OS unique information for the VM guest again. Set the OS unique information for the created VM guest again.

When error_number is "400"

[Citrix Xen]

When "xe vm-param-set::Error code: MEMORY_CONSTRAINT_VIOLATION" is displayed: There is a possibility XenServer is being used with a free license.
Resource Orchestrator does not support XenServer with free licenses.
Check the license of XenServer registered in the pool of CitrixXen, and apply for a paid license.

[Solaris]
The failure may have occurred because of conflicting remote commands. Execute the failed operation again.

[KVM]

When error message returned by command is "command not found": The command was not found on the VM host.
Check that all of the necessary packages have been installed on the VM host.

When error message returned by command is "no operating system was found on this disk": No guest operating system was found on the image disk.
This is probably because libguestfs-winsupport.x86_64 has not been installed on the VM host.
For the packages installed to a guest OS, refer to the "Preparations" of "When using a Windows cloning image" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE".

When "Packages for automatic OS setting not installed." is displayed for detail

The required packages for automatic OS configuration (ip, host name, etc.) of the VM on a VM host has have not been installed.

- Check that all of the packages for automatic OS setting in "Preparations" of the "When using a Linux (SELinux) cloning image" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE" have been installed.

- Check that all of the packages for automatic OS setting in "Preparations" of the "When using a Windows cloning image" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE" have been installed.

When "DefaultPassword registry not found." is displayed for detail

The "DefaultPassword" registry value was not found.
Check the following registry value on the L-Server that is the target of cloning image collection.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultPassword

Or, check all of packages for automatic OS setting are installed in "Preparations" in "When using a Windows cloning image" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE".
Refer to the "Preparations" of "When using a Windows cloning image" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE".

When "timeout occurred while executing sysprep." is displayed for detail

There is a possibility that preparation was not performed correctly, or execution of sysprep failed.
Log in to the L-Server that is the target of cloning image collection and check the following registry value.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultPassword

If there is a mistake in the administrator password, enter the administrator password again and then perform the operation that collects cloning images.

If this does not resolve the problem, there is possibility that execution of sysprep failed.
After removing the cause of the error of sysprep, collect the cloning image again, and create an L-Server.

As the sysprep logs are stored on the VM guest, it is necessary to log in to the VM guest linked with the virtual L-Server when collecting the sysprep logs.
The procedure to log in to the VM guest linked with the virtual L-Server of which creation failed, and to collect troubleshooting data is given below.
The procedure to log in to the VM guests differs depending on the type of disk resources that were to be allocated to the system volume of the virtual L-Server of which creation failed.

When allocating disk resources to the system volume of the virtual L-Server from virtual storage

The VM guest and the qcow2 format image file used for the system volume remain.
Collect the sysprep logs from the VM guest.

1. Identify the VM guest linked with the Virtual L-Server for which creation failed.

- For the VM host on which the VM guest is defined
"(message,vmerrno=error_number,ip=IP_address)",host=VM_host_IP_address)" is output for detail in the error message.
The VM guest linked with the virtual L-Server of which creation failed is defined in the VM host displayed in "VM_host_IP_address".

- For the VM guest name
For details on the VM guest name defined in the VM guest, refer to "Association of an L-Server Name with a VM Guest Name" in "16.1 Creation Using an L-Server Template" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
The VM guest name is displayed in the line of [Creating VM guest] in the Progress List for the virtual L-Server creation in the Recent Operations on the ROR Console.

2. Start the VM guest identified in step 1.
For details on how to start VM guests, refer to the following in the "Virtualization Administration Guide".

URL:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html

3. Log in to the VM guest identified in step 2, and collect the troubleshooting data.
For details on collecting troubleshooting data, refer to the following:

URL: http://technet.microsoft.com/ja-jp/library/dd744583(v=ws.10).aspx

4. It is recommended to delete the qcow2 format image file used for the system volume and the VM guest identified in this procedure, after the collection of troubleshooting data is complete.
For details on how to delete the VM guest and the image file, refer to the "Virtualization Administration Guide".

URL:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html

Note

When keeping the VM guest instead of deleting it, it will consume some of the memory and the CPU of the VM guest.
When leaving the qcow2 image file without deleting it, it will consume some of the virtual storage capacity.

When allocating disk resources created in advance to the system volume of the virtual L-Server

The content of the cloning image remains in the disk resource that was to be allocated to the system volume.
Collect the sysprep log from this image.

1. Identify the disk resource created in advance that was to be allocated to the system volume of the virtual L-Server for which creation failed.

2. Check that the disk resources identified in step 1 are not allocated.

Note

Check that the disk resource has not been allocated to another L-Server.
If a virtual L-Server created after this step, while the disk resource is still allocated to another L-Server, the data on the disk resource may be damaged.
For details on how to check, refer to the line in the L-SERVER[num] column in "Table: Detailed Information for Disk Resources" in "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".

Check that the disk resource is not allocated to a cloning image.
It is necessary to check if there are image resources stored on the disk resource.
For details on how to check, refer to the description in the -extend image section in "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".

3. Create the virtual L-Server to which the disk resource from step 2 is to be allocated as the system volume.
At this time do not specify the cloning image to deploy.
For details on the method not to specify the cloning image, refer to "Image" in "16.3.1 [General] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

4. Log in to the VM guest linked with the virtual L-Server created in step 3, and collect the troubleshooting data.
For details on collecting troubleshooting data, refer to the following:

URL: http://technet.microsoft.com/ja-jp/library/dd744583(v=ws.10).aspx

5. It is recommended to delete the virtual L-Server created in this procedure, after collection of troubleshooting data is complete.

Note

When keeping a virtual L-Server, it will consume some of the memory and the CPU of the VM host.

When "Error: libvirt-0.9.4-23.el6_2.4 or later is needed." is displayed in detail: This means the version of libvirt package installed on VM host in the migration destination is older than 0.9.4-23.el6_2.4.
As there are non-compatible functions that can lead to security vulnerabilities, upgrade the libvirt package to 0.9.4-23.el6_2.4 or a later version.

[Solaris Zones]

When "operation failed:creating directory" is displayed for detail: Failed to create a directory for storing images on the VM host.
Referring to the event messages, resolve the cause of why a directory for storing images cannot be created on the VM host.

When "operation failed:encrypting password" is displayed for detail: Password encryption on the VM host failed.
Referring to the event messages, resolve the cause of why password encryption cannot be performed on the VM host.

When "operation failed:creating vm guest configuration" is displayed for detail

Failed to create a VM guest. Check the following and then perform the operation again.

- There may already be a VM guest with the same name as the one to be created on the destination VM host. Check whether a VM guest with the same name exists.

- Check that there are no incorrect details in the image.

When "operation failed:customizing vm guest" is displayed for detail: Failed to modify the configuration of the VM guest.
Check that there are no incorrect details in the image.
Information
When creating an L-Server, add or modify the following resources and attributes as necessary:
Therefore, do not describe resources or attributes which are in exclusive relationship with these attributes in zone.conf.
- zonepath
- pool
- capped-memory: physical
- capped-cpu: ncpus
- anet
- fs
- rootzpool
Combination examples of resources and attributes in exclusive relationships
- capped-cpu and dedicated-cpu
- anet and ip-type=shared

When "operation failed:installing guest os" is displayed for detail

Installation of an OS on the VM guest failed.
Check that the access settings for the repository server on the VM host are correct, and that the repository server is running.

Also check the corrective action for the following situation, described in "Message number 62597".

- When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain.

When "operation failed:booting vm guest" or "operation failed:shutting down vm guest" is displayed for detail

Performance of power operations on the VM guest failed.
There is an inconsistency between the value specified while creating the L-Server and the VM host settings.
Check the operation status and network settings of the VM host.

Also check the corrective action for the following situation, described in "Message number 62597".

- When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain.

[OVM for SPARC]

When "failed to start os installation" is displayed for detail

This product might have been unable to connected to a URL defined in ovm_sparc_install_server.rcxprop.
Check that the value defined for ovm_sparc_install_server.rcxprop is correct.
In addition, when the created guest domain is not deleted, delete the guest domain referring to "Deletion procedure for guest domains" given in "Message number 67373".

Also, in BladeLogic Server Automation, there is a possibility that a provisioning job for a guest domain is being performed.
Check the run state of provisioning jobs referring to the "Procedure for checking the run state of a job in BladeLogic Server Automation", and when a job is being performed, cancel it.

When "shutdown vm guest failed" is displayed for detail: The shutdown process after OS installation failed in the L-Server creation process for which a Solaris 10 image was specified.
It may be because specification of the administrator password was omitted during L-Server creation.
In addition, when the created guest domain is not deleted, delete the guest domain referring to "Deletion procedure for guest domains" given in "Message number 67373".
Also, in BladeLogic Server Automation, there is a possibility that a provisioning job for a guest domain is being performed.
Check the run state of provisioning jobs referring to the "Procedure for checking the run state of a job in BladeLogic Server Automation", and when a job is being performed, cancel it.
Re-create the L-Server after carrying out the above-mentioned actions, with the administrator password specified.

Procedure for checking the run state of a job in BladeLogic Server Automation

Start BladeLogic Server Automation Console.
Start BladeLogic ServerAutomation Console and enter the user name and password for connecting with the Application Server of BladeLogic Server Automation.
Check the run state of the job.
In the [Task under execution] view, check whether the provisioning job of the L-Server (guest domain) for which creation failed is displayed.
When the applicable job name is displayed, choose the job and click [Cancel].
The format of job names is as follows:
The execution time of the job_control domain's IP address_guest domain name

When error_number is "401": [Solaris Zones]
Virtual L-Servers cannot be created in the global zone on physical servers.
Create a virtual L-Server using the global zone on the guest domain of OVM for SPARC.

When error_number is "501" or "608": Make sure that the specified virtual network name exists on the VM host.

When error_number is "503": There is no target operation image on VM management software.
Perform the operation again after checking that there are no differences between image information on Resource Orchestrator and the VM management software.

When error_number is "514": After confirming if there is no trouble with the administrator account information, perform the operation again.

When error_number is "515" or "607": Perform the operation again, after specifying a supported OS for VM host.

When error_number is "534": Check if the target VM host name is correct.

When error_number is "535": Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact your network administrator.

When error_number is "536", "538", or "546": There is a problem with the library of System Center Virtual Machine Manager. Check that the status of the library server or shared library is normal, then perform the operation again after waiting for a short time.

When error_number is "537" or "539": Operation of the System Center Virtual Machine Manager library failed. Check the result of the job using System Center Virtual Machine Manager.

When error_number is "548"

Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

When using VDI coordination, there may have been a problem with the installation of VMware Horizon View. Check that VMware Horizon View has been configured properly.

When error_number is "552", "553", or "554": Remote WMI execution of Failover Cluster failed. Check that the remote WMI execution is not blocked by Windows Firewall or anything else. If it is not blocked, check that the status of the Failover Cluster is normal using Failover Cluster Manager, and then perform operation again after a while.

When error_number is "555": Remote WMI execution of Failover Cluster failed. Register the login account of VM management software (which is entered when the VM management software is registered in Resource Orchestrator) in the Administrators groups of all VM hosts, and then perform the operation again.

When error_number is "604": Specify a value smaller than the physical memory size of the VM host.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

When error_number is "605": Specify a value smaller than the number of CPU cores of the VM host.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

When error_number is "606": The number exceeds the number of available CPUs. Specify a value in the available range.

When error_number is "609": The VLAN ID value is not in the available range of values. Specify the available range.

When error_number is "614": The level exceeds that of available CPU performance. Specify the available range.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

When error_number is "616": The specification format for the time zone is incorrect. Specify the correct format.

When error_number is "617": The product ID specification format is incorrect. Specify the correct format.

When error_number is "618": Administrator information is invalid. Specify valid information.

When error_number is "621"

There is an error in one of the following specified IP addresses:

The IP address specified during creation of the L-Server
The IP address specified in the OS property definition file

Confirm the following:

That the format of the IP address is correct
That the IP address is unique within the system

When error_number is "624": The template of System Center Virtual Machine Manager corresponding to the specified image is either invalid or damaged. Check the image using System Center Virtual Machine Manager.

When error_number is "643": The specified pass-through disk could not be found.
Check that the unique ID of the specified pass-through disk exists on the target VM host.

When error_number is "644": The specified pass-through disk has already been used.
Specify the unique ID of a pass-through disk that has not been used.

When error_number is "654": The MAC address pool was not found under the management of System Center Virtual Machine Manager at the IP address.
Check if a MAC address pool available for use exists in the corresponding System Center Virtual Machine Manager.

When error_number is "655": There are multiple MAC address pools that can be used.
Specify the name of the pool to use.

When error_number is "656": A MAC address available for use could not be obtained from the MAC address pool specified in the definition file "scvmm_mac_pool.rcxprop" or "scvmm_mac_pool_tenant_name.rcxprop".
Check the corresponding System Center Virtual Machine Manager to see if there are any MAC addresses available for use left in the specified MAC address pool.

When error_number is "657": The MAC address pool specified in the definition file "scvmm_mac_pool.rcxprop" or "scvmm_mac_pool_tenant_name.rcxprop" is not under management of System Center Virtual Machine Manager at the IP address.
Check if the specified MAC address pool exists in the corresponding System Center Virtual Machine Manager.

When error_number is "658": The MAC address pool specified in the definition file "scvmm_mac_pool.rcxprop" or "scvmm_mac_pool_tenant_name.rcxprop" cannot be used by the host group to which the VM host at VM_host_IP_address belongs.
Check the corresponding System Center Virtual Machine Manager to see if the specified MAC address pool can be used by the host group to which the target VM host belongs.

When error_number is "659": Wait for a short while and then perform the operation again. If the retry failed, the tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check if all file paths in the message can be accessed on the VM host where the target VM guest exists. If not, take corrective action to make them accessible, and then request the user who reported the problem to perform the operation again.

When error_number is "663": Waiting for a while, then perform the operation or check again.

When error_number is "665": The virtual network connected to the virtual network adapter does not have a high availability attribute. Configure the virtual network definition file of Resource Orchestrator so that a high availability virtual network is defined as the destination. If there is no problem with the configuration defined in the virtual network definition file, the virtual network configuration information on the VM management software may have not been updated. Wait for a while or update the host cluster on the VM management software, and then perform the operation again.

When error_number is "669": The specified VM network name could not be found.
Check that the specified VM network name exists on SCVMM.

When error_number is "670": As there are multiple VM network names specified, the connection destination cannot be identified.
Modify the VM network name not to overlap with others on SCVMM.

When error_number is "804": The data center cannot be found on the VM management software. Check if the data center name has been modified on the VM management software. If it has been modified, wait for a while and perform the operation again.

When error_number is "806": VM host cluster is not configured on the VM management software. Configure the cluster, referring to the server virtualization software manual. If the cluster has been configured, check if the cluster name has been modified on the VM management software. If it has been modified, wait for a while and perform the operation again.

When error_number is "807": High availability setting is disabled for the VM host cluster on the VM management software. Enable high availability setting, referring to the server virtualization software manual, and then perform the operation again.

When error_number is "809" [Citrix Xen] [OVM for x86 3.x]: The device nodes specified during L-Server creation are already used for CD-ROMs or Raw disks.
After specifying another device node, perform L-Server creation again.

When error_number is "812": The format of the specified file is invalid. Check the format of the file assigned to the group qualifications.

When error_number is "820"

[Citrix-Xen]

When detail is "Selected device number is already used(device number=number)": The specified disk number has already been used. Release connection with the device using the disk number, and perform the operation again.

When detail is " sr name not found(sr name=SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address" or "sr type is not iso(sr name=SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address": There is a possibility a definition of the guest OS customization definition file is wrong. Confirm the content of the definition file, and perform the operation again. In addition, confirm whether the SR (storage repository) defined in the definition file exists in XenServer.

When detail is "duplicate sr name found(sr name= SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address": Two or more SRs with the same name are registered in XenServer. Change the SR names so they do not overlap, and perform the operation again.

When detail is "timeout occurred while executing the customizing process.,vmerrno=820, ip=IP_address,host=VM_host_IP_address"

There is a possibility that the disk configuration of the specified image is wrong. Confirm whether the system disk exists in the device "0". If there is no system disk in the device "0", change the disk configuration of the image and perform the operation again. Refer to the manual of the VM product for the change in the disk configuration.

- Check whether the customizing tool has been installed on the guest OS. If the customization tool has not been installed, install it and perform the operation again.

- There is a possibility that the product key is wrong. Confirm whether the correct product key has been specified.

When detail is "PowerShell script execution error : generate answer file failed : administrator password value not specified,vmerrno=820, ip=IP_address,host=VM_host_IP_address": The administrator password of the guest OS is not specified. Specify the administrator password, and perform the operation again.

When detail is "PowerShell script execution error : generate answer file failed : non-builtin account name cannot be specified,vmerrno=820, ip=IP_address,host=VM_host_IP_address": Something other than the name of the built-in administrator has specified for the administrator account of the guest OS. In server OS, it is necessary to specify the name of the built-in administrator. Confirm whether the content of the administrator account definition file is correct, and execute it again.

When detail is "PowerShell script execution error : generate answer file failed : non-builtin account name required,vmerrno=820, ip=IP_address,host=VM_host_IP_address": The name of the built-in administrator has been specified for the administrator account of the guest OS. In the client OS, it is necessary to specify a name other than the name of the built-in administrator. Confirm whether the content of the account definition file is correct, and execute it again.

When error_number is "851"

Starting of an OS service on the VM guest failed.

[Solaris Zones]
Environment settings may be incorrect, for example, the IP address used for the VM guest is already used for the server.
Check the operation status and network settings of the VM host.

Information

This message is also output when the SMF service cannot start correctly after completion of OS customization.
In this case, the troubleshooting data that contains the cause of the SMF service being started is stored in the following folder of the manager. After checking the details, resolve the cause, and perform the operation again.

Storage Location of Troubleshooting Data

[Windows Manager]
Installation_folder\SVROR\Manager\var\vm_customize_log\solaris_zone

[Linux Manager]
/opt/FJSVrcvmr/var/vm_customize_log/solaris_zone

File Name of Troubleshooting Data: Operation_start_date_and_time_Non_global_zone_name.log

Details of Troubleshooting Data

The log file of the relevant service in /var/svc/log on the non-global zone is output in the following format:

Log file name
Log file details

Example

When the IP address configured in the non-global zone overlaps with the IP address configured in another server (when svc:/network/install:default is not started)

/var/svc/log/network-install:default.log
[ Feb 18 02:41:08 Enabled. ]
[ Feb 18 02:41:35 Executing start method ("/lib/svc/method/net-install"). ]
Error creating address on net2/v4:
state = duplicate
[ Feb 18 02:41:43 Method "start" exited with status 95. ]
[ Feb 18 02:41:43 Rereading configuration. ]

Note

As the troubleshooting data is not automatically deleted, manually delete it when it is no longer necessary.
Troubleshooting data is not a migration target for backup and restore, or upgrade installations.
To retain the troubleshooting data after backup and restore, or an upgrade installation, manually back it up before the operation.

When error_number is "853"

[Solaris Zones]

When "publisher (publisher_name) not found." is displayed for detail: Check if the publisher publisher_name is registered on the global zone.

When error_number is "854"

[Solaris Zones]

When "MAC address not found in Network_interface_name" is displayed for detail

There are no available MAC addresses on the network interface of the global zone corresponding to the specified network resource. After reviewing the following, perform the operation again.

- If a sufficient number of factory MAC addresses (substitute MAC addresses of the virtual network device of the guest domain) is allocated to the network interface of the relevant global zone.

- If there are any incorrect definitions in the virtual network definition file (vnetwork_solariscontainer.rcxprop).

When error_number is "855"

[Solaris Zones]

When "VM guest disk(diskpath) already exists." is displayed for detail

The virtual disk diskpath, which is to be allocated to the VM guest, already exists. Delete the virtual disk displayed in diskpath from the VM host, and then perform the operation again.

If a virtual disk that was already allocated remains, delete it also from the VM host.

The virtual disk (ZFS file system) is created using the following path format:

Virtual_storage_resource_name/rcx/VM_guest_name/diskXXX

For details on how to delete virtual disks, refer to the server virtualization software manual.

When error_number is "860": Connection with the VMware Horizon View service failed. Check if the VMware Horizon View service of the VDI management server has been started.

When error_number is "861": Connection from the VDI management server to the Active Directory has failed. Check if the Active Directory service of the domain is running.

When error_number is "862": A domain user who is not included in the specified domain group account is to be registered as the VDI user. Check the domain configuration and the VDI user specification.

When error_number is "863": There are already virtual machines of the specified VDI user in the specified VDI pool.
VDI users can only use one virtual machine per VDI pool. Do not register multiple virtual machines used by the same VDI user in a single VDI software pool.

When error_number is "864": Obtaining of the virtual machine information failed. Check that the VDI management server is able to communicate with the VMware vCenter Server registered in VMware Horizon View.

When error_number is "865": Failed to create the VDI pool. Check the specifications of the VDI pool.

When error_number is "866": Assigning of VDI user qualifications for the VDI pool or the group account qualifications for the domain failed. Check the specifications of the VDI user or the domain group account.

When error_number is "867": Assigning of VDI user qualifications for the virtual machine failed. Check the specifications of the VDI user.

When error_number is "873": The VDI user name is incorrect. Specify the correct VDI user name.

When error_number is "874": The domain group account described in the file assigned for the group qualifications is not on the Active Directory. Check the group account of the domain that was specified.

When error_number is "875": The domain name is incorrect. Specify the correct domain name.

If detail is displayed in the "invalid parameter:parameter:value" format: The parameter value is invalid. Perform the operation again after modifying the entered value.

If detail is "timeout occurred"

The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
Due to hardware failure, L-Server creation may take an excessive amount of time.
When it takes a long time, L-Server creation may fail.
There is a possibility that the hardware of the server used for L-Server creation has failed.
Check the following:

When the server used to create the L-Server is a blade server, if failure of the Fibre Channel switch blade has occurred
When the server used to create the L-Server is a blade server, if failure of the LAN switch blade has occurred

When hardware failure has occurred, update the hardware information held by the server virtualization software.
For details on how to update hardware information, refer to the server virtualization software manual.

[Solaris Zones]
If an error occurs during L-Server creation, check the following:

Check that a network interface that does not exist on the VM host has not been specified.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
Check that a network interface used by another zone has not been specified on the VM host.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
When configuring the L-Server network interface using the DHCP settings, check if the settings to allocate IP addresses from the DHCP server are configured.
Check that the IP address allocated to the L-Server has not been allocated in duplicate.

When detail is "(repositoryId: repository not found,vmerrno=244,ip=IP_address,host= VM_host_IP_address)": An error occurred while customizing the guest OS.
There may be incorrect definitions in the guest OS customization definition file (os_customize_ovmx86.rcxprop).
Confirm the content of the definition file, and perform the operation again. In addition, confirm whether the SR (storage repository) defined in the definition file exists in OVM for x86 3.x.

When detail is "(ftp error:Error_msg., vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

Logging-in to the FTP server has failed.

Confirm that the URL, user name, and password of the registered FTP server are correct, register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Failed to change directory.,vmerrno=820,ip=IP_address,host=VM_host_IP_address): The directory for storing VCD on the FTP server does not exist.
Confirm that there is a directory for storing VCD in the registered FTP server.
Register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Permission denied.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)": The user does not have permission for uploading, downloading, or deleting files on the FTP server.
Configure permission for uploading, downloading, and deleting files on the FTP server. Then perform the operation again.

When detail is "(timeout occurred while executing the customizing process.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

An error occurred while customizing the guest OS.

Check whether the customization tool has been installed on the guest OS.

If the customization tool has not been installed, install it and perform the operation again.

When the guest OS is Windows, there are the following possibilities:

An incorrect system type may have been specified during image collection.
Check whether the system type is correct, and perform the operation again.
There is a possibility that the executable frequency of sysprep (frequency at which the Windows delay time limit can be reset) is 0.
Execute the following command on the VM guest that is the source for image collection, and confirm the frequency that can be reset.
When the frequency that can be reset is 0, image collection cannot be executed. Prepare a new VM guest to use as the source for image collection.
>%systemroot%\system32\slmgr.vbs /dlv <RETURN>

When detail is "( PowerShell script execution error : Error_Msg,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

An error occurred while executing the PowerShell script during creation of the ISO for guest OS customization.
The administrator password of the guest OS is not specified. Specify the administrator password, and perform the operation again.

For details on how to set administrator passwords, refer to "8.10.8 [OS] Tab Configuration" in the "Setup Guide CE".

When detail is one of the following:

When detail is one of following, if system failure occurs on the VM management software server or VM management software while creating or starting the L-Server, creating or starting of the L-Server will fail.

The "(vmware remote error,vmerrno=101,ip=IP_address)" format
The "(logout failed(remote error),vmerrno=116,ip=IP_address)" format
"timeout occurred"

Make sure that the VM management software is running, and use the following procedure for restoration.

Check the resource name related to the error message above with the event log on the ROR console. The VM guest name is displayed for the resource name.
Display the VM management console, and check if the VM guest checked in step 1 exists. Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached in step 2, detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in step 2, delete it from the VM management console.
For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
Check if the VM management software can communicate with the manager. Select the VM management software in the server resource tree of the ROR console, and check if the status displayed on the main panel is "normal".
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in step 1 does not exist, create or start the L-Server again.

[OVM for x86 3.x]

When detail is "timeout occurred": The response from VM host or VM management software to requests from the admin server timed out.
The setting of "VM Start Policy" for the Server Pool of Oracle VM Manager may be incorrect.
Check the setting of "VM Start Policy", and then perform the operation again.
For details on the setting of "VM Start Policy", refer to "Configuration of "VM Start Policy" for the Server Pool of Oracle VM Manager" in "8.10.12 Customization Function of Guest OS" in the "Setup Guide CE".

If detail is "invalid parameter:memory size:Memory_size_in_the_unit_of_MB": The memory size allocated to the VM guest is incorrect. The value specified for MAXDefinableMemorySize must be the same as or larger than the value of MemorySize.
For details on the MAXDefinableMemorySize setting method, refer to "8.1.2 VM Specific Information Definition File" in the "Setup Guide CE".

When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243] is displayed in the system event log: For the corrective action, refer to "13.1 When the Desktop Heap is Exhausted" in "Troubleshooting".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67391

FJSVrcx:ERROR:67391:deleting VM guest failed. detail=detail

[Cloud Edition]

Description

Failed to delete the VM guest.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host, VM management software, VDI management server, or VDI management software from IP_address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "16"
  A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
- When error_number is "17"
  A VM guest was not found. Check the following:
  - Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted.
  - Check whether the VM guest is set to be moved when its power status is changed using the VM management console.
  The VM host, which the L-Server is running on, detects that the VM guest of the L-Server does not exist, so L-Server deletion fails. Check the name of the VM guest of the L-Server using the GUI or the CLI.
  When using the GUI:
  Display the ROR console.
  1. Select the L-Server on the orchestration tree.
  2. Select the [Resource Details] tab on the main panel, and check the guest name of the resource.
  When using the CLI:
  1. Execute the following command:
    >rcxadm lserver show -name L-Server_name <RETURN>
  2. Check the display of "VmGuest:".
  If the VM guest name is not displayed, delete the L-Server again.
  If the VM guest name is displayed, check that migration is not being performed from the management screen of the VM management software, and then delete the L-Server again.
  When a message is output during deletion of the L-Server, check that the VM guest name of the L-Server is not displayed, and then delete the L-Server again.
- When error_number is "99"
  Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
- When error_number is "100", "115", "260", or "337"
  The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
  Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", "116", "263", or "341"
  Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
  When using VDI coordination, communication between the admin server and the VDI management software has failed. Check the operating status and network settings of the admin server and the VDI management software.
- When error_number is "104", "105", "135", "136", or "527"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
  Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
  When using VDI coordination, processing of VDI management software tasks has failed.
  As an inconsistency exists between the information held by Resource Orchestrator and the information held by the VDI management software, operation of the VM management software may have failed. Resolve the problem caused by the inconsistency, and then perform the operation.
  Take corrective action when "104" has occurred due to an error during L-Platform cancellation. For details, refer to "Cancellation" in "H.3.1 VMware Horizon View" in the "Setup Guide CE".
- When error_number is "113"
  Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
  Change the entered values (user name and password) for the login account information to the correct values.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
  When using VDI coordination, communication with the VDI management software using the login account information of the VDI management software is not possible.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "261"
  Failed to delete the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "262"
  Failed to delete the VM guest. VM guests cannot be deleted while their power is ON. Check the power state of the VM guest.
- When error_number is "330", "331", "332", "333", "334", "335", "336", "339", "340", or "342 "
  Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "338"
  Failed to modify the configuration because another operation was performed on the VM guest. Perform the operation again after waiting a while.
- When error_number is "400"
  Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
  If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.
  [Solaris Zones]
  - When "operation failed:uninstalling guest os" is displayed for detail
    Uninstallation of the OS of the VM guest failed.
    Change to a state where the VM guest can be deleted from the VM host, and perform the operation again.
  - When "operation failed:deleting vm guest configuration" is displayed for detail
    Failed to delete the VM guest.
    Delete the VM guest from the VM host, and perform the operation again.
  [KVM]
  If the following message is contained in detail, check that the operations and settings on the VM host are correct.
  libvir: QEMU error : Requested operation is not valid: Refusing to undefine while domain managed save image exists
  - Operations on VM hosts
    Execute the following command from the VM host where the target VM guest that could not be deleted exits.
    After this command is complete, you can delete the VM guest.
    # virsh managedsave-remove VM_guest_name <RETURN>
    Example
    When specifying vm_guest for the VM_guest_name
    # virsh managedsave-remove vm_guest <RETURN>
  - Checking /etc/sysconfig/libvirt-guests Configuration
    Check that /etc/sysconfig/libvirt-guests has been configured correctly.
    For details, refer to "E.5.2 Preparations for Servers" in "Design Guide CE".
- When error_number is "548"
  Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.
  When using VDI coordination, there may have been a problem with the installation of VMware Horizon View. Check that VMware Horizon View has been configured properly.
- When error_number is "860"
  Connection with the VMware Horizon View service failed. Check if the VMware Horizon View service of the VDI management server has been started.
- When error_number is "861"
  Connection from the VDI management server to the Active Directory has failed. Check if the Active Directory service of the domain is running.
- When error_number is "864"
  Obtaining of the virtual machine information failed. Check that the VDI management server is able to communicate with the VMware vCenter Server registered in VMware Horizon View.
- When error_number is "868"
  Failed to delete the VDI pool. Check the specifications of the VDI pool.
- When error_number is "869"
  Failed to delete the user or the user group of the VDI pool. Check the specifications of the user or the user group.
- When error_number is "870"
  Failed to delete the user of the virtual machine. Check the specifications for the user.
- When error_number is "871"
  Failed to delete the specified virtual machine from the VDI pool.
- When error_number is "872"
  Connection from the VDI management server to the VMware vCenter Server has failed. Communication using the specified login account information is not possible. Check the values (user name and password) entered for the login account information.
- When error_number is "873"
  The VDI user name is incorrect. Specify the correct VDI user name.
- When error_number is "874"
  The domain group account described in the file assigned for the group qualifications is not on the Active Directory.
  Check the group account of the domain that was specified.
- When error_number is "875"
  The domain name is incorrect. Specify the correct domain name.
If detail is "timeout occurred"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243] is displayed in the system event log
For the following OSs, allocation of the OS memory size, which is referred to as the desktop heap, failed.
- Windows Server 2008
- Windows Server 2012
- Windows Server 2016
For the corrective action, refer to "13.1 When the Desktop Heap is Exhausted" in "Troubleshooting".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67392

FJSVrcx:ERROR:67392:modifying VM guest failed. detail=detail

[Cloud Edition]

Description

Failed to modify the configuration of the VM guest.
Take corrective action for the content displayed for detail.
If this message is displayed when modifying L-Server configuration, some information may have been modified. If you want to check modified information, wait for a while and then check the L-Server information.
If this message is displayed when creating an L-Server, and the operation fails, the VM guests being created on server virtualization software may remain. For the corrective action, refer to "Corrective Action".

Corrective Action

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "9"

detail

The "(message,vmerrno=9,ip=IP_address)" format

Occurred Problems

System failure, or reboot of the admin server or manager
Job cancel or time out on VM management software
Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

Corrective Action: Make sure that the manager is running, and use the following procedure for restoration:

Check the VM guest name related to the error message above with the event log on the ROR console.
The VM guest name is displayed for the resource name in the event log.
Display the VM management console, and check if the VM guest checked in step 1 exists.
Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached in step 2, detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in step 2, delete it from the VM management console. For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in step 1 does not exist, create or start the L-Server again.

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "16": A VM host was not found. Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.

When error_number is "17"

A VM guest was not found. Check the following:

Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted.
Check whether the VM guest is set to be moved when its power status is changed using the VM management console.

When error_number is "20"

The port group of the specified virtual switch was not found on VM management software.
Check that the port group exists on VM management software.

If no port groups exist:
Create a port group for the virtual switch on VM management software.
If port groups exist:
When using the virtual network definition file, check that all definitions are described correctly.
After checking the definition file, perform the operation again.

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/ VM management software resulting from multiple operations, obtaining of information from VM host/ VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "100", "115", or "337": The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "101", "110", "111", "112", "114", "116", or "341": Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "104", "105", "135", "136", "512", "519", "520", "521", "523", "524", "525", "526", "528", "550", or "556"

Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.

[OVM for x86 3.3 or later]
When the HugePages setting is enabled, memory size modification for L-Servers may fail.
Perform either of the following corrective actions:

Use OVM Manager to disable the HugePages configuration for the VM guest and then repeat the operation
Use OVM Manager to modify the memory size of the VM guest

When error_number is "113": Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "200": vSphere PowerCLI has not been installed on the admin server. Install and configure vSphere PowerCLI, and then perform the operation again.

When error_number is "330", "331", "332", "333", "334", "335", "336", "339", "340", or "342 ": Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.

When error_number is "338": Failed to modify the configuration because another operation was performed on the VM guest. Perform the operation again after waiting a while.

When error_number is "400"

[Citrix Xen]

When "xe vm-param-set::Error code: MEMORY_CONSTRAINT_VIOLATION" is displayed: There is a possibility XenServer is being used with a free license.
Resource Orchestrator does not support XenServer with free licenses.
Check the license of XenServer registered in the pool of CitrixXen, and apply for a paid license.

When error_number is "501" or "608": Make sure that the specified virtual network name exists on the VM host.

When error_number is "515" or "607": Select an OS supported by the VM host and then perform the operation again.

When error_number is "522": There is no target VM guest virtual disk on VM management software.
Perform the operation again after checking that there are no differences between virtual disk information on Resource Orchestrator and the VM management software.

When error_number is "533": There is no virtual network adapter of the target VM guest on VM management software.
Perform the operation again after checking that there are no differences between virtual network adapter information on Resource Orchestrator and the VM management software.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

When error_number is "552", "553", or "554": Remote WMI execution of Failover Cluster failed. Check that the remote WMI execution is not blocked by Windows Firewall or anything else. If it is not blocked, check that the status of the Failover Cluster is normal using Failover Cluster Manager, and then perform operation again after a while.

When error_number is "555": Remote WMI execution of Failover Cluster failed. Register the login account of VM management software (which is entered when the VM management software is registered in Resource Orchestrator) in the Administrators groups of all VM hosts, and then perform the operation again.

When error_number is "604": Specify a value smaller than the physical memory size of the VM host.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details of the definition files, refer to "8.1.4 Definition Files when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

When error_number is "605": Specify a value smaller than the number of CPU cores of the VM host.

When error_number is "606": The number exceeds the number of available CPUs. Specify the available range.

When error_number is "609": The VLAN ID value is not in the available range of values. Specify the available range.

When error_number is "611": This operation cannot be performed on VM guests that have not been stopped. Stop the specified VM guest and then perform the operation again.

When error_number is "612", "613", "663", or "664": Wait for a while, then perform the operation or check again.

When error_number is "614": The level exceeds that of available CPU performance. Specify the available range.

When error_number is "643": The specified pass-through disk could not be found.
Check that the unique ID of the specified pass-through disk exists on the target VM host.

When error_number is "644": The specified pass-through disk has already been used.
Specify the unique ID of a pass-through disk that has not been used.

When error_number is "655": There are multiple MAC address pools that can be used.
Specify the name of the pool to use.

When error_number is "659": Wait for a short while and then perform the operation again. If the retry failed, the tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check if all file paths in the message can be accessed on the VM host where the target VM guest exists. If not, take corrective action to make them accessible, and then request the user who reported the problem to perform the operation again.
If the file path in the message does not exist or has been deleted, unregister the specified disk resource for automatically created LUNs, using the rcxadm disk unregister command. For details on the rcxadm disk command, refer to "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".

When error_number is "660": Disks with snapshots cannot be detached. Perform the operation on disks without snapshots.

When error_number is "665": The virtual network connected to the virtual network adapter does not have a high availability attribute. Configure the virtual network definition file of Resource Orchestrator so that a high availability virtual network is defined as the destination. If there is no problem with the configuration defined in the virtual network definition file, the virtual network configuration information on the VM management software may have not been updated. Wait for a while or update the host cluster on the VM management software, and then perform the operation again.

When error_number is "669": The specified VM network name could not be found.
Check that the specified VM network name exists on SCVMM.

When error_number is "670": As there are multiple VM network names specified, the connection destination cannot be identified.
Modify the VM network name not to overlap with others on SCVMM.

When error_number is "804": The data center cannot be found on the VM management software. Check if the data center name has been modified on the VM management software. If it has been modified, wait for a while and perform the operation again.

When error_number is "806": VM host cluster is not configured on the VM management software. Configure the cluster, referring to the server virtualization software manual. If the cluster has been configured, check if the cluster name has been modified on the VM management software. If it has been modified, wait for a while and perform the operation again.

When error_number is "807": High availability setting is disabled for the VM host cluster on the VM management software. Enable high availability setting, referring to the server virtualization software manual, and then perform the operation again.

When error_number is "809" [Citrix Xen] [OVM for x86 3.x]: The device nodes specified during configuration changes are already used for CD-ROMs or Raw disks.
After specifying different device nodes, change the configuration again.

When error_number is "855"

[Solaris Zones]

When "VM guest disk(diskpath) already exists." is displayed for detail
The disk diskpath, which is to be allocated to the VM guest, already exists. Delete the disk displayed in diskpath from the VM host, and then perform the operation again.

If detail is displayed in the "invalid parameter:parameter:value" format: The parameter value is invalid. Perform the operation again after modifying the entered value.

If detail is "timeout occurred": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When detail is "(slot_number:assigned to another device,vmerrno=809,ip=IP_address,host= VM_host_IP_address)"

When using the guest OS customization function, the ISO file must be allocated to slot_number.

Remove the device allocated to slot_number, and then perform the operation again.

When detail is "(ftp error:Error_msg., vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

Logging-in to the FTP server has failed.

Confirm that the URL, user name, and password of the registered FTP server are correct, register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Failed to change directory.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)": The directory for storing VCD on the FTP server does not exist.
Confirm that there is a directory for storing VCD in the registered FTP server.
Register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Permission denied.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)": The user does not have permission for uploading, downloading, or deleting files on the FTP server.
Configure permission for uploading, downloading, and deleting files on the FTP server. Then perform the operation again.

When detail is "(timeout occurred while executing the customizing process.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

An error occurred while customizing the guest OS.

Check whether the customization tool has been installed on the guest OS.

If the customization tool has not been installed, install it and perform the operation again.

When the guest OS is Windows, there are the following possibilities:

An incorrect system type may have been specified during image collection.
Check whether the system type is correct, and perform the operation again.
There is a possibility that the executable frequency of sysprep (frequency at which the Windows delay time limit can be reset) is 0.
Execute the following command on the VM guest that is the source for image collection, and confirm the frequency that can be reset.
When the frequency that can be reset is 0, image collection cannot be executed. Prepare a new VM guest to use as the source for image collection.
>%systemroot%\system32\slmgr.vbs /dlv <RETURN>

When detail is one of the following:

When detail is either one of the following, if system failure occurs on the VM management software server or VM management software while creating or starting the L-Server, creating or starting of the L-Server will fail.

The "(vmware remote error,vmerrno=101,ip=IP_address)" format
The "(logout failed(remote error),vmerrno=116,ip=IP_address)" format

Make sure that the VM management software is running, and use the following procedure for restoration.

Check the resource name related to the error message above with the event log on the ROR console. The VM guest name is displayed for the resource name.
Display the VM management console, and check if the VM guest checked in step 1 exists. Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached in step 2, detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in step 2, delete it from the VM management console.
For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
Check if the VM management software can communicate with the manager. Select the VM management software in the server resource tree of the ROR console, and check if the status displayed on the main panel is "normal".
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in step 1 does not exist, create or start the L-Server again.

If detail is "operation failed:customizing vm guest (cpu settings)"

Failed to modify the CPU count/CPU performance of the VM guest.

Check the operation status, network settings, and login account information of the admin server/VM host/VM management software from the ROR console or VM management console.
The manager may not be able to communicate with the VM host/VM management software. Check the status of the manager, and after restoring communication, perform the operation again.
Check that the VM guest exists, and its operating status from the ROR console or the VM management console.
When another operation is being performed on the VM guest, wait for a while and then perform the operation again.
This operation is not possible on VM guests that are powered on. Either stop the specified VM guest or make changes to the VM guest options so that changes can be made while the power is on, and then retry.
Check the physical CPU performance of the VM host on which the VM guest is operating using the ROR console and the VM management window.
When CPU performance values for the VM host registered in a VM pool and for the VM host registered in VM management software differ, refer to "3.10 Migration of a Virtual L-Server between Servers or Modification of Specifications Fails." in "Troubleshooting".
When an operation for a powered on L-Server fails, the specified value might not have been correct.
Check the cause of the error on the VM host/VM management software from the VM management console.
If the cause was specification of an incorrect value, specify the correct value and then perform the operation.
When using VMware vSphere 6.7, the error may have been caused by a known issue of VMware.
If the guest OS is Windows, check whether Virtualization Based Security (VBS) is enabled.
If Virtualization Based Security (VBS) is enabled, take corrective action referring to the release notes of VMware vSphere 6.7.

If no problems are found when checking the above, check the cause of the error on the VM host/VM management software from the VM management console. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.

If detail is "operation failed:customizing vm guest (memory settings)": Failed to modify the memory size of the VM guest.
Refer to "If detail is "operation failed:customizing vm guest (cpu settings)"".

If detail is "operation failed:customizing vm guest (properties settings)":: Failed to modify the name or OS type of the VM guest.
Refer to "If detail is "operation failed:customizing vm guest (cpu settings)"".

When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243] is displayed in the system event log: For the corrective action, refer to "13.1 When the Desktop Heap is Exhausted" in "Troubleshooting".

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67395

FJSVrcx:ERROR:67395:image operation failed. detail

[Cloud Edition]

Description

Image processing failed.

Corrective Action

Take corrective action for the content displayed for detail.

If detail is "(Disk copy failed. No space left on disk[LUN information], ip = VM_host_IP_address)"
The disk copy operation failed as the size of the disk specified as the copy destination is smaller, relative to the size of the cloning image. Specify a disk with larger disk space than the size of the cloning image.
If detail is "(Disk copy failed. No such disk[LUN information], ip = VM_host_IP_address)"
The disk copy operation failed as the disk specified by VM host cannot be found.
Check the connection between the VM host and storage so that the disk can be accessed by the VM host.
If detail is"(Disk copy failed. from [LUN information] to [LUN information], ip = VM_host_ip_address)"
The copy operation to the specified disk failed. During the copy operation, access to storage from the VM host may have been rejected. Check the connection between the VM host and storage.

67397

FJSVrcx:ERROR:67397:failed to create image. detail=detail

[Cloud Edition]

Description

Failed to collect the image of the VM guest.
Take corrective action for the content displayed for detail.

Corrective Action

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format

When error_number is "6", "7", "8", or "9": Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".

When error_number is "15": The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.

When error_number is "17"

A VM guest was not found. Check the following:

Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted.
Check whether the VM guest is set to be moved when its power status is changed using the VM management console.

When error_number is "19": There is no target operation image on server virtualization software.
Perform the operation again after checking that there are no differences between image information on the manager and snapshot information on the server virtualization software.

When error_number is "99": Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.

When error_number is "100", "115", or "178": The login account information for the VM management software entered during registration may not have the required privileges.
Check the granted authority using the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

When error_number is "101", "110", "111", "112", "114", "116", "148", "181", or "263": Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.

When error_number is "104"

Make sure that the manager is running, and use the following procedure for restoration:

Check the resource name related to the error message above with the event log on the ROR console.
The image name is displayed for the resource name.
Wait until a "Message number 21161" containing the image name confirmed in step 1 is output in the event log.
This message displays the image name and generation.
Display the VM management console and check if the image of Image_name@Version exists.
If there was an image in step 3, delete it from the VM management console.
For details on how to delete images, refer to the server virtualization software manual.
Wait until a "Message number 21162" containing the image name deleted in step 4 is output in the event log.
After that, perform the collection of the image again.

[KVM]

When detail is "Requested operation is not valid: Disk 'diskpath' does not support snapshotting"
The snapshot function is not supported in diskpath.
The snapshot of an L-Server connected only with a disk resource with the disk type "Virtual Disk" can be collected.
Delete the disk resource with the disk type "Raw Disk", and perform the operation again.
For details, refer to "8.6.9 Advisory Notes for RHEL-KVM Usage" in the "Setup Guide CE".

When error_number is "104", "105", "135", "136", "147", "178", "506", "516", "518", "531", or "532 "

When the VM management software is System Center 2016 Virtual Machine Manager or later, depending on the settings for virtual machine checkpoints, collection of checkpoints may fail. In this case, perform the following operation targeting the relevant virtual machine using the management console of SCVMM, and then perform the image creation operation again.

Repair the virtual machine.
For the [Repair] option, select [Ignore].
For details on repairing virtual machines, refer to the manuals of SCVMM.
Confirm the checkpoint settings of the virtual machine.
Check whether checkpoints are enabled for the virtual machine.
For details on checkpoints, refer to the manuals of SCVMM.

[Hyper-V]
When using MAK license authentication for activation of the following guest OSs, there is a chance that an error has occurred due to the limit on execution of Sysprep.

Windows Server 2008
Windows Server 2008 R2
Windows Vista
Windows 7

For these guest OSs, Sysprep can be executed a maximum of three times.
As Sysprep is executed when collecting cloning images, it is not possible to collect cloning images or create L-Servers with images specified more than three times. When Sysprep has already been executed three times, it is not possible to collect cloning images from that L-Server.
When a template created using VM management software has been registered as a cloning image, Sysprep will also be executed when the template is created using the VM management software.

When error_number is "113": Communication with the VM management software is not possible using the login account information of the specified VM management software.
Change the entered values (user name and password) for the login account information to the correct values.

When error_number is "141", "143", "144", "145", "146", "170", "171", "172", "173", "174", "175", "176", "177", "180", or "261": An error occurred while collecting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.

When error_number is "142" or "179": Failed to collect the image because another operation was performed on the target VM guest. Perform the operation again after waiting a while.

When error_number is "400": Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.

When error_number is "500" or "602": Check if the specified library server has been started.
Check if the specified library server can perform name resolution.
Check the firewall configuration.

When error_number is "516"

During cloning image collection, if job cancellation or timeout occurs on the VM management software, cloning image collection may fail.

Use the following procedure to perform recovery.

Display the VM management console, and check if a VM guest whose name starts with "!temp_ror" exists.
If there is a VM guest that meets the condition in step 1, delete it from the VM management console.
For details on how to delete VM guests, refer to the server virtualization software manual.
Collect cloning images again.

When error_number is "529": Specify the shared volume of the cluster.
When linking a virtual machine that is not highly available, cloning images cannot be collected. This is because the virtual machine does not exist on the Cluster Shared Volume.

When error_number is "530": Check the available space on the disk.

When error_number is "534": Check if the target VM host name is correct.

When error_number is "535": Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact your network administrator.

When error_number is "548": Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

When error_number is "600"

Collection of cloning images cannot be performed from VM guests which are holding snapshots. Delete the snapshots of the specified VM guest and perform the operation again. Cloning images also cannot be collected when there are snapshots or checkpoints created by VM management software.

[Hyper-V]
When there are snapshots that have been collected using Resource Orchestrator or checkpoints created using VM management software, it is not possible to collect cloning images as VMs are operated on difference disks. For combining of difference disks, it is necessary to delete not only all snapshots collected using Resource Orchestrator, but also all checkpoints created using VM management software. Combining of the disk is automatically performed by SCVMM, but depending on the status of the VM guest the operation may take a long time, because it is only performed while the target VM guest is stopped.

When error_number is "601": This operation cannot be performed on VM guests that have not been stopped. Stop the specified VM guest and then perform the operation again.

When error_number is "619": Operations cannot be performed for VM guests using RAW disks.

When error_number is "620": Operations cannot be performed for VM guests with no system volumes.

When error_number is "642": A cloning image with the specified name already exists. Specify a new name.

When error_number is "652": The disk merge process was not completed during snapshot deletion.
Wait a couple of minutes until completion of the merge process, and then execute the command again.

When error_number is "820"

[Citrix-Xen]

When detail is "Selected device number is already used(device number=number)": The specified disk number has already been used. Release connection with the device using the disk number, and perform the operation again.

When detail is " sr name not found(sr name=SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address" or "sr type is not iso(sr name=SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address": There is a possibility a definition of the guest OS customization definition file is wrong. Confirm the content of the definition file, and perform the operation again. In addition, confirm whether the SR (storage repository) defined in the definition file exists in XenServer.

When detail is "duplicate sr name found(sr name= SR_name),vmerrno=820,ip=IP_address,host= VM_host_IP_address": Two or more SRs with the same name are registered in XenServer. Change the SR names so they do not overlap, and perform the operation again.

When detail is "timeout occurred while executing the customizing process.,vmerrno=820, ip=IP_address,host=VM_host_IP_address"

- Check whether the customizing tool has been installed on the guest OS. If the customization tool has not been installed, install it and perform the operation again.

- There is a possibility that the wrong system type was specified when the image was collected. Check whether the system type is correct, and perform the operation again.

- There is a possibility that the executable frequency of sysprep (frequency at which the Windows delay time limit can be reset) is 0. Execute the following command on the VM guest that is the source for image collection, and confirm the frequency that can be reset. When the frequency that can be reset is 0, image collection cannot be executed. Prepare a new VM guest to use as the source for image collection.

>%systemroot%\system32\slmgr.vbs /dlv <RETURN>

When detail is (PowerShell script execution error : create_image:create image failed. See details in the job result in System Center Virtual Machine Manager.,vmerrno=518,ip=IP_address,host=VM_host_IP_address)

Make sure that the manager is running, and use the following procedure for restoration:

Check the resource name related to the error message above with the event log on the ROR console.
The image name is displayed for the resource name.
Wait until a "Message number 21161" containing the image name confirmed in step 1 is output in the event log.
This message displays the image name and generation.
Display the VM management console and check if the image of Image_name@Version exists.
If there was an image in step 3, delete it from the VM management console.
For details on how to delete images, refer to the server virtualization software manual.
Wait until a "Message number 21162" containing the image name deleted in step 4 is output in the event log.
After that, perform the collection of the image again.

When detail is "(slot_number:assigned to another device,vmerrno=809,ip=IP_address,host= VM_host_IP_address)"

When using the guest OS customization function, the ISO file must be allocated to slot_number.

Remove the device allocated to slot_number, and then perform the operation again.

When detail is "(repositoryId: repository not found,vmerrno=244,ip=IP_address,host= VM_host_IP_address)": An error occurred while customizing the guest OS.
There may be incorrect definitions in the guest OS customization definition file (os_customize_ovmx86.rcxprop).
Confirm the content of the definition file, and perform the operation again. In addition, confirm whether the SR (storage repository) defined in the definition file exists in OVM for x86 3.x.

When detail is "(ftp error:Error_msg., vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

Logging-in to the FTP server has failed.

Confirm that the URL, user name, and password of the registered FTP server are correct, register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Failed to change directory.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)": The directory for storing VCD on the FTP server does not exist.
Confirm that there is a directory for storing VCD in the registered FTP server.
Register the FTP server again, and then perform the operation again.

When detail is "(ftp error: 550 Permission denied.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)": The user does not have permission for uploading, downloading, or deleting files on the FTP server.
Configure permission for uploading, downloading, and deleting files on the FTP server. Then perform the operation again.

When detail is "(timeout occurred while executing the customizing process.,vmerrno=820,ip=IP_address,host=VM_host_IP_address)"

An error occurred while customizing the guest OS.

Check whether the customization tool has been installed on the guest OS.

If the customization tool has not been installed, install it and perform the operation again.

When the guest OS is Windows, there are the following possibilities:

An incorrect system type may have been specified during image collection.
Check whether the system type is correct, and perform the operation again.
There is a possibility that the executable frequency of sysprep (frequency at which the Windows delay time limit can be reset) is 0.
Execute the following command on the VM guest that is the source for image collection, and confirm the frequency that can be reset.
When the frequency that can be reset is 0, image collection cannot be executed. Prepare a new VM guest to use as the source for image collection.
>%systemroot%\system32\slmgr.vbs /dlv <RETURN>

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67398

FJSVrcx:ERROR:67398:failed to delete image. detail=detail

[Cloud Edition]

Description

Failed to delete the VM guest image.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "17"
  The image could not be found. Click [Update] on the image list screen of the ROR console to refresh the screen, and check whether the image has been deleted.
- When error_number is "19", "503", or "504"
  There is no target operation image on VM management software.
  Perform the operation again after checking that there are no differences between image information on Resource Orchestrator and the VM management software.
- When error_number is "99"
  Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
- When error_number is "100", "115", "147", or "260"
  The login account information for the VM management software entered during registration may not have the required privileges.
  Check the granted authority using the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", "116", "148", or "263"
  Communication between the admin server and the VM host or VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "104", "105", "135", "136", "505", or "507"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
  [VMware]
  - When detail is "snapshot snapshot_name:task result timeout,vmerrno=105,ip=IP_address"
    The snapshot deletion process has not been completed within the prescribed time of Resource Orchestrator.
    In this case, as consolidation of snapshots is necessary, the status of the virtual L-Servers that have the corresponding snapshots may become "warning".
    Refer to the VMware web site and consolidate the snapshots.
    URL: https://kb.vmware.com/kb/2003638
- When error_number is "113"
  Communication with the VM management software is not possible using the login account information of the specified VM management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "261"
  An error occurred while deleting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "400" [Citrix Xen] [OVM for x86 3.x]
  Processing of a VM host remote command failed. Check the operation status and network settings of the VM host.
  If nothing happens when the command is executed on the VM host, there is a problem with the VM host. Resolve the problem with the VM host, and then perform the operation.
- When error_number is "544"
  Obtaining the information of the VHD file, which is a related file of the target image to be deleted, failed. Use System Center Virtual Machine Manager to check that the status of the shared library is normal. After waiting for a short time, perform the operation again.
- When error_number is "545"
  Deletion of the related files of the target image to be deleted failed. Check the result of the job using System Center Virtual Machine Manager.
- When error_number is "548"
  Calling of the PowerShell module of VM management software has failed. There may be a problem with installation of SCVMM. Check that SCVMM has been configured properly.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.

67399

FJSVrcx:ERROR:67399:failed to deploy image. detail=detail

[Cloud Edition]

Description

Failed to deploy the cloning image of the VM guest.

Corrective Action

Take corrective action for the content displayed for detail.

When detail is "(Message,vmerrno=error_number,ip=IP_address)"
An error has occurred in control of the VM host or VM management software from IP_address. Take corrective action based on error_number.
- When error_number is "6", "7", "8", or "9"
  Make sure that the manager is running. If the manager has been stopped, start it and perform the operation again.
  For details on how to check the running state of the manager and how to start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
- When error_number is "15"
  The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
- When error_number is "17"
  The VM guest/image could not be found. Check the following:
  - Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM guest has been deleted. Click [Update] on the cloning image list screen of the ROR console to refresh the screen, and check whether the image has been deleted.
  - Check whether the VM guest is set to be moved when its power status is changed using the VM management console.
- When error_number is "99"
  Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
- When error_number is "100", "115", "178", "260", "337", or "381"
  The login account information for the VM management software entered during registration may not have the required privileges.
  Check the granted authority using the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
  For details, refer to "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- When error_number is "101", "110", "111", "112", "114", "116", "181", "263", "341", or "382 "
  Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the admin server, VM host, and VM management software.
- When error_number is "104", "105", "135", or "136"
  Processing of VM host or VM management software tasks failed. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
- When error_number is "113"
  Communication with the VM management software is not possible using the login account information of the specified VM management software.
  Change the entered values (user name and password) for the login account information to the correct values.
- When error_number is "170", "171", "172", "173", "174", "175", "176", "177", or "180"
  An error occurred while deploying the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "179"
  Failed to deploy the image. The requested process could not be executed because the VM guest/image is being used by another process.
  Check whether the VM guest/image is being used by another process from the VM management software.
- When error_number is "261"
  An error occurred while deleting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "262"
  Failed to delete the VM guest. VM guests cannot be deleted while their power is ON. Check the power state of the VM guest.
- When error_number is "330", "332", "333", "334", "336", "340", "342", or "380"
  Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
- When error_number is "338"
  Failed to modify the configuration because another operation was performed on the created VM guest or the destination VM guest for deployment. Perform the operation again after waiting a while.
- When error_number is "339"
  The total number of devices for the destination VM guest for deployment and the image to deploy is too great. Perform the operation again after decreasing the numbers of disks or NIC in the image to deploy or the destination VM guest for deployment.

If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.