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. |
|
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. |
|
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. |
|
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:
| |
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:
| |
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. |
| |
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:
| |
Invalid Port Invalid port |
The specified port of the local storage system is in the following status:
|
Check the following, and correct them if they are not 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:
| |
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:
| |
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:
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
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
At the secondary site, swap suspend the pair by specifying a consistency group.
Command example:pairsplit -g oraHA -RS -IH1
At the secondary site, swap resynchronize the pair by specifying a consistency group.
Command example:pairresync -g oraHA -swaps -IH1
At the primary site, swap suspend the pair by specifying a consistency group.
Command example:pairsplit -g oraHA -RS -IH0
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
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
At the primary site, swap suspend the pair by specifying a consistency group.
Command example:pairsplit -g oraHA -RS -IH0
At the primary site, swap resynchronize the pair by specifying a consistency group.
Command example:pairresync -g oraHA -swaps -IH0
At the secondary site, swap suspend the pair by specifying a consistency group.
Command example:pairsplit -g oraHA -RS -IH1
At the secondary site, swap resynchronize the pair by specifying a consistency group.
Command example:pairresync -g oraHA -swaps -IH1