Troubleshooting Using Remote Web Console - HP StorageWorks P9000 User Manual

Table 24 Resolving pair suspension
Classification
Primary or
secondary system
hardware
Communication
between the
primary and
secondary systems
RIO overload or
RIO failure
Planned power
outage to the
primary system

Troubleshooting using Remote Web Console

The user is responsible for the operation and normal maintenance of Remote Web Console
computers. For troubleshooting information on Remote Web Console, see HP StorageWorks P9000
Remote Web Console User Guide.
Here are some guidelines for troubleshooting the Remote Web Console computer:
Check the cabling and the LAN. Verify that both the computer and LAN cabling are firmly
attached.
Reboot the computer. Close any programs that are not responding. If necessary, reboot the
computer and restart the Remote Web Console program.
Check error codes. For detailed information about error codes displayed on Remote Web
Console computers, see HP StorageWorks P9000 Remote Web Console Messages.
Causes of suspension
Hardware redundancy has been lost due
to some blockade condition. As a result,
one of the following could not complete:
primary-secondary system
communication, journal creation, copy
operation, restore operation, staging
process, or de-staging process.
Journals cannot be retained because
some portion of the cache memory or
the shared memory has been blocked
due to hardware failure.
The primary system failed to create and
transfer journals due to unrecoverable
hardware failure.
The secondary system failed to receive
and restore journals due to
unrecoverable hardware failure.
The drive parity group was in
correction-access status while the Cnt
Ac-J Z pair was in Pending Duplex status.
Communication between the systems
failed because the secondary system or
network relay devices were not running.
Journal volumes remained full even after
the timeout period elapsed.
An unrecoverable RIO (remote I/O)
timeout occurred because the system or
network relay devices were overloaded.
Or, RIO could not be finished due to a
failure in the system.
The Cnt Ac-J Z pairs were temporarily
suspended due to a planned power
outage to the primary system.
SIM Recovery procedure
DC0x According to SIM, remove the hardware
DC1x blockade or failure.
DC2x
If a failure occurs when Business Continuity
Manager is being used, secondary volumes
in Suspend (equivalent to SWAPPING in
Business Continuity Manager) may remain in
the master journal. If these volumes remain,
execute the YKRESYNC REVERSE option on
the secondary volumes with a pair status of
Suspend, which is equivalent to SWAPPING
in Business Continuity Manager terminology
(YKRESYNC is the Business Continuity
Manager command for resynchronizing a
pair.) This operation changes all volumes in
the master journal to primary volumes. After
this operation, restore the volume pairs
(Resume Pair).
DC0x Remove the failure from the primary and
secondary systems or the network relay
DC1x
devices.
If necessary, increase resources as needed
(for example, the amount of cache, the
number of paths between primary and
secondary systems, the parity groups for
journal volumes, etc.).
Restore the failed pairs (Resume Pair).
DC2x Release failed pairs (Delete Pair).
If necessary, increase resources as needed
(for example, the amount of cache, the
number of paths between primary and , the
parity groups for journal volumes, etc.).
Re-establish failed pairs (Add Pair).
DC8x No recovery procedure is required. The
primary system automatically removes the
suspension condition when the system is
powered on.
Troubleshooting using Remote Web Console 121