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

Table 53 Resolving Universal Replicator for Mainframe Pair Suspension
Recovery procedure SIM Causes of Suspension Classification
According to the SIM, remove the
hardware blockade or failure. DC0x
DC1x
Hardware redundancy has been lost
due to some blockade condition. As
a result, one of the following could Primary storage
system hardware
or secondary
Restore the failed volume pairs
(Resume Pair).
DC2x
not complete: primary-secondary
storage system communication, storage system
hardware
If a failure occurs when Business
Continuity Manager is being used,
journal creation, copy operation,
restore operation, staging process, or
de-staging process.
secondary volumes in Suspend
(equivalent to SWAPPING in Business
Journals cannot be retained because
some portion of the cache memory or
Continuity Manager) may remain in
the master journal group. If these
the shared memory has been blocked
due to hardware failure.
volumes remain, execute the
YKRESYNC REVERSE option on the
The primary storage system failed to
create and transfer journals due to
unrecoverable hardware failure. secondary volumes whose pair status
is Suspend, which is equivalent to
SWAPPING in Business Continuity
Manager terminology (YKRESYNC is
The secondary storage system failed
to receive and restore journals due to
unrecoverable hardware failure.
the Business Continuity Manager
command for resynchronizing pair).
This operation changes all volumes in
The drive parity group was in
correction-access status while the
the master journal group to primary
volumes. After this operation, restore
the volume pairs (Resume Pair).
Universal Replicator for Mainframe
pair was in Pending Duplex status.
Remove the failure from the primary
and secondary storage systems or the
network relay devices. DC0x
DC1x
Communication between the storage
systems failed because the secondary
storage system or network relay
devices were not running. Communication
between the
primary and
secondary storage
systems
If necessary, increase resources as
needed (for example, the amount of
Journal volumes remained full even
after the timeout period elapsed.
cache, the number of paths between
primary and secondary storage
systems, the parity groups for journal
volumes, etc.).
Restore the failed pairs (Resume Pair).
Release failed pairs (Delete Pair). DC2x An unrecoverable RIO (remote I/O)
timeout occurred because the storage RIO overload or
RIO failure
If necessary, increase resources as
needed (for example, the amount of
system or networks relay devices were
overloaded. Or, an RIO could not be
cache, the number of paths between
finished due to a failure in the storage
system.
primary and secondary storage
systems, the parity groups for journal
volumes, etc.).
Re-establish failed pairs (Add Pair).
No recovery procedure is required.
The primary storage system will DC8x The Universal Replicator for
Mainframe pairs were temporarily Planned power
outage to the
automatically remove the suspension suspended due to a planned power
outage to the primary storage system. primary storage
system
condition when the storage system is
powered on.
Universal Replicator for Mainframe Software Error Codes
Remote Web Console computers display an error message when an error occurs during Universal
Replicator for Mainframe operations. The error message describes the error and displays an error
code consisting of four digits. The error message may also include an SVP error code. If you need
to call HP technical support for assistance, report the Universal Replicator for Mainframe and SVP
error code(s). See the HP XP24000/XP20000 Remote Web Console Error Codes for a list of error
codes displayed on the Remote Web Console computers.
Universal Replicator for Mainframe Software Error Codes 233