HSG60/HSG80 Array Controller ACS Version 8.5
CLI Reference Guide
Second Edition (May 2000)
Part Number: EKHSG85RG. B01
Compaq Computer Corporation
Notice
2000 Compaq Computer Corporation.
COMPAQ, the Compaq logo, and StorageWorks Registered in U. S. Patent and Trademark Office.
OpenVMS and Tru64 are trademarks and/or service marks of Compaq Information Technologies Group,
L.P.
Microsoft, MS-DOS, Windows, Windows NT, Windows 95, Windows 98 and Windows 2000 are
trademarks of Microsoft Corporation.
UNIX is a trademark of The Open Group.
All other product names mentioned herein may be trademarks or registered trademarks of their respective
companies.
Confidential computer software. Valid license from Compaq required for possession, use or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license. [use this DFAR statement for software products as required]
Com paq shall not be liable for technical or editorial errors or omissions contained herein. The
information in this document is subject to change without notice.
The information in this publication is subject to change without notice and is provided "AS IS"
WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF
THIS INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE
FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER
DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF
BUSINESS PROFITS, BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION),
EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE
FOREGOING SHALL APPLY REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF
EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS IN CONTRACT,
NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGAL LIABILITY, AND
NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
The limited warranties for Compaq products are exclusively set forth in the documentation accompanying
such products. Nothing herein should be construed as constituting a further or additional warranty.
Printed in the U.S.A.
HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Second Edition May 2000
Part Number EKHSG85RG. B01
Contents
About This Guide
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Special Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1
CLI Command Introduction
CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Command Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Controller Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Device Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Storageset Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Partition Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Unit Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Diagnostic and Utility Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Data Replication Manager (DRM) commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Entering CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
iv HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Chapter 2
CLI Command Descriptions
CLI Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
ADD ASSOCIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ADD CONCATSETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
ADD CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ADD DISK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
ADD MIRRORSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
ADD RAIDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
ADD REMOTE_COPY_SETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
ADD SNAPSHOT_UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
ADD SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
ADD STRIPESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
ADD UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CLEAR_ERRORS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CLEAR_ERRORS this_controller INVALID_CACHE . . . . . . . . . . . . . . . . . . . . . . . . . . 235
CLEAR_ERRORS device-name UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CLEAR_ERRORS unit-number LOST_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CLEAR_ERRORS unit-number UNWRITEABLE_DATA . . . . . . . . . . . . . . . . . . . . . . . . 240
CONFIGURATION RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CONFIGURATION RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
CONFIGURATION SAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
CREATE_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
DELETE associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
DELETE concatsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
DELETE connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
DELETE remote copy sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
DELETE container-name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
DELETE FAILEDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
DELETE SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
DELETE unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
DESTROY_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
POWEROFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
RESTART this_controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Contents v
RETRY_ERRORS unit-number UNWRITEABLE_DATA . . . . . . . . . . . . . . . . . . . . . . . 283
RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
SELFTEST this_controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
SET associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
SET concatsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
SET connection-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
SET controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
SET device-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
SET EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
SET FAILEDSET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2101
SET FAILOVER COPY=this_controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
SET mirrorset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
SET MULTIBUS_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2109
SET NOFAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
SET RAIDset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
SET remote-copy-set-names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116
SET this_controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2119
SET unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128
SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
SHUTDOWN this_controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2140
SITE_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2142
UNMIRRO R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143
Glossary
Index
vi HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Tables
Table 11 Recall and Edit Command Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 21 ADD UNIT Switches for New Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Table 22 POWEROFF Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Table 23 EMU Set Point Temperatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2100
Table 24 SET UNIT Switches for Existing Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128
About This Guide
This book describes the Command Line Interpreter (CLI) of the HSG80 Array Controller
running Array Controller Software (ACS) 8.5. In the description of the CLI commands,
the syntax, parameters, and switches to the command are also described.
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.
Conventions
This book uses the following special notices and typographical conventions to help you
find what you are looking for.
viii HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
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 are carrying out the procedures in this book.
WARNING: A Warning contains information essential to people's safety. It advises
users that failure to take or avoid a specific action could result in physical harm to the
user or hardware. Use a warning, not a caution, when such damage is possible.
CAUTION: A Caution contains information that the user needs to know to avoid
damaging the software or hardware.
IMPORTANT: An important note is a type of note that provides information essential to the
completion of a task. Users can disregard information in a note and still complete a task, but
they should not disregard an important note.
NOTE: A note indicates neutral or positive information that emphasizes or supplements
important points of the main text. A note supplies information that may apply only in special
cases--for example, memory limitations, equipment configurations, or details that apply to
specific versions of a program.
About This Guide ix
Typographical Conventions
C onvention Meaning
ALLCAPS BOLD Command syntax that must be entered exactly as shown, for example:
SET FAILOVER COPY=OTHER
Command syntax that is discussed within text, for example:
ALLCAPS
"Use the SHOW SPARESET command to show the contents of the spareset."
MONOSPACED ALL SCREEN DISPLAYS ARE IN UPPER-CASED MONOSPACED
FONT.
Sans serif italic Command variable or numeric value that you supply, for example: SHOW
Sans serif italic RAIDset-name or
SET THIS_CONTROLLER ID=(n,n,n,n,)
Reference to other books, for example: "See the HSJ80 Array Controller
italic
Configuration Guide for details."
Typographical Conventions Continued...
. Indicates that a portion of an example or figure has been omitted.
The controller serving your current CLI session through a local or remote terminal.
"this controller"
The controller in a dual-redundant pair that's connected to the controller serving
"other controller"
your current CLI session.
x HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Related Publications
The following table lists some of the documents related to the use of the controller, cache
module, and external cache battery.
Table 1 Relevant Publications
Document Title Part Number
Compaq StorageWorks HSG60/HSG80 Array Controller ACS EKH SG84SV. D01
Version 8.5 Maintenance and Service Guide
Compaq StorageWorks Command Console v2.3 User Guide AARFA2FTE
Compaq StorageWorks Command Console v2.3 for MA6000 User AARMBDATE
Guide
Compaq StorageWorks UltraSCSI RAID Enclosure (BA370-Series) EKBA370UG. C02
User Guide
Compaq StorageWorks Model 2100 and Model 2200 UltraSCSI EK-SE2C8-UA. B01
Controller Enclosure User Guide
Compaq StorageWorks Enclosures Model 4200 Family Ultra2 LVD EK-SWLVD-UA. A01
Disk Enclosures User Guide
Compaq StorageWorks Fibre Channel Storage Switch Service AARHBZATE
Guide
Compaq StorageWorks Fibre Channel Storage Switch User Guide AARHBYATE
Compaq StorageWorks Fibre Channel Switch Quick Setup Guide AARH C0ATE
Compaq StorageWorks Fibre Channel Arbitrated Loop Hub EKDHGGAUG
(DS-DHGGA-CA) User Guide
Compaq StorageWorks KGPSA PCI-to-Fibre Channel Host EKKGPSAUG
Adapter User Guide
The RAIDBOOK--A Source Book for Disk Array Technology RAID Advisory Board:
I.S.B.N 1-879936-90-9
Revision History
First Release: October 1999
First Revision: May 2000
1
Chapter
CLI Command Introduction
This guide contains descriptions of the command line interpreter (CLI) commands you
can use to interact with the controller. This interaction can be by way of:
I A local terminal connected to the maintenance port of the controller
I A remote connection by way of the host system terminal
I The CLI window of StorageWorks Command Console (SWCC)
This section is divided into an overview and a command description. The overview
provides a general description of the CLI interface and how to use it. The command
description contains the description, full syntax, and examples of the use of each
command available on the CLI interface.
CLI Overview
The CLI is the most direct interface to the controller. The CLI commands allow you to
manage the subsystem by viewing and modifying the configuration of the controller and
its attached storage devices. 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 also available. This GUI is called StorageWorks Command Console, or
SWCC. SWCC replicates most of the functions available within the CLI in graphic form
and provides a graphical method of configuring and monitoring the controller. In addition
to the graphical interface, SWCC has a CLI window through which CLI commands can be
entered.
12 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
CLI commands for configuring and viewing the controllers use the relative terms "this
controller" and "other controller." See "Typographical Conventions," page ix, for an
explanation of these terms.
Using the CLI
You can access the CLI through the following methods:
I By connecting a local terminal/PC to the maintenance port on the front of the
controller.
I Using the DUP utility from the system terminal you may also enable a remote
connection to the controller. After you have initially configured the controller, and
made it visible to the host, you can perform other configuration tasks through this
remote connection.
I Using the SWCC by way of a PC setup on the subsystem. The SWCC can be used to
perform most of the CLI commands that the local terminal can.
Command Overview
CLI commands are divided into categories based on what options or structures they
control. The following is a list of the command categories:
I Controller Commands--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.
I Device Commands--Create and configure containers made from physical devices
attached to the controller.
I Storageset Commands--Create and configure complex containers made from groups
of device containers. There are four basic types of storagesets: stripesets, RAIDsets,
striped-mirrorsets, and mirrorsets. Storageset commands group device containers
together and allow them to be handled as single units.
I Logical Unit Commands--Create and optimize access to logical units made from any
container type.
I Failover Commands--Configure a pair of controllers to operate in either transparent
failover mode or multiple-bus failover mode.
I Diagnostic and Utility Commands--Perform general controller support functions.
I Data Replication Manager Commands--Work only in a remote copy environment
and require V8.5P code.
CLI Overview 1 3
Controller Commands
CLI Controller commands fall into two categories:
I General commands
I Failover commands
The CLI commands that pertain to the controllers in a general way are as follows:
I CLEA R_ERRO RS
CLI
INVALID_CACH E
I Configuration
RESET
RESTORE
SAVE
I EXIT
I HELP
I POWEROF F
I RESTART
I SELFTEST
I SET
I SHOW
CLI Commands that control the failover mode of a controller pair are:
I SET FAILOVER
I SET NOFAILOVER
Device Commands
Device commands fall into two categories:
I General commands
I Spareset/failedset commands
CLI Commands that allow you to add and configure physical devices in general are:
I ADD DISK
I CLEA R_ERRO RS
14 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
LOST_DATA
UNKNOWN
UNWRITEABLE_DATA
I DELETE
I INITIALIZE
I LOCATE
I RENAME
I SET
CLI Commands that allow you to change the sparesets/failedsets are:
I ADD SPARESET
I DELETE FAILEDSET
I DELETE SPARESET
I SET FAILEDSET
I SHOW FAILEDSET
Storageset Commands
CLI Commands that pertain to storagesets are:
I ADD MIRRORSET
I ADD RAIDSET
I ADD STRIPESET
I DELETE
I INITIALIZE
I LOCATE
I MIRROR
I REDUCE
I RENAME
I SET
I SHOW
I SHOW MIRRORSETS
I SHOW RAIDSETS
CLI Overview 1 5
I SHOW STRIPESETS
I UNMIRROR
Partition Commands
CLI Commands that pertain to partitions are:
I CREATE_PARTITION
I DESTROY_PARTITION
Unit Commands
CLI commands that pertain to units are:
I ADD CONCATSETS
I DELETE
I LOCATE
I RENAME
I RETRY_ERRORS UNWRITEABLE_DATA
I SET
I SHOW
I SHOW UNITS
I ADD SNAPSHOT_UNITS
Diagnostic and Utility Commands
Commands that pertain to the diagnostics and utilities are:
I DIRECTORY
I RUN
16 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Data Replication Manager (DRM) commands
NOTE: All DRM commands are hidden and inoperative until the controller pair is put into remote
copy mode by specifying the REMOTE_COPY switch of the SET this controller command.
DRM applies only to the HSG80 array controller running ACS Version 8.5P.
ADD ASSOCIATIONS
ADD REMOTE_COPY_SET
DELETE association-set_name
DELETE remote-copy-set-name
SET association-set-name
SET remote-copy-set-name
SITE FAILOVER
SHOW
Getting Help
To get help with using CLI commands, enter HELP at the CLI prompt. The resultant
display shows an overview of the CLI help system. To obtain help with a specific
command or to determine what switches are available with a command, enter as much of
the command syntax 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 ?
Another example: to see what is allowed for a prompt, enter:
SET THIS PROMPT=?
CLI Overview 1 7
Entering CLI Commands
Use the following tips and techniques to aid you in the entering of CLI commands:
I Commands are not case-sensitive.
I 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.
I The controller processes each command in sequence. You can continue entering
subsequent commands while the controller is processing prior commands. A controller
experiencing heavy data I/O may respond slowly to CLI commands.
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 11 lists the keys used to recall
and edit commands.
Table 11 Recall and Edit Command Keys
Key Function
Up Arrow or Ctrl/B, Steps forwards or backward through the four most recent CLI
Down Arrow or Ctrl/N commands
Left arrow or Ctrl/D, Moves the cursor left or right in a command line.
Right arrow or Ctrl/F
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 or F14 Toggles between insert and overstrike mode:
I The default setting is insert mode allowing you to insert
characters at the cursor location (moving the existing
characters to the right).
I Overstrike mode replaces existing characters. The CLI prompt
returns to insert mode at the beginning of each line.
Ctrl/R Recalls the contents of the command line. This is especially helpful
if the system issues a message that interrupts your typing.
18 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Command Syntax
The following structure defines how each command to the controller is used:
COMMAND PARAMETER_NAME=parameter SWITCHES
I COMMAND--A word or phrase that instructs the controller what to do. Commands
are represented in this manual in capitalized form.
I PARAMETER NAME--The name of a parameter, followed by an equal sign and the
parameter variable. If a specific command specifies parameter names, they must be
entered in the command string. Parameter names are represented in this manual in
capitalized form.
I parameter--W hen required in the command, parameters are words or phrases that
supply necessary variables to support the action of the COMMAND. Not all CLI
commands require parameters.
I SWITCHES--An optional word or phrase that modifies the command. Not all CLI
commands use switches. Switches are represented in this manual as capitalized,
italicized text.
2
Chapter
CLI Command Descriptions
This section describes the CLI commands and presents full syntax and examples of the use
of each command.
CLI Command Descriptions
This section contains the descriptions of the available CLI commands used with the ACS
V8.5 software. Each command is described using the following format:
I Command name and brief description
I Syntax needed to enable command
I Parameters needed (if any) to further specify the command
I Switches needed (if any) to modify the command
I Example(s) to illustrate the command usage
I A "See Also" section to cross-reference to other commands with similar usage
22 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD ASSOCIATIONS
NOTE: This command works only in a Data Replication Manager (DRM) environment and
requires an HSG80 array controller with ACS Version 8.5P code. Like all DRM commands, it is
heavily restricted in its use. See Data Replication Manager HSG80 ACS Version 8.5P Operations
Guide for examples of usage.
This command is valid only on the node on which the Initiator resides (where remote copy sets
are configured).
An association set is a group of remote copy sets that shares common attributes. This
command adds a one-member association set (that is, an association set consisting of one
remote copy set) to the controller pair's configuration. Additional remote copy sets can be
added to the association set with the SET associations command.
This command is rejected if the specified remote copy set is unknown to the controller
pair.
Syntax
ADD ASSOCIATIONS association-set-name remote-copy-set-name
Parameters
The following parameters are required for the ADD ASSOCIATIONS command:
I association set name
I remote copy set name
These parameters are described in the following paragraphs.
association-set-name
The name that will be assigned to the association set.
NOTE: Association sets cannot be renamed with the RENAME command. If the wrong name is
entered, the association set must be deleted and then added again.
The association set 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 (_).
remote-copy-set-name
The name of the first member of the association set.
ADD ASSOCIATIONS 23
Switches
There are no switches associated with this command.
Exam ples
To create an association set, AS3, from remote copy sets RSC1 and RSC2, enter:
ADD ASSOCIATIONS AS3 RSC1
SET AS3 ADD=RSC2
See also
ADD REMOTE_COPY_SET
SET associations
24 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD CONCATSETS
CAUTION: This command should only be executed with host operating systems that
support dynamic volume expansion. If the operating system cannot handle one of its
disks increasing in size, use of this command could make data inaccessible.
This command creates a specialized volume, called a concatset (short for concatenation
set), from a storageset that has been given a unit number. Another storageset can then be
added to the concatset by the SET concatset command.
Syntax
ADD CONCATSETS concat-name storageset-name
Parameters
The following parameters are required for the ADD CONCATSETS command:
I concatset-name
I storageset-name
These parameters are described in the following paragraphs.
concatset-name
Assigns a name to the concatenation set, or concatset.
The 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 (_).
storageset-nam e
Designates the first storageset to be a member of the concatset.
Switches
There are no switches associated with this command.
ADD CONCATSETS 25
Examples
To expand the capacity of unit D0, which consists of stripeset Stripe1, by adding another
stripeset, Stripe2, enter:
ADD CONCATSETS C1 STRIPE1
SET C1 ADD=STRIPE2
See also
DELETE concatset-name
SET concatset-name
SHOW CONCATSETS
SHOW concatset-name
26 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD CONNECTIONS
Each path between a Fibre Channel adapter in a host computer and an active host port on a
controller is a connection.
This command adds the specified host connection to the table of known connections. This
table is maintained in the controller's memory. The maximum table length is 64
connections; if the table contains 64 entries, new connections cannot be added unless
some old ones are deleted.
There are two mechanisms for adding a new connection to the table:
1. Physically connecting a host adapter to a controller host port. During Fibre Channel
initialization, the controller becomes aware of the connection and adds it to the table.
This physical discovery of connections occurs at the point when a host adapter is
plugged in to a controller port and after issuing a RESTART command. New
connections discovered through physical connection are assigned a default connection
name by the controller. The default connection name is of the form !NEWCONnn.
NOTE: Certain host conditions, such as a power cycle, that disturb the state of the switched
fabric may cause a connection to reappear in the table. The connection will be assigned a
default connection name.
2. Adding a connection through the ADD CONNECTIONS command.
NOTE: ADD CONNECTIONS will add an entry to the table whether the connection physically
exists or not. The table can be completely filled up with fictitious connections.
Syntax
ADD CONNECTIONS connection_name HOST_ID=host_id ADAPTER_ID=adapter_id
CONTROLLER=controller PORT=port
Parameters
The following parameters are required to the ADD CONNECTIONS command:
I connection name
I host ID
I adapter ID
I controller
ADD CONNECTIONS 27
I port
These parameters are described in the following paragraphs.
connection-name
The name that will be assigned to the host connection. The connection name can be
any character string, with one exception: it cannot be in the form of a default
connection name. The form of a default connection name is !NEWCONnn.
The default connection name is assigned automatically by the controller when the
connection is physically made between a host adapter and a controller port. Default
connection names are assigned only by the controller.
HOST_ID=host_id
HOST_ID is the parameter name for the host_id variable, which is the worldwide
name (WWN) of the host. WWN is a 16-character hexadecimal number. The hyphens
aren't necessary, but are recommended to avoid mistakes in entering the number. The
HOST_ID parameter name must be entered, followed by an equal sign, followed by
the WWN of the host.
For example, to specify a WWN of AAAA-AAAA-AAAA-AAAA, type:
host_id=AAAA-AAAA-AAAA-AAAA
ADAPTER_ID =adapter_id
ADAPTER_ID is the parameter name for the adapter_id variable, which is the
worldwide name (WWN) of the host Fibre Channel adapter. WWN is a 16-character
hexadecimal number. The hyphens aren't necessary, but are recommended to avoid
mistakes in entering the number. The ADAPTER_ID parameter name must be entered,
followed by an equal sign, followed by the WWN of the host bus adapter.
For example, to specify a WWN of FFFF-FFFF-BBBB-9876, type:
adapter_id=FFFF-FFFF-BBBB-9876
NOTE: The worldwide name of the host and adapter are sometimes the same. This is a
characteristic of the adapter.
CONTROLLER=controller
CONTROLLER is the parameter name for the controller variable, which specifies
which controller the host is to connect through. The choices are this_controller, which
can be shortened to this, and other_controller, which can be shortened to other.
28 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
PORT=port
PORT is the parameter name for the port variable, which specifies which host port (1 or 2)
the connection is on.
Switches
The following switches are available with the ADD CONNECTION command:
I unit offset
I operating system
These switches are described in the following paragraphs.
UNIT_O FFSET=n
Offset is a decimal value that establishes the beginning of the range of units that a host
connection can access. It defines and restricts host connection access to a contiguous
group of unit numbers.
In transparent failover mode, host connections on port 1 default to an offset of 0; port 1
connections can see units 0 through 99. Host connections on port 2 default to an offset
of 100; port 2 connections can see units 100 through 199.
In multiple-bus failover mode, the default offset is 0 for all host connections.
NOTE: If a controller pair is switched from transparent failover mode to multiple-bus failover
mode, the unit offsets for transparent mode remain in effect.
The LUN number equals the unit number minus the offset:
LUN number = unit number - offset.
I Logical unit number or LUN number = the logical unit number presented to the
host connection.
I Unit number = the number assigned to the unit in the ADD UNIT command. This
is the number by which the unit is known internally to the controllers.
For example, a system has three host connections, each of which can see 8 LUNs. Each
connection designates its LUNs as 0 through 7. To define for each of these connections a
block of 8 units, set the offset for each connection, as follows:
CLI>SET SERVER1 OFFSET=0
CLI>SET SERVER2 OFFSET=10
CLI>SET SERVER3 OFFSET=120
(It is not necessary to use offsets that are divisible by 10, but it makes things simpler.)
ADD CONNECTIONS 29
The effect of these offset assignments will be as follows:
I Server1 will access units D0 through D7, which it will see as LUNs 0 through 7.
I Server2 will access units D10 through D17, which it will see as LUNs 0 through 7.
I Server3 will access units D120 through D127, which it will see as LUNs 0 through 7.
There is one additional factor to consider when assigning unit numbers and offsets. If the
SCSI_VERSION qualifier of the SET THIS/OTHER CONTROLLER command is set to
SCSI-3, the command console LUN (CCL) is presented as LUN 0 to every connection,
superseding any unit assignments. For more information see the ADD UNIT command.
OPERATING_SYSTEM= OS_name
Specifies the operating system of the host. The OPERATING_SYSTEM switch tailors
the controllers behavior for use with a particular operating system. Enter a question
mark after OPERATING_SYSTEM to see the supported operating systems, as follows:
ADD CONNECTIONS SERVER1 OPERATING_SYSTEM=?
The response for this command is a list of abbreviations for the supported operating
systems.
Exam ples
This example shows how to add an entry for a connection named George to the table of
known connections, with the indicated host and adapter worldwide names, on port 2 of
"this controller."
ADD CONNECTIONS GEORGE HOST_ID=1000-0000-C920-1234
ADAPTER_ID=1000-0000-C920-5678 CONTROLLER=THIS PORT=2
See also
ADD UNIT
DELETE connections
SET connection-name
210 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD DISK
This command names a disk drive and adds it to the controller configuration. This
command is typically used when disk drives are physically added to a previously
configured subsystem. During initial set-up, the entire set of disk drives is customarily
added to the controller's configuration through the CONFIG utility.
Syntax
ADD DISK disk_name port target lun
Parameters
The following parameters are required for the ADD DISK command:
I disk name
I port
I target
I LUN
These parameters are described in the following paragraphs.
container_name
Assigns a name to the disk device. This container name is then used with the ADD
UNIT command to create a logical unit.
The disk 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 (_).
It is common to name a disk drive DISKpttll, where pttll is the disk's Port-Target-LUN
address. Although other naming conventions are acceptable, this one presents the user
with the type of disk drive and its SCSI location.
port
Designates the SCSI device port number, from 1 to 6, on which the disk resides.
target
Designates the SCSI target ID of the disk on the port. Valid device target IDs for single
controller configurations are 0015, excluding ID 7. Valid device target IDs for dual
controller configurations are 0015, excluding IDs 4 through 7.
ADD DISK 211
lun
Indicates the LUN of the disk drive, and is always zero.
The parameters port, target, and lun must be entered with at least one space between them.
Leading zeroes can be excluded.
Switches
The following switches are available with the ADD DISK command:
I transfer rate requested
I transportable/notransportable
These switches are described in the following paragraphs.
TRANSFER_RATE_REQUESTED=ASYNCHRO NOUS
TRANSFER_RATE_REQUESTED=20MHZ (Default)
TRANSFER_RATE_REQUESTED=10MHZ
TRANSFER_RATE_REQUESTED=5MH Z
Specifies the maximum data transfer rate at which the controller is to communicate
with the disk drive. The user might need to limit the transfer rate to accommodate long
cables between the controllers and the device.
TRANSPORTABLE
NOTRANSPORTABLE (Default)
If NOTRANSPORTABLE is specified, the controller makes a small portion of each disk
inaccessible to the host. It uses this restricted space to store administrative information
(metadata) which improves data reliability, error detection, and recovery. This
improvement comes at the expense of transportability, because the metadata is specific
to StorageWorks products.
Transportable disks do not contain metadata or use restricted areas on the media, so
they forfeit any advantages this feature provides. Transportable disks, however, can be
moved to a non-StorageWorks environment with their data intact.
If NOTRANSPORTABLE is specified and there is no valid metadata on the unit, the
unit must be initialized.
NOTE: Avoid using transportable disks unless there is no other way to move the data.
212 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
Exam ples
To add DISK10000 at port 1, target 0, LUN 0, enter:
ADD DISK DISK10000 1 0 0
To add DISK40200 as a transportable drive to port 4, target 2, LUN 0, enter:
ADD DISK DISK40200 4 2 0 TRANSPORTABLE
To add a disk drive named DISK30200 as a non-transportable disk to port 3, target 2, LUN
0 and set the data transfer rate to 10 MHz, enter the following:
ADD DISK DISK30200 3 2 0 NOTRANSPORTABLE TRANSFER_RATE_REQUESTED=10MHZ
See also
ADD UNIT
DELETE container-name
INITIALIZE
LOCATE
SHOW DISKS
SHOW DEVICES
SET container-name
ADD MIRRORSET 213
ADD MIRRORSET
This command creates and names a mirrorset and adds it to the controller configuration.
The capacity of the mirrorset is constrained by its smallest member.
Syntax
ADD MIRRORSET mirrorset-name disk-name1 [disk-nameN]
Parameters
The following parameters are required for the ADD MIRRORSET command:
I mirrorset name
I disk names
These parameters are described in the paragraphs that follow.
mirrorset-name
Assigns a name to the mirrorset container. This is the 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 (_).
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
The following switches are available with the ADD DISK command:
I copy
I policy/nopolicy
I read source
214 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
These switches are described in the following paragraphs.
COPY=FAST
COPY=NORMAL (Default)
Sets the speed at which the controller copies data to a new member from normal
mirrorset members when data is being mirrored to the disk drives of the storageset:
I Specify COPY=FAST to allow the creation of mirrored data to take precedence
over other controller operations. When you specify COPY=FAST, the controller
uses more resources to create the mirrored data, and copying takes less time.
However, overall controller performance is reduced.
I Specify COPY=NORMAL when operations performed by the controller should
take priority over the copy operation. If you specify COPY=NORMAL, creating the
mirrored data has a minimal impact on performance.
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
Sets the selection criteria the controller uses to choose a replacement disk from the
spareset when a mirrorset member fails.
I Specify POLICY=BEST_FIT to choose a replacement disk drive from the spareset
that equals or exceeds the base member size (smallest disk drive at the time the
mirrorset was initialized). If there is more than one disk drive in the spareset that
meets the criteria, the controller selects a disk drive with the best performance.
I Specify POLICY=BEST_PERFORMANCE to allow the software to choose a
replacement disk drive from the spareset with 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 a disk drive that equals or exceeds the base member
size.
I 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 placed
in the mirrorset.
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.
ADD MIRRORSET 215
I 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.
I Specify READ_SOURCE=LEAST_BUSY to direct read requests to the mirrorset
disk with the least amount of work in its queue. If multiple disks have equally short
queues, the controller queries normal disks for each read request as it would when
READ_SOURCE=ROUND_ROBIN is specified.
I Specify READ_SOURCE=ROUND_ROBIN to sequentially direct read requests to
each mirrorset disk. The controller equally queries all normal disks for each read
request.
Exam ples
To create a mirrorset named MIRR1 consisting of disks DISK10000, DISK20100, and
DISK30200, enter:
ADD MIRRORSET MIRR1 DISK10000 DISK20100 DISK30200
See also
ADD DISK
ADD UNIT
DELETE container-name
INITIALIZE
MIRROR
REDUCE
SHOW mirrorset-name
SHOW MIRRORSETS
SHOW STORAGESETS
UNMIRROR
216 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
This co mma nd creates an d names a RAIDs et an d adds the RAIDset to the controller config ura t ion. Compaq RAIDsets are often referred to as RAID level 3 /5 storagesets because they use the best characteris tic s of RAID level 3 and RA ID level 5.
ADD RAIDSET
The capacity of the RAIDset is constrained by its smallest member.
Syntax
ADD RAIDSET RAIDset-name disk-name1 disk-name2 disk-name3 [disk-nameN]
Parameters
The following parameters are available to the ADD RAIDSET command:
I RAID set name
I disk names
These parameters are described in the paragraphs that follow.
RAIDset-name
Assigns a name to the RAIDset. The RAIDset 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 (_).
It is common to name a RAIDset RAIDn, where n is a sequentially assigned, unique
identifier. This naming convention presents the user with the type of container and its
unique identifier.
disk-name1 disk-name2 disk-name3 [disk-nameN]
Identifies the disks making up the RAIDset. RAIDsets must include at least 3 disk
drives, and no more than 14.
Switches
The following switches are available with the ADD RAIDSET command:
I policy/nopolicy
I copy
I reconstruct
I reduced/noreduced
These switches are described in the following paragraphs.
ADD RAIDSET 217
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 RAIDset member fails:
I Specify POLICY=BEST_FIT to choose a replacement disk drive from the spareset
that equals or exceeds the base member size 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 that will provide the best performance.
I 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 a disk drive that equals or exceeds the base member
size of the RAIDset.
I Specify NOPOLICY to prevent the controller from automatically replacing a failed
disk device. This RAIDset operates in a reduced state until you select either
POLICY=BEST_PERFORMANCE or POLICY=BEST_FIT, or manually place a
member in the RAIDset.
RECONSTRUCT=FAST
RECO NSTRUCT=NORMAL (Default)
Sets the speed at which the controller reconstructs data to a new RAIDset disk that
replaces a failed disk:
I 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.
I Specify NORMAL to balance other controller operations with the reconstruct
operation. The controller uses relatively few resources to perform the reconstruct
process: there is little impact on performance.
REDUCED
NOREDUCED (Default)
Permits the addition of a RAIDset missing a member:
I Specify the REDUCED switch when you add a reduced RAIDset (a RAIDset that
is missing one member).
218 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
NOTE: Verify the RAIDset contains all but one of its disks before specifying the REDUCED
switch.
I Specify the NOREDUCED switch when all the disks making up the RAIDset are
present--for instance, when creating a new RAIDset.
Exam ples
To create a RAIDset named RAID9 that contains disks DISK10000, DISK20100, and
DISK30200, enter:
ADD RAIDSET RAID9 DISK10000 DISK20100 DISK30200
To create a RAIDset named RAID8 that contains disks DISK10000, DISK20100,
DISK30200, and uses the BEST_FIT switch to indicate the replacement policy, enter:
ADD RAIDSET RAID8 DISK10000 DISK20100 DISK30200 POLICY=BEST_FIT
NOTE: The ADD RAIDSET command must be entered on one line.
To create a RAIDset named RAID8 that contains disks DISK10000, DISK20100,
DISK30200, then initialize it and make it into a host-addressable unit, enter:
ADD RAIDSET RAID8 DISK10000 DISK20100 DISK30200
INITIALIZE RAID8
ADD UNIT D70 RAID8
To create a three-member RAIDset from the members of a reduced four-member
RAIDset, enter the following (do not initialize the RAIDset again):
CAUTION: Data contained on the RAIDset will be erased if you reinitialize the RAIDset.
ADD RAIDSET RAID6 DISK10300 DISK20400 DISK30200 REDUCED
See also
ADD UNIT
DELETE container-name
SET RAIDSET
SHOW RAIDSET
SHOW RAIDset-name
SHOW STORAGESETS
INITIALIZE
ADD REMOTE_COPY_SETS 219
ADD REMOTE_COPY_SETS
NOTE: This command works only in a Data Replication Manager (DRM) environment and
requires an HSG80 array controller with ACS Version 8.5P code. Like all DRM commands, it is
heavily restricted in its use. See Data Replication Manager HSG80 ACS Version 8.5P Operations
Guide for examples of usage.
This command must only be used on the initiator (local) site.
This command creates a remote copy set (RCS), consisting of one unit at the initiator site
and one unit at the target site. The units may be a single disk (JBOD) or a stripeset,
mirrorset, or RAIDset.
The following restrictions apply to remote copy sets:
I MAXIMUM_CACHE_TRANSFER_SIZE (a switch of the ADD UNIT and SET unit
command) should be set to 1 on target units. For initiator units,
MAXIMUM_CACHE_TRANSFER_SIZE should be set to whatever is optimal for the
application.
I There is a maximum of 12 remote copy sets per initiator/target pair.
I Neither initiator nor target units can be transportable units, concatset units, or snapshot
units.
Syntax
ADD REMOTE_COPY_SETS remote-copy-set-name initiator-unit-name
remote-node-name\target-unit-name
Parameters
The parameters required for this command are:
I remote copy set name
I initiator unit name
I remote node name\target unit name (this parameter is not required; it can be added
later through the SET command)
These parameters are described in the following paragraphs.
220 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
rem ote-copy-set-name
The name by which the remote copy set will be known. This name must be unique
across the fabric.
NOTE: Remote copy sets cannot be renamed with the RENAME command. If the wrong name is
entered, the remote copy set must be deleted and then added again.
The remote copy set name must start with RCS and may consist of a maximum of 9
characters including letters A through Z, numbers 0 through 9, periods (.), dashes (-),
or underscores (_).
initiator-unit-name
The name of the initiator unit that is to be the first member of the remote copy set.
rem ote-node-name\target-unit- name
The remote-node-name part of the parameter specifies the name of the controller
pair--called a node--receiving the command. The target-unit-name part specifies the
unit on the remote node to be added as the target of the remote copy set.
Switches
OPERATION_MO DE=SYNCHRONOU S (default)
OPERATION_MO DE=ASYNCHRONOUS
This switch determines which of two normal operating modes is assigned to the remote
copy set.
In synchronous mode, write operations must be completed on the remote units of the
remote copy set before the host is informed that the operation is complete.
Synchronous operation assures data consistency at all times among the members of a
remote copy set.
In asynchronous mode, the write operation is reported as complete to the host before
the data is written to the remote units of the remote copy set. Asynchronous mode
gives greater performance and faster response time, but the data on all members of the
remote copy set cannot be assumed to be always the same.
OUTSTANDING_IO= n
This switch sets the number of outstanding I/O operations from the initiator to the
target.
n is a decimal number between 1 and 240, with 20 being the default value.
The way this switch operates depends on which operating mode is set by the
OPERATION_MODE switch:
ADD REMOTE_COPY_SETS 221
I In synchronous mode, OUTSTANDING_IO refers to the number of remote writes
(write operations from the initiator to the target) that can be outstanding.
I In asynchronous mode, OUTSTANDING_IO refers to the number of write
operations that can be reported as completed to the host before they have been
written on all the members of the remote copy set.
Exam ple
To create remote copy set RCS1, consisting of unit D1 on the local controller pair and unit
D21 on a remote controller pair (node) named London, enter:
ADD REMOTE_COPY_SET RCS1 D1 LONDON\D21
See also
ADD ASSOCIATIONS
SET controller REMOTE_COPY
SET remote-copy-set-name
222 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD SNAPSHOT_UNITS
NOTE: This command is operational only in controller software versions V8.5S and V8.5P.
NOTE: This commands is operational only if both controllers have 512MB mirrored cache.
This command creates and names a snapshot unit. A snapshot unit is one that reflects the
contents of another unit at a particular point in time (the instant the ADD
SNAPSHOT_UNITS command is entered). The snapshot unit can be presented to the
host. The snapshot unit remains until it is deleted (DELETE command).
Syntax
ADD SNAPSHOT_UNITS snapshot-unit storageset source-unit
Parameters
The following parameters are required for the ADD SNAPSHOT_UNITS command:
I snapshot unit
I storageset
I source unit
The relationship of the parameters can be summarized as follows:
When the ADD SNAPSHOT_UNITS command is entered, storageset becomes
snapshot-unit and archives the current contents of source-unit at that instant.
These parameters are described in the paragraphs that follow.
snapshot-unit
The unit number that will be assigned to the snapshot unit. The unit number 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 (_).
The snapshot unit is created with all host access disabled by default. Do a SET
command to set up host access.
The snapshot unit will be created on the same controller as the source unit, and must
remain there.
ADD SNAPSHOT_UNITS 223
storageset
Identifies the storageset that will become the snapshot unit. The storageset must have
the following characteristics:
capacity equal to or greater than the source unit
initialized
not a partition or a concatset
source-unit
The unit whose contents will be frozen in time and preserved on the snapshot unit. The
source unit must have the following characteristics:
less than 512 GB
write-back cache enabled
non-transportable
Switches
There are no switches associated with this command.
Exam ples
To create unit D4, which consists of storageset RAID4 and which will become a
point-in-time snapshot of unit D1, enter:
ADD SNAPSHOT_UNITS D4 raid2 D1
See also
SET unit
DELETE container-name
224 HSG60/HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
ADD SPARESET
This command adds a disk drive to the spareset and initializes the metadata on the drive.
The spareset is a pool of drives available to the controller to replace failing members of
storagesets.
Syntax
ADD SPARESET disk-name
Parameters
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
There are no switches associated with this command.
Exam ple
To add a disk drive named DISK20200 and DISK30300 to a spareset, enter:
ADD SPARESET DISK20200
ADD SPARESET DISK30300
See also
DELETE SPARESET
SHOW SPARESET
SHOW STORAGESETS
ADD STRIPESET 225
ADD STRIPESET
This command creates and names a stripeset and adds it to the controller configuration.
Stripesets are also referred to as RAID level 0 storagesets. The number of members in the
stripeset is determined by the number of container-name parameters specified.
Syntax
ADD STRIPESET stripeset-name container-name1 container-name2 [container-nameN]
Parameters
The following parameters are required for the ADD STRIPESET command:
I stripeset name
I container names
These parameters are described in the paragraphs that follow.
stripeset-name
Assigns a name to the stripeset. This is the name used with the ADD UNIT command
to identify the stripeset as a host-addressable unit.
container-name1 container-name2 [container-nameN]
Identifies the members (disk drives or mirrorsets) making up the stripeset. Stripesets
can contain between 2 and 14 members.
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 (_).
It is common to name a stripeset STRIPEn, where n is a sequentially assigned, unique
| DS-DHGGA-CA
ed-write-ba
EK-SE2C8-UA
EK-SWLVD-UA
|
