This section explains the 673XX message series.
[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 "D.3 Configuration" of the "Setup Guide VE", and check if the setup of the cluster service for the manager has been performed successfully.
[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
[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
[Virtual Edition]
[Description]
An error occurred during power control operation for target.
[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.
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 "15"
For the requests from the admin server, the response from VM host or VM management software 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, refer to "9.1.7 Changing VM Host Login Account Information" or "9.5 Changing VM Management Software Settings" of 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 "9.1.7 Changing VM Host Login Account Information" or "9.5 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 "D.2 Configuration Requirements" in the "Design Guide VE".
When error_number is "124"
There are the following possibilities:
The necessary power control settings for the VM guest may not have been configured.
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 "D.2 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, refer to "9.1.7 Changing VM Host Login Account Information" or "9.5 Changing VM Management Software Settings" of the "User's Guide VE".
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 that the OS of the Virtual Machine is operating. If the OS has not been installed or is not operating, start the OS and then perform the operation.
When error_number is "400"
Processing of a VM host remote command failed. Check the operating 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]
An error occurred during power control operation for target.
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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. 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.
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 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 "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.
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, refer to "C.1.4 Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" 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 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 "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.
When 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 the settings for VM guest power operation that must be performed in advance, refer to "D.2 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 "124"
There are the following possibilities:
The necessary power control settings for the VM guest may not have been configured.
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 "D.2 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 "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. Check the following:
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 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.
When error_number is "400"
Processing of a VM host remote command failed.
Check the operating 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 Containers]
Check if the disk that contains non-global zone is mounted on the global zone and can be accessed from the file system.
When 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.
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 "C.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.
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.
[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.
Restart Manager service, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" and "Operation Guide CE".
[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.
[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, "17.2 Collecting a Cloning Image" in the "User's Guide VE".
For Cloud Edition, "17.5.1 Collecting and Registering Cloning Images" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[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 details how to set the admin LAN IP address of the admin server for the module for image file operation, refer to "An Error may Occur When Performing Backup and Restore of System Images or Collection and Deployment of Cloning Images. [Physical Servers] [Hyper-V]" of "4.1 Operations for Images or Cloning Images" of the "Troubleshooting".
When "-" is displayed for ip, no values have been set.
[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 details how to set the admin LAN IP address of the admin server for the module for image file operation, refer to "An Error may Occur When Performing Backup and Restore of System Images or Collection and Deployment of Cloning Images. [Physical Servers] [Hyper-V]" of "4.1 Operations for Images or Cloning Images" of the "Troubleshooting".
If the host name cannot be resolved, review the settings concerning the resolution of host names such as the DNS.
[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]
Failure may have occurred due to excessive load on the network or the server. Perform cloning image deployment again.
Alternatively, 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.
[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" of 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.
[Description]
The cloning image image is in use.
[Corrective Action]
After the operation using the specified cloning image is completed, perform the operation again.
[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.
[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, "16.5 Deleting" in the "User's Guide VE".
For Cloud Edition, "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.
[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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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" 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 operating status and network settings of the admin server, VM host, and VM management software.
If 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" of 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.
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.
[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 how to start and stop manager, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" and "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.
[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 "B.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]
The SSL certifications of the target and manager may be different.
[Corrective Action]
For details refer to "An Error may Occur during Cloning after the Manager is Reinstalled." of "4.1 Operations for Images or Cloning Images" of the "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".
[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.
[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".
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]
Communication may have failed temporarily because there is a problem in the network environment or the load of the server target is high.
[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 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 the there is no error in the filename or content of the definition file, referring to "C.1.5 Configuration when Creating a Virtual L-Server Using VMware ESXi on Other Vendor's Servers" in the "Setup Guide CE".
If this does not resolve the problem, changing the timeout value may resolve the problem.
Collect troubleshooting information and contact Fujitsu technical staff.
[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" of 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 detail to rcxadm lanctl unset command, refer to "5.9 rcxadm lanctl" in the "Resource 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.
[Description]
Communication with the server target might not be possible or have failed temporarily because the load is high.
[Corrective Action]
Check the following "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: |
<Example: Abnormal communication>
Pinging ipaddr with 32 bytes of data: |
[Linux]
# ping the_IP_addresses_of_managed_servers <RETURN> |
<Example: Normal communication>
PING host name (ipaddr) 56(84) bytes of data. |
<Example: Abnormal communication>
PING host name (ipaddr) 56(84) bytes of data. |
Corrective Action
Check the following items:
For <Example: Normal communication>
"IP address checks"
"Firewall checks"
For <Example: Abnormal communication>
"target checks"
"Firewall checks"
"IP address checks"
"LAN network checks"
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.
Refer to "Appendix A Port List" of the "Design Guide VE" or "Design Guide CE", and assign permission for communication to the necessary ports.
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.
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.
[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" of the "Operation Guide VE" or "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.
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" of 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" of the "Design Guide CE".
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 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.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
There may be a problem with the network environment.
[Corrective Action]
Check the following "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>
Pinging ipaddr with 32 bytes of data: |
<Example: Abnormal communication>
Pinging ipaddr with 32 bytes of data: |
[Linux Manager]
# ping the_IP_addresses_of_managed_servers <RETURN> |
<Example: Normal communication>
PING host name (ipaddr) 56(84) bytes of data. |
<Example: Abnormal communication>
PING host name (ipaddr) 56(84) bytes of data. |
Corrective Action
Check the following items:
For <Example: Normal communication>
"IP address checks"
"Firewall checks"
For <Example: Abnormal communication>
"target checks"
"Firewall checks"
"IP address checks"
"LAN network checks"
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" of the "Design Guide VE".
For Cloud Edition, give the permission for communication to ports listed in "Appendix A Port List" of the "Design Guide VE".
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.
[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
For how to check, refer to "Chapter 2 Starting and Stopping Managers and Agents" of the "Operation Guide VE" or "Operation Guide CE".
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.
[Description]
An internal error has occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Virtual Edition]
[Description]
Registration of the VM host obj failed, because an error has occurred in control of 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 operating 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.
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. Check the operating 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 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.
[Corrective Action]
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
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 operating status and network settings of the VM host.
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 the Manager" in the "Operation Guide CE".
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 "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 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:
VM host doesn't running correctly
VM host's network isn't correct
Setup of Global zone isn't executed
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.
[Virtual Edition]
[Description]
Stopping of the spare server target failed.
[Corrective Action]
Take corrective action for the content displayed for detail.
"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.
[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"
Take corrective actions based on error_number, then perform the operation again.
When error_number is "15"
For the requests from the admin server, the response from VM host timed out. Check the operating 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" of the "User's Guide VE".
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 "9.1.7 Changing VM Host Login Account Information" of the "User's Guide VE".
When error_number is "104", "105", "135", or "136"
Processing of VM host tasks failed. Check the operating 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 operating status and network settings of the VM host.
When error_number is "400"
Processing of a VM host remote command failed. Check the operating 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]
The spare server cannot be used as the destination of server switchover.
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.
[Corrective Action]
Take corrective action for the content displayed for detail.
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 the Manager" 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.
"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.
"VMware maintenance mode, enter, vmerrno=error_number" or "VM maintenance mode, enter, vmerrno=error_number"
Take corrective actions based on error_number, then perform the operation again.
When error_number is "15"
For the requests from the admin server, the response from VM host timed out. Check the operating 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 "7.1.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 "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 "7.1.7 Changing VM Host Login Account Information" of 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 operating 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 operating status and network settings of the VM host.
When error_number is "400"
Processing of a VM host remote command failed. Check the operating 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]
The spare server cannot be used as the destination of server switchover.
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.
[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 operating 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" of 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 operating 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]
Refer to the explanation in "Message number 67363".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
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 the Manager" 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.
[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.
[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 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, "17.2 Collecting a Cloning Image" of the "Operation Guide VE".
For Cloud Edition, "17.5.1 Collecting and Registering Cloning Images" of the "Operation Guide CE".
[Description]
Accessing the registry failed.
[Corrective Action]
Check the following, resolve 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 setup, refer to "2.2 Agent Installation" of the "Setup Guide VE" or "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.
[Description]
command returned the result code and terminated abnormally.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Virtual Edition]
[Description]
Setting the VM host obj into VM maintenance mode failed.
[Corrective Action]
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"
For the requests from the admin server, the response from VM host or VM management software 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)"
An error has occurred in control of the VM host from IP_address. Take corrective action based on error_number.
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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"
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" of 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 "9.1.7 Changing VM Host Login Account Information" of the "User's Guide VE".
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.
[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 operating 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]
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]
Setting the VM host obj into VM maintenance mode failed.
[Corrective Action]
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"
For the requests from the admin server, the response from VM host or VM management software 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)"
An error has occurred in control of the VM host 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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 "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 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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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.
If 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 "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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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.
When error_number is "400"
Processing of a VM host remote command failed. Check the operating 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 "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.
[Virtual Edition]
[Description]
Releasing the VM host obj from VM maintenance mode failed.
[Corrective Action]
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"
For the requests from the admin server, the response from VM host or VM management software 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)"
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.
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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"
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" of 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 "9.1.7 Changing VM Host Login Account Information" of the "User's Guide VE".
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 operating 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]
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]
Releasing the VM host obj from VM maintenance mode failed.
[Corrective Action]
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"
For the requests from the admin server, the response from VM host or VM management software 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)"
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.
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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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 "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 "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" of 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 "7.1.7 Changing VM Host Login Account Information" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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 operating 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 "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.
[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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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.
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 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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If 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" of 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"
For the requests from the admin server, the response from VM host or VM management software 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.
[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]
Refer to the explanation in "Message number 67380".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
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 the Manager" 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.
[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 entered when registering the 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 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 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 the Manager" 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 entered when registering the 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 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 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.
[Virtual Edition]
[Description]
Migration of the VM guest vmguest failed. The server vmhost1 is the migration source and the server vmhost2 is the migration target.
[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 "15"
For the requests from the admin server, the response from VM host or VM management software 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"
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" or "9.5 Changing VM Management Software Settings" of 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 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.5 Changing VM Management Software Settings" of 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.
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 operating 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]
Migration of the VM guest vmguest failed. The server vmhost1 is the migration source and the server vmhost2 is the migration target.
[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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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 "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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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 "104" or "152"
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.
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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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 "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 "17.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 "C.2.11 Overcommit" or "C.3.12 Overcommit" in the "Setup Guide CE".
If 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 "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 "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 "216"
There are no VM hosts that can be used for migration. Check the operating status of the VM host.
If error_number is "400"
Processing of a VM host remote command failed. Check the operating 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]
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 "C.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_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 "Appendix D Server Virtualization Products" 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.
[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
Specified Address is already in use on obj.
[Corrective Action]
When value is image
Perform the operation again after specifying another cloning image name.
When value is Address
Specify other Address, and then perform the operation again.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "11"
[KVM]
When detail is "invalid format key:val.", the value of key is invalid. After check "val" you enterd, perform the operation again.
For how to check,refer to "C.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 "15"
For the requests from the admin server, the response from VM host or VM management software 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"
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.
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.
If 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" 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 operating status and network settings of the admin server, VM host, and VM management software.
If error_number is "104", "105", "135", "136", "178", "509", "510", "511", "512", "513", "519", "520", "521", "531", "532 ", or "550"
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.
[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 of the definition files, refer to "C.1.4Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" of 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" 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.
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.
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.
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"
Processing of a VM host remote command failed. Check the operating 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]
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.
When cloning image is Windows, take the following corrective actions depending on the content of detail. The format of detail is "command"::"error message returned by command".
"command not found"
The command is not found in the VM host.
Please check whether all the packages that a command needs are installed in VM host.
"no operating system was found on this disk"
Operating system is not found on the image disk.
This is probably caused by package libguestfs-winsupport.x86_64 is not installed in VMhost.
Please check the libguestfs-winsupport.x86_64 package is installed in VMhost.
"Packages for automatic OS setting not installed."
Packages for automatic OS setting not installed in VM host.
Check all of packages for automatic OS setting are installed in "preparation" of the "When clonig imange is Windows" of the "C.6.7 Collect Cloning Images" of the "Setup Guide CE"
"DefaultPassword registry not found."
Registry "DefaultPassword" is not found.
Check thefollowing regitory in the target L-Server for collecting clonig images.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultPassword |
Or, Check all of packages for automatic OS setting are installed in "preparation" of the "When clonig imange is Windows" of the "C.6.7 Collect Cloning Images" in the "Setup Guide CE".
"timeout occurred while executing sysprep."
There is possibility that mistakes in "preparation" of the "When clonig imange is Windows" in the "C.6.7 Collect Cloning Images" in the "Setup Guide CE" or fail to executing sysprep.
Check thefollowing regitory in the target L-Server for collecting clonig images.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultPassword |
In case of mistakes password of Administrator, perform the operation that collect cloning images after you enter Administrator" s password again.
If this does not resolve the problem, There is possibility that fail to executing sysprep.
perform the operation that collect cloning images after you enter Administrator' s password again, after check the cause of the error on sysprep.
For details, refer to the following web site.
URL: http://support.microsoft.com/ |
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.
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.
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.
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.
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 "C.1.4Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" of 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 "C.1.4Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" of 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 "C.1.4Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" of 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"
The format of the specified IP address is incorrect. Specify an IP address in the correct format.
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 "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 "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.
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 "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.
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"
For the requests from the admin server, the response from VM host or VM management software timed out. Check the operating status and network settings of the VM host or 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 "C.1.2 VM Specific Information Definition File" in "Setup Guide 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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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 "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" of 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.
If 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 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" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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.
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.
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 operating 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]
When detail is including following message
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 in VM host on which L-Server is.
After this command is succeeded, you can delete L-server.
# virsh managedsave-remove VM_guest_name <RETURN> |
Example
When vm guest name = vm_guest
# 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".
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"
For the requests from the admin server, the response from VM host or VM management software 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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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.
If 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" 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 operating status and network settings of the admin server, VM host, and VM management software.
If error_number is "104", "105", "135", "136", "512", "519", "520", "521", "523", "524", "525", "526", "528", or "550"
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" 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.
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 operating 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 "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.
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.
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, refer to "C.1.4 Configuration 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 "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 "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.
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"
For the requests from the admin server, the response from VM host or VM management software timed out. Check the operating status and network settings of the VM host or 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. 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)"".
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]
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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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.
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 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" 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 operating status and network settings of the admin server, VM host, and VM management software.
If error_number is "104", "105", "135", "136", "147", "178", "506", "516", "518", "531", or "532 "
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.
[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.
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.
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.
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 operating 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 "529"
Specify the shared volume of the cluster.
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.
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]
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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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.
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.
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" of 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.
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 "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.
[Cloud Edition]
[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 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 the Manager" in the "Operation Guide CE".
When error_number is "15"
For the requests from the admin server, the response from VM host or VM management software 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" 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 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.
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.
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.
