Page 1 Command Control Interface User and Reference Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform F400, F600, F800 Hitachi Virtual Storage Hitachi PlatformUnified Storage VM...
Page 2 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.
Page 3 Contents Preface....................xi Intended audience....................xii Product version......................xii Release notes......................xii Changes in this revision.................... xii Referenced documents.....................xiii Document conventions.....................xiv Convention for storage capacity values..............xvi Accessing product documentation................xvii Getting help......................xvii Comments......................xvii 1 Overview....................1-1 About Command Control Interface................1-2 CCI functions......................1-2 CCI functions matrix..................
Page 4 Command device guarding...............2-3 Alternate command device function............2-5 Remote command device.................2-6 CCI and the SCSI command interface..............2-7 Command competition................2-8 Command flow..................2-8 Issuing commands for LDEVs within a LUSE device........2-9 CCI instance components on the host server.............2-9 HORCM operational environment............... 2-9 CCI instance configurations................
Page 5 Controlling User Role..................3-9 Controlling user resources................3-10 Commands executed depending on operation authorities........3-13 Relation between resource groups and command operations........3-21 Resource lock function..................3-24 Command execution modes................... 3-25 Overview......................3-25 Context check....................3-26 How to check..................3-27 Details of check contents............... 3-27 Configuration check..................
Page 6 5 Provisioning operations with CCI............5-1 About provisioning operations..................5-2 Overview of the configuration setting command..........5-2 Synchronous command processing............5-3 Asynchronous command processing............5-3 Errors during asynchronous command processing........5-3 Workflow for executing asynchronous commands........5-4 Asynchronous commands.................5-4 Help on configuration setting commands............5-6 LDEV nickname function..................5-6 Available provisioning operations................
Page 7 Moving parity groups................5-54 Checking result of CLPR transfer.............5-55 Server Priority Manager operations.................5-55 Configuring Server Priority Manager by specifying ports and WWNs of HBAs..5-56 Controlling the priority of I/O operations in storage systems on servers..5-56 Using and managing Server Priority Manager...........5-57 Setting SPM names for WWNs and registering them to the SPM group..
Page 8 Creating a Copy-on-Write Snapshot pair............6-34 Copy-on-Write Snapshot pair status..............6-35 Pair status relationship to Copy-on-Write Snapshot commands......6-36 Controlling Volume Migration................. 6-37 Specifications for Volume Migration..............6-37 Commands to control Volume Migration............6-39 Relations between "cc" command issues and status.......... 6-42 Restrictions for Volume Migration..............6-43 Universal Replicator MxN configuration and control..........6-44 Overview......................6-44...
Page 9 SSB codes...................... 9-22 SSB codes returned by the replication commands........9-22 SSB codes returned by the configuration setting command (raidcom)..9-24 Other SSB codes indicating internal errors..........9-197 Calling Hitachi Data Systems customer support............. 9-199 Index Command Control Interface User and Reference Guide...
Page 10 Command Control Interface User and Reference Guide...
Page 11 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. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.
Page 12: Intended Audience
Readers of this document should be familiar with the following: • Data processing and RAID storage systems and their basic functions. • The Hitachi RAID storage system and the manual for the storage system (for example, Hardware Guide, Hitachi Virtual Storage Platform User and Reference Guide). •...
Page 13: Referenced Documents
Command Control Interface User and Reference Guide, MK-90RD7010 Hitachi Command Suite: • Hitachi Command Suite User Guide, MK-90HC172 Hitachi Virtual Storage Platform G200, G400, G600, G800 and Hitachi Virtual Storage Platform F400, F600, F800: • Hitachi Thin Image User Guide, MK-92RD8011 •...
Page 14: Document Conventions
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 •...
Page 15 Convention Description Hitachi Virtual Refers to all models of the Hitachi Virtual Storage Platform G200, Storage Platform G400, G600, G800 storage systems, unless otherwise noted. G200, G400, G600, G800 (VSP G200, G400, G600, G800) VSP Gx00 models Hitachi Virtual Refers to all models of the Hitachi Virtual Storage Platform F400, Storage Platform F600, F800 storage systems, unless otherwise noted.
Page 16 Convention Description floor(value) ↑value↑ ceiling Ceiling function (round up value to the next integer) ceiling(value) _ (underlined text) Default value This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important or additional information. Provides helpful information, guidelines, or suggestions for performing tasks more effectively.
Page 17: Getting Help
Getting help is the destination for technical Hitachi Data Systems Support Connect support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: https://support.hds.com/en_us/contact-us.html. is a new global online community for...
Page 18 xviii Preface Command Control Interface User and Reference Guide...
Page 19: Overview
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 □ CCI functions □ CCI functions available on all RAID storage systems Overview...
Page 20: About Command Control Interface
Hitachi Virtual Storage Platform G200, G400, G600, G800 • Hitachi Virtual Storage Platform F400, F600, F800 • Hitachi Virtual Storage Platform G1000 and G1500 (VSP G1000 and G1500) For information about availability of Virtual Storage Platform F1500, contact your Hitachi Data Systems representative.
Page 21: Provisioning Functions
Table 1-1 Available CCI functions on the storage system models Storage system G1000, VSP Gx00 Function TagmaStore USP V/VM HUS VM models, VSP USP/NSC G1500, Fx00 models F1500 Local copy (open) Local copy (mainframe) Yes* Remote copy (open) Remote copy Yes* (mainframe) Data protection...
Page 22: Command Execution Modes
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 file is specified with the -zt option • Line-by-line mode, in which commands are executed row-by-row for the configuration setting (raidcom) commands You can use transaction mode to execute the following checking: •...
Page 23: Command Execution By The In-Band And Out-Of-Band Methods
The following table shows the checking function combinations between the precheck function and the transaction mode. Table 1-2 Summary of the checking functions Syntax Context Config Command syntax Execution check check check raidcom <command> Executed Executed executed executed raidcom <command> -checkmode precheck Executed executed executed...
Page 24 depending on the storage system models. For details about the location, System configuration using CCI on page 3-2. 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 configuration with VMware Site Recovery Manager (SRM), or from scripts, the command response might slow.
Page 25 Figure 1-1 Overview of out-of-band and in-band operations The following table provides a comparison of in-band and out-of-band operations. Table 1-3 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.
Page 26: User Authentication Mode
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 define the copy groups in the CCI configuration definition file on each host.
Page 27: Resource Group Function
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 Data Systems RAID storage systems. •...
Page 28: Data Protection
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 ®...
Page 29: Cci Software Environment
CCI software environment This chapter describes the CCI software environment. □ Overview of the CCI software environment □ CCI components on the RAID storage system □ CCI instance components on the host server □ CCI software files □ CCI log and trace files □...
Page 30: Overview Of 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.
Page 31: Command Device Guarding
(for example, for online maintenance), you can switch to an alternate command device manually. If no alternate command device is defined 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 on page...
Page 32 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 confirm whether it was required as the assignment for CCI or not, by detecting and adding two status bits to the instance assignment table.
Page 33: Alternate Command Device Function
# 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 Alternate command device function...
Page 34: Remote Command Device
Virtual Storage Platform: RCD is recommended in 3DC TC/UR and 3DC TCz/URz configurations. If there is intermix with VSP G1000, G1500 or VSP F1500, RCD is required. • Hitachi Unified Storage VM: RCD is recommended in 3DC TC/UR configurations. CCI software environment Command Control Interface User and Reference Guide...
Page 35: Cci And The Scsi Command Interface
The remote command device is defined using Device Manager - Storage Navigator. For more information, see the Hitachi Universal Volume Manager User Guide. 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.
Page 36: Command Competition
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. Command competition The CCI commands are asynchronous commands issued via the SCSI interface.
Page 37: Issuing Commands For Ldevs Within A Luse Device
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 configuration of the LDEVs when issuing a command, a new command is used to specify a target LU and acquire LDEV configuration data, as shown in the following figure.
Page 38: Cci Instance Configurations
Figure 2-8 HORCM operational environment 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- defined configuration definition file, and the log function for maintenance. Each instance uses its own configuration definition file to manage volume relationships while maintaining awareness of the other CCI instances.
Page 39 Figure 2-9 CCI instance configuration & components The four possible CCI instance configurations 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 offline 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.
Page 40: Host Machines That Can Be Paired
storage systems in different 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).
Page 41: Configuration Definition File
Restriction: CCI's communications among different 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 different operating systems).
Page 42 Figure 2-11 Configuration definition of paired volumes on page 2-14 illustrates the configuration definition of paired volumes. Figure 2-11 Configuration definition of paired volumes Configuration file 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...
Page 43 oralog oralog3 CL1-A1 oralog oralog4 CL1-A1 HORCM_INST #dev_group ip_address service oradb HST2 horcm oradb HST3 horcm oralog HST3 horcm Configuration file example — Windows servers The following table lists the parameters defined in the configuration file and specifies the default value, type, and limit for each parameter. Table 2-2 Configuration (HORCM_CONF) parameters Parameter Default...
Page 44: Configuration Definition File Settings
Notes: Use decimal notation for numeric values (not hexadecimal). For VSP G1000, G1500, 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 configuration definition file while CCI is running. Shut down CCI, edit the configuration file as needed, and then restart CCI.
Page 45: Horcm_Mon
• HORCM_CMD (out-of-band method) on page 2-21 • HORCM_DEV on page 2-23 • HORCM_INST on page 2-25 • HORCM_LDEV on page 2-26 • HORCM_LDEVG on page 2-27 • HORCM_INSTP on page 2-28 • HORCM_ALLOW_INST on page 2-28 HORCM_MON The monitor parameter (HORCM_MON) defines the following values: •...
Page 46 \\.\CMD-<Serial Number>:<Device special file name> <Serial Number>: Sets the serial number. For VSP G1000, G1500, and VSP F1500, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345. <Device special file name>: Sets the device special file name of a command device.
Page 47 \\.\CMD-Ser#-ldev#-Port# Note: For VSP G1000, G1500, and VSP F1500, add a "3" to the beginning of the serial number (for example, enter "312345" for serial number "12345"). The following example specifies 30095 for the storage system's serial...
Page 48 \\.\CMD-Ser#-ldev#-Port#:HINT Note: For VSP G1000, G1500, and VSP F1500, add a "3" to the beginning of the serial number (for example, enter "312345" for serial number "12345"). The following example specifies 30095 for the storage system's serial...
Page 49: Horcm_Cmd (Out-Of-Band Method)
\\.\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 specifications An alternate path with storage system’s serial number 30095 and LDEV number 250 can be specified as follows: \\.\CMD-30095-250-CL1:/dev/rdsk/ \\.\CMD-30095-250-CL2 \\.\CMD-30095:/dev/rdsk/c1...
Page 50 To create a virtual command device on an SVP (VSP, HUS VM, VSP G1000, G1500, and VSP F1500) Specify the following to HORCM_CMD of the configuration definition file. \\.\IPCMD-<SVP IP address>-<UDP communication port number>[-Unit ID] • <SVP IP address>: Sets an IP address of SVP.
Page 51: Horcm_Dev
HORCM_CMD #dev_name dev_name dev_name \\.\CMD-64015:/dev/rdsk/* \\.\IPCMD-158.214.135.113-31001 The following expresses the case when both the in-band and out-band methods are used in a command device alternative configuration: 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/* The following expresses the case of virtual command devices in a cascade configuration (three units): HORCM_CMD #dev_name dev_name dev_name...
Page 52 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).
Page 53: Horcm_Inst
• LU#: Defines the iSCSI/Fibre logical unit number (LU#) of the physical volume on the specified target ID and port. Note: In case of fibre channel, if the TID and LU# displayed on the system are different than the TID on the fibre address conversion table, then you must use the TID and LU# indicated by the raidscan command in the CCI configuration file.
Page 54: Horcm_Ldev
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 defined in the HORCM_INST parameter: • dev_group: The server name described in dev_group of HORC_DEV. •...
Page 55: Horcm_Ldevg
• Serial#: This parameter is used to specify the serial number of RAID box. For VSP G1000, G1500, and VSP F1500, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345. •...
Page 56: Horcm_Instp
HORCM_LDEVG #Copy_Group ldev_group Serial# 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.
Page 57: Correspondence Of Configuration File And Mirror Descriptors
Figure 2-14 Management of Pair configuration 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 configuration definition file are assigned to the corresponding mirror descriptors. This outline is described in the following table. "Omission of MU#"...
Page 58: Cascading Connection And Configuration Files
ShadowIma ge (Copy-on- MU#0 Write UR/GAD Snapshot) HORCM_DEV Parameter in Configuration File Only MU#1-#2 MU#1-#3 UR/GAD (MU#3-#63) Oradb oradev1 CL1-D HORCM_DEV oradev1 #dev_group dev_name port# TargetID LU# MU# Oradb oradev1 CL1-D HORCM_DEV oradev1 oradev11 #dev_group dev_name port# TargetID LU# MU# oradev21 Oradb oradev1...
Page 59: Shadowimage
Figure 2-15 ShadowImage cascade connection and configuration file ShadowImage Since ShadowImage is a mirrored configuration within one storage system, it can be described as a volume of the cascading connection according to two configuration definition files. For a ShadowImage-only cascading connection, the specified group is assigned to the mirror descriptor (MU#) of ShadowImage, specifically defining "0"...
Page 60 Figure 2-16 Pairdisplay on HORCMINST0 Figure 2-17 Pairdisplay on HORCMINST1 Figure 2-18 Pairdisplay on HORCMINST0 2-32 CCI software environment Command Control Interface User and Reference Guide...
Page 61: Cascading Connections For Truecopy And Shadowimage
Cascading connections for TrueCopy and ShadowImage The cascading connections for TrueCopy/ShadowImage can be set up by using three configuration definition files that describe the cascading volume entity in a configuration definition file on the same instance. The mirror descriptor of ShadowImage and TrueCopy definitely describe "0" as MU#, and the mirror descriptor of TrueCopy does not describe "0"...
Page 62 Figure 2-20 Pairdisplay for TrueCopy on HOST1 Figure 2-21 Pairdisplay for TrueCopy on HOST2 (HORCMINST) 2-34 CCI software environment Command Control Interface User and Reference Guide...
Page 63: Cci Software Files
Figure 2-22 Pairdisplay for ShadowImage on HOST2 (HORCMINST) Figure 2-23 Pairdisplay for ShadowImage on HOST2 (HORCMINST0) CCI software files The CCI software consists of files supplied with the software, log files created internally, and files created by the user. These files are stored on the local disk in the server machine.
Page 64: Cci Files Supplied With The Software
CCI files supplied with the software • CCI files for UNIX-based systems on page 2-36 • CCI files for Windows-based systems on page 2-37 • CCI files for OpenVMS-based systems on page 2-39 CCI files for UNIX-based systems Title File name Command name Mode User*...
Page 65: Cci Files For Windows-Based Systems
Title File name Command name Mode User* Group DB Validator /usr/bin/raidvchkset raidvchkset 0544 root setting DB Validator /usr/bin/raidvchkdsp raidvchkdsp 0544 root confirmation DB Validator /usr/bin/raidvchkscan raidvchkscan 0544 root confirmation Storage /HORCM/usr/bin/rmsra rmsra 0544 root Replication Adapter Configuration HORCM/usr/bin/raidcom raidcom 0544 root setting command A file for...
Page 66 Command Title File name name HORCM activation script \HORCM\etc\horcmstart.exe horcmstart HORCM shutdown script \HORCM\etc\horcmshutdown.exe horcmshutdown Synchronous waiting \HORCM\etc\pairsyncwait.exe pairsyncwait Connection confirmation \HORCM\etc\inqraid.exe inqraid Configuration setting and \HORCM\Tool\mkconf.exe mkconf confirming command Text filtering \HORCM\Tool\rmawk.exe rmawk Oracle Validation setting \HORCM\etc\raidvchkset.exe raidvchkset Oracle Validation confirmation \HORCM\etc\raidvchkdsp.exe raidvchkdsp Oracle Validation confirmation...
Page 67: Cci Files For Openvms-Based Systems
Command Title File name name Configuration setting and \HORCM\usr\bin\raidcfg.exe raidcfg confirming command 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.
Page 68: Cci Log And Trace Files
Title File name Command name User Synchronous waiting $ROOT:[HORCM.usr.bin]pairsyncwait.exe pairsyncwait Configuration file making $ROOT:[HORCM.usr.bin]mkconf.exe Text filtering $ROOT:[HORCM.usr.bin]rmawk.exe Database Validator setting $ROOT:[HORCM.usr.bin]raidvchkset.exe raidvchkset DB Validator confirmation $ROOT:[HORCM.usr.bin]raidvchkdsp.exe raidvchkdsp DB Validator confirmation $ROOT:[HORCM.usr.bin]raidvchkscan.exe raidvchkscan Storage Replication Adapter $ROOT:[HORCM.usr.bin]rmsra.exe rmsra Sample file for horcmstart $ROOT:[HORCM]loginhorcm*.com Sample file for horcmstart $ROOT:[HORCM]runhorcm*.com...
Page 69 The following figure shows a graphical representation of the CCI log and trace files within the CCI configuration environment. Figure 2-24 Logs and traces The startup log, error log, trace, and core files are stored as shown in Table 2-4 Log file names and locations on page 2-41.
Page 70 File UNIX-based systems Windows-based systems Error HORCM error log: HORCM error log: $HORCM_LOG/horcmlog_HOST/ $HORCM_LOG\horcmlog_HOST\horcm_log.txt horcm.log Trace HORCM trace: HORCM trace: $HORCM_LOG/horcmlog_HOST/ $HORCM_LOG\horcmlog_HOST\horcm_PID_trc.txt horcm_PID.trc Command trace: Command trace: $HORCM_LOG\horcmlog_HOST\horcc_PID_trc.txt $HORCM_LOG/horcmlog_HOST/ horcc_PID.trc Core HORCM core: HORCM core: $HORCM_LOG\core_HOST_PID\core $HORCM_LOG/core_HOST_PID/core Command core: Command core: $HORCM_LOG\core_HOST_PID\core $HORCM_LOG/core_HOST_PID/core Note: HOST denotes the host name of the corresponding machine.
Page 71: Cci Trace Files
CCI trace files The command trace file is used for maintenance aiming at troubleshooting. It is not created normally. If a cause of an error cannot be identified using the log file, the environment variables or trace control commands with trace control parameters are issued to start tracing and the trace file is created.
Page 72 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 file is moved to /HORCM/log*/horcc_HOST.oldlog file when reaching in the specified maximum size.
Page 73 $HORCC_LOGSZ HORCC_HOST.conf Performing Unspecified HORCC_LOGSZ=value Global tracing within this CCI instance HORCC_LOGSZ=0 NO global tracing within this CCI instance Unspecified or Use the default value (0) The same as nonexistent the current logging for only command error • Examples for execution /HORCM/log* directory [root@raidmanager log9]# total 16...
Page 74: Logging Raidcom Command
Logging raidcom command The history of performing raidcom command can be stored in syslog server by outputting it to the syslog file. Since the information of what command was performed by who and when are recorded on the syslog file, this is available to use for audit log.
Page 75 Output setting for the syslog file A syslog file is output when "1" is set on the RAIDCOM_SYSLOG of environment variables. The syslog file 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.
Page 76 Item Output example User name of the host root (user ID) Time that performed Wed Jun 27 10:15:13 2012 raidcom Table 2-8 Display information of the command row Item Output example Syslog fixed output Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info] part (Including the *It varies depending on the host OS.
Page 77: User-Created Files
• Logs when the 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).
Page 78 2-50 CCI software environment Command Control Interface User and Reference Guide...
Page 79: Cci Functions
CCI functions This chapter describes the CCI functions. □ System configuration using CCI □ Connecting to CCI server already connected by In-Band method using Out-of-Band method □ User authentication □ Command operation authority and user authentication □ Relation between resource groups and command operations □...
Page 80: System Configuration Using Cci
System configuration using CCI This section describes system configurations using the in-band method or out-of-band method. In addition, a system configuration 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 on page 1-5.
Page 81 Figure 3-1 System configuration example of in-band and out-of-band methods (VSP) In the following figure, 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.
Page 82 Figure 3-2 System Configuration Example of In-Band and Out-of-Band Methods (VSP G800, VSP F800) Note: In the out-of-band method using SVP of VSP G1000, VSP G1500, VSP F1500, VSP, or HUS VM, a command times out if the microcode of SVP is changed.
Page 83: Method Using The Out-Of-Band Method
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 specified 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.
Page 84: Hardware Requirements
system in In-Band method can be connected in Out-of-Band method. If a CCI server is specified as a virtual command device, it provides better performance than the Out-of-Band method with specified SVP/GUM as a virtual command device. 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.
Page 85 configuration definition file, users who can use virtual command device can be restricted. For the details about the settings to HORCM_ALLOW_INST, please refer to "Configuration definition file". • Security setting for virtual command device By using the following environment variable, security can be set to virtual command device.
Page 86: User Authentication
User authentication CCI allows user authentication by using the operation authority of a user set • 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 configuration information operation and in the out-of-band method.
Page 87: Command Operation Authority And User Authentication
Provisioning Guide for Hitachi Virtual Storage Platform Gx00 and Fx00 Models. • If the specific 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.
Page 88: Controlling User Resources
Controlling user resources CCI verifies the user who executes the command has been authenticated already. After that, CCI obtains the access authority of the resource groups that are configured on the user roles, and then compares the access authority of the user and the specified resources. Checking resource authorities If the access is not permitted by comparing the access authorities of the resource groups configured on the user roles and the specified resource, CCI...
Page 89 Commands raidcom pairXX Resources Authenticated Authenticated authenticated authenticated user user user user Virtual Permitted by the Permitted by the Permitted EX_EGPERM storage authority of the authority of the EX_EPPERM target resource target resource machine Notes: Above-described commands except for the raidcom command. User who uses the mode without the command authentication.
Page 90 Figure 3-4 Example of a pair operation when you do not define the HOMRCF_CHECK_RSGID environment variable The following figure shows an example of a local copy pair operation when you define the HOMRCF_CHECK_RSGID environment variable. You can avoid creating a pair which includes the volume without authority, therefore whether the both volumes which configure a pair are authenticated or not is checked.
Page 91: Commands Executed Depending On Operation Authorities
Figure 3-5 Example of a local copy pair operation when you define the HOMRCF_CHECK_RSGID environment variable Target resources The following objects are arbitrarily defined as the resource groups by each user. • LDEV • Physical port • Host group • RAID group •...
Page 92 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 Hitachi Storage Navigator User Guide for the storage system. Table 3-3 Executable commands executed depending on operation...
Page 93 Operation Executable Operation Operation Authority target command authority (Role) LDEV deletion raidcom delete ldev Storage authority Administrator (Provisioning) LDEV format raidcom initialize Storage authority ldev -operation fmt Administrator (Provisioning) raidcom initialize ldev -operation qfmt LDEV raidcom initialize Storage shredding ldev -operation shrd Administrator execution (Provisioning)
Page 94 Operation Executable Operation Operation Authority target command authority (Role) creation raidcom modify drive Storage cancellation -spare disable (VSP Administrator authority Gx00 models, VSP (Provisioning) Fx00 models) External External raidcom add Storage volume volume external_grp Administrator (Universal creation (Provisioning) raidcom discover Volume authority external_storage...
Page 95 Operation Executable Operation Operation Authority target command authority (Role) Pool deletion raidcom delete pool Storage authority Administrator (Provisioning) Dynamic Dynamic raidcom add ldev - Storage Provisioning Provisioning pool Administrator virtual virtual volume (Provisioning) raidcom extend ldev volume creation authority Dynamic raidcom delete ldev Storage Provisioning...
Page 96 Operation Executable Operation Operation Authority target command authority (Role) WWN deletion raidcom delete Storage authority hba_wwn Administrator (Provisioning) raidcom delete hba_iscsi raidcom delete chap_user LDEV group Device group raidcom add Storage and Copy device_grp Administrator group creation (Provisioning) raidcom add authority copy_grp Device group...
Page 97 Operation Executable Operation Operation Authority target command authority (Role) Pool raidcom reallocate Storage monitoring and pool Administrator reallocation (Provisioning) raidcom monitor start and stop pool authority Port Port attribute raidcom modify port Storage setting -port_attribute Administrator authority (System Resource Management) Port setting raidcom modify port Storage...
Page 98 Operation Executable Operation Operation Authority target command authority (Role) SPM setting raidcom add Storage information authority spm_wwn Administrator (System Resource raidcom add Management) spm_group raidcom delete spm_wwn raidcom delete spm_group raidcom modify spm_wwn raidcom modify spm_group raidcom modify spm_ldev raidcom delete spm_ldev Local copy Pairsplit and...
Page 99: Relation Between Resource Groups And Command Operations
Operation Executable Operation Operation Authority target command authority (Role) Quorum disk LDEV setting raidcom modify Storage authority quorum Administrator (Provisioning) HAM/GAD pair raidcom replace Storage creation quorum Administrator authority (Provisioning) HAM/GAD pair deletion authority Relation between resource groups and command operations The operation for using resource groups are different by the command devices (the In-Band method) or the Out-of-Band method that are used when you start CCI.
Page 100 Figure 3-6 Relation among user, command devices, and resource groups Table 3-4 Relation between resource groups and command devices Command operations Login Command Configuration using the Operating range Reference user device change out-of- band method System Can operate all resource Operable Operable Operable...
Page 101 Command operations Login Command Configuration using the Operating range Reference user device change out-of- band method and the shared ports after logging in. User 10 Can operate only in the Operable Operable Operable range of resource group 10 and 11, and the shared ports after logging in.
Page 102: Resource Lock Function
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, specifies only the objects or specifies 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.
Page 103 If multiple users (IDs) operate the same resource, you can prevent operation conflict for the target resource by using the raidcom lock resource command to confirm that no other user is using the resource. After the configuration change is completed, release the lock status by the raidcom unlock resource command.
Page 104: Context Check
• Precheck Specify the checkmode precheck option. It operates checking only (it does not execute processing even if no error is detected.) This can be specified at the both line-by-line mode and transaction mode. The following table shows the overview of execution modes and options of the configuration setting command.
Page 105: How To Check
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 the contents before executing the script helps reduce debugging after running the script.
Page 106 It is checked whether the operation is performed for the existing LDEV or not. 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 configuration definition file (if the target LDEV information does not exist in the configuration definition file), the error is not detected.
Page 107 • 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 configuration definition file or not (if the target LDEV information does not exist in the configuration definition file), the error is not detected.
Page 108 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 configuration definition 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...
Page 109 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#>...
Page 110 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.
Page 111: Configuration Check
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 configuration definition file), the error is not detected.
Page 112: Resource Location And Parameter
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 configuration information, execute the script by specifying the configuration file.
Page 113: Ldev Grouping Function
MP blade name MP blade number MP blade ID MPB-2PL MPB-2PM Table 3-8 MP blade names and parameters for VSP MP blade name MP blade number MP blade ID MPB-1MA MPB-1MB MPB-2MC MPB-2MD MPB-1ME MPB-1MF MPB-2MG MPB-2MH Table 3-9 MP unit names and parameters for HUS VM MP unit name MP blade number MP blade ID...
Page 114 Figure 3-7 LDEV grouping for USP V/VM and earlier For Virtual Storage Platform and later, CCI can be used to create a group of multiple LDEVs by defining device groups. This is accomplished by defining device groups in either the primary or secondary configuration definition file, but not both.
Page 115 Figure 3-8 LDEV grouping for VSP and later (device group and copy group) However, for executing replication function commands in CCI, two device groups must be combined and defined as a copy group. 3-37 CCI functions Command Control Interface User and Reference Guide...
Page 116: Device Group Definition Methods
When defining a device group or copy group by a command, the command can be issued from multiple CCI instances because the group information is defined in the storage system. Device group definition methods To define a device group or copy group in the CCI that supports Virtual Storage Platform or later, use one or both of following methods.
Page 117: Define Device Group
Command device setting Reading of device group or Group HORCM_LDEVG Security to be set User copy group Security information authentication information acquisition Do not read Only HORCM_DEV allowed User authentication Read required Do not read User authentication required Only HORCM_DEV allowed CMD security Read...
Page 118: Device Group Creation
• 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.
Page 119: Ldev Addition To Device Group
Creating a device group configured of simplex volumes with same ¢ device names. LDEV addition to device group Adding an LDEV to the device group by specifying a created device group name and the LDEV ID of the LDEV to be added. •...
Page 120: Device Group Deletion
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 shows use cases that can be deleted an LDEV from a device group.
Page 121: Copy Group Function
• Use Cases The following shows use cases that can be deleted an LDEV from a device group. Deleting a device group configured of simplex volumes and not ¢ associated with a copy group. • Deleting a device group configured of a simplex volume and a paired volume and not associated with a copy group.
Page 122 pair creation. As configuration 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 specification of multiple LDEVs.
Page 123: Copy Group Creation
Copy group creation Specifying two device groups and creating a copy group. The same device name must not be defined for any LDEVs in a specified device group. A copy group can be created whether the LDEV in the device group is paired status or not.
Page 124: Ldev Deletion From Copy Group
• Use cases The following shows use cases that can be added an LDEV to the device group associating a copy group. Adding an LDEV with a different device name (simplex volume) to a ¢ device group forming a copy group. Adding an LDEV with a different device name (paired volume) to a ¢...
Page 125: Copy Group Deletion
Copy group deletion Deleting a copy group by specifying a defined copy group. • Use cases A copy group can be deleted even if it is configured of simplex volumes or paired volumes. The following shows use cases that can be deleted a copy group. Deleting a copy group configured of simplex volumes.
Page 126 If a consistency group attribute is valid and no consistency group ID is specified, automatically assign a consistency group ID (1 copy group=1 consistency group). If the automatic consistency group assignment is specified and the other pairs in a copy group already have consistency group IDs, assign the same consistency group ID.
Page 127: 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®...
Page 128: Pair Status And Access Permission For Mainframe Ldevs
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 *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...
Page 129 Pair status in Storage Access to Access to Pair status in CCI Navigator mainframe mainframe Notes P-VOL S-VOL Open Mainframe Open Mainframe Notes: When the system option mode 20 is on, this is a read only volume. PDUB (inconsistency in LUSE status) does not exist in the mainframe system. Table 3-12 Pair status and access permission for Universal Replicator/Universal Replicator for Mainframe Pair status in Storage...
Page 130: Operational Differences For Multiplatform Volumes
Table 3-13 Pair status and access permission for ShadowImage/ShadowImage for Mainframe Pair status in Storage Access to Access to Pair status in CCI Navigator mainframe mainframe Notes P-VOL S-VOL Open Mainframe Open Mainframe SMPL Simplex SMPL SMPL Read/write Read/write simplex enabled enabled COPY(PD)
Page 131: Operational Differences For Replication Commands
Operational differences for replication commands The following table shows the differences between open volumes and mainframe volumes in replication commands. For details on the differences, see the manual for each program product. Table 3-15 Differences in replication commands Operation in Operation in Command Option...
Page 132: Global Storage Virtualization Function
The global storage virtualization function enables you to minimize rewrites of configuration definition files (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 modification of the script file that you used for the older models, when you operate volumes using the script file created by you.
Page 133: Using Cci With The Global Storage Virtualization Function
Using CCI with the global storage virtualization function To use CCI with the system configuration using the global storage virtualization function, the following two methods can be used. • Specifying a virtual storage machine to HORCM_VCMD in configuration definition files •...
Page 134 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...
Page 135: Machine By Horcm_Cmd
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 specified for HORCM_CMD.
Page 136 #/********** For HORCM_INST ****************/ HORCM_INST #dev_group ip_address service PHOST horcm0 raidqry command display example # raidqry -l No Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB) 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 specified for HORCM_CMD.
Page 137: Specifying A Virtual Storage Machine To Horcm_Vcmd
Specifying a virtual storage machine to HORCM_VCMD This section covers the following topics: • Command operations to the virtual storage machine on page 3-59 • Operation target for raidcom commands when specifying the virtual storage machine in HORCM_VCMD on page 3-61 Command operations to the virtual storage machine When HORCM starts, CCI obtains the virtual storage machine information from multiple storage systems, and configure each virtual storage machine...
Page 138 HORCM_CMD, do not specify the -v jnl and -v pid option. horcctl Specify VSP G1000, VSP G1500, VSP F1500, If you specify the VSP G200, G400, G600, G800, or VSP F400, virtual storage F600, F800 information. machine information, error (No such control device) occurs.
Page 139: Operation Target For Raidcom Commands When Specifying The Virtual Storage Machine In Horcm_Vcmd
How to issue the command to the virtual Commands Remarks storage machine raidcom Specify the virtual storage machine by the When you specify a command option (-s <seq#> or -u <unit volume that belongs ID>). to meta_resource for HORCM_CMD, if you The virtual storage machine can be specified specify the virtual regardless of the description contents of the...
Page 140 VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models, the operational target is: VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models for which the virtual storage machine of the first serial number specified in HORCM_VCMD is defined.
Page 141 Operation targets according to the Commands type definition of HORCM_VCMD raidcom get hba_wwn VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models raidcom add hba_wwn VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models...
Page 142 Operation targets according to the Commands type definition of HORCM_VCMD raidcom add ldev VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models raidcom delete ldev VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models...
Page 143 Operation targets according to the Commands type definition of HORCM_VCMD raidcom modify initiator_chap_user VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models raidcom discover external_iscsi_name VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models...
Page 144 Operation targets according to the Commands type definition of HORCM_VCMD raidcom add rcu_iscsi_port VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models raidcom delete rcu_iscsi_port VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models...
Page 145 Virtual storage machine raidcom modify snapshot Virtual storage machine Server raidcom get spm_wwn VSP G1000, VSP G1500, VSP F1500, VSP Priority Gx00 models, or VSP Fx00 models Manager raidcom get spm_group VSP G1000, VSP G1500, VSP F1500, VSP...
Page 146: Horcm_Cmd
Operation Operation targets according to the Commands type definition of HORCM_VCMD raidcom get local_replica_opt VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, or VSP Fx00 models Quorum raidcom get quorum VSP G1000, VSP G1500, VSP F1500, VSP disk Gx00 models, or VSP Fx00 models...
Page 147: Starting Up Cci
Starting up CCI You can begin using the CCI software after you have installed the CCI software, set the command device, created the configuration definition file(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.
Page 148: Starting Up On Unix Systems
Starting up on UNIX systems One instance To start up one instance of CCI on a UNIX system: Modify /etc/services to register the port name/number (service) of each configuration definition file. Make the port name/number the same on all servers: horcm xxxxx/udp xxxxx = the port name/number for horcm.conf If you want CCI to start automatically each time the system starts up,...
Page 149: Starting Up On Windows Systems
For C shell: # setenv HORCMINST X Set the log directory (HORCC_LOG) in the command execution environment as needed. 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.
Page 150: Starting Up On Openvms Systems
xxxxx = the port name/number of horcm0.conf horcm1 xxxxx/udp xxxxx = the port name/number of horcm1.conf If you want CCI to start automatically each time the system starts up, add \HORCM\etc\horcmstart 0 1 to the system automatic startup file (for example, \autoexec.bat). Execute the horcmstart script manually to start CCI: D:\HORCM\etc>...
Page 151 independent process to the terminal LOGOFF, use the "RUN /DETACHED" command. Confirm the configuration. 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.
Page 152: Starting Cci As A Service (Windows Systems)
independent process to the terminal LOGOFF, use "RUN /DETACHED" command. Set the HORCM instance numbers in the environment in which the command is to be executed: $ HORCMINST:=X X = instance number (0 or 1) Confirm the configuration using a CCI command. Set the log directory (HORCC_LOG) in the command execution environment as required.
Page 153 :[2] set a user account to this service. :[3] confirm to start using horcmstart 0. :[4] confirm to stop using horcmshutdown 0. :[5] start as a service by net start HORCM0. Starting CCI as a service Registering 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"...
Page 154 Starting up CCI Command Control Interface User and Reference Guide...
Page 155: Provisioning Operations With Cci
Provisioning operations with CCI This chapter describes storage provisioning operations with CCI. □ About provisioning operations □ Available provisioning operations □ Provisioning operations that can be performed on device groups □ Workflow for performing provisioning operations □ Resource group operations □...
Page 156: About Provisioning Operations
• Hitachi Virtual Storage Platform G200, G400, G600, G800 • Hitachi Virtual Storage Platform F400, F600, F800 • xHitachi Virtual Storage Platform G1000, G1500, and Hitachi Virtual Storage Platform F1500 • Hitachi Virtual Storage Platform • Hitachi Unified Storage VM For details about the provisioning operations, see the Provisioning Guide for the storage system.
Page 157: Synchronous Command Processing
Figure 5-1 Synchronous and asynchronous command processing The processing difference between these two command types are described Synchronous command processing on page 5-3 Asynchronous command processing on page 5-3. 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.
Page 158: Workflow For Executing Asynchronous Commands
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.
Page 159 Function Command syntax Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, active flash for mainframe, or Copy-on-Write Snapshot Deleting virtual volume for Dynamic raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group Provisioning, Dynamic Provisioning option> -device_grp_name <device group name> [<device for Mainframe, Dynamic Tiering, name>] } [-operation initialize_capacity_saving] active flash, Dynamic Tiering for...
Page 160: Help On Configuration Setting Commands
Function Command syntax Deleting the external path raidcom delete path -path_grp <path group#> -port <port#> - external_wwn <wwn strings> Releasing the mapping of external raidcom delete external_grp -external_grp_id <gno-sgno> [- volume forcible] Stopping the use of paths to the raidcom disconnect path -path_grp <path group#> -port <port#> external volume -external_wwn <wwn strings>...
Page 161 Operation type Description Corresponding command Unlock resource. raidcom unlock resource -resource_name <resource group name > Display resource group raidcom get resource information. 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>...
Page 162 Operation type Description Corresponding command {enable|disable}] [- accelerated_compression {enable| disable}] [- clpr <clpr#>] Delete a parity group. raidcom delete parity_grp -parity_grp_id <gnosgno> Define SSID. raidcom add ssid -rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid> raidcom delete ssid -rcu <serial#> <mcu#> <rcu#> -ssid <ssid>...
Page 163 Operation type Description Corresponding command Change the pool for HDP raidcom modify pool -pool {<pool ID#> | <pool to the pool for HDT. naming>} -pool_attribute dt_manual Change the pool for HDT raidcom modify pool -pool {<pool ID#> | <pool to the pool for HDP. naming>} -pool_attribute dp Set the newly allocation raidcom modify pool -pool {<pool ID#>...
Page 164 Operation type Description Corresponding command -device_grp_name <device group name> [<device name>]}[-user_threshold <%> ] Start or stop the raidcom monitor pool -pool {<pool ID#> | <pool performance monitor for naming>} -operation <type> HDT, HDTz, active flash, or active flash for mainframe. Start or stop the tier raidcom reallocate pool -pool {<pool ID#>...
Page 165 Operation type Description Corresponding command Change cache mode of raidcom modify external_grp -external_grp_id <gno- external volume. sgno> -cache_mode < y|n > Control cache write of raidcom modify external_grp -external_grp_id <gno- external volume. sgno> -cache_inflow < y|n > Modify ownership MP raidcom modify external_grp -external_grp_id <gno- Blade of external volume.
Page 166 Operation type Description Corresponding command Device Create device group. raidcom add device_grp -device_grp_name <ldev group group name> <device name> -ldev_id <ldev#>… [- cnt <count>] Delete LDEV from device raidcom delete device_grp -device_grp_name group. <device group name> -ldev_id <ldev#>… [-cnt <count>] Display device group raidcom get device_grp [-device_grp_name <device information.
Page 167: Provisioning Operations That Can Be Performed On Device Groups
Operation type Description Corresponding command Display journal raidcom get journal [ -key <keyword>]raidcom get information. 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.
Page 168: Operation Method
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.
Page 169: Workflow For Performing Provisioning Operations
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.
Page 170: Resource Group Operations
Step Description Command Unlock the resource group. raidcom unlock resource -resource_name <resource group name> Display the resource group raidcom get resource information to confirm the operations and lock information. Log out. raidcom -logout Resource group operations Creating resource groups To create resource groups, perform the following provisioning operations. Step Operation Description...
Page 171: Allocating Resources To Other Resource Groups
Step Operation Description Command allocation of resources to the resource group: meta_resource must be finished. Deleting Deletes resource groups. raidcom delete resource -resource_name <resource resource group name> groups Displaying Displays resource group raidcom get resource resource group information and confirms information results of command executions.
Page 172: Execution Example
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 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.
Page 173 Step Operation Description Command topology and data transfer speed as needed. Creating host Specify port and create host raidcom add host_grp -port <port#> -host_grp_name group group. <host group name> Setting host Specify port and set host mode raidcom modify host_grp -port <port#>...
Page 174: Script Examples (Open Systems)
Script examples (open systems) The following shows script examples of virtual volume (Dynamic Provisioning) operation. Figure 5-2 Script examples of virtual volume operation (Dynamic Provisioning) (1/3) 5-20 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 175 Figure 5-3 Script examples of virtual volume operation (Dynamic Provisioning) (2/3) 5-21 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 176: Creating Internal Volumes (Mainframe Volume)
Figure 5-4 Script examples of virtual volume operation (Dynamic Provisioning) (3/3) Creating internal volumes (Mainframe volume) To create LDEVs of internal volumes (Mainframe volume) and make the LDEVs available to the host, perform the following provisioning operations. Step Operation Description Command SSID settings Configures the SSID...
Page 177: Script Examples
Step Operation Description Command Displaying a Displays an information of raidcom get ldev -ldev_id <ldev#> … [-cnt <count>] LDEV created LDEV, and [-key <keyword>] information confirms an execution result of the command. Script examples The following shows the script examples of internal volume (mainframe volume) operations.
Page 178 Figure 5-5 Script examples of internal volume (Mainframe volume) operation 5-24 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 179: Script Examples
Script examples The following shows script examples for internal open-system volume operations. Figure 5-6 Script examples of internal open-system volume operation (1/2) 5-25 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 180: Virtual Volume (Dynamic Provisioning) Operations
Figure 5-7 Script examples of internal open-system volume operation (2/2) 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. Operation Step Description...
Page 181 Operation Step Description Executed command overview Creating host Specify port and create host raidcom add host_grp -port <port#> -host_grp_name group group. <host group name> Setting host Specify port and set host mode raidcom modify host_grp -port <port#> [<host mode for host group. group name>] -host_mode <host mode>...
Page 182: Script Examples
Operation Step Description Executed command overview <threshold_1> [<threshold_2>]] Creating LDEV Specify pool and create an raidcom add ldev -pool {<pool ID#> | (V-VOL) LDEV(V-VOL). <pool naming> | snap} -ldev_id <ldev#> {-capacity <size> | -offset_capacity <size> | -cylinder <size>} [-emulation <emulation type>][-location <lba>] [-mp_blade_id <mp#>] Creating LDEV...
Page 183 Figure 5-8 Script examples of virtual volume operation (Dynamic Provisioning) (1/3) 5-29 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 184 Figure 5-9 Script examples of virtual volume operation (Dynamic Provisioning) (2/3) 5-30 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 185: Raidcom Delete Ldev Command To Delete A Virtual Volume
Figure 5-10 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: •...
Page 186: Volume
# 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.
Page 187: Virtual Volume (Dynamic Provisioning For Mainframe) Operations
[-cnt <count>] LDEV created LDEV, and confirms an [-key <keyword>] information execution result of the command. Creating the Creates the pool for the Hitachi raidcom add dp_pool {{-pool_id <pool ID#> pool (for the Dynamic Provisioning for [-pool_name <pool Hitachi mainframe.
Page 188: Script Examples
Operation Step Description Executed command overview Creating LDEV Specifies the pool and creates raidcom add ldev -pool {<pool ID#> | <pool (V-VOL) LDEV (V-VOL). naming> | snap} -ldev_id <ldev#> {-capacity <size> | -offset_capacity <size> | -cylinder <size>} [-emulation <emulation type>][-location <lba>] [-mp_blade_id <mp#>] Creating LDEV Creates LDEV (V-VOL)
Page 189 Figure 5-11 Script examples of virtual volume operation (Dynamic Provisioning for Mainframe) (1/2) 5-35 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 190: Virtual Volume (Dynamic Tiering) Operations
Figure 5-12 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.
Page 191 5-37 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 192: Creating Virtual Volumes (Dynamic Tiering)
The virtual volume management area is created automatically when cache memory is added. For information about adding cache memory, please contact Hitachi Data Systems customer support. Caution: The operations explained here are executable by the storage administrator only.
Page 193 Operation Step Description Executed command overview <size> | -cylinder <size>} [- emulation <emulation type>][- location <lba>] [-mp_blade_id <mp#>] Formatting Format created LDEV. raidcom initialize ldev -ldev_id LDEV <ldev#> -operation <type> Creating LDEV Create LDEV nickname. raidcom modify ldev -ldev_id nickname <ldev#>...
Page 194: Script Examples
Operation Step Description Executed command overview Setting MP Set MP blade of created LDEV raidcom modify ldev -ldev_id blade of LDEV (V-VOL). <ldev#> -mp_blade_id (V-VOL) <mp#> Displaying Display information of created raidcom get ldev -ldev_id LDEV (V-VOL) LDEV (V-VOL) and confirm the <ldev#>...
Page 195 Figure 5-13 Script examples of virtual volume operation (Dynamic Tiering) (1/3) 5-41 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 196 Figure 5-14 Script examples of virtual volume operation (Dynamic Tiering) (2/3) 5-42 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 197: Configuring Iscsi Virtual Ports
Figure 5-15 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. 5-43 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 198: Setting An Iscsi Virtual Port
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. 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...
Page 199: External Volume Operations
# 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 Disable the virtual port mode for the iSCSI port (CL4-E). # raidcom modify port -port CL4-E -iscsi_virtual_port_mode disable Confirm that the virtual port mode is disabled ( ISCSI_VP_MODE : D).
Page 200 Operation Step Description Executed command overview < y|n > | -mp_blade_id <mp#>} Checking Display external volume raidcom get external_grp [-external_grp_id external information and confirm result <gno-sgno>] volume of executing command. information Setting Set external path. Execute the raidcom add path -path_grp <path group#>...
Page 201: Creating External Volumes (Iscsi)
Operation Step Description Executed command overview Setting MP Set MP blade of created LDEV. raidcom modify ldev -ldev_id <ldev#> blade of LDEV -mp_blade_id <mp#> Displaying Display information of created raidcom get ldev -ldev_id <ldev#> … [-cnt <count>] LDEV LDEV and confirm the result of [-key <keyword>] information executing the command.
Page 202 Operation Step Description Executed command overview information for storage systems, set the CHAP -iscsi_name <external iscsi name> connecting to user name and a password -address <external IP the iSCSI (secret) used by the External address> target of an (ELUN) port of the local [-chap_user <user name>...
Page 203 Operation Step Description Executed command overview Checking Display external volume raidcom get external_grp [-external_grp_id <gno- external information and confirm the sgno>] volume result of executing the information command. Setting Set external path. Execute the raidcom add path -path_grp <path group#> external path required number of commands.
Page 204: Script Examples
Operation Step Description Executed command overview [-location <lba>] [-mp_blade_id <mp#>] Setting LDEV Set a nickname of the created raidcom modify ldev -ldev_id <ldev#> nicknames LDEV. -ldev_name <ldev naming> (arbitrary) This operation is arbitrary. Setting the MP Set the MP blade of the created raidcom modify ldev -ldev_id <ldev#>...
Page 205 Figure 5-16 Script Examples of External Volume Operation (1/3) 5-51 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 206 Figure 5-17 Script Examples of External Volume Operation (2/3) 5-52 Provisioning operations with CCI Command Control Interface User and Reference Guide...
Page 207: Virtual Partition Manager Operations
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 Performance Guide for VSP. •...
Page 208: Displaying Clpr Information
Operation Step Description Command overview Confirming the CLPR Check the status of raidcom get clpr configuration. the CLPRs. Migrating one of the Specify the LDEV raidcom modify clpr -clpr <clpr#> { -ldev_id <ldev#> | following to other number, parity group -parity_grp_id <gno-sgno>...
Page 209: Checking Result Of Clpr Transfer
distributed parity group have to be allocated the same CLPR. Parity groups including LDEVs where cache area of Cache Residency is defined 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.
Page 210: Configuring Server Priority Manager By Specifying Ports And Wwns Of Hbas
For details, see Configuring Server Priority Manager by specifying LDEVs and WWNs or iSCSI names of HBAs on page 5-66. 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.
Page 211: Using And Managing Server Priority Manager
Priority Server performance If the amount of traffic 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.
Page 212: Setting Spm Names For Wwns And Registering Them To The Spm Group
Setting SPM names for WWNs and registering them to the SPM group The following figure shows the workflow of setting SPM names for WWNs and registering them in the SPM group. 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.
Page 213 Table 5-4 Controlling server performance when the host group is not registered in the SPM group Operation Description Executed command overview Setting the Set the priority raidcom modify spm_wwn -port <port#> [-spm_priority <y/n>] {-limit_io | (prioritized or non- -limit_kb | -limit_mb } <value> {- information prioritized option) for hba_wwn <wwn_strings>...
Page 214 Operation Description Executed command overview limit value prioritized WWN by of the non- specifying WWN or prioritized the SPM name. Change the threshold raidcom modify spm_group -port <port#> [-spm_priority <y/n>] {-limit_io | or the upper limit -limit_kb | -limit_mb } <value> - value of the non- spm_group <group_name>...
Page 215 Operation Description Executed command overview Specify the host raidcom get spm_group -port <port#> [<host group name>] -spm_host_grp group to display the SPM setting status. Specify the SPM raidcom get spm_group -port <port#> -spm_group <group_name> group name to display the SPM setting status.
Page 216 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.
Page 217: Cautions About Using Server Priority Manager
time. You can also set the same upper limit value for all host bus adapters in an SPM group at the same time. Examples of setting the SPM group: 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 Set the WWN (210000e08b039c15) for the SPM gropup name...
Page 218 • VSP Gx00 models and VSP Fx00 models: Adding, replacing, or removing front-end module (CHB) • VSP G1000, VSP G1500, VSP F1500: Replacing MP blades • VSP G1000, VSP G1500, VSP F1500: Adding, replacing, or removing front-end directors (CHAs) •...
Page 219 WWN or iSCSI defined by IEEE) is specified. name of LDEVs In VSP G1000, VSP G1500, VSP F1500, if you specify SPM information and HBAs: for an invalid WWN, you might not be able to set SPM information with Invalid WWNs an iSCSI name specified.
Page 220 You cannot register host groups in SPM groups in which WWNs (SPM targets) are registered in step 3 of Table 5-4 Controlling server performance when the host group is not registered in the SPM group on page 5-59. You can register host groups described in limitation 1 above in SPM groups that were not specified in step 3 of Table 5-3 if the WWNs that belong to the host group meet the following requirements: •...
Page 221 Item Range Number of WWNs that can be registered for each 1 to 2,0482 storage system Number of iSCSI names that can be registered 1 to 2,0482 for each storage system Number of WWNs that can be registered for each 1 to 32 LDEV Number of iSCSI names that can be registered...
Page 222: Virtual Storage Machine Operations
Table 5-7 Server Priority Manager operations when an LDEV and a WWN or iSCSI name of an HBA is specified Operation Description Executed command overview Setting SPM Specify the LDEV number, and the raidcom modify spm_ldev -ldev_id <ldev#> {-hba_wwn <wwn strings> | information for an WWN or iSCSI name of the host bus -hba_iscsi_name <initiator iscsi...
Page 223: Adding Ldevs To A Virtual Storage Machine
Operation Description Executed command overview Reserving host Reserve ports and host group raidcom add resource -resource_name <resource group IDs IDs to the resource groups in group name> the virtual storage machine. -port <port#> -<HG#> Be sure to execute the command before creating host groups.
Page 224: Removing The Virtual Storage Machine
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. Operation Description Executed command overview Remove the LU Remove the LU path from the raidcom delete lun -port <port#>...
Page 225: Data Replication Operations With Cci
Data replication operations with CCI This chapter describes data replication operations with CCI. □ About data replication operations □ Features of paired volumes □ Using CCI with ShadowImage and TrueCopy □ Using CCI with Thin Image □ Using CCI with global-active device □...
Page 226: About Data Replication Operations
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). Data replication operations with CCI...
Page 227: Using Cci With Shadowimage And Truecopy
Figure 6-1 Concept of paired volumes Addressing paired logical volumes: The correspondence of paired logical volumes to their physical volumes is defined by describing the paired logical volume names and group names in the configuration definition files of each server. It is possible to define a server for the paired logical volumes in units of group name.
Page 228: Using Cci With Thin Image
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”...
Page 229: Using Cci With Global-Active Device
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.
Page 230: Shadowimage Duplicated Mirroring
• 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.
Page 231: Shadowimage Cascading Pairs
Figure 6-3 ShadowImage duplicated mirrors ShadowImage cascading pairs ShadowImage provides a cascading function for the ShadowImage S-VOL. Cascading mirror volumes can be specified 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 configuration diagram as shown below.
Page 232: Restrictions For Shadowimage Cascading Volumes
Figure 6-4 ShadowImage cascade volume pairs 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 first without creating the oradb, the subsequent oradb creation will be rejected with EX_CMDRJE or EX_CMDIOE.
Page 233: Restriction For Truecopy/Shadowimage Cascading Volumes
the S/P-VOL (oradb) is in a COPY or PAIR state, the pairsplit command is rejected with EX_CMDRJE or EX_CMDIOE. 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.
Page 234: Truecopy Takeover Commands
Note: For information about the operational requirements and specifications for TrueCopy, please see the Hitachi TrueCopy® User Guide for your storage system. TrueCopy takeover commands Figure 6-5 Server failover system configuration on page 6-10 illustrates a high-availability (HA) environment.
Page 235 • Script: Shell script that automatically performs takeover process when CM detects the server failure. 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...
Page 236: Takeover-Switch Function
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.
Page 237: Swap-Takeover Function
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.
Page 238: Svol-Takeover Function
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 (specified 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.
Page 239: Pvol-Takeover Function
Caution: The SVOL-takeover operation is required to copy Nontransmitted P- VOL data within a given timeout value (specified 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.
Page 240 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 configurations and to restore the volumes to their original state after a server failover has been recovered.
Page 241: Truecopy Local Commands
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 Figure 6-8 TrueCopy local system configuration on page 6-17 illustrates a...
Page 242: Truecopy/Shadowimage/Universal Replicator Pair Status
ShadowImage pairs are contained within the same storage system and are maintained using asynchronous update copy operations. For details on ShadowImage specifications 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 configuration file.
Page 243 • Table 6-5 Pair status versus ShadowImage commands on page 6-22 shows the relationship between pair status and ShadowImage command acceptance. • Table 6-6 Pair status versus Copy-on-Write Snapshot commands on page 6-24 shows the relationship between pair status and Copy-on-Write Snapshot command acceptance.
Page 244 Table 6-3 Universal Replicator pair status Status Universal Replicator Pair Status Primary Secondary SMPL Unpaired volume R/W enabled R/W enabled PAIR The pair is synchronized. Updates to the P-VOL are R/W enabled R enabled duplicated on the S-VOL. COPY In paired state, but initial copy, pairsplit, or resync R/W enabled R enabled operation is not complete.
Page 245 Status Universal Replicator Pair Status Primary Secondary • SSWS is displayed by CCI, from which the horctakover command is issued. • Storage Navigator displays this status as PSUS or PSUE. PFUL If data in the journal volume exceeds 80%, pair status R/W enabled R enabled changes to PFUL.
Page 246 Table 6-5 Pair status versus ShadowImage commands ShadowImage command paircreate pairsplit pairresync Pair Status No -split -split -E option -C option -S option Resync SMPL Accepted 2 Accepted 2 Rejected Rejected Acceptable Rejected to 4 COPY Acceptable Accepted [1] Accepted 5 Accepted [1] Accepted 1 Acceptable...
Page 247 • If you attempt to read non-reflected data on S-VOL in PVOL_PSUS & SVOL_COPY state, then ShadowImage copies non-reflected 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.
Page 248 unable to perform. In this case, you need to wait until the S-VOL state becomes SVOL_SSUS. Table 6-6 Pair status versus Copy-on-Write Snapshot commands Copy-on-Write Snapshot Command Pair Status paircreate pairsplit pairresync No -split -split -E option -C option -S option Resync SMPL Accepted 2...
Page 249 Figure 6-9 TrueCopy Async consistency groups Restrictions • Group definition of TrueCopy Async/Universal Replicator/TrueCopy/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 ID), then pair operation of the group specification is handled in consistency group entirety.
Page 250 TrueCopy, 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. Table 6-7 Assignment of consistency group IDs (CTG IDs) CTG ID Assignment 0 -127 TrueCopy Asynchronous CTG 0-127 TrueCopy...
Page 251: Sidefile Cache For Truecopy Async
Sidefile cache for TrueCopy Async The first-in-first-out (FIFO) queue of each consistency group is placed in an area of cache called the sidefile. The sidefile is used for transferring TrueCopy Async recordsets to the RCU. The sidefile is not a fixed area in cache but has variable capacity for write I/Os for the primary volume.
Page 252 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...
Page 253: Truecopy Async/Universal Replicator Error State
Writing control on TC Storage Description Transfer async volume system data via state internal TrueCopy Writing ESCON TrueCopy Async Response state Sync data Deleting Deleting from PAIR using Normal Usual Sidefile [pairsplit -S] Suspending Suspending Using Via Bitmap Usual Sidefile from PAIR [pairsplit ] Timeout of...
Page 254: Settings
Figure 6-11 TrueCopy Async suspension condition TrueCopy/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.
Page 255 Table 6-9 Relationship between TrueCopy pair statuses and fence levels Fence level and write response TrueCopy pair status of volume Data [1] Status [2] Never [3] Async [4] Mirroring Mirroring Mirroring Data consistency consistency consistency consistency assured assured assured assured ERROR Mirroring Mirroring...
Page 256: Setting The Fence Level
Fence level and write response TrueCopy pair status of volume Data [1] Status [2] Never [3] Async [4] transfer. Due to the use of a bitmap in the suspend state, data consistency is not assured during a copy state resync. •...
Page 257: Copy-On-Write Snapshot Operations
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.
Page 258: Pair Operations And Commands For Copy-On-Write Snapshot And Thin Image
For details on Thin Image or Copy-on-Write Snapshot specifications such as maximum number of mirrored volumes, volumes and operations, please see the Hitachi Thin Image User Guide or Hitachi Copy-on-Write Snapshot User Guide for your storage system. Pair operations and commands for Copy-on-Write Snapshot and Thin...
Page 259: Copy-On-Write Snapshot Pair Status
A Copy-on-Write Snapshot pair is generated in the following two cases: • When a V-VOL (OPEN-0V) is specified as an S-VOL. • When a pool for Copy-on-Write Snapshot is specified as the pool type. A V-VOL has the following characteristics: •...
Page 260: Pair Status Relationship To Copy-On-Write Snapshot Commands
P-VOL Pairing Status Primary Secondary Status PSUE "PSUS" status due to an internal failure. The R/W disable R/W enabled (Error) differences of the updated data for the Copy- on-Write Snapshot volume are not controlled. Notes: 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.
Page 261: Controlling Volume Migration
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.
Page 262 migrated from P-VOL to S-VOL, and the mapping between LDEV and VDEV is swapped after copied. (2) Mapping specification 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.
Page 263: Commands To Control Volume Migration
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 specified for ShadowImage) This option is used to specify the Volume Migration mode.
Page 264 CL1-A-0 9 62496 21 SMPL 30053 CL1-A-0 10 62496 22 SMPL 30053 E-Seq#: Displays the production (serial) number of the external LUN. E- LDEV#: Displays the LDEV# of the external LUN. (3) Command for confirming the status It is possible to confirm the status for Volume Migration by using "-fe" option of the pairdisplay command.
Page 265 Example in Linux: # ls /dev/sd* |./inqraid /dev/sdh -> CHNO = 0 TID = 1 LUN = [SQ] CL2-G Ser = 63528 LDEV =15360 [HITACHI ] [OPEN-V HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group...
Page 266: Relations Between "Cc" Command Issues And Status
/dev/sdu -> CHNO = 0 TID = 1 LUN = [[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 ->...
Page 267: Restrictions For Volume Migration
Command: Pair Creation Pair Splitting Pairing Status CC: -m cc Simplex -S (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.
Page 268 • 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.
Page 269 (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 configured in a group.
Page 270: Command Specifications
(1) Defining to control UR MxN CCI supports a way to specify consistency Q-Marker to the specified group by adding "HORCM_CTQM" as a keyword in horcm.conf (see example below). HORCM CTQM #groupinterval (10ms)mode(optional oradb300 where • group is to be allowed as a group across multiple storage systems. •...
Page 271: Pairsplit Command
# pairdisplay -g ora -v ctg Status AP U(%) Q-Marker QM-Cnt SF(%) Seq# IFC OT/s CT/m RT/m P-VOL PAIR 00000032 64034 ON S-VOL PAIR 00000020 64035 - P-VOL PAIR 00000031 64045 ON S-VOL PAIR 00000022 64046 - # pairdisplay -g ora -v jnl JID MU CTG JNLS U(%)
Page 272 • 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 •...
Page 273 (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) •...
Page 274: Notice On System Operation
• 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.
Page 275 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.
Page 276: Configuration Examples
If group (-g <group>) is specified, then the first dev_name on the specified 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). •...
Page 277 (1) UR 2x2 6-53 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 278: Duplication Of Cci Applications
(2) UR 2x1 Duplication of CCI applications Caution: You must read Requirements for duplication of CCI on page 6-57 before you duplicate CCI applications. 6-54 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 279 When a failure occurs on the CCI application (for example, failure of the server on which CCI is installed) in the MxN configuration 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 first CCI application.
Page 280 6-56 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 281: Requirements For Duplication Of Cci
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. 6-57 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 282: Note For Duplication Of Cci
Hitachi Virtual Storage Platform (VSP) ¢ Hitachi Virtual Storage Platform G1000, G1500, and Hitachi Virtual ¢ Storage Platform F1500 (VSP G1000, VSP G1500, VSP F1500) Hitachi Virtual Storage Platform G200, G400, G600, G800 (VSP Gx00 ¢ models) Hitachi Virtual Storage Platform F400, F600, F800 (VSP Fx00 models) ¢...
Page 283: Discovering A Remote Volume
Figure 6-15 Volume discovery 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 file name..". The raidscan -find inst command on CCI server imports the volume information, and registers it into the HORCM daemon.
Page 284 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 LDEV /dev/rdsk/c1t0d2s2 G1-000 CL4-G-1 64015 /dev/rdsk/c1t0d2s2 G1-000 CL4-G-1 64015 /dev/rdsk/c1t0d3s2...
Page 285 # cat /etc/horcmperm*.conf | raidscan -find verify DEVICE_FILE Group PairVol PORT TARG SERIAL LDEV /dev/rdsk/c1t0d0s2 64015 /dev/rdsk/c1t0d1s2 64015 /dev/rdsk/c1t0d2s2 G1-000 CL4-G-1 64015 /dev/rdsk/c1t0d3s2 G1-001 CL4-G-1 64015 /dev/rdsk/c1t0d4s2 64015 /dev/rdsk/c1t0d5s2 64015 /dev/rdsk/c1t0d7s2 64015 6-61 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 286 6-62 Data replication operations with CCI Command Control Interface User and Reference Guide...
Page 287: Data Protection Operations With Cci
Data protection operations with CCI This chapter describes data protection operations using CCI. □ Data protection operations □ Protection parameters and operations □ Data Protection facility Data protection operations with CCI Command Control Interface User and Reference Guide...
Page 288: Data Protection Operations
Data protection operations User data files are normally placed on a disk through a software layer such as a file 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.
Page 289: Restrictions On Data Retention Utility Volumes
Restrictions on Data Retention Utility volumes • File systems using Data Retention Utility When setting DRU to the UNIX file 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.
Page 290: Restrictions On Database Validator
• Data block address corruption: The OS (file 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. •...
Page 291: Protection Parameters And Operations
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 ¢ confirm 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>...
Page 292 Command device setting Group Security to be set User Security information authentication acquisition Only HORCM_DEV allowed User authentication required User authentication required Only HORCM_DEV allowed CMD security CMD security Only HORCM_DEV allowed CMD security User authentication required CMD security User authentication required Only HORCM_DEV allowed Notes: •...
Page 293: Data Protection Facility Specifications
Figure 7-1 Definition of the protection volumes Data Protection Facility specifications Only the permitted volumes can be registered in horcm.conf. When creating the horcm.conf file, describe volumes only from the view that the host shows. CCI manages mirror descriptors (TrueCopy, ShadowImage/ MU#0/1/2) as a unit.
Page 294: Examples For Configuration And Protected Volumes
volumes from horcm.conf and Inquiry result. Inquiry result is based on configuration 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.
Page 295: Operation Authority With Cmd Security Enabled
Figure 7-3 Example for the one-host configuration 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. •...
Page 296: Permission Command
• The pairdisplay command shows all volumes, so that you can confirm non-permitted volumes. Non-permitted volumes are shown without LDEV# information. As shown below, the LDEV# information is " **** " (- CLI is "-"). # pairdisplay -g oradb Group PairVol(L/R) (Port#,TID,LU-M),Seq#, LDEV#.P/S,Status, Seq#,P-LDEV# M oradb...
Page 297: Raidscan -Find Verify [Mu#]
normally need to use this option. This option issues an Inquiry to a device file 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.
Page 298: Pairdisplay -F[D]
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. # pairdisplay -g oradb -fd Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-...
Page 299: Systems
# export HORCC_MRCF=1 # cat /etc/horcmperm.conf | grep vg01 | raidscan -find verify 1 -fd # vgdisplay -v /dev/vg01|grep dsk|sed 's/\/*\/dsk\//\/rdsk\// g'|raidscan -find verify 1 -fd DEVICE_FILE Group PairVol Device_File SERIAL LDEV /dev/rdsk/c0t3d0 oradb1 oradev1 c0t3d0 35013 /dev/rdsk/c0t3d1 oradb1 oradev2 c0t3d1 35013 /dev/rdsk/c0t3d2...
Page 300: Environment Variables
Table 7-3 Without a $HORCMPERM file: Commands to run on different operating systems System Command HP-UX echo /dev/rdsk/* /dev/rdisk/* /dev/rcdisk/* | /HORCM/usr/bin/raidscan - find inst Linux ls /dev/sd* | /HORCM/usr/bin/raidscan -find inst zLinux ls /dev/sd* /dev/dasd*| /HORCM/usr/bin/raidscan -find inst Solaris ls /dev/rdsk/* | /HORCM/usr/bin/raidscan -find inst lsdev -C -c disk | grep hdisk | /HORCM/usr/bin/raidscan -find inst Tru64 UNIX ls /dev/rdisk/dsk* | /HORCM/usr/bin/raidscan -find inst...
Page 301: Horcmperm
$HORCMPERM This variable is used to specify the HORCM permission file name. If no file name is specified, /etc/horcmperm.conf or /etc/horcmperm*.conf (* = instance number) is the default. • If a HORCM permission file exists, then /etc/horcmgr executes the following command to permit the volumes specified. Example for UNIX systems: cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst Example for Windows systems:...
Page 302 7-16 Data protection operations with CCI Command Control Interface User and Reference Guide...
Page 303: Examples Of Using Cci Commands
Examples of using CCI commands This chapter provides examples of typical tasks performed using CCI commands. □ Group version control for mixed storage system configurations □ LDM volume discovery and flushing for Windows □ Special facilities for Windows systems □ Host group control □...
Page 304: Group Version Control For Mixed Storage System Configurations
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 configuration. If the configuration 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.
Page 305: Volume Discovery Function
Figure 8-2 LDM volume configuration 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. •...
Page 306 \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 configured 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.
Page 307: Mountvol Attached To Windows 2012/2008/2003/2000 Systems
E:\Dsk1\p1 CL2-K 61456 s/s/ss 0004 1:01-10 OPEN-3 F:\Dsk1\p2 CL2-K 61456 s/s/ss 0004 1:01-10 OPEN-3 inqraid $Phy -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID Harddisk0 DDRS-34560D Harddisk1 CL2-K 61456 s/s/ss 0005 1:01-11 OPEN-3 You want to know the relationship between LDM volumes and a group of the configuration files, and then find a group of the configuration file by giving a KEY WORD to raidscan -find verify command.
Page 308: System Buffer Flushing Function
raidscan -pi $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -find DEVICE_FILE S/F PORT TARG SERIAL LDEV PRODUCT_ID \Vol46\Dsk1 CL2-K 61456 OPEN-3 System buffer flushing function The logical drive to be flushed can be specified by the following two methods. One method is that the logical drive (for example, G:\hd1 drive, as below) is specified immediately, but this method must know about the logical drive corresponding to a group before executing the sync command.
Page 309 The following example flushes the system buffer associated with all groups for the local instance. 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[-] ->...
Page 310 P-VOL Side S-VOL Side • Unfreeze DB on opening P-VOL by application. • Resynchronize the paired volume using pairresync -g ORB. Offline backup using raidscan -find sync for Windows NT file system: The raidscan -find sync command flushes the system buffer through finding a logical drive corresponding to a group of the configuration file, without using the -x mount and -x umount commands.
Page 311: Special Facilities For Windows Systems
• 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 8-9 •...
Page 312: Gpt Disk For Windows
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. •...
Page 313 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 file provided via STDIN or arguments, and saves it in a system disk file with the following format: \WindowsDirectory\VOLssss_llll.ini where...
Page 314: Directory Mount Facility For Windows Systems
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. C:\HORCM\Tool>inqraid -CLI -gplbaex hd10,13 Harddisk10 : SLBA = 0x0000003f ELBA = 0x013fe5d9 PCNT = 1 [OPEN-V Harddisk11 : SLBA = 0x00000022 ELBA = 0x013fffdf PCNT = 2...
Page 315 ($LETALL)can also be used with the raidscan -find and mkconf commands. 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 s/s/ss 0005 1:01-01 OPEN-3 D:\hd2\Vol9\Dsk1 CL2-F 61459 s/s/ss 0005 1:01-01 OPEN-3 G:\Dms1\Dsk2 CL2-K 61456 s/s/ss...
Page 316: Host Group Control
Note: This prevents the forcible removal of a volume due to LOG-OFF of Windows. For example: C:\HORCM\etc>raidscan -x mount E:\ Volume{cec25efe-d3b8-11d4- aead-00c00d003b1e} E:\ <+> HarddiskVolume3 • 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 specified, then it is executed by converting a ¢...
Page 317: Commands And Options Including A Host Group
CL1-A 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) Specifiable command for host group The following commands can specify a host group with the port strings: •...
Page 318: Using Cci Slpr Security
#dev_group dev_name port# TargetID # /dev/rdsk/c57t4d1 SER = 62500 LDEV = 257 [ FIBRE FCTBL = 4 ] ORA_000 CL2-D-1 # /dev/rdsk/c57t4d2 SER = 62500 LDEV = 258 [ FIBRE FCTBL = 4 ] ORA_001 CL2-D-1 • inqraid -fg # ls /dev/rdsk/c57* | ./inqraid -CLI -fg DEVICE_FILE PORT SERIAL...
Page 319: Specifying The Slpr Protection Facility
Figure 8-6 Protection of the command device that has the SLPR attribute 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.
Page 320: Slpr Configuration Examples
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.
Page 321 Figure 8-8 Operation across SLPRs using two command devices on a single host 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.
Page 322 both Hosts), is unable to scan a port because the specified port is different than the SLPR of the command device. Figure 8-10 SLPR configuration on dual hosts 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 specified port is different than the SLPR of the command device.
Page 323 because the shared command device has the Bitmap settings SLPR#M and SLPR#N. Figure 8-12 Operating SLPR#N by sharing the command device 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.
Page 324 8-22 Examples of using CCI commands Command Control Interface User and Reference Guide...
Page 325: Troubleshooting
Troubleshooting This chapter provides troubleshooting information for CCI. □ General troubleshooting □ Operational notes and restrictions for CCI operations □ Error messages and error codes □ Calling Hitachi Data Systems customer support Troubleshooting Command Control Interface User and Reference Guide...
Page 326: General Troubleshooting
General troubleshooting If you have a problem with the CCI software, first 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 CCI currently uses the ioctl(SCSI_IOCTL_SEND_COMMAND) for SCSI ioctl sending the control command to the command device.
Page 327: Operational Notes And Restrictions For Cci Operations
Problem Recommended action HORCM_LOG (the default setting: /horcm/log/), and then contact Hitachi Data Systems customer support. The following These messages are output if the path for the PA-RISC version shared messages are library (libcl.sl) is not set when you use CCI on HP-UX (IA64).
Page 328 Items Notes and restrictions Hot standby Note the following when executing hot standby operations using operations 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 different server programs.
Page 329 Items Notes and restrictions Linkage with HA The HORC Manager must not be an object of the process monitoring software 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.
Page 330: Error Messages And Error Codes
If HORCM has shut down, restart HORCM. If an unrecoverable error occurs, obtain the log files and contact Hitachi Data Systems customer support. Error in paired TrueCopy only: If an error occurs in duplicated writing in paired...
Page 331 HORCM_004 HORCM assertion An internal error that could Restart the system, and contact failed, resulting in a not be identified by the Hitachi Data Systems customer fatal internal error in HORCM occurred. support. the HORCM. HORCM_005 The CCI software...
Page 332: Command Error Messages
Manager capacity has 3000 KB or more free space. Free up disk space, and then restart HORCM. If the problem persists, contact Hitachi Data Systems customer support. EX_REQA Required An option or arguments of...
Page 333 Please designate the correct name using name of argument of an option is not the -h option. option appropriate. EX_OPTI Detected contradiction in Contact Hitachi Data Systems customer specified information that RAID support. option is reported. invalid EX_ENOE No such...
Page 334 EX_UNW Unknown Detected a contradiction for Retry your operation after restart of the function a command. instance for CCI. Contact Hitachi Data code Systems customer support if the operation fails because of same error again. EX_CMDI Control...
Page 335 If the phenomenon happens again, contact Hitachi Data Systems customer support. • Other than above: Contact Hitachi Data Systems customer support. If the problem persists, contact Hitachi Data Systems customer support. 9-11 Troubleshooting Command Control Interface User and Reference Guide...
Page 336 WAIT volume, before it made it to volume to try to recover it. state the designated status. If the problem persists, contact Hitachi Data Systems customer support. EX_EWST Timeout Detected a time out, before Please increase the value of the timeout...
Page 337 LUN and target ID definition file. within the RAID storage system. EX_INVR Invalid Wrong return code. Contact Hitachi Data Systems customer return support. code EX_VOLC S-VOL Currency check error for S- Check the volume list to see if an currency VOL.
Page 338 Error Error Returne Condition Recommended action code message d Value definition file found at step 2 (split the pair). 4. Delete the dev_group which matches the consistency group to be deleted from the configuration definition file found in step 2 (delete both P-VOL and S-VOL which configures the split pair).
Page 339 Error Error Returne Condition Recommended action code message d Value 2. Find the configuration definition file 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 configuration definition file found at step 2 which matches the consistency group to which the pair...
Page 340 Error Error Returne Condition Recommended action code message d Value EX_ENQC Unmatche The consistency group Please confirm the CTG ID using the d CTGID references within a group do pairvolchk command and confirm that within the not have an identical CTG group references within the group configuration definition file...
Page 341 Error Error Returne Condition Recommended action code message d Value • The attribute of the port is not Target (TAR) or RCU Target (RCU). • LUN security is invalid. • The specified host group is not installed. • The specified virtual port ID is not correct.
Page 342: Generic Error Codes (Horctakeover And Pair Commands)
[EW_UN option. option. WOPT] Unknown option EW_SYSE System An invalid internal error has Contact Hitachi Data Systems customer error detected. support. EW_ENO Memory to execute a Add more virtual memory of a whole enough command cannot be system, or terminate unnecessary core allocated in HORCM.
Page 343 Table 9-3 Generic error codes (horctakeover and pair commands) Retur Category Error code Error message Value Syntax for Argument EX_REQARG Required Arg list (Unrecoverable) EX_INVARG Invalid argument EX_INVNAM Invalid name of option EX_UNWOPT Unknown option EX_UNWCOD Unknown function code EX_UNWCMD Unknown command EX_ERANGE Result too large...
Page 344: Generic Error Codes (Raidscan, Raidqry, Raidar, Horcctl)
Retur Category Error code Error message Value Resource EX_ENOMEM Not enough core (Unrecoverable) 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"...
Page 345: Specific Error Codes
Category Error code Error message Value EX_INVCMD Invalid RAID command Communication for EX_ATTHOR Can't be attached to HORC manager HORCM EX_ATTDBG Can't be attached to a Debug layer (Recoverable) EX_COMERR Can't be communicated with HORC manager Resource EX_ENOMEM Not enough core (Unrecoverable) Specific error codes The following table lists the specific error codes returned by the following...
Page 346: Ssb Codes
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 Hitachi TrueCopy® • pairresync 9-22 Troubleshooting Command Control Interface User and Reference Guide...
Page 347 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 Hitachi Data Systems customer support. Table 9-6 SSB codes returned by the paircreate command paircreate...
Page 348: Ssb Codes Returned By The Configuration Setting Command (Raidcom)
The following tables provide information about each SSB code returned by the configuration setting command (raidcom command). If you see an error not described in the tables, contact Hitachi Data Systems customer support. Table 9-9 SSB codes returned by the configuration setting command (common)
Page 349 common Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 350 Table 9-10 SSB codes returned by raidcom add external_grp raidcom add external_grp Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 000D Invalid emulation type. Get Command Async 2E00 0013 There are not enough cache management devices. Status CMDRJE Executing...
Page 351 raidcom add external_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 4106 The specified external LU cannot create a external Status volume because the transition of data is required. Get Command Async 2E11 4200 The specified path group cannot be operated Status because a path between other devices exists.
Page 352 raidcom add external_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E31 4000 The specified external storage LU is the device of Status not supported. Get Command Async 2E31 4001 The specified external storage system is not Status supported.
Page 353 Error code Executing/ Error message Description Async SSB1 SSB2 Call Hitachi Data Systems customer support. CMDRJE Executing 2EDA 0905 An internal error occurred by the operation of external volume. Call Hitachi Data Systems customer support. Table 9-12 SSB codes returned by raidcom delete external_grp...
Page 354 raidcom delete external_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E30 4102 The external volume is used as a TrueCopy pair Status volume. Get Command Async 2E30 4103 The external volume is used as a TrueCopy pair Status volume.
Page 355 SSB1 SSB2 Get Command Async 2EE8 FFFB An internal error occurred. Status Call Hitachi Data Systems customer support. Get Command Async 2EFF 41FF An internal error occurred. Status Call Hitachi Data Systems customer support. Table 9-13 SSB codes returned by raidcom check_ext_storage path...
Page 356 Get Command Async 2EDA 0905 An internal error occurred by the operation of Status external path. Call Hitachi Data Systems customer support. CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS platform (System LU).
Page 357 Executing 2E20 4300 There is no specified path. CMDRJE Executing 2E30 000A It is included the Hitachi Dynamic Provisioning volume that is associated with a pool. CMDRJE Executing 2E30 000C The specified LDEV is used as a quorum disk. CMDRJE...
Page 358 CMDRJE Executing 2EDA 0000 An internal error occurred by the operation of disconnecting the external volume. Call Hitachi Data Systems customer support. CMDRJE Executing 2EDA 0905 An internal error occurred by the operation of external volume.
Page 359 CMDRJE Executing 2EDA 0905 An internal error occurred on the changing of an external volume option. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 0002 The specified parameter is incorrect. Check the Command Control Interface Command Reference.
Page 360 raidcom modify port -loop_id Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 054E The specified topology is invalid. CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet.
Page 361 raidcom modify port -topology Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 040F An internal error occurred. CMDRJE Executing B955 044C The specified AL-PA is invalid. CMDRJE Executing B955 054E The specified topology is invalid. CMDRJE Executing B955 05A6...
Page 362 Table 9-18 SSB codes returned by raidcom modify port -security_switch raidcom modify port -security_switch Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 01C1 The specified LDEV is used as a quorum disk. CMDRJE Executing B955 020F The specified LDEV is not installed.
Page 363 Table 9-19 SSB codes returned by raidcom add ldev raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0000 The LDEV number is out of settable range. CMDRJE Executing/ 2E00 0002 The specified capacity is not in the effective range. Async Get Command Status...
Page 364 raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0101 The parity group number or the external group number is not in the effective range. Get Command Async 2E00 1005 Failed to restore the LDEV that is created to Status external volume group.
Page 365 raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0101 The volumes cannot be added because the check Status sum of the encryption key does not match. Get Command Async 2E10 020E The specified LDEV is not in the status where the Status capacity saving setting can be enabled.
Page 366 raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 0209 The operation cannot be performed due to a cache Status memory failure or maintenance work being performed. Get Command Async 2E11 6007 The operation cannot be performed because the Status specified pool volume is blocked.
Page 367 raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E21 9002 The program product is not installed. CMDRJE/Get Executing/ 2E21 9004 The program product is not installed. Command Status Async CMDRJE Executing 2E21 900E Compatible Software for IBM® FlashCopy® SE program product is not installed.
Page 368 The command cannot be accepted. After a while, execute the same command. Get Command Async 2EE8 FFFB An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 0002 The specified parameter is invalid. Check the Command Control Interface Command Reference. CMDRJE...
Page 369 raidcom add ldev Error code Executing/ Error message Description Async SSB1 SSB2 ERANGE Result too Executing The value of the capacity is invalid. large Table 9-20 SSB codes returned by raidcom delete journal raidcom delete journal Error code Executing/ Error message Description Async SSB1...
Page 370 Get Command Async 2EE4 50EE An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing B980 B903 The command was rejected because the selected resource belongs to NAS_Platform_System_RSG. Table 9-21 SSB codes returned by raidcom add journal...
Page 371 9000 A journal volume cannot be registered, or a journal Status cannot be added to the extended consistency group because the program product of Universal Replicator or Hitachi Universal Replicator for Mainframe is not installed. Get Command Async 2E23 0005...
Page 372 raidcom add journal Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing/ 2E30 0005 The specified volume cannot be used as a journal Async volume because it is set by Cache Residency Get Command Manager or Cache Residency Manager for Status Mainframe.
Page 373 The command cannot be accepted. After a while, execute the same command. CMDRJE Executing/ 2EE4 50EE An internal error occurred. Async Get Command Call Hitachi Data Systems customer support. Status CMDRJE Executing/ 2EE4 FEEC An internal error occurred. Async Call Hitachi Data Systems customer support.
Page 374 raidcom add journal Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Status CMDRJE Executing 2EF3 5002 The specified 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.
Page 375 CMDRJE Executing 2EE4 50EE An internal error occurred. Call Hitachi Data Systems customer support. Table 9-23 SSB codes returned by raidcom modify ldev raidcom modify ldev Error code Executing/ Error message Description...
Page 376 Table 9-25 SSB codes returned by raidcom modify ldev -mp_blade_id raidcom modify ldev -mp_blade_id Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0000 The LDEV number is out of settable range. CMDRJE Executing 2E00 8301 MP Blade ID is not in the effective range. CMDRJE Executing 2E10...
Page 377 ID of the LDEV in the specified device group. CMDRJE Executing 2EEA FEEC An internal error occurred. Call Hitachi Data Systems customer support. Table 9-28 SSB codes returned by raidcom modify ldev -ldev_name raidcom modify ldev -ldev_name Error code Executing/ Error message Description...
Page 378 raidcom initialize ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0004 The specified LDEV is used for a Thin Image pair or Status a Copy-on-Write Snapshot pair. Get Command Async 2E10 0008 The specified LDEV is used on the system disk. Status Get Command Async...
Page 379 raidcom initialize ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 6004 The operation of Dynamic Provisioning V-VOL Status cannot be performed because there is a blocked pool. Get Command Async 2E11 6006 The operation of Dynamic Provisioning V-VOL Status cannot be performed because there is a blocked pool volume.
Page 380 An internal error occurred. Status CMDRJE Executing/ 2EE8 FEEC An internal error occurred. Async Get Command Call Hitachi Data Systems customer support. Status CMDRJE Executing/ 2EE8 FFFF An internal error occurred. Async Get Command Call Hitachi Data Systems customer support.
Page 381 raidcom modify ldev -command_device Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 0002 The specified LDEV is used for a Universal Replicator pair or a journal. CMDRJE Executing 2E10 0004 The specified volume cannot be set because it is used by a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 382 2E22 7201 The specified SSID is used for the other boundary. CMDRJE Executing 2EE8 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 0002 The specified parameter is invalid. Check the Command Control Interface Command Reference.
Page 383 raidcom modify ldev -status nml Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0008 The specified LDEV is used as a system disk. Status CMDRJE Executing 2E10 0010 LDEV is not blocked. Get Command Async 2E10 0012 The specified LDEV is a CC/XRC attribute device.
Page 384 raidcom modify ldev -status nml Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E30 002C The specified LDEV cannot be restored because the Status shredding or the formatting operation has not been performed. Get Command Async 2E30 004E The specified LDEV is a Data Retention Utility/...
Page 385 raidcom modify ldev -status blk Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 001E The operation cannot be performed because the Status virtual disk space is blocked. CMDRJE Executing 2E11 0053 The specified LDEV is used in another operation. CMDRJE Executing 2E11...
Page 386 Table 9-34 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 code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0000 Invalid LDEV number. CMDRJE Executing 2E00 6101 The tiering policy is not in the effective range. CMDRJE Executing 2E00...
Page 387 97 is enabled is defined to the specified LDEV. CMDRJE Executing 2EE8 00E7 An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 9F02 The specified operation cannot be performed because it is not supported. 9-63...
Page 388 Table 9-36 SSB codes returned by raidcom modify ldev -status enable_fullallocation/ disable_fullallocation raidcom modify ldev -status enable_fullallocation/disable_fullallocation Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0000 The LDEV number is out of settable range. CMDRJE Executing 2E00 002F The specified value of the Full Allocation is invalid.
Page 389 Table 9-37 SSB codes returned by raidcom modify ldev -quorum_enable raidcom modify ldev -quorum_enable Error code Executing/ Error message Description Async SSB1 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...
Page 390 raidcom modify ldev -quorum_enable Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E21 810A A shared memory is not installed. Status Get Command Async 2E30 0005 Cache Residency Manager is set to the specified Status volume. Get Command Async 2E30...
Page 391 raidcom modify ldev -quorum_disable Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 A007 The setting of the quorum disk was released but Status 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.
Page 392 raidcom delete lun Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 393 raidcom delete lun Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B902 The command was rejected because the specified port is for NAS Platform (User LU). CMDRJE Executing B980 B903 The command was rejected because the selected resource belongs to NAS_Platform_System_RSG.
Page 394 raidcom add lun Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B958 018E The LU path cannot be set because the LDEV has an ALU attribute. 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.
Page 395 raidcom add lun Error code Executing/ Error message Description Async SSB1 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.
Page 396 raidcom add lun Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B980 B902 The command was rejected because the specified port is for NAS Platform (User LU).
Page 397 raidcom discover lun Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specified port is disabled. CMDRJE Executing 2E20 8401 The specified virtual port is not defined. Table 9-43 SSB codes returned by raidcom modify pool raidcom modify pool Error code Executing/...
Page 398 raidcom modify pool Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing/ 2E10 001F The operation cannot be performed because the Async total capacity of virtual volumes for Dynamic Get Command Tiering or active flash in the system exceeds the Status maximum.
Page 399 raidcom modify pool Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E11 800F The operation cannot be performed because the unsupported microcode version exists in the system. Get Command Async 2E11 8010 The storage system is in the internal processing or Status the configuration change processes are conflicting.
Page 400 raidcom modify pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E21 8103 The operation cannot be performed because of the Status insufficient capacity of shared memory. Get Command Async 2E21 810A The shared memory is not installed. Status Get Command Async...
Page 401 0001 Pool ID is not installed. CMDRJE Executing 2EE7 0011 An internal error occurred at the pool operation. Call Hitachi Data Systems customer support. CMDRJE Executing 2EE7 00EE The command cannot be accepted. After a while, execute the same command.
Page 402 The specified command cannot be accepted because the command is not supported. CMDRJE Executing 2EE7 FEEC An internal error occurred in the pool operation. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 9F02 The specified operation cannot be performed because it is not supported.
Page 403 raidcom delete pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 600F The operation cannot be performed because the Status current capacity rate exceeds the value of maximum reserved capacity rate. Get Command Async 2E10 6010 It cannot be deleted because the pool volume is Status...
Page 404 Executing 2EE7 00F9 Pool ID is not installed. CMDRJE Executing 2EE7 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 6002 The specified parameter is invalid. Check the Command Control Interface Command Reference. CMDRJE Executing...
Page 405 raidcom add snap_pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0102 The pool cannot be created because there are not Status enough resources (VDEV) depending on cache management devices. Get Command Async 2E10 600D The operation cannot be performed because the Status pool volume is being deleted.
Page 406 raidcom add snap_pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E30 0007 The specified LDEV has the LU path definition. Status Get Command Async 2E30 000C The specified LDEV is used as a quorum disk. Status Get Command Async...
Page 407 The usage capacity exceeds the license capacity of Status program product. CMDRJE Executing 2EE7 FEEC An internal error occurred. Get Command Async Call Hitachi Data Systems customer support. Status Get Command Async 2EE7 FFFF An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE...
Page 408 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 specified 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 specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 409 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 site of the 3DC cascading configuration is specified 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 specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 410 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 0036 The command ends abnormally because the Volume Migration reserved volume is specified as the P-VOL of a Thin Image pair or aCopy-on-Write Snapshot pair. CMDRJE Executing 2E10...
Page 411 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 Provisioning V-VOL in capacity expanding is specified as the P-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair. 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 specified P-VOL.
Page 412 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 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 specified P-VOL is in progress.
Page 413 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 414 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 • The specified 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.
Page 415 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E20 000B The command ends abnormally because an unmounted volume is specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair. CMDRJE Executing 2E20 000C...
Page 416 raidcom add snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E30 007A The command ends abnormally because the volume other than OPEN-V is specified as the P- VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 417 8000 The specified operation is not supported in the current microcode version. CMDRJE Executing 2EC6 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing B980 B903 The command was rejected because the selected resource belongs to NAS_Platform_System_RSG.
Page 418 raidcom modify snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 0035 The command ends abnormally because the Volume Migration target volume is specified as the P-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 419 raidcom modify snapshot Error code Executing/ Error message Description Async SSB1 SSB2 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. CMDRJE Executing 2E10 004C The Thin Image pair or the Copy-on-Write Snapshot pair cannot be restored because the Thin Image pair...
Page 420 raidcom modify snapshot Error code Executing/ Error message Description Async SSB1 SSB2 • The specified 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.
Page 421 raidcom modify snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 9800 An error occurred at the operation of Thin Image due to one of the following reasons: • The LDEV number specified for the P-VOL or the S-VOL is incorrect.
Page 422 8000 The specified operation is not supported in the current microcode version. CMDRJE Executing 2EC6 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 0002 The specified parameter is invalid. Check the Command Control Interface Command Reference.
Page 423 Error message Description Async SSB1 SSB2 CMDRJE Executing 2EC5 FEEC An internal error occurred. Call Hitachi Data Systems customer support. Table 9-50 SSB codes returned by raidcom delete snapshot raidcom delete snapshot Error code Executing/ Error message Description Async SSB1...
Page 424 raidcom delete snapshot Error code Executing/ Error message Description Async SSB1 SSB2 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...
Page 425 930A The virtual storage machine with the specified serial number is not found. CMDRJE Executing 2EC6 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing B980 B903 The command was rejected because the selected resource belongs to NAS_Platform_System_RSG.
Page 426 Table 9-51 SSB codes returned by raidcom map snapshot raidcom map snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 0028 The command ends abnormally because the volume whose LDEV number is out of range is specified as the P-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 427 raidcom map snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 002E The command ends abnormally because the volume to which S-VOL Disable option is set is specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 428 raidcom map snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 0056 The specified 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 specified P-VOL is different from the virtual storage machine of the specified S-VOL.
Page 429 raidcom map snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E21 9306 The virutal LDEV ID for a virtual storage machine is not defined on the specified LDEV. CMDRJE Executing 2E21 930A The virtual storage machine with the specified serial number is not found.
Page 430 raidcom map snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E30 2E30 The specified 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 specified as an S-VOL.
Page 431 raidcom replace snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 002B The command ends abnormally because the P-VOL of a Universal Replicator pair is specified as the S- VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 432 raidcom replace snapshot Error code Executing/ Error message Description Async SSB1 SSB2 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 specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 433 raidcom replace snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E20 0000 The specified LDEV is not defined. CMDRJE Executing 2E20 000B The command ends abnormally because an unmounted volume is specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair.
Page 434 raidcom replace snapshot Error code Executing/ Error message Description Async SSB1 SSB2 migration is specified as the S-VOL of a Thin Image pair or a Copy-on-Write Snapshot pair. CMDRJE Executing 2E30 0099 The specified LDEV is a volume of which Data Direct Mapping attribute is enabled.
Page 435 raidcom unmap snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 0060 The command ends abnormally because the specified S-VOL is not assigned to a Thin Image pair. CMDRJE Executing 2E10 0061 The specified volume cannot be used for the Thin Image pair operation because the virtual LDEV ID is deleted.
Page 436 raidcom unmap snapshot Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E21 930A The virtual storage machine with the specified serial number is not found. CMDRJE Executing 2E30 008F The command ends abnormally because the specified P-VOL is not a P-VOL of a Thin Image pair.
Page 437 3001 The command cannot be executed because the RCU identification code of a path is invalid. CMDRJE Executing 2ED6 00EF An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2ED6 3300 The SSID is invalid. CMDRJE Executing...
Page 438 Table 9-56 SSB codes returned by raidcom add dp_pool raidcom add dp_pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E00 0000 The LDEV number is out of settable range. Status CMDRJE Executing 2E00 6000 The value of pool ID is out of range. CMDRJE Executing 2E00...
Page 439 raidcom add dp_pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Status Get Command Async 2E11 8003 The operation cannot be performed because the Status power supply is switched off. Get Command Async 2E11 800F The operation cannot be performed because the Status unsupported microcode version exists in the system.
Page 440 raidcom add dp_pool Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E30 000E The specified LDEV is already used as a pool Status volume. Get Command Async 2E30 0010 The specified LDEV is a command device. Status Get Command Async...
Page 441 The command cannot be accepted. After a while, execute the same command. CMDRJE Executing/ 2EE7 FEEC An internal error occurred. Async Get Command Call Hitachi Data Systems customer support. Status Get Command Async 2EE7 FFFF An internal error occurred. Status Call Hitachi Data Systems customer support.
Page 442 Status RCU identification code of a path is invalid. CMDRJE Executing 2ED6 00EF An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2ED6 3300 The value of SSID for the remote storage system is invalid. Table 9-58 SSB codes returned by raidcom delete rcu_path...
Page 443 DKC is busy. After a while, execute the same command. Get Command Async 2ED6 3005 An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 3002 The specified parameter is invalid. Check the Command Control Interface Command Reference. CMDRJE...
Page 444 raidcom delete rcu_path Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B902 The command was rejected because the specified port is for NAS Platform (User LU). Table 9-59 SSB codes returned by raidcom add rcu_path raidcom add rcu_path Error code Executing/ Error message...
Page 445 DKC is busy. After a while, execute the same command. Get Command Async 2ED6 3005 An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage system is invalid. CMDRJE...
Page 446 DKC is busy. After a while, execute the same command. Get Command Async 2ED6 3005 An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage system is invalid. CMDRJE...
Page 447 raidcom add rcu Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E00 3009 The command cannot be executed because all the Status CU numbers in the RCU is not unified at the path that is specified creation or deletion. CMDRJE Executing 2E00...
Page 448 DKC is busy. After a while, execute the same command. Get Command Async 2ED6 3005 An internal error occurred. Status Call Hitachi Data Systems customer support. CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage system is invalid. CMDRJE...
Page 449 raidcom delete ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0001 The specified LDEV is used for a TrueCopy pair, a Status Universal Replicator pair or a command device defined by Business Continuity Manager. Get Command Async 2E10...
Page 450 raidcom delete ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 0004 An LDEV that is in the state of formatting is Status included in the parity group of the target LDEV. Get Command Async 2E11 0005 An LDEV that is in the state of executing quick...
Page 451 raidcom delete ldev Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E30 000F The specified LDEV is used as a journal volume. Status Get Command Async 2E30 0006 The specified LDEV is used in the FICON® Data Status Migration.
Page 452 Get Command Async 2EE8 0A18 An internal error occurred. Status CMDRJE Executing/ 2EE8 FEEC An internal error occurred. Call Hitachi Data Async Systems customer support. Get Command Status Get Command Async 2EE8 FFFB An internal error occurred. Status Call Hitachi Data Systems customer support.
Page 453 Table 9-63 SSB codes returned by raidcom delete hba_wwn raidcom delete hba_wwn Error code Executing/ Error message Description Async SSB1 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...
Page 454 raidcom add hba_wwn Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 B9D8 The WWN which belongs to the specified host group is registered in another SPM group. CMDRJE Executing B957 B9DA The operation cannot be performed because it is locked in another session.
Page 455 raidcom reset hba_wwn Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 4385 The specified WWN does not exist. CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B980...
Page 456 Table 9-69 SSB codes returned by raidcom modify port -port_speed raidcom modify port -port_speed Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 01C1 The specified LDEV is used as a quorum disk. CMDRJE Executing B955 020F The specified LDEV is not installed.
Page 457 raidcom modify port -port_speed Error code Executing/ Error message Description Async SSB1 SSB2 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 specified port is for NAS Platform (System LU).
Page 458 -port_attribute Error code Executing/ Error message Description Async SSB1 SSB2 Call Hitachi Data Systems customer support. CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B980...
Page 459 raidcom modify port -ipv4_subnetmask Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 120E The command cannot be executed because the iSCSI virtual port mode is ON. Table 9-74 SSB codes returned by raidcom modify port -ipv4_gateway_address raidcom modify port -ipv4_gateway_address Error code Executing/...
Page 460 raidcom modify port -ipv6_global_address Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 120E The command cannot be executed because the iSCSI virtual port mode is ON. Table 9-77 SSB codes returned by raidcom modify port -ipv6_global_address2 raidcom modify port -ipv6_global_address2 Error code Executing/...
Page 461 Table 9-79 SSB codes returned by raidcom modify port -ipv6_mode raidcom modify port -ipv6_mode Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 1039 The command device being used at the local CCI exists under the port. CMDRJE Executing B955...
Page 462 raidcom modify port -isns_server_address Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 10C5 The specified 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.
Page 463 Table 9-85 SSB codes returned by raidcom modify port -selective_ack_mode raidcom modify port -selective_ack_mode Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 1039 The command device being used at the local CCI exists under the port. CMDRJE Executing B955...
Page 464 raidcom modify port -delete_vlan_id Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 120E The command cannot be executed because the iSCSI virtual port mode is ON. Table 9-89 SSB codes returned by raidcom modify port -modify_vlan_id raidcom modify port -modify_vlan_id Error code Executing/...
Page 465 Table 9-92 SSB codes returned by raidcom modify port -t10pi raidcom modify port -t10pi Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 8400 The value of the specified port is invalid. Get Command Async Status CMDRJE Executing 2E00 8404...
Page 466 raidcom modify port -add_iscsi_virtual_port Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 467 raidcom modify port -add_iscsi_virtual_port Error code Executing/ Error message Description Async SSB1 SSB2 the external storage system is registered for the specified virtual port. CMDRJE Executing B955 120A An internal error occurred. CMDRJE Executing B955 120B The specified port is not a port of the package for iSCSI.
Page 468 raidcom modify port -modify_iscsi_virtual_port Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 469 raidcom modify port -modify_iscsi_virtual_port Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B955 120B The specified port is not a port of the package for iSCSI. CMDRJE Executing B955 120C The specified virtual port does not exist. CMDRJE Executing B955...
Page 470 Table 9-96 SSB codes returned by raidcom modify port -iscsi_virtual_port_mode raidcom modify port -iscsi_virtual_port_mode Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 8400 The value of the specified port is invalid. CMDRJE Executing 2E11 800F The operation failed because multiple versions of DKCMAIN microcode are included.
Page 471 raidcom delete host_grp Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B956 3202 It cannot be deleted because it is the last path of a TrueCopy or GAD pair. CMDRJE Executing B956 3203 Deletion cannot be executed because the last path of ShadowImage is included in the host group.
Page 472 raidcom add host_grp Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B956 3077 The attribute of the specified port is Initiator or External. CMDRJE Executing B956 30FD The attribute of the specified port is Initiator or External. CMDRJE Executing B956...
Page 473 Table 9-99 SSB codes returned by raidcom modify host_grp raidcom modify host_grp Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B956 304F The program product is not installed. CMDRJE Executing B956 30FD The attribute of the specified port is Initiator or External.
Page 474 raidcom modify host_grp Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B958 098E When using 8FC16 or 16FE10 channel package, you cannot configure the host mode option 51 (Round Trip Set Up Option) for the host group because the host mode option 51 is not supported.
Page 475 Async 2EDA 0905 An internal error occurred by the operation of a Status path for an external path. Call Hitachi Data Systems customer support. CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS platform (System LU).
Page 476 The command cannot be accepted. After a while, execute the same command. Get Command Async 2EDA FEEC An internal error occurred. Status Call Hitachi Data Systems customer support. Get Command Async 2EDA FFFF An internal error occurred. Status Call Hitachi Data Systems customer support.
Page 477 raidcom add path Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 4303 The path operations cannot be performed for the Status following reasons: • The target of the specified path group is TagmaStore USP/TagmaStore NSC. •...
Page 478 The command cannot be accepted. After a while, execute the same command. Get Command Async 2EDA FEEC An internal error occurred. Status Call Hitachi Data Systems customer support. Get Command Async 2EDA FFFF An internal error occurred. Status Call Hitachi Data Systems customer support.
Page 479 The specified pool is the one for Thin Image or Copy-on-Write Snapshot. CMDRJE Executing 2EE7 FEEC An internal error occurred. Call Hitachi Data Systems customer support. Table 9-105 SSB codes returned by raidcom reallocate pool raidcom reallocate pool Error code Executing/...
Page 480 Reallocation cannot be performed because there is only one Tier in the pool group. CMDRJE Executing 2EE7 FEEC An internal error occurred. Call Hitachi Data Systems customer support. Table 9-106 SSB codes returned by raidcom extend ldev raidcom extend ldev Error code Executing/...
Page 481 The operation to resource group 0 (meta_resource) cannot be performed. CMDRJE Executing 2ECA FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing B980 B903 The command was rejected because the selected resource belongs to NAS_Platform_System_RSG. CMDRJE...
Page 482 The attribute of the specified port is Initiator or External. CMDRJE Executing 2ECA FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 2202 The specified operation cannot be performed because it is not supported. CMDRJE...
Page 483 Error message Description Async SSB1 SSB2 CMDRJE Executing 2EF0 FEEC An internal error occurred. Call Hitachi Data Systems customer support. Table 9-110 SSB codes returned by raidcom map resource raidcom map resource Error code Executing/ Error message Description Async SSB1 SSB2...
Page 484 The specified LDEV cannot be set the information of the virtual volume because it is not virtualized. CMDRJE Executing 2ECA FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 2202 The specified operation cannot be performed because it is not supported.
Page 485 0097 The specified LDEV is used as an SLU. CMDRJE Executing 2ECA FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 2202 The specified operation cannot be performed because it is not supported. Table 9-112 SSB codes returned by raidcom modify resource...
Page 486 Table 9-115 SSB codes returned by raidcom unlock resource raidcom unlock resource Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E10 2200 Cannot unlock because it is locked in another session. Table 9-116 SSB codes returned by raidcom modify clpr raidcom modify clpr Error code Executing/...
Page 487 The specified command cannot be accepted because the command is not supported. CMDRJE Executing 2EE8 FEEC An internal error occurred. Call Hitachi Data Systems customer support. CMDRJE Executing 2EF3 0102 The specified parameter is invalid. Check the Command Control Interface Command Reference.
Page 488 raidcom add spm_group Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B9D4 B9DC SPM cannot be operated without specifying the host group because the specified WWN, SPM group to which the SPM name belongs, or the specified SPM group is associated with the host group.
Page 489 Table 9-119 SSB codes returned by raidcom modify spm_group raidcom modify spm_group Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B9D4 B9D0...
Page 490 raidcom add spm_wwn Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not installed. CMDRJE Executing B9D4 B9D7 The specified SPM name has already existed. CMDRJE Executing D9D4 B9DA The operation cannot be performed because it is locked in another session.
Page 491 Table 9-122 SSB codes returned by raidcom modify spm_wwn raidcom modify spm_wwn Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B9D4 B9D0...
Page 492 raidcom modify spm_ldev Error code Executing/ Error message Description Async SSB1 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...
Page 493 Table 9-124 SSB codes returned by raidcom delete spm_ldev raidcom delete spm_ldev Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 9B01 The specified iSCSI name is incorrect. CMDRJE Executing 2E11 9400 The command cannot be accepted. After a while, execute the same command.
Page 494 raidcom get spm_ldev Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E11 9400 The command cannot be accepted. After a while, execute the same command. CMDRJE Executing 2E3F 8000 The specified operation is not supported in the current microcode version.
Page 495 raidcom modify ldev -capacity_saving/-capacity_saving_mode Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0215 The operation cannot be performed because the Status specified volume is being used by Quick Restore of ShadowImage. Get Command Async 2E10 0219 The tiering policy is enabled for the specified Status...
Page 496 Executing 2EBE 9E01 The specified parameter is incorrect. CMDRJE Executing/ 2EE8 FEEC An internal error occurred. Contact Hitachi Data Async Systems customer support. Get Command Status Table 9-128 SSB codes returned by raidcom replace quorum raidcom replace quorum Error code...
Page 497 The specified LDEV is a volume of which Data Direct Mapping attribute is enabled. CMDRJE Executing 2EB9 FEEC An internal error occurred. Contact Hitachi Data Systems customer support. Table 9-129 SSB codes returned by raidcom modify quorum raidcom modify quorum Error code Executing/...
Page 498 Table 9-130 SSB codes returned by raidcom add hba_iscsi raidcom add hba_iscsi Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 404F The program product is not installed. CMDRJE Executing B957 408F The specified command is not supported for the FC port.
Page 499 Table 9-132 SSB codes returned by raidcom set hba_iscsi raidcom set hba_iscsi Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 404F The program product is not installed. CMDRJE Executing B957 408F The specified command is not supported for the FC port.
Page 500 raidcom add chap_user Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 46E4 The specified 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...
Page 501 raidcom set chap_user Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B957 408F The specified command is not supported for the FC port. CMDRJE Executing B957 40FD The attribute of the specified port is Initiator or External. CMDRJE Executing B957...
Page 502 Table 9-138 SSB codes returned by raidcom send ping raidcom send ping Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E00 8400 The value of the specified port is invalid. CMDRJE Executing 2E02 8403 The specified virtual port number is out of range. CMDRJE Executing 2E10...
Page 503 raidcom add rcu_iscsi_port Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing B980 B901 The command was rejected because the specified port is for NAS Platform (System LU). CMDRJE Executing B980 B902 The command was rejected because the specified port is for NAS Platform (User LU).
Page 504 raidcom add external_iscsi_name Error code Executing/ Error message Description Async SSB1 SSB2 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.
Page 505 Table 9-144 SSB codes returned by raidcom discover external_iscsi_name raidcom discover external_iscsi_name Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E02 8403 The specified virtual port number is out of range. CMDRJE Executing 2E10 8404 The iSCSI virtual port mode for the specified port is disabled.
Page 506 raidcom modify initiator_chap_user Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2E11 4305 The operation cannot be performed because the specified port is defined to the external path. CMDRJE Executing 2E21 810A The shared memory is not installed. CMDRJE Executing 2E31...
Page 507 raidcom initialize parity_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 6022 The operation cannot be performed because the Status deduplication system data volume of the pool linked with an LDEV is blocked. Get Command Async 2E11 0007...
Page 508 2E31 0001 Maintenance work cannot be performed because Status the LDEV is a quorum disk. CMDRJE Executing 2ECF FEEC An internal error occurred. Call Hitachi Data Systems customer support. Get Command Async Status CMDRJE Executing 2EF3 0102 The specified parameter is invalid. Check the Command Control Interface Command Reference.
Page 509 raidcom modify parity_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0104 The specified operation cannot be performed Status because the dynamic sparing is in process. Get Command Async 2E10 0105 The specified operation cannot be performed Status because the copy back is in process.
Page 510 2E31 0202 The LDEV in the specified parity group is mapped Status for the online data migration. CMDRJE Executing/ 2ECF FEEC Internal error occurred. Contact Hitachi Data Async Systems customer support. Get Command Status CMDRJE Executing 2EF3 0102 The specified operation cannot be performed because the operation is not supported.
Page 511 8000 The specified operation is not supported in the current microcode version. CMDRJE Executing 2EBD FEEC Internal error occurred. Contact Hitachi Data Systems customer support. CMDRJE Executing 2EBE 9E01 The specified parameter is invalid. Table 9-152 SSB codes returned by raidcom add license (VSP Gx00 models and VSP...
Page 512 raidcom add license Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2EC0 0102 This program product requires a higher-version hardware product. CMDRJE Executing 2EC0 0103 To use this program product, increase the shared memory allocation, and enable the program product.
Page 513 raidcom delete license Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2EC1 0106 To remove this program product, another program product must be removed or disabled first. CMDRJE Executing 2EC1 0107 To remove this program product, another program product must be removed or disabled first.
Page 514 raidcom modify license Error code Executing/ Error message Description Async SSB1 SSB2 CMDRJE Executing 2EC2 010C Data Retention Utility cannot be deleted because secondary volume rejection or reservation settings remain. CMDRJE Executing 2EC2 010D The specified program product is not supported. CMDRJE Executing 2EC2...
Page 515 The specified command cannot be accepted because the command is not supported. CMDRJE Executing / 2EE7 FEEC The internal error occurs. Contact Hitachi Data Systems customer support. Get Command Async Status Table 9-156 SSB codes returned by raidcom add parity_grp...
Page 516 raidcom add parity_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E02 0101 A parity group in which encryption and accelerated Status compression are enabled cannot be created. Get Command Async 2E02 8501 The specified drive has different drive type codes. Status Get Command Async...
Page 517 The specified drive is not installed. Status CMDRJE Executing/ 2EC4 FEEC An internal error occurred. Contact Hitachi Data Systems customer support. Get Command Async Status Table 9-157 SSB codes returned by raidcom delete parity_grp (VSP Gx00 models and VSP Fx00 models)
Page 518 raidcom delete parity_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E10 0000 The specified parity group contains LDEVs used by Status another program product. Get Command Async 2E10 0001 The specified parity group contains an LDEV used Status as a TrueCopy or Universal Replicator pair.
Page 519 raidcom delete parity_grp Error code Executing/ Error message Description Async SSB1 SSB2 Get Command Async 2E11 8012 The specified operation cannot be performed Status because the power condition of the drive box is abnormal. Get Command Async 2E11 8013 The specified operation cannot be performed Status because storage system is in process.
Page 520 CMDRJE Executing/ 2EC4 FEEC An internal error occurred. Contact Hitachi Data Systems customer support. Get Command Async Status Table 9-158 SSB codes returned by raidcom modify drive command (VSP Gx00 models...
Page 521: Other Ssb Codes Indicating Internal Errors
Status Get Command Async 2EC4 FEEC An internal error occurred. Contact Hitachi Data Status Systems customer support. Other SSB codes indicating internal errors The error codes (SSB1) listed below indicate internal errors. For your confirmation, contact Hitachi Data Systems customer support.
Page 522 Error codes Description SSB1 SSB2 2EBB XXXX An internal error occurred. Contact Hitachi Data Systems customer support. 2EBD XXXX An internal error occurred. Contact Hitachi Data Systems customer support. 2EBE XXXX An internal error occurred. Contact Hitachi Data Systems customer support.
Page 523: Calling Hitachi Data Systems Customer Support
The service information messages (SIMs), including reference codes and severity levels, displayed by Storage Navigator. The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. To contact technical support, log on to Hitachi Data...
Page 524 9-200 Troubleshooting Command Control Interface User and Reference Guide...
Page 525 Index out-of-band execution processing asynchronously alternate command device processing synchronously defining configuration check 3-33 asynchronous commands configuration definition file 2-13 list of provisioning examples 2-14 processing 1-3, 5-3 configuration definition file settings 2-16 authorities for commands and operations 3-14 cascading connections 2-30, 2-33 HORCM_ALLOW_INST 2-28...
Page 526 facility SLPR configuration 8-18 parameters specify host group 8-14 permission command 7-10 system buffer flushing permitting protected volumes 7-12 volume discovery specifications external volumes data protection operations creating using Fibre Channel 5-45 data replication operations creating using iSCSI 5-47 Data Retention Utility operations 5-45 how it works...
Page 527 iSCSI virtual port mode disabling 5-44 pairdisplay examples on HOST1 and HOST2 2-33 enabling 5-44 paired volumes iSCSI virtual port number parameters, configuration 2-15 deleting 5-44 permission command and data protection 7-10 setting 5-44 port check 3-30 precheck provisioning operations LDEV adding 3-41...
Page 528 command competition command flow UNIX LDEVs files 2-36 SCSI commands starting up one instance sidefile 6-27 starting up two instances cache 6-27 user authentication 1-8, 3-8 SLPR command operation configuration examples 8-18 security 8-16 security:specify SLPR protection facility 8-17 Solaris virtual port mode dual pathing disabling...
Page 529 Command Control Interface User and Reference Guide...
Page 530 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.com MK-90RD7010-32...

This manual is also suitable for:

Vsp g1000 Vsp g1500 Vsp g200 Vsp g600 Vsp g800 Vsp f400 ... Show all

Hitachi VSP F1500 User And Reference Manual

Quick Links

Troubleshooting

Related Manuals for Hitachi VSP F1500

Summary of Contents for Hitachi VSP F1500