Compaq Computer Corporation
Houston, Texas
CLI Reference Manual
January 1999
While Compaq Computer Corporation believes the information included in this manual is correct as of date of
publication, it is subject to change without notice. Compaq Computer Corporation 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 Compaq Computer Corporation 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 Compaq Computer Corporation, 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 the Compaq Computer Corporation standard commercial license and, when
applicable, the rights in DFAR 252.227 7015, "Technical Data--Commercial Items."
1999 Compaq Computer Corporation.
All rights reserved. Printed in U.S.A.
Compaq, DIGITAL, the Compaq and DIGITAL logos are registered with the U.S. Trademark and Patent office.
DIGITAL UNIX, DECconnect, HSZ, StorageWorks, VMS, OpenVMS, are trademarks of Compaq Computer
Corporation.
UNIX is a registered trademark of the Open Group in the US and other countries. Windows NT is a registered
trademark of the Microsoft Corporation. Sun is a registered trademark of Sun Microsystems, Inc. Hewlett-Packard
and HPUX 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 Gert der Funkstrgrenzwertklasse A. In Wohnbereichen knnen bei Betrieb dieses Gertes
Rundfunkstrungen auftreten, in welchen Fllen der Benutzer fr entsprechende Gegenmanahmen verantwortlich
ist.
Avertissement!
Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel cet appareil peut provoquer des
brouillages radiolectriques. Dans ce cas, il peut tre demand l' utilisateur de prendre les mesures appropries.
iii
Contents
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Electrostatic Discharge Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
VHDCI Cable Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Local-Connection Maintenance Port Precautions . . . . . . . . . . . . . . . . . . . viii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Special Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Command Line Interpreter
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Command Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Entering CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
CLI Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
ADD CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
ADD DISK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
ADD MIRRORSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
ADD PASSTHROUGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
ADD RAIDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
ADD SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
ADD STRIPESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
ADD UNIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
CLEAR_ERRORS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
CLEAR_ERRORS controller INVALID_CACHE . . . . . . . . . . . . . . . . . . .31
CLEAR_ERRORS unit-number LOST_DATA . . . . . . . . . . . . . . . . . . . . . .33
CLEAR_ERRORS UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
CLEAR_ERRORS unit-number UNWRITEABLE_DATA . . . . . . . . . . . .36
CREATE_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
iv CLI Reference Manual
DELETE container-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DELETE FAILEDSET disk-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
DELETE SPARESET disk-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DELETE unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
DESTROY_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7
INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 0
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3
RESTART controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
RETRY_ERRORS UNWRITEABLE_DATA . . . . . . . . . . . . . . . . . . . . . . 66
RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7
SELFTEST controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
SET controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SET device-name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
SET EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SET FAILEDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
SET FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
SET mirrorset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
SET MULTIBUS_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
SET NOFAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
SET RAIDset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
SET unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
S HOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SHUTDOWN controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
UNMIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Glossary
Index
v
Tables
Table 1 Recall and Edit Command Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Table 2 ADD UNIT Switches for New Containers . . . . . . . . . . . . . . . . . . . . . .25
Table 3 SET controller Switches (ALLOCATION_CLASS) . . . . . . . . . . . . .71
Table 4 SET controller Switches (CACHE_FLUSH_TIMER) . . . . . . . . . . . .72
Table 5 SET controller Switches (CACHE_UPS) . . . . . . . . . . . . . . . . . . . . . . .73
Table 6 SET controller Switches (COMMAND_CONSOLE_LUN) . . . . . . .73
Table 7 SET controller Switches (HOST_FUNCTION) . . . . . . . . . . . . . . . .74
Table 8 SET controller Switches (ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Table 9 SET controller Switches (INITIAL_CONFIGURATION) . . . . . . . . . .76
Table 10 SET controller Switches (MIRRORED_CACHE) . . . . . . . . . . . . . . .77
Table 11 SET controller Switches (PREFERRED_ID) . . . . . . . . . . . . . . . . . . .78
Table 12 SET controller Switches (PROMPT) . . . . . . . . . . . . . . . . . . . . . . . . .79
Table 13 SET controller Switches (TERMINAL_PARITY) . . . . . . . . . . . . . . . .79
Table 14 SET controller Switches (TERMINAL_SPEED) . . . . . . . . . . . . . . . .79
Table 15 SET controller Switches (TIME) . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Table 16 SET controller Switches (TRANSFER_RATE_REQUESTED) . . . . . .80
Table 17 EMU Set Point Temperatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Table 18 SET UNIT Switches for Existing Containers . . . . . . . . . . . . . . . . . .104
vii
Preface
This book provides information and guidance for operating the command line
interface (CLI) for the HSZ70 Array Controller running HSOF V7.3. 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.
Precautions
Use the precautions described in the following paragraphs when you are carrying
out any servicing procedures:
s Electrostatic Discharge Precautions, page vii
s VHDCI Cable Precautions, page viii
s Local-Connection Maintenance Port Precautions, page viii
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:
s 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.
s 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.
s Always keep circuit boards and components away from nonconducting
material.
viii CLI Reference Manual
s Always keep clothing away from circuit boards and components.
s Always use antistatic bags and grounding mats for storing circuit
boards or components during replacement procedures.
s 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.
s Do not touch the connector pins of a cable when it is attached to a
component or host.
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:
s Clean the mating surfaces with a blast of clean air.
s 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.
s Test the assembly by gently pulling on the cable, which should not
produce visible separation.
Local-Connection Maintenance Port Precautions
The local-connection maintenance 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.
Conventions
This book adheres to the typographical conventions and special notices
found in the paragraphs that follow to help you find what you're
looking for.
ix
Typographical Conventions
Convention Meanin g
Command syntax that must be entered exactly as
ALLCAPS BOLD
shown, for example:
S E T FAILOVER COPY=OTHER_CONTROLLER
ALLCAPS Command syntax discussed within text, for example:
"Use the SHOW SPARESET command to show the
contents of the spareset."
Monospaced Screen display.
Sans serif italic Command variable or numeric value that you supply,
for example: SHOW RAIDset-name (when being
described within the text) or
set this_controller id=(n,n,n,n,) when showing how to
enter the command syntax.
italic Reference to other books, for example: "See HSZ70
Array Controller HSOF Version 7.3 Configuration
Manual for details."
Indicates that a portion of an example or figure has
been omitted, for example:
. A D D RAIDSET RAID1 DISK10000 DISK20000
I N I T I A L I Z E RAID1
S H O W RAID1
"this controller" The controller in a dual-redundant pair serving your
current CLI session through a locally-connected
maintenance (remote) terminal.
"other controller" The controller in a dual-redundant pair that is not
connected to the maintenance (remote) terminal.
x CLI Reference Manual
Special Notices
This book does not 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.
In addition, there are two other notices to aid you in your understanding
of the subject matter being read:
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.
Required Tools
The following tools are needed for servicing the controller, cache
module, and external cache battery:
s A small screwdriver for loosening and tightening the cable-
retaining screws.
s An antistatic wrist strap.
s An antistatic mat on which to place modules during servicing.
s An SBB Extractor for removing StorageWorks building blocks.
This tool is not required, but it will enable you to provide more
efficient service.
xi
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.3 EKCLI70RM. A01
CLI Reference Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70CG. A01
Configuration Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70SV. A01
Service Manual
SPD xx.xx. 00
HSZ70 Family Array Controller Operating
Software (HSOF) Version 7.3 Software
Product Description
Getting StartedHSZ70 Solutions Software AAR60xxTE. A01
Version 7.3 for...platform
Polycenter Console Manager See the Getting
Started guide for the
platform-specific
order number
StorageWorks Array Controller HSZ70 Array EKHSZ70RN. A01
Controller Operating Software HSOF Version
7.3 Release Notes
StorageWorks Getting Started with Command AAR0HJCTE
Console, Version 2.0
EKSW600UG
DIGITAL StorageWorks Ultra SCSI RAID
Cabinet Subsystem (SW600) Installation and
User's Guide
DIGITAL StorageWorks Ultra SCSI RAID EKBA370UG
Enclosure (BA370-Series) User's Guide
The RAIDBOOK--A Source for RAID RAID Advisory
Technology Board
xii CLI Reference Manual
Revision History
The current revisions of this document include:
EK-CLI70-RM.B01 HSOF V7.3 January 1999
EK-CLI70-RM.A01 HSOF V7.0 July 1997
CLI Commands 1
Command Line Interpreter
This section of the HSZ70 Array Controller CLI Reference Manual
describes the command line interpreter (CLI):
s "Introduction," page 2
s "Using the CLI," page 2
"Command Overview," page 3
"Getting Help," page 4
"Entering CLI Commands," page 4
"Command Syntax," page 6
s "CLI Command Descriptions," page 6
"ADD" commands, pages 7--29
"CLEAR" commands, pages 30--34
"CREATE_PARTITION," page 37
"DELETE" commands, pages 37--40
"DESTROY_PARTITION," page 44
"DIRECTORY," page 46
"HELP," page 47
"INITIALIZE," page 49
"LOCATE," page 54
"MIRROR," page 57
"REDUCE," page 60
"RENAME," page 63
"RESTART controller," page 64
"RETRY_ERRORS UNWRITEABLE_DATA," page 66
"RUN," page 67
"SELFTEST controller," page 69
"SET commands, pages 62--92
"SHOW," page 109
"SHUTDOWN controller," page 115
"UNMIRROR," page 117
2 CLI Reference Manual
Introduction
The CLI is one of the user interfaces through which you control your
StorageWorks array controller in the StorageWorks subsystem. 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 these CLI commands 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
StorageWorks Command Console (SWCC) GUI is capable of
duplicating most of the functions available within the CLI. The graphic
display form of the GUI provides a user-friendly method of executing
the CLI commands.
Some CLI commands for configuring and viewing the controllers in a
dual-redundant configuration use the relative terms "this controller"
and "other controller." See "Typographical Conventions," on page ix,
for an explanation of these terms.
Using the CLI
You can access the CLI by connecting a terminal to the maintenance
port in the front bezel of the controller or by using HSZterm software
(remote connection). See the HSZ70 Array Controller HSOF Version
7.3 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 Maintenance Port Precautions,"
on page viii, explains precautions you should observe when operating
the CLI through a local connection port.
CLI Commands Command Overview 3
Command Overview
CLI commands consist of six basic types as shown in the following
table:
Command Type Description
Controller Configures:
s Controller SCSI ID numbers,
s Maintenance terminal characteristics,
s CLI prompts, and so forth.
Controller commands are also used to shut
down and restart the controller.
Device Creates and configures containers made
from physical devices attached to the
controller.
Storageset Creates and configures complex containers
made from groups of device containers.
There are four basic types of storagesets:
s Stripesets
s RAIDsets
s Striped-mirrorsets
s Mirrorsets.
Storageset commands group device
containers together and allow them to be
handled as single units.
Logical Unit Creates and optimizes access to logical
units made from containers.
Failover Configures the controllers in a dual-
redundant pair to operate in one of two
failover modes:
s Transparent or
s Multiple-bus failover
while providing support for dual-redundant
configurations.
Diagnostic and Utility Perform general controller support
functions
4 Getting Help CLI Reference Manual
Getting Help
Help for using the CLI is at your fingertips. Enter "help" whenever the
prompt is displayed for an overview of the CLI help system. For help
with 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:
S E T THIS_CONTROLLER ?
See the HELP command on page 47 for further information.
Entering CLI Commands
Use the following tips and techniques when entering CLI commands:
s Commands are not case sensitive.
s For most commands, you only need to enter enough of the
command to make the command unique. For example, SHO is the
same as entering SHOW.
s 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.
Note Due to space limitations, some examples in this manual contain
commands which exceed one line in length. In such instances, the
paragraph preceding the example identifies 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 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 Commands Entering CLI Commands 5
Table 1 Recall and Edit Command Keys
Key Function
Up Arrow () or Ctrl/B, Steps backward and forward through
Down Arrow () or Ctrl/N the four most recent CLI commands.
Left arrow () or Ctrl/D, Moves the cursor left or right in a
Right arrow () or Ctrl/F command line.
Ctrl/E Moves the cursor to the end of the line.
Ctrl/H or Backspace Moves the cursor to the start 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:
s Insert mode (default)--allows you
to insert characters at the cursor
location, moving the existing
characters to the right.
s 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 (helpful if the system issues a
message interrupting your typing).
6 Command Syntax CLI Reference Manual
Command Syntax
CLI Commands to the controller use the following structure:
COMMAND parameter SWITCHES
where,
s COMMAND = a word or phrase expressed as a verb used to
instruct the controller what to do. Every CLI command begins with
a command. This manual represents commands in upper-case form.
s parameter = one or more 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 lower-case italicized form.
s 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.
CLI Command Descriptions
This section contains the descriptions of the 30 available CLI
commands used with HSOF V7.3. Each command is described using
the following format:
s Command name/brief description
s Syntax needed to enable command
s Parameters needed (if any) to further specify the command
s Switches needed (if any) to modify the command
s Example(s) to illustrate the command usage
s "See Also" section to cross-reference to others with similar usage
CLI Commands ADD CDROM 7
ADD CDROM
Places a CD-ROM device into 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
(JBOD).
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.3 Configuration
Manual for an explanation of the PTL addressing naming format.
Note See the HSZ70 Array Controller HSOF Version 7.3
Release Notes to confirm the compact disc device you are
planning to use is compatible with the controller.
Switches
None.
Example
This example shows how to add a CD-ROM with a device name of
CD_PLAYER (located at port 1, target 8, LUN 0):
A D D CDROM CD_PLAYER 1 8 0
8 ADD CDROM CLI Reference Manual
See also
ADD UNIT
DELETE container-name
SHOW CDROM
SHOW DEVICES
CLI Commands ADD DISK 9
ADD DISK
Places a disk drive into the controller 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 (JBOD).
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 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 disk drive and its SCSI
location in an intuitive manner.
SCSI-port-location
Indicates the PTL address of the disk device. See "CLI Command
Descriptions," on page 6 for an explanation of the PTL
addressing naming format.
Note See the HSZ70 Array Controller HSOF Version 7.3
Release Notes to confirm the disk drive you are planning to use is
compatible with the controller.
Switches
NOTRANSPORTABLE (Default)
TRANSPORTABLE
The transportable/notransportable switch indicates whether a disk
drive can be accessed exclusively by StorageWorks controllers:
10 ADD DISK CLI Reference Manual
s NOTRANSPORTABLE --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.
If the NOTRANSPORTABLE switch is specified and there is no
metadata on the unit, the unit must be initialized.
s 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.
Note It is recommended that 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
This switch 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 cable lengths
between the controllers and the device, such as with a tape library.
Examples
1. This example shows how to add disk number 10000 to port 1, target 0,
and LUN 0:
A D D DISK DISK10000 1 0 0
2. This example shows how to add disk number 40200 as a transportable
disk drive to port 4, target 2, LUN 0:
ADD DISK DISK40200 4 2 0 TRANSPORTABLE
CLI Commands ADD DISK 11
3. This example shows how to add disk number 30200 as non-
transportable device to port 3, target 2, LUN 0, and set the data transfer
rate to 10 MHz (enter the 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
12 ADD MIRRORSET CLI Reference Manual
ADD MIRRORSET
Creates 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-name2 ...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:
s COPY=FAST--use when you want the creation of mirrored
data 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 Commands ADD MIRRORSET 13
s COPY=NORMAL--use 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:
s POLICY=BEST_FIT --use when choosing 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.
s POLICY=BEST_PERFORMANCE--use when choosing 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.
s NOPOLICY --use 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 mirrorset-name,"
Table 16 on page 91).
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:
14 ADD MIRRORSET CLI Reference Manual
s READ_SOURCE=disk-name--use to specify a storageset
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.
s READ_SOURCE=LEAST_BUSY--use to direct read requests
to the mirrorset member with the least amount of work in its
queue.
s READ_SOURCE=ROUND_ROBIN--use to sequentially
direct read requests to each mirrorset member. The controller
equally queries all normal members for each read request.
Examples
1. This example shows how to add disk numbers 10000, 20100, and 30200
as a mirrorset using the name MIRR1:
A DD DISK DISK10000 1 0 0
A DD DISK DISK20100 2 1 0
A DD DISK DISK30200 3 2 0
A DD MIRRORSET MIRR1 DISK10000 DISK20100 DISK30200
2. This example creates a host-addressable unit after the mirrorset MIRR1
has been created:
I N I T I A L I Z E MIRR1
A D D UNIT D305 MIRR1
See also
ADD DISK
ADD UNIT
DELETE container-name
INITIALIZE
MIRROR
REDUCE
SHOW mirrorset-name
SHOW MIRRORSETS
SHOW STORAGESETS
UNMIRR OR
CLI Commands ADD PASSTHROUGH 15
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.
Note Pass-through devices may not be added to a storage subsystem
which is configured in multiple-bus failover mode.
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.
16 ADD PASSTHROUGH CLI Reference Manual
SCSI-port-location
Indicates the PTL address of the passthrough device. See "CLI
Command Descriptions," on page 6 for an explanation of the
PTL addressing naming format.
Note See the HSZ70 Array Controller HSOF Version 7.3
Release Notes to confirm the passthrough device you are
planning to use is compatible with the controller.
Switches
TRANSFER_RATE_REQUESTED=ASYNCHRONOUS
TRANSFER_RATE_REQUESTED=20MHZ (Default)
TRANSFER_RATE_REQUESTED=10MHZ
TRANSFER_RATE_REQUESTED=5MHZ
This switch specifies the maximum data transfer rate for the
controller to use in communicating with the device. For example,
the transfer rate may need to be limited to accommodate long cable
lengths between the controller and the device, such as with a tape
library. The transfer rate is negotiated immediately and does not
require a restart in order to take effect.
Example
This example shows how to add tape device number 20300 to port 2,
target 3, LUN 0:
A D D PASSTHROUGH TAPE20300 2 3 0
A D D UNIT P100 TAPE20300
See also
ADD UNIT
DELETE container-name
SHOW DEVICES
SHOW PASSTHROUGH
SHOW passthrough-name
CLI Commands ADD RAIDSET 17
ADD RAIDSET
Creates a RAIDset and adds the RAIDset to the controller
configuration. StorageWorks 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 container-
name 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 ...container-
nameN
Specifies the disks making up the RAIDset.
18 ADD RAIDSET CLI Reference Manual
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:
s POLICY=BEST_FIT--use when choosing 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.
s POLICY=BEST_PERFORMANCE--use when choosing 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.
s NOPOLICY--use 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 RAIDset-
name," Table 16 on page 101, 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:
s RECONSTRUCT=FAST--use to allow the reconstruct process
to take precedence over other controller operations. When this
switch is specified, the controller uses more resources to
perform the reconstruction. Reconstruction takes less time, but
overall controller performance is reduced during
reconstruction
CLI Commands ADD RAIDSET 19
s RECONSTRUCT=NORMAL--use 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.
REDUCED
NOREDUCED (Default)
The reduced/noreduced switch permits the addition of a RAIDset
missing a member:
s REDUCED--use when you add a RAIDset missing a member.
s NOREDUCED--use when all RAIDset members making
up the RAIDset are present--for instance, when creating a
new RAIDset.
Note Verify the RAIDset contains at least two disk drives
before specifying the REDUCED switch.
Examples
1. This example shows how to create a RAIDset named RAID9 containing
disks numbers 10000, 20100, and 30200:
A DD DISK DISK10000 1 0 0
A DD DISK DISK20100 2 1 0
A DD DISK DISK30200 3 2 0
A DD RAIDSET RAID9 DISK10000 DISK20100 DISK30200
2. This example shows how to create a RAIDset named RAID8 containing
disks numbers 10000, 20100, and 30200, and using the BEST_FIT
switch to indicate the replacement policy (enter the ADD RAIDSET
command on one line):
A D D DISK DISK10000 1 0 0
A D D DISK DISK20100 2 1 0
A D D DISK DISK30200 3 2 0
A D D RAIDSET RAID8 DISK10000 DISK20100 DISK30200
POLICY=BEST_FIT
20 ADD RAIDSET CLI Reference Manual
3. This example creates RAIDset named RAID8, and then creates a host-
addressable unit:
I N I T I A L I Z E RAID8
A D D UNIT D304 RAID8
4. 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:
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
Caution Data contained on the RAIDset is erased if you reinitialize
the RAIDset.
See also
ADD UNIT
DELETE container-name
SET RAIDSET
SHOW RAIDSET
SHOW RAIDset-name
SHOW STORAGESETS
INITITALIZE
CLI Commands ADD SPARESET 21
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.
Switches
None.
Example
This example shows how to add disks numbered 20200 and 30300 to a
spareset:
A DD DISK DISK20200 2 2 0
A DD DISK DISK30300 3 3 0
A DD SPARESET DISK20200
A DD SPARESET DISK30300
See also
DELETE SPARESET
SET FAILEDSET
SHOW SPARESET
SHOW STORAGESETS
22 ADD STRIPESET CLI Reference Manual
ADD STRIPESET
Creates a stripeset and adds it to the controller configuration. Stripesets
are sometimes referred to as RAID level 0 storagesets. The number of
members in the stripeset is determined by the number of container-
name parameters specified. Specify 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.
Switches
None.
CLI Commands ADD STRIPESET 23
Examples
1. This example shows how to create a stripeset named STRIPE1 with
three disks numbered 10000, 20100, and 30200:
A DD DISK DISK10000 1 0 0
A DD DISK DISK20100 2 1 0
A DD DISK DISK30200 3 2 0
A DD STRIPESET STRIPE1 DISK10000 DISK20100 DISK30200
2. This example show how to create a stripeset named STRIPE1 and then
create a logical unit from it:
I N I T I A L I Z E STRIPE1
A D D UNIT D403 STRIPE1
3. 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.
A D D DISK DISK10000 1 0 0
A D D DISK DISK20100 2 1 0
A D D DISK DISK30200 3 2 0
A D D DISK DISK40300 4 3 0
A D D MIRRORSET MR1 DISK10000 DISK20100
A D D MIRRORSET MR2 DISK30200 DISK40300
A D D STRIPESET STRIPE1 MR1 MR2
I N I T I A L I Z E STRIPE1
A D D UNIT D304 STRIPE1
See also
ADD UNIT
ADD MIRRORSET
DELETE container-name
INITIALIZE
SHOW STORAGESET
SHOW STRIPESET
SHOW stripeset-name
24 ADD UNIT CLI Reference Manual
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.
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.
CLI Commands ADD UNIT 25
Table 2 ADD UNIT Switches for New Containers
Non-Transportable Disk
Container Type
Transportable Disk
Passthrough
CD-ROM
Mirrorset
RAIDset
Stripeset
Partition
Switch
ACCESS_ID=ALL
ACCESS_ID=unit identification
PARTITION=partition-number
MAXIMUM_CACHED_TRANSFER
PREFERRED_PATH
NOPREFERRED_PATH
READ_CACHE
NOREAD_CACHE
RUN
N OR UN
WRITE_PROTECT
NOWRITE_PROTECT
WRITEBACK_CACHE
NOWRITEBACK_CACHE
ACCESS_ID=ALL (Default)
ACCESS_ID=unit identification
Grants exclusive unit access privileges to the host:
s ACCESS_ID=ALL--Use to allow any host to access the unit.
s ACCESS_ID=unit identification--Used to permit only the
specified initiator target ID to read from or write to the unit.
When used, the access ID number must be set to the initiator
SCSI ID number used by the host to communicate with the
controller.
26 ADD UNIT CLI Reference Manual
Note 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
The partition switch identifies the unit number for a partition on a
container. The partition_number identifies the partition associated
with the unit number being added. Use the SHOW container_name
command to find the partition numbers used by the storageset or a
single-disk unit.
Note Partitions must have the same target ID number and 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.
Note Regardless of the storageset type, the RUN and NORUN
switches cannot be specified for partitioned units.
PREFERRED_PATH=OTHER_CONTROLLER
PREFERRED_PATH=THIS_CONTROLLER
NOPREFERRED_PATH (Default)
This switch 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.
CLI Commands ADD UNIT 27
Note If your controllers are configured to operate in
transparent failover 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 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.3 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
The READ_CACHE switch is used to set the controller 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, read caching may not be
necessary (under certain conditions) since only a small amount of
data is cached (such as when performing a backup). 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:
s RUN--use to make a unit available to the host.
28 ADD UNIT CLI Reference Manual
s NORUN --use 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.
Note Do not specify the RUN and NORUN switches for
partitioned storagesets.
WRITE_PROTECT
NOWRITE_PROTECT (Default)
Instructs the controller whether data contained on the unit can be
overwritten:
s WRITE_PROTECT--use to prevent the host from writing data
to the unit. The controller may still write to a write-protected
RAIDset to complete a reconstruct operation and metadata,
reconstruct data, and copy data is still written to
RAIDsets and mirrorsets.
s NOWRITE_PROTECT--use 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:
s WRITEBACK_CACHE--use for all new units you want to take
advantage of the controller write-back caching feature.
s NOWRITEBACK_CACHE--use 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.
CLI Commands ADD UNIT 29
Examples
1. This example shows how to create unit D102 from a disk numbered
10000 and sets the host access to the unit through "this controller":
A D D DISK DISK10000 1 0 0
I N I T I A L I Z E DISK10000
A D D UNIT D102 DISK10000
PREFERRED_PATH=THIS_CONTROLLER
2. This example shows how to create unit D107 from a RAIDset named
RAID9 and instructs the unit to take advantage of the controller's write-
back caching feature.
A D D DISK DISK10100 1 1 0
A D D DISK DISK20100 2 1 0
A D D DISK DISK30100 3 1 0
A D D DISK DISK40100 4 1 0
A D D RAIDSET RAID9 DISK10100 DISK20100 DISK30100
DISK40100
I N I T I A L I Z E RAID9
A D D UNIT D107 RAID9 WRITEBACK_CACHE
See also
CREATE_PARTITION
DELETE unit-number
SET unit-number
SHOW UNITS
30 CLEAR_ERRORS CLI CLI Reference Manual
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
Parameters
None.
Switches
None.
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
C L E A R _ E R R O R S CLI
See also
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA
CLI Commands CLEAR_ERRORS controller INVALID_CACHE 31
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 in the following situations:
s When the controller or cache modules have been replaced,
resulting in mismatched data between the controllers.
s 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
Note 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.
Switches
DATA-RETENTION-POLICY
This parameter instructs the controller on how to handle write-back
cached data:
s NODESTROY_UNFLUSHED_DATA
s DESTROY_UNFLUSHED_DATA
NODESTROY_UNFLUSHED_DATA (default)
DESTROY_UNFLUSHED_DATA
32 CLEAR_ERRORS controller INVALID_CACHE CLI Reference Manual
s NODESTROY_UNFLUSHED_DATA--use to retain the cached
data and discard controller information 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.
s DESTROY_UNFLUSHED_DATA--use to retain the controller
information and discard the cached data in the following
situations:
If the cache module has been replaced.
Any other reason not listed above.
Specifying the DESTROY_UNFLUSHED_DATA switch
Caution
destroys data remaining in cache, which can result in the possible
loss of data.
Examples
1. 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.
C L E A R _ E R R O R S THIS_CONTROLLER INVALID_CACHE
NODESTROY_UNFLUSHED_DATA
2. 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.
C L E A R _ E R R O R S OTHER_CONTROLLER INVALID_CACHE
DESTROY_UNFLUSHED_DATA
See also
CLEAR_ERRORS CLI
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA
CLI Commands CLEAR_ERRORS unit-number LOST_DATA 33
CLEAR_ERRORS unit-number LOST_DATA
Clears lost data errors on a selected unit (all partitions on the unit's
container are effected).
The controller reports a lost data error on the unit when:
s You remove a write-back cache module, or
s When the cache module contains unflushed data.
These conditions may exist possibly due to an interruption in the
primary power source and no backup power is present. The
CLEAR_ERRORS LOST_DATA command clears the lost data error
| ed-write-ba
EK-CLI70-RM
|
