The following table lists and describes the error messages displayed when session errors occur in raidcom commands. For details about other error messages returned by raidcom commands, see the Command Control Interface User and Reference Guide.
|
Error code |
Error message |
Description |
Action |
Return value |
|---|---|---|---|---|
|
EX_COMERR |
Can't communicate with HORC Manager. |
Communication with RAID Manager was failed. |
Wait 15 minutes or more, and then retry the command. If the error persists, reboot the ESM and retry the command. |
255 |
|
EX_ATTDBG |
Can't be attached to a Debug layer. |
CCI is starting. |
Wait for a while, and execute the command again. |
250 |
|
EX_ATTHOR |
Can't be attached to HORC Manager. |
CCI has not started. |
Confirm the storage system status is READY. Wait for 15 minutes and re-execute the command. If the error persists, reboot the ESM and retry the command. |
251 |
|
EX_ESSINV |
The session information is invalid. Log in again. |
Either of the following occurred:
|
Make the SSH connection again |
195 |
|
EX_ESNRDY |
This command cannot be executed in this session. Check if storage system is ready and log in again. |
You are trying to log in before the storage system has not fully started. |
Make the SSH connection after you confirmed that the storage system has started. |
196 |