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

Hitachi TrueCopy for z/OS user guide 23
Initiator ports and RCU target ports
The initiator ports are the dedicated Fibre Channel interface ports on the main disk array (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 XP12000/XP10000 can be
configured as an initiator port. Use the Port Change window to change the configuration of the
XP12000/XP10000 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 subsystem (RCU) to
which the MCU (initiator ports) are connected. Any Fibre Channel interface port of the XP12000/XP10000
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 XP12000/XP10000 is capable of automatically
configuring a Fibre Channel port as an Initiator or RCU target if required in response to the TSO CESTPATH
and CDELPATH commands. See the SVP system option mode 114 in Table 3 on page 18.
NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same
time as the SCSI path definition function of LUN Management.
Two or more initiator ports must be configured before you can add the RCUs and create the TC390 volume
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.
Remote control ports (RCPs) and local control ports (LCPs)
The remote control ports (RCPs) are the dedicated serial interface ports on the main disk subsystem (MCU)
to which the RCUs are connected. The RCPs emulate host processor channels to enable the MCUs to send
write I/O operations directly to the RCUs. The RCPs support the dynamic switching capability provided by
the ESCDs. Any serial port of the XP12000/XP10000 can be configured as an RCP. You can use TC390 to
change the configuration of the disk array serial ports (LCP or RCP) as needed.
The local control ports (LCPs) are used for connecting with the host processor channel interface. All serial
interface ports on the XP12000/XP10000 have a default setting of LCP. An RCU port connected to an
MCU must be in LCP mode to receive remote copy I/O operations from the MCU.
To fully support an automated environment, the XP12000/XP10000 is capable of automatically
configuring a serial port as an RCP or LCP if required in response to the TSO CESTPATH and CDELPATH
commands. See the SVP mode 114 in Table 3 on page 18.
CAUTION: Before issuing the CESTPATH command, verify that the relevant paths are offline from the
host(s) (for example, configure the Chipid offline, deactivate the LPAR, or block the port in the ESCD). If any
active logical paths still exist, the add path operation will fail because the port mode (LCP/RCP) cannot be
changed.
FICON ESCON Not Supported 1
FICON Fibre Channel Supported
1. The configuration of FICON for channel-MCU paths and ESCON for MCU-RCU paths is not
supported, because the bandwidth of FICON is greater than that of ESCON interface. If FICON is
used for channel-MCU paths, use Fibre Channel interface for the MCU-RCU paths.
Table 4 TC390 configuration with FICON (continued)
Application Site Path (System - DKC) MCU-RCU For Use