You can use the Command Control Interface (CCI) operation logs to troubleshoot ShadowImage (SI) operations. The following procedure describes CCI error codes and how to locate and interpret them.
- Open one of the following:
- The CCI window
- The CCI operation log file
- In the log that is displayed, locate the log entry or error code you are investigating. You can use the SSB1/SSB2 error code combination to determine the cause of the error. The error codes are shown to the right of the equal symbol (=) in the log. The SSB1 code is the last four alphanumeric characters to the left of the comma (,). The SSB2 code is the last four alphanumeric characters to the right of the comma (,).
- CCI window sample log entry:
It was rejected due to SKEY=0x05, ASC=0x20,SSB=0xB9E1,0xB901 on Serial#(64015)
SSB1 code: B9E1
SSB2 code: B901
- CCI operation log file sample error code:
11:06:03-37897-10413- SSB = 0xb9a0,2089
SSB1 code: B9A0
SSB2 code: 2089
- CCI window sample log entry:
- Locate the description of the SSB2 error code in the following table.
For details about errors that are not listed in this table, contact customer support.
SSB2 error codes for ShadowImage: SSB1 = 2E31, B9A0, B9A1, B9A2, B9A5, B9A6, B9AE, and B9AF
|
Error code (SSB2) |
Description |
|---|---|
|
- |
An error occurred during an SI pair task. |
|
0C94 |
The SI pair operation cannot be performed because the data reduction shared volume specified as the P-VOL is currently unavailable. |
|
0C95 |
The SI pair operation cannot be performed because the data reduction shared volume specified as the S-VOL is currently unavailable. |
|
0CC6 |
Pair creation was rejected because both the P-VOL and the S-VOL specified for the pair to be created have the vClone Parent attribute or the vClone attribute. |
|
0CC7 |
Pair creation was rejected because a volume being used in a ShadowImage pair or a Volume Migration pair exists in the Thin Image Advanced family containing the volumes specified for the pair to be created. |
|
0CCD |
Pair creation was rejected because the volumes in the ShadowImage pair or the Volume Migration pair (associated with the volume which is specified for the pair to be created) already contain a volume with the vClone Parent attribute or the vClone attribute. |
|
200D |
The pair task was rejected because the specified DP-VOL is not associated with a pool. |
|
201B |
The CTG pair-split was rejected because the UR pair is other than PAIR, PSUS, or PSUE. The UR S-VOL was the SI P-VOL included in the CTG on which the pair-split is being performed. |
|
2026 |
The Quick Restore operation was rejected because the cache mode of the specified P-VOL is different from the cache mode of the external S-VOL. |
|
202D |
The pair task was rejected because one of the following conditions applies to the P-VOL:
|
|
202E |
The pair task was rejected because one of the following conditions applies to the S-VOL:
|
|
2036 |
The pair task was rejected because the global-active device quorum disk was specified as the SI P-VOL. |
|
2037 |
The pair task was rejected because the global-active device quorum disk was specified as the SI S-VOL. |
| 2038 | The operation failed because multiple GAD pairs had been created by using the SI P-VOL. |
|
2043 |
The volume you specified as a P-VOL was a volume using two mirrors included in a 3-UR-DC multi-target or cascade configuration. The operation was rejected because the volume was used as a UR delta resync or data volume. |
|
2044 |
The volume you specified as an S-VOL was a volume using two mirrors included in a 3-UR-DC multi-target or cascade configuration. The operation was rejected because the volume was used as a UR delta resync or data volume. |
|
2047 |
The pair task was rejected because the current firmware version does not support the specified P-VOL capacity. |
|
2048 |
The pair task was rejected because the current firmware version does not support the specified S-VOL capacity. |
|
204F |
The pair task was rejected because the volume you specified as the S-VOL is a migration source volume of Volume Migration and migration processing of Volume Migration cannot be interrupted at the moment. Retry the pair task after the migration processing of Volume Migration is completed. |
|
205B |
The pair was not created because the specified MU number is in use. |
|
2060 |
The volume you specified as an SI P-VOL was a volume of a UR pair. The pair task was rejected because the status of the UR pair is not in the required status. |
|
2061 |
The volume you specified as an SI S-VOL was a volume of a UR pair. The pair task was rejected because the status of the UR pair is not in the required status. |
|
2067 |
Volumes of the specified pair are shared by TC and UR.
|
|
206d |
The Quick Restore operation was rejected because the volume you specified as the P-VOL is used as a volume for a GAD pair, and it is the migration source volume of Volume Migration. |
|
206f |
The Quick Restore operation was rejected because the volume you specified as the P-VOL is used as a volume for a GAD pair, and a new GAD pair is being created or resynchronized. |
|
2071 |
The pair task was rejected because the volume you specified as the P-VOL is a migration source volume of Volume Migration and migration processing of Volume Migration cannot be interrupted at the moment. Retry the pair task after the migration processing of Volume Migration is completed. |
|
2072 |
The pair task was rejected because of one of the following reasons:
|
|
2073 |
The pair task was rejected because of one of the following reasons:
|
|
2077 |
The Quick Restore operation was rejected because the volume you specified as the P-VOL is used as a volume for a GAD pair, and the volume attribute (VOL_ATTR in the raidcom get ldev command) of the S-VOL of the GAD pair is different from that of the S-VOL of a ShadowImage pair. |
|
2078 |
Because the specified P-VOL was also a UR P-VOL for delta resync, one of the following errors occurred:
|
|
2079 |
The pair task was rejected because the specified S-VOL was also a UR P-VOL for delta resync. |
|
2086 |
The pair task was rejected because the initialization process is being performed. |
|
2089 |
The Quick Restore operation was rejected because you are formatting the volume you specified as a P-VOL using Quick Format. For more information about formatting volumes using Quick Format, see the Provisioning Guide. |
|
208A |
The Quick Restore operation was rejected because you are formatting the volume you specified as an S-VOL using Quick Format. For more information about formatting volumes using Quick Format, see the Provisioning Guide. |
|
2093 |
The pair task was rejected because the T10 PI attributes for the P-VOL and S-VOL do not match. |
|
2097 |
The Quick Restore operation was rejected for one of the following reasons:
|
|
20A2 |
The create pair task was rejected because the P-VOL is a DP-VOL for which the capacity is increasing. |
|
20A3 |
The pair was not created because the S-VOL is a DP-VOL for which capacity is increasing. |
|
20A4 |
(VSP One B85) The pair operation was rejected because the volume you specified as the P-VOL is an external volume enabled with the Data Direct Mapping attribute. External volumes enabled with the Data Direct Mapping attribute can be used only as pool volumes. (VSP One B20 series) The pair operation was rejected because you specified either of the following volumes for the P-VOL:
These volumes can only be used as the pool volume. |
|
20A7 |
(VSP One B85) The pair operation was rejected because the volume you specified as the S-VOL is an external volume enabled with the Data Direct Mapping attribute. External volumes enabled with the Data Direct Mapping attribute can be used only as pool volumes. (VSP One B20 series) The pair operation was rejected because you specified either of the following volumes for the S-VOL:
These volumes can only be used as the pool volume. |
|
20A9 |
The pair task was rejected because the specified CTG ID is being used in TIA. |
|
20B0 |
The pair task was rejected because the volume you specified as the P-VOL is a DP-VOL and its capacity is increasing. |
|
20B1 |
The pair task was rejected because the volume you specified as the S-VOL is a DP-VOL and its capacity is increasing. |
|
20B4 |
The pair task was rejected because the volume you specified as the P-VOL is a DP-VOL that is not associated with a pool. |
|
20B5 |
The pair task was rejected because the volume you specified as the S-VOL is a DP-VOL that is not associated with a pool. |
|
20B7 |
The pair task was rejected because an LU path or a namespace on the NVM subsystem with an NVM subsystem port added is not defined to the volume you specified as the P-VOL. |
|
20B8 |
The pair task was rejected because an LU path or a namespace on the NVM subsystem with an NVM subsystem port added is not defined to the volume you specified as S-VOL. |
| 20C3 |
The pair task was rejected because the volume you specified as the P-VOL is a deduplication system data volume. |
| 20C4 |
The pair task was rejected because the volume you specified as the S-VOL is a deduplication system data volume. |
|
20C5 |
The command was rejected because you were in the process of turning off the storage system's power. |
|
20D0 |
The P-VOL rejected the paircreate CCI command because the DP pool is initializing in the DP-VOL. |
|
20D1 |
The S-VOL rejected the paircreate CCI command because the DP pool is initializing in the DP-VOL. |
|
20DD |
The specified consistency group ID cannot be used for ShadowImage because it is being used for ShadowImage for Mainframe. |
|
20DF |
The volume that was specified as the S-VOL cannot be used because the volume is undergoing online data migration. |
|
20E9 |
The pair task was rejected because the volume you specified as the P-VOL is a S-VOL for an existing pair, and the volume you specified as the S-VOL is the P-VOL for another existing pair. |
|
20EC |
The volume which was specified as the P-VOL cannot be used, because the volume is undergoing online data migration and Cache Through is specified as the cache mode. |
|
20F2 |
The pair task was rejected because the physical serial numbers of the corresponding storage systems do not match, even if the virtual serial numbers match, when the serial numbers of the virtual storage machines are specified for the P-VOL and S-VOL. |
|
20F4 |
The pair task was rejected for the volume specified as the P-VOL because either the device model and serial number or the virtual LDEV ID for the virtual storage machine is being changed. |
|
20F5 |
The pair task was rejected for the volume specified as the S-VOL because either the device model and serial number or the virtual LDEV ID for the virtual storage machine is being changed. |
|
20F6 |
The pair creation was rejected because one of the following applied to the volume specified as the P-VOL.
|
|
20F7 |
The pair operation was rejected because one of the following applied to the volume specified as the P-VOL.
|
|
20F8 |
The pair task was rejected for the volume specified as the S-VOL because the volume is undergoing online data migration. |
|
20FC |
The command was rejected because the volume specified as the P-VOL is undergoing online data migration and the command is for creating a third pair. |
|
2301 |
The pair task was rejected because there is not a sufficient amount of installed shared memory or SI is not installed. |
|
2306 |
The pair task was rejected because the LBA size of the specified P-VOL is not the same as the size of the specified S-VOL. |
|
2309 |
The pair was not created because the number of pairs exceeded the maximum number of pairs. |
|
230A |
The pair was not created because the volume you specified as the S-VOL is the P-VOL of the SI pair that has an MU number of 0. |
|
230B |
The pair task was rejected because the pair is being suspended or deleted. |
|
2310 |
One of the following occurred:
|
|
2314 |
The pair was not created because the volume you specified as the S-VOL is the S-VOL of another pair that has been split (PSUS status). |
|
2322 |
The pair task was rejected because there is not a sufficient amount of installed shared memory or initialization is not completed. |
|
2324 |
The pair task was rejected because the number of slots of the volume you specified as the P-VOL exceeded the upper limit. |
|
2325 |
The pair task was rejected because the number of slots of the volume you specified as the S-VOL exceeded the upper limit. |
|
2326 |
The pair was not created because the volume you specified as the P-VOL had already had three S-VOLs. |
|
2327 |
The pair was not created because the node volume specified as the P-VOL had already had two S-VOLs. |
|
2328 |
The pair task was rejected because the pair configuration exceeded the number of the layers of the cascade configuration. |
|
2329 |
The pair task was rejected because the volume you specified as the S-VOL is the S-VOL of an existing pair. |
|
232A |
The pair was not created because pairs that would exceed the license capacity were going to be created. |
|
232F |
The pair task was rejected because the volume you specified as the P-VOL is allocated as the destination of the Volume Migration. |
|
2331 |
The pair task was rejected because the capacity of the specified P-VOL is not the same as the capacity of the S-VOL. |
|
2332 |
The pair was not created because the volume you specified as the P-VOL had already had three S-VOLs. |
|
2333 |
The pair task was rejected because the volume you specified as the P-VOL is not the P-VOL of the existing pair. |
|
2334 |
One of the following occurred:
|
|
2335 |
The pair task was rejected because the volume specified as the S-VOL cannot be operated using CCI due to the emulation type of the volume. |
|
2336 |
The pair task was rejected because the emulation type of the specified P-VOL and that of the S-VOL do not match. |
|
2337 |
The pair task was rejected because the volume specified as the P-VOL is an intermediate volume. |
|
233A |
The pairresync CCI command was rejected because the volume you specified as the P-VOL is not an SI P-VOL. |
|
233B |
The pair task was rejected because the volume you specified as the S-VOL is a root volume. |
|
233C |
The pair task was rejected because the volume you specified as the S-VOL is a node volume, and the volume you specified as the P-VOL is not the P-VOL for the specified S-VOL. |
|
233D |
The pairsplit CCI command was rejected because the specified P-VOL and S-VOLs were a L2 pair, and the L1 pair is not split (PSUS status). |
|
233E |
The pair task was rejected because the volume you specified as the P-VOL is being used as a TC P-VOL. |
|
233F |
The pair task was rejected because the volume you specified as the S-VOL is a TC P-VOL, and the pair is not split (PSUS status) or suspended (PSUE status). |
|
2342 |
The pair task was rejected because the volume you specified as the S-VOL is the destination of the Volume Migration. |
|
2343 |
The pair was not created because the volume you specified as the S-VOL had already been an S-VOL. |
|
2344 |
The pair task was rejected because the volume you specified as the S-VOL for SI pair tasks is not an S-VOL. |
|
2346 |
The volume you specified as an SI S-VOL is a TC P-VOL. The pair task was rejected because the TC pair is not in the required status. |
|
2347 |
The volume you specified as an SI S-VOL was a TC S-VOL. The pair task was rejected because the TC pair is not in the required status. |
|
234A |
Creation of the cascaded pair was rejected because the volume specified as the S-VOL is an intermediate volume. |
|
234B |
The pair task was rejected because the volume you specified as the S-VOL is the volume of the Volume Migration. |
|
234C |
The pair task was rejected because the volume you specified as the P-VOL is a deduplication system data volume (Data Store). |
|
234D |
The pair task was rejected because the volume you specified as the S-VOL is a deduplication system data volume (Data Store). |
|
2350 |
The pair task was rejected because the specified P-VOL and the S-VOL for SI pair tasks is not a pair. |
|
2351 |
The pair task was rejected because the volume you specified as the P-VOL and the volume you specified as the S-VOL are the same. |
|
2352 |
The pair was not restored because the specified P-VOL and S-VOLs is online to the host. |
|
2353 |
The pair was not deleted because the specified P-VOL and S-VOLs are in the process of being Quick Split. |
|
2354 |
The pairresync CCI command was rejected because the P-VOL and S-VOLs is in the process of being Steady Split. |
|
2357 |
The pair creation was rejected because the volume you specified as the S-VOL is the P-VOL of the pair you are splitting or the P-VOL of the pair you are reverse resynchronizing. |
|
2358 |
The pairresync CCI command was rejected because the volume you specified as the S-VOL is the P-VOL of the splitting pair. |
|
235B |
The volume you specified as a P-VOL is a TC P-VOL. The reverse resynchronization was rejected because the TC pair is not suspended (PSUE status) or split (PSUS status). |
|
235C |
The volume you specified as the P-VOL is a TC S-VOL. The reverse resynchronization was rejected because the TC pair is not suspended (PSUE status) or split (PSUS status). |
|
235D |
The volume you specified as an S-VOL is a TC P-VOL. The reverse resynchronization was rejected because the TC pair is not suspended (PSUE status) or split (PSUS status). |
|
236C |
The reverse resynchronization was rejected because the volume you specified as the P-VOL has the S-VOL Disable attribute assigned by the Data Retention Utility. |
|
236D |
The pair task was rejected because the volume you specified as the S-VOL has the S-VOL Disable attribute assigned by the Data Retention Utility. |
|
2370 |
The pair task was rejected because the volume you specified as the P-VOL is not mounted. |
|
2371 |
The pair task was rejected due to one of the following reasons:
|
|
2372 |
The pair task was rejected because the volume you specified as the P-VOL is being formatted or shredded. |
|
2373 |
The pair task was rejected because the volume you specified as the P-VOL is a command device. |
|
2380 |
The pair task was rejected because of one of the following reasons:
|
|
2381 |
The pair task was rejected due to one of the following reasons:
|
|
2382 |
The pair task was rejected because the volume you specified as the S-VOL is being formatted or shredded. |
|
2383 |
The pair task was rejected because the volume you specified as the S-VOL is a command device. |
|
2387 |
The pair was not created because the volume you specified as the P-VOL is the volume for Volume Migration. |
| 2390 |
(VSP One B20 series) The Quick Restore operation was rejected because the volume specified as the P-VOL is a V-VOL for which capacity saving is enabled. (VSP One B85) The Quick Restore operation was rejected because the volume specified as the P-VOL is a DRS-VOL. |
| 2391 |
(VSP One B20 series) The Quick Restore operation was rejected because the volume specified as the S-VOL is a V-VOL for which capacity saving is enabled. (VSP One B85) The Quick Restore operation was rejected because the volume specified as the S-VOL is a DRS-VOL. |
|
2394 |
The pair was not registered in the CTG because the number of the pairs assigned to the CTG has exceeded the defined maximum number of pairs. |
|
2395 |
The pair task was rejected because you are reverse resynchronizing the pair sharing the specified volume as the P-VOL. |
|
2396 |
The pair task was rejected because you are reverse resynchronizing the L1 pair sharing the specified P-VOL as the root volume. |
|
2397 |
The pair task was rejected because you are reverse resynchronizing the L2 pair sharing the specified P-VOL or S-VOL as the node volume. |
|
2398 |
The reverse resynchronization was rejected because the pair is not split (PSUS status) or suspended (PSUE status). |
|
2399 |
The reverse resynchronization was rejected because some of the pairs sharing the specified volume as the P-VOL are not in split (PSUS status) or suspended (PSUE status). |
|
23BB |
The pair was not created because the volume you specified as the S-VOL could not be used as the S-VOL because of Volume Security settings. |
|
23EF |
The pair was not deleted because the P-VOL and S-VOL are in the process of being Quick Split. |
|
23F1 |
The pair was not created because the CTG identifier you specified is not supported. |
|
9100 |
You cannot run the command because the system did not authenticate your user information. |
|
B911 |
The pair task was rejected because the specified volume did not exist. |
|
B912 |
The pair was not created because the specified S-VOL does not exist. |
|
B913 |
The pair task was rejected because the mirror ID is invalid. |