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

To distribute the load on the physical path when 4,000 pairs or more are used, HP recommends
that you restrict the number of pairs so that 4,000 pairs or less use one physical path.
Initiator Ports and RCU Target Ports
The initiator ports are the dedicated Fibre Channel interface ports on the main storage system
(MCU) to which the RCUs (RCU target ports) are connected. The initiator ports connect to the RCUs
to send write I/O operations directly to the RCUs. Any Fibre Channel interface port of the HP disk
array can be configured as an initiator port. The TrueCopy for Mainframe software allows you to
change the configuration of the HP disk array Fibre Channel ports (ordinary target port, initiator
port, or RCU target port) as needed.
The RCU target ports are the dedicated Fibre Channel interface ports on the remote storage system
(RCU) to which the MCU (initiator ports) are connected. Any Fibre Channel interface port of the
HP disk array can be configured as an RCU target port. The RCU target ports can be connected
to the host channel paths via the Fibre Channel switch.
To fully support an automated environment, the HP disk array automatically configures a Fibre
Channel port as an initiator or RCU target if required in response to the TSO CESTPATH and
CDELPATH commands. See system option mode 114 in
“XP Disk Array Modes for TrueCopy for
Mainframe” (page 12) .
For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same
time as the SCSI path definition function of LUN Manager.
Two or more initiator ports must be configured before you can add the RCUs and create the
TrueCopy for Mainframe pairs. The initiator ports cannot communicate with the host processor
channels. To enable the host processor channels to send write I/O operations to the MCU, the
host channel paths must be connected to the other Fibre Channel interface ports in the MCU.
Ordinary Fibre Channel interface ports cannot be connected to the MCU. These ports (usually
called target ports) can be connected to the host processor channels only.
TrueCopy Software
The HP disk array includes TrueCopy for Mainframe and Continuous Access. The Remote Web
Console software communicates with the SVP of the XP via defined TCP/IP connections. For further
information on the Remote Web Console's operations, see the HP XP24000/XP20000 Remote
Web Console User's Guide or contact your HP service representative.
If you plan to use PPRC to perform TrueCopy for Mainframe Asynchronous operations, you must
use the TrueCopy for Mainframe software to add the consistency groups and select the desired
group options and async options before you can add any TrueCopy for Mainframe Asynchronous
pairs. These functions can only be performed using the Remote Web Console software (or SVP).
Once the groups and async options have been configured, PPRC commands can be used to
establish and manage TrueCopy for Mainframe Asynchronous pairs.
If you will be using the Remote Web Console software to perform TrueCopy for Mainframe
operations (instead of PPRC), the MCU of each TrueCopy for Mainframe pair must be LAN-attached
to the Remote Web Console computer. You should also attach all RCUs to an Remote Web Console
computer on a separate LAN at the remote site. Having a separate LAN at the remote site enables
you to access the RCUs and TrueCopy for Mainframe R-VOLs and perform TrueCopy for Mainframe
operations at the remote site in the event that the main site is not available (for example, due to
disaster). If you need to perform TrueCopy for Mainframe operations in the reverse direction from
the remote site to the primary site (for example, disaster recovery), the TrueCopy for Mainframe
software at the remote site simplifies and expedites this process.
For information on TrueCopy for Mainframe Async configuration services, contact your HP service
representative.
16 About TrueCopy for Mainframe Operations