This section explains the 625XX message series.
[Cloud Edition]
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 elements and values specified in key.
Creating an L-Server
For details on the elements and the values, refer to "14.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 "14.3.1 Definition Information for Physical L-Servers (XML)" or "14.3.2 Definition Information for Virtual L-Servers (XML)" in the "Reference Guide (Command/XML) CE".
Importing an L-Server template
For the elements and values, refer to "14.2 L-Server Templates" in the "Reference Guide (Command/XML) CE".
Registration of iSCSI boot information
For the elements and values, refer to "14.4.2 iSCSI Boot Information" in the "Reference Guide (Command/XML) CE".
Registering or changing disk resources for a VM guest
Take corrective action based on the content of key.
"Storage"
It is necessary to define the Storage element.
"Pool"
It is necessary to define the Pool element.
"Pool.name"
It is necessary to define the name attribute for the Pool element.
"VmHosts"
It is necessary to define a VmHosts element.
"VmHost"
It is necessary to define a VmHost element.
"VmHost.ip"
It is necessary to define the ip attribute for the VmHost element.
"VmHost(ip=IP address of the VM host defined in XML).Disks"
It is necessary to define a Disks element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk"
It is necessary to define a Disk element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk.name"
It is necessary to define the name attribute in the Disk element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in the XML).size"
It is necessary to define the size attribute for the Disk tag to which disk resource name defined in XML is specified for name, in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in XML).path"
It is necessary to define the path attribute for the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"Disk(name=disk resource name specified in -name of rcxadm disk modify)"
It is necessary to define the Disk element to which the disk resource name specified in -name of rcxadm disk modify is specified for the name attribute in the XML.
For the elements and values, refer to "14.4.1 Disk Resources [KVM]" in the "Reference Guide (Command/XML) CE".
When importing network configuration information, creating a network device, or executing the rcxnetworkservice command
For the elements and values, refer to "14.6.1 Creating" in the "Reference Guide (Command/XML) CE".
If this message is output when creating or modifying a virtual L-Server
Review the settings in the dialog, and perform the operation again.
If this message is output when starting a virtual L-Server
Check the values in the L-Server definition settings, and perform the operation again.
Take corrective action based on the content of key.
"OSSetting.AdminPassword"
Specify the "Administrator password" on the [OS] tab.
"OSSetting.DNSSearchPaths.DNSSearchPath"
Specify the "DNS Search Path" on the [OS] tab.
For the values, refer to "Chapter 16 Creating L-Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"port group"
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 importing DR
Check the content of the XML file specified when operating the server, and correct the elements and values specified in key.
If this message appears when linking a configured virtual machine with an L-Server and key is "CPU.NumOfCPU"
Confirm that the VM host is managed by the VM management software and then perform the operation again.
[Cloud Edition]
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 ROR console
Description
Registration of the storage management software obj failed, because an error occurred during storage management software control.
Corrective Action
Take corrective action based on the content of detail.
When detail is "version unmatch. [version_of_the_storage_management_software]"
The version of the storage management software is incorrect. Use a supported version.
When detail is "service is not run."
The storage management software has not been started. Start the storage management software.
When detail is "invalid storage management software name"
The name specified for the -soft_name option is incorrect. Specify the correct name.
When detail is "one or more option is short"
A necessary option has not been specified. Specify necessary options.
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 is already registered. Storage management software that has already been registered cannot be registered.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
An error occurred during the control of storage management software, so registration of the storage management software obj failed.
Corrective Action
Take corrective action based on the content of detail.
"version unmatch. [version_of_the_storage_management_software]"
There is an error in the version_of_the_storage_management_software. Use a supported version.
"service is not run."
The storage management software is not operating. Start the storage management software.
"invalid storage management software name"
There is an error in the name specified for the -soft_name option. Specify the correct name.
"one or more option is short"
A required option has not been specified. Specify the required option.
"one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
"storagemgr is already registered"
The specified storage management software has already been registered. Storage management software that is already registered cannot be registered.
"ip address:invalid format"
There is an error in the specified IP address. Specify the correct IP address.
"port:invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
"port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
"command failed."
Storage management software may not be able to be used. Check whether storage management software is available.
In the following cases, storage management software is unavailable. Check that the preparations have been completed, referring to "10.1.1 Allocating Storage" in the "Design Guide CE".
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 this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.
[Cloud Edition]
Description
An error occurred during control of storage management software, so changes to the configuration of the storage management software obj failed.
Corrective Action
Take corrective action based on the content of detail.
"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 how to modify the settings for VM management software, refer to "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
"ip address:invalid format"
There is an error in the specified IP address. Specify the correct IP address.
"port:invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
"port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
"storagemgr is registered as iSCSI controller"
This command cannot change resources, as the disk used for iSCSI boot has been registered.
If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.
Description
Deletion of the storage management software obj failed, because an error occurred during storage management software control.
Corrective Action
Take corrective action based on the content of detail.
"storagemgr is registered as VM management software"
This command cannot be used to delete storage management software, because it is registered as VM management software.
For details on how to delete VM management software, refer to "11.5 Deleting VM Management Software" in the "User's Guide VE".
When detail is "one or more SPARC Enterprise servers are defined as spare servers."
When configuring a SPARC Enterprise server as a spare server, the ESC manager deletion command (rcxadm storagemgr unregister) cannot be used.
Release the spare server settings of all SPARC Enterprise servers, and then delete the ESC manager.
When detail is "WWN information for one or more SPARC Enterprise servers are still remained."
When configuring WWN information in a SPARC Enterprise server, the ESC manager deletion command (rcxadm storagemgr unregister) cannot be used.
Delete all SPARC Enterprise servers in which WWN information is configured from Resource Orchestrator, and then delete the ESC manager.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
An error occurred in the control of the storage management software, so deletion of the storage management software obj failed.
Corrective Action
Take corrective action based on the content of detail.
"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 how to delete VM management software, refer to "9.6 Deleting VM Management Software" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"storagemgr is registered as iSCSI controller"
This command cannot delete resources, as the disk used for iSCSI boot has been registered.
If this does not resolve the problem, or messages other than the above are output for detail, collect troubleshooting information and contact Fujitsu technical staff.
[Cloud Edition]
Description
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.
[Cloud Edition]
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.
[Cloud Edition]
Description
The resource resource_name cannot be selected.
In resource_name, the resource name is displayed.
In detail, the following detailed information is displayed:
"physical_server is user not privileged"
Cannot be selected because the physical server does not have access privileges.
"physical_server is not selectable status"
Cannot be selected because the status of the physical server is error.
"physical_server is specified spare server"
Cannot be selected because the specified physical server has been configured as a spare server in the server resource tree.
"physical_server is not preserved by lserver lserver"
Cannot be selected because the physical server is being used as another L-Server.
"physical_server is already set up"
Cannot be selected because a server profile has been allocated to the physical server.
"invalid model name"
Cannot be selected because there is an error in the model name of the physical server.
"physical_server is incompatible model model and model"
Cannot be selected because the model of the physical server is incompatible.
"physical_server can not get spec cpu or memory"
Cannot be selected because the information about the CPU or memory of the physical server cannot be obtained.
"physical_server spec is low"
Cannot be selected because the information about the CPU, memory, NIC, and FC of the physical server does not meet the defined conditions.
"physical_server is not blade. fc-connection pattern is valid only blade."
[FC connection pattern] is valid with blades only.
"admin LAN pair is not the same between index and index"
Cannot be selected because the combination of the admin LAN pair of the physical server is different from the definitions for physical L-Server creation.
"physical_server is search locked"
Failed because multiple operations of physical L-Server creation were performed at the same time.
"physical_server is search locked"
Cannot be selected because the physical server is used for multiple processes.
"physical_server is preserved. but lserver is repurpose false"
Cannot be selected because the physical server has been released while resource release was not specified when creating the L-Server.
"server type is not the same between"
Cannot be selected because the server type (blade server or rack mount server) of the physical server is different from the definition.
"Virtual I/O type is not the same between"
Cannot be selected because the virtualization method of the physical server is different.
"admin LAN position is not the same between index and index"
Cannot be selected because the position of the admin LAN of the physical server is different from the definitions for the physical L-Server.
"model not supported"
The physical server cannot be selected, as it is not supported.
"is maintenance mode"
Cannot be selected because the physical server is in maintenance mode.
Corrective Action
Take the following corrective action based on the content of detail.
"physical_server is user not privileged"
Grant the physical server access privileges and perform the operation again.
"physical_server is not selectable status. state status"
Check the status of the physical server, and then perform the operation again.
"physical_server is specified spare server"
Cancel the spare server settings, and then perform the operation again.
"physical_server is not preserved by lserver lserver"
Change the physical server status to unused, and then perform the operation again.
"physical_server is already set up"
Check the status of the physical server, and then perform the operation again.
"invalid model name"
Review the model name that was specified during creation of the physical L-Server, then perform the operation again.
"physical_server is incompatible model model and model"
Check the model compatibility of the physical server, and then perform the operation again.
For details, refer to "Table 17.1 List of Items Specified in Definition Files for Checking Spare Server Models and Configurations" in "17.1.1 L-Server High Availability" in the "Operation Guide CE".
"physical_server can not get spec cpu or memory"
Confirm that the CPU and memory information of the physical server has been configured, and then perform the operation again.
"physical_server spec is low"
Review the CPU, memory, NIC, and FC (*) information that was specified during creation of the physical L-Server, and then perform the operation again.
* Note: A physical server cannot be found that has the number of FCs specified in the FC connection pattern.
Refer to "10.1.2 Storage Configuration" in the "Design Guide CE" for information on how to obtain the FC information for the physical server.
"physical_server is not blade. fc-connection pattern is valid only blade."
[FC connection pattern] is valid with blades only.
"admin LAN pair is not the same between"
Confirm that the admin LAN information of the physical L-Server and physical server has been configured, and then perform the operation again.
"physical_server is search locked"
Multiple operations of physical L-Server creation were performed at the same time. Perform the operation again.
"physical_server is search locked"
Check if the physical server is being used for multiple processes, and then perform the operation again.
"physical_server is preserved. but lserver is repurpose false"
Specify resource release when creating the physical L-Server, then perform the operation again.
"server type is not the same between"
Confirm the server type (blade server or rack mount server) used when creating the physical L-Server and then perform the operation again.
"Virtual I/O type is not the same between"
Check the virtualization method setting for the physical server, and then perform the operation again.
"admin LAN position is not the same between index and index"
Check the physical L-Server definition and admin LAN position between physical servers, and then perform the operation again.
"model not supported"
Review the model name that was specified during creation of the physical L-Server, then perform the operation again.
"is maintenance mode"
Release the physical server from maintenance mode or review the specified value, and then perform the operation again.
[Cloud Edition]
Description
An address outside of the specifiable address scope was specified when performing the following operations:
Creating an L-Server
Changing Network Configuration
Registering Managed Servers
Changing Managed Servers
In address, the specified address is displayed.
In start, the start value of the subnet address or start value of the address set resource is displayed.
In end, the end value of the subnet address or end value of the address set resource is displayed.
In resource name, the name of either the network resource or address set resource is displayed.
Start value and end value are included in the specifiable scope.
Corrective Action
Specify an address within the specifiable scope, and perform the operation again.
[Cloud Edition]
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
Take corrective action based on the content of %2.
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, "5.17 rcxadm storagemgr" in the "Reference Guide (Command/XML) CE".
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.
[Cloud Edition]
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.
When using ETERNUS storage other than ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series
When %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.
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.
The disk resource may be being used by another server.
When %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.
When using ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series storage
When %2 is "ERROR:ssmgr3514:The specified value 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.
Corrective Action
When using ETERNUS storage other than ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series
When %2 is "ERROR:ssmgr3419:The specified alias name has already been registered."
Refer to "Corrective Actions for ETERNUS Storage".
When %2 is "ERROR:ssmgr3422:As for specified volume Volume_number, the LUN mapping is done."
Refer to "Corrective Actions when Disk Resource Connection Failed".
When %2 is "ERROR:ssmgr3419:The specified alias name has already been registered."
Refer to "Corrective Actions for ETERNUS Storage".
When any other message is displayed
Performing corrective actions referring to the ETERNUS SF Storage Cruiser manual, and then perform the operation again
When using ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series storage
Refer to "Corrective Actions for ETERNUS Storage".
When the target storage is EMC CLARiiON, EMC Symmetrix DMX or EMC Symmetrix VMAX
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 "Chapter 18 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.
Corrective Actions for ETERNUS Storage
Using the following procedure, identify the overlapping affinity group, delete the unnecessary affinity group or the unnecessary affinity group and the Volume defined in the unnecessary affinity group, and then create the L-Server again.
Check the resource name of the unused address set resource (WWN) with the smallest number.
Execute the following command:
>Installation_folder\SVROR\Manager\bin\rcxadm addrset show -name Resource_name_of_the_Address_Set_Resource(WWN) <RETURN> |
Identify the unused address set resource (WWN) with the smallest number.
The range of the "start" and "end" inside the AddressSet tag becomes the range of the Address set resource (WWN).
In the range of address set resources (WWN), all addresses other than those below are considered unused address set resources (WWN).
Addresses which are not used for management by Resource Orchestrator, and are displayed in the Exclude tag
Addresses which have been allocated, and are displayed in the Reserve tag
From the unused address set resources, identify the one with the smallest number.
Example
When the output result is the one below, the resource name of the unused address set resource (WWN) with the smallest number will be "20:01:00:17:42:50:00:02".
<?xml version="1.0" encoding="utf-8"?>
<AddressSet name="wwndata1" id="540" label="wwn1" subnet="" mask="" start="20:01:00:17:42:50:00:00" end="20:01:00:17:42:50:00:0f">
<Comment>wwn-test-data-1</Comment>
<Exclude>
20:01:00:17:42:50:00:00
</Exclude>
<Reserve>
20:01:00:17:42:50:12:01 AM
</Reserve>
</AddressSet> |
Identify the alias name of the affinity group created when creating ETERNUS storage during L-Server creation.
Extract the characters corresponding to "XX" below from the resource name of the unused address set resource (WWN) with the smallest number. These characters become the alias name of the affinity group created when creating ETERNUS storage.
"YY:XX:YY:YY:YY:XX:XX:XX" |
Example
For "20:01:00:17:42:50:00:02" it would be "01500002".
Identify the affinity group to delete.
Execute the following command to display the affinity groups of each ETERNUS storage that is managed using ESC.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address <RETURN> |
Check if the alias name of the affinity group identified in 2. is included in the affinity group alias names displayed in "NAME".
If the alias name is included
The relevant affinity group will be the target of deletion.
If the alias name is not included
Collect troubleshooting data, and then contact Fujitsu technical staff.
Check the affinity group number that is displayed for "NUMBER" of the relevant affinity group.
Check if the HBA to use the affinity group exists.
Executing the following command displays the affinity group number, which is used from the host and from the WWPN of the HBA that uses ETERNUS.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone info -hex <RETURN> |
The lines after the output result of "<<< FC CA Zone Information >>>", the affinity group numbers that are used from the VM host and from the WWPN of the HBA that uses ETERNUS are collectively displayed for each storage unit.
For the target ETERNUS, check if the affinity group number identified in step 3. is included.
There may be multiple relevant lines.
If an affinity group number is not contained
There is an HBA which uses the relevant affinity group number.
When access to ETERNUS from the VM host using the relevant HBA is not necessary
Check the WWPN of the CA that is displayed for "CA_WWPN" and the WWPN of the HBA that is displayed for "HBA_WWPN", then execute the following procedure.
When access to ETERNUS from the VM host using the relevant HBA is necessary
Collect troubleshooting data, and then contact Fujitsu technical staff.
If an affinity group number is not contained
Execute step 6.
Delete the definition of the HBA that uses the affinity group number.
Executing the following command deletes all definitions of HBAs that were checked in step 4.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone delete -storage CA_WWPN,Affinity_group_number -hba HHBA_WWPN -update all <RETURN> |
Identify the volume to delete.
Execute the following command to display the volume numbers of each Volume defined in the affinity group identified in step 3.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
The Volume with the volume number matching that displayed in "VOLUME" becomes the target of deletion.
Delete the affinity group.
Execute the following command to delete the affinity group identified in step 3.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity delete -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
Decide whether the Volume should be deleted.
Do not delete the Volume when the volume number identified in step 6. corresponds to the LUN created in advance.
The LUN created in advance can be checked by the following method.
Execute the following command: Check that the IP address of ETERNUS is displayed for "UNIT_NAME", and examine the line where "VOLUME_ID" contains the volume number confirmed in step 6.
>Installation_folder\SVROR\Manager\bin\rcxadm disk list -verbose <RETURN> |
When "Yes" is displayed for "PRE_CREATED" in the relevant line
It is not necessary to delete the Volume, as the Volume is the LUN created in advance.
When "No" is displayed for "PRE_CREATED" in the relevant line
It is necessary to delete the Volume, as the Volume is not the LUN created in advance. Proceed to the following procedure.
Delete the Volume.
Execute the following command to delete the Volume identified in step 6.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm volume delete -ipaddr ETERNUS_IP_address -volume Volume_number[,Volume_number,...] <RETURN> |
When any other message is displayed from the storage management software, refer to the manual of the storage management software, take the necessary corrective action for the message, and then perform the operation again.
Corrective Actions when Disk Resource Connection Failed
If a Volume corresponding to a disk resource that has wrongly been specified from another server was being used, delete the mapping definition of the Volume to cancel the relation to the server. After that, connect the disk resource to the L-Server again.
Check the affinity group number of each ETERNUS storage.
Execute the following command to display the affinity groups of each ETERNUS storage that is managed using ESC.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address <RETURN> |
Check all affinity group numbers that are displayed for "NUMBER".
Check the details of each affinity group to identify the affinity group numbers that have been defined for the mapped Volume.
Using the affinity group numbers checked in 1., view the Volume number defined for each affinity group. Find the affinity group with the volume number "VOLUME" displayed in the message.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
Delete a Volume from the affinity group.
When the affinity group has multiple mapping definitions
Execute the following command to delete the Volume from the affinity group that was checked in 2., which corresponds to the volume number that is displayed in the message.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity update -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number -delete -volume Volume_number <RETURN> |
When the affinity group has only one mapping definition
Check HBAs that use the affinity group, then delete the definition of the HBA.
After that, delete the affinity group.
Executing the following command displays the affinity group number, which is used from the WWPN of the CA of ETERNUS, from the WWPN of the HBA that uses ETERNUS, and from the server.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone info -hex <RETURN> |
In the lines after the output result of "<<< FC CA Zone Information >>>", the affinity group numbers that are used from the WWPN of the CA of ETERNUS, from the WWPN of the HBA that uses ETERNUS, and from the server are collectively displayed for each storage unit.
Check the WWPN of the CA and HBA which correspond to the affinity group.
Execute the following command to delete the definition of an HBA.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone delete -storage CA_WWPN,Affinity_group_number -hba HHBA_WWPN -update all <RETURN> |
Execute the following command to delete an affinity group.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity delete -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
[Cloud Edition]
Description
The file format specified for filename is incorrect.
The details of the error are displayed for %1.
Corrective Action
When executing the rcxstorage command:
Take corrective action based on the content of %1.
"specified target volume not found in ROR (line:n)"
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.
"number of column must be 4 (line:n)"
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.
"empty file"
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.
"field missing a value (line:n)"
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.
"definition conflict with line m (line:n)"
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.
"specified target volume not found in ROR (line:n)"
The disk resource corresponding to the target RAID group or TPP for replication specified on line n of the mirroring definition file specified for filename has not been detected and displayed in the resource tree. Check that the target RAID group or TPP for replication is correctly specified, and then execute the command again.
When executing the rcxnetworkservice command:
Take corrective action based on the content of %1.
"Netdevice.MgmtInfos.LoginInfos.LoginInfo.PrivilegedPassword is not same"
Make the NS Appliance administrator password the same for all of the login accounts.
"no NSAppliance found"
NS Appliance information was not found in the specified network configuration information file. Specify a network configuration information file with NS Appliance information.
[Cloud Edition]
Description
Registration of the resource resource_name has failed.
In resource_name, the name of the virtual storage resource or the disk resource is displayed. When multiple resources are operated using one operation, only the first resource name an inconsistency was detected for is displayed.
In resource_type, "vstorage" or "disk" is displayed.
When detail is "attribute of thick/thin provisioning conflicts with target"
Failed due to inconsistencies in the attribute combination of thin provisioning or thick provisioning with the destination storage pool for registration or movement.
In target, the name of the storage pool is displayed.
Corrective Action
Check the content displayed in detail, and then perform the operation again.
When detail is "attribute of thick/thin provisioning conflicts with target"
Make sure that there are no inconsistencies in thin or thick provisioning attributes between resource_name and target, and then perform the operation again.
If this message is output when detaching a disk from a virtual L-Server, either move the virtual storage in which that disk exists to an appropriate thin/thick pool, or create an appropriate thin/thick disk and copy the data to that disk, and then perform the operation again.
[Cloud Edition]
Description
No available VM host was found.
The error may be the result of one of the following:
There is no object that meets the conditions
Creation of an L-Server from the ROR 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
In environments where Hyper-V VM hosts without Windows Server 2008 R2 Service Pack 1 (SP1) or SCVMM that has not been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later are being used, one of the following operations was performed:
Creation of an L-Server for which dynamic memory is enabled
Enabling of dynamic memory using L-Server specification changes
In environments where an SCVMM that has not been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later is being used, the following operation was performed:
Creation of an L-Server specifying a disk that was allocated from a virtual storage and saved
Corrective Action
Take corrective action based on the content of detail.
"one of power status, monitoring status, or maintenance mode is invalid"
Perform the operation again after checking whether a VM host in the following state exists:
Power is ON
Monitoring status is normal
Maintenance mode is not set
Maintenance mode has not been set for the server virtualization software
"no other available VM host found"
When performing migration, if this message is output, take the following corrective action according to the values specified during migration:
When specifying [Automatic Selection] for the destination VM host, or when executing the rcxadm lserver migrate command without specifying the -to option)
The resources used by the L-Server do not contain a VM host that satisfies the conditions described in "one of power status, monitoring status, or maintenance mode is invalid", except the one to migrate.
As the VM host that the L-Server is currently deployed on is set as a resource (VM host) for the L-Server to use, it is not possible to automatically select another VM host as the destination.
Specify the destination VM host, and then perform the operation again.
For how to confirm the resources to use, refer to "17.7 Migration of VM Hosts between Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When specifying [VM host] for the destination VM host, or when executing the rcxadm lserver migrate command specifying the -to option)
The specified VM host does not satisfy the conditions described in "one of power status, monitoring status, or maintenance mode is invalid". Specify another VM host, and then perform the operation again.
"not enough CPU or memory available"
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.
"there is a VM host with sufficient reservation capacity, but not enough CPU or memory"
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.
"no sharable datastore found"
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 how to confirm the VM host to use, refer to "17.7 Migration of VM Hosts between Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If this message is output when creating or starting a virtual L-Server that has disk resources that were created (and saved) from virtual storage, check all such disk resources connected to the L-Server and ensure that a VM host that can access the datastore which generated such disk resources exists, and then perform the operation again.
"no valid HA configuration of the server virtualization software found"
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
[Solaris Containers]
After confirming that spare servers are configured on VM hosts, perform the operation again.
"no accessible VM host or VM pool found"
Check the following and perform the operation again.
That there is an accessible VM pool
That there is a VM host in the VM pool
When an L-Server has been created without configuring overcommit, depending on the VM host selection status, confirm the following:
When [Automatic Selection] is selected
If a VM pool for which overcommit is not configured exists in the accessible area, and if a VM host exists under the VM pool
When [VM Pool] is selected
If overcommit is not configured in the specified VM pool, and if a VM host exists under the VM pool
For details on overcommit, refer to the "Overcommit" section of the server virtualization software to use in "Appendix C Configuration when Creating Virtual L-Servers" in the "Setup Guide CE".
[Hyper-V]
Check if Windows Server 2008 R2 Service Pack 1(SP1) has been applied to the VM hosts and if SCVMM has been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later. If not, apply the appropriate Service Pack and then perform the operation again. When not applying Service Pack, disable dynamic memory and the priority of memory allocation, and perform the operation again.
"no accessible VM pool for over commit found"
Check the following and perform the operation again.
That there is a VM pool for overcommit and that there is a VM host under that VM pool
That both VM pools (the one that is set for overcommit and the one that is not) are inside the access scope
For details on overcommit, refer to the "Overcommit" section of the server virtualization software to use in "Appendix C Configuration when Creating Virtual L-Servers" in the "Setup Guide CE".
[Hyper-V]
Check if Windows Server 2008 R2 Service Pack 1 (SP1) has been applied to the VM hosts and if SCVMM has been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later. If not, apply the appropriate Service Pack and then perform the operation again. When not applying Service Pack, disable dynamic memory and the priority of memory allocation, and perform the operation again.
"combination of image and VM host combination is incorrect"
A template corresponding to the cloning image to deploy and the VM host to which 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 how to check the VM host status and free space, refer to "20.6 Viewing a Resource Pool" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"product version of VM management software"
Check if the SCVMM being used has been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later. If not, upgrade the SCVMM and then perform the operation again.
[Cloud Edition]
Description
The specified VM host cannot be used.
The error may be the result of one of the following:
The specified VM host does not satisfy the conditions for the given operation
Migration between VM hosts has been performed with a specific VM host set as the VM host used for an L-Server
Creation of an L-Server from the ROR 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
In environments where Hyper-V VM hosts without Windows Server 2008 R2 Service Pack 1 (SP1) or SCVMM that has not been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later are being used, one of the following operations was performed:
Creation of an L-Server for which dynamic memory is enabled
Enabling of dynamic memory using L-Server specification changes
Corrective Action
Check the content displayed in detail, and take corrective actions described in "Message number 62514".
[Cloud Edition]
Description
The port combination for the storage unit at storage_unit_ipaddr is not defined in the port combination definition file for SAN storage "storage_portset.rcxprop".
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should define the port combination for the storage unit at storage_unit_ipaddr, referring to "B.1.1 Creating Definition Files Combining Ports of SAN Storage" or "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Cloud Edition]
Description
In the port combination definition file for SAN storage, "storage_portset.rcxprop", an unavailable port is defined for the port combination for the storage unit at storage_unit_ipaddr.
In port, the unavailable port that is defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is displayed.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "B.1.1 Creating Definition Files Combining Ports of SAN Storage" or "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Cloud Edition]
Description
Duplicate port combinations are defined for the storage unit at storage_unit_ipaddr in the port combination definition file for SAN storage "storage_portset.rcxprop".
In port, the duplicate port that is defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is displayed.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "B.1.1 Creating Definition Files Combining Ports of SAN Storage" or "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Cloud Edition]
Description
The port combination for the storage unit at storage_unit_ipaddr defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is not defined using a port pair.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "B.1.1 Creating Definition Files Combining Ports of SAN Storage" in the "Setup Guide CE".
[Cloud Edition]
Description
More than one key is specified.
Corrective Action
If this message is output during the following operation, after reviewing the content of the XML file specified during the operation, ensure that there is only one entry for the element specified in key, and perform the operation again.
When key is "Pool"
Ensure that only one Pool element is defined.
When key is "VmHosts"
Ensure that only one VmHosts element is defined.
When key is "VmHost(ip=IP address of VM host defined in XML)"
Ensure that only one VmHost element to which an IP address of the VM host defined in the XML is specified for ip is defined.
When key is "VmHost(ip=IP address of VM host defined in XML).Disks"
Ensure that only one Disks tag is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
When key is "VmHost(ip=IP address of the VM host defined in the XML).Disks.Disk(name=Disk resource name defined in XML)"
Ensure that only one Disk element to which the disk resource name defined in the XML is specified for name is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
When key is "VmHost (ip=IP address of the VM host defined in XML).Disks.Disk(path=Device path to the disk resource defined in XML)"
Ensure that only one Disk element to which the device path to the disk resource defined in the XML is specified for path is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
[Cloud Edition]
Description
The port combination of the storage unit of the storage_unit_ipaddr file defined by the SAN storage port combination is not defined in the 2 port combination.
storage_unit_ipaddr
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
pattern
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
Refer to "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the port combinations for storage_unit_ipaddr storage unit (as infrastructure administrator).
[Cloud Edition]
Description
The port combination of the storage unit of the storage_unit_ipaddr file defined by the SAN storage port combination is defined using an invalid number of ports.
storage_unit_ipaddr
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
pattern
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
Corrective Action
Notify the infrastructure administrator of the information in this message.
Refer to "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the port combinations for storage_unit_ipaddr storage unit (as infrastructure administrator).
[Cloud Edition]
Description
The number of columns is not num in the line item of the file displayed in filename.
Corrective Action
Check the line item in the file displayed in filename and confirm that the number of columns is num.
[Cloud Edition]
Description
Field value has not been specified in the line item of the file displayed in filename.
Corrective Action
Check the line item in the file displayed in filename and confirm that a field value has been specified.
[Cloud Edition]
Description
Invalid field value in the line item of the file displayed in filename.
Corrective Action
Check the line item in the file displayed in filename and confirm that field value is correct.
"storage_mirroring.rcxprop" is displayed in filename
Check the following:
The RAID group number or TPP number is a hexadecimal of 4 digits starting with 0x.
The virtual storage type is "RAID" or "TPP".
[Cloud Edition]
Description
In the file displayed in filename, the item definitions for the storage unit of ip-address are duplicated.
item
BOX-ID Storage unit BOX-ID of ETERNUS
RAID Storage unit RAID group number of ETERNUS
TPP Storage unit TPP number of ETERNUS
value
Value of the item where definitions are duplicated
Corrective Action
In the file displayed in filename, check that the definitions for the storage unit of ip-address are not duplicated.
"storage_mirroring.rcxprop" is displayed in filename
Take corrective action based on the content of item.
BOX-ID
There are multiple remote site storage units specified as remote site storage units. Review the definition.
RAID
The RAID Group number on the local is duplicated. Review the definition.
TPP
The TPP number on the local is duplicated. Review the definition.
Description
resource does not exist in target or it was deleted from target while processing it.
detail is displayed when there is detailed information.
[Solaris Containers]
When resource is "NIC(Network_interface_Name)"
The network interface corresponding to the specified network resource does not exist on a VM host.
The relationships of network resources and network interfaces are described in the virtual network definition file (vnetwork_solariscontainer.rcxprop).
When the network interface name described in the virtual network definition file is the physical point of attachment of a VLAN, the following is displayed for detail.
(interface-PPA=VLAN_physical_point_of_attachment) |
Corrective Action
Confirm whether resource exists in target, then perform the operation again after reviewing the specified settings.
[Solaris Containers]
When resource is "NIC(Network_interface_Name)"
After reviewing the following, perform the operation again.
Whether the correct network interface name is described in the virtual network definition file (vnetwork_solariscontainer.rcxprop)
Whether there are any mistakes in the network resource settings
[Cloud Edition]
Description
resource matching conditions does not exist in target.
The condition that was not found is displayed in detail.
When creating or starting an L-Server, the resource name that this product retrieved in processing is displayed in target.
When you set the resource (VM host, physical server, and disk, etc.) using Auto Select, the list of the resources retrieved is displayed as follows.
"/Tenant name (pool name[,pool name]...)"
Corrective Action
Confirm whether a resource matching the conditions exists in target, then perform the operation again after reviewing the specified settings.
If this message is displayed when creating or starting an L-Server, review the specified settings for the L-Server and then perform the operation again.
[Cloud Edition]
Description
obj cannot be specified for condition.
detail is displayed when there is detailed information.
The resource name, the XML element, or the value is displayed for obj.
When condition is "resource state is not registered"
As the resource has not been registered, it cannot be specified.
When condition is "not network device", "not registered status", "not registerable type", or "already registered in pool"
As the resource is not a network device, the status is not registered, the type cannot be registered, and the resource (including redundant resource) has been registered in the pool, it cannot be registered.
When condition is "cloning image name without disk configuration information"
As there is no disk information in the cloning image, the disk deployment configuration when specifying images (ServerImageLink.disk) cannot be specified.
Corrective Action
Perform the operation again after reviewing the settings specified for obj.
When condition is "resource state is not registered"
Wait until the resource is registered, and then perform the operation again.
When condition is "not network device", "not registered status", "not registerable type", or "already registered in pool"
"not network device", "not registerable type"
Check that the specified resource is appropriate, and perform the operation specifying an appropriate resource.
"not registered status"
Wait until the resource is registered, and then perform the operation again.
"already registered in pool"
As the resource (including redundant resources) has been registered in the pool, no action is required.
When condition is "cloning image name without disk configuration information"
Wait for around six minutes and then repeat the operation.
[Cloud Edition]
Description
obj1 cannot be specified for obj2.
detail is displayed when there is detailed information.
The command option or the XML tag is displayed in obj1.
The disk resource type or name is displayed in obj2.
When obj1 is "password" and obj2 is "User"
There may be an error in the value specified for the Password element in the user XML file or the value may have been specified for the Password element when not possible.
When obj2 is "Folder" or "L-Platform"
The obj1 tag cannot be specified for the XML of Folder or L-Platform.
When detail is "pool type is not matched"
For the pool type to create, obj1 cannot be specified.
Corrective Action
Perform the operation again after reviewing the combination of obj2 and obj1 and the settings.
When obj1 is "password" and obj2 is "User"
Review the value of the Password element in the user XML file, correct the definition, and perform the operation again.
When obj2 is "Folder" or "L-Platform"
Review the XML specification, and perform the operation again.
When detail is "pool type is not matched"
Review the pool type to create and the specified value, and perform the operation again.
[Cloud Edition]
Description
When executing the rcxadm logctl command
An incorrect value or time range was specified in option.
One of the following is output in option:
-from
-to
-duration
-from >= -to
In other cases
The option is not correctly specified.
Corrective Action
When executing the rcxadm logctl command
Refer to the command reference and specify a correct value or time range in option, then perform the operation again.
For details, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE"
In other cases
Check the explanation of the function that you executed and specify the correct value.
[Cloud Edition]
Description
The process process for the log operation failed.
In process, "read", "delete", or "copy" is output.
Corrective Action
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
Check if there is a quota limit or file system full message.
[Cloud Edition]
Description
You do not have access rights for obj.
When the target is an L-Server, you do not have access rights for the resources composing the L-Server.
detail is displayed when there is detailed information.
Corrective Action
Confirm whether obj is accessible.
When obj is not accessible, you should contact the infrastructure admin and perform the operation again after performing either of the following.
Move the resource registered in the resource pool to an accessible resource pool
Change the access scope of the affected user
[Cloud Edition]
Description
You do not have access rights for obj1 in obj2.
When the target is an L-Server, you do not have access rights for the resources composing the L-Server.
detail is displayed when there is detailed information.
Corrective Action
Confirm whether obj1 is accessible.
When obj1 is not accessible, you should contact the infrastructure admin and perform the operation again after performing either of the following.
Move the resource registered in the resource pool to an accessible resource pool
Change the access scope of the affected user
[Cloud Edition]
Description
obj1 for obj2 is not specified.
detail is displayed when there is detailed information.
When obj1 is "SystemDisk(DiskIndex=0)", SystemDisk has not been specified for the operating L-Server which is displayed in obj2.
Corrective Action
Perform the operation again after reviewing the settings and values specified for obj1.
When obj1 is "SystemDisk(DiskIndex=0)", perform the operation again after adding DiskIndex=0 tag under the Disk element.
[Cloud Edition]
Description
The configuration managed by Resource Orchestrator has already been migrated.
When configuration is "overcommit configuration"
The pool information for overcommit has already been migrated.
Corrective Action
No action is necessary because the configuration information has been migrated.
If configuration is "overcommit configuration" and pool.rcxprop has been modified, remove the modified section from the file (pool.rcxprop) and perform the corresponding modification for the pool configurations using the ROR console.
[Cloud Edition]
Description
obj1 and obj2 do not match.
detail is displayed when there is detailed information.
The resource name, the XML tag, or the value is displayed for obj1.
The information which does not match the resource type or other information is displayed in obj2.
When obj1 is VM type
The combination of the specified VM type and obj2 is not correct.
When obj1 is the resource name
The combination of the specified resource and obj2 is not correct.
Corrective Action
Perform the operation again after reviewing the combination of obj2 and obj1.
When obj1 is VM type
Change the combination of the specified VM type and obj2, and perform the operation again.
When obj1 is the resource name
Change the combination of the specified resource and obj2, and perform the operation again.
[Cloud Edition]
Description
The specified value is outside the allowed range.
The specified value is displayed for value.
The searched target resource name is displayed for targets.
When using automatic selection, the list of the specified resources is displayed as follows:
"all resources in searching /Tenant name (pool name[,pool name]...)"
Corrective Action
Review value or targets, and then perform the operation again.
[Cloud Edition]
Description
The specified resource was not found.
The address type or resource name is displayed in AddressType.
When AddressType is Address type
The searched target resource name is displayed for targets.
When using automatic selection, the list of the specified resources is displayed as follows:
"all resources in searching /Tenant name (pool name[,pool name]...)"
When AddressType is resource name
The searched target resource pool type is displayed for targets.
Corrective Action
Review AddressType or targets, and then perform the operation again.
[Cloud Edition]
Description
The address resources have been exhausted.
The resource type is displayed for AddressType.
The searched target resource name is displayed for targets.
When using automatic selection, the list of the specified resources is displayed as follows:
"all resources in searching /Tenant name (pool name[,pool name]...)"
Corrective Action
Add any available addresses into the address resource.
[Cloud Edition]
Description
The specified obj is not empty.
Corrective Action
Perform the operation again after emptying the specified obj.
[Cloud Edition]
Description
The resource in obj1 is already used by obj2. When multiple resources are operated using one operation, only the first resource name an inconsistency was detected for is displayed.
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 addrset 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.
If this message is output when modifying a managed server
Change the admin IP address of the physical L-Server displayed in obj2, and then perform the operation again.
If this message is output when deleting a managed server
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.
When a network device is modified or deleted
If necessary, change the resource so it is not used, and then perform the operation again.
[Cloud Edition]
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.
[Cloud Edition]
Description
The disk corresponding to the specified diskname is not recognized by vmhost.
In diskname, the name of the disk resource registered with the admin server is displayed.
The name may not be displayed depending on the registration status of the disk resource.
In vmhost, the name of the VM host registered with the admin server is displayed.
Corrective Action
Check and modify the storage settings so that the disk can be recognized by vmhost.
When the disk resource is not displayed, associate it with an L-Server, and perform the operation again.
[Cloud Edition]
Description
The value of item of filename is invalid.
item is NUM_OF_FC
the following is displayed in detail.
please specify the value as 1, 2, or 4
item is BOOT_FC_PORT
the following is displayed in detail.
please specify the value within the range of NUM_OF_FC
When item is STORAGE_0, one of the following is displayed for detail:
please specify the correct format
Corrective Action
Notify the infrastructure administrator of the information in this message.
Refer to "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the item value (as infrastructure administrator).
[Cloud Edition]
Description
The specified resource value does not exist in the source pool. One of the following is displayed in value.
Resource name
The resource may have been deregistered from the pool or it may have been moved to a different pool.
"" (empty string)
The resource may have been deleted.
Corrective Action
Check the content displayed in value, eliminate the cause of the error and then re-execute.
Resource Name
Deselect the value in the resource list, then retry. Alternatively, close the dialog box and try again.
In the case of "" (empty string)
Close the dialog box and try again.
[Cloud Edition]
Description
A pool that does not exist has been specified as the destination. The destination may have been deleted.
Corrective Action
Close the dialog box and check that the destination exists.
[Cloud Edition]
Description
A type other than a resource pool has been specified in dest, so the transfer is not possible. The resource pool specified at the destination must be the same as the resource type at the source.
Corrective Action
Change the destination and then try again.
[Cloud Edition]
Description
A pool type dest_type has been specified as the destination dest that differs from the pool type source_type for the source, so the transfer is not possible. The resource pool specified at the destination must be the same as the resource type at the source.
Corrective Action
Change the destination and then try again.
[Cloud Edition]
Description
An error occurred while performing the import process. The following information is stored in an error message:
type=type
Resource type where the error occurred (template, folder, pool, network, addrset, image, lserver, user, usergroup, firewall) is displayed.
message=message
Details of the error that occurred are displayed.
If the resource type is pool, addrset, lserver, network, or firewall, the following is also displayed.
name=name
The name specifying the resource where the error occurred is displayed. If the name cannot be determined, id = resource ID is displayed.
Example
(L-Server) : /tenant1/l-platform1/l_server1
The name part is not display for any other type.
Corrective Action
Take the following action for each of the error messages:
If this does not resolve the problem, collect this message and troubleshooting data, and contact Fujitsu technical staff.
type is template, folder, pool, network, addrset, user, usergroup
Refer to the message error message, take the appropriate action, then re-import.
type is lserver and the message is ":67154:VM Guest not found"
Use rcxadm config show to view the VM name, host name, and external identifier, then reregister the VM on the import destination.
If the VM is not included in the disk where storage replication was performed, remove the L-Server from the import configuration definition information, then perform import again.
type is lserver and the message is "67154:value:not found"
Use rcxadm config show to determine the resources relevant to the ServerType and value of the L-Server.
ServerType is Virtual, and "VirtualStorage name="value"" is in the relevant value
The virtual storage is not registered in a storage pool that can be viewed from the location where the L-Server is deployed. Check that the following resources (relevant to value in the VM management software registered with Resource Orchestrator) have been correctly registered, then perform import again.
vCenter: Data store name
SCVMM: Cluster Shared Volume name
If the resources are not registered with the VM management software, for example if virtual storage is not included in the disk where storage replication was performed
After removing the relevant L-Server from the configuration definition information for import, perform import again.
type is firewall and the message is "67154:ProvisioningNode(name=fw_device_name):not found"
Check if the network device for fw_device_name is registered in the network pool of the tenant for name.
If it has not been registered, check if fw_device_name has been registered using another name in the server tree. Ensure that it is correctly registered, and then perform import again.
If the network device cannot be registered because it does not exist in the destination environment, delete the name L-Platform, following the procedure described in "4.2 Switchover Operations when Damaged" in the "DR Option Instruction". During the deletion procedure, make a note of the L-Platform name, and delete the L-Platform after the import process is complete.
type is image, and the message is "67154:obj not found"
Check that there is VM management software with an image registered, or a VM host's server registered, if there is not one registered, register one and then perform import again.
In other cases
Refer to the message error message, take the appropriate action, then re-import.
[Cloud Edition]
Description
A resource identifier for import conflicts with another resource identifier.
The rcxadm config reserve command is not executed in the DR procedure.
Corrective Action
Install the manager again. After installation, following the DR procedure, execute the rcxadm config reserve command and the rcxadm config import command.
[Cloud Edition]
Description
Since the NICs specified in the index index for the L-Server server-name were created before the functions of addition or deletion of NICs were supported, the specified NIC cannot be deleted.
Corrective Action
Check the specified values for the NIC index of an L-Server, resolve the cause, and perform the operation again.
[Cloud Edition]
Description
There are no NICs with the specified MAC addresses mac-address that are allocated to VM guests related to the L-Server server-name.
Corrective Action
Check the MAC addresses of NICs from VM management software, and perform the operation again.
[Cloud Edition]
Description
The IP address of the storage unit has not been registered in the storage management product soft.
Corrective Action
Check the following, resolve the problem, and execute the command again.
The specified storage unit has been registered in the storage management product soft.
The IP address of the storage unit has been registered in the storage management product soft.
[Cloud Edition]
Description
Cannot find replication definition.
Corrective Action
After checking that the replication definitions have been correctly registered with the storage management product soft, retry.
[Cloud Edition]
Description
The IP address of the storage apparatus has not been registered in the storage management product soft.
Corrective Action
Perform one of the following corrective actions:
After setting the IP address of the storage apparatus in the storage management product soft, execute the command again.
Once the -local option is specified, specify the IP address and Box ID with the -remote option, then retry.
[Cloud Edition]
Description
The settings of the nth tag_name tag (name) in the definition file are incorrect. In detail_message, a message indicating the cause is displayed. All operations described in the definition file have not been completed.
Corrective Action
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, and execute the operation again.
[Cloud Edition]
Description
Operations of the nth User tag (user) in the definition file failed. In detail_message, a message indicating the cause is displayed. The user operations described before the user_id that caused an error in the definition file have been completed.
Corrective Action
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, create the definition files for after the user that failed, and execute the operation again.
[Cloud Edition]
Description
Operations of the nth Tenant tag (tenant) in the definition file failed. The message that is the cause is displayed in detail_message. All operations described in the definition file have not been completed.
Corrective Action
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, and execute the operation again.
[Cloud Edition]
Description
It is not possible to specify a user group that is used to manage tenants for the user group user_group of users with an infrastructure administrative role or multiple role.
Corrective Action
Specify a user group other than a user group used to manage tenants.
[Cloud Edition]
Description
The option option, which can only be specified once for a user with a tenant administrator role or tenant user role, has been specified multiple times.
Corrective Action
Specify only one option.
[Cloud Edition]
Description
One of following, which cannot be configured, was specified for the role role.
lplatform_user was specified for the role when creating a user.
Only lplatform_user was specified for the role when modifying a user.
Corrective Action
Configure the correct role.
When creating a user, specify a role other than lplatform_user.
When specifying lplatform_user, if modifying a user, also specify the tenant user role.
[Cloud Edition]
Description
One of following roles, which cannot be changed, was specified.
An attempt was made to change from a tenant management role or tenant user role to an infrastructure administrative role or a multiple role.
An attempt was made to change from an infrastructure administrative role or a multiple role to a tenant management role or tenant user role.
Corrective Action
When changing a role, specify a role in the following scopes:
When changing a tenant management role or a tenant user role, specify one of these two roles.
When changing an infrastructure administrative role or a multiple role, specify one of these two roles.
[Cloud Edition]
Description
An attempt was made to create a tenant tenant other than a root folder
Corrective Action
Create a tenant in the root folder.
[Cloud Edition]
Description
The tenant tenant with the same name as that of the user group cannot be created.
Corrective Action
For a tenant, specify a name other than the name of the current user group.
[Cloud Edition]
Description
An L-Platform exists under the tenant tenant.
Corrective Action
Check if the specified tenant name is correct. When the tenant name is correct, delete the L-Platform under the tenant.
[Cloud Edition]
Description
A user exists in the user group user_group used for managing tenants.
Corrective Action
Check if the specified tenant name is correct. When the tenant name is correct, delete the users belonging to the user group used for managing tenants.
[Cloud Edition]
Description
The user group user_group used for managing tenants cannot be changed or deleted.
Corrective Action
Check if the specified user group is correct. The user group managing a tenant is deleted, at the same time as the tenant is deleted.
[Cloud Edition]
Description
Necessary settings have not been configured in the tuning parameter file "file".
In param_names, all parameters that have not been configured are displayed.
If file is the definition file for alive monitoring
"alive_monitoring/definition file name.rcxprop" is displayed.
When file is the definition file for MAC address pools of System Center 2012 Virtual Machine Manager
"scvmm_mac_pool.rcxprop" or "scvmm_mac_pool_tenant_name.rcxprop" is displayed.
Corrective Action
If file is the definition file for alive monitoring
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the settings, referring to "B.1.8 Definition File for Alive Monitoring" in the "Setup Guide CE".
When file is the definition file for MAC address pools of System Center 2012 Virtual Machine Manager
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the settings, referring to "Definition File Format for MAC Address Pools" in "C.3.5 Manual Network Configuration" in the "Setup Guide CE".
[Cloud Edition]
Description
number license_name licenses are insufficient for the operation.
The name of license is displayed in license_name.
The number of licenses is displayed in number.
Corrective Action
Confirm that there is no mistake in the number of licenses required for the resource specified in the parameter. If there is no mistake, add number more license_name licenses to the ROR manager.
Description
In the VM host ip, a disk with the path path2 that overlaps with the path path1 already exists.
When registering multiple disk resources, this message is also displayed when the specified paths overlap.
Example
/work/zones/ror-zone |
An example of paths which overlap the path above is given below.
/work/zones/ror-zone/zone1
/work/zones
An example of paths which do not overlap the path above is given below.
/zones/ror-zone
/work/zones1/ror-zone
Corrective Action
If this message is output when registering disk resources
After changing the specified path or deleting the disk resource with the path that overlaps with the specified path, perform the operation again.
If this message is output when creating a virtual L-Server
After changing the specified disk resource or changing the path of the disk resource, perform the operation again.
If this message is output when migrating a virtual L-Server
After changing the path of the disk resource used for the VM host which is the migration destination of the specified L-Server, perform the operation again.
When one of the following problems occurs during creation of an L-Server, creation fails and VM guests being created on server virtualization software may remain.
System failure, or reboot of the admin server or manager
Job cancel or time out on server management software
Server switchover in which managers are operating using the HA function of cluster software or server virtualization software
Make sure that the manager is running, and use the following procedure for restoration:
Check the VM guest name in the event log of the ROR console.
The VM guest name is displayed for the resource name in the event log.
Check that no jobs of the BMC BladeLogic Server Automation Console are being executed.
Job names are displayed in the following format.
Start time of L-Server creation(*)_VM host name_VM guest name
*) YYYY-MM-DD_HH-MM-SS format
When a job is being executed, cancel that job.
Check from the BMC BladeLogic Server Automation Console whether there is a server with the requested VM guest name in the server folder.
If there is such a server, delete it.
After that, log in to the VM host for deployment, and delete the VM guest.
For details on how to delete VM guests, refer to the server virtualization software manual.
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in 1. does not exist, create the L-Server again.
For details on the operation of BMC BladeLogic Server Automation, refer to the BMC BladeLogic Server Automation documentation.
The BMC BladeLogic Server Automation documentation is located in the following location on the BMC BladeLogic Server Automation admin server.
When the BMC BladeLogic Server Automation admin server is Windows
Installation_folder\onlinedoc
When the BMC BladeLogic Server Automation admin server is Linux
/opt/bmc/bladelogic/onlinedoc
[Cloud Edition]
Description
In the settings of access scope of a user, the location cannot be identified from the specified resource name resource.
When using a user with multiple access scopes specified, it is necessary to specify the hierarchized folder name as a resource name.
Corrective Action
When using a user with multiple access scopes specified, access the access scope folder, and specify the resource name putting a slash "/" after the access scope folder name.
Description
The path path to the disk resource obj on the VM host ip has not been configured as a mount point.
Corrective Action
Check the storage environment and the mount settings.
For details, refer to "E.6.3 Storage Preparations" in the "Design Guide CE".
