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 "B.3 Configuration" of the "ServerView Resource Coordinator VE Installation Guide", 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 following, resolve the problem and execute the command again.
If an error message regarding the disk or file system has been output to the system log
If a message indicating file system quota limit or insufficient space has been output to the system log
[Description]
A configuration check failed.
[Corrective Action]
Check the following, resolve the problem and execute the command again.
If an error message regarding the disk or file system has been output to the system log
[Description]
An error occurred during power control operation for target.
[Corrective Action]
Take corrective action for the content displayed for detail.
When detail is "duplicate resource name"
As several VM names are duplicated on the VM host, the power supply of VM guests cannot be controlled. Specify a different name for each VM name because there is a problem with the settings of the VM host.
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 RC 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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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"
Choose one of the following corrective actions:
The VM host has been set into VM maintenance mode. Release the VM host from VM maintenance mode, and then perform the operation.
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 "A.2 Configuration Requirements" in the "ServerView Resource Coordinator VE Setup Guide".
When error_number is "124"
There are the following possibilities:
There is a chance that settings for VM guest power operation, which must be performed in advance, have not been performed.
Check that settings for VM guest power operation have been performed in advance. If they have not been performed, make the necessary settings and then perform the operation again.
For the settings for VM guest power operation that must be performed in advance, refer to "A.2 Configuration Requirements" in the "ServerView Resource Coordinator VE Setup Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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.
[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 of the rcxadm image list command, refer to "4.1 rcxadm image" of the "ServerView Resource Coordinator VE Command Reference".
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. For details, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide" and restart the manager service.
[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 "8.2 Collecting a Cloning Image" of the "ServerView Resource Coordinator VE Setup Guide".
[Description]
The IP address ip set when installing the agent on the physical server target is invalid.
[Corrective Action]
Check if ip is the admin LAN IP address of the admin server.
If it is not the IP address of the admin server, set the admin LAN IP address of the admin server for the module for image file operation.
For the IP address settings for the module for image file operation, refer to "15.4 Image Operation Issues [Windows/Linux] [Hyper-V]" of the "ServerView Resource Coordinator VE Operation Guide".
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 that hostname is the admin server name, and the admin server IP address used on the managed server can be resolved using the server name.
If it is not the admin server name, in the IP address settings for the module for image file operation set the host name or IP address of the admin server to enable it to be resolved using the admin LAN.
For the IP address settings for the module for image file operation, refer to "15.4 Image Operation Issues [Windows/Linux] [Hyper-V]" of the "ServerView Resource Coordinator VE Operation Guide".
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 Agent 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 Agent failed.
Restart the ServerView Agent.
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.
When using the network parameter auto-configuration function, refer to "8.6.1 Operation Checks and Preparations" of the "ServerView Resource Coordinator VE Setup Guide" 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 this does not resolve the problem, collect troubleshooting information 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 "8.5 Deleting a Cloning Image" of the "ServerView Resource Coordinator VE Setup Guide", and delete excess cloning images so there are less than the maximum.
When collection of a cloning image with the same name is performed multiple times
After completing the collections performed simultaneously, perform the operation again.
[Description]
Startup of the manager has not been completed.
[Corrective Action]
Refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide", and 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 how to stop and start managers, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
If the manager has been started, wait a couple of minutes and then perform the operation again.
If this does not resolve the problem, collect troubleshooting information 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.
[Description]
The SSL certifications of the target and manager may be different.
[Corrective Action]
For check methods and corrective actions, refer to "15.7 Cloning Issues Following Manager Re-installation" of the "ServerView Resource Coordinator VE Operation Guide".
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".
[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.
[Description]
Communication may have failed temporarily because the load of the server target is high.
[Corrective Action]
Check the following:
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 "8.6 Network Parameter Auto-Configuration for Cloning Images" of the "ServerView Resource Coordinator VE Setup Guide".
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 the rcxadm lanctl unset command, refer to "8.6.3 Clearing Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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:
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 C Port List" of the "ServerView Resource Coordinator VE Setup Guide", 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 5 Starting and Stopping" of the "ServerView Resource Coordinator VE Setup Guide", and start the destination server for communication.
However, when target is the name of external software, refer to the manual of the software and start the service of the external software.
Port number checks
Refer to "Appendix C Port List" of the "ServerView Resource Coordinator VE Setup Guide", and check the port numbers of the admin server and managed servers. If there are any mistakes, change the port number to the right one.
For how to change port numbers, refer to "6.3.1.2 Changing Port Numbers" or "6.3.2.6 Changing Port Numbers" of the "ServerView Resource Coordinator VE Setup Guide".
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 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 this does not resolve the problem, collect troubleshooting information 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]
>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:
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.
In Resource Coordinator VE, give the permission for communication to ports listed in "Appendix C Port List" of the "ServerView Resource Coordinator VE Setup Guide".
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, collect troubleshooting information 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
Refer to "Chapter 5 Starting and Stopping" of the "ServerView Resource Coordinator VE Setup Guide", and start the destination server for communication.
However, when target is the name of external software, refer to the manual of the software and start the service of the external software.
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 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 this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An internal error has occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[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 RC 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 entry values (user name and password) of 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.
[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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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 switching.
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.
[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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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.
[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.
For details, refer to "8.2 Collecting a Cloning Image" of the "ServerView Resource Coordinator VE Setup Guide".
There is a license information file on target.
The content of the license information file on target is correct.
[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 "ServerView Resource Coordinator VE Installation Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
command returned the result code and terminated abnormally.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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 Coordinator VE 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.
[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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide".
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.
[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 RC 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 entry values (user name and password) of 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.
[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 RC 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 entry values (user name and password) of 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.
[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 RC 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 RC 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 entry values (user name and password) of the login account information to the correct values.
For details, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide".
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 Coordinator VE.
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.
