Command Control Interface User And Reference Guide CCI V01 46 03 02 MK 90RD7010 35

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 636 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Command Control Interface
01-46-03/02
User and Reference Guide
This document describes and provides instructions for using the Command Control Interface (CCI)
software to configure and perform operations on the Hitachi RAID storage systems.
MK- 90RD7010-35
March 2018
© 2018 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and
recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or
Hitachi Vantara Corporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as an
essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not
make any other copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, video and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials
contain the most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for
information about feature and product availability, or contact Hitachi Vantara Corporation at https://support.hitachivantara.com/en_us/contact-
us.html.
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of
Hitachi products is governed by the terms of your agreements with Hitachi Vantara Corporation.
By using this software, you agree that you are responsible for:
1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other
individuals; and
2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including
the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader
agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or
import the Document and any Compliant Products.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000,
S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of International Business
Machines Corporation.
Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS,
Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,
Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks
of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Command Control Interface User and Reference Guide ii
Contents
Preface.............................................................................................................xiv
Intended audience.............................................................................................xiv
Product version..................................................................................................xiv
Release notes....................................................................................................xiv
Changes in this revision..................................................................................... xv
Referenced documents...................................................................................... xv
Document conventions......................................................................................xvi
Conventions for storage capacity values...........................................................xix
Accessing product documentation..................................................................... xx
Getting help........................................................................................................xx
Comments..........................................................................................................xx
Chapter 1: Overview............................................................................. 21
About Command Control Interface.................................................................... 21
CCI functions..................................................................................................... 22
CCI functions matrix..................................................................................... 22
Provisioning functions...................................................................................23
Asynchronous command processing........................................................... 23
Command execution modes.........................................................................23
Precheck function.........................................................................................24
Command execution by the in-band and out-of-band methods................... 26
User authentication mode............................................................................ 28
LDEV nickname function.............................................................................. 28
LDEV grouping function............................................................................... 28
Resource group function.............................................................................. 29
Resource locking function............................................................................ 29
CCI functions available on all RAID storage systems........................................29
In-system replication.....................................................................................29
Contents
Command Control Interface User and Reference Guide 3
Remote replication........................................................................................30
Data protection............................................................................................. 30
Chapter 2: CCI software environment.................................................31
Overview of the CCI software environment....................................................... 31
CCI components on the RAID storage system.................................................. 32
Command device..........................................................................................32
Command device guarding..................................................................... 33
Alternate command device function........................................................35
Remote command device....................................................................... 36
CCI and the SCSI command interface......................................................... 37
Command competition............................................................................ 38
Command flow........................................................................................ 38
Issuing commands for LDEVs within a LUSE device..............................38
CCI instance components on the host server....................................................39
HORCM operational environment................................................................ 39
CCI instance configurations......................................................................... 40
Host machines that can be paired................................................................42
Configuration definition file........................................................................... 43
Configuration definition file settings..............................................................47
HORCM_MON........................................................................................ 47
HORCM_CMD (in-band method)............................................................48
HORCM_CMD (out-of-band method)......................................................53
HORCM_DEV......................................................................................... 56
HORCM_INST........................................................................................ 59
HORCM_LDEV....................................................................................... 60
HORCM_LDEVG.................................................................................... 61
HORCM_INSTP......................................................................................62
HORCM_ALLOW_INST..........................................................................62
Correspondence of the configuration definition file for cascading volume
and mirror descriptors...................................................................................63
Correspondence of configuration file and mirror descriptors.................. 63
Cascading connection and configuration files.........................................67
ShadowImage......................................................................................... 68
Contents
Command Control Interface User and Reference Guide 4
Cascading connections for TrueCopy and ShadowImage...................... 69
CCI software files...............................................................................................72
CCI files supplied with the software............................................................. 72
CCI files for UNIX-based systems...........................................................72
CCI files for Windows-based systems.....................................................74
CCI files for OpenVMS-based systems...................................................77
CCI log and trace files........................................................................................79
CCI log files.................................................................................................. 79
CCI trace files...............................................................................................82
CCI trace control command..........................................................................82
Command logging for audit.......................................................................... 82
Logging other than raidcom command................................................... 83
Logging raidcom command.....................................................................85
User-created files...............................................................................................88
User environment variable.................................................................................89
Chapter 3: CCI functions......................................................................90
System configuration using CCI........................................................................ 90
In-band system configurations and out-of-band system configurations....... 90
System configuration for connecting to a CCI server connected by the
in-band method using the out-of-band method............................................ 92
Connecting to CCI server already connected by In-Band method using Out-
of-Band method................................................................................................. 93
Hardware requirements................................................................................94
I/O Traffic Control......................................................................................... 94
Security setting.............................................................................................95
User authentication............................................................................................96
Command operation authority and user authentication..................................... 97
Controlling User Role................................................................................... 97
Controlling user resources............................................................................98
Commands executed depending on operation authorities......................... 101
Relation between resource groups and command operations......................... 111
Resource lock function.....................................................................................115
Command execution modes............................................................................ 116
Contents
Command Control Interface User and Reference Guide 5
Overview.....................................................................................................116
Context check.............................................................................................118
Checking contents before executing scripts..........................................118
Details of check contents...................................................................... 118
Configuration check....................................................................................125
Resource location and parameter....................................................................125
MP blade location and parameter.............................................................. 125
LDEV grouping function...................................................................................127
Overview.....................................................................................................127
Device group definition methods................................................................ 130
Read operations and command device settings........................................ 130
Defining device groups...............................................................................132
Creating device groups......................................................................... 133
Adding LDEVs to device groups........................................................... 133
Deleting LDEVs from device groups..................................................... 134
Deleting device groups......................................................................... 135
Copy group function................................................................................... 136
Creating copy groups............................................................................137
Adding LDEVS to copy groups............................................................. 138
Deleting LDEVs from copy groups........................................................139
Deleting copy groups............................................................................ 140
Pair operation by specifying a copy group............................................ 141
Pair operations with mainframe volumes.........................................................143
Using "dummy" LUs for mainframe LDEVs................................................ 143
Pair status and access permission for mainframe LDEVs......................... 144
Operational differences for multiplatform volumes..................................... 147
Operational differences for replication commands..................................... 147
Global storage virtualization function...............................................................149
System configuration example with the global storage virtualization
function.......................................................................................................150
Using CCI with the global storage virtualization function........................... 150
Configuration definition file settings with global storage virtualization........152
Example of the configuration definition files when specifying a virtual
storage machine by HORCM_CMD........................................................... 153
Contents
Command Control Interface User and Reference Guide 6
Specifying a virtual storage machine to HORCM_VCMD.......................... 155
Command operations to virtual storage machines................................155
Operation target for raidcom commands when specifying the virtual
storage machine in HORCM_VCMD.....................................................159
raidcom commands for volumes that belong to virtual storage
machine for HORCM_CMD...................................................................167
Chapter 4: Starting up CCI................................................................. 168
Starting up on UNIX systems...........................................................................168
Starting up one instance of CCI on a UNIX system................................... 168
Starting up two instances of CCI on a UNIX system.................................. 168
Starting up on Windows systems.....................................................................169
Starting up one instance of CCI on a Windows system............................. 169
Starting up two instances of CCI on a Windows system............................ 170
Starting up on OpenVMS systems...................................................................170
Starting up one instance of CCI on an OpenVMS system......................... 170
Starting up two instances of CCI on an OpenVMS system........................ 171
Starting CCI as a service (Windows systems).................................................172
Chapter 5: Provisioning operations with CCI...................................175
About provisioning operations......................................................................... 175
Overview of the configuration setting command........................................ 175
Synchronous command processing......................................................176
Asynchronous command processing.................................................... 176
Errors during asynchronous command processing...............................176
Workflow for executing asynchronous commands................................177
Asynchronous commands.....................................................................177
Help on configuration setting commands................................................... 180
LDEV nickname function............................................................................ 180
Available provisioning operations.................................................................... 180
Provisioning operations that can be performed on device groups...................189
Operation method.......................................................................................190
Workflow for performing provisioning operations.............................................192
Resource group operations............................................................................. 193
Creating resource groups...........................................................................193
Contents
Command Control Interface User and Reference Guide 7
Deleting resource groups........................................................................... 194
Allocating resources to other resource groups...........................................195
Execution example for registering LDEVS to the pools as device groups. 196
Internal volume operations.............................................................................. 197
Creating internal volumes (open volumes).................................................197
Script examples for internal volume operation (open volumes)................. 199
Creating internal volumes (mainframe volumes)........................................202
Script examples of internal volume (mainframe volumes) operations.. 203
Virtual volume (Dynamic Provisioning) operations.......................................... 204
Creating virtual volumes (Dynamic Provisioning).......................................204
Script examples of virtual volume (Dynamic Provisioning) operation.........207
Deleting a virtual volume for which capacity saving is enabled..................209
Using the -operation initialize_capacity_saving option
of the raidcom delete ldev command to delete a virtual volume. 209
Deleting a virtual volume by blocking, initializing, and then deleting
the volume.............................................................................................210
Virtual volume (Dynamic Provisioning for Mainframe) operations................... 211
Creating virtual volumes (Dynamic Provisioning for Mainframe)................ 211
Script examples of virtual volume (Dynamic Provisioning for Mainframe)
operation.....................................................................................................213
Virtual volume (Dynamic Tiering) operations................................................... 215
Operational flow..........................................................................................215
Creating virtual volumes (Dynamic Tiering)................................................216
Script examples cript examples of virtual volume (Dynamic Tiering)
operation.....................................................................................................219
Configuring iSCSI virtual ports.........................................................................222
Setting an iSCSI virtual port....................................................................... 222
Deleting an iSCSI virtual port..................................................................... 223
External volume operations............................................................................. 224
Creating external volumes (Fibre Channel)................................................224
Creating external volumes (iSCSI)............................................................. 227
Script examples of external volume operations..........................................232
Virtual Partition Manager operations................................................................235
Performing Virtual Partition Manager operations........................................235
Contents
Command Control Interface User and Reference Guide 8
Displaying CLPR information......................................................................236
Migrating parity groups in a CLPR............................................................. 236
Displaying parity group information.......................................................236
Moving parity groups.............................................................................237
Checking result of CLPR transfer..........................................................237
Server Priority Manager operations................................................................. 238
Configuring Server Priority Manager by specifying ports and WWNs of
HBAs.......................................................................................................... 238
Controlling the priority of I/O operations in storage systems on
servers.................................................................................................. 239
Using and managing Server Priority Manager...................................... 239
Setting SPM names for WWNs and registering them to the SPM
group.....................................................................................................240
Configuring Server Priority Manager by specifying ports and WWNs
of HBAs.................................................................................................241
Controlling server performance when the host group is not registered
in the SPM group.................................................................................. 241
Controlling server performance when the host group is registered in
the SPM group (VSP only)....................................................................243
Displaying the WWN of host bus adapters........................................... 245
Setting the priority on host bus adapters.............................................. 245
Displaying the status of the prioritized WWN and the non-prioritized
WWN settings....................................................................................... 246
Setting SPM names for host bus adapters........................................... 247
Grouping multiple host bus adapters into one group............................ 247
Obtaining monitoring information of the prioritized WWN and the
non-prioritized WWN.............................................................................247
Stopping performance control of server by using SPM function........... 248
Cautions about using Server Priority Manager..................................... 248
Cautions when using host groups after registering them in SPM
groups (VSP only).................................................................................251
Configuring Server Priority Manager by specifying LDEVs and WWNs or
iSCSI names of HBAs................................................................................ 252
Virtual storage machine operations................................................................. 255
Creating host groups in a virtual storage machine..................................... 255
Adding LDEVs to a virtual storage machine...............................................256
Contents
Command Control Interface User and Reference Guide 9
Removing the virtual storage machine....................................................... 256
Chapter 6: Data replication operations with CCI..............................259
About data replication operations.................................................................... 259
Features of paired volumes............................................................................. 260
Using CCI with ShadowImage and TrueCopy................................................. 261
Using CCI with Thin Image.............................................................................. 261
Using CCI with global-active device................................................................ 262
ShadowImage operations................................................................................ 262
ShadowImage duplicated mirroring............................................................263
ShadowImage cascading pairs.................................................................. 264
Restrictions for ShadowImage cascading volumes.............................. 265
Restriction for TrueCopy/ShadowImage cascading volumes................266
TrueCopy operations....................................................................................... 266
TrueCopy takeover commands.................................................................. 267
Takeover-switch function.......................................................................269
Swap-takeover function........................................................................ 270
SVOL-takeover function........................................................................271
PVOL-takeover function........................................................................272
TrueCopy remote commands..................................................................... 273
TrueCopy local commands.........................................................................274
TrueCopy, ShadowImage, and Universal Replicator operations..................... 275
TrueCopy/ShadowImage volumes............................................................. 275
TrueCopy/ShadowImage/Universal Replicator pair status......................... 276
TrueCopy Async, TrueCopy Sync, Universal Replicator, and global-
active device volumes................................................................................ 284
TrueCopy Async and Universal Replicator volume characteristics.......286
Sidefile cache for TrueCopy Async....................................................... 287
TrueCopy Async transition states and sidefile control.......................... 287
TrueCopy Async/Universal Replicator error state................................. 290
TrueCopy Sync/TrueCopy Async and Universal Replicator/global-active
device fence level settings......................................................................... 290
Setting the fence level...........................................................................292
Copy-on-Write Snapshot operations................................................................293
Contents
Command Control Interface User and Reference Guide 10
Copy-on-Write Snapshot volumes..............................................................294
Pair operations and commands for Copy-on-Write Snapshot and Thin
Image..........................................................................................................294
Creating a Copy-on-Write Snapshot pair....................................................295
Copy-on-Write Snapshot pair status...........................................................295
Pair status relationship to Copy-on-Write Snapshot commands................ 296
Controlling Volume Migration...........................................................................297
Specifications for Volume Migration........................................................... 298
Commands to control Volume Migration.................................................... 299
Relations between "cc" command issues and migration volume status.....304
Restrictions for Volume Migration...............................................................305
Universal Replicator MxN configuration and control........................................305
Overview.....................................................................................................305
Policy..........................................................................................................306
Configuration definition file (horcm.conf)....................................................307
Command specifications............................................................................ 308
pairdisplay command............................................................................ 308
pairsplit command.................................................................................309
Notice on system operation........................................................................ 311
Configuration examples..............................................................................314
Duplication of CCI applications........................................................................315
Requirements for duplication of CCI.......................................................... 318
Note for duplication of CCI......................................................................... 319
Remote volume discovery................................................................................319
Discovering a remote volume.....................................................................320
Import method by the startup of CCI (horcmstart.sh) on the remote
host....................................................................................................... 321
Chapter 7: Data protection operations with CCI.............................. 323
Data protection operations...............................................................................323
Data Retention Utility..................................................................................323
Restrictions on Data Retention Utility volumes..................................... 324
Database Validator..................................................................................... 325
Restrictions on Database Validator....................................................... 325
Contents
Command Control Interface User and Reference Guide 11
Protection parameters and operations.............................................................326
Data Protection facility..................................................................................... 327
Data Protection Facility specifications........................................................328
Examples for configuration and protected volumes................................... 329
Operation authority with CMD security enabled......................................... 331
Target commands for protection.................................................................332
permission command................................................................................. 332
New options for security............................................................................. 333
raidscan -find inst..................................................................................333
raidscan -find verify [MU#].................................................................... 333
raidscan -f[d]......................................................................................... 334
pairdisplay -f[d]......................................................................................334
Permitting protected volumes.....................................................................335
With a $HORCMPERM file................................................................... 335
Without a $HORCMPERM file: Commands to run on different
operating systems.................................................................................337
Environment variables................................................................................338
$HORCMPROMOD.............................................................................. 338
$HORCMPERM.................................................................................... 338
Determining the protection mode command device................................... 338
Chapter 8: Examples of using CCI commands ............................... 340
Group version control for mixed storage system configurations......................340
LDM volume discovery and flushing for Windows........................................... 341
Volume discovery function..........................................................................341
Mountvol attached to Windows 2012/2008/2003/2000 systems................ 344
System buffer flushing function.................................................................. 344
Special facilities for Windows systems............................................................ 348
Signature changing facility for Windows systems...................................... 348
GPT disk for Windows................................................................................351
Directory mount facility for Windows systems............................................ 352
Host group control............................................................................................355
Specifying a host group..............................................................................355
Commands and options including a host group......................................... 356
Contents
Command Control Interface User and Reference Guide 12
Using CCI SLPR security.................................................................................357
Specifying the SLPR protection facility.......................................................358
SLPR configuration examples.................................................................... 359
Single host............................................................................................ 359
Dual Hosts.............................................................................................360
Chapter 9: Troubleshooting............................................................... 363
General troubleshooting.................................................................................. 363
Operational notes and restrictions for CCI operations.....................................366
Error messages and error codes..................................................................... 370
System log messages................................................................................ 370
Command error messages ........................................................................372
Generic error codes (horctakeover and pair commands)................... 390
Generic error codes (raidscan, raidqry, raidar, horcctl).............................. 392
Specific error codes....................................................................................393
SSB codes..................................................................................................395
SSB codes returned by the replication commands............................... 395
SSB codes returned by the configuration setting command (raidcom).397
Other SSB codes indicating internal errors...........................................628
Calling customer support................................................................................. 630
Glossary........................................................................................... 631
Index................................................................................................. 632
Contents
Command Control Interface User and Reference Guide 13
Preface
This document describes and provides instructions for using the Command Control
Interface (CCI) software to congure and perform operations on RAID storage systems.
Please read this document carefully to understand how to use these products, and
maintain a copy for your reference.
Intended audience
This document is intended for system administrators, Hitachi Vantara representatives,
and authorized service providers who install, congure, and operate Hitachi Vantara
RAID storage systems.
Readers of this document should be familiar with the following:
■Data processing and RAID storage systems and their basic functions.
■The Hitachi Vantara RAID storage system and the manual for the storage system (for
example, Hardware Guide for Hitachi Virtual Storage Platform G1000, G1500, and F1500,
Hitachi Virtual Storage Platform User and Reference Guide
■The management software for the storage system (for example, Hitachi Command
Suite, Hitachi Device Manager - Storage Navigator) and the applicable user manuals
(for example, Hitachi Command Suite User Guide and System Administrator Guide).
■The host systems attached to the Hitachi Vantara RAID storage system.
Product version
This document revision applies to CCI version 01-46-03/02 or later.
Release notes
Read the release notes before installing and using this product. They may contain
requirements or restrictions that are not fully described in this document or updates or
corrections to this document. Release notes are available on Hitachi Vantara Support
Connect: https://knowledge.hitachivantara.com/Documents.
Command Control Interface User and Reference Guide xiv
Changes in this revision
■Updated the description of the resource lock function (Resource lock function (on
page 115) ).
■Updated the description of the suspending/deleting status for Universal Replicator
MxN congurations (Notice on system operation (on page 311) ).
■Updated the error code tables.
Referenced documents
Referenced documents
Command Control Interface documents:
■Command Control Interface Installation and Conguration Guide, MK-90RD7008
■Command Control Interface User and Reference Guide, MK-90RD7010
Hitachi Command Suite documents:
■Hitachi Command Suite User Guide, MK-90HC172
Hitachi Virtual Storage Platform F series and G series documents:
■Hitachi Thin Image User Guide, MK-92RD8011
■Provisioning Guide, MK-94HM8014
■Provisioning Guide for Open Systems, MK-92RD8014
■System Administrator Guide, MK-94HM8016
■System Administrator Guide, MK-92RD8016
■Hitachi Device Manager - Storage Navigator Messages, MK-94HM8017
■Hitachi Device Manager - Storage Navigator Messages, MK-92RD8017
■Hitachi TrueCopy® User Guide, MK-92RD8019
■Hitachi ShadowImage® User Guide, MK-92RD8021
■Hitachi Universal Replicator User Guide, MK-92RD8023
■Hitachi Universal Volume Manager User Guide, MK-92RD8024
■Global-Active Device User Guide, MK-92RD8072
Changes in this revision
Command Control Interface User and Reference Guide xv
Hitachi Unied Storage VM documents:
■Provisioning Guide, MK-92HM7012
■Hitachi ShadowImage® User Guide, MK-92HM7013
■System Administrator Guide, MK-92HM7016
■Hitachi Device Manager - Storage Navigator Messages,MK-92HM7017
■Hitachi TrueCopy® User Guide, MK-92HM7018
■Hitachi Universal Replicator User Guide, MK-92HM7019
■Hitachi Universal Volume Manager User Guide, MK-92HM7020
Hitachi Virtual Storage Platform documents:
■Hitachi Copy-on-Write Snapshot User Guide, MK-90RD7013
■Provisioning Guide for Mainframe Systems, MK-90RD7021
■Provisioning Guide for Open Systems, MK-90RD7022
■Hitachi ShadowImage® for Mainframe User Guide, MK-90RD7023
■Hitachi ShadowImage® User Guide, MK-90RD7024
■Hitachi Storage Navigator User Guide, MK-90RD7027
■Hitachi Storage Navigator Messages, MK-90RD7028
■Hitachi TrueCopy® User Guide, MK-90RD7029
■Hitachi TrueCopy® for Mainframe User Guide, MK-90RD7030
■Hitachi Universal Replicator for Mainframe User Guide, MK-90RD7031
■Hitachi Universal Replicator User Guide, MK-90RD7032
■Hitachi Universal Volume Manager User Guide, MK-90RD7033
■Hitachi Thin Image User Guide, MK-90RD7179
Document conventions
This document uses the following storage system terminology conventions:
Convention Description
Hitachi Virtual
Storage Platform
family (VSP family)
Refers to the following storage systems:
■Hitachi Virtual Storage Platform
■Hitachi Virtual Storage Platform G1x00
■Hitachi Virtual Storage Platform F1500
■Hitachi Virtual Storage Platform G200
■Hitachi Virtual Storage Platform G400
Document conventions
Command Control Interface User and Reference Guide xvi
Convention Description
■Hitachi Virtual Storage Platform G600
■Hitachi Virtual Storage Platform G800
■Hitachi Virtual Storage Platform F400
■Hitachi Virtual Storage Platform F600
■Hitachi Virtual Storage Platform F800
VSP G series Refers to the following storage systems:
■Hitachi Virtual Storage Platform G1x00
■Hitachi Virtual Storage Platform G200
■Hitachi Virtual Storage Platform G400
■Hitachi Virtual Storage Platform G600
■Hitachi Virtual Storage Platform G800
VSP F series Refers to the following storage systems:
■Hitachi Virtual Storage Platform F1500
■Hitachi Virtual Storage Platform F400
■Hitachi Virtual Storage Platform F600
■Hitachi Virtual Storage Platform F800
VSP Gx00 models Refers to all of the following models, unless otherwise noted.
■Hitachi Virtual Storage Platform G200
■Hitachi Virtual Storage Platform G400
■Hitachi Virtual Storage Platform G600
■Hitachi Virtual Storage Platform G800
VSP Fx00 models Refers to all of the following models, unless otherwise noted.
■Hitachi Virtual Storage Platform F400
■Hitachi Virtual Storage Platform F600
■Hitachi Virtual Storage Platform F800
This document uses the following typographic conventions:
Document conventions
Command Control Interface User and Reference Guide xvii
Convention Description
Bold ■Indicates text in a window, including window titles, menus,
menu options, buttons, elds, and labels. Example:
Click OK.
■Indicates emphasized words in list items.
Italic ■Indicates a document title or emphasized words in text.
■Indicates a variable, which is a placeholder for actual text
provided by the user or for output by the system. Example:
pairdisplay -g group
(For exceptions to this convention for variables, see the entry for
angle brackets.)
Monospace Indicates text that is displayed on screen or entered by the user.
Example: pairdisplay -g oradb
< > angle
brackets
Indicates variables in the following scenarios:
■Variables are not clearly separated from the surrounding text or
from other variables. Example:
Status-<report-name><file-version>.csv
■Variables in headings.
[ ] square
brackets
Indicates optional values. Example: [ a | b ] indicates that you can
choose a, b, or nothing.
{ } braces Indicates required or expected values. Example: { a | b } indicates
that you must choose either a or b.
| vertical bar Indicates that you have a choice between two or more options or
arguments. Examples:
[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.
This document uses the following icons to draw attention to information:
Icon Label Description
Note Calls attention to important or additional information.
Document conventions
Command Control Interface User and Reference Guide xviii
Icon Label Description
Tip Provides helpful information, guidelines, or suggestions for
performing tasks more eectively.
Caution Warns the user of adverse conditions and/or consequences
(for example, disruptive operations, data loss, or a system
crash).
WARNING Warns the user of a hazardous situation which, if not
avoided, could result in death or serious injury.
Conventions for storage capacity values
Physical storage capacity values (for example, disk drive capacity) are calculated based
on the following values:
Physical capacity unit Value
1 kilobyte (KB) 1,000 (103) bytes
1 megabyte (MB) 1,000 KB or 1,0002 bytes
1 gigabyte (GB) 1,000 MB or 1,0003 bytes
1 terabyte (TB) 1,000 GB or 1,0004 bytes
1 petabyte (PB) 1,000 TB or 1,0005 bytes
1 exabyte (EB) 1,000 PB or 1,0006 bytes
Logical capacity values (for example, logical device capacity, cache memory capacity) are
calculated based on the following values:
Logical capacity unit Value
1 block 512 bytes
1 cylinder Mainframe: 870 KB
Open-systems:
■OPEN-V: 960 KB
■Others: 720 KB
1 KB 1,024 (210) bytes
Conventions for storage capacity values
Command Control Interface User and Reference Guide xix
Logical capacity unit Value
1 MB 1,024 KB or 1,0242 bytes
1 GB 1,024 MB or 1,0243 bytes
1 TB 1,024 GB or 1,0244 bytes
1 PB 1,024 TB or 1,0245 bytes
1 EB 1,024 PB or 1,0246 bytes
Accessing product documentation
Product user documentation is available on Hitachi Vantara Support Connect: https://
knowledge.hitachivantara.com/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release
of the product.
Getting help
Hitachi Vantara Support Connect is the destination for technical support of products and
solutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi Vantara
Support Connect for contact information: https://support.hitachivantara.com/en_us/
contact-us.html.
Hitachi Vantara Community is a global online community for Hitachi Vantara customers,
partners, independent software vendors, employees, and prospects. It is the destination
to get answers, discover insights, and make connections. Join the conversation today!
Go to community.hitachivantara.com, register, and complete your prole.
Comments
Please send us your comments on this document to
doc.comments@hitachivantara.com. Include the document title and number, including
the revision level (for example, -07), and refer to specic sections and paragraphs
whenever possible. All comments become the property of Hitachi Vantara Corporation.
Thank you!
Accessing product documentation
Command Control Interface User and Reference Guide xx
Chapter 1: Overview
This chapter provides an overview of the Command Control Interface (CCI) software and
CCI operations on the Hitachi RAID storage systems.
About Command Control Interface
The Command Control Interface software enables you to perform storage system
conguration and data management operations by issuing commands to the RAID
storage systems:
■Hitachi Virtual Storage Platform G200, G400, G600, G800
■Hitachi Virtual Storage Platform F400, F600, F800
■Hitachi Virtual Storage Platform F1500 (VSP F1500)
■Hitachi Unied Storage VM (HUS VM)
■Hitachi Virtual Storage Platform (VSP)
■Hitachi Universal Storage Platform V/VM (USP V/VM)
■Hitachi TagmaStore® Universal Storage Platform (TagmaStore USP)
■Hitachi TagmaStore® Network Storage Controller (TagmaStore NSC)
CCI continues to provide the proven functionality that has been available for the USP
V/VM and previous storage system models, including in-system replication, remote
replication, and data protection operations.
In addition, CCI for VSP and later provides command-line access to the same provisioning
and storage management operations that are available in the GUI software (for example,
Hitachi Command Suite, Storage Navigator). CCI commands can be used interactively or
in scripts to automate and standardize storage administration functions, thereby
simplifying the job of the storage administrator and reducing administration costs.
Note: If a storage system rejects CCI commands, verify the software licenses
for the storage system (for example, TrueCopy) and the status of the software
product and storage system.
Chapter 1: Overview
Command Control Interface User and Reference Guide 21
CCI functions
CCI functions matrix
The following table lists and describes the CCI functions available on the RAID storage
systems.
Function
Storage system
TagmaStore
USP/
TagmaStore
NSC
USP
V/VM VSP
HUS
VM
VSP
G1x00
VSP
F1500
VSP Gx00
models,
VSP Fx00
models
Local copy (open) Yes Yes Yes Yes Yes Yes
Local copy
(mainframe)
No No Yes* No Yes No
Remote copy (open) Yes Yes Yes Yes Yes Yes
Remote copy
(mainframe)
No No Yes* No Yes No
Data protection Yes Yes Yes Yes Yes Yes
VSS conguration Yes Yes Yes Yes Yes Yes
SRM SRA Yes Yes Yes Yes Yes Yes
Provisioning
(raidcom)
No No Yes Yes Yes Yes
Out-of-band
method
No No Yes Yes Yes Yes
User authentication No No Yes Yes Yes Yes
LDEV nickname No No Yes Yes Yes Yes
LDEV group No No Yes Yes Yes Yes
Resource group No No Yes Yes Yes Yes
Resource lock No No Yes Yes Yes Yes
*If DKCMAIN microcode version of the VSP storage system is 70-03-3x-xx/xx or later,
the operation of TrueCopy for Mainframe, Universal Replicator for Mainframe, and
ShadowImage for Mainframe can be performed from Command Control Interface.
CCI functions
Chapter 1: Overview
Command Control Interface User and Reference Guide 22
Provisioning functions
The raidcom conguration setting command enables you to perform provisioning
functions, such as setting commands or creating LDEVs, from CCI. For information about
the conguration setting command (raidcom command), see Provisioning operations
with CCI (on page 175) .
Asynchronous command processing
For the raidcom conguration setting commands, asynchronous command processing
is used for operations that take time to process on the storage system. Once an
asynchronous command has been issued, you can execute additional commands
without having to wait for the asynchronous command to complete. You can also
monitor the completion status of asynchronous commands by using a status reference
command (for example, raidcom get command_status).
Command execution modes
CCI provides two command execution modes:
■Transaction mode, in which a script le is specied with the -zt option
■Line-by-line mode, in which commands are executed row-by-row for the conguration
setting (raidcom) commands
Provisioning functions
Chapter 1: Overview
Command Control Interface User and Reference Guide 23
You can use transaction mode to execute the following checking:
■Context check: This check is executed when a script le is specied by -zt option. It
checks the context of preceding commands and determines whether a subsequent
command can be executed.
Specifying example:
raidcom -zt <script_file>
■Conguration check: This check veries that the actual storage system conguration
is valid (implemented) for the resources specied in the commands (for example,
LDEVs, ports, pools).
Syntax example:
raidcom get ldev -ldev_id -cnt 65280 -store<work_file>
raidcom -zt <script_file> -load<work_file>
Precheck function
CCI provides a precheck function for the conguration setting (raidcom) commands that
checks the command before it is executed.
In earlier versions of CCI, an error was returned when the syntax of a command to be
executed was not correct. The precheck function checks the command syntax before the
command is executed. To use the precheck function, specify either the -checkmode
precheck option or the -zt option.
The following table shows the summary of the checking function combinations between
the precheck function and the transaction mode.
Command syntax
Syntax
check
Context
check
Config
check
Executio
n
raidcom <command> Execute
d
Not
execute
d
Not
execute
d
Executed
raidcom <command> -checkmode precheck Execute
d
Not
execute
d
Not
execute
d
Not
executed
raidcom -zt <script file> Execute
d
Execute
d
Not
execute
d
Executed
Precheck function
Chapter 1: Overview
Command Control Interface User and Reference Guide 24
Command syntax
Syntax
check
Context
check
Config
check
Executio
n
raidcom get ldev -ldev_id -cnt 65280
-store<work_file>
raidcom -zt <script_file> -load
<work_file>
Execute
d
Execute
d
Execute
d
Executed
raidcom -zt <script file> -checkmode
precheck
Execute
d
Execute
d
Not
execute
d
Not
executed
raidcom get ldev -ldev_id -cnt 65280
-store<work_file>
raidcom -zt <script_file> -load
<work_file>
-checkmode precheck
Execute
d
Execute
d
Execute
d
Not
executed
Precheck function
Chapter 1: Overview
Command Control Interface User and Reference Guide 25
Command execution by the in-band and out-of-band methods
The two methods for issuing commands from a host are the in-band method and the
out-of-band method:
■In-band method:
The method issues a command from a UNIX/PC host connected directly to a storage
system via Fibre Channel or iSCSI. Older CCI versions (that do not support VSP) can
only issue commands by using the in-band method. In this method, when a command
is issued, it is sent to the dedicated LDEV (command device) of the storage system
selected by the user via Fibre Channel or iSCSI from CCI on the host.
■Out-of-band method:
This method issues commands from a UNIX/PC host connected to the storage system
via LAN. As shown in the following gure, CCI supporting VSP and later models can
issue commands using the out-of-band method. Client PCs that are not connected
directly to storage systems can execute the same scripts as the in-band method.
When a command is issued by using the out-of-band method, the command is sent to
a virtual command device via LAN from CCI on the host. Virtual command devices are
created when a command is executed using the out-of-band method. A virtual
command device can be created by specifying the location to create a virtual
command device in the conguration denition le. For details on how to create
command devices, see HORCM_CMD (out-of-band methid). Note, however, that the
location you can create virtual command devices varies depending on the storage
system models. For details about the location, see System conguration using CCI.
Note: If many commands are issued in a short period of time by using the
out-of-band method, for example issuing commands in a conguration
with VMware Site Recovery Manager (SRM), or from scripts, the command
response might slow. In this case, issuing commands by using the in-band
method is recommended.
Tip: For older versions of CCI that do not support VSP, if you want to issue
a command from a client PC which is not connected to a storage system
directly, you must write a remote shell script which is executed by your
logging in to the CCI server of the in-band method via Telnet or SSH.
The following gure illustrates in-band and out-of-band CCI operations. For details about
the in-band and out-of-band system congurations, see System conguration using CCI.
Command execution by the in-band and out-of-band methods
Chapter 1: Overview
Command Control Interface User and Reference Guide 26
The following table provides a comparison of in-band and out-of-band operations.
Route Command Specification
In-band Replication The requirement for user authentication
depends on the setting of user
authentication.
Provisioning User authentication is required. User
authentication mode of the command device
must be enabled.
Out-of-band Replication User authentication is required. For virtual
command devices, user authentication mode
is always enabled.
Command execution by the in-band and out-of-band methods
Chapter 1: Overview
Command Control Interface User and Reference Guide 27
Route Command Specification
Provisioning User authentication is required. For virtual
command devices, user authentication mode
is always enabled.
User authentication mode
You must enable the user authentication mode on the CCI command device. For the
virtual command device the user authentication mode is always enabled.
When user authentication mode is enabled, use the user ID and password that you
created using Device Manager - Storage Navigator or the maintenance utility to log in to
the storage system.
LDEV nickname function
You can assign a unique nickname of up to 32 characters to an LDEV.
LDEV grouping function
In CCI versions prior to the Hitachi Virtual Storage Platform, you needed to dene the
copy groups in the CCI conguration denition le on each host. When the copy group
information changed, the conguration denition le needed to be edited on each host.
In CCI versions after the VSP, the information registered in the storage system can be
used. This LDEV grouping function can minimize the description of the CCI conguration
denition le on each host. When the copy group information changes, you need to
update only one conguration denition le, saving time and eliminating the chance for
error due to mismatching edits.
The LDEV grouping functionality is implemented using device names, device groups, and
copy groups:
Device name
■A name that can be assigned to one LDEV per device group.
■Each name is associated with a device group to which the LDEV belongs.
■An LDEV nickname can be assigned to the LDEV as a unique name for the LDEV
that is not related with a device group. Only one LDEV nickname can be
assigned to each LDEV.
Device group
■A group of one or more LDEVs. One LDEV can belong to multiple device groups.
■A device group can belong to only one copy group.
■If you want to construct a mirror or cascade, you need to dene a dierent
device group and a device name in each copy group.
User authentication mode
Chapter 1: Overview
Command Control Interface User and Reference Guide 28
Copy group
A group that is dened by specifying two device groups: one device group at the
primary site and one device group at the secondary site.
Resource group function
Using Resource Group function, the storage administrator for each resource group can
access only the resources in the resource group. The storage administrator cannot
access resources in other resource groups. This prevents the risk of destroying the data
by another storage administrator in the other resource groups or of leaking out the data.
Resource locking function
The resource locking function prevents conict among multiple users.
User scripts cannot be guaranteed to work correctly when multiple users are using the
following dierent interfaces:
■Storage Navigator
■Device Manager - Storage Navigator
■SVP
■Maintenance utility (VSP Gx00 models and VSP Fx00 models)
■Maintenance PC
You can use the lock command while the script is running to ensure completion. To use
the lock command, user authentication is required.
CCI functions available on all RAID storage systems
CCI provides the following functionality on all Hitachi Vantara RAID storage systems.
■In-system replication
■Remote replication
■Data protection
In-system replication
CCI provides command-line control for in-system (local) replication operations, including
ShadowImage, Thin Image, and Copy-on-Write Snapshot. CCI displays local replication
information and allows you to perform operations by issuing commands or by executing
script les.
Resource group function
Chapter 1: Overview
Command Control Interface User and Reference Guide 29
Remote replication
CCI provides command-line control for remote replication operations, including
TrueCopy, Universal Replicator, and global-active device. CCI displays remote replication
information and allows you to perform operations by issuing commands or by executing
script les.
For remote copy operations, CCI interfaces with the system software and high-availability
(HA) software on the host as well as the software on the RAID storage system. CCI
provides failover operation commands that support mutual hot standby in conjunction
with industry-standard failover products (for example, MC/ServiceGuard, HACMP,
FirstWatch®). CCI also supports a scripting function for dening multiple operations in a
script (or text) le. Using CCI scripting, you can set up and execute a large number of
commands in a short period of time while integrating host-based high-availability control
over copy operations.
Data protection
CCI supports data protection operations, including Hitachi Database Validator and
Hitachi Data Retention Utility.
■Database Validator. The CCI software provides commands to set and verify
parameters for volume-level validation checking of Oracle® database operations.
Once validation checking is enabled, all write operations to the specied volumes
must have valid Oracle checksums. CCI reports a validation check error to the syslog
le each time an error is detected. Database Validator requires the operation of CCI
software product but cannot be controlled via the Storage Navigator software.
■Data Retention Utility. The CCI software enables you to set and verify the parameters
for guarding at the volume level. Once guarding is enabled, the RAID storage system
conceals the target volumes from SCSI commands such as SCSI Inquiry and SCSI Read
Capacity, prevents reading and writing to the volume, and protects the volume from
being used as a copy volume (the TrueCopy, Universal Replicator, global-active device,
or ShadowImage paircreate operation fails).
Remote replication
Chapter 1: Overview
Command Control Interface User and Reference Guide 30
Chapter 2: CCI software environment
This chapter describes the CCI software environment.
Overview of the CCI software environment
The CCI software environment includes components on the Hitachi RAID storage systems
and the CCI software on the host servers and/or on the Storage Navigator computer or
management client. The CCI components on the storage systems include the user data
volumes and CCI command devices.
Each CCI instance on a host server includes:
■CCI application les, referred to as HORC Manager (HORCM)
●Log and trace les
●A command server
●Error monitoring and event reporting les
●A conguration management feature
■Conguration denition le (user-dened)
■User execution environments for the Hitachi Vantara features, including the
commands, a command log, and a monitoring function.
The CCI commands also have interface considerations (see CCI and the SCSI command
interface).
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 31
CCI components on the RAID storage system
Command device
CCI commands are issued by the CCI software to the RAID storage system command
device. The command device is a user-selected, dedicated logical volume on the storage
system that functions as the interface to the CCI software on the host. The command
device is dedicated to CCI communications and cannot be used by any other
applications. The command device accepts CCI read and write commands that are issued
by the storage system. The command device also returns read requests to the host. The
volume designated as the command device is used only by the storage system and is
blocked from the user. The command device uses 32 MB, and the remaining volume
space is reserved for CCI and its utilities. The command device can be any OPEN-x device
(for example, OPEN-V) that is accessible to the host. A LUN Expansion volume cannot be
used as a command device. A Virtual LVI/Virtual LUN volume as small as 36 MB (for
example, OPEN-3-CVS) can be used as a command device.
Warning: Make sure the volume to be selected as the command device does
not contain any user data. The command device will be inaccessible to the
host.
The CCI software on the host issues read and write commands to the command device.
When CCI receives an error notication in reply to a read or write request to the RAID
storage system, the CCI software switches to an alternate command device, if one is
dened. If a command device is blocked (for example, for online maintenance), you can
switch to an alternate command device manually. If no alternate command device is
dened or available, all TrueCopy and ShadowImage commands terminate abnormally,
and the host will not be able to issue commands to the storage system. Therefore, one
or more alternate command devices (see Alternate command device function.) must be
set to avoid data loss and storage system downtime.
Each command device must be set using the LUN Manager software on Storage
Navigator. In addition, for using a Provisioning command, user authentication is
required. Set the security attribute of the command device with user authentication. For
information and instructions on setting a command device, see the Provisioning Guide for
the storage system.
Each command device must also be dened in the HORCM_CMD section of the
conguration denition le for the CCI instance on the attached host. If an alternate
command device is not dened in the conguration denition le, the CCI software
might not be able to use the device.
The CCI Data Protection Facility uses an enhanced command device that has an attribute
to indicate protection ON or OFF.
Note:
■For Solaris operations, the command device must be labeled.
CCI components on the RAID storage system
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 32
To enable dual path of the command device, make sure to include all paths to the
command device on a single line in the HORCM_CMD section of the conguration
denition le. The following shows an example with two controller paths to the
command device. Putting the path information on separate lines might cause parsing
issues, and failover might not occur unless the HORCM startup script is restarted.
HORCM_CMD #dev_name dev_name dev_name /dev/rdsk/c1t66d36s2 /dev/
rdsk/c2t66d36s2
Command device guarding
In the customer environment, a command device might be attacked by the maintenance
program of the Solaris Server, after that usable instance will be exhausted, and CCI
instance would not start up on all servers (except attacked server). This might happen
due to incorrect operation of the maintenance personnel for the UNIX Server. In this
case, the command device should be protected against operator error, as long as it can
be seen as the device le from the maintenance personnel.
Thus, the RAID microcode (for the command device) and CCI support this protection in
order to guard from similar access.
Guarding method
Currently, assignment of the instance via the command device is ONE phase. Therefore,
if the command device reads a special allocation area of the instance through the
maintenance tool and so on, then it causes a fault of full space of the instance, because
the command device interprets as assignment of the instance from CCI.
CCI has TWO phases that it reads to acquire usable LBA, and writes with the acquired
LBA in attaching sequence to the command device, so the command device can conrm
whether it was required as the assignment for CCI or not, by detecting and adding two
status bits to the instance assignment table.
The following gure shows the current assignment sequence.
The following gure shows improved assignment sequence.
Command device guarding
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 33
The command device performs the assignment of an instance through TWO phases that
have "temporary allocation (1 0)" and "actual allocation (1 1)" to the instance assignment
table.
If the command device is attacked, the instance assignment table is lled with
"temporary allocation (1 0)" status. After that, the command device will detect a fault of
full space as the instance assignment, clear up all "temporary allocation (1 0)", and then
reassign the required instance automatically.
This does not require a service representative to switch the command device "OFF/ON"
to clear up the instance table.
Verifying the CCI instance number
CCI provides a way to verify the number of "temporary allocations (1 0)" and "actual
allocations (1 1)" on the instance table so that you can conrm validity of the CCI
instance number in use. The horcctl -DI command shows the number of CCI
instances since HORCM was started as follows.
Example without command device security:
# horcctl -DI
Current control device = /dev/rdsk/c0t0d0 AI = 14 TI = 0 CI = 1
Example with command device security:
# horcctl -DI
Current control device = /dev/rdsk/c0t0d0* AI = 14 TI = 0 CI = 1
AI
NUM of actual instances in use
TI
NUM of temporary instances in RAID
CI
NUM of instances using current (own) instance
Verifying the CCI instance number
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 34
Alternate command device function
The CCI software issues commands to the command device via the UNIX/PC raw I/O
interface. If the command device fails in any way, all CCI commands are terminated
abnormally, and you cannot use any commands. Because the use of alternate I/O path is
platform dependent, restrictions are placed upon it. For example, on HP-UX systems,
only devices subject to the LVM can use the alternate path PV-LINK. To avoid command
device failure, CCI supports an alternate command device function.
Note: When you set a redundant path to the command device by using
alternate path software, make sure that path switching occurs only in case of
a failure. For example, you cannot use round robin.
■Denition of alternate command devices: To use an alternate command device,
you must dene two or more command devices for the HORCM_CMD item in the
conguration denition le. When two or more devices are dened, they are
recognized as alternate command devices. Create all alternate command devices
within the same resource group of the same storage system.
■Timing of alternate command devices: When the HORCM receives an error
notication in reply from the operating system via the raw I/O interface, the alternate
command device is used. You can also change to the alternate command device
forcibly by using the horcct1 -C switch command. However, if you specied
HORCM_CMD for the volume belonging to a virtual storage machine, you cannot use
the horcct1 -C switch command, and therefore you cannot switch to the alternate
command device forcibly.
■Operation of alternating command: If the command device is blocked due to online
maintenance, the switch command should be issued in advance. If the switch
command is issued again after completion of the online maintenance, the previous
command device is activated.
■Multiple command devices on HORCM startup: If at least one command device is
available during one or more command devices described to the conguration
denition le, then HORCM can start with a warning message to the startup log by
using the available command device. Conrm that all command devices can be
changed by using the horcctl -C command option, or HORCM has been started
without the warning message to the HORCM startup log.
The following gure shows the alternate command device function.
Alternate command device function
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 35
Remote command device
A remote command device is a command device on an external (UVM) storage system
that is mapped as a command device of the local storage system. When commands are
issued to a remote command device, the UR/URz journal operations are processed using
the UVM FC path between the arrays. Use of a remote command device provides
improved performance for 3DC congurations by providing separate paths for UR/URz
journal processing and data replication.
The remote command device (RCD) requirements are:
■Virtual Storage Platform G1000, G1500, Virtual Storage Platform F1500:
●RCD is required in 3DC TC/UR and 3DC TCz/URz congurations, including intermix
congurations with VSP or USP V/VM.
●RCD is required in 3DC URxUR and 3DC URzxURz congurations, including intermix
congurations with VSP or USP V/VM.
●RCD is not required in GAD 3DC delta resync (GAD+UR) congurations.
■Virtual Storage Platform G200, G400, G600, G800 and Virtual Storage Platform F400,
F600, F800:
●RCD is required in 3DC TC/UR and URxUR congurations.
●RCD is not required in GAD 3DC delta resync (GAD+UR) congurations.
■Virtual Storage Platform: RCD is recommended in 3DC TC/UR and 3DC TCz/URz
congurations. If there is intermix with VSP G1000, G1500 or VSP F1500, RCD is
required.
■Hitachi Unied Storage VM: RCD is recommended in 3DC TC/UR congurations.
The remote command device is dened using Device Manager - Storage Navigator. For
more information, see the Hitachi Universal Volume Manager User Guide.
Remote command device
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 36
CCI and the SCSI command interface
When CCI commands are converted into a special SCSI command format, a SCSI through
driver that can send specially formatted SCSI commands to the RAID storage system is
needed. As a result, OS support for CCI depends on the OS capabilities. It is necessary to
use a read/write command that can easily be issued by many UNIX/PC server platforms.
For example, ioctl() can be used for the following platforms: HP-UX, Linux, Solaris,
Windows, IRIX64, OpenVMS and zLinux.
■SCSI command format used: Use a RD/WR command that can be used with special
LDEVs, since they should be discriminated from the normal RD/WR command.
■Recognition of the control command area (LBA#): The host issues control
commands through the raw I/O special le of a special LDEV. Since the specic LU
(command device) receiving these commands is viewed as a normal disk by the SCSI
interface, the OS can access its local control area. The RAID storage system must
distinguish such accesses from the control command accesses. Normally, several
megabytes of the OS control area are used starting at the initial LBA#. To avoid using
this area, a specic LBA# area is decided and control commands are issued within this
area. The command LBA# recognized by the storage system is shown below, provided
the maximum OS control area is 16 MB.
The following gure shows the relationship of the special le to the special LDEV.
■Acceptance of commands: A command is issued in the LBA area of the special LDEV
explained above. The RD/WR command meeting this requirement should be received
especially as a CCI command. A command is issued in the form of WR or WR-RD.
When a command is issued in the form of RD, it is regarded as an inquiry (equivalent
to a SCSI inquiry), and a CCI recognition character string is returned.
CCI and the SCSI command interface
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 37
Command competition
The CCI commands are asynchronous commands issued via the SCSI interface. As a
result, if several processes issue these commands to a single LDEV, the storage system
cannot take the proper action. To avoid such a problem, two or more write commands
should not be issued to a single LDEV. The command initiators should not issue two or
more write commands to a single LDEV unless the storage system can receive
commands with independent initiator number * LDEV number simultaneously.
The following gure shows the HORCM and command issue process.
Command flow
This gure shows the ow of read/write command control for a specied LBA#.
Issuing commands for LDEVs within a LUSE device
A LUSE device is a group of LDEVs regarded as a single logical unit. Because it is
necessary to know the conguration of the LDEVs when issuing a command, a new
command is used to specify a target LU and acquire LDEV conguration data, as shown
in the following gure.
Command competition
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 38
CCI instance components on the host server
HORCM operational environment
The HORCM operates as a daemon process on the host server and is activated either
automatically when the server machine starts up or manually by the startup script.
HORCM reads the denitions specied in the conguration le upon startup. The
environment variable HORCM_CONF is used to dene the location of the conguration
le to be referenced. The following gure shows the HORCM operational environment.
CCI instance components on the host server
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 39
CCI instance configurations
The basic unit of the CCI software structure is the CCI instance. A CCI instance consists of
HORC manager (HORCM), CCI commands, the user-dened conguration denition le,
and the log function for maintenance. Each instance uses its own conguration denition
le to manage volume relationships while maintaining awareness of the other CCI
instances. Each CCI instance normally resides on separate servers (one node per
instance). If two or more instances are run on a single server (for example, for test
operations), it is possible to activate two or more instances using instance numbers. The
CCI commands to be used are selected by the environment variable (HORCC_MRCF). The
default command execution environment for CCI is TrueCopy.
The CCI instance shown in the following gure has a remote execution link and a
connection to the RAID storage system. The remote execution link is a network
connection to another PC to allow you to execute CCI functions remotely. The connection
between the CCI instance and the storage system illustrates the connection between the
CCI software on the host and the command device. The command device accepts CCI
commands and communicates read and write I/Os between the host and the volumes
on the storage system. The host does not communicate CCI commands directly to the
volumes on the storage system -- the CCI commands always go through the command
device.
The following gure illustrates CCI instance conguration and components.
CCI instance congurations
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 40
The four possible CCI instance congurations are:
■One host connected to one storage system: Connecting one host to one storage
system allows you to maintain multiple copies of your data for testing purposes or as
an oine backup. Each CCI instance has its own operation manager, server software,
and scripts and commands, and each CCI instance communicates independently with
the command device. The RAID storage system contains the command device that
communicates with the CCI instances as well as the primary and secondary volumes
of both CCI instances.
■One host connected to two storage systems: Connecting the host to two storage
systems enables you to migrate data or implement disaster recovery by maintaining
duplicate sets of data in two dierent storage systems. You can implement disaster
recovery solutions by placing the storage systems in dierent geographic areas. Each
CCI instance has its own operation manager, server software, and scripts and
commands, and each CCI instance communicates independently with the command
device. Each RAID storage system has a command device that communicates with
each CCI instance independently. Each storage system contains the primary volumes
of its connected CCI instance and the secondary volumes of the other CCI instance
(located on the same host in this case).
CCI instance congurations
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 41
■Two hosts connected to one storage system: Having two attached hosts to one
storage system, one host for the primary volume and the other host for the
secondary volume, allows you to maintain and administer the primary volumes while
the secondary volumes can be taken oine for testing. The CCI instances of separate
hosts are connected via the LAN so that they can maintain awareness of each other.
The RAID storage system contains the command device that communicates with both
CCI instances (one on each host) and the primary and secondary volumes of both CCI
instances
■Two hosts connected to two storage systems: Two hosts connected to two storage
systems also allows the most exible disaster recovery plan, because both sets of
data are administered by dierent hosts. This guards against storage system failure
as well as host failure.The CCI instances of separate hosts are connected via the LAN
so that they can maintain awareness of each other. Each RAID storage system has a
command device that communicates with each CCI instance independently. Each
storage system contains the primary volumes of its connected CCI instance and the
secondary volumes of the other CCI instance (located on a dierent host in this case).
Host machines that can be paired
When you perform a pair operation, the version of CCI should be the same on the
primary and secondary sites. As a particular application uses HORC, users sometimes
use a HORC volume as the data backup volume for the server. In this case, CCI requires
that the CCI instance correspond to each OS platform that is located on the secondary
site for the pair operation of data backup on the primary servers of each OS platform.
However, it is possible to prepare only one server at a secondary site by supporting CCI
communications among dierent OSs (including the converter for little-endian vs. big-
endian).
The following gure represents CCI's communication among dierent OSs, and the table
below shows the supported communication (32-bit, 64-bit) among dierent OSs. Please
note the following terms that are used in the example:
■RM-H: Value of HORCMFCTBL environment variable for an HP-UX CCI instance on
Windows
■RM-S: Value of HORCMFCTBL environment variable for a Solaris CCI instance on
Windows
Restriction: CCI's communications among dierent operating systems is supported on
HP-UX, Solaris, AIX, Linux, and Windows (this is not supported on Tru64 UNIX/Digital
UNIX). Also, CCI does not require that the HORCMFCTBL environment variable be set—
except for RM-H and RM-S instances (to ensure that the behavior of the operating
system platform is consistent across dierent operating systems).
Host machines that can be paired
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 42
HORCM
HORCM 32 bit HORCM 64 bit
little big little big
32 bit little AV AV AV -
big AV AV AV -
64 bit little AV AV AV -
big - - - -
Configuration definition file
The CCI conguration denition le is a text le that denes a CCI instance. The
connected hosts, volumes and groups known to the CCI instance are dened in the
conguration denition le. Physical volumes (special les) used independently by the
servers are combined when paired logical volume names and group names are given to
them. The conguration denition le describes the correspondence between the
physical volumes used by the servers and the paired logical volumes and the names of
the remote servers connected to the volumes. See the Command Control Interface
Installation and Conguration Guide for instructions on creating the CCI conguration
denition le.
The following gure illustrates the conguration denition of paired volumes.
Conguration denition le
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 43
Conguration le example — UNIX-based servers
Note that # at the beginning of a line indicates a comment.
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
HST1 horcm 1000 3000
HORCM_CMD
#unitID 0... (seq#30014)
#dev_name dev_name dev_name
/dev/rdsk/c0t0d0
#unitID 1... (seq#30015)
#dev_name dev_name dev_name
/dev/rdsk/c1t0d0
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
oradb oradb1 CL1-A 3 1 0
oradb oradb2 CL1-A 3 1 1
oralog oralog1 CL1-A 5 0
oralog oralog2 CL1-A1 5 0
oralog oralog3 CL1-A1 5 1
oralog oralog4 CL1-A1 5 1 h1
HORCM_INST
Conguration denition le
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 44
#dev_group ip_address service
oradb HST2 horcm
oradb HST3 horcm
oralog HST3 horcm
Conguration le example — Windows servers
The following table lists the parameters dened in the conguration le and species the
default value, type, and limit for each parameter.
Parameter Default Type Limit
ip_address None Character string 63 characters
Service None Character string or numeric
value
15 characters
poll (10 ms) 1000 Numeric value1None
timeout (10 ms) 3000 Numeric value1None
dev_name for
HORCM_CMD
None Character string 63 characters
Recommended value
= 8 char. or fewer
dev_name for
HORCM_DEV
None Character string 31 characters
dev_group None Character string 31 characters
Conguration denition le
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 45
Parameter Default Type Limit
Recommended value
= 8 char. or less
port # None Character string 31 characters
target ID None Numeric value17 characters
LU# None Numeric value17 characters
MU# 0 Numeric value17 characters
Serial#2None Numeric value 12 characters
CU:LDEV(LDEV#) None Numeric value 6 characters
dev_name for
HORCM_CMD
None Character string 63 characters
Recommended value
= 8 char. or less
Notes:
1. Use decimal notation for numeric values (not hexadecimal).
2. For VSP G1x00 and VSP F1500, add a “3” at the beginning of the serial number. For
example, for serial number 12345, enter 312345.
Do not edit the conguration denition le while CCI is running. Shut down CCI, edit the
conguration le as needed, and then restart CCI.
When you change the system conguration, it is required to shut down CCI once and
rewrite the conguration denition le to match with the change and then restart CCI.
When you change the storage system conguration (microprogram, cache capacity, LU
path, and so on), you need to restart CCI regardless of the necessity of the conguration
denition le editing.
When you restart CCI, conrm that there is no contradiction in the connection
conguration by using the -c option of pairdisplay command and raidqry
command. But you cannot conrm the consistency of the P-VOL and S-VOL capacity with
the -c option of pairdisplay command. Conrm the capacity of each volume by using
the raidcom command.
Do not mix pairs created with the "At-Time Split" option (-m grp) and pairs created
without this option in the same group dened in the CCI conguration le. If you do, a
pairsplit operation might end abnormally, or S-VOLs of the P-VOLs in the same
consistency group (CTG) might not be created correctly at the time the pairsplit
request is received.
Conguration denition le
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 46
Configuration definition file settings
This section describes the settings in the conguration denition le:
■HORCM_MON (on page 47)
■HORCM_CMD (in-band method) (on page 48)
■HORCM_CMD (out-of-band method) (on page 53)
■HORCM_DEV (on page 56)
■HORCM_INST (on page 59)
■HORCM_LDEV (on page 60)
■HORCM_LDEVG (on page 61)
■HORCM_INSTP (on page 62)
■HORCM_ALLOW_INST (on page 62)
HORCM_MON
The monitor parameter (HORCM_MON) denes the following values:
■Ip_address: Species the local host name or the IP address of the local host. When
you specify the name of a local host that has multiple IP addresses, one of the IP
addresses is selected at random and used. If you want to use all IP addresses, specify
NONE for IPv4 or NONE6 for IPv6.
■Service: Species the UDP port name assigned to the HORCM communication path,
which is registered in "/etc/services" ("%windir%\system32\drivers\etc\services" in
Windows, "SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT" in OpenVMS). If a port
number is specied instead of a port name, the port number will be used.
■Poll: The interval for monitoring paired volumes. To reduce the HORCM daemon load,
make this interval longer. If set to -1, the paired volumes are not monitored. The value
of -1 is specied when two or more CCI instances run on a single machine.
■Timeout: The time-out period of communication with the remote server.
If HORCM_MON is not specied, then the following are set as defaults.
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE default_port 1000 3000H
Default_port:
For none specied HORCM instance: "31000 + 0"
For instance HORCM X : "31000 + X + 1"
Conguration denition le settings
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 47
HORCM_CMD (in-band method)
When using the in-band method, dene the UNIX device path or Windows physical
device number and specify a command device that can be accessed by CCI for
HORCM_CMD. You can specify multiple command devices in HORCM_CMD to provide
failover in case the original command device becomes unavailable.
Tip: To enhance redundancy, you can make multiple command devices
available for a single storage system. This conguration is called command
device alternative conguration. For this conguration, command devices are
listed horizontally in a line in the conguration denition le. CMD1 and
CMD2 in the following example are command devices of the same storage
system:
HORCM_CMD
CMD1 CMD2
Aside from the command device alternative conguration, to control multiple
storage systems in one conguration denition le, you can list command
devices of each storage system in one conguration denition le. In this
case, command devices are listed vertically. CMD1 and CMD2 in the following
example are command devices of dierent storage systems:
HORCM_CMD
CMD1
CMD2
The command device must be mapped to the iSCSI/Fibre using LUN Manager rst. The
mapped command devices can be identied by the "-CM" at the end of product ID
displayed by the inqraid command. The following are the examples for the inqraid
command.
Example for the inqraid command (UNIX host)
# ls /dev/rdsk/c1t0* | /HORCM/usr/bin/inqraid -CLI -sort
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
c1t0d0s2 CL2-E 63502 576 - - - - OPEN-V-CM
c1t0d1s2 CL2-E 63502 577 - s/s/ss 0006 1:02-01 OPEN-V -SUN
c1t0d2s2 CL2-E 63502 578 - s/s/ss 0006 1:02-01 OPEN-V -SUN
The command device is /dev/rdsk/c1t0d2s2.
HORCM_CMD (in-band method)
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 48
Example for the inqraid command (Windows host)
D:\HORCM\etc>inqraid $Phys -CLI
\\.\PhysicalDrive1:
# Harddisk1 -> [VOL61459_449_DA7C0D92] [OPEN-3 ]
\\.\PhysicalDrive2:
# Harddisk2 -> [VOL61459_450_DA7C0D93] [OPEN-3-CM ]
The command device is \\.\PhysicalDrive2.
After the process of command device mapping, set HORCM_CMD of the conguration
denition le as follows.
\\.\CMD-<Serial Number>:<Device special file name>
<Serial Number>: Sets the serial number. For VSP G1x00 and VSP F1500, add a “3” at the
beginning of the serial number. For example, for serial number 12345, enter 312345.
<Device special le name>: Sets the device special le name of a command device.
Example with serial number 64015 and device special le name, /dev/rdsk/*is
specied:
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-64015:/dev/rdsk/*
Caution: To enable dual path of the command device under UNIX systems,
make sure to include all paths to the command device on a single line in the
HORCM_CMD section of the conguration denition le. Entering path
information on separate lines might cause syntax parsing issues, and failover
might not occur unless the HORCM startup script is restarted on the UNIX
system.
When two or more storage systems are connected, CCI identies each storage system
using unit IDs. The unit ID is assigned sequentially in the order described in
HORCM_CMD of the conguration denition le. For a command device alternative
conguration, a special le for multiple command devices is written.
Caution: When storage systems are shared by two or more servers, unit IDs
and serial numbers must be consistent among the servers. List serial
numbers of the storage systems in HORCM_CMD of the conguration
denition le in the same order. The following gure illustrates unit IDs when
multiple servers share multiple storage systems.
HORCM_CMD (in-band method)
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 49
The following gure shows the conguration and unit IDs for multiple storage systems.
Specifying command devices for Windows 2000, 2003, 2008, and 2012
Normally, physical drives are specied for command devices in storage systems.
However, CCI provides a method that is not aected by changes of physical drives in
Windows 2000, 2003, 2008, and 2012 by using the following naming format to specify the
serial number, LDEV number, and port number in that order:
\\.\CMD-Ser#-ldev#-Port#
Note: For VSP G1x00 and VSP F1500, add a "3" to the beginning of the serial
number (for example, enter "312345" for serial number "12345").
Specifying command devices for Windows 2000, 2003, 2008, and 2012
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 50
The following example species 30095 for the storage system's serial number, 250 for
the LDEV number, and CL1-A for the port number:
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-30095-250-CL1-A
■Minimum specication
For the command device with serial number 30095, specify as follows:
\\.\CMD-30095
■Command devices in the multi-path environment
Specify serial number 30095, and LDEV number 250 as follows:
\\.\CMD-30095-250
■Other specications
Specify serial number 30095, LDEV number 250, and port number CLI-A as follows:
\\.\CMD-30095-250-CL1-A
or
\\.\CMD-30095-250-CL1
Specifying command devices for UNIX
Device les are specied for command devices in UNIX. However, CCI provides a method
that is not aected by changes of device les in UNIX by using the following naming
format specifying the serial number, LDEV number, and port number in that order:
\\.\CMD-Ser#-ldev#-Port#:HINT
Note: For VSP G1x00 and VSP F1500, add a "3" to the beginning of the serial
number (for example, enter "312345" for serial number "12345").
The following example species 30095 for the storage system's serial number, 250 for
the LDEV number, and CL1-A for the port number:
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-30095-250-CL1-A:/dev/rdsk/
Specifying command devices for UNIX
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 51
HINT provides a path to scan and species a directory ending with a slash (/) or a name
pattern including the directory. Device les are searched via a name lter similar to the
inqraid command.
■To nd command devices from /dev/rdsk/, enter: ' /dev/rdsk/*
■To nd command devices from /dev/rdsk/c10, enter: ' /dev/rdsk/c10*
■To nd command devices from /dev/rhdisk, enter: ' /dev/rhdisk*
For a command device alternative conguration, HINT of the second command device
can be omitted. In this case, command devices are searched from the device le that was
scanned rst.
HORCM_CMD
#dev_name dev_name dev_name
\\.\ CMD-30095-CL1:/dev/rdsk/ \\.\ CMD-30095-CL2
■Minimum specication: For the command device of a storage system with serial
number 30095, specify as follows.
\\.\CMD-30095:/dev/rdsk/
■Command devices in the multi-path environment: Specify storage system’s serial
number 30095 and LDEV number 250 as follows.
\\.\CMD-30095-250:/dev/rdsk/
■Other specications: An alternate path with storage system’s serial number 30095
and LDEV number 250 can be specied as follows.
\\.\CMD-30095-250-CL1:/dev/rdsk/ \\.\CMD-30095-250-CL2
\\.\CMD-30095:/dev/rdsk/c1 \\.\CMD-30095:/dev/rdsk/c2
Specifying command devices for UNIX
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 52
Note: If the hardware conguration is changed during the time an OS is
running in Linux, the name of a special le corresponding to the command
device might be changed. At this time, if HORCM was started by specifying the
special le name in the conguration denition le, HORCM cannot detect the
command device, and the communication with the storage system might fail.
To prevent this failure, specify the path name allocated by udev to the
conguration denition le before booting HORCM. Use the following
procedure to specify the path name. In this example, the path name
for /dev/sdgh can be found.
1. Find the special le name of the command device by using inqraid
command. Command example:
[root@myhost ~]# ls /dev/sd* | /HORCM/usr/bin/inqraid -
CLI | grep CM sda CL1-B 30095 0 - - 0000 A:00000 OPEN-V-
CM sdgh CL1-A 30095 0 - - 0000 A:00000 OPEN-V-CM
[root@myhost ~]#
2. Find the path name from the by-path directory. Command example:
[root@myhost ~]# ls -l /dev/disk/by-path/ | grep sdgh
lrwxrwxrwx. 1 root root 10 Jun 11 17:04 2015
pci-0000:08:00.0- fc-0x50060e8010311940-lun-0 -> ../../
sdgh [root@myhost ~]#
In this example, "pci-0000:08:00.0-fc-0x50060e8010311940-lun-0" is the
path name.
3. Enter the path name to HORCM_CMD in the conguration denition le
as follows.
HORCM_CMD /dev/disk/by-path/pci-0000:08:00.0-
fc-0x50060e8010311940-lun-0
4. Boot the HORCM instance as usual.
HORCM_CMD (out-of-band method)
When executing commands using the out-of-band method, use a virtual command
device instead of a command device. By specifying the location to create a virtual
command device in HORCM_CMD, you can create a virtual command device.
The location where the virtual command device can be created is dierent according to
the type of the storage system. For details about locations, see System conguration
using CCI.
HORCM_CMD (out-of-band method)
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 53
To create a virtual command device on an SVP (VSP, HUS VM, VSP G1x00 and
VSP F1500)
Specify the following to HORCM_CMD of the conguration denition le.
\\.\IPCMD-<SVP IP address>-<UDP communication port number>[-Unit ID]
■<SVP IP address>: Sets an IP address of SVP.
■<UDP communication port number>: Sets the UDP communication port number. This
value (31001) is xed.
■[-Unit ID]: Sets the unit ID of the storage system for the multiple units connection
conguration. This can be omitted.
To create a virtual command device on the maintenance utility (VSP Gx00 models,
VSP Fx00 models)
Specify the following to HORCM_CMD of the conguration denition le:
\\.\IPCMD-<GUM IP address>-<UDP communication port number>[-Unit ID]
■<GUM IP address>: Sets an IP address of the maintenance utility (GUM).
■<UDP communication port number>: Sets the UDP communication port number.
These values (31001 and 31002) are xed.
■[-Unit ID]: Sets the unit ID of the storage system for the multiple units connection
conguration. This can be omitted.
Note: To use the maintenance utility, we recommend that you set the
combination of all GUM IP addresses in the storage system and the UDP
communication port numbers by an alternative conguration. See the
following examples for how to set the combination.
Using a CCI server port as a virtual command device:
Specify the following in HORCM_CMD of the conguration denition le:
\\.\IPCMD-<CCI server IP address>-<CCI port number>[-Unit ID]
■<CCI server IP address>: Sets the IP address of the CCI server.
■<CCI port number>: Sets the CCI port number.
■[-Unit ID]: Sets the unit ID of the storage system for the multiple units connection
conguration. This can be omitted.
Example for the case of IPv4
HORCM_CMD
#dev_name dev_name dev_name
\\.\IPCMD-158.214.135.113-31001
To create a virtual command device on an SVP (VSP, HUS VM, VSP G1x00 and VSP F1500)
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 54
Example for the case of IPv6
HORCM_CMD
#dev_name dev_name dev_name
\\.\IPCMD-fe80::209:6bff:febe:3c17-31001
Example for the case when both the in-band and out-band methods are used
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-64015:/dev/rdsk/* \\.\IPCMD-158.214.135.113-31001
Example for the case when both the in-band and out-band methods are used in a
command device alternative conguration
HORCM_CMD
#dev_name dev_name
\\.\CMD-64015:/dev/rdsk/* \\.\IPCMD-158.214.135.113-31001
HORCM_CMD
#dev_name dev_name
\\.\IPCMD-158.214.135.113-31001 \\.\CMD-64015:/dev/rdsk/*
Example for the case of virtual command devices in a cascade conguration (three
units)
HORCM_CMD
#dev_name dev_name dev_name
\\.\IPCMD-158.214.135.113-31001
\\.\IPCMD-158.214.135.114-31001
\\.\IPCMD-158.214.135.115-31001
Example for case of alternative conguration of the combination of all GUM IP
addresses in the storage system and the UDP communication port numbers. In this
case, enter the IP address without a line feed
HORCM_CMD
#dev_name dev_name dev_name
\\.\IPCMD-192.168.0.16-31001
\\.\IPCMD-192.168.0.17-31001
\\.\IPCMD-192.168.0.16-31002
\\.\IPCMD-192.168.0.17-31002
An IP address and a port number can be expressed using a host name and a service
name.
Using a CCI server port as a virtual command device:
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 55
HORCM_DEV
The device parameter (HORCM_DEV) denes the RAID storage system device addresses
for the paired logical volume names. When the server is connected to two or more
storage systems, the unit ID is expressed by port# extension. Each group name is a
unique name discriminated by a server that uses the volumes, the attributes of the
volumes (such as database data, redo log le, UNIX le), recovery level, etc. The group
and paired logical volume names described in this item must reside in the remote server.
The hardware iSCSI/Fibre port, target ID, and LUN as hardware components need not be
the same.
The following values are dened in the HORCM_DEV parameter:
dev_group
Names a group of paired logical volumes. A command is executed for all
corresponding volumes according to this group name.
dev_name
Names the paired logical volume within a group (that is, name of the special le or
unique logical volume). The name of paired logical volume must be dierent to
the dev name in another group.
Port#
Denes the RAID storage system port number of the volume that connects to the
dev_name volume. The following "n" shows unit ID when the server is connected
to two or more storage systems (for example, CL1-A1 = CL1-A in unit ID 1). If the
"n" option is omitted, the unit ID is 0. The port is not case sensitive (for example,
CL1-A = cl1-a = CL1-a = cl1-A).
- Basic Option Option Option
CL1 A
n
B
n
C
n
Dn E
n
F
n
G
n
Hn Jn K
n
L
n
Mn Nn P
n
Qn R
n
CL2 A
n
B
n
C
n
Dn E
n
F
n
G
n
Hn Jn K
n
L
n
Mn Nn P
n
Qn R
n
The following ports can be specied only for the 9900V:
- Basic Option Option Option
CL3 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
qn rn
CL4 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
qn rn
HORCM_DEV
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 56
For 9900V, CCI supports four types of port names for host groups:
■Specifying the port name without a host group: CL1-A CL1-An, where n is the
unit ID if there are multiple RAID storage systems
■Specifying the port name with a host group: CL1-A-g, where g is the host group
CL1-An-g, where n-g is the host group g on CL1-A in unit ID=n
The following ports can be specied for USP V/VM and TagmaStore USP/
TagmaStore NSC:
- Basic Option Option Option
CL5 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CL6 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CL7 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CL8 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CL9 a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLA a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLB a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLC a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLD a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLE a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLF a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
CLG a
n
b
n
cn dn e
n
fn g
n
hn jn k
n
ln mn nn p
n
q
n
rn
Target ID
Denes the iSCSI/Fibre target ID (TID) number of the physical volume on the
specied port.
HORCM_DEV
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 57
LU#
Denes the iSCSI/Fibre logical unit number (LU#) of the physical volume on the
specied target ID and port.
Note: In case of bre channel, if the TID and LU# displayed on the
system are dierent than the TID on the bre address conversion
table, then you must use the TID and LU# indicated by the raidscan
command in the CCI conguration le.
MU# for ShadowImage (HOMRCF)
Denes the mirror unit number (0 - 2) to use the redundant mirror for the
identical LU on the ShadowImage. If this number is omitted, it is assumed to be
(MU#0). The cascaded mirroring of the S-VOL is expressed as virtual volumes
using the mirror descriptors (MU#1-2) in the conguration denition le. The
MU#0 of a mirror descriptor is used for connection of the S-VOL. The mirror
descriptor (MU#0-2) can be used in ShadowImage and Copy-on-Write Snapshot.
MU#3-63 can be used in Copy-on-Write Snapshot only.
Note: When you enter the MU number for a ShadowImage/Copy-on-
Write Snapshot pair into the conguration denition le, enter only the
number, for example, “0” or “1”.
Feature
SMPL P-VOL S-VOL
MU#0-2 MU#3 - 63 MU#0-2 MU#3 - 63
MU#
0 MU#1 - 63
ShadowImage Valid Not valid Valid Not valid Valid Not valid
Copy-on-Write
Snapshot
Valid Valid Valid Valid Valid Not valid
MU# for TrueCopy/Universal Replicator/global-active device
Denes the mirror unit number (0 - 3) if using redundant mirror for the identical
LU on TC/UR/GAD. If this number is omitted, it is assumed to be (MU#0). You can
specify only MU#0 for TrueCopy, and 4 MU numbers (MU#0 - 3) for Universal
Replicator and global-active device.
Note: When you enter the MU number for a TC/UR/GAD pair into the
conguration denition le, add an "h" before the number, for
example, "h0" or "h1".
HORCM_DEV
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 58
Feature
SMPL P-VOL S-VOL
MU#0 MU#1 - 3 MU#0 MU#1 - 3 MU#0 MU#1 - 3
TrueCop
y
Valid Not valid Valid Not valid Valid Not valid
UR Valid Valid Valid Valid Valid Valid
HORCM_INST
The instance parameter (HORCM_INST) denes the network address (IP address) of the
remote server (active or standby). It is used to view or change the status of the paired
volume in the remote server (active or standby). When the primary volume is shared by
two or more servers, there are two or more remote servers using the secondary volume.
Thus, it is necessary to describe the addresses of all of these servers.
The following values are dened in the HORCM_INST parameter:
dev_group
The server name described in dev_group of HORC_DEV.
ip_address
The network address of the specied remote server.
service
The port name assigned to the HORCM communication path (registered in
the /etc/services le). If a port number is specied instead of a port name, the port
number will be used.
A conguration for multiple networks can be found using the raidqry -r <group>
command on each host. The current HORCM network address can be changed using
horcctl -NC <group> on each host.
When you use all IP addresses of the local host in a conguration for multiple networks,
specify NONE (for IPv4) or NONE6 (for IPv6) to the ip_address of the HORCM_MON
parameter.
See the gure below for conguration for multiple networks.
HORCM_INST
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 59
HORCM_LDEV
The HORCM_LDEV parameter is used for specifying stable LDEV# and Serial# as the
physical volumes corresponding to the paired logical volume names. Each group name is
unique and typically has a name tting its use (for example, database data, Redo log le,
UNIX le). The group and paired logical volume names described in this item must also
be known to the remote server.
dev_group
This parameter is the same as HORCM_DEV parameter.
dev_name
This parameter is the same as HORCM_DEV parameter.
MU#
This parameter is the same as HORCM_DEV parameter.
Serial#
This parameter is used to specify the serial number of RAID box. For VSP G1x00
and VSP F1500, add a “3” at the beginning of the serial number. For example, for
serial number 12345, enter 312345.
HORCM_LDEV
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 60
CU:LDEV(LDEV#)
This parameter is used to describe the LDEV number in the RAID storage system
and supports three types of format as LDEV#.
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
oradb dev1 30095 02:40 0
oradb dev2 30095 02:41 0
■Specifying "CU:LDEV" in hex.
Example for LDEV# 260:
01:04
■Specifying "LDEV" in decimal used by the CCI inqraid command.
Example for LDEV# 260:
260
■Specifying "LDEV" in hex used by the CCI inqraid command.
Example for LDEV# 260:
0x104
Note: The HORCM_LDEV format can only be used on the
TagmaStore USP/TagmaStore NSC. LDEV# will be converted to
"Port#, Targ#, Lun#" mapping to this LDEV internally, because the
RAID storage system needs to specify "Port#, Targ#, Lun#" for the
target device. This feature is TagmaStore USP/TagmaStore NSC
microcode dependent; if HORCM fails to start, HORCM_DEV needs
to be used.
HORCM_LDEVG
The HORCM_LDEVG parameter denes the device group information that the CCI
instance reads. For details about device group, see LDEV grouping function.
The following values are dened.
Copy group
Species a name of copy group. This is equivalent to the dev_group of
HORCM_DEV and HORCM_LDEV parameters.
CCI operates by using the information dened here.
ldev_group
Species a name of device group that the CCI instance reads.
HORCM_LDEVG
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 61
Serial#:
Species a storage system serial number. For VSP G1x00 and VSP F1500, add a “3”
at the beginning of the serial number. For example, for serial number 12345, enter
312345.
HORCM_LDEVG
#Copy_Group ldev_group Serial#
ora grp1 64034
HORCM_INSTP
The HORCM_INSTP parameter is used when specifying a path ID for the link of TrueCopy/
Universal Replicator/global-active device as well as HORCM_INST parameter. You can
specify from 1 to 255 for the path ID. If you do not specify the Path ID, the behavior is the
same as when 'HORCM_INST' is used.
HORCM_INSTP
dev_group ip_address service pathID
VG01 HSTA horcm 1
VG02 HSTA horcm 2
Note: The path ID can be specied at TrueCopy, Universal Replicator,
Universal Replicator for Mainframe, and global-active device. However, the
path ID cannot be specied at UR/URz when connecting USP V/VM and USP/
NSC. The same path ID must be specied between the site of P-VOL and S-
VOL because the path ID is used at the paircreate command.
HORCM_ALLOW_INST
The HORCM_ALLOW_INST parameter is used to restrict the users using the virtual
command device. The allowed IP addresses and port numbers are as follows.
For IPv4
HORCM_ALLOW_INST
#ip_address service
158.214.135.113 34000
158.214.135.114 34000
For IPv6
HORCM_ALLOW_INST
#ip_address service
fe80::209:6bff:febe:3c17 34000
Note: Note: If CCI clients not dened HORCM_ALLOW_INST, HORCM instance
starting up is rejected by SCSI check condition (SKEY=0x05, ASX=0xfe) and CCI
cannot be started up.
HORCM_INSTP
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 62
Correspondence of the configuration definition file for cascading
volume and mirror descriptors
The CCI software (HORCM) is capable of keeping a record of the multiple pair
congurations per LDEV. CCI distinguishes the records of the each pair conguration by
MU#. You can assign 64 MU#s for local copy products and 4 MU#s for remote copy
products as the following gure, you can dene up to 68 device groups (records of pair
conguration) in the conguration denition le.
See the following gure for management of pair conguration by mirror descriptors.
Correspondence of configuration file and mirror descriptors
The group name and MU# that are noted in the HORCM_DEV section of the
conguration denition le are assigned to the corresponding mirror descriptors. This
outline is described in the following table. "Omission of MU#" is handled as MU#0, and
the specied group is registered to MU#0 on ShadowImage/Copy-on-Write Snapshot and
TrueCopy/Universal Replicator/global-active device. Also, when you note the MU# in
HORCM_DEV, the sequence of the MU# can be random (for example, 2, 1, 0).
Correspondence of the conguration denition le for cascading volume and mirror descriptors
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 63
HORCM_DEV parameter in configuration
file
MU#0
ShadowIm
age (Copy-
on-Write
Snapshot)
only UR/GAD
TC/
UR/GAD SI
MU#1-#2
(MU#3-
#63)
MU#1-
#3
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1
oradev1 oradev
1
- -
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1
Oradb1 oradev11 CL1-D 2
1 1
Oradb2 oradev21 CL1-D 2
1 2
oradev1 oradev
1
oradev11
oradev21
-
Correspondence of conguration le and mirror descriptors
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 64
HORCM_DEV parameter in configuration
file
MU#0
ShadowIm
age (Copy-
on-Write
Snapshot)
only UR/GAD
TC/
UR/GAD SI
MU#1-#2
(MU#3-
#63)
MU#1-
#3
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1
Oradb1 oradev11 CL1-D 2
1 0
Oradb2 oradev21 CL1-D 2
1 1
Oradb3 oradev31 CL1-D 2
1 2
oradev1 oradev
11
oradev21
oradev31
-
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1 0
- oradev
1
- -
Correspondence of conguration le and mirror descriptors
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 65
HORCM_DEV parameter in configuration
file
MU#0
ShadowIm
age (Copy-
on-Write
Snapshot)
only UR/GAD
TC/
UR/GAD SI
MU#1-#2
(MU#3-
#63)
MU#1-
#3
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1 h0
oradev1 - - -
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1 0
Oradb1 oradev1 CL1-D 2
1 1
Oradb2 oradev21 CL1-D 2
1 2
- oradev
1
oradev11
oradev21
-
Correspondence of conguration le and mirror descriptors
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 66
HORCM_DEV parameter in configuration
file
MU#0
ShadowIm
age (Copy-
on-Write
Snapshot)
only UR/GAD
TC/
UR/GAD SI
MU#1-#2
(MU#3-
#63)
MU#1-
#3
HORCM_DEV
#dev_group dev_name port#
TargetID LU# MU#
Oradb oradev1 CL1-D 2
1
Oradb1 oradev11 CL1-D 2
1 0
Oradb2 oradev21 CL1-D 2
1 h1
Oradb3 oradev31 CL1-D 2
1 h2
Oradb4 oradev41 CL1-D 2
1 h3
oradev1 oradev
11
- oradev2
1
oradev3
1
oradev4
1
Cascading connection and configuration files
A volume of the cascading connection describes entity in a conguration denition le
on the same instance, and classies connection of volume through the mirror descriptor.
In case of TrueCopy/ShadowImage cascading connection, too, the volume entity
describes to a conguration denition le on the same instance. The following gure
shows an example.
Cascading connection and conguration les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 67
ShadowImage
Since ShadowImage is a mirrored conguration within one storage system, it can be
described as a volume of the cascading connection according to two conguration
denition les. For a ShadowImage-only cascading connection, the specied group is
assigned to the mirror descriptor (MU#) of ShadowImage, specically dening "0" as the
MU# for ShadowImage. The following gures show ShadowImage cascading
congurations and the pairdisplay information for each conguration.
Pairdisplay on HORCMINST0
ShadowImage
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 68
Pairdisplay on HORCMINST1
Pairdisplay on HORCMINST0
Cascading connections for TrueCopy and ShadowImage
The cascading connections for TrueCopy/ShadowImage can be set up by using three
conguration denition les that describe the cascading volume entity in a conguration
denition le on the same instance. The mirror descriptor of ShadowImage and
TrueCopy denitely describe "0" as MU#, and the mirror descriptor of TrueCopy does not
describe "0" as MU#.
Cascading connections for TrueCopy and ShadowImage
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 69
TrueCopy/ShadowImage cascading connection and conguration le
The following gures show TrueCopy/ShadowImage cascading congurations and the
pairdisplay information for each conguration.
Pairdisplay for TrueCopy on HOST1
Cascading connections for TrueCopy and ShadowImage
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 70
Pairdisplay for TrueCopy on HOST2 (HORCMINST)
Pairdisplay for ShadowImage on HOST2 (HORCMINST)
Cascading connections for TrueCopy and ShadowImage
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 71
Pairdisplay for ShadowImage on HOST2 (HORCMINST0)
CCI software files
The CCI software consists of les supplied with the software, log les created internally,
and les created by the user. These les are stored on the local disk in the server
machine.
■CCI les supplied with the software (on page 72)
■CCI log and trace les (on page 79)
■User environment variable (on page 89)
CCI files supplied with the software
■CCI les for UNIX-based systems (on page 72)
■CCI les for Windows-based systems (on page 74)
■CCI les for OpenVMS-based systems (on page 77)
CCI files for UNIX-based systems
Title File name
Command
name
Mod
e User*
Grou
p
HORCM /etc/horcmgr horcmd 0544 root sys
HORCM_CONF /HORCM/etc/horcm.conf - 0444 root sys
Takeover /usr/bin/horctakeover horctakeover 0544 root sys
CCI software les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 72
Title File name
Command
name
Mod
e User*
Grou
p
Accessibility
check
/usr/bin/paircurchk paircurchk 0544 root sys
Pair
generation
/usr/bin/paircreate paircreate 0544 root sys
Pair splitting /usr/bin/pairsplit pairsplit 0544 root sys
Pair
resynchronizat
ion
/usr/bin/pairresync pairresync 0544 root sys
Event waiting /usr/bin/pairevtwait pairevtwait 0544 root sys
Error
notication
/usr/bin/pairmon pairmon 0544 root sys
Volume check /usr/bin/pairvolchk pairvolchk 0544 root sys
Pair
conguration
conrmation
/usr/bin/pairdisplay pairdisplay 0544 root sys
RAID scanning /usr/bin/raidscan raidscan 0544 root sys
RAID activity
reporting
/usr/bin/raidar raidar 0544 root sys
Connection
conrming
/usr/bin/raidqry raidqry 0544 root sys
Trace control /usr/bin/horcctl horcctl 0544 root sys
HORCM
activation
script
/usr/bin/horcmstart.sh horcmstart.sh 0544 root sys
HORCM
shutdown
script
/usr/bin/horcmshutdown.sh horcmshutdow
n.sh
0544 root sys
Connection
conrming
/HORCM/usr/bin/inqraid -- 0544 root sys
Synchronous
waiting
/usr/bin/pairsyncwait pairsyncwait 0544 root sys
Conguration
setting and
conrming
command
/HORCM/usr/bin/raidcfg raidcfg 0544 root sys
CCI les for UNIX-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 73
Title File name
Command
name
Mod
e User*
Grou
p
Text ltering /HORCM/usr/bin/rmawk rmawk 0544 root sys
DB Validator
setting
/usr/bin/raidvchkset raidvchkset 0544 root sys
DB Validator
conrmation
/usr/bin/raidvchkdsp raidvchkdsp 0544 root sys
DB Validator
conrmation
/usr/bin/raidvchkscan raidvchkscan 0544 root sys
Storage
Replication
Adapter
/HORCM/usr/bin/rmsra rmsra 0544 root sys
Conguration
setting
command
HORCM/usr/bin/raidcom raidcom 0544 root sys
A le for
management
/HORCM/etc/
Raidcom_Dic_Raid_RM_Patch.
txt
- 0444 root sys
A le for
management
/HORCM/etc/
Raidcom_Help_Raid_RM.txt
- 0444 root sys
A le for
management
/HORCM/etc/
Raidcom_Dic_Raid_RM.txt
- 0444 root sys
* For information and instructions for changing the UNIX user for the CCI software, see
the Command Control Interface Installation and Conguration Guide.
CCI files for Windows-based systems
Title File name
Command
name
HORCM \HORCM\etc\horcmgr.exe horcmd
HORCM_CONF \HORCM\etc\horcm.conf -
Takeover \HORCM\etc\horctakeover.exe horctakeover
Accessibility check \HORCM\etc\paircurchk.exe paircurchk
Pair generation \HORCM\etc\paircreate.exe paircreate
Pair split \HORCM\etc\pairsplit.exe pairsplit
CCI les for Windows-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 74
Title File name
Command
name
Pair re-synchronization \HORCM\etc\pairresync.exe pairresync
Event waiting \HORCM\etc\pairevtwait.exe pairevtwait
Error notication \HORCM\etc\pairmon.exe pairmon
Volume checking \HORCM\etc\pairvolchk.exe pairvolchk
Pair conguration
conrmation
\HORCM\etc\pairdisplay.exe pairdisplay
RAID scanning \HORCM\etc\raidscan.exe raidscan
RAID activity reporting \HORCM\etc\raidar.exe raidar
Connection conrmation \HORCM\etc\raidqry.exe raidqry
Trace control \HORCM\etc\horcctl.exe horcctl
HORCM activation script \HORCM\etc\horcmstart.exe horcmstart
HORCM shutdown script \HORCM\etc\horcmshutdown.exe horcmshutd
own
Synchronous waiting \HORCM\etc\pairsyncwait.exe pairsyncwait
Connection conrmation \HORCM\etc\inqraid.exe inqraid
Conguration setting and
conrming command
\HORCM\Tool\mkconf.exe mkconf
Text ltering \HORCM\Tool\rmawk.exe rmawk
Oracle Validation setting \HORCM\etc\raidvchkset.exe raidvchkset
Oracle Validation
conrmation
\HORCM\etc\raidvchkdsp.exe raidvchkdsp
Oracle Validation
conrmation
\HORCM\etc\raidvchkscan.exe raidvchkscan
Conguration setting
command
\HORCM\etc\raidcom.exe raidcom
A le for management \HORCM\etc
\Raidcom_Dic_Raid_RM_Patch.txt
-
A le for management \HORCM\etc\Raidcom_Help_Raid_RM.txt -
A le for management \HORCM\etc\Raidcom_Dic_Raid_RM.txt -
Tool \HORCM\Tool\chgacl.exe chgacl
CCI les for Windows-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 75
Title File name
Command
name
Tool \HORCM\Tool\svcexe.exe svcexe
Sample script for svcexe \HORCM\Tool\HORCM0_run.txt -
Tool \HORCM\Tool\TRCLOG.bat TRCLOG
Storage Replication Adapter \HORCM\etc\rmsra.exe rmsra
Takeover \HORCM\usr\bin\horctakeover.exe horctakeover
Accessibility check \HORCM\usr\bin\paircurchk.exe paircurchk
Pair generation \HORCM\usr\bin\paircreate.exe paircreate
Pair split \HORCM\usr\bin\pairsplit.exe pairsplit
Pair re-synchronization \HORCM\usr\bin\pairresync.exe pairresync
Event waiting \HORCM\usr\bin\pairevtwait.exe pairevtwait
Volume check \HORCM\usr\bin\pairvolchk.exe pairvolchk
Synchronous waiting \HORCM\usr\bin\pairsyncwait.exe pairsyncwait
Pair conguration
conrmation
\HORCM\usr\bin\pairdisplay.exe pairdisplay
RAID scanning \HORCM\usr\bin\raidscan.exe raidscan
Connection conrmation \HORCM\usr\bin\raidqry.exe raidqry
Oracle Validation setting \HORCM\usr\bin\raidvchkset.exe raidvchkset
Oracle Validation
conrmation
\HORCM\usr\bin\raidvchkdsp.exe raidvchkdsp
Oracle Validation
conrmation
\HORCM\usr\bin\raidvchkscan.exe raidvchkscan
Conguration setting and
conrming command
\HORCM\usr\bin\raidcfg.exe raidcfg
CCI les for Windows-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 76
Note:
■The \HORCM\etc\ commands are used from the console window. If these
commands are executed without an argument, the interactive mode will
start up.
■The \HORCM\usr\bin commands have no console window, and can
therefore be used from the application.
■The \HORCM\usr\bin commands do not support the directory mounted
volumes in subcommands.
■\HORCM\Tool\TRCLOG.bat is a troubleshooting tool. This tool is not usually
used.
■\HORCM\etc\rmsra.exe is the binary data used for cooperation with
VMware. This is used directly by VMware, not usually used by users.
CCI files for OpenVMS-based systems
Title File name
Command
name
Use
r
HORCM $ROOT:[HORCM.etc]horcmgr.exe horcmd sys
HORCM_CONF $ROOT:[HORCM.etc]horcm.conf - sys
Takeover $ROOT:
[HORCM.usr.bin]horctakeover.exe
horctakeover sys
Volume accessibility
check
$ROOT:
[HORCM.usr.bin]paircurchk.exe
paircurchk sys
Pair generation $ROOT:
[HORCM.usr.bin]paircreate.exe
paircreate sys
Pair splitting $ROOT:[HORCM.usr.bin]pairsplit.exe pairsplit sys
Pair re-synchronization $ROOT:
[HORCM.usr.bin]pairresync.exe
pairresync sys
Event waiting $ROOT:
[HORCM.usr.bin]pairevtwait.exe
pairevtwait sys
Error notication $ROOT:[HORCM.usr.bin]pairmon.exe pairmon sys
Volume checking $ROOT:
[HORCM.usr.bin]pairvolchk.exe
pairvolchk sys
Pair cong.
conrmation
$ROOT:
[HORCM.usr.bin]pairdisplay.exe
pairdisplay sys
RAID scan $ROOT:[HORCM.usr.bin]raidscan.exe raidscan sys
RAID activity report $ROOT:[HORCM.usr.bin]raidar.exe raidar sys
CCI les for OpenVMS-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 77
Title File name
Command
name
Use
r
Connection
conrmation
$ROOT:[HORCM.usr.bin]raidqry.exe raidqry sys
Trace control $ROOT:[HORCM.usr.bin]horcctl.exe horcctl sys
HORCM activation
script
$ROOT:
[HORCM.usr.bin]horcmstart.exe
horcmstart.sh sys
HORCM shutdown
script
$ROOT:
[HORCM.usr.bin]horcmshutdown.exe
horcmshutdow
n.sh
sys
Connection
conrmation
$ROOT:[HORCM.usr.bin]inqraid.exe - sys
Synchronous waiting $ROOT:
[HORCM.usr.bin]pairsyncwait.exe
pairsyncwait sys
Conguration le
making
$ROOT:[HORCM.usr.bin]mkconf.exe - sys
Text ltering $ROOT:[HORCM.usr.bin]rmawk.exe - sys
Database Validator
setting
$ROOT:
[HORCM.usr.bin]raidvchkset.exe
raidvchkset sys
DB Validator
conrmation
$ROOT:
[HORCM.usr.bin]raidvchkdsp.exe
raidvchkdsp sys
DB Validator
conrmation
$ROOT:
[HORCM.usr.bin]raidvchkscan.exe
raidvchkscan sys
Storage Replication
Adapter
$ROOT:[HORCM.usr.bin]rmsra.exe rmsra sys
Sample le for
horcmstart
$ROOT:[HORCM]loginhorcm*.com - sys
Sample le for
horcmstart
$ROOT:[HORCM]runhorcm*.com - sys
Note:
■$ROOT is dened as SYS$POSIX_ROOT. $POSIX_ROOT is necessary when
using C RTL.
■The user name for OpenVMS is "System".
CCI les for OpenVMS-based systems
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 78
CCI log and trace files
The CCI software (HORCM) maintains internal startup log les, execution log les, and
trace les that can be used to identify the causes of errors and to keep records of the
status transition history of the paired volumes.
■CCI log les (on page 79)
■CCI trace les (on page 82)
■CCI trace control command (on page 82)
■Command logging for audit (on page 82)
CCI log files
HORCM logs are classied into startup logs and execution logs.
■The startup logs contain data on errors that occur before HORCM becomes ready to
provide services. Thus, if HORCM fails to start up due to improper environment
setting, refer to the startup logs to resolve the problem.
■The HORCM execution logs (error log, trace, and core les) contain data on errors that
are caused by software or hardware problems. These logs contain internal error data
that does not apply to any user settings, therefore, you do not need to refer to the
HORCM execution logs.
■When an error occurs in execution of a command, data on the error is collected in the
command log le. Refer to the command log le if a command execution error
occurs.
The following gure shows a graphical representation of the CCI log and trace les within
the CCI conguration environment.
CCI log and trace les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 79
The startup log, error log, trace, and core les are stored as shown in the following table.
Specify the directories for the HORCM and command log les using the HORCM_LOG
and HORCC_LOG environment variables. If it is not possible to create the log les, or if an
error occurs before the log les are created, the error logs are output in the system log
le. If the HORCM activation fails, the system administrator should check the system log
le and activation log, identify the error cause, and take the proper action. The system
log le for UNIX-based systems is the syslog le. The system log le for Windows-based
systems is the event log le.
File UNIX-based systems Windows-based systems
Start
up
log
HORCM startup log:
$HORCM_LOG/horcm_HOST.log
Command log: $HORCC_LOG/
horcc_HOST.log
$HORCC_LOG/horcc_HOST.oldlog
HORCM startup log:
$HORCM_LOG\horcm_HOST_log.txt
Command log: $HORCC_LOG
\horcc_HOST_log.txt
$HORCC_LOG\horcc_HOST_oldlog.txt
Error
log
HORCM error log:
$HORCM_LOG/horcmlog_HOST/
horcm.log
HORCM error log:
$HORCM_LOG\horcmlog_HOST
\horcm_log.txt
Trace HORCM trace:
$HORCM_LOG/horcmlog_HOST/
horcm_PID.trc
HORCM trace:
$HORCM_LOG\horcmlog_HOST
\horcm_PID_trc.txt
CCI log les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 80
File UNIX-based systems Windows-based systems
Command trace:
$HORCM_LOG/horcmlog_HOST/
horcc_PID.trc
Command trace:
$HORCM_LOG\horcmlog_HOST
\horcc_PID_trc.txt
Core HORCM core:
$HORCM_LOG/core_HOST_PID/
core
Command core:
$HORCM_LOG/core_HOST_PID/
core
HORCM core: $HORCM_LOG
\core_HOST_PID\core
Command core:
$HORCM_LOG\core_HOST_PID\core
Note: HOST denotes the host name of the corresponding machine. PID
denotes the process ID of that machine.
The location of the directory containing the log le depends on your command execution
environment and the HORCM execution environment. The command trace le and core
le reside together under the directory specied in the HORCM execution environment.
A directory specied using the environment variable HORCM_LOG is used as the log
directory in the HORCM execution environment. If no directory is specied, the
directory /tmp is used. A directory specied using the environment variable HORCC_LOG
is used as the log directory in the command execution environment. If no directory is
specied, the directory /HORCM/log* is used (* = instance number). A nonexistent
directory can be specied as a log directory using the environment variable.
The following table shows the environment variables for log directories.
Directory
name Definition
$HORCM_LO
G
A directory specied using the environment variable HORCM_LOG. The
HORCM log le, trace le, and core le as well as the command trace
le and core le are stored in this directory. If no environment variable
is specied, "/HORCM/log/curlog" is used.
$HORCC_LOG A directory specied using the environment variable HORCC_LOG. The
command log le is stored in this directory. If no environment variable
is specied, the directory "/HORCM/log*" is used (* is the instance
number). While the HORCM is running, the log les are stored in the
$HORCM_LOG directory shown in (a). When the HORCM starts up, the
log les created in the operation are stored automatically in the
$HORCM_LOGS directory shown in (b).
a. HORCM log le directory in operation
$HORCM_LOG = /HORCM/log*/curlog (* is instance number)
CCI log les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 81
Directory
name Definition
b. HORCM log le directory for automatic storing
$HORCM_LOGS = /HORCM/log*/tmplog (* is instance number)
CCI trace files
The command trace le is used for maintenance aiming at troubleshooting. It is not
created normally. If a cause of an error cannot be identied using the log le, the
environment variables or trace control commands with trace control parameters are
issued to start tracing and the trace le is created. The trace control parameters include
trace level, le size, mode, etc. More detailed tracing is enabled by increasing the trace
level. Tracing is made in wraparound within the range of the le size. HORCM makes the
trace le according to the trace level specied in the HORCM startup shell script set to
activate the HORCM.
CCI trace control command
The trace control command (one of the HORCM control commands) sets or changes the
trace control parameters. This command is used for troubleshooting and maintenance. If
no trace control parameters can be specied using the environment variables in your
command execution environment, it is possible to change the trace control parameters
into the global parameters using this command. The following table lists and describes
the parameters of the trace control command.
Parameter Function
Trace level parameter Species the trace level, range = 0 to 15.
Trace size parameter Species the trace le size in KB.
Trace mode parameter Species the buer mode or non-buer mode for writing
data in the trace le.
Trace type parameter Species the trace type dened internally.
Trace change
instruction
Species the command or CCI instance for which the trace
control parameters are changed.
Command logging for audit
■Logging other than raidcom command (on page 83)
■Logging raidcom command (on page 85)
CCI trace les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 82
Logging other than raidcom command
This section explains the logging other than the raidcom command described in Logging
raidcom command..
CCI supports command logging, this logging function cannot be used for auditing the
script issuing the command. Thus, CCI supports the function logging the result of the
command executions by expanding the current logging.
This function has the following control parameters.
$HORCC_LOGSZ variable
This variable is used to specify a maximum size (in units of KB) and normal logging
for the current command. /HORCM/log*/horcc_HOST.log le is moved to the /
HORCM/log*/horcc_HOST.oldlog le when reaching in the specied maximum
size. If this variable is not specied or specied as 0, it is same as the current
logging for only command error.
This variable is able to dene to the environment variable and/or horcc_HOST.conf
as discussed below.
For example setting 2MB size: HORCC_LOGSZ=2048 Export HORCC_LOGSZ
/HORCM/log*/horcc_HOST.conf le
This le is used to describe HORCC_LOGSZ variable and the masking variable for
logging. If the HORCC_LOGSZ as the environment variable is not specied, then
HORCC_LOGSZ variable of this le is used. If both variable is not specied, then it
is same as the current logging for only command error.
HORCC_LOGSZ variable
This variable must be described as follows: HORCC_LOGSZ=2048
Masking variable
This variable is used to mask (disable) the logging by specifying a condition of the
command and returned value (except inqraid or EX_xxx error code). This variable is
valid for NORMAL exit.
If executing the pairvolchk command repeatedly at every interval (30 seconds),
logging of this command might not be wanted. Therefore, you can mask it by
specifying HORCC_LOGSZ=0 as shown below, and you might need to change your
scripts if tracing is ON.
Example of masking pairvolchk on a script:
Export HORCC_LOGSZ=0 Pairvolchk -g xxx -s Unset HORCC_LOGSZ
The masking feature is to enable the tracing without changing their scripts. And
this feature is available for all CCI commands (except inqraid or EX_xxx error
code).
For example, if you want to mask pairvolchk (returns 22) and raidqry, specify the
following:
pairvolchk=22 raidqry=0
Logging other than raidcom command
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 83
You can track script performance, and then decide to mask by auditing the
command logging le, as needed.
Relationship between an environment variable and horcc_HOST.conf
Logging depends on the $HORCC_LOGSZ environment variable and/or the
HORCC_HOST.conf le as shown below.
$HORCC_LOGSZ HORCC_HOST.conf Performing
=value Any (does not matter) Tracing within this APP
=0 NO tracing within this APP
Unspecied HORCC_LOGSZ=value Global tracing within this CCI instance
HORCC_LOGSZ=0 NO global tracing within this CCI instance
Unspecied or
nonexistent
Use the default value (0) The same as the
current logging for only command error
Examples for execution: /HORCM/log* directory
[root@raidmanager log9]# ls l
total 16
drwxr-xr-x 3 root root 4096 Oct 27 17:33 curlog
-rw-r--r-- 1 root root 3936 Oct 27 17:36 horcc_raidmanager.log
-rw-r--r-- 1 root root 2097452 Oct 27 17:29 horcc_raidmanager.oldlog
-rw-r--r-- 1 root root 46 Oct 27 17:19 horcc_raidmanager.conf
drwxr-xr-x 3 root root 4096 Oct 27 17:19 tmplog
Examples for execution: /HORCM/log*/horcc_HOST.log le
COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005
CMDLINE : pairvolchk ss g URA
12:21:54-2d27f-10090- [pairvolchk][exit(32)]
COMMAND NORMAL : EUserId for HORC : root (0) Thu Oct 27 17:36:32 2005
CMDLINE : raidqry l
17:36:32-3d83c-17539- [raidqry][exit(0)]
COMMAND ERROR : EUserId for HORC : root (0) Thu Oct 27 17:31:28 2005
CMDLINE : pairdisplay g UR
17:31:28-9a206-17514- ERROR:cm_sndrcv[rc < 0 from HORCM]
17:31:28-9b0a3-17514- [pairdisplay][exit(239)]
[EX_ENOGRP] No such group
[Cause ]:The group name which was designated or the device name
doesn't exist in the configuration file, or the network address
for remote communication doesn't exist.
[Action]:Please confirm if the group name exists in the
configuration file of the local and remote host
Logging other than raidcom command
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 84
Examples for execution: /HORCM/log*/horcc_HOST.conf le
# For Example
HORCC_LOGSZ=2048
#The masking variable
#This variable is used to disable the logging by the command and exit code.
#For masking below log pairvolchk returned '32'(status is SVOL_COPY)
#COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005
#CMDLINE : pairvolchk ss g URA
#12:21:54-2d27f-10090- [pairvolchk][exit(32)]
pairvolchk=32
pairvolchk=22
Logging raidcom command
The history of performing raidcom command can be stored in syslog server by
outputting it to the syslog le. Since the information of what command was performed
by who and when are recorded on the syslog le, this is available to use for audit log.
Output the syslog le by using syslog service on the host OS. For details, refer to the host
OS manual.
Caution:
■The packet loss occurs on the syslog because the syslog uses UDP
communication. The log is also lost when the server to be received the
syslog is down because the server does not have a function to store the
data until it recovered. If you want to record the same log at the client side
by considering the lost of syslog at the syslog server, refer to the output
setting of the syslog le.
■This syslog les are not deleted automatically. Delete unnecessary les
accordingly, or make run the log rotation by installing such as the logrotate
service separately.
The conditions to support the output of syslog le
The conditions to support this function are explained in the following:
Supported OS
This function is supported only when the OS of the host is one of the following (Windows
is out of support):
■Solaris 2.5
■Solaris 10/x86
■HP-UX 10.20/11.0/11.2x
■AIX 4.3
■Red Hat Linux 6.0, 7.0, 8.0 AS/ES 2.1, 3.0, 4.0, 5.0
■AS/ES 2.1, 3.0 Update2, 4.0, 5.0 on EM64T / IA641
Target command
Logging raidcom command
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 85
The following shows the raidcom command that is target to be output on the syslog le.
■Setting commands
■raidcom get command status
■Authentication commands (performing the authentication command at the prompt
also becomes the target.)
However, if the command is not issued to the DKC by detecting the raidcom command
execution error beforehand, the command becomes out of target even if it falls under
the above items.
Output setting for the syslog le
A syslog le is output when "1" is set on the RAIDCOM_SYSLOG of environment variables.
The syslog le is not output at the stage of initial setting.
How to set the syslog.conf:
The contents that can be set on the syslog.conf for the environment setting might vary in
each OS. However, set basically according to the syslog.conf described in the following:
Setting example (It might vary by the host OS)
■Client side (extracts)
user.info /var/log/raidcomuser.err
/var/log/raidcom.erruser.info
@host1234user.err
@host1234
■Server side (extracts)
user.info /var/log/raidcomuser.err
/var/log/raidcom.err
You can record the same log at the client side by considering the lost of syslog at the
syslog server. In this case, add the following settings.
■facility:user
■level:info/err ("info" for the normal command operation; "err" for the abnormal
command operation.)
Syslog le display information
Three kinds of information for one raidcom command are output on the syslog le.
■Title row (rst row)
■Command row (second row)
■Result rows (3 - 132 rows): the number of rows changes depending on the issuing
command.
Logging raidcom command
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 86
Display information of the title row
Item Output example
Syslog xed output
part (Including the
host name)
Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info]
*It varies depending on the host OS.
Process ID PID:1234
Command status COMMAND NORMAL or COMMAND ERROR
Separation :
User name Title EUserId for HORC :
User name of the
host
root
(user ID) (0)
Time that performed
raidcom
Wed Jun 27 10:15:13 2012
Display information of the command row
Item Output example
Syslog xed output
part (Including the
host name)
Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info]
*It varies depending on the host OS.
Process ID PID:1234
Title for performed
command
CMDLINE:
Performed command raidcom modify ldev -ldev_id 1234 -status nml
Display information of the result rows
Item Output example
Syslog xed output
part (Including the
host name)
Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info]
*It varies depending on the host OS.
Process ID PID:1234
[raidcom] [raidcom]
Logging raidcom command
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 87
Item Output example
Rows for the error
information
[EX_CMDRJE] An order to the control/command device was
rejected It was rejected due to SKEY=0x05, ASC=0x26,
ASCQ=0x00, SSB=0x2E11,0x2205 on Serial#(64568)
Result of
get_command_status
HANDLE SSB1 SSB2 ERR_CNT Serial# Description 00c4 - - 0
200414 -
Rows for the returned
values of a command
[exit(0)]
See the following display examples (It might vary depending on the host OS):
Logs: during normal operation
Aug 24 12:24:37 raidmanager raidcom: PID:06864 COMMAND NORMAL : EUserID
for HORC : root(0) Fri Aug 24 12:24:36 2012
Aug 24 12:24:37 raidmanager raidcom: PID:06864 CMDLINE : raidcom get
command_status -ldev_id 0001
Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] HANDLE SSB1
SSB2 ERR_CNT Serial# Description
Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] 00c3 -
- 0 64568 -
Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] [exit(0)]
Logs: during abnormal operation
Aug 24 12:24:27 raidmanager raidcom: PID:06857 COMMAND ERROR : EUserID for
HORC : root(0) Fri Aug 24 12:24:19 2012
Aug 24 12:24:27 raidmanager raidcom: PID:06857 CMDLINE : raidcom get
command_status
Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] User for
Serial#[64568] : user1234
Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] User
authentication has failed on Serial#(64568).
Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [EX_ENAUTH]
Authentication failed with User
Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [exit(202)]
User-created files
CCI supports scripting to provide automated and unattended copy operations. A CCI
script contains a list of CCI commands that describes a series of TrueCopy and/or
ShadowImage operations. The scripted commands for UNIX-based platforms are dened
in a shell script le. The scripted commands for Windows-based platforms are dened in
a text le. The host reads the script le and sends the commands to the command
device to execute the TrueCopy/ShadowImage operations automatically.
User-created les
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 88
The CCI scripts are:
■HORCM startup script (horcmstart.sh, horcmstart.exe): A script that starts
HORCM (/etc/horcmgr), sets environment variables as needed (for example,
HORCM_CONF, HORCM_LOG, HORCM_LOGS), and starts HORCM.
■HORCM shutdown script. (horcmshutdown.sh, horcmshutdown.exe): A script for
stopping the HORCM (/etc/horcmgr).
■HA control script: A script for executing takeover processing automatically when the
cluster manager (CM) detects a server error.
When constructing the HORCM environment, the system administrator should make a
copy of the horcm.conf le. The copied le should be set according to the system
environment and registered as the following le (* is the instance number):
UNIX systems: /etc/horcm.conf or /etc/horcm*.conf
Windows systems:%windir%\horcm.conf or %windir%\horcm*.conf
User environment variable
When HORCM or command is invoked, environment variable can be specied.
User environment variable
Chapter 2: CCI software environment
Command Control Interface User and Reference Guide 89
Chapter 3: CCI functions
This chapter describes the CCI functions.
System configuration using CCI
This section describes system congurations using the in-band method or out-of-band
method. In addition, a system conguration for connecting to an in-band CCI server by
using the out-of-band method is also described. For an overview of the in-band and out-
of-band methods, see Command execution by the in-band and out-of-band methods.
In-band system configurations and out-of-band system configurations
Values to specify for HORCM_CMD in the conguration denition le are dierent
between in-band and out-of-band method system congurations.
■In-band method. This method species the device special le of command device in
the conguration denition le. For details about contents to specify for
HORCM_CMD, see HORCM_CMD (in-band method) topic.
■Out-of-band method. This method species the SVP for creating virtual command
devices or IP addresses of GUM in the command denition le. For details about
contents to specify for HORCM_CMD, see HORCM_CMD (out-of-band method) topic.
The location of the virtual command device depends on the type of storage system. The
following table lists the storage system types and indicates the allowable locations of the
virtual command device.
Storage system type
Location of virtual command device
SVP GUM CCI server1
VSP Gx00 models, VSP Fx00
models
OK2OK OK
VSP G1x00 and VSP F1500 OK Not allowed OK
HUS VM OK Not allowed OK
VSP OK Not allowed OK
1. A CCI server is a remote CCI server connected via LAN.
2. CCI on the SVP must be congured as a CCI server in advance.
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 90
The following gures show a system conguration example and a setting example of a
command device and a virtual command device using the in-band and out-of-band
methods.
Note: For the out-of-band method using the maintenance utility (GUM) of
VSP Gx00 models and VSP Fx00 models, the command might time out if a
controller with GUM is maintained. Before the maintenance, change
command devices so that you use a virtual command device of the other
GUM. For details about how to switch command devices, see Alternate
command device function.
The following gure shows system conguration example of in-band and out-of-band
methods (VSP).
In the following gure, CCI B is the CCI server of CCI A. Users can issue a command from
CCI A to a storage system via a virtual command device of CCI B. Commands can also be
issued directly from CCI B without using CCI A.
The following gure shows a system conguration example of in-band and out-of-band
methods (VSP G800, VSP F800).
In-band system congurations and out-of-band system congurations
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 91
Note: In the out-of-band method using SVP of VSP G1x00 and VSP F1500,
VSP, or HUS VM, a command times out if the microcode of the SVP is
changed. Execute the command again after the microcode change completes.
System configuration for connecting to a CCI server connected by the
in-band method using the out-of-band method
In the out-of-band method, CCI server ports can be specied as virtual command
devices. Specifying a CCI server port as a virtual command device allows you to use the
out-of-band method to connect to a CCI server connected to a storage system using the
in-band method. For details about settings for HORCM_CMD in the conguration
denition le of this conguration, see HORCM_CMD (out-of-band method) topic.
System conguration for connecting to a CCI server connected by the in-band method using the out-of-
band method
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 92
Tip: If you specify a CCI server port as a virtual command device, it achieves
better performance than the out-of-band method which species SVP or
GUM as a virtual command device.
The following gure shows a system conguration example when a CCI server is
connected to a storage system using the in-band method.
Connecting to CCI server already connected by In-Band
method using Out-of-Band method
In Out-of-Band method, CCI server port can also be specied as a virtual command
device. For this reason, CCI server which connected to a storage system in In-Band
method can be connected in Out-of-Band method. If a CCI server is specied as a virtual
command device, it provides better performance than the Out-of-Band method with
specied SVP/GUM as a virtual command device.
Connecting to CCI server already connected by In-Band method using Out-of-Band method
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 93
Hardware requirements
CCI uses SCSI path through driver to issue I/O for command device. To use CCI server
port as virtual command device, the virtual command device interface needs to be
converted to the actual SCSI path through interface. Following is the environment for
using CCI server port as a virtual command device.
■CCI server which can set virtual command devices
CCI support platform except Tru64UNIX and the environment can be used SCSI path
through driver
■Client PC which can issue commands to virtual command devices
It must be CCI support platform.
■Initiator port
Initiator port is required on the following storage systems: Virtual Storage Platform,
Unied Storage VM, Virtual Storage Platform G1000, Virtual Storage Platform G1500,
and Virtual Storage Platform F1500.
Following is the default port number.
If not specied the instance number: 34000
If specied instance number (X): 34000 + X + 1
If you change the default port number, use following environment variables.
$HORCM_IPSCPORT=<services>*
* <services>: port number or service name
For details about supported platforms, see the Command Control Interface Installation and
Conguration Guide.
I/O Traffic Control
Synchronized I/O is issued from a virtual command device. The queueing time might
occur because of the heavy I/O trac because the virtual command device has to relay
the command to the next virtual command device in the cascade conguration using the
virtual command device. To improve the response in this environment, dene the
conguration so that asynchronous I/O is issued using the following environment
variables.
$HORCM_IPSCPAIO=1
Hardware requirements
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 94
Security setting
Following security can be set.
■Specifying security of IP address and port number
By dening IP address and port number of the client PC that issues command to
virtual command device to HORCM_ALLOW_INST in the conguration denition le,
users who can use virtual command device can be restricted. For the details about
the settings to HORCM_ALLOW_INST, please refer to "Conguration denition le".
■Security setting for virtual command device
By using the following environment variable, security can be set to virtual command
device.
$HORCM_IPCMDSEC=<value>
Security setting for virtual command device
Specify the number (from 0 to 7) to <value> depending on the contents of the security
which you want, in reference with the following table.
Value
specified
for <value>
Command device setting
Security
setting
User
authentication
Device group
definition
Security to be set
(see Notes)
0 OFF OFF OFF No security
1 OFF OFF ON Only HORCM_DEV
allowed
2 OFF ON OFF User authentication
required
3 OFF ON ON User authentication
required
Only HORCM_DEV
allowed
4 ON OFF OFF CMD security
5 ON OFF ON CMD security
Only HORCM_DEV
allowed
6 ON ON OFF CMD security
User authentication
required
7 ON ON ON CMD security
Security setting
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 95
Value
specified
for <value>
Command device setting
Security
setting
User
authentication
Device group
definition
Security to be set
(see Notes)
User authentication
required
Only HORCM_DEV
allowed
Notes:
■ON: Enabled
■OFF: Disabled
■Only HORCM_DEV allowed: the operation can be performed only for paired logical
volumes described in HORCM_DEV.
■User authentication required: only commands issued by authorized users can be
executed.
■CMD security: only devices recognizable from the host can be operated. For details
about CMD security, see Data Protection facility (on page 327) .
User authentication
CCI allows user authentication by using the operation authority of a user set by:
■Storage Navigator
■Device Manager - Storage Navigator
■Maintenance utility
User authentication is arbitrary in the Replication operation in the in-band method while
the operation by user authentication is mandatory in the conguration information
operation and in the out-of-band method.
To enable the user authentication function, the user authentication mode of the
command device accessed by CCI must be enabled.
The user authentication function inputs a login command from the client (server) and, to
authenticate the user ID and password sent from CCI and the same types of information
maintained by the storage system, issues an authentication request to the
authentication module (SVP/GUM).
If the user ID and password which are sent by CCI are authenticated, the storage system
generates the session information. The storage system stores the session information,
the user ID, and the client ID, and then sends back the session information to CCI. CCI
stores the session information with the storage system ID. After that, the session
information is added to all commands which are issued by CCI to the storage system. If
the session information which is added to the command is valid, the storage system
permits the command execution.
User authentication
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 96
When the user logs out, the session information which is stored by CCI, and the user ID,
the client ID, and the session information which are stored in the storage system are
deleted.
A storage system can store only one session information for the same user ID and the
same client ID at the same time. If the storage system received the login command with
the user ID and client ID, corresponding to the session information which has already
been stored, the storage system sends back the stored session information to CCI
without authentication. During executing the login command, if another login command
is input with the same user ID from the same client, the authentication result of the
subsequent login command will be the same as the authentication result of login
command being executed.
Note:
■The only function that can be used if the user authentication function is
disabled is the Replication function (replication command). If the user
authentication function is disabled, the Provisioning function
(conguration setting command) cannot be used. If you use the global
storage virtualization function, see the table in Controlling user resources.
For details about global storage virtualization, see the Provisioning Guide
for Open Systems or Provisioning Guide.
■If the specic user information or authority information is changed,
perform the user authentication processing on CCI again.
■CCI stores the session information for each user ID (managed by OS) which
is used for login to the client OS. Therefore, if users having the dierent
user ID (managed by OS) use the same client, execute CCI login command
for each user ID (managed by OS).
Command operation authority and user authentication
When CCI is used with the user authentication function enabled, commands are
executed complying with the operation authority of a user set by:
■Storage Navigator
■Device Manager - Storage Navigator
■Maintenance utility (GUM)
Controlling User Role
CCI veries whether or not the user executing the command on the host was already
authenticated by checking the command device being in the authentication mode. After
that, CCI obtains the execution authority of the command that is congured on the user
role, and then compares the relevant command and the execution authority.
Command operation authority and user authentication
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 97
Checking the execution authority
If the conguring commands authenticated are compared with the execution authorities
of commands congured on the user role and they do not correspond, CCI rejects the
command with an error code "EX_EPPERM".
Normally, the user role needs to be the consistent and integrated authority among the
large storage systems. In case of HORCM instances that are congured by the multiple
large storage systems, the execution authorities are obtained by the serial number of the
storage systems. If the user role is for the multiple storage systems and is not consistent
among these storage systems, CCI makes the integrated authority by performing the
logical AND of the execution authorities among the storage systems.
Target commands
CCI checks execution authorities on the following commands that use command devices.
■horctakeover, horctakeoff
■paircreate, pairsplit, pairresync
■raidvchkset
Controlling user resources
CCI veries the user who executes the command has been authenticated already. After
that, CCI obtains the access authority of the resource groups that are congured on the
user roles, and then compares the access authority of the user and the specied
resources.
Checking resource authorities
If the access is not permitted by comparing the access authorities of the resource groups
congured on the user roles and the specied resource, CCI rejects the command with
an error code "EX_EGPERM". If the resource groups are dened among the large storage
systems, the specied resource is compared with the resource specied by obtaining the
access authority congured to each large storage system.
Target commands
CCI checks resource authorities on the following commands that use command devices.
■raidcom commands (commands for setting congurations)
■horctakeover, horctakeoff, paircurchk, paircreate, pairsplit, pairresync,
pairvolchk, pairevtwait, pairsyncwait, pairmon
■raidscan (-nd verify, -nd inst, -nd sync except for [d]), pairdisplay, raidar,
raidqry (except for -l and -r)
■raidvchkset, raidvchkscan, raidvchkdsp
Controlling user resources
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 98
Relation between user authentication and resource groups
In user authentication mode, CCI veries the access authority of the target resource
based on the user authentication and the role of it. Also, on the user authentication
unnecessary mode and the undened resource groups, CCI checks the access authorities
shown in the following table.
Resources
Commands
pairXX1raidcom
Not
authenticated
user2
Authenticated
user
Not
authenticated
user2
Authenticated
user
Undened
resource3
Permitted Permitted by
the authority of
resource ID 0
EX_EPPERM4Permitted by the
authority of
resource ID 0
Dened
resource
EX_EGPERM4Permitted by
the authority of
the target
resource ID
EX_EGPERM4
EX_EPPERM
Permitted by the
authority of the
target resource
ID
Virtual
storage
machine5
Permitted6Permitted by
the authority of
the target
resource ID
EX_EGPERM4
EX_EPPERM
Permitted by the
authority of the
target resource
ID
Notes:
1. Above-described commands except for the raidcom command.
2. User who uses the mode without the command authentication.
3. Undened as the resource group.
4. Command execution is rejected by the relevant error.
5. The resource group that is dened as the virtual storage machine by the global
storage virtualization function. For details about global storage virtualization, see
the Provisioning Guide for the storage system.
6. When you specify a volume that belongs to meta_resouce or a virtual command
device for HORCM_VCMD in the conguration denition le, the resource
operation for the entire resource group in the virtual storage machine which
species HORCM_VCMD is permitted. If you do not specify the virtual storage
system for HORCM_VCMD, EX_EGPERM is returned. When you specify a volume
that belongs to the virtual storage machine for HORCM_CMD in the conguration
denition le, the resource operation for the entire resource group in the virtual
storage machine to which the volume belongs is permitted. For details about
specifying the virtual storage machine to HORCM_VCMD, see Conguration
denition le settings with global storage virtualization.
Controlling user resources
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 99
Checking the access authority when you operate a pair
When you use the commands other than raidcom commands, which are described in
"Target commands" above, whether the user who executes the command has an access
authority to the resource is checked. Usually, only one resource in the volumes which
congures a pair is checked, the resource is managed by the instance which executes the
pair operation command. However, when you operate a pair of a local copy, if the
HOMRCF_CHECK_RSGID environment variable is dened, an access authority of the
command execution user to both volumes which congure a pair can be checked.
The following gure shows an example of a pair operation when you do not dene the
HOMRCF_CHECK_RSGID environment variable. The command execution user can create
a pair even if one of the volume which congures the pair is a resource to which the user
does not have an authority.
The following gure shows an example of a local copy pair operation when you dene
the HOMRCF_CHECK_RSGID environment variable. You can avoid creating a pair which
includes the volume without authority, therefore whether the both volumes which
congure a pair are authenticated or not is checked.
Controlling user resources
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 100
Target resources
The following objects are arbitrarily dened as the resource groups by each user.
■LDEV
■Physical port
■Host group
■RAID group
■External connection group
Commands executed depending on operation authorities
The following table lists the commands executed depending on operation authority of a
user set by:
■Storage Navigator
■Device Manager - Storage Navigator
■Maintenance utility
For information about creating the user accounts, registering user accounts to user
groups, and user group authorities, see the Hitachi Command Suite User Guide or the
System Administrator Guide or System Administrator Guide for the storage system.
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 101
The following table shows the executable commands executed depending on operation
authority of a user set by Storage Navigator, Device Manager - Storage Navigator, or
maintenance utility.
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
Initial
congurati
on
Program
product
License
management
authority
■raidcom add
license (VSP
G200, G400,
G600, G800 and
VSP F400, F600,
F800 only)
■raidcom delete
license (VSP
G200, G400,
G600, G800 and
VSP F400, F600,
F800 only)
■raidcom modify
license (VSP
G200, G400,
G600, G800 and
VSP F400, F600,
F800 only)
Storage
Administrator
(Initial
conguration)
Overall
setting
MP blade MP blade
setting
authority
raidcom modify
ldev
raidcom modify
journal
raidcom modify
external_grp
Storage
Administrator
(System Resource
Management)
CLPR Parity group
migration
authority
raidcom modify clpr
Resource
group
Resource
group
creation
authority
raidcom add
resource
raidcom modify
resource
raidcom map
resource
Storage
Administrator (View
& Modify)
Resource
group
deletion
authority
raidcom unmap
resource
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 102
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
raidcom delete
resource
Resource
creation,
deletion
LDEV LDEV creation
authority
raidcom add
ldev
raidcom add ldev Storage
Administrator
(Provisioning)
LDEV deletion
authority
raidcom delete ldev Storage
Administrator
(Provisioning)
LDEV format
authority
raidcom initialize
ldev -operation fmt
raidcom initialize
ldev -operation
qfmt
Storage
Administrator
(Provisioning)
LDEV
shredding
execution
authority
raidcom initialize
ldev -operation shrd
raidcom initialize
ldev -operation stop
Storage
Administrator
(Provisioning)
HAM/GAD
Pair creation
authority
raidcom modify
ldev -
quorum_enable
paircreate -f never -
jq
paircreate -f never -
jp
Storage
Administrator
(Provisioning)
HAM/GAD
Pair deletion
authority
raidcom modify
ldev -
quorum_disable
pairsplit -S[F[V]]
pairsplit -R[F[V]]
Storage
Administrator
(Provisioning)
Parity group LDEV
shredding
execution
authority
raidcom initialize
parity_grp
Storage
Administrator
(Provisioning)
Parity group
creation
authority
raidcom modify
parity_grp
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 103
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
Parity group
creation
authority
raidcom add
parity_grp (VSP
Gx00 models, VSP
Fx00 models)
Storage
Administrator
(Provisioning)
Parity group
creation
authority,
encryption
setting
cancellation
authority
raidcom add
parity_grp –
encryption (VSP
Gx00 models, VSP
Fx00 models)
Storage
Administrator
(Provisioning),
Security
Administrator (View
& Modify)
Parity group
creation
cancellation
authority
raidcom delete
parity_grp (VSP
Gx00 models, VSP
Fx00 models)
Storage
Administrator
(Provisioning)
Parity group
creation
authority or
parity group
creation
cancellation
authority
raidcom modify
drive -spare enable
(VSP Gx00 models,
VSP Fx00 models)
Storage
Administrator
(Provisioning)
raidcom modify
drive -spare disable
(VSP Gx00 models,
VSP Fx00 models)
Storage
Administrator
(Provisioning)
External
volume
(Universal
Volume
Manager)
External
volume
creation
authority
raidcom add
external_grp
Storage
Administrator
(Provisioning)
External path
operation
authority
raidcom
check_ext_storage
path
raidcom disconnect
path
Storage
Administrator
(Provisioning)
External
volume
disconnection
authority
raidcom
check_ext_storage
external_grp
raidcom disconnect
external_grp
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 104
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
External
volume
connection
check and
resumption
authority
External
volume
mapping
release
authority
raidcom delete
external_grp
Storage
Administrator
(Provisioning)
UVM Attribute
value setting
authority
raidcom modify
external_grp
raidcom add
external_iscsi_name
raidcom delete
external_iscsi_name
raidcom modify
external_chap_user
raidcom modify
initiator_chap_user
Storage
Administrator
(Provisioning)
UVM path
operation
authority
raidcom delete path Storage
Administrator
(Provisioning)
Pool Pool creation
and capacity
change
authority
raidcom add
dp_pool
raidcom add
snap_pool
raidcom initialize
pool
Storage
Administrator
(Provisioning)
Pool deletion
authority
raidcom delete pool Storage
Administrator
(Provisioning)
Dynamic
Provisioning
virtual
volume
Dynamic
Provisioning
virtual volume
creation
authority
raidcom add ldev -
pool
raidcom extend
ldev
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 105
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
Dynamic
Provisioning
virtual volume
deletion
authority
raidcom delete ldev Storage
Administrator
(Provisioning)
Copy-on-
Write
Snapshot
virtual
volume
Copy-on-Write
Snapshot
virtual volume
creation
authority
raidcom add ldev -
pool
Storage
Administrator
(Provisioning)
Copy-on-Write
Snapshot
virtual volume
deletion
authority
raidcom delete ldev Storage
Administrator
(Provisioning)
Port LUN security
setting
authority
raidcom modify
port -
security_switch
Storage
Administrator
(System Resource
Management)
Storage
Administrator
(Provisioning)
Host group Host group
creation
authority
raidcom add
host_grp
Storage
Administrator
(Provisioning)
Host group
deletion
authority
raidcom delete
host_grp
Storage
Administrator
(Provisioning)
LUN LU path
creation
authority
raidcom add lun Storage
Administrator
(Provisioning)
LU path
deletion
authority
raidcom delete lun Storage
Administrator
(Provisioning)
WWN / iSCSI
name /
CHAP user
name
WWN
addition
authority
raidcom add
hba_wwn
raidcom add
hba_iscsi
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 106
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
raidcom add
chap_user
WWN deletion
authority
raidcom delete
hba_wwn
raidcom delete
hba_iscsi
raidcom delete
chap_user
Storage
Administrator
(Provisioning)
LDEV group Device group
and Copy
group
creation
authority
raidcom add
device_grp
raidcom add
copy_grp
Storage
Administrator
(Provisioning)
Device group
and Copy
group
deletion
authority
raidcom delete
device_grp
raidcom delete
copy_grp
Storage
Administrator
(Provisioning)
Local copy Pair creation
authority
paircreate
raidcom add
snapshot
Storage
Administrator
(Provisioning)
Pair deletion
authority
pairsplit -S
raidcom delete
snapshot
Storage
Administrator
(Provisioning)
Volume
Migration pair
creation
authority
paircreate Storage
Administrator
(Provisioning)
Volume
Migration pair
deletion
authority
pairsplit -S Storage
Administrator
(Provisioning)
Local copy
environmenta
l setting
authority
raidcom modify
local_replica_opt
Storage
Administrator (Local
Copy)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 107
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
Remote
copy
Pair creation
authority
paircreate Storage
Administrator
(Remote Copy)
Pair deletion
authority
pairsplit -S Storage
Administrator
(Remote Copy)
Attribute
change
External
volume
External path
setting
authority
raidcom add path Storage
Administrator
(Provisioning)
Pool Pool setting
authority
raidcom modify
pool
raidcom rename
pool
Storage
Administrator
(Provisioning)
Pool
monitoring
and
reallocation
start and stop
authority
raidcom reallocate
pool
raidcom monitor
pool
Storage
Administrator
(Provisioning)
Port Port attribute
setting
authority
raidcom modify
port -port_attribute
Storage
Administrator
(System Resource
Management)
Port setting
authority
raidcom modify
port -loop_id
raidcom modify
port -topology
raidcom modify
port -port_speed
raidcom modify
port -t10pi
raidcom modify
port -port <port#>
[-mtu <value>]...
raidcom modify
port -port <port#>
[-isns_mode
{enable|disable}]...
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 108
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
Host group Host group
setting
authority
raidcom modify
host_grp
Storage
Administrator
(Provisioning)
LUN LDEV setting
authority
raidcom modify lun Storage
Administrator
(Provisioning)
WWN / iSCSI
name /
CHAP user
name
WWN setting
authority
raidcom set
hba_wwn
raidcom reset
hba_wwn
raidcom set
hba_iscsi
raidcom reset
hba_iscsi
raidcom set
chap_user
raidcom reset
chap_user
Storage
Administrator
(Provisioning)
LDEV
nickname
LDEV
nickname
setting
authority
raidcom modify
ldev -ldev_name
Storage
Administrator
(Provisioning)
SPM
information
SPM setting
authority
raidcom add
spm_wwn
raidcom add
spm_group
raidcom delete
spm_wwn
raidcom delete
spm_group
raidcom modify
spm_wwn
raidcom modify
spm_group
raidcom modify
spm_ldev
Storage
Administrator
(System Resource
Management)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 109
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
raidcom delete
spm_ldev
Local copy Pairsplit and
resync
authority
pairresync
raidcom modify
snapshot
raidcom map
snapshot
raidcom unmap
snapshot
raidcom replace
snapshot
Storage
Administrator (Local
Copy)
Remote
copy
Environment
construction
authority
raidcom add rcu
raidcom delete rcu
raidcom modify rcu
raidcom add
rcu_iscsi_port
raidcom delete
rcu_iscsi_port
raidcom add
rcu_path
raidcom delete
rcu_path
raidcom add
journal
raidcom delete
journal
raidcom modify
journal
raidcom add ssid
raidcom delete ssid
Storage
Administrator
(Remote Copy)
Pairsplit and
resync
authority
pairresync Storage
Administrator
(Remote Copy)
Quorum
disk
LDEV setting
authority
raidcom modify
quorum
Storage
Administrator
(Provisioning)
Commands executed depending on operation authorities
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 110
Operation
Operation
target Authority
Executable
command
Operation authority
(Role)
HAM/GAD
pair creation
authority
HAM/GAD
pair deletion
authority
raidcom replace
quorum
Storage
Administrator
(Provisioning)
Relation between resource groups and command operations
The operation for using resource groups are dierent by the command devices (the In-
Band method) or the Out-of-Band method that are used when you start CCI.
You can create resource groups for each resource. And you can share them with multiple
users. When user 10 and user 20 share the port like the following gure, the relation
between the command devices and resource groups that user can use is given in the
table below.
See the following gure given below for relation among user, command devices, and
resource groups. The table given below shows the relation between resource groups and
command devices.
Relation between resource groups and command operations
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 111
Login
user
Comma
nd
device Operating range Reference
Configuration
change
Comman
d
operatio
ns using
the out-
of-band
method
System
administ
rator
CM0 Can operate all
resource groups after
logging in.
Operable Operable Operable
CM10 Can operate only in the
range of resource
group 10, and the
shared ports after
logging in.
Operable Operable Inoperabl
e
CM11 Can operate only in the
range of resource
group 11, and the
shared ports after
logging in.
Operable Operable Inoperabl
e
Relation between resource groups and command operations
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 112
Login
user
Comma
nd
device Operating range Reference
Configuration
change
Comman
d
operatio
ns using
the out-
of-band
method
CM20 Can operate only in the
range of resource
group 20, and the
shared ports after
logging in.
Operable Operable Inoperabl
e
User 10 CM0 Can operate only in the
range of resource
group 10 and 11, and
the shared ports after
logging in.
Operable Operable Operable
CM10 Can operate only in the
range of resource
group 10, and the
shared ports after
logging in.*
Operable Operable Inoperabl
e
CM11 Can operate only in the
range of resource
group 11, and the
shared ports after
logging in.*
Operable Operable Inoperabl
e
CM20 Cannot log in. Nothing is displayed
or the operation authority error.
Operation
authority error
Inoperabl
e
User 20 CM0 Can operate only in the
range of resource
group 20, and the
shared ports after
logging in.
Operable Operable Operable
CM10 Cannot log in. Nothing is displayed
or the operation authority error.
Operation
authority error
Inoperabl
e
CM11 Cannot log in. Nothing is displayed
or the operation authority error.
Operation
authority error
Inoperabl
e
Relation between resource groups and command operations
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 113
Login
user
Comma
nd
device Operating range Reference
Configuration
change
Comman
d
operatio
ns using
the out-
of-band
method
CM20 Can operate only in the
range of resource
group 20, and the
shared ports after
logging in.
Operable Operable Inoperabl
e
* To use each resource group, the user must separately execute raidcom -login
command. For details about the raidcom -login command, see Command Control
Interface Command Reference.
As shown in the table above, the relation among users, command devices and
operations of resource groups are the following.
■The range that can be operated by command device 0 (CM0) or Out-of-Band is the
shared range (AND) of resource groups that are allocated to each user and all
resource groups.
■The range that can be operated by command device 10 (CM10) is the shared range
(AND) of resource groups that are allocated to each user and resource group 10 that
the command devices are allocated.
Therefore, in the range of resource group 10 can be operated.
The following shows the example of the case that the execution results of the commands
change by the case of having or not having the authority of the operated resources,
species only the objects or species to the parameters.
When user has the authority using CL1-A, CL3-A and CL5-A ports, and CL1-A, CL2-A, CL3-
A, CL4-A and CL5-A ports are implemented in the system, executes the following
command.
When only the objects are specied:
# raidcom get port
The execution results of CL1-A, CL3-A and CL5-A are displayed. The execution results of
CL2-A and CL4-A (the user does not have the authority of the resource) are not displayed
(ltered).
When parameters are also specied:
# raidcom get port -port CL1-A
Relation between resource groups and command operations
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 114
The execution result of CL1-A is only displayed.
# raidcom get port -port CL2-A
The error is displayed because the user does not have the execution authority.
The following shows the output example when -cnt that is used in get ldev is used.
The following command is executed when the user has the authorities of LDEV number
10 and 12.
# raidcom get ldev -ldev_id 10 -cnt 3
Execution results of LDEV number 10 and 12 are displayed. LDEV number 11 is not
displayed because the user does not have the authority of the resource.
Resource lock function
When conguration changes from multiple user interfaces (CCI, HCS, Device Manager -
Storage Navigator, or maintenance utility) are performed on the same resource at the
same time, congurations are changed unexpectedly, and expected results might not
occur. While a command is being executed, if another user changes the conguration,
unexpected results can occur even though it is a viewing command.
To prevent users from changing the conguration of the same resource at the same
time, the resource lock command is provided. When this command is used, the
resource group can be locked to prevent other users from using the specied resource
group. If the resource is not locked, all conguration change commands are performed.
However, conicting operations might cause an error.
The commands for performing the exclusive control and exclusive control release (lock
and unlock) of resource groups are as follows.
■raidcom lock resource -resource_name <resource group name > [-time <time(sec)>]
(Locking a specied resource group)
■raidcom unlock resource -resource_name <resource group name > (Unlocking a
specied resource group)
If multiple users (IDs) operate the same resource, you can prevent operation conict for
the target resource by using the raidcom lock resource command to conrm that
no other user is using the resource.
After the conguration change is completed, release the lock status by the raidcom
unlock resource command.
The user who locks a resource is identied by the session information. When the user
logs out and the session information of the user is deleted from the storage system, the
resource that has been locked by the user is automatically released. For details about the
session information, see User authentication.
Resource lock function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 115
Command execution modes
Overview
Provisioning operations are performed using a conguration setting command. For
details about the conguration setting command, see Overview of the conguration
setting command or Command Control Interface Command Reference.
Two modes can be used for executing the conguration setting command:
■Line-by-line mode.
This mode executes commands input from the command line one at a time.
■Transaction mode.
Executes a script le specied by the -zt option.
When executing the conguration setting command, the following checks can be done
depending on the above two mode types.
■Syntax check:
This function checks if there is no syntax error in the specied command. This is
executed every time at the both line-by-line mode and transaction mode.
■Context check:
This function checks the consistency of one specied line in the script and the
preceding lines in the order from the top. This function is available only at the
Transaction mode. For details about context checking, see Context check topic.
■Conguration check:
Acquire the current conguration information to a conguration le, and then this
function checks whether the resources specied in the script (LDEVs, ports, or host
groups) are congured in the storage system or not. This function is available only at
the transaction mode. For details about context checking, see conguration check
topic.
The conguration setting command also has a execution option described in the
following.
Precheck
Specify the checkmode precheck option. It operates checking only (it does not execute
processing even if no error is detected.) This can be specied at the both line-by-line
mode and transaction mode.
Execution modes and options of the conguration setting command (line-by-line
mode)
The following tables show the overview of execution modes and options of the
conguration setting command.
Command execution modes
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 116
Command syntax
Syntax
check
Context
check
Configura-
tion check
Command
execution
with no error
Remark
s
raidcom <action> Execute
d
Not
executed
Not
executed
Executed Default
raidcom <action> -
checkmode precheck
Execute
d
Not
executed
Not
executed
Not executed Check
only
Execution modes and options of the conguration setting command (transaction
mode)
Command syntax
Syntax
check
Context
check
Configura
-tion
check
Command
execution
with no
error Remarks
raidcom -zt <script
le>
Execute
d
Execute
d
Not
executed
Executed Default
raidcom -zt <script
le> -load <work le>
Execute
d
Execute
d
Executed Executed With
conguration
check
raidcom -zt <script
le> -checkmode
precheck
Execute
d
Execute
d
Not
executed
Not
executed
Check only
raidcom -zt <script
le> -load < work le>
-checkmode precheck
Execute
d
Execute
d
Executed Not
executed
With
conguration
check
Check only
Detailed description are provided in the following sections.
Caution: Observe the following cautions:
■For <script le>, specify an executable le name.
■For <script le>, either specify a full path name or store under the c:
\HORCM\etc folder.
■For <work le>, either specify a full path name or store in the current
directory.
Overview
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 117
Context check
This check can be performed to ensure consistent content of the created script le. For
example, it can check if the script refers to an ldev_id that is already deleted in the
preceding lines.
The script is executed only when no error is detected by the checking of whole script
contents.
The following resources can be the target of the check:
■LDEV
■Port
■Host group
Checking contents before executing scripts
Checking the contents before executing the script helps reduce debugging after running
the script.
Specify the script as follows to execute it.
raidcom -zt <created script file name>
raidcom -zt <created script file name> -load <configuration file>
raidcom -zt <created script file name> -checkmode precheck
raidcom -zt <created script file name> -load <configuration file> -
checkmode precheck
Details of check contents
Details of Context check is described below. Checking contents before issuing a script
can reduce load for the debug operation.
LDEV check
The check is performed from the following perspective. Note that checking for the object
information that is related to the LDEV such as pool or device group, or an attribute of
LDEV is not executed.
Check with the additional operation
The check is performed to ensure no identical LDEV as the existing LDEV is added. If the
existing LDEV is attempted to be added, an error is detected.
If it is not clear whether the LDEV to be added exists or not, or if the target LDEV
information does not exist in the conguration denition le, the error is not detected.
Therefore, the script is executed and the LDEV is added.
Context check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 118
The command as the target of the check is shown below.
raidcom add ldev {-parity_grp_id <gno-sgno>| -external_grp_id
<gno-sgno> | -pool {<pool ID#> | <pool naming> | snap}}
{-ldev_id <ldev#> | -tse_ldev_id <ldev#>} {-capacity <size>
| -offset_capacity <size> | -cylinder <size>} [-emulation
<emulation type>][-location <lba>][-mp_blade_id <mp#>]
[-clpr <clpr#>]
Check with the attribute setting
The check is performed regardless of whether or not the operation is performed for the
existing LDEV. If the operation is attempted to be performed for an LDEV that does not
exist, an error is detected.
If it is not clear whether the LDEV as the target of the operation exists in the
conguration denition le, or if the target LDEV information does not exist in the
conguration denition le, the error is not detected.
The commands as the target of the check are shown below.
■raidcom add lun -port <port#> [<host group name>] {-ldev_id <ldev#> [-lun_id<lun#>]
| -grp_opt <group option> -device_grp_name <device group name> [<device name>]}
■raidcom delete lun -port <port#> [<host group name>] {-lun_id <lun#> | -ldev_id
<ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device
name>]}
■raidcom add journal -journal_id <journal ID#> {-ldev_id <ldev#> …[-cnt<count>] | -
grp_opt <group option> -device_grp_name <device group name> [<device name>]} [-
mp_blade_id <mp#> | -timer_type <timer type>]
■raidcom delete journal -journal_id <journal ID#> [-ldev_id <ldev#> | -grp_opt <group
option> -device_grp_name <device group name> [<device name>]]
■raidcom add snap_pool {-pool_id <pool ID#> [-pool_name <pool naming>] | -
pool_name <pool naming> [-pool_id <pool ID#>] | -pool_id <pool ID#> -pool_name
<pool naming>} {-ldev_id <ldev#> …[-cnt<count>] | -grp_opt <group option> -
device_grp_name <device group name> [<device name>]}[-user_threshold <%>]
■raidcom add dp_pool {{-pool_id <pool ID#> [-pool_name <pool naming>] | -
pool_name <pool naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -pool_name
<pool naming>} {-ldev_id <ldev#> …[-cnt <count>] | -grp_opt <group option> -
device_grp_name <device group name> [<device name>]}[ -user_threshold
<threshold_1> [<threshold_2>]]
■raidcom extend ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name
<device group name> [<device name>]} -capacity <size> | -oset_capacity <size> | -
cylinder <size>
■raidcom check_ext_storage external_grp {-external_grp_id <gno-sgno> | -ldev_id
<ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device
name>]}
■raidcom add device_grp -device_grp_name <ldev group name> <device name> -
ldev_id <ldev#>… [-cnt <count>]
LDEV check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 119
■raidcom delete device_grp -device_grp_name <device group name> -ldev_id<ldev#>…
[-cnt <count>]
■raidcom modify ldev -ldev_id <ldev#> {-status <status> [<level>] | -ldev_name <ldev
naming> | -mp_blade_id <mp#>| -ssid <value> | -command_device < y/n > [Security
value]}
■raidcom initialize ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name
<device group name> [<device name>]} -operation <type>
Check with the deletion operation
It is checked to ensure that the operation is not intended to be performed for the LDEV
that is already deleted. If it is, an error is detected.
If it is not clear whether the LDEV as the target of the operation exists in the
conguration denition le or not (if the target LDEV information does not exist in the
conguration denition le), the error is not detected.
The command as the target of the check is shown below.
■raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option> -
device_grp_name <device group name> [<device name>]}
The example of the script where the existing LDEV is attempted to be added to the
already created LDEV and the execution result of the context check is shown below.
Example of script
raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M
Execution result
C:\HORCM\etc>raidcom get ldev -ldev_id 1 -cnt 65280 -store ldevconf_65
> ldevconf_65.txt
C:\HORCM\etc>raidcom -zt 3_defined_ldev.bat -load ldevconf_65.dat
-checkmode precheck
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity
100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -
capacity 100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity
100M
Example of script (the text in bold indicates the invalid conguration denition.)
raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M
LDEV check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 120
raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M
for /l %%i in (1,1,3) do (raidcom add ldev -parity_grp_id 01-01 -
ldev_id %%i -capacity 100M)
for /l %%i in (1,1,3) do (
raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M)
Execution result (the text in bold indicates the contents of the error accompanying
the invalid conguration denition in the script.)
C:\HORCM\etc>raidcom get ldev -ldev_id 1 -cnt 65280 -store ldevconf_65 >
ldevconf_65.txt
C:\HORCM\etc>raidcom -zt 3_defined_ldev.bat -load ldevconf_65.dat
-checkmode precheck
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity
100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity
100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity
100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity
100M
raidcom: LDEV(1) is already existing as status is [1] on UnitID# 0.
raidcom_#5 : [EX_CTXCHK] Context Check error
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity
100M
raidcom: LDEV(2) is already existing as status is [1] on UnitID# 0.
raidcom_#6 : [EX_CTXCHK] Context Check error
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity
100M
raidcom: LDEV(3) is already existing as status is [1] on UnitID# 0.
raidcom_#7 : [EX_CTXCHK] Context Check error
The number in raidcom # of raidcom_#7: [EX_CTXCHK] Context Check error is the
number of times of performing the raidcom command by using <work le>. The number
of times is incremented each time the raidcom command is executed.
Port check
The check is performed from the following perspective. Note that checking for object
information related to the port, such as external volume group or RCU, or an attribute of
port, is not executed.
Checking for attribute setting
It is checked whether the operation is performed for the existing port. If the port does
not exist, an error is detected.
Port check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 121
If it is not clear whether the port as the target of the operation exists in the conguration
denition le or not (if the target port information does not exist in the conguration
denition le), the error is not detected.
The commands as the target of the check are shown below.
■raidcom modify port -port <port#> {[-port_speed <value>] [-loop_id <value>][-
topology <topology>] [-security_switch < y|n >] | -port_attribute <port attribute>}
■raidcom add external_grp -path_grp <path group#> -external_grp_id <gnosgno> -port
<port#> -external_wwn <wwn strings> -lun_id <lun#> [-emulation <emulation type>] [-
clpr <clpr#>]
■raidcom add path -path_grp <path group#> -port <port#> -external_wwn <wwn
strings>
■raidcom delete path -path_grp <path group#> -port <port#> -external_wwn <wwn
strings>
■raidcom check_ext_storage path -path_grp <path group#> -port <port#> -
external_wwn <wwn strings>
■raidcom disconnect path -path_grp <path group#> -port <port#> -external_wwn
<wwn strings>
■raidcom add rcu {-rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid>| -cu_free <serial#>
<id> <pid>} -mcu_port <port#> -rcu_port <port#>
For example, if a path is attempted to be added to a port that does not exist, an error is
detected. An example of the script where the error is detected and the execution result
of the actual Context check are shown below.
Example of script (the text in bold indicates the part of incorrect conguration
denition.)
raidcom add path -path_grp 1 -port CL1-C -external_wwn 50060e80,06fc4180
raidcom add path -path_grp 1 -port CL1-D -external_wwn 50060e80,06fc4190
raidcom add path -path_grp 1 -port CL1-E -external_wwn 50060e80,06fc41a0
Execution result (the text in bold indicates the contents of the error accompanying
the invalid conguration denition in the script.)
C:\HORCM\etc>raidcom get port -store portcnf_27.dat
PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWN
CL1-A FIBRE TAR AUT EF N FCAL N 0 64539
06fc1b000000fc1b
CL1-B FIBRE TAR AUT EF N FCAL N 0 64539
50060e8006fc1b01
CL2-A FIBRE TAR AUT EF N FCAL N 0 64539
50060e8006fc1b10
CL2-B FIBRE TAR AUT EF N FCAL N 0 64539
50060e8006fc1b11
CL3-A FIBRE TAR AUT E8 N FCAL N 0 64539
50060e8006fc1b20
Port check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 122
CL3-B FIBRE TAR AUT E0 N FCAL N 0 64539
50060e8006fc1b21
CL4-A FIBRE TAR AUT D6 N FCAL N 0 64539
50060e8006fc1b30
CL4-B FIBRE TAR AUT D2 N FCAL N 0 64539
50060e8006fc1b31
CL5-A FIBRE TAR AUT E4 N FCAL N 0 64539
50060e8006fc1b40
CL5-B FIBRE TAR AUT DC N FCAL N 0 64539
50060e8006fc1b41
CL6-A FIBRE TAR AUT D5 N FCAL N 0 64539
50060e8006fc1b50
CL6-B FIBRE TAR AUT D1 N FCAL N 0 64539
50060e8006fc1b51
CL7-A FIBRE ELUN AUT E2 N FCAL N 0 64539
50060e8006fc1b60
CL7-B FIBRE ELUN AUT DA N FCAL N 0 64539
50060e8006fc1b61
CL8-A FIBRE TAR AUT D4 N FCAL N 0 64539
50060e8006fc1b70
CL8-B FIBRE TAR AUT CE N FCAL N 0 64539
50060e8006fc1b71
C:\HORCM\etc>raidcom -zt 4_no_port.bat -load portcnf_27.dat -checkmode
precheck
C:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-C -external_wwn
50060e80,06fc4180
raidcom: PORT(2) does not exist as status is [2] on UnitID# 0.
raidcom_#2 : [EX_CTXCHK] Context Check error
C:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-D -external_wwn
50060e80,06fc4190
raidcom: PORT(3) does not exist as status is [2] on UnitID# 0.
raidcom_#3 : [EX_CTXCHK] Context Check error
C:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-E -external_wwn
50060e80,06fc41a0
raidcom: PORT(4) does not exist as status is [2] on UnitID# 0.
raidcom_#4 : [EX_CTXCHK] Context Check error
Host group check
The check is performed from the following perspective. Note that checking for an
attribute of host group, or for a name of host group is not executed.
Check with the attribute setting
Checks whether the operation is performed for an existing host group. If the host group
does not exist, an error is detected.
If it is not clear whether the target port or host group exists (if the target port or host
group information does not exist in the conguration denition le), the error is not
detected.
Host group check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 123
The commands as the target of the check are shown below.
■raidcom modify host_grp -port <port#> [<host group name>] -host_mode <host
mode> [-host_mode_opt <host mode option> … ]
■raidcom add hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings>
■raidcom delete hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN
strings>
■raidcom set hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings> -
wwn_nickname <WWN Nickname>
■raidcom reset hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN
strings>
■raidcom add lun -port <port#> [<host group name>] {-ldev_id <ldev#> [-lun_id<lun#>]
| -grp_opt <group option> -device_grp_name <device group name> [<device name>]}
■raidcom delete lun -port <port#> [<host group name>] {-lun_id <lun#> | -ldev_id
<ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device
name>]}
Check with deletion operation
It is checked to ensure that the operation is not intended to be performed for the host
group that is already deleted. If the host group is already deleted, an error is detected.
If it is not clear whether the target port or host group exists or not (if the target port or
host group information does not exist in the conguration denition le), the error is not
detected.
The command as the target of the check is shown below.
raidcom delete host_grp -port <port#> [<host group name>
For example, if the host group that does not exist is attempted to be deleted, an error is
detected. An example of the script where the error is detected and the execution result
of the actual context check are shown below.
Example of script (the text in bold indicates the part of incorrect conguration
denition.)
raidcom delete host_grp -port CL1-A-0
raidcom delete host_grp -port CL1-A-1
raidcom delete host_grp -port CL1-A-2
Execution result (the text in bold indicates the contents of the error accompanying
the invalid conguration denition in the script.)
C:\HORCM\etc>raidcom get host_grp -port CL1-A -store hostgrpcnf_27_cl1-
a.dat
PORT GID GROUP_NAME Serial# HMD HMO_BITs
Host group check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 124
CL1-A 0 1A-G00 64539 LINUX/IRIX
C:\HORCM\etc>raidcom -zt 6_no_hstgrp.bat -load hostgrpcnf_27_cl1-a.dat
-checkmode precheck
C:\HORCM\etc>raidcom delete host_grp -port CL1-A-0
C:\HORCM\etc>raidcom delete host_grp -port CL1-A-1
raidcom: PORT-HGRP(0-1) does not exist as status is [2] on UnitID# 0.
raidcom_#3: [EX_CTXCHK] Context Check error
C:\HORCM\etc>raidcom delete host_grp -port CL1-A-2
raidcom: PORT-HGRP(0-2) does not exist as status is [2] on UnitID# 0.
raidcom_#4 : [EX_CTXCHK] Context Check error
Configuration check
The contents of a script le can be checked whether the operation is performed for the
existing resource or not.
Before performing the conguration check, execute the following command, acquire the
current conguration information, and store it in the work le specied by the -store
option.
Check the operation for LDEV
raidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt
<group option> -device_grp_name <device group name> [<device name>]}
-store <work file>
Check the operation for Port
raidcom get port -port -store <work file>
Check the operation for Host group
raidcom get host_grp -port <port#> -store <work file>
After acquiring the conguration information, execute the script by specifying the
conguration le.
raidcom -zt <created script file name> -load <work file>
Resource location and parameter
MP blade location and parameter
To specify MP blade IDs by the raidcom add ldev command, specify the following IDs.
Conguration check
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 125
MP blade names and parameters for VSP G1x00 and VSP F1500
MP blade name MP blade number MP blade ID
MPB-1MA 0 0
MPB-1MB 1 1
MPB-1PE 2 2
MPB-1PF 3 3
MPB-2MA 4 4
MPB-2MB 5 5
MPB-2PE 6 6
MPB-2PF 7 7
MPB-1MC 8 8
MPB-1MD 9 9
MPB-1PL 10 10
MPB-1PM 11 11
MPB-2MC 12 12
MPB-2MD 13 13
MPB-2PL 14 14
MPB-2PM 15 15
MP blade names and parameters for VSP
MP blade name MP blade number MP blade ID
MPB-1MA 0 0
MPB-1MB 1 1
MPB-2MC 2 2
MPB-2MD 3 3
MPB-1ME 4 4
MPB-1MF 5 5
MPB-2MG 6 6
MP blade location and parameter
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 126
MP blade name MP blade number MP blade ID
MPB-2MH 7 7
MP unit names and parameters for HUS VM
MP unit name MP blade number MP blade ID
MPU-10 0 0
MPU-11 1 1
MPU-20 2 2
MPU-21 3 3
LDEV grouping function
The LDEV grouping function enables you to create a group of multiple LDEVs (device
group function and copy group function).
Overview
CCI can be used to create a group of multiple LDEVs by dening copy groups, which are a
group of copy pairs. This is accomplished in both the primary and secondary
conguration denition les by dening the group names of the combined LDEVs
(dev_name of HORCM_DEV or HORCM_LDEV).
To change copy group information, modify the primary and secondary conguration
denition les. For example, to change the LDEV conguration of copy group dbA,
change the LDEV information in conguration denition les A and B.
See the gure for LDEV grouping for USP V/VM and earlier.
LDEV grouping function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 127
For Virtual Storage Platform and later, CCI can be used to create a group of multiple
LDEVs by dening device groups. This is accomplished by dening device groups in either
the primary or secondary conguration denition le, but not both. By dening a device
group, LDEV information can be changed or dened in one operation. It is not required
to modify LDEV information in both conguration denition les. For example,
referencing LDEVs or creating pools can be executed at the same time, because all LDEVs
in the device group are subjected to the operation.
See the gure for LDEV grouping for VSP and later (device group and copy group).
Overview
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 128
However, for executing replication function commands in CCI, two device groups must be
combined and dened as a copy group.
When dening a device group or copy group by a command, the command can be issued
from multiple CCI instances because the group information is dened in the storage
system.
Overview
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 129
Device group definition methods
To dene a device group or copy group in the CCI that supports Virtual Storage Platform
or later, use one or both of following methods.
■Execute a command:
Create a device group with the raidcom add device_grp command, and execute
the raidcom add copy_grp command specifying the name of the device group to
dene a copy group. When the command is executed, a description corresponding to
HORCM_LDEV of CCI is dened in the storage system. Then, dene HORCM LDEVG in
the conguration le to incorporate it into the CCI instance. This can be executed at
CCI that supports Virtual Storage Platform or later.
■Dene a conguration denition le:
Dene HORCM_LDEV or HORCM_DEV of the conguration denition les of the
primary and secondary volumes. For denition details, see Conguration denition
le.
A device name is a name given to an LDEV in each device group. This is equivalent to the
dev_name denition of HORCM_DEV. A device name is not required, but it is convenient
to use to specify device group or device name instead of LDEV number. However, to
create a pool or a journal, specifying LDEV number is required.
The LDEVs that have the same device name are recognized as a pair in the primary and
secondary device group. Therefore, make match the device name for the LDEV to be a
pair. Also, the number of LDEVs in the device group must be the same at the primary and
secondary sides. Pairs are operated in the ascending sequence of the LDEV numbers. If
there is no corresponding device name of LDEV in the device group to be paired, an error
might be occurred on the pair operation.
Read operations and command device settings
When grouping LDEVs, if HORCM_LDEVG on the primary side and secondary side is not
dened, the read operation of CCI is dierent depending on the command device
settings. The following table shows the details.
HORCM_LDE
VG
Command device setting
Reading of
device group
or copy group
information
Security to be
set
Securi
ty
User
authenticati
on
Group
informatio
n
acquisitio
n
Not dened OFF OFF OFF Do not read No security
ON Do not read Only
HORCM_DEV
allowed
Device group denition methods
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 130
HORCM_LDE
VG
Command device setting
Reading of
device group
or copy group
information
Security to be
set
Securi
ty
User
authenticati
on
Group
informatio
n
acquisitio
n
OFF ON OFF Read1User
authentication
required
ON Do not read User
authentication
required
Only
HORCM_DEV
allowed
ON OFF OFF Read1CMD security
ON Do not read CMD security
Only
HORCM_DEV
allowed
ON ON OFF Read1CMD security
User
authentication
required
ON Do not read CMD security
User
authentication
required
Only
HORCM_DEV
allowed
Dened - - - Read2-
Notes:
1. Read the entire group information in the storage system.
2. Read the information of device group and copy group from the contents of the
conguration denition le regardless of the setting of the command device.
Read operations and command device settings
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 131
Defining device groups
A device group is created by specifying a device name and a device group name. Once a
device group is created, the device group name, the LDEV number, and the information if
there is copy group denition or not are stored in the storage system as conguration
information.
The maximum number of device groups is 1,024 in one storage system. The maximum
65,279 LDEVs can be placed under the device group. And one LDEV can be placed in
multiple device groups.
Notes when specifying a device name
■Multiple device names can be dened in one LDEV (Max: 1,024 names).
■The length of a device name must be up to 32 characters.
■In the device group that does not become an element of copy a group, the same
device name can be used in the same device group.
■In the device group that becomes an element of a copy group, a device group name
must be unique in the device group. It is because a pair is created between LDEVs that
have same device names in respective primary and secondary volumes at the group
operation of a replication series command.
Notes when specifying a device group name
■The length of a device group name must be up to 32 characters.
■A device group name must be unique within the storage system. The device group
name cannot be duplicated in one storage system.
■When a device group name is specied by the raidcom command option and an
LDEV to operate is specied by the device name, all devices that have the same name
with the beginning of the specied name will be operated.
The contents of the following operations that can be executed for a device group are
expressed hereafter with its use cases.
1. Device group creation
2. LDEV addition to device group
3. LDEV deletion from device group
4. Device group deletion
Note:
The following symbols are used in the use cases described hereafter.
Dening device groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 132
Creating device groups
Specify the LDEV number and the device group name to create a device group.
Use cases
The following examples show use cases for creating a device group.
■Creating a device group congured of simplex volumes with dierent device names.
■Creating a device group congured of a simplex volume and a paired volume with
dierent device names.
■Creating a device group congured of simplex volumes with same device names.
Adding LDEVs to device groups
Specify the device group name and the LDEV number to add the LDEV to the device
group.
Creating device groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 133
Use Cases
The following gures show use cases that can be added an LDEV to a device group.
■Adding an LDEV (simplex volume) with a dierent device name to a device group.
■Adding an LDEV (paired volume) with a dierent device name to a device group.
■Adding an LDEV to a device group already including the same device name.
The device name can be duplicated in the case of not creating the copy group by
specifying a device group.
Deleting LDEVs from device groups
Specify the device group name and the LDEV number to delete the LDEV from the device
group.
LDEV can be deleted from the device group associating a copy group. The pair status
does not change even if the LDEV is deleted from the device group.
Use Cases
The following gures show use cases that can be deleted an LDEV from a device group.
■Deleting an LDEV (simplex volume) not associated with a copy group from a device
group.
■Deleting an LDEV (paired volume) not associated with a copy group from a device
group.
Deleting LDEVs from device groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 134
■Deleting an LDEV (simplex volume) associated with a copy group from a device group.
■Deleting an LDEV (paired volume) associated with a copy group from a device group.
Deleting device groups
Specify the device group name and the LDEV number to delete the LDEV in the device
group. If all of the LDEVs conguring the device group are deleted from the device, the
relevant device group is deleted. And, even if a device group is deleted, the pair status of
the pair in the device group does not change.
Use Cases
The following gures show use cases that can be deleted an LDEV from a device group.
■Deleting a device group congured of simplex volumes and not associated with a
copy group.
■Deleting a device group congured of a simplex volume and a paired volume and not
associated with a copy group.
Deleting device groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 135
■Deleting a device group congured of simplex volumes and associated with a copy
group.
■Deleting a device group congured of paired volumes and associated with a copy
group.
Copy group function
Dening a copy group by specifying two device groups: one device group from primary
side and one device group from secondary side, whether they are inside or outside the
storage system. A copy group cannot be dened by specifying more than one device
group from just one side of primary or secondary.
When a copy group is created, which device group is primary and which is secondary
cannot be specied. Therefore, it is specied at the time of actual pair creation. As
conguration information, a copy group name, a device group name (primary and
secondary), and an MU# are maintained in the storage system.
The notes when operating copy groups are shown below.
When creating a copy group
■In case of creating a copy group by executing a command, a copy group cannot be
created through direct specication of multiple LDEVs. Create a copy group by
specifying a device group.
■In one device group associated as a copy group, the same device name cannot be
dened.
■Copy groups with the same name cannot be dened within the same storage system.
■One device group cannot be dened to multiple copy groups.
■The maximum number of copy groups per storage system is 16,384.
■At the time of consistency group creation (pair creation) and consistency group
deletion (pair deletion), the collaboration with the group operations (device group
creation/deletion, copy group creation/deletion) is not performed.
Copy group function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 136
When deleting a copy group
■If a copy group is deleted, the association of two device groups is deleted. However,
the actual pair status, the consistency group ID and others are not changed (not
aected). Even if the pair status in the copy group is not single and the copy group is
deleted, the copy group deletion processing is performed.
■If an LDEV is deleted from a device group associated as a copy group, the relevant
LDEVs are deleted from all the associated copy groups.
■A copy group denes the relationship of device groups. Therefore, it is not possible to
specify an LDEV and remove it from the copy group.
■Regardless of the pair status (copy status), it is possible to exclude LDEVs from device
groups associated as a copy group.
The contents of the following operations that can be executed for a copy group are
expressed hereafter with its use cases.
1. Copy group creation
2. LDEV addition to copy group
3. LDEV deletion from copy group
4. Copy group deletion
5. Pair operation by specifying a copy group
Note: The following symbols are used in the use cases described hereafter.
Creating copy groups
Specify the names of two device groups to create a copy group. The same device name
must not be dened for any LDEVs in a specied device group. A copy group can be
created whether the LDEV in the device group is paired status or not.
Creating copy groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 137
Use cases
The following shows use cases that can be created a copy group.
■Creating a copy group in cases where two device groups are congured of simplex
volumes and the device names and the LDEV numbers in the respective device groups
are the same.
In the following example, when a copy group is created, the LDEVs within the device
names of A to A and B to B become a subject of pair operation.
■Creating a copy group in cases where two device groups are congured of paired
volumes and the device names and the LDEV numbers in the respective device groups
are the same.
In the following example, although pairs have been created on the device names of A
to A and B to B, a copy group can be created.
Adding LDEVS to copy groups
Specify the name of the device group for which you created a copy group to add an
LDEV. It is not possible to add LDEVs directly to the copy group.
If the device group you want to specify has the same device name, you cannot add the
LDEV.
Adding LDEVS to copy groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 138
Use cases
The following gures show use cases that can be added an LDEV to the device group
associating a copy group.
■Adding an LDEV with a dierent device name (simplex volume) to a device group
forming a copy group.
■Adding an LDEV with a dierent device name (paired volume) to a device group
forming a copy group.
Deleting LDEVs from copy groups
Specify the device group name for which you created a copy group to delete an LDEV.
You can delete either simplex volume or paired volume LDEVs.
It is not possible to delete LDEVs directly from the copy group.
Deleting LDEVs from copy groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 139
Use cases
The following shows use cases that can be deleted LDEVs from the device group forming
a copy group.
■Deleting an LDEV (simplex volume) from a device group forming a copy group.
■Deleting an LDEV (paired volume) from a device group forming a copy group.
Deleting copy groups
Specify the dened copy group to delete it.
Use cases
A copy group can be deleted even if it is congured of simplex volumes or paired
volumes.
Deleting copy groups
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 140
The following shows use cases that can be deleted a copy group.
■Deleting a copy group congured of simplex volumes.
■Deleting a copy group congured of paired volumes.
Pair operation by specifying a copy group
Specifying a copy group and creating a pair. Pairs are created for which the same device
names of LDEV dened in respective device groups of the LDEVs. Therefore, it is required
to give a same device name for the item to be operated as a pair.
If a consistency group attribute is valid and no consistency group ID is specied,
automatically assign a consistency group ID (1 copy group=1 consistency group). If the
automatic consistency group assignment is specied and the other pairs in a copy group
already have consistency group IDs, assign the same consistency group ID.
If there is no target LDEV to be a pair in the copy group, the process is terminated by
detecting an error.
Pair operation by specifying a copy group
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 141
Use cases
As an example of pair operation, the following shows use cases that can be created a
pair by specifying a copy group.
■Creating a pair in cases where the device names and the numbers of LDEVs in two
device groups in a copy group congured of simplex volumes are the same.
In the following example, pairs are created with LDEVs that have the same device
name, A to A and B to B.
■Creating a pair in cases where the device names and the numbers of LDEVs in two
device groups in a copy group congured of simplex volumes and paired volumes are
the same.
In the following example, a pair is created with LDEVs for the device name A. And no
operation is performed for the volumes of device name B that are already formed
into copy pairs.
■Creating a pair in cases where dierent device names exist in two device groups in a
copy group congured of simplex volumes.
In the following example, a pair for device name A can be created, but not for device
name B and C because they have dierent names.
Pair operation by specifying a copy group
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 142
■Creating a pair in cases where the device names in two device groups in a copy group
congured of simplex volumes and paired volumes are dierent.
In the following example, a pair for device name A to A can be created. For the device
name B and C, although it does not change the paired status, but an error occurs
because they have dierent device names.
■Creating a pair in cases where the numbers of LDEVs in two device groups in a copy
group congured of simplex volumes are dierent.
In the following example, pairs are created for the device name A to A and B to B.
Pair operations with mainframe volumes
You can create a pair with mainframe LDEVs using CCI. However, some of the replication
functions are not available in CCI. For more detailed information, see the user manual
for the replication function: Hitachi TrueCopy® for Mainframe User Guide, Hitachi Universal
Replicator for Mainframe User Guide, or Hitachi ShadowImage® for Mainframe User Guide.
Using "dummy" LUs for mainframe LDEVs
Pseudo-LUs called "dummy" LUs are used to access mainframe LDEVs in CCI. The dummy
LUs are unconditionally dened for all mainframe device emulation types. Since the
dummy LUs are used only by CCI, other user interfaces such as Storage Navigator and
host servers do not display the dummy LUs. Two dummy LUs are assigned to each
mainframe LDEV. The port IDs of the mainframe PCBs are assigned as the port IDs for
the dummy LUs. Host modes cannot be dened for dummy LUs.
To determine the port number for dummy LUs, use the following formula:
Port#:Installed Port#(*1) (LDEV# / 0x4000) × 32
Installed Port#(*1) (LDEV# / 0x4000) × 32+1
Pair operations with mainframe volumes
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 143
*1: The lowest port number of the installed mainframe ports.
TID: (LDEV# & 03xFCO)/64
LU-M: (LDEV# &0x3F)
To perform pair operations on mainframe volumes just like on open-system volumes,
include the mainframe LDEV# in the HORCM_LDEV section of the conguration denition
le. If you have mainframe pairs that already exist, you can verify their MU # using the
raidscan command.
Pair status and access permission for mainframe LDEVs
The pair status of mainframe LDEVs is displayed in the same way as for open-system
LDEVs. However, access permissions to mainframe P-VOLs and S-VOLs are dierent from
those of open volumes. The following tables show the pair status and access
permissions for mainframe LDEVs. For more information about displayed pair status of
open LDEVs, see TrueCopy/ShadowImage/Universal Replicator pair status.
Pair status and access permission for TrueCopy/TrueCopy for Mainframe
Pair status in Storage
Navigator Pair status in CCI Access to
mainfram
e P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfram
e
SMPL Simplex SMPL SMPL Read/
write
enabled
Read/write
enabled
not in pair
COPY Pending COPY COPY Read/
write
enabled
Reject copying
PAIR Duplex PAIR PAIR Read/
write
enabled
Reject pair
PSUS (pair
suspende
d split)
Suspende
d
PSUS PSUS Read/
write
enabled
Reject1suspend
PSUE (pair
suspende
d error)
Suspende
d
PSUE PSUE Read/
write
enabled
Reject1suspend by
failure
Pair status and access permission for mainframe LDEVs
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 144
Pair status in Storage
Navigator Pair status in CCI Access to
mainfram
e P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfram
e
PDUB - PDUB -2- - inconsistenc
y in LUSE
status
SSWS SSWS SSWS SSWS - Read/write
enabled
HAM only/
horctakeover
only
Notes:
1. When the system option mode 20 is on, this is a read only volume.
2. PDUB (inconsistency in LUSE status) does not exist in the mainframe system.
Pair status and access permission for Universal Replicator/Universal Replicator for
Mainframe
Pair status in
Storage Navigator Pair status in CCI Access to
mainframe
P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfram
e
SMPL Simplex SMPL SMPL Read/write
enabled
Read/write
enabled
not in pair
COPY Pending COPY COPY Read/write
enabled
Reject copying
PAIR Duplex PAIR PAIR Read/write
enabled
Reject pair
PSUS (pair
suspende
d split)
Suspend PSUS PSUS Read/write
enabled
Reject* suspend
PSUE (pair
suspende
d error)
Suspend PSUE PSUE Read/write
enabled
Reject* suspend
Suspendi
ng
Suspendi
ng
PAIR PAIR Read/write
enabled
Reject pair
Deleting Deleting PAIR /
COPY
PAIR /
COPY
Read/write
enabled
Reject pair/
copying
Pair status and access permission for mainframe LDEVs
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 145
Pair status in
Storage Navigator Pair status in CCI Access to
mainframe
P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfram
e
HOLD Hold PSUS PSUS Read/write
enabled
Reject* suspend
HOLDING Holding PSUS PSUS Read/write
enabled
- suspend
PSUS
(HLDE)
Hlde PSUE PSUE Read/write
enabled
Reject suspend
PFUL Suspend PFUL PFUL Read/write
enabled
Reject suspend
PFUS Suspend PFUS PFUS Read/write
enabled
Reject suspend
SSWS Suspend SSWS SSWS - Read/write
enabled
suspend
*When system option mode 20 is on, this is a read-only volume.
Pair status and access permission for ShadowImage/ShadowImage for Mainframe
Pair status in Storage
Navigator Pair status in CCI Access to
mainframe
P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfra
me
SMPL Simplex SMPL SMPL Read/write
enabled
Read/write
enabled
simplex
COPY(PD) Pending COPY COPY Read/write
enabled
Reject copying
PAIR Duplex PAIR PAIR Read/write
enabled
Reject pair
COPY (SP) SP-Pend COPY COPY Read/write
enabled
Reject suspend (in
COPY(SP)
COPY-COPY)
PSUS (SP) V-split PSUS PSUS Read/write
enabled
Read/write
enabled
suspend (in
Quick Split
PSUS-COPY)
Pair status and access permission for mainframe LDEVs
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 146
Pair status in Storage
Navigator Pair status in CCI Access to
mainframe
P-VOL
Access to
mainframe
S-VOL NotesOpen
Mainfram
e Open
Mainfra
me
PSUS (pair
suspended
split)
Split PSUS PSUS Read/write
enabled
Read/write
enabled
suspend
PSUE (pair
suspended
error)
Suspend PSUE PSUE Read/write
enabled
Reject suspend by
failure
COPY (RS) Resync COPY COPY Read/write
enabled
Reject resynchronizi
ng
COPY (RS-
R)
Resync-R RCPY RCPY Reject Reject restoring
Operational differences for multiplatform volumes
The following table shows the operational dierences for TrueCopy, Universal Replicator,
and ShadowImage multiplatform volumes.
LU path
definition
LU path
information
reported to CCI
ShadowImage
operations
TrueCopy
operations
Universal
Replicator
operations
LU path is
dened.
Actual LU path
information is
reported.
ShadowImage for
Mainframe
operations
Commands
are rejected.
Commands
are rejected.
LU path is
not dened.
Dummy LU
number is
reported.
ShadowImage for
Mainframe
operations
Commands
are rejected.
Commands
are rejected.
Operational differences for replication commands
The following table shows the dierences between open volumes and mainframe
volumes in replication commands. For details on the dierences, see the manual for
each program product.
Operational dierences for multiplatform volumes
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 147
Comman
d Option Description
Operation
in open
systems
Operation in
mainframe
systems Notes
paircreat
e*
-c
<size>
Species
track size
when
copying.
TrueCopy:
You can
specify 1 to
15 tracks.
TrueCopy for
Mainframe:
3 or 15 tracks
When you
specify the
number 1 to 3,
the copy
speed is 3
tracks.
When you
specify the
number 4 to
15, the copy
speed is 15
tracks.
This option is not
supported in
Universal
Replicator or
Universal
Replicator for
Mainframe.
There is no
dierence between
ShadowImage and
ShadowImage for
Mainframe.
-m grp
[CTG
ID]
If CTG ID is
not
specied,
CTG ID is
automaticall
y assigned
and a pair is
registered to
the
consistency
group. If CTG
ID is
specied, a
pair is
registered to
the CTG ID in
use.
You can
specify this
option.
You can
specify this
option.
ShadowImage
pairs and
ShadowImage for
Mainframe pairs
cannot be
registered to the
same CTG ID. If
both ShadowImage
pairs and
ShadowImage for
Mainframe pairs
are registered to
one group, the
command ends
abnormally.
pairsplit -r
-rw
Species
access mode
to S-VOL
after
splitting a
pair.
-r: Read
only
-rw: Read/
write
enabled
The volume
cannot be
read
regardless of
the specied
options.
This option is only
for TrueCopy,
TrueCopy for
Mainframe,
Universal
Replicator, and
Universal
Replicator for
Mainframe.
Operational dierences for replication commands
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 148
Comman
d Option Description
Operation
in open
systems
Operation in
mainframe
systems Notes
You cannot specify
this option in
ShadowImage or
ShadowImage for
Mainframe.
*If the capacity of the S-VOL is larger than that of the P-VOL, you cannot create a pair
with CCI. To create a TrueCopy for Mainframe pair with volumes that dier in capacity,
use Business Continuity Manager or Storage Navigator.
Notes:
■A mainframe primary volume can also be called a source volume or a main volume.
■A mainframe secondary volume can also be called a target volume or a remote
volume.
Global storage virtualization function
The global storage virtualization function enables you to minimize rewrites of
conguration denition les (horcm*.conf) when you operate volumes migrated from
older models to the VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00
models. You can also minimize the modication of the script le that you used for the
older models, when you operate volumes using the script le created by you. For details
about the global storage virtualization function, see the Provisioning Guide for the storage
system. Volume migration (nondisruptive migration) from older models by using the
global storage virtualization function is supported only on the VSP G1000, VSP G1500,
VSP F1500, VSP Gx00 models, and VSP Fx00 models.
Global storage virtualization function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 149
System configuration example with the global storage virtualization
function
This topic shows a system conguration with the global storage virtualization function. In
this conguration, a virtual storage machine is created in two storage systems
respectively. Volumes in the virtual storage machine are given virtual LDEV IDs.
■Primary site
●Storage system: VSP G1000 (S/N: 67000)
●Virtual storage machine: VSP (S/N: 65000)
●LDEV ID of VSP G1000: 10:00 and 10:01
●Virtual LDEV ID: 01:00 and 01:01
■Secondary site
●Storage system: VSP G1000 (S/N: 68000)
●Virtual storage machine: VSP (S/N: 66000)
●LDEV ID of VSP G1000: 10:00 and 10:01
●Virtual LDEV ID: 02:00 and 02:01
Using CCI with the global storage virtualization function
To use CCI with the system conguration using the global storage virtualization function,
the following two methods can be used.
■Specifying a virtual storage machine to HORCM_VCMD in conguration denition les
■Specifying a virtual storage machine to command options (that is, -s <seq#> or -u
<unit id>)
System conguration example with the global storage virtualization function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 150
If you specify the virtual storage machine to HORCM_VCMD of the conguration le, the
shell scripts can be used continuously, because you do not need to modify their scripts.
However, if you dene HORCM_VCMD, you cannot operate the virtual storage machine
whose the serial number is not specied by HORC_VCMD. If you specify the virtual
storage machine to the command options (that is, -s <seq#> or -u <unit id>) instead of
specifying with HORCM_VCMD, you can also operate the virtual storage machine of the
serial number not specifying to HORCM_VCMD.
After you change the virtual storage machine conguration with the raidcom add
resource command or the raidcom delete resource command, restart HORCM.
Using CCI with the global storage virtualization function
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 151
Configuration definition file settings with global storage virtualization
This topic shows conguration denition le settings with the global storage
virtualization function. For details on other parameters, see Conguration denition le.
The global storage virtualization function is supported on the VSP G1000 storage system,
VSP G1500, VSP F1500, VSP Gx00 models, and VSP Fx00 models.
■HORCM_CMD:
Specify a volume belonging to meta_resource or a virtual storage machine in the
storage system as the command device. CCI obtains the virtual storage machine
information dened in the storage system via the specied command device, and
congures the virtual storage machine components.
When you specify a volume that belongs to a virtual storage machine, note the
following:
●Use the serial number of the virtual storage machine and the virtual LDEV ID for
the serial number and LDEV ID which you are specifying for HORCM_CMD.
●You cannot specify HORCM_VCMD to the same conguration denition le.
●You cannot dene the volume that does not belong to the virtual storage machine
to the HORCM_CMD of the same conguration denition le.
●When you specify multiple volumes of virtual storage machines associated with
the same serial number, these volumes must belong to the same storage system.
Note: The mkconf command lets you create the conguration denition
le by importing the special le name from the standard input. When you
create a conguration denition le by using the mkconf command, make
sure that the special le name of the volume that belongs to the virtual
storage machine and the special le name of the volume that does not
belong to the virtual storage machine are dierent.
■HORCM_VCMD:
In HORCM_VCMD, specify the serial number of the virtual storage machine to be
operated by this instance.
You cannot operate the virtual storage machines whose serial numbers are not
specied in HORCM_VCMD. To operate more than one virtual storage machine from a
instance, specify each serial number of the virtual storage machines in a new line with
HORCM_VCMD. To operate the virtual storage machine specied in the second or
later of HORCM_VCMD, use the command options (for example, -s <seq#> or -u <unit
id>). If you omit the options of the command, the virtual storage machine of which
you rst specied serial number is operated. Even if you specify the virtual storage
machine of which the serial number is not specied in HORCM_VCMD with the
command option (-s <seq#> or -u <Unit ID>), the error (EX_ENOUNT) occurs.
Conguration denition le settings with global storage virtualization
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 152
■HORCM_LDEV:
Specify volumes to be copied. Serial numbers of the virtual storage machine and
virtual LDEV IDs must be specied. You cannot specify the volumes with HORCM_DEV
in the system conguration with the global storage virtualization function. Specify the
volumes with HORCM_LDEV.
■HORCM_INST:
Specify an IP address and a service name of the remote host as it is for not using the
global storage virtualization function.
Example of the configuration definition files when specifying a virtual
storage machine by HORCM_CMD
The following examples show when a volume belonging to meta_resource is specied for
HORCM_CMD.
Note: The underlined parts indicate the information that needs to modify
from the le of the old model.
Example of the conguration denition les (HORCM0)
#/******** HORCM0 on PHOST *****/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm0 1000 3000
#/********** For HORCM_CMD ****************/
HORCM_CMD
#dev_name
\\.\CMD-367000:/dev/rdsk
HORCM_VCMD
# redefine Virtual DKC Serial# as unitIDs
65000
HORCM_LDEV
Ora dev1 65000 01:00 h1
Ora dev2 65000 01:01 h1
#/********** For HORCM_INST ****************/
HORCM_INST
#dev_group ip_address service
Ora RHOST horcm1
Example of the conguration denition les (HORCM1)
#/******** HORCM1 on RHOST *****/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm1 1000 3000
Example of the conguration denition les when specifying a virtual storage machine by HORCM_CMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 153
#/********** For HORCM_CMD ****************/
HORCM_CMD
#dev_name
\\.\CMD-368000:/dev/rdsk
HORCM_VCMD
# redefine Virtual DKC Serial# as unitIDs
66000
HORCM_LDEV
Ora dev1 66000 02:00 h1
Ora dev2 66000 02:01 h1
#/********** For HORCM_INST ****************/
HORCM_INST
#dev_group ip_address service
Ora PHOST horcm0
raidqry command display example
# raidqry -l
No Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB)
1 --- raidmanager 01-31-03/00 0 66000 80-01-00/00 81920
The following examples show when the storage system is VSP G1000 and a volume
belonging to a virtual storage system is specied for HORCM_CMD.
Note: It is not necessary to change HORCM_CMD used in the previous model
or to add HORCM_VCMD.
Example of the conguration denition les (HORCM0)
#/******** HORCM0 on PHOST *****/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm0 1000 3000
#/********** For HORCM_CMD ****************/
HORCM_CMD
#dev_name
\\ . \ CMD-65000:/dev/rdsk
HORCM_LDEV
Ora dev1 65000 01:00 h1
Ora dev2 65000 01:01 h1
#/********** For HORCM_INST ****************/
HORCM_INST
#dev_group ip_address service
Ora RHOST horcm1
Example of the conguration denition les when specifying a virtual storage machine by HORCM_CMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 154
Example of the conguration denition les (HORCM1)
#/******** HORCM1 on RHOST *****/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm1 1000 3000
#/********** For HORCM_CMD ****************/
HORCM_CMD
#dev_name
\\ . \ CMD-66000:/dev/rdsk
HORCM_LDEV
Ora dev1 66000 02:00 h1
Ora dev2 66000 02:01 h1
#/********** For HORCM_INST ****************/
HORCM_INST
#dev_group ip_address service
Ora PHOST horcm0
Specifying a virtual storage machine to HORCM_VCMD
This section covers the following topics:
■Command operations to virtual storage machines (on page 155)
■Operation target for raidcom commands when specifying the virtual storage machine
in HORCM_VCMD (on page 159)
Command operations to virtual storage machines
When HORCM starts, CCI obtains the virtual storage machine information from multiple
storage systems, and congure each virtual storage machine component. CCI regards
commands as the command to the virtual storage machine by the descriptions of the
conguration denition le or the command options (i.e., -s <seq#> or -u <unit id>), and
use their information. The following table shows how to issue the command to the
virtual storage machine for each command.
Commands
How to issue the command to the virtual
storage machine Remarks
paircreate Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairsplit Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairresync Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
Specifying a virtual storage machine to HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 155
Commands
How to issue the command to the virtual
storage machine Remarks
pairevtwait Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairvolchk Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairdisplay Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
paircurchk Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
horctakeover Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
raidvchkset Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
raidvchkdsp Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairsyncwait Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
pairmon Describe the virtual storage machine
information in HORCM_LDEV in the
conguration denition le.
---
raidscan Specify the virtual storage machine by the -s
<seq#> or the -p <port#> (to specify the unit
ID) option.
The virtual storage machine can be specied
regardless of the description contents of the
conguration denition le.
You cannot specify a
virtual storage
machine by the -u
<unit ID> option of
the raidscan
command. Use the -s
<seq#> option, or
the -p <port#> to
specify as "CL1-An"
(n is the unit ID).
Command operations to virtual storage machines
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 156
Commands
How to issue the command to the virtual
storage machine Remarks
raidar Specify the virtual storage machine by a unit
ID by the command option (-p <port#>).
The raidar command
has no option to
specify a serial
number nor a unit
ID. Use the -p
<port#> option as
"CL1-An" (specify a
unit ID in n).
raidqry --- The information of
VSP G1000, VSP
G1500, VSP F1500,
VSP Gx00 models, or
VSP Fx00 models and
the virtual storage
machine is
displayed.
raidvchkscan Specify the virtual storage machine by the
command option (-s <seq#> or -u <unit ID>).
The virtual storage machine can be specied
regardless of the description contents of the
conguration denition le.
If you are specifying
a command device in
a virtual storage
machine for which
user authentication
is disabled to the
HORCM_CMD, do not
specify the -v jnl
and -v pid option.
horcctl Specify VSP G1000, VSP G1500, VSP F1500,
VSP G200, G400, G600, G800, or VSP F400,
F600, F800 information.
If you specify the
virtual storage
machine
information, error
(No such control
device) occurs.
This command
cannot be used if
you specify a volume
belonging to a virtual
storage machine to
HORCM_CMD.
Command operations to virtual storage machines
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 157
Commands
How to issue the command to the virtual
storage machine Remarks
raidcom Specify the virtual storage machine by the
command option (-s <seq#> or -u <unit ID>).
The virtual storage machine can be specied
regardless of the description contents of the
conguration denition le.
When you specify a
volume that belongs
to meta_resource for
HORCM_CMD, if you
specify the virtual
storage machine for
the command
option, some
commands can be
executed using the
virtual storage
machine information
(see Operation target
for raidcom
commands when
specifying the virtual
storage machine in
HORCM_VCMD).
When you specify a
volume that belongs
to a virtual storage
machine for
HORCM_CMD, there
is a limitation of
which command you
can use. You can
execute by using the
virtual storage
machine information
if the raidcom
command can be
used and if you
specify the virtual
storage machine for
the command option
(see raidcom
commands for
volumes that belong
to virtual storage
machine for
HORCM_CMD).
Command operations to virtual storage machines
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 158
Operation target for raidcom commands when specifying the virtual storage
machine in HORCM_VCMD
The virtual storage machine specied in HORCM_VCMD becomes the operation target if
you do not specify the -s <seq#> (serial number) and -u <unit ID> (unit ID of the
command device) options of the raidcom commands. The operational targets according
to the denition of HORCM_VCMD are shown in the table below.
■When you specify the virtual storage machine in HORCM_VCMD and the operation
target for the raidcom command is a virtual storage machine, the operational target
is: The virtual storage machine of the rst serial number specied in HORCM_VCMD.
■When you specify the virtual storage machine in HORCM_VCMD and the operation
target for the raidcom command is VSP G1x00 and VSP F1500, VSP Gx00 models, or
VSP Fx00 models, the operational target is: VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models for which the virtual storage machine of the rst serial
number specied in HORCM_VCMD is dened.
■When you specify the virtual storage machine in HORCM_VCMD and the operation
target for the raidcom command is VSP Gx00 models or VSP Fx00 models, the
operational target is: VSP Gx00 models or VSP Fx00 models for which the virtual
storage machine of the rst serial number specied in HORCM_VCMD is dened.
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
Copy
group
raidcom get copy_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add copy_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete copy_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Device
group
raidcom get device_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add device_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete device_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
External
volume
group
raidcom get external_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add external_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete external_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 159
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom modify external_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom disconnect external_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Host
group
raidcom get host_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add host_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete host_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify host_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
WWN raidcom get hba_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add hba_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete hba_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom set hba_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom reset hba_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
iSCSI
name
and
CHAP
user
name
raidcom get hba_iscsi VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add hba_iscsi VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete hba_iscsi VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom set hba_iscsi VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom reset hba_iscsi VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 160
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom add chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom set chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom reset chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom send ping VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Journal raidcom get journal VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add journal VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete journal VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify journal VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
LDEV raidcom get ldev Virtual storage machine
raidcom add ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete ldev VSP G1x00 and VSP F1500VSP G1x00
and VSP F1500, VSP Gx00 models, or
VSP Fx00 models
raidcom modify ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom extend ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom initialize ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
LUN raidcom get lun Virtual storage machine
raidcom add lun Virtual storage machine
raidcom modify lun Virtual storage machine
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 161
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom delete lun Virtual storage machine
External
path
raidcom get path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom disconnect path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom check_ext_storage path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom check_ext_storage
external_grp
VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom discover external_storage VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom discover lun VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get external_iscsi_name VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add external_iscsi_name VSP G1x00 and VSP F1500, VSP
G1x00 and VSP F1500VSP Gx00
models, or VSP Fx00 models
raidcom delete external_iscsi_name VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify external_chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get initiator_iscsi_name VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify initiator_chap_user VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom discover
external_iscsi_name
VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom check external_iscsi_name VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 162
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
Pool raidcom get pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get dp_pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get snap_pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add dp_pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add snap_pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom reallocate pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom monitor pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom initialize pool VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Port raidcom get port VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify port VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
RCU raidcom get rcu VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add rcu VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete rcu VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify rcu VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Logical
path to
RCU
raidcom add rcu_path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 163
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom delete rcu_path VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add rcu_iscsi_port VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete rcu_iscsi_port VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get rcu_iscsi_port VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Parity
group
raidcom get parity_grp VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom initialize parity_grp VSP Gx00 models or VSP Fx00
models
raidcom modify parity_grp VSP Gx00 models or VSP Fx00
models
raidcom get parity_grp VSP G1x00 and VSP F1500
raidcom add parity_grp VSP Gx00 models, or VSP Fx00
models
raidcom delete parity_grp VSP Gx00 models, or VSP Fx00
models
Drive raidcom get drive VSP Gx00 models, or VSP Fx00
models
raidcom modify drive VSP Gx00 models, or VSP Fx00
models
SSID raidcom get ssid VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add ssid VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete ssid VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Resourc
e group
raidcom get resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 164
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom delete resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom lock resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom unlock resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom map resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom unmap resource VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
CLPR raidcom get clpr VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify clpr VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Thin
Image
raidcom get snapshot Virtual storage machine
raidcom add snapshot Virtual storage machine
raidcom delete snapshot Virtual storage machine
raidcom modify snapshot Virtual storage machine
Server
Priority
Manage
r
raidcom get spm_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get spm_group VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add spm_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom add spm_group VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete spm_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete spm_group VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify spm_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 165
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom modify spm_group VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom monitor spm_wwn VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom monitor spm_group VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify spm_ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom delete spm_ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom monitor spm_ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get spm_ldev VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Program
product
raidcom add license VSP Gx00 models or VSP Fx00
models
raidcom delete license VSP Gx00 models or VSP Fx00
models
raidcom modify license VSP Gx00 models or VSP Fx00
models
raidcom get license VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Local
replica
option
raidcom modify local_replica_opt VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get local_replica_opt VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Quorum
disk
raidcom get quorum VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom modify quorum VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom replace quorum VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Others raidcom get command_status VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 166
Operati
on type Commands
Operation targets according to the
definition of HORCM_VCMD
raidcom reset command_status VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom get error_message VSP G1x00 and VSP F1500, VSP Gx00
models, or VSP Fx00 models
raidcom commands for volumes that belong to virtual storage machine for
HORCM_CMD
You can use the following raidcom commands when you specify a volume that belongs
to virtual storage machine in HORCM_CMD:
# raidcom command
1 raidcom get ldev
2 raidcom delete ldev
3 raidcom add lun
4 raidcom get lun
5 raidcom modify port
6 raidcom get port
7 raidcom add host_grp
8 raidcom delete host_grp
9 raidcom get host_grp
10 raidcom modify host_grp
11 raidcom add hba_wwn
12 raidcom delete hba_wwn
13 raidcom get hba_wwn
14 raidcom get resource
raidcom commands for volumes that belong to virtual storage machine for HORCM_CMD
Chapter 3: CCI functions
Command Control Interface User and Reference Guide 167
Chapter 4: Starting up CCI
You can begin using the CCI software after you have installed the CCI software, set the
command device, created the conguration denition le(s), and (for OpenVMS only)
followed the porting requirements and restrictions. One or two instances of CCI can be
used simultaneously in UNIX, Windows, and OpenVMS operating system environments.
Starting up on UNIX systems
Starting up one instance of CCI on a UNIX system
Procedure
1. Modify /etc/services to register the port name/number (service) of each
conguration denition le. Make the port name/number the same on all servers:
horcm xxxxx/udp xxxxx = the port name/number for horcm.conf
2. If you want CCI to start automatically each time the system starts up, add /etc/
horcmstart.sh to the system automatic startup le (for example, /sbin/rc).
3. Execute the horcmstart.sh script manually to start the CCI instances:
# horcmstart.sh
4. Set the log directory (HORCC_LOG) in the command execution environment as
needed.
5. If you want to perform TrueCopy operations, do not set the HORCC_MRCF
environment variable. If you want to perform ShadowImage operations, set the
HORCC_MRCF environment variable for the CCI execution environment.
For B shell:# HORCC_MRCF=1 # export HORCC_MRCF
For C shell:# setenv HORCC_MRCF 1 # pairdisplay -g xxxx
Where xxxx = group name
Starting up two instances of CCI on a UNIX system
Procedure
1. Modify /etc/services to register the port name/number (service) of each
conguration denition le. The port name/number must be dierent for each CCI
instance.
horcm0 xxxxx/udp xxxxx = the port name/number for horcm0.conf horcm1
yyyyy/udpyyyyy = the port name/number for horcm1.conf
2. If you want CCI to start automatically each time the system starts up, add /etc/
horcmstart.sh 0 1 to the system automatic startup le (for example, /sbin/rc).
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 168
3. Execute the horcmstart.sh script manually to start the CCI instances:
# horcmstart.sh 0 1
4. Set an instance number to the command execution environment:
For B shell:# HORCMINST=X # export HORCMINST
X = instance number = 0 or 1
For C shell:# setenv HORCMINST X
5. Set the log directory (HORCC_LOG) in the command execution environment as
needed.
6. If you want to perform TrueCopy operations, do not set the HORCC_MRCF
environment variable. If you want to perform ShadowImage operations, set the
HORCC_MRCF environment variable for the CCI execution environment.
For B shell:# HORCC_MRCF=1 # export HORCC_MRCF
For C shell:# setenv HORCC_MRCF 1 # pairdisplay -g xxxx
xxxx = group name
Starting up on Windows systems
Starting up one instance of CCI on a Windows system
Procedure
1. Modify %windir%\system32\drivers\etc\services to register the port name/
number (service) of the conguration denition le. Make the port name/number
the same on all servers:
horcm xxxxx/udp
Where, xxxxx = the port name/number of horcm.conf
2. If you want CCI to start automatically each time the system starts up, add \HORCM
\etc\horcmstart to the system automatic startup le (for example, \autoexec.bat).
3. Execute the horcmstart script manually to start CCI:
D:\HORCM\etc> horcmstart
4. Set the log directory (HORCC_LOG) in the command execution environment as
needed.
5. If you want to perform TrueCopy operations, do not set the HORCC_MRCF
environment variable. If you want to perform ShadowImage operations, set the
HORCC_MRCF environment variable for the CCI execution environment:
D:\HORCM\etc> set HORCC_MRCF=1
D:\HORCM\etc> pairdisplay -g xxxx
xxxx = group name
Starting up on Windows systems
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 169
Starting up two instances of CCI on a Windows system
Procedure
1. Modify %windir%\system32\drivers\etc\services to register the port name/
number (service) of the conguration denition les. Make sure that the port name/
number is dierent for each instance:
horcm0 xxxxx/udp
xxxxx = the port name/number of horcm0.conf
horcm1 xxxxx/udp
xxxxx = the port name/number of horcm1.conf
2. If you want CCI to start automatically each time the system starts up, add \HORCM
\etc\horcmstart 0 1 to the system automatic startup le (for example,
\autoexec.bat).
3. Execute the horcmstart script manually to start CCI:
D:\HORCM\etc> horcmstart 0 1
4. Set an instance number to the command execution environment:
D:\HORCM\etc> set HORCMINST=X
X = instance number = 0 or 1
5. Set the log directory (HORCC_LOG) in the command execution environment as
needed.
6. If you want to perform TrueCopy operations, do not set the HORCC_MRCF
environment variable. If you want to perform ShadowImage operations, set the
HORCC_MRCF environment variable for the CCI execution environment:
D:\HORCM\etc> set HORCC_MRCF=1
D:\HORCM\etc> pairdisplay -g xxxx
xxxx = group name
Starting up on OpenVMS systems
Starting up one instance of CCI on an OpenVMS system
Procedure
1. Create the conguration denition le.
For a new installation, use the conguration denition sample le that is supplied
(SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Make a copy of the le:
$ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc]
Edit this le according to your system conguration using a text editor (for example,
eve). Register the port name (service) of the conguration denition le in
SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT.horcm xxxxx/udp
xxxxx = port number
Use the same port number in all servers. The port number can be directly specied
without registering it in "SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT".
Starting up two instances of CCI on a Windows system
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 170
2. Manually execute the HORCM startup command.
$ spawn /nowait /process=horcm horcmstart
Note: The subprocess (HORCM) created by SPAWN is terminated when
the terminal is LOGOFF or the session is terminated. If you want an
independent process to the terminal LOGOFF, use the "RUN /DETACHED"
command.
3. Conrm the conguration.
Set the log directory (HORCC_LOG) in the command execution environment as
required.
Note: If the log directory under SYS$POSIX_ROOT is shared with other
nodes, the log directory of Horc Manager must be set for each node. The
log directory of Horc Manager can be changed by setting the parameter
of horcmstart. See the Command Control Interface Command Reference for
information about horcmstart parameters.
If you want to perform ShadowImage operations, set the environment variable
(HORCC_MRCF).
$ HORCC_MRCF:=1 $ pairdisplay -g xxxx
xxxx = group name
Next steps
Note: If a system conguration change or a RAID conguration change
causes this le to change, (for example, cache size change or microcode
change), these changes will not take eect until you stop HORCM
(horcmshutdown) and restart HORCM (horcmstart). Use the "-c" option of the
pairdisplay command to verify that there are no conguration errors.
Starting up two instances of CCI on an OpenVMS system
Procedure
1. Create the conguration denition les.
For a new installation, use the conguration denition sample le that is supplied
(SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Copy the le twice, once for each
instance.
$ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc]
horcm0.conf$ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS
$POSIX_ROOT:[etc] horcm1.conf
Edit these two les according to your system conguration using a text editor (for
example, eve). Register the port name (service) of the conguration denition le in
SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT.horcm0 xxxxx/udp
xxxxx = port number horcm1 yyyyy/udp
yyyyy = port number.
Starting up two instances of CCI on an OpenVMS system
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 171
Each instance should have a unique port number. The port number can be directly
specied without registering it in "SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT".
2. Execute the HORCM startup command.
$ spawn /nowait /process=horcm0 horcmstart 0 $ spawn /nowait /
process=horcm1 horcmstart 1
Note: The subprocess (HORCM) created by SPAWN is terminated when
the terminal is LOGOFF or the session is terminated. If you want an
independent process to the terminal LOGOFF, use "RUN /DETACHED"
command.
3. Set the HORCM instance numbers in the environment in which the command is to
be executed: $ HORCMINST:=X
X = instance number (0 or 1)
4. Conrm the conguration using a CCI command.
Set the log directory (HORCC_LOG) in the command execution environment as
required.
Note: If the log directory under SYS$POSIX_ROOT is shared with other
nodes, the log directory of Horc Manager must be set for each node. The
log directory of Horc Manager can be changed by setting the parameter
of horcmstart. See the Command Control Interface Command Reference for
information about horcmstart parameters.
If you want to perform ShadowImage operations, set the environment variable
(HORCC_MRCF). $ HORCC_MRCF:=1 $ pairdisplay -g xxxx
xxxx denotes a group name.
Next steps
Note: If a system conguration change or a RAID conguration change
causes this le to change (for example, cache size change, microcode change),
these changes will not take eect until you stop HORCM (horcmshutdown 0 1)
and restart HORCM (horcmstart 0 and horcmstart 1). Use the "-c" option of
the pairdisplay command to verify that there are no conguration errors.
Starting CCI as a service (Windows systems)
Usually, CCI (HORCM) is started by executing the startup script from the Windows
services. However, in the VSS environment, there is no interface to automatically start
CCI. CCI provides the svcexe.exe command and a sample script le (HORCM0_run.txt)
so that CCI can be started automatically as a service.
Starting CCI as a service (Windows systems)
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 172
C:\HORCM\tool\ > svcexe
■Usage for adding [HORCM_START_SVC]: svcexe /A=command_path
●for deleting [HORCM_START_SVC]: svcexe /D
●for specifying a service: svcexe /S=service_name
●for dependent services: svcexe /C=service_name,service_name
This command example uses HORCM0 for registering the service name for HORCM
instance#0:
■Example for adding [HORCM0]: svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"
●for deleting [HORCM0]: svcexe /S=HORCM0 /D
●for starting [HORCM0]:
:[1] make a C:\HORCM\tool\HORCM0_run.txt le.
:[2] set a user account to this service.
:[3] conrm to start using horcmstart 0.
:[4] conrm to stop using horcmshutdown 0.
:[5] start as a service by net start HORCM0.
The following procedure is about starting CCI as a service.
Procedure
1. Register the CCI (HORCM) instance as a service. The system administrator must add
the CCI instance using the following command:
C:\HORCM\tool\ > svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"
2. Customize a sample script le. The system administrator must customize the
sample script le (HORCM0_run.txt) according to the CCI instance. For details, see
the descriptions in the HORCM0_run.txt le.
3. Set the user account. The system administrator must set the user account for the
CCI administrator as needed.
When using the GUI, use "Administrative Tools - Services - Select HORCM0 -
Logon".When using the CUI, use "sc cong" command as follows:C:\HORCM\tool
\>sc config HORCM0 obj= AccountName password= passwordIf the system
administrator uses the default account (LocalSystem), add "HORCM_EVERYCLI=1":
# **** For INSTANCE# X, change to HORCMINST=X as needed ****
START:
set HORCM_EVERYCLI=1
set HORCMINST=0
set HORCC_LOG=STDERROUT
C:\HORCM\etc\horcmstart.exe
exit 0
4. Start the CCI instance from the service. After you have conrmed starting and
stopping using "horcmstart 0" and "horcmshutdown 0", you must verify that
HORCM0 starts from the service and that HORCM0 started automatically from
REBOOT, using the following command:
Starting CCI as a service (Windows systems)
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 173
C:\HORCM\tool\>net start HORCM0
5. Stop CCI instance as a service. Instead of using the "horcmshutdown 0" command,
you must use the following command to stop HORCM0:
C:\HORCM\tool\>net stop HORCM0(By using the "horcmshutdown 0" command,
the script written into HORCM0_run.txt will automatically restart HORCM0).
Starting CCI as a service (Windows systems)
Chapter 4: Starting up CCI
Command Control Interface User and Reference Guide 174
Chapter 5: Provisioning operations with CCI
This chapter describes storage provisioning operations with CCI.
About provisioning operations
You can use CCI to perform provisioning operations on the following storage systems:
■Hitachi Virtual Storage Platform G200, G400, G600, G800
■Hitachi Virtual Storage Platform F400, F600, F800
■Hitachi Virtual Storage Platform G1x00 or Hitachi Virtual Storage Platform F1500
■Hitachi Virtual Storage Platform
■Hitachi Unied Storage VM
For details about the provisioning operations, see the Provisioning Guide for the storage
system.
Note: Be aware of the following when performing provisioning operations
using CCI:
■When you execute provisioning operations using CCI, the operation of
refreshing the window (Device Manager - Storage Navigator, SVP, GUM)
might be delayed.
■During maintenance work on the storage system (Device Manager -
Storage Navigator, maintenance utility, or Maintenance PC in modify
mode), or when the conguration is being changed from the GUI, the CCI
provisioning command might be rejected (2E10, 8000).
■When you execute commands for provisioning operations, host I/O
performance might deteriorate because of increased working ratio of
processor by updating processing of the conguration information of
storage system. If you plan to execute many commands, take account of
the impact on the I/O performance.
Overview of the configuration setting command
CCI functions enable provisioning operations such as host setting, LDEV creation, and
device group creation. These operations are performed using the raidcom conguration
setting command.
The conguration setting command is specied using the following syntax:
raidcom <action> <resource> <parameter>
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 175
The operation itself, such as add or delete, is specied in the action, and the resource
object, such as LDEV or path, is specied in the resource. The necessary value to operate
the resource object is specied in the parameter. For the details about the raidcom
conguration setting command, see the Command Control Interface Command Reference.
Because some provisioning operations can take time to process, CCI provides two ways
to execute the conguration setting command: synchronously or asynchronously.
See the gure for synchronous and asynchronous command processing.
The processing dierence between these two command types are described in
Synchronous command processing and Asynchronous command processing.
Synchronous command processing
In addition to the replication commands, the process is executed by synchronizing with a
command execution, and then returning a response after the processing is completed.
When an error occurs, the error is returned to CCI at each occurrence.
Asynchronous command processing
When an asynchronous command is executed, the command is received at the storage
system, and a response is returned before the processing is executed. The actual
processing is executed asynchronously with command input.
The completion of the asynchronous command processing can be checked with the
raidcom get command_status command. When you execute the raidcom get
command_status command after executing an asynchronous command, the raidcom
get command_status command is terminated after all asynchronous command
processing has been completed.
Errors during asynchronous command processing
When an error occurs during asynchronous command processing, the error information,
such as the total number of errors or error code (SSB1 and SSB2), is provided. After
executing the asynchronous command, execute the raidcom get command_status
command to check the error information if the asynchronous command processing
completed normally.
Synchronous command processing
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 176
Error codes SSB1 and SSB2 are stored only at the rst error occurrence. For the second
and subsequent occurrences, only the number of the error occurrence is stored with no
error code. Therefore, before executing an asynchronous command, reset the error
information in the storage system using the raidcom reset command_status
command. You can check the information in SSB1 and SSB2 by using the raidcom get
error_message command.
In asynchronous command processing, multiple commands received by the host are
executed at the same time. Therefore, the total number of errors might not correspond
with the unexecuted commands. If an error occurs in asynchronous commands, verify
the system conguration using the reference commands. For details about the reference
commands, see Available provisioning operations.
Workflow for executing asynchronous commands
When executing asynchronous commands, execute the command or script using the
following procedure:
1. Execute the raidcom reset command_status command.
The error information of asynchronous command processing in the storage system
is reset.
2. Execute the asynchronous command.
3. Execute the raidcom get command_status command to check if all
asynchronous command processing is done or if no error occurred.
Asynchronous commands
The asynchronous commands associated with the raidcom conguration setting
command provide provisioning functions. The following table lists the provisioning
functions performed by asynchronous commands and describes the required syntax. For
details about raidcom command syntax, see the Command Control Interface Command
Reference.
Function Command syntax
Blocking an LDEV raidcom modify ldev -ldev_id <ldev#> -status blk
Adding an LDEV raidcom add ldev {-parity_grp_id <gno-sgno>| -
external_grp_id <gno-sgno> | -pool {<pool ID#> |
<pool naming> | snap}} -ldev_id <ldev#> { -capacity
<size> | -oset_capacity <size> | -cylinder <size>} [-
emulation <emulation type>][-location <lba>][-
mp_blade_id <mp#>]
Deleting an LDEV raidcom delete ldev {-ldev_id <ldev#> | -grp_opt
<group option> -device_grp_name <device group
name> [<device name>] }
Workow for executing asynchronous commands
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 177
Function Command syntax
LDEV Quick Format raidcom initialize ldev {-ldev_id <ldev#> | -grp_opt
<group option> -device_grp_name <device group
name> [<device name>]} -operation qfmt
Restoring an LDEV raidcom modify ldev -ldev_id <ldev#> -status nml
Creating virtual volume for
HDP/, Dynamic Provisioning,
Dynamic Provisioning for
Mainframe, Dynamic Tiering,
active ash, , active ash for
mainframe, or Copy-on-Write
Snapshot
raidcom add ldev -pool {<pool ID#> | <pool naming>|
snap} -ldev_id <ldev#> -capacity <size>
Deleting virtual volume for
Dynamic Provisioning,
Dynamic Provisioning for
Mainframe, Dynamic Tiering,
active ash, , active ash for
mainframe, or Copy-on-Write
Snapshot
raidcom delete ldev {-ldev_id <ldev#> | -grp_opt
<group option> -device_grp_name <device group
name> [<device name>] } [-operation
initialize_capacity_saving]
Note: The -operation
initialize_capacity_saving option is available
only for DP-VOLs for which capacity saving is enabled.
Creating a pool /adding a pool
volume for Dynamic
Provisioning or Dynamic
Provisioning for Mainframe
raidcom add dp_pool {{-pool_id <pool ID#> [-
pool_name <pool naming>] | -pool_name <pool
naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -
pool_name <pool naming>} {-ldev_id <ldev#> …[-
cnt<count>] | -grp_opt <group option> -
device_grp_name <device group name> [<device
name>]}[ -user_threshold <threshold_1>
[<threshold_2>] ]
Creating a pool /adding a pool
volume for Copy-on-Write
Snapshot
raidcom add snap_pool {{-pool_id <pool ID#> [-
pool_name <pool naming>] | -pool_name <pool
naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -
pool_name <pool naming>}} {-ldev_id <ldev#> …[-
cnt<count>] | -grp_opt <group option> -
device_grp_name <device group name> [<device
name>]}[-user_threshold <%> ]
Deleting or shrinking a pool raidcom delete pool -pool {<pool ID#> | <pool
naming>}[-ldev <ldev#>]
Releasing a blocked pool raidcom modify pool -pool {<pool ID#> | <pool
naming>} -status nml
RCU registration raidcom add rcu -cu_free <serial#> <id> <pid> -
mcu_port <port#> -rcu_port <port#>
Asynchronous commands
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 178
Function Command syntax
RCU logical path addition raidcom add rcu_path -cu_free <serial#> <id> <pid> -
mcu_port <port#> -rcu_port <port#>
RCU deletion raidcom delete rcu -cu_free <serial#> <id> <pid>
RCU logical path deletion raidcom delete rcu_path -cu_free <serial#> <id> <pid>
-mcu_port <port#> -rcu_port <port#>
Creating journal/ Registering
journal volume in the journal
raidcom add journal -journal_id <journal ID#> {-ldev_id
<ldev#> …[-cnt <count>] | -grp_opt <group option> -
device_grp_name <device group name> [<device
name>]}
Deleting journal/ Deleting
journal volume from the
journal
raidcom delete journal -journal_id <journal ID#> [-
ldev_id <ldev#> | -grp_opt <group option> -
device_grp_name <device group name> [<device
name>]]
Restoration of path for the
external path
raidcom check_ext_storage path -path_grp <path
group#> -port <port#> -external_wwn <wwn strings>
Setting the external path raidcom add path -path_grp <path group#> -port
<port#> -external_wwn <wwn strings>
Mapping the external volume raidcom add external_grp -path_grp <path group#> -
external_grp_id <gno-sgno> -port <port#> -
external_wwn <wwn strings> -lun_id <lun#> [-
emulation <emulation type>]
Deleting the external path raidcom delete path -path_grp <path group#> -port
<port#> -external_wwn <wwn strings>
Releasing the mapping of
external volume
raidcom delete external_grp -external_grp_id <gno-
sgno> [-forcible]
Stopping the use of paths to
the external volume
raidcom disconnect path -path_grp <path group#> -
port <port#> -external_wwn <wwn strings>
Creating a parity group raidcom add parity_grp {-parity_grp_id <gno-sgno> | -
concatenated_parity_grp_id <gno-sgno>... } -
drive_location <drive location>... -raid_type <raid type>
[-encryption {enable|disable}] [-copy_back {enable|
disable}] [-accelerated_compression {enable| disable}]
[-clpr <clpr#>]
Deleting a parity group raidcom delete parity_grp -parity_grp_id <gno-sgno>
Setting a spare drive or
cancelling the setting
raidcom modify drive -drive_location <drive location> -
spare {enable |disable}
Asynchronous commands
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 179
Help on configuration setting commands
To see the conguration setting command help, execute any command using the -h
option, for example, raidcom - h.
raidcom -h
LDEV nickname function
As a function of conguration setting command, a nickname can be set for each LDEV.
The details of the denition for the LDEV nickname function are shown below.
The maximum length of a name is 32 characters. For one LDEV, one nickname can be
dened.
A nickname can be dened as follows:
raidcom modify ldev -ldev_id <ldev#> -ldev_name <ldev naming>
Available provisioning operations
The following provisioning operations can be performed using CCI.
Operation type Description Corresponding command
Login and logout Log in. raidcom -login <user_name> <password>
Log out. raidcom -logout
Resource Lock resource. raidcom lock resource -resource_name
<resource group name > [-time <time(sec)>]
Unlock resource. raidcom unlock resource -resource_name
<resource group name >
Display resource
group information.
raidcom get resource
Add resource group. raidcom add resource -resource_name
<resource group name> [-resource_id
<resource group_id > |-ldev_id <ldev#> | -
port <port#> | -port <port#> <host group
name> | -parity_grp_id <gno-sgno> | -
external_grp_id <gno-sgno>]
Help on conguration setting commands
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 180
Operation type Description Corresponding command
Delete resource
group.
raidcom delete resource -resource_name
<resource group name> [-ldev_id <ldev#> |
-port <port#> | -port <port#> <host group
name> | -parity_grp_id <gno-sgno> | -
external_grp_id <gno-sgno>]
Host
(see the
Provisioning
Guide)
Create host group. raidcom add host_grp -port <port#> -
host_grp_name <host group name>
Set host mode. raidcom modify host_grp -port <port#>
[<host group name>] -host_mode < host
mode> [-host_mode_opt <host mode
option> … ]
Register a host to
host group.
raidcom add hba_wwn -port <port#> [<host
group name>] -hba_wwn <WWN strings>
Delete host group. raidcom delete host_grp -port <port#>
[<host group name>]
Display host group
information.
raidcom get host_grp -port <port#> [<host
group name>]
Port
(see the
Provisioning
Guide)
Set port. raidcom modify port -port <port#> {[-
port_speed <value>] [-loop_id<value>] [-
topology <topology>] [-security_switch < y/n
>]}
Set port attribute. raidcom modify port -port <port#> -
port_attribute <port attribute>
Display port
information.
raidcom get port [-port <port#>]
Internal volume
(see the
Provisioning
Guide)
Create LDEV. raidcom add ldev {-parity_grp_id <gno-
sgno> | - external_grp_id <gno-sgno> | -
pool {<pool ID#> | <pool naming> | snap}} -
ldev_id <ldev#> {-capacity <size> | -
oset_capacity <size> | -cylinder <size>} [-
emulation <emulation type>][-location
<lba>] [-mp_blade_id <mp#>]
Display LDEV
information.
raidcom get ldev {-ldev_id <ldev#> … [-cnt
<count>] | -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]} [-key <keyword>]
Display parity group
information.
raidcom get parity_grp [-parity_grp_id <gno-
sgno>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 181
Operation type Description Corresponding command
Create a parity
group.
raidcom add parity_grp {-parity_grp_id
<gnosgno> | -concatenated_parity_grp_id
<gnosgno>... } -drive_location <drive
location>... -raid_type <raid type> [-
encryption {enable| disable}] [-copy_back
{enable|disable}] [-
accelerated_compression {enable| disable}]
[- clpr <clpr#>]
Delete a parity
group.
raidcom delete parity_grp -parity_grp_id
<gnosgno>
Dene SSID. raidcom add ssid -rcu <serial#> <mcu#>
<rcu#> <id> -ssid <ssid>
raidcom delete ssid -rcu <serial#> <mcu#>
<rcu#> -ssid <ssid>
Display drive
information.
raidcom get drive [-parity_grp_id <gno-
sgno> | -usage <usage>]
Set a spare drive, or
cancel the setting.
raidcom modify drive -drive_location <drive
location> -spare {enable | disable}
Virtual volume
(HDP, HDPz, HDT,
HDTz, active
ash, active ash
for mainframe,
or SS)
(see the
Provisioning
Guide)
Create pool for HDP
or HDPz.
raidcom add dp_pool {{-pool_id <pool ID#>
[-pool_name <pool naming>] | -pool_name
<pool naming> [-pool_id <pool ID#>]} | -
pool_id <pool ID#> -pool_name <pool
naming>}} {-ldev_id <ldev#> …[-cnt<count>]
| -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]}[-user_threshold
<threshold_1> [<threshold_2>] ]
Create pool for SS. raidcom add snap_pool {{-pool_id <pool
ID#> [-pool_name <pool naming>] | -
pool_name <pool naming> [-pool_id <pool
ID#>]} | -pool_id <pool ID#> -pool_name
<pool naming>}} {-ldev_id <ldev#> …[-
cnt<count>] | -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]}[-user_threshold <%> ]
Display pool
information for HDP,
HDPz, HDT, HDTz,
active ash, active
ash for mainframe,
or SS.
raidcom get pool [-key <keyword>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 182
Operation type Description Corresponding command
Delete pool for HDP,
HDPz, HDT, HDTz,
active ash, active
ash for mainframe,
or SS.
raidcom delete pool -pool {<pool ID#> |
<pool naming>}
Change the
threshold value of a
pool for HDP, HDPz,
HDT, HDTz, active
ash, active ash for
mainframe, or SS.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -user_threshold
<threshold_1> [<threshold_2>]
Restore a pool for
HDP, HDPz, HDT,
HDTz, active ash,
active ash for
mainframe, or SS.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -status nml
Set the maximum
rate of subscription
of a pool for HDP,
HDPz, HDT, HDTz,
active ash, or active
ash for mainframe.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -subscription <%>
Change the pool for
HDP to the pool for
HDT.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -pool_attribute dt_manual
Change the pool for
HDT to the pool for
HDP.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -pool_attribute dp
Set the newly
allocation free space
percentage of the
pool for HDT, HDTz,
active ash, or active
ash for mainframe.
raidcom modify pool -pool {<pool ID#> |
<pool naming>} -tier <Tier number><ratio>
Create virtual
volume for HDP,
HDPz, HDT, HDTz,
active ash, active
ash for mainframe,
or SS.
raidcom add ldev -pool {<pool ID#> | <pool
naming> | snap} -ldev_id <ldev#> -capacity
<size> [-emulation <emulation type>] [-
location <lba>][-mp_blade_id <mp#>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 183
Operation type Description Corresponding command
Extend capacity of
virtual volume for
HDP, HDPz, HDT,
HDTz, active ash, or
active ash for
mainframe.
raidcom extend ldev{-ldev_id <ldev#> | -
grp_opt <group option> -device_grp_name
<device group name> [<device name>]} -
capacity <size>
Set enabled or
disabled of virtual
volume tier
reallocation for HDT,
HDTz, active ash, or
active ash for
mainframe.
raidcom modify ldev -ldev_id <ldev#> -
status {enable_reallocation |
disable_reallocation}
Discard a page of
virtual volume for
HDP, HDPz, HDT,
HDTz, active ash, or
active ash for
mainframe.
raidcom modify ldev -ldev_id <ldev#> -
status discard_zero_page
Display the
information of a
pool for HDP, HDPz,
HDT, HDTz, active
ash, or active ash
for mainframe.
raidcom get dp_pool [ -key <keyword>]
Display the
information of a
pool for SS.
raidcom get snap_pool
Extend the capacity
of a pool for HDP,
HDPz, HDT, HDTz,
active ash, or active
ash for mainframe.
raidcom add dp_pool {{-pool_id <pool ID#>
[-pool_name <pool naming>] | -pool_name
<pool naming> [-pool_id <pool ID#>]} | -
pool_id <pool ID#> -pool_name <pool
naming>}} {-ldev_id <ldev#> … [-cnt<count>]
| -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]}[-user_threshold
<threshold_1> [<threshold_2>] ]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 184
Operation type Description Corresponding command
Extend the capacity
of a pool for SS.
raidcom add snap_pool {{-pool_id <pool
ID#> [-pool_name <pool naming>] | -
pool_name <pool naming> [-pool_id <pool
ID#>]} | -pool_id <pool ID#> -pool_name
<pool naming>}} {-ldev_id <ldev#> …[-
cnt<count>] | -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]}[-user_threshold <%> ]
Start or stop the
performance
monitor for HDT,
HDTz, active ash, or
active ash for
mainframe.
raidcom monitor pool -pool {<pool ID#> |
<pool naming>} -operation <type>
Start or stop the tier
reallocation of a pool
for HDT, HDTz, active
ash, or active ash
for mainframe.
raidcom reallocate pool -pool {<pool ID#> |
<pool naming>} -operation <type>
LU path
(see the
Provisioning
Guide)
Set LU path. raidcom add lun -port <port#> [<host group
name>] {-ldev_id <ldev#> [-lun_id<lun#>] | -
grp_opt <group option> -device_grp_name
<device group name> [<device name>]}
Delete LU path. raidcom delete lun -port <port#> [<host
group name>] {-lun_id <lun#> | -ldev_id
<ldev#> | -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]}
Display LU path
information.
raidcom get lun -port <port#> [<host group
name>]
External volume
(UVM)
(see the Universal
Volume Manager
User Guide)
Search external
storage.
raidcom discover external_storage -port
<port#>
Search external
volume.
raidcom discover lun -port <port#> -
external_wwn <wwn strings>
Map external
volume.
raidcom add external_grp -path_grp <path
group#> -external_grp_id <gno-sgno> -port
<port#> -external_wwn <wwn strings> -
lun_id <lun#> [-emulation <emulation
type>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 185
Operation type Description Corresponding command
Disconnect the
connection for
external volume.
raidcom disconnect external_grp {-
external_grp_id <gno-sgno> | -ldev_id
<ldev#>}
Check the
connection for
external volume and
restore it.
raidcom check_ext_storage external_grp {-
external_grp_id <gno-sgno> | -ldev_id
<ldev#>}
Unmap external
volume.
raidcom delete external_grp -
external_grp_id <gno-sgno> [-forcible]
Display mapped
external volume
information.
raidcom get external_grp [-external_grp_id
<gno-sgno>]
Create LDEV in
external volume.
raidcom add ldev - external_grp_id <gno-
sgno> -ldev_id <ldev#> -capacity <size> [-
emulation <emulation type>][-location
<lba>] [-mp_blade_id <mp#>]
Display LDEV
information created
in external volume.
raidcom get ldev {-ldev_id <ldev#> … [-cnt
<count>] | -grp_opt <group option> -
device_grp_name <device group name>
[<device name>]} [-key <keyword>]
Change cache mode
of external volume.
raidcom modify external_grp -
external_grp_id <gno-sgno> -cache_mode <
y|n >
Control cache write
of external volume.
raidcom modify external_grp -
external_grp_id <gno-sgno> -cache_inow <
y|n >
Modify ownership
MP Blade of external
volume.
raidcom modify external_grp -
external_grp_id <gno-sgno> -mp_blade_id
<mp#>
Add external path. raidcom add path -path_grp <path group#>
-port <port#> -external_wwn <wwn strings>
Delete external path. raidcom delete path -path_grp <path
group#> -port <port#> -external_wwn <wwn
strings>
Display external path
information.
raidcom get path [-path_grp <path group#>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 186
Operation type Description Corresponding command
Stop the usage of
external path.
raidcom disconnect path -path_grp <path
group#> -port <port#> -external_wwn <wwn
strings>
Restore the external
path.
raidcom check_ext_storage path -path_grp
<path group#> -port <port#> -external_wwn
<wwn strings>
Dene SSID. raidcom add ssid -rcu <serial#> <mcu#>
<rcu#> <id> -ssid <ssid>
raidcom delete ssid -rcu <serial#> <mcu#>
<rcu#> -ssid <ssid>
Mainte
nance
Host Add WWN of host
path adapter.
raidcom add hba_wwn -port <port#> [<host
group name>] -hba_wwn <WWN strings>
Delete WWN of host
path adapter.
raidcom delete hba_wwn -port <port#>
[<host group name>] -hba_wwn <WWN
strings>
Set nickname for
WWN of host path
adapter.
raidcom set hba_wwn -port <port#> [<host
group name>] -hba_wwn <WWN strings> -
wwn_nickname <WWN Nickname>
Delete nickname
from WWN of host
path adapter.
raidcom reset hba_wwn -port <port#>
[<host group name>] -hba_wwn <WWN
strings>
Display registered
WWN information of
host path adapter.
raidcom get host_grp -port <port#> [<host
group name>]
LDEV Blockade or restore
LDEV.
raidcom modify ldev -ldev_id <ldev#> -
status discard_zero_page
Create nickname for
LDEV.
raidcom modify ldev -ldev_id <ldev#> -
ldev_name <ldev naming>
Modify allocated MP
Blade to LDEV.
raidcom modify ldev -ldev_id <ldev#> -
mp_blade_id <mp#>
Format LDEV. raidcom initialize ldev {-ldev_id <ldev#> | -
grp_opt <group option> -device_grp_name
<device group name> [<device name>]} -
operation <type>
Device
group
Create device group. raidcom add device_grp -device_grp_name
<ldev group name> <device name> -ldev_id
<ldev#>… [-cnt <count>]
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 187
Operation type Description Corresponding command
Delete LDEV from
device group.
raidcom delete device_grp -
device_grp_name <device group name> -
ldev_id <ldev#>… [-cnt <count>]
Display device group
information.
raidcom get device_grp [-device_grp_name
<device group name>]
Copy
group
Create copy group. raidcom add copy_grp -copy_grp_name
<copy group name> <device group name>
[device group name] [-mirror_id <mu#> -
journal_id <journal ID#>]
Delete copy group. raidcom delete copy_grp -copy_grp_name
<copy group name>
Display copy group
information.
raidcom get copy_grp
CLPR View CLPR
conguration.
raidcom get clpr
Modify CLPR
(migrate LDEV, parity
group, external
group).
raidcom modify clpr
Remot
e copy
enviro
nment
RCU
(see the
manuals
for TC,
TCz, UR,
and
URz)
Register RCU. raidcom add rcu -cu_free <serial#> <id>
<pid> -mcu_port <port#> -rcu_port <port#>
Delete RCU. raidcom delete rcu -cu_free <serial#> <id>
<pid>
Set RCU attribute. raidcom modify rcu -cu_free <serial#> <id>
<pid> -rcu_option <mpth> <rto> <rtt>
Display RCU
information.
raidcom get rcu [-cu_free <serial#> <id>
<pid>]
RCU
path
(see the
manuals
for TC,
TCz, UR,
and
URz)
Add RCU logical
path.
raidcom add rcu_path -cu_free <serial#>
<id> <pid> -mcu_port <port#> -rcu_port
<port#>
Delete RCU logical
path.
raidcom delete rcu_path -cu_free <serial#>
<id> <pid> -mcu_port <port#> -rcu_port
<port#>
Available provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 188
Operation type Description Corresponding command
Journal
(see the
manuals
for UR
and
URz)
Register journal
volume to Journal.
raidcom add journal -journal_id <journal
ID#> {-ldev_id <ldev#> …[-cnt <count>] | -
grp_opt <group option> -device_grp_name
<device group name> [<device name>]} [-
mp_blade_id <mp#> | -timer_type <timer
type> ]
Delete journal
volume from
Journal/ Delete
journal.
raidcom delete journal -journal_id <journal
ID#> [-ldev_id <ldev#> | -grp_opt <group
option> -device_grp_name <device group
name> [<device name>]]
Change the UR
option to be used at
Journal.
raidcom modify journal -journal_id <journal
ID#> {[-data_overow_watch<time>][-
cache_mode <y/n>][-timer_type <type>]} | -
path_blocked_watch <time> [-mirror_id
<mu#>] | -mp_blade_id <mp#>
Display journal
information.
raidcom get journal [ -key
<keyword>]raidcom get journal[t]
Provisioning operations that can be performed on device
groups
You can use CCI to perform provisioning operations on device groups. When you specify
a device group, you can perform operations on all LDEVs in the device group at the same
time. For details about device groups, see LDEV grouping function.
The following table lists the provisioning operations that can be executed by specifying a
device group.
Contents of operation Command
Register a journal group to a journal raidcom add journal
Delete a journal group from a journal/delete a journal raidcom delete journal
Delete an LDEV/V-VOL raidcom delete ldev
Extend the capacity of V-VOL for Dynamic Provisioning,
Dynamic Provisioning for Mainframe, Dynamic Tiering,
active ash, Dynamic Tiering for Mainframe, or active
ash for mainframe
raidcom extend ldev
Display the LDEV information raidcom get ldev
Provisioning operations that can be performed on device groups
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 189
Contents of operation Command
Format an LDEV raidcom initialize ldev
Create an LU path raidcom add lun
Delete an LU path raidcom delete lun
Create a pool for Copy-on-Write Snapshot raidcom add snap_pool
Extend the capacity of a pool for Copy-on-Write Snapshot raidcom add snap_pool
Create a pool for Dynamic Provisioning, Dynamic
Provisioning for Mainframe
raidcom add dp_pool
Extend the capacity of a pool for Dynamic Provisioning,
Dynamic Provisioning for Mainframe, Dynamic Tiering,
active ash, Dynamic Tiering for Mainframe, or active
ash for mainframe
raidcom add dp_pool
Create a resource group raidcom add resource
Delete a resource group raidcom delete resource
Operation method
To execute a command on a device group, specify the name of the device group (max: 32
characters) and the device name in the device group (max: 32 characters).
The following shows an example of mapping the LDEVs in a device group to LUNs. When
you specify both the device group name and the device name, the operation is executed
for the LDEV that matches the specied device name in the specied device group. If you
do not specify the device name, the operation is executed for all LDEVs in the device
group.
Information of the device group
C:\HORCM\etc>raidcom get device_grp -device_grp_name grp1
LDEV_GROUP LDEV_NAME LDEV# Serial#
grp1 data0 17000 64577
grp1 data0 17001 64577
grp1 data1 17002 64577
grp1 data1 17003 64577
Result of executing raidcom add lun command
The following shows the result of executing the raidcom add lun command and
specifying device group name: grp1 and device name: data0.
C:\HORCM\etc>raidcom add lun -port CL8-A -grp_opt ldev -device_grp_name
grp1 data0
Operation method
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 190
GROUP = grp1, DEVICE = data0, UnitID = 0, LDEV = 17000(0x4268)[1], PORT =
CL8-A, LUN = none:
raidcom: LUN 0(0x0) will be used for adding.
done
GROUP = grp1, DEVICE = data0, UnitID = 0, LDEV = 17001(0x4269)[1], PORT =
CL8-A, LUN = none:
raidcom: LUN 1(0x1) will be used for adding.
done
C:\HORCM\etc>raidcom get lun -port CL8-A-0
PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITs
CL8-A 0 LINUX/IRIX 0 1 17000 - 64577
CL8-A 0 LINUX/IRIX 1 1 17001 - 64577
The following shows the result of executing the raidcom add lun command and
specifying device group name: grp1 (omitting device name).
C:\HORCM\etc>>raidcom add lun -port CL8-A -grp_opt ldev -device_grp_name
grp1
GROUP = grp1 , DEVICE = data0 , UnitID = 0 , LDEV = 17000(0x4268)[1] , PORT
= CL8-A , LUN = none :
raidcom: LUN 0(0x0) will be used for adding.
done
GROUP = grp1 , DEVICE = data0 , UnitID = 0 , LDEV = 17001(0x4269)[1] , PORT
= CL8-A , LUN = none :
raidcom: LUN 1(0x1) will be used for adding.
done
GROUP = grp1 , DEVICE = data1 , UnitID = 0 , LDEV = 17002(0x426A)[1] , PORT
= CL8-A , LUN = none :
raidcom: LUN 2(0x2) will be used for adding.
done
GROUP = grp1 , DEVICE = data1 , UnitID = 0 , LDEV = 17003(0x426B)[1] , PORT
= CL8-A , LUN = none :
raidcom: LUN 3(0x3) will be used for adding.
done
C:\HORCM\etc>>raidcom get lun -port CL8-A-0
PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITs
CL8-A 0 LINUX/IRIX 0 1 17000 - 64577
CL8-A 0 LINUX/IRIX 1 1 17001 - 64577
CL8-A 0 LINUX/IRIX 2 1 17002 - 64577
CL8-A 0 LINUX/IRIX 3 1 17003 - 64577
The following shows examples of specifying device groups and creating journal.
Operation method
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 191
Examples
C:\HORCM\etc>raidcom add device_grp -device_grp_name dg_jnl1 data1 -
ldev_id 512 513 514 515
C:\HORCM\etc>raidcom get device_grp
LDEV_GROUP Serial#
dg_jnl1 64539
C:\HORCM\etc>raidcom get device_grp -device_grp_name dg_jnl1
LDEV_GROUP LDEV_NAME LDEV# Serial#
dg_jnl1 data1 512 64539
dg_jnl1 data1 513 64539
dg_jnl1 data1 514 64539
dg_jnl1 data1 515 64539
C:\HORCM\etc>raidcom add journal -journal_id 2 -grp_opt ldev -
device_grp_name dg_jnl1
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,
PORT = none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] ,
PORT
= none , LUN = none :done
Workflow for performing provisioning operations
When you execute provisioning operations, perform the operations in the following
order to log in and lock resources rst and then unlock resources and view resource
group information after performing operations.
Workow for performing provisioning operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 192
Ste
p
Operat
ion Description Command
1 Login Logs in. raidcom -login <user_name>
<password>
2 Lockin
g
resour
ces
Locks the resource group. raidcom lock resource -
resource_name
<resource group name> [-time
<time(sec)>]
3 Provisi
oning
Performs the desired
provisioning operations.
--
4 Unlock
ing
resour
ces
Unlocks the resource group. raidcom unlock resource -
resource_name
<resource group name>
5 Displa
ying
resour
ce
group
inform
ation
Displays the resource group
information to conrm the
operations and lock
information.
raidcom get resource
6 Logout Logs out. raidcom -logout
Resource group operations
Creating resource groups
To create resource groups, perform the following provisioning operations.
Step Operation Description Command
1 Creating
resource
groups
Creates resource groups. raidcom add resource
-resource_name <resource
group name>
Resource group operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 193
Step Operation Description Command
2 Allocating
resources to
resource
groups
Species resources that
are allocated to
meta_resource (resource
group), and allocates
resources to created
resource groups.
raidcom add resource
-resource_name <resource
group name> [-ldev_id
<ldev#> | -port <port#> |
-port <port#> <host group
name> | -parity_grp_id
<gno-sgno> |
-external_grp_id
<gno-sgno>]
3 Displaying
resource
group
information
Displays a resource group
information, and conrms
execution results of
commands.
raidcom get resource
Deleting resource groups
To delete resource groups, perform the following provisioning operations.
Step Operation Description Command
1 Deleting
resources that
are allocated
to resource
groups
Deletes resources that are
allocated to resource
groups. In other words,
this operation allocates
resources to resource
group: meta_resource.
raidcom delete resource
-resource_name <resource
group name> [-ldev_id
<ldev#> | -port <port#> |
-port <port#> <host group
name> | -parity_grp_id
<gno-sgno> |
-external_grp_id
<gno-sgno>]
2Conrming
resource
deletions
Conrms that resources
are not allocated to
resource groups that you
want to delete. At that
time, allocation of
resources to the resource
group: meta_resource
must be nished.
raidcom get resource
3 Deleting
resource
groups
Deletes resource groups. raidcom delete resource
-resource_name <resource
group name>
Deleting resource groups
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 194
Step Operation Description Command
4 Displaying
resource
group
information
Displays resource group
information and conrms
results of command
executions.
raidcom get resource
Allocating resources to other resource groups
When you want to allocate resources that are already allocated to resource groups to
other resource groups, resources must be once allocated to resource group:
meta_resource. After that, allocate resources to the resource groups that you want to
allocate. LDEVs that congure journals, pools, LUSEs or device groups must be allocated
to resource groups particularly. The following shows the necessary provisioning
operations.
Step Operation Description Command
1 Deleting
resources that
are allocated
to resource
groups
Deletes resources that are
allocated to resource
groups. In other words, this
operation allocates
resources to resource
group: meta_resource.
raidcom delete resource
-resource_name <resource
group name> [-ldev_id
<ldev#> | -port <port#>
|
-port <port#> <host
group
name> | -parity_grp_id
<gno-sgno> |
-external_grp_id
<gno-sgno>]
2Conrming
resource
deletions
Conrms that resources are
not allocated to resource
groups that you want to
delete. At that time,
allocation of resources to
the resource group:
meta_resource must be
nished.
raidcom get resource
3 Allocating
resources to
resource
groups
Species resources that are
allocated to meta_resource
(resource group), and
allocates resources to
resource groups.
raidcom add resource
-resource_name <resource
group name> [-ldev_id
<ldev#> | -port <port#>
|
-port <port#> <host
Allocating resources to other resource groups
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 195
Step Operation Description Command
group
name> | -parity_grp_id
<gno-sgno> |
-external_grp_id
<gno-sgno>]
4 Displaying
resource
group
information
Displays resource group
information and conrms
results of command
executions.
raidcom get resource
LDEVs that are allocated to journals or pools must be migrated by users. We recommend
that you register LDEVs that are allocated to journals or pools as device groups, and then
operate after specifying them by the device groups.
Execution example for registering LDEVS to the pools as device
groups
The following shows the execution example of registering LDEVs to the pool as device
groups, creating resource groups in the device group unit and migrating created
resource groups.
Example 1
C:\HORCM\etc>raidcom add device_grp -device_grp_name dg_jnl1 data1 -
ldev_id 512 513 514 515
C:\HORCM\etc>raidcom get device_grp
LDEV_GROUP Serial#
dg_jnl1 64539
Example 2
C:\HORCM\etc>raidcom get device_grp -device_grp_name dg_jnl1
LDEV_GROUP LDEV_NAME LDEV# Serial#
dg_jnl1 data1 512 64539
dg_jnl1 data1 513 64539
dg_jnl1 data1 514 64539
dg_jnl1 data1 515 64539
Execution example for registering LDEVS to the pools as device groups
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 196
Example 3
C:\HORCM\etc>raidcom add resource -resource_name rsg002 -grp_opt ldev -
device_grp_name dg_jnl1
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,
PORT = none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] ,
PORT
= none , LUN = none :done
Example 4
C:\HORCM\etc>raidcom delete resource -resource_name rsg002 -grp_opt ldev -
device_grp_name dg_jnl1
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,
PORT = none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] ,
PORT
= none , LUN = none :done
GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] ,
PORT
= none , LUN = none :done
Internal volume operations
Creating internal volumes (open volumes)
To create LDEVs of internal volumes (open volumes) and make the LDEVs available to the
host, perform the following provisioning operations.
Internal volume operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 197
Step Operation Description Command
1 Setting port Enables LUN security of the
port. Modify settings such as
port topology and data
transfer speed as needed.
raidcom modify port -port
<port#> -
security_switch y
2 Creating host
group
Species port and create host
group. raidcom add host_grp -port
<port#> -host_grp_name
<host group name>
3 Setting host
mode
Species port and set host
mode for host group. raidcom modify host_grp
-port <port#>
[<host group name>]
-host_mode < host mode>
[-host_mode_opt
<host mode option> … ]
4 Displaying
host group
information
Displays host group
information and conrm
result of executing command.
raidcom get host_grp
-port <port#> [<host
group
name>]
5 Adding host to
host group
Registers host to host group
of the port. raidcom add hba_wwn
-port <port#> [<host
group
name>] -hba_wwn
<WWN strings>
6 Displaying
WWN
information
Displays WWN of connection
host registered to the host
group and conrm the result
of executing the command.
raidcom get hba_wwn -port
<port#> [<host group
name>]
7 Creating LDEV Species a parity group and
create LDEV. raidcom add ldev
-parity_grp_id <gno-
sgno>
-ldev_id <ldev#>
-capacity <size>
[-emulation <emulation
type>]
[-location <lba>]
[-mp_blade_id <mp#>]
Creating internal volumes (open volumes)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 198
Step Operation Description Command
8 Formatting
LDEV
Formats created LDEV. raidcom initialize ldev
-ldev_id <ldev#>
-operation <type>
9 Creating LDEV
nickname
(arbitrary)
Creates nickname for created
LDEV.
This operation is arbitrary.
raidcom modify ldev
-ldev_id <ldev#>
-ldev_name <ldev
naming>
10 Setting MP
blade of LDEV
Sets MP blade of created
LDEV.raidcom modify ldev
-ldev_id <ldev#>
-mp_blade_id <mp#>
11 Displaying
LDEV
information
Displays information of
created LDEV and conrm the
result of executing the
command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt
<count>]
[-key <keyword>]
12 Creating LU
path
Species port, map LDEV to
LUN and create an LU path. raidcom add lun -port
<port#> [<host group
name>] -ldev_id <ldev#>
[-lun_id<lun#>]
13 Displaying LU
path
information
Displays LU path information
and conrm the result of
executing the command.
raidcom get lun
-port <port#>
[<host group name>]
Script examples for internal volume operation (open volumes)
The following shows script examples of internal volume (open volume) operation.
Script examples for internal volume operation (open volumes)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 199
Script examples of internal volume operation (open volume) (1/3)
Script examples for internal volume operation (open volumes)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 200
Script examples of internal volume operation (open volume) (2/3)
Script examples for internal volume operation (open volumes)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 201
Script examples of internal volume operation (open volume) (3/3)
Creating internal volumes (mainframe volumes)
To create LDEVs of internal volumes (mainframe volumes) and make the LDEVs available
to the host, perform the following provisioning operations.
Step Operation Description Command
1 Setting SSID
(arbitrarily)
Congures the SSID
unless it is congured.
Set (register) the SSID by
specifying undened
LDEV numbers in the
area in which SSIDs are
not dened.
raidcom modify ldev
-ldev_id <ldev#> -
ssid<value>
2 Creating
LDEVs
Creates LDEVs by
specifying parity groups. raidcom add ldev -
parity_grp_id
<gno-sgno> -ldev_id <ldev#>
{-capacity <size> |
-offset_capacity <size> |
-cylinder <size>} [-
emulation
<emulation type>][-location
<lba>][-mp_blade_id <mp#>]
3 Formatting
LDEVs
Formats created LDEVs. raidcom initialize ldev
-ldev_id <ldev#>
-operation <type>
Creating internal volumes (mainframe volumes)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 202
Step Operation Description Command
4 Creating LDEV
nicknames
(arbitrarily)
Creates LDEV nicknames.
This operation is
optional.
raidcom modify ldev -ldev_id
<ldev#> -ldev_name <ldev
naming>
5Conguring
MP blades of
LDEVs
Congures MP blades of
created LDEVs. raidcom modify ldev -ldev_id
<ldev#> -mp_blade_id <mp#>
6 Displaying a
LDEV
information
Displays an information
of created LDEV, and
conrms an execution
result of the command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt <count>]
[-key <keyword>]
Script examples of internal volume (mainframe volumes) operations
The following shows the script examples of internal volume (mainframe volume)
operations.
Script examples of internal volume (mainframe volumes) operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 203
Virtual volume (Dynamic Provisioning) operations
Creating virtual volumes (Dynamic Provisioning)
Use the following provisioning operations to create LDEVs of virtual volumes (Dynamic
Provisioning) and make the LDEVs available to the host.
Virtual volume (Dynamic Provisioning) operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 204
Table 1 Operations and descriptions
Step
Operation
overview Description Executed command
1 Setting port Enable LUN security for the
port. Modify settings such as
port topology and data
transfer speed as needed.
raidcom modify port -port
<port#> -security_switch y
2 Creating host
group
Specify port and create host
group.
raidcom add host_grp -port
<port#> -host_grp_name
<host group name>
3 Setting host
mode
Specify port and set host
mode for host group.
raidcom modify host_grp -port
<port#> [<host group name>]
-host_mode <host mode> [-
host_mode_opt <host mode
option> … ]
4 Displaying
host group
information
Display host group
information and conrm
result of executing command.
raidcom get host_grp -port
<port#> [<host group name>]
5 Adding host to
host group
Register host to host group of
the port.
raidcom add hba_wwn -port
<port#> [<host group name>]
-hba_wwn <WWN strings>
6 Displaying
WWN
information
Display WWN of connection
host registered to the host
group and conrm the result
of executing the command.
raidcom get hba_wwn -port
<port#> [<host group name>]
7 Creating LDEV Specify a parity group and
create LDEV.
raidcom add ldev -
parity_grp_id <gno-sgno> -
ldev_id <ldev#> {-capacity
<size> | -oset_capacity
<size> | -cylinder <size>} [-
emulation <emulation type>][-
location <lba>] [-mp_blade_id
<mp#>]
8 Formatting
LDEV
Format created LDEV. raidcom initialize ldev -ldev_id
<ldev#> -operation <type>
9 Creating LDEV
nickname
(arbitrary)
Create nickname for LDEV.
This operation is arbitrary.
raidcom modify ldev -ldev_id
<ldev#> -ldev_name <ldev
naming>
10 Setting MP
blade of LDEV
Set MP blade of created LDEV. raidcom modify ldev -ldev_id
<ldev#> -mp_blade_id <mp#>
Creating virtual volumes (Dynamic Provisioning)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 205
Step
Operation
overview Description Executed command
11 Displaying
LDEV
information
Display information of created
LDEV and conrm the result of
executing the command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt <count>] [-key
<keyword>]
12 Creating pool
(for Dynamic
Provisioning)
Create pool (for Dynamic
Provisioning).
raidcom add dp_pool {{-
pool_id <pool ID#> [-
pool_name <pool naming>] | -
pool_name <pool naming> [-
pool_id <pool ID#>]} | -pool_id
<pool ID#> -pool_name <pool
naming>}} -ldev_id <ldev#> …
[-cnt <count>] [-
user_threshold <threshold_1>
[<threshold_2>]]
13 Creating LDEV
(V-VOL)
Specify pool and create an
LDEV(V-VOL).
raidcom add ldev -pool {<pool
ID#> | <pool naming> | snap}
-ldev_id <ldev#> {-capacity
<size> | -oset_capacity
<size> | -cylinder <size>} [-
emulation <emulation type>][-
location <lba>] [-mp_blade_id
<mp#>]
14 Creating LDEV
(V-VOL)
nickname
(arbitrary)
(Optional) Create nickname
for the created LDEV.
raidcom modify ldev -ldev_id
<ldev#> -ldev_name <ldev
naming>
15 Setting MP
blade of LDEV
(V-VOL)
Set MP blade of created LDEV
(V-VOL).
raidcom modify ldev -ldev_id
<ldev#> -mp_blade_id <mp#>
16 Displaying
LDEV
information
(V-VOL)
Display information of created
LDEV (V-VOL) and conrm the
result of executing the
command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt <count>] [-key
<keyword>]
17 Creating LU
path
Specify port, map LDEV to LUN
and create an LU path.
raidcom add lun -port <port#>
[host group name] -ldev_id
<ldev#> [-lun_id <lun#>]
18 Displaying LU
path
information
Display LU path information
and conrm the result of
executing the command.
raidcom get lun -port <port#>
[<host group name>]
Creating virtual volumes (Dynamic Provisioning)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 206
Script examples of virtual volume (Dynamic Provisioning) operation
The following shows script examples of virtual volume (Dynamic Provisioning) operation.
Script examples of virtual volume operation (Dynamic Provisioning) (1/3)
Script examples of virtual volume (Dynamic Provisioning) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 207
Script examples of virtual volume operation (Dynamic Provisioning) (2/3)
Script examples of virtual volume (Dynamic Provisioning) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 208
Script examples of virtual volume operation (Dynamic Provisioning) (3/3)
Deleting a virtual volume for which capacity saving is enabled
You can use either of the following methods to delete virtual volume for which the
capacity saving setting is enabled:
■Execute the raidcom delete ldev command with the -operation
initialize_capacity_saving option. This command option is supported by CCI
version 01-40-03/xx and later.
■Execute the commands for blocking the LDEV, initializing the LDEV, and then deleting
the LDEV. You can use this method regardless of the CCI version.
Using the -operation initialize_capacity_saving option of the raidcom
delete ldev command to delete a virtual volume
Use the following procedure to delete a virtual volume by executing the raidcom
delete ldev command with the -operation initialize_capacity_saving
option. The command examples in this procedure use LDEV number 200 for the virtual
volume being deleted.
Procedure
1. Delete the volume by executing the raidcom delete ldev command with the -
operation initialize_capacity_saving option.
# raidcom delete ldev -operation initialize_capacity_saving -ldev_id
200
2. Verify that the delete LDEV command completed normally by executing the
raidcom get command_status command. If the command completed normally,
the value “0” is returned.
# raidcom get command_status
Deleting a virtual volume for which capacity saving is enabled
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 209
3. Check the status of the volume by executing the raidcom get ldev command.
# raidcom get ldev -ldev_id 200
While the delete LDEV operation is in process, the VOL_TYPE is REMOVING. When
the volume is deleted correctly, the VOL_TYPE changes from REMOVING to NOT
DEFINED.If VOL_TYPE is other than REMOVING or NOT DEFINED, the deletion ended
abnormally. Check CSV_Status to take either of the following actions:
■When CSV_Status shows FAILED, see the Troubleshooting Dynamic Provisioning
section in the Provisioning Guide for your system.
■When CSV_Status shows a status other than FAILED or does not show any status,
execute the raidcom delete ldev command again without specifying the -
operation initialize_capacity_saving option.
Deleting a virtual volume by blocking, initializing, and then deleting the volume
Use the following procedure to delete a virtual volume by blocking, initializing, and then
deleting the volume. The command examples in this procedure use LDEV number 200
for the virtual volume being deleted.
Procedure
1. Block the volume by executing the raidcom modify ldev command.
# raidcom modify ldev -status blk –ldev_id 200
2. Verify that the block LDEV command completed normally by executing the raidcom
get command_status command. If the command completed normally, the value
“0” is returned.
# raidcom get command_status
3. Initialize the volume by executing the raidcom initialize ldev command.
# raidcom initialize ldev -operation fmt -ldev_id 200
4. Verify that the initialize LDEV command completed normally by executing the
raidcom get command_status command. If the command completed normally,
the value “0” is returned.
# raidcom get command_status
5. Check the status of the volume by executing the raidcom get ldev command.
# raidcom get ldev -ldev_id 200
When the volume is initialized correctly, the VOL_TYPE is OPEN-V-CVS and the
CSV_Status is DISABLED.
Deleting a virtual volume by blocking, initializing, and then deleting the volume
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 210
6. Delete the volume by executing the raidcom delete ldev command.
# raidcom delete ldev -ldev_id 200
7. Verify that the delete LDEV command completed normally by executing the
raidcom get command_status command. If the command completed normally,
the value “0” is returned.
# raidcom get command_status
Virtual volume (Dynamic Provisioning for Mainframe)
operations
Creating virtual volumes (Dynamic Provisioning for Mainframe)
To create LDEVs of virtual volumes (Dynamic Provisioning for Mainframe) and make the
LDEVs available to the host, perform the following Provisioning operations.
Step
Operation
overview Description Executed command
1 Setting SSID
(arbitrarily)
Congures the SSID unless it
is congured. Set (register) the
SSID by specifying undened
LDEV numbers in the area in
which SSIDs are not dened.
raidcom modify ldev
-ldev_id<ldev#>
-ssid<value>
2 Creating
LDEVs
Creates LDEVs by specifying
parity groups. Species only
3390-V for the emulation type.
raidcom add ldev
-parity_grp_id <gno-
sgno>
-ldev_id <ldev#>
{-capacity <size> |
-offset_capacity
<size> |
-cylinder <size>}
-emulation 3390-V
-location <lba>]
[-mp_blade_id <mp#>]
3 Formatting
LDEVs
Formats created LDEVs. raidcom initialize ldev
-ldev_id <ldev#>
-operation <type>
Virtual volume (Dynamic Provisioning for Mainframe) operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 211
Step
Operation
overview Description Executed command
4 Creating LDEV
nicknames
(arbitrarily)
Creates LDEV nicknames. This
operation is optional. raidcom modify ldev
-ldev_id <ldev#>
-ldev_name <ldev
naming>
5Conguring
MP blades of
LDEVs
Congures MP blades of
created LDEVs. raidcom modify ldev
-ldev_id <ldev#>
-mp_blade_id <mp#>
6 Displaying a
LDEV
information
Displays an information of
created LDEV, and conrms an
execution result of the
command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt
<count>]
[-key <keyword>]
7 Creating the
pool (for the
Hitachi
Dynamic
Provisioning
for
mainframe)
Creates the pool for the
Hitachi Dynamic Provisioning
for mainframe.
raidcom add dp_pool
{{-pool_id <pool ID#>
[-pool_name <pool
naming>] | -pool_name
<pool naming> [-pool_id
<pool ID#>]} | -pool_id
<pool ID#> -pool_name
<pool naming>} {-
ldev_id
<ldev#> …[-cnt
<count>] |
-grp_opt <group option>
-device_grp_name
<device
group name> [<device
name>]}[ -
user_threshold
<threshold_1>
[<threshold_2>] ]
8 Creating LDEV
(V-VOL)
Species the pool and creates
LDEV (V-VOL). raidcom add ldev -pool
{<pool ID#> | <pool
naming> | snap} -
ldev_id
<ldev#> {-capacity
<size>
| -offset_capacity
<size>
Creating virtual volumes (Dynamic Provisioning for Mainframe)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 212
Step
Operation
overview Description Executed command
| -cylinder <size>}
[-emulation <emulation
type>][-location <lba>]
[-mp_blade_id <mp#>]
9 Creating LDEV
(V-VOL)
nicknames
(arbitrarily)
Creates LDEV (V-VOL)
nicknames. This operation is
optional.
raidcom modify ldev
-ldev_id <ldev#>
-ldev_name <ldev
naming>
10 Conguring
MP blades of
LDEVs (V-VOL)
Congures MP blades of
created LDEVs (V-VOL). raidcom modify ldev
-ldev_id
<ldev#> -mp_blade_id
<mp#>
11 Displaying a
LDEV (V-VOL)
information
Displays an information of
created LDEV (V-VOL), and
conrms an execution result
of the command.
raidcom get ldev -ldev_id
<ldev#> [-cnt <count>]
[-key <keyword>]
Script examples of virtual volume (Dynamic Provisioning for
Mainframe) operation
The following shows the script examples of virtual volume (Dynamic Provisioning for
Mainframe) operation.
Script examples of virtual volume (Dynamic Provisioning for Mainframe) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 213
Script examples of virtual volume operation (Dynamic Provisioning for Mainframe)
(1/2)
Script examples of virtual volume (Dynamic Provisioning for Mainframe) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 214
Script examples of virtual volume operation (Dynamic Provisioning for Mainframe)
(2/2)
Virtual volume (Dynamic Tiering) operations
Operational flow
When using the V-VOL (Dynamic Tiering), tiers of pools must be created after creating
pools, and then the performance of pools must be monitored before the operation. If
the performance of pools are insucient, extend the capacity of pool volumes (addition
of pool volumes) and of the V-VOL.
The following diagram shows the workow for conguring a virtual volume (Dynamic
Tiering) and the corresponding GUI (Device Manager - Storage Navigator) and CLI (CCI)
tasks.
Virtual volume (Dynamic Tiering) operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 215
Notes:
1. The multi-tier pool is disabled when a pool is created byCCI. Multiple media cannot
be registered as a pool volume when a pool is created. Execute tiering after
changing the multi-tier pool to the enabled status.
2. If you use the GUI, you need to create a pool volume and format LDEVs before
creating a pool. Perform this step from the Create LDEV wizard or the Format LDEVs
wizard.
In addition, if you create a pool using an external volume, you need to create a pool
volume and format the LDEVs before performing this step.
3. When the multi-tier pool is enabled, the tiering control is set to "Manual"
automatically. To change the setting to "Auto", it is required to use.
4. If you use Device Manager - Storage Navigator for this operation, you need to delete
pool volumes after deleting a pool from the Delete LDEVs window.
Note: Before creating a pool, it is required to create a virtual volume
management area on the cache memory. The virtual volume management
area is created automatically when cache memory is added. For information
about adding cache memory, please contact customer support.
Caution: The operations explained here are executable by the storage
administrator only.
Creating virtual volumes (Dynamic Tiering)
Use the following operations to create LDEVs of virtual volumes (Dynamic Tiering) and
making the LDEVs available to the host.
Table 2 Operations and descriptions
Step
Operation
overview Description Executed command
1 Setting port Make enabled the LUN
security of port. Modify setting
such as port topology and
data transfer speed as
needed.
raidcom modify port -port
<port#> -security_switch y
2 Creating host
group
Specify port and create host
group.
raidcom add host_grp -port
<port#> -host_grp_name
<host group name>
3 Setting host
mode
Specify port and set host
mode for host group.
raidcom modify host_grp -port
<port#> [<host group name>]
-host_mode <host mode> [-
host_mode_opt <host mode
option> … ]
Creating virtual volumes (Dynamic Tiering)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 216
Step
Operation
overview Description Executed command
4 Displaying
host group
information
Display host group
information and conrm
result of executing command.
raidcom get host_grp -port
<port#> [<host group name>]
5 Adding host to
host group
Register host to host group of
the port.
raidcom add hba_wwn -port
<port#> [<host group name>]
-hba_wwn <WWN strings>
6 Displaying
WWN
information
Display WWN of connection
host registered to the host
group and conrm the result
of executing the command.
raidcom get hba_wwn {-port
<port#> [<host group name>]}
7 Creating LDEV Specify a parity group and
create LDEV.
raidcom add ldev {-
parity_grp_id <gno-sgno> -
ldev_id <ldev#> {-capacity
<size> | -oset_capacity
<size> | -cylinder <size>} [-
emulation <emulation type>][-
location <lba>] [-mp_blade_id
<mp#>]
8 Formatting
LDEV
Format created LDEV. raidcom initialize ldev -ldev_id
<ldev#> -operation <type>
9 Creating LDEV
nickname
(arbitrary)
Create LDEV nickname.
This operation is arbitrary.
raidcom modify ldev -ldev_id
<ldev#> -ldev_name <ldev
naming>
10 Setting MP
blade of LDEV
Set MP blade of created LDEV. raidcom modify ldev -ldev_id
<ldev#> -mp_blade_id <mp#>
11 Displaying
LDEV
information
Display information of created
LDEV and conrm the result of
executing the command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt <count>] [-key
<keyword>]
12 Creating pool
(for Dynamic
Provisioning)
Create pool (for Dynamic
Provisioning).
raidcom add dp_pool {{-
pool_id <pool ID#> [-
pool_name <pool naming>] | -
pool_name <pool naming> [-
pool_id <pool ID#>]} | -pool_id
<pool ID#> -pool_name <pool
naming>}} -ldev_id <ldev#> …
[-cnt count>] [-user_threshold
<%> ]
Creating virtual volumes (Dynamic Tiering)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 217
Step
Operation
overview Description Executed command
13 Setting pool
option
Modify pool for Dynamic
Provisioning to pool for
Dynamic Tiering.
raidcom modify pool -pool
{<pool ID#> | <pool naming>}
-pool_attribute dt_manual
14 Adding
dierent
media to pool
volume
Add a pool volume of dierent
media to a pool for Dynamic
Tiering.
raidcom add dp_pool {{-
pool_id <pool ID#> [-
pool_name <pool naming>] | -
pool_name <pool naming> [-
pool_id <pool ID#>]} | -pool_id
<pool ID#> -pool_name <pool
naming>} -ldev_id <ldev#> …[-
cnt <count>] [ -user_threshold
<threshold_1>
[<threshold_2>] ]
15 Creating LDEV
(V-VOL)
Specify pool and create LDEV
(V-VOL).
raidcom add ldev -pool {<pool
ID#> | <pool naming> | snap}
-ldev_id <ldev#> -capacity
<size> [-emulation <emulation
type>][-location <lba>] [-
mp_blade_id <mp#>]
16 Creating LDEV
(V-VOL)
nickname
(arbitrary)
Create nickname for created
LDEV (V-VOL).
This operation is arbitrary.
raidcom modify ldev -ldev_id
<ldev#> -ldev_name <ldev
naming>
17 Setting MP
blade of LDEV
(V-VOL)
Set MP blade of created LDEV
(V-VOL).
raidcom modify ldev -ldev_id
<ldev#> -mp_blade_id <mp#>
18 Displaying
LDEV (V-VOL)
information
Display information of created
LDEV (V-VOL) and conrm the
result of executing the
command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt <count>] [-key
<keyword>]
19 Creating LU
path
Specify port, map LDEV to LUN
and create an LU path.
raidcom add lun -port <port#>
[host group name] -ldev_id
<ldev#> [-lun_id <lun#>]
20 Displaying LU
path
information
Display LU path information
and conrm the result of
executing the command.
raidcom get lun -port <port#>
[<host group name>]
Creating virtual volumes (Dynamic Tiering)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 218
Step
Operation
overview Description Executed command
21 Starting
performance
monitoring of
a pool for
Dynamic
Tiering
Start the performance
monitoring of a pool for
Dynamic Tiering.
raidcom monitor pool -pool
{<pool ID#> | <pool naming>}
-operation start
22 Stopping
performance
monitoring of
a pool for
Dynamic
Tiering
Stop the performance
monitoring of a pool for
Dynamic Tiering.
raidcom monitor pool -pool
{<pool ID#> | <pool naming>}
-operation stop
23 Instructing
reallocation of
pool for
Dynamic
Tiering
Perform instruction of
reallocation of pool for
Dynamic Tiering.
raidcom reallocate pool -pool
{<pool ID#> | <pool naming>}
-operation <type>
Script examples cript examples of virtual volume (Dynamic Tiering)
operation
The following shows the script examples of virtual volume (Dynamic Tiering) operation.
Script examples cript examples of virtual volume (Dynamic Tiering) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 219
Script examples of virtual volume operation (Dynamic Tiering) (1/3)
Script examples cript examples of virtual volume (Dynamic Tiering) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 220
Script examples of virtual volume operation (Dynamic Tiering) (2/3)
Script examples cript examples of virtual volume (Dynamic Tiering) operation
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 221
Script examples of virtual volume operation (Dynamic Tiering) (3/3)
Configuring iSCSI virtual ports
You can use CCI to enable and disable the iSCSI virtual port mode and set and delete
virtual port numbers for iSCSI ports.
Setting an iSCSI virtual port
The following procedure describes how to enable the virtual port mode for the iSCSI port
(CL4-E) and then set the virtual port number (15) and IPv4 address for the port.
Conguring iSCSI virtual ports
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 222
Procedure
1. Check the current status of the iSCSI port (CL4-E).
# raidcom get port -port CL4-E -key opt
PORT : CL4-E
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
IPV4_ADDR : 192.168.0.181
IPV4_SMSK : 255.255.255.0
:
VLAN_ID : -
ISCSI_VP_MODE : D
2. Enable the virtual port mode for the iSCSI port (CL4-E).
# raidcom modify port -port CL4-E -iscsi_virtual_port_mode enable
3. Set the virtual port number (15) and IPv4 address (192.168.4.100) for the iSCSI port
(CL4-E).
# raidcom modify port -port CL4-E -add_iscsi_virtual_port 15 -
ipv6_mode disable -ipv4_address 192.168.4.100 -ipv4_subnetmask
255.255.255.0
4. Conrm that the virtual port mode is enabled ( ISCSI_VP_MODE : E) , then make sure
that the information for the virtual port number (15) is set correctly.
# raidcom get port -port CL4-E -key opt
PORT : CL4-E
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
IPV4_ADDR : 192.168.0.181
IPV4_SMSK : 255.255.255.0
:
ISCSI_VP_MODE : E
ISCSI_VP_ID : 0 15
5. Conrm that the IPv4 address (192.168.4.100) is set for the virtual port.
# raidcom get port -port CL4-E -key opt -iscsi_virtual_port_id 15
PORT : CL4-E
ISCSI_VP_ID : 15
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
IPV4_ADDR : 192.168.4.100
IPV4_SMSK : 255.255.255.0
Deleting an iSCSI virtual port
The following procedure describes how to delete the virtual port number (15) and then
disable the virtual port mode for the iSCSI port (CL4-E).
Deleting an iSCSI virtual port
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 223
Procedure
1. Check the current status of the iSCSI port (CL4-E).
#raidcom get port -port CL4-E -key opt
PORT : CL4-E
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
ISCSI_VP_MODE : E
ISCSI_VP_ID : 0 15
2. Delete the virtual port number (15) set for the iSCSI port (CL4-E).
# raidcom modify port -port CL4-E -delete_iscsi_virtual_port 15
3. Conrm that the virtual port number (15) is deleted.
# raidcom get port -port CL4-E -key opt
PORT : CL4-E
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
IPV4_ADDR : 192.168.0.181
IPV4_SMSK : 255.255.255.0
:
ISCSI_VP_MODE : E
ISCSI_VP_ID : 0
4. Disable the virtual port mode for the iSCSI port (CL4-E).
# raidcom modify port -port CL4-E -iscsi_virtual_port_mode disable
5. Conrm that the virtual port mode is disabled ( ISCSI_VP_MODE : D).
# raidcom get port -port CL4-E -key opt
TCP_OPT : IPV6_D : SACK_E : DACK_E : INS_D : VTAG_D
:
IPV4_ADDR : 192.168.0.181
IPV4_SMSK : 255.255.255.0
:
ISCSI_VP_MODE : D
External volume operations
Creating external volumes (Fibre Channel)
Use the following provisioning operations to create LDEVs of external volumes and make
the LDEVs available from the host.
External volume operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 224
Step
Operation
overview Description Executed command
1 Setting port
attribute of
local storage
system
Set port attribute of local
storage system to
External (ELUN) port
raidcom modify port -port
<port#> -port_attribute
ELUN
2 Searching
external
storage
Display port information on
the external storage
connected to the External
port.
raidcom discover
external_storage
-port <port#>
3 Searching
external
volume
Display a list of external
volumes that can be mapped
from External port.
raidcom discover lun
-port <port#>
-external_wwn
<wwn strings>
4 Creating
external
volume
Create external volume. raidcom add ldev
- external_grp_id
<gno-sgno> -ldev_id
<ldev#> -capacity
<size>
[-emulation <emulation
type>][-location <lba>]
[-mp_blade_id <mp#>]
5 Modifying
external
volume option
Modify external volume
option (cache mode, inow
mode, and MP blade setting).
raidcom modify
external_grp
-external_grp_id
<gno-sgno> {-cache_mode
< y|n > | -cache_inflow
< y|n > | -mp_blade_id
<mp#>}
6 Checking
external
volume
information
Display external volume
information and conrm
result of executing command.
raidcom get external_grp
[-external_grp_id
<gno-sgno>]
7 Setting
external path
Set external path. Execute the
required number of
commands.
raidcom add path -
path_grp
<path group#> -port
<port#> -external_wwn
<wwn strings>
Creating external volumes (Fibre Channel)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 225
Step
Operation
overview Description Executed command
8 Displaying
external path
information
Display external path
information for and conrm
the result of executing the
command.
raidcom get path [-
path_grp
<path group#>]
9 Setting port of
external
storage
system
Make enabled the LUN
security of port. Modify
setting such as port topology
and data transfer speed as
needed.
raidcom modify port -port
<port#> -
security_switch y
10 Creating host
group
Specify port, map LDEV to
LUN and create an LU path. raidcom add host_grp -
port
<port#> -host_grp_name
<host group name>
11 Setting host
mode and
host mode
option
Specify port and set host
mode and host mode option
for host group.
raidcom modify host_grp
-port <port#> [<host
group
name>] -host_mode
<host mode>
[-host_mode_opt
<host mode option> … ]
12 Displaying
host group
information
Display host group
information and conrm
result of executing command.
raidcom get host_grp
-port <port#> [<host
group
name>]
13 Adding host to
host group
Register host to host group of
the port. raidcom add hba_wwn
-port <port#> [<host
group
name>] -hba_wwn
<WWN strings>
14 Displaying
WWN
information
Display WWN of connection
host registered to the host
group and conrm the result
of executing the command.
raidcom get hba_wwn
-port <port#> [<host
group
name>]
15 Creating LDEV Specify external volume group
and create LDEV. raidcom add ldev
- external_grp_id
Creating external volumes (Fibre Channel)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 226
Step
Operation
overview Description Executed command
<gno-sgno> -ldev_id
<ldev#> {-capacity
<size>
| -offset_capacity
<size>
| -cylinder <size>}
[-emulation <emulation
type>][-location <lba>]
[-mp_blade_id <mp#>]
16 Creating LDEV
nickname
(arbitrary)
Create nickname of created
LDEV.
This operation is arbitrary.
raidcom modify ldev
-ldev_id <ldev#>
-ldev_name <ldev naming>
17 Setting MP
blade of LDEV
Set MP blade of created LDEV. raidcom modify ldev
-ldev_id <ldev#>
-mp_blade_id <mp#>
18 Displaying
LDEV
information
Display information of
created LDEV and conrm the
result of executing the
command.
raidcom get ldev -ldev_id
<ldev#> … [-cnt
<count>]
[-key <keyword>]
19 Creating LU
path
Specify port, map LDEV to
LUN and create an LU path. raidcom add lun -port
<port#>
[<host group name>]
-ldev_id <ldev#>
[-lun_id<lun#>]
20 Displaying LU
path
information
Display LU path information
and conrm the result of
executing the command.
raidcom get lun -port
<port#>
[<host group name>]
Creating external volumes (iSCSI)
Use the following provisioning operations to create LDEVs of external volumes using
iSCSI and make the LDEVs available from the host.
Creating external volumes (iSCSI)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 227
Step
Operation
overview Description Executed command
1 Setting the
port attribute
of the local
storage
system
Set the port attribute of the
local storage system to the
External (ELUN) port.
raidcom modify port -port
<port#> -port_attribute
ELUN
2 Searching the
iSCSI target of
an external
storage
system
Display information about the
iSCSI target of the external
storage system that has the
specied IP address and is
connected to the External
(ELUN) port.
raidcom discover
external_iscsi_name
-port <port#>
-address <external IP
address>
3 Registering
the iSCSI
name of the
iSCSI target
for an
external
storage
system
Register the iSCSI target to
connect as an external
storage system.*
raidcom add
external_iscsi_name
-port <port#>
-iscsi_name <external
iscsi name>
-address <external IP
address>
4 Setting CHAP
authentication
information
for connecting
to the iSCSI
target of an
external
storage
system
When CHAP authentication is
used for connection to
external storage systems, set
the CHAP user name and a
password (secret) used by the
iSCSI target of an external
storage system for
authenticating the External
(ELUN) port of the local
storage system.
raidcom modify
initiator_chap_user
-port <port#>
[-chap_user
<username> ]
[-secret]
5 Setting CHAP
authentication
information
for connecting
to the iSCSI
target of an
external
storage
system (for
CHAP two-way
authentication
)
When CHAP authentication is
used for connection to
external storage systems, set
the CHAP user name and a
password (secret) used by the
External (ELUN) port of the
local storage system for
authenticating the iSCSI target
of an external storage system.
raidcom modify
external_chap_user
-port <port#>
-iscsi_name <external
iscsi name>
-address <external IP
address>
[-chap_user <user
name> ]
[-secret]
Creating external volumes (iSCSI)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 228
Step
Operation
overview Description Executed command
6 Testing login
to the iSCSI
target
Attempt to log in to the iSCSI
target of the external storage
system registered in the local
storage system, and display
the result.*
raidcom check
external_iscsi_name
[-port <port#>]
7 Searching
external
storage
systems
Display information of the
port on the external storage
system connected to the
External (ELUN) port.
raidcom discover
external_storage
-port <port#>
8 Searching
external
volumes
List the external volumes that
can be mapped from the
External (ELUN) port.
raidcom discover lun -
port <port#>
-external_iscsi_name
<external iscsi name>
-external_address <IP
address>
9 Mapping
external
volume
groups
Map the volume in the
external storage system to
the external volume group.
raidcom add external_grp
-path_grp <path group#>
-external_grp_id <gno-
sgno>
-port <port#>
-external_iscsi_name
<externaliscsi name>
-external_address <IP
address>
-lun_id <lun#>
[-emulation <emulation
type>]
[-clpr <clpr#>]
[-external_attribute
migration]
[-data_direct_mapping
enable]
10 Creating
external
volumes
Create an external volume. raidcom add ldev
-external_grp_id <gno-
sgno>
-ldev_id <ldev#>
-capacity <size>
[-emulation <emulation
type>]
Creating external volumes (iSCSI)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 229
Step
Operation
overview Description Executed command
[-location <lba>]
[-mp_blade_id <mp#>]
11 Modifying
external
volume
options
Modify external volume
options (cache mode, inow
mode, and MP blade settings).
raidcom modify
external_grp
-external_grp_id <gno-
sgno>
{-cache_mode { y|n } |
-cache_inflow {y|n } |
-mp_blade_id <mp#>}
12 Checking
external
volume
information
Display external volume
information and conrm the
result of executing the
command.
raidcom get external_grp
[-external_grp_id <gno-
sgno>]
13 Setting
external path
Set external path. Execute the
required number of
commands.
raidcom add path
-path_grp <path group#>
-port <port#>
-external_iscsi_name
<external iscsi name>
-external_address <IP
address>
14 Displaying
external path
information
Display external path
information and conrm the
result of executing the
command.
raidcom get path
[-path_grp <path
group#>]
15 Setting the
local storage
system port
Enable LUN security settings
of the port.
Change the IP address or the
MTU size of the port if
necessary.
raidcom modify port
-port <port#>
-security_switch y
16 Creating host
groups
Specify the port to create a
host group (iSCSI target). raidcom add host_grp
-port <port#>
-host_grp_name <host
group name>
[-iscsi_name <target
iscsi name>]
Creating external volumes (iSCSI)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 230
Step
Operation
overview Description Executed command
17 Setting the
host mode
and host
mode option
Specify the port to set the
host mode and host mode
option for the host group.
raidcom modify host_grp
-port <port#>
[<host group name>]
-host_mode < host mode>
[-host_mode_opt <host
mode option> … ]
18 Displaying
host group
information
Display host group
information and conrm the
result of executing the
command.
raidcom get host_grp
-port <port#>
[<host group name>]
19 Adding a host
to a host
group
Register the host to the host
group of the port. raidcom add hba_iscsi
-port <port#>
[<host group name>]
-hba_iscsi_name
<initiator iscsi name>
20 Displaying
iSCSI name
information
Display the iSCSI name of the
connected host registered in
the host group, and conrm
the result of executing the
command.
raidcom get hba_iscsi
-port <port#>
[<host group name>]
21 Creating
LDEVs
Specify the external volume
group to create an LDEV. raidcom add ldev
-external_grp_id <gno-
sgno>
-ldev_id <ldev#>
{-capacity <size> |
-offset_capacity <size>
|
-cylinder <size>}
[-emulation <emulation
type>]
[-location <lba>]
[-mp_blade_id <mp#>]
22 Setting LDEV
nicknames
(arbitrary)
Set a nickname of the created
LDEV.
This operation is arbitrary.
raidcom modify ldev
-ldev_id <ldev#>
-ldev_name <ldev naming>
Creating external volumes (iSCSI)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 231
Step
Operation
overview Description Executed command
23 Setting the MP
blade of an
LDEV
Set the MP blade of the
created LDEV. raidcom modify ldev
-ldev_id <ldev#>
-mp_blade_id <mp#>
24 Displaying
LDEV
information
Display information of the
created LDEV and conrm the
result of executing the
command.
raidcom get ldev
-ldev_id <ldev#> …
[-cnt <count>]
[-key <keyword>]
25 Creating an
LU path
Specify the port, map the
LDEV to the LUN, and create
an LU path.
raidcom add lun
-port <port#>
[<host group name>]
-ldev_id <ldev#>
[-lun_id<lun#>]
26 Displaying LU
path
information
Display LU path information,
and conrm the result of
executing the command.
raidcom get lun
-port <port#>
[<host group name>]
*After registering the iSCSI name of the iSCSI target for an external storage system,
perform the login test to check if you can log in to the iSCSI target correctly. If iSCSI
targets to which you cannot log in correctly due to a security setting error are
registered, attempts to check connections are made while external volumes are being
searched. As a result, external volumes and networks are loaded, and recognizing an
external volume might fail. For all iSCSI targets for which login test fails, change the
CHAP authentication information for connecting to the iSCSI target of the external
storage system, or check external storage system settings. After that, perform the login
test again to make sure that the test is successful. In addition, delete unnecessary iSCSI
targets using raidcom delete external_iscsi_name.
Script examples of external volume operations
The following shows the script examples of external volume operations.
Script examples of external volume operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 232
Script Examples of External Volume Operation (1/3)
Script examples of external volume operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 233
Script Examples of External Volume Operation (2/3)
Script examples of external volume operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 234
Script Examples of External Volume Operation (3/3)
Virtual Partition Manager operations
Virtual Partition Manager operations using CCI include migrating LDEVs, parity groups,
and external volume groups to other CLPRs.
■For information about Virtual Partition Manager operations, including important
warnings and restrictions, see the Hitachi Virtual Partition Manager User Guide for USP
V/VM or the Hitachi Virtual Partition Manager User Guide for VSP.
■For details about the CCI commands for Virtual Partition Manager operations, see the
Command Control Interface Command Reference.
Performing Virtual Partition Manager operations
The following table shows the procedure for migrating LDEVs, parity groups, and external
volume groups to other CLPRs.
Step Operation overview Description Command
1Conrming the
CLPR conguration.
Check the status of
the CLPRs. raidcom get clpr
Virtual Partition Manager operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 235
Step Operation overview Description Command
2 Migrating one of the
following to other
CLPRs:
■LDEV
■parity group
■external volume
group
Specify the LDEV
number, parity
group number, or
external volume
group number.
raidcom modify clpr -clpr
<clpr#> { -ldev_id
<ldev#> | -parity_grp_id
<gno-sgno> | -
external_grp_id <gnosgno>}
3 Verifying the CLPR
migration.
For parity group
migration, check the
status of the parity
group.
raidcom get parity_grp
Displaying CLPR information
The raidcom get clpr command lists and displays the status of the CLPRs in the
storage system. If no CLPRs have been created, CLPR0 is displayed as entire cache.
Display example:
# raidcom get clpr
CLPR CLPR_NAME TC_CAP(MB) TU_CAP(MB) WP_CAP(MB) SF_CAP(MB) U(%)
W(%)S(%)
000 Oracle_DB 40000 20000 4000 0 50 30 0
001 Oracle_DB_PROD 20000 10000 2000 0 50 10 0
003 Oracle_DB_BACK 10000 5000 500 0 50 5 0
Migrating parity groups in a CLPR
This section explains operations from checking the parity group information to moving
the parity group.
Displaying parity group information
The raidcom check the status, display the information about the parity group. See the
following example.
Displaying CLPR information
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 236
Display example:
# raidcom get parity_grp
T GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPE
R 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 32-17 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 33-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC
Moving parity groups
If you change the allocation of parity groups, parity groups are moved from another
CLPR. In this case, plural parity groups which congure the distributed parity group have
to be allocated the same CLPR. Parity groups including LDEVs where cache area of Cache
Residency is dened cannot be moved to another CLPR. For the restrictions on the
CLPR's transfer, see the Performance Guide. The following shows examples of parity
groups transfer in CLPR.
Example for moving parity group 32-17 to the CLPR number 1
# raidcom modify clpr -clpr 1 -parity_grp_id 32-17
When you move parity groups by specifying their LDEV numbers, use LDEV numbers for
virtual volumes of Dynamic Provisioning, Copy-on-Write Snapshot, or Thin Image. When
you move other volumes, specify a parity group number or external volume group
number. The following shows an example of moving a virtual volume of Dynamic
Provisioning, Copy-on-Write Snapshot, or Thin Image.
Example for moving the virtual volume of LDEV number: 02:00 to CLPR ID: 2
# raidcom modify clpr -clpr 2 -ldev_id 0x0200
Checking result of CLPR transfer
By displaying the information about parity groups, check the result of CLPR transfer. See
the following example.
Display example:
# raidcom get parity_grp
T GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPE
R 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 32-17 4 45 140000 RAID1 2D+2D 0 1 DKS2C-K072FC
R 33-16 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC
R 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC
Moving parity groups
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 237
Server Priority Manager operations
Server Priority Manager enables you to prioritize host I/O operations to provide high-
speed processing for specied hosts. The host is identied by the WWN or iSCSI name of
the host bus adapter. Server Priority Manager has two settings: prioritized and non-
prioritized. Set the prioritized option for hosts that require high-speed processing, and
the non-prioritized option for the other hosts.
The following methods are used to set the priority level, but only one of them can be
used in a single storage system:
Note: The WWN of a host bus adapter connected to a port is required when
specifying the port with CCI and setting SPM. Since the WWN of an HBA
connected to a NAS Platform port cannot be obtained, the SPM setting with
specifying these port types is not available.
■Specifying ports and WWNs of host bus adapters:
●Using SPM without registering host groups to the SPM group
●Using SPM by registering host groups in the SPM group (VSP only)
For details, see Conguring Server Priority Manager by specifying ports and WWNs of
HBAs (on page 238) .
■Specifying an LDEV and a WWN of the host bus adapter:
For details, see Conguring Server Priority Manager by specifying LDEVs and WWNs or
iSCSI names of HBAs (on page 252) .
■Specifying an LDEV and an iSCSI name of a host bus adapter:
For details, see Conguring Server Priority Manager by specifying LDEVs and WWNs or
iSCSI names of HBAs (on page 252) .
Configuring Server Priority Manager by specifying ports and WWNs of
HBAs
This section describes operations for conguring Server Priority Manager by specifying a
port and a WWN of a host bus adapter.
■Controlling the priority of I/O operations in storage systems on servers (on page 239)
■Using and managing Server Priority Manager (on page 239)
■Setting SPM names for WWNs and registering them to the SPM group (on page 240)
■Conguring Server Priority Manager by specifying ports and WWNs of HBAs (on
page 241)
■Cautions about using Server Priority Manager (on page 248)
■Cautions when using host groups after registering them in SPM groups (VSP only) (on
page 251)
Server Priority Manager operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 238
Controlling the priority of I/O operations in storage systems on servers
To control server performance, specify the I/O operation priority (prioritized or non-
prioritized), the threshold (one value for each storage system), and the upper limit (one
value for each non-prioritized WWN) for host bus adapters on a host. Set a host bus
adapter with higher priority as a prioritized WWN, and set a host bus adapter with lower
priority as a non-prioritized WWN. By adjusting the upper limit or threshold to an
appropriate value, you can maintain the number of accesses or the amount of data to be
transferred to a storage system at a higher level on a prioritized server.
Priority to be set by specifying a port and a WWN of an HBA, and control of server
performance
Priority Server performance
Non-prioritized Controls server performance based on the upper limit. The upper
limit is set for each non-prioritized WWN.
The upper limit suppresses the number of accesses to a storage
system, or the amount of data to be transferred. Monitoring
information can be displayed according to the combination of a port
and a WWN of a host bus adapter.
Prioritized Controls server performance based on the threshold. One threshold
is set for each storage system, but it cannot be set for each
prioritized WWN.
If the amount of trac goes down to the threshold, the control of the
upper limit is disabled automatically.
Monitoring information can be displayed according to the
combination of a port and a WWN of a host bus adapter.
Using and managing Server Priority Manager
You can give a nickname (SPM name) to each host WWN to assist in managing the hosts.
You can also manage WWN and the SPM name per group. The groups to which WWN
and the SPM name are registered are managed uniquely. The following table lists the
details for the Server Priority Manager operations and the management unit.
SPM Operation Management per port
Management per
system
raidcom modify spm_wwn prioritized or non-prioritized
upper limit
WWN or SPM name
threshold
raidcom modify spm_group prioritized or non-prioritized
upper limit
threshold
Controlling the priority of I/O operations in storage systems on servers
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 239
SPM Operation Management per port
Management per
system
SPM group name
raidcom add spm_wwn - SPM name
raidcom add spm_group - SPM group name
raidcom delete spm_wwn - SPM name (SPM
information per port is
also deleted.)
raidcom delete spm_group - SPM group name (SPM
information per port is
also deleted.)
raidcom get spm_wwn prioritized or non-prioritized
upper limit
WWN or SPM name
SPM group name
threshold
raidcom get spm_group prioritized or non-prioritized
upper limit
SPM group name
threshold
raidcom monitor spm_wwn performance of server (IOps/
KBps)
control mode of SPM
raidcom monitor spm_group performance of server (IOps/
KBps)
control mode of SPM
Setting SPM names for WWNs and registering them to the SPM group
The following gure shows the workow of setting SPM names for WWNs and registering
them in the SPM group.
Setting SPM names for WWNs and registering them to the SPM group
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 240
Configuring Server Priority Manager by specifying ports and WWNs of HBAs
This section describes how to use Server Priority Manager when setting a port and a
WWN of a host bus adapter. For VSP models, the procedure varies depending on
whether the host groups is registered in the SPM group. Only VSP models can register
host groups to the SPM group.
Controlling server performance when the host group is not registered in the SPM
group
The following table shows the procedure when the host group is not registered in the
SPM group.
Conguring Server Priority Manager by specifying ports and WWNs of HBAs
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 241
Ste
p
Operation
overview Description Executed command
1 Setting the
SPM
informatio
n for WWN
Set the priority
(prioritized or non-
prioritized option)
for the SPM
controlling by
specifying the
number of port to
which the host bus
adapter is connected
and WWN of the
host bus adapter.
raidcom modify spm_wwn -port <port#>
[-spm_priority <y/n>] {-limit_io |
-limit_kb | -limit_mb } <value> {-
hba_wwn <wwn_strings> | -spm_name
<nick_name>}
2 Giving a
nickname
(SPM
name).
Give a nickname to
WWN for the SPM
controlling to make
the host bus adapter
distinguishable.
raidcom add spm_wwn -port <port#>
-spm_name <nick_name> -hba_wwn
<wwn_strings>
3 Registering
WWN for
SPM to
SPM group
Specifying WWN: To
operate per group,
group multiple
WWNs for SPM
control into one
group.
raidcom add spm_group -port <port#>
-spm_group <group_name> -hba_wwn
<wwn_strings>
Specifying nickname:
To operate per
group, group
multiple WWNs for
SPM control into one
group.
raidcom add spm_group -port <port#>
-spm_group <group_name> <nick_name>
4 Checking
the SPM
informatio
n
Display the setting
state of SPM by
specifying WWN or
the SPM name.
raidcom get spm_wwn -port <port#>
[ -hba_wwn <wwn_strings> | -spm_name
<nick_name> ]
Display the SPM
information by
specifying the SPM
group name.
raidcom get spm_group -port <port#>
-spm_group <group_name>
5 Displaying
the
monitoring
informatio
n of the
prioritized
Display the
monitoring
information by
specifying WWN or
the SPM name.
raidcom monitor spm_wwn {-hba_wwn
<wwn_strings> | -spm_name
<nick_name>}
Controlling server performance when the host group is not registered in the SPM group
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 242
Ste
p
Operation
overview Description Executed command
WWN or
the non-
prioritized
WWN
Display the
monitoring
information by
specifying the SPM
group name.
raidcom monitor spm_group -spm_group
<group_name>
6 Changing
the
threshold
or the
upper limit
value of
the non-
prioritized
WWN
Change the
threshold or the
upper limit value of
the non-prioritized
WWN by specifying
WWN or the SPM
name.
raidcom modify spm_wwn -port <port#>
[-spm_priority <y/n>] {-limit_io |
-limit_kb | -limit_mb } <value> {-
hba_wwn <wwn_strings> | -spm_name
<nick_name>}
Change the
threshold or the
upper limit value of
the non-prioritized
WWN by specifying
the SPM group
name.
raidcom modify spm_group -port
<port#>
[-spm_priority <y/n>] {-limit_io |
-limit_kb | -limit_mb } <value> -
spm_group <group_name>
7 Deleting
WWN from
the SPM
targets
Delete WWN from
the SPM targets by
specifying WWN or
the SPM name.
raidcom delete spm_wwn -port <port#>
[-hba_wwn <wwn_strings> | -spm_name
<nick_name> ]
Delete WWN from
the SPM targets by
specifying the SPM
group name.
raidcom delete spm_group -port
<port#>
-spm_group <group_name>
Controlling server performance when the host group is registered in the SPM
group (VSP only)
The following table shows the procedure when the host group is registered in the SPM
group.
Note: For cautions when registering host groups to the SPM group and
operating them (VSP only), see Cautions when using host groups after
registering them in SPM groups (VSP only).
Controlling server performance when the host group is registered in the SPM group (VSP only)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 243
Ste
p
Operation
overview Description Executed command
1 Registering
the host
group that
contains
WWN
controlled
by SPM to
the SPM
group
Specify the host
group to which WWN
of the host bus
adapter is registered
and register the host
group to the SPM.
raidcom add spm_group -spm_group
<group name>
-port <port#> [<host group name>]
-spm_host_grp
2 Changing
the
threshold
or the
maximum
value of
nonpreferr
ed WWN.
Specify the host
group to change the
threshold or the
maximum value of
the nonpreferred
WWN.
raidcom modify spm_group -port
<port#>
[<host group name>] -spm_host_grp
[ -spm_priority <y/n> ] { -
limit_io |
-limit_kb | -limit_mb } <value>
3 Checking
the SPM
informatio
n
Specify the WWN
name to display the
SPM setting status.
raidcom get spm_wwn -port <port#>
[ -hba_wwn <wwn_strings> ]
4 Specify the host
group to display the
SPM setting status.
raidcom get spm_group -port <port#>
[<host group name>] -spm_host_grp
5 Specify the SPM
group name to
display the SPM
setting status.
raidcom get spm_group -port <port#>
-spm_group <group_name>
6 Displaying
monitoring
informatio
n of
preferred
or
nonpreferr
ed WWN
Specify the WWN
name to display
monitoring
information.
raidcom monitor spm_wwn {-hba_wwn
<wwn_strings> }
7 Specify the SPM
group name to
display monitoring
information.
raidcom monitor spm_group -spm_group
<group_name>
Controlling server performance when the host group is registered in the SPM group (VSP only)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 244
Ste
p
Operation
overview Description Executed command
8 Registering
WWN to
the host
group
registered
in the SPM
group, and
setting the
WWN as
the SPM
target
Register the WWN to
the host group
registered in the
SPM group to set the
WWN as the SPM
target.
raidcom add hba_wwn -port <port#>
[<host group name>] -hba_wwn <WWN
strings>
9 Deleting
from the
SPM
targets
Specify the host
group to delete it
from the SPM target.
raidcom delete spm_group -port
<port#>
[<host group name>] -spm_host_grp
10 Delete the host
group to delete it
from the SPM target.
raidcom delete host_grp -port
<port#>
[<host group name>]
11 Delete WWN from
the host group to
delete it from the
SPM target.
raidcom delete hba_wwn -port <port#>
[<host group name>] -hba_wwn <WWN
strings>
Displaying the WWN of host bus adapters
Displays the WWN of the host bus adapters that are registered in host groups.
Display example:
# raidcom get hba_wwn -port CL4-E-0
PORT GID GROUP_NAME HWWN Serial# NICK_NAME
CL4-E 0 Linux_x86 210000e08b0256f8 63528 ORA_NODE0_CTL_0
CL4-E 0 Linux_x86 210000e08b039c15 63528 ORA_NODE1_CTL_1
Setting the priority on host bus adapters
Display example: Set the host bus adapter (WWN: 210000e0,8b0256f8) to the non-
prioritized WWN, and set 5000 [IOPS] as the upper limit.
# raidcom modify spm_wwn -port CL4-E -spm_priority
n -limit_io 5000 -hba_wwn 210000e0,8b0256f8
Displaying the WWN of host bus adapters
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 245
Display example: Set the host bus adapter (WWN: 210000e0,8b039c15) to the
prioritized WWN, and set 3000 [IOPS] as the threshold.
# raidcom modify spm_wwn -port CL4-E -spm_priority
y -limit_io 3000 -hba_wwn 210000e0,8b039c15
-limit_io 3000 shown in the example of the priority setting is the threshold value of the
entire system.
Displaying the status of the prioritized WWN and the non-prioritized WWN
settings
Display the status of the prioritized WWN and the non-prioritized WWN settings and
check it. Display examples of the status of the prioritized WWN and the non-prioritized
WWN settings are shown below.
Example for displaying the status of settings of the prioritized WWN and the non-
prioritized WWN assigned under the specied port (CL4-E)
# raidcom get spm_wwn -port CL4-E
PORT SPM_MD SPM_WWN NICK_NAME GRP_NAME Serial#
CL4-E WWN 210000e08b0256f8 - - 63528
CL4-E WWN 210000e08b039c15 - - 63528
Example for displaying the status of setting to specify the WWN
(210000e08b0256f8)
# raidcom get spm_wwn -port CL4-E -hba_wwn 210000e0,8b0256f8
PORT SPM_MD PRI IOps KBps Serial#
CL4-E WWN N 5000 - 63528
Example for displaying the status of setting to specify the WWN
(210000e08b039c15)
# raidcom get spm_wwn -port CL4-E -hba_wwn 210000e0,8b039c15
PORT SPM_MD FRI IOps KBps Serial#
CL4-E WWN Y 3000 - 63528
The threshold value displayed for the prioritized WWN by using the get spm_wwn
command is set for the entire system.
Displaying the status of the prioritized WWN and the non-prioritized WWN settings
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 246
Setting SPM names for host bus adapters
The host bus adapters can be identied by checking the WWNs, but using SPM names
might make it easier to identify the host bus adapters. Display examples of setting the
SPM name of the host bus adapter are shown below.
Display example: Set the SPM name (ORA_NODE0_CTL_0) for the WWN
(210000e08b0256f8)
# raidcom add spm_wwn -port CL4-E -spm_name
ORA_NODE0_CTL_0 -hba_wwn 210000e0,8b0256f8
Display example: Set the SPM name (ORA_NODE1_CTL_1) for the WWN
(210000e08b039c15)
# raidcom add spm_wwn -port CL4-E -spm_name
ORA_NODE1_CTL_1 -hba_wwn 210000e0,8b039c15
SPM names are managed uniquely in the entire system.
Grouping multiple host bus adapters into one group
You can group the host bus adapters into SPM groups, and then use the SPM groups to
change the priorities of multiple host bus adapters at the same time. You can also set
the same upper limit value for all host bus adapters in anSPM group at the same time.
Examples of setting the SPM group:
Display example: Set the SPM name (ORA_NODE0_CTL_0) for the SPM gropup name
(WWN_GRP_LINUX0)
# raidcom add spm_group -port CL4-E -spm_group WWN_GRP_LINUX0
ORA_NODE0_CTL_0
Display example: Set the WWN (210000e08b039c15) for the SPM gropup name
(WWN_GRP_LINUX1)
# raidcom add spm_group -port CL4-E -spm_group
WWN_GRP_LINUX1 -hba_wwn 210000e0,8b039c15
SPM group names are managed uniquely in the entire system.
Obtaining monitoring information of the prioritized WWN and the non-prioritized
WWN
You can use the monitoring function to check whether the performance of the prioritized
WWN can be secured by setting the upper limit. Example of acquiring the monitoring
information:
Acquires the monitoring information by specifying the WWN (210000e08b039c15).
Setting SPM names for host bus adapters
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 247
Display example:
# raidcom monitor spm_wwn -hba_wwn 210000e0,8b039c15
PORT SPM_MD IOps KBps Serial#
CL4-E WWN 5000 5000000 63528
Stopping performance control of server by using SPM function
To stop controlling the performance of the server by using the SPM function, delete the
SPM name from the SPM targets.
Example of deleting from the SPM targets:
Delete the SPM name ("ORA_NODE0_CTL_0") from the SPM targets.
Display example:
# raidcom delete spm_wwn -port CL4-E -spm_name ORA_NODE0_CTL_0
Cautions about using Server Priority Manager
The following table describes the cautions about using Server Priority Manager.
Caution Description
Exclusive
access control
with Storage
Navigator
Server Priority Manager settings are exclusive for CCI operations and
Storage Navigator operations:
■If you set Server Priority Manager using CCI, you cannot set Server
Priority Manager from Storage Navigator. You need to delete all
Server Priority Manager settings made using CCI, and then use
Server Priority Manager on Storage Navigator to make the Server
Priority Manager settings.
■If you set Server Priority Manager using Storage Navigator, you
cannot set Server Priority Manager using CCI. You need to delete
all Server Priority Manager settings made using Storage Navigator
(for instructions see the Performance Guide), and then use Server
Priority Manager from CCI to make the Server Priority Manager
settings.
Performance
Monitor of
Device
Manager -
Storage
Navigator
If you set Server Priority Manager using CCI, you cannot use a part of
Performance Monitor of Device Manager - Storage Navigator. For
details, see the Performance Guide.
Stopping performance control of server by using SPM function
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 248
Caution Description
Maintenance When you perform the following operations, the upper limit value
control might be disabled for about two minutes:
■Adding, replacing, or removing cache memory
■Changing the system conguration
■Updating the rmware
■VSP Gx00 models and VSP Fx00 models: Replacing the controller
(CTL)
■VSP Gx00 models and VSP Fx00 models: Adding, replacing, or
removing front-end module (CHB)
■VSP G1x00 and VSP F1500: Replacing MP blades
■VSP G1x00 and VSP F1500: Adding, replacing, or removing front-
end directors (CHAs)
■Powering on and o the storage system
Note:
The upper limit value control might be disabled when an
abnormal condition that causes the login or logout of the
host occurs, such as a network failure or damage on the
HBA or Fibre cable. Resolve the cause of the unexpected
login/logout behavior, and then enable the upper limit
value control.
When
specifying ports
and WWNs of
HBAs: Deleting
SPM names or
SPM group
names
If you delete a combination of the specied port and the WWN of the
HBA from the SPM targets by using the SPM name, the SPM setting
and SPM name under the specied port are deleted. If the same SPM
name is set to another port, only the SPM setting of the specied
port is deleted.
If you delete a combination of the specied port and the WWN of the
HBA from the SPM targets by using the SPM group name, the SPM
setting and the group under the specied port are deleted. If the
same SPM group name is set to another port, only the SPM setting of
the specied port is deleted.
When
specifying ports
and WWNs of
HBAs: Resource
group function
and restrictions
for Server
Priority
Manager
When you use the resource group function, the range of operation is
limited per port of resource group by Server Priority Manager. The
threshold value, the SPM name, and the SPM group name, which are
managed in the entire system, are common among the resource
groups.
Cautions about using Server Priority Manager
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 249
Caution Description
When you perform Server Priority Manager operations using the
resource group function, share the threshold value that the storage
administrator determines among users of resource groups.
Determine rules for SPM names and SPM group names including
port names to avoid redundant names between ports.
When
specifying
WWN or iSCSI
name of LDEVs
and HBAs:
DKCMAIN
microcode
version and
storage models
For microcode 80-04-xx-xx/00 or earlier in VSP G1x00 and VSP F1500
or rmware 83-03-0x-xx/00 or earlier in VSP Gx00 models and VSP
Fx00 models, if SPM information is set or referenced, behavior is not
guaranteed.
The following errors might occur:
■Server performance cannot be controlled according to the
specied upper limit value.
■No detailed error message appears when an error occurs.
■No error message appears if an invalid upper limit value is set.
■The same error as when an invalid WWN is specied occurs. For
details about the errors, see the row below.
Behavior when SPM information is set for or referenced by VSP or
HUS VM models cannot be guaranteed. If SPM information is set or
referenced, the following errors might occur:
■Server performance cannot be controlled according to the
specied upper limit value.
■No detailed error message appears when an error occurs.
■No error message appears if an invalid upper limit value is set.
When
specifying
WWN or iSCSI
name of LDEVs
and HBAs:
Invalid WWNs
Behavior is not guaranteed when an invalid WWN (not in the format
dened by IEEE) is specied.
In VSP G1x00 and VSP F1500, if you specify SPM information for an
invalid WWN, you might not be able to set SPM information with an
iSCSI name specied.
In VSP Gx00 models and VSP Fx00 models with DKCMAIN rmware
83-03-0x or earlier, if you specify SPM information for an invalid
WWN and then update the rmware to 83-03-2x or later, the
following errors might occur:
■Invalid WWNs with SPM information specied are deleted from
the SPM target.
■SPM information is set for the iSCSI name of which SPM
information is not specied.
Cautions about using Server Priority Manager
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 250
Caution Description
When
specifying
WWN or iSCSI
name of LDEVs
and HBAs: I/Os
issued to non-
prioritized
LDEVs
When the number of I/Os issued to a non-prioritized LDEV reaches
the upper limit, I/Os exceeding the upper limit are retained in the
storage system. By this method, host process might be consumed,
and I/O performance of prioritized LDEVs or non-prioritized LDEVs
that have I/Os below the upper limit might be aected. If I/O
performance of other LDEVs becomes lower than expected due to
the host process number limit, review the queue depth settings or
alternate path policy settings of the host.
Cautions when using host groups after registering them in SPM groups (VSP
only)
The following limitations apply when you register host groups in SPM groups (VSP only):
1. You cannot register host groups that contain WWNs for which SPM information is
set in step 1 of Controlling server performance when the host group is not
registered in the SPM group (on page 241) .
2. You cannot register host groups in SPM groups in which WWNs (SPM targets) are
registered in step 3 of Controlling server performance when the host group is not
registered in the SPM group (on page 241) .
You can register host groups described in limitation 1 above in SPM groups that were not
specied in step 3 of Controlling the priority of I/O operations in storage systems on
servers (on page 239) if the WWNs that belong to the host group meet the following
requirements:
■The WWNs are not already registered as SPM targets using another port number by
performing step 1 of Controlling the priority of I/O operations in storage systems on
servers (on page 239) .
■The WWNs belong to SPM groups that were specied in step 3 of Controlling server
performance when the host group is not registered in the SPM group (on page 241) .
After registering a host group in anSPM group, Server Priority Manager sets the SPM
information as follows:
■When the SPM group is associated with the host group, Server Priority Manager sets
the same priority (prioritized or non-prioritized) as the SPM group. Then, for the
prioritized host group Server Priority Manager sets the threshold, or for the non-
prioritized host group Server Priority Manager sets the upper limit of non-prioritized
WWNs.
■When the SPM group is not associated with the host group, Server Priority Manager
sets the priority setting to prioritized without changing the threshold.
For how to register host groups in SPM groups, see Controlling server performance when
the host group is registered in the SPM (VSP only).
Cautions when using host groups after registering them in SPM groups (VSP only)
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 251
Configuring Server Priority Manager by specifying LDEVs and WWNs
or iSCSI names of HBAs
To control the I/O priority for volumes in a storage system on the server, you can
congure Server Priority Manager by specifying an LDEV and a WWN or iSCSI name of a
host bus adapter.
For the combination of a volume (LDEV) and a host (WWN or iSCSI name), specify the I/O
priority (prioritized or non-prioritized). When the priority is non-prioritized, set the upper
limit value to control the server performance. Set the prioritized priority to the host with
higher priority, and the non-prioritized priority to the host with lower priority. By
adjusting the upper limit value to an appropriate value, you can maintain the number of
accesses and the amount of data to be transferred from a prioritized host to a storage
system at a higher level.
Requirements for using Server Priority Manager by specifying the LDEV, the WWN
or iSCSI name of the host bus adapter
Item Range
Number of LDEVs that can be registered
for each storage system
1 to 16,38411
Number of WWNs that can be registered
for each storage system
1 to 2,04822
Number of iSCSI names that can be
registered for each storage system
1 to 2,04822
Number of WWNs that can be registered
for each LDEV
1 to 323
Number of iSCSI names that can be
registered for each LDEV
1 to 323
Notes:
1. When the maximum number of LDEVs for a storage system is less than 16,384,
the maximum number of LDEVs that can be registered is the maximum number
of total LDEVs for a storage system.
2. The sum of the number of WWNs and the number of iSCSI names. This sum
should be a maximum of 2,048 for each storage system.
3. The sum of the number of WWNs and the number of iSCSI names. This sum
should be a maximum of 32 for each LDEV.
Conguring Server Priority Manager by specifying LDEVs and WWNs or iSCSI names of HBAs
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 252
Note:
■When there are 4,096 or more LDEVs with SPM congured, if you congure
SPM in another LDEV, host I/O response in the LDEV is slower than the
existing LDEVs with SPM congured. To improve the host I/O response,
delete the SPM information in the new LDEV with SPM congured, then
delete the existing SPM information to decrease the number of LDEVs with
SPM congured to 4,095 or fewer, and then congure SPM in the new
LDEV again.
Priority to be set by specifying a port and a WWN or iSCSI name of an HBA, and
control of server performance
Priority Server performance
Non-prioritized Controls server performance based on the upper limit. The upper
limit is set for each non-prioritized WWN or non-prioritized iSCSI
name.
The upper limit suppresses the number of accesses from a host bus
adapter to an LDEV, or the amount of data to be transferred.
Monitoring information can be displayed according to the
combination of an LDEV and a WWN or iSCSI name of a host bus
adapter.
Prioritized Does not control server performance of a prioritized WWN or
prioritized iSCSI name.
Monitoring information can be displayed according to the
combination of an LDEV and a WWN or iSCSI name of a host bus
adapter.
Note: Unlike the case of conguring Server Priority Manager by specifying a
port and a WWN of a host bus adapter, the function for enabling or disabling
control of the upper limit automatically according to the trac amount is not
supported.
Conguring Server Priority Manager by specifying LDEVs and WWNs or iSCSI names of HBAs
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 253
Server Priority Manager operations when an LDEV and a WWN or iSCSI name of an
HBA is specied
St
ep
Operation
overview Description Executed command
1 Setting SPM
information for
an LDEV and a
WWN or iSCSI
name
Specify the LDEV number,
and the WWN or iSCSI name
of the host bus adapter to
set the priority (prioritized or
non-prioritized) as the SPM
target.
To set the non-prioritized
option, set the upper limit as
well.
Normally, set the prioritized
option in step 1, and check
the monitoring information
in step 3. And then, if
necessary, change the
priority to non-priority in
step 4, and set the upper
limit.
raidcom modify spm_ldev -
ldev_id <ldev#> {-hba_wwn
<wwn strings> | -
hba_iscsi_name <initiator
iscsi name>} [ -
spm_priority <y/n>] [{-
limit_io | -limit_kb | -
limit_mb} <value> ]
2 Checking SPM
information
Display the setting status of
SPM. raidcom get spm_ldev [-
ldev_id <ldev#> | -
hba_wwn <wwn strings> | -
hba_iscsi_name <initiator
iscsi name> ]
3 Displaying
monitoring
information of
the prioritized or
non-prioritized
WWN
Display monitoring
information. raidcom monitor spm_ldev -
ldev_id <ldev#> {-hba_wwn
<wwn strings> | -
hba_iscsi_name <initiator
iscsi name>}
4 Changing the
upper limit of
the prioritized
and non-
prioritized
WWNs
If necessary, determine the
priority and the upper limit
based on the monitoring
information, and then
change the priority.
When the non-prioritized
option is set, set the upper
limit as well.
raidcom modify spm_ldev -
ldev_id <ldev#> {-
hba_wwn <wwn strings> | -
hba_iscsi_name <initiator
iscsi name>} [-
spm_priority <y/n>] [{-
limit_io | -limit_kb | -
limit_mb} <value>]
Conguring Server Priority Manager by specifying LDEVs and WWNs or iSCSI names of HBAs
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 254
St
ep
Operation
overview Description Executed command
5 Deleting from
the SPM target
Specify the LDEV number
and the WWN or iSCSI name
of the host bus adapter to
delete them from the SPM
target.
raidcom delete spm_ldev -
ldev_id <ldev#> {-hba_wwn
<wwn strings> | -
hba_iscsi_name <initiator iscsi
name>}
Virtual storage machine operations
■Creating host groups in a virtual storage machine (on page 255)
■Adding LDEVs to a virtual storage machine (on page 256)
■Removing the virtual storage machine (on page 256)
Creating host groups in a virtual storage machine
Use the following provisioning operations to create host groups in a virtual storage
machine and to assign virtualized LDEV to LU.
Ste
p
Operation
overview Description Executed command
1 Reserving host
group IDs
Reserve ports and host group
IDs to the resource groups in
the virtual storage machine.
Be sure to execute the
command before creating
host groups.
raidcom add resource
-resource_name <resource
group name>
-port <port#> -<HG#>
2 Creating host
groups
Create host groups by
specifying the reserved port
and host group ID to the
resource group.
raidcom add host_grp -
port <port#> -<HG#>
-host_grp_name <host
group name>
3 Specifying the
host mode and
host mode
options
Specify the host mode to the
created host group. Also,
specify the host mode
options if necessary.
raidcom modify host_grp
-port <port#> [<host
group name>] - host_mode
< host mode> [-
host_mode_opt <host mode
option> … ]
Virtual storage machine operations
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 255
Ste
p
Operation
overview Description Executed command
4 Adding hosts to
the host group
Register hosts to the host
group. raidcom add hba_wwn -
port <port#> [<host
group name>] -hba_wwn
<WWN strings>
Adding LDEVs to a virtual storage machine
Use the following provisioning operations to add LDEVs to a virtual storage machine and
to use LDEVs from hosts.
Ste
p
Operation
overview Description Executed command
1 Delete the virtual
LDEV ID set by
default
Specify an LDEV ID to delete
the virtual LDEV ID set by
default. By default, the virtual
LDEV ID is the same as the
real LDEV ID.
raidcom unmap resource
-ldev_id <ldev#>
-virtual_ldev_id <ldev#>
2 Add the LDEV to
the resource
group
Add the LDEV of which the
virtual LDEV ID was deleted
to the resource group in the
virtual storage machine.
raidcom add resource
-resource_name <resource
group name> -ldev_id
<ldev#>
3 Virtualize LDEVs Set a virtual LDEV ID to the
specied LDEV. Also, specify
the product ID and SSID if
necessary.
raidcom map resource
-ldev_id <ldev#> -
virtual_ldev_id <ldev#>
[-ssid<ssid> -emulation
<emulation type>]
4 Create LU path To create LU path, assign
LDEVs to the host group that
belongs to the resource
group in the virtual storage
machine.
raidcom add lun -port
<port#> [<host group
name>] -ldev_id <ldev#>
[-lun_id<lun#>]
Removing the virtual storage machine
Use the following provisioning operations to remove resources from the virtual storage
machine and to remove the virtual storage machine.
Adding LDEVs to a virtual storage machine
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 256
Ste
p
Operation
overview Description Executed command
1 Remove the LU
path
Remove the LU path from the
LDEV in the virtual storage
machine.
raidcom delete lun -port
<port#> [<host group
name>] {-lun_id <lun#> |
-ldev_id <ldev#> |
-grp_opt <group option>
-device_grp_name <device
group name> [<device
name>]}
2 Remove the
virtual LDEV ID
Remove the virtual LDEV ID
from the LDEV in the virtual
storage machine.
raidcom unmap resource
-ldev_id <ldev#>
-virtual_ldev_id <ldev#>
3 Remove the
LDEV from the
resource group
Remove the LDEV from the
resource group in the virtual
storage machine
raidcom delete resource
-resource_name <resource
group name> -ldev_id
<ldev#>
4 Invalidate the
LDEV
virtualization
Specify the virtual LDEV ID
that is the same as the real
LDEV ID in order to invalidate
the LDEV virtualization.
raidcom map resource
-ldev_id <ldev#>
-virtual_ldev_id <ldev#>
5 Delete the host
group
Delete the host group in the
virtual storage machine. raidcom delete host_grp
-port <port#> [<host
group name>]
6 Remove the host
group ID from
the resource
group
Remove the host group ID
that belongs to the resource
group in the virtual storage
machine
raidcom delete resource
-resource_name <resource
group name> -port <port#>
-<HG#>
7 Remove the
resource from
the resource
group
Remove the resource from
the resource group in the
virtual storage machine.
raidcom delete resource
-resource_name <resource
group name> [-ldev_id
<ldev#> | -port <port#>
[<host group name>] |
-parity_grp <gno-sgno> |
-external_grp_id <gno-
sgno> | -grp_opt <group
option> -device_grp_name
Removing the virtual storage machine
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 257
Ste
p
Operation
overview Description Executed command
<device group name>
[<device name>]]
8 Remove the
virtual storage
machine
Delete all resource groups in
the virtual storage machine
in order to remove the virtual
storage machine.
raidcom delete resource
-resource_name <resource
group name>
Removing the virtual storage machine
Chapter 5: Provisioning operations with CCI
Command Control Interface User and Reference Guide 258
Chapter 6: Data replication operations with CCI
This chapter describes data replication operations with CCI.
About data replication operations
The data replication features of the RAID storage systems include:
■Local replication:
●ShadowImage
●ShadowImage for Mainframe
●Thin Image
●Copy-on-Write Snapshot
■Remote replication:
●TrueCopy
●TrueCopy for Mainframe
●TrueCopy Async
●Universal Replicator
●Universal Replicator for Mainframe
●global-active device
■Mainframe replication:
●Compatible XRC
●Compatible FlashCopy® V2
●Business Continuity Manager
For detailed information about any of these features, see the applicable user guide (for
example, Hitachi ShadowImage® User Guide).
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 259
Features of paired volumes
Paired logical volumes are often handled independently by servers. When CCI is used,
the paired volumes can be managed by the replication functions (for example,
ShadowImage, TrueCopy, Universal Replicator, global-active device) as combined or
separated pairs. The replication functions regard the two volumes being combined or
separated as a uniquely paired logical volume used by the servers. Paired volumes can
also be handled as groups, grouping them by units of server software or units of
databases and their attributes.
For detailed information about volume pairs (for example, maximum number of pairs
per storage system, maximum P-VOL size), see the user guide for your storage system
and copy function (for example, Hitachi ShadowImage® User Guide).
See the following gure depicting the concept of paired volume.
Addressing paired logical volumes: The correspondence of paired logical volumes to
their physical volumes is dened by describing the paired logical volume names and
group names in the conguration denition les of each server. It is possible to dene a
server for the paired logical volumes in units of group name. Each paired logical volume
must belong to a group in order to determine the corresponding server.
Specication of volumes by commands: Volume names to be used by the CCI commands
must be referenced via the paired logical volume names or the group names.
Features of paired volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 260
Using CCI with ShadowImage and TrueCopy
CCI allows you to perform ShadowImage and TrueCopy operations by issuing
ShadowImage and TrueCopy commands from the UNIX/PC server host to the RAID
storage system. ShadowImage and TrueCopy operations are nondisruptive and allow the
primary volume of each volume pair to remain online to all hosts for both read and write
operations. Once established, ShadowImage and TrueCopy operations continue
unattended to provide continuous data backup.
There are specic requirements for using ShadowImage and TrueCopy in high-availability
(HA) congurations. UNIX/PC servers in HA congurations normally support disk
duplication functions to enhance disk reliability (for example, mirroring provided by the
LVM or device driver, RAID5 or an equivalent function provided by the LVM). UNIX/PC
servers also feature hot standby and mutual hot standby functions in case of failures on
the server side. However, mutual hot standby for disaster recovery has not yet been
achieved since it requires the remote mirroring function.
ShadowImage provides the mirroring function within the storage system. For detailed
information about ShadowImage operations, please see the Hitachi ShadowImage® User
Guide for your storage system.
TrueCopy provides remote mirroring functionality, linkage functionality with failover
switching, and remote backup operations among servers, all of which are required by
UNIX/PC servers in HA congurations for disaster recovery. For detailed information
about TrueCopy operations, please see the Hitachi TrueCopy® User Guide for your storage
system.
Using CCI with Thin Image
CCI allows you to perform Hitachi Thin Image operations by issuing raidcom commands
(for example, raidcom add snapshot) to the RAID storage system. Hitachi Thin Image
stores snapshots in storage system. Creating a Thin Image pair changes the status to
“PAIR” and stores snapshot data as a copy of the data on the Thin Image P-VOL. A Thin
Image pair consists of a P-VOL, one or more S-VOLs that are virtual volumes (V-VOLs),
and one or more pool-VOLs that are LDEVs. P-VOL dierential data is stored as snapshot
data in the pool-VOLs. If your storage system experiences a data storage failure, you can
restore the data using the snapshot data in the pool. Splitting a Thin Image pair saves a
snapshot and stops the copying of replaced data in the pool.
Consistency groups and snapshot groups are groups of pairs for which you can
simultaneously perform pair tasks on all pairs within the group. You can use CCI raidcom
commands to create consistency groups and snapshot groups and to split pairs to store
the snapshot data for the groups.
■A consistency group can include HTI, SI, and SIz pairs. Splitting the pairs using the
group assures data consistency at the time the storage system receives the request.
■A snapshot group is a group of only Thin Image pairs. Use consistency or snapshot
groups to perform Thin Image tasks on all of the pairs within the group. You dene
Thin Image pairs to a snapshot group when you create the pairs.
Using CCI with ShadowImage and TrueCopy
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 261
Note: When you use the CCI to dene multiple Thin Image pairs in a
consistency group, you can only specify one consistency group for a group
dened in the CCI conguration denition le.
The conguration denition le for CCI is a group that is not a consistency
group.
Creating a new pair and dening the pairs in a consistency group for a group
you dened using the CCI conguration denition le and the pair is already
dened in a consistency group denes the pair in the same consistency
group, even if you try to create a new pair and assign it to a dierent
consistency group.
For details about Hitachi Thin Image, see the Hitachi Thin Image User Guide for your
storage system.
Using CCI with global-active device
The CCI software is installed on the host servers and used for global-active device
operations. The CCI command devices and CCI conguration denition les are required
for global-active device operations. You can execute CCI commands for global-active
device using the in-band or out-of-band method of CCI command execution.
For details about global-active device, see the Global-Active Device User Guide. For details
about the CCI command options and display results for global-active device operations
(for example, PHY_LDEV, VIR_LDEV), see the Command Control Interface Command
Reference.
Note: If you set the S-VOL Disable attribute of Data Retention Utility to a GAD
secondary volume, GAD pair operations from CCI are restricted. Release the
S-VOL Disable attribute of the GAD secondary volume, and then perform the
GAD pair operations.
ShadowImage operations
The ShadowImage commands also support the functionality that links the system
operation for the purpose of volume backup among UNIX servers managed by the
operating system. For detailed information about the operational requirements and
specications for ShadowImage, see the Hitachi ShadowImage® User Guide for your
storage system.
Following is a list of sample ShadowImage functions that can be executed using CCI
commands:
■Pair creation: Creates a new volume pair. Volume pairs can be created in units of
volumes or groups.
■Pair splitting: Splits a volume pair and allows read and write access to the secondary
volume.
Using CCI with global-active device
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 262
■Pair resynchronization: Resynchronizes a split volume pair based on the primary
volume. The primary volume remains accessible during resynchronization.
■Pair resynchronization with restore option: Resynchronizes a split pair based on
the secondary volume (reverse resync). The primary volume is not accessible during
resync with restore option.
■Event waiting: Used for waiting for the completion of a volume pair creation or
resynchronization to check the pair status.
■Pair status display and conguration conrmation: Displays the pair status and
conguration of the volume pairs; this can also be used for checking the completion
of a pair creation or pair resynchronization. The gure given below illustrates a
ShadowImage system conguration.
ShadowImage duplicated mirroring
Duplicated mirroring of a single primary volume is possible when the ShadowImage
feature is used. Duplicated mirror volumes can be specied up tp the maximum quantity
3. The duplicated mirror volumes of the P-VOL are expressed as virtual volumes using
the mirror descriptors (MU#0-2) in the conguration diagram as shown below.
ShadowImage duplicated mirroring
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 263
ShadowImage cascading pairs
ShadowImage provides a cascading function for the ShadowImage S-VOL. Cascading
mirror volumes can be specied up to the maximum quantity 2. The cascading mirrors of
the S-VOL are expressed as virtual volumes using the mirror descriptors (MU#1-2) in the
conguration diagram as shown below. The MU#0 of a mirror descriptor is used for
connection of the S-VOL.
ShadowImage cascading pairs
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 264
Restrictions for ShadowImage cascading volumes
Pair Creation:
Pair creation of S-VOL (oradb1) can only be performed after the pair creation of S/P-VOL
(oradb). If you create the oradb1 pair rst without creating the oradb, the subsequent
oradb creation will be rejected with EX_CMDRJE or EX_CMDIOE.
Pair splitting:
Pair splitting of S-VOL (oradb1) can only be performed after the S/P-VOL (oradb) is in a
SMPL or PSUS state, since ShadowImage copies are asynchronous. If pair splitting of the
S-VOL (oradb1) is attempted while the S/P-VOL (oradb) is in a COPY or PAIR state, the
pairsplit command is rejected with EX_CMDRJE or EX_CMDIOE.
Restrictions for ShadowImage cascading volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 265
Pair restore:
Pair restore (resync from S-VOL (oradb1) to S/P-VOL) can only be performed when the S-
VOL (oradb) and the P-VOL (oradb2) on the S/P-VOL are in the SMPL and PSUS states. If
the pair restore of S-VOL (oradb1) is performed while either the S-VOL (oradb) or P-VOL
(oradb2) on the S/P-VOL are in a COPY, PAIR or PSUS state, the pairresync -restore
command is rejected with EX_CMDRJE or EX_CMDIOE.
Restriction for TrueCopy/ShadowImage cascading volumes
Pair restore (resynchronization from S-VOL (oradb1) to S/P-VOL) can only be performed
when the TrueCopy S-VOL (oradb) and the P-VOL (oradb2) on the S/P-VOL are in the
SMPL or PSUS(SSUS) state. If pairresync of S-VOL (oradb1) is performed when the S/P-
VOL (oradb or oradb2) is in any other state, the pairresync -restore option
command is rejected with EX_CMDRJE or EX_CMDIOE.
TrueCopy operations
CCI TrueCopy commands operate in conjunction with the software on the UNIX/PC
servers and the TrueCopy functions of the RAID storage systems. The CCI software
provides failover and other functions such as backup commands to allow mutual hot
standby in cooperation with the failover product on the UNIX/PC server (for example,
MC/ServiceGuard, FirstWatch, HACMP).
Restriction for TrueCopy/ShadowImage cascading volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 266
Note: For proper maintenance of TrueCopy operations, it is important to
determine if there are any faults in paired volumes, recover the volumes from
the failures as soon as possible, and continue operation in the original
system.
Note: For information about the operational requirements and specications
for TrueCopy, please see the Hitachi TrueCopy® User Guide for your storage
system.
TrueCopy takeover commands
The gure given below illustrates a high-availability (HA) environment. When a server
software error or a node error is detected, the HA failover software causes the cluster
manager (CM) to monitor server programs and causes the CM of the standby node to
automatically activate the HA control script of the corresponding server program. The HA
control script usually contains database recovery procedures, server program activation
procedures, and other related recovery procedures. The TrueCopyCCI takeover
commands are also activated by the HA control script.
Legend
■CM (Cluster Manager): Demon process that keeps the consistency of the cluster by
monitoring the node and server program in the cluster.
■Script: Shell script that automatically performs takeover process when CM detects the
server failure.
TrueCopy takeover commands
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 267
In an HA environment, a package is a group of applications that are scripted to run on
the secondary host in the event of a primary host failure. When using the HA software
(for example, MC/ServiceGuard), the package can be transferred to the standby node as
an operation executed by the system administrator (see the gure given below for
package transfer on high availability (HA) software).
Note: If the operation is performed when CCI and TrueCopy are being used,
the volume is switched from primary to secondary as if an error had
occurred, even though data consistency is assured. When restoral of the
original node occurs along with its original package (group of applications), it
is necessary to copy the data on the secondary volume onto the primary
volume; this operation can take as much time as the initial copy operation for
the pair. In actual operation, no package can be transferred when TrueCopy is
being used. The secondary package is switched to the primary package, and
vice versa, when the primary volume is switched to the secondary volume.
Therefore, the primary and secondary TrueCopy volumes should be switched
depending on the package state.
The swap option of the takeover command allows swapping of the primary and
secondary volume designations, so if the primary and secondary volume are switched
due to a server error or package transfer, pair operation can be continued using the
reversed volumes. When control is handed back over to the original node, swapping the
volume designations again eliminates the need of copying them. In addition, the
takeover command has the option to allow the secondary volume to be logically
separated (for the purpose of recovery from a disaster at the original operating site). The
takeover command has four functions designed for HA software operation:
Takeoverswitch, swap-takeover, SVOL-takeover, and PVOL-takeover. This command is not
available for ShadowImage.
TrueCopy takeover commands
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 268
Takeover-switch function
The control scripts activated by HA software are used by all nodes of a cluster in exactly
the same manner so they have no discrimination between primary and secondary pair
volumes (they just know the near and far disk in a pair). Thus, the takeover command,
when activated by a control script, must check the combination of attributes of volumes
possessed by the local and remote nodes and determine the proper takeover action. The
table below shows the takeover actions, like Near/Local and Far/Remote Volume
Attributes and Takeover ActionsNear/Local and Far/Remote Volume Attributes and
Takeover Actions.
Local node (Takeover node) Remote node
Takeover action
Volume
attribute Fence and status
Volume
attribute P-VOL status
SMPL - SMPL - Reject
P-VOL - Nop-takeover1
S-VOL - Unconformable
Unknown - Reject
P-VOL
(primary)
Fence == Data or
Status && pair
status == PSUE or
PDUB or MINAP ==
0
SMPL - Reject
P-VOL - Unconformable
S-VOL - PVOL-Takeover2
Unknown - PVOL-Takeover2
Others SMPL - Reject
P-VOL - Unconformable
S-VOL - Nop-takeover1
Unknown - Nop-takeover1
S-VOL
(secondar
y)
Status == SSWS
(After
SVOL_SSUStakeove
r)
- - Nop-takeover1
Other than SSWS SMPL - Unconformable
P-VOL PAIR or PFUL Swap-takeover2
Others SVOL-takeover2
S-VOL - Unconformable
Unknown - SVOL-takeover2
Notes:
Takeover-switch function
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 269
Local node (Takeover node) Remote node
Takeover action
Volume
attribute Fence and status
Volume
attribute P-VOL status
1. No action needed to allow local writes.
2. Required to allow local writes.
Nop-takeover
No operation is done to allow local writes, though the takeover command is
accepted. Personality swaps must be accomplished in another way.
Unconformable
A pair of volumes are not conformable to each other as a pair (that is, one P-VOL,
one S-VOL). The takeover command execution terminates abnormally.
Reject
The takeover command is rejected, and the operation terminates abnormally.
Unknown
The attribute of the remote node is unknown and cannot be identied. This means
that the remote node system has gone down or cannot communicate over the
LAN.
SSWS
Since the SSWS state is referring to a Suspend for Swapping with S-VOL Side only,
the SSWS state is displayed as SSUS (SVOL_PSUS) by all commands except the -fc
option of the pairdisplay command.
Swap-takeover function
The P-VOL status at the remote node is PAIR or PFUL (TrueCopy Async and over high-
water mark) and the S-VOL has mirroring consistency. In such a state, it is possible to
swap the primary and secondary volume designations to continue operation. The
takeover command internally executes the operating commands (explained later) step by
step, to swap the primary and secondary volume designations. Swapping can be
specied at the granularity of volume pair, consistency group, or volume group.
The swap-takeover function does not use Simplex and No Copy mode for Swapping in
order to guarantee mirror consistence more surely, and it is included as a function of
SVOL-takeover.
1. As the preliminary step of swap-takeover, the command orders a Suspend for
Swapping (SSWS) for the local volume (S-VOL). If this step fails, the swap-takeover
function is disabled and it will be returned at an error.
Swap-takeover function
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 270
2. The command orders a Resync for Swapping for switch to the primary volume that
the local volume (S-VOL) is swapped as the NEW_PVOL and re-synchronizes the
NEW_SVOL based on the NEW_PVOL. As for the number of simultaneous copy
tracks, if the remote host is known then the command will use the value of P-VOL
specied at paircreate time, else (remote host is Unknown) the command will use a
default of 3 as the number of tracks for Resync for Swapping.
If this step fails, the swap-takeover function will be returned at SVOL-SSUS-takeover,
and the local volume (S-VOL) is maintained in SSUS(PSUS) state which permits
WRITE and maintaining delta data (BITMAP) for the secondary volume. Also this
special state is displayed as SSWS state using -fc option of pairdisplay command.
TrueCopy Async/Universal Replicator specic behavior for swap-takeover:
The S-VOL side CCI will issue a Suspend for Swapping to the S-VOL side storage system.
Non-transmitted data which remains in the FIFO queue (sidele) of the primary volume
will be copied to the S-VOL side and a Resync for Swapping operation will be performed
(after the copy process). The Swap operation is required to copy Nontransmitted P-VOL
data within a given timeout value (specied by the -t <timeout> option).
SVOL-takeover function
The function makes it so the takeover node alone can use the secondary volume (except
in COPY state) in SSUS(PSUS) state (i.e., reading and writing are enabled), on the
assumption that the remote node (possessing the primary volume) cannot be used.
The data consistency of the secondary volume is judged by its status and fence level. If
this check proves that data is not consistent, the SVOL-takeover function fails. If this
check proves that data is consistent then this function will try to switch the S-VOL to a
primary volume using a Resync for Swapping, and if it succeeds then this function will
return Swap-takeover, else this function will return SVOL-SSUS-takeover as the return
value of horctakeover command. In case of a Host failure, this function will be returned
as Swap-takeover. In case of a FICON or P-VOL site failure, this function will be returned
as SVOL-SSUS-takeover. A SVOL-takeover can be specied by the granularity of a paired
logical volume, consistency group, or volume group. If a SVOL-takeover is specied for a
volume group, a data consistency check is executed for all volumes in the group.
Inconsistent volumes are picked out and displayed in the execution log le as shown
below:
Example
Group Pair vol Port targ# lun# LDEV#...Volstat Status Fence To be...
oradb1 ora001 CL1-A 1 5 145...S-VOL PAIR NEVER Analyzed
oradb1 ora002 CL1-A 1 6 146...S-VOL PSUS STATUS Suspected
Even so, the SVOL-takeover function enables the secondary volume to be used (i.e.,
reading and writing are enabled) since it assumes that the remote node (possessing the
primary volume) cannot be used.
SVOL-takeover function
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 271
TrueCopy Async/Universal Replicator specic behavior for SVOL-takeover:
The S-VOL side CCI will issue a Suspend for Swapping to the S-VOL side storage system.
Non-transmitted P-VOL data will be copied to the S-VOL and a Resync for Swapping
operation will be performed (after the copy process).
In case of a Host failure, this data synchronize operation will be accomplished and the
SVOL-takeover function will return as Swaptakeover after attempting a Resync for
Swapping.
In case of a FICON or P-VOL site failure, this data synchronization operation might fail.
Even so, the SVOL-takeover function will do Suspend for Swapping, and enable the
secondary volume to be used.
As a result, this function will return as SVOL-SSUS-takeover. Through this behavior, you
will be able to judge that non-transmitted data of the primary volume was not
transmitted completely when a SVOL-takeover returns SVOL-SSUS-takeover.
Caution: The SVOL-takeover operation is required to copy Nontransmitted P-
VOL data within a given timeout value (specied by the -t <timeout> option).
If the timeout occurs (before the SVOL-takeover operation has completed all
S-VOL changes to a SSWS state), the horctakeover command will fail with
EX_EWSTOT. If the horctakeover has failed due to a timeout then you need to
try for a recovery as shown below.
■Wait until the S-VOL state becomes SSWS' via pairdisplay -g <group> -l -fc
command, and try to the start-up again for the HA Control Script.
■Make an attempt to re-synchronize the original P-VOL based on the S-VOL
using pairresync -g <group> -swaps -c <size> for a Fast Failback operation.
If this operation fails with [EX_CMDRJE] or [EX_CMDIOE], this is due to a
FICON link down or site failure. After a recovery from the failure, perform
the operation again.
Therefore this timeout value should be a greater than (or equal) to the start-
up timeout value for the MC & CC Control Script.
PVOL-takeover function
A PVOL-takeover relinquishes the pair state for a volume or group in order to make the
P-VOL writable following some type of error (for example, link down with DATA fence).
This function makes it so the takeover node alone can use the primary volume (that is,
reading and writing are enabled), on the assumption that the remote node (possessing
the secondary volume) cannot be used.
The PVOL-takeover function has two functions: PVOL-PSUE-takeover, and PVOL-SMPL-
takeover. A PVOL-PSUE-takeover forces the primary volume to suspend (PSUE, PSUS)
state which permits WRITEs to all primary volumes of the group (even if the fence level is
data). Therefore PSUE and/or PSUS are intermingled in the volume group through the
action of this PVOL-PSUE-takeover. This intermingled pair status creates PSUE as the
group status, therefore the pairvolchk command results give precedence to PSUE (PDUB)
status over PSUS for the group.
PVOL-takeover function
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 272
This special state returns back to its original state by issuing the pairresync command. A
PVOL-SMPL-takeover forces the primary volume to simplex (SMPL) state so the pair is
destroyed. At rst, PVOL-takeover executes PVOL-PSUE-takeover. If PVOL-PSUE-takeover
fails, it then executes PVOL-SMPL-takeover. PVOL-takeover can be specied per paired
logical volume or per volume group.
TrueCopy Async/Universal Replicator specic behavior for PVOL-takeover:
PVOL-takeover will not be executed. It will become a Nop-Takeover, since the fence level
will be Async which is equal to Never so it is not needed to allow P-VOL writes.
TrueCopy remote commands
The CCI TrueCopy remote commands assist the system operation with volume backups
among UNIX servers and their operating system management functions. The TrueCopy
remote pair commands are also used to copy volumes in server failover congurations
and to restore the volumes to their original state after a server failover has been
recovered.
■Pair creation command: Creates a new volume pair. Volume pairs can be created in
units of volume or group.
■Pair splitting command: Splits a volume pair and allows read and write access to the
secondary volume.
■Pair resynchronization command: Resynchronizes a split volume pair based on the
primary volume. The primary volume remains accessible during resynchronization.
●Swaps(p) option (TrueCopy only). Swaps volume from the S-VOL(P-VOL) to the P-
VOL(S-VOL) when the S-VOL(P-VOL) is in the suspended state and resynchronizes
the NEW_SVOL based on the NEW_PVOL. At the result of this operation, the
volume attributes of the host of reference (local host) are used as the attributes for
the NEW_PVOL(SVOL).
■Event waiting command: Used to wait for the completion of volume pair creation or
resynchronization and to check the pair status.
■Pair status display and conguration conrmation command: Displays the pair
status and conguration of the volume pairs and is used for checking the completion
of pair creation or pair resynchronization.
The following gure illustrates a TrueCopy remote system conguration.
TrueCopy remote commands
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 273
Legend
■HORCM: The manager is a demon process, executes multiple commands, charges to a
storage system through itself. Among the managers are connected by UDP, remotely
execute a command among the servers mutually.
■Command: A command provisioned by CCI.
TrueCopy local commands
The CCITrueCopy local commands assist the system operation with volume backups
among UNIX servers and their operating system management functions. The TrueCopy
local commands perform the same functions as the remote commands but within the
same RAID storage system instead of between two RAID storage systems.
The following gure illustrates a TrueCopy local system conguration.
TrueCopy local commands
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 274
TrueCopy, ShadowImage, and Universal Replicator
operations
TrueCopy/ShadowImage volumes
TrueCopy commands allow you to create volume pairs consisting of one primary volume
(P-VOL) and one secondary volume (S-VOL). The TrueCopy P-VOL and S-VOL can be in
dierent storage systems. TrueCopy provides synchronous and asynchronous copy
modes. TrueCopy Async can only be used between separate storage systems (not within
one storage system). For details on TrueCopy specications, volumes and operations,
please see the Hitachi TrueCopy® User Guide for your storage system.
ShadowImage commands allow you to create volume pairs consisting of one P-VOL and
up to nine S-VOLs using the ShadowImage cascade function. ShadowImage pairs are
contained within the same storage system and are maintained using asynchronous
update copy operations. For details on ShadowImage specications volumes and
operations, please see the Hitachi ShadowImage® User Guide for your storage system.
Each volume pair that you want to create must be registered in the CCI conguration le.
ShadowImage volume pairs must include a MU (mirrored unit) number assigned to the
S-VOL. The MU number indicates that the pair is a ShadowImage pair and not a
TrueCopy pair. Once the correspondence between the paired logical volumes has been
dened in the HORCM_DEV section of the conguration le, you can use the
conguration le to group the paired volumes into volume groups that can be managed
by the host operating system's LVM (logical volume manager).
TrueCopy, ShadowImage, and Universal Replicator operations
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 275
The host's LVM allows you to manage the TrueCopy/ShadowImage volumes as individual
volumes or by volume group. TrueCopy/ShadowImage commands can specify individual
logical volumes or group names. For LUSE volumes, you must enter commands for each
volume (LDEV) within the expanded LU. If you dene volume groups and you want to
issue commands to those volume groups, you must register the volume groups in the
conguration le. For further information about the server LVM, see the user
documentation for your corresponding operating system.
TrueCopy/ShadowImage/Universal Replicator pair status
Each TrueCopy pair consists of one P-VOL and one S-VOL, and each ShadowImage pair
consists of one P-VOL and up to nine S-VOLs when the cascade function is used. The P-
VOL controls the pair status for the primary and secondary volumes. The major pair
statuses are SMPL, PAIR, PSUS/PSUE, and COPY/RCPY. Read and write requests from the
host are accepted or rejected depending on the pair status of the volume.
The pair status can change when a CCI command is executed. The validity of the
specied operation is checked according to the status of the volume (primary volume).
See the tables below for the relationship between pair status and TrueCopy/Universal
Replicator command acceptance, pair status and ShadowImage command acceptance
and pair status and Copy-on-Write Snapshot command acceptance.
For details on pair status of TrueCopy for Mainframe, ShadowImage for Mainframe, and
Universal Replicator for Mainframe, see Pair operations with mainframe volumes.
TrueCopy and ShadowImage pair status
Stat
us TrueCopy Pair Status ShadowImage Pair Status Primary
Seconda
ry
SMP
L
Unpaired volume Unpaired volume R/W
enabled
R/W
enabled
PAIR Paired volume. Initial copy
is complete. Updates are
processed synchronously
or asynchronously.
Paired volume. Initial copy
is complete. Updates are
processed asynchronously.
R/W
enabled
R
enabled
COP
Y
In paired state, but initial
copy, pairsplit, or resync
operation is not complete.
Includes COPY(PD),
COPY(SP), and COPY(RS)
status.
In paired state, but initial
copy, pairsplit, or resync
operation is not complete.
Includes COPY(PD),
COPY(SP), and COPY(RS)
status.
R/W
enabled
R
enabled
RCPY Not used for TrueCopy In paired state, but reverse
resync operation is not
complete. Includes
COPY(RS-R) status.
R
enabled
R
enabled
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 276
Stat
us TrueCopy Pair Status ShadowImage Pair Status Primary
Seconda
ry
PSU
S
(split
)
SSUS
(split
)
In paired state, but
updates to the S-VOL data
are suspended due to
user-requested pairsplit.
The RAID storage system
keeps track of P-VOL and S-
VOL updates while the pair
is split.
In paired state, but
updates to the S-VOL data
are suspended due to
user-requested pairsplit.
The RAID storage system
keeps track of P-VOL and S-
VOL updates while the pair
is split.
R/W
enabled
R/W
enabled
when
using
write
enable
pairsplit
option
PSU
E
(erro
r) or
PFUS
In paired state, but
updates to the S-VOL data
are suspended due to an
error condition. (PSUE is
PSUS due to internal error.
PFUS is PSUS due to
sidele full.)
In paired state, but
updates to the S-VOL
volume data are
suspended due to an error
condition. When a PSUE
pair is resynchronized, the
RAID storage system
copies the entire P-VOL to
the S-VOL (same as initial
copy).
R/W
enabled
if no
error
occurs in
the
primary
volume
R
enabled
PDU
B
Used only for TrueCopy
LUSE pairs. In paired state,
but updates to one or
more LDEVs within the
LUSE pair are suspended
due to an error condition.
Not used for ShadowImage R/W
enabled
if no
error
occurs in
the
primary
volume
R
enabled
Universal Replicator pair status
Stat
us Universal Replicator Pair Status Primary Secondary
SMP
L
Unpaired volume R/W enabled R/W enabled
PAIR The pair is synchronized. Updates to the P-
VOL are duplicated on the S-VOL.
R/W enabled R enabled
COP
Y
In paired state, but initial copy, pairsplit, or
resync operation is not complete. Includes
COPY(PD), COPY(SP), and COPY(RS) status.
R/W enabled R enabled
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 277
Stat
us Universal Replicator Pair Status Primary Secondary
PSUS
(split
)
SSUS
(split
)
The user has split the pair or released the
pair; the pair is no longer synchronized.
■The primary and secondary systems keep
track of journal data discarded during the
pairsplit operation.
■When the operation is performed at the
primary system, the status of both the P-
VOL and S-VOL changes to PSUS.
■When the operation is performed at the
secondary system, the status of the S-VOL
changes to PSUS; the primary system
detects this (if path status is normal) and
changes P-VOL status to PSUS.
■When a pair is released from the secondary
system, the secondary system changes the
status of the S-VOL to SMPL. The primary
system detects this (if path status is normal
and changes P-VOL status to PSUS. (The
pair must be released from the primary
system to change P-VOL status to SMPL.)
R/W enabled R/W enabled
when using
write enable
pairsplit
option
PSUE The pair is suspended due to an error; the pair
is not synchronized.
■The primary and secondary systems keep
track of any journal data that are discarded
during the suspension operation.
■The primary system keeps track of P-VOL
tracks that are updated while the pair is
suspended.
■When a UR suspension condition is
detected, the primary system changes P-
VOL and S-VOL status to PSUE. If the
secondary system detects the condition, it
changes the S-VOL status to PSUE; the
primary system detects this and changes P-
VOL status to PSUS.
R/W enabled if
no error
occurs in the
primary
volume
R enabled
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 278
Stat
us Universal Replicator Pair Status Primary Secondary
PFUS If the Data Overow Watch period is
exceeded, pair status changes from PFUL to
PFUS, and the pair is suspended.
■The PFUS status is displayed by CCI and
Storage Navigator as PSUS.
■If a virtual volume of Dynamic Provisioning
(DP-VOL) is used as a UR S-VOL, and the
capacity of a pool-VOL is nearly full, UR
status becomes PFUS and the pair is
suspended.
R/W enabled Read Only,
unless write
option is
enabled.
SSW
S
After Takeover, SSWS is the status of the S-
VOL. With this status, data can be written to
the S-VOL.
■SSWS is displayed by CCI, from which the
horctakover command is issued.
■Storage Navigator displays this status as
PSUS or PSUE.
R enabled R/W enabled
PFUL If data in the journal volume exceeds 80%,
pair status changes to PFUL. The write data
that inows then is monitored during the Data
Overow Watch.
PFUL status is displayed by CCI. Storage
Navigator displays this status as PAIR.
R/W enabled R enabled
Pair status versus TrueCopy/Universal Replicator commands
-
TrueCopy/Universal Replicator command
paircreate pairsplit
pairresyn
c
#
Statu
s Copy Nocopy
-r or -rw
option -P option -S option Resync
1 SMPL Accepted
2
Accepted
3
Rejected Rejected Acceptabl
e
Rejected
2 COPY Acceptabl
e
Acceptabl
e
Accepted 4 Rejected Accepted
1
Acceptabl
e
3 PAIR Acceptabl
e
Acceptabl
e
Accepted 4 Accepted
4
Accepted
1
Acceptabl
e
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 279
-
TrueCopy/Universal Replicator command
paircreate pairsplit
pairresyn
c
#
Statu
s Copy Nocopy
-r or -rw
option -P option -S option Resync
4 PSUS Rejected Rejected Acceptable Acceptabl
e
Accepted
1
Accepted
2*
5 PSUE Rejected Rejected Acceptable Acceptabl
e
Accepted
1
Accepted
2*
6 PDUB Rejected Rejected Rejected Rejected Accepted
1
Accepted
2*
Legend:
Accepted = Accepted and executed. When the operation terminates normally, the
status changes to the indicated number.
Acceptable = Accepted but no operation is executed.
Rejected = Rejected and operation terminates abnormally.
Pairsplit of a TrueCopy Async volume is returned after verication of state transition
that waits until delta data is synchronized from P-VOL to S-VOL.
Note: In the case of the SSWS status after SVOL-SSUS-takeover execution, the
pairresync command (from P-VOL to S-VOL) is rejected because the delta
data for S-VOL becomes dominant, and its status is expected to be using the
-swaps(p) option of pairresync. If the pairresync command (from P-
VOL to S-VOL) is rejected, conrm this special status using the -fc option of
the pairdisplay command.
Pair status versus ShadowImage commands
The following table shows the relation of command acceptances for paired status and
ShadowImage.
-
ShadowImage command
paircreate pairsplit pairresync
Pair
Status No -split -split -E option -C option -S option Resync
1 SMPL Accepted 2 Accepted
2 to 4
Rejected Rejected Acceptable Rejected
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 280
-
ShadowImage command
paircreate pairsplit pairresync
Pair
Status No -split -split -E option -C option -S option Resync
2 COPY
RCPY
Acceptable Accepted
[1] 2 to 4
Accepted 5 Accepted
[1] 2 to 4
Accepted 1 Acceptable
3 PAIR Acceptable Accepted
[2] 2 to 4
Accepted 5 Accepted
[2] 2 to 4
Accepted 1 Acceptable
4 PSUS Rejected Acceptabl
e
Accepted 5 Acceptabl
e
Accepted 1 Accepted 2
5 PSUE Rejected Acceptabl
e
Acceptable Acceptabl
e
Accepted 1 Accepted 2
Legend:
Accepted = Accepted and executed. When the operation terminates normally, the
status changes to the indicated number.
Acceptable = Accepted but no operation is executed.
Rejected = Rejected and operation terminates abnormally.
In the following descriptions, when the pair statuses of P-VOL and S-VOL are dierent,
PVOL_ or SVOL_ are applied to show which volume is indicated.
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 281
Note: If the P-VOL does not have Write in the PAIR state, then data identical
with an S-VOL is guaranteed. Therefore, when using the S-VOL with the SMPL
state, after stopping Write to the P-VOL, generate a paired volume, and then
split the paired volume after conrming that the paired volume has the PAIR
status. In the PSUE state, ShadowImage does not manage dierential data at
the P-VOL or S-VOL. Therefore, pairresync issued to a pair in the PSUE state
is all copy performance, but the copy progress rate returned by the -fc
option of the pairdisplay command indicates "0%".
[1]: The (2 to 4) state change is eective for only the COPY state that is
changed without specication of -split for paircreate command.
[2]: The (2 to 4) state change appears as P-VOL_PSUS & S-VOL_COPY (see
example below), and reading and writing are enabled for S-VOL in SVOL_COPY
state.
# pairsplit -g oradb
# pairdisplay -g oradb -fc
Group PairVol(L/R) (Port#,TID,LU-M), Seq#, LDEV#.P/S, Status, % , P-
LDEV# M
oradb oradev3(L) (CL2-N , 3, 4-0) 8071 28..P-VOL PSUS, 100 29
W
oradb oradev3(R) (CL2-N , 3, 5-0) 8071 29..S-VOL COPY, 97 28
-
PVOL_PSUS & SVOL_COPY is the non-reected PSUS state that data is still being copied
from the P-VOL to the S-VOL, and this state has the following specic behavior.
■If you attempt to read non-reected data on S-VOL in PVOL_PSUS & SVOL_COPY state,
then ShadowImage copies non-reected data from P-VOL to S-VOL, and returns the
correct data after copied. This will bring the performance degradation (1/6 to 1/15
with IOPS) to read on the S-VOL.
■If you attempt to write non-reected data on S-VOL in PVOL_PSUS & SVOL_COPY
state, then ShadowImage copies non-reected data from P-VOL to S-VOL, and writing
data is managed as delta data for S-VOL after copied. This will bring the performance
degradation(1/6 to 1/8 with IOPS) to write on the S-VOL.
■If you attempt to write to the data on P-VOL that does not still reected the data to S-
VOL, then ShadowImage copies non-reected data from P-VOL to S-VOL, and writing
data is managed as delta data for P-VOL. This will bring the performance
degradation(1/6 to 1/8 with IOPS) to write on the P-VOL.
■The state changes for pairsplit are (WD = Write Disable, WE = Write Enable):
If P-VOL has non-reected data in PAIR state:
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 282
Behavior of OLD pairsplit at T0 Behavior of rst pairsplit at T0
T0: PVOL_PAIR from/to SVOL_PAIR(WD)
T1: PVOL_COPY from/to SVOL_COPY(WD)
T2: PVOL_PSUS from/to SVOL_SSUS(WE)
PVOL_PAIR from/to SVOL_PAIR(WD)
PVOL_PSUS from/to SVOL_COPY(WE)
PVOL_PSUS from/to SVOL_SSUS(WE)
If P-VOL has been reected all data to S-VOL in PAIR state:
Behavior of OLD pairsplit at T0 Behavior of First pairsplit at T0
T0: PVOL_PAIR from/to SVOL_PAIR(WD)
T1: PVOL_PSUS from/to SVOL_SSUS(WE)
PVOL_PAIR from/to SVOL_PAIR(WD)
PVOL_PSUS from/to SVOL_SSUS(WE)
■The state changes for paircreate -split are:
Behavior of OLD paircreate -split at
T0
Behavior of First paircreate -split
at T0
T0: SMPL from/to SMPL
T1: PVOL_COPY from/to SVOL_COPY(WD)
T2: PVOL_PSUS from/to SVOL_SSUS(WE)
SMPL from/to SMPL
PVOL_PSUS from/to SVOL_COPY(WE)
PVOL_PSUS from/to SVOL_SSUS(WE)
■If you attempt the pairevtwait -s psus in PVOL_PSUS & SVOL_COPY state, then
pairevtwait will return immediately even if the S-VOL is still in SVOL_COPY state
because P-VOL is already in PVOL_PSUS state. If you want to wait the "SVOL_SSUS"
state, and then you must check the status of the S-VOL becomes "SVOL_PSUS" via the
return code using pairvolchk -ss command on S-VOL side or pairvolchk -ss -
c command on P-VOL side. Or you can use pairevtwait -ss ssus on both P-VOL
and S-VOL, pairevtwait -ss ssus -l on S-VOL locally.
■If you attempt the pairresync -restore or pairsplit -S in PVOL_PSUS &
SVOL_COPY state, then ShadowImage will reject this command due to unable to
perform. In this case, you need to wait until the S-VOL state becomes SVOL_SSUS.
Pair status versus Copy-on-Write Snapshot commands
Pair
Status
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
No -split -split -E option -C option -S option Resync
1 SMPL Accepted 2 Rejected Rejected Rejected Acceptable Rejected
TrueCopy/ShadowImage/Universal Replicator pair status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 283
Pair
Status
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
No -split -split -E option -C option -S option Resync
2 COPY
RCPY
Acceptable Rejected Rejected Rejected Rejected Acceptable
3 PAIR Acceptable Accepted*
4
Rejected Accepted
4
Accepted 1 Acceptable
4 PSUS
(PFUS
)
Rejected Acceptabl
e
Rejected Acceptabl
e
Accepted 1 Accepted*
2
5 PSUE Rejected Rejected Acceptable Rejected Accepted 1 Accepted*
2
Accepted: The command is accepted and executed. When the operation ends normally,
the status changes to the shown number.
Accepted*: The command is accepted and issued. Whether this command is executed
or not is determined by the microcode version of the storage system.
Acceptable: The command is accepted, but not executed.
Rejected: The command is rejected and the operation terminates abnormally.
Note:
■pairsplit ("simplex -S") of Copy-on-Write Snapshot volume is returned
without verication of state transition that waits until SMPL state. In SMPL
state, the volume that was S-VOL becomes R/W disable and data is
discarded.
■In the "PSUE" state, Copy-on-Write Snapshot does not manage for
dierential data between the primary volume and secondary volume.
TrueCopy Async, TrueCopy Sync, Universal Replicator, and global-
active device volumes
TrueCopy Async and Universal Replicator provide paired volumes that use asynchronous
transfer to ensure the sequence of writing data between the primary volume and
secondary volume. The sequence of writing data between the primary and secondary
volumes is guaranteed within each consistency group (CTG). The following gure
illustrates TrueCopy Async consistency group.
TrueCopy Async, TrueCopy Sync, Universal Replicator, and global-active device volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 284
Restrictions
■Group denition of TrueCopy Async/Universal Replicator/TrueCopy Sync/global-
active device volume: All volumes in a group must be contained within the same
storage system. If two or more groups of CCI include the same consistency group
(CTG), then pair operation of the group is applied to the entire CTG.
■Registration of CTG ID number and limitations: CCI registers CTG IDs to the RAID
disk array automatically when paired volumes are created by the paircreate
command, and groups of conguration denition les are mapped to CTG ID. The
maximum number of consistency groups is as follows:
●HUS VM, VSP, USP V/VM, and Universal Storage Platform/TagmaStore NSC: 256
(CTG ID 0 - CTG ID 255)
●VSP G800, VSP F800, and 9900V: 128 (CTG ID 0 - CTG ID 127)
●VSP G400, G600 and VSP F400, F600: 64 (CTG ID 0 - CTG ID 63)
●VSP G200: 16 (CTG ID 0 - CTG ID 15)
TrueCopy Async/Universal Replicator/global-active device pair command is
terminated with EX_ENOCTG when the maximum number of consistency groups is
exceeded.
TrueCopy Async, TrueCopy Sync, Universal Replicator, and global-active device volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 285
■Relationships between CTG ID and Journal ID: The consistency group numbers
from 0 to 127 are assigned to TrueCopy Async and TrueCopy Sync, and from 0 to 255
are assigned to Universal Replicator and global-active device. The consistency group
numbers for Universal Replicator are mapped to the journal. See the table given
below for the assignment of consistency group IDs (CTG IDs).
CTG ID Assignment
0 to 127 TrueCopy Asynchronous
TrueCopy
CTG 0 to 127
Universal Replicator
Global-active device
CTG 0 to 127
128 to 255 Universal Replicator
Global-active device
CTG 128 to 255
■Pair split with the TrueCopy Sync CTG specied: The operation for making data
consistency is only supported by the following option:
pairsplit -g <group> ... [-r]
pairsplit -g <group> ... -rw
TrueCopy Async and Universal Replicator volume characteristics
TrueCopy Async/Universal Replicator volumes have the following characteristics:
■PAIR state: A TrueCopy Async pair changes to the PAIR status as soon as all pending
recordsets have been placed in the queue at the primary volume, without waiting for
the updates to complete in the secondary volume.
■Pair splitting: When a TrueCopy Async pair is split or deleted, all pending recordsets
at the primary volume are sent to the secondary volume, then the pair status changes
to PSUS or SMPL. With the pairsplit command only, updates for the primary
volume that occur during and after the pairsplit operation are marked on the bitmap
of the primary volume.
■Pair resynchronization: The pairresync command resynchronizes the secondary
volume based on the primary volume. This resynchronization does not guarantee the
sequenced data transfer.
■Error suspension: Pending recordsets that have not yet been sent to the secondary
volume are marked on the bitmap of the primary volume, then deleted from the
queue, and then the pair status changes to PSUE.
■Group operations: TrueCopy Async automatically registers the CTG IDs with the
storage system when paired volumes are created using the paircreate command,
and groups in the conguration le are mapped to their corresponding CTG IDs. If
more than one group, dened in the conguration denition le, is assigned to the
same CTG ID, then pair operations on the group specicity apply to the entire
consistency group.
TrueCopy Async and Universal Replicator volume characteristics
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 286
Sidefile cache for TrueCopy Async
The rst-in-rst-out (FIFO) queue of each consistency group is placed in an area of cache
called the sidele. The sidele is used for transferring TrueCopy Async recordsets to the
RCU. The sidele is not a xed area in cache but has variable capacity for write I/Os for
the primary volume. If the host write I/O rate is high and the MCU cannot transfer the
TrueCopy Async recordsets to the RCU fast enough, then the sidele capacity expands
gradually. The sidele has a threshold to control the quantity of data transfer of host side
write I/O. Host side write I/Os are controlled by delaying response when the sidele
exceeds the constant quantity limit on cache in the storage system. See the gure below
for sidele quantity limit.
Legend
■Sidele area: Sidele area = 30% to 70% of cache as set on Storage Navigator (default
sidele = 50% for USP V/VM, ; 40% for TagmaStore USP/TagmaStore NSC).
■Write I/O control via the high-water mark (HWM): When the quantity of data in the
sidele reaches 30% of cache, the TrueCopy Async pair status is HWM of PAIR state,
and the host write I/Os receive a delayed response in the range of 0.5 seconds to 4
seconds. Following is an arithmetic expression of the HWM at 100% of a sidele
space:
HWM(%) = High water mark(%) / Sidele threshold (30 to 70) * 100
■Write I/O control via the sidele threshold: When the quantity of data in the
sidele occupies the maximum dened sidele area, host write I/Os are delayed until
there is enough sidele space to store the next new write data. The copy pending
timeout group option is dened using Storage Navigator and species the maximum
delay between the M-VOL update and the corresponding R-VOL update. The range for
the copy pending timeout option is 1-255 seconds (600 seconds for Universal
Replicator), and default value is 90 seconds (60 seconds for UR). If the timeout occurs
during this wait state, the pair status changes from PAIR to PSUS (sidele full), and
host write I/Os continue with updates being managed by the cylinder bitmap.
Important: The copy pending timeout value should be less than the I/O
timeout value of the host system.
TrueCopy Async transition states and sidefile control
TrueCopy Async volumes have special states for sidele control during status transitions.
The table below shows the transition states for TrueCopy and TrueCopy Async volumes.
Sidele cache for TrueCopy Async
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 287
The suspending and deleting states are temporary internal states within the RAID
storage system. CCI cannot detect these transition states, because these states are
reported on the previous state of the storage system. These states are therefore
concealed inside the pairsplit command. After the pairsplit command is accepted,
host write I/Os for the P-VOL are managed by the cylinder bitmap (normal), non-
transmitted data remaining in the P-VOL's FIFO queue is transferred to the S-VOL's FIFO
queue, and the pair status is then set to PSUS [SMPL] state when all data in the P-VOL's
FIFO queue has been transmitted.
PFUL If the quantity of data in sidele cache exceeds 30% of cache storage, the internal
status of the RAID storage system is PFUL, and host write I/Os receive delayed response
in the range of 0.5 seconds (minimum) to 4 seconds (maximum).
PFUS If the quantity of data in sidele cache exceeds the user-dened sidele area
(30%-70%), then host write I/Os must wait for enough sidele space to become available
for storing the next new write data. If a copy pending timeout occurs during this waiting
state, then the pair status changes from PAIR to PFUS, host write I/Os are accepted, and
write data is managed by bitmap.
The CCI software can detect and report the PFUL and PFUS states as follows:
■As a return code of the pairvolchk command
■As the status code displayed to code item by the pairmon command
■As the paired status displayed to status item using -fc option of pairdisplay
command
State table for TrueCopy Sync vs. TrueCopy Async
The following table describes pair statuses of TrueCopy Sync and TrueCopy Async
volumes.
CCI
stat
e
Storage
system
internal
state
Description
Writing control on
TC async volume Transfe
r data
via
ESCON
TrueCopy
Sync TrueCopy Async
Writing
data
Respon
se
SM
PL
SMPL SMPL Same Normal Usual None
COP
Y
COPY COPY Same Via
Sidele
Usual* Sidele
&
bitmap
Deleting N/A Deleting from COPY
using [pairsplit -S]
Normal Usual Sidele
Suspendi
ng
N/A Suspending from COPY
by using [pairsplit]
Via
Bitmap
Usual Sidele
PAI
R
PAIR Synchroniz
ed
Async
sidele in
use
Less than
HWM
Via
Sidele
Usual Sidele
TrueCopy Async transition states and sidele control
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 288
CCI
stat
e
Storage
system
internal
state
Description
Writing control on
TC async volume Transfe
r data
via
ESCON
TrueCopy
Sync TrueCopy Async
Writing
data
Respon
se
PFUL N/A HWM to
Threshold
Via
Sidele
Delayed Sidele
Over
Threshold
Via
Sidele
Wait
until
under
threshol
d
Sidele
Deleting N/A Deleting from PAIR
using [pairsplit -S]
Normal Usual Sidele
Suspendi
ng
N/A Suspendi
ng from
PAIR
Using
[pairsplit ]
Via
Bitmap
Usual Sidele
Timeout of
over
threshold
PSU
S
PSUS PSUS Same Via
Bitmap
Usual None
PFUS None Timeout Over
Threshold
Via
Bitmap
Usual None
PSU
E
PSUE PSUE Same (link down, etc.) Via
Bitmap
Usual None
PD
UB
PDUB PDUB Same Via
Bitmap
Usual None
* If the host has more write I/Os in COPY state, then host write I/Os are delayed until
there is enough space in the sidele.
Legend:
Bitmap: Host write data is managed via a cylinder BITMAP of delta data.
Normal: Host write data is not managed by BITMAP or sidele.
Usual: Host side writing response is not delayed.
HWM (High Water Mark): Sidele quantity is over 30% of cache storage.
TrueCopy Async transition states and sidele control
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 289
TrueCopy Async/Universal Replicator error state
In the case of an ESCON or bre-channel (FC) failure, the S-VOL FIFO queue is missing a
data block that was transferred from the P-VOL FIFO queue. The RCU waits to store the
next sequenced data block in the S-VOL FIFO queue until the TrueCopy Async copy
pending timeout occurs (dened using TrueCopy). In addition, the timeout value can be
specied at Device Manager - Storage Navigator. The default value is set to 5 minutes. If
the timeout occurs during this waiting state, the pair status changes from PAIR to PSUE,
and non-sequenced data blocks are managed by the S-VOL bitmap. The missing data
block can be recovered using the pairresync command, which merges the S-VOL
bitmap with the P-VOL bitmap. The gure below shows this situation on the secondary
side.
TrueCopy Sync/TrueCopy Async and Universal Replicator/global-
active device fence level settings
TrueCopy volume pairs are assigned a fence level for write I/Os to ensure mirroring
consistency of critical volumes. When the secondary volume takes over from the primary
volume, the takeover action is determined according to the pair status and fence level of
the corresponding secondary volume. The table below shows the relationship between
TrueCopy pair statuses and fence levels.
The fence level for TrueCopy is Data, Status, Never. The fence level for TrueCopy Async
and Universal Replicator is always Async. The fence level for global-active device is
always Never.
■Mirror consistency = Identity and sequence of data is assured via error notication
after an I/O completion.
■Data consistency = Sequence of data is assured in I/O order based on host.
TrueCopy Async/Universal Replicator error state
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 290
Relationship between TrueCopy pair statuses and fence levels
TrueCopy pair status of volume
Fence level and write response
Data 1Status 2Never 3Async 4
OK OK OK OK
Mirroring
consistenc
y assured
Mirroring
consistenc
y assured
Mirroring
consistenc
y assured
Data
consistenc
y assured
ERROR OK OK OK
Mirroring
consistenc
y assured
Mirroring
consistenc
y not
assured
Mirroring
consistenc
y not
assured
Data
consistenc
y assured
ERROR ERROR OK OK
Mirroring
consistenc
y assured
Mirroring
consistenc
y assured
Mirroring
consistenc
y not
assured
Data
consistenc
y assured
Notes:
1. When the fence level is data: Mirroring consistency is assured, since a write error
is returned if mirror consistency with the remote S-VOL is lost. The secondary
volume can continue operation, regardless of the status. Note: A P-VOL write that
discovers a link down situation will, in addition to returning an error to the host,
likely be recorded on [only] the P-VOL side.
2. When the fence level is status: If there is a mirror consistency problem (that is,
PSUE) and it is possible to set the S-VOL to PSUE, the P-VOL write completes OK. If
the S-VOL cannot be set to PSUE for any reason, the P-VOL write completes with
an error. The mirror consistency of the S-VOL depends on its status:
PSUE: The secondary volume is dubious.
PAIR: The secondary volume can continue operation.
3. When the fence level is never: Writing to the P-VOL is still enabled in the state
where mirror consistency to the S-VOL is lost, regardless of whether the
secondary volume status is updated or not. Thus, the secondary could have these
states:
PSUE: The secondary volume is dubious.
TrueCopy Sync/TrueCopy Async and Universal Replicator/global-active device fence level settings
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 291
TrueCopy pair status of volume
Fence level and write response
Data 1Status 2Never 3Async 4
PAIR: The secondary volume is substantially dubious, since it can continue
operation and is also dubious. The P-VOL status must be checked to conrm the
mirroring consistency.
4. When the fence level is async: TrueCopy Async/UR uses asynchronous transfers to
ensure the sequence of write data between the P-VOL and S-VOL. Writing to the P-
VOL is enabled, regardless of whether the S-VOL status is updated or not. Thus
the mirror consistency of the secondary volume is dubious (similar to the "Never"
fence):
■PSUE: The S-VOL mirroring consistency is not assured, but the PSUE
suspended state ensures the sequence of data for the consistency group; thus,
data consistency is also assured during a PSUE state. At a PSUE state, the P-
VOL writes still complete and are also noted in a bitmap for future transfer.
Due to the use of a bitmap in the suspend state, data consistency is not
assured during a copy state resync.
■PAIR: If the P-VOL and S-VOL are both in a PAIR state, mirror consistency is not
assured (might be behind) but data consistency is assured (what has reached
the S-VOL is in the proper order).
Setting the fence level
Data fence level
The gure below shows the relationship between redo log les (journal) and data les. If
the S-VOL takes over from the P-VOL in the status shown in the gure (where two errors
have occurred), the secondary host leaves data (V) unprocessed in the roll-back
processing and cannot be recovered completely. Therefore, the fence level of a redo log
le must be dened as data. Once the fence level is set to data, the P-VOL returns an
error if data might possibly be inconsistent when a write request is issued by the host.
Since writing to the data le is not executed due to a write error of the redo log le, the
log le stays consistent with the data le. However, when the fence level is set to data, a
write I/O error occurs even in the case where operation is suspended due to an error in
the S-VOL. Accordingly, duplication becomes meaningless when the S-VOL takes over.
Thus, applications using paired volumes with the data fence level should be able to
handle write I/O errors properly. For example, the Oracle application creates multiple
redo log les by itself (three by default). The fence level can be set to data in this case in
which disk errors are permissible by creating multiple les.
Setting the fence level
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 292
Never fence level
Because most UNIX le systems (excluding JFS and VxFS) have no journal les, the fence
level should be dened as Never. When a takeover by the S-VOL occurs, fsck is executed
on the volume and the le system is cleaned up, even if the S-VOL is undened at the
secondary host. The data that is lost depends on how much dierential data is contained
in the P-VOL when the S-VOL is suspended. During operation, error recovery should be
performed when the suspended status (PSUE or PDUB) is detected (when one error
occurs).
Copy-on-Write Snapshot operations
Copy-on-Write Snapshot normally creates virtual volumes for copying on write without
specifying LUNs as S-VOLs. However, to use a Copy-on-Write Snapshot volume via the
host, it is necessary to map the Copy-on-Write Snapshot S-VOL to a LUN. Therefore, CCI
provides a combined command to enable the user or application to use the same CCI
command in order to maintain ShadowImage compatibility.
Copy-on-Write Snapshot uses two techniques, one called "V-VOL mapping" (or virtual
volume mapping) and the other is "Snapshot using copy on write" or "Copy-on-write
snapshot." Copy-on-Write Snapshot volumes are also put into pooling volumes called a
"Snapshot pool," and a Snapshot pool is specied as a pool ID when a Snapshot is made.
Copy-on-Write Snapshot and volume mapping is illustrated in the gure given below.
The following gure illustrates Copy-on-Write Snapshot volume mapping.
Copy-on-Write Snapshot operations
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 293
Copy-on-Write Snapshot volumes
The specications for Copy-on-Write Snapshot volumes are:
■Allowable type of paired volume: The supported volume type is OPEN-V only for P
VOL, and OPEN-0V for S VOL.
■Number of volumes (Copy-on-Write Snapshot) can be paired: This depends on P VOL
capacity, Copy-on-Write Snapshot pool capacity, and shared memory capacity on the
RAID storage system.
■Duplicated writing mode: Copying on write.
■Number of mirror volumes:
●Thin Image: Up to 1,024 secondary volumes can be dened for each P VOL.
●Copy-on-Write Snapshot: Up to 64 secondary volumes can be dened for each P
VOL.
For details on Thin Image or Copy-on-Write Snapshot specications such as maximum
number of mirrored volumes, volumes and operations, please see the Hitachi Thin Image
User Guide or Hiitachi Copy-on-Write Snapshot User Guide for your storage system.
Pair operations and commands for Copy-on-Write Snapshot and Thin
Image
The following table shows the pair operations and commands that can be used for Copy-
on-Write Snapshot and Thin Image pairs.
Command
Copy-on-Write
Snapshot Thin Image
Thin Image (cascade
pairs, pairs with the
clone attribute)
paircreate Yes Yes* No
pairsplit Yes Yes* No
pairresync Yes Yes* No
paireventwait Yes Yes* No
pairmon Yes Yes* No
pairvolchk Yes Yes* No
pairdisplay Yes Yes* No
raidscan Yes Yes* No
raidcom No Yes Yes
*The MU numbers that can be used and referenced are from 0 to 63.
Copy-on-Write Snapshot volumes
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 294
Creating a Copy-on-Write Snapshot pair
The CCI command for creating a Thin Image or Copy-on-Write Snapshot pair is the same
as for ShadowImage. However, Thin Image pair can only operate up to 64 S-VOLs.
Therefore, use raidcom command if you want to operate more than 64 S-VOLs.
The RAID storage system determines whether it is a ShadowImage pair or a Thin Image/
Copy-on-Write Snapshot pair by the attribute of the S-VOL. The RAID storage system also
determines whether it is a Thin Image pair or a Copy-on-Write Snapshot pair by the type
of the pool to be used.
A Thin Image pair is generated in the following two cases:
■When a V-VOL (OPEN-0V) is specied as an S-VOL.
■When a pool for Thin Image is specied as the pool type.
A Copy-on-Write Snapshot pair is generated in the following two cases:
■When a V-VOL (OPEN-0V) is specied as an S-VOL.
■When a pool for Copy-on-Write Snapshot is specied as the pool type.
A V-VOL has the following characteristics:
■It appears as "OPEN-0V" to identify a V-VOL easily via the SCSI Inquiry or CCI.
■A V-VOL unmapped to the S-VOL of a Copy-on-Write Snapshot will reply to a SCSI
Inquiry, but Reading and/or Writing is not allowed. LDEV will reply the capacity setting
as an LU to SCSI Read Capacity.
■A V-VOL that has become the S-VOL of a Copy-on-Write Snapshot will reply to a SCSI
Inquiry, and Reading and/or Writing is allowed.
Copy-on-Write Snapshot pair status
Each paired volume consists of a primary volume (P-VOL) and a secondary volume (S-
VOL). Each volume has the status for controlling the pair state.
The P-VOL controls the pair state that is reected on the status of the S-VOL. The major
pair statuses are "SMPL", "PAIR", "PSUS", "COPY", and "RCPY". The status is changed
when the CCI command is issued. A read or write request from the host is allowed or
rejected according to the status.
See the table below for Copy-on-Write Snapshot pairing status.
Creating a Copy-on-Write Snapshot pair
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 295
P-VOL
Status Pairing Status Primary Secondary
SMPL Unpaired (Copy-on-Write Snapshot) volume R/W enabled R/W disable1
PAIR
(PFUL)
The Copy-on-Write Snapshot available state
allocated the resource.
R/W enabled R/W disable
COPY The preparing state allocates the resource for
the Copy-on-Write Snapshot.
R/W enabled R/W disable
RCPY The copying state from Copy-on-Write
Snapshot to the primary volume by using
restore option.
R/W enabled R/W disable
PSUS
(PFUS)
The dierences of the updated data of the
primary and secondary volume are controlled
with copying on write.
R/W enabled R/W enabled
PSUE
(Error)
"PSUS" status due to an internal failure. The
dierences of the updated data for the Copy-
on-Write Snapshot volume are not controlled.
R/W enabled2R/W disable
Notes:
1. V-VOL unmapped to the S-VOL of a Copy-on-Write Snapshot will reply to a SCSI
Inquiry, but Reading and/or Writing is not allowed.
2. Reading and writing are enabled, as long as no failure occurs in the primary
volume.
Pair status relationship to Copy-on-Write Snapshot commands
The pair status relationship to Copy-on-Write Snapshot commands table applies to a
Copy-on-Write Snapshot context. It explains:
1. What a pair status can be prior to any CCI command execution.
2. What the result will be after giving a CCI command.
3. What the pair status can be if the CCI command is accepted.
-
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
Pair
Status No -split -split -E option -C option -S option Resync
1 SMPL Accepted 2 Rejected Rejected Rejected Acceptable Rejected
2 COPY
RCPY
Acceptable Rejected Rejected Accepted* Accepted 1 Acceptable
Pair status relationship to Copy-on-Write Snapshot commands
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 296
-
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
Pair
Status No -split -split -E option -C option -S option Resync
3 PAIR Acceptable Accepted*
4
Rejected Accepted* Accepted 1 Acceptable
4 PSUS
(PFUS
)
Rejected Acceptabl
e
Rejected Accepted* Accepted 1 Accepted*
2
5 PSUE Rejected Rejected Rejected Rejected Accepted 1 Accepted*
2
Accepted: The command is accepted and executed. When the operation ends normally,
the status changes to the shown number.
Accepted*: The command is accepted and issued. Whether this command is executed
or not is determined by the microcode version of the storage system.
Acceptable: The command is accepted, but not executed.
Rejected: The command is rejected and the operation terminates abnormally.
Note:
■pairsplit -S of a Copy-on-Write Snapshot volume is returned without
verication of the state transition that waits until SMPL state. In a SMPL
state, note that the volume that was an S-VOL becomes R/W disabled and
data is discarded.
■In the "PSUE" state, Copy-on-Write Snapshot does not manage dierential
data between the primary volume and secondary volume.
Controlling Volume Migration
Volume Migration, including external volumes, must be controlled using CLI in a Data
Lifecycle Management (DLCM) solution. It is possible to support volume migration
(Volume Migration function) and the external connection by operating the current
ShadowImage and VDEV mapping of the external connection.
Also, it is important to consider the support of Volume Migration on the compatibility
based on the current CLI interface, because CCI is supporting ShadowImage and the
external connection. For this purpose, CCI makes the CLI interface that works by
minimum compatible of the application by specifying the COPY mode for Volume
Migration to the CLI of CCI.
Controlling Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 297
Specifications for Volume Migration
CCI must be mapped to the port for pooling of RAID in order to control the volume of the
external connection. Therefore, the external volume needs to be mapped previously to
the RAID port without connecting to the host. Following is an execution example of the
volume migration executed for LDEV#18.
The following gure shows the Volume Migration congurations.
Volume Migration functions
(1) Command specication
CCI operates the volume migration by specifying to the horcm*.conf as same SI and TC,
because the volume migration using CCI is necessary to be dened the mapping for the
target volume.
MU# (of SMPL as SI) that is not used because SI is used for Volume Migration operation.
An original volume for the migration is dened as P-VOL. A target volume for the
migration is dened as S-VOL. In other words, an original volume is migrated from P-VOL
to S-VOL, and the mapping between LDEV and VDEV is swapped after copied.
(2) Mapping specication
The mapping between LUN and LDEV is maintained for the replying of SCSI-Inquiry in
order to make recognize as identical LUN through the host after mapping changes.
The way to know whether the mapping is changed or not is possible to use "-fe" option
of pairdisplay and/or raidscan command that shows the connection for the external
volumes.
Also LU of the external connection and LU of RAID Group intermingle on the port for
pooling, but can conrm this with the above option of the raidscan command.
Specications for Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 298
(3) Group operation
It is possible to execute the Volume Migration as a group by describing it to the
horcm*.conf, however LU(LDEV), which was mapped to S-VOL after command execution,
does not maintain the consistency of the group. In other words, you must consider the
volume mapped to the S-VOL after execution as the discarded volume.
When HORCM demon is KILLed or the host has crash during group operation, the group
aborting the execution of the command has LUN mixed with the external connection and
RAID Group as the group. In this case, CCI skips the executed LU and issues the CC
(Volume Migration) command to the un-executed LU, and an identical command is
executed once again.
(4) Using MU#
CCI manages the status of TC/SI using MU#, so CCI uses the empty MU# that is managed
for SI. Therefore, execute the command of the volume migration in the environment for
SI having HORCC_MRCF environment variable. An example is shown below.
(5) HORCM instance
It is possible to describe the original and target volume for the volume migration to MU#
as another group in horcm*.conf for HORCM instance of SI and /or TC. Also, it is possible
to dene the original and target volume for the volume migration in the horcm*.conf as
HORCM instance independent from SI/TC.
Commands to control Volume Migration
(1) Command for Volume Migration
CCI supports the volume migration by adding an option (-m cc) to the paircreate
command.
paircreate -g <group> -d <pair vol> … -m <mode> -vl[r] -c <size>
-m <mode> mode = cc (can only be specied for ShadowImage)
This option is used to specify the Volume Migration mode.
Note: This option cannot be specied with "-split" option in the same
command.
-vl[r]
The -vl option species "local", and copies from the local instance LU (P-VOL) to the
remote instance LU (S-VOL), an original volume as the local instance LU is migrated from
P-VOL to S-VOL, and the physical volume mapping between P-VOL and S-VOL is swapped
after copied
Commands to control Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 299
The -vr option species "remote", and copies from the remote instance LU (P-VOL) to
the local instance LU (S-VOL), an original volume as the remote instance LU is migrated
from P-VOL to S-VOL, and the physical volume mapping between P-VOL and S-VOL is
swapped after copied.
-c <size>: This option is used to specify a track size of the case that copies paired
volume at 1-15 extents. In case of stopping Write to P-VOL and copying in a short time,
the maximum value 15 is specied. When this option is omitted, it uses a default value of
(3) is used for track size.
(2) Command for discovering an external volume
It is possible to discover the external volumes by using "-fe" option of the raidscan
command.
raidscan -p <port#> -fe
-fe
This option is used to display the serial# and LDEV# of the external LUNs only mapped to
the LDEV.
If the external LUN mapped to the LDEV on a specied port does not exist, then this
option will do nothing.Also if this option is specied, -f[f][g][d] option is not allowed.
Display example:
# raidscan -p cl1-a-0 -fe -CLI
PORT# /ALPA/C TID# LU# Seq# Num LDEV# P/S Status Fence E-Seq# E-
LDEV#
CL1-A-0 ef 0 0 8 62496 1 19 SMPL - - 30053 30
CL1-A-0 ef 0 0 9 62496 1 21 SMPL - - 30053 32
CL1-A-0 ef 0 0 10 62496 1 22 SMPL - - 30053 33
E-Seq#
Displays the production (serial) number of the external LUN.
E-LDEV#
Displays the LDEV# of the external LUN.
(3) Command for conrming the status
It is possible to conrm the status for Volume Migration by using "-fe" option of the
pairdisplay command.
pairdisplay -g <group> -fe
-fe
Commands to control Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 300
This option is used to display the serial# and LDEV# of the external LUNs mapped to the
LDEV and additional information for the pair volume.
This option displays the information above by adding to last column, and then ignores
the format of 80 column.
This option is invalid if the cascade options (-m all,-m cas) are specied.
Display example:
Before execution of Volume Migration command:
# pairdisplay -g horc0 -fe
Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#
horc0 ... 62496 18.SMPL ---,----- --- - - - - - -
horc0 ... 62496 19.SMPL ---,----- --- - - - H 30053 30
# paircreate -g horc0 -vl -m cc
During execution of Volume Migration command, the progress is displayed in the copy %:
# pairdisplay -g horc0 -fe
Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#
horc0 ... 62496 18.P VOL COPY,62496 19 - - C - - -
horc0 ... 62496 19.S VOL COPY,----- 18 - - C H 30053 30
After completion of Volume Migration command:
Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#
horc0 ... 62496 18.P VOL PSUS,62496 19 - - C V 30053 30
horc0 ... 62496 19.S VOL SSUS,----- 18 - - C - - -
Commands to control Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 301
CM
Displays the following copy modes:
■N: Non Snapshot
■S: Snapshot. For SMPL state, this shows that pair-volume will be created as
Copy-on-Write Snapshot.
■C: Volume Migration
EM
Displays the following external connection modes:
■H: Mapped E-lun as hidden from the host.
■V: Mapped E-lun as visible to the host ' - ': Unmapped to the E-lun.
■BH: Mapped E-lun as hidden from the host, but LDEV blockading.
■BV: Mapped E-lun as visible to the host, but LDEV blockading.
■B: Unmapped to the E-lun, but LDEV blockading
E-Seq#
Displays the production (serial) number of the external LUN. Unknown is shown as
'-'.
E-LDEV#
Displays the LDEV# of the external LUN. 'Unknown' is shown as '-'.
(4) Command for discovering an external volume via the device le
It is possible to discover the external volumes by using the inqraid command.
Example in Linux:
# ls /dev/sd* |./inqraid -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group
PRODUCT_ID
sdh CL2-G 63528 15360 - s/s/ss 0100 5:01-09 OPEN-V
sdu CL2-G 63528 2755 - s/s/ss 000B S:00001 OPEN-
0V
sdv CL2-G 63528 2768 - s/s/ss 000B U:00000 OPEN-
0V
sdw CL2-G 63528 2769 - s/s/ss 000B E:16384 OPEN-V
R:Group
This displays the physical position of an LDEV according to mapping of LDEV in the
RAID storage system.
Commands to control Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 302
LDEV mapping R: Group
RAID Group RAID Level
1: RAID1
5: RAID5
6: RAID6
RAID Group number - Sub
number
Copy-on-Write Snapshot S-VOL S PoolID number
Unmapped U 00000
External LUN E External Group number
Example in Linux:
# ls /dev/sd* |./inqraid
/dev/sdh -> CHNO = 0 TID = 1 LUN = 1
[SQ] CL2-G Ser = 63528 LDEV =15360 [HITACHI ] [OPEN-V
]
HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]
RAID5[Group 1- 9] SSID = 0x0100
/dev/sdu -> CHNO = 0 TID = 1 LUN = 14
[[SQ] CL2-G Ser = 63528 LDEV =2755 [HITACHI ] [OPEN-V
]
HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]
E-LUN[Group 00001] SSID = 0x000B
SNAPS[PoolID 0001] SSID = 0x000B
/dev/sdv -> CHNO = 0 TID = 1 LUN = 15
[[SQ] CL2-G Ser = 63528 LDEV =2768 [HITACHI ] [OPEN-V
]
HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]
E-LUN[Group 08191] SSID = 0x000B
UNMAP[Group 00000] SSID = 0x000B
/dev/sdw -> CHNO = 0 TID = 1 LUN = 16
[[SQ] CL2-G Ser = 63528 LDEV =2769 [HITACHI ] [OPEN-V
]
HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]
E-LUN[Group 16384] SSID = 0x000B
E-LUN[Group 16384] SSID = 0x000B
Group
This item shows physical position of an LDEV according to mapping of LDEV in the
RAID storage system.
LDEV Mapping Display Formats
RAID Group RAID1[Group Group number - Sub number]
Commands to control Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 303
LDEV Mapping Display Formats
RAID5[Group Group number - Sub number]
RAID6[Group Group number - Sub number]
Copy-on-Write Snapshot S-VOL SNAPS[PoolID poolID number ]
Unmapped UNMAP[Group 00000]
External LUN E-LUN[Group External Group number]
Relations between "cc" command issues and migration volume status
The migration volumes can be handled by issuing the CCI commands (pair creation and
pair splitting commands). The validity of the specied operation is checked according to
the status of the paired volume (primary volume).
The table shows the relations between the migration volume statuses and command
acceptances.
Command Pair Creation Pair Splitting
Pairing Status CC -m cc Simplex -S
(1) SMPL Accepted
(2) to (3)
(2) to (4)
Acceptable
(2) COPY Acceptable Accepted (1)
(3) PSUS Rejected Accepted (1)
(4) PSUE PDUB Rejected Accepted (1)
Legend:
Accepted: A command is accepted and executed. When the command execution
succeeds, the status changes to that of the shown number.
Acceptable: No operation is executed, though a command is accepted.
Rejected: Command execution is rejected and the operation terminates abnormally.
Other commands and options (for example, pairresync…) for operating a paired
volume are rejected.
The "-m cc" option cannot be specied with "-split" option in the same command.
Relations between "cc" command issues and migration volume status
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 304
Restrictions for Volume Migration
Volume Migration must be used within the following restrictions:
■ShadowImage (HOMRCF): The operation for the volume migration must be operated
at the "SMPL" or "PAIR" state. If not, paircreate -m cc command is rejected with
EX_CMDRJE or EX_CMDIOE. Also ShadowImage cannot be operated to CC_SVOL
moving in Volume Migration. In copying CC_SVOL, the copy operation for the volume
migration is stopped, if the ShadowImage pairsplit command is executed.
■TrueCopy (HORC): The operation for the volume migration must be performed at the
"SMPL" or "PSUS" state. If not, paircreate -m cc command is rejected with
EX_CMDRJE or EX_CMDIOE. Also HORC cannot be operated to CC_SVOL copying in
Volume Migration. On one hand, in copying CC_SVOL, the copy operation for the
volume migration is stopped, if pairresync command for of HORC is executed.
■LDEV type for Volume Migration: The volume of the external connection for the
volume migration must be mapped to an LDEV as OPEN-V.
Universal Replicator MxN configuration and control
Overview
Universal Replicator supports 4X4 by using sysplex timers on the mainframe. However,
open systems do not have an equivalent of sysplex timers on the mainframe, because
the SCSI protocol does not have timestamps.
If the open system (CCI) has the timestamp as an equivalent of sysplex timers, Universal
Replicator supports 4X4 on the open system.
■CCI: delivers the timestamp(CTQ-Marker) to the consistency group
■Storage system (RCU): arbitrates the timestamp (CTQ-Marker) across multiple storage
systems connected remote command devices, and then commits the journal data.
Restrictions for Volume Migration
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 305
In this architecture, CCI needs to be running. If CCI has stopped, the storage system
(RCU) function does not appear to exist. Therefore, the better architecture is to include
the storage system (RCU) function into CCI.
CCI already supports the group control across multiple storage systems in the TC_Sync
group. This means that CCI can support Universal Replicator MxN on the open system if
CCI is capable of delivering the timestamps and committing the Journal data with a CTQ-
Marker.
Thus, CCI supports UR MxN for open systems in the four ways described in the policy.
Policy
All data consistency of the consistency group across multiple storage systems is
maintained by CCI. The storage system supports only basic functions; there is no relation
between storage systems in order to simplify testing and congurations.
CCI supports Universal Replicator MxN in the following ways.
(1) Delivering the timestamp (CTQ-Marker)
CCI (HORCM daemon process) makes a table for the groups registered to the horcm.conf
as HORCM_CTQM with startup, and makes the threads for each group that delivers the
same timestamp with an increment to the multiple storage systems congured in a
group. The thread for a group delivers the same timestamp with increments, as far as a
group congured Universal Replicator in the PAIR status.
The timestamp is delivered by using Freeze/Q-Marker & Run way as default. The
timestamp is maintained in each storage system. CCI includes this timestamp with
startup, and then delivers the same timestamp with increments to each storage system.
(2) Arbitrating/committing the journal data with CTQ-Marker
The thread for a group on HORCM compares the timestamp of S-JNL on each storage
system (RCU) as far as a group congured Universal Replicator in PAIR state. Once
HORCM detects a matching point of the timestamp (CTQ-Marker) on all storage systems
(RCU), it issues an order to commit the Journal data with CTQ-Marker to each storage
system (RCU).
(3) Propagating Error suspend
The thread for a group on HORCM delivers the same timestamp with increments as far
as a group congured Universal Replicator in PAIR state. If the PSUE/PFUS state detects
at least one storage system, then it noties another storage system to suspend PSUS in
order to keep the state consistent in the consistency group. Then the thread stops to
deliver the timestamp, and keeps monitoring its consistency group with interval of
HORCM_CTQM until it becomes PAIR state by next pair-resync.
Policy
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 306
(4) Committing the Journal data inside the pairsplit command
The pairsplit command makes a suspending state on PAIR state, and inherits to
compare the timestamp of S-JNL on each storage system (RCU). If it detects a matching
point of the timestamp (CTQ-Marker) on all storage systems (RCUs), then it issues an
order to commit the Journal data with Q-Marker to each storage system (RCU), and
repeats it until it detects an EOM (End Of Marker) of CTQ-Marker with the pairsplit
command.
Configuration definition file (horcm.conf)
CCI supports TC_Sync group across multiple storage systems, but it does not allow
TrueCopy Async (UR) group across multiple storage systems. Therefore, CCI needs to add
the group denition (HORCM_CTQM) in order to allow making TrueCopy Async(UR) group
across multiple storage systems. Then the HORCM daemon process delivers the
timestamps (called CTQ-Marker), and commits S-VOL Journal data with CTQ-Marker to
the dened group.
(1) Denition to control UR MxN
CCI supports a way to specify CTQ-Marker to the specied group by adding
"HORCM_CTQM" as a keyword in horcm.conf (see the example below).
HORCM CTQM
#groupinterval (10ms)mode(optional
oradb300
group
Denes the groups to be allowed as a group across multiple storage systems.
interval
Denes the interval for the CTQ-Marker, recommended as a few second.
mode
This is the run mode for the CTQ-Marker (timestamp). The default run mode is
freeze/run. This does not normally need to be specied. If "run" is specied, then
the timestamp is issued without freeze.
(2) Specifying dierent JID for consistency groups
In order to support the MxN conguration, it is necessary to specify a dierent journal ID
(JID) for a consistency group corresponding to a CCI group. Thus CCI adds an option to
specify Journal ID in horcm.conf.
HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
oradb dev1 30095:1 02:40
oradb dev2 30095:1 02:41
Conguration denition le (horcm.conf)
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 307
oradb dev3 30095:2 02:42
oradb dev4 30095:2 02:43
Note: The number at the end of the serial number (for example, :1 or :2)
species the Journal ID.
If JID (Journal ID) is specied on horcm.conf as mentioned above, then the paircreate
command need not specify Journal ID (-jp <jid> -js <jid>) option.
If JID (Journal ID) is not specied on horcm.conf, then Journal ID (-jp <jid> -js <jid>) option
of the paircreate command is used.
Command specifications
CCI does not change the command options for supporting Universal Replicator MxN
Open. However the output of the command is added so that the command can display
the consistency group and Q-Marker for each storage system, because the consistency
group and Q-Marker are managed on each storage system.
pairdisplay command
The output of pairdisplay -v ctg and pairdisplay -v jnl[t] are supported so
that the option can display consistency group information for each storage system.
Example for UR 2x2:
# pairdisplay -g ora -v ctg
CTG P/S Status AP U(%) Q-Marker QM-Cnt SF(%) Seq# IFC OT/s CT/m RT/m
000 P-VOL PAIR 1 0 00000032 18 50 64034 ON 60 -
-
000 S-VOL PAIR 1 0 00000020 - 70 64035 - - -
-
000 P-VOL PAIR 1 0 00000031 15 50 64045 ON 60 -
-
000 S-VOL PAIR 1 0 00000022 - 70 64046 - - -
-
# pairdisplay -g ora -v jnl
JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Num LDEV#
001 1 0 PJNN 1 0 00000049 2 1633672703 64034
2 5376
002 1 0 SJNN 1 0 00000047 0 1633672703 64035
2 5378
001 1 0 PJNN 1 0 00000049 20 211506164 64045
13 12388
Command specications
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 308
002 1 0 SJNN 1 0 00000035 20 260319089 64046
16 12544
# pairdisplay -g ora -v jnlt
JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW
001 1 0 PJNN 1 0 00000c76 20 1633672703 64034
60 300 40
002 1 0 SJNN 1 0 00000c62 20 1633672703 64035
60 300 40
001 1 0 PJNN 1 0 00000c3a 7 211506164 64045
60 300 40
002 1 0 SJNN 1 0 00000c33 7 260319089 64046
60 300 40
# pairdisplay -g horc0 -v jnl -fe
JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq#
Num LDEV# CTQM
016 2 0 PJSN 1 0 0000bb1b 0 198578688 64014
1 32768 -
018 2 0 SJSN 1 0 0000bb1b 0 99283968 64014
1 32770 0000187f
017 2 0 PJSN 1 0 00000011 0 198578688 64014
1 32769 -
019 2 0 SJSN 1 0 00000011 0 99283968 64014
1 32771 0000187f
Note: CTQM displays the last CTQ-Marker that was committed on S-VOL.
pairsplit command
The pairsplit command does not change the command options for supporting UR
MxN Open. However, internal behavior is dierent from 1x1 UR or TrueCopy Async.
(1) pairsplit -r or -rw option
■Issues Freeze to consistency group on each MCU
■Issues Suspend & Run to make a suspending state for consistency group on each
MCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via MCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via
MCU
■Issues End of Suspend to terminate a suspending state, after committed with EOM
(End Of Marker) marked on MCU on all RCU
pairsplit command
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 309
Exception: If an uncommitted state (that is, link failure) is detected while executing its
operation, then the operation of committing is aborted on keeping current CTQ-Marker
level, and a suspending state terminates without waiting for the EOM (End Of Marker).
(2) pairsplit -P option
■Issues Freeze to consistency group on each MCU
■Issues Suspend & Run to make a suspending state for consistency group on each
MCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via MCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via
MCU
■Issues End of Suspend to terminate a suspending state
Exception: If an uncommitted state (that is, link failure) is detected while executing its
operation, then the operation of committing is aborted on keeping current CTQ-Marker
level, and a suspending state terminates without waiting for the EOM (End Of Marker).
(3) pairsplit -S option
■Issues Freeze to consistency group on each MCU
■Issues Delete & Run to make a deleting state for consistency group on each MCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via MCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via
MCU
■Issues End of Delete to terminate a deleting state, after committed with EOM (End Of
Marker) on all RCU
Exception: If an uncommitted state(that is, link failure) is detected while executing its
operation, then the operation of committing is aborted on keeping current CTQ-Marker
level, and a deleting state terminates without waiting for an EOM (End Of Marker).
(4) pairsplit -RS option
In the case of PAIR state (NO failure):
■Issues SwapSuspend to make a suspending state for consistency group on each RCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via RCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via
RCU
■Issues End of Suspend to terminate a suspending state, after committed with an EOM
(End Of Marker) on all RCU
pairsplit command
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 310
Exception: If an uncommitted state (that is, link failure) is detected while executing its
operation, then the operation of committing is aborted on keeping current CTQ-Marker
level, and a suspending state terminates with detecting at least one EOM (End Of
Marker).
In the case of Failure (PSUE/PSUS):
■Issues SwapSuspend to make a suspending state for consistency group on each RCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via RCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM(End Of Marker) marked on all RCU via RCU
■Issues End of Suspend to terminate a suspending state
(5) pairsplit -R option
In the case of PAIR state (NO failure):
■Issues Delete to make a deleting state for consistency group on each RCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via RCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via
RCU
■Issues End of Delete to terminate a deleting state, after committed with an EOM (End
Of Marker) on all RCU
Exception: If an uncommitted state (that is, link failure) is detected while executing its
operation, then the operation of committing is aborted on keeping current CTQ-Marker
level, and a deleting state terminates with detecting at least one EOM (End Of Marker).
In the case of Failure(PSUE/PSUS):
■Issues Delete to make a deleting state for consistency group on each RCU
■Searches/commits a minimum matching point of the CTQ-Marker on RCU via RCU (in
other words, do Journal Restore with CTQ-Marker)
■Repeats above until detecting an EOM(End Of Marker) marked on all RCU via RCU
■Issues End of Delete to terminate a deleting state
Notice on system operation
CCI does not change the command options for supporting Universal Replicator MxN
Open. However, the output of the command is added so that the command can display
the consistency group and Q-Marker for each storage system, because the consistency
group and Q-Marker are managed on each storage system.
(1) Consistency group ID and journal ID for UR
The consistency group ID must be assigned/used as the unique identier across multiple
storage systems. Therefore, the paircreate command makes a group volume having
the same consistency group ID across multiple storage systems.
Notice on system operation
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 311
(2) Cascading operation
The "-FHORC" option for cascading operation does not perform with CTQ-Marker Mode.
Hence the cascading volume must not be specied UR MxN volume when using the "-
FHORC" option.
(3) Running HORCM daemon
HORCM daemon process delivers the timestamps (called the consistency Q-Marker) to
the dened consistency group. Therefore if HORCM daemon is stopped, then UR will
stop to delta (commit) and will suspend because of Journal Full state.
Thus HORCM daemon must be running to keep the PAIR state.
(4) Separating a command device IO from application IO
The HORCM daemon process issues IOs to the command device in order to deliver the
timestamps to the dened consistency group. Therefore, it is recommended to separate
the command device path from the application IO path.
(5) About waiting application IO
The HORCM daemon process delivers the timestamps to the dened consistency group
while freezing IO for each journal.
Waiting Rate = 0.5ms * Number of journal / / Interval (ms) * 100
(Note that 0.5 ms depends on the OS platform.)
Therefore it is recommended to limit within four journal per consistency group and 8192
LDEVs per consistency group. In the case of multiple consistency groups per HORCM, it is
recommended to limit within 256 LDEVs per consistency group.
(6) HOST IO on pairsplit -RS, -R, horctakeover, pairresync -swapp(s)
The pairsplit -RS, -R operation cannot be frozen and Split HOST IO from RCU in
Link Normal state. In other words this option does not support At-time Split, hence these
operations are required to stop HOST IO in order to keep Data Consistency on S-VOL.
This is the same restriction as TC_Sync.
(7) Suspending/deleting status
To commit S-VOL Journal data with CTQ-Marker, the internal status of the storage system
must be suspending or deleting. These statuses are controlled by CCI commands.
If a CCI command is aborted for some reason (KILL, etc.) or EX_EWSTOT, the storage
system keeps that status (suspending/deleting).
To terminate this status restart CCI, and then close it after "JNL Consistency Restore".
(8) Detecting inconsistent CTQ-Marker
The pairsplit command checks data consistency with CTQ-Marker across multiple
storage systems. If an inconsistent CTQ-Marker is detected, then it returns with
EX_VOLCUR after changed to suspend status.
Notice on system operation
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 312
This error needs to conrm if CTQMs are the same on S-VOL on each storage system
using the "pairdisplay -v jnl -fe" option.
# pairdisplay -g horc0 -v jnl -fe
JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq#
Num LDEV# CTQM
016 2 0 PJSN 1 0 0000bb1b 0 198578688 64014
1 32768 -
018 2 0 SJSN 1 0 0000bb1b 0 99283968 64014
1 32770 0000187f
017 2 0 PJSN 1 0 00000011 0 198578688 64014
1 32769 -
019 2 0 SJSN 1 0 00000011 0 99283968 64014
1 32771 0000187f
(9) About pairsyncwait command
Using the Q-Marker with the pairsyncwait command is managed on each Journal
including the target device. Therefore the pairsyncwait command must specify a
target device (-g <group> -d <pair vol>, or -d <device le>, or -d <serial#> <ldev#>). For
example:
# pairsyncwait -g horc0 -d dev-002 -t 500
UnitID CTGID Q-Marker Status Q-Num
1 0 0000003de8 DONE 0
If group (-g <group>) is specied, then the rst dev_name on the specied group is used.
Explanation of terms:
JNL Consistency Restore
Commits up as far as MAX CTQ-Marker.
JNL Full Restore
Commits up to EOM (End of marker for split).
JNL Consistency Suspend
Suspends after "JNL Consistency Restore".
Notice on system operation
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 313
JNL Full Suspend
Suspends after "JNL Full Restore".
Configuration examples
CCI does not change the command options for supporting Universal Replicator MxN
Open. However the output of the command is added so that the command can display
the consistency group and Q-Marker for each storage system, because the consistency
group and Q-Marker are managed on each storage system.
(1) UR 2x2
Conguration examples
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 314
(2) UR 2x1
Duplication of CCI applications
Caution: You must read Requirements for duplication of CCI before you
duplicate CCI applications.
Duplication of CCI applications
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 315
When a failure occurs on the CCI application (for example, failure of the server on which
CCI is installed) in the MxN conguration of Universal Replicator, the data consistency in
the consistency group that spans multiple storage systems will not be able to be
maintained. Duplication of the CCI application is a function to use a second CCI
application to maintain the data consistency in the consistency group when a failure
occurs in the rst CCI application.
You can use up to two CCI applications per one consistency group for each site. The
following gure illustrates the typical MxN conguration.
When you specify the command device to the HORCM_CMD in the conguration
denition le, you must make the denition sequence of storage system match within
the site, as shown in the following denition le examples.
Duplication of CCI applications
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 316
Duplication of CCI applications
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 317
Requirements for duplication of CCI
All of the following requirements must be met in order to use multiple CCI applications. If
any of these requirements is not met, the duplication of CCI makes data inconsistent on
the RCU.
■CCI version: 01-31-03/08 or later
■Platform on which both CCI applications are installed: other than OpenVMS
Requirements for duplication of CCI
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 318
■Storage system:
●Hitachi Virtual Storage Platform (VSP)
●Hitachi Virtual Storage Platform G1x00 and Hitachi Virtual Storage Platform F1500
(VSP G1x00 and VSP F1500)
●Hitachi Virtual Storage Platform G200, G400, G600, G800 (VSP Gx00 models)
●Hitachi Virtual Storage Platform F400, F600, F800 (VSP Fx00 models)
●Hitachi Unied Storage VM (HUS VM)
■DKCMAIN microcode version:
●VSP: 70-06-20-00/00 or later
●VSP G1000: 80-03-00-00/03 or later
●VSP G1500 and VSP F1500: 80-05-00-xx/xx or later
●VSP Gx00 models and VSP Fx00 models: 83-03-00-xx/xx or later
●HUS VM: 73-03-48-x0/00 or later
Note for duplication of CCI
When a failure does not occur in CCI, the running CCI application handles the processing
to keep the data consistency in the consistency group, for example CTQ-Marker, and the
other CCI application stands by in case of a failure. If the stand-by CCI application issues
the pairsplit command, an error (EX_INVVOL) might occur. If this error occurs, issue
the pairsplit command from the other CCI application.
Remote volume discovery
In the conguration separating "Storage admin server (CCI server)" and each production
server, it is dicult to verify/check the volumes on the production servers and the
volumes described to the horcm.conf on CCI server.
In this conguration, you cannot use the following CCI capabilities:
■Command device security
■pairdisplay -fd option that displays the device le on the production host view
■raidscan -find verify
To solve this conguration problem, CCI supports a way to discover the volume
information on the remote server by exporting the volume information with the
inqraid command, and by importing its output with the raidscan -find command.
The following gure illustrates volume discovery.
Note for duplication of CCI
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 319
Discovering a remote volume
The volume information discovered on the production servers is exported by specifying
the inqraid command with the -CLI option and -export option. The volume
information includes "Keyword, Serial#, Ldev#, Device le name..". The raidscan -
find inst command on CCI server imports the volume information, and registers it
into the HORCM daemon.
The inqraid command is needed only for discovering LUNs on the production server.
Example of exporting by inqraid command (Solaris):
# ls /dev/rdsk/c1t* | inqraid -CLI -export
INQRAID:@CL4-G@64015@0@124@OPEN-V-CM@/dev/rdsk/c1t0d0s2
INQRAID:@CL4-G@64015@1@124@OPEN-V-CM@/dev/rdsk/c1t0d1s2
INQRAID:@CL4-G@64015@2@95@OPEN-V@/dev/rdsk/c1t0d2s2
INQRAID:@CL4-G@64015@3@95@OPEN-V@/dev/rdsk/c1t0d3s2
INQRAID:@CL4-G@64015@4@95@OPEN-V@/dev/rdsk/c1t0d4s2
INQRAID:@CL4-G@64015@5@95@OPEN-V@/dev/rdsk/c1t0d5s2
INQRAID:@CL4-G@64015@7@95@OPEN-V@/dev/rdsk/c1t0d7s2
Example for exporting/importing to CCI server using pipe & SSH (Solaris):
# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh
<CCI host> raidscan -find inst
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL
Discovering a remote volume
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 320
LDEV
/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 0
64015 2
/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 -
64015 2
/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 0
64015 3
Example for verifying the imported volume information (Solaris):
# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh <CCI
host> raidscan -find verify
DEVICE_FILE Group PairVol PORT TARG LUN M
SERIAL LDEV
/dev/rdsk/c1t0d0s2 - - - - - -
64015 0
/dev/rdsk/c1t0d1s2 - - - - - -
64015 1
/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 -
64015 2
/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 -
64015 3
/dev/rdsk/c1t0d4s2 - - - - - -
64015 4
/dev/rdsk/c1t0d5s2 - - - - - -
64015 5
/dev/rdsk/c1t0d7s2 - - - - - -
64015 7
Import method by the startup of CCI (horcmstart.sh) on the remote host
The following is the method to import the volume information by exporting the volume
information which is discovered on the production server and starting up the CCI on the
remote host.
Procedure
1. Export the volume information from the local host (Production server) to /etc/
horcmperm*.conf of CCI on the remote host. (* = instance number)
Example of exporting the volume information:
# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh <CCI host> cat > /etc/
horcmperm*.conf
2. Import the volume information. This volume information is imported automatically
by starting up CCI on the remote host.
Example of importing automatically by starting up CCI:
# horcmstart.sh *
Import method by the startup of CCI (horcmstart.sh) on the remote host
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 321
(* = instance number)
3. Verify the imported volume information on the CCI server.
Example for verifying the imported volume information:
# cat /etc/horcmperm*.conf | raidscan -find verify
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV
/dev/rdsk/c1t0d0s2 - - - - - - 64015 0
/dev/rdsk/c1t0d1s2 - - - - - - 64015 1
/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 - 64015 2
/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 - 64015 3
/dev/rdsk/c1t0d4s2 - - - - - - 64015 4
/dev/rdsk/c1t0d5s2 - - - - - - 64015 5
/dev/rdsk/c1t0d7s2 - - - - - - 64015 7
Import method by the startup of CCI (horcmstart.sh) on the remote host
Chapter 6: Data replication operations with CCI
Command Control Interface User and Reference Guide 322
Chapter 7: Data protection operations with CCI
This chapter describes data protection operations using CCI.
Data protection operations
User data les are normally placed on a disk through a software layer such as a le
system, LVM, disk driver, SCSI protocol driver, bus adapter, and SAN switching fabric.
Data corruption can happen due to software layer bugs or human error. CCI Data
Protection Facility does not prevent these types of errors. On the other hand, the
purpose of data protection is to prevent writing to volumes that the RAID storage system
is guarding.
Data protection functions include:
■Data Retention Utility
■Volume Retention Manager
■Volume Security
■Encryption License Key
■Database Validator
Data Retention Utility
The purpose of the Data Retention Utility is to prevent writing to volumes that the RAID
storage system is guarding. Similar to the command that supports Database Validator,
Data Retention Utility sets a protection attribute for the specied LU.
■Hide from Inquiry command. The RAID storage system conceals the target volumes
from the SCSI Inquiry command by responding "unpopulated volume" (0x7F) to the
device type.
■SIZE 0 volume. The RAID storage system replies with "SIZE 0" to the target volumes
through the SCSI Read capacity command.
■Read protection. The RAID storage system protects reading from the target volumes
by responding with the "Illegal function" check condition (SenseKey = 0x05,
SenseCode = 0x2200).
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 323
■Write protection. The RAID storage system replies with "Write Protect" in the mode
sense header, and protects from writing the target volumes by responding with the
"Write Protect" check condition (SenseKey=0x07, SenseCode=0x2700).
■S-VOL disabling. The RAID storage system rejects the command execution of the
copy series program product for not to be overwritten the secondary (target) volume
by the copy process of copy series program product (TrueCopy, Universal Replicator,
ShadowImage, Copy-on-Write Snapshot, global-active device), and protects the target
volume. This option can be used with the other Data Retention Utility options in
parallel. For example, if you want to protect from the writing by the both copy series
program product and the host accessing, set the both write protection option and this
option. Only the setting of write protection option cannot protect the target volume
from the writing executed by the copy processing of the copy series program product.
Restrictions on Data Retention Utility volumes
■File systems using Data Retention Utility
●When setting DRU to the UNIX le system volumes, the volumes must be mounted
with the Read Only option after the volumes are unmounted. If DRU is set to the
volumes as they are in the mounted status, unexpected behavior or errors might
occur in the system.
●When using a le system for Write Protect Mode set disk on Windows Server 2003/
Windows Server 2008/Windows Server 2012, use the "-x mount" and "-x umount"
CCI command options with the above mentioned procedures.
●Data Retention Utility volumes set to Write Protect Mode (Read ONLY) cannot be
used for the Windows NT/Windows 2000 le system (NTFS, FAT).
●In a conguration with NAS modules installed, do not set Data Retention Utility in a
le system volume used by a NAS module. If you do, unexpected behavior or
errors might occur in the system.
■LVM(VxVM) on Data Retention Utility
●If changing LVM conguration including Data Retention Utility, use the raidvchset -
vg command for setting the status of the target volume checking prohibited
temporarily. Also, after the completion of LVM conguration change, set again the
status as checking.
■Data Retention Utility in HA Cluster Server
●If HA Cluster software writes to the metadata at regular intervals to conrm
whether its disks are available or not, then Data Retention Utility should not be
used in HA environments.
■Dynamic disk on Windows systems
●Data Retention Utility volumes cannot be used for the dynamic disk, because the
dynamic disk does not handle the volumes set to Write Protect Mode (Read ONLY).
Data Retention Utility volumes must be used for basic disks only.
■LUN#0
●Some operating systems cannot recognize LUNs over LUN#1 if LUN#0 has the
Data Retention Utility "inv" attribute set. This is because some HBA drivers do not
scan all LUNs on a port if LUN#0 is invisible.
Restrictions on Data Retention Utility volumes
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 324
Database Validator
Database Validator prevents data corruption in an Oracle database by checking Oracle
data validation before an Oracle data block is written on a disk.
■Data Block corruption: This occurs when Oracle data is corrupted by some
intervening software layer and/or hardware components. The RAID storage system
can check the validity of the data block before the Oracle data block is written to disk.
■Data block address corruption: The OS (le system, LVM, Disk driver) might write
blocks to the wrong location. The RAID storage system can check the validity of the
data block address to verify that the Oracle data block is written to the correct
location on disk.
■Protection of Oracle volume: Oracle data les might be overwritten by a non-Oracle
application or by human operation using a command. The RAID storage system can
protect volumes storing Oracle les by preventing the volumes from being modied
by another application or by human error.
Restrictions on Database Validator
■Oracle® tablespace location
●File system-based Oracle les are not supported by Database Validator. All Oracle
database les must be placed on raw volumes (including LVM raw volumes)
directly.
●If host-based striping is used on raw volumes, then the stripe size must be an
exact multiple of the Oracle block size.
●Oracle redo log les (including archive logs) must be on separate volumes with
respect to the data les (including control les). In other words, Oracle redo log
les and the data les must not be mixed on the same LU.
■Restoring Oracle® les
●Before restoring Oracle data les from a backup, data validation might need to be
temporarily turned o for those data les that were backed up prior to the Oracle
checksum being enabled.
Database Validator
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 325
Old blocks can exist on disk without checksum information in them if the database was
running without checksum enabled in the past.
■Oracle® on LVM(VxVM)
●LVM block size must be a multiple of the Oracle block size. The Oracle block size
must be less than or equal to the minimum of the LVM stripe size and the largest
block size at which LVM will not fracture (known as "Logical Track Group" in LVM),
which is 256 KB in LVM.
●When adding new physical volumes (PVs) to a logical volume (LV) to be used as an
Oracle data le, control le, or online log, the data validation should be re-enabled
in order to have HARD checking take eect on those new PVs.
Similarly, in order to have HARD checking no longer performed on PVs that have
been removed from an LV that had previously been used by Oracle, HARD checking
should be explicitly disabled on the device corresponding to the PV.
●If host-based mirroring is used such as LVM mirroring, all component PV mirrors
must be HARD-enabled, otherwise the entire logical volume (LV) is exposed. That
is, if a user takes an unmirrored HARD-enabled LV, then makes it mirrored on the
y without HARD-enabling all sides of the mirror, that entire LV is exposed to data
corruption.
●LVM bad block relocation is not allowed on PVs that are HARD-enabled.
■Oracle® and LVM (VxVM) on HA Cluster Server
●If HA Cluster software writes to LVM metadata at regular intervals to conrm
whether its disks are available or not, change the check area which is set for the
target LU (except management area) by using the "-vs <bsize> SLBA ELBA" option.
Protection parameters and operations
The RAID storage systems have protection checking parameters for each LU, and these
parameters are set through CCI and its command device. CCI supports the following
commands to set and verify the parameters for protection checking for each LU:
■raidvchkset: Sets the protection checking parameter for the specied volumes.
■raidvchkdsp: Shows the protection checking parameter for the specied volumes
based on the CCI conguration denition le.
■raidvchkscan: This command has three dierent uses depending on the options
used with the command.
●Shows the port, target ID, LDEV, and validation checking parameters for the
specied volumes based on the raidscan command.
●Shows the journal volume list setting and information for the journal volume.
●Shows the Copy-on-Write Snapshot pool setting and information for the Copy-on-
Write Snapshot pool.
Protection parameters and operations
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 326
Data Protection facility
The Data Protection Facility permits main operations to volumes that you can see on the
host, and prevents wrong operations. CCI controls protected volumes at the result of
recognition of protection. CCI recognizes only volumes that the host shows. For that
purpose LUN Security is provided for the CCI environment.
The Data Protection Facility ON/OFF is controlled by the security setting for the
command device, as shown in the following table.
Command device setting
Security to be setSecurity
User
authentication
Group
information
acquisition
0 0 0 No security
0 0 1 Only HORCM_DEV allowed1
0 1 0 User authentication required2
0 1 1 User authentication required2
Only HORCM_DEV allowed1
1 0 0 CMD security3
1 0 1 CMD security3
Only HORCM_DEV allowed1
1 1 0 CMD security3
User authentication required2
1 1 1 CMD security3
User authentication required2
Only HORCM_DEV allowed1
Notes:
1. The operation can be performed only for paired logical volumes described at
HORCM_DEV.
2. Only the commands issued by the authorized users can be executed.
3. Only the devices recognizable from the host can be operated
Data Protection facility
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 327
The Data Protection Facility uses an enhanced command device that you dene using
the LUN Manager software (or SNMP). When you dene the command device, the Data
Protection Facility is turned ON or OFF to each command device, which has an attributes
to enable the Data Protection Facility. CCI distinguishes the ON from OFF attribute when
CCI recognizes the command device. The gure given below shows the denition of
protected volumes.
Note: If the command device is set to enable protection mode, there is no
impact on CCI operations. CCI controls pairs under current specication. For
details about the command operations when the Data Protection Facility is
turned ON, see Target commands for protection.
Data Protection Facility specifications
Only the permitted volumes can be registered in horcm.conf. When creating the
horcm.conf le, describe volumes only from the view that the host shows. CCI manages
mirror descriptors (TrueCopy, ShadowImage/MU#0/1/2) as a unit.
The Data Protection Facility has two specications: one must be a volume that you can
see from the host such as the Inquiry tool, and the other must be a mirror descriptor
volume that was registered in horcm.conf. The following table shows the registration
for the mirror descriptor.
Volume
s in
horcm.
conf
Mirror Descriptor in horcm.conf
TrueCopy
ShadowImage
MU#0 MU#1 MU#2
E none E none E none E none
Unkno
wn
--------
/dev/
rdsk/
c0t0d0
permitt
ed
volume
s
- permitt
ed
volume
s
- permitt
ed
volume
s
- permitt
ed
volume
s
-
Data Protection Facility specications
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 328
Volume
s in
horcm.
conf
Mirror Descriptor in horcm.conf
TrueCopy
ShadowImage
MU#0 MU#1 MU#2
E none E none E none E none
Unkno
wn
--------
Legend:
E: Mirror descriptor volume to be registered in horcm.conf.
Unknown: Volumes that own host cannot recognize, even though volumes were
registered in horcm.conf.
■CCI permits operation after the permission command at startup of HORCM. The
target is volume that was registered in the horcm.conf le.
■The permission command is necessary to permit the protected volume at rst. The
permission command compares an identication for volumes of horcm.conf to all
of own host volumes, and the result is registered within HORCM. And HORCM makes
tables for protected volume and permitted volumes from horcm.conf and Inquiry
result. Inquiry result is based on conguration of Data Retention Utility. When
controlling pair volumes, requests to protected volumes are rejected with error code
EX_ENPERM.
■The Data Protection Facility is based on the host side view at the result of Data
Retention Utility. You need to congure Data Retention Utility before CCI operation.
CCI checks Data Retention Utility by Inquiry within CCI.
■The Data Protection Facility can be enabled separately for each command device. If
you want to use protection and non-protection modes in the same storage system at
the same time, you can dene two (or more) command devices: one with protection
ON, one with protection OFF. Protection mode is enabled for the host that has Data
Retention Utility and ON command device.
Examples for configuration and protected volumes
Case (1): Two Hosts (See the gure given below for two host conguration). In protect
mode, Ora2 are rejected to operate the paired volume, because of Unknown for Grp4 on
HOST2.
Examples for conguration and protected volumes
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 329
Case (2): One Host (See the gure given below for one host conguration). In protect
mode, Ora1 and Ora2 are rejected to operate the paired volume, because of Unknown
for Grp2 and Grp4 on HOST1. If HOST1 has a protection OFF command device, then Ora1
and Ora2 are permitted to operate the paired volume.
Note: The Data Protection Facility is implemented by only CCI. CCI needs to
know the protection attribute for the command device whether should be
permitted the operation for paired volume. If HORCM has protection ON
command device at its time, then HORCM checks a permission for a paired
volume.
Examples for conguration and protected volumes
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 330
Operation authority with CMD security enabled
If the CMD security is enabled, you have the operation authority for the LU which meets
both of the following requirements.
■The connection to the host has been recognized when you start CCI.
■The LU is the target of the pair operation specied with MU# which is dened in the
conguration denition le.
For the volumes that you do not have the operation authority, "****" is displayed as the
LDEV#, and "----" is displayed as the status. If you perform the pair operations, CCI rejects
the request with the error code "EX_ENPERM" (pairdisplay is not included).
If you specify 0, 1 2... for the MU#, your operation authority is limited on the LUs for the
local copy program products (ShadowImage, ShadowImage for Mainframe and Copy-on-
Write Snapshot). If you specify h0, h1 or h2 for the MU#, your operation authority is
limited on the LUs for the remote copy operations (TrueCopy, TrueCopy for Mainframe,
TrueCopy Async, Universal Replicator, Universal Replicator for Mainframe, and global-
active device). If you specify nothing for the MU#, you have the operation authority on
MU#0 for the local copy and the remote copy operations.
Operation authority with CMD security enabled
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 331
Target commands for protection
The following commands are controlled by the Data Protection Facility: horctakeover,
paircurchk, paircreate, pairsplit, pairresync, pairvolchk, pairevtwait,
pairsyncwait, raidvchkset, raidvchkdsp, pairdisplay. When the command is
issued to non-permitted volumes, CCI rejects the request with error code "EX_ENPERM"
(pairdisplay is not included).
■The pairdisplay command shows all volumes, so that you can conrm non-
permitted volumes. Non-permitted volumes are shown without LDEV# information.
As shown below, the LDEV# information is " **** " (-CLI is "-").
Example
# pairdisplay -g oradb
Group PairVol(L/R) (Port#,TID,LU-M),Seq#, LDEV#.P/S,Status, Seq#,P-
LDEV# M
oradb oradev1(L) (CL1-D , 3, 0-0) 35013 ****..- -,- -
oradb oradev1(R) (CL1-D , 3, 1-0) 35013 ****..- -,- -
■The raidscan command shows all volumes same as current specication, because it
does not need HORCM_DEV and HORCM_INST on horcm.conf. If you want to know
permitted volumes at raidscan, use raidscan -find. The -find option shows
device le name and storage system information by using internal Inquiry result. You
can use raidscan -find to make horcm.conf, because only permitted volumes are
shown with host side view. Following is an example for HP-UX systems:
Example
# ioscan -fun | grep rdsk | raidscan -find
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV
PRODUCT_ID
/dev/rdsk/c0t3d0 0 F CL1-D 3 0 35013 17 OPEN-3
/dev/rdsk/c0t3d1 0 F CL1-D 3 1 35013 18 OPEN-3
permission command
CCI recognizes permitted volumes at the result of the permission command. The
permission command is the -find inst option of raidscan. This option issues an
inquiry to a specied device le to get Ser# and LDEV# from the RAID storage system,
and checks an identication for volumes of horcm.conf to all of own host volumes, then
stores the result within HORCM of the instance. This permission command is started
by /etc/horcmgr automatically.
Target commands for protection
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 332
The following example shows the relation between the device le and horcm.conf for a
manual operation on an HP-UX system. All volumes of ioscan are permitted.
Example
# ioscan -fun | grep rdsk | raidscan -find inst
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL
LDEV
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013
17
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013
17
New options for security
raidscan -find inst
This option registers the device le name to all mirror descriptors of the LDEV map table
for CCI and permits the matching volumes on horcm.conf in protection mode. It is
started from /etc/horcmgr automatically. You will not normally need to use this option.
This option issues an Inquiry to a device le from the result of STDIN. Then CCI gets Ser#
and LDEV# from the RAID storage system. Subsequently, CCI compares the Inquiry result
to the contents of horcm.conf, and the result is stored within HORCM for the instance.
At the same time CCI shows the result of this option about the relation. This option will
also be terminated to avoid wasteful scanning after registration based on horcm.conf,
because HORCM does not need the registration any more.
Example
# ioscan -fun | grep rdsk | raidscan -find inst
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL
LDEV
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013
17
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013
17
Note: When multiple device les share the same LDEV, the rst device le is
registered to the LDEV map table.
raidscan -find verify [MU#]
This option shows the relation between group on horcm.conf and Device_File
registered to the LDEV map tables from DEVICE_FILE of STDIN.
New options for security
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 333
Example
# ioscan -fun | grep rdsk | raidscan -find verify -fd
DEVICE_FILE Group PairVol Device_File M SERIAL
LDEV
/dev/rdsk/c0t3d0 oradb oradev1 c0t3d0 0 35013
17
/dev/rdsk/c0t3d1 oradb oradev2 Unknown 0 35013
18
/dev/rdsk/c0t3d2 - - - 0 35013
19
Note: It shows shared LDEV among multiple device les, if there is a
dierence between DEVICE_FILE and Device_File. You can also use this option
to the command device that specied non-protection mode. It is used for the
purpose to see the relation between DEVICE_FILE and the group of
horcm.conf.
raidscan -f[d]
This option shows the Device_File that was registered on the group of HORCM, based on
the LDEV (as dened in the local instance conguration denition le).
Example
# raidscan -p cl1-d -fd
Port# ,TargetID#,Lun#..Num(LDEV#....)...P/S, Status,Fence,LDEV#,Device_File
CL1-D , 3, 0...1(17)............SMPL - - -,c0t3d0
CL1-D , 3, 1...1(18)............SMPL - - -,c0t3d1
pairdisplay -f[d]
This option shows the relation between the Device_File and the paired volumes
(protected volumes and permitted volumes), based on the group, even though this
option does not have any relation with protection mode.
Example
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV#
M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18
raidscan -f[d]
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 334
-
oradb oradev1(R) c0t3d1 0 35013 18..S-VOL COPY, 35013 17
-
If either the local or the remote host (instance) has not been shown the Device_File, then
pair operations are rejected (except the local option such as "-l") in protection mode
because of Unknown volume, as shown in the following example.
Example
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV#
M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18
-
oradb oradev1(R) Unknown 0 35013 ****..- -, - - -
Permitting protected volumes
Protection mode needs recognition step to check accessible volumes and the
horcm.conf at the startup of HORCM on protection mode. The protected volumes must
be registered to enable the Data Protection Facility at each startup of HORCM, so that
this registration process is executed automatically by /etc/horcmgr.
With a $HORCMPERM file
The following is executed for registration of permitted volume le ($HORCMPERM le), if
$HORCMPERM le exists and there are permitted volumes. To permit only the volumes
specied, then the volume list must be dened in the $HORCMPERM le.
Naming of $HORCMPERM le on UNIX systems
$HORCMPERM is /etc/horcmperm.conf or /etc/horcmperm*.conf (* = instance
number) by default. For example, on HP-UX systems:
cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst
# The following are an example to permit the LVM Volume groups.
# For MU# 0
vg00 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg00 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
# For MU# 1
vg01 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg01 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
Permitting protected volumes
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 335
Verifying a group for vg01: The following are examples how to verify whether a LVM
volume group is mapped to group (MU#1 for ShadowImage) in the horcm.conf le
correctly.
# export HORCC_MRCF=1
# cat /etc/horcmperm.conf | grep vg01 | raidscan -find verify 1 -fd
OR
# vgdisplay -v /dev/vg01|grep dsk|sed 's/\/*\/dsk\//\/rdsk\//
g'|raidscan -find verify 1 -fd
DEVICE_FILE Group PairVol Device_File M SERIAL
LDEV
/dev/rdsk/c0t3d0 oradb1 oradev1 c0t3d0 1
35013 17
/dev/rdsk/c0t3d1 oradb1 oradev2 c0t3d1 1
35013 18
/dev/rdsk/c0t3d2 oradb oradev3 c0t3d2 1
35013 19
/dev/rdsk/c0t3d3 - - - 1
35013 20
Naming of $HORCMPERM le on Windows systems
$HORCMPERM is %windir%\horcmperm.conf or %windir%\horcmperm*.conf (* =
instance number) by default.
type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst
# The following are an example to permit the DB Volumes.
# Note: a numerical value is interpreted as Harddisk#.
# DB0 For MU# 0
Hd0-10
harddisk12 harddisk13 harddisk17
# DB1 For MU# 1
hd20-23
Verifying a group for DB1: The following is an example of how to verify whether a DB
volume group is mapped to a group (MU#1 for ShadowImage) in the horcm.conf le
correctly.
D:\HORCM\etc> set HORCC_MRCF=1
D:\HORCM\etc> echo hd20-23 | raidscan -find verify 1 -fd
DEVICE_FILE Group PairVol Device_File M SERIAL
LDEV
Harddisk20 oradb1 oradev1 Harddisk20 1 35013
17
Harddisk21 oradb1 oradev2 Harddisk21 1 35013
18
Harddisk22 oradb oradev3 Harddisk22 1 35013
19
With a $HORCMPERM le
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 336
Harddisk23 - - - 1 35013
20
Without a $HORCMPERM file: Commands to run on different operating systems
If NO $HORCMPERM le exists, run a command on the host to permit all volumes on the
host. The following table shows the command to run on each operating system.
System Command
HP-UX echo /dev/rdsk/* /dev/rdisk/* /dev/rcdisk/* | /HORCM/usr/bin/raidscan -
nd inst
Linux ls /dev/sd* | /HORCM/usr/bin/raidscan -nd inst
zLinux ls /dev/sd* /dev/dasd*| /HORCM/usr/bin/raidscan -nd inst
Solaris ls /dev/rdsk/* | /HORCM/usr/bin/raidscan -nd inst
AIX lsdev -C -c disk | grep hdisk | /HORCM/usr/bin/raidscan -nd inst
Tru64 UNIX ls /dev/rdisk/dsk* | /HORCM/usr/bin/raidscan -nd inst
Digital
UNIX
ls /dev/rrz* | /HORCM/usr/bin/raidscan -nd inst
DYNIX/ptx /etc/dumpconf -d | grep sd | /HORCM/usr/bin/raidscan -nd inst
IRIX64 ls /dev/rdsk/*vol /dev/rdsk/*/*vol/* | /HORCM/usr/bin/raidscan -nd inst
OpenVMS /HORCM/usr/bin/raidscan -pi '$1$DGA0-10000 DKA0-10000 DGA0-10000'
-nd inst
Windows X:\HORCM\etc\raidscan.exe -pi $PhysicalDrive -nd inst
Note: This registration process has risk because it is executed automatically
by /etc/horcmgr without judgment for protection mode in order to validate
the -fd option. This registration brings a degradation in horcmstart.sh, but
HORCM daemon has been running as usual, and it will depend on how many
devices a host has. To start faster at HORCM faster in non-protection mode,
create the $HORCMPERM le of "SIZE 0 byte" as a dummy le or to set
HORCMPERM=MGRNOINST. At this time, the -fd option shows Device_File
name as Unknown, and after you can use raidscan -find inst to validate
the -fd option.
Without a $HORCMPERM le: Commands to run on dierent operating systems
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 337
Environment variables
$HORCMPROMOD
This environment variable turns protection mode ON as specied in the following table
depicting the relation between HORCMPROMOD and command device. If your command
device is set for non-protection mode, this parameter sets it to protection mode.
Command Device HORCMPROMOD Mode
Protection mode Don't care Protection mode
Non-protection mode Not specied Non-protection mode
Specied Protection mode
$HORCMPERM
This variable is used to specify the HORCM permission le name. If no le name is
specied, /etc/horcmperm.conf or /etc/horcmperm*.conf (* = instance number) is
the default.
■If a HORCM permission le exists, then /etc/horcmgr executes the following command
to permit the volumes specied.
Example for UNIX systems:
cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst
Example for Windows systems:
type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst
■If no HORCM permission le exists, then /etc/horcmgr executes a built-in command to
permit all volumes of a host. See Without a $HORCMPERM le: Commands to run on
dierent operating systems for examples of commands run on an operating basis.
■/etc/horcmgr does not execute the built-in command if the following is dened for
$HORCMPERM. This is used to execute a system command to permit the volumes
specied from a user's shell script.
HORCMPERM=MGRNOINST.
Determining the protection mode command device
The inquiry page is not changed for a command device with protection mode ON.
Therefore, CCI provides how to nd the protection mode command device. To determine
the currently used command device, use the horcctl -D command. This command
shows the protection mode command device by adding an asterisk (*) to the device le
name.
Environment variables
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 338
Example for HP-UX systems:
# horcctl -D
Current control device = /dev/rdsk/c0t0d0*
- * indicates protection ON.
Determining the protection mode command device
Chapter 7: Data protection operations with CCI
Command Control Interface User and Reference Guide 339
Chapter 8: Examples of using CCI commands
This chapter provides examples of typical tasks performed using CCI commands.
Group version control for mixed storage system
configurations
Before executing each option of a command, CCI checks the facility version of the
storage system internally to verify that the same version is installed on mixed storage
system conguration. If the conguration includes older storage systems (for example,
9900V), this method might not meet the requirements for the mixed storage system
environment, because the older storage system limits the availability enhancements in
later facility versions. If the facility versions of the storage systems are dierent, you
cannot use TagmaStore USP/TagmaStore NSC-specic facility, because CCI applies the
minimum version to all storage systems. To expand the capability for mixed storage
system congurations and avoid problems such as this, CCI supports the following group
version control to manage a version for each group.
■CCI (HORCM daemon) makes a facility version for each group based on a
conguration le at the startup of HORCM.
■In a mixed storage system conguration, if the facility version of the storage systems
(for example, USP V/VM and TagmaStore USP/TagmaStore NSC) is dierent on a
group, CCI will apply the minimum version for each group (see the following gure
showing the denition of the group version).
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 340
LDM volume discovery and flushing for Windows
Windows systems support the Logical Disk Manager (LDM) (such as VxVM), and a logical
drive letter is typically associated with an LDM volume (\Device\HarddiskVolumeX).
Therefore, you cannot know the relationship between LDM volumes and the physical
volumes of the RAID storage system. Therefore, you need to create the CCI conguration
le, and you need to know the relationship that is illustrated in the gure given below.
Volume discovery function
CCI supports the volume discovery function on three levels showing the relationship
between LDM volumes and the physical volumes.
■Physical level: CCI shows the relationship between PhysicalDrive and LDEV by giving
$Physical as a KEY WORD for the discovery.
■LDM volume level: CCI shows the relationship between [LDM volume and
PhysicalDrives] and LDEV by given $Volume as KEY WORD for the discovery.
■Drive letter level: CCI shows the relationship between [Drive letter and LDM volume
and PhysicalDrives] and LDEV by given $LETALL as KEY WORD for the discovery.
The KEY WORD ($Physical, $Volume, $LETALL) can be used with raidscan -find,
inqraid, mkconf commands.
In Windows, DOS devices (for example, C:, Volume{}) are linked to a Device Object Name
(\Device\...). CCI indicates as the following by abbreviating a long Device Object Name.
■Device Object Name of the LDM for Windows:
\Device\HarddiskVolumeX for Partition : \VolX\DskY
LDM volume discovery and ushing for Windows
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 341
DskY shows that VolX are congured through HarddiskY.
■Device Object Name of the LDM for Windows 2003/2000:
\Device\HarddiskDmVolumes\ ... \VolumeX for spanned volume : \DmsX\DskYs
\Device\HarddiskDmVolumes\ ... \StripeX for striped volume : \DmtX\DskYs
\Device\HarddiskDmVolumes\ ... \RaidX for Raid-5 volume : \DmrX\DskYs
DskYs shows that DmsX(DmtX,Dmr) volumes are congured through bundling multiple
HarddiskY1 Y2….
■Device Object Name of the PhysicalDrive for Windows:
\Device\HarddiskX\DR?? : HarddiskX
You can determine the relationship between LDM volumes and LDEV by given a KEY
WORD to the inqraid command.
Example 1
inqraid $LETALL -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
D:\Vol2\Dsk4 - - - - - - - DDRS-34560D
E:\Vol44\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
F:\Vol45\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
G:\Dmt1\Dsk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3
G:\Dmt1\Dsk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3
G:\Dmt1\Dsk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3
Example 2
inqraid $Volume -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
\Vol2\Dsk4 - - - - - - - DDRS-34560D
\Vol44\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
\Vol45\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
\Dmt1\Dsk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3
\Dmt1\Dsk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3
\Dmt1\Dsk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3
Example 3
inqraid $Phy -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
Harddisk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
Harddisk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3
Harddisk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3
Volume discovery function
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 342
Harddisk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3
Harddisk4 - - - - - - - DDRS-34560D
■Device Object Name of the Partition for Windows NT
●\Device\HarddiskX\PartitionY : \DskX\pY
■Device Object Name of the PhysicalDrive for Windows NT
●\Device\HarddiskX\Partition0 : HarddiskX
Example 4
inqraid $LETALL -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
D:\Dsk0\p1 - - - - - - - DDRS-34560D
E:\Dsk1\p1 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
F:\Dsk1\p2 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3
Example 5
inqraid $Phy -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
Harddisk0 - - - - - - - DDRS-34560D
Harddisk1 CL2-K 61456 194 - s/s/ss 0005 1:01-11 OPEN-3
You want to know the relationship between LDM volumes and a group of the
conguration les, and then nd a group of the conguration le by giving a KEY WORD
to raidscan -find verify command.
Example 6
raidscan -pi $LETALL -find verify
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL
LDEV
E:\Vol44\Dsk0 ORA ORA_000 CL2-K 7 2 - 61456
194
F:\Vol45\Dsk0 ORA ORA_000 CL2-K 7 2 - 61456
194
G:\Dmt1\Dsk1 ORB ORB_000 CL2-K 7 4 - 61456
256
G:\Dmt1\Dsk2 ORB ORB_001 CL2-K 7 5 - 61456
257
G:\Dmt1\Dsk3 ORB ORB_002 CL2-K 7 6 - 61456
258
Example 7
raidscan -pi $LETALL -find
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
E:\Vol44\Dsk0 0 F CL2-K 7 2 61456 194 OPEN-3
F:\Vol45\Dsk0 0 F CL2-K 7 2 61456 194 OPEN-3
Volume discovery function
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 343
G:\Dmt1\Dsk1 0 F CL2-K 7 4 61456 256 OPEN-3
G:\Dmt1\Dsk2 0 F CL2-K 7 5 61456 257 OPEN-3
G:\Dmt1\Dsk3 0 F CL2-K 7 5 61456 258 OPEN-3
Mountvol attached to Windows 2012/2008/2003/2000 systems
Pay attention to the mountvol /D command attached to a Windows system, such that it
does not ush the system buer associated with the specied logical drive. The
mountvol command shows the volume mounted as Volume{guid} as follows:
Example
mountvol
Creates, deletes, or lists a volume mount point.
.
.
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
\\?\Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}\
G:\
\\?\Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}\
F:\
You can determine what \\?\Volume{guid}\ is congured, as follows:
Example
inqraid $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
\Vol46\Dsk1 CL2-K 61456 193 - S/s/ss 0004 1:01-10 OPEN-3
raidscan -pi $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -find
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
\Vol46\Dsk1 0 F CL2-K 7 1 61456 193 OPEN-3
System buffer flushing function
The logical drive to be ushed can be specied by the following two methods. One
method is that the logical drive (for example, G:\hd1 drive, as below) is specied
immediately, but this method must know about the logical drive corresponding to a
group before executing the sync command. Also the volume is mounting by a directory
and this method requires nding its volume name. To solve such a complication, CCI
supports a method that ushes the system buer associated with a logical drive through
nding a volume{guid} corresponding to a group of the conguration le. This method
does not depend on mounted point, so that it is possible to ush the volume mounted
by a directory. This method is supported to be specied a group to the raidscan -find
sync command. The gure given below shows the LDM volume ushing operation.
Mountvol attached to Windows 2012/2008/2003/2000 systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 344
The following example ushes the system buer associated with the ORB group through
$Volume.
Example
raidscan -pi $Volume -find sync -g ORB
[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d5
8d69-00c00d003b1e}
[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5
8d69-00c00d003b1e}
[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5
8d69-00c00d003b1e}
The following example ushes the system buer associated with all groups for the local
instance.
Example
raidscan -pi $Volume -find sync
[SYNC] : ORA ORA_000[-] -> \Vol44\Dsk0 : Volume{56e4954a-28d5
4824-a408-3ff9a6521e5d}
[SYNC] : ORA ORA_000[-] -> \Vol45\Dsk0 : Volume{56e4954a-28d5
4824-a408-3ff9a6521e5e}
[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6
11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6
11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6
11d5-8d69-00c00d003b1e}
System buer ushing function
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 345
Note: Windows NT does not support the LDM volume, so specify $LETALL
instead of $Volume.
Oine backup using raidscan -find sync for Windows le system:
The raidscan -find sync command ushes the system buer associated with a
logical drive through nding a Volume{guid} corresponding to a group of the
conguration le, without using the -x mount and -x umount commands. The
following examples are for group ORB.
P-VOL Side S-VOL Side
Close all logical drives on the P-VOL by
application.
■Flush the system buer for P-VOL
using raidscan -pi $Volume -nd
sync -g ORB.
■Split the paired volume using
pairsplit -g ORB with r/w mode.
■Open all logical drives on the P-VOL
by application.
■Resynchronize the paired volume
using pairresync -g ORB.
■Flush the system buer for NEW S-VOL
data using raidscan -pi $Volume -nd sync
-g ORB.
■Back up the S-VOL data.
■Flush the system buer for S-VOL
updates using raidscan -pi $Volume -nd
sync -g ORB when the backup is nished.
Online backup using raidscan -find sync for Windows le system:
The raidscan -find sync command ushes the system buer associated with a
logical drive through nding a Volume{guid} corresponding to a group of the
conguration le, without using the -x mount and -x umount commands. The
following examples are for group ORB.
P-VOL Side S-VOL Side
Freeze DB on opening P-VOL by
application.
■Flush the system buer for P-VOL
using raidscan -pi $Volume -nd
sync -g ORB.
■Splits the paired volume using
pairsplit -g ORB with r/w mode.
■Unfreeze DB on opening P-VOL by
application.
■Resynchronize the paired volume
using pairresync -g ORB.
■Flush the system buer for NEW S-VOL data
using raidscan -pi $Volume -nd sync -g
ORB.
■Back up the S-VOL data.
■Flush the system buer for S-VOL updates
using raidscan -pi $Volume -nd sync -g
ORB when the backup is nished.
System buer ushing function
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 346
Oine backup using raidscan -nd sync for Windows NT le system:
The raidscan -find sync command ushes the system buer through nding a
logical drive corresponding to a group of the conguration le, without using the -x
mount and -x umount commands. The following examples are for group ORB.
P-VOL Side S-VOL Side
Close all logical drives on the P-VOL by
application.
■Flush the system buer for P-VOL
using raidscan -pi $LETALL -nd sync
-g ORB.
■Split the paired volume using
pairsplit -g ORB with r/w mode.
■Open all logical drives on the P-VOL
by application.
■Resynchronize the paired volume
using pairresync -g ORB.
■Back up the S-VOL data.
■Flush the system buer for S-VOL
updates using raidscan -pi $LETALL -nd
sync -g ORB when the backup is nished.
Online backup using raidscan -find sync for Windows NT le system:
The raidscan -find sync command ushes the system buer through nding a
logical drive corresponding to a group of the conguration le, without using the -x
mount and -x umount commands. The following examples are for group ORB.
P-VOL Side S-VOL Side
Freeze DB on opening P-VOL by
application.
■Flush the system buer for P-VOL
using the raidscan -pi $LETALL -
nd sync -g ORB.
■Splits the paired volume using
pairsplit -g ORB with r/w mode.
■Unfreeze DB on opening P-VOL by
application.
■Resynchronize the paired volume
using pairresync -g ORB.
■Back up the S-VOL data.
■Flush the system buer for S-VOL updates
using raidscan -pi $LETALL -nd sync -g ORB
when the backup is nished.
System buer ushing function
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 347
Note:
■P-VOL side must stop the WRITE IO to the logical drive corresponding to a
[-g name] before issuing the raidscan -find sync command.
■S-VOL side must close the logical drive corresponding to a [-g name]
before issuing the raidscan -find sync command.
Special facilities for Windows systems
CCI provides the following special facilities for Windows systems:
■Signature changing facility for Windows systems (on page 348)
■GPT disk for Windows (on page 351)
Signature changing facility for Windows systems
Consider the following Microsoft Cluster Server (MSCS) conguration in which a MSCS P-
VOL is shared from MSCS Node1 and Node2, and the copied volume of S-VOL is used for
backup on Node2. If the Node2 has reboot on standby state, then MSCS of Node2 has a
problem to assign drive letter of S-VOL with previous P-VOL drive letter. This problem will
happen on Node2 on MSCS environment as shown in the following gure. The
conditions are:
■Node1 is active.
■Node2 is standby state where P-VOL on Node2 is hidden by MSCS, and reboots the
Node2.
MSCS on Node2 will misunderstand the S-VOL as MSCS cluster resource, because the
signature of S-VOL and P-VOL is the same due to copied. The reason is that MSCS cluster
resources are managed with the signature only. Therefore S-VOL of Node2 will unable to
backup so that MSCS of Node2 carry away the S-VOL. This is a problem of MSCS service
because Windows system does change the signature through reboot if the same
signature is detected on NO MSCS service. MSCS will not accommodate LUNs with
duplicate signatures and partition layout. The best way to avoid such problems is to
transport to another host outside the cluster, but this enforces to set up a backup server,
so CCI supports a facility to put back the signature as a second way.
Special facilities for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 348
The signature can be changed by using the dumpcfg.exe command attached to
Windows resource kits, but if the S-VOL is created with the Noread option and the
system is rebooted, then the dumpcfg.exe command will fail to change the signature,
because the system does not know the signature and volume layout information for S-
VOL.
CCI adopts the following way with this point in view:
■You must save the signature and volume layout information to the system disk by
using the inqraid -gvinf command, after an S-VOL has set the signature and new
partition by the Windows disk management.
■You can put back the signature by setting the signature and volume layout
information to an S-VOL that was saved to the system disk by using the inqraid -
svinf command, after splitting the S-VOL. If the S-VOL is created with the Noread
option and the system is rebooted, then the system cannot create a device object
(\Device\HarddiskVolume#) and Volume{guid} for S-VOL, but the -svinf option will
create a Device object (\Device\HarddiskVolume#) and Volume{guid} without using
the Windows disk management.
Signature changing facility for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 349
Note: The Cluster Disk Driver does not allow using the Noread volume as
[Device is not ready] at the boot time, since the Cluster Disk Driver is a Non-
Plug and Play Driver. Verify this situation using the inqraid command as
follows:
inqraid $Phy -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group
PRODUCT_ID
Harddisk0 - - - - - - - -
Harddisk1 - - - - - - - -
In this case, do the following to disable the Cluster Disk Driver:
1. In the Computer Management window, double-click System Tools, and
then click Device Manager.
2. On the View menu, click Show Hidden Devices. Non-Plug and Play
Drivers appear in the list in the right pane.
3. Open Non-Plug and Play Drivers, right-click Cluster Disk, and then click
Disable. When prompted to conrm whether to disable the cluster disk,
click Yes. When prompted to restart the computer, click Yes.
4. Verify that you can see the Noread volume using inqraid command as
follows.
inqraid $Phy -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID
R:Group PRODUCT_ID
Harddisk0 CL2-K 61456 194 - s/S/ss 0004 1:01-
10 OPEN-3
Harddisk1 CL2-K 61456 256 - s/S/ss 0005 1:01-
11 OPEN-3
5. After starting up CCI and splitting the S-VOL, put back the signature by
using the inqraid -svinf command.
6. Again, in the Computer Management window, enable the Cluster Disk
Driver, and restart the computer.
Signature changing facility for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 350
GPT disk for Windows
Windows supports the basic disk called GPT disk using GUID partition instead of the
Signature. The GPT disk also can be used as an S-VOL of ShadowImage. Therefore, CCI
supports saving/restoring the GUID DiskId of the GPT Basic disk to the inqraid
command.
■gvinfex option (Windows 2012 only):
This option retrieves the LUN signature and volume layout information by way of a
raw device le provided via STDIN or arguments, and saves it in a system disk le with
the following format:
\WindowsDirectory\VOLssss_llll.ini
where
ssss = serial#
llll = LDEV#
Normally, this option is used to save the Disk signature/GUID DiskId and volume
layout information once, after it has been written on a potential (and before its
paircreate). You do not need to directly view these host les.
For example, saves the volume information for all physical drives:
Example
D:\HORCM\etc>inqraid $Phys -gvinfex -CLI
\\.\PhysicalDrive10:
# Harddisk10 -> [VOL61459_448_DA7C0D91] [OPEN-V ]
\\.\PhysicalDrive11:
# Harddisk11 -> [VOL61459_449_D4CB5F17-2ADC-4FEE-8650
D3628379E8F5] [OPEN-V ]
\\.\PhysicalDrive12:
# Harddisk12 -> [VOL61459_450_9ABDCB73-3BA1-4048-9E94
22E3798C3B61] [OPEN-V ]
■-svinfex[=PTN] option (Windows 2003 only):
This option writes LUN signature/GUID DiskId and volume layout information (that
had previously been saved in a system disk le) by way of a raw device le provided
via STDIN or arguments.
This option gets the serial# and LDEV# of the RAID storage system for the target
device using SCSI Inquiry, and writes the signature/GUID DiskId and volume layout
information from the VOLssss_llll.ini le to the target device.
This option will work correctly (even if Harddisk# changes due to conguration
changes) because the signature/GUID DiskId and volume layout information is
associated the array serial# and LDEV# (not Harddisk#).
GPT disk for Windows
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 351
■[=PTN]:
This option species a string pattern usable to select only the pertinent output lines
being provide from STDIN. If used as shown, only the pairdisplay output lines
containing Harddisk would be used to cause signature writing.
Example
D:\HORCM\etc>pairdisplay -l -fd -g URA | inqraid -svinfex=Harddisk
[VOL61459_448_DA7C0D91] -> Harddisk10 [OPEN-V ]
[VOL61459_449_D4CB5F17-2ADC-4FEE-8650-D3628379E8F5] ->
Harddisk11 [OPEN-V ]
[VOL61459_450_9ABDCB73-3BA1-4048-9E94-22E3798C3B61] ->
Harddisk12 [OPEN-V ]
■-gplbaex option (Windows 2012/2008 only):
This option is used for displaying usable LBA on a Physical drive in units of 512 bytes,
and is used to specify [slba] [elba] options for raidvchkset command.
Example
C:\HORCM\Tool>inqraid -CLI -gplbaex hd10,13
Harddisk10 : SLBA = 0x0000003f ELBA = 0x013fe5d9 PCNT = 1 [OPEN-V
]
Harddisk11 : SLBA = 0x00000022 ELBA = 0x013fffdf PCNT = 2 [OPEN-V
]
Harddisk12 : SLBA = 0x00000022 ELBA = 0x013fffdf PCNT = 3 [OPEN-V
]
SLBA
Displays usable starting LBA in units of 512 bytes
ELBA
Displays usable ending LBA (ELBA -1) in units of 512 bytes
PCNT
Displays the number of partitions
Directory mount facility for Windows systems
The attached mountvol command into Windows supports the directory mount, but it
does not support the directory mount function that ushes the system buer associated
to a logical drive such as in UNIX systems. The directory mount structure on Windows is
only symbolical link between a directory and Volume{guid}, illustrated in the gure given
below. As such, CCI supports the function to discover the mounted volumes by a
directory, and supports the operation to mount/unmount with the subcommand option.
Directory mount facility for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 352
Volume discovery for directory mounted volume:
CCI can discover the directory mounted volume by using $LETALL that shows the
relationship between logical drive and the physical volumes. The KEY WORD
($LETALL)can also be used with the raidscan -find and mkconf commands.
Example
D:\HORCM\etc>inqraid $LETALL -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
D:\Vol2\Dsk7 - - - - - - - DDRS-34560D
D:\hd1\Vol8\Dsk0 CL2-F 61459 448 - s/s/ss 0005 1:01-01 OPEN-3
D:\hd2\Vol9\Dsk1 CL2-F 61459 449 - s/s/ss 0005 1:01-01 OPEN-3
G:\Dms1\Dsk2 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3
G:\Dms1\Dsk3 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3
G:\Dms1\Dsk4 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3
Subcommand for directory mounted volume:
CCI supports the directory mount with the -x mount,-x unmount,-x sync option so
that the directory mount can be used to mount/unmount the S-VOL.
Directory mount facility for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 353
Mount and Sync used Volume{GUID} for Windows:
CCI supports the mountcommand option specied in the device object name, such as
\Device\Harddiskvolume X . Windows changes the device number for the device
object name after recovering from a failure of the PhysicalDrive. As a result, the
mountcommand specied in the device object name might fail. Therefore, CCI supports a
mount command option that species a Volume{GUID} as well as the device object
name.
■Mount
●The mount command option species a Volume{GUID} as well as the device object
name.
●If a Volume{GUID} is specied, then it is executed by converting a Volume{GUID} to
a device object name.
●Discover the Volume{GUID}s by using inqraid $Volu -fv command option.
Example
C:\HORCM\etc>inqraid -CLI $Vol -fv
DEVICE_FILE PORT SERIAL LDEV
CTG H/M/12 SSID R:Group PRODUCT_ID
Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}\Vol3\Dsk0 CL2-D
62496 256 - - - - OPEN-3-CVS-CM
●[ Mount used DeneDosDevice() ]
Note: This might forcibly dismount the mounted volume due to LOG-
OFF of Windows. For example:
Example
C:\HORCM\etc>raidscan -x mount E: Volume{cec25efe-d3b8-11d4-aead-
00c00d003b1e}
E: <+> HarddiskVolume3
●[ Mount used Directory mount ]
Note: This prevents the forcible removal of a volume due to LOG-OFF
of Windows. For example:
Example
C:\HORCM\etc>raidscan -x mount E:\ Volume{cec25efe-d3b8-11d4-aead-
00c00d003b1e}
E:\ <+> HarddiskVolume3
Directory mount facility for Windows systems
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 354
■sync
●The synccommand option will also be able to specify a Volume{GUID} as well as
the device object name.
●If a Volume{GUID} is specied, then it is executed by converting a Volume{GUID} to
a device object name.
Example
C:\HORCM\etc>raidscan -x sync Volume{cec25efe-d3b8-11d4-aead-
00c00d003b1e}
[SYNC] Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}
Host group control
The RAID storage systems have the dened host group in the port and can allocate a
host LU for every host group. CCI does not use this host LU, and species an absolute
LUN in the port. To eliminate confusion that LUN of the CCI notation does not
correspond to LUN on the host view and Storage Navigator, CCI supports specifying a
host group and LUN on the host view.
Specifying a host group
(1) Dening the formats
The addition of arguments for the host group to the raidscan command and the
conguration le means that it is not compatible with conventional CLI. Therefore, CCI
provides a way to support CLI by specifying a host group in the port strings as follows.
■CL1-A-GRP# (GRP# can be up to 127)
Specifying the host group for the raidscan command:
raidscan -p CL1-A-5
Specifying the host group for the conguration le:
#dev_group dev_name port# TargetID LU# MU#
ORA ORA_000 CL2-D-1 4 1 0
ORA ORA_001 CL2-D-1 4 2 0
If the port including a host group is specied to the port name, then a maximum of 255
LUNs can be specied.
(2) Speciable port strings
As a result, CCI supports four kinds of forms for the port name.
■Specifying the port name without a host group
CL1-A
Host group control
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 355
CL1-An where n: unit ID for multiple RAID
■Specifying the port name with a host group
CL1-A-g where g: host group
CL1-An-g where n-g: host group=g on CL1-A in unit ID=n
Commands and options including a host group
(1) Speciable command for host group
The following commands can specify a host group with the port strings:
■raidscan -p <port#>, raidar -p <port#>, raidvchkscan -p <port#>
# raidscan -p CL2-D-1
PORT# /ALPA/C,TID#,LU#.Num(LDEV#....)...P/S, Status,Fence,LDEV#,P-Seq#,P-
LDEV#
CL2-D-1 /da/ 0, 4, 0.1(256)...........SMPL ---- ------ ----, ----- ---
-
CL2-D-1 /da/ 0, 4, 1.1(257)...........SMPL ---- ------ ----, ----- ---
-
CL2-D-1 /da/ 0, 4, 2.1(258)...........SMPL ---- ------ ----, ----- ---
-
(2) Command option including a host group
CCI supports new option for the following commands in order to show a LUN on the host
view by nding a host group via the specied device.
■raidscan -pdg <device>, raidar -pdg <device>, raidvchkscan -pdg <device>
# raidscan -pdg /dev/rdsk/c57t4d1
PORT# /ALPA/C,TID#,LU#.Num(LDEV#....)...P/S, Status,Fence,LDEV#,P-Seq#,P-
LDEV#
CL2-D-1 /da/ 0, 4, 0.1(256)...........SMPL ---- ------ ----, ----- ---
-
CL2-D-1 /da/ 0, 4, 1.1(257)...........SMPL ---- ------ ----, ----- ---
-
CL2-D-1 /da/ 0, 4, 2.1(258)...........SMPL ---- ------ ----, ----- ---
-
Specified device(hgrp=1) is LDEV# 0257
■raidscan -ndg
# ls /dev/rdsk/c57* | raidscan -findg
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV
PRODUCT_ID
/dev/rdsk/c57t4d0 0 F CL2-D-1 4 0 62500 256 OPEN3-
CVS-CM
/dev/rdsk/c57t4d1 0 F CL2-D-1 4 1 62500 257 OPEN3-CVS
/dev/rdsk/c57t4d2 0 F CL2-D-1 4 2 62500 258 OPEN3-CVS
Commands and options including a host group
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 356
■raidscan -ndg conf, mkconf -gg
# ls /dev/rdsk/c57* | raidscan -findg conf 0 -g ORA
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
# /dev/rdsk/c57t4d1 SER = 62500 LDEV = 257 [ FIBRE FCTBL = 4 ]
ORA ORA_000 CL2-D-1 4 1 0
# /dev/rdsk/c57t4d2 SER = 62500 LDEV = 258 [ FIBRE FCTBL = 4 ]
ORA ORA_001 CL2-D-1 4 2 0
■inqraid -fg
# ls /dev/rdsk/c57* | ./inqraid -CLI -fg
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group
PRODUCT_ID
c57t4d0 CL2-D-1 62500 256 - - - - OPEN-3-
CVS-CM
c57t4d1 CL2-D-1 62500 257 - s/P/ss 0005 1:01-02 OPEN-3-
CVS
c57t4d2 CL2-D-1 62500 258 - s/P/ss 0005 1:01-02 OPEN-3-
CVS
Using CCI SLPR security
The Virtual Partition Manager feature of the RAID storage systems (USP V/VM and
TagmaStore USP/TagmaStore NSC) supports storage logical partitioning (SLPR), a feature
that partitions the ports and volumes of the RAID storage system. If CCI does not have
SLPR security, then it can operate the target volumes crossing SLPR through the
command device. The purpose of CCI SLPR security is to prevent CCI from operating the
volumes on another SLPR (SLPR#N) through the command device from the SLPR
(SLPR#M) that is assigned to its Host. You can use CCI SLPR Security by dening the
command device through the Virtual Partition Manager feature, so that CCI can protect
the target volume.
The following example represents the SLPR protection facility. The gure given below
shows an example of protection of the command device that has the SLPR attribute.
Using CCI SLPR security
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 357
Legend:
SLPR
Split of storage
SLPR#M
Split number M of storage
Specifying the SLPR protection facility
When you want to access certain SLPRs on a single Host, use the CCI protection facility so
that the Host can access multiple SLPRs through a single command device. The following
outline reviews the setup tasks for the SLPR protection facility.
Procedure
1. Setting SLPR on the command device: The command device has an SLPR number
and an associated bitmap so you can set multiple SLPRs. You accomplish this by
sharing a command device (using ports connected to dierent SLPRs) by setting the
command device through SLPR#0 (called Storage Administrator) on Storage
Navigator.
For example, if the command device is shared with the port on SLPR#1 and SLPR#2,
then the command device will automatically set the bitmap corresponding to
SLPR#1 and SLPR#2.
2. Testing SLPR: CCI veries whether or not the command device can access a target
within SLPR. So, if the command device belongs to SLPR#0, or CCI has no SLPR
function, then the SLPR protection is ignored.
However, if the command device is shared with the port on SLPR#1 and SLPR#2, CCI
allows you to operate the volume on SLPR#1 and SLPR#2.
Specifying the SLPR protection facility
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 358
3. Rejecting commands: If access is denied on the specied port (or target volume),
CCI rejects the following commands and outputs an error code, EX_ESPERM:
■horctakeover, paircurchk, paircreate, pairsplit, pairresync,
pairvolchk, pairevtwait, pairsyncwait
■raidscan (except -find verify, -find inst), raidar, pairdisplay
■raidvchkset, raidvchkscan (except -v jnl), raidvchkdsp
[EX_ESPERM] Permission denied with the SLPR
[Cause ] : A specified command device does not have a
permission to access other SLPR.
[Action] : Please make the SLPR so that the target port and
the command device belongs to the same SLPR.
SLPR configuration examples
Single host
The gure given below for SLPR conguration on a single host provides an example of
when control is denied to the paircreate and raidscan commands in the following
cases:
■The volume described on RMINST1 is dierent from the SLPR of the command device,
so the paircreate command cannot control the paired volume.
■The specied port is dierent from the SLPR of the command device, so the
raidscan -p CL3-A command cannot scan any ports that are dened as SLPR#N.
To operate SLPR#N, assign the command device. If RMINST1 has been assigned to a
command device for SLPR#N, the paircreate command is permitted. However, the
raidscan -p CL3-A command (via RMINST0) is unable to scan a port, because the
specied port is dierent than the SLPR of the command device. In this case, -p CL3-A
must be operated via RMINST1, as shown in the following example for operation across
SLPRs using two command devices on a single host.
SLPR conguration examples
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 359
To operate SLPR#N, share the command device. If RMINST1 has a shared command
device for SLPR#N, the paircreate command is permitted. Additionally, the raidscan
-p CL3-A command (via RMINST0), is permitted to scan a port, because the shared
command device has the Bitmap settings SLPR#M and SLPR#N.
See the following example for operation across SLPRs using a shared command device
on a single host.
Dual Hosts
In the following example for SLPR conguration on dual hosts, the paircreate
command is unable to operate the paired volume because the volume described on
HostB is dierent than the SLPR of the command device. Also, the raidscan -p CL3-A
command (via both Hosts), is unable to scan a port because the specied port is
dierent than the SLPR of the command device.
Dual Hosts
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 360
To operate SLPR#N, assign the command device. If HostB has a command device for
SLPR#N, the paircreate command is permitted. However, the raidscan -p CL3-A
command via HostA is unable to scan a port because the specied port is dierent than
the SLPR of the command device. In this case, raidscan -p CL3-A command must be
operated via HostB.
See the following example for operation across SLPRs using two command devices on
dual hosts.
To operate SLPR#N, share the command device. If HostB has a shared command
device for SLPR#N, the paircreate command is permitted. Also, the raidscan -p
CL3-A command (via HostA), is allowed to scan a port because the shared command
device has the Bitmap settings SLPR#M and SLPR#N.
See the following example for operating SLPR#N by sharing the command device.
Dual Hosts
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 361
TrueCopy using dual hosts
In the following example, the pair-operation command (except the -l option)
determines whether the operation for paired volumes should be permitted at a remote
site. The result is that the paircreate command is not allowed to operate the paired
volume, because the volume described on HostB diers from the SLPR of the command
device. Also, the raidscan -p CL3-A command (on HostB) is not allowed to scan a
port.
Dual Hosts
Chapter 8: Examples of using CCI commands
Command Control Interface User and Reference Guide 362
Chapter 9: Troubleshooting
This chapter provides troubleshooting information for CCI.
General troubleshooting
If you have a problem with the CCI software, rst make sure that the problem is not
being caused by the UNIX/PC server hardware or software, and try restarting the server.
Problem Recommended action
Deprecated SCSI
ioctl
The following
message is
output to syslog
le(/var/log/
messages) with
every ioctl():
program
horcmgr is
using a
deprecated
SCSI ioctl,
please
convert it to
SG_IO
CCI currently uses the ioctl(SCSI_IOCTL_SEND_COMMAND) for
sending the control command to the command device. However, in
RHEL 4.0 using kernel 2.6.9.xx, the following message is output to
syslog le(/var/log/messages) with every ioctl():
program horcmgr is using a deprecated SCSI ioctl, please
convert it to SG_IO
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 363
Problem Recommended action
This can originate from the following kernel code in drivers/scsi/
scsi_ioctl.c as way of warning that ioctl(SCSI_IOCTL_…) of kernel
2.6.9.xx does not properly handle an error of the HBA driver.
---------------------------------------------------------------
-------
/* Check for deprecated ioctls ... all the ioctls that
do not follow
the new unique numbering scheme are deprecated */
switch (cmd) {
case SCSI_IOCTL_SEND_COMMAND:
case SCSI_IOCTL_TEST_UNIT_READY:
case SCSI_IOCTL_BENCHMARK_COMMAND:
case SCSI_IOCTL_SYNC:
case SCSI_IOCTL_START_UNIT:
case SCSI_IOCTL_STOP_UNIT:
printk(KERN_WARNING "program %s is using a
deprecated SCSI "
"ioctl, please convert it to SG_IO\n",
current->comm);
---------------------------------------------------------------
------
General troubleshooting
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 364
Problem Recommended action
Thus, CCI supports a way to change to the ioctl(SG_IO) automatically,
if Linux kernel supports the ioctl(SG_IO) for horcmgr and inqraid
command. However, CCI might encounter Linux kernel that does
not support the ioctl(SG_IO) fully, so CCI also supports by dening
either following environment variable or "/HORCM/etc/
USE_OLD_IOCTL" le(size=0) that uses the
ioctl(SCSI_IOCTL_SEND_COMMAND) forcibly. For example:
export USE_OLD_IOCTL=1
horcmstart.sh 10
HORCM/etc:
-rw-r--r-- 1 root root 0 Nov 11 11:12 USE_OLD_IOCTL
-r--r--r-- 1 root sys 32651 Nov 10 20:02 horcm.conf
-r-xr--r-- 1 root sys 282713 Nov 10 20:02 horcmgr
CCI cannot be
started because
horcmstart
command fails
If you have changed the conguration denition le settings: make
sure that the conguration denition le you changed is correct.
If you have changed the settings of the storage system: make sure
that the settings you changed are correct, and if necessary, change
the conguration denition le settings.
Even if there are no problems in these les and settings, but if you
cannot run CCI, get all log les under the specied directory by
HORCM_LOG (the default setting: /horcm/log/), and then contact
customer support.
The following
messages are
output to the
standard error
output with
every command
I/O:
These messages are output if the path for the PA-RISC version
shared library (libcl.sl) is not set when you use CCI on HP-UX (IA64).
Set the path of the libcl.sl to the LD_PRELOAD environment variable.
Example: # export LD_PRELOAD=/path/libcl.sl
Enter the absolute path for specifying the directory where libcl.sl is
stored into path.
General troubleshooting
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 365
Problem Recommended action
"/usr/lib/
dld.sl:
Can't
shl_load() a
library
containing
Thread Local
Storage: /us
r/lib/
libcl.sl"
"/usr/lib/
dld.sl: Exec
format
error"
When you
attempt to
remove RM
Shadow Copy
Provider, the
installer displays
a message
indicating that a
le cannot be
deleted because
it is used by
another
program.
Perform the following steps to delete the le:
1. Check the information about the program that is using the le
indicated by the installer.
2. Stop the removal of RM Shadow Copy Provider.
3. Close the program you found out in step 1.
4. Try to remove RM Shadow Copy Provider again.
5. Repeat steps 1 through 4 until you can remove RM Shadow
Copy Provider successfully.
Operational notes and restrictions for CCI operations
For maintenance of volumes used by CCI and the Hitachi Vantara features it supports, if
a volume failure occurs, it is important to nd the failure in the paired volumes, recover
the volumes, and continue operation on the original system. When a CCI (HORCM) or
Hitachi Vantara feature failure is detected, please collect the data in the error log le and
trace data (all les in HORCM_LOG directory), and report the failure to your Hitachi
Vantara representative.
Operational notes and restrictions for CCI operations
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 366
Items Notes and restrictions
Startup
restrictions
When the server starts up, sometimes a volume group (VG) is
activated by the LVM, or a le system is mounted automatically,
and the host writes to the S-VOL. When this happens, if the S-VOL
does not permit writing, data cannot be written and the operation
fails. To avoid this failure, change the S-VOL to PSUS (R/W enable)
or to the SMPL state and restart the server.
Hot standby
operations
Note the following when executing hot standby operations using
industry-standard failover products (for example, MC/
ServiceGuard, HACMP, FirstWatch®) and TrueCopy/ TrueCopy
Async/ Universal Replicator.
■Do not split a single volume using partitions and share it
among dierent server programs. If you do so, the takeover
command is executed for the volume when failover of a server
program happens, and that might aect other servers that
share the volume.
■If you are using the LVM, do not create LDEVs for dierent LVM
within the same volume. If you do so, the takeover command is
executed for the volume when failover of a server program
happens, and that might aect other servers that share the
volume.
Coexistence of
LVM mirror and
TrueCopy
When the LVM mirror and TrueCopy volumes are used together,
the LVM mirror handles write errors and changes the volumes.
Thus, the fence level of the volumes used by the LVM mirror must
be set to data.
Using paired
volume in a single
host
When constructing paired volume in a single host, it is necessary
to activate two or more CCI instances. To activate two or more CCI
instances, instance numbers must be assigned using the
environment variable HORCMINST. The HORCM and TrueCopy/
ShadowImage commands must possess this environment
variable.
A conguration denition le and a log directory is set for each
instance. For sharing command devices over 17 instances, use LU
path among the storage system ports to share the command
devices.
Sharing volumes
in a hot standby
conguration
When paired volume is used for the disk shared by the hosts in
hot standby conguration using HA software, use the primary
volume as the shared disk and describe the corresponding hosts
using the paired volume in the conguration denition le as
shown below. In the HA conguration, if a TrueCopy command
issued by host C fails in host B (because host B has gone down
and/or IO_ERROR of the command device), host A is connected
and the command execution is retried.
Operational notes and restrictions for CCI operations
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 367
Items Notes and restrictions
Linkage with HA
software
The HORC Manager must not be an object of the process
monitoring by the HA software (cluster manager), because
HORCM should run in the same level as the cluster manager.
Cooperation with HA software is done by activating the takeover
command from the shell script activated by the cluster manager in
units of the package software.
Note: Cannot use a pair volume for the cluster lock disk that HA
software uses for election.
Maintenance Restart of HORCM is required if the storage system conguration
is changed (for example, microcode exchange, cache memory
install/uninstall).
TrueCopy only: In the case of an error (for example, single error in
cache memory) which made the pair volume is accompanied by
maintenance work, the pairresync or paircreate command
cannot execute copy rejection.
SVP/GUM
microcode
exchange
In out-of-band method using SVP, if the microcode exchange of
the SVP is performed, the timeout on command occurs. Execute
the command again after nishing the microcode exchange.
In out-of-band method using GUM, if the maintenance on the
controller with GUM is performed, the timeout on command
might occur. Switch the command device so that the other virtual
command device of GUM can be used before the maintenance.
For details about the alternate command device function, see
Alternate command device function.
Operational notes and restrictions for CCI operations
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 368
Items Notes and restrictions
Command device Each TrueCopy/ShadowImage command is executed by issuing a
command to the command device. The TrueCopy/ShadowImage
command is read or written from/into the specic block area of
the command device. Therefore, the command device cannot be
used. In addition, this device must not belong to an LVM volume
group. For Windows systems, do not assign a drive letter to the
command device to prevent utilization by general users.
SCSI alternate
path restrictions
If the P-VOL and S-VOL are on the same server, alternate path
from P-VOL to S-VOL cannot be used. Use of SCSI alternate path to
a volume pair in the pair status is limited to among primary
(secondary) volumes. Alternate path using Path Manager (Safe
Path) is limited to primary volumes.
horctakeover
(Swap-Takeover)
When executing horctakeover on a standby server manually, I/O
on the active server must be stopped. When the package software
goes for a standby server a failover by HA software, the HA
software must guarantee an I/O insulation of the active server.
HORCM failure to
activate
After a new system has been constructed, a failure to activate
HORCM might occur due to improper environment setting and/or
conguration denition. Refer to the HORCM activation log, and
correct the settings.
Abnormal
termination of
command
Refer to the command log le and HORCM log le to identify the
cause of the error. If a command terminates abnormally because
of a remote server failure, recover the server from the failure, then
re-execute the command. If HORCM has shut down, restart
HORCM. If an unrecoverable error occurs, obtain the log les and
contact customer support.
Error in paired
volume operation
TrueCopy only: If an error occurs in duplicated writing in paired
volumes (that is, pair suspension), the server software using the
volumes might detect the error by means of the fence level of the
paired volume. In such a case, check the error notication
command or syslog le to identify a failed paired volume.
The system administrator can conrm that duplicated writing in a
paired volume is suspended due to a failure and the system runs
in regressed state using the error notication command of the
TrueCopy. HORCM monitors failures in paired volumes at regular
intervals. When it detects a failure, it outputs it to the host's syslog
le. Thus, the system administrator can detect the failure by
checking the syslog le. Concerning the operation of the RAID
storage system, the failure can also be found on Storage Navigator
(or SVP) provided.
Operational notes and restrictions for CCI operations
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 369
Items Notes and restrictions
Issue the TrueCopy commands manually to the identied failed
paired volume to try to recover it. If the secondary volume is
proved to be the failed volume, issue the pair resynchronization
command to recover it. If the primary volume fails, delete the
paired volume (pair splitting simplex) and use the secondary
volume as the substitute volume.
About "/
HORCM/.uds"
directory
CCI uses "/HORCM/.uds" as the directory for the UNIX domain
socket for IPC (Inter Process Communication), and makes the
directory and les as "/HORCM/.uds/.lcm*" in CCI version
01-17-03/01 or later.
Caution: This "/HORCM/.uds/.lcm*" should not be removed while
HORCM is running.
Error messages and error codes
System log messages
The following table lists and describes the HORCM system log messages and provides
recommended actions for resolving the error conditions.
Message ID Condition Cause Recommended action
HORCM_001 The HORCM log
le cannot be
opened.
The le cannot be
created in the
HORCM directory.
Create space on the disk
on which the root directory
resides.
HORCM_002 The HORCM trace
le cannot be
opened.
The le cannot be
created in the
HORCM directory.
Create space on the disk
on which the root directory
resides.
HORCM_003 The HORCM
daemon process
cannot create a
child process due
to an error.
HORCM daemon
attempted to create
more processes than
the maximum
allowable number.
Terminate unnecessary
programs or daemon
processes running
simultaneously.
HORCM_004 HORCM assertion
failed, resulting in
a fatal internal
error in the
HORCM.
An internal error that
could not be
identied by the
HORCM occurred.
Restart the system, and
contact customer support.
Error messages and error codes
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 370
Message ID Condition Cause Recommended action
HORCM_005 The CCI software
failed to create
the end point for
remote
communication.
HORCM failed to
create a socket, or an
error exists in the
format or a
parameter in the
HORCM conguration
denition le
($HORCM_CONF).
Refer to the HORCM
startup log to identify the
cause of the error.
HORCM_006 HORCM memory
allocation failed.
HORCM memory
could not be secured.
Increase the system virtual
memory, or close any
unnecessary programs.
HORCM_007 An error exists in
the parameter
value in the
HORCM setup le.
An error exists in the
parameter value
setting in the HORCM
setup le.
Refer to the startup log
and reset the parameters.
HORCM_008 HORCM
conguration
denition le
parameters
reading fails.
An error exists in the
format or parameters
of the HORCM
conguration
denition le
($HORCM_CONF).
Refer to the HORCM
startup log to identify the
cause of the error.
HORCM_009 TrueCopy/
ShadowImage
connection to the
CCI software
failed.
System devices are
improperly
connected, or an
error exists in the
device parameter in
the HORCM
conguration
denition le.
Refer to the HORCM
startup log to identify the
cause of the error.
HORCM_101 TrueCopy/
ShadowImage and
the CCI software
communication
fails.
A system I/O error
occurred or an error
exists in the device
parameter in the
HORCM conguration
denition le
($HORCM_CONF).
Refer to the HORCM
startup log to identify the
cause of the error.
HORCM_102 The volume is
suspended.
The pair status was
suspended due to
code XXXX.
Contact customer support.
System log messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 371
Message ID Condition Cause Recommended action
HORCM_103 Detected a
validation check
error on this
volume (xxxx
unit#x,ldev#x):
CfEC=n, MNEC=n,
SCEC=n, BNEC=n
A validation error
occurs on the
database volume, or
validation parameters
for this volume are
illegal.
Please conrm the
following items, and use
raidvchkdsp -v <op>
command for verifying the
validation parameters.
(1)Check if the block size (-
vs <size>) is an appropriate
size.
(2)Check if the type for
checking (-vt <type>) is an
appropriate type.
(3)Check if the data
validations are disabled for
LVM conguration
changes.
(4)Check if the data
validations are not shared
on le system.
(5)Check if the redo log and
data le are separated
among the volumes.
Command error messages
The following table lists and describes the command error messages and their return
values and provides recommended action for resolving the error conditions.
The messages below are typical command error messages. Check the command log le
for details of the error. For details about the command log le, see CCI log les.
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_COM
ERR
Can't be
commu
nicate
with
HORC
Manage
r
This command failed to
communicate with the CCI
software.
Conrm whether HORCM is enabled.
If HORCM is not activated yet, start
HORCM. If HORCM ended
abnormally despite being activated,
verify the disk capacity has 3000 KB
or more free space. Free up disk
space, and then restart HORCM. If
the problem persists, contact
customer support.
255
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 372
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_REQ
ARG
Require
d Arg list
Arguments for the
command are not
sucient, or the
command syntax is not
correct.
Please designate the correct option
using the -h option.
254
EX_INVA
RG
Invalid
argume
nt
An option or arguments of
an option are incorrect.
Please designate the correct option
using the -h option.
253
EX_UNW
OPT
Unknow
n option
Designated an unknown
option.
Please designate the correct option
using the -h option.
252
EX_ATTH
OR
Can't be
attached
to HORC
Manage
r
Could not connect with
HORCM.
Please verify that HORCM is running
and/or that HORCMINST is set
correctly.
251
EX_ATTD
BG
Can't be
attached
to a
Debug
layer
Failed to communicate
with HORCM, or cannot
make a log directory le.
Verify that HORCM is running by
using UNIX commands [ps - ef | grep
horcm].
250
EX_INVN
AM
Invalid
name of
option
The name specied in an
argument of an option is
not appropriate.
Please designate the correct name
using the -h option.
249
EX_OPTI
NV
A
specie
d option
is invalid
Detected contradiction in
information that RAID
reported.
Contact customer support. 248
EX_ENO
ENT
No such
device
or group
The designated device or
group name does not exist
in the conguration
denition le.
Verify the device or group name and
add it to the conguration denition
le of the remote and local hosts.
247
EX_ENO
DEV
No such
device
The designated device
name does not exist in the
conguration denition
le.
Verify the device name and add it to
the conguration denition le of the
remote and local hosts.
246
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 373
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_ENO
UNT
No such
RAID
unit
The designated RAID unit
ID does not exist in the
conguration denition
le.
Verify the RAID unit ID and add it to
the conguration denition le of the
remote and local hosts.
219
EX_ENQ
SER
Unmatc
hed
Serial#
vs RAID
unitID
The group designated by
ShadowImage paircreate
does not have the same
RAID unit, or the unitID is
not identical to the unit ID
in the same RAID serial#
(Seq#).
Conrm the serial# (Seq#) of the
storage system using the
pairdisplay command, or conrm
that the serial# (Seq#) and the unit
ID of storage system are the same
among hosts using the raidqry -r
command.
218
EX_ENO
MEM
Not
enough
core
Insucient memory
exists.
Increase the virtual memory capacity
of the system, or close any
unnecessary programs and/or
daemon processes.
245
EW_ENE
SCR
Cannot
execute
script
le
The script le specied by
the -zt option cannot be
performed.
Conrm the execution right,
permission the extension, the
execution path of the script le.
131
EX_ERA
NGE
Result
too
large
Your entry is one of the
following statuses.
■The value was entered
beyond the maximum.
■The result value is
beyond the maximum.
■The unit you set is
invalid.
Refer to the error message, and
designate an appropriate value or
conrm whether you specied the
unit correctly.
244
EX_ENA
MLG
File
name
too long
Undened error. Contact customer support. 243
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 374
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_ENO
RMT
No
remote
host
alive for
remote
comman
ds or
remote
HORCM
might
be
blocked
(sleepin
g) on an
existing
I/O
A timeout occurred on
remote communication,
and HORC Manager failed
to re-execute.
Please conrm that the HORC
Manager in the remote host is
running. If the IP address of the host
has been changed, restart the
HORCM instance. If the HORCM still
does not restart, increase the value
of the timeout in the conguration
denition le.
242
EX_INVM
OD
Invalid
RAID
comman
d mode
Detected a contradiction
for a command.
Contact customer support. 241
EX_INVC
MD
Invalid
RAID
comman
d
Detected a contradiction
for a command.
Contact customer support. 240
EX_ENO
GRP
No such
group
The designated device or
group name does not exist
in the conguration
denition le, or the
network address for
remote communication
does not exist.
Verify the device or group name and
add it to the conguration denition
le of the remote and local hosts.
239
EX_UNW
COD
Unknow
n
function
code
Detected a contradiction
for a command.
Retry your operation after restart of
the instance for CCI. Contact
customer support if the operation
fails because of same error again.
238
EX_CMD
IOE
Control
comman
d I/O
error
A read/write to the
command device failed
with an I/O error.
This error might occur due to a
device failure. Check device
condition, then retry the command
after recovery from the failure. If the
error occurs even after the retry,
refer to the host syslog le, and
investigate the cause of the error.
237
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 375
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
If the problem persists, collect the log
information of HORCM
($HORCM_LOG), and contact
customer support.
EX_CMD
RJE
An order
to the
control/
comman
d device
was
rejected
The request to the
command device failed or
was rejected.
Note: This error code is
sometimes caused by the
operating system and
reported as EX_CMDIOE
instead of EX_CMDRJE (see
next row).
Verify the program products, such as
TrueCopy and ShadowImage, are
installed.
Verify ports are set.
Verify CU paths have been
established by Device Manager -
Storage Navigator, CCI, or other
methods.
Verify that the target volume is
available.
CCI displays "SSB" in the output of
the commands so a service
representative can identify the cause
of EX_CMDRJE (except for Tru64,
DYNIX).
Example:
# paircreate -g G1 -f never -
vl -nocopy
paircreate: [EX_CMDRJE] An
order to the control/command
device was rejected
Refer to the command log (/
HORCM/log10/horcc_u1-1.log)
for details.
It was rejected due to
SKEY=0x05, ASC=0x26,
SSB=0xB9BF,0xB9C7 on
Serial#(63502).
221
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 376
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_CMD
IOE
Control
comman
d I/O
error or
rejected
A read/write to the
command device failed
with an I/O error or was
rejected.
This error might occur due to a
device failure. Check device
condition, then retry the command
after recovery from the failure. If the
error occurs even after the retry,
refer to the host syslog le, and
investigate the cause of the error. If
the cause is "Illegal Request (0x05)"
Sense Key, please conrm the
following items.
Verify the program products, such as
TrueCopy and ShadowImage, are
installed.
Verify ports are set.
Verify CU paths have been
established by Device Manager -
Storage Navigator, CCI, or other
methods.
Verify that the volume which is the
target of the pair operation is in the
appropriate status for issuing the
concerned command.
237
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 377
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
Verify that the status of the volume
which is the target of the pair
operation changed to the intended
status after 160 or more seconds
have passed since the concerned
command issued.
■When the status has changed as
you intended: The command
executed normally. The
communication delay or other
errors may happen. Conrm the
path between the storage
systems.
■When the status has not changed:
Issue the concerned command
again. If the phenomenon
happens again, contact customer
support.
■Other than above: Contact
customer support.
If the problem persists, contact
customer support.
EX_ENQ
VOL
Unmatc
hed
volume
status
within
the
group
The volume attribute or
the fence level within a
group is not identical.
Conrm status using the
pairdisplay command. Make sure
all volumes in the group have the
same fence level and volume
attributes.
236
EX_EVOL
CE
Pair
Volume
combina
tion
error
Combination of a volume
is unsuitable between the
remote and local host.
Conrm volume status using the
pairdisplay command, and
change the combination of volumes
properly.
235
EX_EWS
USE
Pair
suspend
ed at
WAIT
state
Detected a suspended
status (PSUE) for the
paired volume, before it
made it to the designated
status.
Please issue the pairresync
command manually to the identied
failed paired volume to try to recover
it.
If the problem persists, contact
customer support.
234
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 378
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_EWS
TOT
Timeout
waiting
for
specie
d status
Detected a time out,
before it made it to the
designated status.
Please increase the value of the
timeout using the -t option. For
details, refer to the troubleshooting
information in the relevant user
document.
When this error occurs during
execution of the pairsplit command,
contact customer support.
233
EX_EWS
LTO
Timeout
waiting
for
specie
d status
on the
local
host
Timeout error because the
remote did not notify
about expected status in
time.
Please conrm that HORC Manager
on the remote host is running.
232
EX_EST
MON
HORCM
Monitor
stopped
HORC Manager
monitoring was refused.
Please conrm the value of "poll" in
the conguration denition le.
231
EX_UNW
CMD
Unknow
n
comman
d
An unknown command
was attempted.
Please conrm the command name. 230
EX_INCS
TG
Inconsis
tent
status in
group
The pair status of a
volume within a group is
not identical to the status
of the other volumes in
the group.
Please conrm the pair status using
the pairdisplay command.
229
EX_INVS
TP
Invalid
pair
status
The pair status of the
target volume is not
appropriate.
Please conrm the pair status using
the pairdisplay command.
228
EX_INVV
OL
Invalid
volume
status
The volume status of the
target volume is not
appropriate.
Please conrm the volume status
using the pairdisplay -l or the
raidvchkdsp -v aou command.
222
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 379
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_INVM
UN
Invalid
mu#
with
HORC/U
R or
HOMRC
F
The MU# of the volume to
be operated is not
appropriate.
Please conrm the MU# (MU #1/2
cannot be used for TrueCopy and
must be P-VOL for ShadowImage.) for
the specied group using the
pairdisplay command. And also
conrm the command execution
environment to be set as HOMRCF.
220
EX_ENL
DEV
No such
LDEV
within
the RAID
A device dened in the
conguration denition
le does not have a
mapping to a real LUN and
target ID within the RAID
storage system.
Please conrm that the Port, Target
ID, LUN are dened correctly under
HORCM_DEV in the conguration
denition le.
227
EX_INVR
CD
Invalid
return
code
Wrong return code. Contact customer support. 226
EX_VOLC
UR
S-VOL
currency
error
Currency check error for
S-VOL. Cannot guarantee
identical data on S-VOL.
Check the volume list to see if an
operation was directed to the wrong
S-VOL.
225
EX_VOLC
UE
Local
volume
currency
error
The volume specied with
the S-VOL-takeover
command is not the same
as the P-VOL.
Please conrm the pair status of the
local volume using the pairdisplay
command.
224
EX_VOLC
RE
Local
and
remote
volume
currency
error
The combination of the
volumes specied with
Swap-takeover is
unsuitable.
Please conrm the pair status of
remote and local volumes using the
pairdisplay command.
223
EX_UNW
ERR
Unknow
n error
code.
Wrong error code. Contact customer support. --
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 380
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_ENO
CTG
Not
enough
CT
groups
in RAID
The specied CTG ID
cannot be used when the
volume for TrueCopy,
Universal Replicator,
global-active device or
ShadowImage pair is
created, because the
specied CTG ID is used by
the other program
product in the storage
system. Otherwise, CTG ID
cannot be registered
because the number of
the consistency groups
exceeds the maximum
number.
For details about the
maximum number of the
consistency groups, see
TrueCopy, Universal
Replicator, and global-
active device volumes.
When the specied CTG ID is used by
the other program product, use the
other CTG ID which is not used by the
other program product in the storage
system.
217
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 381
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
When the number of the consistency
groups exceeds the maximum
number, execute one of the following
actions:
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 382
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
■To create the TC, UR, GAD or SI
pair after reducing the
consistency groups:
1. Select consistency group which
can be deleted in the existing
consistency groups.
2. Find the conguration
denition le in which the name
of the consistency group to be
deleted is written at dev_group.
3. Execute the pairsplit -S
command specifying the
dev_group name of the
consistency group to be deleted
by the HORCM instance which
matches the conguration
denition le found at step 2 (split
the pair).
4. Delete the dev_group which
matches the consistency group to
be deleted from the conguration
denition le found in step 2
(delete both P-VOL and S-VOL
which congures the split pair).
5. Restart the HORCM instance
which matches the conguration
denition le found at step 2,
reecting the editing results of the
conguration denition le.
6. Add the device to the
dev_group which matches the
consistency group to be added
using new or existing
conguration denition le (add
P-VOL and S-VOL which congures
the pair to be added).
7. Start or restart the HORCM
instance which matches the
conguration denition le used
at step 6.
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 383
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
8. Execute the paircreate
command specifying the
dev_group name of the
consistency group in which the
pair is added by the HORCM
instance which matches the
conguration denition le used
at step 6 as follows.
In case of TC, UR, or GAD:
paircreate -g <dev_group
name> -f[g] <fence>
[CTGID]
In case of SI:
paircreate -g <dev_group
name> -m grp [CTGID]
Conrm the CTG ID of the existing
consistency group by pairvolchk
command.
When the -fg option is specied
and CTGID is omitted in the
paircreate command, unused
CTG ID is set automatically.
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 384
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
■To add the TC, UR, GAD or SI pair
to the existing consistency group
that is used by the same program
product:
1. Select an existing consistency
group to which the pair can be
added.
2. Find the conguration
denition le in which the name
of the consistency group to which
the pair is added is written at
dev_group.
3. Add the device to the
dev_group in the conguration
denition le found at step 2
which matches the consistency
group to which the pair is added
(add P-VOL and S-VOL which
congures the pair to be added).
4. Restart the HORCM instance
which matches the conguration
denition le found at step 2,
reecting the editing results of the
conguration denition le.
5. Execute the paircreate
command specifying the
dev_group name of the
consistency group to which the
pair is added by the HORCM
instance which matches the
conguration denition le found
at step 2 as follows.
In case of TC, UR, or GAD:
paircreate -g <dev_group
name> -f[g] <fence>
[CTGID]
In case of SI:
paircreate -g <dev_group
name> -m grp [CTGID]
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 385
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
Conrm the CTG ID of the existing
consistency group by pairvolchk
command.
When the -fg option is specied
and CTGID is omitted in the
paircreate command, unused
CTG ID is set automatically.
EX_EXTC
TG
Extende
d CT
group
across
RAIDs
A TrueCopy, Universal
Replicator, global-active
device, or ShadowImage
volume is dened in the
conguration denition
le (HORCM_CONF) as a
group that extends across
storage systems.
Please conrm the serial # of the
volumes by using the pairdisplay
command to verify that the
consistency group is contained
completely within one RAID storage
system.
216
EX_ENXC
TG
No CT
groups
left for
OPEN
Vol use.
An available consistency
group for OPEN Volume
does not exist.
Please conrm whether all
consistency groups are already used
by mainframe volumes.
215
EX_ENQ
CTG
Unmatc
hed
CTGID
within
the
group
The consistency group
references within a group
do not have an identical
CTG ID.
Please conrm the CTG ID using the
pairvolchk command and conrm
that group references within the
conguration denition le
(HORCM_CONF) refer to the same
consistency group.
214
EX_ENPE
RM
Permissi
on
denied
with the
LDEV
A device mentioned in the
conguration denition
le does not have a
permission for a pair-
operation.
Please conrm whether pair-
operation is permitted on the device
by using the pairdisplay or
raidscan -find verify
command.
213
EX_ENQ
SIZ
Unmatc
hed
volume
size for
pairing
Size of a volume is
unsuitable between the
remote and local volume.
Please conrm volume size or
number of LUSE volume using the
'raidscan -f' command, and make
sure the volume sizes are identical.
212
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 386
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_ERPE
RM
Permissi
on
denied
with the
RAID
A storage system (RAID)
mentioned in the
conguration le does not
have a permission for CCI.
Please conrm if the type of storage
system is permitted for a CCI by
using the inqraid -CLI and
raidqry -h commands.
211
EX_ESVO
LD
S-VOL
denied
due to
be
disablin
g
A specied target volume
for S-VOL is denied to
become S-VOL by the
setting of Data Retention
Utility.
Please conrm whether a target
volume is setting to S-VOL disabling y
using inqraid -fl or
raidvchkscan -v gflag
command.
209
EX_ENO
SUP
Microco
de not
support
ed
The storage system does
not support a function for
CCI.
Please conrm the storage system
model name and microcode version
by using the raidqry -l command.
210
EX_EPR
ORT
Mode
changes
denied
due to
retentio
n time
A target volume is denied
to be changing due to
retention time via LDEV
guarding.
Please conrm the retention time for
a target volume that is set to Data
Retention Utility by using
raidvchkscan -v gflag
command.
208
EX_ESPE
RM
Permissi
on
denied
with the
SLPR
A specied command
device does not have a
permission to access
other SLPR.
Please make the SLPR so that the
target port and the command device
belongs to the same SLPR.
207
EX_ENO
POL
Not
enough
Pool in
RAID
Could not retain the pool
for executing a command
due to be exceeded the
threshold rate.
Please release the pair of older
generations paired volume, or re-
synchronize the pair of split status
paired volume.
206
EX_ENO
OBJ
No such
Object
in the
RAID
The specied object is not
installed. There are port,
LDEV, and Hostgroup in
the object.
Specify the appropriate object. Check
the status of one of the following.
■The specied port is not installed.
■The value of the specied port is
invalid.
■LU path is dened.
■A logical path between MCU and
RCU remain.
■LDEV is not installed.
205
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 387
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
■The attribute of the port is not
Target (TAR) or RCU Target (RCU).
■LUN security is invalid.
■The specied host group is not
installed.
■The specied virtual port ID is not
correct.
EX_EPPE
RM
Permissi
on
denied
with the
privilege
The specied command
device does not have an
authority to execute this
command.
Check the operation authentication. 203
EX_ENQ
CLP
Unmatc
hed
CLPR
with JNL
and
Volume
The specied command
device does not have an
authority to execute this
command.
Check the operation authentication. 204
EX_CTXC
HK
Context
check
error
An error is detected by the
Context Checking.
Check if the operation by the
command executes a proper
procedures and has the consistency
or not.
199
EX_EACC
ES
Access
denied
with
Lock/
Unlock
The resource that you
specied to lock or unlock
has already been used by
another user.
Check if the specied resource is
used by such as Storage Navigator or
Device Manager - Storage Navigator
or not.
200
EX_ENA
UTH
Authenti
cation
failed
with
User
User authentication failed
at the authentication
command device.
Check the user ID and password. 202
EW_INV
ARG
Invalid
argume
nt
Invalid option or an
argument of the option.
User -h option to check the correct
option, and specify it.
253
EW_INV
OPA
Invalid
option
argume
nt
Invalid argument of an
option
Use -h option to check the correct
option and use it.
131
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 388
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EW_INV
OPT
Invalid
option
Invalid option. Use -h option to check the correct
option and use it.
131
EW_LNG
ARG
Argume
nt too
long
The number of character
for action, object, option
or argument of option
exceeded the maximum.
Specify the number of characters of
action, object, option, an argument of
option, or the total number of
characters are to be appropriate
number of characters.
131
EW_MAX
ARG
Maximu
m
argume
nt
The total number of
option or the argument of
option exceeded the
maximum.
Check the total number of option or
argument of option.
131
EW_ENFI
LE
No such
le
The specied le dies not
exist.
Check if the specied le exist or not,
and specify the correct le.
131
EW_REQ
CMD
Require
d action/
object
list
The number of action or
the argument of object is
insucient.
Use -h option and specify the correct
action or object.
131
EW_REQ
OPT
Require
d option
list
The number of option or
the argument of option is
insucient.
Use -h option and specify the correct
option.
131
EW_UN
WCMD
Unknow
n
comman
d
The command action or
an object is undened.
Check the issued command action
and object.
230
EW_UN
WOPT
raidcom:
[EW_UN
WOPT]
Unknow
n option
Species an undened
option.
Use -h option and specify the correct
option.
252
EW_SYS
ERR
System
error
An invalid internal error
has detected.
Contact customer support. 131
EW_ENO
MEM
Not
enough
core
Memory to execute a
command cannot be
allocated in HORCM.
Add more virtual memory of a whole
system, or terminate unnecessary
programs or daemons that are
executed in parallel.
245
Command error messages
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 389
Error
code
Error
messag
e Condition Recommended action
Returne
d Value
EX_CHG
OBJ
Objects
was
changed
while
referring
The object is in operation. Issue the command again after the
operation of the object is complete.
198
EX_EGPE
RM
Permissi
on
denied
with the
Resourc
e Group
You do not have the
operation authority to
operate the target
resource group.
Specify the resource group that is
allocated to the user group as the
operation target or set the operation
authority to the user group in order
to operate the target resource group.
201
EX_IDEX
HA
There is
no
available
request
ID.
There are no request IDs
that can be used for the
storage system.
Release the request IDs that are no
longer used.
194
Generic error codes (horctakeover and pair commands)
The following table lists the generic error codes returned by the following commands:
■horctakeover
■paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk,
pairsyncwait, pairdisplay
In this table, "Unrecoverable" indicates errors that cannot be recovered by reexecuting
the command, and "Recoverable" indicates errors that can be recovered by reexecuting
the command.
Category Error code Error message
Retu
rn
Valu
e
Syntax for
Argument
(Unrecoverable)
EX_REQARG Required Arg list 254
EX_INVARG Invalid argument 253
EX_INVNAM Invalid name of option 249
EX_UNWOPT Unknown option 252
EX_UNWCOD Unknown function code 238
Generic error codes (horctakeover and pair commands)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 390
Category Error code Error message
Retu
rn
Valu
e
EX_UNWCMD Unknown command 230
EX_ERANGE Result too large 244
EX_ENAMLG File name too long 243
EX_INVRCD Invalid return code 226
Conguration
(Unrecoverable)
EX_ENOGRP No such group 239
EX_ENOENT No such device or group 247
EX_ENODEV No such device 246
EX_ENLDEV No such LDEV within the RAID 227
EX_ENOUNT No such RAID unit 219
EX_INVMUN Invalid mu# with HORC or HOMRCF 220
EX_ENQSER Unmatched Serial# vs RAID unitID 218
EX_EXTCTG Extended CTgroup across RAIDs 216
EX_ENQCTG Unmatched CTGID within the group 214
EX_ENPERM Permission denied with the LDEV 213
EX_ERPERM Permission denied with the RAID 211
EX_ESPERM Permission denied with the SLPR 207
Command I/O to
RAID
(Recoverable)
EX_CMDRJE An order to the control/command was
rejected
221
EX_CMDIOE Control command I/O error, or
rejected
237
EX_OPTINV A specied option is invalid 248
EX_INVMOD Invalid RAID command mode 241
EX_INVCMD Invalid RAID command 240
Communication for
HORCM
(Recoverable)
EX_ATTHOR Cannot be attached to HORC manager 251
EX_ATTDBG Cannot be attached to a Debug layer 250
EX_COMERR Cannot be communicate with HORC
manager
255
Generic error codes (horctakeover and pair commands)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 391
Category Error code Error message
Retu
rn
Valu
e
Recoverable EX_ENORMT No remote host alive for remote
commands, or Remote CCI might be
blocked (sleeping) on an existing I/O.
242
Resource
(Unrecoverable)
EX_ENOMEM Not enough core 245
Generic error codes (raidscan, raidqry, raidar, horcctl)
The following table lists the generic error codes returned by the following commands:
■raidscan
■raidqry
■raidar
■horcctl
In this table, "Unrecoverable" indicates errors that cannot be recovered by reexecuting
the command, and "Recoverable" indicates errors that can be recovered by reexecuting
the command.
Category Error code Error message
Valu
e
Syntax for
Argument
(Unrecoverable)
EX_REQARG Required Arg list 254
EX_INVARG Invalid argument 253
EX_INVNAM Invalid name of option 249
EX_UNWOPT Unknown option 252
EX_UNWCOD Unknown function code 238
EX_UNWCMD Unknown command 230
EX_ERANGE Result too large 244
EX_ENAMLG File name too long 243
EX_INVRCD Invalid return code 226
Conguration
(Unrecoverable)
EX_ENLDEV No such LDEV within the RAID 227
EX_ENOUNT No such RAID unit 219
Generic error codes (raidscan, raidqry, raidar, horcctl)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 392
Category Error code Error message
Valu
e
EX_INVMUN Invalid mu# with HORC or HOMRCF 220
EX_ERPERM Permission denied with the RAID 211
EX_ENOSUP Microcode not supported 210
EX_ESPERM Permission denied with the SLPR 207
Command I/O to
RAID
(Recoverable)
EX_CMDIOE Control command I/O error 237
EX_OPTINV A specied option is invalid 248
EX_INVMOD Invalid RAID command mode 241
EX_INVCMD Invalid RAID command 240
Communication
for HORCM
(Recoverable)
EX_ATTHOR Can't be attached to HORC manager 251
EX_ATTDBG Can't be attached to a Debug layer 250
EX_COMERR Can't be communicated with HORC
manager
255
Resource
(Unrecoverable)
EX_ENOMEM Not enough core 245
Specific error codes
The following table lists the specic error codes returned by the following commands:
■horctakeover
■paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk,
pairsyncwait, raidvchkset
In this table, "Unrecoverable" indicates errors that cannot be recovered by reexecuting
the command, and "Recoverable" indicates errors that can be recovered by reexecuting
the command.
See the Command Control Interface Command Reference for more information on error
codes for each command.
Category Error code Error message Value
Volume Status
(Unrecoverable)
EX_ENQVOL Unmatched volume status within the
group
236
EX_INCSTG Inconsistent status in group 229
Specic error codes
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 393
Category Error code Error message Value
EX_INVVOL Invalid volume status 222
EX_EVOLCE Pair Volume combination error 235
EX_INVSTP Invalid pair status 228
EX_VOLCUR S-VOL currency error 225
EX_VOLCUE Local Volume currency error 224
EX_VOLCRE Local and Remote Volume currency error 223
EX_EWSUSE Pair suspended at WAIT state 234
EX_ENQSIZ Unmatched volume size for pairing 212
EX_ESVOLD S-VOL denied due to be disabling 209
EX_EPRORT Mode changes denied due to retention
time
208
Timer
(Recoverable)
EX_EWSTOT Timeout waiting for specied status 233
EX_EWSLTO Timeout waiting for specied status on
the local host
232
Resource
(Unrecoverable)
EX_ENOCTG Not enough CT groups in the RAID 217
EX_ENXCTG No CT groups left for OPEN Vol use. 215
EX_ENOPOL Not enough Pool in RAID 206
Specic error codes
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 394
SSB codes
An SSB code is error information that is output when an error occurs by executing a CCI
command. The SSB code is output to the CCI execution log le or to the console. Identify
the SSB code from an error code as follows:
■SSB code that is output to the CCI execution log le.
The following shows an example of a SSB code that is output to the CCI execution log
le.
Example:11:06:03-37897-10413- SSB = 0xb9a0,2089
The alphanumeric characters after the equal sign shows an error code. The last four
digits of alphanumeric characters on the left side of the comma (,) is SSB1 (for
example, b9ao), and the alphanumeric characters on the right side is SSB2 (for
example, 2089).
■SSB code that is output on the console.
The following shows an example of an SSB code that is output to the console.
The alphanumeric characters after the "SSB=" show an error code. The last four digits
of alphanumeric characters on the left side of comma (,) is SSB1 (for example, B9E1),
and the last four digits of alphanumeric characters on the right side is SSB2 (for
example, B901).
The following describes the SSB codes returned by the replication commands and the
conguration setting command (raidcom).
SSB codes returned by the replication commands
When a replication command returns an SSB code, refer to the troubleshooting
information in the user document for the product as follows:
Command Product returning the SSB code
■paircreate
■pairresync
■pairsplit
■horctakeover
■horctakeo
Hitachi TrueCopy®
■paircreate
■pairresync
■pairsplit
Universal Replicator
SSB codes
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 395
Command Product returning the SSB code
■horctakeover
■horctakeo
■paircreate
■pairresync
■pairsplit
■horctakeover
■horctakeo
global-active device
■paircreate
■pairresync
■pairsplit
Hitachi ShadowImage®
■paircreate
■pairsplit
Hitachi Volume Migration
■paircreate
■pairresync
■pairsplit
Hitachi Thin Image
■raidvchkset -vt
■raidvchkset -vs
Database Validator
■raidvchkset -vg Data Retention Utility
■raidvchkset -vext Hitachi Dynamic Provisioning
The following tables provide information about the SSB codes returned by the replication
commands. If you see an error not described in the tables, contact customer support.
SSB codes returned by the paircreate command
paircreate
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
SSB codes returned by the replication commands
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 396
paircreate
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by the pairsplit command
pairsplit
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
SSB codes returned by the pairsplit -S command
pairsplit -S
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
SSB codes returned by the configuration setting command (raidcom)
Executing the conguration setting command (raidcom command) can return an SSB
code. An error can occur whether the command is executed synchronously or
asynchronously. For an asynchronous error, the error information is displayed on the
console by executing raidcom get command_status command. When the error
message shows "CMDRJE" or "Get Command Status", check the contents of SSB1 and
SSB2. You can verify a content of an error by the raidcom get error_message
command. When you specify the SSB code with the raidcom get error_message
command, make sure not to specify a wrong SSB code.
The following tables provide information about each SSB code returned by the
conguration setting command (raidcom command). If you see an error not described
in the tables, contact customer support.
SSB codes returned by the conguration setting command (raidcom)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 397
Common
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE Executing 2E11 2205 The resource group to which the operation
object belongs is locked by another user (or
another session). Check the lock status of the
resource group. If maintenance personnel is
performing maintenance operations, retry the
command after conrming the completion of
the operations.
CMDRJE Executing 2E11 2206 You do not have the operation authority for the
target resource group. Specify the resource
group that is allocated to the user group as the
operation target, or set the operation authority
to the user group in order to operate the target
resource group.
CMDRJE Executing 2E11 2207 The system is locked by another user (or
another session). Wait a while, then retry the
command. If maintenance personnel is
performing maintenance operations, retry the
command after conrming the completion of
the operations..
CMDRJE
Get Command
Status
Executing/
Async
2E11 8303 The command cannot be executed because
there is blocked part in the system.
CMDRJE Executing 2E11 9400 The command cannot be accepted. Wait a
while, then retry the command.
CMDRJE Executing 2E31 9100 The command cannot be executed because the
user authentication is not performed.
CMDRJE
Get Command
Status
Executing/
Async
2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EBE 9E01 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by the conguration setting command (raidcom)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 398
Common
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 9300 The specied command cannot be executed
due to the following reasons:
■The command cannot be accepted because
it is not supported.
■The command is not supported in the
current CCI version.
CMDRJE Executing 2EF3 9F02 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EF4 0026 The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2EFF FF00 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B90F B90F The specied operation is not supported in the
current microcode version.
CMDRJE Executing B954 FF5F The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9EC B9EC The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9EE B9EE The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9FD B90A The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9FD B90C The specied operation is not supported in the
current microcode version.
SSB codes returned by raidcom add external_grp
raidcom add external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 000D Invalid emulation type.
SSB codes returned by raidcom add external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 399
raidcom add external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 0013 There are not enough cache management
devices.
CMDRJE Executing 2E00 4100 The external volume group is not in a eective
range.
Get Command
Status
Async 2E00 4104 The command cannot be executed by receiving
the multiple operations for the same external
volume group.
Get Command
Status
Async 2E00 4108 The external volume group exists already.
Get Command
Status
Async 2E00 410B The specied CLPR does not exist.
CMDRJE Executing 2E00 410D The volume cannot be mapped for online data
migration because the emulation type is not
OPEN-V.
CMDRJE Executing 2E00 410E The specied external volume group attribute is
invalid.
CMDRJE
Get Command
Status
Executing
Async
2E00 4111 This command does not support the specied
emulation type.
CMDRJE Executing 2E00 4500 The path group is not in a eective range.
CMDRJE Executing 2E00 8400 The value of the specied port is not valid.
CMDRJE Executing 2E00 9B01 The specied iSCSI name is invalid.
Get Command
Status
Async 2E02 4101 The iSCSI target cannot be specied because
the emulation type is for mainframe.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
Get Command
Status
Async 2E10 4200 LUN of the specied external storage port does
not exist.
Get Command
Status
Async 2E10 4201 The external volume cannot be created
because the specied external LU is a
command device.
SSB codes returned by raidcom add external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 400
raidcom add external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 4203 The volume cannot be mapped as a remote
command device because the specied
external LU is not a command device.
Get Command
Status
Async 2E10 4400 The WWN on the side of the specied external
storage does not connected to a External port.
This message may be output if the migration
source storage system is USP V/VM and the
host mode option 2 is not set to the port that
connects to the migration target storage
system.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
Get Command
Status
Async 2E11 4106 The specied external LU cannot create a
external volume because the transition of data
is required.
Get Command
Status
Async 2E11 4200 The specied path group cannot be operated
because a path between other devices exists.
Get Command
Status
Async 2E11 800F The operation cannot be performed because
the unsupported microcode version exists in
the system.
CMDRJE Executing 2E11 8010 The storage system is in internal process, or the
conguration changing processes are
conicting.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 4102 Package for Mainframe is required when you
specify the emulation type of mainframe.
Get Command
Status
Async 2E20 8300 The specied MP Blade is not installed.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE
Get Command
Status
Executing/
Async
2E21 9008 The program product of Universal Volume
Manager is not installed.
SSB codes returned by raidcom add external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 401
raidcom add external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E21 9013 The program product of nondisruptive
migration is not installed.
Get Command
Status
Async 2E22 4100 The external volume group exists already.
CMDRJE Executing 2E22 4100 The external volume group exists already.
Get Command
Status
Async 2E23 0201 The operation cannot be performed because
the number of remote command devices that
can be created in the system exceeds the
maximum number.
Get Command
Status
Async 2E23 4102 Exceeded the number of mapping that can be
set per 1 port.
Get Command
Status
Async 2E23 4303 The operation cannot be performed because
the number of path in the path group exceeds
8.
Get Command
Status
Async 2E30 4119 The external volume cannot be added because
the number of virtual volumes that can be
created in the system exceeded the maximum
number.
Get Command
Status
Async 2E30 411B The external volume having the Data Direct
Mapping attribute cannot be created because
the size of the specied external LU is less than
8GB.
Get Command
Status
Async 2E30 4201 The specied external LU has mapped already.
CMDRJE Executing 2E30 8400 The port attribute is not External.
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
Get Command
Status
Async 2E31 4000 The specied external storage LU is the device
of not supported.
Get Command
Status
Async 2E31 4001 The specied external storage system is not
supported.
Get Command
Status
Async 2E31 4002 The specied external volume does not support
nondisruptive migration.
SSB codes returned by raidcom add external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 402
raidcom add external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E31 9000 The usage capacity exceeds the license capacity
of the program product.
CMDRJE Executing 2EDA 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EDA 41FA An internal error occurred.
CMDRJE Executing 2EF3 4102 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
selected port is for NAS Platform (User LU).
SSB codes returned by raidcom check_ext_storage external_grp
raidcom check_ext_storage external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4100 The external volume group is not in the
eective range.
CMDRJE Executing 2E10 4301 The specied external volume has already
disconnected the path, or is in the process of
checking path.
CMDRJE Executing 2E11 001B The target LDEV is blocked.
CMDRJE Executing 2E11 4000 The path for the specied external path is in
the state of disconnected.
CMDRJE Executing 2E11 4302 All the paths for the specied external path are
blocked.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E20 4300 There is no external path.
CMDRJE Executing 2E30 001E Online from the mainframe host.
SSB codes returned by raidcom check_ext_storage external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 403
raidcom check_ext_storage external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2EDA 0905 An internal error occurred by the operation of
external path.
Call customer support.
CMDRJE Executing 2EDA 0905 An internal error occurred by the operation of
external volume.
Call customer support.
SSB codes returned by raidcom delete external_grp
raidcom delete external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4100 The external volume group # is in the eective
range.
Get Command
Status
Async 2E10 0012 LDEVs in the external volume group are devices
that have a CC/XRC attributes.
CMDRJE Executing 2E11 0153 The specied external volume group is used in
another operation.
Get Command
Status
Async 2E11 4103 Destage is not executed.
Get Command
Status
Async 2E11 4104 The external volume is used as Compatible
FlashCopy® V2.
Get Command
Status
Async 2E11 4105 The specied external volume cannot be
deleted because audit logs for the system disk
are being used.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 8010 The storage system is in internal process, or the
conguration changing processes are
conicting.
Get Command
Status
Async 2E11 8108 The operation cannot be performed because
there is blocked part in the system.
SSB codes returned by raidcom delete external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 404
raidcom delete external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E30 0007 LU path is dened to LDEV in the external
volume group.
Get Command
Status
Async 2E30 0057 The external volume is used as a system disk.
Get Command
Status
Async 2E30 4101 The external volume is used as LUSE.
Get Command
Status
Async 2E30 4102 The external volume is used as a TrueCopy pair
volume.
Get Command
Status
Async 2E30 4103 The external volume is used as a TrueCopy pair
volume.
Get Command
Status
Async 2E30 4104 The specied volume is used as a ShadowImage
pair volume, a Thin Image pair volume, or a
FICON® Data Migration volume.
Get Command
Status
Async 2E30 4105 The specied volume is used as a ShadowImage
pair volume, a Thin Image pair volume, or a
FICON® Data Migration volume.
Get Command
Status
Async 2E30 4106 There is the volume that has path denition.
Get Command
Status
Async 2E30 4107 The external volume is used as a ShadowImage
reserved VOL.
Get Command
Status
Async 2E30 4108 The external volume is used as aVolume
Migration reserved VOL.
Get Command
Status
Async 2E30 4109 There is a mainframe path group setting in the
external volume.
Get Command
Status
Async 2E30 410A There is a Data Retention Utility setting in the
external volume.
Get Command
Status
Async 2E30 410B There is a mainframe LDEV Guard setting in the
external volume.
Get Command
Status
Async 2E30 410C There is a Volume Security setting in the
external volume.
SSB codes returned by raidcom delete external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 405
raidcom delete external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 410D The external volume is used as a Universal
Replicator pair volume.
Get Command
Status
Async 2E30 410E The external volume is used as a Universal
Replicator journal volume.
Get Command
Status
Async 2E30 410F The external volume is used as a pool-VOL.
Get Command
Status
Async 2E30 4110 The external volume is used as a pool-VOL.
Get Command
Status
Async 2E30 4111 The external volume is used as aVolume
Migration VOL.
Get Command
Status
Async 2E30 4112 The external volume is used as aVolume
Migration VOL.
Get Command
Status
Async 2E31 0001 The target external group cannot be deleted
because a quorum disk exists in it.
CMDRJE Executing 2EDA 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EE8 FFFB An internal error occurred.
Call customer support.
Get Command
Status
Async 2EFF 41FF An internal error occurred.
Call customer support.
SSB codes returned by raidcom check_ext_storage path
raidcom check_ext_storage path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4500 The path group is not in the enabled range.
CMDRJE Executing 2E00 8400 The value of the port is not enabled.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
SSB codes returned by raidcom check_ext_storage path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 406
raidcom check_ext_storage path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 4301 The specied external volume has already
disconnected the path, or is in the process of
checking path.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
Get Command
Status
Async 2E11 001B The target LDEV is blocked.
Get Command
Status
Async 2E11 4000 The path for the specied external path is in
the state of disconnected.
Get Command
Status
Async 2E11 4302 All the paths for the specied external path are
blocked.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 4100 There is no specied external volume.
Get Command
Status
CMDRJE
Async/
Executing
2E20 4300 There is no specied path.
CMDRJE Executing 2E20 4400 WWN is not registered.
CMDRJE Executing 2E20 4500 This command cannot be operated due to one
of the following reasons:
■There is no path group.
■external_wwn is not dened.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
Get Command
Status
Async 2E30 001E Online from the mainframe host.
CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
CMDRJE Executing 2EDA 00EE The command cannot be accepted. After a
while, execute the same command.
SSB codes returned by raidcom check_ext_storage path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 407
raidcom check_ext_storage path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2EDA 0905 An internal error occurred by the operation of
external path.
Call customer support.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom disconnect external_grp
raidcom disconnect external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4100 The external volume group is not in the
eective range.
CMDRJE Executing 2E10 0000 The specied LDEV is used for a ShadowImage
pair.
CMDRJE Executing 2E10 0001 It is used as a TrueCopy or Universal Replicator
pair.
CMDRJE Executing 2E10 0003 A ShadowImage pair, a Thin Image/Copy-on-
Write Snapshot pair or a Compatible
FlashCopy® V2 relationship or in status of
splitting or pending exists.
CMDRJE Executing 2E10 0004 The specied LDEV is used for a Thin Image
pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0008 It is used as a system disk.
CMDRJE Executing 2E10 0012 It is used as a concurrent copy or XRC.
CMDRJE Executing 2E10 0062 The specied LDEV is used as the primary
volume of a global-active device (GAD) pair.
CMDRJE Executing 2E10 0063 The specied LDEV is used as the secondary
volume of aGAD pair.
SSB codes returned by raidcom disconnect external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 408
raidcom disconnect external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 4100 The specied external volume group is in the
state of disconnected.
CMDRJE Executing 2E10 4102 The specied external device is in the state of
disconnected.
CMDRJE Executing 2E10 4301 The specied external volume has already
disconnected the path, or is in the process of
checking path.
CMDRJE Executing 2E11 0007 It is in the state of shredding.
CMDRJE Executing 2E11 001B The target LDEV is blocked.
CMDRJE Executing 2E11 4000 The path for the specied external path is in
the state of disconnected.
CMDRJE Executing 2E11 410D The DP-VOL with the Data Direct Mapping
attribute which is allocated to the specied
external volume is not blocked.
CMDRJE Executing 2E11 4302 All the paths for the specied external path are
blocked.
CMDRJE Executing 2E11 6005 The specied external volume belongs to a
Thin Image or Copy-on-Write Snapshot where
the pair in the PSUS status exists.
CMDRJE Executing 2E11 800E The operation cannot be performed because
the internal processing is in progress. Wait for
a while, then retry the operation.
CMDRJE Executing 2E20 4100 There is no specied external volume.
CMDRJE Executing 2E20 4300 There is no specied path.
CMDRJE Executing 2E30 000A It is included the Hitachi Dynamic Provisioning
volume that is associated with a pool.
CMDRJE Executing 2E30 000C The specied LDEV is used as a quorum disk.
CMDRJE Executing 2E30 000E It is used as a pool volume.
CMDRJE Executing 2E30 000F It is used as a journal volume.
CMDRJE Executing 2E30 0014 It is used as a reserved volume of Volume
Migration.
CMDRJE Executing 2E30 001A Volume Security is set.
SSB codes returned by raidcom disconnect external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 409
raidcom disconnect external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 001C It is used as a remote command device.
CMDRJE Executing 2E30 001E Online from the mainframe host.
CMDRJE Executing 2E30 004E This is a volume that the Data Retention Utility
is set.
CMDRJE Executing 2E30 0061 The Dynamic Provisioning volume not in the
blocked state is included in the Dynamic
Provisioning that is associated with the pool to
which the pool volume is belongs.
CMDRJE Executing 2EDA 0000 An internal error occurred by the operation of
disconnecting the external volume.
Call customer support.
CMDRJE Executing 2EDA 0905 An internal error occurred by the operation of
external volume.
Call customer support.
SSB codes returned by raidcom modify external_grp
raidcom modify external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4100 The external volume group is not in the
eective range.
CMDRJE Executing 2E00 410F The specied value of the load balance mode is
invalid.
CMDRJE Executing 2E00 4110 The specied value of the ALUA mode is invalid.
CMDRJE Executing 2E00 8301 MP Blade ID is not in the eective range.
CMDRJE Executing 2E10 4202 The operation cannot be performed because
the volume used for data migration is reserved
from the host.
CMDRJE Executing 2E10 8300 The specied MP Blade is blocked.
SSB codes returned by raidcom modify external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 410
raidcom modify external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 4107 The attribute cannot be changed because
Volume Migration is being executed.
CMDRJE Executing 2E11 4303 The load balance mode cannot be changed
because the alternative path mode is set to
Single.
CMDRJE Executing 2E11 800F The load balance mode cannot be changed
because microcodes of multiple versions are in
the storage system.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E20 8300 The specied MP Blade is not installed.
CMDRJE Executing 2E30 4104 The attribute cannot be changed because the
external volume is used as a ShadowImage pair
volume.
CMDRJE Executing 2E30 410D The external volume is used as a Universal
Replicator pair volume.
CMDRJE Executing 2E30 411A The external volume is used as a TrueCopy
volume.
CMDRJE Executing 2E30 411C The operation cannot be performed because
the external volume is being used as a global-
active device pair.
CMDRJE Executing 2E31 000C Cache mode cannot be changed because there
is an LDEV that Cache Residency Manager bind
mode is set.
CMDRJE Executing 2E31 4101 Cache mode cannot be changed because the
specied external volume includes a pool
volume or an LDEV that is used by LUSE.
CMDRJE Executing 2E31 4107 The cache mode cannot be changed because
the specied external volume is one of the
following.
■A pool volume in the pool that consists of
both external volumes and internal volumes.
■A pool volume in the pool whose multi-tier
pool option is enabled.
SSB codes returned by raidcom modify external_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 411
raidcom modify external_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E31 4108 The attribute of the external volume cannot be
changed from the current cache mode to the
specied cache mode.
CMDRJE Executing 2E31 4109 The attribute cannot be changed because the
external volume group is not mapped for
online data migration.
CMDRJE Executing 2EDA 00F1 The specied command cannot be accepted
because the command is not supported.
CMDRJE Executing 2EDA 0905 An internal error occurred on the changing of
an external volume option.
Call customer support.
CMDRJE Executing 2EF3 0002 The specied parameter is incorrect. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom modify port -loop_id
raidcom modify port -loop_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 0404 An LU path or a logical path has been dened.
CMDRJE Executing B955 040F An internal error occurred.
CMDRJE Executing B955 044C The specied AL-PA is invalid.
CMDRJE Executing B955 054E The specied topology is invalid.
CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specied
when specifying a topology of the package for
Fibre Channel over Ethernet.
CMDRJE Executing B955 05A7 The other than "P-to-P (point to point)" cannot
be specied when specifying a topology of the
package for Fibre Channel over Ethernet.
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
SSB codes returned by raidcom modify port -loop_id
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 412
raidcom modify port -loop_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 104F The program product is not installed.
CMDRJE Executing B955 113D Invalid host speed is set for the 4Gbps bre
adapter. The available host speeds are AUTO,
1G, 2G, and 4G only.
CMDRJE Executing B955 113F Invalid host speed is set for the 8Gbps bre
adapter. The available host speeds are AUTO,
2G, 4G, and 8G only.
CMDRJE Executing B955 11A5 The other than "10G" cannot be specied when
specifying a host speed of the package for Fibre
Channel over Ethernet.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
selected port is for NAS Platform (User LU).
SSB codes returned by raidcom modify port -topology
raidcom modify port -topology
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 0404 An LU path or a logical path has been dened.
CMDRJE Executing B955 040F An internal error occurred.
CMDRJE Executing B955 044C The specied AL-PA is invalid.
CMDRJE Executing B955 054E The specied topology is invalid.
CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specied
when specifying a topology of the package for
Fibre Channel over Ethernet.
CMDRJE Executing B955 05A7 The other than "P-to-P (point to point)" cannot
be specied when specifying a topology of the
package for Fibre Channel over Ethernet.
SSB codes returned by raidcom modify port -topology
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 413
raidcom modify port -topology
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 104F The program product is not installed.
CMDRJE Executing B955 113D Invalid host speed is set for the 4Gbps bre
adapter. The available host speeds are AUTO,
1G, 2G, and 4G only.
CMDRJE Executing B955 113F Invalid host speed is set for the 8Gbps bre
adapter. The available host speeds are AUTO,
2G, 4G, and 8G only.
CMDRJE Executing B955 11A5 The other than "10G" cannot be specied when
specifying a host speed of the package for Fibre
Channel over Ethernet.
CMDRJE Executing B955 12AF The combination of the specied topology FC-
AL and the host speed set for the bre channel
adapter is not supported. See the Provisioning
Guide of your system for supported
combinations of data transfer speed and type
of connection.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
selected port is for NAS Platform (User LU).
SSB codes returned by raidcom modify port -security_switch
raidcom modify port -security_switch
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 0404 An LU path or a logical path has been dened.
CMDRJE Executing B955 040F An internal error occurred.
CMDRJE Executing B955 044C The specied AL-PA is invalid.
CMDRJE Executing B955 054E The specied topology is invalid.
SSB codes returned by raidcom modify port -security_switch
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 414
raidcom modify port -security_switch
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specied
when specifying a topology of the package for
Fibre Channel over Ethernet.
CMDRJE Executing B955 05A7 The other than "P-to-P (point to point)" cannot
be specied when specifying a topology of the
package for Fibre Channel over Ethernet.
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 104F The program product is not installed.
CMDRJE Executing B955 113D Invalid host speed is set for the 4Gbps bre
adapter. The available host speeds are AUTO,
1G, 2G, and 4G only.
CMDRJE Executing B955 113F Invalid host speed is set for the 8Gbps bre
adapter. The available host speeds are AUTO,
2G, 4G, and 8G only.
CMDRJE Executing B955 11A5 The other than "10G" cannot be specied when
specifying a host speed of the package for Fibre
Channel over Ethernet.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
selected port is for NAS Platform (User LU).
SSB codes returned by raidcom add ldev
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 0002 The specied capacity is not in the eective
range.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 415
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0003 SSID is not in the eective range.
CMDRJE Executing 2E00 000D The value of the specied emulation type is
invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E00 000E The specied emulation type is not supported
in this command.
Get Command
Status
Async 2E00 0010 The operation cannot be performed because
the specied LDEV number is already used.
Get Command
Status
Async 2E00 0013 The operation cannot be performed because
there are not enough cache management
devices.
Get Command
Status
Async 2E00 0014 Cannot create because the specied capacity is
invalid.
CMDRJE Executing 2E00 0019 The capacity in the case of specifying a
emulation type of the mainframe series must
be dividable by the cylinder.
CMDRJE Executing 2E00 001A The capacity when 3390-V emulation type is
specied must be divisible by page unit.
CMDRJE Executing 2E00 001C When you specify emulation type for open
system, you cannot specify the size by the
cylinder.
CMDRJE
Get Command
Status
Executing/
Async
2E00 0025 The following external volume cannot be
created because the capacity which is specied
with LBA is not same as the size of the external
volume group.
■An external volume for the online data
migration.
■An external volume having the Data Direct
Mapping attribute.
CMDRJE Executing 2E00 0026 The capacity must be specied because LDEVs
are in the parity group (or the external volume
group).
CMDRJE Executing 2E00 0027 The capacity must be specied.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 416
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 002D The emulation type of the mainframe cannot
be specied because the virtual volume is set
for the specied LDEV.
CMDRJE Executing 2E00 002F The specied value of the Full Allocation is
invalid.
Get Command
Status
Async 2E00 0030 Full Allocation cannot be specied to the
specied LDEV because the emulation type is
not supported.
CMDRJE Executing 2E00 0101 The parity group number or the external group
number is not in the eective range.
Get Command
Status
Async 2E00 1005 Failed to restore the LDEV that is created to
external volume group.
CMDRJE Executing 2E00 6000 The specied pool ID is not in the eective
range.
CMDRJE Executing 2E00 7000 The specied CLPR ID is not in the eective
range.
CMDRJE Executing 2E00 8301 MP Blade ID is not in the eective range.
CMDRJE Executing 2E02 0201 The specied protection type is not supported.
Get Command
Status
Async 2E02 0203 The specied operation cannot be performed
because it is an external volume.
Get Command
Status
Async 2E02 0204 The operation cannot be performed because
the specied capacity is less than 8 GB.
Get Command
Status
Async 2E02 0205 Full Allocation cannot be performed because
the pool uses the LDEV belonging to a parity
group with accelerated compression enabled.
CMDRJE
Get Command
Status
Executing/
Async
2E02 A601 The operation cannot be performed because
either of the following applies:
■The specied request ID is invalid.
■A request ID managed by another session is
specied.
CMDRJE Executing 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 417
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 001F The operation cannot be performed because
the total capacity of virtual volumes for
Dynamic Tiering or active ash in the system
exceeds the maximum.
Get Command
Status
Async 2E10 002D The operation cannot be performed because
the specied LDEV is a journal volume.
Get Command
Status
Async 2E10 005A The operation cannot be performed because
the following information of the migration
source and the migration target does not
match.
■serial number
■product ID
■emulation type
■SSID
■LUSE
■CVS conguration
■LDEV number
Get Command
Status
Async 2E10 0064 The specied pool volume is already linked with
the virtual volume having the Data Direct
Mapping attribute.
Get Command
Status
Async 2E10 0100 The volumes cannot be added because the
encryption value of the key number that is set
to encryption ECC is invalid.
Get Command
Status
Async 2E10 0101 The volumes cannot be added because the
check sum of the encryption key does not
match.
Get Command
Status
Async 2E10 020E The specied LDEV is not in the status where
the capacity saving setting can be enabled.
Get Command
Status
Async 2E10 6014 The operation cannot be performed because
the specied pool status is incorrect.
Get Command
Status
Async 2E10 601B The free space in the specied pool is
insucient.
Get Command
Status
Async 2E10 601C Full Allocation cannot be performed because
the pool volume is being deleted.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 418
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 6020 The deduplication function cannot be used in
the specied pool.
Get Command
Status
Async 2E10 6021 The deduplication system data volume dened
for the specied pool is not in the normal
status.
Get Command
Status
Async 2E10 6022 The operation cannot be performed because
the deduplication system data volume of the
pool linked with the specied LDEV is blocked.
Get Command
Status
Async 2E11 0003 An LDEV that is in the state of shredding is
included in the parity group of the target LDEV.
Get Command
Status
Async 2E11 0004 An LDEV that is in the state of formatting is
included in the parity group of the target LDEV.
Get Command
Status
Async 2E11 0005 An LDEV that is in the state of executing quick
format is included in the parity group of the
target LDEV.
Get Command
Status
Async 2E11 001B The specied LDEV is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used in another
operation.
Get Command
Status
Async 2E11 0102 The parity group of the target LDEV is in the
state of correction copy.
CMDRJE Executing 2E11 0153 The parity group or the external volume group
that the specied LDEV is belongs to is used in
another operation.
Get Command
Status
Async 2E11 0205 The operation cannot be performed because
the total capacity of provisioning virtual
volumes and deduplication system data
volumes dened in the specied pool exceeds
the maximum of reserved pool capacity.
Get Command
Status
Async 2E11 0209 The operation cannot be performed due to a
cache memory failure or maintenance work
being performed.
CMDRJE
Get Command
Status
Executing/
Async
2E11 2208 The operation cannot be performed because
you do not have the resource group authority.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 419
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E11 2209 The operation cannot be performed because
there is no LDEV ID that can be used in a
system or resource group.
Get Command
Status
Async 2E11 6007 The operation cannot be performed because
the specied pool volume is blocked.
Get Command
Status
Async 2E11 6008 The operation cannot be performed because
the pool linked with the specied LDEV is in the
unusable status.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 8010 The storage system is in internal process, or the
conguration changing processes are
conicting.
Get Command
Status
Async 2E11 8105 Cache segment size is incorrect.
Get Command
Status
Async 2E11 8108 The operation cannot be performed because
there is blocked part in the system.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing/
Async
2E11 A602 The operation cannot be performed because
the internal processing is in progress. After a
while, perform the operation again.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE
Get Command
Status
Executing/
Async
2E20 0007 The specied CLPR does not exist.
CMDRJE Executing 2E20 0100 There is no parity group.
CMDRJE
Get Command
Status
Executing/
Async
2E20 6000 Pool ID is invalid.
Get Command
Status
Async 2E20 8300 The specied MP Blade is not installed.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 420
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 6003 There is not enough free shared memory
space.
Get Command
Status
Async 2E21 8103 The operation cannot be performed because
the capacity of shared memory is insucient.
Get Command
Status
Async 2E21 810A The shared memory is not installed.
Get Command
Status
Async 2E21 8300 Package for Mainframe is required when you
specify the emulation type of mainframe.
Get Command
Status
Async 2E21 9000 The program product is not installed.
CMDRJE Executing 2E21 9001 The program product is not installed.
CMDRJE Executing 2E21 9002 The program product is not installed.
CMDRJE/Get
Command Status
Executing/
Async
2E21 9004 The program product is not installed.
CMDRJE Executing 2E21 900E Hitachi Compatible Software for IBM®
FlashCopy® SE program product is not installed.
CMDRJE Executing 2E22 0001 LDEV is already dened.
CMDRJE Executing 2E22 000F You cannot create the volume because the size
of the specied external volume group exceeds
the maximum capacity of the external volume
for online data migration.
CMDRJE
Get Command
Status
Executing/
Async
2E23 0001 The number exceeds the maximum number of
LDEV that can be created in the current system
conguration.
Get Command
Status
Async 2E30 0006 The specied LDEV is used in the FICON® Data
Migration.
CMDRJE Executing 2E30 0020 The specied SSID is already used in another
CU.
CMDRJE Executing 2E30 0021 The SSID is allocated to the CU already.
Get Command
Status
Async 2E30 0025 The specied volume is used as an alias device
in Compatible PAV.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 421
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 0026 An LDEV of another emulation type is allocated
in the range where the number is divided into
each 32LDEVs.
CMDRJE Executing 2E30 004C The emulation type that cannot be mixed with
is specied.
CMDRJE Executing 2E30 004D The number of LDEVs exceeds the maximum
number of LDEVs that can be created in the
parity group or the external volume group.
CMDRJE Executing 2E30 0098 The volume which is specied as a pool volume
must have a Data Direct Mapping attribute.
Get Command
Status
Async 2E30 0099 The specied LDEV is a volume for which the
Data Direct Mapping attribute is enabled.
Get Command
Status
Async 2E30 009A The page reservation cannot be set for the
specied LDEV with the specied operation.
Get Command
Status
Async 2E30 009B The operation cannot be performed because
the page reservation is set for the specied
LDEV.
CMDRJE Executing 2E30 0104 There is not enough amount of free space that
is specied in the parity group or the external
volume group.
CMDRJE Executing 2E30 0105 The location is out of the range that can be
specied.
CMDRJE Executing 2E30 0106 Volume whose emulation type is 3390-V cannot
be created in RAID1 parity group.
CMDRJE
Get Command
Status
Executing/
Async
2E30 4119 The virtual volume cannot be added because
the number of virtual volumes that can be
created in the system exceeded the maximum
number.
CMDRJE
Get Command
Status
Executing/
Async
2E30 6003 The specied pool is the pool for Thin Image or
Copy-on-Write Snapshot.
Get Command
Status
Async 2E30 6012 The operation cannot be performed because
the specied pool is used for Data Direct
Mapping.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 422
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 6014 The operation cannot be performed because
the specied pool is for active ash.
Get Command
Status
Async 2E31 6003 The operation cannot be performed with the
specied pool type.
CMDRJE Executing 2E31 6007 TSE-VOL cannot be created because of the
following conditions.
■The specied pool is other than HDPz pool.
■The specied emulation type is other than
3390-A.
CMDRJE Executing 2E31 6008 TSE-VOL cannot be created in combination with
the specied pool ID and the CU number of
LDEV.
You must specify the even CU number for the
pool of even pool ID, and the odd CU number
for the pool of odd pool ID.
Get Command
Status
Async 2E31 6009 A TSE-VOL cannot be created in the specied
pool for Dynamic Tiering or active ash.
CMDRJE
Get Command
Status
Executing/
Async
2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE
Get Command
Status
Executing/
Async
2EBE 9E01 The specied parameter is invalid.
CMDRJE Executing 2EE8 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EE8 FFFB An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 0002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 423
raidcom add ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
ERANGE Result
too large
Executing - - The value of the capacity is invalid.
SSB codes returned by raidcom delete journal
raidcom delete journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The number of specied LDEV is invalid.
Get Command
Status
Async 2E00 0023 The specied volume capacity is too small.
CMDRJE Executing 2E00 5000 The specied journal ID is exceeds the range.
Get Command
Status
Async 2E10 0011 The specied volume is not installed or cannot
be used.
Get Command
Status
Async 2E10 0053 The specied volume is used in maintenance
operation.
Get Command
Status
Async 2E10 5000 The specied operation failed because the
journal or mirror is not in the operable status.
Get Command
Status
Async 2E10 5010 The journal volume cannot be deleted with the
specied journal status.
Get Command
Status
Async 2E11 800B The operation cannot be performed because it
is in the state of start-up.
Get Command
Status
Async 2E11 800E The operation cannot be performed because
the internal processing is in progress. Wait for a
while, then retry the operation.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E13 5002 The specied LDEV is not in the journal.
CMDRJE Executing 2E20 5000 The specied journal ID is not registered.
Get Command
Status
Async 2E21 5000 The operation failed because the specied
journal is not registered.
SSB codes returned by raidcom delete journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 424
raidcom delete journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 8104 The journal volume cannot be added, or the
journal cannot be added to the extended
consistency group due to insucient capacity
of the shared memory.
CMDRJE Executing 2E21 8105 The shared memory for Universal Replicator is
not installed.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
Get Command
Status
Async 2E30 0062 The specied volume cannot be used as a
journal volume because it is an external volume
that can execute the I/O suppression mode.
Get Command
Status
Async 2E30 5002 The specied journal cannot be deleted
because there are data volumes.
CMDRJE Executing 2EE4 08E6 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EE4 50EE An internal error occurred.
Call customer support.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add journal
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The value of LDEV number is invalid.
CMDRJE Executing 2E00 0018 A new journal volume cannot be registered
because the number of journal volume exceeds
the maximum that can be registered.
Get Command
Status
Async 2E00 0023 The specied volume capacity is too small.
SSB codes returned by raidcom add journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 425
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 8301 The specied MP Blade ID is invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E10 0000 The specied volume is already used by
another program product.
CMDRJE
Get Command
Status
Executing/
Async
2E10 0011 The specied volume is not installed or cannot
be used.
Get Command
Status
Async 2E10 001A The specied volume is connected from the
mainframe host.
CMDRJE
Get Command
Status
Executing/
Async
2E10 001B There is a PIN slot in the journal volume.
CMDRJE
Get Command
Status
Executing/
Async
2E10 001C The specied volume cannot be registered as a
journal volume because it is in shredding. Wait
until the shredding operation is completed,
then retry the operation.
Get Command
Status
Async 2E10 0053 The specied volume is used in maintenance
operation.
Get Command
Status
Async 2E10 0056 The specied volume cannot be used as the
journal volume because the virtual LDEV ID is
deleted.
Get Command
Status
Async 2E10 0057 The specied volume cannot be used as the
journal volume because it is the virtual volume.
Get Command
Status
Async 2E10 5000 The specied operation failed because the
journal or mirror is not in the operable status.
Get Command
Status
Async 2E11 800B The operation cannot be performed because it
is in the state of start-up.
Get Command
Status
Async 2E11 800E The operation cannot be performed because
the internal processing is in progress. Wait for a
while, then retry the operation.
CMDRJE
Get Command
Status
Executing/
Async
2E11 810A Abnormal cache status.
SSB codes returned by raidcom add journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 426
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 8300 The specied MP Blade is not installed.
Get Command
Status
Async 2E21 5000 The operation failed because the specied
journal is not installed.
Get Command
Status
Async 2E21 8104 The journal volume cannot be added, or the
journal cannot be added to the extended
consistency group due to insucient capacity
of the shared memory.
CMDRJE Executing 2E21 8105 The shared memory for Universal Replicator is
not installed.
Get Command
Status
Async 2E21 9000 A journal volume cannot be registered, or a
journal cannot be added to the extended
consistency group because the program
product of Universal Replicator or Hitachi
Universal Replicator software for Mainframe is
not installed.
Get Command
Status
Async 2E23 0005 A new journal volume cannot be registered, or
the number of selected volumes is too many.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
Get Command
Status
Async 2E23 003E The operation failed because the multiple LDKC
numbers cannot be mixed in the journal.
Get Command
Status
Async 2E23 5000 The operation failed because the number of
journals in the journal or the extended
consistency group exceeds the maximum.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0005 The specied volume cannot be used as a
journal volume because it is set by Cache
Residency Manager or Cache Residency
Manager for Mainframe.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0006 The specied volume cannot be used because
it is used in FICON(R) Data Migration.
SSB codes returned by raidcom add journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 427
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E30 0007 A path is dened in the specied volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 000C The operation failed because the specied
volume is a quorum disk.
CMDRJE
Get Command
Status
Executing/
Async
2E30 000D The specied volume cannot be used as a
journal volume because it is a system disk.
Get Command
Status
Async 2E30 000E The operation failed because the specied
volume is a pool volume of Dynamic
Provisioning.
Get Command
Status
CMDRJE
Async/
Executing
2E30 000F The specied volume is already used as a
journal volume or a data volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0010 The specied volume is used as a command
device.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0013 The specied volume cannot be used as a
journal volume because it is a LUSE volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0019 The specied volume cannot be used as a
journal volume because it is set by Data
Retention Utility or .
CMDRJE
Get Command
Status
Executing/
Async
2E30 001A Using the specied volume is prohibited by
Volume Security.
CMDRJE Executing 2E30 0035 The internal volumes and external volumes
exist in the specied journal.
Get Command
Status
Async 2E30 0040 The emulation type of the specied volume is
not supported. Or, the combination of an
emulation type of the journal volume is
incorrect.
SSB codes returned by raidcom add journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 428
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 0041 The volume cannot be registered as a journal
volume because the CLPR ID of the specied
volume diers from the CLPR ID of the
registered journal volume.
CMDRJE Executing 2E30 005F The specied LDEV is a remote command
device.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0062 The specied volume cannot be used as a
journal volume because it is an external volume
that can execute the I/O suppression mode.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0064 The specied volume is a reserved volume of a
mainframe host.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0065 The specied volume is used by XRC.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0067 The specied volume is a volume of Just in Time
(On-demand) function.
Get Command
Status
Async 2E30 0068 The specied volume cannot be used as a
journal volume because it is used by
Compatible PAV.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0070 The resource group ID of the specied volume
cannot be registered because the resource
group ID is dierent from the resource group ID
of the other journal volume in the specied
journal group.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
Get Command
Status
Async 2E30 0084 The specied LDEV cannot be used as a journal
volume because the size of the LDEV is less
than the minimum capacity of journal volume.
SSB codes returned by raidcom add journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 429
raidcom add journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E30 0086 The operation cannot be performed because
the specied volume is not the Dynamic
Provisioning V-VOL.
Get Command
Status
Async 2E30 0208 The operation cannot be performed because
the specied LDEV is a volume for which
capacity saving setting is enabled or a
deduplication system data volume.
CMDRJE Executing 2EE4 08E6 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing/
Async
2EE4 50EE An internal error occurred.
Call customer support.
CMDRJE
Get Command
Status
Executing/
Async
2EE4 FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 5002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom modify journal
raidcom modify journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E00 0000 The specied volume number is out of eective
range.
CMDRJE Executing 2E00 0023 The specied volume capacity is too small.
CMDRJE Executing 2E00 5000 The specied journal ID exceeds the range.
SSB codes returned by raidcom modify journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 430
raidcom modify journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 500B The specied path blocked path monitoring is
not in the valid range.
CMDRJE Executing 2E00 8301 The specied MP Blade ID is invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E02 5201 The specied mirror ID is out of eective range.
CMDRJE
Get Command
Status
Executing/
Async
2E10 0011 The specied volume is not installed or cannot
be used.
Get Command
Status
Async 2E10 021C The specied remote command device cannot
be operated because it is blocked.
Get Command
Status
Async 2E10 021D No more mirrors can be assigned to the
specied remote command device.
Get Command
Status
Async 2E10 021E The operation cannot be performed because
the number of remote command devices that
can be assigned to the mirror exceeds the
maximum.
CMDRJE Executing 2E10 5000 The specied operation failed because the
journal or mirror is not in the operable status.
CMDRJE Executing 2E10 5006 The specied operation failed because the
mirror of journal is not in the operable status.
CMDRJE Executing 2E10 8300 The specied MP Blade is blocked.
Get Command
Status
Async 2E11 4306 The operation cannot be performed due to a
temporary path failure.
Get Command
Status
Async 2E11 5201 Another remote command device is already
assigned to the specied mirror.
Get Command
Status
Async 2E11 5202 The operation cannot be performed because
the mirror of the journal is not in the operable
status.
Get Command
Status
Async 2E11 5203 The operation cannot be performed because
the specied mirror is not available.
SSB codes returned by raidcom modify journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 431
raidcom modify journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 5204 The operation cannot be performed because
the remote command device is not assigned to
the specied mirror.
Get Command
Status
Async 2E11 5205 The assignment of the remote command device
failed because the Universal Replicator pair in
the specied mirror is cooperating with the
global-active device pair.
CMDRJE
Get Command
Status
Executing/
Async
2E11 800B The operation cannot be performed because it
is in the state of start-up.
Get Command
Status
Async 2E11 800E The operation cannot be performed because
the internal processing is in progress. Wait a
while, then retry the operation.
Get Command
Status
Async 2E11 8801 The operation cannot be performed because
the remote command device does not match
the serial number of the mirror.
CMDRJE Executing 2E11 9400 The operation cannot be accepted. Wait a
while, then execute the command again.
Get Command
Status
Async 2E13 5003 The operation cannot be performed because
the specied journal is not in a 3DC cascade or
3DC multi target conguration.
CMDRJE Executing 2E20 0000 The specied volume is not installed.
CMDRJE Executing 2E20 5000 The specied journal ID is not registered.
CMDRJE
Get Command
Status
Executing/
Async
2E21 5000 The operation failed because the specied
journal is not registered.
CMDRJE
Get Command
Status
Executing/
Async
2E21 8104 The journal volume cannot be added, or the
journal cannot be added to the extended
consistency group due to insucient capacity
of the shared memory.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
Get Command
Status
Async 2E30 0062 The specied volume cannot be used as a
journal volume because it is an external volume
that can execute the I/O suppression mode.
SSB codes returned by raidcom modify journal
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 432
raidcom modify journal
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 020A The operation cannot be performed because
the specied volume is not a remote command
device.
CMDRJE Executing 2E30 5001 The timer type cannot be changed because the
specied journal belongs to the extended
consistency group.
CMDRJE Executing 2E30 5003 The parameter of inow control cannot be
changed because the specied journal is not a
primary journal.
CMDRJE Executing 2E30 5005 The cache mode option or the data overow
monitoring time cannot be changed because
the specied journal is used by both the
primary and the secondary journals.
CMDRJE
Get Command
Status
Executing/
Async
2EE4 50EE An internal error occurred.
Call customer support.
CMDRJE
Get Command
Status
Executing/
Async
2EE4 FEEC An internal error occurred.
Call customer support.
Get Command
Status
Async 2EF3 3001 The remote storage system does not support
conguration operation for remote command
devices.
SSB codes returned by raidcom modify ldev
raidcom modify ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom modify ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 433
raidcom modify ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B906 An LDEV for which an LU path is set in NAS
Platform (User LU) cannot have the Command
Device attribute.
SSB codes returned by raidcom modify ldev -alua
raidcom modify ldev -alua
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E11 0059 The status of the GAD pair is not able to change
ALUA.
CMDRJE Executing 2E11 800F The operation cannot be performed because
the unsupported microcode version exists in
the system.
CMDRJE Executing 2E20 0000 The specied LDEV is not installed.
CMDRJE Executing 2E23 1001 The number of the host groups which can be
set by ALUA exceeded the maximum.
CMDRJE Executing 2EE8 FEEC An internal error occurred.
SSB codes returned by raidcom modify ldev -mp_blade_id
raidcom modify ldev -mp_blade_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 8301 MP Blade ID is not in the eective range.
CMDRJE Executing 2E10 8300 The specied MP Blade is blocked.
CMDRJE Executing 2E20 0000 LDEV is not installed.
SSB codes returned by raidcom modify ldev -alua
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 434
raidcom modify ldev -mp_blade_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 8300 The specied MP Blade is not installed.
SSB codes returned by raidcom delete device_grp
raidcom delete device_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E20 0000 LDEV is not installed.
CMDRJE Executing 2E20 0002 LDEV is not registered in the device group.
CMDRJE Executing 2E20 2100 A device group is not installed.
CMDRJE Executing 2E22 000E The number of LDEVs that can be deleted in a
operation exceeds the maximum. The number
of LDEVs that can be deleted includes the
number of LDEVs of a LUSE.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
SSB codes returned by raidcom add device_grp
raidcom add device_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E20 0000 LDEV is not installed.
CMDRJE Executing 2E22 0009 The number of device name in the system has
reached the maximum.
CMDRJE Executing 2E22 000A The device name of an LDEV is duplicated in the
system.
SSB codes returned by raidcom delete device_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 435
raidcom add device_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E22 000E The number of LDEVs that can be registered in
a operation exceeds the maximum. The
number of LDEVs that can be registered
includes the number of LDEVs of a LUSE.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
CMDRJE Executing 2E23 2100 It exceeds the number of device group in the
system.
CMDRJE Executing 2E30 0051 The LDEV to be allocated to the device group is
not set the device name.
CMDRJE Executing 2E30 0072 The specied resource group ID of the LDEV
cannot be registered because it is dierent
from other resource group ID of the LDEV in the
specied device group.
CMDRJE Executing 2EEA FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom modify ldev -ldev_name
raidcom modify ldev -ldev_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 0007 LDEV nickname is not specied.
CMDRJE Executing 2E20 0000 LDEV is not installed.
Invalid Character Executing - - Unavailable character is included in LDEV
nickname.
SSB codes returned by raidcom modify ldev -ldev_name
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 436
SSB codes returned by raidcom initialize ldev
raidcom initialize ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
Get Command
Status
Async 2E10 0000 The specied LDEV is used for a ShadowImage
pair.
Get Command
Status
Async 2E10 0001 The specied LDEV is used for a TrueCopy pair
or a Universal Replicator pair.
Get Command
Status
Async 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
Get Command
Status
Async 2E10 0004 The specied LDEV is used for a Thin Image pair
or a Copy-on-Write Snapshot pair.
Get Command
Status
Async 2E10 0008 The specied LDEV is used on the system disk.
Get Command
Status
Async 2E10 0010 LDEV is not blocked.
Get Command
Status
Async 2E10 0012 The specied LDEV is a CC/XRC attribute device.
Get Command
Status
Async 2E10 0062 The specied LDEV is used as the primary
volume of aGAD pair.
Get Command
Status
Async 2E10 0063 The specied LDEV is used as the secondary
volume of aGAD pair.
Get Command
Status
Async 2E10 0100 The formatting operation cannot be performed
because the encryption value of the key
number that is set to encryption ECC is invalid.
Get Command
Status
Async 2E10 0101 The formatting operation cannot be performed
because the check sum of the encryption key is
not coincident.
Get Command
Status
Async 2E10 0210 The specied LDEV cannot be operated because
capacity saving status is Failed.
Get Command
Status
Async 2E10 6022 The operation cannot be performed because
the deduplication system data volume of the
pool linked with the specied LDEV is blocked.
Get Command
Status
Async 2E11 0007 The LDEV is in shredding.
SSB codes returned by raidcom initialize ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 437
raidcom initialize ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 0009 The operation cannot be performed because
LDEV is now expanding.
Get Command
Status
Async 2E11 001E The operation cannot be performed because
the virtual disk space is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used in another
operation.
CMDRJE
Get Command
Status
Executing/
Async
2E11 0060 The operation failed because accelerated
compression of the parity group to which the
specied LDEV belongs is enabled.
Get Command
Status
Async 2E11 0102 The parity group of the target LDEV is in the
state of correction copy.
CMDRJE Executing 2E11 0153 The parity group or the external volume group
to which the specied LDEV belongs is used in
another operation.
CMDRJE Executing 2E11 0201 The operation cannot be performed because
the parity group format is not done for the
parity group to which the specied LDEV
belongs.
Get Command
Status
Async 2E11 6004 The operation of Dynamic Provisioning V-VOL
cannot be performed because there is a
blocked pool.
Get Command
Status
Async 2E11 6006 The operation of Dynamic Provisioning V-VOL
cannot be performed because there is a
blocked pool volume.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
Get Command
Status
Async 2E11 8010 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E14 0000 The processing stopped because aborting
processing is required.
CMDRJE Executing 2E20 0000 LDEV is not installed.
SSB codes returned by raidcom initialize ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 438
raidcom initialize ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 9011 The program product is not installed.
Get Command
Status
Async 2E22 0100 The quick format cannot be performed because
the total number of parity groups in which the
LDEVs in quick formatting or the LDEVs blocked
while quick formatting are implemented
exceeds the maximum number that can be
performed at the same time.
Get Command
Status
Async 2E30 000A The specied LDEV is used for a Dynamic
Provisioning.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
CMDRJE
Get Command
Status
Executing/
Async
2E30 000E The specied LDEV is used as a pool volume.
Get Command
Status
Async 2E30 000F The specied LDEV is used as a journal volume.
Get Command
Status
Async 2E30 001A Volume Security is set to the specied LDEV.
Get Command
Status
Async 2E30 002D Quick format cannot be performed because the
target LDEV is not an internal volume.
Get Command
Status
Async 2E30 004E The specied LDEV is a Data Retention Utility/
Volume Retention Manager attribute device.
Get Command
Status
Async 2E30 0061 The specied LDEV is a pool volume and the
pool volume include the Dynamic Provisioning
volume that is not in the blocked status.
Get Command
Status
Async 2E30 0074 The specied LDEV cannot be operated because
it is an external volume mapped for online data
migration.
CMDRJE Executing 2E30 0075 The specied ldev is used as the TSE-VOL.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
SSB codes returned by raidcom initialize ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 439
raidcom initialize ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 0209 The operation cannot be performed because
the specied LDEV is a volume for which
capacity saving setting is enabled.
Get Command
Status
Async 2E31 0001 Maintenance work cannot be performed
because the target LDEV is a quorum disk.
Get Command
Status
Async 2E31 0017 LDEV cannot be formatted because there is no
normal external path.
CMDRJE Executing 2EE8 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EE8 0A18 An internal error occurred.
CMDRJE
Get Command
Status
Executing/
Async
2EE8 FEEC An internal error occurred.
Call customer support.
CMDRJE
Get Command
Status
Executing/
Async
2EE8 FFFF An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 0002 The specied parameter is incorrect. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom initialize ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 440
SSB codes returned by raidcom modify ldev -command_device
raidcom modify ldev -command_device
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0000 The command device cannot be set to the
specied LDEV because of the following causes.
■The LDEV is used for a ShadowImage pair.
■The reserve attribute of a ShadowImage is
congured.
CMDRJE Executing 2E10 0001 The specied LDEV is used for a TrueCopy pair.
CMDRJE Executing 2E10 0002 The specied LDEV is used for a Universal
Replicator pair or a journal.
CMDRJE Executing 2E10 0004 The specied volume cannot be set because it
is used by a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0062 The specied LDEV is used as the primary
volume of aGAD pair.
CMDRJE Executing 2E10 0063 The specied LDEV is used as the secondary
volume of aGAD.
CMDRJE Executing 2E10 0201 The operation failed because the T10 PI
attribute of the specied LDEV is enabled.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E21 9000 The following settings cannot be performed
because the program product of LUN Manager
is not installed.
■Command device settings
■Command security settings
CMDRJE Executing 2E30 0004 The emulation type of the specied volume is
not OPEN volume.
CMDRJE Executing 2E30 0008 The command device cannot be set because
LDEV is used as a virtual volume of Thin Image
or Copy-on-Write Snapshot.
CMDRJE Executing 2E30 000C The specied volume cannot be set because it
is a quorum disk.
SSB codes returned by raidcom modify ldev -command_device
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 441
raidcom modify ldev -command_device
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 000D The specied volume cannot be set because it
is a system disk.
CMDRJE Executing 2E30 000E The specied volume cannot be set because it
is a pool volume.
CMDRJE Executing 2E30 0012 The specied LDEV cannot be released because
it is command device that is being used.
CMDRJE Executing 2E30 0013 The specied volume cannot be set because it
is a LUSE volume.
CMDRJE Executing 2E30 0014 The command device cannot be set to the
specied LDEV because of the following causes.
■It is used as aVolume Migration.
■The reserve attribute of aVolume Migration
is congured.
CMDRJE Executing 2E30 0019 The specied volume cannot be used as a
command device because it is set by a Data
Retention Utility.
CMDRJE Executing 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
CMDRJE Executing 2E30 0096 The specied LDEV is used as an ALU.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
CMDRJE Executing 2EE8 FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom modify ldev -command_device
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 442
SSB codes returned by raidcom modify ldev -ssid
raidcom modify ldev -ssid
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 0023 SSID cannot be changed because there are
LDEVs in the boundary where the specied
LDEV belongs.
CMDRJE Executing 2E22 7201 The specied SSID is used for the other
boundary.
CMDRJE Executing 2EE8 FEEC An internal error occurred. Call customer
support.
CMDRJE Executing 2EF3 0002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom modify ldev -status nml
raidcom modify ldev -status nml
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
Get Command
Status
Async 2E10 0000 The specied LDEV is used for a ShadowImage
pair.
Get Command
Status
Async 2E10 0001 The specied LDEV is used for a TrueCopy pair
or a Universal Replicator pair.
Get Command
Status
Async 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
Get Command
Status
Async 2E10 0004 The specied LDEV is used for a Thin Image pair
or a Copy-on-Write Snapshot pair.
Get Command
Status
Async 2E10 0008 The specied LDEV is used as a system disk.
CMDRJE Executing 2E10 0010 LDEV is not blocked.
Get Command
Status
Async 2E10 0012 The specied LDEV is a CC/XRC attribute device.
SSB codes returned by raidcom modify ldev -ssid
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 443
raidcom modify ldev -status nml
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 001E The specied LDEV is not formatted after it is
used as the journal volume.
Get Command
Status
Async 2E10 0062 The specied LDEV is used as the primary
volume of aGAD pair.
Get Command
Status
Async 2E10 0063 The specied LDEV is used as the secondary
volume of aGAD pair.
Get Command
Status
Async 2E10 600B The pool is blocked.
Get Command
Status
Async 2E11 0009 The operation cannot be performed because
LDEV is not expanding.
Get Command
Status
Async 2E11 001E The operation cannot be performed because
the virtual disk space is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used in another
operation.
CMDRJE Executing 2E11 0153 The parity group or the external group to which
the specied LDEV belongs is used in another
operation.
Get Command
Status
Async 2E11 6006 The operation of Dynamic Provisioning V-VOL
cannot be performed because there is a
blocked pool volume.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 0000 The specied LDEV is not installed.
Get Command
Status
Async 2E30 000A The specied LDEV is used for a Dynamic
Provisioning.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000E The specied LDEV is used as a pool volume.
Get Command
Status
Async 2E30 0014 The specied LDEV is used as a reserved
volume of Volume Migration.
SSB codes returned by raidcom modify ldev -status nml
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 444
raidcom modify ldev -status nml
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 001A Volume Security is set to the specied LDEV.
Get Command
Status
Async 2E30 002C The specied LDEV cannot be restored because
the shredding or the formatting operation has
not been performed.
Get Command
Status
Async 2E30 004E The specied LDEV is a Data Retention Utility/
Volume Retention Manager attribute device.
Get Command
Status
Async 2E31 0017 LDEV cannot be restored because there is no
connection path to the normal external path.
CMDRJE Executing 2EE8 00EE The command cannot be accepted. After a
while, execute the same command.
SSB codes returned by raidcom modify ldev -status blk
raidcom modify ldev -status blk
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
Get Command
Status
Async 2E10 0000 The specied LDEV is used for a pair of
ShadowImage/Thin Image/Copy-on-Write
Snapshot/Volume Migration or as a relationship
of Compatible FlashCopy® V2/Hitachi
Compatible Software for IBM® FlashCopy® SE.
Get Command
Status
Async 2E10 0001 The specied LDEV is used for a pair of
TrueCopy or Universal Replicator.
Get Command
Status
Async 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
Get Command
Status
Async 2E10 0004 The specied LDEV is used for a Thin Image pair
or a Copy-on-Write Snapshot pair.
Get Command
Status
Async 2E10 0008 The specied LDEV is used as a system disk.
SSB codes returned by raidcom modify ldev -status blk
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 445
raidcom modify ldev -status blk
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0011 LDEV is not installed, or LDEV is not in the state
of Normal.
Get Command
Status
Async 2E10 0012 The specied LDEV is used at the concurrent
copy or XRC.
Get Command
Status
Async 2E10 0062 The specied LDEV is used as the primary
volume of aGAD pair.
Get Command
Status
Async 2E10 0063 The specied LDEV is used as the secondary
volume of aGAD pair.
Get Command
Status
Async 2E11 0009 The operation cannot be performed because
LDEV is now expanding.
Get Command
Status
Async 2E11 001E The operation cannot be performed because
the virtual disk space is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used in another
operation.
CMDRJE Executing 2E11 0153 The parity group or the external group to which
the specied LDEV belongs is used in another
operation.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 0000 The specied LDEV is not installed.
Get Command
Status
Async 2E30 000A The specied LDEV is used for a Dynamic
Provisioning.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000E The specied LDEV is used as a pool volume.
CMDRJE Executing 2E30 000F It is used as a journal.
Get Command
Status
Async 2E30 0014 The specied LDEV is used as a reserved
volume of Volume Migration.
SSB codes returned by raidcom modify ldev -status blk
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 446
raidcom modify ldev -status blk
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 001A Volume Security is set to the specied LDEV.
Get Command
Status
Async 2E30 001C It is used as a remote command device.
Get Command
Status
Async 2E30 004E It is a volume that the Data Retention Utility is
set.
Get Command
Status
Async 2E30 004E The specied LDEV is a Data Retention Utility/
Volume Retention Manager attribute device.
Get Command
Status
Async 2E30 0060 It is used as a command device that is used at
extended consistency group.
Get Command
Status
Async 2E30 0061 DP volume that is not in the blocked state is
included in the DP volume associated with a
pool that the pool volume is belongs to.
Get Command
Status
Async 2E31 0001 Maintenance work cannot be performed
because the target LDEV is a quorum disk.
Get Command
Status
Async 2E31 0017 LDEV cannot be blocked because there is no
connection path to the normal external path.
Get Command
Status
Async 2EE8 0A18 An internal error occurred.
SSB codes returned by raidcom modify ldev -status enable_reallocation/
disable_reallocation/new_page_allocation/enable_relocation_policy
raidcom modify ldev -status enable_reallocation/disable_reallocation/new_page_allocation/
enable_relocation_policy
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 Invalid LDEV number.
CMDRJE Executing 2E00 6101 The tiering policy is not in the eective range.
CMDRJE Executing 2E00 6102 The new page assignment tier is invalid.
CMDRJE Executing 2E20 0000 The specied LDEV is not installed.
SSB codes returned by raidcom modify ldev -status enable_reallocation/disable_reallocation/
new_page_allocation/enable_relocation_policy
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 447
raidcom modify ldev -status enable_reallocation/disable_reallocation/new_page_allocation/
enable_relocation_policy
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 8102 The shared memory for Dynamic Tiering or
active ash is not installed.
CMDRJE Executing 2E30 000B The specied LDEV is not a virtual volume of
Dynamic Provisioning, Dynamic Tiering, or
active ash.
CMDRJE Executing 2E30 0073 The specied LDEV is not a virtual volume of
Dynamic Tiering or active ash.
CMDRJE Executing 2E30 0209 The operation cannot be performed because
the specied LDEV is a volume for which the
capacity saving setting is enabled.
CMDRJE Executing 2EE8 0014 The specied LDEV is not a virtual volume of
Dynamic Tiering or active ash.
SSB codes returned by raidcom modify ldev -status discard_zero_page/
stop_discard_zero_page
raidcom modify ldev -status discard_zero_page/stop_discard_zero_page
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0000 The specied LDEV is used for a ShadowImage
pair.
CMDRJE Executing 2E10 0001 The specied LDEV is used for a TrueCopy pair.
CMDRJE Executing 2E10 0002 The specied LDEV is used for a Universal
Replicator pair.
CMDRJE Executing 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
CMDRJE Executing 2E10 0004 The specied LDEV is used for a Thin Image pair
or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0005 The specied LDEV is used for aVolume
Migration pair.
CMDRJE Executing 2E10 0011 The specied LDEV is blocked.
SSB codes returned by raidcom modify ldev -status discard_zero_page/stop_discard_zero_page
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 448
raidcom modify ldev -status discard_zero_page/stop_discard_zero_page
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 600B The associated pool is blocked.
CMDRJE Executing 2E11 0054 The page cannot be discarded because the pool
volume is being deleted or the Tier is being
reallocated.
CMDRJE Executing 2E11 0055 The operation cannot be performed because
the system pool volume is blocked.
CMDRJE Executing 2E11 8003 The operation cannot be performed because
the power supply is switched o.
CMDRJE Executing 2E14 0001 The page cannot be discarded because of the
non-operable status.
CMDRJE Executing 2E20 0000 The specied LDEV is not installed.
CMDRJE Executing 2E20 000A The operation cannot be performed because
the specied volume is being formatted.
CMDRJE Executing 2E30 000B The specied LDEV is not a virtual volume of
Dynamic Provisioning, Dynamic Tiering, or
active ash.
CMDRJE Executing 2E30 000F The specied LDEV is used as a journal volume.
CMDRJE Executing 2E30 0033 It is not associated to a pool.
CMDRJE Executing 2E30 0065 The specied volume is used by XRC.
CMDRJE Executing 2E30 0075 The page cannot be discarded because the
specied LDEV is a TSE-VOL.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
CMDRJE Executing 2E31 001B The page of DP-VOL cannot be discarded
because the LU path to the host group whose
host mode option 97 is enabled is dened to
the specied LDEV.
CMDRJE Executing 2EE8 00E7 An internal error occurred.
Call customer support.
SSB codes returned by raidcom modify ldev -status discard_zero_page/stop_discard_zero_page
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 449
raidcom modify ldev -status discard_zero_page/stop_discard_zero_page
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 9F02 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom modify ldev -status enable_fullallocation/
disable_fullallocation
raidcom modify ldev -status enable_fullallocation/disable_fullallocation
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 002F The specied value of the Full Allocation is
invalid.
CMDRJE Executing 2E00 0030 Full Allocation cannot be specied to the
specied LDEV because the emulation type is
not supported.
CMDRJE Executing 2E10 0065 The operation failed because the specied
LDEV is a DP-VOL that belongs to the pool of
which accelerated compression is enabled.
CMDRJE Executing 2E10 600B The associated pool is blocked.
CMDRJE Executing 2E10 600D The operation cannot be performed because a
pool volume is being deleted.
CMDRJE Executing 2E10 601B The free space in the specied pool is
insucient.
CMDRJE Executing 2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE Executing 2E11 001B The specied LDEV is blocked.
CMDRJE Executing 2E20 0000 LDEV is not installed.
CMDRJE Executing 2E30 000B The specied LDEV is not DP-VOL.
SSB codes returned by raidcom modify ldev -status enable_fullallocation/disable_fullallocation
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 450
raidcom modify ldev -status enable_fullallocation/disable_fullallocation
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
Get Command
Status
Async 2E30 0209 The operation cannot be performed because
the specied LDEV is a volume for which the
capacity saving setting is enabled.
CMDRJE Executing 2EE8 00EE The command cannot be accepted because the
DKC is busy. After a while, execute the same
command.
CMDRJE Executing 2EE8 FEEC An internal error occurred.
CMDRJE Executing 2EF3 9F02 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom modify ldev -quorum_enable
raidcom modify ldev -quorum_enable
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 8000 The device type is invalid.
CMDRJE Executing 2E00 8001 The serial number is invalid.
CMDRJE Executing 2E00 A001 The quorum disk ID is out of settable range.
Get Command
Status
Async 2E10 0005 The specied LDEV is used for Volume
Migration.
Get Command
Status
Async 2E10 0057 The specied LDEV cannot be congured
because the LDEV is a virtual volume.
Get Command
Status
Async 2E10 0201 The operation failed because the T10 PI
attribute of the specied LDEV is enabled.
SSB codes returned by raidcom modify ldev -quorum_enable
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 451
raidcom modify ldev -quorum_enable
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 0202 The specied volume belongs to the resource
group of NAS_Platform_System_RSG.
Get Command
Status
Async 2E10 A001 The specied quorum disk ID is being used.
Get Command
Status
Async 2E10 A003 The specied quorum disk is in processing.
Get Command
Status
Async 2E10 A005 The specied quorum disk is used as the
quorum disk of the dierent device.
Get Command
Status
Async 2E10 A006 The specied LDEV is used as the quorum disk.
Get Command
Status
Async 2E10 A007 The operation failed because the quorum disk
was inaccessible.
Get Command
Status
Async 2E11 001B The specied LDEV is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used for other operation.
Get Command
Status
Async 2E11 410B The external volume is inaccessible.
Get Command
Status
Async 2E11 410C An unformatted external volume is used.
Format the external volume, then retry the
operation.
Get Command
Status
Async 2E11 8014 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E13 0001 The specied LDEV is not the rst LDEV that
belongs to the external volume group.
CMDRJE Executing 2E20 0000 LDEV is not installed.
Get Command
Status
Async 2E20 000E The specied LDEV is not an external volume.
Get Command
Status
Async 2E21 810A A shared memory is not installed.
Get Command
Status
Async 2E30 0005 Cache Residency Manager is set to the specied
volume.
SSB codes returned by raidcom modify ldev -quorum_enable
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 452
raidcom modify ldev -quorum_enable
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 0007 A path is dened to the specied volume.
Get Command
Status
Async 2E30 000E The specied LDEV is used as a pool volume.
Get Command
Status
Async 2E30 000F The specied LDEV is used as a journal volume.
Get Command
Status
Async 2E30 0010 The specied volume is used as a command
device.
Get Command
Status
Async 2E30 004E Data Retention Utility is set to the specied
volume.
Get Command
Status
Async 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
Get Command
Status
Async 2E30 008E The emulation type of the specied LDEV is not
OPEN-V.
Get Command
Status
Async 2E30 0092 The specied LDEV cannot be used because the
size of LDEV is less than the minimum capacity
of the quorum disk.
Get Command
Status
Async 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE
Get Command
Status
Executing/
Async
2EE8 FEEC Internal error occurred.
SSB codes returned by raidcom modify ldev -quorum_disable
raidcom modify ldev -quorum_disable
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
SSB codes returned by raidcom modify ldev -quorum_disable
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 453
raidcom modify ldev -quorum_disable
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 A002 The specied LDEV is not a quorum disk.
Get Command
Status
Async 2E10 A003 The specied quorum disk is in processing.
Get Command
Status
Async 2E10 A004 The pair using the specied quorum disk exists.
Get Command
Status
Async 2E10 A007 The setting of the quorum disk was released
but the operation failed.
If you display the ldev information using
raidcom get ldev command, "QRD" (that means
the disk is the quorum disk) is not displayed on
VOL_ATTR because the quorum disk setting was
released. But the management information
possibly remains in the external volume.
If you dene again an external volume in which
the management information remains as a
quorum disk, an error may occur. When you
reuse an external volume which was used as a
quorum disk after removing it, format the
external volume.
CMDRJE Executing 2E11 0053 The specied LDEV is being used for other
operation.
CMDRJE Executing 2E20 0000 LDEV is not installed.
Get Command
Status
Async 2E21 810A A shared memory is not installed.
CMDRJE
Get Command
Status
Executing 2EE8 FEEC Internal error occurred.
SSB codes returned by raidcom modify ldev -quorum_disable
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 454
SSB codes returned by raidcom delete lun
raidcom delete lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 0155 The other than multiplatform volume or OPEN
volume is included in the specied LDEV.
CMDRJE Executing B958 015D An used LDEV exists in the specied LDEV.
CMDRJE Executing B958 0202 It cannot be deleted because it is the last path
of a TrueCopy or GAD pair.
CMDRJE Executing B958 0203 It cannot be deleted because it is the last path
of ShadowImage.
CMDRJE Executing B958 020A It cannot be deleted because it is the last path
of Thin Image or Copy-on-Write Snapshot.
CMDRJE Executing B958 020B It cannot be deleted because it is the last path
of Universal Replicator.
CMDRJE Executing B958 020F The specied LDEV is not installed.
CMDRJE Executing B958 0233 It cannot be deleted because the operation
object LU is executing host I/O.
CMDRJE Executing B958 0234 It cannot be deleted because the operation
object LU is reserved.
CMDRJE Executing B958 0239 The command device is being used in the local
Command Control Interface.
CMDRJE Executing B958 0240 A command device is being set.
CMDRJE Executing B958 028E It cannot be deleted because of the ALU path
denition.
CMDRJE Executing B958 0927 The command cannot be operated because the
virtual LDEV is not dened yet.
CMDRJE Executing B958 0944 The value of LUN exceeds the maximum.
CMDRJE Executing B958 0945 The value of LDEV exceeds the maximum.
CMDRJE Executing B958 0956 The value of host group ID exceeds the
maximum.
CMDRJE Executing B958 0957 The program product is not installed.
CMDRJE Executing B958 0959 Host group is not installed.
SSB codes returned by raidcom delete lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 455
raidcom delete lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 095D An invalid LDEV exists in the specied LDEVs.
CMDRJE Executing B958 098C Multiple LDEVs cannot be specied.
CMDRJE Executing B958 098D When the host mode option 60 is set, the LU
path of LUN0 cannot be set or released.
CMDRJE Executing B958 0996 The LU path cannot be deleted because the
virtual LDEV ID of the specied volume was
deleted.
CMDRJE Executing B958 099F The specied port is not mounted.
CMDRJE Executing B958 09A1 Another LDEV is already mapped in the
specied LUN.
Executing B980 B901 The
comm
and
was
rejecte
d
becaus
e the
speci
ed port
is for
NAS
Platfor
m
(Syste
m LU).
SSB codes returned by raidcom delete lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 456
raidcom delete lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B902 The
comm
and
was
rejecte
d
becaus
e the
speci
ed port
is for
NAS
Platfor
m
(User
LU).
Executing B980 B903 The
comm
and
was
rejecte
d
becaus
e the
selecte
d
resour
ce
belong
s to
NAS_Pl
atform
_Syste
m_RSG
.
SSB codes returned by raidcom delete lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 457
SSB codes returned by raidcom add lun
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF6 0014 An invalid LDEV exists in the specied LDEVs.
Get Command
Status
Executing B958 0101 The LU path cannot be set because it is
reserved for Volume Migration.
Get Command
Status
Executing B958 010C The LU path cannot be set because the volume
is a deduplication system data volume.
CMDRJE Executing B958 014A When an ISCSI is used, the LU path cannot be
set in the LDEV other than the OPEN volume.
CMDRJE Executing B958 0150 The attribute of the specied port is Initiator or
External.
CMDRJE Executing B958 0155 The other than HMDE volume or OPEN volume
is included in the specied LDEV.
Get Command
Status
Executing B958 015A An LU path has already been dened in the
target LDEV.
CMDRJE Executing B958 015D An invalid LDEV exists in the specied LDEVs.
Get Command
Status
Executing B958 015E It exceeds the maximum LUN under the port.
Get Command
Status
Executing B958 0178 LDEV is set as a pool volume.
CMDRJE Executing B958 017B The LU path cannot be set because the LDEV is
a system disk.
Get Command
Status
Executing B958 017C The LU path cannot be set because the LDEV is
a journal volume.
CMDRJE Executing B958 017D The LU path cannot be set because the access
attribute of LDEV Data Retention Utility is
reserved.
CMDRJE Executing B958 017E The LU path cannot be set because the access
attribute of LDEV Data Retention Utility is
dierent from "Read/Write".
Get Command
Status
Executing B958 018E The LU path cannot be set because the LDEV
has an ALU attribute.
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 458
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 01A3 When the host mode is Universal Volume
Manager(0x4C), the LU path cannot be set in
other than the external volume.
Get Command
Status
Executing B958 01C1 The LU path cannot be dened because the
volume is used as a quorum disk.
Get Command
Status
Executing B958 01DC The number of the host groups which can be
set by ALUA exceeded the maximum.
Get Command
Status
Executing B958 01DE The operation cannot be performed because
the specied LDEV is the external volume
having the Data Direct Mapping attribute.
Get Command
Status
Executing B958 01DF The LU path cannot be dened because the
LDEV belongs to the parity group of which
accelerated compression is enabled.
Get Command
Status
Executing B958 01F2 The host group and the LDEV that congure the
LU path do not exist in the same virtual storage
machine.
CMDRJE Executing B958 01F3 The LU path cannot be dened because the
virtual LDEV information of the specied LDEV
is not dened yet.
Get Command
Status
Executing B958 01F4 The path of the external volume which has an
NDM attribute cannot be dened
Get Command
Status
Executing B958 01F9 The LU path cannot be added because the
setting of the T10 PI attribute on the specied
port or on the specied LDEV is not correct.
Enable the T10 PI attribute on the specied
port. Otherwise, disable the T10 PI attribute on
the specied LDEV.
Get Command
Status
Executing B958 01FA The operation failed because the T10 PI
attribute of the specied LDEV is enabled.
CMDRJE Executing B958 0601 The command device cannot be set because it
is reserved for Volume Migration.
CMDRJE Executing B958 0606 The command device cannot be set because it
is a ShadowImage pair or it is reserved.
CMDRJE Executing B958 060F The specied LDEV is not installed.
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 459
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 0639 The command device cannot be operated
because it is used at the local CCI.
CMDRJE Executing B958 064A A command device cannot be set because LDEV
is other than the OPEN volume.
CMDRJE Executing B958 065D The specied LDEV is not installed.
CMDRJE Executing B958 0679 A command device cannot be set because LDEV
is the virtual volume of Thin Image or Copy-on-
Write Snapshot.
CMDRJE Executing B958 06C0 The specied LDEV is being used as a volume of
aGAD pair.
CMDRJE Executing B958 06C1 The specied LDEV is used as a quorum disk.
CMDRJE Executing B958 06C2 The specied LDEV is used for a TrueCopy pair
or a Universal Replicator pair.
Get Command
Status
Executing/
Async
B958 090F An internal error occurred.
Call customer support.
CMDRJE Executing B958 0927 The command cannot be operated because the
virtual LDEV is not dened yet.
CMDRJE Executing B958 0944 The value of LUN exceeds the maximum.
CMDRJE Executing B958 0945 The value of LDEV exceeds the maximum.
CMDRJE Executing B958 0947 Another LDEV is already mapped to the
specied LUN.
CMDRJE Executing B958 0956 The value of Host group ID exceeds the
maximum.
Get Command
Status
Executing B958 0957 The program product is not installed.
Get Command
Status
Executing B958 0959 The specied host group is not installed.
Get Command
Status
Executing B958 095D An invalid LDEV exists in the specied LDEVs.
CMDRJE Executing B958 098C The multiple LDEV cannot be specied.
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 460
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 098D When the host mode option 60 is set, the LU
path of LUN0 cannot be set or released.
CMDRJE Executing B958 0994 An invalid LDEV exists in the specied LDEVs.
CMDRJE Executing B958 0996 The LU path cannot be added because the
virtual LDEV ID of the specied volume was
deleted.
CMDRJE Executing B958 099C The number of paths exceeds the maximum.
CMDRJE Executing B958 099D Only one path is set for NAS Platform (User LU).
CMDRJE Executing B958 099E The same port number is specied more than
once.
Get Command
Status
Executing B958 099F The specied port is not mounted.
Get Command
Status
Executing B958 09F8 The LU path cannot be set because the
specied LDEV is being deleted.
Get Command
Status
Async B958 1307 The operation cannot be performed because
there is no free common LU path number in the
specied host group.
Executing/Async B958 2116 The
opera
tion
canno
t be
perfor
med
becau
se the
speci
ed
port is
used
by
Stora
ge
Advis
or
Embe
dded.
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 461
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B901 The
comm
and
was
reject
ed
becau
se the
speci
ed
port is
for
NAS
Platfo
rm
(Syste
m
LU).
Executing B980 B902 The
comm
and
was
reject
ed
becau
se the
speci
ed
port is
for
NAS
Platfo
rm
(User
LU).
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 462
raidcom add lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B903 The
comm
and
was
reject
ed
becau
se the
select
ed
resou
rce
belon
gs to
NAS_
Platfo
rm_Sy
stem_
RSG.
Executing B980 B905 The
LU
path
canno
t be
set in
Com
mand
Devic
e
becau
se
Port is
NAS
Platfo
rm
(User
LU).
SSB codes returned by raidcom add lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 463
SSB codes returned by raidcom modify lun
raidcom modify lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 1000 The value of host group ID exceeds the
maximum.
CMDRJE Executing 2E02 1102 The value of LUN exceeds the maximum.
CMDRJE Executing 2E02 8404 The value of the specied port is invalid.
CMDRJE Executing 2E11 2206 You do not have the operation authority to
operate the target resource group.
Specify the resource group that is allocated to
the user group as the operation target or set
the operation authority to the user group in
order to operate the target resource group.
CMDRJE Executing 2E20 1003 The specied host group is not installed.
CMDRJE Executing 2E20 1102 The LU path denition does not exist in the
host group.
CMDRJE Executing 2E20 1103 The path is not dened for the specied LUN.
Get Command
Status
Async 2EA9 FEEC An internal error occurred.
Call customer support.
CMDRJE Executing B958 5021 The PCB type of the port to which the host
group belongs is out of operation target.
CMDRJE Executing B958 5046 The LU path denition does not exist in the
host group.
CMDRJE Executing B958 5056 The value of host group ID exceeds the
maximum.
CMDRJE Executing B958 5059 Host group is not installed.
CMDRJE Executing B958 50DD The specied ALUA path priority is invalid.
CMDRJE Executing B958 50F7 Unavailable to operate because another
application is in progress on Storage Navigator,
Device Manager - Storage Navigator, or SVP.
SSB codes returned by raidcom modify lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 464
SSB codes returned by raidcom discover lun
raidcom discover lun
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is invalid.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
SSB codes returned by raidcom modify pool
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of the valid range.
CMDRJE Executing 2E00 0003 The SSID is out of the valid range.
Get Command
Status
Async 2E00 0010 The specied LDEV number is already used.
Get Command
Status
Async 2E00 0013 There are not enough cache management
devices.
Get Command
Status
Async 2E00 0016 The command cannot be executed by receiving
multiple operations for the same pool ID.
CMDRJE Executing 2E00 002F The specied attribute is invalid.
CMDRJE Executing 2E00 6000 The value of pool ID is invalid.
CMDRJE Executing 2E00 6001 The specied pool is for Thin Image or Copy-on-
Write Snapshot.
CMDRJE Executing 2E00 6002 The specied maximum reserve rate is not in
the eective range.
CMDRJE Executing 2E00 6003 The specied Tier Range value is invalid.
SSB codes returned by raidcom discover lun
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 465
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6004 Relations between the specied lower limit of
Tier Range and the Delta value is invalid.
CMDRJE Executing 2E00 6006 The specied Tier capacity threshold value is
out of range.
CMDRJE Executing 2E00 6009 The threshold of the specied High water mark
is out of range.
CMDRJE Executing 2E00 600A The operation cannot be performed because
the specied threshold of Warning is larger
than the threshold of the specied High water
mark.
CMDRJE Executing 2E00 6100 The specied tier number is out of range.
CMDRJE Executing 2E02 0202 The threshold value cannot be changed to the
specied value, because the specied pool is
used for Data Direct Mapping.
CMDRJE
Get Command
Status
Executing/
Async
2E10 001F The operation cannot be performed because
the total capacity of virtual volumes for
Dynamic Tiering or active ash in the system
exceeds the maximum.
CMDRJE Executing 2E10 600B The specied pool is in the state of blocked.
Get Command
Status
Async 2E10 600C The setting of the threshold value is less than
the pool usage value.
CMDRJE Executing 2E10 600D The operation cannot be performed because it
is in the state of shrinking.
CMDRJE Executing 2E10 6011 The operation cannot be performed because it
is being discarded pages.
Get Command
Status
Async 2E10 6012 Pool cannot be restored because the usage rate
of pool is 100%.
Get Command
Status
Async 2E10 6014 The operation cannot be performed because
the specied pool status is incorrect.
CMDRJE Executing 2E10 6015 The operation cannot be performed because
the Tier is being deterred reallocation.
CMDRJE Executing 2E10 6017 The operation cannot be performed because
collecting the performance monitoring data is
being prepared.
SSB codes returned by raidcom modify pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 466
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 601D The specied pool cannot be changed to the
pool for Data Direct Mapping, because the
threshold value of High water mark is xed.
CMDRJE
Get Command
Status
Executing/
Async
2E10 601F The deduplication function is set to be enabled
for the specied pool.
Get Command
Status
Async 2E10 6020 The deduplication function cannot be used in
the specied pool.
CMDRJE
Get Command
Status
Executing/
Async
2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE
Get Command
Status
Executing/
Async
2E11 0205 The operation cannot be performed because
the total capacity of provisioning virtual
volumes and deduplication system data
volumes dened in the specied pool exceeds
the maximum of reserved pool capacity.
CMDRJE Executing 2E11 6003 The pool is not in the status where the pool
option can be set.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because of
the internal processing.
CMDRJE Executing 2E11 800F The operation cannot be performed because
the unsupported microcode version exists in
the system.
Get Command
Status
Async 2E11 8010 The storage system is in the internal processing
or the conguration change processes are
conicting.
Get Command
Status
Async 2E11 8105 The cache segment size is incorrect.
Get Command
Status
Async 2E11 8108 The operation cannot be performed because
there is a blocked part in the storage system.
CMDRJE Executing 2E11 9400 The command cannot be accepted. Wait a
while, and then execute the same command.
SSB codes returned by raidcom modify pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 467
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E13 6000 The Dynamic Tiering or active ash operations
cannot be performed to the pool because the
specied pool contains RAID 1 pool VOLs.
CMDRJE Executing 2E13 6002 The specied pool for Dynamic Provisioning
cannot be changed to a pool for Dynamic
Tiering because the pool is related to TSE-VOL.
CMDRJE Executing 2E13 6005 The setting cannot be performed because the
microcode does not support active ash.
CMDRJE Executing 2E13 6007 The operation cannot be performed because
the specied pool is already linked with the
virtual volume of Dynamic Provisioning.
CMDRJE Executing 2E13 6008 The operation cannot be performed because
the pool volume having the Data Direct
Mapping attribute is included in the specied
pool.
Get Command
Status
Async 2E13 600A The operation cannot be performed because
the specied pool is linked with an LDEV for
which the deduplication function is enabled.
Get Command
Status
Async 2E13 600B The operation cannot be performed because
the specied pool is linked with an LDEV that
has deduplication data.
Get Command
Status
Async 2E13 600C The operation cannot be performed because
the specied pool is linked with a volume for
which capacity saving function is enabled.
CMDRJE Executing 2E20 6000 Pool ID is not installed.
CMDRJE Executing 2E20 6101 The specied Tier number is invalid.
Get Command
Status
Async 2E20 8300 The specied MP blade or MP unit is not
installed.
CMDRJE Executing 2E21 8101 The shared memory for Dynamic Provisioning is
not installed.
CMDRJE Executing 2E21 8102 The shared memory for Dynamic Tiering or
active ash is not installed.
Get Command
Status
Async 2E21 8103 The operation cannot be performed because of
the insucient capacity of shared memory.
SSB codes returned by raidcom modify pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 468
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 810A The shared memory is not installed.
Get Command
Status
Async 2E21 9000 The program product is not installed.
CMDRJE Executing 2E21 9014 Data Retention Utility program product is not
installed.
CMDRJE
Get Command
Status
Executing/
Async
2E22 0001 The specied LDEV is already dened.
Get Command
Status
Async 2E23 0001 The number exceeds the maximum number of
LDEVs that can be created in the current system
conguration.
CMDRJE
Get Command
Status
Executing/
Async
2E23 0008 The number of specied deduplication system
data volumes exceeds the maximum limit.
CMDRJE Executing 2E23 7201 The specied SSID number exceeds the
maximum limit.
Get Command
Status
Async 2E30 0020 The specied SSID is already used in the
another CU.
Get Command
Status
Async 2E30 0021 The SSID is already allocated to the CU.
Get Command
Status
Async 2E30 0025 The specied volume is used as an alias device
in Compatible PAV.
Get Command
Status
Async 2E30 0026 An LDEV of another emulation type is allocated
in the range where the number is divided into
each 32 LDEVs.
CMDRJE Executing 2E30 006E The Dynamic Tiering or active ash operation
cannot be performed to the pool because the
specied pool contains the external volumes
whose cache mode is invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0071 A pool volume cannot be operated because the
LDEV of the resource group dierent from the
resource group of the pool volume belonging to
the specied pool is specied.
SSB codes returned by raidcom modify pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 469
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 009A The page reservation cannot be set on the
specied LDEV with the specied operation.
Get Command
Status
Async 2E30 4119 The operation cannot be performed because
the number of V-VOLs that can be created in
the system exceeds the maximum number.
CMDRJE Executing 2E30 6000 The threshold value 1 is out of range.
CMDRJE Executing 2E30 6003 The specied pool is for Thin Image or Copy-on-
Write Snapshot.
CMDRJE Executing 2E30 6005 The specied pool must be assigned two user-
dened thresholds to.
CMDRJE Executing 2E30 600D On the specied pool, Tier Reallocation is not
enabled.
CMDRJE Executing 2E30 600F The specied operation cannot be performed
because the specied pool is not for Dynamic
Provisioning.
CMDRJE Executing 2E30 6010 Active ash cannot be enabled because an SSD
medium does not exist on Tier 1 of Dynamic
Provisioning.
CMDRJE Executing 2E30 6011 Active ash cannot be enabled or disabled
because the pool is for Dynamic Provisioning.
CMDRJE Executing 2E30 6012 The operation of Dynamic Tiering cannot be
performed because the specied pool is used
for Data Direct Mapping.
Get Command
Status
Async 2E30 6014 The operation cannot be performed because
the specied pool is for active ash.
Get Command
Status
Async 2E31 6003 The operation cannot be performed because
the specied pool is for Dynamic Provisioning
for Mainframe.
CMDRJE Executing 2E31 6004 The specied pool includes the dierent RAID
levels of volumes although the pool cannot
include those volumes together.
CMDRJE Executing 2E31 6005 The specied pool includes external volumes
although the pool cannot include those
volumes together.
SSB codes returned by raidcom modify pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 470
raidcom modify pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E31 6006 The specied pool cannot be used for a
Dynamic Tiering or active ash.
CMDRJE Executing 2E31 9000 The capacity that can be used by the installed
program products exceeds the maximum.
CMDRJE Executing 2E31 9001 The program product is not installed.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EE7 0001 Pool ID is not installed.
CMDRJE Executing 2EE7 0011 An internal error occurred at the pool
operation.
Call customer support.
CMDRJE Executing 2EE7 00EE The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2EE7 00F0 The specied command cannot be accepted
because the command is not supported.
CMDRJE Executing 2EE7 FEEC An internal error occurred in the pool
operation.
Call customer support.
CMDRJE Executing 2EF3 9F02 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom rename pool
raidcom rename pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
CMDRJE Executing 2E10 6016 The pool name cannot be changed because the
pool conguration is being changed.
CMDRJE Executing 2E20 6000 Invalid pool ID.
SSB codes returned by raidcom rename pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 471
raidcom rename pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E31 6001 The pool name is duplicated with another pool.
CMDRJE Executing 2EE7 FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom delete pool
raidcom delete pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
Get Command
Status
Async 2E00 600B All pool volumes associated to a pool cannot be
deleted.
Get Command
Status
Async 2E10 0009 The specied LDEV is in the state of blocked.
CMDRJE Executing 2E10 600D This pool cannot be deleted because a pool
volume is being deleted.
Get Command
Status
Async 2E10 600E The operation cannot be performed because
the pool usage rate exceeds the threshold value
of the pool usage.
Get Command
Status
Async 2E10 600F The operation cannot be performed because
the current capacity rate exceeds the value of
maximum reserved capacity rate.
Get Command
Status
Async 2E10 6010 It cannot be deleted because the pool volume is
set in the state of being deterred deleting.
Get Command
Status
Async 2E10 6011 Deleting operation cannot be performed
because it is being discarded pages.
Get Command
Status
Async 2E10 601F The deduplication function is set to be enabled
for the specied pool.
Get Command
Status
Async 2E10 8002 The specied operation is not supported in the
current microcode version.
SSB codes returned by raidcom delete pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 472
raidcom delete pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 001F The operation cannot be performed because a
Thin Image pair or a Copy-on-Write Snapshot
pair remains or the association with a Dynamic
Provisioning virtual volume exists.
Get Command
Status
Async 2E11 0020 The operation cannot be performed because a
Thin Image pair or a Copy-on-Write Snapshot
pair is being deleted or a Dynamic Provisioning
virtual volume is being deleted.
Get Command
Status
Async 2E11 0021 The operation cannot be performed because a
pool volume of a specied pool is being
formatted.
CMDRJE
Get Command
Status
Executing/
Async
2E11 6003 The pool is not in the status where the pool can
be deleted or a pool volume can be deleted.
Get Command
Status
Async 2E11 8003 The operation cannot be performed because
the power supply is switched o.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E13 0002 The operation cannot be performed because
the specied LDEV is linked with the virtual
volume having the Data Direct Mapping
attribute.
Get Command
Status
Async 2E13 6006 The last SSD medium on Tier 1 of active ash
cannot be deleted.
Get Command
Status
Async 2E13 6009 The operation cannot be performed because
the pool capacity is insucient for Data Direct
Mapping.
CMDRJE Executing 2E20 0003 The specied LDEV is not registered to the pool.
Get Command
Status
Async 2E20 0003 The operation cannot be performed because
the pool volume is not of a specied pool.
CMDRJE
Get Command
Status
Executing/
Async
2E20 6000 Pool ID is not installed.
SSB codes returned by raidcom delete pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 473
raidcom delete pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 8106 The operation cannot be performed because
the shared memory is not initialized.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
CMDRJE Executing 2E30 0052 The specied LDEV cannot be deleted because
it is a top VOL of the pool.
CMDRJE Executing 2E30 6003 The specied pool is a pool for Thin Image or
Copy-on-Write Snapshot.
CMDRJE Executing 2EE7 00EE The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2EE7 00F9 Pool ID is not installed.
CMDRJE Executing 2EE7 FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 6002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add snap_pool
raidcom add snap_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 6000 Pool ID is out of range.
CMDRJE Executing 2E00 6001 The type of pool is invalid.
CMDRJE Executing 2E00 6002 The maximum reserve ratio for V-VOL is out of
range.
SSB codes returned by raidcom add snap_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 474
raidcom add snap_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 000C The operation cannot be performed because a
SATA-E drive in the state of quick formatting is
in the specied LDEV.
Get Command
Status
Async 2E10 0009 The specied LDEV is in the state of blocked.
CMDRJE Executing 2E10 0011 The specied LDEV is in the state of blocked, or
not installed.
Get Command
Status
Async 2E10 0050 Thin Image cannot be used because there are
not enough cache management devices to
create pairs.
Get Command
Status
Async 2E10 0102 The pool cannot be created because there are
not enough resources (VDEV) depending on
cache management devices.
Get Command
Status
Async 2E10 600D The operation cannot be performed because
the pool volume is being deleted.
Get Command
Status
Async 2E11 005F The operation failed because accelerated
compression of the parity group to which the
specied LDEV belongs is enabled and the
other LDEV in the parity group is being used for
the other pool.
Get Command
Status
Async 2E11 0108 The specied LDEV is the LDEV conguring the
RAID conguration which cannot be used for
the pool volume.
CMDRJE
Get Command
Status
Executing/
Async
2E11 6003 The pool is not in the status where the pool
volume can be added.
Get Command
Status
Async 2E11 8003 The operation cannot be performed because
the power supply is switched o.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 0000 The specied LDEV is not installed.
Get Command
Status
Async 2E21 8103 The operation cannot be performed because
the memory capacity of the shared memory is
insucient.
SSB codes returned by raidcom add snap_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 475
raidcom add snap_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 8106 The operation cannot be performed because
the shared memory for Thin Image or Copy-on-
Write Snapshot is not initialized.
CMDRJE Executing 2E21 9007 Thin Image or Copy-on-Write Snapshot
program product is not installed.
Get Command
Status
Async 2E22 0005 Exceeded the number of pool volume that can
be registered in a pool.
Get Command
Status
Async 2E22 000D The larger number of drive types than the
supported conguration cannot be added to
the specied pool.
Get Command
Status
Async 2E22 6100 Pool volume cannot be registered because the
drive type of the specied LDEV is dierent
from the other pool volume type, or the drive
type in the pool exceeds the three.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
Get Command
Status
Async 2E30 0000 The emulation type of the specied LDEV
cannot be used as a pool VOL.
Get Command
Status
Async 2E30 0007 The specied LDEV has the LU path denition.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000D The specied LDEV is used as a system disk.
Get Command
Status
Async 2E30 000E The specied LDEV is already used as a pool
volume.
Get Command
Status
Async 2E30 0010 The specied LDEV is a command device.
Get Command
Status
Async 2E30 0038 It cannot be used as a pool volume because
the size of the specied LDEV is less than 8GB.
Get Command
Status
Async 2E30 0039 Creating a pool or adding a pool volume
cannot be performed because CLPR is mixed in
the specied pool.
Get Command
Status
Async 2E30 005C The specied LDEV is used as a V-VOL.
SSB codes returned by raidcom add snap_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 476
raidcom add snap_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 005E The specied LDEV is used in another program
product.
CMDRJE Executing 2E30 006C An LDEV, whose emulation type is not available
to be mixed, is in the specied LDEVs.
CMDRJE Executing 2E30 006D The emulation type of the specied volume is
not OPEN-V.
Get Command
Status
Async 2E30 006E The operation cannot be performed for the
following reasons:
■The pool volumes include external volumes
whose cache modes are invalid.
■The pool includes both external volumes
whose cache modes are invalid and internal
volumes.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0071 A pool volume cannot be added because the
LDEV of the resource group dierent from the
resource group of the pool volume to which
the specied pool belongs is specied.
Get Command
Status
Async 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
Get Command
Status
Async 2E30 0085 The specied volume cannot be used as a pool
volume.
Get Command
Status
Async 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 6000 The threshold value 1 is out of range.
Get Command
Status
Async 2E30 6004 The specied pool attribute diers from the
pool attribute of existed pool.
Get Command
Status
Async 2E31 0015 The RAID level of the specied LDEV is dierent
from the RAID level of the other pool volumes.
Get Command
Status
Async 2E31 0016 There is a blocked pool volume.
Get Command
Status
Async 2E31 0018 External volumes whose cache modes are
dierent are included.
SSB codes returned by raidcom add snap_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 477
raidcom add snap_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E31 6001 The POOL Name is duplicated with another
pool.
Get Command
Status
Async 2E31 6004 The pool cannot include volumes in dierent
RAID levels because the pool cannot include
those volumes. Or the pool cannot include the
RAID 1 volumes and the volumes of other RAID
levels together.
Get Command
Status
Async 2E31 6005 The pool cannot include both internal volumes
and external volumes because the pool is not
set to Mixable.
Get Command
Status
Async 2E31 9000 The usage capacity exceeds the license capacity
of program product.
CMDRJE
Get Command
Status
Executing
Async
2EE7 FEEC An internal error occurred.
Call customer support.
Get Command
Status
Async 2EE7 FFFF An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 0002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add snapshot
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 0013 A pair cannot be created because there are not
enough cache management devices.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 478
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0028 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E00 0029 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E00 6000 The specied pool ID is out of the range.
CMDRJE Executing 2E00 9701 There are not enough required input
parameters.
CMDRJE Executing 2E10 0020 A pair cannot be created because the volume
that has the size exceeding the supported size
is specied as the P-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0021 A pair cannot be created because the volume
exceeded the support size is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0022 A pair cannot be created because the V-VOL is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0023 A pair cannot be created because the pool-VOL
is specied as the P-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0024 A pair cannot be created because the journal
volume of Universal Replicator is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0025 The command ends abnormally because the
LUSE volumes of dierent structure are
specied as the P-VOL and the S-VOL.
CMDRJE Executing 2E10 0026 A pair cannot be created because the volume in
which the VMA is set is specied as the P-VOL.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 479
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0027 A pair cannot be created because the external
volume is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0028 A pair cannot be created because the volume
other than V-VOL is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0029 A pair cannot be created because the pool-VOL
is specied as the S-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002A A pair cannot be created because the volume
(the data volume or the journal volume) of the
Universal Replicator pair that is in the
intermediate site of the 3DC cascading
conguration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002B A pair cannot be created because the P-VOL of
a Universal Replicator pair is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 002C A pair cannot be created because the S-VOL of
a Universal Replicator pair is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 002D A pair cannot be created because the journal
volume of the Universal Replicator is specied
as the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 002E The command ends abnormally because the
volume to which S-VOL Disable option is set is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002F A pair cannot be created because the volume to
which VMA is set is specied as the S-VOL of a
Thin Image pair or aCopy-on-Write Snapshot
pair.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 480
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0030 The command ends abnormally because the
volumes of dierent Max LBA size are specied
as the P-VOL and S-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0031 The command ends abnormally because the
volumes whose the number of slots is dierent
are specied as the P-VOL and S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0032 A pair cannot be created because the Dynamic
Provisioning V-VOL is specied as the S-VOL of a
Thin Image pair or the specied Thin Image pair
does not exist.
CMDRJE Executing 2E10 0033 The command ends abnormally because the
ShadowImage reserved volume is specied as
the P-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0034 The command ends abnormally because the
Volume Migration source volume is specied as
the P-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0035 The command ends abnormally because the
Volume Migration target volume is specied as
the P-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0036 The command ends abnormally because the
Volume Migration reserved volume is specied
as the P-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0037 The command ends abnormally because the P-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Image pair or aCopy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0038 The command ends abnormally because the S-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Image pair or aCopy-on-Write
Snapshot pair.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 481
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0039 The command ends abnormally because the
ShadowImage reserved volume is specied as
the S-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003A The command ends abnormally because the
Volume Migration source volume is specied as
the S-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003B The command ends abnormally because the
Volume Migration target volume is specied as
the S-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003C The command ends abnormally because the
Volume Migration reserved volume is specied
as the S-VOL of a Thin Image pair or aCopy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003D A Thin Image pair or aCopy-on-Write Snapshot
pair cannot be created because the volume of
Universal Replicator for the delta resync is
specied as the P-VOL of a Thin Image pair or
aCopy-on-Write Snapshot pair.
CMDRJE Executing 2E10 003E A Thin Image pair or aCopy-on-Write Snapshot
pair cannot be created because the volume of
Universal Replicator pair for the delta resync
operation is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 003F The command ends abnormally because the
quorum disk is specied as the P-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0040 The command ends abnormally because the
quorum disk is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0041 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because the Dynamic
Provisioning V-VOL in capacity expanding is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 482
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0042 A pair cannot be created because the page
discard (reclaim zero pages) is being executed
by a SCSI command from the Host to the
specied P-VOL.
CMDRJE Executing 2E10 0045 A pair cannot be created because the P-VOL of
a TrueCopy pair is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0046 A pair cannot be created because the S-VOL of
a TrueCopy pair is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0049 The command ends abnormally because the
ShadowImage pair is being resynchronized
when the volume is shared between the P-VOL
of a Thin Image/Copy-on-Write Snapshot pair
and the P-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004A The command ends abnormally because the
ShadowImage pair status is other than PSUS
when the volume is shared between P-VOL of a
Thin Image/Copy-on-Write Snapshot pair and
the S-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004E The operation cannot be performed because
the P-VOL of the ShadowImage pair on which
the Quick Restore is being operated is specied
as the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0051 The pair operation cannot be performed
because the volume which species the volume
using two mirrors cannot accept the specied
command in the following congurations using
three Universal Replicator sites.
■3DC multi target conguration
■3DC cascade conguration
■Delta resync conguration
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 483
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0052 A Thin Image pair cannot be created because
the pair status of all Thin Image pairs sharing
the specied P-VOL is PSUE.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
CMDRJE Executing 2E10 005C A Thin Image pair cannot be operated because
changing the model and the serial number in
the virtual storage machine of the specied P-
VOL is in progress.
CMDRJE Executing 2E10 005D A Thin Image pair cannot be operated because
changing the model and the serial number in
the virtual storage machine of the specied S-
VOL is in progress.
CMDRJE Executing 2E10 0203 The operation failed because the setting of the
T10 PI attribute is not match between the
specied P-VOL and the specied S-VOL.
CMDRJE Executing 2E10 0205 A pair cannot be created because the page
discard (reclaim zero pages) is being executed
by a SCSI command from the Host to the
specied S-VOL.
CMDRJE Executing 2E10 0206 A Thin Image pair cannot be created because
the Dynamic Provisioning V-VOL in capacity
expanding is specied as the S-VOL of a Thin
Image pair.
CMDRJE Executing 2E10 0211 The command ends abnormally because the
volume which is being deleted is specied.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 484
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 2300 A Thin Image pair or a Copy-on-Write Snapshot
pair with the specied consistency group ID
cannot be created due to one of the following
reasons:
■The specied consistency group ID is used
by the ShadowImage.
■The number of pairs that can be dened in a
consistency group exceeds the maximum.
■The pair created by using the same P-VOL
already exists in the specied consistency
group.
CMDRJE Executing 2E10 2302 A Thin Image pair specifying CTG mode cannot
be created because the maximum number of
consistency groups has already been dened.
CMDRJE Executing 2E10 6018 A Thin Image pair cannot be created due to one
of the following reasons:
■The pool usage value exceeds the threshold
value.
■The specied pool is blocked.
CMDRJE Executing 2E10 8100 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because there are not
enough pair tables.
CMDRJE Executing 2E10 8101 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because there are not
enough dierential tables.
CMDRJE Executing 2E10 8102 A pair cannot be created because there is not
enough free shared memory space.
CMDRJE Executing 2E10 9701 The command ends abnormally because the
pair is in the state of unacceptable the
command.
CMDRJE Executing 2E10 9705 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because the number of
Thin Image pairs or Copy-on-Write Snapshot
pairs has already reached the maximum.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 485
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 9706 A Thin Image pair cannot be created because
the maximum number of Snapshot IDs (MU
numbers) has already been in use for the
specied P-VOL.
CMDRJE Executing 2E10 9707 A Thin Image pair cannot be created because
the maximum number of Snapshot groups has
already been dened, or the maximum number
of Thin Image pairs has already been dened in
the specied Snapshot group.
CMDRJE Executing 2E10 9708 A Thin Image pair cannot be created because
the DP pool is being initialized.
CMDRJE Executing 2E10 970D The pair cannot be created because the
number of pair layers in the cascade
conguration exceeds the maximum number.
CMDRJE Executing 2E10 970E The pair cannot be created because the
number of clone attribute pair layers exceeds
the maximum number.
CMDRJE Executing 2E10 970F When the pair status is other than PAIR or
PSUS, you cannot create a pair by specifying the
S-VOL of a Thin Image pair.
CMDRJE Executing 2E10 9712 Thin Image pairs that can be cascaded or
cloned and Thin Image pairs that cannot be
cascaded or cloned cannot be contained in a
snapshot tree.
CMDRJE Executing 2E10 9713 The operation cannot be performed because
the snapshot tree is being deleted.
CMDRJE Executing 2E10 9800 An error occurred at the operation of Thin
Image due to one of the following reasons:
■The LDEV number specied for the P-VOL or
the S-VOL is incorrect.
■The LDEV specied as the P-VOL or the S-
VOL is not paired.
■The pair of the specied P-VOL or the S-VOL
is not ready to perform the specied
operation.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 486
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
■The specied Snapshot ID (MU number) is
wrong.
■The specied Snapshot ID (MU number) is
already used.
■The specied pool is not in the usable status.
■The license capacity has exceeded the
maximum.
■The control table for Thin Image is depleted.
■The number of pairs that can be created in a
snapshot tree has exceeded the maximum.
CMDRJE Executing 2E11 8003 The operation cannot be performed because
power-o is in progress.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E11 9701 A pair cannot be created because the specied
snapshot group contains Thin Image pairs with
the clone attribute and without the clone
attribute.
CMDRJE Executing 2E11 9702 A pair cannot be created in the same
consistency group as the Thin Image pair which
uses the specied P-VOL as an S-VOL.
CMDRJE Executing 2E13 0000 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because the specied P-
VOL is a LUSE volume.
CMDRJE Executing 2E13 6003 A pair cannot be created because there is a pair
in the specied primary volume, which is using
a dierent pool number from the specied pool
number.
CMDRJE Executing 2E13 6004 The specied pair operation cannot be
performed for the specied pool.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 487
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E13 9900 The consistency group to be used in the
specied Snapshot Group is in one of the
following status:
■The number of pairs that can be dened in a
consistency group exceeds the maximum.
■The pair created by using the same P-VOL
already exists in the specied consistency
group.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 0008 The command ends abnormally because an
unmounted volume is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 0009 The command ends abnormally because the
blocked volume is specied as the P-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000A The command ends abnormally because the
volume in formatting is specied as the P-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E20 000B The command ends abnormally because an
unmounted volume is specied as the S-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000C The command ends abnormally because the
blocked volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000D The command ends abnormally because the
volume in formatting is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E20 0201 When you create a pair with the clone attribute,
you must specify the S-VOL.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 488
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension1) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
CMDRJE Executing 2E21 8109 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created due to one of the
following reasons:
■The shared memory is not expanded for
necessary capacity.
■It is in the initializing process.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E21 9010 The program product is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage
machine is not dened on the specied LDEV.
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2E30 000C The specied LDEV is used as a quorum disk.
CMDRJE Executing 2E30 0076 A pair cannot be created because the volume is
already used in the S-VOL of a Thin Image pair
or a Copy-on-Write Snapshot pair is specied as
the P-VOL.
CMDRJE Executing 2E30 0077 A pair cannot be created because the volume is
already used as the P-VOL of a Thin Image pair
or a Copy-on-Write Snapshot pair is specied as
the S-VOL.
CMDRJE Executing 2E30 0078 A pair cannot be created because the volume is
already used as the S-VOL of a Thin Image pair
or a Copy-on-Write Snapshot pair is specied as
the S-VOL.
CMDRJE Executing 2E30 007A The command ends abnormally because the
volume other than OPEN-V is specied as the P-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 489
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 007B A pair cannot be created because the volume
whose command device is set is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E30 007C The command ends abnormally because the
volume other than OPEN-V is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E30 007D A pair cannot be created because the volume
whose command device is set is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E30 007E The command ends abnormally because the
volume having no path denition is specied as
the P-VOL of a Thin Image pair or the specied
Thin Image pair does not exist.
CMDRJE Executing 2E30 007F The command ends abnormally because the
volume having no path denition is specied as
the S-VOL of a Thin Image pair or the specied
Thin Image pair does not exist.
CMDRJE Executing 2E30 0080 The command ends abnormally because the
external volume mapped for the online data
migration is specied as the P-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 0081 The command ends abnormally because the
external volume mapped for the online data
migration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 0090 The pair operation is rejected because the
specied volume as the primary volume is a
reserved volume for GAD, or a volume for the
GAD pair which is in the invalid status.
CMDRJE Executing 2E30 0091 The pair operation is rejected because the
specied volume as the secondary volume is a
reserved volume for GAD, or a volume for
aGAD pair.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 490
raidcom add snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0201 The specied LDEV is an external volume of
which Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0202 The specied LDEV is a virtual volume of which
Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
CMDRJE Executing 2E30 600E A pair cannot be created because the attribute
of the pool is other than Thin Image or Copy-
on-Write Snapshot.
A pair for which a snapshot group was specied
cannot be created because the specied pool is
one of the following:
■A pool for which Data Direct Mapping
attribute is enabled.
■A pool for HDT.
■A pool for mainframe.
CMDRJE Executing 2E31 9002 A pair cannot be created because the capacity
exceeds the licensed capacity.
CMDRJE Executing 2E31 9701 For creation of a pair with the cascade or clone
attribute, a Dynamic Provisioning V-VOL is not
specied for the S-VOL.
CMDRJE Executing 2E31 9702 A pair cannot be created in the specied pool
due to restrictions of the system.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EC6 FEEC An internal error occurred. Call customer
support.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 491
SSB codes returned by raidcom modify snapshot
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 000B The MU number exceeds the maximum.
CMDRJE Executing 2E00 0028 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E02 9701 The command cannot be executed because the
clone specication of the input parameter and
the clone attribute of a Thin Image pair to be
operated do not match.
CMDRJE Executing 2E10 0033 The command ends abnormally because the
ShadowImage reserved volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0034 The command ends abnormally because the
Volume Migration source volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0035 The command ends abnormally because the
Volume Migration target volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0036 The command ends abnormally because the
Volume Migration reserved volume is specied
as the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003F The command ends abnormally because the
quorum disk is specied as the P-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0043 The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
TrueCopy pair status is other than PSUS or PSUE
when the volume is shared between the P-VOL
of a Thin Image/Copy-on-Write Snapshot pair
and the P-VOL of a TrueCopy pair.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 492
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0044 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be restored because the Universal
Replicator pair status is other than PSUS or PSUE
when the volume is shared between the P-VOL
of a Thin Image/Copy-on-Write Snapshot pair
and the P-VOL of a Universal Replicator pair.
CMDRJE Executing 2E10 0047 A Snapshot data cannot be obtained because
the TrueCopy pair status is COPY when the
volume is shared between the P-VOL of a Thin
Image/Copy-on-Write Snapshot pair and the S-
VOL of a TrueCopy pair.
CMDRJE Executing 2E10 0048 A Snapshot data cannot be obtained because
the Universal Replicator pair status is COPY
when the volume is shared between the P-VOL
of a Thin Image/Copy-on-Write Snapshot pair
and the S-VOL of a Universal Replicator pair.
CMDRJE Executing 2E10 0049 The command ends abnormally because the
ShadowImage pair is being resynchronized when
the volume is shared between the P-VOL of a
Thin Image/Copy-on-Write Snapshot pair and
the P-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004A The command ends abnormally because the
ShadowImage pair status is other than PSUS
when the volume is shared between P-VOL of a
Thin Image/Copy-on-Write Snapshot pair and
the S-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004B The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
Thin Image pair or the Copy-on-Write Snapshot
pair status is other than PSUS or PSUE when the
volume is shared between the P-VOL of a Thin
Image/Copy-on-Write Snapshot pair and the P-
VOL of a ShadowImage pair.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 493
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 004C The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
Thin Image pair or the Copy-on-Write Snapshot
pair status is other than PSUS when the volume
is shared between the P-VOL of a Thin Image/
Copy-on-Write Snapshot pair and the S-VOL of a
ShadowImage pair.
CMDRJE Executing 2E10 004D A Snapshot data cannot be obtained because
the TrueCopy asynchronous pair status is other
than PSUS or PSUE when the volume is shared
between the P-VOL of a Thin Image/Copy-on-
Write Snapshot pair and the S-VOL of a
TrueCopy asynchronous pair.
CMDRJE Executing 2E10 004E The operation cannot be performed because the
P-VOL of the ShadowImage pair on which the
Quick Restore is being operated is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0051 The pair operation cannot be performed
because the volume which species the volume
using two mirrors cannot accept the specied
command in the following congurations using
three Universal Replicator sites.
■3DC multi target conguration
■3DC cascade conguration
■Delta resync conguration
CMDRJE Executing 2E10 0052 A Thin Image pair operation cannot be
performed because the pair status of all Thin
Image pairs sharing the specied P-VOL is PSUE.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 494
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0061 The Thin Image pair operation cannot be
performed because the virtual LDEV ID of the
specied volume is deleted.
CMDRJE Executing 2E10 6018 A Thin Image pair cannot be created due to one
of the following reasons:
■The pool usage value exceeds the threshold
value.
■The specied pool is blocked.
CMDRJE Executing 2E10 6019 A Snapshot data cannot be obtained because
the pool or the pool-VOL is blocked.
CMDRJE Executing 2E10 8100 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because there are not
enough pair tables.
CMDRJE Executing 2E10 8101 A Thin Image pair or a Copy-on-Write Snapshot
pair cannot be created because there are not
enough dierential tables.
CMDRJE Executing 2E10 8102 A pair cannot be created because there is not
enough free shared memory space.
CMDRJE Executing 2E10 9700 The command ends abnormally because other
than the raidcom add snapshot command is
issued for the volume other than the Thin Image
pair or the Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 9701 The command ends abnormally because the
pair is in the state of unacceptable the
command.
CMDRJE Executing 2E10 9702 The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
volume is shared between the P-VOL of a Thin
Image/Copy-on-Write Snapshot pair and the S-
VOL of a TrueCopy pair.
CMDRJE Executing 2E10 9703 The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
volume is shared between the P-VOL of a Thin
Image/Copy-on-Write Snapshot pair and the S-
VOL of a Universal Replicator pair.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 495
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 9704 The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored due to one of
the following reasons:
■Snapshot data of a restore target Thin Image
pair or Copy-on-Write Snapshot pair is being
obtained per consistency group.
■Snapshot data of a dierent pair whose
primary volume is the restore target P-VOL of
a Thin Image pair or a Copy-on-Write
Snapshot pair is being obtained per
consistency group.
CMDRJE Executing 2E10 9710 The clone attribute of the specied Thin Image
pair is enabled.
CMDRJE Executing 2E10 9713 The operation cannot be performed because the
snapshot tree is being deleted.
CMDRJE Executing 2E10 9714 The specied snapshot group name cannot be
changed because it is already registered.
CMDRJE Executing 2E10 9800 An error occurred at the operation of Thin Image
due to one of the following reasons:
■The LDEV number specied for the P-VOL or
the S-VOL is incorrect.
■The LDEV specied as the P-VOL or the S-VOL
is not paired.
■The pair of the specied P-VOL or the S-VOL
is not ready to perform the specied
operation.
■The specied Snapshot ID (MU number) is
wrong.
■The specied Snapshot ID (MU number) is
already used.
■The specied pool is not in the usable status.
■The license capacity has exceeded the
maximum.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 496
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
■The control table for Thin Image is depleted.
■The snapshot group name cannot be
changed.
CMDRJE Executing 2E11 8003 The operation cannot be performed because
power-o is in progress.
CMDRJE Executing 2E11 9703 The pair operation cannot be performed
because the status of the pair that uses the
specied P-VOL as an S-VOL is not PSUS.
CMDRJE Executing 2E11 9705 The command was rejected because pairs in the
status other than PAIR exist under the specied
pair.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 0008 The command ends abnormally because an
unmounted volume is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 0009 The command ends abnormally because the
blocked volume is specied as the P-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000A The command ends abnormally because the
volume in formatting is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension1) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E21 9010 The program product is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage machine
is not dened on the specied LDEV.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 497
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2E30 000C The specied LDEV is used as a quorum disk.
CMDRJE Executing 2E30 0079 The Thin Image pair or the Copy-on-Write
Snapshot pair cannot be restored because the
volume that is set the S-VOL Disable is specied
as the P-VOL.
CMDRJE Executing 2E30 007A The command ends abnormally because the
volume other than OPEN-V is specied as the P-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E30 0081 The command ends abnormally because the
external volume mapped for the online data
migration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 0090 The pair operation is rejected because the
specied volume as the primary volume is a
reserved volume for GAD, or the volume for the
GAD pair which is in the invalid status.
CMDRJE Executing 2E30 0091 The pair operation is rejected because the
specied volume as the secondary volume is a
reserved volume for GAD, or the volume for the
GAD pair.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0201 The specied LDEV is an external volume of
which Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0202 The specied LDEV is a virtual volume of which
Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EC6 FEEC An internal error occurred. Call customer
support.
CMDRJE Executing 2EF3 0002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom modify snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 498
raidcom modify snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom get snapshot
raidcom get snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC5 FEEC An internal error occurred. Call customer
support.
SSB codes returned by raidcom delete snapshot
raidcom delete snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 000B The MU number exceeds the maximum.
CMDRJE Executing 2E00 0028 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0033 The command ends abnormally because the
ShadowImage reserved volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0034 The command ends abnormally because the
Volume Migration source volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
SSB codes returned by raidcom get snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 499
raidcom delete snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0035 The command ends abnormally because the
Volume Migration target volume is specied as
the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0036 The command ends abnormally because the
Volume Migration reserved volume is specied
as the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0049 The command ends abnormally because the
ShadowImage pair is being resynchronized
when the volume is shared between the P-VOL
of a Thin Image/Copy-on-Write Snapshot pair
and the P-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004A The command ends abnormally because the
ShadowImage pair status is other than PSUS
when the volume is shared between P-VOL of a
Thin Image/Copy-on-Write Snapshot pair and
the S-VOL of a ShadowImage pair.
CMDRJE Executing 2E10 004D A Snapshot data cannot be obtained because
the TrueCopy asynchronous pair status is other
than PSUS or PSUE when the volume is shared
between the P-VOL of a Thin Image/Copy-on-
Write Snapshot pair and the S-VOL of a
TrueCopy asynchronous pair.
CMDRJE Executing 2E10 004E The operation cannot be performed because
the P-VOL of the ShadowImage pair on which
the Quick Restore is being operated is specied
as the P-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
SSB codes returned by raidcom delete snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 500
raidcom delete snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0061 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 0204 The operation failed because the specied
LDEV which is holding the attribute of SLU is
bind to the LDEV which is holding the attribute
of ALU.
CMDRJE Executing 2E10 6019 A Snapshot data cannot be obtained because
the pool or the pool-VOL is blocked.
CMDRJE Executing 2E10 9700 The command ends abnormally because other
than the raidcom add snapshot command is
issued for the volume other than the Thin
Image pair or the Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 9701 The command ends abnormally because the
pair is in the state of unacceptable the
command.
CMDRJE Executing 2E10 9800 An error occurred at the operation of Thin
Image due to one of the following reasons:
■The LDEV number specied for the P-VOL or
the S-VOL is incorrect.
■The LDEV specied as the P-VOL or the S-
VOL is not paired.
■The pair of the specied P-VOL or the S-VOL
is not ready to perform the specied
operation.
■The specied Snapshot ID (MU number) is
wrong.
■The specied Snapshot ID (MU number) is
already used.
■The specied pool is not in the usable
status.
■The license capacity has exceeded the
maximum.
■The control table for Thin Image is depleted.
CMDRJE Executing 2E11 2206 You do not have the operation authority to
operate the target resource group.
SSB codes returned by raidcom delete snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 501
raidcom delete snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Specify the resource group that is allocated to
the user group as the operation target, or set
the operation authority to the user group in
order to operate the target resource group.
CMDRJE Executing 2E11 8003 The operation cannot be performed because
power-o is in progress.
CMDRJE Executing 2E11 9704 The operation cannot be performed because a
pair exists under the specied pair.
CMDRJE Executing 2E11 9706 The operation cannot be performed because
the specied volume is not a root volume of a
pair with the cascade or clone attribute, or the
volume is an S-VOL in another snapshot tree.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 0008 The command ends abnormally because an
unmounted volume is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 0009 The command ends abnormally because the
blocked volume is specied as the P-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension2) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage
machine is not dened on the specied LDEV.
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2EC6 FEEC An internal error occurred. Call customer
support.
SSB codes returned by raidcom delete snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 502
raidcom delete snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom map snapshot
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0028 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E00 0029 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0020 The command ends abnormally because the
volume that has the size exceeding the
supported size is specied as the P-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0025 The command ends abnormally because the
LUSE volumes of dierent structure are
specied as the P-VOL and the S-VOL.
CMDRJE Executing 2E10 0027 The command ends abnormally because the
external volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0028 The command ends abnormally because the
volume other than V-VOL is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 503
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0029 The command ends abnormally because the
pool-VOL is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002A The command ends abnormally because the
volume (the data volume or the journal volume)
of the Universal Replicator pair that is in the
intermediate site of the 3DC cascading
conguration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002B The command ends abnormally because the P-
VOL of a Universal Replicator pair is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 002C The command ends abnormally because the S-
VOL of a Universal Replicator pair is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 002D The command ends abnormally because the
journal volume of the Universal Replicator is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002E The command ends abnormally because the
volume to which S-VOL Disable option is set is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002F The command ends abnormally because the
volume to which VMA is set is specied as the
S-VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0030 The command ends abnormally because the
volumes of dierent Max LBA size are specied
as the P-VOL and S-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0031 The command ends abnormally because the
volumes whose the number of slots is dierent
are specied as the P-VOL and S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 504
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0032 A pair cannot be created because the Dynamic
Provisioning V-VOL is specied as the S-VOL of a
Thin Image pair or the specied Thin Image pair
does not exist.
CMDRJE Executing 2E10 0037 The command ends abnormally because the P-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0038 The command ends abnormally because the S-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 003A The command ends abnormally because the
Volume Migration source volume is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003B The command ends abnormally because the
Volume Migration target volume is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003E The command ends abnormally because the
volume of Universal Replicator pair for the
delta resync operation is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0045 The command ends abnormally because the P-
VOL of a TrueCopy pair is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0046 The command ends abnormally because the S-
VOL of a TrueCopy pair is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 505
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
CMDRJE Executing 2E10 005F The command ends abnormally because the
specied S-VOL is assigned to a Thin Image
pair.
CMDRJE Executing 2E10 0203 The operation failed because the setting of the
T10 PI attribute is not match between the
specied P-VOL and the specied S-VOL.
CMDRJE Executing 2E10 0211 The command ends abnormally because the
volume which is being deleted is specied.
CMDRJE Executing 2E10 9709 The command ends abnormally because the
specied Thin Image pair does not exist.
CMDRJE Executing 2E10 970B The command ends abnormally because the
specied Thin Image pair is assigned to an S-
VOL.
CMDRJE Executing 2E10 9713 The operation cannot be performed because
the snapshot tree is being deleted.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 0008 The command ends abnormally because an
unmounted volume is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000B The command ends abnormally because an
unmounted volume is specied as the S-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000C The command ends abnormally because the
blocked volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 506
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 000D The command ends abnormally because the
volume in formatting is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension1) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
CMDRJE Executing 2E21 9010 The program product is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage
machine is not dened on the specied LDEV.
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2E30 0077 The command ends abnormally because the
volume is already used as the P-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair is
specied as the S-VOL.
CMDRJE Executing 2E30 0078 The command ends abnormally because the
volume is already used as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair is
specied as the S-VOL.
CMDRJE Executing 2E30 007C The command ends abnormally because the
volume other than OPEN-V is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E30 007D The command ends abnormally because the
volume whose command device is set is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 007F The command ends abnormally because the
volume having no path denition is specied as
the S-VOL of a Thin Image pair or the specied
Thin Image pair does not exist.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 507
raidcom map snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 0081 The command ends abnormally because the
external volume mapped for the online data
migration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 008F The command ends abnormally because the
specied P-VOL is not a P-VOL of a Thin Image
pair.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0201 The specied LDEV is an external volume of
which Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0202 The specied LDEV is a virtual volume of which
Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
CMDRJE Executing 2E30 0207 The operation cannot be performed because
the specied volume is a DP-VOL with the SLU
attribute.
CMDRJE Executing 2E30 2E30 The specied LDEV is a V-VOL for which the
Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E31 9701 For mapping pairs with the cascade or clone
attribute, the Dynamic Provisioning V-VOL is not
specied as an S-VOL.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B980 B903 The operation cannot be performed because
the selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom map snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 508
SSB codes returned by raidcom replace snapshot
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0029 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0020 The command ends abnormally because the
volume that has the size exceeding the
supported size is specied as the P-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0025 The command ends abnormally because the
LUSE volumes of dierent structure are
specied as the P-VOL and the S-VOL.
CMDRJE Executing 2E10 0027 The command ends abnormally because the
external volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0028 The command ends abnormally because the
volume other than V-VOL is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0029 The command ends abnormally because the
pool-VOL is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002A The command ends abnormally because the
volume (the data volume or the journal volume)
of the Universal Replicator pair that is in the
intermediate site of the 3DC cascading
conguration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002B The command ends abnormally because the P-
VOL of a Universal Replicator pair is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
SSB codes returned by raidcom replace snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 509
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 002C The command ends abnormally because the S-
VOL of a Universal Replicator pair is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 002D The command ends abnormally because the
journal volume of the Universal Replicator is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002E The command ends abnormally because the
volume to which S-VOL Disable option is set is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 002F The command ends abnormally because the
volume to which VMA is set is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0030 The command ends abnormally because the
volumes of dierent Max LBA size are specied
as the P-VOL and S-VOL of a Thin Image pair or
a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0031 The command ends abnormally because the
volumes whose the number of slots is dierent
are specied as the P-VOL and S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0032 A pair cannot be created because the Dynamic
Provisioning V-VOL is specied as the S-VOL of a
Thin Image pair or the specied Thin Image pair
doest not exist.
CMDRJE Executing 2E10 0037 The command ends abnormally because the P-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Imagepair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0038 The command ends abnormally because the S-
VOL of a ShadowImage pair is specied as the
S-VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
SSB codes returned by raidcom replace snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 510
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 003A The command ends abnormally because the
Volume Migration source volume is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003B The command ends abnormally because the
Volume Migration target volume is specied as
the S-VOL of a Thin Image pair or a Copy-on-
Write Snapshot pair.
CMDRJE Executing 2E10 003E The command ends abnormally because the
volume of Universal Replicator pair for the delta
resync operation is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E10 0045 The command ends abnormally because the P-
VOL of a TrueCopy pair is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0046 The command ends abnormally because the S-
VOL of a TrueCopy pair is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
CMDRJE Executing 2E10 0060 The command ends abnormally because the
specied S-VOL is not assigned to a Thin Image
pair.
CMDRJE Executing 2E10 0061 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 0204 The operation failed because the specied LDEV
which is holding the attribute of SLU is bind to
the LDEV which is holding the attribute of ALU.
SSB codes returned by raidcom replace snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 511
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 9709 The command ends abnormally because the
specied Thin Image pair is not exist.
CMDRJE Executing 2E10 970B The command ends abnormally because the
specied Thin Image pair is assigned to an S-
VOL.
CMDRJE Executing 2E10 970C The command ends abnormally because the
specied Thin Image pair is not assigned to an
S-VOL.
CMDRJE Executing 2E10 9710 The clone attribute of the specied Thin Image
pair is enabled.
CMDRJE Executing 2E10 9711 The operation cannot be performed because
the S-VOL is the node volume.
CMDRJE Executing 2E10 9713 The operation cannot be performed because
the snapshot tree is being deleted.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 000B The command ends abnormally because an
unmounted volume is specied as the S-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000C The command ends abnormally because the
blocked volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000D The command ends abnormally because the
volume in formatting is specied as the S-VOL
of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension1) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
SSB codes returned by raidcom replace snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 512
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 9010 The program product is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage
machine is not dened on the specied LDEV.
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2E30 0077 The command ends abnormally because the
volume is already used as the P-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair is
specied as the S-VOL.
CMDRJE Executing 2E30 0078 The command ends abnormally because the
volume is already used as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair is
specied as the S-VOL.
CMDRJE Executing 2E30 007C The command ends abnormally because the
volume other than OPEN-V is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E30 007D The command ends abnormally because the
volume whose command device is set is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 007F The command ends abnormally because the
volume having no path denition is specied as
the S-VOL of a Thin Image pair or the specied
Thin Image pair doest not exist.
CMDRJE Executing 2E30 0081 The command ends abnormally because the
external volume mapped for the online data
migration is specied as the S-VOL of a Thin
Image pair or a Copy-on-Write Snapshot pair.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0201 The specied LDEV is an external volume of
which Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0202 The specied LDEV is a virtual volume of which
Data Direct Mapping attribute is enabled.
SSB codes returned by raidcom replace snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 513
raidcom replace snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E31 9701 For replacement of pairs with the cascade or
clone attribute, a Dynamic Provisioning V-VOL is
not specied for the S-VOL.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B980 B903 The operation cannot be performed because
the selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom unmap snapshot
raidcom unmap snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0028 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the P-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E00 0029 The command ends abnormally because the
volume whose LDEV number is out of range is
specied as the S-VOL of a Thin Image pair or a
Copy-on-Write Snapshot pair.
CMDRJE Executing 2E10 0028 The command ends abnormally because the
volume other than V-VOL is specied as the S-
VOL of a Thin Image pair or a Copy-on-Write
Snapshot pair.
CMDRJE Executing 2E10 0056 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 005B The Thin Image pair operation cannot be
performed because the virtual storage machine
of the specied P-VOL is dierent from the
virtual storage machine of the specied S-VOL.
SSB codes returned by raidcom unmap snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 514
raidcom unmap snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0060 The command ends abnormally because the
specied S-VOL is not assigned to a Thin Image
pair.
CMDRJE Executing 2E10 0061 The specied volume cannot be used for the
Thin Image pair operation because the virtual
LDEV ID is deleted.
CMDRJE Executing 2E10 0204 The operation failed because the specied
LDEV which is holding the attribute of SLU is
bind to the LDEV which is holding the attribute
of ALU.
CMDRJE Executing 2E10 9709 The command ends abnormally because the
specied Thin Image pair is not exist.
CMDRJE Executing 2E10 970C The command ends abnormally because the
specied Thin Image pair is not assigned to an
S-VOL.
CMDRJE Executing 2E10 9710 The clone attribute of the specied Thin Image
pair is enabled.
CMDRJE Executing 2E10 9711 The operation cannot be performed because
the S-VOL is the node volume.
CMDRJE Executing 2E10 9713 The operation cannot be performed because
the snapshot tree is being deleted.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E20 0000 The specied LDEV is not dened.
CMDRJE Executing 2E20 0008 The command ends abnormally because an
unmounted volume is specied as the P-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E20 000B The command ends abnormally because an
unmounted volume is specied as the S-VOL of
a Thin Image pair or a Copy-on-Write Snapshot
pair.
SSB codes returned by raidcom unmap snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 515
raidcom unmap snapshot
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 000C The command ends abnormally because the
blocked volume is specied as the S-VOL of a
Thin Image pair or a Copy-on-Write Snapshot
pair.
CMDRJE Executing 2E21 8107 The command ends abnormally because the
shared memory (FC, TPF, or Extension1) is not
added for necessary capacity or maintenance
work is being performed.
CMDRJE Executing 2E21 8108 The shared memory for Thin Image or Copy-on-
Write Snapshot is not installed.
CMDRJE Executing 2E21 9010 The program product is not installed.
CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage
machine is not dened on the specied LDEV.
CMDRJE Executing 2E21 930A The virtual storage machine with the specied
serial number is not found.
CMDRJE Executing 2E30 008F The command ends abnormally because the
specied P-VOL is not a P-VOL of a Thin Image
pair.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0201 The specied LDEV is an external volume of
which Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 0202 The specied LDEV is a virtual volume of which
Data Direct Mapping attribute is enabled.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B980 B903 The operation cannot be performed because
the selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom unmap snapshot
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 516
SSB codes returned by raidcom add ssid
raidcom add ssid
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 The CU number of the RCU exceeds the
eective value.
CMDRJE Executing 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
CMDRJE Executing 2E00 7100 The CU number is out of eective range.
CMDRJE Executing 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E20 3000 The serial number, product ID, or SSID of the
target storage system is incorrect.
CMDRJE Executing 2E20 3001 The command cannot be executed because the
specied RCU is not registered.
CMDRJE Executing 2E22 3002 The operation cannot be performed due to one
of the following reasons:
■The number of RCUs registered in MCU or
RCU is more than four.
■The number of RCUs registered in the
system is more than 64 in the case of
specifying the cu free.
CMDRJE Executing 2E23 3301 The number of the specied SSIDs is invalid.
CMDRJE Executing 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
CMDRJE Executing 2ED6 00EF An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The SSID is invalid.
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom add ssid
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 517
SSB codes returned by raidcom delete ssid
raidcom delete ssid
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 The CU number of the RCU exceeds the
eective value.
CMDRJE Executing 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
CMDRJE Executing 2E00 7100 The CU number is out of eective range.
CMDRJE Executing 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E20 3000 The serial number, the product ID, or the SSID
of the remote storage system is invalid.
CMDRJE Executing 2E20 3001 The command cannot be executed because the
specied RCU is not registered.
CMDRJE Executing 2E23 3301 The number of the specied SSIDs is invalid.
CMDRJE Executing 2ED6 00EF An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The SSID is invalid.
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom add dp_pool
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
CMDRJE Executing 2E00 6001 The type of pool is invalid.
SSB codes returned by raidcom delete ssid
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 518
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6002 The maximum reserve ratio of V-VOL is out of
range.
CMDRJE Executing 2E00 6009 The threshold of the specied High water mark
is out of range.
CMDRJE Executing 2E00 600A The operation cannot be performed because
the specied threshold of Warning is larger
than the threshold of the specied High water
mark.
Get Command
Status
Async 2E10 0009 The specied LDEV is in the state of blocked.
Get Command
Status
Async 2E10 000C The operation cannot be performed because a
SATA-E drive in the state of quick formatting is
in the specied LDEV.
CMDRJE Executing 2E10 0011 The specied LDEV is in the state of blocked, or
not installed.
Get Command
Status
Async 2E10 0102 The pool cannot be created because there are
not enough resources (VDEV) depending on
cache management devices.
Get Command
Status
Async 2E10 600D The operation cannot be performed because
the pool volume is being deleted.
Get Command
Status
Async 2E10 6029 The lowest tier cannot be added because either
of the following applies to the specied pool:
■The pool contains a volume for which
capacity saving is enabled.
■The deduplication function is enabled.
Get Command
Status
Async 2E10 8002 The specied operation is not supported in the
current microcode version.
Get Command
Status
Async 2E11 005F The operation failed because accelerated
compression of the parity group to which the
specied LDEV belongs is enabled and the
other LDEV in the parity group is being used for
the other pool.
Get Command
Status
Async 2E11 0108 The specied LDEV is the LDEV conguring the
RAID conguration which cannot be used for
the pool volume.
SSB codes returned by raidcom add dp_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 519
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E11 6003 The pool is not in the status where the pool
volume can be added.
Get Command
Status
Async 2E11 8003 The operation cannot be performed because
the power supply is switched o.
Get Command
Status
Async 2E11 800F The operation cannot be performed because
the unsupported microcode version exists in
the system.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E13 6009 The operation cannot be performed because
the pool capacity is insucient for Data Direct
Mapping.
Get Command
Status
Async 2E20 0000 The specied LDEV is not installed.
Get Command
Status
Async 2E21 8103 The operation cannot be performed because
the memory capacity of the shared memory is
insucient.
Get Command
Status
Async 2E21 8106 The operation cannot be performed because
the shared memory is not initialized.
CMDRJE Executing 2E21 9007 Dynamic Provisioning program product is not
installed.
Get Command
Status
Async 2E21 9014 Data Retention Utility program product is not
installed.
Get Command
Status
Async 2E22 0005 Exceeded the number of pool volume that can
be registered in a pool.
Get Command
Status
Async 2E22 000D The larger number of drive types than the
supported conguration cannot be added to
the specied pool.
Get Command
Status
Async 2E22 6100 Pool volume cannot be registered because the
drive type of the specied LDEV is dierent
from the other pool volume type, or the drive
type in the pool exceeds three.
CMDRJE Executing 2E23 0008 The number of specied LDEVs is invalid.
SSB codes returned by raidcom add dp_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 520
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E30 0000 The emulation type of the specied LDEV
cannot be used as a pool VOL.
Get Command
Status
Async 2E30 0007 The specied LDEV has the LU path denition.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000D The specied LDEV is used as a system disk.
Get Command
Status
Async 2E30 000E The specied LDEV is already used as a pool
volume.
Get Command
Status
Async 2E30 0010 The specied LDEV is a command device.
Get Command
Status
Async 2E30 0038 It cannot be used as a pool volume because the
size of the specied LDEV is less than 8GB.
Get Command
Status
Async 2E30 0039 Creating a pool or adding a pool volume cannot
be performed because CLPR is mixed in the
specied pool.
Get Command
Status
Async 2E30 004D The number of LDEVs that can be created in the
parity group or the external volume exceeds
the maximum.
Get Command
Status
Async 2E30 005C The specied LDEV is used as a V-VOL.
Get Command
Status
Async 2E30 005D The specied LDEV is a volume of unsupported
Dynamic Tiering or active ash.
Get Command
Status
Async 2E30 005E The specied LDEV is used in another program
product.
CMDRJE Executing 2E30 006C An LDEV, whose emulation type is not available
to be mixed, is in the specied LDEVs.
SSB codes returned by raidcom add dp_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 521
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 006E The operation cannot be performed for the
following reasons:
■The pool volumes to be added to the
Dynamic Tiering pool or active ash pool
include external volumes whose cache
modes are invalid.
■The Dynamic Provisioning pool includes
both external volumes whose cache modes
are invalid and internal volumes.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0071 A pool volume cannot be added because the
LDEV of the resource group dierent from the
resource group of the pool volume to which the
specied pool belongs is specied.
Get Command
Status
Async 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
Get Command
Status
Async 2E30 0085 The specied volume cannot be used as a pool
volume.
Get Command
Status
Async 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2E30 6000 The threshold value 1 is out of range.
Get Command
Status
Async 2E30 6004 The specied pool attribute diers from the
pool attribute of existed pool.
Get Command
Status
Async 2E30 6013 The LDEV that belongs to the parity group
which accelerated compression is enabled
cannot be added to the pool with the DP-VOL
which is full allocated.
Get Command
Status
Async 2E31 0015 The RAID level of the specied LDEV is dierent
with the RAID level of others.
Get Command
Status
Async 2E31 0016 There is a blocked pool volume.
Get Command
Status
Async 2E31 0018 External volumes whose cache modes are
dierent are included.
CMDRJE Executing 2E31 6001 The POOL Name is duplicated with another
pool.
SSB codes returned by raidcom add dp_pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 522
raidcom add dp_pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E31 6004 The pool cannot include volumes in dierent
RAID levels because the pool cannot include
those volumes. Or the pool cannot include the
RAID 1 volumes and the volumes of other RAID
levels together.
Get Command
Status
Async 2E31 6005 The pool cannot include both internal volumes
and external volumes because the pool is not
set to Mixable.
Get Command
Status
Async 2E31 9000 The usage capacity exceeds the license capacity
of program product.
CMDRJE Executing 2EE7 00EE The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing/
Async
2EE7 FEEC An internal error occurred.
Call customer support.
Get Command
Status
Async 2EE7 FFFF An internal error occurred.
Call customer support.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom modify rcu
raidcom modify rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 CU# of RCU exceed the eective value.
CMDRJE Executing 2E00 3002 The value of least path number is invalid.
CMDRJE Executing 2E00 3003 The value of RIO MIH time is invalid.
CMDRJE Executing 2E00 3004 The value of Round-trip response time is
invalid.
SSB codes returned by raidcom modify rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 523
raidcom modify rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3005 Invalid product ID or path registration ID.
CMDRJE Executing 2E00 3007 Incident that is created by CU is not in the one
of followings.
- Incident that is sent to MCU host and RCU.
- Incident that is sent to RCU.
Get Command
Status
Async 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
Get Command
Status
Async 2E00 3009 The command cannot be executed because all
the CU numbers in the RCU is not unied at the
path that is specied creation or deletion.
CMDRJE Executing 2E00 7100 The CU number is out of eective range.
CMDRJE Executing 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E20 3000 The serial number, the product ID, or the SSID
of the target storage system is incorrect.
CMDRJE Executing 2E20 3001 The attribute of the RCU cannot be changed
because the specied RCU is not registered.
Get Command
Status
Async 2E21 7101 The specied CU number is not dened, or an
LDEV is not dened under the CU number.
CMDRJE Executing 2E23 3101 The operation cannot be performed because
the number of paths becomes less than the
least path number.
Get Command
Status
Async 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
CMDRJE Executing 2ED6 00EF An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The value of SSID for the remote storage
system is invalid.
SSB codes returned by raidcom modify rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 524
SSB codes returned by raidcom delete rcu_path
raidcom delete rcu_path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 The CU# of RCU exceeds the eective value.
CMDRJE Executing 2E00 3005 The product ID or the path registration ID is
invalid.
Get Command
Status
Async 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
CMDRJE Executing 2E00 3200 The specied port # on the side of RCU is
invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E00 7100 The CU number is out of eective range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 8400 The value of the specied port is invalid.
Get Command
Status
Async 2E10 3101 Failed to establish a path or the deletion
operation. The following factor can be thought.
■Input parameter is invalid.
■Port status or the MP Blade status is in the
state of abnormal.
■Cable is not connected correctly.
■Port is specied incorrectly.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 3001 A logical path cannot be deleted because the
specied RCU is not registered.
Get Command
Status
Async 2E21 7101 The specied CU number is not dened, or an
LDEV is not dened under the CU number.
Get Command
Status
Async 2E23 3101 The operation cannot be performed because
the number of paths becomes less than the
least path number.
SSB codes returned by raidcom delete rcu_path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 525
raidcom delete rcu_path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 840A The port attribute is not Initiator (MCU).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
Get Command
Status
Async 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
Get Command
Status
Async 2E31 3101 The command cannot be executed because the
serial number is not unied in the specied
path.
CMDRJE Executing 2ED6 00EE The command cannot be accepted because the
DKC is busy. After a while, execute the same
command.
Get Command
Status
Async 2ED6 3005 An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom add rcu_path
raidcom add rcu_path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 CU# of RCU exceeds the eective value.
CMDRJE Executing 2E00 3005 Invalid product ID or path registration ID.
Get Command
Status
Async 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
SSB codes returned by raidcom add rcu_path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 526
raidcom add rcu_path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 3009 The command cannot be executed because all
the CU numbers in the RCU is not unied at the
path that is specied creation or deletion.
CMDRJE Executing 2E00 3200 The value of port # on the side of RCU is invalid.
CMDRJE
Get Command
Status
Executing
/Async
2E00 7100 The CU number is out of eective range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 8400 The value of the specied port is invalid.
Get Command
Status
Async 2E10 3101 Failed to establish a path or the deletion
operation. The following factor can be thought.
■Input parameter is invalid.
■Port status or the MP Blade status is in the
state of abnormal.
■Cable is not connected correctly.
■Port is specied incorrectly.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 3000 The serial number, the product ID, or the SSID
of the target storage system is incorrect.
Get Command
Status
Async 2E20 3001 A logical path cannot be added because the
specied RCU is not registered.
Get Command
Status
Async 2E21 7101 The specied CU number is not dened, or an
LDEV is not dened under the CU number.
Get Command
Status
Async 2E23 3100 An RCU path cannot be added because the
number of valid paths exceeds the maximum.
Get Command
Status
Async 2E23 3101 The operation cannot be performed because
the number of paths becomes less than the
least path number.
SSB codes returned by raidcom add rcu_path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 527
raidcom add rcu_path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 840A The port attribute is not Initiator (MCU).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
Get Command
Status
Async 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
Get Command
Status
Async 2E31 3101 The command cannot be executed because the
serial number is not unied in the specied
path.
CMDRJE Executing 2ED6 00EE The command cannot be accepted because the
DKC is busy. After a while, execute the same
command.
Get Command
Status
Async 2ED6 3005 An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage
system is invalid.
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom delete rcu
raidcom delete rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 CU# on the RCU exceeds the eective range.
CMDRJE Executing 2E00 3005 Invalid product ID or path registration ID.
Get Command
Status
Async 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
SSB codes returned by raidcom delete rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 528
raidcom delete rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3200 The value of the specied port# on the RCU
side is invalid.
Get Command
Status
Async 2E00 7100 The CU number is out of eective range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 8400 The value of the specied port is invalid.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 3000 The serial number, the product ID, or the SSID
of the target storage system is incorrect.
Get Command
Status
Async 2E20 3001 The specied RCU cannot be deleted because
the RCU is not registered.
Get Command
Status
Async 2E21 7101 The specied CU number is not dened, or an
LDEV is not dened under the CU number.
Get Command
Status
Async 2E22 3101 The path cannot be deleted because there is a
pair of TrueCopy/Universal Replicator, or a
journal volume is in the target CU.
Get Command
Status
Async 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
CMDRJE Executing 2ED6 00EE The command cannot be accepted because the
DKC is busy. After a while, execute the same
command.
Get Command
Status
Async 2ED6 3005 An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage
system is invalid.
CMDRJE Executing 2EDE 00D1 RCU storage system does not exist.
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom delete rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 529
SSB codes returned by raidcom add rcu
raidcom add rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3001 The value of CU# on the RCU exceeds the
eective range.
CMDRJE Executing 2E00 3005 Invalid product ID or path registration ID.
Get Command
Status
Async 2E00 3008 The command cannot be executed because the
parameter of the specied RCU is invalid.
Get Command
Status
Async 2E00 3009 The command cannot be executed because all
the CU numbers in the RCU is not unied at the
path that is specied creation or deletion.
CMDRJE Executing 2E00 3200 The value of port# on the side of RCU is invalid.
CMDRJE
Get Command
Status
Executing/
Async
2E00 7100 The CU number is out of eective range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 8400 The value of the specied port is invalid.
Get Command
Status
Async 2E10 3101 Failed to establish a path or the deletion
operation. The following factor can be thought.
■Input parameter is invalid.
■Port status or the MP Blade status is in the
state of abnormal.
■Cable is not connected correctly.
■Port is specied incorrectly.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the microcode is being changed.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E20 3000 The serial number, the product ID, or the SSID
of the target storage system is incorrect.
Get Command
Status
Async 2E21 7101 The specied CU number is not dened, or an
LDEV is not dened under the CU number.
SSB codes returned by raidcom add rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 530
raidcom add rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E22 3001 The specied RCU is already registered to
another product ID.
Get Command
Status
Async 2E22 3002 The operation cannot be performed due to one
of the following reasons:
■The number of RCUs registered in MCU or
RCU is more than four.
■The number of RCUs registered in the
system is more than 64 in the case of
specifying the cu free.
Get Command
Status
Async 2E22 3300 The specied SSID is already registered to
another RCU.
Get Command
Status
Async 2E23 3000 The specied RCU is cannot be registered
because there is no free RCU.
Get Command
Status
Async 2E23 3101 The operation cannot be performed because
the number of paths becomes less than the
least path number.
CMDRJE Executing 2E30 840A The port attribute is not Initiator (MCU).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
Get Command
Status
Async 2E31 3001 The command cannot be executed because the
RCU identication code of a path is invalid.
Get Command
Status
Async 2E31 3002 The operation cannot be performed because
the remote storage system does not support
the path between CUs.
Get Command
Status
Async 2E31 3101 The command cannot be executed because the
serial number is not unied in the specied
path.
CMDRJE Executing 2ED6 00EE The command cannot be accepted because the
DKC is busy. After a while, execute the same
command.
Get Command
Status
Async 2ED6 3005 An internal error occurred.
Call customer support.
CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage
system is invalid.
SSB codes returned by raidcom add rcu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 531
raidcom add rcu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 3002 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom delete ldev
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
Get Command
Status
Async 2E00 000E This command does not support the emulation
type of the specied LDEV.
Get Command
Status
Async 2E00 0016 The command cannot be executed by receiving
multiple operations for the same LDEV.
Get Command
Status
Async 2E10 0000 The specied LDEV is used for a pair of
ShadowImage/Thin Image/Copy-on-Write
Snapshot/Volume Migration or as a relationship
of Compatible FlashCopy® V2/Hitachi
Compatible Software for IBM® FlashCopy® SE.
Get Command
Status
Async 2E10 0001 The specied LDEV is used for a TrueCopy pair,
a Universal Replicator pair or a command
device dened by Business Continuity Manager.
Get Command
Status
Async 2E10 0002 The specied LDEV is used for a Universal
Replicator pair or a journal.
Get Command
Status
Async 2E10 0003 The specied LDEV is used as a Compatible
FlashCopy® V2 relationship.
Get Command
Status
Async 2E10 0004 The specied LDEV is used for a Thin Image pair
or a Copy-on-Write Snapshot pair.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 532
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 0005 The specied LDEV is used for aVolume
Migration.
Get Command
Status
Async 2E10 0008 The specied LDEV is used as a system disk.
Get Command
Status
Async 2E10 0012 The specied LDEV is used as a CC/XRC
attribute device.
Get Command
Status
Async 2E10 0062 The specied LDEV is used as the primary
volume for the GAD pair.
Get Command
Status
Async 2E10 0063 The specied LDEV is used as the secondary
volume for the GAD pair.
Get Command
Status
Async 2E10 020B The specied LDEV cannot be operated
because the deduplication function is set.
Get Command
Status
Async 2E10 020C The specied LDEV cannot be operated
because deduplicated data exists.
Get Command
Status
Async 2E10 020D The specied LDEV cannot be operated
because it is in the status where the capacity
saving setting cannot be disabled.
Get Command
Status
Async 2E10 0212 The operation cannot be performed because a
page is allocated to the specied LDEV. To
delete the volume, specify the -operation
initialize_capacity_saving option, or
perform any one of the following before the
deletion:
■Format the LDEV.
■Disable the capacity saving setting of the
LDEV.
■Initialize the deduplication system data
volume of the pool and the volume that
contains deduplicated data.
CMDRJE
Get Command
Status
Executing/
Async
2E10 0217 The specied LDEV cannot be operated
because it is a volume for which capacity saving
setting is disabled.
Get Command
Status
Async 2E10 600B The pool is blocked.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 533
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 6022 The operation cannot be performed because
the deduplication system data volume of the
pool linked with the specied LDEV is blocked.
Get Command
Status
Async 2E10 6026 The specied virtual volume cannot be
operated because the used capacity of the pool
associated with the specied virtual volume
exceeds the depletion threshold.
Get Command
Status
Async 2E11 0004 An LDEV that is in the state of formatting is
included in the parity group of the target LDEV.
Get Command
Status
Async 2E11 0005 An LDEV that is in the state of executing quick
format is included in the parity group of the
target LDEV.
Get Command
Status
Async 2E11 001B The specied LDEV is blocked.
CMDRJE Executing 2E11 0053 The specied LDEV is used in another
operation.
Get Command
Status
Async 2E11 0102 The parity group of the target LDEV is in the
state of correction copy.
CMDRJE Executing 2E11 0153 The parity group or the external volume group
that the specied LDEV is belongs to is used in
another operation.
Get Command
Status
Async 2E11 0202 The external volume group with the Data Direct
Mapping attribute which is allocated to the
specied LDEV is not in the state of
disconnected.
Get Command
Status
Async 2E11 6004 The operation cannot be performed because
pools are blocked.
Get Command
Status
Async 2E11 6008 The operation cannot be performed because
the pool linked with the specied LDEV is in the
unusable status.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
Get Command
Status
Async 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 534
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 8010 The storage system is in internal process, or the
conguration changing processes are
conicting.
Get Command
Status
Async 2E11 8108 The operation cannot be performed because
there is blocked part in the system.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing/
Async
2E20 0000 LDEV is not installed.
CMDRJE Executing 2E30 0007 An LU path has been dened.
Get Command
Status
Async 2E30 000A The specied LDEV is used for a Dynamic
Provisioning.
Get Command
Status
Async 2E30 000C The specied LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000E The specied LDEV is used as a pool volume.
Get Command
Status
Async 2E30 000F The specied LDEV is used as a journal volume.
Get Command
Status
Async 2E30 0006 The specied LDEV is used in the FICON® Data
Migration.
Get Command
Status
Async 2E30 0010 The specied LDEV is a command device.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0013 The specied volume cannot be deleted
because it is a LUSE volume.
Get Command
Status
Async 2E30 0014 The specied LDEV is used as a reserved
volume of Volume Migration.
Get Command
Status
Async 2E30 0018 This is a volume that the Data Retention Utility
is set.
Get Command
Status
Async 2E30 001A Volume Security is set to the specied LDEV.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 535
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 001E The specied LDEV cannot be deleted because
of online from the mainframe host.
Get Command
Status
Async 2E30 002C The specied LDEV cannot be operated
because it has not been formatted.
Get Command
Status
Async 2E30 004E The specied LDEV is a Data Retention Utility/
Volume Retention Manager attribute device.
Get Command
Status
Async 2E30 0053 This is a volume that the Volume Retention
Manager is set.
Get Command
Status
Async 2E30 0054 The specied LDEV is used as a Compatible
FlashCopy® V2 or a Hitachi Compatible Software
for IBM® FlashCopy® SE relationship.
Get Command
Status
Async 2E30 0055 The specied LDEV is used for aVolume
Migration.
Get Command
Status
Async 2E30 0056 The specied LDEV is used for aVolume
Migration
Get Command
Status
Async 2E30 0057 The specied LDEV is used as a system disk.
Get Command
Status
Async 2E30 0058 The specied LDEV is used as a system disk.
Get Command
Status
Async 2E30 0060 The specied LDEV is a command device.
Get Command
Status
Async 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
Get Command
Status
Async 2E30 0096 The specied LDEV is used as an ALU.
Get Command
Status
Async 2E30 0097 The specied LDEV is used as an SLU.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
Get Command
Status
Async 2E30 4102 The specied volume is used as a TrueCopy.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 536
raidcom delete ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 4103 The specied volume is used as a TrueCopy.
Get Command
Status
Async 2E30 4104 The specied volume is used as a
ShadowImage pair volume, a Thin Image pair
volume, or a FICON® Data Migration volume.
Get Command
Status
Async 2E30 4105 The specied volume is used as a
ShadowImage pair volume, a Thin Image pair
volume, or a FICON® Data Migration volume.
Get Command
Status
Async 2E30 4107 The specied volume is used as a
ShadowImage.
Get Command
Status
Async 2E30 4108 The specied LDEV is used as a reserved
volume of Volume Migration.
Get Command
Status
Async 2E31 0001 The target LDEV is a quorum disk and cannot
be deleted.
CMDRJE Executing 2EE8 00EE The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2EE8 00F0 The specied command cannot be accepted
because the command is not supported.
Get Command
Status
Async 2EE8 0A18 An internal error occurred.
CMDRJE
Get Command
Status
Executing/
Async
2EE8 FEEC An internal error occurred. Call customer
support.
Get Command
Status
Async 2EE8 FFFB An internal error occurred.
Call customer support.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom delete ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 537
SSB codes returned by raidcom delete hba_wwn
raidcom delete hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 4087 The host group ID exceeds the maximum value.
CMDRJE Executing B957 4089 The specied host group is not installed.
CMDRJE Executing B957 408A The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 408F The specied command is not supported for
the iSCSI port.
Executing B980 B901 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
Platfor
m
(Syste
m LU).
SSB codes returned by raidcom delete hba_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 538
raidcom delete hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B902 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
Platfor
m
(User
LU).
SSB codes returned by raidcom add hba_wwn
raidcom add hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 4081 The value of hba_wwn is invalid.
CMDRJE Executing B957 4087 The value of host group ID exceeds the
maximum.
CMDRJE Executing B957 4089 The host group is not installed.
CMDRJE Executing B957 408A The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 408F The specied command is not supported for
the iSCSI port.
CMDRJE Executing B957 4184 The number of WWN reached the maximum.
CMDRJE Executing B957 4188 HBA WWN is already registered.
SSB codes returned by raidcom add hba_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 539
raidcom add hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B901 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
Platfor
m
(Syste
m LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom set hba_wwn
raidcom set hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 4087 The value of host group ID exceeds the
maximum.
CMDRJE Executing B957 4089 The host group is not installed.
CMDRJE Executing B957 408A The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 4385 The specied WWN does not exist.
CMDRJE Executing B957 438B The specied WWN nickname is already used in
the same port.
SSB codes returned by raidcom set hba_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 540
raidcom set hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom reset hba_wwn
raidcom reset hba_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 4087 The value of Host group ID exceeds the
maximum.
CMDRJE Executing B957 4089 The host group is not installed.
CMDRJE Executing B957 408A The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 4385 The specied WWN does not exist.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom add copy_grp
raidcom add copy_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 000B The number of MU# exceeds the maximum.
CMDRJE Executing 2E00 2100 Invalid device number.
SSB codes returned by raidcom reset hba_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 541
raidcom add copy_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 5000 The specied journal ID exceeds the range.
CMDRJE Executing 2E20 2100 A device group is not installed.
CMDRJE Executing 2E22 2000 There is a copy group.
CMDRJE Executing 2E23 2000 The number of copy groups in the system
reached the maximum.
CMDRJE Executing 2E30 2100 The specied device group is already dened in
the other copy group.
CMDRJE Executing 2E31 0012 There is an LDEV in the device group that has
an undened device name.
CMDRJE Executing 2E31 0013 The same device names of LDEV are in the
device group.
CMDRJE Executing 2E31 0014 The same LDEVs are in the copy group.
Invalid Character Executing - - Unavailable character is included in the name
of copy group.
SSB codes returned by raidcom delete copy_grp
raidcom delete copy_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 2000 The copy group is not installed.
Invalid Character Executing - - Unavailable character is included in the name
of copy group.
SSB codes returned by raidcom delete copy_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 542
SSB codes returned by raidcom modify port -port_speed
raidcom modify port -port_speed
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 0404 An LU path or a logical path has been dened.
CMDRJE Executing B955 040F An internal error occurred.
CMDRJE Executing B955 044C The specied AL-PA is invalid.
CMDRJE Executing B955 054E The specied topology is invalid.
CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specied
when specifying a topology of the package for
Fibre Channel over Ethernet.
CMDRJE Executing B955 05A7 The other than "P-to-P (point to point)" cannot
be specied when specifying a topology of the
package for Fibre Channel over Ethernet.
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 104F The program product is not installed.
CMDRJE Executing B955 113D Invalid host speed is set for 4Gbps bre
adapter. The available host speeds are AUTO,
1G, 2G, and 4G only.
CMDRJE Executing B955 113E Invalid host speed is set for the specied bre
adapter.
CMDRJE Executing B955 113F Invalid host speed is set for 8Gbps bre
adapter. The available host speeds are AUTO,
2G, 4G, and 8G only.
CMDRJE Executing B955 11A5 The other than "10G" cannot be specied when
specifying a host speed of the package for Fibre
Channel over Ethernet.
CMDRJE Executing B955 11AE Invalid host speed is set for 16Gbps bre
adapter. The available host speeds are AUTO,
2G, 4G, and 8G only.
SSB codes returned by raidcom modify port -port_speed
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 543
raidcom modify port -port_speed
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 12AF The combination of the specied host speed
and the topology FC-AL set for the bre channel
adapter is not supported. See the Provisioning
Guide of your system for supported
combinations of data transfer speed and type
of connection.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom modify port -port_attribute
raidcom modify port -port_attribute
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E00 8404 The target channel adapter or the channel
board does not support the specied port
attribute.
CMDRJE Executing 2E10 8001 The operation cannot be performed because
another application, for example Storage
Navigator, Device Manager - Storage Navigator,
and SVP is used.
CMDRJE Executing 2E10 8400 The specied port is blocked.
CMDRJE Executing 2E10 8402 There is a pair for TrueCopy/Universal
Replicator that is using the specied port.
CMDRJE Executing 2E10 8403 There is a pair for TrueCopy/Universal
Replicator that is using the specied port.
CMDRJE Executing 2E11 800D The storage system is in the state of start-up.
Wait for a while, then retry the operation.
CMDRJE Executing 2E13 8401 The port attribute cannot be changed because
it is used for the iSCSI path of the remote
replication.
SSB codes returned by raidcom modify port -port_attribute
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 544
raidcom modify port -port_attribute
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E13 8402 iSNS is set for the specied port.
CMDRJE Executing 2E20 8400 The specied port is not installed.
CMDRJE Executing 2E30 8403 There is a path for TrueCopy/Universal
Replicator in the specied port.
CMDRJE Executing 2E30 8406 There is an external VOL path in the specied
port.
CMDRJE Executing 2E30 8407 There is a path for TrueCopy/Universal
Replicator in the specied port.
CMDRJE Executing 2E30 8408 There is a path for TrueCopy/Universal
Replicator in the specied port.
CMDRJE Executing 2E30 8409 An LU path has been dened.
CMDRJE Executing 2ED0 84FC An internal error occurred.
Call customer support.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom modify port -delayed_ack_mode
raidcom modify port -delayed_ack_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -delayed_ack_mode
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 545
SSB codes returned by raidcom modify port -ipv4_address
raidcom modify port -ipv4_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B3 The network address, loop-back address,
broadcast address or the IP address beginning
with 255 cannot be used as the IP address for
IPv4.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv4_subnetmask
raidcom modify port -ipv4_subnetmask
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10DB The subnet mask cannot be set because the
specied value is invalid.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv4_gateway_address
raidcom modify port -ipv4_gateway_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
SSB codes returned by raidcom modify port -ipv4_address
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 546
raidcom modify port -ipv4_gateway_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_gateway_address
raidcom modify port -ipv6_gateway_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B9 The multicast address or the loop-back address
cannot be set as the default gateway for IPv6.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_global_address
raidcom modify port -ipv6_global_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B8 The multicast address or the loop-back address
cannot be set as global address 1 for IPv6.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_gateway_address
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 547
SSB codes returned by raidcom modify port -ipv6_global_address2
raidcom modify port -ipv6_global_address2
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 10FD If global address 1 for IPv6 is not set, you
cannot set global address 2 for IPv6 manually.
CMDRJE Executing B955 10FE The multicast address or the loop-back address
cannot be set as global address 2 for IPv6.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_local_address
raidcom modify port -ipv6_local_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B6 The invalid value is specied for the link local
address of IPv6.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_global_address2
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 548
SSB codes returned by raidcom modify port -ipv6_mode
raidcom modify port -ipv6_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10C8 To disable IPv6, delete the remote path for
avoiding the failure of remote copy.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -isns_mode
raidcom modify port -isns_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10FC The attribute of the specied port is Initiator or
External.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -isns_port
raidcom modify port -isns_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -ipv6_mode
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 549
SSB codes returned by raidcom modify port -isns_server_address
raidcom modify port -isns_server_address
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10C5 The specied IP address of the iSNS server is
incorrect by the following reasons:
■The loop-back address, broadcast address
or the IP address beginning with 255 has
been set as the IPv4 address.
■The multicast address or the loop-back
address has been set as the IPv6 address, or
the address has not been specied yet.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -keep_alive_timer
raidcom modify port -keep_alive_timer
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10BE The invalid value is specied for the Keep Alive
timer.
CMDRJE Executing B955 10FB The attribute of the specied port is Initiator or
External.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -isns_server_address
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 550
SSB codes returned by raidcom modify port -mtu
raidcom modify port -mtu
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B0 The invalid value is specied for the Ethernet
MTU size.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -selective_ack_mode
raidcom modify port -selective_ack_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -tcp_port
raidcom modify port -tcp_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -mtu
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 551
SSB codes returned by raidcom modify port -add_vlan_id
raidcom modify port -add_vlan_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B2 The invalid value is specied for the VLAN ID.
CMDRJE Executing B955 10CB The number of VLANs exceeds the maximum.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -delete_vlan_id
raidcom modify port -delete_vlan_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B2 The invalid value is specied for the VLAN ID.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -modify_vlan_id
raidcom modify port -modify_vlan_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B2 The invalid value is specied for the VLAN ID.
CMDRJE Executing B955 10CD The command cannot be executed because the
specied VLAN ID is already used.
SSB codes returned by raidcom modify port -add_vlan_id
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 552
raidcom modify port -modify_vlan_id
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -vlan_tagging_mode
raidcom modify port -vlan_tagging_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10BF The VLAN tagging mode cannot be set because
the VLAN ID has not been entered yet.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -window_size
raidcom modify port -window_size
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 120E The command cannot be executed because the
iSCSI virtual port mode is ON.
SSB codes returned by raidcom modify port -vlan_tagging_mode
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 553
SSB codes returned by raidcom modify port -t10pi (VSP Gx00 models, VSP Fx00
models)
raidcom modify port -t10pi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing
Async
2E00 8400 The value of the specied port is invalid.
CMDRJE
Get Command
Status
Executing
Async
2E00 8404 The channel board of the object is not
supported.
Get Command
Status
Async 2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE
Get Command
Status
Executing
Async
2E10 8400 The specied port is blocked.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing
Async
2E20 8400 The specied port is not installed.
Get Command
Status
Executing
Async
2E30 840F LU path of the specied port or LU path of the
port in the same group is dened, the T10 PI
attribute of the port cannot be changed.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE
Get Command
Status
Executing
Async
2ED0 FEEC An internal error occurred.
SSB codes returned by raidcom modify port -t10pi (VSP Gx00 models, VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 554
SSB codes returned by raidcom modify port -add_iscsi_virtual_port
raidcom modify port -add_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B0 The invalid value is specied for the Ethernet
MTU size.
CMDRJE Executing B955 10B2 The invalid value is specied for the VLAN ID.
CMDRJE Executing B955 10B3 This command cannot be set due to one of the
following reasons:
■The network address, loop-back address,
broadcast address, or the IP address
beginning with 255 is set as the IPv4
address.
■No option is set when a virtual port in IPv4
mode was added. See the Command Control
Interface Command Reference.
CMDRJE Executing B955 10B8 The multicast address or the loop-back address
cannot be set as global address 1 for IPv6.
CMDRJE Executing B955 10B9 The multicast address or the loop-back address
cannot be set as the default gateway for IPv6.
CMDRJE Executing B955 10BE The invalid value is specied for the Keep Alive
timer.
CMDRJE Executing B955 10BF The VLAN tagging mode cannot be set because
the VLAN ID has not been entered yet.
CMDRJE Executing B955 10C8 To disable IPv6, delete the remote path for
avoiding the failure of remote copy.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 10CB The number of VLANs exceeds the maximum.
CMDRJE Executing B955 10CD The command cannot be executed because the
specied VLAN ID is already used.
SSB codes returned by raidcom modify port -add_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 555
raidcom modify port -add_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 10DB This command cannot be set due to one of the
following reasons:
■The specied value is invalid.
■No option is set when a virtual port in IPv4
mode was added. See the Command Control
Interface Command Reference.
CMDRJE Executing B955 10FB The attribute of the specied port is Initiator or
External.
CMDRJE Executing B955 1201 The command cannot be executed because the
invalid virtual port number has been entered.
CMDRJE Executing B955 1202 The command cannot be executed because the
iSCSI virtual port mode is OFF.
CMDRJE Executing B955 1203 The same IPv6 address cannot be set to the
same virtual port redundantly.
CMDRJE Executing B955 1204 The IPv6 global address 2 cannot be set for the
ports other than virtual port 0.
CMDRJE Executing B955 1205 The command cannot be executed because the
RCU port or the iSCSI name of the iSCSI target
for the external storage system is registered for
the specied virtual port.
CMDRJE Executing B955 120A An internal error occurred.
CMDRJE Executing B955 120B The specied port is not a port of the package
for iSCSI.
CMDRJE Executing B955 120C The specied virtual port does not exist.
CMDRJE Executing B955 120D The storage system is in the internal
processing, or the conguration change
processes are conicting.
CMDRJE Executing B955 120F The command cannot be executed because the
information of the virtual port is already set for
the specied port.
CMDRJE Executing B955 1210 The command cannot be executed because
both IPv4 mode and IPv6 mode are disabled.
SSB codes returned by raidcom modify port -add_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 556
raidcom modify port -add_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1211 The command cannot be executed for ports
that are not registered as targets.
CMDRJE Executing B955 1212 iSNS cannot be set for virtual ports.
CMDRJE Executing B955 1214 The command cannot be set because the same
VLAN IDs are conicting in the physical port.
CMDRJE Executing B955 1215 The command cannot be executed because the
virtual ports with the same VLAN IDs and the
same IPv4 addresses are conicting in the
physical port.
SSB codes returned by raidcom modify port -modify_iscsi_virtual_port
raidcom modify port -modify_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 10B0 The invalid value is specied for the Ethernet
MTU size.
CMDRJE Executing B955 10B2 The invalid value is specied for the VLAN ID.
CMDRJE Executing B955 10B3 This command cannot be set due to one of the
following reasons:
■The network address, loop-back address,
broadcast address, or the IP address
beginning with 255 is set as the IPv4
address.
■No option is set when the port is changed to
IPv4 mode. See the Command Control
Interface Command Reference.
CMDRJE Executing B955 10B8 The multicast address or the loop-back address
cannot be set as global address 1 for IPv6.
SSB codes returned by raidcom modify port -modify_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 557
raidcom modify port -modify_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 10B9 The multicast address or the loop-back address
cannot be set as the default gateway for IPv6.
CMDRJE Executing B955 10BE The invalid value is specied for the Keep Alive
timer.
CMDRJE Executing B955 10BF The VLAN tagging mode cannot be set because
the VLAN ID has not been entered yet.
CMDRJE Executing B955 10C8 To disable IPv6, delete the remote path for
avoiding the failure of remote copy.
CMDRJE Executing B955 10C9 The same IPv6 address cannot be set to the
same port redundantly.
CMDRJE Executing B955 10CB The number of VLANs exceeds the maximum.
CMDRJE Executing B955 10DB This command cannot be set due to one of the
following reasons:
■The specied value is invalid.
■No option is set when the port is changed to
IPv4 mode. See the Command Control
Interface Command Reference.
CMDRJE Executing B955 10FB The attribute of the specied port is Initiator or
External.
CMDRJE Executing B955 10FD If global address 1 for IPv6 is not set, you
cannot set global address 2 for IPv6 manually.
CMDRJE Executing B955 10FE The multicast address or the loop-back address
cannot be set as global address 2 for IPv6.
CMDRJE Executing B955 1201 The command cannot be executed because the
invalid virtual port number has been entered.
CMDRJE Executing B955 1202 The command cannot be executed because the
iSCSI virtual port mode is OFF.
CMDRJE Executing B955 1203 The same IPv6 address cannot be set to the
same virtual port redundantly.
CMDRJE Executing B955 1204 The IPv6 global address 2 cannot be set for the
ports other than virtual port 0.
SSB codes returned by raidcom modify port -modify_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 558
raidcom modify port -modify_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1205 The command cannot be executed because the
RCU port or the iSCSI name of the iSCSI target
for the external storage system is registered for
the specied virtual port.
CMDRJE Executing B955 1206 The command cannot be executed for virtual
port 0.
CMDRJE Executing B955 120A An internal error occurred.
CMDRJE Executing B955 120B The specied port is not a port of the package
for iSCSI.
CMDRJE Executing B955 120C The specied virtual port does not exist.
CMDRJE Executing B955 120D The storage system is in the internal
processing, or the conguration change
processes are conicting.
CMDRJE Executing B955 1210 The command cannot be executed because
both IPv4 mode and IPv6 mode are disabled.
CMDRJE Executing B955 1211 The command cannot be executed for ports
that are not registered as targets.
CMDRJE Executing B955 1212 iSNS cannot be set for virtual ports.
CMDRJE Executing B955 1213 The command cannot be executed for the ports
other than virtual port 0.
CMDRJE Executing B955 1214 The command cannot be set because the same
VLAN IDs are conicting in the physical port.
CMDRJE Executing B955 1215 The command cannot be executed because the
virtual ports with the same VLAN IDs and the
same IPv4 addresses are conicting in the
physical port.
SSB codes returned by raidcom modify port -modify_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 559
SSB codes returned by raidcom modify port -delete_iscsi_virtual_port
raidcom modify port -delete_iscsi_virtual_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B955 1039 The command device being used at the local
CCI exists under the port.
CMDRJE Executing B955 1201 The command cannot be executed because the
invalid virtual port number has been entered.
CMDRJE Executing B955 1202 The command cannot be executed because the
iSCSI virtual port mode is OFF.
CMDRJE Executing B955 1206 The command cannot be executed for virtual
port 0.
CMDRJE Executing B955 120A An internal error occurred.
CMDRJE Executing B955 120B The specied port is not a port of the package
for iSCSI.
CMDRJE Executing B955 120C The specied virtual port does not exist.
CMDRJE Executing B955 120D The storage system is in the internal
processing, or the conguration change
processes are conicting.
SSB codes returned by raidcom modify port -iscsi_virtual_port_mode
raidcom modify port -iscsi_virtual_port_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 8400 The value of the specied port is invalid.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E11 8010 The storage system is in internal process, or the
conguration changing processes are
conicting.
CMDRJE Executing 2E11 810A Abnormal cache status.
SSB codes returned by raidcom modify port -delete_iscsi_virtual_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 560
raidcom modify port -iscsi_virtual_port_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 8403 The operation cannot be performed because
iSNS is set for the specied port or a port of the
same group.
CMDRJE Executing 2E11 8404 The operation cannot be performed because a
virtual port is registered for the specied port
or a port of the same group.
CMDRJE Executing 2E20 8400 The specied port is not installed.
CMDRJE Executing 2E31 8301 The specied port is not a port of the package
for iSCSI.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2ED0 FEEC An internal error occurred.
SSB codes returned by raidcom delete host_grp
raidcom delete host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B956 302C The host group cannot be deleted because the
host mode option 61 or 72 is set.
CMDRJE Executing B956 304F The program product is not installed.
CMDRJE Executing B956 3071 The value of host group ID exceeds the
maximum.
CMDRJE Executing B956 3077 The attribute of the specied port is Initiator or
External.
CMDRJE Executing B956 30FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B956 3203 Deletion cannot be executed because the last
path of ShadowImage is included in the host
group.
SSB codes returned by raidcom delete host_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 561
raidcom delete host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B956 320A Deletion cannot be executed because the last
path of Thin Image or Copy-on-Write Snapshot
is included in the host group.
CMDRJE Executing B956 3234 Deletion cannot be executed because the LU
which is the target of the operation is in the
reserved status.
CMDRJE Executing B956 3239 The command device being used at the local
CCI exists under the host group.
Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom add host_grp
raidcom add host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B956 304F The program product is not installed.
CMDRJE Executing B956 3071 The value of host group ID exceeds the
maximum.
CMDRJE Executing B956 3077 The attribute of the specied port is Initiator or
External.
CMDRJE Executing B956 30FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B956 3173 The same host group name is already installed
in the specied port.
CMDRJE Executing B956 3174 The default host group name cannot be
registered for the host group ID is other than 0.
CMDRJE Executing B956 31D0 The character or the number of characters of
the iSCSI target name is invalid.
SSB codes returned by raidcom add host_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 562
raidcom add host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B956 31D5 The character or the number of characters of
the iSCSI target alias is invalid.
CMDRJE Executing B956 31D7 The specied iSCSI target alias is already
assigned to the same port.
CMDRJE Executing B956 31D8 The specied iSCSI target alias cannot be
registered because the iSCSI target alias is
reserved for the iSCSI target ID 00.
CMDRJE Executing B956 31D9 The specied iSCSI target name is already used
for the same port.
CMDRJE Executing B956 31DA The specied iSCSI target name cannot be
registered because the iSCSI target name is
reserved for the iSCSI target ID 00.
CMDRJE Executing B956 3204 An LU path or a logical path has been dened.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom modify host_grp
raidcom modify host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B956 304F The program product is not installed.
CMDRJE Executing B956 30FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B956 3204 An LU path or a logical path has been dened.
CMDRJE Executing B958 032F You cannot cancel the host mode option
because the specied host group is associated
with the LDEV in another virtual storage
machine by the path denition.
CMDRJE Executing B958 0339 The command device being used at the local
CCI exists under the host group.
SSB codes returned by raidcom modify host_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 563
raidcom modify host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B958 0350 Changing of the host mode/ host mode option
cannot be executed for the port of Initiator or
External.
CMDRJE Executing B958 0354 The invalid host mode is specied.
CMDRJE Executing B958 092C The cancellation of the host mode option 61 or
72 was suppressed.
CMDRJE Executing B958 0956 The host group ID exceeds the maximum.
CMDRJE Executing B958 0957 The program product is not installed.
CMDRJE Executing B958 0959 The specied host group is not installed.
CMDRJE Executing B958 098E When using 8FC16 or 16FE10 channel package,
you cannot congure the host mode option 51
(Round Trip Set Up Option) for the host group
because the host mode option 51 is not
supported.
Executing B980 B901 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
Platfor
m
(Syste
m LU).
SSB codes returned by raidcom modify host_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 564
raidcom modify host_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B902 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
Platfor
m
(User
LU).
Executing B980 B903 The
comm
and
was
rejecte
d
becau
se the
selecte
d
resour
ce
belong
s to
NAS_Pl
atform
_Syste
m_RS
G.
SSB codes returned by raidcom modify host_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 565
SSB codes returned by raidcom disconnect path
raidcom disconnect path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4500 The path group is out of the enabled range.
CMDRJE Executing 2E00 8400 The value of the specied port is invalid.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
Get Command
Status
Async 2E10 4301 The specied external path has already
disconnected the path, or is in the process of
checking path.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
Get Command
Status
Async 2E11 001B The target LDEV is blocked.
Get Command
Status
Async 2E11 4000 The path for the specied external path is in
the state of disconnected.
Get Command
Status
Async 2E11 4302 This command cannot be operated due to one
of the following reasons:
■All the paths to the external volumes are
blocked.
■There will be no normal paths.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
CMDRJE
Executing/
Async
2E20 4100 There is no specied external volume.
Get Command
Status
CMDRJE
Executing/
Async
2E20 4300 There is no connection path to an external
volume.
CMDRJE Executing 2E20 4400 WWN is not registered.
SSB codes returned by raidcom disconnect path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 566
raidcom disconnect path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 4500 This command cannot be operated due to one
of the following reasons:
■There is no path group.
■external_wwn is not dened.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
Get Command
Status
Async 2E30 001E Online from the mainframe host.
CMDRJE Executing 2E30 8400 The attribute of a port is not External(ELUN).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
CMDRJE Executing 2EDA 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EDA 0905 An internal error occurred by the operation of a
path for an external path.
Call customer support.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom delete path
raidcom delete path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 4500 The path group is not in a eective range.
CMDRJE Executing 2E00 8400 The value of the specied port is incorrect.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
SSB codes returned by raidcom delete path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 567
raidcom delete path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 4303 The path operations cannot be performed for
the following reasons:
■The target of the specied path group is
TagmaStore USP/TagmaStore NSC.
■The specied path group contains an
external volume for which the reserve
attribute is set by the host.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
Get Command
Status
Async 2E11 8011 The operation cannot continue because the
microcode is being replaced.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E20 4300 There is no external connection path.
CMDRJE Executing 2E20 4400 WWN is not registered.
CMDRJE
Get Command
Status
Executing/
Async
2E20 4500 There is no path group.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE
Get Command
Status
Executing/
Async
2E23 4300 Paths cannot be deleted because there are no
normal paths.
CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN).
CMDRJE Executing 2E30 840E The command cannot be executed with the
specied port attribute.
CMDRJE Executing 2EDA 00EE The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2EDA FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom delete path
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 568
raidcom delete path
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2EDA FFFF An internal error occurred.
Call customer support.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom -logout
raidcom -logout
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E01 2200 Failed to release the resource lock.
SSB codes returned by raidcom monitor pool
raidcom monitor pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
CMDRJE Executing 2E10 6004 Monitor cannot be started because the
performance monitor is in the collecting status.
CMDRJE Executing 2E10 6005 Monitor cannot be stopped because the
performance monitor is stopped.
CMDRJE Executing 2E10 6006 Monitor cannot start because the performance
monitor is in use. Retry the operation after
completing or stopping the reallocation of Tier.
CMDRJE Executing 2E10 6007 There is not enough time after collecting
performance monitor.
SSB codes returned by raidcom -logout
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 569
raidcom monitor pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 6003 The pool is not in the state of specifying the
performance monitor to start or stop.
CMDRJE Executing 2E20 6000 The pool ID is not installed.
CMDRJE Executing 2E21 8101 A shared memory for Dynamic Provisioning is
not installed.
CMDRJE Executing 2E21 8102 A shared memory for Dynamic Tiering or active
ash is not installed.
CMDRJE Executing 2E21 9000 The program product of Dynamic Tiering or
active ash is not installed.
CMDRJE Executing 2E30 6002 Start or stop of performance monitor by hand
cannot be performed because it is a pool for
Dynamic Provisioning or it is automatic
execution mode.
CMDRJE Executing 2E30 6003 The specied pool is the one for Thin Image or
Copy-on-Write Snapshot.
CMDRJE Executing 2EE7 FEEC An internal error occurred. Call customer
support.
SSB codes returned by raidcom reallocate pool
raidcom reallocate pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
CMDRJE Executing 2E10 6007 There is not enough time after collecting
performance monitor.
CMDRJE Executing 2E10 6008 Tier reallocation cannot be started because the
state of performance monitor information is
not enabled. Start the performance monitor
again.
CMDRJE Executing 2E10 6009 Reallocation cannot be started because it is
reallocating.
SSB codes returned by raidcom reallocate pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 570
raidcom reallocate pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 600A Reallocation cannot be stopped because it is
not reallocating.
CMDRJE Executing 2E10 6011 The operation cannot be performed because it
is being discarded pages.
CMDRJE Executing 2E10 6015 The operation cannot be performed because
the Tier is being deterred reallocation.
CMDRJE Executing 2E11 6003 The pool is not in the status of specifying the
reallocation to start or stop.
CMDRJE Executing 2E20 6000 The pool ID is not installed.
CMDRJE Executing 2E21 8101 A shared memory for Dynamic Provisioning is
not installed.
CMDRJE Executing 2E21 8102 A shared memory for Dynamic Tiering or active
ash is not installed.
CMDRJE Executing 2E21 9000 The program product of Dynamic Tiering or
active ash is not installed.
CMDRJE Executing 2E30 6002 Start or stop of performance monitor by hand
cannot be performed because it is a pool for
Dynamic Provisioning or it is automatic
execution mode.
CMDRJE Executing 2E30 6003 The specied pool is the one for Thin Image or
Copy-on-Write Snapshot.
CMDRJE Executing 2E31 6000 Reallocation cannot be performed because
there is only one Tier in the pool group.
CMDRJE Executing 2EE7 FEEC An internal error occurred. Call customer
support.
SSB codes returned by raidcom reallocate pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 571
SSB codes returned by raidcom extend ldev
raidcom extend ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing - - See the troubleshooting topics in the
Provisioning Guide for the storage system.
SSB codes returned by raidcom delete resource
raidcom delete resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 2201 The specied resource group cannot be
operated.
CMDRJE Executing 2E10 2201 The specied resource groups cannot be
deleted because the resource groups are
locked by another user (or another session).
Check the lock status of the resource groups. If
maintenance personnel is performing
maintenance operations, retry the command
after conrming the completion of the
operations..
CMDRJE Executing 2E10 2202 The LDEV and the host group cannot be set to
the dierent virtual storage machine.
CMDRJE Executing 2E20 0100 There is no parity group.
CMDRJE Executing 2E20 2200 A resource group cannot be deleted because
the specied resource group is undened.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E21 9305 The information for the virtual storage machine
is set in the specied resource.
CMDRJE Executing 2E22 2202 A resource group cannot be deleted because a
resource belongs to the specied resource
group.
SSB codes returned by raidcom extend ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 572
raidcom delete resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E22 2203 A resource cannot be deleted from the
resource group because the specied LDEV
number is not the top LDEV number in the
LUSE volume.
CMDRJE Executing 2E30 2201 The operation to resource group 0
(meta_resource) cannot be performed.
CMDRJE Executing 2ECA FEEC An internal error occurred.
Call customer support.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
CMDRJE Executing B980 B904 The command was rejected because the
selected resource group belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom add resource
raidcom add resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 2200 The specied resource group name is against
the naming rules.
CMDRJE Executing 2E00 2201 The specied resource group cannot be
operated.
CMDRJE Executing 2E00 2202 The resource ID and the sub-resource ID are
out of the eective range.
CMDRJE Executing 2E00 8000 The machine type is invalid.
CMDRJE Executing 2E00 8001 The serial number is invalid.
CMDRJE Executing 2E00 8400 The value of the specied port is invalid.
CMDRJE Executing 2E10 2202 The LDEV and the host group cannot be set to
the dierent virtual storage machine.
SSB codes returned by raidcom add resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 573
raidcom add resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 0100 There is no parity group.
CMDRJE Executing 2E20 2200 You cannot execute this command because of
either reason below.
■A resource cannot be added to the resource
group because the specied resource group
is undened.
■A resource group name cannot be changed
because the specied resource group is
undened.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE Executing 2E20 8400 The specied port is not installed.
CMDRJE Executing 2E21 900D The program products of Resource Partition
Manager are not installed.
CMDRJE Executing 2E21 9305 The information for the virtual storage machine
is set in the specied resource.
CMDRJE Executing 2E21 930B A virtual storage machine cannot be created
because the virtual storage machine with the
specied serial number already exists.
CMDRJE Executing 2E22 2200 You cannot execute this command because of
either reason below.
■A resource group cannot be created because
the specied resource group name is
duplicated.
■A resource group name cannot be changed
because the specied resource group name
is duplicated.
CMDRJE Executing 2E22 2201 A resource cannot be added to a resource
group because the specied resource belongs
to the resource group.
CMDRJE Executing 2E22 2203 A resource cannot be added to the resource
group because the specied LDEV number is
not the top LDEV number in the LUSE volume.
CMDRJE Executing 2E23 2200 Any more resource groups cannot be created
because the registered number of resource
groups has reached the maximum.
SSB codes returned by raidcom add resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 574
raidcom add resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E23 2201 A virtual storage machine cannot be created
because the number of registered virtual
storage machines has reached the maximum.
CMDRJE Executing 2E30 2201 The operation to resource group 0
(meta_resource) cannot be performed.
CMDRJE Executing 2E30 8402 The attribute of the specied port is Initiator or
External.
CMDRJE Executing 2ECA FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
CMDRJE Executing B980 B903 The command was rejected because the
selected resource belongs to
NAS_Platform_System_RSG.
CMDRJE Executing B980 B904 The command was rejected because the
selected resource group belongs to
NAS_Platform_System_RSG.
SSB codes returned by raidcom get resource
raidcom get resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF0 FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom get resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 575
SSB codes returned by raidcom map resource
raidcom map resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The specied LDEV number or the LDEV
number for the virtual volume is out of the
range.
CMDRJE Executing 2E00 0003 SSID is not with in the valid range.
CMDRJE Executing 2E00 000E The specied emulation type of the LDEV is not
supported in this command.
CMDRJE Executing 2E00 002B The specied attribute of the virtual LDEV is not
supported.
CMDRJE Executing 2E00 002C The specied attribute of the virtual LDEV is
invalid.
CMDRJE Executing 2E00 2205 You cannot execute the command because a
parameter required for the virtualization was
not specied.
CMDRJE Executing 2E00 9301 The specied emulation type is invalid.
CMDRJE Executing 2E10 0055 The specied LDEV cannot be operated
because it belongs to the default virtual storage
machine.
CMDRJE Executing 2E10 0059 The specied volume cannot be operated
because the LDEV number of the specied
volume does not match the LDEV number of
the virtual volume.
CMDRJE Executing 2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE Executing 2E21 9305 The information of the virtual storage machine
is already set in the specied resource.
CMDRJE Executing 2E21 9307 The specied virtual LDEV number is already
exist in the virtual storage machine to which the
specied LDEV belongs.
SSB codes returned by raidcom map resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 576
raidcom map resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E21 9308 You cannot operate the LDEV that has the LU
path denition.
CMDRJE Executing 2E22 0001 The specied LDEV is already dened.
CMDRJE Executing 2E30 0013 The specied volume cannot be set because it
is a LUSE volume.
CMDRJE Executing 2E30 0088 The specied LDEV cannot be operated
because it has an attribute.
CMDRJE Executing 2E30 0089 The specied LDEV cannot be operated
because the ldev has a reserve attribute for
GAD.
CMDRJE Executing 2E30 008A The specied LDEV is used for aGAD pair.
CMDRJE Executing 2E30 008C The specied LDEV cannot be set the
information of the virtual volume because it is
not virtualized.
CMDRJE Executing 2ECA FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom unmap resource
raidcom unmap resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0000 The specied LDEV number or the LDEV
number for the virtual volume is out of the
range.
CMDRJE Executing 2E10 004F The specied LDEV for the virtual storage
machine is not dened in the specied LDEV.
CMDRJE Executing 2E10 005E The specied LDEV is used by the TrueCopy pair
or the Universal Replicator pair.
SSB codes returned by raidcom unmap resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 577
raidcom unmap resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE Executing 2E21 9012 The Resource Partition Manager is not installed.
CMDRJE Executing 2E21 9306 The information of the virtual storage machine
is not set in the specied resource.
CMDRJE Executing 2E21 9308 You cannot operate the LDEV that has the LU
path denition.
CMDRJE Executing 2E30 000C The specied LDEV is used as a quorum disk.
CMDRJE Executing 2E30 000F The specied LDEV is used as a journal volume.
CMDRJE Executing 2E30 008A The specied LDEV is used for aGAD pair.
CMDRJE Executing 2E30 008B The specied LDEV cannot be operated
because it is the external volume for the online
data migration.
CMDRJE Executing 2E30 008D The specied volume cannot be operated
because it is the mainframe volume.
CMDRJE Executing 2E30 0096 The specied LDEV is used as an ALU.
CMDRJE Executing 2E30 0097 The specied LDEV is used as an SLU.
CMDRJE Executing 2ECA FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom unmap resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 578
SSB codes returned by raidcom modify resource
raidcom modify resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom set resource
raidcom set resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom reset resource
raidcom reset resource
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EF3 2202 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom modify clpr
raidcom modify clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 002A The specied LDEV is not subject to processing.
SSB codes returned by raidcom modify resource
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 579
raidcom modify clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0101 The parity group number or the external
volume group number is not in the eective
range.
CMDRJE Executing 2E00 0102 The specied group type is not correct.
CMDRJE Executing 2E00 0107 The combined parity group cannot be set
across multiple CLPRs.
CMDRJE Executing 2E00 1300 The item cannot be migrated to another CLPR
because of either reason below.
■The specied parity group or external
volume group has an LUSE volume.
■The specied volume is an LUSE volume.
CMDRJE Executing 2E00 7000 The specied CLPR ID is invalid.
CMDRJE Executing 2E11 810A Abnormal cache status.
CMDRJE Executing 2E13 0101 The CLPR cannot be migrated because the
specied parity group or the external volume
group includes the pool volume that is used in
the pool for Thin Image or Copy-on-Write
Snapshot.
CMDRJE Executing 2E20 0000 LDEV is not installed.
CMDRJE Executing 2E20 0100 There is no parity group.
CMDRJE Executing 2E20 4100 There is no external volume group.
CMDRJE
Get Command
Status
Executing/
Async
2E20 7001 The specied CLPR is not installed.
CMDRJE Executing 2E30 0005 CLPR cannot be transferred by either one of the
following two reasons.
■Cache Residency Manager is set for the
specied volume.
■The specied parity group includes the
volumes for which Cache Residency
Manager are set.
CMDRJE Executing 2E30 000F The specied LDEV is used as a journal volume.
SSB codes returned by raidcom modify clpr
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 580
raidcom modify clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 0083 The specied parity group includes HDEV with
the journal attribute.
CMDRJE Executing 2EE8 00F0 The specied command cannot be accepted
because the command is not supported.
CMDRJE Executing 2EE8 FEEC An internal error occurred.
Call customer support.
CMDRJE Executing 2EF3 0102 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
CMDRJE Executing 2EF3 9F02 The specied operation cannot be performed
because it is not supported.
CMDRJE Executing 2EF6 FEEC An internal error occurred.
Call customer support.
SSB codes returned by raidcom add spm_group
raidcom add spm_group
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
SSB codes returned by raidcom add spm_group
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 581
raidcom add spm_group
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D4 B9D6 The number of Server Priority Manager groups
exceeds the maximum.
SSB codes returned by raidcom delete spm_group
raidcom delete spm_group
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D2 The specied WWN or nickname does not exist.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
SSB codes returned by raidcom delete spm_group
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 582
SSB codes returned by raidcom modify spm_group
raidcom modify spm_group
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D3 The specied WWN or upper limit is invalid.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
SSB codes returned by raidcom modify spm_group
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 583
SSB codes returned by raidcom add spm_wwn
raidcom add spm_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D2 The specied WWN does not exist.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
CMDRJE Executing B9D4 B9D7 The specied SPM name has already existed.
SSB codes returned by raidcom delete spm_wwn
raidcom delete spm_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
SSB codes returned by raidcom add spm_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 584
raidcom delete spm_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D2 The conguration WWN or nickname does not
exist.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
SSB codes returned by raidcom modify spm_wwn
raidcom modify spm_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
SSB codes returned by raidcom modify spm_wwn
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 585
raidcom modify spm_wwn
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D4 B9D0 The command cannot be executed due to one
of the following reasons:
■Server Priority Manager is being used by
Storage Navigator or Device Manager -
Storage Navigator. Delete all settings of
Server Priority Manager using Storage
Navigator or Device Manager - Storage
Navigator.
■Server Priority Manager information for the
port WWN already exists in the system.
Delete Server Priority Manager information
from Performance Monitor.
CMDRJE Executing B9D4 B9D1 The number of WWNs exceeds the maximum
that can be set in the system.
CMDRJE Executing B9D4 B9D3 The specied WWN or upper limit is invalid.
CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not
installed.
CMDRJE Executing B9D4 B9D5 The number of WWNs exceeds the maximum
that can be set to the port.
SSB codes returned by raidcom modify spm_ldev
raidcom modify spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is incorrect.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E21 8301 The specied operation cannot be performed
because of no iSCSI package.
SSB codes returned by raidcom modify spm_ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 586
raidcom modify spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E22 9B04 The iSCSI name cannot be registered because
the number of iSCSI names that can be
registered in the system exceeded the
maximum number.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9D3 B9D0 The operation cannot be performed because
internal processing is in progress. Wait a while,
and then retry the command. If maintenance
personnel is performing maintenance
operations, retry the command after
conrming the completion of the maintenance
operations.
CMDRJE Executing B9D3 B9D1 The Server Priority Manager information for the
port WWN already exists in the system.
CMDRJE Executing B9D3 B9D2 The LDEV cannot be registered because the
number of LDEVs that can be registered in the
system exceeded the maximum number.
CMDRJE Executing B9D3 B9D3 The WWN cannot be registered because the
number of WWNs that can be registered in the
system exceeded the maximum number.
CMDRJE Executing B9D3 B9D4 The WWN cannot be registered because the
number of WWNs that can be registered in the
LDEV exceeded the maximum number.
CMDRJE Executing B9D3 B9D5 The specied LDEV is not dened.
CMDRJE Executing B9D3 B9D7 Server Priority Manager is being used by
Storage Navigator or Device Manager - Storage
Navigator.
CMDRJE Executing B9D3 B9D8 The iSCSI name cannot be registered because
an invalid WWN is registered. Invalid WWNs are
WWNs which are not in the WWN format
dened by IEEE. See Cautions about using
Server Priority Manager for details.
CMDRJE Executing B9D3 B9D9 The specied operation cannot be performed
because of no iSCSI package.
SSB codes returned by raidcom modify spm_ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 587
raidcom modify spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D7 B9D7 The specied WWN, iSCSI name, or upper limit
is incorrect.
CMDRJE Executing B9D8 B9D8 The specied LDEV does not have the WWN or
iSCSI name.
CMDRJE Executing B9D9 B9D9 The Server Priority Manager program product is
not installed.
SSB codes returned by raidcom delete spm_ldev
raidcom delete spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is incorrect.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9D3 B9D0 The operation cannot be performed because
internal processing is in progress. Wait a while,
and then retry the command. If maintenance
personnel is performing maintenance
operations, retry the command after
conrming the completion of the maintenance
operations.
CMDRJE Executing B9D3 B9D9 The specied operation cannot be performed
because of no iSCSI package.
CMDRJE Executing B9D7 B9D7 The specied WWN or iSCSI name is incorrect.
CMDRJE Executing B9D8 B9D8 The specied LDEV does not have the WWN or
iSCSI name.
SSB codes returned by raidcom delete spm_ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 588
SSB codes returned by raidcom monitor spm_ldev
raidcom monitor spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is incorrect.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9D3 B9D0 The operation cannot be performed because
internal processing is in progress. Wait a while,
and then retry the command. If maintenance
personnel is performing maintenance
operations, retry the command after
conrming the completion of the maintenance
operations.
CMDRJE Executing B9D7 B9D7 The specied WWN or iSCSI name is incorrect.
SSB codes returned by raidcom get spm_ldev
raidcom get spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is incorrect.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing B9D3 B9D0 The operation cannot be performed because
internal processing is in progress. Wait a while,
and then retry the command. If maintenance
personnel is performing maintenance
operations, retry the command after
conrming the completion of the maintenance
operations.
SSB codes returned by raidcom monitor spm_ldev
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 589
raidcom get spm_ldev
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B9D7 B9D7 The specied WWN or iSCSI name is incorrect.
SSB codes returned by raidcom modify ldev -capacity_saving/-
capacity_saving_mode
raidcom modify ldev -capacity_saving/-capacity_saving_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of the valid range.
Get Command
Status
Async 2E00 0013 The operation cannot be performed because
there are not enough cache management
devices.
Get Command
Status
Async 2E10 002D The operation cannot be performed because
the specied LDEV is a journal volume.
Get Command
Status
Async 2E10 0207 The specied LDEV cannot be operated
because it is a Universal Replicator P-VOL and
is being copied.
Get Command
Status
Async 2E10 0208 The specied LDEV cannot be operated
because its pages are being released.
Get Command
Status
Async 2E10 020B The specied LDEV cannot be operated
because the deduplication function is enabled.
Get Command
Status
Async 2E10 020C The specied LDEV cannot be operated
because deduplicated data exists.
Get Command
Status
Async 2E10 020D The specied LDEV cannot be operated
because it is in the status where the capacity
saving setting cannot be disabled.
Get Command
Status
Async 2E10 020E The specied LDEV is not in the status where
the capacity saving setting can be enabled.
Get Command
Status
Async 2E10 020F The specied LDEV is not in the status where
the capacity saving setting can be changed.
SSB codes returned by raidcom modify ldev -capacity_saving/-capacity_saving_mode
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 590
raidcom modify ldev -capacity_saving/-capacity_saving_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 0214 The operation cannot be performed because
the specied volume is being used by Volume
Migration.
Get Command
Status
Async 2E10 0215 The operation cannot be performed because
the specied volume is being used by Quick
Restore of ShadowImage.
Get Command
Status
Async 2E10 0219 The tiering policy is enabled for the specied
LDEV.
Get Command
Status
Async 2E10 6020 The deduplication function cannot be used in
the pool linked with the specied LDEV.
Get Command
Status
Async 2E10 6022 The operation cannot be performed because
the deduplication system data volume of the
pool linked with the specied LDEV is blocked.
Get Command
Status
Async 2E10 6026 The specied virtual volume cannot be
operated because the used capacity of the
pool associated with the specied virtual
volume exceeds the depletion threshold.
Get Command
Status
Async 2E11 001B The specied LDEV is blocked.
Get Command
Status
Async 2E11 0209 The operation cannot be performed due to a
cache memory failure or maintenance work
being performed.
Get Command
Status
Async 2E11 6008 The operation cannot be performed because
the pool linked with the specied LDEV is in
unusable status.
CMDRJE Executing 2E11 9400 The command cannot be accepted. Wait a
while, and issue the same command.
CMDRJE
Get Command
Status
Executing/
Async
2E20 0000 The specied LDEV is not installed.
Get Command
Status
Async 2E21 8103 The operation cannot be performed because
the capacity of shared memory is insucient.
Get Command
Status
Async 2E21 810A The shared memory is not installed.
SSB codes returned by raidcom modify ldev -capacity_saving/-capacity_saving_mode
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 591
raidcom modify ldev -capacity_saving/-capacity_saving_mode
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E21 9000 The program product is not installed.
Get Command
Status
Async 2E30 0086 The operation cannot be performed because
the specied volume is not a DP-VOL.
Get Command
Status
Async 2E30 0099 The specied LDEV is set that the Data Direct
Mapping attribute is enabled.
Get Command
Status
Async 2E30 009B The operation cannot be performed because
the page reservation is set for the specied
LDEV.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the specied LDEV is a deduplication system
data volume.
Get Command
Status
Async 2E30 6014 The operation cannot be performed because
the pool linked with the specied LDEV is for
active ash.
Get Command
Status
Async 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EBE 9E01 The specied parameter is incorrect.
CMDRJE
Get Command
Status
Executing/
Async
2EE8 FEEC An internal error occurred. Contact customer
support.
SSB codes returned by raidcom replace quorum
raidcom replace quorum
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0000 The LDEV number is out of settable range.
CMDRJE Executing 2E00 A001 The quorum disk ID is out of settable range.
CMDRJE Executing 2E10 0005 The specied LDEV is used for Volume
Migration.
SSB codes returned by raidcom replace quorum
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 592
raidcom replace quorum
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 0057 The specied LDEV cannot be congured
because the LDEV is a virtual volume.
CMDRJE Executing 2E10 0201 The operation failed because the T10 PI
attribute of the specied LDEV is enabled.
CMDRJE Executing 2E10 0202 The specied volume belongs to the resource
group of NAS_Platform_System_RSG.
CMDRJE Executing 2E10 A003 The specied quorum disk is in processing.
CMDRJE Executing 2E10 A006 The specied LDEV is used as the quorum disk.
CMDRJE Executing 2E10 A008 The operation cannot be performed because
the LDEV set for the quorum disk is not
blocked.
CMDRJE Executing 2E11 001B The specied LDEV is blocked.
CMDRJE Executing 2E11 800F The operation failed because multiple versions
of DKCMAIN microcode are included.
CMDRJE Executing 2E13 0001 The specied LDEV is not the rst LDEV that
belongs to the external volume group.
CMDRJE Executing 2E20 000E The specied LDEV is not an external volume.
CMDRJE Executing 2E20 A001 The specied quorum disk is not dened.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E30 0005 Cache Residency Manager is set to the specied
volume.
CMDRJE Executing 2E30 0007 A path is dened to the specied volume.
CMDRJE Executing 2E30 000E The specied LDEV is used as a pool volume.
CMDRJE Executing 2E30 000F The specied LDEV is used as a journal volume.
CMDRJE Executing 2E30 0010 The specied volume is used as a command
device.
CMDRJE Executing 2E30 004E Data Retention Utility is set to the specied
volume.
CMDRJE Executing 2E30 0074 The specied LDEV cannot be operated
because it is an external volume mapped for
online data migration.
SSB codes returned by raidcom replace quorum
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 593
raidcom replace quorum
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E30 008E The emulation type of the specied LDEV is not
OPEN-V.
CMDRJE Executing 2E30 0092 The specied LDEV cannot be used because the
size of the LDEV is less than the minimum
capacity of the quorum disk.
CMDRJE Executing 2E30 0099 The specied LDEV is a volume of which Data
Direct Mapping attribute is enabled.
CMDRJE Executing 2EB9 FEEC An internal error occurred. Contact customer
support.
SSB codes returned by raidcom modify quorum
raidcom modify quorum
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 A001 The specied quorum disk ID is out of the valid
range.
CMDRJE Executing 2E00 A002 The specied value for Read Response
Guaranteed Time When Quorum Disk Blocked
is not in the valid range.
CMDRJE Executing 2E20 A001 The specied quorum disk is not dened.
CMDRJE Executing 2EE8 FEEC An internal error occurred.
CMDRJE Executing 2EF3 9F02 The specied operation cannot be performed
because it is not supported.
SSB codes returned by raidcom modify quorum
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 594
SSB codes returned by raidcom add hba_iscsi
raidcom add hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 44E0 The invalid character or the invalid number of
characters is specied for the initiator iSCSI
name.
CMDRJE Executing B957 44E4 The specied iSCSI target is not registered.
CMDRJE Executing B957 44E7 The iSCSI name cannot be added because the
number of iSCSI names that can be used for
this port has already reached the maximum
value.
Executing B980 B901 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
platfor
m
(Syste
m LU).
SSB codes returned by raidcom add hba_iscsi
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 595
raidcom add hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B902 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
platfor
m
(User
LU).
SSB codes returned by raidcom delete hba_iscsi
raidcom delete hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 44E0 The invalid character or the invalid number of
characters is specied for the initiator iSCSI
name.
CMDRJE Executing B957 44E4 The specied iSCSI target is not registered.
SSB codes returned by raidcom delete hba_iscsi
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 596
raidcom delete hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Executing B980 B901 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
platfor
m
(Syste
m LU).
Executing B980 B902 The
comm
and
was
rejecte
d
becau
se the
speci
ed
port is
for
NAS
platfor
m
(User
LU).
SSB codes returned by raidcom delete hba_iscsi
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 597
SSB codes returned by raidcom set hba_iscsi
raidcom set hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 45E0 The character or the number of characters that
cannot be specied for the initiator iSCSI name
is specied.
CMDRJE Executing B957 45E2 The character or the number of characters that
cannot be specied for the initiator iSCSI
nickname is specied.
CMDRJE Executing B957 45E3 The specied iSCSI name is not registered.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom reset hba_iscsi
raidcom reset hba_iscsi
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom set hba_iscsi
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 598
SSB codes returned by raidcom add chap_user
raidcom add chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 46E4 The specied iSCSI target is not registered.
CMDRJE Executing B957 46E8 The character used for the user ID, or the
number of characters is invalid.
CMDRJE Executing B957 46EB The specied CHAP user name is already used
for the same port.
CMDRJE Executing B957 46EF The CHAP user ID cannot be added because the
number of CHAP user IDs that can be set for
this port has already reached the maximum
value.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom delete chap_user
raidcom delete chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
SSB codes returned by raidcom add chap_user
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 599
raidcom delete chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 46E4 The specied iSCSI target is not registered.
CMDRJE Executing B957 46E8 The character used for the user ID, or the
number of characters is invalid.
CMDRJE Executing B957 46EC The specied CHAP user name is not
registered.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom set chap_user
raidcom set chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 47E4 The specied iSCSI target is not registered.
CMDRJE Executing B957 47E8 The character used for the user ID, or the
number of characters is invalid.
CMDRJE Executing B957 47EA The specied password for CHAP
authentication is incorrect.
CMDRJE Executing B957 47EC The specied CHAP user name is not
registered.
CMDRJE Executing B957 47EE The iSCSI target cannot be set because the user
authentication of the iSCSI target is invalid.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
SSB codes returned by raidcom set chap_user
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 600
raidcom set chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom reset chap_user
raidcom reset chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing B957 404F The program product is not installed.
CMDRJE Executing B957 408F The specied command is not supported for
the FC port.
CMDRJE Executing B957 40FD The attribute of the specied port is Initiator or
External.
CMDRJE Executing B957 47E4 The specied iSCSI target is not registered.
CMDRJE Executing B957 47E8 The character used for the user ID, or the
number of characters is invalid.
CMDRJE Executing B957 47EC The specied CHAP user name is not
registered.
CMDRJE Executing B957 47EE The iSCSI target cannot be set because the user
authentication of the iSCSI target is invalid.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS platform (User LU).
SSB codes returned by raidcom reset chap_user
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 601
SSB codes returned by raidcom send ping
raidcom send ping
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 8400 The value of the specied port is invalid.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E10 8400 The specied port is blocked.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E10 8405 The IP version of the specied IP address is not
enabled.
CMDRJE Executing 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE Executing 2E20 8400 The specied port is not installed.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
SSB codes returned by raidcom add rcu_iscsi_port
raidcom add rcu_iscsi_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 3005 The product ID is invalid.
CMDRJE Executing 2E02 9C01 The specied IP address is invalid.
CMDRJE Executing 2E20 3000 The serial number or product ID of the target
storage system is incorrect.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E22 3202 The specied RCU port is already registered.
SSB codes returned by raidcom send ping
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 602
raidcom add rcu_iscsi_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E22 9B02 The total number of registered iSCSI targets
and RCU ports in the storage system reached
the maximum.
CMDRJE Executing 2E22 9B03 The total number of registered iSCSI targets
and RCU ports per port reached the maximum.
CMDRJE Executing 2E30 840A The port attribute is not Initiator (MCU).
CMDRJE Executing 2E31 8301 The specied port is not a port of the package
for iSCSI.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom delete rcu_iscsi_port
raidcom delete rcu_iscsi_port
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E20 3000 The serial number, product ID, or SSID of the
target storage system is incorrect.
CMDRJE Executing 2E20 3201 The specied RCU port is not registered.
CMDRJE Executing 2E21 3201 Deletion cannot be executed because the RCU
path is dened.
CMDRJE Executing B980 B901 The command was rejected because the
specied port is for NAS Platform (System LU).
CMDRJE Executing B980 B902 The command was rejected because the
specied port is for NAS Platform (User LU).
SSB codes returned by raidcom delete rcu_iscsi_port
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 603
SSB codes returned by raidcom add external_iscsi_name
raidcom add external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B01 The specied iSCSI name is invalid.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E02 9C01 The specied IP address is invalid.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E22 8401 The specied target information is registered
for another virtual port under the specied
physical port.
CMDRJE Executing 2E22 9B01 The specied iSCSI target is already registered.
CMDRJE Executing 2E22 9B02 The total number of registered iSCSI target and
RCU port in the storage system reached the
maximum.
CMDRJE Executing 2E22 9B03 The total number of registered iSCSI targets
and RCU ports per port reached the maximum.
CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN).
CMDRJE Executing 2E31 8301 The specied port is not a port of the package
for iSCSI.
SSB codes returned by raidcom check external_iscsi_name
raidcom check external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
SSB codes returned by raidcom add external_iscsi_name
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 604
raidcom check external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E20 9B01 The specied iSCSI target is not registered.
SSB codes returned by raidcom delete external_iscsi_name
raidcom delete external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E20 9B01 The specied iSCSI target is not registered.
CMDRJE Executing 2E11 4304 The operation cannot be performed because
the specied iSCSI target is dened to the
external path.
SSB codes returned by raidcom discover external_iscsi_name
raidcom discover external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
SSB codes returned by raidcom delete external_iscsi_name
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 605
raidcom discover external_iscsi_name
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 9B01 Failed to search the iSCSI target. Check the
setting of input parameter or the network
connection.
CMDRJE Executing 2E14 9B01 The processing failed because multiple
searches for the iSCSI target were executed.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN).
CMDRJE Executing 2E31 8301 The specied port is not a port of the package
for iSCSI.
SSB codes returned by raidcom modify external_chap_user
raidcom modify external_chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B02 The specied CHAP user or CHAP secret is
invalid.
CMDRJE Executing 2E02 8403 The specied virtual port number is out of
range.
CMDRJE Executing 2E02 9C01 The specied IP address is invalid.
CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specied
port is disabled.
CMDRJE Executing 2E20 8401 The specied virtual port is not dened.
CMDRJE Executing 2E20 9B01 The specied iSCSI target is not registered.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN).
SSB codes returned by raidcom modify external_chap_user
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 606
SSB codes returned by raidcom modify initiator_chap_user
raidcom modify initiator_chap_user
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 9B02 The specied CHAP user or CHAP secret is
invalid.
CMDRJE Executing 2E11 4305 The operation cannot be performed because
the specied port is dened to the external
path.
CMDRJE Executing 2E21 810A The shared memory is not installed.
CMDRJE Executing 2E31 8301 The specied port is not a port of the package
for iSCSI.
SSB codes returned by raidcom initialize parity_grp
raidcom initialize parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 0101 The parity group number is not in the eective
range.
CMDRJE Executing 2E00 0102 The operation cannot be performed because it
is not a parity group.
Get Command
Status
Async 2E10 0000 LDEV is used as a ShadowImage pair volume.
Get Command
Status
Async 2E10 0001 LDEV is used as a TrueCopy pair volume or
Universal Replicator pair volume.
Get Command
Status
Async 2E10 0003 LDEV is used as a Compatible FlashCopy® V2
relationship.
Get Command
Status
Async 2E10 0004 LDEV is used as a Thin Image pair volume or a
Copy-on-Write Snapshot pair volume.
Get Command
Status
Async 2E10 0008 LDEV is used as a system disk.
Get Command
Status
Async 2E10 0010 LDEV is not blocked.
SSB codes returned by raidcom modify initiator_chap_user
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 607
raidcom initialize parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 0062 LDEV is used as the primary volume of a global-
active device (GAD) pair.
Get Command
Status
Async 2E10 0063 LDEV is used as the secondary volume of a
global-active device (GAD) pair.
Get Command
Status
Async 2E10 0100 The formatting operation cannot be performed
because the encryption value of the key
number that is set to encryption ECC is invalid.
Get Command
Status
Async 2E10 0101 The formatting operation cannot be performed
because the checksum of the encryption key
does not match.
Get Command
Status
Async 2E10 0210 The operation cannot be performed because
the capacity saving status of LDEV is Failed.
Get Command
Status
Async 2E10 6022 The operation cannot be performed because
the deduplication system data volume of the
pool linked with an LDEV is blocked.
Get Command
Status
Async 2E11 0007 LDEV is in shredding.
Get Command
Status
Async 2E11 0009 The operation cannot be performed because
LDEV is now expanding.
Get Command
Status
Async 2E11 001E The operation cannot be performed because
the virtual disk space is blocked.
Get Command
Status
Async 2E11 010A The target parity group is in the state of
correction copy.
Get Command
Status
Async 2E11 6004 The operation of Dynamic Provisioning V-VOL
cannot be performed because there is a
blocked pool.
Get Command
Status
Async 2E11 6006 The operation of Dynamic Provisioning V-VOL
cannot be performed because there is a
blocked pool volume.
Get Command
Status
Async 2E11 8004 The operation cannot be performed because
the internal processing is in progress.
Get Command
Status
Async 2E11 8010 The operation cannot be performed because
the internal processing is in progress.
SSB codes returned by raidcom initialize parity_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 608
raidcom initialize parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing
Async
2E13 0102 The operation cannot be performed because
there is no LDEV in the parity group.
Get Command
Status
Async 2E14 0000 The processing stopped because aborting
processing is required.
Get Command
Status
Async 2E20 0000 LDEV is not installed.
CMDRJE
Get Command
Status
Executing
Async
2E20 0100 There is no parity group.
Get Command
Status
Async 2E30 000A LDEV is used as a Dynamic Provisioning.
Get Command
Status
Async 2E30 000C LDEV is used as a quorum disk.
Get Command
Status
Async 2E30 000E LDEV is used as a pool volume.
Get Command
Status
Async 2E30 000F LDEV is used as a journal volume.
Get Command
Status
Async 2E30 001A Volume Security is set to LDEV.
Get Command
Status
Async 2E30 004E The Data Retention Utility/Volume Retention
Manager attribute of LDEV is enabled.
Get Command
Status
Async 2E30 0061 LDEV is a pool volume and the pool volume
include the Dynamic Provisioning volume that
is not in the blocked status.
Get Command
Status
Async 2E30 0074 LDEV cannot be operated because it is an
external volume mapped for online data
migration.
Get Command
Status
Async 2E30 0206 The operation cannot be performed because
the LDEV is a deduplication system data
volume.
SSB codes returned by raidcom initialize parity_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 609
raidcom initialize parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E31 0001 Maintenance work cannot be performed
because the LDEV is a quorum disk.
CMDRJE
Get Command
Status
Executing
Async
2ECF FEEC An internal error occurred. Call customer
support.
CMDRJE Executing 2EF3 0102 The specied parameter is invalid. Check the
Command Control Interface Command Reference.
SSB codes returned by raidcom get parity_grp
raidcom get parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2ECF 00F1 The operation cannot be executed because the
operation is not supported.
SSB codes returned by raidcom modify parity_grp
raidcom modify parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E00 0101 The parity group number or the external
volume group number is not within a valid
range.
CMDRJE Executing 2E00 0102 The specied group type is not correct.
Get Command
Status
Async 2E10 0103 The specied operation cannot be performed
because the collection copy is in process.
Get Command
Status
Async 2E10 0104 The specied operation cannot be performed
because the dynamic sparing is in process.
SSB codes returned by raidcom get parity_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 610
raidcom modify parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 0105 The specied operation cannot be performed
because the copy back is in process.
Get Command
Status
Async 2E10 0107 The specied operation cannot be performed
because the collection access is in process.
Get Command
Status
Async 2E10 0108 The specied parity group is a RAID
conguration which cannot be used as the pool
vol.
Get Command
Status
Async 2E10 010A The specied operation cannot be performed
because the parity group does not support
accelerated compression.
Get Command
Status
Async 2E10 010B The operation cannot be performed because
data remains in a expanded space of the parity
group. Format parity groups.
Get Command
Status
Async 2E10 010C The specied operation cannot be performed
because the encryption is enabled.
Get Command
Status
Async 2E10 8500 The specied operation cannot be performed
because the drive copy is in process.
Get Command
Status
Async 2E10 8501 The specied operation cannot be performed
because the drive is blocked.
Get Command
Status
Async 2E10 8506 The specied operation cannot be performed
because the drive’s rmware does not support
accelerated compression.
Get Command
Status
Async 2E11 0057 The specied operation cannot be performed
because the LDEV is under format, shredding,
or quick format.
Get Command
Status
Async 2E11 005A The specied operation cannot be performed
because the pool is used as the pool which is
full allocated.
Get Command
Status
Async 2E11 005B The specied operation cannot be performed
because the LDEV in the parity group is
dispersed in several pools.
Get Command
Status
Async 2E11 005C There is a volume which Data Retention Utility
is set in the specied parity group.
SSB codes returned by raidcom modify parity_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 611
raidcom modify parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 005D The specied operation cannot be performed
because the LDEV is created in the expanded
space of the parity group.
Get Command
Status
Async 2E11 005E The specied operation cannot be performed
because the LDEV belongs in the blocked pool.
Get Command
Status
Async 2E11 0208 The operation cannot be performed because
the specied parity group contains an LDEV
that is not a pool volume.
Get Command
Status
Async 2E11 800F The operation failed because the DKCMAIN
microcode version is mixed.
CMDRJE Executing 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
CMDRJE
Get Command
Status
Executing/
Async
2E20 0100 There is no parity group.
Get Command
Status
Async 2E30 0005 The volume which Cache Residency Manager is
congured is available in the specied parity
group.
Get Command
Status
Async 2E30 0007 The LDEV of which path is dened is available.
Get Command
Status
Async 2E30 000F The LDEV in the specied parity group is used
as the journal volume.
Get Command
Status
Async 2E30 0038 The LDEV of which size is smaller than the
possible value that can be registered to the
pool is in the specied parity group.
Get Command
Status
Async 2E31 0001 The LDEV in the specied parity group is used
as the quorum disk.
Get Command
Status
Async 2E31 0201 The LDEV in the specied parity group is used
as the pair volume.
Get Command
Status
Async 2E31 0202 The LDEV in the specied parity group is
mapped for the online data migration.
CMDRJE Executing/
Async
2ECF FEEC Internal error occurred. Contact customer
support.
SSB codes returned by raidcom modify parity_grp
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 612
raidcom modify parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
CMDRJE Executing 2EF3 0102 The specied operation cannot be performed
because the operation is not supported.
SSB codes returned by raidcom get local_replica_opt
raidcom get local_replica_opt
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EBD FEEC Internal error occurred.
SSB codes returned by raidcom modify local_replica_opt
raidcom modify local_replica_opt
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 9D01 Multiple option IDs cannot be specied.
CMDRJE Executing 2E02 9D02 The specied option ID is out of the eective
range.
CMDRJE Executing 2E10 8000 The operation cannot be performed because
Storage Navigator or Device Manager - Storage
Navigator is in progress, another application is
in progress on the SVP, or the conguration is
being changed. Wait a while, and then retry the
operation.
CMDRJE Executing 2E11 8019 Shadow Initialize is running.
CMDRJE Executing 2E21 810A A shared memory is not installed.
SSB codes returned by raidcom get local_replica_opt
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 613
raidcom modify local_replica_opt
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E3F 8000 The specied operation is not supported in the
current microcode version.
CMDRJE Executing 2EBD FEEC Internal error occurred. Contact customer
support.
CMDRJE Executing 2EBE 9E01 The specied parameter is invalid.
SSB codes returned by raidcom add license (VSP Gx00 models and VSP Fx00
models)
raidcom add license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC0 0009 No program product is supported.
CMDRJE Executing 2EC0 0030 The program product cannot be installed
because the history of the trial for the
Temporary key remains.
CMDRJE Executing 2EC0 0051 To install this program product, install or
enable the related program products rst.
CMDRJE Executing 2EC0 0052 This program product cannot be installed
because it is pre-installed.
CMDRJE Executing 2EC0 0060 The program product is already installed.
CMDRJE Executing 2EC0 0081 The specied program product ID is invalid.
CMDRJE Executing 2EC0 0090 The specied license key code is invalid.
CMDRJE Executing 2EC0 0091 The serial number is not correct.
CMDRJE Executing 2EC0 0101 The current DKCMAIN rmware version does
not support this program product.
CMDRJE Executing 2EC0 0102 This program product requires a higher-version
hardware product.
SSB codes returned by raidcom add license (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 614
raidcom add license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC0 0103 To use this program product, increase the
shared memory allocation, and enable the
program product.
CMDRJE Executing 2EC0 0108 This program product requires another type of
DKC.
CMDRJE Executing 2EC0 010D The specied program product is not
supported.
CMDRJE Executing 2EC0 0130 The model information for the license key code
is not correct.
CMDRJE Executing 2EC0 0200 The specied number of extended days is
shorter than the number of trial days.
CMDRJE Executing 2EC0 0201 The program product cannot be enabled
because the license capacity is insucient.
CMDRJE Executing 2EC0 0204 The license capacity is insucient. The program
product is installed, but it will be invalid if the
license capacity is not increased before the
contract period expires.
CMDRJE Executing 2EC0 0206 The status of the specied license is already
changed or incorrect.
CMDRJE Executing 2EC0 050C With the current DKCMAIN rmware version,
the program product cannot be installed.
CMDRJE Executing 2EC0 2E01 The specied operation is not supported in the
current microcode version.
SSB codes returned by raidcom delete license (VSP Gx00 models and VSP Fx00
models)
raidcom delete license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC1 0009 No program product is supported.
SSB codes returned by raidcom delete license (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 615
raidcom delete license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC1 0051 To remove this program product, remove or
disable the related program products rst.
CMDRJE Executing 2EC1 0081 The specied program product ID is invalid.
CMDRJE Executing 2EC1 0104 To remove this program product, the
conguration must be changed.
CMDRJE Executing 2EC1 0105 This program product cannot be removed
because it is being used.
CMDRJE Executing 2EC1 0106 To remove this program product, another
program product must be removed or disabled
rst.
CMDRJE Executing 2EC1 0107 To remove this program product, another
program product must be removed or disabled
rst.
CMDRJE Executing 2EC1 010C Data Retention Utility cannot be deleted
because secondary volume rejection or
reservation settings remain.
CMDRJE Executing 2EC1 010D The specied program product is not
supported.
CMDRJE Executing 2EC1 0206 The status of the specied license is already
changed or incorrect.
CMDRJE Executing 2EC1 0501 The specied program product is already
removed.
CMDRJE Executing 2EC1 050C With the current DKCMAIN rmware version,
the program product cannot be removed.
SSB codes returned by raidcom modify license (VSP Gx00 models and VSP Fx00
models)
raidcom modify license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC2 0009 No program product is supported.
SSB codes returned by raidcom modify license (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 616
raidcom modify license
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2EC2 0051 To enable or disable this program product,
enable or disable the related program products
rst.
CMDRJE Executing 2EC2 0081 The specied program product ID is invalid.
CMDRJE Executing 2EC2 0101 The current DKCMAIN rmware version does
not support this program product.
CMDRJE Executing 2EC2 0102 This program product requires a higher-version
hardware product.
CMDRJE Executing 2EC2 0103 To use this program product, increase the
shared memory allocation, and enable the
program product.
CMDRJE Executing 2EC2 0105 This program product cannot be removed
because it is being used.
CMDRJE Executing 2EC2 0106 To disable this program product, another
program product must be removed or disabled
rst.
CMDRJE Executing 2EC2 0107 To disable this program product, another
program product must be removed or disabled
rst.
CMDRJE Executing 2EC2 0108 This program product requires another type of
DKC.
CMDRJE Executing 2EC2 010C Data Retention Utility cannot be deleted
because secondary volume rejection or
reservation settings remain.
CMDRJE Executing 2EC2 010D The specied program product is not
supported.
CMDRJE Executing 2EC2 0205 The program product was removed because
the Term license had expired.
CMDRJE Executing 2EC2 0206 The status of the specied license is already
changed or incorrect.
CMDRJE Executing 2EC2 0503 The specied operation cannot be performed
because the key type is incorrect.
CMDRJE Executing 2EC2 050C The current DKCMAIN rmware version cannot
enable or disable the program product.
SSB codes returned by raidcom modify license (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 617
SSB codes returned by raidcom initialize pool
raidcom initialize pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E00 6000 The value of the specied ID is out of range.
Get Command
Status
Async 2E10 0001 The volume dened in specied pool is used as
a TrueCopy pair.
Get Command
Status
Async 2E10 0002 The volume dened in specied pool is used as
a Universal Replicator pair.
Get Command
Status
Async 2E10 0004 The volume dened in specied pool is used as
a Thin Image pair.
Get Command
Status
Async 2E10 0005 The volume dened in specied pool is used as
aVolume Migration volume.
Get Command
Status
Async 2E10 0213 The volume dened in specied pool is used as
a global-active device (GAD) pair.
Get Command
Status
Async 2E10 0216 The volume dened in specied pool is used as
a ShadowImage pair.
Get Command
Status
Async 2E10 600B The specied pool is blocked.
Get Command
Status
Async 2E10 600D The specied pool is shrinking.
Get Command
Status
Async 2E10 6020 The specied pool is in deduplication disabled.
Get Command
Status
Async 2E10 6023 The specied pool is being created or
expanded.
Get Command
Status
Async 2E10 6024 The specied pool is being deleted.
Get Command
Status
Async 2E11 0204 The deduplication system data volume dened
in the specied pool or the volume for which
the deduplication function is enabled is not
blocked.
CMDRJE Executing 2E11 9400 The command cannot be accepted. Wait a
while and issue the same command.
CMDRJE Executing /
Async
2E20 6000 The specied pool is not installed.
SSB codes returned by raidcom initialize pool
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 618
raidcom initialize pool
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Get Command
Status
Async 2E21 8101 The control memory or shared memory for
Dynamic Provisioning is not installed.
Get Command
Status
Async 2E30 000F The volume dened in specied pool is used as
a journal volume.
CMDRJE Executing 2EE7 00F0 The specied command cannot be accepted
because the command is not supported.
CMDRJE
Get Command
Status
Executing /
Async
2EE7 FEEC The internal error occurs. Contact customer
support.
SSB codes returned by raidcom add parity_grp (VSP Gx00 models, VSP Fx00
models)
raidcom add parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E00 000D The emulation type is incorrect.
CMDRJE
Get Command
Status
Executing/
Async
2E00 0101 The parity group number is not in the eective
range.
CMDRJE
Get Command
Status
Executing/
Async
2E00 0108 The RAID type of the specied parity group is
not correct.
CMDRJE
Get Command
Status
Executing/
Async
2E00 7000 The specied CLPR ID is out of the range.
CMDRJE Executing 2E00 8500 The specied drive box or drive is not correct.
SSB codes returned by raidcom add parity_grp (VSP Gx00 models, VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 619
raidcom add parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E02 0101 A parity group in which encryption and
accelerated compression are enabled cannot
be created.
Get Command
Status
Async 2E02 8501 The specied drive has dierent drive type
codes.
Get Command
Status
Async 2E10 0109 The parity group cannot be created because
the parity group which is specied to be
combined contains parity groups that do not
support accelerated compression.
Get Command
Status
Async 2E10 010A The specied operation cannot be performed
because the parity group does not support
accelerated compression.
Get Command
Status
Async 2E10 8003 The specied operation cannot be performed
because the storage system is being turned o.
Get Command
Status
Async 2E10 8500 The specied operation cannot be performed
because the drive copy is in process.
Get Command
Status
Async 2E10 8501 The specied operation cannot be performed
because the drive is blocked.
Get Command
Status
Async 2E10 8503 The specied drive is already used.
Get Command
Status
Async 2E10 8505 The parity group cannot be created because
some of the specied drives do not support
accelerated compression.
Get Command
Status
Async 2E10 8506 The specied operation cannot be performed
because the drive’s rmware version does not
support accelerated compression.
Get Command
Status
Async 2E11 0001 The specied operation cannot be performed
because the LDEV is being veried.
Get Command
Status
Async 2E11 0056 The specied operation cannot be performed
because data in the cache is corrupted.
Get Command
Status
Async 2E11 0057 The specied operation cannot be performed
because the LDEV is under format, shredding,
or quick format.
SSB codes returned by raidcom add parity_grp (VSP Gx00 models, VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 620
raidcom add parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 0109 The entered parity group ID is already used.
Get Command
Status
Async 2E11 8012 The specied operation cannot be performed
because the power condition of the drive box is
abnormal.
Get Command
Status
Async 2E11 8013 The specied operation cannot be performed
because storage system is in process.
Get Command
Status
Async 2E11 8102 The specied operation cannot be performed
because cache memory is blocked.
Get Command
Status
Async 2E11 810A The specied operation cannot be performed
because the cache status is abnormal.
Get Command
Status
Async 2E11 8200 The specied operation cannot be performed
because the MP unit status is being changed.
Get Command
Status
Async 2E11 8201 The specied operation cannot be performed
because the MP unit is blocked.
Get Command
Status
Async 2E11 8301 The specied operation cannot be performed
because DKB is being transferred.
Get Command
Status
Async 2E11 8302 The specied operation cannot be performed
because CHB is being transferred.
Get Command
Status
Async 2E11 8311 The specied operation cannot be performed
because DKB is blocked.
Get Command
Status
Async 2E11 8312 The specied operation cannot be performed
because CHB is blocked.
Get Command
Status
Async 2E11 8400 The specied operation cannot be performed
because the port is blocked.
Get Command
Status
Async 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E11 9A00 The encryption key cannot be obtained from
the key management server.
Get Command
Status
Async 2E11 9A01 The specied operation cannot be performed
because the unused encryption keys have run
out.
SSB codes returned by raidcom add parity_grp (VSP Gx00 models, VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 621
raidcom add parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E20 7001 The specied CLPR is not installed.
Get Command
Status
Async 2E20 8501 The specied drive is not installed.
CMDRJE
Get Command
Status
Executing/
Async
2EC4 FEEC An internal error occurred. Contact customer
support.
SSB codes returned by raidcom delete parity_grp (VSP Gx00 models and VSP
Fx00 models)
raidcom delete parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E00 0101 The parity group number is not within the valid
range.
Get Command
Status
Async 2E10 0000 The specied parity group contains LDEVs used
by another program product.
Get Command
Status
Async 2E10 0001 The specied parity group contains an LDEV
used as a TrueCopy or Universal Replicator
pair.
Get Command
Status
Async 2E10 0062 The specied parity group contains an LDEV
used as the P-VOL of a GAD pair.
Get Command
Status
Async 2E10 0063 The specied parity group contains an LDEV
used as the S-VOL of a GAD pair.
Get Command
Status
Async 2E02 0100 The specied operation cannot be performed
because the encryption value of the key
number that is set to encryption ECC is invalid.
Get Command
Status
Async 2E10 0101 The specied operation cannot be performed
because the checksum of the encryption key is
not coincident.
SSB codes returned by raidcom delete parity_grp (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 622
raidcom delete parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E10 8003 The specied operation cannot be performed
because the storage system is being turned o.
Get Command
Status
Async 2E10 8500 The specied operation cannot be performed
because the drive copy is in process.
Get Command
Status
Async 2E10 8501 The specied operation cannot be performed
because the drive is blocked.
Get Command
Status
Async 2E11 0001 The specied operation cannot be performed
because the LDEV is being veried.
Get Command
Status
Async 2E11 0056 The specied operation cannot be performed
because data in the cache is corrupted.
Get Command
Status
Async 2E11 0057 The specied operation cannot be performed
because the LDEV is under format, shredding,
or quick format.
Get Command
Status
Async 2E11 0058 The specied operation cannot be performed
because the specied parity group is using a
spare drive.
Get Command
Status
Async 2E11 2206 You do not have the operation authority to
operate the target resource group. Specify the
resource group that is allocated to the user
group as the operation target, or set the
operation authority to the user group in order
to operate the target resource group.
Get Command
Status
Async 2E11 8012 The specied operation cannot be performed
because the power condition of the drive box is
abnormal.
Get Command
Status
Async 2E11 8013 The specied operation cannot be performed
because storage system is in process.
Get Command
Status
Async 2E11 8102 The specied operation cannot be performed
because cache memory is blocked.
Get Command
Status
Async 2E11 810A The specied operation cannot be performed
because the cache status is abnormal.
Get Command
Status
Async 2E11 8200 The specied operation cannot be performed
because the MP unit status is being changed.
SSB codes returned by raidcom delete parity_grp (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 623
raidcom delete parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E11 8201 The specied operation cannot be performed
because the MP unit is blocked.
Get Command
Status
Async 2E11 8301 The specied operation cannot be performed
because DKB is being transferred.
Get Command
Status
Async 2E11 8302 The specied operation cannot be performed
because CHB is being transferred.
Get Command
Status
Async 2E11 8311 The specied operation cannot be performed
because DKB is blocked.
Get Command
Status
Async 2E11 8312 The specied operation cannot be performed
because CHB is blocked.
Get Command
Status
Async 2E11 8400 The specied operation cannot be performed
because the port is blocked.
Get Command
Status
Async 2E11 9400 The command cannot be accepted. After a
while, execute the same command.
Get Command
Status
Async 2E11 9A00 The encryption key cannot be obtained from
the key management server.
Get Command
Status
Async 2E11 9A01 The specied operation cannot be performed
because the unused encryption keys have run
out.
Get Command
Status
Async 2E14 0101 The operation cannot be continued because an
error occurred while the command for deleting
a parity group was being executed. Check if the
parity group is deleted. If it is not deleted,
execute the command again. If this problem
occurs again, contact customer support.
Get Command
Status
Async 2E20 0100 The parity group is not found.
Get Command
Status
Async 2E30 0007 The specied parity group contains LDEVs for
which LU path is already dened.
Get Command
Status
Async 2E30 000E The operation failed because the specied
parity group contains a pool volume of
Dynamic Provisioning.
SSB codes returned by raidcom delete parity_grp (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 624
raidcom delete parity_grp
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Async 2E30 000F The specied parity group contains an LDEV
which is already used as a journal volume or a
data volume.
Get Command
Status
Async 2E30 004E The specied parity group contains a Data
Retention Utility/Volume Retention Manager
attribute device.
Get Command
Status
Async 2E30 0060 The LDEV in the specied parity group is used
as a command device that is used in the
extended consistency group.
Get Command
Status
Async 2E30 0095 The specied parity group cannot be deleted
because it contains the remote command
device which is used for the mirror of the
journal group.
CMDRJE
Get Command
Status
Executing/
Async
2EC4 FEEC An internal error occurred. Contact customer
support.
SSB codes returned by the raidcom add clpr command (VSP Gx00 models and
VSP Fx00 models)
raidcom add clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 7001 CLPR 0 is specied.
Get Command
Status
Executing/
Async
2E02 7002 The number of characters of the specied CLPR
name is invalid.
Get Command
Status
Executing/
Async
2E02 7003 The specied CLPR name contains characters
other than alphanumeric characters.
Get Command
Status
Executing/
Async
2E02 7004 The CLPR capacity of CLPR0 is out of the range.
Get Command
Status
Executing/
Async
2E02 7005 The value set for the specied CLPR capacity is
out of the range.
SSB codes returned by the raidcom add clpr command (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 625
raidcom add clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Executing/
Async
2E02 7006 The specied CLPR name is reserved for the
storage system.
Get Command
Status
Executing/
Async
2E11 7001 The specied CLPR name is duplicated.
Get Command
Status
Executing/
Async
2E11 7002 The number of characters of the specied CLPR
name is invalid.
Get Command
Status
Executing/
Async
2E11 7003 The capacity of the CLPR is being changed.
Get Command
Status
Executing/
Async
2E11 7004 The resource of the CLPR is being moved.
SSB codes returned by raidcom reset command_status command
raidcom reset command_status
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2EF1 000C The operation cannot be performed because
the internal processing is in progress. After a
while, perform the operation again.
CMDRJE
Get Command
Status
Executing/
Async
2EF1 000E The specied request ID is invalid.
CMDRJE
Get Command
Status
Executing/
Async
2EF1 000F The operation cannot be performed because a
request ID managed by another session is
specied.
CMDRJE
Get Command
Status
Executing/
Async
2EF1 0010 The operation cannot be performed because
the specied request ID is being executed.
SSB codes returned by raidcom reset command_status command
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 626
SSB codes returned by the raidcom add clpr command (VSP Gx00 models and
VSP Fx00 models)
raidcom add clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 7001 CLPR 0 is specied.
Get Command
Status
Executing/
Async
2E02 7002 The number of characters of the specied CLPR
name is invalid.
Get Command
Status
Executing/
Async
2E02 7003 The specied CLPR name contains characters
other than alphanumeric characters.
Get Command
Status
Executing/
Async
2E02 7004 The CLPR capacity of CLPR0 is out of the range.
Get Command
Status
Executing/
Async
2E02 7005 The value set for the specied CLPR capacity is
out of the range.
Get Command
Status
Executing/
Async
2E02 7006 The specied CLPR name is reserved for the
storage system.
Get Command
Status
Executing/
Async
2E11 7001 The specied CLPR name is duplicated.
Get Command
Status
Executing/
Async
2E11 7002 The number of characters of the specied CLPR
name is invalid.
Get Command
Status
Executing/
Async
2E11 7003 The capacity of the CLPR is being changed.
Get Command
Status
Executing/
Async
2E11 7004 The resource of the CLPR is being moved.
SSB codes returned by the raidcom delete clpr command (VSP Gx00 models and
VSP Fx00 models)
raidcom delete clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
CMDRJE Executing 2E02 7001 CLPR 0 is specied.
Get Command
Status
Executing/
Async
2E02 7002 The number of characters of the specied CLPR
name is invalid.
SSB codes returned by the raidcom add clpr command (VSP Gx00 models and VSP Fx00 models)
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 627
raidcom delete clpr
Error message
Executing/
Async
Error code
DescriptionSSB1 SSB2
Get Command
Status
Executing/
Async
2E02 7003 The specied CLPR name contains characters
other than alphanumeric characters.
Get Command
Status
Executing/
Async
2E11 7002 The number of characters of the specied CLPR
name is invalid.
Get Command
Status
Executing/
Async
2E11 7003 The capacity of the CLPR is being changed.
Get Command
Status
Executing/
Async
2E11 7004 The resource of the CLPR is being moved.
Get Command
Status
Executing/
Async
2E13 7001 A parity group or virtual volume is allocated to
the specied CLPR.
Get Command
Status
Executing/
Async
2E20 7002 The specied CLPR is not installed.
Get Command
Status
Executing/
Async
2E20 7002 The specied CLPR is already installed.
Get Command
Status
Executing/
Async
2E23 7001 The number of CLPRs that can be installed is
exceeded.
Other SSB codes indicating internal errors
The error codes (SSB1) listed below in the table indicate internal errors. For your
conrmation, contact customer support.
Error codes
DescriptionSSB1 SSB2
2EBB XXXX An internal error occurred. Contact customer support.
2EBD XXXX An internal error occurred. Contact customer support.
2EBE XXXX An internal error occurred. Contact customer support.
2EBF XXXX An internal error occurred. Contact customer support.
2EC3 XXXX An internal error occurred. Contact customer support.
2EC4 XXXX An internal error occurred. Contact customer support.
Other SSB codes indicating internal errors
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 628
Error codes
DescriptionSSB1 SSB2
2EC5 XXXX An internal error occurred. Contact customer support.
2EC6 XXXX An internal error occurred. Contact customer support.
2EC8 XXXX An internal error occurred. Contact customer support.
2EC9 XXXX An internal error occurred. Contact customer support.
2ECA XXXX An internal error occurred. Contact customer support.
2ECC XXXX An internal error occurred. Contact customer support.
2ECD XXXX An internal error occurred. Contact customer support.
2ECE XXXX An internal error occurred. Contact customer support.
2ECF XXXX An internal error occurred. Contact customer support.
2ED0 XXXX An internal error occurred. Contact customer support.
2ED6 XXXX An internal error occurred. Contact customer support.
2EDA XXXX An internal error occurred. Contact customer support.
2EDB XXXX An internal error occurred. Contact customer support.
2EE4 XXXX An internal error occurred. Contact customer support.
2EE6 XXXX An internal error occurred. Contact customer support.
2EE7 XXXX An internal error occurred. Contact customer support.
2EE8 XXXX An internal error occurred. Contact customer support.
2EEA XXXX An internal error occurred. Contact customer support.
2EEC XXXX An internal error occurred. Contact customer support.
2EEE XXXX An internal error occurred. Contact customer support.
2EEF XXXX An internal error occurred. Contact customer support.
2EF0 XXXX An internal error occurred. Contact customer support.
2EF6 XXXX An internal error occurred. Contact customer support.
2EXX FEEC An internal error occurred. Contact customer support.
Other SSB codes indicating internal errors
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 629
Calling customer support
If you need to contact customer support, please provide as much information about the
problem as possible, including:
■The circumstances surrounding the error or failure.
■The exact content of any error messages displayed on the host systems.
■The exact content of any error messages displayed by Storage Navigator.
■The Storage Navigator conguration information (use the Dump Tool).
■The data in the CCI error log le and trace data (all les in the HORCM_LOG directory).
■The service information messages (SIMs), including reference codes and severity
levels, displayed by Storage Navigator.
The Hitachi Vantara customer support sta is available 24 hours a day, seven days a
week. To contact technical support, log on to Hitachi Vantara Support Connect for
contact information: https://support.hitachivantara.com/en_us/contact-us.html
Calling customer support
Chapter 9: Troubleshooting
Command Control Interface User and Reference Guide 630
Glossary
Glossary
Command Control Interface User and Reference Guide 631
Index
A
alternate command device
dening 36
asynchronous commands
list of provisioning 177
processing 23, 176
authorities for commands and operations 101
C
cascading connections
and conguration les 67
conguration les 69
cascading pairs 264
cascading volumes
restrictions 265
CCI functions 22
cluster manager 267
command device
alternate 35
guarding 33
instance number 34
command execution modes 116
command parameter, HORCM_CMD (in-band 48
command parameter, HORCM_CMD (out-of-band 53
commands
authorities 101
error logging for audit 82
error messages and troubleshooting 372
examples 340
execution modes 23
in-band execution 90
out-of-band execution 90
processing asynchronously 176
processing synchronously 176
conguration check 125
conguration denition le
examples 43
conguration denition le settings
cascading connections 67, 69
HORCM_ALLOW_INST 62
conguration denition le settings (continued)
HORCM_CMD (in-band 48
HORCM_CMD (out-of-band 53
HORCM_DEV 56
HORCM_INST 59
HORCM_INSTP 62
HORCM_LDEV 60
HORCM_LDEVG 61
HORCM_MON 47
conguration le
parameters 43
conguration le parameters 43
conguration setting commands, raidcom 23
consistency groups 284
copy groups
dening 136
deleting 140
deleting LDEV 139
D
data protection
command compatibility 332
conguration examples 329
dening command device 338
environment variables 338
facility 327
parameters 326
permission command 332
permitting protected volumes 335
specications 328
data protection operations 323
data replication operations 259
Data Retention Utility
how it works 323
restrictions on volumes 324
Database Validator
how it works 325
restrictions 325
denition le, conguration
parameters 43
denition le, conguration parameters 43
Index
Command Control Interface User and Reference Guide 632
device groups
denition methods 130
deleting 135
settings and read operations 130
device parameter, HORCM_DEV 56
discovering remote volumes 319
dual pathing on Solaris 32
duplicated mirroring 263
E
endian
little vs big 42
environment variables for data protection 338
environment variables for log directories 79
error codes
horctakeover and pair
commands:troubleshooting 390
raidscan, raidqry, raidar, horcctl:troubleshooting
392
troubleshooting 370, 393
error messages
troubleshooting 370
examples
directory mound for Windows 352
GPT disk for Windows 351
group version control for mixed storage system
congurations 340
LDM volume discovery and ushing for Windows
341
mountvol attached to Windows 344
signature changing facility for Windows 348
SLPR conguration 359
specify host group 355
system buer ushing 344
volume discovery 341
external volumes
creating using Fibre Channel 224
creating using iSCSI 227
operations 224
F
fence level settings 290, 292
bre channel failure 290
les
log and trace les 79
OpenVMS 77
UNIX 72
user-created scripts 88, 89
Windows 74
H
HORCM_ALLOW_INST 62
HORCM_CMD (in-band) 48
HORCM_CMD (out-of-band) 53
HORCM_DEV 56
HORCM_INST 59
HORCM_INSTP 62
HORCM_LDEV 60
HORCM_LDEVG 61
HORCM_MON 47
horcm.conf le 307
host components
and pairing 42
HORCM 39
instance congurations 40
host group check 123
I
in-band
command execution 90
in-system replication 29
instance number 34
instance parameter, HORCM_INST 59
internal volumes
creating 197, 202
operations 197
iSCSI virtual port mode
disabling 223
enabling 222
iSCSI virtual port number
deleting 223
setting 222
L
LDEV
adding 133
check 118
deleting 134
LDEV group function 127
LDEV group parameter, HORCM_LDEVG 61
LDEV grouping 28
LDEV nickname 28, 180
LDEV parameter, HORCM_LDEV 60
line-by-line mode 23, 116
log and trace les
command error logging for audit 82
log les
environment variables for log directories 79
names and locations 79
Index
Command Control Interface User and Reference Guide 633
logging command errors for audit 82
M
mirror descriptors
and volumes 328
conguration le correspondence 63
mirroring
duplicated 263
monitor parameter, HORCM_MON 47
MxN conguration and control 305
O
OpenVMS
les 77
starting up one instance 170
starting up two instances 171
Oracle
protection of volume 325
restrictions with Database Validator 325
out-of-band
command execution 90
P
pairdisplay examples on HOST1 and HOST2 69
paired volumes 260
parameters, conguration 43
permission command and data protection 332
port check 121
precheck 24
provisioning operations 175
R
raidcom command
conguration setting command 23
remote command device
dening 36
replication 305
remote replication 30
remote volume discovery 319
replication
cascading pairs 264
cascading volumes 265
duplicated mirroring 263
in-system 29
local system conguration 274
operations 259, 275
pair status 276
paired volumes 284
replication (continued)
remote 30
remote system conguration 273
requirements 261
sidele cache 287
volume status 276
resource group locking 29
resource lock function 115
restrictions
cascading volumes 265
CCI operations 366
Data Retention Utility 324
Database Validator 325
replication 284
Volume Migration 305
S
script les
content checking 118
SCSI command interface
command competition 38
command ow 38
LDEVs 38
SCSI commands 37
sidele
cache 287
SLPR
conguration examples 359
security 357
security:specify SLPR protection facility 358
Solaris
dual pathing 32
SSB codes
troubleshooting 395
starting
as a service on Windows 172
one instance on OpenVMS 170
one instance on UNIX 168
one instance on Windows 169
two instance on OpenVMS 171
two instances on UNIX 168
two instances on Windows 170
synchronous commands
processing 176
system log messages
troubleshooting 370
T
takeover commands 267
trace control command 82
Index
Command Control Interface User and Reference Guide 634
trace les
trace control command 82
transaction mode 23, 24, 116
troubleshooting
command error codes 372
error messages and error codes 370
general 363
generic error codes (horctakeover and pair
commands) 390, 395
generic error codes (raidscan, raidqry, raidar,
horcctl) 392
notes and restrictions 366
specic codes 393
system log messages 370
U
UNIX
les 72
starting up one instance 168
starting up two instances 168
user authentication
command operation 97
V
virtual port mode
disabling 223
enabling 222
virtual port number
deleting 223
setting 222
virtual volumes
creating 204, 216
operations 204, 215
volume migration
commands 299
congurations 298
controlling 297
specications 298
volumes
restrictions using Data Retention Utility 324
W
Windows
les 74
starting as a service 172
starting up one instance 169
starting up two instances 170
Index
Command Control Interface User and Reference Guide 635
Hitachi Vantara Corporation
Corporate Headquarters
2845 Lafayette Street
Santa Clara, CA 95050-2639 USA
www.HitachiVantara.com | community.HitachiVantara.com
Regional Contact Information
Americas: +1 866 374 5822 or info@hitachivantara.com
Europe, Middle East, and Africa: +44 (0) 1753 618000 or info@emea@hitachivantara.com
Asia Pacific: + 852 3189 7900 or info.marketing.apac@hitachivantara.com

Navigation menu