This appendix explains the messages output or displayed by Resource Orchestrator.
[Description]
The status of the type resource name has changed to status.
Status ("normal", "stop", "unknown") is displayed in status.
[Corrective Action]
Check the status status of the type resource name. If the status is "normal" or if the status changed to "stop" after an operation accompanying stopping of the resource stop, no action is necessary.
When "Disk" is displayed for type, and "unknown" is displayed for status
The disk resource may be being used for other than the managed server.
Check that there are no problems.
[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.
When "Disk" is displayed for type:
The disk resource name is displayed in obj.
[Corrective Action]
No action is necessary.
[Description]
The resource displayed in type has been migrated.
When type is "Disk"
The name of the disk that has been migrated is displayed in obj.
[Corrective Action]
No action is necessary.
[Description]
The configuration information (CPU, memory, disk, etc.) of the L-Server on obj has been updated.
"L-Server" is displayed in type.
[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.
When 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]
When deleting a network resource, the resource name corresponding to the network resource that exists on the server server was not deleted.
The resource name was manually created by a user, not automatically by Resource Orchestrator. Therefore, it is not deleted.
When "virtual switch" is displayed for resource
The resource indicates a virtual switch.
When "virtual network" is displayed for resource
If the target is a VMware server, the resource indicates a port group on the virtual switch.
In cases other than the above, the resource indicates a virtual network.
[Corrective Action]
No action is necessary.
[Description]
The directory service has been successfully configured as an external authentication function. The following cases may occur for done:
For "registered"
The directory service has been registered.
For "unregistered"
The directory service has been unregistered.
For "modified"
The directory service has been changed.
[Corrective Action]
No action is necessary.
[Description]
Refer to the explanation in "Message number 41303" in "ServerView Resource Coordinator VE Messages".
However, for Resource Orchestrator, "warning", "error", or "unknown" may be displayed for the status of the L-Server or the resources that comprise the L-Server.
[Corrective Action]
Refer to the corrective action described in "Message number 41303" in "ServerView Resource Coordinator VE Messages".
When "warning", "error", or "unknown" are displayed for status of the L-Server or the resources that comprise the L-Server, perform the following corrective action:
Identify the failure location from the RC console.
For the operation method using the RC console, refer to "Chapter 2 User Interface" of the "ServerView Resource Coordinator VE Setup Guide".
When there is resource management software on the resource, identify the failed part using the resource management software.
[Description]
During the operation for obj, part of the process function was skipped to enable continuance of the operation.
The resource name is displayed for obj.
The name of the skipped process is displayed for function.
The reason the process was not performed is displayed for cause.
[Corrective Action]
When "StorageChassisFailover" is displayed for function:
The process obj was skipped by the switchover between operating and standby storage.
When "not supported" is displayed for cause:
There are no storage unit name or volume identifiers in the disk information.
Check that the content of the replication definition file is correct.
When "mirror_definition not found" is displayed for cause:
The replication definition file corresponding to a disk registered in Resource Orchestrator does not exist.
Check that the content of the replication definition file is correct.
When "not pre_created" is displayed for cause:
The disk registered with Resource Orchestrator is not the one created in advance.
The target is the disk created in advance.
[Description]
There is an invalid value in the definition file.
The file name is displayed for file.
The details of the error are displayed for detail. When multiple errors are detected, they are displayed separated by commas (",").
When l_server.rcxprop is displayed for file, and allocate_after_create or auto_preserved is displayed for detail, the value in the [Create an L-Server] dialog or the [Modify an L-Server] dialog has not been correctly set. Therefore, an unintended value may be set.
When vnetwork_ibp.rcxprop is displayed for file, and support_ibp_mode is displayed for detail, the IBP setting values have not been set correctly.
[Corrective Action]
When the file name is l_server.rcxprop, check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive. After that, perform the following corrective actions.
When allocate_after_create is displayed for detail:
When there is no problem with the L-Server even if resources are allocated, no action is necessary.
When creating only the L-Server definition, delete the L-Server and create it again.
When auto_preserved is displayed for detail.
When the resource has been allocated to an L-Server, change the "Resource release" in the [Modify an L-Server] dialog.
When the L-Server has only a definition, change the "Resource release" in the [Modify L-Server's definition] dialog.
When changing the L-Server using the command, set the Repurpose tag, and then change the L-Server.
When the file name is vnetwork_ibp.rcxprop, check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive.
For details, refer to "F.4 Pre-setup Preparations (Network)" of the "ServerView Resource Orchestrator User's Guide".
[Description]
The recording process of the operation log failed.
[Corrective Action]
Check the following, resolve the cause of the error, and then perform the operation again.
When detail is "filesystem full"
Check the system log to see if there are error message(s) regarding the disk or file system.
Check the system log to see if there is quota limit or file system full message.
[Description]
When server is a physical server:
The external connection port of the switch specified for the network resource name and NICnumber are not connected.
When server is a VM host:
The external connection port of the switch specified in the network resource name and NICnumber used by the virtual network created by the user in advance, are not connected.
[Corrective Action]
When server is a physical server:
Check the details related to the causes of the explanations above, and specify a NIC which can be connected with the network resource.
When server is a VM host:
Check the details related to the causes of the description above, and create the virtual network again.
[Description]
An error was ignored by the option.
In detail, a detailed message is displayed.
[Corrective Action]
Check the contents in detail, and then perform the corrective actions.
[Description]
VLAN configuration for the LAN switch displayed in name has failed.
In detail, an error message that explains the root cause of the problem is output.
[Corrective Action]
The VLAN information used by the source server for switchover may be set for the LAN switch displayed in name.
Delete the VLAN information by manually operating the LAN switch when necessary.
[Description]
There is a conflict between value and the address_type of obj.
The following causes are possible:
The specified value overlaps with the address_type of obj
The value of an already registered obj is incorrect
One of the following is displayed in address_type:
IP address
MAC address
network address
One of the following is displayed in obj:
admin server
Indicates an admin server.
Resource name
Indicates a registered resource.
Subnet name
Indicate a registered subnet.
[Corrective Action]
When the specified value overlaps with the address_type of obj
Perform the operation again after correcting the specified value.
When the value of an already registered obj is incorrect
Perform the operation again after changing the value of obj.
When this message is displayed during creation of a network resource for which the Admin LAN type is set
Select [Create Resource]-[Using existing admin subnet] to create a resource.
[Description]
Refer to the explanation in "Message number 61162" in "ServerView Resource Coordinator VE Messages".
[Corrective Action]
Refer to the corrective action described in "Message number 61162" in "ServerView Resource Coordinator VE Messages".
[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 a physical L-Server, the server name selected when creating the L-Server will be displayed in server_name.
[Corrective Action]
Hardware requirements may not have been met.
For details, refer to "Table 1.27 Required Hardware" of "1.4 Hardware Environment" in the "ServerView Resource Orchestrator User's Guide".
[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 check whether or not the same address is included in the information.
If incorrect information remains, delete the information, and then perform the operation again.
When using the server as a current server, perform the following operations to set a unique address, and then perform the operation again:
Set the address resource as being outside the range
Use the current server as an L-Server
[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]
The settings for iSCSI boot differ between spare_servers and server_name.
One of the following is displayed in spare_servers and server_name:
L-Server XML
iscsi_user_group_name.rcxprop
iscsi.rcxprop
iSCSI disk resource
When spare_servers or server_name is something other than the above, refer to the explanation in "Message number 61184" in "ServerView Resource Coordinator VE Messages".
[Corrective Action]
Review the settings of spare_servers and server_name, and perform the operation again.
When spare_servers or server_name is "L-Server XML"
Review the content of the L-Server XML definition file.
For details on L-Server XML definition files, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
When spare_servers or server_name is "iscsi_user_group_name.rcxprop" or "iscsi.rcxprop"
Review the content of the iSCSI boot network definition file.
For details on iSCSI boot network definition files, refer to "5.2.5 Network Resources" of the "ServerView Resource Orchestrator User's Guide".
When spare_servers or server_name is "iSCSI disk resource"
Review the content of the definition file of the disk used for iSCSI boot.
For details on definition files of disks used for iSCSI boot, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
[Description]
service is not installed.
The following is displayed for service:
DHCP Server
[Corrective Action]
After installing service, perform the operation again.
There is also the following case for Resource Orchestrator.
When "DHCP Server" is displayed for service on a Windows manager
After installing the standard DHCP service of the OS, perform the operation again.
[Description]
The process function for obj was not executed.
The reason why function was not executed is displayed for detail.
When "failover", "failback", or "recovery" is displayed for function:
Due to the reason in detail, the process of failover, failback, or recovery using the rcxstorage command was aborted.
[Corrective Action]
When "failover", "failback", or "recovery" is displayed for function:
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The version used for the export of the configuration information and the one used for the import are different.
The version used for the export is output in ExportVersion. When the version information does not exist in the configuration information specified at import, "unknown" is output.
The version used for the import is output in ImportVersion.
[Corrective Action]
Use the same version for the export and import system.
[Description]
The format of the specified value, or the content of the XML specified when performing the following is not correct:
Import of configuration information
Detailed information is output in the format "message: error part" for detail.
When the message is "invalid MIME type":
The format of the configuration information specified at import is not in XML format.
The specified MIME type is output in the error part.
When the message is "invalid XML tag":
The format of the XML tag information of the configuration information specified at import is not correct.
The XML tag name of the incorrect format is output in the error part.
When the message is "invalid tag name":
An incorrect resource type exists in the configuration information specified at import.
The highest-level tag of the incorrect resource type is output in the error part. When multiple tag names are output, they are displayed separated by commas (",").
When the message is "lack of XML tag":
The configuration information specified at import does not contain all of the configuration information required for the resource type.
The highest-level tag of the resource type and the insufficient resource name are output in the error part. When multiple tag names are output, they are displayed separated by commas (",").
When the message is "lack of resource tag":
The resource type information of the configuration information specified at import does not contain all of the required resource information.
The highest-level tag of the resource type and the insufficient resource name are output in the error part, separated by commas (",").
When the message is "duplicate XML tag":
There are multiple highest-level tags of the same resource type in the configuration information specified at import. When importing, multiple instances of the same resource type cannot be processed.
The top-level tag of the resource type is output to the error part. When multiple tag names are output, they are displayed separated by commas (",").
[Corrective Action]
Contact Fujitsu technical staff.
[Description]
key must be specified.
[Corrective Action]
If this message is output during the following operations, check the content of the XML file specified when operating the server, and correct the tags and values specified in key.
Creating an L-Server
For details on the tags and the values, refer to "2.3 L-Servers".
When creating another L-Server using detailed L-Server information, which is output using the rcxadm lserver show command, refer to "Creating another L-Server using detailed L-Server information" of "2.3.1 For Physical L-Servers" or "2.3.2 For Virtual L-Servers".
Importing an L-Server template
For details on the tags and the values, refer to "2.2 L-Server Template".
Registration of iSCSI boot information
For details on the tags and the values, refer to "2.9 iSCSI Boot Information".
If this message is output when creating or changing a virtual L-Server, check and correct the value set in the dialog window and perform the operation again.
If this message is output when starting the virtual L-Server, check the value in the L-Server definition settings, and perform the operation again.
When "OSSetting.AdminPassword" is displayed for key
Specify the "Administrator password" on the [OS] tab.
When "OSSetting.DNSSearchPaths.DNSSearchPath" is displayed for key
Specify the "DNS Search Path" on the [OS] tab.
For more information on this value, refer to "Appendix D L-Server Parameter Details" of the "ServerView Resource Orchestrator User's Guide".
When "port group" is displayed for key
Check that there are no incomplete descriptions for the virtual bridge or VLAN ID in the virtual network definition file.
If this message is output when performing file import operations for DR, review the details of the XML specified at the operations, and add the tag and value described in key, and then perform the operation again.
[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 RC console
[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.
When detail is "command failed."
Storage management software may not be able to be used. Check whether or not storage management software is available.
In the following cases, storage management software is unavailable. Check that the preparations have been completed, referring to "3.2 Preparations for Storage Environments" in the "ServerView Resource Orchestrator User's Guide".
When the IP address for access to the storage management software specified with the -ip option is incorrect
When descriptions in the storage connection definition file are incorrect
When a security file has not been created
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 modify VM management software settings, refer to "6.3.6 Changing VM Management Software Settings" in 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.
When detail is "storagemgr is registered as iSCSI controller"
This command cannot change resources, as the disk used for iSCSI boot has been registered.
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 "6.4.5 Deleting VM Management Software" in the "ServerView Resource Coordinator VE Setup Guide".
When detail is "storagemgr is registered as iSCSI controller"
This command cannot delete resources, as the disk used for iSCSI boot has been registered.
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]
The L-Server cannot be deleted because the VM host vm_host on the L-Server server_name is registered with the VM pool pool.
[Corrective Action]
When deleting the L-Server, delete the registration of the VM host vm_host from the VM pool pool, and then perform the operation again.
[Description]
It is necessary to specify the "-allow deldisk" option when executing the command, because this operation may delete the disk contents.
The name of the L-Server or the disk is displayed for resource.
[Corrective Action]
Specify the "-allow deldisk" option for the command, and perform the operation again.
When backing up the disk contents of L-Server, perform this corrective action and then perform the operation again.
[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]
When using NetApp as storage management software
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 %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.
When using PRIMECLUSTER GDS as storage management software
When %1 is /usr/sbin/sdxvolume, and %3 contains "no enough space"
Since the specified disk size is larger than the available space, creation of a volume on the storage unit failed.
When "Permission denied" or "not privileged" is included in %3
The user specified when registering the storage management software does not have sufficient privileges to execute the command.
Change the user name for the storage management software.
For details on the command, refer to the "1.7.1 rcxadm storagemgr" in the "ServerView Resource Orchestrator Reference Guide".
When %1 is /usr/sbin/sdxvolume, and %3 contains "class closed down", or when %1 is /bin/dd, and %3 contains "No such device or address"
A failure may occur on the disk used as virtual storage.
Refer to the PRIMECLUSTER GDS manual.
When %1 is /usr/sbin/sdxvolume, and %3 contains "related to proxy volume"
In the settings of PRIMECLUSTER GDS, a proxy volume is related to a disk.
After deleting the relationship using PRIMECLUSTER GDS, perform the operation again.
When a character string beginning with "/usr/sbin/sdx" is displayed in %1
An error occurred while executing a PRIMECLUSTER GDS command.
Refer to the PRIMECLUSTER GDS manual.
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]
When the target storage is ETERNUS
If %2 is "ERROR:ssmgr3419:The specified alias name has already been registered."
Creation or startup 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 "When an L-Server is Created or Started, "Message number 62511" is Displayed, then Creation or Startup of the L-Server Fails.".
When %2 is "ERROR:ssmgr3422:As for specified volume Volume_number, the LUN mapping is done."
Connecting a disk resource to an L-Server has failed because the Volume corresponding to the disk resource had already been mapped.
For details, refer to "When a Disk Resource is Connected to an L-Server, "Message number 62511" is Displayed and Connection Fails.".
When any other message is displayed
Performing corrective actions referring to the ETERNUS SF Storage Cruiser manual, and then perform the operation again
When the target storage is EMC CLARiiON or EMC Symmetrix DMX
When %2 is "lunmask doesn't set it."
A disk resource connected to an L-Server has been released from storage management software.
Detach the disk resource from the L-Server, and then perform the operation again.
When any other message is displayed
Perform the operation again after performing corrective actions referring to "3.2 Messages Beginning with swsag or ssmgr".
When using any other storage
Perform operations again after performing corrective actions, referring to the storage management software manual.
[Description]
There is an error in the file format specified for filename.
The details of the error are displayed for %1.
[Corrective Action]
When executing the rcxstorage command:
When "specified target volume not found in ROR (line:n)" is displayed for %1:
The disk resource corresponding to the target volume for replication specified on line n of the replication definition file specified for filename has not been detected and displayed in the resource tree. Check that the target volume for replication is correctly specified, and then execute the command again.
When "number of column must be 4 (line:n)" is displayed for %1:
There is an error with the number of columns in line n of the replication definition file that is specified for filename. Check that the number of columns is 4, and then execute the command again.
When "empty file" is displayed for %1:
There is no content in the replication definition file specified for filename. Check that the content of the replication definition file is correct, and then execute the command again.
When "field missing a value (line:n)" is displayed for %1:
A column with no value set exists in line n of the replication definition file specified for filename. Set the value for the column, and then execute the command again.
When "definition conflict with line m (line:n)" is displayed for %1:
The definition in line n of the replication definition file specified for filename is found again in line m. Correct the volume, and execute the command again.
[Description]
An incorrect value or time range was specified in option.
One of the following is output in option:
-from
-to
-duration
-from >= -to
[Corrective Action]
Refer to the command reference and specify a correct value or time range in option, then perform the operation again.
For details, refer to "1.7.14 rcxadm logctl".
[Description]
The process process for the log operation failed.
In process,"read","delete", or "copy" is output.
[Corrective Action]
Check the following, resolve the cause of the error, and then perform the operation again.
Check the system log to see if there are error message(s) regarding the disk or file system.
Check the system log to see if there is quota limit or file system full message.
[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 VM management software is deleted
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) for deletion.
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 storage management software is deleted
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.
If there is a storage pool managed by the storage management software that has virtual storage resources registered, the storage management software cannot be deleted.
If this message is displayed when deleting storage management software, release virtual storage resources managed by the storage management software (obj1) that will be deleted.
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 storage pool in which resource is registered is displayed in obj2. When there are multiple storage pools, an arbitrary storage pool will be displayed.
When a disk resource corresponding to the LUN created in advance has been registered in a storage pool, storage management software corresponding to the disk resource cannot be deleted. Before deleting the storage management software, unregister the disk resource corresponding to the LUN created in advance from the storage pool.
When creating a physical L-Server
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.
When an address set resource is deleted
Perform the operation again, after changing the resource so it is not used.
If an L-Server using a WWN and a MAC address selected from an address set resource exists, the address set resource cannot be deleted.
If this message is displayed when deleting an address set resource, execute the rcxadm address show command to check the WWN or the MAC address in use, then delete all L-Servers for which the WWN and the MAC address are set.
The WWN and the MAC address used by the L-Server are displayed in resource. If multiple WWNs and MAC addresses exist, one WWN or one MAC address is displayed at random.
The address set resource name for deletion is displayed in obj1.
"L-Server" is displayed in obj2.
When a managed server is modified or deleted
Perform the operation again, after changing the resource so it is not used.
If there is a physical L-Server for which the same admin IP address as that of the specified managed server has been set, the managed server cannot be modified or deleted.
When modifying the managed server, if this message is displayed, change the admin IP address of the physical L-Server displayed in obj2, and then perform the operation again.
When modifying the managed server, if this message is displayed, either delete the physical L-Server displayed in obj2, or release the managed server from the physical L-Server, and then perform the operation again.
The admin IP address used by a physical L-Server is displayed in resource.
The name of the network resource in use is displayed in obj1.
The name of the physical L-Server for which the same IP address as that of the specified managed server has been set, is displayed in obj2.
[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.
If the target server is a Hyper-V server:
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Perform the action indicated in the code information.
If code is 15 or 1511:
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.
When using Intel PROSet in Hyper-V, refer to "G.2.7 Advisory Notes for Hyper-V Usage" of the "ServerView Resource Orchestrator User's Guide".
If code is 16, 1524, or 1525:
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 100, 115, 1512, 1526, 1527, 1528, 1529, or 1531:
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
When using Intel PROSet in Hyper-V, review "G.2.7 Advisory Notes for Hyper-V Usage" of the "ServerView Resource Orchestrator User's Guide".
If code is 101, 110, 111, 112, 114, 116, or 1509:
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 or 1510:
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
If code is 500, 511, 1530, 1532, 1533, 1534, or 1600:
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. Check the configuration of the physical network adapter and virtual switch of the VM host/VM management software, referring to "5.2.5 Network Resources" of the "ServerView Resource Orchestrator User's Guide".
When using Intel PROSet in Hyper-V, review "G.2.7 Advisory Notes for Hyper-V Usage" of the "ServerView Resource Orchestrator User's Guide".
If code is 513 or 1601:
Failed to create the virtual switch as the physical network adapter to connect to another 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 code is 1599:
Failed to create the virtual switch as the response from the VM host or VM management software to the admin server is not correct. Check the operation status and network settings of the VM host or VM management software.
When using Intel PROSet in Hyper-V, refer to "G.2.7 Advisory Notes for Hyper-V Usage" of the "ServerView Resource Orchestrator User's Guide".
If code is 1602:
Creation of the virtual switch failed because the virtual switch name already exists. Change the virtual switch name 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.
If the target server is a Hyper-V server:
Virtual switch indicates the virtual network of Hyper-V.
[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 or 1511:
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, 1524, or 1525:
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 100, 115, or 1512:
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
If code is 101, 110, 111, 112, 114, 116, or 1509:
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 or 1510:
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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.
When 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 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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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.
When 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 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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 login account information, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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 "5.2.5 Network Resources" of the "ServerView Resource Orchestrator User's Guide".
[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.
When 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.
When 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.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
[Description]
NICnumber cannot be connected with the network resource name.
The following causes are possible:
When defining an external connection port on the switch for the network resource name, NICnumber is not connected to any switches.
When not defining the external connection port on the switch for the network resource name, specify a NIC other than that of the recommended configuration. Check the configuration of the VM host, referring to "5.2.5 Network Resources" of the "ServerView Resource Orchestrator User's Guide".
[Corrective Action]
Check the details related to the causes of the explanations above, and specify a NIC which can be connected with the network resource.
[Description]
NIC redundancy has not been configured for the combination of NIC (number) on the server server.
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
In mac, the MAC address information of the server NIC to connect with the virtual switches is displayed, separated by commas.
If the target server is a Hyper-V server:
Virtual switch indicates the virtual network of Hyper-V.
When creating a virtual switch, it is connected to NIC (number) on the server server.
Redundancy may not have been configured for the NIC(number) in advance.
[Corrective Action]
If the target server is a Hyper-V server:
Configure NIC redundancy using the combination of NIC (number) on the server server.
[Description]
The virtual switch name1 cannot be created, as there is a virtual switch, name2, for NIC(number) on the server server.
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
If the target server is a Hyper-V server:
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Delete the virtual switch name2 or change the name to the virtual switch name1.
[Description]
The virtual switch name already exists on a NIC other than NIC(number).
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
If the target server is a Hyper-V server:
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Either delete the virtual switch name created on the interface, excluding NIC(number), or change the name of the virtual switch.
[Description]
When server is a physical server:
The external connection port of the switch specified for the network resource name and NICnumber are not connected.
When server is a VM host:
The external connection port of the switch specified in the network resource name is not connected to the NICnumber used for the virtual network manually created by the user in advance.
[Corrective Action]
When server is a physical server:
Check the details related to the causes of the description above, and specify a NIC which can be connected with the network resource.
When server is a VM host:
Check the details related to the causes of the description above, and create the virtual network again.
[Description]
The specified configuration is unavailable for automatic network configuration.
When detail is "different types of LAN switch blades model"
In the specified LAN switch blades on the external connection ports for the network resource, different models of LAN switch blades are selected in the combination model for the same chassis.
The model names of the LAN switch blades are output in model, separated by commas(",").
[Corrective Action]
Check the configurations supported for automatic network configuration, and resolve the error.
When detail is "different types of LAN switch blades model"
For each chassis, check that the same model of the LAN switch blade is specified on the external connection ports for the network resource.
For LAN switch blades, the same model must be used in the same chassis, according to the following units:
For BX900 chassis, use the same model in units of Fabric
For BX600 chassis, use the same model in units of the combination NET1/NET2, and, NET3/NET4
For BX400 chassis, use the same model in units of the combination Fabric1/Fabric2
[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]
An error occurred while starting the L-Server console.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while turning on the L-Server. Power has not been turned on.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while turning off the L-Server. Power has not been turned off.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while rebooting the L-Server. Rebooting has not been performed.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while registering a user group. The user group 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 changing a user group. The user group has not been changed.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while deleting a user group. The user group has not been deleted.
[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]
The directory server could not be communicated with.
[Corrective Action]
Check whether the communication settings are correct, and the directory server has been started.
Then perform the operation again.
For details, refer to "1.7.10 rcxadm authctl".
[Description]
Refer to the explanation in "Message number 65841" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
The specified user does not belong to the user group.
The specified user belongs to multiple user groups.
[Corrective Action]
Refer to the corrective action described in "Message number 65841" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
Set the specified user as a member of an appropriate user group.
[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, resource pool XML file, image XML file, or the [Create an L-Server] dialog has a formatting error
An invalid character has been used
There is no value set
The item specified in an XML file of iSCSI boot information contains an error
The network resource name and the subnet name of the public LAN subnet are different
The network resource name and the admin LAN subnet name are different
When performing switchover of operating or standby storage, the content of the replication definition file is incorrect
The value for item that has been specified in the XML file to create tenant folders, or in the XML file of the L-Server has a formatting error
A tagged VLAN has been configured for a network resource for which PXE boot is specified
When PXE boot is specified, and an image is also specified
When retrieving the L-Server, the L-Server name has been specified incorrectly
One of the following is displayed in item:
Disk (Disk name)
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 tag or attribute name of the image XML file
A key value in the [Create an L-Server]
A tag or attribute name of the resource pool XML file
A tag or attribute name of the iSCSI boot information XML file
Network name, AddressSet name
The network resource name and the public LAN subnet name are different.
Network name, ManagementLanSubnet name
The network resource name and the admin LAN subnet name are different.
Disk.Shared
There is an error in the shared disk specifications.
A tag or attribute name of the XML file to create tenant folders
PXENetworkLink or net
ServerImageLink.id
NICs.NIC.NICIndex
The L-Server name when retrieved
processors shares
memory shares
Network auto
There is an error in the value specified for automatic configuration.
[Corrective Action]
Perform the operation again after checking the content displayed in item, and resolving the cause of the error.
Disk (Disk name)
The value of "value" in the disk information is incorrect.
When performing the switchover operation of operating or standby storage, check the content of the replication definition file.
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.
Only "new" or a hyphen ("-") can be specified in the sections after the line of "#Backup configuration".
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 "Appendix D Format of CSV System Configuration Files" of 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 tag or attribute name of the image XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the image XML file 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.
A tag or attribute name of the iSCSI boot information XML file
Perform the operation again after reviewing the value in the iSCSI boot information XML file and correcting the definition.
A tag or attribute name of the resource pool XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the resource pool XML file and correcting the definition.
Network name, AddressSet name
Specify the same value for both the network resource name and the public LAN subnet name.
Network name, ManagementLanSubnet name
Specify the same value for both the network resource name and the admin LAN subnet name.
Disk.Shared
The system disk is specified as a shared disk.
System disks cannot be specified as shared disks.
After correcting the definitions, perform the operation again.
A tag or attribute name of the XML file for tenant folders
Perform the operation again after correcting the value corresponding to the displayed key value in the XML file of the tenant folder and correcting the definition.
PXENetworkLink or net
For the network resource for which PXE boot is specified, select a network resource that does not have a tagged VLAN configured.
ServerImageLink.id
When specifying PXE boot, images cannot be specified.
After specifying only PXE boot, perform the operation again.
NICs.NIC.NICIndex
Check that sequential numbers starting from 0 are used for the NICIndex tag value of each NIC tag.
The L-Server name when retrieved
If an L-Server name was not specified when retrieved, specify the name and perform the operation again.
If an L-Server name was specified, check and correct the name.
processors shares
Review the CPUShare value defined in the L-Server template, import the L-Server template, and then perform the operation again.
When an error occurs while creating an L-Server using commands
If the CPUShare tag has been entered in the XML, review the value specified for the CPUShare tag also, and then perform the operation again.
When an error occurs when starting an L-Server
Review the CPUShare value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
memory shares
Review the MemoryShare value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When an error occurs while creating an L-Server using commands
If the MemoryShare tag has been entered in the XML, review the value specified for the MemoryShare tag also, and then perform the operation again.
When an error occurs when starting an L-Server
Review the MemoryShare value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
Network auto
Perform the operation again after reviewing the value specified for automatic configuration and correcting the definition.
[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
When value is "PhysicalServer"
When the resource type is "PhysicalServer", the physical server which satisfies the conditions may not exist or may be in an incorrect status.
When "(Storage pool)" follows after value
The process was canceled because one of the following applies to the specified disk resource:
The specified disk resource is not registered in the resource pool
The virtual storage resource in which the specified disk resource was created is not registered in the resource pool
When "value" is "IOVirtualOptionPool"
The process was canceled because one of the following applies to the specified address set resource:
There is no address pool to store the address set resources to allocate to L-Servers
There are no unused address set resources in the address 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.
When "PhysicalServer" has been output for value, a physical server that matches the specified conditions may not exist, or the status may be invalid. Check that the L-Server definition and the physical server in the specified server pool meet or exceed all of the following conditions.
Number of CPUs
CPU Clock Speed
Memory Size
Number of NICs
Also check that the network configuration of the admin LAN matches completely, including NIC redundancy.
When "IOVirtualOptionPool" is output for value, check that an address pool to store the address set resource exists, or an unused address set resource exists in the address pool.
[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 a physical L-Server
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.
When executing the rcxstorage command:
When "mirror definition" is displayed for obj
The disk matching the description of the replication definition file has not been defined in Resource Orchestrator.
(There are no disks to be recovered in failover or Disaster Recovery.)
When "disk" is displayed for obj
There are no disk resources to be processed.
When switching over the operating and standby storage
The disk to be processed was created in advance, and the storage unit supports switchover of operating and standby storage.
When linking a configured physical server to a physical L-Server:
When "disk" is displayed for obj
There are no disk resources to be processed.
When creating a virtual L-Server:
When obj starts with "VLANID"
The virtual network resource specified in the virtual network definition file was not found on the VM host.
[Corrective Action]
Review the specified conditions.
When creating a physical L-Server
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.
When executing the rcxstorage command:
When "mirror definition" is displayed for obj
Check that the content of the replication definition file is correct, and then execute the command again.
When "disk" is displayed for obj
Check the disk resource to be processed, and perform the command again.
When linking a configured physical server to a physical L-Server:
When "disk" is displayed for obj
Check the disk resource to be processed, and perform the command again.
When creating a virtual L-Server:
When obj starts with "VLANID"
Perform the operation again after checking the target virtual network definition file and resolving the cause of the error.
[Description]
"Usage" is displayed.
When "Usage" is "Usage: rcxbackup -dir directory [[-nowait]|[-timeout value]]"
There is an error in the input format of the rcxbackup command. The command is not executed.
When "Usage" is "Usage: rcxrestore -file filename"
There is an error in the input format of the rcxrestore command. The command is not executed.
[Corrective Action]
Check the format displayed in "Usage", and then execute the command again.
[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 a physical L-Server, 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 for the 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
Registration of iSCSI boot information
Create tenant folders
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
Pool XML
iSCSI XML
Tenant XML
Specified_value (IP address, etc.)
-duration
[Corrective Action]
When -duration is output
Specify a correct value or format for the option, then perform the operation again.
For details, refer to "1.7.14 rcxadm logctl".
In cases other than the above, correct the specified value or the content of the XML file, and then perform the operation again.
For details on XML files, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
[Description]
Refer to the explanation in "Message number 67135" in "ServerView Resource Coordinator VE Messages".
In Resource Orchestrator, "Network ManagementLanSubnet" or "Network AddressSet" may be displayed for option.
In these cases, both the admin LAN subnet and the public LAN subnet are specified.
[Corrective Action]
When "Network ManagementLanSubnet" or "Network AddressSet" is displayed for option
Both the admin LAN subnet and the public LAN subnet are specified.
Based on the type of network resource to be created, specify either the admin LAN subnet or the public LAN subnet.
When another message is displayed for option
Refer to the corrective action in "Message number 67135" in "ServerView Resource Coordinator VE Messages".
[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 "8.2 Collecting a Cloning Image" of 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" of the "ServerView Resource Orchestrator User's Guide".
When "server_spec.rcxprop" is displayed in filename, check the file format referring to "5.2.6 Servers Not Using Server Management Software" of the "ServerView Resource Orchestrator User's Guide".
[Description]
The rcxbackup or the rcxrestore command is already being executed. The command is not executed.
[Corrective Action]
After the rcxbackup command or the rcxrestore command is completed, execute the command again when necessary.
[Description]
Refer to the explanation in "Message number 67142" in "ServerView Resource Coordinator VE Messages".
[Corrective Action]
Refer to the corrective action described in "Message number 67142" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When "server_spec.rcxprop" is displayed in filename, check that reading of the file is allowed.
[Description]
The process was canceled as the target file was not found.
[Corrective Action]
When executing the rcxchkmismatch command and file_name is "fullbackup_info.xml"
Perform the following corrective actions and then continue restoring the admin server:
There is an error in the directory name of the L-Server restoration log storage directory specified for the argument of the -logdir option.
Specify a correct directory name for the argument of the -logdir option, and then execute the rcxchkmismatch command again.
The rcxreserveid command has not been executed.
Perform the operation for restoring the admin server again, from execution of the rcxreserveid command.
In other cases
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.
When obj is "network_resource_name"
A network resource with the same name already exists.
[Corrective Action]
Refer to the corrective action described in "Message number 67153" in "ServerView Resource Coordinator VE Messages".
When obj is "vnet"
Either specify a different VLAN ID, or delete the existing network resource, and then perform the operation again.
When obj is "network_resource_name"
Change the network resource name, and perform the operation again.
When executing the rcxadm config import command
Change the name of the object to import, or either delete or rename obj, 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
The target resource folder was not specified when a user with multiple access scopes performed an operation
When a user with multiple access scopes performs the following operations, "Folder:not found" or "Specified_resource_name:not found" is displayed.
Creation of an L-Server, with no target resource folder name set
Creation of a tenant folder, resource folder, or resource pool, without specifying the name using the hierarchy
Moving of a tenant folder, resource folder, or resource pool, without specifying the -to option for the destination
Creation of an L-Server from the RC console, specifying values in the definition file. The values are larger than the actual number of CPUs and CPU clock speed of a server for which server management software is not used
If this message is displayed when the 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.
The specified object name or the resource type of the specified object name is displayed in obj.
If the object was deleted during the process, the resource type is displayed.
If the command was executed, "server OS", "vm_host", or VM_host_name is displayed for the resource type of the object name for a physical OS or VM host, "VM Guest" or VM_guest_name for a VM guest, Management_software_name for a management software, and "image" or "obj(image)" for a system image or cloning image, "library share" for a shared library, and "AuthManager" for a directory service.
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.
For details on conditions for automatic creation of virtual switches, refer to "Automatic Network Configuration for Blade Servers" of "1.2.6 Simplifying Network Settings" in the "ServerView Resource Orchestrator User's Guide".
When obj starts with rcx-portset, the procedure of "NetApp FAS Storage Configuration" in "F.3.2 When Using NetApp FAS Storage" of the "ServerView Resource Orchestrator User's Guide" may not have been performed.
When obj is "AuthManager", the operation has failed because a directory service is not registered.
When obj begins with one of the following values, there is no target L-Server for the power operation.
LServer
Check the status of the L-Server and whether the L-Server exists in the resource folder.
When obj starts with the following value, there is no L-Server template for the operation.
L-Server Template
Check that the specified L-Server template exists.
[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
Specification of a target resource folder, when the user has multiple access scopes
When creating an L-Server, specify the name of the resource folder where the L-Server will be created in the XML file for the L-Server.
For details on resource folder names, refer to the following information:
"2.3.1 For Physical L-Servers"
"Element Name Resource folder name or tenant folder name" of "Example Creating an L-Server in a resource folder or a tenant folder"
"Element Name Resource folder name or tenant folder name" of "Example Creating an L-Server in a resource folder or a tenant folder"
When creating tenant folders, resource folders, or resource pools, specify the name using the folder hierarchy, including the destination resource folder name.
For details on resource folder names, refer to the following information:
When moving a tenant folder, a resource folder, or a resource pool, specify the destination resource folder.
For details on destination resource folders, refer to the following information:
Check that the values specified in the definition file are less than the actual number of CPUs and CPU clock speed of a server for which server management software is not used.
If this message is displayed when the command is executed, perform the operation again after checking the resource type of the specified object.
If one of the following is output in obj, perform the appropriate corrective action.
"library share" [Hyper-V]
There is an error in the storage destination specified for the cloning image.
Check if the specified shared library is available.
"Selectable virtual_storage(condition)"
There is a chance that there is not enough available disk space on the selected virtual storage.
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
When using RHEL5-Xen as server virtualization software, the contents of the storage connection definition file may be incorrect.
Review the settings in the storage connection definition file.
For details, refer to "G.3.4 Setup" of the "ServerView Resource Orchestrator User's Guide".
"Selectable disk(condition)"
There is no disk resource matching the specified size registered in the storage pool.
Check whether or not an unused disk resource larger than size=%1(GB) has been registered in the storage pool, then perform the operation again.
In condition, one of the following is displayed:
size=%1
"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 status is 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 migration, if this message is output, take the following corrective action:
When specifying "Automatic Selection" for the destination VM host (For the command, when omitting the -to option)
The resources used by the L-Server do not contain a VM host that satisfies the conditions in 1. except the one to migrate.
Specify the destination VM host, and then perform the operation again.
For details on how to check the resources to use, refer to the cautionary notes of "6.8 Moving an L-Server Between Servers (Migration)" of the "ServerView Resource Orchestrator User's Guide".
When specifying "VM host" for the destination VM host (For the command, when specifying the -to option)
The specified VM host does not satisfy the conditions in 1. Specify another VM host, and then perform the operation again.
capacity
There is a chance that there are not enough available resources for the CPU or memory of a VM pool. Check the available resources for the CPU and memory of the VM pool.
Perform the operation again after performing the following corrective actions:
If there is insufficient CPU performance or memory resources of the VM pool
Add a VM host to the VM pool.
If there is no VM host in the VM pool that meets CPU performance or the number of CPUs specified for an L-Server or an L-Server template
Change the CPU performance or the number of CPUs specified for an L-Server or an L-Server template, or add a VM host meeting the necessary performance to the VM pool.
datastore
Perform the operation again after checking whether a VM host sharing a datastore exists.
If this message is displayed when performing migration, check whether the datastore is shared between the VM host where the L-Server is deployed and the "VM host" set for the L-Server using VM management software. If the datastore is not shared, specify a VM host that shares the datastore with the destination VM host, and then perform the operation again.
When migrating between VM hosts that do not share a datastore, perform the operation using VM management software.
For details on how to check the VM host to use, refer to "6.8 Moving an L-Server Between Servers (Migration)" of the "ServerView Resource Orchestrator User's Guide".
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.
If using overcommit, check that both VM pools (the one that is set for overcommit and the one that is not) are in the access scope, and then perform the operation again.
For details on the overcommit function, refer to "G.1.8 Overcommit" of the "ServerView Resource Orchestrator User's Guide".
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.
If using overcommit, check that both VM pools (the one that is set for overcommit and the one that is not) are in the access scope, and then perform the operation again.
For details on the overcommit function, refer to "G.1.8 Overcommit" of the "ServerView Resource Orchestrator User's Guide".
vm_type
Specify or change the VM host to use and perform the operation again.
If using overcommit, check the overcommit settings for resource pools and L-Servers.
reserved capacity
There is a possibility that there is a VM host with sufficient reservation capacity for failover in the VM pool, and there are not enough available CPU or memory resources in the VM pool. Check the cluster configuration of the server virtualization software, correct the reservation capacity, and then perform the operation again.
If the problem is still not resolved after performing the corrective actions above, perform the following corrective actions:
If there is insufficient CPU performance or memory resources of the VM pool
Add a VM host to the VM pool.
If there is no VM host in the VM pool that meets CPU performance or the number of CPUs specified for an L-Server or an L-Server template
Change the CPU performance or the number of CPUs specified for an L-Server or an L-Server template, or add a VM host meeting the necessary performance to the VM pool.
image
A template (Virtual Machine Template) corresponding to the cloning image to deploy and the VM host (Server) where the cloning image is deployed must belong to the Oracle VM server pool.
On Oracle VM Manager, perform configuration so the VM host exists in the same Oracle VM server pool as the template corresponding to the cloning image to deploy.
Also, register the VM host in a VM pool included in the access scope, and then perform the operation again.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
For details on checking the status and free capacity of a VM host, refer to "A.4 Viewing a Resource Pool" in the "ServerView Resource Orchestrator User's Guide".
"Selectable mac_address_set(condition)"
Perform the appropriate corrective action for each condition. In condition, one of the following is displayed:
free address
Perform the operation again, after checking if there are vacant addresses in the address set resources (MAC addresses).
resource
There are no address set resources (MAC addresses). Perform the operation again, after registering the address set resources (MAC addresses) in accessible address pools.
"resource" or "Pool"
The resource to be registered with or canceled from the resource pool, or the resource pool, was not found. Check that the resource or the resource pool exists, and then perform the operation again.
"DNSServer.nic=X"
The NIC definition to set for the DNS server was not found. Check whether the NIC for X exists, review the NIC definition on DNS server, and then perform the operation again.
"AuthManager"
Perform the operation again after registering a directory service.
When obj starts with one of the following values, refer to "5.2.5 Network Resources" of the "ServerView Resource Orchestrator User's Guide", 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 "NetApp FAS Storage Configuration" in "F.3.2 When Using NetApp FAS Storage" of the "ServerView Resource Orchestrator User's Guide".
When obj begins with one of the following values, there is no target L-Server for the power operation. Check the status of the L-Server, and perform the appropriate operation or specify another resource folder, and then perform the operation again.
LServer
When obj starts with the following value, there is no L-Server template for the operation. Specify another L-Server template, and then perform the operation again.
L-Server Template
When obj starts with one the following values, check whether one of the items listed exist on the VM guest allocated to the L-Server: virtual disks that contain the path for device_name, networks that have one more network resource than NIC_index, or networks that have MAC_address.
VmGuestStorage(device_name)
VirtualNic(LNic index=NIC_index)
VirtualNic(LNic mac_address=MAC_address)
When obj starts with the following values, check that the VM host, or the resource pool and the destination folder for L-Server creation belong to the same tenant. This assumes that there is a configured virtual machine on the VM host, and a physical server belongs to the resource pool.
TargetServer id=Virtual_machine_ID
PhysicalServer id=Physical_server_ID
When the destination folder for L-Server creation does not belong to the same tenant as that of the resource pool, change the value of "Destination folder" (use the -to option for the command operation) to make them belong to the same tenant, and then perform the operation again.
When a resource pool does not belong to a tenant, specify a folder not contained in a tenant as the destination for L-Server creation.
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 "VM", "Server", "Storage", "Network", "Address", or "Image" is displayed for type, and this message is output during creation of resource pools
obj has already been registered in a resource pool.
When physical L-Servers were created, or network resource settings were changed, the IP addresses of the admin LANs, which are used by the physical L-Servers and the managed servers that are registered in the server tree, will overlap.
When type is "server", and this message is output during creation of physical L-Servers
The IP address of obj is overlapping with the IP address of the admin LAN used by the L-Servers and the managed servers.
When "IP address" is displayed for type
The IP address obj of the public LAN specified during creation of the physical L-Server is already in use.
When type is "iSCSI.iqn"
The IQN name in obj is already in use.
When type is "iSCSI.ip"
The IP address in obj 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 "VM", "Server", "Storage", "Network", "Address", or "Image" is displayed for type, and this message is output during creation of resource pools
Check the resource pool of obj, and create it again if necessary.
When physical L-Servers were created, or network resource settings were changed, change the IP address of the admin LAN used by the managed servers that are registered on physical L-Servers or the server tree, then perform the operation again.
When type is "server", and this message is output during creation of physical L-Servers
For the admin LAN IP address, specify an IP address not used by another resource, or change the IP address of the resource that is currently overlapping, and then perform the operation again.
When "IP address" is displayed for type
For the created physical L-Server, manually set the public LAN IP address, or review the network configuration after deleting the physical L-Server, and then perform the operation again.
When type is "iSCSI.iqn"
Perform the operation again after correcting the specified IQN name.
When type is "iSCSI.ip"
Perform the operation again after correcting the specified IP address.
[Description]
A user who does not have sufficient privileges executed the command. The command is not executed.
[Corrective Action]
Execute the command again, with sufficient privileges.
[Description]
option must be specified. "usage" is displayed.
[Corrective Action]
After checking the parameter, perform the operation again.
When option is "name"
Specify the L-Server name for the -name option, and perform the operation again.
When option is "NICGroups.NICGroup.NICLinks"
Check that the NICLink tag appears twice in the XML file specified in creation or modification of the L-Server.
[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 obj:
Virtual storage resource name
Disk Resource Name
VM name
VM guest name
Library server name
L-Server Name
Physical server name
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 space for disk(name=disk)
not enough free space
defined
preserved
allocated
shared
reserved
free
excluded
"power-on" refers to when the power of the server is on.
"power-off" indicates the state in which a server is powered off, a VM guest that was operated on an L-Server has been deleted from server virtualization software, or an unregistered VM host has been moved to a VM pool.
"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 or server.
"not enough free space(name=disk)" refers to when there is insufficient free space on the virtual storage resource. The resource name of the disk is displayed in disk.
"not enough free space" refers to when there is insufficient free space on the virtual storage resource.
"defined" indicates that resources (VM guests, servers, and disks) have not been allocated.
"preserved" indicates that servers have not been allocated.
When obj is an IP address and status is "reserved", it indicates that the IP address is already reserved.
When obj is an IP address and status is "free", it indicates that the IP address has already been released.
When obj is an IP address and status is "excluded", it indicates that the IP address has already been excluded.
[Corrective Action]
Check the necessary requirements for the obj operation, and fulfill them. Perform the operation again after fulfilling the requirements.
During batch power ON operation, if status is displayed as "defined", perform the usual startup operations for the relevant L-Servers.
When status is the following, change the IP address of the L-Server or managed server, then perform the operation again:
"reserved"
"free"
"excluded"
[Description]
Execution of the request failed, as the specified obj is not mode mode.
When obj is a disk resource
In mode, one of the following is displayed:
shared (shared mode)
local (local mode)
Fibre Channel connection (Fibre Channel connection)
iSCSI connection (iSCSI connection)
When obj is something other than the above, refer to "Message number 67181" in the "ServerView Resource Coordinator VE Messages".
[Corrective Action]
When obj is a disk resource
When "true" is specified for Sharing Configuration (Shared) in the L-Server XML, the disk can be shared between multiple L-Servers.
When "false" is specified for Sharing Configuration (Shared) in the L-Server XML, the disk can be restricted to one L-Server.
Check the connection status of the specified obj.
When "FC" is specified for Disk connection type (Disk type) in the L-Server XML, a disk with a Fibre Channel connection is allocated to the L-Server.
When "iSCSI" is specified for Disk connection type (Disk type) in the L-Server XML, a disk with an iSCSI connection is allocated to the L-Server.
[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 "1.2.1 Resource Pool" in the "ServerView Resource Orchestrator User's Guide".
If this message is output when registering the disk resource with a storage pool, check whether the disk is the one created in advance using the disk resource.
From the command-line, execute rcxadm disk show.
For details on the rcxadm disk show command, refer to "1.3.4 rcxadm disk".
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.
The combination of an obj1 resource and an obj2 resource is incorrect. Specify an unused address resource for the combination to be supported, and 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.
This message is output when a communication error occurs between the L-Server and the manager.
[Corrective Action]
Check that an agent is installed on the L-Server.
Check that there is no problem in the network path between the L-Server and the manager.
Execute the command specifying the file for the argument. When target is "Resource Coordinator Manager", check whether or not the character code for the XML file is UTF-8.
Refer to the explanation in "Message number 67192" in "ServerView Resource Coordinator VE Messages".
[Description]
An error occurred in the manager command.
The details of the message are displayed in detail.
When "Failed to access database for backup." is displayed for detail
Accessing of the database where configuration definition information is stored failed. The command is not executed.
[Corrective Action]
Perform corrective action for content output in detail.
Where there is nothing relevant to detail, refer to "Message number 67198" in the "ServerView Resource Coordinator VE Messages".
When timeout is displayed in detail
When using PRIMECLUSTER GDS as storage management software
During the process, the connection between the admin server and the storage management software may have been lost.
Check the power status and communication status of the storage management software.
There may be an error in the PRIMECLUSTER GDS settings.
Review the PRIMECLUSTER GDS settings.
The storage management software may be overloaded.
Perform the operation again after completing the high-load processing.
When "Failed to access database for backup." is displayed for detail
Check the status of the database, resolve the cause of the access failure, and then execute the command again.
If a string including double-byte characters is specified for the -dir option of the rcxbackup command, accessing of the database will fail.
[Description]
Refer to the explanation in "Message number 67209" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
obj is already in use.
This also applies when an already excluded IP address (an admin server, a managed server, a network address, or a broadcast address) is specified for an exclusion IP address, when configuring a network resource.
In obj, the MAC address written in "mac_address=" has already been used.
[Corrective Action]
Refer to the corrective action described in "Message number 67209" in "ServerView Resource Coordinator VE Messages".
When obj is already in use
Review the specified option argument, and perform the operation again.
In obj, when the MAC address written in "mac_address=" has already been used
Perform the operation again after correcting the specified MAC address.
[Description]
The requested process cannot be performed as another process is already being performed.
[Corrective Action]
When obj is a network resource
Wait for a short while and then repeat the operation. After deleting the L-Server connected to the network resource, perform the operation again.
When obj is "Manager task"
Check the status of the admin server, and perform the operation again after any operations being executed on the admin server are completed.
If this message is displayed when the admin server is stopped, the operation being executed on the admin server may remain in the database. Start the admin server and complete the operation being executed on the admin server, or restore the configuration definition information already collected, then perform the operation again.
[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 "5.1 Manager" 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 a physical L-Server has been switched over
There are no physical server resources available as spare servers in the specified spare server resource pool.
[Corrective Action]
Check that the physical server in the server pool which was specified as a spare server meets or exceeds all of the following conditions.
Number of CPUs
CPU Clock Speed
Memory Size
Number of NICs
Refer to the corrective action described in "Message number 67220" in "ServerView Resource Coordinator VE Messages".
When a physical L-Server 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 a physical L-Server 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.
When "-system" or "-force" is displayed in option
The storage unit to which the disk resource, for which an operation was attempted using the rcxadm lserver attach command or the rcxadm lserver detach command, belongs does not support the -system option or the -force option of the rcxadm lserver command used for the switchover of operating and standby storage. Therefore, the -system option and the -force option cannot be specified.
When "resource" is displayed in "option"
The specified resource is not the target of the movement, or the resource has not been registered in the orchestration tree.
[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 a physical L-Server was created, "NICs.NIC.NetworkLinkfor NICIndex(num)" is displayed in option
Change the network resource settings and perform the operation again.
When "-system" or "-force" is displayed in option
Check that switchover of operating or standby storage is being performed for the correct storage unit, or check the content of the replication definition file.
When "resource" is displayed in "option"
Specify a movable resource. Also, register resources that have not been registered in the resource orchestration tree into resource pools.
[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.
function cannot be executed, as VMware FT has been set for the target resource.
Or function cannot be executed as VMware FT cannot be configured for the target resource.
"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","Shared","Disks.Disk.type","Policy.SpareSelection"
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.
"Not Physical Server"
This command can only be performed for the physical L-Server.
Execute this command for the physical L-Server.
"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 a physical L-Server, the IP address cannot be automatically configured if a Red Hat Enterprise Linux image is specified.
When using the created L-Server, manually configure the public LAN IP address.
"disk share"
The Shared tag cannot be specified in XML for disks with the disk number 0.
"disk link"
The DiskLink tag cannot be specified in XML for disks with the disk number 0.
"disk copy"
The DiskCopy tag cannot be specified in XML for disks with the disk number 0.
"disk link, copy"
The DiskLink tag and the DiskCopy tag cannot be specified in XML for a single disk at the same time.
"disk type"
The value specified for "type" cannot be set for disks other than disk number 0.
"Shared","DiskLink","DiskCopy","MacAddress"
An L-Server cannot be created, as the above tags are not supported when creating an L-Server.
"Not Virtual Machine" or "Physical Server"
Usage is not possible for physical L-Servers.
"already in use"
A disk that is already being used exclusively by an L-Server cannot be attached to another L-Server.
"last","logical server not found"
The function cannot be executed, since operations not supported by the target resources were specified.
"hierarchizing of Tenant folder"
As the hierarchizing of tenant folders is not supported, tenant folders cannot be created in, or moved into, a tenant folder.
"invalid Repurpose"
function cannot be executed, as the resource to be operated does not support the XML tag in detail.
"already in use"
A virtual machine, a physical server, or a disk that is already being used exclusively by an L-Server cannot be connected to another L-Server.
"VM Type","VMType","VM type"
The target resource displayed in obj is server virtualization software that does not support function.
[VMware]
For VMware ESXi, the following operation is not supported.
Backup
[Hyper-V] [Xen]
The following operation is not supported.
Overcommit
[Oracle VM]
The following operation is not supported.
Creation of an L-Server without specifying a cloning image
"illegal disk type"
The disk type is not supported.
"not creatable storage"
Disk resources cannot be automatically generated on the target storage device.
"can not delete the static disk"
The LUN created in advance cannot be deleted.
"VIOM is required"
When allocating disk resources to physical L-Servers from multiple storage chassis, VIOM is necessary.
"subnet"
The subnet address of the admin LAN resource that is directly connected from the manager cannot be changed.
"mask"
The subnet mask of the admin LAN resource that is directly connected from the manager cannot be changed.
"DefaultGateway"
The default gateway of the admin LAN resource that is directly connected from the manager cannot be changed.
obj is "network_resource_name", and detail is "AddressSet".
The subnet address of a resource of the admin LAN directly connected to a manager cannot be specified.
obj is "network_resource_name", and detail is "ManagementLanSubnet".
Subnet addresses of the admin LAN cannot be used for public LAN resources.
The <ManagementLanSubnet> tag cannot be specified when the <Type> tag to specify the network resource type is not set.
obj is "UserGroup", and detail is "supervisor group"
The "supervisor" group cannot be edited and deleted.
"Pool"
The resource pool cannot be specified.
"Type"
The network resource type cannot be specified.
"Vlanid"
The VLAN ID cannot be specified.
"other tenant folder"
A resource that is being used by a powered on L-Server cannot be moved to another tenant.
Stop the L-Server before moving the resource.
The following resources cannot be moved:
Powered on L-Servers
Folders that contain powered on L-Servers
Resource pools used by powered on L-Servers
Folders or resource pools that contain resource pools used by powered on L-Servers
"The resources used are permission denied."
Access authority is necessary for some resources displayed in obj, which are used by the L-Server.
Check the status of the resources used by the L-Server.
"storage is not configured properly"
The function displayed in function cannot be used as the storage has not been configured properly.
"ExternalPorts"
Only the following operation can be performed for external networks.
Addition of external connection ports of a chassis attached to the target external network, when one or more external networks exist
"unknown disk"
function cannot be executed, as there is an unknown disk on the resource to be operated.
"converted vm" or "converted server"
function cannot be executed, as the resource to be operated is an L-Server linked to either a configured physical server or a virtual machine.
"secondary vm of VMware FT"
function cannot be executed, as the resource to be operated is a VMware FT secondary virtual machine.
"exist spare server settings"
function cannot be executed, as the resource to be operated is a physical server for which a spare server has been configured.
"agent is not registered"
function cannot be executed, as there is no registered agent.
"Server pool,Storage pool,Network pool,Address pool,and Image pool"
The operation is valid for VM pools.
The elements in the resources registered in the resource pool cannot be displayed for the resource to be operated.
Reserve information for configuring HA cannot be displayed, as the resource to be operated is not a VM pool.
"Storage pool,Network pool,Address pool,and Image pool"
The resource to be operated cannot be displayed linked to L-Servers. The operation is valid for VM pools and server pools.
When registering resources to a resource pool, and "force" is displayed
function cannot be executed, as the force option is not supported for resources other than server pools.
"Dynamic Memory is enabled"
Dynamic memory settings are enabled for the target resource.
Memory capacity cannot be changed for L-Servers for which dynamic memory settings are enabled.
[Corrective Action]
When obj is "Target network overlaps with admin LAN"
After creating a physical L-Server, configure the IP address manually. Configure the admin LAN and the public LAN in different networks.
When obj is something other than "Target network overlaps with admin LAN"
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.
When obj is "network_resource_name" and detail is "AddressSet"
Specify the subnet name of the admin LAN, and perform the operation again.
When obj is "network_resource_name" and detail is "ManagementLanSubnet"
Specify a different value for the subnets of the admin LAN and public LAN, and perform the operation again.
When creating a network resource for the admin LAN using the public LAN subnet, add the <Type>admin</Type> tag, and specify the <ManagementLanSubnet> tag.
When obj is "DafaultGateway" and detail is "ManagementLanSubnet name = "" , Type = admin"
For the admin LAN connected directly to a manager, do not specify the default gateway.
When function is "convert L-Server" and detail is "storage is not configured properly":
Check that the storage has been configured for linking the configured physical server to the L-Server.
When obj is "network_resource_name" and detail is "ExternalPorts"
Check the information for the specified external connection port and define all new information of the settings after modification.
When the following conditions are met, perform the addition of external connection ports using the command.
The target network resource has been created using a command
If this message is displayed when adding an external connection port from the GUI
When detail is "some settings exist"
When registering a configured physical server to a resource pool, specify the -force option and perform the operation again.
When detail is "Dynamic Memory is enabled":
If changing the memory capacity when dynamic memory is enabled, perform the operation using VM management software.
The changed values are reflected on the configuration of the L-Server by periodic queries made to the VM management software.
For details on the reflection of L-Server configuration by periodic queries, refer to "6.3 Modifying an L-Server" of the "ServerView Resource Orchestrator User's Guide".
When changing the memory capacity using Resource Orchestrator, change the settings of the target virtual machine to static memory using VM management software.
After the change has been reflected on the L-Server, perform the operation again.
[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.
When performing user authentication using directory service
obj has already been registered in the root folder, the same resource folder, the same tenant folder, or the same resource pool. The names are not case-sensitive.
When importing the configuration information for the operation of Disaster Recovery environments.
There are multiple VM guests or VM hosts specified in obj.
When the name on management software has been changed, reverse the change, and perform the operation again.
[Corrective Action]
Refer to the corrective action described in "Message number 67295" in "ServerView Resource Coordinator VE Messages".
When registering resources to resource pools
With Resource Orchestrator, if obj has already been registered in a resource pool, it is displayed because currently registered resources cannot be registered. No action is necessary.
When performing user authentication using directory service
A resource with the same name as an already registered resource is displayed, because it cannot be registered at the same time. Change the resource name, and then perform the operation again.
[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 how to check its running state, refer to "5.1 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. Check 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 be installed, or roles may be 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 status is changed using 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 changing the entered values, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 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.
When CPU or memory to be allocated to a VM guest is insufficient, depending on your environment, either migrate the VM guest to another VM host, or stop the VM guest.
[VMware]
When VMware DPM is enabled and there is a VM host in standby mode in a VMware cluster with a VM guest, start the VM guest from VM management software.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
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 changing the entered values, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 "A.2 Configuration Requirements" in 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 "A.2 Configuration Requirements" in 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 changing the entered values, refer to "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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. Check the following:
Check the operation status and network settings of the VM host/VM management software.
If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
[Hyper-V]
Check whether or not a virtual machine OS has been installed and if the OS has been started.
If an OS has not been installed on a virtual machine, install and start one.
If the OS is not running on the virtual machine, perform the operation after starting up the OS.
If error_number 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 547 is displayed:
VM host/VM management software may not meet the requirements necessary for starting the target VM guest. Use SCVMM to check whether the VM host/VM management software meet the requirements.
If 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 how to check its running state, refer to "5.1 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 99 is displayed:
Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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 "5.2.4 Storage Resources" in the "ServerView Resource Orchestrator User's Guide" and correctly describe the port combination definition file of the SAN 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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
[Description]
Stopping of the spare server target failed.
[Corrective Action]
Refer to the explanation in "Message number 67360" in "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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
[Description]
An error occurred in communication with the VM host, so changing of the login account information of the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67363" in "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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
[Description]
Setting of VM maintenance mode for the VM host obj failed.
[Corrective Action]
Refer to the explanation in "Message number 67368" in "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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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]
As the VM guest obj does not have a CD/DVD drive, connection of the VM guest tool is not possible.
[Corrective Action]
Add a CD/DVD drive using the VM management software.
[Description]
Connection of the VM guest obj to the VM guest tool failed.
[Corrective Action]
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:
As the manager was restarted during processing, the process has failed. Check that the manager has started properly, and then perform the operation again.
For details on how to check its running state, refer to "5.1 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. On the management software tree of the RC console, select the VM management software used to manage the VM host, and perform [Update].
After that, display the server resource tree, and check whether the VM guest has been moved to another VM host.
If error_number 17 is displayed:
The VM guest could not be found. On the management software tree of the RC console, select the VM management software used to manage the VM host, and perform [Update].
After that, display the server resource tree, and check whether the VM guest has been deleted.
Also, check whether the VM guest is set to be moved when its power status is changed using the VM management console.
If error_number 101, 110, 111, 112, 114, 116, or 473 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 "6.3.2.7 Changing VM Host Login Account Information" in the "ServerView Resource Coordinator VE Setup Guide".
If error_number 100, 115, or 471 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 "6.3.2.7 Changing VM Host Login Account Information" in 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.
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 472 is displayed:
Due to the occurrence of an error on the VM host or VM management software, connection with the VM guest tool was not possible.
Check the cause of the error in the VM host/VM management software, and resolve the error.
If "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]
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 "5.1 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 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 "5.1 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
[Description]
Migration of the VM guest vmguest failed. Server vmhost1 is the source and server vmhost2 is the destination.
[Corrective Action]
Refer to the explanation in "Message number 67385" in "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 "5.1 Manager" in the "ServerView Resource Coordinator VE Setup Guide".
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 status is changed using 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 104 or 152 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 150 or 164 is displayed:
The VM host specified as the destination does not meet the requirements for the migration destination of VM guests. Specify a VM host that meets the requirements for the destination.
For environments where overcommit is being used, also refer to the cautionary notes of "6.8 Moving an L-Server Between Servers (Migration)" of the "ServerView Resource Orchestrator User's Guide".
For details on the overcommit function, refer to "G.1.8 Overcommit" of the "ServerView Resource Orchestrator User's 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 "Appendix A Server Virtualization Products" of 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 "5.1 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 of the VM host/VM management software, and perform the operation again.
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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 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.
[Hyper-V]
If error_number is 104, and the guest OS type is Windows, the product key may be not correct. Check that the correct product key has been specified. The product key cannot be omitted.
[VMware]
If the error number is 104 and the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 536, 538, or 546 is displayed:
There is a problem with the library of System Center Virtual Machine Manager. Check that the status of the library server or shared library is normal, then perform the operation again after waiting for a short time.
If error_number 537 or 539 is displayed:
Operation of the System Center Virtual Machine Manager library failed. Check the result of the job using System Center Virtual Machine Manager.
If error_number 604 is displayed:
Specify a value smaller than the physical memory size of the VM host.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
If error_number 605 is displayed:
Specify a value smaller than the number of CPU cores of the VM host.
If the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
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 the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
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 error_number 621 is displayed:
The format of the specified IP address is incorrect. Specify an IP address in the correct format.
If error_number 624 is displayed:
The template of System Center Virtual Machine Manager corresponding to the specified image is either invalid or damaged. Check the image using System Center Virtual Machine Manager.
If 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 "5.1 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 status is changed using 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 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 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 "5.1 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 status is changed using the VM management console.
If error_number 20 is displayed:
The port group of the specified virtual switch was not found on VM management software.
Check that the port group exists on VM management software.
If no port groups exist:
Create a port group for the virtual switch on VM management software.
If port groups exist:
When using the virtual network definition file, check that all definitions are described correctly.
After checking the definition file, perform the operation again.
If error_number 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 of the VM host/VM management software, and perform the operation again.
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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 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 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in the "ServerView Resource Coordinator VE Setup Guide".
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 the target server is not using server management software, there may be differences between the values in the definition files and the actual configuration information of that server. Check that the correct values have been entered.
For details on the definition file, refer to "5.2.6 Servers Not Using Server Management Software" of "ServerView Resource Orchestrator User's Guide".
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 "5.1 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 status is changed using 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 99 is displayed:
Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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. Cloning images also cannot be collected when there are snapshots or check points created by VM management software.
[Hyper-V]
When there are snapshots that have been collected using Resource Orchestrator or checkpoints created using VM management software, it is not possible to collect cloning images as VMs are operated on difference disks. For combining of difference disks, it is necessary to delete not only all snapshots collected using Resource Orchestrator, but also all checkpoints created using VM management software. Combining of the disk is automatically performed by SCVMM, but depending on the status of the VM guest the operation may take a long time, because it is only performed while the target VM guest is stopped.
If error_number 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 error_number 642 is displayed:
A cloning image with the specified name already exists. Specify a new name.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the VM guest image.
[Corrective Action]
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 "5.1 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 99 is displayed:
Due to temporary inconsistencies in the information held by VM host/VM management software resulting from multiple operations, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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 error_number 544 is displayed:
Obtaining the information of the VHD file, which is a related file of the target image to be deleted, failed. Use System Center Virtual Machine Manager to check that the status of the shared library is normal. After waiting for a short time, perform the operation again.
If error_number 545 is displayed:
Deletion of the related files of the target image to be deleted failed. Check the result of the job using System Center Virtual Machine Manager.
If 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 "5.1 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 status is changed using 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, operations of VM host/VM management software failed. Check the operating status of the VM host/VM management software, and perform the operation again.
If error_number 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 "6.3.2.7 Changing VM Host Login Account Information" or "6.3.6 Changing VM Management Software Settings" in 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]
User authentication failed because the user registered in a directory service does not belong to a user group. In user, the user name is displayed.
When this message is displayed during operation, the directory service information may have been modified.
[Corrective Action]
Check the user information and user group information registered in the directory service, then set the displayed user as a member of an appropriate user group.
[Description]
User authentication failed because the user registered in a directory service belongs to multiple user groups.
In user, the user name is displayed.
In detail, up to two user group names are displayed.
When this message is displayed during operation, the directory service information may have been modified.
[Corrective Action]
Check the user information and use group information registered in the directory service. Operation by a user belonging to multiple user groups is not possible. Set the displayed user as a member of an appropriate user group.
[Description]
The resource information of a directory service does not match the manager internal information. In detail, the name of a problematic resource is displayed.
[Corrective Action]
Execute the rcxadm authctl sync command.
[Description]
There is an error in the assignment of the role registered in the directory service. Multiple roles assigned to one user are pointing to the same access scope.
In user, the user name or the name of the user group that the user belongs to is displayed.
In detail, the access scope is displayed in DN format.
[Corrective Action]
Check the role of the user registered in the directory service.
Operations using multiple roles that are assigned to one user and pointing to the same access scope cannot be allowed. Set a proper role for the user who is being displayed.
[Description]
A timeout error occurred during command execution.
[Corrective Action]
When this message is displayed during execution of the rcxbackup command or the rcxrestore command, there are the following possibilities:
An operation being executed on the admin server remains in the database.
The manager was stopped or started during command execution.
Perform the following corrective actions for each command:
When executing the rcxbackup command:
Start the admin server and complete the operation being executed on the admin server, or restore the configuration definition information already collected, then perform the operation again.
Check that the manager has not been stopped or started, then perform the operation again.
When executing the rcxrestore command:
Check that the manager has not been stopped or started, then perform the operation again.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the following cases:
Either an internal error has occurred or the XML file specified during the following operations has been loaded:
L-Server creation or configuration modification
Importing an L-Server template
Importing for DR
Creating network resources
When executing backup and restoration of configuration definition information
[Corrective Action]
When executing the following operations:
L-Server creation or configuration modification
Importing an L-Server template
Importing for DR
Creating network resources
Review the content of the XML specified during operations, then perform the operation again.
When executing backup and restoration of configuration definition information
There is the possibility that the manager was stopped or started during execution of the rcxbackup command or the rcxrestore command.
Check that the manager is not stopped or not started, then perform the operation again.
There is a possibility that the database could not be accessed.
Execute the rcxbackup command or the rcxrestore command again.
This message may be output after cancelling execution of rcxbackup command or the rcxrestore command by pressing "Ctrl + C".
Corrective action is not necessary because the execution has been canceled correctly.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
process timed out during an image operation.
Refer to the explanation in "Message number 68253" in "ServerView Resource Coordinator VE Messages".
[Corrective Action]
Refer to the corrective action described in "Message number 68253" in "ServerView Resource Coordinator VE Messages".
When process is reboot, check the corrective action for "Message number 68259".
[Description]
The process for the disk was aborted.
Refer to the explanation in "Message number 68259" in "ServerView Resource Coordinator VE Messages".
[Corrective Action]
Refer to the corrective action described in "Message number 68259" in "ServerView Resource Coordinator VE Messages".
There is also the following case for Resource Orchestrator.
When a managed server is configured for iSCSI boot
Check that there are no problems in the connection between the storage unit and the managed server.
[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 a physical L-Server
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 a physical L-Server
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".
For "Oracle VM 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, perform the following corrective action:
Check that Oracle VM Manager is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the Oracle VM Manager manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "Oracle VM Manager communication error"
Check that Oracle VM Manager is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the Oracle VM Manager 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. For details, refer to "Appendix F Configuration when Creating a Physical L-Server" in the "ServerView Resource Orchestrator User's Guide".
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 the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
