Digital PDFs

EK-CLI70-RM-A01

July 1997

170 pages

Original

0.7MB

Document:	DIGITAL StorageWorks HSZ70 Array Controller HSOF Version 7.0 CLI Reference Manual
Order Number:	EK-CLI70-RM
Revision:	A01
Pages:	170
Original Filename:

OCR Text

DIGITAL StorageWorks
HSZ70 Array Controller
HSOF Version 7.0
EK–CLI70–RM. A01
Digital Equipment Corporation
Maynard, Massachusetts

CLI Reference Manual

July 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.
DIGITAL, DIGITAL UNIX, DECconnect, HSZ, StorageWorks, VMS, OpenVMS, and the DIGITAL logo are
trademarks of Digital Equipment Corporation.
UNIX is a registered trademark in the United States and other countries exclusively through X/Open Company Ltd.
Windows NT is a trademark of the Microsoft Corporation. Sun is a registered trademark of Sun Microsystems, Inc.
Hewlett-Packard and HP–UX are registered trademarks of the Hewlett-Packard Company. IBM and AIX are
registered trademarks of International Business Machines Corporation. All other trademarks and registered
trademarks are the property of their respective owners.
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 manuals, 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

Contents

Preface
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Electrostatic Discharge Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
VHDCI Cable Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Local-Connection Port Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
CLI Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Command Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Entering CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Unit Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
ADD CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
ADD DISK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
ADD MIRRORSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
ADD PASSTHROUGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
ADD RAIDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
ADD SPARESET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
ADD STRIPESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
ADD UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
CLEAR_ERRORS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
CLEAR_ERRORS UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
CREATE_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
DELETE FAILEDSET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
DELETE SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

CLI Reference Manual

DESTROY_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
REDUCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
RETRY_ERRORS UNWRITEABLE_DATA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
RUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
SET EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
SET FAILEDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
SET FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
SET MULTIBUS_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SET NOFAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
UNMIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Glossary
Index

Tables

Recall and Edit Command Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Unit Numbering Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
ADD UNIT Switches for New Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
SET controller Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Maximum SCSI-Bus Cable Lengths for Given Data Transfer Rate . . . . . . . . . . . .91
EMU Set Point Temperatures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
SET UNIT Switches for Existing Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

vii

Preface

This book provides information and guidance for operating the command line
interface (CLI) for the array controller. This book defines, explains, and presents
examples of how you can implement the commands supported by the software
accompanying your controller.
This book does not contain information about the operating environments to which
the controller may be connected, nor does it contain detailed information about
subsystem enclosures or their components. See the documentation that
accompanied these peripherals for information about them.

viii

CLI Reference Manual

Precautions
Follow these precautions when you’re carrying out the procedures in
this book.

Electrostatic Discharge Precautions
Static electricity collects on all nonconducting material, such as paper,
cloth, and plastic. An electrostatic discharge (ESD) can easily damage
a controller or other subsystem component even though you may not
see or feel the discharge. Follow these precautions whenever you’re
servicing a subsystem or one of its components:

Always use an ESD wrist strap when servicing the controller or
other components in the subsystem. Make sure that the strap
contacts bare skin and fits snugly, and that its grounding lead is
attached to a bus that is a verified earth ground.
Before touching any circuit board or component, always touch a
verifiable earth ground to discharge any static electricity that may
be present in your clothing.
Always keep circuit boards and components away from
nonconducting material.
Always keep clothing away from circuit boards and components.
Always use antistatic bags and grounding mats for storing circuit
boards or components during replacement procedures.
Always keep the ESD cover over the program card when the card is
in the controller. If you remove the card, put it in its original
carrying case. Never touch the contacts or twist or bend the card
while you’re handling it.
Do not touch the connector pins of a cable when it is attached to a
component or host.

Preface

VHDCI Cable Precautions
All of the cables to the controller, cache module, and external cache
battery use very-high-density cable interconnect connectors (VHDCI).
These connectors have extraordinarily small mating surfaces that can
be adversely affected by dust and movement.
Use the following precautions when you’re connecting cables that use
VHDCI connectors:

Clean the mating surfaces with a blast of clean air.
Mate the connectors by hand, then tighten the retaining screws to
1.5 inch-pounds—approximately 1/4 additional turn after the
connectors have fully mated.
Test the assembly by gently pulling on the cable, which should not
produce visible separation.

Local-Connection Port Precautions
The local-connection port generates, uses, and radiates radio-frequency
energy through cables that are connected to it. This energy may
interfere with radio and television reception. Do not leave a cable
connected to this port when you’re not communicating with the
controller.

CLI Reference Manual

Conventions
This book uses the following typographical conventions and special
notices to help you find what you’re looking for.

Typographical Conventions
Convention
ALLCAPS BOLD

Meaning
Command syntax that must be entered exactly as
shown, for example:
SET FAILOVER COPY=OTHER_CONTROLLER

ALLCAPS

Monospaced

Command discussed within text, for example:
“Use the SHOW SPARESET command to show the
contents of the spareset.”
Screen display.

Sans serif italic Command variable or numeric value that you
supply, for example: SHOW RAIDset-name or
SET THIS_CONTROLLER ID= (n,n,n,n,)
italic

..
.

Reference to other books, for example: “See HSZ70
Array Controller HSOF Version 7.0 Configuration
Manual for details.”
Indicates that a portion of an example or figure has
been omitted, for example:
ADD RAIDSET RAID1 DISK10000 DISK20000
INITIALIZE RAID1
.
.
.
SHOW RAID1

“this controller” The controller serving your current CLI session
through a local or remote terminal.
“other controller” The controller in a dual-redundant pair that’s
connected to the controller serving your current
CLI session.

Preface

Special Notices
This book doesn’t contain detailed descriptions of standard safety
procedures. However, it does contain warnings for procedures that
could cause personal injury and cautions for procedures that could
damage the controller or its related components. Look for these
symbols when you’re carrying out the procedures in this book:
Warning A warning indicates the presence of a hazard that can cause
personal injury if you do not avoid the hazard.

Caution A caution indicates the presence of a hazard that might
damage hardware, corrupt software, or cause a loss of data.

Tip A tip provides alternative methods or procedures that may not be
immediately obvious. A tip may also alert prior customers that the
controller’s behavior being discussed is different from prior software
or hardware versions.

Note A note provides additional information that’s important to the
completion of an instruction or procedure.

xii

CLI Reference Manual

Related Publications
The following table lists some of the documents related to the use of
the controller, cache module, and external cache battery.
Document Title

Part Number

HSZ70 Array Controller HSOF Version 7.0
CLI Reference Manual

EK–CLI70–RM. A01

HSZ70 Array Controller HSOF Version 7.0
Configuration Manual

EK–HSZ70–CG. A01

HSZ70 Array Controller HSOF Version 7.0
Service Manual

EK–HSZ70–SV. A01

HSZ70 Family Array Controller Operating
Software (HSOF) Version 7.0 Software
Product Description

SPD xx.xx. 00

Getting Started–HSZ70 Solutions Software
Version 7.0 for...platform

AA–R60xx–TE. A01

Polycenter Console Manager

See the Getting
Started guide for the
platform-specific
order number

StorageWorks Array Controller HSZ70 Array
Controller Operating Software HSOF Version
7.0 Release Notes

EK–HSZ70–RN. A01

StorageWorks Getting Started with Command AA–R0HJC–TE
Console, Version 2.0
DIGITAL StorageWorks Ultra SCSI RAID
Cabinet Subsystem (SW600) Installation and
User’s Guide

EK–SW600–UG

DIGITAL StorageWorks Ultra SCSI RAID
Enclosure (BA370-Series) User’s Guide

EK–BA370–UG

The RAIDBOOK—A Source for RAID
Technology

RAID Advisory
Board

Preface

Revision History
This is a new document.

xiii

CLI Overview

CLI Overview
The command line interpreter (CLI) is one of the user interfaces
through which you control your StorageWorks array controller in the
StorageWorks subsystem. The CLI commands allow you to manage
the subsystem by viewing and modifying the configuration of the
controller and the devices attached to them. You can also use the CLI
to start controller diagnostic and utility programs.
While the CLI provides the most detailed level of subsystem control, a
graphical user interface (GUI) is available for use with the CLI. The
GUI, named StorageWorks Command Console, replicates most of the
functions available within the CLI in graphic form and provides a very
user-friendly method of executing CLI commands.
CLI commands for configuring and viewing the controllers in a dualredundant configuration use the relative terms “this controller” and
“other controller.” See “Typographical Conventions,” page x, for an
explanation of these terms.

Using the CLI
You can access the CLI by connecting a maintenance terminal to the
port in the front bezel of the controller (local connection) or by using
HSZterm software (remote connection). See the HSZ70 Array
Controller HSOF Version 7.0 Configuration Manual for instructions
explaining how to connect a local terminal to the controller. After you
have initially configured the controller, making it visible to the host,
you can perform all other configuration tasks through a remote
connection.
The section entitled “Local-Connection Port Precautions,” page ix,
explains precautions you should observe when operating the CLI
through a local connection port.

Command Overview
The CLI consists of six basic command types:

Controller Commands—Enable you to configure the controller’s
SCSI ID numbers, maintenance terminal characteristics, CLI
prompt, and so forth. Controller commands are also used to shut
down and restart the controller.

CLI Reference Manual

Device Commands—Enable you to create and configure containers
made from physical devices attached to the controller.
Storageset Commands—Enable you to create and configure
complex containers made from groups of device containers. There
are four basic types of storagesets: stripesets, RAIDsets, stripedmirrorsets, and mirrorsets. Storageset commands group device
containers together and allow them to be handled as single units.
Logical Unit Commands—Enable you to create and optimize
access to logical units made from any container type.
Failover Commands—Enable you to configure the controllers to
operate in transparent or mulle bus failover while also providing
support for dual-redundant configurations.
Diagnostic and Utility Commands—Enable you to perform general
controller support functions

Getting Help
Help on using the CLI is at your fingertips. For an overview of the CLI
help system, enter “help” at the prompt. For help on a specific
command or to determine what switches are available with a
command, enter as much of the command as you know followed by a
space and a question mark. For example, to get information on the
switches used with the SET THIS_CONTROLLER command, enter:
SET THIS_CONTROLLER ?

See the HELP command on page -57 for further information.

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

Commands are not case sensitive.
For most commands, you only need to enter enough of the
command to make the command unique (usually three characters).
For example, SHO is the same as entering SHOW.
The controller processes each command in sequence. You may
continue entering subsequent commands while the controller is
processing prior commands. A device experiencing heavy data
input and output (I/O) may respond slowly to CLI commands.

CLI Overview

Note Due to space limitations the length, some examples in this
manual contain commands which exceed one line in length. In such
instances, the paragraph proceeding the example will identify which
command is continued on the next line.
Specific keys or a combination of keys allow you to recall and edit the
last four commands. This feature can save time and help prevent
mistakes when you need to enter similar commands during the
configuration process. Table 1 lists the keys used to recall and edit
commands.

CLI Reference Manual

Table 1

Recall and Edit Command Keys

Key

Function

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

Steps backward and forward through the
four 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 all characters on the same line as 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. 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 interrupting your typing.

Unit Naming
The host operating system identifies the location of units based on a
logical unit numbering (LUN) scheme.
Each unit number contains the following:

The first character is a letter indicating the kind of device in the
storage unit: use D for disk devices (including CD-ROMs) or P to
indicate passthrough devices such as tape devices, loaders, and
libraries.

Note A device letter is automatically supplied when you use the
CFMENU utility to configure your storagesets and devices.

CLI Overview

If entered, the next one or two digits indicate which target ID
number is to access the unit during normal operation. Use one of
the controller’s SCSI target ID numbers assigned to the controller
with the SET controller ID= command. Omit leading zeroes for
SCSI target ID numbers less than ten. For example, use 2 instead of
02 for a storageset being accessed through the controller SCSI
target ID number 0, LUN 2. The SCSI target ID number is initially
set with the SET THIS_CONTROLLER ID= or SET
OTHER_CONTROLLER ID= command. See page -83 for an
explanation of these commands.
By carefully choosing the SCSI target ID number when adding
units, the preferred paths for all of your storage units in a dualredundant configuration can be established. Data I/O load to the
units can likewise be controlled by equally distributing unit access
between the controllers.
If the target ID number is not entered, the unit is still brought online
by whatever target ID number is specified in the ADD UNIT
command.

Note When operating in multiple bus failover mode, settings specified
with the PREFERRED_ID= switch takes priority over settings
assigned with the SET controller ID= switch.

The digit following the SCSI target ID number is always zero.
The last digit identifies the logical unit number (LUN) for the
device or storage unit. Acceptable LUN numbers are 0 through 7.

CLI Reference Manual

Table 2

Unit Numbering Examples

Unit Number

Device Type

Target ID Number

LUN

D1207

disk

D401

disk

D30
D5

(not an acceptable unit number)
disk

When a container is partitioned, assign all partitions to the same
controller target ID number.
Note The host communicates with a logical unit based on its LUN
address. The controller communicates with a device based on its PTL
address.

Command Syntax
Commands to the controller must use the following command structure:
Command Parameter Switches

Command. A word or phrase expressed as a verb used to instruct
the controller what to do. Every CLI command begins with a
command. Commands are represented in this manual in capitalized
form.
Parameter. When required in the command, one or more a words
or phrases entered to supply necessary information to support the
action of the command. Not all CLI commands require parameters.
Parameters are represented in this manual in capitalized form.
Switches. An optional word or phrase which modifies the
command. Not all CLI commands require switches. Switches are
represented in this manual as capitalized, italicized text.

ADD CDROM

ADD CDROM
Names a CD-ROM device and adds it to the controller configuration.

Syntax
ADD CDROM container-name SCSI-port-location

Parameters
container-name
Assigns a name to the CD-ROM device. This is the same name used
with the ADD UNIT command to create a single-disk unit.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
SCSI-port-location
Indicates the PTL address of the CD-ROM used by the controller. See
the HSZ70 Array Controller HSOF Version 7.0 Configuration Manual
for an explanation of the PTL addressing naming format.
Note See the HSZ70 Array Controller HSOF Operating Software
Version 7.0 Release Notes to confirm the compact disc device you are
planning to use is compatible with the controller.

Example
This example shows how to add a CD-ROM device named
CD_PLAYER located at port 1, target 8, LUN 0:
ADD CDROM CD_PLAYER 1 8 0

See also
ADD UNIT
DELETE container-name
SHOW CDROM
SHOW DEVICES

ADD DISK

ADD DISK
Names a disk drive and adds it to the controller’s configuration.

Syntax
ADD DISK container-name SCSI-port-location

Parameters
container-name
Assigns a name to the disk device. This is the same name used with the
ADD UNIT command to create a single-disk unit.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a disk drive DISKptl, where ptl is the
disk’s Port-Target-LUN address. Although other naming conventions
are certainly acceptable, this naming convention offers the advantage
of presenting to the user both the type of disk drive and its SCSI
location in an intuitive manner.
SCSI-port-location
Indicates the PTL address of the disk device. See the HSZ70 Array
Controller HSOF Version 7.0 Configuration Manual for an
explanation of the PTL addressing naming format.
Note See the HSZ70 Array Controller HSOF Operating Software
Version 7.0 Release Notes to confirm the disk drive you are planning
to use is compatible with the controller.

Switches
NOTRANSPORTABLE (Default)
TRANSPORTABLE
Indicates whether a disk drive can be accessed exclusively by
StorageWorks controllers.

CLI Reference Manual

If the NOTRANSPORTABLE switch is specified, the controller makes
a small portion of a non-transportable disk inaccessible to the host.
This restricted space is used to store information (metadata) used to
improve data reliability, error detection, and the ability to recover data.
Because of this metadata, only StorageWorks controllers can retrieve
data from non-transportable devices. Disks used as storagesets cannot be
set as being transportable.
Transportable disk drives do not contain any metadata or restricted
areas on them. Therefore, transportable disks forfeit the advantage
metadata provides. However, transportable disks can be moved to a
non-StorageWorks environment with their data intact.
If the NOTRANSPORTABLE switch is specified and there is no
metadata on the unit, the unit must be initialized.
Note DIGITAL recommends you avoid making a disk transportable
unless it is imperative and there is no other way to accomplish moving
the data.
TRANSFER_RATE_REQUESTED=ASYNCHRONOUS
TRANSFER_RATE_REQUESTED=20MHZ (Default)
TRANSFER_RATE_REQUESTED=10MHZ
TRANSFER_RATE_REQUESTED=5MHZ
Specifies the maximum data transfer rate at which the controller is to
communicate with the disk drive. The transfer rate may need to be
limited to accommodate long cables between the controllers and the
device, such as with a tape library.

Examples
This example shows how to add DISK10000 at port 1, target 0, LUN 0:
ADD DISK DISK10000 1 0 0

This example shows how to add DISK40200 as a transportable disk
drive to port 4, target 2, LUN 0.
ADD DISK DISK40200 4 2 0 TRANSPORTABLE

This example shows how to:

ADD DISK

Add a disk drive named DISK30200 as non-transportable device to
port 3, target 2, LUN 0
Set the data transfer rate to 10 MHz.

Enter the following command on one line.
ADD DISK DISK30200 3 2 0 NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED=10MHZ

See also
ADD MIRRORSET
ADD UNIT
DELETE container-name
LOCATE
SHOW DISKS
SHOW DEVICES
SET container-name

ADD MIRRORSET

ADD MIRRORSET
Names a mirrorset and adds it to the controller configuration.

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

Parameters
mirrorset-name
Assigns a name to the mirrorset. This is the same name used with the
ADD UNIT command to identify the mirrorset as a host-addressable
unit.
The mirrorset name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a mirrorset MIRRn, where n is a
sequentially assigned, unique identifier. Other naming conventions are
acceptable, but this naming convention presents both the type of
container and its unique identifier in an intuitive manner.
disk-name1 [disk-nameN
Identifies the disk drives making up the mirrorset. A mirrorset may
contain one to six disk drives.

Switches
COPY=FAST
COPY=NORMAL (Default)
Sets the speed at which the controller copies data from normal
mirrorset members to a new member or members when data is being
mirrored to the storagesets disk drives.
Specify COPY=FAST when you want the creation of mirrored data is
to take priority over other controller operations. When COPY=FAST is
specified, the controller uses more resources to create the mirrored
data. Copying takes less time. However, overall controller performance
is reduced.

CLI Reference Manual

Specify COPY=NORMAL when operations performed by the other
controller should take priority over the copy operation. When
COPY=NORMAL is specified, the controller uses relatively few
resources when creating the mirrored data, resulting in minimal impact
on performance.
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
Sets the selection criteria the controller uses to choose a replacement
member from the spareset when a mirrorset member fails.
Specify POLICY=BEST_FIT to choose a replacement disk drive from
the spareset most closely matching the capacity of the mirrorset. If
there is more than one disk drive in the spareset most closely matching
the capacity of the mirrorset, the controller selects the disk drive
having the best performance.
Specify POLICY=BEST_PERFORMANCE to choose a replacement
disk drive from the spareset having the best performance. The
controller attempts to select a disk on a different port than existing
mirrorset members. If there is more than one disk drive in the spareset
matching the best performance criteria, the controller selects the disk
drive most closely matching the capacity of the mirrorset.
Specify NOPOLICY to prevent the controller from automatically
replacing a failed disk device. The mirrorset operates in a reduced state
until a POLICY=BEST_FIT or POLICY=BEST_PERFORMANCE is
selected, or a member is manually replaced in the mirrorset (see
“SET,” page 103).
READ_SOURCE=disk-name
READ_SOURCE=LEAST_BUSY (Default)
READ_SOURCE=ROUND_ROBIN
Selects the mirrorset member used by the controller to satisfy a read
request.
Specify the READ_SOURCE=disk-name of a specific member to
which you want the controller to direct all read requests. If the member
fails out of the mirrorset, the controller selects the first normal member
it finds to satisfy its read requests.

ADD MIRRORSET

Specify READ_SOURCE=LEAST_BUSY to direct read requests to
the mirrorset member with the least amount of work in its queue.
Specify READ_SOURCE=ROUND_ROBIN to sequentially direct
read requests to each mirrorset member. The controller equally queries
all normal members for each read request.

Examples
This example shows how to add DISK10000, DISK20100, and
DISK30200 as a mirrorset with the name MIRR1:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD MIRRORSET MIRR1 DISK10000 DISK20100 DISK30200

This example creates a host-addressable unit after the mirrorset
MIRR1 has been created:
INITIALIZE MIRR1
ADD UNIT D305 MIRR1

See also
ADD DISK
ADD UNIT
DELETE container-name
INITIALIZE
MIRROR
REDUCE
SHOW mirrorset-name
SHOW MIRRORSETS
SHOW STORAGESETS
UNMIRROR

ADD PASSTHROUGH

ADD PASSTHROUGH
Creates a passthrough container. A passthrough container bypasses
controller processing and allows the host to have direct access to the
device. A passthrough device appears as if it were connected directly
to the host bus rather than to the controller. Use passthrough containers
to communicate with tape devices and tape loaders because they do not
require the controller for optimum operation performance.

Syntax
ADD PASSTHROUGH passthrough-name SCSI-port-location

Parameter
passthrough-name
Names the device being added to or changed in a subsystem
configuration. This is the same name used with the ADD UNIT
command to create a host-addressable unit. You may want to use a
name indicating the type of device is being added as a passthrough
container, such as TAPE or LOADER.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a tape passthrough device TAPEptl, where
ptl is the tape’s Port-Target-LUN address. Although other naming
conventions are acceptable, this naming convention offers the
advantage of presenting to the user both the type of device and its
SCSI location in an intuitive manner.
SCSI-port-location
Indicates the PTL address of the passthrough device. See the HSZ70
Array Controller HSOF Version 7.0 Configuration Manual for an
explanation of the PTL addressing naming format.
Note See the HSZ70 Array Controller HSOF Operating Software
Version 7.0 Release Notes to confirm the passthrough device you are
planning to use is compatible with the controller.

CLI Reference Manual

Example
This example shows how to add tape device TAPE20300 at port 2,
target 3, LUN 0:
ADD PASSTHROUGH TAPE20300 2 3 0
ADD UNIT P100 TAPE20300

See also
ADD UNIT
DELETE container-name
SHOW DEVICES
SHOW PASSTHROUGH
SHOW passthrough-name

ADD RAIDSET

ADD RAIDSET
Names a RAIDset and adds the RAIDset to the controller’s
configuration. DIGITAL RAIDsets are often referred to as RAID level
3/5 storagesets because they use the best characteristics of RAID level
3 and RAID level 5. The number of members in the storageset is
determined by the number of containers specified by the containername parameter in the command. The data capacity of the RAIDset is
determined by the storage size of the smallest member.

Syntax
ADD RAIDSET RAIDset-name container-name1 container-name2
container-name3 [container-nameN]

Parameters
RAIDset-name
Assigns a name to the RAIDset. This name is also used with the ADD
UNIT command to identify the RAIDset as a host-addressable unit.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a RAIDset RAIDn, where n is a
sequentially assigned, unique identifier. This naming convention
presents to the user both the type of container and its unique identifier
in an intuitive manner.
container-name1 container-name2 container-name3 [containernameN]
Specifies the disks making up the RAIDset.

Switches
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
Switches set the selection criteria the controller uses to choose a
replacement member from the spareset when a RAIDset member fails.

CLI Reference Manual

Specify POLICY=BEST_FIT to choose a replacement disk drive from
the spareset most closely matching the sizes of the remaining members
of the RAIDset. If more than one disk drive in the spareset is the
correct size, the controller selects the disk drive giving the best
performance.
Specify POLICY=BEST_PERFORMANCE to choose a replacement
disk drive from the spareset resulting in the best performance of the
RAIDset. The controller attempts to select a disk on a different port
than existing RAIDset members. If there is more than one disk drive in
the spareset matching the best performance criteria, the controller
selects the disk drive most closely matching the size of the remaining
members of the RAIDset selected.
Specify NOPOLICY to prevent the controller from automatically
replacing a failed disk device. This causes the RAIDset to operate in a
reduced state until a POLICY=BEST_FIT or
POLICY=BEST_PERFORMANCE is selected, or a member is
manually replaced in the mirrorset. See the “SET,” page 113, for more
information regarding this procedure.
RECONSTRUCT=FAST
RECONSTRUCT=NORMAL (Default)
Sets the speed at which the controller reconstructs data to a new
RAIDset member replacing a the failed member.
Specify NORMAL to balance other controller operations with the
reconstruct operation. The controller uses relatively few resources to
perform the reconstruct process. Thus, there is little impact on
performance.
Specify FAST to allow the reconstruct process to take precedence over
other controller operations. When the RECONSTRUCT=FAST switch
is specified, the controller uses more resources to perform the
reconstruction. Reconstruction takes less time, but overall controller
performance is reduced during reconstruction.
REDUCED
NOREDUCED (Default)
Switches permit the addition of a RAIDset missing a member. Specify
the REDUCED switch when you add a RAIDset missing a member.
Specify the NOREDUCED switch when all RAIDset members making

ADD RAIDSET

up the RAIDset are present—for instance, when creating a new
RAIDset.
Verify the RAIDset contains at least two disk drives before specifying
the REDUCED switch.

Examples
This example shows how to create a RAIDset named RAID9
containing disks DISK10000, DISK20100, and DISK30200.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID9 DISK10000 DISK20100 DISK30200

This example shows how to create a RAIDset named RAID8
containing disks DISK10000, DISK20100, and DISK30200, and uses
the BEST_FIT switch to indicate the replacement policy. Enter the
ADD RAIDSET command on one line.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID8 DISK10000 DISK20100 DISK30200
POLICY=BEST_FIT

This example creates RAIDset named RAID8, and then creates a hostaddressable unit.
INITIALIZE RAID8
ADD UNIT D304 RAID8
This example shows how you can create a three-member RAIDset
from the members of an already reduced four-member RAIDset. Do
not initialize the RAIDset again because it was initialized when it was
added.
Caution Data contained on the RAIDset is erased if you reinitialize
the RAIDset.
ADD DISK DISK10300 1 3 0
ADD DISK DISK20400 2 4 0
ADD DISK DISK30500 3 5 0
ADD RAIDSET RAID6 DISK10300 DISK20400 DISK30500 REDUCED

CLI Reference Manual

See also
ADD UNIT
DELETE container-name
SET RAIDSET
SHOW RAIDSET
SHOW RAIDset-name
SHOW STORAGESETS
INITITALIZE

ADD SPARESET

ADD SPARESET
Adds a disk drive to the spareset and initializes the metadata on it.

Syntax
ADD SPARESET disk-name

Parameter
disk-name
Indicates the name of the disk drive being added to the spareset. Only
one disk drive can be added to the spareset with each ADD
SPARESET command.

Example
This example shows how to add a disk drive named DISK20200 and
DISK30300 to a spareset:
ADD DISK DISK20200 2 2 0
ADD DISK DISK30300 3 3 0
ADD SPARESET DISK20200
ADD SPARESET DISK30300

See also
DELETE SPARESET
SET FAILEDSET
SHOW SPARESET
SHOW STORAGESETS

ADD STRIPESET

ADD STRIPESET
Names a stripeset and adds it to the controller configuration. Stripesets
sometimes referred to as RAID level 0 storagesets. The number of
members in the stripeset is determined by the number of containername parameters specified. Specified at least two disk drives for
RAIDsets.

Syntax
ADD STRIPESET stripeset-name container-name1 container-name2
[container-nameN]

Parameters
stripeset-name
Assigns a name to the stripeset. This is the same name used with the
ADD UNIT command to identify the stripeset as a host-addressable
unit.
container-name1 container-name2 [container-nameN]
Indicates the name of name of the disk drive being added to or changed
in a subsystem configuration. This is the same name used with the
ADD UNIT command to create a host-addressable unit.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a stripeset STRIPEn, where n is a
sequentially assigned, unique identifier. This naming convention
presents to the user both the type of container and its unique identifier
in an intuitive manner.
container-name1 container-name2 [container-nameN]
Identifies the disk drives or mirrorsets making up the stripeset.

CLI Reference Manual

Examples
This example shows how to create a stripeset named STRIPE1 with
three disks: DISK10000, DISK20100, and DISK30200:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD STRIPESET STRIPE1 DISK10000 DISK20100 DISK30200

This example show how to create a stripeset named STRIPE1 and then
create a logical unit from it:
INITIALIZE STRIPE1
ADD UNIT D403 STRIPE1

This example shows how to create a two-member striped mirrorset (a
stripeset whose members are mirrorsets), and how to create a logical
unit from it. Because you can initialize the stripeset, you do not need to
individually initialize the mirrorsets.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD DISK DISK40300 4 3 0
ADD MIRRORSET MR1 DISK10000 DISK20100
ADD MIRRORSET MR2 DISK30200 DISK40300
ADD STRIPESET STRIPE1 MR1 MR2
INITIALIZE STRIPE1
ADD UNIT D304 STRIPE1

See also
ADD UNIT
ADD MIRRORSET
DELETE container-name
INITIALIZE
SHOW STORAGESET
SHOW STRIPESET
SHOW stripeset-name

ADD UNIT

ADD UNIT
Creates a logical unit from a device, container, or partition. The
controller maps all requests from the host to the logical-unit number as
requests to the container specified in the ADD UNIT command.
Initialize the disk drive or storageset container before adding it as a
logical unit.

Syntax
ADD UNIT unit-number container-name

Parameters
unit-number
Assigns a number to the unit being created from a device, container, or
partition in the subsystem. The host uses this number to indicate the
source or target for every I/O request it sends to the controller. The
unit-number is a host-addressable LUN.
container-name
Specifies the name of the container (that is, disk drive, device,
storageset, or partition) being used to create the unit.
The maximum of 32 devices are allowed in each unit.

CLI Reference Manual

Switches
Table 3 lists all switches for the ADD UNIT command and identifies
which switches may be used with each type of device or storageset.
Descriptions of each switch follow the table.

PARTITION=partition-number

MAXIMUM_CACHED_

PREFERRED_PATH

READ_CACHE

RUN

WRITE_PROTECT

WRITEBACK_CACHE

ADD UNIT Switches for New Containers

ACCESS_ID=ALL

Table 3

RAIDset

✓

Stripeset

✓

Mirrorset

✓

Non-Transportable
Disk

✓

Transportable Disk

✓

CD-ROM

✓

Partition

✓

Container Type

Switch

Passthrough

✓

Note Regardless of the storageset type, the RUN and NORUN
switches cannot be specified for partitioned units.
ACCESS_ID=ALL (Default)
ACCESS_ID=unit identification
Grants exclusive unit access privileges to the host. The access ID
number must be set to the initiator SCSI ID number used by the host to

ADD UNIT

communicate with the controller. When a specific ID number is
assigned, only the initiator’ target ID number specified is permitted to
read from or write to the unit. When set to ALL, any host may access
the unit.
Units added as passthrough LUNs do not accept ACCESS_ID
numbers. The ACCESS_ID switch for passthrough LUNs is set to
ALL by default.
PARTITION=partition_number
Identifies the unit number for a partition on a container. The partitionnumber identifies the partition associated with the unit number being
added. Use the SHOW container-name command to find the partition
numbers used by a storageset or a single-disk unit.
Note Partitions must be have the same target ID number and must be
part of the same container.
MAXIMUM_CACHED_TRANSFER=32 (Default)
MAXIMUM_CACHED_TRANSFER=n
Sets the largest number of write blocks to be cached by the controller.
The controller will not cache any transfers over the set size. Accepted
write block sizes are 1 through 1024.
PREFERRED_PATH=OTHER_CONTROLLER
PREFERRED_PATH=THIS_CONTROLLER
NOPREFERRED_PATH (Default)
May be set only when dual-redundant controllers are operating in a
multiple bus failover configuration. In a multiple bus failover
configuration, the host determines which controller the units are
accessed through. The host’s unit-to-controller settings always take
precedence over the preferred path assigned to units with this switch.
The target ID numbers assigned with the SET controller ID=
command determines which target ID number the controller uses to
respond to the host.
Note If your controller are configured to operate in transparentfailover mode, do not set the PREFERRED_PATH switch with the
ADD UNIT or SET unit-number command—otherwise, an error
message is displayed. The error message indicates the assignment of a
preferred controller path at the unit level is valid only when operating

CLI Reference Manual

in multiple bus failover mode.
When no preferred path is assigned, the unit is targeted through the
controller which detects the unit first after the controllers start.
Select PREFERRED_PATH=THIS_CONTROLLER to instruct “this
controller” to bring the units online.
Select PREFERRED_PATH=OTHER_CONTROLLER to instruct the
“other controller” to bring the units online.
See the HSZ70 Array Controller HSOF Version 7.0 Configuration
Manual for information regarding multiple bus failover.
Tip Subsystem performance is better if target ID numbers are
balanced across the dual-redundant pair.
READ_CACHE (Default)
NOREAD_CACHE
Switches are used to set the controller’s cache read policy function.
Read caching improves performance in almost all situations.
Therefore, it is recommended you leave its default setting
READ_CACHE enabled. However, under certain conditions, such as
when performing a backup, read caching may not be necessary since
only a small amount of data is cached. In such instances, it may be
beneficial to disable the read cache function and remove the processing
overhead associated with caching data.
RUN (Default)
NORUN
Controls the unit's availability to the host.
Specify RUN to make a unit available to the host.
Specify NORUN to make a unit unavailable to the host and to cause
any data in cache to be flushed to one or more drives. NORUN spins
down the devices used in the unit. The drives making up the unit spin
down after the data has been completely flushed.

ADD UNIT

Note Do not specify the RUN and NORUN switches for partitions.
WRITE_PROTECT
NOWRITE_PROTECT (Default)
Instructs the controller whether data contained on the unit can be
overwritten.
Specify WRITE_PROTECT to prevent the host from writing data to
the unit. However, the controller may still write to a write-protected
RAIDset to complete a reconstruct operation. However, metadata,
reconstruct data, and copy data is still written to RAIDsets and
mirrorsets.
Specify NOWRITE_PROTECT to allow the host to write data to the
unit. This allows the controller to overwrite existing data.
WRITEBACK_CACHE
NOWRITEBACK_CACHE (Default)
Enable or disable the write-back data caching function of the
controller. The controller’s write-back caching feature improves write
performance.
Specify WRITEBACK_CACHE for all new units you want to take
advantage of the controller’s write-back caching feature.
Specify NOWRITEBACK_CACHE for units you want to receive data
directly from the host without being cached.
Caution Though there is built-in redundancy to protect data contained
in cache, allowing data to be written to write-back cache may result in
the loss of data if a catastrophic subsystem failure occur.

Examples
This example shows how to create unit D102 from a single-disk drive
named DISK10000 and sets host’s access to the unit through “this
controller”:
ADD DISK DISK10000 1 0 0
INITIALIZE DISK10000
ADD UNIT D102 DISK10000 PREFERRED_PATH=THIS_CONTROLLER

CLI Reference Manual

This example shows how to create unit D107 from a RAIDset named
RAID9 and instructs the unit to take advantage of the controller’s writeback caching feature.
ADD DISK DISK10100 1 1 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30100 3 1 0
ADD DISK DISK40100 4 1 0
ADD RAIDSET RAID9 DISK10100 DISK20100 DISK30100 DISK40100
INITIALIZE RAID9
ADD UNIT D107 RAID9 WRITEBACK_CACHE

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

CLEAR_ERRORS CLI

CLEAR_ERRORS CLI
Stops the display of current or previous error messages at the CLI
prompt. This command does not clear the error conditions, it only
stops the display of errors at the CLI prompt.
After the cause of the error condition has been corrected, issue the
CLEAR_ERRORS CLI command to clear the error message.
Enter this command to clear errors existing from previous error
conditions.

Syntax
CLEAR_ERRORS CLI

Example
This example shows how to clear the message “All NVPM components
initialized to their default settings” from the CLI prompt:
ALL NVPM COMPONENTS INITIALIZED TO THEIR DEFAULT SETTINGS
CLEAR_ERRORS CLI

See also
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS controller INVALID_CACHE

CLEAR_ERRORS controller INVALID_CACHE
Clears an invalid cache error and allows the controller and cache to
resume operation. If the error is due to an incorrectly mirrored
configuration, the controller indicates mirrored mode status after the
error is cleared.
Use this command for the following situations:

When the controller or cache modules have been replaced, resulting
in mismatched data between the controllers.
When the controller or cache module is replaced while data is still
in cache and not properly flushed with the SHUTDOWN or SET
NOFAILOVER COPY= commands.

Syntax
CLEAR_ERRORS controller INVALID_CACHE
Completely spell out the phrase INVALID_CACHE.

Parameters
controller
Identifies which controller is to receive the CLEAR_ERRORS
command. You must specify THIS_CONTROLLER or
OTHER_CONTROLLER.
data-retention-policy
DESTROY_UNFLUSHED_DATA
NODESTROY_UNFLUSHED_DATA (Default)
Instructs the controller how to handle write-back cached data. Specify
NODESTROY_UNFLUSHED_DATA (default) to retain the cached data
and discard controller information. Specify
DESTROY_UNFLUSHED_DATA to retain the controller information
and discard the cached data.
Specify NODESTROY_UNFLUSHED_DATA in the following
situations:

If the controller module has been replaced
If the controller’s nonvolatile memory (NVMEM) has lost its
contents, possibly from an NVMEM battery failure

CLI Reference Manual

Specify DESTROY_UNFLUSHED_DATA in the following situations:

If the cache module has been replaced
Any other reason not listed above

Caution Specifying the DESTROY_UNFLUSHED_DATA switch
destroys data remaining in cache, which can result in the possible loss
of data.

Examples
This example shows how to clear an invalid cache error on “this
controller” after you have replaced a controller module. Enter the
command on one line.
CLEAR_ERRORS THIS_CONTROLLER INVALID_CACHE
NODESTROY_UNFLUSHED_DATA

This example shows how to clear an invalid cache error on the “other
controller” after a cache module has been replaced. Enter this
command on the same line. Enter the command on one line.
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 unit-number LOST_DATA

CLEAR_ERRORS unit-number LOST_DATA
Clears lost data errors on a unit and All partitions on the unit’s
container are effected.
The controller reports a lost data error on the unit when you remove a
write-back cache module or when the cache module contains
unflushed data, possibly due to an interruption in the primary power
source with no backup power present. The CLEAR_ERRORS
LOST_DATA command clears the lost data error but does not recover
the lost data.
Note Clearing lost data errors or lost data block errors on a RAIDset
causes a reconstruction of all parity blocks. Clearing lost data errors or
lost data block errors on a mirrorset causes members to normalize.

Syntax
CLEAR_ERRORS unit-number LOST_DATA
Completely spell out the phrase LOST_DATA.
Caution This command may cause data loss.

Parameters
unit-number
Identifies the unit on which the lost data error is to be cleared. The unitnumber is the same name given to the unit when you added it to the
controller’s configuration.

Example
This example shows how to clear the lost data error on disk unit
number D103:
CLEAR_ERRORS D103 LOST_DATA

CLI Reference Manual

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS UNKNOWN

CLEAR_ERRORS UNKNOWN
Clears unknown errors from a device the controller identifies as
unknown or not correctly configured.
If a device failure causes the controller to label the device as unknown,
the controller does not check the device again to see if it has been
repaired or if the error condition has been corrected. You must enter
this command so the controller can recognize the device after the cause
of the error has been corrected.
Use this command to force the controller to recognize a failed device,
regardless of the controller’s prior evaluation of the device’s condition.

Syntax
CLEAR_ERRORS device-name UNKNOWN
The word UNKNOWN must be completely spelled out.

Parameters
device-name
Identifies the device with the unknown error.

Example
This example shows how to force the controller to recognize a
previously unknown device named DISK30000:
CLEAR_ERRORS DISK30000 UNKNOWN

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLEAR_ERRORS unit-number UNWRITEABLE_DATA

CLEAR_ERRORS unit-number UNWRITEABLE_DATA
This command clears an unwriteable data error on a unit.
This command affects all partitions on the same container.
If a storageset or disk drive fails before its data has been written to the
it, 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.
Caution This command causes the data loss.

Syntax
CLEAR_ERRORS unit-number UNWRITEABLE_DATA
Completely spell out the phrase UNWRITEABLE_DATA.

Parameters
unit-number
Identifies the unit having the unwriteable data error. The unit-number
is the name given to the unit when it was created with the ADD UNIT
command.

Example
This example shows how to clear the unwriteable data error on disk
unit D103:
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

CREATE_PARTITION

CREATE_PARTITION
This command divides a non-transportable disk drive or single-disk
storageset into several, separately addressable storage units. The
command marks a specified percentage of a disk drive or storageset to
be used as a separately addressable unit. You an divide any
nontransportable disk into a maximum of eight partitions. Each
partition can be separately presented to the host. Partitions are not
supported in multiple bus failover mode. Initialize disks and
storagesets before creating partitions.
Note Partitioned storagesets partitioned single-disk units cannot
function in multiple bus failover dual-redundant configurations.
Because they are not supported, you must delete your partitions before
configuring the controllers for multiple bus failover.
After you partition a container, you must initialize it before destroying
the partitions.

Syntax
CREATE_PARTITION container-name SIZE=percent

Parameters
container-name
Identifies the disk or storageset to partition. This is the same name
given to the disk or storageset when it was created with the ADD
command (for example, ADD DISK, ADD STRIPESET, and so forth).
Any disk, stripeset, mirrorset, striped mirrorset, or RAIDset can be
partitioned. A transportable disk cannot be partitioned. You must
initialize the container before creating a partition.
SIZE=percent
SIZE=LARGEST
Specifies the size of the partition to be created as a percentage of the
total container’s storageset size.
To create a partition, specify a percentage of the container’s total
capacity. The entire container is then divided into segments equal to
the percentage specified. For example, if SIZE-20, the container is
divided into five (1.0/0.2=5) equal segments. The resulting partition is

CLI Reference Manual

slightly smaller than the size specified because metadata also
accompanies each partition.
Specify LARGEST in the following situations:

To have the controller create the largest partition possible from
unused space on the disk or storageset.
To create the last partition on a container. Because the remaining
space is not equal to an exact percentage value, specifying
LARGEST allows you to optimize use of the remaining space.

Example
This example shows how to create a RAIDset named RAID9 and
divide it into four equal parts. It also creates host-addressable units for
each partition:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID9 DISK10000 DISK20100 DISK30200
INITIALIZE RAID9
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITOIN RAID9 SIZE=LARGEST
ADD UNIT D101 RAID9 PARTITION=1
ADD UNIT D102 RAID9 PARTITION=2
ADD UNIT D103 RAID9 PARTITION=3
ADD UNIT D104 RAID9 PARTITION=4

See also
ADD UNIT
DELETE unit-number
DESTROY PARTITION
SHOW

DELETE container-name

DELETE container-name
Deletes a container from the controller’s configuration. You cannot
delete a container in use by a higher-level container. For example, you
cannot delete a disk belonging to a member of a RAIDset, or a
RAIDset being declared as a unit; you must first delete the higher-level
container or containers.
Note This command does not delete spareset or failedsets. Spareset
and failedset containers cannot be deleted.
When a container is deleted, the individual disks are free to be used by
another container. If the container is again created with the exact same
disk configuration, and none of the disks have been used for anything,
then the container can be reassembled using its original disks.

Syntax
DELETE container-name

Parameters
container-name
Identifies the container to be deleted. This is the name given to the
container when it was created using the ADD command (for example,
ADD DISK, ADD STRIPESET, and so forth).

Examples
This example shows how to delete a disk drive named DISK10000:
DELETE DISK10000

This example shows how to delete a stripeset named STRIPE1:
DELETE STRIPE1

This example shows how to delete a RAIDset named RAID9:
DELETE RAID9

CLI Reference Manual

See also
DELETE FAILEDSET
DELETE SPARESET
UNMIRROR

DELETE FAILEDSET

DELETE FAILEDSET
Removes a disk drive from the failedset. The failedset contains disk
drives removed by the controller from RAIDsets and mirrorsets
because they failed or were manually removed using the SET
command. Enter the DELETE FAILEDSET command before
removing failed members from the storage shelf for testing, repair, or
replacement.
Regard disk drives in the failedset defective. Repair or replace
defective disk devices.

Syntax
DELETE FAILEDSET disk-name

Parameter
disk-name
Identifies the disk you want to delete from the failedset. Remove only
one disk at a time from a failedset.

Example
This example shows how to delete DISK20200 from the failedset:
DELETE FAILEDSET DISK20200

See also
SHOW UNITS
SHOW unit-number

SHOW

123

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

Syntax
SHOW controller
SHOW device-type
SHOW device-name
SHOW storageset-type
SHOW storageset-name
SHOW DEVICES
SHOW EMU
SHOW FAILEDSET
SHOW UNITS
SHOW unit-number

Parameters
device-type
Specifies the type of devices you want to be displayed. Valid choices
are:

DEVICES—Shows all devices attached to the controller
CDROMS—Shows all CD-ROM devices attached to the controller
DISKS—Shows all disks attached to the controller
PASSTHROUGH—Shows all passthrough containers attached to
the controller

device-name
Specifies the name of a particular device to be displayed. For example,
SHOW DISK20100 displays information about the device named
DISK20100.

124

CLI Reference Manual

EMU
Displays information regarding the status of the environmental
monitoring unit (EMU).
storageset-type
Specifies the type of storageset to be displayed. Valid types are:

STORAGESETS—Shows all storagesets configured with the
controller
RAIDSETS—Shows all RAIDsets configured to the controller
STRIPESETS—Shows all stripesets configured to the controller
MIRRORSETS—Shows all mirrorsets configured to the controller
SPARESET—Show the spareset configured to the controller
FAILEDSET—Shows the failedset configured to the controller

storageset-name
Specifies the name of a particular storageset to be displayed. 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 to be displayed. For example,
SHOW D102 displays information about the unit named D102.
THIS_CONTROLLER
OTHER_CONTROLLER
Specifies the controller to be displayed.

Switches
FULL
Displays additional information about each device, storageset, or
controller.

SHOW

125

Examples
This example shows how to display a listing of disks:
SHOW DISKS
Name
Type
Port Targ Lun
Used by
----------------------------------------------------------DISK20300
disk
2 3 0
D203
DISK20400
disk
2 4 0
D204

This example shows a full listing of devices attached to the controller:
SHOW DEVICES FULL
Name

Type

Port Targ

Lun

Used by

-----------------------------------------------------------------------------DISK11200
disk
1
12
0
R0
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8378028 blocks
DISK11400
disk

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8378028 blocks
DISK11500
disk

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8378028 blocks
DISK21200
disk

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8377528 blocks
Configuration being backed up on this container
DISK21400

disk
DEC

2
RZ28D

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 4108970 blocks
Configuration being backed up on this container
DISK21500
disk
2
15
0

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8377528 blocks
Configuration being backed up on this container

126

CLI Reference Manual

This example shows how to display a complete listing of the mirrorset
named MIRR1:
SHOW MIRR1
Name
Storageset
Uses
Used by
-----------------------------------------------------------------------------MIRR1

mirrorset

DISK50300
DISK60300

Switches:
POLICY (for replacement) = BEST_PERFORMANCE
COPY (priority) = NORMAL
READ_SOURCE = LEAST_BUSY
MEMBERSHIP = 2, 2 members present
State:
NORMAL
DISK60300 (member

0) is NORMAL

DISK50300 (member 1) is NORMAL
Size: 17769177 blocks

This example shows the full information for a controller:
SHOW THIS_CONTROLLER FULL
Controller:
Not configured for dual-redundancy
Device port SCSI address 7
Time: NOT SET
Host port:
SCSI target(s) (0, 2, 4, 5)
Preferred target(s) (0, 2, 4)
TRANSFER_RATE_REQUESTED = 20MHZ
Host Functionality Mode = A
Command Console LUN is target 0, lun 4
Cache:
64 megabyte write cache, version 4
Cache is GOOD
Battery is GOOD
No unflushed data in cache
CACHE_FLUSH_TIMER = DEFAULT (10 seconds)
NOCACHE_UPS
Mirrored Cache:
64 megabyte write cache, version 4
Cache is GOOD
Battery is GOOD
No unflushed data in cache
Extended information:
Terminal speed 19200 baud, eight bit, no parity, 1 stop bit
Operation control: 00000001 Security state code: 75580
Configuration backup disabled

SHOW

127

This example shows how to display the current settings for the EMU:
SHOW EMU
EMU CABINET SETTINGS
SENSOR_1_SETPOINT

DEGREES C

SENSOR_2_SETPOINT
SENSOR_3_SETPOINT

35
35

DEGREES C
DEGREES C

FANSPEED AUTOMATIC

SHUTDOWN controller

129

SHUTDOWN controller
Flushes all user data from the specified controller's write-back cache
(if present) and shuts down the controller. The controller does not
automatically restart. All units accessed through the failed controller
failover to the surviving controller.

Syntax
SHUTDOWN controller

Parameter
controller
Indicates which controller is to shut down. Specify
OTHER_CONTROLLER or THIS_CONTROLLER.

Switches
IGNORE_ERRORS
NOIGNORE_ERRORS (Default)
Controls the reaction of the controller based on the status of write-back
cache.
Caution The IGNORE_ERRORS and IMMEDIATE switches cause
the controller to keep unflushed data in the write-back cache until it
restarts and is able to write the data to devices. Do not perform any
hardware changes until the controller flushes the cache.
Specify IGNORE_ERRORS to instruct the controller to shutdown even
if the data within write-back cache cannot be written to the devices.
Specify NOIGNORE_ERRORS to instruct the controller to stop
operation if the data within write-back cache cannot be written to the
devices.
IMMEDIATE_SHUTDOWN
NOIMMEDIATE_SHUTDOWN (Default)
Instructs the controller when to shutdown.

130

CLI Reference Manual

Specify IMMEDIATE_SHUTDOWN to cause the controller to
shutdown immediately without checking for online devices or before
flushing data from the write-back cache to devices.
Specify NOIMMEDIATE_SHUTDOWN to cause the controller not to
shutdown without checking for online devices or before all data has
been flushed from the write-back cache to devices.

Examples
This example shows how to shut down “this controller”:
SHUTDOWN THIS_CONTROLLER

This example shows how to shut down the other controller, even if it
cannot write all of the write-back cached data to the units:
SHUTDOWN OTHER_CONTROLLER IGNORE_ERRORS

See also
RESTART controller
SELFTEST controller

UNMIRROR

131

UNMIRROR
Converts a one-member mirrorset back to a non-mirrored disk drive
and deletes its mirrorset from the list of known mirrorsets. This
command can be used on mirrorsets already members of higher-level
containers (stripesets or units).
The UNMIRROR command is not valid for disk drives having a
capacity greater than the capacity of the existing mirrorset. If a
mirrorset is comprised of disk drives with different capacities, the
mirrorset capacity is limited to the size of the smallest member; larger
members contain unused capacity. If a member with unused capacity is
the last remaining member of a mirrorset, the UNMIRROR command
cannot be used to change the disk drive back to a single-disk unit. This
change would cause a change in the reported disk capacity, possibly
confusing the operating system.

Syntax
UNMIRROR disk-name

Parameter
disk-name
Specifies the name of the normal mirrorset member to be removed
from a mirror storageset.

Example
This example shows how to convert DISK10300 back to a single
device:
UNMIRROR DISK10300

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

133

Glossary

This glossary defines terms pertaining to the HSZ70 array controller. It
is not a comprehensive glossary of computer terms.
adapter

A device that converts the protocol and hardware interface of one bus
type into another without changing the function of the bus.

array controller

See controller.

autospare

A controller feature that automatically replaces a failed disk drive. To
aid the controller in automatically replacing failed disk drives, you can
enable the AUTOSPARE switch for the failedset causing physically
replaced disk drives to be automatically placed into the spareset. Also
called “autonewspare.”

bad block

A data block that contains a physical defect.

backplane

The electronic printed circuit board into which you plug subsystem
devices—for example, the SBB or power supply.

BBR

Bad Block Replacement. A replacement routine that substitutes defectfree disk blocks for those found to have defects. This process takes
place in the controller, transparent to the host.

block

Also called a sector. The smallest collection of consecutive bytes
addressable on a disk drive. In integrated storage elements, a block
contains 512 bytes of data, error codes, flags, and the block’s address
header.

bootstrapping

A method used to bring a system or device into a defined state by
means of its own action. For example, a machine routine whose first
few instructions are enough to bring the rest of the routine into the
computer from an input device.

cache memory

A portion of memory used to accelerate read and write operations.

134

CLI Reference Manual

CDU

Cable distribution unit. The power entry device for StorageWorks
cabinets. The CDU provides the connections necessary to distribute
power to the cabinet shelves and fans.

channel

Another term for a SCSI bus. See also SCSI.

chunk

A block of data written by the host.

chunk size

The number of data blocks, assigned by a system administrator, written
to the primary RAIDset or stripeset member before the remaining data
blocks are written to the next RAIDset or stripeset member.

CLI

Command line interpreter. The configuration interface to operate the
controller software.

cold swap

A method of device replacement that requires the entire subsystem to
be turned off before the device can be replaced. See also hot swap and
warm swap.

configuration file

A file that contains a representation of a storage subsystem’s
configuration.

container

(1) Any entity that is capable of storing data, whether it is a physical
device or a group of physical devices. (2) A virtual, internal, controller
structure representing either a single disk or a group of disk drives
linked as a storageset. Stripesets and mirrorsets are examples of
storageset containers the controller uses to create units.

controller

A hardware device that, with proprietary software, facilitates
communications between a host and one or more devices organized in
an array. HS family controllers are examples of array controllers.

copying

A state in which data to be copied to the mirrorset is inconsistent with
other members of the mirrorset. See also normalizing.

copying member

Any member that joins the mirrorset after the mirrorset is created is
regarded as a copying member. Once all the data from the normal
member (or members) is copied to a normalizing or copying member,
the copying member then becomes a normal member. See also
normalizing member.

Glossary

135

data center cabinet

A generic reference to large DIGITAL subsystem cabinets, such as the
SW600-series and 800-series cabinets in which StorageWorks
components can be mounted.

data striping

The process of segmenting logically sequential data, such as a single
file, so that segments can be written to multiple physical devices
(usually disk drives) in a round-robin fashion. This technique is useful
if the processor is capable of reading or writing data faster than a
single disk can supply or accept the data. While data is being
transferred from the first disk, the second disk can locate the next
segment.

differential I/O module

A 16 bit I/O module with SCSI bus converter circuitry for extending a
differential SCSI bus. See also I/O module.

differential SCSI bus

A bus in which 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. The controller’s diagnostic software used to test
the data transfer capabilities of disk drives in a way that simulates a
high level of user activity.

dirty data

The write-back cached data that has not been written to storage media,
even though the host operation processing the data has completed.

DOC

DWZZA-On-a-Chip. An NCR53C120 SCSI bus extender chip used to
connect a SCSI bus in an expansion cabinet to the corresponding SCSI
bus in another cabinet.

dual-redundant
configuration

A controller configuration consisting of two active controllers
operating as a single controller. If one controller fails, the other
controller assumes control of the failing controller’s devices.

DUART

Dual universal asynchronous receiver and transmitter. An integrated
circuit containing two serial, asynchronous transceiver circuits.

DWZZA

A StorageWorks SCSI-bus-signal converter used to connect 8-bit
single-ended devices to hosts with 16-bit differential SCSI adapters.
This converter extends the range of a single-ended SCSI cable to the
limit of a differential SCSI cable. See also SCSI bus signal converter.

136

CLI Reference Manual

DWZZB

A StorageWorks SCSI bus signal converter used to connect a variety
of 16-bit single-ended devices to hosts with 16-bit differential SCSI
adapters. See also SCSI bus signal converter.

DWZZC

The 16-bit SCSI table-top SCSI bus signal converter used to extend a
differential SCSI bus, or connect a differential SCSI bus to a single
ended SCSI bus. See also SCSI bus signal converter.

ECB

External cache battery. The unit that supplies backup power to the
cache module in the event the primary power source fails or is
interrupted.

EMU

Environmental monitoring unit. A unit that provides increased
protection against catastrophic failures. Some subsystem enclosures
include an EMU which works with the controller to detect conditions
such as failed power supplies, failed blowers, elevated temperatures,
and external air sense faults. The EMU also controls certain cabinet
hardware including DOC chips, alarms, and fan speeds.

ESD

Electrostatic discharge. The discharge of potentially harmful static
electrical voltage as a result of improper grounding.

extended subsystem

A subsystem in which two cabinets are connected to the primary
cabinet.

external cache battery

See ECB.

failedset

A group of failed mirrorset or RAIDset devices automatically created
by the controller.

failover

The process that takes place when one controller in a dual-redundant
configuration assumes the workload of a failed companion controller.
Failover continues until the failed controller is repaired or replaced.

FCC

Federal Communications Commission. The federal agency responsible
for establishing standards and approving electronic devices within the
United States.

FCC Class A

This certification label appears on electronic devices that can only be
used in a commercial environment within the United States.

Glossary

137

FCC Class B

This certification label appears on electronic devices that can be used
in either a home or a commercial environment within the United States.

FD SCSI

The fast, narrow, differential SCSI bus with an 8-bit data transfer rate
of 10 MB/s. See also FWD SCSI and SCSI.

flush

The act of writing dirty data from cache to a storage media.

forced errors

A data bit indicating a corresponding logical data block contains
unrecoverable data.

FRU

Field replaceable unit. A hardware component that can be replaced at
the customer’s location by DIGITAL service personnel or qualified
customer service personnel.

FWD SCSI

A fast, wide, differential SCSI bus with a maximum 16-bit data
transfer rate of 20 MB/s. See also SCSI and FD SCSI.

host

The primary or controlling computer to which a storage subsystem is
attached.

host adapter

A device that connects a host system to a SCSI bus. The host adapter
usually performs the lowest layers of the SCSI protocol. This function
may be logically and physically integrated into the host system.

host compatibility mode

A setting used by the controller to provide optimal controller
performance with specific operating systems. This improves the
controller’s performance and compatibility with the specified operating
system. The supported modes are: A, Normal (including DIGITAL
UNIX®, OpenVMS, Sun®, and Hewlett-Packard® HP–UX); B, IBM
AIX®; C, Proprietary; and D, Microsoft Windows NTTM Server.

hot disks

A disk containing multiple hot spots. Hot disks occur when the
workload is poorly distributed across storage devices and prevents
optimum subsystem performance. See also hot spots.

hot spots

A portion of a disk drive frequently accessed by the host. Because the
data being accessed is concentrated in one area, rather than spread
across an array of disks providing parallel access, I/O performance is
significantly reduced. See also hot disks.

138

CLI Reference Manual

hot swap

A method of device replacement that allows normal I/O activity on a
device’s bus to remain active during device removal and insertion. The
device being removed or inserted is the only device that cannot
perform operations during this process. See also cold swap and warm
swap.

HSOF

Hierarchical Storage Operating Firmware. Software contained on a
removable ROM program card that provides the operating system for
the array controller.

initiator

A SCSI device that requests an I/O process to be performed by another
SCSI device, namely, the SCSI target. The controller is the initiator on
the device bus. The host is the initiator on the host bus.

instance code

A four-byte value displayed in most text error messages and issued by
the controller when a subsystem error occurs. The instance code
indicates when during software processing the error was detected.

I/O module

A 16-bit SBB shelf device that integrates the SBB shelf with either an
8-bit single ended, 16-bit single-ended, or 16-bit differential SCSI bus.
See also I/O Module.

JBOD

Just a bunch of disks. A term used to describe a group of single-device
logical units.

local connection

A connection to the subsystem using either its serial maintenance port
or the host’s SCSI bus. A local connection enables you to connect to
one subsystem controller within the physical range of the serial or host
SCSI cable.

local terminal

A terminal plugged into the EIA-423 maintenance port located on the
front bezel of the controller. See also maintenance terminal.

logical bus

A single-ended bus connected to a differential bus by a SCSI bus
signal converter.

logical unit

A physical or virtual device addressable through a target ID number.
LUNs use their target’s bus connection to communicate on the SCSI
bus.

logical unit number

A value that identifies a specific logical unit belonging to a SCSI target
ID number. A number associated with a physical device unit during a

Glossary

139

task’s I/O operations. Each task in the system must establish its own
correspondence between logical unit numbers and physical devices.
LRU

Least recently used. A cache term used to describe the block
replacement policy for read cache.

maintenance terminal

An EIA-423-compatible terminal used with the controller. This
terminal is used to identify the controller, enable host paths, enter
configuration information, and check the controller’s status. The
maintenance terminal is not required for normal operations.
See also local terminal.

MB/s

Megabytes per second. A unit designation used to measure the SCSI
bus bandwidth.

member

A container that is a storage element in a RAID array.

metadata

The data written to a disk for the purposes of controller administration.
Metadata improves error detection and media defect management for
the disk drive. It is also used to support storageset configuration and
partitioning. Non-transportable disks also contain metadata to indicate
they are uniquely configured for StorageWorks environments.
Metadata can be thought of as “data about data.”

mirroring

The act of creating an exact copy or image of data.

mirrored write-back
caching

A method of caching data that maintains two copies of the cached data.
The copy is available if either cache module fails.

mirrorset

See RAID level 1.

nominal membership

The desired number of mirrorset members when the mirrorset is fully
populated with active devices. If a member is removed from a
mirrorset, the actual number of members may fall below the “nominal”
membership.

non-redundant
controller configuration

(1) A single controller configuration. (2) A controller configuration
which does not include a second controller.

normal member

A mirrorset member that, block-for-block, contains the same data as
other normal members within the mirrorset. Read requests from the
host are always satisfied by normal members.

140

CLI Reference Manual

normalizing

Normalizing is a state in which, block-for-block, data written by the
host to a mirrorset member is consistent with the data on other normal
and normalizing members. The normalizing state exists only after a
mirrorset is initialized. Therefore, no customer data is on the mirrorset.

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. A normalizing
member is created by a normal member when either all of the normal
members fail or all of the normal members are removed from the
mirrorset. See also copying member.

NVM

Non-Volatile Memory. A type of memory—the contents of which
survive loss of power.

OCP

Operator control panel. The control or indicator panel associated with
a device. The OCP is usually mounted on the device and is accessible
to the operator.

other controller

The controller in a dual-redundant pair that’s connected to the
controller that’s serving your current CLI session. See also this
controller.

PCM

Polycenter Console Manager.

PCMCIA

Personal Computer Memory Card Industry Association. An
international association formed to promote a common standard for PC
card-based peripherals to be plugged into notebook computers. The
card commonly known as a PCMCIA card is about the size of a credit
card.

parity

A method of checking if binary numbers or characters are correct by
counting the ONE bits. In odd parity, the total number of ONE bits
must be odd; in even parity, the total number of ONE bits must be
even. Parity information can be used to correct corrupted data.
RAIDsets use parity to improve the availability of data.

parity bit

A binary digit added to a group of bits that checks to see if there are
errors in the transmission.

parity RAID

See RAIDset.

Glossary

141

partition

A logical division of a container, represented to the host as a logical
unit.

port

(1) In general terms, a logical channel in a communications system. (2)
The hardware and software used to connect a host controller to a
communications bus, such as a SCSI bus or serial bus.
Regarding the controller, the port is: (1) the logical route for data in
and out of a controller that can contain one or more channels, all of
which contain the same type of data. (2) The hardware and software
that connects a controller to a SCSI device.

primary cabinet

The primary cabinet is the subsystem enclosure that contains the
controllers, cache modules, external cache batteries, and the PVA
module.

program card

The PCMCIA card containing the controller’s operating software.

PTL

Port-Target-LUN. The controller’s method of locating a device on the
controller’s device bus.

PVA module

Power Verification and Addressing module.

quiesce

The act of rendering bus activity inactive or dormant. For example,
“quiesce the SCSI bus operations during a device warm-swap.”

RAID

Redundant Array of Independent Disks. Represents multiple levels of
storage access developed to improve performance or availability or
both.

RAID level 0

A RAID storageset that stripes data across an array of disk drives. A
single logical disk spans multiple physical disks, allowing parallel data
processing for increased I/O performance. While the performance
characteristics of RAID level 0 is excellent, this is the only RAID level
that does not provide redundancy. Raid level 0 storagesets are
sometimes referred to as stripesets.

RAID level 0+1

A RAID storageset that stripes data across an array of disks (RAID
level 0) and mirrors the striped data (RAID level 1) to provide high I/O
performance and high availability. This RAID level is alternatively
called a striped mirrorset. Raid level 0+1 storagesets are sometimes
referred to as striped mirrorsets.

142

CLI Reference Manual

RAID level 1

A RAID storageset of two or more physical disks that maintains a
complete and independent copy of the entire virtual disk's data. This
type of storageset has the advantage of being highly reliable and
extremely tolerant of device failure. Raid level 1 storagesets are
sometimes referred to as mirrorsets.

RAID level 3

A RAID storageset that transfers data parallel across the array’s disk
drives a byte at a time, causing individual blocks of data to be spread
over several disks serving as one enormous virtual disk. A separate
redundant check disk for the entire array stores parity on a dedicated
disk drive within the storageset. Contrast RAID level 5.

RAID Level 5

A RAID storageset that, unlike RAID level 3, stores the parity
information across all of the disk drives within the storageset. Contrast
RAID level 3.

RAID level 3/5

A DIGITAL-developed RAID storageset that stripes data and parity
across three or more members in a disk array. A RAIDset combines
the best characteristics of RAID level 3 and RAID level 5. A RAIDset
is the best choice for most applications with small to medium I/O
requests, unless the application is write intensive. A RAIDset is
sometimes called parity RAID. Raid level 3/5 storagesets are
sometimes referred to as RAIDsets.

RAIDset

See RAID level 3/5.

read caching

A cache management method used to decrease the subsystem’s
response time to a read request by allowing the controller to satisfy the
request from the cache memory rather than from the disk drives.

reconstruction

The process of regenerating the contents of a failed member’s data.
The reconstruct process writes the data to a spareset disk and then
incorporates the spareset disk into the mirrorset, striped mirrorset, or
RAIDset from which the failed member came. See also regeneration.

reduced

Indicates that a mirrorset or RAIDset is missing one member because
the member has failed or has been physically removed.

redundancy

The provision of multiple interchangeable components to perform a
single function in order to cope with failures and errors. A RAIDset is
considered to be redundant when user data is recorded directly to one

Glossary

143

member and all of the other members include associated parity
information.
regeneration

(1) The process of calculating missing data from redundant data. (2)
The process of recreating a portion of the data from a failing or failed
drive using the data and parity information from the other members
within the storageset. The regeneration of an entire RAIDset member
is called reconstruction. See also reconstruction.

RFI

Radio frequency interference. The disturbance of a signal by an
unwanted radio signal or frequency.

replacement policy

The policy specified by a switch with the SET FAILEDSET command
indicating whether a failed disk from a mirrorset or RAIDset is to be
automatically replaced with a disk from the spareset. The two switch
choices are AUTOSPARE and NOAUTOSPARE.

SBB

StorageWorks building block. (1) A modular carrier plus the interface
required to mount the carrier into a standard StorageWorks shelf. (2)
any device conforming to shelf mechanical and electrical standards
installed in a 3.5-inch or 5.25-inch carrier, whether it is a storage
device or power supply.

SCSI

Small computer system interface. (1) An ANSI interface standard
defining the physical and electrical parameters of a parallel I/O bus
used to connect initiators to devices. (2) a processor-independent
standard protocol for system-level interfacing between a computer and
intelligent devices including hard drives, floppy disks, CD-ROMs,
printers, scanners, and others.

SCSI-A cable

A 50-conductor (25 twisted-pair) cable generally used for singleended, SCSI-bus connections.

SCSI bus signal
converter

Sometimes referred to as an adapter. (1) A device used to interface
between the subsystem and a peripheral device unable to be mounted
directly into the SBB shelf of the subsystem. (2) a device used to
connect a differential SCSI bus to a single-ended SCSI bus. (3) A
device used to extend the length of a differential or single-ended SCSI
bus. See also DWZZA, DWZZB, DWZZC, and I/O module.

144

CLI Reference Manual

SCSI device

(1) A host computer adapter, a peripheral controller, or an intelligent
peripheral that can be attached to the SCSI bus. (2) Any physical unit
that can communicate on a SCSI bus.

SCSI device ID number

A bit-significant representation of the SCSI address referring to one of
the signal lines, numbered 0 through 7 for an 8-bit bus, or 0 through 15
for a 16-bit bus. See also target ID number.

SCSI ID number

The representation of the SCSI address that refers to one of the signal
lines numbered 0 through 15.

SCSI-P cable

A 68-conductor (34 twisted-pair) cable generally used for differential
bus connections.

SCSI port

(1) Software: The channel controlling communications to and from a
specific SCSI bus in the system. (2) Hardware: The name of the logical
socket at the back of the system unit to which a SCSI device is
connected.

signal converter

See SCSI bus signal converter.

single ended I/O module

A 16-bit I/O module. See also I/O module.

single-ended SCSI bus

An electrical connection where one wire carries the signal and another
wire or shield is connected to electrical ground. Each signal’s logic
level is determined by the voltage of a single wire in relation to
ground. This is in contrast to a differential connection where the
second wire carries an inverted signal.

spareset

A collection of disk drives made ready by the controller to replace
failed members of a storageset.

storage array

An integrated set of storage devices.

storage array subsystem

See storage subsystem.

storageset

(1) A group of devices configured with RAID techniques to operate as
a single container. (2) Any collection of containers, such as stripesets,
mirrorsets, striped mirrorsets, and RAIDsets.

storage subsystem

The controllers, storage devices, shelves, cables, and power supplies
used to form a mass storage subsystem.

Glossary

145

storage unit

The general term that refers to storagesets, single-disk units, and all
other storage devices that are installed in your subsystem and accessed
by the 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.

StorageWorks

A family of DIGITAL modular data storage products which allow
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 enclosures to form storage subsystems.
StorageWorks systems include integrated SBBs and array controllers
to form storage subsystems. System-level enclosures to house the
shelves and standard mounting devices for SBBs are also included.

stripe

The data divided into blocks and written across two or more member
disks in an array.

striped mirrorset

See RAID level 0+1.

stripeset

See RAID level 0.

stripe size

The stripe capacity as determined by n–1 times the chunksize, where n
is the number of RAIDset members.

striping

The technique used to divide data into segments, also called chunks.
The segments are striped, or distributed, across members of the
stripeset. This technique helps to distribute hot spots across the array
of physical devices to prevent hot spots and hot disks.
Each stripeset member receives an equal share of the I/O request load,
improving performance.

surviving controller

The controller in a dual-redundant configuration pair that serves its
companion’s devices when the companion controller fails.

tape

A storage device supporting sequential access to variable sized data
records.

Tape Inline Exerciser

See TILX.

146

CLI Reference Manual

target

(1) A SCSI device that performs an operation requested by an initiator.
(2) Designates the target identification (ID) number of the device.

target ID number

The address a bus initiator uses to connect with a bus target. Each bus
target is assigned a unique target address.

this controller

The controller that is serving your current CLI session through a local
or remote terminal. See also other controller.

TILX

Tape inline exerciser. The controller’s diagnostic software to test the
data transfer capabilities of tape drives in a way that simulates a high
level of user activity.

Ultra SCSI bus

A wide, fast-20 SCSI bus.

unit

A container made accessible to a host. A unit may be created from a
single disk drive or tape drive. A unit may also be created from a more
complex container such as a RAIDset. The controller supports a
maximum of eight units on each target. See also target and target ID
number.

unwritten cached data

Sometimes called unflushed data. See dirty data.

UPS

Uninterruptible power supply. A battery-powered power supply
guaranteed to provide power to an electrical device in the event of an
unexpected interruption to the primary power supply. Uninterruptible
power supplies are usually rated by the amount of voltage supplied and
the length of time the voltage is supplied.

VHDCI

Very high-density-cable interface. A 68-pin interface. Required for
ultra-SCSI connections.

virtual terminal

A software path from an operator terminal on the host to the
controller's CLI interface, sometimes called a host console. The path
can be established via the host port on the controller (using HSZ term)
or via the maintenance port through an intermediary host.

warm swap

A device replacement method that allows the complete system remains
online during device removal or insertion. The system bus may be
halted, or quiesced, for a brief period of time during the warm-swap
procedure.

Glossary

147

write-back caching

A cache management method used to decrease the subsystem’s
response time to write requests by allowing the controller to declare
the write operation “complete” as soon as the data reaches its cache
memory. The controller performs the slower operation of writing the
data to the disk drives at a later time.

write-through caching

A cache management method used to decrease the subsystem’s
response time to a read. This method allows the controller to satisfy the
request from the cache memory rather than from the disk drives.

write hole

The period of time in a RAID level 1 or RAID level 5 write operation
when there is an opportunity for undetectable RAIDset data corruption.
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 in cache and unsuccessful write operations can be retried.

write-through cache

A cache management technique for retaining host write requests in
read cache. When the host requests a write operation, the controller
writes data directly to the storage device. This technique allows the
controller to complete some read requests from the cache, greatly
improving the response time to retrieve data. The operation is complete
only after the data to be written is received by the target storage device.
This cache management method may update, invalidate, or delete data
from the cache memory accordingly, to ensure that the cache contains
the most current data.

149

Index
A
abbreviations, xii
ADD CDROM command, syntax, 7
ADD device-name command
switches
TRANSFER_RATE_REQUESTED, 10
ADD DISK command
switches
NOTRANSPORTABLE, 9
TRANSPORTABLE, 9
syntax, 9
ADD MIRRORSET command
switches
COPY, 13
POLICY, 14
READ_SOURCE, 14
syntax, 13
ADD PASSTHROUGH command
switches
TRANSFER_RATE_REQUESTED, 18
syntax, 17
ADD RAIDSET command
switches
NOPOLICY, 19–20
POLICY, 19–20
RECONSTRUCT, 20
REDUCED, 20
syntax, 19
ADD SPARESET command, syntax, 23
ADD STRIPESET command, syntax, 25
ADD UNIT command
switches
ACCESS_ID, 28
MAXIMUM_CACHED_TRANSFER, 29
PARTITION, 29
PREFERRED_PATH, 29

RUN, 30, 120
WRITE_PROTECT, 31, 120
WRITEBACK_CACHE, 31, 120
syntax, 27
adding
CD-ROM drives, 7
disks, 9
mirrorsets, 13
passthrough containers, 17
sparesets, 23
stripesets, 25
units, 27
addressing, units, 4–6

B
BBR, 133

C
cable distribution unit, 134
cables
SCSI-bus cable lengths, 90
tightening, ix
cache, setting flush timer, 84
Caution, defined, xi
CD-ROM
adding to configuration, 7
deleting, 45
showing, 123
CD-ROMs
displaying information, 123
CFMENU, running, 79
chunksize, setting storageset size, 60
CLCP, running, 79
CLEAR_ERRORS CLI command, syntax, 33
CLEAR_ERRORS controller

150

CLI Reference Manual

INVALID_CACHE command
syntax, 35
CLEAR_ERRORS controller
INVALID_CACHE command, syntax, 35
CLEAR_ERRORS LOST_DATA command,
syntax, 37
CLEAR_ERRORS UNKNOWN command,
syntax, 39
CLEAR_ERRORS UNWRITEABLE_DATA
command, syntax, 41
CLI
abbreviating commands, 2
customizing the prompt, 89
definition, 1
help, 57
overview, 1
CLONE, running, 79
command editing keys, 3
command line interpreter. See CLI
commands
abbreviating, 2
ADD CDROM, 7
ADD DISK, 9
ADD MIRRORSET, 13
ADD PASSTHROUGH, 17
ADD RAIDSET, 19
ADD SPARESET, 23
ADD STRIPESET, 25
ADD UNIT, 27
CLEAR_ERRORS CLI, 33
CLEAR_ERRORS INVALID_CACHE, 35
CLEAR_ERRORS LOST_DATA, 37
CLEAR_ERRORS UNKNOWN, 39
CLEAR_ERRORS
UNWRITEABLE_DATA, 41
CREATE_PARTITION, 43
DELETE container-name, 45
DELETE FAILEDSET, 47
DELETE SPARESET, 49
DELETE unit-number, 51
DESTROY_PARTITION, 53
DIRECTORY , 55

getting help, 2
HELP, 57
INITIALIZE, 59
LOCATE, 63
MIRROR, 65
overview, 1
REDUCE, 69
RENAME, 73
RETRY_ERRORS, 77
rules for entering, 2
RUN, 79
SET device-name, 93
SET EMU, 95
SET FAILEDSET, 99
SET FAILOVER, 101
SET mirrorset-name, 103
SET MULTIBUS_FAILOVER, 109
SET NOMULTIBUS_FAILOVER. See
SET NOFAILOVER
SET RAIDset-name, 113
SET unit-number, 117
SHOW, 123
syntax, 6
typing ahead, 2
UNMIRROR, 131
CONFIG, running, 79
configuration
modifying controller configurations, 1
restoring, 61
connection
local, 1
remote, 1
container
defined, 134
initializing, 59
controllers
"this" and "other" defined, x
displaying information, 123
load balancing, 88
showing, 123
shutting down, 129

Index

conventions
abbreviations, xii
typographical, x
warnings, cautions, tips, notes, x
CREATE_PARTITION command, syntax, 43
creating
CD-ROMs, 7
disks, 9
mirrorsets, 13
passthrough containers , 17
single-disk units, 31
sparesets, 23
stripesets, 25
units, 27

D
data center cabinet, 135
DELETE container-name command, syntax, 45
DELETE FAILEDSET command, syntax, 47
DELETE SPARESET command, syntax, 49
DELETE unit-number command, syntax, 51
deleting
CD-ROMs, 45
devices, 45
mirrorsets, 45
optical disk drives, 45
RAIDsets, 45
storagesets, 45
stripesets, 45
tape drives, 45
tape loaders, 45
units, 51
DESTROY_PARTITION command, syntax, 53
devices
locating, 63
setting data transfer rate, 10, 18, 93
showing, 123
diagnostics
listing of, 55
running, 79
DILX, running, 79
DIRECT, running, 80

DIRECTORY command, syntax, 55
disk drives
adding to configuration, 9
deleting, 45
displaying information, 123
initializing, 59
making transportable, 93
mirroring, 65
removing from a mirrorset, 69
removing from the failedset, 47
removing from the spareset, 49
renaming, 73
setting device data transfer rate, 10, 18
showing, 123
transfer rate, 10, 18
documentation, related, xii
DSTAT, running, 80
dual-redundant configuration
disabling, 111
enabling, 101
DUART, 135
DWZZA, 135
DWZZB, 136

E
electrostatic discharge See ESD , viii
EMU
defined, 136
setting, 95
error messages
clearing from CLI, 33
clearing unwriteable data errors, 41
ESD
defined, 136
precautions, viii

F
failedset, deleting members, 47
failover
defined, 136
disabling, 111

151

152

CLI Reference Manual

finding devices and storagesets, 63
FMU, running, 80
FRUTIL, running, 80
FWD SCSI, 137

H
HELP command, syntax, 57
history, revision of this manual, xiii
host
compatibility mode, 85
setting data transfer rate, 90
hot standby controller, 89
HSOF, 138
HSUTIL, running, 80
HSZterm. See remote connection

switches
COPY, 65
POLICY, 66
syntax, 65
mirrorset
actual number of members, 69
adding to configuration, 13
choosing a replacement member, 14, 19
converting back to a single device, 131
creating from a single disk, 65
deleting, 45
initializing, 59
removing a member, 69
setting a replacement policy, 14, 19
showing, 123
unmirroring, 131
mirrorsets
displaying information, 123
renaming, 73

initialize
before adding unit, 27
saving user data, 60
INITIALIZE command
switches
CHUNKSIZE, 60
DESTROY, 60
SAVE_CONFIGURATION, 61
syntax, 59

nominal membership, 139
non-redundant configuration, 139
nonvolatile, defined
normalizing member, 140
Note, defined, xi
NV. See nonvolatile

listing diagnostics and utilities, 55
load balancing, 88
local connection, 1
local connection port, precautions, ix
local terminal, 138
LOCATE command, syntax, 63
lost data error, clearing, 37
LRU, 139

M
maintenance terminal, defined, 139
MIRROR command

optical disk drives
deleting, 45
displaying information, 123
showing, 123
other controller, explained, 1

P
partitions
creating, 43
deleting unit, 51
displaying size, 123

Index

setting size, 43
showing, 123
passthrough containers
adding to configuration, 17
deleting, 45
renaming, 73
showing, 123
port-target-LUN, defined, 141
precautions
electrostatic discharge, viii
local connection port, ix
VHDCI cables, ix
preferred SCSI target ID numbers, setting, 88
PTL
defined, 141
specifying with ADD CDROM command, 7
specifying with ADD DISK command, 9
specifying with ADD PASSTHROUGH
command, 17
publications, related, xii

Q
quiesce, 141

R
RAIDset
adding while missing a member, 20
changing characteristics, 113
deleting, 45
displaying information, 123
initializing, 59
removing a member, 114
replacing a member, 115
showing, 123
specifying chunksize, 60
specifying replacement policy, 113
RAIDsets
renaming, 73
REDUCE command, syntax, 70
redundancy, defined, 142
regenerate process, defined, 143

153

related publications, xii
remote connection, 1
removing a mirrorset member, 69
RENAME command, syntax, 73
RESTART controller command
switches
IGNORE_ERRORS, 75
IMMEDIATE_SHUTDOWN, 75–76
NOIGNORE_ERRORS, 75
NOIMMEDIATE_SHUTDOWN, 75–76
syntax, 75
RETRY_ERRORS command, syntax, 77
RETRY_ERRORS UNWRITEABLE_DATA
command, syntax, 77
revision history, xiii
RUN
CFMENU, 79
CLCP, 79
CLONE, 79
command syntax, 79
CONFIG, 79
DILX, 79
DIRECT, 80
DSTAT, 80
FMU, 80
FRUTIL, 80
HSUTIL, 80
VTDPY , 80

S
SBB, 143
SCSI
bus cable lengths, 90
preferring target ID numbers, 88
setting target ID numbers, 86
SCSI-A cable, 143
SCSI-B cable, 144
SELFTEST controller command
switches
IGNORE_ERRORS, 81
IMMEDIATE_SHUTDOWN, 81
syntax, 81

154

CLI Reference Manual

SET controller command, 83
switches
CACHE_FLUSH_TIMER, 84
CACHE_UPS, 85
COMMAND_CONSOLE_LUN, 85
INITIAL_CONFIGURATION, 87
MIRRORED_CACHE, 87
PREFERRED_ID , 88
PROMPT, 89
target ID number, 86
TERMINAL_PARITY, 89
TERMINAL_SPEED, 89
TIME, 90
TRANSFER_RATE_REQUESTED, 90
syntax, 83
SET device-name
switches
TRANSFER_RATE_REQUESTED, 93
SET device-name command
switches
NOTRANSPORTABLE, 93–94
TRANSFER_RATE_REQUESTED, 10, 18
TRANSPORTABLE, 93–94
syntax, 93
SET EMU command
switches
FANSPEED, 96
SENSOR SETPOINT, 95
syntax, 95
SET FAILEDSET command, syntax, 99
SET FAILOVER command
switches
DESTROY_UNFLUSHABLE_DATA, 111
syntax, 101
SET mirrorset-name command
switches
COPY, 103
MEMBERSHIP, 103
POLICY, 105
READ_SOURCE, 106
REMOVE, 104
REPLACE, 105

syntax, 103
SET MULTIBUS_FAILOVER command, syntax, 109
SET NOFAILOVER command
switches, 111–112
syntax, 111
SET RAIDset-name command
switches
POLICY, 113
RECONSTRUCT, 114
REMOVE, 114
REPLACE, 115
syntax, 113
SET unit-number command
switches
ACCESS_ID, 118
MAXIMUM_CACHED_TRANSFER, 118
PREFERRED_PATH, 119
READ_CACHE, 119
syntax, 117
setting
cache flush timer, 84
CLI prompt, 89
command console LUN, 85
command console lun, 85
control of metadata, 60
controller behavior at restart, 75
controller behavior at shutdown, 129
controller behavior selftest, 81
controller cache flush timer, 84
controller cache ups policy, 85
controller configuration handling, 61
controller data transfer rate, 90
controller error handling at restart, 75
controller error handling at selftest, 75, 81
controller error handling at shutdown, 129
controller initial configuration, 87
controller preferred target ID number, 88
controller target ID number, 86
controller transfer rate, 90
controller’s host compatibility mode, 85
data retention policy, 35

Index

device data transfer rate, 10, 18, 93
device transfer rate, 10, 18, 93
failedset autospare feature, 99
fan speed, 96
full display, 124
host data transfer rate, 90
mirrored write-back cache, 87
mirrorset copy data, 65
mirrorset copy speed, 13, 103
mirrorset member read source, 14
mirrorset read source, 14
mirrorset spareset replacement policy, 14
number of blocks cached by controller, 29, 118
number of mirrorset members, 103
number of unit partitions, 29
partition size, 35, 43
preferred path for units, 29, 119
preferred SCSI target ID numbers, 88
RAIDset member reconstruct policy, 20, 114
RAIDset member replacement policy, 14, 19, 113
RAIDset reduced member policy, 20
read cache for units, 30, 119
SCSI target ID numbers, 86
storageset chunksize, setting, 60
subsystem temperature sensor setpoint, 95
terminal parity, 89
terminal speed, 89
time, 90
transportability of devices, 93
transportability of disks , 9, 93
unit access ID number, 28, 118
unit availability to the host, 30, 120
virtual LUN, 85
write protect for units, 31, 120
write-back cache for units, 31, 120
SHOW command
parameters, 123–124
switches, FULL, 124
syntax, 123
SHUTDOWN controller command
parameters, 129
switches, 129–130

IGNORE_ERRORS, 129
IMMEDIATE_SHUTDOWN, 129
syntax, 129
spareset
adding to configuration, 23
removing a disk drive, 49
speed. See transfer rate
storagesets
defined, 144
displaying information, 123
initializing, 59
locating, 63
renaming, 73
showing, 123
StorageWorks array controller, 1
stripe size, defined, 145
stripe, defined, 145
stripesets
adding to configuration, 25
deleting, 45
displaying information, 123
initializing, 59
mirroring, 65
renaming, 73
showing, 123
specifying chunksize, 60

T
tape drives
deleting, 45
displaying information, 123
renaming, 73
showing, 123
tape loaders
deleting, 45
displaying information, 123
showing, 123
terminal
setting parity, 89
setting speed, 89
testing controllers, 81
this controller

155

156

CLI Reference Manual

defined, x
explained, 1
removing from dual-redundant
configuration, 111
starting diagnostic or utility programs, 79
tightening VHDCI cables, ix
Tip, defined, xi
transfer rate
setting controller, 90
setting device, 10, 18, 93
typographical conventions, x

U
units
adding to configuration, 27
changing characteristics, 117
clearing lost data error, 37
deleting from the configuration, 51
displaying configured units, 124
displaying information, 123
mirroring, 65
number format, 4–6
showing, 123
UNMIRROR command
parameters, 131
syntax, 131
unwriteable data error, retrying, 77
utilities
CFMENU, 79
CLCP, 79
CLONE, 79
CONFIG, 79
DILX, 79
DIRECT, 80
DSTAT, 80
FMU, 80
FRUTIL, 80
HSUTIL, 80
listing of, 55
running, 79
VTDPY , 80

V
VHDCI cable precautions, ix
virtual disk, setting. See SET controller
COMMAND_CONSOLE_LUNcommand
VTDPY, running, 80

W
Warning, defined, xi
write hole, 147
write-back cache, setting the flush timer, 84