Remote path status problems
The following table provides a list of remote path status problems.
|
Path status |
Description |
Corrective action |
|---|---|---|
|
Normal |
This path has been successfully established and can be used for TrueCopy copy activities. |
None required. |
|
Initialization Failed |
The link initialization procedure to the secondary system failed because the physical path connection was missing between the primary and secondary system. |
|
|
Communication Time Out |
Communication between the primary and secondary system timed out. |
|
|
Port Rejected |
The primary system rejected the logical path link control function because all logical path resources in the primary system are being used for other connections. |
|
|
Serial Number Mismatch |
The secondary system's S/N does not match the specified S/N. |
|
|
Invalid Port |
The specified local storage system port is in the following status:
|
|
|
Communication Failed |
The primary system connected to the secondary system successfully, but logical communication timeout occurred. |
|
|
Path Blockade |
Blockaded due to continual path or link failure. |
See the following. |
|
The primary system port does not work. |
Repair the port on the primary system, then restore the path*. |
|
|
The secondary system port does not work. |
Repair the port on the secondary system, then restore the path*. |
|
|
The path relay equipment does not work. |
Repair the path relay equipment, then restore the path*. |
|
|
The connection cable is physically broken. |
Replace the broken cable, then restore the path*. |
|
|
Program Error |
A program error is detected. |
Restore the path*. |
|
In Progress |
Paths are being created or deleted. |
Wait until processing is completed. |
|
* To restore a path, delete and then add the path again. It may be necessary to delete and then add the RCU again. To delete the RCU or path, see Deleting TrueCopy remote connections or Deleting remote paths. To re-register, see Adding remote connection. If you cannot restore the path after performing these operations, contact the Hitachi Solution Support Center. |
||