System Operations Using Spreadsheets · Hitachi Virtual Storage Platform System Operations Using Spreadsheets viii Preface Intended audience This document is intended for system administrators,

Product Version

Document Organization

Getting Help

FASTFIND LINKS

Contents

Hitachi Virtual Storage PlatformSystem Operations Using Spreadsheets

MK-90RD7026-06

Hitachi Virtual Storage Platform System Operations Using Spreadsheets

ii

© 2010-2012 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, ESCON, FICON, FlashCopy, IBM, MVS/ESA, MVS/XA, OS/390, S/390, VM/ESA, VSE/ESA, z/OS, zSeries, z/VM, and zVSE 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.

iiiHitachi Virtual Storage Platform System Operations Using Spreadsheets

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiChanges in this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiReferenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixDocument organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiAccessing product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

1 Spreadsheet operation overview . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Processing spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Software applications used to process spreadsheets . . . . . . . . . . . . . . . . . . . . 1-2CLI spreadsheet templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Spreadsheet format requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Command Line Interface installation and commands . . . . . . . . . . . 2-1CLI-based products that can process spreadsheets . . . . . . . . . . . . . . . . . . . . . 2-2CLI permission levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2CLI configuration workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Copying CLI tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Changing the Java security policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Creating user authentication files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Example: user authentication file for an IPv4 address . . . . . . . . . . . . . . 2-4Example: user authentication file for an IPv6 address . . . . . . . . . . . . . . 2-4

CLI command file locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4CLI termination codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5


iv

3 LUN Expansion operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1LUN Expansion spreadsheet tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Prerequisites for using spreadsheets in LUN Expansion . . . . . . . . . . . . . . . . . . 3-2Workflow for CLI-based spreadsheets in LUN Expansion . . . . . . . . . . . . . . . . . 3-2CLI-based spreadsheet format in LUN Expansion . . . . . . . . . . . . . . . . . . . . . . 3-2LUN Expansion command summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Editing CLI-based spreadsheet templates in LUN Expansion . . . . . . . . . . . . . . 3-4Validating CLI-based spreadsheets in LUN Expansion . . . . . . . . . . . . . . . . . . . 3-4Correcting validation errors in LUN Expansion . . . . . . . . . . . . . . . . . . . . . . . . 3-5Running CLI-based spreadsheets in LUN Expansion . . . . . . . . . . . . . . . . . . . . 3-7

Making configuration changes in LUN Expansion. . . . . . . . . . . . . . . . . . . . 3-7Retrieving storage system information in LUN Expansion. . . . . . . . . . . . . . 3-7Retrieving information about logical volumes in LUN Expansion . . . . . . . . . 3-8Creating LUN Expansion volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Releasing LUN Expansion volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Troubleshooting runtime CLI errors in LUN Expansion . . . . . . . . . . . . . . . . . . 3-10

4 LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1LUN Manager spreadsheet tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Workflow for CFL-based spreadsheets in LUN Manager . . . . . . . . . . . . . . . . . . 4-2

Exporting system settings to spreadsheets in LUN Manager. . . . . . . . . . . . 4-2Setting up spreadsheets for editing in LUN Manager . . . . . . . . . . . . . . . . . 4-3

CFL-based spreadsheet format in LUN Manager . . . . . . . . . . . . . . . . . . 4-4Function tags in spreadsheets in LUN Manager. . . . . . . . . . . . . . . . . . . 4-5Definitions used in spreadsheet formats in LUN Manager. . . . . . . . . . . . 4-6

Editing CFL-based spreadsheets in LUN Manager . . . . . . . . . . . . . . . . . . . 4-6Changing the port settings in LUN Manager . . . . . . . . . . . . . . . . . . . . . 4-7Configuring host groups in LUN Manager . . . . . . . . . . . . . . . . . . . . . . . 4-8Configuring WWN information in LUN Manager. . . . . . . . . . . . . . . . . . 4-10Configuring LU paths in LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . 4-11Changing command device settings in LUN Manager. . . . . . . . . . . . . . 4-12

Importing and validating spreadsheets in LUN Manager . . . . . . . . . . . . . 4-13Errors when importing spreadsheets in LUN Manager . . . . . . . . . . . . . 4-14Viewing import error messages in LUN Manager . . . . . . . . . . . . . . . . . 4-14

Applying changes to CFL-based spreadsheets in LUN Manager . . . . . . . . . 4-15Errors when applying CFL-based spreadsheets in LUN Manager . . . . . . 4-15

5 Universal Volume Manager operations . . . . . . . . . . . . . . . . . . . . . 5-1Universal Volume Manager spreadsheet tasks . . . . . . . . . . . . . . . . . . . . . . . . 5-2Prerequisites for using spreadsheets in Universal Volume Manager. . . . . . . . . . 5-2Workflow for CLI-based spreadsheets in Universal Volume Manager . . . . . . . . . 5-2CLI-based spreadsheet format in Universal Volume Manager . . . . . . . . . . . . . . 5-3Universal Volume Manager command summary . . . . . . . . . . . . . . . . . . . . . . . 5-3Editing CLI-based spreadsheets in Universal Volume Manager . . . . . . . . . . . . . 5-4Validating CLI-based spreadsheets in Universal Volume Manager . . . . . . . . . . . 5-4

vHitachi Virtual Storage Platform System Operations Using Spreadsheets

Correcting validation errors in Universal Volume Manager . . . . . . . . . . . . . . . . 5-5Running CLI-based spreadsheets in Universal Volume Manager . . . . . . . . . . . . 5-7

Changing the configuration settings in Universal Volume Manager . . . . . . . 5-7Retrieving storage system information in Universal Volume Manager. . . . . . 5-7Retrieving SSID information in Universal Volume Manager . . . . . . . . . . . . . 5-8Retrieving external-volume group information in Universal Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Retrieving external volume information in Universal Volume Manager . . . . . 5-9Mapping external volumes with multiple LDEVs in UVM . . . . . . . . . . . . . . 5-10Specifying LDEV capacity in Universal Volume Manager . . . . . . . . . . . . . . 5-13Mapping external volumes with one LDEV in Universal Volume Manager . . 5-14Disconnecting external volumes in Universal Volume Manager . . . . . . . . . 5-16Restoring external volumes in Universal Volume Manager . . . . . . . . . . . . 5-16Deleting external volume mapping in Universal Volume Manager . . . . . . . 5-17Moving external volumes to another path group in UVM . . . . . . . . . . . . . 5-17Moving external volumes to a new path group in UVM . . . . . . . . . . . . . . 5-18

Troubleshooting runtime CLI errors in Universal Volume Manager. . . . . . . . . . 5-19

6 Universal Replicator for Mainframe operations. . . . . . . . . . . . . . . . 6-1Universal Replicator for Mainframe spreadsheet tasks . . . . . . . . . . . . . . . . . . . 6-2Prerequisites for using spreadsheets in Universal Replicator for Mainframe . . . . 6-2Workflow for CLI-based spreadsheets in Universal Replicator for Mainframe . . . 6-2CLI-based spreadsheet format in Universal Replicator for Mainframe . . . . . . . . 6-3Creating CLI-based spreadsheets in Universal Replicator for Mainframe . . . . . . 6-4Editing CLI-based spreadsheets in Universal Replicator for Mainframe . . . . . . . 6-5Validating CLI-based spreadsheets in Universal Replicator for Mainframe . . . . . 6-5Correcting validation errors in Universal Replicator for Mainframe. . . . . . . . . . . 6-6Running CLI-based spreadsheets in Universal Replicator for Mainframe. . . . . . . 6-8

Making configuration changes in Universal Replicator for Mainframe . . . . . . 6-8Retrieving storage system information in Universal Replicator for Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Retrieving Universal Replicator for Mainframe pair information . . . . . . . . . . 6-9Adding Universal Replicator for Mainframe pairs . . . . . . . . . . . . . . . . . . . 6-11Suspending Universal Replicator for Mainframe pairs. . . . . . . . . . . . . . . . 6-12Resynchronizing Universal Replicator for Mainframe pairs . . . . . . . . . . . . 6-13Releasing Universal Replicator for Mainframe pairs . . . . . . . . . . . . . . . . . 6-14

Troubleshooting runtime CLI errors in Universal Replicator for Mainframe . . . . 6-15

7 Volume Retention Manager operations . . . . . . . . . . . . . . . . . . . . . 7-1Prerequisites for using spreadsheets in Volume Retention Manager . . . . . . . . . 7-2Volume Retention Manager spreadsheet tasks . . . . . . . . . . . . . . . . . . . . . . . . 7-2Example: Using CFL-based spreadsheets in Volume Retention Manager . . . . . . 7-2Workflow for CFL-based spreadsheets in Volume Retention Manager . . . . . . . . 7-3

Exporting access attributes to spreadsheets in Volume Retention Manager . 7-4Editing CFL-based spreadsheets in Volume Retention Manager . . . . . . . . . . 7-4


vi

CFL-based spreadsheet format in Volume Retention Manager. . . . . . . . . 7-6Function tags in spreadsheets in Volume Retention Manager . . . . . . . . . 7-6Definitions used in spreadsheet formats in Volume Retention Manager . . 7-8

Importing and validating spreadsheets in Volume Retention Manager . . . . . 7-8Errors when importing spreadsheets in Volume Retention Manager . . . . 7-8Viewing import error messages in Volume Retention Manager . . . . . . . . 7-9

Applying changes to spreadsheets in Volume Retention Manager . . . . . . . 7-10Errors when applying spreadsheets in Volume Retention Manager . . . . 7-10

A Configuration File Loader GUI reference . . . . . . . . . . . . . . . . . . . . A-1Configuration File Loader window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

LUN Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Volume Retention window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Index

Preface viiHitachi Virtual Storage Platform System Operations Using Spreadsheets

Preface

This document describes and provides instructions for using spreadsheets to perform operations on the Hitachi Virtual Storage Platform (VSP) storage system.

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

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document organization

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments


viii Preface

Intended audienceThis document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who are involved in installing, configuring, and operating the Hitachi Virtual Storage Platform 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 Hitachi Virtual Storage Platform storage system, and you should have read the Hitachi Virtual Storage Platform User and Reference Guide.

• You should be familiar with the Storage Navigator (SN) software for the Hitachi Virtual Storage Platform storage system, 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 (for example, Microsoft Excel).

Product versionThis document revision applies to Hitachi Virtual Storage Platform microcode 70-05-0x or later.

Document revision level

Changes in this revision• Added Volume Retention Manager (VRM) as a software application with

which you can process spreadsheets. For more information about the list of software applications that you can use to process spreadsheets, see Software applications used to process spreadsheets on page 1-2.

• Added information to the following chapter and sections:

Volume Retention Manager operations on page 7-1.

Volume Retention window on page A-4.

Errors when importing spreadsheets in Volume Retention Manager on page 7-8.

Revision Date Description

MK-90RD7026-00 October 2010 Initial release

MK-90RD7026-01 December 2010 Supersedes and replaces MK-90RD7026-00.

MK-90RD7026-02 April 2011 Supersedes and replaces MK-90RD7026-01.

MK-90RD7026-03 August 2011 Supersedes and replaces MK-90RD7026-02.

MK-90RD7026-04 March 2012 Supersedes and replaces MK-90RD7026-03.

MK-90RD7026-05 August 2012 Supersedes and replaces MK-90RD7026-04.

MK-90RD7026-06 November 2012 Supersedes and replaces MK-90RD7026-05.

Preface ixHitachi Virtual Storage Platform System Operations Using Spreadsheets

Added causes and solutions for the (java.lang.NoClassDefFoundError) error for those software applications that use CLI to process spreadsheets to the following sections:

- Troubleshooting runtime CLI errors in LUN Expansion on page 3-10

- Troubleshooting runtime CLI errors in Universal Volume Manager on page 5-19.

• Changed the range of the PathGroup parameter in the Adding Universal Replicator for Mainframe pairs table. For more information about this parameter, see Adding Universal Replicator for Mainframe pairs on page 6-11.

• Changed the description for the Version number variable in the table that describes the variables used in the spreadsheet format for Hitachi LUN Manager (LUNM). For more information, see CFL-based spreadsheet format in LUN Manager on page 4-4.

Referenced documentsThe Hitachi Virtual Storage Platform storage system:

• Hitachi Virtual Storage Platform User and Reference Guide, MK-90RD7042

• Hitachi Storage Navigator User Guide, MK-90RD7027

• Hitachi Universal Volume Manager User Guide, MK-90RD7033

• Provisioning Guide for Open Systems, MK-90RD7022

• Provisioning Guide for Mainframe Systems, MK-90RD7021

• Hitachi Universal Replicator for Mainframe User Guide, MK-90RD7031

Document organizationThe following table provides an overview of the contents and organization of this document. Click the chapter title in the Chapter column to go to that chapter. This first page of each chapter provides links to the sections in that chapter.

Chapter Description

Chapter 1, Spreadsheet operation overview

Provides a summary of the software applications that support the use of spreadsheets.

Chapter 2, Command Line Interface installation and commands

Provides instructions for setting up the Command Line Interface (CLI), a list of the command file locations, and CLI termination codes.

Chapter 3, LUN Expansion operations

Provides information and instructions for using Hitachi LUN Expansion (LUSE) spreadsheets.

Chapter 4, LUN Manager operations

Provides information and instructions for using LUNM spreadsheets.


x Preface

Document conventionsThis document uses the following typographic conventions:

This document uses the following icons to draw attention to information:

Chapter 5, Universal Volume Manager operations

Provides information and instructions for using Hitachi Universal Volume Manager (UVM) spreadsheets.

Chapter 6, Universal Replicator for Mainframe operations

Provides information and instructions for using Hitachi Universal Replicator software for Mainframe (URz) spreadsheets.

Chapter 7, Volume Retention Manager operations

Provides information and instructions for using VRM spreadsheets.

Appendix A, Configuration File Loader GUI reference

Contains information about the Configuration File Loader window in the SN GUI.

Chapter Description

Convention Description

Bold Indicates text on a window or dialog box, including window and dialog box names, menus, menu options, buttons, fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file

Notes: Angled brackets (< >) are also used to indicate variables.

screen/code Indicates text that is displayed on the screen or entered by the user. Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group>

Notes: Italic font 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.

Underline Indicates the default value. Example: [ a | b ]

Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Preface xiHitachi Virtual Storage Platform System Operations Using Spreadsheets

Convention for storage capacity valuesPhysical storage capacity values, such as disk drive capacity, are calculated based on the following values:

Logical storage capacity values, such as logical device capacity, are calculated based on the following values:

Accessing product documentationThe Hitachi Virtual Storage Platform storage system user documentation is available on the Hitachi Data Systems Support Portal: https://portal.hds.com. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Note Calls attention to important and/or additional information.

Caution Warns the user of adverse conditions and/or consequences (such as disruptive operations).

WARNING Warns the user of severe conditions and/or consequences (such as destructive operations).

Icon Meaning Description

Physical capacity unit Value

1 KB 1,000 bytes

1 MB 1,0002 bytes

1 GB 1,0003 bytes

1 TB 1,0004 bytes

1 PB 1,0005 bytes

1 EB 1,0006 bytes

Logical capacity unit Value

1 KB 1,024 bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 block 512 bytes

https://hdssupport.hds.com



xii Preface

Getting helpThe 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 Support Portal for contact information: https://portal.hds.com.

CommentsSend us your comments on this document: [email protected]. Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems.

Thank you!



1

Spreadsheet operation overview 1–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Spreadsheet operation overview

Use custom spreadsheets to help you make or schedule changes or perform repeated operations on a large scale to the configuration of large deployment storage systems. Spreadsheets can help reduce the risk of human error.

□ Processing spreadsheets

□ Software applications used to process spreadsheets

□ CLI spreadsheet templates

□ Spreadsheet format requirements


1–2 Spreadsheet operation overview

Processing spreadsheetsSpreadsheets are created when you export system information using Configuration File Loader (CFL). CFL is a Storage Navigator (SN) software application that is installed with SN. Once you have written and edited a spreadsheet, you use CFL or Command Line Interface (CLI) to perform operations such as editing, importing, and applying spreadsheets.

For more information about how to process spreadsheets for each software application, see the following:

• Workflow for CLI-based spreadsheets in LUN Expansion on page 3-2

• Workflow for CFL-based spreadsheets in LUN Manager on page 4-2

• Workflow for CLI-based spreadsheets in Universal Volume Manager on page 5-2

• Workflow for CLI-based spreadsheets in Universal Replicator for Mainframe on page 6-2

• Workflow for CFL-based spreadsheets in Volume Retention Manager on page 7-3

Software applications used to process spreadsheetsYou can validate and run custom spreadsheets that contain configuration information using software applications and software application features on the Virtual Storage Platform (VSP) storage system.

You can use spreadsheets with the following software applications:

• LUN Expansion (LUSE)

• LUN Manager (LUNM)

• Universal Volume Manager (UVM)

• Universal Replicator for Mainframe (URz)

• Volume Retention Manager (VRM)

The methods in which you edit, validate, and run spreadsheets is specific to the software application you use. The following table lists the software application and the software-based tool that is supported and that you can use to process spreadsheets.

For more information about installing CLI and the commands you can use, see Command Line Interface installation and commands on page 2-1.

Software Application Command Line Interface (CLI)

Configuration File Loader (CFL)

LUSE X

LUNM X

UVM X

URz X

VRM X

Spreadsheet operation overview 1–3Hitachi Virtual Storage Platform System Operations Using Spreadsheets

For more information about the Graphical User Interface (GUI) for CFL, see Configuration File Loader GUI reference on page A-1.

CLI spreadsheet templates CLI-based spreadsheet templates are included with the following software applications:

• LUSE.

For more information on using LUSE, see LUN Expansion operations on page 3-1.

• UVM.

For more information on using UVM, see Universal Volume Manager operations on page 5-1.

• URz.

For more information on using URz, see Universal Replicator for Mainframe operations on page 6-1.

The CLI-based spreadsheet templates are included in a tool pack. The following table lists the template names for the CLI-based spreadsheets.

Spreadsheet format requirementsSpreadsheets must meet certain requirements so that the CLI commands or CFL can process them. Software-specific requirements appear in the product-specific information.

The following table lists the spreadsheet format requirements.

Software Application Spreadsheet Template Name

LUSE LUSE_Expansion_def_.spd

LUSE_Get_def.spd

LUSE_Release_def_.spd

URz RemoteCopyJournalMF_AddPair_def_.spd

RemoteCopyJournalMF_DeletePair_def_.spd

RemoteCopyJournalMF_Get_def_.spd

RemoteCopyJournalMF_ResumePair_def_.spd

RemoteCopyJournalMF_SuspendPair_def_.spd

UVM 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


1–4 Spreadsheet operation overview

Item Requirement

File type Text file

File name • You must use the .spd file extension.

• Character limit (including the extension): 32

• Prohibited symbols in file names: \ / : , ; * ? “ < > | and space.

• Character limit:

CLI-based spreadsheets: 240

CFL-based spreadsheets: 255

Rows • Number of rows limit:

CLI-based spreadsheets: 65,536

• CFL-based spreadsheets in LUNM: 400,000

• CFL-based spreadsheets in VRM: 70,000

• Character limit per row (including the line feed):

- CLI-based spreadsheets: 512

• - CFL-based spreadsheets in LUNM: 200

• - CFL-based spreadsheets in VRM: 128

End-of-line character The line feed must appear at the end of each row.

Case-sensitivity No with the following exceptions in LUNM:

• WWN

• group settings

CLI/CLF spreadsheet format

• The first row contains the spreadsheet version, which is defined for each software application.*

• Separate each parameter with a comma (,).

• Tabs and spaces before or after commas are ignored.

CLI-based spreadsheets: You must add a semicolon (;) at the end of each row that contains a parameter.

Comments Begin a comment row with a hash (#) sign. Comments can contain characters from any language.

* Microcode updates can affect the number of items or the range of available values. Before editing the spreadsheet, ensure the spreadsheet is compatible with the microcode your system is running.

2

Command Line Interface installation and commands 2–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Command Line Interface installationand commands

The CLI is an SN feature that provides commands for retrieving, validating, and running spreadsheets. The system administrator can assign permission levels to users.

□ CLI-based products that can process spreadsheets

□ CLI permission levels

□ CLI configuration workflow

□ CLI command file locations

□ CLI termination codes


2–2 Command Line Interface installation and commands

CLI-based products that can process spreadsheetsYou can use CLI commands from a command prompt to run spreadsheets for the following software applications:

• LUNM

• UVM

• URz

CLI permission levelsWhen setting up the CLI, the system administrator must assign users the correct permissions. The following table lists the CLI command set for spreadsheets and permission levels.

CLI configuration workflow1. Copy and set up the CLI files.

For more information, see Copying CLI tools on page 2-3.

2. Install the Java Runtime Environment (JRE) 1.6 or later.

For more information, see the JRE documentation.

3. Change the Java security policy file.

For more information, see Changing the Java security policy on page 2-3.

4. Create a user authentication file.

For more information, see Creating user authentication files on page 2-3.

Note: You must install and configure the CLI before you can use spreadsheets.

For more information on how to install spreadsheet templates and the CLI, see CLI configuration workflow on page 2-2.

CLI command Built-in permission

CFLCHK Storage Administrator (view) role.

CFLGET Storage Administrator (view) role.

CFLSET User must hold all the listed roles:

• Storage Administrator (default setting)

• Storage Administrator (system resource management)

• Storage Administrator (provisioning)

• Storage Administrator (performance management)

• Storage Administrator (local backup management)

• Storage Administrator (remote backup management)

Note: If you install JRE 1.5, you must create a custom installation and choose the option for support of other languages.


Copying CLI toolsThe /CFLCLItool directory contains the CLI files. This directory is located on CD#3 of a microcode distribution kit.

This directory contains the following files, folders, and spreadsheet templates:

• /CFLCLItool folder - contains the following files:

JSanCLI.jar

java.policy file - the default policy file

For more information about this policy file, see the Java documentation.

• sample folder - contains the CLI command files

• template folder - contains the spreadsheet templates

1. Create an installation directory to store the CLI files.

2. Insert CD#3 into the CD-ROM drive.

3. Copy the /CFLCLItool directory from the CD to the directory you created.

Changing the Java security policyYou must change the Java security policy to be able to execute CLI commands. Java runs on the Web browser and communicates with the VSP storage systems to which it is attached.

You can use the current policy file in the CLI as a user policy file. If you use this policy file, the security policy changes only when you execute CLI commands. The policy file is stored in the CLI installation directory.

Alternatively, you can edit the java.policy file.

1. Launch a text editor, and open the java.policy file located in the /CFLCLItool folder.

2. Enter the following into the file:

grant { permission java.security.AllPermission;};

3. Save your changes.

Creating user authentication filesEach CLI user must have a user authentication file that contains the IP address, user name, and password. After you create the user authentication file, set the appropriate access authority for the file using your operating system security feature.

1. Log in to SN using a storage administrator account.

2. From the /CFLCLITool/sample file, copy and then paste the appropriate statement in the /CFLCLITool directory.

(For Windows) Execute the following command:



mkatfile.bat

(For UNIX) Execute the following command:

mkatfile.sh

3. (For UNIX systems) If you have a shell program installed in a directory other than /bin, execute the following command:

mkatfile.sh

4. Change #! /bin/csh in the first row to the directory where the shell program is installed. For example, /usr/bin/csh).

5. From the command prompt, change directories to the destination-folder/CFLCLITool directory.

6. Run the batch file. Execute the following command:

mkatfile SVP-ip-address user-id password > myAuthentication.txt

(For UNIX) Execute the following command:

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.

The system creates a user authentication file named myAuthentication.txt in the current directory. You can change file name. The file name and file extension .txt must use single-byte characters. If you rename the file, change the name of the user authentication file in the .bat file.

Example: user authentication file for an IPv4 address

On Windows, the system creates the myAuthentication.txt text file using the IPv4 address (192.168.0.1), user ID (administrator), and password (adminpassword).

mkatfile 192.168.0.1 administrator adminpassword >myAuthentication.txt

Example: user authentication file for an IPv6 address

On Windows, the system creates the myAuthentication.txt text file with the IPv6 address (fe80::20a:e4ff:fe8f:20b5), user ID (administrator), and password (adminpassword).

mkatfile [fe80::20a:e4ff:fe8f:20b5] administrator adminpassword >myAuthentication.txt

CLI command file locationsThe following table lists the directory and filenames of the CLI commands (batch files). Windows and UNIX files are stored in the same directory.


The following table lists file and directory names that you can change. If you make a change in the If... column, then you must make the corresponding change that is listed in the You must change... column.

Examples of the batch file for the CFLSET command

The following table lists examples of the batch file for the CFLSET command.

CLI termination codesWhen the system processes a command, the system writes a CLI termination code. Even when the termination codes appear correct, check for errors in the spreadsheet.

The following table lists the CLI termination codes that the system returns when you execute a CLI command (batch file).

Directory File name Description

CFLCLITool\sample (For Windows) CFLCHK.bat

(For Unix) CFLCHK.sh

Validates the spreadsheet to be applied to the CFLSET command.

(For Windows) CFLGET.bat

(For Unix) CFLGET.sh

Retrieves storage system information.

(For Windows) CFLSET.bat

(For Unix) CFLSET.sh

Applies the contents of the spreadsheet to the storage system.

If... You must change...

You rename the user authentication file name...

The .txt file in each CLI command file to the file name that you specified.

You move the directory where you store the user authentication file to a directory other than “/CFLCLITool”...

This directory location in each file to the relative or absolute path. You can only specify single-byte characters for path or file names.

(For UNIX) You install a shell program in a directory other than "/bin"...

The #! /bin/csh directory name in the first row in each file to your installation directory. For example, /usr/bin/csh).

Operating system Batch file

Windows java -jar -Djava.security.policy=java.policy JSanCLI.jar myAuthentication.txt CFLSET %1 %2

UNIX #! /bin/cshjava -jar -Djava.security.policy=java.policy JSanCLI.jar myAuthentication.txt CFLSET $1 $2

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 appear at the command prompt. The following table lists CLI termination code references that you can use.

Example of a CLI termination code reference

This example shows a reference to a CLI termination code that you can use in a Windows batch file. When you run the batch file and the system returns a CLI termination code of 0, the “COMMAND SUCCESSFUL” message appears. If the system receives a CLI termination code other than 0, the “COMMAND FAILED” message appears.

java -Djava.security.policy=java.policy -jar JSanCLI.jarmyAuthentication.txt CFLGET %1 %2if %errorlevel% NEQ 0 echo COMMAND FAILED.if %errorlevel% EQU 0 echo COMMAND SUCCESSFUL.

Batch file or Shell script Termination code reference

Windows batch file %errorlevel%

UNIX Bourne shell script %?

UNIX C shell script %Status

3

LUN Expansion operations 3–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

LUN Expansion operations

Use spreadsheets in LUSE to retrieve volume information and create and release LUSE volumes. You use CLI in LUSE to process spreadsheets.

□ LUN Expansion spreadsheet tasks

□ Prerequisites for using spreadsheets in LUN Expansion

□ Workflow for CLI-based spreadsheets in LUN Expansion

□ CLI-based spreadsheet format in LUN Expansion

□ LUN Expansion command summary

□ Editing CLI-based spreadsheet templates in LUN Expansion

□ Validating CLI-based spreadsheets in LUN Expansion

□ Correcting validation errors in LUN Expansion

□ Running CLI-based spreadsheets in LUN Expansion

□ Troubleshooting runtime CLI errors in LUN Expansion


3–2 LUN Expansion operations

LUN Expansion spreadsheet tasksSpreadsheet templates for the following tasks are provided with SN:

• Creating LUSE volumes. For more information about creating volumes, see Creating LUN Expansion volumes.

• Retrieving information about logical volumes (LDEV) that can be combined into LUSE volumes. For more information about retrieving logical volumes, see Retrieving information about logical volumes in LUN Expansion.

• Identifying LDEVs that are part of LUSE volumes.

• Releasing LUSE volumes. For more information about releasing volumes, see Releasing LUN Expansion volumes.

Prerequisites for using spreadsheets in LUN ExpansionBefore using spreadsheets in LUSE, ensure you have met the following prerequisites:

• The CLI and accompanying third-party files are installed.

• You have the appropriate permissions.

• All resource group IDs that are set to the storage system are assigned to the user ID referenced in the user authentication file of the SN CLI.

For more information on how to install the CLI files or change user permissions, see Command Line Interface installation and commands on page 2-1.

Workflow for CLI-based spreadsheets in LUN ExpansionUse the following workflow to process CLI-based spreadsheets in LUSE:

1. Make a copy the spreadsheet template from the tools folder and save it with a unique name to a working folder or the desktop. For more information on locating the tools folder, see Copying CLI tools on page 2-3.

2. Do the following until no errors exist:

Edit the spreadsheet. For more information about editing spreadsheets, see Editing CLI-based spreadsheet templates in LUN Expansion.

Validate the spreadsheet. For more information about validating spreadsheets, see Validating CLI-based spreadsheets in LUN Expansion on page 3-4.

3. On the SN system, run the spreadsheet. For more information on how to run a spreadsheet, see Running CLI-based spreadsheets in LUN Expansion on page 3-7.

CLI-based spreadsheet format in LUN ExpansionThe following example shows the spreadsheet format in LUSE:


#!Version Version number, program product, type,;

Operation tag

Parameter

The italic text are the variables you must change to values appropriate for your storage system deployment.

The following table describes the variables used in the spreadsheet format.

For more information about spreadsheet format requirements, see Spreadsheet format requirements.

LUN Expansion command summaryTo create a spreadsheet to automate an operation, copy the correct operation tag and parameters into a spreadsheet template that retrieves information (Get) or expands or releases volumes (VolumeOperation).

The following table lists the commands, operation tags, version numbers, and template file names available for LUSE.

Variables Content

First row—declaration line

#! Indicates the declaration line. You cannot edit this row.

Version number The number that corresponds to the operation tag.

Program product “CLI_LUSE” for LUSE

Type The command that retrieves information or performs an operation. Enter a comma and a semicolon with no space between them (,;) after the type.

Second row

Operation tag Indicates the type of information to be collected or the operation to do. Surround operation tags with brackets.

Third row

Parameter The LDEV data that is necessary to run the operation.

Command Operation Tag Version number Template with Program Product Name

Get LUSE 06_01_00 LUSE_Get_def.spd

SerialNumber

VolumeOperation Expansion 06_01_00 LUSE_Expansion_def_.spd

LUSE_Release_def_.spdRelease

SerialNumber



You can retrieve LUSE information by issuing the GET command. You can expand or release a volume by issuing the VolumeOperation command. The SerialNumber operation tag matches the serial number of the storage system with the serial number in the spreadsheet. You can use this tag with either command type.

Editing CLI-based spreadsheet templates in LUN Expansion

1. Launch a spreadsheet application, such as Microsoft Excel, and open the spreadsheet.

2. Change the variable placeholders to meet your storage needs.

3. Edit the spreadsheet.


Validating CLI-based spreadsheets in LUN Expansion1. (For Windows) Open a command prompt (Start > Run) and execute the

following command:

CFLCHK input-file-name output-file-name

Example:

CFLCHK LUSE_ReleaseOperation.spd LUSE_ReleaseOperation_Result.spd

In this example, the LUSE_ReleaseOperation.spd spreadsheet is checked and the results are copied to the LUSE_ReleaseOperation_Result.spd spreadsheet.

2. Execute the following command:

CFLSET

Note: For UNIX, execute the following command: CFLCHK.sh

Operand Description

input-file-name The spreadsheet you want to verify. Include the relative or absolute path.

Character limit: 240

output-file-name The output file name. Include the relative or absolute path.



“Normal end” appears at the end of each correctly processed line.

Correcting validation errors in LUN ExpansionIf you find errors in the spreadsheet results, edit the spreadsheet and execute the CFLCHK command again until no errors exist. Use the following guidelines to check for errors in the results file:

• Message codes appear at the end of lines that contain errors. For more information, see Hitachi Storage Navigator Messages.

• Check errors from the last row with an error.

• If a lower layer has an error, the upper layers also show an error even though no error might exist.

• If a higher layer has an error, parameters in the lower layers are not verified. After correcting the error in the upper layer, execute the CFLCHK command to check for errors further down.

Example 1

#!Version

06_01_00,CLI_RemoteCopyJournalMF,PairOperation,;Error(6505-66004)

[SerialNumber]

64040,;Check OK

[Suspend-Pair]

#^,;Check NG(6505-66004)

00,04,40,01,P-VOL,00,64040,Mirror,Disable,Flush,;

This example shows two errors:

• In the declaration line (the first row). The (xxxx-yyyyy) following “Error” is a code-error code. For more information about the error codes, see Hitachi Storage Navigator Messages.

• In the SuspendPair operation tag, identified in the row below beginning begins with #^. An error occurred in the SuspendPair operation tag.

Example 2

Note: Processing stops when you right-click the command prompt window while the command prompt is not in Quick Edit Mode. To start processing, press the Esc key or left-click the command prompt window.

Processing also stops if you left-click when the command prompt is in Quick Edit Mode. To start processing, press the Esc key or right-click the command prompt window.

If CLI processing is suspended for a long period, the Remote Method Invocation (RMI) time-out occurs and your log-in status is cancelled. When you resume processing, an error (0001 4011) occurs. To resume processing and avoid this error, open a new command prompt window.



#!Version

06_01_00,CLI_RemoteCopyJournalMF,PairOperation,;Warning(1305-66578)

[SerialNumber]

64040,;Normal end

[SuspendPair]

00,04,40,01,P-VOL,00,64041,Volume,Disable,Flush,;Error(6505-58075)

00,04,41,01,P-VOL,00,64040,Volume,Disable,Flush,;Normal end



This example shows three errors:

• In the declaration line (the first row), the warning indicates an invalid condition. For more information, see Hitachi Storage Navigator Messages.

• Errors appear in the first and fourth row in the SuspendPair operation tag.

Example 3

#!Version

06_01_00,CLI_ExternalStorage,VolumeOperationFibre,;Error(1305 66578)

[SerialNumber]

65536,;Normal end

[AddVolumeSetting]

1,1A,60060E8004F81370,0000,E1-1,Normal,00,OPEN-V,Disable,Enable,;Error(605-66797)

+,1B,60060E8004F81371,0001,;Error(605-66695)

+,+,00,00,00,96000,0004,;

The following example shows errors when the parameters are in a hierarchical structure:

• 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 layers lower than the error are not verified. After you correct the visible errors, finish processing the rest of the spreadsheet. From a command prompt, execute the CFLCHK command.


Running CLI-based spreadsheets in LUN ExpansionOpen a command prompt and execute the following CLI command types:

• CFLSET - changes system settings or performs an operation.

• CFLGET - retrieves storage system information and saves it in a file that you specify.

Making configuration changes in LUN ExpansionExecute the CFLSET command to change the configuration settings you have altered in the spreadsheet. Execute the CFLSET command to create a results file which you can use to check the operation completion status.

1. At a command prompt, change directories to the location of the spreadsheet file.

2. (For Windows) Execute the following command:

CFLSET input-file-name output-file-name

where:

For example:

CFLCHK LUSE_ReleaseOp.spd LUSE_ReleaseOp_Result.spd

3. Open the results file and verify that the operation completed successfully. If the operation does not finish successfully, troubleshoot the runtime CLI errors.

For more information about the errors, see Troubleshooting runtime CLI errors in LUN Expansion on page 3-10.

Retrieving storage system information in LUN ExpansionExecute the CFLGET command to retrieve storage system information. When you execute this command, a results file is generated. Use this results file to ensure that the operation completed successfully.

At a command prompt, change directories to the location of the spreadsheet file. (For Windows) Execute the following command:

CFLGET input-file-name output-file-directory

where:

Operand Description





Note: For UNIX, execute the following command:

CFLCHK.sh



For example:

CFLGET ExtStorage_VolumeOperation.spd C:\CFLoutput

Retrieving information about logical volumes in LUN ExpansionUse 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.

To retrieve information about logical volumes, execute the following command:

[LUSE] GET_ALL

The output is saved to a file.

Example spreadsheet:

LDEV information appears in layers.

Operand Description






CFLCHK.sh

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)


Each line shows one LDEV, identified by Logical Disk Controller (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.

Creating LUN Expansion volumesUse the Luse_Expansion_def_.spd spreadsheet template to create LUSE volumes. The volumes to be created are layered similarly in the spreadsheet as the output for retrieving LUSE volume information:

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

The following image shows an example spreadsheet:

• The example spreadsheet shows that three LUSE volumes are being created.

• Each LUSE volume needs the creation of two layers.

• The text between commas populates the spreadsheet column. In the example above, in the first row in the first LUSE volume to be created, “00” populates column A. In the second row, “+” populates column A, “00” populates column B, and so on.

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)



Releasing LUN Expansion volumesUse the Luse_Release_def_.spd spreadsheet template to release LUSE volumes. When you enter the volumes in the spreadsheet template, use the same layered order that you used in the Luse_Expansion spreadsheet when you created the LUSE volumes. For more information on how to create LUSE volumes, see Creating LUN Expansion volumes on page 3-9.

The following image shows an example spreadsheet:

• The example spreadsheet shows that three LUSE volumes are being released.

• To release a LUSE volume, under the [Release] operation tag, add the top LDEV in the LUSE volume in the following format:

LDKC-number:CU-number:LDEV-number

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 row in the first LUSE volume to be released, “00” populates column A. In the second row, “+” populates column A, “00” populates column B, and so on.

Troubleshooting runtime CLI errors in LUN ExpansionIf a results file indicates that a spreadsheet operation did not happen correctly, one of the following conditions might have occurred:

• A communication error.

• Volumes or pairs do not have a status of “Ready” and are not ready to accept changes.

• Another user is working with the storage system in SN in Modify mode.

If you have an error, correct the condition and execute the command again.

The following table contains other CLI-related troubleshooting information.


Error Codes and Operations Causes and Solutions

Error (1310 69052) • The directory specified as the output file might not exist. Make sure that the specified directory exists.

• You cannot write to the directory or file that is specified as the output file. Make sure that you can write to the specified directory or file.

• A correct version of Apache might not be installed on the SVP of the server. For more information about the correct version, call the Support Center.

For more information, see the Hitachi Storage Navigator User Guide.

When a suspended SN CLI process is resumed, error (0001 4011) occurs.

The RMI timeout occurred because the SN CLI processing was stopped. Execute the SN CLI command again.

Error (java.lang.NoClassDefFoundError)

• You do not have the Java version that meets the operating condition installed on the execution environment for the SN CLI. Ensure that you have the correct Java version installed.

For more information about the Java version, see Hitachi Storage Navigator User Guide.

• On the execution environment for the SN CLI, you have not defined an execution path to the correct Java version. Confirm the execution path.

• If you cannot solve the errors using the above solutions, call the Support Center.




4

LUN Manager operations 4–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

LUN Manager operations

Use spreadsheets in LUNM to change storage system settings. You use CFL in LUNM to process spreadsheets.

□ LUN Manager spreadsheet tasks

□ Workflow for CFL-based spreadsheets in LUN Manager


4–2 LUN Manager operations

LUN Manager spreadsheet tasksYou can configure a spreadsheet to add, change, or delete the following system settings:

• Configuration settings, which include:

Arbitrated loop-physical address (AL-PA)

Data transfer speed (host speed)

Topology

LUN security

• [HostGroup] function tag settings

• [WWN] function tag settings

• Path settings

• Command device settings

Workflow for CFL-based spreadsheets in LUN ManagerUse the following workflow to process CFL-based spreadsheets:

1. Export the system settings to a spreadsheet.

For more information about exporting system settings, see Exporting system settings to spreadsheets in LUN Manager on page 4-2.

2. Set up the spreadsheet for editing.

For more information about setting up spreadsheets, see Setting up spreadsheets for editing in LUN Manager on page 4-3.


For more information about editing spreadsheets, see Editing CFL-based spreadsheets in LUN Manager on page 4-6.

4. Import the spreadsheet.

For more information about importing spreadsheets, see Importing and validating spreadsheets in LUN Manager on page 4-13.

5. Apply the changes to the spreadsheet.

For more information about applying changes, see Applying changes to CFL-based spreadsheets in LUN Manager on page 4-15.

Exporting system settings to spreadsheets in LUN ManagerUse this procedure to export system settings from CFL to a spreadsheet. When you export the system settings, the spreadsheet is created.

1. In SN, select Actions > Other Functions > Configuration File Loader.

Note: If the spreadsheet imports with errors, correct the errors by editing the spreadsheet then repeat this step.

For more information about correcting errors, see Errors when importing spreadsheets in LUN Manager on page 4-14.


2. Change to modify mode by clicking the Modify icon.

3. In the Configuration File Loader window, click Select Sheet and then select the product whose system settings you want to export.

4. Click Export.

5. In the LUN Manager window, enter or browse to a path where you want to export the file in the File Name on Client field. You must follow the file name requirement. For more information about the file name requirements, see Spreadsheet format requirements on page 1-3.

6. Click Export. The spreadsheet is exported to the location you specified.

Setting up spreadsheets for editing in LUN ManagerUse this procedure to set up the new configuration definition area in the spreadsheet, the area of the spreadsheet that you can edit. The new configuration definition area is the area you can edit in the spreadsheet and consists of the 11th through 17th columns (columns K through Q) in the spreadsheet.

The exported spreadsheet contains 10 columns (columns A through J). The current configuration definition area consists of the 1st through 7th columns (columns A through G) in the spreadsheet. The 8th through 10th columns (columns H through J) in the spreadsheet remain blank.

The following figure shows a spreadsheet with the current configuration definition area displayed on the left of the spreadsheet and the new configuration definition area on the right.


Note: If you use a Web browser for UNIX systems, the Download Manager dialog box can display. If this dialog box displays, close it.



2. Starting at the 1st column (column A), select and copy the fields in the current configuration definition area of the spreadsheet.

3. Starting at the 11th column (column K), paste the copied fields in the right side of the spreadsheet. The new configuration definition area is created.

4. Add the word Change to the declaration row in the third column (Column C).

CFL-based spreadsheet format in LUN Manager

The following example shows the spreadsheet format:

#!Version Version number,program product,process mode,;

Function tag

Definitions

For more information about the function tags, see Function tags in spreadsheets in LUN Manager on page 4-5. For more information about the definitions, see Definitions used in spreadsheet formats in LUN Manager on page 4-6.


Note: Do not select the declaration line (the first row).

Note: Any configuration definitions you omit from the copy area and do not paste in the new configuration definition area are deleted when you apply the changes to the spreadsheet. For more information about applying changes, see Applying changes to CFL-based spreadsheets in LUN Manager on page 4-15

Variables Description


#! Declaration line. Do not alter this row.

Version Indicates that the RMI version number follows. You cannot change Version. A space follows Version.

Version number RMI version followed by a comma with no space.

Example: 06_01_00

Program product The program product followed by a comma with no space.

Enter LUN.

Process mode “Change”. Indicates adding, changing, deleting. The downloaded spreadsheet does not have a process mode.

Second row

Function tag [Port], [HostGroup], [WWN], [LUN], [LDEV]

Indicates the function tags in the above order, enclosed in brackets.

Row following function tag

Definitions System configuration data.



The following table shows sample function tags and parameters with current and new column locations.

Function tags in spreadsheets in LUN Manager

Each spreadsheet has its own operations or functions and parameters. The function tags contained within a spreadsheet are classified according to the function. Function tags describe the type of function and the settings.

Function tag definitions are applied to the storage system one at a time in the order they appear in the spreadsheet. Comments and definitions written in the same row as the function tag are ignored.

Definitions in earlier function tags can affect function tags that appear later in the spreadsheet. For example, if you delete a host group in the [HostGroup] function tag, the path definitions related to the deleted host group are also deleted. If you then write definitions for the deleted path in the [LUN] or [WWN] function tag, which appear later in the spreadsheet, an error occurs.

You must enter at least one function tags in the spreadsheet. Enter function tags beginning with the first column in the row (column A). In the first column, enter the tag without space.

ColumnFunction Tag

[Port] [HostGroup] WWN [LUN] [LDEV]

Current

(no editing)

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 *

Column 9th

10th

New

(for editing)

11th Port Port Port Port Ldkc

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 row after the function tag is a commented heading row that shows the required values. In the following example, Security Switch after the hash symbol (#) is the heading, separated by a comma.

[Port]

#Port, Security Switch

Adhere to the following rules when working with function tags:

• Do not delete the [Port] and [LDEV] function tags. You must enter a new definition for these functions. If you delete these functions, an error is generated.

• Add the symbols #$ at the beginning of lines that contain existing settings. Do not change comment rows.

Example:

[LUN]

#Port, Group Id, LunId, Ldev (items to be changed)#$1C,0,1,1,1,1 (existing settings row)

Definitions used in spreadsheet formats in LUN Manager

Definitions are the parameters you enter when editing the new configuration definition area in spreadsheets. A definition consists of the index and the parameter. The index is fixed for each function tag.

The following figure shows a sample spreadsheet showing the index, parameter and the new configuration definition area, which is the editable area of the spreadsheet:

Editing CFL-based spreadsheets in LUN ManagerThe following is a list of best practices when working with definitions:

• Edit in the new configuration definition area of the spreadsheet.

• Change current settings by entering a different parameter. The format must be the same as the existing setting.

Change definitions using the same definition format in the new configuration definition area that is used in the current configuration definition area.


For more information about definitions, see Definitions used in spreadsheet formats in LUN Manager on page 4-6.

• Add new definitions when the current setting is blank and has not yet been specified.

• Delete the unused function tags from the spreadsheet. Delete them by removing them from the new configuration definition area of the spreadsheet.

For more information about function tags, see Function tags in spreadsheets in LUN Manager on page 4-5.

Use this procedure to edit CFL-based spreadsheets in LUNM. You edit the spreadsheet by adding, changing, and deleting the parameter definitions in the new configuration definition area of the spreadsheet.

1. Launch a spreadsheet application, such as Microsoft Excel, and open the exported spreadsheet.

2. Do the following:

Change the variables to values appropriate for your storage system deployment.

Use the spreadsheet format to edit the configuration settings. For more information about CFL-based spreadsheet formats, see Definitions used in spreadsheet formats in LUN Manager on page 4-6.

Change the function tags and command device settings:

Change port settings. For more information about changing port settings, see Changing the port settings in LUN Manager on page 4-7.

Change [HostGroup] function tag settings. For more information about configuring host groups, see Configuring host groups in LUN Manager on page 4-8.

Change [WWN] function tag settings. For more information about configuring WWN information, see Configuring WWN information in LUN Manager on page 4-10.

For more information about configuring LU paths, see Configuring LU paths in LUN Manager on page 4-11.

For more information about changing command device settings, Changing command device settings in LUN Manager on page 4-12.


Changing the port settings in LUN Manager

You set port information and change the security switch (LUN security) between Enable (ON) and Disable (OFF) by editing the [Port] function tag parameter. You cannot add or delete this function tag.

The following table lists the available definitions for the [Port] function tag.

Note: The function tags that remain in the spreadsheet with existing definitions are deleted from the spreadsheet when you import the spreadsheet.



Configuring host groups in LUN Manager

You can add, delete, or change host group settings using the [HostGroup] function tag parameters. You can delete the settings for host group 0 (zero), but you cannot delete the host group. If you delete all the settings for host group 0, the settings revert to the default settings.

If you delete the host group, the system deletes the WWN and path definition of that host group. If you edit settings for a host group that is deleted in the [LUN] or [WWN] function tag, an error will occur.

The following table lists the available definitions for the [HostGroup] function tag.

Column Item Available values

11th (Index)

Port Set one of the following:

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

1G, 3G, 5G, 7G, 1H, 3H, 5H, 7H, 2G, 4G, 6G, 8G, 2H, 4H, 6H, 8H

1J, 3J, 5J, 7J, 1K, 3K, 5K, 7K, 2J, 4J, 6J, 8J, 2K, 4K, 6K, 8K

1L, 3L, 5L, 7L, 1M, 3M, 5M, 7M, 2L, 4L, 6L, 8L, 2M, 4M, 6M, 8M

1N, 3N, 5N, 7N, 1P, 3P, 5P, 7P, 2N, 4N, 6N, 8N, 2P, 4P, 6P, 8P

1Q, 3Q, 5Q, 7Q, 1R, 3R, 5R, 7R, 2Q, 4Q, 6Q, 8Q, 2R, 4R, 6R, 8R

9A, BA, DA, FA, 9B, BB, DB, FB, AA, CA, EA, GA, AB, CB, EB, GB

9C, BC, DC, FC, 9D, BD, DD, FD, AC, CC, EC, GC, AD, CD, ED, GD

9J, BJ, DJ, FJ, 9K, BK, DK, FK, AJ, CJ, EJ, GJ, AK, CK, EK, GK

9L, BL, DL, FL, 9M, BM, DM, FM, AL, CL, EL, GL, AM, CM, EM, GM

Ports threshold: 192

Editable column Item Available value

12th Group Id Set with hexadecimal numbers in one or two digits.

Range: 00 - FE

13th Group Name Character limit: 64 single-byte ASCII characters (letters, numerals, and symbols)

Case Sensitive: Yes

Example: company and Company are recognized as different host group names.

Note:

• Prohibited symbols: \ / : , ; * ? " < > |

• You cannot use blanks at the beginning or end of the host group name.


Host mode option

The host mode option consists of 96 flags (0 to 95), which are stored in bits of 32. Binary bit flags (option flags) are assigned to each ID, starting with zero (0). Every four binary bit flags are set as a group, which is converted to a hexadecimal number that represents the host mode option.

The following figure shows the flags with option flag IDs from 0 to 31.

The following figure shows an example in which the host mode option becomes “1AB30005”.

The following table shows binary to hexadecimal conversion.

14th Host Mode Range: 00 - 4F. Set with hexadecimal numbers in one or two digits.

15th Option[0:31] Set with hexadecimal numbers in from one digit to eight digits*. You can omit the “0”s at the head of the number. For example, you can enter “00000FE3” as “FE3”.

Default (during export): 8 digits

Range:0 - FFFFFFFF

For more information about host mode, see Host mode option on page 4-9.

16th Option[32:63]

17th Option[64:95]

Editable column Item Available value

Binary number Hexadecimal number Binary number Hexadecimal

number

000 0 100 8

000 1 100 9

001 2 101 A

001 3 101 B

010 4 110 C

010 5 110 D



Configuring WWN information in LUN Manager

You can add, delete, or change WWN information by editing [WWN] function tag parameters. The following table lists items and values available for the [WWN] function tag.

011 6 111 E

011 7 111 F

Binary number Hexadecimal number Binary number Hexadecimal

number

Column Item Available Values

11th (Index) Port One of the following can be set:














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.


Configuring LU paths in LUN Manager

You can add, delete, or change LU path definitions by editing [LUN] function tag parameters. The following table lists items and values available for the [WWN] function tag.

14th Nickname Character limit: 64 single-byte ASCII characters (letters, numerals, and symbols)

Case Sensitive: Yes

Example: company and Company are recognized as different host group names.

Note:

• Prohibited symbols: \ / : , ; * ? " < > |

• You cannot use blanks at the beginning or end of the nickname.

15th to 17th Blank

Column Item Available Values


11th (Index) Port One of the following can be set:














12th (Index) Group Id 00 - FE. Set with hexadecimal numbers in one or two digits.

13th (Index) LunId 0000 - 07FF. Set with hexadecimal numbers in up to four digits.



Changing command device settings in LUN Manager

You can change command device settings by editing [LDEV] function tag parameters. Though you can change, you cannot add or delete command device settings with the [LDEV] function tag.

The following are restrictions when changing command device settings:

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

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

• In the spreadsheet, change the colons that usually separate the LDEV numbers for an LDEV to commas.

For example:

[LDEV]

00,00,01,Disable,Disable,,,,,, 00,00,01,Enable,Enable00,01,01,Disable,Disable,,,,,, 00,01,01,Enable,Disable00,02,01,Disable,Disable,,,,,, 00,02,01,Enable,Disable00,03,01,Disable,Disable,,,,,, 00,03,01,Enable,Disable

The following table lists the values for the [LDEV] function tag.

14th Ldkc 00

15th Cu 00 - FE. Set with hexadecimal numbers in one or two digits.

16th Ldev 00 - FF. Set with hexadecimal numbers in one or two digits.

17th Blank


Column Item Available value

11th (Index) Ldkc 00

12th (Index) Cu 00 - FE. 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

(Command Device)

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.


Importing and validating spreadsheets in LUN ManagerUse this procedure to import the spreadsheet back into CFL and validate it.

Importing CFL-based spreadsheets does the following:

• Accepts the spreadsheet.

• Verifies the formats of the function tags.

• Validates the contents.

• Compares the function tags in the current configuration definition area with the function tags you added to the new configuration definition area. If errors are not detected, the spreadsheet status changes to “Ready”. If errors are detected, the spreadsheet status changes to “Error” and the error messages are displayed in the Error Information list.

For more information about this list, see Errors when importing spreadsheets in LUN Manager on page 4-14.



3. In the Configuration File Loader window, click Select Sheet and then select the software application whose spreadsheet you want to import.

4. Click Import. The spreadsheet is accepted by CFL. The spreadsheet status changes to “Ready”.

15th Cmd. Sec (Command Device Security)



16th Cmd.Usr (User Authentication)



17th Cmd.Grp (Device Group Definition)



Caution: When configuration definitions are long, the [LDEV] function tag might not appear in the exported spreadsheet. In that case, add the [LDEV] function tag and set the command device.

Caution: The 18th column is used only for outputting information. Do not specify attributes in this column. When changing settings, you must specify the 18th column as a blank.

Column Item Available value



Errors when importing spreadsheets in LUN Manager

You can get errors when importing spreadsheets into CFL. If you get errors, ensure the spreadsheet is meeting the following requirements:

• The spreadsheet file meets the spreadsheet format requirements. For more information about spreadsheet format requirements, see Spreadsheet format requirements on page 1-3.

• The definitions are entered properly:

The spreadsheet contains at least one definition.

The spreadsheet file contains supported definition values.

The parameter ranges are correct.

For more information about definitions in CFL-based spreadsheets, see Definitions used in spreadsheet formats in LUN Manager on page 4-6. For more information about supported formats in VRM, see CFL-based spreadsheet format in LUN Manager on page 4-4.

• The function tags are entered properly:

The spreadsheet contains at least one function tag.

The spreadsheet contains supported function tags.

The function tags contain an valid parameter.

For more information about function tags in CFL-based spreadsheets, see Function tags in spreadsheets in LUN Manager on page 4-5

• The declaration line has been entered properly.

For more information about the declaration line, see CFL-based spreadsheet format in LUN Manager on page 4-4.

• The version number is entered properly.

For more information about the version number, see CFL-based spreadsheet format in LUN Manager on page 4-4.

Viewing import error messages in LUN Manager

You can receive errors when importing spreadsheets which imports the spreadsheet (the spreadsheet is accepted) but changes the spreadsheet status to “Error”. The error code and detailed information about the error is displayed in the Error Information list in CFL. Each line in this list shows the affected row in the spreadsheet, the error code, the column in the spreadsheet, and a description. The spreadsheet status is also displayed in this list.

The values listed in the Select Tag list are the function tags that you have added to the new configuration definition area of the spreadsheet. An asterisk (*) appears after the function tags that have an error. For more information about the function tags in the new configuration definition area, see Function tags in spreadsheets in LUN Manager on page 4-5.

For more information about the errors that can occur during the import process, see Hitachi Storage Navigator Messages.



2. In the Configuration File Loader window, select the function tag you want to display from the Select Tag list. The error information for that function tag is displayed in the Error Information list.

Applying changes to CFL-based spreadsheets in LUN ManagerUse this procedure to apply the changes you made to the settings in the spreadsheet to the system. You must import the spreadsheet without errors and the spreadsheet status must be “Ready” before you can apply the changes.

All changes are applied except when one of the following conditions is present:

• The current spreadsheet matches the imported spreadsheet. The spreadsheet is accepted, but since you have made not changes to the spreadsheet, the spreadsheet is not applied to the system.

• The spreadsheet is needed to process I/O and you are attempting to delete it.

• All the resource group IDs that are set to the storage system are not assigned to the user account who logs in to SN.

For more information about errors when applying changes in CFL-based spreadsheets, see Errors when importing spreadsheets in LUN Manager on page 4-14.


2. Click Apply.

Errors when applying CFL-based spreadsheets in LUN Manager

When you use CFL to apply the volume settings and an error occurs, the settings are applied normally. If necessary, you can reset the volume settings where the error is displayed. You can view the status of the spreadsheet in the bottom right of the Error Information list in CFL.

If the volumes where you apply the settings are valid for one of the following conditions, an error message is displayed. Check the following settings or make changes to the configuration as appropriate:

• LDEVs that are not mapped to physical devices and are therefore undefined

• Volume usable by open-systems (except multiplatform volumes)

• Journal volumes

• Compatible FlashCopy V2 volumes

• System Disk volumes

• LDEVs that are configured as command devices

• You have not downloaded the software application (except when you change the access attribute to Read/Write)

• Volumes whose emulation types are 3390-V

• Volumes that are comprised of a pool



• Volumes for Compatible Software for IBM® FlashCopy® SE

• Volumes for Mainframe Fibre Data Migration

5

Universal Volume Manager operations 5–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Universal Volume Manager operations

Use spreadsheets for UVM to retrieve system information and map external volumes to the local system. You use CLI in UVM to process spreadsheets.

□ Universal Volume Manager spreadsheet tasks

□ Prerequisites for using spreadsheets in Universal Volume Manager

□ Workflow for CLI-based spreadsheets in Universal Volume Manager

□ CLI-based spreadsheet format in Universal Volume Manager

□ Universal Volume Manager command summary

□ Editing CLI-based spreadsheets in Universal Volume Manager

□ Validating CLI-based spreadsheets in Universal Volume Manager

□ Correcting validation errors in Universal Volume Manager

□ Running CLI-based spreadsheets in Universal Volume Manager

□ Troubleshooting runtime CLI errors in Universal Volume Manager


5–2 Universal Volume Manager operations

Universal Volume Manager spreadsheet tasksThe CLI can process custom spreadsheets for UVM tasks, such as:

• Retrieve SSID information.

• Retrieve external group information.

• Retrieve external volume information.

• Map external volumes with LDEVs.

• Disconnect an external volume.

• Restore an external volume.

• Delete the mapping to an external volume.

• Move external volumes from one path group to an existing path group or to a new group path.

Use the spreadsheet templates that are provided in SN for these activities in UVM. For more information about the spreadsheet templates, see Universal Volume Manager command summary.

Prerequisites for using spreadsheets in Universal Volume Manager

Before using spreadsheets in UVM, ensure you have met the following prerequisites:

• The CLI and accompanying third-party files are installed.



For more information on how to install the CLI files or change user permissions, see Command Line Interface installation and commands on page 2-1.

Workflow for CLI-based spreadsheets in Universal Volume Manager

Use the following workflow for CLI-based spreadsheets:

1. Make a copy the spreadsheet template from the tools folder and save it with a unique name to a working folder or the desktop.

For more information on how to locate the tools folder, see Copying CLI tools on page 2-3.

2. Do the following until no errors exist:a. Edit the spreadsheet, and then save your changes.b. Validate the edited spreadsheet. For more information about

validating CLI-based spreadsheets in UVM, see Validating CLI-based spreadsheets in Universal Volume Manager.


3. On the SN system, run the spreadsheet. For more information on how to run a spreadsheet, see Running CLI-based spreadsheets in Universal Volume Manager on page 5-7

CLI-based spreadsheet format in Universal Volume Manager

The following example shows the spreadsheet format in UVM:


Operation tag

Parameter



Universal Volume Manager command summaryTo create a spreadsheet to automate an operation, you must copy the correct operation tag and parameters into a template. You can copy the following operation tags into a template:

• Get - Retrieves information.

• VolumeOperationFibre - Expands or releases volumes.

The following table shows command types, the related operation tags, and spreadsheet templates available for UVM.

Variables Content


#! Indicates the declaration line. Do not alter this row.

Version number The number that corresponds to the operation tag.

Program product “CLI_ExternalStorage” for UVM.

Type Command that retrieves information or performs an operation. One comma and one semicolon with no space between them (,;) is after the type.

Second row


Third row

Parameter The LDEV data that is necessary to run the operation.



In addition to the operation tags shown in the table, you can also use the SerialNumber operation tag. Use this tag to verify that the serial number in the spreadsheet matches the serial number of the storage system. The SerialNumber operation tag is included in all spreadsheet templates.

Editing CLI-based spreadsheets in Universal Volume Manager

1. Launch a spreadsheet application, such as Microsoft Excel, and then open your copy of the spreadsheet template.




5. Validate your changes. For more information on how to validate your changes, see Validating CLI-based spreadsheets in Universal Volume Manager on page 5-4.

Validating CLI-based spreadsheets in Universal Volume Manager

After you edit a spreadsheet, validate the spreadsheet by executing the CFLCHK command and then execute the CFLSET command.

(For Windows) From the command prompt (Start > Run), execute the following command:


Command Operation tag Version number Spreadsheet Template

Get SSID

ExternalGroup

MappedVolume

06_01_00 ExternalStorage_Get_def.spd

VolumeOperationFibre

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


CFLCHK.sh



Correcting validation errors in Universal Volume ManagerIf you find errors in the spreadsheet results, edit the spreadsheet and execute the CFLCHK command again until no errors exist. Use the following guidelines to check for errors in the results file:

• Message codes appear at the end of lines that contain errors.

For more information, see Hitachi Storage Navigator Messages.


• If a lower layer has an error, the upper layers also show an error—even though no error might exist.

• If a higher layer has an error, parameters in the lower layers are not verified. After correcting the error in the upper layer, execute the CFLCHK command to check for errors further down.

Example 1

#!Version 06_01_00,CLI_RemoteCopyJournalMF,PairOperation,;Error(6505-66004)

[SerialNumber]

64040,;Check OK

[Suspend-Pair]

#^,;Check NG(6505-66004)



Operand Description





Note: Processing stops when you right-click the command prompt window while the command prompt is not in Quick Edit Mode. To start processing, press the Esc key or left-click the command prompt window.

Processing also stops if you left-click when the command prompt is in Quick Edit Mode. To start processing, press the Esc key or right-click the command prompt window.

If CLI processing is suspended for a long period, an RMI time-out occurs and your log-in status is cancelled. When you resume processing, an error (0001 4011) occurs. To resume processing and avoid this error, open a new command prompt window.



• In the declaration line (first row). The (xxxx-yyyyy) following “Error” is a code-error code.


• In the SuspendPair operation tag, identified in the row below beginning begins with #^. An error occurred in the SuspendPair tag.

Example 2

#!Version


[SerialNumber]

64040,;Normal end

[SuspendPair]






• In the declaration line (first row), the warning indicates an invalid condition.


• Errors appear in the first and fourth row in the SuspendPair tag.

Example 3

#!Version 06_01_00,CLI_ExternalStorage,VolumeOperationFibre,;Error(130566578)

[SerialNumber]65536,;Normal end

[AddVolumeSetting]1,1A,60060E8004F81370,0000,E1-1,Normal,00,OPEN-V,Disable,Enable,;Error(605-66797)+,1B,60060E8004F81371,0001,;Error(605-66695)+,+,00,00,00,96000,0004,;

The example shows errors when the parameters are in a hierarchical structure:


• Parameters in the layers lower than the error are not verified. After you correct the visible errors, finish processing the rest of the spreadsheet. Execute the CFLCHK command.


Running CLI-based spreadsheets in Universal Volume Manager

Use the following procedure to run the validated spreadsheet. Execute the command on the SN computer.

Open a command prompt and execute the following CLI commands:

• CFLSET - to change system settings or perform an operation.

• CFLGET - to retrieve system information to a file.

Changing the configuration settings in Universal Volume ManagerExecute the CFLSET command to change the configuration settings you changed in the spreadsheet or to do other tasks. When you execute this command, a results file is created. Use this file to check operation completion status.




where:

3. Check the results file to verify that the operation completed successfully. If the operation does not finish successfully, troubleshoot the runtime CLI errors. For more information, see Troubleshooting runtime CLI errors in Universal Volume Manager on page 5-19.

Retrieving storage system information in Universal Volume Manager

Execute the CFLGET command to retrieve storage system information. When you execute this command, a results file is generated. Use this results file to ensure that the operation completed successfully.



where:

Operand Description






CFLCHK.sh



For example:


Retrieving SSID information in Universal Volume ManagerUse the ExternalStorage_Get_def.spd spreadsheet template to retrieve LDEV and SSID information from the storage system. Information is returned concerning both internal and external volumes.

To retrieve SSID information, run the following command:

[SSID] GET_ALL,;


The following table shows information returned for the SSID tag.

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,;

Retrieving external-volume group information in Universal Volume Manager

Use the ExternalStorage_Get_def.spd spreadsheet template to retrieve information regarding external-volume groups that are configured to the local storage system.

To retrieve external-volume group information, run the following command:

[ExternalGroup] GET_ALL,;

Operand Description






CFLCHK.sh

Column Returned value Content

A LDKC:CU:LDEV-LDEV The range of LDEV numbers to which the SSID is assigned.

B SSID The SSID.



The following table lists the information returned for the ExternalGroup operation tag.

Retrieving external volume information in Universal Volume Manager

Use the ExternalStorage_Get_def.spd spreadsheet template to retrieve information regarding external volumes that are associated with the local storage system.

To retrieve external volume information, execute the following command:

[MappedVolume] GET_ALL,;


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 (++).

The following table shows the information that is returned for the MappedVolume function tag.

Column Parameter Content

A ExG External volume group number and its sequential number.


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.

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.



Mapping external volumes with multiple LDEVs in UVMUse the ExternalStorage_AddVolumeSetting_def_.spd spreadsheet template to map external volumes to the storage system. With this template you can create multiple LDEVs in an external volume.

For more information on how to create one LDEV per external volume, see Mapping external volumes with one LDEV in Universal Volume Manager on page 5-14.

Use the AddVolumeSetting tag to specify LDEV capacity in blocks, which results in an LDEV with a specified capacity. For example, use the AddVolumeSetting tag to create a pair.

Enter parameters in the spreadsheet in hierarchical layers. The following table shows identifiers and content for each layer.

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.


Layer Identifier Content Description

First None Information about external volumes and the primary path

This layer is required.

Second + Information about alternate paths

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.


The following table shows the AddVolumeSetting parameters.

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.


Column Parameter Description Values Characters

First Layer: Information about external volumes and the primary path.

A PathGroup Path group number. 0 to 63231 5 decimal digits or less

B Port Port number of the primary path. 1A to GR 2 digits or less

C WWN WWN of the primary path. 0000000000000000 toFFFFFFFFFFFFFFFF

16 hexadecimal digits

D LUN LU number set to the external volume. 0000 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, E16384-4096).

Grp: 1 to 16384

VPG: 1 to 4096

Grp: 5 decimal digits or less

VPG: 4 decimal digits or less

F Attribute • Normal: Maps an external volume.

• R-CMD: Maps a command device.

Normal

R-CMD

N/A

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.

For information about entering the same characters as the emulation type, see the Hitachi Universal Volume Manager User Guide.

N/A 16 or less in ASCII format

I CacheMode • Enable: Sets cache mode to Enable.

• Disable: Sets cache mode to Disable.

Enable

Disable

N/A

J InflowControl

• Enable: Sets inflow control to Enable.

• Disable: Sets inflow control to Disable.

Enable

Disable

N/A

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 GR 2 digits or less

C WWN WWN of the alternate path. 0000000000000000 to FFFFFFFFFFFFFFFF


Third Layer: Information about LDEVs to be created in an external volume.


B +



Example of mapping external volumes with multiple LDEVs

#!Version 06_01_00,CLI_ExternalStorage,VolumeOperationFibre,;

[SerialNumber]65536,;

[AddVolumeSetting]1,1A,60060E8004F81370,0001,E16384-4095,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.

E16384-4095 is configured for an external volume group (ExG).

• Two cross-storage system paths are configured as follows:

The primary path

C LDKC LDKC number 00 to 01 2 hexadecimal digits or less

D CU CU number 00 to FE 2 hexadecimal digits or less

E LDEV LDEV number. Specify an LDEV number that is not already assigned in another emulation group (grouped by 32 LDEV numbers).

For more information about emulation groups, see the Provisioning Guide for Open Systems or the Provisioning Guide for Mainframe Systems.

Ensure a number is assigned. To do this, open SN and check the LDEV tab on the Basic Information Display dialog box (File > Go > Basic Information).

00 to FF 2 hexadecimal digits or less

F Capacity Capacity of the LDEV in blocks.

For more information on how to calculate LDEV size in blocks and emulation considerations, see Specifying LDEV capacity in Universal Volume Manager on page 5-13.

1 to 8589934592

10 decimal digits or less

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. If you create an LDEV that does not have any SSID, specify an SSID that is not written in the output file.

For more information on SSIDs, see the Provisioning Guide for Open Systems or the Provisioning Guide for Mainframe Systems.

0004 to FFFE 4 hexadecimal digits or less



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

LDEV number: 00:00:00, 00:01:00, 00:02:00

LDEV capacity: 96,000 blocks

Specifying LDEV capacity in Universal Volume ManagerUse the following processes to specify LDEV capacity for OPEN-V emulation types and non-OPEN-V emulation types.

To specify OPEN-V emulation types:

• Limits: 96000 to 8589934592

• Create an LDEV 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. You cannot use the adjustment area 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.

• The capacity of the external volume must be 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 four LDEVs of 100,000 blocks each. The required capacity of the external volume is 401,056 blocks.



To specify non-OPEN-V emulation types:

• If the capacity of the external volume is equal to or larger than the base LDEV capacity, specify the base data area capacity. Make sure that the external volume capacity is greater than or equal to the total capacity of the base LDEV capacity for all the LDEVs.

• If the capacity of the external volume is smaller than the base LDEV capacity, create one or less LDEV. Find the capacity using the following equation:

LDEV capacity = floor[(External volume capacity – Control information area capacity) ÷ Cylinder capacity]× Cylinder capacity

In the equation, floor indicates that the value enclosed in brackets must be rounded down to the nearest whole number.

Use the following numbers for cylinder capacity:

For 3380 mainframe volumes: 1,440 blocks

For 3390 mainframe volumes: 1,740 blocks

For open volumes other than OPEN-V: 1,440 blocks

For more information on the base LDEV capacity, the base data area capacity, and the control information area capacity, see the Hitachi Universal Volume Manager User Guide.

Mapping external volumes with one LDEV in Universal Volume Manager

Use the ExternalStorage_AddVolumeSetting2_def_.spd template to create an LDEV in an external volume. LDEV capacity is not specified. The LDEV you create has the same capacity as the external volume. You can also use the [AddVolumeSetting2] tag when you use existing data in the external volume after mapping.

The system creates the LDEV with the following settings:

• LDEV capacity: the same capacity as the external volume*


• Emulation type: OPEN-V

• Cache mode: Disable

• Inflow control: Disable

Enter the parameters in the spreadsheet in hierarchical layers. For more information, see Mapping external volumes with multiple LDEVs in UVM on page 5-10.

The parameters are described in the following table.


First Layer: Information about external volumes and the primary path.

A PathGroup Path group number. 0 to 63231 5 decimal digits or less

B Port Port number of the primary path. 1A to GR 2 digits or less

C WWN WWN of the primary path. 0000000000000000 toFFFFFFFFFFFFFFFF


D LUN LU number set to the external volume. 0000 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, E16384-4096).

Grp: 1 to 16384

VPG: 1 to 4096



F Attribute • Normal: Maps an external volume.

• R-CMD: Maps a command device.

Normal

R-CMD

N/A

G CLPR CLPR that is used to access the external volume.

0 to 31 2 decimal digits or less

Second Layer: Information about alternate paths. Specify the paths in the order of descending priorities.


B Port Port number of the alternate path. 1A to GR 2 digits or less

C WWN WWN of the alternate path. 0000000000000000 to FFFFFFFFFFFFFFFF


Third Layer: Information about the LDEV to be created in the external volume.


B +

C LDKC LDKC number 00 to 01 2 hexadecimal digits or less

D CU CU number 00 to FE 2 hexadecimal digits or less



Disconnecting external volumes in Universal Volume ManagerUse the ExternalStorage_DisconnectVolume_def_.spd template to disconnect an external volume. To disconnect a volume, from the command prompt, execute the following command:

DisconnectVolume

Restoring external volumes in Universal Volume ManagerUse the ExternalStorage_CheckPath-RestoreVolume_def_.spd spreadsheet template to resume an individual external volume operation. To restore a volume, use the following operation tag:

CheckPath-RestoreVolume

E LDEV LDEV number. Specify a number not currently assigned.

Note: You can assign LDEV numbers in another emulation group (grouped by 32 LDEV numbers), in which case you cannot user them.

For more information, see the Provisioning Guide for Open Systems or the Provisioning Guide for Mainframe Systems.

Ensure a number is assigned. To do this, open SN and check the LDEV tab on the Basic Information Display dialog box (File > Go > Basic Information).

00 to FF 2 hexadecimal digits or less

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. If you create an LDEV that does not have any SSID, specify an SSID that is not written in the output file.

For more information on SSIDs, see the Provisioning Guide for Open Systems or the Provisioning Guide for Mainframe Systems.

0004 to FFFE 4 hexadecimal digits or less


Column Parameter Description Range of values

Number of characters

A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E16384-4096)

Grp: 1 to 16384

VPG: 1 to 4096




Deleting external volume mapping in Universal Volume ManagerUse the ExternalStorage_DeleteVolume_def_.spd spreadsheet template to delete external volume mapping.

For more information, see the prerequisite information deleting external volume mapping in the Hitachi Universal Volume Manager User Guide.

To delete a volume mapping, from a command prompt, execute the following command:

DeleteVolume

Moving external volumes to another path group in UVMUse the ExternalStorage_UnitePathGroup_def_.spd spreadsheet template to move all external volumes from one path group to another existing path group. When you move all external volumes to another existing path group, the original path group is deleted.

To move an external volume to another path group, use the following operation tag:

[UnitePathGroup]

Enter parameters in the spreadsheet in hierarchical layers. The following table shows identifiers and content for each layer.



A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E16384-4096).

Grp: 1 to 16384

VPG: 1 to 4096





A ExG External volume group number and its sequential number. The format should be EGrp-VPG (for example, E16384-4096).

Grp: 1 to 16384

VPG: 1 to 4096




First None Information about the path group external volumes moving to




The following table lists parameters and supported values.

Moving external volumes to a new path group in UVMUse the ExternalStorage_DividePathGroup_def_.spd spreadsheet template to move external volumes to a new path group. When you move external volumes to a new path and no other external volumes remain, the original path group is deleted.

To move external volumes to a new path group, use the following operation tag:

[DividePathGroup]

To move an external volume to a different, existing path group, use the ExternalStorage_UnitePathGroup_def_.spd template.

Enter parameters in hierarchical layers. The following table lists identifiers and the content for each layer.

The following table lists the DividePathGroup parameters.

Bottom + Information about the path group external volumes moving from

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.



First Layer: Information about the path group moving to.

A PathGroup Path group number 0 to 63231 5 decimal digits or less

Second Layer: Information about the path group moving from.


B TargetPathGroup

Path group number 0 to 63231 5 decimal digits or less


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

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.


Troubleshooting runtime CLI errors in Universal Volume Manager

If a results file indicates that a spreadsheet operation did not happen correctly, one of the following conditions might have occurred:


• Volumes or pairs do not have a status of “Ready” and are not ready to accept changes.


If you have an error, correct the condition and run the command again. The following table contains other CLI-related troubleshooting information.


Number of

characters

First Layer: Information about the path group moving from.

A PathGroup Existing path group number 0 to 63231


Second Layer: Information about the new path group.

A + Identifier

B NewPathGroup

New path group number 0 to 63231


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, E16384-4096).

Grp: 1 to 16384

VPG: 1 to 4096








• A correct version of Apache might not be installed on the SVP of the server. For more information about the correct version, call the Support Center.


When a suspended CLI process is resumed, error (0001 4011) occurs.

The RMI timeout occurred because the CLI processing was stopped. Run the CLI command again.







6

Universal Replicator for Mainframe operations 6–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Universal Replicator for Mainframeoperations

You use the CLI to load spreadsheets for URz.

For more information about installing the CLI and the commands used to process spreadsheets, see Command Line Interface installation and commands on page 2-1.

□ Universal Replicator for Mainframe spreadsheet tasks

□ Prerequisites for using spreadsheets in Universal Replicator for Mainframe

□ Workflow for CLI-based spreadsheets in Universal Replicator for Mainframe

□ CLI-based spreadsheet format in Universal Replicator for Mainframe

□ Creating CLI-based spreadsheets in Universal Replicator for Mainframe

□ Editing CLI-based spreadsheets in Universal Replicator for Mainframe

□ Validating CLI-based spreadsheets in Universal Replicator for Mainframe

□ Correcting validation errors in Universal Replicator for Mainframe

□ Running CLI-based spreadsheets in Universal Replicator for Mainframe

□ Troubleshooting runtime CLI errors in Universal Replicator for Mainframe


6–2 Universal Replicator for Mainframe operations

Universal Replicator for Mainframe spreadsheet tasksYou can use URz spreadsheets to do the following tasks:

• Get pair definitions.

• Create pairs.

• Suspend pairs.

• Resynchronize pairs.

• Release pairs.

Prerequisites for using spreadsheets in Universal Replicator for Mainframe

Before using spreadsheets in URz, ensure you have met the following prerequisites:

• A master journal exists.

• The secondary storage system is registered.

• The remote journal exists.

• CLI and accompanying third-party files are installed.



For more information on installing the CLI files and changing user permissions, see Command Line Interface installation and commands on page 2-1.

The following is a list of the caveats:

• If you specify data volumes other than the URz data volumes or if you specify data volumes for the SuspendPair and ResumePair operation tags, an error can occur. The pair operations defined by other tags in the same spreadsheet cannot run.

When an error occurs, use the Pair operation tag or the GUI Pair Operation window to check the volume status. If a pair operations does not complete because of an error, create the spreadsheet and then process the spreadsheet again.

• If an error occurs when verifying or performing tasks with a spreadsheet, use the error code to determine the necessary operations you must complete. For example, if the pair operation did not work properly, create the spreadsheet again, and try the pair operation again.

Workflow for CLI-based spreadsheets in Universal Replicator for Mainframe

Use the following workflow to work with CLI-based spreadsheets in URz:

1. Make a copy of the spreadsheet template from the tools folder. Save it with a unique name to a working folder or the desktop.


For more information about creating spreadsheets, see Creating CLI-based spreadsheets in Universal Replicator for Mainframe.

For more information on locating the tools folder, see CLI command file locations on page 2-4.

For more information about the spreadsheet format, see CLI-based spreadsheet format in Universal Replicator for Mainframe.

2. Do the following until no errors exist:a. Edit the spreadsheet.

For more information on editing spreadsheets, see Editing CLI-based spreadsheets in Universal Replicator for Mainframe.

b. Validate the spreadsheet.

For more information on validating spreadsheets, see Validating CLI-based spreadsheets in Universal Replicator for Mainframe on page 6-5.

For more information on processing valid spreadsheets, see Troubleshooting runtime CLI errors in Universal Replicator for Mainframe on page 6-15.

3. Process the spreadsheet.

For more information on the commands you can use to process the spreadsheet, see the following:

For more information about adding pairs using the AddPair operation tag, see Adding Universal Replicator for Mainframe pairs.

For more information about suspending pairs using the SuspendPair operation tag, see Suspending Universal Replicator for Mainframe pairs.

For more information about resynchronizing pairs using the ResumePair command, see Resynchronizing Universal Replicator for Mainframe pairs.

For more information about releasing pairs using the DeletePair operation tag, see Releasing Universal Replicator for Mainframe pairs.

CLI-based spreadsheet format in Universal Replicator for Mainframe

The following example shows the basic spreadsheet format:


Operation tag

Parameter


Variables Content





Creating CLI-based spreadsheets in Universal Replicator for Mainframe

Use this procedure to create a spreadsheet to automate an operation. You can add one of the following commands (and operation tags) into a spreadsheet template:

• Get - Retrieves information. The following spreadsheets use the output from the GetPair command:

RemoteCopyJournalMF_ResumePair_def_.spd

RemoteCopyJournalMF_DeletePair_def_.spd

• PairOperation - Expands or releases volumes.

• SerialNumber - Verifies that the serial number in the spreadsheet matches the serial number of the storage system.

The following table shows the command types, the related operation tags available for URz, and the output spreadsheet files.

#! Indicates the declaration line and cannot be changed.

Version number Number that corresponds to the operation tag.

Program product “xxx” for Universal Replicator for Mainframe.

Type Command that retrieves information or performs an operation. One comma and one semicolon with no space between them (,;) is after the type.

Second row


Third row

Parameter LDEV data necessary for running the operation.

Variables Content

Note: You can only use the PairOperation command once per spreadsheet file.

Note: This operation tag is included in all spreadsheet templates.

Command Type Operation Tag Output Spreadsheet File

Get Pair RemoteCopyJournalMF_Get_def_.spd

PairOperation AddPair RemoteCopyJournalMF_AddPair_def_.spd

SuspendPair RemoteCopyJournalMF_SuspendPair_def_.spd

ResumePair RemoteCopyJournalMF_ResumePair_def_.spd

DeletePair RemoteCopyJournalMF_DeletePair_def_.spd


For more information about adding pairs using the AddPair operation tag, see Adding Universal Replicator for Mainframe pairs.

For more information about suspending pairs using the SuspendPair operation tag, see Suspending Universal Replicator for Mainframe pairs.

For more information about resynchronizing pairs using the ResumePair command, see Resynchronizing Universal Replicator for Mainframe pairs.

For more information about releasing pairs using the DeletePair operation tag, see Releasing Universal Replicator for Mainframe pairs.

Editing CLI-based spreadsheets in Universal Replicator for Mainframe



3. Edit your spreadsheet.


Validating CLI-based spreadsheets in Universal Replicator for Mainframe

(For Windows) From a command prompt (Start > Run), execute the following command:


For example:

CFLCHK LUSE_ReleaseOperation.spd LUSE_ReleaseOperation_Result.spd

In this example, the LUSE_ReleaseOperation.spd spreadsheet is checked, and the results are copied to the LUSE_ReleaseOperation_Result.spd spreadsheet.


CFLCHK.sh

Operand Description








Correcting validation errors in Universal Replicator for Mainframe

If you find errors in the spreadsheet results, do the following until no errors exist:


2. Execute the CFLCHK command.

Use the following guidelines to check for errors in the results file:

• Message codes appear at the end of lines that contain errors.



• If a lower layer has an error, the upper layers also show an error—even though no error might exist.

• If a higher layer has an error, parameters in the lower layers are not verified. After correcting the error in the upper layer, run the CFLCHK command to check for errors further down.

Example 1

#!Version

06_01_00,CLI_RemoteCopyJournalMF,PairOperation,;Error(6505-66004)

[SerialNumber]

64040,;Check OK

[Suspend-Pair]

#^,;Check NG(6505-66004)



• In the declaration line (first row). The (xxxx-yyyyy) following “Error” is a code-error code.


Note: If you right-click the command prompt window while the command prompt is not in Quick Edit Mode, the processing stops. To start processing, press the Esc key or left-click the command prompt window.

If you left-click the command prompt window when the command prompt is in Quick Edit Mode, the processing also stops. To start 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, the 0001 4011 error occurs. To resume processing and avoid this error, open a new command prompt window.


• In the Suspend-Pair operation tag, identified in the row below beginning begins with #^. An error occurred in the SuspendPair operation tag.

Example 2

#!Version


[SerialNumber]

64040,;Normal end

[SuspendPair]






• In the declaration line (first row), the warning indicates an invalid condition.


• Errors appear in the first and fourth row in the SuspendPair operation tag.

Example 3

#!Version

06_01_00,CLI_ExternalStorage,VolumeOperationFibre,;Error(1305 66578)

[SerialNumber]

65536,;Normal end

[AddVolumeSetting]

1,1A,60060E8004F81370,0000,E1-1,Normal,00,OPEN-V,Disable,Enable,;Error(605-66797)

+,1B,60060E8004F81371,0001,;Error(605-66695)

+,+,00,00,00,96000,0004,;

The following example shows errors when the parameters are in a hierarchical structure:




• Parameters in the layers lower than the error are not verified. After you correct the visible errors, execute the CFLCHK command again to finish processing the rest of the spreadsheet.

Running CLI-based spreadsheets in Universal Replicator for Mainframe

After you edit and validate the spreadsheet, the spreadsheet has a status of “Ready” and is ready to run. Use the following CLI commands to run spreadsheets:

• CFLSET - to change system settings or perform an operation.

• CFLGET - to retrieve system information to a file.

Making configuration changes in Universal Replicator for Mainframe

Run CFLSET to change the configuration settings you have altered in the spreadsheet, or to do other tasks. The system generates a results file when you run CFLSET, so you can check whether or not the operation completed successfully.




where:

For example:

CFLCHK LUSE_ReleaseOp.spd LUSE_ReleaseOp_Result.spd

3. Check the results file to verify that the operation completed successfully. If the operation did not finish successfully, troubleshoot the error.

For more information, see Troubleshooting runtime CLI errors in Universal Replicator for Mainframe on page 6-15.

Operand Description






CFLCHK.sh


Retrieving storage system information in Universal Replicator for Mainframe

Execute the CFLGET command to retrieve storage system information. When you execute this command, a results file is generated. Use this results file to ensure that the operation completed successfully.



where:

For example:


Retrieving Universal Replicator for Mainframe pair informationUse the RemoteCopyJournalMF_Get_def_.spd spreadsheet template to retrieve pair information. By specifying the LDKC and CU in the Pair operation tag, you can retrieve information about the pairs in a specified range.

To retrieve the pair information, execute the following command:

[PAIR]


Example [Pair] spreadsheet:

#!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,;

Operand Description






CFLCHK.sh



Duplex,00,00,01,00,01,01,00,00,00,22222,5,00,Entire,32,Mirror,Only_P-VOL,;

The following table shows the information that is returned when you use the Pair operation tag.

• One line lists the information for one pair.

• The VSP storage system allows only 65,280 URz pairs.

• The information returned by Get Pair is output to a file named RemoteCopyJournalMF_Pair_00.spd.

• Save the pair information. You can copy some retrieved parameter data and use them when writing SuspendPair, ResumePair, and DeletePair operation tags. You can use this information to add the pair again.


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

M PathGroup Path group ID

N CopyMode Copy mode specified when you add the pair *

O Priority Priority specified when you add or resynchronize the pair

P ErrorLevel Error level specified when you added or resynchronized the pair, or changed the option of that pair

Q CFW CFW specified when you added or resynchronized the pair, or changed the option of the pair. CFW is the setting that specifies whether the Cache-fast-write data is copied to the secondary data volume or not.

*If you add a pair using the AddPair operation tag and you specify None for the Copy Mode parameter, the Pair operation tag outputs Entire for this item. If you perform the delta resync operation after adding a pair, the output copy mode may be different from the copy mode specified when you added the pair.


Adding Universal Replicator for Mainframe pairsUse the RemoteCopyJournalMF_AddPair_def_.spd spreadsheet template to add URz pairs. Add pairs on the primary storage system.

Note: Do not use P-VOLs and S-VOLs volume pairs with other URz pairs.

Column Parameter ContentRange/

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 00000 to 99999

K ControllerID Controller ID of the secondary storage system 4 to 8

L PathGroup Path group ID 00 to FF

M CopyMode Entire: The system runs an initial copy operation.

None: The system does not run an initial copy operation.

Delta: Without executing the initial copy operation, a pair for delta resync operation is added.

N/A

N Priority Priority of the operation 1 to 2561

O ErrorLevel2 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.

N/A

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.

N/A

Notes:

1. Though the smaller the number the higher the priority, when you are add many pairs at a time, specifying the Priority parameter may not be enough to manage the priority of adding pairs operation. To ensure the pairs are added by priority, 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.



Suspending Universal Replicator for Mainframe pairsUse the RemoteCopyJournalMF_SuspendPair_def_.spd spreadsheet template to suspend URz pairs. You can use the output from the Get Pair operation in this spreadsheet. Suspend pairs on the primary or secondary system.

To suspend a pair, execute the following command:

[SuspendPair]


Example [SuspendPair] spreadsheet:

#!Version 06_01_00,CLI_RemoteCopyJournalMF,PairOperation,;

[SuspendPair]

#LDKC,CU,LDEV,MirrorID,VolType,LDKC(Pair),DKCSN,Range,S-VOLWrite,SuspendMode


To suspend the pairs in a mirror (by specifying Mirror as the Range parameter), specify any URz pair in the mirror. This suspends all of the pairs.

Use only URz volumes. If an error happens, use the Pair operation tag or the SN Pair Operation window to check status. If the an error occurs and the operation does not complete, create and then run the spreadsheet again.

Note: You can use a spreadsheet to add a URz pair for delta resync operation.

Best Practice: Use Business Continuity Manager to add a URz pair.

Note: The pair must be in “Pending” or “Duplex” status before you can suspend the pair.


Character numbers




D Mirror ID Mirror ID 00 to 03

E VolType1 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 00000 to 99999

H Range2 Mirror: All pairs in the same mirror are split.

Volume: Only specified pair in the mirror is split

N/A


Resynchronizing Universal Replicator for Mainframe pairsUse the RemoteCopyJournalMF_ResumePair_def_.spd spreadsheet template to resynchronize a URz pair. You can use the output from the GetPair operation in this spreadsheet. To resynchronize pairs, open a command prompt on the primary system and execute the following command:

[ResumePair]


Example [ResumePair] spreadsheet:

#!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, specify a URz pair in the mirror. Specify Mirror for the Range parameter. This splits all pairs.

I S-VOLWrite3 Disable: The host cannot write data in the secondary data volume while the pair is being split.

Enable: The host can write data in the secondary data volume while the pair is being split.

N/A

J SuspendMode4 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.

N/A

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 is in “Pending”, “Duplex”, or “Suspend” status 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. If you specify Purge as the Suspend Mode, specify Mirror as the Range.


Character numbers


Character Numbers





Releasing Universal Replicator for Mainframe pairsUse the RemoteCopyJournalMF_DeletePair_def_.spd spreadsheet template to release a URz pair. You can use the output from the GetPair operation in this spreadsheet. Release pairs on the primary or secondary system.



E M-JNL Master journal ID 00 to 1FF


G DKCSN Serial number of the secondary storage system 00000 to 99999

H ResyncMode1 Normal: The pair in Suspend status is resynchronized.

N/A

I Range2 Mirror: All pairs in the same mirror are resynchronized.

Volume: Only specified pair in the mirror is resynchronized.

N/A

J Priority Priority of the operation 1 to 2563

K ErrorLevel4 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.

N/A

L CFW Specify the current setting (Only_P-VOL or Copy_to_S-VOL).

N/A

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 is in “Pending”, “Duplex”, or “Suspend” status and Mirror is specified for Range, all pairs in the same mirror are resynchronized. If a Suspend pair does not exist 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 adding many pairs at a time, specifying the Priority parameter may not be enough to manage the priority of adding pairs operation. Therefore, to insure the pairs are added by priority, 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.


Character Numbers

Column Parameter Content Range





Troubleshooting runtime CLI errors in Universal Replicator for Mainframe

If a results file indicates that a spreadsheet operation did not happen correctly, one of the following conditions might have occurred:


• Volumes or pairs are not in “Ready” status and are not ready to accept changes.


If you have an error, correct the condition and run the command again. The following table contains other CLI-related troubleshooting information.


E VolType1 P-VOL

S-VOL

N/A


G DKCSN Serial number of the secondary storage system

00000 to 99999

H Range2 Mirror: All pairs in the same mirror are released.

Volume: Only specified pair in the mirror is released

N/A

I DeleteMode3 Disable: The host cannot write data in the secondary data volume while the pair is being split.

Enable: The host can write data in the secondary data volume while the pair is being split.

N/A

J SuspendMode 4

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.

N/A

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 Universal Storage Platform VM (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. If you specify Force as the SuspendMode, specify Mirror as the Range. Even if the spreadsheet ends normally when you specify Volume as the Range and Force as the DeleteMode, the pair is not released. If you specify Force as the SuspendMode for the volumes other than Universal Replicator pairs, an error does not occur. In this case, the pair is not released.

Column Parameter Content Range






• You do not have a correct version of Apache installed on the SVP of the server. For more information about the correct version, call the Support Center.


When a suspended SN CLI process is resumed, error (0001 4011) occurs.

The RMI timeout occurred because the SN CLI processing was stopped. Run the SN CLI command again.







7

Volume Retention Manager operations 7–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Volume Retention Manager operations

Use spreadsheets to configure access to or get current access attributes for LDEV and to set or change access attributes for mainframe system volumes. You use CFL in VRM to process spreadsheets.

□ Prerequisites for using spreadsheets in Volume Retention Manager

□ Volume Retention Manager spreadsheet tasks

□ Example: Using CFL-based spreadsheets in Volume Retention Manager

□ Workflow for CFL-based spreadsheets in Volume Retention Manager


7–2 Volume Retention Manager operations

Prerequisites for using spreadsheets in Volume Retention Manager

VRM must be installed before you can use spreadsheets in VRM. If you do not have VRM installed and you attempt to process a spreadsheet, an error message will not appear and the spreadsheet will not be processed.

Volume Retention Manager spreadsheet tasksYou can do the following tasks using spreadsheets in VRM:

• Save the current LDEV access attributes to a spreadsheet.

• Set or change access attributes for mainframe system volumes.

Example: Using CFL-based spreadsheets in Volume Retention Manager

You, as the system administrator, want to change the LDEV access attributes to Read/write depending on business hours. You create two spreadsheets: Ptn_1 for LDEV1 and Ptn_2 for LDEV2.

Ptn_1 contains the read/write attribute for LDEV1 and the protect attribute for LDEV2. Ptn_2 contains the read only attribute for LDEV1 and the read/write attribute.

If you apply Ptn_1 to the storage system, the hosts can read and write to LDEV1. If you apply Ptn_2 to the storage system, the hosts can do the following:

• Read data from LDEV1

• Read and write data to LDEV2

The following figure shows the scenario:


Workflow for CFL-based spreadsheets in Volume Retention Manager

Use the following workflow for CFL-based spreadsheets in VRM:

1. Export the access attributes to a spreadsheet.

For more information about exporting access attributes, see Exporting access attributes to spreadsheets in Volume Retention Manager on page 7-4.


For more information about editing spreadsheets, see Editing CFL-based spreadsheets in Volume Retention Manager on page 7-4.

3. Import the spreadsheet.



For more information about importing spreadsheets, see Importing and validating spreadsheets in Volume Retention Manager on page 7-8.

4. Apply the changes to the spreadsheet.

For more information about applying changes, see Applying changes to spreadsheets in Volume Retention Manager on page 7-10.

Exporting access attributes to spreadsheets in Volume Retention Manager

Use this procedure to export access attributes from CFL to a spreadsheet. When you export the access attributes, the spreadsheet is created.

The first row has the Version number, followed by Serial Number, function tags and system configuration data. For more details about the variables used in VRM spreadsheet, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.



3. In the Configuration File Loader window, click Select Sheet and then select the product whose access attributes you want to export.

4. Click Export.

5. In the Volume Retention window, enter or browse to a path where you want to export the file in the File Name on Client field. You must follow the file name requirement.

For more information about the file name requirements, see Spreadsheet format requirements on page 1-3.

6. Complete the following fields:

LDKC

CU group

For more information about the fields in this window, see Volume Retention window on page A-4.

7. Click Export. The spreadsheet is exported to the location you specified.

Editing CFL-based spreadsheets in Volume Retention ManagerThe following is a list of best practices when editing definitions:

• Change current settings by entering a different parameter. The format must be the same as the existing setting.

Note: If the spreadsheet imports with errors, correct the errors by editing the spreadsheet then repeat this step.

For more information about correcting errors, see Errors when importing spreadsheets in Volume Retention Manager on page 7-8.

Note: If you use a Web browser for UNIX systems, the Download Manager dialog box can display. If this dialog box displays, close it.


Change definitions by overwriting them in the current definition area. Use the same definition format.

For more information about definitions, see Definitions used in spreadsheet formats in Volume Retention Manager on page 7-8.

• Add new definitions when the current setting is blank and has not yet been specified.

• Delete unused function tags by removing them from the current configuration definition area of the spreadsheet.

For more information about function tags, see Function tags in spreadsheets in Volume Retention Manager on page 7-6.

Use this procedure to edit CFL-based spreadsheets in VRM. You edit the spreadsheet by adding, changing, and deleting the definitions in the current configuration definition area of the spreadsheet.


2. Do the following:

Change the variables to values appropriate for your storage system deployment.

Use the spreadsheet format to edit the configuration settings.

For more information about CFL-based spreadsheet formats, see Function tags in spreadsheets in Volume Retention Manager on page 7-6.

Change the function tags and access attributes.

For [Serial Number], specify the serial number of the storage system.

For [LDKC], specify the LDKC (00) which you want to set access attributes.

For [Attribute], specify the CU, LDEV, and Attribute (access). LDEV range: 1 to 65,280. Write CU and LDEV in one or two hexadecimal digits. Specify the following for Attribute: Read/Write, Read Only, Protect.

For more information about access attributes, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.

For more information about the spreadsheet format and the variables you can use, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.

Note: The function tags that remain in the spreadsheet with existing definitions are deleted from the spreadsheet when you import the spreadsheet.

Note: You can omit the [Serial Number] and [LDKC] function tag parameters, but the [Attribute] function tag parameter is required.

Note: If you do not specify an LDKC, the default value (00) is used.




CFL-based spreadsheet format in Volume Retention Manager

The following example shows the spreadsheet format:

#!Version Version number,program product,;

Function tag

Definitions

For more information about the function tags, see Function tags in spreadsheets in Volume Retention Manager on page 7-6. For more information about the definitions, see Definitions used in spreadsheet formats in Volume Retention Manager on page 7-8.



Function tags in spreadsheets in Volume Retention Manager

Each spreadsheet has its own operations or functions and parameters. The function tags contained within a spreadsheet are classified according to the function. Function tags describe the type of function and the settings.

Function tag definitions are applied to the storage system one at a time in the order they appear in the spreadsheet. Comments and definitions written in the same row as the function tag are ignored.

You must enter at least one function tags in the spreadsheet. Enter function tags beginning with the first column in the row (column A). In the first column, enter the tag without space.

Example: Volume Retention Manager spreadsheet

Variables Description


#! Declaration line. Do not alter this row.

Version Indicates that the RMI version number follows. You cannot change Version. A space follows Version.

Version number RMI version followed by a comma with no space.

Example: 06_05_00

Program product The program product followed by a comma with no space.

Enter VR.

Second row

Function tag [Serial Number], [LDKC], [Attribute]

Indicates the function tags in the above order, enclosed in brackets.

Row following function tag

Definitions System configuration data.


You want to change the attribute in CU=26 LDEV=00 from Read/Write to Protect.

Exported file

#!Version 06_05_00,VR,

[Serial Number]

#Serial Number

64535

[LDKC]

#LDKC

00

[Attribute]

#CU,LDEV, Attribute(Read/Write,Read Only,Protect)

26,00,Read/Write

26,01,Read/Write

26,02,Read/Write

26,03,Read/Write

26,04,Read/Write

26,05,Read/Write

You change the exported file as follows:

File to be imported

#!Version 06_05_00,VR,

[Serial Number]

#Serial Number

64535

[LDKC]

#LDKC

00

[Attribute]

#CU,LDEV, Attribute(Read/Write,Read Only,Protect)

26,00,Protect

26,01,Read/Write

26,02,Read/Write

26,03,Read/Write



26,04,Read/Write

26,05,Read/Write

The row after the function tag is a commented heading row that shows the required values. In the following example, Security Switch after the hash symbol (#) is the heading, separated by a comma.

Definitions used in spreadsheet formats in Volume Retention Manager

Definitions are the parameters you enter when editing the current configuration definition area in spreadsheets. A definition consists of the index and the parameter. The index is fixed for each function tag.

Importing and validating spreadsheets in Volume Retention Manager

Use this procedure to import the spreadsheet back into CFL and validate it.

Importing CFL-based spreadsheets does the following:

• Accepts the spreadsheet.

• Verifies the formats of the function tags.

• Validates the contents.

• Checks the function tags in the current configuration definition area. If errors are not detected, the spreadsheet changes to “Ready” status. If errors are detected, the spreadsheet changes to “Error” status and the error messages are displayed in the Error Information list.

For more information about this list, see Viewing import error messages in Volume Retention Manager on page 7-9.


2. Change to Modify mode by clicking the Modify icon.

3. In the Configuration File Loader window, click Select Sheet and then select the software application whose spreadsheet you want to import.

4. Click Import. The spreadsheet is accepted by CFL. The spreadsheet status changes to “Ready”.

Errors when importing spreadsheets in Volume Retention Manager

You can get errors when importing spreadsheets into CFL. If you get errors, check to make sure the spreadsheet is meeting the following requirements:

• The spreadsheet file meets the spreadsheet format requirements.

For more information about spreadsheet format requirements, see Spreadsheet format requirements on page 1-3.

• The definitions are entered properly:

The spreadsheet contains at least one definition.

The spreadsheet file contains supported definition values.

The parameter ranges are correct.


For more information about definitions in CFL-based spreadsheets, see Definitions used in spreadsheet formats in Volume Retention Manager on page 7-8.

For more information about supported formats in VRM, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.

• The function tags are entered properly:

The spreadsheet contains at least one function tag.

The spreadsheet contains supported function tags.

The function tags contain an valid parameter.

For more information about function tags in CFL-based spreadsheets, see Function tags in spreadsheets in Volume Retention Manager on page 7-6.

• The declaration line has been entered properly.

For more information about the declaration line, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.

• The version number is entered properly.

For more information about the version number, see CFL-based spreadsheet format in Volume Retention Manager on page 7-6.

Viewing import error messages in Volume Retention Manager

You can receive errors when importing spreadsheets which imports the spreadsheet (the spreadsheet is accepted) but changes the spreadsheet status to “Error”. The error code and detailed information about the error is displayed in the Error Information list in CFL. Each line in this list shows the affected row in the spreadsheet, the error code, the column in the spreadsheet, and a description. The spreadsheet status is also displayed in this list.

The values listed in the Select Tag list are the function tags that you have overwritten in the current configuration definition area of the spreadsheet. An asterisk (*) appears after the function tags that have an error.

For more information about the function tags in the current configuration definition area, see Function tags in spreadsheets in Volume Retention Manager on page 7-6.

For more information about the errors that can occur during the import process, see Hitachi Storage Navigator Messages.


2. In the Configuration File Loader window, select the function tag you want to display from the Select Tag list. The error information for that function tag is displayed in the Error Information list.



Applying changes to spreadsheets in Volume Retention ManagerUse this procedure to apply the changes you made to the settings in the spreadsheet to the system. You must import the spreadsheet without errors and the spreadsheet status must be “Ready” before you can apply the changes.

All changes are applied except when one of the following conditions is present:

• The current spreadsheet matches the imported spreadsheet. The spreadsheet is accepted, but since you have made no changes to the spreadsheet, the spreadsheet is not applied to the system.

• All the resource group IDs that are set to the storage system are not assigned to the user account who logs in to SN.

For more information about errors when applying changes to CFL-based spreadsheets, see Errors when importing spreadsheets in Volume Retention Manager on page 7-8.


2. Click Apply.

Errors when applying spreadsheets in Volume Retention Manager

When you use CFL to apply the volume settings and an error occurs, the settings are applied normally. If necessary, you can reset the volume settings where the error is displayed. You can view the status of the spreadsheet in the bottom right of the Error Information list in CFL.

If the volumes where you apply the settings are valid for one of the following conditions, an error message is displayed. Check the following settings or make changes to the configuration as appropriate:

• LDEVs that are not mapped to physical devices and are therefore undefined

• Volume usable by open-systems (except multiplatform volumes)

• Journal volumes

• Compatible FlashCopy V2 volumes

• System Disk volumes

• LDEVs that are configured as command devices

• You have not installed VRM (except when you change an access attribute to Read/Write).

For more information about changing access attributes, see Editing CFL-based spreadsheets in Volume Retention Manager on page 7-4.

• Volumes whose emulation types are 3390-V

• Volumes that are comprised of a pool

• Volumes for Compatible Software for IBM® FlashCopy® SE

• Volumes for Mainframe Fibre Data Migration

A

Configuration File Loader GUI reference A–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Configuration File Loader GUIreference

SN is embedded with CFL. LUNM and VRM use CFL to export system settings and automate certain configuration settings.

□ Configuration File Loader window


A–2 Configuration File Loader GUI reference

Configuration File Loader windowUse the Configuration File Loader window to:

• Export system settings.

For more information about exporting system settings, see the following:

Exporting system settings to spreadsheets in LUN Manager on page 4-2

Exporting access attributes to spreadsheets in Volume Retention Manager on page 7-4

• Import and validate CFL-based spreadsheets.

For more information about importing and validating spreadsheets, see the following:

Importing and validating spreadsheets in LUN Manager on page 4-13

Importing and validating spreadsheets in Volume Retention Manager on page 7-8

• Run CFL-based spreadsheets.

For more information about running spreadsheets, see the following:

Applying changes to CFL-based spreadsheets in LUN Manager on page 4-15

Applying changes to spreadsheets in Volume Retention Manager on page 7-10

The following is an image of the Configuration File Loader window:


Item Description

Select Sheet Select the software application for which you want to import or export a spreadsheet file.

Values:

• LUN Manager

• Volume Retention Manager

Import Imports the spreadsheet from the specified software application.

If you are using a Web browser for UNIX systems, the Download Manager dialog box may open when you click Import. If this happens, close the dialog box and continue importing.

Export Exports the settings from a specific product type.

If using a Web browser for UNIX systems, the Download Manager dialog box may open when you click Export. If this happens, close the dialog box and continue exporting.

Select Tag The function tag that you want to display. This list is available after you have imported a spreadsheet. An asterisk (*) appears after the function tags that have an error.

No. The row number that includes the error.



LUN Manager windowUse the LUN Manager window to export LUNM access attributes to the spreadsheet. You access this window from the Configuration File Loader window.

The following is an image of the LUN Manager window:

Volume Retention windowUse the Volume Retention window to export VRM access attributes to the spreadsheet. You access this window from the Configuration File Loader window.

The following is an image of the Volume Retention window:

Error Code The part code and error number.

Example: 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.

For more information on the error codes and error messages displayed in the list, see Hitachi Storage Navigator Messages.

Status Indicates the spreadsheet status. If you imported the spreadsheet without errors, the status is “Ready” and you can apply the changes you made to the settings. The Apply button is available if the spreadsheet status is “Ready”.

Values: Error or Ready

Apply Applies the changes to the settings in the imported spreadsheet to the system. This button is available if you import the spreadsheet without errors and the spreadsheet status is “Ready”.

Cancel Cancels the settings and returns to the original status of the Configuration File Loader window.

Item Description

Item Description

File Name on Client The specific file that has been previously saved.

Export Exports the settings to a spreadsheet file and closes the LUN Manager window.

Cancel Closes the LUN Manager window without exporting the settings to a spreadsheet file.


Item Description

File Name on Client The specific file that has been previously saved.

LDKC The LDKC which you want to export to a spreadsheet file.

Values: 00

CU Group The CU which you want to export to a spreadsheet file.

Values:

• ALL: Exports the defined LDEVs which belong to all CUs.

• 00-3F: Exports the defined LDEVs which belong to the CUs from 00 to 3F.

• 40-7F: Exports the defined LDEVs which belong to the CUs from 40 to 7F.

• 80-BF: Exports the defined LDEVs which belong to the CUs from 80 to BF.

• C0-FE: Exports the defined LDEVs which belong to the CUs from C0 to FE.

Export Exports the settings to a spreadsheet file and closes the Volume Retention window.

Cancel Closes the Volume Retention window without exporting the settings to a spreadsheet file.



Index–1Hitachi Virtual Storage Platform System Operations Using Spreadsheets

Index

Aauthentication file, creating 2–3

Bbatch files 2–4

CCFLGET, running 3–7, 5–7, 6–9CLI

command files, preparing 2–4workflow 3–2, 5–2, 6–2

command device, changing 4–12

Eerrors, correcting 3–5, 5–5, 6–6external volume group info, retrieving 5–8external volume with one LDEV, mapping 5–14external volume, deleting 5–17external volume, disconnecting 5–16external volume, moving 5–18external volume, restoring 5–16external volumes with multiple LDEVs,

mapping 5–10external volumes, moving 5–17

Ffile name requirements for spreadsheets 1–4

Hhost groups, configuring 4–8host mode option 4–9

JJava security policy, changing 2–3

LLDEVs, retrieving information for 3–8LU paths, configuring 4–11LUN Expansion

creating LUSE volumes 3–9releasing LUSE volumes 3–10retrieving LDEV info 3–8

LUN Managerchanging port settings 4–7changing the command device 4–12configuring host groups 4–8configuring LU paths 4–11configuring WWNs 4–10

LUSE volumes, creating 3–9LUSE volumes, releasing 3–10

Oobtaining a CLI spreadsheet 1–3overview 1–2

Ppair information, retrieving 6–9pairs

creating 6–11releasing 6–14resynchronizing 6–13suspending 6–12

port settings, changing 4–7

RRetrieving pair information 6–9running CLI-based spreadsheet 3–7, 5–7, 6–8

Sspreadsheets

errors, correcting 3–5, 5–5, 6–6obtaining CLI-based 1–3running CLI-based 3–7, 5–7, 6–8validating CLI-based 3–4, 5–4, 6–5

SSID information, retrieving 5–8

Ttermination codes in batch files 2–5


Index–2

UUniversal Replicator for Mainframe

creating pairs 6–11releasing pairs 6–14resynchronizing pairs 6–13retrieving pair information 6–9suspending pairs 6–12

Universal Volume Managerdeleting an external volume 5–17disconnecting an external volume 5–16mapping an external volume with one

LDEV 5–14mapping external volumes with multiple

LDEVs 5–10moving an external volume 5–18moving external volumes 5–17restoring an external volume 5–16retrieving external volume group info 5–8retrieving external volume info 5–9retrieving SSID info 5–8

user authentication 2–3

Vvalidating CLI-based spreadsheet 3–4, 5–4, 6–5

Wworkflow for CLI spreadsheets 3–2, 5–2, 6–2WWNs, configuring 4–10


MK-90RD7026-06

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

Documents

System Operations Using Spreadsheets · Hitachi Virtual Storage Platform System Operations Using Spreadsheets viii Preface Intended audience This document is intended for system administrators,