Digital PDFs

EK-CLI40-RM-B01

March 1997

118 pages

Original

0.3MB

Document:	DIGITAL StorageWorks HSZ40 Array Controller HSOF 3.1 CLI Reference Manual
Order Number:	EK-CLI40-RM
Revision:	B01
Pages:	118
Original Filename:

OCR Text

DIGITAL StorageWorks
HSZ40 Array Controller
HSOF 3.1
CLI Reference Manual
Part Number: EK–CLI40–RM. B01

March 1997

Software Version:

Digital Equipment Corporation
Maynard, Massachusetts

HSOF Version 3.1

March 1997
While Digital Equipment Corporation believes the information included in this manual is correct as of the date of publication, it
is subject to change without notice. DIGITAL makes no representations that the interconnection of its products in the manner
described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document
imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. No responsibility is
assumed for the use or reliability of firmware on equipment not supplied by DIGITAL or its affiliated companies. Possession,
use, or copying of the software or firmware described in this documentation is authorized only pursuant to a valid written license
from DIGITAL, an authorized sublicensor, or the identified licensor.
Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to
the U.S. Government with DIGITAL’S standard commercial license and, when applicable, the rights in DFAR 252.227-7015,
“Technical Data—Commercial Items.”
© Digital Equipment Corporation, 1997.
Printed in U.S.A.
All rights reserved.
CI, DIGITAL, HSC, HSJ, HSD, HSZ, OpenVMS, StorageWorks, VAX, VAXcluster, VMS, VMScluster, and the DIGITAL logo
are trademarks of Digital Equipment Corporation. All other trademarks and registered trademarks are the property of their
respective holders.
UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company LTD.
SUN is a registered trademark of Sun Microsystems Corp.
IBM is a registered trademark of International Business Machines Corp.
Windows NT is a registered trademark of Microsoft Corporation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense. Restrictions apply to the use of the local-connection port on this series of controllers; failure to
observe these restrictions may result in harmful interference. Always disconnect this port as soon as possible after completing
the setup operation. Any changes or modifications made to this equipment may void the user's authority to operate the
equipment.
Warning!
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
Achtung!
Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen
auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.
Avertissement!
Cet appareil est un appareil de Classe A. Dans un environnement résidentiel cet appareil peut provoquer des brouillages
radioélectriques. Dans ce cas, il peut être demandé à l’ utilisateur de prendre les mesures appropriées.

iii

Table of Contents
1 Introduction to the CLI .............................................................1–1
CLI Overview ......................................................................................................... 1–2
Accessing and Exiting the CLI................................................................................ 1–3
Capturing Your CLI Session ................................................................................... 1–4
Entering CLI Commands......................................................................................... 1–4
Specifying the Device PTL ..................................................................................... 1–5
Syntax .............................................................................................................. 1–6

2 CLI Commands..........................................................................2–1
ADD CDROM ........................................................................................................ 2–2
ADD DISK ............................................................................................................. 2–3
ADD MIRRORSET ................................................................................................ 2–5
ADD PASSTHROUGH........................................................................................... 2–8
ADD RAIDSET .................................................................................................... 2–10
ADD SPARESET.................................................................................................. 2–13
ADD STRIPESET................................................................................................. 2–14
ADD UNIT ........................................................................................................... 2–16
CLEAR_ERRORS CLI ......................................................................................... 2–22
CLEAR_ERRORS INVALID_CACHE................................................................. 2–23
CLEAR_ERRORS LOST_DATA ......................................................................... 2–25
CLEAR_ERRORS UNKNOWN ........................................................................... 2–26
CLEAR_ERRORS UNWRITEABLE_DATA ....................................................... 2–27
CREATE_PARTITION......................................................................................... 2–28
DELETE container-name...................................................................................... 2–30
DELETE device-name .......................................................................................... 2–31
DELETE FAILEDSET.......................................................................................... 2–32

HSZ40 Array Controller

CLI Reference Manual

DELETE SPARESET ........................................................................................... 2–33
DELETE unit-number........................................................................................... 2–34
DESTROY_PARTITION...................................................................................... 2–35
DIRECTORY ....................................................................................................... 2–36
EXIT..................................................................................................................... 2–37
HELP.................................................................................................................... 2–38
INITIALIZE ......................................................................................................... 2–39
LOCATE .............................................................................................................. 2–42
MIRROR .............................................................................................................. 2–44
REDUCE .............................................................................................................. 2–47
RENAME ............................................................................................................. 2–49
RESTART THIS_CONTROLLER and RESTART OTHER_CONTROLLER ...... 2–50
RETRY_ERRORS UNWRITEABLE_DATA ....................................................... 2–52
RUN ..................................................................................................................... 2–53
SELFTEST OTHER_CONTROLLER and SELFTEST THIS_CONTROLLER .... 2–54
SET device-name .................................................................................................. 2–56
SET FAILEDSET ................................................................................................. 2–58
SET FAILOVER................................................................................................... 2–59
SET mirrorset-name.............................................................................................. 2–61
SET MULTIBUS_FAILOVER ............................................................................. 2–65
SET NOFAILOVER (SET NOMULTIBUS_FAILOVER) .................................... 2–68
SET THIS_CONTROLLER and SET OTHER_CONTROLLER........................... 2–70
SET RAIDset-name ............................................................................................... 2–75
SET unit-number................................................................................................... 2–77
SHOW .................................................................................................................. 2–82
SHUTDOWN THIS_CONTROLLER and SHUTDOWN OTHER_CONTROLLER2–86
UNMIRROR......................................................................................................... 2–88

Glossary
Index
Figures
Figure 1–1 Identifying THIS_CONTROLLER, OTHER_CONTROLLER .......................... 1–2
Figure 2–1 Controller Connections in Multiple Bus Failover Configuration ....... 2–66

CLI Reference Manual

HSZ40 Array Controller

Related Documents
The following table lists some of the documents related to the use of this product.
Document title

Part number

DECevent Installation Guide

AA–Q73JA–TE

StorageWorks BA350–MA Controller Shelf User's
Guide

EK–350MA–UG

StorageWorks Configuration Manager for DEC
OSF/1 Installation Guide

AA–QC38A–TE

StorageWorks Configuration Manager for DEC
OSF/1 System Manager's Guide for HSZterm

AA–QC39A–TE

StorageWorks Solutions Configuration Guide

EK–BA350–CG

StorageWorks Solutions Shelf and SBB User's
Guide

EK–BA350–UG

StorageWorks Solutions SW300-Series RAID
Enclosure Installation and User's Guide

EK–SW300–UG

StorageWorks SW500-Series Cabinet Installation
and User's Guide

EK–SW500–UG

StorageWorks SW800-Series Data Center Cabinet
Installation and User's Guide

EK–SW800–UG

The RAIDBOOK—A Source for RAID
Technology

RAID Advisory
Board

Polycenter Console Manager User's Guide

Computer Associates

VAXcluster Systems Guidelines for VAXcluster
System Configurations

EK–VAXCS–CG

16-Bit SBB User’s Guide

EK-SBB16-UG

7-Bit SBB Shelf (BA356 Series) User’s Guide

EK-BA356-UG

SBB User’s Guide

EK-SBB35-UG

HSZ40 Array Controller

CLI Reference Manual

1
Introduction to the CLI
CLI Overview
How to Access and Exit the CLI
Entering CLI Commands

HSZ40 Array Controller

CLI Reference Manual

1–2

Introduction to the CLI

CLI Overview
The command line interpreter (CLI) is one of the user interfaces to the StorageWorks™
array controllers in your subsystem. The CLI commands allow you to manage the
subsystem by viewing and modifying the configuration of the controllers and the devices
attached to them. You also use the CLI to start controller diagnostic and utility programs.
CLI commands for configuring and viewing the controllers use the relative terms
THIS_CONTROLLER and OTHER_CONTROLLER. THIS_CONTROLLER always refers to
the controller that is running the current CLI session. You may have a maintenance
terminal or PC directly connected to the terminal port on the front of the controller, or you
may be using a virtual terminal connection through the host bus. In either case,
THIS_CONTROLLER is the one that you are interacting with directly. This is shown in Figure
1–1.

Figure 1–1 Identifying THIS_CONTROLLER, OTHER_CONTROLLER

OTHER_CONTROLLER

THIS_CONTROLLER

CXO-5193A-MC

OTHER_CONTROLLER always refers to the controller that is not running the current CLI
sessionthe one that is not connected to a terminal or terminal session.

CLI Reference Manual

HSZ40 Array Controller

Introduction to the CLI

1–3

Accessing and Exiting the CLI
__________________________ Note _____________________________
The maintenance terminal port on the controller is meant to be used only for
initial configuration and required maintenance functions. Operation of this port
may cause harmful radio frequency interference. Always disconnect the terminal
and cable when you have finished working with the controller.
____________________________________________________________
You can access the CLI from a maintenance terminal connected to the front bezel of the
controller (local connection) or through the host operating system using a VAXcluster™
system console (VCS), a diagnostic and utility protocol (DUP), or an HSZterm (remote
connection). You must use a local connection to perform initial controller configuration,
such as setting the controller ID. Once you have completed initial configuration and the
controller is visible on the host bus, you can perform all other configuration through a
remote connection.
In a dual-redundant controller configuration, you can view and set the configurations of
both controllers with one local or remote connection. Use THIS_CONTROLLER commands to
change the configuration on the controller that is running the CLI session. Use
OTHER_CONTROLLER commands to view or change the configuration on the partner
controller.
If you are using a remote DUP connection to the CLI, enter the EXIT command at the CLI
prompt to close the connection. You do not need to exit from a local connection.

HSZ40 Array Controller

CLI Reference Manual

1–4

Introduction to the CLI

Capturing Your CLI Session
If you are using a remote terminal connection via DUP on an OpenVMS™ system and you
specify the /LOG switch on your command line, a log file of your CLI session is created.
You must use the EXIT command to exit the CLI in order to close and print the log file.

Entering CLI Commands
Use the following tips and techniques when entering CLI commands:
•

Commands are not case sensitive.

•

With few exceptions, you only need to enter enough of each command to make the
command unique (usually three characters). For example, SHO is equivalent to SHOW.

•

While the controller is processing a command, you can enter succeeding commands
without waiting for the CLI prompt. The controller will process each command when
it has completed the previous command. (A unit that is experiencing heavy I/O load
may be slow to respond to CLI commands.)

•

You can enter only one switch (or “qualifier”) with each SET command. To enter
multiple switches for the same device or unit, you must use multiple SET commands.

You can recall and edit the last five commands. This feature can save time and help
prevent mistakes when you need to enter similar commands during configuration. Use the
following keys to recall and edit commands:
Key

Function

Up Arrow or Ctrl/B,
Down Arrow or
Ctrl/N

Steps backward and forward through the five most recent CLI
commands.

Left arrow or Ctrl/D,
Right arrow or
Ctrl/F

Moves the cursor left or right in a command line.

Ctrl/E

Moves the cursor to the end of the line.

Ctrl/H or Backspace

Moves the cursor to the beginning of the line.

Ctrl/J or Linefeed

Deletes the word to the left of the cursor.

Ctrl/U

Deletes characters from the beginning of the line to the cursor.

Ctrl/A

Toggles between insert mode and overstrike mode. The default
setting is insert mode, which allows you to insert characters at the
cursor location, moving the existing characters to the right.
Overstrike mode replaces existing characters when you type. The
CLI returns to insert mode at the beginning of each line.

Ctrl/R

Recalls the contents of the command line. This is especially
helpful if the system issues a message that interrupts your typing.

CLI Reference Manual

HSZ40 Array Controller

Introduction to the CLI

1–5

Specifying the Device PTL
Units accessed by the controller are commonly called logical units (LUN). Each logical
unit has a number that is device addressable through a target. Often, a command requires
that a device’s port-target-LUN (PTL) address be entered. The PTL address is a five-digit
address by which the controller identifies the location of the device.
•

P—Designates the controller’s SCSI port number (1 through 6 for 6-port controllers).

•

T—Designates the target identification (ID) number of the device. Valid target ID
numbers for a single-controller configuration are 0 through 6. Valid target ID numbers
for a dual-redundant-controller configuration are 0 through 5.

•

L—Designates the LUN of the device (must be 0).

Place one space between the port number, target number, and the two-digit LUN number
when entering the PTL address. An example of a PTL address follows:

1 02 00

__________________________ Note _____________________________
DIGITAL UNIX® requires passthrough units to be at LUN 0. OpenVMS accepts
LUN numbers 0 through 7.
____________________________________________________________

HSZ40 Array Controller

CLI Reference Manual

1–6

Introduction to the CLI

Syntax
Commands to the controller must match the following command structure:
COMMAND PARAMETER SWITCHES

Q
Q
Q

Command—Instructs the controller to do something. For example, the SET
command instructs the controller to set something.
Parameter—The object that receives the command and is assigned the task
of processing the command.
Switches—Reserved words that have a special function. For example, the
member switch indicates that the term after it is the name or number of the
storage member.

CLI Reference Manual

HSZ40 Array Controller

2
CLI Commands
Descriptions of all CLI Commands
Required Parameters
Optional Switches
Examples

2–2

ADD CDROM

ADD CDROM
Adds a CD–ROM drive to the controller configuration and names the drive.

Format
ADD CDROM CDROM-name SCSI-location

Parameters
CDROM-name
Specifies a name for the CD−ROM drive. You use this name with the ADD UNIT command
to identify the CD−ROM drive as a host-addressable unit.
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
SCSI-location
The SCSI-Location parameter assigns a PTL address to the CD-ROM that is used by the
controller. See page 1–5, Specifying the Device PTL, for an explanation of the PTL
numbering system.

Examples
To add a CD−ROM drive at port 1, target 0, LUN 0, named CD_PLAYER:
CLI> ADD CDROM CD_PLAYER 1 0 0

See also
ADD UNIT
DELETE
SHOW CDROM

ADD DISK

2–3

ADD DISK
Adds a disk drive to the controller configuration and names the drive.

Format
ADD DISK disk-name SCSI-location

Parameters
disk-name
Specifies a name for the disk drive. You use this name when adding the disk drive to a
storageset or with the ADD UNIT command to create a single-disk host-addressable unit.
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
SCSI-location
The SCSI-location parameter assigns a PTL address to the disk drive. See page 1–5,
Specifying the Device PTL, for an explanation of the PTL numbering system.

Switches
TRANSPORTABLE
NOTRANSPORTABLE (Default)
Specify the TRANSPORTABLE switch for any disk drive that you want to move to and from
StorageWorks environments with the data intact.
__________________________ Note _____________________________
Use the TRANSPORTABLE switch only for disk drives that must be moved to
StorageWorks environments with data intact.
____________________________________________________________
A TRANSPORTABLE disk drive does not contain any special information space and can be
moved to a non-StorageWorks environment with its data intact. You cannot use a
TRANSPORTABLE disk drive in any type of storageset, such as a stripeset or RAIDset.
Specify NOTRANSPORTABLE for all disk drives that will be used in RAIDsets, stripesets, and
mirrorsets. Also use the NOTRANSPORTABLE switch for all single-disk units that will be
used exclusively in a StorageWorks or HSC™ controller.
The controller makes a small portion of nontransportable disk drives inaccessible to the
host and uses the space to store information (metadata) that improves data reliability, error
detection, and recovery. Because of this metadata, only StorageWorks controllers can
retrieve user data from nontransportable disk drives.
HSZ40 Array Controller

CLI Reference Manual

2–4

ADD DISK

Examples
To add nontransportable DISK100 at port 1, target 0, LUN 0:
CLI> ADD DISK DISK100 1 0 0

To add transportable disk DISK230 at port 2, target 3, LUN 0:
CLI> ADD DISK DISK230 2 3 0 TRANSPORTABLE

See also
DELETE
LOCATE
SHOW DISKS
SET disk-name

ADD MIRRORSET

2–5

ADD MIRRORSET
Adds a mirrorset to the controller configuration and names the mirrorset. The number of
members is set to the number of devices specified in the command.

Format
ADD MIRRORSET mirrorset-name disk-name1 [disk-nameN]

Parameters
mirrorset-name
Specifies a name for the mirrorset. You use this name with the ADD UNIT command to
identify the mirrorset as a host-addressable unit.
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
disk-name1 disk-nameN
The names of the disk drives that make up the mirrorset. A mirrorset contains 1 to 6 disk
drives.

Switches
COPY=NORMAL (Default)
COPY=FAST
__________________________ Note _____________________________
A normal mirrorset member is one whose entire contents are the same as all
other normal members.
____________________________________________________________
The COPY switch allows you to set the speed at which the controller copies data from
normal mirrorset members to new members.
Select NORMAL to prioritize other controller operations over the copy operation. The
controller uses relatively few resources to perform the copy, and there is little impact on
performance.
Select FAST when the copy operation must take precedence over other controller
operations. The controller uses more resources and the copy takes less time, but overall
controller performance is reduced during the copy.

HSZ40 Array Controller

CLI Reference Manual

2–6

ADD MIRRORSET

POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
The POLICY switch allows you to set the criteria the controller uses to choose a replacement
member from the spareset when a mirrorset member fails.
Select BEST_FIT to choose a replacement device from the spareset that most closely
matches the capacities of the remaining members. If more than one device in the spareset
is the correct size, the controller selects the device that gives the best performance.
Select BEST_PERFORMANCE to choose a replacement device from the spareset that results in
the best performance (the device should be on a different port than existing members). If
more than one device in the spareset has the best performance, the controller selects the
device that most closely matches the size of the remaining members.
READ_SOURCE=ROUND_ROBIN
READ_SOURCE=LEAST_BUSY (Default)
READ_SOURCE=disk-name
The READ_SOURCE switch allows you to control which mirrorset member is used by the
controller to satisfy a read request.
Select ROUND_ROBIN to cause the controller to direct read requests to each NORMAL
mirrorset member in sequential membership order. No preference is given to any NORMAL
member.
Select LEAST_BUSY to cause the controller to direct read requests to the NORMAL mirrorset
member with the least busy work queue.
Select the disk-name of a specific member to cause the controller to direct all read requests
to that member. If that member fails out of the mirrorset, the controller reverts to the
LEAST_BUSY method for mirrorset read requests.

Examples
To add DISK100, DISK210, and DISK320 as a mirrorset with the name MIRR1:
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD MIRRORSET MIRR1 DISK100 DISK210 DISK320
CLI> INITIALIZE MIRR1
CLI> ADD UNIT D305 MIRR1

ADD MIRRORSET

2–7

See also
ADD DISK
DELETE
INITIALIZE
MIRROR
REDUCE
SHOW MIRRORSETS
UNMIRROR

HSZ40 Array Controller

CLI Reference Manual

2–8

ADD PASSTHROUGH

ADD PASSTHROUGH
Creates a passthrough container (command disk) to allow direct access to a device. HSZ
controllers use passthrough containers to communicate with tape drives and tape loaders.

Format
For tape drives and loaders attached to HSZ controllers:
ADD PASSTHROUGH passthrough-name SCSI-location

Parameters
passthrough-name
Specifies a name for the passthrough container. You use this name with the ADD UNIT
command to identify the passthrough container as a host-addressable unit. You may want
to use a name that indicates the type of device served by the passthrough container, such as
“TAPE” or “LOADER.”
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
SCSI-location
The SCSI-location parameter assigns a PTL address to the drive or loader. See page 1–5,
Specifying the Device PTL, for an explanation of the PTL numbering system.

ADD PASSTHROUGH

2–9

Examples
__________________________ Note _____________________________
DIGITAL UNIX requires HSZ passthrough units to be at LUN 0 (the third digit
in the unit number). OpenVMS accepts LUN numbers 0-7.
____________________________________________________________
To add tape drive TAPE230 at port 2, target 3, LUN 0:
CLI> ADD PASSTHROUGH TAPE230 2 3 0
CLI> ADD UNIT P100 TAPE230

See also
ADD UNIT
DELETE
SHOW PASSTHROUGH

HSZ40 Array Controller

CLI Reference Manual

2–10

ADD RAIDSET

ADD RAIDSET
Creates a RAIDset from 3 to 14 disks.

Format
ADD RAIDSET RAIDset-name disk-name1 disk-name2 [disk-nameN]

Parameters
RAIDset-name
Specifies a name for the RAIDset. You use this name with the ADD UNIT command to
identify the RAIDset as a host-addressable unit.
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
disk-name1 disk-name2 disk-nameN
The disks that will make up the RAIDset. A RAIDset can contain 3 to 14 member disks.

Switches
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
The POLICY switch allows you to set the criteria the controller uses to choose a replacement
member from the spareset when a RAIDset member fails.
Select BEST_FIT to choose a replacement device from the spareset that most closely
matches the capacities of the remaining members. If more than one device in the spareset
is the correct size, the controller selects the device that gives the best performance.
Select BEST_PERFORMANCE to choose a replacement device from the spareset that results in
the best performance (the device should be on a different port than existing members). If
more than one device in the spareset has the best performance, the controller selects the
device that most closely matches the size of the remaining members.
Select NOPOLICY to prevent the controller from replacing a failed disk drive. This causes
the RAIDset to run in a reduced state until a BEST_FIT or BEST_PERFORMANCE policy is
selected, or a member is manually replaced in the RAIDset (see SET RAIDset-name).
RECONSTRUCT=NORMAL (Default)
RECONSTRUCT=FAST
The RECONSTRUCT switch allows you to set the speed at which the controller reconstructs
the data on a new RAIDset member that has replaced a failed member.

ADD RAIDSET

2–11

Select NORMAL to balance other controller operations against the reconstruct operation.
The controller uses relatively few resources to perform the reconstruct, and there is little
impact on performance.
Select FAST when the reconstruct operation must take precedence over other controller
operations. The controller uses more resources and the reconstruct takes less time, but
overall controller performance is reduced during the reconstruct.
REDUCED
NOREDUCED (Default)
The REDUCED switch allows you to add a RAIDset that is missing one member. You only
need to use the REDUCED switch if you are re-adding a reduced RAIDset to the subsystem.
The NOREDUCED setting is the default and indicates that all RAIDset members that make
up the RAIDset are being specified, such as when creating a new RAIDset.

Examples
To create RAIDset RAID9 with disks DISK100, DISK210, and DISK320:
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD RAIDSET RAID9 DISK100 DISK210 DISK320
CLI> INITIALIZE RAID9
CLI> ADD UNIT D204 RAID9

To create RAIDset RAID8 with disks DISK100, DISK210, and DISK320, and use the
BEST_FIT replacement policy:
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD RAIDSET RAID8 DISK100 DISK210 DISK320 POLICY=BEST_FIT
CLI> INITIALIZE RAID8
CLI> ADD UNIT D205 RAID8

This example shows creating a three-member RAIDset from the members of a fourmember RAIDset that was already reduced. Note that you must not initialize the RAIDset,
because it was initialized in its previous location.
CLI> ADD DISK DISK100 1 3 0
CLI> ADD DISK DISK210 2 4 0
CLI> ADD DISK DISK320 3 5 0
CLI> ADD RAIDSET RAID6 DISK130 DISK240 DISK350 REDUCED
CLI> ADD UNIT D205 RAID6

HSZ40 Array Controller

CLI Reference Manual

2–12

ADD RAIDSET

See also
ADD UNIT
DELETE
SET RAIDSET
SHOW RAIDSET
INITIALIZE

ADD SPARESET

2–13

ADD SPARESET
Adds a disk drive to the spareset and initializes the metadata on the drive. The spareset is a
pool of disk drives available to the controller to replace failing members of RAIDsets and
mirrorsets.

Format
ADD SPARESET disk-name

Parameters
disk-name
The name of the disk drive to add to the spareset. You can add only one drive to the
spareset with each command.

Examples
To add DISK220 and DISK330 to the spareset:
CLI> ADD DISK DISK220 2 2 0
CLI> ADD DISK DISK330 3 3 0
CLI> ADD SPARESET DISK220
CLI> ADD SPARESET DISK330

See also
DELETE SPARESET
SET FAILEDSET
SHOW SPARESET

HSZ40 Array Controller

CLI Reference Manual

2–14

ADD STRIPESET

ADD STRIPESET
Creates a stripeset out of 2 to 14 disks or mirrorsets.

Format
ADD STRIPESET stripeset-name container-name1 [container-nameN]

Parameters
stripeset-name
Specifies a name for the stripeset. You use this name with the ADD UNIT command to
identify the stripeset as a host-addressable unit.
The name must start with a letter (A–Z) and can then consist of up to eight more
characters made up of letters A-Z, numbers 0-9, periods (.), dashes (-), or underscores (_),
for a total of nine characters.
container-name1 container-nameN
The names of the disk drives or mirrorsets that make up the stripeset. A stripeset can be
made up of from 2 to 14 containers.

Examples
To create stripeset STRIPE1 with three disks: DISK100, DISK210, and DISK320:
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD STRIPESET STRIPE1 DISK100 DISK210 DISK320
CLI> INITIALIZE STRIPE1
CLI> ADD UNIT D403 STRIPE1

The next example shows creating a two-member striped mirrorset (a stripeset whose
members are mirrorsets). Note that you only need to initialize the stripeset; you do not
need to initialize the mirrorsets individually.
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD DISK DISK430 4 3 0
CLI> ADD MIRRORSET MR1 DISK100 DISK210
CLI> ADD MIRRORSET MR2 DISK320 DISK430
CLI> ADD STRIPESET STRIPE1 MR1 MR2
CLI> INITIALIZE STRIPE1
CLI> ADD UNIT D304 STRIPE1

ADD STRIPESET

2–15

See also
ADD UNIT
ADD MIRRORSET
DELETE
INITIALIZE
SHOW STRIPESET

HSZ40 Array Controller

CLI Reference Manual

2–16

ADD UNIT

ADD UNIT
Identifies a device, container, or partition as a host-addressable logical unit. The controller
maps all requests from the host to the logical unit number as requests to the container
specified in the ADD UNIT command.
You must initialize the disk drive or container before you can add it as a unit.

Format
ADD UNIT unit-number container-name

Parameters
unit-number
A number such as D104, where D represents a device-type letter, 1 is one of the controller
target IDs, and the 4 is a logical unit number (the middle number is always 0).
The device type letter is either “D” for disk containers (including CD–ROMs) or “P” for
passthrough containers created from tape drives and loaders.
The controller target ID must be in the range 0 to 7, and must be one of the IDs set with
the SET THIS_CONTROLLER ID and SET OTHER_CONTROLLER ID commands. You must leave
out the target ID if it is 0, and only use the logical unit number.
The logical unit number must be in the range 0 to 7. You can assign up to eight logical
units for each controller target ID.
Table 2–1 breaks out the components in HSZ unit numbering.
Table 2–1 HSZ Unit Numbering
Unit number

Device type

Target ID

LUN

D401

Disk

P100

Passthrough

Disk

On a partitioned container, all of the partitions must be addressed through a single
controller. Thus, the unit numbers for all partitions on a container must have the same
controller target ID.
container-name
The name of the container that is used to create the unit.

ADD UNIT

2–17

Switches
Table 2–2 lists all switches for the ADD UNIT command and shows which switches can be
used with each type of device and storageset. Descriptions of the switches follow the table.
Table 2–2 Switches for the ADD UNIT Command
Switch

RAID Stripe- set set

PARTITION=partition_number
MAXIMUM_CACHED_TRANSFER
PREFERRED_PATH
NOPREFERRED_PATH (Default)
READ_CACHE (Default)
NOREAD_CACHE
RUN (Default)
NORUN
WRITE_PROTECT
NOWRITE_PROTECT (Default)
WRITEBACK_CACHE
NOWRITEBACK_CACHE (Default)

9
9
9
9
9
9
9

Mirror- NoTrans Trans
set
Disk
Disk

9
9
9
9
9
9
9

9
9
9
9
9

CD–ROM Passthrough

9
9
9
9

__________________________ Note _____________________________
The RUN/NORUN switch cannot be specified for partitioned units.
____________________________________________________________
PARTITION=partition_number
The PARTITION switch allows you to set the unit number for a partition on a storageset or
single-disk unit. Use the partition-number to identify the partition for which you are
adding the host-addressable unit number. (Use the SHOW command to find partition
numbers for a storageset or single-disk unit.)
MAXIMUM_CACHED_TRANSFER=n
MAXIMUM_CACHED_TRANSFER=32 (Default)
The MAXIMUM_CACHED_TRANSFER switch allows you to set the largest transfer (in blocks)
to be cached by the controller. The controller will not cache any transfers over this size.
Valid values are 1–1024.

HSZ40 Array Controller

CLI Reference Manual

2–18

ADD UNIT

PREFERRED_PATH=THIS_CONTROLLER
PREFERRED_PATH=OTHER_CONTROLLER
NOPREFERRED_PATH (Default)
___________________________ Note ____________________________
All partitions on a container must be addressed through the same controller. If
you set PREFERRED_PATH for one partition, all partitions on that container will
inherit the same path.
____________________________________________________________
The PREFERRED_PATH switch allows you to balance I/O load by specifying the controller
through which the unit will be accessed. If you set NOPREFERRED_PATH for a unit, it can be
accessed through either controller.
The controllers only use the PREFERRED_PATH setting if they are in a dual-redundant
configuration. If one controller fails, all the devices are accessed through the remaining
controller, ignoring the PREFERRED_PATH setting.
___________________________ Note ____________________________
The PREFERRED_PATH and NOPREFERRED_PATH switches are valid only for HSZ
controllers in dual-redundant multiple bus-failover configurations. The preferred
path for units on dual-redundant HSZ controllers is determined by the first digit
in the unit number (the controller target ID) specified in the ADD UNIT command.
____________________________________________________________
When the failed controller is restarted, the drives automatically return to the controller
specified by the PREFERRED_PATH switch.
You can specify the PREFERRED_PATH switch on a single controller; however, the switch
will not take effect until you add a second controller and configure the two controllers for
dual-redundancy.
READ_CACHE (Default)
NOREAD_CACHE
The READ_CACHE switch allows you to enable or disable the use of read cache with a unit.
Read caching improves performance in almost all situations, so it is generally good to
leave it enabled. However, under certain workloads, like a backup, there may be a low
probability for a cache hit and it may be beneficial to turn read caching off to remove the
overhead of caching.
RUN (Default)
NORUN
The RUN switch allows you to enable and disable a unit's availability to the host.

ADD UNIT

2–19

Select NORUN to make a unit unavailable to the host and to cause any user data for that unit
to be flushed from the write-back cache to the disk drives. The devices that make up the
unit are still spun up.
Select RUN to make a unit available to the host.
__________________________ Note _____________________________
The RUN and NORUN switches cannot be specified for partitioned units.
____________________________________________________________

WRITE_PROTECT
NOWRITE_PROTECT (Default)
__________________________ Note _____________________________
Write protect disables the writing of any new data by the host. However, the
controller may still write to a write-protected RAIDset to satisfy a reconstruct
pass or to reconstruct a newly replaced member.
____________________________________________________________
The WRITE_PROTECT switch allows you to ensure that data on a unit is not overwritten.
Select WRITE_PROTECT to prevent write operations to the unit.
Select NOWRITE_PROTECT to allow both reads and writes to the unit.
WRITEBACK_CACHE
NOWRITEBACK_CACHE (Default)
__________________________ Note _____________________________
WRITEBACK_CACHE requires that write-back cache modules be installed in the
subsystem and that the licensed feature be enabled through FLS.
____________________________________________________________
The WRITEBACK_CACHE switch allows you to enable or disable the use of write-back cache
with a unit.
Select WRITEBACK_CACHE for all new RAIDsets and mirrorsets, and for all other units for
which you want this feature. The write-back cache improves performance for write
operations to the unit.

HSZ40 Array Controller

CLI Reference Manual

2–20

ADD UNIT

___________________________ Note ____________________________
It may take up to 5 minutes for the controller to flush unwritten data from the
cache once you disable write-back caching.
____________________________________________________________
Select NOWRITEBACK_CACHE for those units for which you want all writes to go directly to
devices without being cached.
Considerations When Using Write-back Caching
The following list summarizes considerations you must be aware of when using
write-back cache.
Two conditions will cause data contained within write-back cache to be lost: if
power from the main power supply and the external cache battery is
interrupted, or if the cache module is removed before the controller flushes
the data from the write-back cache.

•

•
•

When restarted, the controller attempts to flush any unflushed data within the write-back
cache to the devices. However, by specifying the IGNORE_ERRORS or
IMMEDIATE_SHUTDOWN switch, you allow data to reside in write-back cache when
the controller is turned off, regardless of any errors detected.

ADD UNIT

2–21

Examples
To create disk unit D102 from the single disk DISK100 and set unit access to be through
THIS_CONTROLLER:
CLI> ADD DISK DISK100 1 0 0
CLI> INITIALIZE DISK100
CLI> ADD UNIT D102 DISK100 PREFERRED_PATH=THIS_CONTROLLER

To create disk unit D107 from RAIDset RAID9 and enable write-back caching for the unit:
CLI> ADD DISK DISK110 1 1 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK310 3 1 0
CLI> ADD DISK DISK410 4 1 0
CLI> ADD RAIDSET RAID9 DISK110 DISK210 DISK310 DISK410
CLI> INITIALIZE RAID9
CLI> ADD UNIT D107 RAID9 WRITEBACK_CACHE

See also
CREATE_PARTITION
DELETE unit-number
SET unit-number
SHOW UNITS

HSZ40 Array Controller

CLI Reference Manual

2–22

CLEAR_ERRORS CLI

CLEAR_ERRORS CLI
Stops the display of current or previous error messages at the CLI prompt.
___________________________ Note ____________________________
This command does not clear the error conditions, it only stops displaying the
errors at the CLI prompt.
____________________________________________________________
The controller displays any error messages before the CLI prompt. After you correct the
error condition, you must issue the CLEAR_ERRORS CLI command or restart the
controller to clear the error message.

Format
CLEAR_ERRORS CLI

Examples
To clear the message “All NVPM components initialized to their default settings.” from
the CLI prompt:
CLI>
All NVPM components initialized to their default settings.
CLI> CLEAR_ERRORS CLI

See also
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS INVALID_CACHE

2–23

CLEAR_ERRORS INVALID_CACHE
Clears an INVALID_CACHE error and allows the controller and cache to resume
operation.
A controller presents an INVALID CACHE error during initialization if it detects a
mismatch between the cache information on the controller and the cache information on
the cache module. The controller allows only a limited set of CLI commands until you
clear the error, to prevent you from giving commands that may make the situation worse.
The CLEAR_ERRORS INVALID_CACHE command either clears the information in the
controller module or the information in the cache module.

Format
CLEAR_ERRORS controller INVALID_CACHE data_retention
You must completely spell out “INVALID_CACHE.”

Parameters
controller
Identifies the controller for which to clear the INVALID_CACHE condition. You must
specify either THIS_CONTROLLER or OTHER_CONTROLLER.
data_retention
Specifies whether to keep the cache data and overwrite the controller information
(NODESTROY_UNFLUSHED_DATA) or keep the controller information and discard the cache
data (DESTROY_UNFLUSHED_DATA).
Use the NODESTROY_UNFLUSHED_DATA parameter in the following situations:
•

You have replaced the controller module.

•

The controller’s nonvolatile memory (NVMEM) has lost its memory, possibly from an
NVMEM battery failure.

•

You removed the cache module while there was unflushed data.

Use the DESTROY_UNFLUSHED_DATA parameter in the following situations:
•

You have replaced the cache module.

•

Any other reason not listed above.

HSZ40 Array Controller

CLI Reference Manual

2–24

CLEAR_ERRORS INVALID_CACHE

Examples
To clear an invalid cache error on THIS_CONTROLLER after replacing a controller module:
CLI> CLEAR_ERRORS THIS_CONTROLLER INVALID_CACHE
NODESTROY_UNFLUSHED_DATA

To clear an invalid cache error on the O THER_CONTROLLER after replacing a cache module:
CLI> CLEAR_ERRORS OTHER_CONTROLLER INVALID_CACHE
DESTROY_UNFLUSHED_DATA

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS LOST_DATA

2–25

CLEAR_ERRORS LOST_DATA
Clears the lost data error on a unit.
__________________________ Note _____________________________
Issuing the CLEAR_ERRORS LOST_DATA command for one partition on a container
will clear the lost data for all partitions on the container.
____________________________________________________________
If a write-back cache module is removed or fails while it contains data that has not been
written to disk, a LOST DATA error is reported on the unit. The CLEAR_ERRORS
LOST_DATA command clears the lost data error but does not recover the lost data. It may
take up to 5 minutes to clear lost data.

Format
CLEAR_ERRORS unit-number LOST_DATA
You must completely spell out “LOST_DATA”.

Parameters
unit-number
Specifies the unit number that will have the lost data error cleared. The unit-number is the
name given the unit when it was created using the ADD UNIT command.

Examples
To clear the lost data error on disk unit D103:
CLI> CLEAR_ERRORS D103 LOST_DATA

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

HSZ40 Array Controller

CLI Reference Manual

2–26

CLEAR_ERRORS UNKNOWN

CLEAR_ERRORS UNKNOWN
Clears the UNKNOWN error from a device.
If a device has a failure such that the controller marks the device as UNKNOWN, the
controller does not check the device again to see if it has been repaired or if the failure
condition has been rectified. You must use this command for the controller to recognize
the device after you correct the condition that caused the device to be marked
UNKNOWN.

Format
CLEAR_ERRORS device-name UNKNOWN
You must completely spell out “UNKNOWN.”

Parameters
device-name
Specifies the name of the device with the UNKNOWN error.

Examples
To cause the controller to recognize DISK300, a previously UNKNOWN device:
CLI> CLEAR_ERRORS DISK300 UNKNOWN

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS UNWRITEABLE_DATA

2–27

CLEAR_ERRORS UNWRITEABLE_DATA
Clears the unwriteable data error on a unit.
_________________________Caution____________________________
This command causes loss of user data.
____________________________________________________________
If a container fails in a way that user data in the write-back cache cannot be written to the
container, the controller reports an unwriteable data error. The CLEAR_ERRORS
UNWRITEABLE_DATA command removes the data from the cache and clears the unwriteable
data error.

Format
CLEAR_ERRORS unit-number UNWRITEABLE_DATA
You must completely spell out “UNWRITEABLE_DATA.”

Parameters
unit-number
Specifies the unit number that will have the unwriteable data error cleared. The unitnumber is the name given the unit when it was created using the ADD UNIT command.

Examples
To clear the unwriteable data error on disk unit D103:
CLI> CLEAR_ERRORS D103 UNWRITEABLE_DATA

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
RETRY_ERRORS UNWRITEABLE_DATA

HSZ40 Array Controller

CLI Reference Manual

2–28

CREATE_PARTITION

CREATE_PARTITION
Marks part of a disk or storageset to be used as a separately addressable unit. You can
divide any disk or storageset into as many as six partitions, each of which can be
separately presented to the host.

Format
CREATE_PARTITION container-name SIZE=n

Parameters
container-name
___________________________ Note ____________________________
Once you have partitioned a container, you cannot reunify it without
reinitializing the container.
____________________________________________________________
The name of the disk or storageset from which you want to create a partition. This is the
name given the disk or storageset when it was created using the ADD command (ADD DISK,
ADD STRIPESET, and so forth). You can partition any disk, stripeset, mirrorset, striped
mirrorset, or RAIDset. You must initialize the container before creating partitions.
SIZE=percent
SIZE=LARGEST
Specifies the size of the partition to be created as a percentage of the total size of the disk
or storageset.
Specify a percentage of the total container capacity to set the partition to a particular size,
or to evenly divide the disk or storageset. The resulting partition will be slightly smaller
than the size you specify, to accomodate controller information and so that each partition
ends with a complete stripe.
Specify LARGEST to have the controller create the largest partition possible from unused
space on the disk or storageset. You must also use the LARGEST setting when creating the
last partition on a container, because the space will not be equal to an exact percentage
value.

CREATE_PARTITION

2–29

Examples
To create RAIDset R9 and divide it into four parts:
CLI> ADD DISK DISK100 1 0 0
CLI> ADD DISK DISK210 2 1 0
CLI> ADD DISK DISK320 3 2 0
CLI> ADD RAIDSET RAID9 DISK100 DISK210 DISK320
CLI> INITIALIZE RAID9
CLI> CREATE_PARTITION RAID9 SIZE=25
CLI> CREATE_PARTITION RAID9 SIZE=25
CLI> CREATE_PARTITION RAID9 SIZE=25
CLI> CREATE_PARTITION RAID9 SIZE=LARGEST
CLI> ADD UNIT D101 RAID9 PARTITION=1
CLI> ADD UNIT D102 RAID9 PARTITION=2
CLI> ADD UNIT D103 RAID9 PARTITION=3
CLI> ADD UNIT D104 RAID9 PARTITION=4

See also
ADD UNIT
DELETE unit-number
DESTROY PARTITION
SHOW

HSZ40 Array Controller

CLI Reference Manual

2–30

DELETE container-name

DELETE container-name
Deletes a container from the list of known containers. You cannot delete a container that is
in use by a higher-level container. For example, you cannot delete a disk that is a member
of a RAIDset, or a RAIDset that is declared as a unit. You must first delete the higherlevel containers.

Format
DELETE container-name

Parameters
container-name
___________________________ Note ____________________________
You cannot delete the spareset and failedset containers.
____________________________________________________________
Specifies a name that identifies the container. This is the name given the container when it
was created using the ADD command (ADD DISK, ADD STRIPESET, and so forth).

Examples
To delete disk drive DISK100:
CLI> DELETE DISK100

To delete stripeset STRIPE1:
CLI> DELETE STRIPE1

To delete RAIDset RAID9:
CLI> DELETE RAID9

See also
DELETE FAILEDSET
DELETE SPARESET
UNMIRROR

DELETE device-name

2–31

DELETE device-name
Deletes a device from the controller configuration.

Format
DELETE device-name

Parameters
device-name
The name of the device to delete.

Examples
To delete disk device number 120:
CLI> DELETE DISK120

To delete tape device number 130:
CLI> DELETE TAPE130

See also
SHOW UNITS
SHOW unit-number

HSZ40 Array Controller

CLI Reference Manual

2–82

SHOW

SHOW
Displays information about controllers, storagesets, devices, and partitions.
___________________________ Note ____________________________
The SHOW command may not display some information for devices accessed
through the companion controller in a dual-redundant configuration. When
device or parameter information does not appear, enter the same SHOW
command from the other controller.
____________________________________________________________

Format
SHOW device-type
SHOW device-name
SHOW storageset-type
SHOW storageset-name
SHOW UNITS
SHOW unit-name
SHOW THIS_CONTROLLER
SHOW OTHER_CONTROLLER

Parameters
device-type
Specifies the type of devices that you want to display:
DEVICES—All devices attached to the controller
CDROMS—All CD–ROM devices attached to the controller
DISKS—All disk drive devices attached to the controller
PASSTHROUGH—All passthrough containers attached to the controller
device-name
Specifies the name of a particular device that you want to display. For example, SHOW
DISK210 displays information about the device named DISK210.

SHOW

2–83

storageset-type
Specifies the type of storageset that you want to display:
STORAGESETS—all storagesets configured in the controller. This includes
stripesets, mirrorsets, RAIDsets, the spareset and the failedset.
RAIDSETS—all RAIDsets configured in the controller
STRIPESETS—all stripesets configured in the controller
MIRRORSETS—all mirrorsets configured in the controller
SPARESET—the pool of disk drives available to replace failing members of
RAIDsets and mirrorsets
FAILEDSET—all disk drives that have failed out of RAIDsets and mirrorsets
storageset-name
Specifies the name of a particular storageset that you want to display. For example, SHOW
STRIPE1 displays information about the stripeset named STRIPE1.
units
Displays information for all units configured to the controller.
unit-name
Specifies the name of a particular unit that you want to display. For example, SHOW D102
displays information about the unit named D102.
THIS_CONTROLLER
OTHER_CONTROLLER
Specifies the controller that you want to display.

Switches
FULL
Displays additional information about each device or controller.

Examples
To show a basic listing of CDROMs:
CLI> SHOW CDROM
Name
Type
Port Targ Lun
Used by
----------------------------------------------------------CDROM230
cdrom
2
3
0
D623
CDROM240
cdrom
2
4
0
D624

HSZ40 Array Controller

CLI Reference Manual

2–84

SHOW

To show a full listing of devices attached to the controller:
CLI> SHOW DEVICES FULL
Name
Type
Port Targ Lun
Used by
-----------------------------------------------------------------------------DISK100

disk
1
0
0
D500
DEC
RZ28
(C) DEC 435E
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 10MHZ (synchronous 10 MB/SEC negotiated)
Size: 4109470 blocks

DISK120

disk
1
2
0
S0
DEC
RZ28
(C) DEC 435E
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 10MHZ (synchronous 10 MB/SEC negotiated)
Size: 4109470 blocks

DISK140

disk
1
4
0
S0
DEC
RZ28M
(C) DEC 0616
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 10MHZ (synchronous 10 MB/SEC negotiated)
Size: 4109470 blocks

DISK200

disk
DEC
RZ28
Switches:
NOTRANSPORTABLE

D501

TRANSFER_RATE_REQUESTED = 10MHZ (synchronous 10 MB/SEC negotiated)
Size: 4109470 blocks
DISK220

disk
2
2
0
S0
DEC
RZ28B
(C) DEC 0006
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 10MHZ (synchronous 10 MB/SEC negotiated)
Size: 4109470 blocks

SHOW

2–85

To show a complete listing of the mirrorset named MIRR1:
CLI> SHOW MIRR1
Name
Storageset
Uses
Used by
-----------------------------------------------------------MIRR1
mirrorset
DISK130
D202
Switches:
NOPOLICY (for replacement)
COPY (priority) = NORMAL
READ_SOURCE = LEAST_BUSY
MEMBERSHIP = 2, 1 member present
State:
DISK130
(member 0) is NORMAL
Size: 4109470 blocks

To show the full information for a controller:
CLI> SHOW THIS_CONTROLLER FULL
Controller:
HSZ40-CX (C) ZG60300054 Firmware V31Z-0, Hardware 0000
Not configured for dual-redundancy
SCSI address 6
Time: NOT SET
Host port:
SCSI target(s) (4, 5), Preferred target(s) (5)
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS
Cache:
No cache
Host Functionality Mode = A
Licensing information:
RAID (RAID Option) is ENABLED, license key is VALID
WBCA (Writeback Cache Option) is ENABLED, license key is VALID
MIRR (Disk Mirroring Option) is ENABLED, license key is VALID
Extended information:
Terminal speed 19200 baud, eight bit, no parity, 1 stop bit
Operation control: 00000005 Security state code: 24968
Configuration backup disabled

HSZ40 Array Controller

CLI Reference Manual

2–86

SHUTDOWN THIS_CONTROLLER and SHUTDOWN OTHER_CONTROLLER

SHUTDOWN THIS_CONTROLLER and SHUTDOWN
OTHER_CONTROLLER
Flushes all user data from the specified controller's write-back cache (if present) and shuts
down the controller. The controller does not restart. All units accessed through the
controller failover to the surviving controller.
THIS CONTROLLER is the controller that is running the current CLI session.
OTHER_CONTROLLER is the controller that is not running the current CLI session.

Format
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

SHUTDOWN THIS_CONTROLLER and SHUTDOWN OTHER_CONTROLLER

2–87

Examples
To shut down THIS_CONTROLLER as long as there are no units online:
CLI> SHUTDOWN THIS_CONTROLLER

To shut down the other controller even if it cannot write all write-back cache data to units:
CLI> SHUTDOWN OTHER_CONTROLLER IGNORE_ERRORS

See also
RESTART THIS_CONTROLLER
RESTART OTHER_CONTROLLER
SELFTEST THIS_CONTROLLER
SELFTEST OTHER_CONTROLLER

HSZ40 Array Controller

CLI Reference Manual

2–88

UNMIRROR

UNMIRROR
Converts a one-member mirrorset back to a single device and deletes the mirrorset from
the list of known mirrorsets. You can use this command on mirrorsets that are already
members of higher level containers (stripesets or units).
The UNMIRROR command is not valid for devices that have a capacity greater than the
capacity of the mirrorset. If a mirrorset is comprised of devices of different capacities, the
mirrorset capacity is limited to the size of the smallest member; larger members will have
unused capacity. If a member with unused capacity is the last remaining member of a
mirrorset, you cannot use the UNMIRROR command to change the device back to a singledisk unit, because that change would cause a change in reported disk capacity, possibly
confusing the operating system.

Format
UNMIRROR disk-name

Parameter
disk-name
The disk-name parameter specifies the name of the mirrorset member to be removed from
the mirrorset.

Examples
To convert DISK130 back to a single device:
CLI> UNMIRROR DISK130

See also
ADD MIRRORSET
MIRROR
REDUCE
RUN CLONE
SET mirrorset-name

Glossary

HSZ40 Array Controller

CLI Reference Manual

G-2

Glossary

adapter
A device that converts the protocol and hardware interface of one bus type into that of
another without changing the functionality of the bus.
allocation class
A numerical value assigned to a controller to identify units across multiple, independent
controllers. (Controllers in a dual-redundant configuration must have the same allocation
class.)
array controller
A hardware/software device that facilitates communications between a host and one or
more devices organized in an array. HS family controllers are examples of array
controllers.
BBR
Bad block replacement. The procedure used to locate a replacement block, mark the bad
block as replaced, and move the data from the bad block to the replacement block.
BBU
Battery backup unit. A StorageWorks SBB option that extends power availability after the
loss of primary ac power or a power supply to protect against the corruption or loss of
data.
block
The smallest data unit addressable on a disk. Also called a sector. In integrated storage
elements, a block contains 512 bytes of data, EDC, ECC, flags, and the block's address
header.
CDU
Cable distribution unit. The power entry device for StorageWorks cabinets. The unit
provides the connections necessary to distribute ac power to cabinet shelves and fans.
CI bus
Computer interconnect bus. Uses two serial paths, each with a transfer rate of 70 Mb/s
(8.75 MB/s).
CLI
Command line interpreter. Operator command line interface for the HS family controller
firmware.
CLI Reference Manual

HSZ40 Array Controller

Glossary

G-3

controller shelf
A StorageWorks shelf designed to contain controller and cache memory modules.
CRC
An 8-character cyclic redundancy check string used in conjunction with the customer
identification string for turning on licensed features such as write-back caching.
data center cabinet
A generic reference to the large cabinets, such as the SW800-series, in which
StorageWorks components can be mounted.
DDL
Dual data link. The ability to operate on the CI bus using both paths simultaneously to the
same remote node.
differential SCSI bus
A signal's level is determined by the potential difference between two wires. A differential
bus is more robust and less subject to electrical noise than is a single-ended bus.
DILX
Disk inline exerciser. Diagnostic firmware used to test the data transfer capabilities of disk
drives in a way that simulates a high level of user activity.
DSA
DIGITAL storage architecture. A set of specifications and interfaces describing standards
for designing mass storage products. DSA defines the functions performed by host
computers, controllers, and disk drives. It also specifies how they interact to accomplish
mass storage management.
DSSI
DIGITAL storage system interconnect. A DIGITAL-specific data bus with an 8-bit data
transfer rate of 4 MB/s.
dual-redundant configuration
Two controllers in one controller shelf providing the ability for one controller to take over
the work of the other controller in the event of a failure of the other controller.

HSZ40 Array Controller

CLI Reference Manual

G-4

Glossary

DUART
Dual universal asynchronous receiver/transmitter. An integrated circuit containing two
serial, asynchronous transceiver circuits.
DUP
Diagnostic and utility protocol. Host application software that allows a host terminal to be
connected to the controller's command line interpreter.
DWZZA
The StorageWorks compatible SCSI bus signal converter.
ECB
External cache battery.
ECC
Error correction code. One or more cyclic redundancy check (CRC) words that allow
detection of a mismatch between transmitted and received data in a communications
system, or between stored and retrieved data in a storage system. The ECC allows for
location and correction of an error in the received/retrieved data. All ECCs have limited
correction power.
EDC
Error detection code. One or more checksum words that allow detection of a mismatch
between transmitted and received data in a communications system, or between stored and
retrieved data in a storage system. The EDC has no data correction capability.
ESD
Electrostatic discharge. The discharge of a potentially harmful static electric voltage as a
result of improper grounding.
failedset
A group of disk drives that have been removed from RAIDsets due to a failure or a manual
removal. Disk drives in the failedset should be considered defective and should be tested,
repaired, and then placed into the spareset.
failover
The process that takes place when one controller in a dual-redundant configuration
assumes the workload of a failed controller.

CLI Reference Manual

HSZ40 Array Controller

Glossary

G-5

flush
The act of writing data from the cache module to the media.
FRU
Field replaceable unit. A hardware component that can be replaced.
FWD SCSI
Fast, wide, differential SCSI. The differential SCSI bus with a 16-bit parallel data path that
yields a transfer rate of up to
20 MB/s.
half-height device
A device that occupies half of a 5.25 inch SBB carrier. Two half-height devices can be
mounted in a 5.25 inch SBB carrier. The first half-height device is normally mounted in
the lower part of the carrier. The second device is normally mounted in the upper part of
the carrier.
HBVS
Host-based volume shadowing. Also known as Phase 2 volume shadowing.
HSOF
Hierarchical storage operating firmware. Software contained on a program card that
provides the logic for the HS array controllers.
HIS
Host interconnect services. The firmware in the HS array controller that communicates
with the host.
host
Any computer to which a storage subsystem can be attached.
hot swap
A method of replacing a device whereby the system that contains the device remains
online and active during replacement. The device being replaced is the only device that
cannot perform operations during a hot swap.
initiator
A SCSI device that requests an I/O process to be performed by another SCSI device (a
target). This is always the controller.
HSZ40 Array Controller

CLI Reference Manual

G-6

Glossary

local terminal
A terminal plugged into the EIA-423 maintenance port on the front bezel of the HS array
controller. Also called a maintenance terminal.
logical unit
The physical device or storage unit seen by the host. Often these logical units are spread
across more than one physical device, especially in RAID implementations. This is not a
LUN.
logical unit number
See LUN.
LRU
Least recently used. This is cache terminology for the block replacement policy for the
read cache.
LUN
A logical unit number is a physical or virtual peripheral device addressable through a
target. LUNs use their target's bus connection to communicate on the SCSI bus.
maintenance terminal
Any EIA-423 compatible terminal to be plugged into the HS controller. This terminal is
used to identify the controller, enable host paths, define the configuration, and check
controller status. It is not required for normal operations. It is sometimes referred to as a
local terminal.
metadata
Data written on the physical disk that is not visible to the host/customer that allows the HS
array controller to maintain a high integrity of customer data.
mirrorset
Two or more physical disks configured to present one highly reliable virtual unit to the
host.
MSCP
Mass storage control protocol. The protocol by which blocks of information are transferred
between the host and the controller.

CLI Reference Manual

HSZ40 Array Controller

Glossary

G-7

nonredundant configuration
A single controller configuration. A controller configuration which does not include an
second backup controller permitting failover in the event of a failure.
normal member
A mirrorset member whose entire contents is guaranteed to be the same as all other
NORMAL members. All NORMAL members are exactly equivalent.
normalizing member
A mirrorset member whose contents is the same as all other NORMAL and
NORMALIZING members for data that has been written since the mirrorset was created or
lost cache data was cleared. Data that has never been written may differ among
NORMALIZING members.
NV
Nonvolatile. A term used to describe memory that can retain data during a power loss to
the controller.
partition
A percentage of a storageset or single-disk unit that may be presented to the host as a
storage unit.
partitioning
Device partitioning is the process of dividing up a single large container into a number of
smaller containers.
port
The hardware and software used to connect a host controller to a communication bus, such
as CI, DSSI, or SCSI bus. This term also is used to describe the connection between the
controller and its SCSI storage devices.
PTL
Port-target-LUN. A method of device notation where P designates the controller’s device
port (1-6), T designates the target ID of the device (0-6), and L designates the LUN of the
device (0-7).
qualified device
A device that has been fully tested in an approved StorageWorks configuration, (that is,
shelf, cabinet, power supply, cabling, and so forth) and is in complete compliance with

HSZ40 Array Controller

CLI Reference Manual

G-8

Glossary

country-specific standards (for example, FCC, TUV, and so forth) and with all DIGITAL
standards.
quiesce
To make a bus inactive or dormant. The operator must quiesce SCSI bus operations, for
example, during a device warm swap.
RAID
Redundant array of independent disks. The multiple storage access methods devised for
performance (RAID 0, striping) and/or various cost levels of availability (RAID 1 through
RAID 5).
RAIDset
Three or more physical disks that are configured to present an array of disks as a single
virtual unit to the host.
read cache
The cache used to accelerate read operations by retaining data which has been previously
read, written, or erased, based on a prediction that it will be reread.
replacement policy
The method by which a spare disk is selected to replace a disk that has failed in a
RAIDset.
SBB
StorageWorks building block. A modular carrier plus the individual mechanical and
electromechanical interface required to mount it into a standard StorageWorks shelf. Any
device conforming to shelf mechanical and electrical standards is considered an SBB.
SBB shelf
StorageWorks building block shelf. A StorageWorks shelf, such as the BA350--Sx,
designed to house plug-in SBB modules.
SCS
System communication services. A delivery protocol for packets of information
(commands or data) to or from the host.

CLI Reference Manual

HSZ40 Array Controller

Glossary

G-9

SCSI
Small computer system interface. An ANSI interface defining the physical and electrical
parameters of a parallel I/O bus used to connect initiators to a maximum of seven devices.
The StorageWorks device interface is implemented according to SCSI--2 standard,
allowing the synchronous transfer of 8-bit data at rates of up to 10 MB/s.
SCSI device
A host computer adapter, a peripheral controller, or a storage element that can be attached
to the SCSI bus.
SCSI device ID
The bit-significant representation of the SCSI addressing that refers to one of the signal
lines numbered 0 through 7. Also referred to as a target ID.
SCSI--A cable
A 50-conductor (25 twisted pair cable used for single-ended, SCSI bus connections.
SCSI--P cable
A 68-conductor (34 twisted pair cable used for differential bus connections.
Small Computer System Interface
See SCSI.
spareset
A pool of disk drives used by the controller to replace failed members of a RAIDset.
SPD
Software product description. A document that contains the legal description of a product.
storageset
Any collection of containers, such as stripesets, RAIDsets, the spareset, and the failedset,
that make up a container.
storage unit
The general term that refers to storagesets, single disk units, and all other storage devices
that can be installed in your subsystem and accessed by a host. A storage unit can be any
entity that is capable of storing data, whether it is a physical device or a group of physical
devices.

HSZ40 Array Controller

CLI Reference Manual

G-10

Glossary

StorageWorks
DIGITAL's family of modular data storage products that allows customers to design and
configure their own storage subsystems. Components include power, packaging, cabling,
devices, controllers, and software. Customers can integrate devices and array controllers in
StorageWorks enclosure to form storage subsystems.
StorageWorks building block
See SBB.
stripeset
A virtual disk drive with its physical data spread across multiple physical disks. Stripeset
configurations do not include a data recovery mechanism.
striped mirrorset
Stripesets whose members have been mirrored.
tagged command queuing
A SCSI feature that allows a device to have multiple I/O requests outstanding to it at one
time.
target
A SCSI device that performs an operation requested by an initiator. The target number is
determined by the device's address on its SCSI bus.
TILX
Tape inline exerciser. Diagnostic firmware used to test the data transfer capabilities of tape
drives in a way that simulates a high level of user activity.
TMSCP
Tape mass storage control protocol. The protocol by which blocks of information are
transferred between the host and the controller.
unit
The host's view of a container on an HS array controller. A unit may be made up of simply
a physical disk or tape drive, or a more complex container such as a RAIDset.
unwritten cached data
Data in the write-back cache which has not yet been written to the physical device, but the
user has been notified that the data has been written.
CLI Reference Manual

HSZ40 Array Controller

Glossary

G-11

VCS
VAXcluster console system.
virtual terminal
A software path from an operator terminal on the host to the controller's CLI. The path can
be established via the host port on the controller (using DUP) or via the maintenance port
through on intermediary host (VCS). A virtual terminal is also sometimes called a host
console.
warm swap
A method for adding or replacing a device whereby the system remains online, but all
activity on the device’s bus must be halted for the duration of the swap.
write-back caching
A caching strategy that writes data to the cache memory, then flushes the data to the
intended device at some future time. From the user’s perspective, the write operation is
complete when the data is stored in the cache memory. This strategy avoids unnecessary
access of the devices.
write hole
Undetectable RAID level 1 or 5 data corruption. A write hole is caused by the successful
writing of some, but not all, of the storageset members. Write holes occur under conditions
such as power outages, where the writing of multiple members can be abruptly interrupted.
A battery backed-up cache design eliminates the write hole, because data is preserved and
writes can be retried.
write-through cache
A cache write strategy in which the destination of the write data is the primary storage
media. This operation may update, invalidate, or delete data from the cache memory
accordingly, to ensure that the cache does not contain obsolete data. The user sees the
operation as complete only after the backup storage device has been updated.

HSZ40 Array Controller

CLI Reference Manual

Index
A

ADD CDROM command, 2–2
ADD DISK command, 2–3
ADD MIRRORSET command, 2–5
ADD PASSTHROUGH command, 2–8
ADD RAIDSET command, 2–10
ADD SPARESET command, 2–13
ADD STRIPESET command, 2–14
ADD UNIT command, 2–16
Adding
CD-ROM drive, 2–2
disk drive, 2–3
HSZ tape drive, 2–8
HSZ tape loader, 2–8
mirrorset, 2–5
passthrough container, 2–8
RAIDset, 2–10
striped mirrorset, 2–14
stripeset, 2–14
unit, 2–16
AUTOMATIC SPARE POLICY, 2–58

Cables
SCSI bus cable lengths, 2–74
Cache
clearing invalid cache errors, 2–23
enabling/disabling read cache, 2–18, 2–79
enabling/disabling write-back cache, 2–19, 2–
80
flush timer, 2–71
setting maximum transfer size, 2–17, 2–79
CD-ROM
adding to controller, 2–2
deleting, 2–30
displaying information, 2–83
showing, 2–83
Chunksize, 2–39
CLEAR_ERRORS CLI command, 2–22
CLEAR_ERRORS INVALID_CACHE command,
2–23
CLEAR_ERRORS LOST_DATA command, 2–25
CLEAR_ERRORS UNKNOWN command, 2–26
CLEAR_ERRORS UNWRITEABLE_DATA
command, 2–27
CLI
abbreviating commands, 1–4
accessing, 1–3
capturing your session, 1–4

B
Battery policy, 2–71

HSZ40 Array Controller

CLI Reference Manual

I-2

clearing error messages, 2–22
command rules, 1–4
definition, 1–2
editing keys, 1–4
exiting, 1–3, 2–37
help, 2–38
overview, 1–2
printing the session log file, 1–4
specifying a prompt, 2–74
type ahead, 1–4
Command disk. See Passthrough container
Command line interpreter. See CLI
Commands
abbreviating, 1–4
ADD CDROM, 2–2
ADD DISK, 2–3
ADD MIRRORSET, 2–5
ADD PASSTHROUGH, 2–8
ADD RAIDSET, 2–10
ADD SPARESET, 2–13
ADD STRIPESET, 2–14
ADD UNIT, 2–16
CLEAR_ERRORS CLI, 2–22
CLEAR_ERRORS INVALID_CACHE, 2–23
CLEAR_ERRORS LOST_DATA, 2–25
CLEAR_ERRORS UNKNOWN, 2–26
CLEAR_ERRORS UNWRITEABLE_DATA,
2–27
CREATE_PARTITION, 2–28
DELETE container-name, 2–30
DELETE device-name, 2–31
DELETE FAILEDSET, 2–32
DELETE SPARESET, 2–33
DELETE unit-number, 2–34
DESTROY_PARTITION, 2–35
DIRECTORY, 2–36
EXIT, 2–37
HELP, 2–38
INITIALIZE, 2–39
LOCATE, 2–42
MIRROR, 2–44
REDUCE, 2–47
RENAME, 2–49
RESTART OTHER_CONTROLLER, 2–50
RESTART THIS_CONTROLLER, 2–50
RETRY_ERRORS, 2–52

CLI Reference Manual

Index

RUN, 2–53
SELFTEST, 2–54
SET device-name, 2–56
SET FAILEDSET, 2–58
SET FAILOVER, 2–59
SET mirrorset-name, 2–61
SET MULTIBUS_FAILOVER, 2–65
SET NOFAILOVER, 2–68
SET OTHER_CONTROLLER, 2–70
SET RAIDset-name, 2–76
SET THIS_CONTROLLER, 2–70
SET unit number, 2–78
SHOW, 2–83
SHUTDOWN OTHER_CONTROLLER, 2–87
SHUTDOWN THIS_CONTROLLER, 2–87
UNMIRROR, 2–89
Commands:syntax, 1–6
Configuration
restoring, 2–40
saving on devices, 2–40
Configuring
dual-redundant controllers, 1–3
initial controller configuration, 1–3
modifying controller configurations, 1–2
when to use a local connection, 1–3
when to use a remote connection, 1–3
Connection
local, 1–3
remote, 1–3
Controller
displaying information, 2–83
dual-redundant configuration, 1–3
initial configuration, 1–3
showing, 2–83
showing attached devices, 2–83
shutting down, 2–87
CREATE_PARTITION command, 2–28
Creating
host-addressable unit, 2–16
passthrough container, 2–8
RAIDsets, 2–10
single-disk unit, 2–21
striped mirrorset, 2–14
stripeset, 2–14
unit, 2–16

HSZ40 Array Controller

Index

D
DELETE container-name command, 2–30
DELETE device-name command, 2–31
DELETE FAILEDSET command, 2–32
DELETE SPARESET command, 2–33
DELETE unit-number command, 2–34
Deleting
CD-ROM, 2–30
mirrorset, 2–30
optical disk drive, 2–30
RAIDset, 2–30
storagesets and devices, 2–30
stripeset, 2–30
tape drive, 2–30
tape loader, 2–30
unit, 2–34
Deleting Devices
deleting from the configuration, 2–31
DESTROY_PARTITION command, 2–35
Device data transfer rate
setting, 2–56
Diagnostics
list of, 2–36
starting, 1–2, 2–53
DIRECTORY command, 2–36
Disk drive
adding to a RAIDset, 2–10
adding to a reduced RAIDset, 2–77
adding to a spareset, 2–13
adding to a stripeset, 2–14
adding to configuration, 2–3
deleting, 2–30
displaying information, 2–83
initializing, 2–39
making transportable, 2–56
mirroring, 2–44
moving to non-«Brand» environments, 2–3,
2–56
moving with data intact, 2–3, 2–56
removing from a failedset, 2–32
removing from a mirrorset, 2–47, 2–61
removing from a RAIDset, 2–77
removing from a spareset, 2–33
renaming, 2–49
showing, 2–83

HSZ40 Array Controller

I-3

Dual-redundant configuration, 1–3
disabling, 2–68
enabling, 2–59
DUP connection, 1–3

E
Error messages
clearing from CLI, 2–22
clearing invalid cache, 2–23
clearing lost data, 2–25
clearing unknown errors, 2–26
clearing unwriteable data errors, 2–27
EXIT command, 2–37

F
Failedset
changing the automatic spare policy, 2–58
deleting members, 2–32
displaying members, 2–84
Failover
and preferred path, 2–18, 2–79
disabling, 2–68
enabling, 2–59
Finding devices and storagesets, 2–42

H
HELP command, 2–38
Host compatibility mode, 2–72
Host data transfer rate
setting, 2–74
Hot spare, 2–58
Hot standby controller, 2–73
HSZterm. See Remote connection

I
IBM host mode, 2–72
Initialize
before adding unit, 2–16
save user data, 2–40
INITIALIZE command, 2–39
Invalid cache error
clearing, 2–23

CLI Reference Manual

I-4

Index

List

normal mirrorset member
defined, 2–5, 2–44, 2–63

diagnostics and utilities, 2–36
Load balancing
HSZ controllers, 2–73
Local connection, 1–3
LOCATE command, 2–42
Lost data error
clearing, 2–25

M
Maintenance terminal. See Local connection
Metadata
defined, 2–3, 2–57
MIRROR command, 2–44
Mirrorset
actual number of members, 2–47
adding members, 2–61
adding to controller, 2–5
as a member of a stripeset, 2–14
changing mirrorset name, 2–61
choosing a replacement member, 2–6, 2–45
converting back to a single device, 2–89
copying data to new members, 2–5, 2–45, 2–
63
creating from a single disk, 2–44
deleting, 2–30
displaying information, 2–83
enabling write-back cache, 2–19, 2–80
initializing, 2–39
nominal number of members, 2–47
normal member defined, 2–5, 2–44, 2–63
preventing replacement of failed drive, 2–45
removing members, 2–47, 2–61
renaming, 2–49
setting a replacement policy, 2–6
setting the actual number of members, 2–5
setting the copying speed, 2–5, 2–45, 2–63
setting the read source, 2–6, 2–63
showing, 2–83
striping, 2–14
unmirror, 2–89
Moving
disk drives, 2–3, 2–56

CLI Reference Manual

O
Optical disk drive
deleting, 2–30
displaying information, 2–83
showing, 2–83
OTHER_CONTROLLER
CHANGING PARAMETERS, 2–70
DEFINED, 1–2
displaying information, 2–83
REMOVING FROM DUAL-REDUNDANT
CONFIGURATION, 2–68
SELF-TEST, 2–54

P
Partition
adding as a unit, 2–16
creating, 2–28
deleting unit, 2–34
destroying, 2–35
displaying size, 2–83
setting size, 2–28
showing, 2–83
Passthrough container
creating for HSZ controllers, 2–8
deleting, 2–30
renaming, 2–49
showing, 2–83
Preferred path
in dual-redundant configurations, 2–18, 2–79
Preferred SCSI target IDs
setting, 2–73

R
RAIDset
adding a member when reduced, 2–77
adding while missing a member, 2–11
changing characteristics, 2–76
choosing a replacement member, 2–10
creating, 2–10
deleting, 2–30
HSZ40 Array Controller

Index

displaying information, 2–83
enabling write-back cache, 2–19, 2–80
initializing, 2–39
number of members, 2–10
preventing replacement of failed member, 2–
10, 2–76
removing a member, 2–77
renaming, 2–49
setting speed for reconstruct, 2–10, 2–76
showing, 2–83
specifying chunksize, 2–39
specifying replacement policy, 2–76
Read cache
enabling and disabling, 2–18, 2–79
REDUCE command, 2–47
Remote connection, 1–3
Removing. See also Deleting
mirrorset member, 2–47
RENAME command, 2–49
RESTART OTHER_CONTROLLER command, 2–
50
RESTART THIS_CONTROLLER command, 2–50
Restoring
initial controller configuration, 2–73
RETRY_ERRORS command, 2–52
RUN command, 2–53

S
SCSI bus cable lengths, 2–74
SCSI target IDs
preferring, 2–73
setting, 2–72
SELFTEST command, 2–54
SELFTEST CONTROLLER
command:switches:IGNORE_ERRORS, 2–50,
2–54, 2–87
SELFTEST CONTROLLER
command:switches:IMMEDIATE_SHUTDOWN
, 2–51, 2–55, 2–88
SET device-name command, 2–56
SET FAILEDSET command, 2–58
SET FAILOVER command, 2–59
SET mirrorset-name command, 2–61
SET MULTIBUS_FAILOVER command, 2–65
SET NOFAILOVER command, 2–68
SET OTHER_CONTROLLER command, 2–70
HSZ40 Array Controller

I-5

SET RAIDset-name command, 2–76
SET THIS_CONTROLLER command, 2–70
SET unit-number command, 2–78
Setting
controller preferred SCSI target IDs, 2–73
controller SCSI target IDs, 2–72
device data transfer rate, 2–56
Host data transfer rate, 2–74
maximum cached transfer size, 2–17, 2–79
transportability, 2–56
Setting:controller behavior selftest, 2–51, 2–55,
2–88
Setting:controller error handling at selftest, 2–50,
2–54, 2–87
SHOW command, 2–83
SHUTDOWN OTHER_CONTROLLER command,
2–87
SHUTDOWN THIS_CONTROLLER command,
2–87
Spareset
adding a disk drive, 2–13
definition, 2–33
displaying members, 2–84
removing a disk drive, 2–33
Starting
CLI session, 1–3
Storageset
displaying configured sets, 2–84
displaying information, 2–83
initializing, 2–39
renaming, 2–49
showing, 2–83
Striped mirrorset
creating, 2–14
Stripeset
creating, 2–14
deleting, 2–30
displaying information, 2–83
initializing, 2–39
mirroring, 2–44
renaming, 2–49
showing, 2–83
specifying chunksize, 2–39

T
Tape drive
CLI Reference Manual

I-6

Index

adding to an HSZ configuration, 2–8
deleting, 2–30
displaying information, 2–83
renaming, 2–49
showing, 2–83
Tape loader
adding to an HSZ configuration, 2–8
deleting, 2–30
displaying information, 2–83
showing, 2–83
Terminal
setting parity, 2–74
setting speed, 2–74
Testing
controllers, 2–54
THIS_CONTROLLER
CHANGING PARAMETERS, 2–70
DEFINED, 1–2
displaying information, 2–83
REMOVING FROM DUAL-REDUNDANT
CONFIGURATION, 2–68
SELF-TEST, 2–54
SETTING TO INITIAL CONFIGURATION, 2–73
starting diagnostic or utility programs, 2–53
Time
setting on controllers, 2–74

displaying information, 2–83
enabling/disabling host availability, 2–18, 2–
80
enabling/disabling read cache, 2–18, 2–79
enabling/disabling write-back cache, 2–19, 2–
80
mirroring, 2–44
numbering, 2–16
setting write protection, 2–19, 2–80
showing, 2–83
specifying a preferred path, 2–18, 2–79
Unknown error
clearing, 2–26
UNMIRROR command, 2–89
Unwriteable data error
clearing, 2–27
retrying, 2–52
UPS
setting cache policy, 2–71
Utilities
list of, 2–36
starting, 1–2, 2–53

V
Virtual terminal. See Remote connection

U
Unit
adding, 2–16
changing characteristics, 2–78
clearing lost data error, 2–25
deleting from the configuration, 2–34
displaying configured units, 2–84

CLI Reference Manual

Windows NT host mode, 2–72
Write protection, 2–19, 2–80
Write-back cache
enabling/disabling, 2–19, 2–80
setting the battery policy, 2–71
setting the flush timer, 2–71

HSZ40 Array Controller