This section explains the 673XX message series.
[Description]
An error occurred while performing with target power control.
[Corrective Action]
Take corrective action based on the content of detail.
If 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.
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "16"
The VM host could not be found. Check the following:
Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
[Hyper-V]
Check that Hyper-V is installed and roles are enabled.
If error_number is "17"
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.
If 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 error_number is "100" or "115"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from 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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "101", "110", "111", "112", "114", or "116"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", or "136"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. Perform the operation again after resolving the problem with the VM host/VM management software.
When 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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.
Operation cannot be performed with the current power state. Check the power state of the VM guest.
If error_number is "123"
The error may be the result of one of the following:
The necessary power control settings for the VM guest may not have been configured. For details on the necessary power control settings for the VM guest, refer to "E.2 Configuration Requirements" in the "Setup 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.
If error_number is "124"
The error may be the result of one of the following:
The necessary power control settings for the VM guest may not have been configured.
Check whether the necessary power control settings for the VM guest have been configured. If the settings have not been configured, perform the operation again after configuring the necessary settings.
For details on the necessary power control settings for the VM guest, refer to "E.2 Configuration Requirements" in the "Setup Guide VE".
You may not have the required licenses for operation of the VM host/VM management software.
Check the license status from the VM management software.
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from 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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "125"
The VM host is processing another task. Perform the operation again after checking whether other clients are performing operations simultaneously.
If error_number is "127"
Power control operation of the VM guest failed. Check the following:
Check the operation status and network settings of the VM host/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. Perform the operation again after resolving the problem with the VM host/VM management software.
[Hyper-V]
Check whether or not 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.
If error_number is "400"
The remote command processing of the VM host failed.
Check the operation status and network settings of the VM host. If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If error_number is "547"
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.
If 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 "E.6.5 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.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[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.
[Description]
Failed to restore a VM guest.
[Corrective Action]
Take corrective action based on the content of detail.
If 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If 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.
If error_number is "19"
The image could not be found. Wait for around three minutes and then repeat the operation.
If 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 error_number is "100" or "115"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", or "508"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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.
If 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.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
There may be an error in the configuration file for communication with the destination target.
[Corrective Action]
Take corrective action based on the content of target.
"storage unit"
Refer to "6.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.
In other cases
Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the control of the VM host, so registration of the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67359" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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.
[Description]
Stopping of the spare server target failed.
[Corrective Action]
Refer to the explanation in "Message number 67360" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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.
[Description]
An error occurred in communication with the VM host, so changing of the login account information of the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67363" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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.
[Description]
Setting of VM maintenance mode for the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67368" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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 error_number is "534"
Check if the target VM host name is correct.
If 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.
If 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.
[Description]
Releasing of VM maintenance mode for the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67369" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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 error_number is "534"
Check if the target VM host name is correct.
If 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.
If 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.
[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.
[Description]
Connection of the VM guest obj to the VM guest tool failed.
[Corrective Action]
Take corrective action based on the content of detail.
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "16"
The VM host could not be 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.
If error_number is "17"
The VM guest could not be 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.
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "3.2.7 Changing VM Host Login Account Information" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "100", "115", or "471"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
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 "3.2.7 Changing VM Host Login Account Information" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "104", "105", "135", or "136"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
If 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"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the control of the VM management software, so registration of the VM management software obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67380" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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.
[Description]
An error occurred in the control of the VM management software, so changing the settings of the VM management software obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67381" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If 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.
[Description]
Migration of the VM guest vmguest failed. Server vmhost1 is the source and server vmhost2 is the destination.
[Corrective Action]
Refer to the explanation in "Message number 67385" in the "Messages VE".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "17"
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.
If 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 error_number is "104" or "152"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
If 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 using an environment with overcommit enabled, also refer to the advisory notes in "11.7 Migration of VM Hosts between Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on the overcommit function, refer to "E.2.7 Overcommit" or "E.3.6 Overcommit" of the "Setup Guide CE".
If error_number is "400"
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
[KVM]
When the following description is displayed in detail, check the host configuration for the live migration.
"Temporary failure in name resolution"
"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"
For details, refer to "Configuration for L-Server Live Migration" in "E.6.5 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.
If error_number is "534"
Check if the target VM host name is correct.
If error_number is "535"
Check whether the server specified as the destination has a configuration that allows migration referring to "Appendix E Server Virtualization Products" of the "Setup 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.
If 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.
[Description]
The specified cloning image name image is already in use by another VM management software obj.
[Corrective Action]
Perform the operation again after specifying another cloning image name.
[Description]
Failed to create a VM guest.
[Corrective Action]
Take corrective action based on the content of detail.
If 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "16"
The VM host could not be found. Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number is "17"
The image could not be found. Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the image has been deleted.
If 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.
If error_number is "100", "115", "178", "337", or "381"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", "178", "509", "510", "511", "512", "513", "519", "520", "521", "531", "532 ", or "550"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
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.
[Hyper-V]
If error_number is "104", and the guest OS type is Windows, the product key may be not 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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.
If 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.
If 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.
If error_number is "245"
The VM guest name is invalid. Change the VM guest name.
If error_number is "246"
The specified VM host cannot create a VM guest. Change the destination VM host.
If 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.
If 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.
If 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.
If 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.
If error_number is "400"
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
[KVM]
If "Error: LVM is not supported for VM guest." is displayed for detail, LVM cannot be used for cloning images. Use a non-LVM cloning image.
If error_number is "501" or "608"
Make sure that the specified virtual network name exists on the VM host.
If 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.
If error_number is "514"
After confirming if there is no trouble with the administrator account information, perform the operation again.
If error_number is "515" or "607"
Perform the operation again, after specifying a supported OS for VM host.
If error_number is "534"
Check if the target VM host name is correct.
If 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.
If 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.
If 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.
If 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 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.
If 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.
If 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If error_number is "606"
The number exceeds the number of available CPUs. Specify a value in the available range.
If error_number is "609"
The VLAN ID value is not in the available range of values. Specify the available range.
If 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If error_number is "616"
The specification format for the time zone is incorrect. Specify the correct format.
If error_number is "617"
The product ID specification format is incorrect. Specify the correct format.
If error_number is "618"
Administrator information is invalid. Specify valid information.
If error_number is "621"
The format of the specified IP address is incorrect. Specify an IP address in the correct format.
If 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.
If 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.
If error_number is "656"
The 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.
If 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.
If 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.
If 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 error_number is "663"
Waiting for a while, then perform the operation or check again.
If 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.
If 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.
If 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.
If 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.
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"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
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 "VM Specific Information Definition File" in "E.1.1 Definition Files" in the "Setup Guide CE".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the VM guest.
[Corrective Action]
Take corrective action based on the content of detail.
If 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "16"
The VM host could not be found. Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number is "17"
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.
If 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 error_number is "100", "115", "260", or "337"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "101", "110", "111", "112", "114", "116", "263", or "341"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", or "527"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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.
If 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.
If 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.
If 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.
If error_number is "400"
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If 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 "timeout occurred"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to modify the configuration of the VM guest.
[Corrective Action]
Take corrective action based on the content of 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 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "16"
The VM host could not be found. Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number is "17"
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.
If 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.
If 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.
If error_number is "100", "115", or "337"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", "512", "519", "520", "521", "523", "524", "525", "526", "528", or "550"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. 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.
If error_number is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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.
If 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.
If error_number is "400"
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If error_number is "501" or "608"
Make sure that the specified virtual network name exists on the VM host.
If error_number is "515" or "607"
Select an OS supported by the VM host and then perform the operation again.
If 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.
If 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.
If 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 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.
If 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.
If 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 on definition files, refer to "Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in "E.1.1 Definition Files" in the "Setup Guide CE".
If error_number is "605"
Specify a value smaller than the number of CPU cores of the VM host.
If error_number is "606"
The number exceeds the number of available CPUs. Specify the available range.
If error_number is "609"
The VLAN ID value is not in the available range of values. Specify the available range.
If 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.
If error_number is "612", "613", "663", or "664"
Wait for a while, then perform the operation or check again.
If error_number is "614"
The level exceeds that of available CPU performance. Specify the available range.
If 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 "1.3.4 rcxadm disk".
If error_number is "660"
Disks with snapshots cannot be detached. Perform the operation on disks without snapshots.
If 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.
If 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.
If 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.
If 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.
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"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
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.
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. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
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)"".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Image processing failed.
[Corrective Action]
Take corrective action based on the content of 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.
[Description]
Failed to collect the image of the VM guest.
[Corrective Action]
Take corrective action based on the content of detail.
If 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number is "17"
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.
If 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.
If 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 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 privilege status from 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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", "147", "178", "506", "516", "518", "531", or "532 "
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. Perform the operation again after resolving the problem with the VM host/VM management software.
[Hyper-V]
When using MAK license authentication for activation of Windows Server 2008 guest OS's, there is a chance that an error has occurred due to the limit on execution of Sysprep. For these guest OS's, 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.
If error_number is "113"
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If 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.
If 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.
If error_number is "400"
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If 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.
If error_number is "529"
Specify the shared volume of the cluster.
If error_number is "530"
Check the available space on the disk.
If error_number is "534"
Check if the target VM host name is correct.
If 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.
If 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 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.
If 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.
If error_number is "619"
Operations cannot be performed for VM guests using RAW disks.
If error_number is "620"
Operations cannot be performed for VM guests with no system volumes.
If error_number is "642"
A cloning image with the specified name already exists. Specify a new name.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the VM guest image.
[Corrective Action]
Take corrective action based on the content of detail.
If 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 the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If 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.
If 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.
If 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 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 privilege status from 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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If error_number is "101", "110", "111", "112", "114", "116", "148", or "263"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", "136", "505", or "507"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. Perform the operation again after resolving the problem with the VM host/VM management software.
If error_number is "113"
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If 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.
If 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.
If 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.
If 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 the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to deploy the cloning image of the VM guest.
[Corrective Action]
Take corrective action based on the content of detail.
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If 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 "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
If error_number is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If 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.
If 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 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 privilege status from 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 "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operation status and network settings of the admin server/VM host/VM management software.
If error_number is "104", "105", "135", or "136"
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/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. Perform the operation again after resolving the problem with the VM host/VM management software.
If error_number is "113"
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If 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.
If 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.
If 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.
If 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.
If 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.
If 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.
If 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 the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
