HP XP P9500 Storage - Manual (Page 76)

Corrective action Error
The paircreate or pairresync operation resulted
in a timeout error. • Hardware failure: If the timeout error was caused by a hardware
failure, a SIM is generated. If this occurs, call service personnel,
then retry Continuous Access Synchronous operations after the
problem is fixed.
•
Heavy workload: If no SIM was generated, wait 5 or 6 minutes
then check the pair’s status.
- If status changed correctly, the failed operation completed after
the timeout message was issued.
- If the pair status did not change as expected, heavy workload
might have prevented the operation from being completed. Retry
the operation when the system has a lighter workload.
•
A communication error may have occurred between the Remote
Web Console computer and SVP. See the HP XP P9000 Remote
Web Console User Guide for information and instructions.
See “Pinned track recovery” (page 87) for more information. There is a pinned track on a Continuous Access
Synchronous volume.
Because the time setting of SVP is changed, the monitoring data
might not be updated. Disable Monitoring Switch, then enable again. Monitoring data is not updated though the
Monitoring Switch option is set to Enable.
For more information about Monitoring Switch, see the HP XP P9000
Performance for Open and Mainframe Systems User Guide.
Secondary path status problems
The following table provides a list of secondary path status problems.
Corrective action Description Path status
None required. This path has been
successfully established and Normal
can be used for Continuous
Access Synchronous copy
activities.
The link initialization
procedure to the secondary Initialization Failed • Make sure that the primary and secondary system are
physically and correctly connected.
system failed because the
•
Make sure that you entered the correct secondary system
S/N, Controller ID, and primary and secondary system
port numbers.
physical path connection was
missing between the primary
and secondary system.
•
Make sure the primary and secondary system ports are
configured correctly.
Communication between the
primary and secondary
system timed out. Communication Time
Out •
Make sure the secondary system is powered on and that
NVS and cache are fully functional.
• Make sure that network relay devices are properly
configured and functional. This includes cables, connectors,
switches, extender devices, communication lines, and all
other devices connected to the extenders.
The primary system rejected
the logical path link control Path Rejected
(MCU/RCU) •
Delete all paths and RCUs not in use.
•
Make sure that all primary and secondary system ports are
properly configured: ordinary RCU target ports for
function because all logical
path resources in the primary
76 Troubleshooting