Command Control Interface SSB2 codes

This table lists the SSB2 codes when SSB1 is 2E11, 2E30, 2E31, 2EBE, B901, B9A8, B9A9, B9AD, or B9AE, the related CCI command, and the cause of the error.

SSB2	CCI command	Cause of error
020C	raidcom add snapshot	You cannot create a pair with the SLU attribute because a volume with the SLU attribute has been specified as a secondary volume.
020D	raidcom add snapshot	You cannot create a pair because a volume with the ALU attribute has been specified as a primary volume or a secondary volume.
0210	raidcom modify snapshot	You cannot operate on the specified volume because it is not the root volume of the Thin Image pair.
0C00	paircreate	The snapshot tree cannot contain a Thin Image pair and a Thin Image Advanced pair. Delete all Thin Image pairs (HTI only) in the snapshot tree.
0C03	pairsplit	A Thin Image pair (HTI only) created by using data reduction shared volumes cannot be split. Delete the Thin Image pair (HTI only).
800F	raidcom modify snapshot	You cannot perform the operation because there is an unsupported microcode version of the MP (processor) in the storage system.
801D	raidcom modify snapshot	You cannot perform the operation because the storage system is in internal process, or the configuration changing processes are conflicting. Wait a while, and then retry the operation.
801E	raidcom modify snapshot	You cannot perform the operation because the local replication pair is being initialized.
9100	All commands	You cannot run the command because the user authentication is not performed.
9685	paircreate	You cannot create the HTI pair because of a shortage of pair tables.
9700	paircreate	You cannot create the HTI pair because the pool is not available or the pool threshold (threshold of the pool usage rate) is exceeded.
9702	paircreate	You cannot create the HTI pair because you specified a pool ID different from the pool ID used by existing pairs with the specified P-VOL.
9703	paircreate	You cannot create the HTI pair because the volume you specified as the P-VOL is already used by another HTI S-VOL.
9704	paircreate	You cannot create the HTI pair because the volume you specified as the S-VOL is already used by another HTI P-VOL.
9705	paircreate	You cannot create the HTI pair because the volume you specified as the S-VOL is already used by another HTI S-VOL.
9706	paircreate/add snapshot	You cannot create the HTI pair because another HTI pair is using the MU number you specified. If you create a new HTI pair with an S-VOL for an existing HTI pair, you cannot create the HTI pair because the S-VOL for the existing HTI pair is using the MU number zero (0) you specified.
9707	paircreate	You cannot create the HTI pair because the capacity of the pair that you are trying to create exceeds the amount of licensed capacity you have reserved.
9708	raidcom modify snapshot	The execution status of the snapshot garbage data deletion processing (defragmentation processing) of the specified root volume is not in an operable status.
9718	All commands	The command ended abnormally. You tried to use a command other than paircreate for the volume in the pair other than the HTI pair. This error can also occur if you run the command with an unsupported parameter specified.
9719	All commands	The command ended abnormally because the pair is in a status that the command does not accept. This error can also be reported if you run the command with an unsupported parameter specified.
971A	paircreate	You cannot create the HTI pair because you do not have sufficient SM capacity.
971F	pairresync -restore	You cannot restore the HTI pair because the volume you specified as the P-VOL has an S-VOL Disable attribute.
9722	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified either of the following for the HTI P-VOL. External volume for which the Data Direct Mapping attribute is enabled. Normal volume for which accelerated compression is enabled. These volumes can only be used as pool volumes.
9723	All commands	The command ended abnormally because shared memory (Base) is not added
9724	All commands	The command ended abnormally because shared memory (Base or greater) is not added.
9725	All commands	The command ended abnormally because the LDEV number of the volume you specified as the HTI P-VOL is beyond the specified range.
9726	All commands	The command ended abnormally because you specified an unmounted volume as the HTI P-VOL.
9727	All commands	The command ended abnormally because either of the following volumes is specified as the P-VOL of the HTI pair: A blocked volume A volume in the same pool that contains a blocked pool volume
9728	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume that is in the process of being shredded or formatted as the HTI P-VOL.
9729	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume as the HTI P-VOL, and that volume has an emulation type other than OPEN-V.
972A	paircreate	You cannot create the HTI pair because the volume you specified as the HTI P-VOL has the command device setting.
972C	paircreate	You cannot create the HTI pair because the capacity of the volume you specified as the HTI P-VOL exceeds the supported size.
972E	paircreate	You cannot create the HTI pair because the capacity of the volume you specified as the HTI S-VOL exceeds the supported size.
972F	paircreate	You cannot create the HTI pair because you specified a V-VOL as the HTI P-VOL.
9730	paircreate	You cannot create the HTI pair because you specified a pool-VOL as the HTI P-VOL.
9731	pairresync -restore	You cannot restore the HTI pair because the HTI P-VOL and TC P-VOL share a volume, and the TC pair is not split ("PSUS" status) or is suspended and blocked (“PSUE” status).
9732	pairresync -restore	You cannot restore the HTI pair because the HTI P-VOL and UR P-VOL share a volume, and the UR pair is not split ("PSUS" status) or is suspended and blocked (“PSUE” status).
9733	pairresync -restore	You cannot restore the HTI pair because the HTI P-VOL and TC S-VOL share a volume.
9734	pairresync -restore	You cannot restore the HTI pair because the HTI P-VOL and UR S-VOL share a volume.
9735	paircreate	You cannot create the HTI pair because you specified a UR journal volume as the HTI P-VOL.
973B	All commands	The command ended abnormally because the LDEV number of the volume you specified as the HTI S-VOL is beyond the specified range.
973C	All commands	The command ended abnormally because you specified an unmounted volume as the HTI S-VOL.
973D	All commands	The command ended abnormally because either of the following volumes is specified as the S-VOL of the HTI pair: A blocked volume A volume in the same pool that contains a blocked pool volume
973E	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume that is in process of being shredded or formatted as the HTI S-VOL.
973F	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume whose emulation type is other than OPEN-V as the HTI S-VOL.
9740	paircreate	You cannot create the HTI pair because the volume you specified as the HTI S-VOL has the command device setting.
9742	paircreate	You cannot create the HTI pair because you specified an external volume as the HTI S-VOL.
9744	pairsplit -S, unmap snapshot, replace snapshot	The command ended abnormally because the volume you specified as the S-VOL was grouped with a datastore of Hitachi Storage Provider for VMware vCenter.
9745	paircreate	You cannot create the HTI pair because you specified a volume other than a V-VOL as the HTI S-VOL.
9746	paircreate	You cannot create the HTI pair because you specified a pool-VOL as the HTI S-VOL.
9747	paircreate	You cannot create the HTI pair because you specified a TC P-VOL as the HTI S-VOL.
9748	paircreate	You cannot create the HTI pair because you specified a TC S-VOL as the HTI S-VOL.
9749	paircreate	You cannot create the HTI pair because you specified a UR data volume or journal volume in the intermediate site of 3DC cascading configuration as the HTI S-VOL.
974A	paircreate	You cannot create the HTI pair because you specified a UR P-VOL as the HTI S-VOL.
974B	paircreate	You cannot create the HTI pair because you specified a UR S-VOL as the HTI S-VOL.
974C	paircreate	You cannot create the HTI pair because you specified a UR journal volume as the HTI S-VOL.
974F	All commands	The command ended abnormally because the volume you specified as the HTI S-VOL has an S-VOL Disable attribute.
9752	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because the Max LBA size of the volumes you specified as the HTI P-VOL and S-VOL is different.
9753	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because the number of slots of the volumes you specified as the HTI P-VOL and S-VOL is different.
9754	paircreate	You cannot create the HTI pair because you specified a DP-VOL as the HTI S-VOL.
9756	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified either of the following for the HTI S-VOL. External volume for which the Data Direct Mapping attribute is enabled. Normal volume for which accelerated compression is enabled. These volumes can only be used as pool volumes.
9757	All commands	The command ended abnormally because you specified a Volume Migration V2 source volume as the HTI P-VOL. For more information about using Volume Migration V2, contact customer support.
9758	All commands	The command ended abnormally because you specified a Volume Migration V2 target volume as the HTI P-VOL. For more information about using Volume Migration V2, contact customer support.
975A	All commands	The command ended abnormally because you specified an SI P-VOL as the HTI S-VOL.
975B	All commands	The command ended abnormally because you specified an SI S-VOL as the HTI S-VOL.
975C	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a DP-VOL for which the Data Direct Mapping attribute is enabled as the HTI S-VOL.
975D	All commands	The command ended abnormally because you specified a Volume Migration V2 source volume as the HTI S-VOL. For more information about using Volume Migration V2, contact customer support.
975E	All commands	The command ended abnormally because you specified a Volume Migration V2 target volume as the HTI S-VOL. For more information about using Volume Migration V2, contact customer support.
976A	paircreate	An unavailable parameter (unsupported parameter) is specified in the command.
976C	pairsplit	You cannot store the snapshot data because you have run the command when the pair is suspended and blocked ("PSUE" status).
976E	pairsplit	The snapshot data cannot be stored because the HTI P-VOL and a TC S-VOL share the volume, and the status of the TC pair is "COPY".
976F	pairsplit	Snapshot data cannot be stored because the HTI P-VOL and a UR S-VOL share the volume, and the status of the UR pair is "COPY".
9772	paircreate	The HTI pair cannot be created because you specified a UR delta resync pair volume as the HTI S-VOL.
9774	paircreate	The HTI pair cannot be created because the HTI P-VOL and an SI P-VOL share the volume, and the MU number you specified for the HTI pair is already used by the SI pair.
9777	paircreate	The HTI pair cannot be created because the HTI P-VOL and an SI S-VOL share the volume, and you specified MU number zero (0) for the HTI P-VOL.
977A	paircreate, pairsplit	The command ended abnormally because the HTI P-VOL and an SI P-VOL share the volume, and the SI pair was in the process of resynchronization.
977B	paircreate, pairsplit	The command ended abnormally because the HTI P-VOL and an SI S-VOL share the volume, and the SI pair status is not "PSUS".
977C	pairresync -restore	You cannot restore the HTI pair because the HTI P-VOL and an SI P-VOL share the volume, and the SI pair is not split ("PSUS" status) or is suspended and blocked ("PSUE" status).
977D	pairresync -restore	The HTI pair cannot be restored because the HTI P-VOL and an SI S-VOL share the volume, and the SI pair is not split ("PSUS" status).
977E	pairsplit	Snapshot data cannot be stored because the pool or the pool-VOL is blocked or the pool is full.
9783	pairresync -restore	You cannot restore the HTI pair because of one of the following reasons: You are storing snapshot data for the HTI pair that you want to restore using the consistency group to which the pair is assigned. You are using the P-VOL of the HTI pair you want to restore as the P-VOL for another HTI pair, and you are storing the snapshot data of the latter pair using the consistency group in which the pair is defined.
9786	All commands	The command ended abnormally because you specified a global-active device volume for quorum disk as the HTI P-VOL.
9787	All commands	The command ended abnormally because you specified a global-active device volume for quorum disk as the HTI S-VOL.
978A	paircreate	You cannot create the HTI pair using the consistency group ID because of one of the following reasons: SI is using the specified consistency group ID. You have reached the maximum number of pairs that can be created for a consistency group. A pair that uses the same P-VOL is assigned to the specified consistency group.
978B	paircreate	You cannot create the HTI pair because the consistency group ID you specified is not within range.
9790	All commands	The command ended abnormally because a DP-VOL whose capacity is being expanded was specified as the P-VOL in an HTI pair.
9793	paircreate	You cannot create the HTI pair because a DP-VOL that is processing the Unmap command issued with system option mode 905 ON has been specified as the HTI P-VOL
9796	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume that does not have an LU path definition or a volume that is not assigned to a namespace for NVMe as the HTI P-VOL.
9797	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because you specified a volume that does not have an LU path definition or a volume that is not assigned to a namespace for NVMe as the HTI S-VOL.
97A1	paircreate	If you have reached the maximum number of HTI pairs, you cannot create new pairs.
97A2	paircreate, pairsplit, pairresync, pairresync-restore	The command ended abnormally because you specified a volume that uses two mirrors in a three UR data center configuration as the P-VOL.
97A3	paircreate, pairsplit, pairresync, pairresync-restore	The command ended abnormally because the volume specified as the S-VOL uses two mirrors in a three UR data center configuration.
97A4	paircreate	You cannot create the HTI pair because you have specified a DP-VOL in the initialization process as the HTI P-VOL.
97A5	All commands	The command ended abnormally because you specified a volume that was undergoing online data migration as the HTI P-VOL.
97A6	All commands	The command ended abnormally because you specified a volume that was undergoing online data migration as the HTI S-VOL.
97B4	paircreate	You cannot create the pair and use the specified consistency group because you have you have reached the maximum number of consistency groups that can be created.
97B5	paircreate	You cannot create the HTI pair for the specified P-VOL because the maximum number of snapshot ID (MU number) was used.
97B6	paircreate	You cannot create the HTI pair because of one of the following reasons: You were in the process of creating a new snapshot group but you reached the maximum number of snapshot groups that can be created. You have specified a snapshot group which has reached the maximum number of pairs allowed in a group.
97B7	paircreate	You cannot create the HTI pair because the HDP pool is being initialized.
97B9	paircreate, pairsplit, pairresync, pairresync -restore	The command ended abnormally because the status of the pairs using the P-VOL you specified is suspended ("PSUE" status).
97BD	map snapshot/unmap snapshot	The command ended abnormally because you specified a P-VOL that is not an HTI P-VOL.
97BE	map snapshot/unmap snapshot/replace snapshot replace snapshot is for VSP 5000 series	The command ended abnormally because you specified a volume that does not exist.
97BF	paircreate	You cannot create the HTI pair from the consistency group to which the specified snapshot group belongs because of one of the following reasons: SI is using the specified consistency group. You have reached the maximum number of pairs that can be created for a consistency group. A pair that uses the same P-VOL exists already in the specified snapshot group.
97C2	All commands	The command ended abnormally because you specified an MU number outside the allowable range.
97C4	All commands	The command ended abnormally because of one of the following reasons: You have specified a pool that is neither an HTI pool nor a DP pool. You have specified a pool that does not exist.
97C6	paircreate, pairsplit, pairresync, or pairresync -restore	The command ended abnormally because HTI is not installed.
97C7	paircreate	You cannot create the HTI pair because the capacity of cache management devices is insufficient.
97C8	paircreate	You cannot create the HTI pair because the capacity of the volume you specified as the P-VOL or the S-VOL of the HTI pair is more than the supported size.
97CB	All commands	The command ended abnormally because you specified a pool that is neither an HTI pool nor a DP pool.
97CD	paircreate/map snapshot	The command ended abnormally because you specified a deduplication system data volume (fingerprint) as the P-VOL of a Thin Image pair.
97CE	paircreate/map snapshot	The command ended abnormally because you specified a deduplication system data volume (fingerprint) as the S-VOL of a Thin Image pair.
97CF	paircreate	You cannot create the HTI pair because an HTI group is already using the CG number you specified.
97D4	All commands	The command ended abnormally because you are in the process of turning off the power.
97D5	All commands	You cannot run the command because even though the specified serial number matches the virtual storage machine, the physical storage system's serial number that corresponds with the virtual storage machine's serial number does not match when the virtual storage machine's serial number is specified for P-VOL and S-VOL.
97D6	All commands	You cannot run the command because the model, serial number, or virtual LDEV ID of the volume specified as P-VOL is being changed.
97D7	All commands	You cannot run the command because the model, serial number, or virtual LDEV ID of the volume specified as S-VOL is being changed.
97D8	All commands	The pair operation was rejected because one of the following conditions holds for the volume that is specified as the HTI P-VOL: The volume is used as a global-active device pair volume and does not accept pair operations. The volume is specified reservation attribute of a global-active device.
97D9	All commands	The pair operation was rejected because one of the following conditions holds for the volume that is specified as the HTI S-VOL: The volume is used as a global-active device pair volume. The volume is specified reservation attribute of a global-active device.
97DA	paircreate, map snapshot	The command ended abnormally because the T10 PI settings for the P-VOL and S-VOL did not match.
97DD	unmap snapshot/replace snapshot	The command ended abnormally because you specified a pair to which an S-VOL is not assigned.
97DE	map snapshot/unmap snapshot/replace snapshot	The operation failed because different DKCMAIN microcode versions are mixed. Confirm DKCMAIN microcode version.
97DF	map snapshot	The command ended abnormally because you specified an S-VOL that is assigned to a pair.
97F1	replace snapshot	The command ended abnormally because the pair cannot be identified from snapshot data and the P-VOL that you specified.
97F1	map snapshot/replace snapshot	The command ended abnormally because you specified a pair to which an S-VOL is assigned.
97FA	unmap snapshot/replace snapshot	The command ended abnormally because you specified an S-VOL that is not assigned to a pair.
9E03	raidcom add snapshot	You cannot create a pair because both of a Clone option and an SLU option have been specified.
B912	paircreate, pairsplit, pairresync	The HTI pair task failed because you specified the incorrect S-VOL.
B9A7	All commands	You cannot retrieve the consistency group information because HTI is not installed.
FF58	pairsplit, pairresync, pairresync -restore	The command ended abnormally because the specified pair is a cascaded pair.
FF59	paircreate	The command ended abnormally because the specified P-VOL is used by a cascaded pair.
FF68	All commands	The command ended abnormally because a DP-VOL whose capacity is being expanded was specified as the S-VOL in an HTI pair
FF6D	paircreate	The command ended abnormally because the specified P-VOL is used by a cascaded pair.
FF72	paircreate, pairsplit, pairresync, pairresync -restore	The Thin Image pair task failed because a snapshot tree is being deleted.
FF7A	paircreate	The Thin Image pair could not be created because the V-VOL capacity exceeded the subscription limit for the pool.
FF7C	paircreate	The Thin Image pair whose snapshot data is stored in the DP pool could not be created because system option mode 1120 is set to ON.
FF82	paircreate／map snapshot	The command ended abnormally because the deduplication system data volume (data store) is specified as the Thin Image P-VOL.
FF83	paircreate／map snapshot	The command ended abnormally because the deduplication system data volume (data store) is specified as the Thin Image S-VOL.