Troubleshooting Using Remote Web Console - HP XP P9500 User Manual

Table 18 Resolving pair suspension (continued)
Classification
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 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 P9000 Remote Web Console Messages.
Check error codes. For detailed information about error codes displayed on Remote Web
Console computers, see HP P9000 Remote Web Console Messages.
Check the status lamp on the Remote Web Console main window. If the color of the lamp
becomes yellow (
Causes of suspension
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 pair was in COPY 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 pairs were temporarily
suspended due to a planned power
outage to the primary system.
) or red ( ), check the status of the storage system on the Status window
SIM Recovery procedure
remain, execute the pairresync -swaps
command on the secondary volumes whose
pair status is SSWS (pairresync is the RAID
Manager command for resynchronizing pair
and -swaps is a swap option. This operation
changes all volumes in the master journal to
primary volumes. After this operation, restore
the volume pairs (Pairresync).
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 (Pairresync).
DC2x Release failed pairs (pairsplit-S).
If necessary, increase resources as needed.
For example, the amount of cache, the
number of paths between primary and
secondary system, the parity groups for
journal volumes, and so on.
Re-establish failed pairs (Paircreate).
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 107