command control interface command reference · pdf filesyntax ... hitachi command control...

Product Version

Contents

Getting Help

FASTFIND LINKS

Command Control InterfaceCommand Reference

Hitachi Virtual Storage Platform G1000Hitachi Unified Storage VM

Hitachi Virtual Storage PlatformHitachi Universal Storage Platform V/VM

MK-90RD7009-18

Hitachi Command Control Interface Command Reference

ii

© 2010-2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.

All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

https://portal.hds.com

iiiHitachi Command Control Interface Command Reference

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiRelease notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiChanges in this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xixReferenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xixDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiAccessing product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

1 Overview of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Summary of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Data management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Configuration setting commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Subcommands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Command tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Typographic conventions for command format . . . . . . . . . . . . . . . . . . . . . . . . 1-8Differences between CCI and Storage Navigator/Device Manager - Storage Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Supported characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Maximum number of characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Operational differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

2 Data management commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1paircreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9


iv

Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

pairsplit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

pairresync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

pairevtwait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

pairmon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

pairvolchk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

pairdisplay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52

paircurchk (for TrueCopy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

horctakeover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

vHitachi Command Control Interface Command Reference

raidscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

raidar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71

raidqry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72

raidvchkset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77

raidvchkdsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81

raidvchkscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88

raidvchkscan for Universal Replicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93

raidvchkscan for Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97


vi

Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97

horcmstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-100

horcmshutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-102Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-102Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-102

horcctl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-102Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-103Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-103

horctakeoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-104Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-104Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-105Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-106Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-106Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-106

pairsyncwait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-108Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-109Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-110Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-111Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-112Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-112

3 Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Windows subcommands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

findcmddev. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

drivescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

portscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

sync, syncd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

viiHitachi Command Control Interface Command Reference

umount, umountd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Environment variable subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

4 Command tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1inqraid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

mkconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

rmawk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Returned values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

5 Configuration setting commands . . . . . . . . . . . . . . . . . . . . . . . . . 5-1raidcom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Method for specifying LDEV number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Methods for specifying multiple LDEVs. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Operations where multiple LDEVs can be specified . . . . . . . . . . . . . . . . . . 5-6Specifying and displaying the VSP G1000 serial number . . . . . . . . . . . . . . 5-8

Resource group operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Resource lock operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Resource locking and CCI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Ranges of command parameters for storage system types. . . . . . . . . . . . . . . 5-13raidcom get clpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

raidcom modify clpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15


viii

raidcom get command_status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

raidcom reset command_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

raidcom add copy_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

raidcom delete copy_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

raidcom get copy_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

raidcom add device_grp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

raidcom delete device_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

raidcom get device_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

raidcom get error_message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

raidcom add external_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

raidcom check_ext_storage external_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

raidcom delete external_grp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

ixHitachi Command Control Interface Command Reference

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24raidcom disconnect external_grp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

raidcom get external_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

raidcom modify external_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

raidcom discover external_storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

raidcom add host_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

raidcom delete host_grp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

raidcom get host_grp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

raidcom modify host_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

raidcom add hba_wwn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

raidcom delete hba_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

raidcom get hba_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

raidcom reset hba_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36


x

Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

raidcom set hba_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37

raidcom add journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

raidcom delete journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

raidcom get journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40

raidcom modify journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43

raidcom add ldev. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

raidcom delete ldev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50

raidcom extend ldev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51

raidcom get ldev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55

Internal volume examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55External volume examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59Dynamic Provisioning V-VOL example . . . . . . . . . . . . . . . . . . . . . . . . 5-60Dynamic Tiering V-VOL examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61rmawk command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

raidcom initialize ldev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64

xiHitachi Command Control Interface Command Reference

raidcom modify ldev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68

raidcom add lun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70

raidcom delete lun. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

raidcom discover lun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

raidcom get lun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

raidcom add path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75

raidcom get path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75

raidcom check_ext_storage path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77

raidcom delete path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78

raidcom disconnect path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79

raidcom delete pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80

raidcom get pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80


xii

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80raidcom modify pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83

raidcom monitor pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85

raidcom reallocate pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85

raidcom rename pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86

raidcom get port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-86Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87

raidcom modify port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-88Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89

raidcom get parity_grp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90

raidcom add rcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92

raidcom delete rcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93

raidcom get rcu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94

raidcom modify rcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97

raidcom add rcu_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98

xiiiHitachi Command Control Interface Command Reference

Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99

raidcom delete rcu_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100

raidcom add ssid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100

raidcom delete ssid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101

raidcom add resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103

raidcom modify resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103

raidcom delete resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105

raidcom get resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105

raidcom lock resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107

raidcom unlock resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107

raidcom map resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108

raidcom unmap resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109

raidcom add snap_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109


xiv

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-111

raidcom get snap_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112

raidcom add snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-112Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113

raidcom delete snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114

raidcom modify snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-115Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116

raidcom get snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117

raidcom add spm_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119

raidcom delete spm_wwn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120raidcom modify spm_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120Options and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-121raidcom get spm_wwn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-121


Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122raidcom monitor spm_wwn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-123


Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-123raidcom add spm_group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-124


Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-124

xvHitachi Command Control Interface Command Reference

raidcom delete spm_group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125raidcom modify spm_group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125raidcom get spm_group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126


Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126raidcom monitor spm_group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-127


Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-127raidcom add dp_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-128

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-128Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-128Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130

raidcom get dp_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130Options and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-131


xvi

Preface xviiHitachi Command Control Interface Command Reference

Preface

This document describes and provides instructions for using the Hitachi Command Control Interface (CCI) software to configure and perform operations on the Hitachi RAID storage systems.

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

This preface includes the following information:

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments


xviii 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 storage system.

Readers of this document should be familiar with the following:• Data processing and RAID storage systems and their basic functions.• The Hitachi RAID storage system and the manual for the storage system

(for example, Hitachi Virtual Storage Platform G1000 Product Overview, Hitachi Virtual Storage Platform User and Reference Guide).

• The management software for the storage system (for example, Hitachi Command Suite, Hitachi Device Manager - Storage Navigator, Storage Navigator) and the applicable user manuals (for example, Hitachi Command Suite User Guide, Hitachi Virtual Storage Platform G1000 Mainframe System Administrator Guide, Hitachi Storage Navigator User Guide for VSP, HUS VM, USP V/VM.

Product versionHitachi Command Control Interface software version 01-32-03/01 or later.

Release notesThe Release Notes provide information about the microcode (DKCMAIN and SVP), including new features and functions and changes. The Release Notes are available on the Hitachi Data Systems Portal: https://portal.hds.com

Document revision level

Revision Date Description

MK-90RD7009-00 October 2010 Initial release

MK-90RD7009-01 December 2010 Supersedes and replaces MK-90RD7009-00

MK-90RD7009-02 January 2011 Supersedes and replaces MK-90RD7009-01

MK-90RD7009-03 April 2011 Supersedes and replaces MK-90RD7009-02

MK-90RD7009-04 June 2011 Supersedes and replaces MK-90RD7009-03

MK-90RD7009-05 August 2011 Supersedes and replaces MK-90RD7009-04

MK-90RD7009-06 November 2011 Supersedes and replaces MK-90RD7009-05

MK-90RD7009-07 March 2012 Supersedes and replaces MK-90RD7009-06

MK-90RD7009-08 July 2012 Supersedes and replaces MK-90RD7009-07

MK-90RD7009-09 September 2012 Supersedes and replaces MK-90RD7009-08


MK-90RD7009-11 December 2012 Supersedes and replaces MK-90RD7009-10

MK-90RD7009-12 January 2013 Supersedes and replaces MK-90RD7009-11

MK-90RD7009-13 May 2013 Supersedes and replaces MK-90RD7009-12

MK-90RD7009-14 July 2013 Supersedes and replaces MK-90RD7009-13


Preface xixHitachi Command Control Interface Command Reference

Changes in this revision• Added the following raidcom commands:

raidcom map resource

raidcom unmap resource

raidcom modify resource

• Added information and updates for global-active device operations: -jp <id> and -jq <id> options for paircreate -fe option for pairdisplay PHY_Serial#, PHY_LDEV, VIR_LDEV, QRP_Serial#, QRP_ID

for raidcom get ldev -quorum_enable <serial#> <id>, -quorum_id <quorum id>,

-quorum_disable options for raidcom modify ldev -virtual_type <serial#> <id> option for raidcom add resource -key <option> option for raidcom get resource V_Serial#, V_ID, V_IF for raidcom get resource

• Added information about the processing of the raidcom disconnect external_grp command (raidcom disconnect external_grp on page 5-24).

• Added the display of the resource group ID (RS_GID) for LDEVs.• Updated the description of the -logout option of the raidcom command.

Referenced documentsHitachi Command Control Interface documents:• Command Control Interface Installation and Configuration Guide,

MK-90RD7008• Command Control Interface User and Reference Guide, MK-90RD7010

Hitachi Virtual Storage Platform G1000 documents:• Hitachi Virtual Storage Platform G1000 Product Overview,

MK-92RD8051• Hitachi Command Suite User Guide, MK-90HC172• Hitachi Command Suite Messages, MK-90HC178• Hitachi Virtual Storage Platform G1000 Mainframe System Administrator

Guide, MK-92RD8016• Hitachi ShadowImage® User Guide, MK-92RD8021

MK-90RD7009-15 October 2013 Supersedes and replaces MK-90RD7009-14


MK-90RD7009-17 April 2014 Supersedes and replaces MK-90RD7009-16

MK-90RD7009-18 August 2014 Supersedes and replaces MK-90RD7009-17

Revision Date Description


xx Preface

• Hitachi TrueCopy® User Guide, MK-92RD8019• Hitachi Universal Replicator User Guide, MK-92RD8023• Hitachi Virtual Storage Platform G1000 Provisioning Guide for Open

Systems, MK-92RD8014• Hitachi Universal Volume Manager User Guide, MK-92RD8024• Hitachi Thin Image User Guide, MK-92RD8011• Global-Active Device User Guide, MK-92RD8072

Hitachi Unified Storage VM documents:• Hitachi Unified Storage VM Block Module Provisioning Guide,

MK-92HM7012• Hitachi ShadowImage® User Guide, MK-92HM7013• Hitachi Storage Navigator User Guide, MK-92HM7016• Hitachi Storage Navigator Messages, MK-92HM7017• Hitachi TrueCopy® User Guide, MK-92HM7018• Hitachi Universal Replicator User Guide, MK-92HM7019• Hitachi Universal Volume Manager User Guide, MK-92HM7020

Hitachi Virtual Storage Platform documents:• Hitachi Copy-on-Write Snapshot User Guide, MK-90RD7013• Provisioning Guide for Mainframe Systems, MK-90RD7021• Provisioning Guide for Open Systems, MK-90RD7022• Hitachi ShadowImage® for Mainframe User Guide, MK-90RD7023• Hitachi ShadowImage® User Guide, MK-90RD7024• Hitachi Storage Navigator User Guide, MK-90RD7027• Hitachi Storage Navigator Messages, MK-90RD7028• Hitachi TrueCopy® User Guide, MK-90RD7029• Hitachi TrueCopy® for Mainframe User Guide, MK-90RD7030• Hitachi Universal Replicator for Mainframe User Guide, MK-90RD7031• Hitachi Universal Replicator User Guide, MK-90RD7032• Hitachi Universal Volume Manager User Guide, MK-90RD7033

Hitachi Universal Storage Platform V/VM documents:• Hitachi Copy-on-Write Snapshot User Guide, MK-96RD607• LUN Manager User’s Guide, MK-96RD615

• Hitachi ShadowImage for IBM® z/OS® User Guide, MK-96RD619• Hitachi ShadowImage® User Guide, MK-96RD618• Hitachi Storage Navigator User Guide, MK-96RD621• Hitachi Storage Navigator Messages, MK-96RD613• Hitachi TrueCopy® User Guide, MK-96RD622

• Hitachi TrueCopy for IBM® z/OS® User’s Guide, MK-96RD623

Preface xxiHitachi Command Control Interface Command Reference

• Hitachi Universal Replicator for IBM® z/OS® User’s Guide, MK-96RD625• Hitachi Universal Replicator User Guide, MK-96RD624• Hitachi Universal Volume Manager User Guide, MK-96RD626

Document conventionsThis document uses the following terminology conventions:

This document uses the following typographic conventions:

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

Convention Description

Hitachi RAID storage system

Refers to all supported models unless otherwise noted. The Hitachi RAID storage systems include the following models:• Hitachi Virtual Storage Platform G1000• Hitachi Unified Storage VM• Hitachi Virtual Storage Platform• Hitachi Universal Storage Platform V/VM• Hitachi TagmaStore® Universal Storage Platform• Hitachi TagmaStore® Network Storage Controller

Hitachi enterprise storage system

Refers to the Hitachi RAID storage systems except for the Hitachi Unified Storage VM.


Regular text bold In text: keyboard key, parameter name, property name, hardware label, hardware button, hardware switchIn a procedure: user interface item

Italic Variable, emphasis, reference to document title, called-out term

Screen text Command name and option, drive name, file name, folder name, directory name, code, file content, system and application output, user input

< > (angle brackets) Variable (used when italic is not enough to identify variable)

[ ] (square brackets) Optional value

{ } (braces) Required or expected value

| (vertical bar) Choice between two or more options or arguments

Icon Meaning Description

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

Note Provides information that is essential to the completion of a task.

Caution Warns that failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to data).


xxii Preface

Convention for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) are calculated based on the following values:

Logical storage capacity values (for example, logical device capacity) are calculated based on the following values:

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

WARNING Warns the user of severe conditions, consequences, or both (for example, destructive operations).

Icon Meaning Description

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity unit Value

1 block 512 bytes

1 cylinder (cyl) Open-systems:• OPEN-V: 960 KB• Other than OPEN-V: 720 KBMainframe: 870 KB

1 KB 1,024 (210) 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


Preface xxiiiHitachi Command Control Interface Command Reference

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

CommentsPlease send us your comments on this document: [email protected]. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.

Thank you!



xxiv Preface

1

Overview of commands 1–1Hitachi Command Control Interface Command Reference

Overview of commands

This chapter provides an overview of the Command Control Interface (CCI) commands.

□ Summary of commands

□ Typographic conventions for command format

□ Differences between CCI and Storage Navigator/Device Manager - Storage Navigator


1–2 Overview of commands

Summary of commandsCommand Control Interface is command-line interface (CLI) software that enables you to perform operations on Hitachi RAID storage systems. CCI can be used from attached hosts and from Storage Navigator computers.

This document describes and provides the specifications for the CCI commands. There are four types of CCI commands:• Data management commands on page 1-2• Configuration setting commands on page 1-4• Command tools on page 1-8• Subcommands on page 1-7

Data management commandsData management operations include data replication and data protection operations. Table 1-1 Data management commands on page 1-2 lists the CCI data management commands in alphabetical order and provides a brief description of each command.

Table 1-1 Data management commands

Command Description

horcctl Used for both maintenance and troubleshooting on CCI. The horcctl command allows you to change and display the internal trace control parameters (for example, level, type, buffer size) of the HORC Manager/CCI commands. If a new value is not specified to a parameter, the trace control parameter that is specified currently is displayed.HORC Manager (HORCM) is another name for the CCI software.

horcmshutdown Script for stopping HORCM.

horcmstart Script that starts HORCM. This script can also set the environment variables for HORCM as needed (for example, HORCM_CONF, HORCM_LOG, HORCM_LOGS).

horctakeoff Scripted command for executing multiple HORC operation commands combined. It checks the volume attribute (optionally specified) and decides a takeover action. The horctakeoff operation is defined to change from 3DC multi-target to 3DC multi-hop with the state of running APP, after that the horctakeover command can configure 3DC multi-target on the remote site without stopping the application. The granularity of either a logical volume or volume group can be specified with this command.

horctakeover Scripted command for executing multiple TrueCopy takeover operations. It checks the specified volume's or group's attributes (paircurchk), decides the takeover function based on the attributes, executes the chosen takeover function, and returns the result.

paircreate Creates a new volume pair from two unpaired volumes.

paircurchk Checks the current status of the TrueCopy secondary volume(s) by evaluating the data consistency based on pair status and fence level.


pairdisplay Displays the pair status allowing you to verify completion of pair operations (for example, paircreate, pairresync). The pairdisplay command is also used to confirm the configuration of the pair volume connection path (the physical link of paired volumes and servers).

pairevtwait Waits for completion of pair creation and pair resynchronization and confirms the status of pair operations

pairmon Obtains the pair status transition of each volume pair and reports it. If the pair status changes (due to an error or a user-specified command), the pairmon command issues a message.

pairresync Re-establishes a split pair volume and then restarts the update copy operations to the secondary volume. The pairresync command can resynchronize either a paired logical volume or a group of paired volumes.

pairsplit Splits and deletes volume pairs.

pairsyncwait Used to confirm data consistency between the TrueCopy Async/Universal Replicator P-VOL and S-VOL by confirming that required writing was stored in the DFW area of RCU, and confirming whether the last writing just before this command reached the RCU DFW area.

pairvolchk Checks the attributes and status of a pair volume. It acquires and reports the attribute of a volume or group connected to the local host (issuing the command) or remote host. The volume attribute is SMPL (simplex), P VOL (primary volume), or S VOL (secondary volume).

raidar Displays the status and I/O activity information for the specified port/TID(s)/LUN(s) at the specified time interval. The configuration information is acquired directly from the storage system (not from the configuration definition file).

raidqry Displays the configuration of the connected host and RAID storage system.

raidscan Displays the status information for the specified port/TID(s)/LUN(s)/MU#(s). The information is acquired directly from the storage system (not the configuration definition file).

raidvchkdsp Displays the parameters for data validation of the specified volumes. Unit of checking for the validation is based on the group of CCI configuration definition file.

raidvchkscan Displays the fibre port of the storage system, target ID, LDEV mapped for LUN#, and LDEV status, regardless of the configuration definition file.

raidvchkscan (for UR/URz)

Supports the (-v jnl [t] [unit#]) option to find the journal volume list setting. It also displays any information for the journal volume. The Universal Replicator function is available on the USP V/VM and TagmaStore USP/TagmaStore NSC storage systems.

raidvchkscan (for Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning pool)

Supports the option (-v pid[a] [unit#]) to find the Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning pool settings, and displays information for the Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning pool.

Command Description



Configuration setting commandsTable 1-2 Configuration setting commands on page 1-4 lists and describes the CCI configuration setting commands. The configuration setting commands include all commands that begin with "raidcom".

Table 1-2 Configuration setting commands

raidvchkset You can set the parameters for data validation of the specified volumes. You also can set to off all of the validation checking without specifying [type]. Unit of checking for the validation is based on the group of CCI configuration definition file.

Command Description

Command Description

raidcom add host_grp Creates a host group.

raidcom delete host_grp Deletes a host group.

raidcom modify host_grp Sets the host mode.

raidcom get host_grp Displays the host group information.

raidcom add hba_wwn Registers a host to a host group.

raidcom delete hba_wwn Deletes a host (WWN) from a host group.

raidcom get hba_wwn Displays WWN information of a registered host adapter.

raidcom set hba_wwn Sets a nickname to the WWN specified on the specified port.

raidcom reset hba_wwn Deletes a nickname from the WWN specified on the specified port.

raidcom add lun Sets the LU paths.

raidcom delete lun Deletes a LU path on the host group of the specified port.

raidcom get lun Displays LU path information.

raidcom discover lun Searches the external volume information.

raidcom modify port Sets port.

raidcom get port Displays port information.

raidcom get ldev Displays LDEV information.

raidcom extend ldev Extends the virtual volume capacity of Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe V-VOL.

raidcom add ldev Creates LDEV or V-VOL.

raidcom delete ldev Deletes LDEV or V-VOL.

raidcom get parity_grp Displays a parity group information.

raidcom get external_grp Displays the external volume information that is already registered.

raidcom modify ldev Changes the attribute of an LDEV.

raidcom initialize ldev Formats an LDEV.

raidcom discover external_storage Searches the external storage information.

raidcom add external_grp Maps an external volume.

raidcom delete external_grp Unmaps an external volume.


raidcom modify external_grp Changes the attribute of an external volume.

raidcom check_ext_storage external_grp Checks the connection for an external volume and restarts using.

raidcom disconnect external_grp Disconnects the connection for an external volume.

raidcom add path Adds an external path to the existed path group.

raidcom delete path Deletes an external path.

raidcom check_ext_storage path Recovers a path for the external volume.

raidcom disconnect path Stops a path for the external volume.

raidcom get path Displays an external path.

raidcom get rcu Displays RCU information.

raidcom add rcu Registers an RCU.

raidcom delete rcu Deletes an RCU.

raidcom modify rcu Sets an attribute of RCU.

raidcom add rcu_path Add a logical path of RCU.

raidcom delete rcu_path Deletes a logical path between RCUs.

raidcom add ssid Adds an SSID to an RCU.

raidcom delete ssid Deletes an SSID from an RCU.

raidcom add journal Registers a journal volume to a journal.

raidcom delete journal Deletes a journal volume from a journal. and delete the journal.

raidcom modify journal Changes an option of Universal Replicator to be used at a journal.

raidcom get journal Displays a journal group information.

raidcom add snap_pool Creates a pool for Thin Image or Copy-on-Write Snapshot.

raidcom get snap_pool Displays pool information for Thin Image or Copy-on-Write Snapshot.

raidcom add dp_pool Creates a pool for Dynamic Provisioning and Dynamic Provisioning for Mainframe.

raidcom get dp_pool Displays pool information for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe.

raidcom delete pool Deletes a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

raidcom monitor pool Starts or stops the performance monitoring pool for Dynamic Tiering and Dynamic Tiering for Mainframe.

raidcom reallocate pool Starts or stops a relocation of the Dynamic Tiering and Dynamic Tiering for Mainframe pool.

raidcom modify pool Sets an option of a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

raidcom get pool Displays pool information for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

raidcom rename pool Changes the pool name.

Command Description



raidcom add copy_grp Creates a copy group.

raidcom delete copy_grp Deletes a copy group.

raidcom get copy_grp Displays copy group information.

raidcom add device_grp Creates a device group.

raidcom delete device_grp Deletes a device group.

raidcom get device_grp Displays a device group.

raidcom lock resource Locks a resource.

raidcom unlock resource Unlocks a resource.

raidcom add resource Creates a resource group and adds a resource to a resource group.

raidcom modify resource Sets the virtual storage mode of a resource group.

raidcom delete resource Deletes a resource group and deletes a resource from a resource group.

raidcom get resource Displays resource group information.

raidcom map resource Arranges a resource to the virtual storage machine.

raidcom unmap resource Cancels the resource arrangement in the virtual storage machine.

raidcom add snapshot Adds the specified LDEV and Pool to a snapshot group.

raidcom delete snapshot Deletes the snapshot data and the snapshot group.

raidcom modify snapshot Modifies the specified snapshot group.

raidcom get snapshot Displays the information of snapshot group and snapshot data that are defined in the device.

raidcom get command_status Displays an error information of the configuration setting command which is executed asynchronously.

raidcom reset command_status Resets an error information of the configuration setting command which is executed asynchronously.

raidcom get error_message Displays the error message for an error code.

raidcom get clpr Displays the CLPR information.

raidcom modify clpr Modifies a CLPR.

raidcom add spm_wwn Specifies the Server Priority Manager name for preferred/non-preferred WWNs.

raidcom add spm_group Registers Server Priority Manager target WWN to Server Priority Manager group.

raidcom delete spm_wwn Deletes WWN from the Server Priority Manager targets.

raidcom delete spm_group Deletes the Server Priority Manager target WWN from the Server Priority Manager group and releases the specified WWN from the monitoring.

raidcom modify spm_wwn Specifies the Server Priority Manager information to the Server Priority Manager target WWN.

raidcom modify spm_group Specifies the Server Priority Manager information to the Server Priority Manager target group.

raidcom get spm_wwn Gets the Server Priority Manager information of the Server Priority Manager target WWN.

Command Description


SubcommandsCCI provides subcommands that are executed as options of CCI commands. The CCI subcommands include the Windows subcommands and the environment variable subcommands. Table 1-3 Windows subcommands on page 1-7 lists the Windows subcommands in alphabetical order and provides a brief description of each subcommand. Table 1-4 Environment variable subcommands on page 1-7 lists the environment variable subcommands in alphabetical order and provides a brief description of each subcommand.

Table 1-3 Windows subcommands

Table 1-4 Environment variable subcommands

raidcom get spm_group Gets the Server Priority Manager information of the Server Priority Manager target WWN in the specified port by the Server Priority Manager group unit.

raidcom monitor spm_wwn Gets the monitoring information of Server Priority Manager target WWN.

raidcom monitor spm_group Gets the monitoring information of Server Priority Manager target WWN by the Server Priority Manager group unit.

Command Description

Subcommand Description

drivescan Displays the relationship between the disk numbers assigned by the Windows system and the LDEVs on the RAID storage system, and also displays attribute and status information for each LDEV.

findcmddev Searches for command devices within the specified range of disk drive numbers. If it is found, the command device appears in the same format as in the configuration definition file. This subcommand is used when the command device name is not known and when the HORCM is not started.

mount Mounts the specified drive to the specified partition on the specified data drive using the drive letter. When the mount subcommand is executed without an argument, all currently mounted drives (including directory mounted volumes) are displayed, and logical drive has been mounting an LDM volume then displays Harddisk#[n] configured an LDM volume.

portscan Displays the devices on the specified port(s).

sync and syncd The sync (synchronization) Windows subcommand sends unwritten data remaining on the Windows server to the specified device(s) to synchronize the pair(s) before the CCI command is executed. The syncd (sync delay) Windows subcommand waits the delayed IO for dismount after issued 'sync'.


env Displays the environment variables.

setenv Sets the specified environment variables.

sleep Causes CCI to wait for the specified time.



Command toolsTable 1-5 Command tools on page 1-8 lists and describes the CCI command tools.

Table 1-5 Command tools

Typographic conventions for command formatThis document uses the following terminology conventions for command format. Note that if you specify a parameter that is not described in the options and parameters of the command, the parameter will be ignored.

usetenv Deletes the specified environment variables.



inqraid Used to confirm the drive connection between the storage system and host system. The inqraid command displays the relation between special file(s) on the host system and actual physical drive of the RAID storage system.

mkconf Used to make a configuration file from a special file (raw device file) provided via STDIN.

rmawk Scriptable command used to associate pair operation commands and raidcom commands.


Bold Indicates text on a window, other than the window title, including 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-fileNote: Angled brackets (< >) are also used to indicate variables.

screen/code Indicates text that is displayed on 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>

Note: Italic is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.


Differences between CCI and Storage Navigator/Device Manager - Storage Navigator

This section describes the differences between CCI and Storage Navigator/Device Manager - Storage Navigator:• Supported characters on page 1-9• Maximum number of characters on page 1-12

Supported charactersThere are some differences between the supported characters for CCI and the supported characters for Storage Navigator and Device Manager - Storage Navigator. Because of this, you should always use only characters that are supported by both CCI and Storage Navigator/Device Manager - Storage Navigator.

Figure 1-1 Usable characters for CCI commands on page 1-11 shows the characters that can be used in CCI commands and their ASCII codes. Figure 1-2 Usable characters for Storage Navigator/Device Manager - Storage Navigator on page 1-12 shows the characters that can be used in Storage Navigator and Device Manager - Storage Navigator commands and their ASCII codes. For CCI do not use characters that are not supported by the operating system in which the command is executed.

The following characters are not supported by both CCI and Storage Navigator/Device Manager - Storage Navigator. To ensure that names are usable in both CCI and Storage Navigator/Device Manager - Storage Navigator, do not use these characters in names.• ! (exclamation mark)• ' (quotation mark)• # (number sign)

{ } braces When items in braces are set off with vertical bars:• Indicates required or expected values. Example: { a | b }

indicates that you must choose either a or b.When items in braces are enclosed by square brackets:• Indicates one or more items can be specified. Example:

{ [ -A ][ -B ][ -C ]} indicates that you can specify one or more items from A, B, or C.

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

... ellipsis Indicates that the user can type multiple arguments of the same type. The user types only the information, not the ellipsis (…). Example:-ldev_id <ldev#> …Multiple "ldev_id<ldev#>" can be specified.




• $ (dollar sign)• % (percent sign)• & (ampersand)• ' (apostrophe)• ( (left parenthesis)• ) (right parenthesis)• + (plus sign)• · (middle dot)• { (left curly bracket)• } (right curly bracket)• | (vertical line)• ~ (tilde)• : (colon)• = (equals sign)

Caution: Observe the following restrictions for using characters:• The backslash character (\) can be used only on WIN32.• The forward slash character (/) can be used only on UNIX systems.• A hyphen can be used in a name, but it cannot be used at the beginning

of the name. You can neither use some character codes according to the OS on which you execute the command.

• A space (SP) can be used in a name, but if you specify a space for a user name, reference commands will fail, because a space is used as a delimiter and the commands cannot distinguish whether the space is for user name or delimiter.

• A space can be used in between characters. If you use a space at the beginning or end of a name, the space is omitted automatically. Also, you cannot use a name using only a space.Examples of using a space (SP) in a name:"group name"Examples in which you cannot use a space:" name""name "" "


Figure 1-1 Usable characters for CCI commands



Maximum number of charactersThere are some differences between the maximum number of characters for names in CCI commands and the maximum number of characters for names in Storage Navigator and Device Manager - Storage Navigator. Because of this, you should always try to use the number of characters that can be used in both CCI and Storage Navigator/Device Manager - Storage Navigator.

If you enter more than the maximum number of characters for a name in a CCI command, the name is truncated and only the allowable number of characters is used. For example, if the maximum number of characters is 32 and you enter 35 characters, only the first 32 characters are used.

Figure 1-2 Usable characters for Storage Navigator/Device Manager - Storage Navigator


Table 1-6 Maximum number of characters on page 1-13 specifies the maximum number of characters for names in CCI and Storage Navigator/Device Manager - Storage Navigator. To ensure that names are usable in both CCI and Storage Navigator/Device Manager - Storage Navigator, observe the following requirements:• WWN nickname: Do not use more than 32 characters.• User ID: Do not use more than 63 characters.• Password: Do not use more than 63 characters.

Table 1-6 Maximum number of characters

Operational differencesTable 1-7 Operational differences between CCI and Storage Navigator/Device Manager - Storage Navigator on page 1-13 lists the operational differences between CCI and Storage Navigator/Device Manager - Storage Navigator.

Table 1-7 Operational differences between CCI and Storage Navigator/Device Manager - Storage Navigator

Name CCI commandStorage Navigator/Device Manager - Storage Navigator

Host group name 64 characters 64 characters

Device group name 32 characters -

Device name 32 characters -

LDEV nickname 32 characters 32 characters

WWN nickname 64 characters 64 characters

Copy group name 32 characters 32 characters

Pool name 32 characters 32 characters

Resource group name 32 characters 32 characters

User name (User ID) 63 characters 256 characters

User name (Password) 63 characters 256 characters

Operation CCIStorage Navigator/Device Manager - Storage Navigator

Add path or change path for an external volume (UVM)

The path definition is required for each external volume in the path group.

You can specify the path groups on the screen and execute the add/change path at one time.

Operations when a program product is not installed

You can change and delete existing resources for this program product, but you cannot add new resources.

You cannot perform any operations for this program product.

Display of WWN The WWN is displayed only when LUN security is enabled.

The WWN is displayed (in gray) if LUN security is disabled.

Pool ID setting Optional Required



Add LDEV You can specify the LDEV size in GB or LBA. When you specify GB, CCI can perform with or without size correction. If the capacity of LDEVs that are created by each GUI and CLI are the same, a copy pair might not be created. To create a pair with the LDEV that is created by GUI, create an LDEV by specifying LBA.

You can specify the LDEV size in GB or LBA. When you specify GB, CCI performs size correction.

Extending the capacity of Dynamic Provisioning or Dynamic Provisioning for Mainframe volume

You need to specify the capacity to be added to the volume.

You need to specify the total capacity after the volume is extended.

Moving the CLPR assigned to the parity groups of LUSE volumes or the parity groups of the volumes including LUSE volumes

CLPRs can be moved, but it is not recommended.

CLPRs cannot be moved.

Moving the CLPR assigned to the journal volumes

CLPRs cannot be moved. CLPRs can be moved if you specify all LDEVs in the journal.

Deleting SPM name The registration of the SPM name in the specified port is released by deleting the SPM name from WWN.

The SPM name of WWN is deleted, but the SPM registration is maintained.

Deleting SPM group The registration of SPM in the specified port is released by deleting WWN from the group.

WWN is deleted from the group, but the SPM registration is maintained.

Moving the parity groups which configure the distributed parity group between the CLPRs

Parity groups cannot be moved. All parity groups which are concatenated are moved.

Operation CCIStorage Navigator/Device Manager - Storage Navigator

2

Data management commands 2–1Hitachi Command Control Interface Command Reference

Data management commands

This chapter provides the specifications for the CCI data management (replication and protection) commands.

□ paircreate

□ pairsplit

□ pairresync

□ pairevtwait

□ pairmon

□ pairvolchk

□ pairdisplay

□ paircurchk (for TrueCopy)

□ horctakeover

□ raidscan

□ raidar

□ raidqry

□ raidvchkset

□ raidvchkdsp

□ raidvchkscan

□ raidvchkscan for Universal Replicator

□ raidvchkscan for Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning Pool

□ horcmstart

□ horcmshutdown

□ horcctl

□ horctakeoff

□ pairsyncwait


2–2 Data management commands

paircreate

The paircreate command is used to create a new volume pair from two unpaired volumes. The paircreate command can create either a paired logical volume or a group of paired volumes. The paircreate command allows you to specify the direction (local or remote) of the pair generation (see Figure 2-1 Pair Creation on page 2-2). If local (vl option) is specified, the server issuing the paircreate command has the primary volume. If remote (vr option) is specified, the remote server has the primary volume. The -split option of the paircreate command (ShadowImage and Copy-on-Write Snapshot only) allows you to simultaneously create and split pairs using a replication command only. When -split is used, the pair status changes from COPY to PSUS (instead of PAIR) when the initial copy operation is complete.

Before issuing the paircreate command, make sure that the secondary volume is not mounted on any system. If the secondary volume is found to be mounted after paircreate, delete the pair (pairsplit -S), unmount the secondary volume, and then reissue the paircreate command.

The paircreate command terminates before the initial copy operation is complete (except when the nocopy option is specified). Use the pairevtwait or pairdisplay command to verify that the initial copy operation completed successfully (status changes from COPY to PAIR, or from COPY to PSUS if the -split option was specified).

WARNING: Use the paircreate command with caution. The command starts the initial copy operation, which overwrites all data on the secondary (target) volume of the pair. If the primary and secondary volumes are not identified correctly, or if the wrong options are specified (for example, vl instead of vr), data is copied to the wrong volume overwriting and the data in the target of transferring is overwritten.

Figure 2-1 Pair Creation


Syntaxpaircreate { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -g <group>| -d <pair Vol> | -d[g] <raw_device> [MU#] | -FHORC [MU#] or -FCA[MU#] | -d[g] <seq#> <LDEV#> [MU#]| -f[g] <fence> [CTGID] | -v | -c <size> | -nocopy | -nomsg | -split | [-m <mode>]| -jp <id> | -jq <id> | -js <id> | -pid <PID> | -fq <mode>| -cto <o-time> [c-time] [r-time] | -pvol(svol)[ldevgrp]-nocsus }

Options and parameters

Option Description

-h Displays help/usage and version information.

-q Terminates the interactive mode and exits the command.

-z or -zx Makes the paircreate command enter interactive mode. The -zx option guards performing of the HORCM in interactive mode. When this option detects a HORCM shutdown, interactive mode terminates.OpenVMS cannot use the -zx option.

-I[H][M] [instance#] or-I[TC][SI] [instance#]

Specifies the command as [HORC]/[HOMRCF] or [TrueCopy]/[ShadowImage], and used when specifying the CCI instance number.

-g <group> Specifies a group name defined in the configuration definition file. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol>

Specifies paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volume.

-d[g] <raw_device> [MU#]

Searches whether the specified raw_device is included in a group on the configuration definition file (local instance). If it is in the group, the target volume is executed as the paired logical volume (-d) or group (-dg). This option is effective without specification of -g <group> option. If the specified raw_device is contained in two or more groups, the command is executed for the first group.

-d[g] <seq#> <LDEV#> [MU#]

Searches whether the specified LDEV is included in a group on the configuration definition file (local instance). If it is in the group, the target volume is executed as the paired logical volume (-d) or group (-dg). This option is effective without specification of '-g <group>' option. If the specified LDEV is contained in two or more groups, the command is executed on the first group. The <seq#> <LDEV#> values can be specified in hexadecimal (add the '0x' prefix) or decimal notation.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.



-f[g] <fence> [CTGID]

TrueCopy, TrueCopy Async, Universal Replicator, and HAM only.Specifies the fence level for assuring the consistency of paired volume data. A fence level of 'data', 'status', 'never', or 'async' must be specified. This option must always be specified. Fence level '-f async' can be specified only for TrueCopy Async and Universal Replicator. The '-fg' option is used to make TrueCopy Sync CTG volume, and fence level must be specified as '-fg data', '-fg status', or '-fg never'.Specifies the fence level of '-f never' for HAM.A CTGID (CT group ID) is assigned automatically if you do not specify the 'CTGID' option in this command and define it in the config file. If 'CTGID' is not specified (with '-f async' or '-fg' option) and the maximum number of CT groups already exists (for example, 256 (0-255) for TagmaStore USP/TagmaStore NSC), an EX_ENOCTG error is returned. Therefore, the 'CTGID' option can forcibly assign a volume group to an existing CTGID on the RAID storage systems. The CTGID option is ignored unless you specify the '-f async' or '-fg' option.

-vl or -vr-pvol [ldevgrp] or-svol [ldevgrp]

Specifies the data flow direction and must always be specified. The -vl(-pvol) option specifies 'local' and the host which issues the command possesses the primary volume. The -vr(-svol) option specifies 'remote' and the remote host possesses the primary volume while the local host possesses the secondary volume. [ldevgrp] makes the specified LDEV group as the second volume.

-c <size> TrueCopy, TrueCopy Async, and ShadowImage only.Specifies the track size of extents (1 - 15) to be used for the copy operation. If you specify a large number, the time for copy operation is shortened.When you want to copy in a short time by stopping write of P-VOL, specify the maximum value 15. If this option is not specified, the default value (3) is used.In TrueCopy for Mainframe, when you specify the number less than or equal to 3, the copy pace is 3 tracks. When you specify the number more than or equal to 4, the copy pace is 15 tracks. In ShadowImage, when you specify 1 or 2, the copy pace is slow, when you specify 3, the copy pace is medium, and when you specify 4, the copy pace is fast.

-nocopy Creates paired volumes without copying data when the data consistency of simplex volumes is assured by the user.Note: This option cannot be specified for ShadowImage or ShadowImage for Mainframe.

-nomsg Suppresses messages to be displayed when this command is executed. It is used to execute this command from a user program. This option must be specified at the beginning of a command argument. The command execution log is not affected by this option.

-split ShadowImage and Copy-on-Write Snapshot only.Splits the paired volume after the initial copy operation is complete. This option returns after changed the state in PVOL_PSUS & SVOL_COPY immediately, and S-VOL state is changed to 'SVOL_SSUS' after all data is copied.

Option Description


-m <mode> Specifies the mode.mode = noread (ShadowImage only): Specifies the noread mode for hiding the secondary volume. The secondary volume becomes read-disabled when this mode option is specified. The secondary volume is read-enabled when this mode option is omitted. Note: The primary volume becomes read-disabled during a reverse resync operation (restore option of pairresync command).mode = cyl (9900V only): sets bitmap difference management to cylinder for TrueCopy, TrueCopy Async, Universal Replicator.mode = trk (9900V only)): sets bitmap difference management to track for TrueCopy, TrueCopy Async, Universal Replicator. Note: If the mode (cyl or track) is not specified, the default values are used: default is track for OPEN-3 and OPEN-9; default is cylinder for OPEN-E and OPEN-L.Note: For TrueCopy, TrueCopy Async, and Universal Replicator volumes paired between 9900V storage systems, the bitmap tables are managed at the Cylinder level, even if Track is specified.mode=grp [CTGID] (9900V only) (ShadowImage, Copy-on-Write Snapshot, Volume Migration). Makes a group for splitting all ShadowImage pairs specified in a group. Like a TrueCopy Async or Universal Replicator consistency group, ShadowImage guarantees data consistency among multiple LUNs in a group at a single point in time when doing a split using the 'pairsplit -g <group>' command (except '-S' or '-E' option).A CTGID (CT group ID) is assigned automatically if you do not specify the 'CTGID' option in this command. If 'CTGID' is not specified and the maximum number of CT groups already exists, an EX_ENOCTG error is returned. Therefore, the 'CTGID' option can forcibly assign a volume group to an existing CTGID (for example, 0-127 on USP V/VM).For the detail, see Restrictions on specified volumes with '–m grp' option. on page 2-9.Note: This option cannot be specified with '-split' option in the same command. mode = cc (Volume Migration only): Specifies Volume Migration.The -vl option specifies 'local', and copies from the local instance LU (P-VOL) to the remote instance LU (S-VOL). An original volume as the local instance LU is migrated from P-VOL to S-VOL, and the physical volume mapping between P-VOL and S-VOL is swapped after copied.The -vr option specifies 'remote', and copies from the remote instance LU (P-VOL) to the local instance LU (S-VOL). An original volume as the remote instance LU is migrated from P-VOL to S-VOL, and the physical volume mapping between P-VOL and S-VOL is swapped after copied. During maintenance work on the storage system (SVP is in modify mode), this operation cannot be completed.Notes: This option cannot be specified with the '-split' option in the same command.This option ignores the '-c <size>' option.

Option Description



-jp <id> or -jq <id>

UR, HAM, or GAD configuration only only.• For Universal Replicator:

You can use the -jp <id> option when specifying a journal ID for P-VOL.The -jp <id> option is valid when the fence level is set to 'ASYNC', and a journal ID is automatically bound to the CTGID.

• For High Availability Manager or global-active device: You can create a HAM/GAD pair by using either the -jp <id> or -jq <id> option.Specify the quorum ID with -f fence (never) option and quorum ID when creating a HAM pair or a GAD pair. You do not need to check the resource group of the quorum volume.

The following conditions must be met in the case of the HAM configuration.• It is not a CT group.• The fence level is set to 'Never'.• The RCU path is set to 'CU Free'.The following conditions must be met in the case of the GAD configuration.• The fence level is set to 'Never'.• The RCU path is set to 'CU Free'.

-js <id> Universal Replicator only.This option is used when specifying a journal ID for S-VOL.Both the -jp <id> and -js <id> options are valid when the fence level is set to 'ASYNC', and each journal ID is automatically bound to the CTGID.

-pid <PID> Copy-on-Write Snapshot only.The user or application can specify the Pool ID so that they can specify independent ID for Copy-on-Write Snapshot pool different from [CTGID] for splitting at time.LDEVs in a group which was specified by 'PID' belong to the specified Pool for the Copy-on-Write Snapshot.If 'PID' is not specified, then the corresponding LDEVs belong to the default pool ID(0).If the specified pool is for Thin Image, a Thin Image pair is created.If the specified pool is for Copy-on-Write Snapshot, a Copy-on-Write Snapshot pair is created.

Option Description


-fq <mode> ShadowImage only.This option is used when specifying the mode whether '-split' is performed or not as 'QUICK'.mode = normal. The 'paircreate -split' is performed as non-quick mode regardless of setting of $HORCC_SPLT environment variable and/or the system option mode 122 via SVP. mode = quick: The 'paircreate -split' is performed as Quick Split regardless of setting of $HORCC_SPLT environment variable and/or the system option mode 122 via SVP.If this option is not specified, then the performing of the 'Split' depends on $HORCC_SPLT environment variable and/or the system option mode setting through the SVP, whether the paircreate operation is Quick Split or not.The relationship between '-fq' option and $HORCC_SPLT is as shown below:_______________________________________________________ -fq option $HORCC_SPLT Behavior -----------------------------------------------quick Don't care Quick Splitnormal Don't care Normal SplitUnspecified QUICK Quick SplitUnspecified NORMAL Normal SplitUnspecified Depends on system option mode 122_______________________________________________________Note: The -fq option also is validated on TrueCopy-TrueCopy/ShadowImage cascading operation using '-FBC [MU#]' option.

-FHORC [MU#] or -FCA [MU#]

This option is used when creating the cascading configuration with -g <group> and -gs <group> option from the local node (takeover node). -g <group> is used when specifying the cascading P-VOL, and also -gs <group> option is used when specifying the cascading S-VOL. This operation ignores the -vl or vr option, because S-VOL is specified with -gs <group> option. -gs <group>: This 's' option is used when specifying a group name for cascading S-VOL (defined in the configuration definition file). The command is executed for the specified group unless the -ds <pair Vol> option shown below is specified. -ds <pair Vol>: The following options can be specified for cascading S-VOL. -d[g]s <raw_device> [MU#] ... -d[g]s <seq#> <LDEV#> [MU#]Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

Option Description



-cto <o-time> [c-time] [r-time]

TrueCopy Async and Universal Replicator only.These options are valid for only TrueCopy Async/Universal Replicator. If you specify the -cto <o-time> [c-time] [r-time] option on TrueCopy Sync, it is ignored.o-time: This option is used when setting offloading timer for controlling inflow of write I/O to the specified CT group.For TrueCopy Async o-time must be specified within 1 to 255 seconds. If this option is not specified, then 90 seconds is set as default.For Universal Replicator, o-time cannot be specified. If you want to change the value for offloading timer, use the raidcom modify journal command. If you do not change the value by executing the raidcom modify journal command, 60 seconds is set as default.If o-time=0 is specified, the inflow of write I/O becomes invalid.If sidefile quantity is over limit of sidefile area then host side write I/O is waited for enough space of sidefile when storing next new write data until this timeout value (1 second to 255 seconds for TrueCopy Async, 1 second to 600 seconds for Universal Replicator). The default timeout values are 90 seconds for TrueCopy Async and 60 seconds for Universal Replicator. If the timeout happens with this waiting state, then the pair state is changed from PAIR to PSUS state of sidefile (Journal) Full, and its host side write I/O is continued and writing data is managed by BITMAP mode.Therefore o-time timeout value should have less a low value than I/O timeout value of the host system[c-time](TrueCopy Async only): This option is used when setting Copy Pending timer to the specified CT group. c-time must be specified within 1 to 15 minutes. If this option is not specified, then this value is set as below.• If CT group is created, then the default of 5 minutes is set.• If CT group is not created, it is not changed.[r-time] (TrueCopy Async only): This option is used when specifying RCU Ready timer to the specified CT group. r-time can be set from 1 to 10 minutes. If this option is not specified, this value is set as follows:• If CT group is created, then the default of 5 minutes is set.• If CT group is not created, it is not changed.Notes:These options are invalid when pair-volume is added in CT group.The propagation and persistence of these parameters are as follows.For TrueCopy Async, these parameters are also forwarded to the S-VOL side with the paircreate command, and are used when S-VOL is changed to P-VOL. These parameters are maintained until the pair-volumes are changed to SMPL.For Universal Replicator, these parameters are maintained on each journal. Therefore, if you set the value for offloading timer, execute the raidcom modify journal command on both P-VOL and S-VOL side.

-nocsus Universal Replicator only.This option is used to create the suspended journal volumes without copying data in order to make the delta-resync between DC2 (Sync-SVOL) and DC3 (Universal Replicator-SVOL).

Option Description


Returned valuesThe paircreate command sets either of the following returned values in exit (), which allows users to check the execution results using a user program.

Normal termination: 0. When creating groups, 0 = normal termination for all pairs.

Abnormal termination: other than 0. Refer to the error code for error details.

Error codesUnrecoverable errors are fixed and not resolved, even after re-executing the command. If the command fails, the detailed status is logged in the CCI command log ($HORCC_LOG), even if the user script has no error handling.

Restrictions on specified volumes with '–m grp' option.• Vollume group definition

Volume groups specified with -m grp can not define groups across the storage systems.

Category Error Code Error Message Recommended Action Value

Volume status(Unrecoverable)

EX_ENQVOL Unmatched volume status within the group

Confirm status using the pairdisplay command. Make sure all volumes in the group have the same fence level and volume attributes.

236

EX_INCSTG Inconsistent status in group

Confirm pair status using pairdisplay. 229

EX_INVVOL Invalid volume status

Confirm volume status/attribute using pairdisplay (-l option) or 'raidvchkdsp -v aou'."Aou" (allocation on use) refers to dynamic provisioning.

222

EX_INVSTP Invalid pair status

Confirm pair status using pairdisplay. 228

EX_ENQSIZ Unmatched volume size for pairing

Confirm volume size or number of LUSE volume using raidscan -f, and make sure volume sizes are identical.

212

Resource(Unrecoverable)

EX_ENOCTG Not enough CT groups in the RAID

Choose an existing CTGID (pairvolchk displays CTGIDs). Use '-f async <CTGID>' or '-m grp <CTGID>' option of paircreate to force the pair into a pre-existing CTGID.

217

EX_ENXCTG No CT groups left for OPEN Vol use.

Confirm whether all CT groups are already used by TrueCopy/TrueCopy Async or ShadowImage.

215

EX_ENOPOL Not enough Pool in RAID

Could not retain the pool for executing a command due to be exceeded the threshold rate.Delete unnecessary/earlier generations paired volume, or re-synchronize unnecessary/earlier generations split volume.

206



In case of including plural group of CCI within identical CT group (CTGID), the pair of group designation is operated on the entire CT group.

In case that a ShadowImage, Copy-on-Write Snapshot, or Volume Migration volume is cascaded by TrueCopy, TrueCopy Async, or Universal Replicator volume, the data consistency is not guaranteed by the pairsplit command (including pairsplit -FMRCF) of the continuing I/O.

• Registration and limitations of the number of CTGIDWhen a pair creating, the CCI maps and assigns the configuration definition file group to CTGID managed by storage system equiptment. The maximum number of the group that can be resistered to the storage system is 128 (from 0 to 127 for group ID). If resistered over 128, the pair creation is terminated with EX_ENOCTG error.

Examples

Example 1

The following figure shows an example of creating a cascading configuration with -g <group> and -gs <group> option from the local node (takeover node).

Example 2

The following figure shows an example for creating a suspended journal volume.

On DC1 side:

paircreate -g G1 -gs G2 -FHORC 2 -nocsus -f async <ctgid> -jp <id> -js <id>

On DC2 side:

paircreate -g G3 -vl -nocsus -f async <ctgid> -jp <id> -js <id>

Figure 2-2 Creating a cascading configuration from the local node


On DC3 side:

paircreate -g G3 -vr -nocsus -f async <ctgid> -jp <id> -js <id>

Note: The journal ID for the shared Universal Replicator-SVOL must be specified the same journal ID for S-VOL currently. The CTGID for paircreate can be specified the same CT group for S-VOL currently.

Example 3

The following figure shows a takeover example used to suspend a journal volume.

Note: The pairresync command must be issued after TC_Sync volume became SVOL_SSWS or PVOL_COPY/PAIR through the horctakeover command.

Figure 2-3 Example for creating a suspended journal volume



pairsplitThe pairsplit command is used to split volume pairs. This command stops updates to the secondary volume of a pair and can either maintain (status = PSUS) or delete (status = SMPL) the pairing status of the volumes. The pairsplit command can be applied to a paired logical volume or a group of paired volumes. The pairsplit command allows read access or read/write access to the secondary volume, depending on the selected options. When the pairsplit command is specified, acceptance of write requests to the primary volume depends on the fence level of the pair (data, status, never, or async).

Figure 2-4 Takeover example used to suspend a journal volume


The primary volume's server is automatically detected by the pairsplit command, so the server does not need to be specified in the pairsplit command parameters. If the -S option (simplex) is used, the volume pair is deleted, the volumes are returned to the simplex state, and the primary and secondary volume status is lost. Paired volumes are split as soon as the pairsplit command is issued. If you want to synchronize the volumes, the pairsplit command must be issued after write I/Os to the paired volume have completed.

You can create and split ShadowImage pairs simultaneously using the -split option of the paircreate command (see paircreate on page 2-2).

You can delete pairs by using the -S option of the pairsplit command. When the pairsplit -S command is issued, the specified pair is deleted, and each volume is changed to SMPL (simplex) mode. If you want to re-establish a pair that has been deleted, you must use the paircreate command (not pairresync).

Note on Quick Split: If '$HORCC_SPLT=QUICK' environment variable is set, the pairsplit and paircreate -split operations are performed as Quick Split regardless of the system option mode 122 setting on the SVP.

Syntaxpairsplit {-h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -g <group> | -d <pair Vol>| -d[g] <raw_device> [MU#] | -FHORC [MU#] | -FMRCF [MU#]| -d[g] <seq#> <LDEV#> [MU#] | -r | -rw | -S | -R[S][B] | -P | -l| -nomsg | -C <size> | -E | -fq <mode>}

Options and parametersOnly one pairsplit option (-r, -rw, -S, -R, -P, -C, or -E) can be specified. If more than one option is specified, only the last option is executed.

Figure 2-5 Pair Splitting



Option Description


-q Terminates the interactive mode and exits this command.

-z or -zx Makes the pairsplit command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option is specified and a HORCM shutdown is detected, interactive mode terminates.OpenVMS cannot use the -zx option

-I [H] [M] [instance#] or-I [TC] [SI] [instance#]


-g <group> Specifies a group name defined in the configuration definition file. This option must always be specified. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol>

Specifies the paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volumes.





-r or -rw TrueCopy, TrueCopy Async, and Universal Replicator only.Specifies a mode of access to the S-VOL after paired volumes are split. The -r option (default) allows read-only to the S-VOL.The -rw option enables read and write access to the S-VOL.

-S Selects simplex mode (deletes the pair). When the pairing direction is reversed among the hosts (for example, disaster recovery), this mode is established once, and then the paircreate command is issued. When splitting a pair, whether or not you can change the pair status of S-VOL, changing the pair status of P-VOL to SMPL takes priority. Therefore, if the pair status of S-VOL cannot be changed to SMPL, the pair status of P-VOL might not correspond with that of S-VOL. When a path failure has occurred, the pair status of S-VOL cannot be changed to SMPL.


-R [S] [B] TrueCopy, TrueCopy Async, and Universal Replicator only.Brings the secondary volume into the simplex mode forcibly. It is issued by the secondary host, if the host possessing the primary volume is down or has failed.-RS option is used to bring the secondary volume forcibly into SSWS mode.-RB option is used to back the secondary volume forcibly from SSWS into PSUS(PSUE)(SSUS) mode.This allows backing up to the primary volume if you want to back from the secondary host in the SSWS state on Link failure to the primary host.

-P TrueCopy, TrueCopyAsync, and Universal Replicator only.For TrueCopy Sync, this option is used to bring the primary volume forcibly into write disabled mode like PSUE with 'fence=data'. It is issued by the secondary host to disable P-VOL data changes by the host possessing the primary volume.For TrueCopy Async and Universal Replicator, this option is used to suspend and purge the remaining data into SideFile/Journal like link failure (PSUE) without updating S-VOL. This lets you stop journal operations forcibly when the journal utilization traffic becomes high. This is the same for the case of disaster that S-VOL data is not up to date, but it allows to specify '-rw -P' for writing enable. In that situation, if you are using the S-VOL as file system (that is, UFS, NTFS, HANFS), then an FSCK(CHKDSK) is necessary before mounting the volume even after the P-VOL is unmounted.

-l When the remote host cannot be used due to host down, this option enables a pairsplit operation by a local host only. Except the -R option, the target volume of a local host must be P-VOL. (ShadowImage or Copy-on-Write Snapshot volumes are able to split only S-VOL.)

-nomsg Suppresses messages to be displayed when this command is executed. It is used to execute a command from a user program. This option must be specified at the beginning of a command argument. The command execution log is not affected by this option.

-C <size> ShadowImage only.Copies difference data retained in the primary volume into the secondary volume, then enables reading and writing from/to the secondary volume after completion of the copying. (This is the default option.) If not specified, the value used for paircreate or pairresync command is used. In ShadowImage, specify 1 or 2 for slow copy pace, specify 3 for medium copy pace, and specify 4 for fast copy pace.

-E ShadowImage and Copy-on-Write Snapshot only.Suspends a paired volume forcibly when a failure occurs. Not normally used.When this option is specified, the copy pace is set to the default value (3: medium).


Forcibly specifies a cascading remote copy volume for specified volume pair on local copy environment. If the -l option is specified, a cascading remote copy volume is split on a local host (near site). If the -l option is not specified, a cascading remote copy volume is split on a remote host (far site). The target remote copy volume must be a P-VOL, or '-R[S][B]' option can be specified on S-VOL.

Option Description



Returned valuesThe pairsplit command sets the following returned values during exit allowing you to check the execution results.

Normal termination: 0. When splitting groups, 0 = normal termination for all pairs.

Abnormal termination: other than 0, refer to the error codes for error details.

-FMRCF [MU#] or -FBC [MU#]

Forcibly specifies a cascading local copy volume for specified volume pair on remote copy environment. If the -l option is specified, a cascading local copy volume is split on a local host (near site). If -l option is not specified, a cascading local copy volume is split on a remote host (far site). The target local copy volume must be a P-VOL, and the -E option cannot be specified.

-fq <mode>

ShadowImage only.This option is used to specify the mode whether 'pairsplit' is performed or not as 'QUICK'. mode = normal'pairsplit' is performed as Non quick mode regardless of setting of $HORCC_SPLT environment variable and/or the system option mode 122 via SVP. mode = quick'pairsplit' is performed as Quick Split regardless of setting of $HORCC_SPLT environment variable and/or the system option mode 122 via SVP.If this option is not specified, then performing the 'Split' depends on $HORCC_SPLT environment variable and/or the system option mode setting through the SVP whether the pairsplit operation is Quick Split or not.The relationship between '-fq' option and $HORCC_SPLT is as shown below._______________________________________________________ -fq option $HORCC_SPLT Behavior ------------------------------------------------quick Don't care Quick Splitnormal Don't care Normal SplitUnspecified QUICK Quick SplitUnspecified NORMAL Normal SplitUnspecified Unspecified Depends on system option mode 122_______________________________________________________Note:• The -fq option is also validated on TrueCopy-TrueCopy/ShadowImage

cascading operation using '-F BC [MU#]' option.

Option Description


Error codesThe following table lists and describes the error codes for the pairsplit command. Unrecoverable errors are fixed and not resolved, even after re-executing the command. If the command failed, the detailed status is logged in the CCI command log ($HORCC_LOG), even if the user script has no error handling.

Table 2-1 Specific Error Codes for pairsplit

Examples





236


Confirm pair status using pairdisplay.

229


Confirm volume status/attribute using pairdisplay -l or 'raidvchkdsp -v aou'."Aou" (allocation on use) refers to dynamic provisioning.

222

EX_EVOLCE Pair volume combination error

Confirm pair status using pairdisplay, and change combination of volumes.

235



228

EX_EWSUSE Pair suspended at WAIT state

Issue pairresync manually to the identified failed paired volume to try to recover it. If the trouble persists, call the Hitachi Data Systems Support Center.

234

Figure 2-6 Example of -FHORC Option for pairsplit



pairresyncThe pairresync command re-establishes a split pair volume and then restarts the update copy operations to the secondary volume. The pairresync command can resynchronize either a paired logical volume or a group of paired volumes. The normal direction of resynchronization is from the primary volume to the secondary volume. If the --restore option is specified (ShadowImage only), the pair is resynchronized in the reverse direction (that is, secondary volume to primary volume). The primary volume remains accessible during pairresync, except when the -restore option is specified. The secondary volume becomes write-disabled when the pairresync command is issued.

The pairresync command terminates before resynchronization of the secondary (or primary) volume is complete. Use the pair event waiting (pairevtwait) or pairdisplay command to verify that the resync operation completed successfully (status changes from COPY to PAIR). The execution log file also shows completion of the resync operation. The status transition of the paired volume is judged by the status of the primary volume. The fence level is not changed (only for TrueCopy, TrueCopy Async, or Universal Replicator).

If no data was written to the secondary volume while the pair was split, the differential data on the primary volume is copied. If data was written to the secondary volume, the differential data on the primary volume and secondary volume is copied. This process is reversed when the ShadowImage -restore option is specified.

Before issuing the pairresync command (normal or reverse direction), make sure that the secondary volume is not mounted on any UNIX system. Before issuing a reverse pairresync command, make sure that the primary volume is not mounted on any UNIX system.

Note on Quick Resync/Restore: If the '$HORCC_RSYN=QUICK' /'$HORCC_REST=QUICK' environment variable is set, the pairresync operation is performed as Quick Resync regardless of the system option mode 87/80 setting via SVP.

Figure 2-7 Example of -FMRCF Option for pairsplit


TrueCopy, TrueCopy Async, and Universal Replicator only: The swaps(p) option is used to swap volume from the SVOL(PVOL) to PVOL(SVOL) at suspending state on the SVOL(PVOL) side, and resynchronize the NEW_SVOL based on the NEW_PVOL. At the result of this operation, the volume attributes of own host (local host) become the attributes for the NEW_PVOL(SVOL). The paircreate command cannot execute copy rejection for an error condition which made the target volume is accompanied by maintenance work.

The swaps(p) option:

Ignores the -l option.

If -c size option is omitted, use 3 (default value of the number of copy track (-c size)).

Executes at PAIR state as well as PSUS/PSUE state (not applicable to COPY and SMPL).

If the target volume is already the P-VOL (S-VOL), the pair operation is skipped.

Figure 2-8 Pair Resynchronization



Syntaxpairresync { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -g <group> | -d <pair Vol>| -d[g] <raw_device> [MU#] | -FHORC [MU#] | -FMRCF [MU#]| -d[g] <seq#> <LDEV#> [MU#] |-c <size> | -nomsg | -l | -restore| -swaps | -swapp | -fq <mode>| -cto <o-time> [c-time] [r-time]| -f[g] <fence> [CTGID]}

Options and parametersThe primary volume's server is automatically detected by the pairresync command, so the server does not need to be specified in the pairresync command options.

Figure 2-9 Normal Resync and ShadowImage Restore Resync

Note: Read* : Option when the pair was created. If you specified '-m noread', it is not readable.

Option Description



-z or -zx Makes the pairresync command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.




-g <group> Used to specify a group name defined in the configuration definition file. This option must always be specified. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol> Specifies a paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volumes.






Forcibly specifies a cascading remote copy volume for specified pair logical volumes on local copy environment. If the -l option is specified, this option resyncs a cascading remote copy volume on a local host (near site). If no -l option is specified, this option resyncs a cascading remote copy volume on a remote host (far site). The target remote copy volume must be a P-VOL, the -swapp option cannot be specified.


Forcibly specifies a cascading local copy volume for specified volume pair on remote copy environment. If the -l option is specified, a cascading local copy volume is split on a local host (near site). If -l option is not specified, a cascading local copy volume is split on a remote host (far site). The target local copy volume must be a P-VOL, and the -E option cannot be specified.

-swaps -FHORC [MU#]

Swaps the cascading TrueCopy or Universal Replicator volume from the primary node for failback.In failback operation from 3DC Cascade Site Failure, if you want to failback to DC1 from DC3 directly, it is necessary to operate all cascading volume from DC1.In order to make this operation possible, CCI supports the 'pairresync -swaps -FHORC' option that swaps the Universal Replicator volume on the cascading TrueCopy Sync/Universal Replicator volume.

-c <size> TrueCopy, TrueCopy Async, and ShadowImage only.Specifies the copy pace for the resync operation (range = 1 to 15 track extents). If not specified, the value used for paircreate or pairsplit command is used. However, when you use -swaps or -swapp option, unspecified copy pace becomes 3 as the default value.In TrueCopy for Mainframe, when you specify a number less than or equal to 3, the copy pace is 3 tracks. When you specify a number more than or equal to 4, the copy pace is 15 tracks. In ShadowImage, when you specify 1 or 2, the copy pace is slow; when you specify 3, the copy pace is medium; and when you specify 4, the copy pace is fast.

Option Description




-l When this option cannot utilize the remote host for host down, this option enables a pairresync operation by the local host only. The target volume of the local host must be P-VOL. (ShadowImage or Copy-on-Write Snapshot volumes are able to resync only S-VOL.)

-restore ShadowImage and Copy-on-Write Snapshot only.Performs reverse resync (from secondary volume to primary volume).

-swaps TrueCopy, TrueCopy Async, and Universal Replicator only.Executed from the S-VOL side when there is no host on the P-VOL side to help. Typically executed in PSUS state to facilitate 'fast failback' without requiring a full copy. For both -swaps and -swapp, the delta data from the original S-VOL becomes dominant and is copied to the original P-VOL, then the S, P-VOL designations are swapped.

-swapp TrueCopy, TrueCopy Async, and Universal Replicator only.Executes the equivalent of a -swaps from the original P-VOL side. Unlike -swaps, -swapp does require the cooperation of hosts at both sides.

-fq <mode> ShadowImage and Copy-on-Write Snapshot only.Specifies the mode whether 'pairresync' is performed or not as 'QUICK'. mode = normal pairresync is performed as Non quick mode regardless of setting of $HORCC_RSYN environment variable and/or the system option mode 87 via SVP. mode = quick pairresync is performed as Quick Resync regardless of setting of $HORCC_RSYN environment variable and/or the system option mode 87 via SVP.If this option is not specified, then performing pairresync is dependent on $HORCC_RSYN environment variable and/or the system option mode setting through the SVP whether the pairresync operation is Quick Split or not.The relationship between '-fq' option and $HORCC_RSYN is as shown below._____________________________________________________ -fq option $HORCC_RSYN Behavior --------------------------------------------------quick Don't care Quick resyncnormal Don't care Normal resyncUnspecified QUICK Quick resyncUnspecified NORMAL Normal resyncUnspecified Unspecified Dependent on mode 87

Option Description


-fq <mode>(In the case of Restore (-restore is specified))

In the case of Restore (-restore is specified):mode = normalThe pairresync -restore command is performed as Non quick mode regardless of the setting of the $HORCC_REST environment variable and/or the system option mode 80 via SVP.mode = quickThe pairresync -restore command is performed as Quick Restore regardless of the setting of the $HORCC_REST environment variable and/or the system option mode 80 via SVP.If this option is not specified, then the performing of the pairresync has being depended on $HORCC_REST environment variable and/or the system option mode setting through the SVP whether the pairresync operation is Quick Restore or not.The relationship between '-fq' option and $HORCC_REST are shown as below._____________________________________________________ -fq option $HORCC_REST Behavior ----------------------------------------------------quick Don't care Quick restorenormal Don't care Normal restoreUnspecified QUICK Quick restoreUnspecified NORMAL Normal restoreUnspecified Unspecified Dependent on Mode 80

-fq <mode>(Notes)

Notes:• This -fq option also is validated on TrueCopy-TrueCopy/

ShadowImage cascading operation using '-F BC [MU#]' option.• If this option is combined with '-restore' option in VSP, during the

maintenance work in the storage system (SVP is in modify mode), this operation cannot be completed.

Option Description



Changing the option (fence level) and the volume attribute:

-cto <o-time> [c-time] [r-time]

TrueCopy Async and Universal Replicator only.These options are valid for only TrueCopy Async/Universal Replicator, if you specify '-cto <o-time> [c-time] [r-time]' option on TrueCopy sync, then it is ignored.o-time: This option is used when setting offloading timer for controlling inflow of write I/O to the specified CT group. For TrueCopy Async, o-time can be set from 1 to 255 seconds. If this option is not specified, 90 seconds is set as default. For Universal Replicator, o-time cannot be specified. If you want to change the value for offloading timer, use the raidcom modify journal command. If you do not change the value by executing the raidcom modify journal command, 60 seconds is set as default. If o-time=0 is specified, the inflow of write I/O becomes invalid. If sidefile quantity is over limit of sidefile area then host side write I/O is waited for enough space of sidefile when storing next new write data until this timeout value (1 second to 255 seconds for TrueCopy Async, and 1 second to 600 seconds for Universal Replicator). The default timeout values are 90 seconds for TrueCopy Async, and 60 seconds for Universal Replicator. If the timeout happens with this waiting state then pair state is changed from PAIR to PSUS state of sidefile(Journal) Full, and its host side Write I/O is continued and Writing data is managed by BITMAP mode. Therefore the o-time timeout value should be less than the I/O timeout value of the host system.[c-time]: (Applicable for only TrueCopy Async) This option is used when setting Copy Pending timer to the specified CT group. c-time can be specified from 1 to 15 minutes in increments of 1 minute. If this option is not specified, then this value is set as below.• If CT group is created, then 5 minutes is set as the default. If not,

it is not changed.[r-time]: (Applicable for only TrueCopy Async) This option is used when specifying RCU Ready timer to the specified CT group. r-time can be specified from 1 to 10 minutes in increments of 1 minute. If this option is not specified, then it is not changed.Note:• These options can also be set if all volumes of CT group are

suspended.• The propagation and persistence of these parameters are as

follows.For TrueCopy Async, these parameters are also forwarded to S-VOL side with pairresync command, and are used when S-VOL is changed to P-VOL. These parameters are maintained until the pair-volumes are changed to SMPL.For Universal Replicator, these parameters are maintained on each journal. Therefore, if you set the value for offloading timer, execute the raidcom modify journal command on both P-VOL and S-VOL side.

-f[g] <fence> [CTGID]

TrueCopy, TrueCopyAsync, and Universal Replicator only. -f[g] <fence> [CTGID] (TrueCopy only): This option is used to change from existing TrueCopy Sync volumes to TrueCopy Sync CTG without deleting paired-volume. It is possible to change the option (fence level) and the volume attribute as shown below. This option is valid without '-swaps' or '-swapp' option.

Option Description


Returned valuesThe pairresync command sets the following returned values during exit allowing you to check the execution results.

Normal termination: 0. When resynchronizing groups, 0 = normal termination for all pairs.


Error codesUnrecoverable errors are fixed and not resolved, even after re-executing the command. If the command failed, the detailed status is logged in the CCI command log ($HORCC_LOG), even if the user script has no error handling.

The primary and secondary volumes must not be mounted, because the pairresync command renews data on both the primary and secondary volumes. This command cannot be executed because it is rejected when the target volume is in a failure accompanying maintenance work (for example, one side cache failure) (TrueCopy, TrueCopy Async, and Universal Replicator only).

AttributeOptions

-f fence -fg fence -fg fence CTGID

Sync Updates fence Cmd rejectedAbnormal term.

Changes to Sync CTG Updates fence*

Sync CTG Changes to Sync Updates fence

Updates fence Cmd rejectedAbnormal term.

Async Cmd rejectedAbnormal term.

Cmd rejectedAbnormal term.

Cmd rejectedAbnormal term.

Explanation of terms:fence: data, status, or never ('async' cannot be specified)Cmd rejected/Abnormal term.: Command execution is rejected, and the operation terminates abnormally.

*If the identical CTGID is specified with the different group name of CCI, then the command is rejected. So different CTGID must be specified for the different group name.



Table 2-2 Specific Error Codes for pairresync

Examples





236



229


Confirm pair status using pairdisplay -l.

222



228

Figure 2-10 Example of -FHORC Option for pairresync

Figure 2-11 Example of -FMRCF Option for pairresync


Figure 2-12 Swap Operation

Figure 2-13 Example of -swaps option with -FHORC [MU#]



pairevtwaitThe pairevtwait (pair event waiting) command is used to wait for completion of pair creation and to confirm the status of pair operations. It waits ('sleeps') until the paired volume status becomes identical to a specified status and then completes. The pairevtwait command can be used for a paired logical volume or a group of paired volumes. The primary volume's server is automatically detected by the pairevtwait command, so the server does not need to be specified in the pairevtwait command parameters.

The pairevtwait command waits until the specified status is established, and terminates abnormally if an abnormal status is detected. The transition of the paired volume status is judged by the status of the primary volume. If the pairevtwait command is issued for a group, the command waits until the status of each volume in the group changes to the specified status. When the pairevtwait command with the -nowait option is issued for a group, the status is returned if the status of each volume in the group is identical. For ShadowImage pairs, this command must be used to confirm a pair status transition.

Syntaxpairevtwait{ -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -FHORC [MU#] | -FMRCF [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -s [s] <status> ... | -t <timeout>[intervall] | -nowait[s] | -l | -nomsg }


Figure 2-14 Pair Event Waiting

Option Description




-z or -zx Makes the pairevtwait command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.

-I[H][M] [instance#]or-I[TC][SI] [instance#]


-g <group> Specifies a group name defined in the configuration definition file. This option must always be specified. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol> Specifies a paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volumes.




Forcibly specifies a cascading remote copy volume for specified pair logical volumes on local copy environment. If the -l option is specified, this option tests status of a cascading remote copy volume on a local host (near site). If no -l option is specified, this option tests status of a cascading remote copy volume on a remote host (far site). The target remote copy volume must be P-VOL or SMPL.


Forcibly specifies a cascading local copy volume for specified pair logical volumes on remote copy environment. If the -l option is specified, this option tests status of a cascading local copy volume on a local host (near site). If no -l option is specified, this option tests status of a cascading local copy volume on a remote host (far site). The target local copy volume must be a P-VOL or SMPL.



-s <status> Specifies the waiting status, which is 'smpl', 'copy(including 'RCPY')', 'pair', 'psus', or 'psue'. If two or more statuses are specified following -s, waiting is done according to the logical OR of the specified statuses. This option is valid when the -nowait option is not specified.

-ss <status> Specifies the waiting status, which is 'smpl', 'copy'('RCPY' is included), 'pair', 'ssus','psue' on S-VOL. If two or more statuses are specified following -ss, waiting is done according to the logical OR of the specified statuses. This option is valid when the -nowait option is not specified.

Option Description



Returned valuesThe pairevtwait command sets the following returned values during exit allowing you to check the execution results.

Table 2-3 Returned values for pairevtwait

-t <timeout> [interval]

Specifies the interval of monitoring a status specified using the -s and -ss option and the time-out period in increments of 1 second. Unless [interval] is specified, the default value (3 seconds) is used. This option is valid when the -nowait option is not specified. If <timeout> is specified more than 1999999, then 'WARNING' message appears.If you execute the command in the Out-of-Band method, specify 3 seconds (default value) or more to <timeout>.

-nowait When this option is specified, the pair status at that time is reported without waiting. The pair status is set as a returned value for this command. When this option is specified, the -t and -s options are not needed.

-nowaits When this option is specified, the pairing status on S-VOL at that time is reported without waiting. The pairing status is set as a returned value for this command. When this option is specified, the -t and -ss options are not needed.

-l When this command cannot utilize a remote host for host down, this option executes this command by a local host only. The target volume of a local host must be SMPL or P-VOL. (ShadowImage and Copy-on-Write Snapshot volumes are able to specify from S-VOL.)


Option Description

Condition Value

When the -nowait option is specified:

Normal termination:1:The status is SMPL.2:The status is COPY or RCPY.3:The status is PAIR.4:The status is PSUS.5:The status is PSUE.When monitoring groups, 1/2/3/4/5 = normal termination for all pairs.Abnormal termination: other than 0 to 127, refer to the error codes for error details.



Table 2-4 Specific Error Codes for pairevtwait

When the -nowaits option is specified:

Normal termination:1:The status is SMPL.2:The status is COPY or RCPY.3:The status is PAIR.4:The status is SSUS (Note that SVOL_PSUS appears as SSUS).5:The status is PSUE.Abnormal termination: other than 0 to 127, refer to the error codes for error details.

When the -nowait and/or nowaits option is not specified:

Normal termination: 0. When monitoring groups, 0 = normal termination for all pairs.Abnormal termination: other than 0 to 127, refer to the error code for error details.

Condition Value





236



229



222



235

EX_EWSUSE Pair suspended at WAIT state

Issue pairresync manually to the identified failed paired volume to try to recover it. If the trouble persists, call the Hitachi Data Systems Support Center

234



Examples

Timer(Recoverable)

EX_EWSTOT Timeout waiting for specified status

Increase timeout value using the -t option.

233

EX_EWSLTO Timeout waiting for specified status on the local host

Confirm that CCI (HORCM) on the remote host is running.

232

Figure 2-15 Example of -FHORC option for pairevtwait



Using the -ss <status> ... and -nowaits options. In PVOL_PSUS & SVOL_COPY state of ShadowImage quick mode, pairevtwait returns immediately even if the S-VOL is still in SVOL_COPY state because P-VOL is already in PVOL_PSUS state. If you want to wait the SVOL_SSUS state, then use the -ss <status> and -nowaits options to wait for the pair status on S-VOL side. This is needed for operating pairresync -restore or pairsplit -S.

The figure below shows five examples of waiting until 'PVOL_PSUS' & 'SVOL_COPY' state is changed to SVOL_SSUS.

The horctakeover command suspends G2(CA-Jnl) automatically if horctakeover returns 'Swap-takeover' as an exit code. In DC1 host failure, if APP1 wants to wait until DC3 becomes the suspend state, then they can verify the 'SSUS' state by using the pairevtwait command as shown below.

Figure 2-16 Example of -FMRCF option for pairevtwait

Figure 2-17 Example for waiting on ShadowImage



pairmonThe pairmon (pair monitor) command, which is connected to the HORCM daemon, obtains the pair status transition of each volume pair and reports the status change. If the pair status changes (due to an error or a user-specified command), the pairmon command displays a message.

The pair status transition events exist in the HORCM pair state transfer queue. The -resevt option (reset event) deletes one/all events from the HORCM pair state transfer queue. If reset event is not specified, the pair state transfer queue is maintained. If the -s option is not specified, pairmon displays all events for which it receives information from HORCM. If the -s option is specified, only the specified status transitions are displayed.

The CCI software supports the error monitoring and configuration confirmation commands for linkage with the system operation management of the UNIX server.

Syntaxpairmon { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -D | -allsnd | -resevt | -nowait | -s <status> ... }


Figure 2-18 Example for waiting 'SSUS' on 3DC using TC/UR

Option Description




ExamplesThe following shows an example of the pairmon command and its output.

# pairmon -allsnd -nowaitGroup Pair vol Port targ#lun#LDEV#…Oldstat code -> Newstat codeoradb oradb1 CL1-A 1 5 145…SMPL 0x00 -> COPY 0x01oradb oradb2 CL1-A 1 6 146…PAIR 0x02 -> PSUS 0x04

Output of the pairmon command:

Group: The group name (dev_group) described in the configuration definition file.

Pair vol: The paired volume name (dev_name) in the specified group that is described in the configuration definition file.

Port targ# lun#: The port ID, TID, and LUN which is described in the configuration definition file. For further information on fibre-to-SCSI address conversion, see the Command Control Interface Installation and Configuration Guide.

LDEV#: The LDEV ID for the specified device.

Oldstat: The old pair status when the status of the volume is changed.

Newstat: The new pair status when the status of the volume is changed.

-z or -zx Makes the pairmon command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-D Selects the default report mode. In the default mode, if there is pair status transition information to be reported, one event is reported and the event is reset. If there is no pair status transition information to be reported, the command waits. The report mode consists of the three flags: -allsnd, - resevt, and -nowait options.

-allsnd Reports all events if there is pair status transition information.

-resevt Reports events if there is pair status transition information, and then resets all events.

-nowait When this option is specified, the command does not wait when there is no pair status transition information.

-s <status>...

Specifies the pair status transition to be reported: smpl, copy (includes rcpy), pair, psus, psue. If two or more statuses are specified following -s, masking is done according to the logical OR of the specified statuses. If this option is not specified, pairmon displays all events which received information from HORCM.

Option Description



code: The storage system-internal code for the specified status.

The following table specifies the results of the pairmon command options.

Table 2-5 Results of pairmon command options

pairvolchkThe pairvolchk command checks the attributes and status of a pair volume. It acquires and reports the attribute of a volume or group connected to the local host (issuing the command) or remote host. The volume attribute is SMPL (simplex), P-VOL (primary volume), or S-VOL (secondary volume). The -s[s] option reports the pair status in addition to the attribute.

Syntaxpairvolchk { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -FHORC [MU#] | -FMRCF [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -c | -ss |-nomsg }

-D -nowait

-resevt

-allsnd Actions

-D - - - When HORCM does not have an event, this option waits until an event occurs. If one or more events exist, then it reports one event and resets the event which it reported.

Invalid - - -allsnd When HORCM does not have an event, this option waits until an event occurs. If one or more events exist, then it reports all events.

Invalid - -resevt - When HORCM does not have an event, this option waits until an event occurs. If one or more events exist, then it reports one event and resets all events.

Invalid - -resevt -allsnd When HORCM does not have an event, this option waits until an event occurs. If one or more events exist, then it reports all events and resets all events.

Invalid -nowait - - When HORCM does not have an event, this option reports event nothing. If one or more events exist, then it reports one event and resets the event which it reported.

Invalid -nowait - -allsnd When HORCM does not have an event, this option reports event nothing. If one or more events exist, then it reports all events.

Invalid -nowait -resevt - When HORCM does not have an event, this option reports event nothing. If one or more events exist, then it reports one event and resets all events.

Invalid -nowait -resevt -allsnd When HORCM does not have an event, this option reports event nothing. If one or more events exist, then it reports all events and resets all events.



Option Description


-q Terminates the interactive mode and exits the pair volume check command.

-z or -zx Makes the pairvolchk command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option



-g <group> Specifies the group name defined in the configuration definition file. This option must always be specified. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol> Specifies the paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volumes.





-c Checks the conformability of the paired volumes of the local and remote hosts and reports the volume attribute of the remote host. If this option is not specified, the volume attribute of the local host is reported.

-ss Used when acquiring the attribute of a volume and the pair status of a volume. If this option is not specified, the volume attribute of the local host is reported.




Returned valuesThe pairvolchk command sets the following returned values during exit allowing you to check the execution results.

Table 2-6 pairvolchk returned values


Forcibly specifies a cascading remote copy volume for specified pair logical volumes on local copy environment. If no -c option is specified, this option acquires the attributes of a cascading remote copy volume on a local host (near site). If the -c option is specified, this option acquires the attributes of a cascading remote copy volume on a remote host (far site).

-FMRCF [MU#] or -FBC [MU#]:

Forcibly specifies a cascading local copy volume for specified pair logical volumes on remote copy environment. If no -c option is specified, acquires the attributes of a cascading local copy volume on a local host (near site). If the -c option is specified, acquires the attributes of a cascading local copy volume on a remote host (far site).

Option Description

Condition Value

When the -ss option is not specified

Normal termination:1: The volume attribute is SMPL.2: The volume attribute is P-VOL.3: The volume attribute is S-VOL.Abnormal termination: Other than 0 to 127, refer to the error codes for error details.

When the -ss option is specified

Normal termination:11: The status is SMPL.Abnormal termination: specific error codes (see Error Codes) and generic error codes.

For TrueCopy, ShadowImage, Copy-on-Write Snapshot, Volume Migration

22: The status is PVOL_COPY or PVOL_RCPY.23: The status is PVOL_PAIR.24: The status is PVOL_PSUS.25: The status is PVOL_PSUE.26: The status is PVOL_PDUB (TrueCopy & LUSE volume only).32: The status is SVOL_COPY or SVOL_RCPY.33: The status is SVOL_PAIR.34: The status is SVOL_PSUS.35: The status is SVOL_PSUE.36: The status is SVOL_PDUB (TrueCopy & LUSE volume only).To identify TrueCopy Async and Universal Replicator, the pairvolchk command returns a value which is 20 more than the TrueCopy status code and adds PFUL and PFUS states to return code to identify sidefile status of TrueCopy Async or Universal Replicator journal file.


For TrueCopy Async and Universal Replicator

42: The status is PVOL_COPY. 43: The status is PVOL_PAIR. 44: The status is PVOL_PSUS. 45: The status is PVOL_PSUE. 46: The status is PVOL_PDUB. (TrueCopy & LUSE volume only)47: The status is PVOL_PFUL.48: The status is PVOL_PFUS.52: The status is SVOL_COPY or SVOL_RCPY. 53: The status is SVOL_PAIR. 54: The status is SVOL_PSUS. 55: The status is SVOL_PSUE. 56: The status is SVOL_PDUB. (TrueCopy & LUSE volume only)57: The status is SVOL_PFUL.58: The status is SVOL_PFUS.

For Copy-on-Write Snapshot

Copy-on-Write Snapshot needs to show the status of Full of the Copy-on-Write Snapshot Pool as Copy-on-Write Snapshot condition. For this purpose, Copy-on-Write Snapshot also uses PFUL and PFUS status which is the status of Full of the sidefile for TrueCopy Async. The APP can refer this status as the return value.22: The status is PVOL_COPY or PVOL_RCPY. 23: The status is PVOL_PAIR. 24: The status is PVOL_PSUS. 25: The status is PVOL_PSUE. 26: The status is PVOL_PDUB. (TrueCopy && LUSE volumes only)27: The status is PVOL_PFUL. (PAIR closing Full status of the Copy-on-Write Snapshot Pool)28: The status is PVOL_PFUS. (PSUS closing Full status of the Copy-on-Write Snapshot Pool)32: The status is SVOL_COPY or SVOL_RCPY. 33: The status is SVOL_PAIR. 34: The status is SVOL_PSUS. 35: The status is SVOL_PSUE. 36: The status is SVOL_PDUB. (TrueCopy && LUSE volumes only)37: The status is SVOL_PFUL. (PAIR closing Full status of the Copy-on-Write Snapshot Pool)38: The status is SVOL_PFUS. (PSUS closing Full status of the Copy-on-Write Snapshot Pool)You can set the threshold for the specified pool via Storage Navigator and Device Manager - Storage Navigator. The default value is 80% of pool capacity. PFUS is set when the Copy-on-Write Snapshot pool became over threshold in the PSUS state. PFUL is set when the Copy-on-Write Snapshot pool became over threshold in the PAIR state.

Condition Value



Error codes

Examples

Example 1

Display example for ShadowImage/Copy-on-Write Snapshot:

# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR ]

Display example for ShadowImage (specified with '-m grp' option):

# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR, CTGID = 1 ]

Display example for TrueCopy:

# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR, fence = DATA, MINAP = 2 ]

Display example for TrueCopy Sync CTG:

# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR, fence = DATA, CTGID = 2 MINAP = 2 ]

Display example for TrueCopy Async:

# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2 MINAP = 2 ]

MINAP displays the following two conditions (status) according to the pair status:

PVOL: This shows the minimum in Active Paths on specified group in TrueCopy/TrueCopy Async.

Category Error code Error message Recommended action Value




236


Confirm pair status using the pairdisplay command, and change combination of volumes.

235


SVOL_ SSUS(SSWS): MINAP shows the result of the suspend operation that indicates whether the remaining data on P-VOL was completely passed (synchronized) to S-VOL. If MINAP is 'one', all data is passed. Otherwise, all data is not passed from P-VOL.

Note: If the microcode on the storage system does not support the active paths, then the 'MINAP' item is not displayed as follows:

pairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2]

Example 2

Display example for Universal Replicator:

# pairvolchk -g oradbpairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2 MINAP = 2 ]

MINAP displays the following two conditions (status) according to the pair status:

PVOL or SVOL_PAIR (except SSUS(SSWS)): this shows the minimum in Active Paths on specified group in Universal Replicator.

SVOL_ SSUS(SSWS): MINAP shows the result of the suspend operation that indicates whether or not the remaining All data on P-VOL were Passed (synchronized) to S-VOL completely. If MINAP is 'one', All data were passed. If not, all data were not passed from P-VOL.

Note: If the microcode on the storage system does not support the active paths, then the 'MINAP' item is not displayed as follows:

pairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2]

Example 3

Display example for LDEV blockading:



# pairvolchk -g oradb pairvolchk : Volstat is P-VOL.[status = PAIR fence = DATA MINAP = 2 LDEV = BLOCKED]

LDEV = BLOCKED: Displays the status of LDEV blockading in order to detect a link failure of E-LUN.

Example 4

The following shows examples of the pairvolchk command and its output.

TrueCopy Async:

# pairvolchk -g oradbpairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2]

TrueCopy:

# pairvolchk -g oradbpairvolchk : Volstat is P-VOL.[status = PAIR fence = DATA ]

ShadowImage:

pairvolchk -g oradbpairvolchk : Volstat is P-VOL.[status = PAIR ]

ShadowImage pair splitting with specifying the consistency group:

# pairvolchk -g oradbpairvolchk : Volstat is P-VOL.[status = PAIR CTGID = 1]

Example 5

The following shows a pairvolchk example that acquires the status (PVOL_PSUS) of the intermediate P/Pvol through specified pair group on ShadowImage environment. The following figure shows a pairvolchk example that acquires the status (PVOL_PSUS) of the intermediate S/Pvol (MU#1) through specified pair group on TrueCopy environment.


The following table shows the pairvolchk group status.

Table 2-7 Pairvolchk group status

Figure 2-19 Example of -FHORC option for pairvolchk

Figure 2-20 Example of -FMRCF option for pairvolchk

Option COPY/RCPY PSUE PDUB PFUS PSUS PFUL PAIR Group

status

Status of each volume in the group -



Note: This option can be used only when 'pairvolchk -s' has the variable, USE_OLD_VCHK.

The PFUL state appears as PAIR by all commands (except the -fc option of the pairdisplay command), since PFUL indicates PAIR state with sidefile at the HWM.

The PFUS state appears as PSUS by all commands (except the -fc option of the pairdisplay command), since PFUS indicates SUSPENDED state due to sidefile full.

The SVOL_PSUS state appears as SSUS by the pairdisplay command and other commands.

pairdisplayThe pairdisplay command displays the pair status allowing you to verify completion of pair operations (for example, paircreate, pairresync). The pairdisplay command is also used to confirm the configuration of the pair

See Note under this table

exist ignore ignore ignore ignore ignore ignore COPY/RCPY

not-exist exist ignore ignore ignore ignore ignore PSUE

not-exist not-exist

exist ignore ignore ignore ignore PDUB

not-exist not-exist

not-exist

exist ignore ignore ignore PFUS

not-exist not-exist

not-exist

not-exist

exist ignore ignore PSUS

not-exist not-exist

not-exist

not-exist

not-exist

exist ignore PFUL

not-exist not-exist

not-exist

not-exist

not-exist

not-exist

exist PAIR

-ss exist ignore ignore ignore ignore ignore ignore COPY/RCPY

not-exist exist ignore ignore ignore ignore ignore PSUE

not-exist not-exist

exist ignore ignore ignore ignore PDUB

not-exist not-exist

not-exist

ignore ignore exist ignore PFUL

not-exist not-exist

not-exist

ignore ignore not-exist

exist PAIR

not-exist not-exist

not-exist

exist not-exist

not-exist

not-exist

PFUS

not-exist not-exist

not-exist

not-exist

exist not-exist

not-exist

PSUS

exist : the target status existing in the groupnot-exist : the target status not existing in the group

Option COPY/RCPY PSUE PDUB PFUS PSUS PFUL PAIR Group

status


volume connection path (the physical link of paired volumes and servers). The pairdisplay command can be used for a paired volume or a group of paired volumes.

Syntaxpairdisplay{ -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -FHORC [MU#]| -FMRCF [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -c | -l | -f[xcdmew] | -CLI | -m <mode> | -v jnl[t] | -v ctg | -v pid }


Option Description


-q Terminates the interactive mode and exits the pair volume check command.

-z or -zx Makes the pairdisplay command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option



-g <group> Specifies the group name defined in the configuration definition file. This option must always be specified. The command is executed for the specified group unless the -d <pair Vol> option is specified.

-d <pair Vol> This option is used to specify the paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volumes.




Forcibly specifies a cascading remote copy volume for specified pair logical volumes on local copy environment. If the -l option is specified, this option displays status of a cascading remote copy volume on a local host (near site). If no -l option is specified, this option displays status of a cascading remote copy volume on a remote host (far site). This option cannot be specified with -m <mode> option on the same command line.




Forcibly specifies a cascading local copy volume for specified pair logical volumes on remote copy environment. If the -l option is specified, this option displays status of a cascading local copy volume on a local host (near site). If no -l option is specified, this option displays status of a cascading local copy volume on a remote host (far site). This option cannot be specified with -m <mode> option on the same command line.



-c Checks the configuration of the paired volume connection path (physical link of paired volume among the servers) and displays illegal pair configurations. If this option is not specified, the status of the specified paired volume is displayed without checking the path configuration.

-l Displays the paired volume status of the local host (which issues this command).

-fx Displays the LDEV ID as a hexadecimal number.

-fc Displays copy operation progress, sidefile percentage, bitmap percentage, or Universal Replicator journal percentage. Displays PFUL/PFUS for TrueCopy Async and Universal Replicator. Used to confirm SSWS state as indication of SVOL_SSUS-takeover after.

-fd Displays the relation between the Device_File and the paired volumes, based on the group (as defined in the local instance configuration definition file). If Device_File column shows 'Unknown' as shown in the Display example, it means that the volume cannot be recognized by the host because the volume has not been registered when you start CCI, and pair operation are rejected (except the local option such as '-l') in protection mode.Display example:# pairdisplay -g oradb -fdGroup PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -oradb oradev1(R) Unknown 0 35013 ****..---- ----, ----- -- -

-fm Displays the Bitmap mode to output of M column.

Option Description


-fe Displays the serial# and LDEV# of the external LUNs mapped to the LDEV and additional information for the pair volume. This option displays the information above by adding to last column, and then ignores the format of 80 column. This option is not valid if the cascade options (-m all,-m cas) are specified.Display example for TC/TC Async/UR:# pairdisplay -g horc0 -fe Group ... LDEV#.P/S,Status,Fence,Seq#,P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# R/Whorc0 ... 41.P-VOL PAIR ASYNC ,63528 40 - 0 - 2 - - - -/-horc0 ... 40.S-VOL PAIR ASYNC ,----- 41 - 0 - - - - - -/-

Display example for SI/Copy-on-Write Snapshot/Volume Migration:# pairdisplay -g horc0 -fe Group ... Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M CTG CM EM E-Seq# E-LDEV# horc0 ... 63528 65.P-VOL COPY,63528 64 - - N - - -horc0 ... 63528 64.S-VOL COPY,----- 65 - - N - - -

CTG: For TC, TC Async, and UR, it displays the CT group ID when the fence level is ASYNC. For TC Sync CTG, it displays the CT group ID when the fence level is DATA, STATUS, or NEVER. For SI, it displays the CT group ID on volumes split with specifying the consistency group using SI.JID: The journal ID for P-VOL or S-VOL. In the HAM configuration, it shows the quorum ID and the fence level is set to 'Never'. When it is not the UR or HAM configuration, '-' is displayed.AP: The number of active paths for UR links on P-VOL, and it displays the number of active paths for UR links on P-VOL and S-VOL.'Unknown'is shown as '-'. Refer to 'MINAP' information that is displayed by running the pairvolchk command.CM: The Copy mode• N: Non SnapShot• S: SnapShot. In the SMPL state, this shows that pair-volume is

created as SnapShot.• C: Cruising CopyEM: The external connection mode• H: Mapped E-lun as hidden from the host.• V: Mapped E-lun as visible to the host• ' - ': Unmapped to the E-lun• BH: Mapped E-lun as hidden from the host, but LDEV blockading.• BV: Mapped E-lun as visible to the host, but LDEV blockading• B: Unmapped to the E-lun, but LDEV blockadingE-Seq#: The production (serial) number of the external LUN. 'Unknown' is shown as '-'. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345). E-LDEV#: The LDEV# of the external LUN, 'Unknown' is shown as '-'.

Option Description



-fe (continued)

R/W: Displays the I/O mode when Read/Write is performed. For GAD configuration, the following modes are displayed:• L/L: Read/Write is performed on both the primary and secondary

volumes.• L/M: Read is performed on both the primary and secondary

volumes. Write is performed on the primary volume first, and then done on the secondary volume.

• B/B: Read/Write is rejected (Illegal Request is replied). LU-undefined is returned as a response of the Inquiry command on this volume.

-fw Used when displaying the WWN setting (defined by '50060E80+RAID Type,Serial#,Port#)) to the port instead of a port name. If this option is specified with the '-fe' option at the same line, then 'LUN WWN' appears as shown below. If WWN is not computed, then 'Unknown' appears (for example, SCSI).Display example:# pairdisplay -g PG01 -fwGroup PairVol(L/R) (WWN, LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# MPG01 ora01(L) (500060e804f42001, 3-0) 62496 67. P-VOL COPY, 62496 69 -PG01 ora01(R) (500060e804f42001, 5-0) 62496 69. S-VOL COPY, ----- 67 -PG01 ora02(L) (500060e804f42001, 4-0) 62496 68. P-VOL COPY, 62496 64 -PG01 ora02(R) (500060e804f42001, 6-0) 62496 64. S-VOL COPY, ----- 68 -

Display example:# pairdisplay -IH -g PG01 -CLI -l -fweGroup PairVol L/R WWN LU Seq# LDEV# P/S Status Fence Seq# P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# LUN-WWN PG01 oradb01 L 500060e804fa0f01 1 64015 11 P-VOL PAIR ASYNC 62496 11 - 5 - 1 - - - 60060e8005fa0f000000fa0f0000000b PG01 oradb02 L 500060e804fa0f01 2 64015 12 P-VOL PAIR ASYNC 62496 12 - 5 - 1 - - - 60060e8005fa0f000000fa0f0000000c

-CLI Used when specifying display for command line interface (CLI). This option displays to the same position that defined number of columns, and displays one header. The delimiters between columns are displayed as spaces or hyphens (-). Display example:Group PairVol L/R Port# TID LU-M Seq# LDEV# P/S Status Seq#P-LDEV# Mhomrcf1 deva0 L CL1-D 3 5 0 30053 271 P-VOL PAIR 30053 263 -homrcf1 deva1 L CL1-D 3 5 1 30053 271 SMPL - - - - homrcf1 deva2 L CL1-D 3 5 2 30053 271 SMPL - - - -

Option Description


-m <mode> Used when displaying a paired status of each mirror descriptors for the specified pair logical volume, and used for paired status indication of the cascading volume. The <mode> option can be designated 'cas' or 'all' :• The 'cas' option is used when displaying a paired status of

specified group that is registered to the mirror descriptor (MU#) on the cascading configuration file.

• The 'all' option is used when displaying a paired status of all mirror descriptors (MU#).

This option (-m <mode>) is not affected with command execution environment (TrueCopy/TrueCopy Async/Universal Replicator and ShadowImage/Copy-on-Write Snapshot /Volume Migration), and displays the paired status. This option cannot be specified with the -FHORC/-FMRCF option on the same command line.

-v jnl[t] Displays the JNL status for the local and remote interconnected to the group. Also finds the journal ID for each local and remote interconnected to the group via the specified group or <raw_device>, and displays information of each journal ID corresponding the local and remote. The first line shows the journal information for the local host, second line shows the journal information for the remote host. The item for displaying is the same as raidvchkscan -v jnl[t].Example:# pairdisplay -g VG01 -v jnlJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Nnm LDEV#001 0 2 PJNN 4 21 43216fde 30 512345 62500 2 265002 0 2 SJNN 4 95 3459fd43 52000 512345 62538 3 270

Example:# pairdisplay -g VG01 -v jnltJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW001 1 2 PJNN 4 21 43216fde 30 512345 62500 20 300 40002 1 2 SJNN 4 95 3459fd43 52000 512345 62538 20 300 40

Example:# pairdisplay -g VG01 -v jnl -FCA 1JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Nnm LDEV# 003 1 2 PJNN 4 21 43216fde 30 512345 62500 2 265

Notes: • This option can be specified with following options on the same

command line:{-g<group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -FCA [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -l | -f[x] }

• The '-FHORC [MU#]' or '-FCA [MU#]' option is used when displaying the journal information of cascading Universal Replicator volume, and then it shows the journal information for the remote host only.

• This option displays nothing if the target volume is NOT a Universal Replicator volume.

Option Description



-v ctg This option finds the CT group for each local and remote interconnected to the group via the specified group or <raw_device>, and displays any information of each CT group corresponding the local and remote. The first line shows the CT group information for the local host, second line shows the CT group information for the remote host.Example:# pairdisplay -g VG01-v ctgCTG P/S Status AP U(%) Q-Marker QM-Cnt SF(%) Seq# IFC OT/sCT/m RT/m001 P-VOL PAIR 2 0 00000080 3 50 63528 ON 90 5 5001 S-VOL PAIR - 0 0000007d - 50 63528 - - - -

CTG: Displays the CT group ID.P/S: The attribute of a volume in first LDEV of the specified group. Status: The status of the paired volume in first LDEV of the specified group.AP: Displays the number of Active Path in Universal Replicator links on P-VOL, also displays the number of active path in Universal Replicator links on P-VOL and S-VOL, 'Unknown' is shown as '-'.U(%):The usage sidefile/journal data, it is valid at PAIR state.For TrueCopy Async: The sidefile percentage for CT group in relationship to a 100% full sidefile in cache.For Universal Replicator: The usage rate of the current journal data as 100% of the journal data space.Q-Marker: In P-VOL, the latest sequence # of the MCU PVol when the write command was received. In S-VOL, the latest sequence # of the DFW on RCU. This item is valid at PAIR state.QM-Cnt: The number of remaining Q-Marker within CT group of the Unit. TrueCopy Async sends a token called 'dummy recordset' at regular interval time, therefore QM-Cnt always shows '2' or '3' even if host has NO writing. This item is valid at PAIR state.SF(%):The usage of cache setting as the sidefile regardless of Universal Replicator and TrueCopy Async.Seq#: The serial number of the RAID storage system. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345).IFC: Shows 'ON'/ 'OFF' for controlling Inflow.OT/s: The 'offloading timer' (specified in seconds) setting to CT group for TrueCopy Async and Universal Replicator. In Universal Replicator, this is the same as 'DOW' item shown by raidvchkscan -v jnlt or pairdisplay -v jnlt.CT/m: The 'Copy Pending timer' (specified in minutes) setting to CT group for only TrueCopy Async.RT/m: The 'RCU Ready timer' (specified in minutes) setting to CT group for only TrueCopy Async.Note: This option displays nothing if the target volume is NOT a TrueCopy Async or Universal Replicator volume. The '-FHORC [MU#]' or '-FCA [MU#]' option is used when displaying the information of cascading TrueCopy Async/Universal Replicator volume, and then it shows the CT group information for the remote host only.

Option Description


Returned values--

Error codes--

ExamplesTrueCopy/TrueCopy Async/Universal Replicator pairdisplay command example:

# pairdisplay -g oradb -fcxGroup Pair Vol(L/R) (P,T#,L#), Seq#, LDEV#..P/S, Status,Fence, Copy%, P-LDEV# Moradb oradb1(L) (CL1-B, 1,0) 1234 64..P-VOL PAIRNever, 75 C8 -oradb oradb1(R) (CL1-A, 1,0) 5678 C8..S-VOL PAIRNever, ---- 64 -

-v pid Finds the pool ID for each local and remote interconnected to the group via the specified group or <raw_device>, and displays any information of each pool ID corresponding the local and remote. The first line shows the pool information for the local host, second line shows the pool information for the remote host. The displayed items are the same as for raidvchkscan -v pid.Example:# pairdisplay -g VG01 -v pid PID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%) 127 POLN 0 6 3000 3000 63528 2 864 80127 POLN 0 6 3000 3000 63528 2 864 80# pairdisplay -g VG01 -v pid -lPID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%) 127 POLN 0 6 3000 3000 63528 2 864 80

H(%): Displays the threshold rate being set to the Copy-on-Write Snapshot pool as High water mark. 'Unknown' is shown as '-'.Note: This option displays nothing if the target volume is NOT Copy-on-Write Snapshot volume.

-v pid -FMRCF The '-FBC [MU#]' option is used for displaying the pool information of cascading Copy-on-Write Snapshot volume, so that you can monitor the pool status on remote host connected to cascading TrueCopy_PVOL to TrueCopy_SVOL/Copy-on-Write Snapshot_PVOL. It shows the pool information for the remote host only.Example:# pairdisplay -g VG01 -v pid -FMRCFPID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%)127 POLN 0 6 3000 3000 63528 2 864 80

Option Description



ShadowImage/Copy-on-Write Snapshot pairdisplay command example:

# pairdisplay -g oradbGroup Pair Vol(L/R) (Port#,TID,LU-M), Seq#, LDEV#..P/S, Status,Fence, Seq#, P-LDEV# Moradb oradb1(L) (CL1-A, 1,0) 30053 18..P-VOL PAIRNever, 30053 19 -oradb oradb1(R) (CL1-D, 1,0) 30053 19..S-VOL PAIRNever, ---- 18 -

Examples of pairdisplay -m

Display example for -m cas:# pairdisplay -g oradb -m casGroup PairVol(L/R) (Port#,TID,LU-M), Seq#, LDEV#..P/S, Status,Seq#, P-LDEV# Moradb oradev1(L) (CL1-D , 3, 0-0) 30052 266....SMPL ----,----- ---- -oradb oradev1(L) (CL1-D , 3, 0) 30052 266....P-VOL COPY,30053 268 -oradb1 oradev11(R) (CL1-D , 3, 2-0) 30053 268....P-VOL COPY,30053 270 -oradb2 oradev21(R) (CL1-D , 3, 2-1) 30053 268....P-VOL PSUS,30053 272 Woradb oradev1(R) (CL1-D , 3, 2) 30053 268....S-VOL COPY,----- 266 -

Display examples for -m all:# pairdisplay -g oradb -m allGroup PairVol(L/R) (Port#,TID,LU-M), Seq#, LDEV#..P/S, Status,Seq#, P-LDEV# Moradb oradev1(L) (CL1-D , 3, 0-0) 30052 266....SMPL ----,---- ---- ------ -----(L) (CL1-D , 3, 0-1) 30052 266....SMPL ----,---- ---- ------ -----(L) (CL1-D , 3, 0-2) 30052 266....SMPL ----,---- ---- -oradb oradev1(L) (CL1-D , 3, 0) 30052 266....P-VOL PAIR,30053 268 -oradb1 oradev11(R) (CL1-D , 3, 2-0) 30053 268....P-VOL COPY,30053 270 -oradb2 oradev21(R) (CL1-D , 3, 2-1) 30053 268....P-VOL PSUS,30053 272 W----- -----(R) (CL1-D , 3, 2-1) 30053 268....SMPL ----,----- ---- -oradb oradev1(R) (CL1-D , 3, 2) 30053 268....S-VOL COPY,----- 266 -

# pairdisplay -d /dev/rdsk/c0t3d0 -l -m allGroup PairVol(L/R) (Port#,TID,LU-M), Seq#, LDEV#..P/S, Status,Seq#, P-LDEV# Moradb oradev1(L) (CL1-D , 3, 0-0) 30052 266....SMPL ----,---- ---- ------ -----(L) (CL1-D , 3, 0-1) 30052 266....SMPL ----,---- ---- -


----- -----(L) (CL1-D , 3, 0-2) 30052 266....SMPL ----,---- ---- -oradb oradev1(L) (CL1-D , 3, 0) 30052 266....P-VOL PAIR,30053 268 -

Output of the pairdisplay command:

Group = group name (dev_group) as described in the configuration definition file

Pair Vol(L/R) = paired volume name (dev_name) as described in the configuration definition file. (L) = local host; (R) = remote host

(P,T#,L#) (TrueCopy, TrueCopy Async, Universal Replicator) = port, TID, and LUN as described in the configuration definition file.

(Port#,TID,LU-M) (ShadowImage, Copy-on-Write Snapshot) = port number, TID, LUN, and MU number as described in the configuration definition file.

Seq# = serial number of the RAID storage system. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345).

LDEV# = logical device number

P/S = volume attribute

Status = status of the paired volume

Fence (TrueCopy, TrueCopy Async, Universal Replicator) = fence level

% = copy operation completion, or percent pair synchronization

Vol. Copy Pair Other Copy Pair Other Copy Pair Pvol_psus Svol_copy Other

TrueCopy Async status

TrueCopy Sync status ShadowImage, Copy-on-Write Snapshot, or Volume Migration status

P-VOL

CR SF BMP CR BMP BMP CR CR BMP CR

S-VOL

- SF BMP - BMP BMP CR CR CR CR

Volume Copy Pair PSUS/SSUS (PJNS/SJNS) Other

Universal Replicator status

P-VOL CR JF JF BMP

S-VOL - JF JF BMP



P-LDEV# = LDEV number of the partner volume of the pair

M

For P-VOL and 'PSUS' state:

M='W' shows that S-VOL is suspending with R/W enabled through the pairsplit.

M='-' shows that S-VOL is suspending with read only through the pairsplit.

For S-VOL and 'SSUS' state:

M='W' shows that S-VOL has been altered since entering SSUS state.

M='-' shows that S-VOL has NOT been altered since entering SSUS state.

For 'COPY/RCPY/PAIR/PSUE' state:

M='N' shows that its volume are read-disabled through the paircreate '-m noread'.

paircurchk (for TrueCopy)The paircurchk command is used to check the currency of the TrueCopy secondary volume(s) by evaluating the data consistency based on pair status and fence level.

The following table specifies the data consistency for each possible state of a TrueCopy volume. A paired volume or group can be specified as the target of the paircurchk command. The paircurchk command assumes that the target is an S-VOL. If the paircurchk command is specified for a group, the data consistency of each volume in the group is checked, and all inconsistent volumes are found in the execution log file and displayed. The paircurchk command is also executed as part of the horctakeover command (see next section).

Table 2-8 Data consistency displayed by the paircurchk command

CR: Shows the copy operation rate (identical rate of a pair). BMP: Shows the identical percentage of BITMAP both P-VOL and S-VOL. SF: Shows sidefile percentage of each CT group as sidefile 100% on cache of both P-VOL and S-VOL. Following is an arithmetic expression using the high water mark (HWM) as 100% of a sidefile space:HWM(%) = HWM(%)/Sidefile space (30 to 70) × 100 JF: Shows the usage rate of the current journal data as 100% of the journal data space.

Volume Copy Pair PSUS/SSUS (PJNS/SJNS) Other

Object Volume Currency

Attribute Status Fence Paircurchk SVOL_takeover

SMPL - - To be confirmed -

P-VOL - - To be confirmed -


Syntaxpaircurchk { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -nomsg }

S-VOL COPY Data Inconsistent Inconsistent

Status

Never

Async Inconsistent Inconsistent

PAIR Data OK OK

Status OK OK

Never To be analyzed To be analyzed

PAIR Async To be analyzed OK (assumption)

PFUL To be analyzed OK (assumption)

PSUS Data Suspected Suspected

Status Suspected Suspected

Never Suspected Suspected

PSUS Async Suspected Suspected

PFUS Suspected OK (assumption)

PSUEPDUB

Data OK OK

Status Suspected Suspected

Never Suspected Suspected

Async Suspected OK (assumption)

SSWS Data Suspected -

Status Suspected

Never Suspected

Async Suspected

Legend:To be confirmed = It is necessary to check the object volume, since it is not the secondary volume.Inconsistent = Data in the volume is inconsistent because it was being copied.To be analyzed = It cannot be judged from the status of the secondary volume whether data is consistent or not. It is OK if the status of the primary volume is PAIR. It is Suspected if the status is PSUS or PSUE.Suspected = The primary volume data and secondary volume data are not consistent.OK (assumption) = Mirroring consistency is not assured, but as S-VOL of TrueCopy Async or Universal Replicator, the sequence of write data is ensured.

Object Volume Currency

Attribute Status Fence Paircurchk SVOL_takeover




Returned valuesThe paircurchk command sets the following returned values during exit allowing you to check the execution results.

Normal termination (data is consistent): 0


Option Description



-z or -zx Makes the paircurchk command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.




-d <pair Vol> Specifies paired logical volume name defined in the configuration definition file. When this option is specified, the command is executed for the specified paired logical volume.





-nomsg: Suppresses messages to be displayed when this command is executed. This option must be specified at the beginning of a command argument. The command execution log is not affected by this option.


Error codesThe following table lists and describes the error codes for the paircurchk command. Unrecoverable errors are fixed and is not resolved, even after re-executing the command. If the command fails, the detailed status is logged in the CCI command log ($HORCC_LOG), even if the user script has no error handling.

Table 2-9 Specific error code for paircurchk

ExamplesThe following shows an example of the paircurchk command for a group and the resulting display of inconsistent volumes in the specified group.

# paircurchk -g oradbGroup Pair vol Port targ# lun# LDEV# Volstatus Status Fence To be...oradb oradb1 CL1-A 1 5 145 S-VOL PAIR NEVER Analyzedoradb oradb2 CL1-A 1 6 146 S-VOL PSUS STATUS Suspected

horctakeoverThe horctakeover command is a scripted command for executing several takeover operations. The horctakeover command checks the specified volume's or group's attributes (paircurchk), decides the takeover function based on the attributes, executes the chosen takeover function, and returns the result. The four takeover functions designed for HA software operation are (see Horctakeover command functions in the User and Reference Guide): takeover-switch, swap-takeover, PVOL-takeover, and SVOL-takeover. A paired volume or a group can be specified as the target of the TrueCopy takeover command. If SVOL-takeover is specified for a group, the data consistency check is executed for all volumes in the group, and all inconsistent volumes are found in the execution log file and displayed (same as paircurchk command). You can execute the horctakeover command only for remote copy pairs.

The horctakeover command allows swapping of the primary and secondary volumes, so that if the primary or secondary volume is switched due to a server error or package transfer, duplex operations can be continued using the reversed volumes. When control is handed over to the current node, swapping the volumes again eliminates the need to copy them. The horctakeover command also allows the secondary volume to be separated for disaster recovery operations.



EX_VOLCUR S-VOL currency error

Check volume list to see if an operation was directed to the wrong S-VOL.

225



Syntaxhorctakeover { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -S | -l | -t <timeout> | -nomsg }


Option Description



-z or -zx Makes the horctakeover command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.


Specifies the command as [HORC]/[HOMRCF] or [TrueCopy]/[ShadowImage], and used to specify the CCI instance number.







-S Selects and executes SVOL-takeover. The target volume of the local host must be an S-VOL. If this option is specified, then the following '-l' option is invalid.


Returned valuesThe horctakeover command sets the following returned values during exit allowing you to check the execution results.

Normal termination:

0: Nop-takeover (no operation).

1: Swap-takeover was successfully executed.

2: SVOL-takeover was successfully executed.

3: PVOL-SMPL-takeover was successfully executed.

4: PVOL-PSUE-takeover was successfully executed. (This value depends on the microcode level.)

5: SVOL-SSUS-takeover was successfully executed. (This value depends on the microcode level.)

Abnormal termination: other than 0-5, refer to the error codes for error details.

Error codesThe following table lists and describes the error codes for the horctakeover command. Unrecoverable errors are fixed and not resolved, even after re-executing the command. If the command fails, the detailed status is logged in the CCI command log ($HORCC_LOG), even if the user script has no error handling.

-l Enables read and write to the primary volume(s) by a local host only without a remote host, and executes PVOL-takeover when the primary volume cannot be used because it is fenced (fence = DATA or STATUS, state = PSUE or PDUB, or PSUE or PDUB volume is contained in the group). If the primary volume can be accessed, nop-takeover is executed. The target volume of the local host must be a P-VOL.

-t <timeout> Can be specified for asynchronous pairs only, ignored for synchronous pairs. Specifies the maximum time to wait (in seconds) for swap-takeover and SVOL-takeover operation to synchronize the P-VOL and S-VOL. If this timeout occurs, the horctakeover command fails with EX_EWSTOT. To avoid timeout, set this value less than or equal to the start-up timeout value of the HA control script.

-nomsg Suppresses messages to be displayed when this command is executed. This option must be specified at beginning of a command argument. The command execution log is not affected by this option.

Option Description



Table 2-10 Specific error codes for horctakeover

raidscanThe raidscan command displays configuration and status information for the specified port/TID(s)/LUN/MU#. The information is acquired directly from the storage system (not the configuration definition file).

Syntaxraidscan { -h | -q | -z | -I[H][M][instance#] or -I[TC][SI][instance#] | -p <port> [hgrp]|-pd[g] <raw_device> | -s <seq#> | -t <targ> | -l <lun> | [ -f[xfgde] ] | -CLI | -find[g] [op] [MU#] | [-g <group>] | -pi <strings> | -m <MU#>}





Confirm status using pairdisplay command. Make sure all volumes in the group have the same fence level and volume attributes.

236



229



235

EX_VOLCUR S-VOL currency error

Check volume list to see if an operation was directed to the wrong S-VOL.

225

EX_VOLCUE Local volume currency error

Confirm pair status of the local volume.

224

EX_VOLCRE Local and remote volume currency error

Confirm pair status of remote and local volumes using pairdisplay command.

223

Timer(Recoverable)

EX_EWSTOT Timeout waiting for specified status

Increase timeout value using -t option.

233

Option Description



-z or -zx Makes the raidscan command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.




-p <port> [hgrp]

Specifies the port ID of the port to be scanned.• Valid ports are CL1-A to CL1-R and CL2-A to CL2-R (excluding CL1-

I, CL1-O, CL2-I, CL2-O).• Valid expanded ports are CL3-A to CL3-R (excluding CL3-I and

CL3-O) and CLG-A to CLG-R (excluding CLG-I and CLG-O).The port is not case sensitive (for example, CL1-A = cl1-a = CL1-a = cl1-A).This option must be specified if '-find' or '-pd <raw_device>'option is not specified. [hgrp] is specified to display only the LDEVs mapped to a host group on a port.

-pd[g] <raw_device>

Specifies the raw device name. This option finds Seq# and port_name of the storage system to which the specified device can be connected, and scans the port of the storage system which corresponds with the unit ID that searches the unit ID from Seq#. This option must be specified if the '-find' option is not specified. If this option is specified, the following -s <seq#> option is not valid.The -pdg option is used when displaying a LUN on the host view by finding a host group.

-s <seq#> Used to specify the seq# (serial#) of the storage system when this option cannot specify the unit ID which is contained for '-p <port>' option. This option scans the port specified by '-p <port>' option of the storage system which corresponds with the unit ID that searches the unit ID from seq#. If this option is specified, then the unit ID that is contained in '-p <port>' option is invalid.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-t <targ> Specifies the target ID of the specified port. If this option is not specified, the command applies to all target IDs.

-l <lun> Specifies the LUN of the specified target ID. If this option is not specified, the command applies to all LUNs. If this option is specified, the TID must also be specified.

-f or -ff Specifies display of volume-type for a display column. If this is specified, -f[g] [d] option is invalid.

-fx Displays the LDEV number in hexadecimal notation.

-fg Specifies display of group_name for a display column. This option searches a group on the configuration definition file (local CCI instance) from the scanned LDEV, and displays a group_name when the scanned LDEV is contained in the group. If this option is specified, the -f[f] option is not allowed and the -f[d] option is invalid.

-fd Displays the Device_File that was registered to the group of the HORCM in the output, based on the LDEV (as defined in local instance config. def. file). If this option is specified, -f[f][g] option is not allowed.

Option Description



-fe Displays the serial# (E-Seq#) and LDEV# (E-LDEV#) of the external LUNs only mapped to the LDEV. If the external LUN mapped to the LDEV on a specified port does not exist, then this option does nothing. Also if this option is specified, -f[f][g][d] option is not allowed.Display example:# raidscan -p cl1-a-0 -fe -CLIPORT# /ALPA/C TID# LU# Seq# Num LDEV# P/S Status Fence E-Seq# E-LDEV# CL1-A-0 ef 0 0 48 62468 2 256 SMPL - - 30053 17CL1-A-0 ef 0 0 49 62468 2 272 SMPL - - 30053 23CL1-A-0 ef 0 0 50 62468 1 288 SMPL - - 30053 28

-CLI Specifies display for command line interface (CLI). This option displays to the same position that defined number of columns, and displays one header. The delimiters between columns are displayed as spaces or hyphens (-). Display example:Port# TargetID# Lun# Seq# Num LDEV# P/S Status Fence P- Seq# P-LDEV#CL1-C 1 0 30053 1 274 SMPL - - - -CL1-C 2 2 30053 1 260 P-VOL PAIR NEVER 30053 268CL1-C 2 3 30053 1 261 P-VOL PAIR NEVER 30053 269

-m <MU#> This option is used for displaying only the specified mirror descriptor. If you want to display all mirror descriptor, specify '-m all' for displaying all MUs.

-pi <strings> Changes a strings via STDIN for -find option to '<strings>'. If this option is specified, the -find option is ignored a raw device file provided via STDIN, and <strings> is used as input. A <strings> must be specified within 255 characters.

Option Description


-find [op] [MU#]

Executes the specified [op] using a raw device file provided via STDIN. If the -pi <strings> option is specified, this option does not use a strings via STDIN, and -pi <strings> is used as input.Restrictions: Special files via STDIN are specified in the following ways:• HP-UX: /dev/rdsk/* or /dev/rdisk/disk*• Solaris: /dev/rdsk/*s2 or c*s2• Linux: /dev/sd... or /dev/rd..., /dev/raw/raw*.• zLinux: /dev/sd... or /dev/dasd… or /dev/rd... /dev/raw/raw*.• AIX: /dev/rhdisk* or /dev/hdisk* or hdisk*• DIGITAL or Tru64: /dev/rrz*c or /dev/rdisk/dsk*c or /dev/cport/

scp*• IRIX64 : /dev/rdsk/*vol or /dev/rdsk/node_wwn/*vol/* or /dev/

dsk/*vol or /dev/dsk/node_wwn/*vol/*• Windows: hdX-Y,$LETALL,$Volume,$Phys,

D:\Vol(Dms,Dmt,Dmr)X\DskY, \Vol(Dms,Dmt,Dmr)X\DskYFor further information on LDM volumes for Windows systems, see Volume Discovery Function in the User and Reference Guide.• OpenVMS: $1$* or DK* or DG* or GK*Lines starting with '#' via STDIN are interpreted as comments.Lines starting with 'quit' via STDIN are interpreted as exit.

-find[g] Displays the port, target ID, and LUN (RAID storage system notation) which was mapped for LDEV using a special file (raw device file) provided via STDIN. If target ID and LUN are Unknown for the target device file, you should start CCI without any description for HORCM_DEV and HORCM_INST, and should describe the shown port, target ID, and LUN for HORCM_DEV. This option also uses the -fx option to display the LDEV numbers in hexadecimal.The -findg option is used to show a LUN on the host view by finding a host group.

Option Description



-find inst Registers the Device File name (raw device file provided via STDIN) to all mirror descriptors of the LDEV map table for HORCM, permits the matching volumes on horcm.conf in protection mode, and is started automatically. Therefore, you do not need to use this option normally. This option is also terminated to avoid wasteful scanning when the registration has been finished with based on HORCM. Therefore if HORCM does not need the registration any more, then nothing is done and it exits. This option can be used with '-fx' option to display LDEV numbers in hexadecimal. Example for HP-UX:# ioscan -fun | grep rdsk | raidscan -find instDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013 17/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17/dev/rdsk/c0t3d0 oradb1 oradev2 CL1-D 3 0 1 35013 17Note: When multiple device files share the same LDEV, the first device file is registered to the LDEV map table.• Group: Displays the group name (dev_group) defined in the

configuration definition file.• PairVol: Displays the paired volume name (dev_name) within the

group defined in the configuration definition file.• PORT: Displays the port number (port#) defined in the

configuration definition file.• TARG: Displays the target ID (TargetID) defined in the

configuration definition file.• LUN: Displays the LUN (LU#) defined in the configuration

definition file.• M: Displays the MUN (MU#) defined in the configuration definition

file. MU# for TrueCopy are shown as '-', and MU# for ShadowImage and Copy-on-Write Snapshot are shown as '0', '1', '2'.

• SERIAL: Displays the production (serial#) number of the RAID storage system. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345).

• LDEV: Displays the LDEV# within the RAID storage system.

Option Description


-find verify [MU#]

Displays the relation between group on the configuration definition file and Device_File registered to the LDEV map tables, based on the Device File name (raw device file provided via STDIN). This option can be used with '-fx' and '-fd' options. This option is affected by the command execution environment (HORCC_MRCF).# ioscan -fun | grep rdsk | raidscan -find verify DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17/dev/rdsk/c0t3d1 oradb oradev2 CL1-D 3 1 0 35013 18/dev/rdsk/c0t3d2 - - - - - 0 35013 19# ioscan -fun | grep rdsk | raidscan -find verify 1 -fdDEVICE_FILE Group PairVol Device_File M SERIAL LDEV/dev/rdsk/c0t3d0 oradb oradev1 c0t3d0 1 35013 17/dev/rdsk/c0t3d1 oradb oradev2 Unknown 1 35013 18/dev/rdsk/c0t3d2 - - - 1 35013 19

Note: If the device name is different between DEVICE_FILE and Device_File, then it shows shared LDEV among multiple device files.• Group: Displays the group name (dev_group) defined in the

configuration definition file.• PairVol: Displays the paired volume name (dev_name) within the

group defined in the configuration definition file.• PORT: Displays the port number (port#) defined in the

configuration definition file.• TARG: Displays the target ID (TargetID) defined in the

configuration definition file.• LUN: Displays the LUN (LU#) defined in the configuration

definition file.• M: Displays the MUN (MU#) defined in the configuration definition

file. MU# for TrueCopy are shown as '-', and MU# for ShadowImage and Copy-on-Write Snapshot are shown as '0', '1', '2'.

• Device_File: Displays Device_File which is registered to the LDEV map tables into the CCI.

• SERIAL: Displays the production (serial#) number of the RAID storage system. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345).

• LDEV: Displays the LDEV# within the RAID storage system.

Option Description



-find[g] conf [MU#] [-g <group>]

Displays the port, target ID, LUN in horcm.conf image by using a special file (raw device file) provided via STDIN. If target ID & LUN are Unknown for the target device file, you must start CCI without any description for HORCM_DEV and HORCM_INST, and should be described the shown port, target ID, LUN for HORCM_DEV. This option can be used with the '-fx' option.[-g <group>] specifies the group for 'dev_group' on horcm.conf. If omitted, the group applies 'VG' as default.The -findg option is used when displaying a LUN on the host view by finding a host group.# cat /etc/horcmperm.conf | raidscan -find conf 0 -g ORAHORCM_DEV#dev_group dev_name port# TargetID LU# MU## /dev/rdsk/c23t0d0 SER = 61456 LDEV = 192 [ FIBRE FCTBL = 4 ]ORA ORA_000 CL2-J 0 0 0# /dev/rdsk/c23t0d1 SER = 61456 LDEV = 193 [ FIBRE FCTBL = 4 ]ORA ORA_001 CL2-J 0 1 0# /dev/rdsk/c23t0d2 SER = 61456 LDEV = 194 [ FIBRE FCTBL = 4 ]ORA ORA_002 CL2-J 0 2 0# /dev/rdsk/c23t0d3 SER = 61456 LDEV = 195 [ FIBRE FCTBL = 4 ]ORA ORA_003 CL2-J 0 3 0# ERROR [CMDDEV] /dev/rdsk/c23t0d7 SER = 61456 LDEV = 259 [ OPEN-3-CM ]

If the target device has shared an LDEV among multiple device files and an LDEV is displayed by another target device already, then its target device is suppressed as a comment as shown below:# ERROR [LDEV LINK] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [FIBRE FCTBL = 4]

If the target device does not have a valid MU#, then its target device is suppressed as a comment as shown below:# ERROR [INVALID MUN (2 < 1)] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3 ]

If the target device is mixed with a different RAID TYPE, then its target device is suppressed as a comment as shown below:# ERROR [MIXING RAID TYPE] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3 ]

Option Description


Returned values--

Error codes--

-find sync[d] [MU#] [-g <group>]

Flushes the system buffer associated to a logical drive which corresponds to a [-g <group>] through the KEY WORD($Volume,$LETALL, $Physical) provided via STDIN. [-g <group>] specifies the group for 'dev_group' on horcm.conf. If this option is not specified, then flushes the system buffer associated to all groups for the local instance.Example of flushing the system buffer associated to ORB group through $Volume (Windows):echo $Volume | raidscan -find sync -g ORB orraidscan -pi $Volume -find sync -g ORB[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}

Example of flushing the system buffer associated to all groups for the local instance (Windows):echo $Volume | raidscan -find sync orraidscan -pi $Volume -find sync[SYNC] : ORA ORA_000[-] -> \Vol44\Dsk0 : Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}[SYNC] : ORA ORA_000[-] -> \Vol45\Dsk0 : Volume{56e4954a-28d5-4824-a408-3ff9a6521e5e}[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}

Notes:(2) The option cannot be specified the device object name as follows: D:\Vol(Dms,Dmt,Dmr)X\DskY,\Vol(Dms,Dmt,Dmr)X\DskY(3) Sync executes the following behavior under any conditions:• If the logical drive which corresponds to a [-g <group>] is not

open by any applications, then sync flushes the system buffer to a drive and makes the dismount state for this drive.

• If the logical drive which corresponds to a [-g <group>] is already opened by any applications, then sync flushes only the system buffer to a drive. This is allowed to flush the system buffer before pairsplit with mounting the P-VOL (opening state), and indicates the behavior as [FLUSH] below: [FLUSH] : ORA ORA_000[-] -> \Vol44\Dsk0 : Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}

Option Description



Examples

raidscan command examples for fibre-channel ports

# raidscan -p cl1-rPORT#/ALPA/C,TID#,LU#Num(LDEV#...)P/S,Status,Fence,LDEV#,P-Seq#P-LDEV#CL1-R/ ce/15,15, 7 5(100,101..)P-VOL PAIR NEVER 100,5678 200CL1-R/ ce/15,15, 6 5(200,201..)SMPL ---- ---- ---- ---- -----

# raidscan -p cl1-r -fPORT#/ALPA/C,TID#,LU#Num(LDEV#...)P/S,Status,Fence,LDEV#,Vol.TypeCL1-R/ ce/15,15, 7 5(100,101..)P-VOL PAIR NEVER 100,OPEN-3CL1-R/ ce/15,15, 6 5(200,201..)SMPL ---- ---- ----OPEN-3

Example of -find option for raidscan

# ls /dev/rdsk/* | raidscan -findDEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID/dev/rdsk/c0t0d4 0 S CL1-M 0 4 31168 216 OPEN-3-CVS-CM/dev/rdsk/c0t0d1 0 S CL1-M 0 1 31168 117 OPEN-3-CVS/dev/rdsk/c1t0d1 - - CL1-M - - 31170 121 OPEN-3-CVS

Output of the raidscan command:

Port#, ALPA/C, TID#, LU#: port ID, arbitrated loop physical address, target ID, LUN.

For ShadowImage, raidscan displays the MU# for each LUN (for example, LUN 7-0, 7-1, 7-2).

Num(LDEV#…): number of LDEVs and LDEV ID for a LUSE volume

P/S: volume attribute

Status: status of the paired volume

Fence: fence level (TrueCopy only)

P-Seq#: serial # of the storage system which contains the partner volume of the pair. The serial number for VSP G1000 is displayed with a “3” at the beginning (“312345” = serial # 12345).

P-LDEV#: LDEV number of the partner volume of the pair

Vol.Type: logical unit (LU) type (for example, OPEN-V, OPEN-9)

Group: group name (dev_group) as described in the configuration definition file

UID: Displays the unit ID for multiple storage system configuration. If UID appears as '-', the command device for HORCM_CMD is not found.

S/F: Displays whether the port is SCSI or fibre

PORT: Displays the RAID storage system port number

TARG: Displays the target ID (that was converted by the fibre conversion table)


LUN: Displays the LUN (that was converted by the fibre conversion table)

SERIAL: Displays the production (serial#) number of the RAID storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

LDEV: Displays the LDEV# within the RAID storage system

PRODUCT_ID: Displays product-id field in the STD inquiry page

raidarThe raidar command displays configuration, status, and I/O activity information for the specified port/TID(s)/LUN at the specified time interval. The configuration information is acquired directly from the storage system (not from the configuration definition file).

The I/O activity of a TrueCopy, TrueCopyAsync, or Universal Replicator S-VOL in the COPY or PAIR state includes TC/TC Async/UR remote I/Os (update copy operations) in addition to host-requested I/Os. The I/O activity of a ShadowImage, Copy-on-Write Snapshot, or Volume Migration S-VOL in the COPY or PAIR state includes only host-requested I/Os (ShadowImage, Copy-on-Write Snapshot, and Volume Migration update copy operations are excluded). The I/O activity of a P-VOL or simplex volume includes only host-requested I/Os. If the status changed into SMPL in S-VOL (COPY, PAIR) I/O activity, I/O activity is reported as the SMPL status, until the pair status is changed.

Syntaxraidar { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -p <port> <targ> <lun> [mun]| -pd[g] <raw_device> [mun]| -s [interval] [count] }


Option Description



-z or -zx Makes the raidar command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.





Returned values--

Error codes--

ExamplesThe following shows an example of the raidar command and its output.

# raidar -p cl1-a 15 6 -p cl1-b 14 5 -p cl1-a 12 3 -s 3TIME[03] PORT T L VOL STATUS IOPS HIT(%)W(%)IOCNT13:45:25 - - - - - - - - -13:45:28 CL1-A 15 6 SMPL - 200.0 80.0 40.0 600 CL1-B 14 5 P-VOL PAIR 133.3 35.0 13.4 400 CL1-A 12 3 P-VOL PSUS 200.0 35.0 40.6 600

Output of the raidar command:

IOPS: # of I/Os (read/write) per second (total I/O rate).

HIT(%): Hit rate for read I/Os (read hit rate).

W(%): Ratio of write I/Os to total I/Os (percent writes).

IOCNT: number of write and read I/Os.

-p <port> <targ> <lun> [mun]....

Monitors one or more (up to 16) devices at a time.• <port>: Specifies the port to be reported: CL1-A to CL1-R and CL2-

A to CL2-R (excluding CL1-I, CL1-O, CL2-I, CL2-O). In case of the expanded port, specify from following: CL3-A to CL3-R (excluding CL3-I and CL3-O), or CLG-A to CLG-R (excluding CLG-I and CLG-O).

The port is not case sensitive (for example, CL1-A= cl1-a= CL1-a= cl1-A, CL3-a= CL3-A= cl3-a= cl3-A).• <targ>: Specifies the SCSI TID of the specified port.• <lun>: Specifies the LUN on the specified TID.• [mun]: Specifies the MU number of the specified LUN within the

range of 0 to 63 (ShadowImage or Copy-on-Write Snapshot only).

-pd[g] <raw_device>

Allows designation of an LDEV by raw device file name. The -pdg option is used to show a LUN on the host view by finding a host group.

-s [interval] or -sm [interval]

Designates the time interval in seconds.• -s: Interprets the time interval as seconds.• -sm: Interprets the time interval as minutes.• [interval]: Designates the time interval value (1 to 60). If not

specified, the default interval (3) is used.• [count]: Designates the number of repeats. When omitted, this

command repeats until CNTL-C.

Option Description


raidqryThe raidqry command (RAID query) displays the configuration of the connected host and RAID storage system.

Syntaxraidqry { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -l | -r <group> | [ -f ] | -g}


Returned values--

Error codes--

Examples

Example 1

The following shows an example of the raidqry command and its output.

# raidqry -lNo Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB) 1 --- HOSTA 01-22-03/06 0 30053 50-04-00/00 256

Option Description



-z or -zx Makes the raidqry command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-l Displays the configuration information for the local host and the local RAID storage system.

-r <group> Displays the configuration information for the remote host and the remote storage system which contains the specified group.

-f Displays the host name (ip_address) as specified in the configuration definition file. Use this option if 'floatable IP address' is used for the host name (ip_address) in the configuration file.

-g This option is used when displaying the lists of group name (dev_group) which described in the configuration file of a local host (instance).



1 --- HOSTA 01-22-03/06 1 30054 50-04-00/00 256

# raidqry -r oradbNo Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB) 1 oradb HOSTA 01-22-03/06 0 30053 50-04-00/00 256 2 oradb HOSTB 01-22-03/06 0 30053 50-04-00/00 256 1 oradb HOSTA 01-22-03/06 1 30054 50-04-00/00 256 2 oradb HOSTB 01-22-03/06 1 30054 50-04-00/00 256

# raidqry -l -fNo Group Floatable Host HORCM_ver Uid Serial# Micro_ver Cache(MB) 1 --- FH001 01-22-03/06 0 30053 50-04-00/00 256

Output of the raidqry command:

No: This column shows the order when the group name (dev_group) which is described in the configuration definition file has multiple remote hosts.

Group: When the -r option is used, this column shows the group name (dev_group) which is described in the configuration definition file.

Hostname: When using -l option, this column shows the host name of local host. When using -r option, this column shows the host name of remote host which is included the group name (dev_group) described in a configuration definition file. Over 30 characters long of the host name is not displayed.

Floatable Host: When the -f option is used, this column shows the host name (ip_address) which is described in the configuration definition file. Up to 30 host names can be displayed. The -f option interprets the host name as utilizing floatable IP for a host.

HORCM_ver: This column shows the version of CCI on the local or remote host. The -l option specifies local host. The -r option specifies remote host.

Uid Serial# Micro_ver: This column shows unitID, serial number, and (DKCMAIN) microcode version of the storage system that is connected to the local or remote host. The -l option specifies local host. The -r option specifies remote host. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Cache(MB): Shows the logical cache capacity (in MB) of the storage system connected to the local or remote host. The -l option specifies local host, and -r specifies remote host.

Example 2

# raidqry -gGNo Group RAID_type IV/H IV/M MUN/H MUN/M 1 ora HTC_RAID 12 9 4 64 2 orb XP_RAID 12 9 4 64 3 orc HTC_DF 8 6 1 1

GNo: The order of the group name (dev_group) described in the configuration definition file.

Group: The group name (dev_group) described in the configuration definition file.

RAID_type: The type of RAID configured in the group.


IV/H: The interface version for TrueCopy/TrueCopy Async/Universal Replicator in a group, and this is used for maintenance.

IV/M: The interface version for ShadowImage/Copy-on-Write Snapshot/Volume Migration in a group, and this is used for the maintenance.

MUN/H: The number of maximum MUs for Universal Replicator in a group.

MUN/M: The number of maximum MUs for ShadowImage/Copy-on-Write Snapshot in a group.

raidvchksetThe raidvchkset command sets the parameters for validation checking of the specified volumes, and can also be used to turn off all validation checking without specifying [type]. Unit of checking for the validation is based on the group of CCI configuration definition file.

This command is controlled as protection facility. This command is rejected with EX_ERPERM by connectivity checking between CCI and the RAID storage system.

Syntaxraidvchkset { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -nomsg | -vt [type] | -vs < bsize> [slba] [elba] | -vg [type] [rtime] | -vext <size> }


Option Description



-z or -zx Makes the raidvchkset command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-g <group> Specifies a group name written in the configuration definition file.









-vt [type] Specifies the following data type that assumes the target volumes as Oracle database. If [type] is not specified, then this option disables all of the checking.• redo8: The target volumes sets the parameter for validation

checking as Oracle redo log files (including archive logs) prior Oracle9I. This option sets <bsize> to 1(512bytes) or 2(1024bytes).

• data8: The target volumes sets the parameter for validation checking as Oracle data files (including control files) prior Oracle9I.

• redo9: The target volumes sets the parameter for validation checking as Oracle redo log files (including archive logs) for Oracle9IR2 or later. This option sets <bsize> to 1 (512 bytes) or 2 (1024 bytes).

• data9: The target volumes sets the parameter for validation checking as Oracle data files (including control files) for Oracle9IR2 later. For Oracle for Tru64 or Windows, set the parameter in the init.ora file to '_HARD_PROTECTION = TRUE '. If not so, a parameter for validation must be changed by using the following '-vmf we' option: raidvchkset -vt data9 -vmf we

• rd10g: The target volumes sets the parameter for validation checking as Oracle ALL files (including redo and data and RMAN backup piece) for Oracle10gR2 or later. This option sets <bsize> to 1 (512 bytes) or 2 (1024 bytes). This option sets to the low 5 bits DBA for checking regarding CHK-F2.

Option Description


-vs <bsize> [slba] [elba]

Specifies the data block size of Oracle I/O and a region on a target volume for validation checking.• <bsize> is used when specifying the data block size of Oracle I/O,

in increments of 512 bytes. <bsize> is able to specify between 1 (512 bytes) and 64 (32 KB) (effective size for Oracle is also 1-64).

• [slba] [elba] is used when specifying a region defined between Start_LBA (0 based) and End_LBA on a target volume for checking, in increments of 512 bytes.

• [slba] [elba] can be specified in hexadecimal (by addition of '0x ') or decimal notation. If this option is not specified, then a region for a target volume is set as all blocks (slba=0,elba=0).

-vg [type] [rtime]

Specifies the following guard type to the target volumes for Data Retention Utility. If [type] is not specified, this option releases all of the guarding.The following values are available to specify on [type].• inv: The target volumes are concealed from SCSI Inquiry

command by responding 'unpopulated volume'.• sz0: The target volumes replies with 'SIZE 0' through SCSI Read

capacity command.• rwd: The target volumes are prohibited from reading and writing.• wtd: The target volumes are prohibited from writing.• svd: If the target volume is SMPL, it is protected from paircreate

(from becoming an S-VOL). If the target volume is P-VOL, it is protected from pairresync restore or pairresync swaps(p). If the target volume is SVOL_PSUS(SSUS), it is protected from pairresync synchronous copy.svd option can be used with the other option (inv, sz0, rwd, wtd) in parallel. For example, if you want to protect the absolute volume from the writing executed by the copy series program product and the host access, set the both wtd and svd options. The only setting of wtd option cannot protect the absolute volume from the writing by the copy processing of the copy series program product.

[rtime]: Specifies the retention time in days. If [rtime] is not specified, the default time defined by the storage system is used.• This option sets each four flags for guarding type as follows:typeINQRCAPREADWRITE inv1111Sz00111rwd0011wtd0001

-vext <size> Used when extending the LUN capacity of a Dynamic Provisioning volume. <size> is used when specifying the extension data size in units of 'G, g, M, m, K, k'. If <size> is specified without unit, it is assumed to be 1 block size (512 bytes).Examples for extending 1GB (gigabyte) are: -vext 1G, -vext 1g, -vext 1024M, -vext 1024m, -vext 1048576K, -vext 1048576k, -vext 2097152Examples for extending 1KB (kilobyte) are: -vext 1K, -vext 1k, -vext 2LUN capacity and usage rate for Dynamic Provisioning volume can be verified by referring 'LU_CAP' of the 'raidvchkdsp -v aou' or 'raidvchkdsp -v aoub' command. "Aou" (allocation on use) refers to dynamic provisioning.Note: When a group operation is specified, a warning message appears, and this command enters the interactive mode.

Option Description



Returned valuesThe raidvchkset command sets the following returned values during exit allowing you to check the execution results.

Normal termination: 0

Abnormal termination: see Error Codes.

Error codesThe raidvchkset -vg option command returns the following error code as well as generic error codes.

Table 2-11 Specific error code for raidvchkset -vg option

ExamplesSets volumes in oralog group as redolog file prior to Oracle9I:

raidvchkset -g oralog -vt redo8

Sets volumes in oradat group as data file that Oracle block size is 8KB:

raidvchkset -g oradat -vt data8 -vs 16

Sets volumes in oradat group as data file that Oracle block size is 16KB:

raidvchkset -g oradat -vt data8 -vs 32

Releases all checking to volumes in oralog group:

raidvchkset -g oralog -vt

Sets Oracle10g volumes for oralog group as redolog file:

raidvchkset -g oralog -vt rd10g

Sets Oracle10g volumes for oradat group as data file with block size of 8KB:

raidvchkset -g oradat -vt rd10g -vs 16

Disables writing to volumes in oralog group:

raidvchkset -g oralog -vg wtd

Disables writing and sets retention time to volumes in oralog group:

raidvchkset -g oralog -vg wtd 365

Releases all guarding to volumes in oralog group:

raidvchkset -g oralog -vg


Volume Status(Unrecoverable)

EX_EPRORT Mode changes denied due to retention time

Confirm the retention time for a target volume by using raidvchkscan -v gflag command.

208


raidvchkdspThe raidvchkdsp command displays the parameters for validation checking of the specified volumes. Unit of checking for the validation is based on the group of CCI configuration definition file.

Syntaxraidvchkdsp { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#] | -d[g] <seq#> <LDEV#> [MU#] | -f[xde] | -v <op> | -c }


Option Description



-z or -zx Makes the raidvchkdsp command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-g <group> Specifies a group name written in the configuration definition file.






-fx Displays the LDEV/STLBA/ENLBA number in hexadecimal.



-fd Displays the relation between the Device_File and the paired volumes, based on the group (as defined in the local instance configuration definition file). If Device_File column shows 'Unknown' to HOST (instance), then the volume is not recognized on own HOST, and raidvchkdsp command is rejected in protection mode. Non-permitted volume is shown without LDEV# information (LDEV# '-').

-fe Displays the serial# and LDEV# of the external LUNs mapped to the LDEV for the target volume by adding to last column (ignores the format of 80 column).

Option Description


-c When CCI starts, HORCM_DEV in horcm.conf is translated from port/target/lun numbers to the CU:Ldev information, on one hand HORCM_LDEV in horcm.conf is translated from the CU:Ldev information to port/target/lun numbers, because RAID needs to specify 'Port#, Targ#, Lun#' and 'LDEV' for specifying the target device, and then HORCM keeps this information as internal database for the configuration.If a storage administrator changes the LDEV to LUN/port mapping, such as• a new/different LDEV is mapped to a previously used port/LUN, or• an LDEV is mapped to a different/new portthen pair operations might be rejected because the new mapping is different from the mapping information of the database in the running CCI instance. A pairdisplay command shows the real LDEV mapping at the time of the command execution and hence shows different information than what is stored in the internal database of the CCI instance.The '-c' option for raidvchkdsp allows you to see if there is a difference between the current running CCI instance information and the real mapping. This indication should be used to find such issues which indicate that:• the CCI instance should be restarted to discover and use the new

mapping information, or• a configuration change occurred without changing the affected

configuration files of the CCI instance. Example change from LDEV#785 to LDEV#786: # raidvchkdsp -g VG000 -cGroup PairVol Port# TID LU Seq# LDEV# LDEV#(conf) -change-> LDEV#VG000 vg0001 CL4-E-0 0 17 63528 786 785(conf) -change-> 786# raidvchkdsp -g VG000 -c -fxGroup PairVol Port# TID LU Seq# LDEV# LDEV#(conf) -change-> LDEV#VG000 vg0001 CL4-E-0 0 17 63528 312 311(conf) -change-> 312 Example remove LDEV#785 from a port: # raidvchkdsp -g VG000 -cGroup PairVol Port# TID LU Seq# LDEV# LDEV#(conf) -change-> LDEV#VG000 vg0001 CL4-E-0 0 17 63528 - 785(conf) -change-> NO LDEV# raidvchkdsp -g VG000 -c -fxGroup PairVol Port# TID LU Seq# LDEV# LDEV#(conf) -change-> LDEV#VG000 vg0001 CL4-E-0 0 17 63528 - 311(conf) -change-> NO LDEV Note: If there have not been any changes to the specified volumes, this option displays nothing.

Option Description



Returned values--

Error codes--

Examples

Example 1

Example of raidvchkdsp command with -fd option:

raidvchkdsp -g vg01 -fd -v cflagGroup PairVol Device_File Seq# LDEV# BR-W-E-E MR-W-B BR-W-B SR-W-B-Svg01 oradb1 Unknown 2332 - - - - - - - - - - - - - - -vg01 oradb2 c4t0d3 2332 3 D E B R D D D D E E D E D D

Example 2

Example of raidvchkdsp command with -fe option and its output:

-v [op] Specifies the following operation that displays each parameter for validation checking:• cflag: Displays all flags for checking regarding data block

validation for target vols.• offset: Displays the range setting for data block size of Oracle I/O

and a region on a target volume for validation checking.• errcnt: Displays the statistical information counted as an error for

each checking on the target volumes. Each statistical information counted as an error is cleared when the individual flag for validation checking is disabled.

• gflag: Displays the parameter for guarding on the specified target volumes.

• pool: This option displays the capacity and the usable capacity of the Copy-on-Write Snapshot pool corresponding to the group. Usually, this option displays the pool capacity and the usable capacity for the pool ID of which the group is belonging because pool ID is specified in pair creation with group. This is needed to help the decision whether the restore operation is possible or not, because the pool capacity is consumed by the restore operation of the Copy-on-Write Snapshot.

• aou[b]: Displays the LUN capacity and usage rate for Dynamic Provisioning volume corresponding to the group of RM configuration file, and displays the ID of the pool to which LDEV belongs.

• aoub: Displays the LUN capacity in blocks (1 block = 512 bytes).

Option Description


# raidvchkdsp -g horc0 -v gflag -feGroup... TID LU Seq# LDEV# GI-C-R-W-S PI-C-R-W-S R-Time EM E-Seq# E-LDEV#horc0... 0 20 63528 65 E E E E E E E E E E 0 - --horc0... 0 20 63528 66 E E E E E E E E E E 0 - --

Output of the raidvchkdsp command with -fe option:

EM: external connection mode.• H = Mapped E-lun is hidden from the host.• V = Mapped E-lun is visible to the host.• — = Unmapped to the E-lun.• BH = Mapped E-lun as hidden from the host, but LDEV blockading.• BV = Mapped E-lun as visible to the host, but LDEV blockading.• B = Unmapped to the E-lun, but LDEV blockading.

E-Seq#: production (serial) number of the external LUN ('Unknown' shown as '-'). For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

E-LDEV#: LDEV# of the external LUN ('Unknown' shown as '-').

Example 3

Example of raidvchkdsp command with -v cflag option and its output:

raidvchkdsp -g vg01 -fd -v cflagGroup PairVol Device_File Seq# LDEV# BR-W-E-E MR-W-B BR-W-B-Z SR-W-B-Svg01 oradb1 c4t0d2 2332 2 D E B R D D D D E E E D E D Dvg01 oradb2 c4t0d3 2332 3 D E B R D D D D E E E D E D D

Output of the raidvchkdsp command with -v cflag option:

BR-W-E-E: Displays the flags for checking data block size.

R=E: Checking for data block size on read is enabled. R=D: Checking for data block size on read is disabled.

W=E: Checking for data block size on write is enabled. W=D: Checking for data block size on write is disabled.

E=L: Data block on read/write is interpreted as little endian format. E=B: Data block on read/write is interpreted as big endian format.

E=W: This shows the Warning that read/write is not rejected when validation error is detected. E=R: This shows the Reject that read/write is rejected when validation error is detected.

MR-W-B: Displays the flags for checking CHK-F3 in the data block.

R=E: Checking for CHK-F3 on read is enabled. R=D: Checking for CHK-F3 on read is disabled.



W=E: Checking for CHK-F3 on write is enabled. W=D: Checking for CHK-F3 on write is disabled.

B=E: Checking for CHK-F3 in the data block #0 is enabled. B=D: Checking for CHK-F3 in the data block #0 is disabled.

BR-W-B-Z: Displays the flags for checking regarding CHK-F2 in the data block.



B=E: Comparing for CHK-F2 in the data block is enabled. B=D: Comparing for CHK-F2 in the data block is disabled.

Z=E: The NON zero checking for CHK-F2 in the data block shows to being enabled. Z=D: The NON zero checking for CHK-F2 in the data block shows to being disabled.

SR-W-B-S: Displays the flags for checking regarding CHK-F1 in the data block.




S=E: Referring for CHK-F1 flag contained in the data block is enabled. S=D: Referring for CHK-F1 flag contained in the data block is disabled.

Example 4

Example of raidvchkdsp command with-v offset option and its output:

# raidvchkdsp -g vg01 -fd -v offsetGroup PairVol Device_File Seq# LDEV# Bsize STLBA ENLBA BNMvg01 oradb1 c4t0d2 2332 2 1024 1 102400 9vg01 oradb2 c4t0d3 2332 3 1024 1 102400 9

Output of the raidvchkdsp command with -v offset option:

Bsize: Displays the data block size of Oracle I/O in bytes.

STLBA: Displays the start of LBA on a target volume for checking in blocks (512 bytes).

ENLBA: Displays the end of LBA on a target volume for checking in blocks (512 bytes).

Note: If STLBA and ENLBA are both zero, this means to check all blocks.


BNM: Displays the number of bits for checking regarding CHK-F2 (in bits). If BNM is zero, this means the checking for CHK-F2 is disabled.

Example 5

Example of raidvchkdsp command with -v errcnt option and its output:

# raidvchkdsp -g vg01 -fd -v errcntGroup PairVol Device_File Seq# LDEV# CfEC MNEC SCEC BNECvg01 oradb1 c4t0d2 2332 2 0 0 0 0vg01 oradb2 c4t0d3 2332 3 0 0 0 0

Output of the raidvchkdsp command with -v errcnt option:

CfEC: Displays the error counter for checking of block size validation.

MNEC: Displays the error counter for checking of CHK-F3 validation.

SCEC: Displays the error counter for checking of CHK-F1 validation.

BNEC: Displays the error counter for checking of CHK-F2 validation.

Example 6

Example of raidvchkdsp command with -v gflag option and its output:

# raidvchkdsp -g vg01 -fd -v gflagGroup PairVol Device_File Seq# LDEV# GI-C-R-W-S PI-C-R-W-S R-Timevg01 oradb1 c4t0d2 2332 2 E E D D E E E D D E 365vg01 oradb2 c4t0d3 2332 3 E E D D E E E D D E -

Output of the raidvchkdsp command with -v gflag option:

GI-C-R-W-S: Displays the flags for guarding as for the target volume.

I=E: Enabled for Inquiry command. I=D: Disabled for Inquiry command.

C=E: Enabled for Read Capacity command. C=D: Disabled for Read Capacity command.

R=E: Enabled for Read command. R=D: Disabled for Read command.

W=E: Enabled for Write command. W=D: Disabled for Write command.

S=E: Enabled for becoming the S-VOL. S=D: Disabled for becoming the S-VOL.

PI-C-R-W-S: Displays the permission flags that show whether each mode flag can be changed to enable or not.

I=E: 'I' flag can be changed to enable. I=D: 'I' flag cannot be changed to enable.

C=E: 'C' flag can be changed to enable. C=D: 'C' flag cannot be changed to enable.

R=E: 'R' flag can be changed to enable. R=D: 'R' flag cannot be changed to enable.



W=E: 'W' flag can be changed to enable. W=D: 'W' flag cannot be changed to enable.

S=E: 'S' flag can be changed to enable. S=D: 'S' flag cannot be changed to enable.

R-Time: Displays the retention time for write protect in days. The hyphen (-) shows that the retention time is infinite. The application knows whether the target volume is denied to change to writing enable by referring 'R-Time'.

R-time (Rtime) is identical to rtime and both of them indicate Retention Time. This setting value can normally be identified as a value of R-time that is output by raidychkdsp (the logging format is Rtime=xxxx). However, R-time (Rtime) is indicated as the value of 'Retention Time + 1000000' when the expiration lock is enabled. The setting of raidvchkset command in this status is denied.

Audit lock status is shown as the retention time plus 1000000. 'R-Time + 1000000' shows the retention time with Audit lock status.

Example 7

Example of raidvchkdsp command with -v pool option and its output:

raidvchkdsp -g vg01 -v poolGroup PairVol Port# TID LU Seq# LDEV# Bsize Available CapacityVg01 oradb1 CL2-D 2 7 62500 167 2048 100000 1000000000Vg01 oradb2 CL2-D 2 10 62500 170 2048 100000 1000000000

Output of the raidvchkdsp command with -v pool option:

Bsize: Displays the data block size of the pool in blocks (512 bytes).

Available(Bsize): Displays the available capacity for the volume data on the Copy-on-Write Snapshot pool in units of Bsize.

Capacity(Bsize): Displays the total capacity in the Copy-on-Write Snapshot pool in units of Bsize.

Example 8

Example of raidvchkdsp command with -v aou option and its output ("aou" (allocation on use) refers to dynamic provisioning):

[Display example]# raidvchkdsp -v aou -g AOUGroup PairVol Port# TID LU Seq# LDEV# Used(MB) LU_CAP(MB) U(%) T(%) PIDAOU AOU_001 CL2-D 2 7 62500 167 20050 1100000 10 70 1AOU AOU_002 CL2-D 2 10 62500 170 110000 1100000 10 70 1

Output of the raidvchkdsp command with the -v aou option:

Used(MB): Displays the usage size of the allocated block on this LUN. Range: 0 ≤ Used (MB) < LU_CAP(MB) + 42 MB


LU_CAP(MB): Displays the LUN capacity responded to the 'Readcapacity' command as SCSI interface.

LU_CAP(BLK): Displays the LUN capacity (in block/512 bytes) responded to the 'Readcapacity' command as SCSI interface.

U(%): Displays the usage rate of the allocated block on the Dynamic Provisioning pool containing this LU.

T(%): Displays the threshold rate being set to the Dynamic Provisioning pool as high water mark.

PID: Displays the Dynamic Provisioning pool ID assigned to this Dynamic Provisioning volume.

raidvchkscanThe raidvchkscan command displays the fibre port of the storage system, target ID, LDEV mapped for LUN# and MU#, and status of LDEV, regardless of the configuration definition file.

Note: This command is rejected with EX_ERPERM by connectivity checking between CCI and the RAID storage system.

Syntaxraidvchkscan { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -p <port> [hgrp] | -pd[g] <raw_device> | -s <seq#> | -t <target> | -l <lun> | [ -f[x] ] | -v <op> }


Option Description



-z or -zx Makes the raidvchkscan command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.





-p <port> [hgrp]

Specifies the port ID of the port to be scanned. Valid ports are CL1-A to CL1-R and CL2-A to CL2-R (excluding CL1-I, CL1-O, CL2-I, CL2-O). In addition, it is able to specify from CL3-a to CL3-r (except CL3-i, CL3-o), or CL4-a to CL4-r (except CL4-i, CL4-o) for the expanded port. The port is not case sensitive (for example, CL1-A= cl1-a= CL1-a= cl1-A, CL3-a= CL3-A= cl3-a= cl3-A). This option must be specified if '-find' or '-pd <raw_device>'option is not specified.Specify [hgrp] to display only the LDEVs mapped to a host group on a port.

-pd[g] <raw_device>

Specifies the raw device name. This option finds Seq# and port_name of the storage system to which the specified device can be connected, and scans the port of the storage system which corresponds with the unit ID that searches the unit ID from Seq#. This option must be specified if the '-find' option is not specified. If this option is specified, the following -s <seq#> option is invalid.-pdg: Shows a LUN on the host view by finding a host group.

-s <seq#> Used to specify the seq# (serial#) of the storage system when this option cannot specify the unit ID which is contained for '-p <port>' option. This option scans the port specified by '-p <port>' option of the storage system which corresponds with the unit ID that searches the unit ID from seq#. If this option is specified, then the unit ID which is contained in '-p <port>' option is invalid.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-t <target> Specifies a target ID (0 to 15) of the specified port. If this option is not specified, the command applies to all target IDs.

-l <lun> Specifies a LUN (0 to 7) of the specified target ID. If this option is not specified, the command applies to all LUNs. If this option is specified, the TID must also be specified.

-fx Displays the LDEV/STLBA/ENLBA number in hexadecimal notation.

Option Description


Returned values--

Error codes--

Examples

Example 1

Example of raidvchkscan command with -v cflag option

# raidvchkscan -p CL1-A -v cflagPORT# /ALPA/C TID# LU# Seq# Num LDEV# BR-W-E-E MR-W-B BR-W-B-Z SR-W-B-SCL1-A / ef/ 0 0 0 2332 1 0 D E B R D D D D E E E D E D DCL1-A / ef/ 0 0 1 2332 1 1 D E B R D D D D E E E D E D D

Output of the raidvchkscan command with -v cflag option:

BR-W-E-E: Displays the flags for checking regarding data block size.

R=E: Checking for data block size on read is enabled. R=D: Checking for data block size on read is disabled.

W=E: Checking for data block size on write is enabled. W=D: Checking for data block size on write is disabled.

-v [op] Specifies the following operation that displays each parameter for validation checking:cflag: Displays all flags for checking regarding data block validation for target vols.offset: Displays the range setting for data block size of Oracle I/O and a region on a target volume for validation checking.errcnt: Displays the statistical information counted as an error for each checking on the target volumes. Each statistical information counted as an error is cleared when the individual flag for validation checking is disabled.gflag: Displays the parameter for guarding on the specified target volumes. pool: This option displays the pool capacity and the usable capacity for the pool ID to which the LDEV belongs. This is needed to help the decision whether the restore operation is possible or not, because the pool capacity is consumed by the restore operation of the Copy-on-Write Snapshot. aou[b]: Displays the LUN capacity and usage rate for only Dynamic Provisioning volume mapped to the specified port, and displays the ID of the pool to which LDEV belongs. aoub: Displays the LUN capacity in blocks (512 bytes).

Option Description



E=L: Data block on read/write is interpreted as little endian format. E=B: Data block on read/write is interpreted as big endian format.

E=W: This shows the Warning that read/write is not rejected when validation error is detected. E=R: This shows the Reject that read/write is rejected when validation error is detected.

MR-W-B: Displays the flags for checking regarding CHK-F3 in the data block.




BR-W-B-Z: Displays the flags for checking regarding CHK-F2 in the data block.



B=E: Comparing for CHK-F2 in the data block is enabled. B=D: Comparing for CHK-F2 in the data block is disabled.

Z=E: The NON zero checking for CHK-F2 in the data block is enabled. Z=D: The NON zero checking for CHK-F2 in the data block is disabled.

SR-W-B-S: Displays the flags for checking regarding CHK-F1 in the data block.




S=E: Referring for CHK-F1 flag contained in the data block is enabled. S=D: Referring for CHK-F1 flag contained in the data block is disabled.

Example 2

Example of raidvchkscan command with -v offset option

# raidvchkscan -p CL1-A -v offsetPORT# /ALPA/C TID# LU# Seq# Num LDEV# Bsize STLBA ENLBA BNMCL1-A / ef/ 0 0 0 2332 1 0 1024 1 102400 9CL1-A / ef/ 0 0 1 2332 1 1 1024 1 102400 9


CL1-A / ef/ 0 0 2 2332 1 2 1024 1 102400 9CL1-A / ef/ 0 0 3 2332 1 3 1024 1 102400 9CL1-A / ef/ 0 0 4 2332 1 4 1024 1 102400 9

Output of the raidvchkscan command with -v offset option:

Bsize: Displays the data block size of Oracle I/O in bytes.

STLBA: Displays the Start of LBA on a target volume for checking in blocks (512 bytes).

ENLBA: Displays the End of LBA on a target volume for checking in blocks (512 bytes).

Note: If STLBA and ENLBA are both zero, this means to check all blocks.

BNM: Displays the number of bits for checking regarding CHK-F2 (in bits). If BNM is zero, this means the checking for CHK-F2 is disabled.

Example 3

Example of raidvchkscan command with -v errcnt option

# raidvchkscan -p CL1-A -v errcntPORT# /ALPA/C TID# LU# Seq# Num LDEV# CfEC MNEC SCEC BNECCL1-A / ef/ 0 0 0 2332 1 0 0 0 0 0CL1-A / ef/ 0 0 1 2332 1 1 0 0 0 0CL1-A / ef/ 0 0 2 2332 1 2 0 0 0 0CL1-A / ef/ 0 0 3 2332 1 3 0 0 0 0CL1-A / ef/ 0 0 4 2332 1 4 0 0 0 0

Output of the raidvchkscan command with -v errcnt option:

CfEC: Displays the error counter for checking of block size validation.

MNEC: Displays the error counter for checking of CHK-F3 validation.

SCEC: Displays the error counter for checking of CHK-F1 validation.

BNEC: Displays the error counter for checking of CHK-F2 validation.

Example 4

Example of raidvchkscan command with -v gflag option

# raidvchkscan -p CL1-A -v gflagPORT# /ALPA/C TID# LU# Seq# Num LDEV# GI-C-R-W-S PI-C-R-W-S R-TimeCL1-A / ef/ 0 0 0 2332 1 0 E E D D E E E D D E 365CL1-A / ef/ 0 0 1 2332 1 1 E E D D E E E D D E -



CL1-A / ef/ 0 0 2 2332 1 2 E E D D E E E D D E 0

Output of the raidvchkscan command with -v gflag option:

GI-C-R-W-S: Displays the flags for guarding as for the target volume.

I=E: Enabled for Inquiry command. I=D: Disabled for Inquiry command.

C=E: Enabled for Read Capacity command. C=D: Disabled for Read Capacity command.

R=E: Enabled for Read command. R=D: Disabled for Read command.

W=E: Enabled for Write command. W=D: Disabled for Write command.

S=E: Enabled for becoming the S-VOL. S=D: Disabled for becoming the S-VOL.

PI-C-R-W-S: Displays the permission flags that show whether each mode flag can be changed to enable or not.

I=E: 'I' flag can be changed to enable. I=D: 'I' flag cannot be changed to enable.

C=E: 'C' flag can be changed to enable. C=D: 'C' flag cannot be changed to enable.

R=E: 'R' flag can be changed to enable. R=D: 'R' flag cannot be changed to enable.

W=E: 'W' flag can be changed to enable. W=D: 'W' flag cannot be changed to enable.

S=E: 'S' flag can be changed to enable. S=D: 'S' flag cannot be changed to enable.

R-Time: Displays the retention time for write protect in days. The hyphen (-) shows that the retention time is infinite. The application knows whether the target volume is denied to change to writing enable by referring 'R-Time'.

Audit lock status is shown as the retention time plus 1000000. 'R-Time + 1000000' shows the retention time with Audit lock status.

Example 5

Example of raidvchkscan command with -v pool option

# raidvchkscan -v pool -p CL2-d-0PORT# /ALPA/C TID# LU# Seq# Num LDEV# Bsize Available CapacityCL2-D-0 /e4/ 0 2 0 62500 1 160 2048 100000 1000000000CL2-D-0 /e4/ 0 2 1 62500 1 161 2048 100000 1000000000

Output of the raidvchkscan command with -v pool option:

Bsize: Displays the data block size of the pool in blocks (512 bytes).


Available(Bsize): Displays the available capacity for the volume data on the Copy-on-Write Snapshot pool in units of Bsize.

Capacity(Bsize): Displays the total capacity in the Copy-on-Write Snapshot pool in units of Bsize.

Example 6

Example of raidvchkscan command with -v aou option ("aou" (allocation on use) refers to dynamic provisioning)

# raidvchkscan -v aou -p CL2-d-0PORT# /ALPA/C TID# LU# Seq# Num LDEV# Used(MB) LU_CAP(MB) U(%) T(%) PIDCL2-D-0 /e4/ 0 2 0 62500 1 160 20050 1100000 1 60 1CL2-D-0 /e4/ 0 2 1 62500 1 161 200500 1100000 18 60 2

Output of the raidvchkscan command with -v aou option:

Used(MB): Displays the usage size the allocated block on this LUN. Range: 0 ≤ Used (MB) < LU_CAP(MB) + 42MB

LU_CAP(MB): Displays the LUN capacity responded to the 'Readcapacity' command as SCSI interface.

LU_CAP(BLK): Displays the LUN capacity (in block/512 bytes) responded to the 'Readcapacity' command as SCSI interface.

U(%): Displays the usage rate of the allocated block on the Dynamic Provisioning pool containing this LU.

T(%): Displays the threshold rate being set to the Dynamic Provisioning pool as high water mark.

PID: Displays the Dynamic Provisioning pool ID assigned to this Dynamic Provisioning volume.

raidvchkscan for Universal ReplicatorThe raidvchkscan command supports the (-v jnl [t] [unit#]) option to find the journal volume list. It also displays any information for the journal volume.

Syntaxraidvchkscan { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -v jnl [t] [unit#] | [ -s <seq#>] | [ -f[x] ] }


Option Description




Returned values--

Error codes--

Examples

Example 1

Example of raidvchkscan command with -v jnl 0 option

# raidvchkscan -v jnl 0JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Nnm LDEV# 001 0 1 PJNN 4 21 43216fde 30 512345 62500 2 265 002 1 2 PJNF 4 95 3459fd43 52000 512345 62500 3 270 002 2 2 SJNS 4 95 3459fd43 52000 512345 62500 3 270 003 0 3 PJSN 4 0 - - 512345 62500 1 275 004 0 4 PJSF 4 45 1234f432 78 512345 62500 1 276 005 0 5 PJSE 0 0 - - 512345 62500 1 277 006 - - SMPL - - - - 512345 62500 1 278


-z or -zx Makes the raidvchkscan command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-s <seq#> Used to specify the seq# (serial#) of the storage system when this option cannot specify unitID which is contained for '-v jnl' option. If this option is specified, the unitID which is contained in '-v jnl' is invalid.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.


-v jn Displays information for the journal volume.

-v jnlt Displays the DOW, DPW, and APW time-out values for controlling the journal.

Option Description


007 0 6 SMPL 4 5 345678ef 66 512345 62500 1 278

Output of the raidvchkscan command with -v jnl 0 option:

JID: journal ID

MU: mirror descriptions on Universal Replicator

CTG: CT group ID

JNLS: Status of the journal:• SMPL: This means the journal volume which does not have a pair, or in

the state of deleting.• P(S)JNN: This means 'P(S) Journal Volume is in Normal status'.• P(S)JSN: This means 'P(S) Journal Volume is suspended in Normal

status'.• PJNF: This means 'P(S) Journal Volume is in Full status'.• P(S)JSF: This means 'P(S) Journal Volume is suspended in Full status'.• P(S)JSE: This means 'P(S) Journal Volume is suspended by an error

(including link failures)'.• AP: Displays the following two conditions (status) according to the pair

status.

Shows the number of active paths on the initiator port in Universal Replicator links. 'Unknown' is shown as '-'.

AM: The activity monitor that detects whether or not there is a request for data from the initiator at regular intervals. If AM detects a time-out, the P-JNL state is changed from P-JNN to PJSE.

Note: The same path information is used for AP for three commands (pairvolchk, pairdisplay, raidvchkscan). The differential is that pairvolchk and pairdisplay are to show a special meaning with SSUS(SSWS) state.

Q-Marker: Displays the sequence # of the journal ID, called the Q-marker. For P-JNL, Q-Marker shows the latest sequence # on the P-JNL volume. For S-JNL, the Q-Marker shows the latest sequence # of the cache(DFW).

Q-CNT: Displays the number of remaining Q-Markers within each journal volume.



U(%): Displays the usage rate of the journal data.

D-SZ: Displays the capacity for the journal data on the journal volume.

Seq#: Displays the serial number of the RAID storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Num: Displays the number of LDEVs configured the journal volume.

LDEV#: Displays the first number of the LDEV that is configured for the journal volume. Using a combination of JNLS status and other information, the application knows the following detail state.

The following table lists information about the different journal volume statuses. QCNT=0 indicates that the number of remaining Q-Markers is '0'. The letter 'N' indicates a non-zero.

Table 2-12 Detailed Status of the Journal Volume

Figure 2-21 Example of Q-Marker and Q-CNT

JNLS Other Information Description

P-JNL S-JNL QCNT AP

SMPL 0 - Configured as journal volume, but NOT pair

N - Deleting the journal volume

PJNN(PJNS)

SJNN(SJNS)

0 - Normal state of the journal volume without data

PJNN(PJNS)

- N - Normal state of the journal volume with data

- SJNN(SJNS)

N N Normal state of the journal volume with data

0 Still normal state of the journal volume at Link failure

PJSN SJSN 0 - Suspended journal volume via operation

N - Suspending the journal volume

PJNF - N - High water mark state


Example 2

Example of raidvchkscan command with -v jnlt option

# raidvchkscan -v jnltJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW001 0 1 PJNN 4 21 43216fde 30 512345 63528 20 300 40002 1 2 PJNF 4 95 3459fd43 52000 512345 63528 20 300 40003 0 3 PJSN 4 0 - - 512345 63528 20 300 40

Output of the raidvchkscan command with -v jnlt option:

DOW: Data Overflow Watch' timer (in seconds) setting per the Journal.

PBW: Path Blockade Watch timer setting (in seconds) per the Journal. If the setting is more than 3600 seconds, it displays 6000 seconds.

APW: This shows 'Active Path Watch' timer (in seconds) for detecting Link failure.

raidvchkscan for Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning Pool

The raidvchkscan command supports the option (-v pid[a] [unit#]) to find the Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning pool settings via SVP, and displays information for the Thin Image, Copy-on-Write Snapshot, or Dynamic Provisioning pool.

Syntaxraidvchkscan { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -v pid[a][s] [unit#] | [ -s <seq#>] | [ -f[x ] | }

PJSF SJSF 0 - Suspended journal volume due to full journal

N - Suspending the journal volume due to full journal

PJSE - 0 - Suspended journal volume due to failure/Link failure

N - Suspending the journal volume due to failure/Link failure

- SJSE 0 N Suspended journal volume due to failure

0 Suspended journal volume due to Link failure

N N Suspending the journal volume due to failure

0 Suspending the journal volume due to Link failure

JNLS Other Information Description

P-JNL S-JNL QCNT AP




Returned values--

Error codes--

ExamplesExample of raidvchkscan command example with -v pid option

# raidvchkscan -v pid 0PID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%)001 POLN 10 330 10000000 1000000000 62500 2 265 80002 POLF 95 9900 100000 1000000000 62500 3 270 70003 POLS 100 10000 100 1000000000 62500 1 275 70004 POLE 0 0 0 0 62500 0 0 80

Output of the raidvchkscan command with -v pid option:

Option Description



-z or -zx Makes the raidvchkdsp command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-s <seq#> Used to specify the Seq# (serial#) of the storage system when this option cannot specify unitID which is contained for '-v jnl[a]' option. If this option is specified, the unitID which is contained in '-v jnl[a]' is invalid.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.


-v pid[s] Displays information for the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

-v pid[a] Displays information for the Dynamic Provisioning pool.


PID: Displays the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool ID.

POLS: Displays the following status in the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

POLN = 'Pool Normal'

POLF = 'Pool Full'

POLS = 'Pool Suspend'

POLE = 'Pool failure'. In this state, information for the pool has no meaning and is displayed as '0'.

U(%): Displays the usage rate of the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

SSCNT: Displays the number of Thin Images/Copy-on-Write Snapshot volume in Thin Image/Copy-on-Write Snapshot pool or the total number of Dynamic Provisioning volumes mapped in this Dynamic Provisioning pool.

Available(MB): Displays the available capacity for the volume data on the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

Capacity(MB): Displays the total capacity in the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

Seq#: Displays the serial number of the RAID storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Num: Displays the number of LDEVs configured the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

LDEV#: Displays the first number of LDEV configured the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool.

H(%): Displays the threshold rate being set to the Thin Image/Copy-on-Write Snapshot/Dynamic Provisioning pool as High water mark. 'Unknown' is shown as '-'.

Example of raidvchkscan command example with -v pida option

# raidvchkscan -v pida 0PID POLS U(%) AV_CAP(MB) TP_CAP(MB) W(%) H(%) Num LDEV# LCNT TL_CAP(MB)001 POLN 10 45000000 50000000 50 80 2 265 33 65000000 002 POLF 95 10000 100000000 50 80 3 270 900 100000000 004 POLN 0 10000000 100000000 80 90 2 280 0 0

Output of the raidvchkscan command with -v pida option:

PID: Displays the Dynamic Provisioning pool ID.

POLS: Displays the following status of the Dynamic Provisioning pool:• POLN = 'Pool Normal'



• POLF = 'Pool Full' • POLS = 'Pool Suspend'• POLE = 'Pool failure'. In this state, information for the pool has no

meaning and is displayed as '0'.

U(%): Displays the usage rate of the Dynamic Provisioning pool.

AV_CAP(MB): Displays the available capacity for the Dynamic Provisioning volumes mapped to this pool.

TP_CAP(MB): Displays the total capacity of the Dynamic Provisioning pool.

W(%): Displays the threshold value for 'WARNING' set for this Dynamic Provisioning pool.

H(%): Displays the threshold rate set for the Dynamic Provisioning pool as high water mark.

Num: Displays the number of LDEVs configured the Dynamic Provisioning pool.

LDEV#: Displays the first number of LDEV configured the Dynamic Provisioning pool.

LCNT: Displays the total number of Dynamic Provisioning volumes mapped to this Dynamic Provisioning pool.

TL_CAP(MB): Displays the total capacity of all Dynamic Provisioning volumes mapped to this Dynamic Provisioning pool.

horcmstartThe horcmstart command is a script that starts HORCM. This script also sets the environment variables for HORCM as needed (for example, HORCM_CONF, HORCM_LOG, HORCM_LOGS).

Syntaxhorcmstart.sh { inst ... } (UNIX systems)horcmstart.exe { inst ... } (Windows systems)



Option Description

inst Specifies the HORCM instance number (range= from 0 to 2047). When this option is specified, the horcmstart shell script sets the environment variables (HORCMINST, HORCM_CONF, HORCM_LOG, HORCM_LOGS) corresponding to the instance number, and starts the specified HORCM instance. (Environment variables set by the user become invalid.) When this option is not specified, the horcmstart shell script starts 1 HORCM and uses the environment variables set by the user. If you have designated full environment variables, use horcmstart.sh without any arguments. If you did not designate environment variables (HORCM_CONF, HORCM_LOG, HORCM_LOGS), then this shell script sets the environment variables as follows:For UNIX-based platforms:If HORCMINST is specified:HORCM_CONF = /etc/horcm*.conf (* is instance number)HORCM_LOG = /HORCM/log*/curlog HORCM_LOGS = /HORCM/log*/tmplogIf HORCMINST is not specified:HORCM_CONF = /etc/horcm.confHORCM_LOG = /HORCM/log/curlogHORCM_LOGS = /HORCM/log/tmplogFor Windows platform:If HORCMINST is specified:HORCM_CONF = %windir%\horcm*.conf (* is the instance number)HORCM_LOG = \HORCM\log*\curlog HORCM_LOGS = \HORCM\log*\tmplogIf HORCMINST is not specified:HORCM_CONF = %windir%\horcm.confHORCM_LOG = \HORCM\log\curlogHORCM_LOGS = \HORCM\log\tmplog[environmental variable]The HORCM_LOGS environment variable is used when specifying the log file directory for automatic storing. When HORCM starts up, the log files created in the operation are stored automatically in the HORCM_LOGS directory. This log directory must give an equality class with HORCM_LOGHORCMSTART_WAIT (for waiting the CCI instance with start-up). Horcmgr does fork/exec() horcmd_XX as daemon process, and verifies/waits until HORCM become ready state. The timeout is used for only avoiding infinite loop, currently the default time is 200 sec in consideration of maximum LDEV. However, it may be needed to change the default timeout value for starting HORCM under high-loading of the server, or the remote command device. In such a case, this environmental variable is used when changing a timeout value (in seconds) from the current default value (200 sec), this value must be specified more than 5 seconds and multiple of 5 seconds. For example, setting 500 sec:HORCMSTART_WAIT=500 Export HORCMSTART_WAIT

For OpenVMS platform: OpenVMS needs to make the Detached LOGINOUT.EXE Process as a JOB in the background by using the 'RUN /DETACHED' command. For details see Requirements and restrictions for OpenVMS (item 4) in the Installation and Configuration Guide.


horcmshutdownThe horcmshutdown command is a script for stopping HORCM.

Syntaxhorcmshutdown.sh {inst...} (UNIX systems)horcmshutdown.exe {inst...} (Windows systems)


horcctlThe HORCM software have logs that identify the cause of software and/or hardware errors as well as a tracing function for investigating such errors. The location of the log files depends on the user's command execution environment and the HORCM execution environment. The command trace file and core file reside together under the directory specified in the HORCM execution environment.

The horcctl command can be used for both maintenance and troubleshooting. The horcctl command allows you to change and display the internal trace control parameters (for example, level, type, buffer size) of the HORC Manager (CCI) software. If a new value for a parameter is not specified, the current trace control parameter is displayed.

Caution: Do not change the trace level unless directed to do so by a Hitachi Data Systems representative. Level 4 is the normal trace level setting. Levels 0-3 are for troubleshooting. Setting a trace level other than 4 may impact problem resolution. If you request a change of the trace level using the horcctl -l <level> command, a warning message appears, and this command enters interactive mode.

Option Description

inst Specifies the HORCM (CCI) instance number (range= from 0 to 2047). When this option is specified, the command stops the specified HORCM instance. When this option is not specified, the command refers to the instance (environment variable HORCMINST) of the execution environment of this shell script and stops the following the HORCM instance.When HORCMINST is specified, this command stops the HORCM instance of the execution environment of this shell script.When HORCMINST is not specified, this command stops the HORCM having no instance setting.

Caution: After direction of stopping HORCM instance, this command returns a response just before stopping HORCM instance. Thus to return the response of this command, it does not mean HORCM instance disappeared.



Syntaxhorcctl { -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -d | -c | -l <level> | -b <y/n> | -s <size(KB)> | -t <type> | -S | -D[I] | -C | [-u <-unitid> | -ND | -NC | -g <group> }


Option Description



-z or -zx Makes the horcctl command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.



-d Interprets the control options following this option (-l <level>, -b <y/n>, -s <size(KB)>, and -t <type>) as the parameters of the CCI commands.

-c Interprets the control options following this option (-l <level>, -b <y/n> and -t <type>) as the parameters of the HORC Manager (HORCM).

-l <level> Sets the trace level (range = 0 to 15). If a negative value is specified, the trace mode is canceled. A negative value 'n' must be specified as '--n'.Caution: Do not change the trace level unless directed to do so by a Hitachi Data Systems representative. Level 4 is the normal trace level setting. Levels 0-3 are for troubleshooting. Setting a trace level other than 4 may impact problem resolution. If you request a change of the trace level using the horcctl -l <level> command, a warning message appears, and this command enters interactive mode.

-b <y/n> Sets the trace writing mode: Y = buffer mode, N = synchronous mode.

-t <type> Sets the trace type (range = 0 to 511). When this option is used, only traces of the specified type are output. One or more values can be specified.

-s <size(KB)>

Sets the trace buffer size in increments of 1024 bytes (default = 1 MB).

-S Shuts down HORCM.

-D Displays the command device name currently used by HORCM. If the command device is blocked due to online maintenance (microcode replacement) of the storage system, you can check the command device name in advance using this option.


horctakeoffThis is a scripted command for executing several HORC operation commands combined. It checks the volume attribute (optionally specified) and decides a takeover action. The horctakeoff operation is defined to change from 3DC multi-target to 3DC multi-hop with the state of running APP, after that the horctakeover command is able to configure 3DC multi-target on the remote site without stopping the APP. The granularity of either a logical volume or volume group can be specified with this command.

Syntaxhorctakeoff | -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#] | -g[s] <group> | -d[s] <pair Vol> | -d[g][s] <raw_device> [MU#] | -d[g][s] <seq#> <LDEV#> [MU#] | -jp <id> | -js <id> | [-t <timeout> ]| -nomsg }

-c Changes the command device name being used by HORCM and displays the new command device name. If the command device is blocked due to online maintenance (microcode replacement) of the storage system, you can change the command device in advance using this option.Note: horcctl -D -C command designates a protection mode command device by adding '*' to the device file name as follows: HP-UX example with command device security: # horcctl -DCurrent control device = /dev/rdsk/c0t0d0*'horcctl -DI' command shows the number of CCI instances of when HORCM has being started as follows: HP-UX example without command device security: # horcctl -DI Current control device = /dev/rdsk/c0t0d0 AI = 14 TI = 0 CI = 1 whereAI : NUM of actual instances in useTI : NUM of temporary instances in RAIDCI : NUM of instances using current (own) instance

-u <unitid> Used when specifying the unit ID of a command device as the target. This option is effective when the -D or -C option is specified. If this option is not specified, the unit ID is 0.

-ND -g <group>

Displays the network address and port name being used by HORCM. The -g <group> option is used when specifying the group name defined in the configuration definition file.

-NC -g <group>

Changes the network address and port name being used by HORCM and displays the new network address name. The -g <group> option specifies the group name defined in the configuration definition file.

Option Description




Option Description



-z or -zx Makes the raidvchkdsp command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shutdown, interactive mode terminates.OpenVMS cannot use the -zx option.



-g[s] <group> Specifies a group name (defined in the configuration definition file). The command is executed for the specified group unless the -d <pair Vol> option shown below is specified.

-d[s] <pair Vol> Specifies a logical (named) volume (defined in the configuration definition file). When this option is specified, the command is executed for the specified paired logical volume.

-d[g][s] <raw_device> [MU#]

Searches the configuration definition file (local instance) for a volume that matches the specified raw device. If a volume is found, the command is executed on the paired volume (-d) or group (-dg). This option is effective without specification of the '-g <group>' option. If the specified raw_device is listed in multiple device groups, this applies to the first one encountered.

-d[g][s] <seq#> <LDEV#> [MU#]

Searches the configuration definition file (local instance) for a volume that matches the specified sequence # and LDEV. If a volume is found, the command is executed on the paired logical volume (-d) or group (-dg). This option is effective without specification of the '-g <group>' option. If the specified LDEV is listed in multiple device groups, this applies to the first one encountered. <seq#> <LDEV#> can be specified in a hexadecimal (by addition of '0x') or decimal.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-jp <id> (HORC/UR only)

Horctakeoff command can change 3DC configuration from 3DC multi-target to 3DC multi-hop. To create a 3DC multi-hop (TC_Sync to TC_Sync/UR_PVOL to UR), you must specify a journal ID for UR_PVOL. So this option is used for that purpose. If this option is not specified, a journal ID for UR_PVOL used for 3DC multi-target is inherited automatically.

-js <id>(HORC/UR only)

Horctakeoff command can be changed 3DC configuration from 3DC multi-target to 3DC multi-hop. To create a 3DC multi-hop (TC_Sync to TC_Sync/UR to UR_SVOL), you must specify a journal ID for UR_SVOL. So this option is used for that purpose. If this option is not specified, a journal ID for UR_SVOL used with 3DC multi-target is inherited automatically. The CTGID is also inherited automatically for the internal paircreate command.


Returned valuesThe horctakeoff command sets the following returned values during exit allowing you to check the execution results.

Normal termination: 0

Abnormal termination: The horctakeoff command returns the following error codes as well as generic error.

Error codesUnrecoverable error should have been done without re-execute by handling of an error code. If the command failed, then the detailed status is logged in CCI command log ($HORCC_LOG), even though the user script has no error handling.

Examples

Example 1

horctakeoff command on L1 local site

-t <timeout> Specifies the maximum time to wait for the Sync_PVOL to Sync_SVOL delta data resynchronizing operation. Used for the internal pairresync command with the time-out period in seconds. If this option is not specified, the default timeout value (7200 sec) is used.

-noms Suppresses messages when this command is executed from a user program. This option must be specified at the beginning of the command arguments.

Option Description

Category Error Code Error Message Value


EX_ENQVOL Unmatched volume status within the group 236

EX_INCSTG Inconsistent status in group 229

EX_EVOLCE Pair Volume combination error 235

EX_VOLCRE Local and Remote Volume currency error 223

Timer(Recoverable)

EX_EWSTOT Timeout waiting for specified status 233



# horctakeoff -g G1 -gs G2horctakeoff : 'pairsplit -g G1 -S -FHORC 2' is in progresshorctakeoff : 'pairsplit -g G1' is in progresshorctakeoff : 'pairsplit -g G2 -S' is in progresshorctakeoff : 'paircreate -g G1 -gs G2 -FHORC 2 -nocopy -f async -jp 0 -js 1' is in progresshorctakeoff : 'pairsplit -g G1 -FHORC 2' is in progresshorctakeoff : 'pairresync -g G1' is in progresshorctakeoff : 'pairresync -g G1 -FHORC 2' is in progresshorctakeoff : horctakeoff done

Example 2

horctakeoff command on L2 local site

# horctakeoff -g G1 -gs G3horctakeoff : 'pairsplit -g G1 -S -FHORC 1' is in progress.horctakeoff : 'pairsplit -g G1' is in progress.horctakeoff : 'pairsplit -g G3 -S' is in progress.horctakeoff : 'paircreate -g G1 -gs G3 -FHORC 1 -nocopy -f async -jp 0 -js 1' is in progress.horctakeoff : 'pairsplit -g G1 -FHORC 1' is in progress.horctakeoff : 'pairresync -g G1' is in progress.horctakeoff : 'pairresync -g G1 -FHORC 1' is in progress.horctakeoff : horctakeoff done.

Example 3

horctakeoff command on L1 remote site

# horctakeoff -g G1 -gs G2horctakeoff : 'pairsplit -g G2 -S' is in progress.horctakeoff : 'pairsplit -g G1' is in progress.horctakeoff : 'pairsplit -g G1 -FHORC 2 -S' is in progress.


horctakeoff : 'paircreate -g G2 -vl -nocopy -f async -jp 0 -js 1' is in progress.horctakeoff : 'pairsplit -g G2' is in progress.horctakeoff : 'pairresync -g G1' is in progress.horctakeoff : 'pairresync -g G2' is in progress.horctakeoff : horctakeoff done.

Example 4

horctakeoff command on L2 remote site

# horctakeoff -g G1 -gs G3horctakeoff : 'pairsplit -g G3 -S' is in progress.horctakeoff : 'pairsplit -g G1' is in progress.horctakeoff : 'pairsplit -g G1 -FHORC 1 -S' is in progress.horctakeoff : 'paircreate -g G3 -vl -nocopy -f async -jp 0 -js 1' is in progress.horctakeoff : 'pairsplit -g G3' is in progress.horctakeoff : 'pairresync -g G1' is in progress.horctakeoff : 'pairresync -g G3' is in progress.horctakeoff : horctakeoff done.

pairsyncwaitThe pairsyncwait command is used to confirm data consistency between the TrueCopy Async/Universal Replicator P-VOL and S-VOL by confirming that required writing was stored in the DFW area of RCU, and confirming whether the last writing just before this command reached the RCU DFW area.

This command gets the latest sequence # of the MCU sidefile (P-VOL latest sequence # within the CT group ID) and the sequence # of the RCU DFW within the CT group ID corresponding to the <group> or <raw_device> specified by pairsyncwait, and compares the MCU with the RCU sequence # at that time and at regular intervals. If the RCU sequence # is over the value of the MCU sequence # within the term specified by pairsysncwait, this command displays the return code 0 with the meaning of completion of synchronization. The -nowait option shows the latest sequence # (Q-marker) of MCU PVol and CTGID. The marker is a 10-digit hexadecimal number.

When a client issues the pairsyncwait command, this command is placed on the queue buffer for waiting in the HORCM daemon as a command request. HORCM gets the latest sequence # from the MCU sidefile and the



sequence # whose block was transferred and stored in the DFW area of RCU with data consistency, and compares the latest sequence # of MCU sidefile with the sequence # of the RCU DFW area within the term. HORCM replies return codes to this command, when the write of MCU sidefile was stored in RCU DFW area.

Using this function, a client can confirm that a commit() has reached the remote site, and also the backup utility on a remote site can split the cascading ShadowImage volumes (TrueCopy Async/Universal Replicator to TrueCopy Async/ShadowImage/Universal Replicator) without splitting TrueCopy Async/Universal Replicator.

More robust systems need to confirm the data consistency between the TrueCopy Async/Universal Replicator P-VOL and S-VOL. In DB operations (for example, Oracle), the commit() of DB transaction (see the following figure) is needed to confirm that a last writing for the commit() on a local site reached the remote site by using CCI-unique API command.

Syntaxpairsyncwait{ -h | -q | -z | -I[H][M][instance#] or I[TC][SI][instance#]| -g <group> | -d <pair Vol>| -d[g] <raw_device> [MU#] | -d[g] <seq#> <LDEV#> [MU#]| -m <marker> | -t <timeout> | -nowait | -nomsg | -fq }

Figure 2-22 Synchronization for TrueCopy Async/Universal Replicator



Option Description



-z or -zx Makes the pairsyncwait command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.OpenVMS cannot use the -zx option.









-m <marker> Specifies the sequence # of MCU P-VOL in 10-digit hexadecimal, called the Q-marker. If the application gets Q-marker as the result of execution of pairsyncwait because of timeout or '-nowait', the application can reconfirm the completion of Async transfer by using pairsysncwait with Q-marker. If the application does not specify Q-marker, CCI uses the latest sequence # when CCI receives pairsysncwait. It is also possible to wait for the completion from S-VOL side with this option.Q-Marker format: iissssssss, where ii = regeneration # of pair volume, and ssssssss = latest sequence # on the side of P-VOL.

-t <timeout> Specifies the timeout value to wait for the completion of RCU DFW area. The unit is 100 ms. MCU gets the latest sequence # from RCU at regular interval.



Returned valuesThe pairsyncwait command sets the following returned values during exit allowing you to check the execution results.

-nowait Gets the latest sequence # of MCU PVol and CTGID without waiting. When this option is specified, the latest sequence # of MCU PVol is reported immediately, and -t <timeout>option is ignored.

-nomsg Suppresses messages to be displayed when this command is executed from a user program. This option must be specified at the beginning of the command arguments.

-fq Displays the number of remaining Q-Markers within the CT group by adding 'QM-Cnt' to the last column. 'QM-Cnt' is shown as follows:• When specifying '-nowait -fq''QM-Cnt' is shown as the number of remaining Q-Marker at this time within CT group.• When specifying '-nowait -m <marker> -fq''QM-Cnt' is shown as the number of remaining Q-Marker from the specified <marker> within CT group.• When specifying 'TIMEOUT' without '-nowait''QM-Cnt' is shown as the number of remaining Q-Marker at this timeout within CT group.'QM-Cnt' is shown as '-', if the status for Q-Marker is invalid (that is, status is 'BROKEN' or 'CHANGED'). Example:# pairsyncwait -g oradb -nowait -fqUnitID CTGID Q-Marker Status Q-Num QM-Cnt 0 3 01003408ef NOWAIT 2 120# pairsyncwait -g oradb -nowait -m 01003408e0 -fqUnitID CTGID Q-Marker Status Q-Num QM-Cnt 0 3 01003408e0 NOWAIT 2 105# pairsyncwait -g oradb -t 50 -fqUnitID CTGID Q-Marker Status Q-Num QM-Cnt 0 3 01003408ef TIMEOUT 2 5

Restriction Specified <group> volume must be PVol with status PAIR. Other cases reply with error (EX_INVVOL). It is possible to issue pairsysncwait from S-VOL side with -m <marker>.

Option Description

Condition Returned Value

When the -nowait option is specified

• Normal termination: 0: The status is NOWAIT.• Abnormal termination: other than 0 to 127, refer to the error

code for error details.



ExamplesThe following shows examples of the pairsyncwait command with and without the -nowait option.

# pairsyncwait -g oradb -nowait <=-nowait is specified.UnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef NOWAIT 2# pairsyncwait -g oradb -t 100 <=-nowait is not specified.UnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef DONE 2# pairsyncwait -g oradb -t 1UnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef TIMEOUT 3# pairsyncwait -g oradb -t 100 -m 01003408efUnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef DONE 0# pairsyncwait -g oradb -t 100UnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef BROKEN 0# pairsyncwait -g oradb -t 100 -m 01003408efUnitID CTGID Q-Marker Status Q-Num 0 3 01003408ef CHANGED 0 -> '01003408ef' is invalid because the pair volume is not already resynchronized.

Output of the pairsyncwait command:

UnitID: Unit ID in the case of multiple storage system connection

CTGID: CTGID within Unit ID

Q-Marker: The latest sequence # of MCU PVol (Marker) when the command is received.

When the -nowait option is not specified

• Normal termination:0: The status is DONE (completion of synchronization).1: The status is TIMEOUT (timeout).2: The status is BROKEN (Q-marker synchronized process is rejected).3: The status is CHANGED (Q-marker is invalid due to resynchronize).• Abnormal termination: other than 0 to 127, refer to the error

codes for error details.

Condition Returned Value





222



Status: The status after the execution of command.

Q-Num: The number of process queues to wait for synchronization within the CTGID.

QM-Cnt: The number of remaining Q-Markers within CT group of the Unit. TrueCopy Async/Universal Replicator sends a token called 'dummy recordset' at regular intervals, therefore QM-Cnt always shows '2' or '3' even if host has NO writing.

Arithmetic expression for determining the remaining data in a CT group:

Remaining data in CT group = sidefile capacity × sidefile percentage ÷ 100

Sidefile percentage is the rate showed to '%' column with 'PAIR' state by Pairdisplay command. Sidefile capacity is the capacity within 30% to 70% of the cache setting as the sidefile.

Arithmetic expression for determining the average data per Q-Marker in a CT group:

Data per Q-Marker = Remaining data in CT group ÷ QM-Cnt

3

Subcommands 3–1Hitachi Command Control Interface Command Reference

Subcommands

This chapter provides the specifications for the CCI subcommands.

□ Windows subcommands

□ Environment variable subcommands


3–2 Subcommands

Windows subcommandsCCI provides subcommands for the Windows platform that are executed as an option of another command. When you specify a subcommand as the only option of a command, you do not need to start HORCM. If another option of the command and the subcommand are specified on the same command line,place the other option after the subcommand.

The Windows subcommands are:• findcmddev on page 3-2• drivescan on page 3-3• portscan on page 3-4• sync, syncd on page 3-5• mount on page 3-7• umount, umountd on page 3-9

findcmddevThe findcmddev subcommand searches for command devices within the specified range of disk drive numbers. If it is found, the command device appears in the same format as in the configuration definition file. This subcommand is used when the command device name is not known and when the HORCM is not started.

Caution: The findcmddev subcommand must be used when HORCM is running.

Note: The findcmddev subcommand searches for the physical and logical drives associated with the command device. If the command device is indicated as a logical drive in addition to a physical drive, then a drive letter is assigned to the command device. You must delete the drive letter assigned to the command device to prevent utilization by general users.

The 'Volume{GUID}' must be made by setting a partition using the disk management. Do not format it (no file system). In a SAN environment, the physical drive number might be changed on every reboot. For this case, use the Volume (GUID) that keeps as the same name.

Syntax

-x findcmddev drive#(0-N)

Argument

drive#(0-N): Specifies the range of disk drive numbers on the Windows system.

Example

The following shows an example of the findcmddev subcommand used as an option of the raidscan command and its output. This example searches for command devices in the range of disk drive numbers 0 through 20.


D:\HORCM\etc> raidscan -x findcmddev hdisk0, 20cmddev of Ser# 62496 = \\.\PhysicalDrive0cmddev of Ser# 62496 = \\.\E:cmddev of Ser# 62496 = \\.\Volume{b9b31c79-240a-11d5-a37f-00c00d003b1e}

drivescanThe drivescan subcommand displays the relationship between the disk numbers assigned by the Windows system and the LDEVs on the RAID storage system, and also displays attribute and status information for each LDEV.

Syntax

-x drivescan drive#(0-N)

Argument

drive#(0-N): Specifies the range of data drive numbers on the Windows system.

Example

The following shows an example of the drivescan subcommand used as an option of the raidscan command and its output. This example displays the devices for the range of disk drive numbers from 0 to 20.

raidscan -x drivescan harddisk0,20Harddisk 0..Port[1] PhId[0] TId[0] Lun[0] [HITACHI] [DK328H-43WS]Harddisk 1..Port[2] PhId[4] TId[29] Lun[0] [HITACHI] [OPEN-3] Port[CL1-J] Ser#[ 30053] LDEV#[ 9(0x009)] HORC=P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3Harddisk 2..Port[ 2] PhId[ 4] TId[29] Lun[ 1] [HITACHI] [OPEN-3] Port[CL1-J] Ser#[ 30053] LDEV#[ 10(0x00A)] HORC=S-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0004 CTGID = 3Harddisk 3..Port[2] PhId[4] TId[29] Lun[ 6] [HITACHI] [OPEN-3-CM] Port[CL1-J] Ser#[ 30053] LDEV#[ 15(0x00F)]

Output of the drivescan subcommand:

Harddisk #: Shows the data drive recognized by the Windows system.

Port: Shows the port number on the device adapter recognized by the Windows system.

Phid: Shows the bus number on the device adapter port recognized by Windows system.

Tid: Shows the target ID of the data drive(s) connected to device adaptor port. For the detail of fibre-to-SCSI address conversion, see the CCI Installation and Configuration Guide.

LUN: Shows the LU number of the data drive connected to device adaptor port.


3–4 Subcommands

Port[CLX-Y]: Shows the port number on the storage system.

Ser#: Shows the production number (serial number) of the storage system.

LDEV#: Shows the LDEV ID (hexadecimal) of the specified volume.

HORC: Shows the TrueCopy attribute (P-VOL, S-VOL, SMPL) of the specified volume.

HOMRCF: Shows the ShadowImage or Copy-on-Write Snapshot attribute (P-VOL, S-VOL, or SMPL) and MU number (0-2) of the specified volume.

RAIDX[Group]: Shows the physical location (frame number-parity group number) of the specified volume and the RAID level of this parity group.

SSID: Shows the SSID (hexadecimal) of the specified volume. The Unified Storage VM does not support SSID but displays the specified value.

CTGID (TrueCopy Async and Universal Replicator only): Shows the consistency group ID of specified volume.

portscanThe portscan subcommand displays the devices on the specified port(s).

Syntax

-x portscan port#(0-N)

Argument

port#(0-N): Specifies the range of port numbers on the Windows system.

Example

The following shows an example of the portscan subcommand used as an option of the raidscan command and its output. This example displays the devices for the range of ports from 0 to 20.

raidscan -x portscan port0,20PORT[ 0] IID [ 7] SCSI Devices PhId[ 0] TId[ 3] Lun[ 0] [MATSHIT] [CD-ROM CR-508]...Claimed PhId[ 0] TId[ 4] Lun[ 0] [HP ] [C1537A ]...ClaimedPORT[ 1] IID [ 7] SCSI Devices PhId[ 0] TId[ 0] Lun[ 0] [HITACHI] [DK328H-43WS ]...ClaimedPORT[ 2] IID [ 7] SCSI Devices PhId[ 0] TId[ 5] Lun[ 0] [HITACHI] [OPEN-3 ]...Claimed PhId[ 0] TId[ 5] Lun[ 1] [HITACHI] [OPEN-3 ]...Claimed PhId[ 0] TId[ 5] Lun[ 2] [HITACHI] [OPEN-3 ]...Claimed PhId[ 0] TId[ 6] Lun[ 0] [HITACHI] [3390-3A ]...Claimed

Note: This example displays the devices for the range of ports from 0 to 20.

Output of the portscan subcommand:

Port: Shows the port number on the device adapter recognized by the Windows system

IID: Shows the initiator ID on the specified device adapter port


Phid: Shows the BUS number on the specified device adapter port

Tid: Shows the target ID of the data drive(s) connected to device adapter port.

LUN: Shows the LU number of each data drive connected to device adapter port. This item shows LDEV# of the partner who becomes a pair in or among the RAID storage systems.

sync, syncdThe sync (synchronization) subcommand sends unwritten data remaining on the Windows server to the specified device(s) to synchronize the pair(s) before the CCI command is executed. The syncd (synchronization delay) subcommand waits for the delayed IO for dismount after issued 'sync'.

Syntax

-x sync[d] A: B: C: ... -x sync[d] all-x sync[d] drive#(0-N)-x sync[d] Volume#(0-N) ...-x sync[d] D:\Directory or \Directory pattern...

Arguments

Argument Description

A: B: C: [\directory or \Directory pattern]

Specifies the logical drive that you want to synchronize. Data is flushed into the specified logical drive and the physical drive corresponding to the logical drive. If the specified logical drive has the directory mount volumes then SYNC is executed to all of the volumes on the logical drive as shown below:pairsplit -x sync D: [SYNC] D: HarddiskVolume2 [SYNC] D:\hd1 HarddiskVolume8 [SYNC] D:\hd2 HarddiskVolume9

[\directory or \Directory pattern] is used to find the directory mount point on the logical drive. If the directory is specified, then SYNC does execute to a directory mounted volume only.pairsplit -x sync D:\hd1 [SYNC] D:\hd1 HarddiskVolume8

If the directory pattern is specified, then SYNC does execute to any directory mounted volumes identified to '\directory pattern'.pairsplit -x sync D:\h [SYNC] D:\hd1 HarddiskVolume8 [SYNC] D:\hd2 HarddiskVolume9


3–6 Subcommands

Examples

The following examples show the sync subcommand used as an option of the pairsplit command.

sync subcommand with pairsplit

For the following example, the data remaining on logical drives C: and D: is written to disk, all pairs in the specified group are split (status = PSUS), and read/write access is enabled for all S-VOLs in the specified group.

pairsplit -x sync C: D: -g oradb -rw

sync subcommand with pairsplit -S

For the following example, the data remaining on physical devices harddisk2 and harddisk3 is written to disk, all pairs in the specified group are deleted (status = SMPL), which enables read/write access for all secondary volumes.

pairsplit -x sync hdisk2 hdisk3 -g oradb -S

Note: The sync subcommand has the following behavior on any conditions:

If the logical drives designated as the objects of the sync command are not opened to any applications, then sync flushes the system buffer to a drive and makes the dismount state for this drive.

If the logical drives designated as the objects of the sync command are already opened to any applications, then sync only flushes the system buffer to a drive.

all Synchronizes all logical drives and the physical drives corresponding to the logical drives assuming that they are on the data drives. The logical drive on which the CCI software is installed and the logical drive containing the Windows directory are excluded. If the logical drive has the directory mount volumes then SYNC is executed to all volumes on the logical drive as shown below:pairsplit -x sync all [SYNC] C: HarddiskVolume1 [SYNC] D:\hd1 HarddiskVolume8 [SYNC] D:\hd2 HarddiskVolume9 [SYNC] G: HarddiskVolume10

drive#(0-N) Specifies the physical drives to be flushed.

Volume#(0-N) Specifies the LDM volumes to be flushed. Volume# must be specified '\Vol#, \Dms#, \Dmt#, \Dmr# or Volume{...}' as LDM volume for Windows systems. To flush HarddiskVolumeX:-x sync \VolX

For information on '\Vol#, \Dms#, \Dmt#, \Dmr# or Volume{...}' for LDM volumes, see Volume Discovery Function in the User and Reference Guide.



This flushes the system buffer before pairsplit without unmounting the P-VOL (opening state), and indicates as [WARNING] below:

pairsplit -x sync C: WARNING: Only flushed to [\\.\C:] drive due to be opening [SYNC] C: HarddiskVolume3

Note: Syncd has the following behavior as well:• If the logical drives designated as the objects of the sync command are

not opened to any applications, then syncd flushes the system buffer to a drive and waits (30 sec) the delayed (paging) IO for dismount after made the dismount state about the drive. If the logical drives are opened to applications, the syncd waits (30 sec) after the flush of system buffer.This avoids a problem that NTFS on P-VOL is split on inconsistent state because Windows 2003 delays the IO for dismounting.

Note: If sync has failed, you need to confirm the following conditions:• The logical and physical drives designated as the objects of the sync

command are not opened to any applications. For example, confirm that Explore is not pointed on the target drive. If Explore is pointed on the target drive, the target drive is opening.

• The sync command does not ignore the detected error on the NT file system, so sync executes successfully in normal case (NO ERROR case) only on NT file system. For example, confirm the target drive has no failure on the system for Event Viewer. In this case, you must reboot the system or delete the partition and reconfigure the target drive.

mountThe mount subcommand mounts the specified drive to the specified partition on the specified data drive using the drive letter. When the mount subcommand is executed without an argument, all currently mounted drives (including directory mounted volumes) are displayed, and logical drive has been mounting an LDM volume then displays Harddisk#[n] configured an LDM volume.

Syntax

-x mount-x mount drive: Volume#(0-N)-x mount drive: [\directory] Volume#(0-N)

Arguments


drive: hdisk# [partition #]

Specifies the logical drive, data drive (number), and partition to be mounted.


3–8 Subcommands

Example

The following example shows the mount subcommand used as an option of the pairsplit command and its outputs.

This example executes the mount command from a sub-command option of pairsplit. It mounts the "F:"drive to the harddiskvolume2, and then displays mounted devices.

pairsplit -x mount F: hdisk2pairsplit -x mountDrive FS_name VOL_name Device Partition ... Port PathID Targ LunC NTFS Null Harddiskvolume1 ... Harddisk0F: NTFS Null Harddiskvolume2 ... Harddisk1D: NTFS Null Harddiskvolume3 ... Harddisk2D:\hd1 NTFS Null Harddiskvolume4 ... Harddisk3D:\hd2 NTFS Null Harddiskvolume5 ... Harddisk4G: NTFS Null HarddiskDmVolumes\…\Volume1...Harddisk5[3]

This example executes mount from command option of the pairsplit command and then displays the mounted devices:

Output of the mount subcommand:

Drive: Shows the logical drive recognized by the Windows system

drive: [\directory] Volume#

Specifies the logical drive and LDM volume name and number to be mounted. Volume# must be specified '\Vol# or \Dms# or \Dmt# or \Dmr# ' as LDM volume for Windows. To mount HarddiskVolumeX: -x mount C: hdX or -x mount C: \VolXFor information on '\Vol# or \Dms# or \Dmt# or \Dmr#' for LDM volumes, see Volume Discovery Function in the User and Reference Guide.[\directory]: Specifies the directory mount point on the logical drive.pairsplit -x mount D:\hd1 \Vol8 D:\hd1 <+> HarddiskVolume8 pairsplit -x mount D:\hd2 \Vol9 D:\hd2 <+> HarddiskVolume9

Caution: The partition on the specified data drive must be recognized on the Windows system.

[\directory] for the mount must be specified a mount point without embedded space character.

If [\directory] is detected as mount point with embedded space (that is, aaa bbb), then the directory is shown by adding '…' to first strings as below.

pairsplit -x mount

Drive FS_name VOL_name Device Partition ... Port PathID Targ Lun

D: NTFS Null Harddiskvolume3 ... Harddisk2

D:\aaa… NTFS Null Harddiskvolume4 ... Harddisk3

The same method is used for 'inqraid $LETALL' and 'raidscan -pi $LETALL -find' command.



FS_name: Shows the name of the file system formatted on the logical drive

VOL_name: Shows the volume label name for the logical drive

Device, Partition: Shows the device name and partition for the mounted logical drive

Port,PathID,Targ,Lun: Shows the port number, path group ID (bus), target ID, and LUN for the device adaptor of the mounted logical drive.

umount, umountdThe umount subcommand unmounts the specified logical drive and deletes the drive letter. Before deleting the drive letter, this subcommand executes sync internally for the specified logical drive and flushes unwritten data. The umountd subcommand unmounts the logical drive after waiting the delayed IO for dismount.

Syntax

-x umount[d] drive:[\directory] [time]

Argument

Example

The following example shows the umount subcommand used as an option of the pairsplit command.

pairsplit -x umount F: -x umount G: -g oradb -rwpairsplit -x mount

Drive FS_name VOL_name Device Partition... Port PathID Targ LunC: FAT Null Harddisk0 Partition1... 1 0 0 0Z: Unknown Unknown CdRom0 ... Unknown


drive Specifies the mounted logical drive.

[\directory] Specifies the directory mount point on the logical drive. This command option calls 'mountvol /P' internally, if 'USE_MOUNTVOL_P' environment variable is specified. In case of Windows 2008/2012, it is required to specify 'USE_MOUNTVOL_P' variable to avoid a problem of mount.pairsplit -x umount D:\hd1 D:\hd1 <-> HarddiskVolume8 set USE_MOUNTVOL_P=1 pairsplit -x umount D:\hd2 D:\hd2 <-> HarddiskVolume9Example for waiting 45 sec: pairsplit -x umount D: 45 D: <-> HarddiskVolume8

Caution: Umountd has above restriction and it will prompt the delayed IO for dismount. Wait 30 seconds until the completion and release the mount point after making dismount status of the logical drive. This avoids a problem (Windows 2003 only) that the delayed writing for dismount as Event ID51, 57.


3–10 Subcommands

This example unmounts the F: and G: drives, splits all pairs in the specified group (status = PSUS), enables read/write access to all secondary volumes in the specified group, and then displays all mounted drives.

Output of the umount subcommand:

Drive: Shows the logical drive recognized by the Windows system

FS_name: Shows the name of the file system formatted on the logical drive

VOL_name: Shows the volume label name for the logical drive

Device, Partition: Shows the device name and partition for the mounted logical drive

Port,Phid,Targ,Lun: Shows the port number, path group ID (bus), target ID, and LUN for the device adaptor of mounted logical drive.

Note: The umount command flushes (sync) the system buffer of the associated drive before deleting the drive letter. If umount fails, confirm the following conditions:

The logical and physical drives designated as the objects of the umount command are not opened to any applications. For example, confirm that Explore is not pointed on the target drive. If it is, then the target drive is opening.

Umount command does not ignore the detected error on the NT file system, so that umount is successful in a normal case (NO ERROR case) only on NT file system. For example, confirm the target drive has no failure on the system for Event Viewer. If so, you must reboot the system or delete the partition and reconfigure the target drive.

Note: The umountd command has the following behavior as well.

Unmount the logical drive after waiting (30 sec) the delayed (paging) IO for dismount after flushed the system buffer to a drive.

This avoids a problem (Windows 2003 only) that NTFS on P-VOL is split on inconsistent state because Windows 2003 (SP1) delays the IO for dismounting. This also avoids a problem that the delayed (paging) IO for dismounting is written on SVOL_PAIR(Writing Disable) state by rescan, and logged as Windows event (that is, ID51,57).

These problems do not occur on Windows 2008 systems.

Environment variable subcommandsIf no environment variables are set in the execution environment, the following environment variable subcommands set or cancel an environment variable within the CCI command.

setenv: The setenv subcommand sets the specified environment variable(s).

usetenv: The usetenv subcommand deletes the specified environment variable(s).


env: The env subcommand displays the environment variable(s).

sleep: The sleep subcommand causes CCI to wait for the specified time.

Syntax-x setenv vaname value-x usetenv vaname-x env-x sleep time

Arguments

ExampleThe following examples show the setenv and usetenv subcommands used as an option of the raidscan command. This example changes from 'HORC' to 'HOMRCF' an execution environment of the raidscan command that makes a dialog mode, because of establishing 'HORCC_MRCF' as an environment variable.

raidscan[HORC]: -x setenv HORCC_MRCF 1raidscan[HOMRCF]:

raidscan[HOMRCF]: -x usetenv HORCC_MRCF raidscan[HORC]:


Vaname Specifies the environment variable to be set or canceled.

Value Specifies the value or character string of the environment variable to be set.

Time Specifies the sleep time in seconds.

Caution: The environment variables must be set before connecting to HORCM. And it must be specified during interactive mode (-z option). If specified with other than interactive mode, all specified environment variables are not enable. Changing an environment variable after a CCI command execution error is invalid.


3–12 Subcommands

4

Command tools 4–1Hitachi Command Control Interface Command Reference

Command tools

This chapter provides the specifications for the CCI command tools.

□ inqraid

□ mkconf

□ rmawk


-find[c] Finds the appropriate group within the configuration file using a special file provided by STDIN.-find: Searches a group on the configuration definition file (local instance) from <special file> of STDIN by using pairdisplay command, and uses the following options of the pairdisplay command to display its state. This option must be specified HORCMINST as command execution environment.For ShadowImage and Copy-on-Write Snapshot:pairdisplay -d <seq#> <LDEV#> 0 1 2 -l [-fx] [-CLI] 2>/dev/null

For TrueCopy and Universal Replicator:pairdisplay -d <seq#> <LDEV#> -l [-fx] [-CLI] 2>/dev/null

Note: <Seq#> and <LDEV#> are included using SCSI Inquiry command. For VSP G1000 add a “3” at the beginning of the serial number (for example, enter “312345” for serial number 12345.<special file>: This option is used to specify the special file name as argument of command. If no argument, this command makes mode that waits for STDIN. The input from the special file has to be waited.-findc: Uses the following options of the pairdisplay command, and displays with CLI format by editing an output of pairdisplay command. This option must be specified HORCMINST as command execution environment.For ShadowImage and Copy-on-Write Snapshot: pairdisplay -d <seq#> <LDEV#> <MU#> -fd -CLI 2>/dev/null

For TrueCopy and Universal Replicator:pairdisplay -d <seq#> <LDEV#> -fd -CLI 2>/dev/null

Note: <Seq#> and <LDEV#> are included using SCSI Inquiry command. For VSP G1000 add a “3” at the beginning of the serial number.<special file>: Specifies a special file name as the argument of a command. If no argument, this command makes mode that waits for STDIN. The input from the special file has to be waited.

-CLI Specifies the display of structured column output for command line interface (CLI) parsing. Also used for '-find' option. The delimiters between columns can be spaces and/or dashes (-).

-CLIWP, -CLIWN

Displays the WWN (world wide name for host adapter) with command line interface (CLI) format, also used for '-find' option.

-sort[CM] Sorts the target devices by Serial#,LDEV# order.[CM] Searches command device from the specified special file (STDIN or argument) and displays the command device only in structure definition file image. This option is valid within '-sort' option.

Option Description


4–4 Command tools

-gvinf-gvinfex

Windows systems only. -gvinfex is for GPT disk only.Gets the signature and volume layout information of a raw device file provided via STDIN or arguments, and saves this information to the system disk with the following format: \WindowsDirectory\VOLssss_llll.ini where ssss = serial#, llll = LDEV#Normally this option is used by the Windows Disk Management after setting the signature and volume layout information for S-VOL. You do not need to be aware of this file.

-svinf[=PTN]-svinfex[=PTN]

Windows systems only. -svinfex[=PTN] is for GPT disk only.Reconfigure the signature and volume layout information that was saved to the system disk to a device provided by STDIN or arguments. Gets the serial# and LDEV# for the target device issuing SCSI Inquiry, and sets the signature and volume layout information into VOLssss_llll.ini file to the readout device. This option sets correctly because the signature and volume layout information is managed by the serial# and LDEV# without depending on Harddisk#, which can be changed by configuration changes.[=PTN]: Specifies a strings pattern to interpret the strings provided by STDIN or argument as a raw device.\Device\HarddiskVolume#(number) is made in a sequential order executed -svinf to Harddisk, and its number remains the same as long as the system configuration is not changed. If you want to make \Device\HarddiskVolume#(number) more absolutely, then make \Device\HarddiskVolume# in serial# and LDEV# order by using the '-sort' option as shown below:[VOL61459_451_5296A763] -> Harddisk3 [OPEN-3 ][VOL61459_452_5296A760] -> Harddisk4 [OPEN-3 ][VOL61459_453_5296A761] -> Harddisk5 [OPEN-3 ]

-gplba-gplbaex

Windows systems only. -gplbaex is for GPT disk only.Displays usable LBA on a physical drive in blocks (512 bytes), and specifies [slba] [elba] options for raidvchkset command. Example:C:\HORCM\etc>inqraid $Phys -CLI -gplba -sortHarddisk11 : SLBA = 0x00003f00 ELBA = 0x000620d9 PCNT = 7 [OPEN-3-CVS ] Harddisk12 : SLBA = 0x00003f00 ELBA = 0x00042ad1 PCNT = 4 [OPEN-3-CVS ] Harddisk13 : SLBA = 0x0000003f ELBA = 0x000620d9 PCNT = 1 [OPEN-3-CVS ]

SLBA: Displays usable starting LBA in blocks (512 bytes). ELBA: Displays usable ending LBA (ELBA -1) in blocks (512 bytes). PCNT: Displays the number of partitions.Example for setting of Harddisk11: C:\HORCM\etc>raidvchkset -d hd11 -vs 16 0x00003f00 0x000620d9

Option Description


-fv Windows systems only.Displays the Volume{GUID} via $Volume with wide format.Example:C:\HORCM\etc>inqraid -CLI $Vol -fvDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}\Vol3\Dsk0 CL2-D 62496 256 - - - - OPEN-3-CVS-CM

-fp or -fl or-pin

If the target device file is set as a protection volume or PIN track volume is occurred by dual failure of the RAID, the device file name is shown by appending '*'. It is valid when specified with "-CLI" option. If the -fp option is specified, the data protection volume is a Database Validator volume. If the -fl option is specified, the data protection volume is a Data Retention Utility volume. If the -pin option is specified, shows that the volume is PIN track volume because of double drive failure and/or especially external connection disk failure.# ls /dev/rdsk/c57t4* | ./inqraid -CLI -fpDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDc57t4d0* CL1-D 62496 32 - s/P/ss 0004 5:01-03 OPEN-3c57t4d3* CL1-D 62496 35 - s/P/ss 0004 5:01-03 OPEN-3c57t4d4 CL1-D 62496 36 - s/P/ss 0004 5:01-01 OPEN-3c57t4d5 CL1-D 62496 37 - s/P/ss 0004 5:01-02 OPEN-3

This example shows that c57t4d0 and c57t4d3 (marked by *) are set to enable Database Validator checking (-fp option). The raidvchkset command is used to enable and disable volume protection.For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

-fg Shows a LUN on the host view by finding a host group.

Option Description


4–6 Command tools

-CLIB -sort This option is used to know how much pair is possible to create in the paired volume on the actual storage system, and calculates the total Bitmap page for TrueCopy, Universal Replicator, and ShadowImage and the unused Bitmap page by sorting the specified special file (the standard input or the argument) with Serial#,LDEV# order.The default is ShadowImage. This option is valid within '-sort' option.Note: An identical LDEV which was sorted in Serial#, LDEV# is excepted from the accumulated total (LDEVs shared by multiple ports are calculated as one LDEV).Also, a command device is excepted from the accumulated total.Example: # ls /dev/rdsk/* | inqraid -sort -CLIBDEVICE_FILE PORT SERIAL LDEV SL CL +SI/SI UNUSED PRODUCT_IDc1t0d0 CL1-E 63516 0 0 0 - - OPEN-9-CMc1t0d1 CL1-E 63516 12288 0 0 1 30718 OPEN-3c1t0d2 CL1-E 63516 12403 0 0 4 30718 OPEN-9c1t0d3 CL1-E 63516 12405 0 0 9 30718 OPEN-Ec1t0d4 CL1-E 63516 12800 0 0 12 30718 OPEN-8c1t0d5 CL1-E 63516 12801 0 0 18 30718 OPEN-8*2c1t0d6 CL1-E 63516 13057 0 0 31 30718 OPEN-Lc2t0d6 CL2-E 63516 13057 0 0 31 30718 OPEN-L

SL: Shows the SLPR number of LDEV.CL: Shows the CLPR number of LDEV.+SI/SI: Shows the accumulated total of differential Bitmap for the ShadowImage. The increase page shows necessary Bitmap page capacity as one paired volume of ShadowImage.UNUSED: Shows the unused Bitmap page for ShadowImage. One Page is about 64 KB.For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Option Description


-fh[c] Specifies the bitmap page for TrueCopy and Universal Replicator. The '-fc' option is used to calculate the bitmap page of cylinder size for TrueCopy.Example: # ls /dev/rdsk/* | inqraid -sort -CLIB -fhDEVICE_FILE PORT SERIAL LDEV SL CL +TC/UR UNUSED PRODUCT_IDc1t0d0 CL1-E 63516 0 0 0 - - OPEN-9-CMc1t0d1 CL1-E 63516 12288 0 0 1 11605 OPEN-3c1t0d2 CL1-E 63516 12403 0 0 3 11605 OPEN-9c1t0d3 CL1-E 63516 12405 0 0 10 11605 OPEN-Ec1t0d4 CL1-E 63516 12800 0 0 11 11605 OPEN-8c1t0d5 CL1-E 63516 12801 0 0 13 11605 OPEN-8*2c1t0d6 CL1-E 63516 13057 0 0 21 11605 OPEN-Lc2t0d6 CL2-E 63516 13057 0 0 21 11605 OPEN-L

SL: Shows the SLPR number of LDEV.CL: Shows the CLPR number of LDEV.+TC/UR: Shows the accumulated total of differencial Bitmap for the TrueCopy or Universal Replicator. The increase page shows the necessary differential bitmap capacity for TrueCopy or Universal Replicator.UNUSED: Shows the unused Bitmap page capacity for TrueCopy and Universal Replicator. One Page is about 64 KB.For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

-CLI -fn Displays the LDEV nickname in the PRODUCT ID. If the storage system does not support LDEV nickname, '-' is displayed.Example:# ls /dev/rdsk/c57t4* | ./inqraid -CLI -fnDEVICE_FILE PORT SERIAL LDEV CTG C/B/12 SSID R:Group LDEV_NIC_NAMEc57t4d0 CL1-D 62496 32 - s/P/ss 0004 5:01-03 my_volume_1c57t4d3 CL1-D 62496 35 - s/P/ss 0004 5:01-03 my_volume_2c57t4d4 CL1-D 62496 36 - s/P/ss 0004 5:01-01 -c57t4d5 CL1-D 62496 37 - s/P/ss 0004 5:01-02 -

For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Option Description


4–8 Command tools

Examples

Example 1: using inqraid and system command to display the connection between STDIN special file and actual physical drive of storage system

HP-UX system:

# ioscan -fun | grep rdsk | ./inqraid/dev/rdsk/c0t2d1 -> [HP] CL2-D Ser = 30053 LDEV = 9 [HP ] [ OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3/dev/rdsk/c0t4d0 -> [HP] CL2-D Ser = 30053 LDEV = 14 [HP ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

Linux and zLinux system:

-CLI -export This option outputs as export format after obtaining the storage system device information from the specified special file (STDIN or argument). The device information includes 'Keyword, Serial#, Ldev#, Device file name, ...'. This export formatted file can import as STDIN of the raidscan -find verify or the raidscan -find inst. If the application server and CCI server are operated on different hosts, volume discovery can be performed with this option among the hosts.Example:# ls /dev/rdsk/c1t* | inqraid -CLI -exportINQRAID:@CL4-G@64015@0@124@OPEN-V-CM@/dev/rdsk/c1t0d0s2INQRAID:@CL4-G@64015@1@124@OPEN-V-CM@/dev/rdsk/c1t0d1s2INQRAID:@CL4-G@64015@2@95@OPEN-V@/dev/rdsk/c1t0d2s2INQRAID:@CL4-G@64015@3@95@OPEN-V@/dev/rdsk/c1t0d3s2INQRAID:@CL4-G@64015@4@95@OPEN-V@/dev/rdsk/c1t0d4s2INQRAID:@CL4-G@64015@5@95@OPEN-V@/dev/rdsk/c1t0d5s2INQRAID:@CL4-G@64015@7@95@OPEN-V@/dev/rdsk/c1t0d7s2

For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Restrictions on device naming

STDIN or special files are specified as follows:• HP-UX: /dev/rdsk/* or /dev/rdisk/disk*• Solaris: /dev/rdsk/*s2 or c*s2• Linux : /dev/sd... or /dev/rd... ,/dev/raw/raw*.• zLinux: /dev/sd... or /dev/dasd… or /dev/rd... ,/dev/raw/raw*• AIX: /dev/rhdisk* or /dev/hdisk* or hdisk*• DIGITAL or Tru64: /dev/rrz*c or /dev/rdisk/dsk*c or /dev/

cport/scp*

• IRIX64: /dev/rdsk/*vol or /dev/rdsk/node_wwn/*vol/* or /dev/dsk/*vol or /dev/dsk/node_wwn/*vol/*

• OpenVMS: $1$* or DK* or DG* or GK*• Windows: hdX-Y, $LETALL, $Volume, $Phys,

D:\Vol(Dms,Dmt,Dmr)X\DskY, \Vol(Dms,Dmt,Dmr)X\DskYFor information about LDM volumes for Windows systems, see Remote Volume Discovery in the User and Reference Guide.

Lines starting with '#' via STDIN are interpreted as comments.

Option Description


# ls /dev/sd* | ./inqraid/dev/sdh -> CHNO = 0 TID = 1 LUN = 7 [HP] CL2-B Ser = 30053 LDEV = 23 [HP ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 1- 2] SSID = 0x0004 CTGID = 2/dev/sdi -> CHNO = 0 TID = 4 LUN = 0 [HP] CL2-B Ser = 30053 LDEV = 14 [HP ] [OPEN-3-CM ] RAID5[Group 1- 2] SSID = 0x0004

Solaris system:

# ls /dev/rdsk/* | ./inqraid/dev/rdsk/c0t2d1 -> [HP] CL2-D Ser = 30053 LDEV = 9 [HP ] [OPEN-3 ] CA = P-VOL BC[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3/dev/rdsk/c0t4d0 -> [HP] CL2-D Ser = 30053 LDEV = 14 [HP ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

AIX system:

# lsdev -C -c disk | grep hdisk | ./inqraidhdisk1 -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3hdisk2 -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

Windows system:

C:\HORCM\etc> echo hd1-2 | inqraid ( or inqraid hd1-2 )Harddisk 1 -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3 Harddisk 2 -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

Tru64 UNIX system:

# ls /dev/rdisk/dsk* | ./inqraid/dev/rdisk/dsk10c -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3/dev/rdisk/dsk11c -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

IRIX system with FC_AL:

# ls /dev/rdsk/*vol | ./inqraid/dev/rdsk/dks1d6vol -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3/dev/rdsk/dks1d7vol -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

IRIX system with fabric:

# ls /dev/rdsk/*/*vol/* | ./inqraid/dev/rdsk/50060e8000100262/lun3vol/c8p0 -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3


4–10 Command tools

/dev/rdsk/50060e8000100262/lun4vol/c8p0 -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI] [OPEN-3-CM] RAID5[Group 2- 1] SSID = 0x0008

OpenVMS system:

$ inqraid dka145-146DKA145 -> [ST] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3DKA146 -> [ST] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM ] RAID5[Group 2- 1] SSID = 0x0008

The following items are output for the inqraid command tool:

CL X - Y: Displays the port number on the RAID storage system.

Ser: Displays the production (serial#) number on the RAID storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

LDEV: Displays the LDEV# in the RAID storage system.

HORC: Displays the attribute ('P-VOL/S-VOL/SMPL') of a volume in the RAID storage system.

HOMRCF: Displays the attribute ('P-VOL/S-VOL/SMPL') of a volume as MU#0-2 of ShadowImage or Copy-on-Write Snapshot in the RAID storage system.

Group: Displays the relation of the physical volume mapped to LDEV.

SSID: Displays storage subsystem ID (hexadecimal) of the LDEV in the RAID storage system. The Unified Storage VM does not support SSID but displays the specified value.

CTGID: Displays CT group ID of TrueCopy Async and Universal Replicator when the LDEV has been defined as the P-VOL or S-VOL of the TrueCopy Async or Universal Replicator.

CHNO: Displays the channel number on the device adapter that recognizes on the Linux host. Displayed only for Linux systems.

TID: Displays target ID of the data drive that connects on the device adapter port. Displayed only for Linux systems.

LDEV Mapping Display Formats

RAID Group RAID1[Group Group number - Sub number] RAID5[Group Group number - Sub number] RAID6[Group Group number - Sub number]

Copy-on-Write Snapshot S-VOL

SNAPS[PoolID poolID number ]

Unmapped UNMAP[Group 00000]

External LUN E-LUN[Group External Group number]

Dynamic Provisioning volume

A-LUN[PoolID poolID number ]


LUN: Displays logical unit number of the data drive that connects on the device adapter port. Displayed only for Linux systems.

Note: The display of group, SSID, and CTGID depends on the storage system microcode level. The CHNO, TID, and LUN items are displayed only for Linux systems.

Example 2: inqraid with -find option (Linux shown)

ls /dev/sd* | inqraid -find/dev/sdb -> No such on the groupGroup PairVol (L/R) (Port#,TID,LU),Seq#,LDEV#.P/S, Status,Fence,Seq#,P-LDEV# Moradb oradev2 (L) (CL2-N , 3, 2) 8071 22..SMPL ----- ------,----- ---- -->/dev/sdc

Example 3: inqraid with -find option (HP-UX shown)

# echo /dev/rdsk/c23t0d0 /dev/rdsk/c23t2d3 | ./inqraid -findGroup PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# Mhorc1 dev00(L) (CL2-J, 0, 0-0) 61456 192..S-VOL SSUS,----- 193 -->/dev/rdsk/c23t0d0Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# Mhorc1 dev10(L) (CL2-J , 2, 3-0) 61456 209..S-VOL SSUS,----- 206 -->/dev/rdsk/c23t2d3

Example 4: inqraid with -findc option (HP-UX shown)

# echo /dev/rdsk/c23t0d0 /dev/rdsk/c23t2d3 | ./inqraid -findcDEVICE_FILE M Group PairVol P/S Stat R_DEVICE M P/S Stat LKc23t0d0 0 horc1 dev00 S-VOL SSUS c23t0d1 0 P-VOL PSUS OK/dev/rdsk/c23t0d0[1] -> No such on the group/dev/rdsk/c23t0d0[2] -> No such on the groupDEVICE_FILE M Group PairVol P/S Stat R_DEVICE M P/S Stat LKc23t2d3 0 horc1 dev10 S-VOL SSUS c23t2d2 0 P-VOL PSUS OK/dev/rdsk/c23t2d3[1] -> No such on the group/dev/rdsk/c23t2d3[2] -> No such on the group

# echo /dev/rdsk/c23t0d0 /dev/rdsk/c23t2d3 | ./inqraid -findc -CLIDEVICE_FILE M Group PairVol P/S Stat R_DEVICE M P/S Stat LKc23t0d0 0 horc1 dev00 S-VOL SSUS c23t0d1 0 P-VOL PSUS OKc23t2d3 0 horc1 dev10 S-VOL SSUS c23t2d2 0 P-VOL PSUS OK

DEVICE_FILE: Device file name.

M: MU# of local and remote.

Group: Group name (dev_group) defined in the configuration file.

PairVol: Paired vol. name (dev_name) within the group defined in the configuration file.

P/S: Volume attribute (P-VOL or S-VOL or simplex).

Stat: Status of the paired volume.



R_DEVICE: Device file name of remote site.

LK: Check result of the paired volume connection path.

Example 5: inqraid with -cli option (Linux shown)

# ls /dev/sd* | ./inqraid -CLIDEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_IDsdh CL2-B 30053 23 2 S/P/ss 0004 5:02-01 OPEN-3sdi CL1-A 64015 14 - - 0004 E:00002 OPEN-3-CMsdj - - - - - - - -

DEVICE_FILE: Displays the device file name only.

PORT: Displays the RAID storage system port number.

SERIAL: Displays the production (serial#) number of the storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

LDEV: Displays the LDEV# within the storage system.

CTG: Displays the CT group ID of TrueCopy Async and Universal Replicator when the LDEV has been defined as a TrueCopy Async or Universal Replicator P-VOL or S-VOL.

H/M/12: Displays attribute (P-VOL is 'P', S-VOL is 'S', SMPL is 's') of a TrueCopy volume, ShadowImage or Copy-on-Write Snapshot volume, and ShadowImage or Copy-on-Write Snapshot MU#1,2 volumes.

SSID: Displays the storage subsystem ID of an LDEV in the storage system. The Unified Storage VM does not support SSID but displays the specified value.

R:Group: Displays the physical position of an LDEV according to mapping of LDEV in the storage system.

PRODUCT_ID: Displays product-id field in the STD inquiry page.

Note: For a command device, PORT/SERIAL/LDEV/PRODUCT_ID is the SCSI Inquiry information for the external command device, if the command device is mapped as ELUN(R: =E).

LDEV Mapping R: Group

RAID Group RAID Level 1 : RAID1 5 : RAID5 6 : RAID6

RAID Group number - Sub number

Copy-on-Write Snapshot S-VOL

S Pool ID number

Unmapped U 00000

External LUN E External group number

Dynamic Provisioning volume

A Pool ID number


Example 6: inqraid with -cliwp and -cliwn options (HP-UX shown)

# echo /dev/rdsk/c23t0d0 /dev/rdsk/c23t0d1 | ./inqraid -CLIWPDEVICE_FILE PWWN AL PORT LUN SERIAL LDEV PRODUCT_IDc23t0d0 500060e802f01018 - CL2-J - 61456 192 OPEN-3c23t0d1 500060e802f01018 - CL2-J - 61456 193 OPEN-3

# echo /dev/rdsk/c0t2d3 | ./inqraid -CLIWNDEVICE_FILE NWWN AL PORT LUN SERIAL LDEV PRODUCT_IDc0t2d3 5000E000E0005000 - CL1-A - 30015 2054 OPEN3-CVS

DEVICE_FILE: Displays the device file name only.

WWN: CLIWP option displays Port_WWN of the host adapter included in the STD inquiry page. CLIWN option displays Node_WWN of host adapter included in STD inquiry page.

AL: Always displays '-'.

PORT: Displays the RAID storage system port number.

LUN: Always displays '-'.

SERIAL: Displays the production (serial#) number of the storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

LDEV: Displays the LDEV# within the storage system.

PRODUCT_ID: Displays product-id field in the STD inquiry page.

Example 7: inqraid with -sort[cm] option (HP-UX shown)

#ioscan -fun | grep rdsk | ./inqraid -sort -CM -CLIHORCM_CMD#dev_name dev_name dev_name#UnitID 0 (Serial# 30012)/dev/rdsk/c0t3d0 /dev/rdsk/c1t2d1#UnitID 1 (Serial# 30013)/dev/rdsk/c2t3d0

Example 8: inqraid with -gvinf option

D:\HORCM\etc>inqraid $Phys -gvinf -CLI\\.\PhysicalDrive0:# Harddisk0 -> [VOL61459_448_DA7C0D91] [OPEN-3 ] \\.\PhysicalDrive1:# Harddisk1 -> [VOL61459_449_DA7C0D92] [OPEN-3 ]\\.\PhysicalDrive2:# Harddisk2 -> [VOL61459_450_DA7C0D93] [OPEN-3 ] -> S/N LDEV Signature

Example 9: inqraid with -svinf[=PTN] option

D:\HORCM\etc>pairdisplay -l -fd -g URAGroup PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#, P-LDEV# MURA URA_000(L) Harddisk3 0 61459 451..S-VOL SSUS,----- 448 -URA URA_001(L) Harddisk4 0 61459 452..S-VOL SSUS,-----



449 -URA URA_002(L) Harddisk5 0 61459 453..S-VOL SSUS,----- 450 -

D:\HORCM\etc>pairdisplay -l -fd -g URA | inqraid -svinf=Harddisk[VOL61459_451_5296A763] -> Harddisk3 [OPEN-3 ][VOL61459_452_5296A760] -> Harddisk4 [OPEN-3 ][VOL61459_453_5296A761] -> Harddisk5 [OPEN-3 ]

Caution: If the S-VOL is created with 'Noread' option (ShadowImage only) and the system is rebooted, the system cannot create a Device object (\Device\HarddiskVolume#) and Volume{guid} for S-VOL, but a Device object (\Device\HarddiskVolume#) and Volume{guid} is created by using -svinf option after splits the S-VOL.

mkconfThe mkconf command is a CCI command tool used to make a configuration file from a special file (raw device file) provided via STDIN.

Syntax/HORCM/usr/bin/mkconf.sh (UNIX systems)\HORCM\Tool\mkconf.exe (Windows and OpenVMS systems)mkconf.sh [ -g[g] <group> [-m <mu#>] [-i <inst#>] [-s <service>][-a] ]mkconf.exe [ -g[g] <group> [-m <mu#>] [-i <inst#>] [-s <service>][-a] [-c <drive#>] ]


Option Description

No argument No option displays help/usage and version information.

-g <group> Specifies the 'dev_group' name for a configuration file. If not specified, 'VG' is used as default.

-gg Shows a LUN on the host view by finding a host group.

-m <mu#> Specifies the mirror descriptor for ShadowImage and Copy-on-Write Snapshot volumes. TrueCopy volume does not specify the mirror descriptor.

-i <inst#> Specifies the instance number for HORCM.

-s <service> Specifies the service name (port name) for a configuration file. If not specified, '52323' is used as default.

-a Specifies an addition of the group to a configuration file.

-c <drive#> Windows systems only.Specifies the range of drive numbers that should be examined in order to discover the command devices. If not specified, '$PhysicalDrive' is used as default.

-c <DKA#-#> OpenVMS systems only.Specifies the range of drive numbers that should be examined to discover the command devices. If not specified, '$1$DGA0-10000 DKA0-10000 DGA0-10000' is used as default.


Examples

Example 1: mkconf command tool (HP-UX shown)

In this example, the configuration file is created as 'horcm*.conf' in the current directory. The log directory of HORCM is specified as 'log*' in the current directory. You must modify the 'ip_address & service' of an existing configuration file as needed.

# cd /tmp/test# cat /etc/horcmperm.conf | /HORCM/usr/bin/mkconf.sh -g ORA -i 9 -m 0starting HORCM inst 9HORCM inst 9 starts successfully.HORCM Shutdown inst 9 !!!A CONFIG file was successfully completed.starting HORCM inst 9HORCM inst 9 starts successfully.DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c23t0d0 ORA ORA_000 CL2-J 0 0 0 61456 192/dev/rdsk/c23t0d1 ORA ORA_001 CL2-J 0 1 0 61456 193/dev/rdsk/c23t0d2 ORA ORA_002 CL2-J 0 2 0 61456 194/dev/rdsk/c23t0d3 ORA ORA_003 CL2-J 0 3 0 61456 195/dev/rdsk/c23t0d4 ORA ORA_004 CL2-J 0 4 0 61456 256/dev/rdsk/c23t0d5 ORA ORA_005 CL2-J 0 5 0 61456 257/dev/rdsk/c23t0d6 ORA ORA_006 CL2-J 0 6 0 61456 258/dev/rdsk/c23t0d7 - - - - - 0 61456 259HORCM Shutdown inst 9 !!!Please check '/tmp/test/horcm9.conf','/tmp/test/log9/curlog/horcm_*.log', and modify 'ip_address & service'.

# ls <=Verify configuration and log files.horcm9.conf log9# vi *.conf <=Verify config file, check ip address & service.

# Created by mkconf.sh on Mon Jan 22 17:59:11 JST 2001

HORCM_MON#ip_address service poll(10ms) timeout(10ms)127.0.0.1 52323 1000 3000

HORCM_CMD#dev_name dev_name dev_name#UnitID 0 (Serial# 61456)/dev/rdsk/c23t3d0

Example 2: mkconf command tool (HP-UX shown

HORCM_DEV#dev_group dev_name port# TargetID LU# MU## /dev/rdsk/c23t0d0 SER = 61456 LDEV = 192 [FIBRE FCTBL = 4] ORA ORA_000 CL2-J 0 0 0# /dev/rdsk/c23t0d1 SER = 61456 LDEV = 193 [FIBRE FCTBL = 4] ORA ORA_001 CL2-J 0 1 0# /dev/rdsk/c23t0d2 SER = 61456 LDEV = 194 [FIBRE FCTBL = 4] ORA ORA_002 CL2-J 0 2 0# /dev/rdsk/c23t0d3 SER = 61456 LDEV = 195 [FIBRE FCTBL = 4] ORA ORA_003 CL2-J 0 3 0# /dev/rdsk/c23t0d4 SER = 61456 LDEV = 256 [FIBRE FCTBL = 4] ORA ORA_004 CL2-J 0 4 0# /dev/rdsk/c23t0d5 SER = 61456 LDEV = 257 [FIBRE FCTBL = 4] ORA ORA_005 CL2-J 0 5 0



# /dev/rdsk/c23t0d6 SER = 61456 LDEV = 258 [FIBRE FCTBL = 4] ORA ORA_006 CL2-J 0 6 0# ERROR [CMDDEV] /dev/rdsk/c23t0d7 SER = 61456 LDEV = 259 [OPEN-3-CM] <=See Notes.

HORCM_INST#dev_group ip_address serviceORA 127.0.0.1 52323 <=Check and update as needed.

Notes on mkconf:• A unitID is added to the Serial# order. If two or more command devices

exist in the storage system, select the device file that is shared among the storage system ports on a priority basis, and treat as an alternate command device. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

• If the STDIN device includes the command device, the target device is commented out as shown below:

# ERROR [CMDDEV] /dev/rdsk/c23t0d7 SER = 61456 LDEV = 259 [ OPEN-3-CM ]

• If the STDIN device is shared among multiple device files and already displayed as a target device, the target device is commented out as shown below:

# ERROR [LDEV LINK] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [FIBREFCTBL = 4]

• If the STDIN device does not have appropriate mirror description (MU#), the target device is commented out as shown below:

# ERROR [INVALID MUN (2 < 1)] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3 ]

• If the STDIN device is mixed among the storage systems of differential mirror control, the target device is commented out as shown below:

# ERROR [MIXING RAID TYPE] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3]

rmawkThe rmawk command is a scriptable command for associating with the pair operation commands and raidcom commands.

This command provides basically the following three functions:• Outputs by filtering STDIN with the specified conditions.

Command | rmawk @1-eq:PAIR -a @2-ne:0

• Performs the command with the variable parameter specified by interpreting STDIN with the specified conditions.

Command | rmawk @3-eq:TAR exe="Command line @1"

• Tests by interpreting the output command with the specified conditions or waits until the conditions become TRUE, by performing the specified command.


rmawk exe="Command line" @2-eq:PAIR -o @2-eq:PSUSrmawk exe="Command line" @2-eq:COPY timeout=300

Syntax/HORCM/usr/bin/rmawk [-h | exe="…" | sys="…" | timeout=value | interval=value | -BL | -AT | -EC[VAL] | @variable operators ]


Option Description

No argumentor-h

No option displays help/usage and version information.

exe="command_line"

Specifies the command line to be performed when the result of the specified formula and the conditions are TRUE. The testing/waiting specifies the command to be its target."@variable" with the field variables of STDIN can be included in the command line.Example:exe="raidcfg -a qry -o hgrp -pport @1"exe="raidcfg -a reg -o hgrp -pport @1-@2 -pname @3"exe="type map.txt | rmawk @@L-eq:@L exe=\"raidcfg -a map -osnap -pname @1 -pldev @5 @@1\""

exe="print …. "

Specifies printing (with Line Feed) when the result of the specified formula and the conditions are TRUE."@variable" with the field variables of STDIN can be included in the command line. When "@variable" is specified as "@C#/C#*", the variable is interpreted as character string. When "@variable" is specified as "@C#?/C#+/L/C/R", the variable is interpreted as integer.The printing range is from "print" to the end including spaces.Example:exe="print PORT=@1 LDEV=@3"exe="print PORT=@1 LDEV=@3 Total CAP = @4+"

exe="printn…. "orexe="prints…. "

Specifies printing (without Line Feed) when the result of the specified formula and the conditions are TRUE."@variable" with the field variables of STDIN can be included in the command line. When "@variable" is specified as "@C#/C#*", the variable is interpreted as character string. When "@variable" is specified as "@C#?/C#+/L/C/R", the variable is interpreted as integer.The printing range is from "print" to the end including spaces.Example:exe="printn PORT=@1 LDEV=@3"

Note: "prints..." is used to print to the strings buffer of '@0*'.

exe=exit Specifies to exit this command when the result of the specified formula and the conditions are TRUE. The return value of exit is "@R" variable.



sys="command_line"

Specifies the command line to be performed in the transparent mode when the result of the specified formula and the conditions are TRUE."@variable" and "@expression" in the command line are not interpreted as variables but are filtered out as variables to path them to the specified command.Example: UNIX.sys='rmawk exe="pairdisplay -g G1 -CLI -l" @6-eq:PAIR'

Example: Windows.sys="rmawk exe=\"pairdisplay -g G1 -CLI -l\" @6-eq:PAIR"

Example: OpenVMS.sys="rmawk exe=""pairdisplay -g G1 -CLI -l"" @6-eq:PAIR"

Exception: When "exe="..."" is specified in the command line and there is "@variable" as an argument in this command, it is interpreted as "@variable" that is including the field variables of STDIN.Example: UNIX.sys='rmawk exe="pairdisplay -d @3 @5 -CLI -l" @6-eq:PAIR'

Example: Windows.sys="rmawk exe=\"pairdisplay -d @3 @5 -CLI -l\" @6-eq:PAIR"

Example: OpenVMS.sys="rmawk exe=""pairdisplay -d @3 @5 -CLI -l"" @6-eq:PAIR"

timeout=value

Specifies the timeout time in seconds for waiting by interpreting this output command with the specified conditions when the specified command is performed.

interval=value

Specifies the interval time in seconds for waiting by interpreting this output command with the specified conditions when the specified command is performed.

-BL Specifies to include blank lines from STDIN. This is used to detect the blank lines when there are in the STDIN.

-AT • When "-AT" is specified (the default setting does not specify this option)Specifies to testing or waiting until the conditions become TRUE in all the command lines, by interpreting the output of the specified command with the specified conditions.Testing ends as an ERROR (1) if there is even one FALSE in the specified condition. And waiting waits until all the lines become TRUE by retrying the specified command until becoming timeout if there is even one FALSE in the lines of the specified conditions. If it becomes timeout, the command ends as an ERROR (1).

• When "-AT" is not specifiedIt tests or waits until at least one line becomes TRUE, by interpreting the output of the specified command with the specified conditions.If there is one TRUE at least in the specified conditions, the testing ends as NORMAL (0). If there is one TRUE at least in the specified conditions, the waiting ends as NORMAL (0). If all the lines are FALSE, it waits until at least one line become TRUE by retrying the specified command until becoming timeout. If it becomes timeout, the command ends as an ERROR (1).

Option Description


-EC[VAL] Performs only once with ending of lines or "exe=exit" as Line#0. If you need to perform something special at end of lines, specify this option that is called as Line#0. This is enabled in the run mode.If VAL(integer) is specified, @C#? variable for all are initialized to the specified VAL before starting. If VAL is invalid such as -ECM, then @C#? variable for all are initialized to the MAX value with 64-bit integer.

@variable Specifies the following variables. The variables can be specified in both the left and right side of the formula. The variables can also be specified as arguments of the command to be performed or of printing.• @C#

Field strings corresponding to the column number (Column#) from STDIN. If "C#" is specified in hexadecimal ("0x..."), then its field is treated as hexadecimal strings.

• @C#*Strings from the field to the end corresponding to the column number from STDIN.

• @C#?64 bit variables corresponding to the column number from STDIN (initial value 0).

• @C#+64 bit variables adding field variables corresponding to the column number from STDIN (initial value 0).

• @0A variable that indicates one line (This is used when printing or searching within the line.).

• @LA variable that indicates the line number from STDIN.

• @CA variable that indicates the number of column in each line of STDIN.

• @RA return value of performing command.

• @0*A string variable that can be memorized one line.

• nullA special variable that tests if the character string is null or not.

• @C#?tA variable that can be specified within exe="…" to print the C#? variable as TOD (time of day). If the C#? variable is zero, thecurrent time is printed.

• @C#?xA variable that can be specified within exe="…" to print the C#? variable as hexadecimal strings by adding 0x.

• @@A variable that can be specified within exe="…" to print the @ character.

Option Description



operators (-operator:)

Specifies the following comparison operation. Variables in the field are operated in 64-bit integers.The numerical values in the field strings are "1234..." or "0x1234..." format without octal code.• -eq:

Treats the target as character strings or integers by comparing with "==". When "@C#/C#" is specified in the left side of an equation, this is treated as character strings. When "@C#?/C#+/L/C/R" is specified in it, this is treated as integers.

• -ne:Treats the target as character strings or integers by comparing with "!=". When "@C#/C#" is specified in the left side of an equation, this is treated as character strings. When "@C#?/C#+/L/C/R" is specified in it, this is treated as integers.

• -gt:Treats the target as integers by comparing with ">".

• -ge:Treats the target as integers by comparing with ">=".

• -lt:Treats the target as integers by comparing with "<".

• -le:Treats the target as integers by comparing with "<=".

operators (=operator:)

Specifies the following arithmetical operation. Variables in the field are operated in 64-bit integers.The numerical values in the field strings are "1234..." or "0x1234..." format without octal code.• =ad:

Treats the target as integers by operating with "+ (Addition)".• =sb:

Treats the target as integers by operating with "- (Subtraction)".• =ml:

Treats the target as integers by operating with "* (Multiplication)".• =dv:

Treats the target as integers by operating with "/ (Division)".• =st:

Treats the target as integers by substituting with "= (Setting)".

operators (-operator)

Specifies the following logical operation for the result of the comparison operation.• -o

Judges the result of the comparison operation as the "Logical OR".• -a

Judges the result of the comparison operation as the "Logical AND".• -n

Inverts the result of the comparison operation. (TRUE becomes FALSE, FALSE becomes TRUE.)

Option Description


Returned valuesThe rmawk command sets the following returned values during exit allowing you to check the execution results.

Normal termination:

0: The command ends normally with the specified condition.

1:• Testing: The specified condition is FALSE.• Waiting: The specified condition is Timeout.

Abnormal termination:

125: The command ends with a syntax error.

126: The command ends with a system error.

ExamplesFor examples of display, see rmawk command examples on page 5-62.

Examples of comparison expression

@20-eq:PAIR: Compares if the character string in Column #20 from STDIN matches "PAIR".

@20-eq:PSU*: Compares if "PSU" is included in the character string in Column #20 from STDIN.

@0-eq:PSU*: Compares if "PSU" is included in one line from STDIN. This is equivalent to "grep PSU".

@20-eq:@21: Compares if the character strings in Column #20 and Column #21 match.

@20-ge:50: Compares if it is "value >= 50" of Column #20 from STDIN.

@L-ge:20: Compares if it is the current "number of lines >= 20" from STDIN.

@C-ge:20: Compares if it is "number of columns >= 20" of the current lines from the STDIN.

@R-gt:0: Compares if it is "return value > 0" of the specified command.

Examples of arithmetic expression

@8?=ad:@8: Performs "@8? = @8? + @8". This is equivalent to "@8+".

@8=ad:@5: Performs "@8? = @8 + @5".

@8=ad:@5?: Performs "@8? = @8 + @5?".

@8=ad:30: Performs "@8? = @8 + 30?".

@8=st:30: Performs "@8? = 30".



@5=st:@5: Performs "@5? = @5" for converting to the integer.

Example:

Command | rmawk @8?=ad:@8 exe="print Total = @8?"Command | rmawk exe="print Total = @8+"

Example of the command option format

Performs the operation by interpreting the specified option format and classifying them in the following three function formats.• Performs the operation as a filter if there is no "exe="..."" in the

specified option.

Command | rmawk [@expression1] Logical operator [@expression2] …

Example:

Command | rmawk @1-eq:PAIR -a @2-ne:0

• Performs the operation as a testing if there is one "exe="..."" but no "@variable" in the specified option.

rmawk exe="Command line" [@expression1] Logical operator [@expression2] …

Example:

rmawk exe="Command line" @2-eq:PAIR -o @2-eq:PSUS

And performs as an waiting command if "timeout=value" is specified as an option.

rmawk exe="Command line" [@expression1] Logical operator [@expression2] timeout=6

Example:

rmawk exe="Command line" @2-eq:COPY timeout=300

• Other than the above, it performs the multiple "exe="Command line"" commands that include contexts written in multiple formulas and the variable parameters by interpreting the STDIN.

Command | rmawk [@expression1] Logical operator [@expression2] exe="Command line"

Example:

Command | rmawk @3-eq:TAR exe="Command line @1"Command | rmawk @3-eq:TAR exe="Command line(true) @1" -n exe="Command line(false) @1"

Because the command runs with the result of TRUE, multiple command can be performed if you keep writing lines ("exe="command line2"", "exe="command line3"", and so on).


Command | rmawk [@expression1] Logical operator [@expression2] exe="Command line1" exe="Command line2" exe="Command line3"

Example:

Command | rmawk @3-eq:TAR exe="Command line @1" exe="Command line2 @1"Command | rmawk @3-eq:TAR exe="Command line(true) @1" exe="Command line2(true) @1" -n exe="Command line(false) @1"

5

Configuration setting commands 5–1Hitachi Command Control Interface Command Reference

Configuration setting commands

This chapter provides the specifications for the CCI configuration setting (raidcom) commands.

□ raidcom

□ Resource group operation

□ Resource lock operation

□ Resource locking and CCI commands

□ Ranges of command parameters for storage system types

□ raidcom get clpr□ raidcom modify clpr

□ raidcom get command_status□ raidcom reset command_status

□ raidcom add copy_grp□ raidcom delete copy_grp□ raidcom get copy_grp

□ raidcom add device_grp□ raidcom delete device_grp□ raidcom get device_grp

□ raidcom get error_message

□ raidcom add external_grp□ raidcom check_ext_storage external_grp□ raidcom delete external_grp□ raidcom disconnect external_grp□ raidcom get external_grp□ raidcom modify external_grp

□ raidcom discover external_storage

□ raidcom add host_grp□ raidcom delete host_grp□ raidcom get host_grp


5–2 Configuration setting commands

□ raidcom modify host_grp

□ raidcom add hba_wwn□ raidcom delete hba_wwn□ raidcom get hba_wwn□ raidcom reset hba_wwn□ raidcom set hba_wwn

□ raidcom add journal□ raidcom delete journal□ raidcom get journal□ raidcom modify journal

□ raidcom add ldev□ raidcom delete ldev□ raidcom extend ldev□ raidcom get ldev□ raidcom initialize ldev□ raidcom modify ldev

□ raidcom add lun□ raidcom delete lun□ raidcom discover lun□ raidcom get lun

□ raidcom add path□ raidcom get path□ raidcom check_ext_storage path□ raidcom delete path□ raidcom disconnect path

□ raidcom delete pool□ raidcom get pool□ raidcom modify pool□ raidcom monitor pool□ raidcom reallocate pool□ raidcom rename pool

□ raidcom get port□ raidcom modify port

□ raidcom get parity_grp

□ raidcom add rcu□ raidcom delete rcu□ raidcom get rcu□ raidcom modify rcu

□ raidcom add rcu_path□ raidcom delete rcu_path

□ raidcom add ssid□ raidcom delete ssid

□ raidcom add resource□ raidcom modify resource□ raidcom delete resource


□ raidcom get resource□ raidcom lock resource□ raidcom unlock resource□ raidcom map resource□ raidcom unmap resource

□ raidcom add snap_pool□ raidcom get snap_pool

□ raidcom add snapshot□ raidcom delete snapshot□ raidcom modify snapshot□ raidcom get snapshot

□ raidcom add spm_wwn□ raidcom delete spm_wwn□ raidcom modify spm_wwn□ raidcom get spm_wwn□ raidcom monitor spm_wwn

□ raidcom add spm_group□ raidcom delete spm_group□ raidcom modify spm_group□ raidcom get spm_group□ raidcom monitor spm_group

□ raidcom add dp_pool□ raidcom get dp_pool



raidcomSpecifies a configuration change.

Executes by specifying respective parameters and values that are expressed in raidcom add copy_grp on page 5-17 and later.

SyntaxDisplaying help

raidcom { [-h]

Log-in and log-out

raidcom {-login [<user_name> <password>] | -logout] [-s <seq# > | -u <unit#>] [-I[H][M] <instance#>] [-I[TC][SI] <instance#>]

Configuration change: line-by-line mode

raidcom <action> <object> [<param> <value>…] [-fx] [-checkmode <check mode>] [-store <filename>] [-nomsg] [-login [<user_name> <password>] [-resource <resource_grp_id>…] | -logout] [-s <seq# > | -u <unit#>] [-I[H][M] <instance#>] [-I[TC][SI] <instance#>]

Configuration change: transaction mode

raidcom -zt <filename> [-load <work_filename>] [-checkmode <check mode>]


Option Description

[-h ] Displays help of raidcom.

[-login [<user_name> <password>]]

Specifies user authentication for the storage system. Specifies user name and password.If no user authentication is done yet and the -login option is omitted, the input of the user name and the password is required. And, in case of omitting the user name and the password by specifying -login option, the input of the user name and the password is required. The maximum number of the user who can login at same time is 512.

[-logout] Deletes the cache of the session control table in the storage system and logs out from the storage system (command device). Also deletes all the authentication files corresponding to the storage system.At the time of next login, the CCI command requires the user name and the password. If an application that uses the command device exists in the host, the application also requires the user name and the password. If the same user is set for multiple hosts, the session control table of each host is managed so that the logout is applied only to the relevant host.

[-s <seq#>] Specifies the serial number.Note for VSP G1000: When specifying <seq#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

[-u <Unit#>] Specifies the unit ID of command device as HORCM_CMD of configuration file.


ExamplesPerforming user authentication (login) by the user ID: USER01 and the password: PASS01.

# raidcom -login USER01 PASS01

Performing log-out.

# raidcom -logout

Performing user authentication (login) to instance 99 by the user ID: USER01 and the password: PASS01.

# raidcom –login USER01 PASS01 -I 99

Performing syntax check and the context check of the script file (the actual processing is not executed).

# raidcom -zt <script file> -checkmode precheck

Performing syntax check, the context check, and the implementation check of the script file (the actual processing is not executed).

# raidcom -zt < script file> -load <work file> -checkmode precheck

[-I[H][M] <instance#>] or [-I[TC][SI] <instance#>]

Specifies CCI instance number by specifying the command as HORC/HOMRCF or TrueCopy/ShadowImage. If you specify only -I, the command refers to the setting of HORCC_MRCF environment variable.

<action> <object> [<param> <value>…]

Specifies each command name that is expressed in raidcom add copy_grp on page 5-17 and later section and the parameters and values that are required at each operation.

[-fx] Displays the LDEV number in hexadecimal notation.

[ -checkmode < check mode> ]

Specifies when executing Precheck function (execute checking commands only). It specifies the following value.Precheck: When this option is specified, the actual process is not executed for the storage system even if the command is executed.This option is available to specify the setting of $HORCC_NO_EXEC environment variable and $HORCC_CTX_CHK environment variable.

[ -store <file name> ]

Specifies the file name of the configuration file to be created for implementation check.

[-nomsg] Prevents displaying messages. This option is required to be defined on the beginning of the command parameter.

[ -zt <file name> ]

Specifies the script file.

[-load <file name>]

Specifies the file name of the file (Configuration file) that is created for implementation check.

[-resource <resource_grp_id>…]

Limits the operations coverage to the specified resource groups. When this option is specified in reference commands, objects that are in the specified resource groups are displayed. When the resource group specified by this option does not contain the resource specified for executing the command, the command is not executed because of the EX_EGPERM error.

Option Description



Method for specifying LDEV numberThe methods for specifying LDEV numbers are shown in the following table.

Methods for specifying multiple LDEVs

Methods for specifying multiple LDEVs by LDEV IDs

The methods for specifying multiple LDEV IDs in a single command are shown below. Some methods do not apply to some commands.

-ldev_id 300-305-ldev_id 0x12C-0x131-ldev_id 01:2C-01:31-ldev_id 300 -cnt 6-ldev_id 300 301 302 303 304 305

Method for specifying LDEVs by device group

When you configure multiple LDEVs for pools or journals (for example, changing the resource group), you must issue the command to each LDEV. However, if you define LDEVs that configure pools or journals, you can issue the command to all LDEVs defined as a device group by specifying each device group at a time.

If you issue the command to LDEVs by specifying a device group, the command is executed in each LDEV registered in the device group. If an error occurs in an LDEV while the command is being executed, the execution of command stops at the LDEV where the error occurred. The command is not executed in the remaining LDEVs. If an error occurs, solve the error. Then restore the LDEV and issue the command to all remaining LDEVs.• Creating a pool by specifying a device group:

# raidcom add device_grp -device_grp_name dg_pool1 data1 -ldev_id 512 513 514 515

# raidcom add dp_pool -pool_id 2 -grp_opt ldev -device_grp_name dg_pool1

• Creating a journal by specifying a device group:

# raidcom add device_grp -device_grp_name dg_jnl1 data1 -ldev_id 512 513 514 515

# raidcom add journal -journal_id 2 -grp_opt ldev -device_grp_name dg_jnl1

Operations where multiple LDEVs can be specifiedYou can use "-ldev_id <ldev#>" to specify multiple LDEVs at the same time in the following operations only:

Specification method Example

Decimal number -ldev_id 300

Hexadecimal number -ldev_id 0x12C-ldev_id 01:2C


(a) Displaying LDEV information

# raidcom get ldev -ldev_id 100-103

# raidcom get ldev -ldev_id 100 -cnt 4

Note: Specifying multiple LDEV as follows cannot be performed:#raidcom get ldev -ldev_id 100 101 103

(b) Creating a journal

# raidcom add journal -journal_id 1 -ldev_id 265 266 267 268

# raidcom add journal -journal_id 1 -ldev_id 265-268

# raidcom add journal -journal_id 1 -ldev_id 265 -cnt 4

(c) Creating a pool

Creating a pool for Copy-on-Write Snapshot:

# raidcom add snap_pool -pool 1 -ldev_id 365 366 367

# raidcom add snap_pool -pool 1 -ldev_id 365-367

# raidcom add snap_pool -pool 1 -ldev_id 365 -cnt 3

Creating a pool for Dynamic Provisioning or Dynamic Provisioning for Mainframe:

# raidcom add dp_pool -pool 1 -ldev_id 465 466 467

# raidcom add dp_pool -pool 1 -ldev_id 465-470

# raidcom add dp_pool -pool 1 -ldev_id 465 -cnt 5

(d) Creating a device group

# raidcom add device_grp -device_grp_name DevG2 dev101 -ldev_id 101 105 201

# raidcom add device_grp -device_grp_name DevG2 dev101 -ldev_id 101-105

# raidcom add device_grp -device_grp_name DevG2 dev101 -ldev_id 101 -cnt 5

(e) Deleting a device group

# raidcom delete device_grp -device_grp_name DevG3 -ldev_id 200 201 204

# raidcom delete device_grp -device_grp_name DevG3 -ldev_id 200-204

# raidcom delete device_grp -device_grp_name DevG3 -ldev_id 200 -cnt 5



Specifying and displaying the VSP G1000 serial numberWhen specifying <seq#> for VSP G1000 in CCI, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345. The serial number for VSP G1000 is displayed by CCI with a “3” added to the beginning (for example, “312345” = serial number 12345).

For GUI operations (Hitachi Command Suite, HDvM - SN) use the five-digit serial number for the VSP G1000 (do not add “3” in the GUI).

Resource group operationWhen you have multiple resource group authorities, use the -resource option to see the resource group information.

Examples

# raidcom get resourceRS_GROUP RGID stat Lock_owner Lock_host Serial#meta_resource 0 Unlocked - - 64568RSG_CLI1 1 Unlocked - - 64568RSG_CLI2 2 Unlocked - - 64568

# raidcom get portPORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWN PHY_PORTCL1-A FIBRE ELUN AUT EF N FCAL N 0 64568 50060e8006fc3800 -CL1-B FIBRE TAR AUT EF N FCAL N 0 64568 50060e8006fc3801 -CL1-C FICON TAR - - - - - 0 64568 50060e8006fc3802 -CL1-D FICON TAR - - - - - 0 64568 50060e8006fc3803 -

# raidcom get port -resource 1PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWN PHY_PORTCL1-B FIBRE TAR AUT EF N FCAL N 0 64568 50060e8006fc3801 -CL1-C FICON TAR - - - - - 0 64568 50060e8006fc3802 -

# raidcom get port -resource 2PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWN PHY_PORTCL1-A FIBRE ELUN AUT EF N FCAL N 0 64568 50060e8006fc3800 -CL1-D FICON TAR - - - - - 0 64568 50060e8006fc3803 -

Resource lock operationWhen you use the following commands, lock the resource that is allocated to resource groups before executing the command.• add• delete• modify• initialize• check_ext_storage• disconnect• set• reset• reallocate


• monitor

The following examples show locking resource groups, executing commands, and then unlocking resource groups.

Examples• Performing a user authentication by User ID: USER01, Password:

PASS01.

# raidcom -login USER01 PASS01

• Locking a resource group: rsg001.

# raidcom lock resource -resource_name rsg001

• Creating LDEV#100 and #101.

# raidcom add ldev -parity_grp_id 33-16 -ldev_id 100 -capacity 10g

# raidcom add ldev -parity_grp_id 33-16 -ldev_id 101 -capacity 10g

• Unlocking resource group: rsg001

# raidcom unlock resource -resource_name rsg001

Resource locking and CCI commandsIf you execute a CCI command when the specified resource is locked, the specified resource groups cannot be used by other users. Commands can be executed when the specified resources are not locked. However, if another user locks the resource, CCI commands will result in error. The following table shows the relations between CCI commands and resources that need to be locked, except for the required options for the commands. In the following table:• Res. group: resource group• Lock/auth: Resource locking and resource authority are required.• Auth: Only resource authority check is specified.

Relation between commands and resources that need to be locked

Res. group Port Host

groupParity group

External

volume/VDEV

LDEV Command Option

- - - - - Lock/auth

raidcom add copy_grp

-

- - - - - Lock/auth

raidcom delete copy_grp

-

- - - - - Auth raidcom get copy_grp

-



- - - - - Lock/auth

raidcom add device_grp

-

- - - - - Lock/auth

raidcom delete device_grp

-

- - - - - Auth raidcom get device_grp

-

- Lock/auth

- - - - raidcom add external_grp

-

- - - - Lock/auth

- raidcom check_ext_storage external_grp

-

- - - - Lock/auth

Auth raidcom check_ext_storage external_grp

-ldev_id <ldev#>

- - - - Lock/auth

- raidcom delete external_grp

-

- - - - Lock/auth

- raidcom disconnect external_grp

-

- - - - Lock/auth

Auth raidcom disconnect external_grp

-ldev_id <ldev#>

- - - - Auth - raidcom get external_grp

-

- - - - Lock/auth

- raidcom modify external_grp

-

- Auth - - - - raidcom discover external_storage

-

- - Lock/auth

- - - raidcom add host_grp

-

- - Lock/auth

- - - raidcom delete host_grp

-

- Auth Auth - - - raidcom get host_grp

-

- - Lock/auth

- - - raidcom modify host_grp

-

- - Lock/auth

- - - raidcom add hba_wwn

-

- - Lock/auth

- - - raidcom delete hba_wwn

-

- Auth Auth - - - raidcom get hba_wwn

-

- - - - - Lock/auth

raidcom add journal -

- - - - - Lock/auth

raidcom delete journal

-

- - - - - Auth raidcom get journal -


groupParity group

External

volume/VDEV

LDEV Command Option


- - - - - Lock/auth

raidcom modify journal

-

- - - Lock/auth

- Lock/auth

raidcom add ldev -parity_ grp_id <gno-sgno>

- - - - Lock/auth

Lock/auth

raidcom add ldev -external_ grp_id <gno-sgno>

- - - - - Lock/auth

raidcom add ldev -

- - - - - Lock/auth

raidcom delete ldev -

- - - - - Lock/auth

raidcom extend ldev

-

- - - - - Auth raidcom get ldev -

- - - - - Lock/auth

raidcom initialize ldev

-

- - - - - Lock/auth

raidcom modify ldev

-

- - Lock/auth

- - Lock/auth

raidcom add lun -

- - Lock/auth

- - Lock/auth

raidcom delete lun -

- Auth - - - - raidcom discover lun

-

- - Auth - - - raidcom get lun -

- Lock/auth

- - - - raidcom add path -

- Lock/auth

- - - - raidcom check_ext_storage path

-

- Lock/auth

- - - - raidcom delete path -

- Lock/auth

- - - - raidcom disconnect path

-

- - - - - Auth raidcom get path -

- - - - - Lock/auth

raidcom delete pool -

- - - - - Auth raidcom get pool -

- - - - - Lock/auth

raidcom modify pool

-

- Auth - - - - raidcom get port -

- Lock/auth

- - - - raidcom modify port

-


groupParity group

External

volume/VDEV

LDEV Command Option



- - - Auth - - raidcom get parity_grp

-

- Lock/auth

- - - - raidcom add rcu -

- Lock/auth

- - - - raidcom delete rcu -

- Auth - - - - raidcom get rcu -

- Lock/auth

- - - - raidcom modify rcu -

- Lock/auth

- - - - raidcom add rcu_path

-

- Lock/auth

- - - - raidcom delete rcu_path

-

Auth - - - - - raidcom get resource

-

Auth - - - - - raidcom lock resource

-

Auth - - - - - raidcom unlock resource

-

- - - - - Lock/auth

raidcom add snap_pool

-

- - - - - Auth raidcom get snap_pool

-

- - - - - Lock/auth

raidcom add dp_pool

-

- - - - - Auth raidcom get dp_pool

-

- - Lock/auth

- - - raidcom set hba_wwn

-

- - Lock/auth

- - - raidcom reset hba_wwn

-

- - - - - Lock/auth

raidcom monitor pool

-

- - - - - Lock/auth

raidcom reallocate pool

-

- - - - - - raidcom get command_status

-

- - - - - - raidcom reset command_status

-

- - - - - - raidcom add resource

-

Lock/auth

- - - - Lock/auth

raidcom add resource

-ldev_id <ldev#>


groupParity group

External

volume/VDEV

LDEV Command Option


Ranges of command parameters for storage system typesThe following table specifies the valid ranges of command parameters for the storage system types. CCI commands might be accepted even if the specified value is not within the valid range for the storage system type.

Lock/auth

Lock/auth

- - - - raidcom add resource

-port <port#>

Lock/auth

- Lock/auth

- - - raidcom add resource

-port <port#> <host group name>

Lock/auth

- - Lock/auth

- - raidcom add resource

-parity_grp_id <gno-sgno>

Lock/auth

- - - Lock/auth

- raidcom add resource

-external_ grp_id <gno-sgno>

Auth - - - - - raidcom delete resource

-

Lock/auth

- - - - Lock/auth

raidcom delete resource

-ldev_id <ldev#>

Lock/auth

Lock/auth

- - - - raidcom delete resource

-port <port#>

Lock/auth

- Lock/auth

- - - raidcom delete resource

-port <port#> <host group name>

Lock/auth

- - Lock/auth

- - raidcom delete resource

-parity_grp_id <gnosgno>

Lock/auth

- - - Lock/auth

- raidcom delete resource

-external_ grp_id <gno-sgno>


groupParity group

External

volume/VDEV

LDEV Command Option

Parameter ItemStorage system type

VSP HUS VM VSP G1000

-ldev_id LDEV number 0 - 65279 0 - 16383 0 - 65279

-parity_grp_id parity group number

gno : 1 - 32sgno : 1 - 16

gno : 1 - 16sgno : 1 - 32

gno : 1 - 24sgno : 1 - 24

-path_grp external volume path group number

0 - 63232 0 - 14080 0 - 63232

-mp_blade_id MP blade ID 0 - 7 0 - 3 0 - 16



raidcom get clprDisplays the CLPR information for the storage system.

Syntaxraidcom get clpr

Options and parametersNone

Examples# raidcom get clprCLPR CLPR_NAME TC_CAP(MB) TU_CAP(MB) WP_CAP(MB) SF_CAP(MB) U(%) W(%) S(%)001 Oracle_DB_PROD 20000 10000 2000 0 50 10 0003 Oracle_DB_BACK 10000 5000 500 0 50 5 0

CLPR: CLPR number (decimal)

CLPR_NAME: nickname of the CLPR

TC_CAP(MB): capacity of cache memory of the CLPR

TU_CAP(MB): used capacity of cache memory of the CLPR

WP_CAP(MB): capacity of write pending data of the CLPR

SF_CAP(MB): capacity of sidefiles of the CLPR

U(%): usage rate of cache memory of the CLPR

W(%): rate of write pending data of the CLPR

S(%): usage rate of sidefiles of the CLPR

raidcom modify clprModifies a CLPR.

Syntaxraidcom modify clpr -clpr <clpr#> { -ldev_id <ldev#> | -parity_grp_id <gno-sgno> | -external_grp_id <gno-sgno>}


Option Description

-clpr <clpr#> Specifies a CLPR number (0-31).For example:• -clpr 2


ExamplesMoving the LDEV 02:00 to the CLPR number 2.

# raidcom modify clpr -clpr 2 -ldev_id 0x0200

Moving the parity group 33-16 to the CLPR number 2

# raidcom modify clpr -clpr 2 -parity_grp_id 33-16

Moving the external volume group 1-1 to the CLPR number 2.

# raidcom modify clpr -clpr 2 -external_grp_id 01-01

raidcom get command_statusIt displays an error information of the configuration setting command (asynchronous command) to be executed asynchronously.

When an error occurs with the execution of an asynchronous command, the total number of errors or error information such as error codes (SSB1 and SSB2) are stored in the storage system at the first occurrence. After executing asynchronous command, check the error information by executing this command.

However, an error from the second time occurrence, error codes of SSB1 and SSB2 are not stored. To be able to refer the error code when an error occurs, reset the error information that is stored by the storage system by executing raidcom reset command_status before and after executing asynchronous command.

Syntaxraidcom get command_status [-time <time(sec)>]

-ldev_id <ldev#>

Specifies an LDEV number (0-65279).For example:• -ldev_id 200You cannot specify the LDEV that configures a LUSE by using this command. For other notes, see the Hitachi Virtual Partition Manager User Guide.


Specifies a parity group number (gno: 1-32, sgno: 1-16).For example:• 3-1

-external_grp_id <gno-sgno>

Specifies an external volume group number (gno: 1-16384, sgno: 1-4096).For example:• 52-11

Option Description




ExamplesDisplaying error information of the asynchronous command.

# raidcom get command_statusHANDLE SSB1 SSB2 ERR_CNT Serial# Description7E30 2E20 6000 4 64034 The pool ID is not installed

Description of each column in output example

HANDLE: handle number that uniquely identifies the user

SSB1: SSB1 error code. For details about error codes, see the Command Control Interface User and Reference Guide.

SSB2: SSB2 error code. For details about error codes, see the Command Control Interface User and Reference Guide.

ERR_CNT: total number of errors in this user handle

Serial#: serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Description: Error information. If no error occurred, a hyphen (-) is displayed.

Returned Value: Either of the following returned values is returned to exit (), which allows users to check the execution results using a user program or a script.• 0: Normal Termination• 1: One or more errors occurred.

Abnormal terminationEX_EWSTOT : Timeout while waiting the result of the command execution

raidcom reset command_statusResets the error information of the configuration setting command that is stored in the storage system and executed asynchronously (Asynchronous command).

Syntaxraidcom reset command_status

Option Description

[-time <time(sec)>]

Specifies waiting time to complete the process of asynchronous command.If this option is omitted, the default waiting time (CMD_DEF_TMOUT: 7200 sec.) is set.


Options and parametersNone

ExamplesResetting the error information of the asynchronous command.

# raidcom reset command_status

raidcom add copy_grpCreates a copy group.

Syntaxraidcom add copy_grp -copy_grp_name <copy group name> <device group name> [<device group name>] [-mirror_id <mu#> -journal_id <journal ID#>]


ExampleCreating a copy group (ora) by device groups (grp1, grp2).

# raidcom add copy_grp -copy_grp_name ora grp1 grp2

raidcom delete copy_grpDeletes the specified copy group.

Syntaxraidcom delete copy_grp -copy_grp_name <copy group name>

Option Description

-copy_grp_name <copy group name><device group name>[<device group name>]

Specifies the device group (maximum 32 characters) configuring a copy group (maximum 32 characters). You can specify up to two device group names. If you specify more than two, the option is ignored.For a copy group for an ShadowImage pair, specify two device groups.For a copy group for a TrueCopy pair, specify only one device group for the relevant storage system side (primary/main or secondary/remote).

[-mirror_id <mu#> ]

Specifies the mirror ID.If this option is omitted (by raidcom get copy_grp), "-" is displayed.

[ -journal_id <journal ID#> ]

Specifies the journal number (0-255).If this option is omitted (by raidcom get copy_grp), "-" is displayed.




ExampleDeleting the copy group: ora.

# raidcom delete copy_grp -copy_grp_name ora

raidcom get copy_grpDisplays the information of the specified copy group.

Syntaxraidcom get copy_grp

Options and parametersNone.

ExamplesDisplaying copy group information.

# raidcom get copy_grpCOPY_GROUP LDEV_GROUP MU# JID# Serial#ora grp1 0 - 64034ora grp2 0 - 64034

Description of each column in output example:

COPY_GROUP: Copy group name

LDEV_GROUP: Device group name that composes copy group

MU#: Mirror ID to which the device group belongs. If -mirror_id is not specified at the creation, "-" is displayed.

JID#: Journal number to which device group belongs. If -journal_id is not specified at the creation, "-" is displayed.

Serial#: Product serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

raidcom add device_grpAssigns a device name to the specified LDEV, and creates a device group. If the group already exists, the LDEV is added to the group. If the LDEV also already exists in the specified device group, the specified LDEV name is set.

Option Description

-copy_grp_name <copy group name>

Specifies the name of the copy group (maximum 32 characters).


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


ExampleAssigning a device name: data1 to an LDEV: 400 and adding it to the device group: grp1.

# raidcom add device_grp -device_grp_name grp1 data1 -ldev_id 400

raidcom delete device_grpDeletes the specified LDEV from the specified group. When the last LDEV is deleted, the device group is also deleted.

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


Option Description

device_grp_name <device group name><device name>

Specifies the device group name (maximum 32 characters) and the device name in the device group (maximum 32 characters). If multiple LDEVs are specified, the same device name is set for all of them.

-ldev_id <ldev#> …

Specifies the LDEV number (0-65279).When you specify an LDEV that is part of a LUSE volume, all LDEVs in the LUSE volume have the same name. For example:• -ldev_id 200• -ldev_id 100-110• -ldev_id 100 -cnt 10Up to 64 of LDEVs can be specified.When you specify an LDEV in a LUSE volume, the number of LDEVs in the LUSE volume is included.

[ -cnt <count> ] Specifies the count (2-64).If this option is omitted, the count is set to one.

Option Description

-device_grp_name <device group name>

Specifies the device group name (maximum 32 characters)



ExampleDeleting the LDEV400 from the device group: grp1.

# raidcom delete device_grp -device_grp_name grp1 -ldev_id 400

raidcom get device_grpDisplays the LDEV information for the specified device group, or lists all device groups.

Syntaxraidcom get device_grp [-device_grp_name <device group name>]


ExamplesDisplaying device group information.

# raidcom get device_grpLDEV_GROUP Serial#grp1 64034grp2 64034grp3 64034

Displaying device group information: grp1.

# raidcom get device_grp -device_grp_name grp1LDEV_GROUP LDEV_NAME LDEV# Serial#grp1 data1 400 64034grp1 data2 401 64034



Specifies the LDEV number (0-65279). For example:• -ldev_id 200• -ldev_id 100-110• -ldev_id 100 -cnt 10Up to 64 of LDEVs can be specified. When you specify an LDEV in a LUSE volume, the number of LDEVs in the LUSE volume is included.

[-cnt <count> ] Specifies the count (2-64).If this option is omitted, the count is set to one.

Option Description

Option Description

[ -device_grp_name <device group name> ]

Displays the device (LDEV) information for the specified device group (maximum 32 characters).If this option is omitted, the list of the registered device groups is displayed.


LDEV_GROUP: Device group name

LDEV_NAME: Device name in the device group

LDEV#: LDEV number


raidcom get error_messageDisplays the error message for the specified error code.

Syntaxraidcom get error_message -ssb <ssb1> <ssb2>


ExampleDisplaying the error message for the error code whose SSB1 is 0x2E00 and SSB2 is 0x0023.

# raidcom get error_message -ssb 0x2E00 0x0023CAUSE : Volume capacity is too small.

raidcom add external_grpAdds an external volume to the specified external volume group, and connects to an external LUN on the specified external port/wwn. Only one external VOL is added in each operation. If the external volume group already exists, the external volume is added to the external volume group.

This command is executed asynchronously with the command input. Check the completion of this process using the raidcom get command_status command.

Syntaxraidcom add external_grp -path_grp <path group#> -external_grp_id <gno-sgno> -port <port#> -external_wwn <wwn strings> -lun_id <lun#> [-emulation <emulation type>[-clpr <clpr#>] [-external_attribute migration]]

Option Description

-ssb <ssb1> <ssb2>

Specifies the error code as a hexadecimal number (add the 0x prefix).<ssb1>: Specifies SSB1 of the error code.<ssb2>: Specifies SSB2 of the error code.




Option Description

-path_grp <path group#>

Specifies the external VOL path group number (0-63231).


Specifies the external volume group number (gno:1-16384, sgno:1-4096). For example:• 52-11

-port <port#> Specifies the port number. Specifies the port number whose attribute is External. For example:• CL1-ADisplays an external port.

-external_wwn <wwn strings>

Specifies the WWN value (hexadecimal value) of the external storage system in 8 bytes. The value can be split in increments of 4 bytes by "," (commas). For example:• 210000e08b0256f8• 210000e0,8b0256f8

-lun_id <lun#> Displays LUN (0-2047) of the external storage system port.

[-emulation <emulation type> ]

Specifies the emulation type. If this option is omitted, OPEN-V is used.The valid values for <emulation type> are:• OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-K, OPEN-L, OPEN-V• 3390-1, 3390-2, 3390-3, 3390-A, 3390-3A, 3390-3B, 3390-

3C, 3390-3R, 3390-9, 3390-9A, 3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, 3390-LC, 3390-M, 3390-MA, 3390-MB, 3390-MC, 3390-V

• 3380-3, 3380-3A, 3380-3B, 3380-3C• 6586-G, 6586-J, 6586-K, 6586-KA, 6586-KB, 6586-KC6588-

1, 6588-3, 6588-9, 6588-3A, 6588-3B, 6588-3C, 6588-9A, 6588-9B, 6588-9C, 6588-L, 6588-LA, 6588-LB, 6588-LC

Some emulation types cannot be specified according to the type of device.Caution:You can specify 3390-3 or 3390-3R as the emulation type, but these are unable to be mixed. You can specify the 3380 series or the 3390 series as the emulation type for each parity group, but they are unable to be mixed for each 32 address boundary because of the OS restriction. You can specify the 6588 series or the 6586 series as the emulation type for each parity group, but they are unable to be mixed for each 32 address boundary because of the OS restriction.

[-clpr <clpr#>] Specifies the CLPR number.

[-external_attribute migration]

Specifies if an attribute of nondisruptive migration functions is set.


ExampleMapping an LU: 0 defined to the external storage system port: 50060e80,05fa0f36 connected to the port: CL1-A (external port) by the external volume group #1-1 and path group #1.

# raidcom add external_grp -path_grp 1 -external_grp_id 1-1 -port CL1-A -external_wwn 50060e80,05fa0f36 -lun_id 0

raidcom check_ext_storage external_grpSpecifies the external volume group, check the connection for the external VOL, and then restart using. Only one external VOL is operated in each operation.

An LDEV or device group can be specified instead of an external volume group.• If an LDEV is specified, CCI finds the external volume groups to which

the specified LDEV belongs and displays the result.• If a device group is specified, CCI finds the external volume groups to

which the specified device group belongs and displays the result.

If no LDEV exists in the external volume, the command is rejected with EX_ENOOBJ.

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


Option Description



-ldev_id <ldev#> Specifies the LDEV number (0-65279). For example:• -ldev_id 200

-grp_opt <group option>

Specifies the device information extracted from the LDEV belonging to the device group. Specify "ldev" (fixed). The information about LDEV belonging to the device group is used.

-device_grp_name <device group name> [<device name>]

Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all of the LDEVs in the device group are operated.



ExamplesExecuting the confirmation of existence and the LDEV recovery for the external volume group #1-1.

# raidcom check_ext_storage external_grp -external_grp_id 1-1

Executing the confirmation of connection and the LDEV recovery for the external volume group including the external volume (LDEV:200).

# raidcom check_ext_storage external_grp -ldev_id 200

Executing the confirmation of connection and the LDEV recovery for the external volume group including the LDEV belonging to the device group: grp1.

# raidcom check_ext_storage external_grp -grp_opt ldev -device_grp_name grp1

raidcom delete external_grpReleases the mapping of the external volume to delete the registered external VOLs from the configuration. Only one external VOL is deleted in each operation. When the last external volume is deleted, the path group is also deleted.

This command is executed asynchronously with the command input. Check the completion of this process using the raidcom get command_status command.

Syntaxraidcom delete external_grp -external_grp_id <gno-sgno>


ExampleDeleting the external volume group #1-1.

# raidcom delete ext_grp -ext_grp 01-01

raidcom disconnect external_grpDisconnects the connection to the external volumes. Only one external VOL is operated in each operation.

You can specify an LDEV defined for the external volume group or a device group to which the LDEV in the external volume group belongs instead of the external volume group.

Option Description




• If an LDEV is specified, CCI finds the external volume groups to which the specified LDEV belongs and displays the result.

• If a device group is specified, CCI finds the external volume groups to which the LDEV in the specified device group belongs and displays the result.

If no LDEV exists in the external volume group, the command is rejected with EX_ENOOBJ.

Before finishing the write processing from the cache to the external volume, the processing of raidcom disconnect external_grp command ends. Check the status (STS) using the raidcom get path command, and confirm the finishing of the write processing (destaging). (destaging). The following are the statuses (STS) after executing the raidcom disconnect external_grp command.• NML: It means the previous status of receiving the request by the

raidcom disconnect external_grp command.• SYN: Write processing (destaging) is in process.• DSC: Write processing (destaging) has finished.• BLK: Write processing (destaging) has failed.

For details, see raidcom get path on page 5-75.

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


ExamplesDisconnect the connection to the external volume group #1-1.

Option Description





Specifies the device information extracted from the LDEV belonging to the device group.Specify "ldev" (fixed). The information of LDEV belonging to the device group is used.


Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all of the LDEVs belonging in the device group are operated.



# raidcom disconnect external_grp -external_grp_id 1-1

Disconnect the connection to the external volume group including the external volume (LDEV:200) to "blocked".

# raidcom disconnect external_grp -ldev_id 200

Disconnect the connection to the external volume group including the LDEV belonging to the device group: grp1.

# raidcom disconnect external_grp -grp_opt ldev -device_grp_name grp1

raidcom get external_grpDisplays the information of registered external volumes.

Syntaxraidcom get external_grp [-external_grp_id <gno-sgno>]


ExamplesDisplaying external volume information (The display might not be in ascending order.).

#raidcom get external_grpT GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL E_TYPE SL CL DRIVE_TYPEE 1-1 0 0 100 - OPEN-V 0 0 OPEN-VE 1-2 0 0 30 - OPEN-V 0 0 OPEN-V


T: Type of the volume group

R: Parity group, E: External volume group

GROUP: External volume group number

Num_LDEV: number of LDEV assigned to the external volume group

U(%): usage rate of the external volume group

AV_CAP(GB): available capacity (free space) for the external volume group

R_LVL: RAID level of the parity group. As the external volume group is not relevant, "-" (bar) is displayed.

Option Description

[-external_grp_id <gno-sgno> ]

Specifies the external volume group number (gno:1-16384, sgno:1-4096).If this option is omitted, the list of the registered external volumes is displayed.If this option is specified. the LDEV information defined for the specified external volume group is displayed. For example:52-11


E_TYPE: base emulation type of the external volume group

SL: SLPR to which the external volume group belongs (always displays 0)

CL: CLPR to which the external volume group belongs

DRIVE_TYPE: Product ID included in the SCSI Inquiry command of the external volume group

Displaying the external volume information by specifying the external volume group:

# raidcom get external_grp -external_grp_id 01-01T GROUP P_NO LDEV# STS LOC_LBA SIZE_LBA Serial#E 1-1 0 - NML 0x000000000000 0x000000003f00 64034E 1-1 1 200 NML 0x000000003f00 0x000000010000 64034E 1-1 2 201 REG 0x000000013f00 0x000000010000 64034E 1-1 3 - DEL 0x000000023f00 0x0000f0000000 64034


T: type of the volume group

R: Parity group, E: External volume group

GROUP: external volume group number.

P_NO: partition number in this external volume group.

LDEV#: LDEV number assigned to this external volume group.

STS: displays the following status.

- NML: an LDEV is installed.

- REG: an LDEV is being created.

- DEL: an LDEV is being deleted.

LOC_LBA: starting point of LBA for this partition on this external volume group, in blocks (512 bytes).

SIZE_LBA: partition size of this external volume group, in blocks (512 bytes).


raidcom modify external_grpChanges the attribute of external volume options (cache mode, cache inflow control mode, and MP blade ID setting).

Syntaxraidcom modify external_grp -external_grp_id <gno-sgno> {-cache_mode {y | n} | -cache_inflow {y | n} | -mp_blade_id <mp#>} | -load_balance <mode> |-alua_switch <y|n>




ExamplesTurning the cache mode of the external volume group #01-01 ON.

# raidcom modify external_grp -external_grp_id 01-01 -cache_mode y

Enabling the Cache Inflow Control mode of the external volume group #01-01 ON.

# raidcom modify external_grp -external_grp_id 01-01 -cache_inflow y

Changing the MP blade ID of the external volume group #01-01 to "3".

# raidcom modify external_grp -external_grp_id 01-01 -mp_blade_id 3

raidcom discover external_storageSearches the port information on the external storage system connected to the external port.

Option Description



-cache_mode {y | n}

Specifies whether to use the cache mode for an external volume. If the relevant external volume group is split into the multiple LDEVs and these LDEVs are allocated to the pools, you cannot change the setting for the cache mode.• y: Write cache enabled (E)• n: Write cache disabled (D)• through: Cache through (T). Available only when the attribute

of the relevant external volume is NDM.• sync: Write Sync mode (S). Available only when the attribute of

the relevant external volume is NDM.

-cache_inflow {y | n}

Specifies whether to use the Cache Inflow Control mode for an external volume. If the external volume group consists of multiple LDEVs and these LDEVs are allocated to the pool, you cannot change this parameter.• y : Cache Inflow Control mode enabled (E)• n : Cache Inflow Control mode disabled (D)

-mp_blade_id <mp#>

Specifies the MP blade ID (0-7). For example:-mp_blade_id 2

-load_balance <mode>

Specifies load distribution mode of the alternate paths.• normal: normal round robin• extended: extended round robin• disable: disables the alternate paths

-alua_switch <y|n>

Specifies whether the ALUA mode is used or not.


Syntaxraidcom discover external_storage -port <port#>


ExampleDisplaying the external storage system ports from the port: CL1-A.

# raidcom discover external_storage -port CL1-APORT WWN PM USED Serial# VENDOR_ID PRODUCT_IDCL1-A 50060e8005fa0f36 M YES 60010 HITACHI VSPCL1-A 50060e8005fa0f38 M YES 60010 HITACHI VSP


PORT: Displays the external port number of the storage system.

WWN: Displays the WWN which can be referred to from the port.

PM: Displays the path mode for external path.• M: Multi• S: Single• A: APLB

USED: Displays whether this target WWN is used or not.• YES: Used• NO: Not used

Serial#: Product serial number of the external storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

VENDOR_ID: Displays the VENDOR_ID of the external storage system. "OTHER" is displayed if an unsupported external storage system is connected.

PRODUCT_ID: Displays the PRODUCT_ID of the external storage system. "OTHER" is displayed if an unsupported external storage system is connected.

raidcom add host_grpCreates a host group on the specified port.

If the specified port does not exist, the command is rejected with EX_ENOOBJ.

Option Description

-port <port#> Specifies the port number. Specifies the port number where the attribute is "ELUN(External)". For example:• CL1-ADisplays an external port.



If the specified port/host group already exists, the existing host group name is changed to the specified host group name.

The specified host group name must be unique in a port.

Syntaxraidcom add host_grp -port <port#> -host_grp_name <host group name>


ExamplesCreating a host group ID: 3, the host group name: a host group of Win_export, to the port: CL4-E.

# raidcom add host_grp -port CL4-E-3 -host_grp_name Win_export

Creating a host group ID: allocated automatically, the host group name: a host group of Win_export, to the port: CL4-E.

# raidcom add host_grp -port CL4-E -host_grp_name Win_export

raidcom delete host_grpDeletes the specified host group and all WWN/LUNs setting on the specified port. If LUSE is defined, release the LUSE volume.


Syntaxraidcom delete host_grp -port <port#> [<host group name>]


Option Description

-port <port#> Specifies the port number and the host group ID. For example:CL1-A-g (g is from 0 to 254)

-host_grp_name <host group name>

Specifies the HOST group name.Up to 64 characters can be set by CCI. If more than 64 characters are set, commands that specify host group name by CCI cannot be executed.

Option Description

-port <port#> [<host group name>]

Specifies the port number, host group ID, and host group name. If the host group name is more than 64 characters, use the host group ID. For example:• CL1-A-g (g is from 0 to 255)• CL1-A Linux_X86


ExamplesDeleting the host group of port CL4-E, host group #7.

# raidcom delete host_grp -port CL4-E-7

Deleting the host group of port CL4-E, host group name: host group of Win_export.

# raidcom delete host_grp -port CL4-E Win_export

raidcom get host_grpDisplays the information about all host groups that are defined on the specified port.

Syntaxraidcom get host_grp -port <port#> [<host group name>] [-key <keyword>]


ExamplesDisplaying the host group information set for the port: CL4-E.

# raidcom get host_grp -port CL4-EPORT GID GROUP_NAME Serial# HMD HMO_BITsCL4-E 0 Linux_x86 63528 LINUX/IRIX 2 13CL4-E 1 Solaris 63528 SOLARIS 2 22CL4-E 2 HP-UX 63528 HP-UX 40CL4-E 3 Win_export 63528 WIN_EX 7CL4-E 5 DEC 63528 TRU64 14CL4-E 6 OpenVMS 63528 OVMSCL4-E 254 RMTEST 63528 LINUX 7

Displaying only the host group IDs that are allocated to available resource groups for users.

# raidcom get host_grp -port CL4-E -key host_grpPORT GID GROUP_NAME Serial# HMD HMO_BITsCL4-E 0 Linux_x86 63528 LINUX/IRIX 2 13CL4-E 1 Solaris 63528 SOLARIS 2 22

Option Description


Specifies the port number, host group ID, and host group name. If the host group name is more than 64 characters, use the host group ID.For example:• CLI-A• CL1-A-g (g is from 0 to 254)• CL1-A Linux_X86If you specified the above settings, the information about all host groups that are defined on the specified port is displayed regardless of the examples.

[-key <keyword>]

Specifies when displaying unavailable host group IDs. Specify host_grp in <keyword>.



CL4-E 2 HP-UX 63528 HP-UX 40CL4-E 3 Win_export 63528 WIN_EX 7CL4-E 5 DEC 63528 TRU64 14CL4-E 6 OpenVMS 63528 OVMSCL4-E 10 - 63528 -CL4-E 11 - 63528 -CL4-E 12 - 63528 -CL4-E 13 - 63528 -CL4-E 254 RMTEST 63528 LINUX 7

PORT: Displays the port number.

GID: Displays the host group ID of a port.

GROUP_NAME: Displays the host group name of a port.


HMD: Displays the following HOST MODE for the host adapter setting on host group.• HP-UX, SOLARIS, AIX, WIN, LINUX/IRIX, TRU64, OVMS, NETWARE, HI-

UX• VMWARE, HP-UX, VMWARE_EX, WIN_EX, UVM

HMO_BITs: Displays the host mode options of the host group. For details about host mode options, see the Provisioning Guide or LUN Manager User Guide for the storage system.

raidcom modify host_grpSets a host mode to the host group on the specified port.

To set a host mode option, specify the "-host_mode_opt" option.

To reset a host mode option, specify the "-host_mode_opt 100" .

If the specified host group does not exist, the command is ignored.

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


Option Description

-port <port#>[<host group name>]



ExamplesSetting the host mode: HP-UX for the port: CL4-E, the host group: #2.

# raidcom modify host_grp -port CL4-E-2 -host_mode HP-UX

Setting the host mode: HP-UX and the host mode option: 2, 13 for the port: CL4-E, the host group: #2.

# raidcom modify host_grp -port CL4-E-2 -host_mode HP-UX -host_mode_opt 2 13

Clearing the host mode options of the host mode: HP-UX of the port: CL4-E, the host group: #2.

# raidcom modify host_grp -port CL4-E-2 -host_mode HP-UX -host_mode_opt 100

raidcom add hba_wwn Registers the WWN of the host adapter to the host group on the specified port.

If the specified WWN already exists, this command is ignored.

-host_mode <host mode>

Specifies the host mode using the following strings. For details about host modes, see the Provisioning Guide or LUN Manager User Guide for the storage system.• LINUX or IRIX• VMWARE• HP-UX• OVMS• TRU64• SOLARIS• NETWARE• WIN• AIX• VMWARE_EX• WIN_EX• UVM

[ -host_mode_opt <host mode option>… ]

Host mode optionThis parameter is used when setting the option bits for the host mode option. For details about host modes, see the Provisioning Guide or LUN Manager User Guide for the storage system.Byte [n] MSB-------Bit------LSBByte [0] 00 01 02 03 04 05 06 07Byte [1] 08 09 10 11 12 13 14 15::Byte [11] 88 89 90 91 92 93 94 95

Option Description



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


ExampleSetting the WWN of host adapter: 210000e0, 8b0256f8 to the port: CL4-E, the host group #0.

# raidcom add hba_wwn -port CL4-E-0 -hba_wwn 210000e0,8b0256f8

raidcom delete hba_wwnDeletes the specified host (WWN) from the host group.

If the specified WWN does not exist, this command is ignored.

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


Option Description



-hba_wwn <WWN strings>

Specifies the WWN value (hexadecimal value) of the host adapter. For example:• 210000e08b0256f8• 210000e0,8b0256f8 (The value can be split in increments of 4

bytes by "," (commas).)

Option Description




Specifies the WWN value (hexadecimal value) of the host adapter. For example:• 210000e08b0256f8• 210000e0,8b0256f8 (The value can be split in increments of 4

bytes by "," (commas).)


ExampleDeleting the WWN of host adapter: 210000e0,8b039800 set for the port: CL4-E, the host group #0.

# raidcom delete hba_wwn -port CL4-E-0 -hba_wwn 210000e0,8b039800

raidcom get hba_wwnDisplays the WWN of the HBA registered to the host group.

Syntaxraidcom get hba_wwn -port <port#> [<host group name>]


ExampleDisplaying the WWN of host adapter set for the port: CL4-E, the host group 0.

# raidcom get hba_wwn -port CL4-E-0PORT GID GROUP_NAME HWWN Serial# NICK_NAMECL4-E 0 Linux_x86 210000e08b0256f8 63528 ORA_NODE0_CTL_0CL4-E 0 Linux_x86 210000e08b039c15 63528 ORA_NODE1_CTL_0



GID: Displays the host group ID of a port.

GROUP_NAME: Displays the host group name of a port.

HWWN: Displays the WWN of registered host adapter.


NICK_NAME: Displays the Nick Name of the WWN of host adapter.

Option Description


Specifies s a port number, a host group ID, and a host group name. It cannot be specified when more than 64 characters is set for the host group name. Use the host group ID. If setting the host group ID or the host group name is omitted, the information about host group ID 0 is displayed. For example,• CLI-A• CL1-A-g (g is from 0 to 254)• CL1-A Linux_X86



raidcom reset hba_wwnDeletes the nickname from the specified WWN on the specified port.

If there is no specified port, the command is rejected with EX_ENOOBJ.

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


ExamplesDeleting the nickname that is given to the connection host "WWN:210000e0,8b0256f8" to which the port: CL4-E and host group #0 are set.

# raidcom reset hba_wwn -port CL4-E-0 -hba_wwn 210000e0,8b0256f8

raidcom set hba_wwnSets a nickname (maximum 64 characters) to the specified WWN on the specified port.


If a nickname exists for the specified WWN, it is changed as NEW.

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


Option Description


Specifies the port number. For example:• CL1-A-g (g: 0-254)• CL1-A Linux_X86


Specifies WWN value (Hexadecimal value). For example:• 210000e08b0256f8• 210000e0,8b0256f8 (The value can be split in increments of 4

bytes by "," (commas).

Option Description




ExamplesGiving the nickname of "ORA_NODE0_CTL_0" to the connection host "WWN: 210000e0,8b0256f8" to which the port: CL4-E and host group #0 are set.

# raidcom set hba_wwn -port CL4-E-0 -hba_wwn 210000e0,8b0256f8 -wwn_nickname ORA_NODE0_CTL_0

raidcom add journalRegisters (adds) a volume to a journal.

This makes a Journal for "Open System" or "M/F System" to the specified LDEVs.

If the journal already exists, the specified LDEV is added to the journal.

If the journal does not exist, you must create it first, and then add an LDEV.

If the -timer_type option is specified, this command makes a journal as "M/F System". If not, this command makes a journal as "Open System".

A device group can also be specified instead of an LDEV.

This command is executed asynchronously with the command input. Check the completion of this process on the raidcom get command_status command.

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



Specifies WWN values (hexadecimal value). For example:• 210000e08b0256f8• 210000e0,8b0256f8 (The value can be split in increments of 4

bytes by "," (commas).

-wwn_nickname <WWN Nickname>

Specifies the nickname (maximum 64 characters) to be assigned to the WWN of a specific port.You cannot specify the same nickname to another WWN in the same port.

Option Description

Option Description

-journal_id <journal ID#>

Specifies the journal number (0-255).



ExamplesExamples for Open:

Creating a journal #1 of LDEVs: 265, 266, 267, and 278.

# raidcom add journal -journal_id 1 -ldev_id 265 266 267 268

Creating a journal #1 with an LDEV belonging to the device group: grp1.

# raidcom add journal -journal_id 1 -grp_opt ldev -device_grp_name grp1

Example for mainframe:

Creating a journal #1 with LDEVs: 265, 266, 267, and 278. As a timer type, the system clock of the mainframe host is used. (When LDEV is added to the journal of M/F, it is required to specify the system clock of the mainframe host to the timer type.)

# raidcom add journal -journal_id 1 -ldev_id 265 266 267 268 -timer_type system


Specifies the LDEV number (0-65279).Up to 64 LDEVs can be specified at a time. For example:• -ldev_id 200• -ldev_id 100-110• -ldev_id 100 -cnt 10

[-cnt <count> ] Specifies the count (2-64).If this option is omitted, "1" is used as the count.





[-mp_blade_id <mp#> ]

Specifies the MP blade ID number (0-7).If this option is omitted, the device automatically allocates an MP blade ID number. For example:• -mp_blade_id 2

[-timer_type <timer type> ]

Specifies the timer type: system, local, or None. For example:• -timer_type system• -timer_type localFor details, see the Universal Replicator manual for the storage system.

Option Description


raidcom delete journalDeletes a journal from the specified journal.

A device group can also be specified instead of an LDEV. If the LDEV and device group are not specified, journal is deleted.


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


ExamplesDeleting the specified Journal.

# raidcom delete journal -journal_id 6

Deleting the specified LDEV from the Journal.

# raidcom delete journal -journal_id 6 -ldev_id 265

Deleting the LDEV belonging to the device group: grp1 from the Journal.

# raidcom delete journal -journal_id 6 -grp_opt ldev -device_grp_name grp1

raidcom get journalDisplays the information of registered journal.

Option Description

-journal <journal ID#>

Specifies the journal number (0-255).

[-ldev_id <ldev#> ] Specifies the LDEV number (0-65279). If the both LDEV and device group are not specified, journal is deleted. For example:• -ldev_id 200




Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all of the LDEVs belonging in the device group are operated. If the both LDEV and device group are not specified, journal is deleted.



SyntaxDisplaying journal information

raidcom get journal [-key <keyword>]

Displaying timer related information

raidcom get journalt


ExamplesDisplaying journal information.

# raidcom get journalJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Num LDEV#001 0 1 PJNN 4 21 43216fde 30 512345 62500 4 265002 1 2 PJNF 4 95 3459fd43 52000 512345 62500 3 270002 2 2 SJNS 4 95 3459fd43 52000 512345 62500 3 270003 0 3 PJSN 4 0 - - 512345 62500 1 275004 0 4 PJSF 4 45 1234f432 78 512345 62500 1 276005 0 5 PJSE 0 0 - - 512345 62500 1 277

Displaying Timer related information of the journal.

# raidcom get journaltJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW001 0 1 PJNN 4 21 43216fde 30 512345 63528 20 300 40002 1 2 PJNF 4 95 3459fd43 52000 512345 63528 20 300 40003 0 3 PJSN 4 0 - - 512345 63528 20 300 40

Displaying option information of the journal.

# raidcom get journal -key optJID MU CTG JNLS TYPE TTYPE MODE IF DOW(S) PBW(M) CR CS(bps) DM MP# Seq#001 0 1 PJNN OPEN - HDD E 30 5 M 256 Y 2 64034002 1 2 PJNF M/F system CACHE D 30 5 H 256 Y 2 64034


JID: Journal number.

MU: Mirror ID on Universal Replicator.

CTG: Consistency group number.

JNLS: Status in the journal:• SMPL: a journal volume that does not have a pair, or is being deleted.• P(S)JNN: "P(S)vol Journal Normal Normal".• P(S)JNS: "P(S)vol Journal Normal Suspend" created with -nocsus

option.

Option Description

[-key <keyword> ]

Specifies the display keyword. Specify opt as <keyword>.


• P(S)JSN: "P(S)vol Journal Suspend Normal".• PJNF: "P(S)vol Journal Normal Full".• P(S)JSF: "P(S)vol Journal Suspend Full".• P(S)JSE: "P(S)vol Journal Suspend Error" including link failure.• P(S)JES: "P(S)vol Journal Error Suspend" created with -nocsus option.

AP: Number of active link paths of Universal Replicator.

U(%): Usage rate of journal volumes assuming the entire relevant volume is 100%.

Q-Marker: The P-VOL journal volume shows the newest sequential number (Q-marker) at the time of receiving WRITE data. The S-VOL journal volume shows the newest sequential number (Q-marker) written to the cache.

Q-CNT: Number of Q-markers remaining in the P-VOL journal volume.

D-SZ(BLK): Capacity of the data block size of the journal volume in blocks (512 bytes).

Seq#: Serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Num: Number of LDEVs configuring the journal volume.

LDEV#: LDEV number.

DOW: Data Overflow Watch timer setting (in seconds) per the Journal.

PBW: Path Blockade Watch timer setting (in seconds) per the Journal. If the setting is more than 3600 seconds, it displays 6000 seconds.

APW: Active Path Watch timer setting (in seconds) to detect any link failures.

TYPE: Open or M/F (mainframe) system.

TTYPE: Timer type for mainframe: System or Local.

MODE: Status of the journal:• HDD: Store the journal data to the journal volume (cache mode

disabled).• CACHE: Store the journal data to the cache (cache mode enabled).

IF: Inflow control for journal:• E: Enable• D: Disable

DOW(S): Data Overflow Watch timer setting (in seconds) per the Journal.

PBW(M): Path Blockade Watch timer setting (in minutes) per the Journal. If the setting is more than 60 minutes, it displays 100 minutes.

CR: Copy rate: Low, Medium, or High.

CS(bps): Copy speed (copy pace) in bps: 10 bps, 100 bps, or 256 bps.



DM: Copy mode "Y" or "N" under failure of the delta resync:• Y: copying ALL data.• N: No copying.

MP#: MP blade ID.

raidcom modify journalChanges the option of Universal Replicator to be used at journal, and sets the specified control parameter to the journal.

If you specify the -mp_blade_id option, you cannot specify the other options (-data_overflow_watch, - path_blocked_watch, -cache_mode, or -timer_type).

The -timer_type option must be specified to the journal on mainframe systems. This means that this option cannot be used for changing from "Open System" to "M/F System".

SyntaxWhen changing the data overflow watching time of journal data area, path blocked watch or the timer type, specify more than one option.

# raidcom modify journal -journal_id <journal ID#> {[-data_overflow_watch <time>][-cache_mode (y | n}] [-timer_type <timer type>][-copy_size <size>]}

When changing the path blocked watch.

# raidcom modify journal -journal_id <journal ID#> -path_blocked_watch <time> [-mirror_id <mu#>]

When changing the MP blade ID.

# raidcom modify journal -journal_id <journal ID#> -mp_blade_id <mp#>


Option Description

-journal_id <journal ID#> Specifies the journal number (0-255).

-data_overflow_watch <time(sec)>

The data overflow watch timer (0-600) (second).Specifies the watch time for the journal data area being full.If 0 is specified, the setting of the data overflow watch timer is changed and the inflow control for journals is set to disabled.

-path_blocked_watch <time(min)>

The watch for the path blockage (1-60) (minute).Use Storage Navigator or Device Manager - Storage Navigator to set the value with more than 60 minutes.If 0 is specified, the time of the watch for the path blockage does not change, and the watch for the path blockage is invalid.


ExamplesChanging the data overflow watch time for journal "6" to 15 seconds.

# raidcom modify journal -journal_id 6 -data_overflow_watch 15

Changing the settings for journal 6: data overflow watch time to 15 seconds, and the timer type to the system clock of the mainframe host .

# raidcom modify journal -journal_id 6 -data_overflow_watch 15 -timer_type system

Changing the the MP blade ID for journal "6" to 2.

# raidcom modify journal -journal_id 6 -mp_blade_id 2

Changing the setting for journal "6" to store journal data in the secondary journal to the cache.

# raidcom modify journal -journal_id 6 -cache_mode y

Changing the path block monitoring time of mirror ID 1 for journal "6" to 59 minutes.

-cache_mode (y | n} Specifies whether to use the cache mode.• y: Cache mode enabled (E)• n: Cache mode disabled (D)

[-timer_type <timer type>] Specifies the timer type: system, local, or None. For example:• -timer_type system• -timer_type localFor details, see the Universal Replicator manual for the storage system.

-mp_blade_id <mp#> Specifies the MP blade ID (0-7).Changing MP blade ID should be executed during off-peak hours of I/O loading. Do not change the MP blade ID during initial copying of Universal Replicator (on-peak hours of I/O loading).To change the MP blade ID again for the same journal, wait for more than 30 minutes after changing the MP blade ID. For example:• -mp_blade_id 2

[-mirror_id <mu#>] Specifies the Mirror ID.If the setting is omitted, "0" is used.

[-copy_size <size>] Specify the track <size> from 1 to 15 as follows. If you specify the large value as this option, the copy time shortens, but the I/O performance might deteriorate. If you do not use this option, the copy is performed at medium-speed.• 1 or 2: low-speed• 3: medium-speed• More than 4: high-speed

Option Description



# raidcom modify journal -journal_id 6 -path_blocked_watch 59 -mirror_id 1

raidcom add ldevAdds an LDEV to the specified parity group or the external volume group. Or this adds V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, Thin Image, or Copy-on-Write Snapshot to the specified pool.


Syntaxraidcom add ldev {-parity_grp_id <gno-sgno> | -external_grp_id <gno-sgno> | -pool {<pool ID#> | <pool naming> | snap}} -ldev_id <ldev#> {-capacity <size> | -offset_capacity <size> | -cylinder <size>} [-emulation <emulation type>][-location <lba>] [-mp_blade_id <mp#>] [-clpr <clpr#>


Option Description


Specifies the parity group number (gno:1-32, sgno:1-16). For example:• 3-1Specifies one of the following options: -raid_grp, - external_grp_id, or -pool_id.


Specifies the external volume group number (gno:1-16384, sgno:1-4096). For example:• 52-11 ("E" is not required)Specifies one of the following options: -raid_grp, - external_grp_id, or -pool_id.

-pool {<pool ID#> | <pool naming> | snap}

Specifies a Pool ID or Pool name for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe when V-VOL is created to a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.When only a number is specified, it is recognized as a pool ID. Therefore, when you specify a pool that the pool name is only a number, specify the pool ID instead of the pool name.When creating V-VOL for a Thin Image or Copy-on-Write Snapshot pool, specify "snap".

-ldev_id <ldev#> | -tse_ldev_id <ldev#>

Specifies the LDEV number (0-65279).If you specify -tse_ldev_id option, the volume is the same as the volume used by FlashCopy SE. When using -tse_ldev_id option, you must create the virtual volumes in Dynamic Provisioning for Mainframe. Examples:• -ldev_id 200• -tse_ldev_id 400


-capacity <size> Specifies the capacity. The size can be specified in bytes or LBAs. When specifying bytes, the unit is t/T (terabyte), g/G (gigabyte), m/M (megabyte), or k/K (kilobyte). If this option is omitted, block (512 bytes) is used.When specifying byte, note the following:• There is no size correction.• If the capacity of LDEVs that are created by GUI and by CLI

are the same, a copy pair might not be created. To create a pair with an LDEV that was created by GUI, create the LDEV by specifying LBA.

Example of specification:1GB (gigabyte) is:-capacity 1G, -capacity 1g, -capacity 1024M, -capacity 1024m, -capacity 1048576K, -capacity 1048576k, -capacity 2097152In the case of volumes other than OPEN-V, more free space than the capacity that was actually specified is required. For details, see the Provisioning Guide or LUN Manager User Guide for the storage system.When you specify "all" instead of digits to create an OPEN-V LDEV and no LDEV has been created in the specified parity group* or the external volume group, the system allocates all empty space for the LDEV. If the empty space is larger than the maximum capacity of an LDEV, the system creates the LDEV with the maximum capacity and leaves the rest of the space as an empty space.*: "all" cannot be specified depending on the combination of the drive type and drive level because of the LDEV control area allocation, and so on. In this case specify byte or LBA.

-offset_capacity <size>

Specifies capacity. Corrects the size as well as GUI for the specified capacity. The capacity can be specified in bytes or blocks. When specifying byte, the unit is t/T (terabyte), g/G (gigabyte), m/M (megabyte), or k/K (kilobyte).

-cylinder <size> Specifies the size in cylinder unit. When specifying, the unit is t/T (teracylinder), g/G (gigacylinder), m/M (megacylinder), or k/K (kilocylinder). Cylinder is applied if you do not specify the unit.When an open-systems emulation type is specified, this option cannot be specified.

[-location <lba>] Specifies the Location (the starting point of the LDEV to be created in the parity group/external volume group). If this specification is omitted, create a LDEV and close up in the free space.

Option Description



ExamplesCreating an LDEV: 100 of size 10GB in a parity group: 33-16.

Location in the parity group: automatic allocation, LDEV Emulation type: OPEN-V

# raidcom add ldev -parity_grp_id 33-16 -ldev_id 100 -capacity 10G

Creating an LDEV with the following conditions: Parity group: 33-17, location of the parity group: automatic allocation, Emulation type: 3390-3, Size: 10M cylinder (Cylinder specification), LDEV: 120.

# raidcom add ldev -parity_grp_id 33-17 -ldev_id 120 -cylinder 10m -emulation 3390-3

[-emulation <emulation type> ]

Specifies the emulation type. For example:• OPEN-VIf this specification is omitted, OPEN-V is specified.If this specification is omitted when the virtual volume is created, the following emulation type is specified.• OPEN-V: Dynamic Provisioning or Dynamic Tiering• 3390-A: Dynamic Provisioning for Mainframe or Dynamic

Tiering for MainframeThe values that can be specified for <emulation type> are:• OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, OPEN-V• 3380-3, 3380-3A, 3380-3B, 3380-3C• 3390-1, 3390-2, 3390-3, 3390-A, 3390-3A, 3390-3B, 3390-

3C, 3390-3R, 3390-9, 3390-9A, 3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, 3390-LC, 3390-M, 3390-MA, 3390-MB, 3390-MC, 3390-V

• 6586-G, 6586-J, 6586-K, 6586-KA, 6586-KB, 6586-KC• 6588-1, 6588-3, 6588-9, 6588-3A, 6588-3B, 6588-3C,

6588-9A, 6588-9B, 6588-9C, 6588-L, 6588-LA, 6588-LB, 6588-LC

Some emulation types cannot be specified depending on the emulation type.Caution:You can specify 3390-3 or 3390-3R as the emulation type, but these are unable to be mixed. You can specify the 3380 series or the 3390 series as the emulation type for each parity group, but they are unable to be mixed for each 32 address boundary because of the OS restriction. You can specify the 6588 series or the 6586 series as the emulation type for each parity group, but they are unable to be mixed for each 32 address boundary because of the OS restriction.

[-mp_blade_id <mp#> ]

Specifies the MP blade ID (0-7). If this specification is omitted, it is allocated automatically.

[-clpr <clpr#> ] When you create virtual volumes by specifying the -pool_id <pool#> option, specify the CLPR number. If you omit this option, the CLPR number to which the pool is allocated is used.

Option Description


Creating an LDEV of position in the external volume: allocated automatically, emulation type: OPEN-V, External volume: 01-02, Capacity: 200MB, and LDEV number: 200.

# raidcom add ldev -external_grp_id 01-02 -ldev_id 200 -capacity 200m

Creating an LDEV of external volume group:01-03, position in the external volume: allocated automatically, emulation type: OPEN-V, External volume size: takeover, and LDEV number: 220.

# raidcom add ldev -external_grp_id 01-03 -ldev_id 220 -capacity all

Creating a V-VOL of Capacity: 300MB and number: 300, to a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, or Dynamic Tiering, or Dynamic Tiering for Mainframe.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m

Creating a V-VOL of Capacity: 300MB and LDEV number: 400, to a pool for Thin Image or Copy-on-Write Snapshot.

# raidcom add ldev -pool snap -ldev_id 400 -capacity 300m

raidcom delete ldevDeletes the specified LDEVs or the V-VOLs. A device group can also be specified instead of an LDEV.


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


Option Description

-ldev_id <ldev#> (0-65279)

Specifies the LDEV number (0-65279). For example:• -ldev_id 200


Specifies the device information extracted from the LDEV belonging to the device group. Specify "ldev" (fixed). The information of LDEV belonging to the device group is used.


Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all the LDEVs belonging in the device group are operated.



ExamplesDeleting an LDEV: 200.

raidcom delete ldev -ldev_id 200

Deleting an LDEV belonging to the device group: grp1.

raidcom delete ldev -grp_opt ldev -device_grp_name grp1

raidcom extend ldevExtends the capacity of V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, or Dynamic Tiering, or Dynamic Tiering for Mainframe volume.

If the specified LDEV is not a V-VOL of Dynamic Provisioning, Dynamic Provisioning for Mainframe, or Dynamic Tiering, or Dynamic Tiering for Mainframe, the command is rejected with EX_ENOOBJ.


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


Option Description

-ldev_id <ldev#> (0-65279)

Specifies the LDEV number (0-65279). Specify LDEVs for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe. For example:• -ldev_id 200





-capacity <size> Specifies the capacity to be extended. The unit is g/G, m/M, or k/K. If this option is omitted, block (512 bytes) is used.Example of specification:1GB (gigabyte) is:-capacity 1G, -capacity 1g, -capacity 1024M, -capacity 1024m, -capacity 1048576K, -capacity 1048576k, -capacity 2097152

-offset_capacity <size>

Specifies capacity. Corrects the size as well as GUI for the specified capacity. The capacity can be specified in bytes or blocks.


ExamplesExtending the capacity of a Dynamic Provisioning or Dynamic Provisioning for Mainframe V-VOL: 200 by 10 GB.

# raidcom extend ldev -ldev_id 200 -capacity 10G

Extending the capacity of a Dynamic Provisioning or Dynamic Provisioning for MainframeV-VOL: 201 by 200 MB.

# raidcom extend ldev -ldev_id 201 -capacity 200M

Extending the capacity of Dynamic Provisioning or Dynamic Provisioning for Mainframe V-VOL belonging to the device group: grp1 by 200 MB.

# raidcom extend ldev -grp_opt ldev -device_grp_name grp1 -capacity 200M

raidcom get ldevDisplays the information of the specified LDEV or the device file. A device group can also be specified instead of an LDEV.

Syntaxraidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt <group option> -device_grp_name <device group name> [<device name>] | -ldev_list <ldev list option>} [-key <keyword>][{-check_status | -check_status_not} <string> [-time <time>]]


-cylinder <size> Specifies the size in cylinder unit. When specifying, the unit is g/G (gigabyte), m/M (megabyte), or k/K (kilobyte). Cylinder is applied if you do not specify the unit.When the emulation type for the Open System is specified, this option cannot be specified.

Option Description

Option Description

-ldev_id <ldev#> … Specifies the LDEV number (0-65279). For example:• -ldev_id 200• -ldev_id 100-110• -ldev_id 100 -cnt 10

[-cnt <count> ] Specifies the count (2-65280).If this option is omitted, the count is set to one.







-ldev_list <ldev list option>

Specifies the type of LDEVs to display. Specify one of the following LDEV list options.• defined: Displays all implemented LDEVs.• dp_volume: Displays LDEVs that have Dynamic Provisioning

attributes.Combining this with -pool_id <pool id> specification displays LDEVs that have Dynamic Provisioning attributes related to the specified POOL.

• external_volume: Displays external volumes.• undefined: Displays all LDEV numbers that are not

implemented.• mapped: Displays all LDEVs to which LU paths are defined.

Combining this with -pool_id <pool id> specification displays LDEVs (defined the LU path) relate to the specified POOL.

• unmapped: Displays all LDEVs to which LU paths are defined. However, LDEVs that are not implemented or mainframe volumes are not displayed because they cannot specify the LU path.Combining this with -pool_id <pool id> specification displays LDEVs (not defined the LU path) relate to the specified POOL.

• journal -journal_id <journal id>: Displays LDEVs that belong to the specified journal.

• pool -pool_id <pool id>: Displays LDEVs that belong to the specified pool.If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.

• parity_grp -parity_grp_id <parity group id>: Displays LDEVs that belong to the specified parity group.

• mp_blade -mp_blade_id <mp#>: Displays LDEVs that are set to the specified MP blades.

• quorum: Displays LDEVs set for the quorum disks.If the LDEV that meets the specified condition does not exist, [EX_ENODEV] No such device is displayed.

[-key <keyword> ] Specifies a display keyword.If this option is omitted, basic LDEV information is displayed. If this option is specified, the following information is displayed. The following display keywords can be specified:front_end: Front-end informationparity_grp: Parity group informationexternal: External volume informationtier: Tier information for the Dynamic Tiering V-VOL.

Option Description


[-check_status <string> [-time <time>]]

Check if the LDEV is in the state as shown in <string>.The following strings are specified in the <string>.• STS

NML: Normal BLK: Blocked BSY: Status is changing

• OPE_TYPE FMT: Formatting QFMT: Quick formatting CCOPY: Data copying (Correction copy / Copy back /

Drive copy / Dynamic sparing) CACCS: Accessing to collections NONE: Not in operation SHRD: Shredding ZPD: Page discarding SHRPL: Deleting from the pool RLC: Pool relocating RBL: Pool rebalancing

• VOL_TYPE NOT DEFINED: An LDEV is not installed DEFINING: An LDEV is being created REMOVING: An LDEV is being deleted

If the relevant LDEV is in the specified status, the operation ends normally.If "-time" is specified, the status of the LDEV is checked every three seconds until the specified time (seconds) passes.

Option Description



Some keywords might not be displayed depending on the LDEV attribute as shown below.

[-check_status_not <string> [-time <time>]]

Check that the LDEV is not in the state as shown in <string>.The following strings are specified in the <string>.• STS

NML: Normal BLK: Blocked BSY: Status is changing

• OPE_TYPE FMT: Formatting QFMT: Quick formatting CCOPY: Data copying (Correction copy / Copy back /

Drive copy / Dynamic sparing) CACCS: Accessing to collections NONE: Not in operation SHRD: Shredding ZPD: Page discarding SHRPL: Deleting from the pool RLC: Pool relocating RBL: Pool rebalancing

• VOL_TYPE NOT DEFINED: An LDEV is not installed DEFINING: An LDEV is being created REMOVING: An LDEV is being deleted

If the relevant LDEV is not in the specified status, the operation ends normally.If "-time" is specified, the status of the LDEV is checked every three seconds until the specified time (seconds) passes.

Option Description

LDEV attribute Front end Parity group External Tier

Normal volume Internal volume Y Y N Y

External volume Y N Y Y

POOL volume for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe

Internal volume N Y N N

External volume N N Y N


Legend Y: Displayed, N: Not displayed

Examples

Internal volume examples

Displaying the information of the LDEV number 577 (internal VOL)

# raidcom get ldev -ldev_id 577Serial# : 63502 PHY_Serial# : 302594LDEV : 577 PHY_LDEV : 600SL : 0CL : 0VOL_TYPE : OPEN-V-CVSVOL_Capacity(BLK) : 2181120NUM_LDEV : 1LDEVs : 577NUM_PORT : 2PORTs : CL2-E-0 1 Linux_X86 : CL2-E-1 1 SolarisF_POOLID : NONEVOL_ATTR : CVSRAID_LEVEL : RAID1RAID_TYPE : 2D+2DNUM_GROUP : 1RAID_GROUPs : 02-01DRIVE_TYPE : DKS2C-K072FCDRIVE_Capa : 141822798LDEV_NAMING : Oracle_data_1STS : NMLOPE_TYPE : QFMTOPE_RATE : 100MP# : 2SSID:001FRSGID : 0



The virtual serial number is displayed when you specify a volume that is virtualized by the global virtualization function using the virtual LDEV number.

PHY_Serial#: If you specify a volume that is virtualized by the global virtualization function using the virtual LDEV number, the serial number of VSP G1000 is displayed. In other cases, this item is not displayed.

LDEV: LDEV number.

Journal volume Internal volume N Y N N

External volume N N Y N

LDEV attribute Front end Parity group External Tier



PHY_LDEV: LDEV number of VSP G1000. This item is displayed only when you specify the volume that was virtualized by the global virtualization function using the virtual LDEV number.

VIR_LDEV: Virtual LDEV number is displayed when you specify the volume that was virtualized by the global virtualization function using the LDEV number of VSP G1000 and it is different from the virtual LDEV number. When the virtual LDEV number is not given to the volume, "FF:FE(65534)" is displayed. When you set the reserve attribute of global-active device to the volume, "FF:FF(65535)" is displayed. This item is displayed only when the volume is virtualized by global virtualization, and this item is displayed on the place where PHY_LDEV is displayed in the example (Displaying the information of the LDEV number 577 (internal VOL)). However, VIR_LDEV and PHY_LDEV cannot be displayed at the same time.

SL: SLPR information ("0" is displayed for storage systems other than USP V/VM).

CL: CLPR information.

VOL_TYPE: Emulation type of the relevant LDEV. Displays the same name as the product ID of the Inquiry command. If the LDEV is not installed or is in the process of being created or deleted, the status is one of the following:• NOT DEFINED: An LDEV is not installed.• DEFINING: An LDEV is being created.• REMOVING: An LDEV is being deleted.

VOL_Capacity (BLK): capacity of LDEV in block size.

VOL_Capacity(cyl) : capacity of LDEV in cylinder size. Displayed only when the attribute is MF-VOL.

NUM_LDEV: number of LDEVs that configures the LU where the specified LDEV is belongs to.

LDEVs: number of LDEV in the LU.

NUM_PORT: number of ports defined to the paths for relevant LDEV. When the relevant LDEV is a mainframe volume or a multiplatform volume without the LU path definition, the number of ports for the dummy LU is displayed. For details about the dummy LU, see User and Reference Guide.

PORTs: ports defined to the paths for the relevant LDEV. It lists up the ports defined to the paths for the relevant LDEV. When the relevant LDEV is a mainframe volume or a multiplatform volume without the LU path definition, the port number of the dummy LU is displayed.

F_POOLID: pool ID if the LDEV is a component of the pool. In other cases, "NONE" is displayed.

VOL_ATTR: attributes of the LDEV.• CMD: Command device (open-systems only)• CLUN: Cache LUN (DCR)• CVS: CVS volume


• LUSE: LUSE volume• ALUN: Volume Migration volume• ELUN: External volume• OLG: OpenLDEV Guard volume• VVOL: V-VOL• HORC: The remote copy pair volumes:

TrueCopy, Universal Replicator, Universal Replicator for Mainframe: P-VOL or S-VOL

TrueCopy for Mainframe: M-VOL or R-VOL MRCF: ShadowImage volume (P-VOL or S-VOL) QS: Thin Image or Copy-on-Write Snapshot volume (P-VOL or S-

VOL) JNL: JNL volume HDP: Dynamic Provisioning(HDP) or Dynamic Provisioning for

Mainframe volume HDT: Dynamic Tiering (HDT) or Dynamic Tiering for Mainframe

volume POOL: POOL volume QRD: Quorum disk ENCD: Encryption disk SYSD: System disk TSE: Dynamic Provisioning for Mainframe volumes that are used in

FlashCopy SE.• RAID_LEVEL: RAID level (RAID1, RAID5, or RAID6).• RAID_TYPE: configuration of the drives.• NUM_GROUP: number of parity groups where the relevant LDEV is

belongs to.• RAID_GROUPs: parity groups where the relevant LDEVs are belong to.• DRIVE_TYPE: type of HDD drive where the relevant LDEV is configured.• DRIVE_Capa: capacity of relevant HDD in the number of block (512

bytes) (decimal number).• LDEV_NAMING: nickname of the LDEV.• STS: status of the LDEV:

NML: Normal BLK: Blocked BSY: Status is changing NONE: unknown state (not supported)

• OPE_TYPE: current operation. FMT: Formatting QFMT: Quick formatting



CCOPY: Data copying (Correction copy / Copy back / Drive copy / Dynamic sparing)

CACCS: Accessing to collections NONE: Not in operation SHRD: Shredding ZPD: Page Discarding SHRPL: Deleting from the pool RLC: Pool relocating RBL: Pool rebalancing

• OPE_RATE: progress of the format or shred operation. When the status is other than formatting or shredding, 100 is displayed. If the process ended abnormally, "BSY" is displayed on the "STS".

• MP#: MP blade ID.• SSID: storage subsystem ID number (hexadecimal). The Unified

Storage VM does not support SSID but displays the specified value.• RSGID: Displays the resource group ID of the resource group to which

the LDEV belongs.

Displaying front-end information of the LDEV number 577

# raidcom get ldev -ldev_id 577 -key front_end Serial# LDEV# SL CL VOL_TYPE VOL_Cap(BLK) PID ATTRIBUTE Ports PORT_No:LU#:GRPNAME …63502 577 0 0 OPEN-V-CVS 2181120 - CVS 2 CL2-E-0:1:Linux_X86 CL2-E-1:1:Solaris


PID: pool ID for a virtual volume. If the volume is not a virtual volume, hyphen (-) is displayed.

ATTRIBUTE: LDEV attribute. Same as VOL_ATTR.

Displaying back-end (parity group) information of the LDEV number 577

# raidcom get ldev -ldev_id 577 -key parity_grp Serial# LDEV# SL CL PID ATTRIBUTE R_LVL RAID_TYPE DRV_TYPE DRV_Cap GRPs RAID_GRP … 63502 577 0 0 - CVS RAID1 2D+2D DKS2C-K072FC 141822798 1 02-01

Check if the LDEV number 577 is in normal status

# raidcom get ldev -ldev_id 577 -check_status NML

Check if the LDEV number 577 is in blocked status

# raidcom get ldev -ldev_id 577 -check_status BLK


Set in wait status for 30 seconds until the formatting process of LDEV number 577 is complete

# raidcom get ldev -ldev_id 577 -check_status_not FMT -time 30raidcom:[EX_EWSTOT]Timeout waiting for specified statusRefer to the command log(/HORCM/log0/horcc_rmhost.log) for details.

(The command fails if the FMT does not change (is not complete) in the 30 seconds.)

External volume examples

Displaying the information of the LDEV number 160 (external VOL)

# raidcom get ldev -ldev_id 160Serial# : 63502LDEV : 160SL : 0CL : 0VOL_TYPE : OPEN-VVOL_Capacity(BLK) : 4385280NUM_PORT : 0PORTs :F_POOLID : NONEVOL_ATTR : ELUNE_VendorID : HITACHIE_ProductID : OPEN-VE_VOLID : 484954414348492052353030463830453030364100000000000000000000000000000000E_VOLID_C : HITACHI R500F80E006A................NUM_E_PORT : 1E_PORTs : CL2-G-0 0 50060e8004f80e34LDEV_NAMING : Oracle_data_1STS : NMLOPE_TYPE : QFMTOPE_RATE : 70MP# : 2SSID:001FRSGID : 0

Description of columns in output example

E_VendorID: VENDOR information in the SCSI information of the external volume.

E_ProductID: PRODUCT information in the SCSI information of the external volume.

E_VOLID: Device identification information in the SCSI information of the external volume (hexadecimal).

E_VOLID_C: PRODUCT information in the SCSI information of the external volume (ASCII display).

NUM_E_PROTs: Number of alternate paths.

E_PORTs: List of defined alternate paths.

QRDID: ID of the external volume that is a quorum disk for HAM.



If the LDEV number 160 is an external volume, its back-end (RAID group) information is displayed

Displaying the information of the LDEV number 600 (quorum disk)

# raidcom get ldev -ldev_id 600Serial# : 64543LDEV : 600SL : 0CL : 0VOL_TYPE : OPEN-VVOL_Capacity(BLK) : 16385280NUM_PORT : 0PORTs :F_POOLID : NONEVOL_ATTR : ELUN : QRDE_VendorID : HITACHIE_ProductID : OPEN-VE_VOLID : 484954414348492052353030464331463132303100000000000000000000000000000000E_VOLID_C : HITACHI R500FC1F1201................NUM_E_PORT : 1E_PORTs : CL2-H-0 1 50060e8006fc1f37LDEV_NAMING :STS : NMLOPE_TYPE : NONEOPE_RATE : 100MP# : 2SSID : 103FQRDID : 16QRP_Serial# : 65384QRP_ID : R7RSGID : 0

Description of a column in output example

QRDID: ID of the quorum disk for HAM or GAD.

QRP_Serial#: Shows the serial number of the storage system when the external volume is the quorum disk for HAM or GAD.

QRP_ID: Shows the ID for identifying storage systems when the external volume is the quorum disk for HAM or GAD.

Dynamic Provisioning V-VOL example

Displaying the information of the LDEV number 300 (V-VOL of Dynamic Provisioning)

# raidcom get ldev -ldev_id 300Serial# : 63502LDEV : 300SL : 0CL : 0VOL_TYPE : OPEN-V-CVS


VOL_Capacity(BLK) : 2181120NUM_PORT : 1PORTs : CL2-E-0 14 Linux_X86F_POOLID : NONEVOL_ATTR : CVS : HDPB_POOLID : 5LDEV_NAMING : Oracle_data_1STS : NMLOPE_TYPE : NONEOPE_RATE : 100MP# : 2SSID:001FRSGID : 0

Dynamic Tiering V-VOL examples

Displaying the information of the LDEV number 640 (V-VOL of Dynamic Tiering)

# raidcom get ldev -ldev_id 640Serial# : 63502LDEV : 640SL : 0CL : 0VOL_TYPE : OPEN-V-CVSVOL_Capacity(BLK) : 2181120NUM_LDEV : 1PORTs : CL2-E-0 14 Linux_X86F_POOLID : NONEVOL_ATTR : CVS : HDP : HDTB_POOLID : 5LDEV_NAMING : Oracle_data_1STS : NMLOPE_TYPE : NONEOPE_RATE : 100MP# : 2SSID:001FUsed_Block(BLK) : 218112TIER_Relocation : EnableTIER_level : 6TIER#1(MB) : 1120TIER#2(MB) : 3000TIER_Alloc_level : HTIER#1_Alloc_rate : MAX : 50 : MIN : 30TIER#3_Alloc_rate : MAX : 50 : MIN : 30RSGID : 0

Description of columns in output example:

B_POOL ID: Pool ID to which the LDEV is associated.

Used_Block(BLK): Number of blocks used in the pool.

TIER_Relocation: Status of the relocation setting:• Enable: The status where the relocation is enabled• Disable: The status where the relocation is disabled

TIER_LEVEL: Shows the level of tiering policy that is used for reallocation.• all: Shows that all tiers of the pool to which the relevant LDEV is

allocated are being used.



• 1-5: Shows the tiering policy level that is configured to the relevant LDEV.

• 6-31: Shows the tiering policy (customized policy (1-26)) that is configured to the relevant LDEV. For details, see the Provisioning Guide or LUN Manager User Guide for the storage system.

TIER#n(MB): Capacity (in MB) assigned to each tier.

TIER_Alloc_level: Shows the new page assignment tier level.• H: High• M: Middle• L: Low

TIER#1_Alloc_rate: Shows the Tier1 Max or Min value that is set in the tiering policy.

TIER#3_Alloc_rate: Shows the Tier3 Max or Min value that is set in the tiering policy.

Displays the tier information of the LDEV number 640 (V-VOL of Dynamic Tiering)

# raidcom get ldev -ldev_id 640 -key tierSerial# LDEV# SL CL VOL_TYPE VOL_Cap(BLK) PID ATTRIBUTE VOL_Used(BLK) TR TL T#1(MB) T#2(MB) ...63502 640 0 0 OPEN-V-CVS 204800 13 CVS|HDP|HDT 4720 E 0 3000 1120 600 0 0


TR: Displays the enabled or disabled of the tier relocation.• E: Enabled• D: Disabled

TL: Displays the tier level.• 0: ALL• 1-5: Level (1-5)• 6-31: Customized policy (1-26)

T#x(MB): Displays the allocated volume of the relevant LDEV for Tier x. Displays up to 5 tiers. If there is no tier, "0" is displayed.

rmawk command examples

For details about the rmawk command, see rmawk on page 4-16.

Displays the information of the used Tier 1 capacity for the pool ID 73 of the HDT volume (using the rmawk command)

# raidcom get ldev -ldev_list dp_volume -pool_id 73 -key tier |rmawk -EC @L-ne:0 @12?=ad:@12 -n exe="print Total = @12?"

Total = 8064


Displays the information of each used tier capacity for the pool ID 73 of the HDT volume (using the rmawk command)

# raidcom get ldev -ldev_list dp_volume -pool_id 73 -key tier |rmawk -EC @L-ne:0 @12=ad:@12? @13=ad:@13? @14=ad:@14? exe="print @0" -n exe="print " exe="print Total = T#1(MB): @12? T#2(MB): @13? T#3(MB): @14?"

Serial# LDEV# SL CL VOL_TYPE VOL_Cap(BLK) PID ATTRIBUTE VOL_ Used(BLK) TR TL T#1(MB) T#2(MB) T#3(MB) T#4(MB) T#5(MB)64558 29440 0 0 OPEN-V-CVS 4042752 73 CVS|HDP|HDT 404 2752 E 5 0 0 1974 0 064558 29441 0 0 OPEN-V-CVS 10924032 73 CVS|HDP|HDT 1092 4032 E 6 5334 0 0 0 064558 29442 0 0 OPEN-V-CVS 10924032 73 CVS|HDP|HDT 1092 4032 E 13 1596 1638 2100 0 064558 29443 0 0 OPEN-V-CVS 10924032 73 CVS|HDP|HDT 1092 4032 E 18 1134 3654 546 0 0

Total = T#1(MB):8064 T#2(MB):5292 T#3(MB):4620

raidcom initialize ldevFormats LDEVs. You can specify Quick Format, Normal Format, or Shredding.



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


Option Description








ExamplesPerforming Quick Format for an LDEV: 200.

# raidcom initialize ldev -operation qfmt -ldev_id 200

Performing Quick Format for an LDEV belonging to the device group: grp1.

# raidcom initialize ldev -operation qfmt -grp_opt ldev -device_grp_name grp1

Performing Normal Format for an LDEV: 200.

# raidcom initialize ldev -operation fmt -ldev_id 200

Performing Shredding (Pattern: 0x55aa55aa) for an LDEV: 200.

# raidcom initialize ldev -operation shrd 0x55aa55aa -ldev_id 200

Stopping Shredding.

# raidcom initialize ldev -operation stop -ldev_id 200

raidcom modify ldevChanges the following LDEV attributes:• Switching LDEV normal and LDEV blockade.• Setting LDEV nickname.• Setting MP blade ID of LDEV.

-operation <type> Instructs the operation.The following operations can be specified.• fmt: Normal Format• qfmt: Quick Format• shrd [<pattern>]: Shredding

Formats the LDEV three times according to the shredding pattern which is specified to "pattern".If <pattern> is specified, format the LDEV three times according to the following order. 0x00000000 The specified shredding pattern 0x00000000

If <pattern> is omitted, format the LDEV three times according to the following order. 0x00000000 0xFFFFFFFF 0x00000000

• stop: Stops shredding. The processing for all LDEVs stops. However, normal and quick format processing cannot be stopped.

Option Description


• Setting the tiering policy, the new page assignment tier, or enabling or disabling of the tier relocation for the Dynamic Tiering or Dynamic Tiering for Mainframe V-VOL.

• Instructing the page discarding of V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

• Setting the command device attribute.• Creating and deleting the quorum disk.

When executing LDEV blocking or recovery operation, this command is executed asynchronously with the command input. Check the completion of this process on the raidcom get command_status command.

Syntaxraidcom modify ldev -ldev_id <ldev#> {-status <status> [<level>] | -ldev_name <ldev naming> | -mp_blade_id <mp#> | -ssid <value> | -command_device {y | n} [Security value]} | -quorum_enable <serial#> <id> -quorum_id <quorum id> | -quorum_disable}


Option Description




-status <status> [<level>]

Specifies the LDEV status.The following LDEV statuses can be specified.nml: Changes the LDEV status to Normalblk: Changes the LDEV status to Blockade{enable_reallocation [<level>]|enable_relocation [<level>]}: Relocation of LDEV (V-VOL for Dynamic Tiering or Dynamic Tiering for Mainframe) enabled. Defines the tier that is used for reallocation depending on the value of the level.• all: Uses all tiers in the pool.• 1-5: Specifies the level of the tier for use. For details, see the

Provisioning Guide or LUN Manager User Guide for the storage system.

disable_reallocation| disable_relocation : Relocation of LDEV (V-VOL for Dynamic Tiering or Dynamic Tiering for Mainframe) disableddiscard_zero_page: Discarding 0 page of LDEV(V-VOL) for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.enable_relocation_policy <policy_id>: Enables the LDEV relocation for Dynamic Tiering and sets the level or customized tiering policy to be used for the relocation by Policy ID.<policy_id>: • all: Uses all tiers in the pool.• 1-5: Specifies the level of the tier for use.• 6-31: Specifies the customized policy of the tier for use.new_page_allocation: Sets the tier when new page is allocated to the LDEV for Dynamic Tiering (V-VOL). The value is one of high/middle/low.For example:• -status nml

-ldev_name <ldev naming>

Specifies the LDEV nickname (maximum 32 characters).

Option Description


-mp_blade_id <mp#>

Specifies the MP blade ID (0-7).Changing MP blade ID should be executed during off-peak hours of I/O loading. Do not change the MP blade ID during initial copying of TrueCopy, ShadowImage, or Universal Replicator (on-peak hours of I/O loading).To change the MP blade ID again for the same LDEV, wait for more than 30 minutes after changing the MP blade ID. For example:-mp_blade_id 2When you change the MP blade ID where the LDEV is allocated, both before and after the changing should be executed during as off-peak hours for the rate of write pending data of the MP blade as possible. It recommends to execute when the rate of write pending data of the all CLPR is less than 50%.Do not change the MP blade ID in regard to a lot of LDEVs at the same time. The number of LDEVs and I/O workload for which you can change the MP blade ID at the same time is lower than 10% of the total number of LDEVs where the same MP blade ID is allocated as a guideline.

-ssid <value> Specifies SSID (hexadecimal number).When specifying SSID, specify not only unallocated SSID but also LDEV ID. In this case, LDEV ID must be ID for the undefined LDEV in the area where SSID is not allocated. For example:To change the SSID again for the same LDEV, wait for more than 30 minutes after changing the SSID. For example:-ssid 0x1234 -ldev_id 200Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.

Option Description



ExamplesRestoring the LDEV: 200.

# raidcom modify ldev -status nml -ldev_id 200

Blocking the LDEV: 200.

# raidcom modify ldev -status blk -ldev_id 200

Assigning an LDEV nickname: my_volume to LDEV: 200

# raidcom modify ldev -ldev_id 200 -ldev_name my_volume

Setting the LDEV owner MP blade ID of LDEV: 200 to 2

# raidcom modify ldev -ldev_id 200 -mp_blade_id 2

-command_device {y | n} [Security value]

Configures command device attribute.y: Command device attribute enabled.n: Command device attribute disabled.Specifies the value of command device security (0-7).You can specify 0-7 to Security value as the command device security setting:• 0: Security: OFF, User authentication: OFF, Group information

acquisition: OFF• 1: Security: OFF, User authentication: OFF, Group information

acquisition: ON• 2: Security: OFF, User authentication: ON, Group information

acquisition: OFF• 3: Security: OFF, User authentication: ON, Group information

acquisition: ON• 4: Security: ON, User authentication: OFF, Group information

acquisition: OFF• 5: Security: ON, User authentication: OFF, Group information

acquisition: ON• 6: Security: ON, User authentication: ON, Group information

acquisition: OFF• 7: Security: ON, User authentication: ON, Group information

acquisition: ON

-quorum_enable <serial#> <id>

Sets quorum disk for global-active device configuration. You must also set the -quorum_id parameter.serial#: Serial number (of the migration source storage system)id: The identifier of the source storage system• R800: VSP G1000• R700: VSP• R600: USP V• RK600: USP VM

-quorum_id <quorum id>

Specifies the quorum ID for setting the quorum disk.

-quorum_disable Releases setting of the quorum disk.

Option Description


Enabling relocation of LDEV (Dynamic Tiering, Dynamic Tiering for Mainframe V-VOL) : 200

# raidcom modify ldev -ldev_id 200 -status enable_reallocation

Disabling relocation of LDEV (Dynamic Tiering, Dynamic Tiering for Mainframe V-VOL) : 200

# raidcom modify ldev -ldev_id 200 -status disable_reallocation

Discarding of the 0 page of LDEV (Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe V-VOL): 200

# raidcom modify ldev -ldev_id 200 -status discard_zero_page

Specifies 0x1234 to SSID of LDEV: 200.

Note: Specify undefined LDEV number: 200 in the area that is not allocated SSID, and assign new SSID: 0x1234. If you specify LDEV number that is already defined or SSID that is already registered, an error occurs.

# raidcom modify ldev -ssid 0x1234 -ldev_id 200

Enables LDEV command device attribute of LDEV: 200. Specifies 2 to the value of command device security.

# raidcom modify ldev -command_device y 2 -ldev_id 200

Disables LDEV command device attribute of LDEV: 200.

# raidcom modify ldev -command_device n -ldev_id 200

Set the relocation of LDEV for LDEV:200 by the customized policy 6.

# raidcom modify ldev -ldev_id 200 -status enable_relocation_policy 6

Set the new page assignment tier of LDEV: 200 to High.

# raidcom modify ldev -ldev_id 200 -status new_page_allocation high

Set LDEV: 200 as the quorum disk whose quorum ID is 10.

# raidcom modify ldev -ldev_id 200 –quorum_enable 65384 R700 – quorum_id 10

raidcom add lunTo set the LU path, this maps the specified LDEV to a LUN on a host group on the specified port and creates a LUN path or alternative path. A device group can also be specified instead of an LDEV.

If the specified port or host group does not exist, this command is rejected with EX_ENOOBJ(EX_CMDRJE).

If the specified LUN or LDEV already exists, this command is ignored.

If a LUN is not specified, an empty LUN is assigned automatically.

Not allowed:• Mapping the same LDEV to another LUN in the same host group.



• Overwriting the same LUN to another LDEV.

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


ExamplesMap the LDEV: 200 to the LU numbers: 1 for the port: CL1-A, the host group #0.

# raidcom add lun -port CL1-A-0 -lun_id 1 -ldev_id 200

Map the LDEV: 200 for the port: CL1-A, the host group #0. The LU numbers are automatically assigned.

# raidcom add lun -port CL1-A-0 -ldev_id 200

Map the LDEV for the port: CL1-A, the host group #0, and the one belonging to the device group: grp1. The LU numbers are automatically assigned.

# raidcom add lun -port CL1-A-0 -grp_opt ldev -device_grp_name grp1

Caution:• LDEVs in LUSE volumes cannot be configured with this command.• If you execute this command on an LDEV with the command device

attribute already set and the LDEV already has a defined/configured path, the command device attribute will be released.

Option Description


Specifies the port number. For example:• CL1-A-g (g: 0-254) • CL1-A Linux_X86






[-lun_id <lun#> ] Specifies the LU number (0-2047). This is unavailable to specify when the device group is specified to operate. If this option is omitted, a free LU number is assigned automatically.


raidcom delete lunDeletes the LU path on the host group on the specified port.

An LDEV or a device group can also be specified instead of a LUN.

If an LDEV does not exist on the specified port /host group/LUN, this command is rejected with EX_ENLDEV or EX_ENOOBJ.

When deleting the LU path, stop the I/O for the LU path to be deleted.

In the last one path, LDEV must be specified as SMPL volume.

Note: LDEVs in LUSE volumes cannot be configured with this command. Do not execute this command to the LDEV whose command device attribute is set. If the command is executed, the command device attritute is released.

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


ExamplesDeleting LUN: 1(LDEV number 200) on the port: CL1-A-0

# raidcom delete lun -port CL1-A-0 -lun 1# raidcom delete lun -port CL1-A-0 -ldev_id 200

Deleting LDEV belonging to the device group: grp1 on the port: CL1-A-0

# raidcom delete lun -port CL1-A-0 -grp_opt ldev -device_grp_name grp1

Option Description



-lun_id <lun#> Specifies the LUN number (0-2047).








raidcom discover lunSearches external volumes. Displays a list of LUs which can be referred to from the External port of a specific external storage system.

Syntaxraidcom discover lun -port <port#> -external_wwn <wwn strings>


ExamplesDisplaying LUs defined to the external storage system port: 50060e80, 06fc3850 connected to the port: CL5-A (External port).

# raidcom discover lun -port CL5-A -external_wwn 50060e8006fc3850PORT WWN LUN VOL_Cap(BLK) PRODUCT_ID E_VOL_ID_CCL5-A 50060e8006fc3850 0 102400 OPEN-V HITACHI R500FC381000CL5-A 50060e8006fc3850 1 102400 OPEN-V HITACHI R500FC381001CL5-A 50060e8006fc3850 2 102400 OPEN-V HITACHI R500FC381002CL5-A 50060e8006fc3850 3 102400 OPEN-V HITACHI R500FC381003CL5-A 50060e8006fc3850 4 102400 OPEN-V HITACHI R500FC381004CL5-A 50060e8006fc3850 5 102400 OPEN-V HITACHI R500FC381005CL5-A 50060e8006fc3850 6 102400 OPEN-V HITACHI R500FC381006CL5-A 50060e8006fc3850 7 102400 OPEN-V HITACHI R500FC381007CL5-A 50060e8006fc3850 8 102400 OPEN-V HITACHI R500FC381008CL5-A 50060e8006fc3850 9 102400 OPEN-V HITACHI R500FC381009CL5-A 50060e8006fc3850 10 102400 OPEN-V HITACHI R500FC38100A

PORT: External initiator port number.

WWN: WWN on the external storage system.

LUN: LUN of the port on external storage system.

VOL_Cap (BLK): Capacity of the external volume in blocks (512 bytes).

PRODUCT_ID: Product_ID included in the SCSI Inquiry command responding to the external volume.

E_VOL_ID_C: Volume identifier including in the SCSI inquiry command of the external volume.

Option Description

-port <port#> Specifies the port number. It specifies a port of which attribute is External. For example:• CL1-A


Specifies the WWN (hexadecimal value) of the external storage system in 8 bytes. The value can be split in increments of 4 bytes by "," (commas). For example:• 210000e08b0256f8• 210000e0,8b0256f8


raidcom get lunDisplays the LU path information defined in the specified port and host group.

If the specified port does not exist, this command is rejected with EX_ENOOBJ. If an external port is specified, it is rejected with EX_REQARG.

Syntaxraidcom get lun -port <port#> <host group name> [-key <keyword>]


ExamplesDisplaying the LU information defined to the port CL4-E, the host group #0.

# raidcom get lun -port CL4-E-0PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITsCL4-E 0 LINUX/IRIX 0 1 0 CM 63528 2 13CL4-E 0 LINUX/IRIX 2 1 2 - 63528 2 13CL4-E 0 LINUX/IRIX 3 1 3 - 63528 2 13CL4-E 0 LINUX/IRIX 4 1 4 - 63528 2 13CL4-E 0 LINUX/IRIX 5 1 992 - 63528 2 13CL4-E 0 LINUX/IRIX 6 1 993 - 63528 2 13

#raidcom get lun -port CL4-E-0 -key optPORT GID HMD LUN NUM LDEV CM Serial# OPKMA HMO_BITsCL4-E 0 LINUX/IRIX 0 1 0 CM 63528 -Y--- 2 13CL4-E 0 LINUX/IRIX 2 1 2 - 63528 -Y--- 2 13CL4-E 0 LINUX/IRIX 3 1 3 - 63528 -Y--- 2 13CL4-E 0 LINUX/IRIX 6 1 993 - 63528 -Y--- 2 13



GID: Displays the host group ID on the port.

HMD: Displays the following HOST MODE for the host adapter setting on host group.• HP-UX, SOLARIS, AIX, WIN, LINUX/IRIX, TRU64, OVMS, NETWARE, HI-

UX

Option Description


Specifies the port number, host group ID, and host group name. If the host group name is more than 64 characters, use the host group ID. If the host group ID and host group name are omitted, the LU path information for host group ID 0 is displayed.For example,• CLI-A• CL1-A-g (g: 0-254)• CL1-A Linux_X86

-key <keyword>]

Specifies opt as <keyword> to display the status of the host-reserved LUN.



• VMWARE, HP-UX, VMWARE_EX, WIN_EX, UVM

LUN: Displays LUN number on host group mapping LDEV.

NUM: Displays the number of LDEV configured an LUSE.

LDEV: Displays the LDEV number.

CM: Displays the command device.


OPKMA: Displays the host-reserved LU.• O: The LU is reserved by an open system.• P: The LU is reserved by a persistent group.• K: The LU is reserved by an RGR key.• M: The LU is reserved by a mainframe. • A: The LU is reserved by ACA.

If Y is displayed under each character, the LU is reserved. If a hyphen (-) is displayed, the LU is not reserved.

HMO_BITs: Displays the host mode options of the host groups. For details about host mode options, see the Provisioning Guide or LUN Manager User Guide for the storage system.

raidcom add pathAdds and changes an external path to an external volume. Only one path is operated in one operation.

The order of priority for the path is allocated in accordance with the order of adding paths.


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


Option Description



-port <port#> Specifies the port number. Specifies the number of the port whose attribute is External. For example:• CL1-A


ExamplesAdding a path of External port CL1-A, external storage system port 50060e80,05fa0f36 to an external volume path group number: 1.

# raidcom add path -path_grp 1 -port CL1-A -external_wwn 50060e80,05fa0f36

raidcom get pathDisplays the external path information to an external volume.

Syntaxraidcom get path [-path_grp <path group#>]


ExamplesDisplaying the external path (group) information to the external volume.

# raidcom get pathPHG GROUP STS CM IF MP# PORT WWN PR LUN PHS Serial# PRODUCT_ID1 1-1 NML E D 2 CL1-A 50060e8005fa0f36 1 3 NML 60010 VSP1 1-1 NML E D 2 CL2-A 50060e8005fa0f38 2 3 NML 60010 VSP

Displaying the information of the external volume path group number: 1.

# raidcom get path -path_grp 1PHG GROUP STS CM IF MP# PORT WWN PR LUN PHS Serial# PRODUCT_ID LB1 1-1 NML E D 2 CL1-A 50060e8005fa0f36 1 3 NML 60010 VSP N1 1-1 NML E D 2 CL2-A 50060e8005fa0f38 2 3 NML 60010 VSP N

PHG GROUP STS CM IF MP# PORT WWN PR LUN PHS Serial# PRODUCT_ID LB PM5 1-1 NML E D 0 CL3-B 50060e8006fc3222 1 0 NML 64562 VSP N M5 1-1 NML E D 0 CL5-A 50060e8006fc4150 - - UNK 64562 VSP N M5 1-2 NML E D 2 CL3-B 50060e8006fc3222 - - UNK 64562 VSP N A5 1-2 NML E D 2 CL5-A 50060e8006fc4150 1 0 NML 64562 VSP N A


PHG: Displays the path group number for the external volume.



Option Description

Option Description

[-path_grp <path group#> ]

Specifies the external VOL path group number (0-63231).If it is omitted, all groups are displayed.



GROUP: Displays the external volume group number.

STS: Displays the status of the external volume:• NML: "Normal"• CHK: "Checking"• SYN: "Cache Destage"• DSC: "Disconnect" in the external path for the external volume.• BLK: "Blockading" in the external path for the external volume.• UNK: "Unknown"• WAR: "Warning"

CM: Displays the cache mode for external volume:• E: Enable• D: Disable

IF: Displays the cache inflow control for external volume:• E: Write cache enabled• D: Write cache disabled• EM: NDM attribute and Write cache enabled.• DM: NDM attribute and Write cache disabled.• TM: NDM attribute and cache through mode.• SM: NDM attribute and Write sync mode.

MP#: Displays the MP blade ID for the external volume owner.


WWN: Displays the target wwn on the external storage system.

PR: Displays the priority number in the external volume path group.

LUN: Displays the LUN in the port on the external storage system side.

PHS: Displays the status of the external path:• - NML: "Normal" status in external path.• - CHK: "temporary blockading " status in external path.• - BLK: "blockading" status in external path.• - DSC: "disconnected" status in external path.• - UNK: "Unknown" status in external path.

Serial#: Displays the serial number of external storage system. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

PRODUCT_ID: Displays the PRODUCT_ID of the external storage system.

LB: Displays the I/O load balance mode for the external storage system. If Single is used for the path mode or the load balance mode is not supported, a hyphen (-) is displayed.


• - N: "normal round robin" mode.• - E: "extended round robin" mode.• - D: Executes with one path without load balance mode.

PM: Displays the path mode for the external storage system:• - M: Multiple path mode.• - S: Single path mode.• - A: APLB mode.• - AL: ALUA mode.• - MA: Multiple path mode (changeable to ALUA mode).• - SA: Single path mode (changeable to ALUA mode).

raidcom check_ext_storage pathRestores an external path to external VOLs. Only one path is operated in one operation.


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


ExamplesRestoring a path of external volume path group number: 1, External port CL1-A, and external storage system port 50060e80,05fa0f36.

# raidcom check_ext_storage path -path_grp 1 -port CL1-A -external_wwn 50060e80,05fa0f36

Option Description


Specifies the external VOL (0-63231) path group number.

-port <port#> Specifies the port number. Specifies the number of the port whose attribute is ELUN (External). For example:• CL1-A





raidcom delete pathDeletes the external path or alternative path to an external volume. Only one path is operated in one operation.


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


ExamplesDeleting a path of External port CL1-A, and external storage system port 50060e80,05fa0f36 from the external volume path group number: 1.

# raidcom delete path -path_grp 1 -port CL1-A -external_wwn 50060e80,05fa0f36

raidcom disconnect pathBlocks the usage of external paths to external VOLs. Only one path is operated in one operation.


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

Option Description








ExamplesBlocks the usage of a path of the external volume path group number: 1, the External port CL1-A, and the external storage port 50060e80,05fa0f36.

# raidcom disconnect path -path_grp 1 -port CL1-A -external_wwn 50060e80,05fa0f36

raidcom delete poolDeletes the specified Pool for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, and Dynamic Tiering, and Dynamic Tiering for Mainframe.

When LDEVs or device groups are specified, LDEVs are deleted from the specified pools.


Syntaxraidcom delete pool -pool {<pool ID#> | <pool naming>} [-ldev_id <ldev#> |-grp_opt <group option> -device_grp_name <device group name> [<device name>]]


Option Description






Option Description

-pool {<pool ID#> | <pool naming>}

Specifies the Pool ID (0-127) or pool name for Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.When you specify only a number, it is recognized as a pool ID. Therefore, to specify a pool whose name is a number, use the pool ID instead of the pool name.

-ldev_id <ldev#> Specifies the LDEV number (0-65279), for example:• -ldev_id 200



ExamplesDeleting a pool of pool ID 5:

# raidcom delete pool -pool_id 5

Deleting a pool of pool name "my_aou_pool":

# raidcom delete pool -pool my_aou_pool

Note: "Aou" (allocation on use) refers to dynamic provisioning.

raidcom get poolDisplays pool information for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, and Dynamic Tiering, and Dynamic Tiering for Mainframe.

Syntaxraidcom get pool [-key <keyword>]


ExamplesDisplaying pool information.

# raidcom get poolPID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%)001 POLN 10 330 10000000 1000000000 62500 2 365 80002 POLF 95 9900 100000 1000000000 62500 3 370 70003 POLS 100 10000 100 1000000000 62500 1 375 70004 POLE 0 0 0 0 62500 0 0 80

Displaying pool name.

# raidcom get pool -key optPID POLS U(%) POOL_NAME Seq# Num LDEV# H(%) VCAP(%) TYPE PM001 POLN 10 my_aou_pool 62500 2 265 80 65500 OPEN S002 POLF 95 New_Pool_2 62500 3 270 70 65534 OPEN S




Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of the LDEV (maximum 32 characters).If the device name is omitted, all the LDEVs belonging in the device group are operated.

Option Description

Option Description

[-key <keyword>]

Specifies when displaying a pool name. Specify "opt" as the <keyword>.


003 POLS 100 my_ss_pool 62500 1 275 70 - OPEN N004 POLN 0 New_Pool_4 62500 2 280 80 - 0 M/F N005 POLE 0 New_Pool_5 62500 4 0 80 100 M/F S


PID: Displays the pool ID.

POLS: Displays the following status in the pool:

- POLN: "Pool Normal" (The pool is in the normal status.)

- POLF: "Pool Full" (The pool is in the overflow status exceeding the threshold.)

- POLS: "Pool Suspend" (The pool is in the overflow status exceeding the threshold and is suspended.)

- POLE: "Pool failure" (The pool is suspended in the failure status.) In this status, the pool information cannot be displayed.

U(%): Displays the usage rate of the pool.

SSCNT: Displays the number of volumes in the pool.

POOL_NAME: Displays the pool name.

Available (MB): Displays the capacity available to the volume data in the pool.

Capacity (MB): Displays the total capacity of the pool.

Seq#: Displays the product serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Num: Displays the number of LDEVs configured the pool.

LDEV#: displays the first number of LDEV configured the pool.

H(%): Displays threshold for the pool.

VCAP (%): Displays the subscription threshold %. "-" indicates unlimited.

TYPE: Displays the types of pools.• Open: Shows that it is a Dynamic Provisioning pool.• M/F: Shows that it is a Dynamic Provisioning for Mainframe pool.

PM: Displays the pool status.• N: Normal status.• S: Shrinking or rebalancing.• NT: The pool for Thin Image is in the normal status.• ST: The pool for Thin Image is shrinking or rebalancing.



raidcom modify poolSets the options of a pool for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, and Dynamic Tiering, and Dynamic Tiering for Mainframe.

When the -status option is specified, the operation is executed asynchronously with the command input. Check the completion of this process on the raidcom get command_status command.

Syntaxraidcom modify pool -pool {<pool ID#> | <pool naming>} { -status <status> | -user_threshold <threshold_1> [<threshold_2>] | -tier <Tier number> [<ratio>][-tier_buffer_rate <%>] | -subscription <%> | -pool_attribute <pool_attribute> | -monitor_mode <Monitor mode>}


Option Description


Specifies the Pool ID (0-127) or pool name for Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.When only a number is specified, it is recognized as a pool ID. Therefore, to specify a pool whose name is a number, use the pool ID instead of the pool name.

-status <status> Specifies the status of the pool."nml" must be specified as the status.

-user_threshold <threshold_1> [<threshold_2>]

Sets a user-defined threshold.• For Dynamic Provisioning, Dynamic Provisioning for Mainframe,

and Dynamic Tiering, and Dynamic Tiering for Mainframe, you may specify two user-defined thresholds, and their valid ranges are 1-100%, respectively. If you specify <threshold_1> and <threshold_2>:The value of <threshold_1> is set as the threshold for WARNING specified to a pool.The value of <threshold_2> is set as the threshold for High water mark specified to a pool.If you specify only <threshold_1>, your specified value and the system default value (80%) are applied.The setting in which you specify only <threshold_1> is supported to maintain backward compatibility with microcode before 70-02-0x-xx/xx. Once you specify two user-defined thresholds, you must continue to specify two user-defined thresholds thereafter.

• The valid range for Thin Image or Copy-on-Write Snapshot is 20-95%. You may specify only <threshold_1>. Even if you specify the value for <threshold_2>, the value is ignored.


ExamplesRestoring the status of a pool ID: 6.

# raidcom modify pool -pool 6 -status nml

Restoring the status of a pool name: my_ss_pool.

# raidcom modify pool -pool my_ss_pool -status nml

Changing the user-defined thresholds of the pool ID:6 of the pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe, WARNING to 70% and High water mark to 80%.

# raidcom modify pool -pool 6 -user_threshold 70 80

Changing the user-defined threshold of the pool ID: 6 of the pool for Thin Image or Copy-on-Write Snapshot to 80%.

# raidcom modify pool -pool 6 -user_threshold 80

-tier <Tier number> [<ratio>]

Specifies the pool information for Dynamic Tiering and Dynamic Tiering for Mainframe. This is specified when changing the free space percentage for a new allocation by each tier. When this option is specified, pool attribute changes into manual relocation.<Tier number>:Tier number (1-3)<ratio>: Free space percentage for new allocation(0-50) [%]

[-tier_buffer_rate <%>]

Specifies the pool information for Dynamic Tiering and Dynamic Tiering for Mainframe. Specifies the amount of reallocation buffer (2-40) for each tier in percent (%).

-subscription <%>

Sets the maximum reserved V-VOL capacity rate (0-65535) to the pool capacity.0-65534: Specified percentage65535: Unlimited

-pool_attribute <pool_attribute>

Specifies when changing the pool from Dynamic Provisioning/Dynamic Provisioning for Mainframe to Dynamic Tiering/Dynamic Tiering for Mainframe, or from Dynamic Tiering/Dynamic Tiering for Mainframe to Dynamic Provisioning/Dynamic Provisioning for Mainframe.Specifies the following value depend on the type of pool desired to be changed.• dt_manual: Changes the pool from Dynamic Provisioning/

Dynamic Provisioning for Mainframe to Dynamic Tiering/Dynamic Tiering for Mainframe. It is changed to manual relocation.

• dp: Changes the pool from Dynamic Tiering/Dynamic Tiering for Mainframe to Dynamic Provisioning/Dynamic Provisioning for Mainframe.

-monitor_mode <monitor mode>

Specifies the monitoring mode for a Dynamic Tiering or Dynamic Tiering for Mainframe pool.• period: Performs monitoring periodically.• continuous: Performs monitoring continuously.

Option Description



Changing the free space percentage for a new allocation to the tier number 1 of the pool ID:6 for Dynamic Tiering or Dynamic Tiering for Mainframe to 30%.

# raidcom modify pool -pool 6 -tier 1 30

Changing the amount of reallocation buffer to the tier number 1 of the pool ID:6 for Dynamic Tiering or Dynamic Tiering for Mainframe to 20%.

# raidcom modify pool -pool 6 -tier 1 -tier_buffer_rate 20

Changing a Dynamic Provisioning/Dynamic Provisioning for Mainframe pool of the pool ID:6 to a Dynamic Tiering/Dynamic Tiering for Mainframe pool.

# raidcom modify pool -pool 6 -pool_attribute dt_manual

Changing a Dynamic Tiering/Dynamic Tiering for Mainframe pool of the pool ID:6 to a Dynamic Provisioning/Dynamic Provisioning for Mainframe pool.

# raidcom modify pool -pool 6 -pool_attribute dp

Changing the automatic relocation of the pool (Pool name: my_pool) for Dynamic Provisioning to manual relocation.

# raidcom modify pool -pool my_pool -pool_attribute dt_manual

Changing the monitoring mode of Dynamic Tiering/Dynamic Tiering for Mainframe pool of the pool ID: 6 to continuous.

# raidcom modify pool -pool 6 –monitor_mode continuous

raidcom monitor poolSets the start or stop of performance monitoring of a pool for Dynamic Tiering and Dynamic Tiering for Mainframe.

Syntaxraidcom monitor pool -pool {<pool ID#> | <pool naming>} -operation <type>


Option Description


Specifies the pool ID (0-127) or pool name of a pool for Dynamic Tiering or Dynamic Tiering for Mainframe.When specifying just a number, it is recognized as a pool ID. Therefore, when you specify a pool that the pool name is only a number, operate by specifying pool ID instead of specifying pool name.

-operation <type>

Instructs the operation of performance monitoring.The operational types that can be specified are shown below.start: Start the performance monitoring.stop: Stop the performance monitoring.


ExamplesStarting the performance monitoring of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool ID: 20.

# raidcom monitor pool -pool 20 -operation start

Starting the performance monitoring of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool Name: my_tier_pool.

# raidcom monitor pool -pool my_tier_pool -operation start

Stopping the performance monitoring of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool ID: 20.

# raidcom monitor pool -pool 20 -operation stop

Stopping the performance monitoring of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool Name: my_tier_pool.

# raidcom monitor pool -pool my_tier_pool -operation stop

raidcom reallocate poolSets the start or stop of tier relocation of a pool for Dynamic Tiering and Dynamic Tiering for Mainframe.

Syntaxraidcom reallocate pool -pool {<pool ID#> | <pool naming>} -operation <type>


ExamplesStarting the tier relocation of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool: 20.

# raidcom reallocate pool -pool 20 -operation start

Starting the tier relocation of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool Name: my_tier_pool.

# raidcom reallocate pool -pool my_tier_pool -operation start

Stopping the relocation of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool: 20.

Option Description


Specifies the pool ID (0-127) or pool name of a Dynamic Tiering or Dynamic Tiering for Mainframe pool.When only a number is specified, it is recognized as a pool ID. Therefore, when you specify a pool whose name is only a number, use the pool ID instead of the pool name.

-operation <type> Relocation operation instruction:start: Start the tier relocation.stop: Stop the tier relocation.



# raidcom reallocate pool -pool 20 -operation stop

Stopping the relocation of a pool for Dynamic Tiering/Dynamic Tiering for Mainframe with Pool Name: my_tier_pool.

# raidcom reallocate pool -pool my_tier_pool -operation stop

raidcom rename poolChanges the pool name of a pool for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

Syntaxraidcom rename pool -pool_id <pool ID#> -pool_name <pool naming>


ExamplesChanging the pool name of the pool (ID: 1) to my_pool.

# raidcom rename pool -pool_id 1 -pool_name my_pool

raidcom get portDisplays port information.

This queries the setting informations on all port.

Syntaxraidcom get port [-port <port#> [-key opt]]


Option Description

-pool_id <pool ID#>

Specifies a pool ID (0-127).If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.

-pool_name <pool naming>

Specifies a new pool name. You can specify up to 32 characters.The -pool_name option cannot be specified by configuring only in numeric because numeric values are preferentially identified as a pool ID. Specifies a pool ID with the '-pool_id<pool ID#>' option.

Option Description

[-port <port#>]

Specifies the port number. If the port number is specified for the port which is enabled LUN security, it displays LOGIN WWN. For example:CL1-A

[-key opt] Specifies this option to see the detailed information when the specified port is FCoE (fiber channel over ethernet).


ExamplesDisplaying port information.

In the case of mainframe port (FICON, ESCON), "-" is displayed to the rows from SPD to SSW.

# raidcom get portPORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial# WWN PHY_PORTCL1-A FIBRE TAR AUT EF N FCAL N 0 64568 50060e8006fc3800 -CL1-B FIBRE TAR AUT EF N FCAL N 0 64568 50060e8006fc3801 -CL1-C FICON TAR - - - - - 0 64568 50060e8006fc3802 -CL1-D FICON TAR - - - - - 0 64568 50060e8006fc3803 -CL2-A FIBRE TAR AUT D9 N FCAL N 0 64568 50060e8006fc3810 -CL2-B FIBRE TAR AUT D3 N FCAL Y 0 64568 50060e8006fc3811 -CL2-C FICON TAR - - - - - 0 64568 50060e8006fc3812 -CL2-D FICON TAR - - - - - 0 64568 50060e8006fc3813 -CL3-A FIBRE MCU AUT E8 N FCAL N 0 64568 50060e8006fc3820 -CL3-B FIBRE TAR AUT E0 N FCAL Y 0 64568 50060e8006fc3821 -


PORT: Displays the port numbers.

TYPE: Displays the following package type on a port: FIBRE, SCSI, ISCSI, ENAS, FICON, ESCON, FCoE

ATTR: Displays the following attribute setting on a port. One of the following items is displayed.• TAR: Fibre target port (target port)• MCU: MCU initiator port (initiator port)• RCU: RCU target port (RCU target port)• ELUN: External initiator port (External port)

SPD: Displays the transfer rate setting on a port. One of the following values is displayed: AUT(AUTO), 1G, 2G, 4G, 8G, 10G…

LPID: Displays the Loop ID(AL_PA) setting on a port.

FAB: Displays the fabric mode setting on a port as Y(YES) or N(NO).

CONN: Displays the following topology setting on a port: FCAL/PtoP

SSW: Displays the LUN security setting on a port as Y (enabled) or N (disabled).

SL: Displays the SLPR number to which the port belongs.


WWN: Displays the external WWN.

PHY_PORT: Displays the port number of the physical port in a resource ID takeover configuration.

Displaying the information of the port CL4-E.



# raidcom get port -port CL4-EPORT LOGIN_WWN Serial# -CL4-E 210000e08b0256f8 63528 OLA_NODE0_CTL_0CL4-E 210000e08b039c15 63528 OLA_NODE1_CTL_0


PORT: Displays the port numbers.

LOGIN_WWN: Displays WWN of the host adapter login to this port.

Note: Only the currently connected WWN is displayed unlike the display on Storage Navigator and Device Manager - Storage Navigator.


For example, for getting information on FCoE option:

# raidcom get port -port CL4-E -key optPORT ENMA VLAN_ID FPMA VPS VP_I FCF_ICL4-E e3:00:00:e0:8b:02 0x03fe e2:00:00:e0:8b:02 DWN 0x00 0x0000

Description of each column in output example.


ENMA: Displays Enode MAC address setting to this port.

VLAN_ID: Displays the VLAN identifier.

FPMA: Displays FP MAC address setting to this port.

VPS: Displays the virtual port status.• DWN: the Link status is in Link Down.• LOT: the Link status is in Link Up and Log-Out.• LIN: the Link status is in Link Up and Log-In.

VP_I: Displays the virtual port index (zero is currently displayed).

FCF_I: Displays the FCoE index (zero is currently displayed).

raidcom modify portThis sets the attribute value of the specified port.

When the value other than the port attribute value is specified, the specified port must be "TYPE=FIBRE or FCoE package and ATTR=TAR". If not, this command is rejected with EX_ENOOBJ.

When using a package of Fiber Channel over Ethernet, specify port speed: 10G, port topology: f_port. In this case, port attribute cannot be changed.


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


ExamplesChanging the port attributes (the Loop ID and the topology of the port) of a port CL3-E.

# raidcom modify port -port CL3-E -loop_id 0xAB -topology fl_port

Changing the port attributes of the port CL3-E to the External initiator port (ELUN).

# raidcom modify port -port CL3-E -port_attribute ELUN

Option Description

-port <port#> Specifies the port number. For example:• CL1-A

[-port_speed <value> ]

Specifies the HOST speed (0, 1, 2, 4, 8, 10) as follows.0: AUTO1: 1G2: 2G4: 4G8: 8G10: 10G

[-loop_id <alpa value> ]

Specifies the Loop ID (0x01-0xEF) of the port.

[-topology < topology> ]

Specifies the topology of the port as follows:fl-port : fabric on and fcalf-port : fabric on and PtoPnl-port : fabric off and fcaln-port : fabric off and PtoP

[-security _switch {y | n} ]

Specifies whether to use the security switch or not.

-port_attribute <port attribute>

Specifies the port attribute as follows:TAR: Fibre target port (target port)MCU: MCU initiator port (initiator port)RCU: RCU target port (RCU target port)ELUN: External initiator port (External port)If this port attribute is changed from Target or RCU Target to Initiator or External, the host group belonging to this port belongs to meta_resource.



raidcom get parity_grpDisplays parity group information.

Syntaxraidcom get parity_grp [-parity_grp_id <gno-sgno>]


ExamplesDisplaying parity group information.

# raidcom get parity_grpT GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPE R 33-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC R 33-17 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC


T: Displays the type of the volume group.• R: Parity

GROUP: Displays the parity group number.

Num_LDEV: Displays the number of LDEVs assigned to this parity group.

U(%): Displays the usage rate of this parity group.

AV_CAP(GB): Displays the available capacity (free space) for this parity group. The value is displayed by rounding less than 1GB down.

R_LVL: Displays the RAID level of the parity group.

R_TYPE: Displays the RAID type of the parity group.

SL: Displays the SLPR number to which the parity group or an external volume group belongs.

CL: Displays the CLPR number to which the parity group or an external volume group belongs.

DRIVE_TYPE: Displays the PRODUCT_ID of the drives in the parity group.

# raidcom get parity_grp -parity_grp_id 33-16T GROUP P_NO LDEV# STS LOC_LBA SIZE_LBA Serial# R 33-16 0 - NML 0x000000000000 0x000000003f00 64034R 33-16 1 100 NML 0x000000003f00 0x000000010000 64034

Option Description

[-parity_grp_id <gno-sgno> ]

Specifies the parity group number (gno: 1-32, sgno: 1-16).If this option is omitted, the list of parity groups defined in the storage system is displayed.If this option is specified, the LDEV and free space information defined in the specified parity group is displayed. For example:• 3-1


R 33-16 2 101 REG 0x000000013f00 0x000000010000 64034R 33-16 3 - DEL 0x000000023f00 0x0000f0000000 64034


T: Displays the type of the volume group.• R: Parity group

GROUP: Displays the parity group number.

P_NO: Displays the partition number partitioning this parity group.

LDEV#: Displays LDEV number.

STS: Displays the following status.• NML: LDEV is installed or free space is settled.• REG: LDEV is being created.• DEL: LDEV is being deleted.

LOC_LBA: Displays the Start of LBA for this partition on this parity group, in blocks (512 bytes).

SIZE_LBA: Displays the size for this partition on this parity group, in blocks (512 bytes).


raidcom add rcuRegisters RCUs.


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




ExampleRegister VSP of serial number: 64034 with CU free. Sets the path group ID: 0, the port on MCU: CL1-A, and the port on RCU: CL1-B.

# raidcom add rcu -cu_free 64034 R700 0 -mcu_port CL1-A -rcu_port CL1-B

Option Description

-rcu <serial#> <mcu#> <rcu#> <id>

Specifies the CU specified by serial number, <mcu#>, <rcu#>, and <id>. You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <mcu#> and <rcu#>.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.

-ssid <ssid> Specifies storage subsystem IDs. Up to 4 SSIDs can be specified.You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <ssid>.Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.

-cu_free <serial#> <id> <pid>

Specifies the CU free specified by serial#, id#, pid#.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (0-255).Note: The RCU registered by specifying "0" for <pid> is displayed by default or "0" on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe.

-mcu_port <port#>

Specifies the port number of the MCU.

-rcu_port <port#>

Specifies the port number on the RCU (storage system port on the remote side).Specify the port that the attribute is MCU Initiator port (MCU) or RCU Target port (RCU).


raidcom delete rcuDeletes the RCU.


Syntaxraidcom delete rcu {-rcu <serial#> <mcu#> <rcu#> -ssid <ssid> | -cu_free <serial#> <id> <pid>


ExamplesDeleting the VSP for which the product number: 64034, the RAID type: R700 and the path group ID: 1 are set.

# raidcom delete rcu -cu_free 64034 R700 1

Option Description

-rcu <serial#> <mcu#> <rcu#>

Specifies the CU specified by serial number, <mcu#>, <rcu#>. You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <mcu#> and <rcu#>.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-ssid <ssid> Specifies the storage subsystem ID.You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <ssid>.Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.

-cu_free <serial#><id><pid>

Specifies the CU free specified by serial#, id#, pid# for setting the RCU to be deleted.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (0-255).Note: Deleting the RCU registered by specifying "0" for <pid> causes removal of the display as shown by default on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe.



raidcom get rcuDisplays MCU/RCU information.

Syntaxraidcom get rcu [-rcu <serial#> <mcu#> <rcu#> -ssid <ssid> | -cu_free <serial#> <id> <pid>


ExamplesDisplaying RCU information.

# raidcom get rcuSerial# ID PID MCU RCU M/R T STS MP NP IM FZ RTO(s) RTT(ms) 64034 R7 - 1C 23 RCU F NML 4 8 MR D 15 20 64034 R7 - 1C 23 RCU F NML 4 8 RO E 15 20 64034 R7 1 - - MCU E NML 4 8 - - 15 20


Option Description


Specifies the CU specified by serial number, <mcu#>, <rcu#>. You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <mcu#> and <rcu#>.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-ssid <ssid> Specifies the storage subsystem ID.You can use hexadecimal numbers (add "0x" prefix) or decimal numbers for <ssid>.Note: This option is for enterprise storage systems. You need not specify the -ssid option when you use Unified Storage VM, but this option is enabled.

[-cu_free <serial#><id><pid>]

Specifies the CU free specified by serial#, id#, pid# for setting MCU or RCU which shows the information.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (0-255).Note: The RCU registered by specifying "0" for <pid> is displayed its information by default on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe.



ID: Displays the ID for identifying RAID type: R8 = VSP G1000, R7 = VSP, R6 = USP V/VM, R5 = TagmaStore USP/TagmaStore NSC, M7 = HUS VM

PID: Displays a path group ID. If CU is specified for RCU, "-" is displayed.

MCU: Displays the CU number (hexadecimal) as MCU. If CU free is specified for RCU, "-" is displayed.

RCU: Displays the CU number (hexadecimal) as RCU. If CU free is specified for RCU, "-" is displayed.

M/R: Displays the CU type as MCU/RCU.

T: Displays the type of physical path, F:FIBRE, E:ESCON

STS: Displays the following status of the CU.• NML: Normal• WAR: Warning• ERR: Failing• UNK: Unknown, displayed when the target of the pair is MCU.

MP: Displays the number of path as minimum.

NP: Displays the number of path setting between MCU and RCU.

IM: Displays the incident mode setting to RCU.• MR: it sends incident to MCU host and RCU host• RO: it sends incident only to RCU host• If CU free is specified for RCU, "-" is displayed.

FZ: Displays the freeze option.• D: the freeze option is disabled.• E: the freeze option is enabled.• -: "-" is displayed when CU free is specified for RCU.

RTO (s): Displays the timeout value for RIO (Remote IO) setting between MCU and RCU.

RTT (ms): Displays the round trip time value between MCU and RCU.

# raidcom get rcu -cu_free 64034 R700 1Serial# ID PID MCU RCU M/R T PNO MPORT RPORT STS_CD SSIDs …64034

R7 1 - - RCU F 1 CL1-A CL1-B NML_01 -64034 R7 1 - - RCU F 2 CL1-A CL1-B NML_01 -64034 R7 1 - - RCU F 3 CL1-A CL1-B NML_01 -





ID: Displays the ID for identifying RAID type: R8 = VSP G1000, R7 = VSP, R6 = USP V/VM, R5 = TagmaStore USP/TagmaStore NSC, M7 = HUS VM

PID: Displays the path group ID. If CU is specified for RCU, "-" is displayed.

MCU: Displays the CU number (hexadecimal) as MCU. If CU free is specified for RCU, "-" is displayed.

RCU: Displays the CU number (hexadecimal) as RCU. If CU free is specified for RCU, "-" is displayed.

M/R: Displays the CU type as MCU/RCU.

T: Displays the type of physical path: F: FIBRE, E:ESCON.

PNO: Displays the path number.

MPORT: Displays the MCU port number.

RPORT: Displays the RCU port number.

STS_CD: Displays the following path status:• NML_01: Normal• ERR_02: Initialization failed• ERR_03: Communication timeout• ERR_04: Logical blockade• ERR_05: Resource Shortage• ERR_06: Serial Number Mismatch• ERR_10: Invalid Port• ERR_80: RCU Port Number Mismatch• ERR_81: RCU Port Type Mismatch• ERR_82: Communication Failed.• If path creation or path deletion is in progress, "-" is displayed.

SSIDs: Displays the SSIDs (hexadecimal) setting to RCU. If CU free is specified for RCU, "-" is displayed.

raidcom modify rcuThis sets the control parameters to specified CU that is specified using two way.

Syntaxraidcom modify rcu {-rcu <serial#> <mcu#> <rcu#> -ssid <ssid> | -cu_free <serial#> <id> <pid>} -rcu_option <mpth> <rto> <rtt> [fzd | fze]



ExamplesFor the RCU for which the product number: 64034, the RAID type: R700 and the path ID: 1 are set, setting the options: the minimum number of paths <mpth>4, RIO MIH time<rto>15 seconds, and round trip time 20 milisecond are set.

# raidcom modify rcu -cu_free 64034 R700 1 -rcu_option 4 15 20

Option Description


Specifies the CU specified by serial number, <mcu#>, and <rcu#>. You can use hexadecimal numbers (add 0x prefix ) or decimal numbers for the <mcu#> and <rcu#>.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-ssid <ssid> Specifies the storage subsystem ID.You can use hexadecimal numbers (add 0x prefix) or decimal numbers for the <ssid>.Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.


Specifies CU free specified by serial#, id#, pid# for setting CU for the operational object.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (1-255).Note: The RCU is displayed by default on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe when "0" is specified for <pid>.

-rcu_option <mpth> <rto> <rtt> [fzd | fze]

Specifies CU control parameters:• <mpth>: minimum number of paths (1-8)• <rto>: RIO timeout value (10-100) (second) for RIO

(Remote IO) setting between MCU and RCU.• <rtt> is used to set the round trip time value (1-500)

(millisecond) between MCU and RCU.• [fzd | fze]: Specify fze to enable the freeze option, or fzd

to disable it.If the freeze option is not specified to the RCU with CU units, the freeze option is disabled.



raidcom add rcu_pathAdds logical paths to RCUs.


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


Option Description





This parameter is used to specify CU free specified by serial#, id#, pid#.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For Hitachi Virtual Storage Platform G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (1-255).Note: The RCU is displayed by default on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe when "0" is specified for <pid>.

-mcu_port <port#> Specifies the port number on the MCU.

-rcu_port <port#> Specifies the port number on the RCU (storage system port on the remote side).Specify the port that the attribute is MCU initiator port (MCU) or RCU target port (RCU).


ExamplesTo the RCU for which the product number: 64034, the RAID type: R700 and the path ID: 1 are set, adding RCU path: mcu port: CL1-A, rcu port CL1-B.

# raidcom add rcu_path -cu_free 64034 R700 1 -mcu_port CL1-A -rcu_port CL1-B

raidcom delete rcu_pathDeletes logical paths from a specified RCU.


Syntaxraidcom delete rcu_path {-rcu <serial#> <mcu#> <rcu#> -ssid <ssid> | -cu_free <serial#> <id> <pid>} -mcu_port <port#> -rcu_port <port#>


Option Description





This parameter is used to specify CU free specified by serial#, id#, pid#.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.< id > specifies the storage system type as follows:• For VSP G1000 use R800.• For VSP use R700.• For HUS VM use M700.• For USP V/VM use R600.• For TagmaStore USP/TagmaStore NSC use R500.< pid> specifies the path group ID (1-255).Note: The RCU is displayed by default on the GUI of TrueCopy, Universal Replicator, or Universal Replicator for Mainframe when "0" is specified for <pid>.



ExamplesFrom the RCU for which the product number: 64034, the RAID type: R700 and the path ID: 1 are set, deleting RCU path: mcu port: CL1-A and rcu port CL1-B.

# raidcom delete rcu_path -cu_free 64034 R700 1 -mcu_port CL1-A -rcu_port CL1-B

raidcom add ssidAdds the specified SSID to the RCU that is specified by serial number, <mcu#>, and <rcu#>.

Syntaxraidcom add ssid -rcu <serial#> <mcu#> <rcu#> <id> -ssid <ssid>


ExamplesAdding SSID:345 to the RCU with serial number: 64034, RAID type: R700, MCU#:0, and RCU#:1 are set.

-mcu_port <port#> Specifies the port number on the MCU.

-rcu_port <port#> Specifies the port number on the RCU (storage system port on the remote side).Specifies the port that the attribute is MCU initiator port (MCU) or RCU target port (RCU).

Option Description

Option Description

-rcu <serial#> <mcu#> <rcu#> <id>

Specifies the CU specified by serial number, <mcu#>, <rcu#>, and <id>. You can use hexadecimal (add the prefix 0x) or decimal for the <mcu#> and <rcu#> numbers .Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.Use the following strings for <id> to specify the RAID storage system type:• For VSP G1000 use R800.• For VSP, use "R700".• For USP V/VM, use "R600".• For TagmaStore USP/TagmaStore NSC, use "R500".

-ssid <ssid> Specifies the storage subsystem ID (SSID) to add to the RCU.You can use hexadecimal (add the 0x prefix) or decimal for the <ssid> number.Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.


raidcom add ssid -rcu 64034 0 1 R700 -ssid 345

raidcom delete ssidDeletes the specified SSID from the RCU that is specified by a serial number, <mcu#>, and <rcu#>.

Syntaxraidcom delete ssid -rcu <serial#> <mcu#> <rcu#> -ssid <ssid>


ExamplesDeleting SSID:345 from the RCU where the serial number: 64034, MCU#:0, and RCU#:1 are set.

raidcom delete ssid -rcu 64034 0 1 -ssid 345

raidcom add resourceCreating resource groups. If you specify only the resource group name, an empty resource group is created. If you specify the resource group name and the information on the virtual storage machine, an empty resource group that corresponds to the virtual storage machine is created.

When you input a resource group name and a resource group ID, the current name of the resource group whose ID you specify is changed to the new resource group name.

When you specify resource group name, LDEV number, port number, host group number, parity group ID or an external group ID, the specified resource is registered to the specified resource group.If the specified resource group does not exist, an error occurs. When the resource group is already created, the specified resource is added to the resource group. You can specify a device group name instead of an LDEV number.

Option Description


This parameter is used to specify a CU that is specified by a serial number, <mcu#>, and <rcu#>. This option specifies <mcu#> and <rcu#> with hexadecimal numbers (adding 0x) or decimal numbers.Note for VSP G1000: When specifying <serial#> for VSP G1000, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.

-ssid <ssid> Specifies the storage subsystem ID to be deleted from the RCU.You can specify the ssid as a hexadecimal number (add the 0x prefix) or a decimal number.Note: This option is for enterprise storage systems. You need not specify the -ssid option for the Unified Storage VM, but this option is enabled.



When the relevant LDEVs configure the pool, journal, and LUSE, all LDEVs must be added to the same resource group.

Syntaxraidcom add resource -resource_name <resource group name> [-virtual_type <serial#> <id>] | -resource_id <resource group_id | -ldev_id <ldev#> | -port <port#> [<host group name>] | -parity_grp_id <gno-sgno> | -external_grp_id <gno-sgno> | -grp_opt <group option> | -device_grp_name <device group name> [<device name>]]


Option Description

-resource_name <resource group name>

Specifies the resource group name. Up to 32 characters can be specified.

[-virtual_type <serial#> <id>]

Specifies the information about the virtual storage machine.• serial#: Serial ID of the source DKC.• id: The type identifier of the source DKC

R800: VSP G1000 R700: VSP R600: USP V RK600: USP VM R500: TagmaStore USP RK500: TagmaStore NSC

-resource_id <resource group_id

Specifies the resource group ID (1-1023) (for example, 5).

-ldev_id <ldev#>

Specifies the LDEV number (0-65279) (for example, -ldev_id 200).


Specifies the port number, host group ID, and host group name. If the host group name is more than 64 characters, use the host group ID instead of the host group name (for example, CL1-A or CL1-A-g, where g is from 0 to 255).


Specifies the parity group number (gno:1-32, sgno:1-16) (for example, 3-1).


Specifies the external volume group number (gno:1-16384, sgno:1-4096) (for example, 52-11, "E" is not required).


Specifies the device information extracted from the LDEV in the device group. Specify "ldev" (fixed). The information about the LDEV in the device group is used.


Specifies the name of the device group (maximum 32 characters).To specify an LDEV in the device group, use the device name of the LDEV (maximum 32 characters).If the device name is omitted, this command is applied to all LDEVs in the specified device group.


ExamplesCreating a resource group of resource group name: sql_srv.

# raidcom add resource -resource_name sql_srv

Creating a virtual storage machine: rsg_vir, and the serial number of the virtual storage machine: 1000.

# raidcom add resource -resource_name rsg_vir -virtual_type 1000 R700

Changing the resource group name of the resource group ID:5 to sql_srv.

# raidcom add resource -resource_name sql_srv -resource_id 5

Add LDEV: 400 to the resource group: sql_srv.

# raidcom add resource -resource_name sql_srv -ldev_id 400

Adding a port of CL1-A to a resource group: sql_srv.

# raidcom add resource -resource_name sql_srv -port CL1-A

Adding a host group of CL1-A-0 to a resource group: sql_srv.

# raidcom add resource -resource_name sql_srv -port CL1-A-0

Adding a parity group:33-16 to a resource group: sql_srv.

# raidcom add resource -resource_name sql_srv -parity_grp_id 33-16

Adding an external volume group:01-02 to a resource group: sql_srv.

# raidcom add resource -resource_name sql_srv -external_grp_id 01-02

raidcom modify resourceSets the virtual storage mode of a resource group. This is an asynchronous command.

Syntaxraidcom modify resource -resource_name <resource group name> -virtual_switch <y/n>


ExampleResource group: Enable the virtual storage mode of sql_srv.

Option Description



-virtual_switch <y/n>

Sets the virtual storage mode of the resource group to ON/OFF.• y: Enable the virtual storage mode• n: Disable the virtual storage mode



# raidcom modify resource -resource_name sql_srv -virtual_switch y

raidcom delete resourceDeletes resource groups. You can delete a resource group only after all resources that are registered to that resource group have been deleted.

LDEV number, port number, host group number, parity group, and external group are deleted from the specified resource groups. The deleted resources are moved to resource group 0. You can specify a device group name instead of a LDEV number.

If an LDEV is a volume that configures a pool, journal, or LUSE, all LDEVs of the pool, journal, or LUSE must be assigned to the same resource group.

Syntaxraidcom delete resource -resource_name <resource group name> [-ldev_id <ldev#> | -port <port#> [<host group name>] | -parity_grp <gno-sgno> | -external_grp_id <gno-sgno> | -grp_opt <group option> -device_grp_name <device group name> [<device name>]]


Option Description





Specifies the port number, host group ID, and host group name. If the host group name is more than 64 characters, use the host group ID instead of the host group name. For example:• CL1-A or CL1-A-g (g is from 0 to 255)


Specifies the parity group number (gno:1-32, sgno:1-16). For example:• 3-1


Specifies the external volume group number (gno:1-16384, sgno:1-4096). For example:• 52-11 ("E" is not required)


Specifies the device information about the LDEV in the device group. Specify "ldev" (fixed). The information about the LDEV in the device group is used.


Specifies the name of device group (maximum 32 characters) to be deleted.To specify the specific LDEV in the device group, specify the device name of the LDEV (maximum 32 characters) in the device group.If the device name is omitted, the command is applied to all LDEVs in the device group.


ExamplesDeleting the LDEV: 400 from the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv -ldev_id 400

Deleting a port of CL1-A from the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv -port CL1-A

Deleting a host group of CL1-A-0 from the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv -port CL1-A-0

Deleting a parity group: 33-16 from the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv -parity_grp_id 33-16

Deleting an external volume group: 01-02 from the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv -external_grp_id 01-02

Deleting the resource group: sql_srv.

# raidcom delete resource -resource_name sql_srv

raidcom get resourceDisplays resource group information.

Syntaxraidcom get resource -key <option>


ExamplesDisplaying a resource group and resource group lock information.

# raidcom get resourceRS_GROUP RGID stat Lock_owner Lock_host Serial#meta_resource 0 Unlocked - - 64556

Displaying a resource group status on the virtual mode.

#raidcom get resource -key optRS_GROUP RGID V_Serial# V_ID V_IF Serial#meta_resource 0 302624 R8 Y 302624USP_002 1 64035 R5 Y 302624

Description of each column in output example.

RS_GROUP: Resource group name.

Option Description

-key <option> Specify "opt" as the option to display resource group information on the virtual mode.



RGID: resource group ID. RGID=0 is used for meta resource group.

stat: locking status of the resource group name on HUS VM and VSP.

Lock_owner: owner (authorized user) who locks the resource group name.

Lock_host: host name of a user who locks the resource group name.


V_Serial#: Product serial number on the virtual mode.

V_ID: Storage system type:• Virtual Storage Platform G1000: R8• Unified Storage VM: M7• Virtual Storage Platform: R7• Universal Storage Platform V: R6• Universal Storage Platform VM: RK6• TagmaStore USP: R5• TagmaStore NSC: RK5

V_IF: Status of the virtual mode:• Y: The virtual mode is enabled.• N: The virtual mode is disabled.

raidcom lock resourceThis locks the specified resource group name.

When you perform these commands, lock the resource group to which resource is allocated before executing the command.• add• delete• modify• initialize• check_ext_storage• disconnect• set• reset• reallocate• monitor

If the specified resource group name does not exist, this command is rejected with EX_ENOOBJ.

In authentication mode, the user executing this command must have a permission for the resource group name.


Syntaxraidcom lock resource [-resource_name <resource group name>] [-time <time(sec)>]


ExamplesResource group: Locking the resource of the meta_resource.

# raidcom lock resource -resource_name meta_resource

raidcom unlock resourceThis unlocks the specified resource group name.

If the specified resource group name does not exist, this command is rejected with EX_ENOOBJ.

In authentication mode, A user executing this command must have a permission for the resource group name.

Syntaxraidcom unlock resource [-resource_name <resource group name>]


ExamplesResource group: Unlocking the resource of the meta_resource.

Option Description

[-resource_name <resource group name>]

Specifies the name of resource group (maximum 32 characters).Specify defined resource group names.If this parameter is not specified, all resource groups that are assigned to the user are locked.

[-time <time(sec)> ] This parameter is used for specifying the latency until the specified resource is locked.The TOV time of the lock instruction is specified.When <time> is specified as "0", it is executed as "nowait (no waiting time)" mode.If this parameter is not specified, the default waiting time (7200 seconds) is used.

Option Description

[-resource_name <resource group name>]

Specifies the name of resource group (maximum 32 characters).Specify defined resource group names.If this parameter is not specified, all resource groups that are assigned to the user are unlocked.



# raidcom unlock resource -resource_name meta_resource

raidcom map resourceArrange a resource to the virtual storage machine. This is a synchronous command.

Syntaxraidcom map resource {-ldev_id <ldev#> -virtual_ldev_id <ldev#> [-ssid<ssid> -emulation <emulation type>] | -port <port#> -virtual_port <port#>}


ExamplesCreate a virtual LDEV100 in an LDEV400.

Option Description

-ldev_id <ldev#> Specify an LDEV ID (0-65279).Example:• -ldev_id 200

-virtual_ldev_id <ldev#>

Specify an LDEV ID (0-65279) to be used in the virtual storage machine.If you specify "reserve" instead of the LDEV ID, the reserve attribute of global-active device is set.Example:• -virtual_ldev_id 300

-ssid <ssid> Specify an SSID related to an LDEV in the virtual storage machine.

[-emulation <emulation type>]

Specify the emulation type of a relevant LDEV on the virtual storage machine. This setting is reflected in the inquiry response.Specify the emulation type by adding "*n" in the LUSE configuration or by adding "-CVS" in the CVS configuration. ("n" shows the number of LUSE components.)Apply in order from "*n" (LUSE configuration) to "-CVS" (CVS configuration) when it is LUSE configuration and CVS configuration.Example:• -emulation OPEN-3-CVS• -emulation OPEN-3*6• -emulation OPEN-3*6-CVS

-port <port#> Specify a port number. Specify the port number whose attribute is Target.Example:• CL1-A

-virtual_port <port#>

Specify a port number to be used in the virtual storage machine.Example:• CL3-B


# raidcom map resource -ldev_id 400 -virtual_ldev_id 100

Create a virtual port CL2-B in a port CL1-A.

# raidcom map resource -port CL1-A -virtual_port CL2-B

raidcom unmap resourceCancel the resource arrangement in the virtual storage machine. This is a synchronous command.

Syntaxraidcom unmap resource {-ldev_id <ldev#> -virtual_ldev_id <ldev#> | -port <port#> -virtual_port <port#>}


ExamplesCancel a virtual LDEV100 in an LDEV400.

# raidcom unmap resource -ldev_id 400 -virtual_ldev_id 100

Cancel a virtual port CL2-B in a port CL1-A.

# raidcom unmap resource -port CL1-A -virtual_port CL2-B

raidcom add snap_poolCreates pools and adds pool VOLs for Thin Image and Copy-on-Write Snapshot by the specified LDEVs. A device group can also be specified instead of an LDEV.

Option Description

-ldev_id <ldev#> Specify an LDEV ID (0-65279).Example:• -ldev_id 200

-virtual_ldev_id <ldev#>

Specify an LDEV ID (0-65279) to be used in the virtual storage machine.If you specify "reserve" instead of the LDEV ID, the reserve attribute of global-active device is released.Example:• -virtual_ldev_id 300

-port <port#> Specify a port number. Specify the port number whose attribute is Target.Example:• CL1-A

-virtual_port <port#>

Specify a port number to be used in the virtual storage machine.Example:• CL3-B



When specifying a pool that is already created for Thin Image or Copy-on-Write Snapshot, the specified LDEV is added as a pool volume.

Specify either one of Pool ID or Pool Name certainly. If both the Pool ID and Pool Name options are omitted, this command is rejected with EX_REQARG.


If you create multiple pools with specifying only the pool names, execute the raidcom get command_status command to each pool and confirm each completion.

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


Option Description

-pool_id <pool ID#>

Specifies the Pool ID (0-127) of a Thin Image or Copy-on-Write Snapshot pool.If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.When you omit specifying -pool_id option, you need to specify -pool_name option.When specifying -pool_name option without specifying -pool_id option, a pool ID is allocated automatically.


Specifies the pool name of a pool for Thin Image or Copy-on-Write Snapshot. Up to 32 characters can be specified.When specifying a pool ID or a pool name, if a pool name exists in the specified pool ID, the pool name is overwritten. If the pool volume is added by specifying only a pool ID, the pool name is not changed. When the specification of Pool Name is omitted, a Pool ID must be specified. When the Pool ID is specified and the Pool Name is omitted, a pool name is allocated automatically in the form of "New Pool<number>". The -pool_name option cannot be specified by configuring only in numeric because numeric values are preferentially identified as a pool ID. Specifies a pool ID with the '-pool_id<pool ID#>' option.

-ldev_id <ldev#> Specifies the LDEV number (0-65279). Up to 64 of LDEVs can be specified at a time. For example:• -ldev_id 100• -ldev_id 100-110• -ldev_id 100 -cnt 10


ExamplesUsing LDEVs:400, 401, and 402, creating a pool of Pool ID:1, Pool Name: my_ss_pool for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 1 -pool_name my_ss_pool -ldev_id 400 401 402

Using LDEVs:410, 411, and 412, creating a pool of Pool ID:3, Pool Name: my_ss_pool for Thin Image.

# raidcom add snap_pool -pool_id 3 -pool_name my_ss_pool -ldev_id 410 411 412 -thinsnap

Using LDEVs:500, 501, and 502, creating a pool of Pool ID: Allocated automatically, Pool Name: my_ss_pool for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_name my_ss_pool -ldev_id 500 501 502

Using LDEVs:600, 601, and 602, creating a pool of Pool ID: 2, Pool Name: Allocated automatically for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 2 -ldev_id 600 601 602

Using LDEV belonging to the device group: grp1, creating a pool of Pool ID: 1, Pool Name: Allocated automatically for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 1 -grp_opt ldev -device_grp_name grp1

[-cnt <count> ] Specifies the count (2-64).The count becomes singular if not specified.Up to 64 of LDEVs can be specified at a time.




Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all the LDEVs belonging to the device group are operated.When the -pool_name option is omitted, the device group name changes into the pool name.

[-user_threshold <%> ]

Specifies the user defined threshold value (20-95) %.If this option is omitted, "80" is used.When you add a pool volume, this option is ignored even if it is specified. If you want to change the user defined threshold value of the additional pool volume, execute the raidcom modify pool command.

[-thinsnap] When this option is specified, a pool for Thin Image is created.

Option Description



raidcom get snap_poolDisplays pool information for Thin Image or Copy-on-Write Snapshot.

Syntaxraidcom get snap_pool

Options and parametersNone.

ExamplesDisplaying pool information for Thin Image or Copy-on-Write Snapshot.

# raidcom get snap_poolPID POLS U(%) SSCNT Available(MB) Capacity(MB) Seq# Num LDEV# H(%)003 POLS 100 10000 100 1000000000 62500 1 375 70


PID: pool ID

POLS: Displays the pool status:• - POLN: "Pool Normal" (The pool is in the normal status.)• - POLF: "Pool Full" (The pool is in the overflow status exceeding the

threshold.)• - POLS: "Pool Suspend" (The pool is in the overflow status exceeding the

threshold and is suspended.)• - POLE: "Pool failure" (The pool is suspended in the failure status.) In

this status, the pool information cannot be displayed.

U(%): usage rate of the pool

SSCNT: number of volumes in the pool

Available (MB): available capacity for the data volumes in the pool

Capacity (MB): total capacity of the pool

Seq#: Serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

Num: number of LDEVs in the pool

LDEV#: number of the first LDEV in the pool

H(%): threshold value for the pool

raidcom add snapshotAdd a combination of the specified LDEV number and Pool ID to a snapshot group. If there is no name of specified snapshot group, create a new snapshot group.


Syntaxraidcom add snapshot -ldev_id <ldev#(P)> <ldev#(S)> -pool {<pool ID#> | <pool naming>} -snapshotgroup <name> [-snap_mode <mode>]


ExamplesAdding a combination of the P-VOL (LDEV number 10:10), the S-VOL (LDEV number 20:20), and the Pool (SnapPool00) to the snapshot group (db1).

# raidcom add snapshot -ldev_id 0x1010 0x2020 -pool SnapPool00 -snapshotgroup db1

raidcom delete snapshotDeletes the snapshot data and the snapshot group. The relevant snapshot data of the LDEV is deleted from the snapshot group by specifying LDEV number. When no snapshot data left in the snapshot group, the snapshot group is deleted.

Syntaxraidcom delete snapshot {-snapshotgroup <name> | -ldev_id <ldev#> {-mirror_id <mu#> |-snapshotgroup <name>}}

Option Description

-ldev_id <ldev#(P)> <ldev#(S)>

Specifies the LDEV number to be created the snapshot data. LDEV numbers for P-VOL and S-VOL must be included.


Specifies the pool ID or the pool name created for Snapshot.

-snapshotgroup <name>

Specifies a name to be given for snapshot group.

[-snap_mode <mode>]

Specifies the mode to create a snapshot group.The following mode can be specified:<mode>= CTG: For creating in CTG mode. The CTG number is allocated internally by itself.If this option is omitted, the snapshot group is created in normal mode.This option is effective only when a new snapshot group is to be created.This option is ignored if this is specified for the existing snapshot group.




ExamplesDeleting the snapshot data of the snapshot group (db1).

# raidcom delete snapshot -snapshotgroup db1

Deleting the snapshot data of the P-VOL (LDEV number 10:10) and the Mirror ID (10).

# raidcom delete snapshot -ldev_id 0x1010 –mirror_id 10

Deleting the snapshot data of the LDEV number 10:10 that is included in the snapshot group (db1).

# raidcom delete snapshot -ldev_id 0x1010 -snapshotgroup db1

# raidcom delete snapshot -snapshotgroup db1 -ldev_id 0x1010

Deleting the snapshot data of the S-VOL (LDEV number 20:10).

# raidcom delete snapshot -ldev_id 0x2010

raidcom modify snapshotOperate the specified snapshot group.

Syntaxraidcom modify snapshot -ldev_id <ldev#> {-snapshotgroup <name> | -mirror_id <mu#>} -snapshot_data <op>raidcom modify snapshot -snapshotgroup <name> -snapshot_data <op>raidcom modify snapshot -ldev_id <ldev#> -snapshot_data <op>

Option Description


Specifies the snapshot group in which the target data to be deleted is included.If the snapshot group is specified as the target, all the snapshot data and the snapshot group are deleted.

-ldev_id <ldev#>

Specifies the LDEV number of P-VOL or S-VOL for the snapshot data to be deleted.When P-VOL is specified, specify the snapshot data by specifying the MU number or the snapshot group (Specifying the MU number or the snapshot group is mandatory.).When you specify the S-VOL, do not specify a MU number or a Snapshot group. If you specify the MU number or the Snapshot group, the P-VOL of specified LDEV number becomes the subject of deletion.

-mirror_id <mu#>

Specifies the Mirror ID of the snapshot data to be deleted.


Specifies the snapshot group to be deleted.The smallest number of MU in the snapshot group becomes the subject to be deleted.



The following shows the operation of the snapshot data with the combination of options and parameters:

When creating a snapshot data (when specifying create/split)

When discarding or restoring the snapshot data (when specifying resync/restore)

Option Description

-ldev_id <ldev#>

Specifies the LDEV number of P-VOL (or S-VOL) to be performed.


Specifies the snapshot group name in which the snapshot data is included.

-mirror_id <mu#>

Specifies the mirror ID of a snapshot data.

-snapshot_data <op>

Specifies the operation to be performed for the specified snapshot group. The parameter of the operation to be specified is the following:• create: Creates a snapshot data.• split: Creates a snapshot data.• resync: Discards the created snapshot data.• restore: Restores the snapshot data.

#The ways to specify the parameter

CTG mode normal mode

1 LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2 LDEV number and MU number.

Specified P-VOL and MU number.


3 LDEV number only (Specifying S-VOL).

P-VOL and MU number that are mapped by the specified S-VOL.


4 Snapshot group.

All the P-VOLs related to the snapshot group.The consistency is endured.

All the P-VOLs related to the snapshot group.The consistency is not endured.



1 LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2 LDEV number and MU number.





ExamplesCreating a snapshot data for the P-VOL (LDEV number 10:10) that is included in the snapshot group (db1).

# raidcom modify snapshot -ldev_id 0x1010 -snapshotgroup db1 -snapshot_data create

Creating a snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 –mirror_id 10 -snapshot_data create

Creating a snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data create

Creating a snapshot data for all the P-VOLs that are included in the snapshot group (db1).

# raidcom modify snapshot -snapshotgroup db1 -snapshot_data create

Discarding the snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 –mirror_id 10 -snapshot_data resync

Restoring the snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data restore

raidcom get snapshotDisplays the information of snapshot group and snapshot data that are defined in the device. If this option is omitted, the list of snapshot group is displayed.

Syntaxraidcom get snapshot [-ldev_id <ldev#> | -snapshotgroup <name>][{-check_status | -check_status_not} <string> [-time <time>]]

3 LDEV number only (Specifying S-VOL).



4 Snapshot group.

All the P-VOLs related to the snapshot group.

All the P-VOLs related to the snapshot group.





ExamplesDisplaying the list of snapshot groups.

Option Description

[-ldev_id <ldev#>]

Specifies the LDEV number to be displayed the snapshot data information. Specifies either one of P-VOL or S-VOL for the LDEV number.

[-snapshotgroup <name>]

Specifies the snapshot group in which you want to display the snapshot data information.

[-check_status <string> [-time <time>]]

Check if the snapshot group or the snapshot data is in the state as shown in <string>. The following strings are specified in the <string>.• COPY: Copy status.• PAIR: Pair status.• PSUS: Suspend status.• PSUE: Suspend failure status.• PFUL: Indicates that the Thin Image or Copy-on-Write Snapshot

pool exceeds the threshold in the PAIR status.• PFUS: Indicates that the Thin Image or Copy-on-Write Snapshot

pool exceeds the threshold in the PSUS status.• RCPY: Shows that the copying is in progress by

resynchronization.If the snapshot group or the snapshot data is in the specified state, the operation ends normally.When it is not in the specified status, the operation is placed in wait status for the time (seconds) set by the <time> if "-time" is specified. If "-time" is not specified, the operation soon ends abnormally.

[-check_status_not <string> [-time <time>]]

Check if the snapshot group or the snapshot data is not in the state as shown in <string>. The following strings are specified in the <string>.• COPY: Copy status.• PAIR: Pair status.• PSUS: Suspend status.• PSUE: Suspend failure status.• PFUL: Indicates that the Thin Image or Copy-on-Write Snapshot

pool exceeds the threshold in the PAIR status.• PFUS: Indicates that the Thin Image or Copy-on-Write Snapshot

pool exceeds the threshold in the PSUS status.• RCPY: Shows that the copying is in progress by

resynchronization.If the snapshot group or the snapshot data is not in the specified state, the operation ends normally.When it is in the specified status, the operation is placed in wait status for the time (seconds) set by the <time> if "-time" is specified. If "-time" is not specified, the operation soon ends abnormally.



# raidcom get snapshotSnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIMEsnap1 - - 85000098 - - - - - ---- -snap2 - - 85000098 - - - - - ---- -snap3 - - 85000098 - - - - - ---- -

Displaying the snapshot data related to the specific P-VOL (LDEV number: 14536).

# raidcom get snapshot -ldev_id 14536SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIMEsnap1 P-VOL PAIR 85000098 14536 1010 - 2 100 ---- -snap2 P-VOL PAIR 85000098 14536 1011 13000 2 100 G--- -snap3 P-VOL PAIR 85000098 14536 1012 - 2 100 ---- -

Displaying the snapshot data related to the specific S-VOL (LDEV number: 13000).

# raidcom get snapshot -ldev_id 13000SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIMEsnap2 S-VOL PAIR 85000098 13000 1011 14536 2 100 G--- -

Displaying the snapshot data included in the specific snapshot group.

# raidcom get snapshot -snapshotgroup snap2SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIMEsnap2 P-VOL PAIR 85000098 14536 1011 13000 2 100 G--- -snap2 P-VOL PAIR 85000098 14537 1011 13001 2 100 G--- -snap2 P-VOL PAIR 85000098 14538 1011 13002 2 100 G--- -


SnapShot_name: Displays the name of snapshot group defined in the device.

P/S: Displays the attribute of the target LDEV. It displays P-VOL for the P-VOL and S-VOL for the S-VOL. In the list of snapshot, "-" is displayed.

STAT: Displays the status of each snapshot data. For details, see pairdisplay on page 2-45.

Serial#: Displays the product serial number. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

LDEV#: Displays the LDEV number related to the snapshot.

MU#: Displays the Mirror ID.

P-LDEV#: Displays the LDEV number of the volume (P-VOL or S-VOL) of the pair associated with the snapshot data. If the LDEV that is paired belongs to a different virtual storage machine, "----" is displayed.

PID: Displays the pool ID.

%: Displays the concordance rate between P-VOL and S-VOL.

MODE: Displays the status of snapshot data:• G: The snapshot data created in CTG mode.


• W: The status when the data are written in the secondary volume from the host in the PSUS/PFUS status.

SPLT-TIME: Displays the time when a snapshot data is created. Indicating accumulated time in seconds from January 1, 1970 (GMT).

raidcom add spm_wwnSpecifies the Server Priority Manager name for preferred/non-preferred WWNs.

Syntaxraidcom add spm_wwn -port <port#> -spm_name <nick_name> -hba_wwn <wwn_strings>


ExamplesSpecifies the SPM name (WWN_NICK_LINUX) to WWN (50060e8005fa0f36).

# raidcom add spm_wwn -port CL4-E -spm_name WWN_NICK_LINUX -hba_wwn 50060e80,05fa0f36

raidcom delete spm_wwnDeletes WWN from the Server Priority Manager targets.

Syntaxraidcom delete spm_wwn -port <port#> [-hba_wwn <wwn_string> | -spm_name <nick_name>]

Option Description

-port <port#> Specifies the port number with the Target attribute, for example:• CL1-A

-spm_name <nick_name>

Specifies the SPM name.Up to 64 characters can be specified by CLI.SPM names are managed uniquely in the entire system.

-hba_wwn <wwn_strings>

Specifies the monitored WWN.Before setting the SPM name, the WWN must be registered as preferred or non-preferred.WWN is specified as a 16-digit hexadecimal number. The 17th digit is ignored.




Examples

Deletes the SPM name (WWN_NICK_LINUX) from the SPM targets.

# raidcom delete spm_wwn -port CL4-E -spm_name WWN_NICK_LINUX

Deletes the WWN (50060e8005fa0f36) from the SPM targets.

# raidcom delete spm_wwn -port CL4-E -hba_wwn 50060e80,05fa0f36

raidcom modify spm_wwnSpecifies the Server Priority Manager information to the Server Priority Manager target WWN.

Syntaxraidcom modify spm_wwn -port <port#> [-spm_priority <y/n>]{-limit_io | -limit_kb | -limit_mb } <value>{-hba_wwn <wwn_strings> | -spm_name <nick_name>}


Option Description

-port <port#> Specifies the port number whose attribute is Target. For example: • CL1-A

-hba_wwn <wwn_string>

Specifies WWN to be deleted.WWN is specified in hexadecimal number of 16 digits. The 17th digit or later is ignored.


Specifies the SPM name to be deleted.Up to 64 characters can be specified by CLI.

Option Description

-port <port#> Specifies the port number whose attribute is Target. For example:• CL1-A

-spm_priority <y/n>

Specifies preferred/non-preferred WWN.• y: preferred WWN• n: non-preferred WWN

{-limit_io | -limit_kb | -limit_mb } <value>

Specifies maximum value/threshold value by the I/O rate or the transmission rate.• -limit_io: I/O rate, maximum value: 2,147,483,647 [IOPS]• -limit_kb: transmission rate (unit of KB), maximum value:

2,147,483,647 [KB]• -limit_mb: transmission rate (unit of MB), maximum value:

2,097,151 [MB](If the value is specified by MB, 1 MB is calculated as 1024 KB.)

The threshold value for the prioritized WWN is the same as the threshold value for the entire system.


Examples

Specifies WWN (50060e8005fa0f36) as non-preferred WWN, and specifies 5000/[I/O] (I/O rate) as the maximum value.

# raidcom modify spm_wwn -port CL4-E -spm_priority n -limit_io 5000 -hba_wwn 50060e80,05fa0f36

Specifies the SPM name (WWN_NICK_LINUX) as non-preferred WWN, and specifies 500[MB/s] (transmission rate) as the maximum value.

# raidcom modify spm_wwn -port CL4-E -spm_priority n -limit_mb 500 -spm_name WWN_NICK_LINUX

Specifies WWN (50060e8005fa0f36) as preferred WWN, and specifies 5000/[I/O] (I/O rate) as the threshold value.

# raidcom modify spm_wwn -port CL4-E -spm_priority y -limit_io 5000 -hba_wwn 50060e80,05fa0f36

Specifies the SPM name (WWN_NICK_LINUX) as preferred WWN, and specifies 500000[KB/s] (transmission rate) as the maximum value.

# raidcom modify spm_wwn -port CL4-E -spm_priority y -limit_kb 500000 -spm_name WWN_NICK_LINUX

Deletes the SPM information of WWN (50060e8005fa0f36).

# raidcom modify spm_wwn -port CL4-E -hba_wwn 50060e80,05fa0f36

Deletes the SPM information of the SPM name (WWN_NICK_LINUX).

# raidcom modify spm_wwn -port CL4-E -spm_name WWN_NICK_LINUX

raidcom get spm_wwnGets the Server Priority Manager information of the Server Priority Manager target WWN.

Syntaxraidcom get spm_wwn -port <port#> [-hba_wwn <wwn_strings> | -spm_name <nick_name>


-hba_wwn <wwn_strings> |

Specifies WWN that you set the SPM informartion.WWN is specified as a 16-digit hexadecimal number. The 17th digit is ignored.


Specifies the SPM name.Up to 64 characters can be specified by CLI.

Option Description

Option Description




Examples

Gets the SPM information of WWN that belongs to the specified port (CL4-E).

#raidcom get spm_wwn -port CL4-EPORT SPM_MD SPM_WWN NICK_NAME GRP_NAME Serial#CL4-E WWN 210000e08b0256f8 WWN_NICK_LINUX_0 OLA_NODE0_CTL 63528CL4-E WWN 210000e08b0256f7 WWN_NICK_LINUX_1 OLA_NODE0_CTL 63528

Specifies WWN (50060e8005fa0f36) to get the SPM information.

# raidcom get spm_wwn -port CL4-E -hba_wwn 50060e80,05fa0f36PORT SPM_MD PRI IOps KBps Serial#CL4-E WWN Y 5000 - 63528

Specifies the SPM name (WWN_NICK_LINUX) to get the SPM information.

# raidcom get spm_wwn -port CL4-E -spm_name WWN_NICK_LINUXPORT SPM_MD PRI IOps KBps Serial#CL4-E WWN Y - 5000 63528

Description on each column in output example

PORT: Displays the port to which the WWN is set.

SPM_MD: Displays the Control mode of the SPM.• WWN: WWN control• PORT: Port control

SPM_WWN: Displays the set WWN.

NICK_NAME: Displays the SPM name set to the WWN. If the SPM name is not set, a hyphen (-) is displayed.

GRP_NAME: Displays the SPM group name to which the WWN belongs. If the WWN does not belong to the group, a hyphen (-) is displayed.

Serial#: Displays the Seq#. For VSP G1000 the serial number is displayed with a “3” added to the beginning (for example, “312345” = serial number 12345).

PRI: Displays the settings of the priority.• Y: Preferred• N: Non-preferred

IOps: If the PRI setting is Y, it displays the threshold. If the PRI setting is N, it displays the maximum value. If the value is set by the transferred rate (KBps), it displays a hyphen (-).


Specifies WWN that you get the SPM informartion.WWN is specified as a 16-digit hexadecimal number. The 17th digit is ignored.


Specifies the SPM name that you get the SPM information.Up to 64 characters can be specified by CLI.

Option Description


KBps: If the PRI setting is Y, it displays the threshold. If the PRI setting is N, it displays the maximum value. If the value is set by the IO rate (IOps), it displays a hyphen (-). If the value is set by MB, 1 MB is calculated as 1024 KB, and displays the value by KB.

raidcom monitor spm_wwnGets the monitoring information of Server Priority Manager target WWN.

Syntaxraidcom monitor spm_wwn {-hba_wwn <wwn_strings> | -spm_name <nick_name>}


Examples

Specifies WWN (50060e8005fa0f36) to get the monitoring information.

# raidcom monitor spm_wwn -hba_wwn 50060e80,05fa0f36PORT SPM_MD IOps KBps Serial#CL4-E PORT 5000 5000000 63528

Specifies the SPM name (WWN_NICK_LINUX) to get the monitoring information.

# raidcom monitor spm_wwn -spm_name WWN_NICK_LINUXPORT SPM_MD IOps KBps Serial#CL4-E PORT 5000 5000000 63528




IOps: Displays the current IO rate (IOps) of the specified WWN of or the specified SPM name.

KBps: Displays the current transferred rate (KBps) of the specified WWN or the specified SPM name.


Option Description


Specifies WWN that you get the monitoring informartion.WWN is specified as a 16-digit hexadecimal number. The 17th digit is ignored.


Specifies the SPM name that you get the monitoring information.Up to 64 characters can be specified by CLI.



raidcom add spm_groupRegisters Server Priority Manager target WWN to Server Priority Manager group.

Syntaxraidcom add spm_group -port <port#> -spm_group <group_name> [<nick_name>]raidcom add spm_group -port <port#> -spm_group <group_name> -hba_wwn <wwn_strings>


Examples

Registers WWN (50060e8005fa0f36) as the group name (WWN_GRP_LINUX).

# raidcom add spm_group -port CL4-E -spm_group WWN_GRP_LINUX -hba_wwn 50060e80,05fa0f36

Registers the SPM name (WWN_NICK_LINUX) as the group name (WWN_GRP_LINUX).

# raidcom add spm_group -port CL4-E -spm_group WWN_GRP_LINUX WWN_NICK_LINUX

raidcom delete spm_groupDeletes the Server Priority Manager target WWN from the Server Priority Manager group and releases the specified WWN from the monitoring.

Syntaxraidcom delete spm_group -port <port#> -spm_group <group_name>


Option Description

-port <port#> Specifies the port number whose attribute is Target. For example: • CL1-A

-spm_group <group_name>[<nick_name>]

Specifies the SPM group name and SPM name. Up to 64 characters can be specified by CLI.If a <nick_name> is omitted, you must specify the -hba_wwn option.SPM group names are managed uniquely in the entire system.


Specifies SPM target WWN.WWN is specified as a 16-digit hexadecimal number. The 17th digit is ignored.

Option Description



Examples

Deletes the SPM group (WWN_GRP_LINUX).

# raidcom delete spm_group -port CL4-E -spm_group WWN_GRP_LINUX

raidcom modify spm_groupSpecifies the Server Priority Manager information to the Server Priority Manager target group.

Syntaxraidcom modify spm_group -port <port> [-spm_priority <y/n>]{-limit_io | -limit_kb | -limit_mb } <value> -spm_group <group_name>


Examples

Specifies the SPM group name (WWN_GRP_LINUX) as non-preferred WWN, and specifies 5000[I/O] (I/O rate) as the maximum value.

# raidcom modify spm_group –port CL4-E –spm_priority n –limit_io 5000 –spm_group WWN_GRP_LINUX

-spm_group <group_name>

Specifies the SPM group name.Up to 64 characters can be specified by CLI.

Option Description

Option Description


-spm_priority <y/n>

Specifies preferred/non-preferred WWN.• y: preferred WWN• n: non-preferred WWN

{-limit_io | -limit_kb | -limit_mb } <value>

Specifies maximum value/threshold value by the I/O rate or the transmission rate.• -limit_io: I/O rate, maximum value: 2,147,483,647 [IOPS]• -limit_kb: transmission rate (unit of KB), maximum value:

2,147,483,647 [KB]• -limit_mb: transmission rate (unit of MB), maximum value:

2,097,151 [MB]If you specify the value per MB, 1 MB is calculated as 1024 KB.

The threshold value for the prioritized WWN is the same as the threshold value for the entire system.


Specifies the SPM group name that you set the SPM information.Up to 64 characters can be specified by CLI.



Specifies the SPM group name (WWN_GRP_LINUX) as non-preferred WWN, and specifies 500[MB/s] (transmission rate) as the maximum value.

# raidcom modify spm_group –port CL4-E –spm_priority n –limit_mb 500 –spm_group WWN_GRP_LINUX

Specifies the SPM group name (WWN_GRP_LINUX) as preferred WWN, and specifies 5000[I/O] (I/O rate) as the threshold value.

# raidcom modify spm_group –port CL4-E –spm_priority y –limit_io 5000 –spm_group WWN_GRP_LINUX

Specifies the SPM group name (WWN_GRP_LINUX) as preferred WWN, and specifies 500000[KB/s] (transmission rate) as the threshold value.

# raidcom modify spm_group –port CL4-E –spm_priority y –limit_kb 500000 –spm_group WWN_GRP_LINUX

Deletes the SPM information of the SPM group name (WWN_GRP_LINUX).

# raidcom modify spm_group –port CL4-E –spm_group WWN_GRP_LINUX

raidcom get spm_groupGets the Server Priority Manager information of the Server Priority Manager target WWN in the specified port by the Server Priority Manager group unit.

Syntaxraidcom get spm_group -port <port#> -spm_group <group_name>


Examples

Specifies the port (CL4-E) and the SPM group name (WWN_GRP_LINUX) to get the SPM information.

# raidcom get spm_group -port CL4-E -spm_group WWN_GRP_LINUXPORT SPM_MD PRI IOps KBps Serial#CL4-E PORT Y 5000 - 63528




PRI: Displays the settings of the priority.

Option Description





• Y: Preferred• N: Non-preferred

IOps: If the PRI setting is Y, it displays the threshold. If the PRI setting is N, it displays the maximum value. If the value is set by the transferred rate (KBps), it displays a hyphen (-).

KBps: If the PRI setting is Y, it displays the threshold. If the PRI setting is N, it displays the maximum value. If the value is set by the IO rate (IOps), it displays a hyphen (-). If the value is set by MB, 1 MB is calculated as 1024 KB, and displays the value by KB.


raidcom monitor spm_groupGets the monitoring information of Server Priority Manager target WWN by the Server Priority Manager group unit.

Syntaxraidcom monitor spm_group -spm_group <group_name>


Examples

Specifies the SPM group name (WWN_GRP_LINUX) to get the monitoring information.

# raidcom monitor spm_group -spm_group WWN_GRP_LINUXPORT SPM_MD IOps KBps Serial#CL4-E PORT 5000 5000000 63528




IOps: Displays the current IO rate (IOps) of the specified WWN or the specified SPM name.

KBps: Displays the current transferred rate (KBps) of the specified WWN or the specified SPM name.

Option Description






raidcom add dp_poolCreate a pool for Dynamic Provisioning or Dynamic Provisioning for Mainframe by the specified LDEVs. Or, add pool volumes to the pools for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe. A device group can also be specified instead of an LDEV.

When specifying a pool that is already created for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe, the specified LDEV is added as a pool volume.

Specify either one of Pool ID or Pool Name certainly. If both the Pool ID and Pool Name options are omitted, this command is rejected with EX_REQARG.


If you create multiple pools with specifying only the pool names, execute the raidcom get command_status command to each pool and confirm each completion.

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


Option Description

-pool_id <pool ID#>

Specifies the Pool ID (0-127) for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe. When the specification of Pool ID is omitted, a Pool Name must be specified.If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.When you omit specifying -pool_id option, you need to specify -pool_name option.When specifying -pool_name option without specifying -pool_id option, a pool ID is allocated automatically.



Specifies a pool name of a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe. Up to 32 characters can be specified.When specifying a pool ID or a pool name, if the pool name exists in the specified pool ID, the pool name is overwritten. If the pool volume is added by specifying only a pool ID for already existing pool, the pool name is not changed. When the specification of Pool Name is omitted, a Pool ID must be specified. When the Pool ID is specified and the Pool Name and -device_grp_name option are omitted, a pool name is allocated automatically in the form of "New Pool<number>". The -pool_name option cannot be specified by configuring only in numeric because numeric values are preferentially identified as a pool ID. Specifies a pool ID with the '-pool_id<pool ID#>' option.


Specifies the LDEV number (0-65279). Up to 64 of LDEVs can be specified at a time. For example:• -ldev_id 100• -ldev_id 100 - 110• -ldev_id 100 -cnt 10

[-cnt <count> ] Specifies the count (2-64).If this specificaion is omitted, "1" is used.Up to 64 of LDEVs can be specified at a time.




Specifies the name of device group (maximum 32 characters) to be operated.To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.If the device name is omitted, all the LDEVs belonging in the device group are operated.When the -pool_name option is omitted, the device group name changes into the pool name.

[-user_threshold <threshold_1> [<threshold_2>] ]

You may specify two user-defined thresholds, and their valid ranges are 1-100%, respectively. If you specify <threshold_1> and <threshold_2>:the value of <threshold_1> is set as the threshold for WARNING specified to a pool.the value of <threshold_2> is set as the threshold for High water mark specified to a pool.If you specify only <threshold_1>, your specified value and the system default value (80%) are applied. If you omit to specify the value, 70% and 80% are applied, automatically.When you add a pool volume, this option is ignored even if it is specified. If you want to change the user defined threshold value of the additional pool volume, execute the raidcom modify pool command.

Option Description



ExamplesBy using LDEVs:400, 401, and 402, creating a pool of Pool ID:1, Pool Name: my_pool for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 1 -pool_name my_pool -ldev_id 400 401 402

By using LDEVs:500, 501, and 502, creating a pool of Pool ID: Allocated automatically, Pool Name: my_pool for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_name my_pool -ldev_id 500 501 502

By using LDEVs:600, 601, and 602, creating a pool of Pool ID: 2, Pool Name: Allocated automatically for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 2 -ldev_id 600 601 602

By using LDEVs: 700, 701, and 702, creating a pool of Pool ID: 3, Pool Name: my_pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, with the user-defined thresholds WARNING specified to 70% and High water mark to 80%.

# raidcom add dp_pool -pool_id 3 -pool_name my_pool -ldev_id 700 701 702 -user_threshold 70 80

Add LDEV: 368 to the pool ID: 10 for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe.

# raidcom add dp_pool -pool_id 10 -ldev_id 368

By using LDEV belonging to the device group: grp1, creating a pool of Pool ID:1, pool name: Allocated automatically for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 1 -grp_opt ldev -device_grp_name grp1

raidcom get dp_poolDisplays pool information for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe.

Syntaxraidcom get dp_pool [-key <keyword> [-fx] [-pool {<pool_id> | <pool naming >} ]]


Option Description

[-key <keyword> [-fx]]

Specifies the display keyword. Specify opt as <keyword>. If you specify opt, information about Dynamic Tiering and Dynamic Tiering for Mainframe pool is displayed.If you specify the -fx option, TL_RANGE and TD_RANGE are displayed in hexadecimal notation.


ExamplesDisplaying the pool information of the pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe.

# raidcom get dp_poolPID POLS U(%) AV_CAP(MB) TP_CAP(MB) W(%) H(%) Num LDEV# LCNT TL_CAP(MB)001 10 45000000 50000000 50 80 2 265 33 65000000 002 POLF 95 10000 100000000 50 80 3 270 900 100000000 004 POLN 0 10000000 100000000 80 90 2 280 0 200000000


PID: Displays the pool ID for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe.

POLS: Displays the following status of the pool.• POLN: "Pool Normal" (The pool is in the normal status.)• POLF: "Pool Full" (The pool is in the overflow status exceeding the

threshold.)• POLS: "Pool Suspend" (The pool is in the overflow status exceeding the

threshold and is suspended.)• POLE: "Pool failure" (The pool is suspended in the failure status.) In this

status, the pool information cannot be displayed.

U(%): Displays the usage rate of the pool.

AV_CAP(MB): Displays the available capacity for the volumes of Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe mapped to this pool.

TP_CAP(MB): Displays the total capacity of the pool.

W(%): Displays the threshold value for "WARNING" set for the pool.

H(%): Displays the threshold value set for the pool as high water mark.

Num: Displays the number of LDEVs configuring the pool.

LDEV#: Displays the LDEV number of a pool-VOL that includes the pool management area.

[-pool {<pool_id> | <pool naming >} ]

Specifies the pool ID or the pool name of Dynamic Tiering/Dynamic Tiering for Mainframe when you want to display the range for each tiering level of Dynamic Tiering/Dynamic Tiering for Mainframe pools. When you specify only digits, it is recognized as a pool ID. When the pool name consists of digits, specify the pool ID instead of the pool name.

Option Description



LCNT: Displays the total number of Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe volumes mapped to the pool.

TL_CAP(MB): Displays the total capacity of all Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe volumes mapped to the pool.

Displays the tier information of the pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, or Dynamic Tiering for Mainframe. For details about the parameters, see the Provisioning Guide for the storage system.

# raidcom get dp_pool -key opt

PID POLS MODE STS DAT TNO TL_RANGE TD_RANGE TU_CAP(MB) TT_CAP(MB) T(%) P(%) R(%) B(%) MM

001 POLN DEF STP VAL 1 00005000 00003000 200000 1000000 80 54 98 40 PM

001 POLN DEF STP VAL 2 00003000 00002000 400000 1000000 80 54 98 30 CM

001 POLN DEF STP VAL 3 00002000 00002000 600000 1000000 80 54 98 40 PM

002 POLF AUT MON PND 1 - - 500000 1000000 80 54 100 2 PM

When you specify -pool, it displays the range for each tiering level of corresponding pools.

# raidcom get dp_pool -pool 1 -key optPID POLS MODE STS DAT TNO TL_RANGE TD_RANGE TU_CAP(MB) TT_CAP(MB) T(%) P(%) R(%) B(%) MM001 POLN DEF STP VAL 0 4294967294 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 0 4294967294 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 0 00000000 00000000 504 8190 10 33 100 2 PM001 POLN DEF STP VAL 1 00000000 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 1 00000000 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 1 00000000 00000000 504 8190 10 33 100 2 PM001 POLN DEF STP VAL 2 00000039 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 2 00000000 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 2 00000000 00000000 504 8190 10 33 100 2 PM001 POLN DEF STP VAL 3 00000100 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 3 00000041 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 3 00000000 00000000 504 8190 10 33 100 2 PM001 POLN DEF STP VAL 4 00000001 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 4 00000000 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 4 00000000 00000000 504 8190 10 33


100 2 PM001 POLN DEF STP VAL 5 00000001 00000000 8064 8190 10 28 100 2 PM001 POLN DEF STP VAL 5 00000001 00000000 3948 3990 10 100 100 2 PM001 POLN DEF STP VAL 5 00000000 00000000 504 8190 10 33 100 2 PM


PID: Displays the pool ID for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tiering for Mainframe.

POLS: Displays the following status of the pool.• POLN: "Pool Normal" (The pool is in the normal status.)• POLF: "Pool Full" (The pool is in the overflow status exceeding the

threshold.)• POLS: "Pool Suspend" (The pool is in the overflow status exceeding the

threshold and is suspended.)• POLE: "Pool failure" (The pool is suspended in the failure status.) In this

status, the pool information cannot be displayed.

MODE: Displays the execution mode.• DEF: The start/termination of the monitor is performed by the

instruction of the CCI, and the tier range setting is performed by the automatic calculation of the storage system.

• AUT: The start/termination of the monitor is performed by time specification, and the tier range setting is performed by the automatic calculation of the storage system.Note: AUT cannot be instructed from the CCI. AUT can only performed if displayed when set from the SN2.

STS: Displays the operational status of the performance monitor and the tier relocation.• STP: The performance monitor and the tier relocation are stopped.• RLC: The performance monitor is stopped. The tier relocation is

operating.• MON: The performance monitor is operating. The tier relocation is

stopped.• RLM: The performance monitor and the tier relocation are operating.

DAT: Displays the status of the monitor information.• VAL: Valid.• INV: Invalid.• PND: Being calculated.

TNO: Tiering number. When you specify the pool, it displays the tiering level (0 means "all" is set to the level of tiering policy).

TL_RANGE: Lowest limit value of the tier in IOPH.



0 (0x00000000) to 4294967294 (0xFFFFFFFE): When "all" is set to the level of tiering policy, the lowest limit value of the tier is displayed. When there is no V-VOL where "all" is set to the level of tiering policy, or when there is no V-VOL related to the pool, the invalid value "-" (0xFFFFFFFF) is displayed. If the -fix option is specified, this displays the value in parentheses given in hexadecimal.

TD_RANGE: Delta value of the tier in IOPH. 0 (0x00000000) to 4294967294 (0xFFFFFFFE): When "all" is set to the level of tiering policy, the lowest limit value of the tier is displayed. When there is no V-VOL where "all" is set to the level of tiering policy, or when there is no V-VOL related to the pool, the invalid value "-" (0xFFFFFFFF) is displayed. If the -fix option is specified, this displays the value in parentheses given in hexadecimal.

TU_CAP(MB): Tier capacity (Usage amount)

TT_CAP(MB): Tier capacity (Total capacity)

T(%): The free space percentage for the new allocation

P(%): Performance working ratio

R(%): Progress percentage of relocation.• 0 to 99: Shows one of the following statuses.

When the value of STS is RLC or RLM: relocation is in progress. When the value of STS is STP or MON: relocation is suspended.

• 100: Shows if the relocation operation is not in progress, or the relocation is complete.

B(%): Displays the amount of buffer for the tier reallocation.

MM: Displays the mode of performance monitoring:• PM: Periodical mode.• CM: Continuous mode.

MK-90RD7009-18

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]

command control interface command reference · pdf filesyntax ... hitachi command control...

Documents