Hitachi Unified Storage VM Block Module

Transcription

1 Hitachi Unified Storage VM Block Module System Operations Using Spreadsheets FASTFIND LINKS Contents Product Version Getting Help MK-92HM

2 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. (hereinafter referred to as "Hitachi") and Hitachi Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems"). Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without notice and assume no responsibility for its use. This document contains the most current information available at the time of publication. When new and/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 may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information about feature and product availability. Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems agreements. The use of Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems. 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. ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems. AIX and IBM are registered trademarks or trademarks of International Business Machines Corporation. All other trademarks, service marks, and company names are properties of their respective owners. Microsoft product screen shots reprinted with permission from Microsoft Corporation. ii

3 Contents Preface vii Intended audience viii Product version viii Release notes viii Document revision level viii Changes in this revision viii Referenced documents viii Conventions ix Convention for storage capacity values x Accessing product documentation x Getting help x Comments xi 1 Spreadsheet operation overview Processing spreadsheets Spreadsheet operations LUN Manager LUN Expansion Universal Volume Manager About Command Line Interface About Configuration File Loader Resources that can be executed for each function Configuring CLI CLI requirements CLI configuration workflow Setting up CLI directories and files Installing the JRE Editing the Java security policy Creating user authentication files Preparing CLI command files iii

4 CLI termination codes Common requirements and procedures Spreadsheet file formatting requirements Opening spreadsheet files Saving spreadsheet files Working with CLI spreadsheets Workflow for CLI-based spreadsheets Obtaining the CLI-based spreadsheet files Editing the CLI-based spreadsheet Validating the CLI-based spreadsheet Running the CLI-based spreadsheet Running the CFLSET command Running the CFLGET command Working with CFL spreadsheets CFL-based spreadsheet workflow Exporting system settings to a spreadsheet Setting up the CFL-based spreadsheet for editing Editing the CFL-based spreadsheet Importing and validating a CFL-based spreadsheet Running a CFL-based spreadsheet LUN Manager operations Supported operations and workflow LUN Manager's CFL spreadsheet format About function tags About definitions Editing the spreadsheet Changing port settings Configuring host groups Configuring WWNs Configuring LU paths Changing command device settings LUN Expansion operations Supported operations and workflow Prerequisite information Example of basic spreadsheet format Command types and operation tags Editing templates Retrieving LDEV information iv

5 Example output Creating LUSE volumes Example spreadsheet Releasing LUSE volumes Example spreadsheet Universal Volume Manager operations Supported operations and workflow Prerequisites for installing CLI Example of basic spreadsheet format Command types and operation tags Editing templates Retrieving SSID information Retrieving external-volume group information Retrieving external volume information Mapping external volumes with multiple LDEVs Specifying LDEV Capacity Mapping an external volume with one LDEV Disconnecting an external volume Restoring an external volume Deleting external volume mapping Moving external volumes to another path group Moving external volumes to a new path group Universal Replicator for Mainframe operations Supported operations and workflow Required prerequisites Example of basic spreadsheet format Command types and operation tags Editing templates Retrieving pair information Example of retrieved pair tag information Creating pairs Suspending pairs Example of suspending pairs Resynchronizing pairs Example Releasing pairs Executing spreadsheets Troubleshooting Command Line Interface errors v

6 A Configuration File Loader GUI reference A-1 Configuration File Loader window A-2 Glossary Index vi

7 Preface This document describes and provides instructions for using spreadsheets to perform operations on the Hitachi Unified Storage VM (HUS VM) storage system. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes. This preface includes the following information: Intended audience Product Version Release notes Document revision level Changes in this revision Referenced documents Conventions Convention for storage capacity values Accessing product documentation Getting Help Comments Preface vii

8 Intended audience Product version Release notes This document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who are involved in installing, configuring, and operating the HUS VM storage system. Readers of this document should meet the following requirements: You should have a background in data processing and understand RAID storage systems and their basic functions. You should be familiar with the HUS VM storage system, and you should have read the Hitachi Unified Storage VM Block Module Hardware User Guide. You should be familiar with the Storage Navigator software for HUS VM, and you should have read the Hitachi Storage Navigator User Guide. You should be familiar with the software used to create, edit, and manage spreadsheets (such as Microsoft Excel). This document revision applies to HUS VM microcode x or later. The Hitachi Unified Storage VM Release Notes provide information about the HUS VM microcode (DKCMAIN and SVP), including new features and functions and changes. The Release Notes are available on the Hitachi Data Systems Portal: Document revision level Revision Date Description MK-92HM September 2012 Initial release MK-92HM December 2012 Supersedes and replaces MK-92HM MK-92HM October 2013 Supersedes and replaces MK-92HM Changes in this revision Revised CLIset command and termination code examples. See Examples of the batch file for the CFLSET command and Example of a CLI termination code reference. Referenced documents Hitachi Unified Storage VM (HUS VM) documents: Hitachi Storage Navigator User Guide, MK-92HM7016 Hitachi Universal Volume Manager User Guide, MK-92HM7020 Hitachi ShadowImage User Guide, MK-92HM7013 viii Preface

9 Conventions Hitachi Unified Storage VM Block Module Provisioning Guide, MK- 92HM7012 Hitachi TrueCopy User Guide, MK-92HM7018 Hitachi Universal Replicator User Guide, MK-92HM7019 This document uses the following typographic conventions: Convention Description Bold Italic Indicates the following: Text in a window or dialog box, such as menus, menu options, buttons, and labels. Example: On the Add Pair dialog box, click OK. Text appearing on screen or entered by the user. Example: The -split option. The name of a directory, folder, or file. Example: The horcm.conf file. Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Angle brackets are also used to indicate variables. Monospace Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb < > angle brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Italic is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Meaning Description Tip Helpful information, guidelines, or suggestions for performing tasks more effectively. Note Calls attention to additional information. Caution Failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to data). Preface ix

10 Icon Meaning Description WARNING Failure to take or avoid a specified action can result in severe conditions or consequences (for example, loss of data). Convention for storage capacity values Physical storage capacity values (disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 KB 1,000 (10 3 ) bytes 1 MB 1,000 KB or 1,000 2 bytes 1 GB 1,000 MB or 1,000 3 bytes 1 TB 1,000 GB or 1,000 4 bytes 1 PB 1,000 TB or 1,000 5 bytes 1 EB 1,000 PB or 1,000 6 bytes Logical storage capacity values (logical device capacity) are calculated based on the following values: Logical capacity unit Value 1 KB 1,024 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Getting help The Unified Storage VM user documentation is available on the Hitachi Data Systems Portal: Check this site for the most current documentation, including important updates that may have been made after the release of the product. 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: x Preface

11 Comments Please send us your comments on this document: 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. Thank you! Preface xi

12 xii Preface

13 1 Spreadsheet operation overview This chapter provides information and instructions for using spreadsheets for HUS VM storage system operations. This topic discusses the software and operations that can be run with spreadsheets. Processing spreadsheets Spreadsheet operations About Command Line Interface About Configuration File Loader Resources that can be executed for each function Spreadsheet operation overview 1 1

14 Processing spreadsheets You can make large-scale changes or perform various operations on a large scale and at a scheduled time by running spreadsheets against HUS VM. An operation is executed when you edit a spreadsheet and run it from the command prompt or file loader. By using the program-specific operation tags and parameters that correspond to the software, you can schedule a disparate range of operations or changes to a system's configuration. Changes and operations using spreadsheets are supported by the following Hitachi software products: LUN Manager (LUNM) LUN Expansion (LUSE) Universal Volume Manager (UVM) Two of these software products LUN Expansion and Universal Volume Manager provide their own spreadsheet templates. Templates are meant to be edited to your specific requirements and then run. LUN Manager spreadsheets are created when you export system information using Storage Navigator CFL. Spreadsheets, after you have written or edited them, are validated and run using either CFL or the Command Line Interface (CLI). These methods are not interchangeable; you use the method supported by the product. Instructions for editing, validating, and running spreadsheets for the supported software are provided. Spreadsheet operations LUN Manager The following topics describe the operations you can perform with each program's spreadsheet, and the required method for executing the spreadsheet. Spreadsheets for LUN Manager are operated using CFL. You can use spreadsheets to add, change, or delete the following settings: Configuration settings, which include: Arbitrated loop-physical address (AL-PA) Data transfer speed (host speed) Topology LUN security Host group settings WWN settings Path settings Command device settings 1 2 Spreadsheet operation overview

15 LUN Expansion Spreadsheets for LUN Expansion are operated using the Command Line Interface (CLI). You can use spreadsheets to perform the following operations: Create LUSE volumes. Get information about LDEVs that can be combined into LUSE volumes. Get information about LDEVs that have been part of LUSE volumes. Release LUSE volumes. Universal Volume Manager Spreadsheets for Universal Volume Manager are operated using the CLI. You can use spreadsheets to perform the following operations: Retrieve SSID information Retrieve external group information Retrieve external volume information Map external volumes with one or more LDEVs Disconnect an external volume Restore an external volume Delete the mapping to an external volume Move one or more external volumes from one path group to another existing path group, or to a new group path. About Command Line Interface The Command Line Interface is a Storage Navigator function. CLI files must be downloaded and configured manually. The CLI provides commands for retrieving, validating, and running spreadsheets. CLI commands are run from a command prompt for the following spreadsheets: LUN Manager Universal Volume Manager The CLI must be set up prior to use. See Configuring CLI on page 2-1 for details. About Configuration File Loader Configuration File Loader (CFL) is a Storage Navigator software application that is installed with Storage Navigator. With CFL, you import and export LUN Manager spreadsheet files, validate the imported spreadsheet, view errors, and then run the spreadsheets on the current storage system. Spreadsheet operation overview 1 3

16 Resources that can be executed for each function Storage Navigator secondary window shows all the resources in the storage system. When you execute each function in the Storage Navigator secondary window, verify the resource group ID in the Basic Information Display dialog boxes, and then execute the operations for the resources assigned to the user account. When you use the functions described in this manual, the resources for each operation must satisfy the specific conditions. For details on the conditions of the resources, see the Hitachi Unified Storage VM Block Module Provisioning Guide. 1 4 Spreadsheet operation overview

17 2 Configuring CLI You check and run spreadsheets using Command Line Interface (CLI) commands for Universal Volume Manager and LUN Expansion operations. Setup is required before using the CLI. LUN Manager uses a Configuration File Loader (CFL). No configuration is necessary for a CFL spreadsheet. CLI requirements CLI configuration workflow Setting up CLI directories and files Installing the JRE Editing the Java security policy Creating user authentication files Preparing CLI command files Configuring CLI 2 1

18 CLI requirements CLI requirements include the following: Storage Navigator Set up the Storage Navigator CLI on a computer that can access Storage Navigator. Spreadsheet software or a text editor (Microsoft Excel is recommended) JAR file for the Storage Navigator CLI Java security policy file JRE User authentication file Permissions for the CLI commands, shown below. Table 2-1 CLI commands and corresponding permissions CLI command CFLCHK CFLGET CFLSET Built-in permission Storage Administrator (view) role. Storage Administrator (view) role. User must hold all the roles below. Storage Administrator (Initial Configuration) Storage Administrator (System Resource Management) Storage Administrator (Provisioning) Storage Administrator (Performance Management) Storage Administrator (Local Copy) Storage Administrator (Remote Copy) CLI configuration workflow The workflow for setting up CLI consists of the following procedures: 1. Copy and set up CLI files. See Setting up CLI directories and files on page 2-2 below. 2. Install the Java Runtime Environment (JRE). See Installing the JRE on page Edit the Java security policy file. See Editing the Java security policy on page 2-4 for details. 4. Create a user authentication file. See Creating user authentication files on page 2-5. Setting up CLI directories and files To install a CLI on a computer with access to Storage Navigator: 1. Create an installation directory to store CLI files. 2. Insert the CD into the CD-ROM drive. 3. Copy the CD's /CFLCLITool directory to the newly created directory. 2 2 Configuring CLI

19 The CLI installation directory contains the following files and subdirectories: CFLCLITool\JSanCLI.jar: CLI JAR file CFLCLITool\java.policy: Java policy file used for Storage Navigator CLI CFLCLITool\sample\: CLI command files. Copy the files to the same directory as the SanCLI.jar file. CFLCLITool\template\: templates for spreadsheets. Installing the JRE Storage Navigator is provided as a Java application program. To use Storage Navigator CLI on JRE 1.5, the Java Runtime Environment (JRE) is required. JRE with support for additional languages is recommended. The dialog for selecting "Support for Additional Languages" does not appear in JRE 1.6. To use a CLI on JRE 1.6, install the setup file with the default settings. 1. Download the JRE setup file from 2. Start the JRE setup file. 3. If the Security Alert dialog box opens, review the displayed information and click Run. The License Agreement dialog box displays. 4. Review the license agreement, select Custom setup and click Accept. The Custom Setup dialog box displays. Figure 2-1 License Agreement dialog box on JRE Click the Support for Additional Languages icon and select This feature will be installed on local hard drive. Configuring CLI 2 3

20 Figure 2-2 Custom Setup dialog box JRE Click Next. The Browser Registration dialog box appears. 7. Select the browsers you want to register with Java(TM) Plug-In and click Next. Installation begins. When completed, the Complete dialog box displays. 8. Click Finish. Editing the Java security policy The Java security policy must be changed in order to run CLI commands. The Java application runs on the Web browser, and communicates with the attached HUS VM storage systems. Use the policy file that CLI provides as a user policy file. If you use this policy file, the security policy changes only when you execute the CLI commands. The policy file is stored in the CLI installation directory. Edit the default policy file (java.policy) a. In the /CFLCLITOOL folder, locate and open java.policy with a text editor. b. Add the following: grant { }; permission java.security.allpermission; For more information about the policy file, see the Java documentation. 2 4 Configuring CLI

21 Creating user authentication files A user authentication file is required for each CLI user. 1. Log in to Storage Navigator using a storage administrator account. 2. From /CFLCLITool/sample, copy one of the following and paste in the /CFLCLITool directory. (This is the same directory in which the JSanCLI.jar is located.) For Windows: mkatfile.bat For UNIX: mkatfile.sh 3. On UNIX systems, if you have a shell program installed in a directory other than /bin, open mkatfile.sh and change #! /bin/csh in the first line to the directory where the shell program is installed (such as /usr/ bin/csh). 4. From the command prompt, change directories to the destinationfolder/cflclitool directory. 5. Run the batch file as follows: mkatfile SVP-ip-address user-id password > myauthentication.txt For UNIX, enter.sh after mkatfile (that is, mkatfile.sh). Specify the following items: SVP-ip-address: specify the IP address of the SVP. To use an IPv6 address, enclose the IPv6 address in square brackets [ ]. user-id: specify the user ID of the storage administrator. password: specify the storage administrator password. When you execute the command, a user authentication file named myauthentication.txt is created in the current directory. For example: In this example for Windows, myauthentication.txt is created using the IP address ( ), user ID (administrator), and password (adminpassword). mkatfile administrator adminpassword >myauthentication.txt In this example for Windows, myauthentication.txt is created using the IP address (fe80::20a:e4ff:fe8f:20b5), user ID (administrator), and password (adminpassword). mkatfile [fe80::20a:e4ff:fe8f:20b5] administrator adminpassword >myauthentication.txt You can change this file name. However, you must use single-byte characters for the file name and use a literal file extension,.txt. If you rename the file, make sure also to change the name of the user authentication file in the.bat file. After the user authentication file is created, set the appropriate access authority for it using your operating system's security feature. Configuring CLI 2 5

22 Preparing CLI command files The directory and filenames of the command batch files are shown below (the same directory as JSanCLI.jar). Both Windows and UNIX files are stored in the same directory. Table 2-2 Batch files for running CLI commands Directory File name Description CFLCLITool\sample CFLCHK.bat Windows CFLCHK.sh UNIX CFLGET.bat Windows CFLGET.sh UNIX CFLSET.bat Windows CFLSET.sh UNIX Validates the spreadsheet to be applied to the CFLSET command. Retrieves storage system information. Applies the contents of the spreadsheet to the storage system. If you change files or directories that are shown in column one of the following table, you must also make the corresponding change or changes that are shown in column two. Table 2-3 File or directory changes If you change... If you rename the user authentication file name... If you move the directory where you store the user authentication file to a directory other than "/CFLCLITool"... If your operating system is UNIX and you install a shell program in a directory other than "/bin"... You must also change... Change.txt in each CLI command file to the file name that you specified. Change this directory location in each file to the relative or absolute path. Only single-byte characters can be specified for a path or file name. No double-byte characters can be specified. Change #! /bin/csh in the first line in each file to your installation directory (such as /usr/bin/csh). Examples of the batch file for the CFLSET command The following table shows examples of the batch file for the CFLSET command. Table 2-4 Examples of the batch file for the CFLSET command Operating system Batch file Windows java -jar -Djava.security.policy=java.policy - Djava.rmi.server.useCodebaseOnly=false JSanCLI.jar myauthentication.txt CFLSET %1 %2 UNIX #! /bin/csh java -jar -Djava.security.policy=java.policy - Djava.rmi.server.useCodebaseOnly=false JSanCLI.jar myauthentication.txt CFLSET $1 $2 2 6 Configuring CLI

23 CLI termination codes When a command completes, a CLI termination code shows the results of the operation. Even when the termination codes terminate normally, make sure to check for errors in the spreadsheet. The following table shows the meanings of the CLI termination codes that are returned when a CLI command (batch file) is executed. Table 2-5 CLI termination code meanings Code Meaning 0 Command completed successfully. Other than 0 An error occurred. You can use a CLI termination code reference in your batch file that causes a message to display at the command prompt. The CLI termination code references that you can use are shown in the following table. Table 2-6 CLI termination code references Batch file or Shell script Termination code reference Windows batch file %errorlevel% UNIX Bourne shell script %? UNIX C shell script %Status Example of a CLI termination code reference The following example shows a reference to a CLI termination code that can be used in a Windows batch file. When the batch file is run and a CLI termination code of 0 is returned, the command prompt displays, "COMMAND SUCCESSFUL". If a CLI termination code other than 0 is returned, the command prompt displays, "COMMAND FAILED". java -jar -Djava.security.policy=java.policy - Djava.rmi.server.useCodebaseOnly=false JSanCLI.jar myauthentication.txt CFLSET %1 %2 if %errorlevel% NEQ 0 echo COMMAND FAILED. if %errorlevel% EQU 0 echo COMMAND SUCCESSFUL. Configuring CLI 2 7

24 2 8 Configuring CLI

25 3 Common requirements and procedures Although the workflows for running Command Line Interface (CLI) spreadsheets and Configuration File Loader (CFL) spreadsheets are different, format requirements and opening and closing procedures are similar. Spreadsheet file formatting requirements Opening spreadsheet files Saving spreadsheet files Common requirements and procedures 3 1

26 Spreadsheet file formatting requirements You set up a spreadsheet file based on specifications required by CLI commands or CFL. Requirements for the detailed content of each spreadsheet are based on the software functionality, and are described in the product-related modules later in this document. Table 3-1 File requirements for CLI, CFL-based spreadsheets Item Requirement File type Text file File name Extension must be ".spd". Maximum number of letters for the file name is 32 including the extension. The following symbols cannot be used for the file name: \ / :, ; *? " < > and space. Maximum number of letters in directory path: - CLI spreadsheets: CFL spreadsheets: 255 Maximum number of rows CLI spreadsheets: 65,536 CFL spreadsheets: 400,000 End-of-line character Maximum number of letters in a row Case-sensitivity Format Comments Linefeed code must be put in the end of each row. CLI spreadsheet: 512 including linefeed CFL/LUN Manager spreadsheet: 200 Not case-sensitive, except for LUN Manager's WWN and host group settings. CLI/CLF spreadsheets The first line contains the spreadsheet version, which is defined for each software. * Separate each parameter with a comma (,). Tab and spaces before or after a comma are ignored. CLI spreadsheets only Add a semicolon (;) at the end of the line where a parameter is written. Begin a comment line with the # character. Comments can consist of characters in any language. * Updating the microcode version of the storage system might change the version of the CLI/CFL spreadsheet. This can affect the number of items or the range of available values. Check the spreadsheet version before editing a spreadsheet. Opening spreadsheet files As best practice, open a spreadsheet file from within a spreadsheet program. Microsoft Excel is recommended for both CLI-based and CFLbased spreadsheet files. 3 2 Common requirements and procedures

27 Saving spreadsheet files When you finish editing a spreadsheet, save the file. This is important for the file validation process. Common requirements and procedures 3 3

28 3 4 Common requirements and procedures

29 4 Working with CLI spreadsheets This topic provides instructions for editing, validating and then running CLIbased spreadsheets. Workflow for CLI-based spreadsheets Obtaining the CLI-based spreadsheet files Editing the CLI-based spreadsheet Validating the CLI-based spreadsheet Running the CLI-based spreadsheet Working with CLI spreadsheets 4 1

30 Workflow for CLI-based spreadsheets Following is the workflow for using a CLI spreadsheet: 1. Obtain a clean CLI spreadsheet by copying and renaming the spreadsheet template. 2. Open the CLI spreadsheet in a spreadsheet program. Open the spreadsheet with the settings specified in Configuring CLI on page 2-1. This also applies to closing and saving the spreadsheet. 3. Edit the spreadsheet. Each spreadsheet has its own operations, functions, and parameters. 4. Go to a command prompt and use the CFLCHK command to validate the spreadsheet file. 5. Correct any errors by re-editing and revalidating the spreadsheet. 6. Run the spreadsheet using the CLI commands, CFLSET or CFLGET. Obtaining the CLI-based spreadsheet files Find and save a copy. Spreadsheet templates for LUN Expansion (LUSE) and Universal Volume Manager are located in your installation directory's / CFLCLITOOLS/template folder. See Setting up CLI directories and files on page 2-2. Original template names for CLI-based spreadsheets are shown in the following table. Table 4-1 Template names for CLI-based spreadsheets Program Product Universal Volume Manager LUN Expansion (LUSE) Template ExternalStorage_AddVolumeSetting2_def_.spd ExternalStorage_AddVolumeSetting_def_.spd ExternalStorage_CheckPath-RestoreVolume_def_.spd ExternalStorage_DeleteVolume_def_.spd ExternalStorage_DisconnectVolume_def_.spd ExternalStorage_DividePathGroup_def_.spd ExternalStorage_Get_def.spd ExternalStorage_UnitePathGroup_def_.spd LUSE_Expansion_def_.spd LUSE_Get_def.spd LUSE_Release_def_.spd Editing the CLI-based spreadsheet Edit and then validate the spreadsheet before running it. Prerequisite information When opening a spreadsheet file, make sure you have reviewed Opening spreadsheet files on page 3-2 for important information. 4 2 Working with CLI spreadsheets

31 When closing a spreadsheet file, make sure to review Saving spreadsheet files on page 3-3. Settings must be strictly formatted to prevent errors during validation. Adhere to the formatting requirements in Spreadsheet file formatting requirements on page 3-2. Follow the program-specific parameter requirements and guidelines in the following topics: LUN Expansion operations on page 7-1 Universal Volume Manager operations on page 8-1 Validating the CLI-based spreadsheet After editing a spreadsheet, you must use the CFLCHK command to validate the spreadsheet before you run the CFLSET command. To validate the CLI-based spreadsheet, go to the command prompt (Start>Run>"cmd") and enter the following: CFLCHK input-file-name output-file-name For example: enter CFLCHK LUSE_ReleaseOperation.spd LUSE_ReleaseOperation_Result.spd In this example, the spreadsheet, LUSE_ReleaseOperation.spd, is checked, and the results are placed in the file, LUSE_ReleaseOperation_Result.spd. Note: For UNIX, add.sh to CFLCHK (that is, CFLCHK.sh). Operand input-file-name output-file-name Description The spreadsheet you want to verify. Include relative or absolute path. Maximum length is 240 characters. The output file name. Include relative or absolute path. Maximum length is 240 characters. Valid parameters read "Normal end" at the end of their lines. Note: Processing suspends when you right-click the command prompt window while the command prompt is not in Quick Edit Mode. To resume processing, press the Esc key, or left-click the command prompt window. Processing also suspends if you left-click when the command prompt is in Quick Edit Mode. To resume processing, press the Esc key, or right-click the command prompt window. If CLI processing is suspended for a long period, RMI time-out occurs and your log-in status is cancelled. When you resume processing in this case, an error ( ) occurs. To avoid this error, resume processing by opening a new command prompt window. Working with CLI spreadsheets 4 3

32 Correcting errors in a CLI-based spreadsheet If you find errors in the results, re-edit the spreadsheet and run the CFLCHK command again. Use the following guidelines to check for errors in the results file: In the results file, the code at the end of the declaration line, (xxxxyyyyy), indicates part codes and error codes. For details, see the Hitachi Storage Navigator Messages. Check errors from the bottom up. Find the last row with an error first. If a lower layer has an error, the upper layers also display an error even though the upper layer may have no error. If a higher layer has an error, parameters in the lower layers are not verified. After correcting the error in the upper layer, re-run CFLCHK to check for errors further down. Example 1 #!Version 06_01_00,CLI_LUSE,Get,;Error( ) [SerialNumber] 64569,;Normal end [LUSE] #^,;Error( ) GET_ALL,; This example shows two errors: In the declaration (top row). The (xxxx-yyyyy) following "Error" is a code-error code, which are described in Hitachi Storage Navigator Messages. In the Suspend-Pair operation tag, identified in the row below beginning begins with #^. In this example, an error occurred in the LUSE tag Example 2 #!Version 06_01_00,CLI_LUSE,VolumeOperation,;Error( ) [SerialNumber] 64601,;Normal end [Expansion] 00,00,00,;Error( ) +,00,00,01,;Error( ) This example shows three errors: In the declaration (top row). The (xxxx-yyyyy) following "Error" is a code-error code, which are described in Hitachi Storage Navigator Messages. Note that the Serial Number operation tag returned a "Normal end" result. "Normal end" indicates that a line is correct. Errors occurred in the first and second row in the Expansion tag. Example Working with CLI spreadsheets

33 The following example shows errors when the parameters are in a hierarchical structure. #!Version 06_01_00,CLI_ExternalStorage,VolumeOperationFibre,;Error( ) [SerialNumber] 65536,;Normal end [AddVolumeSetting] 1,1A,60060E8004F81370,0000,E1-1,Normal,00,OPEN- V,Disable,Enable,;Error( ) +,1B,60060E8004F81371,0001,;Error( ) +,+,00,00,00,96000,0004,; To identify where an error occurred in a hierarchical structure, find the last row with an error. In this example, an error occurred in the second layer that begins with +,. Parameters in the lower layers than the layer with an error are not verified and no execution results are displayed for them. When the errors are corrected, running CFLCHK again will show errors in subsequent lines, if they exist. Running the CLI-based spreadsheet After a CLI-based spreadsheet has been edited and validated, it is ready to run. Spreadsheets for LUN Expansion (LUSE) and Universal Volume Manager are run using the following CLI commands: Use the CFLSET command to change system settings or perform an operation. Use CFLGET to retrieve system information to a file. Running the CFLSET command Run CFLSET to change the configuration settings you have altered in the spreadsheet, or to perform other operations, such as run pair commands. A results file is generated when you run CFLSET, from which you can check whether the operation completed successfully. 1. At a command prompt, change directories to the location of the spreadsheet file. 2. Enter the following: CFLSET input-file-name output-file-name where: input-file-name is the name of the spreadsheet file with relative or absolute path. Maximum length is 240 characters. output-file-name is the name of the results file with relative or absolute path. Maximum length is 240 characters. For example: CFLCHK LUSE_ReleaseOp.spd LUSE_ReleaseOp_Result.spd On UNIX, add ".sh" to CFLSET, that is, CFLSET.sh. Working with CLI spreadsheets 4 5

34 3. Check the results file to verify that the operation completed successfully. Errors that may occur are: A communication error. Volumes or pairs that are not ready to accept changes. Another user is working with the storage system in Storage Navigator in Modify mode. If you have an error, correct the condition and run the command again. Running the CFLGET command Run CFLGET to retrieve storage system information and save it in a file. A results file is generated when you run CFLGET, from which you can check whether the retrieval completed successfully. 1. At a command prompt, change directories to the location of the spreadsheet file. 2. Enter the following: CFLGET input-file-name output-file-directory where: input-file-name is the name of the spreadsheet file with relative or absolute path. Maximum length is 240 characters. output-file directory is the name of the directory in which the results file and the spreadsheet file (output) are saved. Include the relative or absolute path. Maximum length is 150 characters. On UNIX, add ".sh" to CFLGET, that is, CFLGET.sh. For example: CFLGET ExtStorage_VolumeOperation.spd C:\CFLoutput 4 6 Working with CLI spreadsheets

35 5 Working with CFL spreadsheets You can use spreadsheets to automate changes to the storage system's configuration. This topic provides instructions and information for exporting, editing, importing, validating, and running CFL-based spreadsheets. Only LUN Manager uses CFL-based spreadsheets. CFL-based spreadsheet workflow Exporting system settings to a spreadsheet Setting up the CFL-based spreadsheet for editing Editing the CFL-based spreadsheet Importing and validating a CFL-based spreadsheet Running a CFL-based spreadsheet Working with CFL spreadsheets 5 1

36 CFL-based spreadsheet workflow You can perform the following operations using a CFL-based spreadsheet: 1. Obtain the spreadsheet by using CFL to export system information to a file. 2. Open the spreadsheet in a spreadsheet program. Open the spreadsheet with the settings specified in Configuring CLI on page 2-1. Do not use a tool that modifies the format of the file. This also applies to closing and saving the spreadsheet. 3. Edit the spreadsheet. Each spreadsheet has its own operations or functions, and parameters. 4. Validate the spreadsheet file by importing the edited file back into CFL. Error checking is performed during import. 5. Correct any errors by re-editing and revalidating the spreadsheet. 6. Run the spreadsheet in CFL. Exporting system settings to a spreadsheet The first step in setting up an editable spreadsheet is to export system settings from CFL to a spreadsheet file. LUN Manager is the only program product supported by CFL at this time. 1. In Storage Navigator, select Actions > Other Functions > Configuration File Loader from the menu. 2. Change to Modify mode by clicking the icon. 3. In the Configuration File Loader window, click Select Sheet and then select the product whose settings you want to export. 4. Click Export. If you use a Web browser for UNIX systems, the Download Manager dialog box may display when you click Export. If this occurs, close the Download Manager dialog box and continue the operation. 5. In the export dialog box, type or browse to the path where you want to export the file. A file name is supplied, which you can change if desired. Consult Spreadsheet file formatting requirements on page 3-2 for file naming requirements. Figure 5-1 Export dialog box 6. Click Export. The spreadsheet file is exported to the specified location. Continue to the next section to prepare and edit the spreadsheet. After editing, see Importing and validating a CFL-based spreadsheet on page Working with CFL spreadsheets

37 Setting up the CFL-based spreadsheet for editing Though spreadsheet settings have been exported from CFL, the file is not ready to edit yet. The following shows how to set up the exported file for editing, and provides other requirements and recommendations. 1. Open the spreadsheet. See Opening spreadsheet files on page 3-2 for important information. 2. Select and copy all of the settings in the spreadsheet, except the declaration line, and paste them on the right side of the spreadsheet. The editable spreadsheet must adhere to the following: Figure 5-2 Current and new settings 1st column to 7th column: Current settings area. Do not edit. 8th column to 10th column: Blank columns. 11th column to 17th column: New settings area for editing. Although you may want to change some, but not all, settings, you must copy and paste all of the current settings to the new settings area. Any setting that is omitted is deleted when the spreadsheet is run. The following table shows sample function tags and parameters with existing and new locations. Table 5-1 Sample function tags and parameters Column Existing (no editing) Function Tag [Port] [HostGroup] WWN [LUN] [LDEV] 1st Port Port Port Port Ldkc 2nd Security Switch Group Id Group Id Group Id Cu 3rd AL-PA Group Name WWN LunId Ldev 4th Fabric Host Mode Nickname Ldkc Cmd.Dev 5th Connection Option[0:31] Blank Cu Cmd.Sec 6th Channel speed Option[32:63] Blank Ldev Cmd.Usr 7th Blank Option[64:95] Blank Blank Cmd.Grp 8th Blank Blank Blank Blank Attribute * Working with CFL spreadsheets 5 3

38 Column Function Tag [Port] [HostGroup] WWN [LUN] [LDEV] Column 9th 10th New 11th Port Port Port Port Ldkc (for editing) 12th Security Switch Group Id Group Id Group Id Cu 13th AL-PA Group Name WWN LunId Ldev 14th Fabric Host Mode Nickname Ldkc Cmd.Dev 15th Connection Option[0:31] Blank Cu Cmd.Sec 16th Channel speed Option[32:63] Blank Ldev Cmd.Usr 17th Blank Option[64:95] Blank Blank Cmd.Grp * For external volumes, #External is output. The exported spreadsheet contains 10 columns. Editing the CFL-based spreadsheet You edit a spreadsheet to add, change, or delete system settings. Editing a spreadsheet requires the correct formats. Follow these guidelines when editing: Make sure the spreadsheet is set up for editing. See Setting up the CFLbased spreadsheet for editing on page 5-3 Consult the general formatting requirements in Spreadsheet file formatting requirements on page 3-2. Consult function tags and parameters in LUN Manager operations on page Add the word "Change" in the Declaration row in column Edit parameters only in the new settings. 5 4 Working with CFL spreadsheets

39 Figure 5-3 Example CFL-based spreadsheet 3. In the new settings area, edit parameters but not the index. A definition consists of the index and the parameter. The index is fixed for each function tag. Working with CFL spreadsheets 5 5

40 4. Do not duplicate an index within the same function tag. 5. Place a definition between function tags or between a function tag and the end of the file. 6. A function tag may require fewer than seven columns. In this case, leave the unused columns blank. The version of the spreadsheet may also determine the number of parameters for a function tag. Importing and validating a CFL-based spreadsheet After the spreadsheet is edited, import it back into CFL, which validates the spreadsheet during import. 1. Go to Storage Navigator and select Actions > Other Functions > Configuration File Loader from the menu. 2. Change to Modify mode by clicking the icon. 3. In the Configuration File Loader window, click Select Sheet and then select the product whose spreadsheet you want to import. 4. Click Import. If you use a Web browser for UNIX systems, the Download Manager dialog box may display when you click Import. If this occurs, close the Download Manager dialog box and continue the operation. 5. In the dialog box, type the path and spreadsheet file name, or browse to the path and select the.spd spreadsheet file. Figure 5-4 Import dialog box 6. Click Import. When a spreadsheet is imported, CFL verifies the formats. A spreadsheet can be rejected, in which case CFL displays a message with a message code. The following errors can display when a file is rejected. The file name is incorrect (such as the extension is not ".spd", or the file name exceeds the maximum number of letters). The spreadsheet file is not in text file format but is a binary file. The first row of the spreadsheet (the declaration line) is not correctly written, or the stated program product is not installed. There is no function tag in the spreadsheet. A spreadsheet must have at least one function tag. The number of letters in a row exceeds the limit. 7. In the Select Tag box, select any function tag with an asterisk to see errors. 5 6 Working with CFL spreadsheets

41 The Select Tag box is enabled when a spreadsheet is accepted by CFL. At the same time, a second level of error-checking takes place, in which the existing function settings are compared to the new settings. The Select Tag list consists of the spreadsheet's function tags; a function with errors is shown with an asterisk (*). 8. In the Error Information area, check errors for the selected function. Figure 5-5 Error Information area with LUN function errors Each line shows the affected row in the spreadsheet, the error code, the column in the spreadsheet, and a description. Errors that may occur are: A function tag is not supported in the current spreadsheet. Make sure you have not changed a function tag. A parameter value is incorrect or omitted. The range for a parameter is incorrect. Parameter values must be entered in the following ranges: LDKC: 00 CU: 00-3F LDEV: 00 - FF LUN: FF Group ID: 00 - FE Host Mode: 00-4F See Hitachi Storage Navigator Messages for error code information. 9. Edit the spreadsheet to correct errors, then re-import. When all errors are corrected, the spreadsheet imports with no errors. The word, "Ready", displays below the Error Information list, and the Apply button is enabled. Continue to the next section to run the spreadsheet. Running a CFL-based spreadsheet When a spreadsheet is imported into CFL with no errors, "Ready", displays at the bottom right of the Error Information list. This indicates that the spreadsheet is ready to be run. Working with CFL spreadsheets 5 7

42 To run the spreadsheet, click Apply. The changes made in the spreadsheet are applied to the system, unless one of the following conditions is present: There is no difference between the current configuration and the configuration on the imported spreadsheet. The spreadsheet is accepted, but no operation is performed. You are trying to delete a LUN that is needed to process I/O. All the resource group IDs that are set to the storage system are not assigned to the user account who logs in to Storage Navigator. 5 8 Working with CFL spreadsheets

43 6 LUN Manager operations Spreadsheets for LUN Manager are used to change storage system settings. LUN Manager-specific formats, operation tags, and parameters for the individual operations are explained in this topic. Also, specific editing requirements and recommendations are explained. General file naming, opening and closing, editing, validation, and running of the spreadsheets are explained in Working with CFL spreadsheets on page 5-1. Supported operations and workflow LUN Manager's CFL spreadsheet format Editing the spreadsheet Changing port settings Configuring host groups Configuring WWNs Configuring LU paths Changing command device settings LUN Manager operations 6 1

44 Supported operations and workflow You can add, change, or delete the following LUN Manager settings using spreadsheets: Change these port settings: arbitrated loop-physical address (AL-PA), data transfer speed (host speed), and topology. You can also change the LUN Security setting. Add, change, or delete host groups. Add, change, or delete WWN information. Add, delete, or change LU paths. Change command device settings. LUN Manager spreadsheet operations are validated and run using the Configuration File Loader. The spreadsheet workflow consists of the following: Export the system setting information using CFL to a spreadsheet file. Edit the settings with any additions, changes, and/or deletions. Import the edited spreadsheet back into CFL, which validates the contents immediately. Run the spreadsheet in CFL. Spreadsheet settings may be applied concurrently to multiple logical volumes in a Logical Disk Controller (LDKC). LUN Manager's CFL spreadsheet format LUN Manager's spreadsheet is exported from CFL. The basic spreadsheet format is shown in the following example: #!Version Version number,program product,process mode,; Function tag Definitions Italics indicate variables that must be input by the user. Table 6-1 Format variables Variables Description First line declaration line #! Indicate the declaration line. Cannot be changed. Version Indicates that the Remote Method Invocation (RMI) version number follows. Cannot be changed. Followed by a space. Version number Remote Method Invocation (RMI) version. Followed by a comma, no space. Program product "LUN". Followed by a comma, no space. Process mode "Change". Indicates adding, changing, deleting. The downloaded spreadsheet has no process mode. Second line 6 2 LUN Manager operations

45 Variables Description About function tags Function tag [Port], [HostGroup], [WWN], [LUN], [LDEV], Indicates the function, in the above order, whose definitions follow. Enclosed in brackets. See About function tags on page 6-3, below, for more information. Line following function tag Definitions System configuration data. See About definitions on page 6-4 for more information. Function tags describe the type of function. Note the following when working with function tags: Function tags must be written at the beginning of a row. Maintain the order that function tags appear in the exported spreadsheet file. The definitions under function tags are applied to the storage system one at a time in the order they appear in the spreadsheet. Definitions in earlier function tags may affect succeeding function tags. For example, if you deleted a host group in the [HostGroup] function tag, the path definitions related to the deleted host group would also be automatically deleted. If you then write new definitions for the deleted path in the [LUN] tag or the [WWN] tag, which appear later in the spreadsheet, an error would occur. If a function tag does not need to be changed, delete it from the new area of the spreadsheet (see Setting up the CFL-based spreadsheet for editing on page 5-3). Definitions are deleted if the function tag remains in the spreadsheet with no new definitions. [Port], and [LDEV] tags do not support a delete operation. If no new definition is written for these functions an error occurs. Comments and definitions written in the same row as the function tag are ignored. The row after the function tag is a commented heading row that shows the required values. In the example below, Security Switch are the headings, separated by commas. Example: [Port] #Port, Security Switch Existing settings are written with #$ at the beginning of the line. These are comment rows and cannot be changed. Example: [LUN] #Port, Group Id, LunId, Ldkc, Cu, Ldev (items to be changed) #$1C,0,1,1,1,1 (existing settings row) LUN Manager operations 6 3

46 About definitions Definitions are the actual parameters you enter when editing the spreadsheet. You enter new definitions, change existing definitions, or delete them. Note the following when working with definitions: All editing occurs in the new-setting area of the spreadsheet. See Setting up the CFL-based spreadsheet for editing on page 5-3. You can add a new setting when the current setting is blank. A setting is blank when it has not been specified. Delete a setting by removing the parameter from the spreadsheet. Change current settings by entering a different parameter. The format must be the same as the existing setting. The following shows a LUN Manager spreadsheet with current and new settings. The right-hand side shows the new settings, which is the area you edit. Editing the spreadsheet Figure 6-1 Edited LUN Manager spreadsheet You edit the spreadsheet by adding, changing, and deleting the parameter definitions. After editing and validating, you run the spreadsheet to apply the changes. 1. Follow the procedures in Setting up the CFL-based spreadsheet for editing on page Follow the procedure in Opening spreadsheet files on page Follow procedures in Editing the CFL-based spreadsheet on page Use the values in the following sections for specific configuration settings. 6 4 LUN Manager operations

47 Changing port settings You set port information and change the security switch (LUN security) between Enable (ON) and Disable (OFF) by editing [Port] function parameters. [Port] function parameters can be changed, but not added or deleted. The following table lists the available definitions for the [Port] function. Table 6-2 Available [Port] function values Colum n Item Available values 11th (Index) 12th Port Set one of the following (Maximum number of ports is 48): 1A, 3A, 5A, 7A, 1B, 3B, 5B, 7B, 2A, 4A, 6A, 8A, 2B, 4B, 6B, 8B 1C, 3C, 5C, 7C, 1D, 3D, 5D, 7D, 2C, 4C, 6C, 8C, 2D, 4D, 6D, 8D 1E, 3E, 5E, 7E, 1F, 3F, 5F, 7F, 2E, 4E, 6E, 8E, 2F, 4F, 6F, 8F Security Switch (LUN Security) Enable or Disable (The default when the spreadsheet is exported) ON or OFF are also available as the set value when you write the spreadsheet. 13th AL-PA Set with hexadecimal numbers in one or two digits. 14th Fabric Enable or Disable (The default when the spreadsheet is exported)on or OFF are also available as the set value when you write the spreadsheet. 15th Connectio FCAL or PtoP n 16th Channel Set one of the following: Speed 8 Gbps settings 2, 4, 8, or Auto Settings for fibre channel that is noncompliant to 8 Gbps 1, 2, 4, or Auto Configuring host groups You can add, delete, or change host group settings when you edit [HostGroup] parameters. Note the following restrictions: You can delete the settings for host group 0 (zero), but the host group itself cannot be deleted. If you delete all the settings for host group 0, the settings revert to the default settings. When you delete a host group (other than host group 0), the WWN and path definition of that host group are automatically deleted. Thus, if you edit settings for a host group that is deleted in the [LUN] or [WWN] tag, an error will occur. The following table lists the available definitions for the [HostGroup] function. LUN Manager operations 6 5

48 Table 6-3 Available [HostGroup] function values Editable column Item Available value 11th (Index) Port One of the following can be set (Maximum number of ports is 48): 1A, 3A, 5A, 7A, 1B, 3B, 5B, 7B, 2A, 4A, 6A, 8A, 2B, 4B, 6B, 8B 1C, 3C, 5C, 7C, 1D, 3D, 5D, 7D, 2C, 4C, 6C, 8C, 2D, 4D, 6D, 8D 1E, 3E, 5E, 7E, 1F, 3F, 5F, 7F, 2E, 4E, 6E, 8E, 2F, 4F, 6F, 8F 12th Group Id 00 - FE. Set with hexadecimal numbers in one or two digits. 13th Group Name Up to 64 alphanumeric characters. Note the following when you specify a host group name: You can use up to 64 single-byte ASCII characters (letters, numerals, and symbols). However, you cannot use the following symbols: \ / :, ; *? " < > You cannot use blanks at the beginning or end of the host group name. The specification of the host group name is case-sensitive. (For example, hitachi and Hitachi are recognized as different host group names.) 14th Host Mode 00-4F. Set with hexadecimal numbers in one or two digits. See Host mode option on page 6-6, below, for more information. 15th Option[0:31] 0 - FFFFFFFF. Set with hexadecimal numbers in from one digit to 16th Option[32:63] eight digits*. 17th Option[64:95] The default value when the spreadsheet is exported is in eight digits. "0"s at the head of the number can be omitted when you set the value. Host mode option The host mode option consists of 96 flags (0 to 95), which are stored in bits of 32. The figure below shows the flags with option flag IDs from 0 to 31. Binary bit flags (option flags) are assigned to each ID (starting with 0). Every four binary bit flags are set as a group, which is converted to a hexadecimal number that represents the host mode option. Figure 6-2 Concept of host mode option 6 6 LUN Manager operations

49 The following figure shows an example in which the host mode option becomes "1AB30005". Figure 6-3 Example of host mode option Binary to the hexadecimal conversion is shown below. Table 6-4 Binary to hexadecimal conversion Binary number Hexadecimal number Binary number Hexadecimal number A B C D E F Write a host mode option in one or more digits (up to eight). "0"s at the head of the number can be omitted when you set the value. For example, "00000FE3" can be written as "FE3". The default value when the spreadsheet is exported is written in eight digits. Configuring WWNs You can add, delete, or change WWN information by editing [WWN] parameters. The following table lists items and values available for the [WWN] function. Table 6-5 Available configuration values for the [WWN] tag Column Item Available Values 11th (Index) Port One of the following can be set (Maximum number of ports is 48): 1A, 3A, 5A, 7A, 1B, 3B, 5B, 7B, 2A, 4A, 6A, 8A, 2B, 4B, 6B, 8B 1C, 3C, 5C, 7C, 1D, 3D, 5D, 7D, 2C, 4C, 6C, 8C, 2D, 4D, 6D, 8D 1E, 3E, 5E, 7E, 1F, 3F, 5F, 7F, 2E, 4E, 6E, 8E, 2F, 4F, 6F, 8F 12th (Index) Group Id 00 - FE. Set with hexadecimal numbers in one or two digits. 13th (Index) WWN Set with hexadecimal numbers in 16 digits. LUN Manager operations 6 7

50 Column Item Available Values 14th Nickname Up to 64 alphanumeric characters. Note the following when you specify a nickname: You can use up to 64 single-byte ASCII characters (letters, numerals, and symbols). However, you cannot use the following symbols: \ / :, ; *? " < > You cannot use blanks at the beginning or end of the nickname. The specification of the nickname is case-sensitive. (For example, hitachi and Hitachi are recognized as different host group names.) 15th to 17th Blank Configuring LU paths You can add, delete, or change LU path definitions by editing [LUN] parameters. The following table lists items and values available for the [WWN] function Table 6-6 Available configuration values for the [LUN] tag Column Item Available values 11th (Index) Port One of the following can be set (Maximum number of ports is 48): 1A, 3A, 5A, 7A, 1B, 3B, 5B, 7B, 2A, 4A, 6A, 8A, 2B, 4B, 6B, 8B 1C, 3C, 5C, 7C, 1D, 3D, 5D, 7D, 2C, 4C, 6C, 8C, 2D, 4D, 6D, 8D 1E, 3E, 5E, 7E, 1F, 3F, 5F, 7F, 2E, 4E, 6E, 8E, 2F, 4F, 6F, 8F 12th (Index) Group Id 00 - FE. Set with hexadecimal numbers in one or two digits. 13th (Index) LunId FF. Set with hexadecimal numbers in up to four digits. 14th Ldkc 00 15th Cu 00-3F. Set with hexadecimal numbers in one or two digits. 16th Ldev 00 - FF. Set with hexadecimal numbers in one or two digits. 17th Blank Changing command device settings You can change command device settings by editing [LDEV] function parameters. Though you can change, you cannot add or delete command device settings with the [LDEV] function. Also, note the following restrictions: An error occurs when the command device (Cmd.Dev) is Disable (OFF), and the command device security (Cmd.Sec), command device user authentication (Cmd.Usr), and command device group definition (Cmd.Grp) are Enable (ON). You can set the command device OFF, regardless of the existence of the LU path. 6 8 LUN Manager operations

51 You cannot change the remote command device setting. When the storage system setting is output to the spreadsheet, the remote command device setting is commented out with #$ at the beginning of the row. The colons that usually separate an LDEV's LDKC, CU, and logical volume numbers are changed to commas in the spreadsheet. For example: [LDEV] 00,00,01,Disable,Disable,,,,,, 00,00,01,Enable,Enable 00,01,01,Disable,Disable,,,,,, 00,01,01,Enable,Disable 00,02,01,Disable,Disable,,,,,, 00,02,01,Enable,Disable 00,03,01,Disable,Disable,,,,,, 00,03,01,Enable,Disable The following table lists the values available for the [LDEV] tag. Table 6-7 Available configuration values for the [LDEV] Tag Column Item Available value 11th (Index) Ldkc 00 12th (Index) Cu 00-3F. Set with hexadecimal numbers in one or two digits. 13th (Index) Ldev 00 - FF. Set with hexadecimal numbers in one or two digits. 14th Cmd. Dev Enable or Disable (The default when the spreadsheet is exported) 15th 16th 17th (Comman d Device) Cmd. Sec (Comman d Device Security) Cmd.Usr (User Authentica tion) Cmd.Grp (Device Group Definition) ON or OFF are also available as the set value when you write the spreadsheet. Enable or Disable (The default when the spreadsheet is exported) ON or OFF are also available as the set value when you write the spreadsheet. Enable or Disable (The default when the spreadsheet is exported) ON or OFF are also available as the set value when you write the spreadsheet. Enable or Disable (The default when the spreadsheet is exported) ON or OFF are also available as the set value when you write the spreadsheet. Caution: When configuration definitions are long, the [LDEV] tag might not be output in the exported spread sheet. In that case, add the LDEV tag and set the command device. Caution: You cannot specify an attribute in the 18th column because it is used only for outputting information. When changing settings, you must specify the 18th column as a blank. LUN Manager operations 6 9

52 6 10 LUN Manager operations

53 7 LUN Expansion operations Spreadsheets for LUN Expansion are used to retrieve volume information and create and release LUSE volumes. LUN Expansion-specific formats and parameters for the individual operations are provided in this module. Also, specific editing requirements and recommendations are provided. General file naming, opening and closing, editing and validation, and running of the spreadsheets are covered in Working with CLI spreadsheets on page 4-1. Supported operations and workflow Prerequisite information Example of basic spreadsheet format Editing templates Retrieving LDEV information Creating LUSE volumes Releasing LUSE volumes LUN Expansion operations 7 1

54 Supported operations and workflow You can perform the following LUN Expansion operations using spreadsheets: Retrieve information concerning existing LUSE volumes Retrieve information concerning unused but available LDEVs for use in a LUSE volume. Create LUSE volumes Release LUSE volumes Spreadsheet templates for these operations are provided with Storage Navigator. The spreadsheet workflow consists of the following tasks: Edit the spreadsheet template provided by Hitachi Data Systems. Templates are provided for each supported LUN Expansion operation. They allow you to quickly edit, verify, and run the spreadsheet. Validate the spreadsheet. If errors occur, re-edit the spreadsheet then validate again, until the spreadsheet is free of errors. Run the spreadsheet. This topic provides formats, operation tags, and parameters for the individual operations. File naming, opening and closing, validation, and running of spreadsheets are covered in Common requirements and procedures on page 3-1 and Working with CLI spreadsheets on page 4-1. Prerequisite information CLI must be installed, along with accompanying third-party files. See Configuring CLI on page 2-1 for details. All the resource group IDs that are set to the storage system must be assigned to the user ID that is set to the user authentication file of the Storage Navigator CLI when you use the spreadsheet for LUN Expansion. Example of basic spreadsheet format The following example shows the basic spreadsheet format. #!Version Version number, program product, type,; Operation tag Parameter Italics indicate variables that must be input by the user. Table 7-1 Format variables Variables Content First line declaration line 7 2 LUN Expansion operations

55 Variables Content Command types and operation tags The available operation tag depends on the command type, and the version number written in the spreadsheet depends on the operation tag. The following table shows the command types, related operation tags, and version numbers available for LUN Expansion. Table 7-2 LUN Expansion Command Types and Associated Operation Tags In addition to the operation tags shown in the table, the SerialNumber tag can also be used. It allows you to verify that the serial number in the spreadsheet matches the serial number of the storage system. SerialNumber is included in all spreadsheet templates. Editing templates #! Indicates the declaration line. Cannot be changed. Version number Depends on the operation tag. See Table 7-2 LUN Expansion Command Types and Associated Operation Tags on page 7-3. Program product "CLI_LUSE". Type Type of command. See the table in Command types and operation tags on page 7-3 for available types. Followed by a comma and semicolon, no space between (,;). Second line Operation tag Operation to be performed. See the table in Command types and operation tags on page 7-3. Enclosed in brackets. Third line Parameter LDEV data necessary for running the operation. Command Type Operation Tag Version Template Get LUSE 06_01_00 LUSE_Get_def.spd VolumeOperation Expansion 06_01_00 LUSE_Expansion_def_.spd Release LUSE_Release_def_.spd You edit the spreadsheet by inserting your system's specific settings in the appropriate parameters. 1. Templates are provided with Storage Navigator for the three LUN Expansion operations that can be performed with spreadsheets. Locate the desired template in the /CFLCLITOOLS folder on the microcode CD. 2. Follow the procedure in Setting up CLI directories and files on page Follow procedures in Editing the CLI-based spreadsheet on page Use the values in the following sections to make specific edits. LUN Expansion operations 7 3

56 When editing is completed, you will run CLI commands to validate and then run the spreadsheet. Retrieving LDEV information Use the Luse_Get_def.spd template to retrieve information from the system about LDEVs that are used in LUSE volumes, or about LDEVs that can be combined into LUSE volumes. The command is: [LUSE] GET_ALL Example output Output is saved to a file. The following example shows retrieved LDEV information. Note that LDEV information displays in layers. Layer Identifier Content Top None Top LDEV in the LUSE volume (00,00,00) Middle + Other LDEVs in the LUSE volume (00,00,01; 00,00,02) Bottom None LDEVs available for a LUSE volume (00:00:10, 00:01:00, 00:10:01) Also note that: Top and bottom layers have no identifier. The plus signs (+) identifies the middle layer. Each line displays an LDEV, identified by LDKC, CU, and LDEV numbers. This format is indicated in the comment lines, which begin with the pound sign (#). The text between commas populates a spreadsheet column. In the example above, in the top layer, "00" populates column A. In the middle layer, "+" populates column A, "00" populates column B, and so on. 7 4 LUN Expansion operations

57 Creating LUSE volumes Use the Luse_Expansion_def_.spd template to create LUSE volumes. The volumes to be created are layered similarly in the spreadsheet as the output for retrieving LUSE volume information. Note the following points when creating LUSE volumes: You can use between 2 and 36 LDEVs in a LUSE volume. Top layer LDEVs are arranged in ascending order. LDEVs for the LUSE volume must be arranged in ascending order. Example spreadsheet The example spreadsheet shows that three LUSE volumes are being created. There are two layers per LUSE volume to be created. The text between commas populates the spreadsheet column. In the example above, in the first line in the first LUSE volume to be created, "00" populates column A. In the second line, "+" populates column A, "00" populates column B, and so on. Releasing LUSE volumes Layer Identifier Content Top None Top LDEV in the LUSE volume (00,00,00) Bottom + Other LDEVs in the LUSE volume (00,00,01; 00,00,02) Use the Luse_Release_def_.spd template to release LUSE volumes. When you enter the volumes to be released, use the same layered order used for the Luse_Expansion spreadsheet in Creating LUSE volumes on page 7-5. LUN Expansion operations 7 5

58 Example spreadsheet The example spreadsheet shows that three LUSE volumes are being released. To release a LUSE volume, under the [Release] tag, add the top LDEV in the LUSE volume in the format of LDKC-number:CU-number:LDEVnumber. For multiple LUSE volumes, add the top LDEVs in ascending order based on the above numbers. The text between commas populate a spreadsheet column. In the example above, in the first line in the first LUSE volume to be released, "00" populates column A. In the second line, "+" populates column A, "00" populates column B, and so on. 7 6 LUN Expansion operations

59 8 Universal Volume Manager operations Spreadsheets for Universal Volume Manager retrieve system information and map volumes to the local system. This module provides Universal Volume Manager-specific formats and editing requirements. File naming and editing are covered in Working with CLI spreadsheets on page 4-1. Supported operations and workflow Prerequisites for installing CLI Example of basic spreadsheet format Editing templates Retrieving SSID information Retrieving external-volume group information Retrieving external volume information Mapping external volumes with multiple LDEVs Mapping an external volume with one LDEV Disconnecting an external volume Restoring an external volume Deleting external volume mapping Moving external volumes to another path group Moving external volumes to a new path group Universal Volume Manager operations 8 1

60 Supported operations and workflow You can use spreadsheets to perform the following Universal Volume Manager operations: Retrieve information about all SSIDs in the local system Retrieve information about external volume groups configured to the local system Retrieve information about external volumes in the local system Map external volumes with multiple or single LDEVs to the local system Disconnect an external volume from the local system Restore an external volume Delete the mapping to an external volume Move an external volume or volumes from one path group to another path group, or to move it to a new path. Spreadsheet templates for these operations are provided with Storage Navigator. The spreadsheet workflow consists of the following tasks: Edit the spreadsheet template provided by Hitachi Data Systems. Templates are prewritten for each supported Universal Volume Manager operation. They allow you to edit, verify, and run the spreadsheet. Validate the spreadsheet. If errors occur, you re-edit the spreadsheet then validate again, until the spreadsheet is free of errors. Run the spreadsheet. This module provides formats, operation tags, and parameters for the individual operations. File naming, opening and closing, editing, validation, and running of the spreadsheets are covered in Working with CLI spreadsheets on page 4-1. Prerequisites for installing CLI CLI must be installed, along with accompanying third-party files. See Configuring CLI on page 2-1 for prerequisites. Example of basic spreadsheet format The following example shows the basic spreadsheet format. #!Version Version number, program product, type,; Operation tag Parameter Italics indicate variables that must be input by the user. 8 2 Universal Volume Manager operations

61 Table 8-1 Format variables Variables Content First line declaration line #! Indicates the declaration line. Cannot be changed. Version number Depends on the operation tag. See Table 8-2 Command types and associated operation tags on page 8-3. Program product "CLI_ExternalStorage". Type Type of command. See the table in Table 8-2 Command types and associated operation tags on page 8-3 for available types. Followed by a comma and semicolon with no space between them (,;). Second line Operation tag Operation to be performed. See the table in Table 8-2 Command types and associated operation tags on page 8-3. Enclosed in brackets. Third line Parameter LDEV data necessary for running the operation. Command types and operation tags The command types and related operation tags available for Universal Volume Manager are provided in the individual spreadsheet templates as shown below. The Version Number differs according to the operation tag. Table 8-2 Command types and associated operation tags Type Operation tag Version number Template Get VolumeO perationfi bre SSID ExternalGroup MappedVolume 06_01_00 ExternalStorage_Get_def.spd AddVolumeSetting 06_01_00 ExternalStorage_AddVolumeSetting_def_.spd AddVolumeSetting2 06_01_00 ExternalStorage_AddVolumeSetting2_def_.spd DisconnectVolume 06_01_00 ExternalStorage_DisconnectVolume_def_.spd CheckPath-RestoreVolume 06_01_00 ExternalStorage_CheckPath- RestoreVolume_def_.spd DeleteVolume 06_01_00 ExternalStorage_DeleteVolume_def_.spd DividePathGroup 06_01_00 ExternalStorage_DividePathGroup_def_.spd UnitePathGroup 06_01_00 ExternalStorage_UnitePathGroup_def_.spd Universal Volume Manager operations 8 3

62 In addition to the operation tags shown in the table, the SerialNumber tag can also be used. It allows you to verify that the serial number in the spreadsheet matches the serial number of the storage system. SerialNumber is included in all spreadsheet templates. Editing templates You edit the spreadsheet template by inserting specific settings in the appropriate parameters. 1. Templates are provided with Storage Navigator. Locate the desired template in the /CFLCLITOOLS folder on the microcode CD. 2. Follow the procedure in Setting up CLI directories and files on page Follow procedures in Editing the CLI-based spreadsheet on page 4-2. You can use up to 32 alphanumeric characters to name the file; the character limit includes the file extension. Always change the file name of the copied template to avoid overwriting the original. 4. When making edits to a spreadsheet, use the value tables and descriptions that pertain to the template you want to use. The tables and descriptions follow this section. Retrieving SSID information Use the ExternalStorage_Get_def.spd template to retrieve LDEV and SSID information from the storage system. Information is returned concerning both internal and external volumes. The command is: [SSID] GET_ALL,; Output is saved to a file. The following table shows the information returned for the SSID tag: Table 8-3 SSID information retrieved Column Returned value Content A LDKC:CU:LDEV-LDEV The range of LDEV numbers to which the SSID is assigned. B SSID The SSID. Output example of SSID information retrieved [SSID] #LDKC:CU:LDEV-LDEV,SSID,; 00:00:00-FF,0004,; 00:01:00-FF,0005,; 00:02:00-FF,0006,; 00:03:00-FF,0007,; 8 4 Universal Volume Manager operations

63 Retrieving external-volume group information Use the ExternalStorage_Get_def.spd template to retrieve information regarding external-volume groups that are configured to the local storage system. The command is: [ExternalGroup] GET_ALL,; Output is saved to a file. The following table describes the information returned for the ExternalGroup tag. Table 8-4 External-volume group information retrieved Column Parameter Content A ExG External volume group number and its sequential number. Retrieving external volume information Use the ExternalStorage_Get_def.spd template to retrieve information regarding external volumes that are associated with the local storage system. The command to retrieve external volume information is: [MappedVolume] GET_ALL,; Output is saved to a file. The following table shows the information that is returned for the MappedVolume tag. Output parameter lines are layered as follows: Lines in the first layer have no identifier. Lines in the second layer begin with the plus sign (+). Lines in the third layer begin with two plus signs (++). Table 8-5 External volume information retrieved Column Parameter Content First layer Information about the external storage system. A Vendor Name of the vendor. B Product Name of the storage system. C SerialNumber Serial number of the storage system. Second layer Information about the external volume. A + Identifier B PathGroup Path group number. C ExG External volume group number and its sequential number. D Characteristic1 Identification number of the external volume. Universal Volume Manager operations 8 5

64 Column Parameter Content E Device Name of the storage system that is reported to the host by the external volume. F Attribute Normal: This volume is an external volume. R-CMD: This volume is a remote command device. G CacheMode Enable: Cache mode is set to Enable. Disable: Cache mode is set to Disable. H InflowControl Enable: Inflow control is set to Enable. Disable: Inflow control is set to Disable. I PathMode Single: The cross-storage system paths work in the Single mode. Multi: The cross-storage system paths work in the Multi mode. APLB: The cross-storage system paths work in the APLB mode. J Capacity Capacity of the external volume. This capacity is expressed in blocks. K Characteristic2 Extended identification number of the external volume. Third layer Information about the cross-storage system paths. A + Identifier. B + Identifier. C Port Port number of the local storage system. D WWN WWN of the external storage system. E LUN LU number of the external volume. Mapping external volumes with multiple LDEVs Use the ExternalStorage_AddVolumeSetting_def_.spd template to map external volumes to the storage system. With this template you can create multiple LDEVs in an external volume. To create one LDEV per external volume, see the next topic, Mapping an external volume with one LDEV on page 8-10 The operation tag is: AddVolumeSetting With this tag, you specify LDEV capacity in blocks, which results in an LDEV with a specified capacity (which can be used, for example, for creating a pair). Parameters are entered in the spreadsheet in hierarchical layers. The following table shows identifiers and content for each layer: 8 6 Universal Volume Manager operations

65 Table 8-6 AddVolumeSetting layers, identifiers, and content Layer Identifier Content Description First None Information about external volumes and the primary path Second + Information about alternate paths The following table shows the AddVolumeSetting parameters: Table 8-7 AddVolumeSetting parameters This layer is required. Specifies one row for each alternate path. Up to seven rows can be specified. It is recommended that you specify at least one alternate path. Third +,+ Information about LDEVs Specifies one row for each LDEV. Up to 2,048 rows can be specified. If you do not specify the third layer, no LDEVs will be created. Col. Param. Description Range of values Number of characters First Layer: Information about external volumes and the primary path. A PathGroup Path group number. 0 to decimal digits or less B Port Port number of the primary path. 1A to 8F 2 digits or less C WWN WWN of the primary path tofffffffff FFFFFFF 16 hexadecimal digits D LUN LU number set to the external volume to 0FFF 4 hexadecimal digits or less E ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ). F Attribute Normal: Maps an external volume. R-CMD: Maps a command device. Grp: 1 to VPG: 1 to 4096 Normal R-CMD Grp: 5 decimal digits or less VPG:4 decimal digits or less G CLPR CLPR that is used to access the external volume. 0 to 31 2 decimal digits or less H Emulation Emulation type of the external volume. OPEN-V 16 characters or less in ASCII format I CacheMode Enable: Sets cache mode to Enable. Enable N/A Disable: Sets cache mode to Disable. Disable J InflowContr ol Enable: Sets inflow control to Enable. Disable: Sets inflow control to Disable. Enable Disable Second Layer: Information about alternate paths. Specify the paths in the order of descending priorities. N/A N/A Universal Volume Manager operations 8 7

66 Col. Param. Description Range of values Number of characters A + Identifier N/A N/A B Port Port number of the alternate path. 1A to 8F 2 digits or less C WWN WWN of the alternate path to FFFFFFFFFFF FFFFF 16 hexadecimal digits Third Layer: Information about LDEVs to be created in an external volume. A + Identifier N/A N/A B + C LDKC LDKC number 00 to 01 2 hexadecimal digits or less D CU CU number 00 to 3F 2 hexadecimal digits or less E LDEV LDEV number. Specify a number that is not currently assigned. You can see whether a number is assigned by opening Storage Navigator and checking the LDEV tab on the Basic Information Display dialog box (File>Go>Basic Information). F Capacity Capacity of the LDEV in blocks. For instructions on calculating LDEV size in blocks, plus emulation considerations, see Specifying LDEV Capacity on page 8-9. G SSID SSID assigned to the range of the LDEV numbers. Use the SSID shown in the output file from the ExternalStorage_Get_def.spd spreadsheet for the range. 00 to FF 2 hexadecimal digits or less 1 to decimal digits or less 0004 to FFFE 4 hexadecimal digits or less Example of mapping external volumes with multiple LDEVs #!Version 06_01_00,CLI_ExternalStorage,VolumeOperationFibre,; [SerialNumber] 65536,; [AddVolumeSetting] 1,1A,60060E8004F81370,0001,E ,Normal,00,OPEN- V,Enable,Disable,; +,1B,60060E8004F81371,; +,+,00,00,00,96000,0004,; +,+,00,01,00,96000,0005,; +,+,00,02,00,96000,0006,; Keep in mind the following points: The external volume is configured as follows: 0001 is configured as a LUN discovered through the primary path. 1 is used for a path group number. E is configured for an external volume group (ExG). Two cross-storage system paths are configured as follows: 8 8 Universal Volume Manager operations

67 The primary path Port number on the local storage system: 1A WWN on the external storage system: 60060E8004F81370 The alternate path Port number on the local storage system: 1B WWN on the external storage system: 60060E8004F81371 Attributes of the external volume are configured as follows: Emulation type: OPEN-V Cache mode: Enable Inflow control: Disable CLPR: 00 LDEVs are configured as follows: Number of LDEVs: 3 Specifying LDEV Capacity LDEV number: 00:00:00, 00:01:00, 00:02:00 LDEV capacity: 96,000 blocks This topic explains how to specify LDEV capacity. Specify the value between and An LDEV is created at the beginning of a slot. If you specify the LDEV capacity indivisible by the slot size (512 blocks), an adjustment area is created between the end of the LDEV and the beginning of the next LDEV. The adjustment area cannot be used as an LDEV. Calculate the adjustment area using the following equation: Adjustment area capacity = ceiling[ldev capacity 512] 512 LDEV capacity In the equation, ceiling indicates that the value that is enclosed in brackets must be rounded up to the nearest whole number. Make sure that the capacity of the external volume is greater than or equal to the sum of the total capacity of all the LDEVs in the external volume plus the total capacity of the adjustment areas. The following figure shows an example of creating four LDEVs of 100,000 blocks each. In this case, the required capacity of the external volume is 401,056 blocks. Universal Volume Manager operations 8 9

68 Figure 8-1 When creating multiple LDEVs in an external volume Mapping an external volume with one LDEV Use the ExternalStorage_AddVolumeSetting2_def_.spd template to create an LDEV in an external volume. LDEV capacity is not specified. The created LDEV will have the same capacity as the external volume. You can also use this tag when you use existing data in the external volume after mapping. The operation tag is: [AddVolumeSetting2] Parameters are described in the following table. Parameters are entered in the spreadsheet in hierarchical layers. For details, see Table 8-6 AddVolumeSetting layers, identifiers, and content on page 8-7. The LDEV is created with the following settings (not mentioned in the table below). LDEV capacity: the same capacity as the external volume* Emulation type: OPEN-V Cache mode: Disable Inflow control: Disable Table 8-8 AddVolumeSetting2 parameters Col. Param. Description Range of values Number of characters First Layer: Information about external volumes and the primary path. A PathGroup Path group number. 0 to decimal digits or less B Port Port number of the primary path. 1A to 8F 2 digits or less 8 10 Universal Volume Manager operations

69 Col. Param. Description Range of values Number of characters C WWN WWN of the primary path tofffffffff FFFFFFF Disconnecting an external volume Use the ExternalStorage_DisconnectVolume_def_.spd template to disconnect an individual external volume. The operation tag is: DisconnectVolume 16 hexadecimal digits D LUN LU number set to the external volume to 0FFF 4 hexadecimal digits or less E ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ). F Attribute Normal: Maps an external volume. R-CMD: Maps a command device. Grp: 1 to VPG: 1 to 4096 Normal R-CMD Grp: 5 decimal digits or less VPG:4 decimal digits or less G CLPR CLPR that is used to access the external volume. 0 to 28 2 decimal digits or less Second Layer: Information about alternate paths. Specify the paths in the order of descending priorities. A + Identifier N/A N/A B Port Port number of the alternate path. 1A to 8F 2 digits or less C WWN WWN of the alternate path to FFFFFFFFFFF FFFFF Third Layer: Information about the LDEV to be created in the external volume. N/A 16 hexadecimal digits A + Identifier N/A N/A B + C LDKC LDKC number 00 to 01 2 hexadecimal digits or less D CU CU number 00 to 3F 2 hexadecimal digits or less E LDEV LDEV number. Specify a number not currently assigned. You can see whether a number is assigned by opening Storage Navigator and checking the LDEV tab on the Basic Information Display dialog box (File>Go>Basic Information). F SSID SSID assigned to the range of the LDEV numbers. Use the SSID shown in the output file from the ExternalStorage_Get_def.spd spreadsheet for the range. 00 to FF 2 hexadecimal digits or less 0004 to FFFE 4 hexadecimal digits or less Universal Volume Manager operations 8 11

70 Table 8-9 DisconnectVolume Parameters Column Parameter Description A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ) Range of values Grp: 1 to VPG: 1 to 4096 Number of characters 5 decimal digits or less VPG:4 decimal digits or less Restoring an external volume Use the ExternalStorage_CheckPath-RestoreVolume_def_.spd template to resume an individual external volume operation. The operation tag is: CheckPath-RestoreVolume Table 8-10 CheckPath-RestoreVolume Tag Parameters Column Parameter Description A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ). Range of values Grp: 1 to VPG: 1 to 4096 Number of characters Grp: 5 decimal digits or less VPG:4 decimal digits or less Deleting external volume mapping Use the ExternalStorage_DeleteVolume_def_.spd template to delete external volume mapping. See the prerequisite information for this operation in the Hitachi Universal Volume Manager User Guide. The operation tag is: DeleteVolume Table 8-11 DeleteVolume tag parameters Column Parameter Description A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ). Range of values Grp: 1 to VPG: 1 to 4096 Number of characters Grp: 5 decimal digits or less VPG:4 decimal digits or less 8 12 Universal Volume Manager operations

71 Moving external volumes to another path group Use the ExternalStorage_UnitePathGroup_def_.spd template to move all external volumes from one path group to another path group. The original path group is automatically deleted. The operation tag is: [UnitePathGroup] To move external volumes to a new path group, use the DividePathGroup tag. Parameters are entered in the spreadsheet in hierarchical layers. The following table shows identifiers and content for each layer. Table 8-12 UnitePathGroup layers, identifiers, and content Layer Identifier Content Description First None Information about the path group external volumes moving to Bottom + Information about the path group external volumes moving from This layer is required. Specifies one row for each alternate path. External volumes in two or more path groups can be moved to one path group by specifying two or more path groups. Parameters are described in the following table: Table 8-13 UnitePathGroup parameters Col. Param. Description Range of values # of characters First Layer: Information about the path group moving to. A PathGroup Path group number 0 to decimal digits or less Second Layer: Information about the path group moving from. A + Identifier N/A N/A B TargetPath Group Path group number 0 to decimal digits or less Moving external volumes to a new path group Use the ExternalStorage_DividePathGroup_def_.spd template to move one or more external volumes to a new path group. The original path group, if no other external volumes remain, is automatically deleted. The operation tag is: Universal Volume Manager operations 8 13

72 [DividePathGroup] To move an external volume to a different, existing path group, use the ExternalStorage_UnitePathGroup_def_.spd template. Parameters are entered in the spreadsheet in hierarchical layers. The following shows identifiers and content for each layer. Table 8-14 DividePathGroup Layers, Identifiers, and Content) Layer Identifier Content Description First None Information about the existing path group Second + Information about the new path group Third +,+ Information about the external volume or volumes to be moved This layer is required. This layer is required. Specifies one row for each external volume. External volumes in the same path groups can be moved to one path group by specifying two or more external groups. Parameters are described in the second table below. Table 8-15 DividePathGroup Parameters Column Paramete r Description Range of values Number of character s First Layer: Information about the path group moving from. A PathGroup Existing path group number 0 to Second Layer: Information about the new path group. A + Identifier B NewPathG roup New path group number 0 to Third Layer: Information about the external volume or volumes to be moved. A + Identifiers B + C ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E ). Grp:1 to VPG:1 to decimal digits or less 5 decimal digits or less Grp:5 decimal digits or less VPG:4 decimal digits or less 8 14 Universal Volume Manager operations

73 9 Universal Replicator for Mainframe operations Use Universal Replicator for Mainframe spreadsheets to perform pair operations. This topic provides Universal Replicator for Mainframe formats and parameters for the individual operations, as well as specific editing requirements and recommendations. General file naming, opening and closing, editing, validation, and running of the spreadsheets are covered in Working with CLI spreadsheets on page 4-1. Supported operations and workflow Required prerequisites Example of basic spreadsheet format Editing templates Retrieving pair information Creating pairs Suspending pairs Resynchronizing pairs Releasing pairs Executing spreadsheets Universal Replicator for Mainframe operations 9 1

74 Supported operations and workflow You can perform the following Universal Replicator for Mainframe operations with spreadsheets: Retrieve information for existing pairs Create pairs Suspend pairs Resume pairs Delete pairs Spreadsheet templates for these operations are provided with Storage Navigator. The spreadsheet workflow consists of the following tasks: Edit the spreadsheet template provided by Hitachi. Templates are prewritten for each supported operation. They allow you to quickly edit, verify, and run the spreadsheet. Validate the spreadsheet. If errors occur, re-edit the spreadsheet and then validate it again, until the spreadsheet is free of errors. Run the spreadsheet. This topic provides formats, operation tags, and parameters for the individual operations. File naming, opening and closing, editing, validation, and running of the spreadsheets are covered in Working with CLI spreadsheets on page 4-1. Required prerequisites The following prerequisites are required before you can create, import, and run a CLI spreadsheet: Before using the spreadsheets for Universal Replicator for Mainframe operations, use Storage Navigator to perform the following tasks. Create master the journal Register the secondary storage system Create the remote journal Install the CLI and accompanying third-party files. See Configuring CLI on page 2-1 for details. An error occurs if you specify data volumes other than the Universal Replicator for Mainframe data volumes or if you specify data volumes for the SuspendPair and ResumePair operations. The pair operations defined by other tags in the same sheet may not be executed. When an error occurs, use the Pair tag or the GUI Pair Operation window to check the volume status. If pair operations are not executed because of an error, recreate the spreadsheet and execute the operation again. 9 2 Universal Replicator for Mainframe operations

75 If an error occurs when verifying or performing tasks with a spreadsheet, perform the necessary operations based on the error code. For example, if the pair operations did not work properly, recreate the spreadsheet if needed, and perform the pair operation again. Example of basic spreadsheet format The following example shows the basic spreadsheet format. #!Version Version number, program product, type,; Operation tag Parameter Italics indicate variables that must be input by the user. Table 9-1 Format variables Variables Description First line declaration line #! Indicate the declaration line. Cannot be changed. Version number "06_01_00" (RMI version). Followed by a comma and space. Program product "CLI_RemoteCopyJournalMF". Followed by a comma and space. Type Type of command. See the table in Command types and operation tags on page 9-3 for available types. Followed by a comma and semicolon, no space between (,;). Second line Operation tag Operation to be performed. See the table in Command types and operation tags on page 9-3. Enclosed in brackets. Third line Parameter Pair data necessary for running the operation. Command types and operation tags The available operation tag depends on the command type. The following table shows the command types and related operation tags available for Universal Replicator for Mainframe. Table 9-2 Universal Replicator for Mainframe Command Types and Associated Operation Tags Command Type Operation Tag Output File Get Pair RemoteCopyJournalMF_Get_def_.spd Pair Operation Add RemoteCopyJournalMF_AddPair_def_.spd Suspend Pair RemoteCopyJournalMF_SuspendPair_def_.spd Resume Pair RemoteCopyJournalMF_ResumePair_def_.spd Delete Pair RemoteCopyJournalMF_DeletePair_def_.spd Universal Replicator for Mainframe operations 9 3

76 Only one PairOperation command is allowed per spreadsheet file. In addition to the operation tags shown in the table, the SerialNumber tag can also be used. It allows you to verify that the serial number in the spreadsheet matches the serial number of the storage system. SerialNumber is included in all spreadsheet templates. Editing templates You edit the spreadsheet template by entering specific settings for the appropriate parameters. To edit the Universal Replicator for Mainframe spreadsheet templates 1. Templates are provided with Storage Navigator for the five Universal Replicator for Mainframe operations that can be performed using spreadsheets. Locate the desired template in the /CFLCLITOOLS folder on the microcode CD. 2. Follow the procedure in Setting up CLI directories and files on page Follow the procedures in Editing the CLI-based spreadsheet on page Use the values in the following sections to make specific edits. Retrieving pair information Use the RemoteCopyJournalMF_Get_def_.spd template to retrieve pair information after the pairs exist. By specifying the LDKC and CU in the Pair tag, you can retrieve information about the pairs in a specified range. The command is: [PAIR] Output is saved to a file. The following table shows the information returned for the Pair tag. Table 9-3 Pair tag information retrieved Column Parameter Content A Status Pair status B LDKC LDKC number of the primary data volume C CU CU number of the primary data volume D LDEV LDEV number of the primary data volume E LDKC LDKC number of the secondary data volume F CU(s) CU number of the secondary data volume G LDEV(s) LDEV number of the secondary data volume H Mirror ID Mirror ID I M-JNL The number of the master journal J R-JNL The number of the remote journal K DKCSN Serial number of the secondary storage system L ControllerID Controller ID of the secondary storage system 9 4 Universal Replicator for Mainframe operations

77 One line provides the information for one pair. Virtual Storage Platform allows only 65,280 Universal Replicator for Mainframe pairs. The information returned by Get/Pair is output to a file named RemoteCopyJournalMF_Pair_00.spd. It is a good idea to save pair information. Some retrieved parameter data can be copied and used when writing SuspendPair, ResumePair, and DeletePair scripts. It can also be used to recreate a pair. Example of retrieved pair tag information Creating pairs Column Parameter Content M PathGroup Path group ID N CopyMode Copy mode specified when you create the pair * O Priority Priority specified when you create or resynchronize the pair P ErrorLevel Error level specified when you created or resynchronized the pair, or changed the option of that pair Q CFW CFW specified when you created or resynchronized the pair, or changed the option of the pair. CFW is the setting that specifies whether the Cache-fastwrite data is copied to the secondary data volume or not. *Even if you specify None for the Copy Mode parameter when creating a pair using the AddPair tag, the Pair tag outputs Entire for this item. In addition, if the delta resync operation is performed after the pair creation, the output copy mode may be different from the copy mode specified when the pair was created. Pair tag information is shown in the following example. The output displays in the order shown in the preceding table. #!Version 06_01_00,CLI_RemoteCopyJournalMF,Get,; [Pair] #Status,LDKC,CU,LDEV,LDKC(S),CU(S),LDEV(S),MirrorID,M-JNL, RJNL,DKCSN,ControllerID,PathGroup,CopyMode,Priority, ErrorLevel,CFW Duplex,00,00,00,00,01,00,00,00,00,22222,5,00,Entire,32,Mirror,Only _P-VOL,; Duplex,00,00,01,00,01,01,00,00,00,22222,5,00,Entire,32,Mirror,Only _P-VOL,; Use the RemoteCopyJournalMF_AddPair_def_.spd template to create Universal Replicator for Mainframe pairs. Perform the add pair operation on the primary storage system. Note that volumes specified as P-VOLs and S-VOLs should not be used by other Universal Replicator for Mainframe pairs. Universal Replicator for Mainframe operations 9 5

78 Column Parameter Content Range/ Character Numbers A LDKC LDKC number of the primary data volume 00 B CU CU number of the primary data volume 00 to FE C LDEV LDEV number of the primary data volume 00 to FF D LDKC LDKC number of the secondary data volume 00 to FF E CU(S) CU number of the secondary data volume 00 to FE F LDEV(S) LDEV number of the secondary data volume 00 to FF G Mirror ID Mirror ID 00 to 03 H M-JNL Master journal ID 00 to 1FF I R-JNL Restore journal ID 00 to 1FF J DKCSN Serial number of the secondary storage system to K ControllerID Controller ID of the secondary storage system 4 to 8 L PathGroup Path group ID 00 M CopyMode Entire: Initial copy operation is executed. None: Initial copy operation is not executed. Delta: Without executing the initial copy operation, a pair for delta resync operation is created. N/A N Priority Priority of the operation 1 to O ErrorLevel 2 Mirror: When a failure occurs, all the pairs in the same mirror are split. Volume: When a failure occurs, only the specified pair is split. P CFW Only_P-VOL: Cache-fast-write data is not copied to the secondary data volume. Copy_to_S-VOL: Cache-fast-write data is copied to the secondary data volume. Notes: 1. Though the smaller the number the higher the priority, when you are creating many pairs at a time, specifying the Priority parameter may not be enough to manage the priority of pair creation. Therefore, to insure the pairs are created by priority, it is recommended that you separate the spreadsheets for high priority pairs and other pairs. 2. The USP V/VM option for this field, Group, is also available. The setting is the same whether you specify Mirror or Group. Mirror is recommended. Note: You can create a Universal Replicator for Mainframe pair for delta resync using a spreadsheet. However, using Business Continuity Manager would be a more efficient method in this case. N/A N/A 9 6 Universal Replicator for Mainframe operations

79 Suspending pairs Use the RemoteCopyJournalMF_SuspendPair_def_.spd template to split Universal Replicator for Mainframe pairs. You can use the output from the Get/Pair operation in this spreadsheet. Perform the suspend pair operation on either the primary or secondary system. Pair status must be Pending or Duplex. Use only Universal Replicator for Mainframe volumes. If an error occurs, use the Pair tag or the Storage Navigator Pair Operation window to check status. If the operation did not execute because of the error, recreate the spreadsheet and execute the operation again. Column Parameter Content Range/ Character numbers A LDKC LDKC number of the primary data volume 00 B CU CU number of the primary data volume 00 to FE C LDEV LDEV number of the primary data volume 00 to FF D Mirror ID Mirror ID 00 to 03 E VolType 1 P-VOL S-VOL N/A F LDKC(Pair) DKC number of the remote storage system 00 to FF G DKCSN Serial number of the secondary storage system to H Range 2 Mirror: All pairs in the same mirror are split. Volume: Only specified pair in the mirror is split N/A I S-VOLWrite 3 Disable: The host is not allowed to write data in the secondary data volume during the pair is being split. Enable: The host is allowed to write data in the secondary data volume during the pair is being split. J SuspendMode 4 Flush: the secondary data volume is updated during the pair splitting operation. Purge: the secondary data volume is not updated during the pair splitting operation. Notes: 1. When the specified volume type (primary or secondary) in VolType is different from the actual volume type, the spreadsheet ends normally but the pair is not split. 2. When the pair status is Pending, Duplex, or Suspend, and Mirror is specified for Range, all pairs in the same mirror are split. If the pair in the same mirror is in Suspend status, an error occurs. In addition, an error also occurs if you specify multiple Universal Replicator pairs in the same spreadsheet. The USP V/VM Group option is available for this field. The setting is the same whether you specify Mirror or Group; however, Mirror is recommended. 3. This setting is available only when the data volume in the local storage system is the copy source (that is, primary site). If the data volume in the local storage system is the copy target (that is, secondary site), specify Disable. 4. f you specify Purge, specify Mirror for Range. N/A N/A Universal Replicator for Mainframe operations 9 7

80 Example of suspending pairs #!Version 06_01_00,CLI_RemoteCopyJournalMF,PairOperation,; [SuspendPair] #LDKC,CU,LDEV,MirrorID,VolType,LDKC(Pair),DKCSN,Range,S- VOLWrite,SuspendMode 00,00,00,00,P-VOL,00,22222,Mirror,Disable,Flush,; To split the pairs in a mirror (by specifying Mirror for the Range parameter), specify any URz pair in the mirror. All pairs will be split. Resynchronizing pairs Use the RemoteCopyJournalMF_ResumePair_def_.spd template to resynchronize pairs. You can use the output from the Get/Pair operation in this spreadsheet. Perform the resume pair operation on the primary system. Column Parameter Content Range/ Character Numbers A LDKC LDKC number of the primary data volume 00 B CU CU number of the primary data volume 00 to FE C LDEV LDEV number of the primary data volume 00 to FF D Mirror ID Mirror ID 00 to 03 E M-JNL Master journal ID 00 to 1FF F LDKC(Pair) DKC number of the remote storage system 00 to FF G DKCSN Serial number of the secondary storage system to H ResyncMode 1 Normal: The pair in Suspend status is N/A resynchronized. I Range 2 Mirror: All pairs in the same mirror are N/A resynchronized. Volume: Only specified pair in the mirror is resynchronized. J Priority Priority of the operation 1 to K ErrorLevel 4 Mirror: When a failure occurs, all the pairs in the same mirror are split. Volume: When a failure occurs, only the specified pair is split. L CFW Specify the current setting (Only_P-VOL or Copy_to_S-VOL) N/A N/A 9 8 Universal Replicator for Mainframe operations

81 Column Parameter Content Range/ Character Numbers Notes: 1. Use Business Continuity Manager to resynchronize the pair for delta resync operation. 2. If Mirror is specified for Range, the setting of Priority, ErrorLevel, and CFW are ignored. When the pair status is Pending, Duplex, or Suspend, and Mirror is specified for Range, all pairs in the same mirror are resynchronized. If there is no Suspend pair in the mirror, an error occurs. An error also occurs if you specify multiple Universal Replicator pairs in the same spreadsheet. The USP V/VM Group option is also available for this field. The setting is the same whether you specify Mirror or Group; however, Mirror is recommended. 3. Though the smaller the number the higher the priority, when creating many pairs at a time, specifying the Priority parameter may not be enough to manage the priority of pair creation. Therefore, to insure the pairs are created by priority, it is recommended that you separate the spreadsheets for high priority pairs and other pairs. 4. The USP V/VM Group option is also available for this field. The setting is the same whether you specify Mirror or Group; however, Mirror is recommended. Example #!Version 06_01_00,CLI_RemoteCopyJournalMF,PairOperation,; [ResumePair] #LDKC,CU,LDEV,MirrorID,M-JNL,LDKC(Pair),DKCSN,ResyncMode,Range, Priority,ErrorLevel,CFW 00,00,00,00,00,00,22222,5,Normal,Mirror,32,Mirror,Only_P-VOL,; To resynchronize the pairs in a mirror (by specifying Mirror for the Range parameter), specify any URz pair in the mirror. All pairs will be split. Releasing pairs Use the RemoteCopyJournalMF_DeletePair_def_.spd template to resynchronize pairs. You can use the output from the Get/Pair operation in this spreadsheet. Perform the delete pair operation on either the primary or secondary system Column Parameter Content Range/ Character Numbers A LDKC LDKC number of the primary data volume 00 B CU CU number of the primary data volume 00 to FE C LDEV LDEV number of the primary data volume 00 to FF D Mirror ID Mirror ID 00 to 03 E VolType 1 P-VOL S-VOL N/A F LDKC(Pair) DKC number of the remote storage system 00 to FF G DKCSN Serial number of the secondary storage system to Universal Replicator for Mainframe operations 9 9

82 Column Parameter Content Range/ Character Numbers H Range 2 Mirror: All pairs in the same mirror are released. Volume: Only specified pair in the mirror is released I J DeleteMode 3 SuspendMo de 4 Executing spreadsheets Disable: The host is not allowed to write data in the secondary data volume during the pair is being split. Enable: The host is allowed to write data in the secondary data volume during the pair is being split. Normal: The pair is released only when the pair status can be changed to Simplex in the primary storage system. Force: Under any condition, the pair is forcibly released in the site on which the operation is performed. Notes:: 1. When the specified volume type (primary or secondary) in VolType is different from the actual volume type, the spreadsheet ends normally but the pair is not released. 2. An error occurs if you specify Mirror and multiple Universal Replicator pairs in the same spreadsheet. The USP V/VM Group option is also available for this field. The setting is the same whether you specify Mirror or Group. Mirror is recommended. 3. Specify Mirror for Range when you specify Force. Even if the spreadsheet ends normally when you specify Volume for Range and Force for DeleteMode, the pair is not released. In addition, no error occurs if you specify Force for the volumes other than Universal Replicator pairs, however, in this case, that the pair is not released. Use the CLI to run the spreadsheet. Refer to the command reference topic for CLI in the Hitachi Storage Navigator User Guide for instructions. N/A N/A N/A 9 10 Universal Replicator for Mainframe operations

83 10 Troubleshooting This topic describes how to troubleshoot CLI errors. Command Line Interface errors Troubleshooting 10 1

84 Command Line Interface errors This topic describes solutions for errors that might occur in CLI operations. Table 10-1 CLI errors, causes, and solutions Error Codes and Operations Causes and Solutions Error ( ) The directory specified as the output file might not exist. Make sure that the specified directory exists. Writing to the directory or file that is specified as the output file might not be allowed. Make sure that writing operations to the specified directory or file is allowed. If the execution environment for the Storage Navigator CLI is JRE1.5, a JRE that supports additional languages might not have been installed. Follow the procedure described in Installing the JRE on page 2-3 to install the JRE that supports additional languages. In the execution environment for the Storage Navigator CLI is JRE1.7.0_21, 1.6.0_45, 1.5.0_45 or later, dynamic load for class might have been failed. Edit the command batch file of execution Storage Navigator CLI and follow the procedure described in Preparing CLI command files on page 2-6 to add the following: -Djava.rmi.server.useCodebaseOnly=false for the java launch parameter. A correct version of Apache might not have been installed on the SVP of the server. Call the Hitachi Data Systems technical support center shown in the Hitachi Storage Navigator User Guide. When a suspended Storage Navigator CLI process is resumed, error ( ) occurs. Error (java.lang.noclassdeffounderro r) The RMI timeout occurred because the Storage Navigator CLI processing was stopped. Run the Storage Navigator CLI command again. A correct version of Java might not be installed on the execution environment for the Storage Navigator CLI. Make sure that the Java whose version meets the operating condition in the Hitachi Storage Navigator User Guide is installed. The execution path to the correct version of Java might not be defined on the execution environment for the Storage Navigator CLI. Confirm the execution path to the Java. If you cannot solve the problems by the above solutions, call the Hitachi Data Systems technical support center shown in the Hitachi Storage Navigator User Guide Troubleshooting

85 A Configuration File Loader GUI reference This appendix describes the Configuration File Loader window in Storage Navigator. Configuration File Loader window Configuration File Loader GUI reference A 1

86 Configuration File Loader window This window enables you to export system information, import a LUN Manager spreadsheet, validate, and run the spreadsheet. Use this window to: Exporting system settings to a spreadsheet on page 5-2 Importing and validating a CFL-based spreadsheet on page 5-6 Running a CFL-based spreadsheet on page 5-7 Item Select Sheet Import Description Select the program product option for which you want to import or export a spreadsheet file. Imports the edited spreadsheet file. If using a Web browser for UNIX systems, the Download Manager dialog box may open when you click Import. If this occurs, close the Download Manager dialog box and continue the operation. A 2 Configuration File Loader GUI reference

87 Item Description Export Exports the current spreadsheet file. If using a Web browser for UNIX systems, the Download Manager dialog box may open when you click Export. If this occurs, close the Download Manager dialog box and continue the operation. Select tag This list is available after you have imported a spreadsheet, and allows you to select the function tag that you want to display. An asterisk (*) appears after one or more of the function tags that has an error. No. The row number that includes the error. Error Code The part code and error number such as 8105 (part code) 1212 (error number). Column The column number that includes the error. A dash "-" indicates the error column cannot be specified. Information The error message. Please see the Hitachi Storage Navigator Messages for the error codes and error messages displayed on the list. Status Indicates whether the imported spreadsheet has errors. If there are no errors, the Apply button becomes available. Status conditions are: Error Ready Apply Implements the settings in the imported spreadsheet. This button is available only when a spreadsheet is imported without errors. Cancel Cancels the settings and returns to the original status of the Configuration File Loader window. Configuration File Loader GUI reference A 3

88 A 4 Configuration File Loader GUI reference

89 Glossary This glossary defines the special terms used in this document. Click the letter links below to navigate. A AL arbitrated loop AL-PA arbitrated loop physical address alternate path APLB C A secondary path (port, target ID, LUN) to a logical volume, in addition to the primary path, that is used as a backup in case the primary path fails. cache active path load balancing A set of RAM (Random Access Memory modules used to store data temporarily. capacity The amount of data storage space available on a disk drive, storage system. Generally measured in MB, but can also use other measurements such as TB and PB, depending on the total storage space. # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 1

90 CFL CFW CH CLI CLPR Configuration File Loader. A Storage Navigator function for validating and running scripted spreadsheets. cache fast write channel command line interface cache logical partition. Consists of virtual cache memory which is set up to be allocated to different hosts in contention for cache memory. command device A dedicated logical volume used only by array management software to interface with the storage systems. Can be shared between several hosts. configuration definition file Defines the configuration, parameters, and options of Command Control Interface (CCI) operations. A text file that defines the connected hosts and the volumes and groups known to the Command Control Interface (CCI) instance. copy pair D A pair of volumes in which one volume contains original data and the other volume contains the copy of the original. Copy operations can be synchronous or asynchronous, and the volumes of the copy pair can be located in the same storage system (local copy) or in different storage systems (remote copy).a copy pair can also be called a volume pair, or just pair. delta resync A disaster recovery solution in which TrueCopy and Universal Replicator systems are configured to provide a quick recovery using only differential data stored at an intermediate site. DEV, dev device # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 2

91 device DKC E A physical or logical unit with a specific function. disk controller, though the acronym is used in various other ways. When it refers to the RAID product, it is synonymous with the storage system; when it refers to controller components, it is synonymous with the controller. emulation group A set of device emulation types that can be intermixed within a RAID group and treated as a group. ESCON EXG Enterprise System Connection external volume group external volume H HDS A logical volume whose data resides on drives that are physically located outside the storage system. Hitachi Data Systems host group Used to segregate hosts by operating system platform. For AMS, "host groups" are used with iscsi systems and "RAID groups" are used with Fibre Channel systems. host mode Operational modes that provide enhanced compatibility with supported host platforms. Used with fibre-channel ports on RAID storage systems. host mode option Additional options for fibre-channel ports on RAID storage systems. Provide enhanced functionality for host software and middleware. # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 3

92 I initial copy An initial copy operation is performed when a copy pair is created. Data on the primary volume is copied to the secondary volume before any updates are processed. IZPIOCP J JNL L LDEV LDKC Enhanced IOCP program for zseries servers journal logical device logical disk controller logical volume LUSE M See volume. LUN Expansion; LU Size Expansion master journal MIH M-JNL. Holds differential data on the primary Universal Replicator system until it is copied to the restore journal on the secondary system. missing interrupt handler mirror In Universal Replicator, each pair relationship in and between journal groups is called a "Mirror". Each pair is assigned a mirror ID when it is created. The mirror ID identifies individual pair relationships between journal groups. # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 4

93 M-JNL main journal modify mode MVS The mode of operation of Storage Navigator that allows changes to the storage system configuration. See also view mode. Multiple Virtual Storage MVS/ESA Multiple Virtual Storage/Enterprise Systems Architecture MVS/XA O Multiple Virtual Storage/Extended Architecture OPEN-V A logical unit (LU) of variable size for use by open-systems hosts. OPEN-x A logical unit (LU) of fixed size (OPEN 3 or OPEN 9) that is used primarily for sharing data between mainframe and open-systems hosts using Hitachi Cross-OS File Exchange. OS/390 P pair Operating System/390 Two logical volumes in a replication relationship, in which one volume contains original data to be copied and the other volume contains the copy of the original data. The pair volumes can be located in the same storage system (local copy) or in different storage systems (remote copy). pair status Indicates a pair's condition. A pair must have a specific status for specific operations. When an specific operation completes, the pair must have a specific status. # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 5

94 physical device See device. primary site The physical location of a storage system that contains original data and that is connected to one or more storage systems at a secondary site via remote copy connections. A primary site can also be called a "main site" or "local site". The term is also used for host failover operations. In that case, the primary site is the host computer where the production applications are running, and the secondary site is where the backup applications run when the applications on the primary site fail, or where the primary site itself fails. primary volume P-VOL. The volume in a pair that contains the original data used as the source of the copy operations. The data on the P VOL is duplicated synchronously or asynchronously on the secondary volume (S-VOL). The following Hitachi products use the term P-VOL: Copy-on-Write Snapshot, ShadowImage, TrueCopy, and Universal Replicator. P-VOL R RAID primary volume redundant array of inexpensive disks restore journal R-JNL. Holds differential data on the secondary Universal Replicator system until it is copied to the S-VOL. R-JNL S restore journal scripting The use of command line scripts, or spreadsheets downloaded by Configuration File Loader, to automate functionality. secondary volume S-VOL. The volume in a pair that is the copy of the original data on the primary volume (P-VOL). # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 6

95 The following Hitachi products use the term, secondary volume, or S- VOL: ShadowImage, TrueCopy, and Universal Replicator. service processor SVP. The computer inside a RAID storage system that hosts the Storage Navigator software and is used by service personnel for configuration and maintenance of the storage system. source volume S-VOL. The mainframe volume in a copy pair that contains the original data that is duplicated on the target volume (T-VOL). The following Hitachi products use the term, source volume (S-VOL): Dataset Replication for IBM z/os, IBM FlashCopy. space SSID Generally refers to the data storage capacity of a hard disk. IBM mainframe term: storage subsystem ID (SSID). SSIDs are used for reporting information from the CU to the operating system. Each group of 64 or 256 volumes requires one SSID, so there are one or four SSIDs per CU image. The user-specified SSIDs are assigned during storage system installation and must be unique to all connected host operating environments. S-VOL T secondary volume; source volume T-VOL U UVM V target volume Hitachi Universal Volume Manager Virtual LVI/LUN volume Usually consists of at least one fixed volume (FV), one or more customsized volumes (CVs), and some free space. # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 7

96 virtual volume VM V-VOL. The secondary volume in a Copy-on-Write Snapshot pair. When in PAIR status, the V-VOL is an up-to-date virtual copy of the P-VOL. When in SPLIT status, the V-VOL points to data in the P-VOL and to replaced data in the pool, maintaining the point-in-time copy of the P- VOL at the time of the split operation. Also used with Dynamic Provisioning, though referred to as DP-VOL. volume migration; volume manager VM/ESA Virtual Machine/Enterprise Systems Architecture VOL, vol volume volume A logical device (LDEV), or a set of LDEVs in the case of LUSE, that has been defined to one or more hosts as a single data storage unit. A mainframe volume is called a logical volume image (LVI), and an opensystems volume is called a logical unit. (LU). volume pair VPG See copy pair. virtual parity group V-VOL virtual volume # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary 8

97 Index A authentication file, creating 2 5 B batch files 2 6 C CFLGET, running 4 6 CFLSET, running 4 5 CLI about 1 3 command files, preparing 2 6 requirements 2 2 workflow 4 2 columns in a spreadsheet 5 3 command device, changing 6 8 Configuration File Loader about 1 3 importing a spreadsheet 5 6 preparing a spreadsheet for 5 3 running a spreadsheet 5 7 window in GUI A 2 current settings, new settings 5 3 E editing CFL-based 5 4 editing, preparing spreadsheet for 5 3 Error Information 5 7 errors, correcting 4 4 exporting 5 2 external volume group info, retrieving 8 5 external volume with one LDEV, mapping 8 10 external volume, deleting 8 12 external volume, disconnecting 8 11 external volume, moving 8 13 external volume, restoring 8 12 external volumes with multiple LDEVs, mapping 8 6 external volumes, moving 8 13 F file name requirements for spreadsheets 3 2 function tags;parameters, CLI 5 3 H host groups, configuring 6 5 host mode option 6 6 J Java security policy, changing 2 4 JRE, installing 2 3 L LDEVs, retrieving information for 7 4 LU paths, configuring 6 8 LUN Expansion creating LUSE volumes 7 5 releasing LUSE volumes 7 5 retrieving LDEV info 7 4 workflow for spreadsheet operations 7 2 LUN Manager changing port settings 6 5 changing the command device 6 8 configuring host groups 6 5 configuring LU paths 6 8 configuring WWNs 6 7 workflow for spreadsheet operations 6 2 LUSE volumes, creating 7 5 LUSE volumes, releasing 7 5 O obtaining a CFL spreadsheet 5 2 obtaining a CLI spreadsheet 4 2 overview 1 2 P pair information, retrieving 9 4 pairs creating 9 5 releasing 9 9 Index 1

98 resynchronizing 9 8 suspending 9 7 port settings, changing 6 5 program products using spreadsheets 1 2 R requirements, CLI 2 2 Retrieving pair information 9 4 running CFL-based spreadsheet 5 7 running CLI-based spreadsheet 4 5 S saving a spreadsheet file 3 3 Select Tab box 5 6 spreadsheets editing CFL-based 5 4 editing CLI-based 4 2 errors, correcting 4 4 format requirements 3 2 importing 5 6 obtaining CFL-based 5 2 obtaining CLI-based 4 2 operations that can be performed 1 2 preparing CFL-based 5 3 running CFL-based 5 7 running CLI-based 4 5 saving the file 3 3 validating CFL-based 5 6 validating CLI-based 4 3 workflow for CFL-based 5 2 SSID information, retrieving 8 4 workflow for spreadsheet operations 8 2 user authentication 2 5 V validating CFL-based spreadsheet 5 6 validating CLI-based spreadsheet 4 3 W workflow for CFL spreadsheets 5 2 workflow for CLI spreadsheets 4 2 WWNs, configuring 6 7 T template location 7 3, 8 4 termination codes in batch files 2 7 U Universal Replicator for Mainframe creating pairs 9 5 format 9 3 releasing pairs 9 9 resynchronizing pairs 9 8 retrieving pair information 9 4 suspending pairs 9 7 workflow for spreadsheet operations 9 2 Universal Volume Manager deleting an external volume 8 12 disconnecting an external volume 8 11 mapping an external volume with one LDEV 8 10 mapping external volumes with multiple LDEVs 8 6 moving an external volume 8 13 moving external volumes 8 13 restoring an external volume 8 12 retrieving external volume group info 8 5 retrieving external volume info 8 5 retrieving SSID info 8 4 Index 2

99

100 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California U.S.A. Regional Contact Information Americas Europe, Middle East, and Africa +44 (0) Asia Pacific MK-92HM