XP7 RAID Manager User Guide - Hewlett Packardh20628. · 2019-01-17 · XP7RAIDManagerUserGuide...

XP7 RAID Manager User Guide

AbstractThis document describes and provides instructions for using the RAID Manager to configure and perform operationson the RAID storage systems.

Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.

Part Number: 858760-004Published: October 2016Edition: 11

© Copyright 2014, 2016 Hewlett Packard Enterprise Development LP

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and servicesare set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constitutingan additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensedto the U.S. Government under vendor's standard commercial license.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Warranty

WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:

http://www.hpe.com/info/storagewarranty

Revision HistoryMay 2014Revision 1

Applies to microcode version 80-01-22-00/02 or later.

September 2014Revision 2Applies to microcode version 80-01-42-00/00 or later.

October 2014Revision 3Applies to microcode version 80-02-01-00/01 or later.

April 2015Revision 4Applies to microcode version 80-02-22-00/00 or later.

June 2015Revision 5Applies to microcode version 80-02-41-00/00 or later.

September 2015Revision 6Applies to microcode version 80-03-01-00/00 or later.

December 2015Revision 7Applies to microcode version 80-03-01-00/00 or later.

March 2016Revision 8Applies to microcode version 80-04-02-00/00 or later.

April 2016Revision 9Applies to microcode version 80-04-02-00/00 or later.

June 2016Revision 10Applies to microcode version 80-04-21-00/00 or later.

October 2016Revision 11Applies to microcode version 80-05-02-00/00 or later.

http://www.hpe.com/info/storagewarranty

Contents1 Overview..............................................................................................................9

About RAID Manager............................................................................................................................9RAID Manager functions.......................................................................................................................9

RAID Manager functions matrix.......................................................................................................9Provisioning functions....................................................................................................................10Asynchronous command processing............................................................................................10Command execution modes..........................................................................................................11Precheck function..........................................................................................................................11Command execution by the in-band and out-of-band methods....................................................12User authentication mode..............................................................................................................13LDEV nickname function...............................................................................................................14LDEV grouping function.................................................................................................................14Resource group function...............................................................................................................14Resource locking function.............................................................................................................14

RAID Manager functions available on all RAID storage systems.......................................................15In-system replication......................................................................................................................15Remote replication.........................................................................................................................15Data protection..............................................................................................................................15

2 RAID Manager software environment...............................................................16Overview of the RAID Manager software environment......................................................................16RAID Manager components on the RAID storage system.................................................................16

Command device...........................................................................................................................16Command device guarding......................................................................................................17Alternate command device function.........................................................................................19Remote command device........................................................................................................19

RAID Manager and the SCSI command interface.........................................................................20Command competition.............................................................................................................21Command flow.........................................................................................................................21Issuing commands for LDEVs within a LUSE device...............................................................21

RAID Manager instance components on the host server...................................................................22HORCM operational environment.................................................................................................22RAID Manager instance configurations.........................................................................................22Host machines that can be paired.................................................................................................24Configuration definition file............................................................................................................25Configuration definition file settings...............................................................................................28

HORCM_MON.........................................................................................................................28HORCM_CMD (in-band method).............................................................................................29HORCM_CMD (out-of-band method).......................................................................................32HORCM_DEV..........................................................................................................................34HORCM_INST..........................................................................................................................36HORCM_LDEV........................................................................................................................36HORCM_LDEVG......................................................................................................................37HORCM_INSTP.......................................................................................................................37HORCM_ALLOW_INST...........................................................................................................38

Correspondence of the configuration definition file for cascading volume and mirrordescriptors.....................................................................................................................................38

Correspondence of configuration file and mirror descriptors...................................................39Cascading connection and configuration files..........................................................................40Business Copy.........................................................................................................................40Cascading connections for Continuous Access Synchronous and Business Copy.................41

RAID Manager software files..............................................................................................................44

Contents 3

RAID Manager files supplied with the software.............................................................................44RAID Manager files for UNIX-based systems..........................................................................44RAID Manager files for Windows-based systems....................................................................45RAID Manager files for OpenVMS-based systems..................................................................47

RAID Manager log and trace files.......................................................................................................48RAID Manager log files..................................................................................................................48RAID Manager trace files..............................................................................................................50RAID Manager trace control command.........................................................................................50Command logging for audit...........................................................................................................51

Logging other than raidcom command.....................................................................................51Logging raidcom command......................................................................................................53

User-created files................................................................................................................................56User environment variable..................................................................................................................56

3 RAID Manager functions...................................................................................57System configuration using RAID Manager........................................................................................57

In-band system configurations and out-of-band system configurations........................................57System configuration for connecting to a RAID Manager server connected by the in-band methodusing the out-of-band method.......................................................................................................58

Connecting to RAID Manager server already connected by In-Band method using Out-of-Bandmethod................................................................................................................................................59User authentication.............................................................................................................................61Command operation authority and user authentication......................................................................62

Controlling User Role....................................................................................................................62Controlling user resources.............................................................................................................62Commands executed depending on operation authorities............................................................65

Relation between resource groups and command operations...........................................................70Resource lock function.......................................................................................................................73Command execution modes...............................................................................................................73

Overview........................................................................................................................................73Context check................................................................................................................................75

How to check............................................................................................................................75Details of check contents.........................................................................................................75

Configuration check.......................................................................................................................80Resource location and parameter.......................................................................................................81

MP blade location and parameter.................................................................................................81LDEV grouping function......................................................................................................................82

Overview........................................................................................................................................82Device group definition methods...................................................................................................85Read operations and command device settings...........................................................................85Define device group.......................................................................................................................86

Device group creation..............................................................................................................88LDEV addition to device group.................................................................................................88LDEV deletion from device group............................................................................................89Device group deletion..............................................................................................................90

Copy group function......................................................................................................................91Copy group creation.................................................................................................................93LDEV addition to a copy group................................................................................................93LDEV deletion from copy group...............................................................................................94Copy group deletion.................................................................................................................95Pair operation by specifying a copy group...............................................................................96

Pair operations with mainframe volumes............................................................................................99Using "dummy" LUs for mainframe LDEVs...................................................................................99Pair status and access permission for mainframe LDEVs..........................................................100Operational differences for multiplatform volumes......................................................................102

4 Contents

Operational differences for replication commands......................................................................102Multi-array virtualization function (XP7)............................................................................................103

System configuration example with the multi-array virtualization function..................................103Using RAID Manager in a system configuration with the multi-array virtualization function.......104Configuration definition file settings with multi-array virtualization..............................................104Example of the configuration definition files when specifying a virtual storage machine byHORCM_CMD.............................................................................................................................105Specifying a virtual storage machine to HORCM_VCMD...........................................................107

Command operations to the virtual storage machine.............................................................107Operation target for raidcom commands when specifying the virtual storage machine inHORCM_VCMD.....................................................................................................................109raidcom commands for volumes that belong to virtual storage machine for HORCM_CMD..113

4 Starting up RAID Manager..............................................................................114Starting up on UNIX systems............................................................................................................114Starting up on Windows systems......................................................................................................115Starting up on OpenVMS systems....................................................................................................116Starting RAID Manager as a service (Windows systems)................................................................117

5 Provisioning operations with RAID Manager...................................................120About provisioning operations..........................................................................................................120

Overview of the configuration setting command.........................................................................120Synchronous command processing.......................................................................................120Asynchronous command processing.....................................................................................120Errors during asynchronous command processing................................................................121Workflow for executing asynchronous commands.................................................................121Asynchronous commands......................................................................................................121

Help on configuration setting commands....................................................................................123LDEV nickname function.............................................................................................................123

Available provisioning operations.....................................................................................................123Provisioning operations that can be performed on device groups....................................................128

Operation method........................................................................................................................128Workflow for performing provisioning operations..............................................................................130Resource group operations..............................................................................................................131

Creating resource groups............................................................................................................131Deleting resource groups............................................................................................................131Allocating resources that are allocated to resource groups to other resource groups................131Execution example......................................................................................................................132

Internal volume operations...............................................................................................................133Creating internal volumes (open-systems)..................................................................................133Script examples (open systems).................................................................................................134Creating internal volumes (Mainframe volume)...........................................................................137

Script examples......................................................................................................................137Script examples...........................................................................................................................138

Virtual volume (Thin Provisioning) operations..................................................................................140Creating virtual volumes (Thin Provisioning)...............................................................................140Script examples...........................................................................................................................142

Virtual volume (Thin Provisioning MF) operations............................................................................145Creating virtual volumes (Thin Provisioning MF).........................................................................145Script examples...........................................................................................................................146

Virtual volume (Smart Tiers) operations...........................................................................................147Operational flow...........................................................................................................................147Creating virtual volumes (Smart Tiers)........................................................................................149Script examples...........................................................................................................................150

External volume operations..............................................................................................................153Creating external volumes...........................................................................................................153

Contents 5

Script Examples...........................................................................................................................155Cache Partition operations...............................................................................................................157

Performing Cache Partition operations.......................................................................................158Displaying CLPR information......................................................................................................158Migrating parity groups in a CLPR..............................................................................................158

Displaying parity group information........................................................................................158Moving parity groups..............................................................................................................158Checking result of CLPR transfer...........................................................................................158

Performance Control operations.......................................................................................................159Configuring Performance Control by specifying ports and WWNs of HBAs................................159

Controlling the priority of I/O operations in storage systems on servers................................159Using and managing Performance Control............................................................................160Setting PFC names for WWNs and registering them to the PFC group................................161Configuring Performance Control by specifying ports and WWNs of HBAs..........................161Cautions about using Performance Control...........................................................................165Cautions when using host groups after registering them in PFC groups (P9500 only).........166

Configuring Performance Control by specifying LDEVs and WWNs of HBAs..................................167Virtual storage machine operations..................................................................................................168

Creating host groups in a virtual storage machine......................................................................169Adding LDEVs to a virtual storage machine................................................................................169Removing the virtual storage machine........................................................................................169

6 Data replication operations with RAID Manager.............................................171About data replication operations.....................................................................................................171Features of paired volumes..............................................................................................................171Using RAID Manager with Business Copy and Continuous Access Synchronous..........................172Using RAID Manager with Fast Snap...............................................................................................173Using RAID Manager with High Availability......................................................................................173Business Copy operations................................................................................................................174

Business Copy duplicated mirroring............................................................................................175Business Copy cascading pairs..................................................................................................175

Restrictions for Business Copy cascading volumes...............................................................176Restriction for Continuous Access Synchronous/Business Copy cascading volumes..........177

Continuous Access Synchronous operations...................................................................................177Continuous Access Synchronous takeover commands..............................................................178

Takeover-switch function........................................................................................................179Swap-takeover function..........................................................................................................180SVOL-takeover function.........................................................................................................181PVOL-takeover function.........................................................................................................182

Continuous Access Synchronous remote commands.................................................................182Continuous Access Synchronous local commands.....................................................................184

Continuous Access Synchronous, Business Copy, and Continuous Access Journal operations.....184Continuous Access Synchronous/Business Copy volumes........................................................184Continuous Access Synchronous/Business Copy/Continuous Access Journal pair status........185Continuous Access Asynchronous, Continuous Access Synchronous, Continuous AccessJournal, and High Availability volumes........................................................................................190

Sidefile cache for Continuous Access Asynchronous............................................................192Continuous Access Asynchronous transition states and sidefile control...............................192Continuous Access Asynchronous/Continuous Access Journal error state..........................194

Continuous Access Synchronous/Continuous Access Asynchronous and Continuous AccessJournal/High Availability fence level settings...............................................................................194

Setting the fence level............................................................................................................196Snapshot operations.........................................................................................................................196

Snapshot volumes.......................................................................................................................197Pair operations and commands for Snapshot and Fast Snap.....................................................197

6 Contents

Creating a Snapshot pair.............................................................................................................198Snapshot pair status....................................................................................................................198Pair status relationship to Snapshot commands.........................................................................199

Controlling Auto LUN........................................................................................................................200Specifications for Auto LUN.........................................................................................................200Commands to control Auto LUN..................................................................................................201Relations between "cc" command issues and status..................................................................204Restrictions for Auto LUN............................................................................................................205

Continuous Access Journal MxN configuration and control.............................................................205Overview......................................................................................................................................205Policy...........................................................................................................................................206horcm.conf...................................................................................................................................206Command specifications.............................................................................................................207

pairdisplay command.............................................................................................................207pairsplit command..................................................................................................................208

Notice on system operation.........................................................................................................210Configuration examples...............................................................................................................212

Duplication of RAID Manager applications.......................................................................................213Requirements for duplication of RAID Manager..........................................................................216Note for duplication of RAID Manager.........................................................................................217

Remote volume discovery................................................................................................................217Discovering a remote volume......................................................................................................218

7 Data protection operations with RAID Manager..............................................220Data protection operations................................................................................................................220

Data Retention.............................................................................................................................220Restrictions on Data Retention volumes................................................................................220

Protection parameters and operations..............................................................................................221Data Protection facility......................................................................................................................221

Data Protection Facility specifications.........................................................................................223Examples for configuration and protected volumes....................................................................224Operation authority with CMD security enabled..........................................................................225Target commands for protection..................................................................................................225permission command..................................................................................................................225New options for security..............................................................................................................226

raidscan -find inst...................................................................................................................226raidscan -find verify [MU#].....................................................................................................226raidscan -f[d]...........................................................................................................................226pairdisplay -f[d].......................................................................................................................226

Permitting protected volumes......................................................................................................227With a $HORCMPERM file....................................................................................................227Without a $HORCMPERM file: Commands to run on different operating systems................228

Environment variables.................................................................................................................228$HORCMPROMOD...............................................................................................................228$HORCMPERM.....................................................................................................................229

Determining the protection mode command device....................................................................2298 Examples of using RAID Manager commands................................................230

Group version control for mixed storage system configurations.......................................................230LDM volume discovery and flushing for Windows............................................................................230

Volume discovery function...........................................................................................................231Mountvol attached to Windows 2012/2008/2003/2000 systems.................................................233System buffer flushing function...................................................................................................233

Special facilities for Windows systems.............................................................................................236Signature changing facility for Windows systems.......................................................................236GPT disk for Windows.................................................................................................................238

Contents 7

Directory mount facility for Windows systems.............................................................................239Host group control............................................................................................................................240

Specifying a host group...............................................................................................................241Commands and options including a host group..........................................................................241

Using RAID Manager SLPR security................................................................................................242Specifying the SLPR Protection Facility......................................................................................243SLPR configuration examples.....................................................................................................243

9 Troubleshooting...............................................................................................248General troubleshooting...................................................................................................................248Operational notes and restrictions for RAID Manager operations....................................................249Error messages and error codes......................................................................................................251

System log messages.................................................................................................................251Command error messages..........................................................................................................253Generic error codes (horctakeover and pair commands)............................................................262Generic error codes (raidscan, raidqry, raidar, horcctl)...............................................................263Specific error codes.....................................................................................................................264SSB codes...................................................................................................................................265

SSB codes returned by the replication commands................................................................266SSB codes returned by the configuration setting command (raidcom)..................................267

Calling HPE technical support..........................................................................................................38710 Support and other resources.........................................................................389

Accessing Hewlett Packard Enterprise Support...............................................................................389Accessing updates............................................................................................................................389Related information...........................................................................................................................389Websites...........................................................................................................................................390Remote support................................................................................................................................390Documentation feedback..................................................................................................................390

A Warranty and regulatory information...............................................................392Warranty information.........................................................................................................................392Regulatory information......................................................................................................................392

Belarus Kazakhstan Russia marking...........................................................................................392Turkey RoHS material content declaration..................................................................................393Ukraine RoHS material content declaration................................................................................393

Index...................................................................................................................394

8 Contents

1 OverviewThis chapter provides an overview of the RAID Manager software and RAID Manager operationson the HPE RAID storage systems.

About RAID ManagerThe RAID Manager software enables you to perform storage system configuration and datamanagement operations by issuing commands to the HPE RAID storage systems:

• XP7 Storage (XP7)

• P9500

• XP24000/XP20000 Disk Array

• XP12000 Disk Array

• XP10000 Disk ArrayRAID Manager continues to provide the proven functionality that has been available for theXP24000/XP20000 Disk Array and previous storage system models, including in-systemreplication, remote replication, and data protection operations.In addition, RAID Manager for P9500 and later provides command-line access to the sameprovisioning and storage management operations that are available in the GUI software (forexample, Remote Web Console). RAID Manager commands can be used interactively or inscripts to automate and standardize storage administration functions, thereby simplifying the jobof the storage administrator and reducing administration costs.

NOTE: If a storage system rejects RAID Manager commands, verify the software licenses forthe storage system (for example, Continuous Access Synchronous) and the status of the softwareproduct and storage system.

RAID Manager functionsRAID Manager functions matrix

The following table lists and describes the RAID Manager functions available on the HPE storagesystems.

Table 1 Available RAID Manager functions on the storage system models

Storage systemFunction

XP7P9500XP24000/XP20000Disk Array

XP12000 DiskArray/XP10000 DiskArray

YesYesYesYesLocal copy (open)

YesYes*NoNoLocal copy (mainframe)

YesYesYesYesRemote copy (open)

YesYes*NoNoRemote copy (mainframe)

YesYesYesYesData protection

YesYesYesYesVSS configuration

YesYesYesYesSRM SRA

YesYesNoNoProvisioning (raidcom)

About RAID Manager 9

Table 1 Available RAID Manager functions on the storage system models (continued)

Storage systemFunction

XP7P9500XP24000/XP20000Disk Array

XP12000 DiskArray/XP10000 DiskArray

YesYesNoNoOut-of-band method

YesYesNoNoUser authentication

YesYesNoNoLDEV nickname

YesYesNoNoLDEV group

YesYesNoNoResource group

YesYesNoNoResource lock

*If DKCMAIN Microcode version of the P9500 storage system is 70-03-3x-xx/xx or later, the operation of Continuous AccessSynchronous MF, Continuous Access Journal MF, and Business Copy MF can be performed from RAID Manager.

Provisioning functionsThe raidcom configuration setting command enables you to perform provisioning functions,such as setting commands or creating LDEVs, from RAID Manager. For information about theconfiguration setting command (raidcom command), see “Provisioning operations with RAIDManager” (page 120).

Asynchronous command processingFor the raidcom configuration setting commands, asynchronous command processing is usedfor operations that take time to process on the storage system. Once an asynchronous commandhas been issued, you can execute additional commands without having to wait for theasynchronous command to complete. You can also monitor the completion status of asynchronouscommands by using a status reference command (for example, raidcom getcommand_status).

10 Overview

Command execution modesRAID Manager 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:

• Context check: This check is executed when a script file is specified by -zt option. It checksthe context of preceding commands and determines whether a subsequent command canbe executed.Specifying example:raidcom -zt <script_file>

• Configuration check: This check verifies that the actual storage system configuration isvalid (implemented) for the resources specified in the commands (for example, LDEVs,ports, pools).Syntax example:raidcom get ldev -ldev_id -cnt 65280 -store<work_file>

raidcom -zt <script_file> -load<work_file>

Precheck functionRAID Manager provides a precheck function for the configuration setting (raidcom) commandsthat checks the command before it is executed.In earlier versions of RAID Manager, an error was returned when the syntax of a command tobe executed was not correct. The precheck function checks the command syntax before thecommand is executed. To use the precheck function, specify either the -checkmode precheckoption or the -zt option.The following table shows the checking function combinations between the precheck functionand the transaction mode.

Table 2 Summary of the checking functions

ExecutionConfigcheck

Contextcheck

Syntaxcheck

Command syntax

ExecutedNot executedNot executedExecutedraidcom <command>

Not executedNot executedNot executedExecutedraidcom <command> -checkmode precheck

ExecutedNot executedExecutedExecutedraidcom -zt <script file>

ExecutedExecutedExecutedExecutedraidcom get ldev -ldev_id -cnt 65280-store<work_file>

raidcom -zt <script_file> -load <work_file>

Not executedNot executedExecutedExecutedraidcom -zt <script file> -checkmode precheck

Not executedExecutedExecutedExecutedraidcom get ldev -ldev_id -cnt 65280-store<work_file>

raidcom -zt <script_file> -load <work_file>-checkmode precheck

RAID Manager functions 11

Command execution by the in-band and out-of-band methodsThe two methods for issuing commands from a host are the in-band method and the out-of-bandmethod:

• In-band methodThe method issues a command from a UNIX/PC host connected directly to a storage systemvia Fibre Channel or iSCSI. Older RAID Manager versions (that do not support P9500) canonly issue commands by using the in-band method. In this method, when a command isissued, it is sent to the dedicated LDEV (command device) of the storage system selectedby the user via Fibre Channel or iSCSI from RAID Manager on the host.

• Out-of-band methodThis method issues commands from a UNIX/PC host connected to the storage system viaLAN. As shown in the following figure, RAID Manager supporting P9500 and later modelscan issue commands using the out-of-band method. Client PCs that are not connecteddirectly to storage systems can execute the same scripts as the in-band method.When a command is issued by using the out-of-band method, the command is sent to avirtual command device via LAN from RAID Manager on the host. Virtual command devicesare created when a command is executed using the out-of-band method. A virtual commanddevice can be created by specifying the location to create a virtual command device in theconfiguration definition file. For details on how to create command devices, see“HORCM_CMD (out-of-band method)” (page 32). Note, however, that the location you cancreate virtual command devices varies depending on the storage system models. For detailsabout the location, see “System configuration using RAID Manager” (page 57).

NOTE: If many commands are issued in a short period of time by using the out-of-bandmethod, for example issuing commands in a configuration with VMware Site RecoveryManager (SRM), or from scripts, the command response might slow. In this case, issuingcommands by using the in-band method is recommended.

TIP: For older versions of RAID Manager that do not support P9500, if you want to issuea command from a client PC which is not connected to a storage system directly, you mustwrite a remote shell script which is executed by your logging in to the RAID Manager serverof the in-band method via Telnet or SSH.

The following figure illustrates in-band and out-of-band RAID Manager operations. For detailsabout the in-band and out-of-band system configurations, see “System configuration using RAIDManager” (page 57).

12 Overview

Figure 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 3 Comparison of in-band and out-of-band operations

SpecificationCommandRoute

The requirement for user authentication depends on the setting ofuser authentication.

ReplicationIn-band

User authentication is required. User authentication mode of thecommand device must be enabled.

Provisioning

User authentication is required. For virtual command devices, userauthentication mode is always enabled.

ReplicationOut-of-band

User authentication is required. For virtual command devices, userauthentication mode is always enabled.

Provisioning

User authentication modeYou must enable the user authentication mode on the RAID Manager command device. For thevirtual command device the user authentication mode is always enabled.

RAID Manager functions 13

When user authentication mode is enabled, use the user ID and password that you created usingRemote Web Console to log in to the storage system.

LDEV nickname functionYou can assign a unique nickname of up to 32 characters to an LDEV.

LDEV grouping functionIn RAID Manager versions prior to the P9500, you needed to define the copy groups in the RAIDManager configuration definition file on each host. When the copy group information changed,the configuration definition file needed to be edited on each host. In RAID Manager versions afterthe P9500, the information registered in the storage system can be used. This LDEV groupingfunction can minimize the description of the RAID Manager configuration definition file on eachhost. When the copy group information changes, you need to update only one configurationdefinition file, saving time and eliminating the chance for error due to mismatching edits.The LDEV grouping functionality is implemented using device names, device groups, and copygroups:

• Device name:

A name that can be assigned to one LDEV per device group.◦◦ Each name is associated with a device group to which the LDEV belongs.

◦ An LDEV nickname can be assigned to the LDEV as a unique name for the LDEV thatis not related with a device group. Only one LDEV nickname can be assigned to eachLDEV.

• Device group:

A group of one or more LDEVs. One LDEV can belong to multiple device groups.◦◦ A device group can belong to only one copy group.

◦ If you want to construct a mirror or cascade, you need to define a different device groupand a device name in each copy group.

• Copy group: A group that is defined by specifying two device groups: one device group atthe primary site and one device group at the secondary site.

Resource group functionUsing Resource Group function, the storage administrator for each resource group can accessonly the resources in the resource group. The storage administrator cannot access resources inother resource groups. This prevents the risk of destroying the data by another storageadministrator in the other resource groups or of leaking out the data.

Resource locking functionThe resource locking function prevents conflict among multiple users.User scripts cannot be guaranteed to work correctly when multiple users are using the followingdifferent interfaces:

• Remote Web Console

• SVPYou can use the lock command while the script is running to ensure completion.To use the lockcommand, user authentication is required.

14 Overview

RAID Manager functions available on all RAID storage systemsRAID Manager provides the following functionality on all Hewlett Packard Enterprise RAID storagesystems.

• In-system replication

• Remote replication

• Data protection

In-system replicationRAID Manager provides command-line control for in-system (local) replication operations, includingBusiness Copy, Fast Snap, and Snapshot. RAID Manager displays local replication informationand allows you to perform operations by issuing commands or by executing script files.

Remote replicationRAID Manager provides command-line control for remote replication operations, includingContinuous Access Synchronous, Continuous Access Journal, and High Availability. RAIDManager displays remote replication information and allows you to perform operations by issuingcommands or by executing script files.For remote copy operations, RAID Manager interfaces with the system software andhigh-availability (HA) software on the host as well as the software on the RAID storage system.RAID Manager provides failover operation commands that support mutual hot standby inconjunction with industry-standard failover products (for example, MC/ServiceGuard, HACMP,FirstWatch®). RAID Manager also supports a scripting function for defining multiple operationsin a script (or text) file. Using RAID Manager scripting, you can set up and execute a large numberof commands in a short period of time while integrating host-based high-availability control overcopy operations.

Data protectionRAID Manager supports data protection operations, including Data Retention.

• Data Retention. The RAID Manager software enables you to set and verify the parametersfor guarding at the volume level. Once guarding is enabled, the RAID storage system concealsthe target volumes from SCSI commands such as SCSI Inquiry and SCSI Read Capacity,prevents reading and writing to the volume, and protects the volume from being used as acopy volume (the Continuous Access Synchronous, Continuous Access Journal, HighAvailability, or Business Copy paircreate operation fails).

RAID Manager functions available on all RAID storage systems 15

2 RAID Manager software environmentThis chapter describes the RAID Manager software environment.

Overview of the RAID Manager software environmentThe RAID Manager software environment includes components on the HPE RAID storage systemsand the RAID Manager software on the host servers and/or on the Remote Web Consolecomputer. The RAID Manager components on the storage systems include the user data volumesand RAID Manager command devices.Each RAID Manager instance on a host server includes:

• RAID Manager application files, referred to as HORC Manager (HORCM):

Log and trace files◦◦ A command server

◦ Error monitoring and event reporting files

◦ A configuration management feature

• Configuration definition file (user-defined)

• User execution environments for the HPE features, including the commands, a commandlog, and a monitoring function.

The RAID Manager commands also have interface considerations (see “RAID Manager and theSCSI command interface” (page 20)).

RAID Manager components on the RAID storage systemCommand device

RAID Manager commands are issued by the RAID Manager software to the RAID storage systemcommand device. The command device is a user-selected, dedicated logical volume on thestorage system that functions as the interface to the RAID Manager software on the host. Thecommand device is dedicated to RAID Manager communications and cannot be used by anyother applications. The command device accepts RAID Manager read and write commands thatare issued by the storage system. The command device also returns read requests to the host.The volume designated as the command device is used only by the storage system and is blockedfrom the user. The command device uses 32 MB, and the remaining volume space is reservedfor RAID Manager and its utilities. The command device can be any OPEN-x device (for example,OPEN-V) that is accessible to the host. A LUN Expansion volume cannot be used as a commanddevice. A Virtual LVI/Virtual LUN volume as small as 36 MB (for example, OPEN-3-CVS) can beused as a command device.

WARNING! Make sure the volume to be selected as the command device does not containany user data. The command device will be inaccessible to the host.

The RAID Manager software on the host issues read and write commands to the commanddevice. When RAID Manager receives an error notification in reply to a read or write request tothe RAID storage system, the RAID Manager software switches to an alternate command device,if one is defined. If a command device is blocked (for example, for online maintenance), you canswitch to an alternate command device manually. If no alternate command device is defined oravailable, all Continuous Access Synchronous and Business Copy commands terminateabnormally, and the host will not be able to issue commands to the storage system. Therefore,

16 RAID Manager software environment

one or more alternate command devices (see “Alternate command device function” (page 19))must be set to avoid data loss and storage system downtime.Each command device must be set using the LUN Manager software on Remote Web Console.In addition, for using a Provisioning command, user authentication is required. Set the securityattribute of the command device with user authentication. For information and instructions onsetting a command device, see the Provisioning Guide for the storage system.Each command device must also be defined in the HORCM_CMD section of the configurationdefinition file for the RAID Manager instance on the attached host. If an alternate commanddevice is not defined in the configuration definition file, the RAID Manager software might not beable to use the device.The RAID Manager Data Protection Facility uses an enhanced command device that has anattribute to indicate protection ON or OFF.

NOTE:• For Solaris operations, the command device must be labeled.

To enable dual path of the command device, make sure to include all paths to the commanddevice on a single line in the HORCM_CMD section of the configuration definition file. Thefollowing shows an example with two controller paths to the command device. Putting the pathinformation on separate lines might cause parsing issues, and failover might not occur unlessthe HORCM startup script is restarted.HORCM_CMD #dev_name dev_name dev_name /dev/rdsk/c1t66d36s2/dev/rdsk/c2t66d36s2

Command device guardingIn the customer environment, a command device might be attacked by the maintenance programof the Solaris Server, after that usable instance will be exhausted, and RAID Manager instancewould not start up on all servers (except attacked server). This might happen due to incorrectoperation of the maintenance personnel for the UNIX Server. In this case, the command deviceshould be protected against operator error, as long as it can be seen as the device file from themaintenance personnel.Thus, the RAID microcode (for the command device) and RAID Manager support this protectionin order to guard from similar access.

Guarding methodCurrently, assignment of the instance via the command device is ONE phase. Therefore, if thecommand device reads a special allocation area of the instance through the maintenance tooland so on, then it causes a fault of full space of the instance, because the command deviceinterprets as assignment of the instance from RAID Manager.RAID Manager has TWO phases that it reads to acquire usable LBA, and writes with the acquiredLBA in attaching sequence to the command device, so the command device can confirm whetherit was required as the assignment for RAID Manager or not, by detecting and adding two statusbits to the instance assignment table.

RAID Manager components on the RAID storage system 17

Figure 2 Current assignment sequence

Figure 3 Improved assignment sequence

The command device performs the assignment of an instance through TWO phases that have"temporary allocation (1 0)" and "actual allocation (1 1)" to the instance assignment table.If the command device is attacked, the instance assignment table is filled with "temporary allocation(1 0)" status. After that, the command device will detect a fault of full space as the instanceassignment, clear up all "temporary allocation (1 0)", and then reassign the required instanceautomatically.This does not require a service representative to switch the command device "OFF/ON" to clearup the instance table.

Verifying the RAID Manager instance numberRAID Manager provides a way to verify the number of "temporary allocations (1 0)" and "actualallocations (1 1)" on the instance table so that you can confirm validity of the RAID Managerinstance number in use. The horcctl -DI command shows the number of RAID Managerinstances since HORCM was started as follows.Example without command device security:# horcctl -DICurrent control device = /dev/rdsk/c0t0d0 AI = 14 TI = 0 CI = 1Example with command device security:# horcctl -DICurrent control device = /dev/rdsk/c0t0d0* AI = 14 TI = 0 CI = 1AI: NUM of actual instances in useTI: NUM of temporary instances in RAIDCI: NUM of instances using current (own) instance


Alternate command device functionThe RAID Manager software issues commands to the command device via the UNIX/PC rawI/O interface. If the command device fails in any way, all RAID Manager commands are terminatedabnormally, and you cannot use any commands. Because the use of alternate I/O path is platformdependent, restrictions are placed upon it. For example, on HP-UX systems, only devices subjectto the LVM can use the alternate path PV-LINK. To avoid command device failure, RAID Managersupports an alternate command device function.

• Definition of alternate command devices. To use an alternate command device, you mustdefine two or more command devices for the HORCM_CMD item in the configuration definitionfile. When two or more devices are defined, they are recognized as alternate commanddevices. Create all alternate command devices within the same resource group.

• Timing of alternate command devices. When the HORCM receives an error notificationin reply from the operating system via the raw I/O interface, the alternate command deviceis used. You can also change to the alternate command device forcibly by using thehorcct1 -C switch command. However, if you specified HORCM_CMD for the volumebelonging to a virtual storage machine, you cannot use the horcct1 -C switch command,and therefore you cannot switch to the alternate command device forcibly.

• Operation of alternating command. If the command device is blocked due to onlinemaintenance, the switch command should be issued in advance. If the switch command isissued again after completion of the online maintenance, the previous command device isactivated.

• Multiple command devices onHORCMstartup. If at least one command device is availableduring one or more command devices described to the configuration definition file, thenHORCM can start with a warning message to the startup log by using the available commanddevice. Confirm that all command devices can be changed by using the horcctl -Ccommand option, or HORCM has been started without the warning message to the HORCMstartup log.

Figure 4 Alternate command device function

Remote command deviceA remote command device is a command device on an external (Ext Stor) storage system thatis mapped as a command device of the local storage system. When commands are issued to aremote command device, the Cnt Ac-J/Cnt Ac-J MF journal operations are processed using theExt Stor FC path between the arrays. Use of a remote command device provides improvedperformance for 3DC configurations by providing separate paths for Cnt Ac-J/Cnt Ac-J MF journalprocessing and data replication.


The remote command device (RCD) requirements are:

• XP7 Storage:

RCD is required in 3DC Cnt Ac-S/Cnt Ac-J and 3DC Cnt Ac-S MF/Cnt Ac-J MFconfigurations, including intermix configurations with P9500 or XP24000/XP20000 DiskArray.

◦

◦ RCD is required in 3DC Cnt Ac-JxCnt Ac-J and 3DC Cnt Ac-J MFxCnt Ac-J MFconfigurations, including intermix configurations with P9500 or XP24000/XP20000 DiskArray.

◦ RCD is not required in HA 3DC delta resync (HA+Cnt Ac-J) configurations.

• P9500: RCD is recommended in 3DC Cnt Ac-S/Cnt Ac-J and 3DC Cnt Ac-S MF/Cnt Ac-JMF configurations. If there is intermix with XP7, RCD is required.

The remote command device is defined using Remote Web Console. For more information, seethe HP P9000 External Storage for Open and Mainframe Systems User Guide.

RAID Manager and the SCSI command interfaceWhen RAID Manager commands are converted into a special SCSI command format, a SCSIthrough driver that can send specially formatted SCSI commands to the RAID storage systemis needed. As a result, OS support for RAID Manager depends on the OS capabilities. It isnecessary to use a read/write command that can easily be issued by many UNIX/PC serverplatforms. For example, ioctl() can be used for the following platforms: HP-UX, Linux, Solaris,Windows, IRIX64, OpenVMS and zLinux.SCSI command format used. Use a RD/WR command that can be used with special LDEVs,since they should be discriminated from the normal RD/WR command.Recognition of the control command area (LBA#). The host issues control commands throughthe raw I/O special file of a special LDEV. Since the specific LU (command device) receivingthese commands is viewed as a normal disk by the SCSI interface, the OS can access its localcontrol area. The RAID storage system must distinguish such accesses from the control commandaccesses. Normally, several megabytes of the OS control area are used starting at the initialLBA#. To avoid using this area, a specific LBA# area is decided and control commands areissued within this area. The command LBA# recognized by the storage system is shown below,provided the maximum OS control area is 16 MB.

Figure 5 Relationship of the special file to the special LDEV

Acceptance of commands. A command is issued in the LBA area of the special LDEV explainedabove. The RD/WR command meeting this requirement should be received especially as a RAID


Manager command. A command is issued in the form of WR or WR-RD. When a command isissued in the form of RD, it is regarded as an inquiry (equivalent to a SCSI inquiry), and a RAIDManager recognition character string is returned.

Command competitionThe RAID Manager commands are asynchronous commands issued via the SCSI interface. Asa result, if several processes issue these commands to a single LDEV, the storage system cannottake the proper action. To avoid such a problem, two or more write commands should not beissued to a single LDEV. The command initiators should not issue two or more write commandsto a single LDEV unless the storage system can receive commands with independent initiatornumber * LDEV number simultaneously.

Figure 6 HORCM and command issue process

Command flowThis figure shows the flow of read/write command control for a specified LBA#.

Figure 7 Command flow

Issuing commands for LDEVs within a LUSE deviceA LUSE device is a group of LDEVs regarded as a single logical unit. Because it is necessaryto know the configuration of the LDEVs when issuing a command, a new command is used tospecify a target LU and acquire LDEV configuration data, as shown in the following figure.


Figure 8 LUSE Device and Command Issue

RAID Manager instance components on the host serverHORCM operational environment

The HORCM operates as a daemon process on the host server and is activated eitherautomatically when the server machine starts up or manually by the startup script. HORCM readsthe definitions specified in the configuration file upon startup. The environment variableHORCM_CONF is used to define the location of the configuration file to be referenced.

Figure 9 HORCM operational environment

RAID Manager instance configurationsThe basic unit of the RAID Manager software structure is the RAID Manager instance. A RAIDManager instance consists of HORC manager (HORCM), RAID Manager commands, theuser-defined configuration definition file, and the log function for maintenance. Each instanceuses its own configuration definition file to manage volume relationships while maintainingawareness of the other RAID Manager instances. Each RAID Manager instance normally resideson separate servers (one node per instance). If two or more instances are run on a single server(for example, for test operations), it is possible to activate two or more instances using instance


numbers. The RAID Manager commands to be used are selected by the environment variable(HORCC_MRCF). The default command execution environment for RAID Manager is ContinuousAccess Synchronous.The RAID Manager instance shown in the following figure has a remote execution link and aconnection to the RAID storage system. The remote execution link is a network connection toanother PC to allow you to execute RAID Manager functions remotely. The connection betweenthe RAID Manager instance and the storage system illustrates the connection between the RAIDManager software on the host and the command device. The command device accepts RAIDManager commands and communicates read and write I/Os between the host and the volumeson the storage system. The host does not communicate RAID Manager commands directly tothe volumes on the storage system -- the RAID Manager commands always go through thecommand device.

Figure 10 RAID Manager instance configuration & components

The four possible RAID Manager instance configurations are:

• One host connected to one storage system. Connecting one host to one storage systemallows you to maintain multiple copies of your data for testing purposes or as an offlinebackup. Each RAID Manager instance has its own operation manager, server software, andscripts and commands, and each RAID Manager instance communicates independentlywith the command device. The RAID storage system contains the command device thatcommunicates with the RAID Manager instances as well as the primary and secondaryvolumes of both RAID Manager instances.

• One host connected to two storage systems. Connecting the host to two storage systemsenables you to migrate data or implement disaster recovery by maintaining duplicate setsof data in two different storage systems. You can implement disaster recovery solutions by

RAID Manager instance components on the host server 23

placing the storage systems in different geographic areas. Each RAID Manager instancehas its own operation manager, server software, and scripts and commands, and each RAIDManager instance communicates independently with the command device. Each RAIDstorage system has a command device that communicates with each RAID Manager instanceindependently. Each storage system contains the primary volumes of its connected RAIDManager instance and the secondary volumes of the other RAID Manager instance (locatedon the same host in this case).

• Two hosts connected to one storage system. Having two attached hosts to one storagesystem, one host for the primary volume and the other host for the secondary volume, allowsyou to maintain and administer the primary volumes while the secondary volumes can betaken offline for testing. The RAID Manager instances of separate hosts are connected viathe LAN so that they can maintain awareness of each other. The RAID storage systemcontains the command device that communicates with both RAID Manager instances (oneon each host) and the primary and secondary volumes of both RAID Manager instances

• Two hosts connected to two storage systems. Two hosts connected to two storage systemsalso allows the most flexible disaster recovery plan, because both sets of data areadministered by different hosts. This guards against storage system failure as well as hostfailure.The RAID Manager instances of separate hosts are connected via the LAN so thatthey can maintain awareness of each other. Each RAID storage system has a commanddevice that communicates with each RAID Manager instance independently. Each storagesystem contains the primary volumes of its connected RAID Manager instance and thesecondary volumes of the other RAID Manager instance (located on a different host in thiscase).

Host machines that can be pairedWhen you perform a pair operation, the version of RAID Manager should be the same on theprimary and secondary sites. As a particular application uses HORC, users sometimes use aHORC volume as the data backup volume for the server. In this case, RAID Manager requiresthat the RAID Manager instance correspond to each OS platform that is located on the secondarysite for the pair operation of data backup on the primary servers of each OS platform.However, it is possible to prepare only one server at a secondary site by supporting RAID Managercommunications among different OSs (including the converter for little-endian vs. big-endian).Figure 11 (page 25) represents RAID Manager's communication among different OSs, andTable 4 (page 25) shows the supported communication (32-bit, 64-bit, MPE/iX) among differentOSs. Please note the following terms that are used in the example:

• RM-H: Value of HORCMFCTBL environment variable for an HP-UX RAID Manager instanceon Windows

• RM-S: Value of HORCMFCTBL environment variable for a Solaris RAID Manager instanceon Windows

Restriction: RAID Manager for MPE/iX cannot communicate with 64-bit HORCM.Restriction: RAID Manager's communications among different operating systems is supportedon HP-UX, Solaris, AIX, Linux, and Windows (this is not supported on Tru64 UNIX/Digital UNIX).Also, RAID Manager does not require that the HORCMFCTBL environment variable be set—exceptfor RM-H and RM-S instances (to ensure that the behavior of the operating system platform isconsistent across different operating systems).


Figure 11 RAID Manager communication among different operating systems

Table 4 Supported RAID Manager (HORCM) communication

MPE/iXHORCM 64 bitHORCM 32 bitHORCM

bigbiglittlebiglittle

AV-AVAVAVlittle32 bit

AV-AVAVAVbig

NA-AVAVAVlittle64 bit

-----big

AV-NAAVAVbigMPE/iX

Configuration definition fileThe RAID Manager configuration definition file is a text file that defines a RAID Manager instance.The connected hosts, volumes and groups known to the RAID Manager instance are defined inthe configuration definition file. Physical volumes (special files) used independently by the serversare combined when paired logical volume names and group names are given to them. Theconfiguration definition file describes the correspondence between the physical volumes usedby the servers and the paired logical volumes and the names of the remote servers connectedto the volumes. See the RAID Manager Installation and Configuration Guide for instructions oncreating the RAID Manager configuration definition file.Figure 12 (page 26) illustrates the configuration definition of paired volumes.


Figure 12 Configuration definition of paired volumes

Configuration file example — UNIX-based serversNote that # at the beginning of a line indicates a comment.HORCM_MON#ip_address service poll(10ms) timeout(10ms)HST1 horcm 1000 3000

HORCM_CMD#unitID 0... (seq#30014)#dev_name dev_name dev_name/dev/rdsk/c0t0d0#unitID 1... (seq#30015)#dev_name dev_name dev_name/dev/rdsk/c1t0d0

HORCM_DEV#dev_group dev_name port# TargetID LU# MU#oradb oradb1 CL1-A 3 1 0oradb oradb2 CL1-A 3 1 1oralog oralog1 CL1-A 5 0oralog oralog2 CL1-A1 5 0oralog oralog3 CL1-A1 5 1oralog oralog4 CL1-A1 5 1 h1HORCM_INST#dev_group ip_address serviceoradb HST2 horcmoradb HST3 horcmoralog HST3 horcm

Configuration file example — Windows servers


The following table lists the parameters defined in the configuration file and specifies the defaultvalue, type, and limit for each parameter.

Table 5 Configuration (HORCM_CONF) parameters

LimitTypeDefaultParameter

63 charactersCharacter stringNoneip_address

15 charactersCharacter string or numeric valueNoneService

NoneNumeric value11000poll (10 ms)

NoneNumeric value13000timeout (10 ms)

63 charactersCharacter stringNonedev_name forHORCM_CMD Recommended value = 8 char.

or fewer

31 charactersCharacter stringNonedev_name forHORCM_DEV

31 charactersCharacter stringNonedev_groupRecommended value = 8 char.or less

31 charactersCharacter stringNoneport #

7 charactersNumeric value1Nonetarget ID

7 charactersNumeric value1NoneLU#

7 charactersNumeric value10MU#

12 charactersNumeric valueNoneSerial#2

6 charactersNumeric valueNoneCU:LDEV(LDEV#)

63 charactersCharacter stringNonedev_name forHORCM_CMD Recommended value = 8 char.

or less

Notes:


Table 5 Configuration (HORCM_CONF) parameters (continued)

LimitTypeDefaultParameter

1. Use decimal notation for numeric values (not hexadecimal).2. For XP7, 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 RAID Manager is running. Shut down RAIDManager, edit the configuration file as needed, and then restart RAID Manager.When you change the system configuration, it is required to shut down RAID Manager once andrewrite the configuration definition file to match with the change and then restart RAID Manager.When you change the storage system configuration (microprogram, cache capacity, LU path,and so on), you need to restart RAID Manager regardless of the necessity of the configurationdefinition file editing.When you restart RAID Manager, confirm that there is no contradiction in the connectionconfiguration by using the "-c" option of pairdisplay command and raidqry command. But youcannot confirm the consistency of the P-VOL and S-VOL capacity with the "-c" option of pairdisplaycommand. Confirm the capacity of each volume.Do not mix pairs created with the "At-Time Split" option (-m grp) and pairs created without thisoption in the same group defined in the RAID Manager configuration file. If you do, a pairsplitoperation might end abnormally, or S-VOLs of the P-VOLs in the same consistency group (CTG)might not be created correctly at the time the pairsplit request is received.

Configuration definition file settingsThis section describes the settings in the configuration definition file:

• “HORCM_MON” (page 28)

• “HORCM_CMD (in-band method)” (page 29)

• “HORCM_CMD (out-of-band method)” (page 32)

• “HORCM_DEV” (page 34)

• “HORCM_INST” (page 36)

• “HORCM_LDEV” (page 36)

• “HORCM_LDEVG” (page 37)

• “HORCM_INSTP” (page 37)

• “HORCM_ALLOW_INST” (page 38)

HORCM_MONThe monitor parameter (HORCM_MON) defines the following values:

• Ip_address: Specifies the local host name or the IP address of the local host. When youspecify the name of a local host that has multiple IP addresses, one of the IP addresses isselected at random and used. If you want to use all IP addresses, specify NONE for IPv4or NONE6 for IPv6.

• Service: Specifies the UDP port name assigned to the HORCM communication path, whichis registered in "/etc/services" ("%windir%\system32\drivers\etc\services" in Windows,"SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT" in OpenVMS). If a port numberis specified instead of a port name, the port number will be used.


• Poll: The interval for monitoring paired volumes. To reduce the HORCM daemon load, makethis interval longer. If set to -1, the paired volumes are not monitored. The value of -1 isspecified when two or more RAID Manager instances run on a single machine.

• Timeout: The time-out period of communication with the remote server.If HORCM_MON is not specified, then the following are set as defaults.HORCM_MON

#ip_address service poll(10ms) timeout(10ms)

NONE default_port 1000 3000H

Default_port:For none specified HORCM instance: "31000 + 0"For instance HORCM X : "31000 + X + 1"

HORCM_CMD (in-band method)When using the in-band method, define the UNIX device path or Windows physical device numberand specify a command device that can be accessed by RAID Manager for HORCM_CMD. Youcan specify multiple command devices in HORCM_CMD to provide failover in case the originalcommand device becomes unavailable.

TIP: To enhance redundancy, you can make multiple command devices available for a singlestorage system. This configuration is called command device alternative configuration. For thisconfiguration, command devices are listed horizontally in a line in the configuration definition file.CMD1 and CMD2 in the following example are command devices of the same storage system:HORCM_CMDCMD1 CMD2

Aside from the command device alternative configuration, to control multiple storage systems inone configuration definition file, you can list command devices of each storage system in oneconfiguration definition file. In this case, command devices are listed vertically. CMD1 and CMD2in the following example are command devices of different storage systems:HORCM_CMDCMD1CMD2

The command device must be mapped to the iSCSI/Fibre using LUN Manager first. The mappedcommand devices can be identified by the "-CM" at the end of product ID displayed by the inqraidcommand. The following are the examples for the inqraid command.Example for the inqraid command (UNIX host)# ls /dev/rdsk/c1t0* | /HORCM/usr/bin/inqraid -CLI -sortDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID

c1t0d0s2 CL2-E 63502 576 - - - - OPEN-V-CM

c1t0d1s2 CL2-E 63502 577 - s/s/ss 0006 1:02-01 OPEN-V -SUN

c1t0d2s2 CL2-E 63502 578 - s/s/ss 0006 1:02-01 OPEN-V -SUN

The command device is /dev/rdsk/c1t0d2s2.Example for the inqraid command (Windows host)D:\HORCM\etc>inqraid $Phys –CLI

\\.\PhysicalDrive1:

# Harddisk1 -> [VOL61459_449_DA7C0D92] [OPEN-3 ]

\\.\PhysicalDrive2:

# Harddisk2 -> [VOL61459_450_DA7C0D93] [OPEN-3-CM ]


The command device is \\.\PhysicalDrive2.After the process of command device mapping, set HORCM_CMD of the configuration definitionfile as follows.

• \\.\CMD-<Serial Number>:<Device special file name><Serial Number>: Sets the serial number. For XP7, add a “3” at the beginning of the serialnumber. For example, for serial number 12345, enter 312345.<Device special file name>: Sets the device special file name of a command device.

ExampleWhen the serial number, 64015 and device special file name, /dev/rdsk/*is specified:HORCM_CMD#dev_name dev_name dev_name\\.\CMD-64015:/dev/rdsk/*

CAUTION: To enable dual path of the command device under UNIX systems, make sure toinclude all paths to the command device on a single line in the HORCM_CMD section of theconfiguration definition file. Entering path information on separate lines might cause syntaxparsing issues, and failover might not occur unless the HORCM startup script is restarted on theUNIX system.

When two or more storage systems are connected, RAID Manager identifies each storage systemusing unit IDs. The unit ID is assigned sequentially in the order described in HORCM_CMD ofthe configuration definition file. For a command device alternative configuration, a special file formultiple command devices is written.

CAUTION: When storage systems are shared by two or more servers, unit IDs and serialnumbers must be consistent among the servers. List serial numbers of the storage systems inHORCM_CMD of the configuration definition file in the same order. The following figure illustratesunit IDs when multiple servers share multiple storage systems.

Figure 13 Configuration and unit IDs for multiple storage systems

For Windows 2000, 2003, 2008, and 2012


Normally, physical drives are specified for command devices in storage systems. However, RAIDManager provides a method that is not affected by changes of physical drives in Windows 2000,2003, 2008, and 2012 by using the following naming format to specify the serial number, LDEVnumber, and port number in that order:\\.\CMD-Ser#-ldev#-Port#

NOTE: For XP7, 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 number, 250 for the LDEVnumber, and CL1-A for the port number:HORCM_CMD#dev_name dev_name dev_name\\.\CMD-30095-250-CL1-A

• Minimum specificationFor the command device with serial number 30095, specify as follows:\\.\CMD-30095

• Command devices in the multi-path environmentSpecify serial number 30095, and LDEV number 250 as follows:\\.\CMD-30095-250

• Other specificationsSpecify serial number 30095, LDEV number 250, and port number CLI-A as follows:\\.\CMD-30095-250-CL1-A

or\\.\CMD-30095-250-CL1

For UNIXDevice files are specified for command devices in UNIX. However, RAID Manager provides amethod that is not affected by changes of device files in UNIX by using the following namingformat specifying the serial number, LDEV number, and port number in that order:\\.\CMD-Ser#-ldev#-Port#:HINT

NOTE: For XP7, 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 number, 250 for the LDEVnumber, and CL1-A for the port number:HORCM_CMD#dev_name dev_name dev_name\\.\CMD-30095-250-CL1-A:/dev/rdsk/

HINT provides a path to scan and specifies a directory ending with a slash (/) or a name patternincluding the directory. Device files are searched via a name filter similar to the inqraid command.

• To find command devices from /dev/rdsk/, enter: ' /dev/rdsk/*

• To find command devices from /dev/rdsk/c10, enter: ' /dev/rdsk/c10*

• To find command devices from /dev/rhdisk, enter: ' /dev/rhdisk*

For a command device alternative configuration , HINT of the second command device can beomitted. In this case, command devices are searched from the device file that was scanned first.


HORCM_CMD#dev_name dev_name dev_name\\.\ CMD-30095-CL1:/dev/rdsk/ \\.\ CMD-30095-CL2

• Minimum specificationFor the command device of a storage system with serial number 30095, specify as follows:\\.\CMD-30095:/dev/rdsk/

• Command devices in the multi-path environmentSpecify storage system’s serial number 30095 and LDEV number 250 as follows:\\.\CMD-30095-250:/dev/rdsk/

• Other specificationsAn alternate path with storage system’s serial number 30095 and LDEV number 250 canbe specified as follows:\\.\CMD-30095-250-CL1:/dev/rdsk/ \\.\CMD-30095-250-CL2\\.\CMD-30095:/dev/rdsk/c1 \\.\CMD-30095:/dev/rdsk/c2

NOTE: If the hardware configuration is changed during the time an OS is running in Linux, thename of a special file corresponding to the command device might be changed. At this time, ifHORCM was started by specifying the special file name in the configuration definition file, HORCMcannot detect the command device, and the communication with the storage system might fail.To prevent this failure, specify the path name allocated by udev to the configuration definitionfile before booting HORCM. Use the following procedure to specify the path name. In this example,the path name for /dev/sdgh can be found.1. Find the special file name of the command device by using inqraid command. Command

example:[root@myhost ~]# ls /dev/sd* | /HORCM/usr/bin/inqraid -CLI | grepCM sda CL1-B 30095 0 - - 0000 A:00000 OPEN-V-CM sdgh CL1-A 30095 0- - 0000 A:00000 OPEN-V-CM [root@myhost ~]#

2. Find the path name from the by-path directory. Command example:[root@myhost ~]# ls -l /dev/disk/by-path/ | grep sdgh lrwxrwxrwx.1 root root 10 Jun 11 17:04 2015 pci-0000:08:00.0-fc-0x50060e8010311940-lun-0 -> ../../sdgh [root@myhost ~]#

In this example, "pci-0000:08:00.0-fc-0x50060e8010311940-lun-0" is the path name.3. Enter the path name to HORCM_CMD in the configuration definition file as follows.

HORCM_CMD /dev/disk/by-path/pci-0000:08:00.0-fc-0x50060e8010311940-lun-0

4. Boot the HORCM instance as usual.

HORCM_CMD (out-of-band method)When executing commands using the out-of-band method, use a virtual command device insteadof a command device. By specifying the location to create a virtual command device inHORCM_CMD, you can create a virtual command device.To create a virtual command deviceSpecify 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.

• <UDP communication port number>: Sets the UDP communication port number. This value(31001) is fixed.

• [-Unit ID]: Sets the unit ID of the storage system for the multiple units connection configuration.This can be omitted.

To use a RAID Manager server port as a virtual command device:Specify the following in HORCM_CMD of the configuration definition file:\\.\IPCMD-<RAID Manager server IP address>-<RAID Manager port number>[-UnitID]

• <RAID Manager server IP address>: Sets the IP address of the RAID Managerserver.

• <RAID Manager port number>: Sets the RAID Manager port number.

• [-Unit ID]: Sets the unit ID of the storage system for the multiple units connectionconfiguration. This can be omitted.

ExamplesThe following expresses the case of IPv4.HORCM_CMD#dev_name dev_name dev_name\\.\IPCMD-158.214.135.113-31001

The following expresses the case of IPv6.HORCM_CMD#dev_name dev_name dev_name\\.\IPCMD-fe80::209:6bff:febe:3c17-31001

The following expresses the case when both the in-band and out-band methods are used:HORCM_CMD#dev_name dev_name dev_name\\.\CMD-64015:/dev/rdsk/* \\.\IPCMD-158.214.135.113-31001

The following expresses the case when both the in-band and out-band methods are used in acommand device alternative configuration:HORCM_CMD#dev_name dev_name\\.\CMD-64015:/dev/rdsk/* \\.\IPCMD-158.214.135.113-31001HORCM_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 (threeunits):HORCM_CMD#dev_name dev_name dev_name\\.\IPCMD-158.214.135.113-31001\\.\IPCMD-158.214.135.114-31001\\.\IPCMD-158.214.135.115-31001

HORCM_CMD#dev_name dev_name dev_name\\.\IPCMD-192.168.0.16-31001\\.\IPCMD-192.168.0.17-31001\\.\IPCMD-192.168.0.16-31002\\.\IPCMD-192.168.0.17-31002

An IP address and a port number can be expressed using a host name and a service name.


HORCM_DEVThe device parameter (HORCM_DEV) defines the RAID storage system device addresses forthe paired logical volume names. When the server is connected to two or more storage systems,the unit ID is expressed by port# extension. Each group name is a unique name discriminatedby a server that uses the volumes, the attributes of the volumes (such as database data, redolog file, UNIX file), recovery level, etc. The group and paired logical volume names described inthis item must reside in the remote server. The hardware iSCSI/Fibre port, target ID, and LUNas hardware components need not be the same.The following values are defined in the HORCM_DEV parameter:

• dev_group: Names a group of paired logical volumes. A command is executed for allcorresponding volumes according to this group name.

• dev_name: Names the paired logical volume within a group (that is, name of the special fileor unique logical volume). The name of paired logical volume must be different to the devname in another group.

• Port#: Defines the RAID storage system port number of the volume that connects to thedev_name volume. The following "n" shows unit ID when the server is connected to two ormore 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).

OptionOptionOptionBasic-

RnQnPnNnMnLnKnJnHnGnFnEnDnCnBnAnCL1

RnQnPnNnMnLnKnJnHnGnFnEnDnCnBnAnCL2

The following ports can be specified only for the XP1024/XP128 Disk Array:


rnqnpnnnmnlnknjnhngnfnendncnbnanCL3


For XP1024/XP128 Disk Array, RAID Manager supports four types of port names for host groups:• Specifying the port name without a host group: CL1-A CL1-An, where n is the unit ID if

there are multiple RAID storage systems• Specifying the port name with a host group: CL1-A-g, where g is the host group CL1-An-g,

where n-g is the host group g on CL1-A in unit ID=nThe following ports can be specified for XP24000/XP20000 Disk Array and XP12000 DiskArray/XP10000 Disk Array:







rnqnpnnnmnlnknjnhngnfnendncnbnanCLA

rnqnpnnnmnlnknjnhngnfnendncnbnanCLB



rnqnpnnnmnlnknjnhngnfnendncnbnanCLC

rnqnpnnnmnlnknjnhngnfnendncnbnanCLD

rnqnpnnnmnlnknjnhngnfnendncnbnanCLE

rnqnpnnnmnlnknjnhngnfnendncnbnanCLF

rnqnpnnnmnlnknjnhngnfnendncnbnanCLG

• Target ID: Defines the iSCSI/Fibre target ID (TID) number of the physical volume on thespecified port.

• LU#: Defines the iSCSI/Fibre logical unit number (LU#) of the physical volume on the specifiedtarget ID and port.

NOTE: In case of fibre channel, if the TID and LU# displayed on the system are differentthan the TID on the fibre address conversion table, then you must use the TID and LU#indicated by the raidscan command in the RAID Manager configuration file.

• MU# for Business Copy (HOMRCF): Defines the mirror unit number (0 - 2) to use theredundant mirror for the identical LU on the Business Copy. If this number is omitted, it isassumed to be (MU#0). The cascaded mirroring of the S-VOL is expressed as virtual volumesusing the mirror descriptors (MU#1-2) in the configuration definition file. The MU#0 of amirror descriptor is used for connection of the S-VOL. The mirror descriptor (MU#0-2) canbe used in Business Copy and Snapshot. MU#3-63 can be used in Snapshot only.

NOTE: When you enter the MU number for a Business Copy/Business Copy/Snapshotpair into the configuration definition file, enter only the number, for example, “0” or “1”.

S-VOLP-VOLSMPLFeature

MU#1 - 63MU#0MU#3 - 63MU#0-2MU#3 - 63MU#0-2

Not validValidNot validValidNot validValidBusiness Copy

Not validValidValidValidValidValidSnapshot

• MU# for Continuous Access Synchronous/Continuous Access Journal/High Availability:Defines the mirror unit number (0 - 3) if using redundant mirror for the identical LU on CntAc-S/Cnt Ac-J/HA. If this number is omitted, it is assumed to be (MU#0). You can specifyonly MU#0 for Continuous Access Synchronous, and 4 MU numbers (MU#0 - 3) forContinuous Access Journal and High Availability.

NOTE: When you enter the MU number for a Cnt Ac-S/Cnt Ac-J/HA pair into theconfiguration definition file, add an "h" before the number, for example, "h0" or "h1".

S-VOLP-VOLSMPLFeature

MU#1 - 3MU#0MU#1 - 3MU#0MU#1 - 3MU#0

Not validValidNot validValidNot validValidContinuousAccessSynchronous

ValidValidValidValidValidValidCnt Ac-J


HORCM_INSTThe instance parameter (HORCM_INST) defines the network address (IP address) of the remoteserver (active or standby). It is used to view or change the status of the paired volume in theremote server (active or standby). When the primary volume is shared by two or more servers,there are two or more remote servers using the secondary volume. Thus, it is necessary todescribe 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.

• ip_address: The network address of the specified remote server.

• service: The port name assigned to the HORCM communication path (registered in the/etc/services file). If a port number is specified instead of a port name, the port number willbe used.

A configuration for multiple networks can be found using the raidqry -r <group> commandon each host. The current HORCM network address can be changed using horcctl -NC<group> on each host.When you use all IP addresses of the local host in a configuration for multiple networks, specifyNONE (for IPv4) or NONE6 (for IPv6) to the ip_address of the HORCM_MON parameter.

Figure 14 Configuration for multiple networks

HORCM_LDEVThe HORCM_LDEV parameter is used for specifying stable LDEV# and Serial# as the physicalvolumes corresponding to the paired logical volume names. Each group name is unique andtypically has a name fitting its use (for example, database data, Redo log file, UNIX file). The


group and paired logical volume names described in this item must also be known to the remoteserver.

• dev_group: This parameter is the same as HORCM_DEV parameter.

• dev_name: This parameter is the same as HORCM_DEV parameter.

• MU#: This parameter is the same as HORCM_DEV parameter.

• Serial#: This parameter is used to specify the serial number of RAID box. For XP7, add a“3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

• CU:LDEV(LDEV#): This parameter is used to describe the LDEV number in the RAID storagesystem and supports three types of format as LDEV#.#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#

oradb dev1 30095 02:40 0oradb dev2 30095 02:41 0

◦ Specifying "CU:LDEV" in hex.Example for LDEV# 260:01:04

◦ Specifying "LDEV" in decimal used by the RAID Manager inqraid command.Example for LDEV# 260:260

◦ Specifying "LDEV" in hex used by the RAID Manager inqraid command.Example for LDEV# 260:0x104

NOTE: The HORCM_LDEV format can only be used on the XP12000 DiskArray/XP10000 Disk Array. LDEV# will be converted to "Port#, Targ#, Lun#" mappingto this LDEV internally, because the RAID storage system needs to specify "Port#,Targ#, Lun#" for the target device. This feature is XP12000 Disk Array/XP10000 DiskArray microcode dependent; if HORCM fails to start, HORCM_DEV needs to be used.

HORCM_LDEVGThe HORCM_LDEVG parameter defines the device group information that the RAID Managerinstance reads. For details about device group, see “LDEV grouping function” (page 82).The following values are defined.

• Copy group: specifies a name of copy group. This is equivalent to the dev_group ofHORCM_DEV and HORCM_LDEV parameters.RAID Manager operates by using the information defined here.

• ldev_group: Specifies a name of device group that the RAID Manager instance reads.

• Serial#: Specifies a storage system serial number. For XP7, add a “3” at the beginning ofthe serial number. For example, for serial number 12345, enter 312345.

HORCM_LDEVG#Copy_Group ldev_group Serial#ora grp1 64034

HORCM_INSTPThe HORCM_INSTP parameter is used when specifying a path ID for the link of ContinuousAccess Synchronous/Continuous Access Journal/High Availability 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, thebehavior is the same as when 'HORCM_INST' is used.HORCM_INSTPdev_group ip_address service pathIDVG01 HSTA horcm 1VG02 HSTA horcm 2

Note: The path ID can be specified at Continuous Access Synchronous, Continuous AccessJournal, Continuous Access Journal MF, and High Availability. However, the path ID cannot bespecified at Cnt Ac-J/Cnt Ac-J MF when connecting XP24000/XP20000 Disk Array and XP12000Disk Array/XP10000 Disk Array. The same path ID must be specified between the site of P-VOLand S-VOL because the path ID is used at the paircreate command.

HORCM_ALLOW_INSTThe HORCM_ALLOW_INST parameter is used to restrict the users using the virtual commanddevice. The allowed IP addresses and port numbers are as follows.For IPv4HORCM_ALLOW_INST#ip_address service158.214.135.113 34000158.214.135.114 34000

For IPv6HORCM_ALLOW_INST#ip_address servicefe80::209:6bff:febe:3c17 34000

Note: If RAID Manager clients not defined HORCM_ALLOW_INST, HORCM instance startingup is rejected by SCSI check condition (SKEY=0x05, ASX=0xfe) and RAID Manager cannot bestarted up.

Correspondence of the configuration definition file for cascading volume and mirrordescriptors

The RAID Manager software (HORCM) is capable of keeping a record of the multiple pairconfigurations per LDEV. RAID Manager distinguishes the records of the each pair configurationby MU#. You can assign 64 MU#s for local copy products and 4 MU#s for remote copy productsas the following figure, you can define up to 68 device groups (records of pair configuration) inthe configuration definition file.

Figure 15 Management of Pair configuration by Mirror Descriptors


Correspondence of configuration file and mirror descriptorsThe group name and MU# that are noted in the HORCM_DEV section of the configurationdefinition file are assigned to the corresponding mirror descriptors. This outline is described inthe following table. "Omission of MU#" is handled as MU#0, and the specified group is registeredto MU#0 on Business Copy/Snapshot and Continuous Access Synchronous/Continuous AccessJournal/High Availability. Also, when you note the MU# in HORCM_DEV, the sequence of theMU# can be random (for example, 2, 1, 0).

Table 6 Assignments of Group name and MU# to Mirror Descriptors

Cnt Ac-J/HABusiness Copy(Snapshot) Only

MU#0HORCM_DEV Parameter in Configuration File

MU#1-#3MU#1-#2BCCnt Ac-S/Cnt Ac-J/HA (MU#3-#63)

--oradev1oradev1HORCM_DEV

#dev_group dev_name port# TargetID LU# MU#

Oradb oradev1 CL1-D 2 1

-oradev11oradev1oradev1HORCM_DEV

oradev21#dev_group dev_name port# TargetID LU# MU#


Oradb1 oradev11 CL1-D 2 1 1


-oradev21oradev11oradev1HORCM_DEV






--oradev1-HORCM_DEV


Oradb oradev1 CL1-D 2 1 0

---oradev1HORCM_DEV


Oradb oradev1 CL1-D 2 1 h0

-oradev11oradev1-HORCM_DEV


Oradb oradev1 CL1-D 2 1 0



oradev21-oradev11oradev1HORCM_DEV

#dev_group dev_name port# TargetID LU# MU# oradev31

Oradb oradev1 CL1-D 2 1 oradev41


Oradb2 oradev21 CL1-D 2 1 h1




Cascading connection and configuration filesA volume of the cascading connection describes entity in a configuration definition file on thesame instance, and classifies connection of volume through the mirror descriptor. In case ofContinuous Access Synchronous/Business Copy cascading connection, too, the volume entitydescribes to a configuration definition file on the same instance. The following figure shows anexample of this.

Figure 16 Business Copy cascade connection and configuration file

Business CopySince Business Copy is a mirrored configuration within one storage system, it can be describedas a volume of the cascading connection according to two configuration definition files. For aBusiness Copy-only cascading connection, the specified group is assigned to the mirror descriptor(MU#) of Business Copy, specifically defining "0" as the MU# for Business Copy. Figure 17(page 41) - Figure 19 (page 41) show Business Copy cascading configurations and the pairdisplayinformation for each configuration.


Figure 17 Pairdisplay on HORCMINST0



Cascading connections for Continuous Access Synchronous and Business CopyThe cascading connections for Continuous Access Synchronous/Business Copy can be set upby using three configuration definition files that describe the cascading volume entity in aconfiguration definition file on the same instance. The mirror descriptor of Business Copy and


Continuous Access Synchronous definitely describe "0" as MU#, and the mirror descriptor ofContinuous Access Synchronous does not describe "0" as MU#.

Figure 20 Continuous Access Synchronous/Business Copy cascading connection andconfiguration file

Figure 21 (page 42) through Figure 24 (page 44) show Continuous Access Synchronous/BusinessCopy cascading configurations and the pairdisplay information for each configuration.

Figure 21 Pairdisplay for Continuous Access Synchronous on HOST1


Figure 22 Pairdisplay for Continuous Access Synchronous on HOST2 (HORCMINST)

Figure 23 Pairdisplay for Business Copy on HOST2 (HORCMINST)


Figure 24 Pairdisplay for Business Copy on HOST2 (HORCMINST0)

RAID Manager software filesThe RAID Manager 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.

• “RAID Manager files supplied with the software” (page 44)

• “RAID Manager log and trace files” (page 48)

• “User environment variable” (page 56)

RAID Manager files supplied with the software• “RAID Manager files for UNIX-based systems” (page 44)

• “RAID Manager files for Windows-based systems” (page 45)

• “RAID Manager files for OpenVMS-based systems” (page 47)

RAID Manager files for UNIX-based systems

GroupUser*1ModeCommand nameFile nameTitle

sysroot0544horcmd/etc/horcmgrHORCM

sysroot0444-/HORCM/etc/horcm.confHORCM_CONF

sysroot0544horctakeover/usr/bin/horctakeoverTakeover

sysroot0544paircurchk/usr/bin/paircurchkAccessibility check

sysroot0544paircreate/usr/bin/paircreatePair generation

sysroot0544pairsplit/usr/bin/pairsplitPair splitting

sysroot0544pairresync/usr/bin/pairresyncPair resynchronization

sysroot0544pairevtwait/usr/bin/pairevtwaitEvent waiting

sysroot0544pairmon/usr/bin/pairmonError notification

sysroot0544pairvolchk/usr/bin/pairvolchkVolume check


GroupUser*1ModeCommand nameFile nameTitle

sysroot0544pairdisplay/usr/bin/pairdisplayPair configurationconfirmation

sysroot0544raidscan/usr/bin/raidscanRAID scanning

sysroot0544raidar/usr/bin/raidarRAID activity reporting

sysroot0544raidqry/usr/bin/raidqryConnection confirming

sysroot0544horcctl/usr/bin/horcctlTrace control

sysroot0544horcmstart.sh/usr/bin/horcmstart.shHORCM activationscript

sysroot0544horcmshutdown.sh/usr/bin/horcmshutdown.shHORCM shutdownscript

sysroot0544--/HORCM/usr/bin/inqraidConnection confirming

sysroot0544pairsyncwait/usr/bin/pairsyncwaitSynchronous waiting

sysroot0544raidcfg/HORCM/usr/bin/raidcfgConfiguration settingand confirmingcommand

sysroot0544rmawk/HORCM/usr/bin/rmawkText filtering

sysroot0544raidvchkset/usr/bin/raidvchksetDB Validator setting

sysroot0544raidvchkdsp/usr/bin/raidvchkdspDB Validatorconfirmation

sysroot0544raidvchkscan/usr/bin/raidvchkscanDB Validatorconfirmation

sysroot0544rmsra/HORCM/usr/bin/rmsraStorage ReplicationAdapter

sysroot0544raidcomHORCM/usr/bin/raidcomConfiguration settingcommand

sysroot0644-HORCM/etc/Raidcom_Dic_Raid_RMXP_Patch.txtA file for management

sysroot0644-HORCM/etc/Raidcom_Help_Raid_RMXP.txtA file for management

sysroot0644-HORCM/etc/Raidcom_Dic_Raid_RMXP.txtA file for management

For information and instructions on changing the UNIX user for the RAID Manager software,please see the RAID Manager Installation and Configuration Guide.

RAID Manager files for Windows-based systems

Command nameFile nameTitle

horcmd\HORCM\etc\horcmgr.exeHORCM

-\HORCM\etc\horcm.confHORCM_CONF

horctakeover\HORCM\etc\horctakeover.exeTakeover

paircurchk\HORCM\etc\paircurchk.exeAccessibility check

paircreate\HORCM\etc\paircreate.exePair generation

pairsplit\HORCM\etc\pairsplit.exePair split

pairresync\HORCM\etc\pairresync.exePair re-synchronization

RAID Manager software files 45


pairevtwait\HORCM\etc\pairevtwait.exeEvent waiting

pairmon\HORCM\etc\pairmon.exeError notification

pairvolchk\HORCM\etc\pairvolchk.exeVolume checking

pairdisplay\HORCM\etc\pairdisplay.exePair configuration confirmation

raidscan\HORCM\etc\raidscan.exeRAID scanning

raidar\HORCM\etc\raidar.exeRAID activity reporting

raidqry\HORCM\etc\raidqry.exeConnection confirmation

horcctl\HORCM\etc\horcctl.exeTrace control

horcmstart\HORCM\etc\horcmstart.exeHORCM activation script

horcmshutdown\HORCM\etc\horcmshutdown.exeHORCM shutdown script

pairsyncwait\HORCM\etc\pairsyncwait.exeSynchronous waiting

inqraid\HORCM\etc\inqraid.exeConnection confirmation

mkconf\HORCM\Tool\mkconf.exeConfiguration setting and confirmingcommand

rmawk\HORCM\Tool\rmawk.exeText filtering

raidvchkset\HORCM\etc\raidvchkset.exeOracle Validation setting

raidvchkdsp\HORCM\etc\raidvchkdsp.exeOracle Validation confirmation

raidvchkscan\HORCM\etc\raidvchkscan.exeOracle Validation confirmation

raidcom\HORCM\etc\raidcom.exeConfiguration setting command

-\HORCM\etc\Raidcom_Dic_Raid_RMXP_Patch.txtA file for management

-\HORCM\etc\Raidcom_Help_Raid_RMXP.txtA file for management

-\HORCM\etc\Raidcom_Dic_Raid_RMXP.txtA file for management

chgacl\HORCM\Tool\chgacl.exeTool

svcexe\HORCM\Tool\svcexe.exeTool

-\HORCM\Tool\HORCM0_run.txtSample script for svcexe

TRCLOG\HORCM\Tool\TRCLOG.batTool

rmsra\HORCM\etc\rmsra.exeStorage Replication Adapter

horctakeover\HORCM\usr\bin\horctakeover.exeTakeover

paircurchk\HORCM\usr\bin\paircurchk.exeAccessibility check

paircreate\HORCM\usr\bin\paircreate.exePair generation

pairsplit\HORCM\usr\bin\pairsplit.exePair split

pairresync\HORCM\usr\bin\pairresync.exePair re-synchronization

pairevtwait\HORCM\usr\bin\pairevtwait.exeEvent waiting

pairvolchk\HORCM\usr\bin\pairvolchk.exeVolume check

pairsyncwait\HORCM\usr\bin\pairsyncwait.exeSynchronous waiting

pairdisplay\HORCM\usr\bin\pairdisplay.exePair configuration confirmation



raidscan\HORCM\usr\bin\raidscan.exeRAID scanning

raidqry\HORCM\usr\bin\raidqry.exeConnection confirmation

raidvchkset\HORCM\usr\bin\raidvchkset.exeOracle Validation setting

raidvchkdsp\HORCM\usr\bin\raidvchkdsp.exeOracle Validation confirmation

raidvchkscan\HORCM\usr\bin\raidvchkscan.exeOracle Validation confirmation

raidcfg\HORCM\usr\bin\raidcfg.exeConfiguration setting and confirmingcommand

NOTE:• The \HORCM\etc\ commands are used from the console window. If these commands are

executed without an argument, the interactive mode will start up.• The \HORCM\usr\bin commands have no console window, and can therefore be used from

the application.• The \HORCM\usr\bin commands do not support the directory mounted volumes in

subcommands.• \HORCM\Tool\TRCLOG.bat is a troubleshooting tool. This tool is not usually used.

• \HORCM\etc\rmsra.exe is the binary data used for cooperation with VMware. This is useddirectly by VMware, not usually used by users.

RAID Manager files for OpenVMS-based systems

UserCommand nameFile nameTitle

syshorcmd$ROOT:[HORCM.etc]horcmgr.exeHORCM

sys-$ROOT:[HORCM.etc]horcm.confHORCM_CONF

syshorctakeover$ROOT:[HORCM.usr.bin]horctakeover.exeTakeover

syspaircurchk$ROOT:[HORCM.usr.bin]paircurchk.exeVolume accessibility check

syspaircreate$ROOT:[HORCM.usr.bin]paircreate.exePair generation

syspairsplit$ROOT:[HORCM.usr.bin]pairsplit.exePair splitting

syspairresync$ROOT:[HORCM.usr.bin]pairresync.exePair re-synchronization

syspairevtwait$ROOT:[HORCM.usr.bin]pairevtwait.exeEvent waiting

syspairmon$ROOT:[HORCM.usr.bin]pairmon.exeError notification

syspairvolchk$ROOT:[HORCM.usr.bin]pairvolchk.exeVolume checking

syspairdisplay$ROOT:[HORCM.usr.bin]pairdisplay.exePair config. confirmation

sysraidscan$ROOT:[HORCM.usr.bin]raidscan.exeRAID scan

sysraidar$ROOT:[HORCM.usr.bin]raidar.exeRAID activity report

sysraidqry$ROOT:[HORCM.usr.bin]raidqry.exeConnection confirmation

syshorcctl$ROOT:[HORCM.usr.bin]horcctl.exeTrace control

syshorcmstart.sh$ROOT:[HORCM.usr.bin]horcmstart.exeHORCM activation script

syshorcmshutdown.sh$ROOT:[HORCM.usr.bin]horcmshutdown.exeHORCM shutdown script

RAID Manager software files 47

UserCommand nameFile nameTitle

sys-$ROOT:[HORCM.usr.bin]inqraid.exeConnection confirmation

syspairsyncwait$ROOT:[HORCM.usr.bin]pairsyncwait.exeSynchronous waiting

sys-$ROOT:[HORCM.usr.bin]mkconf.exeConfiguration file making

sys-$ROOT:[HORCM.usr.bin]rmawk.exeText filtering

sysraidvchkset$ROOT:[HORCM.usr.bin]raidvchkset.exeDatabase Validator setting*

sysraidvchkdsp$ROOT:[HORCM.usr.bin]raidvchkdsp.exeDB Validator confirmation

sysraidvchkscan$ROOT:[HORCM.usr.bin]raidvchkscan.exeDB Validator confirmation

sysrmsra$ROOT:[HORCM.usr.bin]rmsra.exeStorage Replication Adapter

sys-$ROOT:[HORCM]loginhorcm*.comSample file for horcmstart

sys-$ROOT:[HORCM]runhorcm*.comSample file for horcmstart

* Database Validator is only supported on XP P9500 and prior XP generations.

NOTE:• $ROOT is defined as SYS$POSIX_ROOT. $POSIX_ROOT is necessary when using C RTL.

• The user name for OpenVMS is "System".

RAID Manager log and trace filesThe RAID Manager software (HORCM) maintains internal startup log files, execution log files,and trace files that can be used to identify the causes of errors and to keep records of the statustransition history of the paired volumes.

• “RAID Manager log files” (page 48)

• “RAID Manager trace files” (page 50)

• “RAID Manager trace control command” (page 50)

• “Command logging for audit” (page 51)

RAID Manager log filesHORCM logs are classified into startup logs and execution logs.

• The startup logs contain data on errors that occur before HORCM becomes ready to provideservices. Thus, if HORCM fails to start up due to improper environment setting, refer to thestartup logs to resolve the problem.

• The HORCM execution logs (error log, trace, and core files) contain data on errors that arecaused by software or hardware problems. These logs contain internal error data that doesnot apply to any user settings, therefore, you do not need to refer to the HORCM executionlogs.

• When an error occurs in execution of a command, data on the error is collected in thecommand log file. Refer to the command log file if a command execution error occurs.

The following figure shows a graphical representation of the RAID Manager log and trace fileswithin the RAID Manager configuration environment.


Figure 25 Logs and traces

The startup log, error log, trace, and core files are stored as shown in Table 7 (page 49). Specifythe directories for the HORCM and command log files using the HORCM_LOG and HORCC_LOGenvironment variables as shown in Table 8 (page 50). If it is not possible to create the log files,or if an error occurs before the log files are created, the error logs are output in the system logfile. If the HORCM activation fails, the system administrator should check the system log file andactivation log, identify the error cause, and take the proper action. The system log file forUNIX-based systems is the syslog file. The system log file for Windows-based systems is theevent log file.

Table 7 Log file names and locations

Windows-based systemsUNIX-based systemsFile

HORCM startup log:HORCM startup log:Startuplog $HORCM_LOG\horcm_HOST_log.txt$HORCM_LOG/horcm_HOST.log

Command log: $HORCC_LOG\horcc_HOST_log.txtCommand log: $HORCC_LOG/horcc_HOST.log$HORCC_LOG\horcc_HOST_oldlog.txt$HORCC_LOG/horcc_HOST.oldlog

HORCM error log:HORCM error log:Error log$HORCM_LOG\horcmlog_HOST\horcm_log.txt$HORCM_LOG/horcmlog_HOST/horcm.log

HORCM trace:HORCM trace:Trace$HORCM_LOG\horcmlog_HOST\horcm_PID_trc.txt$HORCM_LOG/horcmlog_HOST/horcm_PID.trcCommand trace:Command trace:$HORCM_LOG\horcmlog_HOST\horcc_PID_trc.txt$HORCM_LOG/horcmlog_HOST/horcc_PID.trc

HORCM core: $HORCM_LOG\core_HOST_PID\coreHORCM core:CoreCommand core:$HORCM_LOG/core_HOST_PID/core$HORCM_LOG\core_HOST_PID\coreCommand core:

RAID Manager log and trace files 49

Table 7 Log file names and locations (continued)

Windows-based systemsUNIX-based systemsFile

$HORCM_LOG/core_HOST_PID/core

NOTE: HOST denotes the host name of the corresponding machine. PID denotes the processID of that machine.

The location of the directory containing the log file depends on your command executionenvironment and the HORCM execution environment. The command trace file and core file residetogether under the directory specified in the HORCM execution environment. A directory specifiedusing the environment variable HORCM_LOG is used as the log directory in the HORCM executionenvironment. If no directory is specified, the directory /tmp is used. A directory specified usingthe environment variable HORCC_LOG is used as the log directory in the command executionenvironment. If no directory is specified, the directory /HORCM/log* is used (* = instance number).A nonexistent directory can be specified as a log directory using the environment variable.

Table 8 Environment variables for log directories

DefinitionDirectory name

A directory specified using the environment variable HORCM_LOG. The HORCM log file, trace file, andcore file as well as the command trace file and core file are stored in this directory. If no environmentvariable is specified, "/HORCM/log/curlog" is used.

$HORCM_LOG

A directory specified using the environment variable HORCC_LOG. The command log file is stored inthis directory. If no environment variable is specified, the directory "/HORCM/log*" is used (* is the

$HORCC_LOG

instance number). While the HORCM is running, the log files are stored in the $HORCM_LOG directoryshown in (a). When the HORCM starts up, the log files created in the operation are stored automaticallyin the $HORCM_LOGS directory shown in (b).a. HORCM log file directory in operation$HORCM_LOG = /HORCM/log*/curlog (* is instance number)b. HORCM log file directory for automatic storing$HORCM_LOGS = /HORCM/log*/tmplog (* is instance number)

RAID Manager trace filesThe command trace file is used for maintenance aiming at troubleshooting. It is not creatednormally. If a cause of an error cannot be identified using the log file, the environment variablesor trace control commands with trace control parameters are issued to start tracing and the tracefile is created. The trace control parameters include trace level, file size, mode, etc. More detailedtracing is enabled by increasing the trace level. Tracing is made in wraparound within the rangeof the file size. HORCM makes the trace file according to the trace level specified in the HORCMstartup shell script set to activate the HORCM.

RAID Manager trace control commandThe trace control command (one of the HORCM control commands) sets or changes the tracecontrol parameters. This command is used for troubleshooting and maintenance. If no tracecontrol parameters can be specified using the environment variables in your command executionenvironment, it is possible to change the trace control parameters into the global parametersusing this command. Table 9 (page 51) lists and describes the parameters of the trace controlcommand.


Table 9 Trace command parameters

FunctionParameter

Specifies the trace level, range = 0 to 15.Trace level parameter

Specifies the trace file size in KB.Trace size parameter

Specifies the buffer mode or non-buffer mode for writing data in the trace file.Trace mode parameter

Specifies the trace type defined internally.Trace type parameter

Specifies the command or RAID Manager instance for which the trace controlparameters are changed.

Trace change instruction

Command logging for audit• “Logging other than raidcom command” (page 51)

• “Logging raidcom command” (page 53)

Logging other than raidcom commandThis section explains the logging other than the raidcom command described in “Logging raidcomcommand” (page 53).RAID Manager supports command logging, this logging function cannot be used for auditing thescript issuing the command. Thus, RAID Manager supports the function logging the result of thecommand executions by expanding the current logging.This function has the following control parameters.

• $HORCC_LOGSZvariableThis variable is used to specify a maximum size (in units of KB) and normal logging for thecurrent command. /HORCM/log*/horcc_HOST.log file is moved to/HORCM/log*/horcc_HOST.oldlog file when reaching in the specified maximum size. If thisvariable is not specified or specified as 0, it is same as the current logging for only commanderror.This variable is able to define to the environment variable and/or horcc_HOST.conf asdiscussed below.For example setting 2MB size: HORCC_LOGSZ=2048 Export HORCC_LOGSZ

• /HORCM/log*/horcc_HOST.conf fileThis file is used to describe HORCC_LOGSZ variable and the masking variable for logging.If the HORCC_LOGSZ as the environment variable is not specified, then HORCC_LOGSZvariable of this file is used. If both variable is not specified, then it is same as the currentlogging for only command error.

• HORCC_LOGSZ variableThis variable must be described as follows: HORCC_LOGSZ=2048

• The masking variableThis variable is used to mask (disable) the logging by specifying a condition of the commandand returned value (except inqraid or EX_xxx error code). This variable is valid for NORMALexit.If executing the pairvolchk command repeatedly at every interval (30 seconds), loggingof this command might not be wanted. Therefore, you can mask it by specifyingHORCC_LOGSZ=0 as shown below, and you might need to change your scripts if tracingis ON.Example of masking pairvolchk on a script:


Export HORCC_LOGSZ=0 Pairvolchk -g xxx -s Unset HORCC_LOGSZThe masking feature is to enable the tracing without changing their scripts. And this featureis available for all RAID Manager commands (except inqraid or EX_xxx error code).For example, if you want to mask pairvolchk (returns 22) and raidqry, specify the following:pairvolchk=22 raidqry=0You can track script performance, and then decide to mask by auditing the command loggingfile, as needed.

• Relationship between an environment variable and horcc_HOST.confLogging depends on the $HORCC_LOGSZ environment variable and/or theHORCC_HOST.conf file as shown below.

PerformingHORCC_HOST.conf$HORCC_LOGSZ

Tracing within this APPAny (does not matter)=value

NO tracing within this APP=0

Global tracing within this RAID Manager instanceHORCC_LOGSZ=valueUnspecified

NO global tracing within this RAID Manager instanceHORCC_LOGSZ=0

Use the default value (0) The same as the currentlogging for only command error

Unspecified or nonexistent


• Examples for execution/HORCM/log* directory[root@raidmanager log9]# ls ltotal 16drwxr-xr-x 3 root root 4096 Oct 27 17:33 curlog-rw-r--r-- 1 root root 3936 Oct 27 17:36 horcc_raidmanager.log-rw-r--r-- 1 root root 2097452 Oct 27 17:29 horcc_raidmanager.oldlog-rw-r--r-- 1 root root 46 Oct 27 17:19 horcc_raidmanager.confdrwxr-xr-x 3 root root 4096 Oct 27 17:19 tmplog

/HORCM/log*/horcc_HOST.log fileCOMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005CMDLINE : pairvolchk ss g URA12:21:54-2d27f-10090- [pairvolchk][exit(32)]COMMAND NORMAL : EUserId for HORC : root (0) Thu Oct 27 17:36:32 2005CMDLINE : raidqry l17:36:32-3d83c-17539- [raidqry][exit(0)]COMMAND ERROR : EUserId for HORC : root (0) Thu Oct 27 17:31:28 2005CMDLINE : pairdisplay g UR17:31:28-9a206-17514- ERROR:cm_sndrcv[rc < 0 from HORCM]17:31:28-9b0a3-17514- [pairdisplay][exit(239)][EX_ENOGRP] No such group[Cause ]:The group name which was designated or the device namedoesn't exist in the configuration file, or the network addressfor remote communication doesn't exist.[Action]:Please confirm if the group name exists in theconfiguration file of the local and remote host

/HORCM/log*/horcc_HOST.conf file# For ExampleHORCC_LOGSZ=2048#The masking variable#This variable is used to disable the logging by the command and exitcode.#For masking below log pairvolchk returned '32'(status is SVOL_COPY)#COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005#CMDLINE : pairvolchk ss g URA#12:21:54-2d27f-10090- [pairvolchk][exit(32)]pairvolchk=32pairvolchk=22

Logging raidcom commandThe history of performing raidcom command can be stored in syslog server by outputting it tothe syslog file. Since the information of what command was performed by who and when arerecorded on the syslog file, this is available to use for audit log.Output the syslog file by using syslog service on the host OS. For details, refer to the host OSmanual.

CAUTION:• The packet loss occurs on the syslog because the syslog uses UDP communication. The

log is also lost when the server to be received the syslog is down because the server doesnot have a function to store the data until it recovered. If you want to record the same log atthe client side by considering the lost of syslog at the syslog server, refer to the output settingof the syslog file.

• This syslog files are not deleted automatically. Delete unnecessary files accordingly, or makerun the log rotation by installing such as the logrotate service separately.


The conditions to support the output of syslog fileThe conditions to support this function are explained in the following:Supported OSThis function is supported only when the OS of the host is one of the following (Windows is outof support):

• Solaris 2.5

• Solaris 10/x86

• HP-UX 10.20/11.0/11.2x

• AIX 4.3

• Red Hat Linux 6.0, 7.0, 8.0 AS/ES 2.1, 3.0, 4.0, 5.0

• AS/ES 2.1, 3.0 Update2, 4.0, 5.0 on EM64T / IA641Target commandThe following shows the raidcom command that is target to be output on the syslog file.

• Setting commands

• raidcom get command status

• Authentication commands (performing the authentication command at the prompt alsobecomes the target.)

However, if the command is not issued to the DKC by detecting the raidcom command executionerror beforehand, the command becomes out of target even if it falls under the above items.

Output setting for the syslog fileA syslog file is output when "1" is set on the RAIDCOM_SYSLOG of environment variables. Thesyslog file is not output at the stage of initial setting.How to set the syslog.confThe contents that can be set on the syslog.conf for the environment setting might vary in eachOS. However, set basically according to the syslog.conf described in the following:Setting example (It might vary by the host OS)

• Client side (extracts)user.info /var/log/raidcomuser.err

/var/log/raidcom.erruser.info @host1234user.err@host1234

• Server side (extracts)user.info /var/log/raidcomuser.err

/var/log/raidcom.err

You can record the same log at the client side by considering the lost of syslog at the syslogserver. In this case, add the following settings.

• facility:user

• level:info/err ("info" for the normal command operation; "err" for the abnormal commandoperation.)

Syslog file display informationThree kinds of information for one raidcom command are output on the syslog file.

• Title row (first row)

• Command row (second row)

• Result rows (3 - 132 rows): the number of rows changes depending on the issuing command.


Table 10 Display information of the title row

Output exampleItem

Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info]Syslog fixed output part(Including the host name) *It varies depending on the host OS.

PID:1234Process ID

COMMAND NORMAL or COMMAND ERRORCommand status

:Separation

EUserId for HORC :User name Title

rootUser name of the host

(0)(user ID)

Wed Jun 27 10:15:13 2012Time that performed raidcom

Table 11 Display information of the command row

Output exampleItem


PID:1234Process ID

CMDLINE:Title for performed command

raidcom modify ldev -ldev_id 1234 -status nmlPerformed command

Table 12 Display information of the result rows

Output exampleItem


PID:1234Process ID

[raidcom][raidcom]

[EX_CMDRJE] An order to the control/command device was rejected It was rejecteddue to SKEY=0x05, ASC=0x26, ASCQ=0x00, SSB=0x2E11,0x2205 on Serial#(64568)

Rows for the error information

HANDLE SSB1 SSB2 ERR_CNT Serial# Description 00c4 - - 0 200414 -Result ofget_command_status

[exit(0)]Rows for the returned valuesof a command

Display example (It might vary depending on the host OS.)

• Logs when the normal operationAug 24 12:24:37 raidmanager raidcom: PID:06864 COMMAND NORMAL : EUserID for HORC : root(0) FriAug 24 12:24:36 2012Aug 24 12:24:37 raidmanager raidcom: PID:06864 CMDLINE : raidcom get command_status -ldev_id0001Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] HANDLE SSB1 SSB2 ERR_CNTSerial# Description

Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] 00c3 - - 064568 -

Aug 24 12:24:37 raidmanager raidcom: PID:06864 [raidcom] [exit(0)]

• Logs when the abnormal operationAug 24 12:24:27 raidmanager raidcom: PID:06857 COMMAND ERROR : EUserID for HORC : root(0) FriAug 24 12:24:19 2012Aug 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] : user1234Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] User authentication has failed onSerial#(64568).Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [EX_ENAUTH] Authentication failed withUserAug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [exit(202)]

User-created filesRAID Manager supports scripting to provide automated and unattended copy operations. A RAIDManager script contains a list of RAID Manager commands that describes a series of ContinuousAccess Synchronous and/or Business Copy operations. The scripted commands for UNIX-basedplatforms are defined in a shell script file. The scripted commands for Windows-based platformsare defined in a text file. The host reads the script file and sends the commands to the commanddevice to execute the Continuous Access Synchronous/Business Copy operations automatically.The RAID Manager scripts are:

• HORCM startup script (horcmstart.sh, horcmstart.exe). A script that starts HORCM(/etc/horcmgr), sets environment variables as needed (for example, HORCM_CONF,HORCM_LOG, HORCM_LOGS), and starts HORCM.

• HORCM shutdown script. (horcmshutdown.sh, horcmshutdown.exe): A script forstopping the HORCM (/etc/horcmgr).

• HA control script. A script for executing takeover processing automatically when the clustermanager (CM) detects a server error.

When constructing the HORCM environment, the system administrator should make a copy ofthe horcm.conf file. The copied file should be set according to the system environment andregistered as the following file (* is the instance number):UNIX systems: /etc/horcm.conf or /etc/horcm*.confWindows systems:%windir%\horcm.conf or %windir%\horcm*.conf

User environment variableWhen HORCM or command is invoked, environment variable can be specified.


3 RAID Manager functionsThis chapter describes the RAID Manager functions.

System configuration using RAID ManagerThis 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 RAID Manager server by usingthe 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” (page 12).

In-band system configurations and out-of-band system configurationsValues to specify for HORCM_CMD in the configuration definition file are different betweenin-band and out-of-band method system configurations.

• In-band method.This method specifies the device special file of command device in theconfiguration definition file. For details about contents to specify for HORCM_CMD, see“HORCM_CMD (in-band method)” (page 29).

• Out-of-band method.This method specifies the SVP for creating virtual command devicesin the command definition file. For details about contents to specify for HORCM_CMD, see“HORCM_CMD (out-of-band method)” (page 32).

The location of the virtual command device depends on the type of storage system. The followingtable lists the storage system types and indicates the allowable locations of the virtual commanddevice.

Location of virtual command deviceStorage system type

RAID Manager server1SVP

OKOKXP7

OKOKP9500

1. A RAID Manager server is a remote RAID Manager server connected via LAN.

The following figure shows a system configuration example and a setting example of a commanddevice and a virtual command device using the in-band and out-of-band methods.

System configuration using RAID Manager 57

Figure 26 System configuration example of in-band and out-of-band methods (P9500)

System configuration for connecting to a RAID Manager server connected by thein-band method using the out-of-band method

In the out-of-band method, RAID Manager server ports can be specified as virtual commanddevices. Specifying a RAID Manager server port as a virtual command device allows you to usethe out-of-band method to connect to a RAID Manager server connected to a storage systemusing the in-band method. For details about settings for HORCM_CMD in the configurationdefinition file of this configuration, see “HORCM_CMD (out-of-band method)” (page 32).

TIP: If you specify a RAID Manager server port as a virtual command device, it achieves betterperformance than the out-of-band method which specifies SVP as a virtual command device.

The following figure shows a system configuration example when a RAID Manager server isconnected to a storage system using the in-band method.

58 RAID Manager functions

Figure 27 System configuration example when the RAID Manager server is connected tothe storage system by in-band

Connecting to RAID Manager server already connected by In-Bandmethod using Out-of-Band method

In Out-of-Band method, RAID Manager server port can also be specified as a virtual commanddevice. For this reason, RAID Manager server which connected to a storage system in In-Bandmethod can be connected in Out-of-Band method. If a RAID Manager server is specified as avirtual command device, it provides better performance than the Out-of-Band method with specifiedSVP as a virtual command device.

Hardware requirementsRAID Manager uses SCSI path through driver to issue I/O for command device. To use RAIDManager server port as virtual command device, the virtual command device interface needs tobe converted to the actual SCSI path through interface. Following is the environment for usingRAID Manager server port as a virtual command device.

• RAID Manager server which can set virtual command devicesRAID Manager support platform except Tru64UNIX and the environment can be used SCSIpath through driver

• Client PC which can issue commands to virtual command devicesIt must be RAID Manager support platform. Windows client such a Windows XP can be usedas well.

• Initiator portInitiator port is required.

Connecting to RAID Manager server already connected by In-Band method using Out-of-Band method 59

Following is the default port number.If not specified the instance number: 34000If specified instance number (X): 34000 + X + 1If you change the default port number, use following environment variables.$HORCM_IPSCPORT=<services>** <services>: port number or service name

For details about supported platforms, see the RAID Manager Installation and ConfigurationGuide.

I/O Traffic ControlSynchronized I/O is issued from a virtual command device. The queueing time might occurbecause of the heavy I/O traffic because the virtual command device has to relay the commandto the next virtual command device in the cascade configuration using the virtual commanddevice. To improve the response in this environment, define the configuration so that asynchronousI/O is issued using the following environment variables.$HORCM_IPSCPAIO=1

Security settingFollowing security can be set.

• Specifying security of IP address and port numberBy defining IP address and port number of the client PC that issues command to virtualcommand device to HORCM_ALLOW_INST in the configuration definition file, users whocan use virtual command device can be restricted. For the details about the settings toHORCM_ALLOW_INST, please refer to "Configuration definition file".

• Security setting for virtual command deviceBy using the following environment variable, security can be set to virtual command device.

$HORCM_IPCMDSEC=<value>

Specify the number (from 0 to 7) to <value> depending on the contents of the security which youwant, in reference with the following table.

Table 13 Security setting for virtual command device

Command device settingValuespecifying to<value> Security to be set

(see Notes)Device groupdefinition

User authenticationSecurity setting

No securityOFFOFFOFF0

Only HORCM_DEVallowed

ONOFFOFF1

User authenticationrequired

OFFONOFF2


ONONOFF3


CMD securityOFFOFFON4

CMD securityONOFFON5


Table 13 Security setting for virtual command device (continued)

Command device settingValuespecifying to<value> Security to be set

(see Notes)Device groupdefinition

User authenticationSecurity setting


CMD securityOFFONON6User authenticationrequired

CMD securityONONON7User authenticationrequiredOnly HORCM_DEVallowed

Notes:• ON: Enabled

• OFF: Disabled

• Only HORCM_DEV allowed: the operation can be performed only for paired logical volumes described inHORCM_DEV.

• User authentication required: only commands issued by authorized users can be executed.

• CMD security: only devices recognizable from the host can be operated. For details about CMD security, see“Data Protection facility” (page 221).

User authenticationRAID Manager allows user authentication by using the operation authority of a user set by:

• Remote Web ConsoleUser authentication is arbitrary in the Replication operation in the in-band method while theoperation by user authentication is mandatory in the configuration information operation and inthe out-of-band method.To enable the user authentication function, the user authentication mode of the command deviceaccessed by RAID Manager must be enabled.The user authentication function inputs a login command from the client (server) and, toauthenticate the user ID and password sent from RAID Manager and the same types of informationmaintained by the storage system, issues an authentication request to the authentication module(SVP).If the user ID and password which are sent by RAID Manager are authenticated, the storagesystem generates the session information. The storage system stores the session information,the user ID, and the client ID, and then sends back the session information to RAID Manager.RAID Manager stores the session information with the storage system ID. After that, the sessioninformation is added to all commands which are issued by RAID Manager to the storage system.If the session information which is added to the command is valid, the storage system permitsthe command execution.When the user logs out, the session information which is stored by RAID Manager, and the userID, the client ID, and the session information which are stored in the storage system are deleted.A storage system can store only one session information for the same user ID and the sameclient ID at the same time. If the storage system received the login command with the user IDand client ID, corresponding to the session information which has already been stored, the storagesystem sends back the stored session information to RAID Manager without authentication.

User authentication 61

During executing the login command, if another login command is input with the same user IDfrom the same client, the authentication result of the subsequent login command will be the sameas the authentication result of login command being executed.

NOTE:• The only function that can be used if the user authentication function is disabled is the

Replication function (replication command). If the user authentication function is disabled,the Provisioning function (configuration setting command) cannot be used. If you use themulti-array virtualization function, see Table 14 (page 63). For details about multi-arrayvirtualization, see the XP7 Provisioning for Open Systems User Guide.

• If the specific user information or authority information is changed, perform the userauthentication processing on RAID Manager again.

• RAID Manager stores the session information for each user ID (managed by OS) which isused for login to the client OS. Therefore, if users having the different user ID (managed byOS) use the same client, execute RAID Manager login command for each user ID (managedby OS).

Command operation authority and user authenticationWhen RAID Manager is used with the user authentication function enabled, commands areexecuted complying with the operation authority of a user set by:

• Remote Web Console

Controlling User RoleRAID Manager verifies whether or not the user executing the command on the host was alreadyauthenticated by checking the command device being in the authentication mode. After that,RAID Manager obtains the execution authority of the command that is configured on the userrole, and then compares the relevant command and the execution authority.

Checking the execution authorityIf the configuring commands authenticated are compared with the execution authorities ofcommands configured on the user role and they do not correspond, RAID Manager rejects thecommand with an error code "EX_EPPERM".Normally, the user role needs to be the consistent and integrated authority among the largestorage systems. In case of HORCM instances that are configured by the multiple large storagesystems, the execution authorities are obtained by the serial number of the storage systems. Ifthe user role is for the multiple storage systems and is not consistent among these storagesystems, RAID Manager makes the integrated authority by performing the logical AND of theexecution authorities among the storage systems.

The target commandsRAID Manager checks execution authorities on the following commands that use commanddevices.

• horctakeover, horctakeoff

• paircreate, pairsplit, pairresync

• raidvchkset

Controlling user resourcesRAID Manager verifies the user who executes the command has been authenticated already.After that, RAID Manager obtains the access authority of the resource groups that are configuredon the user roles, and then compares the access authority of the user and the specified resources.


Checking resource authoritiesIf the access is not permitted by comparing the access authorities of the resource groupsconfigured on the user roles and the specified resource, RAID Manager rejects the commandwith an error code "EX_EGPERM". If the resource groups are defined among the large storagesystems, the specified resource is compared with the resource specified by obtaining the accessauthority configured to each large storage system.

Target commandsRAID Manager checks resource authorities on the following commands that use commanddevices.

• raidcom commands (commands for setting configurations)

• horctakeover, horctakeoff, paircurchk, paircreate, pairsplit, pairresync, pairvolchk, pairevtwait,pairsyncwait, pairmon

• raidscan (-find verify, -find inst, -find sync except for [d]), pairdisplay, raidar, raidqry (exceptfor -l and -r)

• raidvchkset, raidvchkscan, raidvchkdsp

Relation between user authentication and resource groupsIn user authentication mode, RAID Manager verifies the access authority of the relevant resourcebased on the user authentication and the role of it. Also, on the user authentication unnecessarymode and the undefined resource groups, RAID Manager checks the access authorities shownin the following table.

Table 14 Relations between resource groups and command devices

CommandsResources

raidcompairXX1

Authenticated userNot authenticateduser2

Authenticated userNot authenticateduser2

Permitted by theauthority of resource ID0

EX_EPPERM4Permitted by theauthority of resourceID 0

PermittedUndefinedresource3

Permitted by theauthority of the relevantresource ID

EX_EGPERM4

EX_EPPERM

Permitted by theauthority of therelevant resource ID

EX_EGPERM4Defined resource

Permitted by theauthority of the relevantresource ID

EX_EGPERM4

EX_EPPERM

Permitted by theauthority of therelevant resource ID

Permitted6Virtual storagemachine5

Notes:1. Above-described commands except for the raidcom command.2. User who uses the mode without the command authentication.3. Undefined as the resource group.4. Command execution is rejected by the relevant error.5. The resource group that is defined as the virtual storage machine by the multi-array virtualization function. For

details about multi-array virtualization, see the Provisioning Guide for the storage system.6. When you specify a volume that belongs to meta_resouce or a virtual command device for HORCM_VCMD in

the configuration definition file, the resource operation for the entire resource group in the virtual storage machinewhich specifies HORCM_VCMD is permitted. If you do not specify the virtual storage system for HORCM_VCMD,EX_EGPERM is returned. When you specify a volume that belongs to the virtual storage machine for HORCM_CMDin the configuration definition file, the resource operation for the entire resource group in the virtual storagemachine to which the volume belongs is permitted. For details about specifying the virtual storage machine toHORCM_VCMD, see “Configuration definition file settings with multi-array virtualization” (page 104).

Command operation authority and user authentication 63

Check of the access authority when you operate a pairWhen you use the commands other than raidcom commands, which are described in "Targetcommands" above, whether the user who executes the command has an access authority to theresource is checked. Usually, only one resource in the volumes which configures a pair is checked,the resource is managed by the instance which executes the pair operation command. However,when you operate a pair of a local copy, if the HOMRCF_CHECK_RSGID environment variableis defined, an access authority of the command execution user to both volumes which configurea pair can be checked.The following figure shows an example of a pair operation when you do not define theHOMRCF_CHECK_RSGID environment variable. The command execution user can create apair even if one of the volume which configures the pair is a resource to which the user does nothave an authority.

Figure 28 Example of a pair operationwhen you do not define the HOMRCF_CHECK_RSGIDenvironment variable

The following figure shows an example of a local copy pair operation when you define theHOMRCF_CHECK_RSGID environment variable. You can avoid creating a pair which includesthe volume without authority, therefore whether the both volumes which configure a pair areauthenticated or not is checked.


Figure 29 Example of a local copy pair operation when you define theHOMRCF_CHECK_RSGID environment variable

Target resourcesThe following objects are arbitrarily defined as the resource groups by each user.

• LDEV

• Physical port

• Host group

• RAID group

• External connection group

Commands executed depending on operation authoritiesThe following table lists the commands executed depending on operation authority of a user setby:

• Remote Web ConsoleFor information about creating the user accounts, registering user accounts to user groups, anduser group authorities, see the XP7 Remote Web Console User Guide or the XP7 Remote WebConsole User Guide or P9000 Remote Web Console User Guide for the storage system.


Table 15 Executable commands executed depending on operation authority of a user set byRemote Web Console

Operation authority (Role)Executable commandAuthorityOperation targetOperation

Storage Administrator (SystemResource Management)

raidcom modify ldevraidcom modify journal

MP blade settingauthority

MP bladeOverall setting

raidcom modify external_grp

raidcom modify clprParity groupmigration authority

CLPR

Storage Administrator (View &Modify)

raidcom add resourceraidcom modify resource

Resource groupcreation authority

Resource group

raidcom map resource

raidcom unmap resourceResource groupdeletion authority raidcom delete resource

Storage Administrator(Provisioning)

raidcom add ldevLDEV creationauthority raidcomadd ldev

LDEVResourcecreation,deletion


raidcom delete ldevLDEV deletionauthority


raidcom initialize ldev-operation fmt

LDEV formatauthority

raidcom initialize ldev-operation qfmt


raidcom initialize ldev-operation shrd

LDEV shreddingexecution authority

raidcom initialize ldev-operation stop


raidcom modify ldev-quorum_enable

ESAM/HA Paircreation authority

paircreate -f never -jqpaircreate -f never -jp


raidcom modify ldev-quorum_disable

ESAM/HA Pairdeletion authority

pairsplit -S[F[V]]pairsplit -R[F[V]]


raidcom initialize parity_grpLDEV shreddingexecution authority

Parity group


raidcom modify parity_grpParity group creationauthority


raidcom add external_grpraidcom discoverexternal_storage

External volumecreation authority

External volume(External Storage)

raidcom discover lun


raidcom check_ext_storagepath

External pathoperation authority

raidcom disconnect path


Table 15 Executable commands executed depending on operation authority of a user set byRemote Web Console (continued)



raidcom check_ext_storageexternal_grp

External volumedisconnectionauthority raidcom disconnect

external_grpExternal volumeconnection checkand resumptionauthority


raidcom delete external_grpExternal volumemapping releaseauthority


raidcom modify external_grpraidcom addexternal_iscsi_name

Ext Stor Attributevalue settingauthority

raidcom deleteexternal_iscsi_nameraidcom modifyexternal_chap_userraidcom modifyinitiator_chap_user


raidcom delete pathExt Stor pathoperation authority


raidcom add thp_poolraidcom add snap_pool

Pool creation andcapacity changeauthority

Pool

raidcom initialize pool


raidcom delete poolPool deletionauthority


raidcom add ldev -poolraidcom extend ldev

Thin Provisioningvirtual volumecreation authority

Thin Provisioningvirtual volume


raidcom delete ldevThin Provisioningvirtual volumedeletion authority


raidcom add ldev -poolSnapshot virtualvolume creationauthority

Snapshot virtualvolume


raidcom delete ldevSnapshot virtualvolume deletionauthority


raidcom modify port-security_switch

LUN security settingauthority

Port



raidcom add host_grpHost group creationauthority

Host group


raidcom delete host_grpHost group deletionauthority





raidcom add lunLU path creationauthority

LUN


raidcom delete lunLU path deletionauthority


raidcom add hba_wwnraidcom add hba_iscsi

WWN additionauthority

WWN / iSCSI name/ CHAP user name

raidcom add chap_user


raidcom delete hba_wwnraidcom delete hba_iscsi

WWN deletionauthority

raidcom delete chap_user


raidcom add device_grpraidcom add copy_grp

Device group andCopy group creationauthority

LDEV group


raidcom delete device_grpraidcom delete copy_grp

Device group andCopy group deletionauthority


paircreateraidcom add snapshot

Pair creationauthority

Local copy


pairsplit -Sraidcom delete snapshot

Pair deletionauthority


paircreateAuto LUN paircreation authority


pairsplit -SAuto LUN pairdeletion authority

Storage Administrator (LocalCopy)

raidcom modifylocal_replica_opt

Local copyenvironmental settingauthority

Storage Administrator (RemoteCopy)

paircreatePair creationauthority

Remote copy


pairsplit -SPair deletionauthority


raidcom add pathExternal path settingauthority

External volumeAttributechange


raidcom modify poolraidcom rename pool

Pool setting authorityPool


raidcom reallocate poolraidcom monitor pool

Pool monitoring andreallocation start andstop authority


raidcom modify port-port_attribute

Port attribute settingauthority

Port


raidcom modify port -loop_idraidcom modify port -topology

Port setting authority




raidcom modify port-port_speedraidcom modify port -port<port#> [-mtu <value>]...raidcom modify port -port<port#> [-isns_mode{enable|disable}]...


raidcom modify host_grpHost group settingauthority

Host group


raidcom modify lunLDEV settingauthority

LUN


raidcom set hba_wwnraidcom reset hba_wwn

WWN settingauthority

WWN / iSCSI name/ CHAP user name

raidcom set hba_iscsiraidcom reset hba_iscsiraidcom set chap_userraidcom reset chap_user


raidcom modify ldev-ldev_name

LDEV nicknamesetting authority

LDEV nickname


raidcom add pfc_wwnraidcom add pfc_group

Perf Ctl settingauthority

Perf Ctl information

raidcom delete pfc_wwnraidcom delete pfc_groupraidcom modify pfc_wwnraidcom modify pfc_groupraidcom modify pfc_ldevraidcom delete pfc_ldev

Storage Administrator (LocalCopy)

pairresyncraidcom modify snapshot

Pairsplit and resyncauthority

Local copy

raidcom mount snapshotraidcom unmount snapshotraidcom replace snapshot





raidcom add rcuraidcom delete rcu

Environmentconstruction authority

Remote copy

raidcom modify rcuraidcom add rcu_iscsi_portraidcom delete rcu_iscsi_portraidcom add rcu_pathraidcom delete rcu_pathraidcom add journalraidcom delete journalraidcom modify journalraidcom add ssidraidcom delete ssid


pairresyncPairsplit and resyncauthority

Relation between resource groups and command operationsThe operation for using resource groups are different by the command devices (the In-Bandmethod) or the Out-of-Band method that are used when you start RAID Manager.You can create resource groups for each resource. And you can share them with multiple users.When user 10 and user 20 share the port like the following figure, the relation between thecommand devices and resource groups that user can use is like Table 16 (page 71).


Figure 30 Relation among user, command devices, and resource groups

Table 16 Relation between resource groups and command devices

Commandoperations

Configuration changeReferenceOperating rangeCommanddevice

Login user

using theout-of-bandmethod

OperableOperableOperableCan operate all resource groupsafter logging in.

CM0Systemadministrator

InoperableOperableOperableCan operate only in the range ofresource group 10, and the sharedports after logging in.

CM10


CM11


CM20

OperableOperableOperableCan operate only in the range ofresource group 10 and 11, and theshared ports after logging in.

CM0User 10

InoperableOperableOperableCan operate only in the range ofresource group 10, and the sharedports after logging in.*

CM10

Relation between resource groups and command operations 71

Table 16 Relation between resource groups and command devices (continued)

Commandoperationsusing theout-of-bandmethod

Configuration changeReferenceOperating rangeCommanddevice

Login user

InoperableOperableOperableCan operate only in the range ofresource group 11, and the sharedports after logging in.*

CM11

InoperableOperation authorityerror

Cannot log in. Nothing is displayed or the operationauthority error.

CM20

OperableOperableOperableCan operate only in the range ofresource group 20, and the sharedports after logging in.

CM0User 20



CM10



CM11


CM20

* To use each resource group, the user must separately execute raidcom -login command. For details about the raidcom -logincommand, see RAID Manager Reference Guide.

As shown in the table above, the relation among users, command devices and operations ofresource groups are the following.

• The range that can be operated by command device 0 (CM0) or Out-of-Band is the sharedrange (AND) of resource groups that are allocated to each user and all resource groups.

• The range that can be operated by command device 10 (CM10) is the shared range (AND)of resource groups that are allocated to each user and resource group 10 that the commanddevices are allocated.Therefore, in the range of resource group 10 can be operated.

The following shows the example of the case that the execution results of the commands changeby the case of having or not having the authority of the operated resources, specifies only theobjects 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.When only the objects are specified:# raidcom get port

The execution results of CL1-A, CL3-A and CL5-A are displayed. The execution results of CL2-Aand CL4-A (the user does not have the authority of the resource) are not displayed (filtered).When parameters are also specified:# raidcom get port -port CL1-A

The execution result of CL1-A is only displayed.# raidcom get port -port CL2-A

The error is displayed because the user does not have the execution authority.The following shows the output example when -cnt that is used in get ldev is used.The following command is executed when the user has the authorities of LDEV number 10 and12.


# raidcom get ldev -ldev_id 10 -cnt 3

Execution results of LDEV number 10 and 12 are displayed. LDEV number 11 is not displayedbecause the user does not have the authority of the resource.

Resource lock functionWhen configuration changes from multiple user interfaces (RAID Manager, CVAE, Remote WebConsole) are performed on the same resource at the same time, unexpected results can occur.To prevent users from changing the configuration of the same resource at the same time, theresource lock command is provided. When this command is used, the resource group can belocked to prevent other users from using the specified resource group. If the resource is notlocked, all configuration change commands are performed. However, conflicting operations mightcause an error.The commands for performing the exclusive control and exclusive control release (lock andunlock) of resource groups are as follows.

• raidcom lock resource -resource_name <resource group name > [-time <time(sec)>] (Lockinga specified resource group)

• raidcom unlock resource -resource_name <resource group name > (Unlocking a specifiedresource group)

If multiple users (IDs) operate the same resource, by confirming by the raidcom lock resourcecommand that no other user is using the resource, the operation competition for the relevantresource can be prevented.After the configuration change is completed, release the lock status by the raidcom unlockresource command.The user who locks a resource is identified by the session information. When the user logs outand the session information of the user is deleted from the storage system, the resource whichhas been locked by the user is automatically released. For details about the session information,see “User authentication” (page 61).

Command execution modesOverview

Provisioning operations are performed using a configuration setting command. For details aboutthe configuration setting command, see “Overview of the configuration setting command” (page 120)or RAID Manager Reference Guide.Two modes can be used for executing the configuration setting command:

• Line-by-line mode.This mode executes commands input from the command line one at a time.

• Transaction mode.Executes a script file specified by the -zt option.

Resource lock function 73

When executing the configuration setting command, the following checks can be done dependingon the above two mode types.

• Syntax checkThis function checks if there is no syntax error in the specified command. This is executedevery time at the both line-by-line mode and transaction mode.

• Context checkThis function checks the consistency of one specified line in the script and the precedinglines in the order from the top. This function is available only at the Transaction mode. Fordetails about context checking, see “Context check” (page 75).

• Configuration checkAcquire the current configuration information to a configuration file, and then this functionchecks whether the resources specified in the script (LDEVs, ports, or host groups) areconfigured in the storage system or not. This function is available only at the transactionmode. For details about context checking, see “Configuration check” (page 80).

The configuration setting command also has a execution option described in the following.

• PrecheckSpecify the checkmode precheck option. It operates checking only (it does not executeprocessing even if no error is detected.) This can be specified at the both line-by-line modeand transaction mode.

The following table shows the overview of execution modes and options of the configurationsetting command.

Table 17 Execution modes and options of the configuration setting command (line-by-line mode)

RemarksCommandexecution with noerror

Configura-tioncheck

Context checkSyntaxcheck

Command syntax

DefaultExecutedNot executedNot executedExecutedraidcom <action>

Check onlyNot executedNot executedNot executedExecutedraidcom <action> -checkmodeprecheck

Table 18 Execution modes and options of the configuration setting command (transaction mode)

RemarksCommandexecutionwith noerror

Configura-tioncheck

Contextcheck

Syntaxcheck

Command syntax

DefaultExecutedNot executedExecutedExecutedraidcom -zt <script file>

With configurationcheck

ExecutedExecutedExecutedExecutedraidcom -zt <script file> -load<work file>

Check onlyNot executedNot executedExecutedExecutedraidcom -zt <script file>-checkmode precheck

With configurationcheck

Not executedExecutedExecutedExecutedraidcom -zt <script file> -load <work file> -checkmode precheck

Check only


Detailed description are provided in the following.

CAUTION: Observe the following cautions:• For <script file>, specify an executable file name.

• For <script file>, either specify a full path name or store under the c:\HORCM\etc folder.

• For <work file>, either specify a full path name or store in the current directory.

Context checkThis check can be performed to ensure consistent content of the created script file. For example,it can check if the script refers to an ldev_id that is already deleted in the preceding lines.The script is executed only when no error is detected by the checking of whole script contents.The following resources can be the target of the check:

• LDEV

• Port

• Host groupChecking the contents before executing the script helps reduce debugging after running thescript.

How to checkThe script is performed by specifying it as follows.

raidcom -zt <created script file name>

raidcom -zt <created script file name> -load <configuration file>

raidcom -zt <created script file name> -checkmode precheck

raidcom -zt <created script file name> -load <configuration file> -checkmode precheck

Details of check contentsDetails of Context check is described below. checking contents before issuing a script can reduceload for the debug operation in a way of executing script.

LDEV checkThe check is performed from the following perspective. Note that checking for the objectinformation that is related to the LDEV such as pool or device group, or an attribute of LDEV isnot executed.Check with the additional operationIt is checked to ensure no same LDEV as the already existing LDEV is added. If the same LDEVis attempted to be added, an error is detected.If it is not clear whether the LDEV to be added exists or not (if the target LDEV information doesnot exist in the configuration definition file), the error is not detected. Therefore, the script isexecuted and the LDEV is added.The command as the target of the check is shown below.raidcom add ldev {-parity_grp_id <gno-sgno>| -external_grp_id

<gno-sgno> | -pool {<pool ID#> | <pool naming> | snap}}{-ldev_id <ldev#> | -tse_ldev_id <ldev#>} {-capacity <size>

Command execution modes 75

| -offset_capacity <size> | -cylinder <size>} [-emulation<emulation type>][-location <lba>][-mp_blade_id <mp#>][-clpr <clpr#>]

Check with the attribute settingIt is checked whether the operation is performed for the existing LDEV or not. If the operation isattempted 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 definitionfile (if the target LDEV information does not exist in the configuration definition file), the error isnot detected.The commands as the target of the check are shown below.

• raidcom add lun -port <port#> [<host group name>] {-ldev_id <ldev#> [-lun_id<lun#>] |-grp_opt <group option> -device_grp_name <device group name> [<device name>]}

• raidcom delete lun -port <port#> [<host group name>] {-lun_id <lun#> | -ldev_id <ldev#> |-grp_opt <group option> -device_grp_name <device group name> [<device name>]}

• raidcom add journal -journal_id <journal ID#> {-ldev_id <ldev#> …[-cnt<count>] | -grp_opt<group option> -device_grp_name <device group name> [<device name>]} [-mp_blade_id<mp#> | -timer_type <timer type>]

• raidcom delete journal -journal_id <journal ID#> [-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]]

• raidcom add snap_pool {-pool_id <pool ID#> [-pool_name <pool naming>] | -pool_name<pool naming> [-pool_id <pool ID#>] | -pool_id <pool ID#> -pool_name <pool naming>}{-ldev_id <ldev#> …[-cnt<count>] | -grp_opt <group option> -device_grp_name <devicegroup name> [<device name>]}[-user_threshold <%>]

• raidcom add thp_pool {{-pool_id <pool ID#> [-pool_name <pool naming>] | -pool_name<pool naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -pool_name <pool naming>}{-ldev_id <ldev#> …[-cnt <count>] | -grp_opt <group option> -device_grp_name <devicegroup name> [<device name>]}[ -user_threshold <threshold_1> [<threshold_2>]]

• raidcom extend ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name <devicegroup name> [<device name>]} -capacity <size> | -offset_capacity <size> | -cylinder <size>

• raidcom check_ext_storage external_grp {-external_grp_id <gno-sgno> | -ldev_id <ldev#>| -grp_opt <group option> -device_grp_name <device group name> [<device name>]}

• raidcom add device_grp -device_grp_name <ldev group name> <device name> -ldev_id<ldev#>… [-cnt <count>]

• raidcom delete device_grp -device_grp_name <device group name> -ldev_id<ldev#>… [-cnt<count>]

• raidcom modify ldev -ldev_id <ldev#> {-status <status> [<level>] | -ldev_name <ldev naming>| -mp_blade_id <mp#>| -ssid <value> | -command_device < y/n > [Security value]}

• raidcom initialize ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name <devicegroup name> [<device name>]} -operation <type>

Check with the deletion operationIt is checked to ensure that the operation is not intended to be performed for the LDEV that isalready 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 definitionfile or not (if the target LDEV information does not exist in the configuration definition file), theerror is not detected.


The command as the target of the check is shown below.

• raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}

The example of the script where the same LDEV is attempted to be added to the already createdLDEV and the execution result of the Context check is shown below.

• Example of script

raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M



• Execution result

C:\HORCM\etc>raidcom get ldev -ldev_id 1 -cnt 65280 -store ldevconf_65 > ldevconf_65.txt

C:\HORCM\etc>raidcom -zt 3_defined_ldev.bat -load ldevconf_65.dat -checkmode precheck

C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M



• Example of script (the text in bold indicates the part of incorrect configuration definition.)






raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100Mfor /l %%i in (1,1,3) do (

raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M

)

for /l %%i in (1,1,3) do (

raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M

)

• Execution result (the text in bold indicates the contents of the error accompanying the invalidconfiguration 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





raidcom: LDEV(1) is already existing as status is [1] on UnitID# 0.

raidcom_#5 : [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M



raidcom_#6 : [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M


raidcom_#7 : [EX_CTXCHK] Context Check error

The number in raidcom # of raidcom_#7: [EX_CTXCHK] Context Check error is the number oftimes of performing the raidcom command by using <work file>. The number of times isincremented each time the raidcom command is executed.

Port checkThe check is performed from the following perspective. Note that checking for object informationrelated to the port, such as external volume group or RCU, or an attribute of port, is not executed.Checking for attribute settingIt is checked whether the operation is performed for the existing port. If the port does not exist,an error is detected.If it is not clear whether the port as the target of the operation exists in the configuration definitionfile or not (if the target port information does not exist in the configuration definition file), the erroris not detected.The commands as the target of the check are shown below.

• raidcom modify port -port <port#> {[-port_speed <value>] [-loop_id <value>][-topology<topology>] [-security_switch < y|n >] | -port_attribute <port attribute>}

• raidcom add external_grp -path_grp <path group#> -external_grp_id <gnosgno> -port <port#>-external_wwn <wwn strings> -lun_id <lun#> [-emulation <emulation type>] [-clpr <clpr#>]

• raidcom add path -path_grp <path group#> -port <port#> -external_wwn <wwn strings>

• raidcom delete path -path_grp <path group#> -port <port#> -external_wwn <wwn strings>

• raidcom check_ext_storage path -path_grp <path group#> -port <port#> -external_wwn<wwn strings>

• raidcom disconnect path -path_grp <path group#> -port <port#> -external_wwn <wwn strings>

• raidcom add rcu {-rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid>| -cu_free <serial#> <id><pid>} -mcu_port <port#> -rcu_port <port#>

For example, if a path is attempted to be added to a port that does not exist, an error is detected.An example of the script where the error is detected and the execution result of the actual Contextcheck are shown below.


raidcom add path -path_grp 1 -port CL1-C -external_wwn 50060e80,06fc4180raidcom add path -path_grp 1 -port CL1-D -external_wwn 50060e80,06fc4190raidcom add path -path_grp 1 -port CL1-E -external_wwn 50060e80,06fc41a0


C:\HORCM\etc>raidcom get port -store portcnf_27.datPORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWNCL1-A FIBRE TAR AUT EF N FCAL N 0 64539 06fc1b000000fc1b


CL1-B FIBRE TAR AUT EF N FCAL N 0 64539 50060e8006fc1b01CL2-A FIBRE TAR AUT EF N FCAL N 0 64539 50060e8006fc1b10CL2-B FIBRE TAR AUT EF N FCAL N 0 64539 50060e8006fc1b11CL3-A FIBRE TAR AUT E8 N FCAL N 0 64539 50060e8006fc1b20CL3-B FIBRE TAR AUT E0 N FCAL N 0 64539 50060e8006fc1b21CL4-A FIBRE TAR AUT D6 N FCAL N 0 64539 50060e8006fc1b30CL4-B FIBRE TAR AUT D2 N FCAL N 0 64539 50060e8006fc1b31CL5-A FIBRE TAR AUT E4 N FCAL N 0 64539 50060e8006fc1b40CL5-B FIBRE TAR AUT DC N FCAL N 0 64539 50060e8006fc1b41CL6-A FIBRE TAR AUT D5 N FCAL N 0 64539 50060e8006fc1b50CL6-B FIBRE TAR AUT D1 N FCAL N 0 64539 50060e8006fc1b51CL7-A FIBRE ELUN AUT E2 N FCAL N 0 64539 50060e8006fc1b60CL7-B FIBRE ELUN AUT DA N FCAL N 0 64539 50060e8006fc1b61CL8-A FIBRE TAR AUT D4 N FCAL N 0 64539 50060e8006fc1b70CL8-B FIBRE TAR AUT CE N FCAL N 0 64539 50060e8006fc1b71C:\HORCM\etc>raidcom -zt 4_no_port.bat -load portcnf_27.dat -checkmode precheckC:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-C -external_wwn 50060e80,06fc4180raidcom: PORT(2) does not exist as status is [2] on UnitID# 0.raidcom_#2 : [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-D -external_wwn 50060e80,06fc4190raidcom: PORT(3) does not exist as status is [2] on UnitID# 0.raidcom_#3 : [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom add path -path_grp 1 -port CL1-E -external_wwn 50060e80,06fc41a0raidcom: PORT(4) does not exist as status is [2] on UnitID# 0.raidcom_#4 : [EX_CTXCHK] Context Check error

Host group checkThe check is performed from the following perspective. Note that checking for an attribute of hostgroup, or for a name of host group is not executed.Check with the attribute settingChecks whether the operation is performed for an existing host group. If the host group does notexist, an error is detected.If it is not clear whether the target port or host group exists (if the target port or host groupinformation does not exist in the configuration definition file), the error is not detected.The commands as the target of the check are shown below.

• raidcom modify host_grp -port <port#> [<host group name>] -host_mode <host mode>[-host_mode_opt <host mode option> … ]

• raidcom add hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings>

• raidcom delete hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings>

• raidcom set hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings>-wwn_nickname <WWN Nickname>

• raidcom reset hba_wwn -port <port#> [<host group name>] -hba_wwn <WWN strings>

• raidcom add lun -port <port#> [<host group name>] {-ldev_id <ldev#> [-lun_id<lun#>] |-grp_opt <group option> -device_grp_name <device group name> [<device name>]}

• raidcom delete lun -port <port#> [<host group name>] {-lun_id <lun#> | -ldev_id <ldev#> |-grp_opt <group option> -device_grp_name <device group name> [<device name>]}


Check with deletion operationIt is checked to ensure that the operation is not intended to be performed for the host group thatis 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 groupinformation does not exist in the configuration definition file), the error is not detected.The command as the target of the check is shown below.

• raidcom delete host_grp -port <port#> [<host group name>]For example, if the host group that does not exist is attempted to be deleted, an error is detected.An example of the script where the error is detected and the execution result of the actual contextcheck are shown below.


raidcom delete host_grp -port CL1-A-0raidcom delete host_grp -port CL1-A-1raidcom delete host_grp -port CL1-A-2


C:\HORCM\etc>raidcom get host_grp -port CL1-A -store hostgrpcnf_27_cl1-a.datPORT GID GROUP_NAME Serial# HMD HMO_BITsCL1-A 0 1A-G00 64539 LINUX/IRIXC:\HORCM\etc>raidcom -zt 6_no_hstgrp.bat -load hostgrpcnf_27_cl1-a.dat-checkmode precheckC:\HORCM\etc>raidcom delete host_grp -port CL1-A-0C:\HORCM\etc>raidcom delete host_grp -port CL1-A-1raidcom: PORT-HGRP(0-1) does not exist as status is [2] on UnitID# 0.raidcom_#3: [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom delete host_grp -port CL1-A-2raidcom: PORT-HGRP(0-2) does not exist as status is [2] on UnitID# 0.raidcom_#4 : [EX_CTXCHK] Context Check error

Configuration checkThe contents of a script file can be checked whether the operation is performed for the existingresource or not.Before performing the configuration check, execute the following command, acquire the currentconfiguration information, and store it in the work file specified by the -store option.Check the operation for LDEV

raidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt <group option>-device_grp_name <device group name> [<device name>]} -store <work file>

Check the operation for Port

raidcom get port -port -store <work file>


Check the operation for Host group

raidcom get host_grp -port <port#> -store <work file>

After acquiring the configuration information, execute the script by specifying the configurationfile.

raidcom -zt <created script file name> -load <work file>

Resource location and parameterMP blade location and parameter

To specify MP blade IDs by the raidcom add ldev command, specify the following IDs.

Table 19 MP blade names and parameters for XP7

MP blade IDMP blade numberMP blade name

00MPB-1MA

11MPB-1MB

22MPB-1PE

33MPB-1PF

44MPB-2MA

55MPB-2MB

66MPB-2PE

77MPB-2PF

88MPB-1MC

99MPB-1MD

1010MPB-1PL

1111MPB-1PM

1212MPB-2MC

1313MPB-2MD

1414MPB-2PL

1515MPB-2PM

Table 20 MP blade names and parameters for P9500


00MPB-1MA

11MPB-1MB

22MPB-2MC

33MPB-2MD

44MPB-1ME

55MPB-1MF

Resource location and parameter 81

Table 20 MP blade names and parameters for P9500 (continued)


66MPB-2MG

77MPB-2MH

LDEV grouping functionThe LDEV grouping function enables you to create a group of multiple LDEVs (device groupfunction and copy group function).

OverviewRAID Manager can be used to create a group of multiple LDEVs by defining copy groups, whichare a group of copy pairs. This is accomplished in both the primary and secondary configurationdefinition files by defining the group names of the combined LDEVs (dev_name of HORCM_DEVor HORCM_LDEV).To change copy group information, modify the primary and secondary configuration definitionfiles. For example, to change the LDEV configuration of copy group dbA (see following figure),change the LDEV information in configuration definition files A and B.


Figure 31 LDEV grouping for XP24000/XP20000 Disk Array and earlier

For P9500, RAID Manager can be used to create a group of multiple LDEVs by defining devicegroups. This is accomplished by defining device groups in either the primary or secondaryconfiguration definition file, but not both. By defining a device group, LDEV information can bechanged or defined in one operation. It is not required to modify LDEV information in bothconfiguration definition files. For example, referencing LDEVs or creating pools can be executedat the same time, because all LDEVs in the device group are subjected to the operation.

LDEV grouping function 83

Figure 32 LDEV grouping for P9500 and later (device group and copy group)

However, for executing replication function commands in RAID Manager, two device groupsmust be combined and defined as a copy group.When defining a device group or copy group by a command, the command can be issued frommultiple RAID Manager instances because the group information is defined in the storage system.


Device group definition methodsTo define a device group or copy group in the RAID Manager that supports P9500 or later, useone or both of following methods.

• Execute a commandCreate a device group with the raidcom add device_grp command, and execute the raidcomadd copy_grp command specifying the name of the device group to define a copy group.When the command is executed, a description corresponding to HORCM_LDEV of RAIDManager is defined in the storage system. Then, define HORCM LDEVG in the configurationfile to incorporate it into the RAID Manager instance. This can be executed at RAID Managerthat supports P9500 or later.

• Define a configuration definition fileDefine HORCM_LDEV or HORCM_DEV of the configuration definition files of the primaryand secondary volumes. For definition details, see “Configuration definition file” (page 25).

A device name is a name given to an LDEV in each device group. This is equivalent to thedev_name definition of HORCM_DEV. A device name is not required, but it is convenient to useto specify device group or device name instead of LDEV number. However, to create a pool ora journal, specifying LDEV number is required.The LDEVs that have the same device name are recognized as a pair in the primary andsecondary device group. Therefore, make match the device name for the LDEV to be a pair.Also, the number of LDEVs in the device group must be the same at the primary and secondarysides. Pairs are operated in the ascending sequence of the LDEV numbers. If there is nocorresponding device name of LDEV in the device group to be paired, an error might be occurredon the pair operation.

Read operations and command device settingsWhen grouping LDEVs, if HORCM_LDEVG on the primary side and secondary side is not defined,the read operation of RAID Manager is different depending on the command device settings.The following table shows the details.

Table 21 Reading of command device setting and group information

Security to be setReading of devicegroup or copy groupinformation

Command device settingHORCM_LDEVG

Groupinformationacquisition

Userauthentication

Security

No securityDo not readOFFOFFOFFNot defined


Do not readON


Read1OFFONOFF


Do not readON


CMD securityRead1OFFOFFON

CMD securityDo not readONOnly HORCM_DEVallowed

CMD securityRead1OFFONON


Table 21 Reading of command device setting and group information (continued)

Security to be setReading of devicegroup or copy groupinformation

Command device settingHORCM_LDEVG

Groupinformationacquisition

Userauthentication

Security


CMD securityDo not readONUser authenticationrequiredOnly HORCM_DEVallowed

-Read2---Defined

Notes:1. Read the entire group information in the storage system.2. Read the information of device group and copy group from the contents of the configuration definition file regardless of the

setting of the command device.

Define device groupA device group is created by specifying a device name and a device group name. Once a devicegroup is created, the device group name, the LDEV number, and the information if there is copygroup definition or not are stored in the storage system as configuration information.The maximum number of device groups is 1,024 in one storage system. The maximum 65,279LDEVs can be placed under the device group. And one LDEV can be placed in multiple devicegroups.

Notes when specifying a device name

• Multiple device names can be defined in one LDEV (Max: 1,024 names).

• The length of a device name must be up to 32 characters.

• In the device group that does not become an element of copy a group, the same devicename can be used in the same device group.

• In the device group that becomes an element of a copy group, a device group name mustbe unique in the device group. It is because a pair is created between LDEVs that havesame device names in respective primary and secondary volumes at the group operationof a replication series command.

Notes when specifying a device group name

• The length of a device group name must be up to 32 characters.

• A device group name must be unique within the storage system. The device group namecannot be duplicated in one storage system.

• When a device group name is specified by the raidcom command option and an LDEV tooperate is specified by the device name, all devices that have the same name with thebeginning of the specified name will be operated.

The contents of the following operations that can be executed for a device group are expressedhereafter with its use cases.1. Device group creation2. LDEV addition to device group


3. LDEV deletion from device group4. Device group deletionNote: The following symbols are used in the use cases described hereafter.


Device group creationCreating a device group by specifying a subject of multiple LDEV IDs and device group namesof the device groups to be created.

• Use cases. The following examples show use cases for creating a device group.

◦ Creating a device group configured of simplex volumes with different device names.

◦ Creating a device group configured of a simplex volume and a paired volume withdifferent device names.

◦ Creating a device group configured of simplex volumes with same device names.

LDEV addition to device groupAdding an LDEV to the device group by specifying a created device group name and the LDEVID of the LDEV to be added.


• Use CasesThe following shows use cases that can be added an LDEV to a device group.

◦ Adding an LDEV (simplex volume) with a different device name to a device group.

◦ Adding an LDEV (paired volume) with a different device name to a device group.

◦ Adding an LDEV to a device group already including the same device name.The device name can be duplicated in the case of not creating the copy group byspecifying a device group.

LDEV deletion from device groupDeleting an LDEV from the device group by specifying a created device group name and anLDEV ID of the LDEV to be deleted.


LDEV can be deleted from the device group associating a copy group. The pair status does notchange even if the LDEV is deleted from the device group.

• Use CasesThe following shows use cases that can be deleted an LDEV from a device group.

◦ Deleting an LDEV (simplex volume) not associated with a copy group from a devicegroup.

• Deleting an LDEV (paired volume) not associated with a copy group from a device group.

• Deleting an LDEV (simplex volume) associated with a copy group from a device group.

• Deleting an LDEV (paired volume) associated with a copy group from a device group.

Device group deletionDeleting an LDEV that configuring a device group by specifying a created device group nameand an LDEV ID of the LDEV to be deleted. If all the LDEVs configuring the device group are


deleted from the device, the relevant device group is deleted. And, even if a device group isdeleted, the pair status of the pair in the device group does not change.

• Use CasesThe 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 copygroup.

• Deleting a device group configured of a simplex volume and a paired volume and notassociated with a copy group.

• Deleting a device group configured of simplex volumes and associated with a copy group.

• Deleting a device group configured of paired volumes and associated with a copy group.

Copy group functionDefining a copy group by specifying two device groups: one device group from primary side andone device group from secondary side, whether they are inside or outside the storage system.A copy group cannot be defined by specifying more than one device group from just one side ofprimary or secondary.When a copy group is created, which device group is primary and which is secondary cannot bespecified. Therefore, it is specified at the time of actual pair creation. As configuration information,


a copy group name, a device group name (primary and secondary), and an MU# are maintainedin 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 createdthrough direct specification of multiple LDEVs. Create a copy group by specifying a devicegroup.

• In one device group associated as a copy group, the same device name cannot be defined.

• Copy groups with the same name cannot be defined within the same storage system.

• One device group cannot be defined to multiple copy groups.

• The maximum number of copy groups per storage system is 16,384.

• At the time of consistency group creation (pair creation) and consistency group deletion (pairdeletion), the collaboration with the group operations (device group creation/deletion, copygroup creation/deletion) is not performed.

When deleting a copy group

• If a copy group is deleted, the association of two device groups is deleted. However, theactual pair status, the consistency group ID and others are not changed (not affected). Evenif the pair status in the copy group is not single and the copy group is deleted, the copy groupdeletion processing is performed.

• If an LDEV is deleted from a device group associated as a copy group, the relevant LDEVsare deleted from all the associated copy groups.

• A copy group defines the relationship of device groups. Therefore, it is not possible to specifyan LDEV and remove it from the copy group.

• Regardless of the pair status (copy status), it is possible to exclude LDEVs from devicegroups associated as a copy group.

The contents of the following operations that can be executed for a copy group are expressedhereafter with its use cases.1. Copy group creation2. LDEV addition to copy group3. LDEV deletion from copy group4. Copy group deletion5. Pair operation by specifying a copy groupNote: The following symbols are used in the use cases described hereafter.


Copy group creationSpecifying two device groups and creating a copy group. The same device name must not bedefined for any LDEVs in a specified device group. A copy group can be created whether theLDEV in the device group is paired status or not.

• Use casesThe following shows use cases that can be created a copy group.

◦ Creating a copy group in cases where two device groups are configured of simplexvolumes and the device names and the LDEV numbers in the respective device groupsare the same.In the following example, when a copy group is created, the LDEVs within the devicenames of A to A and B to B become a subject of pair operation.

◦ Creating a copy group in cases where two device groups are configured of pairedvolumes and the device names and the LDEV numbers in the respective device groupsare the same.In the following example, although pairs have been created on the device names of Ato A and B to B, a copy group can be created.

LDEV addition to a copy groupAdding an LDEV to a device group by specifying a device group name forming a copy group. Itis not possible to add LDEVs directly to the copy group.


With the same device name, the operation for the device group associated with a copy groupcannot be performed.

• Use casesThe following shows use cases that can be added an LDEV to the device group associatinga copy group.

◦ Adding an LDEV with a different device name (simplex volume) to a device group forminga copy group.

◦ Adding an LDEV with a different device name (paired volume) to a device group forminga copy group.

LDEV deletion from copy groupDeleting an LDEV from a device group forming a copy group. It can be deleted both the simplexvolume or paired volume LDEVs.


It is not possible to delete LDEVs directly from the copy group.

• Use casesThe following shows use cases that can be deleted LDEVs from the device group forminga copy group.

◦ Deleting an LDEV (simplex volume) from a device group forming a copy group.

◦ Deleting an LDEV (paired volume) from a device group forming a copy group.

Copy group deletionDeleting a copy group by specifying a defined copy group.


• Use casesA 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.

◦ Deleting a copy group configured of paired volumes.

Pair operation by specifying a copy groupSpecifying a copy group and creating a pair. Pairs are created for which the same device namesof LDEV defined in respective device groups of the LDEVs. Therefore, it is required to give asame device name for the item to be operated as a pair.If a consistency group attribute is valid and no consistency group ID is specified, automaticallyassign a consistency group ID (1 copy group=1 consistency group). If the automatic consistencygroup assignment is specified and the other pairs in a copy group already have consistencygroup IDs, assign the same consistency group ID.


If there is no target LDEV to be a pair in the copy group, the process is terminated by detectingan error.


• Use casesAs an example of pair operation, the following shows use cases that can be created a pairby specifying a copy group.

◦ Creating a pair in cases where the device names and the numbers of LDEVs in twodevice groups in a copy group configured of simplex volumes are the same.In the following example, pairs are created with LDEVs that have the same device name,A to A and B to B.

◦ Creating a pair in cases where the device names and the numbers of LDEVs in twodevice groups in a copy group configured of simplex volumes and paired volumes arethe same.In the following example, a pair is created with LDEVs for the device name A. And nooperation is performed for the volumes of device name B that are already formed intocopy pairs.

◦ Creating a pair in cases where different device names exist in two device groups in acopy group configured of simplex volumes.In the following example, a pair for device name A can be created, but not for devicename B and C because they have different names.

◦ Creating a pair in cases where the device names in two device groups in a copy groupconfigured of simplex volumes and paired volumes are different.In the following example, a pair for device name A to A can be created. For the devicename B and C, although it does not change the paired status, but an error occursbecause they have different device names.


◦ Creating a pair in cases where the numbers of LDEVs in two device groups in a copygroup configured of simplex volumes are different.In the following example, pairs are created for the device name A to A and B to B.

Pair operations with mainframe volumesYou can create a pair with mainframe LDEVs using RAID Manager. However, some of thereplication functions are not available in RAID Manager. For more detailed information, see theuser manual for the replication function:HPP9000 Continuous Access Synchronous for MainframeSystems User Guide,HPP9000 Continuous Access Journal for Mainframe Systems User Guide,or HP P9000 Business Copy for Mainframe Systems User Guide.

Using "dummy" LUs for mainframe LDEVsPseudo-LUs called "dummy" LUs are used to access mainframe LDEVs in RAID Manager. Thedummy LUs are unconditionally defined for all mainframe device emulation types. Since thedummy LUs are used only by RAID Manager, other user interfaces such as Remote Web Consoleand host servers do not display the dummy LUs. Two dummy LUs are assigned to each mainframeLDEV. The port IDs of the mainframe PCBs are assigned as the port IDs for the dummy LUs.Host modes cannot be defined for dummy LUs.

To determine the port number for dummy LUs, use the following formula:Port#:Installed Port#(*1) (LDEV# / 0x4000) × 32

Installed Port#(*1) (LDEV# / 0x4000) × 32+1

*1: The lowest port number of the installed mainframe ports.TID: (LDEV# & 03xFCO)/64LU-M: (LDEV# &0x3F)

To perform pair operations on mainframe volumes just like on open-system volumes, include themainframe LDEV# in the HORCM_LDEV section of the configuration definition file. If you havemainframe pairs that already exist, you can verify their MU # using the raidscan command.

Pair operations with mainframe volumes 99

Pair status and access permission for mainframe LDEVsThe pair status of mainframe LDEVs is displayed in the same way as for open-system LDEVs.However, access permissions to mainframe P-VOLs and S-VOLs are different from those ofopen volumes. The following tables show the pair status and access permissions for mainframeLDEVs. For more information about displayed pair status of open LDEVs, see “Continuous AccessSynchronous/Business Copy/Continuous Access Journal pair status” (page 185).

Table 22 Pair status and access permission for Continuous Access Synchronous/ContinuousAccess Synchronous MF

NotesAccess tomainframeS-VOL

Access tomainframeP-VOL

Pair status in RAID ManagerPair status in Remote WebConsole

MainframeOpenMainframeOpen

not in pairRead/writeenabled

Read/writeenabled

SMPLSMPLSimplexSMPL

copyingRejectRead/writeenabled

COPYCOPYPendingCOPY

pairRejectRead/writeenabled

PAIRPAIRDuplexPAIR

suspendReject1Read/writeenabled

PSUSPSUSSuspendedPSUS (pairsuspendedsplit)

suspend by failureReject1Read/writeenabled

PSUEPSUESuspendedPSUE (pairsuspendederror)

inconsistency inLUSE status

---2PDUB-PDUB

ESAM only/horctakeover only

Read/writeenabled

-SSWSSSWSSSWSSSWS

Notes:1. When the system option mode 20 is on, this is a read only volume.2. PDUB (inconsistency in LUSE status) does not exist in the mainframe system.

Table 23 Pair status and access permission for Continuous Access Journal/Continuous AccessJournal MF





not in pairRead/writeenabled

Read/writeenabled

SMPLSMPLSimplexSMPL


COPYCOPYPendingCOPY


PAIRPAIRDuplexPAIR


Table 23 Pair status and access permission for Continuous Access Journal/Continuous AccessJournal MF (continued)





suspendReject*Read/writeenabled

PSUSPSUSSuspendPSUS (pairsuspendedsplit)


PSUEPSUESuspendPSUE (pairsuspendederror)


PAIRPAIRSuspendingSuspending

pair/copyingRejectRead/writeenabled

PAIR / COPYPAIR / COPYDeletingDeleting


PSUSPSUSHoldHOLD

suspend-Read/writeenabled

PSUSPSUSHoldingHOLDING

suspendRejectRead/writeenabled

PSUEPSUEHldePSUS (HLDE)


PFULPFULSuspendPFUL


PFUSPFUSSuspendPFUS

suspendRead/writeenabled

-SSWSSSWSSuspendSSWS

*When system option mode 20 is on, this is a read-only volume.

Table 24 Pair status and access permission for Business Copy/Business Copy MF



Pair status in RAIDManager

Pair status in Remote WebConsole


simplexRead/writeenabled

Read/writeenabled

SMPLSMPLSimplexSMPL


COPYCOPYPendingCOPY(PD)


PAIRPAIRDuplexPAIR

suspend (inCOPY(SP)COPY-COPY)

RejectRead/writeenabled

COPYCOPYSP-PendCOPY (SP)

suspend (in QuickSplit PSUS-COPY)

Read/writeenabled

Read/writeenabled

PSUSPSUSV-splitPSUS (SP)

suspendRead/writeenabled

Read/writeenabled

PSUSPSUSSplitPSUS (pairsuspendedsplit)

Pair operations with mainframe volumes 101

Table 24 Pair status and access permission for Business Copy/Business Copy MF (continued)



Pair status in RAIDManager

Pair status in Remote WebConsole


suspend by failureRejectRead/writeenabled

PSUEPSUESuspendPSUE (pairsuspendederror)

resynchronizingRejectRead/writeenabled

COPYCOPYResyncCOPY (RS)

restoringRejectRejectRCPYRCPYResync-RCOPY (RS-R)

Operational differences for multiplatform volumesThe following table shows the operational differences for Continuous Access Synchronous,Continuous Access Journal, and Business Copy multiplatform volumes.

Table 25 Operational differences for multiplatform volumes

Continuous AccessJournal operations

Continuous AccessSynchronousoperations

Business Copy operationsLU path informationreported to RAIDManager

LU path definition

Commands arerejected.


Business Copy MFoperations

Actual LU pathinformation is reported.

LU path is defined.



Business Copy MFoperations

Dummy LU number isreported.

LU path is notdefined.

Operational differences for replication commandsThe following table shows the differences between open volumes and mainframe volumes inreplication commands. For details on the differences, see the manual for each program product.

Table 26 Differences in replication commands

NotesOperation inmainframe systems

Operation inopen systems

DescriptionOptionCommand

This option is not supportedin Continuous Access Journal

Continuous AccessSynchronous MF:

ContinuousAccessSynchronous:

Specifies track sizewhen copying.

-c <size>paircreate*

or Continuous AccessJournal MF.

3 or 15 tracksWhen you specify thenumber 1 to 3, thecopy speed is 3 tracks.

You can specify 1to 15 tracks. There is no difference

between Business Copy andBusiness Copy MF.

When you specify thenumber 4 to 15, thecopy speed is 15tracks.

Business Copy pairs andBusiness Copy MF pairs

You can specify thisoption.

You can specifythis option.

If CTG ID is notspecified, CTG ID is

-m grp[CTG ID]

cannot be registered to theautomaticallysame CTG ID. If bothassigned and a pairBusiness Copy pairs andis registered to theBusiness Copy MF pairs areconsistency group.registered to one group, thecommand ends abnormally.

If CTG ID isspecified, a pair isregistered to theCTG ID in use.


Table 26 Differences in replication commands (continued)

NotesOperation inmainframe systems

Operation inopen systems

DescriptionOptionCommand

This option is only forContinuous Access

The volume cannot beread regardless ofspecified options.

-r: Read only-rw: Read/writeenabled

Specifies accessmode to S-VOLafter splitting a pair.

-r-rw

pairsplit

Synchronous, ContinuousAccess Synchronous MF,Continuous Access Journal,and Continuous AccessJournal MF.You cannot specify thisoption in Business Copy orBusiness Copy MF.

*If the capacity of the S-VOL is larger than that of the P-VOL, you cannot create a pair with RAID Manager. To create aContinuous Access Synchronous MF pair with volumes that differ in capacity, use Business Continuity Manager or RemoteWeb Console.Notes:

• A mainframe primary volume can also be called a source volume or a main volume.

• A mainframe secondary volume can also be called a target volume or a remote volume.

Multi-array virtualization function (XP7)The multi-array virtualization function enables you to minimize rewrites of configuration definitionfiles (horcm*.conf) when you operate volumes migrated from older models to the XP7. You canalso minimize the modification of the script file that you used for the older models, when youoperate volumes using the script file created by you. For details about the multi-array virtualizationfunction, see the Provisioning Guide for the storage system. Volume migration (Online Migration)from older models by using the multi-array virtualization function is supported only on the XP7.

System configuration example with the multi-array virtualization functionThis topic shows a system configuration with the multi-array virtualization function. In thisconfiguration, a virtual storage machine is created in two storage systems respectively. Volumesin the virtual storage machine are given virtual LDEV IDs.

• Primary site

Storage system: XP7 (S/N: 67000)◦◦ Virtual storage machine: P9500 (S/N: 65000)

◦ LDEV ID of XP7: 10:00 and 10:01

◦ Virtual LDEV ID: 01:00 and 01:01

• Secondary site

Storage system: XP7 (S/N: 68000)◦◦ Virtual storage machine: P9500 (S/N: 66000)

◦ LDEV ID of XP7: 10:00 and 10:01

◦ Virtual LDEV ID: 02:00 and 02:01

Multi-array virtualization function (XP7) 103

Using RAID Manager in a system configuration with the multi-array virtualizationfunction

To use RAID Manager with the system configuration using the multi-array virtualization function,the following two methods can be used.

• Specifying a virtual storage machine to HORCM_VCMD in configuration definition files

• Specifying a virtual storage machine to command options (that is, -s <seq#> or -u <unit id>)If you specify the virtual storage machine to HORCM_VCMD of the configuration file, the shellscripts can be used continuously, because you do not need to modify their scripts. However, ifyou define HORCM_VCMD, you cannot operate the virtual storage machine whose the serialnumber is not specified by HORC_VCMD. If you specify the virtual storage machine to thecommand options (that is, -s <seq#> or -u <unit id>) instead of specifying with HORCM_VCMD,you can also operate the virtual storage machine of the serial number not specifying toHORCM_VCMD.After you change the virtual storage machine configuration with the raidcom add resourcecommand or the raidcom delete resource command, restart HORCM.

Configuration definition file settings with multi-array virtualizationThis topic shows configuration definition file settings with the multi-array virtualization function.For details on other parameters, see “Configuration definition file” (page 25). The multi-arrayvirtualization function is supported on the XP7 storage system.

• HORCM_CMDSpecify a volume belonging to meta_resource or a virtual storage machine in the storagesystem as the command device. RAID Manager obtains the virtual storage machineinformation defined in the storage system via the specified command device, and configuresthe virtual storage machine components.


When you specify a volume that belongs to a virtual storage machine, note the following:

◦ Use the serial number of the virtual storage machine and the virtual LDEV ID for theserial number and LDEV ID which you are specifying for HORCM_CMD.

◦ You cannot specify HORCM_VCMD to the same configuration definition file.

◦ You cannot define the volume that does not belong to the virtual storage machine tothe HORCM_CMD of the same configuration definition file.

NOTE: The mkconf command lets you create the configuration definition file by importingthe special file name from the standard input. When you create a configuration definition fileby using the mkconf command, make sure that the special file name of the volume thatbelongs to the virtual storage machine and the special file name of the volume that does notbelong to the virtual storage machine are different.

• HORCM_VCMDIn HORCM_VCMD, specify the serial number of the virtual storage machine to be operatedby this instance.You cannot operate the virtual storage machines whose serial numbers are not specified inHORCM_VCMD. To operate more than one virtual storage machine from a instance, specifyeach serial number of the virtual storage machines in a new line with HORCM_VCMD. Tooperate the virtual storage machine specified in the second or later of HORCM_VCMD, usethe command options (for example, -s <seq#> or -u <unit id>). If you omit the options of thecommand, the virtual storage machine of which you first specified serial number is operated.Even if you specify the virtual storage machine of which the serial number is not specifiedin HORCM_VCMD with the command option (-s <seq#> or -u <Unit ID>), the error(EX_ENOUNT) occurs.

• HORCM_LDEVSpecify volumes to be copied. Serial numbers of the virtual storage machine and virtualLDEV IDs must be specified. You cannot specify the volumes with HORCM_DEV in thesystem configuration with the multi-array virtualization function. Specify the volumes withHORCM_LDEV.

• HORCM_INSTSpecify an IP address and a service name of the remote host as it is for not using themulti-array virtualization function.

Example of the configuration definition files when specifying a virtual storage machineby HORCM_CMD

The following examples show when a volume belonging to meta_resource is specified forHORCM_CMD.

Example of the configuration definition files (HORCM0)The underlined parts indicate the information that needs to modify from the file of the old model.#/******** HORCM0 on PHOST *****/HORCM_MON#ip_address service poll(10ms) timeout(10ms)NONE horcm0 1000 3000

#/********** For HORCM_CMD ****************/HORCM_CMD#dev_name\\.\CMD-367000:/dev/rdskHORCM_VCMD


# redefine Virtual DKC Serial# as unitIDs65000

HORCM_LDEVOra dev1 65000 01:00 h1Ora dev2 65000 01:01 h1

#/********** For HORCM_INST ****************/HORCM_INST#dev_group ip_address serviceOra RHOST horcm1

Example of the configuration definition files (HORCM1)The underlined parts indicate the information that needs to modify from the file of the old model.#/******** HORCM1 on RHOST *****/HORCM_MON#ip_address service poll(10ms) timeout(10ms)NONE horcm1 1000 3000

#/********** For HORCM_CMD ****************/HORCM_CMD#dev_name\\.\CMD-368000:/dev/rdskHORCM_VCMD# redefine Virtual DKC Serial# as unitIDs66000

HORCM_LDEVOra dev1 66000 02:00 h1Ora dev2 66000 02:01 h1

#/********** For HORCM_INST ****************/HORCM_INST#dev_group ip_address serviceOra PHOST horcm0

raidqry command display example# raidqry -lNo Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB)1 --- raidmanager 01-31-03/00 0 66000 80-01-00/00 81920

The following examples show when the storage system is XP7 and a volume belonging to avirtual storage system is specified for HORCM_CMD.

Example of the configuration definition files (HORCM0)It is not necessary to change HORCM_CMD used in the previous model or to add HORCM_VCMD.#/******** HORCM0 on PHOST *****/HORCM_MON#ip_address service poll(10ms) timeout(10ms)NONE horcm0 1000 3000#/********** For HORCM_CMD ****************/HORCM_CMD#dev_name\\ . \ CMD-65000:/dev/rdskHORCM_LDEVOra dev1 65000 01:00 h1Ora dev2 65000 01:01 h1#/********** For HORCM_INST ****************/HORCM_INST#dev_group ip_address serviceOra RHOST horcm1


Example of the configuration definition files (HORCM1)It is not necessary to change HORCM_CMD used in the previous model or to add HORCM_VCMD.#/******** HORCM1 on RHOST *****/HORCM_MON#ip_address service poll(10ms) timeout(10ms)NONE horcm1 1000 3000#/********** For HORCM_CMD ****************/HORCM_CMD#dev_name\\ . \ CMD-66000:/dev/rdskHORCM_LDEVOra dev1 66000 02:00 h1Ora dev2 66000 02:01 h1#/********** For HORCM_INST ****************/HORCM_INST#dev_group ip_address serviceOra PHOST horcm0

Specifying a virtual storage machine to HORCM_VCMDThis section covers the following topics:

• “Command operations to the virtual storage machine” (page 107)

• “Operation target for raidcom commands when specifying the virtual storage machine inHORCM_VCMD” (page 109)

Command operations to the virtual storage machineWhen HORCM starts, RAID Manager obtains the virtual storage machine information from multiplestorage systems, and configure each virtual storage machine component. RAID Manager regardscommands as the command to the virtual storage machine by the descriptions of the configurationdefinition file or the command options (i.e., -s <seq#> or -u <unit id>), and use their information.The following table shows how to issue the command to the virtual storage machine for eachcommand.

RemarksHow to issue the command to the virtual storagemachine

Commands

---Describe the virtual storage machine information inHORCM_LDEV in the configuration definition file.

paircreate


pairsplit


pairresync


pairevtwait


pairvolchk


pairdisplay


paircurchk


horctakeover


raidvchkset



Commands


raidvchkdsp


pairsyncwait


pairmon

You cannot specify a virtualstorage machine by the -u

Specify the virtual storage machine by the -s <seq#> or the-p <port#> (to specify the unit ID) option.

raidscan

<unit ID> option of theThe virtual storage machine can be specified regardless ofthe description contents of the configuration definition file. raidscan command. Use the

-s <seq#> option, or the -p<port#> to specify as "CL1-An"(n is the unit ID).

The raidar command has nooption to specify a serial

Specify the virtual storage machine by a unit ID by thecommand option (-p <port#>).

raidar

number nor a unit ID. Use the-p <port#> option as "CL1-An"(specify a unit ID in n).

The information of XP7 andthe virtual storage machine isdisplayed.

---raidqry

If you are specifying acommand device in a virtual

Specify the virtual storage machine by the command option(-s <seq#> or -u <unit ID>).

raidvchkscan

storage machine for whichThe virtual storage machine can be specified regardless ofthe description contents of the configuration definition file. user authentication is disabled

to the HORCM_CMD, do notspecify the -v jnl and -vpid option.

If you specify the virtualstorage machine information,

Specify XP7 information.horcctl

error (No such control device)occurs.This command cannot be usedif you specify a volumebelonging to a virtual storagemachine to HORCM_CMD.

When you specify a volumethat belongs to meta_resource

Specify the virtual storage machine by the command option(-s <seq#> or -u <unit ID>).

raidcom

for HORCM_CMD, if youThe virtual storage machine can be specified regardless ofthe description contents of the configuration definition file. specify the virtual storage

machine for the commandoption, some commands canbe executed using the virtualstorage machine information(see “Operation target forraidcom commands whenspecifying the virtual storagemachine in HORCM_VCMD”(page 109)).When you specify a volumethat belongs to a virtualstorage machine forHORCM_CMD, there is alimitation of which commandyou can use. You can executeby using the virtual storage



Commands

machine information if theraidcom command can beused and if you specify thevirtual storage machine for thecommand option (see“raidcom commands forvolumes that belong to virtualstorage machine forHORCM_CMD” (page 113)).

Operation target for raidcom commands when specifying the virtual storage machine inHORCM_VCMD

The virtual storage machine specified in HORCM_VCMD becomes the operation target if youdo not specify the -s <seq#> (serial number) and -u <unit ID> (unit ID of the command device)options of the raidcom commands. The operational targets according to the definition ofHORCM_VCMD are shown in the table below.

• When you specify the virtual storage machine in HORCM_VCMD and the operation targetfor the raidcom command is a virtual storage machine, the operational target is: The virtualstorage machine of the first serial number specified in HORCM_VCMD.

• When you specify the virtual storage machine in HORCM_VCMD and the operation targetfor the raidcom command is XP7, the operational target is: XP7 for which the virtual storagemachine of the first serial number specified in HORCM_VCMD is defined.

Operation targets according to the definition ofHORCM_VCMD

CommandsOperationtype

XP7raidcom get copy_grpCopy group

XP7raidcom add copy_grp

XP7raidcom delete copy_grp

XP7raidcom get device_grpDevice group

XP7raidcom add device_grp

XP7raidcom delete device_grp

XP7raidcom get external_grpExternalvolume group

XP7raidcom add external_grp

XP7raidcom delete external_grp

XP7raidcom modify external_grp

XP7raidcom disconnect external_grp

XP7raidcom get host_grpHost group

XP7raidcom add host_grp

XP7raidcom delete host_grp

XP7raidcom modify host_grp

XP7raidcom get hba_wwnWWN

XP7raidcom add hba_wwn

XP7raidcom delete hba_wwn




XP7raidcom set hba_wwn

XP7raidcom reset hba_wwn

XP7raidcom get hba_iscsiiSCSI nameand CHAPuser name XP7raidcom add hba_iscsi

XP7raidcom delete hba_iscsi

XP7raidcom set hba_iscsi

XP7raidcom reset hba_iscsi

XP7raidcom get chap_user

XP7raidcom add chap_user

XP7raidcom delete chap_user

XP7raidcom set chap_user

XP7raidcom reset chap_user

XP7raidcom send ping

XP7raidcom get journalJournal

XP7raidcom add journal

XP7raidcom delete journal

XP7raidcom modify journal

Virtual storage machineraidcom get ldevLDEV

XP7raidcom add ldev

XP7raidcom delete ldev

XP7raidcom modify ldev

XP7raidcom extend ldev

XP7raidcom initialize ldev

Virtual storage machineraidcom get lunLUN

Virtual storage machineraidcom add lun

Virtual storage machineraidcom modify lun

Virtual storage machineraidcom delete lun

XP7raidcom get pathExternal path

XP7raidcom add path

XP7raidcom delete path

XP7raidcom disconnect path

XP7raidcom check_ext_storage path

XP7raidcom check_ext_storage external_grp

XP7raidcom discover external_storage

XP7raidcom discover lun




XP7raidcom get external_iscsi_name

XP7raidcom add external_iscsi_name

XP7raidcom delete external_iscsi_name

XP7raidcom modify external_chap_user

XP7raidcom get initiator_iscsi_name

XP7raidcom modify initiator_chap_user

XP7raidcom discover external_iscsi_name

XP7raidcom check external_iscsi_name

XP7raidcom get poolPool

XP7raidcom get thp_pool

XP7raidcom get snap_pool

XP7raidcom add thp_pool

XP7raidcom add snap_pool

XP7raidcom delete pool

XP7raidcom modify pool

XP7raidcom reallocate pool

XP7raidcom monitor pool

XP7raidcom initialize pool

XP7raidcom get portPort

XP7raidcom modify port

XP7raidcom get rcuRCU

XP7raidcom add rcu

XP7raidcom delete rcu

XP7raidcom modify rcu

XP7raidcom add rcu_pathLogical pathto RCU

XP7raidcom delete rcu_path

XP7raidcom add rcu_iscsi_port

XP7raidcom delete rcu_iscsi_port

XP7raidcom get rcu_iscsi_port

XP7raidcom get parity_grpParity group

XP7raidcom get ssidSSID

XP7raidcom add ssid

XP7raidcom delete ssid

XP7raidcom get resourceResourcegroup

XP7raidcom add resource




XP7raidcom delete resource

XP7raidcom lock resource

XP7raidcom unlock resource

XP7raidcom map resource

XP7raidcom unmap resource

XP7raidcom get clprCLPR

XP7raidcom modify clpr

Virtual storage machineraidcom get snapshotFast Snap

Virtual storage machineraidcom add snapshot

Virtual storage machineraidcom delete snapshot

Virtual storage machineraidcom modify snapshot

XP7raidcom get pfc_wwnPerformanceControl

XP7raidcom get pfc_group

XP7raidcom add pfc_wwn

XP7raidcom add pfc_group

XP7raidcom delete pfc_wwn

XP7raidcom delete pfc_group

XP7raidcom modify pfc_wwn

XP7raidcom modify pfc_group

XP7raidcom monitor pfc_wwn

XP7raidcom monitor pfc_group

XP7raidcom modify pfc_ldev

XP7raidcom delete pfc_ldev

XP7raidcom monitor pfc_ldev

XP7raidcom get pfc_ldev

XP7raidcom get licenseProgramproduct

XP7raidcom modify local_replica_optLocal replicaoption

XP7raidcom get local_replica_opt

XP7raidcom get command_statusOthers

XP7raidcom reset command_status

XP7raidcom get error_message


raidcom commands for volumes that belong to virtual storage machine for HORCM_CMDYou can use the following raidcom commands when you specify a volume that belongs to virtualstorage machine in HORCM_CMD:

raidcom command#

raidcom get ldev1

raidcom delete ldev2

raidcom add lun3

raidcom get lun4

raidcom modify port5

raidcom get port6

raidcom add host_grp7

raidcom delete host_grp8

raidcom get host_grp9

raidcom modify host_grp10

raidcom add hba_wwn11

raidcom delete hba_wwn12

raidcom get hba_wwn13

raidcom get resource14


4 Starting up RAID ManagerYou can begin using the RAID Manager software after you have installed the RAID Managersoftware, set the command device, created the configuration definition file(s), and (for OpenVMSonly) followed the porting requirements and restrictions. One or two instances of RAID Managercan be used simultaneously in UNIX, Windows, and OpenVMS operating system environments.

Starting up on UNIX systemsOne instanceTo start up one instance of RAID Manager on a UNIX system:1. 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/udpxxxxx = the port name/number for horcm.conf

2. If you want RAID Manager to start automatically each time the system starts up, add/etc/horcmstart.shto the system automatic startup file (for example, /sbin/rc).

3. Execute the horcmstart.sh script manually to start the RAID Manager instances: #horcmstart.sh

4. Set the log directory (HORCC_LOG) in the command execution environment as needed.5. If you want to perform Continuous Access Synchronous operations, do not set the

HORCC_MRCF environment variable. If you want to perform Business Copy operations,set theHORCC_MRCF environment variable for the RAID Manager execution environment.For B shell:# HORCC_MRCF=1 # export HORCC_MRCFFor C shell:# setenv HORCC_MRCF 1 # pairdisplay -gxxxx xxxx = group name

Two instancesTo start up two instances of RAID Manager on a UNIX system:1. Modify /etc/services to register the port name/number (service) of each configuration

definition file. The port name/number must be different for each RAID Manager instance.horcm0xxxxx/udpxxxxx = the port name/number for horcm0.confhorcm1yyyyy/udpyyyyy = the port name/number for horcm1.conf

2. If you want RAID Manager to start automatically each time the system starts up, add/etc/horcmstart.sh 0 1 to the system automatic startup file (for example, /sbin/rc).

3. Execute the horcmstart.sh script manually to start the RAID Manager instances: #horcmstart.sh 0 1

4. Set an instance number to the command execution environment:For B shell:# HORCMINST=X # export HORCMINSTX = instance number = 0 or 1For C shell:# setenv HORCMINSTX

114 Starting up RAID Manager

5. Set the log directory (HORCC_LOG) in the command execution environment as needed.6. If you want to perform Continuous Access Synchronous operations, do not set the

HORCC_MRCF environment variable. If you want to perform Business Copy operations,set theHORCC_MRCF environment variable for the RAID Manager execution environment.For B shell:# HORCC_MRCF=1 # export HORCC_MRCFFor C shell:# setenv HORCC_MRCF 1 # pairdisplay -gxxxxxxxx = group name

Starting up on Windows systemsOne instanceTo start up one instance of RAID Manager on a Windows system:1. Modify%windir%\system32\drivers\etc\services to register the port name/number (service)

of the configuration definition file. Make the port name/number the same on all servers:horcmxxxxx/udp xxxxx = the port name/number of horcm.conf

2. If you want RAID Manager to start automatically each time the system starts up, add\HORCM\etc\horcmstart to the system automatic startup file (for example, \autoexec.bat).

3. Execute the horcmstart script manually to start RAID Manager:D:\HORCM\etc> horcmstart4. Set the log directory (HORCC_LOG) in the command execution environment as needed.5. If you want to perform Continuous Access Synchronous operations, do not set the

HORCC_MRCF environment variable. If you want to perform Business Copy operations,set theHORCC_MRCF environment variable for the RAID Manager execution environment:D:\HORCM\etc> set HORCC_MRCF=1 D:\HORCM\etc> pairdisplay -gxxxxxxxx = group name

Two instancesTo start up two instances of RAID Manager on a Windows system:1. Modify%windir%\system32\drivers\etc\services to register the port name/number (service)

of the configuration definition files. Make sure that the port name/number is different for eachinstance:horcm0xxxxx/udpxxxxx = the port name/number of horcm0.confhorcm1xxxxx/udpxxxxx = the port name/number of horcm1.conf

2. If you want RAID Manager 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).

3. Execute the horcmstart script manually to start RAID Manager:D:\HORCM\etc> horcmstart0 1

4. Set an instance number to the command execution environment: D:\HORCM\etc> setHORCMINST=XX = instance number = 0 or 1

5. Set the log directory (HORCC_LOG) in the command execution environment as needed.

Starting up on Windows systems 115

6. If you want to perform Continuous Access Synchronous operations, do not set theHORCC_MRCF environment variable. If you want to perform Business Copy operations,set theHORCC_MRCF environment variable for the RAID Manager execution environment:D:\HORCM\etc> set HORCC_MRCF=1 D:\HORCM\etc> pairdisplay -gxxxxxxxx = group name

Starting up on OpenVMS systemsOne instanceTo start up one instance of RAID Manager on an OpenVMS system:1. Create the configuration definition file.

For a new installation, use the configuration definition sample file that is supplied(SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Make a copy of the file: $ COPYSYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc]Edit this file according to your system configuration using a text editor (for example, eve).Register the port name (service) of the configuration definition file in"SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT ".horcm xxxxx/udp xxxxx = port numberUse the same port number in all servers. The port number can be directly specified withoutregistering it in "SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT".

2. Manually execute the HORCM startup command.$ spawn /nowait /process=horcm horcmstart

NOTE: The subprocess (HORCM) created by SPAWN is terminated when the terminalis LOGOFF or the session is terminated. If you want an independent process to the terminalLOGOFF, use the "RUN /DETACHED" command.

3. 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 logdirectory of Horc Manager must be set for each node. The log directory of Horc Managercan be changed by setting the parameter of horcmstart. See the RAID Manager ReferenceGuide for information about horcmstart parameters.

If you want to perform Business Copy operations, set the environment variable(HORCC_MRCF). $ HORCC_MRCF:=1 $ pairdisplay -gxxxx xxxx = group name

NOTE: If a system configuration change or a RAID configuration change causes this file tochange, (for example, cache size change or microcode change), these changes will not takeeffect until you stop HORCM (horcmshutdown) and restart HORCM (horcmstart). Use the "-c"option of the pairdisplay command to verify that there are no configuration errors.

Two instancesTo start up two instances of RAID Manager on an OpenVMS system:


1. Create the configuration definition files.For a new installation, use the configuration definition sample file that is supplied(SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Copy the file twice, once for each instance.$ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc]horcm0.conf$ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc]horcm1.confEdit these two files according to your system configuration using a text editor (for example,eve).Register the port name (service) of the configuration definition file in"SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT".horcm0xxxxx/udp xxxxx = port number horcm1yyyyy/udp yyyyy = port numberEach instance should have a unique port number.The port number can be directly specified without registering it in"SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT".

2. Execute the HORCM startup command.$ spawn /nowait /process=horcm0 horcmstart 0 $ spawn /nowait /process=horcm1horcmstart 1

NOTE: The subprocess (HORCM) created by SPAWN is terminated when the terminalis LOGOFF or the session is terminated. If you want an independent process to the terminalLOGOFF, use "RUN /DETACHED" command.

3. Set the HORCM instance numbers in the environment in which the command is to beexecuted: $ HORCMINST:=X X = instance number (0 or 1)

4. Confirm the configuration using a RAID Manager command.Set the log directory (HORCC_LOG) in the command execution environment as required.

NOTE: If the log directory under SYS$POSIX_ROOT is shared with other nodes, the logdirectory of Horc Manager must be set for each node. The log directory of Horc Managercan be changed by setting the parameter of horcmstart. See the RAID Manager ReferenceGuide for information about horcmstart parameters.

If you want to perform Business Copy operations, set the environment variable(HORCC_MRCF). $ HORCC_MRCF:=1 $ pairdisplay -gxxxx xxxx denotes a group name.

NOTE: If a system configuration change or a RAID configuration change causes this file tochange (for example, cache size change, microcode change), these changes will not take effectuntil you stop HORCM (horcmshutdown 0 1) and restart HORCM (horcmstart 0 and horcmstart1). Use the "-c" option of the pairdisplay command to verify that there are no configuration errors.

Starting RAID Manager as a service (Windows systems)Usually, RAID Manager (HORCM) is started by executing the startup script from the Windowsservices. However, in the VSS environment, there is no interface to automatically start RAIDManager. RAID Manager provides the svcexe.exe command and a sample script file(HORCM0_run.txt) so that RAID Manager can be started automatically as a service.

Starting RAID Manager as a service (Windows systems) 117

C:\HORCM\tool\>svcexe

• Usage for adding [HORCM_START_SVC]: svcexe /A=command_path

◦ for deleting [HORCM_START_SVC]: svcexe /D

◦ for specifying a service: svcexe /S=service_name

◦ for dependent services: svcexe /C=service_name,service_name

This command example uses HORCM0 for registering the service name for HORCM instance#0:

• Example for adding [HORCM0]: svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"

◦ for deleting [HORCM0]: svcexe /S=HORCM0 /D

◦ for starting [HORCM0]:

:[1] make a C:\HORCM\tool\HORCM0_run.txt file.:[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 RAID Manager as a service1. Registering the RAIDManager (HORCM) instance as a service. The system administrator

must add the RAID Manager instance using the following command:C:\HORCM\tool\>svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"

2. Customizing a sample script file. The system administrator must customize the samplescript file (HORCM0_run.txt) according to the RAID Manager instance. For details, see thedescriptions in the HORCM0_run.txt file.

3. Setting the user account. The system administrator must set the user account for the RAIDManager administrator as needed.When using the GUI, use "Administrative Tools - Services - Select HORCM0 - Logon".When using the CUI, use "sc config" command as follows:C:\HORCM\tool\>sc config HORCM0 obj= AccountName password= password

If the system administrator uses the default account (LocalSystem), add"HORCM_EVERYCLI=1":# **** For INSTANCE# X, change to HORCMINST=X as needed ****START:set HORCM_EVERYCLI=1set HORCMINST=0set HORCC_LOG=STDERROUTC:\HORCM\etc\horcmstart.exeexit 0

4. Starting the RAID Manager instance from the service. After you have confirmed starting andstopping using "horcmstart 0" and "horcmshutdown 0", you must verify that HORCM0 startsfrom the service and that HORCM0 started automatically from REBOOT, using the followingcommand:C:\HORCM\tool\>net start HORCM0


5. Stopping RAID Manager instance as a service. Instead of using the "horcmshutdown 0"command, you must use the following command to stop HORCM0:C:\HORCM\tool\>net stop HORCM0(By using the "horcmshutdown 0" command, the script written into HORCM0_run.txt willautomatically restart HORCM0).

Starting RAID Manager as a service (Windows systems) 119

5 Provisioning operations with RAID ManagerThis chapter describes storage provisioning operations with RAID Manager.

About provisioning operationsYou can use RAID Manager to perform provisioning operations on the following storage systems:

• XP7 Storage

• P9500For details about the provisioning operations, see the Provisioning Guide for the storage system.

NOTE: Be aware of the following when performing provisioning operations using RAID Manager:• When you execute provisioning operations using RAID Manager, the operation of refreshing

the window (Remote Web Console, SVP) might be delayed.• During maintenance work on the storage system (Remote Web Console in modify mode),

or when the configuration is being changed from the GUI, the RAID Manager provisioningcommand might be rejected (2E10, 8000).

• When you execute commands for provisioning operations, host I/O performance mightdeteriorate because of increased working ratio of processor by updating processing of theconfiguration information of storage system. If you plan to execute many commands, takeaccount of the impact on the I/O performance.

Overview of the configuration setting commandRAID Manager functions enable provisioning operations such as host setting, LDEV creation,and device group creation. These operations are performed using the raidcom configurationsetting command.The configuration setting command is specified using the following syntax:

raidcom <action> <resource> <parameter>

The operation itself, such as add or delete, is specified in the action, and the resource object,such as LDEV or path, is specified in the resource. The necessary value to operate the resourceobject is specified in the parameter. For the details about the raidcom configuration settingcommand, see the RAID Manager Reference Guide.Because some provisioning operations can take time to process, RAID Manager provides twoways to execute the configuration setting command: synchronously or asynchronously.The processing difference between these two command types are described in “Synchronouscommand processing” (page 120) and “Asynchronous command processing” (page 120).

Synchronous command processingIn addition to the replication commands, the process is executed by synchronizing with a commandexecution, and then returning a response after the processing is completed. When an erroroccurs, the error is returned to RAID Manager at each occurrence.

Asynchronous command processingWhen an asynchronous command is executed, the command is received at the storage system,and a response is returned before the processing is executed. The actual processing is executedasynchronously with command input.The completion of the asynchronous command processing can be checked with the raidcomget command_status command. When you execute the raidcom get command_status

120 Provisioning operations with RAID Manager

command after executing an asynchronous command, the raidcom get command_statuscommand is terminated after all asynchronous command processing has been completed.

Errors during asynchronous command processingWhen an error occurs during asynchronous command processing, the error information, suchas the total number of errors or error code (SSB1 and SSB2), is provided. After executing theasynchronous command, execute the raidcom get command_status command to checkthe error information if the asynchronous command processing completed normally.Error codes SSB1 and SSB2 are stored only at the first error occurrence. For the second andsubsequent occurrences, only the number of the error occurrence is stored with no error code.Therefore, before executing an asynchronous command, reset the error information in the storagesystem using the raidcom reset command_status command. You can check the informationin SSB1 and SSB2 by using the raidcom get error_message command.In asynchronous command processing, multiple commands received by the host are executedat the same time. Therefore, the total number of errors might not correspond with the unexecutedcommands. If an error occurs in asynchronous commands, verify the system configuration usingthe reference commands. For details about the reference commands, see “Available provisioningoperations” (page 123).

Workflow for executing asynchronous commandsWhen executing asynchronous commands, execute the command or script using the followingprocedure:1. Execute the raidcom reset command_status command.

The error information of asynchronous command processing in the storage system is reset.2. Execute the asynchronous command.3. Execute the raidcom get command_status command to check if all asynchronous

command processing is done or if no error occurred.

Asynchronous commandsThe asynchronous commands associated with the raidcom configuration setting commandprovide provisioning functions. The following table lists the provisioning functions performed byasynchronous commands and describes the required syntax. For details about raidcom commandsyntax, see the RAID Manager Reference Guide.

Table 27 Asynchronous commands of the configuration setting command

Command syntaxFunction

raidcom modify ldev -ldev_id <ldev#> -status blkBlocking an LDEV

raidcom add ldev {-parity_grp_id <gno-sgno>| - external_grp_id <gno-sgno> |-pool {<pool ID#> | <pool naming> | snap}} -ldev_id <ldev#> { -capacity <size> |

Adding an LDEV

-offset_capacity <size> | -cylinder <size>} [-emulation <emulation type>][-location<lba>][-mp_blade_id <mp#>]

raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name<device group name> [<device name>]}

Deleting an LDEV

raidcom initialize ldev {-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]} -operation qfmt

LDEV Quick Format

raidcom modify ldev -ldev_id <ldev#> -status nmlRestoring an LDEV

raidcom add ldev -pool {<pool ID#> | <pool naming>| snap} -ldev_id <ldev#>-capacity <size>

Creating virtual volume for ThinProvisioning, Thin Provisioning MF, SmartTiers, Real Time Smart Tier, Smart Tiers

About provisioning operations 121

Table 27 Asynchronous commands of the configuration setting command (continued)


MF, Real Time Smart Tier for Mainframe,or Snapshot

raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name<device group name> [<device name>]}

Deleting virtual volume for ThinProvisioning, Thin Provisioning MF, SmartTiers, Real Time Smart Tier, Smart TiersMF, Real Time Smart Tier for Mainframe,or Snapshot

raidcom add thp_pool {{-pool_id <pool ID#> [-pool_name <pool naming>] |-pool_name <pool naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -pool_name

Creating a pool /adding a pool volume forThin Provisioning or Thin Provisioning MF

<pool naming>} {-ldev_id <ldev#> …[-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}[ -user_threshold<threshold_1> [<threshold_2>] ]

raidcom add snap_pool {{-pool_id <pool ID#> [-pool_name <pool naming>] |-pool_name <pool naming> [-pool_id <pool ID#>]} | -pool_id <pool ID#> -pool_name

Creating a pool /adding a pool volume forSnapshot

<pool naming>}} {-ldev_id <ldev#> …[-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}[-user_threshold <%>]

raidcom delete pool -pool {<pool ID#> | <pool naming>}[-ldev <ldev#>]Deleting or shrinking a pool

raidcom modify pool -pool {<pool ID#> | <pool naming>} -status nmlReleasing a blocked pool

raidcom add rcu -cu_free <serial#> <id> <pid> -mcu_port <port#> -rcu_port <port#>RCU registration

raidcom add rcu_path -cu_free <serial#> <id> <pid> -mcu_port <port#> -rcu_port<port#>

RCU logical path addition

raidcom delete rcu -cu_free <serial#> <id> <pid>RCU deletion

raidcom delete rcu_path -cu_free <serial#> <id> <pid> -mcu_port <port#> -rcu_port<port#>

RCU logical path deletion

raidcom add journal -journal_id <journal ID#> {-ldev_id <ldev#> …[-cnt <count>]| -grp_opt <group option> -device_grp_name <device group name> [<devicename>]}

Creating journal/ Registering journal volumein the journal

raidcom delete journal -journal_id <journal ID#> [-ldev_id <ldev#> | -grp_opt <groupoption> -device_grp_name <device group name> [<device name>]]

Deleting journal/ Deleting journal volumefrom the journal

raidcom check_ext_storage path -path_grp <path group#> -port <port#>-external_wwn <wwn strings>

Restoration of path for the external path

raidcom add path -path_grp <path group#> -port <port#> -external_wwn <wwnstrings>

Setting the external path

raidcom add external_grp -path_grp <path group#> -external_grp_id <gno-sgno>-port <port#> -external_wwn <wwn strings> -lun_id <lun#> [-emulation <emulationtype>]

Mapping the external volume

raidcom delete path -path_grp <path group#> -port <port#> -external_wwn <wwnstrings>

Deleting the external path

raidcom delete external_grp -external_grp_id <gno-sgno>Releasing the mapping of external volume

raidcom disconnect path -path_grp <path group#> -port <port#> -external_wwn<wwn strings>

Stopping the use of paths to the externalvolume

raidcom add parity_grp {-parity_grp_id <gno-sgno> | -concatenated_parity_grp_id<gno-sgno>... } -drive_location <drive location>... -raid_type <raid type>

Creating a parity group

[-encryption {enable|disable}] [-copy_back {enable|disable}][-accelerated_compression {enable| disable}] [-clpr <clpr#>]


Table 27 Asynchronous commands of the configuration setting command (continued)


raidcom delete parity_grp -parity_grp_id <gno-sgno>Deleting a parity group

raidcom modify drive -drive_location <drive location> -spare {enable |disable}Setting a spare drive or cancelling thesetting

Help on configuration setting commandsTo see the configuration setting command help, execute any command using the -h option, forexample, raidcom - h.raidcom -h

LDEV nickname functionAs a function of configuration setting command, a nickname can be set for each LDEV.The details of the definition for the LDEV nickname function are shown below.The maximum length of a name is 32 characters. For one LDEV, one nickname can be defined.A nickname can be defined as follows:

raidcom modify ldev -ldev_id <ldev#> -ldev_name <ldev naming>

Available provisioning operationsThe following provisioning operations can be performed using RAID Manager.

Corresponding commandDescriptionOperation type

raidcom -login <user_name> <password>Log in.Login and logout

raidcom -logoutLog out.

raidcom lock resource -resource_name <resource group name> [-time <time(sec)>]

Lock resource.Resource

raidcom unlock resource -resource_name <resource group name>

Unlock resource.

raidcom get resourceDisplay resource groupinformation.

raidcom add resource -resource_name <resource group name>[-resource_id <resource group_id > |-ldev_id <ldev#> | -port

Add resource group.

<port#> | -port <port#> <host group name> | -parity_grp_id<gno-sgno> | -external_grp_id <gno-sgno>]

raidcom delete resource -resource_name <resource group name>[-ldev_id <ldev#> | -port <port#> | -port <port#> <host groupname> | -parity_grp_id <gno-sgno> | -external_grp_id <gno-sgno>]

Delete resource group.

raidcom add host_grp -port <port#> -host_grp_name <host groupname>

Create host group.Host(see the ProvisioningGuide for the storagesystem) raidcom modify host_grp -port <port#> [<host group name>]

-host_mode < host mode> [-host_mode_opt <host mode option>… ]

Set host mode.

raidcom add hba_wwn -port <port#> [<host group name>]-hba_wwn <WWN strings>

Register a host to host group.

raidcom delete host_grp -port <port#> [<host group name>]Delete host group.

Available provisioning operations 123


raidcom get host_grp -port <port#> [<host group name>]Display host group information.

raidcom modify port -port <port#> {[-port_speed <value>][-loop_id<value>] [-topology <topology>] [-security_switch < y/n>]}

Set port.Port(see the ProvisioningGuide for the storagesystem) raidcom modify port -port <port#> -port_attribute <port attribute>Set port attribute.

raidcom get port [-port <port#>]Display port information.

raidcom add ldev {-parity_grp_id <gno-sgno> | - external_grp_id<gno-sgno> | -pool {<pool ID#> | <pool naming> | snap}} -ldev_id

Create LDEV.Internal volume(see the ProvisioningGuide for the storagesystem)

<ldev#> {-capacity <size> | -offset_capacity <size> | -cylinder<size>} [-emulation <emulation type>][-location <lba>][-mp_blade_id <mp#>]

raidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt<group option> -device_grp_name <device group name> [<devicename>]} [-key <keyword>]

Display LDEV information.

raidcom get parity_grp [-parity_grp_id <gno-sgno>]Display parity groupinformation.

raidcom add parity_grp {-parity_grp_id <gnosgno> |-concatenated_parity_grp_id <gnosgno>... } -drive_location <drive

Create a parity group.

location>... -raid_type <raid type> [-encryption {enable| disable}][-copy_back {enable|disable}] [- accelerated_compression {enable|disable}] [- clpr <clpr#>]

raidcom delete parity_grp -parity_grp_id <gnosgno>Delete a parity group.

raidcom add ssid -rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid>Define SSID.raidcom delete ssid -rcu <serial#> <mcu#> <rcu#> -ssid <ssid>

raidcom get drive [-parity_grp_id <gno-sgno> | -usage <usage>]Display drive information.

raidcom modify drive -drive_location <drive location> -spare{enable | disable}

Set a spare drive, or cancel thesetting.

raidcom add thp_pool {{-pool_id <pool ID#> [-pool_name <poolnaming>] | -pool_name <pool naming> [-pool_id <pool ID#>]} |

Create pool for THP or THPMF.

Virtual volume(THP, THP MF, Smart,Smart MF, RTST, RTSTMF, or SS)

-pool_id <pool ID#> -pool_name <pool naming>}} {-ldev_id<ldev#> …[-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<devicename>]}[-user_threshold <threshold_1> [<threshold_2>] ](see the Provisioning

Guide for the storagesystem) raidcom add snap_pool {{-pool_id <pool ID#> [-pool_name <pool

naming>] | -pool_name <pool naming> [-pool_id <pool ID#>]} |Create pool for SS.

-pool_id <pool ID#> -pool_name <pool naming>}} {-ldev_id<ldev#> …[-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<devicename>]}[-user_threshold <%> ]

raidcom get pool [-key <keyword>]Display pool information forTHP, THP MF, Smart, SmartMF, RTST, RTST MF, or SS.

raidcom delete pool -pool {<pool ID#> | <pool naming>}Delete pool for THP, THP MF,Smart, Smart MF, RTST, RTSTMF, or SS.

raidcom modify pool -pool {<pool ID#> | <pool naming>}-user_threshold <threshold_1> [<threshold_2>]

Change the threshold value ofa pool for THP, THP MF, Smart,Smart MF, RTST, RTST MF, orSS.



raidcom modify pool -pool {<pool ID#> | <pool naming>} -statusnml

Restore a pool for THP, THPMF, Smart, Smart MF, RTST,RTST MF, or SS.

raidcom modify pool -pool {<pool ID#> | <pool naming>}-subscription <%>

Set the maximum rate ofsubscription of a pool for THP,THP MF, Smart, Smart MF,RTST, or RTST MF.

raidcom modify pool -pool {<pool ID#> | <pool naming>}-pool_attribute smart_manual

Change the pool for THP to thepool for Smart.

raidcom modify pool -pool {<pool ID#> | <pool naming>}-pool_attribute thp

Change the pool for Smart tothe pool for THP.

raidcom modify pool -pool {<pool ID#> | <pool naming>} -tier <Tiernumber><ratio>

Set the newly allocation freespace percentage of the poolfor Smart, Smart MF, RTST, orRTST MF.

raidcom add ldev -pool {<pool ID#> | <pool naming> | snap}-ldev_id <ldev#> -capacity <size> [-emulation <emulation type>][-location <lba>][-mp_blade_id <mp#>]

Create virtual volume for THP,THP MF, Smart, Smart MF,RTST, RTST MF, or SS.

raidcom extend ldev{-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}-capacity <size>

Extend capacity of virtualvolume for THP, THP MF,Smart, Smart MF, RTST, orRTST MF.

raidcom modify ldev -ldev_id <ldev#> -status {enable_reallocation| disable_reallocation}

Set enabled or disabled ofvirtual volume tier reallocationfor Smart, Smart MF, RTST, orRTST MF.

raidcom modify ldev -ldev_id <ldev#> -status discard_zero_pageDiscard a page of virtual volumefor THP, THP MF, Smart, SmartMF, RTST, or RTST MF.

raidcom get thp_pool [ -key <keyword>]Display the information of a poolfor THP, THP MF, Smart, SmartMF, RTST, or RTST MF.

raidcom get snap_poolDisplay the information of a poolfor SS.

raidcom add thp_pool {{-pool_id <pool ID#> [-pool_name <poolnaming>] | -pool_name <pool naming> [-pool_id <pool ID#>]} |

Extend the capacity of a poolfor THP, THP MF, Smart, SmartMF, RTST, or RTST MF. -pool_id <pool ID#> -pool_name <pool naming>}} {-ldev_id

<ldev#> … [-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<devicename>]}[-user_threshold <threshold_1> [<threshold_2>] ]

raidcom add snap_pool {{-pool_id <pool ID#> [-pool_name <poolnaming>] | -pool_name <pool naming> [-pool_id <pool ID#>]} |

Extend the capacity of a poolfor SS.

-pool_id <pool ID#> -pool_name <pool naming>}} {-ldev_id<ldev#> …[-cnt<count>] | -grp_opt <group option>-device_grp_name <device group name> [<devicename>]}[-user_threshold <%> ]

raidcom monitor pool -pool {<pool ID#> | <pool naming>}-operation <type>

Start or stop the performancemonitor for Smart, Smart MF,RTST, or RTST MF.

raidcom reallocate pool -pool {<pool ID#> | <pool naming>}-operation <type>

Start or stop the tier reallocationof a pool for Smart, Smart MF,RTST, or RTST MF.



raidcom add lun -port <port#> [<host group name>] {-ldev_id<ldev#> [-lun_id<lun#>] | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}

Set LU path.LU path(see the ProvisioningGuide for the storagesystem) raidcom delete lun -port <port#> [<host group name>] {-lun_id

<lun#> | -ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}

Delete LU path.

raidcom get lun -port <port#> [<host group name>]Display LU path information.

raidcom discover external_storage -port <port#>Search external storage.External volume(Ext Stor) raidcom discover lun -port <port#> -external_wwn <wwn strings>Search external volume.(see the External StorageUser Guide for the storagesystem)

raidcom add external_grp -path_grp <path group#>-external_grp_id <gno-sgno> -port <port#> -external_wwn <wwnstrings> -lun_id <lun#> [-emulation <emulation type>]

Map external volume.

raidcom disconnect external_grp {-external_grp_id <gno-sgno>| -ldev_id <ldev#>}

Disconnect the connection forexternal volume.

raidcom check_ext_storage external_grp {-external_grp_id<gno-sgno> | -ldev_id <ldev#>}

Check the connection forexternal volume and restore it.

raidcom delete external_grp -external_grp_id <gno-sgno>[-forcible]

Unmap external volume.

raidcom get external_grp [-external_grp_id <gno-sgno>]Display mapped externalvolume information.

raidcom add ldev - external_grp_id <gno-sgno> -ldev_id <ldev#>-capacity <size> [-emulation <emulation type>][-location <lba>][-mp_blade_id <mp#>]

Create LDEV in externalvolume.

raidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt<group option> -device_grp_name <device group name> [<devicename>]} [-key <keyword>]

Display LDEV informationcreated in external volume.

raidcom modify external_grp -external_grp_id <gno-sgno>-cache_mode < y|n >

Change cache mode of externalvolume.

raidcom modify external_grp -external_grp_id <gno-sgno>-cache_inflow < y|n >

Control cache write of externalvolume.

raidcom modify external_grp -external_grp_id <gno-sgno>-mp_blade_id <mp#>

Modify ownership MP Blade ofexternal volume.

raidcom add path -path_grp <path group#> -port <port#>-external_wwn <wwn strings>

Add external path.

raidcom delete path -path_grp <path group#> -port <port#>-external_wwn <wwn strings>

Delete external path.

raidcom get path [-path_grp <path group#>]Display external pathinformation.

raidcom disconnect path -path_grp <path group#> -port <port#>-external_wwn <wwn strings>

Stop the usage of external path.

raidcom check_ext_storage path -path_grp <path group#> -port<port#> -external_wwn <wwn strings>

Restore the external path.

raidcom add ssid -rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid>Define SSID.raidcom delete ssid -rcu <serial#> <mcu#> <rcu#> -ssid <ssid>

raidcom add hba_wwn -port <port#> [<host group name>]-hba_wwn <WWN strings>

Add WWN of host path adapter.HostMaintenance



raidcom delete hba_wwn -port <port#> [<host group name>]-hba_wwn <WWN strings>

Delete WWN of host pathadapter.

raidcom set hba_wwn -port <port#> [<host group name>]-hba_wwn <WWN strings> -wwn_nickname <WWN Nickname>

Set nickname for WWN of hostpath adapter.

raidcom reset hba_wwn -port <port#> [<host group name>]-hba_wwn <WWN strings>

Delete nickname from WWN ofhost path adapter.

raidcom get host_grp -port <port#> [<host group name>]Display registered WWNinformation of host pathadapter.

raidcom modify ldev -ldev_id <ldev#> -status discard_zero_pageBlockade or restore LDEV.LDEV

raidcom modify ldev -ldev_id <ldev#> -ldev_name <ldev naming>Create nickname for LDEV.

raidcom modify ldev -ldev_id <ldev#> -mp_blade_id <mp#>Modify allocated MP Blade toLDEV.

raidcom initialize ldev {-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name <device group name> [<device name>]}-operation <type>

Format LDEV.

raidcom add device_grp -device_grp_name <ldev group name><device name> -ldev_id <ldev#>… [-cnt <count>]

Create device group.Device group

raidcom delete device_grp -device_grp_name <device groupname> -ldev_id <ldev#>… [-cnt <count>]

Delete LDEV from devicegroup.

raidcom get device_grp [-device_grp_name <device group name>]Display device groupinformation.

raidcom add copy_grp -copy_grp_name <copy group name><device group name> [device group name] [-mirror_id <mu#>-journal_id <journal ID#>]

Create copy group.Copy group

raidcom delete copy_grp -copy_grp_name <copy group name>Delete copy group.

raidcom get copy_grpDisplay copy group information.

raidcom get clprView CLPR configuration.CLPR

raidcom modify clprModify CLPR (migrate LDEV,parity group, external group).

raidcom add rcu -cu_free <serial#> <id> <pid> -mcu_port <port#>-rcu_port <port#>

Register RCU.RCU(see themanuals for

Remotecopyenvironment

raidcom delete rcu -cu_free <serial#> <id> <pid>Delete RCU.Cnt Ac-S,raidcom modify rcu -cu_free <serial#> <id> <pid> -rcu_option<mpth> <rto> <rtt>

Set RCU attribute.Cnt Ac-S MF,Cnt Ac-J, andCnt Ac-J MF)

raidcom get rcu [-cu_free <serial#> <id> <pid>]Display RCU information.

raidcom add rcu_path -cu_free <serial#> <id> <pid> -mcu_port<port#> -rcu_port <port#>

Add RCU logical path.RCU path(see themanuals for raidcom delete rcu_path -cu_free <serial#> <id> <pid> -mcu_port

<port#> -rcu_port <port#>Delete RCU logical path.Cnt Ac-S,

Cnt Ac-S MF,Cnt Ac-J, andCnt Ac-J MF)

raidcom add journal -journal_id <journal ID#> {-ldev_id <ldev#>…[-cnt <count>] | -grp_opt <group option> -device_grp_name

Register journal volume toJournal.

Journal(see themanuals for <device group name> [<device name>]} [-mp_blade_id <mp#> |

-timer_type <timer type> ]



raidcom delete journal -journal_id <journal ID#> [-ldev_id <ldev#>| -grp_opt <group option> -device_grp_name <device groupname> [<device name>]]

Delete journal volume fromJournal/ Delete journal.

Cnt Ac-J andCnt Ac-J MF)

raidcom modify journal -journal_id <journal ID#>{[-data_overflow_watch<time>][-cache_mode <y/n>][-timer_type

Change the Cnt Ac-J option tobe used at Journal.

<type>]} | -path_blocked_watch <time> [-mirror_id <mu#>] |-mp_blade_id <mp#>

raidcom get journal [ -key <keyword>]raidcom get journal[t]Display journal information.

Provisioning operations that can be performed on device groupsYou can use RAID Manager to perform provisioning operations on device groups. When youspecify a device group, you can perform operations on all LDEVs in the device group at the sametime. For details about device groups, see “LDEV grouping function” (page 82).The following table lists the provisioning operations that can be executed by specifying a devicegroup.

Table 28 Performing provisioning operations by specifying a device group

CommandContents of operation

raidcom add journalRegister a journal group to a journal

raidcom delete journalDelete a journal group from a journal/delete a journal

raidcom delete ldevDelete an LDEV/V-VOL

raidcom extend ldevExtend the capacity of V-VOL for Thin Provisioning, Thin Provisioning MF,Smart Tiers, Real Time Smart Tier, Smart Tiers MF, or Real Time Smart Tierfor Mainframe

raidcom get ldevDisplay the LDEV information

raidcom initialize ldevFormat an LDEV

raidcom add lunCreate an LU path

raidcom delete lunDelete an LU path

raidcom add snap_poolCreate a pool for Snapshot

raidcom add snap_poolExtend the capacity of a pool for Snapshot

raidcom add thp_poolCreate a pool for Thin Provisioning, Thin Provisioning MF

raidcom add thp_poolExtend the capacity of a pool for Thin Provisioning, Thin Provisioning MF,Smart Tiers, Real Time Smart Tier, Smart Tiers MF, or Real Time Smart Tierfor Mainframe

raidcom add resourceCreate a resource group

raidcom delete resourceDelete a resource group

Operation methodTo execute a command on a device group, specify the name of the device group (max: 32characters) and the device name in the device group (max: 32 characters).The following shows an example of mapping the LDEVs in a device group to LUNs. When youspecify both the device group name and the device name, the operation is executed for the LDEVthat matches the specified device name in the specified device group. If you do not specify thedevice name, the operation is executed for all LDEVs in the device group.


Information of the device group

C:\HORCM\etc>raidcom get device_grp -device_grp_name grp1

LDEV_GROUP LDEV_NAME LDEV# Serial#

grp1 data0 17000 64577

grp1 data0 17001 64577

grp1 data1 17002 64577

grp1 data1 17003 64577

ResultThe following shows the result of executing the raidcom add lun command and specifyingdevice group name: grp1 and device name: data0.

C:\HORCM\etc>raidcom add lun -port CL8-A -grp_opt ldev -device_grp_namegrp1 data0

GROUP = grp1, DEVICE = data0, UnitID = 0, LDEV = 17000(0x4268)[1], PORT =CL8-A, LUN = none:

raidcom: LUN 0(0x0) will be used for adding.

done

GROUP = grp1, DEVICE = data0, UnitID = 0, LDEV = 17001(0x4269)[1], PORT =CL8-A, LUN = none:


done

C:\HORCM\etc>raidcom get lun -port CL8-A-0

PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITs

CL8-A 0 LINUX/IRIX 0 1 17000 - 64577

CL8-A 0 LINUX/IRIX 1 1 17001 - 64577

The following shows the result of executing the raidcom add lun command and specifyingdevice group name: grp1 (omitting device name).

C:\HORCM\etc>>raidcom add lun -port CL8-A -grp_opt ldev -device_grp_name grp1

GROUP = grp1 , DEVICE = data0 , UnitID = 0 , LDEV = 17000(0x4268)[1] , PORT= CL8-A , LUN = none :


done

GROUP = grp1 , DEVICE = data0 , UnitID = 0 , LDEV = 17001(0x4269)[1] , PORT= CL8-A , LUN = none :


done

GROUP = grp1 , DEVICE = data1 , UnitID = 0 , LDEV = 17002(0x426A)[1] , PORT= CL8-A , LUN = none :


done

GROUP = grp1 , DEVICE = data1 , UnitID = 0 , LDEV = 17003(0x426B)[1] , PORT= CL8-A , LUN = none :


done

C:\HORCM\etc>>raidcom get lun -port CL8-A-0

PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITs

CL8-A 0 LINUX/IRIX 0 1 17000 - 64577

CL8-A 0 LINUX/IRIX 1 1 17001 - 64577

Provisioning operations that can be performed on device groups 129

CL8-A 0 LINUX/IRIX 2 1 17002 - 64577

CL8-A 0 LINUX/IRIX 3 1 17003 - 64577

The following shows an example of specifying device groups and creating journal.

C:\HORCM\etc>raidcom add device_grp -device_grp_name dg_jnl1 data1 -ldev_id 512 513 514 515C:\HORCM\etc>raidcom get device_grpLDEV_GROUP Serial#dg_jnl1 64539

C:\HORCM\etc>raidcom get device_grp -device_grp_name dg_jnl1LDEV_GROUP LDEV_NAME LDEV# Serial#dg_jnl1 data1 512 64539dg_jnl1 data1 513 64539dg_jnl1 data1 514 64539dg_jnl1 data1 515 64539

C:\HORCM\etc>raidcom add journal -journal_id 2 -grp_opt ldev -device_grp_name dg_jnl1GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,PORT = none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] , PORT= none , LUN = none :done

Workflow for performing provisioning operationsWhen you execute provisioning operations, perform the operations in the following order to login and lock resources first and then unlock resources and view resource group information afterperforming operations.

CommandDescriptionStep

raidcom -login <user_name> <password>Log in.1

raidcom lock resource -resource_name<resource group name> [-time<time(sec)>]

Lock the resource group.2

--Perform the desired provisioning operations.3

raidcom unlock resource -resource_name<resource group name>

Unlock the resource group.4

raidcom get resourceDisplay the resource group information toconfirm the operations and lock information.

5

raidcom -logoutLog out.6


Resource group operationsCreating resource groups

To create resource groups, perform the following provisioning operations.

CommandDescriptionOperationStep

raidcom add resource-resource_name <resourcegroup name>

Creates resource groups.Creating resourcegroups

1

raidcom add resource-resource_name <resource

Specifies resources that areallocated to meta_resource

Allocationgresources toresource groups

2

group name> [-ldev_id<ldev#> | -port <port#> |

(resource group), and allocatesresources to created resourcegroups. -port <port#> <host group

name> | -parity_grp_id<gno-sgno> |-external_grp_id<gno-sgno>]

raidcom get resourceDisplays a resource groupinformation, and confirms executionresults of commands.

Displaying aresource groupinformation

3

Deleting resource groupsTo delete resource groups, perform the following provisioning operations.


raidcom delete resource-resource_name <resource

Deletes resources that are allocatedto resource groups. In other words,

Deleting resourcesthat are allocated toresource groups.

1


this operation allocates resources toresource group: meta_resource.

-port <port#> <host groupname> | -parity_grp_id<gno-sgno> |-external_grp_id<gno-sgno>]

raidcom get resourceConfirms that resources are notallocated to resource groups that you

Confirming resourcedeletions

2

want to delete. At that time, allocationof resources to the resource group:meta_resource must be finished.

raidcom delete resource-resource_name <resourcegroup name>

Deletes resource groups.Deleting resourcegroups

3

raidcom get resourceDisplays resource group informationand confirms results of commandexecutions.

Displaying resourcegroup information

4

Allocating resources that are allocated to resource groups to other resource groupsWhen you want to allocate resources that are already allocated to resource groups to otherresource groups, resources must be once allocated to resource group: meta_resource. Afterthat, allocate resources to the resource groups that you want to allocate. LDEVs that configure

Resource group operations 131

journals, pools, LUSEs or device groups must be allocated to resource groups particularly. Thefollowing shows the necessary provisioning operations.


raidcom delete resource-resource_name <resource

Deletes resources that are allocatedto resource groups. In other words,

Deleting resourcesthat are allocated toresource groups

1


this operation allocates resources toresource group: meta_resource.


raidcom get resourceConfirms that resources are notallocated to resource groups that you

Confirming resourcedeletions

2

want to delete. At that time, allocationof resources to the resource group:meta_resource must be finished.

raidcom add resource-resource_name <resource

Specifies resources that are allocatedto meta_resource (resource group),

Allocating resourcesto resource groups

3

group name> [-ldev_idand allocates resources to resourcegroups. <ldev#> | -port <port#> |


raidcom get resourceDisplays resource group informationand confirms results of commandexecutions.

Displaying resourcegroup information

4

LDEVs that are allocated to journals or pools must be migrated by users. We recommend thatyou register LDEVs that are allocated to journals or pools as device groups, and then operateafter specifying them by the device groups.

Execution exampleThe 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.

C:\HORCM\etc>raidcom add device_grp -device_grp_name dg_jnl1 data1 -ldev_id 512 513 514 515C:\HORCM\etc>raidcom get device_grpLDEV_GROUP Serial#dg_jnl1 64539

C:\HORCM\etc>raidcom get device_grp -device_grp_name dg_jnl1LDEV_GROUP LDEV_NAME LDEV# Serial#dg_jnl1 data1 512 64539dg_jnl1 data1 513 64539dg_jnl1 data1 514 64539dg_jnl1 data1 515 64539

C:\HORCM\etc>raidcom add resource -resource_name rsg002 -grp_opt ldev -device_grp_name dg_jnl1GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,PORT = none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] , PORT


= none , LUN = none :done

C:\HORCM\etc>raidcom delete resource -resource_name rsg002 -grp_opt ldev -device_grp_name dg_jnl1GROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 512(0x0200)[1] ,PORT = none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 513(0x0201)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 514(0x0202)[1] , PORT= none , LUN = none :doneGROUP = dg_jnl1 , DEVICE = data1 , UnitID = 0 , LDEV = 515(0x0203)[1] , PORT= none , LUN = none :done

Internal volume operationsCreating internal volumes (open-systems)

To create LDEVs of internal open-systems volumes and make the LDEVs available to the host,perform the following provisioning operations.


raidcom modify port -port<port#> -security_switch y

Enable LUN security of the port. Modifysettings such as port topology and datatransfer speed as needed.

Setting port1

raidcom add host_grp -port<port#> -host_grp_name<host group name>

Specify port and create host group.Creating host group2

raidcom modify host_grp-port <port#>

Specify port and set host mode for hostgroup.

Setting host mode3

[<host group name>]-host_mode < host mode>[-host_mode_opt<host mode option> … ]

raidcom get host_grp-port <port#> [<host groupname>]

Display host group information andconfirm result of executing command.

Displaying hostgroup information

4

raidcom add hba_wwn-port <port#> [<host group

Register host to host group of the port.Adding host to hostgroup

5

name>] -hba_wwn<WWN strings>

raidcom get hba_wwn -port<port#> [<host groupname>]

Display WWN of connection hostregistered to the host group and confirmthe result of executing the command.

Displaying WWNinformation

6

raidcom add ldev-parity_grp_id <gno-sgno>

Specify a parity group and create LDEV.Creating LDEV7

-ldev_id <ldev#>-capacity <size>[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]

raidcom initialize ldev-ldev_id <ldev#>-operation <type>

Format created LDEV.Formatting LDEV8

raidcom modify ldev-ldev_id <ldev#>-ldev_name <ldev naming>

Create nickname for created LDEV.This operation is arbitrary.

Creating LDEVnickname (arbitrary)

9

Internal volume operations 133


raidcom modify ldev-ldev_id <ldev#>-mp_blade_id <mp#>

Set MP blade of created LDEV.Setting MP blade ofLDEV

10

raidcom get ldev -ldev_id<ldev#> … [-cnt <count>][-key <keyword>]

Display information of created LDEV andconfirm the result of executing thecommand.

Displaying LDEVinformation

11

raidcom add lun -port<port#> [<host group

Specify port, map LDEV to LUN andcreate an LU path.

Creating LU path12

name>] -ldev_id <ldev#>[-lun_id<lun#>]

raidcom get lun-port <port#>[<host group name>]

Display LU path information and confirmthe result of executing the command.

Displaying LU pathinformation

13

Script examples (open systems)The following shows script examples of virtual volume (Thin Provisioning) operation.


Figure 33 Script examples of virtual volume operation (Thin Provisioning) (1/3)



Creating internal volumes (Mainframe volume)To create LDEVs of internal volumes (Mainframe volume) and make the LDEVs available to thehost, perform the following provisioning operations.


raidcom modify ldev-ldev_id <ldev#> -ssid<value>

Configures the SSID unless it isconfigured. Set (register) the SSIDby specifying undefined LDEV

SSID settings(arbitrarily)

1

numbers in the area in whichSSIDs are not defined.

raidcom add ldev -parity_grp_id<gno-sgno> -ldev_id <ldev#>

Creates LDEVs by specifying paritygroups.

Creating LDEVs2

{-capacity <size> |-offset_capacity <size> |-cylinder <size>} [-emulation<emulation type>][-location<lba>][-mp_blade_id <mp#>]


Formats created LDEVs.Formatting LDEVs3

raidcom modify ldev -ldev_id<ldev#> -ldev_name <ldevnaming>

Creates LDEV nicknames. Thisoperation is optional.

Creating LDEVnicknames(arbitrarily)

4

raidcom modify ldev -ldev_id<ldev#> -mp_blade_id <mp#>

Configures MP blades of createdLDEVs.

Configuring MPblades of LDEVs

5


Displays an information of createdLDEV, and confirms an executionresult of the command.

Displaying a LDEVinformation

6

Script examplesThe following shows the script examples of internal volume (mainframe volume) operations.


Figure 36 Script examples of internal volume (Mainframe volume) operation

Script examplesThe following shows script examples for internal open-system volume operations.


Figure 37 Script examples of internal open-system volume operation (1/2)


Figure 38 Script examples of internal open-system volume operation (2/2)

Virtual volume (Thin Provisioning) operationsCreating virtual volumes (Thin Provisioning)

Use the following provisioning operations to create LDEVs of virtual volumes (Thin Provisioning)and make the LDEVs available to the host.

Executed commandDescriptionOperationoverviewStep


Enable LUN security for the port. Modifysettings such as port topology and datatransfer speed as needed.

Setting port1



raidcom modify host_grp-port <port#> [<host group


Setting host mode3

name>] -host_mode<host mode>[-host_mode_opt<host mode option> … ]






4



5


raidcom get hba_wwn-port <port#> [<host groupname>]



6



-ldev_id <ldev#>{-capacity <size> |-offset_capacity <size> |-cylinder <size>}[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]

raidcom initialize ldev-ldev_id<ldev#> -operation <type>


raidcom modify ldev-ldev_id

Create nickname for LDEV.This operation is arbitrary.


9

<ldev#> -ldev_name<ldev naming>



10




11

raidcom add thp_pool{{-pool_id <pool ID#>

Create pool (for Thin Provisioning).Creating pool (forThin Provisioning)

12

[-pool_name <poolnaming>] | -pool_name<pool naming> [-pool_id<pool ID#>]} | -pool_id<pool ID#> -pool_name<pool naming>}} -ldev_id<ldev#> …[-cnt <count>][-user_threshold<threshold_1>[<threshold_2>]]

raidcom add ldev -pool{<pool ID#> |

Specify pool and create an LDEV(V-VOL).Creating LDEV(V-VOL)

13

<pool naming> | snap}-ldev_id <ldev#>{-capacity <size> |-offset_capacity <size>| -cylinder <size>}[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]


Create nickname for the created LDEV.This operation is arbitrary.

Creating LDEV(V-VOL) nickname(arbitrary)

14

Virtual volume (Thin Provisioning) operations 141



Set MP blade of created LDEV (V-VOL).Setting MP blade ofLDEV (V-VOL)

15


Display information of created LDEV(V-VOL) and confirm the result ofexecuting the command.

Displaying LDEVinformation (V-VOL)

16

raidcom add lun -port<port#> [host group name]


Creating LU path17

-ldev_id <ldev#>[-lun_id <lun#>]

raidcom get lun -port<port#> [<host groupname>]



18

Script examplesThe following shows script examples of virtual volume (Thin Provisioning) operation.



Virtual volume (Thin Provisioning) operations 143


Virtual volume (Thin Provisioning MF) operationsCreating virtual volumes (Thin Provisioning MF)

To create LDEVs of virtual volumes (Thin Provisioning MF) and make the LDEVs available tothe host, perform the following Provisioning operations.


raidcom modify ldev-ldev_id<ldev#>-ssid<value>

Configures the SSID unless it isconfigured. Set (register) the SSID byspecifying undefined LDEV numbers inthe area in which SSIDs are not defined.

SSID settings(arbitrarily)

1


Creates LDEVs by specifying paritygroups. Specifies only 3390-V for theemulation type.

Creating LDEVs2

-ldev_id <ldev#>{-capacity <size> |-offset_capacity <size> |-cylinder <size>}-emulation 3390-V-location <lba>][-mp_blade_id <mp#>]


Formats created LDEVs.Formatting LDEVs3


Creates LDEV nicknames. This operationis optional.

Creating LDEVnicknames(arbitrarily)

4


Configures MP blades of created LDEVs.Configuring MPblades of LDEVs

5


Displays an information of created LDEV,and confirms an execution result of thecommand.

Displaying a LDEVinformation

6

raidcom add thp_pool{{-pool_id <pool ID#>

Creates the pool for the Thin Provisioningfor mainframe.

Creating the pool(for the Thin

7

[-pool_name <pool

Virtual volume (Thin Provisioning MF) operations 145


naming>] | -pool_name<pool naming> [-pool_id

Provisioning formainframe)

<pool ID#>]} | -pool_id<pool ID#> -pool_name<pool naming>} {-ldev_id<ldev#> …[-cnt <count>] |-grp_opt <group option>-device_grp_name <devicegroup name> [<devicename>]}[ -user_threshold<threshold_1>[<threshold_2>] ]

raidcom add ldev -pool{<pool ID#> | <pool

Specifies the pool and creates LDEV(V-VOL).

Creating LDEV(V-VOL)

8

naming> | snap} -ldev_id<ldev#> {-capacity <size>| -offset_capacity <size>| -cylinder <size>}[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]


Creates LDEV (V-VOL) nicknames. Thisoperation is optional.

Creating LDEV(V-VOL) nicknames(arbitrarily)

9

raidcom modify ldev-ldev_id

Configures MP blades of created LDEVs(V-VOL).

Configuring MPblades of LDEVs(V-VOL)

10

<ldev#> -mp_blade_id<mp#>

raidcom get ldev -ldev_id<ldev#> [-cnt <count>][-key <keyword>]

Displays an information of created LDEV(V-VOL), and confirms an execution resultof the command.

Displaying a LDEV(V-VOL) information

11

Script examplesThe following shows the script examples of virtual volume (Thin Provisioning for mainframe)operation.


Figure 42 Script examples of virtual volume operation (Thin Provisioning for Mainframe)(1/2)

Figure 43 Script examples of virtual volume operation (Thin Provisioning for Mainframe)(2/2)

Virtual volume (Smart Tiers) operationsOperational flow

When using the V-VOL (Smart Tiers), tiers of pools must be created after creating pools, andthen the performance of pools must be monitored before the operation. If the performance ofpools are insufficient, extend the capacity of pool volumes (addition of pool volumes) and of theV-VOL.The following diagram shows the flow of work to use a virtual volume (Smart Tiers) when operatingwith GUI (Remote Web Console) or CLI (RAID Manager):

Virtual volume (Smart Tiers) operations 147

Note *1: The Smart Pool is disabled when a pool is creating at RAID Manager. And multiplemedia cannot be registered as a pool volume when a pool is created. Execute tiering afterchanging the Smart Pool to the enabled status.


Note *2: When the Smart Pool is enabled, the tiering control is set to "Manual" automatically. Tochange the setting to "Auto", it is required to execute from Remote Web Console.

CAUTION: The operations explained here are executable by the storage administrator only.

NOTE: Before creating a pool, it is required to create a virtual volume management area onthe cache memory. The virtual volume management area is created automatically when cachememory is added. For information about adding cache memory, please contact HPE technicalsupport.

Creating virtual volumes (Smart Tiers)Use the following operations to create LDEVs of virtual volumes (Smart Tiers) and making theLDEVs available to the host.


raidcom modify port -port <port#>-security_switch y

Make enabled the LUN security of port.Modify setting such as port topology anddata transfer speed as needed.

Setting port1

raidcom add host_grp -port <port#>-host_grp_name <host group name>


raidcom modify host_grp -port <port#>[<host group name>] -host_mode <host


Setting host mode3

mode> [-host_mode_opt <host modeoption> … ]

raidcom get host_grp -port <port#> [<hostgroup name>]



4

raidcom add hba_wwn -port <port#>[<host group name>] -hba_wwn <WWNstrings>


5

raidcom get hba_wwn {-port <port#>[<host group name>]}



6

raidcom add ldev {-parity_grp_id<gno-sgno> -ldev_id <ldev#> {-capacity


<size> | -offset_capacity <size> | -cylinder<size>} [-emulation <emulationtype>][-location <lba>] [-mp_blade_id<mp#>]

raidcom initialize ldev -ldev_id <ldev#>-operation <type>


raidcom modify ldev -ldev_id <ldev#>-ldev_name <ldev naming>

Create LDEV nickname.This operation is arbitrary.


9

raidcom modify ldev -ldev_id <ldev#>-mp_blade_id <mp#>


10

raidcom get ldev -ldev_id <ldev#> … [-cnt<count>] [-key <keyword>]



11

raidcom add thp_pool {{-pool_id <poolID#> [-pool_name <pool naming>] |

Create pool (for Thin Provisioning).Creating pool (forThin Provisioning)

12

-pool_name <pool naming> [-pool_id <poolID#>]} | -pool_id <pool ID#> -pool_name



<pool naming>}} -ldev_id <ldev#> …[-cntcount>] [-user_threshold <%> ]

raidcom modify pool -pool {<pool ID#> |<pool naming>} -pool_attributesmart_manual

Modify pool for Thin Provisioning to poolfor Smart Tiers.

Setting pool option13

raidcom add thp_pool {{-pool_id <poolID#> [-pool_name <pool naming>] |

Add a pool volume of different media to apool for Smart Tiers.

Adding differentmedia to poolvolume

14

-pool_name <pool naming> [-pool_id <poolID#>]} | -pool_id <pool ID#> -pool_name<pool naming>} -ldev_id <ldev#> …[-cnt<count>] [ -user_threshold <threshold_1>[<threshold_2>] ]

raidcom add ldev -pool {<pool ID#> | <poolnaming> | snap} -ldev_id <ldev#> -capacity

Specify pool and create LDEV (V-VOL).Creating LDEV(V-VOL)

15

<size> [-emulation <emulationtype>][-location <lba>] [-mp_blade_id<mp#>]

raidcom modify ldev -ldev_id <ldev#>-ldev_name <ldev naming>

Create nickname for created LDEV(V-VOL).

Creating LDEV(V-VOL) nickname(arbitrary)

16

This operation is arbitrary.

raidcom modify ldev -ldev_id <ldev#>-mp_blade_id <mp#>

Set MP blade of created LDEV (V-VOL).Setting MP blade ofLDEV (V-VOL)

17

raidcom get ldev -ldev_id <ldev#> … [-cnt<count>] [-key <keyword>]

Display information of created LDEV(V-VOL) and confirm the result ofexecuting the command.

Displaying LDEV(V-VOL) information

18

raidcom add lun -port <port#> [host groupname] -ldev_id <ldev#> [-lun_id <lun#>]


Creating LU path19

raidcom get lun -port <port#> [<host groupname>]



20

raidcom monitor pool -pool {<pool ID#> |<pool naming>} -operation start

Start the performance monitoring of a poolfor Smart Tiers.

Startingperformance

21

monitoring of a poolfor Smart Tiers

raidcom monitor pool -pool {<pool ID#> |<pool naming>} -operation stop

Stop the performance monitoring of a poolfor Smart Tiers.

Stoppingperformance

22

monitoring of a poolfor Smart Tiers

raidcom reallocate pool -pool {<pool ID#>| <pool naming>} -operation <type>

Perform instruction of reallocation of poolfor Smart Tiers.

Instructingreallocation of poolfor Smart Tiers

23

Script examplesThe following shows the script examples of virtual volume (Smart Tiers) operation.


Figure 44 Script examples of virtual volume operation (Smart Tiers) (1/3)



External volume operationsCreating external volumes

Use the following provisioning operations to create LDEVs of external volumes and make theLDEVs available from the host.


raidcom modify port -port<port#> -port_attributeELUN

Set port attribute of local storage systemtoExternal (ELUN) port

Setting port attributeof local storagesystem

1

raidcom discoverexternal_storage-port <port#>

Display port information on the externalstorage connected to the External port.

Searching externalstorage

2

External volume operations 153


raidcom discover lun-port <port#>

Display a list of external volumes that canbe mapped from External port.

Searching externalvolume

3

-external_wwn<wwn strings>

raidcom add ldev- external_grp_id

Create external volume.Creating externalvolume

4

<gno-sgno> -ldev_id<ldev#> -capacity <size>[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]

raidcom modify external_grp-external_grp_id

Modify external volume option (cachemode, inflow mode, and MP blade setting).

Modifying externalvolume option

5

<gno-sgno> {-cache_mode< y|n > | -cache_inflow< y|n > | -mp_blade_id<mp#>}

raidcom get external_grp[-external_grp_id<gno-sgno>]

Display external volume information andconfirm result of executing command.

Checking externalvolume information

6

raidcom add path -path_grp<path group#> -port

Set external path. Execute the requirednumber of commands.

Setting external path7

<port#> -external_wwn<wwn strings>

raidcom get path [-path_grp<path group#>]

Display external path information for andconfirm the result of executing thecommand.

Displaying externalpath information

8


Make enabled the LUN security of port.Modify setting such as port topology anddata transfer speed as needed.

Setting port ofexternal storagesystem

9



Creating host group10

raidcom modify host_grp-port <port#> [<host group


Setting host mode11

name>] -host_mode<host mode>[-host_mode_opt<host mode option> … ]




12



13


raidcom get hba_wwn-port <port#> [<host groupname>]



14

raidcom add ldev- external_grp_id

Specify external volume group and createLDEV.

Creating LDEV15

<gno-sgno> -ldev_id<ldev#> {-capacity <size>| -offset_capacity <size>| -cylinder <size>}



[-emulation <emulationtype>][-location <lba>][-mp_blade_id <mp#>]


Create nickname of created LDEV.This operation is arbitrary.


16



17




18

raidcom add lun -port<port#>


Creating LU path19

[<host group name>]-ldev_id <ldev#>[-lun_id<lun#>]

raidcom get lun -port<port#>[<host group name>]



20

Script ExamplesThe following shows the script examples of external volume operations.

Figure 47 Script Examples of External Volume Operation (1/3)

External volume operations 155


Cache Partition operationsCache Partition operations using RAID Manager include migrating LDEVs, parity groups, andexternal volume groups to other CLPRs.

• For information about Cache Partition operations, including important warnings andrestrictions, see the HP P9000 Cache Partition User Guide.

• For details about the RAID Manager commands for Cache Partition operations, see theRAID Manager Reference Guide.

Cache Partition operations 157

Performing Cache Partition operationsThe following table shows the procedure for migrating LDEVs, parity groups, and external volumegroups to other CLPRs.

CommandDescriptionOperation overviewStep

raidcom get clprCheck the status of theCLPRs.

Confirming the CLPRconfiguration.

1

raidcom modify clpr -clpr <clpr#> { -ldev_id<ldev#> | -parity_grp_id <gno-sgno> | -external_grp_id <gnosgno>}

Specify the LDEV number,parity group number, orexternal volume groupnumber.

Migrating one of thefollowing to other CLPRs:

2

• LDEV

• parity group

• external volume group

raidcom get parity_grpFor parity group migration,check the status of theparity group.

Verifying the CLPRmigration.

3

Displaying CLPR informationThe raidcom get clpr command lists and displays the status of the CLPRs in the storage system.If no CLPRs have been created, CLPR0 is displayed as entire cache. Display example:# raidcom get clprCLPR CLPR_NAME TC_CAP(MB) TU_CAP(MB) WP_CAP(MB) SF_CAP(MB) U(%) W(%)S(%)000 Oracle_DB 40000 20000 4000 0 50 30 0001 Oracle_DB_PROD 20000 10000 2000 0 50 10 0003 Oracle_DB_BACK 10000 5000 500 0 50 5 0

Migrating parity groups in a CLPRThis section explains operations from checking the parity group information to moving the paritygroup.

Displaying parity group informationThe raidcom check the status, display the information about the parity group. The following showsthe display example of parity groups.# raidcom get parity_grpT GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPER 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FCR 32-17 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FCR 33-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FCR 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC

Moving parity groupsIf you change the allocation of parity groups, parity groups are moved from another CLPR. Inthis case, plural parity groups which configure the distributed parity group have to be allocatedthe same CLPR. Parity groups including LDEVs where cache area of Cache Residency is definedcannot be moved to another CLPR. For the restrictions on the CLPR's transfer, see the HP P9000Cache Partition User Guide. The following shows examples of parity groups transfer in CLPR.Move the parity group 32-17 to the CLPR number 1.# raidcom modify clpr -clpr 1 -parity_grp_id 32-17

Checking result of CLPR transferBy displaying the information about parity groups, check the result of CLPR transfer. The followingshows an example of parity group list.


# raidcom get parity_grpT GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPER 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FCR 32-17 4 45 140000 RAID1 2D+2D 0 1 DKS2C-K072FCR 33-16 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FCR 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC

Performance Control operationsPerformance Control enables you to prioritize host I/O operations to provide high-speed processingfor specified hosts. The host is identified by the WWN of the host bus adapter. PerformanceControl has two settings: prioritized and non-prioritized. Set the prioritized option for hosts thatrequire high-speed processing, and the non-prioritized option for the other hosts.The following methods are used to set the priority level, but only one of them can be used in asingle storage system:

• Specifying ports and WWNs of host bus adapters

Using PFC without registering host groups to the PFC group◦◦ Using PFC by registering host groups in the PFC group (P9500 only)

For details, see “Configuring Performance Control by specifying ports and WWNs of HBAs”(page 159).

• Specifying an LDEV and a WWN of the host bus adapterFor details, see “Configuring Performance Control by specifying ports and WWNs of HBAs”(page 159).

• Specifying an LDEV and an iSCSI name of a host bus adapterFor details, see “Configuring Performance Control by specifying ports and WWNs of HBAs”(page 159).

NOTE: The WWN of a host bus adapter connected to a port is required when specifying theport with RAID Manager and setting PFC. Since the WWN of an HBA connected to a NAS Platformport cannot be obtained, the PFC setting with specifying these port types is not available.

Configuring Performance Control by specifying ports and WWNs of HBAsThis section describes operations for configuring Performance Control by specifying a port anda WWN of a host bus adapter.

• “Controlling the priority of I/O operations in storage systems on servers” (page 159)

• “Using and managing Performance Control” (page 160)

• “Setting PFC names for WWNs and registering them to the PFC group” (page 161)

• “Configuring Performance Control by specifying ports and WWNs of HBAs” (page 161)

• “Cautions about using Performance Control” (page 165)

• “Cautions when using host groups after registering them in PFC groups (P9500 only)”(page 166)

Controlling the priority of I/O operations in storage systems on serversTo control server performance, specify the I/O operation priority (prioritized or non-prioritized),the threshold (one value for each storage system), and the upper limit (one value for eachnon-prioritized WWN) for host bus adapters on a host. Set a host bus adapter with higher priorityas a prioritized WWN, and set a host bus adapter with lower priority as a non-prioritized WWN.By adjusting the upper limit or threshold to an appropriate value, you can maintain the number

Performance Control operations 159

of accesses or the amount of data to be transferred to a storage system at a higher level on aprioritized server.

Table 29 Priority to be set by specifying a port and aWWNof an HBA, and control of serverperformance

Server performancePriority

Controls server performance based on the upper limit. The upper limit is set for eachnon-prioritized WWN.

Non-prioritized

The upper limit suppresses the number of accesses to a storage system, or the amount ofdata to be transferred. Monitoring information can be displayed according to the combinationof a port and a WWN of a host bus adapter.

Controls server performance based on the threshold. One threshold is set for each storagesystem, but it cannot be set for each prioritized WWN.

Prioritized

If the amount of traffic goes down to the threshold, the control of the upper limit is disabledautomatically.Monitoring information can be displayed according to the combination of a port and a WWNof a host bus adapter.

Using and managing Performance ControlYou can give a nickname (PFC name) to each host WWN to assist in managing the hosts. Youcan also manage WWN and the PFC name per group. The groups to which WWN and the PFCname are registered are managed uniquely. The following table lists the details for the PerformanceControl operations and the management unit.

Management per systemManagement per portPFC Operation

thresholdprioritized or non-prioritizedraidcom modify pfc_wwnupper limitWWN or PFC name

thresholdprioritized or non-prioritizedraidcom modify pfc_groupupper limitPFC group name

PFC name-raidcom add pfc_wwn

PFC group name-raidcom add pfc_group

PFC name (PFC information perport is also deleted.)

-raidcom delete pfc_wwn

PFC group name (PFCinformation per port is alsodeleted.)

-raidcom delete pfc_group

thresholdprioritized or non-prioritizedraidcom get pfc_wwnupper limitWWN or PFC namePFC group name

thresholdprioritized or non-prioritizedraidcom get pfc_groupupper limitPFC group name

control mode of PFCperformance of server (IOps/KBps)raidcom monitor pfc_wwn

control mode of PFCperformance of server (IOps/KBps)raidcom monitor pfc_group


Setting PFC names for WWNs and registering them to the PFC groupThe following figure shows the workflow of setting PFC names for WWNs and registering themin the PFC group.

Configuring Performance Control by specifying ports and WWNs of HBAsThis section describes how to use Performance Control when setting a port and a WWN of ahost bus adapter. For P9500 models, the procedure varies depending on whether the host groupsis registered in the PFC group. Only P9500 models can register host groups to the PFC group.The following table shows the procedure when the host group is not registered in the PFC group.

Table 30 Controlling server performance when the host group is not registered in the PFCgroup

Executed commandDescriptionOperationoverview

Step

raidcom modify pfc_wwn -port <port#>[-pfc_priority <y/n>] {-limit_io |

Set the priority (prioritized ornon-prioritized option) for the

Setting the PFCinformation forWWN

1

-limit_kb | -limit_mb } <value> {-hba_wwn<wwn_strings> | -pfc_name <nick_name>}PFC controlling by specifying

the number of port to whichthe host bus adapter isconnected and WWN of thehost bus adapter.

raidcom add pfc_wwn -port <port#>-pfc_name <nick_name> -hba_wwn <wwn_strings>

Give a nickname to WWN forthe PFC controlling to makethe host bus adapterdistinguishable.

Giving anickname (PFCname).

2


Table 30 Controlling server performance when the host group is not registered in the PFCgroup (continued)


Step

raidcom add pfc_group -port <port#>-pfc_group <group_name> -hba_wwn<wwn_strings>

Specifying WWN: To operateper group, group multipleWWNs for PFC control intoone group.

RegisteringWWN for PFCto PFC group

3

raidcom add pfc_group -port <port#>-pfc_group <group_name> <nick_name>

Specifying nickname: Tooperate per group, groupmultiple WWNs for PFCcontrol into one group.

raidcom get pfc_wwn -port <port#>[ -hba_wwn <wwn_strings> | -pfc_name<nick_name> ]

Display the setting state ofPFC by specifying WWN orthe PFC name.

Checking thePFCinformation

4

raidcom get pfc_group -port <port#>-pfc_group <group_name>

Display the PFC informationby specifying the PFC groupname.

raidcom monitor pfc_wwn {-hba_wwn<wwn_strings> | -pfc_name <nick_name>}

Display the monitoringinformation by specifyingWWN or the PFC name.

Displaying themonitoringinformation of

5

the prioritizedraidcom monitor pfc_group -pfc_group<group_name>

Display the monitoringinformation by specifying thePFC group name.

WWN or thenon-prioritizedWWN

raidcom modify pfc_wwn -port <port#>[-pfc_priority <y/n>] {-limit_io |

Change the threshold or theupper limit value of the

Changing thethreshold or the

6

-limit_kb | -limit_mb } <value> {-hba_wwn<wwn_strings> | -pfc_name <nick_name>}non-prioritized WWN by

specifying WWN or the PFCname.

upper limitvalue of thenon-prioritizedWWN

raidcom modify pfc_group -port <port#>[-pfc_priority <y/n>] {-limit_io |

Change the threshold or theupper limit value of the

-limit_kb | -limit_mb } <value> -pfc_group<group_name>

non-prioritized WWN byspecifying the PFC groupname.

raidcom delete pfc_wwn -port <port#>[-hba_wwn <wwn_strings> | -pfc_name<nick_name> ]

Delete WWN from the PFCtargets by specifying WWNor the PFC name.

Deleting WWNfrom the PFCtargets

7

raidcom delete pfc_group -port <port#>-pfc_group <group_name>

Delete WWN from the PFCtargets by specifying the PFCgroup name.

The following table shows the procedure when the host group is registered in the PFC group.

NOTE: For cautions when registering host groups to the PFC group and operating them (P9500only), see “Cautions when using host groups after registering them in PFC groups (P9500 only)”(page 166).

Table 31 Controlling server performance when the host group is registered in the PFCgroup (P9500 only)


Step

raidcom add pfc_group -pfc_group <group name>Specify the host group towhich WWN of the host bus

Registering thehost group that

1


Table 31 Controlling server performance when the host group is registered in the PFCgroup (P9500 only) (continued)


Step

-port <port#> [<host group name>]-pfc_host_grp

adapter is registered andregister the host group to thePFC.

contains WWNcontrolled byPFC to the PFCgroup

raidcom modify pfc_group -port <port#>[<host group name>] -pfc_host_grp

Specify the host group tochange the threshold or the

Changing thethreshold or the

2

[ -pfc_priority <y/n> ] { -limit_io |-limit_kb | -limit_mb <value>

maximum value of thenonpreferred WWN.

maximum valueof nonpreferredWWN.

raidcom get pfc_wwn -port <port#>[ -hba_wwn <wwn_strings> ]

Specify the WWN name todisplay the PFC settingstatus.

Checking thePFCinformation

3

raidcom get pfc_group -port <port#>[<host group name>] -pfc_host_grp

Specify the host group todisplay the PFC settingstatus.

4

raidcom get pfc_group -port <port#>-pfc_group <group_name>

Specify the PFC group nameto display the PFC settingstatus.

5

raidcom monitor pfc_wwn {-hba_wwn<wwn_strings> }

Specify the WWN name todisplay monitoringinformation.

Displayingmonitoringinformation of

6

preferred orraidcom monitor pfc_group -pfc_group<group_name>

Specify the PFC group nameto display monitoringinformation.

7 nonpreferredWWN

raidcom add hba_wwn -port <port#>[<host group name>] -hba_wwn <WWN strings>

Register the WWN to thehost group registered in thePFC group to set the WWNas the PFC target.

RegisteringWWN to thehost groupregistered in

8

the PFC group,and setting theWWN as thePFC target

raidcom delete pfc_group -port <port#>[<host group name>] -pfc_host_grp

Specify the host group todelete it from the PFC target.

Deleting fromthe PFC targets

9

raidcom delete host_grp -port <port#>[<host group name>]

Delete the host group todelete it from the PFC target.

10

raidcom delete hba_wwn -port <port#>[<host group name>] -hba_wwn <WWN strings>

Delete WWN from the hostgroup to delete it from thePFC target.

11

Displaying the WWN of host bus adaptersDisplays the WWN of the host bus adapters that are registered in host groups. Display example:# raidcom get hba_wwn -port CL4-E-0PORT GID GROUP_NAME HWWN Serial# NICK_NAMECL4-E 0 Linux_x86 210000e08b0256f8 63528 ORA_NODE0_CTL_0CL4-E 0 Linux_x86 210000e08b039c15 63528 ORA_NODE1_CTL_1

Setting the priority on host bus adaptersSet the host bus adapter (WWN: 210000e0,8b0256f8) to the non-prioritized WWN, and set 5000[IOPS] as the upper limit.


# raidcom modify pfc_wwn -port CL4-E -pfc_priorityn -limit_io 5000 -hba_wwn 210000e0,8b0256f8

Set the host bus adapter (WWN: 210000e0,8b039c15) to the prioritized WWN, and set 3000[IOPS] as the threshold.# raidcom modify pfc_wwn -port CL4-E -pfc_priorityy –limit_io 3000 -hba_wwn 210000e0,8b039c15

-limit_io 3000 shown in the example of the priority setting is the threshold value of the entiresystem.

Displaying the status of the prioritized WWN and the non-prioritized WWN settingsDisplay the status of the prioritized WWN and the non-prioritized WWN settings and check it.Display examples of the status of the prioritized WWN and the non-prioritized WWN settings.Display the status of settings of the prioritized WWN and the non-prioritized WWN assignedunder the specified port (CL4-E).# raidcom get pfc_wwn -port CL4-EPORT PFC_MD PFC_WWN NICK_NAME GRP_NAME Serial#CL4-E WWN 210000e08b0256f8 - - 63528CL4-E WWN 210000e08b039c15 - - 63528

Display the status of setting to specify the WWN (210000e08b0256f8).# raidcom get pfc_wwn -port CL4-E -hba_wwn 210000e0,8b0256f8PORT PFC_MD PRI IOps KBps Serial#CL4-E WWN N 5000 - 63528

Displays the status of setting to specify the WWN (210000e08b039c15).# raidcom get pfc_wwn -port CL4-E -hba_wwn 210000e0,8b039c15PORT PFC_MD FRI IOps KBps Serial#CL4-E WWN Y 3000 - 63528

The threshold value displayed for the prioritized WWN by using the get pfc_wwn command isset for the entire system.

Setting PFC names for host bus adaptersThe host bus adapters can be identified by checking the WWNs, but using PFC names mightmake it easier to identify the host bus adapters. Display examples of setting the PFC name ofthe host bus adapter:Set the PFC name (ORA_NODE0_CTL_0) for the WWN (210000e08b0256f8).# raidcom add pfc_wwn -port CL4-E -pfc_nameORA_NODE0_CTL_0 -hba_wwn 210000e0,8b0256f8

Set the PFC name (ORA_NODE1_CTL_1) for the WWN (210000e08b039c15).# raidcom add pfc_wwn -port CL4-E -pfc_nameORA_NODE1_CTL_1 -hba_wwn 210000e0,8b039c15

PFC names are managed uniquely in the entire system.

Grouping multiple host bus adapters into one groupYou can group the host bus adapters into PFC groups, and then use the PFC groups to changethe priorities of multiple host bus adapters at the same time. You can also set the same upperlimit value for all host bus adapters in a PFC group at the same time.Examples of setting the PFC group:Set the PFC name (ORA_NODE0_CTL_0) for the PFC gropup name (WWN_GRP_LINUX0).# raidcom add pfc_group -port CL4-E -pfc_group WWN_GRP_LINUX0 ORA_NODE0_CTL_0

Set the WWN (210000e08b039c15) for the PFC gropup name (WWN_GRP_LINUX1).# raidcom add pfc_group -port CL4-E -pfc_groupWWN_GRP_LINUX1 -hba_wwn 210000e0,8b039c15


PFC group names are managed uniquely in the entire system.

Obtaining monitoring information of the prioritized WWN and the non-prioritized WWNYou can use the monitoring function to check whether the performance of the prioritized WWNcan be secured by setting the upper limit. Example of acquiring the monitoring information:Acquires the monitoring information by specifying the WWN (210000e08b039c15).# raidcom monitor pfc_wwn -hba_wwn 210000e0,8b039c15PORT PFC_MD IOps KBps Serial#CL4-E WWN 5000 5000000 63528

Stopping performance control of server by using PFC functionTo stop controlling the performance of the server by using the PFC function, delete the PFCname from the PFC targets.Example of deleting from the PFC targets:Delete the PFC name ("ORA_NODE0_CTL_0") from the PFC targets.# raidcom delete pfc_wwn -port CL4-E -pfc_name ORA_NODE0_CTL_0

Cautions about using Performance ControlThe following table describes the cautions about using Performance Control.

DescriptionCaution

Performance Control settings are exclusive for RAID Manager operations and Remote WebConsole operations:

Exclusive accesscontrol with RemoteWeb Console • If you set Performance Control using RAID Manager, you cannot set Performance Control

from Remote Web Console. You need to delete all Performance Control settings madeusing RAID Manager, and then use Performance Control on Remote Web Console tomake the Performance Control settings.

• If you set Performance Control using Remote Web Console, you cannot set PerformanceControl using RAID Manager. You need to delete all Performance Control settings madeusing Remote Web Console, and then use Performance Control from RAID Manager tomake the Performance Control settings.

If you set Performance Control using RAID Manager, you cannot use a part of PerformanceMonitor of Remote Web Console. For details, see the XP7 Performance for Open andMainframe Systems User Guide.

Performance Monitorof Remote WebConsole

When you perform the following operations, the upper limit value control might be disabledfor about two minutes:

Maintenance

• Adding, replacing, or removing cache memory

• Changing the system configuration

• Updating the firmware

• XP7: Replacing MP blades

• XP7: Adding, replacing, or removing channel adaptesr (CHAs)

• Powering on and off the storage system

Note: The upper limit value control might be disabled when an abnormal condition that causesthe login or logout of the host occurs, such as a network failure or damage on the HBA orFibre cable. Resolve the cause of the unexpected login/logout behavior, and then enable theupper limit value control.

If you delete a combination of the specified port and the WWN of the HBA from the PFCtargets by using the PFC name, the PFC setting and PFC name under the specified port are

When specifying portsand WWNs of HBAs:

deleted. If the same PFC name is set to another port, only the PFC setting of the specifiedport is deleted.

Deleting PFC namesor PFC group names

If you delete a combination of the specified port and the WWN of the HBA from the PFCtargets by using the PFC group name, the PFC setting and the group under the specified


DescriptionCaution

port are deleted. If the same PFC group name is set to another port, only the PFC setting ofthe specified port is deleted.

When you use the resource group function, the range of operation is limited per port ofresource group by Performance Control. The threshold value, the PFC name, and the PFC

When specifying portsand WWNs of HBAs:

group name, which are managed in the entire system, are common among the resourcegroups.

Resource groupfunction and

When you perform Performance Control operations using the resource group function, sharethe threshold value that the storage administrator determines among users of resource

restrictions forPerformance Control

groups. Determine rules for PFC names and PFC group names including port names to avoidredundant names between ports.

For microcode 80-04-xx-xx/00 or earlier in XP7, if PFC information is set or referenced,behavior is not guaranteed.

When specifyingWWN or iSCSI name

The following errors might occur:of LDEVs and HBAs:DKCMAIN microcode

• Server performance cannot be controlled according to the specified upper limit value.version and storagemodels • No detailed error message appears when an error occurs.

• No error message appears if an invalid upper limit value is set.

• The same error as when an invalid WWN is specified occurs. For details about the errors,see the row below.

Behavior when PFC information is set for or referenced by P9500 cannot be guaranteed. IfPFC information is set or referenced, the following errors might occur:

• Server performance cannot be controlled according to the specified upper limit value.

• No detailed error message appears when an error occurs.

• No error message appears if an invalid upper limit value is set.

Behavior is not guaranteed when an invalid WWN (not in the format defined by IEEE) isspecified.


In XP7, if you specify PFC information for an invalid WWN, you might not be able to set PFCinformation with an iSCSI name specified.

of LDEVs and HBAs:Invalid WWNs

When the number of I/Os issued to a non-prioritized LDEV reaches the upper limit, I/Osexceeding the upper limit are retained in the storage system. By this method, host process


might be consumed, and I/O performance of prioritized LDEVs or non-prioritized LDEVs thatof LDEVs and HBAs:have I/ Os below the upper limit might be affected. If I/O performance of other LDEVs becomesI/Os issued to

nonprioritized LDEVs lower than expected due to the host process number limit, review the queue depth settingsor alternate path policy settings of the host.

Cautions when using host groups after registering them in PFC groups (P9500 only)The following limitations apply when you register host groups in PFC groups (P9500 only):1. You cannot register host groups that contain WWNs for which PFC information is set in step

1 of Table 30 (page 161).2. You cannot register host groups in PFC groups in which WWNs (PFC targets) are registered

in step 3 of Table 30 (page 161).You can register host groups described in limitation 1 above in PFC groups that were not specifiedin step 3 of Table 5-3 if the WWNs that belong to the host group meet the following requirements:

• The WWNs are not already registered as PFC targets using another port number byperforming step 1 of Table 5-3.

• The WWNs belong to PFC groups that were specified in step 3 of Table 5-4.After registering a host group in a PFC group, Performance Control sets the PFC information asfollows:• When the PFC group is associated with the host group, Performance Control sets the same

priority (prioritized or non-prioritized) as the PFC group. Then, for the prioritized host group


Performance Control sets the threshold, or for the non-prioritized host group PerformanceControl sets the upper limit of non-prioritized WWNs.

• When the PFC group is not associated with the host group, Performance Control sets thepriority setting to prioritized without changing the threshold.

For how to register host groups in PFC groups, see Table 31 (page 162).

Configuring Performance Control by specifying LDEVs and WWNs ofHBAs

To control the I/O priority for volumes in a storage system on the server, you can configurePerformance Control by specifying an LDEV and a WWN of a host bus adapter.For the combination of a volume (LDEV) and a host (WWN or iSCSI name), specify the I/O priority(prioritized or non-prioritized). When the priority is non-prioritized, set the upper limit value tocontrol the server performance. Set the prioritized priority to the host with higher priority, and thenon-prioritized priority to the host with lower priority. By adjusting the upper limit value to anappropriate value, you can maintain the number of accesses and the amount of data to betransferred from a prioritized host to a storage system at a higher level.The following table shows requirements for using Performance Control by specifying the LDEV,the WWN or iSCSI name of the host bus adapter.

RangeItem

1 to 16,38411Number of LDEVs that can be registered for each storagesystem

1 to 2,04822Number of WWNs that can be registered for each storagesystem

1 to 2,04822Number of iSCSI names that can be registered for eachstorage system

1 to 323Number of WWNs that can be registered for each LDEV

1 to 323Number of iSCSI names that can be registered for eachLDEV

Notes:1. When the maximum number of LDEVs for a storage system is less than 16,384, the maximum number of LDEVs

that can be registered is the maximum number of total LDEVs for a storage system.2. The sum of the number of WWNs and the number of iSCSI names. This sum should be a maximum of 2,048 for

each storage system.3. The sum of the number of WWNs and the number of iSCSI names. This sum should be a maximum of 32 for

each LDEV.

NOTE:• When there are 4,096 or more LDEVs with PFC configured, if you configure PFC in another

LDEV, host I/O response in the LDEV is slower than the existing LDEVs with PFC configured.To improve the host I/O response, delete the PFC information in the new LDEV with PFCconfigured, then delete the existing PFC information to decrease the number of LDEVs withPFC configured to 4,095 or fewer, and then configure PFC in the new LDEV again.

Table 32 Priority to be set by specifying a port and aWWNof an HBA, and control of serverperformance


Controls server performance based on the upper limit. The upper limit is set for eachnon-prioritized WWN or non-prioritized iSCSI name.

Non-prioritized

Configuring Performance Control by specifying LDEVs and WWNs of HBAs 167

Table 32 Priority to be set by specifying a port and aWWNof an HBA, and control of serverperformance (continued)


The upper limit suppresses the number of accesses from a host bus adapter to an LDEV, orthe amount of data to be transferred.Monitoring information can be displayed according to the combination of an LDEV and aWWN of a host bus adapter.

Does not control server performance of a prioritized WWN or prioritized iSCSI name.PrioritizedMonitoring information can be displayed according to the combination of an LDEV and aWWN of a host bus adapter.

NOTE: Unlike the case of configuring Performance Control by specifying a port and a WWNof a host bus adapter, the function for enabling or disabling control of the upper limit automaticallyaccording to the traffic amount is not supported.

Table 33 Performance Control operations when an LDEV and a WWN of an HBA is specified

Executed commandDescriptionOperation overviewStep

raidcom modify pfc_ldev -ldev_id<ldev#> -hba_wwn <wwn strings> [

Specify the LDEV number, and the WWNof the host bus adapter to set the priority

Setting PFC informationfor an LDEV and a WWN

1

-pfc_priority <y/n>] [{-limit_io |-limit_kb | -limit_mb} <value> ]

(prioritized or non-prioritized) as the PFCtarget.To set the non-prioritized option, set theupper limit as well.Normally, set the prioritized option in step1, and check the monitoring information instep 3. And then, if necessary, change thepriority to non-priority in step 4, and set theupper limit.

raidcom get pfc_ldev [-ldev_id<ldev#> | -hba_wwn <wwn strings> ]

Display the setting status of PFC.Checking PFC information2

raidcom monitor pfc_ldev -ldev_id<ldev#> -hba_wwn <wwn strings>

Display monitoring information.Displaying monitoringinformation of theprioritized ornon-prioritized WWN

3

raidcom modify pfc_ldev -ldev_id<ldev#> -hba_wwn <wwn strings>

If necessary, determine the priority and theupper limit based on the monitoringinformation, and then change the priority.

Changing the upper limitof the prioritized andnon-prioritized WWNs

4

[-pfc_priority <y/n>] [{-limit_io| -limit_kb | -limit_mb} <value>]

When the non-prioritized option is set, setthe upper limit as well.

raidcom delete pfc_ldev -ldev_id <ldev#>-hba_wwn <wwn strings>

Specify the LDEV number and the WWNof the host bus adapter to delete them fromthe PFC target.

Deleting from the PFCtarget

5

Virtual storage machine operations• “Creating host groups in a virtual storage machine” (page 169)

• “Adding LDEVs to a virtual storage machine” (page 169)

• “Removing the virtual storage machine” (page 169)


Creating host groups in a virtual storage machineUse the following provisioning operations to create host groups in a virtual storage machine andto assign virtualized LDEV to LU.


raidcom add resource-resource_name <resource group

Reserve ports and host group IDs to theresource groups in the virtual storage

Reserving host groupIDs

1

name>-port <port#> -<HG#>

machine. Be sure to execute thecommand before creating host groups.

raidcom add host_grp -port<port#> -<HG#>

Create host groups by specifying thereserved port and host group ID to theresource group.

Creating host groups2

-host_grp_name <host groupname>

raidcom modify host_grp-port <port#> [<host group name>] -

Specify the host mode to the created hostgroup. Also, specify the host modeoptions if necessary.

Specifying the hostmode and host modeoptions

3host_mode < host mode> [- host_mode_opt<host mode option> … ]

raidcom add hba_wwn -port <port#>[<host group name>] -hba_wwn <WWNstrings>

Register hosts to the host group.Adding hosts to the hostgroup

4

Adding LDEVs to a virtual storage machineUse the following provisioning operations to add LDEVs to a virtual storage machine and to useLDEVs from hosts.


raidcom unmap resource-ldev_id <ldev#>-virtual_ldev_id <ldev#>

Specify an LDEV ID to delete the virtualLDEV ID set by default. By default, thevirtual LDEV ID is the same as the realLDEV ID.

Delete the virtual LDEVID set by default

1

raidcom add resource-resource_name <resource groupname> -ldev_id <ldev#>

Add the LDEV of which the virtual LDEVID was deleted to the resource group inthe virtual storage machine.

Add the LDEV to theresource group

2

raidcom map resource-ldev_id <ldev#>

Set a virtual LDEV ID to the specifiedLDEV. Also, specify the product ID andSSID if necessary.

Virtualize LDEVs3

-virtual_ldev_id <ldev#>[-ssid<ssid> -emulation<emulation type>]

raidcom add lun -port <port#>[<host group name>] -ldev_id

To create LU path, assign LDEVs to thehost group that belongs to the resourcegroup in the virtual storage machine.

Create LU path4

<ldev#>[-lun_id<lun#>]

Removing the virtual storage machineUse the following provisioning operations to remove resources from the virtual storage machineand to remove the virtual storage machine.


raidcom delete lun -port<port#> [<host group name>]

Remove the LU path from the LDEV inthe virtual storage machine.

Remove the LU path1

{-lun_id <lun#> |-ldev_id <ldev#> |-grp_opt <group option>

Virtual storage machine operations 169


-device_grp_name <device groupname> [<device name>]}

raidcom unmap resource-ldev_id <ldev#>-virtual_ldev_id <ldev#>

Remove the virtual LDEV ID from theLDEV in the virtual storage machine.

Remove the virtualLDEV ID

2

raidcom delete resource-resource_name <resource groupname> -ldev_id <ldev#>

Remove the LDEV from the resourcegroup in the virtual storage machine

Remove the LDEV fromthe resource group

3

raidcom map resource-ldev_id <ldev#>-virtual_ldev_id <ldev#>

Specify the virtual LDEV ID that is thesame as the real LDEV ID in order toinvalidate the LDEV virtualization.

Invalidate the LDEVvirtualization

4

raidcom delete host_grp-port <port#> [<host groupname>]

Delete the host group in the virtualstorage machine.

Delete the host group5

raidcom delete resource-resource_name <resource group

Remove the host group ID that belongsto the resource group in the virtualstorage machine

Remove the host groupID from the resourcegroup

6

name> -port <port#>-<HG#>

raidcom delete resource-resource_name <resource group name>

Remove the resource from the resourcegroup in the virtual storage machine.

Remove the resourcefrom the resource group

7[-ldev_id <ldev#> | -port <port#> [<hostgroup name>] |-parity_grp <gno-sgno> |-external_grp_id <gno-sgno> | -grp_opt<group option> -device_grp_name <devicegroup name> [<device name>]]

raidcom delete resource-resource_name <resource groupname>

Delete all resource groups in the virtualstorage machine in order to remove thevirtual storage machine.

Remove the virtualstorage machine

8


6 Data replication operations with RAID ManagerThis chapter describes data replication operations with RAID Manager.

About data replication operationsThe data replication features of the RAID storage systems include:

• Local replication:

Business Copy◦◦ Business Copy MF

◦ Fast Snap

◦ Snapshot

◦ Auto LUN

• Remote replication:

Continuous Access Synchronous◦◦ Continuous Access Synchronous MF

◦ Continuous Access Journal

◦ Continuous Access Journal MF

◦ High Availability

• Mainframe replication:

Compatible XRC◦◦ Compatible FlashCopy

◦ Business Continuity Manager

For detailed information about any of these features, see the applicable user guide (for example,HP P9000 Business Copy User Guide).

Features of paired volumesPaired logical volumes are often handled independently by servers. When RAID Manager isused, the paired volumes can be managed by the replication functions (for example, BusinessCopy, Continuous Access Synchronous, Continuous Access Journal, High Availability) ascombined or separated pairs. The replication functions regard the two volumes being combinedor separated as a uniquely paired logical volume used by the servers. Paired volumes can alsobe handled as groups, grouping them by units of server software or units of databases and theirattributes.For detailed information about volume pairs (for example, maximum number of pairs per storagesystem, maximum P-VOL size), see the user guide for your storage system and copy function(for example, HP P9000 Business Copy User Guide).

About data replication operations 171

Figure 50 Concept of paired volumes

Addressing paired logical volumes: The correspondence of paired logical volumes to their physicalvolumes is defined by describing the paired logical volume names and group names in theconfiguration definition files of each server. It is possible to define a server for the paired logicalvolumes in units of group name. Each paired logical volume must belong to a group in order todetermine the corresponding server.Specification of volumes by commands: Volume names to be used by the RAID Managercommands must be referenced via the paired logical volume names or the group names.

Using RAID Manager with Business Copy and Continuous AccessSynchronous

RAID Manager allows you to perform Business Copy and Continuous Access Synchronousoperations by issuing Business Copy and Continuous Access Synchronous commands from theUNIX/PC server host to the RAID storage system. Business Copy and Continuous AccessSynchronous operations are nondisruptive and allow the primary volume of each volume pair toremain online to all hosts for both read and write operations. Once established, Business Copyand Continuous Access Synchronous operations continue unattended to provide continuousdata backup.There are specific requirements for using Business Copy and Continuous Access Synchronousin high-availability (HA) configurations. UNIX/PC servers in HA configurations normally supportdisk duplication functions to enhance disk reliability (for example, mirroring provided by the LVMor device driver, RAID5 or an equivalent function provided by the LVM). UNIX/PC servers also

172 Data replication operations with RAID Manager

feature hot standby and mutual hot standby functions in case of failures on the server side.However, mutual hot standby for disaster recovery has not yet been achieved since it requiresthe remote mirroring function.Business Copy provides the mirroring function within the storage system. For detailed informationabout Business Copy operations, please see the HP P9000 Business Copy User Guide for yourstorage system.Continuous Access Synchronous provides remote mirroring functionality, linkage functionalitywith failover switching, and remote backup operations among servers, all of which are requiredby UNIX/PC servers in HA configurations for disaster recovery. For detailed information aboutContinuous Access Synchronous operations, please see the HP P9000 Continuous AccessSynchronous User Guide for your storage system.

Using RAID Manager with Fast SnapRAID Manager allows you to perform Fast Snap operations by issuing raidcom commands (forexample, raidcom add snapshot) to the RAID storage system. Fast Snap stores snapshotsin storage system. Creating a Fast Snap pair changes the status to “PAIR” and stores snapshotdata as a copy of the data on the Fast Snap P-VOL. A Fast Snap pair consists of a P-VOL, oneor more S-VOLs that are virtual volumes (V-VOLs), and one or more pool-VOLs that are LDEVs.P-VOL differential data is stored as snapshot data in the pool-VOLs. If your storage systemexperiences a data storage failure, you can restore the data using the snapshot data in the pool.Splitting a Fast Snap pair saves a snapshot and stops the copying of replaced data in the pool.Consistency groups and snapshot groups are groups of pairs for which you can simultaneouslyperform pair tasks on all pairs within the group. You can use RAID Manager raidcom commandsto create consistency groups and snapshot groups and to split pairs to store the snapshot datafor the groups.

• A consistency group can include FS, BC, and BC MF pairs. Splitting the pairs using thegroup assures data consistency at the time the storage system receives the request.

• A snapshot group is a group of only Fast Snap pairs. Use consistency or snapshot groupsto perform Fast Snap tasks on all of the pairs within the group. You define Fast Snap pairsto a snapshot group when you create the pairs.

NOTE: When you use the RAID Manager to define multiple Fast Snap pairs in a consistencygroup, you can only specify one consistency group for a group defined in the RAID Managerconfiguration definition file.The configuration definition file for RAID Manager is a group that is not a consistency group.Creating a new pair and defining the pairs in a consistency group for a group you defined usingthe RAID Manager configuration definition file and the pair is already defined in a consistencygroup defines the pair in the same consistency group, even if you try to create a new pair andassign it to a different consistency group.

For details about Fast Snap, see the HP P9000 Fast Snap User Guide for your storage system.

Using RAID Manager with High AvailabilityThe RAID Manager software is installed on the host servers and used for High Availabilityoperations. The RAID Manager command devices and RAID Manager configuration definitionfiles are required for High Availability operations. You can execute RAID Manager commandsfor High Availability using the in-band or out-of-band method of RAID Manager commandexecution.For details about High Availability, see the XP7 High Availability User Guide. For details aboutthe RAID Manager command options and display results for High Availability operations (forexample, PHY_LDEV, VIR_LDEV), see the RAID Manager Reference Guide.

Using RAID Manager with Fast Snap 173

NOTE: If you set the S-VOL Disable attribute of Data Retention to an HA secondary volume,HA pair operations from RAID Manager are restricted. Release the S-VOL Disable attribute ofthe HA secondary volume, and then perform the HA pair operations.

Business Copy operationsFigure 51 (page 174) illustrates a Business Copy configuration. The Business Copy commandsalso support the functionality that links the system operation for the purpose of volume backupamong UNIX servers managed by the operating system. For detailed information about theoperational requirements and specifications for Business Copy, see the HP P9000 BusinessCopy User Guide for your storage system.Following is a list of sample Business Copy functions that can be executed using RAID Managercommands:

• Pair creation: Creates a new volume pair. Volume pairs can be created in units of volumesor groups.

• Pair splitting: Splits a volume pair and allows read and write access to the secondary volume.

• Pair resynchronization: Resynchronizes a split volume pair based on the primary volume.The primary volume remains accessible during resynchronization.

• Pair resynchronization with restore option: Resynchronizes a split pair based on the secondaryvolume (reverse resync). The primary volume is not accessible during resync with restoreoption.

• Event waiting: Used for waiting for the completion of a volume pair creation orresynchronization to check the pair status.

• Pair status display and configuration confirmation: Displays the pair status and configurationof the volume pairs; this can also be used for checking the completion of a pair creation orpair resynchronization.

Figure 51 Business Copy system configuration


Business Copy duplicated mirroringDuplicated mirroring of a single primary volume is possible when the Business Copy feature isused. Duplicated mirror volumes can be specified up tp the maximum quantity 3. The duplicatedmirror volumes of the P-VOL are expressed as virtual volumes using the mirror descriptors(MU#0-2) in the configuration diagram as shown below.

Figure 52 Business Copy duplicated mirrors

Business Copy cascading pairsBusiness Copy provides a cascading function for the Business Copy S-VOL. Cascading mirrorvolumes can be specified up to the maximum quantity 2. The cascading mirrors of the S-VOLare expressed as virtual volumes using the mirror descriptors (MU#1-2) in the configurationdiagram as shown below. The MU#0 of a mirror descriptor is used for connection of the S-VOL.

Business Copy operations 175

Figure 53 Business Copy cascade volume pairs

Restrictions for Business Copy cascading volumesPair Creation. Pair creation of S-VOL (oradb1) can only be performed after the pair creation ofS/P-VOL (oradb). If you create the oradb1 pair first without creating the oradb, the subsequentoradb creation will be rejected with EX_CMDRJE or EX_CMDIOE.

Pair splitting. Pair splitting of S-VOL (oradb1) can only be performed after the S/P-VOL (oradb)is in a SMPL or PSUS state, since Business Copy copies are asynchronous. If pair splitting ofthe S-VOL (oradb1) is attempted while the S/P-VOL (oradb) is in a COPY or PAIR state, thepairsplit 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 whenthe S-VOL (oradb) and the P-VOL (oradb2) on the S/P-VOL are in the SMPL and PSUS states.If the pair restore of S-VOL (oradb1) is performed while either the S-VOL (oradb) or P-VOL(oradb2) on the S/P-VOL are in a COPY, PAIR or PSUS state, the pairresync -restorecommand is rejected with EX_CMDRJE or EX_CMDIOE.

Restriction for Continuous Access Synchronous/Business Copy cascading volumesPair restore (resynchronization from S-VOL (oradb1) to S/P-VOL) can only be performed whenthe Continuous Access Synchronous S-VOL (oradb) and the P-VOL (oradb2) on the S/P-VOLare in the SMPL or PSUS(SSUS) state. If pairresync of S-VOL (oradb1) is performed when theS/P-VOL (oradb or oradb2) is in any other state, the pairresync -restore option commandis rejected with EX_CMDRJE or EX_CMDIOE.

Continuous Access Synchronous operationsRAID Manager Continuous Access Synchronous commands operate in conjunction with thesoftware on the UNIX/PC servers and the Continuous Access Synchronous functions of the RAIDstorage systems. The RAID Manager software provides failover and other functions such asbackup commands to allow mutual hot standby in cooperation with the failover product on theUNIX/PC server (for example, MC/ServiceGuard, FirstWatch, HACMP).

NOTE: For proper maintenance of Continuous Access Synchronous operations, it is importantto determine if there are any faults in paired volumes, recover the volumes from the failures assoon as possible, and continue operation in the original system.

NOTE: For information about the operational requirements and specifications for ContinuousAccess Synchronous, please see the HP P9000 Continuous Access Synchronous User Guidefor your storage system.

Continuous Access Synchronous operations 177

Continuous Access Synchronous takeover commandsFigure 54 (page 178) illustrates a high-availability (HA) environment. When a server software erroror a node error is detected, the HA failover software causes the cluster manager (CM) to monitorserver programs and causes the CM of the standby node to automatically activate the HA controlscript of the corresponding server program. The HA control script usually contains databaserecovery procedures, server program activation procedures, and other related recoveryprocedures. The Continuous Access Synchronous RAID Manager takeover commands are alsoactivated by the HA control script.

Figure 54 Server failover system configuration

Legend

• CM (Cluster Manager): Demon process that keeps the consistency of the cluster by monitoringthe node and server program in the cluster.

• Script: Shell script that automatically performs takeover process when CM detects the serverfailure.

In an HA environment, a package is a group of applications that are scripted to run on thesecondary 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 executedby the system administrator (see Figure 55 (page 179)).

NOTE: If the operation is performed when RAID Manager and Continuous Access Synchronousare being used, the volume is switched from primary to secondary as if an error had occurred,even though data consistency is assured. When restoral of the original node occurs along withits original package (group of applications), it is necessary to copy the data on the secondaryvolume onto the primary volume; this operation can take as much time as the initial copy operationfor the pair. In actual operation, no package can be transferred when Continuous AccessSynchronous is being used. The secondary package is switched to the primary package, andvice versa, when the primary volume is switched to the secondary volume. Therefore, the primaryand secondary Continuous Access Synchronous volumes should be switched depending on thepackage state.


Figure 55 Package transfer on high availability (HA) software

The swap option of the takeover command allows swapping of the primary and secondary volumedesignations, so if the primary and secondary volume are switched due to a server error orpackage transfer, pair operation can be continued using the reversed volumes. When control ishanded back over to the original node, swapping the volume designations again eliminates theneed of copying them. In addition, the takeover command has the option to allow the secondaryvolume to be logically separated (for the purpose of recovery from a disaster at the originaloperating site). The takeover command has four functions designed for HA software operation:Takeoverswitch, swap-takeover, SVOL-takeover, and PVOL-takeover. This command is notavailable for Business Copy.

Takeover-switch functionThe control scripts activated by HA software are used by all nodes of a cluster in exactly thesame manner so they have no discrimination between primary and secondary pair volumes (theyjust know the near and far disk in a pair). Thus, the takeover command, when activated by acontrol script, must check the combination of attributes of volumes possessed by the local andremote nodes and determine the proper takeover action. The table below shows the takeoveractions.

Table 34 Near/Local and Far/Remote Volume Attributes and Takeover Actions

Takeover actionRemote nodeLocal node (Takeover node)

P-VOL statusVolumeattribute

Fence and statusVolumeattribute

Reject-SMPL-SMPL

Nop-takeover1-P-VOL

Unconformable-S-VOL

Reject-Unknown

Reject-SMPLFence == Data or Status&& pair status == PSUE orPDUB or MINAP == 0

P-VOL(primary)

Unconformable-P-VOL

PVOL-Takeover2-S-VOL

PVOL-Takeover2-Unknown

Reject-SMPLOthers

Unconformable-P-VOL


Table 34 Near/Local and Far/Remote Volume Attributes and Takeover Actions (continued)

Takeover actionRemote nodeLocal node (Takeover node)

P-VOL statusVolumeattribute

Fence and statusVolumeattribute

Nop-takeover1-S-VOL

Nop-takeover1-Unknown

Nop-takeover1--Status == SSWS (AfterSVOL_SSUStakeover)

S-VOL(secondary)

Unconformable-SMPLOther than SSWS

Swap-takeover2PAIR or PFULP-VOL

SVOL-takeover2Others

Unconformable-S-VOL

SVOL-takeover2-Unknown

Notes:1. No action needed to allow local writes.2. Required to allow local writes.

Nop-takeover: No operation is done to allow local writes, though the takeover command isaccepted. Personality swaps must be accomplished in another way.Unconformable: A pair of volumes are not conformable to each other as a pair (that is, oneP-VOL, one S-VOL). The takeover command execution terminates abnormally.Reject: The takeover command is rejected, and the operation terminates abnormally.Unknown: The attribute of the remote node is unknown and cannot be identified. This meansthat the remote node system has gone down or cannot communicate over the LAN.SSWS: Since the SSWS state is referring to a Suspend for Swapping with S-VOL Side only, theSSWS state is displayed as SSUS (SVOL_PSUS) by all commands except the -fc option of thepairdisplay command.

Swap-takeover functionThe P-VOL status at the remote node is PAIR or PFUL (Continuous Access Synchronous Asyncand over high-water mark) and the S-VOL has mirroring consistency. In such a state, it is possibleto swap the primary and secondary volume designations to continue operation. The takeovercommand internally executes the operating commands (explained later) step by step, to swapthe primary and secondary volume designations. Swapping can be specified at the granularityof volume pair, consistency group, or volume group.The swap-takeover function does not use Simplex and No Copy mode for Swapping in order toguarantee mirror consistence more surely, and it is included as a function of SVOL-takeover.1. As the preliminary step of swap-takeover, the command orders a Suspend for Swapping

(SSWS) for the local volume (S-VOL). If this step fails, the swap-takeover function is disabledand it will be returned at an error.

2. The command orders a Resync for Swapping for switch to the primary volume that the localvolume (S-VOL) is swapped as the NEW_PVOL and re-synchronizes the NEW_SVOL basedon the NEW_PVOL. As for the number of simultaneous copy tracks, if the remote host isknown then the command will use the value of P-VOL specified at paircreate time, else


(remote host is Unknown) the command will use a default of 3 as the number of tracks forResync for Swapping.If this step fails, the swap-takeover function will be returned at SVOL-SSUS-takeover, andthe local volume (S-VOL) is maintained in SSUS(PSUS) state which permits WRITE andmaintaining delta data (BITMAP) for the secondary volume. Also this special state is displayedas SSWS state using -fc option of pairdisplay command.

Continuous Access Synchronous Async/Continuous Access Journal specific behaviorfor swap-takeover: The S-VOL side RAID Manager will issue a Suspend for Swapping to theS-VOL side storage system. Non-transmitted data which remains in the FIFO queue (sidefile) ofthe primary volume will be copied to the S-VOL side and a Resync for Swapping operation willbe performed (after the copy process). The Swap operation is required to copy NontransmittedP-VOL data within a given timeout value (specified by the -t <timeout> option).

SVOL-takeover functionThe function makes it so the takeover node alone can use the secondary volume (except inCOPY state) in SSUS(PSUS) state (i.e., reading and writing are enabled), on the assumptionthat the remote node (possessing the primary volume) cannot be used.The data consistency of the secondary volume is judged by its status and fence level. If thischeck proves that data is not consistent, the SVOL-takeover function fails. If this check provesthat data is consistent then this function will try to switch the S-VOL to a primary volume usinga Resync for Swapping, and if it succeeds then this function will return Swap-takeover, else thisfunction will return SVOL-SSUS-takeover as the return value of horctakeover command. In caseof a Host failure, this function will be returned as Swap-takeover. In case of a FICON or P-VOLsite failure, this function will be returned as SVOL-SSUS-takeover. A SVOL-takeover can bespecified by the granularity of a paired logical volume, consistency group, or volume group. If aSVOL-takeover is specified for a volume group, a data consistency check is executed for allvolumes in the group. Inconsistent volumes are picked out and displayed in the execution logfile as shown below:Example:Group Pair vol Port targ# lun# LDEV#...Volstat Status Fence To be...oradb1 ora001 CL1-A 1 5 145...S-VOL PAIR NEVER Analyzedoradb1 ora002 CL1-A 1 6 146...S-VOL PSUS STATUS Suspected

Even so, the SVOL-takeover function enables the secondary volume to be used (i.e., readingand writing are enabled) since it assumes that the remote node (possessing the primary volume)cannot be used.Continuous Access Synchronous Async/Continuous Access Journal specific behaviorfor SVOL-takeover: The S-VOL side RAID Manager will issue a Suspend for Swapping to theS-VOL side storage system. Non-transmitted P-VOL data will be copied to the S-VOL and aResync for Swapping operation will be performed (after the copy process).In case of a Host failure, this data synchronize operation will be accomplished and theSVOL-takeover function will return as Swaptakeover after attempting a Resync for Swapping.In case of a FICON or P-VOL site failure, this data synchronization operation might fail. Even so,the SVOL-takeover function will do Suspend for Swapping, and enable the secondary volumeto be used.


As a result, this function will return as SVOL-SSUS-takeover. Through this behavior, you will beable to judge that non-transmitted data of the primary volume was not transmitted completelywhen a SVOL-takeover returns SVOL-SSUS-takeover.

CAUTION: The SVOL-takeover operation is required to copy Nontransmitted P-VOL datawithin 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 toa SSWS state), the horctakeover command will fail with EX_EWSTOT. If the horctakeover hasfailed due to a timeout then you need to try for a recovery as shown below.

• Wait until the S-VOL state becomes SSWS' via pairdisplay -g <group> -l -fc command, andtry to the start-up again for the HA Control Script.

• Make an attempt to re-synchronize the original P-VOL based on the S-VOL using pairresync-g <group> -swaps -c <size> for a Fast Failback operation.If this operation fails with [EX_CMDRJE] or [EX_CMDIOE], this is due to a FICON link downor site failure. After a recovery from the failure, perform the operation again.

Therefore this timeout value should be a greater than (or equal) to the start-up timeout value forthe MC & CC Control Script.

PVOL-takeover functionA PVOL-takeover relinquishes the pair state for a volume or group in order to make the P-VOLwritable following some type of error (for example, link down with DATA fence). This functionmakes it so the takeover node alone can use the primary volume (that is, reading and writing areenabled), on the assumption that the remote node (possessing the secondary volume) cannotbe used.The PVOL-takeover function has two functions: PVOL-PSUE-takeover, and PVOL-SMPL-takeover.A PVOL-PSUE-takeover forces the primary volume to suspend (PSUE, PSUS) state whichpermits WRITEs to all primary volumes of the group (even if the fence level is data). ThereforePSUE and/or PSUS are intermingled in the volume group through the action of thisPVOL-PSUE-takeover. This intermingled pair status creates PSUE as the group status, thereforethe pairvolchk command results give precedence to PSUE (PDUB) status over PSUS for thegroup.This special state returns back to its original state by issuing the pairresync command. APVOL-SMPL-takeover forces the primary volume to simplex (SMPL) state so the pair is destroyed.At first, PVOL-takeover executes PVOL-PSUE-takeover. If PVOL-PSUE-takeover fails, it thenexecutes PVOL-SMPL-takeover. PVOL-takeover can be specified per paired logical volume orper volume group.Continuous Access Synchronous Async/Continuous Access Journal specific behaviorfor PVOL-takeover: PVOL-takeover will not be executed. It will become a Nop-Takeover, sincethe fence level will be Async which is equal to Never so it is not needed to allow P-VOL writes.

Continuous Access Synchronous remote commandsFigure 56 (page 183) illustrates a Continuous Access Synchronous remote configuration. TheRAID Manager Continuous Access Synchronous remote commands assist the system operationwith volume backups among UNIX servers and their operating system management functions.The Continuous Access Synchronous remote pair commands are also used to copy volumes in


server failover configurations and to restore the volumes to their original state after a serverfailover has been recovered.

• Pair creation command: Creates a new volume pair. Volume pairs can be created in unitsof volume or group.

• Pair splitting command: Splits a volume pair and allows read and write access to thesecondary volume.

• Pair resynchronization command: Resynchronizes a split volume pair based on the primaryvolume. The primary volume remains accessible during resynchronization.

◦ Swaps(p) option (Continuous Access Synchronous only). Swaps volume from theS-VOL(P-VOL) to the P-VOL(S-VOL) when the S-VOL(P-VOL) is in the suspendedstate and resynchronizes the NEW_SVOL based on the NEW_PVOL. At the result ofthis operation, the volume attributes of the host of reference (local host) are used asthe attributes for the NEW_PVOL(SVOL).

• Event waiting command: Used to wait for the completion of volume pair creation orresynchronization and to check the pair status.

• Pair status display and configuration confirmation command: Displays the pair status andconfiguration of the volume pairs and is used for checking the completion of pair creation orpair resynchronization.

Figure 56 Continuous Access Synchronous remote system configuration

Legend

• HORCM: The manager is a demon process, executes multiple commands, charges to astorage system through itself. Among the managers are connected by UDP, remotely executea command among the servers mutually.

• Command: A command provisioned by RAID Manager.


Continuous Access Synchronous local commandsFigure 57 (page 184) illustrates a Continuous Access Synchronous local configuration. The RAIDManager Continuous Access Synchronous local commands assist the system operation withvolume backups among UNIX servers and their operating system management functions. TheContinuous Access Synchronous local commands perform the same functions as the remotecommands but within the same RAID storage system instead of between two RAID storagesystems.

Figure 57 Continuous Access Synchronous local system configuration

Continuous Access Synchronous, Business Copy, and Continuous AccessJournal operationsContinuous Access Synchronous/Business Copy volumes

Continuous Access Synchronous commands allow you to create volume pairs consisting of oneprimary volume (P-VOL) and one secondary volume (S-VOL). The Continuous AccessSynchronous P-VOL and S-VOL can be in different storage systems. Continuous AccessSynchronous provides synchronous and asynchronous copy modes. Continuous AccessAsynchronous can only be used between separate storage systems (not within one storagesystem). For details on Continuous Access Synchronous specifications, volumes and operations,please see the HP P9000 Continuous Access Synchronous User Guide for your storage system.Business Copy commands allow you to create volume pairs consisting of one P-VOL and up tonine S-VOLs using the Business Copy cascade function. Business Copy pairs are containedwithin the same storage system and are maintained using asynchronous update copy operations.For details on Business Copy specifications volumes and operations, please see the HP P9000Business Copy User Guide for your storage system.Each volume pair that you want to create must be registered in the RAID Manager configurationfile. Business Copy volume pairs must include a MU (mirrored unit) number assigned to theS-VOL. The MU number indicates that the pair is a Business Copy pair and not a ContinuousAccess Synchronous pair. Once the correspondence between the paired logical volumes has


been defined in the HORCM_DEV section of the configuration file, you can use the configurationfile to group the paired volumes into volume groups that can be managed by the host operatingsystem's LVM (logical volume manager).The host's LVM allows you to manage the Continuous Access Synchronous/Business Copyvolumes as individual volumes or by volume group. Continuous Access Synchronous/BusinessCopy commands can specify individual logical volumes or group names. For LUSE volumes,you must enter commands for each volume (LDEV) within the expanded LU. If you define volumegroups and you want to issue commands to those volume groups, you must register the volumegroups in the configuration file. For further information about the server LVM, see the userdocumentation for your corresponding operating system.

Continuous Access Synchronous/Business Copy/Continuous Access Journal pairstatus

Each Continuous Access Synchronous pair consists of one P-VOL and one S-VOL, and eachBusiness Copy pair consists of one P-VOL and up to nine S-VOLs when the cascade functionis used. Table 35 (page 185) lists and describes the Continuous Access Synchronous and BusinessCopy pair status terms. Table 36 (page 186) lists and describes the Continuous Access Journalpair status terms. The P-VOL controls the pair status for the primary and secondary volumes.The major pair statuses are SMPL, PAIR, PSUS/PSUE, and COPY/RCPY. Read and writerequests from the host are accepted or rejected depending on the pair status of the volume.The pair status can change when a RAID Manager command is executed. The validity of thespecified operation is checked according to the status of the volume (primary volume).

• Table 37 (page 187) shows the relationship between pair status and Continuous AccessSynchronous/Continuous Access Journal command acceptance.

• Table 38 (page 188) shows the relationship between pair status and Business Copy commandacceptance.

• Table 39 (page 189) shows the relationship between pair status and Snapshot commandacceptance.

For details on pair status of Continuous Access Synchronous MF, Business Copy MF, andContinuous Access Journal MF, see “Pair operations with mainframe volumes” (page 99).

Table 35 Continuous Access Synchronous and Business Copy pair status

SecondaryPrimaryBusiness Copy Pair StatusContinuousAccessSynchronousPairStatus

Status

R/W enabledR/W enabledUnpaired volumeUnpaired volumeSMPL

R enabledR/W enabledPaired volume. Initial copy is complete.Updates are processed asynchronously.

Paired volume. Initial copy is complete.Updates are processed synchronouslyor asynchronously.

PAIR

R enabledR/W enabledIn paired state, but initial copy, pairsplit,or resync operation is not complete.

In paired state, but initial copy, pairsplit,or resync operation is not complete.

COPY

Includes COPY(PD), COPY(SP), andCOPY(RS) status.

Includes COPY(PD), COPY(SP), andCOPY(RS) status.

R enabledR enabledIn paired state, but reverse resyncoperation is not complete. IncludesCOPY(RS-R) status.

Not used for Continuous AccessSynchronous

RCPY

R/W enabledwhen using

R/W enabledIn paired state, but updates to the S-VOLdata are suspended due to

In paired state, but updates to the S-VOLdata are suspended due to

PSUS(split)

write enablepairsplit option

user-requested pairsplit. The RAIDstorage system keeps track of P-VOLand S-VOL updates while the pair is split.

user-requested pairsplit. The RAIDstorage system keeps track of P-VOLand S-VOL updates while the pair is split.

SSUS(split)

Continuous Access Synchronous, Business Copy, and Continuous Access Journal operations 185

Table 35 Continuous Access Synchronous and Business Copy pair status (continued)

SecondaryPrimaryBusiness Copy Pair StatusContinuousAccessSynchronousPairStatus

Status

R enabledR/W enabled ifno error

In paired state, but updates to the S-VOLvolume data are suspended due to an

In paired state, but updates to the S-VOLdata are suspended due to an error

PSUE(error)

occurs in theerror condition. When a PSUE pair iscondition. (PSUE is PSUS due to internalerror. PFUS is PSUS due to sidefile full.)

orPFUS primary

volumeresynchronized, the RAID storagesystem copies the entire P-VOL to theS-VOL (same as initial copy).

R enabledR/W enabled ifno error

Not used for Business CopyUsed only for Continuous AccessSynchronous LUSE pairs. In paired state,

PDUB

occurs in thebut updates to one or more LDEVs withinprimaryvolume

the LUSE pair are suspended due to anerror condition.

Table 36 Continuous Access Journal pair status

SecondaryPrimaryContinuous Access Journal Pair StatusStatus

R/W enabledR/W enabledUnpaired volumeSMPL

R enabledR/W enabledThe pair is synchronized. Updates to the P-VOL are duplicated onthe S-VOL.

PAIR

R enabledR/W enabledIn paired state, but initial copy, pairsplit, or resync operation is notcomplete. Includes COPY(PD), COPY(SP), and COPY(RS) status.

COPY

R/W enabled whenusing write enablepairsplit option

R/W enabledThe user has split the pair or released the pair; the pair is no longersynchronized.

PSUS(split)SSUS(split)

• The primary and secondary systems keep track of journal datadiscarded during the pairsplit operation.

• When the operation is performed at the primary system, thestatus of both the P-VOL and S-VOL changes to PSUS.

• When the operation is performed at the secondary system, thestatus of the S-VOL changes to PSUS; the primary systemdetects this (if path status is normal) and changes P-VOL statusto PSUS.

• When a pair is released from the secondary system, thesecondary system changes the status of the S-VOL to SMPL.The primary system detects this (if path status is normal andchanges P-VOL status to PSUS. (The pair must be releasedfrom the primary system to change P-VOL status to SMPL.)

R enabledR/W enabled if noerror occurs in theprimary volume

The pair is suspended due to an error; the pair is not synchronized.PSUE

• The primary and secondary systems keep track of any journaldata that are discarded during the suspension operation.

• The primary system keeps track of P-VOL tracks that are updatedwhile the pair is suspended.

• When a Cnt Ac-J suspension condition is detected, the primarysystem changes P-VOL and S-VOL status to PSUE. If thesecondary system detects the condition, it changes the S-VOLstatus to PSUE; the primary system detects this and changesP-VOL status to PSUS.

Read Only, unlesswrite option is enabled.

R/W enabledIf the Data Overflow Watch period is exceeded, pair status changesfrom PFUL to PFUS, and the pair is suspended.

PFUS

• The PFUS status is displayed by RAID Manager and RemoteWeb Console as PSUS.

• If a virtual volume of Thin Provisioning (THP-VOL) is used as aCnt Ac-J S-VOL, and the capacity of a pool-VOL is nearly full,Cnt Ac-J status becomes PFUS and the pair is suspended.


Table 36 Continuous Access Journal pair status (continued)

SecondaryPrimaryContinuous Access Journal Pair StatusStatus

R/W enabledR enabledAfter Takeover, SSWS is the status of the S-VOL. With this status,data can be written to the S-VOL.

SSWS

• SSWS is displayed by RAID Manager, from which the horctakovercommand is issued.

• Remote Web Console displays this status as PSUS or PSUE.

R enabledR/W enabledIf data in the journal volume exceeds 80%, pair status changes toPFUL. The write data that inflows then is monitored during the DataOverflow Watch.

PFUL

PFUL status is displayed by RAID Manager. Remote Web Consoledisplays this status as PAIR.

Table 37 Pair status versus Continuous Access Synchronous/Continuous Access Journalcommands

Continuous Access Synchronous/Continuous Access Journal command-

pairresyncpairsplitpaircreate

Resync-S option-P option-r or -rw optionNocopyCopyStatus#

RejectedAcceptableRejectedRejectedAccepted 3Accepted 2SMPL1

AcceptableAccepted 1RejectedAccepted 4AcceptableAcceptableCOPY2

AcceptableAccepted 1Accepted 4Accepted 4AcceptableAcceptablePAIR3

Accepted 2*Accepted 1AcceptableAcceptableRejectedRejectedPSUS4

Accepted 2*Accepted 1AcceptableAcceptableRejectedRejectedPSUE5

Accepted 2*Accepted 1RejectedRejectedRejectedRejectedPDUB6

Legend:Accepted = Accepted and executed. When the operation terminates normally, the status changes to the indicated number.Acceptable = Accepted but no operation is executed.Rejected = Rejected and operation terminates abnormally.

Pairsplit of a Continuous Access Synchronous Async volume is returned after verification of statetransition that waits until delta data is synchronized from P-VOL to S-VOL.

NOTE: In the case of the SSWS status after SVOL-SSUS-takeover execution, the pairresynccommand (from P-VOL to S-VOL) is rejected because the delta data for S-VOL becomes dominant,and its status is expected to be using the -swaps(p) option of pairresync. If the pairresynccommand (from P-VOL to S-VOL) is rejected, confirm this special status using the -fc option ofthe pairdisplay command.

The following table shows the relation of command acceptances for paired status and BusinessCopy.


Table 38 Pair status versus Business Copy commands

Business Copy command-


Resync-S option-C option-E option-splitNo -splitPair Status

RejectedAcceptableRejectedRejectedAccepted 2 to 4Accepted 2SMPL1

AcceptableAccepted 1Accepted [1] 2to 4

Accepted 5Accepted [1] 2to 4

AcceptableCOPYRCPY

2

AcceptableAccepted 1Accepted [2] 2to 4

Accepted 5Accepted [2] 2to 4

AcceptablePAIR3

Accepted 2Accepted 1AcceptableAccepted 5AcceptableRejectedPSUS4

Accepted 2Accepted 1AcceptableAcceptableAcceptableRejectedPSUE5

Legend:Accepted = Accepted and executed. When the operation terminates normally, the status changes to the indicated number.Acceptable = Accepted but no operation is executed.Rejected = Rejected and operation terminates abnormally.

In the following descriptions, when the pair statuses of P-VOL and S-VOL are different, PVOL_or SVOL_ are applied to show which volume is indicated.

NOTE: If the P-VOL does not have Write in the PAIR state, then data identical with an S-VOLis guaranteed. Therefore, when using the S-VOL with the SMPL state, after stopping Write tothe P-VOL, generate a paired volume, and then split the paired volume after confirming that thepaired volume has the PAIR status. In the PSUE state, Business Copy does not managedifferential data at the P-VOL or S-VOL. Therefore, pairresync issued to a pair in the PSUEstate is all copy performance, but the copy progress rate returned by the -fc option of thepairdisplay command indicates "0%".[1]:The (2 to 4) state change is effective for only the COPY state that is changed withoutspecification of -split for paircreate command.[2]:The (2 to 4) state change appears as P-VOL_PSUS & S-VOL_COPY (see example below),and reading and writing are enabled for S-VOL in SVOL_COPY state.

# pairsplit -g oradb

# pairdisplay -g oradb -fcGroup PairVol(L/R) (Port#,TID,LU-M), Seq#, LDEV#.P/S, Status, % , P-LDEV# M

oradb oradev3(L) (CL2-N , 3, 4-0) 8071 28..P-VOL PSUS, 100 29 W

oradb oradev3(R) (CL2-N , 3, 5-0) 8071 29..S-VOL COPY, 97 28 -

PVOL_PSUS & SVOL_COPY is the non-reflected PSUS state that data is still being copied fromthe P-VOL to the S-VOL, and this state has the following specific behavior.

• If you attempt to read non-reflected data on S-VOL in PVOL_PSUS & SVOL_COPY state,then Business Copy copies non-reflected data from P-VOL to S-VOL, and returns the correctdata after copied. This will bring the performance degradation (1/6 to 1/15 with IOPS) toread on the S-VOL.

• If you attempt to write non-reflected data on S-VOL in PVOL_PSUS & SVOL_COPY state,then Business Copy copies non-reflected data from P-VOL to S-VOL, and writing data ismanaged as delta data for S-VOL after copied. This will bring the performance degradation(1/6to 1/8 with IOPS) to write on the S-VOL.

• If you attempt to write to the data on P-VOL that does not still reflected the data to S-VOL,then Business Copy copies non-reflected data from P-VOL to S-VOL, and writing data is


managed as delta data for P-VOL. This will bring the performance degradation(1/6 to 1/8with IOPS) to write on the P-VOL.

• The state changes for pairsplit are (WD = Write Disable, WE = Write Enable):If P-VOL has non-reflected data in PAIR state:

Behavior of first pairsplit at T0Behavior of OLD pairsplit at T0PVOL_PAIR from/to SVOL_PAIR(WD)T0: PVOL_PAIR from/to SVOL_PAIR(WD)PVOL_PSUS from/to SVOL_COPY(WE)T1: PVOL_COPY from/to SVOL_COPY(WD)PVOL_PSUS from/to SVOL_SSUS(WE)T2: PVOL_PSUS from/to SVOL_SSUS(WE)

If P-VOL has been reflected all data to S-VOL in PAIR state:

Behavior of First pairsplit at T0Behavior of OLD pairsplit at T0PVOL_PAIR from/to SVOL_PAIR(WD)T0: PVOL_PAIR from/to SVOL_PAIR(WD)PVOL_PSUS from/to SVOL_SSUS(WE)T1: PVOL_PSUS from/to SVOL_SSUS(WE)

• The state changes for paircreate -split are:

Behavior of First paircreate -split at T0Behavior of OLD paircreate -split at T0SMPL from/to SMPLT0: SMPL from/to SMPLPVOL_PSUS from/to SVOL_COPY(WE)T1: PVOL_COPY from/to SVOL_COPY(WD)PVOL_PSUS from/to SVOL_SSUS(WE)T2: PVOL_PSUS from/to SVOL_SSUS(WE)

• If you attempt the pairevtwait -s psus in PVOL_PSUS & SVOL_COPY state, thenpairevtwait will return immediately even if the S-VOL is still in SVOL_COPY state becauseP-VOL is already in PVOL_PSUS state. If you want to wait the "SVOL_SSUS" state, andthen you must check the status of the S-VOL becomes "SVOL_PSUS" via the return codeusing pairvolchk -ss command on S-VOL side or pairvolchk -ss -c command on P-VOLside. Or you can use pairevtwait -ss ssus on both P-VOL and S-VOL, pairevtwait -ssssus -l on S-VOL locally.

• If you attempt the pairresync -restore or pairsplit -S in PVOL_PSUS & SVOL_COPY state,then Business Copy will reject this command due to unable to perform. In this case, youneed to wait until the S-VOL state becomes SVOL_SSUS.

Table 39 Pair status versus Snapshot commands

Snapshot CommandPair Status


Resync-S option-C option-E option-splitNo -split

RejectedAcceptableRejectedRejectedRejectedAccepted 2SMPL1

AcceptableRejectedRejectedRejectedRejectedAcceptableCOPYRCPY

2

AcceptableAccepted 1Accepted 4RejectedAccepted* 4AcceptablePAIR3

Accepted* 2Accepted 1AcceptableRejectedAcceptableRejectedPSUS(PFUS)

4

Accepted* 2Accepted 1RejectedAcceptableRejectedRejectedPSUE5

Accepted*: A command is accepted and issued; whether this command is executed or not depends on the microcode versionof the RAID storage system.


NOTE:• pairsplit ("simplex -S") of Snapshot volume is returned without verification of state transition

that waits until SMPL state. In SMPL state, the volume that was S-VOL becomes R/Wdisable and data is discarded.

• In the "PSUE" state, Snapshot does not manage for differential data between the primaryvolume and secondary volume.

Continuous Access Asynchronous, Continuous Access Synchronous, ContinuousAccess Journal, and High Availability volumes

Continuous Access Asynchronous, Continuous Access Journal, and High Availability providepaired volumes that use asynchronous transfer to ensure the sequence of writing data betweenthe primary volume and secondary volume. The sequence of writing data between the primaryand secondary volumes is guaranteed within each consistency (CT) group (see Figure 58(page 190)).

Figure 58 Continuous Access Asynchronous consistency groups

Restrictions

• Group definition of Continuous Access Asynchronous/Continuous Access Journal/ContinuousAccess Synchronous/High Availability volume: All volumes in a group must be containedwithin the same storage system. If two or more groups of RAID Manager include the sameconsistency group (CTG ID), then pair operation of the group specification is handled inconsistency group entirety.

• Registration of CTG ID number and limitations: RAID Manager registers CTG ID to RAIDdisk array automatically when paired volumes are created by paircreate command, and


groups of configuration definition files are mapped to CTG ID. The maximum number ofconsistency groups is as follows:

◦ P9500, XP24000/XP20000 Disk Array, and XP12000 Disk Array/XP10000 Disk Array:256 (CTG ID 0 - CTG ID 255)

◦ XP1024/XP128 Disk Array: 128 (CTG ID 0 - CTG ID 127)

Continuous Access Synchronous Async/Continuous Access Journal/High Availability paircommand is terminated with EX_ENOCTG when the maximum number of consistencygroups is exceeded.

• Relationships between CTG ID and Journal ID: The consistency group numbers from 0to 127 are assigned to Continuous Access Asynchronous and Continuous AccessSynchronous, and from 0 to 255 are assigned to Continuous Access Journal and HighAvailability. The consistency group numbers for Continuous Access Journal are mapped tothe journal.

Table 40 Assignment of consistency group IDs (CTG IDs)

AssignmentCTG ID

CTG 0-127Continuous Access Asynchronous0 -127Continuous Access Synchronous

CTG 0-127Continuous Access JournalHigh Availability

CTG 128-255Continuous Access Journal128 - 255High Availability

• At-time Split for Continuous Access Synchronous: The operation for making dataconsistency is only supported by the following option:pairsplit -g <group> ... [-r]

pairsplit -g <group> ... -rw

Continuous Access Asynchronous and Continuous Access Journal volume characteristicsContinuous Access Asynchronous/Continuous Access Journal volumes have the followingcharacteristics:

• PAIR state: A Continuous Access Asynchronous pair changes to the PAIR status as soonas all pending recordsets have been placed in the queue at the primary volume, withoutwaiting for the updates to complete at the secondary volume.

• Pair splitting:When a Continuous Access Asynchronous pair is split or deleted, all pendingrecordsets at the primary volume are sent to the secondary volume, then the pair statuschanges to PSUS or SMPL. With the pairsplit command only, updates for the primaryvolume that occur during and after the pairsplit operation are marked on the bitmap of theprimary volume.

• Pair resynchronization: The pairresync command resynchronizes the secondary volumebased on the primary volume. This resynchronization does not guarantee the sequenceddata transfer.

• Error suspending: Pending recordsets that have not yet been sent to the secondary volumeare marked on the bitmap of the primary volume, then deleted from the queue, and then thepair status changes to PSUE.

• Group operations: Continuous Access Asynchronous automatically registers the CTG IDswith the storage system when paired volumes are created using the paircreate command,


and groups in the configuration file are mapped to their corresponding CTG IDs. If morethan one group, defined in the configuration definition file, is assigned to the same CTG ID,then pair operations on the group specificity apply to the entire consistency group.

Sidefile cache for Continuous Access AsynchronousThe first-in-first-out (FIFO) queue of each consistency group is placed in an area of cache calledthe sidefile. The sidefile is used for transferring Continuous Access Asynchronous recordsets tothe RCU. The sidefile is not a fixed area in cache but has variable capacity for write I/Os for theprimary volume. If the host write I/O rate is high and the MCU cannot transfer the ContinuousAccess Asynchronous recordsets to the RCU fast enough, then the sidefile capacity expandsgradually. The sidefile has a threshold to control the quantity of data transfer of host side writeI/O. Host side write I/Os are controlled by delaying response when the sidefile exceeds theconstant quantity limit on cache in the storage system (see Figure 59 (page 192)).

Figure 59 Sidefile quantity limit

Sidefile area: Sidefile area = 30% to 70% of cache as set on Remote Web Console (defaultsidefile = 50% for XP24000/XP20000 Disk Array, XP1024/XP128 Disk Array; 40% for XP12000Disk Array/XP10000 Disk Array).Write I/O control via the high-water mark (HWM): When the quantity of data in the sidefile reaches30% of cache, the Continuous Access Asynchronous pair status is HWM of PAIR state, and thehost write I/Os receive a delayed response in the range of 0.5 seconds to 4 seconds. Followingis an arithmetic expression of the HWM at 100% of a sidefile space:HWM(%) = High water mark(%) / Sidefile threshold (30 to 70) * 100Write I/O control via the sidefile threshold: When the quantity of data in the sidefile occupies themaximum defined sidefile area, host write I/Os are delayed until there is enough sidefile spaceto store the next new write data. The copy pending timeout group option is defined using RemoteWeb Console and specifies the maximum delay between the M-VOL update and the correspondingR-VOL update. The range for the copy pending timeout option is 1-255 seconds (600 secondsfor Continuous Access Journal), and default value is 90 seconds (60 seconds for Cnt Ac-J). Ifthe timeout occurs during this wait state, the pair status changes from PAIR to PSUS (sidefilefull), and host write I/Os continue with updates being managed by the cylinder bitmap. Important:The copy pending timeout value should be less than the I/O timeout value of the host system.

Continuous Access Asynchronous transition states and sidefile controlContinuous Access Asynchronous volumes have special states for sidefile control during statustransitions. Table 41 (page 193) shows the transition states for Continuous Access Synchronousand Continuous Access Asynchronous volumes.The suspending and deleting states are temporary internal states within the RAID storage system.RAID Manager cannot detect these transition states, because these states are reported on theprevious state of the storage system. These states are therefore concealed inside the pairsplitcommand. After the pairsplit command is accepted, host write I/Os for the P-VOL are managedby the cylinder bitmap (normal), non-transmitted data remaining in the P-VOL's FIFO queue is


transferred to the S-VOL's FIFO queue, and the pair status is then set to PSUS [SMPL] statewhen all data in the P-VOL's FIFO queue has been transmitted.PFUL. If the quantity of data in sidefile cache exceeds 30% of cache storage, the internal statusof the RAID storage system is PFUL, and host write I/Os receive delayed response in the rangeof 0.5 seconds (minimum) to 4 seconds (maximum).PFUS. If the quantity of data in sidefile cache exceeds the user-defined sidefile area (30%-70%),then host write I/Os must wait for enough sidefile space to become available for storing the nextnew write data. If a copy pending timeout occurs during this waiting state, then the pair statuschanges from PAIR to PFUS, host write I/Os are accepted, and write data is managed by bitmap.The RAID Manager software can detect and report the PFUL and PFUS states as follows:

• As a return code of the pairvolchk command

• As the status code displayed to code item by the pairmon command

• As the paired status displayed to status item using -fc option of pairdisplay command

Table 41 State table for Continuous Access Synchronous vs. Continuous Access Asynchronous

Transferdata viaESCON

Writing control on Cnt Ac-Sasync volume

DescriptionDisk arrayinternal state

RAIDManagerstate

ResponseWriting dataContinuous AccessAsynchronous

ContinuousAccessSynchronous

NoneUsualNormalSameSMPLSMPLSMPL

Sidefile &bitmap

Usual*Via SidefileSameCOPYCOPYCOPY

SidefileUsualNormalDeleting from COPY using [pairsplit-S]

N/ADeleting

SidefileUsualVia BitmapSuspending from COPY by using[pairsplit]

N/ASuspending

SidefileUsualVia SidefileLess than HWMAsync sidefilein use

SynchronizedPAIRPAIR

SidefileDelayedVia SidefileHWM toThreshold

N/APFUL

SidefileWait untilunderthreshold

Via SidefileOver Threshold

SidefileUsualNormalDeleting from PAIR using [pairsplit-S]

N/ADeleting

SidefileUsualVia BitmapUsing [pairsplit ]Suspendingfrom PAIR

N/ASuspending

Timeout of overthreshold

NoneUsualVia BitmapSamePSUSPSUSPSUS

NoneUsualVia BitmapTimeout Over ThresholdNonePFUS

NoneUsualVia BitmapSame (link down, etc.)PSUEPSUEPSUE

NoneUsualVia BitmapSamePDUBPDUBPDUB

* If the host has more write I/Os in COPY state, then host write I/Os are delayed until there is enough space in the sidefile.Legend:Bitmap: Host write data is managed via a cylinder BITMAP of delta data.Normal: Host write data is not managed by BITMAP or sidefile.


Table 41 State table for Continuous Access Synchronous vs. Continuous Access Asynchronous(continued)

Transferdata viaESCON

Writing control on Cnt Ac-Sasync volume

DescriptionDisk arrayinternal state

RAIDManagerstate

ResponseWriting dataContinuous AccessAsynchronous

ContinuousAccessSynchronous

Usual: Host side writing response is not delayed.HWM (High Water Mark): Sidefile quantity is over 30% of cache storage.

Continuous Access Asynchronous/Continuous Access Journal error stateIn the case of an ESCON or fibre-channel (FC) failure, the S-VOL FIFO queue is missing a datablock that was transferred from the P-VOL FIFO queue. The RCU waits to store the nextsequenced data block in the S-VOL FIFO queue until the Continuous Access Asynchronous copypending timeout occurs (defined using Continuous Access Synchronous). In addition, the timeoutvalue can be specified at Remote Web Console. The default value is set to 5 minutes. If thetimeout occurs during this waiting state, the pair status changes from PAIR to PSUE, andnon-sequenced data blocks are managed by the S-VOL bitmap. The missing data block can berecovered using the pairresync command, which merges the S-VOL bitmap with the P-VOLbitmap. Figure 60 (page 194) shows this situation on the secondary side.

Figure 60 Continuous Access Asynchronous suspension condition

Continuous Access Synchronous/Continuous Access Asynchronous and ContinuousAccess Journal/High Availability fence level settings

Continuous Access Synchronous volume pairs are assigned a fence level for write I/Os to ensuremirroring consistency of critical volumes. When the secondary volume takes over from the primaryvolume, the takeover action is determined according to the pair status and fence level of thecorresponding secondary volume. Table 42 (page 195) shows the relationship between ContinuousAccess Synchronous pair statuses and fence levels.


The fence level for Continuous Access Synchronous is Data, Status, Never. The fence level forContinuous Access Asynchronous and Continuous Access Journal is always Async. The fencelevel for High Availability is always Never.

• Mirror consistency = Identity and sequence of data is assured via error notification after anI/O completion.

• Data consistency = Sequence of data is assured in I/O order based on host.

Table 42 Relationship between Continuous Access Synchronous pair statuses and fence levels

Fence level and write responseContinuous Access Synchronous pair statusof volume

Async [4]Never [3]Status [2]Data [1]

OKOKOKOK

Data consistencyassured

Mirroringconsistencyassured



OKOKOKERROR


Mirroringconsistency notassured



OKOKERRORERROR





[1] When the fence level is data: Mirroring consistency is assured, since a write error is returned if mirror consistency with theremote S-VOL is lost. The secondary volume can continue operation, regardless of the status. Note: A P-VOL write thatdiscovers a link down situation will, in addition to returning an error to the host, likely be recorded on [only] the P-VOL side.

[2] When the fence level is status: If there is a mirror consistency problem (that is, PSUE) and it is possible to set the S-VOLto PSUE, the P-VOL write completes OK. If the S-VOL cannot be set to PSUE for any reason, the P-VOL write completes withan error. The mirror consistency of the S-VOL depends on its status:PSUE: The secondary volume is dubious.PAIR: The secondary volume can continue operation.

[3] When the fence level is never: Writing to the P-VOL is still enabled in the state where mirror consistency to the S-VOL islost, regardless of whether the secondary volume status is updated or not. Thus, the secondary could have these states:PSUE: The secondary volume is dubious.PAIR: The secondary volume is substantially dubious, since it can continue operation and is also dubious. The P-VOL statusmust be checked to confirm the mirroring consistency.

[4] When the fence level is async: Continuous Access Asynchronous/Cnt Ac-J uses asynchronous transfers to ensure thesequence of write data between the P-VOL and S-VOL. Writing to the P-VOL is enabled, regardless of whether the S-VOLstatus is updated or not. Thus the mirror consistency of the secondary volume is dubious (similar to the "Never" fence):

• PSUE: The S-VOL mirroring consistency is not assured, but the PSUE suspended state ensures the sequence of data forthe consistency group; thus, data consistency is also assured during a PSUE state. At a PSUE state, the P-VOL writes still


Table 42 Relationship between Continuous Access Synchronous pair statuses and fence levels(continued)

Fence level and write responseContinuous Access Synchronous pair statusof volume

Async [4]Never [3]Status [2]Data [1]

complete and are also noted in a bitmap for future transfer. Due to the use of a bitmap in the suspend state, data consistencyis not assured during a copy state resync.

• PAIR: If the P-VOL and S-VOL are both in a PAIR state, mirror consistency is not assured (might be behind) but dataconsistency is assured (what has reached the S-VOL is in the proper order).

Setting the fence levelData fence levelFigure 61 (page 196) shows the relationship between redo log files (journal) and data files. If theS-VOL takes over from the P-VOL in the status shown in Figure 61 (page 196) (where two errorshave occurred), the secondary host leaves data (V) unprocessed in the roll-back processing andcannot be recovered completely. Therefore, the fence level of a redo log file must be defined asdata. Once the fence level is set to data, the P-VOL returns an error if data might possibly beinconsistent when a write request is issued by the host. Since writing to the data file is not executeddue to a write error of the redo log file, the log file stays consistent with the data file. However,when the fence level is set to data, a write I/O error occurs even in the case where operation issuspended due to an error in the S-VOL. Accordingly, duplication becomes meaningless whenthe S-VOL takes over. Thus, applications using paired volumes with the data fence level shouldbe able to handle write I/O errors properly. For example, the Oracle application creates multipleredo log files by itself (three by default). The fence level can be set to data in this case in whichdisk errors are permissible by creating multiple files.

Figure 61 Relationship between logs (journal) and data in paired status

Never fence levelBecause most UNIX file systems (excluding JFS and VxFS) have no journal files, the fence levelshould be defined as Never. When a takeover by the S-VOL occurs, fsck is executed on thevolume and the file system is cleaned up, even if the S-VOL is undefined at the secondary host.The data that is lost depends on how much differential data is contained in the P-VOL when theS-VOL is suspended. During operation, error recovery should be performed when the suspendedstatus (PSUE or PDUB) is detected (when one error occurs).

Snapshot operationsSnapshot normally creates virtual volumes for copying on write without specifying LUNs asS-VOLs. However, to use a Snapshot volume via the host, it is necessary to map the SnapshotS-VOL to a LUN. Therefore, RAID Manager provides a combined command to enable the useror application to use the same RAID Manager command in order to maintain Business Copycompatibility.Snapshot uses two techniques, one called "V-VOL mapping" (or virtual volume mapping) andthe other is "Snapshot using copy on write" or "Copy-on-write snapshot." Snapshot volumes arealso put into pooling volumes called a "Snapshot pool," and a Snapshot pool is specified as a


pool ID when a Snapshot is made. Snapshot and volume mapping is illustrated in Figure 62(page 197).

Figure 62 Snapshot and volume mapping

Snapshot volumesThe specifications for Snapshot volumes are:

• Allowable type of paired volume: The supported volume type is OPEN-V only for P VOL,and OPEN-0V for S VOL.

• Number of volumes (Snapshot) can be paired: This depends on P VOL capacity, Snapshotpool capacity, and shared memory capacity on the RAID storage system.

• Duplicated writing mode: Copying on write.

• Number of mirror volumes:

Fast Snap: Up to 1,024 secondary volumes can be defined for each P VOL.◦◦ Snapshot: Up to 64 secondary volumes can be defined for each P VOL.

For details on Fast Snap or Snapshot specifications such as maximum number of mirroredvolumes, volumes and operations, please see theHP P9000 Fast Snap User Guide orHP P9000Snapshot User Guide for your storage system.

Pair operations and commands for Snapshot and Fast SnapThe following table shows the pair operations and commands that can be used for Snapshot andFast Snap pairs.

Fast Snap (cascade pairs,pairs with the clone attribute)

Fast SnapSnapshotCommand

NoYes*Yespaircreate

NoYes*Yespairsplit

Snapshot operations 197

Fast Snap (cascade pairs,pairs with the clone attribute)

Fast SnapSnapshotCommand

NoYes*Yespairresync

NoYes*Yespaireventwait

NoYes*Yespairmon

NoYes*Yespairvolchk

NoYes*Yespairdisplay

NoYes*Yesraidscan

YesYesNoraidcom

*The MU numbers that can be used and referenced are from 0 to 63.

Creating a Snapshot pairThe RAID Manager command for creating a Fast Snap or Snapshot pair is the same as forBusiness Copy. However, Fast Snap pair can only operate up to 64 S-VOLs. Therefore, useraidcom command if you want to operate more than 64 S-VOLs.The RAID storage system determines whether it is a Business Copy pair or a Fast Snap/Snapshotpair by the attribute of the S-VOL. The RAID storage system also determines whether it is a FastSnap pair or a Snapshot pair by the type of the pool to be used.A Fast Snap pair is generated in the following two cases:

• When a V-VOL (OPEN-0V) is specified as an S-VOL.

• When a pool for Fast Snap is specified as the pool type.A 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 Snapshot is specified as the pool type.A V-VOL has the following characteristics:

• It appears as "OPEN-0V" to identify a V-VOL easily via the SCSI Inquiry or RAID Manager.

• A V-VOL unmapped to the S-VOL of a Snapshot will reply to a SCSI Inquiry, but Readingand/or Writing is not allowed. LDEV will reply the capacity setting as an LU to SCSI ReadCapacity.

• A V-VOL that has become the S-VOL of a Snapshot will reply to a SCSI Inquiry, and Readingand/or Writing is allowed.

Snapshot pair statusEach paired volume consists of a primary volume (P-VOL) and a secondary volume (S-VOL).Each volume has the status for controlling the pair state.The P-VOL controls the pair state that is reflected on the status of the S-VOL. The major pairstatuses are "SMPL", "PAIR", "PSUS", "COPY", and "RCPY". The status is changed when theRAID Manager command is issued. A read or write request from the host is allowed or rejectedaccording to the status.


Table 43 Snapshot Pairing Status

SecondaryPrimaryPairing StatusP-VOLStatus

R/W disable1R/W enabledUnpaired (Snapshot) volumeSMPL

R/W disableR/W enabledThe Snapshot available state allocated the resource.PAIR(PFUL)

R/W disableR/W enabledThe preparing state allocates the resource for the Snapshot.COPY

R/W disableR/W enabledThe copying state from Snapshot to the primary volume byusing restore option.

RCPY

R/W enabledR/W enabledThe differences of the updated data of the primary andsecondary volume are controlled with copying on write.

PSUS(PFUS)

R/W disableR/W enabled2"PSUS" status due to an internal failure. The differences ofthe updated data for the Snapshot volume are not controlled.

PSUE(Error)

Notes:1. V-VOL unmapped to the S-VOL of a Snapshot will reply to a SCSI Inquiry, but Reading and/or Writing is not

allowed.2. Reading and writing are enabled, as long as no failure occurs in the primary volume.

Pair status relationship to Snapshot commandsTable 44 (page 199) applies to a Snapshot context. It explains 1) what a pair status can be priorto any RAID Manager command execution, 2) what the result will be after giving a RAID Managercommand, and 3) what the pair status can be if the RAID Manager command is Accepted.

Table 44 Pair status relationship to Snapshot commands

Snapshot Command-


Resync-S option-C option-E option-splitNo -splitPair Status

RejectedAcceptableRejectedRejectedRejectedAccepted 2SMPL1

AcceptableAccepted 1Accepted*RejectedRejectedAcceptableCOPYRCPY

2

AcceptableAccepted 1Accepted*RejectedAccepted*4AcceptablePAIR3

Accepted*2Accepted 1Accepted*RejectedAcceptableRejectedPSUS(PFUS)

4

Accepted*2Accepted 1RejectedRejectedRejectedRejectedPSUE5

*A command is accepted and issued. Whether this command is executed or not depends on the microcode version of theRAID storage system.

Snapshot operations 199

NOTE:• pairsplit -S of a Snapshot volume is returned without verification of the state transition that

waits until SMPL state. In a SMPL state, note that the volume that was an S-VOL becomesR/W disabled and data is discarded.

• In the "PSUE" state, Snapshot does not manage differential data between the primary volumeand secondary volume.

Controlling Auto LUNAuto LUN, including external volumes, must be controlled using CLI in a Data LifecycleManagement (DLCM) solution. It is possible to support volume migration (Auto LUN function)and the external connection by operating the current Business Copy and VDEV mapping of theexternal connection.Also, it is important to consider the support of Auto LUN on the compatibility based on the currentCLI interface, because RAID Manager is supporting Business Copy and the external connection.For this purpose, RAID Manager makes the CLI interface that works by minimum compatible ofthe application by specifying the COPY mode for Auto LUN to the CLI of RAID Manager.

Specifications for Auto LUNRAID Manager must be mapped to the port for pooling of RAID in order to control the volume ofthe external connection. Therefore, the external volume needs to be mapped previously to theRAID port without connecting to the host. Following is an execution example of the volumemigration executed for LDEV#18.

Figure 63 Auto LUN configurations

(1) Command specificationRAID Manager operates the volume migration by specifying to the horcm*.conf as same BC andCnt Ac-S, because the volume migration using RAID Manager is necessary to be defined themapping for the target volume.MU# (of SMPL as BC) that is not used because BC is used for Auto LUN operation.An original volume for the migration is defined as P-VOL. A target volume for the migration isdefined as S-VOL. In other words, an original volume is migrated from P-VOL to S-VOL, and themapping between LDEV and VDEV is swapped after copied.


(2) Mapping specificationThe mapping between LUN and LDEV is maintained for the replying of SCSI-Inquiry in order tomake recognize as identical LUN through the host after mapping changes.The way to know whether the mapping is changed or not is possible to use "-fe" option ofpairdisplay and/or raidscan command that shows the connection for the external volumes.Also LU of the external connection and LU of RAID Group intermingle on the port for pooling,but can confirm this with the above option of the raidscan command.

(3) Group operationIt is possible to execute the Auto LUN as a group by describing it to the horcm*.conf, howeverLU(LDEV), which was mapped to S-VOL after command execution, does not maintain theconsistency of the group. In other words, you must consider the volume mapped to the S-VOLafter execution as the discarded volume.When HORCM demon is KILLed or the host has crash during group operation, the group abortingthe execution of the command has LUN mixed with the external connection and RAID Group asthe group. In this case, RAID Manager skips the executed LU and issues the CC (Auto LUN)command to the un-executed LU, and an identical command is executed once again.

(4) Using MU#RAID Manager manages the status of Cnt Ac-S/BC using MU#, so RAID Manager uses theempty MU# that is managed for BC. Therefore, execute the command of the volume migrationin the environment for BC having HORCC_MRCF environment variable. An example is shownbelow.

(5) HORCM instanceIt is possible to describe the original and target volume for the volume migration to MU# asanother group in horcm*.conf for HORCM instance of BC and /or Cnt Ac-S. Also, it is possibleto define the original and target volume for the volume migration in the horcm*.conf as HORCMinstance independent from BC/Cnt Ac-S.

Commands to control Auto LUN(1) Command for Auto LUNRAID Manager supports the volume migration by adding an option (-m cc) to the paircreatecommand.paircreate -g <group> -d <pair vol> … -m <mode> -vl[r] -c <size>

-m <mode> mode = cc (can only be specified for Business Copy)This option is used to specify the Auto LUN mode.

NOTE: This option cannot be specified with "-split" option in the same command.

-vl[r]The -vl option specifies "local", and copies from the local instance LU (P-VOL) to the remoteinstance LU (S-VOL), an original volume as the local instance LU is migrated from P-VOL toS-VOL, and the physical volume mapping between P-VOL and S-VOL is swapped after copied

Controlling Auto LUN 201

The -vr option specifies "remote", and copies from the remote instance LU (P-VOL) to the localinstance LU (S-VOL), an original volume as the remote instance LU is migrated from P-VOL toS-VOL, and the physical volume mapping between P-VOL and S-VOL is swapped after copied.-c <size>This option is used to specify a track size of the case that copies paired volume at 1-15 extents.In case of stopping Write to P-VOL and copying in a short time, the maximum value 15 is specified.When this option is omitted, it uses a default value of (3) is used for track size.(2) Command for discovering an external volumeIt is possible to discover the external volumes by using "-fe" option of the raidscan command.raidscan -p <port#> -fe-feThis option is used to display the serial# and LDEV# of the external LUNs only mapped to theLDEV.If the external LUN mapped to the LDEV on a specified port does not exist, then this option willdo nothing.Also if this option is specified, -f[f][g][d] option is not allowed.Display example:# raidscan -p cl1-a-0 -fe -CLI

PORT# /ALPA/C TID# LU# Seq# Num LDEV# P/S Status Fence E-Seq# E-LDEV#

CL1-A-0 ef 0 0 8 62496 1 19 SMPL - - 30053 30

CL1-A-0 ef 0 0 9 62496 1 21 SMPL - - 30053 32

CL1-A-0 ef 0 0 10 62496 1 22 SMPL - - 30053 33

E-Seq#: Displays the production (serial) number of the external LUN. E-LDEV#: Displays theLDEV# of the external LUN.(3) Command for confirming the statusIt is possible to confirm the status for Auto LUN by using "-fe" option of the pairdisplaycommand.pairdisplay -g <group> -fe-feThis option is used to display the serial# and LDEV# of the external LUNs mapped to the LDEVand additional information for the pair volume.This option displays the information above by adding to last column, and then ignores the formatof 80 column.This option is invalid if the cascade options (-m all,-m cas) are specified.Display example:Before execution of Auto LUN command:# pairdisplay -g horc0 -fe

Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#horc0 ... 62496 18.SMPL ---,----- --- - - - - - -

horc0 ... 62496 19.SMPL ---,----- --- - - - H 30053 30

# paircreate -g horc0 -vl -m cc

During execution of Auto LUN command, the progress is displayed in the copy %:# pairdisplay -g horc0 -fe

Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#horc0 ... 62496 18.P VOL COPY,62496 19 - - C - - -

horc0 ... 62496 19.S VOL COPY,----- 18 - - C H 30053 30

After completion of Auto LUN command:


Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV#horc0 ... 62496 18.P VOL PSUS,62496 19 - - C V 30053 30horc0 ... 62496 19.S VOL SSUS,----- 18 - - C - - -

CM: Displays the copy mode N: Non Snapshot S: Snapshot. For SMPL state, this shows thatpair-volume will be created as Snapshot. C: Auto LUNEM: Displays the external connection modeH: Mapped E-lun as hidden from the host. V: MappedE-lun as visible to the host ' - ': Unmapped to the E-lun BH: Mapped E-lun as hidden from thehost, but LDEV blockading. BV: Mapped E-lun as visible to the host, but LDEV blockading B:Unmapped to the E-lun, but LDEV blockadingE-Seq#: Displays the production (serial) number of the external LUN. Unknown is shown as '-'.E-LDEV#: Displays the LDEV# of the external LUN. 'Unknown' is shown as '-'.(4) Command for discovering an external volume via the device fileIt is possible to discover the external volumes by using the inqraid command.Example in Linux:

# ls /dev/sd* |./inqraid -CLI

DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:GroupPRODUCT_IDsdh CL2-G 63528 15360 - s/s/ss 0100 5:01-09OPEN-Vsdu CL2-G 63528 2755 - s/s/ss 000B S:00001OPEN-0Vsdv CL2-G 63528 2768 - s/s/ss 000B U:00000OPEN-0Vsdw CL2-G 63528 2769 - s/s/ss 000B E:16384OPEN-V

• R:Group: This displays the physical position of an LDEV according to mapping of LDEV inthe RAID storage system.

GroupR:LDEV mapping

RAID Group number - Sub numberRAID LevelRAID Group1: RAID15: RAID56: RAID6

PoolID numberSSnapshot S-VOL

00000UUnmapped

External Group numberEExternal LUN

Example in Linux:# ls /dev/sd* |./inqraid/dev/sdh -> CHNO = 0 TID = 1 LUN = 1

[HP] CL2-G Ser = 63528 LDEV =15360 [HP ] [OPEN-V]

HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]RAID5[Group 1- 9] SSID = 0x0100

/dev/sdu -> CHNO = 0 TID = 1 LUN = 14[[HP] CL2-G Ser = 63528 LDEV =2755 [HP ] [OPEN-V

]HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]E-LUN[Group 00001] SSID = 0x000BSNAPS[PoolID 0001] SSID = 0x000B

/dev/sdv -> CHNO = 0 TID = 1 LUN = 15[[HP] CL2-G Ser = 63528 LDEV =2768 [HP ] [OPEN-V

]

Controlling Auto LUN 203

HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]E-LUN[Group 08191] SSID = 0x000BUNMAP[Group 00000] SSID = 0x000B

/dev/sdw -> CHNO = 0 TID = 1 LUN = 16[[HP] CL2-G Ser = 63528 LDEV =2769 [HP ] [OPEN-V

]HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL]E-LUN[Group 16384] SSID = 0x000BE-LUN[Group 16384] SSID = 0x000B

• Group: This item shows physical position of an LDEV according to mapping of LDEV in theRAID storage system.

Display FormatsLDEV Mapping

RAID1[Group Group number - Sub number]RAID GroupRAID5[Group Group number - Sub number]RAID6[Group Group number - Sub number]

SNAPS[PoolID poolID number ]Snapshot S-VOL

UNMAP[Group 00000]Unmapped

E-LUN[Group External Group number]External LUN

Relations between "cc" command issues and statusThe migration volumes can be handled by issuing the RAID Manager commands (pair creationand pair splitting commands). The validity of the specified operation is checked according to thestatus of the paired volume (primary volume).Table 45 (page 204) shows the relations between the migration volume statuses and commandacceptances.

Table 45 Command issues and pairing status transition

Pair SplittingPair CreationCommand:

Simplex -S-m ccPairing Status CC:

AcceptableAccepted(1) SMPL(2) to (3)(2) to (4)

Accepted (1)Acceptable(2) COPY

Accepted (1)Rejected(3) PSUS

Accepted (1)Rejected(4) PSUE PDUB

Legend:Accepted: A command is accepted and executed. When the command execution succeeds, the status changes tothat of the shown number.Accepted: A command is accepted and executed. When the command execution succeeds, the status changes tothat of the shown number.Acceptable: No operation is executed, though a command is accepted.Rejected: Command execution is rejected and the operation terminates abnormally.Other commands and options (for example, pairresync…) for operating a paired volume are rejected.The "-m cc" option cannot be specified with "-split" option in the same command.


Restrictions for Auto LUNAuto LUN must be used within the following restrictions:

• Business Copy (HOMRCF). The operation for the volume migration must be operated atthe "SMPL" or "PAIR" or "COPY" state. If not, paircreate -m cc command is rejectedwith EX_CMDRJE or EX_CMDIOE. Also Business Copy cannot be operated to CC_SVOLmoving in Auto LUN. In copying CC_SVOL, the copy operation for the volume migration isstopped, if the Business Copy pairsplit command is executed.

• Continuous Access Synchronous (HORC). The operation for the volume migration mustbe performed at the "SMPL" or "PSUS" state. If not, paircreate -m cc command isrejected with EX_CMDRJE or EX_CMDIOE. Also HORC cannot be operated to CC_SVOLcopying in Auto LUN. On one hand, in copying CC_SVOL, the copy operation for the volumemigration is stopped, if pairresync command for of HORC is executed.

• LDEV type for Auto LUN. The volume of the external connection for the volume migrationmust be mapped to an LDEV as OPEN-V.

Continuous Access Journal MxN configuration and controlOverview

Continuous Access Journal 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 SCSIprotocol does not have timestamps.If the open system (RAID Manager) has the timestamp as an equivalent of sysplex timers,Continuous Access Journal supports 4X4 on the open system.

• RAID Manager: delivers the timestamp(CTQ-Marker) to the consistency group

• Disk array (RCU): arbitrates the timestamp (CTQ-Marker) across multiple storage systemsconnected remote command devices, and then commits the journal data.

In this architecture, RAID Manager needs to be running. If RAID Manager has stopped, thestorage system (RCU) function does not appear to exist. Therefore, the better architecture is toinclude the storage system (RCU) function into RAID Manager.

Continuous Access Journal MxN configuration and control 205

RAID Manager already supports the group control across multiple storage systems in the CntAc-S_Sync group. This means that RAID Manager can support Continuous Access Journal MxNon the open system if RAID Manager is capable of delivering the timestamps and committingthe Journal data with a CTQ-Marker.Thus, RAID Manager supports Cnt Ac-J MxN for open systems in the four ways described in“Policy” (page 206).

PolicyAll data consistency of the consistency group across multiple storage systems is maintained byRAID Manager. The storage system supports only basic functions; there is no relation betweenstorage systems in order to simplify testing and configurations.RAID Manager supports Continuous Access Journal MxN in the following ways.

(1) Delivering the timestamp (CTQ-Marker)RAID Manager (HORCM daemon process) makes a table for the groups registered to thehorcm.conf as HORCM_CTQM with startup, and makes the threads for each group that deliversthe same timestamp with an increment to the multiple storage systems configured in a group.The thread for a group delivers the same timestamp with increments, as far as a group configuredContinuous Access Journal in the PAIR status.The timestamp is delivered by using Freeze/Q-Marker & Run way as default. The timestamp ismaintained in each storage system. RAID Manager includes this timestamp with startup, andthen delivers the same timestamp with increments to each storage system.

(2) Arbitrating/committing the journal data with CTQ-MarkerThe thread for a group on HORCM compares the timestamp of S-JNL on each storage system(RCU) as far as a group configured Continuous Access Journal in PAIR state. Once HORCMdetects a matching point of the timestamp (CTQ-Marker) on all storage systems (RCU), it issuesan order to commit the Journal data with CTQ-Marker to each storage system (RCU).

(3) Propagating Error suspendThe thread for a group on HORCM delivers the same timestamp with increments as far as agroup configured Continuous Access Journal in PAIR state. If the PSUE/PFUS state detects atleast one storage system, then it notifies another storage system to suspend PSUS in order tokeep the state consistent in the consistency group. Then the thread stops to deliver the timestamp,and keeps monitoring its consistency group with interval of HORCM_CTQM until it becomesPAIR state by next pair-resync.

(4) Committing the Journal data inside pairsplit commandThe pairsplit command makes a suspending state on PAIR state, and inherits to compare thetimestamp of S-JNL on each storage system (RCU). If it detects a matching point of the timestamp(CTQ-Marker) on all storage systems (RCUs), then it issues an order to commit the Journal datawith Q-Marker to each storage system (RCU), and repeats it until it detects an EOM (End OfMarker) of CTQ-Marker with the pairsplit command.

horcm.confRAID Manager supports Cnt Ac-S_Sync group across multiple storage systems, but it does notallow Continuous Access Asynchronous (Cnt Ac-J) group across multiple storage systems.Therefore, RAID Manager needs to add the group definition (HORCM_CTQM) in order to allowmaking Continuous Access Asynchronous(Cnt Ac-J) group across multiple storage systems.Then the HORCM daemon process delivers the timestamps (called the consistency Q-Marker),and commits S-VOL Journal data with Q-Marker to the defined group.


(1) Defining to control Cnt Ac-J MxNRAID Manager 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(optionaloradb300

where

• group is to be allowed as a group across multiple storage systems.

• interval is the interval for the CTQ-Marker, recommended as a few second.

• mode is the run mode for the CTQ-Marker (timestamp). The default run mode is freeze/run.This does not normally need to be specified. If "run" is specified, then the timestamp is issuedwithout freeze.

(2) Specifying different JID into consistency groupIn order to support the MxN configuration, it is necessary to specify a different journal ID (JID)into a consistency group corresponding to a RAID Manager group. Thus RAID Manager addsan option to specify Journal ID in horcm.conf.HORCM_LDEV

#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#oradb dev1 30095:1 02:40oradb dev2 30095:1 02:41oradb dev3 30095:2 02:42oradb dev4 30095:2 02:43

NOTE: The number at the end of the serial number (for example, :1 or :2) specifies the JournalID.

If JID (Journal ID) is specified on horcm.conf as mentioned above, then the paircreatecommand need not specify Journal ID (-jp <jid> -js <jid>) option.If JID (Journal ID) is not specified on horcm.conf, then Journal ID (-jp <jid> -js <jid>) option ofthe paircreate command is used.

Command specificationsRAID Manager does not change the command options for supporting Continuous Access JournalMxN Open. However the output of the command is added so that the command can display theconsistency group and Q-Marker for each storage system, because the consistency group andQ-Marker are managed on each storage system.

pairdisplay commandThe output of pairdisplay -v ctg and pairdisplay -v jnl[t] are supported so thatthe option can display consistency group information for each storage system. Following is anexample for Cnt Ac-J 2x2:# pairdisplay -g ora -v ctgCTG P/S Status AP U(%) Q-Marker QM-Cnt SF(%) Seq# IFC OT/s CT/m RT/m000 P-VOL PAIR 1 0 00000032 18 50 64034 ON 60 - -000 S-VOL PAIR 1 0 00000020 - 70 64035 - - - -000 P-VOL PAIR 1 0 00000031 15 50 64045 ON 60 - -000 S-VOL PAIR 1 0 00000022 - 70 64046 - - - -

# pairdisplay -g ora -v jnlJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Num LDEV#001 1 0 PJNN 1 0 00000049 2 1633672703 640342 5376002 1 0 SJNN 1 0 00000047 0 1633672703 640352 5378


001 1 0 PJNN 1 0 00000049 20 211506164 6404513 12388002 1 0 SJNN 1 0 00000035 20 260319089 6404616 12544

# pairdisplay -g ora -v jnltJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW001 1 0 PJNN 1 0 00000c76 20 1633672703 6403460 300 40002 1 0 SJNN 1 0 00000c62 20 1633672703 6403560 300 40001 1 0 PJNN 1 0 00000c3a 7 211506164 6404560 300 40002 1 0 SJNN 1 0 00000c33 7 260319089 6404660 300 40

# pairdisplay -g horc0 -v jnl -feJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq#Num LDEV# CTQM016 2 0 PJSN 1 0 0000bb1b 0 198578688 640141 32768 -018 2 0 SJSN 1 0 0000bb1b 0 99283968 640141 32770 0000187f017 2 0 PJSN 1 0 00000011 0 198578688 640141 32769 -019 2 0 SJSN 1 0 00000011 0 99283968 640141 32771 0000187f

NOTE: CTQM: Displays the last CTQ-Marker that was committed on S-VOL.

pairsplit commandThe pairsplit command does not change the command options for supporting Cnt Ac-J MxNOpen. However, internal behavior is different from 1x1 Cnt Ac-J or Continuous AccessAsynchronous.

(1) pairsplit -r or -rw option

• Issues Freeze to consistency group on each MCU

• Issues Suspend & Run to make a suspending state for consistency group on each MCU

• Searches/commits a minimum matching point of the CTQ-Marker on RCU via MCU (in otherwords, do Journal Restore with CTQ-Marker)

• Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU viaMCU

• Issues End of Suspend to terminate a suspending state, after committed with EOM (End OfMarker) marked on MCU on all RCU

Exception:If an uncommitted state (that is, link failure) is detected while executing its operation,then the operation of committing is aborted on keeping current CTQ-Marker level, and asuspending state terminates without waiting for the EOM (End Of Marker).

(2) pairsplit -P option


• Issues Suspend & Run to make a suspending state for consistency group on each MCU




• Issues End of Suspend to terminate a suspending stateException:If an uncommitted state (that is, link failure) is detected while executing its operation,then the operation of committing is aborted on keeping current CTQ-Marker level, and asuspending state terminates without waiting for the EOM (End Of Marker).

(3) pairsplit -S option


• Issues Delete & Run to make a deleting state for consistency group on each MCU



• Issues End of Delete to terminate a deleting state, after committed with EOM (End Of Marker)on all RCU

Exception:If an uncommitted state(that is, link failure) is detected while executing its operation,then the operation of committing is aborted on keeping current CTQ-Marker level, and a deletingstate terminates without waiting for an EOM (End Of Marker).

(4) pairsplit -RS optionIn 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 otherwords, do Journal Restore with CTQ-Marker)

• Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU viaRCU

• Issues End of Suspend to terminate a suspending state, after committed with an EOM (EndOf Marker) on all RCU

Exception:If an uncommitted state (that is, link failure) is detected while executing its operation,then the operation of committing is aborted on keeping current CTQ-Marker level, and asuspending state terminates with detecting at least one EOM (End Of Marker).In the case of Failure (PSUE/PSUS):

• Issues SwapSuspend to make a suspending state for consistency group on each RCU


• Repeats above until detecting an EOM(End Of Marker) marked on all RCU via RCU

• Issues End of Suspend to terminate a suspending state

(5) pairsplit -R optionIn the case of PAIR state (NO failure):

• Issues Delete to make a deleting state for consistency group on each RCU



• Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU viaRCU

• Issues End of Delete to terminate a deleting state, after committed with an EOM (End OfMarker) on all RCU

Exception:If an uncommitted state (that is, link failure) is detected while executing its operation,then the operation of committing is aborted on keeping current CTQ-Marker level, and a deletingstate terminates with detecting at least one EOM (End Of Marker).In the case of Failure(PSUE/PSUS):

• Issues Delete to make a deleting state for consistency group on each RCU


• 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 operationRAID Manager does not change the command options for supporting Continuous Access JournalMxN Open. However, the output of the command is added so that the command can display theconsistency group and Q-Marker for each storage system, because the consistency group andQ-Marker are managed on each storage system.

(1) Consistency group ID and journal ID for Cnt Ac-JThe consistency group ID must be assigned/used as the unique identifier across multiple storagesystems. Therefore, the paircreate command makes a group volume having the same consistencygroup ID across multiple storage systems.

(2) Cascading operationThe "-FHORC" option for cascading operation does not perform with CTQ-Marker Mode. Hencethe cascading volume must not be specified Cnt Ac-J MxN volume when using the "-FHORC"option.

(3) Running HORCM daemonHORCM daemon process delivers the timestamps (called the consistency Q-Marker) to thedefined consistency group. Therefore if HORCM daemon is stopped, then Cnt Ac-J will stop todelta (commit) and will suspend because of Journal Full state.Thus HORCM daemon must be running to keep the PAIR state.

(4) Separating a command device IO from application IOThe HORCM daemon process issues IOs to the command device in order to deliver thetimestamps to the defined consistency group. Therefore, it is recommended to separate thecommand device path from the application IO path.

(5) About waiting application IOThe HORCM daemon process delivers the timestamps to the defined consistency group whilefreezing IO for each journal.Waiting Rate = 0.5ms * Number of journal / / Interval (ms) * 100(Note that 0.5 ms depends on the OS platform.)Therefore it is recommended to limit within four journal per consistency group and 8192 LDEVsper consistency group. In the case of multiple consistency groups per HORCM, it is recommendedto 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 LinkNormal state. In other words this option does not support At-time Split, hence these operationsare required to stop HOST IO in order to keep Data Consistency on S-VOL. This is the samerestriction as Cnt Ac-S_Sync.

(7) Suspending/deleting statusThe suspending/deleting for committing S-VOL Journal data with CTQ-Marker is accomplishedby the RAID Manager commands. Therefore the storage system has nothing to do in that status(suspending/deleting).If a RAID Manager command is aborted for some reason (KILL, etc.) or EX_EWSTOT, the storagesystem keeps that status (suspending/deleting).To terminate this status, re-execute the RAID Manager command, then terminatesuspending/deleting status after "JNL Consistency Restore".

(8) Detecting inconsistent CTQ-MarkerThe pairsplit command checks data consistency with CTQ-Marker across multiple storagesystems. If an inconsistent CTQ-Marker is detected, then it returns with EX_VOLCUR afterchanged to suspend status.This error needs to confirm if CTQMs are the same on S-VOL on each storage system using the"pairdisplay -v jnl -fe" option.# pairdisplay -g horc0 -v jnl -fe

JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq#Num LDEV# CTQM

016 2 0 PJSN 1 0 0000bb1b 0 198578688 640141 32768 -

018 2 0 SJSN 1 0 0000bb1b 0 99283968 640141 32770 0000187f

017 2 0 PJSN 1 0 00000011 0 198578688 640141 32769 -

019 2 0 SJSN 1 0 00000011 0 99283968 640141 32771 0000187f

(9) About pairsyncwait commandUsing the Q-Marker with the pairsyncwait command is managed on each Journal includingthe target device. Therefore the pairsyncwait command must specify a target device (-g<group> -d <pair vol>, or -d <device file>, or -d <serial#> <ldev#>). For example:# pairsyncwait -g horc0 -d dev-002 -t 500

UnitID CTGID Q-Marker Status Q-Num

1 0 0000003de8 DONE 0

If group (-g <group>) is 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).

• JNL Consistency Suspend: suspends after "JNL Consistency Restore"

• JNL Full Suspend: suspends after "JNL Full Restore"


Configuration examplesRAID Manager does not change the command options for supporting Continuous Access JournalMxN Open. However the output of the command is added so that the command can display theconsistency group and Q-Marker for each storage system, because the consistency group andQ-Marker are managed on each storage system.

(1) Cnt Ac-J 2x2


(2) Cnt Ac-J 2x1

Duplication of RAID Manager applications

CAUTION: You must read “Requirements for duplication of RAID Manager” (page 216) beforeyou duplicate RAID Manager applications.

When a failure occurs on the RAID Manager application (for example, failure of the server onwhich RAID Manager is installed) in the MxN configuration of Continuous Access Journal, thedata consistency in the consistency group that spans multiple storage systems will not be ableto be maintained. Duplication of the RAID Manager application is a function to use a second

Duplication of RAID Manager applications 213

RAID Manager application to maintain the data consistency in the consistency group when afailure occurs in the first RAID Manager application.You can use up to two RAID Manager applications per one consistency group for each site. Thefollowing figure illustrates the typical MxN configuration.

When you specify the command device to the HORCM_CMD in the configuration definition file,you must make the definition sequence of storage system match within the site, as shown in thefollowing definition file examples.


Duplication of RAID Manager applications 215

Requirements for duplication of RAID ManagerAll of the following requirements must be met in order to use multiple RAID Manager applications.If any of these requirements is not met, the duplication of RAID Manager makes data inconsistenton the RCU.

• RAID Manager version:01.31.08 or later

• Platform on which both RAID Manager applications are installed:Other than OpenVMS


• Storage system:

P9500◦◦ XP7 Storage (XP7)

• DKCMAIN microcode version:

70-06-20-00/00 or later (P9500)◦◦ 80-03-00-00/03 or later (XP7)

Note for duplication of RAID ManagerWhen a failure does not occur in RAID Manager, the running RAID Manager application handlesthe processing to keep the data consistency in the consistency group, for example CTQ-Marker,and the other RAID Manager application stands by in case of a failure. If the stand-by RAIDManager application issues the pairsplit command, an error (EX_INVVOL) might occur. Ifthis error occurs, issue the pairsplit command from the other RAID Manager application.

Remote volume discoveryIn the configuration separating "Storage admin server (RAID Manager server)" and each productionserver, it is difficult to verify/check the volumes on the production servers and the volumesdescribed to the horcm.conf on RAID Manager server.In this configuration, you cannot use the following RAID Manager capabilities:

• Command device security

• pairdisplay -fd option that displays the device file on the production host view

• raidscan -find verifyTo solve this configuration problem, RAID Manager supports a way to discover volumes on theremote server by adding the -export option to the inqraid command, and by importing itsoutput via the raidscan -find command.

Remote volume discovery 217

Figure 64 Volume discovery

Discovering a remote volumeThe inqraid command exports the device information discovered on the production servers.The device information includes "Keyword, Serial#, Ldev#, Device file name..". The raidscan-find inst command on RAID Manager server imports the device information, and registersit into the HORCM daemon.The inqraid command is needed only for discovering LUNs on the production server.

(1) inqraid formatThe inqraid command adds the "-export" option with -CLI for exporting the results of the volumediscovery on the remote server.Example from UNIX (Solaris):# ls /dev/rdsk/c1t* | inqraid -CLI -exportINQRAID:@CL4-G@64015@0@124@OPEN-V-CM@/dev/rdsk/c1t0d0s2INQRAID:@CL4-G@64015@1@124@OPEN-V-CM@/dev/rdsk/c1t0d1s2INQRAID:@CL4-G@64015@2@95@OPEN-V@/dev/rdsk/c1t0d2s2INQRAID:@CL4-G@64015@3@95@OPEN-V@/dev/rdsk/c1t0d3s2INQRAID:@CL4-G@64015@4@95@OPEN-V@/dev/rdsk/c1t0d4s2INQRAID:@CL4-G@64015@5@95@OPEN-V@/dev/rdsk/c1t0d5s2INQRAID:@CL4-G@64015@7@95@OPEN-V@/dev/rdsk/c1t0d7s2

(2) A way to export/import using pipe & SSHExample for exporting from UNIX (Solaris) to RAID Manager host:# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh<RAID Manager host> raidscan -find instDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 0


64015 2/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 -64015 2/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 064015 3

Example for Verifying from UNIX (Solaris) to RAID Manager host:# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh <RAID Managerhost> raidscan -find verifyDEVICE_FILE Group PairVol PORT TARG LUN MSERIAL LDEV/dev/rdsk/c1t0d0s2 - - - - - -64015 0/dev/rdsk/c1t0d1s2 - - - - - -64015 1/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 -64015 2/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 -64015 3/dev/rdsk/c1t0d4s2 - - - - - -64015 4/dev/rdsk/c1t0d5s2 - - - - - -64015 5/dev/rdsk/c1t0d7s2 - - - - - -64015 7

(3) A way to import with horcmstart.sh on RAID Manager hostExample 1 for exporting:# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh <RAID Managerhost> cat > /etc/horcmperm*.conf

ORExample 2 for exporting:# ls /dev/rdsk/c1t* | inqraid -CLI -export > /tmp/inqraid.ex

ftp "/tmp/inqraid.ex" to "/etc/horcmperm*.conf" on RAID Manager hostThis example for importing on RAID Manager host executes horcmstart.sh * on the RAID Managerhost, where * is the instance number.Display example for verifying on RAID Manager host:# cat /etc/horcmperm*.conf | raidscan -find verifyDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c1t0d0s2 - - - - - - 64015 0/dev/rdsk/c1t0d1s2 - - - - - - 64015 1/dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 - 64015 2/dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 - 64015 3/dev/rdsk/c1t0d4s2 - - - - - - 64015 4/dev/rdsk/c1t0d5s2 - - - - - - 64015 5/dev/rdsk/c1t0d7s2 - - - - - - 64015 7# pairdisplay -g G1 -fd -lGroup PairVol(L/R) Device_File ,Seq#,LDEV#.P/S,Status,Fence,Seq#,P-LDEV#MG1 G1-000(L) c1t0d2s2 64015 2.SMPL ---- ------,----- ------G1 G1-001(L) c1t0d3s2 64015 3.SMPL ---- ------,----- ------

Remote volume discovery 219

7 Data protection operations with RAID ManagerThis chapter describes data protection operations using RAID Manager.

Data protection operationsUser 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 corruptioncan happen due to software layer bugs or human error. RAID Manager Data Protection Facilitydoes not prevent these types of errors. On the other hand, the purpose of data protection is toprevent writing to volumes that the RAID storage system is guarding.Data protection functions include:

• Data Retention

• Volume Retention

• Volume Security for Mainframe

• DKA Encryption

Data RetentionThe purpose of the Data Retention is to prevent writing to volumes that the RAID storage systemis guarding. Data Retention sets a protection attribute for the specified LU.

• Hide from Inquiry command.The RAID storage system conceals the target volumes fromthe SCSI Inquiry command by responding "unpopulated volume" (0x7F) to the device type.

• SIZE 0 volume.The RAID storage system replies with "SIZE 0" to the target volumes throughthe SCSI Read capacity command.

• Read protection.The RAID storage system protects reading from the target volumes byresponding with the "Illegal function" check condition (SenseKey = 0x05, SenseCode =0x2200).

• Write protection.The RAID storage system replies with "Write Protect" in the mode senseheader, and protects from writing the target volumes by responding with the "Write Protect"check condition (SenseKey=0x07, SenseCode=0x2700).

• S-VOL disabling.The RAID storage system rejects the command execution of the copy series program productfor not to be overwritten the secondary (target) volume by the copy process of copy seriesprogram product (Continuous Access Synchronous, Continuous Access Journal, BusinessCopy, Snapshot, High Availability), and protects the target volume. This option can be usedwith the other Data Retention options in parallel. For example, if you want to protect fromthe writing by the both copy series program product and the host accessing, set the bothwrite protection option and this option. Only the setting of write protection option cannotprotect the target volume from the writing executed by the copy processing of the copy seriesprogram product.

Restrictions on Data Retention volumes

• File systems using Data Retention

When setting Data Ret to the UNIX file system volumes, the volumes must be mountedwith the Read Only option after the volumes are unmounted. If Data Ret is set to the

◦

220 Data protection operations with RAID Manager

volumes as they are in the mounted status, unexpected behavior or errors might occurin the system.

◦ When using a file system for Write Protect Mode set disk on Windows Server2003/Windows Server 2008/Windows Server 2012, use the "-x mount" and "-x umount"RAID Manager command options with the above mentioned procedures.

◦ Data Retention volumes set to Write Protect Mode (Read ONLY) cannot be used forthe Windows NT/Windows 2000 file system (NTFS, FAT).

◦ In a configuration with NAS modules installed, do not set Data Retention in a file systemvolume used by a NAS module. If you do, unexpected behavior or errors might occurin the system.

• LVM(VxVM) on Data Retention

◦ If changing LVM configuration including Data Retention, use the raidvchset -vg commandfor setting the status of the target volume checking prohibited temporarily. Also, afterthe completion of LVM configuration change, set again the status as checking.

• Data Retention in HA Cluster Server

◦ If HA Cluster software writes to the metadata at regular intervals to confirm whether itsdisks are available or not, then Data Retention should not be used in HA environments.

• Dynamic disk on Windows systems

◦ Data Retention volumes cannot be used for the dynamic disk, because the dynamicdisk does not handle the volumes set to Write Protect Mode (Read ONLY). DataRetention volumes must be used for basic disks only.

• LUN#0

◦ Some operating systems cannot recognize LUNs over LUN#1 if LUN#0 has the DataRetention "inv" attribute set. This is because some HBA drivers do not scan all LUNson a port if LUN#0 is invisible.

Protection parameters and operationsThe RAID storage systems have protection checking parameters for each LU, and theseparameters are set through RAID Manager and its command device. RAID Manager supportsthe following commands to set and verify the parameters for protection checking for each LU:

• raidvchkset: Sets the protection checking parameter for the specified volumes.

• raidvchkdsp: Shows the protection checking parameter for the specified volumes basedon the RAID Manager configuration definition file.

• raidvchkscan: This command has three different uses depending on the options used withthe command.

◦ Shows the port, target ID, LDEV, and validation checking parameters for the specifiedvolumes based on the raidscan command.

◦ Shows the journal volume list setting and information for the journal volume.

◦ Shows the Snapshot pool setting and information for the Snapshot pool.

Data Protection facilityThe Data Protection Facility permits main operations to volumes that you can see on the host,and prevents wrong operations. RAID Manager controls protected volumes at the result of

Protection parameters and operations 221

recognition of protection. RAID Manager recognizes only volumes that the host shows. For thatpurpose LUN Security is provided for the RAID Manager environment.The Data Protection Facility ON/OFF is controlled by the security setting for the command device,as shown in the following table.

Table 46 Security setting for command device

Security to be setCommand device setting

Group informationacquisition

User authenticationSecurity

No security000

Only HORCM_DEV allowed100

User authentication required010

User authentication required110Only HORCM_DEV allowed

CMD security001

CMD security101Only HORCM_DEV allowed

CMD security011User authentication required

CMD security111User authentication requiredOnly HORCM_DEV allowed

Notes:• Only HORCM_DEV allowed: means to be able to perform the operation for only paired logical volumes described

at HORCM_DEV.

• User authentication required: means that only the commands issued by the authorized users can be executed.

• CMD security: means that only the devices recognizable from the host can be operated.

The Data Protection Facility uses an enhanced command device that you define using the LUNManager software (or SNMP). When you define the command device, the DataProtection Facilityis turned ON or OFF to each command device, which has an attributes to enable the DataProtection Facility. RAID Manager distinguishes the ON from OFF attribute when RAID Managerrecognizes the command device. Figure 65 (page 223) shows the definition of protected volumes.

NOTE: If the command device is set to enable protection mode, there is no impact on RAIDManager operations. RAID Manager controls pairs under current specification. For details aboutthe command operations when the Data Protection Facility is turned ON, see “Target commandsfor protection” (page 225).


Figure 65 Definition of the protection volumes

Data Protection Facility specificationsOnly the permitted volumes can be registered in horcm.conf.When creating the horcm.conffile, describe volumes only from the view that the host shows. RAID Manager manages mirrordescriptors (Continuous Access Synchronous, Business Copy/MU#0/1/2) as a unit. The DataProtection Facility has two specifications: one must be a volume that you can see from the hostsuch as the Inquiry tool, and the other must be a mirror descriptor volume that was registered inhorcm.conf. The following table shows the registration for the mirror descriptor.

Table 47 Registration for the mirror descriptor

Mirror Descriptor in horcm.confVolumes inhorcm.conf

Business CopyContinuous AccessSynchronous

MU#2MU#1MU#0

noneEnoneEnoneEnoneE

--------Unknown

-permittedvolumes

-permittedvolumes

-permittedvolumes

-permittedvolumes

/dev/rdsk/c0t0d0

--------Unknown

Legend:E: Mirror descriptor volume to be registered in horcm.conf.Unknown: Volumes that own host cannot recognize, even though volumes were registered in horcm.conf.

• RAID Manager permits operation after the permission command at startup of HORCM.The target is volume that was registered in the horcm.conf file.

• The permission command is necessary to permit the protected volume at first. Thepermission command compares an identification for volumes of horcm.conf to all ofown host volumes, and the result is registered within HORCM. And HORCM makes tablesfor protected volume and permitted volumes from horcm.conf and Inquiry result. Inquiryresult is based on configuration of Data Retention. When controlling pair volumes, requeststo 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.You need to configure Data Retention before RAID Manager operation. RAID Managerchecks Data Retention by Inquiry within RAID Manager.

• The Data Protection Facility can be enabled separately for each command device. If youwant to use protection and non-protection modes in the same storage system at the sametime, you can define two (or more) command devices: one with protection ON, one with

Data Protection facility 223

protection OFF. Protection mode is enabled for the host that has Data Retention and ONcommand device.

Examples for configuration and protected volumesCase (1): Two Hosts (Figure 66 (page 224)). In protect mode Ora2 are rejected to operate thepaired volume, because of Unknown for Grp4 on HOST2.Case (2): One Host (Figure 67 (page 224)). In protect mode Ora1 and Ora2 are rejected to operatethe paired volume, because of Unknown for Grp2 and Grp4 on HOST1. If HOST1 has a protectionOFF command device, then Ora1 and Ora2 are permitted to operate the paired volume.

NOTE: The Data Protection Facility is implemented by only RAID Manager. RAID Managerneeds to know the protection attribute for the command device whether should be permitted theoperation for paired volume. If HORCM has protection ON command device at its time, thenHORCM checks a permission for a paired volume.

Figure 66 Example for the two-host configuration

Figure 67 Example for the one-host configuration


Operation authority with CMD security enabledIf the CMD security is enabled, you have the operation authority for the LU which meets both ofthe following requirements.

• The connection to the host has been recognized when you start RAID Manager.

• The LU is the target of the pair operation specified with MU# which is defined in theconfiguration definition file.

For the volumes that you do not have the operation authority, "****" is displayed as the LDEV#,and "----" is displayed as the status. If you perform the pair operations, RAID Manager rejectsthe request with the error code "EX_ENPERM" (pairdisplay is not included).If you specify 0, 1 2... for the MU#, your operation authority is limited on the LUs for the localcopy program products (Business Copy, Business Copy MF and Snapshot). If you specify h0,h1 or h2 for the MU#, your operation authority is limited on the LUs for the remote copy operations(Continuous Access Synchronous, Continuous Access Synchronous MF, Continuous AccessSynchronous Async, Continuous Access Journal, Continuous Access Journal MF, and HighAvailability). If you specify nothing for the MU#, you have the operation authority on MU#0 forthe local copy and the remote copy operations.

Target commands for protectionThe following commands are controlled by the Data Protection Facility: horctakeover,paircurchk, paircreate, pairsplit, pairresync, pairvolchk, pairevtwait,pairsyncwait, raidvchkset, raidvchkdsp, pairdisplay. When the command is issuedto non-permitted volumes, RAID Manager rejects the request with error code "EX_ENPERM"(pairdisplay is not included).

• The pairdisplay command shows all volumes, so that you can confirm non-permittedvolumes. Non-permitted volumes are shown without LDEV# information. As shown below,the LDEV# information is " **** " (-CLI is "-").).#pairdisplay -g oradbGroup PairVol(L/R) (Port#,TID,LU-M),Seq#, LDEV#.P/S,Status, Seq#,P-LDEV# Moradb oradev1(L) (CL1-D , 3, 0-0) 35013 ****..- -,- -oradb oradev1(R) (CL1-D , 3, 1-0) 35013 ****..- -,- -

• The raidscan command shows all volumes same as current specification, because it doesnot need HORCM_DEV and HORCM_INST on horcm.conf. If you want to know permittedvolumes at raidscan, use raidscan -find. The -find option shows device file nameand storage system information by using internal Inquiry result. You can use raidscan-find to make horcm.conf, because only permitted volumes are shown with host sideview. Following is an example for HP-UX systems:#ioscan -fun | grep rdsk | raidscan -findDEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID/dev/rdsk/c0t3d0 0 F CL1-D 3 0 35013 17 OPEN-3/dev/rdsk/c0t3d1 0 F CL1-D 3 1 35013 18 OPEN-3

permission commandRAID Manager recognizes permitted volumes at the result of the permission command. Thepermission command is the -find inst option of raidscan. This option issues an inquiryto a specified device file to get Ser# and LDEV# from the RAID storage system, and checks anidentification for volumes of horcm.conf to all of own host volumes, then stores the result withinHORCM of the instance. This permission command is started by /etc/horcmgr automatically.The following example shows the relation between the device file and horcm.conf for a manualoperation on an HP-UX system. All volumes of ioscan are permitted.


#ioscan -fun | grep rdsk | raidscan -find instDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013 17/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17

New options for security

raidscan -find instThis option registers the device file name to all mirror descriptors of the LDEV map table for RAIDManager and permits the matching volumes on horcm.conf in protection mode. It is startedfrom /etc/horcmgr automatically. You will not normally need to use this option. This option issuesan Inquiry to a device file from the result of STDIN. Then RAID Manager gets Ser# and LDEV#from the RAID storage system. Subsequently, RAID Manager compares the Inquiry result to thecontents of horcm.conf, and the result is stored within HORCM for the instance. At the sametime RAID Manager shows the result of this option about the relation. This option will also beterminated to avoid wasteful scanning after registration based on horcm.conf, because HORCMdoes not need the registration any more.# ioscan -fun | grep rdsk | raidscan -find instDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013 17/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17

NOTE: When multiple device files share the same LDEV, the first device file is registered tothe LDEV map table.

raidscan -find verify [MU#]This option shows the relation between group on horcm.conf and Device_File registered tothe LDEV map tables from DEVICE_FILE of STDIN.# ioscan -fun | grep rdsk | raidscan -find verify -fdDEVICE_FILE Group PairVol Device_File M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 c0t3d0 0 35013 17/dev/rdsk/c0t3d1 oradb oradev2 Unknown 0 35013 18/dev/rdsk/c0t3d2 - - - 0 35013 19

NOTE: It shows shared LDEV among multiple device files, if there is a difference betweenDEVICE_FILE and Device_File. You can also use this option to the command device that specifiednon-protection mode. It is used for the purpose to see the relation between DEVICE_FILE andthe group of horcm.conf.

raidscan -f[d]This option shows the Device_File that was registered on the group of HORCM, based on theLDEV (as defined in the local instance configuration definition file).# raidscan -p cl1-d -fdPort# ,TargetID#,Lun#..Num(LDEV#....)...P/S, Status,Fence,LDEV#,Device_FileCL1-D , 3, 0...1(17)............SMPL - - -,c0t3d0CL1-D , 3, 1...1(18)............SMPL - - -,c0t3d1

pairdisplay -f[d]This option shows the relation between the Device_File and the paired volumes (protectedvolumes and permitted volumes), based on the group, even though this option does not haveany relation with protection mode.# pairdisplay -g oradb -fdGroup PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# Moradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -oradb oradev1(R) c0t3d1 0 35013 18..S-VOL COPY, 35013 17 -


If either the local or the remote host (instance) has not been shown the Device_File, then pairoperations are rejected (except the local option such as "-l") in protection mode because ofUnknown volume, as shown in the following example.# pairdisplay -g oradb -fdGroup PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# Moradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -oradb oradev1(R) Unknown 0 35013 ****..- -, - - -

Permitting protected volumesProtection mode needs recognition step to check accessible volumes and the horcm.conf atthe startup of HORCM on protection mode. The protected volumes must be registered to enablethe Data Protection Facility at each startup of HORCM, so that this registration process is executedautomatically by /etc/horcmgr.

With a $HORCMPERM fileThe following is executed for registration of permitted volume file ($HORCMPERM file), if$HORCMPERM file exists and there are permitted volumes. To permit only the volumes specified,then the volume list must be defined in the $HORCMPERM file.

Naming of $HORCMPERM file on UNIX systems$HORCMPERM is /etc/horcmperm.conf or /etc/horcmperm*.conf (* = instance number) by default.For example, on HP-UX systems:cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst# The following are an example to permit the LVM Volume groups.# For MU# 0vg00 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1vg00 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3# For MU# 1vg01 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1vg01 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3

Verifying a group for vg01. The following are examples how to verify whether a LVM volumegroup is mapped to group (MU#1 for Business Copy) in the horcm.conf file correctly.# export HORCC_MRCF=1# cat /etc/horcmperm.conf | grep vg01 | raidscan -find verify 1 -fd

OR# vgdisplay -v /dev/vg01|grep dsk|sed 's/\/*\/dsk\//\/rdsk\//g'|raidscan -find verify 1 -fdDEVICE_FILE Group PairVol Device_File M SERIAL LDEV/dev/rdsk/c0t3d0 oradb1 oradev1 c0t3d0 135013 17/dev/rdsk/c0t3d1 oradb1 oradev2 c0t3d1 135013 18/dev/rdsk/c0t3d2 oradb oradev3 c0t3d2 135013 19/dev/rdsk/c0t3d3 - - - 135013 20

Naming of $HORCMPERM file on Windows systems$HORCMPERM is %windir%\horcmperm.conf or %windir%\horcmperm*.conf (* = instancenumber) by default.type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst# The following are an example to permit the DB Volumes.# Note: a numerical value is interpreted as Harddisk#.# DB0 For MU# 0Hd0-10harddisk12 harddisk13 harddisk17


# DB1 For MU# 1hd20-23

Verifying a group for DB1. The following is an example of how to verify whether a DB volumegroup is mapped to a group (MU#1 for Business Copy) in the horcm.conf file correctly.D:\HORCM\etc> set HORCC_MRCF=1D:\HORCM\etc> echo hd20-23 | raidscan -find verify 1 -fdDEVICE_FILE Group PairVol Device_File M SERIAL LDEVHarddisk20 oradb1 oradev1 Harddisk20 1 35013 17Harddisk21 oradb1 oradev2 Harddisk21 1 35013 18Harddisk22 oradb oradev3 Harddisk22 1 35013 19Harddisk23 - - - 1 35013 20

Without a $HORCMPERM file: Commands to run on different operating systemsIf NO $HORCMPERM file exists, run a command on the host to permit all volumes on the host.Table 48 (page 228) shows the command to run on each operating system.

Table 48 Without a $HORCMPERM file: Commands to run on different operating systems

CommandSystem

echo /dev/rdsk/* /dev/rdisk/* /dev/rcdisk/* | /HORCM/usr/bin/raidscan -find instHP-UX

ls /dev/sd* | /HORCM/usr/bin/raidscan -find instLinux

ls /dev/sd* /dev/dasd*| /HORCM/usr/bin/raidscan -find instzLinux

ls /dev/rdsk/* | /HORCM/usr/bin/raidscan -find instSolaris

lsdev -C -c disk | grep hdisk | /HORCM/usr/bin/raidscan -find instAIX

ls /dev/rdisk/dsk* | /HORCM/usr/bin/raidscan -find instTru64 UNIX

ls /dev/rrz* | /HORCM/usr/bin/raidscan -find instDigital UNIX

/etc/dumpconf -d | grep sd | /HORCM/usr/bin/raidscan -find instDYNIX/ptx

ls /dev/rdsk/*vol /dev/rdsk/*/*vol/* | /HORCM/usr/bin/raidscan -find instIRIX64

/HORCM/usr/bin/raidscan -pi '$1$DGA0-10000 DKA0-10000 DGA0-10000' -find instOpenVMS

X:\HORCM\etc\raidscan.exe -pi $PhysicalDrive -find instWindows

NOTE: This registration process has risk because it is executed automatically by /etc/horcmgrwithout judgment for protection mode in order to validate the -fd option. This registration bringsa degradation in horcmstart.sh, but HORCM daemon has been running as usual, and it willdepend on how many devices a host has. To start faster at HORCM faster in non-protectionmode, create the $HORCMPERM file of "SIZE 0 byte" as a dummy file or to setHORCMPERM=MGRNOINST. At this time, the -fd option shows Device_File name as Unknown,and after you can use raidscan -find inst to validate the -fd option.

Environment variables

$HORCMPROMODThis environment variable turns protection mode ON as specified in the following table. If yourcommand device is set for non-protection mode, this parameter sets it to protection mode.


Table 49 Relation between HORCMPROMOD and command device

ModeHORCMPROMODCommand Device

Protection modeDon't careProtection mode

Non-protection modeNot specifiedNon-protection mode

Protection modeSpecified

$HORCMPERMThis 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 topermit the volumes specified.

Example for UNIX systems:cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst

Example for Windows systems:type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst

• If no HORCM permission file exists, then /etc/horcmgr executes a built-in command to permitall volumes of a host. See “Without a $HORCMPERM file: Commands to run on differentoperating systems” (page 228) for examples of commands run on an operating basis.

• /etc/horcmgr does not execute the built-in command if the following is defined for$HORCMPERM. This is used to execute a system command to permit the volumes specifiedfrom a user's shell script.HORCMPERM=MGRNOINST.

Determining the protection mode command deviceThe inquiry page is not changed for a command device with protection mode ON. Therefore,RAID Manager provides how to find the protection mode command device. To determine thecurrently used command device, use the horcctl -D command. This command shows theprotection mode command device by adding an asterisk (*) to the device file name.Example for HP-UX systems:# horcctl -DCurrent control device = /dev/rdsk/c0t0d0*- * indicates protection ON.


8 Examples of using RAID Manager commandsThis chapter provides examples of typical tasks performed using RAID Manager commands.

Group version control for mixed storage system configurationsBefore executing each option of a command, RAID Manager checks the facility version of thestorage system internally to verify that the same version is installed on mixed storage systemconfiguration. If the configuration includes older storage systems (for example, XP1024/XP128Disk Array), this method might not meet the requirements for the mixed storage systemenvironment, because the older storage system limits the availability enhancements in laterfacility versions. If the facility versions of the storage systems are different, you cannot useXP12000 Disk Array/XP10000 Disk Array-specific facility, because RAID Manager applies theminimum version to all storage systems. To expand the capability for mixed storage systemconfigurations and avoid problems such as this, RAID Manager supports the following groupversion control to manage a version for each group.

• RAID Manager (HORCM daemon) makes a facility version for each group based on aconfiguration file at the startup of HORCM.

• In a mixed storage system configuration, if the facility version of the storage systems (forexample, XP24000/XP20000 Disk Array and XP12000 Disk Array/XP10000 Disk Array) isdifferent on a group, RAID Manager will apply the minimum version for each group (see thefollowing figure).

Figure 68 Definition of the group version

LDM volume discovery and flushing for WindowsWindows systems support the Logical Disk Manager (LDM) (such as VxVM), and a logical driveletter is typically associated with an LDM volume (\Device\HarddiskVolumeX). Therefore, youcannot know the relationship between LDM volumes and the physical volumes of the RAIDstorage system. Therefore, you need to create the RAID Manager configuration file, and youneed to know the relationship that is illustrated in Figure 69 (page 231).

230 Examples of using RAID Manager commands

Figure 69 LDM volume configuration

Volume discovery functionRAID Manager supports the volume discovery function on three levels showing the relationshipbetween LDM volumes and the physical volumes.

• Physical level. RAID Manager shows the relationship between PhysicalDrive and LDEVby giving $Physical as a KEY WORD for the discovery.

• LDM volume level. RAID Manager shows the relationship between [LDM volume andPhysicalDrives] and LDEV by given $Volume as KEY WORD for the discovery.

• Drive letter level. RAID Manager shows the relationship between [Drive letter and LDMvolume and PhysicalDrives] and LDEV by given $LETALL as KEY WORD for the discovery.

The KEY WORD ($Physical, $Volume, $LETALL)can be used with raidscan -find,inqraid, mkconf commands.In Windows, DOS devices (for example, C:, Volume{}) are linked to a Device Object Name(\Device\...). RAID Manager indicates as the following by abbreviating a long Device ObjectName.

• Device Object Name of the LDM for Windows:\Device\HarddiskVolumeX for Partition : \VolX\DskYDskY shows that VolX are configured through HarddiskY.

• Device Object Name of the LDM for Windows 2003/2000:\Device\HarddiskDmVolumes\ ... \VolumeX for spanned volume : \DmsX\DskYs\Device\HarddiskDmVolumes\ ... \StripeX for striped volume : \DmtX\DskYs\Device\HarddiskDmVolumes\ ... \RaidX for Raid-5 volume : \DmrX\DskYsDskYs shows that DmsX(DmtX,Dmr) volumes are configured through bundling multiple HarddiskY1Y2….

• Device Object Name of the PhysicalDrive for Windows:\Device\HarddiskX\DR?? : HarddiskX

LDM volume discovery and flushing for Windows 231

You can determine the relationship between LDM volumes and LDEV by given a KEY WORDto the inqraid command.inqraid $LETALL -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDD:\Vol2\Dsk4 - - - - - - - DDRS-34560DE:\Vol44\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3F:\Vol45\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3G:\Dmt1\Dsk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3G:\Dmt1\Dsk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3G:\Dmt1\Dsk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3

inqraid $Volume -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID\Vol2\Dsk4 - - - - - - - DDRS-34560D\Vol44\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3\Vol45\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3\Dmt1\Dsk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3\Dmt1\Dsk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3\Dmt1\Dsk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3

inqraid $Phy -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDHarddisk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3Harddisk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3Harddisk2 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3Harddisk3 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3Harddisk4 - - - - - - - DDRS-34560D

• Device Object Name of the Partition for Windows NT

◦ \Device\HarddiskX\PartitionY : \DskX\pY

• Device Object Name of the PhysicalDrive for Windows NT

◦ \Device\HarddiskX\Partition0 : HarddiskX

inqraid $LETALL -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDD:\Dsk0\p1 - - - - - - - DDRS-34560DE:\Dsk1\p1 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3F:\Dsk1\p2 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3

inqraid $Phy -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDHarddisk0 - - - - - - - DDRS-34560DHarddisk1 CL2-K 61456 194 - s/s/ss 0005 1:01-11 OPEN-3

You want to know the relationship between LDM volumes and a group of the configuration files,and then find a group of the configuration file by giving a KEY WORD to raidscan -findverify command.raidscan -pi $LETALL -find verifyDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEVE:\Vol44\Dsk0 ORA ORA_000 CL2-K 7 2 - 61456 194F:\Vol45\Dsk0 ORA ORA_000 CL2-K 7 2 - 61456 194G:\Dmt1\Dsk1 ORB ORB_000 CL2-K 7 4 - 61456 256G:\Dmt1\Dsk2 ORB ORB_001 CL2-K 7 5 - 61456 257G:\Dmt1\Dsk3 ORB ORB_002 CL2-K 7 6 - 61456 258

raidscan -pi $LETALL -findDEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_IDE:\Vol44\Dsk0 0 F CL2-K 7 2 61456 194 OPEN-3F:\Vol45\Dsk0 0 F CL2-K 7 2 61456 194 OPEN-3G:\Dmt1\Dsk1 0 F CL2-K 7 4 61456 256 OPEN-3G:\Dmt1\Dsk2 0 F CL2-K 7 5 61456 257 OPEN-3G:\Dmt1\Dsk3 0 F CL2-K 7 5 61456 258 OPEN-3


Mountvol attached to Windows 2012/2008/2003/2000 systemsPay attention to the mountvol /D command attached to a Windows system, such that it doesnot flush the system buffer associated with the specified logical drive. The mountvol commandshows the volume mounted as Volume{guid} as follows:mountvolCreates, deletes, or lists a volume mount point...MOUNTVOL [drive:]path VolumeNameMOUNTVOL [drive:]path /DMOUNTVOL [drive:]path /L

\\?\Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}\G:\

\\?\Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}\F:\

You can determine what \\?\Volume{guid}\ is configured, as follows:inqraid $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID\Vol46\Dsk1 CL2-K 61456 193 - S/s/ss 0004 1:01-10 OPEN-3raidscan -pi $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -findDEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID\Vol46\Dsk1 0 F CL2-K 7 1 61456 193 OPEN-3

System buffer flushing functionThe logical drive to be flushed can be specified by the following two methods. One method isthat the logical drive (for example, G:\hd1 drive, as below) is specified immediately, but thismethod must know about the logical drive corresponding to a group before executing the synccommand. Also the volume is mounting by a directory and this method requires finding its volumename. To solve such a complication, RAID Manager supports a method that flushes the systembuffer associated with a logical drive through finding a volume{guid} corresponding to a groupof the configuration file. This method does not depend on mounted point, so that it is possible toflush the volume mounted by a directory. This method is supported to be specified a group tothe raidscan -find sync command.


Figure 70 LDM volume flushing

The following example flushes the system buffer associated with the ORB group through $Volume.raidscan -pi $Volume -find sync -g ORB[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d58d69-00c00d003b1e}[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d58d69-00c00d003b1e}[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d58d69-00c00d003b1e}

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-28d54824-a408-3ff9a6521e5d}[SYNC] : ORA ORA_000[-] -> \Vol45\Dsk0 : Volume{56e4954a-28d54824-a408-3ff9a6521e5e}[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef611d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef611d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef611d5-8d69-00c00d003b1e}

NOTE: Windows NT does not support the LDM volume, so specify $LETALL instead of$Volume.

Offline backup usingraidscan -find syncfor Windows file system:


The raidscan -find sync command flushes the system buffer associated with a logical drivethrough finding a Volume{guid} corresponding to a group of the configuration file, without usingthe -x mount and -x umount commands. The following examples are for group ORB.

S-VOL SideP-VOL Side

Close all logical drives on the P-VOL by application. • Flush the system buffer for NEW S-VOL data usingraidscan -pi $Volume-find sync -g ORB.• Flushthe system buffer for P-VOL using raidscan

-pi $Volume -find sync -g ORB. • Back up the S-VOL data.• Split the paired volume using pairsplit -g ORB with

r/w mode.• Flush the system buffer for S-VOL updates using raidscan

-pi $Volume -find sync -g ORB when the backup isfinished.• Open all logical drives on the P-VOL by application.

• Resynchronize the paired volume using pairresync-g ORB.

Online backup usingraidscan -find syncfor Windows file system:The raidscan -find sync command flushes the system buffer associated with a logical drivethrough finding a Volume{guid} corresponding to a group of the configuration file, without usingthe -x mount and -x umount commands. The following examples are for group ORB.


Freeze DB on opening P-VOL by application. • Flush the system buffer for NEW S-VOL data using raidscan-pi $Volume -find sync -g ORB.• Flushthe system buffer for P-VOL using raidscan

-pi $Volume -find sync -g ORB. • Back up the S-VOL data.• Splits the paired volume using pairsplit -g ORB

with r/w mode.• Flush the system buffer for S-VOL updates using raidscan

-pi $Volume -find sync -g ORB when the backup is finished.• Unfreeze DB on opening P-VOL by application.

• Resynchronize the paired volume usingpairresync -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 drivecorresponding to a group of the configuration file, without using the -x mount and -x umountcommands. The following examples are for group ORB.


Close all logical drives on the P-VOL by application. • Back up the S-VOL data.• Flushthe system buffer for P-VOL using raidscan

-pi $LETALL -find sync -g ORB.• Flush the system buffer for S-VOL updates using raidscan

-pi $LETALL -find sync -g ORB when the backup isfinished.• Split the paired volume using pairsplit -g ORB with

r/w mode.

• Open all logical drives on the P-VOL by application.

• Resynchronize the paired volume using pairresync-g ORB.

Online backup usingraidscan -find syncfor Windows NT file system:


The raidscan -find sync command flushes the system buffer through finding a logical drivecorresponding to a group of the configuration file, without using the -x mount and -x umountcommands. The following examples are for group ORB.


Freeze DB on opening P-VOL by application. • Back up the S-VOL data.• Flushthe system buffer for P-VOL using the

raidscan -pi $LETALL -find sync -g ORB.• Flush the system buffer for S-VOL updates using raidscan

-pi $LETALL -find sync -g ORB when the backup is finished.• Splits the paired volume using pairsplit -g ORB

with r/w mode.

• Unfreeze DB on opening P-VOL by application.

• Resynchronize the paired volume usingpairresync -g ORB.

NOTE:• P-VOL sidemust stop the WRITE IO to the logical drive corresponding to a [-g name] before

issuing the raidscan -find sync command.

• S-VOL side must close the logical drive corresponding to a [-g name] before issuing theraidscan -find sync command.

Special facilities for Windows systemsRAID Manager provides the following special facilities for Windows systems:

• “Signature changing facility for Windows systems” (page 236)

• “GPT disk for Windows” (page 238)

Signature changing facility for Windows systemsConsider the following Microsoft Cluster Server (MSCS) configuration in which a MSCS P-VOLis shared from MSCS Node1 and Node2, and the copied volume of S-VOL is used for backupon Node2. If the Node2 has reboot on standby state, then MSCS of Node2 has a problem toassign drive letter of S-VOL with previous P-VOL drive letter. This problem will happen on Node2on MSCS environment as shown in the following figure. The conditions are:

• Node1 is active.

• Node2 is standby state where P-VOL on Node2 is hidden by MSCS, and reboots the Node2.

Figure 71 Configurations with MSCS and Business Copy (HOMRCF)

MSCS on Node2 will misunderstand the S-VOL as MSCS cluster resource, because the signatureof S-VOL and P-VOL is the same due to copied. The reason is that MSCS cluster resources aremanaged with the signature only. Therefore S-VOL of Node2 will unable to backup so that MSCSof Node2 carry away the S-VOL. This is a problem of MSCS service because Windows system


does change the signature through reboot if the same signature is detected on NO MSCS service.MSCS will not accommodate LUNs with duplicate signatures and partition layout. The best wayto avoid such problems is to transport to another host outside the cluster, but this enforces to setup a backup server, so RAID Manager supports a facility to put back the signature as a secondway.The signature can be changed by using the dumpcfg.exe command attached to Windowsresource kits, but if the S-VOL is created with the Noread option and the system is rebooted,then the dumpcfg.exe command will fail to change the signature, because the system doesnot know the signature and volume layout information for S-VOL.RAID Manager adopts the following way with this point in view:

• You must save the signature and volume layout information to the system disk by using theinqraid -gvinf command, after an S-VOL has set the signature and new partition bythe Windows disk management.

• You can put back the signature by setting the signature and volume layout information toan S-VOL that was saved to the system disk by using the inqraid -svinf command,after splitting the S-VOL. If the S-VOL is created with the Noread option and the system isrebooted, then the system cannot create a device object (\Device\HarddiskVolume#) andVolume{guid} for S-VOL, but the -svinf option will create a Device object(\Device\HarddiskVolume#) and Volume{guid} without using the Windows disk management.

NOTE: The Cluster Disk Driver does not allow using the Noread volume as [Device is notready] at the boot time, since the Cluster Disk Driver is a Non-Plug and Play Driver. Verify thissituation using the inqraid command as follows:

inqraid $Phy -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDHarddisk0 - - - - - - - -Harddisk1 - - - - - - - -

In this case, do the following to disable the Cluster Disk Driver:1. In the Computer Managementwindow, double-click System Tools, and then click Device

Manager.2. On the View menu, click Show Hidden Devices. Non-Plug and Play Drivers appear in the

list in the right pane.3. Open Non-Plug and Play Drivers, right-click Cluster Disk, and then click Disable. When

prompted to confirm whether to disable the cluster disk, click Yes. When prompted to restartthe computer, click Yes.

4. Verify that you can see the Noread volume using inqraid command as follows.inqraid $Phy -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDHarddisk0 CL2-K 61456 194 - s/S/ss 0004 1:01-10 OPEN-3Harddisk1 CL2-K 61456 256 - s/S/ss 0005 1:01-11 OPEN-3

5. After starting up RAID Manager and splitting the S-VOL, put back the signature by using theinqraid -svinf command.

6. Again, in the Computer Management window, enable the Cluster Disk Driver, and restartthe computer.

Special facilities for Windows systems 237

GPT disk for WindowsWindows supports the basic disk called GPT disk using GUID partition instead of the Signature.The GPT disk also can be used as an S-VOL of the BC. Therefore, RAID Manager supportssaving/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 devicefile provided via STDIN or arguments, and saves it in a system disk file with the followingformat:\WindowsDirectory\VOLssss_llll.ini

wheressss = serial#

llll = LDEV#

Normally, this option is used to save the Disk signature/ GUID DiskId and volume layoutinformation once, after it has been written on a potential (and before its paircreate). You donot need to directly view these host files.For example, saves the volume information for all physical drives:D:\HORCM\etc>inqraid $Phys -gvinfex -CLI\\.\PhysicalDrive10:# Harddisk10 -> [VOL61459_448_DA7C0D91] [OPEN-V ]\\.\PhysicalDrive11:# Harddisk11 -> [VOL61459_449_D4CB5F17-2ADC-4FEE-8650D3628379E8F5] [OPEN-V ]\\.\PhysicalDrive12:# Harddisk12 -> [VOL61459_450_9ABDCB73-3BA1-4048-9E9422E3798C3B61] [OPEN-V ]

• -svinfex[=PTN] option (Windows 2003 only)This option writes LUN signature/GUID DiskId and volume layout information (that hadpreviously been saved in a system disk file) by way of a raw device file provided via STDINor arguments.This option gets the serial# and LDEV# of the RAID storage system for the target deviceusing SCSI Inquiry, and writes the signature/GUID DiskId and volume layout informationfrom the VOLssss_llll.ini file to the target device.This option will work correctly (even if Harddisk# changes due to configuration changes)because the signature/GUID DiskId and volume layout information is associated the arrayserial# and LDEV# (not Harddisk#).

• [=PTN]This option specifies a string pattern usable to select only the pertinent output lines beingprovide from STDIN. If used as shown, only the pairdisplay output lines containingHarddisk would be used to cause signature writing.D:\HORCM\etc>pairdisplay -l -fd -g URA | inqraid -svinfex=Harddisk[VOL61459_448_DA7C0D91] -> Harddisk10 [OPEN-V ][VOL61459_449_D4CB5F17-2ADC-4FEE-8650-D3628379E8F5] ->Harddisk11 [OPEN-V ][VOL61459_450_9ABDCB73-3BA1-4048-9E94-22E3798C3B61] ->Harddisk12 [OPEN-V ]


• -gplbaex option (Windows 2012/2008 Only)This option is used for displaying usable LBA on a Physical drive in units of 512 bytes, andis used to specify [slba] [elba] options for raidvchkset command.C:\HORCM\Tool>inqraid -CLI -gplbaex hd10,13Harddisk10 : SLBA = 0x0000003f ELBA = 0x013fe5d9 PCNT = 1 [OPEN-V

]Harddisk11 : SLBA = 0x00000022 ELBA = 0x013fffdf PCNT = 2 [OPEN-V

]Harddisk12 : SLBA = 0x00000022 ELBA = 0x013fffdf PCNT = 3 [OPEN-V

]

SLBA: displays usable starting LBA in units of 512 bytesELBA: displays usable ending LBA (ELBA -1) in units of 512 bytesPCNT: displays the number of partitions

Directory mount facility for Windows systemsThe attached mountvol command into Windows supports the directory mount, but it does notsupport the directory mount function that flushes the system buffer associated to a logical drivesuch as in UNIX systems. The directory mount structure on Windows is only symbolical linkbetween a directory and Volume{guid}, illustrated in Figure 72 (page 239) below. As such, RAIDManager supports the function to discover the mounted volumes by a directory, and supportsthe operation to mount/unmount with the subcommand option.

Figure 72 Directory mount structure

Volume discovery for directory mounted volume: RAID Manager can discover the directorymounted volume by using $LETALL that shows the relationship between logical drive and thephysical volumes. The KEY WORD ($LETALL)can also be used with the raidscan -findand mkconf commands.D:\HORCM\etc>inqraid $LETALL -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDD:\Vol2\Dsk7 - - - - - - - DDRS-34560DD:\hd1\Vol8\Dsk0 CL2-F 61459 448 - s/s/ss 0005 1:01-01 OPEN-3D:\hd2\Vol9\Dsk1 CL2-F 61459 449 - s/s/ss 0005 1:01-01 OPEN-3G:\Dms1\Dsk2 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3

Special facilities for Windows systems 239

G:\Dms1\Dsk3 CL2-K 61456 257 - s/s/ss 0005 1:01-11 OPEN-3G:\Dms1\Dsk4 CL2-K 61456 258 - s/s/ss 0005 1:01-11 OPEN-3

Subcommand for directory mounted volume: RAID Manager supports the directory mountwith the -x mount,-x unmount,-x sync option so that the directory mount can be used tomount/unmount the S-VOL.Mount and Sync used Volume{GUID} for Windows: RAID Manager supports themountcommand option specified in the device object name, such as \Device\HarddiskvolumeX. Windows changes the device number for the device object name after recovering from a failureof the PhysicalDrive. As a result, the mountcommand specified in the device object name mightfail. Therefore, RAID Manager supports a mountcommand option that specifies a Volume{GUID}as well as the device object name.

• Mount

◦ The mountcommand option specifies a Volume{GUID} as well as the device objectname.

◦ If a Volume{GUID} is specified, then it is executed by converting a Volume{GUID} to adevice object name.

◦ Discover the Volume{GUID}s by using inqraid $Volu -fv command option.

Examples:C:\HORCM\etc>inqraid -CLI $Vol -fvDEVICE_FILE PORT SERIAL LDEVCTG H/M/12 SSID R:Group PRODUCT_IDVolume{cec25efe-d3b8-11d4-aead-00c00d003b1e}\Vol3\Dsk0 CL2-D62496 256 - - - - OPEN-3-CVS-CM

[ Mount used DefineDosDevice() ]

NOTE: This might forcibly dismount the mounted volume due to LOG-OFF of Windows. Forexample:

C:\HORCM\etc>raidscan -x mount E: Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}E: <+> HarddiskVolume3

[ Mount used Directory mount ]

NOTE: This prevents the forcible removal of a volume due to LOG-OFF of Windows. Forexample:

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 thedevice object name.

◦ If a Volume{GUID} is specified, then it is executed by converting a Volume{GUID} to adevice object name.

Example:C:\HORCM\etc>raidscan -x sync Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}[SYNC] Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}

Host group controlThe RAID storage systems have the defined host group in the port and can allocate a host LUfor every host group. RAID Manager does not use this host LU, and specifies an absolute LUNin the port. To eliminate confusion that LUN of the RAID Manager notation does not correspond


to LUN on the host view and Remote Web Console, RAID Manager supports specifying a hostgroup and LUN on the host view.

Specifying a host group(1) Defining the formatsThe addition of arguments for the host group to the raidscan command and the configurationfile means that it is not compatible with conventional CLI. Therefore, RAID Manager provides away to support CLI by specifying a host group in the port strings as follows.

• CL1-A-GRP# (GRP# can be up to 127)Specifying the host group for the raidscan command:raidscan -p CL1-A-5Specifying the host group for the configuration file:#dev_group dev_name port# TargetID LU# MU#ORA ORA_000 CL2-D-1 4 1 0ORA ORA_001 CL2-D-1 4 2 0

If the port including a host group is specified to the port name, then a maximum of 255 LUNscan be specified.(2) Specifiable port stringsAs a result, RAID Manager supports four kinds of forms for the port name.

• Specifying the port name without a host groupCL1-ACL1-An where n: unit ID for multiple RAID

• Specifying the port name with a host groupCL1-A-g where g: host groupCL1-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 groupThe following commands can specify a host group with the port strings:

• raidscan -p <port#>, raidar -p <port#>, raidvchkscan -p <port#># raidscan -p CL2-D-1PORT# /ALPA/C,TID#,LU#.Num(LDEV#....)...P/S, Status,Fence,LDEV#,P-Seq#,P-LDEV#CL2-D-1 /da/ 0, 4, 0.1(256)...........SMPL ---- ------ ----, ----- ----CL2-D-1 /da/ 0, 4, 1.1(257)...........SMPL ---- ------ ----, ----- ----CL2-D-1 /da/ 0, 4, 2.1(258)...........SMPL ---- ------ ----, ----- ----

(2) Command option including a host groupRAID Manager supports new option for the following commands in order to show a LUN on thehost view by finding a host group via the specified device.

• raidscan -pdg <device>, raidar -pdg <device>, raidvchkscan -pdg <device># raidscan -pdg /dev/rdsk/c57t4d1PORT# /ALPA/C,TID#,LU#.Num(LDEV#....)...P/S, Status,Fence,LDEV#,P-Seq#,P-LDEV#CL2-D-1 /da/ 0, 4, 0.1(256)...........SMPL ---- ------ ----, ----- ----CL2-D-1 /da/ 0, 4, 1.1(257)...........SMPL ---- ------ ----, ----- ----CL2-D-1 /da/ 0, 4, 2.1(258)...........SMPL ---- ------ ----, ----- ----Specified device(hgrp=1) is LDEV# 0257

• raidscan -findg# ls /dev/rdsk/c57* | raidscan -findgDEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID

Host group control 241

/dev/rdsk/c57t4d0 0 F CL2-D-1 4 0 62500 256 OPEN3-CVS-CM/dev/rdsk/c57t4d1 0 F CL2-D-1 4 1 62500 257 OPEN3-CVS/dev/rdsk/c57t4d2 0 F CL2-D-1 4 2 62500 258 OPEN3-CVS

• raidscan -findg conf, mkconf -gg# ls /dev/rdsk/c57* | raidscan -findg conf 0 -g ORAHORCM_DEV#dev_group dev_name port# TargetID LU# MU## /dev/rdsk/c57t4d1 SER = 62500 LDEV = 257 [ FIBRE FCTBL = 4 ]ORA ORA_000 CL2-D-1 4 1 0# /dev/rdsk/c57t4d2 SER = 62500 LDEV = 258 [ FIBRE FCTBL = 4 ]ORA ORA_001 CL2-D-1 4 2 0

• inqraid -fg# ls /dev/rdsk/c57* | ./inqraid -CLI -fgDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDc57t4d0 CL2-D-1 62500 256 - - - - OPEN-3-CVS-CMc57t4d1 CL2-D-1 62500 257 - s/P/ss 0005 1:01-02 OPEN-3-CVSc57t4d2 CL2-D-1 62500 258 - s/P/ss 0005 1:01-02 OPEN-3-CVS

Using RAID Manager SLPR securityThe Cache Partition feature of the RAID storage systems (XP24000/XP20000 Disk Array andXP12000 Disk Array/XP10000 Disk Array) supports storage logical partitioning (SLPR), a featurethat partitions the ports and volumes of the RAID storage system. If RAID Manager does nothave SLPR security, then it can operate the target volumes crossing SLPR through the commanddevice. The purpose of RAID Manager SLPR security is to prevent RAID Manager from operatingthe volumes on another SLPR (SLPR#N) through the command device from the SLPR (SLPR#M)that is assigned to its Host. You can use RAID Manager SLPR Security by defining the commanddevice through the Cache Partition feature, so that RAID Manager can protect the target volume.The following example represents the SLPR protection facility.

Figure 73 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 FacilityWhen you want to access certain SLPRs on a single Host, use the RAID Manager protectionfacility so that the Host can access multiple SLPRs through a single command device. Thefollowing outline reviews the setup tasks for the SLPR protection facility.1. Setting SLPR on the command device: The command device has an SLPR number and

an associated bitmap so you can set multiple SLPRs. You accomplish this by sharing acommand device (using ports connected to different SLPRs) by setting the command devicethrough SLPR#0 (called Storage Administrator) on Remote Web Console.For example, if the command device is shared with the port on SLPR#1 and SLPR#2, thenthe command device will automatically set the bitmap corresponding to SLPR#1 and SLPR#2.

2. Testing SLPR: RAID Manager verifies whether or not the command device can access atarget within SLPR. So, if the command device belongs to SLPR#0, or RAID Manager hasno SLPR function, then the SLPR protection is ignored.However, if the command device is shared with the port on SLPR#1 and SLPR#2, RAIDManager allows you to operate the volume on SLPR#1 and SLPR#2.

3. Rejecting commands: If access is denied on the specified port (or target volume), RAIDManager rejects the following commands and outputs an error code, EX_ESPERM:• horctakeover,paircurchk,paircreate,pairsplit,pairresync,pairvolchk,

pairevtwait, pairsyncwait

• raidscan (except -find verify, -find inst), raidar, pairdisplay

• raidvchkset, raidvchkscan (except -v jnl), raidvchkdsp[EX_ESPERM] Permission denied with the SLPR[Cause ] : A specified command device does not have apermission to access other SLPR.[Action] : Please make the SLPR so that the target port andthe command device belongs to the same SLPR.

SLPR configuration examples

Single hostFigure 74 (page 244) provides an example of when control is denied to the paircreate andraidscan commands in the following cases:

• The volume described on RMINST1 is different from the SLPR of the command device, sothe paircreate command cannot control the paired volume.

• The specified port is different from the SLPR of the command device, so the raidscan -pCL3-A command cannot scan any ports that are defined as SLPR#N.

Using RAID Manager SLPR security 243

Figure 74 SLPR configuration on a single host

To operate SLPR#N, assign the command device. If RMINST1 has been assigned to acommand device for SLPR#N, the paircreate command is permitted. However, the raidscan-p CL3-A command (via RMINST0) is unable to scan a port, because the specified port isdifferent than the SLPR of the command device. In this case, -p CL3-A must be operated viaRMINST1, as shown in the following example.

Figure 75 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 devicefor SLPR#N, the paircreate command is permitted. Additionally, the raidscan -p CL3-Acommand (via RMINST0), is permitted to scan a port, because the shared command device hasthe Bitmap settings SLPR#M and SLPR#N.


Figure 76 Operation across SLPRs using a shared command device on a single host

Dual HostsIn the following example, the paircreate command is unable to operate the paired volumebecause the volume described on HostB is different than the SLPR of the command device. Also,the raidscan -p CL3-A command (via both Hosts), is unable to scan a port because thespecified port is different than the SLPR of the command device.

Figure 77 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 viaHostA is unable to scan a port because the specified port is different than the SLPR of thecommand device. In this case, raidscan -p CL3-A command must be operated via HostB.


Figure 78 Operation across SLPRs using two command devices on dual hosts

To operate SLPR#N, share the command device. If HostB has a shared command device forSLPR#N, the paircreate command is permitted. Also, the raidscan -p CL3-A command(via HostA), is allowed to scan a port because the shared command device has the Bitmapsettings SLPR#M and SLPR#N.

Figure 79 Operating SLPR#N by sharing the command device

Continuous Access Synchronous using dual hostsIn the following example, the pair-operation command (except the -l option) determineswhether the operation for paired volumes should be permitted at a remote site. The result is thatthe paircreate command is not allowed to operate the paired volume, because the volumedescribed on HostB differs from the SLPR of the command device. Also, the raidscan -pCL3-A command (on HostB) is not allowed to scan a port.


Figure 80 Continuous Access Synchronous operation using SLPR


9 TroubleshootingThis chapter provides troubleshooting information for RAID Manager.

General troubleshootingIf you have a problem with the RAID Manager software, first make sure that the problem is notbeing caused by the UNIX/PC server hardware or software, and try restarting the server.

Recommended actionProblem

RAID Manager currently uses the ioctl(SCSI_IOCTL_SEND_COMMAND) for sending thecontrol command to the command device. However, in RHEL 4.0 using kernel 2.6.9.xx, thefollowing message is output to syslog file(/var/log/messages) with every ioctl():

DeprecatedSCSI ioctlThe following messageis output to syslog

program horcmgr is using a deprecated SCSI ioctl, please convert itto SG_IO

file(/var/log/messages)with every ioctl():

This can originate from the following kernel code in drivers/scsi/scsi_ioctl.c as way of warningthat ioctl(SCSI_IOCTL_…) of kernel 2.6.9.xx does not properly handle an error of the HBAdriver.

program horcmgris using adeprecated SCSIioctl, please

----------------------------------------------------------------------convert it toSG_IO /* Check for deprecated ioctls ... all the ioctls that do not follow

the new unique numbering scheme are deprecated */

switch (cmd) {

case SCSI_IOCTL_SEND_COMMAND:

case SCSI_IOCTL_TEST_UNIT_READY:

case SCSI_IOCTL_BENCHMARK_COMMAND:

case SCSI_IOCTL_SYNC:

case SCSI_IOCTL_START_UNIT:

case SCSI_IOCTL_STOP_UNIT:

printk(KERN_WARNING "program %s is using a deprecatedSCSI "

"ioctl, please convert it to SG_IO\n",current->comm);

---------------------------------------------------------------------

Thus, RAID Manager supports a way to change to the ioctl(SG_IO) automatically, if Linuxkernel supports the ioctl(SG_IO) for horcmgr and inqraid command. However, RAIDManager might encounter Linux kernel that does not support the ioctl(SG_IO) fully, so RAIDManager also supports by defining either following environment variable or"/HORCM/etc/USE_OLD_IOCTL" file(size=0) that uses theioctl(SCSI_IOCTL_SEND_COMMAND) forcibly. For example:export USE_OLD_IOCTL=1horcmstart.sh 10HORCM/etc:

-rw-r--r-- 1 root root 0 Nov 11 11:12 USE_OLD_IOCTL

-r--r--r-- 1 root sys 32651 Nov 10 20:02 horcm.conf

-r-xr--r-- 1 root sys 282713 Nov 10 20:02 horcmgr

If you have changed the configuration definition file settings: make sure that the configurationdefinition file you changed is correct.

RAID Manager cannotbe started because

If you have changed the settings of the storage system: make sure that the settings youchanged are correct, and if necessary, change the configuration definition file settings.

horcmstart commandfails

Even if there are no problems in these files and settings, but if you cannot run RAID Manager,get all log files under the specified directory by HORCM_LOG (the default setting:/horcm/log/), and then contact HPE technical support.

These messages are output if the path for the PA-RISC version shared library (libcl.sl) isnot set when you use RAID Manager on HP-UX (IA64).

The followingmessages are output

248 Troubleshooting

Recommended actionProblem

Set the path of the libcl.sl to the LD_PRELOAD environment variable.to the standard erroroutput with everycommand I/O:

Example: # export LD_PRELOAD=/path/libcl.sl

Enter the absolute path for specifying the directory where libcl.sl is stored into path."/usr/lib/dld.sl:Can't shl_load()a librarycontaining ThreadLocal Storage: /usr/lib/libcl.sl"

"/usr/lib/dld.sl:Exec formaterror"

Operational notes and restrictions for RAID Manager operationsFor maintenance of volumes used by RAID Manager and the HPE features it supports, if a volumefailure occurs, it is important to find the failure in the paired volumes, recover the volumes, andcontinue operation on the original system. When a RAID Manager (HORCM) or HPE featurefailure is detected, please collect the data in the error log file and trace data (all files inHORCM_LOG directory), and report the failure to your HPE representative.

Notes and restrictionsItems

When the server starts up, sometimes a volume group (VG) is activated by the LVM, ora file system is mounted automatically, and the host writes to the S-VOL. When this

Startup restrictions

happens, if the S-VOL does not permit writing, data cannot be written and the operationfails. To avoid this failure, change the S-VOL to PSUS (R/W enable) or to the SMPL stateand restart the server.

Note the following when executing hot standby operations using industry-standard failoverproducts (for example, MC/ServiceGuard, HACMP, FirstWatch®) and Continuous AccessSynchronous/ Continuous Access Asynchronous/ Continuous Access Journal.

Hot standby operations

• Do not split a single volume using partitions and share it among different serverprograms. If you do so, the takeover command is executed for the volume when failoverof a server program happens, and that might affect other servers that share the volume.

• If you are using the LVM, do not create LDEVs for different LVM within the samevolume. If you do so, the takeover command is executed for the volume when failoverof a server program happens, and that might affect other servers that share the volume.

When the LVM mirror and Continuous Access Synchronous volumes are used together,the LVM mirror handles write errors and changes the volumes. Thus, the fence level ofthe volumes used by the LVM mirror must be set to data.

Coexistence of LVMmirror and ContinuousAccess Synchronous

When constructing paired volume in a single host, it is necessary to activate two or moreRAID Manager instances. To activate two or more RAID Manager instances, instance

Using paired volume in asingle host

numbers must be assigned using the environment variable HORCMINST. The HORCMand Continuous Access Synchronous/Business Copy commands must possess thisenvironment variable.A configuration definition file and a log directory is set for each instance. For sharingcommand devices over 17 instances, use LU path among the storage system ports toshare the command devices.

When paired volume is used for the disk shared by the hosts in hot standby configurationusing HA software, use the primary volume as the shared disk and describe the

Sharing volumes in a hotstandby configuration

corresponding hosts using the paired volume in the configuration definition file as shownbelow. In the HA configuration, if a Continuous Access Synchronous command issuedby host C fails in host B (because host B has gone down and/or IO_ERROR of thecommand device), host A is connected and the command execution is retried.

Operational notes and restrictions for RAID Manager operations 249


The HORC Manager must not be an object of the process monitoring by the HA software(cluster manager), because HORCM should run in the same level as the cluster manager.

Linkage with HA software

Cooperation with HA software is done by activating the takeover command from the shellscript activated by the cluster manager in units of the package software.Note: Cannot use a pair volume for the cluster lock disk that HA software uses for election.

Restart of HORCM is required if the storage system configuration is changed (for example,microcode exchange, cache memory install/uninstall).

Maintenance

Continuous Access Synchronous only: In the case of an error (for example, single errorin cache memory) which made the pair volume is accompanied by maintenance work,the pairresync or paircreate command cannot execute copy rejection.

In out-of-band method using an SVP, if the microcode exchange of the SVP is performed,the timeout on command occurs. Execute the command again after finishing the microcodeexchange.

SVP microcodeexchange

Each Continuous Access Synchronous/Business Copy command is executed by issuinga command to the command device. The Continuous Access Synchronous/Business

Command device

Copy command is read or written from/into the specific block area of the command device.Therefore, the command device cannot be used. In addition, this device must not belongto an LVM volume group. For Windows systems, do not assign a drive letter to thecommand device to prevent utilization by general users.

If the P-VOL and S-VOL are on the same server, alternate path from P-VOL to S-VOLcannot be used. Use of SCSI alternate path to a volume pair in the pair status is limited

SCSI alternate pathrestrictions

to among primary (secondary) volumes. Alternate path using Path Manager (Safe Path)is limited to primary volumes.

When executing horctakeover on a standby server manually, I/O on the active servermust be stopped. When the package software goes for a standby server a failover by HAsoftware, the HA software must guarantee an I/O insulation of the active server.

horctakeover(Swap-Takeover)

After a new system has been constructed, a failure to activate HORCM might occur dueto improper environment setting and/or configuration definition. Refer to the HORCMactivation log, and correct the settings.

HORCM failure toactivate

Refer to the command log file and HORCM log file to identify the cause of the error. If acommand terminates abnormally because of a remote server failure, recover the server

Abnormal termination ofcommand

from the failure, then re-execute the command. If HORCM has shut down, restart HORCM.If an unrecoverable error occurs, obtain the log files and contact HPE technical support.

Continuous Access Synchronous only: If an error occurs in duplicated writing in pairedvolumes (that is, pair suspension), the server software using the volumes might detect

Error in paired volumeoperation

250 Troubleshooting


the error by means of the fence level of the paired volume. In such a case, check theerror notification command or syslog file to identify a failed paired volume.The system administrator can confirm that duplicated writing in a paired volume issuspended due to a failure and the system runs in regressed state using the errornotification command of the Continuous Access Synchronous. HORCM monitors failuresin paired volumes at regular intervals. When it detects a failure, it outputs it to the host'ssyslog file. Thus, the system administrator can detect the failure by checking the syslogfile. Concerning the operation of the RAID storage system, the failure can also be foundon Remote Web Console (or SVP) provided.Issue the Continuous Access Synchronous commands manually to the identified failedpaired volume to try to recover it. If the secondary volume is proved to be the failed volume,issue the pair resynchronization command to recover it. If the primary volume fails, deletethe paired volume (pair splitting simplex) and use the secondary volume as the substitutevolume.

RAID Manager uses "/var/tmp" or "/usr/tmp" as the directory for the UNIX domain socketfor IPC (Inter Process Communication), and makes the directory and files as"/var/tmp/.lcm*" in RAID Manager version 01-16-03/06 or later.

About "/var(usr)/tmp"directory

Caution: This "/var/tmp/.lcm*" should not be removed while HORCM is running.On Red Hat Linux, Cron executes the following "/etc/cron.daily/tmpwatch" file as default:------------------------------------------------------------

/usr/sbin/tmpwatch 240 /tmp

/usr/sbin/tmpwatch 720 /var/tmp

for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do

if [ -d "$d" ]; then

/usr/sbin/tmpwatch -f 720 $d

fi

done

------------------------------------------------------------

The command of second line will remove "/var/tmp/.lcm*" directory after 720 Hr fromHORCM startup, even though RAID Manager command is used.Action: So administrator needs to add the following command in order to avoid thisproblem:------------------------------------------------------------

/bin/touch -c /var/tmp/.lcm* 2>/dev/null/usr/sbin/tmpwatch 240 /tmp

/usr/sbin/tmpwatch 720 /var/tmp

for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do

if [ -d "$d" ]; then

/usr/sbin/tmpwatch -f 720 $d

fi

done

------------------------------------------------------------

Error messages and error codesSystem log messages

The following table lists and describes the HORCM system log messages and providesrecommended actions for resolving the error conditions.

Error messages and error codes 251

Table 50 System log messages

Recommended actionCauseConditionMessage ID

Create space on the disk on which theroot directory resides.

The file cannot be created in theHORCM directory.

The HORCM log file cannotbe opened.

HORCM_001

Create space on the disk on which theroot directory resides.

The file cannot be created in theHORCM directory.

The HORCM trace filecannot be opened.

HORCM_002

Terminate unnecessary programs ordaemon processes runningsimultaneously.

HORCM daemon attempted tocreate more processes than themaximum allowable number.

The HORCM daemonprocess cannot create achild process due to anerror.

HORCM_003

Restart the system, and contact HPEtechnical support.

An internal error that could notbe identified by the HORCMoccurred.

HORCM assertion failed,resulting in a fatal internalerror in the HORCM.

HORCM_004

Refer to the HORCM startup log toidentify the cause of the error.

HORCM failed to create asocket, or an error exists in the

The RAID Managersoftware failed to create the

HORCM_005

format or a parameter in theend point for remotecommunication. HORCM configuration definition

file ($HORCM_CONF).

Increase the system virtual memory, orclose any unnecessary programs.

HORCM memory could not besecured.

HORCM memory allocationfailed.

HORCM_006

Refer to the startup log and reset theparameters.

An error exists in the parametervalue setting in the HORCMsetup file.

An error exists in theparameter value in theHORCM setup file.

HORCM_007


An error exists in the format orparameters of the HORCM

HORCM configurationdefinition file parametersreading fails.

HORCM_008

configuration definition file($HORCM_CONF).


System devices are improperlyconnected, or an error exists in

Continuous AccessSynchronous/Business

HORCM_009

the device parameter in theCopy connection to theHORCM configuration definitionfile.

RAID Manager softwarefailed.


A system I/O error occurred oran error exists in the device

Continuous AccessSynchronous/Business

HORCM_101

parameter in the HORCMCopy and the RAIDconfiguration definition file($HORCM_CONF).

Manager softwarecommunication fails.

Contact HPE technical support.The pair status was suspendeddue to code XXXX.

The volume is suspended.HORCM_102

Please confirm the following items, anduse raidvchkdsp -v <op> commandfor verifying the validation parameters.

A validation error occurs on thedatabase volume, or validationparameters for this volume areillegal.

Detected a validation checkerror on this volume (xxxxunit#x,ldev#x): CfEC=n,MNEC=n, SCEC=n,BNEC=n

HORCM_103

(1)Check if the block size (-vs <size>) isan appropriate size.(2)Check if the type for checking (-vt<type>) is an appropriate type.(3)Check if the data validations aredisabled for LVM configuration changes.(4)Check if the data validations are notshared on file system.(5)Check if the redo log and data file areseparated among the volumes.

252 Troubleshooting

Command error messagesThe following table lists and describes the command error messages and their return values andprovides recommended action for resolving the error conditions.The messages below are typical command error messages. Check the command log file fordetails of the error. For details about the command log file, see “RAID Manager log files” (page 48).

Table 51 Command error messages

ReturnedValue

Recommended actionConditionErrormessage

Errorcode

255Confirm whether HORCM is enabled. If HORCMis not activated yet, start HORCM. If HORCM

This command failed tocommunicate with the RAIDManager software.

Can't becommunicatewith HORCManager

EX_COMERR

ended abnormally despite being activated, verifythe disk capacity has 3000 KB or more free space.Free up disk space, and then restart HORCM. Ifthe problem persists, contact HPE technicalsupport.

254Please designate the correct option using the -hoption.

An option or arguments of anoption are not sufficient.

RequiredArg list

EX_REQARG


An option or arguments of anoption are incorrect.

Invalidargument

EX_INVARG


Designated an unknown option.Unknownoption

EX_UNWOPT

251Please verify that HORCM is running and/or thatHORCMINST is set correctly.

Could not connect with HORCM.Can't beattached to

EX_ATTHOR

HORCManager

250Verify that HORCM is running by using UNIXcommands [ps - ef | grep horcm].

Failed to communicate withHORCM, or cannot make a logdirectory file.

Can't beattached toa Debuglayer

EX_ATTDBG

249Please designate the correct name using the -hoption.

The name specified in anargument of an option is notappropriate.

Invalidname ofoption

EX_INVNAM

248Contact HPE technical support.Detected contradiction ininformation that RAID reported.

A specifiedoption isinvalid

EX_OPTINV

247Verify the device or group name and add it to theconfiguration definition file of the remote and localhosts.

The designated device or groupname does not exist in theconfiguration definition file.

No suchdevice orgroup

EX_ENOENT

246Verify the device name and add it to theconfiguration definition file of the remote and localhosts.

The designated device name doesnot exist in the configurationdefinition file.

No suchdevice

EX_ENODEV

219Verify the RAID unit ID and add it to theconfiguration definition file of the remote and localhosts.

The designated RAID unit ID doesnot exist in the configurationdefinition file.

No suchRAID unit

EX_ENOUNT

218Confirm the serial# (Seq#) of the storage systemusing the pairdisplay command, or confirm

The group designated by BusinessCopy paircreate does not have thesame RAID unit, or the unitID is

UnmatchedSerial# vsRAID unitID

EX_ENQSER

that the serial# (Seq#) and the unit ID of storagenot identical to the unit ID in thesame RAID serial# (Seq#).

system are the same among hosts using theraidqry -r command.

245Increase the virtual memory capacity of thesystem, or close any unnecessary programsand/or daemon processes.

Insufficient memory exists.Not enoughcore

EX_ENOMEM


Table 51 Command error messages (continued)

ReturnedValue


Errorcode

131Confirm the execution right, permission theextension, the execution path of the script file.

The script file specified by the -ztoption cannot be performed.

Cannotexecutescript file

EW_ENESCR

244Refer to the error message, and designate anappropriate value or confirm whether you specifiedthe unit correctly.

Your entry is one of the followingstatuses.

Result toolarge

EX_ERANGE

• The value was entered beyondthe maximum.

• The result value is beyond themaximum.

• The unit you set is invalid.

243Contact HPE technical support.Undefined error.File nametoo long

EX_ENAMLG

242Please confirm that the HORC Manager in theremote host is running, and then increase the

A timeout occurred on remotecommunication, and HORCManager failed to re-execute.

No remotehost alivefor remote

EX_ENORMT

value of the timeout in the configuration definitionfile.commands

or remoteHORCMmight beblocked(sleeping)on anexisting I/O

241Contact HPE technical support.Detected a contradiction for acommand.

InvalidRAID

EX_INVMOD

commandmode

240Contact HPE technical support.Detected a contradiction for acommand.

InvalidRAIDcommand

EX_INVCMD

239Verify the device or group name and add it to theconfiguration definition file of the remote and localhosts.

The designated device or groupname does not exist in theconfiguration definition file, or the

No suchgroup

EX_ENOGRP

network address for remotecommunication does not exist.

238Retry your operation after restart of the instancefor RAID Manager. Contact HPE technical supportif the operation fails because of same error again.

Detected a contradiction for acommand.

Unknownfunctioncode

EX_UNWCOD

237Refer to the host syslog file, and investigate thecause of the error.

A read/write to the commanddevice failed with an I/O error.

ControlcommandI/O error

EX_CMDIOE

If the problem persists, collect the log informationof HORCM ($HORCM_LOG), and contact HPEtechnical support.

221Verify the program products, such as ContinuousAccess Synchronous and Business Copy, areinstalled.

The request to the commanddevice failed or was rejected.Note: This error code issometimes caused by the

An order tothecontrol/commanddevice wasrejected

EX_CMDRJE

Verify ports are set.Verify CU paths have been established by RemoteWeb Console, RAID Manager, or other methods.

operating system and reported asEX_CMDIOE instead ofEX_CMDRJE (see next row).

Verify that the target volume is available.

254 Troubleshooting


ReturnedValue


Errorcode

RAID Manager displays "SSB" in the output of thecommands so a service representative can identifythe cause of EX_CMDRJE (except for Tru64,DYNIX).Example:# paircreate -g G1 -f never -vl-nocopy

paircreate: [EX_CMDRJE] An order tothe control/command device wasrejected

Refer to the command log (/HORCM/log10/horcc_u1-1.log) for details.

It was rejected due to SKEY=0x05,ASC=0x26, SSB=0xB9BF,0xB9C7 onSerial#(63502).

237Refer to the host syslog file, and investigate thecause of the error. If the cause is "Illegal Request

A read/write to the commanddevice failed with an I/O error orwas rejected.

ControlcommandI/O error orrejected

EX_CMDIOE

(0x05)" Sense Key, please confirm the followingitems.Verify the program products, such as ContinuousAccess Synchronous and Business Copy, areinstalled.Verify ports are set.Verify CU paths have been established by RemoteWeb Console, RAID Manager, or other methods.Verify that the volume which is the target of thepair operation is in the appropriate status forissuing the concerned command.Verify that the status of the volume which is thetarget of the pair operation changed to theintended status after 160 or more seconds havepassed since the concerned command issued.

• When the status has changed as you intended:The command executed normally. Thecommunication delay or other errors mayhappen. Confirm the path between the storagesystems.

• When the status has not changed: Issue theconcerned command again. If the phenomenonhappens again, contact HPE technical support.

• Other than above: Contact HPE technicalsupport.

If the problem persists, contact HPE technicalsupport.

236Confirm status using the pairdisplaycommand. Make sure all volumes in the grouphave the same fence level and volume attributes.

The volume attribute or the fencelevel within a group is not identical.

Unmatchedvolumestatus withinthe group

EX_ENQVOL

235Confirm volume status using the pairdisplaycommand, and change the combination ofvolumes properly.

Combination of a volume isunsuitable between the remoteand local host.

Pair Volumecombinationerror

EX_EVOLCE



ReturnedValue


Errorcode

234Please issue the pairresync commandmanually to the identified failed paired volume totry to recover it.

Detected a suspended status(PSUE) for the paired volume,before it made it to the designatedstatus.

Pairsuspendedat WAITstate

EX_EWSUSE

If the problem persists, contact HPE technicalsupport.

233Please increase the value of the timeout usingthe -t option. For details, refer to the

Detected a time out, before itmade it to the designated status.

Timeoutwaiting for

EX_EWSTOT

troubleshooting information in the relevant userdocument.

specifiedstatus

232Please confirm that HORC Manager on the remotehost is running.

Timeout error because the remotedid not notify about expectedstatus in time.

Timeoutwaiting forspecified

EX_EWSLTO

status onthe localhost

231Please confirm the value of "poll" in theconfiguration definition file.

HORC Manager monitoring wasrefused.

HORCMMonitorstopped

EX_ESTMON

230Please confirm the command name.An unknown command wasattempted.

Unknowncommand

EX_UNWCMD

229Please confirm the pair status using thepairdisplay command.

The pair status of a volume withina group is not identical to thestatus of the other volumes in thegroup.

Inconsistentstatus ingroup

EX_INCSTG

228Please confirm the pair status using thepairdisplay command.

The pair status of the targetvolume is not appropriate.

Invalid pairstatus

EX_INVSTP

222Please confirm the volume status using thepairdisplay -l or the raidvchkdsp -v aoucommand.

The volume status of the targetvolume is not appropriate.

Invalidvolumestatus

EX_INVVOL

220Please confirm the MU# (MU #1/2 cannot be usedfor Continuous Access Synchronous and must be

The MU# of the volume to beoperated is not appropriate.

Invalid mu#with

EX_INVMUN

P-VOL for Business Copy.) for the specified groupHORC/Cntusing the pairdisplay command. And alsoAc-J or

HOMRCF confirm the command execution environment tobe set as HOMRCF.

227Please confirm that the Port, Target ID, LUN aredefined correctly under HORCM_DEV in theconfiguration definition file.

A device defined in theconfiguration definition file doesnot have a mapping to a real LUN

No suchLDEV withinthe RAID

EX_ENLDEV

and target ID within the RAIDstorage system.

226Contact HPE technical support.Wrong return code.Invalidreturn code

EX_INVRCD

225Check the volume list to see if an operation wasdirected to the wrong S-VOL.

Currency check error for S-VOL.Cannot guarantee identical dataon S-VOL.

S-VOLcurrencyerror

EX_VOLCUR

224Please confirm the pair status of the local volumeusing the pairdisplay command.

The volume specified with theS-VOL-takeover command is notthe same as the P-VOL.

Localvolumecurrencyerror

EX_VOLCUE

256 Troubleshooting


ReturnedValue


Errorcode

223Please confirm the pair status of remote and localvolumes using the pairdisplay command.

The combination of the volumesspecified with Swap-takeover isunsuitable.

Local andremotevolume

EX_VOLCRE

currencyerror

--Contact HPE technical support.Wrong error code.Unknownerror code.

EX_UNWERR

217When the specified CTG ID is used by the otherprogram product, use the other CTG ID which is

The specified CTG ID cannot beused when the volume for

Not enoughCT groupsin RAID

EX_ENOCTG

not used by the other program product in thestorage system.

Continuous Access Synchronous,Continuous Access Journal, High



ReturnedValue


Errorcode

When the number of the consistency groupsexceeds the maximum number, execute one ofthe following actions:

• To create the Cnt Ac-S, Cnt Ac-J, HA or BCpair after reducing the consistency groups:1. Select consistency group which can bedeleted in the existing consistency groups.2. Find the configuration definition file in whichthe name of the consistency group to bedeleted is written at dev_group.3. Execute the pairsplit -S commandspecifying the dev_group name of theconsistency group to be deleted by theHORCM instance which matches theconfiguration definition file found at step 2 (splitthe pair).4. Delete the dev_group which matches theconsistency group to be deleted from theconfiguration definition file found in step 2(delete both P-VOL and S-VOL whichconfigures the split pair).5. Restart the HORCM instance which matchesthe configuration definition file found at step 2,reflecting the editing results of the configurationdefinition file.6. Add the device to the dev_group whichmatches the consistency group to be addedusing new or existing configuration definitionfile (add P-VOL and S-VOL which configuresthe pair to be added).7. Start or restart the HORCM instance whichmatches the configuration definition file usedat step 6.8. Execute the paircreate commandspecifying the dev_group name of theconsistency group in which the pair is addedby the HORCM instance which matches theconfiguration definition file used at step 6 asfollows.In case of Cnt Ac-S, Cnt Ac-J, or HA:paircreate -g <dev_group name>-f[g] <fence> [CTGID]

In case of BC:paircreate -g <dev_group name> -mgrp [CTGID]

Confirm the CTG ID of the existing consistencygroup by pairvolchk command.When the -fg option is specified and CTGIDis omitted in the paircreate command,unused CTG ID is set automatically.

Availability or Business Copy pairis created, because the specifiedCTG ID is used by the otherprogram product in the storagesystem. Otherwise, CTG ID cannotbe registered because the numberof the consistency groups exceedsthe maximum number.For details about the maximumnumber of the consistency groups,see “Continuous AccessAsynchronous, Continuous AccessSynchronous, Continuous AccessJournal, and High Availabilityvolumes” (page 190).

258 Troubleshooting


ReturnedValue


Errorcode

• To add the Cnt Ac-S, Cnt Ac-J, HA or BC pairto the existing consistency group that is usedby the same program product:1. Select an exigting consistency group towhich the pair can be added.2. Find the configuration definition file in whichthe name of the consistency group to whichthe pair is added is written at dev_group.3. Add the device to the dev_group in theconfiguration definition file found at step 2which matches the consistency group to whichthe pair is added (add P-VOL and S-VOL whichconfigures the pair to be added).4. Restart the HORCM instance which matchesthe configuration definition file found at step 2,reflecting the editing results of the configurationdefinition file.5. Execute the paircreate commandspecifying the dev_group name of theconsistency group to which the pair is addedby the HORCM instance which matches theconfiguration definition file found at step 2 asfollows.In case of Cnt Ac-S, Cnt Ac-J, or HA:paircreate -g <dev_group name>-f[g] <fence> [CTGID]

In case of BC:paircreate -g <dev_group name> -mgrp [CTGID]

Confirm the CTG ID of the existing consistencygroup by pairvolchk command.When the -fg option is specified and CTGIDis omitted in the paircreate command,unused CTG ID is set automatically.

216Please confirm the serial # of the volumes byusing the pairdisplay command to verify that

A Continuous AccessSynchronous, Continuous AccessJournal, High Availability, or

ExtendedCT groupacrossRAIDs

EX_EXTCTG

the consistency group is contained completelywithin one RAID storage system.Business Copy volume is defined

in the configuration definition file(HORCM_CONF) as a group thatextends across storage systems.

215Please confirm whether all consistency groupsare already used by mainframe volumes.

An available consistency group forOPEN Volume does not exist.

No CTgroups left

EX_ENXCTG

for OPENVol use.

214Please confirm the CTG ID using thepairvolchk command and confirm that group

The consistency group referenceswithin a group do not have anidentical CTG ID.

UnmatchedCTGIDwithin thegroup

EX_ENQCTG

references within the configuration definition file(HORCM_CONF) refer to the same consistencygroup.

213Please confirm whether pair-operation is permittedon the device by using the pairdisplay orraidscan -find verify command.

A device mentioned in theconfiguration definition file doesnot have a permission for apair-operation.

Permissiondenied withthe LDEV

EX_ENPERM



ReturnedValue


Errorcode

212Please confirm volume size or number of LUSEvolume using the 'raidscan -f' command, andmake sure the volume sizes are identical.

Size of a volume is unsuitablebetween the remote and localvolume.

Unmatchedvolume sizefor pairing

EX_ENQSIZ

211Please confirm if the type of storage system ispermitted for a RAID Manager by using theinqraid -CLI and raidqry -h commands.

A storage system (RAID)mentioned in the configuration filedoes not have a permission forRAID Manager.

Permissiondenied withthe RAID

EX_ERPERM

209Please confirm whether a target volume is settingto S-VOL disabling y using inqraid -fl orraidvchkscan -v gflag command.

A specified target volume forS-VOL is denied to becomeS-VOL by the setting of DataRetention.

S-VOLdenied dueto bedisabling

EX_ESVOLD

210Please confirm the storage system model nameand microcode version by using the raidqry-l command.

The storage system does notsupport a function for RAIDManager.

Microcodenotsupported

EX_ENOSUP

208Please confirm the retention time for a targetvolume that is set to Data Retention by usingraidvchkscan -v gflag command.

A target volume is denied to bechanging due to retention time viaLDEV guarding.

Modechangesdenied dueto retentiontime

EX_EPRORT

207Please make the SLPR so that the target port andthe command device belongs to the same SLPR.

A specified command device doesnot have a permission to accessother SLPR.

Permissiondenied withthe SLPR

EX_ESPERM

206Please release the pair of older generations pairedvolume, or re-synchronize the pair of split statuspaired volume.

Could not retain the pool forexecuting a command due to beexceeded the threshold rate.

Not enoughPool inRAID

EX_ENOPOL

205Specify the appropriate object. Check the statusof one of the following.

The specified object is notinstalled. There are port, LDEV,and Hostgroup in the object.

No suchObject inthe RAID

EX_ENOOBJ

• The specified port is not installed.

• The value of specified port is invalid.

• LU path is defined.

• A logical path between MCU and RCU remain.

• LDEV is not installed.

• The attribute of the port is not Target (TAR) orRCU Target (RCU).

• LUN security is invalid.

• The specified host group is not installed.

203Check the operation authentication.The specified command devicedoes not have an authority toexecute this command.

Permissiondenied withthe privilege

EX_EPPERM

204Check the operation authentication.The specified command devicedoes not have an authority toexecute this command.

UnmatchedCLPR withJNL andVolume

EX_ENQCLP

199Check if the operation by the command executesa proper procedures and has the consistency ornot.

An error is detected by the ContextChecking.

Contextcheck error

EX_CTXCHK

200Check if the specified resource is used by suchas Remote Web Console or not.

The resource that you specified tolock or unlock has already beenused by another user.

Accessdenied withLock/Unlock

EX_EACCES

260 Troubleshooting


ReturnedValue


Errorcode

202Check the user ID and password.User authentication failed at theauthentication command device.

Authenticationfailed withUser

EX_ENAUTH

253User -h option to check the correct option, andspecify it.

Invalid option or an argument ofthe option.

Invalidargument

EW_INVARG

131Use -h option to check the correct option and useit.

Invalid argument of an optionInvalidoptionargument

EW_INVOPA

131Use -h option to check the correct option and useit.

Invalid option.Invalidoption

EW_INVOPT

131Specify the number of characters of action, object,option, an argument of option, or the total number

The number of character foraction, object, option or argumentof option exceeded the maximum.

Argumenttoo long

EW_LNGARG

of characters are to be appropriate number ofcharacters.

131Check the total number of option or argument ofoption.

The total number of option or theargument of option exceeded themaximum.

Maximumargument

EW_MAXARG

131Check if the specified file exist or not, and specifythe correct file.

The specified file dies not exist.No such fileEW_ENFILE

131Use -h option and specify the correct action orobject.

The number of action or theargument of object is insufficient.

Requiredaction/objectlist

EW_REQCMD

131Use -h option and specify the correct option.The number of option or theargument of option is insufficient.

Requiredoption list

EW_REQOPT

230Check the issued command action and object.The command action or an objectis undefined.

Unknowncommand

EW_UNWCMD

252Use -h option and specify the correct option.Specifies an undefined option.raidcom:[EW_UNWOPT]

EW_UNWOPT

Unknownoption

131Contact HPE technical support.An invalid internal error hasdetected.

Systemerror

EW_SYSERR

245Add more virtual memory of a whole system, orterminate unnecessary programs or daemons thatare executed in parallel.

Memory to execute a commandcannot be allocated in HORCM.

Not enoughcore

EW_ENOMEM

198Issue the command again after the operation ofthe object is complete.

The object is in operation.Objects waschanged

EX_CHGOBJ

whilereferring

201Specify the resource group that is allocated to theuser group as the operation target or set the

You do not have the operationauthority to operate the relevantresource group.

Permissiondenied withthe

EX_EGPERM

operation authority to the user group in order tooperate the relevant resource group.Resource

Group


Generic error codes (horctakeover and pair commands)The following table lists the generic error codes returned by the following commands:

• horctakeover

• paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk,pairsyncwait, pairdisplay

In this table, "Unrecoverable" indicates errors that cannot be recovered by reexecuting thecommand, and "Recoverable" indicates errors that can be recovered by reexecuting the command.

Table 52 Generic error codes (horctakeover and pair commands)

ReturnValue

Error messageError codeCategory

254Required Arg listEX_REQARGSyntax for Argument(Unrecoverable) 253Invalid argumentEX_INVARG

249Invalid name of optionEX_INVNAM

252Unknown optionEX_UNWOPT

238Unknown function codeEX_UNWCOD

230Unknown commandEX_UNWCMD

244Result too largeEX_ERANGE

243File name too longEX_ENAMLG

226Invalid return codeEX_INVRCD

239No such groupEX_ENOGRPConfiguration(Unrecoverable) 247No such device or groupEX_ENOENT

246No such deviceEX_ENODEV

227No such LDEV within the RAIDEX_ENLDEV

219No such RAID unitEX_ENOUNT

220Invalid mu# with HORC or HOMRCFEX_INVMUN

218Unmatched Serial# vs RAID unitIDEX_ENQSER

216Extended CTgroup across RAIDsEX_EXTCTG

214Unmatched CTGID within the groupEX_ENQCTG

213Permission denied with the LDEVEX_ENPERM

211Permission denied with the RAIDEX_ERPERM

207Permission denied with the SLPREX_ESPERM

221An order to the control/command was rejectedEX_CMDRJECommand I/O to RAID(Recoverable) 237Control command I/O error, or rejectedEX_CMDIOE

248A specified option is invalidEX_OPTINV

241Invalid RAID command modeEX_INVMOD

240Invalid RAID commandEX_INVCMD

251Cannot be attached to HORC managerEX_ATTHORCommunication for HORCM(Recoverable) 250Cannot be attached to a Debug layerEX_ATTDBG

262 Troubleshooting

Table 52 Generic error codes (horctakeover and pair commands) (continued)

ReturnValue

Error messageError codeCategory

255Cannot be communicate with HORC managerEX_COMERR

242No remote host alive for remote commands, or RemoteRAID Manager might be blocked (sleeping) on anexisting I/O.

EX_ENORMTRecoverable

245Not enough coreEX_ENOMEMResource(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" indicates errors that cannot be recovered by reexecuting thecommand, and "Recoverable" indicates errors that can be recovered by reexecuting the command.

Table 53 Generic error codes (raidscan, raidqry, raidar, horcctl)

ValueError messageError codeCategory

254Required Arg listEX_REQARGSyntax for Argument(Unrecoverable) 253Invalid argumentEX_INVARG

249Invalid name of optionEX_INVNAM

252Unknown optionEX_UNWOPT

238Unknown function codeEX_UNWCOD

230Unknown commandEX_UNWCMD

244Result too largeEX_ERANGE

243File name too longEX_ENAMLG

226Invalid return codeEX_INVRCD

227No such LDEV within the RAIDEX_ENLDEVConfiguration(Unrecoverable) 219No such RAID unitEX_ENOUNT

220Invalid mu# with HORC or HOMRCFEX_INVMUN

211Permission denied with the RAIDEX_ERPERM

210Microcode not supportedEX_ENOSUP

207Permission denied with the SLPREX_ESPERM

237Control command I/O errorEX_CMDIOECommand I/O to RAID(Recoverable) 248A specified option is invalidEX_OPTINV

241Invalid RAID command modeEX_INVMOD

240Invalid RAID commandEX_INVCMD


Table 53 Generic error codes (raidscan, raidqry, raidar, horcctl) (continued)


251Can't be attached to HORC managerEX_ATTHORCommunication for HORCM(Recoverable) 250Can't be attached to a Debug layerEX_ATTDBG

255Can't be communicated with HORC managerEX_COMERR

245Not enough coreEX_ENOMEMResource(Unrecoverable)

Specific error codesThe following table lists the specific error codes returned by the following commands:

• horctakeover

• paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk,pairsyncwait, raidvchkset

In this table, "Unrecoverable" indicates errors that cannot be recovered by reexecuting thecommand, and "Recoverable" indicates errors that can be recovered by reexecuting the command.See theRAIDManager Reference Guide for more information on error codes for each command.

Table 54 Specific error codes


236Unmatched volume status within the groupEX_ENQVOLVolume Status(Unrecoverable) 229Inconsistent status in groupEX_INCSTG

222Invalid volume statusEX_INVVOL

235Pair Volume combination errorEX_EVOLCE

228Invalid pair statusEX_INVSTP

225S-VOL currency errorEX_VOLCUR

224Local Volume currency errorEX_VOLCUE

223Local and Remote Volume currency errorEX_VOLCRE

234Pair suspended at WAIT stateEX_EWSUSE

212Unmatched volume size for pairingEX_ENQSIZ

209S-VOL denied due to be disablingEX_ESVOLD

208Mode changes denied due to retention timeEX_EPRORT

233Timeout waiting for specified statusEX_EWSTOTTimer(Recoverable) 232Timeout waiting for specified status on the local hostEX_EWSLTO

217Not enough CT groups in the RAIDEX_ENOCTGResource(Unrecoverable) 215No CT groups left for OPEN Vol use.EX_ENXCTG

206Not enough Pool in RAIDEX_ENOPOL

264 Troubleshooting

SSB codesAn SSB code is error information that is output when an error occurs by executing a RAID Managercommand. The SSB code is output to the RAID Manager execution log file or to the console.Identify the SSB code from an error code as follows:

• SSB code that is output to the RAID Manager execution log file.The following shows an example of a SSB code that is output to the RAID Manager executionlog file.Example:11:06:03-37897-10413- SSB = 0xb9a0,2089The alphanumeric characters after the equal sign shows an error code. The last four digitsof alphanumeric characters on the left side of the comma (,) is SSB1 (for example, b9ao),and the alphanumeric characters on the right side is SSB2 (for example, 2089).

• SSB code that is output on the console.The following shows an example of an SSB code that is output to the console.

Figure 81 An example of SSB code that is output to the console

The alphanumeric characters after the "SSB=" show an error code. The last four digits ofalphanumeric characters on the left side of comma (,) is SSB1 (for example, B9E1), and thelast four digits of alphanumeric characters on the right side is SSB2 (for example, B901).

The following describes the SSB codes returned by the replication commands and the configurationsetting command (raidcom).


SSB codes returned by the replication commandsWhen a replication command returns an SSB code, refer to the troubleshooting information inthe user document for the product as follows:

Product returning the SSB codeCommand

Continuous Access Synchronous• paircreate

• pairresync

• pairsplit

• horctakeover

• horctakeoff

Continuous Access Journal• paircreate

• pairresync

• pairsplit

• horctakeover

• horctakeoff

High Availability• paircreate

• pairresync

• pairsplit

• horctakeover

• horctakeoff

Business Copy• paircreate

• pairresync

• pairsplit

Auto LUN• paircreate

• pairsplit

Fast Snap• paircreate

• pairresync

• pairsplit

Database Validator*• raidvchkset -vt

• raidvchkset -vs

Data Retention• raidvchkset -vg

Thin Provisioning• raidvchkset -vext

* Database Validator is only supported on XP P9500 and prior XP generations.

The following tables provide information about the SSB codes returned by the replicationcommands. If you see an error not described in the tables, contact HPE technical support.

266 Troubleshooting

Table 55 SSB codes returned by thepaircreate command

paircreate

DescriptionError codeExecuting/Async

Error message

SSB2SSB1

The command was rejected because the specified port is forNAS Platform (System LU).

B901B980ExecutingCMDRJE

The command was rejected because the selected resourcebelongs to NAS_Platform_System_RSG.


Table 56 SSB codes returned by the pairsplit command

pairsplit


Error message

SSB2SSB1



Table 57 SSB codes returned by the pairsplit -S command

pairsplit -S


Error message

SSB2SSB1



SSB codes returned by the configuration setting command (raidcom)Executing the configuration setting command (raidcom command) can return an SSB code. Anerror can occur whether the command is executed synchronously or asynchronously. For anasynchronous error, the error information is displayed on the console by executing raidcom getcommand_status command. When the error message shows "CMDRJE" or "Get CommandStatus", check the contents of SSB1 and SSB2. You can verify a content of an error by theraidcom get error_message command. When you specify the SSB code with the raidcom geterror_message command, make sure not to specify a wrong SSB code.The following tables provide information about each SSB code returned by the configurationsetting command (raidcom command). If you see an error not described in the tables, contactHPE technical support.

Table 58 SSB codes returned by the configuration setting command (common)

common


Error message

SSB2SSB1

Unavailable to operate because another application is inprogress on Remote Web Console or SVP.

80002E10Executing/AsyncCMDRJEGet Command Status

The resource group to which the operation object belongs islocked by the other user.

22052E11ExecutingCMDRJE

The system is locked by another user.22072E11ExecutingCMDRJE


Table 58 SSB codes returned by the configuration setting command (common) (continued)

common


Error message

SSB2SSB1

The command cannot be executed because there is blockedpart in the system.


The command cannot be executed because the userauthentication is not performed.


The specified command cannot be executed due to thefollowing reasons:

93002EF3ExecutingCMDRJE

• The command cannot be accepted because it is notsupported.

• The command is not supported in the current RAID Managerversion.

The specified operation is not supported in the currentmicrocode version.

9F022EF3ExecutingCMDRJE

The virtual storage machine with the specified serial numberis not found.



FF002EFFExecutingCMDRJE


B90FB90FExecutingCMDRJE


FF5FB954ExecutingCMDRJE


B9ECB9ECExecutingCMDRJE


B9EEB9EEExecutingCMDRJE


B90AB9FDExecutingCMDRJE


B90CB9FDExecutingCMDRJE

Table 59 SSB codes returned by raidcom add external_grp

raidcom add external_grp


Error message

SSB2SSB1

Invalid emulation type.000D2E00ExecutingCMDRJE

There are not enough cache management devices.00132E00AsyncGet Command Status

The external volume group is not in a effective range.41002E00ExecutingCMDRJE

The command cannot be executed by receiving the multipleoperations for the same external volume group.

41042E00AsyncGet Command Status

The external volume group exists already.41082E00AsyncGet Command Status

The specified CLPR does not exist.410B2E00AsyncGet Command Status

268 Troubleshooting

Table 59 SSB codes returned by raidcom add external_grp (continued)



Error message

SSB2SSB1

The volume cannot be mapped for online data migrationbecause the emulation type is not OPEN-V.

410D2E00ExecutingCMDRJE

The specified external volume group attribute is invalid.410E2E00ExecutingCMDRJE

This command does not support the specified emulation type.41112E00AsyncGet Command Status

The path group is not in a effective range.45002E00ExecutingCMDRJE

The value of the specified port is not valid.84002E00ExecutingCMDRJE

The specified iSCSI name is invalid.9B012E00ExecutingCMDRJE

The iSCSI target cannot be specified because the emulationtype is for mainframe.


LUN of the specified external storage port does not exist.42002E10AsyncGet Command Status

The external volume cannot be created because the specifiedexternal LU is a command device.


The WWN on the side of specified external storage does notconnected to a External port.


This message may be output if the migration source storagesystem is XP24000/XP20000 Disk Array and the host modeoption 2 is not set to the port that connects to the migrationtarget storage system.

The specified external LU cannot create a external volumebecause the transition of data is required.


The specified path group cannot be operated because a pathbetween other devices exists.


The operation cannot be performed because the unsupportedmicrocode version exists in the system.

800F2E11AsyncGet Command Status

The storage system is in internal process, or the configurationchanging processes are conflicting.


The command cannot be accepted. After a while, execute thesame command.


Package for Mainframe is required when you specify theemulation type of mainframe.


The specified MP Blade is not installed.83002E20AsyncGet Command Status

The program product of External Storage is not installed.90082E21Executing/AsyncCMDRJEGet Command Status

The program product of Online Migration is not installed.90132E21Executing/AsyncCMDRJEGet Command Status

The external volume group exists already.41002E22AsyncGet Command Status

The external volume group exists already.41002E22ExecutingCMDRJE

Exceeded the number of mapping that can be set per 1 port.41022E23AsyncGet Command Status

The operation cannot be done because the number of path inthe path group exceeds 8.



Table 59 SSB codes returned by raidcom add external_grp (continued)



Error message

SSB2SSB1

The external volume cannot be added because the number ofvirtual volumes that can be created in the system exceededthe maximum number.


The external volume having the Data Direct Mapping attributecannot be created because the size of the specified externalLU is less than 8GB.

411B2E30AsyncGet Command Status

The specified external LU has mapped already.42012E30AsyncGet Command Status

The port attribute is not External.84002E30ExecutingCMDRJE

The command cannot be executed with the specified portattribute.

840E2E30ExecutingCMDRJE

The specified external storage LU is the device of notsupported.


The specified external storage system is not supported.40012E31AsyncGet Command Status

The specified external volume does not support OnlineMigration.


The usage capacity exceeds the license capacity of theprogram product.



00EE2EDAExecutingCMDRJE

An internal error occurred.41FA2EDAAsyncGet Command Status

The specified parameter is invalid. Check the RAID ManagerReference Guide.




The command was rejected because the selected port is forNAS Platform (User LU).


Table 60 SSB codes returned by raidcom check_ext_storage external_grp

raidcom check_ext_storage external_grp


Error message

SSB2SSB1

The external volume group is not in the effective range.41002E00ExecutingCMDRJE

The specified external volume has already disconnected thepath, or is in the process of checking path.


The target LDEV is blocked.001B2E11ExecutingCMDRJE

The path for the specified external path is in the state ofdisconnected.


All the paths for the specified external path are blocked.43022E11ExecutingCMDRJE

There is no external volume group.41002E20ExecutingCMDRJE

There is no external path.43002E20ExecutingCMDRJE

270 Troubleshooting

Table 60 SSB codes returned by raidcom check_ext_storage external_grp (continued)

raidcom check_ext_storage external_grp


Error message

SSB2SSB1

Online from the mainframe host.001E2E30ExecutingCMDRJE

An internal error occurred by the operation of external path.09052EDAAsyncGet Command StatusCall HPE technical support.

An internal error occurred by the operation of external volume.09052EDAExecutingCMDRJECall HPE technical support.

Table 61 SSB codes returned by raidcom delete external_grp

raidcom delete external_grp


Error message

SSB2SSB1

The external volume group # is in the effective range.41002E00ExecutingCMDRJE

LDEVs in the external volume group are devices that have aCC/XRC attributes.


The specified external volume group is used in anotheroperation.


Destage is not executed.41032E11AsyncGet Command Status

The external volume is used as Compatible FlashCopy.41042E11AsyncGet Command Status

The specified external volume cannot be deleted because auditlogs for the system disk are being used.


The operation cannot be done because the internal processingis in progress.




The operation cannot be done because there is blocked partin the system.





LU path is defined to LDEV in the external volume group.00072E30ExecutingCMDRJE

The external volume is used as a system disk.00572E30AsyncGet Command Status

The external volume is used as LUSE.41012E30AsyncGet Command Status

The external volume is used as a Continuous AccessSynchronous pair volume.


The external volume is used as a Continuous AccessSynchronous pair volume.


The specified volume is used as a Business Copy pair volume,a Fast Snap pair volume, or a FICON® Data Migration volume.





Table 61 SSB codes returned by raidcom delete external_grp (continued)

raidcom delete external_grp


Error message

SSB2SSB1

There is the volume that has path definition.41062E30AsyncGet Command Status

The external volume is used as a Business Copy reservedVOL.


The external volume is used as an Auto LUN V2 reserved VOL.41082E30AsyncGet Command Status

There is a mainframe path group setting in the external volume.41092E30AsyncGet Command Status

There is a Data Retention setting in the external volume.410A2E30AsyncGet Command Status

There is a mainframe LDEV Guard setting in the externalvolume.


There is a Volume Security for Mainframe setting in the externalvolume.

410C2E30AsyncGet Command Status

The external volume is used as a Continuous Access Journalpair volume.

410D2E30AsyncGet Command Status

The external volume is used as a Continuous Access Journaljournal volume.

410E2E30AsyncGet Command Status

The external volume is used as a pool-VOL.410F2E30AsyncGet Command Status

The external volume is used as a pool-VOL.41102E30AsyncGet Command Status

The external volume is used as an Auto LUN V2 VOL.41112E30AsyncGet Command Status

The external volume is used as an Auto LUN V2 VOL.41122E30AsyncGet Command Status

The target external group cannot be deleted because a quorumdisk exists in it.




An internal error occurred.FFFB2EE8AsyncGet Command StatusCall HPE technical support.

An internal error occurred.41FF2EFFAsyncGet Command StatusCall HPE technical support.

Table 62 SSB codes returned by raidcom check_ext_storage path

raidcom check_ext_storage path


Error message

SSB2SSB1

The path group is not in the enabled range.45002E00ExecutingCMDRJE

The value of the port is not enabled.84002E00ExecutingCMDRJE



The target LDEV is blocked.001B2E11AsyncGet Command Status



272 Troubleshooting

Table 62 SSB codes returned by raidcom check_ext_storage path (continued)

raidcom check_ext_storage path


Error message

SSB2SSB1

All the paths for the specified external path are blocked.43022E11AsyncGet Command Status



There is no specified external volume.41002E20AsyncGet Command Status

There is no specified path.43002E20Async/Get Command StatusExecutingCMDRJE

WWN is not registered.44002E20ExecutingCMDRJE

The path group is not registered.45002E20ExecutingCMDRJE

The path group does not exist.45002E20ExecutingCMDRJE

Online from the mainframe host.001E2E30AsyncGet Command Status

The port attribute is not External (ELUN).84002E30ExecutingCMDRJE





An internal error occurred by the operation of external path.09052EDAAsyncGet Command StatusCall HPE technical support.

The command was rejected because the specified port is forNAS platform (System LU).


The command was rejected because the specified port is forNAS platform (User LU).


Table 63 SSB codes returned by raidcom disconnect external_grp

raidcom disconnect external_grp


Error message

SSB2SSB1


The specified LDEV is used for a Business Copy pair.00002E10ExecutingCMDRJE

It is used as a Continuous Access Synchronous or ContinuousAccess Journal pair.


A Business Copy pair, a Fast Snap/Snapshot pair or aCompatible FlashCopy relationship or in status of splitting orpending exists.


The specified LDEV is used for a Fast Snap pair or aSnapshot pair.


It is used as a system disk.00082E10ExecutingCMDRJE

It is used as a concurrent copy or XRC.00122E10ExecutingCMDRJE


Table 63 SSB codes returned by raidcom disconnect external_grp (continued)



Error message

SSB2SSB1

The specified LDEV is used as the primary volume of a HighAvailability (HA) pair.


The specified LDEV is used as the secondary volume of anHA pair.


The specified external volume group is in the state ofdisconnected.


The specified external device is in the state of disconnected.41022E10ExecutingCMDRJE



It is in the state of shredding.00072E11ExecutingCMDRJE

The target LDEV is blocked.001B2E11ExecutingCMDRJE



The THP V-VOL with the Data Direct Mapping attribute whichis allocated to the specified external volume is not blocked.


All the paths for the specified external path are blocked.43022E11ExecutingCMDRJE

The specified external volume belongs to a Fast Snap orSnapshot where the pair in the PSUS status exists.


The operation cannot be done because the internal processingis in progress. Wait for a while, then retry the operation.


There is no specified external volume.41002E20ExecutingCMDRJE

There is no specified path.43002E20ExecutingCMDRJE

It is included the Thin Provisioning volume that is associatedwith a pool.

000A2E30ExecutingCMDRJE

The specified LDEV is used as a quorum disk.000C2E30ExecutingCMDRJE

It is used as a pool volume.000E2E30ExecutingCMDRJE

It is used as a journal volume.000F2E30ExecutingCMDRJE

It is used as a reserved volume of Auto LUN V2.00142E30ExecutingCMDRJE

Volume Security for Mainframe is set.001A2E30ExecutingCMDRJE

It is used as a remote command device.001C2E30ExecutingCMDRJE

Online from the mainframe host.001E2E30ExecutingCMDRJE

This is a volume that the Data Retention is set.004E2E30ExecutingCMDRJE

The Thin Provisioning volume not in the blocked state isincluded in the Thin Provisioning that is associated with thepool to which the pool volume is belongs.


An internal error occurred by the operation of disconnectingthe external volume.

00002EDAExecutingCMDRJE

274 Troubleshooting

Table 63 SSB codes returned by raidcom disconnect external_grp (continued)



Error message

SSB2SSB1

Call HPE technical support.

An internal error occurred by the operation of external volume.09052EDAExecutingCMDRJECall HPE technical support.

Table 64 SSB codes returned by raidcom modify external_grp



Error message

SSB2SSB1


The specified value of the load balance mode is invalid.410F2E00ExecutingCMDRJE

The specified value of the ALUA mode is invalid.41102E00ExecutingCMDRJE

MP Blade ID is not in the effective range.83012E00ExecutingCMDRJE

The operation cannot be performed because the volume usedfor data migration is reserved from the host.


The specified MP Blade is blocked.83002E10ExecutingCMDRJE

The attribute cannot be changed because Auto LUN is beingexecuted.


The load balance mode cannot be changed because thealternative path mode is set to Single.


The load balance mode cannot be changed becausemicrocodes of multiple versions are in the storage system.

800F2E11ExecutingCMDRJE


The specified MP Blade is not installed.83002E20ExecutingCMDRJE

The attribute cannot be changed because the external volumeis used as a Business Copy pair volume.


The external volume is used as a Continuous Access Journalpair volume.


The external volume is used as a Continuous AccessSynchronous volume.


Cache mode cannot be changed because there is an LDEVthat Cache Residency bind mode is set.

000C2E31ExecutingCMDRJE

Cache mode cannot be changed because the specified externalvolume includes a pool volume or an LDEV that is used byLUSE.


The cache mode cannot be changed because the specifiedexternal volume is one of the following.


• A pool volume in the pool that consists of both externalvolumes and internal volumes.

• A pool volume in the pool whose Smart Pool option isenabled.


Table 64 SSB codes returned by raidcom modify external_grp (continued)



Error message

SSB2SSB1

The attribute of the external volume cannot be changed fromthe current cache mode to the specified cache mode.


The attribute cannot be changed because the external volumegroup is not mapped for online data migration.


The specified command cannot be accepted because thecommand is not supported.

00F12EDAExecutingCMDRJE

An internal error occurred on the changing of an externalvolume option.

09052EDAExecutingCMDRJE


The specified parameter is incorrect. Check theRAIDManagerReference Guide.


Table 65 SSB codes returned by raidcom modify port loop_id

raidcom modify port -loop_id


Error message

SSB2SSB1

The specified AL-PA is invalid.044CB955ExecutingCMDRJE

The specified topology is invalid.054EB955ExecutingCMDRJE

The other than "fabric on" cannot be specified when specifyinga topology of the package for Fibre Channel over Ethernet.

05A6B955ExecutingCMDRJE

The other than "P-to-P (point to point)" cannot be specifiedwhen specifying a topology of the package for Fibre Channelover Ethernet.


The command device being used at the local RAID Managerexists under the port.

1039B955ExecutingCMDRJE

The program product is not installed.104FB955ExecutingCMDRJE

Invalid host speed is set for the 4Gbps fibre adapter. Theavailable host speeds are AUTO, 1G, 2G, and 4G only.

113DB955ExecutingCMDRJE


113FB955ExecutingCMDRJE

The other than "10G" cannot be specified when specifying ahost speed of the package for Fibre Channel over Ethernet.






276 Troubleshooting

Table 66 SSB codes returned by raidcom modify port topology

raidcom modify port -topology


Error message

SSB2SSB1
















The combination of the specified topology FC-AL and the hostspeed set for the fibre channel adapter is not supported. See

12AFB955ExecutingCMDRJE

the Provisioning Guide of your system for supportedcombinations of data transfer speed and type of connection.





Table 67 SSB codes returned by raidcom modify port -security_switch

raidcom modify port -security_switch


Error message

SSB2SSB1













Table 67 SSB codes returned by raidcom modify port -security_switch (continued)

raidcom modify port -security_switch


Error message

SSB2SSB1









Table 68 SSB codes returned by raidcom add ldev

raidcom add ldev


Error message

SSB2SSB1

The LDEV number is out of settable range00002E00ExecutingCMDRJE

The specified capacity is not in the effective range.00022E00Executing/AsyncCMDRJEGet Command Status

SSID is not in the effective range.00032E00ExecutingCMDRJE

The value of specified emulation type is invalid.000D2E00ExecutingCMDRJE

The specified emulation type is not supported in this command.000E2E00Executing/Async

CMDRJEGet Command Status

The operation cannot be performed because the specifiedLDEV number is already used.


The operation cannot be performed because there are notenough cache management devices.


Cannot create because the specified capacity is invalid.00142E00AsyncGet Command Status

The capacity in the case of specifying a emulation type of themainframe series must be dividable by the cylinder.


The capacity when 3390-V emulation type is specified mustbe divisible by page unit.


When you specify emulation type for open system, you cannotspecify the size by the cylinder.


The following external volume cannot be created because thecapacity which is specified with LBA is not same as the sizeof the external volume group.


• An external volume for the online data migration.

• An external volume having the Data Direct Mappingattribute.

The capacity must be specified because LDEVs are in theparity group (or the external volume group).


The capacity must be specified.00272E00ExecutingCMDRJE

278 Troubleshooting

Table 68 SSB codes returned by raidcom add ldev (continued)

raidcom add ldev


Error message

SSB2SSB1

The emulation type of the mainframe cannot be specifiedbecause the virtual volume is set for the specified LDEV.


The specified value of the Full Allocation is invalid.002F2E00ExecutingCMDRJE

Full Allocation cannot be specified to the specified LDEVbecause the emulation type is not supported.


The parity group number or the external group number is notin the effective range.


Failed to restore the LDEV that is created to external volumegroup.


The specified pool ID is not in the effective range.60002E00ExecutingCMDRJE

The specified CLPR ID is not in the effective range.70002E00ExecutingCMDRJE


The specified protection type is not supported.02012E02ExecutingCMDRJE

The specified operation cannot be done because it is anexternal volume.


The operation cannot be performed because the specifiedcapacity is less than 8 GB.


Full Allocation cannot be performed because the pool uses theLDEV belonging to a parity group with capacity expansionenabled.


The specified LDEV is used as a Compatible FlashCopyrelationship.


The operation cannot be performed because the total capacityof virtual volumes for Smart Tiers or Real Time Smart Tier inthe system exceeds the maximum.


The operation cannot be performed because the specifiedLDEV is a journal volume.


The operation cannot be performed because the followinginformation of the migration source and the migration targetdoes not match.

005A2E10AsyncGet Command Status

• serial number

• product ID

• emulation type

• SSID

• LUSE

• CVS configuration

• LDEV number

The specified pool volume is already linked with the virtualvolume having the Data Direct Mapping attribute.




raidcom add ldev


Error message

SSB2SSB1

The volumes cannot be added because the encryption valueof the key number that is set to encryption ECC is invalid.


The volumes cannot be added because the check sum of theencryption key does not match.


The specified LDEV is not in the status where the capacitysaving setting can be enabled.


The operation cannot be performed because the specified poolstatus is incorrect.


The free space in the specified pool is insufficient.601B2E10AsyncGet Command Status

Full Allocation cannot be performed because the pool volumeis being deleted.


The deduplication function cannot be used in the specifiedpool.


The deduplication system data volume defined for the specifiedpool is not in the normal status.


The operation cannot be performed because the deduplicationsystem data volume of the pool linked with the specified LDEVis blocked.


An LDEV that is in the state of shredding is included in theparity group of the target LDEV.


An LDEV that is in the state of formatting is included in theparity group of the target LDEV.


An LDEV that is in the state of executing quick format isincluded in the parity group of the target LDEV.


The specified LDEV is blocked.001B2E11AsyncGet Command Status

The specified LDEV is used in another operation.00532E11ExecutingCMDRJE

The operation failed because capacity expansion of the paritygroup to which the specified LDEV belongs is enabled.


The parity group of the target LDEV is in the state of correctioncopy.


The parity group or the external volume group that the specifiedLDEV is belongs to is used in another operation.


The operation cannot be performed because the specified poolvolume is blocked.


The operation cannot be performed because the pool linkedwith the specified LDEV is in the unusable status.






Cache segment size is incorrect.81052E11AsyncGet Command Status

280 Troubleshooting


raidcom add ldev


Error message

SSB2SSB1





The specified LDEV is not defined.00002E20ExecutingCMDRJE

The specified CLPR does not exist.00072E20Executing/AsyncCMDRJEGet Command Status

There is no parity group.01002E20ExecutingCMDRJE

Pool ID is invalid.60002E20Executing/CMDRJEAsyncGet Command Status

The specified MP Blade is not installed.83002E20AsyncGet Command Status

There is not enough free shared memory space.60032E21AsyncGet Command Status

The operation cannot be performed because the capacity ofshared memory is insufficient.


The shared memory is not installed.810A2E21AsyncGet Command Status

Package for Mainframe is required when you specify theemulation type of mainframe.


The program product is not installed.90002E21AsyncGet Command Status

The program product is not installed.90012E21ExecutingCMDRJE


The program product is not installed.90042E21Executing/AsyncCMDRJE/GetCommand Status

Compatible FlashCopy SE program product is not installed.900E2E21ExecutingCMDRJE

LDEV is already defined.00012E22ExecutingCMDRJE

You cannot create the volume because the size of the specifiedexternal volume group exceeds the maximum capacity of theexternal volume for online data migration.


The number exceeds the maximum number of LDEV that canbe created in the current system configuration.

00012E23Executing/Async


The specified LDEV is used in the FICON® Data Migration.00062E30AsyncGet Command Status

The specified SSID is already used in another CU.00202E30ExecutingCMDRJE

The SSID is allocated to the CU already.00212E30ExecutingCMDRJE

The specified volume is used as an alias device in ParallelAccess Volumes.


An LDEV of another emulation type is allocated in the rangewhere the number is divided into each 32LDEVs.


The emulation type that cannot be mixed with is specified.004C2E30ExecutingCMDRJE



raidcom add ldev


Error message

SSB2SSB1

The number of ldevs exceeds the maximum number of ldevsthat can be created in the parity group or the external volumegroup.


The volume which is specified as a pool volume must have aData Direct Mapping attribute.


The specified LDEV is a volume for which the Data DirectMapping attribute is enabled.


The page reservation cannot be set for the specified LDEVwith the specified operation.


The operation cannot be performed because the pagereservation is set for the specified LDEV.


There is not enough amount of free space that is specified inthe parity group or the external volume group.


The location is out of the range that can be specified.01052E30ExecutingCMDRJE

Volume whose emulation type is 3390-V cannot be created inRAID1 parity group.


The virtual volume cannot be added because the number ofvirtual volumes that can be created in the system exceededthe maximum number.


The specified pool is the pool for Fast Snap or Snapshot.60032E30Executing/AsyncCMDRJEGet Command Status

The operation cannot be performed because the specified poolis used for Data Direct Mapping.


The operation cannot be performed because the specified poolis for the Smart Tiers.


The operation cannot be performed with the specified pooltype.


TSE-VOL cannot be created because of the followingconditions.


• The specified pool is other than THP MF pool.

• The specified emulation type is other than 3390-A.

TSE-VOL cannot be created in combination with the specifiedpool ID and the CU number of LDEV.


You must specify the even CU number for the pool of evenpool ID, and the odd CU number for the pool of odd pool ID.

A TSE-VOL cannot be created in the specified pool for SmartTiers or Real Time Smart Tier.



80002E3FExecuting/AsyncCMDRJEGet Command Status

The specified parameter is invalid.9E012EBEExecuting/AsyncCMDRJEGet Command Status

282 Troubleshooting


raidcom add ldev


Error message

SSB2SSB1


00EE2EE8ExecutingCMDRJE






The value of the capacity is invalid.--ExecutingERANGE Result toolarge

Table 69 SSB codes returned by raidcom delete journal

raidcom delete journal


Error message

SSB2SSB1

The number of specified LDEV is invalid.00002E00ExecutingCMDRJE

The specified volume capacity is too small.00232E00AsyncGet Command Status

The specified journal ID is exceeds the range.50002E00ExecutingCMDRJE

The specified volume is not installed or cannot be used.00112E10AsyncGet Command Status

The specified volume is used in maintenance operation.00532E10AsyncGet Command Status

The specified operation failed because the journal or mirror isnot in the operable status.


The journal volume cannot be deleted with the specified journalstatus.


The operation cannot be done because it is in the state ofstart-up.






The specified LDEV is not in the journal.50022E13ExecutingCMDRJE

The specified journal ID is not registered.50002E20ExecutingCMDRJE

The operation failed because the specified journal is notregistered.


The journal volume cannot be added, or the journal cannot beadded to the extended consistency group due to insufficientcapacity of the shared memory.


The shared memory for Continuous Access Journal is notinstalled.


The number of specified LDEVs is invalid.00082E23ExecutingCMDRJE


Table 69 SSB codes returned by raidcom delete journal (continued)

raidcom delete journal


Error message

SSB2SSB1

The specified volume cannot be used as a journal volumebecause it is an external volume that can execute the I/Osuppression mode.


The specified journal cannot be deleted because there are datavolumes.



08E62EE4ExecutingCMDRJE

An internal error occurred.50EE2EE4AsyncGet Command StatusCall HPE technical support.



Table 70 SSB codes returned by raidcom add journal

raidcom add journal


Error message

SSB2SSB1

The value of LDEV number is invalid.00002E00ExecutingCMDRJE

A new journal volume cannot be registered because the numberof journal volume exceeds the maximum that can be registered.


The specified volume capacity is too small.00232E00AsyncGet Command Status

The specified MP Blade ID is invalid.83012E00ExecutingCMDRJE

The specified volume is already used by another programproduct.


The specified volume is not installed or cannot be used.00112E10Executing/AsyncCMDRJEGet Command Status

The specified volume is connected from the mainframe host.001A2E10AsyncGet Command Status

There is a PIN slot in the journal volume.001B2E10Executing/AsyncCMDRJEGet Command Status

The specified volume cannot be registered as a journal volumebecause it is in shredding. Wait until the shredding operationis completed, then retry the operation.

001C2E10Executing/AsyncCMDRJEGet Command Status

The specified volume is used in maintenance operation.00532E10AsyncGet Command Status

The specified volume cannot be used as the journal volumebecause the virtual LDEV ID is deleted.


The specified volume cannot be used as the journal volumebecause it is the virtual volume.




284 Troubleshooting

Table 70 SSB codes returned by raidcom add journal (continued)

raidcom add journal


Error message

SSB2SSB1





Abnormal cache status.810A2E11Executing/AsyncCMDRJEGet Command Status





The operation failed because the specified journal is notinstalled.




The shared memory for Continuous Access Journal is notinstalled.


A journal volume cannot be registered, or a journal cannot beadded to the extended consistency group because the program


product of Continuous Access Journal or Continuous AccessJournal MF is not installed.

A new journal volume cannot be registered, or the number ofselected volumes is too many.



The operation failed because the multiple LDKC numberscannot be mixed in the journal.


The operation failed because the number of journals in thejournal or the extended consistency group exceeds themaximum.


The specified volume cannot be used as a journal volumebecause it is set by Cache Residency or Cache Residency MF.


The specified volume cannot be used because it is used inFICON(R) Data Migration.


A path is defined in the specified volume.00072E30Executing/AsyncCMDRJEGet Command Status

The operation failed because the specified volume is a quorumdisk.

000C2E30Executing/AsyncCMDRJEGet Command Status

The specified volume cannot be used as a journal volumebecause it is a system disk.

000D2E30Executing/AsyncCMDRJEGet Command Status



raidcom add journal


Error message

SSB2SSB1

The operation failed because the specified volume is a poolvolume of Thin Provisioning.


The specified volume is already used as a journal volume ora data volume.

000F2E30Async/Executing

Get Command StatusCMDRJE

The specified volume is used as a command device.00102E30Executing/AsyncCMDRJEGet Command Status

The specified volume cannot be used as a journal volumebecause it is a LUSE volume.


The specified volume cannot be used as a journal volumebecause it is set by Data Retention or Mainframe ArrayManagement.


Using the specified volume is prohibited by Volume Securityfor Mainframe.

001A2E30Executing/AsyncCMDRJEGet Command Status

The internal volumes and external volumes exist in the specifiedjournal.


The emulation type of the specified volume is not supported.Or, the combination of an emulation type of the journal volumeis incorrect.


The volume cannot be registered as a journal volume becausethe CLPR ID of the specified volume differs from the CLPR IDof the registered journal volume.


The specified LDEV is a remote command device.005F2E30ExecutingCMDRJE



The specified volume is a reserved volume of a mainframehost.


The specified volume is used by XRC.00652E30Executing/AsyncCMDRJEGet Command Status

The specified volume is a volume of Just in Time (On-demand)function.


The specified volume cannot be used as a journal volumebecause it is used by Parallel Access Volumes.


The resource group ID of the specified volume cannot beregistered because the resource group ID is different from the


resource group ID of the other journal volume in the specifiedjournal group.

The specified LDEV cannot be operated because it is anexternal volume mapped for online data migration.


286 Troubleshooting


raidcom add journal


Error message

SSB2SSB1

The specified LDEV cannot be used as a journal volumebecause the size of the LDEV is less than the minimum capacityof journal volume.


The operation cannot be performed because the specifiedvolume is not the Thin Provisioning V-VOL.


The operation cannot be performed because the specifiedLDEV is a volume for which capacity saving setting is enabledor a deduplication system data volume.



08E62EE4ExecutingCMDRJE

An internal error occurred.50EE2EE4Executing/AsyncCMDRJECall HPE technical support.Get Command Status

An internal error occurred.FEEC2EE4Executing/AsyncCMDRJECall HPE technical support.Get Command Status





Table 71 SSB codes returned by raidcom modify journal

raidcom modify journal


Error message

SSB2SSB1

The specified volume capacity is too small.00232E00ExecutingCMDRJE

The specified path block watch time is not in the range.500B2E00ExecutingCMDRJE

The specified MP Blade ID is invalid.83012E00ExecutingCMDRJE

The specified volume is not installed or cannot be used.00112E10ExecutingCMDRJE



The specified operation failed because the mirror of journal isnot in the operable status.




800B2E11ExecutingCMDRJE

The specified journal ID is not registered.50002E20ExecutingCMDRJE

The operation failed because the specified journal is notregistered.





Table 71 SSB codes returned by raidcom modify journal (continued)

raidcom modify journal


Error message

SSB2SSB1



The timer type cannot be changed because the specified journalbelongs to the extended consistency group.


The parameter of inflow control cannot be changed becausethe specified journal is not a primary journal.


The cache mode option or the data overflow monitoring timecannot be changed because the specified journal is used byboth the primary and the secondary journals.


An internal error occurred.50EE2EE4ExecutingCMDRJECall HPE technical support.

Table 72 SSB codes returned by raidcom modify ldev

raidcom modify ldev


Error message

SSB2SSB1



An LDEV for which an LU path is set in NAS Platform (UserLU) cannot have the Command Device attribute.


Table 73 SSB codes returned by raidcom modify ldev -alua

raidcom modify ldev -alua


Error message

SSB2SSB1

The LDEV number is out of settable range.00002E00ExecutingCMDRJE

The status of the HA pair is not able to change ALUA.00592E11ExecutingCMDRJE



The specified LDEV is not installed.00002E20ExecutingCMDRJE

The number of the host groups which can be set by ALUAexceeded the maximum.


An internal error occurred.FEEC2EE8ExecutingCMDRJE

288 Troubleshooting

Table 74 SSB codes returned by raidcom modify ldev -mp_blade_id

raidcom modify ldev -mp_blade_id


Error message

SSB2SSB1




LDEV is not installed.00002E20ExecutingCMDRJE


Table 75 SSB codes returned by raidcom delete device_grp

raidcom delete device_grp


Error message

SSB2SSB1



LDEV is not registered in the device group.00022E20ExecutingCMDRJE

A device group is not installed.21002E20ExecutingCMDRJE

The number of LDEVs that can be deleted in a operationexceeds the maximum. The number of LDEVs that can bedeleted includes the number of LDEVs of a LUSE.



Table 76 SSB codes returned by raidcom add device_grp

raidcom add device_grp


Error message

SSB2SSB1



The number of device name in the system has reached themaximum.


The device name of an LDEV is duplicated in the system.000A2E22ExecutingCMDRJE

The number of LDEVs that can be registered in a operationexceeds the maximum. The number of LDEVs that can beregistered includes the number of LDEVs of a LUSE.



It exceeds the number of device group in the system.21002E23ExecutingCMDRJE

The LDEV to be allocated to the device group is not set thedevice name.



Table 76 SSB codes returned by raidcom add device_grp (continued)

raidcom add device_grp


Error message

SSB2SSB1

The specified resource group ID of the LDEV cannot beregistered because it is different from other resource group IDof the LDEV in the specified device group.


An internal error occurred.FEEC2EEAExecutingCMDRJECall HPE technical support.

Table 77 SSB codes returned by raidcom modify ldev -ldev_name

raidcom modify ldev -ldev_name


Error message

SSB2SSB1


LDEV nickname is not specified.00072E00ExecutingCMDRJE


Unavailable character is included in LDEV nickname.--ExecutingInvalid Character

Table 78 SSB codes returned by raidcom initialize ldev

raidcom initialize ldev


Error message

SSB2SSB1


The specified LDEV is used for a Business Copy pair.00002E10AsyncGet Command Status

The specified LDEV is used for a Continuous AccessSynchronous pair or a Continuous Access Journal pair.




The specified LDEV is used for a Fast Snap pair or a Snapshotpair.


The specified LDEV is used on the system disk.00082E10AsyncGet Command Status

LDEV is not blocked.00102E10AsyncGet Command Status

The specified LDEV is a CC/XRC attribute device.00122E10AsyncGet Command Status

The specified LDEV is used as the primary volume of an HApair.




The formatting operation cannot be performed because theencryption value of the key number that is set to encryptionECC is invalid.


The formatting operation cannot be performed because thecheck sum of the encryption key is not coincident.


290 Troubleshooting

Table 78 SSB codes returned by raidcom initialize ldev (continued)



Error message

SSB2SSB1

The specified LDEV cannot be operated because capacitysaving status is Failed.




The LDEV is in shredding.00072E11AsyncGet Command Status

The operation cannot be performed because LDEV is nowexpanding.


The operation cannot be performed because the virtual diskspace is blocked.



The operation failed because capacity expansion of the paritygroup to which the specified LDEV belongs is enabled.




The parity group or the external volume group to which thespecified LDEV belongs is used in another operation.


The operation cannot be done because the parity group formatis not done for the parity group to which the specified LDEVbelongs.


The operation of Thin Provisioning V-VOL cannot be donebecause there is a blocked pool.


The operation of Thin Provisioning V-VOL cannot be donebecause there is a blocked pool volume.








The processing stopped because aborting processing isrequired.




The quick format cannot be performed because the totalnumber of parity groups in which the LDEVs in quick formatting


or the LDEVs blocked while quick formatting are implementedexceeds the maximum number that can be performed at thesame time.

The specified LDEV is used for a Thin Provisioning.000A2E30AsyncGet Command Status

The specified LDEV is used as a quorum disk.000C2E30AsyncGet Command Status

The specified LDEV is used as a pool volume.000E2E30Executing/AsyncCMDRJE


Table 78 SSB codes returned by raidcom initialize ldev (continued)



Error message

SSB2SSB1

Get Command Status

The specified LDEV is used as a journal volume.000F2E30AsyncGet Command Status

Volume Security for Mainframe is set to the specified LDEV.001A2E30AsyncGet Command Status

Quick format cannot be done because the target LDEV is notan internal volume.


The specified LDEV is a Data Retention/Volume Retentionattribute device.


The specified LDEV is a pool volume and the pool volumeinclude the Thin Provisioning volume that is not in the blockedstatus.




The specified ldev is used as the TSE-VOL.00752E30ExecutingCMDRJE

The operation cannot be performed because the specifiedLDEV is a deduplication system data volume.


The operation cannot be performed because the specifiedLDEV is a volume for which capacity saving setting is enabled.


Maintenance work cannot be performed because the targetLDEV is a quorum disk.


LDEV cannot be formatted because there is no normal externalpath.




An internal error occurred.0A182EE8AsyncGet Command Status


The specified parameter is incorrect. Check theRAIDManagerReference Guide.




292 Troubleshooting

Table 79 SSB codes returned by raidcom modify ldev -command_device

raidcom modify ldev -command_device


Error message

SSB2SSB1

The command device cannot be set to the specified LDEVbecause of the following causes.


• The LDEV is used for a Business Copy pair.

• The reserve attribute of a Business Copy is configured.

The specified LDEV is used for a Continuous AccessSynchronous pair.


The specified LDEV is used for a Continuous Access Journalpair or a journal.


The specified volume cannot be set because it is used by aFast Snap pair or a Snapshot pair.




The specified LDEV is used as the secondary volume of anHA.


The operation failed because the T10 PI attribute of thespecified LDEV is enabled.



The following settings cannot be performed because theprogram product of LUN Manager is not installed.


• Command device settings

• Command security settings

The emulation type of the specified volume is not OPENvolume.


The command device cannot be set because LDEV is used asa virtual volume of Fast Snap or Snapshot.


The specified volume cannot be set because it is a quorumdisk.


The specified volume cannot be set because it is a systemdisk.


The specified volume cannot be set because it is a pool volume.000E2E30ExecutingCMDRJE

The specified LDEV cannot be released because it is commanddevice that is being used.


The specified volume cannot be set because it is a LUSEvolume.


The command device cannot be set to the specified LDEVbecause of the following causes.


• It is used as an Auto LUN.

• The reserve attribute of an Auto LUN is configured.

The specified volume cannot be used as a command devicebecause it is set by a Data Retention.



Table 79 SSB codes returned by raidcom modify ldev -command_device (continued)

raidcom modify ldev -command_device


Error message

SSB2SSB1



The specified LDEV is used as an ALU.00962E30ExecutingCMDRJE



An internal error occurred.FEEC2EE8ExecutingCMDRJECall HPE technical support.

Table 80 SSB codes returned by raidcom modify ldev -ssid

raidcom modify ldev -ssid


Error message

SSB2SSB1

SSID cannot be changed because there are LDEVs in theboundary where the specified LDEV belongs.


The specified SSID is used for the other boundary.72012E22ExecutingCMDRJE

An internal error occurred. Call HPE technical support.FEEC2EE8ExecutingCMDRJE



Table 81 SSB codes returned by raidcom modify ldev -status nml

raidcom modify ldev -status nml


Error message

SSB2SSB1


The specified LDEV is used for a Business Copy pair.00002E10AsyncGet Command Status

The specified LDEV is used for a Continuous AccessSynchronous pair or a Continuous Access Journal pair.






The specified LDEV is used as a system disk.00082E10AsyncGet Command Status

LDEV is not blocked.00102E10ExecutingCMDRJE

The specified LDEV is a CC/XRC attribute device.00122E10AsyncGet Command Status

The specified LDEV is not formatted after it is used as thejournal volume.




294 Troubleshooting

Table 81 SSB codes returned by raidcom modify ldev -status nml (continued)

raidcom modify ldev -status nml


Error message

SSB2SSB1



The associated pool is blocked.600B2E10AsyncGet Command Status

The operation cannot be done because LDEV is not expanding.00092E11AsyncGet Command Status

The operation cannot be done because the virtual disk spaceis blocked.



The parity group or the external group to which the specifiedLDEV belongs is used in another operation.


The operation of Thin Provisioning V-VOL cannot be donebecause there is a blocked pool volume.









The specified LDEV is used as a pool volume.000E2E30AsyncGet Command Status

The specified LDEV is used as a reserved volume of Auto LUN.00142E30AsyncGet Command Status


The specified LDEV cannot be restored because the shreddingor the formatting operation has not been performed.




LDEV cannot be restored because there is no connection pathto the normal external path.




Table 82 SSB codes returned by raidcom modify ldev -status blk

raidcom modify ldev -status blk


Error message

SSB2SSB1


The specified LDEV is used for a pair of Business Copy/FastSnap/Snapshot/Auto LUN V2 or as a relationship of CompatibleFlashCopy/Compatible FlashCopy SE.



Table 82 SSB codes returned by raidcom modify ldev -status blk (continued)



Error message

SSB2SSB1

The specified LDEV is used for a pair of Continuous AccessSynchronous or Continuous Access Journal.







LDEV is not installed, or LDEV is not in the state of Normal.00112E10ExecutingCMDRJE

The specified LDEV is used at the concurrent copy or XRC.00122E10AsyncGet Command Status





The operation cannot be done because LDEV is nowexpanding.


The operation cannot be done because the virtual disk spaceis blocked.



The parity group or the external group to which the specifiedLDEV belongs is used in another operation.






The specified LDEV is not installed.00002E20ExecutionCMDRJE




It is used as a journal.000F2E30ExecutingCMDRJE

The specified LDEV is used as a reserved volume of Auto LUNV2.



It is used as a remote command device.001C2E30AsyncGet Command Status

It is a volume that the Data Retention is set.004E2E30AsyncGet Command Status



It is used as a command device that is used at extendedconsistency group.


296 Troubleshooting

Table 82 SSB codes returned by raidcom modify ldev -status blk (continued)



Error message

SSB2SSB1

THP volume that is not in the blocked state is included in theTHP volume associated with a pool that the pool volume isbelongs to.


Maintenance work cannot be performed because the targetLDEV is a quorum disk.


LDEV cannot be blocked because there is no connection pathto the normal external path.



Table 83 SSB codes returned by raidcom modify ldev -status enable_reallocation/disable_reallocation/new_page_allocation/enable_relocation_policy

raidcommodify ldev -status enable_reallocation/disable_reallocation/new_page_allocation/enable_relocation_policy


Error message

SSB2SSB1

Invalid LDEV number.00002E00ExecutingCMDRJE

The tiering policy is not in the effective range.61012E00ExecutingCMDRJE

The new page assignment tier is invalid.61022E00ExecutingCMDRJE


The shared memory for Smart Tiers or Real Time Smart Tieris not installed.


The specified LDEV is not a virtual volume of Thin Provisioning,Smart Tiers, or Real Time Smart Tier.


The specified LDEV is not a virtual volume of Smart Tiers orReal Time Smart Tier.


The specified LDEV is not a virtual volume of Smart Tiers orReal Time Smart Tier.

00142EE8ExecutingCMDRJE

Table 84 SSB codes returned by raidcom modify ldev -status discard_zero_page

raidcom modify ldev -status discard_zero_page


Error message

SSB2SSB1

The specified LDEV is used for a Business Copy pair.00002E10ExecutingCMDRJE

The specified LDEV is used for a Continuous AccessSynchronous pair.


The specified LDEV is used for a Continuous Access Journalpair.







Table 84 SSB codes returned by raidcom modify ldev -status discard_zero_page (continued)

raidcom modify ldev -status discard_zero_page


Error message

SSB2SSB1

The specified LDEV is used for an Auto LUN pair.00052E10ExecutingCMDRJE

The specified LDEV is blocked.00112E10ExecutingCMDRJE

The associated pool is blocked.600B2E10ExecutingCMDRJE

The page cannot be discarded because the pool volume isbeing deleted or the Tier is being reallocated.


The operation cannot be done because the system pool volumeis blocked.


The operation cannot be done because the power supply isswitched off.


The page cannot be discarded because of the non-operablestatus.



The operation cannot be done because the specified volumeis being formatted.


The specified LDEV is not a virtual volume of Thin Provisioning,Smart Tiers, or Real Time Smart Tier.


The specified LDEV is used as a journal volume.000F2E30ExecutingCMDRJE

It is not associated to a pool.00332E30ExecutingCMDRJE

The specified volume is used by XRC.00652E30ExecutingCMDRJE

The page cannot be discarded because the specified LDEV isa TSE-VOL.


The specified LDEV is a volume of which Data Direct Mappingattribute is enabled.




The page of THP V-VOL cannot be discarded because the LUpath to the host group whose host mode option 97 is enabledis defined to the specified LDEV.


An internal error occurred.00E72EE8ExecutingCMDRJECall HPE technical support.

The specified operation cannot be performed because it is notsupported.


298 Troubleshooting

Table 85 SSB codes returned by raidcom modify ldev -status enable_fullallocation/disable_fullallocation

raidcom modify ldev -status enable_fullallocation/disable_fullallocation


Error message

SSB2SSB1


The specified value of the Full Allocation is invalid.002F2E00ExecutingCMDRJE

Full Allocation cannot be specified to the specified LDEVbecause the emulation type is not supported.


The operation failed because the specified LDEV is a THPV-VOL that belongs to the pool of which capacity expansion isenabled.


The associated pool is blocked.600B2E10ExecutingCMDRJE

The operation cannot be done because a pool volume is beingdeleted.


The free space in the specified pool is insufficient.601B2E10ExecutingCMDRJE

The operation cannot be done because another application,for example Remote Web Console and SVP is used.


The specified LDEV is blocked.001B2E11ExecutingCMDRJE


The specified LDEV is not THP V-VOL.000B2E30ExecutingCMDRJE





The operation cannot be performed because the specifiedLDEV is a volume for which the capacity saving setting isenabled.


The command cannot be accepted because the DKC is busy.After a while, execute the same command.





Table 86 SSB codes returned by raidcom modify ldev -quorum_enable

raidcom modify ldev -quorum_enable


Error message

SSB2SSB1


The device type is invalid.80002E00ExecutingCMDRJE

The serial number is invalid.80012E00ExecutingCMDRJE

The quorum disk ID is out of settable range.A0012E00ExecutingCMDRJE

The specified LDEV is used for Auto LUN.00052E10AsyncGet Command Status


Table 86 SSB codes returned by raidcom modify ldev -quorum_enable (continued)



Error message

SSB2SSB1

The specified LDEV cannot be configured because the LDEVis a virtual volume.




The specified volume belongs to the resource group ofNAS_Platform_System_RSG.


The specified quorum disk ID is being used.A0012E10AsyncGet Command Status

The specified quorum disk is in processing.A0032E10AsyncGet Command Status

The specified quorum disk is used as the quorum disk of thedifferent device.

A0052E10AsyncGet Command Status

The specified LDEV is used as the quorum disk.A0062E10AsyncGet Command Status

The operation failed because the quorum disk was inaccessible.A0072E10AsyncGet Command Status


The specified LDEV is used for other operation.00532E11ExecutingCMDRJE

The external volume is inaccessible.410B2E11AsyncGet Command Status

An unformatted external volume is used. Format the externalvolume, then retry the operation.




The specified LDEV is not the first LDEV that belongs to theexternal volume group.



The specified LDEV is not an external volume.000E2E20AsyncGet Command Status

A shared memory is not installed.810A2E21AsyncGet Command Status

Cache Residency is set to the specified volume.00052E30AsyncGet Command Status

A path is defined to the specified volume.00072E30AsyncGet Command Status



The specified volume is used as a command device.00102E30AsyncGet Command Status

Data Retention is set to the specified volume.004E2E30AsyncGet Command Status



The emulation type of the specified LDEV is not OPEN-V.008E2E30AsyncGet Command Status

The specified LDEV cannot be used because the size of LDEVis less than the minimum capacity of the quorum disk.


300 Troubleshooting

Table 86 SSB codes returned by raidcom modify ldev -quorum_enable (continued)



Error message

SSB2SSB1



Internal error occurred.FEEC2EE8Executing/AsyncCMDRJEGet Command Status

Table 87 SSB codes returned by raidcom modify ldev -quorum_disable

raidcom modify ldev -quorum_disable


Error message

SSB2SSB1


The specified LDEV is not a quorum disk.A0022E10AsyncGet Command Status

The specified quorum disk is in processing.A0032E10AsyncGet Command Status

The pair using the specified quorum disk exists.A0042E10AsyncGet Command Status

The setting of the quorum disk was released but the operationfailed.

A0072E10AsyncGet Command Status

If you display the ldev information using raidcom get ldevcommand, "QRD" (that means the disk is the quorum disk) isnot displayed on VOL_ATTR because the quorum disk settingwas released. But the management information possiblyremains in the external volume.If you define again an external volume in which themanagement information remains as a quorum disk, an errormay occur. When you reuse an external volume which wasused as a quorum disk after removing it, format the externalvolume.

The specified LDEV is being used for other operation.00532E11ExecutingCMDRJE


A shared memory is not installed.810A2E21AsyncGet Command Status

Internal error occurred.FEEC2EE8ExecutingCMDRJEGet Command Status

Table 88 SSB codes returned by raidcom delete lun

raidcom delete lun


Error message

SSB2SSB1

The other than multiplatform volume or OPEN volume isincluded in the specified LDEV.


An used LDEV exists in the specified LDEV.015DB958ExecutingCMDRJE

It cannot be deleted because it is the last path of ContinuousAccess Synchronous.



Table 88 SSB codes returned by raidcom delete lun (continued)

raidcom delete lun


Error message

SSB2SSB1

It cannot be deleted because it is the last path of BusinessCopy.


It cannot be deleted because it is the last path of Fast Snap orSnapshot.

020AB958ExecutingCMDRJE

It cannot be deleted because it is the last path of ContinuousAccess Journal.

020BB958ExecutingCMDRJE

It cannot be deleted because the operation object LU isexecuting host I/O.


It cannot be deleted because the operation object LU isreserved.


The command device is being used in the local RAID Manager.0239B958ExecutingCMDRJE

A command device is being set.0240B958ExecutingCMDRJE

It cannot be deleted because of the ALU path definition.028EB958ExecutingCMDRJE

The command cannot be operated because the virtual LDEVis not defined yet.


The value of LUN exceeds the maximum.0944B958ExecutingCMDRJE

The value of LDEV exceeds the maximum.0945B958ExecutingCMDRJE

The value of host group ID exceeds the maximum.0956B958ExecutingCMDRJE

The program product is not installed.0957B958ExecutingCMDRJE

Host group is not installed.0959B958ExecutingCMDRJE

An invalid LDEV exists in the specified LDEVs.095DB958ExecutingCMDRJE

Multiple LDEVs cannot be specified.098CB958ExecutingCMDRJE

When the host mode option 60 is set, the LU path of LUN0cannot be set or released.


The LU path cannot be deleted because the virtual LDEV IDof the specified volume was deleted.


The specified port is not mounted.099FB958ExecutingCMDRJE

Another LDEV is already mapped in the specified LUN.09A1B958ExecutingCMDRJE



The command was rejected because the specified port is forNAS Platform (User LU).




302 Troubleshooting

Table 89 SSB codes returned by raidcom add lun

raidcom add lun


Error message

SSB2SSB1

An invalid LDEV exists in the specified LDEVs.00142EF6ExecutingCMDRJE

The LU path cannot be set because it is reserved for Auto LUN.0101B958ExecutingCMDRJE

The LU path cannot be set because it is a deduplication systemdata volume.

010CB958ExecutingCMDRJE

The LU path cannot be set because the volume is adeduplication system data volume.


When an ISCSI is used, the LU path cannot be set in the LDEVother than the OPEN volume.


The attribute of the specified port is Initiator or External.0150B958ExecutingCMDRJE

The other than HMDE volume or OPEN volume is included inthe specified LDEV.


An LU path has already defined in the relevant LDEV.015AB958ExecutingCMDRJE


It exceeds the maximum LUN under the port.015EB958ExecutingCMDRJE

LDEV is set as a pool volume.0178B958ExecutingCMDRJE

The LU path cannot be set because the LDEV is a system disk.017BB958ExecutingCMDRJE

The LU path cannot be set because the LDEV is a journalvolume.


The LU path cannot be set because the access attribute ofLDEV Data Retention is reserved.


The LU path cannot be set because the access attribute ofLDEV Data Retention is different from "Read/Write".

017EB958ExecutingCMDRJE

The LU path cannot be set because the LDEV has an ALUattribute.


When the host mode is External Storage(0x4C), the LU pathcannot be set in other than the external volume.


The LU path cannot be defined because the volume is usedas a Quorum disk.

01C1B958ExecutingCMDRJE

The number of the host groups which can be set by ALUAexceeded the maximum.

01DCB958ExecutingCMDRJE

The operation cannot be performed because the specifiedLDEV is the external volume having the Data Direct Mappingattribute.

01DEB958ExecutingCMDRJE

The LU path cannot be defined because the LDEV belongs tothe parity group of which capacity expansion is enabled.

01DFB958ExecutingCMDRJE

The host group and the LDEV that configure the LU path donot exist in the same virtual storage machine.

01F2B958ExecutingCMDRJE

The LU path cannot be defined because the virtual LDEVinformation of the specified LDEV is not defined yet.


The path of the external volume which has an OM attributecannot be defined



Table 89 SSB codes returned by raidcom add lun (continued)

raidcom add lun


Error message

SSB2SSB1

The LU path cannot be added because the setting of the T10PI attribute on the specified port or on the specified LDEV isnot correct.


Enable the T10 PI attribute on the specified port. Otherwise,disable the T10 PI attribute on the specified LDEV.


01FAB958ExecutingCMDRJE

Command device cannot be set because it is reserved for AutoLUN.


Command device cannot be set because it is an BusinessCopy pair/or it is reserved.


The command device cannot be operated because it is usedat the local RAID Manager.


A command device cannot be set because LDEV is other thanthe OPEN volume.


The specified LDEV is not installed.065DB958ExecutingCMDRJE

A command device cannot be set because LDEV is the virtualvolume of Fast Snap or Snapshot.


The command cannot be operated because the virtual LDEVis not defined yet.


The value of LUN exceeds the maximum.0944B958ExecutingCMDRJE

The value of LDEV exceeds the maximum.0945B958ExecutingCMDRJE

Another LDEV is already mapped to the specified LUN.0947B958ExecutingCMDRJE

The value of Host group ID exceeds the maximum.0956B958ExecutingCMDRJE


The specified host group is not installed.0959B958ExecutingCMDRJE


The multiple LDEV cannot be specified.098CB958ExecutingCMDRJE

When the host mode option 60 is set, the LU path of LUN0cannot be set or released.


An invalid LDEV exists in the specified LDEVs.0994B958ExecutingCMDRJE

The LU path cannot be added because the virtual LDEV ID ofthe specified volume was deleted.


The number of paths exceeds the maximum.099CB958ExecutingCMDRJE

Only one path is set for NAS Platform (User LU).099DB958ExecutingCMDRJE

Both the port number and the host group ID are specified.099EB958ExecutingCMDRJE

The specified port is not mounted.099FB958ExecutingCMDRJE



304 Troubleshooting

Table 89 SSB codes returned by raidcom add lun (continued)

raidcom add lun


Error message

SSB2SSB1





The LU path cannot be set in Command Device because Portis NAS Platform (User LU).


Table 90 SSB codes returned by raidcom modify lun

raidcom modify lun


Error message

SSB2SSB1

You do not have the operation authority to operate the relevantresource group.


Specify the resource group that is allocated to the user groupas the operation target or set the operation authority to the usergroup in order to operate the relevant resource group.

The PCB type of the port to which the host group belongs isout of operation target.


The LU path definition does not exist in the host group.5046B958ExecutingCMDRJE


Host group is not installed.5059B958ExecutingCMDRJE

The specified ALUA path priority is invalid.50DDB958ExecutingCMDRJE

Unavailable to operate because another application is inprogress on Remote Web Console or SVP.


Table 91 SSB codes returned by raidcom discover lun

raidcom discover lun


Error message

SSB2SSB1


Table 92 SSB codes returned by raidcom modify pool

raidcom modify pool


Error message

SSB2SSB1

The LDEV number is out of the valid range.00002E00ExecutingCMDRJE

The SSID is out of the valid range.00032E00ExecutingCMDRJE

The specified LDEV number is already used.00102E00AsyncGet Command Status

There are not enough cache management devices.00132E00AsyncGet Command Status


Table 92 SSB codes returned by raidcom modify pool (continued)

raidcom modify pool


Error message

SSB2SSB1

The command cannot be executed by receiving multipleoperations for the same pool ID.


The specified attribute is invalid.002F2E00ExecutingCMDRJE

The value of pool ID is invalid.60002E00ExecutingCMDRJE

The specified pool is for Fast Snap or Snapshot.60012E00ExecutingCMDRJE

The specified maximum reserve rate is not in the effectiverange.


The specified Tier Range value is invalid.60032E00ExecutingCMDRJE

Relations between the specified lower limit of Tier Range andthe Delta value is invalid.


The specified Tier capacity threshold value is out of range.60062E00ExecutingCMDRJE

The threshold of the specified High water mark is out of range.60092E00ExecutingCMDRJE

The operation cannot be done because the specified thresholdof Warning is larger than the threshold of the specified Highwater mark.


The specified tier number is out of range.61002E00ExecutingCMDRJE

The threshold value cannot be changed to the specified value,because the specified pool is used for Data Direct Mapping.


The operation cannot be done because the total capacity ofvirtual volumes for Smart Tiers or Real Time Smart Tier in thesystem exceeds the maximum.

001F2E10Executing/Async


The specified pool is in the state of blocked.600B2E10ExecutingCMDRJE

The setting of the threshold value is less than the pool usagevalue.


The operation cannot be done because it is in the state ofshrinking.


The operation cannot be done because it is being discardedpages.


Pool cannot be restored because the usage rate of pool is100%.


The operation cannot be performed because the specified poolstatus is incorrect.


The operation cannot be done because the Tier is beingdeterred reallocation.


The operation cannot be done because collecting theperformance monitoring data is being prepared.


The specified pool cannot be changed to the pool for DataDirect Mapping, because the threshold value of High watermark is fixed.


The deduplication function is set to be enabled for the specifiedpool.

601F2E10Executing/AsyncCMDRJEGet Command Status

306 Troubleshooting


raidcom modify pool


Error message

SSB2SSB1

The deduplication function cannot be used in the specifiedpool.


The operation cannot be performed because anotherapplication is in progress on Remote Web Console, SVP, oranother software.



The operation cannot be performed because the amountcapacity of provisioning virtual volumes and deduplication


system data volumes defined in the specified pool exceeds themaximum of reserved pool capacity.

The pool is not in the status where the pool option can be set.60032E11ExecutingCMDRJE

The operation cannot be performed because of the internalprocessing.




The storage system is in the internal processing or theconfiguration change processes are conflicting.


The cache segment size is incorrect.81052E11AsyncGet Command Status

The operation cannot be done because there is a blocked partin the storage system.


The command cannot be accepted. Wait a while, and thenexecute the same command.


The Smart Tiers or Real Time Smart Tier operations cannotbe done to the pool because the specified pool contains RAID1 pool VOLs.


The specified pool for Thin Provisioning cannot be changed toa pool for Smart Tiers because the pool is related to TSE-VOL.


The setting cannot be done because the microcode does notsupport Real Time Smart Tier.


The operation cannot be performed because the specified poolis already linked with the virtual volume of Thin Provisioning.


The operation cannot be performed because the pool volumehaving the Data Direct Mapping attribute is included in thespecified pool.


The operation cannot be performed because the specified poolis linked with an LDEV for which the deduplication function isenabled.


The operation cannot be performed because the specified poolis linked with an LDEV that has deduplication data.


The operation cannot be performed because the specified poolis linked with a volume for which capacity saving function isenabled.


Pool ID is not installed.60002E20ExecutingCMDRJE

The specified Tier number is invalid.61012E20ExecutingCMDRJE



raidcom modify pool


Error message

SSB2SSB1

The specified MP blade or MP unit is not installed.83002E20AsyncGet Command Status

The shared memory for Thin Provisioning is not installed.81012E21ExecutingCMDRJE

The shared memory for Smart Tiers or Real Time Smart Tieris not installed.


The operation cannot be performed because of the insufficientcapacity of shared memory.




Data Retention program product is not installed.90142E21ExecutingCMDRJE

The specified LDEV is already defined.00012E22Executing/AsyncCMDRJEGet Command Status

The number exceeds the maximum number of LDEVs that canbe created in the current system configuration.


The number of specified deduplication system data volumesexceeds the maximum limit.


The specified SSID number exceeds the maximum limit.72012E23ExecutingCMDRJE

The specified SSID is already used in the another CU.00202E30AsyncGet Command Status

The SSID is already allocated to the CU.00212E30AsyncGet Command Status

The specified volume is used as an alias device in ParallelAccess Volumes.


An LDEV of another emulation type is allocated in the rangewhere the number is divided into each 32 LDEVs.


The Smart Tiers or Real Time Smart Tier operation cannot bedone to the pool because the specified pool contains theexternal volumes whose cache mode is invalid.


A pool volume cannot be operated because the LDEV of theresource group different from the resource group of the poolvolume belonging to the specified pool is specified.


The page reservation cannot be set on the specified LDEVwith the specified operation.


The operation cannot be performed because the number ofV-VOLs that can be created in the system exceeds themaximum number.


The threshold value 1 is out of range.60002E30ExecutingCMDRJE

The specified pool is for Fast Snap or Snapshot.60032E30ExecutingCMDRJE

The specified pool must be assigned two user-definedthresholds to.


On the specified pool, Tier Reallocation is not enabled.600D2E30ExecutingCMDRJE

308 Troubleshooting


raidcom modify pool


Error message

SSB2SSB1

The specified operation cannot be performed because thespecified pool is not for Thin Provisioning.


Real Time Smart Tier cannot be enabled because an SSDmedium does not exist on Tier 1 of Thin Provisioning.


Real Time Smart Tier cannot be enabled or disabled becausethe pool is for Thin Provisioning.


The operation of Smart Tiers cannot be performed becausethe specified pool is used for Data Direct Mapping.


The operation cannot be performed because the specified poolis for the Smart Tiers pool.


The operation cannot be performed because the specified poolis for Thin Provisioning MF.


The specified pool includes the different RAID levels of volumesalthough the pool cannot include those volumes together.


The specified pool includes external volumes although the poolcannot include those volumes together.


The specified pool cannot be used for a Smart Tiers or RealTime Smart Tier.


The capacity that can be used by the installed program productsexceeds the maximum.




80002E3FExecutingCMDRJE

Pool ID is not installed.00012EE7ExecutingCMDRJE

An internal error occurred at the pool operation.00112EE7ExecutingCMDRJECall HPE technical support.




00F02EE7ExecutingCMDRJE

An internal error occurred in the pool operation.FEEC2EE7ExecutingCMDRJECall HPE technical support.




Table 93 SSB codes returned by raidcom rename pool

raidcom rename pool


Error message

SSB2SSB1

The value of pool ID is out of range.60002E00ExecutingCMDRJE

The pool name cannot be changed because the poolconfiguration is being changed.


Invalid pool ID.60002E20ExecutingCMDRJE

The pool name is duplicated with another pool.60012E31ExecutingCMDRJE


Table 94 SSB codes returned by raidcom delete pool

raidcom delete pool


Error message

SSB2SSB1



All pool volumes associated to a pool cannot be deleted.600B2E00AsyncGet Command Status

The specified LDEV is in the state of blocked.00092E10AsyncGet Command Status

This pool cannot be deleted because a pool volume is beingdeleted.


The operation cannot be done because the pool usage rateexceed the threshold value of the pool usage.


The operation cannot be done because the current capacityrate exceeds the value of maximum reserved capacity rate.


It cannot be deleted because the pool volume is set in the stateof being deterred deleting.


Deleting operation cannot be done because it is beingdiscarded pages.


The deduplication function is set to be enabled for the specifiedpool.




The operation cannot be done because a Fast Snap pair or aSnapshot pair remains or the association with a ThinProvisioning virtual volume exists.


The operation cannot be done because a Fast Snap pair or aSnapshot pair is being deleted or a Thin Provisioning virtualvolume is being deleted.


The operation cannot be done because a pool volume of aspecified pool is being formatted.


The pool is not in the status where the pool can be deleted ora pool volume can be deleted.



310 Troubleshooting

Table 94 SSB codes returned by raidcom delete pool (continued)

raidcom delete pool


Error message

SSB2SSB1





The operation cannot be performed because the specifiedLDEV is linked with the virtual volume having the Data DirectMapping attribute.


The last SSD medium on Tier 1 of Real Time Smart Tier cannotbe deleted.


The operation cannot be performed because the pool capacityis insufficient for Data Direct Mapping.


The specified LDEV is not registered to the pool.00032E20ExecutingCMDRJE

The operation cannot be done because the pool volume is notof a specified pool.


Pool ID is not installed.60002E20Executing/AsyncCMDRJEGet Command Status

The operation cannot be performed because the sharedmemory is not initialized.



The specified LDEV cannot be deleted because it is a top VOLof the pool.


The specified pool is a pool for Fast Snap or Snapshot.60032E30ExecutingCMDRJE



Pool ID is not installed.00F92EE7ExecutingCMDRJE






Table 95 SSB codes returned by raidcom add snap_pool

raidcom add snap_pool


Error message

SSB2SSB1

The LDEV number is out of settable range.00002E00AsyncGet Command Status

Pool ID is out of range.60002E00ExecutingCMDRJE

The type of pool is invalid.60012E00ExecutingCMDRJE


Table 95 SSB codes returned by raidcom add snap_pool (continued)



Error message

SSB2SSB1

The maximum reserve ratio for V-VOL is out of range.60022E00ExecutingCMDRJE

The operation cannot be done because a SATA-E drive in thestate of quick formatting is in the specified LDEV.



The specified LDEV is in the state of blocked, or not installed.00112E10ExecutingCMDRJE

Fast Snap cannot be used because there are not enough cachemanagement devices to create pairs.


The pool cannot be created because there are not enoughresources (VDEV) depending on cache management devices.


The operation cannot be performed because the pool volumeis being deleted.


The operation failed because capacity expansion of the paritygroup to which the specified LDEV belongs is enabled and theother LDEV in the parity group is being used for the other pool.


The specified LDEV is the LDEV configuring the RAIDconfiguration which cannot be used for the pool volume.


The pool is not in the status where the pool volume can beadded.






The specified LDEV is not installed.00002E20AsyncGet Command Status

The operation cannot be performed because the memorycapacity of the shared memory is insufficient.


The operation cannot be done because the shared memoryfor Fast Snap or Snapshot is not initialized.


Fast Snap or Snapshot program product is not installed.90072E21ExecutingCMDRJE

Exceeded the number of pool volume that can be registeredin a pool.


The larger number of drive types than the supportedconfiguration cannot be added to the specified pool.


Pool volume cannot be registered because the drive type ofspecified LDEV is different from the other pool volume type,or the drive type in the pool exceeds the three.



The emulation type of specified LDEV cannot be used as apool VOL.


The specified LDEV has the LU path definition.00072E30AsyncGet Command Status


312 Troubleshooting




Error message

SSB2SSB1

The specified LDEV is used as a system disk.000D2E30AsyncGet Command Status

The specified LDEV is already used as a pool volume.000E2E30AsyncGet Command Status

The specified LDEV is a command device.00102E30AsyncGet Command Status

It cannot be used as a pool volume because the size ofspecified LDEV is less than 8GB.


Creating a pool or adding a pool volume cannot be donebecause CLPR is mixed in the specified pool.


The specified LDEV is used as a V-VOL.005C2E30AsyncGet Command Status

The specified LDEV is used in another program product.005E2E30AsyncGet Command Status

An LDEV, whose emulation type is not available to be mixed,is in the specified LDEVs.


The emulation type of the specified volume is not OPEN-V.006D2E30ExecutingCMDRJE

The operation cannot be done for the following reasons:006E2E30AsyncGet Command Status

• The pool volumes include external volumes whose cachemodes are invalid.

• The pool includes both external volumes whose cachemodes are invalid and internal volumes.

A pool volume cannot be added because the LDEV of theresource group different from the resource group of the poolvolume to which the specified pool belongs is specified.




The specified volume cannot be used as a pool volume.00852E30AsyncGet Command Status




The specified pool attribute differs from the pool attribute ofexisted pool.


The RAID level of the specified LDEV is different from the RAIDlevel of the other pool volumes.


There is a blocked pool volume.00162E31AsyncGet Command Status

External volumes whose cache modes are different areincluded.


The POOL Name is duplicated with another pool.60012E31ExecutingCMDRJE

The pool cannot include volumes in different RAID levelsbecause the pool cannot include those volumes. Or the pool


cannot include the RAID 1 volumes and the volumes of otherRAID levels together.

The pool cannot include both internal volumes and externalvolumes because the pool is not set to Mixable.






Error message

SSB2SSB1

The usage capacity exceeds the license capacity of programproduct.


An internal error occurred.FEEC2EE7ExecutingCMDRJECall HPE technical support.AsyncGet Command Status

An internal error occurred.FFFF2EE7AsyncGet Command StatusCall HPE technical support.





Table 96 SSB codes returned by raidcom add snapshot

raidcom add snapshot

DescriptionError codeExecuting/AsyncError message

SSB2SSB1


A pair cannot be created because there are not enough cachemanagement devices.


The command ends abnormally because the volume whoseLDEV number is out of range is specified as the P-VOL of aFast Snap pair or a Snapshot pair.


The command ends abnormally because the volume whoseLDEV number is out of range is specified as the S-VOL of aFast Snap pair or a Snapshot pair.


The specified pool ID is out of the range.60002E00ExecutingCMDRJE

There are not enough required input parameters.97012E00ExecutingCMDRJE

A pair cannot be created because the volume that has the sizeexceeding the supported size is specified as the P-VOL of aFast Snap pair or a Snapshot pair.


A pair cannot be created because the volume exceeded thesupport size is specified as the S-VOL of a Fast Snap pair ora Snapshot pair.


A pair cannot be created because the V-VOL is specified asthe P-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the pool-VOL is specifiedas the P-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the journal volume ofContinuous Access Journal is specified as the P-VOL of a FastSnap pair or a Snapshot pair.


The command ends abnormally because the LUSE volumesof different structure are specified as the P-VOL and the S-VOL.


314 Troubleshooting

Table 96 SSB codes returned by raidcom add snapshot (continued)



SSB2SSB1

A pair cannot be created because the volume in which the VMAis set is specified as the P-VOL.


A pair cannot be created because the external volume isspecified as the S-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the volume other than V-VOLis specified as the S-VOL of a Fast Snap pair or a Snapshotpair.


A pair cannot be created because the pool-VOL is specifiedas the S-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the volume (the data volumeor the journal volume) of the Continuous Access Journal pair


that is in the intermediate site of the 3DC cascadingconfiguration is specified as the S-VOL of a Fast Snap pair ora Snapshot pair.

A pair cannot be created because the P-VOL of a ContinuousAccess Journal pair is specified as the S-VOL of a Fast Snappair or a Snapshot pair.


A pair cannot be created because the S-VOL of a ContinuousAccess Journal pair is specified as the S-VOL of a Fast Snappair or a Snapshot pair.


A pair cannot be created because the journal volume of theContinuous Access Journal is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


The command ends abnormally because the volume to whichS-VOL Disable option is set is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


A pair cannot be created because the volume to which VMAis set is specified as the S-VOL of a Fast Snap pair oraSnapshot pair.


The command ends abnormally because the volumes ofdifferent Max LBA size are specified as the P-VOL and S-VOLof a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the volumes whosethe number of slots is different are specified as the P-VOL andS-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the Thin Provisioning V-VOLis specified as the S-VOL of a Fast Snap pair or the specifiedFast Snap pair does not exist.


The command ends abnormally because the Business Copyreserved volume is specified as the P-VOL of a Fast Snap pairor aSnapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the P-VOL of a Fast Snap pair oraSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the P-VOL of a Fast Snap pair oraSnapshot pair.






SSB2SSB1

The command ends abnormally because the Auto LUNreserved volume is specified as the P-VOL of a Fast Snap pairor aSnapshot pair.


The command ends abnormally because the P-VOL of aBusiness Copy pair is specified as the S-VOL of a Fast Snappair or aSnapshot pair.


The command ends abnormally because the S-VOL of aBusiness Copy pair is specified as the S-VOL of a Fast Snappair or aSnapshot pair.


The command ends abnormally because the Business Copyreserved volume is specified as the S-VOL of a Fast Snap pairor aSnapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the S-VOL of a Fast Snap pair oraSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the S-VOL of a Fast Snap pair oraSnapshot pair.


The command ends abnormally because the Auto LUNreserved volume is specified as the S-VOL of a Fast Snap pairor aSnapshot pair.


A Fast Snap pair or aSnapshot pair cannot be created becausethe volume of Continuous Access Journal for the delta resync


is specified as the P-VOL of a Fast Snap pair or aSnapshotpair.

A Fast Snap pair or aSnapshot pair cannot be created becausethe volume of Continuous Access Journal pair for the delta


resync operation is specified as the S-VOL of a Fast Snap pairor a Snapshot pair.

The command ends abnormally because the Quorum disk isspecified as the P-VOL of a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the Quorum disk isspecified as the S-VOL of a Fast Snap pair or a Snapshot pair.


A Fast Snap pair or a Snapshot pair cannot be created becausethe Thin Provisioning V-VOL in capacity expanding is specifiedas the P-VOL of a Fast Snap pair or a Snapshot pair.


A pair cannot be created because the page discard (reclaimzero pages) is being executed by a SCSI command from theHost to the specified P-VOL.


A pair cannot be created because the P-VOL of a ContinuousAccess Synchronous pair is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


A pair cannot be created because the S-VOL of a ContinuousAccess Synchronous pair is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


The command ends abnormally because the Business Copypair is being resynchronized when the volume is shared


316 Troubleshooting




SSB2SSB1

between the P-VOL of a Fast Snap/Snapshot pair and theP-VOL of a Business Copy pair.

The command ends abnormally because the Business Copypair status is other than PSUS when the volume is shared


between P-VOL of a Fast Snap/Snapshot pair and the S-VOLof a Business Copy pair.

The operation cannot be performed because the P-VOL of theBusiness Copy pair on which the Quick Restore is being


operated is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.

The pair operation cannot be performed because the volumewhich specifies the volume using two mirrors cannot accept


the specified command in the following configurations usingthree Continuous Access Journal sites.

• 3DC multi target configuration

• 3DC cascade configuration

• Delta resync configuration

A Fast Snap pair cannot be created because the pair status ofall Fast Snap pairs sharing the specified P-VOL is PSUE.


The specified volume cannot be used for the Fast Snap pairoperation because the virtual LDEV ID is deleted.


The Fast Snap pair operation cannot be performed becausethe virtual storage machine of the specified P-VOL is differentfrom the virtual storage machine of the specified S-VOL.


A Fast Snap pair cannot be operated because changing themodel and the serial number in the virtual storage machine ofthe specified P-VOL is in progress.


A Fast Snap pair cannot be operated because changing themodel and the serial number in the virtual storage machine ofthe specified S-VOL is in progress.


The operation failed because the setting of the T10 PI attributeis not match between the specified P-VOL and the specifiedS-VOL.


A pair cannot be created because the page discard (reclaimzero pages) is being executed by a SCSI command from theHost to the specified S-VOL.


A Fast Snap pair cannot be created because the ThinProvisioning V-VOL in capacity expanding is specified as theS-VOL of a Fast Snap pair.


The command ends abnormally because the volume which isbeing deleted is specified.






SSB2SSB1

A Fast Snap pair or a Snapshot pair with the specifiedconsistency group ID cannot be created due to one of thefollowing reasons:


• The specified consistency group ID is used by the BusinessCopy.

• The number of pairs that can be defined in a consistencygroup exceeds the maximum.

• The pair created by using the same P-VOL already existsin the specified consistency group.

A Fast Snap pair specifying CTG mode cannot be createdbecause the maximum number of consistency groups hasalready been defined.


A Fast Snap pair or a Snapshot pair cannot be created due tounavailable of the pool.


A Fast Snap pair or a Snapshot pair cannot be created becausethere are not enough pair tables.


A Fast Snap pair or a Snapshot pair cannot be created becausethere are not enough differential tables.


A pair cannot be created because there is not enough freeshared memory space.


The command ends abnormally because the pair is in the stateof unacceptable the command.


A Fast Snap pair or a Snapshot pair cannot be created becausethe number of Fast Snap pairs or Snapshot pairs has alreadyreached the maximum.


A Fast Snap pair cannot be created because the maximumnumber of Snapshot IDs (MU numbers) has already been inuse for the specified P-VOL.


A Fast Snap pair cannot be created because the maximumnumber of Snapshot groups has already been defined, or the


maximum number of Fast Snap pairs has already been definedin the specified Snapshot group.

A Fast Snap pair cannot be created because the THP pool isbeing initialized.


The pair cannot be created because the number of pair layersin the cascade configuration exceeds the maximum number.


The pair cannot be created because the number of cloneattribute pair layers exceeds the maximum number.


When the pair status is other than PAIR or PSUS, you cannotcreate a pair by specifying the S-VOL of a Fast Snap pair.


Fast Snap pairs that can be cascaded or cloned and Fast Snappairs that cannot be cascaded or cloned cannot be containedin a snapshot tree.


The operation cannot be performed because the snapshot treeis being deleted.


318 Troubleshooting




SSB2SSB1

An error occurred at the operation of Fast Snap due to one ofthe following reasons:


• The LDEV number specified for the P-VOL or the S-VOL isincorrect.

• The LDEV specified as the P-VOL or the S-VOL is notpaired.

• The pair of the specified P-VOL or the S-VOL is not readyto perform the specified operation.

• The specified Snapshot ID (MU number) is wrong.

• The specified Snapshot ID (MU number) is already used.

• The specified pool is not in the usable status.

• The license capacity has exceeded the maximum.

• The control table for Fast Snap is depleted.

• The number of pairs that can be created in a snapshot treehas exceeded the maximum.

The operation cannot be performed because power-off is inprogress.


The operation failed because multiple versions of DKCMAINmicrocode are included.


A pair cannot be created because the specified snapshot groupcontains Fast Snap pairs with the clone attribute and withoutthe clone attribute.


A pair cannot be created in the same consistency group as theFast Snap pair which uses the specified P-VOL as an S-VOL.


A Fast Snap pair or a Snapshot pair cannot be created becausethe specified P-VOL is a LUSE volume.


A pair cannot be created because there is a pair in the specifiedprimary volume, which is using a different pool number fromthe specified pool number.


The specified pair operation cannot be performed for thespecified pool.


The consistency group to be used in the specified SnapshotGroup is in one of the following status:


• The number of pairs that can be defined in a consistencygroup exceeds the maximum.

• The pair created by using the same P-VOL already existsin the specified consistency group.


The command ends abnormally because an unmounted volumeis specified as the P-VOL of a Fast Snap pair or a Snapshotpair.


The command ends abnormally because the blocked volumeis specified as the P-VOL of a Fast Snap pair or a Snapshotpair.






SSB2SSB1

The command ends abnormally because the volume informatting is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because an unmounted volumeis specified as the S-VOL of a Fast Snap pair or a Snapshotpair.


The command ends abnormally because the blocked volumeis specified as the S-VOL of a Fast Snap pair or a Snapshotpair.


The command ends abnormally because the volume informatting is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


When you create a pair with the clone attribute, you mustspecify the S-VOL.


The command ends abnormally because the shared memory(FC, TPF, or Extension1) is not added for necessary capacity.


The shared memory for Fast Snap or Snapshot is not installed.81082E21ExecutingCMDRJE

A Fast Snap pair or a Snapshot pair cannot be created due toone of the following reasons:


• The shared memory is not expanded for necessary capacity.

• It is in the initializing process.

The shared memory is not installed.810A2E21ExecutingCMDRJE


The virutal LDEV ID for a virtual storage machine is not definedon the specified LDEV.





A pair cannot be created because the volume is already usedin the S-VOL of a Fast Snap pair or a Snapshot pair is specifiedas the P-VOL.


A pair cannot be created because the volume is already usedas the P-VOL of a Fast Snap pair or a Snapshot pair is specifiedas the S-VOL.


A pair cannot be created because the volume is already usedas the S-VOL of a Fast Snap pair or a Snapshot pair is specifiedas the S-VOL.


The command ends abnormally because the volume other thanOPEN-V is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


A pair cannot be created because the volume whose commanddevice is set is specified as the P-VOL of a Fast Snap pair ora Snapshot pair.


320 Troubleshooting




SSB2SSB1

The command ends abnormally because the volume other thanOPEN-V is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


A pair cannot be created because the volume whose commanddevice is set is specified as the S-VOL of a Fast Snap pair ora Snapshot pair.


The command ends abnormally because the volume havingno path definition is specified as the P-VOL of a Fast Snap pairor the specified Fast Snap pair does not exist.


The command ends abnormally because the volume havingno path definition is specified as the S-VOL of a Fast Snap pairor the specified Fast Snap pair does not exist.


The command ends abnormally because the external volumemapped for the online data migration is specified as the P-VOLof a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the external volumemapped for the online data migration is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.


The pair operation is rejected because the specified volumeas the primary volume is a reserved volume for HA, or a volumefor the HA pair which is in the invalid status.


The pair operation is rejected because the specified volumeas the secondary volume is a reserved volume for HA, or avolume for an HA pair.




The specified LDEV is an external volume of which Data DirectMapping attribute is enabled.


The specified LDEV is a virtual volume of which Data DirectMapping attribute is enabled.




A pair cannot be created because the attribute of the pool isother than Fast Snap or Snapshot is specified.


A pair cannot be created because the capacity exceeds thelicensed capacity.


For creation of a pair with the cascade or clone attribute, a ThinProvisioning V-VOL is not specified for the S-VOL.




An internal error occurred. Call HPE technical support.FEEC2EC6ExecutingCMDRJE




Table 97 SSB codes returned by raidcom modify snapshot

raidcom modify snapshot


SSB2SSB1


The MU number exceeds the maximum.000B2E00ExecutingCMDRJE

The command ends abnormally because the volume whoseLDEV number is out of range is specified as the P-VOL of a FastSnap pair or a Snapshot pair.


The command cannot be executed because the clonespecification of the input parameter and the clone attribute of aFast Snap pair to be operated do not match.


The command ends abnormally because the Business Copyreserved volume is specified as the P-VOL of a Fast Snap pairor a Snapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUN reservedvolume is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Quorum disk isspecified as the P-VOL of a Fast Snap pair or a Snapshot pair.


The Fast Snap pair or the Snapshot pair cannot be restoredbecause the Continuous Access Synchronous pair status is


other than PSUS or PSUE when the volume is shared betweenthe P-VOL of a Fast Snap/Snapshot pair and the P-VOL of aContinuous Access Synchronous pair.

A Fast Snap pair or a Snapshot pair cannot be restored becausethe Continuous Access Journal pair status is other than PSUS


or PSUE when the volume is shared between the P-VOL of aFast Snap/Snapshot pair and the P-VOL of a Continuous AccessJournal pair.

A Snapshot data cannot be obtained because the ContinuousAccess Synchronous pair status is COPY when the volume is


shared between the P-VOL of a Fast Snap/Snapshot pair andthe S-VOL of a Continuous Access Synchronous pair.

A Snapshot data cannot be obtained because the ContinuousAccess Journal pair status is COPY when the volume is shared


between the P-VOL of a Fast Snap/Snapshot pair and the S-VOLof a Continuous Access Journal pair.

The command ends abnormally because the Business Copypair is being resynchronized when the volume is shared between


the P-VOL of a Fast Snap/Snapshot pair and the P-VOL of aBusiness Copy pair.




322 Troubleshooting

Table 97 SSB codes returned by raidcom modify snapshot (continued)



SSB2SSB1

The Fast Snap pair or the Snapshot pair cannot be restoredbecause the Fast Snap pair or the Snapshot pair status is other


than PSUS or PSUE when the volume is shared between theP-VOL of a Fast Snap/Snapshot pair and the P-VOL of aBusiness Copy pair.

The Fast Snap pair or the Snapshot pair cannot be restoredbecause the Fast Snap pair or the Snapshot pair status is other


than PSUS when the volume is shared between the P-VOL ofa Fast Snap/Snapshot pair and the S-VOL of a Business Copypair.

A Snapshot data cannot be obtained because the ContinuousAccess Synchronous asynchronous pair status is other than


PSUS or PSUE when the volume is shared between the P-VOLof a Fast Snap/Snapshot pair and the S-VOL of a ContinuousAccess Synchronous asynchronous pair.




The pair operation cannot be performed because the volumewhich specifies the volume using two mirrors cannot accept the


specified command in the following configurations using threeContinuous Access Journal sites.

• 3DC multi target configuration

• 3DC cascade configuration

• Delta resync configuration

A Fast Snap pair operation cannot be performed because thepair status of all Fast Snap pairs sharing the specified P-VOLis PSUE.




The Fast Snap pair operation cannot be performed because thevirtual storage machine of the specified P-VOL is different fromthe virtual storage machine of the specified S-VOL.


The Fast Snap pair operation cannot be performed because thevirtual LDEV ID of the specified volume is deleted.


A Fast Snap pair or a Snapshot pair cannot be created due tounavailable of the pool.


A Snapshot data cannot be obtained because the pool or thepool-VOL is blocked.


A Fast Snap pair or a Snapshot pair cannot be created becausethere are not enough pair tables.


A Fast Snap pair or a Snapshot pair cannot be created becausethere are not enough differential tables.


A pair cannot be created because there is not enough freeshared memory space.






SSB2SSB1

The command ends abnormally because other than the raidcomadd snapshot command is issued for the volume other than theFast Snap pair or the Snapshot pair.




The Fast Snap pair or the Snapshot pair cannot be restoredbecause the volume is shared between the P-VOL of a Fast


Snap/Snapshot pair and the S-VOL of a Continuous AccessSynchronous pair.

The Fast Snap pair or the Snapshot pair cannot be restoredbecause the volume is shared between the P-VOL of a Fast


Snap/Snapshot pair and the S-VOL of a Continuous AccessJournal pair.

The Fast Snap pair or the Snapshot pair cannot be restored dueto one of the following reasons:


• Snapshot data of a restore target Fast Snap pair or Snapshotpair is being obtained per consistency group.

• Snapshot data of a different pair whose primary volume isthe restore target P-VOL of a Fast Snap pair or a Snapshotpair is being obtained per consistency group.

The clone attribute of the specified Fast Snap pair is enabled.97102E10ExecutingCMDRJE






• The LDEV specified as the P-VOL or the S-VOL is not paired.

• The pair of the specified P-VOL or the S-VOL is not ready toperform the specified operation.








The pair operation cannot be performed because the status ofthe pair that uses the specified P-VOL as an S-VOL is not PSUS.


The command was rejected because pairs in the status otherthan PAIR exist under the specified pair.





324 Troubleshooting




SSB2SSB1

The command ends abnormally because the blocked volume isspecified as the P-VOL of a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the volume informatting is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.









The virtual storage machine with the specified serial number isnot found.



The Fast Snap pair or the Snapshot pair cannot be restoredbecause the volume that is set the S-VOL Disable is specifiedas the P-VOL.


The command ends abnormally because the volume other thanOPEN-V is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.




The pair operation is rejected because the specified volume asthe primary volume is a reserved volume for HA, or the volumefor the HA pair which is in the invalid status.


The pair operation is rejected because the specified volume asthe secondary volume is a reserved volume for HA, or thevolume for the HA pair.








The specified operation is not supported in the current microcodeversion.








Table 98 SSB codes returned by raidcom get snapshot

raidcom get snapshot


SSB2SSB1


Table 99 SSB codes returned by raidcom delete snapshot

raidcom delete snapshot


SSB2SSB1


The MU number exceeds the maximum.000B2E00ExecutingCMDRJE



The command ends abnormally because the Business Copyreserved volume is specified as the P-VOL of a Fast Snap pairor a Snapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the P-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUNreserved volume is specified as the P-VOL of a Fast Snap pairor a Snapshot pair.


The command ends abnormally because the Business Copypair is being resynchronized when the volume is shared


between the P-VOL of a Fast Snap/Snapshot pair and theP-VOL of a Business Copy pair.




A Snapshot data cannot be obtained because the ContinuousAccess Synchronous asynchronous pair status is other than


PSUS or PSUE when the volume is shared between the P-VOLof a Fast Snap/Snapshot pair and the S-VOL of a ContinuousAccess Synchronous asynchronous pair.








326 Troubleshooting

Table 99 SSB codes returned by raidcom delete snapshot (continued)



SSB2SSB1



The operation failed because the specified LDEV which isholding the attribute of SLU is bind to the LDEV which is holdingthe attribute of ALU.


A Snapshot data cannot be obtained because the pool or thepool-VOL is blocked.


The command ends abnormally because other than the raidcomadd snapshot command is issued for the volume other thanthe Fast Snap pair or the Snapshot pair.







• The LDEV specified as the P-VOL or the S-VOL is notpaired.

• The pair of the specified P-VOL or the S-VOL is not readyto perform the specified operation.






You do not have the operation authority to operate the relevantresource group.Specify the resource group that is allocated to the user groupas the operation target, or set the operation authority to theuser group in order to operate the relevant resource group.




The operation cannot be performed because a pair exists underthe specified pair.


The operation cannot be performed because the specifiedvolume is not a root volume of a pair with the cascade or cloneattribute, or the volume is an S-VOL in another snapshot tree.





The command ends abnormally because the blocked volumeis specified as the P-VOL of a Fast Snap pair or a Snapshotpair.



Table 99 SSB codes returned by raidcom delete snapshot (continued)



SSB2SSB1











Table 100 SSB codes returned by raidcom mount snapshot

raidcom mount snapshot


Error message

SSB2SSB1





The command ends abnormally because the volume that hasthe size exceeding the supported size is specified as the P-VOLof a Fast Snap pair or a Snapshot pair.




The command ends abnormally because the external volumeis specified as the S-VOL of a Fast Snap pair or a Snapshotpair.


The command ends abnormally because the volume other thanV-VOL is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the pool-VOL isspecified as the S-VOL of a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the volume (the datavolume or the journal volume) of the Continuous Access Journal


pair that is in the intermediate site of the 3DC cascadingconfiguration is specified as the S-VOL of a Fast Snap pair ora Snapshot pair.

The command ends abnormally because the P-VOL of aContinuous Access Journal pair is specified as the S-VOL ofa Fast Snap pair or a Snapshot pair.


328 Troubleshooting

Table 100 SSB codes returned by raidcom mount snapshot (continued)



Error message

SSB2SSB1

The command ends abnormally because the S-VOL of aContinuous Access Journal pair is specified as the S-VOL ofa Fast Snap pair or a Snapshot pair.


The command ends abnormally because the journal volumeof the Continuous Access Journal is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.




The command ends abnormally because the volume to whichVMA is set is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.






A pair cannot be created because the Thin Provisioning V-VOLis specified as the S-VOL of a Fast Snap pair or the specifiedFast Snap pair does not exist.


The command ends abnormally because the P-VOL of aBusiness Copy pair is specified as the S-VOL of a Fast Snappair or a Snapshot pair.


The command ends abnormally because the S-VOL of aBusiness Copy pair is specified as the S-VOL of a Fast Snappair or a Snapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the volume ofContinuous Access Journal pair for the delta resync operation


is specified as the S-VOL of a Fast Snap pair or a Snapshotpair.

The command ends abnormally because the P-VOL of aContinuous Access Synchronous pair is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the S-VOL of aContinuous Access Synchronous pair is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.








Error message

SSB2SSB1



The command ends abnormally because the specified S-VOLis assigned to a Fast Snap pair.


The operation failed because the setting of the T10 PI attributeis not match between the specified P-VOL and the specifiedS-VOL.


The command ends abnormally because the volume which isbeing deleted is specified.


The command ends abnormally because the specified FastSnap pair is not exist.


The command ends abnormally because the specified FastSnap pair is assigned to an S-VOL.























The command ends abnormally because the volume is alreadyused as the P-VOL of a Fast Snap pair or a Snapshot pair isspecified as the S-VOL.


330 Troubleshooting




Error message

SSB2SSB1

The command ends abnormally because the volume is alreadyused as the S-VOL of a Fast Snap pair or a Snapshot pair isspecified as the S-VOL.




The command ends abnormally because the volume whosecommand device is set is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


The command ends abnormally because the volume havingno path definition is specified as the S-VOL of a Fast Snap pairor the specified Fast Snap pair does not exist.




The command ends abnormally because the specified P-VOLis not a P-VOL of a Fast Snap pair.










The operation cannot be performed because the specifiedvolume is a THP V-VOL with the SLU attribute.


The specified LDEV is a V-VOL for which the Data DirectMapping attribute is enabled.


For mapping pairs with the cascade or clone attribute, the ThinProvisioning V-VOL is not specified as an S-VOL.




The operation cannot be performed because the selectedresource belongs to NAS_Platform_System_RSG.



Table 101 SSB codes returned by raidcom replace snapshot

raidcom replace snapshot


Error message

SSB2SSB1



The command ends abnormally because the volume that hasthe size exceeding the supported size is specified as the P-VOLof a Fast Snap pair or a Snapshot pair.




The command ends abnormally because the external volumeis specified as the S-VOL of a Fast Snap pair or a Snapshotpair.




The command ends abnormally because the pool-VOL isspecified as the S-VOL of a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the volume (the datavolume or the journal volume) of the Continuous Access Journal


pair that is in the intermediate site of the 3DC cascadingconfiguration is specified as the S-VOL of a Fast Snap pair ora Snapshot pair.

The command ends abnormally because the P-VOL of aContinuous Access Journal pair is specified as the S-VOL ofa Fast Snap pair or a Snapshot pair.


The command ends abnormally because the S-VOL of aContinuous Access Journal pair is specified as the S-VOL ofa Fast Snap pair or a Snapshot pair.


The command ends abnormally because the journal volumeof the Continuous Access Journal is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.




The command ends abnormally because the volume to whichVMA is set is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.






A pair cannot be created because the Thin Provisioning V-VOLis specified as the S-VOL of a Fast Snap pair or the specifiedFast Snap pair doest not exist.


332 Troubleshooting

Table 101 SSB codes returned by raidcom replace snapshot (continued)



Error message

SSB2SSB1

The command ends abnormally because the P-VOL of aBusiness Copy pair is specified as the S-VOL of a FastSnappair or a Snapshot pair.


The command ends abnormally because the S-VOL of aBusiness Copy pair is specified as the S-VOL of a Fast Snappair or a Snapshot pair.


The command ends abnormally because the Auto LUN sourcevolume is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the Auto LUN targetvolume is specified as the S-VOL of a Fast Snap pair or aSnapshot pair.


The command ends abnormally because the volume ofContinuous Access Journal pair for the delta resync operation


is specified as the S-VOL of a Fast Snap pair or a Snapshotpair.

The command ends abnormally because the P-VOL of aContinuous Access Synchronous pair is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.


The command ends abnormally because the S-VOL of aContinuous Access Synchronous pair is specified as the S-VOLof a Fast Snap pair or a Snapshot pair.






The command ends abnormally because the specified S-VOLis not assigned to a Fast Snap pair.








The command ends abnormally because the specified FastSnap pair is assigned to an S-VOL.


The command ends abnormally because the specified FastSnap pair is not assigned to an S-VOL.



The operation cannot be performed because the SVOL is thenode volume.








Error message

SSB2SSB1


















The command ends abnormally because the volume is alreadyused as the P-VOL of a Fast Snap pair or a Snapshot pair isspecified as the S-VOL.


The command ends abnormally because the volume is alreadyused as the S-VOL of a Fast Snap pair or a Snapshot pair isspecified as the S-VOL.




The command ends abnormally because the volume whosecommand device is set is specified as the S-VOL of a FastSnap pair or a Snapshot pair.


The command ends abnormally because the volume havingno path definition is specified as the S-VOL of a Fast Snap pairor a Snapshot pair.










334 Troubleshooting




Error message

SSB2SSB1

For replacement of pairs with the cascade or clone attribute,a Thin Provisioning V-VOL is not specified for the S-VOL.






Table 102 SSB codes returned by raidcom unmount snapshot

raidcom unmount snapshot


Error message

SSB2SSB1











The command ends abnormally because the specified S-VOLis not assigned to a Fast Snap pair.








The command ends abnormally because the specified FastSnap pair is not assigned to an S-VOL.



The operation cannot be performed because the SVOL is thenode volume.






Table 102 SSB codes returned by raidcom unmount snapshot (continued)

raidcom unmount snapshot


Error message

SSB2SSB1















The command ends abnormally because the specified P-VOLis not a P-VOL of a Fast Snap pair.












Table 103 SSB codes returned by raidcom add ssid

raidcom add ssid


Error message

SSB2SSB1

The CU number of the RCU exceeds the effective value.30012E00ExecutingCMDRJE

The command cannot be executed because the parameter ofthe specified RCU is invalid.


The CU number is out of effective range.71002E00ExecutingCMDRJE

The operation cannot be done because the microcode is beingchanged.


The serial number, product ID, or SSID of the target storagesystem is incorrect.


336 Troubleshooting

Table 103 SSB codes returned by raidcom add ssid (continued)

raidcom add ssid


Error message

SSB2SSB1

The command cannot be executed because the specified RCUis not registered.


The operation cannot be performed due to one of the followingreasons:


• The number of RCUs registered in MCU or RCU is morethan four.

• The number of RCUs registered in the system is more than64 in the case of specifying the cu free.

The number of the specified SSIDs is invalid.33012E23ExecutingCMDRJE

The command cannot be executed because the RCUidentification code of a path is invalid.


An internal error occurred.00EF2ED6ExecutingCMDRJECall HPE technical support.

The SSID is invalid.33002ED6ExecutingCMDRJE



Table 104 SSB codes returned by raidcom delete ssid

raidcom delete ssid


Error message

SSB2SSB1

The CU number of the RCU exceeds the effective value.30012E00ExecutingCMDRJE

The command cannot be executed because the parameter ofthe specified RCU is invalid.





The serial number, the product ID, or the SSID of the remotestorage system is invalid.


The command cannot be executed because the specified RCUis not registered.


The number of the specified SSIDs is invalid.33012E23ExecutingCMDRJE


The SSID is invalid.33002ED6ExecutingCMDRJE




Table 105 SSB codes returned by raidcom add thp_pool

raidcom add thp_pool


Error message

SSB2SSB1

The LDEV number is out of settable range.00002E00AsyncGet Command Status


The type of pool is invalid.60012E00ExecutingCMDRJE

The maximum reserve ratio of V-VOL is out of range.60022E00ExecutingCMDRJE

The threshold of the specified High water mark is out of range.60092E00ExecutingCMDRJE

The operation cannot be done because the specified thresholdof Warning is larger than the threshold of the specified Highwater mark.



The operation cannot be done because a SATA-E drive in thestate of quick formatting is in the specified LDEV.


The specified LDEV is in the state of blocked, or not installed.00112E10ExecutingCMDRJE

The pool cannot be created because there are not enoughresources (VDEV) depending on cache management devices.


The operation cannot be performed because the pool volumeis being deleted.




The operation failed because capacity expansion of the paritygroup to which the specified LDEV belongs is enabled and theother LDEV in the parity group is being used for the other pool.


The specified LDEV is the LDEV configuring the RAIDconfiguration which cannot be used for the pool volume.


The pool is not in the status where the pool volume can beadded.








The operation cannot be performed because the pool capacityis insufficient for Data Direct Mapping.


The specified LDEV is not installed.00002E20AsyncGet Command Status

The operation cannot be performed because the memorycapacity of the shared memory is insufficient.


The operation cannot be performed because the sharedmemory is not initialized.


Thin Provisioning program product is not installed.90072E21ExecutingCMDRJE

Data Retention program product is not installed.90142E21AsyncGet Command Status

338 Troubleshooting

Table 105 SSB codes returned by raidcom add thp_pool (continued)



Error message

SSB2SSB1

Exceeded the number of pool volume that can be registeredin a pool.


The larger number of drive types than the supportedconfiguration cannot be added to the specified pool.


Pool volume cannot be registered because the drive type ofspecified LDEV is different from the other pool volume type,or the drive type in the pool exceeds three.



The emulation type of specified LDEV cannot be used as apool VOL.


The specified LDEV has the LU path definition.00072E30AsyncGet Command Status


The specified LDEV is used as a system disk.000D2E30AsyncGet Command Status

The specified LDEV is already used as a pool volume.000E2E30AsyncGet Command Status


It cannot be used as a pool volume because the size ofspecified LDEV is less than 8GB.


Creating a pool or adding a pool volume cannot be donebecause CLPR is mixed in the specified pool.


The specified LDEV is used as a V-VOL.005C2E30AsyncGet Command Status

The specified LDEV is a volume of unsupported Smart Tiersor Real Time Smart Tier.


The specified LDEV is used in another program product.005E2E30AsyncGet Command Status

An LDEV, whose emulation type is not available to be mixed,is in the specified LDEVs.


The operation cannot be done for the following reasons:006E2E30AsyncGet Command Status

• The pool volumes to be added to the Smart Tiers pool orReal Time Smart Tier pool include external volumes whosecache modes are invalid.

• The Thin Provisioning pool includes both external volumeswhose cache modes are invalid and internal volumes.

A pool volume cannot be added because the LDEV of theresource group different from the resource group of the poolvolume to which the specified pool belongs is specified.




The specified volume cannot be used as a pool volume.00852E30AsyncGet Command Status





Table 105 SSB codes returned by raidcom add thp_pool (continued)



Error message

SSB2SSB1

The specified pool attribute differs from the pool attribute ofexisted pool.


The LDEV that belongs to the parity group which capacityexpansion is enabled cannot be added to the pool with theTHP V-VOL which is full allocated.


The RAID level of the specified LDEV is different with the RAIDlevel of others.


There is a blocked pool volume.00162E31AsyncGet Command Status

External volumes whose cache modes are different areincluded.


The POOL Name is duplicated with another pool.60012E31ExecutingCMDRJE

The pool cannot include volumes in different RAID levelsbecause the pool cannot include those volumes. Or the pool


cannot include the RAID 1 volumes and the volumes of otherRAID levels together.

The pool cannot include both internal volumes and externalvolumes because the pool is not set to Mixable.


The usage capacity exceeds the license capacity of programproduct.





An internal error occurred.FFFF2EE7AsyncGet Command StatusCall HPE technical support.



Table 106 SSB codes returned by raidcom modify rcu

raidcom modify rcu


Error message

SSB2SSB1

CU# of RCU exceed the effective value.30012E00ExecutingCMDRJE

The value of least path number is invalid.30022E00ExecutingCMDRJE

The value of RIO MIH time is invalid.30032E00ExecutingCMDRJE

The value of Round-trip response time is invalid.30042E00ExecutingCMDRJE

Invalid product ID or path registration ID.30052E00ExecutingCMDRJE

Incident that is created by CU is not in the one of followings.30072E00ExecutingCMDRJE- Incident that is sent to MCU host and RCU.- Incident that is sent to RCU.

340 Troubleshooting

Table 106 SSB codes returned by raidcom modify rcu (continued)

raidcom modify rcu


Error message

SSB2SSB1

Command cannot be executed because the parameter ofspecified RCU is invalid.


Command cannot be executed because all the CU numbersin the RCU is not unified at the path that is specified creationor deletion.





The serial number, the product ID, or the SSID of the targetstorage system is incorrect.


The attribute of the RCU cannot be changed because thespecified RCU is not registered.


The specified CU number is not defined, or an LDEV is notdefined under the CU number.


The operation cannot be done because the number of pathsbecomes less than the least path number.


Command cannot be executed because the RCU identificationcode of a path is invalid.



The value of SSID for the remote storage system is invalid.33002ED6ExecutingCMDRJE

Table 107 SSB codes returned by raidcom delete rcu_path

raidcom delete rcu_path


Error message

SSB2SSB1

The CU# of RCU exceeds the effective value.30012E00ExecutingCMDRJE

The product ID or the path registration ID is invalid.30052E00ExecutingCMDRJE



The specified port # on the side of RCU is invalid.32002E00ExecutingCMDRJE

The CU number is out of effective range.71002E00Executing/Async


The value of specified port is invalid.84002E00Executing/AsyncCMDRJEGet Command Status

Failed to establish a path or the deletion operation. Thefollowing factor can be thought.


• Input parameter is invalid.

• Port status or the MP Blade status is in the state ofabnormal.


Table 107 SSB codes returned by raidcom delete rcu_path (continued)

raidcom delete rcu_path


Error message

SSB2SSB1

• Cable is not connected correctly.

• Port is specified incorrectly.





A logical path cannot be deleted because the specified RCUis not registered.






The port attribute is not Initiator (MCU).840A2E30ExecutingCMDRJE





Command cannot be executed because the serial number isnot unified in the specified path.



00EE2ED6ExecutingCMDRJE

An internal error occurred.30052ED6AsyncGet Command StatusCall HPE technical support.







Table 108 SSB codes returned by raidcom add rcu_path

raidcom add rcu_path


Error message

SSB2SSB1

CU# of RCU exceeds the effective value.30012E00ExecutingCMDRJE




342 Troubleshooting

Table 108 SSB codes returned by raidcom add rcu_path (continued)



Error message

SSB2SSB1



The value of port # on the side of RCU is invalid.32002E00ExecutingCMDRJE

The CU number is out of effective range.71002E00ExecutingCMDRJE/AsyncGet Command Status














A logical path cannot be added because the specified RCU isnot registered.




An RCU path cannot be added because the number of validpaths exceeds the maximum.














The value of SSID on the remote storage system is invalid.33002ED6ExecutingCMDRJE


Table 108 SSB codes returned by raidcom add rcu_path (continued)



Error message

SSB2SSB1







Table 109 SSB codes returned by raidcom delete rcu

raidcom delete rcu


Error message

SSB2SSB1

CU# on the RCU exceeds the effective range.30012E00ExecutingCMDRJE




The value of specified port# on the side of RCU is invalid.32002E00ExecutingCMDRJE

The CU number is out of effective range.71002E00AsyncGet Command Status








The specified RCU cannot be deleted because the RCU is notregistered.




Path cannot be deleted because there is a pair of ContinuousAccess Synchronous/Continuous Access Journal, or a journalvolume is in the relevant CU.








344 Troubleshooting

Table 109 SSB codes returned by raidcom delete rcu (continued)

raidcom delete rcu


Error message

SSB2SSB1

RCU storage system does not exist.00D12EDEExecutingCMDRJE



Table 110 SSB codes returned by raidcom add rcu

raidcom add rcu


Error message

SSB2SSB1

The value of CU# on the RCU exceeds the effective range.30012E00ExecutingCMDRJE






The value of port# on the side of RCU is invalid.32002E00ExecutingCMDRJE

The CU number is out of effective range.71002E00Executing/AsyncCMDRJEGet Command Status
















The specified RCU is already registered to another product ID.30012E22AsyncGet Command Status


Table 110 SSB codes returned by raidcom add rcu (continued)

raidcom add rcu


Error message

SSB2SSB1

The operation cannot be performed due to one of the followingreasons:


• The number of RCUs registered in MCU or RCU is morethan four.

• The number of RCUs registered in the system is more than64 in the case of specifying the cu free.

The specified SSID is already registered to another RCU.33002E22AsyncGet Command Status

The specified RCU is cannot be registered because there isno free RCU.









The operation cannot be performed because the remote storagesystem does not support the path between CUs.














Table 111 SSB codes returned by raidcom delete ldev

raidcom delete ldev


Error message

SSB2SSB1


This command does not support the emulation type of thespecified LDEV.


The command cannot be executed by receiving multipleoperations for the same LDEV.


346 Troubleshooting

Table 111 SSB codes returned by raidcom delete ldev (continued)

raidcom delete ldev


Error message

SSB2SSB1

The specified LDEV is used for a pair of Business Copy/FastSnap/Snapshot/Auto LUN V2 or as a relationship of CompatibleFlashCopy/Compatible FlashCopy SE.


The specified LDEV is used for a Continuous AccessSynchronous pair, a Continuous Access Journal pair or acommand device defined by Business Continuity Manager.


The specified LDEV is used for a Continuous Access Journalpair or a journal.






The specified LDEV is used for an Auto LUN.00052E10AsyncGet Command Status


The specified LDEV is used as a CC/XRC attribute device.00122E10AsyncGet Command Status

The specified LDEV is used as the primary volume for the HApair.


The specified LDEV is used as the secondary volume for theHA pair.


The specified LDEV cannot be operated because thededuplication function is set.


The specified LDEV cannot be operated because deduplicateddata exists.


The specified LDEV cannot be operated because it is in thestatus where the capacity saving setting cannot be disabled.


The operation cannot be performed because a page is allocatedto the specified LDEV.


The pool is blocked.600B2E10AsyncGet Command Status

An LDEV that is in the state of formatting is included in theparity group of the target LDEV.


An LDEV that is in the state of executing quick format isincluded in the parity group of the target LDEV.






The parity group or the external volume group that the specifiedLDEV is belongs to is used in another operation.


The external volume group with the Data Direct Mappingattribute which is allocated to the specified LDEV is not in thestate of disconnected.


The operation cannot be performed because pools are blocked.60042E11AsyncGet Command Status



raidcom delete ldev


Error message

SSB2SSB1

The operation cannot be performed because the pool linkedwith the specified LDEV is in the unusable status.










LDEV is not installed.00002E20Executing/AsyncCMDRJEGet Command Status

An LU path has been defined.00072E30ExecutingCMDRJE





The specified LDEV is used in the FICON® Data Migration.00062E30AsyncGet Command Status


The specified volume cannot be deleted because it is a LUSEvolume.




This is a volume that the Data Retention is set.00182E30AsyncGet Command Status


The specified LDEV cannot be deleted because of online fromthe mainframe host.




This is a volume that the Volume Retention is set.00532E30AsyncGet Command Status

The specified LDEV is used as a Compatible FlashCopy or aCompatible FlashCopy SE relationship.


The specified LDEV is used for an Auto LUN.00552E30AsyncGet Command Status

The specified LDEV is used for an Auto LUN00562E30AsyncGet Command Status




348 Troubleshooting


raidcom delete ldev


Error message

SSB2SSB1



The specified LDEV is used as an ALU.00962E30AsyncGet Command Status

The specified LDEV is used as an SLU.00972E30AsyncGet Command Status



The specified volume is used as a Continuous AccessSynchronous.


The specified volume is used as a Continuous AccessSynchronous.






The specified volume is used as a Business Copy.41072E30AsyncGet Command Status



The target LDEV is a quorum disk and cannot be deleted.00012E31AsyncGet Command Status




An internal error occurred. Call HPE technical support.FEEC2EE8Executing/AsyncCMDRJEGet Command Status




Table 112 SSB codes returned by raidcom delete hba_wwn

raidcom delete hba_wwn


Error message

SSB2SSB1


The host group ID exceeds the maximum value.4087B957ExecutingCMDRJE


The attribute of specified port is Initiator or External.408AB957ExecutingCMDRJE

The specified command is not supported for the iSCSI port.408FB957ExecutingCMDRJE


Table 112 SSB codes returned by raidcom delete hba_wwn (continued)

raidcom delete hba_wwn


Error message

SSB2SSB1

The operation cannot be done because it is locked in anothersession.

B9DAB957ExecutingCMDRJE





Table 113 SSB codes returned by raidcom add hba_wwn

raidcom add hba_wwn


Error message

SSB2SSB1


The value of hba_wwn is invalid.4081B957ExecutingCMDRJE


The host group is not installed.4089B957ExecutingCMDRJE


The specified command is not supported for the iSCSI port.408FB957ExecutingCMDRJE

The number of WWN reached the maximum.4184B957ExecutingCMDRJE

HBA WWN is already registered.4188B957ExecutingCMDRJE

The number of WWNs exceeds the maximum that can be setin PFC.

B9D1B957ExecutingCMDRJE

Performance Control program product is not installed.B9D4B957ExecutingCMDRJE

The number of WWNs exceeds the maximum that can be setto the port in PFC.


The WWN which belongs to the specified host group isregistered in another PFC group.








350 Troubleshooting

Table 114 SSB codes returned by raidcom set hba_wwn

raidcom set hba_wwn


Error message

SSB2SSB1





The specified WWN does not exist.4385B957ExecutingCMDRJE

The specified WWN nickname is already used in the sameport.

438BB957ExecutingCMDRJE





Table 115 SSB codes returned by raidcom reset hba_wwn

raidcom reset hba_wwn


Error message

SSB2SSB1


The value of Host group ID exceeds the maximum.4087B957ExecutingCMDRJE


The attribute of the specified port is Initiator or External.408AB957ExecutingCMDRJE

The specified WWN does not exist.4385B957ExecutingCMDRJE





Table 116 SSB codes returned by raidcom add copy_grp

raidcom add copy_grp


Error message

SSB2SSB1

The number of MU# exceeds the maximum.000B2E00ExecutingCMDRJE

Invalid device number.21002E00ExecutingCMDRJE

The specified journal ID exceeds the range.50002E00ExecutingCMDRJE

A device group is not installed.21002E20ExecutingCMDRJE

There is a copy group.20002E22ExecutingCMDRJE

The number of copy groups in the system reached themaximum.



Table 116 SSB codes returned by raidcom add copy_grp (continued)

raidcom add copy_grp


Error message

SSB2SSB1

The specified device group is already defined in the other copygroup.


There is an LDEV in the device group that has an undefineddevice name.


The same device names of LDEV are in the device group.00132E31ExecutingCMDRJE

The same LDEVs are in the copy group.00142E31ExecutingCMDRJE

Unavailable character is included in the name of copy group.--ExecutingInvalid Character

Table 117 SSB codes returned by raidcom delete copy_grp

raidcom delete copy_grp


Error message

SSB2SSB1

The copy group is not installed.20002E20ExecutingCMDRJE

Unavailable character is included in the name of copy group.--ExecutingInvalid Character

Table 118 SSB codes returned by raidcom modify port -port_speed

raidcom modify port -port_speed


Error message

SSB2SSB1










Invalid host speed is set for 4Gbps fibre adapter. The availablehost speeds are AUTO, 1G, 2G, and 4G only.


Invalid host speed is set for the specified fibre adapter.113EB955ExecutingCMDRJE






11AEB955ExecutingCMDRJE

352 Troubleshooting

Table 118 SSB codes returned by raidcom modify port -port_speed (continued)

raidcom modify port -port_speed


Error message

SSB2SSB1

The combination of the specified host speed and the topologyFC-AL set for the fibre channel adapter is not supported. See

12AFB955ExecutingCMDRJE

the Provisioning Guide of your system for supportedcombinations of data transfer speed and type of connection.





Table 119 SSB codes returned by raidcom modify port -port_attribute

raidcom modify port -port_attribute


Error message

SSB2SSB1

The target channel adapter or the channel board does notsupport the specified port attribute.


The operation cannot be done because another application,for example Remote Web Console and SVP is used.


The specified port is blocked.84002E10ExecutingCMDRJE

There is a pair for Continuous Access Synchronous/ContinuousAccess Journal that is used the specified port.


There is a pair for Continuous Access Synchronous/ContinuousAccess Journal that is used the specified port.


The storage system is in the state of start-up. Wait for a while,then retry the operation.


The port attribute cannot be changed because it is used forthe iSCSI path of the remote replication.


iSNS is set for the specified port.84022E13ExecutingCMDRJE

The specified port is not installed.84002E20ExecutingCMDRJE

There is a path for Continuous Access Synchronous/ContinuousAccess Journal in the specified port.


There is an external VOL path in the specified port.84062E30ExecutingCMDRJE





An LU path has been defined.84092E30ExecutingCMDRJE

An internal error occurred.84FC2ED0ExecutingCMDRJECall HPE technical support.


Table 119 SSB codes returned by raidcom modify port -port_attribute (continued)

raidcom modify port -port_attribute


Error message

SSB2SSB1





Table 120 SSB codes returned by raidcom modify port -delayed_ack_mode

raidcom modify port -delayed_ack_mode


Error message

SSB2SSB1



Table 121 SSB codes returned by raidcom modify port -ipv4_address

raidcom modify port -ipv4_address


Error message

SSB2SSB1



The network address, loop-back address, broadcast addressor the IP address beginning with 255 cannot be used as theIP address for IPv4.

10B3B955ExecutingCMDRJE

Table 122 SSB codes returned by raidcom modify port -ipv4_subnetmask

raidcom modify port -ipv4_subnetmask


Error message

SSB2SSB1



The subnet mask cannot be set because the specified valueis invalid.

10DBB955ExecutingCMDRJE

Table 123 SSB codes returned by raidcom modify port -ipv4_gateway_address

raidcom modify port -ipv4_gateway_address


Error message

SSB2SSB1



354 Troubleshooting

Table 124 SSB codes returned by raidcom modify port -ipv6_gateway_address

raidcom modify port -ipv6_gateway_address


Error message

SSB2SSB1



The multicast address or the loop-back address cannot be setas the default gateway for IPv6.


The same IPv6 address cannot be set to the same portredundantly.


Table 125 SSB codes returned by raidcom modify port -ipv6_global_address

raidcom modify port -ipv6_global_address


Error message

SSB2SSB1



The multicast address or the loop-back address cannot be setas global address 1 for IPv6.




If global address 1 for IPv6 is not set, you cannot set globaladdress 2 for IPv6 manually.

10FDB955ExecutingCMDRJE

The multicast address or the loop-back address cannot be setas global address 2 for IPv6.

10FEB955ExecutingCMDRJE

Table 126 SSB codes returned by raidcom modify port -ipv6_local_address

raidcom modify port -ipv6_local_address


Error message

SSB2SSB1



The invalid value is specified for the link local address of IPv6.10B6B955ExecutingCMDRJE



Table 127 SSB codes returned by raidcom modify port -ipv6_mode

raidcom modify port -ipv6_mode


Error message

SSB2SSB1



To disable IPv6, delete the remote path for avoiding the failureof remote copy.



Table 128 SSB codes returned by raidcom modify port -isns_mode

raidcom modify port -isns_mode


Error message

SSB2SSB1



The attribute of the specified port is Initiator or External.10FCB955ExecutingCMDRJE

Table 129 SSB codes returned by raidcom modify port -isns_server_address

raidcom modify port -isns_server_address


Error message

SSB2SSB1



The specified IP address of the iSNS server is incorrect by thefollowing reasons:


• The loop-back address, broadcast address or the IP addressbeginning with 255 has been set as the IPv4 address.

• The multicast address or the loop-back address has beenset as the IPv6 address, or the address has not beenspecified yet.

Table 130 SSB codes returned by raidcom modify port -keep_alive_timer

raidcom modify port -keep_alive_timer


Error message

SSB2SSB1



The invalid value is specified for the Keep Alive timer.10BEB955ExecutingCMDRJE

The attribute of the specified port is Initiator or External.10FBB955ExecutingCMDRJE

Table 131 SSB codes returned by raidcom modify port -mtu

raidcom modify port -mtu


Error message

SSB2SSB1



The invalid value is specified for the Ethernet MTU size.10B0B955ExecutingCMDRJE

356 Troubleshooting

Table 132 SSB codes returned by raidcom modify port -tcp_port

raidcom modify port -tcp_port


Error message

SSB2SSB1



Table 133 SSB codes returned by raidcom modify port -add_vlan_id

raidcom modify port -add_vlan_id


Error message

SSB2SSB1



The invalid value is specified for the VLAN ID.10B2B955ExecutingCMDRJE

The number of VLANs exceeds the maximum.10CBB955ExecutingCMDRJE

Table 134 SSB codes returned by raidcom modify port -delete_vlan_id

raidcom modify port -delete_vlan_id


Error message

SSB2SSB1



The invalid value is specified for the VLAN ID.10B2B955ExecutingCMDRJE

Table 135 SSB codes returned by raidcom modify port -vlan_tagging_mode

raidcom modify port -vlan_tagging_mode


Error message

SSB2SSB1



The VLAN tagging mode cannot be set because the VLAN IDhas not been entered yet.

10BFB955ExecutingCMDRJE

Table 136 SSB codes returned by raidcom modify port -window_size

raidcom modify port -window_size


Error message

SSB2SSB1




Table 137 SSB codes returned by raidcom modify port -t10pi

raidcom modify port -t10pi


Error message

SSB2SSB1

The value of specified port is invalid.84002E00ExecutingCMDRJEAsyncGet Command Status

The channel board of the object is not supported.84042E00ExecutingCMDRJEAsyncGet Command Status

Unavailable to operate because another application is inprogress on Remote Web Console, Remote Web Console, orSVP.


The specified port is blocked.84002E10ExecutingCMDRJEAsyncGet Command Status



The specified port is not installed.84002E20ExecutingCMDRJEAsyncGet Command Status

LU path of the specified port or LU path of the port in the samegroup is defined, the T10 PI attribute of the port cannot bechanged.

840F2E30ExecutingAsync

Get Command Status



An internal error occurred.FEEC2ED0ExecutingCMDRJEAsyncGet Command Status

Table 138 SSB codes returned by raidcom delete host_grp

raidcom delete host_grp


Error message

SSB2SSB1

The host group cannot be deleted because the host modeoption 61 or 72 is set.





The attribute of the specified port is Initiator or External.30FDB956ExecutingCMDRJE

Deletion cannot be executed because the last path of BusinessCopy is included in the host group.


Deletion cannot be executed because the last path of FastSnap or Snapshot is included in the host group.


Deletion cannot be executed because the LU which is the targetof the operation is in the reserved status.


The command device being used at the local RAID Managerexists under the host group.


358 Troubleshooting

Table 138 SSB codes returned by raidcom delete host_grp (continued)

raidcom delete host_grp


Error message

SSB2SSB1







Table 139 SSB codes returned by raidcom add host_grp

raidcom add host_grp


Error message

SSB2SSB1





The same host group name is already installed in the specifiedport.


The default host group name cannot be registered for the hostgroup ID is other than 0.


The character or the number of characters of the iSCSI targetname is invalid.

31D0B956ExecutingCMDRJE

The character or the number of characters of the iSCSI targetalias is invalid.


The specified iSCSI target alias is already assigned to thesame port.


The specified iSCSI target alias cannot be registered becausethe iSCSI target alias is reserved for the iSCSI target ID 00.


The specified iSCSI target name is already used for the sameport.


The specified iSCSI target name cannot be registered becausethe iSCSI target name is reserved for the iSCSI target ID 00.

31DAB956ExecutingCMDRJE



Table 140 SSB codes returned by raidcom modify host_grp

raidcom modify host_grp


Error message

SSB2SSB1




Table 140 SSB codes returned by raidcom modify host_grp (continued)

raidcom modify host_grp


Error message

SSB2SSB1

You cannot cancel the host mode option because the specifiedhost group is associated with the LDEV in another virtualstorage machine by the path definition.


The command device being used at the local RAID Managerexists under the host group.


Changing of the host mode/ host mode option cannot beexecuted for the port of Initiator or External.


The invalid host mode is specified.0354B958ExecutingCMDRJE

You cannot set the host mode option 51 because the numberof ports that are set the host mode option 51 exceeds themaximum.


You cannot set the host mode option 51 because the option isset to the other host group in the same port.


The cancellation of the host mode option 61 or 72 wassuppressed.


The host group ID exceeds the maximum.0956B958ExecutingCMDRJE



When using 8FC16 or 16FE10 channel package, you cannotconfigure the host mode option 51 (Round Trip Set Up Option)


for the host group because the host mode option 51 is notsupported.







Table 141 SSB codes returned by raidcom disconnect path



Error message

SSB2SSB1

The path group is out of the enabled range.45002E00ExecutingCMDRJE

The value of specified port is invalid.84002E00ExecutingCMDRJE

The specified external path has already disconnected the path,or is in the process of checking path.


The target LDEV is blocked.001B2E11AsyncGet Command Status



360 Troubleshooting

Table 141 SSB codes returned by raidcom disconnect path (continued)



Error message

SSB2SSB1

This command cannot be operated due to one of the followingreasons:


• All the paths to the external volumes are blocked.

• There will be no normal paths.



There is no specified external volume.41002E20Executing/AsyncGet Command StatusCMDRJE

There is no connection path to an external volume.43002E20Executing/AsyncGet Command StatusCMDRJE


There is no path group.45002E20ExecutingCMDRJE

external_wwn is not defined.45002E20ExecutingCMDRJE

Online from the mainframe host.001E2E30AsyncGet Command Status

The attribute of a port is not External(ELUN).84002E30ExecutingCMDRJE





An internal error occurred by the operation of a path for anexternal path.

09052EDAAsyncGet Command Status






Table 142 SSB codes returned by raidcom delete path

raidcom delete path


Error message

SSB2SSB1

The path group is not in a effective range.45002E00ExecutingCMDRJE

The value of the specified port is incorrect.84002E00ExecutingCMDRJE

The path operations cannot be performed for the followingreasons:


• The target of the specified path group is XP12000 DiskArray/XP10000 Disk Array.

• The specified path group contains the external volume thatis set the reserve attribute from the host.


Table 142 SSB codes returned by raidcom delete path (continued)

raidcom delete path


Error message

SSB2SSB1

The operation cannot continue because the microcode is beingreplaced.





There is no external connection path.43002E20ExecutingCMDRJE


There is no path group.45002E20Executing/AsyncCMDRJEGet Command Status

Paths cannot be deleted because there are no normal paths.43002E23Executing/AsyncCMDRJEGet Command Status






An internal error occurred.FEEC2EDAAsyncGet Command StatusCall HPE technical support.

An internal error occurred.FFFF2EDAAsyncGet Command StatusCall HPE technical support.





Table 143 SSB codes returned by raidcom add path

raidcom add path


Error message

SSB2SSB1

The path group is not in the enabled range.45002E00ExecutingCMDRJE

The value of specified port is incorrect.84002E00ExecutingCMDRJE

The path operations cannot be performed for the followingreasons:


• The target of the specified path group is XP12000 DiskArray/XP10000 Disk Array.

• The specified path group contains the external volume thatis set the reserve attribute from the host.

The WWN on the side of specified external storage is notconnected to an External port.


362 Troubleshooting

Table 143 SSB codes returned by raidcom add path (continued)

raidcom add path


Error message

SSB2SSB1

This message may be output if the migration source storagesystem is XP24000/XP20000 Disk Array and the host modeoption 2 is not set to the port that connects to the migrationtarget storage system.

An external volume that is the mainframe emulation type isincluded in the specified external path group.


The operation cannot continue because the microcode is beingreplaced.





Invalid WWN.44002E20AsyncGet Command Status

There is no path group.45002E20ExecutingCMDRJE/AsyncGet Command Status

The same path has been defined already.43002E22Executing/AsyncCMDRJEGet Command Status

The operation cannot be done because the number of path inthe path group exceeds 8.


The attribute of a port is not External (ELUN).84002E30ExecutingCMDRJE



The specified external storage LU is the device of notsupported.


The specified external storage system is not supported.40012E31AsyncGet Command Status



An internal error occurred.FEEC2EDAAsyncGet Command StatusCall HPE technical support.

An internal error occurred.FFFF2EDAAsyncGet Command StatusCall HPE technical support.






Table 144 SSB codes returned by raidcom -logout

raidcom -logout


Error message

SSB2SSB1

Failed to release the resource lock.22002E01ExecutingCMDRJE

Table 145 SSB codes returned by raidcom monitor pool

raidcom monitor pool


Error message

SSB2SSB1


Monitor cannot be started because the performance monitoris in the collecting status.


Monitor cannot be stopped because the performance monitoris stopped.


Monitor cannot start because the performance monitor is inuse. Retry the operation after completing or stopping thereallocation of Tier.


There is not enough time after collecting performance monitor.60072E10ExecutingCMDRJE

The pool is not in the state of specifying the performancemonitor to start or stop.


The pool ID is not installed.60002E20ExecutingCMDRJE

A shared memory for Thin Provisioning is not installed.81012E21ExecutingCMDRJE

A shared memory for Smart Tiers or Real Time Smart Tier isnot installed.


The program product of Smart Tiers or Real Time Smart Tieris not installed.


Start or stop of performance monitor by hand cannot be donebecause it is a pool for Thin Provisioning or it is automaticexecution mode.


The specified pool is the one for Fast Snap or Snapshot.60032E30ExecutingCMDRJE


Table 146 SSB codes returned by raidcom reallocate pool

raidcom reallocate pool


Error message

SSB2SSB1


There is not enough time after collecting performance monitor.60072E10ExecutingCMDRJE

Tier Reallocation cannot be started because the state ofperformance monitor information is not enabled. Start theperformance monitor again.


Reallocation cannot be started because it is reallocating.60092E10ExecutingCMDRJE

364 Troubleshooting

Table 146 SSB codes returned by raidcom reallocate pool (continued)

raidcom reallocate pool


Error message

SSB2SSB1

Reallocation cannot be stopped because it is not reallocating.600A2E10ExecutingCMDRJE

The operation cannot be done because it is being discardedpages.


The operation cannot be done because the Tier is beingdeterred reallocation.


The pool is not in the status of specifying the reallocation tostart or stop.


The pool ID is not installed.60002E20ExecutingCMDRJE

A shared memory for Thin Provisioning is not installed.81012E21ExecutingCMDRJE

A shared memory for Smart Tiers or Real Time Smart Tier isnot installed.


The program product of Smart Tiers or Real Time Smart Tieris not installed.


Start or stop of performance monitor by hand cannot be donebecause it is a pool for Thin Provisioning or it is automaticexecution mode.


The specified pool is the one for Fast Snap or Snapshot.60032E30ExecutingCMDRJE

Reallocation cannot be done because there is only one Tier inthe pool group.



Table 147 SSB codes returned by raidcom extend ldev

raidcom extend ldev


Error message

SSB2SSB1

See the troubleshooting topics in the Provisioning Guide forthe storage system.

--ExecutingCMDRJE

Table 148 SSB codes returned by raidcom delete resource

raidcom delete resource


Error message

SSB2SSB1

The specified resource group cannot be operated.22012E00ExecutingCMDRJE

Resource groups cannot be deleted because the resourcegroups are locked.


The LDEV and the host group cannot be set to the differentvirtual storage machine.



A resource group cannot be deleted because the specifiedresource group is undefined.



Table 148 SSB codes returned by raidcom delete resource (continued)

raidcom delete resource


Error message

SSB2SSB1


The information for the virtual storage machine is set in thespecified resource.


A resource group cannot be deleted because a resourcebelongs to the specified resource group.


A resource cannot be deleted from the resource group becausethe specified LDEV number is not the top LDEV number in theLUSE volume.


The operation to resource group 0 (meta_resource) cannot beperformed.


An internal error occurred.FEEC2ECAExecutingCMDRJECall HPE technical support.



The command was rejected because the selected resourcegroup belongs to NAS_Platform_System_RSG.


Table 149 SSB codes returned by raidcom add resource

raidcom add resource


Error message

SSB2SSB1

The specified resource group name is against the naming rules.22002E00ExecutingCMDRJE

The specified resource group cannot be operated.22012E00ExecutingCMDRJE

The resource ID and the sub-resource ID are out of the effectiverange.


The machine type is invalid.80002E00ExecutingCMDRJE

The serial number is invalid.80012E00ExecutingCMDRJE


The LDEV and the host group cannot be set to the differentvirtual storage machine.



You cannot execute this command because of either reasonbelow.


• A resource cannot be added to the resource group becausethe specified resource group is undefined.

• A resource group name cannot be changed because thespecified resource group is undefined.



366 Troubleshooting

Table 149 SSB codes returned by raidcom add resource (continued)

raidcom add resource


Error message

SSB2SSB1

The program products of Resource Partition are not installed.900D2E21ExecutingCMDRJE

The information for the virtual storage machine is set in thespecified resource.


A virtual storage machine cannot be created because the virtualstorage machine with the specified serial number already exists.


You cannot execute this command because of either reasonbelow.


• A resource group cannot be created because the specifiedresource group name is duplicated.

• A resource group name cannot be changed because thespecified resource group name is duplicated.

A resource cannot be added to a resource group because thespecified resource belongs to the resource group.


A resource cannot be added to the resource group becausethe specified LDEV number is not the top LDEV number in theLUSE volume.


Any more resource groups cannot be created because theregistered number of resource groups has reached themaximum.


A virtual storage machine cannot be created because thenumber of registered virtual storage machines has reachedthe maximum.


The operation to resource group 0 (meta_resource) cannot beperformed.


The attribute of the specified port is Initiator or External.84022E30ExecutingCMDRJE






The command was rejected because the selected resourcegroup belongs to NAS_Platform_System_RSG.


Table 150 SSB codes returned by raidcom get resource

raidcom get resource


Error message

SSB2SSB1

An internal error occurred.FEEC2EF0ExecutingCMDRJECall HPE technical support.


Table 151 SSB codes returned by raidcom map resource

raidcom map resource


Error message

SSB2SSB1

The specified LDEV number or the LDEV number for the virtualvolume is out of the range.


SSID is not with in the valid range.00032E00ExecutingCMDRJE

The specified emulation type of the LDEV is not supported inthis command.


The specified attribute of the virtual LDEV is not supported.002B2E00ExecutingCMDRJE

The specified attribute of the virtual LDEV is invalid.002C2E00ExecutingCMDRJE

You cannot execute the command because a parameterrequired for the virtualization was not specified.


The specified emulation type is invalid.93012E00ExecutingCMDRJE

The specified LDEV cannot be operated because it belongs tothe default virtual storage machine.


The specified volume cannot be operated because the LDEVnumber of the specified volume does not match the LDEVnumber of the virtual volume.


You cannot execute the command because the processing bythe other software (Remote Web Console or SVP, and so on)is in progress.


The information of the virtual storage machine is already setin the specified resource.


The specified virtual LDEV number is already exist in the virtualstorage machine to which the specified LDEV belongs.


You cannot operate the LDEV that has the LU path definition.93082E21ExecutingCMDRJE

The specified LDEV is already defined.00012E22ExecutingCMDRJE

The specified volume cannot be set because it is a LUSEvolume.


The specified LDEV cannot be operated because it has anattribute.


The specified LDEV cannot be operated because the ldev hasa reserve attribute for HA.


The specified LDEV is used for an HA pair.008A2E30ExecutingCMDRJE

The specified LDEV cannot be set the information of the virtualvolume because it is not virtualized.





368 Troubleshooting

Table 152 SSB codes returned by raidcom unmap resource

raidcom unmap resource


Error message

SSB2SSB1

The specified LDEV number or the LDEV number for the virtualvolume is out of the range.


The specified LDEV for the virtual storage machine is notdefined in the specified LDEV.


The specified LDEV is used by the Continuous AccessSynchronous pair or the Continuous Access Journal pair.


You cannot execute the command because the processing bythe other software (Remote Web Console or SVP, and so on)is in progress.


The Resource Partition is not installed.90122E21ExecutingCMDRJE

The information of the virtual storage machine is not set in thespecified resource.


You cannot operate the LDEV that has the LU path definition.93082E21ExecutingCMDRJE



The specified LDEV is used for an HA pair.008A2E30ExecutingCMDRJE

The specified LDEV cannot be operated because it is theexternal volume for the online data migration.


The specified volume cannot be operated because it is themainframe volume.


The specified LDEV is used as an ALU.00962E30ExecutingCMDRJE

The specified LDEV is used as an SLU.00972E30ExecutingCMDRJE




Table 153 SSB codes returned by raidcom modify resource

raidcom modify resource


Error message

SSB2SSB1




Table 154 SSB codes that are returned by raidcom set resource

raidcom set resource


Error message

SSB2SSB1



Table 155 SSB codes returned by raidcom reset resource

raidcom reset resource


Error message

SSB2SSB1



Table 156 SSB codes returned by raidcom unlock resource

raidcom unlock resource


Error message

SSB2SSB1

Cannot unlock because it is locked in another session.22002E10ExecutingCMDRJE

Table 157 SSB codes returned by raidcom modify clpr

raidcom modify clpr


Error message

SSB2SSB1


The specified LDEV is not subject to processing.002A2E00ExecutingCMDRJE

The parity group number or the external volume group numberis not in the effective range.


The specified group type is not correct.01022E00ExecutingCMDRJE

The combined parity group cannot be set across multipleCLPRs.


The item cannot be migrated to another CLPR because ofeither reason below.


• The specified parity group or external volume group has anLUSE volume.

• The specified volume is an LUSE volume.

The specified CLPR ID is invalid.70002E00ExecutingCMDRJE

Abnormal cache status.810A2E11ExecutingCMDRJE

The CLPR cannot be migrated because the specified paritygroup or the external volume group includes the pool volumethat is used in the pool for Fast Snap or Snapshot.




370 Troubleshooting

Table 157 SSB codes returned by raidcom modify clpr (continued)

raidcom modify clpr


Error message

SSB2SSB1


The specified CLPR is not installed.70012E20ExecutingCMDRJE

CLPR cannot be transferred by either one of the following tworeasons.


• Cache Residency is set for the specified volume.

• The specified parity group includes the volumes for whichCache Residency are set.


The specified parity group includes HDEV with the journalattribute.









An internal error occurred.FEEC2EF6ExecutingCMDRJECall HPE technical support.

Table 158 SSB codes returned by raidcom add pfc_group

raidcom add pfc_group


Error message

SSB2SSB1

The command cannot be executed due to one of the followingreasons:

B9D0B9D4ExecutingCMDRJE

• Performance Control is being used by Remote WebConsole.

• Performance Control information for the port WWN alreadyexists in the system.

Performance Control program product is not installed.B9D4B9D4ExecutingCMDRJE

The number of Performance Control groups exceeds themaximum.


The WWN which belongs to the specified host group isregistered in another PFC group.


There is no WWN which belongs to the specified host group.B9D9B9D4ExecutingCMDRJE


B9DAB9D4ExecutingCMDRJE


Table 158 SSB codes returned by raidcom add pfc_group (continued)

raidcom add pfc_group


Error message

SSB2SSB1

PFC cannot be operated without specifying the host groupbecause the specified WWN, PFC group to which the PFC

B9DCB9D4ExecutingCMDRJE

name belongs, or the specified PFC group is associated withthe host group.

The specified PFC group already exists. The specified PFCgroup cannot be registered because it is not associated withthe host group.

B9DDB9D4ExecutingCMDRJE

Table 159 SSB codes returned by raidcom delete pfc_group

raidcom delete pfc_group


Error message

SSB2SSB1







The specified WWN or nickname does not exist.B9D2B9D4ExecutingCMDRJE



D9DAB9D4ExecutingCMDRJE


D9DCB9D4ExecutingCMDRJE


Table 160 SSB codes returned by raidcom modify pfc_group

raidcom modify pfc_group


Error message

SSB2SSB1







The specified WWN or upper limit is invalid.B9D3B9D4ExecutingCMDRJE


372 Troubleshooting

Table 160 SSB codes returned by raidcom modify pfc_group (continued)

raidcom modify pfc_group


Error message

SSB2SSB1


B9DAB9D4ExecutingCMDRJE


B9DCB9D4ExecutingCMDRJE


Table 161 SSB codes returned by raidcom add pfc_wwn

raidcom add pfc_wwn


Error message

SSB2SSB1





The specified WWN does not exist.B9D2B9D4ExecutingCMDRJE


The specified PFC name has already existed.B9D7B9D4ExecutingCMDRJE


B9DAD9D4ExecutingCMDRJE


B9DCD9D4ExecutingCMDRJE


Table 162 SSB codes returned by raidcom delete pfc_wwn

raidcom delete pfc_wwn


Error message

SSB2SSB1







The configuration WWN or nickname does not exist.B9D2B9D4ExecutingCMDRJE



Table 162 SSB codes returned by raidcom delete pfc_wwn (continued)

raidcom delete pfc_wwn


Error message

SSB2SSB1






Table 163 SSB codes returned by raidcom modify pfc_wwn

raidcom modify pfc_wwn


Error message

SSB2SSB1







The number of WWNs exceeds the maximum that can be setin the system.


The specified WWN or upper limit is invalid.B9D3B9D4ExecutingCMDRJE


The number of WWNs exceeds the maximum that can be setto the port.







Table 164 SSB codes returned by raidcom modify pfc_ldev

raidcom modify pfc_ldev


Error message

SSB2SSB1

The specified iSCSI name is incorrect.9B012E00ExecutingCMDRJE



The specified operation cannot be performed because of noiSCSI package.


374 Troubleshooting

Table 164 SSB codes returned by raidcom modify pfc_ldev (continued)

raidcom modify pfc_ldev


Error message

SSB2SSB1

The iSCSI name cannot be registered because the number ofiSCSI names that can be registered in the system exceededthe maximum number.




The operation cannot be done because it is locked in anothersession. Perform the operation again.


The Performance Control information for the port WWN alreadyexists in the system.


The LDEV cannot be registered because the number of LDEVsthat can be registered in the system exceeded the maximumnumber.


The WWN cannot be registered because the number of WWNsthat can be registered in the system exceeded the maximumnumber.


The WWN cannot be registered because the number of WWNsthat can be registered in the LDEV exceeded the maximumnumber.


The specified LDEV is not defined.B9D5B9D3ExecutingCMDRJE

Performance Control is being used by Remote Web Console.B9D7B9D3ExecutingCMDRJE

The iSCSI name cannot be registered because an invalid WWNis registered. Invalid WWNs are WWNs which are not in the


WWN format defined by IEEE. See “Cautions about usingPerformance Control” (page 165) for details.



The specified WWN or upper limit is incorrect.B9D7B9D7ExecutingCMDRJE

The specified LDEV does not have the WWN.B9D8B9D8ExecutingCMDRJE

The Performance Control program product is not installed.B9D9B9D9ExecutingCMDRJE

Table 165 SSB codes returned by raidcom delete pfc_ldev

raidcom delete pfc_ldev


Error message

SSB2SSB1









Table 165 SSB codes returned by raidcom delete pfc_ldev (continued)

raidcom delete pfc_ldev


Error message

SSB2SSB1



The specified WWN is incorrect.B9D7B9D7ExecutingCMDRJE

The specified LDEV does not have the WWN.B9D8B9D8ExecutingCMDRJE

Table 166 SSB codes returned by raidcom monitor pfc_ldev

raidcom monitor pfc_ldev


Error message

SSB2SSB1









Table 167 SSB codes returned by raidcom get pfc_ldev

raidcom get pfc_ldev


Error message

SSB2SSB1









Table 168 SSB codes returned by raidcom modify ldev -data_saving

raidcom modify ldev -data_saving


Error message

SSB2SSB1

The LDEV number is out of the valid range.00002E00ExecutingCMDRJE

The operation cannot be performed because there are notenough cache management devices.


376 Troubleshooting

Table 168 SSB codes returned by raidcom modify ldev -data_saving (continued)



Error message

SSB2SSB1

The operation cannot be performed because the specifiedLDEV is a journal volume.


The specified LDEV cannot be operated because thededuplication function is enabled.


The specified LDEV cannot be operated because deduplicateddata exists.


The specified LDEV cannot be operated because it is in thestatus where the capacity saving setting cannot be disabled.


The specified LDEV is not in the status where the capacitysaving setting can be enabled.


The specified LDEV is not in the status where the capacitysaving setting can be changed.


The operation cannot be performed because the specifiedvolume is being used by Auto LUN.


The operation cannot be performed because the specifiedvolume is being used by Quick Restore of Business Copy.


The operation cannot be performed because the specifiedvolume is being used by Auto LUN.





The operation cannot be performed because the pool linkedwith the specified LDEV is in unusable status.


The command cannot be accepted. Wait a while, and issuethe same command.


The specified LDEV is not installed.00002E20Executing/AsyncCMDRJEGet Command Status

The operation cannot be performed because the capacity ofshared memory is insufficient.




The operation cannot be performed because the specifiedvolume is not a THP V-VOL.


The specified LDEV is set that the Data Direct Mapping attributeis enabled.


The operation cannot be performed because the pagereservation is set for the specified LDEV.




The operation cannot be performed because the pool linkedwith the specified LDEV is for a Smart Tiers pool.



Table 168 SSB codes returned by raidcom modify ldev -data_saving (continued)



Error message

SSB2SSB1


80002E3FAsyncGet Command Status

The specified parameter is incorrect.9E012EBEExecutingCMDRJE

An internal error occurred. Contact HPE technical support.FEEC2EE8Executing/AsyncCMDRJEGet Command Status

Table 169 SSB codes returned by raidcom modify quorum

raidcom modify quorum


Error message

SSB2SSB1

The specified quorum disk ID is out of the valid range.A0012E00ExecutingCMDRJE

The specified value for Read Response Guaranteed TimeWhen Quorum Disk Blocked is not in the valid range.

A0022E00ExecutingCMDRJE

The specified quorum disk is not defined.A0012E20ExecutingCMDRJE




Table 170 SSB codes returned by raidcom add hba_iscsi

raidcom add hba_iscsi


Error message

SSB2SSB1


The specified command is not supported for the FC port.408FB957ExecutingCMDRJE


The invalid character or the invalid number of characters isspecified for the initiator iSCSI name.

44E0B957ExecutingCMDRJE

The specified iSCSI target is not registered.44E4B957ExecutingCMDRJE

The iSCSI name cannot be added because the number ofiSCSI names that can be used for this port has already reachedthe maximum value.






378 Troubleshooting

Table 171 SSB codes returned by raidcom delete hba_iscsi

raidcom delete hba_iscsi


Error message

SSB2SSB1




The invalid character or the invalid number of characters isspecified for the initiator iSCSI name.







Table 172 SSB codes returned by raidcom set hba_iscsi

raidcom set hba_iscsi


Error message

SSB2SSB1




The character or the number of characters that cannot bespecified for the initiator iSCSI name is specified.


The character or the number of characters that cannot bespecified for the initiator iSCSI nickname is specified.


The specified iSCSI name is not registered.45E3B957ExecutingCMDRJE





Table 173 SSB codes returned by raidcom reset hba_iscsi

raidcom reset hba_iscsi


Error message

SSB2SSB1






Table 174 SSB codes returned by raidcom add chap_user

raidcom add chap_user


Error message

SSB2SSB1





The character used for the user ID, or the number of charactersis invalid.


The specified CHAP user name is already used for the sameport.

46EBB957ExecutingCMDRJE

The CHAP user ID cannot be added because the number ofCHAP user IDs that can be set for this port has already reachedthe maximum value.

46EFB957ExecutingCMDRJE





Table 175 SSB codes returned by raidcom delete chap_user

raidcom delete chap_user


Error message

SSB2SSB1







The specified CHAP user name is not registered.46ECB957ExecutingCMDRJE





Table 176 SSB codes returned by raidcom set chap_user

raidcom set chap_user


Error message

SSB2SSB1



380 Troubleshooting

Table 176 SSB codes returned by raidcom set chap_user (continued)

raidcom set chap_user


Error message

SSB2SSB1





The specified password for CHAP authentication is incorrect.47EAB957ExecutingCMDRJE


The iSCSI target cannot be set because the user authenticationof the iSCSI target is invalid.

47EEB957ExecutingCMDRJE





Table 177 SSB codes returned by raidcom reset chap_user

raidcom reset chap_user


Error message

SSB2SSB1








The iSCSI target cannot be set because the user authenticationof the iSCSI target is invalid.

47EEB957ExecutingCMDRJE





Table 178 SSB codes returned by raidcom send ping

raidcom send ping


Error message

SSB2SSB1


The specified port is blocked.84002E10ExecutingCMDRJE


Table 178 SSB codes returned by raidcom send ping (continued)

raidcom send ping


Error message

SSB2SSB1








Table 179 SSB codes returned by raidcom add rcu_iscsi_port

raidcom add rcu_iscsi_port


Error message

SSB2SSB1

The product ID is invalid.30052E00ExecutingCMDRJE

The specified IP address is invalid.9C012E02ExecutingCMDRJE

The serial number or product ID of the target storage systemis incorrect.



The specified RCU port is already registered.32022E22ExecutingCMDRJE

The total number of registered iSCSI targets and RCU portsin the storage system reached the maximum.


The total number of registered iSCSI targets and RCU portsper port reached the maximum.



The specified port is not a port of the package for iSCSI.83012E31ExecutingCMDRJE





Table 180 SSB codes returned by raidcom delete rcu_iscsi_port

raidcom delete rcu_iscsi_port


Error message

SSB2SSB1

The serial number, product ID, or SSID of the target storagesystem is incorrect.


The specified RCU port is not registered.32012E20ExecutingCMDRJE

Deletion cannot be executed because the RCU path is defined.32012E21ExecutingCMDRJE

382 Troubleshooting

Table 180 SSB codes returned by raidcom delete rcu_iscsi_port (continued)

raidcom delete rcu_iscsi_port


Error message

SSB2SSB1





Table 181 SSB codes returned by raidcom add external_iscsi_name

raidcom add external_iscsi_name


Error message

SSB2SSB1




The specified iSCSI target is already registered.9B012E22ExecutingCMDRJE

The total number of registered iSCSI target and RCU port inthe storage system reached the maximum.


The total number of registered iSCSI targets and RCU portsper port reached the maximum.




Table 182 SSB codes returned by raidcom check external_iscsi_name

raidcom check external_iscsi_name


Error message

SSB2SSB1

The specified iSCSI target is not registered.9B012E20ExecutingCMDRJE

Table 183 SSB codes returned by raidcom delete external_iscsi_name

raidcom delete external_iscsi_name


Error message

SSB2SSB1


The operation cannot be done because the specified iSCSItarget is defined to the external path.



Table 184 SSB codes returned by raidcom discover external_iscsi_name

raidcom discover external_iscsi_name


Error message

SSB2SSB1

Failed to search the iSCSI target. Check the setting of inputparameter or the network connection.


The processing failed because multiple searches for the iSCSItarget were executed.




Table 185 SSB codes returned by raidcom modify external_chap_user

raidcom modify external_chap_user


Error message

SSB2SSB1

The specified CHAP user or CHAP secret is invalid.9B022E00ExecutingCMDRJE





Table 186 SSB codes returned by raidcom modify initiator_chap_user

raidcom modify initiator_chap_user


Error message

SSB2SSB1

The specified CHAP user or CHAP secret is invalid.9B022E00ExecutingCMDRJE

The operation cannot be done because the specified port isdefined to the external path.




Table 187 SSB codes returned by raidcom modify parity_grp

raidcom modify parity_grp


Error message

SSB2SSB1

The parity group number or the external volume group numberis not within a valid range.


The specified group type is not correct.01022E00ExecutingCMDRJE

The specified operation cannot be done because the collectioncopy is in process.


384 Troubleshooting

Table 187 SSB codes returned by raidcom modify parity_grp (continued)



Error message

SSB2SSB1

The specified operation cannot be done because the dynamicsparing is in process.


The specified operation cannot be done because the copy backis in process.


The specified operation cannot be done because the collectionaccess is in process.


The specified parity group is a RAID configuration which cannotbe used as the pool vol.


The specified operation cannot be done because the paritygroup does not support capacity expansion.


The operation cannot be done because data remains in aexpanded space of the parity group. Format parity groups.


The specified operation cannot be done because the encryptionis enabled.


The specified operation cannot be done because the drivecopy is in process.


The specified operation cannot be done because the drive isblocked.


The specified operation cannot be done because the drive’sfirmware does not support capacity expansion.


The specified operation cannot be done because the LDEV isunder format, shredding, or quick format.


The specified operation cannot be done because the pool isused as the pool which is full allocated.


The specified operation cannot be done because the LDEV inthe parity group is dispersed in several pools.


There is a volume which Data Retention is set in the specifiedparity group.


The specified operation cannot be done because the LDEV iscreated in the expanded space of the parity group.


The specified operation cannot be done because the LDEVbelongs in the blocked pool.


The operation failed because the DKCMAIN microcode versionis mixed.




There is no parity group.01002E20Executing/AsyncCMDRJEGet Command Status

The volume which Cache Residency is configured is availablein the specified parity group.


The LDEV of which path is defined is available.00072E30AsyncGet Command Status


Table 187 SSB codes returned by raidcom modify parity_grp (continued)



Error message

SSB2SSB1

The LDEV in the specified parity group is used as the journalvolume.


The LDEV of which size is smaller than the possible value thatcan be registered to the pool is in the specified parity group.


The LDEV in the specified parity group is used as the quorumdisk.


The LDEV in the specified parity group is used as the pairvolume.


The LDEV in the specified parity group is mapped for the onlinedata migration.


Internal error occurred. Contact HPE technical support.FEEC2ECFExecuting/AsyncCMDRJEGet Command Status

The specified operation cannot be done because the operationis not supported.


Table 188 SSB codes returned by raidcom get local_replica_opt

raidcom get local_replica_opt


Error message

SSB2SSB1



Internal error occurred.FEEC2EBDExecutingCMDRJE

Table 189 SSB codes returned by raidcom modify local_replica_opt

raidcom modify local_replica_opt


Error message

SSB2SSB1

Multiple option IDs cannot be specified.9D012E02ExecutingCMDRJE

The specified option ID is out of the effective range.9D022E02ExecutingCMDRJE

The operation cannot be done because another application,for example Remote Web Console, or SVP is used.


Shadow Initialize is running.80192E11ExecutingCMDRJE

A shared memory is not installed.810A2E21ExecutingCMDRJE



Internal error occurred. Contact HPE technical support.FEEC2EBDExecutingCMDRJE

Internal error occurred. Contact HPE technical support.9E012EBEExecutingCMDRJE

386 Troubleshooting

Table 190 SSB codes returned by raidcom initialize pool

raidcom initialize pool


Error message

SSB2SSB1

The value of specified ID is out of range.60002E00ExecutingCMDRJE

The volume defined in specified pool is used as a ContinuousAccess Synchronous pair.


The volume defined in specified pool is used as a ContinuousAccess Journal pair.


The volume defined in specified pool is used as a Fast Snappair.


The volume defined in specified pool is used as an Auto LUNV2 volume.


The volume defined in specified pool is used as a HighAvailability (HA) pair.


The volume defined in specified pool is used as a BusinessCopy pair.


The specified pool is blocked.600B2E10AsyncGet Command Status

The specified pool is shrinking.600D2E10AsyncGet Command Status

The specified pool is in deduplication disabled.60202E10AsyncGet Command Status

The specified pool is being created or expanded.60232E10AsyncGet Command Status

The specified pool is being deleted.60242E10AsyncGet Command Status

The deduplication system data volume defined in the specifiedpool or the volume capacity saving set as enabled is notblocked.


The command cannot be accepted. Wait a while and issue thesame command.


The specified pool is not installed.60002E20Executing /CMDRJEAsyncGet Command Status

The control memory or shared memory for Thin Provisioningis not installed.


The volume defined in specified pool is used as a journalvolume.




The internal error occurs. Contact HPE technical support.FEEC2EE7Executing /CMDRJEAsyncGet Command Status

Calling HPE technical supportIf you need to contact HPE technical support, please provide as much information about theproblem as possible, including:

• The circumstances surrounding the error or failure.

• The exact content of any error messages displayed on the host systems.

Calling HPE technical support 387

• The exact content of any error messages displayed by Remote Web Console.

• The Remote Web Console configuration information (use the Dump Tool).

• The data in the RAID Manager error log file and trace data (all files in the HORCM_LOGdirectory).

• The service information messages (SIMs), including reference codes and severity levels,displayed by Remote Web Console.

The Hewlett Packard Enterprise customer support staff is available 24 hours a day, seven daysa week. To contact technical support, log on to Hewlett Packard Enterprise Support Connect forcontact information.

388 Troubleshooting

10 Support and other resourcesAccessing Hewlett Packard Enterprise Support

• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/assistance

• To access documentation and support services, go to the Hewlett Packard Enterprise SupportCenter website:www.hpe.com/support/hpesc

Information to collect• Technical support registration number (if applicable)

• Product name, model or version, and serial number

• Operating system name and version

• Firmware version

• Error messages

• Product-specific reports and logs

• Add-on products or components

• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the

product interface. Review your product documentation to identify the recommended softwareupdate method.

• To download product updates, go to either of the following:

Hewlett Packard Enterprise Support Center Get connected with updates page:www.hpe.com/support/e-updates

◦

◦ Software Depot website:www.hpe.com/support/softwaredepot

• To view and update your entitlements, and to link your contracts and warranties with yourprofile, go to the Hewlett Packard Enterprise Support Center More Information on Accessto Support Materials page:www.hpe.com/support/AccessToSupportMaterials

IMPORTANT: Access to some updates might require product entitlement when accessedthrough the Hewlett Packard Enterprise Support Center. You must have an HP Passportset up with relevant entitlements.

Related informationThe following documents and websites provide related information:

• XP7 Continuous Access Journal for Mainframe Systems User Guide

• XP7 Continuous Access Synchronous for Mainframe Systems User Guide

Accessing Hewlett Packard Enterprise Support 389

http://www.hpe.com/assistance

http://www.hpe.com/support/hpesc

www.hpe.com/support/e-updates

http://www.hpe.com/support/softwaredepot

http://www.hpe.com/support/AccessToSupportMaterials

• XP7 Continuous Access Synchronous User Guide

• XP7 External Storage for Open and Mainframe Systems User Guide

• XP7 for Compatible FlashCopy Mirroring User Guide

• XP7 Provisioning for Mainframe Systems User Guide

• XP7 RAID Manager User Guide

• XP7 Remote Web Console Messages

• XP7 RemoteWeb Console User GuideYou can find these documents at:

• Hewlett Packard Enterprise Support Center website (Manuals page):www.hpe.com/support/manuals

Click Storage >Disk Storage System > XP Storage, and then select your Storage System.

• Hewlett Packard Enterprise Information Library website:www.hpe.com/info/enterprise/docs

Under Products and Solutions, click HP XP Storage. Then, click XP7 Storage under HPXP Storage.

Websites

LinkWebsite

www.hpe.com/info/enterprise/docsHewlett Packard Enterprise Information Library

www.hpe.com/support/hpescHewlett Packard Enterprise Support Center

www.hpe.com/assistanceContact Hewlett Packard Enterprise Worldwide

www.hpe.com/support/e-updatesSubscription Service/Support Alerts

www.hpe.com/support/softwaredepotSoftware Depot

www.hpe.com/info/insightremotesupport/docsInsight Remote Support

www.hpe.com/info/hpux-serviceguard-docsServiceguard Solutions for HP-UX

www.hpe.com/storage/spockSingle Point of Connectivity Knowledge (SPOCK) Storagecompatibility matrix

www.hpe.com/storage/whitepapersStorage white papers and analyst reports

Remote supportRemote support is available with supported devices as part of your warranty or contractual supportagreement. It provides intelligent event diagnosis, and automatic, secure submission of hardwareevent notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolutionbased on your product’s service level. Hewlett Packard Enterprise strongly recommends thatyou register your device for remote support.For more information and device support details, go to the following website:www.hpe.com/info/insightremotesupport/docs

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. Tohelp us improve the documentation, send any errors, suggestions, or comments to Documentation

390 Support and other resources

www.hpe.com/support/manuals

www.hpe.com/info/enterprise/docs

http://www.hpe.com/info/enterprise/docs

http://www.hpe.com/support/hpesc

http://www.hpe.com/assistance

http://www.hpe.com/support/e-updates

http://www.hpe.com/support/softwaredepot

http://www.hpe.com/info/insightremotesupport/docs

http://www.hpe.com/info/hpux-serviceguard-docs

http://www.hpe.com/storage/spock

http://www.hpe.com/storage/whitepapers

http://www.hpe.com/info/insightremotesupport/docs

Feedback ([email protected]). When submitting your feedback, include the documenttitle, part number, edition, and publication date located on the front cover of the document. Foronline help content, include the product name, product version, help edition, and publication datelocated on the legal notices page.

Documentation feedback 391

mailto:[email protected]

A Warranty and regulatory informationFor important safety, environmental, and regulatory information, see Safety and ComplianceInformation for Server, Storage, Power, Networking, and Rack Products, available atwww.hpe.com/support/Safety-Compliance-EnterpriseProducts.

Warranty informationHPE ProLiant and x86 Servers and Optionswww.hpe.com/support/ProLiantServers-Warranties

HPE Enterprise Serverswww.hpe.com/support/EnterpriseServers-Warranties

HPE Storage Productswww.hpe.com/support/Storage-Warranties

HPE Networking Productswww.hpe.com/support/Networking-Warranties

Regulatory informationBelarus Kazakhstan Russia marking

Manufacturer and Local Representative InformationManufacturer information:

• Hewlett Packard Enterprise Company, 3000 Hanover Street, Palo Alto, CA 94304 U.S.Local representative information Russian:• Russia:

• Belarus:

• Kazakhstan:

392 Warranty and regulatory information

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

http://www.hpe.com/support/ProLiantServers-Warranties

http://www.hpe.com/support/EnterpriseServers-Warranties

http://www.hpe.com/support/Storage-Warranties

http://www.hpe.com/support/Networking-Warranties

Local representative information Kazakh:• Russia:

• Belarus:

• Kazakhstan:

Manufacturing date:The manufacturing date is defined by the serial number.CCSYWWZZZZ (serial number format for this product)Valid date formats include:• YWW, where Y indicates the year counting from within each new decade, with 2000 as the

starting point; for example, 238: 2 for 2002 and 38 for the week of September 9. In addition,2010 is indicated by 0, 2011 by 1, 2012 by 2, 2013 by 3, and so forth.

• YYWW, where YY indicates the year, using a base year of 2000; for example, 0238: 02 for2002 and 38 for the week of September 9.

Turkey RoHS material content declaration

Ukraine RoHS material content declaration

Regulatory information 393

Index

Aaccessing

updates, 389alternate command device, 19

defining, 19asynchronous commands

list of provisioning, 121processing, 10, 120

authorities for commands and operations, 65Auto LUN

commands, 201configurations, 200controlling, 200specifications, 200

BBelarus Kazakhstan Russia EAC marking, 392

Ccascading connections

and configuration files, 40configuration files, 41

cascading pairs, 175cascading volumes

restrictions, 176cluster manager, 178command device, 16

alternate, 19guarding, 17instance number, 18

command execution modes, 73command parameter, HORCM_CMD (in-band, 29command parameter, HORCM_CMD (out-of-band, 32commands

authorities, 65error logging for audit, 51error messages and troubleshooting, 253examples, 230execution modes, 11in-band execution, 57out-of-band execution, 57processing asynchronously, 120processing synchronously, 120

configuration check, 80configuration definition file, 25

examples, 25configuration definition file settings, 28

cascading connections, 40–41HORCM_ALLOW_INST, 38HORCM_CMD (in-band, 29HORCM_CMD (out-of-band, 32HORCM_DEV, 34HORCM_INST, 36HORCM_INSTP, 37HORCM_LDEV, 36HORCM_LDEVG, 37

HORCM_MON, 28configuration file

parameters, 27configuration file parameters, 27configuration setting commands, raidcom, 10consistency groups, 190contacting Hewlett Packard Enterprise, 389copy groups, 85

defining, 91deleting, 95deleting LDEV, 94

Ddata protection, 15

command compatibility, 225configuration examples, 224defining command device, 229environment variables, 228facility, 221parameters, 221permission command, 225permitting protected volumes, 227specifications, 223

data protection operations, 220data replication operations, 171Data Retention

how it works, 220restrictions on volumes, 220

definition file, configurationparameters, 27

definition file, configuration parameters, 27device groups, 85

definition methods, 85deleting, 90settings and read operations, 85

device parameter, HORCM_DEV, 34discovering remote volumes, 217document

related information, 389documentation

providing feedback on, 390website, 390

dual pathing on Solaris, 17duplicated mirroring, 175

EEAC marking

Belarus Kazakhstan Russia, 392endian

little vs big, 24environment variables for data protection, 228environment variables for log directories, 50error codes

horctakeover and pair commands:troubleshooting, 262raidscan, raidqry, raidar, horcctl:troubleshooting, 263troubleshooting, 251, 264

error messages

394 Index

troubleshooting, 251EuroAsian Economic Commission (EAC), 392examples

directory mound for Windows, 239GPT disk for Windows, 238group version control for mixed storage system

configurations, 230LDM volume discovery and flushing for Windows, 230mountvol attached to Windows, 233signature changing facility for Windows, 236SLPR configuration, 243specify host group, 241system buffer flushing, 233volume discovery, 231

external volumescreating, 153operations, 153

Ffence level settings, 194, 196fibre channel failure, 194files, 44

log and trace files, 48OpenVMS, 47UNIX, 44user-created scripts, 56Windows, 45

Hhorcm.conf file, 206HORCM_ALLOW_INST, 38HORCM_CMD (in-band), 29HORCM_CMD (out-of-band), 32HORCM_DEV, 34HORCM_INST, 36HORCM_INSTP, 37HORCM_LDEV, 36HORCM_LDEVG, 37HORCM_MON, 28host components, 22

and pairing, 24HORCM, 22instance configurations, 22

host group check, 79

Iin-band

command execution, 57in-system replication, 15instance number, 18instance parameter, HORCM_INST, 36internal volumes

creating, 133, 137operations, 133

LLDEV

adding, 88check, 75

deleting, 89LDEV group function, 82LDEV group parameter, HORCM_LDEVG, 37LDEV grouping, 14LDEV nickname, 14, 123LDEV parameter, HORCM_LDEV, 36line-by-line mode, 10–11, 73–74log and trace files, 48

command error logging for audit, 51log files, 48

environment variables for log directories, 50names and locations, 49

logging command errors for audit, 51

Mmirror descriptors

and volumes, 223configuration file correspondence, 38

mirroringduplicated, 175

monitor parameter, HORCM_MON, 28MxN configuration and control, 205

OOpenVMS

files, 47starting up one instance, 116starting up two instances, 116

out-of-bandcommand execution, 57

Ppairdisplay examples on HOST1 and HOST2, 42paired volumes, 171parameters, configuration, 27permission command and data protection, 225port check, 78precheck, 11provisioning operations, 120

RRAID Manager functions, 9raidcom command

configuration setting command, 10regulatory information, 392

Turkey RoHS material content declaration, 393Ukraine RoHS material content declaration, 393

related documentation, 389remote command device

defining, 19replication, 205

remote replication, 15remote support, 390remote volume discovery, 217replication

cascading pairs, 175cascading volumes, 176duplicated mirroring, 175in-system, 15

395

local system configuration, 184operations, 171, 184pair status, 185paired volumes, 190remote, 15remote system configuration, 182requirements, 172sidefile cache, 192volume status, 185

resource group locking, 14resource lock function, 73restrictions

Auto LUN, 205cascading volumes, 176Data Retention, 220RAID Manager operations, 249replication, 190

Sscript files, 56

content checking, 75SCSI command interface

command competition, 21command flow, 21LDEVs, 21

SCSI commands, 20sidefile, 192

cache, 192SLPR

configuration examples, 243security, 242security:specify SLPR protection facility, 243

Solarisdual pathing, 17

SSB codestroubleshooting, 265

startingas a service on Windows, 117one instance on OpenVMS, 116one instance on UNIX, 114one instance on Windows, 115two instance on OpenVMS, 116two instances on UNIX, 114two instances on Windows, 115

supportHewlett Packard Enterprise, 389

synchronous commandsprocessing, 120

system log messagestroubleshooting, 251

Ttakeover commands, 178trace control command, 50trace files, 50

trace control command, 50transaction mode, 10–11, 73–74troubleshooting, 248

command error codes, 253

error messages and error codes, 251general, 248generic error codes (horctakeover and pair commands),

262, 265generic error codes (raidscan, raidqry, raidar, horcctl),

263notes and restrictions, 249specific codes, 264system log messages, 251

Turkey RoHS material content declaration, 393

UUkraine RoHS material content declaration, 393UNIX

files, 44starting up one instance, 114starting up two instances, 114

updatesaccessing, 389

user authentication, 13, 61command operation, 62

Vvirtual volumes

creating, 140, 149operations, 140, 147

volumesrestrictions using Data Retention, 220

Wwarranty information, 392

HPE Enterprise servers, 392HPE Networking products, 392HPE ProLiant and x86 Servers and Options, 392HPE Storage products, 392

websites, 390product manuals, 390

Windowsfiles, 45starting as a service, 117starting up one instance, 115starting up two instances, 115

396 Index

XP7 RAID Manager User Guide - Hewlett Packardh20628. · 2019-01-17 · XP7RAIDManagerUserGuide...

Documents

Transcript of XP7 RAID Manager User Guide - Hewlett Packardh20628. · 2019-01-17 · XP7RAIDManagerUserGuide...