Message ID |
Message |
|---|---|
KARS10000-I |
Import of the specified system requirements was skipped because they predate the system requirements registered in the storage cluster. (Job ID = xxx) [Event Name] Import of the system requirements file skipped [Category] StorageCluster |
KARS10001-E |
The system requirements file could not be imported. [Cause] The specified system requirements file is invalid. [Solution] Confirm that the specified file name is correct and the file is not corrupt, and then retry the operation. If the failure persists, obtain the latest system requirements file again, and then retry the operation. |
KARS10010-E |
The request could not be executed. [Cause] Configuration files could not be imported. [Solution] See the console message indicating causes of other failures, and then take action. |
KARS10011-E |
The configuration file could not be imported. [Cause] The number of the storage nodes in the configuration file is not correct. [Solution] See the console message indicating causes of other failures, and then take action. |
KARS10012-E |
The request could not be executed. [Cause] Configuration files could not be exported. [Solution] See the console message indicating causes of other failures, and then take action. |
KARS10013-E |
The configuration files could not be exported. [Cause] A failure occurred during export of configuration files. |
KARS10014-E |
Another operation is running. (Job ID = xxx) [Event Name] Exclusive control error during export [Category] StorageCluster [Cause] Configuration files could not be exported due to another operation in progress. [Solution] Wait for a while, and then retry the export operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10015-E |
An internal error occurred. (Job ID = xxx) [Event Name] Internal error during export [Category] StorageCluster [Cause] An internal error occurred during export of configuration files. [Solution] Wait for a while, and then retry the export operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10016-E |
Another export or download processing of configuration files is in progress. [Event Name] Exclusive control error of export processing (exclusion of export and download) [Category] StorageCluster [Cause] An exclusive control error occurred due to another export or download processing of configuration files. [Solution] Verify whether another export or download processing of configuration files is running. If such a process is in progress, wait until it completes, and then retry the operation. If no such processing is in progress, retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10080-I |
Configuration information was updated. [Event Name] Configuration information update completed [Category] StorageCluster |
KARS10100-I |
The update of xxx is started. (Job ID = xxx) [Event Name] Per-node update start [Category] StorageNode |
KARS10101-I |
The update of xxx is complete. (Job ID = xxx) [Event Name] Per-node update end [Category] StorageNode |
KARS10102-E |
xxx could not be updated. (Job ID = xxx) [Event Name] Per-node update failure [Category] StorageNode [Solution] See event logs indicating causes output for other failures, and then take action. |
KARS10103-W |
As a result of the software update, different software versions are used in storage nodes belonging to the storage cluster. (Job ID = xxx) [Event Name] Different software versions [Category] StorageCluster [Solution] See the event log to resolve the failure, and then, update the software. |
KARS10104-E |
The software update ended because an error was detected in the integrity check of the transferred storage software update file. (Job ID = xxx) [Event Name] Invalid storage software update file [Category] StorageCluster [Solution] Obtain the storage software update file, and transfer it to the storage system, and then update the storage software. |
KARS10105-E |
The software update ended because a failure occurs on the storage node in the storage cluster. (Job ID = xxx) [Event Name] Invalid software update conditions (Storage node failure) [Category] StorageNode [Solution] See event logs indicating causes output for other failures, and then resolve the failure. After that, update the software. |
KARS10106-E |
The software update ended because an incompatible version of the storage software update file was specified. (Job ID = xxx) [Event Name] Invalid software update conditions (Incompatible version of the storage software update file) [Category] StorageCluster [Solution] Obtain the compatible version of the storage software update file, and transfer it to the storage system, and then update the storage software. |
KARS10107-E |
Software update to the target version was aborted because 'xxx' was being used. (Job ID = xxx) [Event Name] Invalid software update conditions (The update file includes incompatible functions) [Category] StorageCluster [Solution] Disable the displayed function, or use an update file for the version which supports the displayed function. |
KARS10108-I |
The specified software update could not be performed because a software update is in progress. (Job ID = xxx, Job ID in progress = xxx) [Event Name] Invalid software update conditions (Multiple executions are not possible) [Category] StorageCluster |
KARS10109-E |
The software update was aborted because another operation is being performed. (Job ID = xxx, Another Job ID in progress = xxx) [Event Name] Invalid software update conditions (Simultaneous execution is not possible) [Category] StorageCluster [Solution] Wait until the displayed processing ends, and then retry the software update. |
KARS10110-E |
Software update was aborted because the storage software update file was not found. (Job ID = xxx) [Event Name] Storage software update file was not uploaded [Category] StorageCluster [Solution] Upload storage software update file. And retry the software update. |
KARS10111-E |
Software update was aborted due to an error in transferring the storage update file to the storage node. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage software update file transfer error [Category] StorageCluster [Solution] Verify the displayed storage node status. If storage nodes are blocked, restore them. |
KARS10112-E |
An initiator node that cannot be used in this version exists in the storage cluster. (Job ID = xxx, Storage node ID = xxx) [Event Name] Unsupported initiator node [Category] StorageCluster [Solution] Remove the target initiator node. |
KARS10113-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 balance, Drive data relocation or Rebuild, or other operations that use internode network are being performed, wait until those operations are completed. If I/O load is high, reduce the I/O load. Also, verify that internode network communication has no error, and then take action as required. Then, retry the software update. |
KARS10114-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. Also, verify whether there is a problem with the network settings (internode network), and then resolve any problem. In addition, verify the status of the storage node VMs on AWS, and then troubleshoot any problem. Then, retry the software update. |
KARS10115-E |
The storage software cannot be downgraded because parameters or options related to downgrade have not been correctly specified. (Job ID = xxx, Version of storage cluster = xxx, Version of the update file = xxx) [Event Name] Invalid software update setting (downgrade guard) [Category] StorageCluster [Solution] If you intend to perform downgrade, see the VSP One SDS Block REST API Reference or VSP One SDS Block CLI Reference to verify whether parameters or options related to downgrade have been correctly specified. If you do not intend to perform downgrade, verify whether the storage software update file is correct. Then, retry the operation from the procedure of uploading the storage software update file to a storage cluster. |
KARS10150-E |
The software update ended abnormally. [Cause] A failure occurred. [Solution] See the event log with the job ID of this job, and then resolve the failure according to the recovery procedure. After that, update the storage software. |
KARS10151-I |
The software update was stopped. [Cause] A request for stopping the software update was detected. [Solution] No action is required. |
KARS10152-I |
The storage software update file could not be uploaded. [Cause] An error was detected in the integrity check of the storage software update file. [Solution] Obtain the storage software update file. |
KARS10153-E |
The storage software update file could not be uploaded. [Cause] An internal error occurred in uploading the storage software update file. [Solution] Retry uploading of the storage software update file. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10200-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 a VM of the storage node to be added is created, remove the VM, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10201-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 the VM of the storage node to be added is created, remove the VM, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10210-E |
The configuration files is not uploaded. (Job ID = xxx) [Event Name] Storage node addition did not succeed (Configuration files not found) [Category] StorageNode [Solution] Upload the configuration files, 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. |
KARS10211-E |
An error occurred in the communication with the storage node to be added. (Job ID = xxx, Storage node ID = xxx, IP address = xxx) [Event Name] Storage node addition did not succeed (Communication with storage node error) [Category] StorageNode [Solution] Verify the network status, 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. |
KARS10212-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] Check the maximum number of supported storage nodes and the number of storage nodes 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. |
KARS10213-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 the VM of the storage node to be added is created, remove the VM, and then retry the operation. |
KARS10215-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 the 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. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10216-E |
An error occurred in the communication with the storage node to be added. (Job ID = xxx, IP address = xxx) [Event Name] Storage node addition did not succeed (Communication with storage node error) [Category] StorageNode [Solution] Verify the network status, 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. |
KARS10217-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. |
KARS10218-E |
Because Data migration is not supported in the storage cluster, an initiator node cannot be added. (Job ID = xxx) [Event Name] Unsupported version (Data migration) [Category] StorageCluster [Solution] To perform Data migration, update the software version of the current storage cluster to a version which supports such migration, and then retry the operation. |
KARS10219-E |
The configuration files includes invalid descriptions or unsupported parameters. (Job ID = xxx) [Event Name] The storage nodes could not be added (Invalid configuration files) [Category] StorageCluster [Solution] Review the descriptions of the configuration files for errors. Also, make sure that the software version of the current storage cluster supports the function to be used. |
KARS10220-E |
The storage node to be added does not exist in the configuration files. (Job ID = xxx) [Event Name] The storage nodes could not be added (Non-existing storage nodes for addition) [Category] StorageCluster [Solution] Review the descriptions of the configuration files for errors. |
KARS10221-E |
Because IPv6 is not supported in the storage cluster, a storage node whose IPv6Mode is enabled cannot be added. (Job ID = xxx) [Event Name] Unsupported version (Compute port IPv6) [Category] StorageCluster [Solution] To enable use with IPv6 settings, update the software version of the current storage cluster to a version that supports IPv6, and then retry the operation. |
KARS10222-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] Review the compute port settings in the configuration file used for adding storage nodes. |
KARS10223-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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10224-E |
An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] Storage node addition did not succeed (DNS server communication error) [Category] StorageNode [Solution] Verify the network status with the DNS server. If an error occurred, resolve the failure. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. |
KARS10225-E |
An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx) [Event Name] Storage node addition did not succeed (NTP server communication error) [Category] StorageNode [Solution] Verify the network status with the NTP server. If an error occurred, resolve the failure. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. |
KARS10226-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 the network status with the NTP server. If an error occurred, resolve the failure. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. If a VM of the storage node to be added is created, remove the VM, and then retry the operation. |
KARS10227-E |
Adding multiple storage nodes at the same time is not allowed because the configuration consists of a single fault domain. (Job ID = xxx) [Event Name] Storage node addition pre-check (Addition of multiple nodes in a single fault domain configuration) [Category] StorageNode [Solution] In a single fault domain configuration, add one storage node at a time. |
KARS10228-E |
The number of storage nodes to be added does not match the number of storage nodes that can be added in multiple fault domain configuration. (Job ID = xxx) [Event Name] Storage node addition pre-check (Number of additional storage nodes mismatch) [Category] StorageNode [Solution] Review the number of storage nodes to be added, and then retry the operation. |
KARS10229-E |
Add one initiator node at a time. (Job ID = xxx) [Event Name] Storage node addition pre-check (Addition of multiple storage nodes including initiator nodes) [Category] StorageNode [Solution] Review the configuration of storage nodes to be added, and then retry the operation. |
KARS10230-E |
The storage node cannot be added because doing so would result in mismatching numbers of storage nodes between fault domains. (Job ID = xxx) [Event Name] Storage node addition pre-check (Number of additional storage nodes mismatch) [Category] StorageNode [Solution] Review the number of storage nodes to be added for each fault domain, and then retry the operation. |
KARS10231-E |
The storage node cannot be added because doing so would result in mismatching numbers of initiator nodes between fault domains. (Job ID = xxx) [Event Name] Storage node addition pre-check (Invalid number of initiator nodes between fault domains) [Category] StorageNode [Solution] Add an initiator node to the fault domain with fewer initiator nodes. |
KARS10232-E |
The name of the fault domain specified for the added storage node does not exist in the storage cluster. (Job ID = xxx) [Event Name] Storage node addition pre-check (Fault domain name of additional storage node invalid) [Category] StorageNode [Solution] Review the fault domain name of the storage node to be added, and then retry the operation. |
KARS10233-E |
The initiator node cannot be added because the storage cluster does not support a resource-saving-version initiator node. (Job ID = xxx) [Event Name] Unsupported version (Resource-saving-version initiator node) [Category] StorageCluster [Solution] Match the version of all the storage nodes in the storage cluster, and then retry the operation. |
KARS10234-E |
The initiator node cannot be added because the storage cluster includes an initiator node that is not a resource-saving-version initiator node. (Job ID = xxx) [Event Name] Storage node addition pre-check (Removal of all the initiator nodes required) [Category] StorageNode [Solution] Remove all the existing initiator nodes in the storage cluster, and then retry the operation. |
KARS10235-E |
Storage nodes cannot be added because their drive connection method to VM of user data drive does not match that of the storage cluster. (Job ID = xxx) [Event Name] Storage node addition pre-check (Drive connection method to VM of user data drive mismatch) [Category] StorageNode [Solution] Match the user data drive setting of the storage node to be added to that of the storage cluster, and then retry the operation. |
KARS10236-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. |
KARS10237-E |
An error occurred in the communication with the storage node to be added. (Job ID = xxx, IP address = xxx) [Event Name] Storage node addition did not succeed (Communication with storage node error) [Category] StorageNode [Solution] Verify that the storage node to be added is powered on and that connection to the storage node to be added is possible. Also, verify that the network setting (described in the VSSB configuration file) of the storage node to be added and the network setting set in the storage node to be added match. If they do not match, set up each storage node according to the network setting (described in the VSSB configuration file) of the storage node to be added. Then, retry the storage node addition. |
KARS10238-E |
Connection to the storage node to be added did not succeed due to a user authentication error. (Job ID = xxx, IP address = xxx) [Event Name] Storage node addition did not succeed (User authentication error) [Category] StorageNode [Solution] Verify that the information (described in the VSSB configuration file) of the storage node to be added and the entered user password of a setup user are correct. Also, verify that setup of each storage node was correctly performed according to the procedure for storage node addition. Then, retry the storage node addition. |
KARS10239-E |
An error occurred during version checking of the VSSB configuration file. (Job ID = xxx, Version of the VSSB configuration file = xxx, Version of storage cluster = xxx) [Event Name] Storage node addition pre-check (Version of the configuration file mismatch) [Category] StorageNode [Solution] Export the configuration file to obtain the VSSB configuration file whose version matches the version of the current storage cluster software. Add the information of the storage node to be added to the obtained VSSB configuration file, and then retry the storage node addition. |
KARS10240-E |
The VSSB configuration file could not be uploaded. (Job ID = xxx) [Event Name] Storage node addition did not succeed (Configuration file not found) [Category] StorageNode [Solution] Retry the storage node addition with the VSSB configuration file specified. |
KARS10241-E |
The VSSB configuration file could not be uploaded. (Job ID = xxx) [Event Name] Storage node addition did not succeed (Uploading a configuration file did not succeed) [Category] StorageNode [Solution] Retry the storage node addition. Perform another storage node addition after the current storage node addition completes. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10242-E |
Existing storage nodes described in the VSSB configuration file are different from the current configuration. (Job ID = xxx) [Event Name] Storage node addition pre-check (Description of the file is different from the configuration) [Category] StorageNode [Solution] Export the configuration file to obtain the latest VSSB configuration file. Add the information of the storage node to be added to the obtained VSSB configuration file, and then retry the storage node addition. |
KARS10243-E |
The host name of the storage node to be added (described in the VSSB configuration file) is already used in the existing storage node. (Job ID = xxx, Storage node = xxx) [Event Name] Storage node addition pre-check (The specified host name is already in use) [Category] StorageNode [Solution] Change the host name of the storage node to be added (described in the VSSB configuration file) to other than the one that is used in the existing storage node. If you also need to change the name of the storage nodes set during setup of each storage node, set up each storage node according to the changed storage node host names. Then, retry the storage node addition. |
KARS10244-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] Check the maximum number of supported storage nodes and the number of storage nodes to be added, and then retry the operation. |
KARS10245-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] Use the storage software installer of the same version as that of the current storage cluster software. Retry the operation from installing the storage software according to the storage node addition procedure. |
KARS10246-E |
The configuration files could not be read. (Job ID = xxx, Detailed information = xxx) [Event Name] The configuration file could not be read [Category] StorageNode [Solution] Retry the storage node addition with the VSSB configuration file specified. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10247-E |
The configuration files could not be read. (Job ID = xxx, Detailed information = xxx) [Event Name] The configuration file could not be read [Category] StorageNode [Solution] Correct the configuration file according to detailed information, and then retry the operation. |
KARS10248-E |
The configuration files could not be read. (Job ID = xxx, Detailed information = xxx) [Event Name] The configuration file could not be read [Category] StorageNode [Solution] Export the configuration file to obtain the latest VSSB configuration file. Add the information of the storage node to be added to the obtained VSSB configuration file, and then retry the storage node addition. |
KARS10249-E |
The configuration files could not be read. (Job ID = xxx, Detailed information = xxx) [Event Name] The configuration file could not be read [Category] StorageNode [Solution] Export the configuration file to obtain the VSSB configuration file whose version matches the version of the current storage cluster software. Add the information of the storage node to be added to the obtained VSSB configuration file, and then retry the storage node addition. |
KARS10250-E |
Addition of the storage node ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the same job ID as this job, and then resolve the failure according to the recovery procedure. Then, retry adding the storage node. However, if the status of the storage node to be added after failure recovery is normal, storage node addition does not need to be performed again. |
KARS10260-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] Retry the storage node addition. However, if there is an event log (with the same job ID as this job) that instructs the installation of the storage software, you need to retry the operation from installing the storage software in the storage node addition procedure for the storage node for which an action to be taken is indicated. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10261-E |
An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] Storage node addition did not succeed (DNS server communication error) [Category] StorageNode [Solution] Verify the network status with the DNS server. If an error occurred, resolve the failure. Then, retry adding the storage node. However, if there is an event log (with the same job ID as this job) that instructs the installation of the storage software, you need to retry the operation from installing the storage software in the storage node addition procedure for the storage node for which an action to be taken is indicated. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10262-E |
An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx) [Event Name] Storage node addition did not succeed (NTP server communication error) [Category] StorageNode [Solution] Verify the network status with the NTP server. If an error occurred, resolve the failure. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Then, retry adding the storage node. However, if there is an event log (with the same job ID as this job) that instructs the installation of the storage software, you need to retry the operation from installing the storage software in the storage node addition procedure for the storage node for which an action to be taken is indicated. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10263-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 the network status with the NTP server. If an error occurred, resolve the failure. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Then, retry adding the storage node. However, if there is an event log (with the same job ID as this job) that instructs the installation of the storage software, you need to retry the operation from installing the storage software in the storage node addition procedure for the storage node for which an action to be taken is indicated. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10264-E |
The host name specified in the VSSB configuration file and the host name set in the storage node to be added do not match. (Job ID = xxx, Host name specified in the VSSB configuration file = xxx, Host name set in the storage node = xxx) [Event Name] Storage node addition did not succeed (Host name mismatch) [Category] StorageNode [Solution] Set up each storage node according to the host name of the storage node to be added described in the VSSB configuration file. Then, retry the storage node addition. |
KARS10265-E |
The network setting (specified in the VSSB configuration file) of the control port and the network setting (set in the storage node to be added) of the control port do not match. (Job ID = xxx, Storage node = xxx, Mismatched settings = xxx) [Event Name] Storage node addition did not succeed (Network setting mismatch) [Category] StorageNode [Solution] Set up each storage node according to the network setting of the control port of the storage node to be added described in the VSSB configuration file. Then, retry the storage node addition. |
KARS10266-E |
The routing setting (specified in the VSSB configuration file) of the control port and the routing setting (set in the storage node to be added) of the control port do not match. (Job ID = xxx, Storage node = xxx) [Event Name] Storage node addition did not succeed (Routing setting mismatch) [Category] StorageNode [Solution] Set up each storage node according to the routing setting of the control port of the storage node to be added described in the VSSB configuration file. Then, retry the storage node addition. |
KARS10267-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. |
KARS10268-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. If this error occurs, you need to install the storage software for the storage node subject to maintenance again. Retry the operation from installing the storage software in the storage node addition procedure. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10269-E |
An error occurred in the communication with the storage node to be added. (Job ID = xxx, IP address = xxx) [Event Name] Storage node addition did not succeed (Communication with storage node 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 AWS, troubleshoot any problem, and then retry the operation. If the VM of the storage node to be added is created, remove the VM before performing the operation. Then, retry the operation that was being performed. |
KARS10270-E |
An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] Storage node addition did not succeed (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 AWS, and then troubleshoot any problem. If the VM of the storage node to be added is created, remove the VM before performing the operation. Then, retry the operation that was being performed. |
KARS10271-E |
An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx) [Event Name] Storage node addition did not succeed (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 AWS, and then troubleshoot any problem. If the VM of the storage node to be added is created, remove the VM before performing the operation. Then, retry the operation that was being performed. |
KARS10272-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 AWS, and then troubleshoot any problem. If the VM of the storage node to be added is created, remove the VM before performing the operation. Then, retry the operation that was being performed. |
KARS10275-E |
The number of storage nodes to be added does not match the number of storage nodes that can be added for the user data protection type (RedundantType) 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, and then retry the operation. |
KARS10276-E |
The spread placement group specified in the storage nodes to be added do not match. (Job ID = xxx) [Event Name] Storage node addition pre-check (Spread placement group of additional storage nodes mismatch) [Category] StorageNode [Solution] Add storage nodes so that the spread placement group for all the storage nodes to be added are the same. |
KARS10277-E |
For storage nodes to be added, specify spread placement group to which no existing storage nodes belong. (Job ID = xxx) [Event Name] Storage node addition pre-check (Spread placement group of additional storage nodes registered) [Category] StorageNode [Solution] Add the target storage nodes so that they are not included in the existing spread placement group. |
KARS10278-E |
Spread placement group has been registered in the initiator node to be added. (Job ID = xxx) [Event Name] Storage node addition pre-check (Spread placement group setting is made for the initiator node) [Category] StorageNode [Solution] Add the target initiator node so that they do not belong to a spread placement group. |
KARS10280-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 AWS, 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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10281-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 there are no such event logs, verify the power status of each storage node, network status, and other factors. After that, verify whether there are storage nodes that need to be removed, and then remove them. If this error occurs, you need to install the storage software for the storage node subject to maintenance again. Retry the operation from installing the storage software in the storage node addition procedure. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10282-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 there are no such event logs, verify the power status of each storage node, network status, and other factors. 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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10283-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 AWS, 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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10284-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 AWS, and then troubleshoot any problem. After that, if the VM of the storage node to be added is created, remove the VM, and then retry the operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10285-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. 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 AWS, and then troubleshoot any problem. After that, if the VM of the storage node to be added is created, remove the VM, and then retry the operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10286-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 AWS, 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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10287-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 AWS, 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. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10288-E |
The processing for this storage node was ended abnormally due to a failure in another storage node. (Operation = xxx, Job ID = xxx, Storage node = xxx) [Event Name] Storage node addition did not succeed (Failure in another storage node) [Category] StorageNode [Solution] If there is an event log with the same job ID as this job, or that indicates a failure that is not related to this job, correct the failure according to the recovery procedure described in the event log. If this error occurs, you need to install the storage software for the storage node subject to maintenance indicated in the message again. Retry the operation from installing the storage software in the storage node addition procedure for the storage node indicated in the message. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10289-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] Export the configuration file to obtain the latest VSSB configuration file. Add the information of the storage node to be added to the obtained VSSB configuration file, and then retry the storage node addition. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10290-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 |
KARS10291-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 |
KARS10292-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 |
KARS10293-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 |
KARS10294-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 |
KARS10295-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 |
KARS10296-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 |
KARS10297-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 |
KARS10298-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 |
KARS10299-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 |
KARS10300-E |
The specified storage node could not be found. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Input parameter error) [Category] StorageNode [Solution] Verify that the correct storage node is specified, and then retry storage node removal. |
KARS10301-E |
The specified storage node is not in a state available for removal. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Specified storage node cannot be removed) [Category] StorageNode [Solution] If the status of the storage node is "starting" or the storage node is under maintenance, try again after processing for the target storage node has been finished. |
KARS10302-E |
The specified storage node cannot be removed normally because it is already blocked. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Specified storage node blocked) [Category] StorageNode [Solution] Remove the storage node normally after restoring the target storage node to normal. |
KARS10303-E |
The processing cannot be performed because there is a storage node that has not been removed yet. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Storage node yet to be removed) [Category] StorageNode [Solution] Complete the storage node removal, and then retry the operation. |
KARS10304-E |
The number of storage nodes not including the initiator node after removal went below the lower limit in the system requirements. (Job ID = xxx) [Event Name] Storage node removal pre-check (Insufficient number of storage nodes) [Category] StorageNode [Solution] To remove the storage node, add another storage node and remove the storage node again. |
KARS10305-E |
The specified storage node cannot be removed because it is the cluster master node. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Cluster master node cannot be removed) [Category] StorageNode [Solution] Try again by specifying a cluster worker node. |
KARS10308-E |
The drive connected to the storage node is not redundant. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal pre-check (Drive not redundant) [Category] StorageNode [Solution] Try again after rebuilding the drive connected to the storage node and making it redundant. |
KARS10310-E |
The processing cannot be performed because the specified storage node contains a volume which is being operated or is in an abnormal state. (Job ID = xxx, Volume ID = xxx) [Event Name] Storage node removal pre-check (Volume in abnormal state) [Category] StorageNode [Solution] If the target volume is being operated, wait until the operation is completed, and then retry the operation. If an error occurred in the target volume, take action according to the event log indicating the failure, and then retry the operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10311-E |
You cannot perform the processing because the specified storage node contains a snapshot volume. (Job ID = xxx, Volume ID = xxx) [Event Name] Storage node removal pre-check (Snapshot volume exists) [Category] StorageNode [Solution] Try again after deleting the snapshot volume. |
KARS10312-E |
You cannot perform the processing because the specified storage node contains a volume to be migrated by another volume. (Job ID = xxx, Volume ID = xxx) [Event Name] Storage node removal pre-check (Volume to be migrated exists) [Category] StorageNode [Solution] Try again after ongoing volume migration has been finished. |
KARS10314-E |
You cannot perform the processing because the specified storage node contains a volume which cannot be migrated. (Job ID = xxx, Volume ID = xxx) [Event Name] Storage node removal pre-check (Volume which cannot be migrated) [Category] StorageNode [Solution] Try again after placing the volume in the state available for migration. |
KARS10315-E |
The storage node cannot be removed because there is a configuration created for data migration from the external storage. (Job ID = xxx) [Event Name] Storage node removal pre-check (External storage exists) [Category] StorageNode [Solution] Try again after removing the configuration created for data migration from the external storage. |
KARS10316-I |
The storage node removal process is started (Step:1/3). (Job ID = xxx) [Event Name] Storage node removal is in progress (Step:1/3) [Category] StorageNode |
KARS10317-I |
Start removal of xxx storage controllers and relocation of xxx storage controllers to remove the storage node (Step:2/3). (Job ID = xxx) [Event Name] Storage node removal is in progress (Step:2/3) [Category] StorageNode |
KARS10318-I |
Removal of storage controller has started. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller removal has started [Category] StorageNode |
KARS10319-I |
Removal of storage controller has been completed. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller removal has been completed [Category] StorageNode |
KARS10320-I |
Start deletion of the storage node from the storage cluster (Step:3/3). (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node removal is in progress (Step:3/3) [Category] StorageNode |
KARS10322-I |
Relocation of storage controller has started. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller relocation has started [Category] StorageNode |
KARS10323-I |
Relocation of storage controller has been completed. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller relocation has been completed [Category] StorageNode |
KARS10325-E |
Drive data relocation to storage node could not be started. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation start error [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists after the retry, collect the logs, and then contact customer support. |
KARS10326-E |
Drive data relocation to the storage node failed. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation error [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists after the retry, collect the logs, and then contact customer support. |
KARS10327-E |
Drive data relocation to the storage node timed out. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation timeout [Category] StorageNode [Solution] No action is required if an event log indicating that the drive data relocation ended normally is output. If an event log indicating that the drive data relocation failed is output, take action referring to the event log. |
KARS10328-E |
Drive data relocation to the storage node could not be aborted. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation stop error [Category] StorageNode [Solution] No action is required if an event log indicating that the drive data relocation ended normally has been output. If an event log indicating that the drive data relocation failed is output, take action referring to the event log. |
KARS10329-E |
The target storage node cannot be removed unless prior storage node is removed first. (Job ID = xxx, Prior storage node ID = xxx, Target storage node ID = xxx) [Event Name] Storage node removal pre-check (Invalid order of removal) [Category] StorageNode [Solution] Remove the specified storage node first, and then remove the target storage node. |
KARS10330-I |
Creation of the storage controller has started. (Job ID = xxx) [Event Name] Storage controller creation has started [Category] StorageNode |
KARS10331-I |
Creation of storage controller has been completed. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller creation has been completed [Category] StorageNode |
KARS10333-W |
Storage controller could not be removed. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller removal did not succeed [Category] StorageNode [Solution] Check for event logs indicating a failure, and then take action. |
KARS10334-W |
Storage controller could not be relocated. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller relocation did not succeed [Category] StorageNode [Solution] Check for event logs indicating a failure, and then take action. |
KARS10335-W |
The storage controller could not be created. (Job ID = xxx) [Event Name] Storage controller creation did not succeed [Category] StorageNode [Solution] Check for event logs indicating a failure, and then take action. |
KARS10336-E |
In a multiple fault domain configuration, a node other than an initiator node cannot be removed. (Job ID = xxx, Specified storage node ID = xxx) [Event Name] Storage node removal pre-check (Removal condition mismatch in multiple fault domain configuration) [Category] StorageNode [Solution] Review the conditions for removing a storage node in a multiple fault domain configuration. |
KARS10337-E |
The storage node cannot be removed because doing so would result in a difference of at least two in the number of initiator nodes between fault domains. (Job ID = xxx, Specified storage node ID = xxx) [Event Name] Storage node removal pre-check (Invalid number of initiator nodes between fault domains) [Category] StorageNode [Solution] Specify an initiator node in the fault domain with more initiator nodes and remove it. |
KARS10338-E |
The storage node could not be removed because the storage controllers could not be relocated. (Job ID = xxx, Specified storage node 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. Then, retry the storage node removal. |
KARS10339-E |
The specified storage node cannot be removed because it is not an initiator node nor a storage node in a status in which removal did not succeed. (Job ID = xxx, Specified storage node ID = xxx) [Event Name] Storage node removal pre-check (Target storage node cannot be removed) [Category] StorageNode [Solution] Specify an initiator node or a storage node in a status in which removal did not succeed for the storage node to be removed, and then perform removal. |
KARS10350-E |
Removing the storage node ended abnormally. [Cause] A failure occurred. [Solution] See the event log with the job ID of this job, and then resolve the failure according to the recovery procedure. After that, remove the storage node. |
KARS10351-I |
Storage node removal processing was aborted. [Cause] A request to abort storage node removal processing was detected. |
KARS10400-E |
The operation cannot be performed because the target storage node is not running. (Job ID = xxx, Storage node ID = xxx) [Event Name] Maintenance pre-check (Storage node not ready) [Category] StorageNode [Solution] If the storage node is under maintenance, try again after processing for the target storage node has been finished. If the storage node is blocked, try again after the storage node is placed in the "ready" state by storage node maintenance recovery. |
KARS10401-E |
The drive connected to the storage node is not redundant. (Job ID = xxx, Storage node ID = xxx, Drive ID = xxx) [Event Name] Maintenance pre-check (Drive not redundant) [Category] StorageNode [Solution] Rebuild and make it redundant, and then retry the operation. |
KARS10404-E |
Processing could not be performed because the cluster master node was not redundant. The cluster master node is blocked. (Job ID = xxx, Storage node ID of cluster master = xxx) [Event Name] Maintenance pre-check (Cluster master node not redundant) [Category] StorageNode [Solution] Restore the blocked cluster master node, and then retry the operation. |
KARS10405-E |
The compute node path is not redundant. (Job ID = xxx) [Event Name] Maintenance pre-check (Compute node path not redundant) [Category] StorageNode [Solution] Add the path information to the compute node to make it redundant, and then retry the operation. |
KARS10406-E |
The storage node could not be stopped normally. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node stop error [Category] StorageNode [Solution] Recover the target storage node, and then retry the software update. |
KARS10407-E |
The specified storage node could not be found. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node maintenance blocking pre-check (Input parameter error) [Category] StorageNode [Solution] Verify that the correct storage node is specified, and then retry storage node maintenance blocking. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10408-W |
The storage node could not be stopped normally. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node stop unsuccessful (Manual stop required) [Category] StorageNode [Solution] If a VM of the target storage node is not stopped, stop it manually. |
KARS10409-W |
The storage node could not be restarted. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node restart unsuccessful (Manual restart required) [Category] StorageNode [Solution] Restart the VM of the target storage node manually. |
KARS10411-E |
Processing cannot be continued because performing storage node maintenance blocking makes the storage cluster status exceed fault tolerance and renders the system unable to continue operation. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node maintenance blocking pre-check (Error exceeding storage cluster fault tolerance) [Category] StorageNode [Solution] Recover or replace the blocked storage node or drive to recover the blockage status, and then retry the maintenance operation. |
KARS10412-W |
The storage node could not be stopped normally. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node stop unsuccessful (Manual stop required) [Category] StorageNode [Solution] If the target storage node is not stopped, stop it manually. |
KARS10413-W |
The storage node could not be restarted. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node restart unsuccessful (Manual restart required) [Category] StorageNode [Solution] Restart the target storage node manually. |
KARS10450-E |
Storage node maintenance blocking ended abnormally. [Cause] A failure occurred. [Solution] See the event log with the job ID of this job, and then resolve the failure according to the recovery procedure. After that, perform the storage node for maintenance. |
KARS10451-E |
Storage node maintenance blocking ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the job ID of this job, and then resolve the failure according to the recovery procedure. Then, retry storage node replacement. |
KARS10500-E |
The storage node is not blocked. (Job ID = xxx, Storage node ID = xxx) [Event Name] Maintenance pre-check (Storage node not blocked) [Category] StorageNode [Solution] Verify that the specification of the storage node is correct. If the specification is correct, block the storage node, and then retry the operation. |
KARS10501-E |
The storage node cannot be recovered because it is being removed. (Job ID = xxx, Storage node ID = xxx) [Event Name] Maintenance pre-check (Storage node yet to be removed) [Category] StorageNode [Solution] Make sure that the correct storage node was specified. |
KARS10502-E |
Rebuilding the storage controller in the storage node failed. (Job ID = xxx, Storage node ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller rebuild did not succeed [Category] StorageNode |
KARS10503-E |
Rebuilding the drive connected to storage node could not be started. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive rebuild start did not succeed [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists after the retry, collect the logs, and then contact customer support. |
KARS10504-E |
Rebuilding the drive connected to the storage node failed. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive rebuild did not succeed [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If event logs indicating other errors are not output, retry updating. If the phenomenon persists after the retry, collect the logs, and then contact customer support. |
KARS10505-E |
Rebuilding the drive connected to the storage node has timed out. (Job ID = xxx, Storage node ID = xxx) [Event Name] Rebuilding drive timeout [Category] StorageNode [Solution] No action is required if an event log indicating that the drive has been rebuilt normally has been output. If an event log indicating that rebuilding the drive failed is output, take action referring to the event log. |
KARS10506-E |
The compute port connected to the storage node could not be unblocked. (Job ID = xxx, Storage node ID = xxx) [Event Name] Compute port blockade restoration did not succeed [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists after the retry, collect the logs, and then contact customer support. |
KARS10507-E |
Rebuilding the drive connected to the storage node could not be aborted. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive rebuild stop did not succeed [Category] StorageNode [Solution] No action is required if an event log indicating that the drive has been rebuilt normally has been output. If an event log indicating that rebuilding the drive failed is output, take action referring to the event log. |
KARS10508-E |
The specified storage node could not be found. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery pre-check (Input parameter error) [Category] StorageNode [Solution] Verify whether the specified storage node is correct, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10509-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 that the internode network is correctly connected to the storage node to be recovered and the storage node is powered on. Then, restart the storage node to be recovered, and then retry the operation. |
KARS10510-E |
The software version of the storage node to be recovered does not match that of the storage node at the time it was blocked. Therefore, the storage node cannot be recovered. (Job ID = xxx, Version of the storage node to be restored = xxx, Version at the time of blockage = xxx) [Event Name] Storage node recovery pre-check (Software version mismatch) [Category] StorageNode [Solution] Match the software version of the target storage node to be recovered to that of the storage node at the time it was blocked, and then replace the storage node for recovery. |
KARS10511-E |
Storage node replacement is required to recover the specified storage node. (Job ID = xxx) [Event Name] Storage node recovery pre-check (Storage node replacement necessary) [Category] StorageNode [Solution] Recover the storage node according to the procedure for storage node replacement. |
KARS10512-E |
The number of compute ports connected to the storage node to be recovered and protocol do not match those of the storage node at the time it was blocked. Therefore, the storage node cannot be recovered. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery pre-check (Number of compute ports mismatch) [Category] StorageNode [Solution] Review the configuration of the compute ports connected to the storage node to be recovered. Retry the operation after matching the number and protocol of compute ports with the configuration at the time when the storage node was blocked. |
KARS10513-E |
The recovery-target storage node cannot be recovered because the configuration of the compute ports connected to the storage node was changed. (Job ID = xxx, Storage node ID = xxx, Compute port ID = xxx) [Event Name] Storage node recovery pre-check (Configuration of compute ports mismatch) [Category] StorageNode [Solution] Review the configuration of the compute ports connected to the storage node to be recovered. Retry the operation after matching the number of compute ports with the configuration at the time when the storage node was blocked. |
KARS10514-E |
The recovery-target storage node cannot be recovered because the configuration of the internode ports connected to the storage node was changed. (Job ID = xxx, Storage node ID = xxx, Internode port ID = xxx) [Event Name] Storage node recovery pre-check (Configuration of internode port mismatch) [Category] StorageNode [Solution] Review the configuration of the internode ports connected to the storage node to be recovered. Retry the operation after matching the number of internode ports with the configuration at the time when the storage node was blocked. |
KARS10515-E |
The recovery-target storage node cannot be recovered because the configuration of the control ports connected to the storage node was changed. (Job ID = xxx, Storage node ID = xxx, Control port ID = xxx) [Event Name] Storage node recovery pre-check (Configuration of control port mismatch) [Category] StorageNode [Solution] Review the configuration of the control ports connected to the storage node to be recovered. Retry the operation after matching the number of control ports with the configuration at the time when the storage node was blocked. |
KARS10516-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 (Storage node recovery) [Category] StorageNode |
KARS10517-E |
An error occurred in the DNS settings. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] The storage node could not be recovered (DNS setting unsuccessful) [Category] StorageNode [Solution] Wait for a while, and then replace the storage node. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10518-E |
An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] The storage node could not be recovered (DNS server communication error) [Category] StorageNode [Solution] Verify the status of the network with the DNS server, and then resolve any failures. Then, replace the storage node. |
KARS10519-E |
An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx) [Event Name] The storage node could not be recovered (NTP server communication error) [Category] StorageNode [Solution] Verify the status of the network with the NTP server, and then resolve any failures. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Then, replace the storage node. |
KARS10520-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 the status of the network with the NTP server, and then resolve any failures. When the NTP server to which the storage node is connected has been specified with a host name (FQDN), verify that the DNS record for resolution of the NTP server host name (FQDN) is correctly set on the DNS server. Also, verify whether the NTP server is normally running and the procedure for setting the NTP server is correct, and then resolve any problems. Then, replace the storage node. |
KARS10521-E |
The target storage node cannot be recovered because it contains a storage controller that is in an unrecoverable state. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery pre-check (Storage controller status error detection) [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS10522-E |
Recover the other storage nodes first, and then recover the target storage node. (Job ID = xxx, Specified storage node ID = xxx, High-priority storage node ID = xxx) [Event Name] Storage node recovery pre-check (Recovery order error detection) [Category] StorageNode [Solution] Recover the storage node indicated in the message, and then recover the target storage node. |
KARS10523-E |
The number of FC ports connected (as compute ports) to the storage node to be recovered does not match that at the time it was blocked. Therefore, the storage node cannot be recovered. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery pre-check (Number of FC ports connected as compute ports mismatch) [Category] StorageNode [Solution] Review the configuration of the compute ports connected to the storage node to be recovered. Retry the operation after matching the number of compute ports with the configuration at the time when the storage node was blocked. |
KARS10524-E |
The operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] The storage node could not be recovered (Storage cluster master node (primary) failover) [Category] StorageNode |
KARS10525-W |
Storage node auto-recovery could not be performed due to conflict with another operation. (Job ID = xxx) [Event Name] Storage node auto-recovery conflicts with another operation [Category] StorageNode [Solution] If the storage node status meets the conditions for auto recovery, auto recovery continues to be performed and no further action is required. |
KARS10526-E |
The storage node is in persistent blockade status. (Job ID = xxx, Storage node ID = xxx) [Event Name] The storage node is in persistent blockade status [Category] StorageNode [Solution] See the event logs with the job ID of this job or event logs that indicate failures other than the target of this job, if any, and then take action. Then, perform manually maintenance recovery or replacement of the storage node. |
KARS10527-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 error) [Category] StorageNode [Solution] Verify that the internode network is correctly connected to the storage node to be recovered and the storage node is powered on, and then restart the storage node. Then, recover the storage node. If the storage node status meets the conditions for storage node auto-recovery, no action is required because auto recovery is to be performed. |
KARS10529-E |
The drive connection method to the VM from the user data drive of the storage cluster differs from the drive connection method to the VM from the user data drive of the storage node. Therefore, the storage node cannot be recovered. (Job ID = xxx) [Event Name] Storage node recovery pre-check (Drive connection method to VM from user data drive mismatch) [Category] StorageNode [Solution] Match the user data drive setting of the storage node to be recovered to that of the storage cluster, and then retry the operation. |
KARS10530-E |
An error occurred in the communication with the storage node to be recovered. (Job ID = xxx, IP address = xxx) [Event Name] Storage node recovery pre-check (Communication error) [Category] StorageNode [Solution] Verify that the storage nodes to be recovered are powered on and that connection to the storage nodes to be recovered is possible. Also, verify that the network setting (registered in the storage cluster) of the storage nodes to be recovered and the network setting set in the storage node to be recovered match. If they do not match, set up each storage node according to the network setting (registered in the storage cluster) of the storage node to be recovered. Then, replace the storage node to be recovered. If the storage node status meets the conditions for the storage node auto-recovery function, recovery is automatically performed and no further action is required. |
KARS10531-E |
The software version of the storage node to be recovered does not match that of the storage node at the time it was blocked. Therefore, the storage node cannot be recovered. (Job ID = xxx, Version of the storage node to be recovered = xxx, Version at the time of blockage = xxx) [Event Name] Storage node recovery pre-check (Software version mismatch) [Category] StorageNode [Solution] Use the storage software installer of the version at the time the recovery-target storage node was blocked. Perform recovery from installing the storage software according to the procedure for storage node replacement. |
KARS10532-E |
The recovery-target storage node cannot be recovered because the configuration of the control ports connected to the storage node was changed. (Job ID = xxx, Storage node ID = xxx, Control port ID = xxx) [Event Name] Storage node recovery pre-check (Configuration of control port mismatch detected) [Category] StorageNode [Solution] Review the configuration of the control ports connected to the storage node to be recovered. Match the configuration of control ports with the configuration at the time the storage node was blocked, and then retry the operation. To change the control port settings of the storage node to be recovered, set up each storage node. |
KARS10533-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 (Storage node recovery) [Category] StorageNode |
KARS10534-E |
Rebuilding the storage controller in the storage node failed. (Job ID = xxx, Storage node ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller rebuild did not succeed [Category] StorageNode |
KARS10535-E |
To recover the specified storage node, you need to perform recovery by storage node maintenance recovery. (Job ID = xxx) [Event Name] Storage node recovery pre-check (Storage node maintenance recovery necessary) [Category] StorageNode [Solution] Perform storage node recovery according to the procedure for storage node maintenance recovery. |
KARS10536-E |
Connection to the storage node to be recovered did not succeed due to a user authentication error. (Job ID = xxx, Storage node ID = xxx, IP address = xxx) [Event Name] The storage node could not be recovered (User authentication error) [Category] StorageNode [Solution] If a storage node to be recovered is specified, verify that the correct storage node is specified. Also, verify that the password for the setup user is correct and setup of each storage node was correctly performed. Then, replace the storage node to be recovered. If the storage node status meets the conditions for the storage node auto-recovery function, recovery is automatically performed and no further action is required. |
KARS10537-E |
To recover the specified storage node, you need to reinstall the storage software of the specified storage node. (Job ID = xxx) [Event Name] Storage node recovery pre-check (Reinstallation of storage software necessary) [Category] StorageNode [Solution] Perform storage node recovery from installing the storage software according to the procedure for storage node replacement. |
KARS10538-E |
Rebuilding the drive connected to storage node could not be started. (Job ID = xxx, Storage node ID = xxx) [Event Name] Drive rebuild start did not succeed [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. Then, if the storage node to be recovered is blocked, recover the target storage node by performing storage node maintenance recovery. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10539-E |
The compute port connected to the storage node could not be unblocked. (Job ID = xxx, Storage node ID = xxx) [Event Name] Compute port blockade restoration did not succeed [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. Then, if the storage node to be recovered is blocked, recover the target storage node by performing storage node maintenance recovery. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10540-E |
The spread placement group setting of the storage node to be recovered does not match that of the storage node at the time it was blocked. Therefore, the storage node cannot be recovered. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery pre-check (Spread placement group ID mismatch) [Category] StorageNode [Solution] Review the spread placement group setting of the storage node to be recovered. Match the spread placement group setting to that at the time the storage node was blocked, and then perform storage node replacement. |
KARS10544-E |
The recovery-target storage node name (registered in the storage cluster) and the host name (set in the recovery-target storage node) do not match. (Job ID = xxx, Storage node name registered in the storage cluster = xxx, Host name set in the storage node = xxx) [Event Name] The storage node could not be recovered (Host name mismatch) [Category] StorageNode [Solution] Set up each storage node according to the storage node name (registered in the storage cluster) of the storage node to be recovered. Then, replace the storage node. |
KARS10545-E |
The network setting (registered in the storage cluster) of the control port of the storage node to be recovered and the network setting (set in the storage node to be recovered) of the control port do not match. (Job ID = xxx, Storage node = xxx, Mismatched settings = xxx) [Event Name] The storage node could not be recovered (Network setting mismatch) [Category] StorageNode [Solution] Set up each storage node according to the network setting (registered in the storage cluster) of the control port of the storage node to be recovered. Then, replace the storage node. |
KARS10546-E |
The routing setting (registered in the storage cluster) of the control port of the storage node to be recovered and the routing setting (set in the storage node to be recovered) of the control port do not match. (Job ID = xxx, Storage node = xxx) [Event Name] The storage node could not be recovered (Routing setting mismatch) [Category] StorageNode [Solution] Set up each storage node according to the routing setting (registered in the storage cluster) of the control port of the storage node to be recovered. Then, replace the storage node. |
KARS10547-E |
Rebuilding the storage controller in the storage node failed. (Job ID = xxx, Storage node ID = xxx, Storage controller ID = xxx) [Event Name] Storage controller rebuild did not succeed [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 AWS, and then troubleshoot any problem. If the phenomenon persists after retry, collect the logs, and then contact customer support. |
KARS10548-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 AWS, and then troubleshoot any problem. Then, restart the storage node to be recovered, and then retry the operation. |
KARS10549-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 (Storage node recovery) [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 AWS, and then troubleshoot any problem. Then, retry recovery of the storage node to be recovered. If the phenomenon persists, perform recovery by storage node replacement. |
KARS10550-E |
Storage node recovery processing ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the job ID of this job, and then resolve the failure according to the recovery procedure. Then, if the storage node to be recovered is blocked, retry the operation to recover the target storage node. |
KARS10551-E |
Storage node recovery processing ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the job ID of this job or event logs that indicate failures other than the target of this job, if any, and then take action. Then, if the storage node to be recovered is blocked, recover the storage node. If the storage node status meets the conditions for storage node auto-recovery, no action is required because auto recovery is to be performed. |
KARS10560-E |
The recovery ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage 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. Then, if the storage node to be recovered is blocked, replace the storage node. If the storage node status meets the conditions for the storage node auto-recovery function, recovery is automatically performed and no further action is required. |
KARS10561-E |
The operation cannot be performed because the storage cluster status is not "Ready". (Operation = xxx, 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 replace the storage node. If the storage node status meets the conditions for the storage node auto-recovery function, recovery is automatically performed and no further action is required. |
KARS10562-E |
Processing will be stopped abnormally due to another processing in progress for the storage node subject to maintenance. (Operation = xxx, Job ID = xxx) [Event Name] Concurrent operation prohibited [Category] StorageNode [Solution] Verify that the applicable storage node is not being used for another operation. If setup of each storage node is in progress, allow it to complete. Then, replace the storage node. If the phenomenon persists, restart the storage node, and then replace it. |
KARS10563-E |
Processing will be stopped abnormally due to disconnection with the storage node subject to maintenance. (Operation = xxx, Job ID = xxx, IP address = xxx) [Event Name] Connection with the storage nodes subject to maintenance has been lost [Category] StorageNode [Solution] Verify that the storage node subject to maintenance is powered on and that connection with the target storage node is possible via the control network. Then, replace the storage node. |
KARS10564-E |
Processing will be stopped abnormally due to disconnection with the storage node subject to maintenance. (Operation = xxx, Job ID = xxx) [Event Name] Connection with the storage nodes subject to maintenance has been lost [Category] StorageNode [Solution] Verify that the storage node subject to maintenance is powered on and that it can be connected to the control network. Then, replace the storage node. |
KARS10565-E |
The network of the compute port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx, MAC address of the device for which a duplicated IP address is set = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address with the component indicated by the MAC address displayed in the message, and then replace the storage node. |
KARS10566-E |
An NIC is not installed in a defined slot of the physical server. (Job ID = xxx, Storage node = xxx, PCI address for which information acquisition was unsuccessful = xxx) [Event Name] Obtaining information from the physical server failed [Category] StorageNode [Solution] Verify whether the defined NIC is installed in the slot with the PCI address displayed in the message. Install the defined NIC in the slot, and then replace the storage node. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10567-E |
Connection from the storage node subject to maintenance to the control network of all the storage nodes could not be verified. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Network connection verification failed [Category] StorageNode [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, and switch settings), and then make the network status such that communication is possible. Then, replace the storage node. |
KARS10568-E |
Connection from the storage node subject to maintenance to the internode network of all the storage nodes could not be verified. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Network connection verification failed [Category] StorageNode [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, and switch settings), and then make the network status such that communication is possible. Then, replace the storage node. |
KARS10569-E |
The operation cannot be continued because the memory capacity of the storage node subject to maintenance is less than the minimum memory capacity of the protection domain (xxx MiB). (Job ID = xxx, Storage node = xxx) [Event Name] Maintenance pre-check (Less than the minimum memory capacity) [Category] StorageNode [Solution] Expand the memory capacity of the storage node subject to maintenance to more than the minimum memory capacity of the protection domain, and then replace the storage node. |
KARS10570-W |
Storage node recovery using a spare node is completed. Configuration backup is required. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node recovery using a spare node completed [Category] StorageNode |
KARS10571-E |
Expanding the storage pool for the drives connected to the applicable storage node did not succeed. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage pool expansion failed [Category] StorageNode [Solution] Recover any blocked storage nodes in the storage cluster. Expand the storage pool for the drives connected to the applicable storage node according to the manual. If the status of the storage node is "Ready", you do not need to recover the storage node. |
KARS10572-E |
Verification of whether expanding the storage pool for the drives connected to the applicable storage node is completed did not succeed. (Job ID = xxx, Storage node ID = xxx) [Event Name] Verification of completion of storage pool expansion failed [Category] StorageNode [Solution] Recover any blocked storage nodes in the storage cluster. If storage pool expansion is being performed while this job is running, verify the results. If storage pool expansion does not succeed or some of the drives connected to the applicable storage node are in Offline status because storage pool expansion has not been performed, perform storage pool expansion according to the manual. If the status of the storage node is "Ready", you do not need to recover the storage node. |
KARS10573-E |
Expanding of the storage pool for the drives connected to the applicable storage node ended abnormally. (Job ID = xxx, Storage node ID = xxx, Storage pool expansion job ID = xxx) [Event Name] Storage pool expansion ended abnormally [Category] StorageNode [Solution] Recover any blocked storage nodes in the storage cluster. Verify the results of the storage pool expansion job, and take action accordingly. If some of the drives connected to the applicable storage node are in Offline status, expand the storage pool according to the manual. If the status of the storage node is "Ready", you do not need to recover the storage node. |
KARS10574-E |
Auto recovery did not succeed. Because a spare node is registered, storage node recovery is automatically performed if the operating conditions for spare node switchover are satisfied. (Job ID = xxx, Storage node ID = xxx) [Event Name] Changing to a spare node switchover target due to a failure of auto recovery [Category] StorageNode [Solution] If the status of the applicable storage node is "TemporaryBlockage", wait until the status is changed. You do not have to act on an event log with the same job ID as this job. |
KARS10575-E |
The network for the internode port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx, MAC address of the device for which a duplicated IP address is set = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address with the component indicated by the MAC address displayed in the message, and then replace the storage node. |
KARS10576-E |
If the storage node auto-recovery function is enabled, manual storage node maintenance recovery and manual storage node replacement for the storage node whose status is "TemporaryBlockage" are not possible. (Operation = xxx, Job ID = xxx) [Event Name] Manual maintenance recovery and replacement not possible [Category] StorageNode [Solution] If the status of the applicable storage node is "TemporaryBlockage", wait until the status is changed. Storage node recovery is automatically performed if the operating conditions for storage node auto-recovery are satisfied. |
KARS10577-E |
An error occurred in communication with the DNS server. (Job ID = xxx, Storage node = xxx, DNS server = xxx) [Event Name] The storage node could not be recovered (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 AWS, and then troubleshoot any problem. Then, replace the storage node. |
KARS10578-E |
An error occurred in communication with the NTP server. (Job ID = xxx, Storage node = xxx, NTP server = xxx) [Event Name] The storage node could not be recovered (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 AWS, and then troubleshoot any problem. Then, replace the storage node. |
KARS10579-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 AWS, and then troubleshoot any problem. Then, replace the storage node. |
KARS10580-E |
The operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] The storage node could not be recovered (Storage cluster master node (primary) failover) [Category] StorageNode [Solution] Verify whether any event log was output to help identify the cause of the failure of the cluster master node (primary). If an event log was 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 AWS, and then troubleshoot any problem. Then, recover the target storage node. If the storage node status meets the conditions for Storage node auto-recovery, no action is required because auto recovery is to be performed. |
KARS10581-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 AWS, and then troubleshoot any problem. Then, restart the storage node. Then, recover the target storage node. If the storage node status meets the conditions for Storage node auto-recovery, no action is required because auto recovery is to be performed. |
KARS10582-E |
The network of the compute port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address indicated in the message, and then replace the storage node. |
KARS10590-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error [Category] StorageNode |
KARS10591-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error [Category] StorageNode |
KARS10597-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 AWS, 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 phenomenon persists, collect the logs, and then contact customer support. |
KARS10598-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error [Category] StorageNode |
KARS10599-E |
An internal error occurred during configuration of a storage node as a storage node to be recovered. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error [Category] StorageNode [Solution] |
KARS10601-W |
An error occurred in forwarding event logs to the syslog servers. [Event Name] Error in forwarding event logs to syslog servers [Category] Service [Solution] Check the network configuration and event log syslog forwarding settings. If the problem persists, collect logs, and then contact customer support. Note that, if an event log with Message ID KARS10602-I is output after this event log, you do not have to contact customer support because the problem has been resolved. |
KARS10602-I |
Forwarding event logs to the syslog servers has recovered. (Storage cluster = xxx) [Event Name] Recovery from error in forwarding event logs to syslog servers [Category] Service |
KARS10603-I |
E-mail Report setting is complete. (Job ID = xxx) [Event Name] E-mail Report setting is complete [Category] Service [Solution] We will send a test email. Verify that the email has arrived at the To email address. If no email has been sent, verify the E-mail Report setting and SMTP server side setting. |
KARS10604-W |
The request could not be executed. [Cause] Another E-mail Report setting is currently running. [Solution] Wait until the current E-mail Report setting is complete, and then retry the operation. |
KARS10605-W |
The request could not be executed. [Cause] Another SNMP setting is already running. [Solution] Wait until the current SNMP setting is complete, and then retry the operation. |
KARS10607-I |
SNMP setting is complete. (Job ID = xxx) [Event Name] SNMP setting complete [Category] Service [Solution] If Trap destination is set, verify that the Test Trap has been received. If it is not received, verify the setting. |
KARS10611-W |
An error occurred in forwarding audit logs to the syslog servers. [Event Name] Error in forwarding audit logs to syslog servers [Category] Service [Solution] Check the network configuration and audit log syslog forwarding settings. If the problem persists, collect logs, and then contact customer support. Note that, if an event log with Message ID KARS10612-I is generated after this event log, you do not have to contact customer support because the problem has been resolved. |
KARS10612-I |
Forwarding audit logs to the syslog servers has recovered. (Storage cluster = xxx) [Event Name] Recovery from error in forwarding audit logs to syslog servers [Category] Service |
KARS10613-W |
The number of unforwarded audit logs has exceeded the threshold (70%). (Storage cluster = xxx) [Event Name] Unforwarded audit log capacity threshold (70%) exceeded [Category] Service [Solution] Check the network configuration and audit log syslog forwarding settings. To avoid audit logs being lost as a result of the number of unforwarded ones reaching the upper limit, create and download an audit log file as necessary. |
KARS10614-W |
The number of unforwarded audit logs has reached the upper limit. (Storage cluster = xxx) [Event Name] Reaching the upper limit of the number of unforwarded audit logs [Category] Service [Solution] Check the network configuration and audit log syslog forwarding settings. To avoid audit logs being lost as a result of the number of unforwarded ones reaching the upper limit, create and download an audit log file as necessary. |
KARS10630-W |
An error occurred during audit log management processing. Any audit logs that are set to be transferred are not transferred until the error is solved. [Event Name] Audit log management processing error [Category] StorageCluster [Solution] If an event log (Message ID: KARS10631-I) is generated after this event log, the problem has been solved and no action is required. If an event log (Message ID: KARS10631-I) is not generated, and the storage cluster is restarted after this event log, also, if restarting the storage cluster does not cause this event log to be generated again after generation of this event log, the problem has been solved and no action is required. In cases other than those above, if an event log (Message ID: KARS10631-I) is not generated, collect the logs, and then contact customer support. |
KARS10631-I |
Audit log management processing restarted. [Event Name] Audit log management processing restarted [Category] StorageCluster |
KARS10632-W |
An error occurred during event log management processing. Any event logs that are set to be transferred are not transferred until the error is solved. [Event Name] Event log management processing error [Category] StorageCluster [Solution] If an event log (Message ID: KARS10633-I) is generated after this event log, the problem has been solved and no action is required. If an event log (Message ID: KARS10633-I) is not generated, and the storage cluster is restarted after this event log, also, if restarting the storage cluster does not cause this event log to be generated again after generation of this event log, the problem has been solved and no action is required. In cases other than those above, if an event log (Message ID: KARS10633-I) is not generated, collect the logs, and then contact customer support. |
KARS10633-I |
Event log management processing restarted. [Event Name] Event log management processing restarted [Category] StorageCluster |
KARS10640-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Wait a while, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10641-E |
The request could not be executed. [Cause] Either creating or downloading the audit log file is running. [Solution] Wait for the completion of creating or downloading the audit log file and retry the operation. |
KARS10642-W |
The request could not be executed. [Cause] A temporary error occurred. [Solution] Wait a while, and then retry the operation. If the error persists, collect the logs, and then contact customer support. |
KARS10650-W |
An error occurred in sending an email. (Detailed information = xxx) [Event Name] The email could not be sent [Category] Service [Solution] Verify the E-mail Report settings and SMTP server settings. |
KARS10651-W |
An error occurred in validating the SMTP server. [Event Name] Validation of the SMTP server was unsuccessful [Category] Service [Solution] Verify the root certificate of the SMTP server or the setting of the smtpServerName. |
KARS10652-W |
The root certificate of the SMTP server is not imported. [Event Name] The root certificate of the SMTP server is not imported [Category] Service [Solution] Import the root certificate of the SMTP server. |
KARS10653-I |
All problems in sending an email have been resolved. [Event Name] Email sending problem resolved [Category] Service [Solution] Verify whether an email was received. |
KARS10654-E |
An internal error occurred in SNMP Trap sending. [Event Name] SNMP Trap internal processing error [Category] Service [Solution] If the event log (KARS10656-I) is not displayed after a while, collect the logs, and then contact customer support. |
KARS10655-W |
The SNMP Trap could not be sent. [Event Name] SNMP Trap could not be sent [Category] Service [Solution] Verify the SNMP Trap settings. |
KARS10656-I |
All problems in sending an SNMP Trap have been resolved. [Event Name] SNMP Trap sending problem resolved [Category] Service [Solution] Verify that the SNMP Trap was received. |
KARS10660-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Contact customer support. |
KARS10661-I |
Dump log file creation is started. [Event Name] Dump log file creation started [Category] StorageNode |
KARS10662-I |
Dump log file creation succeeded. [Event Name] Dump log file creation successful [Category] StorageNode |
KARS10663-E |
Dump log file creation did not succeed. [Event Name] Dump log file creation unsuccessful [Category] StorageNode [Solution] Download the logs indicating the cause of the failure in creating a dump log file, and then contact customer support. |
KARS10664-E |
Dump log file creation did not succeed. [Event Name] Dump log file creation unsuccessful [Category] StorageNode [Solution] Create a dump log file again. If the phenomenon persists, download the logs indicating the cause of the failure in creating a dump log file, and then contact customer support. |
KARS10665-E |
The request could not be executed. [Cause] Failure information in the storage node is being generated. [Solution] Wait a while, and then retry the operation. |
KARS10666-E |
The request could not be executed. [Cause] Information (corresponding to the specified mode) to be collected does not exist. [Solution] Verify that the specified mode and request target storage node are correct. If they are correct, skip collecting the dump log files of the target storage node. If they are incorrect, specify the correct values, and then retry the request. |
KARS10667-E |
The request could not be executed. [Cause] A dump log file with the specified file name does not exist. [Solution] Obtain a list of the latest dump log files, and then specify the target file again. |
KARS10668-I |
Dump log file deletion succeeded. [Event Name] Dump log file deletion successful [Category] StorageNode |
KARS10700-E |
Spare node information could not be registered. The operation cannot be performed because the storage node auto-recovery function is disabled. (Job ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Enable the storage node auto-recovery function, and then retry the operation. |
KARS10701-E |
The operation cannot be performed because storage nodes with the status other than "Ready" exist in the storage cluster. (Operation = xxx, Job ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that all the storage nodes in the storage cluster are in the Ready status. If maintenance is being performed for storage nodes, complete the maintenance operation, and then retry the operation. If the storage nodes are blocked, recover the storage nodes, and then retry the operation. |
KARS10702-E |
The operation cannot be performed because the specified fault domain ID does not exist in the storage cluster. (Operation = xxx, Job ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the entered fault domain ID is correct. If the ID is incorrect, correct it, and then retry the operation. |
KARS10703-E |
The operation cannot be performed because only the defined number of spare nodes can be registered in a fault domain. (Operation = xxx, Job ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify the number of spare nodes registered in the fault domain. |
KARS10704-E |
Spare node information could not be edited. A spare node with the specified ID does not exist. (Job ID = xxx, Spare node ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the entered spare node ID is correct. If the ID is incorrect, correct it, and then retry the operation. |
KARS10705-E |
Spare node information could not be registered. An error occurred in the communication with the control port of the target spare node. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the target storage node is powered on and that there is no problem with connection paths. Verify that there is no problem with the specified control port IP address and network settings for the target spare node. To change the network settings for the target spare node, set up each storage node for the target spare node. Also, spare nodes that already belong to a storage cluster cannot be registered as a spare node. |
KARS10706-E |
Spare node information could not be edited. An error occurred in the control network with the spare node and the storage node. (Job ID = xxx, Spare node ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the target storage node is powered on and that there is no problem with connection paths. Verify that there is no problem with the specified control port IP address and network settings for the target spare node. To change the network settings for the target spare node, set up each storage node for the target spare node. |
KARS10707-E |
Spare node information could not be registered. Connection with the target spare node did not succeed due to an authentication error of a setup user. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the password of the entered setup user is correct. If the ID is incorrect, correct it, and then retry the operation. |
KARS10708-E |
Spare node information could not be edited. Connection with the target spare node did not succeed due to an authentication error of a setup user. (Job ID = xxx, Spare node ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the password of the entered setup user is correct. If the ID is incorrect, correct it, and then retry the operation. |
KARS10709-E |
Spare node information could not be registered. The software version of the storage cluster and the software version of the spare node do not match. (Job ID = xxx, Version of the spare node = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify the software version of the target spare node and storage cluster. If the versions do not match, re-install storage software of the same version as that of the storage cluster into a spare node. Then, retry the operation. |
KARS10710-E |
Spare node information could not be edited. The software version of the storage cluster and the software version of the spare node do not match. (Job ID = xxx, Version of the spare node = xxx, Spare node ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify the software version of the target spare node and storage cluster. If the versions do not match, re-install storage software of the same version as that of the storage cluster into a spare node. Then, retry the operation. |
KARS10711-E |
The operation cannot be performed because the subnets do not match between the control ports of the storage nodes in the specified fault domain. (Operation = xxx, Job ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify whether the subnets are the same between the control ports of the storage nodes in the specified fault domain. |
KARS10712-E |
Spare node information could not be registered. The subnet of the storage node of the target fault domain and the subnet of the control port of the spare node do not match. (Job ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Review the subnet of the control port of the spare node. |
KARS10713-E |
Spare node information could not be edited. The subnet of the storage node of the target fault domain and the subnet of the control port of the spare node do not match. (Job ID = xxx, Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Review the subnet of the control port of the spare node. |
KARS10714-E |
Spare node information could not be deleted. A spare node with the specified ID does not exist. (Job ID = xxx, Spare node ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the entered spare node ID is correct. |
KARS10715-E |
Spare node information could not be registered. The specified spare node has already been registered in the same storage cluster. (Job ID = xxx, Spare node IP address = xxx, Spare node ID of same bios uuid = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the entered spare node IP address is correct and that the applicable spare node is not being used for another operation. |
KARS10716-E |
Spare node information could not be registered. The specified spare node has already been registered in another storage cluster. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the entered spare node IP address is correct and that the applicable spare node has not been registered in another storage cluster. |
KARS10717-E |
Spare node information could not be registered because another operation might be in progress in the specified spare node. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode |
KARS10718-E |
The operation cannot be performed because the subnets do not match between the internode ports of the storage nodes in the specified fault domain. (Operation = xxx, Job ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify whether the subnets are the same between the internode ports of the storage nodes in the specified fault domain. |
KARS10719-E |
The operation cannot be performed because the subnets do not match between the compute ports of the storage nodes in the specified fault domain. (Operation = xxx, Job ID = xxx, Fault domain ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify whether the subnets are the same between the compute ports of the storage nodes in the specified fault domain. |
KARS10720-I |
All the spare nodes are in a state in which spare node switchover is possible. BMC connection information about all the storage nodes that belong to the same fault domain as the spare nodes is valid. [Event Name] Spare node operation monitoring is successful (All nodes) [Category] Service |
KARS10721-I |
All the spare nodes are in a state in which spare node switchover is possible. BMC connection information about all the storage nodes that belong to the same fault domain as the spare nodes is valid. However, confirmation of the storage nodes whose status is other than "Ready" was skipped. [Event Name] Spare node operation monitoring is successful (All nodes) [Category] Service [Solution] For the storage nodes whose status is other than "Ready", verify that the BMC connection information about the storage nodes is valid by referring to the event logs to be output after the status changes to "Ready". |
KARS10722-I |
The spare node is in a state in which spare node switchover is possible. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring is successful (Spare node) [Category] Service |
KARS10723-W |
The spare node is not in a state in which spare node switchover is possible. Connection from the cluster master node (primary) to the control port of the spare node could not be established. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Control network error) [Category] Service |
KARS10724-W |
The spare node is not in a state in which spare node switchover is possible. Connection with the spare node could not be established because authentication of a setup user of the spare node was unsuccessful. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Setup user authentication error) [Category] Service [Solution] Review the information about the spare node registered in the storage cluster. If there is any error, re-set the spare node information. |
KARS10725-W |
The spare node is not in a state in which spare node switchover is possible. The software version of the storage cluster and the software version of the spare node do not match. (Spare node ID = xxx, Fault domain ID = xxx, Version of the spare node = xxx) [Event Name] Spare node operation monitoring alert (Software version mismatch) [Category] Service |
KARS10726-W |
The spare node is not in a state in which spare node switchover is possible. Connection from the control port of the cluster master node (primary) to the BMC port of the spare node could not be established. (Spare node ID = xxx, BMC name of the spare node = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (BMC connection error) [Category] Service [Solution] Review the information about the spare node registered in the storage cluster. If there is any error, re-set the spare node information. Verify that connection between the control port of the cluster master node (primary) and the BMC port of the spare node is possible, and then troubleshoot any problem. Verify that there is no error in the BMC of the spare node, and then troubleshoot any problem. When a host name is used as a BMC name of the spare node, verify that the DNS server is started, the DNS server can resolve the BMC name, and network connection between the control port of the cluster master node (primary) and the DNS server is possible. If there is any problem, troubleshoot it. |
KARS10727-W |
The spare node is not in a state in which spare node switchover is possible. Authentication information of the BMC account of the spare node registered in the storage cluster has an error. Or, privileges assigned to the BMC account are insufficient. (Spare node ID = xxx, BMC name of the spare node = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (BMC account error) [Category] Service [Solution] Review the information about the spare node registered in the storage cluster. If there is any error, re-set the spare node information. Grant the "Login", "Virtual Power and Reset", and "Configure iLO Settings" privileges to the BMC account of the spare node. |
KARS10728-W |
The spare node is not in a state in which spare node switchover is possible. SSL/TLS connection with the BMC of the spare node could not be established. (Spare node ID = xxx, BMC name of the spare node = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (SSL/TLS connection error with the BMC) [Category] Service [Solution] Review the server certificate registered in the BMC of the spare node. Specifically, verify that the information of the BMC name (host name or IP address) of the spare node is included in the SAN or CN information of the server certificate, and confirm that the server certificate in use has not expired. Also, verify that a corresponding root certificate has been imported to the storage cluster. |
KARS10729-W |
The spare node is not in a state in which spare node switchover is possible. The physical server to which the BMC name of the spare node is allocated and the physical server to which the IP address of the control port is allocated do not match. (Spare node ID = xxx, BMC name of the spare node = xxx, Spare node IP address = xxx) [Event Name] Spare node operation monitoring alert (Physical server mismatch) [Category] Service [Solution] Review the information about the spare node registered in the storage cluster. If there is any error, re-set the spare node information. |
KARS10730-W |
The spare node is not in a state in which spare node switchover is possible. Connection from the internode port of the spare node to the internode port of the storage node in the same fault domain could not be established. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Internode network error) [Category] Service [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, and switch settings) of the internode network, and then make the network status such that communication is possible. |
KARS10732-I |
BMC connection information about the storage node is valid. (Storage node ID = xxx) [Event Name] Spare node operation monitoring is successful (Storage node BMC) [Category] Service |
KARS10733-W |
Spare node switchover is not possible for this storage node because BMC connection information about the storage node is invalid. BMC connection information about the storage node is not correctly set. (Storage node ID = xxx) [Event Name] Spare node operation monitoring alert (BMC connection information is not set) [Category] Service [Solution] Review the BMC connection information about the storage node registered in the storage cluster. If there is any problem, re-set the BMC connection information. If there is no problem with the BMC connection information, a password might not be set for the BMC account. Specify a password for the BMC account, and then re-set the BMC connection information. |
KARS10734-W |
Spare node switchover is not possible for the target storage node. Connection from the control port of the cluster master node (primary) to the BMC port of the storage node could not be established. (Storage node ID = xxx, BMC name of the storage node = xxx) [Event Name] Spare node operation monitoring alert (BMC connection error) [Category] Service [Solution] Review the BMC connection information about the storage node registered in the storage cluster. If there is any problem, re-set the BMC connection information. Verify that connection between the control port of the cluster master node (primary) and the BMC port of the storage node is possible, and then troubleshoot any problem. Verify that there is no error in the BMC of the storage node, and then troubleshoot any problem. When a host name is used as a BMC name of the storage node, verify that the DNS server is started, the DNS server can resolve the BMC name, and network connection between the control port of the cluster master node (primary) and the DNS server is possible. If there is any problem, troubleshoot it. |
KARS10735-W |
Spare node switchover is not possible for the target storage node. Authentication information of the BMC account of the storage node registered in the storage cluster has an error. Or, privileges assigned to the BMC account are insufficient. (Storage node ID = xxx, BMC name of the storage node = xxx) [Event Name] Spare node operation monitoring alert (BMC account error) [Category] Service [Solution] Review the BMC connection information about the storage node registered in the storage cluster. If there is any problem, re-set the BMC connection information. Grant the "Login", "Virtual Power and Reset", and "Configure iLO Settings" privileges to the BMC account of the storage node. |
KARS10736-W |
Spare node switchover is not possible for the target storage node. SSL/TLS connection with the BMC of the storage node could not be established. (Storage node ID = xxx, BMC name of the storage node = xxx) [Event Name] Spare node operation monitoring alert (SSL/TLS connection error with the BMC) [Category] Service [Solution] Review the server certificate registered in the BMC of the storage node. Specifically, verify that the information of the BMC name (host name or IP address) of the storage node is included in the SAN or CN information of the server certificate, and confirm that the server certificate in use has not expired. Also, verify that a corresponding root certificate has been imported to the storage cluster. |
KARS10737-W |
Spare node switchover is not possible for this storage node because BMC connection information about the storage node is invalid. The physical server to which the BMC name of the storage node is allocated and the physical server to which the IP address of the control port is allocated do not match. (Storage node ID = xxx, BMC name of the storage node = xxx) [Event Name] Spare node operation monitoring alert (Physical server mismatch) [Category] Service [Solution] Review the BMC connection information about the storage node registered in the storage cluster. If there is any problem, re-set the BMC connection information. |
KARS10738-W |
Spare node switchover is not possible for the target storage node. The BIOS UUID of the physical server of the storage node is not correctly set. (Storage node ID = xxx) [Event Name] Spare node operation monitoring alert (Physical server setting error) [Category] Service [Solution] Contact the hardware vendor to set the BIOS UUID of the physical server. |
KARS10739-W |
The spare node is not in a state in which spare node switchover is possible. The version of the system requirements file is old. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Old system requirements file) [Category] Service [Solution] Obtain the latest system requirements file, and then import the file. |
KARS10740-W |
The spare node is not in a state in which spare node switchover is possible. Connection from the control port of the spare node to the control port of the storage node could not be established. (Spare node ID = xxx, Storage node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Control network error) [Category] Service [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, and switch settings) of the control network, and then make the network status such that communication is possible. |
KARS10741-W |
The spare node is not in a state in which spare node switchover is possible. Subnets of the control port among storage nodes in the same fault domain as the spare node do not match. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Control network subnet mismatch) [Category] Service [Solution] Review the network settings so that the subnet of the control port of the spare node and the subnet of the control port of the storage nodes in the same fault domain match. |
KARS10742-W |
The spare node is not in a state in which spare node switchover is possible. The subnet of the control port of the spare node and the subnet of the control port of the storage nodes in the same fault domain do not match. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Control network subnet mismatch) [Category] Service [Solution] Review the network settings so that the subnet of the control port of the spare node and the subnet of the control port of the storage nodes in the same fault domain match. |
KARS10743-W |
The spare node is not in a state in which spare node switchover is possible. Subnets of the internode port among storage nodes in the same fault domain as the spare node do not match. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Internode network subnet mismatch) [Category] Service [Solution] Review the network settings and verify that the subnets of the internode port among storage nodes in the same fault domain as the spare node match. |
KARS10744-W |
The spare node is not in a state in which spare node switchover is possible. Subnets of the compute port among storage nodes in the same fault domain as the spare node do not match. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Compute network subnet mismatch) [Category] Service [Solution] Review the network settings and verify that the subnets of the compute port among storage nodes in the same fault domain as the spare node match. |
KARS10746-E |
Spare node information could not be registered. Hardware does not meet the system requirements. The installed memory capacity is insufficient. (Job ID = xxx, Spare node IP address = xxx, Installed memory capacity = xxx GiB) [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 maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10747-E |
Spare node information could not be edited. Hardware does not meet the system requirements. The installed memory capacity is insufficient. (Job ID = xxx, Spare node ID = xxx, Installed memory capacity = xxx GiB) [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 maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10748-E |
The operation cannot be performed due to insufficient memory capacity. (Operation = xxx, Job ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If another operation is running, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10749-W |
The spare node is not in a state in which spare node switchover is possible. The BIOS UUID of the physical server of the spare node is not correctly set. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Physical server setting error) [Category] Service [Solution] Contact the hardware vendor to set the BIOS UUID of the physical server. |
KARS10750-E |
Processing of spare node information registration ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the same job ID as this job, and then resolve the failure according to the recovery procedure. Then, retry the spare node information registration. |
KARS10751-E |
The operation could not be started due to conflict with another operation. (Operation = xxx, Job ID = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If another operation is in progress, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10752-E |
Spare node information could not be registered. Processing will be stopped abnormally because the information of the system requirements file registered in the storage cluster is invalid. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the operation. |
KARS10753-E |
Spare node information could not be edited. Processing will be stopped abnormally because the information of the system requirements file registered in the storage cluster is invalid. (Job ID = xxx, Spare node ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the operation. |
KARS10754-E |
Spare node information could not be registered. Processing will be stopped abnormally due to the system requirements file being an old version. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the operation. |
KARS10755-E |
Spare node information could not be edited. Processing will be stopped abnormally due to the system requirements file being an old version. (Job ID = xxx, Spare node ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the operation. |
KARS10756-E |
Spare node information could not be registered. Hardware does not meet the system requirements. The server model is not supported. (Job ID = xxx, Spare node IP address = xxx, Server model = 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 phenomenon persists, collect the logs, and then contact customer support. |
KARS10757-E |
Spare node information could not be edited. Hardware does not meet the system requirements. The server model is not supported. (Job ID = xxx, Spare node ID = xxx, Server model = 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 phenomenon persists, collect the logs, and then contact customer support. |
KARS10758-E |
Spare node information could not be registered. Hardware does not meet the system requirements. The number of installed CPU cores is insufficient. (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 phenomenon persists, collect the logs, and then contact customer support. |
KARS10759-E |
Spare node information could not be edited. Hardware does not meet the system requirements. The number of installed CPU cores is insufficient. (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 phenomenon persists, collect the logs, and then contact customer support. |
KARS10760-E |
Spare node information could not be registered because another operation might be in progress in the specified spare node. (Job ID = xxx, Spare node IP address = xxx) [Event Name] Spare node information setting error [Category] StorageNode |
KARS10763-W |
The spare node is not in a state in which spare node switchover is possible. The spare node has been registered in another storage cluster. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Spare node is registered in another storage cluster) [Category] Service |
KARS10764-W |
The spare node is not in a state in which spare node switchover is possible. Maintenance operation including operations from another storage cluster might be in progress for the spare node. (Spare node ID = xxx, Spare node IP address = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Maintenance operation in progress) [Category] Service |
KARS10766-W |
The spare node is not in a state in which spare node switchover is possible. The system requirements file registered in the storage cluster is invalid. (Spare node ID = xxx, Fault domain ID = xxx) [Event Name] Spare node operation monitoring alert (Invalid system requirements file) [Category] Service [Solution] Obtain the latest system requirements file, and then import the file. |
KARS10767-W |
The spare node is not in a state in which spare node switchover is possible. Spare node hardware does not meet the system requirements. The server model is not supported. (Spare node ID = xxx, Fault domain ID = xxx, Server model = xxx) [Event Name] Spare node operation monitoring alert (Unsupported server model) [Category] Service |
KARS10768-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 insufficient. (Spare node ID = xxx, Fault domain ID = xxx, Installed CPU cores = xxx) [Event Name] Spare node operation monitoring alert (Insufficient CPU core) [Category] Service |
KARS10769-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 installed memory capacity is insufficient. (Spare node ID = xxx, Fault domain ID = xxx, Installed memory capacity = xxx GiB) [Event Name] Spare node operation monitoring alert (Insufficient memory capacity) [Category] Service |
KARS10770-E |
A spare node could not be applied to the blocked storage node because the BMC account of the blocked storage node could not log in or because the BMC account registered in the blocked storage node is not authorized to forcibly stop the storage node. (Storage node ID where the application of the spare node failed = xxx, BMC name of the storage node where the application of the spare node failed = xxx) [Event Name] BMC authentication error or insufficient BMC account privilege for a blocked storage node [Category] StorageNode |
KARS10771-E |
A spare node could not be applied to the blocked storage node because SSL/TLS connection could not be established during BMC connection from the cluster master node (primary) to the blocked storage node via the control network or because the server certificate could not be verified. (Storage node ID where the application of the spare node failed = xxx, BMC name of the storage node where the application of the spare node failed = xxx) [Event Name] BMC security status/certificate setting error for a blocked storage node [Category] StorageNode |
KARS10772-E |
A spare node could not be applied to the blocked storage node because BMC connection from the cluster master node (primary) to the blocked storage node via the control network did not succeed. (Storage node ID where the application of the spare node failed = xxx, BMC name of the storage node where the application of the spare node failed = xxx) [Event Name] BMC connection failure for a blocked storage node [Category] StorageNode |
KARS10773-E |
A spare node could not be applied to the blocked storage node because connection from the cluster master node (primary) to the spare node via the control network did not succeed. (Storage node ID = xxx, Spare node ID = xxx, IP address of the spare node = xxx) [Event Name] Control network communication error [Category] StorageNode [Solution] When the applicable spare node has been registered in the storage cluster, disconnect the physical server of the applicable spare node from the network. After that, perform maintenance recovery manually, or perform replacement of the storage node to which the spare node could not be applied. Then, if the applicable spare node has been registered in the storage cluster, delete the corresponding spare node information. Use the disconnected physical server or a new physical server to perform procedures from installing the storage software to registering a spare node according the procedures for registering spare nodes. Note that, if you use the disconnected physical server, to prevent duplicated IP addresses, install the storage software before connecting it to the storage cluster network. |
KARS10774-E |
Connection to the spare node via the control network did not succeed due to a user authentication error. The spare node could not be applied to the blocked storage node. (Storage node ID = xxx, Spare node ID = xxx, IP address of the spare node = xxx) [Event Name] User authentication error [Category] StorageNode [Solution] When the applicable spare node has been registered in the storage cluster, disconnect the physical server of the applicable spare node from the network. After that, perform maintenance recovery manually, or perform replacement of the storage node to which the spare node could not be applied. Then, if the applicable spare node has been registered in the storage cluster, delete the corresponding spare node information. Use the disconnected physical server or a new physical server to perform procedures from installing the storage software to registering a spare node according the procedures for registering spare nodes. Note that, if you use the disconnected physical server, to prevent duplicated IP addresses, install the storage software before connecting it to the storage cluster network. |
KARS10775-E |
A spare node could not be applied to the blocked storage node because the blocked storage node IP address to be set to the spare node is duplicated on the control network. (Storage node ID where the application of the spare node failed = xxx, Spare node ID = xxx, Duplicated IP address and MAC address of the device with that IP address set = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] When the applicable spare node has been registered in the storage cluster, disconnect the physical server of the applicable spare node from the network. After that, perform maintenance recovery manually, or perform replacement of the storage node to which the spare node could not be applied. Then, if the applicable spare node has been registered in the storage cluster, delete the corresponding spare node information. Use the disconnected physical server or a new physical server to perform procedures from installing the storage software to registering a spare node according the procedures for registering spare nodes. Note that, if you use the disconnected physical server, to prevent duplicated IP addresses, install the storage software before connecting it to the storage cluster network. |
KARS10776-E |
The storage node is in persistent blockage status. (Storage node ID = xxx) [Event Name] Storage node persistent blockage [Category] StorageNode [Solution] If there is an event log indicating that an attempt to apply a spare node to the applicable storage node was not successful, see the event log and take action accordingly. Then, perform manually maintenance recovery or replacement of the storage node. |
KARS10780-I |
The blocked storage node was stopped forcibly. (Storage node ID applying spare node = xxx, BMC name of the storage node that was forcibly stopped = xxx) [Event Name] Forcibly stopped the blocked storage node [Category] StorageNode |
KARS10781-I |
A spare node was applied to the blocked storage node. (Applied storage node ID = xxx, Spare node ID = xxx, BMC name of the spare node = xxx) [Event Name] Applying a spare node to the blocked storage node completed [Category] StorageNode |
KARS10782-W |
A spare node registered in the storage cluster was applied to the blocked storage node, thus consuming one of the spare nodes registered in the storage cluster. [Event Name] Use of a registered spare node [Category] StorageNode [Solution] Disconnect the physical server of the forcibly stopped storage node from the network. To continue to use the spare nodes, prepare a new physical server and register the spare nodes to it. |
KARS10784-E |
Spare node information could not be edited. The specified spare node has already been registered in the same storage cluster. (Job ID = xxx, Spare node ID = xxx, Spare node ID of same bios uuid = xxx) [Event Name] Spare node information setting error [Category] StorageNode [Solution] Verify that the target spare node has not been registered as a spare node for another use. |
KARS10787-E |
A spare node could not be applied to the blocked storage node because another operation might be in progress on the spare node. (Storage node ID where the application of the spare node failed = xxx, Spare node ID = xxx) [Event Name] Concurrent operation prohibited [Category] StorageNode [Solution] Perform maintenance recovery manually, or perform replacement for the storage node to which the spare node could not be applied. |
KARS10788-E |
A spare node could not be applied to the blocked storage node because a failure occurred in the cluster master node (primary). (Storage node ID where the application of the spare node failed = xxx, Spare node ID = xxx) [Event Name] Applying a spare node to the storage node failed (Cluster master node (primary) failure) [Category] StorageNode |
KARS10789-E |
A spare node could not be applied to the blocked storage node because a failure occurred in the cluster master node (primary). (Storage node ID where the application of the spare node failed = xxx, Spare node ID = xxx) [Event Name] Applying a spare node to the storage node failed (Cluster master node (primary) failure) [Category] StorageNode |
KARS10790-E |
Spare node information could not be registered due to an internal error. (Operation = xxx, Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10791-E |
The spare node could not be applied to the blocked storage node because an internal error occurred. (Storage node ID where the application of the spare node failed = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Perform maintenance recovery manually, or replace the storage node to which the spare node could not be applied. Also, verify whether no problem exists with the BMC of the applicable storage node. |
KARS10792-E |
The spare node could not be applied to the blocked storage node because an internal error occurred. (Storage node ID where the application of the spare node failed = xxx, Spare node ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] When the applicable spare node has been registered in the storage cluster, disconnect the physical server of the applicable spare node from the network. After that, perform maintenance recovery manually, or perform replacement for the storage node to which the spare node could not be applied. Then, if the applicable spare node has been registered in the storage cluster, delete the corresponding spare node information. Then, use the disconnected physical server or a new physical server to perform procedures from installing the storage software to registering a spare node, while referring to the instructions for registering spare nodes. Note that, if you use the disconnected physical server, to prevent duplicated IP addresses, install the storage software before connecting it to the storage cluster network. |
KARS10793-E |
Spare node information could not be edited due to an internal error. (Operation = xxx, Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10794-E |
Spare node information could not be deleted due to an internal error. (Operation = xxx, Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10796-E |
Whether spare node switchover is possible cannot be verified because an internal error occurred. [Event Name] Spare node operation monitoring alert (Internal error) [Category] Service [Solution] Verify whether there are any errors in the BMC of the storage node and spare node, and troubleshoot as necessary. If an event log indicating whether spare node switchover is possible is not output after a while, collect the logs, and then contact customer support. |
KARS10798-E |
Processing of spare node information editing ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the same job ID as this job, and then resolve the failure according to the recovery procedure. Then, retry the spare node information edition. |
KARS10799-E |
Processing of spare node information deleting ended abnormally. [Cause] A failure occurred. [Solution] See the event logs with the same job ID as this job, and then resolve the failure according to the recovery procedure. Then, retry the spare node information deletion. |
KARS10800-W |
Update of the health status was aborted. (Type = xxx, Protection domain ID = xxx) [Event Name] Health status update failed [Category] StorageCluster [Solution] If no event log is output showing that update of the health status was resumed, collect the logs, and contact customer support. Note: If the type is "Storage" or "License", "null" is output as Protection domain ID. |
KARS10801-I |
Update of the health status was resumed. (Type = xxx, Protection domain ID = xxx) [Event Name] Health status update recovered [Category] StorageCluster Note: If the type is "Storage" or "License", "null" is output as Protection domain ID. |
KARS10900-E |
Memory is insufficient. (Job ID = xxx) [Event Name] Insufficient memory [Category] StorageNode [Solution] Wait a while, and then retry the operation. If another operation is running, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10901-E |
The operation cannot be executed due to a conflict with another operation. (Job ID = xxx) [Event Name] Conflict with another storage node operation [Category] StorageNode [Solution] Wait a while, and then retry the operation. Also, if you execute another operation, please execute the operation after completion of another operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10902-E |
An error occurred while accessing the database. (Job ID = xxx) [Event Name] Database access error [Category] StorageNode |
KARS10903-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error [Category] StorageNode |
KARS10904-I |
A temporary error occurred so the operation was retried. (Operation = xxx, Job ID = xxx) [Event Name] Operation retry [Category] StorageNode [Solution] If this job is running, wait a while. If this job failed, see other event logs. |
KARS10905-E |
Software update was aborted because the storage node to be updated was in a state that did not allow the software update. (Job ID = xxx, Storage node ID = xxx) [Event Name] Invalid software update conditions (Inappropriate storage node status) [Category] StorageNode [Solution] See the event log, which shows the other causes of the failure, and recover the storage node from the failure. Then, update the software again. |
KARS10906-E |
Processing cannot be performed because storage software is being updated. (Job ID = xxx) [Event Name] Storage node maintenance pre-check [Category] StorageNode [Solution] Retry the operation after storage software has been updated. |
KARS10907-E |
The processing cannot be performed because the specified storage node failed to abort the volume migration. (Job ID = xxx, Volume ID = xxx) [Event Name] Failure to stop volume migration for storage node maintenance [Category] StorageNode [Solution] Retry the operation. |
KARS10908-E |
Maintenance operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage cluster master node (primary) error [Category] StorageNode |
KARS10909-E |
An error occurred in the internode network. (Job ID = xxx, IP address = xxx) [Event Name] Internode network error [Category] StorageNode [Solution] Verify the internode network status. If an error occurred, resolve the failure, and then retry the operation. |
KARS10910-E |
An error occurred in the communicating storage node. (Job ID = xxx, IP address = xxx) [Event Name] Error in the communicating storage node [Category] StorageNode [Solution] Verify the internode network status. If an error occurred, resolve the failure, and then retry the operation. If there is an event log that describes the same job ID as this job ID, or an event log that indicates a failure other than the target of this job, correct the problem according to the recovery procedure described in the event log. Then, retry the operation. |
KARS10911-C |
The system cannot continue operation because a failure exceeding fault tolerance of the storage cluster occurred. The storage cluster is blocked. [Event Name] Failure exceeding fault tolerance of the storage cluster occurred [Category] StorageCluster [Solution] Collect the logs, and then contact customer support. |
KARS10912-E |
Maintenance operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage cluster master node (primary) error [Category] StorageNode |
KARS10913-E |
The processing will be stopped abnormally due to disconnection with the storage node subject to maintenance. (Operation = xxx, Job ID = xxx, IP address = xxx) [Event Name] Disconnection with the storage node subject to maintenance [Category] StorageNode [Solution] Verify that the storage node subject to maintenance is powered on and that connection with the target storage node is possible via the control network. Then, retry the maintenance operation. |
KARS10914-W |
A disconnected path was detected as a result of verifying the connection for each path of a redundant control network. Current processing will be continued. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Reduced network redundancy detected [Category] StorageNode [Solution] After the current processing for the target storage node completes, verify that there is no problem with the network settings (such as wiring, MTU, and switch settings), and then make the network status such that communication is possible. If you need to verify the connection again, perform maintenance blocking for the target storage node, and then perform storage node replacement. |
KARS10915-W |
A disconnected path was detected as a result of verifying the connection for each path of a redundant internode network. Current processing will be continued. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Reduced network redundancy detected [Category] StorageNode [Solution] After the current processing for the target storage node completes, verify that there is no problem with the network settings (such as wiring, MTU, and switch settings), and then make the network status such that communication is possible. If you need to verify the connection again, perform maintenance blocking for the target storage node, and then perform storage node replacement. |
KARS10916-E |
An NIC is not installed in a defined slot of the physical server. (Job ID = xxx, Storage node = xxx, PCI address for which information acquisition was unsuccessful = xxx) [Event Name] Obtaining information from the physical server did not succeed [Category] StorageNode [Solution] Verify whether the defined NIC is installed in the slot with the PCI address displayed in the message. Install the defined NIC in the slot, and then retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10917-E |
The processing will be stopped abnormally due to the old version of the system requirements file. (Operation = xxx, Job ID = xxx) [Event Name] Old system requirements file [Category] StorageCluster [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the maintenance operation. |
KARS10918-E |
The network of the compute port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address indicated in the message, and then reperform maintenance operation. |
KARS10919-E |
The configuration files could not be read. (Job ID = xxx) [Event Name] The configuration file could not be read [Category] StorageCluster [Solution] A configuration file of a different version from that of the current storage cluster software might be in use. Verify the configuration file in use or the procedure of the Operation Guide being performed. |
KARS10920-W |
Verification of control port connection shows that communication with the storage node subject to maintenance was successful. However, network connection might be unstable. (Job ID = xxx, Storage node = xxx, IP address = xxx) [Event Name] Unstable connection of the control network (Connection success rate 80%) [Category] StorageNode [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings). |
KARS10921-E |
Connection from the storage node subject to maintenance to the control network of all the storage nodes could not be verified. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Network connection verification did not succeed [Category] StorageNode [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings), and then make the network status such that communication is possible. After that, retry the maintenance operation. |
KARS10922-E |
Connection from the storage node subject to maintenance to the internode network of all the storage nodes could not be verified. (Job ID = xxx, Storage node = xxx, Information about connection-source MAC address and connection-destination IP address for disconnected paths = xxx) [Event Name] Network connection verification did not succeed [Category] StorageNode [Solution] Verify that there is no problem with the network settings (such as wiring, MTU, or switch settings), and then make the network status such that communication is possible. After that, retry the maintenance operation. |
KARS10923-E |
The network for the internode port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx, MAC address of the device for which a duplicated IP address is set = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address with the component indicated by the MAC address displayed in the message, and then retry the maintenance operation. |
KARS10924-E |
The network of the compute port could not be set because an IP address is duplicated on the network. (Job ID = xxx, Duplicated IP address = xxx, MAC address of the device for which a duplicated IP address is set = xxx) [Event Name] Duplicated IP address [Category] StorageNode [Solution] Resolve the duplication of the IP address with the component indicated by the MAC address displayed in the message, and then retry the maintenance operation. |
KARS10925-E |
The target storage node cannot be integrated into a storage cluster because setup of each storage node is not completed normally. (Operation = xxx, Job ID = xxx, Storage node = xxx) [Event Name] Setup for each storage node could not be completed [Category] StorageNode |
KARS10926-E |
The operation of integrating the target storage node into a storage cluster was evidently already tried. Therefore, the target storage node could not be integrated into the storage cluster. (Operation = xxx, Job ID = xxx, Storage node = xxx) [Event Name] Reinstalling the storage software is necessary [Category] StorageNode |
KARS10927-E |
Processing will be stopped abnormally due to another processing in progress for the storage node subject to maintenance. (Operation = xxx, Job ID = xxx, Storage node = xxx) [Event Name] Concurrent operation prohibited [Category] StorageNode [Solution] If setup of each storage node is in progress, complete it. Then, retry the maintenance operation. |
KARS10928-E |
Processing will be stopped abnormally due to disconnection with the storage node subject to maintenance. (Operation = xxx, Job ID = xxx) [Event Name] Connection with the storage nodes subject to maintenance has been lost [Category] StorageNode [Solution] Verify that the storage nodes subject to maintenance are powered on and that it can be connected to the control network. Then, retry the maintenance operation. |
KARS10931-E |
The operation cannot be performed because the storage cluster status is not "Ready". (Operation = xxx, 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. |
KARS10932-E |
The operation cannot be continued because the memory capacity of the storage node subject to maintenance is less than the minimum memory capacity of the protection domain (xxx MiB). (Job ID = xxx, Storage node = xxx) [Event Name] Maintenance pre-check (Less than the minimum memory capacity) [Category] StorageNode [Solution] Expand the memory capacity of the storage node subject to maintenance to more than the minimum memory capacity of the protection domain, and then retry the operation. |
KARS10933-E |
Processing will be stopped abnormally due to another processing in progress for the storage node subject to maintenance. (Operation = xxx, Job ID = xxx) [Event Name] Concurrent operation prohibited [Category] StorageNode [Solution] Verify that the applicable storage node is not being used for another operation. If setup of each storage node is in progress, allow it to complete. Then, retry the maintenance operation. If the phenomenon persists, restart the storage node, and then perform maintenance operation. |
KARS10934-E |
The processing will be stopped abnormally because the information of the system requirements file registered in the storage cluster is invalid. (Operation = xxx, Job ID = xxx) [Event Name] Invalid system requirements file [Category] StorageNode [Solution] Obtain the latest system requirements file, and then import the system requirements file. Then, retry the maintenance operation. |
KARS10935-E |
The processing cannot be performed because there is a storage node that has not been removed yet. (Operation = xxx, Job ID = xxx, Storage node ID = xxx) [Event Name] Maintenance pre-check (Storage nodes yet to be removed) [Category] StorageNode [Solution] Complete the storage node removal, and then retry the operation. |
KARS10936-E |
The operation cannot be performed due to blocked storage nodes. (Operation = xxx, Job ID = xxx, Storage node ID = xxx) [Event Name] Maintenance pre-check (Blocked storage nodes) [Category] StorageNode [Solution] Recover the blocked storage nodes, and then retry the operation. |
KARS10937-E |
Hardware does not meet the system requirements. The server model is not supported. (Job ID = xxx, Storage node = xxx, Server model = xxx) [Event Name] Hardware that does not meet system requirements (Server model) [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. Then, replace the hardware components with the ones that satisfy hardware requirements. After that, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10938-E |
Hardware does not meet the system requirements. The number of installed CPU cores is insufficient. (Job ID = xxx, Storage node = xxx, Installed CPU cores = xxx) [Event Name] Hardware that does not meet system requirements (CPU) [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. Then, replace the hardware components with the ones that satisfy hardware requirements. After that, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10939-E |
Hardware does not meet the system requirements. The installed memory capacity is insufficient. (Job ID = xxx, Storage node = xxx, Installed memory capacity = xxx GiB) [Event Name] Hardware that does not meet system requirements (Memory) [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. Then, replace the hardware components with the ones that satisfy hardware requirements. After that, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10940-E |
The target storage node might be in use as a spare node. Therefore, the storage node cannot be integrated into a storage cluster. (Operation = xxx, Job ID = xxx, Storage node = xxx) [Event Name] The specified storage node is in use as a spare node [Category] StorageNode |
KARS10941-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 AWS, and then troubleshoot any problem. If the phenomenon persists after retry, collect the logs, and then contact customer support. |
KARS10942-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 AWS, and then troubleshoot any problem. If the phenomenon persists after retry, collect the logs, and then contact customer support. |
KARS10943-E |
Maintenance operation ended abnormally because a failure occurred in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage 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 AWS, and then troubleshoot any problem. Then, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10944-E |
An error occurred in the internode network. (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 AWS, and then troubleshoot any problem. Then, retry the operation that was being performed. |
KARS10945-E |
An error occurred in the communicating storage node. (Job ID = xxx, IP address = xxx) [Event Name] 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 AWS, 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 that was being performed. |
KARS10946-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 AWS, and then troubleshoot any problem. Then, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10947-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 AWS, and then troubleshoot any problem. Then, retry the maintenance operation. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS10948-E |
Storage pool expansion for the drives connected to the storage node subject to maintenance did not succeed. (Job ID = xxx) [Event Name] Storage pool expansion failed [Category] StorageNode [Solution] If storage pool expansion is being performed while this job is running, verify the results. If storage pool expansion is not being performed, no action is required for storage pool expansion failure. |
KARS10949-E |
Verifying completion of expanding the storage pool for the drives connected to the storage node subject to maintenance did not succeed. (Job ID = xxx) [Event Name] Verification of completion of storage pool expansion failed [Category] StorageNode [Solution] If storage pool expansion is being performed while this job is running, verify the results. If storage pool expansion is not being performed, no action is required for storage pool expansion failure. |
KARS10960-E |
Expanding of the storage pool for the drives connected to the storage node subject to maintenance ended abnormally. (Job ID = xxx, Storage pool expansion job ID = xxx) [Event Name] Storage pool expansion ended abnormally [Category] StorageNode [Solution] Verify the results of the storage pool expansion job, and then take action accordingly. |
KARS10992-E |
The request could not be executed. [Cause] The operation conflicts with another one, and, therefore, could not be executed. [Solution] Wait a while, and then retry the operation. Also, if you execute another operation, please execute the operation after completion of another operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS10994-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS10995-C |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error (Customer support) [Category] StorageNode [Solution] Any further operation is prohibited. Collect the logs, and then contact customer support. |
KARS10996-C |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage cluster internal processing error (Customer support) [Category] StorageCluster [Solution] Any further operation is prohibited. Collect the logs, and then contact customer support. |
KARS10997-E |
The operation can not be executed due to conflict another operation. (Operation = xxx, Job ID = xxx) [Event Name] Conflict with another storage cluster operation [Category] StorageCluster |
KARS10998-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage node internal processing error (Retry) [Category] StorageNode |
KARS10999-E |
An internal error occurred. (Operation = xxx, Job ID = xxx) [Event Name] Storage cluster internal processing error (Retry) [Category] StorageCluster |