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

184 Troubleshooting
Table 36 provides troubleshooting instructions for Continuous Access XP Journal pair suspension.
Hardware failures affecting cache memory and shared memory of the primary or secondary array might
also cause Continuous Access XP Journal pairs to be suspended.
Continuous Access XP Journal error codes
The Command View XP management station or XP Remote Web Console displays an error message when
an error occurs during Continuous Access XP Journal operations. The error message describes the error
and displays an error code consisting of four digits. The error message might also include a local array
SVP error code. If you need to contact your HP account support representative for assistance, report the
error codes.
Table 36 Resolving Continuous Access XP Journal pair suspension
Classification Causes of suspension SIM Recovery procedure
Primary array
hardware or
secondary array
hardware
Hardware redundancy was lost due to
some blockade condition. As a result,
one of the following could not
complete: primary-secondary array
communications, journal creation, copy
operation, restore operation, staging
process, or de-staging process.
Journals cannot be retained because
some portion of cache memory or
shared memory was blocked due to
hardware failure.
Primary array failed to create and
transfer journals due to unrecoverable
hardware failure.
Secondary array failed to receive and
restore journals due to unrecoverable
hardware failure.
Drive parity group was in
correction-access status while the
Continuous Access XP Journal was in
COPY status.
DC0x
DC1x
DC2x According to SIM, remove the
hardware blockade or failure.
Restore the failed volume pairs
(pairresync).
Communication
between the
primary and
secondary arrays
Communication between arrays failed
because the secondary array or
network relay devices were not
running.
Journal volumes remained full even
after the timeout period elapsed.
DC0x
DC1x Remove the failure from the primary
and secondary arrays or network relay
devices.
If necessary, increase resources as
needed (for example, amount of
cache, number of paths between
primary and secondary arrays, and
parity groups for journal volumes).
Restore the failed pairs (pairresync).
RIO overload or
RIO failure
Unrecoverable RIO (remote I/O)
timeout occurred because the array or
networks relay devices were
overloaded.
RIO could not be finished due to a
failure in the array.
DC2x Delete failed pairs (pairsplit-S).
If necessary, increase resources as
needed (for example, amount of
cache, number of paths between
primary and secondary arrays, and
parity groups for journal volumes).
Re-establish failed pairs (paircreate).
Planned power
outage to the
primary array
Continuous Access XP Journal pairs
were temporarily suspended due to a
planned power outage to the primary
array.
DC8x None. Primary array automatically
removes the suspension condition when
the array is powered on.