User`s guide

Refer to Chapter 6 and Appendix B for examples for adding storagesets. If
you do not need storagesets for your configuration, skip this step.
Note
If you add a removable media device to an HSJ or HSD30 controller, it
is not known to the host until one of the following occurs: the media is
loaded into the device, the host is reinitialized, or the virtual circuit is
broken and reestablished.
Remember that CD–ROMs are always set TRANSPORTABLE and are
seen by the OpenVMS operating system as DKA devices.
3. (For all controller models:) Enter the INITIALIZE command to initialize
containers (devices or storagesets) prior to using them for host units. Refer to
Section 5.3 for details about initializing transportable and nontransportable
disk drives.
CLI> INITIALIZE container-name
For example:
CLI> INITIALIZE DISK0
CLI> INITIALIZE STRIPE0
CLI> INITIALIZE RAID99
CLI> INITIALIZE MIRR2
CAUTION
The INITIALIZE command destroys all host-accessible data on the
container. Refer to the Appendix B INITIALIZE command section of
this manual for specific requirements for using this command.
When initializing a single disk drive container, if NOTRANSPORTABLE
was specified or (allowed to default) on the ADD DISK or SET disk-name
commands, a small amount of disk space is made inaccessible to the host
and used for metadata. However, if TRANSPORTABLE was specified, any
metadata is destroyed on the device and the full device is accessible to the
host. Refer to Appendix B for details of when initializing is required.
4. (For all controller models:) Add the units that use either the devices
directly or the storagesets built from the devices by entering the following
command at the CLI> prompt:
CLI> ADD UNIT logical-unit-number container-name
For example: CLI> ADD UNIT D300 DISK0
CLI> ADD UNIT D200 RAID99
where:
logical-unit-number is the unit number the host uses to access the device.
container-name identifies the device or the storageset.
A point to remember is that certain information related to the companion
controller in a dual-redundant configuration may not always appear on the
display screen. When a device or parameter information does not appear after
entering a command from one controller, enter the same command from the other
controler.
5–16 Controller Operations