HP XP Continuous Access Software - Manual (Page 103)

Continuous Access XP user guide for the XP1024/XP128 103
3. Split (pairsplit-r) all Continuous Access XP pairs at MCUs (original RCUs) to destage any pending data
from cache. Confirm that pairs are split (PSUS) before proceeding. If an error occurs, resolve it before
proceeding.
4. Delete all Continuous Access XP pairs at MCUs (original RCUs). You do not need to use the Delete Pair
by Force option. For Continuous Access XP Async pairs, the MCU and RCU complete all pending
updates before changing the pair status to SMPL.
5. Change Continuous Access XP settings at MCUs (original RCUs) to prepare for normal Continuous
Access XP operations. Delete Continuous Access XP Async groups and RCUs (original MCUs). If you
plan to use the same remote copy connections, reconfigure ports (change initiator ports back to
ordinary target ports for fibre).
6. If you plan to use the same channel extenders, change the operating mode back to the original
direction. Boxes and nodes connected to MCUs must be set to channel-mode. Boxes and nodes
connected to RCUs must be set to device-mode.
7. At the primary site, configure RCPs or initiator ports, add RCUs, and add Continuous Access XP Async
groups.
8. At the primary site, establish all Continuous Access XP groups and pairs in the original direction. You
can use the None initial copy option because all P-VOLs and S-VOLs are synchronized. If there is any
possibility that volumes are not 100% synchronized, select Entire Volume for the Initial Copy field for
the Initial copy parameters option to be safe.
9. Vary the MCU and P-VOLs online, and start applications at the primary site.
Error codes and messages
Continuous Access XP error codes
Continuous Access XP displays error messages on the Command View XP management station or in XP
Remote Web Console when error conditions occur during Continuous Access XP operations. Error
messages describe the error and can include an SVP error code. If you need to call HP technical support
for assistance, report Continuous Access XP and SVP error codes.
Service Information Messages (SIMs)
The disk array generates SIMs when it is necessary to notify you of a possible service requirement for the
disk array. SIMs can be generated by the channel and storage path microprocessors and by the service
processor (SVP) of the disk array. The SVP reports all SIMs related to Continuous Access XP operations.
Each time a SIM is generated, the amber Message LED on the disk array’s front operator pane (under the
Ready and Alarm LEDs) turns on as an additional alert.
SIMs are classified according to severity for reporting and logging purposes: service, moderate, serious,
or acute. All SIMs are logged on the SVP and reported in the Command View XP framework (Array Event
History). During Continuous Access XP operations, the MCU and RCU generate a service SIM each time
the pair status of the P-VOL or S-VOL changes for any reason, including normal status transitions (for
example, COPY to PAIR). SIMs generated by the MCU include the P-VOL device ID (byte 13). SIMs
generated by the RCU include the S-VOL device ID (byte 13).
If SIM will result in an SNMP trap being sent to the appropriate hosts.
Pinned track recovery for Continuous Access XP volumes
If a pinned track occurs on a Continuous Access XP P-VOL or S-VOL, the MCU suspends the pair (SIM
reference code = DB1x).
To ensure full data integrity of the volume pair while recovering the pinned track, use the following
procedure:
1. Connect to the MCU of the Continuous Access XP pair containing the volume with the pinned track,
and select the correct CU image.
2. Delete the Continuous Access XP pair (pairsplit-S) containing the volume with the pinned track.