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

Table 36 Troubleshooting Suspended XP Continuous Access Pairs (continued)
Corrective Action Description Applies to Pair
Status/Type
transferred within the specified
offloading timer. • Decrease the number of Async
pairs, or
2. In case the system option mode 549
is ON, the suspend occurred due to
• Decrease the host I/Os.
the RIO completion waiting TOV. The
suspend type is Sidefile Overflow. 2. Eliminate the error factor for the RIO
completion waiting TOV (line
disturbance, repeater failure, RCU
overlaod, and others). After
eliminating the error factor,
resynchronize the pair from the MCU
(Pairresync).
Table 37 (page 156) provides troubleshooting instructions for the XP Continuous Access Asynchronous
suspension conditions caused by the offloading timer async option, group timeout options (copy
pending and RCU ready), and recordset errors. Hardware failures that affect the storage
system/shared memory of the MCU or RCU may also cause the XP Continuous Access Asynchronous
pairs to be suspended.
Table 37 Resolving XP Continuous Access Asynchronous Suspension Conditions
Recovery procedure SIM Causes of Suspension Classification
According to the SIM, remove the
hardware blockade or failure. DB0x
DB1x
Hardware redundancy has been lost due
to some blockade condition. As a result,
MCU-RCU communications, creating or MCU/RCU
hardware
Re-establish failed pairs (pairresync).
DB2x
receiving recordsets, or the staging or
de-staging process could not complete.
The pending recordset cannot be
retained because one side of cache
storage or shared memory has been
blocked due to hardware failure.
MCU-Creating/sending recordset failed
due to unrecoverable hardware failure.
RCU-Reading/settling recordset failed
due to unrecoverable hardware failure.
The drive parity group was in
correction-access status while the XP
Continuous Access pair was in COPY
state.
Remove the failed condition at the
RCU/MCU or on the remote copy
connection. DB0x
DB1x
During the power-on-reset sequence, the
MCU could not communicate with the
RCU within the specified RCU ready
timeout. MCU-RCU
communication
Re-establish failed pairs (pairresync).
The RCU could not settle the pending
recordset or could not communicate with
the MCU before the copy pending
timeout due to MCU not-ready or
inoperative facilities on the remote copy
connections.
Release failed pairs (pairsplit-S). DB1x The unrecoverable RIO (remote I/O)
timeout occurred due to an overload on RIO overload
Reconsider the performance
resources necessary, and increase
the RCU or the communications facilities
on the remote copy connections.
resources as needed (cache amount,
No recordset could be sent within the
specified copy pending timeout. number of MCU-RCU paths, and so
on).
The RCU could not settle the pending
recordset before the copy pending Re-establish failed pairs (paircreate).
156 Troubleshooting