Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Troubleshooting

When issues occur with Universal Replicator, there are a number of different troubleshooting options.

General troubleshooting

When an error occurs in a Universal Replicator pair operation with Device Manager - Storage Navigator, an error message with a four-digit error code and description is displayed. An SVP error code might also be included. See Hitachi Device Manager - Storage Navigator Messages for details about error codes.

You can download Device Manager - Storage Navigator dump files using the Dump tool. If you are unable to resolve an error, use the tool to copy the dump files to a file, and then contact customer support for assistance.

The following table lists error conditions and provides recommended action to resolve the condition.

Error

Recommended action

Device Manager - Storage Navigator hangs, or UR operations do not function properly.

Make sure that the problem is not being caused by the computer or Ethernet hardware or software, and restart the computer. Restarting the Device Manager - Storage Navigator computer does not affect UR operations in progress.

Make sure that UR requirements are met.

Make sure that the primary and secondary storage systems and remote copy connections are powered on, and that NVS and cache are fully operational.

Check all the entered values and parameters to make sure that you entered the correct information on the Device Manager - Storage Navigator computer (for example, secondary storage system serial number, path parameters, P-VOL and S-VOL IDs).

If you are using Performance Monitor, refrain from using it.

An initiator channel-enable LED indicator (on the control window) is off or flashing.

Call customer support for assistance.

Status of pairs and/or remote paths is not displayed correctly.

Check whether you selected correct items and options in UR Device Manager - Storage Navigator windows.

A UR error message appears on the Device Manager - Storage Navigator computer.

Remove the error cause, and then retry the UR operation.

The status of a remote path is not normal.

Check the path status in the View Remote Connection Properties window of HDvM - SN, or by the raidcom get rcu command of CCI, and see Remote path status problems.

The pair status is suspended.

Check the pair status in the View Pair Properties window, and see Troubleshooting by suspend type for suspend types and corrective action.

The pair create or pair resync operation resulted in a timeout error.

  • If the timeout error was caused by a hardware failure, a SIM is generated. See Service information messages (SIMs). If necessary, call customer support, and retry UR operations after the problem is solved.
  • If no SIM was generated, wait for a while (5 or 6 minutes), and then check the pair status of the pairs being created or resynchronized. If the pair status changed correctly, the failed operation completed after the timeout message was issued. If the pair status did not change as expected, heavy workload might have prevented the UR operation from being completed. In this case, retry the UR operation when the system has a lighter workload.
  • If a time-out error occurs during the paircreate operation, the copy operation might not have been executed correctly in the order specified in the Priority field. A time-out error may be caused by the CU configuration or a remote copy path error. Review the error, release the pair with the error, and then retry the paircreate operation.
A pair cannot be created or resynchronized.Verify that the controller board is blocked on the primary storage system. Restore the blocked controller board, and then retry the operation.

A communication error between Device Manager - Storage Navigator and the SVP occurred.

For instructions see the System Administrator Guide for your storage system.

Journal volumes are not registered in the journal.

The error caused the delete journal operation to suspend. Re-register the journal volumes that belong to the journal, and then delete the journal again.

The pairresync operation suspends with a warning message.

This is caused when the following two conditions exist:

  • The Preview list contains two or more pairs belonging to the same mirror.
  • Mirror is defined in the Range column for at least one of these pairs.

To continue processing, do either of the following:

  • Ensure that the Range column displays LU for all pairs in the same mirror.
  • In the Preview list, delete all but one pair in the same mirror.

An error occurs when Apply is clicked for a pair operation.

The error code appears in the right-most column of the Preview list. To view detailed information about the error, right click the error code and select Error Detail.

The pairs cannot be deleted after the pair operations because the pair status changed to Suspending or Deleting.

See Deleting a mirror and specify Force for Delete Mode.

The status of a delta resync pair does not change after you perform the delta resync operation.

One or more of the requirements and prerequisites might not be met (for example, SOM 506 must be enabled). First check the status of all pairs including the delta resync pair for information about the problem, and then review the prerequisite material in Delta resync configuration .

All of the journals in a consistency group are suspended.

All of the journals in a consistency group can be suspended when an error occurs in one of the journals in the consistency group. This takes place under the following conditions:

  • The communications lines between CCI and all primary storage systems are normal.
  • The status of the failed journal is PJSE or PJSF.
  • At least one journal in the consistency group is in normal status.

When these conditions are present, you should be aware of the following information:

  • When an error occurs, the status of the journal changes from normal to PJSE (suspended by error).
  • For an error caused by overflowing capacity, the status changes to PJSF.
  • When the staus of one journal becomes PJSE or PJSF, all other normal journals in PJNN status also change to the PJSE status.
  • If you use CCI and if a journal is in the normal status, it will be shown as PJNN.

If some pairs in the journal become suspended by error but the whole journal does not become suspended, the status of other journals does not change.

A hard disk failure occurs in a pool or in a pool volume to whih a journal volume belongs, or PIN data occurs in a journal volume.

Recover from the hard disk failure or replace the journal volume. See Restoring a pair by adding a reserve journal volume.

The SIMs indicating that a M-JNL Meta overflow warning is generated.

If Inflow Control of the journal option is enabled, the I/O responses from the host might be degraded and it might impact the operations. Suspend the pair, and then resynchronize the pair after resolving the causes for accumulating journal data.

Remote path status problems

There are corrective actions you can take given the status of remote paths between the storage systems.

The following table provides troubleshooting information for the remote paths between the storage systems. If the remote path status is not normal, a hardware failure might occur over the network. A hardware failure can include a port failure between the local storage system and a remote storage system or a network relay device failure. In such cases, resolve the hardware failure first, and then perform the corrective actions described in the table.

Path status

Description

Corrective action

Normal

This path has been successfully established and can be used for UR copy activities.

None required.

Initialization Failed

The link initialization procedure to the remote storage system failed because the physical path connection was missing between the local and remote storage systems.

  • Make sure that the local and remote storage systems are physically and correctly connected.
  • Make sure that you entered the correct remote storage system serial number, model, and local and remote storage system port numbers.
  • Make sure the local and remote storage system ports are configured correctly.

Communication Time Out

Communication between the local and remote storage system timed out.

  • Make sure the remote storage system is powered on and fully functional.
  • Make sure that the network relay devices are properly configured and functional, including cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Port Rejected

The local storage system rejected the logical path link control function because all logical path resources in the local storage system are being used for other connections.

  • Delete all remote paths not in use (for example, (use the Remove Remote Paths window of HDvM - SN, or use the raidcom delete rcu_path command of CCI).
  • Delete all remote connections not in use (for example, use the Remove Remote Connections window of HDvM - SN, or use the raidcom delete rcu command of CCI).
  • Make sure that bidirectional ports are configured both for local and remote storage systems.
  • Reconfigure the ports, and then add the paths and configure the remote storage systems to the local storage systems again.

Pair-Port Rejected

The remote storage system rejected the logical path link control function because all logical path resources in the remote storage system are being used for other connections.

Follow the same corrective actions in Port Rejected.

Serial Number Mismatch

The remote storage system's serial number does not match the specified serial number.

  • Make sure that you entered the correct remote storage system serial number and model, and local and remote storage system port numbers.
  • Make sure the local and remote storage system ports are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Invalid Port Mode

The specified port is not configured as a Bidirectional port, or this path already exists.

  • Make sure the correct port on the local storage system is configured as a Bidirectional port.
  • Make sure that no two paths between local and remote storage system ports have the same settings.
  • Make sure that you entered the correct remote storage system serial number and model, and local and remote storage system port numbers.
  • Make sure that the local and remote storage system ports are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Pair-Port Number Mismatch

The specified port in the remote storage system is physically disconnected from the local storage system.

  • Make sure that you specified the correct remote storage system port number. Correct the port number if necessary.
  • Make sure that the cables between the local and remote storage system ports and between the local and remote storage system switches are connected correctly.
  • Make sure that the topology settings of the local and remote storage system ports are correct.

Pair-Port Type Mismatch

The specified remote storage system port is not configured as a Bidirectional port.

Make sure that the remote storage system port is configured as a Bidirectional port.

Communication Failed

The local storage system connected to the remote storage system successfully, but logical communication timeout occurred.

  • Make sure that the remote storage system port and the relay equipment are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

In Progress

Paths are being created or deleted, or the port attribute is being changed.

Wait until processing is completed.

Logical Blockade

Logical blockade was detected.

Remove the remote connections and remote paths you set, and then restore the remote paths.*

Program Error

A program error is detected.

Restore the path.*

* If you use Device Manager - Storage Navigator, restore remote paths by either of the following methods:

  • In the Remove Remote Connections window, delete the remote connection, and then register a remote connection again in the Add Remote Connection window.
  • In the Remove Remote Paths window, remove the remote path, and then create a remote path again in the Add Remote Paths window.

When using CCI, use the raidcom delete rcu_path command to delete the remote path, and then use the raidcom add rcu_path command to create a remote path again. Using this method, you can restore a remote path.

If you cannot restore the path after deleting the remote storage system or deleting the remote path or re-registering by configuring the primary and secondary storage systems, contact Hitachi Vantara for assistance.

Troubleshooting by suspend type

The following table provides troubleshooting information for suspended pairs by suspend type.

Suspend type

Applies to

Description

Corrective action

By RCU

P-VOL

The primary storage system suspended a pair because it detected an error condition in the secondary storage system. The suspend type for the S-VOL is by MCU.

Clear the error condition at the secondary storage system or S-VOL. If you need to access the S-VOL, release the pair from the secondary storage system. If data in the S-VOL has been changed, release the pair from the primary storage system and then re-create the pair by using the Create UR Pairs dialog box of HDvM - SN, or by the paircreate command of CCI. If data in the S-VOL has not been changed, resynchronize the pair from the primary storage system.

S-VOL Failure

P-VOL

The primary storage system detected an error during communication with the secondary storage system or detected an I/O error during update copy. In this case, the suspend type for the S-VOL is usually by MCU.

Check the path status on the DKC Status dialog box (see Remote path status problems).Clear any error conditions at the secondary storage system and the S-VOL. If you need to access the S-VOL, release the pair from the secondary storage system. If data in the S-VOL has been changed, release the pair from the primary storage system and then re-create the pair by using the Create UR Pairs dialog box. If data in the S-VOL has not been changed, resynchronize the pair from the primary storage system.

MCU IMPL

P-VOL, S-VOL

The primary storage system could not find valid control information in its nonvolatile memory during the IMPL procedure. This error occurs only if the primary storage system is without power for more than 48 hours (power failure and fully discharged batteries).

Resynchronize the pair (pairresync) from the primary storage system. The primary storage system performs an initial copy operation in response to the pairresync request, so that the entire P-VOL is copied to the S-VOL.

Initial Copy Failed

P-VOL, S-VOL

The primary storage system suspended this pair during the initial copy operation. The data on the S-VOL is not identical to the data on the P-VOL.

Alternatively, the maintenance operations are performed for the controller boards, or the shared memory is installed or removed on the primary storage system during the initial copy operation.

Release the pair from the primary storage system. Clear all error conditions at the primary storage system, P-VOL, secondary storage system, and S-VOL. Restart the initial copy operation by using the Create UR Pairs dialog box.

Alternatively, verify that the controller board is blocked. If it is blocked, restore the blocked controller board, and then retry the operation.

MCU P/S OFF

S-VOL

The primary storage system suspended all UR pairs because the primary storage system was powered off.

None. The primary storage system automatically resynchronizes these UR pairs when the primary storage system is powered on.

Troubleshooting hardware problems affecting pairs

The following table provides troubleshooting information for hardware failures affecting Universal Replicator operations. In addition to the following conditions, hardware failures that affect cache memory or shared memory can cause UR pairs to be suspended.

Classification

Causes of suspension

SIM

Recovery procedure

Primary or secondary storage system hardware

Hardware redundancy has been lost due to some blockade condition. As a result, one of the following could not complete: primary-secondary storage system communication, journal creation, copy operation, resynchronize operation, staging process, or de-staging process.

Journals cannot be retained because some portion of the cache memory or shared memory has been blocked due to hardware failure.

The primary storage system failed to create and transfer journals due to unrecoverable hardware failure.

The secondary storage system failed to receive and restore journals due to unrecoverable hardware failure.

The drive parity group was in correction-access status while the URpair was in COPY status.

dc0x

dc1x

dc2x

Depending on the SIM, remove the hardware blockade or failure.

Resynchronize the failed volume pairs (pairresync).

If a failure occurs during execution of the CCI horctakeover command, S-VOLs in SSWS pair status may remain in the master journal. If these volumes remain, execute the pairresync -swaps command on the S-VOLs whose pair status is SSWS (pairresync is the CCI command for resynchronizing pair and -swaps is a swap option). This operation changes all volumes in the master journal to primary volumes. After this operation, resynchronize the pairs.

Communication between the primary and secondary storage systems

Communication between the systems failed because the secondary storage system or network relay devices were not running.

Journal volumes remained full even after the timeout period had elapsed.

dc0x

dc1x

Remove the failure from the primary and secondary storage systems or the network relay devices.

If necessary, increase resources as needed (for example, the amount of cache, the number of paths between primary and secondary storage systems, the parity groups for journal volumes, etc.).

Resynchronize the failed pairs.

RIO overload or RIO failure

An unrecoverable RIO (remote I/O) timeout occurred because the system or network relay devices were overloaded. Or, RIO could not be finished due to a failure in the system.

dc2x

Release failed pairs (pairsplit-S).

If necessary, increase resources as needed (for example, the amount of cache, the number of paths between primary and secondary storage system, the parity groups for journal volumes, etc.).

Re-create failed pairs.

Planned power outage to the primary storage system

The UR pairs were temporarily suspended due to a planned power outage to the primary storage system.

dc8x

No recovery procedure is required. The primary storage system automatically removes the suspension condition when the system is powered on.

Error codes for Device Manager - Storage Navigator

If an error occurs during the operation of Universal Replicator, Universal Replicator outputs an error message in the management client. The error message explains the error and shows an error code. When you contact customer support, report the error code. For error codes to be displayed in the management client, see Hitachi Device Manager - Storage Navigator Messages

Troubleshooting with CCI

When an error has occurred in Universal Replicator pair operation when using CCI, you can identify the cause of the error by referring to the CCI operation log file.

The file is stored in the following directory by default:

/HORCM/log*/curlog/horcmlog_HOST/horcm.log

Where:

* is the instance number.

HOST is the host name.

To identify the error code in the log file, open the CCI log file, and find the error code.

Example: 11:06:03-37897-10413- SSB = 2E31, 3703

Error codes appear on the right of the equal symbol (=). The alphanumeric characters on the left of the comma(,) indicates SSB1 (for example, 2E31), and on the right of the comma (,) indicates SSB2 (for example, 3703).

The following tables describe the CCI error codes for Universal Replicator.

CCI error codes for UR: SSB1 = 2E31, B901, B9E0, B9E1, B9E2, B9E4, D004

Error code (SSB2)

Description

3703

A request of UR Pairresync to change the pair status from HLDE to HOLD was rejected because the PIN data was existed in the journal volume.

3704

A request of UR Paircreate was rejected because the emulation types of the specified master journal and of the restore journal were different.

3705

A request of UR Paircreate or UR Pairresync for delta resync was rejected because the version of the secondary storage system did not support the corresponding command.

3706

A request of UR Paircreate for delta resync was rejected because the specified P-VOL was used as the S-VOL of TrueCopy, and the pair status was not PAIR.

3707

A request of UR Pairresync for delta resync was rejected because of the one of following reasons.

  • The specified P-VOL was the P-VOL of TrueCopy, and the UR pair status was not PAIR.
  • The specified P-VOL was the S-VOL of TrueCopy, and the UR pair status was not SSWS.

3708

The UR pair cannot be created because the specified P-VOL was being shredded.

3709

A request of UR Paircreate or UR Pairresync for delta resync was rejected because the specifying of the restore journal was incorrect.

370B

The UR pair cannot be resynchronized (DELTAJNL parameter specifying), because the specified P-VOL is not in the either of HOLD or HOLDTRNS status. Or, the UR pair cannot be resynchronized (ALLJNL parameter specifying), because the specified P-VOL is not in the either of HOLD, HOLDTRANS, or NODELTA status.

370C

A request of Paircreate or Pairresync for UR pair or UR delta resync pair was rejected because the status of the specified master journal or restore journal could not be transited, or the status transition was in progress.

3719

The operation failed because the specified P-VOL contains data which is being migrated by nondisruptive migration, and the P-VOL is used as a GAD pair.

3722

The Paircreate command was rejected because the emulation type of the selected volume is unsupported.

3726 (VSP 5000 series)

The pair cannot be created because the volume specified as the P-VOL was the system disk.

3728

The Paircreate command was rejected because it was connected with the old model and the specified volume was unsupported.

3729

A request for UR Paircreate was received. However, the pair could not share the volume with TrueCopy because the Remote Replication Extended program product was not installed in the primary storage system.

372B

A pair cannot be created because the secondary storage system does not support the combination of multiple primary and secondary storage systems.

372C

The volume is inaccessible because the P-VOL is blocked.

372D (VSP 5000 series)

The specified volume is used in the system that consists of multiple primary and secondary storage systems. Therefore the command was rejected because the delta resync operation cannot be executed.

372E

A request to create or resynchronize a pair in the system that consists of multiple primary and secondary storage systems was rejected because the Remote Replication Extended program product was not installed in the primary storage system.

3737

The UR pair operation failed because the status of the pair of the other mirror is not settled in the configuration where three UR sites are combined.

3738

A request for pair creation was rejected because the Remote Replication Extended program product was not installed in the primary storage system.

3739

The command was rejected because the journal to which the specified S-VOL belongs does not allow the configuration where three UR sites are combined.

373D

A UR pair or a UR pair for delta resync cannot be created. The P-VOL for the pair must meet the following conditions:

  • A consistency group is not shared among multiple local storage systems and remote storage systems.
  • The volume is not combined with TrueCopy.
  • The volume is not combined with global-active device.
  • The volume is not combined with Volume Migration.

373E

The pair operation failed because the status of a mirror in the journal in which the specified S-VOL belongs is other than Initial or Stopped.

3744

A UR pair or a UR pair for delta resync cannot be created. The S-VOL for the pair must meet the following conditions:

  • A consistency group is not shared among multiple local storage systems and remote storage systems.
  • The volume is not combined with TrueCopy.
  • The volume is not combined with global-active device.
  • The volume is not combined with Volume Migration.

3745

A request to create a UR pair between the primary site and the intermediate site in a cascade configuration where three UR sites are combined was received. However, the command was rejected since the journal to which the P-VOL belongs does not allow the configuration.

3747

In the configuration where three UR sites are combined, a request of UR pair resync (journal resync mode) was received. However, since the volume status was being changed, the command was rejected.

3748

The delta resync pair was not created because the status of the pair with the delta resync P-VOL is not PAIR.

3749

The delta resync pair was not created because the status of the pair with the delta resync P-VOL does not meet the following requirements.

  • The volume is the UR P-VOL and the pair status is PAIR, PSUS, PSUE, or SSWS.
  • The volume is UR S-VOL and the pair status is SSWS.

374B

The pair cannot be created because the volume specified as the P-VOL is used as an external volume for nondisruptive migration and Cache Through is set as the cache mode.

374D

The pair cannot be created because the volume specified as the P-VOL is used as an external volume for nondisruptive migration and also used as a volume for a Volume Migration pair.

3752

The pair cannot be created because of one of the following:

  • The secondary storage system's microcode version does not support connection with the primary storage system.
  • The specified S-VOL is being used by TrueCopy.

3753 (VSP 5000 series)

A UR pair for the 3DC delta resync configuration where three UR sites are combined cannot be created. To create the pair, all storage systems in the sites must support the 3DC configuration of UR.

3754 (VSP 5000 series)

The pair cannot be created because one of the storage systems does not support the 3DC UR function.

3755

The command was rejected because the specified S-VOL is used as an S-VOL in another mirror, and the pair status is not in SSWS status.

3756

The pair cannot be created because the secondary storage system does not support the Path Group ID, which was specified as other than 0.

3759

UR or UR delta resync pair creation failed because the remote storage system does not support the combined configuration of GAD function and UR function.

375A

The specified secondary storage system does not support global storage virtualization.

375B

The specified primary storage system does not support global storage virtualization.

375C

The pair cannot be created because no virtual LDEV ID is set for the volume specified as the P-VOL.

375D

The pair cannot be created because no virtual LDEV ID is set for the volume specified as the S-VOL.

3766

The pair cannot be created because the P-VOL is used by the GAD pair.

3767

The pair cannot be created because the S-VOL is used by the GAD pair.

3768

The pair cannot be created because the P-VOL is a GAD reserve volume.

3769

The pair cannot be created because the S-VOL is a GAD reserve volume.

376A

The internal process to secure tier memory difference has timed out. Wait 5 minutes, and then retry the operation.

If this error occurs again, use Performance Monitor to find and resolve the specific problem. If retrying does not work, contact customer support.

376B

The 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 primary storage system is insufficient.
  • Free area for Dynamic Provisioning pool specified as the P-VOL is insufficient.

377B

UR pair creation failed. The P-VOL of the specified UR pair must meet both of the following conditions:

  • The P-VOL of the specified UR pair is the P-VOL of a GAD pair.
  • The status of the GAD pair to which the P-VOL of the specified UR pair belongs is PAIR.

If the GAD pairs in two different mirrors share the P-VOL with the specified UR pair, the GAD pairs in two different mirrors must meet both of the following requirements:

  • The P-VOL of the GAD pair in one mirror shares the specified UR P-VOL and the pair status is COPY.
  • The S-VOL of the GAD pair in the other mirror shares the specified UR P-VOL and the pair status is COPY or PAIR.

377C

UR pair creation or UR delta resync pair creation failed because the specified mirror ID is used for a GAD pair.

377D

UR pair creation or UR delta resync pair creation failed because of one of the following:

  • The GAD pair that is combined with the specified P-VOL does not belong to a consistency group.
  • Another delta resync pair that uses the specified journal or the GAD pair that is combined with UR pair belongs to another CTG.

377E

UR pair creation or UR delta resync pair creation failed because the specified journal is combined with another GAD consistency group.

377F

The UR delta resync pair could not be created, or the UR pair waiting for delta resync could not be resynchronized.

3789

UR delta resync pair creation failed. The P-VOL and S-VOL of the specified UR delta resync pair must meet both of the following conditions:

  • When changing the configuration to use Universal Replicator and global-active device,
    • The P-VOL of the UR delta resync pair is also used as the S-VOL of a GAD pair.
    • The S-VOL of the UR delta resync pair is not used as the UR pair that is created in another mirror.
  • When recovering from a failure in a configuration using UR and GAD,
    • The P-VOL of the UR delta resync pair is also used as the P-VOL of a GAD pair.
    • The S-VOL of the UR delta resync pair is also used as the UR pair that is created in another mirror.

378A

UR pair creation failed. The following two volumes that are combined with the P-VOL and S-VOL of the specified UR pair must match:

  • The S-VOL of the GAD pair that is combined with the P-VOL of the specified UR pair.
  • The P-VOL of the UR delta resync pair that is combined with the S-VOL of the specified UR pair.

378B

Delta resync failed because the number of UR pairs and UR delta resync pairs are different in the restore journal. Due to this failure, the UR delta resync pairs that are not combined with UR pairs are deleted automatically.

378C

Delta resync failed because the status of the GAD pair that is combined with the specified P-VOL is not SSWS.

378D

Resynchronization failed because of one of the following:

  • The GAD pair status is not PAIR, COPY, PSUS, PSUE, or SSWS.
  • The status of the UR delta resync pair is not HLDE.

If the GAD pairs in two different mirrors share the P-VOL with the specified UR pair, the GAD pairs in two different mirrors must meet both of the following requirements:

  • The P-VOL of the GAD pair in one mirror shares the specified UR P-VOL and the pair status is COPY, PAIR, PSUS, or PSUE.
  • The S-VOL of the GAD pair in the other mirror shares the specified UR P-VOL and the pair status is COPY or PAIR.

37A0

UR delta resync pair creation failed. The P-VOL of the specified UR delta resync pair must meet one of the following conditions:

  • The specified P-VOL is the S-VOL of the GAD pair, and the pair status is PAIR.
  • The specified P-VOL is the P-VOL of the GAD pair, and the I/O mode is Block.

A UR delta resync pair cannot be created, because the GAD pairs in two different mirrors share the P-VOL with the specified UR delta resync pair.

37A1

UR delta resync pair creation failed. The following two volumes that are combined with the P-VOL and S-VOL of the specified UR delta resync pair must match:

  • The S-VOL of the GAD pair that is combined with the P-VOL of the specified UR delta resync pair.
  • The P-VOL of the UR pair that is combined with the S-VOL of the specified UR delta resync pair.

37AE

In a cascade configuration where the three UR sites are combined, the request to create a UR pair between the primary and intermediate sites was received. However, the command was rejected because another mirror to which the intermediate site belongs in the journal is used as the P-VOL for the UR pair between the intermediate and secondary sites and also the volume between the primary and intermediate sites is DP-VOL.

37AF

Pair creation failed because the volume specified as the P-VOL is a pool volume.

37B2

Pair creation failed because the volume specified as the P-VOL is an external volume of which data direct mapping attribute is enabled.

37B3

Pair creation failed because the attribute of the volume specified as the P-VOL is invalid.

37B6

Pair creation failed because the data direct mapping attribute of the volume specified as the P-VOL is enabled, and the function of the R-DKC firmware version for mapping external volumes larger than 4 TB is not supported.

37B7

UR pair operation failed. T10 PI attribute settings of the P-VOL and of the S-VOL are different.

37BD (VSP 5000 series)

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.

8C19

The pair cannot be created because the specified CTG ID is out of range of supporting.

8C1A

The pair cannot be created or resynchronized because the specified journal ID is incorrect.

8C1B

The pair cannot be created because the specified journal ID is out of range of supporting.

8C1E

The pair cannot be created because of the one of following reasons:

  • The microcode version of the specified primary storage system does not support connection with the specified secondary storage system.
  • The specified primary storage system does not support connection with the specified secondary storage system.

8C1F

The pair cannot be created because the virtual ID is not set for the specified S-VOL.

8C20

The request to update options was rejected because the specified journal ID or mirror ID is incorrect.

8F00

The pair cannot be created because the specified volume was an external volume.

8F04

The command was rejected because an internal logical error occurred.

8F10

The pair operation failed because the specified P-VOL is one of the following:

  • An SI S-VOL that is not in PSUS status
  • An SI volume in Reverse Copy status

8F11

The pair cannot be created. The processing of volume migration could not be stopped because the P-VOL was being migrated by Volume Migration.

8F17

The pair cannot be created because the specified volume was in the state of online from the host.

8F18

The pair cannot be created because the specified volume was used in a pair on another program product.

8F19

The pair cannot be created because the emulation type of the specified volume was unusable.

8F1B

The pair cannot be created because the specified P-VOL is already paired.

8F1C

The pair cannot be created because the specified P-VOL is not in the PSUS status.

8F1E

The Universal Replicator pair cannot be created because cache or shared memory is undergoing restoration.

8F1F

The Universal Replicator pair cannot be created because cache or shared memory is blocking.

8F21

The pair cannot be created or resynchronized due to one of the following reasons.

  • The specified volume was a TC P-VOL.
  • The specified volume was a TC S-VOL belonging to a consistency group consisting of multiple primary and secondary storage systems.
  • Unavailable configuration of the status transition.

8F24

The pair cannot be created because a path between the devices was not created.

8F25

The pair cannot be created or resynchronized because PIN was existed in the specified volume.

8F28

The pair cannot be created or resynchronized because it could not access to the specified P-VOL or S-VOL.

8F29

The pair cannot be created because the specified master journal was unusable.

8F2A (VSP 5000 series)

The pair cannot be created because the specified P-VOL is a Flash Copy S-VOL.

8F2B

The pair cannot be created because the protect attribute of the Data Retention Utility was set for the specified P-VOL.

8F33

The pair cannot be created because the specified volume was used in a pair on the TrueCopy or the ShadowImage.

8F35

The command was rejected because the physical volume with the specified P-VOL is blocked.

8F38

The following programs for OPEN systems might not be installed, or the licenses of them might be expired. Confirm settings for:

  • TrueCopy
  • Universal Replicator

8F39

The pair cannot be created because the program product of UR was not installed.

8F46

The pair cannot be created because cache CL2 is in abnormal status.

8F47

The pair cannot be created because cache CL1 is in abnormal status.

8F4D

The pair cannot be created or resynchronized due to the following contributing factors:

  • A journal is not registered in the secondary storage system.
  • A volume in the journal which is registered in the secondary storage system is blocked.

8F50

The pair cannot be created or resynchronized because the load of the processing was high. Wait about 5 minutes, and then retry the operation.

8F53

The pair cannot be created because the status of the configuration could not be transited.

8F58

The pair cannot be created or resynchronized because of the one of following reasons.

  • The pair status of the specified S-VOL differed from the one of P-VOL.
  • The state of restore journal differed from the state of master journal.

8F67

The pair cannot be created because the specified secondary storage system did not support the external volume.

8F6D

The pair cannot be created because the specified volume was a command device.

8FEA

The pair cannot be created because the P-VOL is used for Thin Image.

8FEC

The pair cannot be created because the P-VOL is used for Thin Image.

9100

The command cannot be executed because user authentication is not performed.

B91B

The required shared memory for operating UR is not installed.

B992

The information of the consistency group cannot be retrieved, because Universal Replicator was not installed.

B9C0

The source of command device has run out. Set to OFF the command device and to ON again from Hitachi Device Manager - Storage Navigator.

EB2A

The Universal Replicator pair for delta resync cannot be resynchronized due to one of the following reasons:
  1. In a 3DC configuration with TrueCopy and Universal Replicator, the updated data for the TrueCopy pair and that for the Universal Replicator pair are not the same, or an I/O is issued from the host to the secondary volume of the Universal Replicator pair.
  2. In a 3DC configuration with three Universal Replicator sites, an I/O is issued from the host to the secondary volume of the Universal Replicator pair.

Delete the pair that is ready for delta resync, and then copy all data of the primary volume to the secondary volume.

CCI error codes for UR: SSB1 = B9E1

Error code (SSB2)

Description

B901

The command was rejected because the specified device is a command device.

CCI error codes for UR: SSB1 = B9E2

Error code (SSB2)

Description

B901

The pair cannot be deleted because the mirror ID is invalid.

CCI error codes for UR: SSB1 = B901, B9E0, B9E1, B9E2, B9E4, D004

Error code (SSB2)

Description

B900

A status of UR pair was acquired at the time of unavailable to use the UR during the power-on. Retry the operation.

B902

The command was rejected because the mirror ID is invalid. In a 3DC configuration with three Universal Replicator sites, an I/O is issued from the host to the secondary volume of the Universal Replicator pair.

B907

The command was rejected because the volume was unpaired.

B909

The command was rejected because the mirror ID is invalid.

B90A

The S-VOL hide mode is not supported.

B90D

The command was rejected because the UR program product is not installed.

B90E

The command was rejected because the path is not set between the systems.

B910

The settings of the journal option could not be updated.

B912

The command was rejected because no journal was registered.

B913

The command was rejected because the system configuration does not allow these operations.

B920

The pair cannot be created because the system identifier is not correct (left-most number in the 6-digit serial number).

B94B

The command was rejected because the UR configuration was changed. Check the status of the UR pair.

B9F8

The command was rejected because no journal was registered.

DB02

A request for status change was rejected because the status could not be changed (for example, the pair volumes were not unpaired when the Paircreate was requested, or were in a status other than PSUS when the Pairresync was requested).

DB03

A request of UR Pair status transition was rejected because the pair was in the state of Suspending or Deleting.

DB07

UR pair status cannot be transited during the power-on processing.

DB08

UR pair status cannot be transited during the power-off processing.

DB0C

The command was rejected because the specification was volume instead of group.

E843

The command was rejected because the CLPR ID of the specified volume differed from the CLPR ID of the journal.

E847 (VSP 5000 series)

An operation request for the journal, which was used in the system that consists of single primary and secondary storage system, was rejected because the specified volume is defined to be used in the system that consists of multiple primary and secondary storage systems.

E848 (VSP 5000 series)

An operation request for the journal, which was used in the system that consists of multiple primary and secondary storage systems, was rejected because the specified volume is defined to be used in the system that consists of single primary and secondary storage system.

E866

The specified consistency group ID is already used.

E869

The operation cannot be performed because the specified restore journal was used in another mirror and the mirror status was Halting or Stopping. Retry the operation after the mirror status is changed to a status other than Halting or Stopping.

E86E

You cannot use as data volume because shared memory is not implemented for specified LDEV number.

E871

The command was rejected because the path between the storage devices for the both-way was not defined. Check whether the bidirectional normal path was defined or not.

E878

The command was rejected because the data volumes of 3390-9A and other than 3390-9A coexist in the specified journal.

E87B

The command was rejected because the specified journal was unregistered.

E87C

Journal volume is not registered in the specified journal.

E87D

The command was rejected because the specified volume was not for the UR pair.

E87E

The command was rejected because the specified P-VOL or S-VOL was a journal volume.

E880

The command was rejected because the emulation type was different between the specified P-VOL or S-VOL and the journal volume.

E881

The command was rejected because of the power-on processing.

E882

The command was rejected because the emulation type of the specified master journal or the restore journal was invalid.

E883

The specified mirror ID number or the CTG ID differs from the registered mirror ID number or the CTG ID.

E888

The command was rejected because a volume in the specified journal was used for maintenance.

E889

The command was rejected because the specified journal was already used in another UR's mirror ID.

E890

The command was rejected because of one of following:

  • The specified volume is registered in another journal.
  • The specified volume is registered in the same mirror of the same journal.
  • The volume specified as the S-VOL is registered in another mirror of the same journal.
  • When creating a pair using the journal which is not supported in the system of the configuration where three UR sites are combined, a pair creation command for another mirror was received in the same journal.

E891

The command was rejected because the number of pairs that are registered in the specified master journal or restore journal was already reached the maximum number.

E894 (VSP 5000 series)

When creating a pair using journal in the configuration with three UR sites, a request of pair creation of the third mirror was received in the same journal; therefore, the command was rejected.

E897

A pair creation request was received, but the command was rejected because of one of the following reasons:

  • The specified primary and secondary journals do not permit the configuration combining three UR sites.
  • The specified restore journal is already used as a restore journal of another mirror.
  • The paired journal of the specified mirror is already used by another mirror.
  • The specified primary or secondary journals are created using versions that do not support a 3DC multi-target configuration with three UR sites or a 3DC cascade configuration with three UR sites. See Configuration workflow .

E898

The command was rejected because the specified secondary journal is already a secondary journal in another mirror.

E89A

The command was rejected because the path between the storage devices for the both-way was not defined. Check whether the bidirectional normal path was defined or not.

E89B

The command was rejected because the specified master journal or the restore journal remembered the state of connection with another system in the past. Specify another journal, or delete the journal once, and then retry the registration again.

E8A2

The command was rejected because the Serial Number, model, or Path Group ID of the specified secondary storage system is wrong.

E8A6

The specified journal ID is unregistered.

E8A7

Journal volume is unregistered on the specified journal.

E8A8

The command was rejected because the specified volume was not for a UR pair or was a volume of another journal.

E8A9

UR copy pair cannot be suspended because of the power-on processing.

E8B6 (VSP 5000 series)

The command was rejected because the mirror ID of the specified restore journal was already used.

E8B8

The command was rejected because the volume in the specified journal was used for maintenance.

E8F7

The command was rejected because there are multiple journals in the specified consistency group.

E8FB

A logic error occurred in the system, and the command was rejected.

EA00

The command was rejected because the specified P-VOL was already used as an S-VOL.

EA01

The command was rejected because the specified P-VOL was already used by another UR pair.

EA02

The command was rejected because the specified S-VOL was used as the P-VOL.

EA03

The command was rejected because the specified P-VOL was already used by another UR pair.

EA07

The command was rejected because the number of the UR pair registrations in the primary journal exceeds the upper limit.

EA08

The command was rejected because the number of UR pair registrations in the secondary journal exceeds the upper limit.

EA09

The command was rejected because the state of master journal was other than Initial, Active, or Stopped.

EA0A

The command was rejected because the state of restore journal was invalid.

EA12

The command was rejected because the specified S-VOL was not in SSWS status.

EA13

The command was rejected because the request was received for the S-VOL as the P-VOL.

EA15

The command was rejected because the request was received for the P-VOL as the S-VOL.

EA18

The command was rejected because the pair status was not PSUS.

EA19

The command was rejected because the state of journal was not Stopped.

EA1B (VSP 5000 series)

The command was rejected because the journal could not execute the suspend transition, that is, the journal was in HLDE or PSUE status.

EA1C

The command was rejected because the specified secondary journal was not in the Stopped status.

EA1E

The command was rejected because the request was received for the S-VOL as the P-VOL.

EA20

The command was rejected because the request was received for the P-VOL as the S-VOL.

EA22

The command was rejected because the state of journal was not Stopped.

EA25

The command was rejected because the state of S-VOL was not SSWS.

EA29

The command was rejected because the state of master journal was other than Active or Stopped.

EA2C

The command was rejected because the state of restore journal was other than Active or Stopped.

EA33

The command was rejected because the state of mater journal was other than Active.

EA36

The command was rejected because the state of restore journal was other than Active.

EA37

The pair suspend request was received but was rejected because the restore journal status was other than Active or Stopped.

EA3A

The command was rejected because the specified S-VOL was in the state of status transition.

EA3B

The command was rejected because the specified S-VOL was in the state of Suspending.

EA40

The command was rejected because the desired capacity exceeded the charging capacity of the primary storage system's program product.

EA41

The command was rejected because the desired capacity exceeded the charging capacity of the secondary storage system's program product.

EA46 (VSP 5000 series)

In the intermediate site of the cascade configuration with three UR sites, the UR pair deletion and suspend commands were received. However, the commands were rejected because the status of the specified journal which is connected to the mirror of the specified journal is Active.

EA89

The command was rejected because the paircreate or pairresync cannot run with the journal’s attribute or mirror status.

EA8A

The command was rejected because the pair status could not be changed during the power-on or power-off processing.

EA8B

The command was rejected because the specified volume is used in the system that consists of multiple primary and secondary storage systems.

EA95

The command was rejected because the volume specified for the P-VOL was initializing the pool of Dynamic Provisioning.

EA9F (VSP 5000 series)

In the configuration with three UR sites, a request of UR pair resync (journal resync mode) was received. However, the command was rejected because the specified journal did not exist, or no pair existed in the specified journal.

EAA2

The command was rejected because the desired capacity exceeded the charging capacity of the primary storage system's UR. Check the license capacity as well as the related program product.

EAA3

The command was rejected because the desired capacity exceeded the charging capacity of the secondary storage system's TrueCopy. Check the License capacity as well as the related Program product.

EAA5

The command was rejected because the desired capacity exceeded the charging capacity of the secondary storage system's UR. Check the license capacity as well as the related program product.

EAA6

The command was rejected because the desired capacity exceeded the charging capacity of the primary storage system's TrueCopy. Check the license capacity as well as the related program product.

EAAB (VSP 5000 series)

In the configuration with three UR sites, a request of UR pair resync (journal resync mode) was received. However, the command was rejected because the specified option is incorrect.

EAB6

The 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 primary system is insufficient.
  • Free area for Dynamic Provisioning pool specified as the P-VOL is insufficient.

EAB7

The paircreate operation failed because no extended shared memory is installed in the primary storage system. Install extended shared memory in the primary storage system and then repeat the operation.

EAB8

The 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.

EAB9

The paircreate operation failed because no extended shared memory is installed in the secondary storage system. Install extended shared memory in the secondary storage system and then repeat the operation.

EABC

The pair operation failed because shared memory is not installed in the specified LDEV number.

EAD7

The command was rejected because the capacity is different between the UR P-VOL and S-VOL.

EAE5

The command was rejected because the specified P-VOL or S-VOL is in the process of having the capacity changed by Dynamic Provisioning.

EAF6

The command was rejected because the pair was in the state that was unavailable to transit.

EB24

The UR delta resync pair cannot be created because the specified UR S-VOL is in either one of the following statuses:

  • The volume cannot be used as the UR volume for the delta resync operation.
  • The status of the UR pair is other than PAIR.

EB25

The UR delta resync pair cannot be created because the specified UR S-VOL is in either one of the following statuses:

  • The volume cannot be used as the UR volume for the delta resync operation.
  • The status of the UR pair is the status other than PAIR or SUSPEND.

EB27

UR pair creation failed because the GAD S-VOL that is combined with the specified P-VOL is not combined with the UR delta resync pair.

EB28

The command was rejected because the Remote Replication Extended program product was not installed in the secondary storage system.

EB29

The command was rejected because the delta resync settings are configured to the primary and secondary storage systems.

EB2D

The command was rejected because shared memory for operating UR is not installed.

EB2F (VSP 5000 series)

The command was rejected because the specified UR pair was used in the system that consists of multiple primary and secondary storage systems.

EB30

The command was rejected because the specified mirror ID was invalid.

EB37

The command was rejected because the microcode is being exchanged or the micro program exchange operation is suspended.

EB48

The UR delta resync pair cannot be created due to one of the following reasons:

  • The P-VOL of the UR pair is different from the P-VOL of the TrueCopy pair.
  • The serial number of the primary storage system that is recognized by the P-VOL and S-VOL is different.

EB4C

A pair cannot be created because the restore journal was not registered.

EB4D

A pair cannot be created because the master journal was not registered.

EB4F (VSP 5000 series)

The UR pair cannot be created because the timer type of master journal and restore journal is different.

EB50

The command was rejected because the specified S-VOL is in one of the following conditions:

  • Protected
  • Cannot be used
  • A ShadowImage S-VOL
  • (VSP G/F350, G/F370, G/F700, G/F900, VSP E series) A ShadowImage reserved volume
  • (VSP G/F350, G/F370, G/F700, G/F900, VSP E series) A Volume Migration reserved volume
  • Used by Universal Replicator

EB51

The command was rejected because PIN data existed in the specified S-VOL.

EB52

The command was rejected because the specified S-VOL cannot be accessed.

EB53

The command was rejected because the physical volume with the specified S-VOL is blocked.

EB54

The pair cannot be created because the specified S-VOL is used as an external volume mapped for online data migration.

EB57

The command was rejected because the specified S-VOL was online from the host.

EB58

The command was rejected because the specified journal volume or S-VOL was reserved or being used in the storage system. Check the status of the volume.

EB59

The command was rejected because the specified S-VOL was being migrated by Volume Migration. Check the status of the volume.

EB5B

The command was rejected because the access attribute was set to the specified P-VOL or S-VOL by the Data Retention Utility.

EB5C

The command was rejected because an internal logical error occurred.

EB5E

The command was rejected because the S-VOL was already paired.

EB5F

The command was rejected because the program product of UR was not installed in the secondary storage system.

EB60

The command was rejected because the P-VOL capacity is not the same as the S-VOL’s.

EB61

The command was rejected because the path between the primary and the secondary storage systems was not valid.

EB62

The command was rejected because the specified P-VOL was a command device.

EB63

The command was rejected because the restore journal was already linked with another journal.

EB64

The command was rejected because the desired capacity exceeded the charging capacity of the program product.

EB65

The command was rejected because of the abnormal end which is related to the charging capacity of the program product.

EB66

The command was rejected and the retry processing was ordered because P-VOL SUSPENDING was detected when the CCI horctakeover (resync) command was executed.

EB6B (VSP 5000 series)

The command was rejected because a pair is already created with the specified S-VOL by using Compatible FlashCopy® V2.

EB6C

The UR pair create processing was doubly executed:

  • There are no problems if the initial copy operation is restarted when the primary storage system is powered off.
  • There are no problems if a UR pair is created when the primary storage system is reset.

EB6E

The command was rejected because the UR program product was not installed in the primary storage system.

EB70

The command was rejected because the specified S-VOL is assigned to a copy pair of other program products.

EB73

The command was rejected because the specified S-VOL is the system disk.

EB78

The command was rejected because the specified data volume is a command device.

EB79

The command was rejected because the specified data volume is online.

EB7A

The command was rejected because the journal cache of the restore journal was remained.

EB7D

The command was rejected because the specified S-VOL is an external volume.

EB7E

The pair operation failed because the specified S-VOL is in one of the following statuses.

  • The specified S-VOL is being used for a ShadowImage pair.
  • The specified S-VOL is a reserved volume.
  • UR P-VOL and S-VOL are DP-VOL, and the specified S-VOL is being used as ShadowImage P-VOL.
  • UR P-VOL and S-VOL are DP-VOL, and the specified S-VOL is the source volume of Volume Migration.
  • UR P-VOL and S-VOL are DP-VOL, and the specified S-VOL is being used as Thin Image P-VOL.

EB7F

The command was rejected because the emulation type of the specified S-VOL was unsupported.

EB80

The command was rejected because the specified volume was the V-VOL or the pool-VOL. Check the status of the volume.

EB87

The command was rejected because the path from the secondary storage system to the primary storage system is not set, or the volume used as the S-VOL is not paired.

EB88

The UR pair cannot be created because of one of the following:

  • The specified S-VOL was being used as a ShadowImage S-VOL.
  • The specified S-VOL was Not Ready, which means that the data drive (HDD, SSD, SCM, or FMD) cannot be used.

EB89

The command was rejected because the emulation types of the specified P-VOL and S-VOL were not the same.

EB8A

The UR pair could not be created because of one of the following statuses:

  • The emulation type of the master journal and restore journal you specified is different.
  • If you are changing the configuration to use both UR and global-active device, the P-VOL of the UR pair for delta resync and the S-VOL of the global-active device pair do not match.

EB8E

The pair cannot be created because the S-VOL is in a LUSE configuration.

EB94

The command was rejected because the specified pair could not transit the status.

EB9F

The command was rejected because the specified S-VOL was not mounted on the secondary storage system.

EBA0

The command was rejected because the specified S-VOL was not mounted on the secondary storage system.

EBA7

The command was rejected because the volume specified for the secondary volume was in either one of the following status.

  • Increasing the capacity by Dynamic Provisioning.
  • Releasing the page of Dynamic Provisioning.
  • Initializing the pool of Dynamic Provisioning.
  • The Data Direct Mapping attribute of Dynamic Provisioning which is not supported by a storage system in the primary site is enabled.

EBAF

The command was rejected because the license capacity of the Data Retention Utility in the secondary storage system exceeds the setting value. Check the license capacity setting for Data Retention Utility in the secondary storage system.

EBC6 (VSP 5000 series)

The command was rejected because the specified UR S-VOL was used by either ShadowImage or Compatible FlashCopy® V2.

EBCA

The command was rejected because the journal restore operation is in progress in the UR pair through another mirror ID.

  • If the UR pair with another mirror ID is in Suspending status, re-issue the request when the pair status is changed to the Suspend status.
  • If the UR pair with another mirror ID is in the PAIR status, reissue the request after a while.

EBCE (VSP 5000 series)

The command was rejected because un-updated differential data exists in the specified S-VOL.

EBCF

The UR Pairresync (journal resync mode that forcibly copies all data) was received because of the UR Pairresync (delta resync) failed. The command was rejected because the UR pair was not in HOLD status.

EBD9

The command was rejected because the desired capacity exceeded the charging capacity of the secondary storage system's TrueCopy. Check the license capacity as well as the related program product.

EBDB

The command was rejected because the desired capacity exceeded the charging capacity of the secondary storage system's UR. Check the license capacity as well as the related program product.

EBDC

The command was rejected because the processing load of the storage system is heavy. Execute the command again after a while.

EBE0

The command was rejected because the specified S-VOL is already used in a UR delta resync pair.

EBE1

The command was rejected because the all S-VOLs of the specified restore journal were not the another UR's S-VOLs.

EBE2

The resynchronization of the UR delta resync pair was rejected due to either of the following reasons:

  • Update data of TrueCopy (master journal of the UR delta resync pair operation) is inconsistent with the update data of the restore journal of the UR pair.
  • Host I/O is updated for the UR S-VOL.

In the Edit Mirror Options window, specify Entire Copy for Delta Resync Failure to resynchronize the UR pair.

EBE5

The command was rejected because the journal volume of specified restore journal was blocked.

EBF3 (VSP 5000 series)

The command was rejected because the split time of the ATTIME Suspend function is restored.

EBFD

The command was rejected because the specified restore journal was not registered.

F908

The pair cannot be created because of one of the following conditions regarding the specified P-VOL or S-VOL:

  • Virtual access mode is disabled for the volume registered in the mirror, but is enabled for the specified volume.
  • Virtual access mode is enabled for the volume registered in the mirror, but is disabled for the specified volume.
  • The specified volume whose virtual access mode is enabled has an incorrect virtual system serial number or model.

F909

The pair cannot be created because of one of the following conditions regarding the specified P-VOL or S-VOL:

  • Virtual access mode is disabled for the volume registered in the journal group, but is enabled for the specified volume.
  • Virtual access mode is enabled for the volume registered in the journal group, but is disabled for the specified volume.
  • The specified volume whose virtual access mode is enabled has an incorrect virtual system serial number or model.

F90A

The pair cannot be created because the virtual LDEV ID is not set for the volume specified as the P-VOL.

F90C

The pair or delta resync pair cannot be created because the specified journal does not match the journal associated with the GAD CTG.

CCI error codes for Universal Replicator: SSB1 = B9E2

Error code (SSB2)

Description

B9E0

The command was rejected because the function for deleting pairs forcibly is not supported.

CCI error codes for UR: SSB1 = B9FE

Error code (SSB2)

Description

B902

Journal volumes are not registered in the specified journal.

CCI error codes for UR: SSB1 = B912

Error code (SSB2)

Description

B96D

The command was rejected because the volume status is SMPL.

Service information messages (SIMs)

When service is required, storage systems generate service information message (SIMs). SIMs are generated by the channel and storage path microprocessors and by the SVP. All SIMs related to Universal Replicator processing are reported by the SVP. SIMs are classified according to the following severity levels: service, moderate, serious, or acute.

The following figure shows a typical 32-byte SIM. The six-digit reference code consists of bytes 22, 23, and 13. The reference code identifies the possible error and the severity level. The SIM type (byte 28) indicates the component that experienced the error. When the value of byte 22 is 21, the SIM is a control unit SIM. When the value of byte 22 is dx (where x is an arbitrary character), the SIM is a device SIM.

GUID-479B838B-F882-4E8B-84D2-CA775B215F49-low.png

The SIMs are displayed in the Alert tab of the Storage System window of Device Manager - Storage Navigator or can be checked by maintenance utility. For details, see the System Administrator Guide. If SNMP is installed and operational, each SIM results in an SNMP trap being sent to the appropriate hosts. Each time a SIM is generated, the amber Message LED on the control window (under the Ready and Alarm LEDs) turns on as an additional alert for the user.

For details about SNMP operations, see the System Administrator Guide for your storage system. For details about SIM reporting, see the Hardware Guide for your storage system.

When a UR pair is split by the user or suspended due to an error condition, a SIM is issued by the primary storage system, secondary storage system, or both.

  • SIMs generated by the UR primary storage system include the device ID of the P-VOL (byte 13).
  • SIMs generated by the UR secondary storage system include the device ID of the S-VOL (byte 13).

SIM reference code tables

The following tables list the SIM reference codes related to Universal Replicator operations. To clear UR-related SIMs from the SVP, contact customer support.

For more information about SIM reference codes, see the Hitachi Alert Notification Guide, SIM Reference Guide, or System Administrator Guide.

The following table lists and describes the SIMs that require intervention.

SIMs requiring intervention

Reference code

Severity

Description

System generating the SIM

SVP log file

Byte 22

Byte 23

21

80

Moderate

A remote path is blocked due to failure.

Primary, Secondary

SIM log

dc

0x

Serious

The P-VOL has been suspended.

Path recovery is impossible.

Primary

SIM log

dc

1x

Serious

The P-VOL has been suspended.

A failure has been detected in the primary storage system.

Primary

SIM log

dc

2x

Serious

The P-VOL has been suspended.

A failure has been detected in the secondary storage system.

Primary

SIM log

dc

4x

Serious

The P-VOL has been suspended.

The pair has been suspended at the secondary storage system.

Primary

SIM log

dc

5x

Serious

The P-VOL has been suspended.

A pair has been released at the secondary storage system.

Primary

SIM log

dc

6x

Serious

The S-VOL has been suspended.

Path recovery is impossible.

Primary

SIM log

dc

7x

Serious

The S-VOL has been suspended.

A failure has been detected in the secondary storage system.

Secondary

SIM log

dc

9x

Serious

A delta resync P-VOL has been suspended.

A failure has been detected in the primary storage system.

This SIM is also issued when the system option mode 1182 is set to ON and a reserve journal volume is added on the primary storage system of the UR delta resync pair in an environment linking with global-active device.

Primary

SIM log

dc

ax

Serious

A volume used in a P-VOL that is configured in a multiple primary and secondary storage system combination has been suspended.

A failure has been detected in other primary and secondary storage systems.

Primary

SIM log

dc

f1

Serious

The UR Read JNL was interrupted for five minutes. (A failure in the MCU was detected.)

Secondary

SIM log

dc

f3

Serious

The UR Read JNL was interrupted for five minutes. (A failure in the RCU was detected.)

Secondary

SIM log

The following table lists and describes SIMs that do not need immediate intervention but might require intervention later.

SIMs for expected status change, no intervention

Reference code

Severity

Description

System generating the SIM

SVP log file

Byte 22

Byte 23

dc

e0

Moderate

UR M-JNL Meta overflow warning*

Primary

SIM log

dc

e1

Moderate

UR M-JNL Data overflow warning*

Primary

SIM log

dc

e2

Moderate

UR R-JNL Meta overflow warning

Secondary

SIM log

dc

e3

Moderate

UR R-JNL Data overflow warning

Secondary

SIM log

dc

f0

Moderate

The UR Read JNL was interrupted for one minute. (A failure in the MCU was detected.)

Secondary

SIM log

dc

f2

Moderate

The UR Read JNL was interrupted for one minute. (A failure in the RCU was detected.)

Secondary

SIM log

dc

f4

Moderate

UR M-JNL Meta overflow warning in URxUR multi-target configuration

Primary

SIM log

dc

f5

Moderate

UR M-JNL Data overflow warning in URxUR multi-target configuration

Primary

SIM log

* If Inflow Control of the journal option is enabled, the I/O responses from the host might be degraded and it might impact the operations. Take the corrective actions immediately.

The following table lists and describes service-level SIMs that report expected status changes and require no user intervention.

Service SIMs for expected status changes, no intervention required

Reference code

Severity

Description

System generating the SIM

SVP log file

Byte 22

Byte 23

21

81

Service

The remote path is restored.

Primary, Secondary

SSB log

d8

0x

Service

A volume to be used by UR was defined.

Primary, Secondary

SIM log

d8

1x

Service

A volume used by UR began copying.

Primary, Secondary

SIM log

d8

2x

Service

A volume used by UR completed copying.

Primary, Secondary

SIM log

d8

3x

Service

A volume used by UR received a request for suspension.

Primary, Secondary

SIM log

d8

4x

Service

A volume used by UR completed a suspension transaction.

Primary, Secondary

SIM log

d8

5x

Service

A volume used by UR received a request for deletion.

Primary, Secondary

SIM log

d8

6x

Service

A volume used by UR completed a deletion transaction.

Primary, Secondary

SIM log

d8

7x

Service

A volume to be used by UR was defined (placed in PSUS immediately).

Primary, Secondary

SIM log

d8

8x

Service

A delta resync volume to be used by UR was defined.

Primary

SIM log

d8

9x

Service

A delta resync volume used by UR was redefined.

Primary

SIM log

d9

zx

Service

A change to an S-VOL was received from the MCU.

Secondary

SIM log

da

zx

Service

A change to an S-VOL was received from the RCU.

Secondary

SIM log

dc

8x

Service

A volume used by an S-VOL was suspended (PS OFF on the MCU was detected).

Secondary

SIM log

Completing SIMs

When the cause of the SIMs has been resolved, you need to complete the SIMs to change the SIM status to Completed.

NotePerforming this task completes all uncompleted SIMs for both UR and URz operations. If the cause of any of the SIMs has not been resolved, new SIMs will be issued.

Before you begin

  • Required role: Storage Administrator (System Resource Management)

Procedure

  1. Resolve the cause of the SIM.

  2. Open the Complete SIMs (UR) window.

    In Device Manager - Storage Navigator:
    1. From the Device Manager - Storage Navigator menu, click Actions.

    2. Click Remote Replication Complete SIMs (UR).

  3. If desired, select Go to tasks window for status.

  4. Click Apply.

    If you selected Go to tasks window for status, the Tasks window is displayed.

Notification of suspension due to an error (multiple primary and secondary systems)

When multiple primary systems and secondary systems are combined, an error in one of the journals affects other journals, and pairs are suspended by the error. A time stamp is issued to all journals, and the error in one of the journals is notified to the other journals as long as data consistency is maintained in the system.

To notify all journals of a failure, the following conditions must be met:

  • The line between CCI and all primary systems is operating correctly.
  • The status of the failed journal is PJSE or PJSF.
  • At least one journal in the CCI consistency group is in normal status.

When all the above conditions are met, an error occurred in a journal is notified to the other journals. The following explains journal statuses:

  • Normal journals are displayed as PJNN in CCI.
  • When an error occurs, the journal status changes from PJNN (normal) to PJSE (suspended by error).
  • For errors caused by capacity overflow, the status changes to PJSF.
  • When one journal changes to PJSE or PJSF, all other normal journals in the PJNN status also change to the PJSE status (suspended by error).
    NoteWhen an error occurs in a pair in a journal, if the entire journal is not suspended by the error, the status of the other journals does not change.