By understanding the displayed pair status, you can take the appropriate corrective action.
The following table provides a list of split pair problem types.
|
Pair status/split type |
Applies to |
Description |
Corrective action |
|---|---|---|---|
|
PSUE/by RCU 0x06 |
P-VOL |
The primary system detected an error condition at the secondary system, which caused the primary system to split the pair. The S-VOL split type is S-VOL Failure. |
Clear the error condition at the secondary system or S-VOL, and then resynchronize the pair using the pairresync command of CCI. If you need to access the S-VOL to clear the error conditions, split the pair from the secondary system by using the pairsplit -S command. After you clear the error conditions from S-VOL, re-create the pair by using the paircreate command. |
|
PSUE/Secondary Volume Failure |
P-VOL |
The primary system detected an error during communication with the secondary system, or detected an I/O error during update copy. In this case, the split type for the S-VOL is usually S-VOL Failure. |
Check the path status using the raidcom get rcu command of CCI. If errors occurred on the path, clear the error conditions.
|
|
PSUE/MCU IMPL 0x09 |
P-VOL, S-VOL |
The primary system could not find valid control information in its nonvolatile memory during the IMPL procedure. This error occurs only if the system is without power for more than 48 hours (for example, power failure or fully discharged batteries). |
Resynchronize the pair from the primary system by using the pairresync command.. An entire initial copy operation will be performed in response to the pairresync request. |
|
PSUE/Initial Copy Failed 0x50 |
P-VOL, S-VOL |
The primary system split this pair during the initial copy operation. The data on the S-VOL is not identical to the data on the P-VOL. |
Use the pairsplit -S command to delete the pair from the primary system clear all error conditions on the primary system, P-VOL, secondary system, and S-VOL. Use the paircreate command to re-create the pair. |