Home

Hitachi Command Control Interface

1. Table 9 62 SSB codes that are returned by raidcom disconnect path command raidcom disconnect path Executing Error code Error message Async sspi ssB2 Description CMDRJE Executing The path group is out of the enabled range CMDRJE Executing The value of specified port is invalid Get Command Async The specified external path has already Status disconnected the path or is in the process of checking path Get Command Async The target LDEV is blocked Status Get Command Async The path for the specified external path is in the Status state of disconnected Get Command Async This command cannot be operated due to one of Status the following reasons e All the paths to the external volumes are blocked e There will be no normal paths CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Executing There is no specified external volume Status Async CMDRJE Get Command Executing There is no connection path to an external Status Async volume CMDRJE Troubleshooting 9 91 Hitachi Command Control Interface User and Reference Guide raidcom disconnect path Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description WWYN is not registered CMDRJE Executing There is no path group CMDRJE Executing external_wwn is not defined Get Co
2. Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide ShadowImage command paircreate pairsplit pairresync Pair Status PAIR No split split E option C option S option Resync Acceptable Accepted 2 2 to 4 Accepted 5 Accepted 2 2to4 Accepted 1 Acceptable PSUS Rejected Acceptable Accepted 5 Acceptable Accepted 1 Accepted 2 PSUE Rejected Acceptable Acceptable Acceptable Accepted 1 Accepted 2 Legend Accepted Accepted and executed When the operation terminates normally the status changes to the indicated number Acceptable Accepted but no operation is executed Rejected Rejected and operation terminates abnormally In the following descriptions when the pair statuses of P VOL and S VOL are 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 VOL is guaranteed Therefore when using the S VOL with the SMPL state after stopping Write to the P VOL generate a paired volume and then split the paired volume after confirming that the paired volume has the PAIR status In the PSUE state ShadowImage does not manage differential data at the P VOL or S VOL Therefore pairresync issued to a pair in the PSUE state is all copy performance but the copy progress rate returned by the
3. 9 60 Executing A pair cannot be created because there are not enough cache management devices Troubleshooting Hitachi Command Control Interface User and Reference Guide raid com add snapshot Error message Executing Async Executing Error code Description SSB1 SSB2 The command ends abnormally because the volume out of the range of LDEV number is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume out of the range of LDEV number is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The specified pool ID is out of the range Executing There are not enough required input parameters Executing A pair cannot be created because the volume exceeded the support size is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume exceeded the support size is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the V VOL is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the pool VOL is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the journal volume of Universal Replicator i
4. Get Command Async An internal error occurred Status Call Hitachi Data Systems Support Center Table 9 65 SSB codes that are returned by raidcom logout command raidcom logout Executing Error code Async CMDRJE Executing 2E01 2200 Failed to release the resource lock Table 9 66 SSB codes that are returned by raidcom monitor pool command Error message Description raidcom monitor pool Executing Error code Async sspi ssB2 Executing The value of pool ID is out of range Description Error message Executing Monitor cannot be started because the performance monitor is in the collecting status Executing Monitor cannot be stopped because the performance monitor is stopped Executing Monitor cannot start because the performance monitor is in use Retry the operation after completing or stopping the reallocation of Tier Executing There is not enough time after collecting performance monitor Executing The pool is not in the state of specifying the performance monitor to start or stop Executing The pool ID is not installed Executing A SM for Dynamic Provisioning is not installed Executing A SM for Dynamic Tiering is not installed Executing The program product of Dynamic Tiering is not installed Executing Start or stop of performance monitor by hand cannot be done because it is a pool for Dynamic Provisioning or it is aut
5. ee es 6 7 Restrictions for ShadowImage cascading volumes 020005 6 8 Restriction for TrueCopy ShadowImage cascading volumes 6 9 TrueCopy operations 6 i s434b5 es eb ad sO 8 seo OH Osos 1 OPH ESSER SLES LB 6 9 TrueCopy takeover commands 0000 eee eee eee eee 6 10 Takeover switch function 0 sssaaa naaa es 6 12 Swap takeover function 1 es 6 13 SVOL takeover function 2 0 00 cee es 6 14 PVOL takeover function 0 sanaaa aaaea 6 15 TrueCopy remote commands 0000 eee eee 6 16 TrueCopy local commands 0 00 c eee eee eee ees 6 17 TrueCopy ShadowImage and Universal Replicator operations 6 18 vii Hitachi Command Control Interface User and Reference Guide TrueCopy ShadowImage voluMeS 1 0 0 c ce eee 6 18 TrueCopy ShadowImage Universal Replicator pair status 6 19 TrueCopy Async TrueCopy and Universal Replicator volumes 6 25 Sidefile cache for TrueCopy ASyNC 1 6 27 TrueCopy Async transition states and sidefile control 6 28 TrueCopy Async Universal Replicator error state 2008 6 30 TrueCopy TrueCopy Async and Universal Replicator fence level settings 6 31 Setting the fence level f2 see wis bed b ede Hho aes Pee Sw es 6 32 Copy on Write Snapshot operations 0 0 0 cee ees 6 33 Copy on Write Snapshot volumes nasasa asana eee 6 34 Creating a Copy on Write Snapshot pair 0000 ee eee 6 35 C
6. 0 0 0 0 cee eee 3 29 Read operations and command device settingS 00 cea eae 3 29 Define device group 1 ee ees 3 30 Device group creation sssaaa ain be Sew eee ee eae 3 31 LDEV addition to device group 1 cee ees 3 32 LDEV deletion from device group 000 e aaa 3 33 Device group deletion 0 00 cee eee ees 3 34 Copy Group function 22220 veo eee Gve eda ease eee ees Daw tawies 3 35 Copy Group creatio an cues e ae E T ae wae ae eR eee 3 36 LDEV addition to a copy group 1 ee es 3 37 LDEV deletion from copy group 0 cee eee es 3 37 Copy group deletion naana 8 te See a oles Pa Wee Ne ead 3 38 Pair operation by specifying a copy group eee eee ees 3 39 Pair operations with mainframe volumes 0 0000 aaa naaa nnna 3 41 Using dummy LUs for mainframe LDEVS 0 000 eee eee 3 41 Pair status and access permission for mainframe LDEVs 3 41 Operational differences for multiplatform volumes 00005 3 43 Operational differences for replication commands 00005 3 44 Global virtualization function VSP G1000 only 0 0 c eee eee 3 45 System configuration example with the global virtualization function 3 45 Using CCI in a system configuration with the global virtualization function 3 46 Specifying a virtual storage machine by HORCM_VCMD 3 47 Configuration definition file settings when specifying a virtual storage
7. Executing The program product of Dynamic Tiering is not installed Executing Start or stop of performance monitor by hand cannot be done because it is a pool for Dynamic Provisioning or it is automatic execution mode Executing The specified pool is the one for Thin Image or Copy on Write Snapshot Executing Reallocation cannot be done because there is only one Tier in the pool group Executing An internal error occurred Call Hitachi Data Systems Support Center Troubleshooting 9 95 Hitachi Command Control Interface User and Reference Guide Table 9 68 SSB codes that are returned by raidcom extend Idev command raidcom extend Idev Error message Executing Async Executing Error code SSB1 SSB2 Description The command cannot be operated because the virtual LDEV is not defined yet Executing See the troubleshooting topics in the Provisioning Guide for the storage system Table 9 69 SSB codes that are returned by raidcom delete resource command raidcom delete resource Error message Executing Async Executing Error code SSB1 SSB2 Description The specified resource group cannot be operated Executing Resource groups cannot be deleted because the resource groups are locked Executing The LDEV and the host group cannot be set to the different virtual storage machine Executing There is no parity group
8. Volume B Group name oradb 2 j Figure 6 3 ShadowImage duplicated mirrors ShadowImage cascading pairs ShadowImage provides a cascading function for the ShadowImage S VOL Cascading mirror volumes can be specified up to the maximum quantity 2 The cascading mirrors of the S VOL are expressed as virtual volumes using the mirror descriptors MU 1 2 in the configuration diagram as shown below The MU 0 of a mirror descriptor is used for connection of the S VOL Data replication operations with CCI 6 7 Hitachi Command Control Interface User and Reference Guide MU 0 Group name oradb Group name oradb1 Volume E S VOL Volume F S VOL Peteeeecce SCS HRS eee eee Pe eeeeeeseeees SHCSSSSR ESSER SSeS Hees eee eee sees eeeee SSSCOTSSTS SSS SOO SSE Sees SEESSESSEESSESSEEE Group name oradb2 Volume H S VOL Peeesseeessesensses Figure 6 4 ShadowImage cascade volume pairs Restrictions for ShadowImage cascading volumes Pair Creation Pair creation of SVOL oradb1 can only be performed after the pair creation of S PVOL oradb If you create the oradb1 pair first without creating the oradb the subsequent oradb creation will be rejected with EX_CMDRJE or EX_CMDIOE 6 8 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Pair splitting Pair splitting of SVOL oradb1 can only be performed after the S PVOL oradb is in a SMPL or PSUS stat
9. HITACHI Inspire the Next Command Control Interface User and Reference Guide Hitachi Virtual Storage Platform G1000 Hitachi Unified Storage VM Hitachi Virtual Storage Platform Hitachi Universal Storage Platform V VM Contents Product Version Getting Help MK 90RD7010 18 Hitachi Data Systems 2010 2014 Hitachi Ltd All rights reserved No part of this publication may be reproduced or transmitted in any form or by any means electronic or mechanical including photocopying and recording or stored in a database or retrieval system for any purpose without the express written permission of Hitachi Ltd Hitachi Ltd reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use This document contains the most current information available at the time of publication When new or revised information becomes available this entire document will be updated and distributed to all registered users Some of the features described in this document might not be currently available Refer to the most recent product announcement for information about feature and product availability or contact Hitachi Data Systems Corporation at https portal hds com Notice Hitachi Ltd products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements The use of Hitachi Ltd products is governed by the ter
10. Start or stop the performance monitor for Dynamic Tiering raidcom monitor pool pool lt pool ID gt lt pool naming gt operation lt type gt Start or stop the tier reallocation of a pool for Dynamic Tiering raidcom reallocate pool pool lt pool ID gt lt pool naming gt operation lt type gt LU path see the Provisioning Guide for the storage system 5 10 Set LU path raidcom add lun port lt port gt lt host group name gt ldev_id lt ldev gt lun_id lt lun gt grp_opt lt group option gt device_grp_name lt device group name gt lt device names Delete LU path raidcom delete lun port lt port gt lt host group name gt lun_id lt lun gt ldev_id lt ldev gt grp_opt lt group option gt device grp name lt device group name gt lt device names Display LU path information raidcom get lun port lt port gt lt host group name gt Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation type External volume Universal Volume Manager see the Provisioning Guide for the storage system Description Search external storage Corresponding command raidcom discover external storage port lt port gt Search external volume raidcom discover lun port lt port gt external wwn lt wwn strings gt Map external volume raidcom add external _grp
11. Executing The value of the capacity is invalid Table 9 17 SSB codes that are returned by raidcom delete journal command raidcom delete journal Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description The number of specified LDEV is invalid Get Command Status Async The specified volume capacity is too small CMDRJE Executing The specified journal ID is exceeds the range Get Command Status Async The specified volume is not installed or cannot be used Get Command Status Async The specified volume is used in maintenance operation Get Command Status Async The specified operation failed because the journal or mirror is not in the operable status Get Command Status Async The journal volume cannot be deleted with the specified journal status Get Command Status Async The operation cannot be done because it is in the state of start up Get Command Status Async Troubleshooting The operation cannot be done because the internal processing is in progress Wait for a while then retry the operation 9 35 Hitachi Command Control Interface User and Reference Guide raidcom delete journal Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description The command cannot be accepted After a while execute the same comma
12. Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 42 SSB codes that are returned by raidcom add ssid command raidcom add ssid Error message Executing Async Error code SSB1 Description SSB2 CMDRJE Executing 2E00 3001 The CU number of the RCU exceeds the effective value CMDRJE Executing 2E00 3008 The command cannot be executed because the parameter of the specified RCU is invalid CMDRJE Executing 2E00 7100 The CU number is out of effective range CMDRJE Executing 2E11 8004 The operation cannot be done because the microcode is being changed Troubleshooting 9 73 Hitachi Command Control Interface User and Reference Guide raidcom add ssid Error code Error message sy rete Description sync ssBi SSB2 CMDRJE Executing 2E20 3000 The serial number product ID or SSID of the target storage system is incorrect CMDRJE Executing 2E20 3001 The command cannot be executed because the specified RCU is not registered CMDRIJE Executing 2E22 3002 The operation cannot be performed due to one of the following reasons e The number of RCUs registered in MCU or RCU is more than four e The number of RCUs registered in the system is more than 64 in the case of specifying the cu free CMDRJE Executing 2E23 3301 The number of the specified SSIDs is invalid CMDRJE Executing 2E31 3001 The command cannot be ex
13. Executing A resource group cannot be deleted because the specified resource group is undefined Executing There is no external volume group Executing The information for the virtual storage machine is set in the specified resource Executing A resource group cannot be deleted because a resource belongs to the specified resource group Executing A resource cannot be deleted from the resource group because the specified LDEV number is not the top LDEV number in the LUSE volume Executing The operation to resource group 0 meta_resource cannot be performed Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 70 SSB codes that are returned by raidcom add resource command raidcom add resource Error message Executing Async Executing Error code SSB1 SSB2 Description The specified resource group name is against the naming rules 9 96 Executing The specified resource group cannot be operated Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add resource Error code Executing Async sspi ssB2 Error message Description Executing The resource ID and the sub resource ID are out of the effective range Executing The machine type is invalid Executing The serial number is invalid Executing The value of specified port is i
14. Table 5 2 Performing provisioning operations by specifying a device group Contents of operation Command Register a journal group to a journal raidcom add journal Delete a journal group from a journal delete a journal raidcom delete journal Delete an LDEV V VOL raidcom delete ldev Provisioning operations with CCI 5 13 Hitachi Command Control Interface User and Reference Guide Contents of operation Command Extend the capacity of V VOL for Dynamic Provisioning raidcom extend ldev Dynamic Provisioning for Mainframe Dynamic Tiering Display the LDEV information raidcom get ldev Format an LDEV raidcom initialize ldev Create an LU path raidcom add lun Delete an LU path raidcom delete lun Create a pool for Copy on Write Snapshot raidcom add snap _ pool Extend the capacity of a pool for Copy on Write Snapshot raidcom add snap_pool Create a pool for Dynamic Provisioning Dynamic raidcom add dp pool Provisioning for Mainframe Extend the capacity of a pool for Dynamic Provisioning raidcom add dp pool Dynamic Provisioning for Mainframe Dynamic Tiering Create a resource group raidcom add resource Delete a resource group raidcom delete resource Operation method Specify the name of device group max 32 characters and the device name in the device group max 32 characters and execute a command The following shows an example to map the LDEV to the
15. An error exists in the format or parameters of the HORCM configuration file SHORCM_CONF Refer to the HORCM startup log to identify the cause of the error HORCM_009 TrueCopy ShadowImage connection to the CCI software failed System devices are improperly connected or an error exists in the device parameter in the HORCM configuration file Refer to the HORCM startup log to identify the cause of the error HORCM_101 TrueCopy ShadowImage and the CCI software communication fails A system I O error occurred or an error exists in the device parameter in the HORCM configuration file SHORCM_CONF Refer to the HORCM startup log to identify the cause of the error HORCM_102 The volume is suspended The pair status was suspended due to code XXXX Troubleshooting Contact the Hitachi Data Systems Support Center Hitachi Command Control Interface User and Reference Guide Message ID HORCM_103 Condition Detected a validation check error on this volume XxXxX unit x ldev x CfEC n MNEC n SCEC n BNEC n A validation error occurs on the database volume or validation parameters for this volume are illegal Recommended action Please confirm the following items and use raidvchkdsp v lt op gt command for verifying the validation parameters 1 Check if the block size vs lt size gt is an appropriate size 2 Check if the type for checking
16. Error in paired volume operation TrueCopy only If an error occurs in duplicated writing in paired volumes that is pair suspension the server software using the volumes may detect the error by means of the fence level of the paired volume In such a case check the error notification command or syslog file to identify a failed paired volume The system administrator can confirm that duplicated writing in a paired volume is suspended due to a failure and the system runs in regressed state using the error notification command of the TrueCopy HORCM monitors failures in paired volumes at regular intervals When it detects a failure it outputs it to the host s syslog file Thus the system administrator can detect the failure by checking the syslog file Concerning the operation of the RAID storage system the failure can also be found on Storage Navigator or SVP provided Issue the TrueCopy commands manually to the identified failed paired volume to try to recover it If the secondary volume is proved to be the failed volume issue the pair resynchronization command to recover it If the primary volume fails delete the paired volume pair splitting simplex and use the secondary volume as the substitute volume Troubleshooting 9 5 Hitachi Command Control Interface User and Reference Guide Items Notes and restrictions About var usr CCI uses var tmp or usr tmp as the directory for the UNIX tmp directory domain
17. Status Get Command Async 2E11 8108 The operation cannot be done because there is Status blocked part in the system CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Executing 2E20 0007 The specified CLPR does not exist Get Command Status Async CMDRJE Executing 2E20 0100 There is no parity group CMDRJE Executing 2E20 6000 Pool ID is invalid Get Command Async Status Get Command Async 2E20 8300 The specified MP Blade is not installed Status Get Command Status Asynchrono 2E21 6003 There is not enough free shared memory space us Get Command Status Asynchrono 2E21 8300 Package for Mainframe is required when you us specify the emulation type of mainframe CMDRJE Executing 2E21 9001 The program product is not installed CMDRJE Executing 2E21 9002 The program product is not installed CMDRJE Get Executing 2E21 9004 The program product is not installed Command Status Async Troubleshooting 9 33 Hitachi Command Control Interface User and Reference Guide raidcom add Idev Error code Error message eae Description sync SSB1 SSB2 CMDRJE Executing 2E21 900E Compatible Software for IBM FlashCopy SE program product is not installed CMDRJE Executing 2E22 0001 LDEV is already defined CMDRJE Executing 2E22 OOOF You cannot create the
18. e For full specification Specifies the command device for Serial 30095 LDEV 250 connected to Port CL1 A Host group 1 CMD 30095 250 CL1 A 1 CCI software environment Hitachi Command Control Interface User and Reference Guide e Other example CMD 30095 250 CL1 A CMD 30095 250 CL1 dev_name for UNIX In the UNIX SAN environment a device file name is changed at the failover operation under the UNIX SAN environment or each reboot process under the Linux when the SAM is reconfigured CCI user is required to change the HORCM_CMD described in the CCI configuration file by searching new Device special file Therefore CCI supports the following naming format to specify Serial LDEV Port HINT as an expression way of command device for UNIX For VSP Gi000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 CMD Ser Idev Port HINT HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 A 1 dev rdsk Once this name is specified HORCM finds the CMD Serial Ldev Port from the device file specified by the HINT at the time of HORCM startup HINT must specify to be end with for the directory of the device file name or the directory that includes the pattern of device filename as shown in the following Finds CMD which is specified by dev rdsk dev rdsk Finds CMD which is specified by dev rdsk c10 dev rdsk c10 Finds CMD which is specif
19. e OPEN V 960 KB e Other than OPEN V 720 KB Mainframe 870 KB Accessing product documentation The user documentation for CCI and the Hitachi storage systems is available on the Hitachi Data Systems Portal https portal hds com Check this site for the most current documentation including important updates that may have been made after the release of the product Getting help The Hitachi Data Systems customer support staff is available 24 hours a day seven days a week If you need technical support log on to the Hitachi Data Systems Portal for contact information https portal hds com Preface Hitachi Command Control Interface User and Reference Guide Comments Please send us your comments on this document doc comments hds com Include the document title and number including the revision level for example 07 and refer to specific sections and paragraphs whenever possible All comments become the property of Hitachi Data Systems Corporation Thank you Preface xvii Hitachi Command Control Interface User and Reference Guide Preface Hitachi Command Control Interface User and Reference Guide Overview This chapter provides an overview of the Command Control Interface software and CCI operations on the Hitachi RAID storage systems O About Command Control Interface O CCI functions O CCI functions available on all RAID storage systems Overview 1 1 Hitachi Command Control Interface User
20. Async The external volume is used as a Universal Replicator journal volume Get Command Status Async The external volume is used as a pool VOL Get Command Status Async The external volume is used as a pool VOL Get Command Status Async The external volume is used as a Volume Migration VOL Get Command Status Async The external volume is used as a Volume Migration VOL Get Command Status Async The target external group cannot be deleted because a quorum disk exists in it CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center Table 9 10 SSB codes returned by raidcom check_ext_storage path raidcom check_ext_storage path Error code Error message ee Description sync SSB1 SSB2 CMDRJE Executing 2E00 4500 The path group is not in the enabled range CMDRJE Executing 2E00 8400 The value of the port is not enabled Get Command Async 2E10 4301 The specified external volume has already Status disconnected the path or is in the process of checking path Get Command Async 2E11 001B The target LDEV is blocked Status Get Command Async 2E11 4000 The path for the specified external path is in the
21. Description Change the pool for Dynamic Provisioning to the pool for Dynamic Tiering Corresponding command raidcom modify pool pool lt pool ID gt naming gt pool_attribute dt_manual Change the pool for Dynamic Tiering to the pool for Dynamic Provisioning raidcom modify pool pool lt pool ID gt naming gt pool_attribute dp Set the newly allocation free space percentage of the pool for Dynamic Tiering raidcom modify pool pool lt pool ID gt naming gt tier lt Tier number gt lt ratio gt Create virtual volume for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot raidcom add ldev pool lt pool ID gt lt pool naming gt snap ldev_id lt ldev gt capacity lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Extend capacity of virtual volume for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering raidcom extend ldev ldev_id lt ldev gt grp_opt lt group option gt device grp name lt device group name gt lt device names capacity lt size gt Set enabled or disabled of virtual volume tier reallocation for Dynamic Tiering raidcom modify ldev ldev_id lt ldev gt status enable reallocation disable reallocation Release a page of virtual volume for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic
22. EX_UNWCOD Unknown function code EX_UNWCMD Unknown command EX_ERANGE Result too large EX_ENAMLG File name too long EX_INVRCD Invalid return code Configuration Unrecoverable EX_ENLDEV No such LDEV within the RAID EX_ENOUNT No such RAID unit EX_INVMUN Invalid mu with HORC or HOMRCF EX_ERPERM Permission denied with the RAID EX_ENOSUP Microcode not supported EX_ESPERM Permission denied with the SLPR Command I O to RAID Recoverable EX_CMDIOE Control command I O error EX_OPTINV A specified option is invalid EX_INVMOD Invalid RAID command mode EX_INVCMD Invalid RAID command Communication for HORCM Recoverable EX_ATTHOR Can t be attached to HORC manager EX_ATTDBG Can t be attached to a Debug layer EX_COMERR Resource EX_ENOMEM Unrecoverable Can t be communicated with HORC manager Not enough core Specific error codes The following table lists the specific error codes returned by these commands e horctakeover e paircurchk paircreate pairsplit pairresync pairevtwait pairvolchk pairsyncwait raidvchkset 9 18 Troubleshooting Hitachi Command Control Interface User and Reference Guide In this table Unrecoverable indicates errors that cannot be recovered by reexecuting the command and Recoverable indicates errors that can be recoverable by reexecuting the
23. External path 3 52 raidcom get path VSP G1000 raidcom add path VSP G1000 raidcom delete path VSP G1000 raidcom disconnect path VSP G1000 raidcom check_ext_storage path VSP G1000 raidcom check_ext_storage external_grp VSP G1000 raidcom discover external_storage VSP G1000 raidcom discover lun CCI functions VSP G1000 Hitachi Command Control Interface User and Reference Guide Operation type Commands raidcom get pool Operation target when you specify the virtual storage machine VSP G1000 raidcom get dp_pool VSP G1000 raidcom get snap_pool VSP G1000 raidcom add dp_pool VSP G1000 raidcom add snap_pool VSP G1000 raidcom delete pool VSP G1000 raidcom modify pool VSP G1000 raidcom reallocate pool VSP G1000 raidcom monitor pool VSP G1000 raidcom get port VSP G1000 raidcom modify port VSP G1000 raidcom get rcu VSP G1000 raidcom add rcu VSP G1000 raidcom delete rcu VSP G1000 Logical path to RCU raidcom add rcu_path VSP G1000 raidcom delete rcu_path VSP G1000 Parity group raidcom get parity_grp VSP G1000 SSID raidcom get ssid VSP G1000 raidcom add ssid VSP G1000 raidcom delete ssid VSP G1000 Resource group raidcom get resource VSP G1000 raidcom add resource VSP G1
24. Get Command Status Async The specified LDEV has the LU path definition Get Command Status Async The specified LDEV is used as a quorum disk Get Command Status Async The specified LDEV is used as a system disk Get Command Status Async The specified LDEV is already used as a pool volume Get Command Status Async The specified LDEV is a command device Get Command Status Async It cannot be used as a pool volume because the size of specified LDEV is less than 8GB Get Command Status Async Creating a pool or adding a pool volume cannot be done because CLPR is mixed in the specified pool Get Command Status Async The specified LDEV is used as a V VOL Get Command Status Async The specified LDEV is a volume of unsupported Dynamic Tiering Get Command Status Async The specified LDEV is used in another program product CMDRJE Executing An LDEV whose emulation type is not available to be mixed is in the specified LDEVs Get Command Status Async The operation cannot be done for the following reasons e The pool volumes to be added to the Dynamic Tiering pool include external volumes whose cache modes are invalid The Dynamic Provisioning pool includes both external volumes whose cache modes are invalid and internal volumes CMDRJE Get Command Status 9 76 Executing Async A pool volume
25. Pool deletion authority raidcom delete pool Storage Administrator Provisioning Dynamic Provisioning virtual volume Dynamic Provisioning virtual volume creation authority raidcom add Idev pool Storage Administrator Provisioning Dynamic Provisioning virtual volume deletion authority raidcom delete Idev CCI functions Hitachi Command Control Interface User and Reference Guide Storage Administrator Provisioning Operation 3 10 Operation target Copy on Write Snapshot virtual volume Authority Copy on Write Snapshot virtual volume creation authority Executable command raidcom add Idev pool Operation authority Role Storage Administrator Provisioning Copy on Write Snapshot virtual volume deletion authority raidcom delete Idev Storage Administrator Provisioning LUN security setting authority raidcom modify port security_switch Storage Administrator System Resource Management Storage Administrator Provisioning Host group Host group creation authority raidcom add host_grp Storage Administrator Provisioning Host group deletion authority raidcom delete host_grp Storage Administrator Provisioning LU path creation authority raidcom add lun Storage Administrator Provisioning LU path deletion authority raidcom delete lun Storage Administrator Provisioning WWN ad
26. Remarks Default raidcom lt action gt checkmode precheck Executed Not executed Not executed Not executed Check only Table 3 6 Execution modes and options of the configuration setting command transaction mode Command syntax raidcom zt lt script file gt Executed Context check Executed Configura tion check Not executed Command execution with no error Executed Remarks Default raidcom zt lt script file gt load lt work file gt Executed Executed Executed Executed With configuration check raidcom zt lt script file gt checkmode precheck Executed Executed Not executed Not executed Check only raidcom zt lt script file gt load lt work file gt checkmode precheck Executed Executed Executed Not executed Detailed description are provided in the following With configuration check Check only Caution Observe the following cautions AN e For lt script file gt specify an executable file name e For lt script file gt either specify a full path name or store under the c HORCM etc folder e For lt work file gt either specify a full path name or store in the current directory Context check This check can be performed to ensure consistent content of the created script file For example it can check if the script refers to an Idev_id that is already deleted i
27. Server Priority Manager operations O Virtual storage machine operations VSP G1000 only Provisioning operations with CCI 5 1 Hitachi Command Control Interface User and Reference Guide About provisioning operations Provisioning operations can be performed using CCI For details about provisioning see the Provisioning Guide for the storage system A Note The operation of refreshing window on Hitachi Storage Navigator or SVP might be delayed while executing provisioning operation on CCI During maintenance work on the storage system SVP in modify mode the command is rejected 2E10 8000 Overview of the configuration setting command CCI functions enable provisioning operations such as host setting LDEV creation and device group creation These operations are required for performing the data replication operations The is done by using the configuration setting command The configuration setting command is specified using the following syntax raidcom lt action gt lt resource gt lt parameter gt The content of operation such as add or delete is specified in the action and a resource object such as LDEV or path is specified in the resource The necessary value to operate the resource object is specified in the parameter For the details about contents of specification for the configuration setting command see Command Control Interface Command Reference Some provisioning operations take much proce
28. Server Priority Manager operations 5 46 Server Priority Manager enables you to prioritize host I O operations to provide high speed processing for specified hosts The host is identified by WWN of host bus adapter Server Priority Manager has two settings prioritized and non prioritized Set the prioritized option for hosts that require high speed processing and the non prioritized option for the other hosts The upper limit of the non prioritized WWN is set to each port to which the non prioritized WWN belongs and is applied only to the port If the threshold is set to the port to which the prioritized WWN belongs the threshold overwrites the thresholds of all the ports in the storage system to which the prioritized WWN belongs as well For more details about the upper limit and the threshold see Setting the priority on host bus adapter on page 5 49 For details about the CCI commands for Server Priority Manager operations see the Command Control Interface Command Reference You can give a nickname SPM name to each host WWN to assist in managing the hosts You can also manage WWN and the SPM name per group The groups to which WWN and the SPM name are registered are managed uniquely The following table lists the details for the Server Priority Manager operations and the management unit Management per SPM Operation Management per port system raidcom modify spm_wwn prioritized or non prioritized threshold upper limit
29. Specify port map LDEV to LUN and create an LU path raidcom add host_grp port lt port gt host_grp_ name lt host group name gt Setting host mode Specify port and set host mode for host group raidcom modify host_grp port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt Displaying host group information Display host group information and confirm result of executing command Provisioning operations with CCI raidcom get host_grp port lt port gt lt host group name gt Hitachi Command Control Interface User and Reference Guide Operation overview Adding host to host group Description Register host to host group of the port Executed command raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt Displaying WWN information Display WWN of connection host registered to the host group and confirm the result of executing the command raidcom get hba_wwn port lt port gt lt host group name gt Creating LDEV Specify external volume group and create LDEV raidcom add ldev external_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Creating LDEV nickname arbitrary Create
30. The parity group or the external volume group that the specified LDEV is belongs to is used in another operation Get Command Status Async The operation of Dynamic Provisioning V VOL cannot be done because there is a blocked pool Get Command Status Async The operation cannot be done because the internal processing is in progress CMDRJE Executing The storage system is in internal process or the configuration changing processes are conflicting Get Command Status Async The operation cannot be done because there is blocked part in the system CMDRJE 9 84 Executing The command cannot be accepted After a while execute the same command Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom delete Idev Error message CMDRJE Get Command Status Executing Async Executing Async Error code SSB1 SSB2 Description LDEV is not installed CMDRJE Executing An LU path has been defined Get Command Status Async The specified LDEV is used as a Dynamic Provisioning Get Command Status Async The specified LDEV is used as a quorum disk Get Command Status Async The specified LDEV is used as a pool volume Get Command Status Async The specified LDEV is used as a journal volume Get Command Status Async The specified LDEV is used in the FICON Data Migr
31. ioscan fun grep rdsk raidscan find verify fd DEVICE FILE Group PairVol Device File M SERIAL UDEV dev rdsk c0t3d0 oradb oradevl c0t3d0 0 35013 17 dev rdsk c0t3d1 oradb oradev2 Unknowm o 35013 18 dev rdsk c0t3d2 0 35013 19 difference between DEVICE_FILE and Device_File You can also use this option to the command device that specified non protection mode It is used for the purpose to see the relation between DEVICE_FILE and the group of horcm conf Note It shows shared LDEV among multiple device files if there is a raidscan f d This option shows the Device_File that was registered on the group of HORCM based on the LDEV as defined in the local instance configuration definition file raidscan p cll d fd Port TargetID Lun Num LDEV P S Status Fence LDEV Device File CL1 D By Oa LILT uedan SMPL c0t3d0 CL1 D By AL scce occ E ete ie tore ee the SMPL c0t3d1 pairdisplay f d This option shows the relation between the Device_File and the paired volumes protected volumes and permitted volumes based on the group even though this option does not have any relation with protection mode pairdisplay g oradb fd Group PairVol L R Device File M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L c0t3d0 0 35013 17 P VOL COPY 35013 18 oradb oradev1 R c0t3d1 0 35013 18 S VOL COPY 35013 17 If either the local or the remote host instan
32. rcu_port lt port gt For example if a path is attempted to be added to a port that does not exist an error is detected An example of the script where the error is detected and the execution result of the actual Context check are shown below e Example of script the text in bold indicates the part of incorrect configuration definition raidcom add path path_grp 1 port CL1 C external_wwn 50060e80 06fc4180 raidcom add path path_grp 1 port CL1 D external_wwn 50060e80 06fc4190 raidcom add path path_grp 1 port CL1 E external_wwn 50060e80 06fc41a0 e Execution result the text in bold indicates the contents of the error accompanying the invalid configuration definition in the script CCI functions 3 21 Hitachi Command Control Interface User and Reference Guide 3 22 C HORCM etc gt raidcom get port store portcnf_27 dat PORT TYPE ATTR SPD LPID FAB CONN SSW SL _ Serial WWN CL1 A FIBRE TAR AUT EF N FCAL N O 64539 O06fcib000000fc1b CL1 B FIBRE TAR AUT EF N FCAL N O 64539 50060e8006fc1ib01 CL2 A FIBRE TAR AUT EF N FCAL N O 64539 50060e8006fc1b10 CL2 B FIBRE TAR AUT EF N FCAL N O 64539 50060e8006fcib11 CL3 A FIBRE TAR AUT E8 N FCAL N O 64539 50060e8006fc1b20 CL3 B FIBRE TAR AUT EO N FCAL N O 64539 50060e8006fc1b21 CL4 A FIBRE TAR AUT D6 N FCAL N O 64539 50060e8006fc1b30 CL4 B FIBRE TAR AUT D2 N FCAL N O 64539 50060e8006fc1b31 CL5 A FIBRE TAR AUT E4 N FCAL N O 64539 50060e8006fc1b40 CL5 B FIBRE TAR AUT DC N FCAL N O
33. 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 CCI instance horcmO xxxxx udp XXXXX the port name number for horcm0 conf horcmi yyyyy udp yyyyy the port name number for horcm1 conf If you want CCI to start automatically each time the system starts up add etc horcmstart sh O 1 to the system automatic startup file for example sbin rc Execute the horcmstart sh script manually to start the CCI instances horcmstart sh 0 1 Set an instance number to the command execution environment For B shell Starting up CCI Hitachi Command Control Interface User and Reference Guide HORCMINST X export HORCMINST X instance number O or 1 For C shell setenv HORCMINST X Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform ShadowImage operations set the HORCC_MRCF environment variable for the CCI execution environment For B shell HORCC_MRCF 1 export HORCC_MRCF For C shell setenv HORCC_MRCF 1 pairdisplay g xxxx XXXX group name Starting up on Windows systems One instance To start up one instance of CCI on a Windows system 1 Modify Ywindir system32 drivers etc services to register the port name number service of the configuration defini
34. Confirm the serial Seq 218 Serial vs RAID by ShadowImage of the storage system using unitID paircreate does not the pairdisplay command have the same RAID or confirm that the serial unit or the unitID is Seq and the unit ID of not identical to the storage system are the same unit ID in the same among hosts using the RAID serial Seq raidqry r command EX_ENOMEM Not enough core Insufficient memory Increase the virtual memory 245 exists capacity of the system or close any unnecessary programs and or daemon processes EW_ENESCR Cannot execute The script file specified Confirm the execution right 131 script file by the zt option permission the extension cannot be performed the execution path of the script file EX_ERANGE Result too large Your entry is one of Refer to the error message 244 the following statuses and designate an e The value was appropriate value or confirm entered beyond whether you specified the the maximum unit correctly e The result value is beyond the maximum e The unit you set is invalid EX_ENAMLG File name too long Undefined error Contact the Hitachi Data 243 Systems Support Center Troubleshooting 9 9 Hitachi Command Control Interface User and Reference Guide Error code EX_ENORMT Error message No remote host alive for remote commands or remote HORCM might be blocked sleeping on an existing I O Condition A timeout occurred on remote comm
35. Give the device name data 0 to 19 to the LDEV 0 to 19 and add it to Device group name grpl data0 to 9 and grp2 datalO to 19 Display the device group information grpi zand grp2 raidcom add copy_grp copy_grp_name ora grpl grp2Create a copy group ora by the device group raidcom get command_status raidcom reset command_status raidcom get copy_erp for I i in 0 1 9 do raidcom add lun port CL1 A HP UX P Idev_id Shi for I i in 10 1 19 do raidcom add lun port CL2 A HP UX S Idev_id Shi raidcom get lun port CL1 A HP UX P raidcom get lun port CL2 A HP UX S raidcom unlock resource resource_grp_name meta_resource raidcom get resource raidcom logout gt grpl and grp2 Display the copy group information Defining paths of LDEV 0 to 9 to Port CLI A zhost group HP UX P Defining paths of LDEV 10 to 19 to Port CL2 A host group HP UX S JLU number is given automatically Display the path information that is set to PortCL1 A host group HP UX P and the path information that is set to PortCL2 A host group HP UX S Unlock the resource group meta_resource Display the resource group information Log out Figure 5 4 Script examples of internal open system volume operation 2 2 Virtual volume Dynamic Provisioning operations Creating virtual volumes Dynamic Provisioning 5 24 Use the following provisioning operations to create LDEVSs of virtual vo
36. Remote node Volume Volume Takeover action attribute fae a eE attribute SMPL Reject P VOL status P VOL Nop takeover S VOL Unconformable Unknown Reject P VOL Fence Dataor SMPL Reject primary Status amp amp pair P VOL status PSUE or Unconformable PDUB or MINAP S VOL PVOL Takeover2 0 Unknown PVOL Takeover2 Others SMPL Reject P VOL Unconformable S VOL Nop takeover Unknown Nop takeover Status SSWS Nop takeover After SVOL_SSUStakeov er Other than SSWS Unconformable PAIR or PFUL Swap takeover Others SVOL takeover S VOL Unconformable Unknown 7 SVOL takeover 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 is accepted Personality swaps must be accomplished in another way 6 12 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Unconformable A pair of volumes are not conformable to each other as a pair that is one P VOL one S VOL The takeover command execution terminates abnormally Reject The takeover command is rejected and the operation terminates abnormally Unknown The attribute of the remote node is unknown and cannot be identified This means that the remote node system has gone down or cannot commun
37. Status state of disconnected Troubleshooting 9 25 Hitachi Command Control Interface User and Reference Guide raidcom check_ext_storage path Error code Executing Async sspi ssB2 Error message Description Get Command Async All the paths for the specified external path are Status blocked CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Async There is no specified external volume Status Get Command Async There is no specified path Status CMDRJE CMDRJE Executing WWYN is not registered CMDRJE Executing The path group is not registered Executing CMDRJE Executing The path group does not exist Get Command Async Online from the mainframe host Status CMDRJE Executing The port attribute is not External ELUN CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Async An internal error occurred by the operation of Status external path Call Hitachi Data Systems Support Center Table 9 11 SSB codes that are returned by raidcom disconnect external_grp command raidcom disconnect external_grp Executing Error code Error message Async sspi ssB2 Description Executing The external volume group is not in the effective range Executing The specified LDEV is used as a ShadowImage pair Executing It is used as
38. The TrueCopy local commands perform the same functions as the remote commands but within the same RAID storage system instead of between two RAID storage systems Data replication operations with CCI 6 17 Hitachi Command Control Interface User and Reference Guide Operation Management Server software Command device Primary secondary volume Pair generation and re synchronization Pair splitting Figure 6 8 TrueCopy local system configuration TrueCopy ShadowImage and Universal Replicator operations TrueCopy ShadowImage volumes 6 18 TrueCopy commands allow you to create volume pairs consisting of one primary volume P VOL and one secondary volume S VOL The TrueCopy P VOL and S VOL can be in different storage systems TrueCopy provides synchronous and asynchronous copy modes TrueCopy Async can only be used between separate storage systems not within one storage system For details on TrueCopy specifications volumes and operations please see the Hitachi TrueCopy User Guide for your storage system ShadowImage commands allow you to create volume pairs consisting of one P VOL and up to nine S VOLs using the ShadowImage cascade function ShadowImage pairs are contained within the same storage system and are maintained using asynchronous update copy operations For details on ShadowImage specifications volumes and operations please see the Hitachi ShadowImage User Guide for your storage system Each vol
39. The operation failed because the multiple LDKC numbers cannot be mixed in the journal 9 37 Hitachi Command Control Interface User and Reference Guide raidcom add journal Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The operation failed because the number of journals in the journal or the extended CT group exceeds the maximum CMDRJE Get Command Status Executing Async The specified volume cannot be used as a journal volume because it is set by Cache Residency Manager or Cache Residency Manager for Mainframe CMDRJE Get Command Status Executing Async The specified volume cannot be used because it is used in FICON R Data Migration CMDRJE Get Command Status Executing Async A path is defined in the specified volume CMDRJE Get Command Status Executing Async The operation failed because the specified volume is a Quorum disk CMDRJE Get Command Status Executing Async The specified volume cannot be used as a journal volume because it is a system disk Get Command Status Async The operation failed because the specified volume is a pool volume of Dynamic Provisioning Get Command Status CMDRJE Async Executing The specified volume is already used as a journal volume or a data volume CMDRJE Get Command Status Executing Async The specified volume is us
40. The same device name must not be defined for any LDEVs in a specified device group A copy group can be created whether the LDEV in the device group is paired status or not e Use cases The following shows use cases that can be created a copy group o Creating a copy group in cases where two device groups are configured of simplex volumes and the device names and the LDEV numbers in the respective device groups are the same In the following example when a copy group is created the LDEVs within the device names of A to A and B to B become a subject of pair operation o Creating a copy group in cases where two device groups are configured of paired volumes and the device names and the LDEV numbers in the respective device groups are the same In the following example although pairs have been created on the device names of A to A and B to B a copy group can be created 3 36 CCI functions Hitachi Command Control Interface User and Reference Guide LDEV addition to a copy group Adding an LDEV to a device group by specifying a device group name forming a copy group It is 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 group cannot be performed e Use cases The following shows use cases that can be added an LDEV to the device group associating a copy group o Adding an LDEV with a different device name simplex volume to a
41. external_wwn 50060e80 16114870 lun_id 0 raidcom get command_status raidcom reset command_status Log in with user ID USEROI and password gt PASSOI Lock the resource group meta_resource Change the attribute of Port CL3 A to Port External ELUN and of Port CL4 A to External ELUN Display the port on the external storage gt from port CL3 A Display LU that is defined to the port on the external port 50060e80 1611a870 and connected to the port CL3 A External port Map LU O that is defined to the port on the zexternal port 50060e80 1611a80 and cconnected to the port CL3 A External port with the external volume group l 1 path group 1 Figure 5 13 Script Examples of External Volume Operation 1 3 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide raidcom modify external_grp external_grp_id I 1 cache_mode y raidcom get external _grp external grp id 1 1 Turn ON the cache mode of External volume group 1 1 Specify the external volume group and display the external volume information raidcom add path path_grp port CL4 A external_wwn 50060e80 O5faf36 raidcom get conmand_status raidcom reset command status raidcom get path path_grp raidcom modify port port CLI A security _switch y raidcom modify port port CL2 A security _switch y raidcom add host_grp port CLI A host_grp_name HP UX P raidc
42. fc option of the pairdisplay command indicates 0 1 The 2 to 4 state change is effective for only the COPY state that is changed without specification of split for paircreate command 2 The 2 to 4 state change appears as P VOL_PSUS amp S VOL_COPY see example below and reading and writing are enabled for S VOL in SVOL_COPY state pairsplit g oradb pairdisplay g oradb fc Group PairVol L R Port TID LU M Seq LDEV P S Status P LDEV M oradb oradev3 L CL2 N 3 4 0 8071 28 P VOL PSUS 100 29 W oradb oradev3 R CL2 N 3 5 0 8071 29 S VOL COPY 97 28 PVOL_PSUS amp SVOL_COPY is the non reflected PSUS state that data is still being copied from the P VOL to the S VOL and this state has the following specific behavior 6 23 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide e If you attempt to read non reflected data on S VOL in PVOL_PSUS amp SVOL_COPY state then ShadowImage copies non reflected data from P VOL to S VOL and returns the correct data after copied This will bring the performance degradation 1 6 to 1 15 with IOPS to read on the S VOL e If you attempt to write non reflected data on S VOL in PVOL_PSUS amp SVOL_COPY state then ShadowImage copies non reflected data from P VOL to S VOL and writing data is managed as delta data for S VOL after copied This will bring the performance degradation 1 6 to 1 8 with I
43. gt lt host group name gt ldev_id lt Idev gt lun_id lt lun gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt e raidcom delete lun port lt port gt lt host group name gt lun_id lt lun gt ldev_id lt ldev gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt Check with the deletion operation It is checked to ensure that the operation is not intended to be performed for the LDEV that is already deleted If it is an error is detected If it is not clear whether the LDEV as the target of the operation exists in the configuration definition file or not if the target LDEV information does not exist in the configuration definition file the error is not detected The command as the target of the check is shown below e raidcom delete ldev ldev_id lt ldev gt grp_opt lt group option gt device_grp name lt device group name gt lt device name gt The example of the script where the same LDEV is attempted to be added to the already created LDEV and the execution result of the Context check is shown below e Example of script raidcom add ldev parity_grp_id 01 01 ldev_id 1 capacity 100M raidcom add ldev parity_grp_id 01 01 ldev_id 2 capacity 100M raidcom add ldev parity_grp_id 01 01 ldev_id 3 capacity 100M e Execution result CCI functions Hitachi Command Control Interface User and
44. lt port gt system lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt Register a host to host raidcom add hba_wwn port lt port gt lt host group group name gt hba_wwn lt WWN strings gt Delete host group raidcom delete host_grp port lt port gt lt host group name gt Display host group raidcom get host_grp port lt port gt information lt host group name gt Port Set port raidcom modify port port lt port gt port_speed see the Provisioning lt value gt loop_id lt value gt topology lt topology gt security_switch lt y n gt Guide for the storage system Set port attribute raidcom modify port port lt port gt port_attribute lt port attribute gt Display port information raidcom get port port lt port gt 5 6 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation type Internal volume see the Provisioning Guide for the storage system Description Create LDEV Corresponding command raidcom add ldev parity_grp_id lt gno sgno gt external _grp_id lt gno sgno gt pool lt pool ID gt lt pool naming gt snap ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Display LDEV information rai
45. mirror descriptor is used for connection of the S VOL The mirror descriptor MU 0 2 can be used in ShadowImage and Copy on Write Snapshot MU 3 63 can be used in Copy on Write Snapshot only SMPL P VOL Feature MU 0 2 MU 3 63 MU 0 2 MU 3 63 ShadowImage Valid Not valid Valid Not valid Valid Not valid Copy on Write Valid Valid Valid Valid Valid Not valid Snapshot CCI software environment 2 21 Hitachi Command Control Interface User and Reference Guide 2 22 e MU for TrueCopy UR Defines the mirror unit number 0 3 to use the redundant mirror for the identical LU on TrueCopy UR If this number is omitted it is assumed to be zero 0 The UR mirror description is described in the MU column by adding h in order to identify identical LUs as the mirror descriptor for UR The MU for TrueCopy must be specified only 0 TrueCopy has only one mirror description but UR has four mirrors as shown below Feature Valid Not valid Valid Not valid Valid Not valid Valid Valid Valid Valid Valid Valid 4 HORCM_INST The instance parameter HORCM_INST defines the network address IP address of the remote server active or standby It is used to view or change the status of the paired volume in the remote server active or standby When the primary volume is shared by two or more servers there are two or more remote servers using the secondary volume Thus it i
46. mp_blade_id lt mp gt Displaying LDEV information Display information of created LDEV and confirm the result of executing the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt Creating pool for Dynamic Provisioning Create pool for Dynamic Provisioning raidcom add snap_pool pool_id lt pool ID gt pool_ name lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool_ name lt pool naming gt ldev_id lt ldev gt cnt count gt user_ threshold lt gt Setting pool option Modify pool for Dynamic Provisioning to pool for Dynamic Tiering raidcom modify pool pool lt pool ID gt lt pool naming gt pool_attribute dt_manual Adding different media to pool volume Add a pool volume of different media to a pool for Dynamic Tiering raidcom add dp_ pool pool_id lt pool ID gt pool_ name lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool_ name lt pool naming gt ldev_id lt ldev gt cnt lt count gt user_threshold lt threshold_1 gt lt threshold 25 Creating LDEV V VOL Specify pool and create LDEV V VOL Provisioning operations with CCI raidcom add ldev pool lt pool ID gt lt pool naming gt snap ldev_id lt ldev gt capacity lt
47. raidcom EX _ENAUTH Authentication failed with User Aug 24 12 24 27 raidmanager raidcom PID 06857 raidcom exit 202 User created files CCI supports scripting to provide automated and unattended copy operations A CCI script contains a list of CCI commands that describes a series of TrueCopy and or ShadowImage operations The scripted commands for UNIX based platforms are defined in a shell script file The scripted commands for Windows based platforms are defined in a text file The host reads the script file and sends the commands to the command device to execute the TrueCopy ShadowImage operations automatically The CCI scripts are e 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 e HORCM shutdown script horcmshutdown sh horcmshutdown exe A script for stopping the HORCM etc horcmgr e HA control script A script for executing takeover processing automatically when the cluster manager CM detects a server error When constructing the HORCM environment the system administrator should make a copy of the horem conf file The copied file should be set according to the system environment and registered as the following file is the instance number UNIX systems etc horcm conf or etc horcm conf Windows systems Yowindir horcm conf or windir
48. system When a CCI HORCM or HDS feature failure is detected please collect the data in the error log file and trace data all files in HORCM_LOG directory and report the failure to your HDS representative Items Notes and restrictions Startup shutdown When the server starts up the secondary volume may be updated restrictions by the primary volume s server The secondary volume must not be mounted automatically in the startup sequence If the secondary volume is used by the LVM the volume group of the LVM must be deactivated The secondary volume must be mounted in the split state or in the simplex mode When the server starts up the secondary volume can be activated without confirming when can be guaranteed that the secondary volume has been PSUS R W enable or in the SMPL state by server shutdown sequence Hot standby TrueCopy commands cannot execute hot standby operations operations between the primary and secondary volumes Use the takeover command intended for the HA configuration to execute the hot standby operation In hot standby operation two servers are used and the active primary and standby secondary server programs are run alternately in each server in case of a failure in one server Follow these precautions e Operation across volumes Since each TrueCopy command causes the server software to handle the volume by volume a single volume should not be partitioned to prevent it from being used by some server
49. the syslog file CCI software environment 2 41 Hitachi Command Control Interface User and Reference Guide e Setting commands e raidcom get command status e Authentication commands performing the authentication command at the prompt also becomes the target However if the command is not issued to the DKC by detecting the raidcom command execution error beforehand the command becomes out of target even if it falls under the above items Output setting for the syslog file A syslog file is output when 1 is set on the RAIDCOM_SYSLOG of environment variables The syslog file is not output at the stage of initial setting How to set the syslog conf The contents that can be set on the syslog conf for the environment setting may vary in each OS However set basically according to the syslog conf described in the following Setting example It may vary by the host OS e Client side extracts user info var log raidcomuser err var log raidcom erruser info host1234user err host1234 e Server side extracts user info var log raidcomuser err var log raidcom err You can record the same log at the client side by considering the lost of syslog at the syslog server In this case add the following settings e facility user e level info err info for the normal command operation err for the abnormal command operation Syslog file display information Three kinds of information for one raidcom command
50. user defined e User execution environments for the HDS features including the commands a command log and a monitoring function The CCI commands also have interface considerations see CCI and the SCSI command interface on page 2 6 CCI components on the RAID storage system Command device CCI commands are issued by the CCI software to the RAID storage system command device The command device is a user selected dedicated logical volume on the storage system that functions as the interface to the CCI software on the host The command device is dedicated to CCI communications and cannot be used by any other applications The command device accepts CCI read and write commands that are issued by the storage system The command device also returns read requests to the host The volume designated as the command device is used only by the storage system and is blocked from the user The command device uses 16 MB and the remaining volume space is reserved for CCI and its utilities The command device can be any OPEN x device for example OPEN V that is accessible to the host A LUN Expansion volume cannot be used as a command device A Virtual LVI Virtual LUN volume as small as 36 MB for example OPEN 3 CVS can be used as a command device WARNING Make sure the volume to be selected as the command device does not contain any user data The command device will be inaccessible to the host The CCI software on the host issues re
51. 29 do raidcom get Idev Idev_id 10 cnt 20 for I S i in 10 1 19 do raidcom add device_grp device_grp_name grpl data i Idev_id bi for I i in 20 1 29 do raidcom add device_grp device_grp_name grp2 data i Idev_id bi raidcom get command_status raidcom reset command status raidcom get device_grp device_grp_name grpl raidcom get device_grp device_grp_name grp2 raidcom add copy_grp copy_erp_name ora erpl grp2 raidcom get command_status raidcom reset command_status gt Set the LDEV MP Blade ID of LDEV 0 to 9 to 2 Display the information of LDEV 0 to 9 Internal VOL Create Pool 1 by using LDEY 0 to 9 Create each 10 of 10G WOL to Pool_id 1 gt LDEV 10 to 19 20 to 29 Give a nickname to WOL 10 to 29 gt my_virtual_volume 10 to 29 r l Set the VVOL MP Blade ID of VVOL 10 to 29 to raidcom modify Idev Idev_id bi mp_blade_id 2 9 Display the information of WOL 10 to 29 virtual VOL Give the device name data 10 to 29 to VVOL 710 to 29 and add it to the device group name grpl datal0 to 19 and grp2 data20 to 29 Display the device group information grp and cgrp2 Create a copy group ora with the device group grpl and grp2 Figure 5 6 Script examples of virtual volume operation Dynamic Provisioning 2 3 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide raidcom get
52. 64539 50060e8006fc1b41 CL6 A FIBRE TAR AUT D5 N FCAL N O 64539 50060e8006fc1b50 CL6 B FIBRE TAR AUT DI N FCAL N O 64539 50060e8006fc1b51 CL7 A FIBRE ELUN AUT E2 N FCAL N O 64539 50060e8006fc1b60 CL7 B FIBRE ELUN AUT DA N FCAL N O 64539 50060e8006fc1b61 CL8 A FIBRE TAR AUT 64539 50060e8006fc1b70 CL8 B FIBRE TAR AUT CE N FCAL N O 64539 50060e8006fcib71 C HORCM etc gt raidcom zt 4_no_port bat load portcnf_27 dat checkmode precheck C HORCM etc gt raidcom add path path_grp 1 port CLi C external_wwn 50060e80 06fc4180 raidcom PORT 2 does not exist as status is 2 on UnitID 0 raidcom_ 2 EX_CTXCHK Context Check error C HORCM etc gt raidcom add path path_grp 1 port CL1 D external_wwn 50060e80 06fc4190 raidcom PORT 3 does not exist as status is 2 on UnitID 0 raidcom_ 3 EX_CTXCHK Context Check error C HORCM etc gt raidcom add path path_grp 1 port CL1 E external_wwn 50060e80 06fc41a0 raidcom PORT 4 does not exist as status is 2 on UnitID 0 raidcom_ 4 EX_CTXCHK Context Check error iw A Z pu O gt a Host group check The check is performed from the following perspective Note that checking for an attribute of host group or for a name of host group is not executed Check with the attribute setting Checks whether the operation is performed for an existing host group If the host group does not exist an error is detected If it is not clear whether the target port or host group
53. A file for management HORCM etc Raidcom_Dic_Raid_RM txt Tool HORCM Tool chgacl exe chgacl Tool HORCM Tool svcexe exe svcexe Sample script for svcexe HORCM Tool HORCMO_run txt Tool HORCM Tool TRCLOG bat TRCLOG Storage Replication Adapter HORCM etc rmsra exe rmsra Takeover HORCM usr bin horctakeover exe horctakeover Accessibility check HORCM usr bin paircurchk exe paircurchk Pair generation HORCM usr bin paircreate exe paircreate Pair split HORCM usr bin pairsplit exe pairsplit Pair re synchronization HORCM usr bin pairresync exe pairresync Event waiting HORCM usr bin pairevtwait exe pairevtwait Volume check HORCM usr bin pairvolchk exe pairvolchk Synchronous waiting HORCM usr bin pairsyncwait exe pairsyncwait Pair configuration confirmation HORCM usr bin pairdisplay exe pairdisplay RAID scanning HORCM usr bin raidscan exe raidscan Connection confirmation HORCM usr bin raidqry exe raidqry Oracle Validation setting HORCM usr bin raidvchkset exe raidvchkset Oracle Validation confirmation HORCM usr bin raidvchkdsp exe raidvchkdsp Oracle Validation confirmation HORCM usr bin raidvchkscan exe raidvchkscan Configuration setting and confirming command HORCM usr bin raidcfg exe raidcfg Note AN e The HORCM etc commands are used from the console window If these commands are executed without an argument the interactive mode will start up e The HOR
54. CLPRs Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify clpr Error code Error message eae di Description sync ssBi SSB2 CMDRJE Executing 2E00 1300 The item cannot be migrated to another CLPR because of either reason below e The specified parity group or external volume group has an LUSE volume e The specified volume is an LUSE volume CMDRJE Executing 2E00 7000 The specified CLPR number is invalid CMDRIJE Executing 2E11 810A Abnormal cache status CMDRJE Executing 2E13 0101 The CLPR cannot be migrated because the specified parity group or the external volume group includes the pool volume that is used in the pool for Thin Image or Copy on Write Snapshot CMDRJE Executing 2E20 0000 LDEV is not installed CMDRJE Executing 2E20 0100 There is no parity group CMDRJE Executing 2E20 4100 There is no external volume group CMDRJE Executing 2E20 7001 The specified CLPR is not installed CMDRJE Executing 2E30 0005 CLPR cannot be transferred by either one of the following two reasons e Cache Residency Manager is set for the specified volume e The specified parity group includes the volumes for which Cache Residency Manager are set CMDRJE Executing 2E30 OOOF The specified LDEV is used as a journal volume CMDRJE Executing 2E30 0083 The specified parity group includes HDEV with the journal attribute CMDRJE Executi
55. CTG CM EM E Seq E LDEV horc0 62496 18 SMPE jnne ape ete ye horcdO 62496 19 SMPL ase SS H 30053 30 paircreate g horcO vl m cc During execution of Volume Migration command the progress is displayed in the copy pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV horc0 62496 18 P VOL COPY 62496 Lg C 7 horcO 62496 19 S VOL COPY 18 H 30053 30 After completion of Volume Migration command Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV horcO 62496 18 P VOL PSUS 62496 19 Cc v 30053 30 horcO 62496 19 S VOL SSUS 18 Cc CM Displays the copy mode N Non Snapshot S Snapshot For SMPL state this shows that pair volume will be created as Copy on Write Snapshot C Volume Migration EM Displays the external connection mode H Mapped E lun as hidden from the host V Mapped E lunas visible tothe host Unmapped to the E lun BH Mapped E lun as hidden from the host but LDEV blockading BV Mapped E lun as visible to the host but LDEV blockading B Unmapped to the E lun but LDEV blockading E Seq Displays the production serial number of the external LUN Unknown is shown as E LDEV Displays the LDEV of the external LUN Unknown is shown as 4 Comm
56. Control Interface User and Reference Guide A alternate command device 2 5 defining 2 6 asynchronous commands list of provisioning 5 4 processing 1 3 5 3 authorities for commands and operations 3 9 C cascading connections and configuration files 2 26 configuration files 2 29 cascading pairs 6 7 cascading volume pairs definition 2 25 cascading volumes restrictions 6 8 CCI functions 1 2 cluster manager 6 10 command device 2 2 alternate 2 5 guarding 2 3 instance number 2 4 command execution modes 3 15 command parameter HORCM_CMD 2 16 commands authorities 3 9 error logging for audit 2 39 error messages and troubleshooting 9 8 examples 8 1 execution modes 1 4 in band execution 3 2 out of band execution 3 2 processing asynchronously 5 3 processing synchronously 5 3 configuration check 3 24 configuration definition file 2 12 examples 2 13 configuration definition file settings 2 15 2 16 cascading connections 2 26 2 29 cascading volume pairs 2 25 dev_name 2 18 HORCM_DEV 2 20 Index HORCM_INST 2 22 HORCM_LDEV 2 23 HORCM_LDEVG 2 24 HORCM_MON 2 15 configuration file parameters 2 14 configuration file parameters 2 14 configuration setting commands raidcom 1 3 consistency groups 6 25 copy groups 3 29 defining 3 35 deleting 3 38 deleting LDEV 3 37 D data protection 1 9 command compatibility 7 9 configuration examples 7 7 defining command device 7 14 environment variables 7 14 facility 7 5 parameter
57. Control Interface User and Reference Guide CCI files supplied with the software e CCI files for UNIX based systems on page 2 32 e CCI files for Windows based systems on page 2 33 e CCI files for OpenVMS based systems on page 2 35 CCI files for UNIX based systems HORCM File name etc horcmgr Command name horcmd HORCM_CONF HORCM etc horcm conf Takeover usr bin horctakeover horctakeover Accessibility check usr bin paircurchk paircurchk Pair generation usr bin paircreate paircreate Pair splitting usr bin pairsplit pairsplit Pair resynchronization usr bin pairresync pairresync Event waiting usr bin pairevtwait pairevtwait Error notification usr bin pairmon pairmon Volume check usr bin pairvolchk pairvolchk Pair configuration confirmation usr bin pairdisplay pairdisplay RAID scanning usr bin raidscan raidscan RAID activity reporting usr bin raidar raidar Connection confirming usr bin raidqry raidqry Trace control usr bin horcctl horcctl HORCM activation script usr bin horcmstart sh horcmstart sh HORCM shutdown script usr bin horcmshutdown sh horcmshutdown sh Connection confirming HORCM usr bin ingraid Synchronous waiting usr bin pairsyncwait pairsyncwait Configuration setting and confirming command HORCM usr b
58. Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 3 A way to import with horcmstart sh on CCI host Example 1 for exporting ls dev rdsk clt inqraid CLI export ssh lt CCI host gt cat gt etc horcmperm conf OR Example 2 for exporting ls dev rdsk cit inqraid CLI export gt tmp ingraid ex ftp tmp ingraid ex to etc horcmperm conf on CCI host This example for importing on CCI host executes horcmstart sh on the CCI host where is the instance number Display example for verifying on CCI host cat etc horcmperm conf raidscan find verify DEVICE FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c1t0d0s2 64015 0 dev rdsk c1t0d1s2 a a 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 c1 t0d4s2 sE 64015 4 dev rdsk c1 t0d5s2 2 64015 5 dev rdsk c1t0d7s2 oa 64015 7 pairdisplay g G1 fd 1 Group PairVol L R Device File Seq LDEV P S Status Fence Seq P LDEV M G1 G1 000 L c1t0d2s2 64015 2 SMPL G1 G1 001 L c1t0d3s2 64015 3eSMPL ssmimi Data replication operations with CCI 6 57 Hitachi Command Control Interface User and Reference Guide 6 58 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Data protection operations wi
59. ELBA 0x013fffdf PCNT 2 OPEN V Harddisk12 SLBA 0x00000022 ELBA 0x013fffdf PCNT 3 OPEN V SLBA displays usable starting LBA in units of 512 bytes ELBA displays usable ending LBA ELBA 1 in units of 512 bytes PCNT displays the number of partitions Directory mount facility for Windows systems The attached mountvol command into Windows supports the directory mount but it does not support the directory mount function that flushes the system buffer associated to a logical drive such as in UNIX systems The directory mount structure on Windows is only symbolical link between a directory and Volume guid illustrated in Figure 8 5 Directory mount structure on page 8 13 below As such CCI supports the function to discover the mounted volumes by a directory and supports the operation to mount unmount with the subcommand option 8 12 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide Logical Drive Volume quid Volume guid Volume quid LDM wll Volumes Device Device Device HarddiskVolume2 Harddisk Volumes HarddiskVolume Physical Device Device Device Volumes Harddisk HarddiskO Harddisk Figure 8 5 Directory mount structure Volume discovery for directory mounted volume CCI can discover the directory mounted volume by using LETALL that shows the relationship between logical drive and the physical volumes The KEY WORD LETALL can also be used with
60. Idn jen fn Ign hn jn Ikn in mn pn qn For 9900V CCI supports four types of port names for host groups CCI software environment Hitachi Command Control Interface User and Reference Guide o 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 o Specifying the port name with a host group CL1 A g where g is the host group CL1 An g where n g is the host group g on CL1 A in unit ID n The following ports can be specified for USP V VM and TagmaStore USP TagmaStore NSC e Target ID Defines the SCSI fibre target ID TID number of the physical volume on the specified port e LU Defines the SCSI fibre logical unit number LU of the physical volume on the specified target ID and port Note In case of fibre channel if the TID and LU displayed on the AN system are different than the TID on the fibre address conversion table then you must use the TID and LU indicated by the raidscan command in the CCI configuration file e MU for ShadowImage HOMRCF Defines the mirror unit number 0 2 to use the redundant mirror for the identical LU on the ShadowImage If this number is omitted it is assumed to be zero 0 The cascaded mirroring of the S VOL is expressed as virtual volumes using the mirror descriptors MU 1 2 in the configuration definition file The MU 0 of a
61. LDEV belongs is used in another operation Get Command Status Async The operation of Dynamic Provisioning V VOL cannot be done because there is a blocked pool Get Command Status Async The operation of Dynamic Provisioning V VOL cannot be done because there is a blocked pool volume Get Command Status Async The operation cannot be done because the internal processing is in progress CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async The processing stopped because aborting processing is required CMDRJE Executing LDEV is not installed CMDRJE Executing The program product is not installed Get Command Status Async The quick format cannot be performed because the total number of parity groups in which the LDEVs in quick formatting or the LDEVs blocked while quick formatting are implemented exceeds the maximum number that can be performed at the same time Get Command Status Troubleshooting The specified LDEV is used as a Dynamic Provisioning 9 43 Hitachi Command Control Interface User and Reference Guide raidcom initialize Idev Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The specified LDEV is used as a quorum disk CMDRJE Get Command Status Executing Async The specifie
62. OK OK OK OK Mirroring Mirroring Mirroring Data consistency consistency consistency consistency assured assured assured assured Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 6 31 TrueCopy pair status of volume Write response Not Valid F Primary volume Secondary volume Fence level and write response Data 1 ERROR Status 2 OK Never 3 OK Async 4 OK Mirroring consistency assured Mirroring consistency not assured Mirroring consistency not assured Data consistency assured Write response Not Valid ERROR ERROR OK OK Mirroring consistency assured Mirroring consistency assured Mirroring consistency not assured Data consistency assured i Primary volume Secondary volume 1 When the fence level is data Mirroring consistency is assured since a write error is returned if mirror consistency with the remote S VOL is lost The secondary volume can continue operation regardless of the status Note A P VOL write that discovers a link down situation will in addition to returning an error to the host likely be recorded on only the P VOL side 2 When the fence level is status If there is a mirror consistency problem that is PSUE and it is possible to set the S VOL to PSUE the P VOL write completes OK If the S VOL cannot be set to PSUE for any reason the P VOL write c
63. Pool 1 by using LOEW O to 9 sCreate 10 of 3420 cylinder VWOL to Pool 1 CLDEW 10 te 19 Give a nickname to VOL 10 to 29 sEm _wirtual_ volume 10 to 29 2 Figure 5 8 Script examples of virtual volume operation Dynamic Provisioning for Mainframe 1 2 Provisioning operations with CCI 5 31 Hitachi Command Control Interface User and Reference Guide for 1 XXi in 10 1 29 do sSet the VOL MF Blade 1D of WOLI10 to 9 to raideom modify Idew Idev_id AAG mp_blade_id 2 32 raidcom get Idey Idevlid 10 cnt 20 j0 isplay the information of VWOL 10 to s29Cvirtual VOL P raidcom unlock resource resource grp name Unlock the resource group meta_resour ce Weta eS oUF ce E z raidcom get resource 3D isplay the resource group information raidcoam logout sLog out Figure 5 9 Script examples of virtual volume operation Dynamic Provisioning for Mainframe 2 2 Virtual volume Dynamic Tiering operations Operational flow 5 32 When using the V VOL Dynamic Tiering tiers of pools must be created after creating pools and then the performance of pools must be monitored before the operation If the performance of pools are insufficient extend the capacity of pool volumes addition of pool volumes and of the V VOL The following diagram shows the flow of work to use a virtual volume Dynamic Tiering when operating with GUI Storage Navigator or CCI Provisioning operations with CCI Hitachi Command Control I
64. Protection parameters and operationS 0 0 0 ees 7 5 Data Protection facility 1 0 0 eee es 7 5 Data Protection Facility specifications 1 sasaaa naaa 7 6 Examples for configuration and protected volumeS 0000 7 7 Operation authority with CMD security enabled 00055 7 9 Target commands for protection 1 0 ce es 7 9 permission command saasaa asana anaana es 7 10 New options for security 2 0 cee ees 7 10 raidscan find inst 62s ee dd oo eee see deeet eases a esecoe ee ae 7 10 raidscan find verify MU 0 0 0 ce es 7 10 viii Hitachi Command Control Interface User and Reference Guide raidscan f d ote 22 sk ow cee aes ws Cece ne oes oe cotaes 7 11 pairdisplay f d osed debaweeincdad wine lt teve ces dete ed 7 11 Permitting protected volumes 0 0 ees 7 11 With a HORCMPERM file 2 0 0 0 eee ee eee 7 12 Without a HORCMPERM file Commands to run on different operating SYSICING asi ee er o oe area eetird ap ete ease erate eee 7 13 Environment variables a na aaan aaan aaan aaa 7 14 HORCMPROMOD saunaan anaana nannan ean 7 14 SHORCMPERM a earen a a a a ook oe e 7 14 Determining the protection mode command device a s a suasanana 7 14 8 Examples of using CCI commands ssaa asanarea 8 1 Group version control for mixed storage system configurations 8 2 LDM volume discovery and flushing for Windows 0 eee eee 8 2 Volume disc
65. Reference Guide Operation type Device group raidcom Commands get device_grp Operation target when you specify the virtual storage machine VSP G1000 raidcom add device_grp VSP G1000 raidcom delete device_grp VSP G1000 External volume group raidcom get external_grp VSP G1000 raidcom add external_grp VSP G1000 raidcom delete external_grp VSP G1000 raidcom modify external_grp VSP G1000 raidcom disconnect external_grp VSP G1000 Host group raidcom get host_grp VSP G1000 raidcom add host_grp VSP G1000 raidcom delete host_grp VSP G1000 raidcom modify host_grp VSP G1000 raidcom get hba_wwn VSP G1000 raidcom add hba_wwn VSP G1000 raidcom set hba_wwn VSP G1000 raidcom reset hba_wwn VSP G1000 raidcom get journal VSP G1000 raidcom add journal VSP G1000 raidcom delete journal VSP G1000 raidcom modify journal VSP G1000 raidcom get Idev Virtual storage machine raidcom add Idev VSP G1000 raidcom delete Idev VSP G1000 raidcom modify Idev VSP G1000 raidcom extend Idev VSP G1000 raidcom initialize Idev VSP G1000 raidcom get lun Virtual storage machine raidcom add lun Virtual storage machine raidcom delete lun Virtual storage machine
66. Resets the error information of asynchronous command in the storage system 2 Execute an asynchronous command Executes the asynchronous command 3 Execute a raidcom get command_status command Checks if all the asynchronous command processing are done or if no error is occurred Provisioning operations with CCI 5 3 Hitachi Command Control Interface User and Reference Guide Asynchronous commands The asynchronous commands associated with the configuration setting command provide provisioning functions The table lists the functions performed by asynchronous commands and describes the required syntax Table 5 1 Asynchronous commands of the configuration setting command Function Command syntax Blocking an LDEV raidcom modify Idev ldev_id lt Idev gt status blk Adding an LDEV raidcom add Idev parity_grp_id lt gno sgno gt external_grp_id lt gno sgno gt pool lt pool ID gt lt pool naming gt snap Idev_id lt Idev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt Iba gt mp_blade_id lt mp gt Deleting an LDEV raidcom delete Idev ldev_id lt ldev gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt LDEV Quick Format raidcom initialize Idev ldev_id lt ldev gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name
67. Snapshot pair Executing A Thin Image or Copy on Write Snapshot pair cannot be created because the volume of Universal Replicator for the delta resync is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A Thin Image or Copy on Write Snapshot pair cannot be created because the volume of Universal Replicator for the delta resync is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Quorum disk is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Quorum disk is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A Thin Image or Copy on Write Snapshot pair cannot be created because the Dynamic Provisioning V VOL in capacity expanding is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A Thin Image or Copy on Write Snapshot pair cannot be created because the Dynamic Provisioning V VOL that is discharging zero data is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the P VOL of a TrueCopy pair is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the S VOL of a TrueCopy pair is specified as the S VOL of a Thin Image or Copy on Write
68. Snapshot pair Executing The command ends abnormally because the ShadowImage pair is being resynchronized when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a ShadowImage pair Executing The command ends abnormally because the ShadowImage pair status is other than PSUS when the volume is shared between P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a ShadowImage pair Executing The operation cannot be performed because the Quick Restore is being operated on the specified ShadowImage P VOL Troubleshooting 9 63 Hitachi Command Control Interface User and Reference Guide raidcom add snapshot Executing Async Error message Executing Error code SSB1 SSB2 Description A pair operations cannot be performed because the volume using 2 mirrors included in the 3DC multi target configuration 3DC cascade configuration or 3DC delta resync configuration by the 3 Universal Replicator sites is specified Executing A Thin Image pair cannot be created because the pair status of all Thin Image pairs sharing the specified P VOL is PSUE Executing A Thin Image pair cannot be operated because the virtual storage machine of the P VOL is different from the virtual storage machine of the S VOL Executing A Thin Image pair cannot be operated because changing the model and the serial number in the virtual
69. Status and external volumes because the pool is not set to Mixable Get Command Async 2E31 9000 The usage capacity exceeds the license capacity Status of program product CMDRJE Executing 2EE7 OOEE The command cannot be accepted After a while execute the same command CMDRJE Executing 2EE7 FEEC An internal error occurred Get Command Async Call Hitachi Data Systems Support Center Status Table 9 45 SSB codes that are returned by raidcom modify rcu command raidcom modify rcu Error message Executing Async Executing Error code SSB1 SSB2 Description CU of RCU exceed the effective value Executing The value of least path number is invalid Executing The value of RIO MIH time is invalid Executing The value of Round trip response time is invalid Executing Troubleshooting Invalid product ID or path registration ID 9 77 Hitachi Command Control Interface User and Reference Guide raidcom modify rcu Error code Error message se Description sync ssBi SSB2 CMDRJE Executing 2E00 3007 Incident that is created by CU is not in the one of followings Incident that is sent to MCU host and RCU Incident that is sent to RCU Get Command Async 2E00 3008 Command cannot be executed because the Status parameter of specified RCU is invalid Get Command Async 2E00 3009 Command cannot be executed because all the
70. The specified LDEV is not installed Get Command Status Async The specified LDEV is used as a Dynamic Provisioning Get Command Status Async The specified LDEV is used as a quorum disk Get Command Status Async The specified LDEV is used as a pool volume Get Command Status Async The specified LDEV is used as a reserved volume of Volume Migration Get Command Status Async Volume Security is set to the specified LDEV Get Command Status Async The specified LDEV cannot be restored because the shredding or the formatting operation has not been performed Get Command Status Async The specified LDEV is a Data Retention Utility Volume Retention Manager attribute device Get Command Status Async LDEV cannot be restored because there is no connection path to the normal external path CMDRJE Executing Troubleshooting The command cannot be accepted After a while execute the same command 9 47 Hitachi Command Control Interface User and Reference Guide Table 9 28 SSB codes that are returned by raidcom modify Idev status blk command raidcom modify Idev status blk Error code Error message ae Description syne SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceed the range of LDEV number Get Command Async 2E10 0000 The specified LDEV is used as a
71. Tiering raidcom modify ldev ldev_id lt ldev gt status discard_zero_ page Display the information of a pool for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering raidcom get dp pool key lt keyword gt Display the information of a pool for Copy on Write Snapshot raidcom get snap_pool Extend the capacity of a pool for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering Provisioning operations with CCI raidcom add dp pool pool_id lt pool ID gt pool_name lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool_name lt pool naming gt ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp name lt device group name gt lt device name gt user_threshold lt threshold_1 gt lt threshold_ 25 Hitachi Command Control Interface User and Reference Guide Operation type Description Extend the capacity of a pool for Copy on Write Snapshot Corresponding command raidcom add snap_pool pool_id lt pool ID gt pool_ name lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool_name lt pool naming gt ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp_ name lt device group name gt lt device names user_threshold lt gt
72. WWN of host path adapter raidcom set hba_wwn port lt port gt lt host group hba_wwn lt WWN strings gt wwn_nickname lt WWN Nickname gt name gt Delete nickname from WWN of host path adapter raidcom name gt reset hba_wwn port lt port gt lt host group hba_wwn lt WWN strings gt Display registered WWN information of host path adapter raidcom get host _grp port lt port gt lt host group name gt Blockade or restore LDEV raidcom modify ldev ldev_id lt ldev gt status discard_zero_ page Create nickname for LDEV raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Modify allocated MP Blade to LDEV raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Format LDEV raidcom initialize ldev ldev_id lt ldev gt grp_opt lt group option gt device grp name lt device group name gt lt device names operation lt type gt Device group Create device group raidcom add device _grp device_grp_name lt ldev group name gt lt device name gt ldev_id lt ldev gt cnt lt count gt Delete LDEV from device group raidcom delete device _grp device_grp_name lt device group name gt ldev_id lt ldev gt cent lt count gt Display device group information raidcom get device _grp lt device group name gt device_grp_name Create copy group raidcom add copy _grp copy_g
73. When user 10 and user 20 share the port like the following figure the relation between the command devices and resource groups that user can use is like Table 3 4 Relation between resource groups and command devices on page 3 12 CCI functions Hitachi Command Control Interface User and Reference Guide 3 11 oS RE RE Resource group for the common resouce management Port Resource group 0 Resource group 10 Resource group 20 Parity Group Parity Group Parity Group E E O a E Legend gt Accessing CM Command device Figure 3 2 Relation among user command devices and resource groups Table 3 4 Relation between resource groups and command devices Out of band operation Comman Referenc Configuration Login user G device Operating range A change System OK administrator Can operate all resource groups OK Can operate only in the range of resource group 10 OK Can operate only in the range of resource group 20 3 12 CCI functions Hitachi Command Control Interface User and Reference Guide Out of band operation Comman d device Referenc Configuration e change Login user Operating range OK Can operate in the range of resource group 10 and shared ports OK Can operate only in the range of resource group 10 NG Operation Nothing is displayed or the operation authority error authority error OK OK OK Can ope
74. Write Snapshot pair and the S VOL of a TrueCopy pair Executing A Snapshot data cannot be obtained because the Universal Replicator pair status is COPY when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a Universal Replicator pair Executing The command ends abnormally because the ShadowImage pair is being resynchronized when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a ShadowImage pair Executing The command ends abnormally because the ShadowImage pair status is other than PSUS when the volume is shared between P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a ShadowImage pair 9 68 Executing The Thin Image or Copy on Write Snapshot pair cannot be restored because the Thin Image or Copy on Write Snapshot pair status is other than PSUS or PSUE when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a ShadowImage pair Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify snapshot Error message Executing Async Executing Error code SSB1 SSB2 Description The Thin Image or Copy on Write Snapshot pair cannot be restored because the Thin Image or Copy on Write Snapshot pair status is other than PSUS when the volume is shared between the P VOL of a Thin Im
75. You can group the host bus adapters into SPM groups and then use the SPM groups to change the priorities of multiple host bus adapters at the same time You can also set the same upper limit value for all host bus adapters in a SPM group at the same time Examples of setting the SPM group Set the SPM name ORA_NODEO_CTL_0O for the SPM gropup name WWN_GRP_LINUXO Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide raidcom add spm_group port CL4 E spm_group WWN_GRP_ LINUX0O ORA_NODEO CTL 0 Set the WWN 210000e08b039c15 for the SPM gropup name WWN_GRP_LINUX1 raidcom add spm_group port CL4 E spm_group WWN_GRP_LINUX1 hba_wwn 210000e0 8b039c15 SPM group names are managed uniquely in the entire system Checking the traffic of the prioritized WWN and the non prioritized WWN You can use the monitoring function to check whether the performance of the prioritized WWN can be secured by setting the upper limit Example of acquiring the monitoring information Acquires the monitoring information by specifying the WWN 210000e08b039c15 raidcom monitor spm_wwn hba_wwn 210000e0 8b039c15 PORT SPM MD IOps KBps Serial CL4 E WWN 5000 5000000 63528 Stopping performance control of server by using SPM function To stop controlling the performance of the server by using the SPM function delete the SPM name from the SPM targets Example of deleting from the SPM targets Delete th
76. a TrueCopy or Universal Replicator pair Executing A ShadowImage pair a Thin Image Copy on Write Snapshot pair or a Compatible FlashCopy V2 relationship or in status of splitting or pending exists Executing The specified LDEV is used as a Thin Image or Copy on Write Snapshot pair Executing It is used as a system disk Executing It is used as a concurrent copy or a XRC 9 26 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom disconnect external_grp Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The specified LDEV is used as the primary volume of a global active device GAD pair Get Command Status Async The specified LDEV is used as the secondary volume of a GAD pair CMDRJE Executing The specified external volume group is in the state of disconnected CMDRJE Executing The specified external device is in the state of disconnected CMDRJE Executing The specified external volume has already disconnected the path or is in the process of checking path Executing It is in the state of shredding Executing The target LDEV is blocked Executing The path for the specified external path is in the state of disconnected Executing All the paths for the specified external path are blocked Executing The specified externa
77. a deleting state for CT group on each MCU e Searches commits a minimum matching point of the CTQ Marker on RCU via MCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on MCU on all RCU via MCU e Issues End of Delete to terminate a deleting state after committed with EOM End Of Marker on all RCU Exception If an uncommitted state that is link failure is detected while executing its operation then the operation of committing is aborted on keeping current CTQ Marker level and a deleting state terminates without waiting for an EOM End Of Marker 4 pairsplit RS option In the case of PAIR state NO failure e Issues SwapSuspend to make a suspending state for CT group on each RCU Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide e Searches commits a minimum matching point of the CTQ Marker on RCU via RCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on MCU on all RCU via RCU e Issues End of Suspend to terminate a suspending state after committed with an EOM End Of Marker on all RCU Exception If an uncommitted state that is link failure is detected while executing its operation then the operation of committing is aborted on keeping current CTQ Marker level and a suspending state terminates with detecting at least one EOM End Of Mark
78. all logical drives on the P VOL by Back up the S VOL data application Flush the system buffer for S VOL e Flush the system buffer for P VOL updates using raidscan pi LETALL find using raidscan pi LETALL find sync g ORB when the backup is finished sync g ORB Split the paired volume using pairsplit g ORB with r w mode Open all logical drives on the P VOL by application Resynchronize the paired volume using pairresync g ORB Online backup using raidscan find sync for Windows NT file system The raidscan find syne command flushes the system buffer through finding a logical drive corresponding to a group of the configuration file without using the x mount and x umount commands The following examples are for group ORB Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide P VOL Side S VOL Side Freeze DB on opening P VOL by Back up the S VOL data application Flush the system buffer for S VOL updates e Flush the system buffer for P VOL using raidscan pi LETALL find sync g using the raidscan pi LETALL ORB when the backup is finished find sync g ORB Splits the paired volume using pairsplit g ORB with r w mode Unfreeze DB on opening P VOL by application Resynchronize the paired volume using pairresync g ORB Note AN e P VOL side must stop the WRITE IO to the logical drive corresponding to a g name before issuing the raidscan find sync
79. and device group names of the device groups to be created e Use cases The following examples show use cases for creating a device group o Creating a device group configured of simplex volumes with different device names o Creating a device group configured of a simplex volume and a paired volume with different device names CCI functions 3 31 Hitachi Command Control Interface User and Reference Guide o Creating a device group configured of simplex volumes with same device names LDEV addition to device group Adding an LDEV to the device group by specifying a created device group name and the LDEV ID of the LDEV to be added e Use Cases The following shows use cases that can be added an LDEV to a device group o Adding an LDEV simplex volume with a different device name to a device group o Adding an LDEV paired volume with a different device name to a device group o Adding an LDEV to a device group already including the same device name The device name can be duplicated in the case of not creating the copy group by specifying a device group 3 32 CCI functions Hitachi Command Control Interface User and Reference Guide LDEV deletion from device group Deleting an LDEV from the device group by specifying a created device group name and an LDEV ID of the LDEV to be deleted LDEV can be deleted from the device group associating a copy group The pair status does not chan
80. and Reference Guide About Command Control Interface The Command Control Interface software enables you to perform storage system configuration and data management operations by issuing commands to the Hitachi RAID storage systems e Hitachi Virtual Storage Platform G1000 VSP G1000 e Hitachi Unified Storage VM HUS VM e Hitachi Virtual Storage Platform VSP e Hitachi Universal Storage Platform V VM USP V VM e Hitachi TagmaStore Universal Storage Platform TagmaStore USP e Hitachi TagmaStore Network Storage Controller TagmaStore NSC CCI continues to provide the proven functionality that has been available for the USP V VM and previous storage system models including in system replication remote replication and data protection operations In addition CCI for VSP and later now provides command line access to the same provisioning and storage management operations that are available in the Hitachi Storage Navigator graphical user interface CCI commands can be used interactively or in scripts to automate and standardize storage administration functions thereby simplifying the job of the storage administrator and reducing administration costs command is rejected verify the software licenses for the storage system for example TrueCopy and the status of the software product and storage system Caution Some storage systems may reject commands from CCI If a CCI CCI functions CCI functions matrix The foll
81. and grp2 Display the copy group information Execute the path definition of WOL 10 to 719 to Port CLI A host group HP UX P Execute the path definition of VVOL 20 to 29 to Port CL2 A host group HP UX S Give an LU number automatically Display the path information that is set to PortCL1 A host group HP UX P and the path information that is set to PortCL2 A host group HP UX S Unlock the resource group meta_resource Display the resource group information Start monitoring of Pool 1 Stop monitoring of Pool 1 Start reallocation processing of Pool 1 Log out Figure 5 12 Script examples of virtual volume operation Dynamic Tiering 3 3 External volume operations Creating external volumes Use the following provisioning operations to create LDEVs of external volumes and make the LDEVs available from the host Provisioning operations with CCI 5 39 Hitachi Command Control Interface User and Reference Guide Operation overview Setting port attribute of local storage system Description Set port attribute of local storage system to External ELUN port Executed command raidcom modify port port lt port gt port_attribute ELUN Searching external storage Display port information on the external storage connected to the External port raidcom discover external storage port lt port gt Searching external volume Display a list of external volumes
82. assured may be behind but data consistency is assured what has reached the S VOL is in the proper order Setting the fence level Data fence level 6 32 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Figure 6 12 Relationship between logs journal and data in paired status on page 6 33 shows the relationship between redo log files journal and data files If the S VOL takes over from the P VOL in the status shown in Figure 6 12 Relationship between logs journal and data in paired status on page 6 33 where two errors have occurred the secondary host leaves data V unprocessed in the roll back processing and cannot be recovered completely Therefore the fence level of a redo log file must be defined as data Once the fence level is set to data the P VOL returns an error if data may possibly be inconsistent when a write request is issued by the host Since writing to the data file is not executed due 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 is suspended due to an error in the S VOL Accordingly duplication becomes meaningless when the S VOL takes over Thus applications using paired volumes with the data fence level should be able to handle write I O errors properly For example the Oracle application creates multiple redo log file
83. command See the Command Control Interface Command Reference for more information on error codes for each command Table 9 5 Specific error codes Category Error code Error message Volume Status EX_ENQVOL Unmatched volume status within the group 236 Unrecoverable EX_INCSTG Inconsistent status in group 229 EX_INVVOL Invalid volume status 222 EX_EVOLCE Pair Volume combination error 235 EX_INVSTP Invalid pair status 228 EX_VOLCUR S VOL currency error 225 EX_VOLCUE Local Volume currency error 224 EX_VOLCRE Local and Remote Volume currency error 223 EX_EWSUSE Pair suspended at WAIT state 234 EX_ENQSIZ Unmatched volume size for pairing 212 EX_ESVOLD SVOL denied due to be disabling 209 EX_EPRORT Mode changes denied due to retention time 208 Timer EX_EWSTOT Timeout waiting for specified status 233 Recoverable EX_EWSLTO Timeout waiting for specified status on the local 232 host Resource EX_ENOCTG Not enough CT groups in the RAID 217 Unrecoverable EX_ENXCTG No CT groups left for OPEN Vol use 215 EX_ENOPOL Not enough Pool in RAID 206 SSB codes An SSB code is error information that is output when an error occurs by executing a CCI command The SSB code is output to the CCI execution log file or to the console Identify the SSB code from an error code as follows e SSB code that is output to the CCI execution log file The following shows an example of a SSB code that is ou
84. data is managed by bitmap The CCI software can detect and report the PFUL and PFUS states as follows e As a return code of the pairvolchk command e As the status code displayed to code item by the pairmon command e As the paired status displayed to status item using fc option of pairdisplay command Table 6 8 State table for TrueCopy vs TrueCopy Async Storage system internal state TrueCopy Sync Description TrueCopy Async Writing control on TC async volume Writing data Normal Response Usual Transfer data via ESCON None Via Sidefile Usual Sidefile amp bitmap Deleting N A Deleting from COPY using pairsplit S Normal Usual Sidefile Suspending N A Suspending from COPY by using pairsplit Via Bitmap Usual Sidefile PAIR Synchronized PFUL N A Async Less than HWM Via Sidefile Usual Sidefile sidefile in use HWM to Threshold Via Sidefile Delayed Sidefile Over Threshold Via Sidefile Wait until under threshold Sidefile Deleting Deleting from PAIR using pairsplit S Normal Usual Sidefile Suspending Suspending from PAIR Using pairsplit Timeout of over threshold Via Bitmap Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Usual Sidefile 6 29 PSUS Storage sy
85. dev rdsk c0t3d1 vg00 dev rdsk c0t3d2 dev rdsk c0t3d3 For MU 1 vg01 dev rdsk c0t3d0 dev rdsk c0t3d1 vg01 dev rdsk c0t3d2 dev rdsk c0t3d3 Verifying a group for vg01 The following are examples how to verify whether a LVM volume group is mapped to group MU 1 for ShadowImage in the horcm conf 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 fd DEVICE FILE Group PairVol Device File M SERIAL LDEV dev rdsk c0t3d0 oradbl oradevl co0t3do 1 35013 17 dev rdsk c0t3d1 oradb1 oradev2 c0t3d1 1 35013 18 dev rdsk c0t3d2 oradb oradev3 c0t3d2 1 35013 19 dev rdsk c0t3d3 z 1 35013 20 Naming of HORCMPERM file on Windows systems HORCMPERM is windir horcmperm conf or windir horcmperm conf instance number by default type SHORCMPERM 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 DBO For MU 0 Hd0 10 harddisk12 harddisk13 harddisk17 DB1 For MU 1 hd20 23 Verifying a group for DB1 The following is an example of how to verify whether a DB volume group is mapped to a group MU 1 for ShadowImage in the horem conf file correctly Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide D HORCM etc gt se
86. example gt raidcom get Idev Ildev_id cnt 65280 store lt work_file gt gt raidcom zt lt script_file gt load lt work_file gt Precheck function CCI provides a precheck function that checks a configuration command before executing the command for the configuration setting commands raidcom commands In previous versions of CCI an error was returned when the syntax of a command to be executed was not correct Now the precheck function checks the command syntax before the command is issued To use this function specify either the checkmode precheck option or the zt option The following table shows the checking function combinations between the precheck function and the transaction mode Table 1 2 Summary of the checking functions Context check Execution Command syntax raidcom lt command gt Executed Not Not Executed executed executed raidcom lt command gt checkmode precheck Executed Not Not Not executed executed executed raidcom zt lt script file gt Executed Executed Not Executed executed raidcom get ldev ldev_id cnt 65280 Executed Executed Executed Executed store lt work file gt raidcom zt lt script file gt load lt work_file gt raidcom zt lt script file gt checkmode precheck Executed Executed Not Not executed executed 1 4 Overview Hitachi Command Control Interface User and Reference Guide Command syntax Execution raidcom get ld
87. exists if the target port or host group information does not exist in the configuration definition file the error is not detected The commands as the target of the check are shown below CCI functions Hitachi Command Control Interface User and Reference Guide e raidcom modify host_grp port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt e raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom delete hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom set hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt wwn_nickname lt WWN Nickname gt e raidcom reset hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom add lun port lt port gt lt host group name gt ldev_id lt Idev gt lun_id lt lun gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt e raidcom delete lun port lt port gt lt host group name gt lun_id lt lun gt ldev_id lt Ildev gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt Check with deletion operation It is checked to ensure that the operation is not intended to be performed for the host group that is already deleted If the host group is already deleted an
88. for troubleshooting and maintenance If no trace control parameters can be specified using the environment variables in your command execution environment it is possible to change the trace control parameters into the global parameters using this command Table 2 6 Trace command parameters on page 2 38 lists and describes the parameters of the trace control command Table 2 6 Trace command parameters Parameter Function Trace level parameter Specifies the trace level range 0 to 15 Trace size parameter Specifies the trace file size in KB Trace mode parameter Specifies the buffer mode or non buffer mode for writing data in the trace file Trace type parameter Specifies the trace type defined internally Trace change instruction Specifies the command or CCI instance for which the trace control parameters are changed CCI software environment Hitachi Command Control Interface User and Reference Guide Command logging for audit Logging other than raidcom command on page 2 39 Logging raidcom command on page 2 41 Logging other than raidcom command This section explains the logging other than the raidcom command described in Logging raidcom command on page 2 41 CCI supports command logging this logging function cannot be used for auditing the script issuing the command Thus CCI supports the function logging the result of the command executions by expanding the current logging This function
89. for Commands are Commands are defined is reported Mainframe operations rejected rejected Operational differences for replication commands The following table shows the differences between open volumes and mainframe volumes in replication commands For details on the differences see the manual for each program product Table 3 15 Differences in replication commands Operation in mainframe systems Operation in Command Description open systems paircreate c lt size gt Specifies track TrueCopy TrueCopy for This option is not size when You can specify Mainframe supported in Universal copying 1 to 15 tracks 3 or 15 tracks Replicator or Universal Replicator for When you specify Mainframe the number 1 to 3 the copy speed is There is no difference 3 tracks between ShadowImage and ShadowImage for When you specify Mainframe the number 4 to 15 the copy speed is 15 tracks m grp If CTGID is not You can specify You can specify ShadowImage pairs CTGID specified this option this option and ShadowImage for CTGID is Mainframe pairs cannot automatically be registered to the assigned and a same CTG ID If both Pair is ShadowImage pairs registered to the and ShadowImage for CT group If Mainframe pairs are CTGID is registered to one specified a pair group the command is registered to ends abnormally the CTGID in use 3 44 CCI functions Hitachi
90. groups creating resource groups in the device group unit and migrating created resource groups 5 18 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide C HORCM etc gt raidcom add device_grp device_grp_name dg_jnli datai Idev_id 512 513 514 515 C HORCM etc gt raidcom get device_grp LDEV_GROUP dg_jn11 Serial 64539 C HORCM etc gt raidcom get device_grp device_grp_name dg_jnli LDEV_GROUP dg_jn11 dg_jn11 dg_jn11 dg_jn11 C HORCM etc gt raidcom add resource resource_name LDEV_NAME datal datal datal datal device_grp_name dg_jnlii GROUP PORT GROUP dg jnl1l D none LUN dg jnl1l D LUN none dg jnl1l D LUN none dg jnl1l D LUN none none GROUP none GROUP none EVICE datal UnitID 0 none done EVICE UnitID datal done EVICE UnitID datal done EVICE UnitID datal done LDEV LDEV LDEV LDEV 512 513 514 55 Serial 64539 64539 64539 64539 rsg002 grp_opt Idev 512 0x0200 1 513 0x0201 1 514 0x0202 1 LDEV 515 0x0203 1 C HORCM etc gt raidcom delete resource resource_name rsg002 grp_opt Idev device_grp_name dg_jnl1i GROUP PORT GROUP dg jnl1l D none LUN dg jnl1l D LUN none dg jnl1l D LUN none dg jnl1l D LUN none none GROUP none GROUP none EVICE UnitID 0 data
91. gt rcu_port lt port gt Journal see the manuals for UR and URz Register journal volume to Journal raidcom add journal journal_id lt journal ID gt ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp_ name lt device group name gt lt device name gt mp_blade id lt mp gt timer_type lt timer type gt Delete journal volume from Journal Delete journal raidcom delete journal journal_id lt journal ID gt ldev_id lt ldev gt grp_opt lt group option gt device_ grp name lt device group name gt lt device name gt Change the Universal Replicator option to be used at Journal raidcom modify journal journal_id lt journal ID gt data_overflow_watch lt time gt cache_mode lt y n gt timer_type lt type gt path_blocked_watch lt time gt mirror_id lt mu gt mp_blade_id lt mp gt Display journal information raidcom get journal get journal t key lt keyword gt raidcom Available provisioning operation specifying device group Summary CCI can execute provisioning operation by specifying a device group When specifying a device group the LDEVs belonging to the device group can be operated at a time For details about device group see LDEV grouping function on page 3 25 The following table lists the provisioning operations that can be executed by specifying a device group
92. has an attribute to indicate protection ON or OFF Note AN e 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 command device on a single line in the HORCM_CMD section of the configuration file The following shows an example with two controller paths to the command device Putting the path information on separate lines may cause parsing issues and failover may not occur unless the HORCM startup script is restarted HORCM CMD dev_name dev _ name dev name dev rdsk c1t66d36s2 dev rdsk c2t66d36s2 Command device guarding In the customer environment a command device may be attacked by the maintenance program of the Solaris Server after that usable instance will be exhausted and CCI instance would not start up on all servers except attacked server This may happen due to incorrect operation of the maintenance personnel for the UNIX Server In this case the command device should be protected against operator error as long as it can be seen as the device file from the maintenance personnel Thus the RAID microcode for the command device and CCI support this protection in order to guard from similar access Guarding method Currently assignment of the instance via the command device is ONE phase Therefore if the command device reads a special allocation area of the instance through the maintenance tool and so on then it causes a
93. in SVOL_COPY state because P VOL is already in PVOL_PSUS state If you want to wait the SVOL_SSUS state and then you must check the status of the S VOL becomes SVOL_PSUS via the return code using pairvolchk ss command on S VOL side or pairvolchk ss c command on P VOL side Or you can use pairevtwait ss ssus on both P VOL and S VOL pairevtwait ss ssus l on S VOL locally e If you attempt the pairresync restore or pairsplit S in PVOL_PSUS amp SVOL_COPY state then ShadowImage will reject this command due to unable to perform In this case you need to wait until the S VOL state becomes SVOL_SSUS 6 24 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Table 6 6 Pair status versus Copy on Write Snapshot commands Pair Status SMPL Copy on Write Snapshot Command paircreate pairsplit pairresync No split Accepted 2 split Rejected E option Rejected C option Rejected S option Acceptable Resync Rejected COPY RCPY Acceptable Rejected Rejected Rejected Rejected Acceptable PAIR Acceptable Accepted 4 Rejected Accepted 4 Accepted 1 Acceptable PSUS PFUS Rejected Acceptable Rejected Acceptable Accepted 1 Accepted 2 5 PSUE Rejected Rejected Acceptable Rejected Accepted 1 Accepted 2 Accepted A command is accepted and issued w
94. is no path group CMDRJE Get Command Status Executing Async Paths cannot be deleted because there are no normal paths CMDRJE Executing The port attribute is not External ELUN CMDRJE 9 92 Executing The command cannot be accepted After a while execute the same command Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom delete path Error message Get Command Status Executing Async Error code SSB1 SSB2 Description An internal error occurred Call Hitachi Data Systems Support Center Get Command Status An internal error occurred Call Hitachi Data Systems Support Center Table 9 64 SSB codes that are returned by raidcom add path command raidcom add path Error code Error message Wee Description sync SSB1 SSB2 CMDRJE Executing 2E00 4500 The path group is not in the enabled range CMDRJE Executing 2E00 8400 The value of specified port is incorrect Get Command Async 2E10 4303 The path operations cannot be performed for the Status following reasons e The target of the specified path group is TagmaStore USP TagmaStore NSC e The specified path group contains the external volume that is set the reserve attribute from the host Get Command Async 2E10 4400 The WWN on the side of specified external storage Status is not connected to an External po
95. is out of range CMDRJE Executing 2E30 6003 The specified pool is for Thin Image or Copy on Write Snapshot CMDRJE Executing 2E30 6005 The specified pool must be assigned two user defined thresholds to CMDRJE Executing 2E30 600D The specified pool is not the pool for Dynamic Tiering CMDRJE Executing 2E31 6004 The specified pool includes the different RAID levels of volumes although the pool cannot include those volumes together CMDRJE Executing 2E31 6005 The specified pool includes external volumes although the pool cannot include those volumes together CMDRJE Executing 2E31 6006 The specified pool cannot be used for a Dynamic Tiering Troubleshooting 9 55 Hitachi Command Control Interface User and Reference Guide raidcom modify pool Error code Executing Async sspi ssB2 Error message Description Executing The capacity that can be used by the installed program products exceeds the maximum Executing The program product is not installed Executing Pool ID is not installed Executing An internal error occurred at the pool operation Call Hitachi Data Systems Support Center Executing The command cannot be accepted After a while execute the same command Executing An internal error occurred in the pool operation Call Hitachi Data Systems Support Center Table 9 35 SSB codes that are returned by raidcom rename pool command raidcom rename pool
96. is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting 9 67 Hitachi Command Control Interface User and Reference Guide raidcom modify snapshot Error message Executing Async Executing Error code SSB1 SSB2 Description The command ends abnormally because the Volume Migration target volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Quorum disk is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The Thin Image or Copy on Write Snapshot pair cannot be restored because the TrueCopy pair status is other than PSUS or PSUE when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a TrueCopy pair Executing A Thin Image or Copy on Write Snapshot pair cannot be restored because the Universal Replicator pair status is other than PSUS or PSUE when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a Universal Replicator pair Executing A Snapshot data cannot be obtained because the TrueCopy pair status is COPY when the volume is shared between the P VOL of a Thin Image Copy on
97. ldev_id lt ldev gt mp_blade_id lt mp gt Script examples Displaying a LDEV information Displays an information of created LDEV and confirms an execution result of the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt The following shows the script examples of internal volume mainframe volume operations Provisioning operations with CCI 5 21 Hitachi Command Control Interface User and Reference Guide raidcom login USERO1 PASSO1 raidcom lock resource resource grp name Weta_re sour ce for 1 MMi in C0 1 5 do C raidcom add dew parity_grp_id 1 1 emulation S390 A cylinder 483078 Idev_id Wi 1 raidcom get command_status raidcom reset command_status for fl MMi in 0 1 5 do raidcom initialize dew Idew_id Wi operation gt rit l raidcom get command_status raidcom reset command_status for 1 MMi in C0 1 9 do C raidcom modify Idew Idev_id AMG device_name my wo lume Hi l for 1 i in C0 1 9 do L raidcom modify Idew Idev_id ai mp_blade_id 2 raidcom get Idew Idew_id ent 10 for 1 Wi in 0 1 3 do raidcom add dev ice_grp device_grp_name grpl datatai Idev_id HHi 1 ra idom raidcom get command_status reset command_status raidcom get device_erp dewice_grp_ name erpl raidcom add copygrp copy grp name ora grpl ra idom ra idom get command_status reset command_status raidcom get copy_ere f
98. not assign a drive letter to the command device to prevent utilization by general users SCSI alternate path restrictions If the P VOL and S VOL are on the same server alternate path from P VOL to S VOL cannot be used Use of SCSI alternate path to a volume pair in the pair status is limited to among primary secondary volumes Alternate path using Path Manager Safe Path is limited to primary volumes Troubleshooting Hitachi Command Control Interface User and Reference Guide Items Notes and restrictions horctakeover Swap Takeover When executing horctakeover on a standby server manually 1 O on the active server must be stopped When the package software goes for a standby server a failover by HA software the HA software must guarantee an I O insulation of the active server HORCM failure to activate After a new system has been constructed a failure to activate HORCM may occur due to improper environment setting and or configuration definition Refer to the HORCM activation log and correct the settings Abnormal termination of command Refer to the command log file and HORCM log file to identify the cause of the error If a command terminates abnormally because of a remote server failure recover the server from the failure then re execute the command If HORCM has shut down restart HORCM If an unrecoverable error occurs obtain the log files and contact the Hitachi Data Systems Support Center
99. of a Universal Replicator pair is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the journal volume of the Universal Replicator is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume that is set the S VOL Disable is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume that is set the VMA is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volumes of different Max LBA size are specified as the P VOL of a Thin Image or Copy on Write Snapshot pair and S VOL Executing The command ends abnormally because the volumes in which the number of slots is different are specified as the P VOL of a Thin Image or Copy on Write Snapshot pair and S VOL Executing A pair cannot be created because the Dynamic Provisioning V VOL is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the ShadowImage reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration source volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing T
100. of the configuration definition files when specifying a virtual storage machine by command options Example of the configuration definition files HORCMO The underlined parts indicate the information that needs to modify from the file of the old model i ke KK KKK HORCMO on PHOST KK KK HORCM_MON ip address service poll 10ms timeout 10ms NONE horcm0 1000 3000 H kee KR KEKE FOr HORCM CMD kkk kkk RRR RK HORCM CMD dev_name CMD 367000 dev rdsk HORCM_LDEV Ora dev1 365000 01 00 hil Ora dev2 365000 01 01 hil H ke KKKRKKEKE FOr HORCM INST kk RRR KKK KKK EK HORCM_INST dev_group ip address service Ora RHOST horem1 Example of the configuration definition files HORCM1 The underlined parts indicate the information that needs to modify from the file of the old model i eR KKK KKK HORCM1 on RHOST kK KK HORCM_MON ip address service poll 10ms timeout 10ms NONE horcm1 1000 3000 H ke RRR KEKEK FOr HORCM CMD kkk kkk kkk kk kkk HORCM CMD dev_name CMD 368000 dev rdsk HORCM_LDEV Ora dev1 366000 02 00 hil Ora dev2 366000 02 01 hil CCI functions 3 49 Hitachi Command Control Interface User and Reference Guide H ke RK RKEKEK FOr HORCM INST eR RRR RR RR RH HORCM_INST dev_group ip address service Ora PHOST horcm0 Commands to the virtual storage machine Commands paircreate When HORCM starts CCI obtains the virtual storage machine information from multiple s
101. or Copy on Write Snapshot pairs has already reached the maximum Executing 9 64 A Thin Image pair cannot be created because the maximum number of Snapshot IDs MU numbers has already been in use for the specified P VOL Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add snapshot Error code Executing Async sspi ssB2 Error message Description Executing A Thin Image pair cannot be created because the maximum number of Snapshot groups has already been defined or the maximum number of Thin Image pairs has already been defined in the specified Snapshot group Executing A Thin Image pair cannot be created because the DP pool is being initialized Executing An error occurred at the operation of Thin Image due to one of the following reasons e The LDEV number specified for the P VOL or the S VOL is incorrect 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 to 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 e The license capacity has exceeded the maximum e The control table for Thin Image is depleted Executing The operation cannot be performed because power off is in progress Executing A Thin Image or Copy on Write Snapshot p
102. path for the external path raidcom check_ext_storage path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt Setting the external path raidcom add path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt Mapping the external volume raidcom add external_grp path_grp lt path group gt external_grp_id lt gno sgno gt port lt port gt external_wwn lt wwn strings gt lun_id lt lun gt emulation lt emulation type gt Deleting the external path raidcom delete path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt Releasing the mapping of external volume raidcom delete external_grp external_grp_id lt gno sgno gt Stopping the use of paths to the external volume raidcom disconnect path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt Help on configuration setting commands To see the configuration setting command help execute any command using the h option for example raidcom h raidcom h LDEV nickname function As 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 Idev ldev_id lt Id
103. performed because the target LDEV is a quorum disk Get Command Status LDEV cannot be blocked because there is no connection path to the normal external path Get Command Status An internal error occurred Table 9 29 SSB codes that are returned by raidcom modify Idev status enable_reallocation disable_reallocation new_page_allocation enable_relocation_policy command raidcom modify Idev status enable_reallocation disable_reallocation new_page_allocation enable_relocation_policy Error message Executing Async Executing Error code SSB1 SSB2 Description Invalid LDEV number Executing The tiering policy is not in the effective range Executing The new page assignment tier is invalid Executing The specified LDEV is not installed Executing The SM Shared Memory for Dynamic Tiering is not installed Executing The specified LDEV is not a virtual volume of Dynamic Provisioning Dynamic Tiering Executing Troubleshooting The specified LDEV is not a virtual volume of Dynamic Tiering 9 49 Hitachi Command Control Interface User and Reference Guide Table 9 30 SSB codes that are returned by raidcom modify Idev status discard_zero_page command raidcom modify Idev status discard_zero_page Error code Executing Async sspi ssB2 Error message Description Executing The specified LDEV is used as an ShadowI
104. port if LUN 0 is invisible Database Validator Database Validator prevents data corruption in an Oracle database by checking Oracle data validation before an Oracle data block is written on a disk Data Block corruption This occurs when Oracle data is corrupted by some intervening software layer and or hardware components The RAID storage system can check the validity of the data block before the Oracle data block is written to disk Data block address corruption The OS file system LVM Disk driver may write blocks to the wrong location The RAID storage system can check the validity of the data block address to verify that the Oracle data block is written to the correct location on disk Data protection operations with CCI 7 3 Hitachi Command Control Interface User and Reference Guide e Protection of Oracle volume Oracle data files might be overwritten by a non Oracle application or by human operation using a command The RAID storage system can protect volumes storing Oracle files by preventing the volumes from being modified by another application or by human error Restrictions on Database Validator e Oracle tablespace location 7 4 o File system based Oracle files are not supported by Database Validator All Oracle database files must be placed on raw volumes including LVM raw volumes directly If host based striping is used on raw volumes then the stripe size must be an exact multiple of the Oracle block siz
105. provides remote mirroring functionality linkage functionality with failover switching and remote backup operations among servers all of which are required by UNIX PC servers in HA configurations for disaster recovery For detailed information about TrueCopy operations please see the Hitachi TrueCopy User Guide for your storage system Using CCI with Thin Image 6 4 CCI allows you to perform Hitachi Thin Image operations by issuing raidcom commands for example raidcom add snapshot to the RAID storage system Hitachi Thin Image stores snapshots in storage system Creating a Thin Image pair changes the status to PAIR and stores snapshot data as a copy of the data on the Thin Image P VOL A Thin Image pair consists of a P VOL one or more S VOLs that are virtual volumes V VOLs and one or more pool VOLs that are LDEVs P VOL differential data is stored as snapshot data in the pool VOLs If your storage system experiences a data storage failure you can restore the data using the snapshot data in the pool Splitting a Thin Image pair saves a snapshot and stops the copying of replaced data in the pool Consistency groups and snapshot groups are groups of pairs for which you can simultaneously perform pair tasks on all pairs within the group You can use CCI raidcom commands to create consistency groups and snapshot groups and to split pairs to store the snapshot data for the groups e A consistency group can include HTI SI and SIz
106. raidcom add lun Error code Executing Async sspi ssB2 Error message Description Executing An invalid LDEV exists in the specified LDEVs Executing LUN path cannot be set because it is reserved for Volume Migration Executing The attribute of the specified port is Initiator or External Executing The other than HMDE volume or OPEN volume is included in the specified LDEV Executing An LU path has already defined in the relevant LDEV Executing An invalid LDEV exists in the specified LDEVs Executing It exceeds the maximum LUN under the port Executing LDEV is set as a pool volume Executing LUN path cannot be set because the LDEV is a system disk Executing LUN path cannot be set because the LDEV is a journal volume Executing LUN path cannot be set because the access attribute of LDEV Data Retention Utility is reserved Executing When the host mode is Universal Volume Manager 0x4C the LUN path cannot be set in the other than the external volume Executing The host group and the LDEV that configure the LU path do not exist in the same virtual storage machine Executing The LU path definition cannot be set because the virtual LDEV information of the specified LDEV is not defined yet Executing Command device cannot be set because it is reserved for Volume Migration Executing Command device cannot be set because it is an ShadowImage pair or it is
107. raidscan find verify command EX_ENQSIZ Unmatched volume size for pairing Size of a volume is unsuitable between the remote and local volume Please confirm volume size or number of LUSE volume using the raidscan f command and make sure the volume sizes are identical EX_ERPERM Permission denied with the RAID A storage system RAID mentioned in the configuration file does not have a permission for CCI Please confirm if the type of storage system is permitted for a CCI by using the ingraid CLI and raidqry h commands EX_ESVOLD SVOL denied due to be disabling A specified target volume for S VOL is denied to become S VOL by the setting of Data Retention Utility Please confirm whether a target volume is setting to S VOL disabling by using ingraid f1 or raidvchkscan v gflag command EX_ENOSUP Microcode not supported The storage system does not support a function for CCI Please confirm the microcode version by using the raidgry 1 command EX_EPRORT Mode changes denied due to retention time A target volume is denied to be changing due to retention time via LDEV guarding Please confirm the retention time for a target volume that is set to Data Retention Utility by using raidvchkscan v gflag command EX_ESPERM Permission denied with the SLPR A specified command device does not have a permission to access other SLPR Please mak
108. range Get Command Status Async The specified pool attribute differs from the pool attribute of existed pool Get Command Status Async The RAID level of the specified LDEV is different from the RAID level of the other pool volumes Get Command Status Async There is a blocked pool volume Get Command Status Async External volumes whose cache modes are different are included CMDRJE Executing The POOL Name is duplicated with another pool Get Command Status Async The pool cannot include volumes in different RAID levels because the pool cannot include those volumes Or the pool cannot include the RAID 1 volumes and the volumes of other RAID levels together Get Command Status Async The pool cannot include both internal volumes and external volumes because the pool is not set to Mixable Get Command Status Async The usage capacity exceeds the license capacity of program product CMDRJE Get Command Status Executing Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 38 SSB codes returned by raidcom add snapshot raidcom add snapshot Error message Executing Error code Async Executing SSB1 SSB2 Description The value exceeds the range of LDEV number
109. remote host is Unknown the command will use a default of 3 as the number of tracks for Resync for Swapping If this step fails the swap takeover function will be returned at SVOLSSUS takeover and the local volume S VOL is maintained in SSUS PSUS state which permits WRITE and maintaining delta data BITMAP for the secondary volume Also this special state is displayed as SSWS state using fc option of pairdisplay command TrueCopy Async Universal Replicator specific behavior for swap takeover The S VOL side CCI will issue a Suspend for Swapping to the S VOL side storage system Non transmitted data which remains in the FIFO queue sidefile of the primary volume will be copied to the S VOL side and a Resync for Swapping operation will be performed after the copy process The Swap operation is required to copy Nontransmitted P VOL data within a given timeout value specified by the t lt timeout gt option Data replication operations with CCI 6 13 Hitachi Command Control Interface User and Reference Guide SVOL takeover function The function makes it so the takeover node alone can use the secondary volume except in COPY state in SSUS PSUS state i e reading and writing are enabled on the assumption that the remote node possessing the primary volume cannot be used The data consistency of the secondary volume is judged by its status and fence level If this check proves that data is not consistent the SVOL takeover fun
110. sa 4ese See eyes ero eens ss 9 19 SSB codes returned by the replication commands 55 9 20 SSB codes returned by the configuration setting command raidcom 9 20 Calling the HDS Support Center 0 00 cee ee ees 9 103 Index ix Hitachi Command Control Interface User and Reference Guide Hitachi Command Control Interface User and Reference Guide Preface This document describes and provides instructions for using the Command Control Interface software to configure and perform operations on the Hitachi RAID storage systems Please read this document carefully to understand how to use this product and maintain a copy for reference purposes O Intended audience O Product version O Release notes O Document revision level O Changes in this revision O Referenced documents O Document conventions O Convention for storage capacity values O Accessing product documentation O Getting help O Comments Preface xi Hitachi Command Control Interface User and Reference Guide Intended audience This document is intended for system administrators Hitachi Data Systems representatives and authorized service providers who are involved in installing configuring and operating the Hitachi storage system Readers of this document should be familiar with the following e Data processing and understands RAID storage systems and their basic functions e The Hitachi RAID storage system and the manu
111. specified operation cannot be performed because it is not supported Table 9 75 SSB codes that are returned by raidcom set resource command raidcom set resource Executing Error code Error message Async Executing 2EF3 Description The specified operation cannot be performed because it is not supported Table 9 76 SSB codes that are returned by raidcom reset resource command raidcom reset resource Executing Error code Error message Async CMDRJE Executing 2EF3 2202 Description The specified operation cannot be performed because it is not supported Table 9 77 SSB codes that are returned by raidcom unlock resource command raidcom unlock resource Executing Error code Error message Async CMDRJE Executing 2E10 2200 Description Cannot unlock because it is locked in another session Table 9 78 SSB codes that are returned by raidcom modify clpr command raidcom modify clpr Executing Error code Error message Async SSB1 SSB2 Executing Description It exceeds the settable range of LDEV numbers Executing The specified LDEV is not subject to processing Executing The parity group number or the external volume group number is not in the effective range Executing The specified group type is not correct Executing 9 100 The combined parity group cannot be set across multiple
112. specify as the following to HORCM_CMD of the configuration definition file e IPCMD lt SVP IP address gt lt UDP communication port number gt Unit ID lt SVP IP address gt Sets an IP address of SVP lt UDP communication port number gt Sets the UDP communication port number This value is fixed 31001 Unit ID Sets the unit ID of the storage system for the multiple units connection configuration This can be omitted Example for IPv4 HORCM_CMD dev_name dev_name dev_name IPCMD 158 214 135 113 31001 Example for IPv6 HORCM_CMD dev_name dev_name dev_name IPCMD fe80 209 6bff febe 3c17 31001 Note To enable dual path of the command device under Solaris systems make sure to include all paths to the command device on a single line in the HORCM_CMD section of the config file Putting the path information on separate lines may cause parsing issues and failover may not occur unless the HORCM startup script is restarted on the Solaris system When a server is connected to two or more storage systems the HORCM identifies each storage system using the unit ID see Figure 2 12 Configuration and unit IDs for multiple storage systems on page 2 18 The unit ID is assigned sequentially in the order described in this section of the configuration definition file When the storage system is shared by two or more servers each server must be able to verify that the unit ID is the same Serial Seq am
113. status of settings of the prioritized WWN and the non prioritized WWN assigned under the specified port CL4 E raidcom get spm_wwn port CL4 E PORT SPM _MD SPM _WWN NICK NAME GRP_ NAME Serial CL4 E WWN 210000e 08b0256 8 63528 CL4 E WWN 210000e 08b039c15 63528 Display the status of setting to specify the WWN 210000e08b0256f8 raidcom get spm_wwn port CL4 E hba_wwn 210000e0 8b0256f8 PORT SPM MD PRI IOps KBps Serial CL4 E WWN N 5000 63528 Displays the status of setting to specify the WWN 210000e08b039c15 raidcom get spm_wwn port CL4 E hba_wwn 210000e0 8b039c15 PORT SPM MD FRI JI0Ops KBps Serial CL4 E WWN Y 3000 63528 The threshold value displayed for the prioritized WWN by using the get spm_wwn command is set for the entire system Setting SPM name for host bus adapter The host bus adapters can be identified by checking the WWNs but using SPM names may make it easier to identify the host bus adapters Display examples of setting the SPM name of the host bus adapter Set the SPM name ORA_NODEO_CTL_O for the WWN 210000e08b0256f8 raidcom add spm_wwn port CL4 E spm_name ORA_NODEO CTL_0 hba_wwn 210000e0 8b0256f8 Set the SPM name ORA_NODE1_CTL_1 for the WWN 210000e08b039c15 raidcom add spm_wwn port CL4 E spm_name ORA_NODE1_ CTL 1 hba_wwn 210000e0 8b039c15 SPM names are managed uniquely in the entire system Grouping multiple host bus adapters into one group 5 50
114. storage machine of the specified P VOL is in progress Executing A Thin Image pair cannot be operated because changing the model and the serial number in the virtual storage machine of the specified S VOL is in progress Executing A Thin Image or Copy on Write Snapshot pair with the specified consistency group number cannot be created due to one of the following reasons e The specified consistency group number is used by the ShadowImage The number of pairs that can be defined in a consistency group exceeds the maximum The pair created by using the same P VOL already exists in the specified consistency group Executing A Thin Image pair specifying CTG mode cannot be created because the maximum number of consistency groups has already been defined Executing A Thin Image or Copy on Write Snapshot pair cannot be created due to unavailable of the pool Executing A Thin Image or Copy on Write Snapshot pair cannot be created because there are not enough pair tables Executing A Thin Image or Copy on Write Snapshot pair cannot be created because there are not enough differential tables Executing A pair cannot be created because there is not enough free shared memory space Executing The command ends abnormally because the pair is in the state of unacceptable the command Executing A Thin Image or Copy on Write Snapshot pair cannot be created because the number of Thin Image
115. targets by specifying the SPM group name Controlling server performance The server performance is controlled by setting the priority of the I O operation the upper limit and a threshold per system for the host bus adapter The following table shows the procedure for controlling the server performance by setting the priority of the I O operation the upper limit and a threshold per system for the host bus adapter Provisioning operations with CCI 5 47 Hitachi Command Control Interface User and Reference Guide Operation overview Setting the SPM information for WWN Description Set the priority prioritized or non prioritized option for the SPM controlling by specifying the number of port to which the host bus adapter is connected and WWN of the host bus adapter Executed command raidcom modify spm_wwn port lt port gt spm_priority lt y n gt limit_io limit_kb limit_mb lt value gt hba_wwn lt wwn_strings gt spm_name lt nick_name gt Giving a nickname SPM name Give a nickname to WWN for the SPM controlling to make the host bus adapter distinguishable raidcom add spm_wwn port lt port gt spm_name lt nick_name gt hba_wwn lt wwn_strings gt Registering WWN for SPM to SPM group Specifying WWN To operate per group group multiple WWNs for SPM control into one group raidcom add spm_group port lt port gt spm_group lt group_name gt hba_
116. that can be mapped from External port raidcom discover lun port lt port gt external_ wwn lt wwn strings gt Creating external volume Create external volume raidcom add ldev external_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Modifying external volume option Modify external volume option cache mode inflow mode and MP blade setting raidcom modify external _grp external grp_id lt gno sgno gt cache mode lt y n gt cache_inflow lt y n gt mp_ blade id lt mp gt Checking external volume information Display external volume information and confirm result of executing command raidcom get external _grp external_grp_id lt gno sgno gt Setting external path Set external path Execute the required number of commands raidcom add path path_grp lt path group gt port lt port gt external wwn lt wwn strings gt Displaying external path information Display external path information for and confirm the result of executing the command raidcom get path path_grp lt path group gt Setting port of external storage system Make enabled the LUN security of port Modify setting such as port topology and data transfer speed as needed raidcom modify port port lt port gt security switch y Creating host group
117. the argument of option exceeded the maximum Check the total number of option or argument of option EW_ENFILE No such file The specified file dies not exist Check if the specified file exist or not and specify the correct file EW_REQCMD Required action object list The number of action or the argument of object is insufficient Use h option and specify the correct action or object EW_REQOPT Required option list The number of option or the argument of option is insufficient Use h option and specify the correct option EW_UNWCMD Unknown command The command action or an object is undefined Check the issued command action and object EW_UNWOPT raidcom EW_UNWOPT Unknown option Specifies an undefined option Use h option and specify the correct option EW_SYSERR System error An invalid internal error has detected Contact the Hitachi Data Systems Support Center EW_ENOMEM Not enough core Memory to execute a command cannot be allocated in HORCM Add more virtual memory of a whole system or terminate unnecessary programs or daemons that are executed in parallel EX_CHGOBJ Objects was changed while referring The object is in operation Issue the command again after the operation of the object is complete Generic error codes horctakeover and pair commands The following table lists the generic
118. the both line by line mode and transaction mode e Context check This function checks the consistency of one specified line in the script and the preceding lines in the order from the top This function is available only at the Transaction mode For details about context checking see Context check on page 3 16 e Configuration check Acquire the current configuration information to a configuration file and then this function checks whether the resources specified in the script LDEVs ports or host groups are configured in the storage system or not This function is available only at the transaction mode For details about context checking see Configuration check on page 3 24 The configuration setting command also has a execution option described in the following e Precheck Specify the checkmode precheck option It operates checking only it does not execute processing even if no error is detected This can be specified at the both line by line mode and transaction mode The following table shows the overview of execution modes and options of the configuration setting command CCI functions 3 15 Hitachi Command Control Interface User and Reference Guide Table 3 5 Execution modes and options of the configuration setting command line by line mode Command syntax raidcom lt action gt Executed Context check Not executed Configura tion check Not executed Command execution with no error Executed
119. the device group is not set the device name Executing The specified resource group ID of the LDEV cannot be registered because it is different from other resource group ID of the LDEV in the specified device group Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 23 SSB codes that are returned by raidcom modify Idev ldev_name command raidcom modify Idev ldev_name Error message CMDRJE Executing Error code Description Async sspi ssB2 Executing It exceeds the range of LDEV number CMDRJE Executing LDEV nickname is not specified CMDRJE Executing LDEV is not installed Invalid Character Executing Unavailable character is included in LDEV nickname Table 9 24 SSB codes that are returned by raidcom initialize Idev command raidcom initialize Idev Error message CMDRJE Executing Error code Async sspi ssB2 Description Executing It exceeds the range of LDEV number Get Command Status Async The specified LDEV is used as a ShadowImage pair Get Command Status Async The specified LDEV is used as a TrueCopy pair or a Universal Replicator pair Get Command Status Async The specified LDEV is used as a Compatible FlashCopy V2 relationship Get Command Status Async The specified LDEV is used as a Thin Image or Copy on Write Snapshot pair Get Command Stat
120. the raidscan find and mkconf commands D HORCM etc gt ingraid SLETALL CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID D Vol2 Dsk7 z m 2 3 DDRS 34560D D hd1 Vol8 Dsk0 CL2 F 61459 448 s s ss 0005 1 01 01 OPEN 3 D hd2 Vol9 Dsk1 CL2 F 61459 449 s s ss 0005 1 01 01 OPEN 3 G Dms1 Dsk2 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 G Dms1 Dsk3 CL2 K 61456 257 4 s s ss 0005 1 01 11 OPEN 3 G Dms1 Dsk4 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 Subcommand for directory mounted volume CCI supports the directory mount with the x mount x unmount x sync option so that the directory mount can be used to mount unmount the S VOL Mount and Sync used Volume GUID for Windows CCI supports the mountcommand option specified in the device object name such as Device Harddiskvolume X Windows changes the device number for the device object name after recovering from a failure of the PhysicalDrive As a result the mountcommand specified in the device object name may fail Therefore CCI supports a mountcommand option that specifies a Volume GUID as well as the device object name Examples of using CCI commands 8 13 Hitachi Command Control Interface User and Reference Guide e Mount o The mountcommand option specifies a Volume GUID as well as the device object name o If a Volume GUID is specified then it is executed by converting a Volume GUID to a device object name o Di
121. unmounted If DRU is set to the volumes as they are in the mounted status unexpected behavior may occur in the system o When using a file system for Write Protect Mode set disk on Windows Server 2003 Windows Server 2008 Windows Server 2012 use the x mount and x umount CCI command options with the above mentioned procedures o Data Retention Utility volumes set to Write Protect Mode Read ONLY cannot be used for the Windows NT Windows 2000 file system NTFS FAT LVM VxVM on Data Retention Utility o If changing LVM configuration including Data Retention Utility use the raidvchset vg command for setting the status of the target volume checking prohibited temporarily Also after the completion of LVM configuration change set again the status as checking Data Retention Utility in HA Cluster Server o If HA Cluster software writes to the metadata at regular intervals to confirm whether its disks are available or not then Data Retention Utility should not be used in HA environments Dynamic disk on Windows systems o Data Retention Utility volumes cannot be used for the dynamic disk because the dynamic disk does not handle the volumes set to Write Protect Mode Read ONLY Data Retention Utility volumes must be used for basic disks only LUN 0 o Some operating systems cannot recognize LUNs over LUN 1 if LUN 0 has the Data Retention Utility inv attribute set This is because some HBA drivers do not scan all LUNs on a
122. volume because the size of the specified external volume group exceeds the maximum capacity of the external volume for online data migration CMDRJE Executing 2E23 0001 The number exceeds the maximum number of Get Command Async LDEV that can be created in the current system Status configuration Get Command Async 2E30 0006 The specified LDEV is used in the FICON Data Status Migration CMDRJE Executing 2E30 0020 The specified SSID is already used in another CU CMDRJE Executing 2E30 0021 The SSID is allocated to the CU already Get Command Asynchrono 2E30 0025 The specified volume is used as an alias device in Status us Compatible PAV Get Command Async 2E30 0026 An LDEV of another emulation type is allocated in Status the range where the number is divided into each 32LDEVs CMDRJE Executing 2E30 004C The emulation type that cannot be mixed with is specified CMDRJE Executing 2E30 004D The number of Idevs exceeds the maximum number of Idevs that can be created in the parity group or the external volume group CMDRJE Executing 2E30 0104 There is not enough amount of free space that is specified in the parity group or the external volume group CMDRJE Executing 2E30 0105 The location is out of the range that can be specified CMDRJE Executing 2E30 0106 Volume whose emulation type is 3390 V cannot be created in RAID1 parity group CMDRJE Executing 2E30 4119 The virtual volume cannot be added because the Get Command Async num
123. 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 pair statuses are SMPL PAIR PSUS COPY and RCPY The status is changed when the CCI command is issued A read or write request from the host is allowed or rejected according to the status Read Write Read Write A Primary Secondary volume Copy on write volume Resiore copy Data replication operations with CCI 6 35 Hitachi Command Control Interface User and Reference Guide P VOL Status Table 6 10 Copy on Write Snapshot Pairing Status Pairing Status Unpaired Copy on Write Snapshot volume R W enabled Secondary R W disable The Copy on Write Snapshot available state allocated the resource R W enabled R W disable The preparing state allocates the resource for the Copy on Write Snapshot R W enabled R W disable The copying state from Copy on Write Snapshot to the primary volume by using restore option R W enabled R W disable PFUS The differences of the updated data of the primary and secondary volume are controlled with copying on write R W enabled R W enabled PSUE Error PSUS status due sto an internal failure The differences of the updated data for the Copy on Write Snapshot volume are not controlled R W en
124. volume other than OPEN V is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume that is set the command device is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume other than OPEN V is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume that is set the command device is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing 9 66 The command ends abnormally because the volume that has no path definition is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add snapshot Error code Executing Async spi ssB2 Error message Description Executing The command ends abnormally because the volume that has no path definition is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the external volume mapped for the online data migration is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the external volume mapped for the online data migration is specified as the S VOL of a Thin Image or Copy on W
125. vt lt type gt is an appropriate type 3 Check if the data validations are disabled for LVM configuration changes 4 Check if the data validations are not shared on file system 5 Check if the redo log and data file are separated among the volumes Command error messages The following table lists and describes the command error messages and their return values and provides recommended action for resolving the error conditions They are typical messages of command error messages Check the command log file for details of the error For more details about the command log file see CCI log files on page 2 36 Error code EX_COMERR Table 9 2 Command error messages Error message Can t be communicate with HORC Manager Condition This command failed to communicate with the CCI software Recommended action Verify that HORCM is running by using UNIX commands ps ef grep horcm EX_REQARG Required Arg list An option or arguments of an option are not sufficient Please designate the correct option using the h option EX_INVARG Invalid argument An option or arguments of an option are incorrect Please designate the correct option using the h option EX_UNWOPT Unknown option Designated an unknown option Please designate the correct option using the h option EX_ATTHOR Can t be attached to HORC Manager Could not connect with HORCM Please veri
126. when a pool is created Execute tiering after changing the multiple tiering pool to the enabled status Note 2 When the multiple tiering pool is enabled the tiering control is set to Manual automatically To change the setting to Auto it is required to execute from Storage Navigator Note Before creating a pool it is required to create a virtual volume management area on the cache memory The virtual volume management area is created automatically when add a cache memory For the information about adding cache memory please contact the Support Center A Caution The operations are explained here are executable by the storage administrator only A Creating virtual volumes Dynamic Tiering Use the following operations to create LDEVs of virtual volumes Dynamic Tiering and making the LDEVs available to the host Operation overview Setting port Description Make enabled the LUN security of port Modify setting such as port topology and data transfer speed as needed Executed command raidcom modify port port lt port gt security switch y Creating host group Specify port and create host group raidcom add host_grp port lt port gt host_grp_ name lt host group name gt Setting host mode Specify port and set host mode for host group raidcom modify host_grp port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode opti
127. with CCI Hitachi Command Control Interface User and Reference Guide Remote volume discovery In the configuration separating Storage admin server CCI server and each production server it is difficult to verify check the volumes on the production servers and the volumes described to the horcm conf on CCI server In this configuration you cannot use the following CCI capabilities e Command device security e pairdisplay fd option that displays the device file on the production host view e raidscan find verify To solve this configuration problem CCI supports a way to discover volumes on the remote server by adding the export option to the ingraid command and by importing its output via the raidscan find command inqraid CLl export Production Server C Production Servef B Production Server A Horem conf Figure 6 15 Volume discovery Data replication operations with CCI 6 55 Hitachi Command Control Interface User and Reference Guide Discovering a remote volume The 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 CCI server imports the device information and registers it into the HORCM daemon The inqraid command is needed only for discovering LUNs on the production server 1 ingraid format The ingraid command adds the export option with CLI for
128. 000 raidcom delete resource VSP G1000 raidcom lock resource VSP G1000 raidcom unlock resource VSP G1000 raidcom map resource VSP G1000 raidcom unmap resource VSP G1000 raidcom get clpr VSP G1000 raidcom modify clpr VSP G1000 raidcom get snapshot Virtual storage machine raidcom add snapshot Virtual storage machine raidcom delete snapshot Virtual storage machine raidcom modify snapshot CCI functions Virtual storage machine 3 53 Hitachi Command Control Interface User and Reference Guide Operation target when you specify the virtual storage machine Operation type Commands Server Priority Manager raidcom get spm_wwn VSP G1000 raidcom get spm_group VSP G1000 raidcom add spm_wwn VSP G1000 raidcom add spm_group VSP G1000 raidcom delete spm_wwn VSP G1000 raidcom delete spm_group VSP G1000 raidcom monitor spm_wwn VSP G1000 raidcom monitor spm_group VSP G1000 3 54 raidcom get command_status VSP G1000 raidcom reset command_status VSP G1000 raidcom get error_message CCI functions VSP G1000 Hitachi Command Control Interface User and Reference Guide Starting up CCI You can begin using the CCI software after you have installed the CCI software set the command device created the configuration definition file s and for OpenVMS only follow
129. 1 1 ora AP 0 0 oe G lt o 5 Q Marker 00000032 00000020 00000031 00000022 jnl Q Marker 0 00000049 0 00000047 0 00000049 0 00000035 jnlt Q Marker 0 00000c76 0 00000c62 0 00000c3a 0 00000c33 pairdisplay g horcO v jnl fe JID MU CTG JNLS AP U Num LDEV CTQM 016 2 0 PJSN 1 1 32768 018 2 0 SJSN 1 1 32770 0000187f 017 2 0 PJSN 1 1 32769 019 2 0 SJSN 1 1 32771 0000187f o 5 0 0 0 0 Q Marker 0000bb1b 0000bb1b 00000011 00000011 QM Cnt SF 18 50 70 15 50 70 Q CNT 20 20 Q CNT 20 20 Q CNT Seq IFC OT s CT m 64034 ON 64035 64045 ON 64046 D SZ BLK 1633672703 1633672703 211506164 260319089 D SZ BLK 1633672703 1633672703 211506164 260319089 D SZ BLK 198578688 99283968 198578688 99283968 60 60 Seq 64034 64035 64045 64046 Seq 64034 64035 64045 64046 Seq 64014 64014 64014 64014 Note AN VOL CTQM Displays the last CTQ Marker that was committed on S pairsplit command The pairsplit command does not change the command options for supporting UR MxN Open However internal behavior is different from 1x1 UR or TrueCopy Async 1 pairsplit r or rw option e Issues Freeze to CT group on each MCU e Issues Suspend amp Run to make a suspending state for CT group on each MCU Data replication operations with CCI Hitach
130. 2 PSUE Rejected Rejected Acceptable Acceptable Accepted 1 Accepted 2 PDUB Rejected Rejected Rejected Rejected Accepted 1 Accepted 2 Legend Accepted Accepted and executed When the operation terminates normally the status changes to the indicated number Acceptable Accepted but no operation is executed Rejected Rejected and operation terminates abnormally Pairsplit of a TrueCopy Async volume is returned after verification of state transition that waits until delta data is synchronized from P VOL to S VOL Note In the case of the SSWS status after SVOL SSUS takeover execution the pairresync command from P VOL to S VOL is rejected because the delta data for S VOL becomes dominant and its status is expected to be using the swaps p option of pairresync If the pairresync command from P VOL to S VOL is rejected confirm this special status using the fc option of the pairdisplay command The following table shows the relation of command acceptances for paired status and ShadowImage Table 6 5 Pair status versus ShadowImage commands ShadowImage command paircreate pairsplit pairresync Pair Status No split split E option C option S option Resync Accepted 2 Accepted 2 Rejected Rejected Acceptable Rejected to 4 Accepted 1 2 to 4 Accepted 1 Acceptable Accepted 5 Accepted 1 2 to 4 Acceptable
131. 2 A and Host group name HP UX S Set Host mode HP UX to the Host group 0 of PortCLI A and PortCL2 A raidcom modify host_erp port CL2 A 0 host_mode Display the host group information that is set to PortCLI A and PortCL2 A Set Connection host WAN 21000000 amp 0256f8 to PortCLI A and Host group HP UX P Set Connection host WAN 210000e0 amp 0256f9 to PortCL2 A and Host group HP UX S Display Connection host WN that is set to PortCLI A and Host group HP UX P Display Connection host WN that is set to PortCL2 A and Host group HP UX S Create each 10 of 10G LDEV to Parity_grp_id 1 1 and 1 2 LDEV O to 9 10 to 19 Execute Quick format to LDEV 0 to 19 Give a nickname to LDEV 0 to 19 my_volume to 19 Set to 2 the MP blade ID of LDEV 0 to 19 Figure 5 3 Script examples of internal open system volume operation 1 2 Provisioning operations with CCI 5 23 Hitachi Command Control Interface User and Reference Guide raidcom get Idev Idev_id 0 cnt 20 for l S i in 0 1 9 do raidcom add device_grp device_grp_name grpl data i Idev_id i for I S i in 10 1 19 do raidcom add device_grp device_grp_name grp2 data i Idev_id i raidcom get command_status raidcom reset command_status raidcom get device_grp device_grp_name egrpl raidcom get device_grp device_grp_name grp2 Display the information of LDEV 0 to gt 19 Internal VOL
132. 2 shows the supported communication 32 bit 64 bit among different OSs Please note the following terms that are used in the example e RM H Value of HORCMFCTBL environment variable for an HP UX CCI instance on Windows CCI software environment 2 11 Hitachi Command Control Interface User and Reference Guide e RM S Value of HORCMFCTBL environment variable for a Solaris CCI instance on Windows Restriction CCI s communications among different operating systems is supported on HP UX Solaris AIX Linux and Windows this is not supported on Tru64 UNIX Digital UNIX Also CCI does not require that the HORCMFCTBL environment variable be set except for RM H and RM S instances to ensure that the behavior of the operating system platform is consistent across different operating systems Solaris S i Solaris j HP UX Command device Command device E a E S VOL S VOL Ww S RAID Figure 2 10 CCI communication among different operating systems Table 2 1 Supported CCI HORCM communication HORCM 32 bit HORCM 64 bit little big little big little big little big Configuration definition file Overview 2 12 The CCI configuration definition file is a text file that defines a CCI instance The connected hosts volumes and groups known to the CCI instance are defined in the configuration definition file Physical volumes special files used independently by the servers are combined
133. 2EE8 FEEC An internal error occurred Call Hitachi Data Systems Support Center Table 9 26 SSB codes that are returned by raidcom modify Idev ssid command raidcom modify Idev ssid Error code Error message E Description y SSB1 SSB2 CMDRJE Executing 2E11 0023 SSID cannot be changed because there are LDEVs in the boundary where the specified LDEV belongs CMDRIJE Executing 2E22 7201 The specified SSID is used for the other boundary CMDRJE Executing 2EE8 FEEC An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing 2EF3 0002 The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 27 SSB codes that are returned by raidcom modify Idev status nml command raidcom modify Idev status nmi Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description It exceeds the range of LDEV number Get Command Status Async The specified LDEV is used as a ShadowImage pair Get Command Status Async The specified LDEV is used as a TrueCopy pair ora Universal Replicator pair Get Command Status Async The specified LDEV is used as a Compatible FlashCopy V2 relationship Get Command Status Async The specified LDEV is used as a Thin Image or Copy on Write Snapshot pair Get Command Status Async The specified LDEV is used as a system dis
134. 30015 dev_name dev_name dev_name dev rdsk c1itodo HORCM_DEV dev_group dev_name port TargetID LU MU oradb oradb1 CL1 A 3 1 0 oradb oradb2 CL1 A 3 1 1 CCI software environment 2 13 Hitachi Command Control Interface User and Reference Guide oralog oralogl CL1 A 5 0 oralog oralog2 CL1 Al 5 0 oralog oralog3 CL1 Al 5 1 oralog oralog4 CL1 Al 5 1 HORCM_INST dev_group ip address service oradb HST2 horcm oradb HST3 horcm oralog HST3 horcem h1 Configuration file example Windows servers Ej horcmU cont Notepad Cay x File Edit Searca Help HORCH_MON Hip_address service huren poll 16ms 1566 dev_name PHYS ICALDRIVE2 HORCH DEW dev_name kate kate2 oradb3 ip_address PULLUX service horem timeout 16ms 1666 dev_name TargetID 6 The following table lists the parameters defined in the configuration file and specifies the default value type and limit for each parameter Table 2 2 Configuration HORCM_CONF parameters Parameter ip_address Default Character string 63 characters Service Character string value or numeric 15 characters poll 10 ms Numeric value None timeout 10 ms Numeric value None dev_name for HORCM_CMD Character string 63 characters Recommended value 8 char or fewer dev_name for HORCM_DEV 2 14 Character string CCI software environment 31 characters Hitac
135. 31 log and trace files 2 35 OpenVMS 2 35 UNIX 2 32 user created scripts 2 44 Windows 2 33 H HORCM_CMD 2 16 HORCM_DEV 2 20 HORCM_INST 2 22 HORCM_INSTP 2 24 2 25 HORCM_LDEV 2 23 HORCM_LDEVG 2 24 HORCM_MON 2 15 horcm conf file 6 45 host components 2 9 and pairing 2 11 HORCM 2 9 instance configurations 2 9 host group check 3 22 Index 2 I in band command execution 3 2 in system replication 1 8 instance number 2 4 instance parameter HORCM_INST 2 22 internal volumes creating 5 19 5 20 operations 5 19 L LDEV adding 3 32 check 3 17 deleting 3 33 LDEV group function 3 25 LDEV group parameter HORCM_LDEVG 2 24 LDEV grouping 1 7 LDEV nickname 1 7 5 5 LDEV parameter HORCM_LDEV 2 23 line by line mode 1 3 1 4 3 15 3 16 log and trace files 2 35 command error logging for audit 2 39 log files 2 36 environment variables for log directories 2 38 names and locations 2 37 logging command errors for audit 2 39 mirror descriptors and group assignment configuration files 2 25 and volumes 7 7 mirroring duplicated 6 6 monitor parameter HORCM_MON 2 15 MxN configuration and control 6 44 O OpenVMS files 2 35 starting up one instance 4 4 starting up two instances 4 5 Oracle protection of volume 7 4 restrictions with Database Validator 7 4 out of band command execution 3 2 P pairdisplay examples on HOST1 and HOST2 2 29 paired volumes 6 2 parameters configuration 2 14 permission command
136. 39 dg_jn11 datal 514 64539 dg_jn11 datal 515 64539 C HORCM etc gt raidcom add journal journal_id 2 grp_opt Idev device_grp_name dg_jnlii GROUP dg jnll DEVICE datal UnitID 0 LDEV 512 0x0200 1 PORT none LUN none done GROUP dg jnll DEVICE datal UnitID 0 LDEV 513 0x0201 1 PORT none LUN none done GROUP dg jnll DEVICE datal UnitID 0 LDEV 514 0x0202 1 PORT none LUN none done GROUP dg jnll DEVICE datal UnitID 0 LDEV 515 0x0203 1 PORT none LUN none done Common operations when executing provisioning operations When executing each provisioning operation log in log out lock resources unlock resources and view resource group information using the following operational flow Contents of operation Command of Execution Logging in Specify your user name and raidcom login lt user_name gt password to log in lt password gt Locking Lock the resource group raidcom lock resource resource group resource name lt resource group name gt time lt time sec gt Provisioning Execute provisioning operations operations Unlocking Unlock the resource group raidcom unlock resource resource group resource name lt resource group name gt Displaying a Displays a resource group raidcom get resource resource group information and confirms a information resource group i
137. 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 e ingqraid fg ls dev rdsk c57 ingraid CLI fg DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID c57t4d0o CL2 D 1 62500 256 OPEN 3 CVS CM c57t4d1 CL2 D 1 62500 257 s P ss 0005 1 01 02 OPEN 3 CVS c57t4d2 CL2 D 1 62500 258 s P ss 0005 1 01 02 OPEN 3 CVS Using CCI SLPR security 8 16 The Virtual Partition Manager feature of the RAID storage systems USP V VM and TagmaStore USP TagmaStore NSC supports storage logical partitioning SLPR a feature that partitions the ports and volumes of the RAID storage system If CCI does not have SLPR security then it can operate the target volumes crossing SLPR through the command device The purpose of CCI SLPR security is to prevent CCI from operating the volumes on another SLPR SLPR N through the command device from the SLPR SLPR M that is assigned to its Host You can use CCI SLPR Security by defining the command device through the Virtual Partition Manager feature so that CCI can protect the target volume The following example represents the SLPR protection facility Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide Figure 8 6 Protection of the command device that has the SLPR attribute Legend e SLPR split of storage e SLPR M split number M of st
138. 68 P VOL PSUS 30053 272 W oradb oradevi L CL1 D 3 2 30053 268 S VOL PAIR 266 oradb oradev11 R CL1 D 3 4 0 30053 270 S VOL PAIR 268 Figure 2 22 Pairdisplay for ShadowImage on HOST2 HORCMINST LS Seg 30053 idevirdsk cOt3d4 272 pairdisplay g oradb1 m cas Group PairVol U R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradev11 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradev11 R CL1 D 3 2 0 30053 268 P VOL PAIR 30053 270 oradev21 R CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 oradev1 R CL1 D 3 2 30053 268 S VOL PAIR 266 pairdisplay d dev rdsk cOt3d4 m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb1 oradev11 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradb2 oradev11 R CL1 D 3 2 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 R CL1 D 3 2 1 30053 268 P VOLPSUS 30053 272 W oradb oradev1 R CL1 D 3 2 30053 268 S VOL PAIR 266 Figure 2 23 Pairdisplay for ShadowImage on HOST2 HORCMINSTO CCI software files The CCI software consists of files supplied with the software log files created internally and files created by the user These files are stored on the local disk in the server machine e CCI files supplied with the software on page 2 32 e CCI log and trace files on page 2 35 e User environment variable on page 2 44 CCI software environment 2 31 Hitachi Command
139. 8 8 Operation across SLPRs using two command devices on a single host To operate SLPR N share the command device If RMINST1 has a shared command device for SLPR N the paircreate command is permitted Additionally the raidscan p CL3 A command via RMINSTO is permitted to scan a port because the shared command device has the Bitmap settings SLPR M and SLPR N Figure 8 9 Operation across SLPRs using a shared command device on a single host Examples of using CCI commands 8 19 Hitachi Command Control Interface User and Reference Guide Dual Hosts In the following example the paircreate command is unable to operate the paired volume because 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 the specified port is different than the SLPR of the command device Figure 8 10 SLPR configuration on dual hosts To operate SLPR N assign the command device If HostB has a command device for SLPR N the paircreate command is permitted However the raidscan p CL3 A command via HostA is unable to scan a port because the specified port is different than the SLPR of the command device In this case raidscan p CL3 A command must be operated via HostB Figure 8 11 Operation across SLPRs using two command devices on dual hosts 8 20 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guid
140. 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 CE2 D 1 fdas 05 45 1 L 257 se seunas ees SMPL CL2 D 1 da 0 4 2 1 258 SMPL 2 Command option including a host group CCI supports new option for the following commands in order to show a LUN on the host view by finding a host group via the specified device e raidscan pdg lt device gt raidar pdg lt device gt raidvchkscan pdg lt device gt raidscan pdg dev rdsk c57t4d1 PORTH ALPA C TID LU Num LDEV P S Status Fence LDEV P Seq P LDEV Examples of using CCI commands 8 15 Hitachi Command Control Interface User and Reference Guide CL2 D 1 da 0 4 0 1 256 SMP SSee 6 ams CL2 D 1 da 0 4 61 257 ccc sea ae als SMPL CL2 D 1 da 0 4 2 1 258 SMP ses eee sees Specified device hgrp 1 is LDEV 0257 e raidscan findg ls dev rdsk c57 raidscan findg DEVICE FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT ID dev rdsk c57t4d0 0 F cCh2 D 1 4 0 62500 256 OPEN3 CVS CM dev rdsk c57t4d1 0 F cCh2 D 1 4 1 62500 257 OPEN3 CVS dev rdsk c57t4d2 0 F Ch2 D 1 4 2 62500 258 OPEN3 CVS e raidscan findg conf mkconf gg ls dev rdsk c57 raidscan findg conf 0 g ORA HORCM_DEV dev_group dev_name port TargetID LU MU dev rdsk c57t4d1 SER
141. CI instances CCI software environment Hitachi Command Control Interface User and Reference Guide e One host connected to two storage systems Connecting the host to two storage systems enables you to migrate data or implement disaster recovery by maintaining duplicate sets of data in two different storage systems You can implement disaster recovery solutions by placing the storage systems in different geographic areas Each CCI instance has its own operation manager server software and scripts and commands and each CCI instance communicates independently with the command device Each RAID storage system has a command device that communicates with each CCI instance independently Each storage system contains the primary volumes of its connected CCI instance and the secondary volumes of the other CCI instance located on the same host in this case e Two hosts connected to one storage system Having two attached hosts to one storage system one host for the primary volume and the other host for the secondary volume allows you to maintain and administer the primary volumes while the secondary volumes can be taken offline for testing The CCI instances of separate hosts are connected via the LAN so that they can maintain awareness of each other The RAID storage system contains the command device that communicates with both CCI instances one on each host and the primary and secondary volumes of both CCI instances e Two hosts connected to t
142. CM usr bin commands have no console window and can therefore be used from the application e The HORCM usr bin commands do not support the directory mounted volumes in subcommands e HORCM Tool TRCLOG bat is a troubleshooting tool This tool is not usually used e HORCM etc rmsra exe is the binary data used for cooperation with VMware This is used directly by VMware not usually used by users 2 34 Hitachi Command Control Interface User and Reference Guide CCI software environment CCI files for O penVMS based systems HORCM File name ROOT HORCM etc horcmgr exe Command name horcmd HORCM_CONF ROOT HORCM etc horcm conf Takeover ROOT HORCM usr bin horctakeover exe horctakeover Volume accessibility check ROOT HORCM usr bin paircurchk exe paircurchk Pair generation ROOT HORCM usr bin paircreate exe paircreate Pair splitting ROOT HORCM usr bin pairsplit exe pairsplit Pair re synchronization ROOT HORCM usr bin pairresync exe pairresync Event waiting ROOT HORCM usr bin pairevtwait exe pairevtwait Error notification ROOT HORCM usr bin pairmon exe pairmon Volume checking ROOT HORCM usr bin pairvolchk exe pairvolchk Pair config confirmation ROOT HORCM usr bin pairdisplay exe pairdisplay RAID scan ROOT HORCM usr bin raidscan exe raidscan RAID activity report ROOT HORCM usr bi
143. CM_LDEVG Kcopy group Idev_group Serial MDB Cerpo4 30036 Copy Group dbB Store the information in the storage system Read the information in the storage system Copy Group dbA Device Group grp Device Group grp03 _ oradb0 oradb02 l Device Group grp04 in F 01 02 or adb03 oradb04 Serial 30035 Serial 30036 Figure 3 4 LDEV grouping for VSP and later device group and copy group However for executing replication function commands in CCI two device groups must be combined and defined as a copy group 3 28 CCI functions Hitachi Command Control Interface User and Reference Guide When defining a device group or copy group by a command the command can be issued from multiple CCI instances because the group information is defined in the storage system Device group definition methods To define a device group or copy group in the CCI that supports Virtual Storage Platform or later use one or both of following methods Execute a command Create a device group with the raidcom add device_grp command and execute the raidcom add copy_grp command specifying the name of the device group to define a copy group When the command is executed a description corresponding to HORCM_LDEV of CCI is defined in the storage system Then define HORCM LDEVG in the configuration file to incorporate it into the CCI instance This can be executed at CCI that su
144. CU Status numbers in the RCU is not unified at the path that is specified creation or deletion CMDRJE Executing 2E00 7100 The CU number is out of effective range CMDRJE Executing 2E11 8004 The operation cannot be done because the microcode is being changed CMDRJE Executing 2E20 3000 The serial number the product ID or the SSID of the target storage system is incorrect CMDRJE Executing 2E20 3001 The attribute of the RCU cannot be changed because the specified RCU is not registered Get Command Async 2E21 7101 The specified CU number is not defined or an Status LDEV is not defined under the CU number CMDRJE Executing 2E23 3101 The operation cannot be done because the number of paths becomes less than the least path number Get Command Async 2E31 3001 Command cannot be executed because the RCU Status identification code of a path is invalid CMDRJE Executing 2ED6 OOEF An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing 2ED6 3300 The value of SSID for the remote storage system is invalid Table 9 46 SSB codes that are returned by raidcom delete rcu_path command raidcom delete rcu_path Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description The CU of RCU exceeds the effective value CMDRJE Executing The product ID or the path registration ID is invalid Get Command Status Async Command cannot be executed
145. Command Control Interface User and Reference Guide Command Description Specifies access mode to S VOL after splitting a pair Operation in open systems r Read only rw Read write enabled Operation in mainframe systems The volume cannot be read regardless of specified options This option is only for TrueCopy TrueCopy for Mainframe Universal Replicator and Universal Replicator for Mainframe You cannot specify this option in ShadowImage or ShadowImage for Mainframe If the capacity of the S VOL is larger than that of the P VOL you cannot create a pair with CCI To create a TrueCopy for Mainframe pair with volumes that differ in capacity use Business Continuity Manager or Storage Navigator Notes e A mainframe primary volume may also be called a source volume or a main volume e A mainframe secondary volume may also be called a target volume or a remote volume Global virtualization function VSP G1000 only The global virtualization function enables you to minimize rewrites of configuration definition files horcm conf when you operate volumes migrated from other storage system models to the VSP G1000 For details on the global virtualization function see the Provisioning Guide for Open Systems System configuration example with the global virtualization function This topic shows a system configuration with the global virtualization function In this configura
146. Command device setting Reading of Group device group or Securit User 7 copy group y authentication informallon information HORCM_LDEVG Security to be set acquisition Not defined Do not read No security Do not read Only HORCM_DEV allowed Read User authentication required Do not read User authentication required Only HORCM_DEV allowed Read CMD security Do not read CMD security Only HORCM_DEV allowed Read CMD security User authentication required Do not read CMD security User authentication required Only HORCM_DEV allowed 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 group A device group is created by specifying a device name and a device group name Once a device group is created the device group name the LDEV number and the information if there is copy group 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 279 LDEVs can be placed under the device group And one LDEV can be placed in multiple device groups Notes when specifying a device name e Multiple device names can be defined in one LDEV Max 1 024 names e The lengt
147. Context Check error C HORCM etc gt raidcom delete host_grp port CL1 A 2 raidcom PORT HGRP 0 2 does not exist as status is 2 on UnitID 0 raidcom_ 4 EX_CTXCHK Context Check error Configuration check The contents of a script file can be checked whether the operation is performed for the existing resource or not Before performing the configuration check execute the following command acquire the current configuration information and store it in the work file specified by the store option Check the operation for LDEV raidcom get ldev ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device grp name lt device group name gt lt device names store lt work file gt Check the operation for Port raidcom get port port store lt work file gt Check the operation for Host group raidcom get host_grp port lt port gt store lt work file gt After acquiring the configuration information execute the script by specifying the configuration file raidcom zt lt created script file name gt load lt work file gt Resource location and parameter MP blade location and parameter 3 24 To specify MP blade IDs by the raidcom add Idev command specify the following IDs CCI functions Hitachi Command Control Interface User and Reference Guide Table 3 7 MP blade names and parameters for VSP G1000 MP blade name MP blade
148. DEV and HORCM_INST on horcm conf If you want to know permitted volumes at raidscan use raidscan find The find option shows device file name and storage system information by using internal Inquiry result You can use raidscan find to make horcm conf because only permitted volumes are shown with host side view Following is an example for HP UX systems ioscan fun grep rdsk raidscan find DEVICE FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT ID dev rdsk c0t3d0 0 F CL1 D 3 0 35013 aly Data protection operations with CCI 7 9 Hitachi Command Control Interface User and Reference Guide OPEN 3 dev rdsk c0t3d1 0 F CL1 D 3 1 35013 18 OPEN 3 permission command CCI recognizes permitted volumes at the result of the permission command The permission command is the find inst option of raidscan This option issues an inquiry to a specified device file to get Ser and LDEV from the RAID storage system and checks an identification for volumes of horcm conf to all of own host volumes then stores the result within HORCM of the instance This permission command is started by etc horcmgr automatically The following example shows the relation between the device file and horcm conf for a manual operation on an HP UX system All volumes of ioscan are permitted ioscan fun grep rdsk raidscan find inst DEVICE FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c0t3d0 oradb oradevl CL1 D 3 0 35013 17 de
149. DRJE Error message An order to the control command device was rejected Condition The request to the command device failed or was rejected Note This error code is sometimes caused by the operating system and reported as EX_CMDIOE instead of EX_CMDRJE see next row Recommended action Verify TrueCopy ShadowImage functions are installed Verify ports are set Verify CU paths have been established Verify that the target volume is available CCI displays SSB in the output of the commands soa service representative can identify the cause of EX_CMDRIJE except for Tru64 DYNIX Example paircreate g G1 f never vl nocopy paircreate EX_CMDRJE An order to the control command device was rejected Refer to the command log HORCM 10g10 horec_ul 1 log for details It was rejected due to SKEY 0x05 ASC 0x26 SSB 0xB9BF 0xB9C7 on Serial 63502 EX_CMDIOE Control command I O error or rejected A read write to the command device failed with an I O error or was rejected Refer to the host syslog file and investigate the cause of the error If the cause is Illegal Request 0x05 Sense Key please confirm the following items Verify TrueCopy ShadowImage functions are installed Verify ports are set Verify CU paths have been established Verify that the target volume is available If the problem persists contact the Hitachi Data Systems Support Cente
150. Executing A pair cannot be created because there is not enough free shared memory space Executing The command ends abnormally because other than the raidcom add snapshot command is issued for the volume other than the Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the pair is in the state of unacceptable the command Executing The Thin Image or Copy on Write Snapshot pair cannot be restored because the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a TrueCopy pair Troubleshooting 9 69 Hitachi Command Control Interface User and Reference Guide raidcom modify snapshot Error message Executing Async Executing Error code SSB1 SSB2 Description The Thin Image or Copy on Write Snapshot pair cannot be restored because the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a Universal Replicator pair Executing The Thin Image or Copy on Write Snapshot pair cannot be restored due to one of the following reasons e Snapshot data of a restore target Thin Image or Copy on Write Snapshot pair is being obtained per consistency group Snapshot data of a different pair whose primary volume is the restore target P VOL of a Thin Image or Copy on Write Snapshot pair is being obtained per consistency group Executing An error occurred at th
151. Executing Error code Async spi ssB2 Error message Description Executing The value of pool ID is out of range Executing The pool name cannot be changed because the pool configuration is being changed Executing Invalid pool ID Executing The pool name is duplicated with another pool Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 36 SSB codes that are returned by raidcom delete pool command raidcom delete pool Executing Error code Async sspi ssB2 CMDRJE Executing LDEV exceeds the range CMDRJE Executing The value of pool ID is out of range Error message Description Get Command Async All pool volumes associated to a pool cannot be Status deleted Get Command Async The specified LDEV is in the state of blocked Status CMDRJE Executing This pool cannot be deleted because a volume in the pool is being deleted Get Command Async The operation cannot be done because the pool Status usage rate exceed the threshold value of the pool usage 9 56 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom delete pool Error message Executing Async Error code SSB1 SSB2 Description Get Command Async 2E10 600F The operation cannot be done because the Status current capacity rate exceeds th
152. Failback operation If this operation fails with EX_CMDRJE or EX_CMDIOE this is due to a FICON link down or site failure After a recovery from the failure perform the operation again Therefore this timeout value should be a greater than or equal to the start up timeout value for the MC amp CC Control Script PVOL takeover function A PVOL takeover relinquishes the pair state for a volume or group in order to make the P VOL writable following some type of error for example link down with DATA fence This function makes it so the takeover node alone can use the primary volume that is reading and writing are enabled on the assumption that the remote node possessing the secondary volume cannot be used The PVOL takeover function has two functions PVOL PSUE takeover and PVOL SMPL takeover A PVOL PSUE takeover forces the primary volume to suspend PSUE PSUS state which permits WRITEs to all primary volumes of the group even if the fence level is data Therefore PSUE and or PSUS are intermingled in the volume group through the action of this PVOLPSUE_ Takeover This intermingled pair status creates PSUE as the group status therefore the pairvolchk command results give precedence to PSUE PDUB status over PSUS for the group This special state returns back to its original state by issuing the pairresync command A PVOL SMPL Takeover forces the primary volume to simplex SMPL state so the pair is destroyed At first P
153. Give an nickname to LDEV 0 to 9 raidcom modify Idev Idev_id Whi device_name my_volume 0 ot 9 my_volume_ i for I S amp i in 0 1 9 do Set to 2 the LOEV owner WP blade of LDEV raidcom modify Idev Idev_id bi mp_blade id 2 lt 0 to 9 eP raidcom get Idev Idev_id 0 cnt 10 Display the information of LDEV 0 to 9 Internal VOL raidcom add dp_pool pool_id 1 Idev_id 0 ent 5 Use LDEV O to 4 then create pool 1 raidcom get command _status gt raidcom reset command_status raidcom modify pool pool 1 pool_attr ibute dt_manual Change the setting of pool 1 gt from Dynamic Provisioning pool to raidcom add dp_poo pool_id 1 Idev_id cent Dynamic Tiering pool p for I i in 10 1 19 do Add a pool volume of different media to raidcom add Idev Idev_id Whi capacity 10g Pool 1 LDEV 5 to 9 u Create each 10 of 10G WOL to Pool_id 1 for I S i in 20 1 29 do gt LDEV 10 to 19 20 to 29 raidcom add Idev Idev_id hi capacity 10g pool 1 raidcom get command_status raidcom reset command_status for 1 8 i in 10 1 29 do Give a nickname to WOL 10 to 29 raidcom modify Idev Idev_id bi device_name my_virtual_volume 10 to 29 my_virtual_volume_Si y for 1 S i in 10 1 29 do Set to 2 the VVOL owner WP blade of raidcom modify Idev Idev_id bi mp_blade_id 2 WOL 10 to 29 Figure 5 11 Script examples of virtual volume o
154. I 1 set HORCMINST 0 set HORCC_ LOG STDERROUT C HORCM etc horemstart exe exit 0 Starting the CCI instance from the service After you have confirmed starting and stopping using horcmstart 0 and horcmshutdown 0 you must verify that HORCMO starts from the service and that HORCMO started automatically from REBOOT using the following command C HORCM tool gt net start HORCMO Stopping CCI instance as a service Instead of using the horcmshutdown 0 command you must use the following command to stop HORCMO C HORCM tool gt net stop HORCMO By using the horcmshutdown 0 command the script written into HORCMO_run txt will automatically restart HORCMO Starting up CCI 4 7 Hitachi Command Control Interface User and Reference Guide 4 8 Starting up CCI Hitachi Command Control Interface User and Reference Guide Provisioning operations with CCI This chapter describes storage provisioning operations with CCI About provisioning operations O Available provisioning operations 1 Available provisioning operation specifying device grou O Common operations when executing provisioning operations O Resource group operations Internal volume operations O Virtual volume Dynamic Provisioning operations O Virtual volume Dynamic Provisioning for Mainframe operations O Virtual volume Dynamic Tiering operations External volume operations O Virtual Partition Manager operations
155. JE Executing 2E20 6000 Pool ID is not installed Get Command Async Status Get Command Async 2E21 8106 The operation cannot be performed because the Status shared memory SM is not initialized CMDRJE Executing 2E23 0008 The number of specified LDEVs is invalid CMDRJE Executing 2E30 0052 The specified LDEV cannot be deleted because it is a top VOL of the pool CMDRJE Executing 2E30 6003 The specified pool is a pool for Thin Image or Copy on Write Snapshot CMDRJE Executing 2EE7 OOEE The command cannot be accepted After a while execute the same command CMDRJE Executing 2EE7 OOF9 Pool ID is not installed CMDRJE Executing 2EE7 FEEC An internal error occurred Troubleshooting Call Hitachi Data Systems Support Center 9 57 Hitachi Command Control Interface User and Reference Guide raidcom delete pool Error message Executing Async Error code Executing 2EF3 Description The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 37 SSB codes that are returned by raidcom add snap_pool command raidcom add snap_pool Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The value of LDEV number is out of range CMDRJE Executing Pool ID is out of range CMDRJE Executing The type of pool is invalid CMDRJE Executing The maximum reserve ratio for V V
156. LUN by specifying a device group When the both of device group name and device name the operation is executed for the LDEV that matches to the specified device name in the device group If the device name is omitted to specify the operation is executed for all of the LDEVs belonging to the device group Information of the device group to be operated C HORCM etc gt raidcom get device _grp device grp name grpl LDEV_GROUP LDEV_NAME LDEV Serial data0 17000 64577 data0 17001 64577 datal 17002 64577 datal 17003 64577 Result The following shows the result when the raidcom add lun command is executed by specifying device group name grp1 and device name data 0 5 14 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide C HORCM etc gt raidcom add lun port CL8 A grp_ opt ldev device_grp name grpl data0 GROUP grpl DEVIC data0 UnitID 0 LD 17000 0x4268 1 PORT CL8 A LUN none raidcom LUN 0 0x0 will be used for adding done GROUP grpl DEVICE data0 UnitID 0 LD 17001 0x4269 1 PORT CL8 A LUN none raidcom LUN 1 0x1 will be used for adding done C HORCM etc gt raidcom get lun port CL8 A 0 PORT GID HMD LUN NUM LDEV Serial HMO_BITs CL8 A 0 LINUX IRIX 0 1 17000 64577 CL8 A 0O LINUX IRIX 1 1 17001 64577 The following shows the result when the raidcom add lun command is executed by specifying device
157. Manager on the remote host is running EX_ESTMON HORCM Monitor stopped HORC Manager monitoring was refused Please confirm the value of poll in the configuration file EX_UNWCMD Unknown command An unknown command was attempted Please confirm the command name EX_INCSTG Inconsistent status in group The pair status of a volume within a group is not identical to the status of the other volumes in the group Please confirm the pair status using the pairdisplay command EX_INVSTP Invalid pair status The pair status of the target volume is not appropriate Please confirm the pair status using the pairdisplay command EX_INVVOL Invalid volume status The volume status of the target volume is not appropriate Please confirm the volume status using the pairdisplay 1 or the raidvchkdsp v aou command EX_INVMUN 9 12 Invalid mu with HORC UR or HOMRCF The MU of the volume to be operated is not appropriate Troubleshooting Please confirm the MU MU 1 2 cannot be used for TrueCopy and must be P VOL for ShadowImage for the specified group using the pairdisplay command And also confirm the command execution environment to be set as HOMRCF Hitachi Command Control Interface User and Reference Guide Error code Error message Condition Recommended action EX_ENLDEV No such LDEV A de
158. OL is out of range Get Command Status Async The operation cannot be done because a SATA E drive in the state of quick formatting is in the specified LDEV Get Command Status Async The specified LDEV is in the state of blocked CMDRJE Executing The specified LDEV is in the state of blocked or not installed Get Command Status Async Thin Image cannot be used because there are not enough cache management devices to create pairs Get Command Status Async The pool cannot be created because there are not enough resources VDEV depending on cache management devices Get Command Status Async The operation cannot be performed because the pool volume is being deleted CMDRJE Get Command Status Executing Async The pool is not in the status where the pool volume can be added Get Command Status Async The operation cannot be done because the power supply is switched off CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async The specified LDEV is not installed Get Command Status Async The operation cannot be performed because the memory capacity of the shared memory SM is insufficient Get Command Status 9 58 Async The operation cannot be done because the SM for Thin Image or Copy on Write Snapshot is not initialized Troubleshoo
159. OL volume data are enabled if or due to an error condition PSUE suspended due to an error no error PFUS is PSUS due to internal error condition When a PSUE pair is occurs in PFUS is PSUS due to sidefile full resynchronized the RAID the primary storage system copies the entire volume P VOL to the S VOL same as initial copy PDUB Used only for TrueCopy LUSE Not used for ShadowImage R W R enabled pairs In paired state but enabled if updates to one or more LDEVs no error within the LUSE pair are occurs in suspended due to an error the primary condition volume Table 6 3 Universal Replicator pair status Secondary Universal Replicator Pair Status Primary R W enabled R enabled Unpaired volume R W enabled R W enabled The pair is synchronized Updates to the P VOL are duplicated on the S VOL In paired state but initial copy pairsplit or resync operation is not complete Includes COPY PD COPY SP and COPY RS status R W enabled R enabled 6 20 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Universal Replicator Pair Status The user has split the pair or released the pair the pair is no longer synchronized e The primary and secondary systems keep track of journal data discarded during the pairsplit operation When the operation is performed at the primary system the status of both the P VOL and S VOL changes
160. OPEN 3 Mountvol attached to Windows 2012 2008 2003 2000 systems Pay attention to the mountvol D command attached to a Windows system such that it does not flush the system buffer associated with the specified logical drive The mountvol command shows the volume mounted as Volume guid as follows mountvol Creates deletes or lists a volume mount point MOUNTVOL drive path VolumeName MOUNTVOL drive path D Examples of using CCI commands 8 5 Hitachi Command Control Interface User and Reference Guide MOUNTVOL drive path L Volume 56e4954a 28d5 4824 a408 3ff9a6521e5d G Volume b 48a3 95 0ef6 11d5 8d69 00c00d003b1le F You can determine what Volume guid is configured as follows ingraid Volume bf48a395 0ef6 11d5 8d69 00c00d003b1le CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID Vol146 Dsk1 CL2 K 61456 193 S s ss 0004 1 01 10 OPEN 3 raidscan pi Volume bf 48a395 Oef6 11d5 8d69 00c00d003ble find DEVICE FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT ID Vol146 Dsk1 0 F CL2 K 7 I 61456 193 OPEN 3 System buffer flushing function Drive Letter The logical drive to be flushed can be specified by the following two methods One method is that the logical drive for example G hd1 drive as below is specified immediately but this method must know about the logical drive corresponding to a group before executing the sync command Also the volume is mounti
161. OPS to write on the S VOL e If you attempt to write to the data on P VOL that does not still reflected the data to S VOL then ShadowImage 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 8 with IOPS to write on the P VOL e The state changes for pairsplit are WD Write Disable WE Write Enable If P VOL has non reflected data in PAIR state Behavior of OLD pairsplit at TO Behavior of first pairsplit at TO TO PVOL_PAIR from to SVOL_PAIR WD PVOL_PAIR from to SVOL_PAIR WD T1 PVOL_COPY from to SVOL_COPY WD PVOL_PSUS from to SVOL_COPY WE T2 PVOL_PSUS from to SVOL_SSUS WE PVOL_PSUS from to SVOL_SSUS WE If P VOL has been reflected all data to S VOL in PAIR state Behavior of OLD pairsplit at TO Behavior of First pairsplit at TO TO PVOL_PAIR from to SVOL_PAIR WD PVOL_PAIR from to SVOL_PAIR WD T1 PVOL_PSUS from to SVOL_SSUS WE PVOL_PSUS from to SVOL_SSUS WE e The state changes for paircreate split are Behavior of OLD paircreate split at TO Behavior of First paircreate split at TO TO SMPL from to SMPL SMPL from to SMPL T1 PVOL_COPY from to SVOL_COPY WD PVOL_PSUS from to SVOL_COPY WE T2 PVOL_PSUS from to SVOL_SSUS WE PVOL_PSUS from to SVOL_SSUS WE e If you attempt the pairevtwait s psus in PVOL_PSUS amp SVOL_COPY state then pairevtwait will return immediately even if the S VOL is still
162. ORCM core HORCM_LOG core_HOST_PID core Command core HORCM_LOG core_HOST_PID core HORCM_LOG core_HOST_PID core Note HOST denotes the host name of the corresponding machine PID denotes the process ID of that machine The location of the directory containing the log file depends on your command execution environment and the HORCM execution environment The command trace file and core file reside together under the directory specified in the HORCM execution environment A directory specified using the environment variable HORCM_LOG is used as the log directory in the HORCM execution environment If no directory is specified the directory tmp is used A directory specified using the environment variable HORCC_LOG is used as the log directory in the command execution environment If no directory is specified the directory HORCM log is used instance number A nonexistent directory may be specified as a log directory using the environment variable 2 37 CCI software environment Hitachi Command Control Interface User and Reference Guide Table 2 5 Environment variables for log directories Directory name Definition HORCM_LOG A directory specified using the environment variable HORCM_LOG The HORCM log file trace file and core file as well as the command trace file and core file are stored in this directory If no environment variable is specified HORCM log curlog is used HORCC_LOG CCI tra
163. Reference Guide C HORCM etc gt raidcom ldev ldev_id 1 cnt 65280 store ldevconf_65 gt ldevconf 65 txt C HORCM etc gt raidcom 3_defined_ldev bat load ldevconf_65 dat checkmode precheck C HORCM etc gt raidcom ldev parity_grp_id 01 01 ldev_id 1 capacity 100M C HORCM etc gt raidcom ldev parity_grp_id 01 01 ldev_id 2 capacity 100M C HORCM etc gt raidcom ldev parity_grp_id 01 01 ldev_id 3 capacity 100M e Example of script the text in bold indicates the part of incorrect configuration definition raidcom add ldev parity_grp_id 01 01 ldev_id 1 capacity raidcom add ldev parity_grp_id 01 01 ldev_id 2 capacity raidcom add ldev parity_grp_id 01 01 ldev_id capacity raidcom add ldev parity grp_ id 01 01 ldev id 3 raidcom add ldev parity grp_id 01 01 ldev_id 1 capacity 2 capacity 3 raidcom add ldev parity grp_ id 01 01 ldev id for 1 i in 1 1 3 do capacity raidcom add ldev parity_grp_id 01 01 ldev_id i capacity 100M for 1 i in 1 1 3 do raidcom add ldev parity grp id 01 01 ldev id i capacity 100M e Execution result the text in bold indicates the contents of the error accompanying the invalid configuration definition in the script CCI functions 3 19 Hitachi Command Control Interface User and Reference Guide 3 20 C HORCM etc gt raidcom ldev ldev_id 1 cnt 65280 store ldevconf_65 gt ldevconf 65 txt C HORCM etc gt raidcom 3_d
164. TACHI OPEN V HORC SMPL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL E LUN Group 08191 SSID 0x000B UNMAP Group 00000 SSID 0x000B dev sdw gt CHNO 0 TID 1 LUN 16 ot SQ CL2 G Ser 63528 LDEV 2769 HITACHI OPEN V HORC SMPL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL E LUN Group 16384 SSID 0x000B E LUN Group 16384 SSID 0x000B e Group This item shows physical position of an LDEV according to mapping of LDEV in the RAID storage system LDEV Mapping Display Formats RAID Group RAID1i Group Group number Sub number RAID5 Group Group number Sub number RAID6 Group Group number Sub number Copy on Write Snapshot S VOL SNAPS PoolID poolID number Unmapped UNMAP Group 00000 External LUN E LUN Group External Group number Relations between cc command issues and status The migration volumes can be handled by issuing the CCI commands pair creation and pair splitting commands The validity of the specified operation is checked according to the status of the paired volume primary volume Table 6 12 Command issues and pairing status transition on page 6 43 shows the relations between the migration volume statuses and command acceptances 6 42 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Table 6 12 Command issues and pairing status transition Command Pair Creation Pair Splitting Pairing Status CC m
165. The execution results of CL2 A and 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 Idev is used The following command is executed when the user has the authorities of LDEV number 10 and 12 raidcom get ldev ldev_id 10 cnt 3 Execution results of LDEV number 10 and 12 are displayed LDEV number 11 is not displayed because the user does not have the authority of the resource Resource lock function When the configuration changes from multiple CCI SVP or Storage Navigator are done to the same resource unexpected change is executed on each other and it might not be configure the expected configuration To prevent from the changing configuration for the same resource by each of the users the resource lock command is provided When this command is used the resource group can be locked for the other users that they cannot be used the specified resource group And even if the lock is not performed each configuration change command can be performed However the competition with the other application might cause an error The commands for performing the exclusive control and exclusive control r
166. Universal Replicator e pairresync e pairsplit e horctakeover e horctakeoff e paircreate Hitachi ShadowImage e pairresync e pairsplit e raidvchkset vt Database Validator e raidvchkset vs raidvchkset vg Data Retention Utility e raidvchkset vext Hitachi Dynamic Provisioning SSB codes returned by the configuration setting command raidcom Executing the configuration setting command raidcom command may return an SSB code An error may occur whether the command is executed synchronously or asynchronously For an asynchronous error the error information is displayed on the console by executing raidcom get command_status command When the error message shows CMDRJE or Get Command Status check the contents of SSB1 and SSB2 You can 9 20 Troubleshooting Hitachi Command Control Interface User and Reference Guide verify a content of an error by the raidcom get error_message command When you specify the SSB code with the raidcom get error_message command make sure not to specify a wrong SSB code The following tables provide information about each SSB code returned by the configuration setting command raidcom command If you see an error not described in the tables contact the Hitachi Data Systems Support Center Table 9 6 SSB codes returned by the configuration setting command common Error code Error message EE Description y SSB1 SSB2 CMDRJE Executing 2E10 8000 Unav
167. VOL takeover executes PVOL PSUE takeover If PVOL PSUE takeover fails it then executes PVOL SMPLtakeover PVOL takeover can be specified per paired logical volume or per volume group TrueCopy Async Universal Replicator specific behavior for pvol takeover PVOL Takeover will not be executed It will become a Nop Takeover since the Fence Level will be Async which is equal to Never so it is not needed to allow P VOL writes Data replication operations with CCI 6 15 Hitachi Command Control Interface User and Reference Guide TrueCopy remote commands 6 16 Figure 6 7 TrueCopy remote system configuration on page 6 17 illustrates a TrueCopy remote configuration The CCI TrueCopy remote commands assist the system operation with volume backups among UNIX servers and their operating system management functions The TrueCopy remote pair commands are also used to copy volumes in server failover configurations and to restore the volumes to their original state after a server failover has been recovered e Pair creation command Creates a new volume pair Volume pairs can be created in units of volume or group e Pair splitting command Splits a volume pair and allows read and write access to the secondary volume e Pair resynchronization command Resynchronizes a split volume pair based on the primary volume The primary volume remains accessible during resynchronization o Swaps p option TrueCopy only Swaps volume from the SVOL PVOL
168. WWN or SPM name raidcom modify spm_group _ prioritized or non prioritized threshold upper limit SPM group name raidcom add spm_wwn SPM name Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide SPM Operation raidcom add spm_group Management per port Management per system SPM group name raidcom delete spm_wwn SPM name SPM information per port is also deleted raidcom delete spm_group SPM group name SPM information per port is also deleted raidcom get spm_wwn prioritized or non prioritized upper limit WWN or SPM name SPM group name threshold raidcom get spm_group prioritized or non prioritized upper limit SPM group name threshold raidcom monitor spm_wwn performance of server IOps KBps control mode of SPM raidcom monitor spm_group performance of server IOps KBps State transitions of Server Priority Manager The following shows the state by the SPM operation and its state transition control mode of SPM Setting the SPM SPM group Not defined information for WWN WWN WWN WWN Trp SPM target p SPM target a l Withouta SPM Give a SPM With a SPM name name 4 Delete WWN from i by specifying WWN by specifying a WWN or the SPM SPM name name SPM group Defined WWN WWNY i SPM target _ SPM target nae Pr WithoutaSPM Give a SPM With a SPM Delete WWN from the name pee name SPM
169. Write Snapshot Executing It cannot be deleted because it is the last path of Universal Replicator Executing It cannot be deleted because the operation object LU is executing host I O Executing It cannot be deleted because the operation object LU is reserved Executing The command device is being used in the local Command Control Interface Executing A command device is being set Executing The command cannot be operated because the virtual LDEV is not defined yet Executing The value of LUN exceeds the maximum Executing The value of LDEV exceeds the maximum Executing The value of host group ID exceeds the maximum Executing The program product is not installed Executing Host group is not installed Executing An invalid LDEV exists in the specified LDEVs Executing The multiple LDEV cannot be specified Executing When the host mode option 60 is set LUN path of LUNO cannot be set or released Executing The LU path cannot be deleted because the virtual LDEV ID of the specified volume was deleted Executing Another LDEV is already mapped in the specified LUN Executing 9 52 The command device is being used in the local Command Control Interface Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 33 SSB codes that are returned by raidcom add lun command
170. _id lt pool ID gt pool_id lt pool ID gt pool_name lt pool naming gt ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp name lt device group name gt lt device names user_threshold lt gt Display pool information xraidcom get pool key lt keywords gt for Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot Delete pool for Dynamic xraidcom delete pool pool lt pool ID gt Provisioning Dynamic lt pool naming gt Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot Change the threshold raidcom modify pool pool lt pool ID gt lt pool value of a pool for naming gt user_ threshold lt threshold_1 gt Dynamic Provisioning lt threshold 2 gt Dynamic Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot Restore a pool for raidcom modify pool pool lt pool ID gt lt pool Dynamic Provisioning naming gt status nml Dynamic Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot Set the maximum rate of raidcom modify pool pool lt pool ID gt lt pool subscription of a pool for naming gt subscription lt gt Dynamic Provisioning Dynamic Provisioning for Mainframe Dynamic Tiering 5 8 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation type
171. aai PVOL 266 9 0 pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEVi t M oradb oradevi L CL1 D 3 0 0 30053 266 P VOL PAIR 30053 268 oradb oradev1 R CL1 D 3 2 0 30053 268 S VOL PAIR 266 oradb1 oradev11 R CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 R CL1 D 3 2 2 30053 268 P VOL PAIR 30053 272 Figure 2 16 Pairdisplay on HORCMINSTO pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradevi L CL1 D 3 2 0 30053 268 S VOL PAIR 266 oradb1 oradev11 L CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 3 2 2 30053 268 P VOL PAIR 30053 272 oradb oradev1 R CL1 D 3 0 0 30053 266 P VOLPAIR 30053 268 Figure 2 17 Pairdisplay on HORCMINST1 Oradb1 5 idevirdsk c0t3ad4 pairdisplay d dev rdsk cOt3d4 m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEVi M oradb1 oradevi1 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradb1 oradev11 R CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb oradev1 R CL1 D 3 2 0 30053 268 5 VOL PAIR 266 oradb2 oradev21 R CL1 D 3 2 2 30053 268 P VOL PAIR 30053 272 Figure 2 18 Pairdisplay on HORCMINSTO 2 28 CCI software environment Hitachi Command Control Interface User and Reference Guide Cascading connections for Tr
172. able see Alternate command device function on page 2 5 The mapped command devices can be identified by the CM of product ID field of the ingraid command ls dev rdsk c1t0 HORCM usr bin ingqraid CLI sort DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID clt0d0s2 CL2 E 63502 576 OPEN V CM clt0dls2 CL2 E 63502 577 s s ss 0006 1 02 01 OPEN V SUN clt0d2s2 CL2 E 63502 578 s s ss 0006 1 02 01 OPEN V SUN The command device of UNIX host Solaris is described in the following dev rdsk c1tid0s2 The command device of Windows host is described as follows PhysicalDrive2 or CMD 63502 After the process of command device mapping set HORCM_CMD of the configuration definition file as follows e CMD lt Serial Number gt lt Device special file name gt lt Serial Number gt Sets the serial number For VSP G1000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 lt Device special file name gt Sets the device special file name of a command device Example When the serial number 64015 and device special file name dev rdsk is specified CCI software environment Hitachi Command Control Interface User and Reference Guide HORCM_CMD dev_name dev_name dev_name CMD 64015 dev rdsk Out of band method When executing commands using the out of band method create a virtual command device To create a virtual command device
173. able 9 56 SSB codes that are returned by raidcom delete copy_grp command raidcom delete copy_grp Executing Error code Async sspi ssB2 Error message Description CMDRJE Executing The copy group is not installed Invalid Character Executing Unavailable character is included in the name of copy group Table 9 57 SSB codes that are returned by raidcom modify port port_speed command raidcom modify port port_speed Executing Error code Error message Async sspi ssB2 Description Executing The specified AL PA is invalid Executing The specified topology is invalid Executing The other than fabric on cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The other than P to P point to point cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet 9 88 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify port port_speed Error code Executing Async sspi ssB2 Error message Description Executing The command device being used at the local CCI exists under the port Executing The program product is not installed Executing Invalid host speed is set for 4Gbps fibre adapter The available host speeds are AUTO 1G 2G and 4G only Executing Invalid host speed is set for 8Gbps Fibre Adapter The av
174. able range Get Command Async The specified LDEV is used for Volume Migration Status 9 50 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify Idev quorum_enable Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The specified LDEV cannot be configured because the LDEV is a virtual volume Get Command Status Async The specified quorum disk ID is being used Get Command Status Async The specified quorum disk is in processing Get Command Status Async The specified quorum disk is used as the quorum disk of the different device Get Command Status Async The specified LDEV is used as the quorum disk Get Command Status Async The specified LDEV is being blocked CMDRJE Executing The specified LDEV is used for other operation Get Command Status Async The specified LDEV is not the first LDEV that belongs to the external volume group CMDRJE Executing LDEV is not installed Get Command Status Async The specified LDEV is not an external volume Get Command Status Async A shared memory is not installed Get Command Status Async Cache Residency Manager is set to the specified volume Get Command Status Async A path is defined to the specified volume Get Command Status Async The
175. abled R W disable Notes 1 V VOL unmapped to the S VOL of a Copy on Write Snapshot will reply to a SCSI Inquiry but Reading and or Writing is not allowed Reading and writing are enabled as long as no failure occurs in the primary volume Pair status relationship to Copy on Write Snapshot commands Table 6 11 Pair status relationship to Copy on Write Snapshot commands on page 6 36 applies to a Copy on Write Snapshot context It explains 1 what a pair status may be prior to any CCI command execution 2 what the result would be after giving a CCI command and 3 what the pair status may be if the CCI command is Accepted Table 6 11 Pair status relationship to Copy on Write Snapshot commands Copy on Write Snapshot Command pai rcreate pairsplit pairresync Pair Status SMPL No split Accepted 2 split Rejected E option Rejected C option Rejected S option Acceptable Resync Rejected COPY RCPY Acceptable Rejected Rejected Accepted Accepted 1 Acceptable PAIR Acceptable Accepted 4 Rejected Accepted Accepted 1 Acceptable PSUS PFUS Rejected Acceptable Rejected Accepted Accepted 1 Accepted 2 5 PSUE Rejected Rejected Rejected Rejected Accepted 1 Accepted 2 A command is accepted and issued Whether this command is executed or not depends on the microcode versi
176. ad and write commands to the command device When CCI receives an error notification in reply to a read or write request to the RAID storage system the CCI software switches to an alternate command device if one is defined If a command device is blocked for example for online maintenance you can switch to an alternate command device manually If no alternate command device is defined or available all TrueCopy and ShadowImage commands terminate abnormally and the host will not be able to issue commands to the storage CCI software environment Hitachi Command Control Interface User and Reference Guide system Therefore one or more alternate command devices see Alternate command device function on page 2 5 must be set to avoid data loss and storage system downtime Each command device must be set using the LUN Manager software on Storage Navigator In addition for using a Provisioning command user authentication is required Set the security attribute of the command device with user authentication For information and instructions on setting a command device see the Provisioning Guide for the storage system Each command device must also be defined in the HORCM_CMD section of the configuration file for the CCI instance on the attached host If an alternate command device is not defined in the configuration file the CCI software may not be able to use the device The CCI Data Protection Facility uses an enhanced command device that
177. age Copy on Write Snapshot pair and the S VOL of a ShadowImage pair Executing A Snapshot data cannot be obtained because the TrueCopy asynchronous pair status is other than PSUS or PSUE when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a TrueCopy asynchronous pair Executing The operation cannot be performed because the Quick Restore is being operated on the specified ShadowImage P VOL Executing A pair operation cannot be performed because the volume using two mirrors included in the 3DC multi target configuration 3DC cascade configuration or 3DC delta resync configuration by the three Universal Replicator sites is specified Executing A Thin Image pair operation cannot be performed because the pair status of all Thin Image pairs sharing the specified P VOL is PSUE Executing The Thin Image pair operation cannot be performed because the virtual LDEV ID of the specified volume was deleted Executing A Thin Image or Copy on Write Snapshot pair cannot be created due to unavailable of the pool Executing A Snapshot data cannot be obtained because the pool or the pool VOL is blocked Executing A Thin Image or Copy on Write Snapshot pair cannot be created because there are not enough pair tables Executing A Thin Image or Copy on Write Snapshot pair cannot be created because there are not enough differential tables
178. ailable host speeds are AUTO 2G 4G and 8G only Executing The other than 10G cannot be specified when specifying a host speed of the package for Fibre Channel over Ethernet Executing Invalid host speed is set for 16Gbps Fibre Adapter The available host speeds are AUTO 2G 4G and 8G only Executing Topology FC AL and 16G as the host speed are not supported for the 16Gbps fibre adapter Table 9 58 SSB codes that are returned by raidcom modify port port_attribute command raidcom modify port port_attribute Error code Error message Scere Description sync SSB1 SSB2 CMDRJE Executing 2E00 8404 Invalid package CMDRJE Executing 2E10 8001 The operation cannot be done because another application for example Device Manager Storage Navigator and SVP is used CMDRJE Executing 2E10 8400 The specified port is blocked CMDRJE Executing 2E10 8402 There is a pair for TrueCopy Universal Replicator that is used the specified port CMDRJE Executing 2E10 8403 There is a pair for TrueCopy Universal Replicator that is used the specified port CMDRJE Executing 2E11 800D The storage system is in the state of start up Wait for a while then retry the operation CMDRJE Executing 2E20 8400 The specified port is not installed CMDRJE Executing 2E30 8403 There is a path for TrueCopy Universal Replicator in the specified port CMDRJE Executing 2E30 8406 There is an extern
179. ailable to operate because another Get Command Async application is in progress on Device Manager Status Storage Navigator or SVP CMDRJE Executing 2E11 2205 The resource group to which the operation object belongs is locked by the other user CMDRJE Executing 2E11 8303 The command cannot be executed because there is blocked part in the system CMDRJE Executing 2E31 9100 The command cannot be executed because the user authentication is not performed CMDRJE Executing 2EF4 0026 The virtual storage machine with the specified serial number was not found Table 9 7 SSB codes returned by raidcom add external_grp raidcom add external_grp Executing Error code Async sspi ssB2 CMDRJE Executing Invalid emulation type Error message Description Get Command Async There are not enough cache management Status devices CMDRJE Executing The external volume group is not in a effective range Get Command Async The external volume group exists already Status Get Command Async The specified CLPR does not exist Status CMDRJE Executing The volume cannot be mapped for online data migration because the emulation type is not OPEN V Executing Invalid attribute of the specified external volume group Executing The path group is not in a effective range Executing The value of specified port is not enabled Troubleshooting 9 21 Hitachi Command Control Interface User a
180. air cannot be created because the specified P VOL is a LUSE volume Executing A pair cannot be created because there is a pair in the specified primary volume which is using a different pool number from the specified pool number Executing The specified pair operation cannot be performed for the specified pool Executing The consistency group to be used in the specified Snapshot Group is in one of the following status e The number of pairs that can be defined in a consistency group exceeds the maximum The pair created by using the same P VOL already exists in the specified consistency group Executing The specified LDEV is not defined Executing The command ends abnormally because an unmounted volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the blocked volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume in formatting operation is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting 9 65 Hitachi Command Control Interface User and Reference Guide raid com add snapshot Executing Async Error message Executing Error code Description SSB1 SSB2 The command ends abnormally because an unmounted volume is specified as the S VOL of a Thin Image or Copy on Write Snapsho
181. al VOL path in the specified port CMDRJE Executing 2E30 8407 There is a path for TrueCopy Universal Replicator in the specified port CMDRJE Executing 2E30 8408 There is a path for TrueCopy Universal Replicator in the specified port Troubleshooting 9 89 Hitachi Command Control Interface User and Reference Guide raidcom modify port port_attribute Error code Executing Async sspi ssB2 Error message Description Executing An LU path has been defined Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 59 SSB codes that are returned by raidcom delete host_grp command raidcom delete host_grp Error code Error message See Description sync ssBi SSB2 CMDRJE Executing B956 302C The cancelling of the host mode option 61 setting was aborted CMDRJE Executing B956 304F The program product is not installed CMDRJE Executing B956 3071 The value of host group ID exceeds the maximum CMDRJE Executing B956 3077 The attribute of the specified port is Initiator or External CMDRJE Executing B956 3203 Deletion cannot be executed because the last path of ShadowImage is included in the host group CMDRJE Executing B956 320A Deletion cannot be executed because the last path of Thin Image or Copy on Write Snapshot is included in the host group CMDRJE Executing B956 3239 The command device being used at the local CCI exists u
182. al for the storage system for example Hitachi Virtual Storage Platform G1000 Product Overview Hitachi Virtual Storage Platform User and Reference Guide e The management software for the storage system for example Hitachi Command Suite Hitachi Device Manager Storage Navigator Storage Navigator and the applicable user manuals for example Hitachi Command Suite User Guide Hitachi Virtual Storage Platform G1000 Mainframe System Administrator Guide Hitachi Storage Navigator User Guide for VSP HUS VM USP V VM Product version This document revision applies to CCI version 01 32 03 01 or later Release notes The Release Notes provide information about the microcode DKCMAIN and SVP including new features and functions and changes The Release Notes are available on the Hitachi Data Systems Portal https portal hds com Document revision level Revision Description MK 90RD7010 00 October 2010 Initial release MK 90RD7010 01 December 2010 Supersedes and replaces MK 90RD7010 00 MK 90RD7010 02 January 2011 Supersedes and replaces MK 90RD7010 01 MK 90RD7010 03 April 2011 Supersedes and replaces MK 90RD7010 02 MK 90RD7010 04 August 2011 Supersedes and replaces MK 90RD7010 03 MK 90RD7010 05 November 2011 Supersedes and replaces MK 90RD7010 04 MK 90RD7010 06 March 2012 Supersedes and replaces MK 90RD7010 05 MK 90RD7010 07 June 2012 Supersedes and rep
183. ame raidcom modify spm_group port lt port gt spm_priority lt y n gt limit_io limit_kb limit_mb lt value gt spm_group lt group_name gt Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation overview Description Executed command Deleting Delete WWN from the raidcom delete spm_wwn port lt port gt WWN from SPM targets by specifying hba_wwn lt wwn_strings gt spm_name the SPM WWN or the SPM name lt nick_name gt targets Delete WWN from the raidcom delete spm_group port lt port gt SPM targets by specifying spm_group lt group_name gt the SPM group name Checking WWN of host bus adapters Displays the WWN of the host bus adapters that are registered in host groups Display example raidcom get hba_wwn port CL4 E 0 PORT GID GROUP NAME HWWN Serial NICK NAME CL4 E O Linux x86 210000e 08b0256f8 63528 ORA _NODEO CTL_0 CL4 E O Linux x86 210000e 08b039c15 63528 ORA _NODE1 CTL 1 Setting the priority on host bus adapter Set the high priority host bus adapter for the prioritized WWN and set the low priority host bus adapter for the non prioritized WWN You need to set the upper limit and the threshold with the priority The upper limit is set for the non prioritized WWN In the low priority server the frequency of the access to the storage system or the data traffic is restricted with the upper limit The thres
184. ame lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool name lt pool naming gt ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp_ name lt device group name gt lt device name gt user_threshold lt threshold_1 gt lt threshold 25 Creating LDEV V VOL Specifies the pool and creates LDEV V VOL raidcom add ldev pool lt pool ID gt lt pool naming gt snap ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Creating LDEV V VOL nicknames arbitrarily Creates LDEV V VOL nicknames This operation is optional raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Configuring MP blades of LDEVs V VOL Configures MP blades of created LDEVs V VOL raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Displaying a LDEV V VOL information Displays an information of created LDEV V VOL and confirms an execution result of the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keywords Script examples The following shows the script examples of virtual volume Dynamic Provisioning for mainframe operation 5 30 Provisioning operations with CCI Hitachi Command Control Inter
185. and data protection 7 10 port check 3 20 Hitachi Command Control Interface User and Reference Guide precheck 1 4 provisioning operations 5 1 R raidcom command configuration setting command 1 3 remote command device defining 2 6 replication 6 44 remote replication 1 8 remote volume discovery 6 55 replication cascading pairs 6 7 cascading volumes 6 8 duplicated mirroring 6 6 in system 1 8 local system configuration 6 17 operations 6 2 6 18 pair status 6 19 paired volumes 6 25 remote 1 8 remote system configuration 6 16 requirements 6 3 sidefile cache 6 27 volume status 6 19 resource group locking 1 8 resource lock function 3 14 restrictions cascading volumes 6 8 CCI operations 9 3 Data Retention Utility 7 3 Database Validator 7 4 replication 6 26 Volume Migration 6 43 S script files 2 44 content checking 3 16 SCSI command interface command competition 2 7 command flow 2 8 LDEVs 2 8 SCSI commands 2 6 sidefile 6 28 cache 6 27 SLPR configuration examples 8 18 security 8 16 security specify SLPR protection facility 8 17 Solaris dual pathing 2 3 2 17 SSB codes troubleshooting 9 19 starting as a service on Windows 4 6 one instance on OpenVMS 4 4 one instance on UNIX 4 2 one instance on Windows 4 3 two instance on OpenVMS 4 5 two instances on UNIX 4 2 two instances on Windows 4 3 synchronous commands processing 5 3 system log messages troubleshooting 9 6 T takeover commands 6 10 trace cont
186. and for discovering an external volume via the device file It is possible to discover the external volumes by using the ingraid command Example in Linux ls dev sd ingraid CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID sdh CL2 G 63528 15360 s s ss 0100 5 01 09 OPEN V sdu CL2 G 63528 2755 z s s ss 000B S 00001 OPEN 0V sdv CL2 G 63528 2768 s s ss 000B U 00000 OPEN OV sdw CL2 G 63528 2769 s s ss 000B E 16384 OPEN V e R Group This displays the physical position of an LDEV according to mapping of LDEV in the RAID storage system LDEV mapping RAID Group RAID Level RAID Group number Sub number RAID1 RAID5 RAID6 00000 External Group number Unmapped 1 5 6 Copy on Write Snapshot S VOL S PoolID number U E External LUN Example in Linux Data replication operations with CCI 6 41 Hitachi Command Control Interface User and Reference Guide ls dev sd ingraid dev sdh gt CHNO O TID 1 LUN He SQ CL2 G Ser 63528 LDEV 15360 HITACHI OPEN V HORC SMPL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 1 9 SSID 0x0100 dev sdu gt CHNO 0 TID 1 LUN 14 SQ CL2 G Ser 63528 LDEV 2755 HITACHI OPEN V HORC SMPL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL E LUN Group 00001 SSID 0x000B SNAPS PoolID 0001 SSID 0x000B dev sdv gt CHNO 0 TID 1 LUN 15 SQ CL2 G Ser 63528 LDEV 2768 HI
187. arding is enabled the RAID storage system conceals the target volumes from SCSI commands such as SCSI Inquiry and SCSI Read Capacity prevents reading and writing to the volume and protects the volume from being used as a copy volume the TrueCopy Universal Replicator or ShadowImage paircreate operation fails Overview 1 9 Hitachi Command Control Interface User and Reference Guide 1 10 Overview Hitachi Command Control Interface User and Reference Guide CCI software environment This chapter describes the CCI software environment rl Overview of the CCI software environment O CCI components on the RAID storage system CCI instance components on the host server O CCI software files O CCI log and trace files User created files O User environment variable CCI software environment 2 1 Hitachi Command Control Interface User and Reference Guide Overview of the CCI software environment The CCI software environment includes components on the Hitachi RAID storage systems and the CCI software on the host servers and or on the Storage Navigator computer The CCI components on the storage systems include the user data volumes and CCI command devices Each CCI instance on a host server includes e CCI application files referred to as HORC Manager HORCM o Log and trace files o Acommand server o Error monitoring and event reporting files o Aconfiguration management feature e Configuration definition file
188. are output on the syslog file e Title row first row e Command row second row e Result rows 3 132 rows the number of rows changes depending on the issuing command 2 42 CCI software environment Hitachi Command Control Interface User and Reference Guide Table 2 7 Display information of the title row Item Output example Syslog fixed output part Including the host name Jun 27 10 15 13 rmsolx86 raidcom ID 702911 user info It varies depending on the host OS Process ID PID 1234 Command status COMMAND NORMAL or COMMAND ERROR Separation User name Title EUserld for HORC User name of the host root user ID 0 Time that performed raidcom Wed Jun 27 10 15 13 2012 Table 2 8 Display information of the command row Item Output example Syslog fixed output part Including the Jun 27 10 15 13 rmsolx86 raidcom ID 702911 user info It varies depending on the host OS host name Process ID PID 1234 Title for performed CMDLINE command Performed command raidcom modify Idev ldev_id 1234 status nml Table 2 9 Display information of the result rows Item Output example Syslog fixed output part Including the host name Jun 27 10 15 13 rmsolx86 raidcom ID 702911 user info It varies depending on the host OS Process ID PID 1234 raidcom raidcom Rows for the error information EX_CMDRJE An o
189. are rejected with error code EX_ENPERM e The Data Protection Facility is based on the host side view at the result of Data Retention Utility You need to configure Data Retention Utility before CCI operation CCI checks Data Retention Utility by Inquiry within CCI e The Data Protection Facility can be enabled separately for each command device If you want to use protection and non protection modes in the same storage system at the same time you can define two or more command devices one with protection ON one with protection OFF Protection mode is enabled for the host that has Data Retention Utility and ON command device Examples for configuration and protected volumes Case 1 Two Hosts Figure 7 2 Example for the two host configuration on page 7 8 In protect mode Ora2 are rejected to operate the paired volume because of Unknown for Grp4 on HOST2 Data protection operations with CCI 7 7 Hitachi Command Control Interface User and Reference Guide Case 2 One Host Figure 7 3 Example for the one host configuration on page 7 8 In protect mode Oral and Ora2 are rejected to operate the paired volume because of Unknown for Grp2 and Grp4 on HOST1 If HOST1 has a protection OFF command device then Oral and Ora2 are permitted to operate the paired volume Note The Data Protection Facility is implemented by only CCI CCI needs AN to know the protection attribute for the command device whether should be permitted the opera
190. ate a deleting state Data replication operations with CCI 6 49 Hitachi Command Control Interface User and Reference Guide Notice on system operation CCI does not change the command options for supporting Universal Replicator MxN Open However the output of the command is added so that the command can display the CT group and Q Marker for each storage system because the CT group and Q Marker are managed on each storage system 1 CT group ID and journal ID for UR The CT group ID must be assigned used as the unique identifier across multiple storage systems Therefore the paircreate command makes a group volume having the same CT group ID across multiple storage systems 2 Cascading operation The FHORC option for cascading operation does not perform with CTQ Marker Mode Hence the cascading volume must not be specified UR MxN volume when using the FHORC option 3 Running HORCM daemon HORCM daemon process delivers the timestamps called the consistency Q Marker to the defined CT group Therefore if HORCM daemon is stopped then UR will stop to delta commit and will suspend because of Journal Full state Thus HORCM daemon must be running to keep the PAIR state 4 Separating a command device IO from application IO The HORCM daemon process issues IOs to the command device in order to deliver the timestamps to the defined CT group Therefore it is recommended to separate the command device path from the appli
191. ath ID must be specified between the site of P VOL and S VOL because the path ID is used at the paircreate command CCI software environment Hitachi Command Control Interface User and Reference Guide 8 HORCM_ALLOW_INST The HORCM_ALLOW_INST parameter is used to restrict the users using the virtual command device The allowed IP addresses and port numbers are as follows For IPv4 HORCM ALLOW INST ip address service 158 214 135 113 34000 158 214 135 114 34000 For IPv6 HORCM ALLOW INST ip address service e80 209 6bff febe 3c17 34000 Note If CCI clients not defined HORCM_ALLOW_INST HORCM instance starting up is rejected by SCSI check condition SGKEY 0x05 ASX Oxfe and CCI cannot be started up Configuration definition for cascading volume pairs The CCI software HORCM is capable of keeping track of up to seven pair associations per LDEV 1 for TrueCopy UR 3 for UR 3 for ShadowImage Copy on Write Snapshot 1 for Copy on Write Snapshot By this management CCI can be assigned to seven groups per actual LU that is described in the configuration definition file E gt UR orado 04 TrueCopy MU 0 Orad _L gt MUF Shadowlmage Oradb2 3 MU 1 2 Oradb7 MU 3 63 Figure 2 14 Mirror descriptors and group assignment Configuration file and mirror descriptors The group name and MU described in the HORCM_DEV parameter of a configuration definition file are assigned the co
192. ation Get Command Status Async The specified LDEV is a command device CMDRJE Get Command Status Executing Async The specified volume cannot be deleted because it is a LUSE volume Get Command Status Async This is a volume that the Data Retention Utility is set Get Command Status Async Volume Security is set to the specified LDEV Get Command Status Async The specified LDEV cannot be deleted because of online from the mainframe host Get Command Status Async The specified LDEV is a Data Retention Utility Volume Retention Manager attribute device Get Command Status Async This is a volume that the Volume Retention Manager is set Get Command Status Async The specified LDEV is used as a Compatible FlashCopy V2 or a Compatible Software for IBM FlashCopy SE relationship Get Command Status Async The specified LDEV is used as a Volume Migration Get Command Status Async The specified LDEV is used as a Volume Migration Get Command Status Async The specified LDEV is used as a system disk Get Command Status Async The specified LDEV is used as a system disk Get Command Status Async Troubleshooting The specified LDEV is a command device 9 85 Hitachi Command Control Interface User and Reference Guide raidcom delete Idev Error message Get Command Status Execut
193. because the parameter of specified RCU is invalid CMDRJE Executing The specified port on the side of RCU is invalid CMDRJE Get Command Status 9 78 Executing Async The CU number is out of effective range Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom delete rcu_path Error message CMDRJE Get Command Status Executing Async Executing Async Error code SSB1 SSB2 Description The value of specified port is invalid Get Command Status Async Failed to establish a path or the deletion operation The following factor can be thought e Input parameter is invalid e Port status or the MP Blade status is in the state of abnormal e Cable is not connected correctly e Portis specified incorrectly Get Command Status Async The operation cannot be done because the microcode is being changed CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async A logical path cannot be deleted because the specified RCU is not registered Get Command Status Async The specified CU number is not defined or an LDEV is not defined under the CU number Get Command Status Async The operation cannot be done because the number of paths becomes less than the least path number CMDRJE Executing The port attribute is n
194. ber of virtual volumes that can be created in Status the system exceeded the maximum number CMDRJE Executing 2E30 6003 The specified pool is the pool for Thin Image or Get Command Async Copy on Write Snapshot Status CMDRJE Executing 2E31 6003 A virtual volume of Dynamic Provisioning that is associated with the specified pool cannot be created with the specified emulation type 9 34 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add Idev Error message Executing Async Executing Error code SSB1 SSB2 Description TSE VOL cannot be created because of the following conditions e The specified pool is other than HDPz pool e The specified emulation type is other than 3390 A Executing TSE VOL cannot be created in combination with the specified pool ID and the CU number of LDEV You must specify the even CU number for the pool of even pool ID and the odd CU number for the pool of odd pool ID Get Command Status Async A TSE VOL cannot be created in the specified pool for Dynamic Tiering CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The specified parameter is invalid Check the Command Control Interface Command Reference ERANGE Result too large
195. bled Paired volume Initial copy is complete Updates are processed synchronously or asynchronously Paired volume Initial copy is complete Updates are processed asynchronously Data replication operations with CCI R W enabled Hitachi Command Control Interface User and Reference Guide R enabled 6 19 TrueCopy Pair Status ShadowImage Pair Status Primary Secondary COPY In paired state but initial copy In paired state but initial copy R W R enabled pairsplit or resync operation is pairsplit or resync operation is enabled not complete Includes not complete Includes COPY PD COPY SP and COPY PD COPY SP and COPY RS status COPY RS status RCPY Not used for TrueCopy In paired state but reverse R enabled R enabled resync operation is not complete Includes COPY RS R status PSUS In paired state but updates to In paired state but updates to R W R W split the S VOL data are suspended the S VOL data are suspended enabled enabled SSUS due to user requested pairsplit due to user requested pairsplit when using split The RAID storage system keeps The RAID storage system keeps write enable track of P VOL and S VOL track of P VOL and S VOL pairsplit updates while the pair is split updates while the pair is split option PSUE In paired state but updates to In paired state but updates to R W R enabled error the S VOL data are suspended _ the S V
196. blem is not being caused by the UNIX PC server hardware or software and try restarting the server Problem Recommended action Deprecated CCI currently uses the ioctlh SCSI_ITOCTL_SEND_COMMAND for SCSI ioctl sending the control command to the command device However in The following RHEL 4 0 using kernel 2 6 9 XX the following message is output to message is syslog file var log messages with every ioctl output to syslog program horcmgr is using a deprecated SCSI ioctl please file var log convert it to SG IO messages with This may originate from the following kernel code in drivers scsi every ioctl scsi_ioctl c as way of warning that ioctl SCSI_IOCTL_ of kernel program horemgr 2 6 9 XX does not properly handle an error of the HBA driver is using a deprecated SCSI ioctl please Check for deprecated ioctls all the ioctls that do convert it to not follow SG_IO the new unique numbering scheme are deprecated switch cmd case SCSI_IOCTL_SEND_COMMAND case SCSI IOCTL TEST UNIT READY case SCSI_IOCTL BENCHMARK COMMAND case SCSI_IOCTL_SYNC case SCSI_IOCTL_START_UNIT case SCSI_IOCTL STOP _UNIT printk KERN WARNING program s is using a deprecated SCSI ioctl please convert it to SG I0 n current gt comm Thus CCI supports a way to change to the ioctl SG_IO automatically if Linux kernel supports the ioctl SG_IO for horcmgr and inqraid command How
197. c Creating a pool or adding a pool volume cannot be done because CLPR is mixed in the specified pool Get Command Status Async The specified LDEV is used as a V VOL Get Command Status Async The specified LDEV is used in another program product CMDRJE Executing An LDEV whose emulation type is not available to be mixed is in the specified LDEVs CMDRJE Executing The emulation type of the specified volume is not OPEN V Get Command Status Async Troubleshooting The operation cannot be done for the following reasons e The pool volumes include external volumes whose cache modes are invalid The pool includes both external volumes whose cache modes are invalid and internal volumes 9 59 Hitachi Command Control Interface User and Reference Guide raidcom add snap_pool Error message CMDRJE Get Command Status Executing Async Executing Async Error code SSB1 SSB2 Description A pool volume cannot be added because the LDEV of the resource group different from the resource group of the pool volume to which the specified pool belongs is specified Get Command Status Async The specified LDEV cannot be operated because it is an external volume mapped for online data migration Get Command Status Async The specified volume cannot be used as a pool volume CMDRJE Executing The threshold value 1 is out of
198. cal volumes e Physical level CCI shows the relationship between PhysicalDrive and LDEV by giving Physical as a KEY WORD for the discovery e LDM volume level CCI shows the relationship between LDM volume and PhysicalDrives and LDEV by given Volume as KEY WORD for the discovery e Drive letter level CCI shows the relationship between Drive letter and LDM volume and PhysicalDrives and LDEV by given LETALL as KEY WORD for the discovery The KEY WORD Physical Volume LETALL can be used with raidscan find inqraid mkconf commands In Windows DOS devices for example C Volume are linked to a Device Object Name Device CCI indicates as the following by abbreviating a long Device Object Name e Device Object Name of the LDM for Windows Device HarddiskVolumexX for Partition VoIX DskY DskY shows that VoIX are configured through HarddiskyY e Device Object Name of the LDM for Windows 2003 2000 Device HarddiskDmVolumes VolumeX for spanned volume DmsX DskYs Examples of using CCI commands 8 3 Hitachi Command Control Interface User and Reference Guide Device HarddiskDmVolumes StripeX for striped volume DmtX DskYs Device HarddiskDmVolumes RaidX for Raid 5 volume DmrX DskYs DskYs shows that DmsxX DmtX Dmr volumes are configured through bundling multiple HarddiskY1 Y2 e Device Object Name of the PhysicalDrive for Windows Device HarddiskX DR HarddiskxX You can dete
199. can be used continuously because you do not need to modify their scripts However if you define HORCM_VCMD you cannot operate the virtual storage machine whose the serial number is not specified by HORC_VCMD If you specify the virtual storage machine to the command options that is s lt seq gt or u lt unit id gt instead of specifying with HORCM_VCMD you can also operate the virtual storage machine of the serial number not specifying to HORCM_VCMD After you change the virtual storage machine configuration with the raidcom add resource command or the raidcom delete resource command restart HORCM CCI functions Hitachi Command Control Interface User and Reference Guide Specifying a virtual storage machine by HORCM_VCMD Configuration definition file settings when specifying a virtual storage machine by HORCM_VCMD This topic shows configuration definition file settings with the global virtualization function when specifying a virtual storage machine by HORCM_VCMD For details on other parameters see Configuration definition file on page 2 12 HORCM_CMD Specify a volume belonging to meta_resource in VSP G1000 as the command device CCI obtains the virtual storage machine information defined in VSP G1000 via the specified command device and configure the virtual storage machine components When you specify a volume in the virtual storage machine as the command device in the system configuration with the global virtualization f
200. cannot be added because the LDEV of the resource group different from the resource group of the pool volume to which the specified pool belongs is specified Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add dp_pool Error code Error message rae di Description sync SSB1 SSB2 Get Command Async 2E30 0074 The specified LDEV cannot be operated because it Status is an external volume mapped for online data migration Get Command Async 2E30 0085 The specified volume cannot be used as a pool Status volume CMDRJE Executing 2E30 6000 The threshold value 1 is out of range Get Command Async 2E30 6004 The specified pool attribute differs from the pool Status attribute of existed pool Get Command Async 2E31 0015 The RAID level of the specified LDEV is different Status with the RAID level of others Get Command Async 2E31 0016 There is a blocked pool volume Status Get Command Async 2E31 0018 External volumes whose cache modes are Status different are included CMDRJE Executing 2E31 6001 The POOL Name is duplicated with another pool Get Command Async 2E31 6004 The pool cannot include volumes in different RAID Status levels because the pool cannot include those volumes Or the pool cannot include the RAID 1 volumes and the volumes of other RAID levels together Get Command Async 2E31 6005 The pool cannot include both internal volumes
201. cation IO path 5 About waiting application IO The HORCM daemon process delivers the timestamps to the defined CT group while freezing IO for each journal Waiting Rate 0 5ms Number of journal Interval ms 100 Note that 0 5 ms depends on the OS platform Therefore it is recommended to limit within four journal per CT group and 8192 LDEVs per CT group In the case of multiple CT groups per HORCM it is recommended to limit within 256 LDEVs per CT group 6 50 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 6 HOST IO on pairsplit RS R horctakeover pairresync swapp s The pairsplit RS R operation cannot be frozen and Split HOST IO from RCU in Link Normal state In other words this option does not support At time Split hence these operations are required to stop HOST IO in order to keep Data Consistency on S VOL This is the same restriction as TC_Sync 7 Suspending deleting status The suspending deleting for committing S VOL Journal data with CTQ Marker is accomplished by the CCI commands Therefore the storage system has nothing to do in that status suspending deleting If a CCI command is aborted for some reason KILL etc or EX_EWSTOT the storage system keeps that status suspending deleting To terminate this status re execute the CCI command then terminate suspending deleting status after JNL Consistency Restore 8 Detecting inconsis
202. cation unnecessary mode and the undefined resource groups CCI checks the access authorities shown in the following table Table 3 2 Relations between resource groups and command devices Commands pairxx raidcom Resources Not Not authenticated AUthenticated Suthenticateg Authenticated r r user eon user a Undefined Permitted Permitted by EX_EPPERM Permitted by the resource the authority of authority of resource ID 0 resource ID 0 Defined EX EGPERM4 Permitted by EX EGPERM 4 Permitted by the resource the authority of 7 authority of the the relevant EX_EPPERM relevant resource ID resource ID Notes 1 Above described commands except for the raidcom command User who uses the mode without the command authentication 2 3 Undefined as the resource group 4 Command execution is rejected by the relevant error Target resources The following objects are arbitrarily defined as the resource groups by each user e LDEV e Physical port e Host group e RAID group e External connection group Commands executed depending on operation authorities The commands and operation authority managed by Storage Navigator and SVP are listed in the following table For information about creating the Storage Navigator user accounts registering user accounts to user groups and user group authorities see the Hitachi Storage Navigator User Guide 3 8 CCI functions Hitachi Command Control In
203. cause the LDEV number of the specified volume does not match the LDEV number of the virtual volume Executing You cannot execute the command because the processing by the other software Device Manager Storage Navigator or SVP and so on is in progress Executing The information of the virtual storage machine is already set in the specified resource Executing The specified virtual LDEV number is already exist in the virtual storage machine to which the specified LDEV belongs Executing You cannot operate the LDEV that has the LU path definition Executing The specified LDEV is already defined Executing The specified volume cannot be set because it is a LUSE volume 9 98 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom map resource Error code Executing Async sspi ssB2 Error message Description Executing The specified LDEV cannot be operated because it has an attribute Executing The specified LDEV cannot be set the information of the virtual volume because it is not virtualized Executing An internal error occurred Call Hitachi Data Systems Support Center Executing The specified operation cannot be performed because it is not supported Table 9 73 SSB codes that are returned by raidcom unmap resource command raidcom unmap resource Executing Error code Async sspi ssB2 Executing The s
204. cc Simplex S Accepted Acceptable 2 to 3 2 to 4 2 COPY Acceptable Accepted 3 PSUS Accepted 1 4 PSUE PDUB Accepted 1 Legend Accepted A command is accepted and executed When the command execution succeeds the status changes to that of the shown number Accepted A command is accepted and executed When the command execution succeeds the status changes to that of the shown number Acceptable No operation is executed though a command is accepted Blank 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 Volume Migration Volume Migration must be used within the following restrictions e ShadowImage HOMRCF The operation for the volume migration must be operated at the SMPL or PAIR or COPY state If not paircreate m cc command is rejected with EX_CMDRIJE or EX_CMDIOE Also ShadowImage cannot be operated to CC_SVOL moving in Volume Migration In copying CC_SVOL the copy operation for the volume migration is stopped if the ShadowImage pairsplit command is executed 1 COPY or PAIR E ee cc SVOL SVOL e TrueCopy HORC The operation for the volume migration must be performed at the SMPL or PSUS state If not paircreate m cc command is reject
205. ce CCI trace 2 38 A directory specified using the environment variable HORCC_LOG The command log file is stored in this directory If no environment variable is specified the directory JHORCM log is used is the instance number While the HORCM is running the log files are stored in the HORCM_LOG directory shown in a When the HORCM starts up the log files created in the operation are stored automatically in 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 files The command trace file is used for maintenance aiming at troubleshooting It is not created normally If a cause of an error cannot be identified using the log file the environment variables or trace control commands with trace control parameters are issued to start tracing and the trace file is created The trace control parameters include trace level file size mode etc More detailed tracing is enabled by increasing the trace level Tracing is made in wraparound within the range of the file size HORCM makes the trace file according to the trace level specified in the HORCM startup shell script set to activate the HORCM control command The trace control command one of the HORCM control commands sets or changes the trace control parameters This command is used
206. ce has not been shown the Device_File then pair operations are rejected except the local option such as in protection mode because of Unknown volume as shown in the following example pairdisplay g oradb fd Group PairVol L R Device File M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L c0t3d0 0 35013 17 P VOL COPY 35013 18 oradb oradev1 R Unknown 0 35013 1 Permitting protected volumes Protection mode needs recognition step to check accessible volumes and the horcm conf at the startup of HORCM on protection mode The protected volumes must be registered to enable the Data Protection Facility at each startup of HORCM so that this registration process is executed automatically by etc horcmgr Data protection operations with CCI 7 11 Hitachi Command Control Interface User and Reference Guide With a HORCMPERNM file 7 12 The 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 HORCMPERNM 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 SHORCMPERM HORCM usr bin raidscan find inst The following are an example to permit the LVM Volume groups For MUH 0 vg00 dev rdsk c0t3d0
207. chk pairevtwait pairsyncwait o raidscan except find verify find inst raidar pairdisplay o Yraidvchkset raidvchkscan except v jnl raidvchkdsp EX ESPERM Permission denied with the SLPR Cause A specified command device does not have a permission to access other SLPR Action Please make the SLPR so that the target port and the command device belongs to the same SLPR SLPR configuration examples 8 18 Single host Figure 8 7 SLPR configuration on a single host on page 8 18 provides an example of when control is denied to the paircreate and raidscan commands in the following cases e The volume described on RMINST1 is different from the SLPR of the command device so the paircreate command cannot control the paired volume e The specified port is different from the SLPR of the command device so the raidscan p CL3 A command cannot scan any ports that are defined as SLPR N Figure 8 7 SLPR configuration on a single host To operate SLPR N assign the command device If RMINST1 has been assigned to a command device for SLPR N the paircreate command is permitted However the raidscan p CL3 A command via RMINSTO is unable to scan a port because the specified port is different than the SLPR of the command device In this case p CL3 A must be operated via RMINST1 as shown in the following example Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide Figure
208. chronous commands is a method of command processing applied to a command that takes much time in processing on the storage system Once this processing method of command is issued an additional command can be executed without having to wait for the command completion that executed just before It is also possible to monitor the completion status by using a status reference command Command Command Respond Refer status Execute Reccsccncsncesccsessenssncesccnsces ry Execute Processing Processing Respond Synchronous command Asynchronous command Complete Respond Command completion check Overview 1 3 Hitachi Command Control Interface User and Reference Guide Command execution modes CCI provides two command execution modes transaction mode that executes by specifying a script file with zt option and line by line mode that executes a command row by row for the configuration setting commands raidcom commands The transaction mode can execute the following checking e Context check This check is executed when a script file is specified by zt option It checks the context of preceding commands and determines whether a subsequent command can be executed Specifying example gt raidcom zt lt script_file gt e Configuration check This check verifies that the actual storage system confirmation is valid implemented for the resources specified in the commands LDEVs ports pools etc Syntax
209. cified parameter is invalid Check the Hitachi Command Control Interface Command Reference Table 9 40 SSB codes returned by raidcom get snapshot raidcom get snapshot Executing Error code Async sspi ssB2 CMDRJE Executing 2EC5 FEEC An internal error occurred Call Hitachi Data Systems Support Center Table 9 41 SSB codes returned by raidcom delete snapshot Error message Description raidcom delete snapshot Executing Error code Error message Async sspi ssB2 Description Executing The value exceeds the range of LDEV number Executing The MU number exceeds the maximum Executing The command ends abnormally because the volume out of the range of LDEV number is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting 9 71 Hitachi Command Control Interface User and Reference Guide raidcom delete snapshot Executing Async Error message Executing Error code SSB1 SSB2 Description The command ends abnormally because the ShadowImage reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration source volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration target volume is specified as the P VOL of a Thi
210. city command e Read protection The RAID storage system protects reading from the target volumes by responding with the Illegal function check condition SenseKey 0x05 SenseCode 0x2200 e Write protection The RAID storage system replies with Write Protect in the mode sense header and protects from writing the target volumes by responding with the Write Protect check condition SenseKey 0x07 SenseCode 0x2700 e SVOL disabling The RAID storage system rejects the command execution of the copy series program product for not to be overwritten the target volume by the copy process of copy series program product TrueCopy Universal Replicator ShadowImage Copy on Write Snapshot and protects the target volume This option can be used with the other Data Retention Utility options in parallel For example if you want to protect from the writing by the both copy series program product and the host accessing set the both write protection option and this option Only the setting of write protection option cannot protect the target volume from the writing executed by the copy processing of the copy series program product Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide Restrictions on Data Retention Utility volumes File systems using Data Retention Utility o When setting DRU to the UNIX file system volumes the volumes must be mounted with the Read Only option after the volumes are
211. command e S VO OL side must close the logical drive corresponding to a g name before issuing the raidscan find sync command Special facilities for Windows systems CCI provides the following special facilities for Windows systems e Signature changing facility for Windows systems on page 8 9 e GPT disk for Windows on page 8 11 Signature changing facility for Windows systems Consider the following Microsoft Cluster Server MSCS configuration in which a MSCS P VOL is shared from MSCS Nodei and Node2 and the copied volume of S VOL is used for backup on Node2 If the Node2 has reboot on standby state then MSCS of Node2 has a problem to assign drive letter of S VOL with previous P VOL drive letter This problem will happen on Node2 on MSCS environment as shown in the following figure The conditions are e Nodei is active e Node2 is standby state where P VOL on Node2 is hidden by MSCS and reboots the Node2 Node 2 MSCS Backu Shadowlmage HOMRCF P VOL S VOL Figure 8 4 Configurations with MSCS and ShadowImage HOMRCF Examples of using CCI commands 8 9 Hitachi Command Control Interface User and Reference Guide 8 10 MSCS on Node2 will misunderstand the S VOL as MSCS cluster resource because the signature of S VOL and P VOL is the same due to copied The reason is that MSCS cluster resources are managed with the signature only Therefore S VOL of Node2 will unable to backup so that MSCS of Node2 ca
212. 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 conf Edit 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 horcmO xxxxx udp xxxxx port number horcmi yyyyy udp yyyyy port number Each 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 Starting up CCI 4 5 Hitachi Command Control Interface User and Reference Guide spawn nowait process horcm0O horcmstart O spawn nowait process horcm1 horcmstart 1 Note The subprocess HORCM created by SPAWN is terminated AN when the terminal is LOGOFF or the session is terminated If you want an independent process to the terminal LOGOFF use RUN DETACHED command 3 Set the HORCM instance numbers in the environment in which the command is to be executed HORCMINST X X instance number 0 or 1 4 Confirm the configuration using a CCI command Set the log directory HORCC_LOG in the command execution environment as required Note Ifthe log directory under SYS POSIX_ROOT is shared with AN other n
213. copy_erp for I Sei in 10 1 19 do raidcom add lun port CL1 A HP UX P Idev_id Shi for I i in 20 129 do raidcom add lun port CL2 A HP UX S Idev_id thi raidcom get lun port CL1 A HP UX P raidcom get lun port CL2 A HP UxX S raidcom unlock resource resource_grp_name meta_resource raidcom get resource raidcom logout Display the copy group information Define a path of VVOL A host group HP UX P Define a path of YVOL 20 to 29 to Port CL2 JA host group HP UX S Given an LU number automatically 10 to 19 to Port CL1 Display the path information that is set to PortCLI A host group HP UX P and the path information that is set to PortCL2 A host group HP UX S Unlock the resource group meta_resource Display the resource group information Log out Figure 5 7 Script examples of virtual volume operation Dynamic Provisioning 3 3 Virtual volume Dynamic Provisioning for Mainframe operations Creating virtual volumes Dynamic Provisioning for Mainframe To create LDEVs of virtual volumes Dynamic Provisioning for Mainframe and make the LDEVs available to the host perform the following Provisioning operations Operation overview SSID settings arbitrarily Description Configures the SSID unless it is configured Set register the SSID by specifying undefined LDEV numbers in the area in which SSIDs are not defined Executed command raidcom modify ldev lde
214. create an LDEV V VOL Executed command raidcom add ldev pool lt pool ID gt lt pool naming gt snap ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Creating LDEV V VOL nickname arbitrary Create nickname for the created LDEV This operation is arbitrary raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Setting MP blade of LDEV V VOL Set MP blade of created LDEV V VOL raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Displaying LDEV information V VOL Display information of created LDEV V VOL and confirm the result of executing the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt Creating LU path Specify port map LDEV to LUN and create an LU path raidcom add lun port lt port gt host group name ldev_id lt ldev gt lun_id lt lun gt Displaying LU path information Display LU path information and confirm the result of executing the command raidcom get lun port lt port gt lt host group name gt Script examples The following shows script examples of virtual volume Dynamic Provisioning operation 5 26 Provisioning operations with CCI Hitachi Command Control Interface User an
215. cription Command 1 Confirming the CLPR Check the status of raidcom get clpr configuration the CLPRs 5 44 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation none ate Description Command Migrating one of the Specify the LDEV raidcom modify clpr clpr following to other number parity lt clpr gt ldev_id lt ldev gt CLPRs group number or parity_grp_id lt gno sgno gt LDEV external volume external_grp_id lt gnosgno gt group number parity group external volume group Verifying the CLPR For parity group raidcom get parity_grp migration migration check the status of the parity group Displaying CLPR information The raidcom get clpr command lists and displays the status of the CLPRs in the storage system If no CLPRs have been created CLPRO is displayed as entire cache Display example raidcom get clpr CLPR CLPR_NAME TC_CAP MB TU _ CAP MB WP_CAP MB SF_CAP MB U W S 000 Oracle DB 40000 20000 4000 0 50 30 0 001 Oracle DB PROD 20000 10000 2000 0 50 10 0 003 Oracle DB BACK 10000 5000 500 0 50 5 0 Migrating parity groups in a CLPR This section explains operations from checking the parity group information to moving the parity group Displaying parity group information The raidcom check the status display the information about the parity group The following shows the display example of parity group
216. cted to two or more storage systems the unit ID is expressed by port extension Each group name is a unique name discriminated by a server that uses the volumes the attributes of the volumes such as database data redo log file UNIX file recovery level etc The group and paired logical volume names described in this item must reside in the remote server The hardware SCSI fibre port target ID and LUN as hardware components need not be the same The following values are defined in the HORCM_DEV parameter e dev_group Names a group of paired logical volumes A command is executed for all corresponding volumes according to this group name e dev_name Names the paired logical volume within a group that is name of the special file or unique logical volume The name of paired logical volume must be different to the dev name in another group e Port Defines the RAID storage system port number of the volume that connects to the dev_name volume The following n shows unit ID when the server is connected to two or more storage systems for example CL1 A1 CL1 A in unit ID 1 If the n option is omitted the unit ID is 0 The port is not case sensitive for example CL1 A cll a CL1 a cl1 A CLi An Bn Cn Dn En Fn Gn Hn Kn Ln Pn Qn CL2 An Bn Cn Dn En Fn Gn Hn Jn Kn Ln Mn Nn Pn Qn The following ports can be specified only for the 9900V cCL3 jan bn cn en fn gn hn pn qn CL4 an bn cn
217. ction fails If this check proves that data is consistent then this function will try to switch the S VOL to a primary volume using a Resync for Swapping and if it succeeds then this function will return Swap takeover else this function will return SVOL SSUS takeover as the return value of horctakeover command In case of a Host failure this function will be returned as Swap takeover In case of a FICON or P VOL site failure this function will be returned as SVOL SSUS takeover A SVOL takeover can be specified by the granularity of a paired logical volume CT group or volume group If a SVOL takeover is specified for a volume group a data consistency check is executed for all volumes in the group Inconsistent volumes are picked out and displayed in the execution log file as shown below Example Group Pair vol Port targ lun LDEV Volstat Status Fence To be oradb1 ora001 CL1 A 1 5 145 S VOL PAIR NEVER Analyzed oradb1l ora002 CL1 A 1 6 146 S VOL PSUS STATUS Suspected Even so the SVOL takeover function enables the secondary volume to be used i e reading and writing are enabled since it assumes that the remote node possessing the primary volume cannot be used TrueCopy Async Universal Replicator specific behavior for svol takeover The S VOL side CCI will issue a Suspend for Swapping to the S VOL side storage system Non transmitted P VOL data will be copied to the S VOL and a Resync for Swapping operation will be performe
218. cuting 2E11 9400 The command cannot be accepted After a while execute the same command Get Command Async 2E20 3000 The serial number the product ID or the SSID of Status the target storage system is incorrect Get Command Async 2E21 7101 The specified CU number is not defined or an Status LDEV is not defined under the CU number Get Command Async 2E22 3001 The specified RCU is already registered to another Status product ID 9 82 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add rcu Error message Get Command Status Executing Async Error code SSB1 SSB2 Description The operation cannot be performed due to one of the following reasons e The number of RCUs registered in MCU or RCU is more than four The number of RCUs registered in the system is more than 64 in the case of specifying the cu free Get Command Status Async The specified SSID is already registered to another RCU Get Command Status Async The specified RCU is cannot be registered because there is no free RCU Get Command Status Async The operation cannot be done because the number of paths becomes less than the least path number CMDRJE Executing The port attribute is not Initiator MCU Get Command Status Async Command cannot be executed because the RCU identification code of a path is invalid Get Command Status Async The operation ca
219. d after the copy process In case of a Host failure this data synchronize operation will be accomplished and the SVOL takeover function will return as Swaptakeover after attempting a Resync for Swapping In case of a FICON or P VOL site failure this data synchronization operation may fail Even so the SVOL takeover function will do Suspend for Swapping and enable the secondary volume to be used 6 14 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide As a result this function will return as SVOL SSUS takeover Through this behavior you will be able to judge that non transmitted data of the primary volume was not transmitted completely when a SVOL takeover returns SVOL SSUS takeover Caution The SVOL takeover operation is required to copy Nontransmitted AN P VOL data within a given timeout value specified by the t lt timeout gt option If the timeout occurs before the SVOL takeover operation has completed all S VOL changes to a SSWS state the horctakeover command will fail with EX_EWSTOT If the horctakeover has failed due to a timeout then you need to try for a recovery as shown below e Wait until the S VOL state becomes SSWS via pairdisplay g lt group gt fc command and try to the start up again for the HA Control Script e Make an attempt to re synchronize the original P VOL based on the S VOL using pairresync g lt group gt swaps c lt size gt for a Fast
220. d LDEV is used as a pool volume Get Command Status Async The specified LDEV is used as a journal volume Get Command Status Async Volume Security is set to the specified LDEV Get Command Status Async Quick format cannot be done because the target LDEV is not an internal volume Get Command Status Async The specified LDEV is a Data Retention Utility Volume Retention Manager attribute device Get Command Status Async The specified LDEV is a pool volume and the pool volume include the Dynamic Provisioning volume that is not in the blocked status Get Command Status Async The specified LDEV cannot be operated because it is an external volume mapped for online data migration Get Command Status Async Maintenance work cannot be performed because the target LDEV is a quorum disk Get Command Status Async LDEV cannot be formatted because there is no normal external path CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async An internal error occurred CMDRJE Get Command Status Executing Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The specified parameter is incorrect Check the Command Control Interface Command Reference Table 9 25 SSB codes that are returned by raidcom modify Idev comman
221. d Reference Guide raidcom login USEROT PASSO1 raidcom lock resource resource_grp_name meta_resource raidcom modify port port CLI A secur ity switch y raidcom modify port port CL2 A secur ity _switch y raidcom add host_erp port CL1 A D host_grp_name HP UX P raidcom add host_grp port CL2 A 0 host_grp_name HP UX S raidcom modify host_erp port CLI A D host_mode HP UX raidcom modify host_grp port CL2 A 0 host_mode HP UX raidcom get host_erp port CLI A raidcom get host_grp port CL2 A raidcom add hba_wan port CLI A HP UX P hba_wan 210000e0 8bO256f8 raidcom add hba_wan port CL2 A HP UX S hba_wan 210000e0 8bO256f9 raidcom get hba_wan port CLI A HP UX P raidcom get hba_wan port CL2 A HP UX S for I S i in 0 1 9 do raidcom add Idev Idev_id bi capacity 10g parity_grp_id 1 1 raidcom get command_status raidcom reset command_status for I i in 0 1 9 do afmt 5 raidcom get command_status raidcom reset command_status for 1 i in 0 1 9 do raidcom modify Idev Idev_id hi device_name my volume i zLog in with the user ID USERO and the gt password PASSO1 Lock the resource group meta_resource Turn ON the security switch of PortCLI A and Por tCL2 A Set the host group 0 to PortCLI A host gt group name HP UX P and the host group 0 to PortCL2 A host group name HP UX S Set the host mode HP UX to the host group 0 cof PortCLi A a
222. d Storage Navigator CCI supports specifying a host group and LUN on the host view Specifying a host group 1 Defining the formats 8 14 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide The addition of arguments for the host group to the raidscan command and the configuration file means that it is not compatible with conventional CLI Therefore CCI provides a way to support CLI by specifying a host group in the port strings as follows e CL1 A GRP GRP can be up to 127 Specifying the host group for the raidscan command raidscan p CL1 A 5 Specifying the host group for the configuration file dev_group dev_name port TargetID LU MU ORA ORA 000 CL2 D 1 4 1 0 ORA ORA 001 CL2 D 1 4 2 0 If the port including a host group is specified to the port name then a maximum of 255 LUNs can be specified 2 Specifiable port strings As a result CCI supports four kinds of forms for the port name e Specifying the port name without a host group CL1 A CL1 An where n unit ID for multiple RAID e Specifying the port name with a host group CL1 A g where g host group CL1 An g where n g host group g on CL1 A in unit ID n Commands and options including a host group 1 Specifiable command for host group The following commands can specify a host group with the port strings e raidscan p lt port gt raidar p lt port gt raidvchkscan p lt port gt raidscan p CL2 D 1 PORT
223. d command log files using the HORCM_LOG and HORCC_LOG environment variables as shown in Table 2 5 Environment variables for lo 2 36 CCI software environment Hitachi Command Control Interface User and Reference Guide directories on page 2 38 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 log file If the HORCM activation fails the system administrator should check the system log file and activation log identify the error cause and take the proper action The system log file for UNIX based systems is the syslog file The system log file for Windows based systems is the event log file Table 2 4 Log file names and locations UNIX based systems HORCM startup log HORCM_LOG horcm_HOST log Command log HORCC_LOG horcc_HOST log HORCC_LOG horcc_HOST oldlog Windows based systems HORCM startup log HORCM_LOG horcm_HOST_log txt Command log HORCC_LOG horcc_HOST_log txt HORCC_LOG horcc_HOST_oldlog txt HORCM error log HORCM_LOG horcmlog_HOST horcm log HORCM error log HORCM_LOG horcmlog_HOST horcm_log txt HORCM trace HORCM_LOG horcmlog_HOST horcm_PID trc Command trace HORCM_LOG horcmlog_HOST horcc_PID trc HORCM trace HORCM_LOG horcmlog_HOST horcm_PID_trc txt Command trace HORCM_LOG horcmlog_HOST horcc_PID_trce txt HORCM core HORCM_LOG core_HOST_PID core Command core H
224. d eo 2 44 User environment variable 0 0 0 ce ees 2 44 CU Ons 4 bee ee Oe ee Hae Oe oe bs ee he 3 1 Command execution using in band and out of band methods 3 2 Connecting to CCI server already connected by In Band method using Out of Band method 2 24 00 s65 205 eee eee debe eee ete eee eee sete n es 3 3 User authentication 2 ees 3 6 Command operation authority and user authentication 05 3 6 Controlling User Roles 524s ed s 44 beeeenwid edd bere euw led 3 6 Controlling user resources 1 1 es 3 7 Hitachi Command Control Interface User and Reference Guide Commands executed depending on operation authorities 3 8 Relation between resource groups and command operations 3 11 Resource lock TUNCUION amp 5 0 an 64 sess ee ee sole aeb es see se ae eed 3 14 Command execution modes 0 0 0 es 3 15 Overview ex cere tied etn Be Be aioe ee a oy Get ate eet a aa 3 15 Context CHEEK 324 2 o oh a ears Kee ae ee Ba eee ee 3 16 HOWTO ChECK ona Peat see wea e heat ede Sh ae ade oe 3 17 Details of check contents soe wediaw acta ewe ee en ees ee ee 3 17 Configuration check s23 24 e655 e2 8 lees e i Serer ieee 3 24 Resource location and parameter 0 c ee es 3 24 MP blade location and parameter 0 000 cee ee ees 3 24 EDEV Grouping TINCHORi asc eet tt ete Gee eee Saree eS eee 3 25 OVEIVIOW de fea te A er eee Eee a eee et tere ee 3 26 Device group definition methods
225. d with the SLPR Command I O to RAID Recoverable EX_CMDRJE An order to the control command was rejected EX_CMDIOE Control command I O error or rejected EX_OPTINV A specified option is invalid EX_INVMOD Invalid RAID command mode EX_INVCMD Invalid RAID command Communication for HORCM Recoverable EX_ATTHOR Cannot be attached to HORC manager EX_ATTDBG Cannot be attached to a Debug layer EX_COMERR Cannot be communicate with HORC manager Recoverable EX_ENORMT No remote host alive for remote commands or Remote CCI might be blocked sleeping on an existing I O Resource Unrecoverable EX_ENOMEM Not enough core Generic error codes raidscan raidqry raidar horcctl The following table lists the generic error codes returned by these commands Troubleshooting 9 17 Hitachi Command Control Interface User and Reference Guide e raidscan e raidqry e raidar e horcctl In this table Unrecoverable indicates errors that cannot be recovered by reexecuting the command and Recoverable indicates errors that can be recoverable by reexecuting the command Table 9 4 Generic error codes raidscan raidqry raidar horcctl Error code Category Error message Syntax for Argument EX_REQARG EX_INVARG EX_INVNAM EX_UNWOPT Required Arg list Unrecoverable Invalid argument Invalid name of option Unknown option
226. d_device raidcom modify Idev command_device Error message Executing Async Error code SSB1 SSB2 Description CMDRJE 9 44 Executing 2E10 0000 The command device cannot be set to the specified LDEV because of the following causes e The LDEV is used as a ShadowImage pair e The reserve attribute of a ShadowImage is configured Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify Idev command_device Error code Error message rae di Description sync SSB1 SSB2 CMDRJE Executing 2E10 0001 The specified LDEV is used as a TrueCopy pair CMDRJE Executing 2E10 0002 The specified LDEV is used as a Universal Replicator pair or a journal CMDRJE Executing 2E10 0004 The specified volume cannot be set because it is used by the Thin Image or Copy on Write Snapshot pair CMDRJE Executing 2E10 0062 The specified LDEV is used as the primary volume of a GAD pair CMDRJE Executing 2E10 0063 The specified LDEV is used as the secondary volume of a GAD CMDRJE Executing 2E20 0000 The specified LDEV is not defined CMDRJE Executing 2E21 9000 The following settings cannot be performed because the program product of LUN Manager is not installed e Command device settings e Command security settings CMDRJE Executing 2E30 0004 The emulation type of the specified volume is not OPEN volume CMDRJE Executing 2E30 0008 T
227. dcom add ldev create LDEV parity_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt 8 Formatting Format created LDEV raidcom initialize ldev LDEV ldev_id lt ldev gt operation lt type gt 9 Creating LDEV Create nickname for LDEV raidcom modify ldev nickname This operation is arbitrary Oe vag arbitrary lt ldev gt ldev_name lt ldev naming gt 10 Setting MP Set MP blade of created LDEV raidcom modify ldev blade of LDEV ldev_id lt ldev gt mp_blade_id lt mp gt 11 Displaying Display information of created raidcom get ldev ldev_id LDEV LDEV and confirm the result of lt ldev gt cnt lt count gt information executing the command key lt keyword gt 12 Creating pool Create pool for Dynamic raidcom add dp pool for Dynamic Provisioning Provisioning Provisioning operations with CCI pool_id lt pool ID gt pool_name lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool name lt pool naming gt ldev_id lt ldev gt cnt lt count gt user_ threshold lt threshold_1 gt lt threshold_ 2 gt 5 25 Hitachi Command Control Interface User and Reference Guide Operation overview Creating LDEV V VOL Description Specify pool and
228. dcom get ldev ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_grp name lt device group name gt lt device name gt key lt keyword gt Display parity group information raidcom get parity _grp parity_grp_id lt gno sgno gt Define SSID Provisioning operations with CCI raidcom add ssid rcu lt serial gt lt mcu gt lt rcu gt lt id gt ssid lt ssid gt raidcom delete ssid rcu lt serial gt lt mcu gt lt rcu gt ssid lt ssid gt Hitachi Command Control Interface User and Reference Guide Operation type Description Corresponding command Virtual volume Create pool for Dynamic raidcom add dp pool pool_id lt pool ID gt Dynamic Provisioning or Dynamic pool_name lt pool naming gt pool_name Provisioning Provisioning for lt pool naming Roe Lae lt pool ID gt Dynamic Provisioning Mainframe pool_id lt pool ID gt pool_name lt pool y naming gt ldev_id lt ldev gt cnt lt count gt for Mainframe grp_opt lt group option gt Dynamic Tiering device_grp_name lt device group name gt Copy on Write lt device name gt user_threshold Snapshot lt threshold_1 gt lt threshold_2 gt see the Provisioning Guide for the storage Create pool for Copy on raidcom add snap_pool pool_id lt pool ID gt Write Snapshot pool_ name lt pool naming gt pool_name system lt pool naming gt pool
229. device For this reason CCI server which connected to a storage system in In Band method can be connected in Out of Band method If a CCI server is specified as a virtual command device it provides a better performance than Out of Band method specified SVP as a virtual command device CCI functions 3 3 Hitachi Command Control Interface User and Reference Guide 3 4 Hardware requirements CCI uses SCSI path through driver to issue I O for command device To use CCI server port as virtual command device the virtual command device interface needs to be converted to the actual SCSI path through interface Following is the environment for using CCI server port as a virtual command device e CCI server which can set virtual command devices CCI support platform except Tru64UNIX and the environment can be used SCSI path through driver e Client PC which can issue commands to virtual command devices It must be CCI support platform Windows client such a Windows XP can be used as well e Initiator port Initiator port is required Following is the default port number If not specified the instance number 34000 If specified instance number X 34000 X 1 If you change the default port number use following environment variables HORCM_IPSCPORT lt services gt lt services gt port number or service name For details about supported platforms see the Command Control Interface Installation and Configuration Guide I O Traf
230. device group forming a copy group add o Adding an LDEV with a different device name paired volume to a device group forming a copy group add LDEV deletion from copy group Deleting an LDEV from a device group forming a copy group It can be deleted both the simplex volume or paired volume LDEVs It is not possible to delete LDEVs directly from the copy group e Use cases The following shows use cases that can be deleted LDEVs from the device group forming a copy group o Deleting an LDEV simplex volume from a device group forming a copy group CCI functions 3 37 Hitachi Command Control Interface User and Reference Guide o Deleting an LDEV paired volume from a device group forming a copy group Copy group deletion Deleting a copy group by specifying a defined copy group e Use cases A copy group can be deleted even if it is configured of simplex volumes or paired volumes The following shows use cases that can be deleted a copy group o Deleting a copy group configured of simplex volumes delete o Deleting a copy group configured of paired volumes 3 38 CCI functions Hitachi Command Control Interface User and Reference Guide delete Pair operation by specifying a copy group Specifying a copy group and creating a pair Pairs are created for which the same device names of LDEV defined in respective device groups of the LDEVs Therefore it is required to give a same device name for t
231. dition authority raidcom add hba_wwn Storage Administrator Provisioning WWN deletion authority raidcom delete hba_wwn Storage Administrator Provisioning LDEV group Device group and Copy group creation authority raidcom add device_grp raidcom add copy_grp Storage Administrator Provisioning Device group and Copy group deletion authority raidcom delete device_grp raidcom delete copy_grp Storage Administrator Provisioning Local copy Pair creation authority paircreate Storage Administrator Local Copy Pair deletion authority pairsplit S Storage Administrator Local Copy Volume Migration pair creation authority paircreate Storage Administrator Provisioning Volume Migration pair deletion authority pairsplit S Storage Administrator Provisioning Remote copy Pair creation authority paircreate Storage Administrator Remote Copy Pair deletion authority pairsplit S CCI functions Hitachi Command Control Interface User and Reference Guide Storage Administrator Remote Copy Operation Attribute change Operation target External volume Authority External path setting authority Executable command raidcom add path Operation authority Role Storage Administrator Provisioning Pool Pool setting authority raidcom modify pool Storage Administrator Provision
232. document uses Meaning Choice between two or more options or arguments the following icons to draw attention to information Description Tip Provides helpful information guidelines or suggestions for performing tasks more effectively Note Provides information that is essential to the completion of a task Caution Warns that failure to take or avoid a specified action can result in adverse conditions or consequences for example loss of access to data WARNING PRR Hitachi Command Warns that failure to take or avoid a specified action can result in severe conditions or consequences for example loss of data Preface Control Interface User and Reference Guide Convention for storage capacity values Physical storage capacity values for example disk drive capacity are calculated based on the following values 1 KB 1 000 bytes 1 MB 1 000 KB or 1 0002 bytes 1 GB 1 000 MB or 1 000 bytes 1 TB 1 000 GB or 1 0004 bytes 1 PB 1 000 TB or 1 000 bytes 1 EB 1 000 PB or 1 000 bytes Logical storage capacity values for example logical device capacity are calculated based on the following values Logical capacity unit Value 1 KB 1 024 bytes 1 MB 1 024 KB or 1 024 bytes 1 GB 1 024 MB or 1 024 bytes 1 TB 1 024 GB or 1 024 bytes 1 PB 1 024 TB or 1 024 bytes 1 EB 1 024 PB or 1 024 bytes 1 block 512 bytes 1 cylinder cyl Open systems
233. e Oracle redo log files including archive logs must be on separate volumes with respect to the data files including control files In other words Oracle redo log files and the data files must not be mixed on the same LU e Restoring Oracle files o Before restoring Oracle data files from a backup data validation may need to be temporarily turned off for those data files that were backed up prior to the Oracle checksum being enabled Old blocks may exist on disk without checksum information in them if the database was running without checksum enabled in the past e Oracle on LVM VxVM o LVM block size must be a multiple of the Oracle block size The Oracle block size must be less than or equal to the minimum of the LYM stripe size and the largest block size at which LVM will not fracture known as Logical Track Group in LVM which is 256 KB in LVM When adding new physical volumes PVs to a logical volume LV to be used as an Oracle data file control file or online log the data validation should be re enabled in order to have HARD checking take effect on those new PVs Similarly in order to have HARD checking no longer performed on PVs that have been removed from an LV that had previously been used by Oracle HARD checking should be explicitly disabled on the device corresponding to the PV If host based mirroring is used such as LVM mirroring all component PV mirrors must be HARD enabled otherwise the enti
234. e To operate SLPR N share the command device If HostB has a shared command device for SLPR N the paircreate command is permitted Also the raidscan p CL3 A command via HostA is allowed to scan a port because the shared command device has the Bitmap settings SLPR M and SLPR N Figure 8 12 Operating SLPR N by sharing the command device TrueCopy using dual hosts In the following example the pair operation command except the I option determines whether the operation for paired volumes should be permitted at a remote site The result is that the paircreate command is not allowed to operate the paired volume because the volume described on HostB differs from the SLPR of the command device Also the raidscan p CL3 A command on HostB is not allowed to scan a port Figure 8 13 TrueCopy operation using SLPR Examples of using CCI commands 8 21 Hitachi Command Control Interface User and Reference Guide 8 22 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide Troubleshooting This chapter provides troubleshooting information for CCI O General troubleshooting O Operational notes and restrictions for CCI operations O Error messages and error codes O Calling the HDS Support Center Troubleshooting 9 1 Hitachi Command Control Interface User and Reference Guide General troubleshooting If you have a problem with the CCI software first make sure that the pro
235. e group name gt ldev_id lt ldev gt port lt port gt port lt port gt lt host group name gt parity_grp id lt gno sgno gt external grp_id lt gno sgno gt Confirming resource deletions Confirms that resources are not allocated to resource groups that you want to delete At that time allocation of resources to the resource group meta_resource must be finished raidcom get resource Deleting resource groups Deletes resource groups raidcom delete resource resource name lt resource group name gt Displaying resource group information Displays resource group information and confirms results of command executions Provisioning operations with CCI raidcom get resource 5 17 Hitachi Command Control Interface User and Reference Guide Allocating resources that are allocated to resource groups to other resource groups When you want to allocate resources that are already allocated to resource groups to other resource groups resources must be once allocated to resource group meta_resource After that allocate resources to the resource groups that you want to allocate LDEVs that configure journals pools LUSEs or device groups must be allocated to resource groups particularly The following shows the necessary provisioning operations Operation Description Command Deleting Deletes resources that are raidcom delete resource resources that allocated to res
236. e issuing commands in the configuration in cooperation with VMware Site Recovery Manager SRM or from pre existing scripts the command response may slow In this case issuing commands using the In Band method is recommended Out of band operations are supported on the Virtual Storage Platform and later storage systems When executing a command using the in band and out of band methods a command device or a virtual command device is set in a configuration definition file as shown in the following figure For the out of band method the IP address of the SVP is specified in the configuration definition file The following figure shows a system configuration example and a setting example of a command device and a virtual command device using the in band and out of band methods CCI functions Hitachi Command Control Interface User and Reference Guide IP address of the SVP is specified in the configuratio n definition file and Out of Band pr communicati ons IP address of the SVP Figure 3 1 System configuration example and setting example of command device and virtual command device by in band and out of band methods To set these two methods a command device or a virtual command device must be set to HORCM_CMD of a configuration definition file Connecting to CCI server already connected by In Band method using Out of Band method In Out of Band method CCI server port can also be specified as a virtual command
237. e since ShadowImage copies are asynchronous If pair splitting of the SVOL oradb1 is attempted while the S PVOL oradb is in a COPY or PAIR state the pairsplit command is rejected with EX_CMDRJE or EX_CMDIOE Pair restore Pair restore resync from SVOL oradb1 to S PVOL can only be performed when the SVOL oradb and the PVOL oradb2 on the S PVOL are in the SMPL and PSUS states If the pair restore of SVOL oradb1 is performed while either the SVOL oradb or PVOL oradb2 on the S PVOL are in a COPY PAIR or PSUS state the pairresync restore command is rejected with EX_CMDRJE or EX_CMDIOE Restriction for TrueCopy ShadowImage cascading volumes Pair restore resynchronization from SVOL oradb1 to S PVOL can only be performed when the TrueCopy SVOL oradb and the PVOL oradb2 on the S PVOL are in the SMPL or PSUS SSUS state If pairresync of S VOL oradb1 is performed when the S PVOL oradb or oradb2 is in any other state the pairresyne restore option command is rejected with EX_CMDRJE or EX_CMDIOE TrueCopy operations CCI TrueCopy commands operate in conjunction with the software on the UNIX PC servers and the TrueCopy functions of the RAID storage systems The CCI software provides failover and other functions such as backup Data replication operations with CCI 6 9 Hitachi Command Control Interface User and Reference Guide commands to allow mutual hot standby in cooperation with the failover product on th
238. e SPM name ORA_NODEO_CTL_0O from the SPM targets raidcom delete spm_wwn port CL4 E spm_ name ORA NODEO CTL_0 Caution about exclusive access control with Storage Navigator Server Priority Manager settings are exclusive for CCI operations and Storage Navigator operations e If you set Server Priority Manager using CCI you cannot set Server Priority Manager from Storage Navigator You need to delete all Server Priority Manager settings made using CCI and then use Server Priority Manager on Storage Navigator to make the Server Priority Manager settings e If you set Server Priority Manager using Storage Navigator you cannot set Server Priority Manager using CCI You need to delete all Server Priority Manager settings made using Storage Navigator and then use Server Priority Manager from CCI to make the Server Priority Manager settings Deleting WWN from the SPM targets with SPM name or SPM group name If you delete WWN from the SPM targets by using the SPM name the SPM setting and SPM name under the specified port are deleted If the same SPM name is set to another port only the SPM setting of the specified port is deleted Provisioning operations with CCI 5 51 Hitachi Command Control Interface User and Reference Guide If you delete WWN from the SPM targets by using the SPM group name the SPM setting and the group under the specified port are deleted If the same SPM group name is set to another port only the SPM settin
239. e UNIX PC server for example MC ServiceGuard FirstWatch HACMP determine if there are any faults in paired volumes recover the volumes from the failures as soon as possible and continue operation in the original system i Note For proper maintenance of TrueCopy operations it is important to specifications for TrueCopy please see the Hitachi TrueCopy User Guide Note For information about the operational requirements and A for your storage system TrueCopy takeover commands Figure 6 5 Server failover system configuration on page 6 10 illustrates a high availability HA environment When a server software error or a node error is detected the HA failover software causes the cluster manager CM to monitor server programs and causes the CM of the standby node to automatically activate the HA control script of the corresponding server program The HA control script usually contains database recovery procedures server program activation procedures and other related recovery procedures The TrueCopy CCI takeover commands are also activated by the HA control script Host A T Ea Server B yaeta Splitting paired Command device primary volume Figure 6 5 Server failover system configuration Legend e CM Cluster Manager Demon process that keeps the consistency of the cluster by monitoring the node and server program in the cluster 6 10 Data replication operations with CCI Hitachi C
240. e command initiators should not issue two or more write commands to a single LDEV unless the storage system can receive commands with independent initiator number LDEV number simultaneously Command process RD WR command Storage Command device Command process Figure 2 5 HORCM and command issue process CCI software environment 2 7 Hitachi Command Control Interface User and Reference Guide Command flow This figure shows the flow of read write command control for a specified LBA LDEV Target LUN Host side Storage side Write Write read processing code Read e Edited data Scanning edit data by reading Figure 2 6 Command flow Issuing commands for LDEVs within a LUSE device A LUSE device is a group of LDEVs regarded as a single logical unit Because it is necessary to know the configuration of the LDEVs when issuing a command a new command is used to specify a target LU and acquire LDEV configuration data as shown in the following figure Target LU Port SCSI ID LU Special LDEV LDEV n Initial LBA of command Special LDEV space LDEV n 2 Figure 2 7 LUSE Device and Command Issue 2 8 CCI software environment Hitachi Command Control Interface User and Reference Guide CCI instance components on the host server HORCM operational environment The HORCM operates as a daemon process on the host server and is activated either automatically when the se
241. e group name gt lt device name gt user_threshold lt gt Deleting or shrinking a pool raidcom delete pool pool lt pool ID gt lt pool naming gt ldev lt Idev gt Releasing a blocked pool raidcom modify pool pool lt pool ID gt lt pool naming gt status nml RCU registration raidcom add rcu cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt rcu_port lt port gt RCU logical path addition raidcom add rcu_path cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt rcu_port lt port gt RCU deletion raidcom delete rcu cu_free lt serial gt lt id gt lt pid gt 5 4 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Function Command syntax RCU logical path deletion raidcom delete rcu_path cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt rcu_port lt port gt Creating journal Registering journal volume the journal raidcom add journal journal_id lt journal ID gt ldev_id lt Idev gt cnt lt count gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt Deleting journal Deleting journal volume from the journal raidcom delete journal journal_id lt journal ID gt Idev_id lt Idev gt grp_opt lt group option gt device_grp_name lt device group name gt lt device name gt Restoration of
242. e operation of Thin Image due to one of the following reasons e The LDEV number specified for the P VOL or the S VOL is incorrect 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 to 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 e The license capacity has exceeded the maximum e The control table for Thin Image is depleted Executing The operation cannot be performed because power off is in progress Executing The specified LDEV is not defined Executing The command ends abnormally because an unmounted volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the blocked volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume in formatting operation is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the shared memory FC TPF or Extension3 is not expanded for necessary capacity Executing The command ends abnormally because the shared memory SS3 or more is not expanded for necessary capacity 9 70 Executing The program product is
243. e representative to switch the command device OFF ON to clear up the instance table Verifying the CCI instance number CCI provides a way to verify the number of temporary allocations 1 0 and actual allocations 1 1 on the instance table so that you can confirm validity of the CCI instance number in use The horectl DI command shows the number of CCI instances since HORCM was started as follows Example without command device security CCI software environment Hitachi Command Control Interface User and Reference Guide horectl DI Current control device dev rdsk cOt0d0 AI 14 TI 0 cCI 1 Example with command device security horectl DI Current control device dev rdsk cOt0d0 AI 14 TI 0 CI 1 AI NUM of actual instances in use TI NUM of temporary instances in RAID CI NUM of instances using current own instance Alternate command device function The CCI software issues commands to the command device via the UNIX PC raw I O interface If the command device fails in any way all CCI commands are terminated abnormally and you cannot use any commands Because the use of alternate I O path is platform dependent restrictions are placed upon it For example on HP UX systems only devices subject to the LVM can use the alternate path PV LINK To avoid command device failure CCI supports an alternate command device function e Definition of alternate command devices To use an alternate command device yo
244. e system buffer associated with all groups for the local instance raidscan pi Volume find sync SYNC ORA ORA 000 gt Vol44 Dsk0 4824 a408 3 9a6521e5d SYNC ORA ORA 000 4824 a408 3 9a6521e5e SYNC ORB ORB 000 11d5 8d69 00c00d003b1e SYNC ORB ORB 001 j gt Dmt1 Dsk2 Volume 56e4954a 28d5 gt Vol45 Dsk0 Volume 56e4954a 28d5 gt Dmt1 Dsk1 Volume bf48a395 0ef6 Volume bf48a395 0ef6 11d5 8d69 00c00d003ble SYNC ORB ORB 002 11d5 8d69 00c00d003ble gt Dmt1 Dsk3 Volume bf 48a395 0ef6 Note Windows NT does not support the LDM volume so specify LETALL instead of Volume Offline backup using raidscan find sync for Windows file system The raidscan find syne command flushes the system buffer associated with a logical drive through finding a Volume guid corresponding to a group of the configuration file without using the x mount and x umount commands The following examples are for group ORB P VOL Side S VOL Side Close all logical drives on the P VOL by application e Flush the system buffer for P VOL using raidscan pi Volume find sync g ORB Split the paired volume using pairsplit g ORB with r w mode Open all logical drives on the P VOL by application Resynchronize the paired volume using pairresync g ORB Flush the system buffer for NEW S VOL data using raidscan pi Volume find sync g ORB Back up
245. e the SLPR so that the target port and the command device belongs to the same SLPR EX_ENOPOL 9 14 Not enough Pool in RAID Could not retain the pool for executing a command due to be exceeded the threshold rate Troubleshooting Please release the pair of older generations paired volume or re synchronize the pair of split status paired volume Hitachi Command Control Interface User and Reference Guide Error code EX_ENOOBJ Error message No such Object in the RAID Condition The specified object is not installed There are port LDEV and Hostgroup in the object Recommended action Specify the appropriate object Check the status of one of the following e 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 or RCU Target RCU LUN security is invalid The specified host group is not installed EX_EPPERM Permission denied with the privilege The specified command device does not have an authority to execute this command Check the operation authentication EX_ENQCLP Unmatched CLPR with JNL and Volume The specified command device does not have an authority to execute this command Check the operation authentication EX_CTXCHK Context check error An err
246. e value of maximum reserved capacity rate Get Command Async 2E10 6010 It cannot be deleted because the pool volume is Status set in the state of being deterred deleting Get Command Async 2E10 6011 Deleting operation cannot be done because it is Status being discarded pages Get Command Async 2E10 8002 The specified operation is not supported in the Status current microcode version Get Command Async 2E11 0O01F The operation cannot be done because a Thin Status Image or Copy on Write Snapshot pair remains or the association with a Dynamic Provisioning virtual volume exists Get Command Async 2E11 0020 The operation cannot be done because a Thin Status Image or Copy on Write Snapshot pair is being deleted or a Dynamic Provisioning virtual volume is being deleted Get Command Async 2E11 0021 The operation cannot be done because a pool Status volume of a specified pool is being formatted CMDRJE Executing 2E11 6003 The pool is not in the status where the pool can Get Command Async be deleted or a pool volume can be deleted Status Get Command Async 2E11 8003 The operation cannot be done because the power Status supply is switched off CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Executing 2E20 0003 The specified LDEV is not registered to the pool Get Command Async 2E20 0003 The operation cannot be done because the pool Status volume is not of a specified pool CMDR
247. ecurity to be definition set see Notes No security Only HORCM_DEV allowed User authentication required User authentication required Only HORCM_DEV allowed CMD security CMD security Only HORCM_DEV allowed CMD security User authentication required CMD security User authentication required Only HORCM_DEV allowed Notes e Only HORCM_DEV allowed the operation can be performed only for paired logical volumes described in HORCM_DEV User authentication required only commands issued by authorized users can be executed CMD security only devices recognizable from the host can be operated For details about CMD security see Data Protection facility on page 7 5 CCI functions 3 5 Hitachi Command Control Interface User and Reference Guide User authentication CCI allows user authentication by using the user information managed by Storage Navigator and the SVP User authentication is arbitrary in the Replication operation in the in band method while the operation by user authentication is mandatory in the configuration information operation and in the out of band method To enable the user authentication function the user authentication mode of the command device accessed by CCI must be enabled The user authentication function inputs a login command from the client server and to authenticate the user ID and password sent from CCI and the same typ
248. ecuted because the RCU identification code of a path is invalid CMDRJE Executing 2ED6 OOEF An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing 2ED6 3300 The SSID is invalid CMDRJE Executing 2EF3 3002 The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 43 SSB codes that are returned by raidcom delete ssid command raidcom delete ssid Error message Executing Async Executing Error code SSB1 SSB2 Description The CU number of the RCU exceeds the effective value Executing The command cannot be executed because the parameter of the specified RCU is invalid Executing The CU number is out of effective range Executing The operation cannot be done because the microcode is being changed Executing The serial number the product ID or the SSID of the remote storage system is invalid Executing The command cannot be executed because the specified RCU is not registered Executing The number of the specified SSIDs is invalid Executing An internal error occurred Call Hitachi Data Systems Support Center Executing The SSID is invalid 9 74 Executing The specified parameter is invalid Check the Command Control Interface Command Reference Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 44 SSB codes that a
249. ed After a while execute the same command Get Command Status Async An internal error occurred CMDRJE Executing The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 8 SSB codes returned by raidcom check_ext_storage external_grp raidcom check_ext_storage external_grp Error message Executing Async Executing Error code SSB1 SSB2 Description The external volume group is not in the effective range Executing The specified external volume has already disconnected the path or is in the process of checking path CMDRJE Executing The target LDEV is blocked CMDRJE Executing The path for the specified external path is in the state of disconnected CMDRJE Executing All the paths for the specified external path are blocked CMDRJE Executing There is no external volume group CMDRJE Executing There is no external path CMDRJE Executing Online from the mainframe host Get Command Status Async An internal error occurred by the operation of external path Call Hitachi Data Systems Support Center CMDRJE Executing Troubleshooting An internal error occurred by the operation of external volume Call Hitachi Data Systems Support Center 9 23 Hitachi Command Control Interface User and Reference Guide Table 9 9 SSB codes retur
250. ed as a command device CMDRJE Get Command Status Executing Async The specified volume cannot be used as a journal volume because it is a LUSE volume CMDRJE Get Command Status Executing Async The specified volume cannot be used as a journal volume because it is set by Data Retention Utility or Volume Retention Manager CMDRJE Get Command Status Executing Async Using the specified volume is prohibited by Volume Security CMDRJE Executing The internal volumes and external volumes exist in the specified journal Get Command Status 9 38 Async The emulation type of the specified volume is not supported Or the combination of an emulation type of the journal volume is incorrect Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add journal Error message Get Command Status Executing Async Error code SSB1 SSB2 Description The volume cannot be registered as a journal volume because the CLPR number of the specified volume differs from the CLPR number of the registered journal volume CMDRJE Executing The specified LDEV is a remote command device CMDRJE Get Command Status Executing Async The specified volume cannot be used as a journal volume because it is an external volume that can execute the I O suppression mode CMDRJE Get Command Status Executing Async T
251. ed as a journal volume because it is an external volume that can execute the I O suppression mode CMDRJE Executing The timer type cannot be changed because the specified journal belongs to the extended CT group Executing The parameter of inflow control cannot be changed because the specified journal is not a primary journal Executing The cache mode option or the data overflow monitoring time cannot be changed because the specified journal is used by both the primary and the secondary journals Executing 9 40 An internal error occurred Call Hitachi Data Systems Support Center Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 20 SSB codes that are returned by raidcom modify Idev mp_blade_id command raidcom modify Idev mp_blade_id Error code Executing Async spi ssB2 Error message Description Executing The number of LDEV exceeded the range Executing MP Blade ID is not in the effective range Executing The specified MP Blade is blocked Executing LDEV is not installed Executing The specified MP Blade is not installed Table 9 21 SSB codes that are returned by raidcom delete device_grp command raidcom delete device_grp Error message eee eee COS Description SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceeds the range of LDEV number CMDRJE Executing 2E20 0000 LDEV is not i
252. ed by raidcom modify port loop_id command raidcom modify port loop_id Executing Error code Async sspi ssB2 Executing The specified AL PA is invalid Error message Description Executing The specified topology is invalid Executing The other than fabric on cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The other than P to P point to point cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The command device being used at the local CCI exists under the port Executing The program product is not installed Executing Invalid host speed is set for the 4Gbps fibre adapter The available host speeds are AUTO 1G 2G and 4G only Troubleshooting 9 29 Hitachi Command Control Interface User and Reference Guide raidcom modify port loop_id Error code Executing Async sspi ssB2 Error message Description Executing Invalid host speed is set for the 8Gbps fibre adapter The available host speeds are AUTO 2G 4G and 8G only Executing The other than 10G cannot be specified when specifying a host speed of the package for Fibre Channel over Ethernet Table 9 14 SSB codes that are returned by raidcom modify port topology command raidcom modify port topology Executing Error code Async sspi ssB2 Executing The speci
253. ed creation or deletion CMDRJE Executing 2E00 3200 The value of port on the side of RCU is invalid CMDRJE Executing 2E00 7100 The CU number is out of effective range Get Command Async Status CMDRJE Executing 2E00 8400 The value of specified port is invalid Get Command Async Status Get Command Async 2E10 3101 Failed to establish a path or the deletion Status operation The following factor can be thought e Input parameter is invalid e Port status or the MP Blade status is in the state of abnormal e Cable is not connected correctly e Portis specified incorrectly Get Command Async 2E11 8004 The operation cannot be done because the Status microcode is being changed CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command Get Command Async 2E20 3000 The serial number the product ID or the SSID of Status the target storage system is incorrect Get Command Async 2E20 3001 A logical path cannot be added because the Status specified RCU is not registered Get Command Async 2E21 7101 The specified CU number is not defined or an Status LDEV is not defined under the CU number Get Command Async 2E23 3100 An RCU path cannot be added because the Status number of valid paths exceeds the maximum Get Command Async 2E23 3101 The operation cannot be done because the Status number of paths becomes less than the least path number CMDRJE Executing 2E30 840A The port attribute is not Initiator MCU Get Co
254. ed the porting requirements and restrictions One or two instances of CCI can be used simultaneously in UNIX Windows and OpenVMS operating system environments O Starting up on UNIX systems O Starting up on Windows systems Starting up on OpenVMS systems O Starting CCI as a service Windows systems Starting up CCI 4 1 Hitachi Command Control Interface User and Reference Guide Starting up on UNIX systems One instance To start up one instance of CCI 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 udp XXXXX the port name number for horcm conf If you want CCI to start automatically each time the system starts up add etc horcmstart sh to the system automatic startup file for example sbin rc Execute the horcmstart sh script manually to start the CCI instances horcmstart sh Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform ShadowImage operations set the HORCC_MRCF environment variable for the CCI execution environment For B shell HORCC_MRCF 1 export HORCC_MRCF For C shell setenv HORCC_MRCF 1 pairdisplay g xxxx xxxx group name Two instances To start up two instances of CCI on a UNIX system
255. ed volumes and associated with a copy group CCI functions Hitachi Command Control Interface User and Reference Guide Copy group function Defining a copy group by specifying two device groups one device group from primary side and one device group from secondary side whether they are inside or outside the storage system A copy group cannot be defined by specifying more than one device group from just one side of primary or secondary When a copy group is created which device group is primary and which is secondary cannot be specified 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 maintained in the storage system The notes when operating copy groups are shown below When creating a copy group e Incase of creating a copy group by executing a command a copy group cannot be created through direct specification of multiple LDEVs Create a copy group by specifying a device group e In one device group associated as a copy group the same device name cannot be defined e Copy groups with the same name cannot be defined within the same storage system e One device group cannot be defined to multiple copy groups e The maximum number of copy groups per storage system is 16 384 e Atthe time of consistency group creation pair creation and consistency group deletion pair deletion the collaboration
256. ed with EX_CMDRJE or EX_CMDIOE Also HORC cannot be operated to CC_SVOL copying in Volume Migration On one hand in copying CC_SVOL the copy operation for the volume migration is stopped if pairresyne command for of HORC is executed Data replication operations with CCI 6 43 Hitachi Command Control Interface User and Reference Guide E cc cc SVOL SVOL e LDEV type for Volume Migration The volume of the external connection for the volume migration must be mapped to an LDEV as OPEN V Universal Replicator MxN configuration and control Overview Policy 6 44 Universal Replicator supports 4X4 by using sysplex timers on the mainframe However open systems do not have an equivalent of sysplex timers on the mainframe because the SCSI protocol does not have timestamps If the open system CCI has the timestamp as an equivalent of sysplex timers Universal Replicator supports 4X4 on the open system e CCI delivers the timestamp CTQ Marker to the consistency group e Storage system RCU arbitrates the timestamp CTQ Marker across multiple storage systems connected remote command devices and then commits the journal data In this architecture CCI needs to be running If CCI has stopped the storage system RCU function does not appear to exist Therefore the better architecture is to include the storage system RCU function into CCI CCI already supports the group control across multiple storage systems in t
257. eds to add the group definition HORCM_CTQM in order to allow making TrueCopy Async UR 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 Data replication operations with CCI 6 45 Hitachi Command Control Interface User and Reference Guide 1 Defining to control UR MxN CCI supports a way to specify consistency Q Marker to the specified group by adding HORCM_CTQM as a keyword in horcm conf see example below HORCM CTQM groupinterval 10ms mode optional oradb300 where e group is to be allowed as a group across multiple storage systems e interval is the interval for the CTQ Marker recommended as a few second e 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 issued without freeze 2 Specifying different JID into CT group In order to support the MxN configuration it is necessary to specify a different journal ID JID into a CT group corresponding to a CCI group Thus CCI adds an option to specify Journal ID in horcm conf HORCM_LDEV dev_group dev_name Serial CU LDEV LDEV MU oradb dev1 30095 1 02 40 oradb dev2 310095 3 1 02 41 oradb dev3 30095 2 02 42 oradb dev4 30095 2 02 43 A Note The number at the end of the serial number f
258. efined_ldev bat load ldevconf_65 dat_ checkmode precheck C HORCM etc gt raidcom add ldev parity_grp_ id 01 01 ldev_id 1 capacity 100M C HORCM etc gt raidcom add ldev parity_grp_ id 01 01 ldev_id 2 capacity 100M C HORCM etc gt raidcom add ldev parity_grp_id 01 01 ldev_id 3 capacity 100M C HORCM etc gt raidcom add ldev parity_grp_id 01 01 ldev_id 1 capacity 100M raidcom LDEV 1 is already existing as status is 1 on UnitID 0 raidcom_ 5 EX _CTXCHK Context Check error C HORCM etc gt raidcom add ldev parity_grp_id 01 01 ldev_id 2 capacity 100M raidcom LDEV 2 is already existing as status is 1 on UnitID 0 raidcom_ 6 EX _CTXCHK Context Check error C HORCM etc gt raidcom add ldev parity_grp_ id 01 01 ldev_id 3 capacity 100M raidcom LDEV 3 is already existing as status is 1 on UnitID 0 raidcom_ 7 EX _CTXCHK Context Check error The number in raidcom of raidcom_ 7 EX_CTXCHK Context Check error is the number of times of performing the raidcom command by using lt work file gt The number of times is incremented each time the raidcom command is executed Port check The check is performed from the following perspective Note that checking for object information related to the port such as external volume group or RCU or an attribute of port is not executed Checking for attribute setting It is checked whether the operation is performed for the e
259. elease lock and unlock of resource groups are as follows e raidcom lock resource resource_name lt resource group name gt time lt time sec gt Locking a specified resource group e raidcom unlock resource resource_name lt resource group name gt Unlocking a specified resource group If multiple users IDs operate the same resource by confirming by the raidcom lock resource command that no other user is using the resource the operation competition for the relevant resource can be prevented After the configuration change is completed release the lock status by the raidcom unlock resource command 3 14 CCI functions Hitachi Command Control Interface User and Reference Guide Command execution modes Overview Provisioning operations are performed using a configuration setting command For details about the configuration setting command see Overview of the configuration setting command on page 5 2 or Command Control Interface Command Reference Two modes can be used for executing the configuration setting command e Line by line mode This mode executes commands input from the command line one ata time e Transaction mode Executes a script file specified by the zt option When executing the configuration setting command the following checks can be done depending on the above two mode types e Syntax check This function checks if there is no syntax error in the specified command This is executed every time at
260. ence Guide spawn nowait process horcm horcmstart Note The subprocess HORCM created by SPAWN is terminated AN when the terminal is LOGOFF or the session is terminated If you want an independent process to the terminal LOGOFF use the RUN DETACHED command 3 Confirm the configuration Set the log directory HORCC_LOG in the command execution environment as required Note Ifthe log directory under SYS POSIX_ROOT is shared with AN other nodes the log directory of Horc Manager must be set for each node The log directory of Horc Manager can be changed by setting the parameter of horcmstart See the Command Control Interface Command Reference for information about horcmstart parameters If you want to perform ShadowImage operations set the environment variable HORCC_MRCF HORCC_MRCF 1 pairdisplay g XXXX XXXX group name Note Ifa system configuration change or a RAID configuration change AN causes this file to change for example cache size change or microcode change these changes will not take effect 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 instances To start up two instances of CCI 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
261. er In the case of Failure PSUE PSUS e Issues SwapSuspend to make a suspending state for CT group on each RCU e Searches commits a minimum matching point of the CTQ Marker on RCU via RCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on all RCU via RCU e Issues End of Suspend to terminate a suspending state 5 pairsplit R option In the case of PAIR state NO failure e Issues Delete to make a deleting state for CT group on each RCU e Searches commits a minimum matching point of the CTQ Marker on RCU via RCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on MCU on all RCU via RCU e Issues End of Delete to terminate a deleting state after committed with an EOM End Of Marker on all RCU Exception If an uncommitted state that is link failure is detected while executing its operation then the operation of committing is aborted on keeping current CTQ Marker level and a deleting state terminates with detecting at least one EOM End Of Marker In the case of Failure PSUE PSUS e Issues Delete to make a deleting state for CT group on each RCU e Searches commits a minimum matching point of the CTQ Marker on RCU via RCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on all RCU via RCU e Issues End of Delete to termin
262. er and Reference Guide Creating a Copy on Write Snapshot pair The CCI command for creating a Thin Image or Copy on Write Snapshot pair is the same as for ShadowImage However Thin Image pair can only operate up to 64 S VOLs Therefore use raidcom command if you want to operate more than 64 S VOLs The RAID storage system determines whether it is a ShadowImage pair or a Thin Image Copy on Write Snapshot pair by the attribute of the S VOL The RAID storage system also determines whether it is a Thin Image pair or a Copy on Write Snapshot pair by the type of the pool to be used A Thin Image pair is generated in the following two cases e When a V VOL OPEN OV is specified as an S VOL e When a pool for Thin Image is specified as the pool type A Copy on Write Snapshot pair is generated in the following two cases e When a V VOL OPEN OV is specified as an S VOL e When a pool for Copy on Write Snapshot is specified as the pool type A V VOL has the following characteristics e It appears as OPEN OV to identify a V VOL easily via the SCSI Inquiry or CCI e AV VOL unmapped to the S VOL of a Copy on Write Snapshot will reply to a SCSI Inquiry but Reading and or Writing is not allowed LDEV will reply the capacity setting as an LU to SCSI Read Capacity e A V VOL that has become the S VOL of a Copy on Write Snapshot will reply to a SCSI Inquiry and Reading and or Writing is allowed Copy on Write Snapshot pair status Each paired
263. er 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 LUN Manager software or SNMP When you define the command device the DataProtection Facility is turned ON or OFF to each command device which has an attributes to enable the Data Protection Facility CCI distinguishes the ON from OFF attribute when CCI recognizes the command device Figure 7 1 Definition of the protection volumes on page 7 6 shows the definition of protected volumes A Note Ifthe command device is set to enable protection mode there is no impact on CCI operations CCI controls pairs under current specification For details about the command operations when the Data Protection Facility is turned ON see Target commands for protection on page 7 9 Permitted volumes Protected volumes volumes on Host view via LUN Security Host lt volumes on Horem cont via protection On command device Figure 7 1 Definition of the protection volumes Data Protection Facility specifications 7 6 Only the permitted volumes can be registered in horcm conf When creating the horcm conf file describe volumes only from the view that the host shows CCI manages mirror descriptors TrueCopy ShadowImage MU 0 1 2 as a unit The Data Protect
264. eration It is possible to execute the Volume Migration as a group by describing it to the horcm conf however LU LDEV which was mapped to S VOL after command execution does not maintain the consistency of the group In other words you must consider the volume mapped to the S VOL after execution as the discarded volume When HORCM demon is KILLed or the host has crash during group operation the group aborting the execution of the command has LUN mixed with the external connection and RAID Group as the group In this case CCI skips the executed LU and issues the CC Volume Migration command to the un executed LU and an identical command is executed once again 4 Using MU CCI manages the status of TC SI using MU so CCI uses the empty MU that is managed for SI Therefore execute the command of the volume migration in the environment for SI having HORCC_MRCF environment variable An example is shown below It is possible to specify It is possible to specify MU 1 or MU 2 for CC MU 2 for CC 5 HORCM instance Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide It is possible to describe the original and target volume for the volume migration to MU as another group in horcm conf for HORCM instance of SI and or TC Also it is possible to define the original and target volume for the volume migration in the horcm conf as HORCM instance independent from SI TC Commands to con
265. error codes returned by these commands e horctakeover e paircurchk paircreate pairsplit pairresync pairevtwait pairvolchk pairsyncwait pairdisplay In this table Unrecoverable indicates errors that cannot be recovered by reexecuting the command and Recoverable indicates errors that can be recoverable by reexecuting the command 9 16 Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 3 Generic error codes horctakeover and pair commands Category Syntax for Argument Unrecoverable Error code EX_REQARG Error message Required Arg list EX_INVARG Invalid argument EX_INVNAM Invalid name of option EX_UNWOPT Unknown option EX_UNWCOD Unknown function code EX_UNWCMD Unknown command EX_ERANGE Result too large EX_ENAMLG File name too long EX_INVRCD Invalid return code Configuration Unrecoverable EX_ENOGRP No such group EX_ENOENT No such device or group EX_ENODEV No such device EX_ENLDEV No such LDEV within the RAID EX_ENOUNT No such RAID unit EX_INVMUN Invalid mu with HORC or HOMRCF EX_ENQSER Unmatched Serial vs RAID unitID EX_EXTCTG Extended CTgroup across RAIDs EX_ENQCTG Unmatched CTGID within the group EX_ENPERM Permission denied with the LDEV EX_ERPERM Permission denied with the RAID EX_ESPERM Permission denie
266. error is detected If it is not clear whether the target port or host group exists or not if the target port or host group information does not exist in the configuration definition file the error is not detected The command as the target of the check is shown below e raidcom delete host _grp port lt port gt lt host group name gt For example if the host group that does not exist is attempted to be deleted an error is detected An example of the script where the error is detected and the execution result of the actual context check are shown below e Example of script the text in bold indicates the part of incorrect configuration definition raidcom delete host_grp port CL1 A 0 raidcom delete host_grp port CL1 A 1 raidcom delete host_grp port CL1 A 2 e Execution result the text in bold indicates the contents of the error accompanying the invalid configuration definition in the script CCI functions 3 23 Hitachi Command Control Interface User and Reference Guide C HORCM etc gt raidcom get host_grp port CL1 A store hostgrpcnf_27_cli a dat PORT GID GROUP_NAME Serial HMD HMO_BITs CL1 A 0 1A GO00 64539 LINUX IRIX C HORCM etc gt raidcom zt 6_no_hstgrp bat load hostgrpcnf_27_cli a dat checkmode precheck C HORCM etc gt raidcom delete host_grp port CL1 A 0 C HORCM etc gt raidcom delete host_grp port CL1 A 1 raidcom PORT HGRP 0 1 does not exist as status is 2 on UnitID 0 raidcom_ 3 EX_CTXCHK
267. es 2 9 Host machines that can be paired 1 ee es 2 11 Configuration definition file 0 0 0 cee ees 2 12 OVEIVIEW sec acute cae Beeb HGS eee eo oe Meee KS Pee eter ed 2 12 Configuration definition file settingS 0 00 cece eee eee 2 15 Configuration definition for cascading volume pairs 0055 2 25 Configuration file and mirror descriptors 00 e eee eee 2 25 Cascading connection and configuration files 0005 2 26 ShadowImage obese che eee eee Geb bee eess Dew its eee as 2 27 Cascading connections for TrueCopy and ShadowImage 2 29 CCI Software files a na a see 46S ee ewes GONG Bae ee ee ewe yee es 2 31 CCI files supplied with the software 0 000 ce eee eee eee 2 32 CCI files for UNIX based systems 0 000 ce eee eee 2 32 CCI files for Windows based systems 0 00 cence eee eee 2 33 CCI files for O penVMS based systeMS 0 0 eee eee ee 2 35 CCI log and trace TAS lt 3 cs 32 53445 oeee 6446 445 She eee He2s ecb ese es 2 35 COMO MNES w wa ta8s ate Kew eee ae bebe ww thee bee ewe g 2 36 CCI trace files csa cati eek ew ew seuSe aes eee Ries Se a a eas 2 38 CCI trace control command 24s eee accs ees eee beware t awe eee 2 38 Command logging for audit naaa 0c cc es 2 39 Logging other than raidcom command 0000 0 eee eens 2 39 Logging raidcom command 0 00 cee ees 2 41 User created files 24 03 50 050654 e644e44 05 e8 486 eee Gee e See
268. es are also Data replication operations with CCI 6 33 Hitachi Command Control Interface User and Reference Guide put into pooling volumes called a Snapshot pool and a Snapshot pool is specified as a pool ID when a Snapshot is made Copy on Write Snapshot and volume mapping is illustrated in Figure 6 13 Copy on Write Snapshot and volume mapping on page 6 34 STD Inquiry STD Inquiry OPEN OV OPEN OV LDEV20 LDEV22 NG SnapShot pool we Figure 6 13 Copy on Write Snapshot and volume mapping Copy on Write Snapshot volumes 6 34 The specifications for Copy on Write Snapshot volumes are e Allowable type of paired volume The supported volume type is OPEN V only for P VOL and OPEN OV for S VOL e Number of volumes Copy on Write Snapshot can be paired This depends on P VOL capacity Copy on Write Snapshot pool capacity and shared memory capacity on the RAID storage system e Duplicated writing mode Copying on write e Number of mirror volumes o Thin Image Up to 1 024 secondary volumes can be defined for each P VOL o Copy on Write Snapshot Up to 64 secondary volumes can be defined for each P VOL For details on Thin Image or Copy on Write Snapshot specifications such as maximum number of mirrored volumes volumes and operations please see the Hitachi Thin Image User Guide or Hitachi Copy on Write Snapshot User Guide for your storage system Data replication operations with CCI Hitachi Command Control Interface Us
269. es of information maintained by the storage system issues an authentication request to the authentication module SVP If the user ID and password sent from CCI are authenticated CCI for the once authenticated user the user on the client starting up CCI stores the user ID and password This saves the necessity of inputting the user ID and password each time a command is executed If the user logs out the user ID and password stored by CCI are deleted If the user ID and password are different the command is rejected and CCI automatically performs the logout processing for it and requires the user authentication processing user ID and password input again A Note e 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 e If specific user information or authority information is changed delete the user ID and password maintained by the storage system from the SVP Therefore perform the user authentication processing on CCI again e If the communication with the SVP in the out band method cannot be performed the new authentication cannot be performed Command operation authority and user authentication When CCI is used with the user authentication function enabled commands are executed complying with the operation aut
270. es the user who executes the command has been authenticated already After that CCI obtains the access authority of the resource groups that are configured on the user roles and then compares the access authority of the user and the specified resources Checking resource authorities If the access is not permitted by comparing the access authorities of the resource groups configured on the user roles and the specified resource CCI rejects the command with an error code EX_EGPERM If the resource groups are defined among the large storage systems the specified resource is compared with the resource specified by obtaining the access authority configured to each large storage system Target commands CCI checks resource authorities on the following commands that use command devices e raidcom commands commands for setting configurations e horctakeover horctakeoff paircurchk paircreate pairsplit pairresync pairvolchk pairevtwait pairsyncwait pairmon e raidscan find verify find inst find sync except for d pairdisplay raidar raidqry except for I and r e raidvchkset raidvchkscan except for v jnl raidvchkdsp CCI functions 3 7 Hitachi Command Control Interface User and Reference Guide Relation between user authentication and resource groups In user authentication mode CCI verifies the access authority of the relevant resource based on the user authentication and the role of it Also on the user authenti
271. ev gt ldev_name lt Idev naming gt Available provisioning operations The following provisioning operations can be performed using CCI Operation type Log in Login and logout Corresponding command raidcom login lt user_ name gt lt password gt Log out raidcom logout Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation type Description Corresponding command Resource Lock resource raidcom lock resource resource_name lt resource group name gt time lt time sec gt Unlock resource raidcom unlock resource resource_name lt resource group name gt Display resource group raidcom get resource information Add resource group raidcom add resource resource_name lt resource group name gt resource_id lt resource group_id gt ldev_id lt ldev gt port lt port gt port lt port gt lt host group name gt parity grp_id lt gno sgno gt external_ grp_id lt gno sgno gt Delete resource group raidcom delete resource resource_name lt resource group name gt ldev_id lt ldev gt port lt port gt port lt port gt lt host group name gt parity grp_id lt gno sgno gt external_ grp_id lt gno sgno gt Host Create host group raidcom add host_grp port lt port gt see the Provisioning host_grp_name lt host group name gt Guide for the storage Set host mode raidcom modify host_grp port
272. ev ldev_id cnt 65280 Executed Executed Executed Not store lt work file gt executed raidcom zt lt script file gt load lt work_ file gt checkmode precheck Command execution by the out of band method In the CCI before supporting Hitachi Virtual Storage Platform a command can be executed only from the host connected by the fibre channel directly This is known as in band operations In the CCI supporting Hitachi Virtual Storage Platform a command can be executed from any client PC connected to the storage system via LAN not just from connected hosts This is known as out of band operations e For in band CCI operations the command device is used which is a user selected and dedicated logical volume on the storage system that functions as the interface to the storage system on the UNIX PC host The command device accepts read and write commands that are executed by the storage system e For out of band CCI operations a virtual command device is used The virtual command device is defined in the configuration definition file by an IP address on the SVP CCI commands are issued from the client or the host server and transferred via LAN to the virtual command device and the requested operations are then performed by the storage system The following figure illustrates in band and out of band CCI operations Overview 1 5 Hitachi Command Control Interface User and Reference Guide Script file The both ways a
273. ever CCI may encounter Linux kernel that does not support the ioctl SG_IO fully so CCI also supports by defining either following environment variable or HORCM etc USE_OLD_IOCTL file size 0 that uses the ioctl SCSI_IOCTL_SEND_COMMAND forcibly For example export USE OLD IOCTL 1 horcmstart sh 10 HORCM etc rYw 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 Y xr r 1 root sys 282713 Nov 10 20 02 horcmgr CCI cannot be If you have changed the configuration definition file settings make started because sure that the configuration definition file you changed is correct horcmstart If you have changed the settings of the storage system make sure command fails y g J eas that the settings you changed are correct and if necessary change the configuration definition file settings Even if there are no problems in these files and settings but if you cannot run CCI get all log files under the specified directory by HORCM_LOG the default setting horcm log and then contact the Hitachi Data Systems Support Center 9 2 Troubleshooting Hitachi Command Control Interface User and Reference Guide Operational notes and restrictions for CCI operations For maintenance of volumes used by CCI and the HDS features it supports if a volume failure occurs it is important to find the failure in the paired volumes recover the volumes and continue operation on the original
274. exporting the results of the volume discovery on the remote server Example from UNIX Solaris ls dev rdsk cit ingraid CLI export INQRAID CL4 G 64015 0 124 O0PEN V CM dev rdsk c1t0d0s2 INQRAID CL4 G 64015 1 124 OPEN V CM dev rdsk cl1t0d1s2 INQRAID CL4 G 64015 2 95 OPEN V dev rdsk c1t0d2s2 INQRAID CL4 G 64015 3 95 0PEN V dev rdsk c1t0d3s2 INQRAID CL4 G 64015 4 95 OPEN V dev rdsk c1t0d4s2 INQRAID CL4 G 64015 5 95 O0PEN V dev rdsk c1t0d5s2 INQRAID CL4 G 64015 7 95 OPEN V dev rdsk c1t0d7s2 2 A way to export import using pipe amp SSH Example for exporting from UNIX Solaris to CCI host ls dev rdsk cit inqraid CLI export ssh lt CCI host gt raidscan find inst DEVICE 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 0 64015 3 Example for Verifying from UNIX Solaris to CCI host ls dev rdsk clt inqraid CLI export ssh lt CCI host gt raidscan find verify DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c1 to0d0s2 64015 0 dev rdsk c1it0d1s2 x 2 2 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 c1 t0d4s2 7 64015 4 dev rdsk c1t0d5s2 m ENA 64015 5 dev rdsk c1t0d7s2 7 z a 64015 7 6 56
275. face User and Reference Guide raidcom login USERO PASSO1 raidcom lock resource resource grp name meta Y esour ce for 1 MMi in C0 1 9 do C raidcom add dew par ity_grp_id 1 1 emulation 3390 Y cyl inder 483078 Idew_id AN l raidcom get command_status raidcom reset command_statu for 1 MMi in C0 1 99 do raidcom initialize Idew dew_id Ai operation qf mt l raidcom get command_status raidcom reset command_status for 1 Bi in C0 1 9 do raidcom modify Idew Idev_id Hi Wey wo lume ani dev i e_nane 1 for 1 Bi in C0 1 3 do raidcom modify Idew Idev_id Xi mp_blade_id 2 l raidcom get dew Idev_id 0 ent 10 raidcom add dp_pool pool_id 1 Idew_id 0 ent 10 raidcom get command_status raidcom reset command_status for 1 XXi in 10 1 19 dof raidcom add oew Idev_id si emulation 3390 8 cyl inder 3420 pool 1 l raidcom get command_status raidcom reset command_status for 1 XXi in 10 1 29 do rFaidcom modify Ideyv Idev_id Mi device_name wy vir tual vo lume Hi J sLog in with the user ID USEROI and the Password PASSO1 sLock the resource group meta_resour ce Create each 10 of Parity_grp_id 1 1 483078 cyl inder LOEY to CLOEY 0 to 9 Execute the quick format to LDEY 0 to 5 2 Give a nickname to LOEYIO to 9 Emy wo lume O to 9 pSet the LDEY WP Blade ID of LOEY 0 to 9 to 32 Ej Display the information of LOEW O to 3CInternal YOL pCreate
276. fault of full space of the instance because the command device interprets as assignment of the instance from CCI CCI software environment 2 3 Hitachi Command Control Interface User and Reference Guide 2 4 CCI has TWO phases that it reads to acquire usable LBA and writes with the acquired LBA in attaching sequence to the command device so the command device can confirm whether it was required as the assignment for CCI or not by detecting and adding two status bits to the instance assignment table HOST RAID CCI Command Device Read Instance Request Actual allocation Getting LBA ra Getting Write with LBA Configuration to get configuration Figure 2 1 Current assignment sequence HOST RAID CCI Command Device Read Instance Request Temporary allocation Getting LBA a Getting Write with LBA Configuration to get configuration Actual allocation Figure 2 2 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 instance assignment clear up all temporary allocation 1 0 and then reassign the required instance automatically This does not require a servic
277. fic Control Synchronized I O is issued from a virtual command device The queueing time may occur because of the heavy I O traffic because the virtual command device has to relay the command to the next virtual command device in the cascade configuration using the virtual command device To improve the response in this environment define the configuration so that asynchronous I O is issued using the following environment variables SHORCM_ IPSCPAIO 1 Security setting Following security can be set e Specifying security of IP address and port number By defining IP address and port number of the client PC that issues command to virtual command device to HORCM_ALLOW_INST in the configuration definition file users who can use virtual command device can be restricted For the details about the settings to HORCM_ALLOW_INST please refer to Configuration definition file e Security setting for virtual command device CCI functions Hitachi Command Control Interface User and Reference Guide By using the following environment variable security can be set to virtual command device SHORCM_IPCMDSEC lt value gt Specify the number from 0 to 7 to lt value gt depending on the contents of the security which you want in reference with the following table Table 3 1 Security setting for virtual command device Command device setting Value specifying User to lt value gt Security setting authenticatio n Device group S
278. fied AL PA is invalid Error message Description Executing The specified topology is invalid Executing The other than fabric on cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The other than P to P point to point cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The command device being used at the local CCI exists under the port Executing The program product is not installed Executing Invalid host speed is set for the 4Gbps fibre adapter The available host speeds are AUTO 1G 2G and 4G only Executing Invalid host speed is set for the 8Gbps fibre adapter The available host speeds are AUTO 2G 4G and 8G only Executing The other than 10G cannot be specified when specifying a host speed of the package for Fibre Channel over Ethernet Executing Topology FC AL and 16G as the host speed is not supported for the 16Gbps fibre adapter Table 9 15 SSB codes that are returned by raidcom modify port security _switch command raidcom modify port security _switch Executing Error code Async sspi ssB2 Error message Description Executing The specified AL PA is invalid Executing The specified topology is invalid 9 30 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify port security _
279. finition file A ORCM_LDEV CU LDEV LDEV MUH Copy Group dbA 00 0 00 02 00 03 oradbU oradb03 oradb04 30095 30095 ORCM_LDEV tdev croup dev name Serial oradb0l 30096 CU LDEV LDEV MUH ora 96 01 0 oradb03 30096 01 02 HbB oradb04 30096 01 03 Copy Group dbB Copy Group dbA Pr i adb02 00 01 Copy Group dbB or Pal Serial 30095 Serial 30096 Figure 3 3 LDEV grouping for USP V VM and earlier For Virtual Storage Platform and later CCI can be used to create a group of multiple LDEVs by defining device groups This is accomplished by defining device groups in either the primary or secondary configuration definition file but not both By defining a device group LDEV information can be changed or defined in one operation It is not required to modify LDEV information in both configuration definition files For example referencing LDEVs or creating pools can be executed at the same time because all LDEVs in the device group are subjected to the operation CCI functions 3 27 Hitachi Command Control Interface User and Reference Guide Specifies the device group name Unnecessary to specify LDEV or LUN Copy Group dbA Configuration Definitiog file A ORCM_LDEVG tcopy_group Idev_group Serial CUNE CLD Ss LLD i a rs m pe Recognize the ile B group information of Serial 30036 OR
280. following example a pair for device name A can be created but not for device name B and C because they have different names o Creating a pair in cases where the device names in two device groups in a copy group configured 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 device name B and C although it does not change the paired status but an error occurs because they have different device names o Creating a pair in cases where the numbers of LDEVs in two device groups in a copy group configured of simplex volumes are different In the following example pairs are created for the device name A to A and B to B 3 40 CCI functions Hitachi Command Control Interface User and Reference Guide Pair operations with mainframe volumes You can create a pair with mainframe LDEVs using CCI However some of the replication functions are not available in CCI For more detailed information see the user manual for the replication function Hitachi TrueCopy for Mainframe User Guide Hitachi Universal Replicator for Mainframe User Guide or Hitachi ShadowImage for Mainframe User Guide Using dummy LUs for mainframe LDEVs Pseudo LUs called dummy LUs are used to access mainframe LDEVs in CCI The dummy LUs are unconditionally defined for all mainframe device emulation types Since the dummy LUs are used only by CCI other user
281. for split e JNL Consistency Suspend suspends after JNL Consistency Restore e JNL Full Suspend suspends after JNL Full Restore Configuration examples 6 52 CCI does not change the command options for supporting Universal Replicator MxN Open However the output of the command is added so that the command can display the CT group and Q Marker for each storage system because the CT group and Q Marker are managed on each storage system Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 1 UR 2x2 HORCMO on production HORCM_MON ip_address service poll 10ms timeout 10ms NONE horemO 1000 3000 fpfrecseaewes For HORCM_CMD evecansovcaasores UnitID 0 Serial t 64034 4 Serial t 64045 WACMD 64034 dew rdsk ACMD 64045 devirdsk gireenansees For HORCM_LDEV aanerennnneeennn A LDEV MU 400 64034 401 64045 400 64045 401 O OE For HORCM_INST ER EE HORCM_INST dev_group ip_address service ora RHOST horcmO gee For UR of multiple DKC HORCM_CTQM dev_group interval 10ms mode ora 300 Production Server RM Data replication operations with CCI Ht HORCMO on Remote HORCM_MON ip_address service poll 10ms timeout 10ms horemO 1000 3000 yyesewecaace For HORCM_CMD staeweasseosecans UnitID 0 Serial 64035 1 Serial 64046 CMD 64035 dev rdsk CMD 64046 dev rdsk pj eraan For HORCM_LDEV EN HORCM_LDEV de
282. fy that HORCM is running and or that HORCMINST is set correctly EX_ATTDBG 9 8 Can t be attached to a Debug layer Failed to communicate with HORCM or cannot make a log directory file Troubleshooting Verify that HORCM is running by using UNIX commands ps ef grep horcm Hitachi Command Control Interface User and Reference Guide Error code Error message Condition Recommended action EX_INVNAM Invalid name of The name specified in Please designate the correct 249 option an argument of an name using the h option option is not appropriate EX_OPTINV A specified option Detected contradiction Contact the Hitachi Data 248 is invalid in information that Systems Support Center RAID reported EX_ENOENT No such device or The designated device Verify the device or group 247 group or group name does name and add it to the not exist in the configuration file of the configuration file remote and local hosts EX_ENODEV No such device The designated device Verify the device name and 246 name does not exist in add it to the configuration the configuration file file of the remote and local hosts EX_ENOUNT No such RAID unit The designated RAID Verify the RAID unit ID and 219 unit ID does not exist add it to the configuration in the configuration file of the remote and local file hosts EX_ENQSER Unmatched The group designated
283. g group CTGID using volume 0 255 for VSP the pairvolchk command G1000 VSP USP V Then please create a pair VM TagmaStore USP specifying CTGID as the TagmaStore NSC 0 paircreate f option 127 for HUS VM and 9900V 0 15 for 7700E EX_EXTCTG Extended CT A TrueCopy Async UR Please confirm the serial of 216 group across or ShadowImage the volumes by using the RAIDs volume is defined in pairdisplay command to the configuration file verify that the CT group is HORCM_CONF asa contained completely within group that extends one RAID storage system across storage systems EX_ENXCTG No CT groups left An available CT group Please confirm whether all 215 for OPEN Vol use for OPEN Volume does CT groups are already used not exist by mainframe volumes Troubleshooting 9 13 Hitachi Command Control Interface User and Reference Guide Error code EX_ENQCTG Error message Unmatched CTGID within the group Condition The CT group references within a group do not have an identical CTGID Recommended action Please confirm the CTGID using the pairvolchk command and confirm that group references within the configuration file HORCM_CONF refer to the same CT group EX_ENPERM Permission denied with the LDEV A device mentioned in the configuration file does not have a permission for a pair operation Please confirm whether pair operation is permitted on the device by using the pairdisplay Of
284. g of the specified port is deleted Resource group function and restrictions when running Server Priority Manager When you use the resource group function the range of operation is limited per port of resource group by Server Priority Manager The threshold value the SPM name and the SPM group name which are managed in the entire system are common among the resource groups When you perform Server Priority Manager operations using the resource group function share the threshold value that the storage administrator determines among users of resource groups Determine rules for SPM names and SPM group names including port names to avoid redundant names between ports Virtual storage machine operations VSP G1000 only e Creating host groups in a virtual storage machine on page 5 52 e Adding LDEVs to a virtual storage machine on page 5 53 e Removing the virtual storage machine on page 5 53 Creating host groups in a virtual storage machine Use the following provisioning operations to create host groups in a virtual storage machine and to assign virtualized LDEV to LU Operation overview Reserving host group IDs Description Reserve ports and host group IDs to the resource groups in the virtual storage machine Be sure to execute the command before creating host groups Executed command raidcom add resource resource name lt resource group name gt port lt port gt lt HG gt Creating host g
285. ge even if the LDEV is deleted from the device group Use Cases The following shows use cases that can be deleted an LDEV from a device group o Deleting an LDEV simplex volume not associated with a copy group from a device group Deleting an LDEV paired volume not associated with a copy group from a device group Deleting 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 CCI functions 3 33 Hitachi Command Control Interface User and Reference Guide Device group deletion Deleting an LDEV that configuring a device group by specifying a created device group name and 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 is deleted the pair status of the pair in the device group does not change 3 34 Use Cases The following shows use cases that can be deleted an LDEV from a device group o Deleting a device group configured of simplex volumes and not associated with a copy group delete Deleting a device group configured of a simplex volume and a paired volume and not associated with a copy group delete Deleting a device group configured of simplex volumes and associated with a copy group delete Deleting a device group configured of pair
286. group name grp1 only omitting device name C HORCM etc gt gt raidcom add lun port CL8 A grp opt ldev device_grp_ name grpl GROUP grpl DEVICE data0 UnitID 0 LDI 17000 0x4268 1 PORT CL8 A LUN none raidcom LUN 0 0x0 will be used for adding done GROUP grpl DEVICE data0 UnitID 0 I 17001 0x4269 1 CL8 A LUN none raidcom LUN 1 0x1 will be used for adding done GROUP grpl DEVICE datal UnitID 0 I 17002 0x426A 1 CL8 A LUN none raidcom LUN 2 0x2 will be used for adding done GROUP grpl DEVICE datal UnitID 0 1 17003 0x426B 1 CL8 A LUN none raidcom LUN 3 0x3 will be used for adding done C HORCM etc gt gt raidcom get lun port CL8 A 0 GID HMD LDEV Serial HMO_BITs Cl 0 LINUX IRIX 17000 64577 C 0 LINUX IRIX 17001 64577 Cl 0 LINUX IRIX 17002 64577 C 0 LINUX IRIX 17003 64577 The following shows the example for specifying device groups and creating journal Provisioning operations with CCI 5 15 Hitachi Command Control Interface User and Reference Guide C HORCM etc gt raidcom add device_grp device_grp_name dg_jnli datai Idev_id 512 513 514 515 C HORCM etc gt raidcom get device_grp LDEV_GROUP Serial dg_jn11 64539 C HORCM etc gt raidcom get device_grp device_grp_name dg_jnl1i LDEV_GROUP LDEV_NAME LDEV Serial dg_jn11 datal 512 64539 dg _jnll datal 513 645
287. gt operation qfmt Restoring an LDEV raidcom modify Idev ldev_id lt ldev gt status nml Creating virtual volume for raidcom add Idev pool lt pool ID gt lt pool naming gt snap Dynamic Provisioning Dynamic Idev_id lt Idev gt capacity lt size gt Provisioning for Mainframe Dynamic Tiering or Copy on Write Snapshot Deleting virtual volume for raidcom delete Idev ldev_id lt ldev gt grp_opt lt group Dynamic Provisioning Dynamic option gt device_grp_name lt device group name gt lt device Tiering or Copy on Write name gt Snapshot Creating a pool adding a pool raidcom add dp_pool pool_id lt pool ID gt pool_name volume for Dynamic Provisioning or lt pool naming gt pool_name lt pool naming gt pool_id lt pool Dynamic Provisioning for ID gt pool_id lt pool ID gt pool_name lt pool naming gt Mainframe Idev_id lt Idev gt cnt lt count gt grp_opt lt group option gt device_grp_name lt device group name gt _ lt device name gt user_threshold lt threshold_1 gt lt threshold_2 gt Creating a pool adding a pool raidcom add snap_pool pool_id lt pool ID gt pool_name volume for Snapshot lt pool naming gt pool_name lt pool naming gt pool_id lt pool ID gt pool_id lt pool ID gt pool_name lt pool naming gt lIdev_id lt Idev gt cnt lt count gt grp_opt lt group option gt device_grp_name lt devic
288. gurations O LDM volume discovery and flushing for Windows O Special facilities for Windows systems O Host group control O Using CCI SLPR security Examples of using CCI commands 8 1 Hitachi Command Control Interface User and Reference Guide Group version control for mixed storage system configurations Before executing each option of a command CCI checks the facility version of the storage system internally to verify that the same version is installed on mixed storage system configuration If the configuration includes older storage systems for example 9900V this method may not meet the requirements for the mixed storage system environment because the older storage system limits the availability enhancements in later facility versions If the facility versions of the storage systems are different you cannot use TagmaStore USP TagmaStore NSC specific facility because CCI applies the minimum version to all storage systems To expand the capability for mixed storage system configurations and avoid problems such as this CCI supports the following group version control to manage a version for each group e CCI HORCM daemon makes a facility version for each group based on a configuration file at the startup of HORCM e Ina mixed storage system configuration if the facility version of the storage systems for example USP V VM and TagmaStore USP TagmaStore NSC is different on a group CCI will apply the minimum vers
289. h host When changing copy group information editing of the configuration definition file was required on each host In CCI supporting VSP the group information that is registered into the storage system can be used as it is The LDEV grouping function for VSP can minimize the description of the configuration definition file of CCI on each host When the copy group information changes you need to update only one configuration file saving time and eliminating the chance for error due to mismatching edits This new functionality is implemented using device names device groups and copy groups e Device name o A name that can be given in one LDEV per the device group o Each name is associated with a device group in which the LDEV belongs to o An LDEV nickname can be given to the LDEV as a unique name for the LDEV that is not related with device group Only one LDEV nickname can be given for each LDEV e Device group o A group of one or more LDEVs One LDEV can belong to multiple device groups o A device group can belong to only one copy group o If you want to construct a mirror or cascade you need to define a different device group and a device name in each copy group e Copy group A group that is defined by specifying two device groups one device group at the primary side and one device group at the secondary side Overview 1 7 Hitachi Command Control Interface User and Reference Guide Resource group function Usi
290. h of a device name must be up to 32 characters 3 30 CCI functions Hitachi Command Control Interface User and Reference Guide e Inthe device group that does not become an element of copy a group the same device name can be used in the same device group e Inthe device group that becomes an element of a copy group a device group name must be unique in the device group It is because a pair is created between LDEVs that have same device names in respective primary and secondary volumes at the group operation of a replication series command Notes when specifying a device group name e The length of a device group name must be up to 32 characters e A device group name must be unique within the storage system The device group name cannot be duplicated in one storage system e When a device group name is specified by the raidcom command option and an LDEV to operate is specified by the device name all devices that have the same name with the beginning of the specified name will be operated The contents of the following operations that can be executed for a device group are expressed hereafter with its use cases 1 Device group creation 2 LDEV addition to device group 3 LDEV deletion from device group 4 Device group deletion Note The following symbols are used in the use cases described hereafter g symplex volume G paired volume Device group creation Creating a device group by specifying a subject of multiple LDEV IDs
291. hCopy SE Get Command Status Async The specified LDEV is used as a TrueCopy pair a Universal Replicator pair or a command device defined by Business Continuity Manager Get Command Status Async The specified LDEV is used as a Universal Replicator pair or a journal Get Command Status Async The specified LDEV is used as a Compatible FlashCopy V2 relationship Get Command Status Async The specified LDEV is used as a Thin Image or Copy on Write Snapshot pair Get Command Status Async The specified LDEV is used as a Volume Migration Get Command Status Async The specified LDEV is used as a system disk Get Command Status Async The specified LDEV is used as a CC XRC attribute device Get Command Status Async The specified LDEV is used as the primary volume for the GAD pair Get Command Status Async The specified LDEV is used as the secondary volume for the GAD pair Get Command Status Async An LDEV that is in the state of formatting is included in the parity group of the target LDEV Get Command Status Async An LDEV that is in the state of executing quick format is included in the parity group of the target LDEV CMDRJE Executing The specified LDEV is used in another operation Get Command Status Async The parity group of the target LDEV is in the state of correction copy CMDRJE Executing
292. has the following control parameters HORCC_LOGSZ variable This variable is used to specify a maximum size in units of KB and normal logging for the current command HORCM log horcc_HOST log file is moved to HORCM log horcc_HOST oldlog file when reaching in the specified maximum size If this variable is not specified or specified as 0 it is same as the current logging for only command error This variable is able to define to the environment variable and or horcc_HOST conf as discussed below For example setting 2MB size HORCC_LOGSZ 2048 Export HORCC_LOGSZ HORCM log horcc_HOST conf file This 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_LOGSZ variable of this file is used If both variable is not specified then it is same as the current logging for only command error HORCC_LOGSZ variable This variable must be described as follows HORCC_LOGSZ 2048 The masking variable This variable is used to mask disable the logging by specifying a condition of the command and returned value except ingraid or EX_xxx error code This variable is valid for NORMAL exit If executing the pairvolchk command repeatedly at every interval 30 seconds logging of this command may not be wanted Therefore you can mask it by specifying HORCC_LOGSZ 0 as shown below and you may need to change your scripts if tracing is ON Exam
293. hat can be registered Get Command Async 2E00 0023 The specified volume capacity is too small Status CMDRJE Executing 2E00 8301 The specified MP Blade ID is invalid CMDRJE Executing 2E10 0000 The specified volume is already used by another Get Command Async program product Status CMDRJE Executing 2E10 0011 The specified volume is not installed or cannot be Get Command Async used Status Get Command Async 2E10 001A The specified volume is connected from the Status mainframe host 9 36 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add journal Error message CMDRJE Get Command Status Executing Async Executing Async Error code SSB1 SSB2 Description There is a PIN slot in the journal volume CMDRJE Get Command Status Executing Async The specified volume cannot be registered as a journal volume because it is in shredding Wait until the shredding operation is completed then retry the operation Get Command Status Async The specified volume is used in maintenance operation Get Command Status Async The specified volume cannot be used as the journal volume because the virtual LDEV ID is deleted Get Command Status Async The specified volume cannot be used as the journal volume because it is the virtual volume Get Command Status Async The specified operation failed because the journal or mirror is no
294. he TC_Sync group This means that CCI can support Universal Replicator MxN on the open system if CCI is capable of delivering the timestamps and committing the Journal data with a CTQ Marker Thus CCI supports UR MxN for open systems in the four ways described in Policy on page 6 44 All data consistency of the CT group across multiple storage systems is maintained by CCI The storage system supports only basic functions there is no relation between storage systems in order to simplify testing and configurations CCI supports Universal Replicator MxN in the following ways Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 1 Delivering the timestamp CTQ Marker CCI HORCM daemon process makes a table for the groups registered to the horcm conf as HORCM_CTQM with startup and makes the threads for each group that delivers the same timestamp with an increment to the multiple storage systems configured in a group The thread for a group delivers the same timestamp with increments as far as a group configured Universal Replicator in the PAIR status The timestamp is delivered by using Freeze Q Marker amp Run way as default The timestamp is maintained in each storage system CCI includes this timestamp with startup and then delivers the same timestamp with increments to each storage system 2 Arbitrating committing the journal data with CTQ Marker The thread for a group on HORCM c
295. he capacity of a pool VOL is nearly full UR status becomes PFUS and the pair is suspended R W enabled Read Only unless write option is enabled After Takeover SSWS is the status of the S VOL With this status data can be written to the S VOL e SSWS is displayed by CCI from which the horctakover command is issued e Storage Navigator displays this status as PSUS or PSUE R enabled Data replication operations with CCI R W enabled 6 21 Hitachi Command Control Interface User and Reference Guide Secondary Universal Replicator Pair Status If data in the journal volume exceeds 80 percent pair R W enabled R enabled status changes to PFUL The write data that inflows then is monitored during the Data Overflow Watch PFUL status is displayed by CCI Storage Navigator displays this status as PAIR Table 6 4 Pair status versus TrueCopy Universal Replicator commands TrueCopy Universal Replicator command paircreate pairsplit pairresync Status SMPL Copy Accepted 2 Nocopy Accepted 3 r OF rw option Rejected P option Rejected Acceptable S option Resync Rejected COPY Acceptable Acceptable Accepted 4 Rejected Accepted 1 Acceptable PAIR Acceptable Acceptable Accepted 4 Accepted 4 Accepted 1 Acceptable PSUS Rejected Rejected Acceptable Acceptable Accepted 1 Accepted
296. he command device cannot be set because LDEV is used as a Thin Image or Copy on Write Snapshot virtual volume CMDRJE Executing 2E30 000C The specified volume cannot be set because it is a quorum disk CMDRIJE Executing 2E30 000D The specified volume cannot be set because it is a system disk CMDRJE Executing 2E30 000E The specified volume cannot be set because it is a pool volume CMDRJE Executing 2E30 0012 The specified LDEV cannot be released because it is command device that is being used CMDRJE Executing 2E30 0013 The specified volume cannot be set because it is a LUSE volume CMDRJE Executing 2E30 0014 The command device cannot be set to the specified LDEV because of the following causes e Itis used as a Volume Migration e The reserve attribute of a Volume Migration is configured CMDRJE Executing 2E30 0016 The specified LDEV cannot be set because it has a reserve attribute of a Data Retention Utility CMDRJE Executing 2E30 0019 The specified volume cannot be used as a command device because it is set by a Data Retention Utility CMDRJE Executing 2E30 0074 The specified LDEV cannot be operated because it is an external volume mapped for online data migration Troubleshooting 9 45 Hitachi Command Control Interface User and Reference Guide raidcom modify Idev command_device Error message CMDRJE Executing Async Executing Error code Description
297. he command ends abnormally because the Volume Migration target volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the P VOL of a ShadowImage pair is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the S VOL of a ShadowImage pair is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the ShadowImage reserved volume is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing 9 62 The command ends abnormally because the Volume Migration source volume is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add snapshot Error message Executing Async Executing Error code SSB1 SSB2 Description The command ends abnormally because the Volume Migration target volume is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration reserved volume is specified as the S VOL of a Thin Image or Copy on Write
298. he disk on cannot be opened in the HORCM directory which the root directory resides 9 6 Troubleshooting Hitachi Command Control Interface User and Reference Guide Message ID HORCM_003 Condition The HORCM daemon process cannot create a child process due to an error HORCM daemon attempted to create more processes than the maximum allowable number Recommended action Terminate unnecessary programs or daemon processes running simultaneously HORCM_004 HORCM assertion failed resulting in a fatal internal error in the HORCM An internal error that could not be identified by the HORCM occurred Restart the system and contact the Hitachi Data Systems Support Center HORCM_005 The CCI software failed to create the end point for remote communication HORCM failed to create a socket or an error exists in the format or a parameter in the HORCM configuration file HORCM_CONF Refer to the HORCM startup log to identify the cause of the error HORCM_006 HORCM memory allocation failed HORCM memory could not be secured Increase the system virtual memory or close any unnecessary programs HORCM_007 An error exists in the parameter value in the HORCM setup file An error exists in the parameter value setting in the HORCM setup file Refer to the startup log and reset the parameters HORCM_008 HORCM configuration file parameters reading fails
299. he item to be operated as a pair If a consistency group attribute is valid and no consistency group ID is specified automatically assign a consistency group ID 1 copy group 1 consistency group If the automatic consistency group assignment is specified and the other pairs in a copy group already have consistency group IDs assign the same consistency group ID If there is no target LDEV to be a pair in the copy group the process is terminated by detecting an error e Use cases As an example of pair operation the following shows use cases that can be created a pair by specifying a copy group o Creating a pair in cases where the device names and the numbers of LDEVs in two device 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 o Creating a pair in cases where the device names and the numbers of LDEVs in two device groups in a copy group configured of simplex volumes and paired volumes are the same In the following example a pair is created with LDEVs for the device name A And no operation is performed for the volumes of device name B that are already formed into copy pairs CCI functions 3 39 Hitachi Command Control Interface User and Reference Guide o Creating a pair in cases where different device names exist in two device groups in a copy group configured of simplex volumes In the
300. he specified volume is a reserved volume of a mainframe host CMDRJE Get Command Status Executing Async The specified volume is used by the XRC CMDRJE Get Command Status Executing Async The specified volume is a volume of Just in Time On demand function Get Command Status Async The specified volume cannot be used as a journal volume because it is used by Compatible PAV CMDRJE Get Command Status Executing Async The resource group ID of the specified volume cannot be registered because the resource group ID is different from the resource group ID of the other journal volume in the specified journal group CMDRJE Get Command Status Executing Async The specified LDEV cannot be operated because it is an external volume mapped for online data migration Get Command Status Async The specified LDEV cannot be used as a journal volume because the size of the LDEV is less than the minimum capacity of journal volume CMDRJE Get Command Status Executing Async The operation cannot be performed because the specified volume is not the Dynamic Provisioning V VOL CMDRJE Executing The command cannot be accepted After a while execute the same command CMDRJE Get Command Status Executing Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Get Command Status Executing Async An internal erro
301. he threshold value is less than the Status pool usage value CMDRJE Executing 2E10 600D The operation cannot be done because it is in the state of shrinking CMDRJE Executing 2E10 6011 The operation cannot be done because it is being discarded pages Get Command Async 2E10 6012 Pool cannot be restored because the usage rate of Status pool is 100 CMDRJE Executing 2E10 6015 The operation cannot be done because the Tier is being deterred reallocation CMDRJE Executing 2E10 6017 The operation cannot be done because collecting the performance monitoring data is being prepared CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Executing 2E13 6000 The Dynamic Tiering operations cannot be done to the pool because the specified pool contains RAID 1 pool VOLs CMDRJE Executing 2E13 6002 The specified pool for Dynamic Provisioning cannot be changed to a pool for Dynamic Tiering because the pool is related to TSE VOL CMDRJE Executing 2E20 6000 Pool ID is not installed CMDRJE Executing 2E20 6101 The specified Tier number is invalid CMDRJE Executing 2E21 8101 SM for Dynamic Provisioning is not installed CMDRJE Executing 2E21 8102 SM for Dynamic Tiering is not installed CMDRJE Executing 2E30 006E The Dynamic Tiering operation cannot be done to the pool because the specified pool contains the external volumes whose cache mode is invalid CMDRJE Executing 2E30 6000 The threshold value 1
302. hether this command is executed or not depends on the microcode version of the RAID storage system A Note pairsplit simplex S of Copy on Write 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 W disable and data is discarded e Inthe PSUE state Copy on Write Snapshot does not manage for differential data between the primary volume and secondary volume TrueCopy Async TrueCopy and Universal Replicator volumes TrueCopy Async Universal Replicator provides paired volumes that use asynchronous transfer to ensure the sequence of writing data between the primary volume and secondary volume The sequence of writing data between the primary and secondary volumes is guaranteed within each consistency CT group see Figure 6 9 TrueCopy Async consistency groups on page 6 26 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide 6 25 6 26 HA Software Package Write 1 Write 2 Write 4 Write 3 Note Write shows that synchronous writing or Write 5 commit of DB is used Asynchronous transfer Secondary volume Primary volume Primary BITMAP _ BITMAP Secondary volume CT group volume RAID Storage System RAID Storage System Resynchronization Figure 6 9 TrueCopy Async consistency groups Restrictions Group definition of TrueCopy Async Unive
303. hi Command Control Interface User and Reference Guide Parameter Default dev_group None Character string 31 characters Recommended value 8 char or less port None Character string 31 characters target ID None Numeric value 7 characters LU None Numeric value 7 characters MU 0 Numeric value 7 characters Serial 2 None Numeric value 12 characters CU LDEV LDEV None Numeric value 6 characters dev_name for None Character string 63 characters HORCM_CMD Recommended value 8 char or less Notes 1 Use decimal notation for numeric values not hexadecimal 2 For VSP Gi000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 Do not edit the configuration definition file while CCI is running Shut down CCI edit the configuration file as needed and then restart CCI Do not mix pairs created with the At Time Split option m grp and pairs created without this option in the same group defined in the CCI configuration file If you do a pairsplit operation might end abnormally or S VOLs of the P VOLs in the same consistency group CTG might not be created correctly at the time the pairsplit request is received Configuration definition file settings 1 HORCM_MON The monitor parameter HORCM_MON defines the following values e Ip_address The IP address of the local host When HORCM has two or more network addresses on different s
304. hold is set for the prioritized WWN Only one threshold can be set for the entire storage system The threshold cannot be set for each prioritized WWN When the traffic of the high priority server declines to the threshold the control with the upper limit becomes invalid automatically By adjusting the upper limit or the threshold to the appropriate value the frequency of the access to the storage system or the data traffic becomes stabilized in a high level in the high priority server The following shows examples of the priority settings Set the host bus adapter WWN 210000e0 8b0256f8 to the non prioritized WWN and set 5000 IOPS as the upper limit raidcom modify spm_wwn port CL4 E spm_priority n limit_io 5000 hba_wwn 210000e0 8b0256f8 Set the host bus adapter WWN 210000e0 8b039c15 to the prioritized WWN and set 3000 IOPS as the threshold raidcom modify spm_wwn port CL4 E spm_priority y limit_io 3000 hba_wwn 210000e0 8b039c15 limit_io 3000 shown in the example of the priority setting is the threshold value of the entire system Provisioning operations with CCI 5 49 Hitachi Command Control Interface User and Reference Guide Checking the status of the prioritized WWN and the non prioritized WWN settings Display the status of the prioritized WWN and the non prioritized WWN settings and check it Display examples of the status of the prioritized WWN and the non prioritized WWN settings Display the
305. horcm conf User environment variable When HORCM or command is invoked environment variable can be specified 2 44 CCI software environment Hitachi Command Control Interface User and Reference Guide CCI functions This chapter describes the CCI functions C Command execution using in band and out of band methods Connecting to CCI server already connected by In Band method using Out of Band method User authentication Command operation authority and user authentication Relation between resource groups and command operations Resource lock function Command execution modes Resource location and parameter LDEV grouping function Pair operations with mainframe volumes Global virtualization function VSP G1000 only CCI functions Hitachi Command Control Interface User and Reference Guide Command execution using in band and out of band methods The methods of executing commands provided by CCI can be classified into the in band and out of band methods e In band method This method transfers a command from the client or the server to the command device of the storage system via fibre and executes a CCI operation instruction e Out of band method This method transfers a command from the client or the server to the virtual command device in the SVP via LAN assigning a CCI operation instruction to the storage system and executes it If many commands are issued in a short period of time for exampl
306. hority managed by Storage Navigator and the SVP Controlling User Role 3 6 CCI verifies whether or not the user executing the command on the host was already authenticated by checking the command device being in the authentication mode After that CCI obtains the execution authority of the command that is configured on the user role and then compares the relevant command and the execution authority CCI functions Hitachi Command Control Interface User and Reference Guide Checking the execution authority If the configuring commands authenticated are compared with the execution authorities of commands configured on the user role and they do not correspond CCI rejects the command with an error code EX_EPPERM Normally the user role needs to be the consistent and integrated authority among the large storage systems In case of HORCM instances that are configured by the multiple large storage systems the execution authorities are obtained by the serial number of the storage systems If the user role is for the multiple storage systems and is not consistent among these storage systems CCI makes the integrated authority by performing the logical AND of the execution authorities among the storage systems The target commands CCI checks execution authorities on the following commands that use command devices e horctakeover horctakeoff e paircreate pairsplit pairresync e raidvchkset Controlling user resources CCI verifi
307. hysicalDrive find inst Note This registration process has risk because it is executed automatically by etc horcmgr without judgment for protection mode in order to validate the fd option This registration brings a degradation in horcmstart sh but HORCM daemon has been running as usual and it will depend on how many devices a host has To start faster at HORCM faster in non protection mode create the HORCMPERM file of SIZE 0 byte as a dummy file or to set HORCMPERM MGRNOINST At this time the fd option shows Device_File name as Unknown and after you can use raidscan find inst to validate the fd option Data protection operations with CCI 7 13 Hitachi Command Control Interface User and Reference Guide Environment variables HORCMPROMOD This environment variable turns protection mode ON as specified in the following table If your command device is set for non protection mode this parameter sets it to protection mode Table 7 4 Relation between HORCMPROMOD and command device Command Device HORCMPROMOD Protection mode Don t care Protection mode Non protection mode Not specified Non protection mode Specified Protection mode HORCMPERM This variable is used to specify the HORCM permission file name If no file name is specified etc horcmperm conf or etc horcmperm conf instance number is the default e If aHORCM permission file exists then etc horcmgr executes the followi
308. i Command Control Interface User and Reference Guide 6 47 6 48 e Searches commits a minimum matching point of the CTQ Marker on RCU via MCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on MCU on all RCU via MCU e Issues End of Suspend to terminate a suspending state after committed with EOM End Of Marker 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 a suspending state terminates without waiting for the EOM End Of Marker 2 pairsplit P option e Issues Freeze to CT group on each MCU e Issues Suspend amp Run to make a suspending state for CT group on each MCU e Searches commits a minimum matching point of the CTQ Marker on RCU via MCU in other words do Journal Restore with CTQ Marker e Repeats above until detecting an EOM End Of Marker marked on MCU on all RCU via MCU e Issues End of Suspend to terminate a suspending state Exception If an uncommitted state that is link failure is detected while executing its operation then the operation of committing is aborted on keeping current CTQ Marker level and a suspending state terminates without waiting for the EOM End Of Marker 3 pairsplit S option e Issues Freeze to CT group on each MCU e Issues Delete amp Run to make
309. icate over the LAN SSWS Since the SSWS state is referring to a Suspend for Swapping with S VOL Side only the SSWS state is displayed as SSUS SVOL_PSUS by all commands except the fc option of the pairdisplay command Swap takeover function The P VOL status at the remote node is PAIR or PFUL TrueCopy Async and over HWM and the S VOL has mirroring consistency In such a state it is possible to swap the primary and secondary volume designations to continue operation The takeover command internally executes the operating commands explained later step by step to swap the primary and secondary volume designations Swapping can be specified at the granularity of volume pair CT group or volume group The swap takeover function does not use Simplex and No Copy mode for Swapping in order to guarantee mirror consistence more surely and it is included as a function of SVOL takeover 1 As the preliminary step of swap takeover the command orders a Suspend for Swapping SSWS for the local volume S VOL If this step fails the swap takeover function is disabled and it will be returned at an error 2 The command orders a Resync for Swapping for switch to the primary volume that the local volume S VOL is swapped as the NEW_PVOL and re synchronizes the NEW_SVOL based on the NEW_PVOL As for the number of simultaneous copy tracks if the remote host is known then the command will use the value of P VOL specified at paircreate time else
310. ice 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 not ready at the boot time since the Cluster Disk Driver is a Non Plug and Play Driver Verify this situation using the ingraid command as follows ingraid Phy CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT _ID HarddiskO m Harddisk1 io In this case do the following to disable the Cluster Disk Driver 1 In the Computer Management window double click System Tools and then click Device Manager 2 On the View menu click Show Hidden Devices Non Plug and Play Drivers appear in the list in the right pane 3 Open Non Plug and Play Drivers right click Cluster Disk and then click Disable When prompted to confirm whether to disable the cluster disk click Yes When prompted to restart the computer click Yes 4 Verify that you can see the Noread volume using ingraid command as follows Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide ingraid Phy CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID HarddiskoO CL2 K 61456 194 s S ss 0004 1 01 10 OPEN 3 Harddiskl CL2 K 61456 256 s S ss 0005 1 01 11 OPEN 3 After starting up CCI and splitting the S VOL put back the signature by using the ingraid svinf command Again in the Computer Management w
311. ice file provided via STDIN or arguments This option gets the serial and LDEV of the RAID storage system for the target device using SCSI Inquiry and writes the signature GUID DiskId and volume layout information from the VOLssss_IIll ini file to the target device Examples of using CCI commands 8 11 Hitachi Command Control Interface User and Reference Guide 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 array serial and LDEV not Harddisk e PTN This option specifies a string pattern usable to select only the pertinent output lines being provide from STDIN If used as shown only the pairdisplay output lines containing Harddisk would be used to cause signature writing D HORCM etc gt pairdisplay l fd g URA inqraid svinfex Harddisk VOL61459 448 DA7COD91 gt Harddisk10 OPEN V VOL61459 449 D4CB5F17 2ADC 4FEE 8650 D3628379E8F5 gt Harddisk1l1 OPEN V VOL61459 450 9ABDCB73 3BA1 4048 9EF94 22E3798C3B61 gt Harddisk12 OPEN V e gplbaex option Windows 2012 2008 Only This option is used for displaying usable LBA on a Physical drive in units of 512 bytes and is used to specify slba elba options for raidvchkset command C HORCM Tool gt ingraid CLI gplbaex hd10 13 Harddisk10 SLBA 0x0000003f ELBA 0x013fe5d9 PCNT 1 OPEN V Harddisk11 SLBA 0x00000022
312. idcom modify spm_wwn command raidcom modify spm_wwn Error message Executing Async Executing Error code SSB1 SSB2 Description Server Priority Manager is being used by Device Manager Storage Navigator Executing The number of WWNs exceeds the maximum that can be set in the system Executing Server Priority Manager program product is not installed Executing The number of WWNs exceeds the maximum that can be set to the port Calling the HDS Support Center If you need to contact the Hitachi Data Systems Support Center please provide as much information about the problem as possible including The circumstances surrounding the error or failure The exact content of any error messages displayed on the host systems The exact content of any error messages displayed by Storage Navigator The Storage Navigator configuration information use the Dump Tool The data in the CCI error log file and trace data all files in the HORCM_LOG directory The service information messages SIMs including reference codes and severity levels displayed by Storage Navigator The HDS customer support staff is available 24 hours a day seven days a week If you need technical support log on to the HDS Portal for contact information https portal hds com Troubleshooting 9 103 Hitachi Command Control Interface User and Reference Guide 9 104 Troubleshooting Hitachi Command
313. ied by dev rhdisk dev rhdisk A device file is displayed while HINT is filtered with the following pattern HP UX dev rdsk or dev rdisk disk Solaris dev rdsk s2 AIX dev rhdisk Linux dev sd zLinux dev sd Tru64 dev rrz c or dev rdisk dsk c or dev cport scp IRIX64 dev rdsk vol or dev rdsk node_wwn vol If HINT is already specified HINT can be omitted with the following command devices and the command devices are retrieved from the already stored Inquiry information which is not required to execute device scanning HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 dev rdsk CMD 30095 250 CL2 e Basic Specification Specifies when an optional command device of Serial 30095 is used CMD 30095 dev rdsk CCI software environment 2 19 Hitachi Command Control Interface User and Reference Guide 2 20 e Driver in the multi path environment Specifies when an optional port is used as a command device for Serial 30095 LDEV 250 CMD 30095 250 dev rdsk e For full specification Specifies a command device for Serial 30095 LDEV 250 which is connected to Port CL1 A Host group 1 e Other example CMD 30095 250 CL1 dev rdsk CMD 30095 250 CL2 CMD 30095 dev rdsk c1 CMD 30095 dev rdsk c2 3 HORCM_DEV The device parameter HORCM_DEV defines the RAID storage system device addresses for the paired logical volume names When the server is conne
314. in raidcfg raidcfg Text filtering HORCM usr bin rmawk rmawk DB Validator setting usr bin raidvchkset raidvchkset DB Validator confirmation usr bin raidvchkdsp raidvchkdsp DB Validator confirmation 2 32 usr bin raidvchkscan raidvchkscan CCI software environment Hitachi Command Control Interface User and Reference Guide File name Command name Storage HORCM usr bin rmsra Replication Adapter Configuration setting command A file for HORCM etc management Raidcom_Dic_Raid_RM_Patch txt A file for HORCM etc management Raidcom_Help_Raid_RM txt A file for HORCM etc management Raidcom_Dic_Raid_RM txt HORCM usr bin raidcom raidcom For information and instructions on changing the UNIX user for the CCI software please see the Command Control Interface Installation and Configuration Guide CCI files for Windows based systems HORCM File name HORCM etc horcmgr exe Command name horcmd HORCM_CONF HORCM etc horcm conf Takeover HORCM etc horctakeover exe horctakeover Accessibility check HORCM etc paircurchk exe paircurchk Pair generation HORCM etc paircreate exe paircreate Pair split HORCM etc pairsplit exe pairsplit Pair re synchronization HORCM etc pairresync exe pairresync Event waiting HORCM etc pairevtwait exe pairevtwait Error no
315. indow enable the Cluster Disk Driver and restart the computer GPT disk for Windows Windows supports the basic disk called GPT disk using GUID partition instead of the Signature The GPT disk also can be used as an S VOL of the BC Therefore CCI supports saving restoring the GUID DiskId of the GPT Basic disk to the ingraid command gvinfex option Windows 2012 only This option retrieves the LUN signature and volume layout information by way of a raw device file provided via STDIN or arguments and saves it in a system disk file with the following format WindowsDirectory VOLssss 1111l ini where ssss serial 1111 LDEV Normally this option is used to save the Disk signature GUID DiskId and volume layout information once after it has been written on a potential and before its paircreate You do not need to directly view these host files For example saves the volume information for all physical drives D HORCM etc gt ingraid Phys gvinfex CLI PhysicalDrivelo Harddisk10 gt VOL61459 448 DA7COD91 OPEN V PhysicalDrivell Harddisk11 gt VOL61459 449 D4CB5F17 2ADC 4FEE 8650 D3628379E8F5 OPEN V PhysicalDrivel2 Harddisk12 gt VOL61459 450 9ABDCB73 3BA1 4048 9E94 22E3798C3B61 OPEN V svinfex PTN option Windows 2003 only This option writes LUN signature GUID DiskId and volume layout information that had previously been saved in a system disk file by way of a raw dev
316. ing Port Port attribute setting authority raidcom modify port port_attribute Storage Administrator System Resource Management Port setting authority raidcom modify port loop_id raidcom modify port topology raidcom modify port port_speed Storage Administrator Provisioning Host group Host group setting authority raidcom add host_grp Storage Administrator Provisioning WWN WWYN setting authority raidcom set hba_wwn raidcom reset hba_wwn Storage Administrator Provisioning LDEV nickname LDEV nickname setting authority raidcom modify Idev Idev_name Storage Administrator Provisioning Local copy Pairsplit and resync authority pairresync Storage Administrator Local Copy Remote copy Environment construction authority raidcom add rcu raidcom delete rcu raidcom modify rcu raidcom add rcu_path raidcom delete rcu_path raidcom add journal raidcom delete journal raidcom modify journal Storage Administrator Remote Copy Pairsplit and resync authority pairresync Storage Administrator Remote Copy Relation between resource groups and command operations The operation for using resource groups are different by the command devices the In Band method or the Out of Band method that are used when you start CCI You can create resource groups for each resource And you can share them with multiple users
317. ing Async Async Error code SSB1 SSB2 Description The specified LDEV cannot be operated because it is an external volume mapped for online data migration Get Command Status Async The specified volume is used as a TrueCopy Get Command Status Async The specified volume is used as a TrueCopy Get Command Status Async The specified volume is used as a ShadowImage Get Command Status Async The specified volume is used as a ShadowImage Get Command Status Async The specified volume is used as a ShadowImage Get Command Status Async The specified LDEV is used as a reserved volume of Volume Migration Get Command Status Async The target LDEV is a quorum disk and cannot be deleted CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async An internal error occurred CMDRJE Get Command Status Executing Async An internal error occurred Call Hitachi Data Systems Support Center Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center Table 9 51 SSB codes that are returned by raidcom delete hba_wwn command raidcom delete hba_wwn Error message Executing Async Executing Error code SSB1 SSB2 Description The program product is not installed Executing The host g
318. ing Hitachi Command Control Interface User and Reference Guide raidcom delete snapshot Error message Executing Error code Description Async Executing SSB1 SSB2 An error occurred at the operation of Thin Image due to one of the following reasons e The LDEV number specified for the P VOL or the S VOL is incorrect 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 to 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 e The license capacity has exceeded the maximum e The control table for Thin Image is depleted Executing The operation cannot be performed because power off is in progress Executing The specified LDEV is not defined Executing The command ends abnormally because an unmounted volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the blocked volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the shared memory FC TPF or Extension2 is not expanded for necessary capacity Executing The command ends abnormally because the shared memory SS2 or more is not expanded for necessary capacity
319. inted with permission from Microsoft Corporation Hitachi Command Control Interface User and Reference Guide Contents PRI 66 5606 65562466 5 bo 94 OS O4EE ES OG ES EGE REG CEES xi Intended audience 1 ce ees xii PROGUCE VISION 22 4 oie 2s teens Gees eG ere ead Ssee ies ouaeseesee ee xii Document revision level 0 0 0 cee ees xii Changes in this revision n s Ch e4ese bee cettcdawbedewd woh edae ees xiii Referenced documents sasaaa ccc eee ees xiii Document CONVENNIGNS 5050cedecernantedexsed oe xawwd es eee dee aed XV Convention for storage capacity values 0 ce eee xvi Accessing product documentation 0000 e ees xvi Getting help 2ns205 2 6902 sbe 5259482558509 5505 588544502 5508 1 25 xvi Comments 266 a8t56 nto le wtease duees swe use Seaoneas one e eases xvii D e AE E E ae ee ae ee EE ee ay E eH eR we Oo 1 1 About Command Control Interface s a 2 0 cc ees 1 2 CCITUNCIONS sses ser neu woes BGR 4 69 S68 oe Oe bee wes dda eee es 1 2 CCI functions matrix 6 waa vee la tetasee te yheadedsebyedews ode ees 1 2 Provisioning function 2 2 4 22256 se ee see ba eee ewe eee ee eee ee ee 1 3 Asynchronous command processing 00 cece eee eee nes 1 3 Command execution modes 1 cc es 1 4 Precheck function asana ees 1 4 Command execution by the out of band method 000005 1 5 User authentication sc e s arses ese aS adee eo ac eh ee ee WS tee a ee eS 1 7 LDEV nickname func
320. interfaces such as Storage Navigator and host servers do not display the dummy LUs Two dummy LUs are assigned to each mainframe LDEV The port IDs of the mainframe PCBs are assigned as the port IDs for the dummy LUs Host modes cannot be defined for dummy LUs pairdisplay g oradb Group Pair Vol L R Port TID LU M Seqg LDEV P S Status Fence Seqit P LDEVi M oradb oradb1 L CL1 A 1 0 30053 18 P VOL PAIR Never 30053 19 oradb oradb1 R i 30053 19 S VOL PAIR Never 30053 18 information on dummy LUs To determine the port number for dummy LUs use the following formula Port Installed Port 1 LDEV 0x4000 x32 Installed Port 1 LDEV 0x4000 x32 1 1 The lowest port number of the installed mainframe ports TID LDEV amp O3xFCO 64 LU M LDEV amp 0x3F To perform pair operations on mainframe volumes just like on open system volumes include the mainframe LDEV in the HORCM_LDEV section of the configuration definition file If you have mainframe pairs that already exist you can verify their MU using the raidscan command HORCM_LDEV tdev_group dev name Serial CU LDEV LDEV MU oradb devi 30095 0 oradb dev2 30095 0 Define mainframe LDEV Pair status and access permission for mainframe LDEVs The pair status of mainframe LDEVs is displayed in the same way as for open system LDEVs However access permissions to mainframe P VOLs and S VOLs are different from those of open vol
321. ion Facility has two specifications Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide one must be a volume that you can see from the host such as the Inquiry tool and the other must be a mirror descriptor volume that was registered in horem conf The following table shows the registration for the mirror descriptor Table 7 2 Registration for the mirror descriptor Mirror Descriptor in horcm conf ShadowImage TrueCopy MU 1 none none Unknown dev permitted permitted permitted permitted rdsk volumes volumes volumes volumes cOtOdo 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 e CCI permits operation after the permission command at startup of HORCM The target is volume that was registered in the horcm conf file e The permission command is necessary to permit the protected volume at first The permission command compares an identification for volumes of horcm conf to all of own host volumes and the result is registered within HORCM And HORCM makes tables for protected volume and permitted volumes from horcm conf and Inquiry result Inquiry result is based on configuration of Data Retention Utility When controlling pair volumes requests to protected volumes
322. ion for each group see the following figure Facility version N for group A on Conf file Facility version N Facility version N 1 for group B on Conf file for group C on Conf file 9900V facility version N USP NSC facility version N 1 Mixed storage system configuration Figure 8 1 Definition of the group version LDM volume discovery and flushing for Windows Windows systems support the Logical Disk Manager LDM such as VxVM and a logical drive letter is typically associated with an LDM volume Device HarddiskVolumexX Therefore you cannot know the relationship between LDM volumes and the physical volumes of the RAID storage system Therefore you need to create the CCI configuration file and you need to know the relationship that is illustrated in Figure 8 2 LDM volume configuration on page 8 3 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide Mounted point Drive Letter _auvfrnoncncnceneusnceenenensansineteusnasnsneis Volume guid _praseseeanessnsecssssasscsnssnsensasessnnes Volume quid P os Volume guid pi a eae Devici onmes t HarddiskVolumeX HarddiskVolumeY _ Stripex PhysicalDrive Y 1 i I Physical Mirrored Volume ORB ORA Group in configuration file Figure 8 2 LDM volume configuration Volume discovery function CCI supports the volume discovery function on three levels showing the relationship between LDM volumes and the physi
323. is not coincident 9 32 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add Idev Error message Error code Executing Async sspi ssB2 Description CMDRJE Executing 2E10 6014 The specified pool be associated with the virtual Get Command Async volume of Dynamic Provisioning because the Status state of the pool is incorrect Get Command Async 2E11 0003 An LDEV that is in the state of shredding is Status included in the parity group of the target LDEV Get Command Async 2E11 0004 An LDEV that is in the state of formatting is Status included in the parity group of the target LDEV Get Command Async 2E11 0005 An LDEV that is in the state of executing quick Status format is included in the parity group of the target LDEV CMDRJE Executing 2E11 0053 The specified LDEV is used in another operation Get Command Async 2E11 0102 The parity group of the target LDEV is in the state Status of correction copy CMDRJE Executing 2E11 0153 The parity group or the external volume group that the specified LDEV is belongs to is used in another operation Get Command Status Async 2E11 8004 The operation cannot be done because the internal processing is in progress CMDRJE Executing 2E11 8010 The storage system is in internal process or the configuration changing processes are conflicting Get Command Async 2E11 8105 Cache segment size is incorrect
324. ithout a HORCMPERM file Commands to run on different operating systems on page 7 13 Updated the tables of CCI error messages Error messages and error codes on page 9 6 Referenced documents Hitachi Command Control Interface documents Command Control Interface Installation and Configuration Guide MK 90RD7008 Command Control Interface User and Reference Guide MK 90RD7010 Hitachi Virtual Storage Platform G1000 documents Hitachi Virtual Storage Platform G1000 Product Overview MK 92RD8051 Hitachi Command Suite User Guide MK 90HC172 Hitachi Command Suite Messages MK 90HC178 Hitachi Virtual Storage Platform G1000 Mainframe System Administrator Guide MK 92RD8016 Hitachi Thin Image User Guide MK 92RD8011 Hitachi Virtual Storage Platform G1000 Provisioning Guide for Open Systems MK 92RD8014 Hitachi TrueCopy User Guide MK 92RD8019 Hitachi ShadowImage User Guide MK 92RD8021 Hitachi Universal Replicator User Guide MK 92RD8023 Hitachi Universal Volume Manager User Guide MK 92RD8024 Preface xiii Hitachi Command Control Interface User and Reference Guide xiv Global Active Device User Guide MK 92RD8072 Hitachi Unified Storage VM documents Hitachi Unified Storage VM Block Module Provisioning Guide MK 92HM7012 Hitachi ShadowImage User Guide MK 92HM7013 Hitachi Storage Navigator User Guide MK 92HM7016 Hitachi Storage Navigator Messages MK 92HM7017 Hitachi TrueCopy U
325. k CMDRJE Executing LDEV is not blocked Get Command Status Async The specified LDEV is a CC XRC attribute device Get Command Status Async The specified LDEV is not formatted after it is used as the journal volume Get Command Status 9 46 Async The operation cannot be done because LDEV is not expanding Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify Idev status nmi Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The operation cannot be done because the virtual disk space is blocked Get Command Status Async The specified LDEV is used as the primary volume of a GAD pair Get Command Status Async The specified LDEV is used as the secondary volume of a GAD pair CMDRJE Executing The specified LDEV is used in another operation CMDRJE Executing The parity group or the external group to which the specified LDEV belongs is used in another operation Get Command Status Async The operation of Dynamic Provisioning V VOL cannot be done because there is a blocked pool volume Get Command Status Async The operation cannot be done because the internal processing is in progress CMDRJE Executing The command cannot be accepted After a while execute the same command CMDRJE Executing
326. k Status Get Command Async 2E30 4101 The external volume is used as LUSE Status Get Command Async 2E30 4102 The external volume is used as a TrueCopy pair Status volume Get Command Async 2E30 4103 The external volume is used as a TrueCopy pair Status volume Get Command Async 2E30 4104 The external volume is used as a ShadowImage Status pair volume Get Command Async 2E30 4105 The external volume is used as a ShadowImage Status pair volume Get Command Async 2E30 4106 There is the volume that has path definition Status Get Command Async 2E30 4107 The external volume is used as a ShadowImage Status reserved VOL Get Command Async 2E30 4108 The external volume is used as a Volume Status Migration reserved VOL 9 24 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom delete external_grp Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description There is a mainframe path group setting in the external volume Get Command Status Async There is a Data Retention Utility setting in the external volume Get Command Status Async There is a mainframe LDEV Guard setting in the external volume Get Command Status Async There is a Volume Security setting in the external volume Get Command Status Async The external volume is used as a Universal Replicator pair volume Get Command Status
327. l none done EVICE UnitID datal done EVICE UnitID datal done EVICE datal UnitID done Internal volume operations Creating internal volumes open systems LDEV LDEV LDEV 512 0x0200 1 513 0x0201 1 PORT 514 0x0202 1 PORT LDEV 515 0x0203 1 PORT To create LDEVs of internal open systems volumes and make the LDEVs available to the host perform the following provisioning operations Operation Setting port Description Enable LUN security of the port Modify settings such as port topology and data transfer speed as needed Command raidcom modify port port lt port gt security switch y Creating host group Specify port and create host group Provisioning operations with CCI raidcom add host_grp port lt port gt host_grp_ name lt host group name gt 5 19 Hitachi Command Control Interface User and Reference Guide Operation Setting host mode Description Specify port and set host mode for host group Command raidcom modify host_grp port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt Displaying host group information Display host group information and confirm result of executing command raidcom get host_grp port lt port gt lt host group name gt Adding host to host group Register h
328. l volume can be added Get Command Status Async The operation cannot be done because the power supply is switched off CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async The specified LDEV is not installed Get Command Status Async The operation cannot be performed because the memory capacity of the shared memory SM is insufficient Get Command Status Async The operation cannot be performed because the shared memory SM is not initialized CMDRJE Executing Dynamic Provisioning program product is not installed Get Command Status Async Troubleshooting Exceeded the number of pool volume that can be registered in a pool 9 75 Hitachi Command Control Interface User and Reference Guide raidcom add dp_pool Error message Get Command Status Executing Async Error code SSB1 SSB2 Description The larger number of drive types than the supported configuration cannot be added to the specified pool Get Command Status Pool volume cannot be registered because the drive type of specified LDEV is different from the other pool volume type or the drive type in the pool exceeds three CMDRJE Executing The number of specified LDEVs is invalid Get Command Status Async The emulation type of specified LDEV cannot be used as a pool VOL
329. l Volume Manager User Guide MK 96RD626 Preface Hitachi Command Control Interface User and Reference Guide Document conventions This document uses the following terminology conventions Convention Description Hitachi RAID storage system Refers to all supported models unless otherwise noted The Hitachi RAID storage systems include the following models Hitachi Virtual Storage Platform G1000 Hitachi Unified Storage VM Hitachi Virtual Storage Platform Hitachi Universal Storage Platform V VM Hitachi TagmaStore Universal Storage Platform Hitachi TagmaStore Network Storage Controller Hitachi enterprise storage system This document uses Convention Regular text bold Refers to the Hitachi RAID storage systems except for the Hitachi Unified Storage VM the following typographic conventions Description In text keyboard key parameter name property name hardware label hardware button hardware switch In a procedure user interface item Italic Variable emphasis reference to document title called out term Screen text Command name and option drive name file name folder name directory name code file content system and application output user input lt gt angle brackets Variable used when italic is not enough to identify variable Square brackets Optional value braces Required or expected value vertical bar This
330. l volume belongs to a Thin Image or Copy on Write Snapshot where the pair in the PSUS status exists Executing The operation cannot be done because the internal processing is in progress Wait for a while then retry the operation CMDRJE Executing There is no specified external volume CMDRJE Executing There is no specified path CMDRJE Executing It is included the Hitachi Dynamic Provisioning volume that is associated with a pool Get Command Status Async The specified LDEV is used as a quorum disk CMDRJE Executing It is used as a pool volume CMDRJE Executing It is used as a journal volume CMDRJE Executing It is used as a reserved volume of Volume Migration CMDRJE Executing Volume Security is set CMDRJE Executing It is used as a remote command device CMDRJE Executing Online from the mainframe host CMDRJE Executing This is a volume that the Data Retention Utility is set CMDRJE Executing Troubleshooting The Dynamic Provisioning volume not in the blocked state is included in the Dynamic Provisioning that is associated with the pool to which the pool volume is belongs 9 27 Hitachi Command Control Interface User and Reference Guide raidcom disconnect external_grp Error code Executing Async sspi ssB2 Error message Description Executing An internal error occur
331. laces MK 90RD7010 06 MK 90RD7010 08 September 2012 Supersedes and replaces MK 90RD7010 07 MK 90RD7010 09 November 2012 Supersedes and replaces MK 90RD7010 08 MK 90RD7010 10 December 2012 Supersedes and replaces MK 90RD7010 09 MK 90RD7010 11 January 2013 Supersedes and replaces MK 90RD7010 10 MK 90RD7010 12 February 2013 Supersedes and replaces MK 90RD7010 11 MK 90RD7010 13 March 2013 Preface Supersedes and replaces MK 90RD7010 12 Hitachi Command Control Interface User and Reference Guide Revision Description MK 90RD7010 14 July 2013 Supersedes and replaces MK 90RD7010 13 MK 90RD7010 15 October 2013 Supersedes and replaces MK 90RD7010 14 MK 90RD7010 16 December 2013 Supersedes and replaces MK 90RD7010 15 MK 90RD7010 17 April 2014 Supersedes and replaces MK 90RD7010 16 MK 90RD7010 18 August 2014 Supersedes and replaces MK 90RD7010 17 Changes in this revision Added support for global active device operations Remote replication on page 1 8 Using CCI with global active device on page 6 5 Added a note about slow command response during out of band operations Command execution using in band and out of band methods on page 3 2 Added information about HORCM Tool TRCLOG bat and HORCM etc rmsra exe CCI files for Windows based systems on page 2 33 Updated the command to run on HP UX when no HORCMPERM file exists Table 7 3 W
332. licator pair volume Executing The external volume is used as a TrueCopy volume Executing Cache mode cannot be changed because there is an LDEV that Cache Residency Manager bind mode is set 9 28 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify external_grp Error code Executing Async sspi ssB2 Error message Description Executing Cache mode cannot be changed because the specified external volume includes a pool volume or an LDEV that is used by LUSE Executing The cache mode cannot be changed because one of the following applies to the specified external volume e A pool volume of the pool that consists of both external volumes and internal volumes A pool volume of the pool where the multi tier pool option is enabled Executing The attribute of the external volume cannot be changed from the current cache mode to the specified cache mode Executing The attribute cannot be changed because the external volume group is not mapped for online data migration Executing The specified command cannot be accepted because the command is not supported Executing An internal error occurred on the changing of an external volume option Call Hitachi Data Systems Support Center Executing The specified parameter is incorrect Check the Command Control Interface Command Reference Table 9 13 SSB codes that are return
333. lumes Dynamic Provisioning and make the LDEVs available to the host Operation overview Setting port speed as needed Description Enable LUN security for the port Modify settings such as port topology and data transfer Executed command raidcom modify port port lt port gt security_switch y Creating host group group Specify port and create host raidcom add host_grp port lt port gt host_grp_name lt host group name gt Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation overview Description Executed command 3 Setting host Specify port and set host mode raidcom modify host_grp mode for host group port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt 4 Displaying Display host group information raidcom get host_grp host group and confirm result of executing port lt port gt lt host group information command name gt 5 Adding host to Register host to host group of raidcom add hba_wwn host group the port port lt port gt lt host group name gt hba_wwn lt WWN strings gt 6 Displaying Display WWN of connection raidcom get hba_wwn WWN host registered to the host port lt port gt lt host group information group and confirm the result of name gt executing the command 7 Creating LDEV Specify a parity group and rai
334. lumes Dynamic Provisioning for Mainframe 5 29 Script examples 25525 e0 Oren as eaeS ian seen eds nna ce 4 SSR ae 5 30 Virtual volume Dynamic Tiering operations 0 0 eee eee eee 5 32 Operational NOW o lt ccvens eds eo ed ee OE Sa See eve we eae ws 5 32 Creating virtual volumes Dynamic Tiering 0002 eens 5 34 Script CXAMPIES asetan ie ma Genes ode eae xeceerdwatwd asec ee ee 5 36 External volume operations 000 cee eee ees 5 39 Creating external volUMES 1 anaana aana 5 39 Script Examples soccer csedactaads tceaageetessautetases Gent 5 41 Virtual Partition Manager operations asa aaua ee ees 5 44 Performing Virtual Partition Manager operations 00005 5 44 Hitachi Command Control Interface User and Reference Guide Displaying CLPR information 0 000 cee ees 5 45 Migrating parity groups ina CLPR ee es 5 45 Displaying parity group information 0 0 cee ees 5 45 Moving parity groups 6 22000ee cede ewiene de eee eed 5 45 Checking result of CLPR transfer 1 ce es 5 46 Server Priority Manager operations 1 0 0 00 eee ees 5 46 State transitions of Server Priority Manager 00 e eee eee 5 47 Controlling server performance 1 0 ccc ees 5 47 Checking WWN of host bus adapters 000 ee eee eee 5 49 Setting the priority on host bus adapter 0000 e eee 5 49 Checking the status of the prioritized WWN and the non p
335. machine by HORCM_VCMD 0000 cee eee eee eee 3 47 Example of the configuration definition files when specifying a virtual storage machine by HORCM_VCMD 0 00 cece eee ees 3 47 Specifying a virtual storage machine by command options 3 48 Configuration definition file settings when specifying a virtual storage machine by command optionS 0 000 e eee eee eee 3 48 Example of the configuration definition files when specifying a virtual storage machine by command options 00 eee e eae 3 49 Commands to the virtual storage machine 00 eee 3 50 Operation target when you specify the virtual storage machine by the raidcom command aasan bAR Geos Kew eR Ree Se Eee 3 51 v Hitachi Command Control Interface User and Reference Guide vi OA e 64 64 de Shae Soe wed twee ow ee 6 SO EU de ew 4 1 Starting up on UNIX systeMS 1 0 es 4 2 Starting up on Windows systeMS saaa anaana aaa 4 3 Starting up on OpenVMS systemMS 0 es 4 4 Starting CCI as a service Windows systemS 0 000 c eee e eee eee 4 6 Provisioning operations with CCI 242 ce eee eee eee ee ee ee em 5 1 About provisioning operations 0 0 0 saae 5 2 Overview of the configuration setting command 00000e ee 5 2 Synchronous command processing 000 c eee eee eee 5 3 Asynchronous command processing 0 cee eee tees 5 3 Asynchronous commands 000 cee eee eee eee 5 4 Help on configuration se
336. mage pair Executing The specified LDEV is used as a TrueCopy pair Executing The specified LDEV is used as a Universal Replicator pair Executing The specified LDEV is used as a Thin Image or Copy on Write Snapshot pair Executing The specified LDEV is used as a Volume Migration pair Executing The specified LDEV is blocked Executing The associated pool is blocked Executing Page cannot be discarded because the pool volume is being deleted or the Tier is being reallocated Executing The operation cannot be done because the system pool volume is blocked Executing The specified LDEV is not installed Executing The specified LDEV is not a virtual volume of Dynamic Provisioning Dynamic Tiering Executing The specified LDEV is used as a journal volume Executing It is not associated to a pool Executing Page cannot be discarded because the specified LDEV is a TSE VOL Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 31 SSB codes that are returned by raidcom modify Idev quorum_enable command raidcom modify Idev quorum_enable Executing Error code Async sspi ssB2 CMDRIJE Executing The LDEV number is out of settable range CMDRJE Executing The device type is invalid Error message Description CMDRJE Executing The serial number is invalid CMDRJE Executing The quorum disk ID is out of sett
337. mand raidcom reset hba_wwn Executing Error code Error message Async sspi ssB2 Description Executing The program product is not installed Executing The value of Host group ID exceeds the maximum Executing The host group is not installed Executing The attribute of the specified port is Initiator or External Executing The specified WWN does not exists Troubleshooting 9 87 Hitachi Command Control Interface User and Reference Guide Table 9 55 SSB codes that are returned by raidcom add copy_grp command raidcom add copy_grp Error code Executing Async sspi ssB2 Error message Description CMDRJE Executing The number of MU exceeds the maximum CMDRJE Executing Invalid device number CMDRJE Executing The specified journal ID exceeds the range CMDRJE Executing A device group is not installed CMDRJE Executing There is a copy group CMDRJE Executing The number of copy groups in the system reached the maximum CMDRIJE Executing The specified device group is already defined in the other copy group CMDRJE Executing There is an LDEV in the device group that has an undefined device name CMDRJE Executing The same device names of LDEV are in the device group CMDRJE Executing The same LDEVs are in the copy group Invalid Character Executing Unavailable character is included in the name of copy group T
338. mation set to PortCLI A and PortCL2 A Set the connection host WAN 210000e0 8b0256f8 to PortCLi A host group HP UX P and the connection host WAN 210000e0 8b0256f9 to PortCL2 A host group HP UX S Display the connection host WNs set to PortCLi A host group HP UX P and to PortCL2 A host group HP UX S Create each 10 of 106 Ldev to cexternal_grp_id 1 1 LDEV 0 to 9 10 to 19 Give a nickname to LDEV 0 to 19 my_volume 0 to 19 Set the LDEV MP Blade ID of LDEV 0 to 19 to 2 Display the information of LDEV 0 to 19 internal VOL Give a device name data 0 to 19 to LDEV 0 to 19 and add it to device group name grpl data0 to 9 and grp2 datal0 to 19 Figure 5 14 Script Examples of External Volume Operation 2 3 5 43 Hitachi Command Control Interface User and Reference Guide for I S i in 10 1 19 do raidcom add device_grp device_grp_name grp2 data i Idev_id bi raidcom get command_status raidcom reset command_status raidcom get device_grp device_grp_name grpl Display the device group information raidcom get device _grp device_grp_name grp2 grpi 9 erpl grp2 raidcom add copy_grp copy_grp_name ora grpl i grp2 Create copy group ora with the device raidcom get command_status group erpl grp2 raidcom reset command status raidcom get copy erp Display the copy group information for I i in 0 1 9 do Defining
339. maximum Executing The operation to resource group 0 meta_resource cannot be performed Executing An internal error occurred Call Hitachi Data Systems Support Center Troubleshooting 9 97 Hitachi Command Control Interface User and Reference Guide Table 9 71 SSB codes that are returned by raidcom get resource command raidcom get resource Executing Error code Error message g Async Description CMDRJE Executing 2EFO FEEC An internal error occurred Call Hitachi Data Systems Support Center Table 9 72 SSB codes that are returned by raidcom map resource command raidcom map resource Executing Error code Async sspi ssB2 Error message Description Executing The specified LDEV number or the LDEV number for the virtual volume is out of the range Executing SSID is not with in the valid range Executing The specified emulation type of the LDEV is not supported in this command Executing The specified attribute of the virtual LDEV is not supported Executing The specified attribute of the virtual LDEV is invalid Executing You cannot execute the command because a parameter required for the virtualization was not specified Executing The specified emulation type is invalid Executing The specified LDEV cannot be operated because it belongs to the default virtual storage machine Executing The specified volume cannot be operated be
340. me Access to mainframe P VOL Read write enabled Access to mainframe S VOL Read write enabled simplex Pending Read write enabled Reject copying Duplex Read write enabled Reject pair COPY SP SP Pend Read write enabled Reject suspend in COPY SP COPY COPY PSUS SP V split Read write enabled Read write enabled suspend in Quick Split PSUS COPY PSUS pair suspended split Split Read write enabled Read write enabled suspend PSUE pair suspended error Suspend Read write enabled Reject suspend by failure COPY RS Resync Read write enabled Reject resynchronizing COPY RS R Resync R Reject Reject Operational differences for multiplatform volumes restoring The following table shows the operational differences for TrueCopy Universal Replicator and ShadowImage multiplatform volumes CCI functions Hitachi Command Control Interface User and Reference Guide 3 43 Table 3 14 Operational differences for multiplatform volumes Universal Replicator operations LU path information reported to CCI LU path definition ShadowImage TrueCopy operations operations LU path is Actual LU path ShadowImage for Commands are Commands are defined information is Mainframe operations rejected rejected reported LU path is not Dummy LU number ShadowImage
341. me is set for the specified LDEV CMDRJE Executing 2E00 0101 The parity group number or the external group number is not in the effective range Get Command Async 2E00 1005 Failed to restore the LDEV that is created to Status external volume group CMDRJE Executing 2E00 6000 The specified pool ID is not in the effective range Get Command Asynchrono 2E00 6002 The total capacity of Dynamic Provisioning V VOL Status us which is defined in the specified pool exceeds the permitted capacity in the pool CMDRJE Executing 2E00 7000 The specified CLPR number is not in the effective range CMDRJE Executing 2E00 8301 MP Blade ID is not in the effective range CMDRJE Executing 2E10 0003 The specified LDEV is used as a Compatible FlashCopy V2 relationship Get Command Async 2E10 001F The operation cannot be done because the total Status capacity of virtual volumes for Dynamic Tiering in the system exceeds the maximum Get Command Async 2E10 005A The operation cannot be performed because the Status following information of the migration source and the migration target does not match e serial number e product ID e emulation type e SSID e LUSE e CVS configuration e LDEV number Get Command Async 2E10 0100 The volumes cannot be added because the Status encryption value of the key number that is set to encryption ECC is invalid Get Command Async 2E10 0101 The volumes cannot be added because the check Status sum of the encryption key
342. mes e CCI log files on page 2 36 e CCI trace files on page 2 38 2 35 CCI software environment Hitachi Command Control Interface User and Reference Guide e CCI trace control command on page 2 38 e Command logging for audit on page 2 39 CCI log files HORCM logs are classified into startup logs and execution logs e The startup logs contain data on errors that occur before HORCM becomes ready to provide services Thus if HORCM fails to start up due to improper environment setting refer to the startup logs to resolve the problem e The HORCM execution logs error log trace and core files contain data on errors that are caused by software or hardware problems These logs contain internal error data that does not apply to any user settings therefore you do not need to refer to the HORCM execution logs e When an error occurs in execution of a command data on the error is collected in the command log file Users may refer to the command log file if a command execution error occurs The following figure shows a graphical representation of the CCI log and trace files within the CCI configuration environment HORCM execution environment E Log directory HORCM start up logs HORCM HORCM traces Command traces Figure 2 24 Logs and traces The startup log error log trace and core files are stored as shown in Table 2 4 Log file names and locations on page 2 37 Specify the directories for the HORCM an
343. ming gt snap ldev_id lt ldev gt tse_ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt clpr lt clpr gt Check with the attribute setting It is checked whether the operation is performed for the existing LDEV or not If the operation is attempted to be performed for an LDEV that does not exist an error is detected If it is not clear whether the LDEV as the target of the operation exists in the configuration definition file if the target LDEV information does not exist in the configuration definition file the error is not detected The commands as the target of the check are shown below CCI functions 3 17 Hitachi Command Control Interface User and Reference Guide 3 18 e raidcom modify host_grp port lt port gt lt host group name gt host_mode lt host mode gt host_mode_opt lt host mode option gt e raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom delete hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom set hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt wwn_nickname lt WWN Nickname gt e raidcom reset hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt e raidcom add lun port lt port
344. mmand Status Async Online from the mainframe host CMDRJE Executing The attribute of a port is not External ELUN CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Table 9 63 Async An internal error occurred by the operation of a path for an external path Call Hitachi Data Systems Support Center SSB codes that are returned by raidcom delete path command raidcom delete path Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description The path group is not in a effective range CMDRJE Executing The value of the specified port is incorrect Get Command Status Async The path operations cannot be performed for the following reasons e The target of the specified path group is TagmaStore USP TagmaStore NSC The specified path group contains the external volume that is set the reserve attribute from the host Get Command Status Async The operation cannot continue because the microcode is being replaced CMDRJE Executing The command cannot be accepted After a while execute the same command CMDRJE Executing There is no external volume group CMDRJE Executing There is no external connection path CMDRJE Executing WWYN is not registered CMDRJE Get Command Status Executing Async There
345. mmand Async 2E31 3001 Command cannot be executed because the RCU Status identification code of a path is invalid Get Command Async 2E31 3101 Command cannot be executed because the serial Status number is not unified in the specified path CMDRIJE Executing 2ED6 OOEE The command cannot be accepted because the DKC is busy After a while execute the same command Get Command Async 2ED6 3005 An internal error occurred Status Call Hitachi Data Systems Support Center CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage system is invalid 9 80 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add rcu_path Error message Executing Async Error code Executing 2EF3 Table 9 48 SSB codes that are returned by raidcom delete rcu command Description The specified parameter is invalid Check the Command Control Interface Command Reference raidcom delete rcu Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description CU on the RCU exceeds the effective range CMDRJE Executing Invalid product ID or path registration ID Get Command Status Async Command cannot be executed because the parameter of specified RCU is invalid CMDRJE Executing The value of specified port on the side of RCU is invalid Get Command Status Async The CU number is out of effective range CMDRJE Ge
346. ms of your agreements with Hitachi Data Systems Corporation Notice on Export Controls The technical data and technology inherent in this Document may be subject to U S export control laws including the U S Export Administration Act and its associated regulations and may be subject to export or import regulations in other countries Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export re export or import the Document and any Compliant Products Hitachi is a registered trademark of Hitachi Ltd in the United States and other countries Hitachi Data Systems is a registered trademark and service mark of Hitachi Ltd in the United States and other countries Archivas Essential NAS Platform HiCommand Hi Track ShadowImage Tagmaserve Tagmasoft Tagmasolve Tagmastore TrueCopy Universal Star Network and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation AIX AS 400 DB2 Domino DS6000 DS8000 Enterprise Storage Server ESCON FICON FlashCopy IBM Lotus MVS OS 390 RS 6000 S 390 System z9 System z10 Tivoli VM ESA z OS z9 z10 zSeries z VM and z VSE are registered trademarks or trademarks of International Business Machines Corporation All other trademarks service marks and company names in this document or website are properties of their respective owners Microsoft product screen shots are repr
347. n Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the ShadowImage pair is being resynchronized when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the P VOL of a ShadowImage pair Executing The command ends abnormally because the ShadowImage pair status is other than PSUS when the volume is shared between P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a ShadowImage pair Executing A Snapshot data cannot be obtained because the TrueCopy asynchronous pair status is other than PSUS or PSUE when the volume is shared between the P VOL of a Thin Image Copy on Write Snapshot pair and the S VOL of a TrueCopy asynchronous pair Executing The operation cannot be performed because the Quick Restore is being operated on the specified ShadowImage P VOL Executing A Snapshot data cannot be obtained because the pool or the pool VOL is blocked Executing The command ends abnormally because other than the raidcom add snapshot command is issued for the volume other than the Thin Image or Copy on Write Snapshot pair Executing 9 72 The command ends abnormally because the pair is in the state of unacceptable the command Troubleshoot
348. n raidar exe raidar Connection confirmation ROOT HORCM usr bin raidqry exe raidqry Trace control ROOT HORCM usr bin horcctl exe horcctl HORCM activation script ROOT HORCM usr bin horcmstart exe horcmstart sh HORCM shutdown script ROOT HORCM usr bin horcmshutdown exe horcmshutdown sh Connection confirmation ROOT HORCM usr binJingraid exe Synchronous waiting ROOT HORCM usr bin pairsyncwait exe pairsyncwait Configuration file making ROOT HORCM usr bin mkconf exe Text filtering ROOT HORCM usr bin rmawk exe Database Validator setting ROOT HORCM usr bin raidvchkset exe raidvchkset DB Validator confirmation ROOT HORCM usr bin raidvchkdsp exe raidvchkdsp DB Validator confirmation ROOT HORCM usr bin raidvchkscan exe raidvchkscan Storage Replication Adapter ROOT HORCM usr bin rmsra exe rmsra Sample file for horcmstart ROOT HORCM loginhorcm com Sample file for horcmstart ROOT HORCM Jrunhorcm com Note AN e ROOT is defined as SYS POSIX_ROOT POSIX_ROOT is necessary when using C RTL e The user name for OpenVMS is System CCI log and trace files The CCI 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 status transition history of the paired volu
349. n the HA configuration if a TrueCopy command issued by host C fails in host B because host B has gone down and or IO_ERROR of the command device host A is connected and the command execution is retried Primary volume Secondary volume Paired volume Linkage with HA software The HORC Manager must not be an object of the process monitoring by the HA software cluster manager because HORCM should run in the same level as the cluster manager Cooperation with HA software is done by activating the takeover command from the shell script activated by the cluster manager in units of the package software Note Cannot use a pair volume for the cluster lock disk that HA software uses for election Maintenance Restart of HORCM is required if the storage system configuration is changed for example microcode exchange cache memory install uninstall TrueCopy only In the case of an error for example single error in cache memory which made the pair volume is accompanied by maintenance work the pairresync Or paircreate command cannot execute copy rejection Command device Each TrueCopy ShadowImage command is executed by issuing a command to the command device The TrueCopy ShadowImage command is read or written from into the specific block area of the command device Therefore the command device cannot be used In addition this device must not belong to an LVM volume group For Windows systems do
350. n 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 e LDEV e Port e Host group Checking the contents before executing the script helps reduce debugging after running the script 3 16 Hitachi Command Control Interface User and Reference Guide CCI functions How to check The script is performed by specifying it as follows Details of check contents Details of Context check is described below checking contents before issuing a script can reduce load for the debug operation in a way of executing script LDEV check The check is performed from the following perspective Note that checking for the object information that is related to the LDEV such as pool or device group or an attribute of LDEV is not executed Check with the additional operation It is checked to ensure no same LDEV as the already existing LDEV is added If the same LDEV is 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 does not exist in the configuration definition file the error is not detected Therefore the script is executed and the LDEV is added The command as the target of the check is shown below raidcom add ldev parity_grp_id lt gno sgno gt external_grp id lt gno sgno gt pool lt pool ID gt lt pool na
351. nd CMDRJE Executing The specified LDEV is not in the journal CMDRJE Executing The specified journal ID is not registered Get Command Status Async The operation failed because the specified journal is not registered Get Command Status Async The journal volume cannot be added or the journal cannot be added to the extended CT group due to insufficient capacity of the shared memory SM CMDRJE Executing SM for Universal Replicator is not installed CMDRJE Executing The number of specified LDEVs is invalid Get Command Status Async The specified volume cannot be used as a journal volume because it is an external volume that can execute the I O suppression mode Get Command Status Async The specified journal cannot be deleted because there are data volumes CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center Table 9 18 SSB codes that are returned by raidcom add journal command raidcom add journal Error code Error message RS Description sync ssBi SSB2 CMDRJE Executing 2E00 0000 The value of LDEV number is invalid CMDRJE Executing 2E00 0018 A new journal volume cannot be registered because the number of journal volume exceeds the maximum t
352. nd PortCL2 A Display the host group information that is zset to PortCLI A and PortCL2 A Set the connection host WN 210000e0 8bO256f8 gt to the PortCLi A host group HP UX P and gt the connection host AWN 210000e0 8bO256f9 to the PortCL2 A host group HP UX S Display the connection host WAN that is set gt to PortCLI A host group HP UX P and the seonnection host WAN that is set to PortCL2 A shost group HP UX S Create each 10 of 10G Ldev to the Par ity_grp_id 1 1 DEV O to 9 Execute the quick format to LDEV 0 to 9 raidcom initialize Idev Ildev_id Shi operation Give a nickname to LDEV 0 to 9 gt my_volume 0 to 9 Figure 5 5 Script examples of virtual volume operation Dynamic Provisioning 1 3 Provisioning operations with CCI 5 27 Hitachi Command Control Interface User and Reference Guide for I S i in 0 1 9 do raidcom modify Idev Idev_id i mp_blade_id 2 raidcom get Idev Idev_id 0 cnt 10 raidcom add dp_pool pool_id 1 Idev_id 0 cnt 10 raidcom get command status raidcom reset command_status for I S i in 10 1 19 do raidcom add Idev Idev_id hi capacity 10g pool 1 for 1 S i in 20 1 29 do raidcom add Idev Idev_id hi capacity 10g pool 1 raidcom get command_status raidcom reset command_status for I S i in 10 1 29 do raidcom modify Idev Idev_id bi device_name my_virtual_volume_S i for I i in 10 1
353. nd Reference Guide raidcom add external_grp Error message Get Command Status Executing Async Error code SSB1 SSB2 Description LUN of specified external storage port does not exist Get Command Status The external volume cannot be created because the specified external LU is a command device Get Command Status The WWN on the side of specified external storage does not connected to a External port This message may be output if the migration source storage system is USP V VM and the host mode option 2 is not set to the port that connects to the migration target storage system Get Command Status Async The specified external LU cannot create a external volume because the transition of data is required Get Command Status Async The specified path group cannot be operated because a path between other devices exists CMDRJE Executing The storage system is in internal process or the configuration changing processes are conflicting CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async Package for Mainframe is required when you specify the emulation type of mainframe Get Command Status Async The specified MP Blade is not installed CMDRJE Get Command Status Executing Async The program product of Universal Volume Manager is not installed CMDRJE Get C
354. nd information for the journal volume o Shows the Copy on Write Snapshot pool setting and information for the Copy on Write Snapshot pool Data Protection facility The Data Protection Facility permits main operations to volumes that you can see on the host and prevents wrong operations CCI controls protected volumes at the result of recognition of protection CCI recognizes only volumes that the host shows For that purpose LUN Security is provided for the CCI environment The Data Protection Facility ON OFF is controlled by the security setting for the command device as shown in the following table Table 7 1 Security setting for command device Command device setting Group Security to be set information acquisition User Securty authentication No security Only HORCM_DEV allowed User authentication required User authentication required Only HORCM_DEV allowed CMD security Data protection operations with CCI 7 5 Hitachi Command Control Interface User and Reference Guide Command device setting User Group Security to be set authentication information acquisition Security CMD security Only HORCM_DEV allowed CMD security User authentication required CMD security User authentication required Only 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 Us
355. nder the host group Table 9 60 SSB codes that are returned by raidcom add host_grp command raidcom add host_grp Executing Error code Error message Async sspi ssB2 Description Executing The program product is not installed Executing The value of host group ID exceeds the maximum Executing The attribute of the specified port is Initiator or External Executing The same host group name is already installed in the specified port Executing The default host group name cannot be registered for the host group ID is other than 0 9 90 Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 61 SSB codes that are returned by raidcom modify host_grp command raidcom modify host_grp Error code Executing Async sspi ssB2 Error message Description Executing The command device being used at the local CCI exists under the host group Executing Changing of the host mode host mode option cannot be executed for the port of Initiator or External Executing The invalid host mode is specified Executing The cancelling of the host mode option 61 setting was aborted Executing The host group ID exceeds the maximum Executing The program product is not installed Executing The specified host group is not installed Executing The command device being used at the local CCI exists under the host group
356. ned by raidcom delete external_grp raidcom delete external_grp Error code Error message R Description sync ssBi SSB2 CMDRJE Executing 2E00 4100 The external volume group is in the effective range Get Command Async 2E10 0012 LDEVs in the external volume group are devices Status that have a CC XRC attributes CMDRJE Executing 2E11 0153 The specified external volume group is used in another operation Get Command Async 2E11 4103 Destage is not executed Status Get Command Async 2E11 4104 The external volume is used as Compatible Status FlashCopy V2 Get Command Async 2E11 4105 The specified external volume cannot be deleted Status because audit logs for the system disk are being used Get Command Async 2E11 8004 The operation cannot be done because the Status internal processing is in progress CMDRJE Executing 2E11 8010 The storage system is in internal process or the configuration changing processes are conflicting Get Command Async 2E11 8108 The operation cannot be done because there is Status blocked part in the system CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Executing 2E20 4100 There is no external volume group CMDRJE Executing 2E30 0007 LU path is defined to LDEV in the external volume group Get Command Async 2E30 0057 The external volume is used as a system dis
357. ned by raidcom modify pool command raidcom modify pool Executing Error message g Async Executing Error code SSB1 SSB2 Description The value of pool ID is invalid Executing The specified pool is for Thin Image or Copy on Write Snapshot Executing The value of maximum reserve ratio is out of range or it falls below the maximum reserve ratio of the V VOL Executing The specified Tier Range value is invalid Executing Relations between the specified lower limit of Tier Range and the Delta value is invalid Executing The specified Tier capacity threshold value is out of range Executing The threshold of the specified High water mark is out of range Executing The operation cannot be done because the specified threshold of Warning is larger than the threshold of the specified High water mark Executing The specified tier number is out of range Executing The operation cannot be done because the total capacity of virtual volumes for Dynamic Tiering in the system exceeds the maximum Executing 9 54 The specified pool is in the state of blocked Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify pool Error code Error message Brae di Description sync SSB1 SSB2 Get Command Async 2E10 600C The setting of t
358. nformation Display LU path information and confirm the result of executing the command raidcom get lun port lt port gt lt host group name gt Creating internal volumes Mainframe volume To create LDEVs of internal volumes Mainframe volume and make the LDEVs available to the host perform the following provisioning operations 5 20 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation SSID settings arbitrarily Description Configures the SSID unless it is configured Set register the SSID by specifying undefined LDEV numbers in the area in which SSIDs are not defined Command raidcom modify ldev ldev_id lt ldev gt ssid lt value gt Creating LDEVs Creates LDEVs by specifying parity groups raidcom add ldev parity _grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Formatting LDEVs Formats created LDEVs raidcom initialize ldev ldev_id lt ldev gt operation lt type gt Creating LDEV nicknames arbitrarily Creates LDEV nicknames This operation is optional raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Configuring MP blades of LDEVs Configures MP blades of created LDEVs raidcom modify ldev
359. nformation and a lock information Logging out Log out raidcom logout 5 16 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Resource group operations Creating resource groups To create resource groups perform the following provisioning operations Operation Creating resource groups Description Creates resource groups Command raidcom add resource resource name lt resource group name gt Allocationg resources to resource groups Specifies resources that are allocated to meta_resource resource group and allocates resources to created resource groups raidcom add resource resource name lt resource group name gt ldev_id lt ldev gt port lt port gt port lt port gt lt host group name gt parity_grp_id lt gno sgno gt external grp_id lt gno sgno gt Displaying a resource group information Deleting resource groups Operation Deleting resources that are allocated to resource groups Displays a resource group information and confirms execution results of commands Description Deletes resources that are allocated to resource groups In other words this operation allocates resources to resource group meta_resource raidcom get resource To delete resource groups perform the following provisioning operations Command raidcom delete resource resource name lt resourc
360. nformation in HORCM_LDEV in the configuration definition file raidvchkdsp Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairsyncwait 3 50 Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file CCI functions Hitachi Command Control Interface User and Reference Guide Commands pairmon How to issue the command to the virtual storage machine Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file Remarks raidscan Specify the virtual storage machine by the s lt seq gt option The virtual storage machine can be specified regardless of the description contents of the configuration definition file You cannot specify a virtual storage machine by the u lt unit ID gt option of the raidscan command Use the s lt seq gt option Specify the virtual storage machine by a unit ID by the command option p lt port gt The raidar command has no option to specify a serial number nor a unit ID Use the p lt port gt option as CL1 An specify a unit ID inn raidqry The information of both VSP G1000 and the virtual storage machine is displayed raidvchkscan Specify the virtual storage machine by the command option s lt seq gt or u lt unit ID gt The virtual storage machine can be specified regardless of the desc
361. nframe S VOL Read write enabled not in pair Pending Read write enabled Reject copying Duplex Read write enabled Reject pair PSUS pair suspended split Suspend Read write enabled Reject suspend PSUE pair suspended error Suspend Read write enabled Reject suspend Suspending Suspending PAIR PAIR Read write enabled Reject pair Deleting 3 42 Deleting PAIR COPY PAIR COPY Read write enabled CCI functions Hitachi Command Control Interface User and Reference Guide Reject pair copying Pair status in Storage Navigator Access to mainframe S Access to mainframe Pair status in CCI Mainframe Hold Open PSUS Mainframe PSUS P VOL Read write enabled VOL suspend Holding PSUS PSUS Read write enabled suspend Hide PSUE PSUE Read write enabled Reject suspend Suspend PFUL PFUL Read write enabled Reject suspend Suspend PFUS PFUS Read write enabled Reject suspend Suspend SSWS SSWS Read write enabled suspend When system option mode 20 is on this is a read only volume Table 3 13 Pair status and access permission for ShadowImage ShadowImage for Mainframe Pair status in Storage Navigator Pair status in CCI Mainframe Simplex Open Mainfra
362. ng 2EE8 OOFO The specified command cannot be accepted because the command is not supported CMDRJE Executing 2EE8 FEEC An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing 2EF3 0102 The specified parameter is invalid Check the Command Control Interface Command Reference CMDRJE Executing 2EF3 9F02 The specified operation cannot be performed because it is not supported CMDRJE Executing 2EF6 FEEC An internal error occurred Call Hitachi Data Systems Support Center Troubleshooting 9 101 Hitachi Command Control Interface User and Reference Guide Table 9 79 SSB codes that are returned by raidcom add spm_group command raidcom add spm_group Error message Executing Async Executing Error code SSB1 SSB2 Description Server Priority Manager is being used by Device Manager Storage Navigator Executing Server Priority Manager program product is not installed Executing The number of Server Priority Manager groups exceeds the maximum Table 9 80 SSB codes that are returned by raidcom delete spm_group command raidcom delete spm_group Error message Executing Async Executing Error code SSB1 SSB2 Description Server Priority Manager is being used by Device Manager Storage Navigator Executing The specified WWN or nickname does not exist Executing Server Priority Manager program product is not ins
363. ng CTGIDs If more than one group defined in the configuration definition file is assigned to the same CTGID then pair operations on the group specificity apply to the entire consistency group Sidefile cache for TrueCopy Async The first in first out FIFO queue of each CT group is placed in an area of cache called the sidefile The sidefile is used for transferring TrueCopy Async recordsets to the RCU The sidefile is not a fixed area in cache but has variable capacity for write I Os for the primary volume If the host write I O rate is high and the MCU cannot transfer the TrueCopy Async recordsets to the RCU fast enough then the sidefile capacity expands gradually The sidefile has a threshold to control the quantity of data transfer of host side Data replication operations with CCI 6 27 Hitachi Command Control Interface User and Reference Guide write I O Host side write I Os are controlled by delaying response when the sidefile exceeds the constant quantity limit on cache in the storage system see Figure 6 10 Sidefile quantity limit on page 6 28 Sidefile Threshold 30 70 of Cache Sidefile Area Cache Total cache minus FlashAccess High water mark 30 of Cache for TagmaStore USP 0 to 70 of Cache the default is 40 Writing are waited until under threshold Writing response are delayed Figure 6 10 Sidefile quantity limit Sidefile area Sidefile area 30 to 70 of cache as set on Storage Naviga
364. ng Resource Group function the storage administrator for each resource group can access only the resources in the resource group The storage administrator cannot access resources in other resource groups This prevents the risk of destroying the data by another storage administrator in the other resource groups or of leaking out the data Resource locking function The resource locking function prevents conflict among multiple users User scripts cannot be guaranteed to work correctly when there are multiple users Storage Navigator and SVP You can use the lock command while the script is running to ensure completion To use the lock command user authentication is required CCI functions available on all RAID storage systems CCI provides the following functionality on all Hitachi Data Systems RAID storage systems e In system replication e Remote replication e Data protection In system replication CCI provides command line control for in system local replication operations including ShadowImage Thin Image and Copy on Write Snapshot CCI displays local replication information and allows you to perform operations by issuing commands or by executing script files Remote replication CCI provides command line control for remote replication operations including TrueCopy Universal Replicator and global active device CCI displays remote replication information and allows you to perform operations by issuing commands or by execu
365. ng by a directory and this method requires finding its volume name To solve such a complication CCI supports a method that flushes the system buffer associated with a logical drive through finding a volume guid corresponding to a group of the configuration file This method does not depend on mounted point so that it is possible to flush the volume mounted by a directory This method is supported to be specified a group to the raidscan find sync command Mounted point A Volume guid NTFile system Buffer LDM n eee Device Devicel Volumes ASII HarddiskVolumeX HarddiskVolumeY ee ripex preteste PhysicalDrive Y nir H i Physical os i f I sasssa H Ci i Volumes Device HarddiskX DR a i Mirrored Volume i ORB ORA i Group in configuration file ETTTETTTTTETTTETETTETTTTETTTTTETTTTTTETTTETTTTTTTTTTTETT Figure 8 3 LDM volume flushing 8 6 Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide 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 gt Dmt1 Dsk1 8d69 00c00d003bl1e SYNC ORB ORB_001 gt Dmt1 Dsk2 8d69 00c00d003bl1e SYNC ORB ORB_002 gt Dmt1 Dsk3 8d69 00c00d003ble Volume bf 48a395 0ef6 11d5 Volume b 48a395 0ef6 11d5 Volume bf 48a395 0ef6 11d5 The following example flushes th
366. ng command to permit the volumes specified Example for UNIX systems cat SHORCMPERM HORCM usr bin raidscan find inst Example for Windows systems type SHORCMPERM x HORCM etc raidscan exe find inst e If no HORCM permission file exists then etc horcmgr executes a built in command to permit all volumes of a host See Without a HORCMPERM file Commands to run on different operating systems on page 7 13 for examples of commands run on an operating basis e 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 specified from a user s shell script HORCMPERM MGRNOINST Determining the protection mode command device 7 14 The inquiry page is not changed for a command device with protection mode ON Therefore CCI provides how to find the protection mode command device To determine the currently used command device use the horectl D command This command shows the protection mode command device by adding an asterisk to the device file name Example for HP UX systems horectl D Current control device dev rdsk coOt0d0o indicates protection ON Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide Examples of using CCI commands This chapter provides examples of typical tasks performed using CCI commands O Group version control for mixed storage system confi
367. nickname of created LDEV This operation is arbitrary raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Setting MP blade of LDEV Set MP blade of created LDEV raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Displaying LDEV information Display information of created LDEV and confirm the result of executing the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt Creating LU path Specify port map LDEV to LUN and create an LU path raidcom add lun port lt port gt lt host group name gt ldev_id lt ldev gt lun_id lt lun gt Displaying LU path information Display LU path information and confirm the result of executing the command Script Examples raidcom get lun port lt port gt lt host group name gt The following shows the script examples of external volume operations Provisioning operations with CCI 5 41 Hitachi Command Control Interface User and Reference Guide 5 42 raidcom login USEROI PASSO1 raidcom lock resource resource_grp_name meta_resource raidcom modify port port CL3 A port_attr ibute ELUN raidcom modify port port CL4 A port_attribute ELUN raidcom discover external storage port CL3 A raidcom discover lun port CL3 A external_wan 50060880 1611a870 raidcom add external_erp path_grp 1 external_grp_id 1 1 port CL3 A
368. nnot be performed because the remote storage system does not support the path between CUs Get Command Status Async Command cannot be executed because the serial number is not unified in the specified path CMDRJE Executing The command cannot be accepted because the DKC is busy After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The value of SSID on the remote storage system is invalid CMDRJE Executing The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 50 SSB codes that are returned by raidcom delete Idev command raidcom delete Idev Error message Executing Async Error code SSB1 SSB2 Description CMDRJE Executing 2E00 0000 It exceeds the range of LDEV number Get Command Status Async 2E00 000E Troubleshooting This command does not support the emulation type of the specified LDEV 9 83 Hitachi Command Control Interface User and Reference Guide raidcom delete Idev Error message Get Command Status Executing Async Error code SSB1 SSB2 Description The specified LDEV is used as a pair of ShadowImage Thin Image Copy on Write Snapshot Volume Migration or a relationship of Compatible FlashCopy V2 Compatible Software for IBM Flas
369. not installed Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify snapshot A Error code Error message Spee Description sync SSB1 SSB2 CMDRJE Executing 2E30 000C The specified LDEV is used as a quorum disk CMDRJE Executing 2E30 0079 The Thin Image or Copy on Write Snapshot pair cannot be restored because the volume that is set the S VOL Disable is specified as the P VOL CMDRJE Executing 2E30 007A The command ends abnormally because the volume other than OPEN V is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair CMDRJE Executing 2E30 0081 The command ends abnormally because the external volume mapped for the online data migration is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair CMDRJE Executing 2E30 0090 The pair operation is rejected because the specified volume as the primary volume is a reserved volume for GAD or the volume for the GAD pair which is in the invalid status CMDRJE Executing 2E30 0091 The pair operation is rejected because the specified volume as the secondary volume is a reserved volume for GAD or the volume for the GAD pair CMDRJE Executing 2E3F 8000 The specified operation is not supported in the current microcode version CMDRJE Executing 2EC6 FEEC An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing 2EF3 0002 The spe
370. nstalled CMDRJE Executing 2E20 0002 LDEV is not registered in the device group CMDRJE Executing 2E20 2100 A device group is not installed CMDRJE Executing 2E22 000E The number of LDEVs that can be deleted in a operation exceeds the maximum The number of LDEVs that can be deleted includes the number of LDEVs of a LUSE CMDRJE Executing 2E23 0008 The number of specified LDEVs is invalid Table 9 22 SSB codes that are returned by raidcom add device_grp command raidcom add device_grp Error code Error message PN Description sync SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceeds the range of LDEV number CMDRJE Executing 2E20 0000 LDEV is not installed CMDRJE Executing 2E22 0009 The number of device name in the system has reached the maximum CMDRJE Executing 2E22 000A The device name of an LDEV is duplicated in the system CMDRJE Executing 2E22 000E The number of LDEVs that can be registered in a operation exceeds the maximum The number of LDEVSs that can be registered includes the number of LDEVs of a LUSE CMDRJE Executing 2E23 0008 The number of specified LDEVs is invalid Troubleshooting 9 41 Hitachi Command Control Interface User and Reference Guide raidcom add device_grp Error message Error code Executing Async sspi ssB2 Description Executing It exceeds the number of device group in the system Executing The LDEV to be allocated to
371. nterface User and Reference Guide 1 Preparing for operations GUI Expanding cache memory Creating pool VOLs and formatting Create LDEVs wizard LDEVs Format LDEVs wizard Creating a pool and adding the pool VOLs Tier reallocation Disable 1 Create Pools wizard Changing Multi Tier Pool from Disable to Enable 2 t Creating V VOLs Crate LDEVs wizard Defining V VOL LU paths Add LUN paths wizard Monitoring performance of the pool View Tier Properties Adding poo VOLs Creating tiers Create Pools wizard 2 Operating raidcom initialize Idev raidcom monitor pool raidcom add dp_pool raidcom modify pool raidcom monitor pool raidcom reallocate pool raidcom get dp_pool Monitoring performance of the pool View Tler Proparies Reallocating tiers of the pool Not bt toea i expansion is required Increasing the pool capacity Expand Pool wizard raidcom add dp_pool Adding pootVOLs Expand V VOLs wizard raidcom extend Idev Increasing the V VOL capacity 3 Discontinuing operations Deleting V VOL LU paths wage g Deleting V VOLs Delete LDEVs window ora Deleting Dynamic Tiering pool VOLs Delete LDEVs window raldcom delete lun raidcom delete Idev raidcom delete pool Provisioning operations with CCI 5 33 Hitachi Command Control Interface User and Reference Guide Note 1 The multiple tiering pool is disabled when a pool is creating at CCI And multiple media cannot be registered as a pool volume
372. number MP blade ID MPB 1MA 0 0 MPB 1MB 1 1 MPB 1PE 2 2 MPB 1PF 3 3 MPB 2MA 4 4 MPB 2MB 5 5 MPB 2PE 6 6 MPB 2PF 7 7 MPB 1MC 8 8 MPB 1MD 9 9 MPB 1PL 10 10 MPB 1PM 11 11 MPB 2MC 12 12 MPB 2MD 13 13 MPB 2PL 14 14 MPB 2PM 15 15 Table 3 8 MP blade names and parameters for VSP MP blade name MP blade number MP blade ID MPB 1MA 0 0 MPB 1MB 1 1 MPB 2MC 2 2 MPB 2MD 3 3 MPB 1ME 4 4 MPB 1MF 5 5 MPB 2MG 6 6 MPB 2MH 7 7 Table 3 9 MP unit names and parameters for HUS VM MP unit name MP blade number MP blade ID LDEV grouping function The LDEV grouping function enables you to create a group of multiple LDEVs device group function and copy group function CCI functions 3 25 Hitachi Command Control Interface User and Reference Guide Overview 3 26 CCI can be used to create a group of multiple LDEVs by defining copy groups which are a group of copy pairs This is accomplished in both the primary and secondary configuration definition files by defining the group names of the combined LDEVs dev_name of HORCM_DEV or HORCM_LDEV To change copy group information modify the primary and secondary configuration definition files 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 CCI functions Hitachi Command Control Interface User and Reference Guide Configuration De
373. nvalid Executing The LDEV and the host group cannot be set to the different virtual storage machine Executing There is no parity group Executing You cannot execute this command because of either reason below e A resource cannot be added to the resource group because the specified resource group is undefined A resource group name cannot be changed because the specified resource group is undefined Executing There is no external volume group Executing The program products of Resource Partition Manager are not installed Executing The information for the virtual storage machine is set in the specified resource Executing You cannot execute this command because of either reason below e A resource group cannot be created because the specified resource group name is duplicated A resource group name cannot be changed because the specified resource group name is duplicated Executing A resource cannot be added to a resource group because the specified resource belongs to the resource group Executing A resource cannot be added to the resource group because the specified LDEV number is not the top LDEV number in the LUSE volume Executing Any more resource groups cannot be created because the registered number of resource groups has reached the maximum Executing A virtual storage machine cannot be created because the number of registered virtual storage machines has reached the
374. odes the log directory of Horc Manager must be set for each node The log directory of Horc Manager can be changed by setting the parameter of horcmstart See the Command Control Interface Command Reference for information about horcmstart parameters If you want to perform ShadowImage operations set the environment variable HORCC_MRCF HORCC_MRCF 1 pairdisplay g XXXX xxxx denotes a group name A Note Ifa system configuration change or a RAID configuration change causes this file to change for example cache size change microcode change these changes will not take effect until you stop HORCM horcmshutdown 0 1 and restart HORCM horcmstart 0 and horcmstart 1 Use the c option of the pairdisplay command to verify that there are no configuration errors Starting CCI as a service Windows systems 4 6 Usually CCI HORCM is started by executing the startup script from the Windows services However in the VSS environment there is no interface to automatically start CCI CCI provides the svcexe exe command and a sample script file HORCMO_run txt so that CCI can be started automatically as a service C HORCM tool gt svcexe e Usage for adding HORCM_START_SVC svcexe A command_path o for deleting HORCM_START_SVC svcexe D o for specifying a service svcexe S service_name o for dependent services svcexe C service_name service_name This command example uses HORCMO for registering the service name f
375. of paired volumes Paired logical volumes are often handled independently by servers When CCI is used the paired volumes can be managed by the replication functions for example TrueCopy ShadowImage Universal Replicator as combined or separated pairs The replication function regards the two volumes being combined or separated as a uniquely paired logical volume used by the servers Paired volumes can also be handled as groups grouping them by units of server software or units of databases and their attributes For detailed information about volume pairs for example maximum number of pairs per storage system maximum P VOL size see the user guide for your storage system and copy function for example Hitachi ShadowImage User Guide Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Special files C and D a an Local volume space of server A Special files CandD Figure 6 1 Concept of paired volumes Addressing paired logical volumes The correspondence of paired logical volumes to their physical volumes is defined by describing the paired logical volume names and group names in the configuration definition files of each server It is possible to define a server for the paired logical volumes in units of group name Each paired logical volume must belong to a group in order to determine the corresponding server Specification of volumes by commands Volume names to be
376. of the PhysicalDrive for Windows NT Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide o Device HarddiskxX Partitiond HarddiskxX ingraid LETALL CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID D Dsk0 p1 DDRS 34560D E Dsk1 p1 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 F Dsk1 p2 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 ingraid Phy CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID Harddisko DDRS 34560D Harddisk1l 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 find verify command raidscan pi LETALL find verify DEVICE FILE Group PairVol PORT TARG LUN M SERIAL LDEV E Vol44 Dsk0 ORA ORA_000 CL2 K 7 20E 61456 194 F Vol45 Dsk0 ORA ORA 000 CL2 K 7 2 61456 194 G Dmt1 Dsk1 ORB ORB_ 000 CL2 K 7 4 61456 256 G Dmt1 Dsk2 ORB ORB 001 CL2 K 7 B 61456 257 G Dmt1 Dsk3 ORB ORB 002 CL2 K 7 6 61456 258 raidscan pi LETALL find DEVICE FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT ID E Vol44 Dsk0 0 F Ch2 K 7 2 61456 194 OPEN 3 F Vol45 Dsk0 0 F Ch2 K 7 2 61456 194 OPEN 3 G Dmt1 Dsk1 0 F CL2 K 7 4 61456 256 OPEN 3 G Dmt1 Dsk2 0 F Ch2 K 7 5 61456 257 OPEN 3 G Dmt1 Dsk3 0 F Ch2 K 7 5 61456 258
377. om add host_grp port CL2 A host_grp_name HP UX S raidcom modify host_grp port CLI A 0 host_mode HP UX raidcom modify host_grp port CL2 A 0 host_mode HP UX raidcom get host_grp port CLI A raidcon get host_grp port CL2 A raidcom add hba_wwn port CLI A HP UX P hba_wwn 210000e0 8bO256f8 raidcom add hba_wwn port CL2 A HP UX S hba_wwn 21000000 8hO256f9 raidcom get hba_wwn port CLI A HP UX P raidcom get hba_wan port CL2 A HP UX S for I S i in 0 1 19 do raidcom add Idev Idev_id S i capacity 10g external_grp_id 1 1 pi raidcom get command status raidcom reset command_status for 1 S i in 0 1 19 do raidcom modify Idev Idev_id hi device_name my volume i for 1 i in 0 1 19 do raidcom modify Idev Idev_id hi mp_blade_id 2 5 raidcom get Idev Idev_id 0 cnt 20 for I S amp i in 0 1 9 do raidcom add device _grp device_grp_name grpl datah i Idev_id i Provisioning operations with CCI Add paths of External port CL4 A and the sport 50060e80 and OSfa0f36 on the side of External storage to the path group 1 Display the information of Path Group 1 Turn ON the security switches of PortCLI A cand PortCL2 A Set the host group 0 host group name HP UX P to PortCLI A and host group 0 host group name HP UX S to PortCL2 A Set the host mode HP UX to host group 0 of PortCLI A and PortCL2 A Display the host group infor
378. omatic execution mode 9 94 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom monitor pool Error code Executing Async sspi ssB2 Error message Description Executing The specified pool is the one for Thin Image or Copy on Write Snapshot Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 67 SSB codes that are returned by raidcom reallocate pool command raidcom reallocate pool Executing Error code Error message Async sspi ssB2 Description Executing The value of pool ID is out of range Executing There is not enough time after collecting performance monitor Executing Tier Reallocation cannot be started because the state of performance monitor information is not enabled Start the performance monitor again Executing Reallocation cannot be started because it is reallocating Executing Reallocation cannot be stopped because it is not reallocating Executing The operation cannot be done because it is being discarded pages Executing The operation cannot be done because the Tier is being deterred reallocation Executing The pool is not in the status of specifying the reallocation to start or stop Executing The pool ID is not installed Executing A SM for Dynamic Provisioning is not installed Executing A SM for Dynamic Tiering is not installed
379. ommand The history of performing raidcom command can be stored in syslog server by outputting it to the syslog file Since the information of what command was performed by who and when are recorded on the syslog file this is available to use for audit log Output the syslog file by using syslog service on the host OS For details refer to the host OS manual Caution A e The packet loss occurs on the syslog because the syslog uses UDP communication The log is also lost when the server to be received the syslog is down because the server does not have a function to store the data until it recovered If you want to record the same log at the client side by considering the lost of syslog at the syslog server refer to the output setting of the syslog file e This syslog files are not deleted automatically Delete unnecessary files accordingly or make run the log rotation by installing such as the logrotate service separately The conditions to support the output of syslog file The conditions to support this function are explained in the following Supported OS This function is supported only when the OS of the host is one of the following Windows is out of support e Solaris 2 5 e Solaris 10 x86 e HP UX 10 20 11 0 11 2x e AIX 4 3 e Red Hat Linux 6 0 7 0 8 0 AS ES 2 1 3 0 4 0 5 0 e AS ES 2 1 3 0 Update2 4 0 5 0 on EM64T IA641 Target command The following shows the raidcom command that is target to be output on
380. ommand Status Executing Async The program product of nondisruptive migration is not installed Get Command Status Async The external volume group exists already CMDRJE Executing The external volume group exists already Get Command Status Async Exceeded the number of mapping that can be set per 1 port Get Command Status Async The operation cannot be done because the number of path in the path group exceeds 8 Get Command Status Async The external volume cannot be added because the number of virtual volumes that can be created in the system exceeded the maximum number Get Command Status Async The specified external LU has mapped already CMDRJE Executing The port attribute is not External Get Command Status 9 22 Async The specified external storage LU is the device of not supported Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom add external_grp Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The specified external storage system is not supported Get Command Status Async The specified external volume does not support nondisruptive migration Get Command Status Async The usage capacity exceeds the license capacity of the program product CMDRJE Executing The command cannot be accept
381. ommand Control Interface User and Reference Guide e Script Shell script that automatically performs takeover process when CM detects the server failure In an HA environment a package is a group of applications that are scripted to run on the secondary host in the event of a primary host failure When using the HA software for example MC ServiceGuard the package can be transferred to the standby node as an operation executed by the system administrator see Figure 6 6 Package transfer on high availability HA software on page 6 11 Note Ifthe operation is performed when CCI and TrueCopy are being used the volume is switched from primary to secondary as if an error had occurred even though data consistency is assured When restoral of the original node occurs along with its original package group of applications it is necessary to copy the data on the secondary volume onto the primary volume this operation can take as much time as the initial copy operation for the pair In actual operation no package can be transferred when TrueCopy is being used The secondary package is switched to the primary package and vice versa when the primary volume is switched to the secondary volume Therefore the primary and secondary TrueCopy volumes should be switched depending on the package state Primaty Secondary l t Secondary Primary Legend S Standby A Active Figure 6 6 Package transfer on high availability HA softwa
382. ompares the timestamp of S JNL on each storage system RCU as far as a group configured Universal Replicator in PAIR state Once HORCM detects a matching point of the timestamp CTQ Marker on all storage systems RCU it issues an order to commit the Journal data with CTQ Marker to each storage system RCU 3 Propagating Error suspend The thread for a group on HORCM delivers the same timestamp with increments as far as a group configured Universal Replicator in PAIR state If the PSUE PFUS state detects at least one storage system then it notifies another storage system to suspend PSUS in order to keep the state consistent in the CT group Then the thread stops to deliver the timestamp and keeps monitoring its CT group with interval of HORCM_CTQM until it becomes PAIR state by next pair resync 4 Committing the Journal data inside pairsplit command The pairsplit command makes a suspending state on PAIR state and inherits to compare the timestamp of S JNL on each storage system RCU If it detects a matching point of the timestamp CTQ Marker on all storage systems RCUs then it issues an order to commit the Journal data with Q Marker to each storage system RCU and repeats it until it detects an EOM End Of Marker of CTQ Marker with the pairsplit command horcm conf CCI supports TC_Sync group across multiple storage systems but it does not allow TrueCopy Async UR group across multiple storage systems Therefore CCI ne
383. ompletes with an error The mirror consistency of the S VOL depends on its status PSUE The secondary volume is dubious PAIR The secondary volume can continue operation 3 When the fence level is never Writing to the P VOL is still enabled in the state where mirror consistency to the S VOL is lost regardless of whether the secondary volume status is updated or not Thus the secondary could have these states PSUE The secondary volume is dubious PAIR The secondary volume is substantially dubious since it can continue operation and is also dubious The P VOL status must be checked to confirm the mirroring consistency 4 When the fence level is async TrueCopy Async UR uses asynchronous transfers to ensure the sequence of write data between the P VOL and S VOL Writing to the P VOL is enabled regardless of whether the S VOL status is updated or not Thus the mirror consistency of the secondary volume is dubious similar to the Never fence e PSUE The S VOL mirroring consistency is not assured but the PSUE suspended state ensures the sequence of data for the consistency group thus data consistency is also assured during a PSUE state At a PSUE state the P VOL writes still complete and are also noted in a bitmap for future transfer Due to the use of a bitmap in the suspend state data consistency is not assured during a copy state resync PAIR If the P VOL and S VOL are both in a PAIR state mirror consistency is not
384. on page 2 31 show TrueCopy ShadowImage cascading configurations and the pairdisplay information for each configuration CCI software environment 2 29 Hitachi Command Control Interface User and Reference Guide Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradevi L CL1 D 3 0 0 30052 266 SMPL ome o oradb oradevi L CL1 D 3 0 30052 266 P VOL COPY 30053 268 oradb1 oradew11 R CL1 D 3 2 0 30053 268 P VOL COPY 30053 270 oradb2 oradev21 R CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 W oradb oradevi R CL1 D 3 2 30053 268 S VOLCOPY 266 Figure 2 20 Pairdisplay for TrueCopy on HOST1 pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq _LDEV P S Status Seg P LDEV M oradev11 L CL1 D 3 2 0 30053 268 P VOL PAIR 30053 270 oradev21 L CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 W oradevi L CL1 D 3 2 30053 268 S VOL PAIR 266 oradev1 R CL1 D 3 0 0 30052 266 SMPL oradev1 R CL1 D 3 0 30052 266 P VOL PAIR 30053 268 Figure 2 21 Pairdisplay for TrueCopy on HOST2 HORCMINST 2 30 CCI software environment Hitachi Command Control Interface User and Reference Guide pairdisplay g oradb1 m cas Group PairVol U R Port TID LU M Seq LDEV P S Status Seqgt P LDEV M oradb1 oradev11 L CL1 D 3 2 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 3 2 1 30053 2
385. on gt Displaying host group information Display host group information and confirm result of executing command raidcom get host_grp port lt port gt lt host group name gt Adding host to host group Register host to host group of the port raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt Displaying WWN information Display WWN of connection host registered to the host group and confirm the result of executing the command Provisioning operations with CCI raidcom get hba_wwn port lt port gt lt host group name gt Hitachi Command Control Interface User and Reference Guide Operation overview Creating LDEV Description Specify a parity group and create LDEV Executed command raidcom add ldev parity_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Formatting LDEV Format created LDEV raidcom initialize ldev ldev_id lt ldev gt operation lt type gt Creating LDEV nickname arbitrary Create LDEV nickname This operation is arbitrary raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Setting MP blade of LDEV Set MP blade of created LDEV raidcom modify ldev ldev_id lt ldev gt
386. on of the RAID storage system 6 36 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Note AN e pairsplit S of a Copy on Write 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 becomes R W disabled and data is discarded e Inthe PSUE state Copy on Write Snapshot does not manage differential data between the primary volume and secondary volume Controlling Volume Migration Volume Migration including external volumes must be controlled using CLI in a Data Lifecycle Management DLCM solution It is possible to support volume migration Volume Migration function and the external connection by operating the current ShadowImage and VDEV mapping of the external connection Also it is important to consider the support of Volume Migration on the compatibility based on the current CLI interface because CCI is supporting ShadowImage and the external connection For this purpose CCI makes the CLI interface that works by minimum compatible of the application by specifying the COPY mode for Volume Migration to the CLI of CCI Specifications for Volume Migration CCI must be mapped to the port for pooling of RAID in order to control the volume of the external connection Therefore the external volume needs to be mapped previously to the RAID port without connecting to the h
387. on type is not supported in this command CMDRJE Executing 2E00 0010 A Dynamic Provisioning virtual volume cannot be created because the specified LDEV number is already used Get Command Asynchrono 2E00 0013 There are not enough cache management Status us devices Get Command Asynchrono 2E00 0014 Cannot create because the specified capacity is Status us invalid CMDRJE Executing 2E00 0019 The capacity in the case of specifying a emulation type of the mainframe series must be dividable by the cylinder CMDRJE Executing 2E00 001A The capacity when 3390 V emulation type is specified must be divisible by page unit Troubleshooting 9 31 Hitachi Command Control Interface User and Reference Guide raidcom add Idev Error code Error message sey Description sync ssBi SSB2 CMDRJE Executing 2E00 001C When you specify emulation type for open system you cannot specify the size by the cylinder CMDRJE Executing 2E00 0025 A volume for online data migration cannot be Get Command Async created because the specified value of capacity Status LBA is not the maximum CMDRJE Executing 2E00 0026 The capacity must be specified because LDEVs are in the parity group or the external volume group CMDRJE Executing 2E00 0027 The capacity must be specified Get Command Async 2E00 002D The emulation type of the mainframe cannot be Status specified because the virtual volu
388. ong servers This can be verified using the raidqry command CCI software environment 2 17 Hitachi Command Control Interface User and Reference Guide 2 18 unitIDO Ser 30014 unitiID1 Ser 30015 unitiID 0 unitIDO Ser 30014 unitiID1 Ser 30015 Command device Ser 30015 unitiID 1 Figure 2 12 Configuration and unit IDs for multiple storage systems dev_name for Windows In Windows SAN environment Volume guid will be changed on every reboot under MSCS Windows 2003 if Windows finds the same signature on the command device connected with Multi Path Therefore find NEW Volume guid and change Volume guid described in the CCI configuration file Thus CCI supports the following naming format specifying Serial LDEV Port as notation of the command device only for Windows For VSP G1000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 CMD Ser ldev Port HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 A To allow more flexibility CCI allows the following format e For minimum specification Specifies to use any command device for Serial 30095 CMD 30095 If Windows has two different array models that share the same serial number fully define the serial number Idev port and host group for the CMDDEV e For under Multi Path Driver Specifies to use any port as the command device for Serial 30095 LDEV 250 CMD 30095 250
389. ool ID gt lt pool monitoring of a Dynamic Tiering naming gt operation stop pool for Dynamic Tiering 23 Instructing Perform instruction of raidcom reallocate pool reallocation of reallocation of pool for pool lt pool ID gt pool for Dynamic Tiering lt pool naming gt Dynamic operation lt type gt Tiering Script examples The following shows the script examples of virtual volume Dynamic Tiering operation 5 36 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Log on with the user ID USEROI and password PASSO Lock the resource group meta_resource raidcom login USEROI PASSO1 raidcom lock resource resource_grp_name meta_resource raidcom modify port port CL1 A secur ity Turn ON the security switch of PortCLI A switch y raidcom modify port port CL2 A secur ity _switch y raidcom add host_erp port CLI A D host_grp_name HP UX P raidcom add host_grp port CL2 A 0 host_grp_name HP UX S raidcom modify host_erp port CLI A 0 host_mode HP UX raidcom modify host_grp port CL2 A 0 host_mode HP UX raidcom get host_erp port CLI A raidcom get host_grp port CL2 A raidcom add hba_wan port CLI A HP UX P hba_wan 210000e0 8bO256f8 raidcom add hba_wan port CL2 A HP UX S hba_wan 210000e0 8bO256f9 raidcom get hba_wan port CL1 A HP UX P raidcom get hba_wan port CL2 A HP UX S sand PortCL2 A Set the ho
390. opy on Write Snapshot pair status 1 ee es 6 35 Pair status relationship to Copy on Write Snapshot commands 6 36 Controlling Volume Migration 1 0 cee ee ees 6 37 Specifications for Volume Migration 1 0 000 eee eee 6 37 Commands to control Volume Migration 0 0 cee eee ee 6 39 Relations between cc command issues and statuS 05 6 42 Restrictions for Volume Migration 0 00 es 6 43 Universal Replicator MxN configuration and control 0000 eas 6 44 OVEINVIEW si2 2025 seb ad Sader ees dS eae eVaseens poe aes OG ee lt 6 44 POUCY aca dos eranen ose eee oe tee ea e SY See a a aea es 6 44 HOr CON ay ieneec5 se acest eee bate e es be we eee ere ee Sees 6 45 Command specifications 1 0 cc es 6 46 pairdisplay command 0ise0seeeseesecee kes deneavavaesdawed 6 46 pairsplit command 2 2n isin ok hwe ea baa les eos eee Sue sas ale ne 6 47 Notice on system operation 0 0 es 6 50 Configuration examples 0 0 ce ees 6 52 Remote volume discovery 0c eee eee ees 6 55 Discovering a remote volume 2 00 cee eee es 6 56 7 Data protection operations with CCI 2 000000 eae 7 1 Data protection operationS s sasssa namana anaa 7 2 Data Retention Utility 2 2s ssas aaaea 7 2 Restrictions on Data Retention Utility volumes 00000 7 3 Database Validator 0 0 ccc ees 7 3 Restrictions on Database Validator cece ee es 7 4
391. or 1 MMi in C0 1 9 do C raidcom add Jun port CL1i A HP US P Idewv_id Ahi 1 raidcom get lun port CLi A HP UX P raidcom unlock resource resource grp name meta_resour ce raidcom get resource raidcom logout pLog in with the User I0 USERO1 and Passuard PASSO pLock the resource group meta_resource 2 Create each 10 of 483078 cylinder LOEY to Parity grp id 1 1 LOEW 0 to 3 Execute Wuick format to LOEW O to 9 Give a nickname to LOEW O to 49 pmy_va lume 0 to 3 z5et to 2 the MP blade ID of LOEY 0 to 3 2 Display the information of LDEV O ta 9CInternal YOLI Give the device name data O to 9 to the LOEVIO to 9 and add it to Device group name serpl datad to 9 iUisplay the device group information gre Create a copy group foray by the device group gt Carel Fy Display the copy group information Defining paths of LOEW 0 to 5 to Port shost group HP Ux P SLU number is given automat ically CLI A Display the path information that is set to sPortCLi A host group HP Us P iUnlock the resource group meta_resource Display the resource group infor mat ian Log out Figure 5 2 Script examples of internal volume Mainframe volume operation Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Script examples The following shows script examples for internal open system volume operations raidcom login USERO PASSO raidcom lock re
392. or HORCM instance 0 e Example for adding HORCMO svcexe S HORCMO A C HORCM tool svcexe exe o for deleting HORCMO svcexe S HORCMO D Starting up CCI Hitachi Command Control Interface User and Reference Guide o for starting HORCMO 1 make a C HORCM tool HORCMO_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 HORCMO Performing Additional Configuration Tasks 1 Registering the CCI HORCM instance as a service The system administrator must add the CCI instance using the following command C HORCM tool gt svcexe S HORCMO A C HORCM tool svcexe exe Customizing a sample script file The system administrator must customize the sample script file HORCMO_run txt according to the CCI instance For details see the descriptions in the HORCMO_run txt file Setting the user account The system administrator must set the user account for the CCI administrator as needed When using the GUI use Administrative Tools Services Select HORCMO Logon When using the CUI use sc config command as follows C HORCM tool gt sc config HORCMO 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 EVERYCL
393. or example 1 or 2 specifies the Journal ID If JID Journal ID is specified on horcm conf as mentioned above then the paircreate command need not specify Journal ID jp lt jid gt js lt jid gt option If JID Journal ID is not specified on horcm conf then Journal ID jp lt jid gt js lt jid gt option of the paircreate command is used Command specifications CCI does not change the command options for supporting Universal Replicator MXN Open However the output of the command is added so that the command can display the CT group and Q Marker for each storage system because the CT group and Q Marker are managed on each storage system pairdisplay command 6 46 The output of pairdisplay v ctg and pairdisplay v jnl t are supported so that the option can display CT group information for each storage system Following is an example for UR 2x2 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide pairdisplay g ora v ctg CTG P S RT m Status AP U 000 P VOL PAIR 000 S VOL PAIR 000 P VOL PAIR 000 S VOL PAIR 1 1 1 1 pairdisplay g ora JID MU CTG JNLS Num LDEV ool 1 0 PJNN 2 5376 002 1 0o SINN 2 5378 ool 1 QO PINN 13 12388 002 1 QO SINN 16 12544 pairdisplay g JID MU CTG JNLS DOW PBW APW 001 1 60 300 002 1 60 300 001 1 60 300 002 1 60 300 0 PJNN 40 0 SJNN 40 0 PJNN 40 0 SJNN 40 AP 1 1
394. or is detected by the Context Checking Check if the operation by the command executes a proper procedures and has the consistency or not EX_EACCES Access denied with Lock Unlock The resource that you specified to lock or unlock has already been used by another user Check if the specified resource is used by such as Device Manager Storage Navigator or not EX_ENAUTH Authentication failed with User User authentication failed at the authentication command device Check the user ID and password EW_INVARG Invalid argument Invalid option or an argument of the option User h option to check the correct option and specify it EW_INVOPA Invalid option argument Invalid argument of an option Use h option to check the correct option and use it EW_INVOPT Invalid option Invalid option Troubleshooting Use h option to check the correct option and use it Hitachi Command Control Interface User and Reference Guide 9 15 Error code EW_LNGARG Error message Argument too long Condition The number of character for action object option or argument of option exceeded the maximum Recommended action Specify the number of characters of action object option an argument of option or the total number of characters are to be appropriate number of characters EW_MAXARG Maximum argument The total number of option or
395. orage Specifying the SLPR Protection Facility When you want to access certain SLPRs on a single Host use the CCI protection facility so that the Host can access multiple SLPRs through a single command device The following outline reviews the setup tasks for the SLPR protection facility 1 Setting SLPR on the command device The command device has an SLPR number and an associated bitmap so you can set multiple SLPRs You accomplish this by sharing a command device using ports connected to different SLPRs by setting the command device through SLPR 0 called Storage Administrator on Storage Navigator For example if the command device is shared with the port on SLPR 1 and SLPR 2 then the command device will automatically set the bitmap corresponding to SLPR 1 and SLPR 2 2 Testing SLPR CCI verifies whether or not the command device can access a target within SLPR So if the command device belongs to SLPR 0 or CCI has no SLPR function then the SLPR protection is ignored However if the command device is shared with the port on SLPR 1 and SLPR 2 CCI allows you to operate the volume on SLPR 1 and SLPR 2 3 Rejecting commands If access is denied on the specified port or target volume CCI rejects the following commands and outputs an error code EX_ESPERM Examples of using CCI commands 8 17 Hitachi Command Control Interface User and Reference Guide o horctakeover paircurchk paircreate pairsplit pairresync pairvol
396. orage machine Provisioning operations with CCI raidcom delete resource resource name lt resource group name gt Hitachi Command Control Interface User and Reference Guide Data replication operations with CCI This chapter describes data replication operations with CCI About data replication operations O Features of paired volumes Using CCI with ShadowImage and TrueCopy O Using CCI with Thin Image O Using CCI with global active device ShadowImage operations O TrueCopy operations TrueCopy ShadowImage and Universal Replicator operations O Copy on Write Snapshot operations Controlling Volume Migration O Universal Replicator MxN configuration and control O Remote volume discovery Data replication operations with CCI 6 1 Hitachi Command Control Interface User and Reference Guide About data replication operations The data replication features of the RAID storage systems include e Local replication o ShadowImage o ShadowImage for Mainframe o Thin Image o Copy on Write Snapshot e Remote replication o TrueCopy o TrueCopy for Mainframe o Universal Replicator o Universal Replicator for Mainframe o global active device e Mainframe replication o Compatible XRC o Compatible FlashCopy V2 o Business Continuity Manager For detailed information about any of these features see the applicable user guide for example Hitachi ShadowImage User Guide Features
397. ost Following is an execution example of the volume migration executed for LDEV 18 A Command for volume migration Host RM INST1 Port for pooling After copied swaps the mapping for LDEV Figure 6 14 Volume Migration configurations 1 Command specification Data replication operations with CCI 6 37 Hitachi Command Control Interface User and Reference Guide 6 38 CCI operates the volume migration by specifying to the horcm conf as same SI and TC because the volume migration using CCI is necessary to be defined the mapping for the target volume MU of SMPL as SI that is not used because SI is used for Volume Migration operation An original volume for the migration is defined as P VOL A target volume for the migration is defined as S VOL In other words an original volume is migrated from P VOL to S VOL and the mapping between LDEV and VDEV is swapped after copied 2 Mapping specification The mapping between LUN and LDEV is maintained for the replying of SCSI Inquiry in order to make recognize as identical LUN through the host after mapping changes The way to know whether the mapping is changed or not is possible to use fe option of pairdisplay and or raidscan command that shows the connection for the external volumes Also LU of the external connection and LU of RAID Group intermingle on the port for pooling but can confirm this with the above option of the raidscan command 3 Group op
398. ost to host group of the port raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt Displaying WWN information Display WWN of connection host registered to the host group and confirm the result of executing the command raidcom get hba_wwn port lt port gt lt host group name gt Creating LDEV Specify a parity group and create LDEV raidcom add ldev parity_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Formatting LDEV Format created LDEV raidcom initialize ldev ldev_id lt ldev gt operation lt type gt Creating LDEV nickname arbitrary Create nickname for created LDEV This operation is arbitrary raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt Setting MP blade of LDEV Set MP blade of created LDEV raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Displaying LDEV information Display information of created LDEV and confirm the result of executing the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt Creating LU path Specify port map LDEV to LUN and create an LU path raidcom add lun port lt port gt lt host group name gt ldev_id lt ldev gt lun_id lt lun gt Displaying LU path i
399. ot 46 Oct 27 17 19 horcc_raidmanager conf drwxr xr x 3 root root 4096 Oct 27 17 19 tmplog HORCM log horcc_HOST log file COMMAND NORMAL EUserId for HORC root 0 Tue Nov 1 12 21 53 2005 CMDLINE pairvolchk ss g URA 12 21 54 2d27 10090 pairvolchk exit 32 COMMAND NORMAL EUserId for HORC root 0 Thu Oct 27 17 36 32 2005 CMDLINE raidgqry 1 17 36 32 3d83c 17539 raidqry exit 0 COMMAND ERROR EUserId for HORC root 0 Thu Oct 27 17 31 28 2005 CMDLINE pairdisplay g UR 17 31 28 9a206 17514 ERROR cm_sndrcev re lt 0 from HORCM 17 31 28 9b0a3 17514 pairdisplay exit 239 EX ENOGRP No such group Cause The group name which was designated or the device name doesn t exist in the configuration file or the network address for remote communication doesn t exist Action Please confirm if the group name exists in the configuration file of the local and remote host HORCM log horcc_HOST conf file CCI software environment Hitachi Command Control Interface User and Reference Guide For Example HORCC LOGSZ 2048 The masking variable This variable is used to disable the logging by the command and exit code For masking below log pairvolchk returned 32 status is SVOL COPY COMMAND NORMAL EUserId for HORC root 0 Tue Nov 1 12 21 53 2005 CMDLINE pairvolchk ss g URA 12 21 54 2d27 10090 pairvolchk exit 32 pairvolchk 32 pairvolchk 22 Logging raidcom c
400. ot Initiator MCU Get Command Status Async Command cannot be executed because the RCU identification code of a path is invalid Get Command Status Async Command cannot be executed because the serial number is not unified in the specified path CMDRJE Executing The command cannot be accepted because the DKC is busy After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 47 SSB codes that are returned by raidcom add rcu_path command raidcom add rcu_path Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description CU of RCU exceeds the effective value CMDRJE Executing Invalid product ID or path registration ID Get Command Status Async Troubleshooting Command cannot be executed because the parameter of specified RCU is invalid 9 79 Hitachi Command Control Interface User and Reference Guide raidcom add rcu_path Error code Error message P Description sync ssBi SSB2 Get Command Async 2E00 3009 Command cannot be executed because all the CU Status numbers in the RCU is not unified at the path that is specifi
401. ou specify 0 1 2 for the MU your operation authority is limited on the LUs for the local copy program products ShadowImage ShadowImage for Mainframe and Copy on Write Snapshot If you specify hO h1 or h2 for the MU your operation authority is limited on the LUs for the remote copy TrueCopy TrueCopy for Mainframe TrueCopy Async Universal Replicator and Universal Replicator for Mainframe operations If you specify nothing for the MU you have the operation authority on MU 0 for the local copy and the remote copy operations Target commands for protection The following commands are controlled by the Data Protection Facility horctakeover paircurchk paircreate pairsplit pairresync pairvolchk pairevtwait pairsyncwait raidvchkset raidvchkdsp pairdisplay When the command is issued to non permitted volumes RAID Manager rejects the request with error code EX_ENPERM pairdisplay is not included e The pairdisplay command shows all volumes so that you can confirm non permitted volumes Non permitted volumes are shown without LDEV information As shown below the LDEV information is CLI is pairdisplay g oradb Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L CL1 D 3 0 0 35013 oradb oradev1 R CL1 D 3 1 0 35013 e The raidscan command shows all volumes same as current specification because it does not need HORCM_
402. ource resource name lt resource are allocated to groups In other words this group name gt ldev_id resource operation allocates lt ldev gt port lt port gt groups resources to resource group port lt port gt lt host group meta_resource name gt parity_grp_id lt gno sgno gt external grp_id lt gno sgno gt Confirming Confirms that resources are raidcom get resource resource not allocated to resource deletions groups that you want to delete At that time allocation of resources to the resource group meta_resource must be finished Allocating Specifies resources that are raidcom add resource resources to allocated to meta_resource resource name lt resource resource resource group and group name gt ldev_id groups allocates resources to lt ldev gt port lt port gt resource groups port lt port gt lt host group name gt parity_grp_id lt gno sgno gt external _grp_id lt gno sgno gt Displaying Displays resource group raidcom get resource resource group information and confirms information results of command executions LDEVs that are allocated to journals or pools must be migrated by users We recommend that you register LDEVs that are allocated to journals or pools as device groups and then operate after specifying them by the device groups Execution example The following shows the execution example of registering LDEVs to the pool as device
403. overed using the pairresyne command which merges the S VOL bitmap with the P VOL bitmap Figure 6 11 TrueCopy Async suspension condition on page 6 31 shows this situation on the secondary side 6 30 Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide RCU secondary Asynchronous transfer FIFO sidefile nwn a ESCON fibre failure Secondary volume Secondary volume Figure 6 11 TrueCopy Async suspension condition BITMAP TrueCopy TrueCopy Async and Universal Replicator fence level settings TrueCopy volume pairs are assigned a fence level for write I Os to ensure mirroring consistency of critical volumes When the secondary volume takes over from the primary volume the takeover action is determined according to the pair status and fence level of the corresponding secondary volume Table 6 9 Relationship between TrueCo air statuses and fence levels on page 6 31 shows the relationship between TrueCopy pair statuses and fence levels e Mirror consistency Identity and sequence of data is assured via error notification after an I O completion e Data consistency Sequence of data is assured in I O order based on host Table 6 9 Relationship between TrueCopy pair statuses and fence levels TrueCopy pair status of volume Fence level and write response Write response Primary volume Secondary volume Data 1 Status 2 Never 3 Async 4
404. overy function 0 ce ees 8 3 Mountvol attached to Windows 2012 2008 2003 2000 systems 8 5 System buffer flushing function ssas assas c eee es 8 6 Special facilities for Windows systeMS 00 ee ees 8 9 Signature changing facility for Windows systems 000000 8 9 GPT disk for Windows 65s20s ec 05 se Rees Sy bau ee aerwe tees 8 11 Directory mount facility for Windows systems 00000 eee 8 12 Host group control 2 165 s se ice49s eke een O454ee essed bens bees 8 14 Specifying a host group 2 226 se nea ee ee Ue ee eee ee bee ee ee 8 14 Commands and options including a host group eee eens 8 15 Using CCI SLPR SGcunty 12h lt t44wewile She tena d east dhe cdaw dees 8 16 Specifying the SLPR Protection Facility 0 00 cea eee eee 8 17 SLPR configuration examples 0 000 eee es 8 18 9 Troubleshooting oa ee betwee dade baad Oboe Ob bd ed de ee OC 9 1 General troubleshooting 0000 cece eee ees 9 2 Operational notes and restrictions for CCI operations 00005 9 3 Error messages and error codes 1 ce eee 9 6 System log MESSAGES 1 ee es 9 6 Command error messages 1 usasa aaa 9 8 Generic error codes horctakeover and pair commands 9 16 Generic error codes raidscan raidqry raidar horcctl 9 17 Specific error GOdES 2 4 cs4 gees ese vedo Sb Gee de esas aeeS ne eases 9 18 SSB COGS i 2tesen te tese se a teu wh
405. owing table lists and describes CCI functions available on each storage system Table 1 1 Available CCI functions on each storage system Storage system Function TagmaStore USP NSC USP V VM VSP HUS VM Local copy open Local copy mainframe Remote copy open Remote copy mainframe Data protection VSS configuration SRM SRA 1 2 Overview Hitachi Command Control Interface User and Reference Guide Storage system RN n USP V VM VSP HUSVM Provisioning raidcom No No Yes Yes Yes Out of band method No No Yes Yes Yes User authentication No No Yes Yes Yes LDEV nickname No No Yes Yes Yes LDEV group No No Yes Yes Yes Resource group No No Yes Yes Yes Resource lock No No Yes Yes Yes If DKCMAIN Microcode version of the VSP storage system is 70 03 3x xx xx or later the operation of TrueCopy for Mainframe Universal Replicator for Mainframe and ShadowImage for Mainframe can be performed from Command Control Interface Provisioning function By executing a configuration setting command raidcom command from CCI the provisioning function such as setting commands or creating LDEVs can be done For the information about the configuration setting command raidcom command see Overview of the configuration setting command on page 5 2 Asynchronous command processing Within the configuration setting commands raidcom commands using asyn
406. p lt port gt fe fe This option is used to display the serial and LDEV of the external LUNs only mapped to the LDEV If the external LUN mapped to the LDEV on a specified port does not exist then this option will do nothing Also if this option is specified f f g d option is not allowed Data replication operations with CCI 6 39 Hitachi Command Control Interface User and Reference Guide 6 40 Display example raidscan p cll a 0 fe CLI PORTH ALPA C TID LU Seq Num LDEV P S Status Fence E Seq E LDEV CL1 A 0 ef 0 0 8 62496 1 19 SMPL 30053 30 CL1 A 0 ef 0 0 9 62496 1 21 SMPL 30053 32 CL1 A 0 ef 0 0 10 62496 1 22 SMPL 30053 33 E Seq Displays the production serial number of the external LUN E LDEV Displays the LDEV of the external LUN 3 Command for confirming the status It is possible to confirm the status for Volume Migration by using fe option of the pairdisplay command pairdisplay g lt group gt fe fe This option is used to display the serial and LDEV of the external LUNs mapped to the LDEV and additional information for the pair volume This option displays the information above by adding to last column and then ignores the format of 80 column This option is invalid if the cascade options m all m cas are specified Display example Before execution of Volume Migration command pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M
407. pair of Status ShadowImage Thin Image Copy on Write Snapshot Volume Migration or a relationship of Compatible FlashCopy V2 Compatible Software for IBM FlashCopy SE Get Command Async 2E10 0001 The specified LDEV is used for a pair of TrueCopy Status or Universal Replicator Get Command Async 2E10 0003 The specified LDEV is used as a Compatible Status FlashCopy V2 relationship Get Command Async 2E10 0004 The specified LDEV is used as a Thin Image or Status Copy on Write Snapshot pair Get Command Async 2E10 0008 The specified LDEV is used as a system disk Status CMDRJE Executing 2E10 0011 LDEV is not installed or LDEV is not in the state of Normal Get Command Async 2E10 0012 The specified LDEV is used at the concurrent copy Status or XRC Get Command Async 2E10 0062 The specified LDEV is used as the primary volume Status of an GAD pair Get Command Async 2E10 0063 The specified LDEV is used as the secondary Status volume of an GAD pair Get Command Async 2E11 0009 The operation cannot be done because LDEV is Status now expanding Get Command Async 2E11 001E The operation cannot be done because the virtual Status disk space is blocked CMDRJE Executing 2E11 0053 The specified LDEV is used in another operation CMDRJE Executing 2E11 0153 The parity group or the external group to which the specified LDEV belongs is used in another operation Get Command Async 2E11 8004 The operation cannot be done because the Statu
408. pairs Splitting the pairs using the group assures data consistency at the time the storage system receives the request Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide e A snapshot group is a group of only Thin Image pairs Use consistency or snapshot groups to perform Thin Image tasks on all of the pairs within the group You define Thin Image pairs to a snapshot group when you create the pairs consistency group you can only specify one consistency group for a group Note When you use the CCI to define multiple Thin Image pairs in a A defined in the CCI configuration definition file The configuration definition file for CCI 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 using the CCI configuration definition file and the pair is already defined in a consistency group defines the pair in the same consistency group even if you try to create a new pair and assign it to a different consistency group For details about Hitachi Thin Image see the Hitachi Thin Image User Guide for your storage system Using CCI with global active device The CCI software is installed on the host servers and used for global active device operations The CCI command devices and CCI configuration definition files are required for global active device operations You can execute CCI commands for global active device
409. path_grp lt path group gt external_grp_ id lt gno sgno gt port lt port gt external_wwn lt wwn strings gt lun_id lt lun gt emulation lt emulation type gt Disconnect the connection for external volume raidcom disconnect external_grp external_grp_ id lt gno sgno gt ldev_id lt ldev gt Check the connection for external volume and restore it raidcom check _ext_ storage external _grp external_grp_ id lt gno sgno gt ldev_id lt ldev gt Unmap external volume raidcom delete external grp external_grp_id lt gno sgno gt Display mapped external volume information raidcom get external _grp lt gno sgno gt external_grp_id Create LDEV in external volume raidcom add ldev external_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt Display LDEV information created in external volume raidcom get ldev ldev_id lt ldev gt cnt lt count gt grp_opt lt group option gt device_ grp name lt device group name gt lt device name gt key lt keyword gt Change cache mode of external volume raidcom modify external _grp external_grp_id lt gno sgno gt cache mode lt y n gt Control cache write of external volume raidcom modify external _grp external_grp_id lt gno sgno gt cache_inflow lt y n gt Modify o
410. paths of LDEV 0 to 9 to Port raidcom add lun port CL1 A HP UX P Idev_id CLI A host group HP UX P Si Defining path of LDEV 10 to 19 to Port CL2 A host group HP UX S for I i in 10 1 19 do Give an LU number automatically raidcom add lun port CL2 A HP UX S Idev_id Shi raidcom get lun port CLI A HP UX P Display the path information that is set raidcom get lun port CL2 A HP UX S ito PortCLI A host group HP UX P and PortCL2 A host group HP UX S raidcom unlock resource resource_grp_name Unlock the resource group meta_resource meta_resource raidcom get resource Display the resource group information raidcom logout Log out Figure 5 15 Script Examples of External Volume Operation 3 3 Virtual Partition Manager operations Virtual Partition Manager operations using CCI include migrating LDEVs parity groups and external volume groups to other CLPRs e For information about Virtual Partition Manager operations including important warnings and restrictions see the Hitachi Virtual Partition Manager User Guide for USP V VM or the Performance Guide for VSP e For details about the CCI commands for Virtual Partition Manager operations see the Command Control Interface Command Reference Performing Virtual Partition Manager operations The following table shows the procedure for migrating LDEVs parity groups and external volume groups to other CLPRs Operation a j step Glertew Des
411. pecified LDEV number or the LDEV number for the virtual volume is out of the range Error message Description Executing The specified LDEV for the virtual storage machine is not defined in the specified LDEV Executing The specified LDEV is used by the TrueCopy pair or the Universal Replicator pair Executing You cannot execute the command because the processing by the other software Device Manager Storage Navigator or SVP and so on is in progress Executing The Resource Partition Manager is not installed Executing The information of the virtual storage machine is not set in the specified resource Executing You cannot operate the LDEV that has the LU path definition Executing The specified LDEV is used as a quorum disk Executing The specified LDEV cannot be operated because it is the external volume for the online data migration Executing The specified volume cannot be operated because it is the mainframe volume Executing An internal error occurred Call Hitachi Data Systems Support Center Executing The specified operation cannot be performed because it is not supported Troubleshooting 9 99 Hitachi Command Control Interface User and Reference Guide Table 9 74 SSB codes that are returned by raidcom modify resource command raidcom modify resource Executing Error code Error message Async CMDRJE Executing 2EF3 2202 Description The
412. peration Dynamic Tiering 2 3 5 38 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide raidcom get Idev Idev_id 10 cnt 20 for I S i in 10 1 19 do raidcom add device_grp device_grp_name erp datah i Idev_id bi pi for I i in 20 1 29 do raidcom add device_grp device_grp_name grp2 datahsi Idev_id hi raidcom get command_status raidcom reset command_status raidcom get device_grp device_grp_name grpi raidcom get device_grp device_grp_name grp2 raidcom add copy_grp copy_grp_name ora erpl grp2 raidcom get command_status raidcom reset command status raidcom get copy_erp for I S i in 10 1 19 do raidcom add lun port CL1 A HP UX P Idev_id hi for I S i in 20 1 29 do raidcom add lun port CL2 A HP UX S Idev_id hi raidcom get lun port CL1 A HP UX P raidcom get lun port CL2 A HP UX S raidcom unlock resource resource_grp_name meta_resource raidcom get resource raidcom monitor pool pool 1 operation start raidcom monitor pool pool 1 operation stop raidcom reallocate pool pool 1 operation start raidcom logout Display the information of VVOL 10 to 29 virtual VOL Give the device name data to 19 to VVOL 710 to 29 and add it to Device group name zgrpl data0 to 9 and grp2 datal0 to 19 Display the device group information grpi zand grp2 Create a copy group lora at the device group grpl
413. ple of masking pairvolchk on a script Export HORCC_LOGSZ 0 Pairvolchk g xxx s Unset HORCC_LOGSZ The masking feature is to enable the tracing without changing their scripts And this feature is available for all CCI commands except ingqraid Or EX xxx error code CCI software environment 2 39 Hitachi Command Control Interface User and Reference Guide 2 40 For example if you want to mask pairvolchk returns 22 and raidqry specify the following pairvolchk 22 raidqry 0 You can track script performance and then decide to mask by auditing the command logging file as needed Relationship between an environment variable and horcc_HOST conf Logging depends on the HORCC_LOGSZ environment variable and or the HORCC_HOST conf file as shown below HORCC_LOGSZ HORCC_HOST conf Performing value Any does not matter Tracing within this APP NO tracing within this APP Unspecified HORCC_LOGSZ valu Global tracing within this CCI instance e HORCC_LOGSZ 0 NO global tracing within this CCI instance Unspecified or Use the default value 0 The same as nonexistent the current logging for only command error Examples for execution HORCM log directory root raidmanager log9 ls 1 total 16 drwxr xr x 3 root root 4096 Oct 27 17 33 curlog rw r r 1 root root 3936 Oct 27 17 36 horcc_raidmanager log rw r r 1 root root 2097452 Oct 27 17 29 horcc_raidmanager oldlog rw r r 1 root ro
414. pports Virtual Storage Platform or later Define a configuration definition file Define HORCM_LDEV or HORCM_ DEV of the configuration definition files of the primary and secondary volumes For definition details see Configuration definition file on page 2 12 A device name is a name given to an LDEV in each device group This is equivalent to the dev_name definition of HORCM_DEV A device name is not required but it is convenient to use to specify device group or device name instead of LDEV number However to create a pool or a journal specifying LDEV number is required The LDEVs that have the same device name are recognized as a pair in the primary and secondary device group Therefore make match the device name for the LDEV to be a pair Also the number of LDEVs in the device group must be the same at the primary and secondary sides Pairs are operated in the ascending sequence of the LDEV numbers If there is no corresponding device name of LDEV in the device group to be paired an error might be occurred on the pair operation Read operations and command device settings When grouping LDEVs if HORCM_LDEVG on the primary side and secondary side is not defined the read operation of CCI is different depending on the command device settings The following table shows the details CCI functions 3 29 Hitachi Command Control Interface User and Reference Guide Table 3 10 Reading of command device setting and group information
415. r EX_ENQVOL Unmatched volume status within the group The volume attribute or the fence level within a group is not identical Troubleshooting Confirm status using the pairdisplay command Make sure all volumes in the group have the same fence level and volume attributes Hitachi Command Control Interface User and Reference Guide Error code EX_EVOLCE Error message Pair Volume combination error Condition Combination of a volume is unsuitable between the remote and local host Recommended action Confirm volume status using the pairdisplay command and change the combination of volumes properly EX_EWSUSE Pair suspended at WAIT state Detected a suspended status PSUE for the paired volume before it made it to the designated status Please issue the pairresync command manually to the identified failed paired volume to try to recover it If the problem persists contact the Hitachi Data Systems Support Center EX_EWSTOT Timeout waiting for specified status Detected a time out before it made it to the designated status Please increase the value of the timeout using the t option For details refer to the troubleshooting information in the relevant user document EX_EWSLTO Timeout waiting for specified status on the local host Timeout error because the remote did not notify about expected status in time Please confirm that HORC
416. r occurred Call Hitachi Data Systems Support Center CMDRJE Executing Troubleshooting The specified parameter is invalid Check the Command Control Interface Command Reference 9 39 Hitachi Command Control Interface User and Reference Guide Table 9 19 SSB codes that are returned by raidcom modify journal command raidcom modify journal Executing Error message g Async Executing Error code SSB1 SSB2 Description The specified volume capacity is too small Executing The specified path block watch time exceeds the range Executing The specified MP Blade ID is invalid Executing The specified volume is not installed or cannot be used Executing The specified operation failed because the journal or mirror is not in the operable status Executing The specified operation failed because the mirror of journal is not in the operable status Executing The specified MP Blade is blocked Executing The operation cannot be done because it is in the state of start up Executing The specified journal ID is not registered Executing The operation failed because the specified journal is not registered Executing The journal volume cannot be added or the journal cannot be added to the extended CT group due to insufficient capacity of the shared memory SM Get Command Async Status The specified volume cannot be us
417. rate in the range of resource group 20 and shared ports NG Operation Nothing is displayed or the operation authority error authority error OK OK OK Can operate only in the range of resource group 20 Legend OK Operable NG Inoperable As shown in the table above the relation among users command devices and operations of resource groups are the following e The range that can be operated by command device 0 CMO or Out of Band is the shared range AND of resource groups that are allocated to each user and all resource groups e The range that can be operated by command device 10 CM10 is the shared range AND of resource groups that are allocated to each user and resource group 10 that the command devices are allocated Therefore in the range of resource group 10 can be operated The following shows the example of the case that the execution results of the commands change by the case of having or not having the authority of the operated resources specifies only the objects or specifies to the parameters When user has the authority using CL1 A CL3 A and CL5 A ports and CL1 A CL2 A CL3 A CL4 A and CL5 A ports are implemented in the system executes the following command When only the objects are specified raidcom get port CCI functions 3 13 Hitachi Command Control Interface User and Reference Guide The execution results of CL1 A CL3 A and CL5 A are displayed
418. rder to the control command device was rejected It was rejected due to SKEY 0x05 ASC 0x26 ASCQ 0x00 SSB 0x2E11 0x2205 on Serial 64568 Result of get_command_status Serial 200414 HANDLE SSBi SSB2 00c4 ERR_CNT 0 Description Rows for the returned values of a command Display example It exit 0 may vary depending on the host OS Logs when the normal operation Aug 24 12 24 37 raidmanager raidcom PID 06864 COMMAND NORMAL EUserID for HORC Aug 24 12 24 37 raidmanager raidcom root 0 Fri Aug 24 12 24 36 2012 PID 06864 CMDLINE raidcom get command_status ldev_id 0001 Aug 24 12 24 37 Hitachi Command raidmanager raidcom PID 06864 raidcom HANDLE 2 43 CCI software environment Control Interface User and Reference Guide SSB1 SSB2 ERR_CNT Serial Description Aug 24 12 24 37 raidmanager raidcom PID 06864 raidcom 00c3 0 64568 Aug 24 12 24 37 raidmanager raidcom PID 06864 raidcom exit 0 e Logs when the abnormal operation Aug 24 12 24 27 raidmanager raidcom PID 06857 COMMAND ERROR EUserID for HORC root 0 Fri Aug 24 12 24 19 2012 Aug 24 12 24 27 raidmanager raidcom PID 06857 CMDLINE raidcom get command_status Aug 24 12 24 27 raidmanager raidcom PID 06857 raidcom User for Serial 64568 user1234 Aug 24 12 24 27 raidmanager raidcom PID 06857 raidcom User authentication has failed on Serial 64568 Aug 24 12 24 27 raidmanager raidcom PID 06857
419. re The swap option of the takeover command allows swapping of the primary and secondary volume designations so if the primary and secondary volume are switched due to a server error or package transfer pair operation can be continued using the reversed volumes When control is handed back over to the original node swapping the volume designations again eliminates the need of copying them In addition the takeover command has the option to allow the secondary volume to be logically separated for the purpose of recovery from a disaster at the original operating site The takeover command has four functions designed for HA software operation Takeoverswitch swap takeover SVOL takeover and PVOL takeover This command is not available for ShadowImage Data replication operations with CCI 6 11 Hitachi Command Control Interface User and Reference Guide Takeover switch function The control scripts activated by HA software are used by all nodes of a cluster in exactly the same manner so they have no discrimination between primary and secondary pair volumes they just know the near and far disk in a pair Thus the takeover command when activated by a control script must check the combination of attributes of volumes possessed by the local and remote nodes and determine the proper takeover action The table below shows the takeover actions Table 6 1 Near Local and Far Remote Volume Attributes and Takeover Actions Local node Takeover node
420. re available Out of Band operation In Band operation Figure 1 1 Overview of out of band and in band operations The following table provides a comparison of in band and out of band operations Table 1 3 Comparison of in band and out of band operations Command Specification In band issued from the Replication The required or not required of user authentication is host as if it were a command changed by the setting of user authentication tor the command device Provisioning User authentication is required Out of band communicating Replication User authentication is required directly with the SVP Provisioning User authentication is required 1 6 Overview Hitachi Command Control Interface User and Reference Guide User authentication To enable user authentication it is required to enable the user authentication mode for the command device of CCI A virtual command device always enables the user authentication mode If the authentication is disabled provisioning commands and out of band commands cannot be executed The user information to be used user ID and password are the same as those used for Storage Navigator and the SVP LDEV nickname function A unique nickname with up to 32 characters can be given to an LDEV LDEV grouping function In CCI before supporting Hitachi Virtual Storage Platform it was required to define a copy group for the configuration definition file on eac
421. re logical volume LV is exposed That is if a user takes an unmirrored HARD enabled LV then makes it mirrored on the fly without HARD enabling all sides of the mirror that entire LV is exposed to data corruption LVM bad block relocation is not allowed on PVs that are HARD enabled e Oracle and LVM VxVM on HA Cluster Server Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide o If HA Cluster software writes to LVM metadata at regular intervals to confirm whether its disks are available or not change the check area which is set for the target LU except management area by using the vs lt bsize gt SLBA ELBA option Protection parameters and operations The RAID storage systems have protection checking parameters for each LU and these parameters are set through CCI and its command device CCI supports the following commands to set and verify the parameters for protection checking for each LU e raidvchkset Sets the protection checking parameter for the specified volumes e raidvchkdsp Shows the protection checking parameter for the specified volumes based on the CCI configuration definition file e raidvchkscan This command has three different uses depending on the options used with the command o Shows the fibre port target ID LDEV and validation checking parameters for the specified volumes based on the raidscan command o Shows the journal volume list setting a
422. re returned by raidcom add dp_pool command raidcom add dp_pool Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description LDEV number is out of rage CMDRJE Executing The value of pool ID is out of range CMDRJE Executing The type of pool is invalid CMDRJE Executing The maximum reserve ratio of V VOL is out of range CMDRJE Executing The threshold of the specified High water mark is out of range CMDRJE Executing The operation cannot be done because the specified threshold of Warning is larger than the threshold of the specified High water mark Get Command Status Async The specified LDEV is in the state of blocked Get Command Status Async The operation cannot be done because a SATA E drive in the state of quick formatting is in the specified LDEV CMDRJE Executing The specified LDEV is in the state of blocked or not installed Get Command Status Async The pool cannot be created because there are not enough resources VDEV depending on cache management devices Get Command Status Async The operation cannot be performed because the pool volume is being deleted Get Command Status Async The specified operation is not supported in the current microcode version CMDRJE Get Command Status Executing Async The pool is not in the status where the poo
423. red by the operation of disconnecting the external volume Call Hitachi Data Systems Support Center Executing An internal error occurred by the operation of external volume Call Hitachi Data Systems Support Center Table 9 12 SSB codes that are returned by raidcom modify external_grp command raidcom modify external_grp Executing Error code Error message Async sspi ssB2 Description Executing The external volume group is not in the effective range Executing The specified value of the load balance mode is invalid Executing The specified value of the ALUA mode is invalid Executing MP Blade ID is not in the effective range Executing The operation cannot be performed because the volume used for data migration is reserved from the host Executing The specified MP Blade is blocked Executing The attribute cannot be changed because Volume Migration is being executed Executing The load balance mode cannot be changed because the alternative path mode is set to Single Executing The load balance mode cannot be changed because microcodes of multiple versions are in the storage system Executing There is no external volume group Executing The specified MP Blade is not installed Executing The attribute cannot be changed because the external volume is used as a ShadowImage pair volume Executing The external volume is used as a Universal Rep
424. red logical volume names Each group name is unique and typically 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 remote server e dev_group This parameter is the same as HORCM_DEV parameter e dev_name This parameter is the same as HORCM_DEV parameter e MU This parameter is the same as HORCM_DEV parameter e Serial This parameter is used to specify the serial number of RAID box For VSP G1000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 e CU LDEV LDEV This parameter is used to describe the LDEV number in the RAID storage system and supports three types of format as LDEV dev_group dev_name Serial CU LDEV LDEV MU oradb dev1 30095 02 40 0 oradb dev2 30095 02 41 0 o Specifying CU LDEV in hex used by SVP or Web console Example for LDEV 260 01 04 CCI software environment 2 23 Hitachi Command Control Interface User and Reference Guide 2 24 o Specifying LDEV in decimal used by the inqraid command of CCI Example for LDEV 260 260 o Specifying LDEV in hex used by the ingraid command of CCI Example for LDEV 260 0x104 TagmaStore USP TagmaStore NSC LDEV will be converted to Port Targ Lun mapping to this LDEV internally because the RAID storage system needs to specify Port Targ Lun for the target device Thi
425. reserved Executing The command device cannot be operated because it is used at the local CCI Executing A command device cannot be set because LDEV is other than the OPEN volume Executing The specified LDEV is not installed Executing A command device cannot be set because LDEV is the virtual volume of Thin Image or Copy on Write Snapshot Executing The command cannot be operated because the virtual LDEV is not defined yet Executing The value of LUN exceeds the maximum Troubleshooting 9 53 Hitachi Command Control Interface User and Reference Guide raidcom add lun Executing Async Error message Executing Error code SSB1 SSB2 Description The value of LDEV exceeds the maximum Executing Another LDEV is already mapped to the specified LUN Executing The value of Host group ID exceeds the maximum Executing The program product is not installed Executing The specified host group is not installed Executing An invalid LDEV exists in the specified LDEVs Executing The multiple LDEV cannot be specified Executing When the host mode option 60 is set LUN path of LUNO cannot be set or released Executing An invalid LDEV exists in the specified LDEVs Executing The LU path cannot be added because the virtual LDEV ID of the specified volume was deleted Table 9 34 SSB codes that are retur
426. resource group name gt ldev_id lt ldev gt Virtualize LDEVs Set a virtual LDEV ID to the specified LDEV Also specify the product ID and SSID if necessary raidcom map resource ldev_id lt ldev gt virtual_ldev_id lt ldev gt ssid lt ssid gt emulation lt emulation type gt Create LU path To create LU path assign LDEVs to the host group that belongs to the resource group in the virtual storage machine raidcom add lun port lt port gt lt host group name gt ldev_id lt ldev gt lun_id lt lun gt Removing the virtual storage machine Use the following provisioning operations to remove resources from the virtual storage machine and to remove the virtual storage machine Operation overview Remove the LU path Description Remove the LU path from the LDEV in the virtual storage machine Executed command raidcom delete lun port lt port gt lt host group name gt lun_id lt lun gt ldev_id lt ldev gt grp_ opt lt group option gt device_grp name lt device group name gt lt device name gt Remove the virtual LDEV ID Remove the virtual LDEV ID from the LDEV in the virtual storage machine raidcom unmap resource ldev_id lt ldev gt virtual_ldev_id lt ldev gt Remove the LDEV from the resource group Remove the LDEV from the resource group in the virtual storage machine raidcom delete resource resource name l
427. ribes entity in a configuration definition file on the same instance and classifies connection of volume through the mirror descriptor In case of TrueCopy ShadowImage cascading connection too the volume entity describes to a configuration definition file on the same instance The following figure shows an example of this 2 26 CCI software environment Hitachi Command Control Interface User and Reference Guide HORCMINSTO HORCMINST1 MU O Oradb2 Htdev group dev_name port TargetID LU MU oradev1 CL1 D 3 0 0 oradevt CL1 D oradevi1 CL1 D 3 4 i oradevi1 CL1 D oradev21 CL1 D 3 6 ad oradev21 CL1 D ip_address dev c ip_address service HST1 HST1 horcm HST1 HST1 horcm HST1 HST1 horcm0 Figure 2 15 ShadowImage cascade connection and configuration file ShadowImage Since ShadowImage is a mirrored configuration within one storage system it can be described as a volume of the cascading connection according to two configuration definition files For a ShadowImage only cascading connection the specified group is assigned to the mirror descriptor MU of ShadowImage specifically defining 0 as the MU for ShadowImage Figure 2 16 Pairdisplay on HORCMINSTO on page 2 28 Figure 2 18 Pairdisplay on HORCMINSTO on page 2 28 show ShadowImage cascading configurations and the pairdisplay information for each configuration CCI software environment 2 27 Hitachi Command Control Interface User and Reference Guide E
428. rioritized WWN settings soe cue etal Bee e Gee ewe Sh ne aoe eed ee ee 5 50 Setting SPM name for host bus adapter 0000 e eee aee 5 50 Grouping multiple host bus adapters into one group 5 50 Checking the traffic of the prioritized WWN and the non prioritized WWN ceestis sciendi See etre Gates eee eee Howe eew ete es 5 51 Stopping performance control of server by using SPM function 5 51 Caution about exclusive access control with Storage Navigator 5 51 Deleting WWN from the SPM targets with SPM name or SPM group name 5 51 Resource group function and restrictions when running Server Priority MaNOOGl 2 5 sass ae eh eh ee oe ee he eee 6 oe ee ee Sx 5 52 Virtual storage machine operations VSP G1000 only 05 5 52 Creating host groups in a virtual storage machine 04 5 52 Adding LDEVs to a virtual storage machine 000 0c eee 5 53 Removing the virtual storage machine 0 000 es 5 53 Data replication operations with CCI 0 0 00 eee ees 6 1 About data replication operations 1 0 cc ees 6 2 Features of paired VOIUMES 1 ees 6 2 Using CCI with ShadowImage and TrueCopy 00ers 6 3 Using CCI with Thin Image 2 1024 odes a ceeds dawns eee eee sey es 6 4 Using CCI with global active device 1 es 6 5 Shadowlmage operationS 0 0 ce es 6 5 ShadowImage duplicated mirroring 000 e eee ee eee 6 6 ShadowImage cascading pairs
429. ription contents of the configuration definition file Specify VSP G1000 information If you specify the virtual storage machine information error No such control device occurs Specify the virtual storage machine by the command option s lt seq gt or u lt unit ID gt The virtual storage machine can be specified regardless of the description contents of the configuration definition file Some commands only see Operation target when you specify the virtual storage machine by the raidcom command on page 3 51 Operation target when you specify the virtual storage machine by the raidcom command This topic shows operational objects when you specify the virtual storage machine by the raidcom command option s lt seq gt or u lt unit ID gt If the operation target of the command is VSP G1000 when you specify the virtual storage machine even if you specify the virtual storage machine for the command option that is s lt seq gt or u lt unit ID gt the option is ignored When you do not specify the option that is s lt seq gt or u lt unit ID gt operational objects of all the raidcom command is VSP G1000s Operation target when you specify the virtual storage machine VSP G1000 VSP G1000 VSP G1000 Operation type Commands raidcom get copy_grp raidcom add copy_grp raidcom delete copy_grp CCI functions 3 51 Hitachi Command Control Interface User and
430. rite Snapshot pair Executing The pair operation is rejected because the specified volume as the primary volume is a reserved volume for GAD or a volume for the GAD pair which is in the invalid status Executing The pair operation is rejected because the specified volume as the secondary volume is a reserved volume for GAD or a volume for a GAD pair Executing A pair cannot be created because the attribute of the pool is other than Thin Image or Copy on Write Snapshot is specified Executing A pair cannot be created because the capacity exceeds the licensed capacity Executing The specified operation is not supported in the current microcode version Executing An internal error occurred Call Hitachi Data Systems Support Center Table 9 39 SSB codes returned by raidcom modify snapshot raidcom modify snapshot Executing Error code Async sspi ssB2 Error message Description Executing The value exceeds the range of LDEV number Executing The MU number exceeds the maximum Executing The command ends abnormally because the volume out of the range of LDEV number is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the ShadowImage reserved volume is specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the Volume Migration source volume
431. rmine the relationship between LDM volumes and LDEV by given a KEY WORD to the ingraid command ingraid LETALL CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID D Vol2 Dsk4 DDRS 34560D E Vol44 Dsk0 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 F Vol45 Dsk0 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 G Dmt1 Dsk1 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 G Dmt1 Dsk2 CL2 K 61456 257 s s ss 0005 1 01 11 OPEN 3 G Dmt1 Dsk3 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 ingraid Volume CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID Vol2 Dsk4 E 7 z z 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 E s s ss 0005 1 01 11 OPEN 3 Dmt1 Dsk3 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 ingraid Phy CLI DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT ID Harddisko CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 Harddiskl1 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 Harddisk2 CL2 K 61456 257 s s ss 0005 1 01 11 OPEN 3 Harddisk3 CL2 K 61456 258 E s s ss 0005 1 01 11 OPEN 3 Harddisk4 DDRS 34560D e Device Object Name of the Partition for Windows NT o Device HarddiskX PartitionY DskX pY e Device Object Name
432. rol command 2 38 trace files 2 38 trace control command 2 38 transaction mode 1 3 1 4 3 15 3 16 troubleshooting 9 1 command error codes 9 8 error messages and error codes 9 6 general 9 2 generic error codes horctakeover and pair commands 9 16 9 19 generic error codes raidscan raidqry raidar horcctl 9 17 notes and restrictions 9 3 specific codes 9 18 system log messages 9 6 U UNIX files 2 32 starting up one instance 4 2 starting up two instances 4 2 user authentication 1 7 3 6 command operation 3 6 V virtual volumes creating 5 24 5 34 operations 5 24 5 32 volume migration commands 6 39 configurations 6 37 controlling 6 37 specifications 6 37 volumes restrictions using Data Retention Utility 7 3 W Windows files 2 33 starting as a service 4 6 starting up one instance 4 3 starting up two instances 4 3 Index 3 Hitachi Command Control Interface User and Reference Guide Index 4 Hitachi Command Control Interface User and Reference Guide Hitachi Command Control Interface User and Reference Guide Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara California 95050 2639 U S A www hds com Regional Contact Information Americas 1 408 970 1000 info hds com Europe Middle East and Africa 44 0 1753 618000 info emea hds com Asia Pacific 852 3189 7900 hds marketing apac hds com Hitachi Data Systems MK 90RD7010 18
433. roup ID exceeds the maximum value Executing The specified host group is not installed 9 86 Executing The attribute of specified port is Initiator or External Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 52 SSB codes that are returned by raidcom add hba_wwn command raidcom add hba_wwn Error code Executing Async sspi ssB2 Error message Description Executing The program product is not installed Executing The value of hba_wwn is invalid Executing The value of host group ID exceeds the maximum Executing The host group is not installed Executing The attribute of specified port is Initiator or External Executing The number of WWN reached the maximum Executing HBA WWYN is already registered Table 9 53 SSB codes that are returned by raidcom set hba_wwn command raidcom set hba_wwn Executing Error code Async sspi ssB2 Error message Description Executing The program product is not installed Executing The value of host group ID exceeds the maximum Executing The host group is not installed Executing The attribute of specified port is Initiator or External Executing The specified WWN does not exist Executing The specified WWN nickname is already used in the same port Table 9 54 SSB codes that are returned by raidcom reset hba_wwn com
434. roups Create host groups by specifying the reserved port and host group ID to the resource group raidcom add host_grp port lt port gt lt HG gt host_grp_ name lt host group name gt Specifying the host mode and host mode options Specify the host mode to the created host group Also specify the host mode options if necessary raidcom modify host_grp port lt port gt lt host group name gt host _mode lt host mode gt host_mode_opt lt host mode option gt Adding hosts to the host group 5 52 Register hosts to the host group Provisioning operations with CCI raidcom add hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt Hitachi Command Control Interface User and Reference Guide Adding LDEVs to a virtual storage machine Use the following provisioning operations to add LDEVs to a virtual storage machine and to use LDEVs from hosts Operation overview Delete the virtual LDEV ID set by default Description Specify an LDEV ID to delete the virtual LDEV ID set by default By default the virtual LDEV ID is the same as the real LDEV ID Executed command raidcom unmap resource ldev_id lt ldev gt virtual_ldev_id lt ldev gt Add the LDEV to the resource group Add the LDEV of which the virtual LDEV ID was deleted to the resource group in the virtual storage machine raidcom add resource resource name lt
435. rp_name lt copy group name gt lt device group name gt device group name mirror_id lt mu gt journal_id lt journal ID gt Delete copy group raidcom delete copy _grp copy_grp_name lt copy group name gt Display copy group information raidcom get copy _grp 5 12 View CLPR configuration raidcom get clpr Modify CLPR migrate LDEV parity group external group raidcom modify clpr Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Operation type Remote copy environ ment RCU see the manuals for TC TCz UR and URz Description Register RCU Corresponding command raidcom add rcu cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt rcu_port lt port gt Delete RCU raidcom delete rcu cu_free lt serial gt lt id gt lt pid gt Set RCU attribute raidcom modify rcu cu_free lt serial gt lt id gt lt pid gt rcu_option lt mpth gt lt rto gt lt rtt gt Display RCU information raidcom get rcu cu free lt serial gt lt id gt lt pid gt RCU path see the manuals for TC TCz UR and URz Add RCU logical path raidcom add rcu_path cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt rcu_port lt port gt Delete RCU logical path raidcom delete rcu_path cu_free lt serial gt lt id gt lt pid gt mcu_port lt port
436. rresponding mirror descriptors as outlined in Table 2 3 Mirror descriptors and group assignments on page 2 26 Omission of MU is handled as MU 0 and the specified group is registered to MU 0 on ShadowImage and TrueCopy Also the MU that is noted for HORCM_DEV in Table 2 3 Mirror descriptors and group assignments on page 2 26 reflects a random numbering sequence for example 2 1 0 CCI software environment 2 25 Hitachi Command Control Interface User and Reference Guide Table 2 3 Mirror descriptors and group assignments SI Snapshot only HORCM_DEV parameter in configuration file MU 1 2 MU 3 63 HORCM_DEV oradevi oradevi dev_group dev_name Oradb oradev1 HORCM_DEV oradev1 oradevi oradev11 dev_group dev_name Oradb oradev1 Oradb1 oradev11 Oradb2 oradev21 oradev21 HORCM_DEV oradevi oradeviil oradev21 dev_group dev_name TargetID Oradb oradevl 2 Oradb1 oradevil 2 Oradb2 oradev21 2 Oradb3 oradev31 2 oradev31 HORCM_DEV oradevi dev_group dev_name TargetID Oradb oradev1 HORCM_DEV oradevi_ oradevil dev_group dev_name Oradb oradev1 Oradb1 oradev11 Oradb2 oradev21 oradev21 HORCM_DEV oradevi oradevil oradev21 dev_group dev_name TargetID Oradb oradev1 2 Oradb1 oradev11 oradev41 Oradb2 oradev21 Oradb3 oradev31 Oradb4 oradev41 oradev31 Cascading connection and configuration files A volume of the cascading connection desc
437. rry away the S VOL This is a problem of MSCS service because Windows system does change the signature through reboot if the same signature is detected on NO MSCS service MSCS will not accommodate LUNs with duplicate signatures and partition layout The best way to avoid such problems is to transport to another host outside the cluster but this enforces to set up a backup server so CCI supports a facility to put back the signature as a second way The signature can be changed by using the dumpcfg exe command attached to Windows resource kits but if the S VOL is created with the Noread option and the system is rebooted then the dumpcfg exe command will fail to change the signature because the system does not know the signature and volume layout information for S VOL CCI adopts the following way with this point in view e You must save the signature and volume layout information to the system disk by using the ingraid gvinf command after an S VOL has set the signature and new partition by the Windows disk management e You can put back the signature by setting the signature and volume layout information to an S VOL that was saved to the system disk by using the ingraid svinf command after splitting the S VOL If the S VOL is created with the Noread option and the system is rebooted then the system cannot create a device object Device HarddiskVolume and Volume guid for S VOL but the svinf option will create a Device object Dev
438. rsal Replicator TrueCopy volume All volumes in a group must be contained within the same storage system If two or more groups of CCI include the same CT group CTGID then pair operation of the group specification is handled in CT group entirety Registration of CTGID number and limitations CCI registers CTGID to RAID disk array automatically when paired volumes are created by paircreate command and groups of configuration definition files are mapped to CTGID The maximum number of CT groups is 256 for Virtual Storage Platform and USP V VM CTGIDO to CTGID255 128 for TagmaStore USP TagmaStore NSC CTGIDO to CTGID127 64 for Lightning 9900 V CTGIDO CTGID63 and 16 for XP512 XP48 Disk Array CTGIDO to CTGID15 TrueCopy Async Universal Replicator pair command is terminated with EX_ENOCTG when the maximum number of CT groups is exceeded Relationships between CTGID and Journal ID CT group numbers 0 127 are used for TrueCopy Async TrueCopy and Universal Replicator The rest of the CT group numbers 128 255 are used only for Universal Replicator and are mapped to the journal Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Table 6 7 Assignment of consistency group IDs CTGIDs CTGID Assignment TrueCopy Asynchronous CTG 0 127 TrueCopy Universal Replicator CTG 0 127 Universal Replicator CTG 128 255 e At time Split for TrueCopy The operation for making data consi
439. rt This message may be output if the migration source storage system is USP V VM and the host mode option 2 is not set to the port that connects to the migration target storage system Get Command Async 2E11 8011 The operation cannot continue because the Status microcode is being replaced CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Executing 2E20 4100 There is no external volume group Get Command Async 2E20 4400 Invalid WWN Status CMDRJE Executing 2E20 4500 There is no path group Get Command Async Status CMDRJE Executing 2E22 4300 The same path has been defined already Get Command Async Status Get Command Async 2E23 4303 The operation cannot be done because the Status number of path in the path group exceeds 8 CMDRJE Executing 2E30 8400 The attribute of a port is not External ELUN Get Command Async 2E31 4000 The specified external storage LU is the device of Status not supported Troubleshooting 9 93 Hitachi Command Control Interface User and Reference Guide raidcom add path Executing Error code Async sspi ssB2 Get Command Async The specified external storage system is not Status supported Error message Description CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Async An internal error occurred Status Call Hitachi Data Systems Support Center
440. rver machine starts up or manually by the startup script HORCM reads the definitions specified in the configuration file upon startup The environment variable HORCM_CONMF is used to define the location of the configuration file to be referenced HORCM_CONF RD WR command Server machine Remote communication Figure 2 8 HORCM operational environment CCI instance configurations The basic unit of the CCI software structure is the CCI instance A CCI instance consists of HORC manager HORCM CCI commands the user defined configuration definition file and the log function for maintenance Each instance uses its own configuration definition file to manage volume relationships while maintaining awareness of the other CCI instances Each CCI instance normally resides on separate servers one node per instance If two or more instances are run on a single server for example for test operations it is possible to activate two or more instances using instance numbers The CCI commands to be used are selected by the environment variable HORCC_MRCF The default command execution environment for CCI is TrueCopy The CCI instance shown in the following figure has a remote execution link and a connection to the RAID storage system The remote execution link is a network connection to another PC to allow you to execute CCI functions remotely The connection between the CCI instance and the storage system illustrates the connection between
441. s raidcom get parity _grp T GROUP Num_LDEV U AV_CAP GB R_LVL R_TYPE SL CL DRIVE TYPE R 32 16 4 45 140000 RAID1 2D 2D 0 0 DKS2C K072FC R 32 17 4 45 140000 RATID1 2D 2D 0 0 DKS2C K072FC R 33 16 4 45 140000 RATID1 2D 2D 0 0 DKS2C K072FC R 33 17 4 45 140000 RAID1 2D 2D 0 3 DKS2C K072FC Moving parity groups If you change the allocation of parity groups parity groups are moved from another CLPR In this case plural parity groups which configure the distributed parity group have to be allocated the same CLPR Parity groups including LDEVs where cache area of Cache Residency is defined cannot be Provisioning operations with CCI 5 45 Hitachi Command Control Interface User and Reference Guide moved to another CLPR For the restrictions on the CLPR s transfer see the Performance Guide The following shows examples of parity groups transfer in CLPR 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 transfer By displaying the information about parity groups check the result of CLPR transfer The following shows an example of parity group list raidcom get parity _grp T GROUP Num_LDEV U AV_CAP GB R_LVL R_TYPE SL CL DRIVE _TYPE R 32 16 4 45 140000 RAID1 2D 2D 0 0 DKS2C KO72FC R 32 17 4 45 140000 RAID1 2D 2D 0 1 DKS2C KO72FC R 33 16 4 45 140000 RAID1 2D 2D 0 3 DKS2C KO72FC Ro 33 07 4 45 140000 RAID1 2D 2D 0 3 DKS2C KO72FC
442. s Using LVM and TrueCopy together When constructing the LVM on the paired volume in the mutual hot standby configuration the LVM logical volumes must be constructed in units of volume to prevent the volumes from being mounted by the LVM Coexistence of When the LVM mirror and TrueCopy volumes are used together the LVM mirror and LVM mirror handles write errors and changes the volumes Thus TrueCopy the fence level of the volumes used by the LVM mirror must be set to data Using paired When constructing paired volume in a single host it is necessary volume in a single to activate two or more CCI instances To activate two or more CCI host instances instance numbers must be assigned using the environment variable HORCMINST The HORCM and TrueCopy ShadowImage commands must possess this environment variable A configuration definition file and a log directory is set for each instance For sharing command devices over 17 instances use SCSI path among the storage system ports to share the command devices Troubleshooting 9 3 Hitachi Command Control Interface User and Reference Guide Sharing volumes in a hot standby configuration Notes and restrictions When paired volume is used for the disk shared by the hosts in hot standby configuration using HA software use the primary volume as the shared disk and describe the corresponding hosts using the paired volume in the configuration definition file as shown below I
443. s necessary to describe the addresses of all of these servers The following values are defined in the HORCM_INST parameter e dev_group The server name described in dev_group of HORC_DEV e ip_address The network address of the specified remote server e 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 will be used When HORCM has two or more network addresses on different subnets for communication the ip_address of HORCM_MON must be NONE This configuration for multiple networks can be found using the raidqry r lt group gt command option on each host The current HORCM network address can be changed using horcctl NC lt group gt on each host CCI software environment Hitachi Command Control Interface User and Reference Guide HORCM_MON HORCM_MON ip_address service poll 10ms timeout 10ms ip_ address service poll 10ms timeout 10ms NONE horem 1000 3000 NONE horcm 1000 HORCM_INST HORCM_INST dev_group ip_address dev_group ip_address service oradb HST1_IPA oradb HST2_IPA horcm oradb HST1_IPB oradb HST3_IPA horcm oradb horcm horcm Subnet A Subnet B IPA IPB IPA IPB HST3 HST2 IPA IPB Storage Figure 2 13 Configuration for multiple networks 5 HORCM_LDEV The HORCM_LDEV parameter is used for specifying stable LDEV and Serial as the physical volumes corresponding to the pai
444. s 7 5 permission command 7 10 permitting protected volumes 7 11 specifications 7 6 data protection operations 7 1 data replication operations 6 1 Data Retention Utility how it works 7 2 restrictions on volumes 7 3 Database Validator how it works 7 3 restrictions 7 4 definition file configuration parameters 2 14 definition file configuration parameters 2 14 dev_name 2 18 device groups 3 29 definition methods 3 29 deleting 3 34 settings and read operations 3 29 device parameter HORCM_DEV 2 20 Index 1 Hitachi Command Control Interface User and Reference Guide discovering remote volumes 6 55 dual pathing on Solaris 2 3 2 17 duplicated mirroring 6 6 endian little vs big 2 11 environment variables for data protection 7 14 environment variables for log directories 2 38 error codes horctakeover and pair commands troubleshooting 9 16 raidscan raidqry raidar horcctl troubleshooting 9 17 troubleshooting 9 6 9 18 error messages troubleshooting 9 6 examples directory mound for Windows 8 12 GPT disk for Windows 8 11 group version control for mixed storage system configurations 8 2 LDM volume discovery and flushing for Windows 8 2 mountvol attached to Windows 8 5 signature changing facility for Windows 8 9 SLPR configuration 8 18 specify host group 8 14 system buffer flushing 8 6 volume discovery 8 3 external volumes creating 5 39 operations 5 39 F fence level settings 6 31 6 32 fibre channel failure 6 30 files 2
445. s by itself three by default The fence level can be set to data in this case in which disk errors are permissible by creating multiple files Data V Log V Log IV Primary volume Secondary volume Figure 6 12 Relationship between logs journal and data in paired status Never fence level Because most UNIX file systems excluding JFS and VxFS have no journal files the fence level should be defined as Never When a takeover by the S VOL occurs fsck is executed on the volume 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 the S VOL is suspended During operation error recovery should be performed when the suspended status PSUE or PDUB is detected when one error occurs Copy on Write Snapshot operations Copy on Write Snapshot normally creates virtual volumes for copying on write without specifying LUNs as S VOLs However to use a Copy on Write Snapshot volume via the host it is necessary to map the Copy on Write Snapshot S VOL to a LUN Therefore CCI provides a combined command to enable the user or application to use the same CCI command in order to maintain ShadowImage compatibility Copy on Write Snapshot uses two techniques one called V VOL mapping or virtual volume mapping and the other is Snapshot using copy on write or Copy on Write Snapshot Copy on Write Snapshot volum
446. s feature is TagmaStore USP TagmaStore NSC microcode dependent if HORCM fails to start HORCM_DEV needs to be used Note The HORCM_LDEV format can only be used on the 6 HORCM_LDEVG The HORCM_LDEVG parameter defines the device group information that the CCI instance reads For details about device group see LDEV grouping function on page 3 25 The following values are defined e Copy group specifies a name of copy group This is equivalent to the dev_group of HORCM_DEV and HORCM_LDEV parameters CCI operates by using the information defined here e Idev_group Specifies a name of device group that the CCI instance reads e Serial Specifies a storage system serial number For VSP G1000 add a 3 at the beginning of the serial number For example for serial number 12345 enter 312345 HORCM_LDEVG Copy Group ldev_group Serial ora grpl 64034 7 HORCM_INSTP The HORCM_INSTP parameter is used when specifying a path ID for the link of TrueCopy as well as HORCM_INST parameter You can specify from 1 to 255 for the path ID If you do not specify the Path ID the behavior is the same as when HORCM_INST is used HORCM_INSTP dev_group ip address service pathID VGO1 HSTA horem 1 VG02 HSTA horem 2 Note The path ID can be specified at TrueCopy Universal Replicator and Universal Replicator for Mainframe However the path ID cannot be specified at UR URz when connecting USP V VM and USP NSC The same p
447. s internal processing is in progress CMDRJE Executing 2E11 9400 The command cannot be accepted After a while execute the same command CMDRJE Execution 2E20 0000 The specified LDEV is not installed Get Command Async 2E30 000A The specified LDEV is used as a Dynamic Status Provisioning Get Command Async 2E30 000C The specified LDEV is used as a quorum disk Status Get Command Async 2E30 000E The specified LDEV is used as a pool volume Status CMDRJE Executing 2E30 OOOF It is used as a journal 9 48 Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom modify Idev status blk Error message Get Command Status Executing Async Error code SSB1 SSB2 Description The specified LDEV is used as a reserved volume of Volume Migration Get Command Status Volume Security is set to the specified LDEV Get Command Status It is used as a remote command device Get Command Status It is a volume that the Data Retention Utility is set Get Command Status The specified LDEV is a Data Retention Utility Volume Retention Manager attribute device Get Command Status It is used as a command device that is used at extended consistency group Get Command Status DP volume that is not in the blocked state is included in the DP volume associated with a pool that the pool volume is belongs to Get Command Status Maintenance work cannot be
448. s specified as the P VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the LUSE volumes of different structure are specified as the P VOL and the S VOL Executing A pair cannot be created because the volume in which the VMA is set is specified as the P VOL Executing A pair cannot be created because the external volume is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume other than V VOL is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the pool VOL is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the volume the data volume or the journal volume of the Universal Replicator pair that is in the intermediate site of the 3DC cascading configuration is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing A pair cannot be created because the P VOL of a Universal Replicator pair is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Troubleshooting 9 61 Hitachi Command Control Interface User and Reference Guide raid com add snapshot Executing Error message Async Executing Error code Description SSB1 SSB2 A pair cannot be created because the S VOL
449. scover the Volume GUID s by using inqraid Volu fv command option Examples C HORCM etc gt ingraid CLI Vol fv DEVICE FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT _ID Volume cec25efe d3b8 11d4 aead 00c00d003b1e Vo1l3 Dsko0 CL2 D 62496 256 OPEN 3 CVS CM Mount used DefineDosDevice Note This may forcibly dismount the mounted volume due to LOG OFF AN of Windows For example C HORCM etc gt raidscan x mount E Volume cec25efe d3b8 11d4 aead 00c00d003b1e E lt gt HarddiskVolume3 Mount used Directory mount Note This prevents the forcible removal of a volume due to LOG OFF of AN Windows For example C HORCM etc gt raidscan x mount E Volume cec25efe d3b8 11d4 aead 00c00d003b1e E lt gt HarddiskVolume3 e sync o The synecommand option will also be able to specify a Volume GUID as well as the device object name o If a Volume GUID is specified then it is executed by converting a Volume GUID to a device object name Example C HORCM etc gt raidscan x sync Volume cec25efe d3b8 11d4 aead 00c00d003b1e SYNC Volume cec25efe d3b8 11d4 aead 00c00d003ble Host group control The RAID storage systems have the defined host group in the port and can allocate a host LU for every host group CCI does not use this host LU and specifies an absolute LUN in the port To eliminate confusion that LUN of the CCI notation does not correspond to LUN on the host view an
450. ser Guide MK 92HM7018 Hitachi Universal Replicator User Guide MK 92HM7019 Hitachi Universal Volume Manager User Guide MK 92HM7020 Hitachi Virtual Storage Platform documents Hitachi Copy on Write Snapshot User Guide MK 90RD7013 Provisioning Guide for Mainframe Systems MK 90RD7021 Provisioning Guide for Open Systems MK 90RD7022 Hitachi ShadowImage for Mainframe User Guide MK 90RD7023 Hitachi ShadowImage User Guide MK 90RD7024 Hitachi Storage Navigator User Guide MK 90RD7027 Hitachi Storage Navigator Messages MK 90RD7028 Hitachi TrueCopy User Guide MK 90RD7029 Hitachi TrueCopy for Mainframe User Guide MK 90RD7030 Hitachi Universal Replicator for Mainframe User Guide MK 90RD7031 Hitachi Universal Replicator User Guide MK 90RD7032 Hitachi Universal Volume Manager User Guide MK 90RD7033 Hitachi Thin Image User Guide MK 90RD7179 Hitachi Universal Storage Platform V VM documents Hitachi Copy on Write Snapshot User Guide MK 96RD607 LUN Manager User s Guide MK 96RD615 Hitachi ShadowImage for IBM z OS User Guide MK 96RD619 Hitachi ShadowImage User Guide MK 96RD618 Hitachi Storage Navigator User Guide MK 96RD621 Hitachi Storage Navigator Messages MK 96RD613 Hitachi TrueCopy User Guide MK 96RD622 Hitachi TrueCopy for IBM z OS User s Guide MK 96RD623 Hitachi Universal Replicator for IBM z OS User s Guide MK 96RD625 Hitachi Universal Replicator User Guide MK 96RD624 Hitachi Universa
451. size gt emulation lt emulation type gt location lt lba gt mp_blade_id lt mp gt 5 35 Hitachi Command Control Interface User and Reference Guide Operation M R Description Executed command 16 Creating LDEV Create nickname for created raidcom modify ldev V VOL LDEV V VOL ldev_id lt ldev gt nickname This operation is arbitrary videv name lt ldev maming arbitrary 17 Setting MP Set MP blade of created LDEV raidcom modify ldev blade of LDEV V VOL ldev_id lt ldev gt V VOL mp_blade_id lt mp gt 18 Displaying Display information of created raidcom get ldev ldev_id LDEV V VOL LDEV V VOL and confirm the lt ldev gt cnt lt count gt information result of executing the key lt keyword gt command 19 Creating LU Specify port map LDEV to LUN raidcom add lun port path and create an LU path lt port gt host group name ldev_id lt ldev gt lun_id lt lun gt 20 Displaying LU Display LU path information raidcom get lun port path and confirm the result of lt port gt lt host group information executing the command name gt 21 Starting Start the performance raidcom monitor pool pool performance monitoring of a pool for lt pool ID gt lt pool monitoring of a Dynamic Tiering naming gt operation start pool for Dynamic Tiering 22 Stopping Stop the performance raidcom monitor pool pool performance monitoring of a pool for lt p
452. socket for IPC Inter Process Communication and makes the directory and files as var tmp lcm in CCI version 01 16 03 06 or later 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 Sd then usr sbin tmpwatch f 720 d The command of second line will remove var tmp lcm directory after 720 Hr from HORCM startup even though CCI command is used Action So administrator needs to add the following command in order to avoid this problem bin touch c var tmp lcem 2 gt 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 da Sd then usr sbin tmpwatch f 720 d Error messages and error codes System log messages The following table lists and describes the HORCM system log messages and provides recommended actions for resolving the error conditions Table 9 1 System log messages Message ID Condition Recommended action HORCM_001 The HORCM log file The file cannot be created Create space on the disk on cannot be opened in the HORCM directory which the root directory resides HORCM_002 The HORCM trace file The file cannot be created Create space on t
453. source resource_grp_name meta_resource raidcom modify port port CLI A secur ity _switch y raidcom modify port port CL2 A secur ity switch y raidcom add host_grp port CLI A 0 host_grp_name HP UX P raidcom add host_erp port CL2 A 0 host_grp_name HP UX S raidcom modify host_grp port CLI A 0 host_mode HP UX HP UX raidcom get host_grp port CLI A raidcom get host_grp port CL2 A raidcom add hba_wan port CLI A HP UX P hba_wwn 210000e0 8b0256F8 raidcom add hba_wan port CL2 A HP UX S hba_wwn 21000020 8b0256F9 raidcom get hba_wan port CL1 A HP UX P raidcom get hba_wan port CL2 A HP UX S for 1 S i in 0 1 9 do raidcom add Idev Idev_id bi capacity 10g parity_grp_id 1 1 for 1 S i in 10 1 19 do raidcom add Idev Idev_id S i capacity 10g parity_erp_id 1 2 raidcom get command_status raidcom reset command_status for I Sei in 0 1 19 do raidcom initialize Idev ldev_id Shi operation afmt raidcom get command_status raidcom reset command_status for I S i in 0 1 19 do raidcom modify Idev Idev_id bi device_name my_volume_S i j for I S i in 0 1 19 do raidcom modify Idev Idev_id bi mp_blade_id 2 Log in with the User ID USEROI and Password PASSOI Lock the resource group meta_resource Turn ON the security switch of PortCLi A and PortCL2 A Set Host group 0 to PortCLI A and Host group name HP UX P Set Host group 0 to PortCL
454. specified LDEV is used as a pool volume Get Command Status Async The specified LDEV is used as a journal volume Get Command Status Async The specified volume is used as a command device Get Command Status Async Data Retention Utility is set to the specified volume Get Command Status Async The specified LDEV cannot be operated because it is an external volume mapped for online data migration Get Command Status Async The emulation type of the specified LDEV is not OPEN V Get Command Status Async The specified LDEV cannot be used because the size of LDEV is less than the minimum capacity of the quorum disk CMDRJE Get Command Status Executing Async Troubleshooting Internal error occurred 9 51 Hitachi Command Control Interface User and Reference Guide Table 9 32 SSB codes that are returned by raidcom delete lun command raidcom delete lun Executing Async Error message Executing Error code SSB1 SSB2 Description The other than multiplatform volume or OPEN volume is included in the specified LDEV Executing An used LDEV exists in the specified LDEV Executing It cannot be deleted because it is the last path of TrueCopy Executing It cannot be deleted because it is the last path of ShadowImage Executing It cannot be deleted because it is the last path of Thin Image or Copy on
455. ssing time Therefore CCI provides two ways to execute the configuration setting command synchronously and asynchronously Storage system Command accept Command accept Command Command Respond Refer status Execute Lenesesateceseuceuseuenuceseuseetes Processing Respond Synchronous command Asynchronous command Figure 5 1 Synchronous and asynchronous command processing Execute Processing Complete Respond Command completion check The processing difference between these two command types are described in Synchronous command processing on page 5 3 and Asynchronous command processing on page 5 3 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide Synchronous command processing In addition to the replication commands the process is executed by synchronizing with a command execution and then returning a response after the processing is completed When an error occurs the error is returned to CCI at each occurrence Asynchronous command processing When an asynchronous command is executed the command is received at the storage system and a response is returned before the processing is executed The actual processing is executed asynchronously with command input The completion of the asynchronous command processing can be checked with the raidcom get command_status command Executing raidcom get command_status command after e
456. st group 0 host group name HP UX P to the PortCL1 A and the host group 0 host group name HP UX S to the Por tCL2 A Set the host mode HP UX to the host group 0 of PortOL1 A and PortCL2 A Display the host group information that is set to the PortCLI A and the PortCL2 A Set the connection host WW 210000e0 8025678 to the PortCLi A host group HP UX P and the connection host WAN 21000020 8b0256f9 to the PortCL2 A host group HP UX S Display the connection host WIN that is set to the PortCLI A host group HP UX P and ithe connection host WIN that is set to the Por tCL2 A host group HP UX S Figure 5 10 Script examples of virtual volume operation Dynamic Tiering 1 3 Provisioning operations with CCI Hitachi Command Control Interface User and Reference Guide 5 37 for I i in 0 1 4 do Create 5 of 10G LDEV to Parity_grp_id 1 1 raidcom add Idev Idev_id Si capacity 10g LDEV 0 to 4 Low speed media parity_erp_id 1 1 or 1 Si in 5 1 9 do Create 5 of 106 LDEV to Parity_grp_id 1 2 raidcom add Idev Idev_id i capacity 10g gt LDEV 5 to 9 High speed media parity_grp_id 1 2 r raidcom get command_status raidcom reset command_status for I i in 0 1 9 do Ba raidcom initialize Idev Idev_id Shi operation LDEV Execute Quick format to O to 9 qfmt i 5 raidcom get command_status raidcom reset command_status for I i in 0 1 9 do
457. stem internal state PSUS Description Writing control on TC async volume TrueCopy Sync PSUS TrueCopy Async Same Writing data Via Bitmap Response Usual Transfer data via ESCON None PFUS Timeout Over Threshold Via Bitmap Usual None PSUE PSUE PSUE PDUB PDUB PDUB 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 None Same link down etc Via Bitmap Usual None Same Via Bitmap Usual None 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 Usual Host side writing response is not delayed HWM High Water Mark Sidefile quantity is over 30 of cache storage TrueCopy Async Universal Replicator error state In the case of an ESCON or fibre channel FC failure the S VOL FIFO queue is missing a data block that was transferred from the P VOL FIFO queue The RCU waits to store the next sequenced data block in the S VOL FIFO queue until the TrueCopy Async copy pending timeout occurs defined using TrueCopy In addition the timeout value can be specified at SVP The default value is set to 5 minutes If the timeout occurs during this waiting state the pair status changes from PAIR to PSUE and non sequenced data blocks are managed by the S VOL bitmap The missing data block can be rec
458. stency is only supported by the following option pairsplit g lt group gt r pairsplit g lt group gt rw TrueCopy Async and Universal Replicator volume characteristics TrueCopy Async Universal Replicator volumes have the following characteristics e PAIR state A TrueCopy Async pair changes to the PAIR status as soon as all pending recordsets have been placed in the queue at the primary volume without waiting for the updates to complete at the secondary volume e Pair splitting When a TrueCopy Async pair is split or deleted all pending recordsets at the primary volume are sent to the secondary volume then the pair status changes to PSUS or SMPL With the pairsplit command only updates for the primary volume that occur during and after the pairsplit operation are marked on the bitmap of the primary volume e Pair resynchronization The pairresyne command resynchronizes the secondary volume based on the primary volume This resynchronization does not guarantee the sequenced data transfer e Error suspending Pending recordsets that have not yet been sent to the secondary volume are marked on the bitmap of the primary volume then deleted from the queue and then the pair status changes to PSUE e Group operations TrueCopy Async automatically registers the CTGIDs with the storage system when paired volumes are created using the paircreate command and groups in the configuration file are mapped to their correspondi
459. switch Error message Executing Async Executing Error code SSB1 SSB2 Description The other than fabric on cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The other than P to P point to point cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet Executing The command device being used at the local CCI exists under the port Executing The program product is not installed Executing Invalid host speed is set for the 4Gbps fibre adapter The available host speeds are AUTO 1G 2G and 4G only Executing Invalid host speed is set for the 8Gbps fibre adapter The available host speeds are AUTO 2G 4G and 8G only Executing The other than 10G cannot be specified when specifying a host speed of the package for Fibre Channel over Ethernet Table 9 16 SSB codes that are returned by raidcom add Idev command raidcom add Idev Error code Error message Tae Description syne SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceeds the range of LDEV number CMDRJE Executing 2E00 0002 Cannot create because the specified capacity is invalid CMDRJE Executing 2E00 0003 SSID is not in the effective range CMDRJE Executing 2E00 000D The value of specified emulation type is invalid CMDRJE Executing 2E00 000E The specified emulati
460. t Command Status Executing Async The value of specified port is invalid Get Command Status Async The operation cannot be done because the microcode is being changed CMDRJE Executing The command cannot be accepted After a while execute the same command Get Command Status Async The serial number the product ID or the SSID of the target storage system is incorrect Get Command Status Async The specified RCU cannot be deleted because the RCU is not registered Get Command Status Async The specified CU number is not defined or an LDEV is not defined under the CU number Get Command Status Async Path cannot be deleted because there is a pair of TrueCopy Universal Replicator or a journal volume is in the relevant CU Get Command Status Async Command cannot be executed because the RCU identification code of a path is invalid CMDRJE Executing The command cannot be accepted because the DKC is busy After a while execute the same command Get Command Status Async An internal error occurred Call Hitachi Data Systems Support Center CMDRJE Executing The value of SSID on the remote storage system is invalid CMDRJE Executing Troubleshooting RCU storage system does not exist 9 81 Hitachi Command Control Interface User and Reference Guide raidcom delete rcu Error message Executing As
461. t HORCC_MRCF 1 D HORCM etc gt echo hd20 23 raidscan find verify 1 fd DEVICE FILE Group PairVol Device File M SERIAL LDEV Harddisk20 oradb1 oradevl1 Harddisk20 1 35013 17 Harddisk21 oradb1 oradev2 Harddisk21 1 35013 18 Harddisk22 oradb oradev3 Harddisk22 1 35013 19 Harddisk23 1 35013 20 Without a HORCMPERM file Commands to run on different operating systems If NO HORCMPERM file exists run a command on the host to permit all volumes on the host Table 7 3 Without a HORCMPERM file Commands to run on different operating systems on page 7 13 shows the command to run on each operating system Table 7 3 Without a HORCMPERM file Commands to run on different operating systems Command echo dev rdsk dev rdisk dev rcdisk HORCM usr bin raidscan find inst Is dev sd HORCM usr bin raidscan find inst Is dev sd dev dasd HORCM usr bin raidscan find inst Is dev rdsk HORCM usr bin raidscan find inst Isdev C c disk grep hdisk HORCM usr bin raidscan find inst Is dev rdisk dsk HORCM usr bin raidscan find inst Is dev rrz HORCM usr bin raidscan find inst DYNIX ptx etc dumpconf d grep sd HORCM usr bin raidscan find inst IRIX64 Is dev rdsk vol dev rdsk vol HORCM usr bin raidscan find inst OpenVMS HORCM usr bin raidscan pi 1 DGA0 10000 DKAO 10000 DGAO 10000 find inst Windows X HORCM etc raidscan exe pi P
462. t in the operable status Get Command Status Async The operation cannot be done because it is in the state of start up Get Command Status Async The operation cannot be done because the internal processing is in progress Wait for a while then retry the operation CMDRJE Get Command Status Executing Async Abnormal cache status CMDRJE Executing The command cannot be accepted After a while execute the same command CMDRJE Executing The specified LDEV is not defined CMDRJE Executing The specified MP Blade is not installed Get Command Status Async The operation failed because the specified journal is not installed Get Command Status Async The journal volume cannot be added or the journal cannot be added to the extended CT group due to insufficient capacity of the shared memory SM CMDRJE Executing The SM for Universal Replicator is not installed Get Command Status Async A journal volume cannot be registered or a journal cannot be added to the extended CT group because the program product of Universal Replicator or Universal Replicator for Mainframe is not installed Get Command Status Async A new journal volume cannot be registered or the number of selected volumes is too many CMDRJE Executing The number of specified LDEVs is invalid Get Command Status Async Troubleshooting
463. t pair Executing The command ends abnormally because the blocked volume is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the volume in formatting operation is specified as the S VOL of a Thin Image or Copy on Write Snapshot pair Executing The command ends abnormally because the shared memory FC TPF or Extension1 is not expanded for necessary capacity Executing The command ends abnormally because the shared memory SS1 or more is not expanded for necessary capacity Executing A Thin Image or Copy on Write Snapshot pair cannot be created due to one of the following reasons e The shared memory is not expanded for necessary capacity e It is in the initializing process Executing The program product is not installed Executing The specified LDEV is used as a quorum disk Executing A pair cannot be created because the volume is already used in the S VOL of a Thin Image or Copy on Write Snapshot pair is specified as the P VOL Executing A pair cannot be created because the volume is already used in the P VOL of a Thin Image or Copy on Write Snapshot pair is specified as the S VOL Executing A pair cannot be created because the volume is already used in the S VOL of a Thin Image or Copy on Write Snapshot pair is specified as the S VOL Executing The command ends abnormally because the
464. t resource group name gt ldev_id lt ldev gt Invalidate the LDEV virtualization Specify the virtual LDEV ID that is the same as the real LDEV ID in order to invalidate the LDEV virtualization Provisioning operations with CCI raidcom map resource ldev_id lt ldev gt virtual_ldev_id lt ldev gt 5 53 Hitachi Command Control Interface User and Reference Guide 5 54 Operation overview Delete the host group Description Delete the host group in the virtual storage machine Executed command raidcom delete host_grp port lt port gt lt host group name gt Remove the host group ID from the resource group Remove the host group ID that belongs to the resource group in the virtual storage machine raidcom delete resource resource name lt resource group name gt port lt port gt lt HG gt Remove the resource from the resource group Remove the resource from the resource group in the virtual storage machine raidcom delete resource resource name lt resource group name gt ldev_id lt ldev gt port lt port gt lt host group name gt parity_grp lt gno sgno gt external_grp_id lt gno sgno gt grp_opt lt group option gt device_grp_ name lt device group name gt lt device name gt Remove the virtual storage machine Delete all resource groups in the virtual storage machine in order to remove the virtual st
465. talled Table 9 81 SSB codes that are returned by raidcom modify spm_group command raidcom modify spm_group Error message Executing Async Executing Error code SSB1 SSB2 Description Server Priority Manager is being used by Device Manager Storage Navigator Executing Server Priority Manager program product is not installed Table 9 82 SSB codes that are returned by raidcom add spm_wwn command raidcom add spm_wwn Error code Error message sari Description sync ssBi SSB2 CMDRJE Executing B9D4 B9DO Server Priority Manager is being used by Device Manager Storage Navigator CMDRIJE Executing B9D4 B9D2 The specified WWN does not exist CMDRJE Executing B9D4 B9D4 Server Priority Manager program product is not installed CMDRJE Executing B9D4 B9D7 The specified SPM name has already existed 9 102 Troubleshooting Hitachi Command Control Interface User and Reference Guide Table 9 83 SSB codes that are returned by raidcom delete spm_wwn command raidcom delete spm_wwn Error message Executing Async Executing Error code SSB1 SSB2 Description Server Priority Manager is being used by Device Manager Storage Navigator Executing The configuration WWN or nickname does not exist Executing Server Priority Manager program product is not installed Table 9 84 SSB codes that are returned by ra
466. tatus transitions Table 6 8 State table for TrueCopy vs TrueCopy Async on page 6 29 shows the transition states for TrueCopy and TrueCopy Async volumes The suspending and deleting states are temporary internal states within the RAID storage system CCI cannot detect these transition states because these states are reported on the previous state of the storage system These states are therefore concealed inside the pairsplit command After the pairsplit command is accepted host write I Os for the P VOL are managed by the cylinder bitmap normal non transmitted data remaining Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide in the P VOL s FIFO queue is transferred to the S VOL s FIFO queue and the pair status is then set to PSUS SMPL state when all data in the P VOL s FIFO queue has been transmitted PFUL If the quantity of data in sidefile cache exceeds 30 of cache storage the internal status of the RAID storage system is PFUL and host write I Os receive delayed response in the range of 0 5 seconds minimum to 4 seconds maximum PFUS If the quantity of data in 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 next new write data If a copy pending timeout occurs during this waiting state then the pair status changes from PAIR to PFUS host write I Os are accepted and write
467. tent CTQ Marker The pairsplit command checks data consistency with CTQ Marker across multiple storage systems If an inconsistent CTQ Marker is detected then it returns with EX_VOLCUR after changed to suspend status 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 horcO 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 0000bb1ib O 198578688 64014 1 32768 z 018 2 0 SJSN 1 0 0000bb1ib 0 99283968 64014 1 32770 0000187 017 2 0 PJSN 1 0 00000011 O 198578688 64014 1 32769 019 2 0 SJSN 1 0 00000011 0 99283968 64014 1 32771 0000187 9 About pairsyncwait command Using the Q Marker with the pairsynewait command is managed on each Journal including the target device Therefore the pairsyncwait command must specify a target device g lt group gt d lt pair vol gt or d lt device file gt or d lt serial gt lt ldev gt For example pairsyncwait g horcO d dev 002 t 500 UnitID CTGID Q Marker Status Q Num 1 0 0000003de8 DONE 0 If group g lt group gt is specified then the first dev_name on the specified group is used Data replication operations with CCI 6 51 Hitachi Command Control Interface User and Reference Guide Explanation of terms e JNL Consistency Restore commits up as far as MAX CTQ Marker e JNL Full Restore commits up to EOM End of marker
468. terface User and Reference Guide Table 3 3 Commands and operation authority managed by Storage Navigator and SVP Operation Operation target MP blade Authority MP blade setting authority Executable command raidcom modify Idev raidcom modify journal raidcom modify external_grp Operation authority Role Storage Administrator System Resource Management Resource creation deletion LDEV creation authority raidcom add Idev raidcom add Idev Storage Administrator Provisioning LDEV deletion authority raidcom delete Idev Storage Administrator Provisioning External volume Universal Volume Manager External volume creation authority raidcom add external_grp raidcom discover external_storage raidcom discover lun Storage Administrator Provisioning External path operation authority raidcom check_ext_storage path raidcom disconnect path Storage Administrator Provisioning External volume disconnection authority External volume connection check and resumption authority raidcom check_ext_storage external_grp raidcom disconnect external_grp Storage Administrator Provisioning External volume mapping release authority raidcom delete external_grp Storage Administrator Provisioning Pool creation and capacity change authority raidcom add dp_pool raidcom add snap_pool Storage Administrator Provisioning
469. th CCI This chapter describes data protection operations using CCI O Data protection operations O Protection parameters and operations O Data Protection facility Data protection operations with CCI 7 1 Hitachi Command Control Interface User and Reference Guide Data protection operations User data files are normally placed on a disk through a software layer such as a file system LVM disk driver SCSI protocol driver bus adapter and SAN switching fabric Data corruption can happen due to software layer bugs or human error CCI Data Protection Facility does not prevent these types of errors On the other hand the purpose of data protection is to prevent writing to volumes that the RAID storage system is guarding Data protection functions include e Data Retention Utility e Volume Retention Manager e Volume Security e Encryption License Key e Database Validator Data Retention Utility The purpose of the Data Retention Utility is to prevent writing to volumes that the RAID storage system is guarding Data Retention Utility is similar to the command that supports Database Validator setting a protection attribute for the specified LU e Hide from Inquiry command The RAID storage system conceals the target volumes from the SCSI Inquiry command by responding unpopulated volume 0x7F to the device type e SIZE 0 volume The RAID storage system replies with SIZE 0 to the target volumes through the SCSI Read capa
470. the CCI software on the host and the command device The command device accepts CCI commands and communicates read and write I Os between the host and the volumes on CCI software environment 2 9 Hitachi Command Control Interface User and Reference Guide 2 10 the storage system The host does not communicate CCI commands directly to the volumes on the storage system the CCI commands always go through the command device User s execution environment i i User s execution environment TrueCopy i Shadowlmage Command i Configuration definition file omara omen Error A Syslog file TrueCopy Configuration monitoring command gem dha orn and event server PP i monitoring Remote execution HORCM log HORCM trace Command trace file HORCM CCI instances Storage Object volumes TrueCopy control Figure 2 9 CCI instance configuration amp components The four possible CCI instance configurations are e One host connected to one storage system Connecting one host to one storage system allows you to maintain multiple copies of your data for testing purposes or as an offline backup Each CCI instance has its own operation manager server software and scripts and commands and each CCI instance communicates independently with the command device The RAID storage system contains the command device that communicates with the CCI instances as well as the primary and secondary volumes of both C
471. the OS control area are used starting at the initial LBA To avoid using this area a specific LBA area is decided and control commands are issued within this area The command LBA recognized by the storage system is shown below provided the maximum OS control area is 16 MB CCI software environment Hitachi Command Control Interface User and Reference Guide Special LDEV space Special file Craw VO volume oe t oe a gamas P cet Command OS Control Area Command Area LBA Target LU Target LU Seeking position 32 768 LBA 32 768 2 In block units 512 bytes per block The host seeks 32 768 512 bytes and issues a command Figure 2 4 Relationship of the special file to the special LDEV Acceptance of commands A command is issued in the LBA area of the special LDEV explained above The RD WR command meeting this requirement should be received especially as a CCI command A command is issued in the form of WR or WR RD When a command is issued in the form of RD it is regarded as an inquiry equivalent to a SCSI inquiry and a CCI recognition character string is returned Command competition The CCI commands are asynchronous commands issued via the SCSI interface As a result if several processes issue these commands to a single LDEV the storage system cannot take the proper action To avoid such a problem two or more write commands should not be issued to a single LDEV Th
472. the S VOL data Flush the system buffer for S VOL updates using raidscan pi Volume find sync g ORB when the backup is finished Online backup using raidscan find sync for Windows file system The raidscan find syne command flushes the system buffer associated with a logical drive through finding a Volume guid corresponding to a group of the configuration file without using the x mount and x umount commands The following examples are for group ORB Examples of using CCI commands Hitachi Command Control Interface User and Reference Guide 8 8 P VOL Side S VOL Side Freeze DB on opening P VOL by Flush the system buffer for NEW S VOL application data using raidscan pi Volume find e Flush the system buffer for P VOL sync g ORB using raidscan pi Volume find Back up the S VOL data sync g ORB Flush the system buffer for S VOL updates Splits the paired volume using using raidscan pi Volume find sync g pairsplit g ORB with r w mode ORB when the backup is finished Unfreeze DB on opening P VOL by application Resynchronize the paired volume using pairresync g ORB Offline backup using raidscan find sync for Windows NT file system The raidscan find syne command flushes the system buffer through finding a logical drive corresponding to a group of the configuration file without using the x mount and x umount commands The following examples are for group ORB P VOL Side S VOL Side Close
473. tification HORCM etc pairmon exe pairmon Volume checking HORCM etc pairvolchk exe pairvolchk Pair configuration confirmation HORCM etc pairdisplay exe pairdisplay RAID scanning HORCM etc raidscan exe raidscan RAID activity reporting HORCM etc raidar exe raidar Connection confirmation HORCM etc raidqry exe raidqry Trace control HORCM etc horcctl exe horcctl HORCM activation script HORCM etc horcmstart exe horcmstart HORCM shutdown script HORCM etc horcmshutdown exe horcmshutdown Synchronous waiting HORCM etc pairsyncwait exe pairsyncwait Connection confirmation HORCM etc inqraid exe inqraid Configuration setting and confirming command HORCM Tool mkconf exe mkconf Text filtering HORCM Tool rmawk exe rmawk Oracle Validation setting HORCM etc raidvchkset exe raidvchkset Oracle Validation confirmation HORCM etc raidvchkdsp exe CCI software environment raidvchkdsp 2 33 Hitachi Command Control Interface User and Reference Guide File name Command name Oracle Validation confirmation HORCM etc raidvchkscan exe raidvchkscan Configuration setting command HORCM etc raidcom exe raidcom A file for management HORCM etc Raidcom_Dic_Raid_RM_Patch txt A file for management HORCM etc Raidcom_Help_Raid_RM txt
474. ting Hitachi Command Control Interface User and Reference Guide raidcom add snap_pool Error message CMDRJE Executing Async Executing Error code SSB1 SSB2 Description Thin Image or Copy on Write Snapshot program product is not installed Get Command Status Async Exceeded the number of pool volume that can be registered in a pool Get Command Status Async The larger number of drive types than the supported configuration cannot be added to the specified pool Get Command Status Async Pool volume cannot be registered because the drive type of specified LDEV is different from the other pool volume type or the drive type in the pool exceeds the three CMDRJE Executing The number of specified LDEVs is invalid Get Command Status Async The emulation type of specified LDEV cannot be used as a pool VOL Get Command Status Async The specified LDEV has the LU path definition Get Command Status Async The specified LDEV is used as a quorum disk Get Command Status Async The specified LDEV is used as a system disk Get Command Status Async The specified LDEV is already used as a pool volume Get Command Status Async The specified LDEV is a command device Get Command Status Async It cannot be used as a pool volume because the size of specified LDEV is less than 8GB Get Command Status Asyn
475. ting script files For remote copy operations CCI interfaces with the system software and high availability HA software on the host as well as the software on the RAID storage system CCI provides failover operation commands that support mutual hot standby in conjunction with industry standard failover products for example MC ServiceGuard HACMP FirstWatch CCI also supports a scripting function for defining multiple operations in a script or text file Using CCI scripting you can set up and execute a large number of commands in a short period of time while integrating host based high availability control over copy operations 1 8 Overview Hitachi Command Control Interface User and Reference Guide Data protection CCI supports data protection operations including Hitachi Database Validator and Hitachi Data Retention Utility Database Validator The CCI software provides commands to set and verify parameters for volume level validation checking of Oracle database operations Once validation checking is enabled all write operations to the specified volumes must have valid Oracle checksums CCI reports a validation check error to the syslog file each time an error is detected Database Validator requires the operation of CCI software product but cannot be controlled via the Storage Navigator software Data Retention Utility The CCI software enables you to set and verify the parameters for guarding at the volume level Once gu
476. tion os k lt eeienscbeve death eeweseeadva ced 1 7 LDEV grouping function sci sssaaa Ss Sas arse heared wears SE OS e ses 1 7 Resource group function 0 0 ce ees 1 8 Resource locking function s a s asasan maaana eaaa 1 8 CCI functions available on all RAID storage systemS 0 00a eae 1 8 In system replication sss ee see eae ocsee dad ac baGae ame ded ee 1 8 Remote replication 2 2 5 sted ease deeds See Saas See oe ee Sees 1 8 Data protection scac res seee e eee ere a Meee ed eR Eb et a 1 9 iii Hitachi Command Control Interface User and Reference Guide CCI software environment 0000 cee eee eee eee ee ees 2 1 Overview of the CCI software environment 0000 cece eee eee 2 2 CCI components on the RAID storage system 0 cee eee eee 2 2 Command device si 2225 05seer es OFS oe eS ot Oe ed oWOws Oe SRS SE SS 2 2 Command device guarding sasssa 0 0 eee eee ees 2 3 Alternate command device function nassa 0000 eee eee ees 2 5 Define the remote command device 0000 eee eee 2 6 CCI and the SCSI command interface 0 0 0 2 6 Command competition 0 0 cee eee ees 2 7 Command Now sie ox de deed ce eres eho et cee es oe Coase eas 2 8 Issuing commands for LDEVs within a LUSE device 2 8 CCI instance components on the host server 0 0000 cece eee eee 2 9 HORCM operational environment 000 cece eee eee 2 9 CCI instance configurations 1 0
477. tion a virtual storage machine is created in two VSP G1000 storage systems respectively Volumes in the virtual storage machine are given virtual LDEV IDs e Primary site Storage system VSP G1000 S N 67000 Virtual storage machine VSP S N 65000 LDEV ID of VSP G1000 10 00 and 10 01 Virtual LDEV ID 01 00 and 01 01 e Secondary site Storage system VSP G1000 S N 68000 Virtual storage machine VSP S N 66000 LDEV ID of VSP G1000 10 00 and 10 01 Virtual LDEV ID 02 00 and 02 01 o o o o o o o CCI functions 3 45 Hitachi Command Control Interface User and Reference Guide HORCMO HORCMI Host in the primary site Virtual storage machine Virtual storage machine VSP SN 65000 VSP SN 66000 01 00 02 00 10 00 10 00 01 01 02 01 10 01 10 01 VSP G1000 S N 67000 VSP G1000 S NHE8000 Legends Virtual LDEV 1D Device group Universal Replicator pair CND Command device Using CCI in a system configuration with the global virtualization function 3 46 To use CCI with the system configuration using the global virtualization function the following two methods can be used e Specifying a virtual storage machine to HORCM_VCMD in configuration definition files e Specifying a virtual storage machine to command options that is s lt seq gt or u lt unit id gt If you specify the virtual storage machine to HORCM_VCMD of the configuration file the shell scripts
478. tion file Make the port name number the same on all servers horcm xxxxx udp xxxxx the port name number of horcm conf If you want CCI to start automatically each time the system starts up add HORCM etc horcmstart to the system automatic startup file for example autoexec bat Execute the horcmstart script manually to start CCI D HORCM etc gt horcmstart Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform ShadowImage operations set the HORCC_MRCF environment variable for the CCI execution environment D HORCM etc gt set HORCC_MRCF 1 D HORCM etc gt pairdisplay g xxxx XXXX group name Two instances To start up two instances of CCI on a Windows system Starting up CCI 4 3 Hitachi Command Control Interface User and Reference Guide 1 Modify Y 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 each instance horcmO Xxxxxx udp XXXXX the port name number of horcm0 conf horcmi xxxxx udp XXXXxX the port name number of horcm1 conf 2 If you want CCI to start automatically each time the system starts up add HORCM etc horcmstart 0 1 to the system automatic startup file for example autoexec bat 3 Execute the horcmstart script manually
479. tion for paired volume If HORCM has protection ON command device at its time then HORCM checks a permission for a paired volume Horcm conf on Horcm conf on HOST1 HOST2 Volumes for Grp1 Volumes for Grp2 Volumes for Grp3 Volumes for Grp4 Visible to Grp2 Ss a oy se a CM protection On command device Figure 7 2 Example for the two host configuration Horcm0 donf on Horcm1 conf on HOST1 HOST1 Horcm0 conf on Horcm1 conf on HOST2 HOST2 volumes for Grp1 volumes for Grp2 volumes for Grp3 volumes for Grp4 Visible to Grp1 Grp3 volumes for Grp2 Hey volumes for Grp4 eae E ax CM protection On command device Figure 7 3 Example for the one host configuration 7 8 Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide Operation authority with CMD security enabled If the CMD security is enabled you have the operation authority for the LU which meets both of the following requirements e The connection to the host has been recognized when you start CCI e The LU is the target of the pair operation specified with MU which is defined in the configuration 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 CCI rejects the request with the error code EX_ENPERM pairdisplay is not included If y
480. to PSUS When the operation is performed at the secondary system the status of the S VOL changes to PSUS the primary system detects this if path status is normal and changes P VOL status to PSUS When a pair is released from the secondary system the secondary system changes the status of the S VOL to SMPL The primary system detects this if path status is normal and changes P VOL status to PSUS The pair must be released from the primary system to change P VOL status to SMPL R W enabled Secondary R W enabled when using write enable pairsplit option The pair is suspended due to an error the pair is not synchronized e The primary and secondary systems keep track of any journal data that are discarded during the suspension operation The primary system keeps track of P VOL tracks that are updated while the pair is suspended When a UR suspension condition is detected the primary system changes P VOL and S VOL status to PSUE If the secondary system detects the condition it changes the S VOL status to PSUE the primary system detects this and changes P VOL status to PSUS R W enabled if no error occurs in the primary volume R enabled If the Data Overflow Watch period is exceeded pair status changes from PFUL to PFUS and the pair is suspended e The PFUS status is displayed by CCI and Storage Navigator as PSUS If a virtual volume of Dynamic Provisioning DP VOL is used as a UR S VOL and t
481. to start CCI D HORCM etc gt horcmstart 0 1 4 Set an instance number to the command execution environment D HORCM etc gt set HORCMINST X X instance number Oorl 5 Set the log directory HORCC_LOG in the command execution environment as needed 6 If you want to perform TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform ShadowImage operations set the HORCC_MRCF environment variable for the CCI execution environment D HORCM etc gt set HORCC_MRCF 1 D HORCM etc gt pairdisplay g xxxx XXXX group name Starting up on OpenVMS systems One instance To start up one instance of CCI 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 COPY SYS 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 number Use the same port number in all servers The port number can be directly specified without registering it in SYS SYSROOT 000000 TCPIP ETC SERVICES DAT 2 Manually execute the HORCM startup command Starting up CCI Hitachi Command Control Interface User and Refer
482. to the PVOL SVOL when the SVOL PVOL is in the suspended state and resynchronizes the NEW_SVOL based on the NEW_PVOL At the result of this operation the volume attributes of the host of reference local host are used as the attributes for the NEW_PVOL SVOL e Event waiting command Used to wait for the completion of volume pair creation or resynchronization and to check the pair status e Pair status display and configuration confirmation command Displays the pair status and configuration of the volume pairs and is used for checking the completion of pair creation or pair resynchronization Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Operation Operation Management Management Server Server A software HORCM HORCNH software Pair generation and resync Secondary volume Pair splitting Storage Figure 6 7 TrueCopy remote system configuration Legend e HORCM The manager is a demon process executes multiple commands charges to a storage system through itself Among the managers are connected by UDP remotely execute a command among the servers mutually e Command A command provisioned by CCI TrueCopy local commands Figure 6 8 TrueCopy local system configuration on page 6 18 illustrates a TrueCopy local configuration The CCI TrueCopy local commands assist the system operation with volume backups among UNIX servers and their operating system management functions
483. tor default sidefile 50 for USP V VM 9900V 40 for TagmaStore USP TagmaStore NSC Write I O control via the high water mark HWM When the quantity of data in the sidefile reaches 30 of cache the TrueCopy Async pair status is HWM of PAIR state and the host write I Os receive a delayed response in the range of 0 5 seconds to 4 seconds Following is an arithmetic expression of the HWM at 100 of a sidefile space HWM High water mark Sidefile threshold 30 to 70 100 Write I O control via the sidefile threshold When the quantity of data in the sidefile occupies the maximum defined sidefile area host write I Os are delayed until there is enough sidefile space to store the next new write data The copy pending timeout group option is defined using Storage Navigator and specifies the maximum delay between the M VOL update and the corresponding R VOL update The range for the copy pending timeout option is 1 255 seconds 600 seconds for Universal Replicator and default value is 90 seconds 60 seconds for UR If the timeout occurs during this wait state the pair status changes from PAIR to PSUS sidefile full and host write I Os continue with updates being managed by the cylinder bitmap Important The copy pending timeout value should be less than the I O timeout value of the host system TrueCopy Async transition states and sidefile control 6 28 TrueCopy Async volumes have special states for sidefile control during s
484. torage systems and configure each virtual storage machine component CCI regards commands as the command to the virtual storage machine by the descriptions of the configuration definition file or the command options that is s lt seq gt or u lt unit id gt and use their information The following table shows how to issue the command to the virtual storage machine for each command How to issue the command to the virtual storage machine Remarks Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairsplit Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairresync Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairevtwait Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairvolchk Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file pairdisplay Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file paircurchk Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file horctakeover Describe the virtual storage machine information in HORCM_LDEV in the configuration definition file raidvchkset Describe the virtual storage machine i
485. tput to the CCI execution log file Example 11 06 03 37897 10413 SSB 0xb9a0 2089 The alphanumeric characters after the equal sign shows an error code The last four digits of alphanumeric characters on the left side of the comma is SSB1 for example b9ao and the alphanumeric characters on the right side is SSB2 for example 2089 e SSB code that is output on the console The following shows an example of an SSB code that is output to the console Troubleshooting 9 19 Hitachi Command Control Interface User and Reference Guide It was rejected due to SKEY 0x05 ASC 0x 20 SSB 0x89E1 0x8 901 on Serialtih4o 15 5561 5502 Figure 9 1 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 of alphanumeric characters on the left side of comma is SSB1 for example B9E1 and the last four digits of alphanumeric characters on the right side is SSB2 for example B901 The following describes the SSB codes that are returned by the replication commands and the configuration setting command raidcom SSB codes returned by the replication commands When a replication command returns an SSB code refer to the troubleshooting information in the user document for the product as follows Command Product returning the SSB code e paircreate Hitachi TrueCopy e pairresync e pairsplit e horctakeover e horctakeoff e paircreate
486. trol Volume Migration 1 Command for Volume Migration CCI supports the volume migration by adding an option m cc to the paircreate command paircreate g lt group gt d lt pair vol gt m lt mode gt vl r c lt size gt m lt mode gt mode cc can only be specified for ShadowImage This option is used to specify the Volume Migration mode Note This option cannot be specified with split option in the same AN command vl r The vl option specifies local and copies from the local instance LU P VOL to the remote instance LU S VOL an original volume as the local instance LU is migrated from P VOL to S VOL and the physical volume mapping between P VOL and S VOL is swapped after copied The vr option specifies remote and copies from the remote instance LU P VOL to the local instance LU S VOL an original volume as the remote instance LU is migrated from P VOL to S VOL and the physical volume mapping between P VOL and S VOL is swapped after copied c lt size gt 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 volume It is possible to discover the external volumes by using fe option of the raidscan command raidscan
487. ts and describes the TrueCopy and ShadowImage pair status terms Table 6 3 Universal Replicator pair status on page 6 20 lists and describes the Universal Replicator pair 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 write requests from the host are accepted or rejected depending on the pair status of the volume The pair status can change when a CCI command is executed The validity of the specified operation is checked according to the status of the volume primary volume e Table 6 4 Pair status versus TrueCopy Universal Replicator commands on page 6 22 shows the relationship between pair status and TrueCopy Universal Replicator command acceptance e Table 6 5 Pair status versus ShadowImage commands on page 6 22 shows the relationship between pair status and ShadowImage command acceptance e Table 6 6 Pair status versus Copy on Write Snapshot commands on page 6 25 shows the relationship between pair status and Copy on Write Snapshot command acceptance For details on pair status of TrueCopy for Mainframe ShadowImage for Mainframe and Universal Replicator for Mainframe see Pair operations with mainframe volumes on page 3 41 Table 6 2 TrueCopy and ShadowImage pair status TrueCopy Pair Status ShadowImage Pair Status Primary Secondary Unpaired volume Unpaired volume R W enabled R W ena
488. tting commandsS 0000 eee e eens 5 5 LDEV nickname function s4 06 2 sweet onbae Seed eeieeee see ee 5 5 Available provisioning operations 0 00 cc ees 5 5 Available provisioning operation specifying device group 5 5 13 SUMMA ries Da eae bela weed sewer ea dis ere ee ee al ee 5 13 Operation method esd eeu e eae ee i beeew eve seiw ieee dwetee es 5 14 Common operations when executing provisioning operations 5 16 Resource group operationS 1 2 000 cee es 5 17 Creating resource QrOUPS 2 6 ee ee ees 5 17 Deleting resource GrOUPS 1 es 5 17 Allocating resources that are allocated to resource groups to other rESOUrCEGr UDS 6 3 2301 oh sb er eds se bets ous beaks wea ee RSLS 5 18 Execution example 2 52 42 e654 eee sede eee eee ee ee et eee ieee es 5 18 Internal volume operations 1 0 0 0c cee ees 5 19 Creating internal volumes open systemS 0000 e eee eee 5 19 Creating internal volumes Mainframe volume 000 eee eee 5 20 Script CxaMpl S 2445 c5504 555 bs0n 088625 es 02504 eRe RADE 5 21 Script examples 602 50 os4 404 4 456 O24 GG Oe Ee ees bees sheds ees 5 23 Virtual volume Dynamic Provisioning operations 000e eee 5 24 Creating virtual volumes Dynamic Provisioning 0 000es 5 24 Script examples 220s ence dbubede a a i aa ee ew bees bee hee ew ae 5 26 Virtual volume Dynamic Provisioning for Mainframe operations 5 29 Creating virtual vo
489. u must define two or more command devices for the HORCM_CMD item in the configuration definition file When two or more devices are defined they are recognized as alternate command devices e Timing of alternate command devices When the HORCM receives an error notification in reply from the operating system via the raw I O interface the alternate command device is used It is possible to force a switch to use the alternate the command device by issuing the horcctl C switch command provided by CCI e Operation of alternating command If the command device is blocked due to online maintenance the switch command should be issued in advance If the switch command is issued again after completion of the online maintenance the previous command device is activated e Multiple command devices on HORCM startup If at least one command device is available during one or more command devices described to the configuration definition file then HORCM can start with a warning message to the startup log by using the available command device Confirm that all command devices can be changed by using the horectl C command option or HORCM has been started without the warning message to the HORCM startup log CCI software environment 2 5 Hitachi Command Control Interface User and Reference Guide TrueCopy Shadowlmage Command HORCM Command Device Altemating Command Figure 2 3 Alternate Command Device Function Define the remote command de
490. ubnets for communication this must be set to NONE e Service Specifies the UDP port name assigned to the HORCM communication path which is registered in etc services Ywindir system32 drivers etc services in Windows SYS SYSROOT 000000 TCPIP ETC SERVICES DAT in OpenVMS If a port number is specified instead of a port name the port number will be used e Poll The interval for monitoring paired volumes To reduce the HORCM daemon load make this interval longer If set to 1 the paired volumes are not monitored The value of 1 is specified when two or more CCI instances run on a single machine e Timeout The time out period of communication with the remote server CCI software environment 2 15 Hitachi Command Control Interface User and Reference Guide 2 16 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 2 HORCM_CMD When using the in band method this command parameter HORCM_CMD defines the UNIX device path or Windows physical device number and specifies a command device that can access the CCI In band method The command device must be mapped to the SCSI fibre using LUN Manager You can define more than one command device to provide failover in case the original command device becomes unavail
491. ueCopy and ShadowImage The cascading connections for TrueCopy ShadowImage can be set up by using three configuration definition files that describe the cascading volume entity in a configuration definition file on the same instance The mirror descriptor of ShadowImage and TrueCopy definitely describe 0 as MU and the mirror descriptor of TrueCopy does not describe 0 as MU HOST1 HORCMINST for TrueCopy HORCMINST for HORCMINSTO for TrueCopy Shadowilmage Shadowlmage TrueCopy TrueCopy Savirannan piam environment environment HORCC MRCF 1 HORCC_MRCF 1 HORCM_DEV group dev_name por TID LU MU group dev_name port TID LU MU group dev name port TI Oradb oradevi CL1 D 3 0 Oradb oradevi1 CL1 D 3 2 Oradb oradev1 CL1 D Oradb1 oradev11 CL1 D 2 0 Oradb1 oradev11 CL1 D Oradb2 oradev21 CL1 D 2 1 Oradb2 oradev21 CL1 D HORCM_INST HORCNM_INST HORCM_INST dev_group ip_address service dev_group ip_address service dev_group ip _address service Oradb HST2 horcm Oradb HST1 Oradb HST1 horem Oradb HST2 horcm0 Oradb1 HST2 Oradb1 HST2 horcm Oradb2 HST2 horcm Note Shaded portions If HORCMINSTO needs to manage Hitachi TrueCopy s paired volume and then oradb must describe that there is a connection to HST1 via HORCMINSTO Figure 2 19 TrueCopy ShadowImage cascading connection and configuration file Figure 2 20 Pairdisplay for TrueCopy on HOST1 on page 2 30 through Figure 2 23 Pairdisplay for ShadowImage on HOST2 HORCMINSTO
492. ume pair that you want to create must be registered in the CCI configuration file ShadowImage volume pairs must include a MU mirrored unit number assigned to the S VOL The MU number indicates that the pair is a ShadowImage pair and not a TrueCopy pair Once the correspondence between the paired logical volumes has been defined in the HORCM_DEV Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide section of the configuration file you can use the configuration file to group the paired volumes into volume groups that can be managed by the host operating system s LVM logical volume manager The host s LVM allows you to manage the TrueCopy ShadowImage volumes as individual volumes or by volume group TrueCopy ShadowImage commands can specify individual logical volumes or group names For LUSE volumes you must enter commands for each volume LDEV within the expanded LU If you define volume groups and you want to issue commands to those volume groups you must register the volume groups in the configuration file For further information about the server LVM see the user documentation for your corresponding operating system TrueCopy ShadowImage Universal Replicator pair status Each TrueCopy pair consists of one P VOL and one S VOL and each ShadowImage pair consists of one P VOL and up to nine S VOLs when the cascade function is used Table 6 2 TrueCopy and ShadowImage pair status on page 6 19 lis
493. umes The following tables show the pair status and access permissions for mainframe LDEVs For more information about displayed pair status of open LDEVs see TrueCopy ShadowImage Universal Replicator pair status on page 6 19 CCI functions 3 41 Hitachi Command Control Interface User and Reference Guide Table 3 11 Pair status and access permission for TrueCopy TrueCopy for Mainframe Pair status in Storage Navigator Pair status in CCI Access to mainframe Mainframe Simplex Open Mainframe P VOL Read write enabled Access to mainframe S VOL Read write enabled not in pair Pending Read write enabled Reject copying Duplex Read write enabled Reject pair PSUS pair suspended split Suspended Read write enabled Reject suspend PSUE pair suspended error Suspended Read write enabled Reject suspend by failure inconsistency in LUSE status Read write enabled HAM only horctakeover only 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 3 12 Pair status and access permission for Universal Replicator Universal Replicator for Mainframe Pair status in Storage Navigator Pair status in CCI Mainframe Simplex Open Mainframe Access to mainframe P VOL Read write enabled Access to mai
494. unction you cannot start CCI HORCM_VCMD In the beginning of HORCM_VCMD specify a serial number of the virtual storage machine to be operated by this instance If you specify the serial number of the virtual storage machine to HORCM_VCMD even if you do not specify the command option that is s lt seq gt or u lt unit ID gt the virtual storage machine of the serial number defined with the beginning of HORCM_VCMD is operated If you define HORCM_VCMD you cannot operate the virtual storage machines whose serial numbers are not specified by HORCM_VCMD When you specify a virtual storage machine that is not specified with HORCM_VCMD by command options that is s lt seq gt or u lt unit id gt error occurs To operate more than one virtual storage machine from a instance specify serial numbers of the virtual storage machines with HORCM_VCMD To operate the virtual storage machine specified in the second or later of HORCM_VCMD use the command options that is s lt seq gt or u lt unit id gt HORCM_LDEV Specify volumes to be copied Serial numbers of the virtual storage machine and virtual LDEV IDs must be specified You cannot specify the volumes with HORCM_DEV in the system configuration with the global virtualization function Specify the volumes with HORCM_LDEV HORCM_INST Specify an IP address and a service name of the remote host as it is for not using the global virtualization function Example of the config
495. unication and HORC Manager failed to re execute Recommended action Please confirm that the HORC Manager in the remote host is running and then increase the value of the timeout in the configuration file EX_INVMOD Invalid RAID command mode Detected a contradiction for a command Contact the Hitachi Data Systems Support Center EX_INVCMD Invalid RAID command Detected a contradiction for a command Contact the Hitachi Data Systems Support Center EX_ENOGRP No such group The designated device or group name does not exist in the configuration file or the network address for remote communication does not exist Verify the device or group name and add it to the configuration file of the remote and local hosts EX_UNWCOD Unknown function code Detected a contradiction for a command Retry your operation after restart of the instance for CCI Contact the Hitachi Data Systems Support Center if the operation fails because of same error again EX_CMDIOE 9 10 Control command I O error A read write to the command device failed with an I O error Troubleshooting Refer to the host syslog file and investigate the cause of the error If the problem persists collect the log information of HORCM HORCM_LOG and contact the Hitachi Data Systems Support Center Hitachi Command Control Interface User and Reference Guide Error code EX_CM
496. uration definition files when specifying a virtual storage machine by HORCM_VCMD Example of the configuration definition files HORCMO The underlined parts indicate the information that needs to modify from the file of the old model CCI functions 3 47 Hitachi Command Control Interface User and Reference Guide ke KKK KKK HORCMO on PHOST kK KK HORCM_MON ip address service poll 10ms timeout 10ms NONE horcmo 1000 3000 H RKKKKEEKRK FOr HORCM CMD x xk kkkkkk kkk HORCM CMD dev name CMD 367000 dev rdsk HORCM VCMD redefine Virtual DKC Serial as unitIDs 365000 HORCM_LDEV Ora dev1 365000 02 00 hil Ora dev2 365000 02 01 hil H E Ekk kkk KKK For HORCM INST KKK KKK KR RRR kkk kk HORCM_INST E dev group ip address service Ora 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 ke KKK KKK HORCM1 on RHOST KK KK HORCM_MON ip address service poll 10ms timeout 10ms NONE horcm1 1000 3000 H RKKKKKEK FOr HORCM CMD xx kk kkk kkk HORCM CMD dev name CMD 368000 dev rdsk HORCM VCMD redefine Virtual DKC Serial as unitIDs 366000 HORCM_LDEV Ora dev1 366000 02 00 hil Ora dev2 366000 02 01 hil H ke RRR RR KKK For HORCM INST KKK KK KK KR RR KR RK HORCM_INST 7 dev_group ip address service Ora PHOST horcm0 The raidqry command display example raidqr
497. us Async The specified LDEV is used on the system disk Get Command Status 9 42 Async LDEV is not blocked Troubleshooting Hitachi Command Control Interface User and Reference Guide raidcom initialize Idev Error message Get Command Status Executing Async Async Error code SSB1 SSB2 Description The specified LDEV is a CC XRC attribute device Get Command Status Async The specified LDEV is used as the primary volume of a GAD pair Get Command Status Async The specified LDEV is used as the secondary volume of a GAD pair Get Command Status Async The formatting operation cannot be done because the encryption value of the key number that is set to encryption ECC is invalid Get Command Status Async The formatting operation cannot be done because the check sum of the encryption key is not coincident Get Command Status Async The LDEV is in shredding Get Command Status Async The operation cannot be done because LDEV is now expanding Get Command Status Async The operation cannot be done because the virtual disk space is blocked CMDRJE Executing The specified LDEV is used in another operation Get Command Status Async The parity group of the target LDEV is in the state of correction copy CMDRJE Executing The parity group or the external volume group to which the specified
498. used by the CCI commands must be referenced via the paired logical volume names or the group names Using CCI with ShadowImage and TrueCopy CCI allows you to perform ShadowImage and TrueCopy operations by issuing ShadowImage and TrueCopy commands from the UNIX PC server host to the RAID storage system ShadowImage and TrueCopy operations are nondisruptive and allow the primary volume of each volume pair to Data replication operations with CCI 6 3 Hitachi Command Control Interface User and Reference Guide remain online to all hosts for both read and write operations Once established ShadowImage and TrueCopy operations continue unattended to provide continuous data backup There are specific requirements for using ShadowImage and TrueCopy in high availability HA configurations UNIX PC servers in HA configurations normally support disk duplication functions to enhance disk reliability for example mirroring provided by the LVM or device driver RAID5 or an equivalent function provided by the LVM UNIX PC servers also feature hot standby and mutual hot standby functions in case of failures on the server side However mutual hot standby for disaster recovery has not yet been achieved since it requires the remote mirroring function ShadowImage provides the mirroring function within the storage system For detailed information about ShadowImage operations please see the Hitachi ShadowImage User Guide for your storage system TrueCopy
499. using the in band or out of band method of CCI command execution For details about global active device see the Global Active Device User Guide For details about the CCI command options and display results for global active device operations for example PHY_LDEV VIR_LDEV see the Command Control Interface Command Reference GAD secondary volume GAD pair operations from CCI are restricted Release the S VOL Disable attribute of the GAD secondary volume and then perform the GAD pair operations i Note Ifyou set the S VOL Disable attribute of Data Retention Utility to a ShadowImage operations Figure 6 2 ShadowImage system configuration on page 6 6 illustrates a ShadowImage configuration The ShadowImage commands also support the functionality that links the system operation for the purpose of volume backup among UNIX servers managed by the operating system For detailed information about the operational requirements and specifications for ShadowImage see the Hitachi ShadowImage User Guide for your storage system Following is a list of sample ShadowImage functions that can be executed using CCI commands e Pair creation Creates a new volume pair Volume pairs can be created in units of volumes or groups Data replication operations with CCI 6 5 Hitachi Command Control Interface User and Reference Guide Pair splitting Splits a volume pair and allows read and write access to the secondary volume Pair resynchroni
500. v rdsk c0t3d0 oradb oradev1 CL1 D 3 0 0 35013 17 New options for security raidscan find inst This option registers the device file name to all mirror descriptors of the LDEV map table for CCI and permits the matching volumes on horem conf in protection mode It is started from etc horcmgr automatically You will not normally need to use this option This option issues an Inquiry to a device file from the result of STDIN Then CCI gets Ser and LDEV from the RAID storage system Subsequently CCI compares the Inquiry result to the contents of horcm conf and the result is stored within HORCM for the instance At the same time CCI shows the result of this option about the relation This option will also be terminated to avoid wasteful scanning after registration based on horcm conf because HORCM does not need the registration any more ioscan fun grep rdsk raidscan find inst DEVICE FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c0t3d0 oradb oradev1 CL1 D 3 0 35013 17 dev rdsk c0t3d0 oradb oradevl CL1 D 3 0 0 35013 17 Note When multiple device files share the same LDEV the first device file AN is registered to the LDEV map table raidscan find verify MU This option shows the relation between group on horcm conf and Device_File registered to the LDEV map tables from DEVICE_FILE of STDIN 7 10 Data protection operations with CCI Hitachi Command Control Interface User and Reference Guide
501. v_group dev_name Serial LDEV MU ora data0 64035 ora data1 64035 ora data2 64046 ora data3 64046 R eeeennne For HORCM_INST CEE HORCM_INST dev_group ip_address service ora PHOST horcmO H For UR of multiple DKC HORCM_CTQM dev_group interval 10ms mode 300 Remote Server RM HORCMO Hitachi Command Control Interface User and Reference Guide 6 53 6 54 2 UR 2x1 HORCMO on production HORCM_MON ip_address service poll 10ms timeout 10ms NONE horemO 1000 3000 gpireeneneees For HORCM_CMD srenhnareennnrre UnitID 0 Serialt 64034 1 Serial 64045 CMD 64034 devirdsk CMD 64045 devirdsk ireeenneren For HORCM_LDEV RARAAERRAATERRRR f iini For HORCM_INST ee HORCM_INST dev_group ip address service ora RHOST horcm0 aeer For UR of multiple DKC HORCM_CTQM dev_group interval 10ms mode 300 ora Production Server RM HORCMO on Remote ip_address service poll 10ms timeout 10ms NONE horcm0 1000 3000 jeneeeennne For HORCM_CMD aaaerennnneeennn y CMD 64046 dev rdsk bainineiciaiaiaeial For HORCM_LDEV wenannwennnneree 64046 1 400 64046 1 401 64046 2 402 64046 2 403 ee For HORCNM_INST ER HORCM_INST tdev_group ip_address service ora PHOST horcmO H For UR of multiple DKC HORCM_CTQM dev_group interval 10ms mode 300 ora Remote Server RM HORCMO Data replication operations
502. v_id lt ldev gt ssid lt value gt Creating LDEVs Creates LDEVs by specifying parity groups Specifies only 3390 V for the emulation type raidcom add ldev parity_grp_id lt gno sgno gt ldev_id lt ldev gt capacity lt size gt offset_capacity lt size gt cylinder lt size gt emulation 3390 V location lt lba gt mp_blade_id lt mp gt Formatting LDEVs Formats created LDEVs raidcom initialize ldev ldev_id lt ldev gt operation lt type gt Creating LDEV nicknames arbitrarily Creates LDEV nicknames This operation is optional Provisioning operations with CCI raidcom modify ldev ldev_id lt ldev gt ldev_name lt ldev naming gt 5 29 Hitachi Command Control Interface User and Reference Guide Operation overview Configuring MP blades of LDEVs Description Configures MP blades of created LDEVs Executed command raidcom modify ldev ldev_id lt ldev gt mp_blade_id lt mp gt Displaying a LDEV information Displays an information of created LDEV and confirms an execution result of the command raidcom get ldev ldev_id lt ldev gt cnt lt count gt key lt keyword gt Creating the pool for the Hitachi Dynamic Provisioning for mainframe Creates the pool for the Hitachi Dynamic Provisioning for mainframe raidcom add dp_ pool pool_id lt pool ID gt pool_name lt pool naming gt pool_n
503. vice The command device of external storage system that is mapped as a command device of the local storage system is called as remote command device By issuing a command to the remote command device the operation at the external storage system is realized The remote command device is defined by the Storage Navigator For more information see the Hitachi Universal Volume Manager User Guide CCI and the SCSI command interface 2 6 When CCI commands are converted into a special SCSI command format a SCSI through driver that can send specially formatted SCSI commands to the RAID storage system is needed As a result OS support for CCI depends on the OS capabilities It is necessary to use a read write command that can easily be issued by many UNIX PC server platforms For example ioctl can be used for the following platforms HP UX Linux Solaris Windows IRIX64 OpenVMS and zLinux SCSI command format used Use a RD WR command that can be used with special LDEVs since they should be discriminated from the normal RD WR command Recognition of the control command area LBA The host issues control commands through the raw I O special file of a special LDEV Since the specific LU command device receiving these commands is viewed as a normal disk by the SCSI interface the OS can access its local control area The RAID storage system must distinguish such accesses from the control command accesses Normally several megabytes of
504. vice defined in the Please confirm that the Port 227 within the RAID configuration file does Target ID LUN are defined not have a mapping to correctly under HORCM_DEV a real LUN and target in the configuration file ID within the RAID storage system EX_INVRCD Invalid return Wrong return code Contact the Hitachi Data 226 code Systems Support Center EX_VOLCUR S VOL currency Currency check error Check the volume list to see 225 error for S VOL Cannot if an operation was directed guarantee identical to the wrong S VOL data on S VOL EX_VOLCUE Local volume The volume specified Please confirm the pair 224 currency error with the SVOL status of the local volume takeover command is _ using the pairdisplay not the same as the P command VOL EX_VOLCRE Local and remote The combination of Please confirm the pair 223 volume currency the volumes specified status of remote and local error with Swap takeover is volumes using the unsuitable pairdisplay command EX_UNWERR Unknown error Wrong error code Contact the Hitachi Data code Systems Support Center EX_ENOCTG Not enough CT When creating Please create a pair with 217 groups in RAID TrueCopy Async UR or cutting the number of the ShadowImage group on the configuration volume CTGID could files or make already not be registered due existing group and the target to being beyond the group the same CTGID max number of CT Please confirm already groups for an async existin
505. when paired logical volume names and group names are given to them The configuration definition file describes the correspondence between the physical volumes used by the servers and the paired logical volumes and the names of the CCI software environment Hitachi Command Control Interface User and Reference Guide remote servers connected to the volumes See the Command Control Interface Installation and Configuration Guide for instructions on creating the CCI configuration definition file Figure 2 11 Configuration definition of paired volumes on page 2 13 illustrates the configuration definition of paired volumes tion definition fil ia sternal MS Configuration definition file G1 Oradb1 P1 T1 L1 G1 Oradb1 P3 T2 L2 G1 HOSTB i G2 Oradb2 P2 T2 L3 Special file G1 HOSTA G2 Oradb3 P2 T2 L4 G2 HOSTC P3 72 L2 G1 Oradb1 Paired logical volume Oradb2 P4 T1 L1 Explanation of symbols Pn Port name Tn Target ID HOST C Configuration definition file Ln LUN number G2 Oradb2 P4 T1 L1 Special file G2 Oradb3 P4 T1 L2 G2 HOSTA Figure 2 11 Configuration definition of paired volumes Configuration file example UNIX based servers Note that at the beginning of a line indicates a comment HORCM_MON ip address service poll 10ms timeout 10ms HST1 horcm 1000 3000 HORCM_CMD unitID 0 seq 30014 dev_name dev_name dev_name dev rdsk cotodo unitID 1 seq
506. with the group operations device group creation deletion copy group creation deletion is not performed When deleting a copy group e Ifa copy group is deleted the association of two device groups is deleted However the actual pair status the consistency group ID and others are not changed not affected Even if the pair status in the copy group is not single and the copy group is deleted the copy group deletion processing is performed e If an LDEV is deleted from a device group associated as a copy group the relevant LDEVs are deleted from all the associated copy groups e A copy group defines the relationship of device groups Therefore it is not possible to specify an LDEV and remove it from the copy group e Regardless of the pair status copy status it is possible to exclude LDEVs from device groups associated as a copy group The contents of the following operations that can be executed for a copy group are expressed hereafter with its use cases 1 Copy group creation 2 LDEV addition to copy group CCI functions 3 35 Hitachi Command Control Interface User and Reference Guide 3 LDEV deletion from copy group 4 Copy group deletion 5 Pair operation by specifying a copy group Note The following symbols are used in the use cases described hereafter C symplex volume Cc D gt device group g s copy group paired volume Copy group creation Specifying two device groups and creating a copy group
507. wnership MP Blade of external volume raidcom modify external _grp external_grp_id lt gno sgno gt mp_blade_id lt mp gt Add external path raidcom port add path path_grp lt path group gt lt port gt external_wwn lt wwn strings gt Delete external path raidcom port delete path path_grp lt path group gt lt port gt external _wwn lt wwn strings gt Display external path information raidcom get path path_grp lt path group gt Stop the usage of external path raidcom disconnect path path_grp lt path group gt port lt port gt external_ wwn lt wwn strings gt Restore the external path raidcom check _ext_storage path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt Define SSID Provisioning operations with CCI raidcom add ssid rcu lt serial gt lt mcu gt lt rcu gt lt id gt ssid lt ssid gt raidcom delete ssid rcu lt serial gt lt mcu gt lt rcu gt ssid lt ssid gt 5 11 Hitachi Command Control Interface User and Reference Guide Operation type Mainte nance Description Add WWN of host path adapter Corresponding command raidcom add hba_wwn port lt port gt name gt hba_wwn lt WWN strings gt lt host group Delete WWN of host path adapter raidcom delete hba_wwn port lt port gt lt host group name gt hba_wwn lt WWN strings gt Set nickname for
508. wo storage systems Two hosts connected to two storage systems also allows the most flexible disaster recovery plan because both sets of data are administered by different hosts This guards against storage system failure as well as host failure The CCI instances of separate hosts are connected via the LAN so that they can maintain awareness of each other Each RAID storage system has a command device that communicates with each CCI instance independently Each storage system contains the primary volumes of its connected CCI instance and the secondary volumes of the other CCI instance located on a different host in this case Host machines that can be paired When you perform a pair operation the version of CCI should be the same on the primary and secondary sites As a particular application uses HORC users sometimes use a HORC volume as the data backup volume for the server In this case CCI requires that the CCI instance correspond to each OS platform that is located on the secondary site for the pair operation of data backup on the primary servers of each OS platform However it is possible to prepare only one server at a secondary site by supporting CCI communications among different OSs including the converter for ittle endian vs big endian Figure 2 10 CCI communication among different operating systems on page 2 12 represents CCI s communication among different OSs and Table 2 1 Supported CCI HORCM communication on page 2 1
509. wwn lt wwn_strings gt Specifying nickname To operate per group group multiple WWNs for SPM control into one group raidcom add spm_group port lt port gt spm_group lt group name gt lt nick name gt Checking the SPM information Display the setting state of SPM by specifying WWN or the SPM name raidcom get spm_wwn port lt port gt hba_wwn lt wwn_strings gt spm_name lt nick_ name gt Display the SPM information by specifying the SPM group name raidcom get spm_group port lt port gt spm_group lt group name gt Displaying the monitoring information of the prioritized WWN or the non prioritized WWN Display the monitoring information by specifying WWN or the SPM name raidcom monitor spm_wwn hba_wwn lt wwn_strings gt spm_name lt nick_name gt Display the monitoring information by specifying the SPM group name raidcom monitor spm_group spm_group lt group_name gt Changing the threshold or the upper limit value of the non prioritized WWN Change the threshold or the upper limit value of the non prioritized WWN by specifying WWN or the SPM name raidcom modify spm_wwn port lt port gt spm_priority lt y n gt limit_io limit_kb limit_mb lt value gt hba_wwn lt wwn_strings gt spm_name lt nick_name gt Change the threshold or the upper limit value of the non prioritized WWN by specifying the SPM group n
510. xecuting an asynchronous command the raidcom get command_status command is terminated after completing all the asynchronous command processing When an error occurs by executing asynchronous command the error information such as the total number of errors or error code SSB1 and SSB2 is provided After executing the asynchronous command execute raidcom get command_status command to check the 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 and subsequent occurrences only the number of the error occurrence is stored with no error code Therefore before executing an asynchronous command reset the error information in the storage system using the raidcom reset command_status command You can check the information in SSB1 and SSB2 by using the raidcom get error_message command In a part of asynchronous command processing the multiple commands received by the host are executed at a time Therefore the total number of errors may not correspond with the unexecuted commands If the error occurred in asynchronous commands verify the system configuration by the reference commands For details about the reference commands see Available provisioning operations on page 5 5 When executing an asynchronous command execute a command or a script with the following procedures 1 Execute a raidcom reset command_status command
511. xisting 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 definition file or not if the target port information does not exist in the configuration definition file the error is not detected The commands as the target of the check are shown below e raidcom modify port port lt port gt port_speed lt value gt loop_id lt value gt topology lt topology gt security_switch lt y n gt port_attribute lt port attribute gt e raidcom add external_grp path_grp lt path group gt external_grp_id lt gnosgno gt port lt port gt external_wwn lt wwn strings gt lun_id lt lun gt emulation lt emulation type gt clpr lt clpr gt CCI functions Hitachi Command Control Interface User and Reference Guide e raidcom add path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt e raidcom delete path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt e raidcom check_ext_storage path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt e raidcom disconnect path path_grp lt path group gt port lt port gt external_wwn lt wwn strings gt e raidcom add rcu rcu lt serial gt lt mcu gt lt rcu gt lt id gt ssid lt ssid gt cu_free lt serial gt lt id gt lt pid gt mcu_port lt port gt
512. y 1 No Group Hostname HORCM ver Uid Serial Micro ver Cache MB L Sts raidmanager 01 31 03 00 0 66000 80 01 00 00 81920 Specifying a virtual storage machine by command options Configuration definition file settings when specifying a virtual storage machine by command options 3 48 This topic shows configuration definition file settings with the global virtualization function when specifying a virtual storage machine by command options For details on other parameters see Configuration definition file on page 2 12 e HORCM_CMD CCI functions Hitachi Command Control Interface User and Reference Guide Specify a volume belonging to meta_resource in VSP G1000 as the command device CCI obtains the virtual storage machine information defined in VSP G1000 via the specified command device and configure the virtual storage machine components When you specify a volume in the virtual storage machine as the command device in the system configuration with the global virtualization function you cannot start CCI e HORCM_LDEV Specify volumes to be copied Serial numbers of the virtual storage machine and virtual LDEV IDs must be specified You cannot specify the volumes with HORCM_DEV in the system configuration with the global virtualization function Specify the volumes with HORCM_LDEV e HORCM_INST Specify an IP address and a service name of the remote host as it is for not using the global virtualization function Example
513. ync Error code Executing 2EF3 Description The specified parameter is invalid Check the Command Control Interface Command Reference Table 9 49 SSB codes that are returned by raidcom add rcu command raidcom add rcu Error code Error message Baa Description sync SSB1 SSB2 CMDRJE Executing 2E00 3001 The value of CU on the RCU exceeds the effective range CMDRIJE Executing 2E00 3005 Invalid product ID or path registration ID Get Command Async 2E00 3008 Command cannot be executed because the Status parameter of specified RCU is invalid Get Command Async 2E00 3009 Command cannot be executed because all the CU Status numbers in the RCU is not unified at the path that is specified creation or deletion CMDRJE Executing 2E00 3200 The value of port on the side of RCU is invalid CMDRJE Executing 2E00 7100 The CU number is out of effective range Get Command Async Status CMDRJE Executing 2E00 8400 The value of specified port is invalid Get Command Async Status Get Command Async 2E10 3101 Failed to establish a path or the deletion Status operation The following factor can be thought e Input parameter is invalid e Port status or the MP Blade status is in the state of abnormal e Cable is not connected correctly e Port is specified incorrectly Get Command Async 2E11 8004 The operation cannot be done because the Status microcode is being changed CMDRJE Exe
514. zation Resynchronizes a split volume pair based on the primary volume The primary volume remains accessible during resynchronization Pair resynchronization with restore option Resynchronizes a split pair based on the secondary volume reverse resync The primary volume is not accessible during resync with restore option Event waiting Used for waiting for the completion of a volume pair creation or resynchronization to check the pair status Pair status display and configuration confirmation Displays the pair status and configuration of the volume pairs this can also be used for checking the completion of a pair creation or pair resynchronization Operation Operation Management Management Server Server Primary Secondary secondary primary volume volume Pair splitting Figure 6 2 ShadowImage system configuration ShadowImage duplicated mirroring 6 6 Duplicated mirroring of a single primary volume is possible when the ShadowImage feature is used Duplicated mirror volumes can be specified up tp the maximum quantity 3 The duplicated mirror volumes of the P VOL are expressed as virtual volumes using the mirror descriptors MU 0 2 in the configuration diagram as shown below Data replication operations with CCI Hitachi Command Control Interface User and Reference Guide Fes eeseee ee see see Se See See See Ses ees SSeS Ses Sse Sess Group name oradb r te ee I I Group name oradb 1 Volume A V

Hitachi Command Control Interface

Contents

Download Pdf Manuals

Related Search

Related Contents