Message ID |
Message |
|---|---|
KARS08000-E |
A request for stopping the storage cluster could not be accepted. [Cause] A request for stopping the storage cluster could not be accepted due to a currently-running operation that conflicts or other cause. [Solution] Take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference. |
KARS08100-I |
The storage cluster started. [Event Name] Storage cluster start [Category] Service |
KARS08101-I |
Stops the storage cluster. [Event Name] Storage cluster stopping started [Category] Service |
KARS08102-I |
The I/O function stopped. [Event Name] Storage cluster I/O stop [Category] Service |
KARS08103-E |
The storage node, xxx was blocked. [Event Name] Storage node temporary blockage [Category] StorageNode [Solution] Recover the target storage node. Note: The same event log might be notified multiple times. If the following conditions are met, ignore this message:
|
KARS08104-E |
Update of the storage software to the target version was aborted because the cluster master node was not redundant. [Event Name] Invalid software update conditions (Insufficient redundancy of the cluster master node) [Category] StorageCluster [Solution] See the event logs, and recover the storage node from the failure. Then, perform storage software update again. |
KARS08105-I |
The storage cluster is running in maintenance mode. It changes to normal mode the next time it restarts. [Event Name] The storage cluster is in maintenance mode [Category] StorageCluster |
KARS08107-E |
An internal error occurred while the storage cluster was being stopped. [Event Name] The storage cluster failed to stop due to an internal error [Category] Service [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS08108-E |
Storage node starting cannot be verified. (Storage node ID = xxx) [Event Name] Storage node start failed [Category] StorageNode [Solution] Verify that the storage node is powered on and the network is properly connected. |
KARS08109-I |
The storage cluster is running in initializing storage controller mode. It changes to normal mode the next time it restarts. [Event Name] Storage cluster is in initializing storage controller mode [Category] StorageCluster |
KARS08110-I |
Storage node starting could be verified. (Storage node ID = xxx) [Event Name] Storage node starting verification [Category] StorageNode |
KARS08111-I |
Storage cluster starting resumed. [Event Name] Resuming storage cluster start [Category] StorageCluster |
KARS08112-E |
Storage cluster starting was suppressed. [Event Name] Storage cluster starting suppression [Category] StorageCluster [Solution] Take action as described in the message (KARS08108-E). If the storage cluster starting is not resumed 30 minutes after action was taken for all the storage nodes, see the VSP One SDS Block and SDS Cloud System Administration to start the storage cluster forcibly. |
KARS08113-C |
The storage cluster cannot be started because a failure exceeding fault tolerance of the storage cluster occurred. [Event Name] Starting the storage cluster failure (Exceeds the fault tolerance of the storage cluster) [Category] StorageCluster [Solution] Collect the logs, and then contact customer support. |
KARS08114-E |
Storage cluster forced starting was canceled because a failure exceeding fault tolerance of the storage cluster occurs. [Event Name] Storage cluster forced starting cancellation [Category] StorageCluster [Solution] See the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration. If the same error occurs, collect the logs, and then contact customer support. |
KARS08115-E |
The storage cluster cannot be started forcibly. [Event Name] Invalid storage cluster forced starting conditions [Category] StorageCluster [Solution] Verify whether storage cluster forced starting is possible. If it is possible, retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08116-E |
The storage cluster cannot be started forcibly. [Cause] The storage cluster does not meet forced starting conditions. [Solution] Verify whether storage cluster forced starting is possible. If it is possible, retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08117-E |
The storage cluster cannot be started forcibly. [Event Name] Storage cluster forced starting unavailable [Category] StorageCluster [Solution] See the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration. If the same error occurs, collect the logs, and then contact customer support. |
KARS08118-E |
The storage cluster cannot be started forcibly. [Cause] The storage cluster is not in a state where start processing can be resumed. [Solution] See the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration. If the same error occurs, collect the logs, and then contact customer support. |
KARS08119-E |
Instruction for starting the storage cluster forcibly was unsuccessful. [Event Name] Storage cluster forced starting instruction failed (Internal error) [Category] StorageCluster [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS08120-E |
Instruction for starting the storage cluster forcibly was unsuccessful. [Cause] An unexpected error occurred. [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS08121-E |
The storage cluster is being blocked because an abnormal error occurred while the storage cluster was being shut down. [Event Name] Storage cluster blocking (Abnormal error occurred during storage cluster shutdown) [Category] StorageCluster [Solution] Wait at least 45 minutes from when the event log was output, and then see the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration as required. |
KARS08122-E |
Starting the storage cluster failed. [Event Name] Starting the storage cluster failure [Category] StorageCluster [Solution] Wait at least 45 minutes from when the event log was output, and then see the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration. If the same error occurs, collect the logs, and then contact customer support. |
KARS08123-I |
Forcibly stops the storage cluster. [Event Name] Storage cluster force stopping started [Category] Service |
KARS08124-C |
The system cannot continue operation because a failure exceeding fault tolerance of the storage cluster occurred. The storage cluster is blocked. (Storage node ID = xxx) [Event Name] Failure exceeding fault tolerance of the storage cluster occurred due to storage node failure [Category] StorageCluster [Solution] Wait at least 45 minutes from when the event log was output, and then see the VSP One SDS Block and SDS Cloud System Administration to shut down the storage cluster forcibly. Then, start the storage cluster according to the VSP One SDS Block and SDS Cloud System Administration. If startup of the storage cluster is not completed, collect the logs, and then contact customer support. |
KARS08150-E |
The cluster master node xxx was blocked. [Event Name] Cluster master node temporarily blockage [Category] StorageNode [Solution] Change the role or perform recovery of the target storage node. |
KARS08151-I |
The role change of the storage nodes is started. (Promoted storage node ID = xxx, Demoted storage node ID = xxx, Job ID = xxx) [Event Name] Storage node role change started [Category] StorageNode |
KARS08152-I |
The role change of the storage nodes is completed. (Promoted storage node ID = xxx, Demoted storage node ID = xxx, Job ID = xxx) [Event Name] Storage node role change completed [Category] StorageNode |
KARS08153-E |
The role of the storage nodes could not be changed. (Promoted storage node ID = xxx, Demoted storage node ID = xxx, Job ID = xxx) [Event Name] Storage node role change failed [Category] StorageNode [Solution] If an event log indicating another error is output, take action referring to the event log. If the same error occurs, collect the logs, and then contact customer support. |
KARS08154-E |
Status of the intended storage node is invalid. (Promoted storage node ID = xxx, Demoted storage node ID = xxx, Job ID = xxx) [Event Name] Storage node role change failed (Invalid target storage nodes) [Category] StorageNode [Solution] Verify that the appropriate storage node is selected for the intended storage node. |
KARS08155-E |
The status of the storage cluster is invalid. (Job ID = xxx) [Event Name] Storage node role change failed (Invalid storage cluster status) [Category] StorageNode [Solution] Verify the status of the storage cluster. |
KARS08156-E |
An operation that cannot be performed concurrently is being performed. (Job ID = xxx) [Event Name] Storage node role change failed (Concurrent operation prohibited) [Category] StorageNode [Solution] Wait until the operation that cannot be performed concurrently is complete, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08157-E |
The role change of the storage nodes cannot be performed. (Job ID = xxx) [Event Name] Storage node role change failed (Invalid role change) [Category] StorageNode [Solution] To be able to change the role of storage node, the storage cluster must first be stopped. Stop the storage cluster, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08158-E |
The role of the storage nodes could not be changed. (Promoted storage node ID = xxx, Demoted storage node ID = xxx) [Cause] An error occurred while the operation was being performed. [Solution] If an event log indicating another error is output, take action referring to the event log. If the same error occurs, collect the logs, and then contact customer support. |
KARS08159-E |
The role of the storage nodes cannot be changed. (Promoted storage node ID = xxx, Demoted storage node ID = xxx) [Cause] The status of the intended storage node is invalid. [Solution] Select a storage node that satisfies the conditions, and then retry the operation. |
KARS08160-E |
The role of the storage nodes cannot be changed. [Cause] The status of the storage cluster is invalid. [Solution] Wait until the status of the storage cluster is ready, and then retry the operation. |
KARS08161-E |
An operation that can not be performed concurrently is being performed. [Cause] The operation for the storage cluster conflicts with another one. [Solution] Wait until the operation that cannot be performed concurrently is complete, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08162-E |
The role of the storage nodes cannot be changed. [Cause] The role change of the storage nodes cannot be performed. [Solution] To be able to change the role of storage node, the storage cluster must first be stopped. Stop the storage cluster, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08163-E |
The number of cluster master nodes per fault domain is invalid. (Job ID = xxx) [Event Name] Storage node role change failed (Invalid number of cluster master nodes per fault domain) [Category] StorageNode [Solution] Review the VSP One SDS Block and SDS Cloud System Administration, and then select the target storage nodes so that the number of cluster master nodes included in each fault domain is appropriate. |
KARS08164-E |
The role of the storage nodes could not be changed. [Cause] The number of cluster master nodes per fault domain is invalid. [Solution] Review the VSP One SDS Block and SDS Cloud System Administration, and then select the target storage nodes so that the number of cluster master nodes included in each fault domain is appropriate. |
KARS08170-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08171-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08172-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08173-E |
Another operation is running. (Job ID = xxx) [Event Name] Exclusive control error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If you are performing another update operation, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS08175-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08176-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08177-E |
The request could not be executed. (Job ID = xxx) [Event Name] Internal error [Category] StorageNode [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08178-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS08179-E |
The request could not be executed. (Job ID = xxx) [Event Name] Invalid storage node ID specification [Category] StorageNode [Solution] Verify the specified storage node ID, and then retry the operation. |
KARS08180-E |
The request could not be executed. [Cause] An invalid storage node ID was specified. [Solution] Verify the specified storage node ID, and then retry the operation. |
KARS08181-W |
Configuration information locking was detected during storage cluster starting. [Event Name] Configuration information locking during starting [Category] StorageCluster [Solution] If the storage clusters are being started normally, you do not need to take action. If the storage clusters are not being started normally, verify whether any event logs related to starting of other storage clusters are output. If such event logs are output, take action according to the event logs. If such event logs are not output, see the VSP One SDS Block and SDS Cloud Troubleshooting Reference to take action. |
KARS08200-E |
Connection with the DNS server is not possible. (DNS server = xxx, Storage node ID = xxx) [Event Name] DNS server connection error [Category] Service [Solution] Verify DNS server connectivity. To do this, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. |
KARS08201-I |
Connection recovered for all the DNS servers. (Storage node ID = xxx) [Event Name] DNS server connection to recover [Category] Service |
KARS08202-E |
Connection with the NTP server is not possible. (Storage node ID = xxx) [Event Name] NTP server connection error [Category] Service [Solution] Verify NTP server connectivity. To do this, follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference. |
KARS08203-I |
Connection recovered for the NTP server. (NTP server = xxx, Storage node ID = xxx) [Event Name] NTP server connection to recover [Category] Service |
KARS08204-W |
An error was detected when accessing the system drive of the storage node. (Storage node ID = xxx) [Event Name] System drive error detection [Category] StorageNode [Solution] Review the physical node and hypervisor, or target resources in a cloud infrastructure to verify that the storage node system drive has no error. If there is any error, take action according to the VSP One SDS Block and SDS Cloud System Administration. For details about how to confirm a physical server and hypervisor, or target resources in a cloud infrastructure, see the respective vendor's documentation. |
KARS08205-W |
Delays in access response of the storage node system drive were detected. (Storage node ID = xxx) [Event Name] Delayed system drive access response detected [Category] StorageNode [Solution] Verify that no error has occurred in physical server or hypervisor hardware operation, or in target resources in a cloud infrastructure. If there is any error, take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference. For details about how to confirm physical server or hypervisor hardware operation, or target resources in a cloud infrastructure, see the respective vendor's documentation. |
KARS08206-I |
Delays in access response of the storage node system drive have recovered. (Storage node ID = xxx) [Event Name] Delayed system drive access response recovered [Category] StorageNode |
KARS08207-E |
Synchronization with an Azure host was unsuccessful. (Storage node ID = xxx) [Event Name] Azure host time synchronization error [Category] Service [Solution] Contact Azure support to verify whether the Azure host has any problem providing time information. |
KARS08208-I |
Time synchronization with Azure host has been recovered. (Storage node ID = xxx) [Event Name] Azure host time synchronization to recover [Category] Service |
KARS08300-W |
Control port link down was detected. The control port status is Warning. The active port was switched. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port link down [Category] ControlPort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08301-W |
Control port link down was detected. The control port status is Warning. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port link down [Category] ControlPort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08302-E |
Control port link down was detected. The control port status is Error. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port link down [Category] ControlPort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08303-E |
Control port link down was detected. The control port status is Error. (Storage node ID = xxx, Control port (primary) MAC address = xxx, Control port (secondary) MAC address = xxx) [Event Name] Control port link down [Category] ControlPort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08304-I |
Control port connection recovery was detected. The control port status is Warning. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port connection recovery [Category] ControlPort |
KARS08305-I |
Control port connection recovery was detected. The control port status is normal. (Storage node ID = xxx, Control port MAC address = xxx, Active port = xxx) [Event Name] Control port connection recovery [Category] ControlPort |
KARS08306-I |
Control port connection recovery was detected. The control port status is normal. (Storage node ID = xxx, Control port (primary, secondary) MAC address = xxx, Active port = xxx) [Event Name] Control port connection recovery [Category] ControlPort |
KARS08307-E |
The control port status could not be obtained. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port status acquisition failure [Category] ControlPort [Solution] A network failure has occurred on the target port of the MAC address where the failure has occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and deal with network failures. For details about how to review the physical server, see the respective vendor's documentation. |
KARS08308-E |
The control port status could not be obtained. (Storage node ID = xxx, Control port (primary) MAC address = xxx, Control port (secondary) MAC address = xxx) [Event Name] Control port status acquisition failure [Category] ControlPort [Solution] A network failure has occurred on the target port of the MAC address where the failure has occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and deal with network failures. For details about how to review the physical server, see the respective vendor's documentation. |
KARS08309-W |
Internode port link down was detected. The Internode port status is Warning. The active port was switched. (Storage node ID = xxx, Internode port MAC address = xxx) [Event Name] Internode port link down [Category] InternodePort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08310-W |
Internode port link down was detected. The Internode port status is Warning. (Storage node ID = xxx, Internode port MAC address = xxx) [Event Name] Internode port link down [Category] InternodePort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08311-E |
Internode port link down was detected. The internode port status is Error. (Storage node ID = xxx, Internode port MAC address = xxx) [Event Name] Internode port link down [Category] InternodePort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08312-E |
Internode port link down was detected. The internode port status is Error. (Storage node ID = xxx, Internode port (primary) MAC address = xxx, Internode port (secondary) MAC address = xxx) [Event Name] Internode port link down [Category] InternodePort [Solution] Network failure occurred in the port corresponding to the MAC address for which a failure occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and correct network failures. For details about how to confirm the physical server, see the respective vendor's documentation. |
KARS08313-I |
Internode port connection recovery was detected. The internode port status is Warning. (Storage node ID = xxx, Internode port MAC address = xxx) [Event Name] Internode port connection recovery [Category] InternodePort |
KARS08314-I |
Internode port connection recovery was detected. The internode port status is normal. (Storage node ID = xxx, Internode port MAC address = xxx, Active port = xxx) [Event Name] Internode port connection recovery [Category] InternodePort |
KARS08315-I |
Internode port connection recovery was detected. The internode port status is normal. (Storage node ID = xxx, Internode port (primary, secondary) MAC address = xxx, Active port = xxx) [Event Name] Internode port connection recovery [Category] InternodePort |
KARS08316-E |
The internode port status could not be obtained. (Storage node ID = xxx, Internode port MAC address = xxx) [Event Name] Internode port status acquisition failure [Category] InternodePort [Solution] A network failure has occurred on the target port of the MAC address where the failure has occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and deal with network failures. For details about how to review the physical server, see the respective vendor's documentation. |
KARS08317-E |
The internode port status could not be acquired. (Storage node ID = xxx, Internode port (primary) MAC address = xxx, Internode port (secondary) MAC address = xxx) [Event Name] Internode port status acquisition failure [Category] InternodePort [Solution] A network failure has occurred on the target port of the MAC address where the failure has occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and deal with network failures. For details about how to review the physical server, see the respective vendor's documentation. |
KARS08318-I |
The message suppression function of the control port has started. (Storage node ID = xxx) [Event Name] Control port message suppression function start [Category] ControlPort |
KARS08319-I |
The message suppression function of the internode port has started. (Storage node ID = xxx) [Event Name] Internode port message suppression function start [Category] InternodePort |
KARS08320-I |
The message suppression function of the control port has stopped. The number of message suppressions is displayed. (Storage node ID = xxx, Number of suppressions = xxx) [Event Name] Control port message suppression function end [Category] ControlPort |
KARS08321-I |
The message suppression function of the internode port has stopped. The number of message suppressions is displayed. (Storage node ID = xxx, Number of suppressions = xxx) [Event Name] Internode port message suppression function end [Category] InternodePort |
KARS08322-E |
Control port link down was detected. The control port status is Error. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port link down [Category] ControlPort [Solution] A network failure has occurred on the target port of the MAC address where the failure has occurred. Follow the VSP One SDS Block and SDS Cloud Troubleshooting Reference to isolate and deal with network failures. For details about how to review the physical server, see the respective vendor's documentation. |
KARS08323-I |
Control port connection recovery was detected. The control port status is normal. (Storage node ID = xxx, Control port MAC address = xxx) [Event Name] Control port connection recovery [Category] ControlPort |
KARS08324-I |
Control port active port has switched. The control port status is normal. (Storage node ID = xxx, Control port (primary, secondary) MAC address = xxx, Active port = xxx) [Event Name] Control port active port change [Category] ControlPort |
KARS08325-I |
Internode port active port has switched. The internode port status is normal. (Storage node ID = xxx, Internode port (primary, secondary) MAC address = xxx, Active port = xxx) [Event Name] Internode port active port change [Category] InternodePort |
KARS08330-W |
Increase in TCP retransmission was detected in storage node TCP communication. (Storage node ID = xxx, Network type = xxx) [Event Name] Highly frequent TCP retransmission detected [Category] StorageNode [Solution] See the VSP One SDS Block and SDS Cloud Troubleshooting Reference and check for network failure or performance degradation (including network cable, network switch, or link failure, increased delay, increased packet loss, or connection at unexpected link speed or duplex), storage node or storage node communication destination failure (including physical servers, hypervisor, or NIC), or target resource failure in a cloud infrastructure. If there is any problem, troubleshoot it. If the same event log is not output 30 minutes after troubleshooting, the problem has been resolved. If the same event log is repeatedly output after the troubleshooting, collect dump files for each storage node, and then contact customer support. |
KARS08331-E |
Cloud infrastructure maintenance has been scheduled. A storage node affected by the maintenance is blocked. (Storage node ID = xxx) [Event Name] Cloud infrastructure maintenance detected [Category] StorageNode [Solution] If the storage node auto-recovery function is enabled, you do not need to take action because recovery is automatically performed after the cloud infrastructure maintenance is complete. If the storage node auto-recovery function is disabled, wait for a while, and then perform storage node maintenance recovery. |
KARS08332-W |
Cloud infrastructure maintenance is scheduled. Starting and recovery of a storage node affected by the maintenance are suppressed until the maintenance is complete. (Storage node ID = xxx) [Event Name] Suppression of starting and recovering a storage node started [Category] StorageNode [Solution] Verify that event log KARS08333-I (indicating that cloud infrastructure maintenance is complete) is output, and then take action according to the event log. If output of event log KARS08333-I cannot be confirmed after waiting for a while, take action according to the VSP One SDS Block and SDS Cloud Troubleshooting Reference. |
KARS08333-I |
Cloud infrastructure maintenance is complete, and therefore suppression of starting and recovering a storage node has been canceled. (Storage node ID = xxx) [Event Name] Suppression of starting and recovering a storage node canceled [Category] StorageNode [Solution] If event log KARS08331-E (indicating that the storage node is blocked because of cloud infrastructure maintenance) is output, take action according to the event log. If another message indicating a problem is output, take action according to the message. If no other message is output, no action is required. |
KARS08340-I |
Firewall settings are changed to suppress communication with the storage node to be blocked. (Storage node ID = xxx) [Event Name] Communication with the storage node to be blocked is suppressed [Category] StorageCluster |
KARS08341-I |
Firewall settings are changed to cancel suppression of communication with the storage node to be recovered. (Storage node ID = xxx) [Event Name] Suppression of communication with the storage node to be blocked is canceled [Category] StorageCluster |
KARS08342-E |
The storage node is blocked to avoid potentially adverse effects caused by cloud infrastructure maintenance. (Storage node ID = xxx) [Event Name] Cloud infrastructure maintenance is detected [Category] StorageNode [Solution] If the storage node auto-recovery function is enabled, you do not need to take action because recovery is automatically performed after cloud infrastructure maintenance is complete. If the storage node auto-recovery function is disabled, wait for a while, and then perform storage node maintenance recovery. |
KARS08350-E |
A hardware compatibility test resulted in failure because one or more control ports, internode ports, or compute ports have become unrecognizable. (Storage node ID = xxx, Job ID = xxx) [Event Name] Hardware compatibility test failed [Category] StorageNode [Solution] Follow the instructions of message KARS10116-E. |