This appendix explains the messages output or displayed by Resource Orchestrator.
When messages other than the following are output, refer to the "ServerView Resource Coordinator VE Messages".
[Description]
The resource displayed in type has been detected.
When "VMguest" is displayed for type:
The server name of the VM guest is displayed in obj.
When "cloning image" is displayed for type:
The name and version of the cloning image is displayed in obj.
When "snapshot image" is displayed for type:
The name and version of the snapshot is displayed in obj.
When "vstorage" is displayed for type:
The name of the virtual storage resource is displayed in obj.
When "storage" is displayed for type:
The resource name of the physical storage unit is displayed in obj.
[Corrective Action]
No action is necessary.
[Description]
The resource displayed in type is no longer being managed by Resource Orchestrator.
When "VMguest" is displayed for type:
The server name of the VM guest is displayed in obj.
When "cloning image" is displayed for type:
The name and version of the cloning image is displayed in obj.
When "snapshot image" is displayed for type:
The name and version of the snapshot is displayed in obj.
When "vstorage" is displayed for type:
The name of the virtual storage resource is displayed in obj.
When "storage" is displayed for type:
The resource name of the physical storage unit is displayed in obj.
[Corrective Action]
No action is necessary.
[Description]
The virtual switch name on the server server is used.
[Corrective Action]
No action is necessary.
[Description]
The virtual network name on the server server is used.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Corrective Action]
No action is necessary.
[Description]
The power of the L-Server server_name has not been stopped.
The name of the L-Server is displayed in server_name.
[Corrective Action]
Stop the power of the L-Server. Then perform the operation again.
[Description]
The I/O device used for allocation of the server profile on the server server_name was not found.
When creating an L-Server with the server type "Physical", the server name selected when creating the L-Server will be displayed in server_name.
[Corrective Action]
Please mount an FC card in expansion slot 1 of the server.
[Description]
The address specified for the server server_name already exists.
An address that is the same as one already in use may have been specified.
In server_name, the name of the server is displayed.
When the specified address is that of external software, the name of the external software is displayed in external_software.
In detail, a detailed message is displayed.
[Corrective Action]
Specify an unused address resource, and perform the operation again.
When the error occurs even when an unused address resource is specified, part of the external software information may be incorrect.
Refer to the external software information, and perform the operation again after deleting any duplicated addresses.
[Description]
When external_software is VIOM
The address specified for the server server_name is outside the range that is available for use.
In server_name, the name of the server is displayed.
In detail, a detailed message is displayed.
[Corrective Action]
Please change the VIOM settings so that the address (MAC address or WWN) displayed in detail is included in the range that is available for use.
[Description]
The server profile profile_name is assigned to another server.
In profile_name, the name of the server profile is displayed.
[Corrective Action]
Delete the server profile of profile_name, and perform the operation again.
[Description]
Another server profile has been assigned to the server profile_name.
In server_name, the name of the server is displayed.
[Corrective Action]
Delete the server profile configured for the server server_name, and perform the operation again.
[Description]
Failed to delete the server profile.
In server_name, the name of the server is displayed.
In detail, a detailed message is displayed.
[Corrective Action]
Delete the server profile configured for the server server_name, and perform the operation again.
[Description]
key must be specified.
[Corrective Action]
If this message is output when creating an L-Server or importing an L-Server template, review the content of the XML file specified when operating the server, and correct the tags and values specified in key.
[Description]
template is being used by the L-Server output in obj.
If there are three or more L-Server names output in obj, only two are displayed, followed by "...".
[Corrective Action]
If you do not want to use the template template used when creating the L-Server again, perform the following operations:
Add the -force option to the command, and perform the operation again
Delete the L-Server template from the GUI
[Description]
An error occurred during the control of storage management software, so registration of the storage management software obj failed.
[Corrective Action]
When detail is "version unmatch. [version_of_the_storage_management_software]"
There is an error in the version_of_the_storage_management_software. Use a supported version.
When detail is "service is not run."
The storage management software is not operating. Start the storage management software.
When detail is "invalid storage management software name"
There is an error in the name specified for the -soft_name option. Specify the correct name.
When detail is "one or more option is short"
A required option has not been specified. Specify the required option.
When detail is "one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
When detail is "storagemgr is already registered"
The specified storage management software has already been registered. Storage management software that is already registered cannot be registered.
When detail is "ip address: invalid format"
There is an error in the specified IP address. Specify the correct IP address.
When detail is "port: invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
When detail is "port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred during control of storage management software, so changes to the configuration of the storage management software obj failed.
[Corrective Action]
When detail is "storagemgr is registered as VM management software"
This command cannot be used to make configuration changes, as storage management software has been registered as VM management software. For details on how to change configuration of VM management software, refer to the "ServerView Resource Coordinator VE Setup Guide".
When detail is "one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
When detail is "ip address: invalid format"
There is an error in the specified IP address. Specify the correct IP address.
When detail is "port: invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
When detail is "port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the control of the storage management software, so deletion of the storage management software obj failed.
[Corrective Action]
When detail is "storagemgr is registered as VM management software"
This command cannot be used for deletion as the storage management software has been registered as VM management software. For details on how to delete VM management software, refer to the "ServerView Resource Coordinator VE Setup Guide".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred during control of storage management software.
In obj, the resource name of the storage management software is displayed.
For ipaddress, the IP address of the target resource is displayed.
In %1, the internal function name is displayed.
In %2, the internal code information is displayed.
In %3, the internal detail information is displayed.
[Corrective Action]
If %2 is "13115":
Since the specified disk size is less than 20MB, creation of a volume on the storage unit failed.
Perform the operation again after modifying the disk size.
If %2 is "13062":
Since the specified disk size is larger than the available space, creation of a volume on the storage unit failed.
Perform the operation again after modifying the disk size.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in internal code information, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred during control of storage management software.
In obj, the resource name of the storage management software is displayed.
In %1, the internal function name is displayed.
In %2, the message of the storage management software is displayed.
[Corrective Action]
If %2 is "ERROR:ssmgr3419:The specified alias name has already been registered."
Creation of the L-Server failed because the alias name of the affinity group has already been defined when ETERNUS storage was created.
For details, refer to "G.17 When an L-Server is Created, "Message number 62511" is Displayed, and Creation of the L-Server Fails.".
[Description]
The specified obj is not empty.
[Corrective Action]
Perform the operation again after emptying the specified obj.
[Description]
The resource in obj1 is already used by obj2.
[Corrective Action]
When releasing registered resources from resource pools or deleting resource pools forcibly
Perform the operation again, after changing the resource so it is not used.
When an attempt is made to delete VM management software
Perform the operation again, after changing the resource so it is not used.
If an L-Server is being managed by the VM management software, the VM management software cannot be deleted.
If this message is displayed when deleting the VM management software, delete all L-Servers operating on VM hosts managed by the VM management software (obj1) to delete.
The VM host under the management of the VM management software that is to be deleted is displayed in resource. When there are multiple VM hosts, an arbitrary VM host will be displayed.
The L-Server created in resource is displayed in obj2. When there are multiple L-Servers, an arbitrary L-Server will be displayed.
When an attempt is made to delete storage management software
If an L-Server using virtual storage resource is being managed by the storage management software, the storage management software cannot be deleted.
If this message is displayed when deleting the storage management software, delete all L-Servers using virtual storage resource managed by the storage management software (obj1) for deletion.
The virtual storage resource under the management of the storage management software that is to be deleted is displayed in resource. When there are multiple virtual storage resources, an arbitrary virtual storage resource will be displayed.
The L-Server using resource is displayed in obj2. When there are multiple L-Servers, an arbitrary L-Server will be displayed.
L-Server template (When the server type is "Physical")
In this case, the following messages will be output in the event log:
When "(create)" follows after resource
The specified physical server resource is already assigned as an L-Server, or registered as a spare server.
When "(Spare)" follows after resource
The physical server resource specified as a spare server is already assigned as an L-Server, or registered as a spare server.
When "(Primary)" follows after resource
The physical server resource specified in the physical server usage change is already assigned as an L-Server, or registered as a spare server.
Specify a physical server resource or resource pool that is already registered, and perform the operation again.
When IP address is displayed in resource
The network resource of the specified IP address has already been allocated to another L-Server. Specify an unused IP address for the network resource, and perform the operation again.
[Description]
An error occurred while executing a script registered for external integration.
[Corrective Action]
If other software is integrated into Resource Orchestrator, refer to the manuals for that software and check whether script_name is registered.
If script_name is registered, refer to the manual of that software.
If the integrated software cannot be found, collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to create the virtual switch name on server server.
[Corrective Action]
Perform the action indicated in the code information.
If code is 15:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is 16:
The VM host could not be found.
Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If code is 101, 110, 111, 112, 114, or 116:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is 113:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 100 or 115:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 500 or 511:
Failed to create the virtual switch as the configuration of the physical network adapter and virtual switch of the VM host/VM management software is not capable of creating the virtual switch. Refer to "4.2.5 Network Resources", and check the configuration of the physical network adapter and virtual switch of the VM host/VM management software.
If code is 513:
Failed to create the virtual switch as the physical network adapter to connect to the virtual switch is in use. Check the network settings of the VM host/VM management software.
If code is 514 or 515:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the virtual switch name on server server.
[Corrective Action]
Perform the action indicated in the code information.
As the virtual switch name remains on the server server, check its usage status and if it is no longer necessary, delete the virtual switch from the VM management software.
If code is 15:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is 16:
The VM host could not be found.
Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If code is 101, 110, 111, 112, 114, or 116:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is 113:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 100 or 115:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 520:
Failed to delete the virtual switch. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host/VM management software.
If code is 522:
Failed to delete the virtual switch as the switch is in use. If the virtual switch is not necessary, delete the virtual switch from the VM management software.
If code is 523 or 524:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to create the virtual network name on server server.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Corrective Action]
Perform the action indicated in the code information.
If code is 15:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is 16:
The VM host could not be found.
Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If code is 101, 110, 111, 112, 114, or 116:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is 113:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 100 or 115:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 610:
Failed to create the virtual network because the virtual network name already exists. Change the virtual network name for the VM host/VM management software.
If code is 611:
Failed to create the virtual network. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If code is 613:
Failed to create the virtual network as the virtual switch to connect to the virtual network cannot be found. Check the virtual switch of the VM host/VM management software.
If code is 614 or 615:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the virtual network name on server server.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Corrective Action]
Perform the action indicated in the code information.
As the virtual network name remains on the server server, check its usage status and if it is no longer necessary, delete the virtual network from the VM management software.
If code is 15:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is 16:
The VM host could not be found.
Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If code is 101, 110, 111, 112, 114, or 116:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is 113:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 100 or 115:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If code is 620:
Failed to delete the virtual network. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host/VM management software.
If code is 622:
Failed to delete the virtual network as the virtual network being used by the VM guest. If the virtual network is not necessary, delete the virtual network from the VM management software.
If code is 623 or 624:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The virtual switch name was not found on the server server.
[Corrective Action]
Perform the operation again after restoring the target virtual switch using the VM management software.
Due to the specification of an external port for the network resource corresponding to the virtual switch, it is necessary to connect to an appropriate physical network adapter. For details, refer to "4.2.5 Network Resources".
[Description]
The virtual network name was not found on the server server.
[Corrective Action]
Perform the operation again after restoring the target virtual network using the VM management software.
When the virtual network name has the same name as a network resource, check the VLAN ID of the network resource using the GUI, and set the same VLAN ID for the virtual network.
When the virtual network name does not have the same name as a network resource, create a virtual network with the same name as the virtual network created in advance on the server server.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Description]
An attempt was made to create a virtual network name assigned with vlanid1; however, a virtual network name assigned with vlanid2 already exists.
[Corrective Action]
Perform the operation again after deleting the previously created virtual network name assigned with vlanid2, or changing the name of the virtual network on registered VM host server.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Description]
There are multiple virtual networks assigned with vlanid.
[Corrective Action]
Change the virtual network and vlanid combinations so that they are unique between the registered VM hosts.
If the target server is a VMware server:
The virtual network indicates a port group on the virtual switch.
[Description]
An error occurred while creating obj. obj has not been created.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while deleting obj. obj has not been deleted.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while modifying the information of obj. The information of obj has not been modified.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while moving obj. obj has not been moved.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while registering obj. obj has not been registered.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while modifying the configuration of obj. The configuration of obj has not been modified.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while moving obj between servers. obj has not been moved.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while collecting the snapshot image. The snapshot image has not been collected.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while restoring the snapshot image. The snapshot image has not been restored.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while importing obj. obj has not been imported.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while unregistering obj. obj has not been unregistered.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
Registration failed as there is already a registered user with the same name.
[Corrective Action]
Enter a user name that has not been registered, and register it.
[Description]
Export to the file specified for file_name failed.
[Corrective Action]
After confirming the path to the specified file name, perform the operation again.
[Description]
The process was canceled due to one of the following reasons:
The value for item in a configuration definition file, L-Server XML file, L-Server template XML file, or the [Create an L-Server] dialog has a formatting error
An invalid character has been used
There is no value set
One of the following is displayed in item:
Type
operation
Key value of the resource definition information
A tag or attribute name of the L-Server XML file
A tag or attribute name of the L-Server template XML file
A key value in the [Create an L-Server]
[Corrective Action]
Perform the operation again after checking the content displayed in item, and resolving the cause of the error.
Type
If you imported a configuration definition file in the RCXCSV V2.0 format:
An invalid value is specified in the section name.
Correct the definitions in the configuration definition file.
If you imported a configuration definition file in the RCXCSV V1.0 format:
Something other than Chassis, EtherSwitch, or ServerBlade is specified for the resource type.
Correct the definitions in the configuration definition file.
operation
A value other than "new", "change", or a hyphen ("-") is specified in the operation field, or there is a mistake in the operation area of the section header.
Correct the definitions in the configuration definition file.
Key value of the resource definition information
An invalid value is specified for the displayed key, or there is a mistake in the displayed key value in the section header.
Correct the definitions in the configuration definition file.
For details on the values that can be specified for item, refer to the "ServerView Resource Coordinator VE Setup Guide".
A tag or attribute name of the L-Server XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the L-Server XML file and correcting the definition.
A tag or attribute name of the L-Server template XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the XML file of the L-Server template and correcting the definition.
A key value in the [Create an L-Server]
Perform the operation again after correcting the value corresponding to the displayed key value.
When IP address is displayed in value
An IP address outside the range that can be allocated to the network resource has been specified.
Specify an unused IP address for the network resource, and perform the operation again.
[Description]
The process was canceled because the specified resource value is not registered.
The resource value may not be included in the access scope of the user or user group that performed the operation.
When value is "image key = xxx"
The process was canceled because the registered cloning image was deleted due to deletion of a host from VMware vCenter Server.
When "(create)" follows after value
The process was canceled because one of the following applies to the specified physical server:
The specified physical server does not exist.
The specified physical server is not registered in the resource pool.
The specified physical server is already assigned as an L-Server.
The specified physical server is already assigned as a spare server.
The physical server resource does not exist in the resource pool.
When "(Spare)" follows after value
The process was canceled as the resource specified as a spare server does not exist.
When "(Primary)" follows after value
The process was canceled as the resource specified in the physical server usage change does not exist.
The specified physical server does not exist.
The specified physical resource pool does not exist.
The physical server resource does not exist in the specified resource pool.
[Corrective Action]
You cannot modify by specifying an unregistered resource name.
Perform the operation again after specifying a resource name that is already registered.
If you have specified a resource name that is already registered, there is a mistake in the key value of the resource name in the section header. Perform the operation again after correcting the configuration definition file.
To register new resource information with the specified resource name, change the operation to "new".
If "image key = xxxx" is displayed for value, perform the operation again after restoring the deleted cloning image and using a command to modify the L-Server configuration. When modifying the L-Server configuration, set an appropriate value in the ServerImageLink tag.
Perform the operation again after setting the access scope of resources.
[Description]
The process was aborted as a file with an extension that is not the target of operation was specified.
[Corrective Action]
Specify a file with an extension that is the target of operation, and perform the operation again.
[Description]
The specified file already exists.
[Corrective Action]
Change the file name and perform the operation again.
[Description]
The resource that matches obj could not be found.
When creating an L-Server with the server type "Physical"
Failed to configure the IP address of the public LAN.
There are the following cases:
When more NICs than the physical server contains have been specified
The network (NIC) specified when creating the L-Server exceeds the number of NICs of the physical server.
When the drivers of cloning images are not the latest.
When a number exceeding the number of NICs has not been specified, and the cloning image specified when creating the L-Server was Windows, the drivers of the cloning image may not be the latest.
The number displayed as the index is the same number as the detailed display of the L-Server.
[Corrective Action]
Review the specified conditions.
When creating an L-Server with the server type "Physical"
When more NICs than the physical server contains have been specified
Check that the network (NIC) specified when creating the L-Server is smaller than the number of NICs of the physical server.
Change the network settings and perform the operation again.
When the drivers of cloning images are not the latest.
Delete the created L-Server.
Update the drivers of the cloning image specified when creating the L-Server, and create the cloning image again.
Create the L-Server again after specifying the re-created cloning image.
[Description]
The specified value is out of range.
The value specified for value is output in "XML tag (specified value, range)" or "XML key (specified value, range) server/free/remain amount of ip address/remain amount of MAC address/remain amount of WWN address " format.
[Corrective Action]
Perform the operation again after correcting the specified value.
When value is one of the following, perform corrective action according to the content:
For "XML key (specified value, range) server":
Perform the operation again after checking the hardware configuration (CPU, memory) of the VM host on which the L-Server is located using the GUI.
For "XML key (specified value, range) free":
Perform the operation again after checking the available resources (CPU, memory) of the VM host on which the L-Server is located, and securing sufficient resources.
For "XML key (specified value, range) remain amount of ip address/remain amount of MAC address/remain amount of WWN address", there may are the following possibilities.
When using an L-Server with the server type "Physical", the specified NIC number exceeds the upper limit of the supported number
The specified IP addresses, MAC addresses, and WWNs do not exist in the resource pool
There are no vacant addresses in the resource pools of IP addresses, MAC addresses, and WWNs
Perform the operation again after reviewing the values corresponding to the displayed IP addresses, MAC addresses, and WWNs in the L-Server XML file and correcting their definitions. Add the IP addresses, MAC addresses, and WWNs that are necessary the for resource pool.
[Description]
The format of the specified value, or the content of the XML specified when performing the following is not correct:
Creating an L-Server
Modifying an L-Server
Importing an L-Server template
In value, the following information is output:
XML_tag_name
Folder XML
L-Server XML
L-Server Template XML
Network XML
User XML
UserGroup XML
[Corrective Action]
Perform the operation again after correcting the specified value or the content of the XML file.
For details on the XML definition file, refer to "Appendix H XML".
[Description]
There is an error in the file format specified for filename.
[Corrective Action]
Check the specified file format.
When "activation.dat" is displayed in filename, check the format of the license information definition file referring to the information regarding collection of cloning images in the "ServerView Resource Coordinator VE Setup Guide".
When "image_admin_hyperv.rcxprop" or "image_admin_hyperv_user_group_name.rcxprop" is displayed in filename, check the specified file format referring to "D.5 [OS] Tab".
[Description]
The process was canceled as the target file was not found.
[Corrective Action]
Specify a file as the target of operation, and perform the operation again.
[Description]
If file_name is a resource name, no permission has been granted for the specified resource.
If file_name is a file name, no access is available to file name of Resource Orchestrator.
[Corrective Action]
If file_name is a resource name, perform the operation as a user with permission for the specified resource.
If file_name is a file name, collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Refer to the explanation in "Message number 67153" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When obj is vnet
A network resource with the same VLANID has already been created.
[Corrective Action]
Refer to the corrective action described in "Message number 67153" in "ServerView Resource Coordinator VE Messages".
If obj is vnet, perform the following corrective action.
Either specify a different VLANID, or delete the existing network resource and then perform the operation again.
[Description]
The error may be the result of one of the following:
The specified object name obj does not exist
There is no object that meets the conditions
The object that met the conditions was deleted deletion processing
The specified object exists, but is not included in the access scope of the user group or user that performed the operation
If this message is displayed when a command is executed, the resource type of the specified object name may differ from the type of resource that can be specified in the arguments for the command.
In obj, the specified object name or the resource type of the specified object name is displayed.
If the object was deleted during the process, the resource type is displayed.
If a command was executed, "server OS" for a physical OS or VM host, "VM Guest" for a VM guest, and "image" or "obj(image)" for a system image or cloning image, "library share" for a shared library, is displayed for the resource type of the object name.
When the resource type is "virtual_storage", there is a chance that there is not enough available space on the virtual storage resource.
When obj begins with one of the following values, the operation has failed because the configuration of the VM host is not one that allows automatic network configuration.
SERVICE_NIC
TEAMED_NICS
INTERNAL_NIC
CHASSIS_SYSTEM
external port
nic
When obj is one of the following values, the operation has failed because there is no internal resource table.
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
When obj starts with the following value, the operation has failed because there is no virtual network on the target server of L-Server creation.
VirtualNetwork
When the target server is VMware, the virtual network indicates a port group on the virtual switch.
When obj starts with rcx-portset, the procedure of "1.8.1.2 NetApp FAS series/V series" may not have been performed.
[Corrective Action]
After checking the following for the displayed object, perform the operation again.
That the object exists
That the object meets the conditions
The access scope of the object has been set
If this message is displayed when a command is executed, perform the operation again after checking the resource type of the specified object.
[Hyper-V]
When "library share" is output in obj, there is an error in the storage destination specified for the cloning image. Check if the specified shared library is available.
If one of the following is output in obj, perform the appropriate corrective action.
"Selectable virtual_storage(condition)"
As there is a chance that the disk of the selected virtual storage has insufficient space available, check the value of available space indicated by size=%1(GB), and perform the operation again. In condition, one of the following is displayed:
size=%1, vm_host=%2
size=%1, vm_host=%2, pool=%3
size=%1, vm_host=%2, virtual_storage=%3
"Selectable vm_host(condition)"
Perform the appropriate corrective action for each condition. In condition, one of the following is displayed:
server status
Perform the operation again after checking whether a VM host in the following state exists:
Power on
Monitoring status is normal
Maintenance mode is not set
Maintenance mode has not been set for the server virtualization software
current host
When performing a migration, perform the operation again after checking whether a VM host other than the one to migrate that meets the conditions in 1. exists.
capacity
Perform the operation again after checking whether a VM host with sufficient free CPU and memory exists.
datastore
Perform the operation again after checking whether a VM host sharing a data store exists.
cluster
Check and correct the following from the management window of the server virtualization software, and perform the operation again.
That there are two or more VM hosts in the same cluster on the server virtualization software.
That the HA function is enabled in the cluster configuration of the VM hosts.
pool
Perform the operation again after checking whether a VM host that can be accessed exists, or a VM host exists in a VM pool.
unknown
Perform the operation again after checking whether a VM host that can be accessed exists, or a VM host exists in a VM pool.
vm_type
Specify or change the VM host to use 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.
For details on checking the status and free capacity of a VM host, refer to "A.4 View".
When obj starts with one of the following values, refer to "4.2.5 Network Resources" and check the configuration of the VM hosts.
SERVICE_NIC
TEAMED_NICS
INTERNAL_NIC
CHASSIS_SYSTEM
external port
nic
When obj starts with one of the following values, wait for a short while and then perform the operation again.
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
When obj starts with the following value, perform the operation again after creating a virtual network on the target server of L-Server creation.
VirtualNetwork
When the target server is VMware, the virtual network indicates a port group on the virtual switch.
When obj starts with rcx-portset, check the storage unit configuration referring to "1.8.1.2 NetApp FAS series/V series".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in obj, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Refer to the explanation in "Message number 67155" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When type is "VMHost" or "PhysicalServer"
obj has already been registered in a resource pool.
When creating an L-Server with the server type "Physical"
Failed to configure the IP address of the public LAN. The specified IP address is already in use.
[Corrective Action]
Refer to the corrective action described in "Message number 67155" in "ServerView Resource Coordinator VE Messages".
When type is "VMHost" or "PhysicalServer", take the following corrective action:
Perform the operation again after releasing registration of obj from the resource pool.
When creating an L-Server with the server type "Physical", review the specified configuration.
When using an L-Server with the server type "Physical", manually configure the IP address for the public LAN again.
Perform the operation again after deleting the L-Server with the server type "Physical", and reviewing the network configuration.
[Description]
The request could not be executed because obj contains a type object.
The object name is displayed in obj.
In type, "physical server" is displayed for physical servers, "LAN switch" is displayed for LAN switches, "VMHost" is displayed for VM hosts, "disk" is displayed for virtual disks, and "vstorage" is displayed for virtual storage.
[Corrective Action]
Perform the operation again after deleting the type object from obj.
If "disk" is displayed in type, delete the L-Server using the disk resource created from the virtual storage resource displayed in obj.
If "vstorage" is displayed in type, delete the L-Server using the virtual storage resource created under the physical storage unit resource displayed in obj.
[Description]
There is no disk in the VM guest specified for cloning image collection.
If you omit specifying the storage location when collecting a cloning image for a VM guest, it will be stored in the same location as the disk of the VM guest, but in this case the storage location could not be determined because the VM guest does not have a disk.
[Corrective Action]
Perform the operation again after specifying the location to store the cloning image.
[Description]
The request could not be executed because obj is in the status status.
One of the following is displayed in status:
normal
warning
unknown
stop
error
fatal
power-on
power-off
not belonging to any storage pool
not accessible
not enough free space
"power-on" refers to when the power of the server is on.
"power-off" refers to when the power of the server is off.
"not belonging to any storage pool" refers to when the specified virtual storage resource is not registered in a storage pool.
"not accessible" refers to when no access is available from the specified VM host.
"not enough free space" refers to when there is insufficient disk space.
[Corrective Action]
Check the necessary requirements for the obj operation, and fulfill them. Perform the operation again after fulfilling the requirements.
[Description]
Refer to the explanation in "Message number 67182" in "ServerView Resource Coordinator VE Messages".
However, the following is added to type for Resource Orchestrator:
resource type
VMType
OSType
[Corrective Action]
Refer to the corrective action described in "Message number 67182" in "ServerView Resource Coordinator VE Messages".
Also, perform the following corrective action depending on the type value:
If "resource type" is displayed:
Check the resource pool type of obj1 and the resource type of obj2, and perform the operation again after specifying a suitable combination of resource pool and resource.
For details on resource pool types and the resources that can be stored, refer to "Table 1.2 Resource Pool Types" in "1.2.1 Resource Pools".
For VMType
Check the VM type of the resource obj1 and the VM type of the resource obj2, specify resources with the same VM type and then perform the operation again.
For OSType
Check the OS type of the L-Server and the images specified in XML, specify resources with the same OS type, and then perform the operation again.
[Description]
An error occurred while communicating with target.
[Corrective Action]
Refer to the explanation in "Message number 67192" in "ServerView Resource Coordinator VE Messages".
[Description]
The requested process cannot be performed as another process is already being performed.
[Corrective Action]
Wait for a short while and then repeat the operation.
[Description]
Either there is no system image of the managed server, or the specified version of the system image was not found. Or there is no snapshot of the managed server, or the specified version of the snapshot was not found.
[Corrective Action]
Check whether there is a system image or snapshot of the relevant managed server.
If an incorrect version was specified, specify the correct version, and perform the operation again.
There is also a chance that image files have not been synchronized. Restart the manager service referring to the information about managers in the "ServerView Resource Coordinator VE Setup Guide".
[Description]
There are no spare servers that fulfill the conditions. The specified spare server does not fulfill the following conditions.
Refer to the explanation in "Message number 67220" in "ServerView Resource Coordinator VE Messages".
When an L-Server with the server type "Physical" has been switched over
There are no physical server resources available as spare servers in the specified spare server resource pool.
[Corrective Action]
Refer to the corrective action described in "Message number 67220" in "ServerView Resource Coordinator VE Messages".
When an L-Server with the server type "Physical" has been switched over
Register an additional physical server resource in the spare server resource pool specified for the target L-Server.
[Description]
The specified option option is not supported.
Refer to the explanation in "Message number 67255" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When an L-Server with the server type "Physical" was created, "NICs.NIC.NetworkLinkfor NICIndex(num)" is displayed in option
Network resources cannot be specified for the displayed NIC.
The number displayed for NICIndex(num) is a value one lower than the number specified when creating the L-Server.
[Corrective Action]
Perform the operation again after correcting the specified option.
Refer to the corrective action described in "Message number 67255" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When an L-Server with the server type "Physical" was created, "NICs.NIC.NetworkLinkfor NICIndex(num)" is displayed in option
Change the network resource settings and perform the operation again.
[Description]
Refer to the explanation in "Message number 67280" in "ServerView Resource Coordinator VE Messages".
In detail, the following detailed information is displayed:
"power-off"
The function displayed in function cannot be used with the current power state (power-off).
"The last pool_type pool cannot be deleted."
The target resource displayed in obj cannot be deleted because it is the last resource pool of resource pool type pool_type.
"pool type mismatched"
The target resource displayed in obj cannot be registered in the resource pool because it is a resource pool type that cannot be registered.
"already exists in pool name"
The target resource displayed in obj cannot be registered in the resource pool because it is already registered in pool name.
"boot disk"
The boot disk cannot be deleted.
"invalid Redundancy"
The function displayed in function cannot be used as L-Server has been located on a VM host with a disabled HA function.
"Network pool,Address pool,and Image pool"
The target resource cannot be included when calculating the number of L-Servers creatable for each L-Server template.
"VirtualStorage[virtual storage...]","Pool[storage pool...]","VirtualStorage[virtual storage],Pool[storage pool]"
The name of the virtual storage resource is displayed in virtual storage.
The name of the storage pool name is displayed in storage pool.
For the function displayed for function, it is not possible to specify system disks and data disks with differing virtual storage or storage pools.
"vmhost[vmtype]"
In vmhost, the VM host name is displayed.
The VM type for the vmhost is displayed in vmtype.
Migration cannot be performed when the VM types of the L-Server and the VM host specified as the migrate destination are different.
"spare server"
Since the operation target resource is a spare server, registration in the server pool cannot be performed.
"some settings exist"
Registration in the server pool cannot be performed because the target operation resource already has an OS installed, or some settings such as I/O virtualization have been configured.
"VMType","Model","CPU","Memory","Policy.Positioning","NICs"
The above tabs specified in the L-Server template cannot be imported, as they are not supported.
"Not connected PhysicalServer"
Operation cannot be performed, as the physical server is not connected due to changes to physical server usage.
"VIOM"
HBA address rename settings cannot be configured for the server displayed in obj as a virtualization method has been already configured using VIOM.
"setting VIOM server profile"
In the chassis mounting the server displayed in obj, setting of VIOM is not possible because a server with a virtualization method configured using HBA address rename already exists.
"Network Parameter Auto-Configuration is enabled"
Failed to configure the IP address of the public LAN. The specified cloning images cannot be used, as RCVE network parameter settings are valid.
"Invalid target network admin LAN"
Failed to configure the IP address of the public LAN. IP addresses cannot be configured for the admin LAN.
"Target network overlaps with admin LAN"
Failed to configure the IP address of the public LAN. The same network as the admin LAN cannot be configured for the public LAN.
"Invalid agent version"
Failed to configure the IP address of the public LAN. As an agent of a version earlier than ServerView Resource Orchestrator V2.2.1 has been installed, it is not possible to configure a public LAN IP address on the specified cloning image.
When creating an L-Server with the server type "Physical", the IP address cannot be automatically configured if specifying a Red Hat Enterprise Linux image.
When using the created L-Server, manually configure the public LAN IP address.
"Not Virtual Machine" or "Physical Server"
When the L-Server type is "Physical", use is not possible.
[Corrective Action]
The message was displayed because you are trying to use a function that is not supported by obj, or a function that cannot be used because the status is invalid. No action is necessary.
[Description]
Refer to the explanation in "Message number 67295" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When registering resources to resource pools
obj has already been registered in a resource pool.
[Corrective Action]
Refer to the corrective action described in "Message number 67295" in "ServerView Resource Coordinator VE Messages".
If obj has already been registered in a resource pool, it is displayed because currently registered resources cannot be registered. No action is necessary.
[Description]
An error occurred while performing with target power control.
[Corrective Action]
If "duplicate resource name" is displayed in detail:
The power state of the VM guest cannot be controlled because multiple VM names on the VM host conflict. Change the names so that they differ because there is an error in the VM host settings.
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 16 is displayed:
The VM host could not be found. The error may be the result of one of the following:
Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
[Hyper-V]
Hyper-V may not be installed, or the role may not be enabled.
Check whether Hyper-V is installed and the role is enabled.
If error_number 17 is displayed:
The VM guest could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest has been deleted.
Also, check whether the VM guest is set to be moved when its power state changes from the VM management console.
If error_number 101, 110, 111, 112, 114, or 116 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 113 is displayed:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on the entered values for the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If error_number 100 or 115 is displayed:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on the entered values for the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If error_number 104, 105, 135, or 136 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If error_number 122 is displayed:
Perform one of the following corrective actions:
The VM maintenance mode is set for the VM host. Perform the operation again after disabling the VM maintenance mode for the VM host.
Operation cannot be performed with the current power state. Check the power state of the VM guest.
If error_number 123 is displayed:
The error may be the result of one of the following:
The necessary power control settings for the VM guest may not have been configured. For details on the necessary power control settings for the VM guest, refer to the configuration requirements section of the "ServerView Resource Coordinator VE Setup Guide".
The software required for power control on the VM guest may not have been started. Perform the operation again after referring to the server virtualization software manual and checking whether the required software has been started.
If error_number 124 is displayed:
The error may be the result of one of the following:
The necessary power control settings for the VM guest may not have been configured.
Check whether the necessary power control settings for the VM guest have been configured. If the settings have not been configured, perform the operation again after configuring the necessary settings.
For details on the necessary power control settings for the VM guest, refer to the configuration requirements section of the "ServerView Resource Coordinator VE Setup Guide".
You may not have the required licenses for operation of the VM host/VM management software.
Check the license status from the VM management software.
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on the entered values for the login account information, refer to the changing VM host login account information section or the changing VM management software settings section of the "ServerView Resource Coordinator VE Setup Guide".
If error_number 125 is displayed:
The VM host is processing another task. Perform the operation again after checking whether other clients are performing operations simultaneously.
If error_number 127 is displayed:
Power control operation of the VM guest failed. The error may be the result of one of the following:
Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
[Hyper-V]
Make sure that the OS is running on the virtual machine. Perform the operation again after starting the OS. If an OS is not installed, install an OS on the virtual machine.
If error_number 400 is displayed:
The remote command processing of the VM host failed.
Check the operation status and network settings of the VM host. If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Information could not be obtained from a VM host.
In vmhost, the VM host name is displayed.
In detail, the following detailed information is displayed:
OS list
The list information of operating systems that can be specified could not be retrieved when creating a VM guest.
[Corrective Action]
Perform the corrective action according to the detailed information.
OS list
Refer to the management screen of the server virtualization software, and check whether the VM host displayed in vmhost is set to the VM maintenance mode. If the VM host is set to the VM maintenance mode, disable the maintenance mode.
[Description]
Failed to restore a VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 17 is displayed:
The VM guest/image could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest/image has been deleted.
If error_number 19 is displayed:
The image could not be found. Wait for around three minutes and then repeat the operation.
If error_number 101, 110, 111, 112, 114, 116, or 148 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 100 or 115 is displayed:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 104, 105, 135, 136, or 508 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
If error_number 113 is displayed:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 141, 143, 144, 145, 146, or 147 is displayed:
The VM guest could not be restored using an image. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 142 is displayed:
Failed to restore an image because another operation was performed on the VM guest to restore. Perform the operation again after waiting a while.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
There may be an error in the configuration file for communication with the destination target.
[Corrective Action]
When target is "storage unit", refer to "4.2.4 Storage Resources" and correctly describe the FC-CA port combination definition file of the ETERNUS storage.
If target is something other than the above, collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the control of the VM host, so registration of the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67359" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
[Description]
Stopping of the spare server target failed.
[Corrective Action]
Refer to the explanation in "Message number 67360" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
[Description]
An error occurred in communication with the VM host, so changing of the login account information of the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67363" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
[Description]
Setting of VM maintenance mode for the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67368" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 534 is displayed:
Check if the target VM host name is correct.
If error_number 535 is displayed:
Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact Fujitsu technical staff.
[Description]
Releasing of VM maintenance mode for the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67369" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 534 is displayed:
Check if the target VM host name is correct.
If error_number 535 is displayed:
Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact Fujitsu technical staff.
[Description]
An error occurred in the control of the VM management software, so registration of the VM management software obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67380" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 99 is displayed:
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 and network settings of the VM host/VM management software, and perform the operation again.
[Description]
An error occurred in the control of the VM management software, so changing the settings of the VM management software obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67381" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
[Description]
Migration of the VM guest vmguest failed. Server vmhost1 is the source and server vmhost2 is the destination.
[Corrective Action]
Refer to the explanation in "Message number 67385" in "ServerView Resource Coordinator VE Messages".
When using Resource Orchestrator, if detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)"format, the following may also be relevant:
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 534 is displayed:
Check if the target VM host name is correct.
If error_number 535 is displayed:
Check whether the server specified as the destination has a configuration that allows migration referring to the information about server virtualization software products in the "ServerView Resource Coordinator VE Setup Guide". Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact Fujitsu technical staff.
[Description]
The specified cloning image name image is already in use by another VM management software obj.
[Corrective Action]
Perform the operation again after specifying another cloning image name.
[Description]
Failed to create a VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 16 is displayed:
The VM host could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number 17 is displayed:
The image could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the image has been deleted.
If error_number 99 is displayed:
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 and network settings of the VM host/VM management software, and perform the operation again.
If error_number 101, 110, 111, 112, 114, 116, 181, 249, 341, or 382 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 113 is displayed:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 100, 115, 178, 337, or 381 is displayed:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 104, 105, 135, 136, 178, 509, 510, 511, 512, 513, 519, 520, 521, 531, or 532 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
If error_number 170, 171, 172, 173, 174, 175, 176, 177, 179, or 180 is displayed:
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 240, 335, or 603 is displayed:
Failed to create a VM guest because the VM guest name is already in use. Change the VM guest name or the destination VM host.
If error_number 241, 242, 244, or 332 is displayed:
Could not create a VM guest in the definition file storage location of the VM guest. Check the status of the definition file storage location of the VM guest.
If error_number 245 is displayed:
The VM guest name is invalid. Change the VM guest name.
If error_number 246 is displayed:
The specified VM host cannot create a VM guest. Change the destination VM host.
If error_number 330, 331, 333, 334, 336, 340, or 342 is displayed:
Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 338 is displayed:
Failed to modify the configuration because another operation was performed on the created VM guest. Perform the operation again after waiting a while.
If error_number 339 is displayed:
Too many devices were specified for creation in the VM guest. Perform the operation again after decreasing the numbers of disks or NIC.
If error_number 380 is displayed:
Failed to set the OS unique information for the VM guest again. Set the OS unique information for the created VM guest again.
If error_number 400 is displayed:
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If error_number 501 or 608 is displayed:
Make sure that the specified virtual network name exists on the VM host.
If error_number 503 is displayed:
There is no target operation image on VM management software.
Perform the operation again after checking that there are no differences between image information on Resource Orchestrator and the VM management software.
If error_number 514 is displayed:
After confirming if there is no trouble with the administrator account information, perform the operation again.
If error_number 515 or 607 is displayed:
Perform the operation again, after specifying a supported OS for VM host.
If error_number 534 is displayed:
Check if the target VM host name is correct.
If error_number 535 is displayed:
Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact Fujitsu technical staff.
If error_number 604 is displayed:
Specify a value smaller than the physical memory size of the VM host.
If error_number 605 is displayed:
Specify a value smaller than the number of CPU cores of the VM host.
If error_number 606 is displayed:
The number exceeds the number of available CPUs. Specify a value in the available range.
If error_number 609 is displayed:
The VLAN ID value is not in the available range of values. Specify the available range of values.
If error_number 614 is displayed:
The specified value exceeds the available CPU performance. Specify the available range of values.
If error_number 616 is displayed:
The specification format for the time zone is incorrect. Specify the correct format.
If error_number 617 is displayed:
The product ID specification format is incorrect. Specify the correct format.
If error_number 618 is displayed:
Administrator information is invalid. Specify valid information.
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 "timeout occurred" is displayed in detail:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 16 is displayed:
The VM host could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number 17 is displayed:
The VM guest could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest has been deleted.
Also, check whether the VM guest is set to be moved when its power state changes from the VM management console.
If error_number 101, 110, 111, 112, 114, 116, 263, or 341 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 113 is displayed:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 100, 115, 260, or 337 is displayed:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 104, 105, 135, 136, or 527 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
If error_number 261 is displayed:
Failed to delete the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 262 is displayed:
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 330, 331, 332, 333, 334, 335, 336, 339, 340, or 342 is displayed:
Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 338 is displayed:
Failed to modify the configuration because another operation was performed on the VM guest. Perform the operation again after waiting a while.
If error_number 400 is displayed:
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If "timeout occurred" is displayed in detail:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to modify the configuration of the VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 16 is displayed:
The VM host could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM host has been deleted.
If error_number 17 is displayed:
The VM guest could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest has been deleted.
Also, check whether the VM guest is set to be moved when its power state changes from the VM management console.
If error_number 99 is displayed:
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 and network settings of the VM host/VM management software, and perform the operation again.
If error_number 101, 110, 111, 112, 114, 116, or 341 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 113 is displayed:
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 100, 115, or 337 is displayed:
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management console. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 104, 105, 135, 136, 512, 519, 520, 521, 523, 524, 525, 526, or 528 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
Depending on the VM management software, a recovery operation may be required before performing the operation again. For details on the recovery method, refer to the manual of the VM management software.
If error_number 330, 331, 332, 333, 334, 335, 336, 339, 340, or 342 is displayed:
Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 338 is displayed:
Failed to modify the configuration because another operation was performed on the VM guest. Perform the operation again after waiting a while.
If error_number 400 is displayed:
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If error_number 501 or 608 is displayed:
Make sure that the specified virtual network name exists on the VM host.
If error_number 515 or 607 is displayed:
Select an OS supported by the VM host and then perform the operation again.
If error_number 522 is displayed:
There is no target VM guest virtual disk on VM management software.
Perform the operation again after checking that there are no differences between virtual disk information on Resource Orchestrator and the VM management software.
If error_number 533 is displayed:
There is no virtual network adapter of the target VM guest on VM management software.
Perform the operation again after checking that there are no differences between virtual network adapter information on Resource Orchestrator and the VM management software.
If error_number 604 is displayed:
Specify a value smaller than the physical memory size of the VM host.
If error_number 605 is displayed:
Specify a value smaller than the number of CPU cores of the VM host.
If error_number 606 is displayed:
The number exceeds the number of available CPUs. Specify the available range of values.
If error_number 609 is displayed:
The VLAN ID value is not in the available range of values. Specify the available range of values.
If error_number 611 is displayed:
This operation cannot be performed on VM guests that have not been stopped. Stop the specified VM guest and then perform the operation again.
If error_number 612 or 613 is displayed:
Waiting for a while, then perform the operation or check again.
If error_number 614 is displayed:
The specified value exceeds the available CPU performance. Specify the available range of values.
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 "timeout occurred" is displayed in detail:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If "operation failed:customizing vm guest (cpu settings)" is displayed in detail:
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 RC 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 the VM guest exists, and its operating status from the RC 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.
If no problems are found when checking the above, check the cause of the error on the VM host/VM management software from the VM management console. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If "operation failed:customizing vm guest (memory settings)" is displayed in detail:
Failed to modify the memory size of the VM guest.
Refer to "If "operation failed:customizing vm guest (cpu settings)" is displayed in detail".
If "operation failed:customizing vm guest (properties settings)" is displayed in detail:
Failed to modify the name or OS type of the VM guest.
Refer to "If "operation failed:customizing vm guest (cpu settings)" is displayed in detail".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to collect the image of the VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 17 is displayed:
The VM guest could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest has been deleted.
Also, check whether the VM guest is set to be moved when its power state changes from the VM management console.
If error_number 19 is displayed:
There is no target operation image on server virtualization software.
Perform the operation again after checking that there are no differences between image information on the manager and snapshot information on the server virtualization software.
If error_number 100, 115, or 178 is displayed:
The login account information for the VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 101, 110, 111, 112, 114, 116, 148, 181, or 263 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 104, 105, 135, 136, 147, 178, 506, 516, 518, 531, or 532 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
[Hyper-V]
When using MAK license authentication for activation of Windows Server 2008 guest OS's, there is a chance that an error has occurred due to the limit on execution of Sysprep. For these guest OS's, Sysprep can be executed a maximum of three times. As Sysprep is executed when collecting cloning images, it is not possible to collect cloning images or create L-Servers with images specified more than three times. When Sysprep has already been executed three times, it is not possible to collect cloning images from that L-Server.
When a template created using VM management software has been registered as a cloning image, Sysprep will also be executed when the template is created using the VM management software.
If error_number 113 is displayed:
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If error_number 141, 143, 144, 145, 146, 170, 171, 172, 173, 174, 175, 176, 177, 180, or 261 is displayed:
An error occurred while collecting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 142 or 179 is displayed:
Failed to collect the image because another operation was performed on the target VM guest. Perform the operation again after waiting a while.
If error_number 400 is displayed:
The remote command processing of the VM host failed. Check the operation status and network settings of the VM host.
If operations performed on the VM host are not executed, there is a problem with the VM host. Perform the operation again after resolving the problem with the VM host.
If error_number 500 or 602 is displayed:
Check if the specified library server has been started.
Check if the specified library server can perform name resolution.
Check the firewall configuration.
If error_number 529 is displayed:
Specify the shared volume of the cluster.
If error_number 530 is displayed:
Check the available space on the disk.
If error_number 534 is displayed:
Check if the target VM host name is correct.
If error_number 535 is displayed:
Check if the VM management server can communicate correctly with the DNS server. If this does not resolve the problem, contact Fujitsu technical staff.
If error_number 600 is displayed:
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.
If error_number 601 is displayed:
This operation cannot be performed on VM guests that have not been stopped. Stop the specified VM guest and then perform the operation again.
If error_number 619 is displayed:
Operations cannot be performed for VM guests using RAW disks.
If error_number 620 is displayed:
Operations cannot be performed for VM guests with no system volumes.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the VM guest image.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format or the "(message,vmerrno=error_number,ip=IP_address,host=VM_host_IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 17 is displayed:
The image could not be found. Click the <Update> button on the image list screen of the RC console to refresh the screen, and check whether the image has been deleted.
If error_number 19, 503, or 504 is displayed:
There is no target operation image on VM management software.
Perform the operation again after checking that there are no differences between image information on Resource Orchestrator and the VM management software.
If error_number 100, 115, 147, or 260 is displayed:
The login account information for the VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 101, 110, 111, 112, 114, 116, 148, or 263 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 104, 105, 135, 136, 505, or 507 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If error_number 113 is displayed:
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If error_number 261 is displayed:
An error occurred while deleting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to deploy the cloning image of the VM guest.
[Corrective Action]
If detail is displayed in the "(message,vmerrno=error_number,ip=IP_address)" format:
An error has occurred in the control of the VM host/VM management software for the displayed IP_address. Perform the corrective action according to the error_number.
If error_number 6, 7, 8, or 9 is displayed:
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 start the manager and how to check its running state, refer to the information about starting and stopping the manager in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 15 is displayed:
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If error_number 17 is displayed:
The VM guest/image could not be found. Select [Operation]-[Update] from the RC console menu to refresh the screen, and check whether the VM guest has been deleted. Click the <Update> button on the cloning image list screen of the RC console to refresh the screen, and check whether the image has been deleted.
Also, check whether the VM guest is set to be moved when its power state changes from the VM management console.
If error_number 100, 115, 178, 260, 337, or 381 is displayed:
The login account information for the VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM management software.
For details, refer to the "ServerView Resource Coordinator VE Setup Guide".
If error_number 101, 110, 111, 112, 114, 116, 181, 263, 341, or 382 is displayed:
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the admin server/VM host/VM management software.
If error_number 104, 105, 135, or 136 is displayed:
The task processing of the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If error_number 113 is displayed:
The specified login account information for the VM management software cannot be used to communicate with the VM management software.
Change the entered values (user name and password) for the login account information to the correct values.
If error_number 170, 171, 172, 173, 174, 175, 176, 177, or 180 is displayed:
An error occurred while deploying the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 179 is displayed:
Failed to deploy the image. The requested process could not be executed because the VM guest/image is being used by another process.
Check whether the VM guest/image is being used by another process from the VM management software.
If error_number 261 is displayed:
An error occurred while deleting the image. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 262 is displayed:
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 330, 332, 333, 334, 336, 340, 342, or 380 is displayed:
Failed to modify the VM guest. Check the cause of the error in the VM host/VM management software, and resolve the error.
If error_number 338 is displayed:
Failed to modify the configuration because another operation was performed on the created VM guest or the destination VM guest for deployment. Perform the operation again after waiting a while.
If error_number 339 is displayed:
The total number of devices for the destination VM guest for deployment and the image to deploy is too great. Perform the operation again after decreasing the numbers of disks or NIC in the image to deploy or the destination VM guest for deployment.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Either an internal error has occurred or there was a problem while loading the specified XML file during the following operations:
L-Server creation or configuration modification
Importing an L-Server template
[Corrective Action]
When this message is displayed during creation or configuration modification of an L-Server or while importing an L-Server template, check and correct the contents of the specified XML file and then perform the operation again.
In cases other than the above, contact Fujitsu technical staff.
[Description]
An error occurred in the manager command.
Refer to the explanation in "Message number 68296" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When creating an L-Server with the server type "Physical"
Deployment of the cloning image failed. The backup/restore procedure for the admin server may have been performed incorrectly.
[Corrective Action]
Refer to the corrective action described in "Message number 68296" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When creating an L-Server with the server type "Physical"
If a message not related to the above actions is output, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred while communicating with target.
[Corrective Action]
Refer to the corrective action described in "Message number 69111" in "ServerView Resource Coordinator VE Messages". Also, perform the following corrective action depending on the target value.
If the IP address of the VM management software is displayed in target, check whether or not communication with VM management software is possible.
Use a ping command, etc. to check whether there is a problem with the network environment between the admin server and the VM management software.
If a LAN cable has become disconnected, reconnect it.
If the VM management product has VM management software, check whether there is a problem with connecting to the VM management product from the VM management software.
If the IP address of the VM management software is displayed in target, perform the following corrective action depending on the detail value.
For "VMware vCenter Server communication error(virtual_storage_resource_name)"
Check the status of the virtual storage resources registered in the storage pool.
When the status is something other than "unknown", corrective action is not necessary as a communication error has occurred but recovery is complete.
When the status is "unknown", update virtual storage resources.
If the status does not change, perform the following corrective action:
Check that "VMware vCenter Server" is operating correctly on the IP address output for target.
For details on the check method, refer to the manual of the "VMware vCenter Server".
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "VMware vCenter Server communication error"
Check that VMware vCenter Server is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the VMware vCenter Server manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "System Center Virtual Machine Manager communication error(virtual_storage_resource_name)"
Check the status of the virtual storage resources registered in the storage pool.
When the status is something other than "unknown", corrective action is not necessary as a communication error has occurred but recovery is complete.
When the status is "unknown", update virtual storage resources. If the status does not change, take the following corrective action.
Check that SCVMM is operating correctly on the IP address output for target.
For details on the check method, refer to the SCVMM manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "System Center Virtual Machine Manager communication error"
Perform the following corrective actions:
Check that SCVMM is operating correctly on the IP address output for target.
For details on the check method, refer to the SCVMM manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
If the IP address of the storage management software is displayed in target, perform the following corrective actions:
The necessary settings for the storage management software may not have been completed. Check the configuration, referring to "1.8 Required Storage Unit Environment and Configuration When Using Storage Units from an L-Server on a Physical Server".
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
If the problem is still not resolved after performing the above actions, collect this message and troubleshooting data, and contact Fujitsu technical staff.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
