Message ID |
Message |
---|---|
KARS22001-E |
Connection to the storage cluster did not succeed. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. However, if the same error occurs again after you perform step 7, wait for a while, and then retry the operation. <Step1> Verify that the IP address or host name of the storage cluster is correct. If either is incorrect, abort the procedure, and then correct the IP address or host name. <Step2> Verify that connection with the storage cluster is possible. If connection is not possible, abort the procedure, and then resolve the network path problem. <Step3> When connecting with the host name, verify the settings of Windows and the DNS server of the storage cluster. If any settings are incorrect, correct them, and then retry the operation. <Step4> After importing the root certificate into the Windows Certificate Store, restart the configuration utility. <Step5> Verify that the certificate list file (ca.pem) stored in the folder where configuration utility exists can be accessed. If it cannot be accessed, abort the procedure, and then assign an access right to the certificate list file (ca.pem). <Step6> Restart the configuration utility. <Step7> Confirm that the file to be transferred is the correct file (file format, file size, etc.), and if it is invalid, replace it with the correct one. |
KARS22002-E |
Retry was performed (as requested from the storage cluster), but the operation did not complete successfully. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. <Step1> Check the status of network path to the storage cluster, and if there is a problem, resolve it and retry the operation. <Step2> If the error occurs again in step 1, wait for a while, and then retry the operation. <Step3> If the error occurs again in step 2, collect the logs, and then contact customer support. |
KARS22004-E |
Connection to vCenter did not succeed. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. However, if the same error occurs again after you perform step 6, wait for a while, and then retry the operation. <Step1> Verify that the IP address or host name of vCenter is correct. If either is incorrect, abort the procedure, and then correct the IP address or host name. <Step2> Verify that connection with vCenter is possible. If connection is not possible, abort the procedure, and then resolve the network path problem. <Step3> If you want to connect by host name, verify the DNS server settings of the windows and the vCenter. If the DNS server settings is incorrect, correct the DNS server settings. <Step4> After importing the root certificate into the Windows Certificate Store, restart the configuration utility. <Step5> Verify that the certificate list file (ca.pem) stored in the folder where configuration utility exists can be accessed. If it cannot be accessed, abort the procedure, and then assign an access right to the certificate list file (ca.pem). <Step6> Restart the configuration utility. |
KARS22005-E |
Authentication by vCenter did not succeed. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. <Step1> Verify that the ID or password of vCenter is correct. If the ID or password is incorrect, abort the procedure, and then correct the ID or password. <Step2> Confirm that the user role assigned to the ID of vCenter is correct. If it is incorrect, abort the procedure, and then assign the correct user role. <Step3> Verify that the status of the service and others of vCenter is normal. If there is a problem with vCenter, abort the procedure, and then correct it. |
KARS22006-E |
The operation of vCenter did not succeed. [Cause] An unexpected response was returned when executing REST API for vCenter. [Solution] Run configuration utility again. When the same error occurs, collect the logs, and then contact customer support. |
KARS22007-E |
Connection to the maintenance node did not succeed. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. <Step1> Verify that the IP address or host name of the maintenance node is correct. If either is incorrect, abort the procedure, and then correct the IP address or host name. <Step2> Verify that the ID or password of the maintenance node is correct. If the ID or password is incorrect, abort the procedure, and then correct the ID or password. <Step3> Confirm that the user role assigned to the ID of maintenance node is correct. If it is incorrect, abort the procedure, and then assign the correct user role. <Step4> Verify that connection with the maintenance node is possible. If connection is not possible, abort the procedure, and then resolve the network path problem. <Step5> If you want to connect by host name, verify the DNS server settings of the windows and the maintenance node. If the DNS server settings is incorrect, correct the DNS server settings. |
KARS22008-E |
Operation could not be performed on the maintenance node. [Cause] The cause is as follows:
|
KARS22009-E |
File transfer to and from the maintenance node did not succeed. [Cause] The causes are as follows:
|
KARS22010-E |
Connection to additional ESXi host did not succeed. IP address of additional ESXi host : xxx [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. <Step1> Verify that the IP address or host name of additional ESXi host is correct. If either is incorrect, abort the procedure, and then correct the IP address or host name. <Step2> Verify that the ID or password of additional ESXi host is correct. If the ID or password is incorrect, abort the procedure, and then correct the ID or password. <Step3> Confirm that the user role assigned to the ID of the additional ESXi host is correct. If it is incorrect, abort the procedure, and then assign the correct user role. <Step4> Verify that SSH of additional ESXi host is enabled. If the SSH is disabled, abort the procedure, and then enable the SSH. <Step5> Verify that connection with additional ESXi host is possible. If connection is not possible, abort the procedure, and then resolve the network path problem. <Step6> If you want to connect by host name, verify the DNS server settings of the windows and the ESXi host. If the DNS server settings is incorrect, correct the DNS server settings. |
KARS22011-E |
The operation of additional ESXi host did not succeed. IP address of additional ESXi host : xxx [Cause] An unexpected response was returned for the operation of additional ESXi host. [Solution] Run configuration utility again. When the same error occurs, collect the logs, and then contact customer support. |
KARS22012-E |
The number of retries for the storage cluster operation exceeded the threshold. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. <Step1> Check the status of network path to the storage cluster, and if there is a problem, resolve it and then run configuration utility again. <Step2> See the event logs, verify that no job is running, and then run configuration utility again. <Step3> If the error occurs again in step 2, collect the logs, and then contact customer support. |
KARS22013-I |
Awaiting response from the storage cluster. |
KARS22014-I |
Awaiting response from the maintenance node. |
KARS22015-I |
Awaiting response from vCenter. |
KARS22016-I |
Awaiting response from additional ESXi host. |
KARS22017-I |
Do you want to exit configuration utility? |
KARS22018-E |
The system requirements file could not be accessed. [Cause] An access right to the system requirements file has not been assigned. [Solution] Assign an access right to the folder and file containing the system requirements file, and then retry the operation. |
KARS22019-E |
The system requirements file could not be found. [Cause] The system requirements file does not exist. [Solution] Store the system requirements file in any folder, and then retry the operation. |
KARS22020-E |
Could not open the system requirements file. [Cause] The causes are as follows:
[Solution] Perform the following procedure from step 1. However, if the same error occurs again after you perform step 2, collect the logs, and then contact customer support. <Step1> Confirm that the system requirements file is the correct file (file format, file size, etc.), and if it is invalid, replace it with the correct one. <Step2> Run configuration utility again. When the same error occurs, collect the logs, and then contact customer support. |
KARS22021-E |
The public key or private key file could not be accessed. [Cause] An access right to the public key or private key file has not been assigned. [Solution] Assign an access right to the folder and file containing the public key or private key file, and then retry the operation. |
KARS22022-E |
The public key or private key file could not be found. [Cause] The public key or private key file does not exist. [Solution] Store the public key file and private key file in any folder, and then retry the operation. |
KARS22024-E |
The package file for software update could not be accessed. [Cause] An access right to the package file for software update has not been assigned. [Solution] Assign an access right to the package file for software update and the folder that containing it, and then retry the operation. |
KARS22025-E |
The package file for software update could not be found. [Cause] The package file for software update does not exist. [Solution] Store the package file for software update in any folder, and then retry the operation. |
KARS22027-E |
The package file for maintenance node update could not be accessed. [Cause] The file path is too long. [Solution] Try a location that has a shorter path. |
KARS22028-E |
The system requirements file could not be accessed. [Cause] The file path is too long. [Solution] Try a location that has a shorter path. |
KARS22029-E |
The public key or private key could not be accessed. [Cause] The file path is too long. [Solution] Try a location that has a shorter path. |
KARS22030-E |
The package file for software update could not be accessed. [Cause] The file path is too long. [Solution] Try a location that has a shorter path. |
KARS22102-E |
The import of the server certificate to the storage cluster did not succeed. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22103-E |
configuration utility could not be started. [Cause] The causes are as follows:
[Solution] Perform the following procedure. Then, run configuration utility again.
|
KARS22104-E |
The configuration utility version is incompatible with the storage cluster version. [Cause] The version of the configuration utility is older than the storage cluster version. [Solution] Verify the version of configuration utility and the storage cluster, and do one of the following.
|
KARS22105-E |
No executable function is available. [Cause] The user role that are required to processing the function are not assigned to the user ID of the storage cluster or maintenance node. [Solution] Verify that the required role is assigned, and then retry the operation of configuration utility. |
KARS22106-I |
Enter the representative IP address (IPv4) or host name of the storage cluster, the user ID with a Security role, and the password of the user ID. |
KARS22110-I |
Select the server certificate file (public key) to be imported into the storage cluster as a newly imported or updated one. |
KARS22111-I |
Select the server certificate file (private key) to be imported into the storage cluster as a newly imported or updated one. |
KARS22112-I |
The server certificate file could be imported into the storage cluster. |
KARS22114-E |
The information of the storage cluster could not be obtained. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22115-E |
Failed to get information for maintenance node. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22116-E |
The information of vCenter could not be obtained. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22120-E |
configuration utility could not be started. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22121-E |
configuration utility could not be started. [Cause] Write permission is not assigned to the certificate list file. [Solution] Verify the access right for the certificate list file, assign write permission, and then rerun configuration utility. |
KARS22200-E |
Software update could not be started. [Cause] The storage cluster is not ready for software update. [Solution] Verify that the status of the storage cluster is Ready or NondisruptiveUpdating. If the status is other than those, verify the event logs, resolve the failure, make sure that the status is Ready, and then retry the configuration utility operation. |
KARS22202-E |
Software update ended abnormally. [Cause] An error occurred. [Solution] See the event logs with the job ID of the target job, and then resolve the failure according to the prescribed recovery procedure. Then, retry the operation of configuration utility. Job ID : xxx |
KARS22204-I |
Software update was stopped. Click the Cancel button to finish configuration utility. |
KARS22205-E |
Failed to transfer the package file and import the system requirements file. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22207-E |
The information of the storage cluster could not be obtained. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22208-E |
Information of the maintenance node could not be obtained. [Cause] An unexpected response was returned from the maintenance node. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22209-E |
Failed to delete the package file for maintenance node update. [Cause] An unexpected response was returned from the maintenance node. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22210-E |
Failed to perform maintenance node update. [Cause] An unexpected response was returned from the maintenance node. |
KARS22211-I |
The target storage cluster has already been updated. Do you want to start software update? Cluster Name : xxx Current Version : xxx Target Version : xxx If not, you can skip to the post software update operation by clicking No button. Yes : Start software update. No : Skip to the post software update operation. Cancel : Return to the Confirming Storage Cluster Status screen without starting software update. |
KARS22213-I |
Software update is in process on the target storage cluster. Click OK button to confirm the status of software update. The estimated time displayed might differ from the actual time required because software updating is already in progress. |
KARS22221-I |
Transfer of the package file for software update and import of the system requirements file are in process. It takes a few minutes to perform this operation. |
KARS22222-I |
The version of configuration utility is incompatible with that of the storage cluster. Replace with the same or higher version of the configuration utility as the storage cluster version. Click OK button to close the configuration utility. |
KARS22224-I |
Note: It takes approximately 10 to 40 minutes to update the maintenance node. It takes approximately 8 minutes to update the storage configuration file. |
KARS22226-E |
The configuration file could not be updated. [Cause] An unexpected response was returned from the maintenance node. [Solution] xxx |
KARS22227-I |
Are you sure you want to execute maintenance node and configuration file update? Update Package File : xxx Template File Name : xxx Clicking the OK button starts the operation and overwrites the configuration file (if any) on the maintenance node. If you do not want the configuration file to be overwritten, click the Cancel button, back up the configuration file on the maintenance node, and then retry the operation. If you enter the wrong template file name and update the configuration file, the adding storage node will fail from now on. |
KARS22228-E |
The configuration file could not be updated. [Cause] Failed to create a folder for editing the configuration file. [Solution] Assign write permission to the folder containing configuration utility. Verify the disk space to ensure sufficient capacity. Move or delete the folder YYYYMMDDhhmmss in the folder containing configuration utility, if any. Retry the operation of configuration utility. |
KARS22229-E |
The configuration file could not be updated. [Cause] The SystemConfigurationFile.csv file for updating could not be received. [Solution] Retry the operation of configuration utility. |
KARS22230-I |
Updating the maintenance node and VSSB configuration file successfully completed. Perform the following because used files might not have been deleted. |
KARS22231-E |
Failed to update configuration file. [Cause] An unexpected response was returned from the maintenance node. [Solution] Retry the operation of configuration utility. |
KARS22232-E |
The update package file on the maintenance node could not be deleted. [Cause] An unexpected response was returned from the maintenance node. |
KARS22234-I |
Do you want to return to the Selecting Files for Software Update window? The current entry will be lost. |
KARS22236-E |
Failed to update configuration file. [Cause] SystemConfigurationFile.csv was corrupted. [Solution] SystemConfigurationFile.csv could not be updated because SystemConfigurationFile.csv was corrupted. Retry the operation of configuration utility. |
KARS22237-E |
Maintenance node update did not succeed. [Cause] An unexpected response was returned from the maintenance node. |
KARS22238-E |
Connection to the maintenance node did not succeed. [Cause] The causes are as follows:
|
KARS22244-I |
Target storage cluster is ready for software update. Are you sure you want to execute software update? Cluster Name : xxx Current Version : xxx Target Version : xxx |
KARS22245-I |
Software update process was successfully completed. Please click the Next button to confirm the execution result of software update. |
KARS22300-E |
The information of the storage cluster could not be obtained. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22301-E |
The configuration file could not be exported. [Cause] An unexpected error occurred. [Solution] Perform the following procedure from step 1. <Step1> A problem with verification of the storage node certificate retained in the maintenance node might exist. Verify that a valid certificate is added in the maintenance node. Then, run configuration utility again. <Step2> If you are performing the following operations on the target storage cluster, abort the procedure, and then retry the operation of the configuration utility after the operation is complete.
<Step3> Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22302-E |
The VSSB configuration file could not be downloaded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22303-E |
The VM configuration file could not be downloaded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22304-E |
The VSSB configuration file could not be edited. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22305-E |
The VM configuration file could not be edited. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22306-E |
The VSSB configuration file could not be uploaded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22307-E |
The VM configuration file could not be uploaded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22308-E |
The storage node could not be added. [Cause] An unexpected error occurred. |
KARS22309-E |
The storage pool could not be expanded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22310-E |
The drive data could not be relocated. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22311-I |
Would you like to execute the storage node addition function? Note: Clicking OK button starts the operation and overwrites the configuration file (if any) on the maintenance node. If you do not want the configuration file to be overwritten, click Cancel button, back up the configuration file on the maintenance node, and then retry the operation. |
KARS22312-I |
The storage node addition function has been completed. See the event logs and verify that no problem has been occurred during the operation. |
KARS22313-E |
The capacity of the storage controller could not be expanded. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22314-I |
There are no available datastores registered on the additional ESXi host. [Solution] Create a datastore on the ESXi host, and then retry the operation of the configuration utility. |
KARS22315-I |
There are no available port groups registered on the additional ESXi host. [Solution] Create port groups on the ESXi host, and then retry the operation of the configuration utility. |
KARS22316-I |
There are no available drives on the additional ESXi host. [Solution] Add a drive to the ESXi host, and then retry the operation of the configuration utility. |
KARS22317-I |
There are no available storage adapters registered on the additional ESXi host. [Solution] Add a storage adapter to the ESXi host, and then retry the operation of the configuration utility. |
KARS22318-I |
Processing has not started because other priority tasks are running in the storage cluster. |
KARS22319-I |
Storage nodes cannot be added because the maximum number of storage nodes that can be configured has been reached. |
KARS22320-I |
The storage node addition function has been completed. See the event logs and verify that no problem has been occurred during the operation. In addition, perform the following because used files might not have been deleted. [Solution] Delete the used configuration file stored in the folder where configuration utility exists. The used configuration file is as follows. |
KARS22321-E |
The VSSB configuration file could not be edited. [Cause] Write permission is not assigned to the VSSB configuration file. [Solution] Delete the VSSB configuration file stored in the folder where configuration utility exists, and then rerun configuration utility. |
KARS22322-E |
The VSSB configuration file could not be edited. [Cause] The VSSB configuration file is not stored in the folder where configuration utility exists. [Solution] Retry the operation of configuration utility. |
KARS22323-E |
The VM configuration file could not be edited. [Cause] Write permission is not assigned to the VM configuration file. [Solution] Delete the VM configuration file stored in the folder where configuration utility exists, and then rerun configuration utility. |
KARS22324-E |
The VM configuration file could not be edited. [Cause] The VM configuration file is not stored in the folder where configuration utility exists. [Solution] Retry the operation of configuration utility. |
KARS22325-I |
There are no available ESXi hosts registered on the vCenter. [Solution] Register the additional ESXi host to the vCenter, and then retry the operation of the configuration utility. |
KARS22326-I |
Since this function only inputs the IP addresses by consecutive numbers, there is a possibility that the input values may contain invalid values such as already assigned IP addresses as a result of automatic input. Before continuing the process, check the automatically input IP addresses and correct them if necessary. |
KARS22327-E |
The specified value is incorrect. [Cause] The specified value is duplicated. [Solution] Change the duplicated value. |
KARS22328-E |
Failed to check the drive connection method. [Cause] The drive connection method does not match between the existing storage node and the storage node to be added. [Solution] Match the drive connection method of the storage node to be added with one of the existing storage node. |
KARS22400-E |
An exception occurred while importing a system requirements file. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22401-E |
An exception occurred while confirming the drive information. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22402-E |
An exception occurred while expanding the storage pool. [Cause] An unexpected error occurred. [Solution] Collect the logs of configuration utility and the maintenance node and the dump logs of the storage nodes, and then contact customer support. |
KARS22403-I |
Do you want to return to Function Selection window? The current entry will be lost. |
KARS22404-I |
Do you want to import the system requirements file? It will take approximately 1 minute to complete. |
KARS22405-I |
Do you want to skip importing of the system requirements file? |
KARS22406-I |
Import of the system requirements file was successfully completed. |
KARS22407-I |
A drive is not selected. Select drives, and then click Next button. |
KARS22408-I |
No drive is available. Import the latest system requirements file. Add drives, and retry the operation of configuration utility. |
KARS22409-I |
Do you want to add drives? It will take approximately 1 minute to complete. |
KARS22410-I |
Drive addition has been completed. See the event logs and verify that no problem has been occurred during the operation. |
KARS22411-I |
Do you want to return to Importing System Requirements File window? The current entry will be lost. |
KARS22412-I |
Do you want to return to Additional Drive Selection window? The drive information will be updated and all drives will be selected. |