Messages KARS27000-KARS27999

KARS27000-E

Spare node information could not be registered. Hardware does not meet the system requirements. The number of installed CPU cores is excessive. (Job ID = xxx, Spare node IP address = xxx, Installed CPU cores = xxx)

[Event Name]

Spare node information setting error

[Category]

StorageNode

[Solution]

One or more hardware components do not meet hardware requirements. Verify the version of the system requirements file. If the version is old, obtain the latest system requirements file, and then import the system requirements file. After that, replace the hardware components with ones that satisfy hardware requirements, and then retry the operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27001-W

Hyper-Threading might be enabled in the BIOS. If Hyper-Threading is enabled in the BIOS, disable the setting. (Job ID = xxx, Spare node IP address = xxx, Thread(s) per core = xxx)

[Event Name]

Incorrect spare node information

[Category]

StorageNode

[Solution]

One or more hardware components do not meet the requirements. Plan a shutdown of the storage cluster, and then set Hyper-Threading to off.

KARS27002-W

NUMA might be disabled in the BIOS. If NUMA is disabled in the BIOS, enable the settings. (Job ID = xxx, Spare node IP address = xxx, NUMA node(s) = xxx)

[Event Name]

Incorrect spare node information

[Category]

StorageNode

[Solution]

One or more hardware components do not meet requirements. To prevent performance degradation, plan a shutdown of the storage cluster, and then enable NUMA.

KARS27003-E

Spare node information could not be registered. Hardware does not meet the system requirements. Disable SubNUMA in the BIOS settings. (Job ID = xxx, Spare node IP address = xxx, xxx)

[Event Name]

Spare node information setting error

[Category]

StorageNode

[Solution]

One or more hardware components do not meet hardware requirements. Verify the version of the system requirements file. If the version is old, obtain the latest system requirements file, and then import the system requirements file. After that, replace the hardware components with ones that satisfy hardware requirements, and then retry the operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27004-E

Spare node information could not be edited. Hardware does not meet the system requirements. The number of installed CPU cores is excessive. (Job ID = xxx, Spare node ID = xxx, Installed CPU cores = xxx)

[Event Name]

Spare node information setting error

[Category]

StorageNode

[Solution]

One or more hardware components do not meet hardware requirements. Verify the version of the system requirements file. If the version is old, obtain the latest system requirements file, and then import the system requirements file. After that, replace the hardware components with ones that satisfy hardware requirements, and then retry the operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27005-W

Hyper-Threading might be enabled in the BIOS. If Hyper-Threading is enabled in the BIOS, disable the setting. (Job ID = xxx, Spare node ID = xxx, Thread(s) per core = xxx)

[Event Name]

Incorrect spare node information

[Category]

StorageNode

[Solution]

One or more hardware components do not meet the requirements. Plan a shutdown of the storage cluster, and then set Hyper-Threading to off.

KARS27006-W

NUMA might be disabled in the BIOS. If NUMA is disabled in the BIOS, enable the settings. (Job ID = xxx, Spare node ID = xxx, NUMA node(s) = xxx)

[Event Name]

Incorrect spare node information

[Category]

StorageNode

[Solution]

One or more hardware components do not meet requirements. To prevent performance degradation, plan a shutdown of the storage cluster, and then enable NUMA.

KARS27007-E

Spare node information could not be edited. Hardware does not meet the system requirements. Disable SubNUMA in the BIOS settings. (Job ID = xxx, Spare node ID = xxx, xxx)

[Event Name]

Spare node information setting error

[Category]

StorageNode

[Solution]

One or more hardware components do not meet requirements. Verify the version of the system requirements file. If the version is old, obtain the latest version, and then import the new version. After that, replace the hardware components with ones that satisfy hardware requirements, and then retry the operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27008-W

The spare node is not in a state in which spare node switchover is possible. The hardware does not meet the system requirements. The number of installed CPU cores is excessive. (Spare node ID = xxx, Fault domain ID = xxx, Installed CPU cores = xxx)

[Event Name]

Spare node operation monitoring alert (Unsupported server model)

[Category]

Service

[Solution]

Delete information about the spare node registered in the storage cluster. Verify the version of the system requirements file. If the version is old, obtain the latest version, and then import the new version. Replace the hardware with the system components that satisfy system requirements. Reperform the procedure for using the spare node function. If the problem persists, collect the dump log files, and then contact customer support.

KARS27009-W

Hyper-Threading might be enabled in the BIOS. If Hyper-Threading is enabled in the BIOS, disable the setting. (Spare node ID = xxx, Fault domain ID = xxx, Thread(s) per core = xxx)

[Event Name]

Spare node information setting warning

[Category]

Service

[Solution]

One or more hardware components do not meet the requirements. Plan a shutdown of the storage cluster, and then set Hyper-Threading to off.

KARS27010-W

NUMA might be disabled in the BIOS. If NUMA is disabled in the BIOS, enable the settings. (Spare node ID = xxx, Fault domain ID = xxx, NUMA node(s) = xxx)

[Event Name]

Spare node information setting warning

[Category]

Service

[Solution]

One or more hardware components do not meet the requirements. To prevent performance degradation, plan a shutdown of the storage cluster, and then enable NUMA.

KARS27011-W

The spare node is not in a state in which spare node switchover is possible. The hardware does not meet the system requirements. Disable SubNUMA in the BIOS. (Spare node ID = xxx, Fault domain ID = xxx, xxx)

[Event Name]

Spare node operation monitoring alert (Insufficient memory capacity)

[Category]

Service

[Solution]

Delete information about the spare node registered in the storage cluster. Verify the version of the system requirements file. If the version is old, obtain the latest version, and then import new version. Replace the hardware with the system components that satisfy system requirements. Reperform the procedure for using the spare node function. If the problem persists, collect the dump log files, and then contact customer support.

KARS27200-E

The capacity of the memory is insufficient. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Insufficient memory)

[Category]

StorageNode

[Solution]

Restart the storage cluster, and then retry the operation. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27201-E

An operation that can not be performed concurrently is being performed. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Prohibited concurrent operation)

[Category]

StorageNode

[Solution]

Wait until the operation that cannot be performed concurrently completes, and then retry the operation. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27202-E

The number of storage nodes after the addition exceeds the upper limit. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Max. number of storage nodes exceeded)

[Category]

StorageNode

[Solution]

Review the maximum number of supported storage nodes and the number of storage nodes to be added, and then retry the operation. If EC2 instances of the storage node to be added were created, delete the EC2 instances before the retry. To delete them, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27203-E

An error occurred during verification of software versions of the storage node to be added. (Job ID = xxx, Version of storage cluster = xxx, Version of the storage node to be added = xxx)

[Event Name]

Storage node addition pre-check (Software version mismatch)

[Category]

StorageNode

[Solution]

Verify that the software version of the storage node to be added matches that of the storage cluster, and then retry the operation. If EC2 instances of the storage node to be added were created, delete the EC2 instances before the retry. To delete them, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27204-E

Adding storage nodes ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Storage cluster master node (primary) failover)

[Category]

StorageNode

[Solution]

If there are blocked storage nodes, recover them. Verify whether there are storage nodes that need to be removed, and then remove them. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27205-E

The number of compute ports after the addition exceeds the upper limit. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Max. number of compute ports exceeded)

[Category]

StorageNode

[Solution]

Review the maximum number of supported compute ports and the number of compute ports to be added, and then retry the operation. If EC2 instances of the storage node to be added were created, delete the EC2 instances before the retry. To delete them, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27206-E

An error occurred in the DNS settings. (Job ID = xxx, Storage node = xxx, DNS server = xxx)

[Event Name]

The storage nodes could not be added (DNS setting did not succeed)

[Category]

StorageNode

[Solution]

If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27207-E

Storage node addition could not be completed because storage controllers could not be relocated. (Job ID = xxx)

[Event Name]

Storage controllers cannot be relocated

[Category]

StorageNode

[Solution]

If any of the storage nodes in the storage cluster are under maintenance, complete the processing for the storage nodes. If any of the storage nodes in the storage cluster are blocked, recover the storage nodes. After that, if EC2 instances of the storage node to be added were created, delete them, and then retry the operation. To delete them, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27210-E

FaultDomainName of each storage node to be added must be different. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (FaultDomainName of the storage node to be added invalid)

[Category]

StorageNode

[Solution]

Review FaultDomainName of the storage nodes to be added to verify whether there is a problem. Correct any problem, as necessary. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27211-E

The user data protection type xxx is not supported. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (User data protection type unsupported)

[Category]

StorageNode

[Solution]

Review the user data protection type to verify whether there is a problem. Correct any problem, as necessary. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27212-E

The number of storage nodes to be added must be xxx.

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Review the number of storage nodes to be added to verify whether there is a problem. Correct any problem, as necessary. If EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27220-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. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Spread placement group ID mismatch)

[Category]

StorageNode

[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.

KARS27221-E

The AMI ID is invalid. (Job ID = xxx)

[Event Name]

AMI ID is invalid

[Category]

StorageNode

[Solution]

Verify whether the AMI ID specified for configuration file export is correct. If there is any error, export the configuration file with a correct AMI ID specified to obtain a VM configuration file. Also, verify the storage node status according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference, and then troubleshoot any problem. After that, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27222-E

The storage cluster setting could not be verified. (Job ID = xxx)

[Event Name]

Storage cluster settings verification failed

[Category]

StorageNode

[Solution]

Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27223-E

The storage cluster setting could not be verified. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Storage cluster settings verification failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27224-E

Connection of the internode network could not be verified. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Internode network communication error

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27226-E

An error occurred in communication with the DNS server. (Job ID = xxx, DNS server = xxx)

[Event Name]

DNS server communication error

[Category]

StorageNode

[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 EC2 instances on AWS, and then troubleshoot any problem. Delete the storage node EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27229-E

Information could not be obtained from the subnet stack. (Job ID = xxx)

[Event Name]

Obtaining resource information failed

[Category]

StorageNode

[Solution]

Verify whether the network resource specified for the VM configuration file subnet stack name matches AZ configuration of the VM configuration file. If they do not match, create a network resource by using an appropriate cloud configuration file, modify the VM configuration file subnet stack name to the value of the created resource, and then retry the operation. If the same error occurs after retry, collect the installer logs, and then contact customer support.

KARS27230-E

An error occurred in communication with the DNS server. (Job ID = xxx, DNS server = xxx)

[Event Name]

DNS server communication error

[Category]

StorageNode

[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 EC2 instances on AWS, and then troubleshoot any problem. Delete the created storage node stacks, and then retry the operation. To delete the stacks, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27231-E

Stacks could not be updated. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Stack update failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27233-E

The version of the storage cluster and the AMI version of the storage node to be added do not match. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (AMI version mismatch)

[Category]

StorageNode

[Solution]

Verify whether the AMI ID (of the storage node to be added) specified for configuration file export is correct. If there is any error, export the configuration file with a correct AMI ID specified to obtain a VM configuration file. Also, verify the storage node status according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference, and then troubleshoot any problem. After that, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27234-E

The AMI version of the storage node to be replaced and the version of the storage node to be replaced do not match. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (AMI version mismatch)

[Category]

StorageNode

[Solution]

Verify whether the AMI ID (of the storage node to be replaced) specified for configuration file export is correct. If there is any error, export the configuration file with a correct AMI ID specified to obtain a VM configuration file. Also, verify the storage node status according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference, and then troubleshoot any problem. After that, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27239-E

An error occurred during syntax checking of the VM configuration file. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Configuration file syntax error

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27241-E

Storage node EC2 instances that are not included in configuration information about the configured storage cluster exist. (Job ID = xxx)

[Event Name]

Maintenance function pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Delete the storage node EC2 instances that are not included in configuration information about the configured storage cluster, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27242-E

Information could not be obtained from the subnet stack. (Job ID = xxx)

[Event Name]

Obtaining resource information failed

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27243-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify that the configuration file is correct, and then retry the operation. If you are adding a storage node for which the EC2 instances has been created, remove the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the installer logs, and then contact customer support.

KARS27245-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Wait for a while, and then retry the operation. If you performed storage node addition and EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27246-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify the installer version and storage software version. If those versions do not match, retry configuration file export by using the installer of the same version as that of the storage software. If those versions match, wait for a while, and then run the export command again. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27247-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether failure information about AWS is reported. Or, verify that the execution environment and operation are correct, delete the created storage node EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27248-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[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. To delete the stacks, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27249-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If you performed storage node addition and EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27250-E

The AMI specified with the machine image ID does not exist. (Job ID = xxx)

[Event Name]

Option check for configuration export (AMI specification)

[Category]

StorageNode

[Solution]

Verify whether the specified AMI is available. Review the parameter settings, and then retry the operation.

KARS27251-E

Storage nodes cannot be added because a storage node that could not be removed exists in the storage cluster. (Job ID = xxx)

[Event Name]

Configuration file export pre-check (AddStorageNodes specification)

[Category]

StorageNode

[Solution]

Remove the storage node that could not be removed. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27252-E

Initiator node cannot be removed because an initiator node exists in the VSSB configuration file. (Job ID = xxx)

[Event Name]

Configuration file export pre-check (RemoveInitiatorNode specification)

[Category]

StorageNode

[Solution]

Verify whether the specified parameter is correct. If the specification is incorrect, specify the correct value, and then retry the operation. If the specification is correct, remove the initiator node. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27253-E

Initiator node cannot be removed because the setting value for the initiator node does not exist in the VM configuration file. (Job ID = xxx)

[Event Name]

Configuration file export pre-check (RemoveInitiatorNode specification)

[Category]

StorageNode

[Solution]

Verify that the specified request destination is the IP address of the load balancer (ELB) or the cluster master node (primary). Also, verify whether the specified parameter is correct. If the values are incorrect, specify the correct arguments, and then retry the operation.

KARS27254-E

Information about the drive to be replaced could not be obtained from AWS. (Job ID = xxx)

[Event Name]

Obtaining information from the cloud platform failed

[Category]

StorageNode

[Solution]

Verify whether failure information about AWS is reported. 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 EC2 instances on AWS, and then resolve any problem. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27255-E

VM configuration file could not be obtained. (Job ID = xxx)

[Event Name]

Obtaining configuration files failed

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the Amazon S3 storage location, settings, or network settings in the specified VM configuration file. If there is any problem, resolve it, and then retry the operation.

KARS27257-E

All the storage nodes to be added must be included in the same spread placement group. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Invalid spread placement group setting)

[Category]

StorageNode

[Solution]

Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27260-E

The storage nodes to be added must belong to a new spread placement group. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Invalid spread placement group ID)

[Category]

StorageNode

[Solution]

Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27261-E

The initiator nodes is not included in a spread placement group. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Invalid spread placement group setting)

[Category]

StorageNode

[Solution]

Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27262-E

Integrity of the configuration file could not be verified. (Job ID = xxx)

[Event Name]

Maintenance pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If you performed storage node addition and EC2 instances of storage nodes to be added were created, delete the EC2 instances, and then retry the operation. If the EC2 instance of the storage node to be added is created, remove the EC2 instance, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27263-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether failure information about AWS is reported. Or, verify that the execution environment or operation is correct, remove the created storage node EC2 instance, and then retry the operation. To delete the EC2 instance, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27265-E

Integrity of the configuration file could not be verified. (Job ID = xxx)

[Event Name]

Maintenance pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27266-E

The version of the storage cluster and the AMI version of the storage node to be added do not match. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (AMI version mismatch)

[Category]

StorageNode

[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 dump log files, and then contact customer support.

KARS27267-E

Storage node stacks could not be updated. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Stack creation failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27300-E

A required option is not specified. (Job ID = xxx, Required option = xxx)

[Event Name]

Option check for configuration export (Required option not specified)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27301-E

Storage nodes cannot be added because the number of storage nodes has already reached the maximum allowable number. (Job ID = xxx, Count of storage node = xxx)

[Event Name]

Option check for configuration export (Check node number upper limit)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation. If the error is output even when the maximum number of storage nodes has not been reached, collect the dump log files, and then contact customer support.

KARS27302-E

The specified image cannot be used. (Job ID = xxx)

[Event Name]

Option check for configuration export (Check for the specified image)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation. Verify whether the specified image is available. Also, verify that the specified image format is correct, and then retry the operation.

KARS27303-E

The number of specified drives exceeds the allowable number of drives that can be installed on one storage node. (Job ID = xxx, Allowable range of the number of drives : xxx to xxx)

[Event Name]

Option check for configuration export (Check drive number upper limit)

[Category]

StorageNode

[Solution]

Specify an allowable number of drives, and then retry configuration file export. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27304-E

The specified operation cannot be performed because the version of the storage cluster and that of the ARM template do not match. (Job ID = xxx, Cluster version = xxx, Template version = xxx)

[Event Name]

Option check for configuration export (Version mismatch of the storage cluster and template)

[Category]

StorageNode

[Solution]

Verify that the storage cluster version is as intended. If there is an issue, refer to the VSP One SDS Block and SDS Cloud System Administration and perform the necessary operations after the software update to match the stack template version. If the same error occurs after retrying, collect the dump log files and contact customer support.

KARS27305-E

A duplicated IP address is specified. (Job ID = xxx, Duplicate addressSetting Index = xxx)

[Event Name]

Option check for configuration export (Specified IP address duplicated)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27306-E

The specified IP address has already been used in the storage cluster. (Job ID = xxx, Duplicate addressSetting Index = xxx)

[Event Name]

Option check for configuration export (Specified IP address already used)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27307-E

The number of additional nodes and the number of IP addresses to be allocated to the additional nodes do not match. (Job ID = xxx, Number of additional nodes = xxx, Number of specified IP addresses = xxx)

[Event Name]

Option check for configuration export (Mismatch of number of IP addresses and additional nodes)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27308-E

addressSetting indexes are not unique consecutive numbers starting with 1. (Job ID = xxx)

[Event Name]

Option check for configuration export (Invalid addressSetting index)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27309-E

Azure authentication did not succeed. (Job ID = xxx)

[Event Name]

Azure authentication failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Also, verify whether the control network settings are correct. If there is a problem, resolve it. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27310-E

The number of indexes for addressSetting exceeds the maximum number of indexes that can be added simultaneously. (Job ID = xxx)

[Event Name]

Option check for configuration export (addressSetting index upper limit)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27311-E

The availabilityZone in which the initiator node is to be added has not been specified or the specified format is incorrect. (Job ID = xxx)

[Event Name]

Option check for configuration export (Invalid Availability Zone)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27312-E

The same availabilityZone as that for a TB node has been specified as the availabilityZone in which the initiator node is to be added. (Job ID = xxx)

[Event Name]

Option check for configuration export (Specified Availability Zone matches TB)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27313-E

Azure CLI did not succeed. (Job ID = xxx)

[Event Name]

Azure CLI for configuration export failed

[Category]

StorageNode

[Solution]

Verify whether there is a problem with Azure services. Correct any problem as necessary. If the problem persists, collect the logs, and then contact customer support.

KARS27314-E

exportFileType is not specified correctly. (Job ID = xxx)

[Event Name]

Maintenance operation option check for configuration export (Invalid exportFileType)

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27400-E

Synchronization with the Azure host was unsuccessful. (Job ID = xxx, Storage node = xxx)

[Event Name]

Storage node addition did not succeed (Time Synchronization error)

[Category]

StorageNode

[Solution]

Verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Also, contact Azure support to verify whether the Azure host has any problem providing time information. If VMs of storage nodes to be added were created, delete the VMs before the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. Then, retry the operation that was being performed.

KARS27401-E

Synchronization with the Azure host was unsuccessful. (Job ID = xxx, Storage node = xxx)

[Event Name]

Storage node recovery failed (Time Synchronization error)

[Category]

StorageNode

[Solution]

Verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Also, contact Azure support to verify whether the Azure host has any problem providing time information. After the problem is resolved, perform storage node replacement.

KARS27402-E

An error occurred while communicating with the storage node to be added. (Job ID = xxx, IP address = xxx)

[Event Name]

Storage node addition failed (Storage node communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings. If there is a problem, resolve it, and then retry the operation. Also, verify the status of the storage node VMs on the cloud platform, troubleshoot any problem, and then retry the operation. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27403-E

An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx)

[Event Name]

Storage node addition failed (DNS server communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. Then, retry the operation.

KARS27404-E

An error occurred while communicating with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx)

[Event Name]

Storage node addition failed (NTP server communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. Then, retry the operation.

KARS27405-E

Synchronization with the NTP server did not succeed. (Job ID = xxx, Storage node = xxx, NTP server = xxx)

[Event Name]

Storage node addition did not succeed (Time Synchronization error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. Then, retry the operation.

KARS27406-I

Cloud resource creation is started. To confirm the creation status, verify xxx of cluster resource groups with Azure CLI or with Azure Portal. (Job ID = xxx)

[Event Name]

Deployment started

[Category]

StorageNode

[Solution]

Verify Azure Portal to confirm the creation status.

KARS27407-I

Cloud resource creation is completed. Wait until the job (Job ID = xxx) is complete.

[Event Name]

Deployment completed

[Category]

StorageNode

[Solution]

Verify that the resource has been created with Azure Portal.

KARS27408-E

Integrity of the configuration file could not be verified. (Job ID = xxx)

[Event Name]

Configuration file integrity check (Integrity check error)

[Category]

StorageNode

[Solution]

Verify whether operation procedures are correct. Also, verify that the operation content matches that specified for configuration file export. Then, retry the operation from exporting the configuration file according to the VSP One SDS Block and SDS Cloud System Administration. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27409-E

Azure CLI could not be run. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Azure CLI failed

[Category]

StorageNode

[Solution]

See the error message file indicated in Error message file to troubleshoot the problem.

KARS27410-E

A cloud resource could not be created. (Job ID = xxx)

[Event Name]

Cloud resource creation failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Also, verify whether the status of storage node resources and the deploy status of resource groups are correct. If there is a problem, resolve it. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27411-E

Cloud resource creation was canceled by a user. (Job ID = xxx)

[Event Name]

Cloud resource creation canceled

[Category]

StorageNode

[Solution]

Verify the status of the storage node resources on the cloud platform and the deploy status of resource groups on the cloud platform, and then troubleshoot any problem. If an operation is canceled inadvertently, delete the cloud resources according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference as necessary. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27412-E

Cloud resource creation timed out. (Job ID = xxx, Time limit = xxxminutes)

[Event Name]

Cloud resource creation timed out

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Also, verify whether the status of storage node resources and the deploy status of resource groups are correct. If there is a problem, resolve it. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27413-E

Cloud resource deletion was unsuccessful. (Job ID = xxx)

[Event Name]

Cloud resource deletion failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Also, verify whether the status of storage node resources and the deploy status of resource groups are correct. If there is a problem, resolve it. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27414-E

Blob Storage could not be accessed. (Job ID = xxx, Storage account = xxx)

[Event Name]

Blob Storage access failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Also, verify whether the control network settings are correct. If there is a problem, resolve it. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27415-W

Cloud infrastructure maintenance is scheduled. Storage node maintenance recovery affected by the maintenance is suppressed until the maintenance is complete. (Job ID = xxx)

[Event Name]

Storage node maintenance recovery suppressed

[Category]

StorageNode

[Solution]

Verify that event log KARS08332-W (indicating that cloud infrastructure maintenance is scheduled) is output, and then take action according to the event log. If output of KARS08332-W cannot be confirmed, take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27440-E

An error occurred during storage node addition processing. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition failed

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. After that, verify whether there are storage nodes that need to be removed, and then remove them. If the VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27441-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition failed (Storage node internal processing error)

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. After that, verify whether there are storage nodes that need to be removed, and then remove any storage nodes. If the VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27442-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Storage node internal processing error)

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. After that, if VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27443-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition failed (Storage cluster internal processing error)

[Category]

StorageCluster

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, if a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27444-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Storage node internal processing error)

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. After that, retry the maintenance operation. If the VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27445-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Storage cluster internal processing error)

[Category]

StorageCluster

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. Verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the maintenance operation. If the VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27451-E

Rebuilding the storage controller in the storage node did not succeed. (Job ID = xxx, Storage node ID = xxx, Storage controller ID = xxx)

[Event Name]

Storage controller rebuild failed

[Category]

StorageNode

[Solution]

See event logs indicating other errors, if any, and then take action. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If errors persist after retry, collect the dump log files, and then contact customer support.

KARS27452-E

An error occurred in the internode network with the storage node to be recovered. (Job ID = xxx, Storage node ID = xxx, IP address = xxx)

[Event Name]

Storage node recovery pre-check (Communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (internode network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, restart the storage node to be recovered, and then retry the operation.

KARS27453-E

The process could not be started on the storage node to be recovered. (Job ID = xxx, Storage node ID = xxx)

[Event Name]

Process starting error for storage node recovery

[Category]

StorageNode

[Solution]

See event logs indicating other errors, if any, and then take action. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry recovery of the storage node to be recovered. If the problem persists, perform recovery by storage node replacement.

KARS27454-E

An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx)

[Event Name]

Storage node recovery failed (DNS server communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, perform storage node replacement.

KARS27455-E

An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx)

[Event Name]

Storage node recovery failed (NTP server communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, replace the storage node.

KARS27456-E

Synchronization with the NTP server did not succeed. (Job ID = xxx, Storage node = xxx, NTP server = xxx)

[Event Name]

The storage node could not be recovered (Time Synchronization error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (control network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, replace the storage node.

KARS27457-E

The operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx)

[Event Name]

Storage node recovery failed (Cluster master node (primary) failover)

[Category]

StorageNode

[Solution]

Verify whether any event log indicating failures is output to help identify the cause of the failure of the cluster master node (primary). If such an event log is output, take action according to the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, recover the target storage node. If the storage node status meets the conditions for Storage node auto-recovery, maintenance recovery is automatically performed, so no action is required.

KARS27458-E

An error occurred in the internode network with the storage node to be recovered. (Job ID = xxx, Storage node ID = xxx, IP address = xxx)

[Event Name]

Storage node recovery pre-check (Internode network communication error)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (internode network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, restart the storage node. After that, recover the target storage node. If the storage node status meets the conditions for Storage node auto-recovery, maintenance recovery is automatically performed, so no action is required.

KARS27459-E

Integrity of the configuration file could not be verified. (Job ID = xxx)

[Event Name]

Maintenance pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Perform configuration file export, and then retry the operation. If you performed storage node addition and VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27460-E

An error occurred while accessing the database. (Job ID = xxx)

[Event Name]

Database access error

[Category]

StorageNode

[Solution]

See the event logs indicating other errors, if any, and then take action. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If errors persist after retry, collect the dump log files, and then contact customer support.

KARS27461-E

An error occurred in the internode network communication. (Job ID = xxx, IP address = xxx)

[Event Name]

Internode network communication error

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (internode network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the operation.

KARS27462-E

An error occurred in the communicating storage node. (Job ID = xxx, IP address = xxx)

[Event Name]

Processing error in the communicating storage node

[Category]

StorageNode

[Solution]

Verify whether there is a problem with the network settings (internode network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Also, if there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. Then, retry the operation.

KARS27463-E

Operation for transferring the storage software update file to each storage node timed out. Therefore, software update did not succeed. (Job ID = xxx)

[Event Name]

Storage software update file transfer timed out

[Category]

StorageCluster

[Solution]

While storage pool capacity balancing, drive data relocation, rebuild, or other processing that uses internode network is in progress, wait until the processing completes. If I/O load is high, reduce the I/O load. Verify whether there is a problem with the network settings (internode network), and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the software update.

KARS27464-E

The storage node could not be stopped normally. (Job ID = xxx, Storage node ID = xxx)

[Event Name]

Storage node shutdown failed (Manual stop required)

[Category]

StorageNode

[Solution]

If the target storage node VM is not stopped, stop it manually.

KARS27465-E

The storage node could not be restarted. (Job ID = xxx, Storage node ID = xxx)

[Event Name]

Storage node restart failed (Manual restart required)

[Category]

StorageNode

[Solution]

Restart the target storage node VM manually.

KARS27490-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node internal processing error

[Category]

StorageNode

[Solution]

See event logs indicating other errors, if any, and then take action. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, if the storage node to be recovered is blocked, recover the target storage node by performing storage node maintenance recovery. If the problem persists, collect the dump log files, and then contact customer support.

KARS27491-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node internal processing error

[Category]

StorageNode

[Solution]

See the event logs indicating other errors, if any, and then take action. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. If errors persist after retry, collect the dump log files, and then contact customer support.

KARS27492-E

Maintenance operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx)

[Event Name]

Cluster master node (primary) error

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the maintenance operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27493-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the maintenance operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27494-E

An internal error occurred. (Operation = xxx, Job ID = xxx)

[Event Name]

Storage cluster internal processing error (Retry)

[Category]

StorageCluster

[Solution]

If there is an event log with the same job ID as this job, or one that indicates a failure not related to this job, correct the failure according to the recovery procedure described in the event log. If no such event log is output, verify whether there is a problem with the network settings, and then resolve any problem. Also, verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Then, retry the maintenance operation. If the problem persists, collect the dump log files, and then contact customer support.

KARS27520-E

Parameters specified when creating storage node cloud resources with Azure Resource Manager are incorrect.

xxx

[Solution]

Review the parameters specified when creating cloud resources with Azure Resource Manager according to the message. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27521-E

Synchronization with the Azure host was unsuccessful.

[Solution]

Verify the status of the storage node VMs on the cloud platform, and then troubleshoot any problem. Also, contact Azure support to verify whether the Azure host has any problem providing time information. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27524-E

Storage node cloud resource creation was canceled by a user.

[Solution]

Verify the status of the storage node cloud resource by operating the cloud platform console. Delete the storage node cloud resource that was created, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27550-E

The specified operation cannot be performed because the version of the Terraform template and that of the storage cluster do not match. (Job ID = xxx, Cluster version = xxx, Template version = xxx)

[Event Name]

Version mismatch of the Terraform template and storage cluster

[Category]

StorageNode

[Solution]

Verify that the storage cluster version is as intended. If there is a problem, correct the version. If there is no problem, perform postprocessing of the software update according to the manual, and then retry the operation. If the same error occurs even after executing the command again, collect the dump log file, and then contact customer support.

KARS27551-E

When exportFileType is set to ReplaceDrive, there is an error in the parameter settings (driveId and recoverSingleDrive). (Job ID = xxx)

[Event Name]

Parameter settings error for ReplaceDrive

[Category]

StorageNode

[Solution]

Review the parameter settings, and then retry the operation.

KARS27552-E

The replacement drive is unavailable. (Job ID = xxx)

[Event Name]

uuid specified for driveId is unavailable

[Category]

StorageNode

[Solution]

Review the specified drive ID, and then retry the operation.

KARS27553-E

Information could not be obtained with Google CLI. (Job ID = xxx)

[Event Name]

Obtaining information with Google CLI failed

[Category]

StorageNode

[Solution]

Retry the operation, or verify that no failure occurred in Google Cloud. If the problem persists, verify whether the service account is correct and a custom role has been assigned.

KARS27554-E

The replacement node is unavailable. (Job ID = xxx)

[Event Name]

uuid specified for nodeId is unavailable

[Category]

StorageNode

[Solution]

Review the specified storage node ID, and then retry the operation.

KARS27602-E

Terraform state lock was detected. (Job ID = xxx)

[Event Name]

Terraform state lock was detected

[Category]

StorageNode

[Solution]

Verify whether the Terraform command is running. If the command is running, wait until the command completes, and then retry the operation. If the command is not running, verify the lock ID from the terraform plan output, perform unlock with terraform force-unlock, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27603-E

An error occurred in storage node configuration checking. (Job ID = xxx)

[Event Name]

Storage node configuration checking failed

[Category]

StorageNode

[Solution]

Verify whether the parameter specified for configuration file export is correct. Or, verify whether the VM creation operation with Terraform is correct, delete the created VM, and then retry the operation from exporting the configuration file. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27604-E

The IP address reservation name of the additional storage node is already used. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

IP address reservation name is already used

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27605-E

Connection to the cloud storage from the storage node was unsuccessful. (Job ID = xxx)

[Event Name]

Connection to the cloud storage failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27606-E

An error occurred in storage node configuration checking. (Job ID = xxx)

[Event Name]

Storage node configuration checking failed

[Category]

StorageNode

[Solution]

Verify whether the VM creation operation with Terraform is correct, delete the created VM, and then retry the operation from exporting the configuration file. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27607-E

An error occurred in storage node configuration checking. The IPv6 address of the compute port differs from the set value. (Job ID = xxx)

[Event Name]

Storage node configuration checking failed

[Category]

StorageNode

[Solution]

Verify that the set IPv6 address is correct. If it is not correct, delete the created VM, and then retry the operation from exporting the configuration file. Also, verify whether the set IPv6 address is used by another VM. If the IPv6 address is used by another VM, make the IPv6 address unused by another VM, delete the created VM, and then retry the operation from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27750-E

Parameters specified when creating storage node cloud resources with Terraform are incorrect.

xxx

[Solution]

Review the parameters specified when creating cloud resources with Terraform according to the message. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27751-E

Synchronization with the NTP server was unsuccessful. (NTP server = xxx)

[Solution]

Verify whether failure information about the cloud platform 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 the cloud platform, and then troubleshoot any problem. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27752-E

Connection to the folder specified for the gsUri parameter was unsuccessful. (Cloud Storage URI = xxx)

[Solution]

Verify whether a folder exists in the cloud storage URI indicated in the message. If no folder exists, verify whether the specification for the gsUri parameter is correct, and then correct any error as necessary. Also, if no folder has been created, create one. Or, if a folder exists, verify whether failure information about the cloud platform is reported. Then, verify that the execution environment and operation are correct, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27753-E

Connection from the storage node to the cloud storage failed.

[Solution]

Verify whether failure information about cloud platform is reported. Or, verify that the execution environment or operation is correct, remove the created storage node cloud resources, and then retry the operation. To delete it, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27754-E

The version of the VM configuration file template and that of the storage node software do not match.

[Solution]

Verify that the latest VM configuration file is used and the latest VM image is specified, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27755-E

The IP address reservation name of the storage node has already been used.

[Solution]

Release the reservation of the address name indicated in Additional Information, delete the created storage node cloud resources, and then retry the operation. To release the reservation and delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27756-E

Storage cluster configuration could not be verified.

[Solution]

Verify that the values and their combination entered in the template are correct and the template is the latest. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27757-E

Storage cluster configuration could not be verified.

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the template is the latest and the execution environment and operation are correct, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27758-E

Connection to the folder specified for the bucket and prefix parameters of the backend.auto.tfvars file was unsuccessful. (Cloud Storage URI = gs://xxx/xxx/, bucket = xxx, prefix = xxx)

[Solution]

Verify whether a folder exists in the cloud storage URI indicated in the message. If no folder exists, verify whether the specification for the bucket and prefix parameters is correct and correct any error as necessary. Also, if no folder has been created, create one. Or, if a folder exists, verify whether failure information about the cloud platform is reported, delete the folder, and then recreate one. Then, verify that the execution environment and operation are correct, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27759-E

The storage cluster configuration could not be verified. The IPv6 address of the compute port differs from the set value.

[Solution]

Verify that the set IPv6 address is correct. If it is not correct, delete the created storage node cloud resources by using the VM configuration file created for configuration backup, and then retry the operation. Also, verify whether the set IPv6 address is used by another VM. If the IPv6 address is used by another VM, make the IPv6 address unused by another VM, delete the created storage node cloud resources, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27760-E

Storage cluster configuration could not be verified.

[Solution]

If any message is shown in Additional Information, see the message to troubleshoot the problem. Or, verify that the template is the latest and the execution environment and operation are correct, delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27850-E

Memory is insufficient. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Insufficient memory)

[Category]

StorageNode

[Solution]

Restart the storage cluster, and then retry the operation. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27851-E

An operation that can not be performed concurrently is being performed. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Prohibited concurrent operation)

[Category]

StorageNode

[Solution]

Wait until the operation that cannot be performed concurrently is complete, and then retry the operation. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27852-E

The number of storage nodes after the addition exceeds the upper limit. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Max. number of storage nodes exceeded)

[Category]

StorageNode

[Solution]

Review the maximum number of supported storage nodes and the number of storage nodes to be added, and then retry the operation. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27853-E

An error occurred during verification of software versions of the storage node to be added. (Job ID = xxx, Version of storage cluster = xxx, Version of the storage node to be added = xxx)

[Event Name]

Storage node addition pre-check (Software version mismatch)

[Category]

StorageNode

[Solution]

Verify that the software version of the storage node to be added matches that of the storage cluster, and then retry the operation. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27854-E

Adding storage nodes ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Storage cluster master node (primary) failover)

[Category]

StorageNode

[Solution]

If storage nodes are blocked, restore them. Verify whether there are storage nodes to be removed, and then remove them. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27855-E

The number of compute ports after the addition exceeds the upper limit. (Job ID = xxx)

[Event Name]

Storage node addition did not succeed (Max. number of compute ports exceeded)

[Category]

StorageNode

[Solution]

Review the maximum number of supported compute ports and the number of compute ports to be added, and then retry the operation. If the VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27856-E

An error occurred in the DNS settings. (Job ID = xxx, Storage node = xxx, DNS server = xxx)

[Event Name]

The storage nodes could not be added (DNS setting did not succeed)

[Category]

StorageNode

[Solution]

If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27857-E

Storage node addition could not be completed because storage controllers could not be relocated. (Job ID = xxx)

[Event Name]

Storage controllers cannot be relocated

[Category]

StorageNode

[Solution]

If any of the storage nodes in the storage cluster are under maintenance, complete the processing for those storage nodes. If any of the storage nodes in the storage cluster are blocked, recover those storage nodes. After that, if a VM is created for the storage nodes to be added, remove the VM, and then retry the storage node addition. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27858-E

FaultDomainName of each storage node to be added must be different. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (FaultDomainName of the storage node to be added invalid)

[Category]

StorageNode

[Solution]

Review FaultDomainName of the storage nodes to be added to verify whether there is a problem. Correct any problem, as necessary. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27859-E

The user data protection type xxx is not supported. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (User data protection type unsupported)

[Category]

StorageNode

[Solution]

Review the user data protection type to verify whether there is a problem. Correct any problem, as necessary. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27860-E

The number of storage nodes to be added must be xxx.

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Review the number of storage nodes to be added to verify whether there is a problem. Correct any problem, as necessary. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the problem persists, collect the dump log files, and then contact customer support.

KARS27862-E

The storage node could not be replaced. (Job ID = xxx)

[Event Name]

The storage node could not be recovered

[Category]

StorageNode

[Solution]

Take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27863-E

The execution results of the storage node replacement could not be obtained. (Job ID = xxx)

[Event Name]

Storage node recovery failed (Obtaining execution results unsuccessful)

[Category]

StorageNode

[Solution]

Take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

KARS27865-E

Operation was unsuccessful because the storage node was blocked. (Job ID = xxx, Storage node IDs = xxx)

[Event Name]

Operation failed

[Category]

StorageNode

[Solution]

Recover the blocked storage node, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27867-E

Multiple initiator nodes are specified for the storage node to be added. Only one initiator node can be added at a time. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Addition of multiple storage nodes including initiator nodes)

[Category]

StorageNode

[Solution]

Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27868-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. (Job ID = xxx, Fault domain names = xxx)

[Event Name]

Storage node addition pre-check (Fault domain name of additional storage node invalid)

[Category]

StorageNode

[Solution]

Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27869-E

This configuration (RedundantPolicy = xxx) is not supported. (Job ID = xxx)

[Event Name]

The storage nodes could not be added (Invalid configuration files)

[Category]

StorageCluster

[Solution]

Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27871-E

Operation was unsuccessful because the storage node to be replaced does not exist in the configured storage cluster. (Job ID = xxx, Storage node ID = xxx)

[Event Name]

Storage node replacement pre-check (Storage node to be replaced does not exist)

[Category]

StorageNode

[Solution]

Verify whether the specified value for 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 dump log files, and then contact customer support.

KARS27872-E

The name of the storage node to be replaced does not exist in the configuration file. (Job ID = xxx, VM name = xxx, Host name = xxx)

[Event Name]

Storage node replacement pre-check (Storage node to be replaced does not exist)

[Category]

StorageNode

[Solution]

Verify that the 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 dump log files, and then contact customer support.

KARS27873-E

The operation cannot be performed because the storage cluster status is not "Ready". (Job ID = xxx)

[Event Name]

The status in which the storage cluster status is not "Ready"

[Category]

StorageCluster

[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.

KARS27874-E

A key pair could not be created. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Key pair creation failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27875-E

Changes were made other than storage node addition in the VM configuration file. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

The storage nodes could not be added (Invalid configuration files)

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27877-E

A key pair file does not exist or is incorrect. (Job ID = xxx)

[Event Name]

Key pair verification failed

[Category]

StorageNode

[Solution]

Verify whether a key pair file exists and it matches the KeyPair setting of the VM configuration file.

KARS27878-E

The VM configuration file contains illegal changes. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Maintenance pre-check (Invalid changes in the file description)

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27879-E

The key pair could not be removed. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Key pair deletion failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27880-E

Information could not be obtained from the cloud platform. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Obtaining information from cloud platform failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27881-E

When the user data protection type (RedundantType) is xxx, the number of storage nodes to be added must be xxx. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27883-E

The AMI version of the storage node to be replaced and the version of the storage node to be replaced do not match. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (AMI version mismatch)

[Category]

StorageNode

[Solution]

Modify the AMI setting of the storage node to be replaced 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 dump log files, and then contact customer support.

KARS27884-E

AMI information could not be obtained. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Obtaining AMI information failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27885-E

The storage node to be replaced is not in a status that allows for replacement. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Invalid status of the storage node to be replaced)

[Category]

StorageNode

[Solution]

Verify whether the ID 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 dump log files, and then contact customer support.

KARS27886-E

The user data protection type xxx set in the VM configuration file is not supported.

[Event Name]

Storage node addition pre-check (Protection type unsupported)

[Category]

StorageNode

[Solution]

Correct the VM configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27887-E

Multiple fault domain configuration is not supported. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Addition in unsupported configuration)

[Category]

StorageNode

[Solution]

Correct the configuration file according to the message, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27889-E

The number of fault domains of the storage cluster is out of range. (Job ID = xxx, The number of fault domains = xxx)

[Event Name]

Storage node addition pre-check (Number of fault domains out of range)

[Category]

StorageNode

[Solution]

Review the number of fault domains of the configuration file to verify whether there is a problem. Correct any problem, as necessary. Then, retry the operation.

KARS27890-E

The number of storage nodes to be added must be xxx. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Review the number of storage nodes to be added to verify whether there is a problem. Correct any problem, as necessary. Then, retry the operation.

KARS27891-E

The attribute (storageNodeAttributes) of the storage node to be replaced cannot be changed. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Attribute change unavailable)

[Category]

StorageNode

[Solution]

Review the setting of the storage node to be replaced to verify whether there is a problem. Correct any problem, as necessary. Then, retry the operation.

KARS27892-E

The configuration information could not be referenced from the configured storage cluster. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Viewing configuration information from storage cluster failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27895-E

The configuration file could not be read. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

The configuration file could not be read

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27896-E

Two or more protocols exist for compute ports in the storage cluster. (Job ID = xxx)

[Event Name]

The storage nodes could not be added (Different compute port protocols exist)

[Category]

StorageCluster

[Solution]

Retry the operation from exporting the configuration file according to the VSP One SDS Block and SDS Cloud System Administration. If VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27898-E

The number of storage nodes in configuration files does not match the actual configuration. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Number of storage nodes mismatch)

[Category]

StorageNode

[Solution]

Retry the operation from exporting the configuration file according to the VSP One SDS Block and SDS Cloud System Administration.

KARS27899-E

Information could not be obtained from the cloud platform. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Obtaining information from cloud platform failed

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27900-E

The configuration file could not be read. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

The configuration file could not be read

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27904-E

The configuration file could not be read. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

The configuration file could not be read

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27906-E

The number of storage nodes to be added must be xxx. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27907-E

The attribute (storageNodeAttributes) of the storage node to be replaced cannot be changed. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Attribute change unavailable)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27908-E

The number of fault domains of the storage cluster is out of range. (Job ID = xxx, The number of fault domains = xxx)

[Event Name]

Storage node addition pre-check (Number of fault domains out of range)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27909-E

A storage node that could not be removed exists in the storage cluster. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Storage node addition pre-check (Node that could not be removed exists in the storage cluster)

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27912-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify that the execution environment and operation are correct, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27913-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Wait for a while, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27914-E

The storage cluster setting could not be verified. (Job ID = xxx)

[Event Name]

Storage cluster settings verification failed

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27916-E

An error occurred in communication with the DNS server. (Job ID = xxx, DNS server = xxx)

[Event Name]

Storage cluster settings verification failed

[Category]

StorageNode

[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 the cloud platform, and then troubleshoot any problem. Delete the storage node VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27922-E

The version of the storage cluster and the VM image version of the storage node to be added do not match. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (VM image version mismatch)

[Category]

StorageNode

[Solution]

Verify whether the VM image ID (of the storage node to be added) specified for configuration file export is correct. If there is any error, specify the correct VM image ID, and then retry the operation from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27923-E

The VM image version of the storage node to be replaced and the version of the storage node to be replaced do not match. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (VM image version mismatch)

[Category]

StorageNode

[Solution]

Verify whether the VM image ID (of the storage node to be replaced) specified for configuration file export is correct. If there is any error, export the configuration file with a correct VM image ID specified to obtain a VM configuration file. Also, verify the storage node status according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference, and then troubleshoot any problem. After that, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27930-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Wait for a while, and then retry the operation. If you performed storage node addition and VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27931-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27932-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27933-E

An internal error occurred. (Job ID = xxx)

[Event Name]

Storage node internal processing error (Retry)

[Category]

StorageNode

[Solution]

Verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If you performed storage node addition and VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27934-E

An unexpected error occurred in the storage cluster. (Job ID = xxx)

[Event Name]

Storage node internal processing error

[Category]

StorageNode

[Solution]

Collect the dump log files, and then contact customer support.

KARS27935-E

The deployment type does not match between the storage cluster and the configuration file. (Job ID = xxx, Storage cluster deployment type = xxx)

[Event Name]

Maintenance pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Match the configuration file deployment type with the storage node deployment type of the storage cluster. Then, retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27936-E

The deployment type does not match between the storage cluster and the configuration file. (Job ID = xxx, Storage cluster deployment type = xxx)

[Event Name]

Maintenance pre-check (Description of the file is different from the configuration)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27937-E

A key pair could not be obtained. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Failed to obtain a key pair

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27938-E

Configuration information about the configured storage cluster could not be referenced. (Job ID = xxx, Error message file = xxx.txt)

[Event Name]

Failed to reference configuration information

[Category]

StorageNode

[Solution]

See the error message file shown in Error message file to troubleshoot the problem.

KARS27939-E

The number of storage nodes to be added must be xxx. (Job ID = xxx)

[Event Name]

Storage node addition pre-check (Number of additional storage nodes invalid)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27940-E

The attribute (storageNodeAttributes) of the storage node to be replaced cannot be changed. (Job ID = xxx)

[Event Name]

Storage node replacement pre-check (Attribute change unavailable)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27941-E

The number of fault domains of the storage cluster is out of range. (Job ID = xxx, Number of fault domains = xxx)

[Event Name]

Storage node addition pre-check (Number of fault domains out of range)

[Category]

StorageNode

[Solution]

Verify whether the configuration file is stored in the specified location correctly. Or, verify whether the procedures for exporting a configuration file are correct. If there is any problem, retry the operation with the correct procedures from exporting the configuration file. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27950-E

Resource information of the storage node VMs 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 the cloud platform, and then troubleshoot any problem. If storage node VMs were created, remove the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the installer logs, and then contact customer support.

KARS27951-E

Storage node cloud resources could not be created.

[Solution]

Operate the cloud platform console to verify the status of the storage node cloud resources. Also, verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27952-E

The storage cluster setting could not be verified.

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27953-E

The storage cluster setting could not be verified. xxx

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27954-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 the cloud platform, and then troubleshoot any problem. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27955-E

An error occurred in communication with the DNS server. (DNS server = xxx)

[Solution]

Verify whether failure information about the cloud platform 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 the cloud platform, and then troubleshoot any problem. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27956-E

The storage cluster could not be configured.

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27957-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 the cloud platform, and then troubleshoot any problem. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27958-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 cloud resources, and then retry the operation. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27960-E

An internal error occurred.

[Solution]

Verify whether there is a problem with procedures for exporting a configuration file. If there is a problem, retry the operation with correct procedures from exporting the configuration file. If you performed storage node addition and VMs of storage nodes to be added were created, delete the VMs, and then retry the operation. To delete the VM, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27961-E

An internal error occurred.

[Solution]

Verify whether failure information about the cloud platform is reported. Or, verify that the execution environment and operation are correct, delete the created storage node resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.

KARS27962-E

An unexpected error occurred in the storage cluster.

[Solution]

Collect the dump log files, and then contact customer support.

KARS27963-E

An error occurred while verifying a value of the configuration file.

[Solution]

The set 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 dump log files, and then contact customer support.

KARS27964-E

An internal error occurred.

[Solution]

Collect the dump log files, and then contact customer support.

KARS27965-E

Information could not be obtained from the cloud platform.

[Solution]

If any message is shown in Additional Information, see the message to troubleshoot the problem. Delete the created storage node cloud resources, and then retry the operation. To delete the cloud resources, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. If the same error occurs after retry, collect the dump log files, and then contact customer support.