Considerations for executing external volume commands at the same time

Universal Volume Manager User Guide

Version
9.8.6
Audience
anonymous
Part Number
MK-98RD9016-12

If you execute multiple commands for using external volumes at the same time from CCI, REST API, or Storage Advisor Embedded, the commands might fail or you might not obtain the expected result. To avoid this happening, we recommend executing commands in the following table one at a time for a storage system.

Command Type CCI command
Searching ports raidcom discover external_storage
Searching volumes raidcom discover lun
Testing iSCSI target login raidcom check external_iscsi_name
Searching iSCSI targets raidcom discover external_iscsi_name
Note: The following operations are not recommended. The command might not be executed correctly.
  • A single user executes multiple raidcom discover external_storage commands for a single storage system at the same time.
  • When multiple users use the same storage system, they execute one or more raidcom discover external_storage commands at the same time.

If you execute commands for using external volumes at the same time using CCI and an error occurs, take corrective action described in the following table.

Note: Similar symptoms might occur if you execute commands for external volumes at the same time from REST API or Storage Advisor Embedded.
CCI command When multiple commands are executed at the same time Description
  • raidcom discover external_storage
  • raidcom discover lun
  • The raidcom add path or raidcom delete path command fails with error codes EX_CMDRJE, (SSB1, SSB2): (2EDA, FEEC), (2EDA, FFFF), (2EDB, FFFF), (2EDB, FEEC)
  • The raidcom add external_grp command fails with error codes EX_CMDRJE, (SSB1, SSB2):(2EDA, FEEC), (2EDB, FEEC).
  • The raidcom delete external_grp command fails with error code EX_CMDRJE, (SSB1, SSB2): (2EDA, FFFF).

Cause: Multiple commands were executed at the same time.

Action: Wait a while, and then execute the failed commands one at a time. If this problem occurs again, contact customer support.

  • The external storage system cannot be displayed by the raidcom discover external_storage command.
  • LU of the external storage system cannot be displayed by the raidcom discover lun command.

Cause: Multiple commands were executed at the same time.

Action: Make sure that the configuration is correct. Wait a while, and then execute the failed commands one at a time. If this problem occurs again, contact customer support.

  • raidcom check external_iscsi_name
  • raidcom discover external_iscsi_name
  • The raidcom check external_iscsi_name command fails with error codes EX_CMDRJE, (SSB1, SSB2)=(2E11, 9B01), (2E14, 9B01), (2EBF, FEEC).
  • The raidcom discover external_iscsi_name command fails with error codes EX_CMDRJE, (SSB1, SSB2)=(2E11, 9B01), (2E114, 9B01), (2EBF, FEEC).

Cause: Multiple commands were executed at the same time.

Action: Wait a while, and then execute the failed commands one at a time. If this problem occurs again, contact customer support.

If you execute commands for using external volumes at the same time using REST API and an error occurs, take corrective action described in the following table. For details about REST API, see the document for REST API or Configuration Manager REST API.

REST API Corresponding CCI command Symptom
GET <base-URL> /v1/objects/storages/ <storage-device-ID>/external-storage-ports raidcom discover external_storage No external storage system is displayed.
GET <base-URL> /v1/objects/storages/ <storage-device-ID>/external-storage-luns raidcom discover lun No external storage system is displayed.
  • PUT <base-URL> /v1/objects/storages/ <storage-device-ID> /iscsi-ports/ <object-ID> /actions/discover/invoke
  • PUT <base-URL>/v1/objects/storages/ <storage-device-ID> /iscsi-ports/ <object-ID> /actions/check/invoke

raidcom discover external_iscsi_name

raidcom check external_iscsi_name

HTTP status code 503 (Service unavailable) is returned, or a message prompting the user to retry the operation appears.
  • PUT <base-URL> /v1/objects/storages/ <storage-device-ID> /external-path-groups/ <object-ID> /actions/add-path/invoke
  • PUT <base-URL>/v1/objects/storages/ <storage-device-ID> /external-path-groups/ <object-ID> /actions/remove-path/invoke

raidcom add path

raidcom delete path

HTTP status code 503 (Service unavailable) is returned, or a message prompting the user to retry the operation appears.
POST <base-URL> /v1/objects/storages/ <storage-device-ID> /external-parity-groups raidcom add external_grp HTTP status code 503 (Service unavailable) is returned, or a message prompting the user to retry the operation appears.
DELETE <base-URL> /v1/objects/storages/ <storage-device-ID> /external-parity-groups/ <object-ID> raidcom delete external_grp HTTP status code 503 (Service unavailable) is returned, or a message prompting the user to retry the operation appears.