SSB2 error codes when SSB1 = 2E31, B901, B90A, B90B, B912, D004

Error code (SSB2)	Description
4BF0	Although VSP One SDS Block was specified for remote connection, the command was rejected because no path group ID was specified or 0 was specified.
4BF1	Although VSP One SDS Block was specified for remote connection, the command was rejected because a port other than an iSCSI port was specified.
9100	The command cannot be executed because the user authentication is not performed.
B920	The pair cannot be created because the system identifier is not correct.
B923	The consistency group paircreate or pairresync was rejected because supported and unsupported software is used in the DKC.
B927	You cannot run the following operations to a pair in a 2DC configuration: Swap Suspend Takeover
B928	The pair cannot be created because the mirror ID is invalid.
B929	The pair operation was rejected because the microcode is being replaced.
B92A	The pair cannot be created because the specified volume is a command device.
B934	The pair cannot be created because TrueCopy is not installed.
B935	S-VOL hide mode is not supported.
B936	The required shared memory for TrueCopy is not installed.
B93B	The specified volume is a P-VOL. The pair cannot be released because the P-VOL is specified as an S-VOL.
B941	The specified volume is an S-VOL. The pair cannot be released because the S-VOL is specified as a P-VOL.
B945	The command was rejected because the volume is unpaired.
B952	The specified LU is not defined. The DKC configuration might have been changed. Restart CCI.
B97B	The operation cannot run because pair status is either PSUS (by user) or PSUE (because of failure).
B97C	The command was rejected because the volume is unpaired.
B990	The pair cannot be created because the consistency group ID is greater than is allowed. If this error occurred when you did not specify the consistency group ID, contact customer support.
B994	The Swap Resync operation cannot be performed because the S-VOL is not in PSUS or SSWS status. (Swap Resync resynchronizes differential data when the S-VOL is swapped for the P-VOL.)
B998	The pair cannot be created because the secondary system path setting is invalid.
B99B	The pair cannot be created because TrueCopy Asynchronous is not supported.
B9BD	The DKC LDEV configuration might have been changed while starting CCI. Restart CCI.
B9C0	The resource of the command device has run out.
C162	The pair cannot be resynchronized because the pair was not in the PSUS or PSUE status.
C16B	The pair cannot be created because the S-VOL is not available.
C184	A request for a pairsplit -S operation was rejected because the status change of the S-VOL failed.
C189	A request for a pairsplit -S operation was rejected because the pair status was invalid.
C18A	A request for a pairsplit -S operation was rejected because the status of the volume is being changed or the group contains a pair of which status is being changed.
C194	The pair cannot be split because the S-VOL pair status was in transition.
C195	A request for a pairsplit -r operation was rejected because the pair status was already PSUS or PSUE.
C198	The group includes no pair that can be split.
C199	A request for a pairsplit -r operation was rejected because the status of the volume is being changed or the group contains a pair of which status is being changed.
C1BE	The pair's status cannot be changed during the power-on processing of the DKC.
C1D6	The command was rejected because it was issued to a non-TC pair volume.
C211	The command was rejected because the specified volume is a P-VOL.
C212	The command was rejected because the specified volume is an S-VOL.
C214	The command was rejected because the secondary system is not registered, or the registered secondary system information is invalid.
C215	The command was rejected because an internal logical error has occurred.
C218	The command was rejected because the pair status is invalid.
C21A	The command was rejected because the P-VOL status is other than PSUS or PSUE.
C21C	The command was rejected because the secondary system is not registered, or the registered secondary system information is invalid.
C22A	The command was rejected because the pair was deleted on a volume other than P-VOL.
C22C	The command was rejected because the volume is unpaired.
C22D	The command was rejected because the specified volume is the volume other than the P-VOL.
C22E	The command was rejected because the pairsplit command specifying -P option (write protection of P-VOL) was issued to a volume whose status is not PAIR.
C233	The command was rejected because the S-VOL status is unpaired.
C234/C235/C236/C237	The command was rejected because an internal logical error has occurred.
C238	The command was rejected because the specified volume is the volume other than the P-VOL.
C239	The command was rejected because the pair was resynchronized on a volume whose status is other than PSUS or PSUE.
C23A	The command was rejected because an internal logical error has occurred.
C23B	The command was rejected because the volume is unpaired.
C23C	The command was rejected because the volume status is other than PAIR or COPY.
C23D	The command was rejected because the command for TrueCopy Asynchronous was issued to a TrueCopy volume.
C267	The pair cannot be created because the command was issued to the command device.
C271	The command was rejected because the specified consistency group ID is invalid.
C28B	The command was rejected because the horctakeover command was issued to a volume whose status is not SSWS.
C28C	The command was rejected because the secondary system is not registered, or the registered secondary system information is invalid.
C28D	There is no volume to which the horctakeover command can run.
C28E	The command was rejected because an internal logical error has occurred.
C297	The command was rejected because the specified volume is used as an S-VOL.
C2A0	The pair cannot be created because the capacity that is used by software products other than TrueCopy exceeds license capacity.
C2A1	The command was rejected because an internal logical error has occurred.
C2A3	The pair cannot be created because the used capacity exceeds the license capacity.
C2B3	The command was rejected because DP-VOL capacity is being changed.
C2B4	The command was rejected because an internal logical error has occurred.
C2B5	The pair cannot be created because the TC P-VOL is being initialized by SI.
C2B6	The command was rejected because releasing pages in DP-VOL is in progress.
C300	A copy pair associated with Universal Replicator cannot be created because the Remote Replication Extended program product is not installed on the primary system.
C301	A copy pair associated with Universal Replicator cannot be created because the Remote Replication Extended program product is not installed on the secondary system.
C304	The pair cannot be created because the S-VOL is a DP-VOL.
C305	The pair cannot be created because the capacity that is used by TrueCopy in the secondary system exceeds license capacity. Check license capacity, including for related software products.
C30D	The volume in the secondary system or another volume that belongs to the same group is changing to SMPL, PSUS, or PSUE status. Retry the operation after approximately 5 minutes.
C312	The P-VOL is not in unpaired status.
C313	The P-VOL is not in PSUS or PSUE.
C314	The P-VOL is not in unpaired status.
C315	The P-VOL includes PIN data.
C316	The P-VOL is in the process of drive copy for failure assistance.
C318	The P-VOL is terminating the copy task.
C319	The P-VOL is in the process of correction copy.
C31A	The P-VOL is in the process of correction access.
C31B	A request for creating or resynchronizing TrueCopy pairs was received, but the command was rejected because the physical volume with the specified P-VOL is blocked.
C31C	The P-VOL cannot be accessed due to one of the following reasons: The P-VOL is blocked. A pool to which the P-VOL belongs contains a pool volume that is not in the normal status.
C31D	The P-VOL is being formatted.
C31E	The P-VOL is read only.
C320	The number of remote paths between primary and secondary systems is 0 (not specified).
C321	The number of remote paths between primary and secondary systems is smaller than the minimum required.
C322	The DKC type of the primary system does not support TrueCopy.
C324	The secondary system's sequence number is invalid.
C327	The pair cannot be created because the P-VOL is not available for remote copy.
C328	The track formats of the P-VOL and the S-VOL do not match.
C32A	The S-VOL is protected by Data Retention Utility.
C32B	The P-VOL is protected by Data Retention Utility.
C32C	The S-VOL is protected by Data Retention Utility.
C32D	The S-VOL is protected by Data Retention Utility.
C32E	A request for a paircreate operation was rejected because the specified secondary system is an unsupported product.
C32F	The number of P-VOL cylinders in the TC volume is not equal to or smaller than the number of S-VOL cylinders.
C330	The pair cannot be created or resynchronized because of one of the following: P-VOL and S-VOL capacities are not the same. The S-VOL is in a LUSE configuration.
C332	S-VOL cache is disabled.
C335	The S-VOL is a TrueCopy Asynchronous P-VOL.
C336	The S-VOL includes PIN data.
C337	The S-VOL is in reserve status.
C338	Copy pair cannot be created because of the either of the following reasons: The S-VOL is requesting intervention, protected, or cannot be used. The S-VOL is configured as the S-VOL or reserved volume of ShadowImage, reserved volume of Volume Migration, or the volume of Universal Replicator pair.
C339	The S-VOL is not available.
C33A	A request for a paircreate operation was rejected because the secondary system is not supported by TrueCopy.
C33B	The corresponding volume cannot be specified as an S-VOL because the volume is used as another pair's S-VOL.
C33C	A request for a paircreate operation was rejected because the specified S-VOL was not mounted.
C33E	The pair cannot be created because the S-VOL is not installed or is blocked (DEV NOT READY status).
C33F	The corresponding volume cannot be specified as an S-VOL because the volume is already specified as a TC pair volume.
C35C	The P-VOL is not accessible.
C370	There are fewer paths than the required minimum number because a path failure occurred or an invalid path was specified.
C371	The process that is performed after the copying process of Volume Migration in the S-VOL is in progress. Try again in a few minutes.
C372	The process that is performed after the copying process of Volume Migration in the P-VOL is in progress. Try again in a few minutes.
C373	A request for a paircreate operation was rejected because the specified S-VOL is a ShadowImage reserved volume.
C379	The minimum number of paths that need to be set is not met because a path failure occurred or an invalid path was specified.
C37A	An internal error occurred.
C37B	The operation failed due to any of the following reasons: An I/O error occurred in the S-VOL. The S-VOL is not available. This function or configuration is not supported by the DKCMAIN microcode version of the local storage system. Take the following actions: Make sure that the S-VOL is available. If the S-VOL is available, make sure that this function or configuration is supported by the DKCMAIN microcode version of the local storage system.
C37E	The S-VOL cache is disabled.
C380	The primary system cache is in transition to blockage on one side.
C381	The primary system cache is in the process of being restored.
C382	The primary system cache is either in transition to blockage on one side or in the process of being restored on one side.
C388	The pair cannot be created because the emulation type is not available for the specified volume.
C38B	The secondary system is already used by TrueCopy.
C38D	The S-VOL is not available.
C38E	The S-VOL is a device that is not supported by TrueCopy.
C390	The S-VOL status is not PSUS or PSUE.
C391	The S-VOL cannot be copied.
C392	The volume cannot be used as an S-VOL because it is in reserve status, is already being used by TrueCopy, or is being used by Universal Replicator.
C393	The S-VOL includes PIN data.
C395	The pair cannot be created or resynchronized due to one of the following reasons: The specified S-VOL is blocked. The physical volume used as the S-VOL is blocked. The correction access is in progress. A pool to which the specified S-VOL belongs contains a pool volume that is not in the normal status.
C398	The pair cannot be created because the emulation type is not available for the specified volume.
C39B	An internal error occurred.
C39E	The pair cannot be created because the capacity of the P-VOL exceeded the maximum volume capacity allowed to create a TrueCopy pair.
C39F	The pair cannot be created because the capacity of the S-VOL exceeded the maximum volume capacity allowed to create a TrueCopy pair.
C3A0	The P-VOL is a device not supported by TrueCopy.
C3A8	The device type combination between the P-VOL and S-VOL is invalid.
C3AA	The secondary system's cache is blocked on one side.
C3AB	The secondary system's cache is blocked on one side.
C3AC	TrueCopy is not supported for this controller emulation type of the secondary system.
C3AD	The secondary system capacity exceeds the license capacity.
C3AE	TrueCopy is not installed on the secondary system.
C3AF	The DKC type of the secondary system is not supported by TrueCopy.
C3B1	The number of paths is smaller than the required minimum number of paths.
C3B3	An internal error occurred.
C3B5	The configuration combination of P-VOL and S-VOL is invalid
C3B6	The TC P-VOL is a ShadowImage pair volume.
C3B7	The TC S-VOL is a ShadowImage pair volume.
C3B8	An internal error occurred.
C3B9	The pair cannot be created because the LUN is not defined for the S-VOL.
C3BC	TrueCopy is not installed on the secondary system.
C3BE	The following volumes cannot be specified as a TC P-VOL: The SI S-VOL is not in PSUS status. The SI P-VOL is in the process of reverse copy.
C3BF	A SI S-VOL, SI reserved volume, or SI P-VOL in the process of reverse copy cannot be specified as a TC S-VOL.
C3C7	A request for a paircreate operation was rejected because the specified volume was already part of a TC or UR pair (including journal volumes).
C3CA	The S-VOL is reserved, or a secondary system, S-VOL, or the path between primary system and secondary system is in the busy status.
C3CD	The TC S-VOL is a SI pair volume.
C3D2	The DKC type of the secondary storage system is not supported by TrueCopy.
C3D4	A pair cannot be created because the P-VOL is being used by Volume Migration.
C3D6	The specified S-VOL is unavailable because the connecting port cannot recognize it.
C3D7	The pair status of secondary system's S-VOL is invalid.
C3D8	The pair cannot be created because the volume specified for the S-VOL is a system volume.
C3D9	The pair operation cannot be performed if the TC P-VOL or the TC S-VOL meets any of the following conditions: The volume is a DP-VOL, and paired using a reserved volume of ShadowImage, Thin Image, Thin Image Advanced, or Volume Migration. The volume is a DP-VOL and its capacity is being expanded, or pages are being released. The capacity of the P-VOL and the S-VOL is not the same The volume is being initialized by ShadowImage.
C3DB	S-VOL pair status is not PSUS or PSUE.
C4DE	The pair cannot be created because the remote path between the primary and secondary storage systems is not valid.
C4FC	The required amount of shared memory for the operation is not installed in the secondary system.
CB12	TC, TCz, and UR, URz cannot be mixed in the consistency group.
CB19	The secondary system consistency group cannot be deleted because reversing the P-VOL and S-VOL using the horctakeover command failed.
CB1A	Deletion of the secondary system consistency group was abnormally terminated because reversing the P-VOL and S-VOL using the horctakeover command failed.
CB1D	No dummy volume can be created in the S-VOL.
CB1F	The secondary system does not support TrueCopy.
CB20	In referring to the function bit, the system information reference function was abnormally terminated.
CB21	In a Pairresync operation, all difference setting was abnormally terminated.
CB23	An internal error occurred.
CB5D	The command was rejected because after receiving pair creation request, since it is connected to old model, specified P-VOL became out of support.
CB60	TrueCopy is not installed in the secondary system.
CB66	The TC pair cannot be created or resynchronized because the differential bitmap area is not available due to one of the following reasons: Free area for shared memory in the secondary system is insufficient. Free area for Dynamic Provisioning pool specified as the S-VOL is insufficient.
CB67	An additional shared memory is not installed in the secondary system.
CB68	The pair cannot be created or resynchronized because the free area for shared memory in the primary system is insufficient and the differential bitmap area cannot be reserved.
CB69	The pair cannot be created because the number of pairs exceeds the maximum number that can be created in a single consistency group.
CB6E	The paircreate operation cannot run because the P-VOL is a volume in a storage system from another company.
CB71	The paircreate operation cannot run because the P-VOL is a migration volume in a storage system from another company.
CB73	The paircreate operation cannot run because the S-VOL is a migration volume in a storage system from another company.
CB75	The device is not recognized correctly.
CB76	The paircreate operation cannot run because the paths are specified per storage system.
CB77	The used capacity of the Data Retention Utility software product on the secondary system exceeds the license capacity.
CB78	The paircreate operation cannot run because the specified S-VOL is defined as the command device.
CB7E	A request for a paircreate operation was rejected because the specified S-VOL belongs to a different CLPR than the registered consistency group's CLPR.
CB9E	A request for a paircreate operation was rejected in the secondary system due to one of the following reasons: The function for defining a consistency group that contains multiple pairs of storage systems is not supported. The function for defining a consistency group for open systems is not supported.
CBD7	The storage system is in internal processing. Try the operation again.
CBD8	A pair cannot be created because the specified P-VOL is one of the following: A journal volume used for UR A UR secondary volume that is not suspended
CBDA	The paircreate operation cannot run because the used capacity of Data Retention Utility on the secondary system exceeds the license capacity.
CBDC	A request for creating a TC pair was received in the TC-UR combination status. However, the command was rejected because the mirror ID of UR was 0.
CBDD	In configuring a TC-UR multi-target configuration, a request for a TC paircreate operation was rejected because the UR pair was in the process of copying.
CBDE	The pair operation failed because the P-VOL is used by Thin Image or Thin Image Advanced.
CBDF	The pair operation failed because the S-VOL is used by Thin Image or Thin Image Advanced.
CBE1	The paircreate operation cannot run because the S-VOL is a V-VOL of Thin Image (TI only).
CBE2	The paircreate operation cannot run because the P-VOL is a Dynamic Provisioning pool-VOL.
CBE3	The paircreate operation cannot run because the S-VOL is a pool-VOL of Dynamic Provisioning or Thin Image (TI only).
CBE7	65,280 pairs or more cannot be created in one storage system.
CBEB	The pair cannot be created because the specified P-VOL is being shredded by Volume Shredder.
CBEC	The pair cannot be created because the specified S-VOL is being shredded by Volume Shredder.
CBED	The paircreate operation cannot run because of one of the following reasons: The specified S-VOL is the volume for a UR S-VOL. The specified S-VOL is the volume for a UR journal volume. An attempt was made to create the 2DC or 3DC configuration using the specified S-VOL, but a storage system that does not support 2DC or 3DC is included in the configuration.
CBEE	The request for a paircreate operation was rejected because the specified P-VOL is already paired for either of the following purposes: P-VOL for the differential data resync in UR P-VOL for the primary site in the 3DC multi-target configuration with three UR sites.
CBF3	The pair was not created because the specified P-VOL is either of the following: An external volume mapped for moving data online An external volume of which data direct mapping attribute is enabled
CBF7	An attempt was made to create the 2DC or 3DC configuration using the specified P-VOL, but the paircreate operation cannot run because a storage system that does not support the 2DC or 3DC configuration is included.
CBF8	The pair cannot be created due to either of the following reasons: The microcode or firmware version of the primary or secondary system does not support the connection to a remote storage system. The primary or secondary system is a model that does not support the connection to a remote storage system.
CBFC	The pair cannot be created because the consistency group ID is not within the supported range.
CBFF	The pair cannot be created because the remote path between the primary and secondary systems is not valid.
FD01	The pair cannot be created because no virtual LDEV ID is specified for the volume specified as the S-VOL.
FD02	The pair cannot be created because no virtual LDEV ID is specified for the volume specified as the P-VOL.
FD03	The pair cannot be created because the specified virtual information does not match the virtual information registered in the secondary storage system.
FD04	The specified secondary storage system does not support global storage virtualization.
FD05	The specified primary storage system does not support global storage virtualization.
FD07	The pair cannot be created because volume specified as P-VOL is used by GAD pair.
FD08	The pair cannot be created because volume specified as S-VOL is used by GAD pair.
FD09	The pair cannot be created because volume specified as P-VOL is a GAD reserve volume.
FD0A	The pair cannot be created because volume specified as S-VOL is a GAD reserve volume.
FD0B	The internal processing of the specified P-VOL takes some time. Wait for a while, and then retry the operation.
FD0C	The pair cannot be created or resynchronized because the differential bitmap area cannot be reserved due to one of the following reasons: Free area for shared memory in the primary system is insufficient. Free area for Dynamic Provisioning pool specified as the P-VOL is insufficient.
FD0E	Internal processing is being processed in the specified S-VOL. Try again after a while.
FD0F	The pair was not created because the data direct mapping attribute of the specified P-VOL is enabled, and the function of R-DKC for mapping the volumes of an external storage system larger than 4 TB is not supported.
FD10	The pair cannot be created. The T10 PI attribute setting of the primary volume and that of the secondary volume are different.
FD12	The pair was not created because the specified S-VOL operates as the system LU of NAS.
FD21	The pair operation cannot be performed because the LDEV specified as a P-VOL or an S-VOL is already defined as the namespace on the NVM subsystem.
FD22	The pair cannot be created because the host connection settings (LUN paths or namespaces of NVMe-oF) are not the same between the TC P-VOL and TC S-VOL.
FD23	The TC pair linked with the UR pair cannot be created because the TC P-VOL or TC S-VOL is defined as a namespace of NVMe-oF. Make sure that the device configuration is in either of the following states, and then retry the operation: If you want to create a TC pair or 3DC configuration by using a volume defined as a namespace, check whether the combination of the local storage system and the remote storage system is supported and whether the microcode versions are supported. Connect the storage systems of the supported combination again, make sure that the microcode versions of the storage systems are supported versions, and then retry the pair operation. If a volume is mistakenly defined as a namespace, release the namespace and define LUN paths for both P-VOL and S-VOL, and then retry the pair operation.
FD25	Although the TC P-VOL and TC S-VOL are defined as namespaces of NVMe-oF, the pair cannot be created because this storage system combination is not supported. Make sure that the device configuration is in either of the following states, and then retry the operation: If you want to create a TC pair or 3DC configuration by using a volume defined as a namespace, check whether the combination of the local storage system and the remote storage system is supported and whether the microcode versions are supported. Connect the storage systems of the supported combination again, make sure that the microcode versions of the storage systems are supported versions, and then retry the pair operation. If a volume is mistakenly defined as a namespace, release the namespace and define LUN paths for both P-VOL and S-VOL, and then retry the pair operation.
FD26	The TC pair cannot be created because the volume paired with a VSP One SDS Block volume in a UR pair cannot be used for a TC pair.