HP StorageWorks XP Remote Web Console Software - Manual (Page 297)

Troubleshooting 3
Hitachi Universal Replicator for IBM /OS User’s Guide
Table 11-1 General Troubleshooting Information for Universal Replicator
for z/OS ®
Error Corrective Action
The Hitachi USP V Remote Console software
hangs, or URz operations do not function
properly. Make sure that all URz requirements and restrictions are met (e.g.,
track format, VOLSER).
Make sure the primary and secondary storage systems are powered on
and fully operational (NVS, cache, DFW). Refer to the User and
Reference Guide for operational and troubleshooting information.
Check all the entered values and parameters to make sure you entered
the correct information on the Universal Replicator for z/OS ® windows
(e.g., remote storage system S/N, path parameters, primary data volume
IDs and secondary data volume IDs).
Status of pairs and/or logical paths is not
displayed correctly. Make sure that the correct CU image is selected.
An R-SIM warning is displayed on your Hitachi
USP V Storage Navigator computer. Locate the SIM (see the Storage Navigator User’s Guide for
instructions). For information about UR-z/OS SIMs, see Checking
Service Information Messages (SIMs).
A URz error message is displayed on your
Storage Navigator computer. Remove the error cause, and then retry the URz operation.
There is a problem with the Storage Navigator
computer or the URz software. Make sure that the problem is not with the computer, LAN
hardware or software. Restart the computer and retry connecting
to the storage system.
The status of a logical path is not normal. Check the path status in the DKC Status window, and see Table
11-2.
The pair status is suspended. Check the detailed pair status in the Detailed Information window.
See Table 11-3 for suspend types and corrective action for
suspended URz pairs.
Table 11-2 Troubleshooting Problems with Status of Logical Paths
Path Status Description Corrective Action
Initialization Failed The link initialization
procedure for the remote
storage system failed. Make sure that the local and remote storage systems are
correctly connected via cable to each other.
Make sure that you entered the correct remote storage
system S/N (serial number) and path parameters (e.g., local
storage system port, remote storage system port, and
controller ID).
Make sure that the topology settings of the local and remote storage
system ports are correct.
Communication
Time Out Communication between the
local and remote storage
systems timed out. Make sure that the remote storage system is powered on, and
that NVS and cache are fully functional.
Make sure that network relay devices (including cables, connectors,
ESCDs, extender devices, communication lines, and all other
devices connected to the extenders) are properly configured and
functional. After that, delete the failed path. You may need to
change the minimum paths setting or delete the remote storage
system in order to delete the path. After deletion finishes, add the
path or the remote storage system by using the Add Path window or
the Add DKC window.