This section explains the 659XX message series.
Description
Writing of backup information failed because a problem such as an I/O error occurred.
Corrective Action
Check the following, resolve the cause of the problem, and execute the command again.
The disk that the following folder exists on has 10 MB or more space available
[Windows Manager]
Installation_folder\SVROR\Manager\var\config_backup
[Linux Manager]
/var/opt/FJSVrcvmr/config_backup
Writing to the above disk is performed correctly
Writing and reading authority for the directory above has been set for the user executing the operation
All other operations have been completed
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
Export to the file specified for filename failed.
Corrective Action
After confirming the path to the specified file name, perform the operation again.
Description
The export process has failed.
Corrective Action
The export process has failed because another operation is being executed. Wait until the process has finished and then perform export again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
The requested import process was stopped because a file with an extension other than "csv" was specified for import.
Corrective Action
Specify a file with the extension "csv", and then perform the operation again.
Description
As the system configuration file filename specified for import is invalid, the process has been stopped.
If the specified file does not exist, 'unknown' may be displayed for filename.
Corrective Action
Check the following, resolve the cause of the problem, and execute the command again.
That the contents and format of the system configuration file are correct
The specified file exists
That the active user has reading authority for the file specified
That the active user has reading authority for the directory specified
The file specified can be opened using other software
For details on the system configuration file, refer to the following:
Refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide VE".
Refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Description
The process has been stopped because there is a mistake in the format of value for item in the system configuration file, or network configuration information XML file or the file contains an invalid character.
One of the following is displayed in item:
Corrective Action
Resolve the problem referring to the details displayed for item, and then perform the operation again.
When an RCXCSV V2.0 format system configuration file has been imported
An invalid value has been set for the section name.
Correct the definition in the system configuration file.
When an RCXCSV V1.0 format system configuration file has been imported
Something other than Chassis, EtherSwitch, or ServerBlade is specified for the resource type.
Correct the definitions in the system configuration file.
Either a value other than "new", "change" or a hyphen ("-") is specified in the operation column, or the description of the "operation" of the section header is incorrect.
Only "new" or a hyphen ("-") can be specified in the sections after the line of "#Backup configuration".
Correct the definitions in the system configuration file.
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 system configuration file.
When "cfab_ip_address" is displayed, check that values are not configured for both "ip_address" and "cfab_ip_address", and correct the definition in the system configuration file.
When an error occurs when registering using the IP address for oob.
Configure an IP address for oob in "ip_address", and a space (" ") in "cfab_ip_address", and perform the operation again.
When an error occurs when registering using the representative virtual IP address of the fabric
Configure the representative virtual IP address of the fabric in "cfab_ip_address", and perform the operation again after configuring a space (" ") in "ip_address".
When IPMI keys are displayed even though a physical server, for which IPMI communication is not to be performed, has been registered in the system configuration file
Check whether a register_ipmiless definition file has been created, or the definition of server_control.rcxprop is something other than "physical_server_name,false", and perform the operation again.
Perform the operation again after checking the value corresponding to the displayed key name in the network configuration information XML file and correcting the definition.
For details on the XML definition of the network configuration information, refer to "8.1.1 Creation" in the "Reference Guide (Command) VE".
For details on how to modify the XML definition of the network configuration information, refer to "8.1.2 Modification" in the "Reference Guide (Command) VE".
For the values that can be specified for item, refer to the following.
For Virtual Edition, refer to "B.3 Resource Definitions" in the "User's Guide VE".
For Cloud Edition, refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Cloud Edition]
Description
The process was canceled due to one of the following reasons:
There is an error in the format of value for item in a system configuration file, L-Server XML file, L-Server template XML file, resource pool XML file, image XML file, user XML file, network configuration information XML file, or the [Create an L-Server] dialog
An invalid character has been used
There is no value set
There is an error in the format of value for item specified in the XML file of disk resource configuration information for VM guests
There is an error in the format of value for item specified in the iSCSI boot information XML file.
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 tenants, 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
The format of value for item specified in a VM specific information definition file contains an error
An L-Server cannot be linked with a virtual machine on the specified VM host
An L-Server cannot be created for specified VM host
Modification is not possible for an existing L-Server
There is an error in the external connection port number of the LAN switch blade, the value specified for the LAG name, or the port name specified for the Ethernet Fabric switch
There is an error in the number of addresses specified
An excluded address is outside the scope of the lead and end addresses
There is a mistake in the format of value for item specified in the SCSI controller definition file.
The group configuration of NICs in the physical L-Server template does not match that of the L-Platform
One of the following is displayed in item:
Resolve the problem referring to the details displayed for item, and then perform the operation again.
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.
Perform the operation again after correcting the value corresponding to the displayed key value in the L-Server XML file and correcting the definition.
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.
Perform the operation again after correcting the value corresponding to the displayed key value in the image XML file and correcting the definition.
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.
There is an error in the value specified for the name attribute of the Pool element.
Review the value of the name attribute in the Pool element, correct the definition, and then perform the operation again.
There is an error in the value specified for the ip attribute of the VmHost element.
Review the value of the ip attribute in the VmHost element, correct the definition, and then perform the operation again.
There is an error in the value specified for the name attribute in the Disk element in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
Review the values, correct the definition, and then perform the operation again.
There is an error in the value of the size attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
Review the values, correct the definition, and then perform the operation again.
There is an error in the value of the path attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
Review the values, correct the definition, and then perform the operation again.
Perform the operation again after reviewing the value in the iSCSI boot information XML file and correcting the definition.
Perform the operation again after correcting the value corresponding to the displayed key value in the resource pool XML file and correcting the definition.
The network resource name and the public LAN subnet name are different.
Specify the same value for both the network resource name and the public LAN subnet name.
The network resource name and the admin LAN subnet name are different.
Specify the same value for both the network resource name and the admin LAN subnet name.
Perform the operation again after correcting the value corresponding to the displayed key value in the XML file of the tenant and correcting the definition.
For the network resource for which PXE boot is specified, select a network resource that does not have a tagged VLAN configured.
When specifying PXE boot, images cannot be specified.
After specifying only PXE boot, perform the operation again.
The specified image is incorrect.
Review the specified image, and perform the operation again.
Check that sequential numbers starting from 0 are used for the NICIndex element value of each NIC element.
When this message is output when linking a configured physical server to an L-Server, check that NICs are configured in the VIOM or ISM server profile.
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.
Review the CPUShare value defined in the L-Server template, import the L-Server template, and then perform the operation again.
When using a VM specific information definition file, review the value of processor_share, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the CPUShare element has been entered in the XML file, review the value specified for the CPUShare element, 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.
Review the MemoryShare value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_share, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryShare element has been entered in the XML file, review the value specified for the MemoryShare element, 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.
Review the CPUWeight value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of processor_weight, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the CPUWeight element has been entered in the XML file, review the value specified for the CPUWeight element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the CPUWeight value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
Review the MemoryWeight value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_weight, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryWeight element has been entered in the XML file, review the value specified for the MemoryWeight element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the MemoryWeight value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
Review the MemoryBuffer value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_buffer_rate, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryBuffer element has been entered in the XML file, review the value specified for the MemoryBuffer element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the MemoryBuffer value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
Review the StartupRAM value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_startup_size, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the StartupRAM element has been entered in the XML file, review the value specified for the StartupRAM element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the StartupRAM value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
There is an error in the value specified for automatic configuration.
Review the values, correct the definition, and then perform the operation again.
Perform the operation again after correcting the value corresponding to the displayed parameter key value in the displayed customization file and correcting the definition.
Perform the corrective action according to the executed operations.
When linking a configured virtual machine to an L-Server:
Check the OS types of the virtual machine and VM host that are linked to each other, and perform the operation again.
When creating an L-Server:
Check if the OS type of the VM host for L-Server creation and the VM management software for managing the VM host are appropriate, and perform the operation again.
When changing L-Server configurations:
Check if the OS type of the VM host for L-Server creation and the VM management software for managing the VM host are appropriate, and the communication status with VM management software, and perform the operation again.
There is an error in the value specified for VLAN automatic configuration of an external connection port.
Review the values, correct the definition, and then perform the operation again.
There is an error in the value specified for external connection port of LAN switch blades.
Review the external connection port number of the LAN switch blade specified in value and the value specified for the LAG name.
Also confirm that the port name specified for the Ethernet Fabric switch is a CIR port.
After correcting the definition, perform the operation again.
There is an error in the value specified for physical LAN segment name.
Review the values, correct the definition, and then perform the operation again.
Perform the operation again after checking the value corresponding to the displayed key name in the network configuration information XML file and correcting the definition.
For details on the XML definition of the network configuration information, refer to "15.6.1 Creation" in the "Reference Guide (Command/XML) CE".
For details on how to modify the XML definition of the network configuration information, refer to "15.6.2 Modification" in the "Reference Guide (Command/XML) CE".
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. Review the value of the Password element in the user XML file, correct the definition, and perform the operation again.
The value of "value" in the virtual storage information is incorrect. When performing the switchover operation of operating or standby storage, check the content of the replication definition file. When performing switchover operations using Disaster Recovery after damage, ensure that virtual storage exists on the backup site and is not registered in the pool.
When using a VM specific information definition file, review the value of max_definable_memory_size, modify the definition, and perform the operation again.
For details, refer to "8.1.2 VM Specific Information Definition File" in the "Setup Guide CE".
When using a VM specific information definition file, review the value of memory_hotplug, modify the definition, and perform the operation again.
For details, refer to "8.1.2 VM Specific Information Definition File" in the "Setup Guide CE".
When using a VM specific information definition file, review the value of clock_offset, modify the definition, and perform the operation again.
For details, refer to "8.1.2 VM Specific Information Definition File" in the "Setup Guide CE".
The number of addresses in the specified range of address exceeds the limit (65536).
Review the range (starting point and end point in the address) in the specified address. After correcting the definition, perform the operation again.
An excluded address is outside the scope of the lead and end addresses.
Correct the lead, end, and excluded addresses, and then perform the operation again.
There is an error in the OS type.
Change the OS type specified in the XML.
For details on the OS type to specify, refer to the OS type in "15.3.2 Definition Information for Virtual L-Servers (XML)" in the "Reference Guide (Command/XML) CE".
Check if the correct name is specified in the "windomain_name" described in the OS setting property file.
Specify a string of up to 64 characters, including alphanumeric characters, hyphens ("-"), and periods (".") for the DNS domain name. The first character must be an alphanumeric character. Specify a character other than a hyphen or a period for the end of the string. Check the domain name for participation again, and specify the correct domain.
Check if the correct user name is specified in the "windomain_user" described in the OS setting property file.
Specify a string of up to 256 characters for the user name. Check the account for the domain for participation again, and specify the correct user name.
Check if the correct password is specified in the "windomain_password" described in the OS configuration property file.
Specify the password using a string of alphanumeric characters and symbols.
Check if the correct file name is specified in the GUIRunOnce command definition file name described in the L-Server template.
Specify the definition file name using a string of up to 64 characters, including alphanumeric characters, underscores ("_"), and hyphens ("-").
Review the value specified for the SCSI controller type in the SCSI controller definition file, correct the definition, and then perform the operation again.
Configure the grouping of NICs so that the following combinations match:
The combination of the following in the physical L-Server template:
The index of NIC redundancy groups (NICGroupIndex)
The numbers of the NICs contained in each NIC redundancy group (NICLink)
The combination of the following items specified for physical servers using the [Change Configuration] page of the L-Platform
The order of creation of NIC groups (The count starts from 0)
The numbers of the NICs used to create each group
[Common to All Editions]
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.
Change using an un-registered resource name is not possible.
Perform the operation again after specifying a resource name that is already registered.
When value is "NetworkDevice", and "(ip=IP_address)" follows after the value:
When value is "NetworkDevice", and "(ip=IP_address, nic_index=NIC_index)" follows after the value:
When value is "NetworkDevice", and "(ip=IP_address,port=port_name)" follows after the value:
When value is "Domain(id=Domain ID to which the Link Aggregation Port Defined in XML belongs to)"
Corrective Action
The network device with the admin IP address IP_address is not registered.
Register the network device (for which IP address is used as the management IP address) as a resource, and retry.
The NIC corresponding to NIC_index is not registered on the rack mount server with the admin IP address registered using its IP address.
Check the NIC index displayed in the resource details of the rack mount server with the admin IP address registered using the IP address, define the correct index for the NIC index (the NicIndex element) of the device, and then perform the operation again.
The process was canceled because there are no ports with the port_name for the network device registered using the admin IP address, IP_address.
Check the port name (the one displayed in the resource details of the network device that is registered in an IP address that is a management IP address), change it to a correct port name (Port tag), and perform the operation again.
If port names are not displayed in the resource details, there is a possibility that the manager is not communicating with the network device by SNMP. Check the state of the relevant network device, remove the cause of the problem, and perform the operation again.
The process was canceled as the port defined in XML does not exist.
When multiple ports which are defined in the XML exist, the ports are displayed separated by commas.
Define the port name of an existing port in XML, and perform the operation again.
The process was canceled as the link aggregation port defined in XML does not exist.
When multiple link aggregation ports which do not exist in the XML are defined, the link aggregation ports are displayed separated by commas.
Define the identifier information of an existing link aggregation port name in the XML, and perform the operation again.
The process was canceled as the domain defined in XML does not exist.
Define the identifier information of a link aggregation port to which belongs to the domain ID in XML, and perform the operation again.
[Virtual Edition]
Description
The process has been stopped as the specified resource name value has not been registered.
Corrective Action
Change using an un-registered resource name is not possible.
Specify a resource name that has already been registered and perform the operation again.
When an already registered resource name has been registered, the description of the key value of the section header resource name is incorrect.
Correct the system configuration file, and then perform the operation again.
When registering new resource information using the specified resource name, change the operation to "new".
[Cloud Edition]
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.
Change using an un-registered resource name is not possible.
Perform the operation again after specifying a resource name that is already registered.
Corrective Action
There is an error in the key value for the resource name in the section header. Perform the operation again after correcting the system configuration file.
Change the operation to "new".
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 definition files, refer to "7.1.6 Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template" in the "Setup Guide CE".
The process was canceled because the registered cloning image was deleted due to deletion of a host from VMware vCenter Server.
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 element.
Perform the operation again after setting the access scope of resources.
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
The process was canceled as the resource specified as a spare server does not exist.
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 the resource type is "PhysicalServer", the physical server which satisfies the conditions may not exist or may be in an incorrect status.
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
Number of FCs in the FC connection pattern
For the correction method, refer to the corrective action of "Message number 62508".
Check that the network configuration of the admin LAN matches completely, including NIC redundancy.
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.
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
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
Check the following:
There is an address pool to store the address set resources
There is an unused address set resource in the address pool
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 "Appendix G Definition Files" in the "Setup Guide CE".
The server with the admin IP address IP_address is not registered.
Register the rack mounted server (for which IP address is used as the management IP address) as a resource, and retry.
The process was canceled as the VM host that has the IP address defined in the XML does not exist.
Define the IP address of an existing VM host in the XML and perform the operation again.
The process was canceled as the storage pool defined in XML does not exist.
Define an existing storage pool in the XML and perform the operation again.
The process was canceled because the specified storage pool is not registered.
When limiting the range of switchover, confirm that replicated storage pools have been defined correctly. If they have not been defined correctly, correct the definition file and execute the rcxmgrexport command again.
For details on how to specify target storage pools for replication, refer to "3.3 Manager Installation and Configuration" in the "DR Option Instruction".
The process was canceled as the tenant defined in XML does not exist.
When multiple tenants which are defined in the XML exist, the tenants are displayed separated by commas.
Define the tenant name of an existing tenant in the XML, and perform the operation again.
Description
The process has been stopped as registration of the resource name value could not be performed for the resource type type.
Corrective Action
Resource names that have already been registered cannot be used for registration.
Specify a resource name that has not already been registered and perform the operation again.
When changing the resource information of the specified resource name, change the operation to "change".
Description
The process was stopped as the description of the version of file format in the system configuration file is incorrect.
Corrective Action
Correct the description of the version of the file format in the system configuration file, and then perform the operation again.
For details on the system configuration file, refer to the following:
Refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide VE".
Refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Virtual Edition] [Cloud Edition]
Description
The import process was stopped as a file with an extension other than ".csv" was specified for import.
Corrective Action
Specify a system configuration file with the extension ".csv", and then perform the operation again.
[Cloud Edition]
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 process was stopped as there is a line that cannot be loaded in the correct format from the system configuration file.
Corrective Action
The entire line may not be able to be loaded correctly due to a mistake in the use of double quotes ( " ). Check the content of the system configuration file, resolve the problem, and then perform the operation again.
For details on the characters that can be used for Virtual Edition, refer to the following:
Refer to "B.2 File Format" in the "User's Guide VE".
Refer to "B.2 File Format" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Description
The system configuration file does not support operation_type for property_type.
Corrective Action
When operation_type is "change", take the following corrective action based on the applicable property_type.
"mac_address" or "hbaar_mac_address"
When changing the admin LAN MAC address used for the admin LAN or the HBA address rename setup service
Reconfigure the hardware properties again.
When changing other values
Change the MAC address value specified in the system configuration file to one that has already been registered.
Description
The HBA address rename setup service failed to connect to the manager.
Corrective Action
Check the following, resolve the cause of the problem, and execute the command again.
When a problem has occurred in the network environment
Check if there is a problem with the network connection between the HBA address rename setup service and the manager.
Check if a LAN cable is unplugged, or a problem has occurred in the LAN cable or network devices.
When there is a mistake in the entered IP address or port number
Check that there are no mistakes in the IP address and port number for the manager that were specified for connecting to the manager from the HBA address rename setup service.
When the manager has stopped
Restart the manager.
For details on how to check the status of and start the service on the manager, refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
