HP StorageWorks XP Remote Web Console Software User Manual
Page 156
Table 34 General XP Continuous Access Troubleshooting (continued)
Corrective Action
Error
Hardware failure: If the timeout error was caused by a
hardware failure, a SIM will be generated. If this occurs,
call your HP service representative, and retry the XP
Continuous Access operations after the problem is fixed.
Heavy workload: If no SIM was generated, wait for a while
(5 or 6 minutes), then check the pair status of the pair(s)
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, a heavy workload might have prevented the XP
Continuous Access operation from being completed. In this
case, retry the XP Continuous Access operation again when
the storage system has a lighter workload.
If a communications error between the Remote Web Console
computer and SVP occurs, see the HP StorageWorks
XP24000/XP20000 Remote Web Console User's Guide for
instructions.
Paircreate or pairresync operation resulted in
a timeout error.
See
“Pinned Track Recovery for XP Continuous Access
on page
Continuous Access Volumes” (page 146)
for instructions.
There is a pinned track on an XP Continuous
Access volume.
Because the time setting of SVP is changed, the monitoring
data might not be updated. Set Monitoring Switch to Disable,
and set Monitoring Switch to Enable again. For further
information on Monitoring Switch, see the HP StorageWorks
XP24000/XP20000 Performance Monitor User's Guide.
Although Monitoring Switch is set to Enable,
the monitoring data is not updated.
Table 35 Troubleshooting RCU Path Status Problems
Corrective Action
Description
Path Status
Make sure that the MCU and RCU are
physically and correctly connected.
Make sure that you entered the correct RCU
S/N and SSID and path parameters (port,
link address, logical address).
Make sure the correct MCU port is
configured as an initiator port and the
correct RCU port is configured as an RCU
target port.
The link initialization procedure to the RCU
failed.
Initialization
Failed
Make sure the RCU is powered on and fully
functional (NVS, cache).
Make sure that the remote copy connection
hardware (cables, connectors, switches,
extender devices, communication lines, and
all other devices connected to the extenders)
are properly configured and functional.
Delete the failed path. You may need to
change the minimum paths setting or delete
the RCU to delete the path. Then add the
path/RCU using Edit Path or Add RCU.
Communications between the MCU and
RCU timed out.
Communication
Time Out
156
Troubleshooting