Message ID |
Message |
|---|---|
KARS23000-E |
An error occurred while verifying the datastore of ESXi host. xxx [Solution] Verify the datastore capacity, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23002-E |
An error occurred while verifying the datastore of ESXi host. xxx [Solution] Delete the inapplicable VMs from the datastore, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23003-E |
An error occurred while verifying the datastore of ESXi host. xxx [Solution] Verify the specified datastore name, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23004-E |
An error occurred while obtaining a template file from the vCenter server. [Solution] Verify whether network communication between the maintenance node and vCenter server is possible, troubleshoot any problem, and then retry the operation. Or, verify that the current configuration supports the version of the vCenter server and the version of the vCenter ESXi host. If there is a problem, resolve it, and then rerun the export command. Or, if any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether the specification for [vCenterServerHostName/TemplateFileName] of the VSSB configuration file is correct, and then correct any errors. Verify that the user name and password of the specified vCenter server are correct. When you set up an option for denying an invalid server certificate of the vCenter server, verify that the server certificate of the vCenter server is valid and the corresponding route certificate is imported in the node. Accept or deny the invalid server certificate of the vCenter server by using the change_certificate_action command, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23005-E |
An error occurred while obtaining information from the vCenter server. [Solution] Verify whether network communication between the maintenance node and vCenter server is possible, troubleshoot any problems, and then retry the operation. Or, verify whether network communication between the vCenter server and ESXi host is possible, troubleshoot any problems, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23006-E |
The IP address for the control network specified in the VSSB configuration file is already in use by another storage cluster. xxx [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23007-E |
The IP address for the control network specified in the VSSB configuration file is already in use by another storage cluster. xxx [Solution] Specify an unused IP address in the configuration file, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23008-E |
The version of the maintenance node and the version of image file (.ova) for storage node VM are different. [Solution] Configure a maintenance node by using the same version of image file (.ova) for the maintenance node VM as that of the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23009-E |
The import command could not be run. [Solution] Obtain a list of event logs. If an event log (KARS13010-I) including "Operation = CONFIGURATION_FILE_IMPORT" is output, no action is required. Verify that the IP address specified for the --primary_master_ip option is the same as the representative IP address of the storage cluster or control network IP address of the cluster master node (primary). If these values are incorrect, specify the correct arguments, and then rerun the import command. Verify that the user and password specified for the --user and --password options respectively are correct. If these values are incorrect, specify the correct arguments, and then rerun the import command. Verify that the user is assigned a Service role as a user role. If the user has no Service role, rerun the import command by using the Service role user. Verify the DNS server settings and connection with the DNS server. If there is a problem, resolve the problem, and then rerun the import command. Verify whether there is a problem with network connection between the maintenance node and cluster master node (primary). If a network failure occurred, recover the failure, and then rerun the import command. If you specified a representative IP address of the storage cluster of the --primary_master_ip option, rerun the import command with the same arguments specified. If you specified a control network IP address of the cluster master node (primary) for the --primary_master_ip option, verify the control network IP address of the current cluster master node (primary), and then rerun the import command with the IP address specified for the --primary_master_ip option. Note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23010-E |
Execution results of the import command could not be obtained. [Solution] Obtain a list of event logs. If an event log (KARS13010-I) including "Operation = CONFIGURATION_FILE_IMPORT" is output, no action is required. Verify whether there is a problem with network connection between the maintenance node and cluster master node (primary). If a network failure occurred, recover the failure, and then rerun the import command. Or, if you specified a representative IP address of the storage cluster for the --primary_master_ip option, retry the import command with the same arguments specified. Or, if you specified a control network IP address of the cluster master node (primary) for the --primary_master_ip option, verify the control network IP address of the current cluster master node (primary), and then rerun the import command with the IP address specified for the --primary_master_ip option. Also, note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23011-E |
The export command could not be run. [Solution] Verify that the IP address specified for the --primary_master_ip option is the same as the representative IP address of the storage cluster or control network IP address of the cluster master node (primary). If these values are not correct, specify the correct arguments, and then rerun the export command. Verify that the user and password specified for the --user and --password options respectively are correct. If these values are not correct, specify the correct arguments, and then rerun the export command. Verify that the user is assigned a Service role as a user role. If the user has no Service role, run the export command by using the Service role user. Verify the DNS server settings and connection with the DNS server. If a network failure occurred, recover the failure, and then rerun the export command. Verify whether network communication between the maintenance node and cluster master node (primary) is possible. If a network failure occurred, recover the failure, and then rerun the export command. If you specified a representative IP address of the storage cluster for the --primary_master_ip option, rerun the export command with the same arguments specified. If you specified a control network IP address of the cluster master node (primary) for the --primary_master_ip option, verify the control network IP address of the current cluster master node (primary), and then rerun the export command with the IP address specified for the --primary_master_ip option. Note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23012-E |
An error occurred when obtaining execution results of the export command. [Solution] Verify whether network communication between the maintenance node and cluster master node (primary) is possible. If a network failure occurred, recover the failure, and then retry the operation. Or, if you specified a representative IP address of the storage cluster for the --primary_master_ip option, retry the export command with the same arguments specified. Or, if you specified a control network IP address of the cluster master node (primary) for the --primary_master_ip option, verify the control network IP address of the current cluster master node (primary), and then retry the export command with the IP address specified for the --primary_master_ip option. Note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23013-E |
SSH connection with the cluster master node (primary) was unsuccessful. [Solution] Verify whether the setting value of --primary_master_ip is correct. If it is not correct, specify the correct value, and then retry the operation. Or, if the cluster master node (primary) is blocked, recover the node, and then retry the operation. Or, verify whether network communication between the maintenance node and the cluster master node (primary) is possible, resolve any problems, and then retry the operation. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23014-E |
The storage cluster setting could not be verified. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify that the execution environment and operation are correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23015-E |
The storage cluster setting could not be verified. xxx [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify that the execution environment and operation are correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23016-E |
The version of the system requirements file is old. [Solution] Obtain the latest system requirements file, and then store the file in the maintenance node. Then, retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23017-E |
The system requirements file could not be read. [Solution] Verify whether the system requirements file is stored in the correct location. If the system requirements file does not exist in the maintenance node, obtain the latest system requirements file, and then store the file in the maintenance node. Then, retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23018-E |
The system requirements file might have been changed. [Solution] Obtain the latest system requirements file, and then store the file in the maintenance node. Then, retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23019-E |
The storage node could not be added. |
KARS23020-E |
Connection of the internode network could not be verified. xxx [Solution] Verify whether the internode network settings, including the maximum transmission unit (MTU), are correct, and then correct any problems. Or, verify whether internode network communication is possible, and then resolve any problems. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the maintenance node logs, and then contact customer support. |
KARS23021-E |
The storage node could not be replaced. |
KARS23022-E |
The execution results of the storage node replacement could not be obtained. |
KARS23023-E |
The execution results of the storage node addition could not be obtained. |
KARS23024-E |
The database could not be accessed. [Solution] Wait for a while, and then retry the import command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23025-E |
An error occurred while obtaining information from the template file. xxx [Solution] Match the version of the storage node VM image file (.ova) to that of the storage cluster, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23026-E |
Network could not be set. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether network communication between the maintenance node and vCenter server is possible, and then resolve any problems. Or, verify whether network communication between the vCenter server and ESXi host is possible, and then resolve any problems. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23027-E |
Network could not be set. [Solution] Verify whether network communication between the maintenance node and storage node is possible, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23028-E |
The number of storage nodes that can be added in multiple fault domain configuration must be xxx. (Number of adding storage nodes = xxx) [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23029-E |
The hardware does not meet the system requirements. xxx [Solution] Some hardware components are invalid. Replace the invalid components with the valid ones, and then retry the operation. Or, if the profile (SystemRequirementsFile) is old, obtain the latest version of the profile, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23031-E |
When only one fault domain exists, multiple storage nodes cannot be added at the same time. In a single-fault-domain configuration, only one storage node can be added at a time. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23032-E |
The file could not be transferred to the cluster master node (primary) from the maintenance node. (File name = xxx) [Solution] Verify whether network communication between the maintenance node and the cluster master node (primary) is possible, and then resolve any problems. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23033-E |
Connection from the maintenance node to the storage node could not be verified. xxx [Solution] Verify whether network communication between the maintenance node and storage node is possible, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23034-E |
Connection from the maintenance node to the storage node could not be verified. xxx [Solution] Verify whether there are problems with the control network settings of the storage node, and then resolve any problems. Or, verify whether network communication between the maintenance node and storage node is possible, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23036-E |
An error occurred while verifying hardware components of the ESXi host specified in the configuration files (VSSB configuration file and VM configuration file). xxx [Solution] Verify hardware components, correct the configuration file error, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23037-E |
Configuration files could not be downloaded. [Solution] Verify whether network communication between the maintenance node and cluster master node (primary) is possible. If a network failure occurred, recover the failure, and then retry the export command. Or, if you specified a representative IP address of the storage cluster for the --primary_master_ip option, retry the export command with the same arguments specified. Or, if you specified a control network IP address of the cluster master node (primary) for the --primary_master_ip option, verify the control network IP address of the current cluster master node (primary), and then retry the export command with the IP address specified for the --primary_master_ip option. Note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23038-E |
The configuration file could not be read. xxx [Solution] Verify that you logged in to the correct maintenance node and that the login user is correct. If you specified a configuration file, verify that the specified path is correct. If the path is incorrect, store the file in the specified location, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23040-E |
The configuration file could not be read. xxx [Solution] Correct the configuration file according to the message, and then retry the operation. |
KARS23041-E |
The configuration file could not be read. xxx [Solution] Store the correct configuration file, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23042-E |
An error occurred while transferring the configuration file to the storage node. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether network communication between the maintenance node and the cluster master node (primary) is possible, resolve any problems, and then retry the operation. Also, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23043-E |
The number of storage nodes in configuration files does not match the actual configuration. [Solution] Run the export command. Change the exported configuration files. Run the import command again. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23044-E |
The configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether network communication between the maintenance node and the cluster master node (primary) is possible, resolve any problems, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23045-E |
The configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether network communication between the maintenance node and the cluster master node (primary) is possible, resolve any problems, and then retry the operation. Also, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23046-E |
Parameters specified when creating storage node stacks with CloudFormation are incorrect. xxx [Solution] Review the parameters to be specified when creating storage node stacks with CloudFormation according to the message. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23047-E |
Operation was unsuccessful because the storage node was blocked. (Storage node IDs = xxx) [Solution] Recover the blocked storage node, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23048-E |
The storage node subject to maintenance could not be configured because configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Then, retry the operation. Verify whether network communication between the maintenance node and the cluster master node (primary) is possible, and resolve any problems. Also, remove the storage node VM subject to maintenance, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23049-E |
Whether the specified user has the Security or Service role could not be verified. [Solution] Create a user having the Security or Service role, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23050-E |
Multiple initiator nodes are specified for the storage node to be added. Only one initiator node can be added at a time. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23051-E |
The fault domain name specified for the added storage node does not exist in the storage cluster. Verify the fault domain name of the storage node. (Fault domain names = xxx) [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23052-E |
In a multiple-fault-domain configuration, a node that could not be removed exists in the storage cluster. xxx |
KARS23053-E |
When configuring multiple fault domain configuration, the number of storage nodes to be added must be the same for each fault domain. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23054-E |
When configuring multiple fault domains, the number of initiator nodes does not match among fault domains. Add initiator nodes so that all fault domains have the same number of initiator nodes. (Fault domain name = xxx) [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23055-E |
Another operation is running. [Solution] Wait for a while, and then retry the import command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23056-E |
A storage node VM could not be created. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem, and then retry the operation. Or, verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. If a storage node VM is created, remove the VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23057-E |
A storage node VM could not be powered on. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify whether the procedures for configuring the vCenter server and setting the network are correct, and the procedures for configuring and setting the ESXi host and registering the ESXi host in the vCenter server are correct. If any problems occur, resolve them. Or, verify whether network communication between the maintenance node and vCenter server is possible, and network communication between the vCenter server and ESXi host is possible, and then resolve any problems. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23058-E |
Part of the physical server information retrieved from the ESXi host is empty. xxx [Solution] Contact the server administrator to troubleshoot the problem, and then retry the operation. |
KARS23060-E |
The vCenter server could not be accessed. [Solution] Verify that vCenterServerHostName of the VSSB configuration file output by the export command is correct. If vCenterServerHostName is not correct, import the correct configuration file, and then rerun the export command. Or, verify whether network communication between the maintenance node and vCenter server is possible, resolve any problems, and then rerun the export command. Or, when you set up an option for denying an invalid server certificate of the vCenter server, verify that the server certificate of the vCenter server is valid and the corresponding root certificate is imported into the node. Accept or deny the invalid server certificate of the vCenter server by using the change_certificate_action command, and then rerun the export command. Or, verify that the current configuration supports the version of the vCenter server and the version of the vCenter ESXi host. If there is a problem, resolve it, and then rerun the export command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23061-E |
The storage node VM does not exist in the ComputeResource registered in the VSSB database. |
KARS23062-E |
Another operation is running. [Solution] Wait for a while, and then retry the export command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23063-E |
An error occurred while accessing the database. [Solution] Wait for a while, and then retry the export command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23064-E |
The configuration file could not be read. xxx [Solution] Configure a maintenance node by using the image file (.ova) for the latest maintenance node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23065-E |
This configuration (RedundantPolicy = xxx) is not supported. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23066-E |
The server certificate could not be verified. (Connection destination = xxx) |
KARS23067-E |
Connection with the storage node was unsuccessful. (Connection destination = xxx) [Solution] Verify whether network communication between the maintenance node and host is possible, troubleshoot any problems, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23069-E |
Whether the name of the storage node VM is duplicated could not be verified. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem, and then retry the operation. Or, verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23070-E |
Operation was unsuccessful because the storage node to be replaced does not exist in the configured storage cluster. (Storage node ID = xxx) [Solution] Verify whether the setting value of the storage node ID is correct. If it is not correct, specify the correct storage node ID, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23071-E |
The VM name of the storage node to be replaced does not exist in the configuration file. (VM name = xxx, Host name = xxx) [Solution] Verify that the VM name of the storage node to be replaced is shown in the configuration file used for storage node replacement. Also, verify that the ID of the specified storage node is the one for the storage node to be replaced, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23072-E |
The specified operation could not be performed because another operation might be in progress. (Operation that might be in progress = xxx) |
KARS23073-E |
The specified operation could not be performed because another operation might be in progress. |
KARS23080-E |
The operation cannot be performed because the storage cluster status is not "Ready". [Solution] If the storage cluster is in the process of starting, stopping, or maintenance, wait until the operation completes. If the storage cluster has a problem, take action according to the manual or event logs. Verify that the storage cluster status changes to "Ready", and then retry the operation. |
KARS23081-E |
The operation cannot be continued because the memory capacity of the storage node VM subject to maintenance is less than the minimum memory capacity of the protection domain (xxx MiB). [Solution] Expand the memory capacity of the storage node VM subject to maintenance to more than the minimum memory capacity of the protection domain, and then retry the operation. |
KARS23082-E |
An error occurred during syntax checking of the VM configuration file. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem, and then retry the operation. Or, verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23100-E |
A key pair could not be created. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the setting value of the key pair name of the VM configuration file. If there is any problem, resolve it, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23101-E |
Storage node stacks could not be created. [Solution] Delete the stacks that could not be created. Also, if any message is shown in Additional Information, refer to the message to verify whether all settings of the VM configuration file are correct. If there is any error, modify the VM configuration file, and then retry the operation. Or, verify that the execution environment is correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23102-E |
Changes were made other than storage node addition in the VM configuration file. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the changes in the VM configuration file, delete unnecessary changes, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23103-E |
Storage node stacks could not be updated. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem, and then retry the operation. Or, verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23104-E |
A file of a key pair does not exist or is incorrect. [Solution] Verify whether a file of a key pair exists and it matches the KeyPair setting of the VM configuration file. |
KARS23105-E |
The VM configuration file contains illegal changes. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the changes in the VM configuration file, delete unnecessary changes, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23106-E |
Failed to remove the storage node VM to be replaced. |
KARS23107-E |
The key pair could not be removed. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the setting value of the key pair name of the VM configuration file. If there is a problem, resolve it, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23108-E |
The version of the Virtual Storage Software Block installer that is being run does not match that of the AMI. |
KARS23109-E |
VM configuration file could not be obtained. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the specification of storage location, AWS CLI settings, or network settings. If there is any problem, resolve it, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23110-E |
The export command could not be run. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with the AWS CLI settings or network settings. If there is any problem, resolve it, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23111-E |
Information could not be obtained from AWS. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23112-E |
The configuration file could not be read. xxx [Solution] Retry the operation by using the configuration file whose version matches the version of the current storage software. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23114-E |
Logs could not be collected because free disk space is insufficient in the environment in which the log collection was attempted. [Solution] Delete unnecessary files to secure 1 GiB or more of free space, and then retry the operation. If the same error occurs after retry, contact customer support. |
KARS23116-E |
When the user data protection type (RedundantType) is xxx, the number of storage nodes to be added must be xxx. (Number of adding storage nodes = xxx) [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23117-E |
All the storage nodes to be added must be included in the same spread placement group. [Solution] Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23118-E |
The storage nodes to be added must belong to a new spread placement group. [Solution] Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23119-E |
The initiator nodes is not included in a spread placement group. [Solution] Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23121-E |
The software version of the storage cluster and the AMI version of the storage node to be added do not match. [Solution] Modify the AMI setting of the replacement storage node in the VM configuration file so that the AMI of the same version as that of the storage node to be replaced is specified, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23122-E |
Specify the replacement storage node of the same version as that of the storage node to be replaced. [Solution] Modify the AMI setting of the replacement storage node in the VM configuration file so that the AMI of the same version as that of the storage node to be replaced is specified, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23123-E |
AMI information could not be obtained. |
KARS23124-E |
The storage node to be replaced is not in a status that allows for replacement. [Solution] Verify whether the ID (specified in the hsdsinstall command) of the storage node to be replaced is correct. If the specification is incorrect, specify the correct storage node, and then retry storage node replacement. If the specification is correct, block the storage node, and then retry storage node replacement. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23125-E |
The user data protection type (RedundantType) xxx set in the VM configuration file is not supported. [Solution] Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23126-E |
Multiple fault domain configuration is not supported. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23127-E |
Subnet configuration information could not be obtained. [Solution] If any message is shown in Additional Information, refer to the message to verify whether there is a problem with AWS CLI settings, network settings, subnet settings, or the subnet names described in VM configuration files. If there is any problem, resolve it, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23128-E |
The spread placement group setting of the storage node to be replaced does not match that at the time the storage node was blocked. Therefore, the storage node could not be replaced. [Solution] Review the spread placement group setting of the storage node to be replaced. Specify the same spread placement group as that at the time the storage node to be replaced was blocked in the VM configuration file, and then retry the operation. |
KARS23129-E |
The AMI name is invalid. |
KARS23200-E |
The export command could not be run. [Solution] Verify that the IP address specified for the --host option is the same as the control network IP address of the load balancer (ELB) or cluster master node (primary). If these values are incorrect, specify the correct arguments, and then rerun the export command. Verify that the user and password specified for the --user and --password options respectively are correct. If these values are incorrect, specify the correct arguments, and then rerun the export command. Verify that the user is assigned a Service role as a user role. If the user has no Service role, rerun the export command by using the Service role user. Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it, and then rerun the export command. Also, verify the status of the storage node VMs on AWS, troubleshoot any problem, and then rerun the export command. If you specified the load balancer (ELB) for the --host option, rerun the export command with the same arguments specified. If you specified a control network IP address of the cluster master node (primary) of the --host option, verify the control network IP address of the current cluster master node (primary), and then rerun the export command with the IP address specified for the --host option. Note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect Virtual Storage Software Block installer logs and Virtual Storage Software Block dump log files, and then contact customer support. |
KARS23201-E |
An error occurred when obtaining execution results of the export command. [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it, and then rerun the export command. Also, verify the status of the storage node VMs on AWS, troubleshoot any problem, and then rerun the export command. Or, if you specified a control network IP address of the load balancer (ELB) for the --host option, retry the export command with the same arguments specified. Or, if you specified a control network IP address of the cluster master node (primary) for the --host option, verify the control network IP address of the current cluster master node (primary), and then rerun the export command with the IP address of the --host option specified. Also, note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect Virtual Storage Software Block installer logs and Virtual Storage Software Block dump log files, and then contact customer support. |
KARS23202-E |
The storage cluster setting could not be verified. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23203-E |
The storage cluster setting could not be verified. xxx [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23204-E |
Connection of the internode network could not be verified. xxx [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23205-E |
The file could not be transferred to the cluster master node (primary) from the controller node. (File name = xxx) [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23206-E |
Connection from the controller node to the storage node could not be verified. xxx [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23207-E |
Connection from the controller node to the storage node could not be verified. xxx [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23208-E |
Configuration files could not be downloaded. [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it, and then rerun the export command. Also, verify the status of the storage node VMs on AWS, troubleshoot any problem, and then rerun the export command. Or, if you specified a control network IP address of the load balancer (ELB) for the --host option, retry the export command with the same arguments specified. Or, if you specified a control network IP address of the cluster master node (primary) for the --host option, verify the control network IP address of the current cluster master node (primary), and then rerun the export command with the IP address of the --host option specified. Also, note that the cluster master node (primary) might switch to the cluster master node (secondary). If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23209-E |
The configuration file could not be read. xxx [Solution] Verify that you logged in to the correct controller node and that the login user is correct. If you specified a configuration file, verify that the specified path is correct. If the path is incorrect, store the file in the specified location, and then retry the operation. If you have not specified a configuration file, verify that the file SystemConfigurationFile.csv exists in the current directory where the command was run. If the file does not exist, store the file in the current directory, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23210-E |
An error occurred while transferring the configuration file to the storage node. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Also, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23211-E |
The configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23212-E |
The configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Or, verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Also, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23213-E |
The storage node subject to maintenance could not be configured because configuration information could not be referenced from the configured storage cluster. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. If the cluster master node is blocked, perform maintenance recovery for the blocked storage node, and then retry the operation. Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23214-E |
The configuration file could not be read. xxx [Solution] Retry the operation by using the configuration file whose version matches the version of the current storage cluster software. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23215-E |
Connection with the storage node was unsuccessful. (Connection destination = xxx) [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23216-E |
The specified operation could not be performed because another operation might be in progress. (Operation that might be in progress = xxx) |
KARS23217-E |
The specified operation could not be performed because another operation might be in progress. |
KARS23218-E |
An error occurred while communicating with the DNS server. (DNS server = xxx) [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23219-E |
Time query to the NTP server was unsuccessful. (NTP server = xxx) [Solution] Verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23220-E |
The storage cluster could not be started. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23221-E |
The storage cluster could not be configured. [Solution] Verify whether failure information about AWS is reported. Or, verify whether the execution environment or operation is correct. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23222-E |
Resource information of the storage node VM could not be obtained. [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. If a storage node VM is created, remove the VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23223-E |
An error occurred during SSH connection with the storage node. (IP address = xxx) [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23224-E |
An error occurred while transferring the configuration file to the storage node. (Configuration file = xxx) [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23225-E |
Setup processing was unsuccessful. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23226-E |
Setup processing was unsuccessful. [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23228-E |
Configuration information cannot be registered. [Solution] Verify whether failure information about AWS is reported. Or, verify whether the execution environment or operation is correct. The system requirements file might be corrupted. Download the latest system requirements file, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer and dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23229-E |
The number of storage nodes in configuration files does not match the actual configuration. |
KARS23230-E |
Storage node stacks could not be created. [Solution] Operate the AWS Management Console to verify the status of storage node stacks. Also, verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23231-E |
Information could not be obtained from AWS. [Solution] If any message is shown in Additional Information, refer to the message to troubleshoot the problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23232-E |
The storage cluster setting could not be verified. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23233-E |
The storage cluster setting could not be verified. xxx [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23234-E |
Connection of the internode network could not be verified. xxx [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23235-E |
An error occurred while communicating with the DNS server. (DNS server = xxx) [Solution] Verify whether failure information about AWS is reported. Also, verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23236-E |
Time query to the NTP server was unsuccessful. (NTP server = xxx) [Solution] Verify whether failure information about AWS is reported. Also, verify whether there is a problem with the network settings (control network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23237-E |
The storage cluster could not be configured. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23238-E |
An error occurred during SSH connection with the storage node. [Solution] Verify whether there is a problem with the network settings (internode network). If there is a problem, resolve it. Also, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23239-E |
Another storage node could not be set up. [Solution] See the error for another storage node, and then resolve the problem. Delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
KARS23450-E |
An unexpected error occurred in the storage cluster. [Solution] Collect the logs, and then contact customer support. |
KARS23451-E |
Many requests are being processed in the storage cluster. [Solution] Wait a while, and then retry the operation. If the same error occurs again after retry, collect the logs, and then contact customer support. |
KARS23452-E |
The request was rejected due to environmental factors in the storage cluster. [Solution] Wait a while, and then retry the operation. If the same error occurs again after retry, collect the logs, and then contact customer support. |
KARS23456-E |
The request was rejected because the storage cluster was being started or was blocked. |
KARS23500-E |
CFM File transfer did not succeed. xxx [Solution] Verify whether internode network communication is possible, and then resolve any problems. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23501-E |
An error occurred while communicating with the DNS server. (DNS server = xxx) [Solution] Verify whether network communication between the storage node and DNS server is possible, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23502-E |
An error occurred during a DNS server connection test. [Solution] Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23503-E |
An error occurred while obtaining information about the ESXi hosts. [Solution] Verify that the execution environment and operation are valid. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23504-E |
The NTP server could not be set. [Solution] Verify that the execution environment and operation are valid. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23505-E |
Time query to the NTP server was unsuccessful. (NTP server = xxx) [Solution] Verify whether network communication between the storage node and NTP server is possible, and then resolve any problems. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23506-E |
The storage node specified in the --target_node_ip option cannot be accessed. (Expect storage node name = xxx, Target storage node name = xxx) [Solution] Specify the correct command option according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23507-E |
The storage node specified in the --target_node_ip option cannot be accessed. [Solution] Specify the correct command option according to the message, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23508-E |
The version of the storage cluster and the version of the OVA file do not match. (Storage cluster version = xxx, OVA file version = xxx) [Solution] Match the version of the OVA file to that of the storage cluster, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23509-E |
The storage cluster could not be started. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify that the execution environment and operation are correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23510-E |
The storage cluster could not be configured. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify whether the execution environment and operation are correct. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23511-E |
Resource information of the storage node VM could not be obtained. [Solution] Verify whether communication is possible between the storage node and maintenance node, and then resolve any problem. If a storage node VM is created, remove the VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23512-E |
An error occurred during SSH connection with the storage node. (IP address = xxx) [Solution] Verify whether internode communication is possible, and then resolve any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23513-E |
An error occurred while transferring the configuration file to the storage node. (Configuration file = xxx) [Solution] Verify whether internode communication is possible, and then resolve any problem. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23514-E |
Setup processing was unsuccessful. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify that the execution environment and operation are correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23515-E |
Setup processing was unsuccessful. [Solution] Verify whether internode communication is possible, and then resolve any problem. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23516-E |
Synchronization with the primary NTP server was unsuccessful. (NTP server = xxx) [Solution] Verify the network status with the NTP server, and then resolve the cause of any failures. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Remove the storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23517-E |
A configuration file could not be created. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify whether the execution environment and operation are correct. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23518-E |
Configuration file information is invalid. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify whether the execution environment and operation are correct. Then, if a storage node VM was created, remove the VM, and retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23519-E |
An error occurred while verifying a value of the configuration file. [Solution] A value of the configuration file is invalid. Correct the configuration file, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23520-E |
Configuration information cannot be registered. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify whether the execution environment and operation are correct. The system requirements file might be corrupted. Download the latest system requirements file, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23521-E |
An invalid time zone was specified. (Time zone = xxx) [Solution] Correct the configuration file according to the message, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23522-E |
Another storage node could not be set up. [Solution] See the error for another storage node, and then troubleshoot the problem. Remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23596-E |
Network configuration was unsuccessful due to a duplicate IP address on the network. (xxx) [Solution] Resolve the duplication of the IP address with the component indicated by the displayed MAC address, and then retry the operation. |
KARS23597-E |
The specified operation cannot be currently performed. (Storage node status in which the operation is possible = xxx) [Solution] When a "configuring a storage cluster" job is in progress, wait until the job completes. If the "configuring a storage cluster" job was not successful, retry the operation from installing the storage software. Also, if processing other than the "configuring a storage cluster" job is in progress, wait until the processing completes. |
KARS23598-E |
A storage cluster could not be configured because the operation-target storage node was not a representative storage node. (Representative storage node name = xxx) [Solution] Identify the representative storage node, and then perform the operation with the representative storage node. |
KARS23599-E |
Input value is invalid. (xxx) [Solution] Correct the input value according to the message. |
KARS23600-E |
One or more required fields are not entered or the input value is invalid. [Solution] Correct the field value with an exclamation mark displayed according to the message. |
KARS23601-E |
An NIC is not installed in a defined slot of the physical server. (PCI address for which information acquisition was unsuccessful = xxx) [Solution] Verify whether the defined NIC is installed in the slot with the displayed PCI address. Install the defined NIC in the slot, and then retry the "setting up each storage node" operation. If the same error occurs after retry, contact customer support. |
KARS23602-E |
The specified operation cannot be performed with the current status. (Storage node status in which the operation is possible = xxx) [Solution] Wait until the "configuring a storage cluster" job in progress completes. If the "configuring a storage cluster" job was not successful, retry the operation from installing the storage software. |
KARS23603-E |
The specified operation cannot be performed with the current status. (Storage node status in which the operation is possible = xxx) [Solution] Retry the operation from installing the storage software. |
KARS23604-E |
The specified operation cannot be performed with the current status. (Storage node status in which the operation is possible = xxx) [Solution] If a "configuring a storage cluster" job is not being performed, perform the operation. This operation is possible when a representative storage node cannot be started and is not available for some reason. |
KARS23700-E |
The Configuration of the storage cluster could not be performed because another operation might be in progress. [Solution] Verify whether other jobs such as "setting up each storage node", "configuring a storage cluster", "adding storage nodes", "replacing storage nodes", or "registering spare node information" are running. When a "setting up each storage node" job is running, wait until the job completes, and then retry the operation. If a "configuring a storage cluster", "adding storage nodes", "replacing storage nodes" or "registering spare node information" job is running, allow it to complete. You do not need to retry the operation. Or, verify the power status of the storage node and the network settings and status, and fix any problems. Then, retry the operation. |
KARS23701-E |
An error occurred in the procedure for re-performing the operation on a particular storage node. (IP address of the storage node = xxx) |
KARS23702-E |
Network could not be set because an IP address is duplicated on the network. xxx [Solution] Resolve the duplication of the indicated IP address, and then retry the operation. |
KARS23704-E |
Connection between storage nodes was unsuccessful. (Network type = xxx, IP address = xxx) |
KARS23705-E |
The storage cluster setting could not be verified. [Solution] Verify the status of the storage node power and network. If a problem occurs, resolve it. Retry the operation from installing the storage software. If the same error occurs after retry, take a dump on each storage node and contact customer support after logging on the controller node. |
KARS23706-E |
The storage cluster setting could not be verified. xxx [Solution] Verify the status of the storage node power and network. If a problem occurs, resolve it. Retry the operation from installing the storage software. If the same error occurs after retry, take a dump on each storage node and contact customer support after logging on the controller node. |
KARS23707-E |
The host name specified in the VSSB configuration file and the host name set in the storage node do not match. xxx [Solution] Set up each storage node according to the host name of the storage node described in the VSSB configuration file. Retry the operation. |
KARS23708-E |
The network information of the control network specified in the VSSB configuration file does not match the network information set on the storage node. xxx [Solution] Set up each storage node according to the network information of the control network described in the VSSB configuration file. Retry the operation. |
KARS23709-E |
The version of a storage node does not match that of the representative storage node. xxx [Solution] Install the same version of the storage software on all storage nodes. Run through the storage software installation again. |
KARS23710-E |
Network connection from each network to all the storage nodes could not be verified. xxx [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings), and then make the network status such that communication is possible. Retry the operation. |
KARS23711-E |
The system requirements file is invalid. [Solution] Obtain the latest system requirements file, and then store the file in the storage node. Retry the operation. If the same error occurs after retry, collect the dump files for each storage node and logs of the controller node, and then contact customer support. |
KARS23712-E |
The target storage node might be in use as a spare node. Therefore, a storage cluster could not be configured. (IP address of the storage node = xxx) |
KARS23713-E |
The version of the system requirements file is old. [Solution] Obtain the latest system requirements file, and then store the file in the storage node. Retry the operation. If the same error occurs after retry, collect the dump files for each storage node and logs of the controller node, and then contact customer support. |
KARS23715-E |
Failed to build storage cluster. [Solution] Verify the status of the storage node power and network. If a problem occurs, resolve it. Verify whether there is a problem in the BIOS-related environment settings of the storage node by seeing the manual. Also, verify that the time zone settings are all correct for each storage node and there is no lag with actual time. Retry the operation from installing the storage software. If the same error occurs after retry, take a dump on each storage node, log the controller node, and contact customer support. |
KARS23720-E |
The VSSB configuration file could not be found. [Solution] If the VSSB configuration file is not stored in the intended location, upload a VSSB configuration file. If the VSSB configuration file is stored in the intended location, verify the file name. If the file name is incorrect, delete the file, and then upload the file with the correct file name. Retry the operation. If the same error occurs after retry, collect the dump files for each storage node and logs of the controller node, and then contact customer support. |
KARS23721-E |
Hardware does not meet the system requirements. xxx [Solution] One or more hardware components do not meet hardware requirements. Replace such components with ones that meet the requirements. Also, verify the version of the storage software installer that you are using. Make sure that you use the correct version of storage software installer, and then retry the operation from installing the storage software. |
KARS23723-E |
The passwords of a representative storage node and setup user do not match for a storage node. xxx [Solution] Set up each storage node one by one so that the password of the setup user is the same across all the storage nodes. Retry the operation. |
KARS23724-E |
Time query to the NTP server was unsuccessful. (NTP server = xxx) [Solution] Verify whether network connection between the storage node and NTP server is possible, and then resolve any problems. When you specify the NTP server with which the storage node is connected with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set in DNS server. Also, verify that the NTP server is running normally and that the setting procedure for the NTP server is correct. Retry the operation. |
KARS23725-E |
An invalid time zone was specified. (Time zone = xxx) [Solution] Correct the description of the VSSB configuration file. Retry the operation. |
KARS23726-E |
An error occurred while communicating with the DNS server. (DNS server = xxx) [Solution] Verify whether network connection between the storage node and DNS server is possible, and then resolve any problems. Or, make sure that the setting procedure for the DNS server is correct. Retry the operation. |
KARS23727-E |
Files other than the VSSB configuration file (SystemConfigurationFile.csv) and system requirements file (SystemRequirementsFile.yml) are uploaded in the transfer destination directory by SFTP for the representative storage node. [Solution] Delete files other than the VSSB configuration file and system requirements file stored in the transfer destination directory. Retry the operation. |
KARS23760-W |
Storage cluster configuration was continued although a disconnected path was detected as a result of verifying the connection for each path of a redundant network. xxx [Event Name] Reduced network redundancy detected [Category] ControlPort [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings), and then make the network status such that communication is possible. If you need to verify connection again, retry storage software installation. |
KARS23761-W |
Storage cluster configuration was continued although a disconnected path was detected as a result of verifying the connection for each path of a redundant network. xxx [Event Name] Reduced network redundancy detected [Category] InternodePort [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings), and then make the network status such that communication is possible. If you need to verify connection again, retry storage software installation. |
KARS23900-E |
An internal error occurred. [Solution] Verify whether any alert is output in the vCenter server or ESXi host, and resolve any problems. Or, verify that the execution environment and operation are correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23901-E |
An internal error occurred. [Solution] Wait for a while, and then rerun the import command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23902-E |
An internal error occurred. [Solution] Verify that the configuration file is stored in the correct location, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23903-E |
An internal error occurred. [Solution] Verify that the configuration file is correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23904-E |
An internal error occurred. [Solution] Verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23905-E |
An internal error occurred. [Solution] Wait for a while, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23906-E |
An internal error occurred. [Solution] Wait for a while, and then retry the export command. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS23907-E |
An internal error occurred. |
KARS23908-E |
An internal error occurred. [Solution] Collect the dump files for each storage node and logs of the controller node, and then contact customer support. |
KARS23909-E |
An internal error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS23910-E |
An internal error occurred. |
KARS23911-E |
An internal error occurred. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node VM, and then retry the operation. If the same error occurs after retry, collect the logs of the Virtual Storage Software Block installer, and then contact customer support. |
KARS23912-E |
An internal error occurred. [Solution] Verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, and then contact customer support. |
KARS23913-E |
An internal error occurred. [Solution] Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node stacks, and then retry the operation. If the same error occurs after retry, collect the dump log files of Virtual Storage Software Block, and then contact customer support. |
Note: Some messages have "xxx" description. Sometimes, the “xxx” of these messages represents the supplemental information about the error.