Skip to main content
Hitachi Vantara Knowledge

Troubleshooting

When issues occur with global-active device operations, there are a number of different troubleshooting options you can try.

General troubleshooting

Problem

Recommended action

The HCS computer stops, or global-active device does not operate properly.

  • Verify that there are no problems with the HCS computer, with the Ethernet connection, or with the software products, and then restart the HCS computer. Restarting the HCS computer does not affect the GAD operations that are currently running.
  • Confirm that all GAD requirements and restrictions (such as LU types) are met.
  • Confirm that the storage systems of the primary site and secondary site are powered on and that their functions are fully enabled.
  • Confirm that all values and parameters (such as serial number and ID of the remote storage system, path parameter, IDs of the primary volume and secondary volume) were entered correctly.

The LED on the storage system's control panel that indicates that the channel of the initiator is available is off or blinking.

Contact customer support.

GAD error messages are displayed on the HCS computer.

Correct the error, and then re-execute the GAD operation.

The status of a path to the remote storage system is abnormal.

Check the status of the paths in the Remote Connections window, and make the required corrections.

A timeout error occurred while creating a pair or resynchronizing a pair.

  • If a timeout occurred due to a hardware error, a SIM is generated. Contact customer support, and after solving the problem, re-execute the GAD operation.
  • Large workload: If a SIM is not generated, wait for 5 to 6 minutes, and then check the status of the pair you want to create or resynchronize. If the pair status correctly changed, the failed operation completed after the timeout error message was displayed. If the pair status did not change as anticipated, the GAD operation cannot complete due to the large workload. In this case, re-execute the GAD operation when the workload of the storage system is smaller.
  • If a communication error between HCS or management client and the SVP occurred, see System Administrator Guide.
A pair cannot be created or resynchronized.Verify that the controller board is blocked on the primary or the secondary storage system. Restore the blocked controller board, then retry the operation.

A GAD volume has pinned tracks.

Recover the pinned track volume.

The monitoring switch is enabled, but the monitoring data is not updated.

  • The monitoring data might not be updated because the time setting of SVP was changed. Disable the monitoring switch, and then enable it again. For details about the monitoring switch, see the Provisioning Guide for the storage system.
  • Verify that the settings for the target being monitored are correct.

Troubleshooting related to remote path status

Remote path status and description

Status description

Recommended action

Normal

Normal

This remote path is correctly set, and the path can be used for copying GAD.

The remote path status is normal. Recovery is not required.

Initialization Failed

Initialization error

A physical connection between the local storage system and the remote storage system, or a connection between the local storage system and the switch does not exist. Therefore, the error occurred when the connection to the remote storage system was initialized.

Check the following, and correct them if they are not correct:

  • The cable between the ports of the local storage system and the remote storage system or between the ports of the local storage system and the switch of the local storage system is properly connected.
  • The serial number (S/N) and system ID of the remote storage system, the port number of the local storage system, and the port number of the remote storage system are correct.
  • The topology (Fabric, FC-AL, Point-to-point) of the ports of the local storage system and remote storage system is correctly set.

Communication Time Out

Communication timeout

A timeout occurred in a communication between the local storage system and remote storage system.

Check the following, and correct them if they are not correct:

  • The remote storage system is powered on, and the remote storage system can be used normally.
  • The following network relaying devices are correctly configured, and can be properly used:
    • Connectors
    • Cables
    • Switches (zoning settings)
    • Channel extenders (if channel extenders are connected)
    • Lines and systems connected among between channel extenders (if channel extenders are connected)

Port Rejected

Insufficient resources

All resources of the local storage system or remote storage system are being used for other connections. Therefore, the local storage system or remote storage system rejected the connection control function that sets remote paths.

  • In the Remove Remote Paths window, remove all remote paths that are not currently used.
  • In the Remove Remote Connections window, remove all remote storage systems that are not currently used.

Serial Number Mismatch

Mismatched serial number

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

Check the following, and correct them if they are not correct:

  • The serial number (S/N) and system ID of the remote storage system, the port number of the local storage system, and the port number of the remote storage system are correct.
  • The topology (Fabric, FC-AL, Point-to-point) of the ports of the local storage system and remote storage system is correctly set.
  • The following network relaying devices are correctly configured, and can be properly used:
    • Connectors
    • Cables
    • Switches (zoning settings)
    • Channel extenders (if channel extenders are connected)
    • Lines and systems connected among between channel extenders (if channel extenders are connected)

Invalid Port

Invalid port

The specified port of the local storage system is in the following status:

  • The port is not mounted.
  • The remote path already exists.

Check the following, and correct them if they are not correct:

  • No remote path with the same configuration (the same port number of the local storage system and the same port number of the remote storage system) exists.
  • The topology (Fabric, FC-AL, Point-to-point) of the ports of the local storage system and remote storage system is correctly set.
  • The following network relaying devices are correctly configured, and can be properly used:
    • Connectors
    • Cables
    • Switches (zoning settings)
    • Channel extenders (if channel extenders are connected)
    • Lines and systems connected among between channel extenders (if channel extenders are connected)
  • The serial number (S/N) and system ID of the remote storage system, the port number of the local storage system, and the port number of the remote storage system are correct.

Pair-Port Number Mismatch

Incorrect port number of the remote storage system

The specified port of the remote storage system is not physically connected to the local storage system.

Check the following, and correct them if they are not correct:

  • The port number of the remote storage system is correct.
  • The cable between the ports of the local storage system and the remote storage system or between the ports of the local storage system and the switch of the local storage system is properly connected.
  • The topology (Fabric, FC-AL, Point-to-point) of the ports of the local storage system and remote storage system is correctly set.

Communication Failed

Communication error

The local storage system is correctly connected to the remote storage system, but a logical communication timeout occurred.

Check the following, and correct them if they are not correct:

  • The port of the remote storage system and the network relaying devices are correctly set.
  • The following network relaying devices are correctly configured, and can be properly used:
    • Connectors
    • Cables
    • Switches (zoning settings)
    • Channel extenders (if channel extenders are connected)
    • Lines and systems connected among between channel extenders (if channel extenders are connected)

Path Blockade

Logical blockade

Blocked because path errors or link errors repeatedly occurred.

The port of the local storage system is out of order.

Repair the port of the local storage system.

Then, recover the remote path.*

The port of the remote storage system is out of order.

Repair the port of the remote storage system.

Then, recover the remote path.*

A relaying device is out of order.

Repair the relaying device.

Then, recover the remote path.*

The cable is damaged.

Replace the cable.

Then, recover the remote path.*

Program Error

A program error was detected.

Recover the remote path.*

In Progress

A remote path is being created, the remote path is being deleted, or the port attribute (VSP 5000 series) is being changed.

Wait until the processing ends.

* Recover the remote path by either of the following methods:

  • To use Hitachi Command Suite (either of the following):
    • Remove the remote connection in the Remove Remote Connections window, and then register the remote connection again in the Add Remote Connection window. For instructions, see the topic "Removing remote connections" in the help.
    • Remove the remote path in the Remove Remote Paths window, and then create a remote path again in the Add Remote Paths window. For instructions, see the topic "Removing remote paths" in the help.
  • To use CCI:

    Use the raidcom delete rcu_path command to remove the remote path, and then use the raidcom add rcu_path command to re-create the remote path.

If the remote path is still not recovered after these operations, contact customer support.

Error codes and messages

If an error occurs during a global-active device operation, GAD displays an error message that describes the error and includes an error code.

Make sure to record the error codes, so that you can report them if you need to contact customer support. For details about Device Manager - Storage Navigator error codes, see the Messages guide for the storage system.

SIM reports of GAD operations

If a storage system requires maintenance, a SIM is issued and displayed in Device Manager - Storage Navigator. A SIM is also issued when the pair status of a primary or secondary GAD volume changes. SIMs are categorized into service, moderate, serious, and acute according to their severity. The GAD operation history appears in the History window.

If SNMP is installed on the storage systems, SIMs trigger an SNMP trap that is sent to the corresponding server. For details about SNMP operations, see the Hitachi Command Suite User Guide or the Hitachi Alert Notification Guide.

Restoring pair statuses when a GAD consistency group contains local I/O mode pairs and block I/O mode pairs

When a GAD pair is suspended due to a failure, if a GAD consistency group contains pairs whose volumes are in Local I/O mode and pairs in Block I/O mode, you can restore pair statuses in the consistency group after recovering from the failure.

When using GAD and UR, delete UR pairs and UR delta resync pairs first.

After restoring the status of pairs in the consistency group, re-create UR delta resync pairs and UR pairs.

Restoring pair statuses in the consistency group when the primary volume is at the primary site

When a GAD pair is suspended due to a failure and the primary volume is at the primary site, you can restore pair statuses in the consistency group after recovering from the failure.

Procedure

  1. Resynchronize a suspended pair.

    When the I/O mode of the primary volume is Local, resynchronize the pair by specifying the primary volume.

    Command example:

     pairresync -g oraHA -d dev0 -IH0
  2. At the secondary site, swap suspend the pair by specifying a consistency group.

    Command example:

    pairsplit -g oraHA -RS -IH1
  3. At the secondary site, swap resynchronize the pair by specifying a consistency group.

    Command example:

    pairresync -g oraHA -swaps -IH1
  4. At the primary site, swap suspend the pair by specifying a consistency group.

    Command example:

    pairsplit -g oraHA -RS -IH0
  5. At the primary site, swap resynchronize the pair by specifying a consistency group.

    Command example:

    pairresync -g oraHA -swaps -IH0

Restoring pair statuses in the consistency group when the primary volume is at the secondary site

When a GAD pair is suspended due to a failure and the primary volume is at the secondary site, you can restore pair statuses in the consistency group after recovering from the failure.

Procedure

  1. Resynchronize a suspended pair.

    When the I/O mode of the primary volume is Local, resynchronize the pair by specifying the primary volume.

    Command example:

     pairresync -g oraHA -d dev0 -IH1
  2. At the primary site, swap suspend the pair by specifying a consistency group.

    Command example:

    pairsplit -g oraHA -RS -IH0
  3. At the primary site, swap resynchronize the pair by specifying a consistency group.

    Command example:

    pairresync -g oraHA -swaps -IH0
  4. At the secondary site, swap suspend the pair by specifying a consistency group.

    Command example:

    pairsplit -g oraHA -RS -IH1
  5. At the secondary site, swap resynchronize the pair by specifying a consistency group.

    Command example:

    pairresync -g oraHA -swaps -IH1