User`s guide

5.3 Using the TRANSPORTABLE and NOTRANSPORTABLE
Qualifiers
Before initializing a device using the CLI INITIALIZE command, make sure
you know the status of that device. Ask yourself the following questions before
proceeding with a device initialization:
• Will this device be used on HSx and HSC controllers, or not moved at all?
• Will this device be used on an HS array controller or HSC controller? (If so,
set it NOTRANSPORTABLE.)
• Did it come from a non-HS or non-HSC k.SCSI array controller system?
When you bring a device from non-HS or non-HSCk.SCSI array controller system,
and initialize it as nontransportable, you lose a few blocks of data. This is the
metadata at the end of the LBN area.
Therefore, when bringing non-HS array/non-HSC K.SCSI devices to an
HSJ/HSD30/HSZ array controller system, initialize the device as transportable,
then copy the data on that disk to another nontransportable unit. Then
reinitialize that device as nontransportable, thereby putting metadata on the
previously transportable device.
CAUTION
Do not keep any device set as transportable on an HSJ/HSD/HSZ array
controller system because you want forced error support on all units
behind the HS array controllers. This is mandatory for use in Host-Based
Volume Shadowing and is important for improving the data integrity of
the entire array. Devices set transportable are not supported for host
shadow sets. The exception is for CD–ROMs and certain optical disks.
CD–ROMs are always set TRANSPORTABLE.
The transportable feature is provided to bring old non-HS array controller
system customer data into the array system easily, not for normal system
usage.
If you bring in a nontransportable device and initialize it, you destroy all
forced error information for that device. So instead, if the unit was already set
nontransportable, just enter the CLI ADD UNIT command (after adding the
disk), and the HS array controller code verifies that the metadata is present. An
initialization is NOT required.
Devices set transportable are not MSCP compliant. Devices set nontransportable
(using the NOTRANSPORTABLE qualifier) are MSCP compliant, because they
have metadata that provides forced error support.
5.4 Customer Acceptance Tests with Power Applied
This section describes customer acceptance tests. Refer to Chapter 7 for
information on how to run DILX and TILX.
After you install, set parameters for, and configure your controller subsystem,
perform the following acceptance tests for your subsystem:
• Power ON your subsystem—This resets all shelves and starts the spin-up
cycle of the devices within the shelves. This includes the initialization
(diagnostics) on the controllers and device self-tests.
Controller Operations 5–17