HP XP P9500 Storage - Manual (Page 73)

Table 29 General troubleshooting (continued)
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 P9000 Remote
Web Console User Guide for information and instructions.
See “Pinned track recovery” (page 83) 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 on Monitoring Switch, see the HP P9000
Performance for Open and Mainframe Systems User Guide.
Table 30 Troubleshooting secondary path status problems
Corrective action Description Path status
The link initialization
procedure to the remote
system failed. Initialization Failed • Make sure that the primary and secondary systems are
physically and correctly connected.
•
Make sure that you entered the correct remote system S/N,
SSID, and path parameters (port, link address, logical
address).
• Make sure that the Fibre Channel topology settings on the
primary and secondary systems ports are correct.
Communication between the
primary and secondary
systems timed out. Communication Time
Out •
Make sure the secondary system is powered on and fully
functional (NVS, cache).
• Make sure that data path hardware is properly configured
and functional (cables, connectors, switches, extender
devices, communication lines, and all other devices
connected to the extenders).
•
Delete the failed path. You may need to change the
minimum paths setting or delete the secondary system in
order to delete the path. Then add the path/secondary
system using Edit Path or Add RCU.
The primary or secondary
system rejected the logical Path Rejected
(MCU/RCU) •
Delete the failed path.
• Also, delete all paths and secondary systems not currently
in use. The primary system can be connected to a maximum
path link control function
because all logical path
General troubleshooting 73