HP StorageWorks XP Remote Web Console Software User Manual
Page 25
25
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 XP128/XP1024/XP10000/XP12000 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 XP128/XP1024/XP10000/XP12000 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 XP128/XP1024/XP10000/XP12000 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
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.
Two or more RCPs must be configured before you can add the RCUs and establish the TC390 volume
pairs. The RCPs cannot communicate with the host processor channels and are dedicated to TC390
operations. The host channel interface paths must be connected to the other serial interface ports on the
disk array.
Also, the serial interface ports, 1S-1Z and 2S-2Z, cannot be specified as RCPs.
The CHA package port that is added to DKA slot cannot be specified as RCPs. Therefore, if you specify this
port number to use TSO CESTPATH command, an error will occur.
Command View XP Management Station or XP Remote Web Console
The Command View XP management station or XP Remote Web Console communicates with the each
attached XP128/XP1024/XP10000/XP12000. The SVP at the main site must be connected to the MCU
of each TC390 volume pair. A second SVP should also be installed at the remote site and connected to the
RCUs. With another SVP at the remote site, you can modify the async options of the RCU (pending update
data rate, offloading timer) and access the TC390 R-VOLs (for example, to perform ICKDSF). If you need to
perform TC390 operations in the reverse direction from the remote site to the main site (for example,
disaster recovery), using TC390 through Command View XP or XP Remote Web Console simplifies and
expedites this process.
If you plan to perform TC390A operations, you must use the TC390 software to add the consistency groups
and select group options and async options before you can add any TC390A pairs. These functions can
be performed only using TC390 through Command View XP or XP Remote Web Console. After the
consistency groups and asynchronous options have been configured, the PPRC TSO commands can be
used to establish and manage TC390A pairs.