Message ID |
Message |
|---|---|
KARS03000-E |
The compute node cannot be registered. [Cause] The number of registered compute nodes reached the maximum. [Solution] If you are a system administrator, reduce the number of compute nodes, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03001-E |
The compute node name cannot be registered. [Cause] The specified compute node name is already registered. [Solution] Specify another compute node name. |
KARS03002-E |
The request could not be executed. [Cause] The specified compute node could not be found. [Solution] Verify the specified compute node ID, and then retry the operation. When you are using a VPS, also verify the specified VPS ID. If the VPS ID was omitted, specify it, and then perform the operation. |
KARS03003-E |
The initiator cannot be registered. [Cause] The number of initiators per compute node reached the maximum. [Solution] Reduce the number of initiators per compute node, and then retry the operation. |
KARS03004-E |
The initiator name cannot be registered. [Cause] The specified initiator name is already registered. [Solution] Specify another initiator name. |
KARS03005-E |
The specified combination of the initiator and the compute port cannot be registered. [Cause] The specified combination of the initiator and the compute port is already registered. [Solution] Specify another combination of an initiator and a compute port. |
KARS03006-E |
The compute node path cannot be registered. [Cause] The number of registered compute node paths reached the maximum. [Solution] Reduce the number of compute node paths, and then retry the operation. |
KARS03007-E |
The request could not be executed. [Cause] The specified initiator could not be found. [Solution] Verify the specified initiator ID, and then retry the operation. When you are using a VPS, also verify the specified VPS ID. If the VPS ID was omitted, specify it, and then perform the operation. |
KARS03008-E |
The request could not be executed. [Cause] An unregistered compute port ID is specified. [Solution] Check the specified compute port ID, and then retry the operation. |
KARS03009-E |
The request could not be executed. [Cause] The specified volume could not be found. [Solution] Verify the specified volume ID, and then retry the operation. When you are using a VPS, also verify the specified VPS ID. If the VPS ID was omitted, specify it, and then perform the operation. |
KARS03010-E |
The request could not be executed. [Cause] An invalid value for LUN was specified. A value from 0 to 8191 can be specified. [Solution] Set a value within the range. |
KARS03011-E |
The volume path cannot be registered. [Cause] The number of registered volume paths reached the maximum in the compute node. [Solution] Reduce the number of volume paths in the compute node, and then retry the operation. |
KARS03012-E |
The request could not be executed. [Cause] A compute node ID that is not registered in the specified initiator was specified. [Solution] Check the compute nodes in the specified initiator. |
KARS03013-E |
The request could not be executed. [Cause] The compute node name is not specified. [Solution] Specify the compute node name. |
KARS03014-E |
The request could not be executed. [Cause] The initiator name is not specified. [Solution] Specify the initiator name. |
KARS03015-E |
The request could not be executed. [Cause] Characters or the number of characters used for the compute node name are not correct. [Solution] Enter a correct compute node name. |
KARS03016-E |
The request could not be executed. [Cause] Characters or the number of characters used for the initiator name are not correct. [Solution] Enter a correct initiator name. |
KARS03017-E |
The request could not be executed. [Cause] Characters or the number of characters used for the protocol name are not correct. [Solution] Enter a correct protocol name. |
KARS03018-E |
The request could not be executed. [Cause] Characters or the number of characters used for the OS type name are not correct. [Solution] Enter a correct OS type name. |
KARS03019-E |
The request could not be executed. [Cause] An invalid compute node ID was specified. [Solution] Check the specified compute node ID, and then retry the operation. |
KARS03020-E |
The request could not be executed. [Cause] An invalid initiator ID was specified. [Solution] Check the specified initiator ID, and then retry the operation. |
KARS03021-E |
The request could not be executed. [Cause] An invalid compute port ID was specified. [Solution] Check the specified compute port ID, and then retry the operation. |
KARS03022-E |
The request could not be executed. [Cause] An invalid volume ID was specified. [Solution] Check the specified volume ID, and then retry the operation. |
KARS03023-E |
The request could not be executed. [Cause] An unregistered protection domain ID was specified. [Solution] Check the specified protection domain ID, and then retry the operation. |
KARS03024-E |
The request could not be executed. [Cause] An unsupported protocol name was specified. [Solution] Specify a protocol name that is supported. |
KARS03025-E |
The request could not be executed. [Cause] The specified volume path could not be found. [Solution] Verify the specified volume path ID, and then retry the operation. When you are using a VPS, also verify the specified VPS ID. If the VPS ID was omitted, specify it, and then perform the operation. |
KARS03026-E |
The request could not be executed. [Cause] There is no compute node path that matches ID of the specified compute node, compute port, and initiator. [Solution] Check the specified IDs, and then retry the operation. |
KARS03027-E |
The request could not be executed. [Cause] The specified compute node cannot be deleted, because it is registered in the volume path. [Solution] Check the volume path in which the specified compute node is registered. |
KARS03028-E |
The request could not be executed. [Cause] The specified compute node ID cannot be deleted, because it is registered in the initiator. [Solution] Check the initiator in which the specified compute node is registered. |
KARS03029-E |
The request could not be executed. [Cause] The specified initiator cannot be deleted, because it is registered in the compute node path. [Solution] Check the compute node path in which the specified initiator is registered. |
KARS03030-E |
The request could not be executed. [Cause] The combination of the specified LUN and the compute node or volume and the compute node is already registered. [Solution] Specify another combination of a volume, an LUN or a compute node. |
KARS03031-E |
The request could not be executed. [Cause] The compute node ID is not specified. [Solution] Specify the compute node ID. |
KARS03032-E |
The request could not be executed. [Cause] The initiator ID is not specified. [Solution] Specify the initiator ID. |
KARS03033-E |
The request could not be executed. [Cause] The compute port ID is not specified. [Solution] Specify the compute port ID. |
KARS03034-E |
The request could not be executed. [Cause] The volume ID is not specified. [Solution] Specify the volume ID. |
KARS03035-E |
The request could not be executed. [Cause] The protection domain ID is not specified. [Solution] Specify the protection domain ID. |
KARS03036-E |
The request could not be executed. [Cause] The protocol name is not specified. [Solution] Specify the protocol name. |
KARS03037-E |
The request could not be executed. [Cause] The OS type name is not specified. [Solution] Specify the OS type name. |
KARS03038-E |
The request could not be executed. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, wait a while, and then retry the operation. If the error occurs again, collect the logs, and then contact customer support. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03039-E |
While xxx request processing, the port was blockaded. Because updating the configuration failed. [Event Name] Port blockade [Category] ComputeNode [Solution] Collect the logs, and then contact customer support. |
KARS03040-E |
The storage node was blocked because the memory could not be allocated. [Event Name] Port blockade [Category] ComputeNode [Solution] Collect the logs, and then contact customer support. |
KARS03041-E |
The request could not be executed. [Cause] The parameter to be edited is not specified. [Solution] Specify the parameter to be edited. |
KARS03042-E |
The request could not be executed. [Cause] A protocol parameter which is different from the compute port protocol was specified. [Solution] Specify the iSCSI parameter. |
KARS03043-E |
The request could not be executed. [Cause] A protocol parameter which is different from the compute port protocol was specified. [Solution] Specify the FC parameter. |
KARS03044-E |
The request could not be executed. [Cause] The existing nickname was specified. [Solution] Specify an unregistered nickname. |
KARS03045-E |
The request could not be executed. [Cause] The existing name was specified. [Solution] Specify an unregistered name. |
KARS03046-E |
The request could not be executed. [Cause] Another operation is in progress. [Solution] If you are a system administrator, wait until another operation is complete, and then retry the operation. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03047-E |
The request could not be executed. [Cause] There are volume paths mapped by the specified compute node. [Solution] Delete all volume paths mapped by the specified compute node. |
KARS03048-E |
While xxx request processing, all ports were blockaded. Because updating the configuration failed. [Event Name] Port blockade [Category] ComputeNode [Solution] Collect the logs, and then contact customer support. |
KARS03049-E |
The request could not be executed. [Cause] A registered SCSI reservation remains in the volume connected from the compute node path. [Solution] If you are a system administrator, unregister the SCSI reservation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03050-E |
The request could not be executed. [Cause] A registered SCSI reservation remains in the volume specified by the volume path. [Solution] If you are a system administrator, unregister the SCSI reservation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03051-E |
xxx request processing was aborted because update of configuration information failed. [Event Name] Internal error [Category] ComputeNode [Solution] Collect the logs, and then contact customer support. |
KARS03052-E |
The specified storage node cannot be removed because the path to the compute node is not redundant and therefore I/O might stop. (Storage node ID = xxx, Job ID = xxx) [Event Name] Verification prior to remove storage node [Category] ComputeNode [Solution] Add path information to the compute node for redundant configuration, and then retry the operation. |
KARS03053-E |
The specified storage node cannot be updated because the path to the compute node is not redundant and therefore I/O might stop during the update. (Storage node ID = xxx, Job ID = xxx) [Event Name] Verification prior to update storage node [Category] ComputeNode [Solution] Add path information to the compute node for redundant configuration, and then retry the operation. |
KARS03054-E |
xxx request processing was aborted because update of configuration information failed. (Job ID = xxx) [Event Name] Internal error [Category] ComputeNode [Solution] Collect the logs, and then contact customer support. |
KARS03055-I |
Internal reset started in the storage controller because an I/O slowdown was detected due to a temporary overload condition. (Storage controller ID = xxx) [Event Name] Internal reset started in the storage controller [Category] StorageNode [Solution] No action is required because the overload condition is temporary. However, if the same event log is repeatedly output in a short period of time, collect the logs, and then contact customer support. |
KARS03056-I |
Internal reset was completed in the storage controller. (Storage controller ID = xxx) [Event Name] Internal reset was completed in the storage controller [Category] StorageNode |
KARS03057-C |
Internal reset was not completed in the storage controller within the specified time. (Storage controller ID = xxx) [Event Name] Internal reset was not completed in the storage controller [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS03058-E |
The volume connected from the specified storage node cannot be removed because a registered SCSI reservation remains in the volume. (Storage node ID = xxx) [Event Name] Internal error [Category] ComputeNode [Solution] Unregister the SCSI reservation from the volume. |
KARS03059-E |
The request could not be executed. [Cause] A CHAP user ID is not specified. [Solution] Specify a CHAP user ID. |
KARS03060-E |
The request could not be executed. [Cause] A CHAP user name is not specified. [Solution] Specify a CHAP user name. |
KARS03061-E |
The request could not be executed. [Cause] A CHAP secret is not specified. [Solution] Specify a CHAP secret. |
KARS03063-E |
The request could not be executed. [Cause] An unregistered CHAP user ID was specified. [Solution] Check the specified CHAP user ID, and then retry the operation. |
KARS03064-E |
The request could not be executed. [Cause] CHAP user ID was specified that set specified compute port. [Solution] Check the specified chap user ID, and then retry the operation. |
KARS03065-E |
The request could not be executed. [Cause] An invalid CHAP user ID was specified. [Solution] Check the specified CHAP user ID, and then retry the operation. |
KARS03066-E |
The request could not be executed. [Cause] Specified CHAP user has already set specified compute port. [Solution] Check the specified CHAP user name, and then retry the operation. |
KARS03067-E |
The request could not be executed. [Cause] The specified CHAP user name already exists. [Solution] Verify the specified CHAP user name, and then retry the operation. |
KARS03068-E |
The CHAP user cannot be registered. [Cause] The number of registered CHAP users reached the maximum. [Solution] Reduce the number of CHAP users, and then retry the operation. |
KARS03069-E |
The CHAP user cannot be registered to specified compute port. [Cause] The number of registered CHAP users to specified compute port reached the maximum. [Solution] Reduce the number of CHAP users from specified compute port, and then retry the operation. |
KARS03070-E |
The request could not be executed. [Cause] CHAP user ID was specified that does not set compute port. [Solution] Check the specified compute port ID and chap user ID, and then retry the operation. |
KARS03071-E |
The request could not be executed. [Cause] Mutual CHAP user or mutual secret does not specified. [Solution] Specified both mutual CHAP user name and mutual secret, and then retry the operation. |
KARS03072-E |
The request could not be executed. [Cause] iSNS server address does not specified. [Solution] To enable the iSNS client function, retry the operation with the IP address of the iSNS server specified. |
KARS03073-E |
The request could not be executed. [Cause] The specified name cannot be registered because it might be an existent default name. [Solution] Specify a different name. |
KARS03074-E |
The specified volume cannot be deleted because it is connected to the volume path. (Volume ID = xxx) [Event Name] The volume could not be deleted. (Volume path check) [Category] VolumePath [Solution] Disconnect the volume path from the specified volume, and then retry the operation. |
KARS03075-W |
The FC port with the physical WWN installed on the storage node could not be initialized. (Storage node ID = xxx, Physical WWN = xxx) [Event Name] FC port initialization error [Category] ComputePort [Solution] If the status of the compute port indicates an error, perform maintenance blocking of the faulty storage node, stop and restart the physical server, and then perform maintenance recovery of the faulty storage node. If the problem persists, replace the FC adapter. |
KARS03076-E |
The number of FC ports detected on the storage node does not match the configuration. (Storage node ID = xxx) [Event Name] FC port excess or deficiency detection [Category] ComputePort [Solution] Verify the configuration of the storage node. |
KARS03077-W |
An H/W error was detected at the FC port with the physical WWN installed on the storage node. (Storage node ID = xxx, Physical WWN = xxx) [Event Name] FC port H/W error [Category] ComputePort [Solution] If this event occurs repeatedly, replace the FC adapter. |
KARS03078-I |
Reset of the FC port with the physical WWN installed on the storage node has been completed. (Storage node ID = xxx, Physical WWN = xxx) [Event Name] FC port H/W reset completed [Category] ComputePort |
KARS03079-E |
No SFP or an unsupported SFP was detected at the FC port with the physical WWN installed on the storage node. (Storage node ID = xxx, Physical WWN = xxx) [Event Name] No SFP or unsupported SFP detected [Category] ComputePort [Solution] Install a supported SFP. |
KARS03080-E |
The request could not be executed. [Cause] The specified initiator and compute port protocol parameters are different. [Solution] Retry the operation with the same value specified for the initiator protocol and the compute port protocol. |
KARS03081-E |
The compute port could not be updated. (Compute port ID = xxx) [Event Name] Updating of the compute port ended abnormally [Category] ComputePort [Solution] If an event log indicating another problem is issued, correct the problem, and then retry the operation. If the error persists, replace the storage node. |
KARS03082-E |
The specified parameter contains an invalid value. [Event Name] The compute port could not be updated due to an invalid parameter [Category] ComputePort [Solution] Verify the parameter settings, and then retry the operation. |
KARS03083-E |
The request could not be executed. [Cause] The network address cannot be specified as the IPv4 default gateway address. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03084-E |
The request could not be executed. [Cause] The specified IPv6 global address cannot be registered because it is the same as the IPv6 link local address. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03085-E |
The request could not be executed. [Cause] IPv6 subnet prefix length cannot be specified as 0. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03088-E |
The request could not be executed. [Cause] The broadcast address cannot be specified as the IPv4 default gateway address. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03089-E |
The request could not be executed. [Cause] The loopback address cannot be specified as the IPv4 default gateway address. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03090-E |
After adding the storage node, the compute node path could not be updated. (Initiator ID = xxx, Compute port ID = xxx, Job ID = xxx) [Event Name] After adding the storage node, update of the compute node path ended abnormally [Category] ComputeNodePath [Solution] If the status of the compute port is other than ERROR, retry the operation. If the status of the compute port is ERROR, perform maintenance blocking, stopping and restarting of the physical server, and maintenance recovery for the storage node on which the target compute port exists, and then retry the operation. |
KARS03091-E |
The request could not be executed. [Cause] Duplicated IP address is specified. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03092-E |
The volume path cannot be registered. [Cause] The number of registered volume paths reached the maximum in the storage cluster. [Solution] If you are a system administrator, reduce the number of volume paths in the storage cluster, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03093-I |
Link is down in a compute port during maintenance mode. [Event Name] Access restricted during FC compute port connection in maintenance mode [Category] ComputeNodePath [Solution] Before link goes up, release the compute port from maintenance mode. |
KARS03094-E |
The request could not be executed. [Cause] A registered SCSI reservation remains in the volume specified by the volume path. [Solution] If you are a system administrator, see the event logs with Message ID KARS03095-E, and then cancel the SCSI reservation setting. If the operation was performed by a VPS administrator, report the message contents to the system administrator. |
KARS03095-E |
A registered SCSI reservation remains in the volume specified by the volume path. (Job ID = xxx, Compute node ID = xxx, Volume ID = xxx) [Event Name] Volume path deletion restricted for the volume with SCSI reservation setting [Category] VolumePath [Solution] Unregister the SCSI reservation. |
KARS03096-E |
The request could not be executed. [Cause] The specified compute node cannot be changed or deleted because it is connected with the volume path with the SCSI reservation setting. [Solution] If you are a system administrator, see the event logs with Message ID KARS03097-E, and then cancel the SCSI reservation setting. If the operation was performed by a VPS administrator, report the message contents to the system administrator. |
KARS03097-E |
The specified compute node cannot be changed or deleted, because it is connected with the volume path with the SCSI reservation setting. (Job ID = xxx, Compute node ID = xxx, Volume ID = xxx) [Event Name] Deletion restricted for compute node connected with volume path with SCSI reservation setting [Category] ComputeNode [Solution] Unregister the SCSI reservation. |
KARS03098-E |
The volume path cannot be registered. [Cause] The volume registration might have not succeeded due to a storage failure. [Solution] If you are a system administrator and an event log indicating another problem is issued, correct the problem, and then retry the operation. If the phenomenon persists, recover by replacing the storage node. If the phenomenon persists, recover by replacing the storage node. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03099-E |
The volume path cannot be deleted. [Cause] The volume deletion might have not succeeded due to a storage failure. [Solution] If you are a system administrator and an event log indicating another problem is issued, correct the problem, and then retry the operation. If the phenomenon persists, recover by replacing the storage node. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03100-E |
The request could not be executed. [Cause] The combination of isMutualChapAuth and authMode is invalid. When you enable isMutualChapAuth, authMode must be CHAP. [Solution] When you enable isMutualChapAuth, authMode must be CHAP. If you specified NONE or CHAPComplyingWithInitiatorSetting for authMode, isMutualChapAuth must be disabled. |
KARS03101-E |
The request could not be executed. [Cause] The combination of the specified parameters is invalid. [Solution] Review the parameter combination and re-execute. |
KARS03102-E |
The request could not be executed. [Cause] An invalid value for IPv4 subnet mask was specified. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03103-E |
Data migration is not being performed in the specified protection domain. (Protection domain ID = xxx) [Event Name] No data migration to be stopped [Category] Migration [Solution] Verify the specified protection domain, and then retry the operation. |
KARS03104-E |
Initiator node does not exist in the specified protection domain. (Protection domain ID = xxx) [Event Name] Nothing initiator node [Category] Migration [Solution] Verify the specified protection domain, and then retry the operation. |
KARS03105-E |
The request could not be executed. [Cause] A compute node ID in which the initiator is not registered was specified. [Solution] Verify the specified compute node. |
KARS03107-E |
The request could not be executed. [Cause] The number of volume paths for which LUNs (equal to or greater than startLun) can be specified is insufficient for the number of specified volumes. (Compute node ID = xxx) [Solution] Review the volume path configuration of the displayed compute node, reduce the number of registered volume paths or change startLun, and then retry the operation. |
KARS03108-E |
The request could not be executed. [Cause] In some compute nodes, the number of volume paths for which LUNs (equal to or greater than startLun) can be specified is insufficient for the number of specified volumes. (Compute node ID = xxx) [Solution] Review the volume path configuration of each specified compute node, reduce the number of registered volume paths or change startLun, and then retry the operation. |
KARS03109-E |
The request could not be executed. [Cause] The number of volume paths that can be registered is insufficient for the combination of specified startLun and volumes. [Solution] Review the combination of startLun and volumes, and then retry the operation. |
KARS03110-E |
Registration of the volume path was aborted. [Cause] A request to abort the volume path registration was detected. [Solution] If you are a system administrator, see the event logs, confirm that no job is running, and then retry the operation. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03111-E |
Deletion of the volume path was aborted. [Cause] A request to abort the volume path deletion was detected. [Solution] If you are a system administrator, see the event logs, confirm that no job is running, and then retry the operation. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03112-E |
The compute node path cannot be registered. [Cause] The number of registered compute node paths to the specified compute port has reached the maximum. [Solution] If you are a system administrator, reduce the number of registered compute node paths to the specified compute port, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03113-E |
The request could not be executed. [Cause] The number of volume paths in the compute node that can be registered is insufficient for the combination of specified compute nodes and volumes. (Compute node ID = xxx) [Solution] Verify the parameter settings, and then retry the operation. |
KARS03114-E |
The request could not be executed. [Cause] The operation cannot be performed because the number of volume paths that can be registered on the protection domain is exceeded with the combination of the specified compute node and the volume. [Solution] If you are a system administrator, verify the parameter settings, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS03115-E |
The compute node path cannot be registered. [Cause] The compute port on the initiator node cannot be specified. [Solution] Verify the parameter settings, and then retry the operation. |
KARS03116-W |
I/O paths to a storage node for which maintenance recovery performed may not be recovered to ONLINE due to temporary blockage of another storage node occurred while processing maintenance recovery for the storage node. (Storage node ID = xxx) [Event Name] The problem of I/O paths recovery on storage node maintenance recovery [Category] VolumePath [Solution] If I/O paths to a storage node for which maintenance recovery performed are not recovered to ONLINE after maintenance recovery, perform maintenance blockage and maintenance recovery for the storage node. |
KARS03117-E |
The volume path cannot be registered. [Cause] The data volume reduction status of the volume for which the volume path is created may have failed due to Failed. [Solution] If you are a system administrator and an event log indicating another problem is issued, correct the problem, and then retry the operation. If the same error occurs, collect the logs, and then contact the contact information provided in the manual. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS03118-E |
A failure was detected in a compute port installed on the storage node. (Storage node ID = xxx, Compute port MAC address = xxx) [Event Name] Compute port failure detected [Category] ComputePort [Solution] If the status of the compute port indicates an error, perform maintenance blocking of the faulty storage node, stop and restart the physical server, and then perform maintenance recovery of the faulty storage node. If the problem persists, replace the NIC of the compute port. |
KARS03119-E |
The request could not be executed. [Cause] Link down occurred in the specified compute port. [Solution] Link up the compute port, wait for a while, and then retry the operation. |
KARS03120-E |
The request could not be executed. [Cause] The maximum number of initiators that can be registered in the VPS to which the initiators belong has been reached. [Solution] Reduce the number of registered initiators, and then retry the operation. |
KARS03121-E |
The request could not be executed. [Cause] The maximum number of volume paths that can be registered in the VPS to which the volume paths belong has been reached. [Solution] Reduce the number of registered volume paths, and then retry the operation. |
KARS03122-E |
The request could not be executed. [Cause] The maximum number of compute nodes that can be registered in the VPS to which the compute nodes belong has been reached. [Solution] Reduce the number of registered compute nodes, and then retry the operation. |
KARS03123-E |
The request could not be executed. [Cause] The maximum number of volume paths that can be registered in the VPS to which the volume paths belong is exceeded for the specified combination of compute node and volume. Therefore, this operation cannot be performed. [Solution] Review the parameter settings, and then retry the operation. |
KARS03124-E |
A compute node path could not be added after storage node addition. (VPS ID = xxx, Compute node ID = xxx, Compute port ID = xxx) [Event Name] Compute node path addition ended abnormally after storage node addition [Category] ComputeNodePath [Solution] If the status of the compute port is ERROR, perform maintenance blocking, stopping and restarting of a physical server, and node maintenance recovery for the storage node on which the target compute port exists. Then, if the status of the compute port is other than ERROR, ask a VPS administrator to create a compute node path for the compute node indicated in the error message. |
KARS03125-E |
The request could not be executed. [Cause] Volume path operation for volumes of the MigrationDestination type is not possible. (Volume ID = xxx) [Solution] Review the specified volume, and then retry the operation. |
KARS03126-W |
Compute port link down was detected. (Storage node ID = xxx, Compute port ID = xxx) [Event Name] Compute port link down [Category] ComputePort |
KARS03127-I |
Compute port link up was detected. (Storage node ID = xxx, Compute port ID = xxx) [Event Name] Compute port link up [Category] ComputePort |
KARS03128-E |
A compute node path could not be added after storage node addition. (VPS ID = xxx, Compute node ID = xxx, Compute port ID = xxx) [Event Name] Compute node path addition ended abnormally after storage node addition [Category] ComputeNodePath [Solution] Ask a VPS administrator to create a compute node path for the compute node indicated in the error message. |
KARS03129-E |
A compute node path could not be added after storage node addition. (Initiator ID = xxx, Compute port ID = xxx, Job ID = xxx) [Event Name] Compute node path addition ended abnormally after storage node addition [Category] ComputeNodePath [Solution] Retry compute node path addition. |
KARS03130-E |
The request could not be executed. [Cause] A protocol name is not specified. [Solution] Specify a protocol name. |
KARS03131-E |
The request could not be executed. [Cause] An invalid protocol name was specified. [Solution] Specify a compute port protocol name that can be changed. |
KARS03132-E |
The request could not be executed. [Cause] The specified protocol has already been set. [Solution] Review the current compute port protocol and the specified protocol, and then retry the operation. |
KARS03133-E |
The request could not be executed. [Cause] Compute nodes have been registered. [Solution] Delete all the registered compute nodes, and then retry the operation. |
KARS03134-I |
Preparation for changing the compute port protocol has been completed. [Event Name] Preparation for changing the compute port protocol completed [Category] ComputePort [Solution] Restart the storage cluster. |
KARS03135-E |
The compute port protocol could not be changed. [Event Name] Compute port protocol change ended abnormally [Category] ComputePort [Solution] Delete all the registered compute nodes, and then retry the compute port protocol change. |
KARS03136-I |
Compute port protocol change has been completed. [Event Name] Compute port protocol change completed [Category] ComputePort |
KARS03137-I |
Compute port protocol change was canceled because of software update. [Event Name] Compute port protocol change canceled [Category] ComputePort [Solution] See the event logs, verify that software update is not in progress, and then retry the compute port protocol change. |
KARS03138-E |
The request could not be executed. [Cause] Processing cannot be performed because compute ports with the NVMe/TCP protocol exist. [Solution] Configure a storage cluster by using the iSCSI protocol. |
KARS03139-E |
The request could not be executed. [Cause] The specified parameter is not applicable for the protocol of a compute port. [Solution] Specify an NVMe/TCP parameter. |
KARS03140-E |
The request could not be executed. [Cause] The operation may have been unsuccessful because of a failure or maintenance operation. [Solution] If an event log indicating another problem is issued, correct the problem, and then retry the compute port protocol change. If maintenance operation is being performed, wait until it is complete, and then retry the compute port protocol change. If the same error occurs, collect the logs, and then contact customer support. |
KARS03141-E |
The compute port protocol could not be changed. [Event Name] Compute port protocol change ended abnormally [Category] ComputePort [Solution] If an event log indicating another problem is issued, correct the problem, and then retry the compute port protocol change. If maintenance operation is being performed, wait until it is complete, and then retry the compute port protocol change. If the same error occurs, collect the logs, and then contact customer support. |
KARS03143-E |
The request could not be executed. [Cause] CHAP users remain or there are compute ports for which CHAP authentication is enabled. [Solution] Delete all the CHAP users, disable the authentication scheme for all the compute ports, and then retry the compute port protocol change. |
KARS03144-E |
The request could not be executed. [Cause] Compute ports for which the iSNS client function is enabled exist. [Solution] Disable the iSNS client function for all the compute ports, and then retry the compute port protocol change. |
KARS03145-E |
The compute port protocol could not be changed. [Event Name] Compute port protocol change ended abnormally [Category] ComputePort [Solution] Delete all the CHAP users, disable the authentication scheme for all the compute ports, and then retry the compute port protocol change. |
KARS03146-E |
The compute port protocol could not be changed. [Event Name] Compute port protocol change ended abnormally [Category] ComputePort [Solution] Disable the iSNS client function for all the compute ports, and then retry the compute port protocol change. |
KARS03147-E |
The request could not be executed. [Cause] Compute ports are configured by using a protocol that does not support the function for changing a compute port protocol. |
KARS03148-E |
The request could not be executed. [Cause] An unsupported OS was specified. [Solution] Specify a supported OS. |