SSB codes for GAD operations

9100

The command cannot be executed because user authentication has not been performed.

B952

The specified LU is not defined. A configuration of the storage system might have been changed. Restart CCI.

B9A2

You cannot create the GAD pair, because the specified volume is a command device.

B9A4

You cannot create the GAD pair because no SCSI path is defined on the specified volume.

B9A5

You cannot create the GAD pair or perform a swap resync for the pair, because one of the following remote paths is not set:

• A bidirectional remote path between the storage systems at the primary site and secondary site
• A remote path from the storage system at the primary site to the storage system at the secondary site
• A remote path from the storage system at the secondary site to the storage system at the primary site

B9A8

The I/O mode of the specified volume cannot be changed because the volume is not a GAD pair volume.

B9BD

A configuration of the LDEV in the storage system might have been changed while CCI was running. Restart CCI.

B9C0

There are no free resources in the command device. Run the raidcom modify ldev command by specifying "no" for the -command_device option. Then run the raidcom modify ldev command again by specifying "yes" for the -command_device option.

DB89

You cannot change the status of the GAD pair, even though a request to suspend or to delete the pair has been received. This is because the volume paired with the specified volume is in an unusable status.

DB8A

You cannot change the status of the GAD pair, even though a request to suspend or to delete the pair has been received. This is because the volume paired with the specified volume is blocked.

DB8B

You cannot change the status of the GAD pair, even though a request to suspend or to delete the pair has been received. This is because the volume paired with the specified volume is in an unusable status.

DB8D

(VSP One B20 series) You cannot change the status of the GAD pair, even though a request to suspend or to delete the pair has been received. This is because the number of remote paths from the storage systems at the primary site to the storage systems at the secondary site is less than the minimum number of remote paths.

(VSP One B85) The pair operation failed because communication cannot be normally performed on the remote path between storage systems. Confirm the status of the remote path. The suspension by failure might have occurred in the GAD pair. If you deleted the pair, only the volume that accepted the pair deletion might have been deleted.

FA00

You cannot create the GAD pair, because the capacity of the volume that has been specified as the primary volume is larger than the maximum capacity of a GAD pair that can be created.

FA01

The operation failed because the specified P-VOL is an external volume mapped for migrating data online, and the cache mode is not Write Sync.

FA02

You cannot create or resynchronize the GAD pair, because the storage system cache at the primary site is in one of the following statuses:

• One side is blocked or is transitioning to being blocked.
• One side is recovering.
• Recovering

FA03

You cannot create the GAD pair, because the remote paths from the storage systems at the primary site to the storage systems at the secondary site are in either of the following status:

• The number of remote paths is 0 (unspecified).
• The number of remote paths is less than the minimum number.

FA04

You cannot create the GAD pair, because the emulation type of the volume that has been specified as the primary volume is not OPEN-V.

FA05

You cannot create the GAD pair, because the volume that has been specified as the primary volume is a migration volume of a product of another company.

FA07

The pair status of the volume that has been specified as the primary volume is not SMPL.

FA08

The pair status of the volume that has been specified as the primary volume is not PSUS or PSUE.

FA09

There is a pinned track on the volume that has been specified as the primary volume.

FA0A

You cannot create the GAD pair, because the volume that has been specified as the primary volume is blocked.

FA0B

You cannot create the GAD pair, because the volume that has been specified as the primary volume is in one of the following statuses:

• Blocked
• Being formatted
• Read only
• A pool to which the volume specified as the primary volume belongs contains a pool volume that is not in the normal status

FA0D

The virtual emulation type of the P-VOL is not supported.

FA0E

You cannot create the GAD pair, because the volume that has been specified as the primary volume is not a virtual volume of Dynamic Provisioning.

FA0F

The device type of the volume that has been specified as the primary volume is not supported.

FA10

You cannot create the GAD pair because the secondary volume is in an unusable status.

FA12

You cannot create the pair, because the GAD reserve attribute has been set for the volume that was specified as the primary volume.

FA13

The specified volume is being used by TrueCopy.

FA14

The specified volume is being used by Universal Replicator.

FA15

The GAD pair operation cannot be performed due to one of the following reasons:

• The volume that has been specified as the primary volume of GAD is a primary volume of Thin Image or Thin Image Advanced which is being restored.
• The volume that has been specified as the secondary volume of GAD is a primary volume of Thin Image or Thin Image Advanced.
• The specified volume is a secondary volume of Thin Image or Thin Image Advanced.

FA16

The specified P-VOL or S-VOL is being used by ShadowImage. With the current ShadowImage pair status or pair attribute, you cannot perform GAD pair operations.

FA17

The specified volume is being used by Volume Migration.

FA18

The specified P-VOL or S-VOL is being used by ShadowImage. With the current ShadowImage pair status or pair attribute, you cannot perform GAD pair operations.

FA1B

You cannot create the GAD pair, because the information about the virtual storage machine at the primary site disagrees with the one at the secondary site.

FA1C

The access attribute set by Data Retention Utility for the primary volume cannot be transferred to the secondary volume because Data Retention Utility is not installed in the storage system at the secondary site.

FA1D

You cannot create the GAD pair, by using the specified secondary volume because of either one of the following two reasons:

• The specified secondary volume is already used for the other GAD pair.
• The information about the GAD pair still remains only in the secondary volume.

FA1E

You cannot create the GAD pair, because the primary volume is a command device.

FA1F

You cannot create the GAD pair, because the secondary volume is a command device.

FA20

Internal process is taking time for the specified P-VOL. Retry the operation after a while.

FA21

You cannot create or resynchronize the GAD pair, because the differential bitmap area cannot be secured due to either of the following reasons:

• The primary storage system does not have enough available shared memory.
• The DP pool of the volume specified as the P-VOL does not have enough available capacity.

FA23

Internal process is taking time for the specified S-VOL. Retry the operation after a while.

FA24

You cannot create the GAD pair, because the specified secondary storage system's firmware version does not support GAD consistency groups.

FA25

The operation on the GAD pair failed. The T10 PI attribute setting for the primary volume is not the same as for the secondary volume.

FA26

The operation failed because the firmware version of the local storage system or the remote storage system does not support GAD pair operations using nondisruptive migration.

FA27

You cannot create the GAD pair, because the attribute of the volume specified as a P-VOL is not supported.

FA28

You cannot resynchronize or swap-resync the GAD pair in a GAD+UR configuration, because the following conditions are not satisfied (both must be satisfied):

• The volume must be used as both a GAD P-VOL and a UR P-VOL.
• The volume must be used as both a GAD S-VOL and a UR delta resync P-VOL.

FA29

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is not installed or is a command device.

FA2A

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is in the intervention-required condition.

FA2B

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is blocked.

FA2C

The secondary volume is in an unusable status. If the secondary volume is blocked, recover from the blockade.

FA2F

The create pair operation failed for either of the following reasons:

• An I/O error occurred in the S-VOL.
• The S-VOL cannot be used.

FA30

The pair status of the volume that has been specified as the secondary volume is not PSUS or PSUE.

FA31

The pair status of the volume that has been specified as the secondary volume is not SMPL.

FA32

There is a pinned track on the volume that has been specified as the secondary volume.

FA33

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is in one of the following statuses:

• Blocked
• Being formatted
• Read only

FA35

The GAD pair cannot be created due to one of the following reasons:

• The volume specified as the secondary volume is blocked.
• A pool to which the volume specified as the secondary volume belongs contains a pool volume that is not in the normal status.

FA36

You cannot create or resynchronize the GAD pair, because the remote storage system's firmware version does not support pair creation using volumes that are not DP-VOLs.

FA37

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is a migration volume of a product of another company.

FA3A

You cannot create the GAD pair, because the capacity of the volume that has been specified as the secondary volume is larger than the maximum capacity of a GAD pair that can be created.

FA3B

The GAD pair operation failed because the volume that has been specified as the secondary volume is being used by nondisruptive migration.

FA3C

The device type of the volume that has been specified as the secondary volume is not supported.

FA3D

You cannot create the GAD pair, because the attribute of the volume specified as an S-VOL is not supported.

FA3E

The controller emulation types of the storage systems at the primary site and the secondary site are inconsistent.

FA3F

The global-active device feature is not installed in the storage systems at the secondary site.

FA40

The shared memory that is required to create a GAD pair is not installed on the storage system at the secondary site.

FA41

The volume that has been specified as the secondary volume is not installed.

FA42

You cannot create or resynchronize the GAD pair, because the storage system cache at the secondary site is in one of the following statuses:

• One side is blocked or is transitioning to being blocked
• One side is recovering.
• Recovering

FA43

You cannot create the GAD pair, because the remote path from the storage system at the secondary site to the storage system at the primary site is in either of the following status:

• The number of remote paths is 0 (unspecified).
• The number of remote paths is less than the minimum number.

FA46

You cannot create the GAD pair, because the volume that has been specified as the secondary volume is not a virtual volume of Dynamic Provisioning or Dynamic Tiering.

FA48

The volume operation failed because the attributes of the P-VOL and the S-VOL (VOL_ATTR displayed by running the raidcom get ldev command) are different.

FA49

You cannot create the pair, because the serial numbers of the storage systems for the primary volume and the secondary volume are the same.

FA4B

You cannot create the pair, because the GAD reserve attribute is not set for the secondary volume.

FA4C

You cannot create the pair, because no virtual LDEV ID is set for the secondary volume.

FA4D

No LU path to the specified secondary volume is defined.

FA4E

You cannot create the GAD pair, because the capacities of the primary volume and the secondary volume are different.

FA4F

No LU path to the specified secondary volume is defined.

FA50

One of the following is incorrect:

• A primary volume parameter (port name, host group ID, LUN ID)
• A secondary volume parameter (port name, host group ID, LUN ID)

FA59

Timeout of communication between the storage system at the primary site and the storage system at the secondary site has occurred due to either of the following occurring:

• A physical path between the storage system at the primary site and the storage system at the secondary site is overloaded or the path has a failure.
• The storage system at the primary site or secondary site is overloaded.

FA5B

You cannot create the GAD pair, because the remote paths from the storage system at the primary site to the storage system at the secondary site are in one of the following states:

• The number of remote paths is 0 (unspecified).
• The requirement for the minimum number of paths is not met.

FA60

You cannot create a pair, because the remote storage system product or its firmware version does not support the global-active device function.

FA62

You cannot create the GAD pair, because no virtual LDEV ID is set for the volume specified as the primary volume.

FA63

Failed to create the GAD pair. An external volume for which the Data Direct Mapping attribute is enabled is specified as the primary volume.

FA64

Failed to create the GAD pair. An external volume for which the Data Direct Mapping attribute is enabled is specified as the secondary volume.

FA65

Failed to create the GAD pair. The Data Direct Mapping attribute of the volume that was specified as the secondary volume is enabled, but the M-DKC firmware version does not support the functionality for mapping volumes in an external storage system with a capacity exceeding 4TB.

FA66

Failed to create the GAD pair. The Data Direct Mapping attribute of the volume that was specified as the secondary volume is enabled, but the Data Direct Mapping attribute of the volume that was specified as the primary volume is disabled.

FA67

Failed to create the GAD pair. The Data Direct Mapping attribute of the volume that was specified as the primary volume is enabled, but the R-DKC firmware version does not support the functionality for mapping volumes in an external storage system with a capacity exceeding 4TB.

FA6A

You cannot create or resynchronize the GAD pair because no quorum disk volume is set for the GAD P-VOL and the RCU does not support configurations without quorum disk volume.

FA6B

You cannot create or resynchronize the GAD pair because the setting of the Add Quorum Disk without LDEV option differs between the primary and secondary storage systems.

FA70

The GAD pair cannot be created because the specified mirror ID is the same as the one of a UR pair created using the specified volume.

FA73

The GAD pair cannot be created or resynchronized because the remote storage system does not support I/O preference mode when remote path failed.

FA75

The GAD pair cannot be created because the volume paired with a VSP One SDS Block volume in a UR pair cannot be used for a GAD pair.

• The maximum number of virtual storages was exceeded.
• The volume specified as a secondary volume is a usual volume.
• The volume specified as a secondary volume is an external volume.
• The virtual LDEV ID of the primary volume is already used for a volume other than the one used as the secondary volume.
• The secondary volume already has the same virtual model information as the primary volume.
• The volume specified as a secondary volume is assigned to the namespace of the NVM subsystem.
• The secondary storage system does not have an Open Volume Management license installed.

FA9C

The pair operation cannot be performed because the LDEV specified as a P-VOL or an S-VOL is already assigned to the namespace on the NVM subsystem.

FA9D

A GAD pair cannot be created because one of the LDEVs specified as the P-VOL and the S-VOL is registered as a namespace, and the other is registered as an LU.

FA9E

A GAD pair cannot be created because the namespace ID or the NVM subsystem ID differs between the LDEVs specified as the P-VOL and the S-VOL.

FA9F

A GAD pair cannot be created because the LDEVs specified as the P-VOL and the S-VOL are registered as namespaces, and a UR pair has been created using the LDEVs.

FB30

The command cannot be executed because the shared memory cannot be accessed.

FB40

A GAD pair cannot be created because the virtual storage machine information differs between the specified volume and a volume in the consistency group that contains the specified volume.

FB41

You cannot create the GAD pair, because the operation by the consistency group is performed in the consistency group to which the specified volume is registered.

FB42

You cannot create the GAD pair, because the operation from the remote storage system or the processing of the suspension by failure is performed in the consistency group to which the specified volume is registered.

FB43

You cannot create the GAD pair in the consistency group to which the specified volume is registered, because either of the following volumes exists on the storage system that has the secondary volume:

• The primary volume whose pair status is COPY
• The volume whose I/O mode is Local

FB44

You cannot create the GAD pair in the consistency group to which the specified volume is registered, because either of the following volumes exists on the storage system that has the primary volume.

• The secondary volume whose pair status is COPY
• The volume whose I/O mode is Block

FB45

You cannot create the GAD pair, because the suspension by failure occurs in the consistency group to which the specified volume is registered.

FB46

You cannot create the GAD pair, because you specify a value that is out of range as the consistency group ID.

FB47

You cannot create the GAD pair, because the number of GAD pairs registered in one consistency group or mirror has reached the maximum.

FB48

You cannot create the GAD pair, because you specify a different quorum disk ID from the ID used by the GAD pair registered in the consistency group.

FB49

You cannot create the GAD pair, because you specify a different mirror ID from the ID used by the GAD pair registered in the consistency group.

FB4A

The GAD pair cannot be created or resynchronized because the consistency group contains a GAD pair with a different I/O preference mode when remote path failed.

FB50

The pair operation failed because the operation by the consistency group is performed in the consistency group to which the specified volume is registered.

FB51

You cannot resynchronize or swap resynchronize the GAD pair, because the operation from the remote storage system or the processing of the suspension by failure is performed in the consistency group to which the specified volume is registered.

FB54

You cannot resynchronize or swap resynchronize the GAD pair, because the suspension by failure occurs in the specified consistency group.

FB60

You cannot suspend the GAD pair, because the processing of the suspension by the consistency group is performed in the consistency group to which the specified volume is registered.

FB61

You cannot suspend the GAD pair, because either of the following volumes exists in the consistency group in the storage system that receives a request to suspend a pair.

• The secondary volume whose pair status is COPY
• The volume whose I/O mode is Block

FB62

You cannot suspend the GAD pair, because either of the following volumes exists in the consistency group in the paired storage system of the storage system that receives a request to suspend a pair.

• The primary volume whose pair status is COPY
• The volume whose I/O mode is Local

FB63

You cannot suspend the GAD pair, because the suspension by failure occurs in the specified consistency group.

FB64

You cannot suspend the GAD pair, because the processing of the resynchronization by the consistency group is performed in the consistency group to which the specified volume is registered.

FB65

You cannot suspend the GAD pair by the consistency group, because the operation by the volume is performed in the specified consistency group.

FB6E

You cannot swap suspend the GAD pairs registered to a consistency group by volume.

FB70

You cannot delete the GAD pair, because the operation by the consistency group is performed in the consistency group to which the specified volume is registered.

FB71

You cannot delete the GAD pair, because the suspension by failure occurs in the consistency group to which the specified volume is registered.

FB80

The paircreate command or the pairresync command was rejected for one of the following reasons:

• You specified the -fg option. When you specify the -fg option, confirm that the firmware version of the primary storage system supports GAD consistency groups.
• The specified quorum disk ID is out of range.

If none of the above applies, contact customer support.

FB92

You cannot create or resynchronize the GAD pair, because the differential bitmap area cannot be secured due to either of the following reasons:

• The secondary storage system does not have enough available shared memory.
• The DP pool of the volume specified as the S-VOL does not have enough available capacity.

FBB0

A request to delete the GAD pair was received, but the pair cannot be deleted because the volume paired with the specified volume is shared with ShadowImage, Volume Migration, or nondisruptive migration.

FBB1

A request to delete the GAD pair was received, but the pair cannot be deleted because the volume paired with the specified volume is shared with Thin Image or Thin Image Advanced.

FBE0

The command operating on the GAD pair was rejected because the -f data or -f status option was specified for the paircreate or pairresync command.

FBE1

The command operating on the GAD pair was rejected because the -SM block or -SM unblock option was specified for the paircreate or pairresync command.

FBE8

The command operating on the GAD pair was rejected because the -P option was specified for the pairsplit command.

FBE9

The command operating on the GAD pair was rejected because the -rw option was specified for the pairsplit command.

FBEA

The command operating on the GAD pair was rejected because the -RB option was specified for the pairsplit command.

FBEB

The command operating on the GAD pair was rejected because the -SM block or -SM unblock option was specified for the pairsplit command.

FC10

The command was rejected because the storage system of the specified volume is in one of the following states:

• The storage system includes firmware that does not support GAD.
• The GAD feature is not installed.
• Shared memory for GAD is not increased.

If none of the above applies, contact customer support.

FC12

The same operation or a different operation is already being executed.

FC13

An operation to suspend the pair is being processed because an error was detected.

FC14

You cannot execute the command, because you specify a different consistency group ID from the ID of the consistency group to which the specified volume is registered.

FC16

The operation cannot be performed because the pair operation is being performed in a different GAD pair created using the specified volume of the GAD pair.

FC18

The operation cannot be performed because a different GAD pair created using the specified volume is in a status that the specified GAD pair operation cannot be performed.

FC19

The operation cannot be performed because a different GAD pair created using the specified volume is in a status that does not support data migration.

FC20

You cannot create a pair for one of the following reasons:

• The primary storage system does not have enough available shared memory.
• The DP pool of the volume specified as the P-VOL does not have enough available capacity.
• No shared memory is installed in the primary storage system.
• No Resource Partition Manager license is installed in the storage system of the specified volume.
• The GAD license capacity in the storage system of the specified volume is insufficient.

FC21

You cannot create a pair for one of the following reasons:

• The secondary storage system does not have enough available shared memory.
• The DP pool of the volume specified as the S-VOL does not have enough available capacity.
• No shared memory is installed in the secondary storage system.
• No Resource Partition Manager license is installed in the storage system of the volume to be paired with the specified volume.
• The GAD license capacity in the storage system of the volume to be paired with the specified volume is insufficient.

FC22

You cannot create a pair for one of the following reasons:

• The pair status of the specified volume is not SMPL.
• The specified volume is a single volume or is not the primary volume in the GAD pair.

FC23

You cannot create a pair for one of the following reasons:

• The pair status of the volume to be paired with the specified volume is not SMPL or COPY.
• The volume to be paired with the specified volume is a single volume or is not the secondary volume in the GAD pair.

FC24

You cannot create a pair at the primary site for either one of the following two reasons:

• The capacity of the specified volume is being expanded.
• The pool containing the specified volume is being initialized.
• The volume does not have a virtual LDEV ID.

FC25

You cannot create or resynchronize a pair at the secondary site for one of the following reasons:

• The capacity of the volume to be paired with the specified volume is being expanded.
• The pool of the volume paired with the specified volume is being initialized.
• The virtual LDEV ID of the volume to be paired with the specified volume is duplicated in the virtual storage machine.
• You specified the virtual LDEV ID at the primary site the same as the actual LDEV ID at the secondary site from the volume to be paired with the specified volume. However, the actual information of the virtual emulation type (including the settings for CVS and LUSE) or the virtual SSID is different from the virtual information.
• The virtual LDEV ID of the volume to be paired with the specified volume is already in use.
• The number of LUN paths defined in the volume to be paired with the specified volume exceeds the number of LUN paths that can be used by ALUA.
• The ALUA settings do not match between the primary and the secondary volumes.

FC26

You cannot create a pair, because verification of the remote path between storage systems failed in the storage system of the specified volume.

FC27

You cannot create a pair, because verification of the remote path between storage systems failed in the storage system of the volume to be paired with the specified volume.

FC28

You cannot create a pair for one of the following reasons:

• The mirror count for a single volume is depleted for the specified volume.
• The GAD pairs in two different mirrors are already created using the specified volume.
• The pair management table of the specified volume is depleted.
• A GAD pair is already created using the specified volume registered as a namespace.

FC29

You cannot create a pair for one of the following reasons:

• The mirror count for a single volume is depleted for the volume to be paired with the specified volume.
• The volume to be paired with the specified volume is already being used for another GAD pair.
• The pair management table of the volume to be paired with the specified volume is depleted.
• A GAD pair is already created using the specified volume registered as a namespace.

FC2A

You cannot create a pair for one of the following reasons:

• The storage system is in an internal process or the configuration is being changed due to a different operation.
• The specified mirror ID is the same as the one of a different GAD pair created using the specified volume.

FC2B

The operation cannot be performed because the storage system is enabling or disabling ALUA mode. Wait a while, and then try again.

FC2C

The GAD pair cannot be created with the -nocopy option specified because a GAD pair has already been created with the specified volume.

FC2D

The GAD pair cannot be created because the specified quorum disk ID is the same as the one of a different GAD pair created using the specified volume.

FC2E

The GAD pair cannot be created because a different GAD pair is already created using the specified secondary volume of the GAD pair.

FC30

The pair resynchronization or swap resync was rejected for one of the following reasons:

• The pair status of the volume specified for the pair resynchronization is not PSUS or PSUE.
• The volume specified for the pair resynchronization is not the primary volume of the GAD pair.
• The I/O mode of the volume specified for the pair resynchronization is Block.
• The pair status of the volume paired with the volume specified for the swap resync is not PSUS or PSUE.
• The I/O mode of the volume paired with the volume specified for the swap resync is not Block.

FC31

The pair resynchronization or swap resync was rejected for one of the following reasons:

• The pair status of the volume specified for the swap resync is not SSWS.
• The volume specified for the swap resync is not the secondary volume of the GAD pair.
• The I/O mode of the volume specified for the swap resync is Block.
• The pair status of the volume paired with the volume specified for the pair resynchronization is not SSUS or PSUE.
• The I/O mode of the volume paired with the volume specified for the pair resynchronization is not Block.

FC32

You cannot resynchronize or swap resynchronize the GAD pair for one of the following reasons:

• You execute the command with specifying the consistency group ID to the volume that is not registered to the consistency group.
• You execute the command without specifying the consistency group ID to the volume that is registered to the consistency group.
• You execute the swap resynchronization by the volume to the volume that is registered in the consistency group.

FC33

The GAD pair cannot be resynchronized because the capacity of the primary and secondary volumes is not the same.

FC38

A request to suspend a pair was received, but the pair cannot be suspended because the specified volume meets one of the following conditions:

• An instruction specifying that the primary volume be suspended is directed at the secondary volume.
• An instruction specifying that the secondary volume be suspended is directed at the primary volume.
• The pair status is not PAIR or COPY.

FC39

A request to suspend a pair was received, but the pair cannot be suspended because the volume paired with the specified volume meets one of the following conditions:

• The paired volume is the primary volume, but an instruction specifies that the primary volume be suspended.
• The paired volume is the secondary volume, but an instruction specifies that the secondary volume be suspended.
• The pair status is not PAIR or COPY.

FC3A

You cannot suspend the GAD pair for either of the following reasons:

• You execute the command with specifying the consistency group ID to the volume that is not registered in the consistency group.
• You execute the command without specifying the consistency group ID to the volume that is registered in the consistency group.

FC40

A request to delete a pair was received, but the pair cannot be deleted because the specified volume meets one of the following conditions:

• An instruction specifying that the primary volume be deleted is directed at the secondary volume.
• An instruction specifying that the secondary volume be deleted is directed at the primary volume.
• The pair status is not PSUS, SSUS, SSWS, or PSUE.
• The I/O mode is not Local.
• The volume is shared with a Universal Replicator pair.

FC41

A request to delete a pair was received, but the pair cannot be deleted because the volume paired with the specified volume meets one of the following conditions:

• The paired volume is the primary volume, but an instruction specifies that the primary volume be deleted.
• The paired volume is the secondary volume, but an instruction specifies that the secondary volume be deleted.
• The pair status is not PSUS, SSUS, SSWS, or PSUE.
• The I/O mode is not Block.
• The volume is shared with a Universal Replicator pair.

FC44

The request to delete the virtual LDEV ID forcibly was rejected because the volume of the specified GAD pair is the target volume of nondisruptive migration.

FC49

You cannot change the I/O mode because the specified volume is not a GAD pair volume.

FC4A

You cannot change the I/O mode because the pair is not suspended.

FC7E

A request to create a pair, resynchronize a pair, or perform a swap resync was received, but the request was rejected because the status of the quorum disk meets one of the following conditions:

• The ID of the specified quorum disk is out of range.
• The quorum disk has not been created.
• The specified remote storage system is not the same as when the quorum disk was created.
• The same quorum disk ID is allocated to separate external volumes in the storage systems at the primary and secondary sites.
• The quorum disk is blocked.
• An error occurred on the external path between the storage system at the primary or secondary site and the external storage system for the quorum disk.
• The quorum disk or the external path for the quorum disk failed, or recovery by maintenance is in progress.
• The quorum disk was used to suspend the pair.

B928

The command was rejected because the volume status is SMPL.

B96D

The command was rejected because the volume status is SMPL.