HP StorageWorks Command View Advanced Edition Migration User

HP StorageWorks Command View Advanced Edition Migration User

Migration User Guide for the HP Command View XP Portfolio and

HP XP Remote Web Console

Part number: T1780-96005

First edition: July 2005

Legal and notice information

© Copyright 2005 Hewlett-Packard Development Company, L.P.

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

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

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java™ is a U.S. trademark of Sun Microsystems, Inc.

Microsoft Windows is a U.S. registered trademarks of Microsoft Corporation.

Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of The Open Group.

Printed in the US

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Helpful Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Migration overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Recommended configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Option 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Comparing Command View AE and Command View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP StorageWorks XP Remote Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Remote Web Console environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

New Remote Web Console features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Remote Web Console options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

User Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

User group permissions and mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

XP10000/XP12000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

XP1024/XP128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using Remote Web Console without updated firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing Remote Web Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

User sessions: Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Other comparisons between Remote Web Console and the Command View portfolio . . . . . . . . . . . 19

Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Migration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Scenario 1: Migrate to Command View AE with Remote Web Console . . . . . . . . . . . . . . . . . . . . . . . 22

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Requirement(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Accessing new features after migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Scenario 2: Migrate to standalone Remote Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Requirement(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Accessing new features after migration:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Scenario 3: Migrate from Command View to Remote Web Console with Command View . . . . . . . . . . 23

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Requirement(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Accessing new features after migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Negating migration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Scenario 4: Command View AE and Command View installed on the same management server . . . . . . 24

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Confirm migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Accessing new features after migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Negating migration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Scenario 5: Command View AE and Command View installed on different management servers. . . . . . 26

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

3

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Requirement(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Confirm migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

CLI Client Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Accessing new feature after migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Confirm migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Negating migration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Command View CLI migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Application-related migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Supported migration applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Fast Recovery Solution (FRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Standalone Hitachi software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

OpenView Storage Area Manager (Storage Area Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Path Connectivity-related migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Major Path Connectivity features not found in Command View AE . . . . . . . . . . . . . . . . . . . . . . . . 29

Command View AE host: additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Replacing missing features after migration to Command View AE . . . . . . . . . . . . . . . . . . . . . . . . . 29

HP System Insight Manager 5.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

HP Storage Essentials Enterprise Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Performance Advisor (PA) and Application Policy Manager (APM). . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Impact of this migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Confirm migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Negating migration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Third-party products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Miscellaneous migration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Command View license entitlement migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Migration of audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2 CLI migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLI migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLI Migration Tool overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLI Migration Tool requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLI Migration Tool limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Supported target environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Supported commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Translating batch files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Using the CLI Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

CLI Migration Tool procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Invoking the CLI Migration Data Collection Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Invoking the CLI Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Format of input file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Format of property file <arrayserialNo>.properties: optional parameter . . . . . . . . . . . . . . . . . . . . . . . 33

XP128/XP1024/XP12000/XP10000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

XP512/XP48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Format of output file <inputFileName_out.bat> or <inputFileName_out.sh>. . . . . . . . . . . . . . . . . . . . . 35

Working with the CLI Migration Tool files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Setting up the CLI Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Execution of the CLI Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

CLI Migration Data Collection Tool (cmdct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

XP512/XP48:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

XP128/XP1024/XP12000/XP10000: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Mapping Command View CLI commands to Command View AE CLI commands . . . . . . . . . . . . . . . . . 38

Comparing component display names and component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Port name versus port ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4

XP12000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

XP1024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

XP128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

XP512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

XP48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

XP10000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Port fibre address values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Fibre topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Host mode values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

XP48/XP512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

XP128/XP1024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

XP12000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Object Id representation in Command View AE CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

LUN group object ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

WWN group object ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Path object ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Host group object ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Logical Unit object ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

WWN value representation in Command View AE CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

A Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

CLI Migration Tool error/completion messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

CLI Migration Tool error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Command View CLI Data Collection Tool error/completion messages (“cmdct”): . . . . . . . . . . . . . . . . . . . 72

B Sample commands for CLI migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Sample Command View CLI commands versus Command View AE CLI commands . . . . . . . . . . . . . . . . . . 73

EXPAND LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Command View CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

XP48/XP512 arrays: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

XP128/XP1024/XP12000/XP10000 arrays: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Command View AE CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

XP48/XP512 arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

XP128/XP1024/XP12000/XP10000 arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Sample Command View CLI versus Command View AE CLI output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Command View CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

1) list device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

2) list array_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3) list port -l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4) list port -hostgrp -l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5) cat Test.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Command View AE CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

1) Hdvmcli GetStorageArray <equivalent to list device> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2) Hdvmcli GetStorageArray serialnum=10227 model=XP12000 <equivalent to list array_config for

10227> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

3) Hdvmcli GetStorageArray subtarget=Port portsubinfo=HostStorageDomain serialnum=10227 model=XP12000 <equivalent to list port -l and list port -hostgrp -l for 10227> . . . . . . . . . . . . . . . . 76

4) $ pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5) fi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Sample executions of the CLI Migration Tool (XP128/XP1024/XP10000/XP12000) . . . . . . . . . . . . . . . . 79

Sample execution of the CLI Migration Data Collection Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Sample execution of the CLI Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Sample execution of the CLI Migration Data Collection Tool (XP48/XP512) . . . . . . . . . . . . . . . . . . . . 80

Sample execution of the CLI Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

C FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Does “cmt” communicate with the Command View server? . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Does “cmt” communicate with the Command View AE server and submit translated commands? . 83

Does “cmt” communicate with the array SVP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Does “cmdct” communicate with the Command View server? . . . . . . . . . . . . . . . . . . . . . . . . . 83

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

5

Does “cmdct” communicate with Command View AE to collect data?. . . . . . . . . . . . . . . . . . . . 83

Does “cmdct” communicate with the array SVP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

How do I find out if data collection from the array is required? . . . . . . . . . . . . . . . . . . . . . . . . 83

What will happen if data collection was needed before command file migration but was not done because the array was unavailable or due to some other reason? . . . . . . . . . . . . . . . . . . . . . . 83

Can the same property file serve as input for multiple command file migrations? . . . . . . . . . . . . 84

Can the property file that is generated by cmdct be manually repaired/edited? . . . . . . . . . . . . 84

The host screen for my host does not show some LUNs assigned for that host . . . . . . . . . . . . . . 84

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figures

1 HP StorageWorks XP Remote Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2

Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

3 Comparison of Command View AE and Command View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Remote Web Console Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5 Command VIew user groups permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6 Remote Web Console mapping to Command View users (XP10000/XP12000) . . . . . . . . . . . . . . . . . 17

7 Remote Web Console and Command View default users (XP10000/XP12000) . . . . . . . . . . . . . . . . . 17

8 Remote Web Console mapping to Command View users (XP1024/XP128) . . . . . . . . . . . . . . . . . . . . 18

9 Remote Web Console and Command View default users (XP1024/XP128) . . . . . . . . . . . . . . . . . . . . 18

10 Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

11 Application environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

12 Applications supported for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

13 CLI Migration Tool files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

14

Manual CLI command mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

15

XP12000 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

16

XP1024 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

17

XP128 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

18

XP512 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

19

XP48 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

20

XP10000 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

21 Command parameter usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

22 Fibre Addresses/Arbitrated Loop IDs (all array types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

23 Port fibre topology values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

24 XP48/XP512 port host mode values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

25 XP128/XP1024 port host mode values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

26 XP12000/XP10000 port host mode values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

6

About this guide

This guide provides information about:

Planning and evaluating your migration

Migrating to a new environment

Using the migration tools

Intended audience

This guide is intended for customers and HP authorized service providers who are experienced with the following:

Disk array hardware and software

Storage systems

Prerequisites

Prerequisites for migrating include the following:

Knowledge of operating systems

Knowledge of HP StorageWorks XP disk arrays and storage systems

Set up the HP StorageWorks XP disk arrays

Related documentation

In addition to this guide, please refer to other documents for product information, including the following:

HP StorageWorks Command View XP Advanced Edition Device Manager Management Server

Installation and Configuration Guide

HP StorageWorks Command View XP Advanced Edition Device Manager Agent Installation Guide

HP StorageWorks Command View XP Advanced Edition Device Manager Command Line Interface

(CLI) User’s Guide

HP StorageWorks Command View XP Advanced Edition Device Manager Web Client User’s Guide

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128

Readme.txt (included on the migration kit CD)

These and other HP documents can be found on the HP Web site: http://www.hp.com/support/ .

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

7

Document conventions and symbols

Table 1

Document conventions

Convention

Medium blue text: Figure 1

Medium blue, underlined text

( http://www.hp.com

)

Bold font

Element

Cross-reference links and e-mail addresses

Web site addresses

Italics font

Monospace font

Monospace, italic font

Monospace, bold font

Key names

Text typed into a GUI element, such as into a box

GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes

Text emphasis

File and directory names

System output

Code

Text typed at the command-line

Code variables

Command-line variables

Emphasis of file and directory names, system output, code, and text typed at the command line

CAUTION:

Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT:

Provides clarifying information or specific instructions.

NOTE:

Provides additional information.

TIP:

Provides helpful hints and shortcuts.

8

HP technical support

Telephone numbers for worldwide technical support are listed on the HP support Web site: http://www.hp.com/support/ .

Collect the following information before calling:

Technical support registration number (if applicable)

Product serial numbers

Product model names and numbers

Applicable error messages

Operating system type and revision level

Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

HP strongly recommends that customers sign up online using the Subscriber's choice Web site at http://www.hp.com/go/e-updates .

Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources.

After signing up, you can quickly locate your products by selecting Business support and then selecting

Storage under Product Category.

HP-authorized reseller

For the name of your nearest HP-authorized reseller:

In the United States, call 1-800-345-1518.

Elsewhere, visit the HP web site: http://www.hp.com

. Then click Contact HP to find locations and telephone numbers.

Helpful Web sites

For third-party product information, see the following HP Web sites:

http://www.hp.com

http://www.hp.com/go/storage

http://www.hp.com/support/

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

9

10

1 Migration

NOTE:

These reference names are used throughout this user guide:

• HP StorageWorks Command View XP, version 2.

x, is called Command View

• HP StorageWorks Command View XP Advanced Edition is called Command View AE

• HP StorageWorks XP Remote Web Console is called Remote Web Console

Migration overview

HP StorageWorks Command View XP Advanced Edition (Command View AE) is the first release of a new strategic device manager in the Command View XP portfolio. It provides additional, complementary features to the Remote Web Console.

HP StorageWorks XP Remote Web Console (Remote Web Console) was previously delivered as an array-management graphical user interface (GUI) that required Command View 2.

x; it is now offered as a standalone array-management option.

This user guide provides information that is necessary for transitioning to an environment that is best suited for your array management needs. Use it to define, implement, and tailor migration for your storage environment.

The following information will help to guide you through the migration process:

Planning your migration, and evaluating the benefits to and impact on your current environment (see

” Migration planning ” on page 12)

Evaluating Command View AE and Command View (see ” Comparison of Command View AE and

Command View ” on page 13)

Understanding Remote Web Console (see ” HP StorageWorks XP Remote Web Console ” on page 15)

Determining the appropriate migration procedures for your particular storage environment. (See

Table 10 on page 20)

Using the migration procedures to transition to your preferred environment (see ” Migration procedures ” on page 22)

Performing application-related migration (see ” Application-related migrations ” on page 28)

Using the CLI Migration Tool (see ” CLI migration ” on page 31.)

NOTE:

See the readme.txt file in the migration kit for the most current requirements and any last-minute announcements.

The migration might affect other aspects of your array-management environment. For example, Command

View and Command View AE cannot manage the same arrays concurrently.

This guide helps you understand and accommodate such issues.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

11

Migration planning

This section helps you analyze and plan your migration.

Recommended configurations

Table 2

will help you to select the appropriate configuration, depending on the functionality required for your storage environment. The following options are referenced within the table.

Option 1

Move to Command View AE (stop using Command View).

Option 2

Continue to use Command View for existing arrays and start to use Command View AE for newly purchased arrays and for transitioning management of arrays. Two types of configurations are possible with this option:

a. Co-install Command View AE and Command View on the same system

b. Install Command View AE and Command View on different systems (co-existing in the same SAN)

CAUTION:

Do not use both Command View and Command View AE to manage the same array(s). This type of management is not supported.

Table 2

Configuration options

Important Functions to you

Command View Path

Connectivity Diagnostics

Command View XP event notification module

Implications

Command View AE provides various host agent functions, but currently there is no plan to provide Path Diagnostic functions

Command View AE 1.0 does not email events. It only listen for array traps and occasionally polls for events

Suitable Configuration Option

Option 2a or 2b

Option 2a or 2b, or stay with

Command View

Command View CLI functions for existing batch script

Command View AE 1.0 CLI has completely different syntax. You may need time to migrate the scripts slowly.

Option 2a or 2b. Option 1 can also be used with the CLI Migration

Tool.

HP StorageWorks Application

Policy Manager XP (APM)

HP StorageWorks Performance

Advisor XP (PA XP)

HP Fast Recovery Solution (FRS) and Microsoft Virtual Disk

Services (VDS).

Integrated with HP Systems

Insight Manager (HP SIM) via

Command View

APM XP requires Command View to function

PA XP can function as a standalone product; however, the Performance

Estimator Tool requires Command View

FRS and VDS requires Command View to function

Integrated with HP OpenView

Storage Area Manager via

Command View

Option 2a or 2b

Option 1, 2a, or 2b

Option 2a or 2b, or stay with

Command View

Command View AE 1.0 will not be able to provide events for HP SIM until a future

Command View AE release. It is recommended that you keep Command

View until Command View AE fully integrates with HP SIM.

Command View AE 1.0 does not integrate with Storage Area Manager. It is recommended that you wait for versions of

Storage Area Manager that support

Command View AE.

Option 2a or 2b, or stay with

Command View until Command

View AE fully supports the integration

Option 2a or 2b, or stay with

Command View until Command

View AE fully supports the integration

12 Migration

Table 2

Configuration options

Integrated with Storage

Essentials Enterprise Edition

(SEEE) via Command View

Integrated with other third-party application via Command View using SMI-S (for example,

CreekPath’s Storage Operations

Management Suite)

Integrated with other third-party application via Command View using SNMP, Storage Essentials

Enterprise Integration (HP

OpenView Network Node

Manager)

When HP Storage Essentials Enterprise

Edition integrates with Command View AE

1.0, Storage Essentials provides additional features like events, disk drive mapping and the ability to configure the disk arrays.

Command View AE 1.0 may not be able to integrate with other third-party application.

Please refer to the third-party support documentation for details.

Command View AE does not provide

SNMP Trap forwarding with other applications.

Option 2a or 2b

Option 2a or 2b, or stay with

Command View unless the integration is supported by the third-party application.

Option 2a and 2b at least for initial stage.

Comparing Command View AE and Command View

To help you make an informed choice when planning your storage environment, the following table compares Command View AE and Command View. Information about Remote Web Console begins on

page 15.

Table 3

Comparison of Command View AE and Command View

Feature

Path Connectivity

Array Management

Multi-array Management

Reporting

Management of External Storage

Management of Business

Copy/Continuous Access Pairs

Command View AE Command View

Limited availability. See ” Path

Connectivity-related migrations” on page 28

for additional information.

Multiple wizards assist LUN allocation and Business

Copy/Continuous Access pair creation. More intuitive operation for the storage administrator. Greatly reduces chances of errors in creating host-based files.

Provides dynamic path failure sensing

No wizards; must use a manual creation process

Saves time. The Command View AE database consolidates all managed array configurations and presents a host-based view with management of storage across all arrays.

Provides a host-based view that is for monitoring only

Command View can manage more than one array at a time through both the CLI and GUI.

Extensive reporting. GUI and CLI provide comprehensive reports in

HTML and CSV formats (for example, physical, logical view of array, array utilization by host, by logical group

(business segments).

Limited reporting

Saves time. Create and allocate

LUNs on external storage with the same windows as internal storage.

Wizard-based creation of Business

Copy/Continuous Access pairs in addition to status reporting.

Available from Web console only; manages internal and external storage separately

Must use Raid Manager on host to create HORCM files

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

13

Table 3

Comparison of Command View AE and Command View (continued)

Feature

SMI-S and XML API support

Management Server support with

MSCS

User Administration

Value-Added Plug-Ins

Command View AE

Full support of SMI-S V1.0 as well as future SMI-S versions. Also offers richer integration through XML.

Command View

Supports only SMI-S V1.0; will

not

roll to newer versions of SMI-S as they become available.

Eliminates the management server as a single point of failure. Command

View AE can failover to another server to minimize management downtime.

Not available

Granularity on a logical grouping basis goes across arrays in a SAN or within a single array; tied more closely to business needs.

Granularity on a per-array or partition basis only

The second release will support

Replication Manager, Provisioning

Manager, and Tiered Storage

Manager.

No major feature enhancements are planned

Command View AE plug-ins are not supported

Supports active provisioning.

No active provisioning Integration with HP Storage

Essentials Enterprise Edition

Host Agent HBA support Supports any HBA that qualifies for the XP hardware and has a connection to the managed array.

Supports Path Connectivity qualified

HBA only

14 Migration

HP StorageWorks XP Remote Web Console

Remote Web Console is virtually identical to the Command View array-management GUI for the

XP128/XP1024/XP12000/XP10000 arrays.

Previously, this GUI content was embedded within Command View to give the appearance of a single server. Starting with Command View 2.0, the GUI could be launched directly from the SVP but was not considered a standalone product.

Remote Web Console is now available as a standalone application, and provides several new features

(” New Remote Web Console features ” on page 16) and new options (” Remote Web Console options ” on page 16).

Figure 1

HP StorageWorks XP Remote Web Console

You can migrate to using Remote Web Console as a fully functional, standalone product or in conjunction with Command View or Command View AE. The migration procedures help you configure Remote Web

Console and Command View for features that are available in both applications (see ” Migration planning ” on page 12).

Remote Web Console is delivered with the array firmware. You must have the appropriate firmware version for the enhanced version of Remote Web Console. See the readme for either Command View or

Command View AE for the firmware version that supports Remote Web Console.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

15

Remote Web Console environments

Table 4

shows the different environments that are available for Remote Web Console.

Table 4

Remote Web Console Environments

Remote Web Console

Environment

Description

Standalone

Integrated with Command View

Remote Web Console includes all of the standard array-management functions of Command View, including the ability to manage firmware licenses, user administration, and user partition assignments.

All Command View 2.

x versions work with Remote Web Console (see

page 23 for a discussion of restrictions). Remote Web Console can be

launched directly from Command View or used as a standalone product.

Integrated with Command View AE Remote Web Console includes all standard “array management” functions of Command View AE, including the ability to manage firmware licenses, user administration, and for the XP12000, user partition assignments. It can be launched as a standalone product, or it can be launched from Command

View AE for the XP10000/XP12000.

New Remote Web Console features

Remote Web Console offers new features:

Firmware licensing

User administration

Partition administration (XP12000/XP10000 only)

To access Remote Web Console, launch your browser and type the SVP IP address as the URL.

To access the firmware license feature, click Install in the left pane of Remote Web Console window.

License Key is the default pane.

To access the user administration feature, click the Option icon in the upper right side of the Remote Web

Console window. The User Entry tab is the default pane.

See the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128 for additional information.

Remote Web Console options

Remote Web Console provides some options that differ from the Command View portfolio:

The array-management GUI session timeout is now controlled from Remote Web Console

Remote Web Console provides additional administrative capabilities

No management server is required for Remote Web Console

User Administration

The user administration feature of Remote Web Console overlaps with that of Command View. If you use

Command View to manage an array, only perform user administration for that array in Command View.

Each application has a separate user database. Before Command View AE was released, Command View was the central manager for both Command View and the managed arrays.

Users that were created in Command View also appear in the Remote Web Console database, although the permissions allowed in Remote Web Console are slightly different. To map Remote Web Console users and permissions for each Command View user type, see

Table 6 and Table 7 for the XP12000/XP10000

and see

Table 8

and

Table 9

for the XP1024/XP128.

Table 5

provides a list of the permissions belonging to each user group. (User partition assignments are for

XP12000/XP10000 only.)

16 Migration

User group permissions and mapping

Table 5

Command VIew user groups permissions

User Group

Administrators

StorageAdmins

Users

Permissions

Modify all managed arrays

Administer partitions

Administer Command View framework

Create other users

Read and modify privileges for assigned arrays/partitions only

Read-only privileges for assigned arrays/partitions

XP10000/XP12000

Table 6

Remote Web Console mapping to Command View users (XP10000/XP12000)

User Group

Storage Administrator with superuser permissions (create users and administer partitions)

Permissions

Modify entire array configuration

Administer partitions and users

Download/restore administrative backup lists

Configure Remote Web Console settings (for example, client timeout values)

Modify entire array configuration

Command View User Group

Administrators

StorageAdmins Storage Administrator with general permissions

Storage Partition Administrator with super-user permissions

Not applicable (new capability in

Remote Web Console)

Storage Partition Administrator with general permissions

Access assigned partitions only

Modify partition configuration

Create and manage other users for assigned partitions only

Access assigned partitions only

Manage assigned partitions

Users

NOTE:

The Command VIew

Users group is mapped to the

Remote Web Console users group with modify permissions disabled.

Table 7

Remote Web Console and Command View default users (XP10000/XP12000)

User Group Command View and Remote Web Console

Storage Administrator with super-user permissions

Storage Administrator with general permissions administrator/administrator

None

Storage Partition Administrator with super user permissions

None

Storage Partition Administrator with general permissions user/user

NOTE:

The default, “user,” has modify permissions disabled by default.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

17

XP1024/XP128

Table 8

Remote Web Console mapping to Command View users (XP1024/XP128)

User Group

Administrator

User

Permissions

Modify entire array configuration

Administer users

Download/restore administrative backup lists

Configure Remote Web Console settings (for example, client timeout values)

Download operation and access logs

Command View User Group

Administrators

Access restricted to features assigned by Administrator

Access to entire array, depending on availability, when permission is given

Users

NOTE:

The Command VIew

Users group is mapped to the

Remote Web Console users group with modify permissions disabled.

Table 9

Remote Web Console and Command View default users (XP1024/XP128)

User Group

Administrator

User

Command View and Remote Web Console

administrator/administrator user/user

NOTE:

The default, “user,” has modify permissions disabled by default.

When you create accounts in Command View, Command View creates “parallel" users in Remote Web

Console. Even if you stop managing an array from a Command View management server or uninstall

Command View, user accounts in Remote Web Console will remain intact.

If an array is added to a new Command View management server, then Command View will delete all non-default users from Remote Web Console and change the default user passwords to match those in

Command View.

NOTE:

All arrays that Command View manages have users created in their respective Remote Web

Consoles, and each user account in each managed array (for example, user 1 in array A) has the same password (as defined for that user in Command View). Modify these passwords as needed to meet your security needs.

Using Remote Web Console without updated firmware

Remote Web Console was previously delivered as an array-management GUI that required Command

View 2.x to enable full management capabilities; it is now a fully functional, stand-alone array-management option.

If you prefer not to upgrade to the standalone Remote Web Console and you want to use the array-management GUI (available in firmware dated before August 2005), note that the following features will

not be available:

18 Migration

Firmware license key administration

User security administration

Partition user access administration

IMPORTANT:

Use Command View to perform these operations if you do not upgrade to the standalone

Remote Web Console, and then disable Command View and use the console to manage your array(s).

Accessing Remote Web Console

To access Remote Web Console, launch your browser and type the SVP IP address as the URL.

User sessions: Logging in

The same user (ID) in Remote Web Console may not have multiple concurrent sessions with the same SVP

(web server).

Multiple Remote Web Console sessions are allowed to the same array when those sessions are launched from Command View. Multiple login sessions are also allowed in Command View AE. For more information, see the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128.

Other comparisons between Remote Web Console and the Command View portfolio

Session termination is not supported in the Command View AE environment

The array-management GUI session timeout is now controlled from Remote Web Console

Remote Web Console offers additional administrative capabilities for XP12000/XP10000 management, such as the following:

• Downloading the Audit Log File (storage administrator only)

• Editing the user account list (storage administrator with superuser authority and storage partition administrator with superuser authority only)

• Setting Remote Web Console environment parameters (storage administrator with superuser authority only)

No management server is needed for Remote Web Console

No context-sensitive help is available in Remote Web Console unless it is launched from Command

View or Command View AE. However, a link is provided to the

HP StorageWorks XP Software

Documentation Table of Contents, providing Remote Web Console user guides and firmware-enabled software user guides.

For setup requirements for Remote Web Console, see the

HP StorageWorks Remote Web Console User

Guide for the XP12000/XP10000 or the HP StorageWorks Remote Web Console User Guide for the

XP1024/XP128.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

19

Installation scenarios

Several different scenarios are available for coexistence and migration. Use Table 10 to determine the

appropriate migration procedures for your particular storage environment. The five scenarios use

Command View AE, Remote Web Console, and Command View in various arrangements. To implement a

scenario, see ” Migration procedures ” on page 22.

Table 10

Installation scenarios

Scenario

1

2

3

Migrate to

Command View

AE with Remote

Web Console

Migrate to the standalone

Remote Web

Console

Environment

This environment offers array management through Command View

AE and Remote Web

Console.

This environment offers array management only through Remote Web

Console. Neither

Command View nor

Command View AE is present.

Impact Benefits

Some level of migration is required if you are currently using Command

View.

You lose some features from

Command View, such as Path

Connectivity and event notification.

Loss of XP event notification via SNMP traps.

You lose many Command View features, such as CLI, SMI-S, and detailed SNMP event notification.

You have no access to Command

View AE features and future enhancements.

You need to migrate the GUI for later firmware versions, regardless of your management tool.

Loss of XP event notification via SNMP traps.

Complete functionality

Ease-of-use benefits

Enhanced CLI and API support

Application

Integration support

Future plug-in support

All Remote Web

Console benefits apply

Integrates with other applications:

• SMI-S

• Proprietary API

Easy migration for array-management

GUI

All existing Command

View array management GUI functionality is available.

Migrate from

Command View only to Remote

Web Console with

Command View

The arrays that Command

View managed can now also be managed with

Remote Web Console.

Command View AE is not present.

Firmware license, user administration, and user partition administration features of Remote Web Console overlap features of Command View.

The Command View user database can become corrupted if you use

Remote Web Console when

Command View is managing the array. Perform user administration in

Command View.

You can manage firmware licenses from both Remote Web Console and

Command View.

Minimal migration is needed

Legacy CLI and API support

New firmware-based features are automatically supported in the GUI.

20 Migration

Table 10

Installation scenarios (continued)

Scenario

4

Install Command

View and

Command View

AE on the same management server

5

Install Command

View and

Command View

AE on separate management servers

Environment

Command View and

Command View AE are co-installed on the same management server.

Some arrays are managed with Command View, and others are managed with

Command View AE. No array should be managed by both Command View and Command View AE at the same time.

Remote Web Console is present in Command View

AE. Its presence in

Command View depends on the firmware version.

Command View and

Command View AE are installed on separate management servers.

The array is managed by either Command View or

Command View AE (not both at the same time).

Remote Web Console is present in Command View

AE. Its presence in

Command View depends on the firmware version.

Impact

SMI-S uses the same port for both

Command View and Command View

AE. For simplicity, only one SMI-S component should be running on the same server. Both Command View and Command View AE SMI-S are disabled by default after the installation.

Both Command View and Command

View AE use port 162 for SNMP Trap listening. Both applications cannot listen for traps at the same time. If

SNMP Trap listening is disabled in

Command View AE, the arrays cannot notify Command View AE when an event occurs. However, the Alert feature of Command View AE will continue to regularly poll the arrays for events.

See the

HP StorageWorks Command

View XP Advanced Edition Device

Manager Server Installation and

Configuration Guide on the documentation CD for the minimum system requirement and the supported browser and JRE version.

Benefits

You can consider having both Command View and

Command View AE if you prefer using Command

View to manage existing arrays while transitioning to Command View AE to manage newly purchased arrays.

Ability for both applications to receive SNMP traps for XP arrays.

If you do not have a very powerful management server and you are concerned with the limitation associated with installing both

Command View and

Command View AE on the same server, you can choose to install the two applications on separate servers.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

21

Migration procedures

Use the following procedures to migrate to Command View AE and Remote Web Console environments in

various arrangements. See ” Migration planning ” on page 12 to select your preferred scenario.

Scenario 1: Migrate to Command View AE with Remote Web Console

This migration involves transitioning array management from Command View to Command View AE with

Remote Web Console. This is the preferred option for complete functionality.

Environment

This environment offers array management with Command View AE and Remote Web Console.

Requirement(s)

Upgrade to firmware that supports the standalone Remote Web Console for

XP12000/XP10000/XP1024/XP128

Install Command View AE. See the basic installation requirements in the

HP StorageWorks Command

View XP Advanced Edition Device Manager Server Installation and Configuration Guide.

You might require the XP512/XP48 Remote Control for access to provisioning features in Command

View XP (for example, LUN management, LUN security, LUSE, and CVS), although Command View AE also supports those features. Use Remote Web Console with Command View to manage Auto LUN,

Cache LUN, BC/CA, and other low-usage, complex features on the XP512/XP48.

Purchase a Command View AE capacity license for existing arrays

Use Remote Web Console for optional low-level configuration management for arrays

Migrate existing CLI scripts (see ” CLI migration ” on page 31)

Manage licensing through Remote Web Console

Procedure

Uninstall Command View before installing Command View AE or Remote Web Console. To uninstall

Command View, follow the instructions in the

HP StorageWorks Command View XP Installation Guide.

Accessing new features after migration

To access Remote Web Console, launch your browser and type the SVP IP address as the URL.

NOTE:

See the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128 for additional information.

To access Command View AE, launch your browser and type the following:

< http or https>://<DNS name or IP address of management server>:<install

port> (default is 23015)/DeviceManager/Login.

For example, http://12.12.12.12:23015/DeviceManager/Login

To access the firmware license feature, click Install in the left pane of the Remote Web Console window.

License Key is the default pane.

To access the user administration feature, click the Option icon in the upper right side of the Remote

Web Console window. The User Entry tab is the default pane.

NOTE:

For information about integrating with other applications, see ” Application-related migrations ” on page 28.

Scenario 2: Migrate to standalone Remote Web Console

This migration involves transitioning array management from Command View to the standalone Remote

Web Console.

22 Migration

Environment

This environment offers array management from Remote Web Console. Neither Command View or

Command View AE is present.

NOTE:

Install Command View AE if you want to manage your arrays with both Command View AE and

Remote Web Console.

Requirement(s)

Upgrade to firmware that supports Remote Web Console for XP10000/XP12000/XP1024/XP128.

CAUTION:

Firmware license, user administration, and user partition administration features of Remote

Web Console overlap with features of Command View. Perform user administration in Command View

rather than in Remote Web Console. See User Administration , page 16, for information about performing

user administration tasks in Command View.

NOTE:

For information about integrating with other applications, see ” Application-related migrations ” on page 28.

Procedure

All users will need to consider re-working their user accounts in Remote Web Console to meet their needs.

Accessing new features after migration:

To access Remote Web Console, launch your browser and type the SVP IP address as the URL.

To access the firmware license feature, click Install in the left pane of the Remote Web Console window.

License Key is the default pane.

To access the user administration feature, click the Option icon in the upper right side of the Remote

Web Console window. The User Entry tab is the default pane.

NOTE:

See the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128 for additional information.

NOTE:

Although Command View AE cannot manage users who access the array through Remote Web

Console, Command View AE does provide its own user database and associated administrative tools.

Scenario 3: Migrate from Command View to Remote Web Console with Command

View

This migration involves transitioning from using Command View with older firmware to using Command

View with firmware that supports Remote Web Console. If you are running Command View with older firmware, then you already have the array-management GUI, which is similar to Remote Web Console.

However, Remote Web Console provides additional functionality.

NOTE:

This migration occurs automatically if you are using Command View and you upgrade to firmware that supports the standalone Remote Web Console.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

23

Environment

Command View AE is not present in this environment. Arrays that Command View managed are now managed in both Command View and Remote Web Console.

Requirement(s)

This transition requires Command View 2.

x.

Upgrade to firmware that supports standalone Remote Web Console for

XP10000/XP12000/XP1024/XP128.

CAUTION:

Firmware license, user administration, and user partition administration features of Remote

Web Console overlap with features of Command View.

Perform user administration in Command View rather than in Remote Web Console

.

See User Administration , page 16, for information about performing user

administration tasks in Command View.

Perform user administration in Command View. The Command View user database can become corrupted if you make changes through Remote Web Console when Command View is managing the array.

You can manage firmware licenses from both Remote Web Console and Command View.

Procedure

No procedures are required for firmware licensing or user partition administration. See ” User

Administration ” on page 16.

Accessing new features after migration

To access Command View, start the browser and enter the Command View management station’s host name or IP address as the URL.

or

Point your browser directly at the array public IP address (for example, http://123.45.67.890).

To access Remote Web Console, either launch from Command View or launch directly typing the SVP

IP address as the URL.

NOTE:

See the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128 for additional information.

To access the firmware license feature, click Install in the left pane of the Remote Web Console window.

License Key is the default pane.

To access the user administration feature, click the Option icon in the upper right side of the Remote

Web Console window. The User Entry tab is the default pane.

Negating migration changes

Downgrade to a firmware version that does not support the standalone Remote Web Console.

NOTE:

For information about integrating with other applications, see ” Application-related migrations ” on page 28.

Scenario 4: Command View AE and Command View installed on the same management server

This migration is necessary if you want to manage your arrays with both Command View AE and

Command View.

24 Migration

Environment

Command View and Command View AE are co-installed on the same management server. Some arrays are managed with Command View, and others are managed with Command View AE. No array can be managed by both Command View and Command View AE at the same time.

CAUTION:

Do not use both Command View and Command View AE to manage the same array(s). This type of management is not supported.

Requirements

Command View AE can be co-installed with either Command View 2.0 or 2.1. It is recommended that you meet the following minimum requirements:

• 3 GHz Pentium 4

• 2 Gb memory

• 6 Gb available hard disk space

NOTE:

Command View with PA supports a single processor only.

Make sure that your system meets all other minimum system requirements and uses supported browser and JRE versions, as defined in the installation guide and readme.txt for Command View and

Command View AE. Also, see

Table 11 for supported application environments.

The array must be managed by either Command View or Command View AE, but not both at the same time.

Both Command View and Command View AE have an SMI-S provider, and both providers use the same communication port. As a result, you can use only one of the SMI-S providers on the same server.

If you have Command View and PA XP 2.0/2.1 in the environment, you should upgrade the client environment to JRE 1.4.2_06 for Command View AE, Command View, and PA web client and CLI client to co-exist. You may need to clear your Java Plug-in applet cache before launching the Command

View or PA GUI. To do so, follow these instructions:

1.

Go to Control Panel > Java Plug-in > Cache and click Clear.

2.

Go to Control Panel > Java Plug-in > Browser and select Microsoft Internet Explorer.

3.

Restart the browser and launch the GUI.

Co-installing the Command View and Command View AE host agent on the same server is supported.

You can consider having both Command View and Command View AE if you prefer using Command

View to manage existing arrays while transitioning to Command View AE to manage newly purchased arrays.

The following applications can coexist in the same SAN or be installed on the same system.

Table 11

Application environments

Environment

Management Server

(Co-installed on same system or co-existing on the same SAN)

Application 1

Command View

2.0

Command View

2.1

Application 2

Performance

Advisor 2.0

Performance

Advisor 2.1

Application 3

Application Policy

Manager 3.0E

Application Policy

Manager 3.0F

Application 4

Command View

AE 1.0

Command View

AE 1.0

Host Agent

(co-installed on the same system or co-existing on the same SAN)

Command View

2.0

Command View

2.1

Performance

Advisor 2.0

Performance

Advisor 2.1

Application Policy

Manager 3.0E

Application Policy

Manager 3.0F

Command View

AE 1.0

Command View

AE 1.0

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

25

Procedure

1.

Use the procedures in the installation guides for Command View AE and Command View to install the applications.

2.

Set up the supported CLI client and Web client environments as described in the

HP StorageWorks

Command View XP AE Device Manager Command Line Interface Application User Guide and HP

StorageWorks Command View XP AE Manager Web Client User Guide, respectively.

NOTE:

Use Command View and Command View AE to manage a disjointed set of arrays. For example, use Command View to manage arrays A, B, and C, and use Command View AE to manage arrays D and E.

Confirm migration

Confirm that Command View services are started in the management server.

Confirm that Command View AE services are started on the server.

Confirm that the server can collect data from the host agents.

Accessing new features after migration

To access Command View AE, launch your browser and type the following:

< http or https>://<DNS name or IP address of management server>:<install

port> (default is 23015)/DeviceManager/Login.

For example, http://12.12.12.12:23015/DeviceManager/Login

To access Command View, point your browser directly at the array public IP address (for example, http://123.45.67.890).

Negating migration changes

Uninstall all of the applications to back out of the migration changes. Follow the uninstall instructions in the installation guides for Command View, Performance Advisor, Application Policy Manager, and Command

View AE.

NOTE:

For information about integrating with other applications, see ” Application-related migrations ” on page 28

Scenario 5: Command View AE and Command View installed on different management servers

Environment

Command View AE and Command View are installed on different management servers. Some arrays are managed with Command View, and others are managed with Command View AE. No array can be managed by both Command View and Command View AE at the same time.

NOTE:

Do not use both Command View and Command View AE to manage the same array(s). This type of management is not supported.

Requirement(s)

The management servers must meet the requirements of both Command View and

Command View AE. See

Table 11

.

Command View and Command View AE must reside on separate, supported servers.

Remote Web Console clients must meet the requirements for both Command View and Command View

AE.

26 Migration

Procedure

1.

Use the procedures in the installation guides for Command View AE and Command View to install the applications.

2.

Set up the supported CLI client and Web client environments as described in the

HP StorageWorks

Command View XP AE Device Manager Command Line Interface Application User Guide and HP

StorageWorks Command View XP AE Manager Web Client User Guide, respectively.

Confirm migration

Confirm that Command View services are started in the management server.

Confirm that Command View AE services are started on the server.

Confirm that the server can collect data from the host agents.

CLI Client Migration

Procedure

1.

Use the link on the Command View AE GUI on the Device Manager pane to download the CLI client and required JRE.

2.

Set up the supported CLI client as described in the

HP StorageWorks Command View XP AE Device

Manager Command Line Interface Application User Guide.

3.

If you have Command View and Performance Advisor XP (versions 2.0 or 2.1) in the environment and you would like to use the Command View and Performance Advisor XP CLI clients with the Command

View AE client, please upgrade the client environment to JRE 1.4.2_06 for the clients to co-exist on same system.

Accessing new feature after migration

Start the Command View AE CLI client.

Confirm migration

Confirm that the CLI client comes up and can communicate to the server.

Negating migration changes

Uninstall all of the applications to back out of the migration changes. Follow the uninstall instructions in the installation guides for Command View, Performance Advisor, Application Policy Manager, and Command

View AE.

NOTE:

For information about integrating with other applications, see ” Application-related migrations ” on page 28.

Command View CLI migration

CLI migrations currently consist of an automated CLI migration tool and a command mapping/cross

reference table. See ” CLI migration ” on page 31 for CLI-related migration procedures.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

27

Application-related migrations

This section provides information about the following topics:

Supported migration applications

How Command View AE affects applications that integrate with Command View

Alternative migrations

Supported migration applications

Use Table 12

to determine the specific versions of software applications that are supported for migration with Command View AE.

NOTE:

If certain combinations of two products are not supported, then migrations also will not support that combination.

Table 12

Applications supported for integration

Application

System Insight Manager

(SIM)

Supported release Comments

5.0

NOTE:

System

Insight Manager may not fully integrate with Command View

AE, please refer to the SIM support documentation for latest information.

Because the first release of Command View AE does not provide

SMI-S alert indication, you cannot get SMI-S events from System

Insight Manager. It is recommended that you maintain your existing integration setup until Command View AE develops a release that integrates fully with SIM.

HP Storage Essentials

Enterprise Edition (SEEE)

Other HP and third-party applications

See the

HP Storage Essentials Integration Guide at http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentTy

pe=SupportManual&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=1

2169&prodSeriesId=463512 for integration information

Not applicable For support information, see the documentation for the application that you want to integrate.

Fast Recovery Solution (FRS)

Command View must remain in the environment, because the Command View AE server does not support

FRS. Continue to run HP FRS, which uses HP VDS.

Standalone Hitachi software

You do not need to migrate standalone Hitachi software products that Command View does not support if your environment includes both Command View and Command View AE. Examples of such Hitachi software products include Hitachi NAS/Management, HMBR, Data Integrity Check, and HDLM.

OpenView Storage Area Manager (Storage Area Manager)

Command View AE 1.0 does not integrate with Storage Area Manager. It is recommended that you wait for versions of Storage Area Manager that support Command View AE.

Path Connectivity-related migrations

Some of the features in Path Connectivity are not supported in Command View AE. You can either continue to use Command View and Path Connectivity for that functionality, or you can transition to Command View

AE and use other applications for the path-connectivity functionality.

28 Migration

Command View includes the Path Connectivity module, which provides host view and connectivity path information using host agents. Command View AE also provides host agents to collect some host information.

HP Systems Insight Manager and HP Storage Essentials Enterprise Edition are products that provide functionality that is similar to Path Connectivity. While Path Connectivity only supports the XP arrays, SIM supports a heterogeneous environment, which means that you can use a single set of collaborated tools to manage storage devices from a variety of vendors.

Major Path Connectivity features not found in Command View AE

Connectivity Health, Path Diagnostic screen

• Switch health information

• Ping the path

No Host Device file information

• Command View AE Provisioning Manager and other plug-ins provide more host view information.

(Future plug-in offerings will provide greater granularity of device file information.)

Array Security Overview (shows an array view of host and host group that can access each port)

• Recommendation: Use the XP Remote Web Console

Command View AE host: additional features

Provides a GUI interface for HORCM file creation

Offers some Copy Pair management

Provides less-restrictive HBA support

Command View AE can generate .HTML or .CSV files from the host utilization report.

Even if no host agent is installed, some host WWN information is available in the GUI.

Replacing missing features after migration to Command View AE

Path Connectivity users have two options:

1.

Use Command View XP and Path Connectivity during the supported time frame

2.

Migrate to Command View AE and consider using other plug-ins or tools to gain additional host and connectivity information. (If you are planning to have Command View AE and Command View in the

same environment, See Table 10 on page 20.)

HP System Insight Manager 5.

x

System Insight Manager may not fully integrate with Command View AE, please refer to the SIM support documentation for latest information.

HP Storage Essentials Enterprise Edition

If you are currently using Command View to integrate with HP Storage Essentials Enterprise Edition (SEEE), it is recommend that you migrate to Command View AE. This integration provides greater array-management functionality, such as actively creating LUNs, masking LUN security, and creating LUSE.

For addition information, see the HP Storage Essentials Enterprise Edition manuals at http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManua l&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=12169&prodSeriesId=463512

Performance Advisor (PA) and Application Policy Manager (APM)

HP StorageWorks Performance Advisor XP (PA) can run as a standalone product. However, the

Performance Estimator Tool (PET), which is distributed with PA, depends on the Command View API to provide certain information. The PET tool will not function with Command View AE. 1.0

HP StorageWorks Application Policy Manager (APM) requires Command View and Command View Path

Connectivity host agents. Although APM will not integrate with Command View AE, similar functionality is available in HP StorageWorks Performance Control XP.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

29

See Table 11

for a description of how these applications can co-exist in the same SAN or be installed on the same system as Command View AE or Command View.

Impact of this migration

• You retain all of the PA application data from this migration after uninstalling Command View.

• The PA performance estimator tool will not work unless Command View is installed.

• The APM will not function without Command View.

CAUTION:

Do not uninstall Command View if APM is used. APM requires both Command View and the

Command View host agent.

Requirements

PA can run as a standalone product. See the

HP StorageWorks Performance Advisor XP Installation Guide on the product CD for details.

Procedure

You can co-install PA, Command View, and Command View AE on the same server.

Confirm migration

To confirm migration, run the application by launching it directly from the Web GUI.

Negating migration changes

Reinstall Command View on the server with PA, APM, or both.

Third-party products

Currently, other third-party vendors such as Veritas or Creekpath have integrated with Command View by way of the SMI-S component in Command View. However, these third-party products currently might not support integration with Command View AE. For additional information, see the support documents for the third-party products.

Miscellaneous migration information

Command View license entitlement migration

No tools or processes are provided for migrating Command View licenses to Command View AE. Account teams will determine Command View AE entitlements and provide customers with the necessary keys to be installed in Command View AE. See the

HP StorageWorks Command View XP Advanced Edition Device

Manager Server Installation and Configuration Guide for license key installation instructions.

The licensed produces that you have in your environment do not require migration and are not affected by migration to Command View AE. For example, for the LUN Configuration Manager firmware license, no change is required to use Remote Web Console or Command View AE.

Migration of audit logs

Audit logs in the Command View AE time frame are consolidated in the array and accessible from Remote

Web Console. The way logs are obtained or analyzed does not change with the addition of Command

View AE; Command View AE simply adds new entries to the existing logs. All Command View AE users’ actions appear in the access and operation logs with the account name that Command View AE requested when the array subsystem was added (for example, "administrator").

See the

HP StorageWorks XP Remote Web Console User Guide for the XP12000/XP10000 for more about the Command View AE entries in the audit log.

30 Migration

2 CLI migration

NOTE:

These reference names are used throughout this user guide:

• HP StorageWorks Command View XP, Version 2.

x, is called Command View

• HP StorageWorks Command View XP Advanced Edition is called Command View AE

• HP StorageWorks XP Remote Web Console is called Remote Web Console

CLI migration overview

Command Line Interface (CLI) migration changes Command View CLI commands to equivalent Command

View AE CLI Commands. Migration includes the following tasks:

Automated Command View CLI migration process

Data collection process

Manual Command View CLI migration process

The Command View AE CLI has different syntax, output format, and interactive behavior from the

Command View CLI. Because existing Command View CLI scripts will not work directly with the Command

View AE CLI, migration is required.

Many features of the Command View AE CLI are similar to the Command View CLI, such as volume management, LUN configuration, LUN security, LUSE, and CVS. In addition, the Command View AE CLI supports Business Copy and Continuous Access. The Command View AE CLI is also generally easier to use with traditional UNIX

®

-style scripting tools.

One key difference between the Command View and Command View AE CLIs is that the Command View

AE CLI currently cannot combine multiple operations into a single “config change request” to the arrays.

Essentially, Command View AE scales as a linear function of requests. (Scaling is linear because commands to the Command View AE CLI are processed one at a time.) On the other hand, scalability for

Command View is achieved by combining similar commands internally within the Command View server.

Command View’s response time can be similar for single or multi-command batch requests.

The CLI migration procedure involves migrating scripts and Command View CLI command/batch files by using the automated CLI translation tool and a command mapping table (

Table 14

).

CLI Migration Tool overview

If you are currently using automated scripts to make configuration changes on your XP array(s), then the

Command View CLI scripts will need rework. The CLI Migration Tool automatically converts the Command

View CLI commands in the command file to equivalent Command View AE CLI commands. See Manual

CLI command mapping on page 38 if manual command mapping is needed.

CLI Migration Tool requirements

The CLI Migration Tool is supported for CLI command files from Command View 2.0 or later. It supports the following arrays: XP512/XP48/XP128/XP1024/XP12000/XP10000.

CLI Migration Tool limitations

The migration tool can automatically migrate most Command View CLI Batch files. However, the tool will not support migration of any other script types, such as K shell.

Supported target environments

The CLI Migration Tool runs on all platforms where the Command View and Command View AE CLI are supported:

HP-UX

Windows

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

31

Supported commands

The CLI Migration Tool supports the following features:

LUN Management

Volume Management (LUSE, CVS)

LUN Security

Translating batch files

The CLI Migration Tool provides a way for you to automatically translate batch files that contain Command

View CLI commands to Command View AE CLI commands. The commands are processed in two steps:

1.

Command translation: Translates the CV CLI commands to equivalent Command View AE CLI commands

2.

Data translation: Translates the data portions (input parameters) to Command View AE CLI command parameters

Command View CLI command parameters or data portions need to be translated because the Command

View CLI and Command View AE CLI are different.

This is an example of a Command View CLI command: create lun 1A, 16dec1, 9, 3, 48 where create lun is the command portion, and the arguments 1A, 16dec1, 9, 3, 48 are the data portion for the migration tool.

The CLI Migration Tool execution status appears on the console.

See Error codes on page 69 for detailed success/failure messages.

Using the CLI Migration Tool

CLI Migration Tool procedure

Input the batch file that contains only Command View CLI commands for the CLI migration tool (for example, cmt –f < inputFileName > -type <array Type> –slno <arraySerialNo> [-p

<arrayserialNo.properties>])

An error message appears if the CLI Migration Tool identifies any syntax errors.

After the Command View CLI command(s) pass the syntax check, an output file documents the conversion to Command View AE CLI commands. This process of generating the commands automatically is called command translation.

The tool will not convert unsupported or invalid command syntax, which is marked with the following text message:

" ### line##<line number> <inputCommand> <Error code> : Translation not supported for this command. Please refer to command mapping table ### "

" ### line##<line number> <inputCommand> : Invalid command syntax. Please refer to command mapping table ### "

• If you encounter this error message in the output file, manually edit the CLI command using the

command mapping table (see Manual CLI command mapping on page 38).

Because of the differences in the Command View CLI and Command View AE CLI, data translation might create errors marked as (< *** ErrorCode dataportion ***> and

<***errorcode***>) . See

Error codes on page 69 for more details.

If you encounter the error ( <*** ErrorCode dataportion ***>), supply the optional parameter

< arrayserialNo>.properties to the CLI Migration Tool.

Use the CLI Migration Data Collection Tool to generate the property file

<arrayserialNo>.properties. See CLI Migration Data Collection Tool (cmdct) on page 37.

Use the generated command file directly in the Command View AE CLI working environment.

32 CLI migration

NOTE:

The generated command file from the CLI Migration Tool cannot be fed to the Command View AE

CLI with the –i option

See

Sample commands for CLI migration on page 73 for a description of sample commands.

Invoking the CLI Migration Data Collection Tool

Run the CLI Migration Data Collection Tool from a workstation that has access to the array for which the data is being collected. For XP512/XP48 arrays with IP Security enabled, the IP address of the workstation needs to be added to the IPSecurity in the SVP. For the XP128/XP1024/XP12000/XP10000 arrays, the workstation should have access to the SVP, even if a firewall has been set up.

Invoke the CLI Migration Data Collection tool by executing the following command under the migrationtool directory. (The tool takes ArrayIPAddress and ArrayType [integer value] as parameters.) cmdct -ip <ArrayIPAddress> -type <ArrayType>

The tool communicates with the array to collect the data and store it in the output file in a format that the

CLI Migration Tool understands. The output file is created under the working directory of the tool as

<arraySerialNo>.properties.

Invoking the CLI Migration Tool

Translate the commands in the Command View CLI file to equivalent Command View AE CLI commands by invoking the CLI Migration Tool in the command prompt. This tool takes Command View CLI commands file names, array serial number, and ArrayType [integer value] as parameters.

Under the CVCLIMigTool (migrationtool) directory, execute the following command: cmt –f <inputFileName> -slno <arraySerialNo> -type <arrayType> [-p

<arrayserialNo.properties>]

Format of input file

The file must contain only Command View CLI commands. The CLI Migration Tool ( cmt) can take any type of file as an input (for example, *.bat, *.sh,*.txt,*.pl, and others).

NOTE:

The tool does not alter or modify the input data.

Format of property file <arrayserialNo>.properties: optional parameter

The property file contains details such as the HG name to HG ID mapping, and the WWN name to

WWN nickname mapping. These details should be encoded, as shown below. The file name should be the serial number of the array. The file can be generated by using the CLI Migration Data Collection Tool

(cmdct).

The property file contains two sections:

System section (**DO NOT EDIT**): Applicable for all arrays

• The cmdct tool generates this portion and files all of the required fields. This portion should not be edited.

User section (optional): Not applicable for the XP512/XP48 arrays

• This portion is reserved for values that depend on a specific condition. Supply the values if you intend to use the following commands for translation (such as “cmt”).

You will need to edit the "user" section of the .properties file only. Also, you will need to add entries describing any entities that do not exist in the array at the time the migration tool is to be run.

For example, when a script being translated creates a new host group, details of that group will need to be supplied. See

Sample commands for CLI migration on page 73 for additional guidance.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

33

XP128/XP1024/XP12000/XP10000

create HostGroup

NOTE:

The user section is not available for the XP512/XP48. Edit the CLI Migration Tool output file for the following commands.

XP512/XP48

add security to lun add lun_to_lun_group add wwn create lun group delete lun delete lun from lun group delete security from lun modify host mode

34 CLI migration

For example, an XP1024 array type 10033 properties file contains the following data:

# System generated file!.Generated @2005-05-20T12:34:18

# User section.

# User editable portion.

# NOTE- Each name value pair should start in a new line.

hostGroupId=0:1A-G00:0

# System section!.

# User should not edit this section.

# example port_name:HostGrpNickName:HGID:WWN_name:WWN_nickname

#hostGroupId=portId:HostGrpNickName:HGID:WWN_name:WWN_nickname hostGroupId=0:1A-G00:0 hostGroupId=0:CVXP:1 hostGroupId=0:16dec1:2

For example, an XP512 array type 30055 properties file contains the following data:

# System generated file!.Generated @2005-06-01T14:37:45

# User should not edit this.

#Lun=portId:lunId:cuId:ldevId

Lun=0:0:0:5

Lun=0:1:1:3

Lun=0:2:0:204

Lun=0:3:0:9

#Lungroup=port:lungroupname:lunId

Lungroup=0:cvros92:5

Lungroup=0:cvros92:6

Lungroup=0:cvros92:7

Lungroup=0:cvros92:9

Lungroup=0:alpha136:16

#WWNGroup = portId:wwn name : wwn nickname : wwngroupname

WWNGroup=0:12.13.14.15.16.17.18.19:mana

WWNGroup=0:12.34.56.78.93.33.44.44:testing

WWNGroup=0:67.89.00.98.76.52.34.58:mana23

WWNGroup=0:10.00.00.00.c9.32.01.2e:wwnsmis

WWNGroup=0:12.34.56.78.90.12.34.56:nick

WWNGroup=1:20.00.00.e0.69.40.0a.e2:pasun

Format of output file <inputFileName_out.bat> or <inputFileName_out.sh>

The output file is created in the same directory as the input file. The output file name is based on the input file name, with _out appended to that name.Then, depending on your operating system, a .bat or .sh file name suffix is applied.

For example, for Windows, the output file will be 10033_out.bat; for non-Windows, such as HP_UX, it will be 10033_out.sh.

See Sample commands for CLI migration on page 73 for a sample execution of

cmt.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

35

CAUTION:

The array configuration should not be changed through any interface between data collection and the CLI Migration Tool output file submission to Hdvmcli. The collected data collected might be invalid if any configuration changes between data collection and the submission of the CLI Migration Tool output file to Hdvmcli.

Working with the CLI Migration Tool files

Automated installation is not supported for the CLI Migration Tool. Extract a tar file into a specified

directory and then apply the following procedures (” Setting up the CLI Migration Tool ”) before using the

tool.

Table 13

CLI Migration Tool files

File name

cmt.cfg

cmt.cfg

cmt.bat

cmt.sh

cmdct.bat

cmdct.sh

CMT_commands_ legacy.xml

CMT_commands_ nonlegacy.xml cmt.jar

cmdct.jar

Description

Configuration file for the CLI Migration Tool that contain the parameters MAX_LINE,

OS_NAME and TRACE_LEVEL

Configuration file for the CLI Migration Data Collection Tool that contain the parameter

TRACE_LEVEL and TRACE_FILENAME

Batch file to run the CLI Migration Tool in Windows platform

Batch file to run the CLI Migration Tool in non-Windows platform

Batch file to run the CLI Migration Data Collection tool in Windows platform

Batch file to run the CLI Migration Data Collection tool in non-Windows platform

XML file containing Command View CLI commands and equivalent hdvmcli commands for the XP512/XP48 arrays.

XML file containing Command View CLI commands and equivalent hdvmcli commands for XP10000/XP12000/XP128/XP1024 arrays

Jar file containing classes for the CLI Migration Tool

Jar file containing classes for the CLI Migration Data Collection Tool

Setting up the CLI Migration Tool

Follow these instructions to set up the migration tool:

1.

Untar the migrationtool.tar and extract it to a folder (for example, temp).

2.

Change the configurable parameters (if needed) in the cmt.cfg configuration file under

/temp/migrationtool.

Execution of the CLI Migration Tool

1.

Either set the environment variable RUN_DIR to the working directory or allow the tool to set it to the current directory.

2.

Run the cmdct batch file under /temp/migrationtool with the ipaddress of the array and type of array.

NOTE:

The cmdct tool generates the properties file [<array serial number>.properties] and gives it to the cmt tool with the -p option.

Syntax of cmdct:

cmdct -ip <array ip address> -type <array type>

Example:

cmdct -ip 15.43.212.61 -type 1024

36 CLI migration

3.

Run the cmt batch file under /temp/migrationtool with inputcommand filename, serial number of the array, type of array, and the property filename (an optional parameter is the cmdct tool output file).

Syntax of cmt:

cmt -f <input command file> -type <array type>

-slno <array serial number> [-p <properties filename>]

Example:

cmt -f input_lun.txt -type 1024 -slno 10056 -p 10056.properties

Make note of the following issues:

One input command file should contain Command View CLI commands for a single array.

The tool continues to translate subsequent commands in the input file, even if the translation fails for some commands, until it reaches the end of the file or maximum line that the tool supports (this is a configurable value).

The output file is named <inputFileName>_out.bat for Windows operating systems and

< inputFileName>_out.sh for non-Windows operating systems (this is a configurable value).

The output of this tool can be directly executed in the hdvmcli environment.

The tool uses its XML files internally. Do not edit them. The behavior is unpredictable if the files are edited.

Configuration files

The configuration file cmt.cfg is located in /migrationtool contains the following configurable parameters:

The maximum line that the tool can translate in a single invocation

The name of the operating system where the output of this tool will be run

The tracelevel to get debug information for the tool

• Value ranges from 0 to 8, with 0 being the lowest and 8 being the highest tracelevel.

The configuration file cmdct.cfg, which is currently in the /migrationtool directory,contains the following configurable parameters:

The cmdct tool trace file name

The tracelevel to get debug information for the cmdct tool

• Value ranges from 0 to 8, with 0 being the lowest and 8 being the highest tracelevel.

CLI Migration Data Collection Tool (cmdct)

You will occasionally need to collect data from the array SVP. Because of the functional differences between the Command View CLI and Command View AE CLI, the expected input parameters for some commands might vary. For example, the Command View AE CLI expects a particular parameter for

HostGroup ID, but the Command View CLI uses the HostGroup nickname for the same functionality.

The CLI Migration Data Collection Tool accommodates the differences in the parameters between the

Command View CLI and hdvmcli by collecting and translating the data from the array.

The following commands collect data that is needed for the translation:

XP512/XP48:

add security to lun group add wwn to wwn group create wwn group delete wwn delete wwn from wwn group delete security from lun group

XP128/XP1024/XP12000/XP10000:

delete HostGroup

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

37

modify HostGroup create Lun delete Lun modify Host Mode create WWN delete WWN create LUSE <data> –lun <data>

Mapping Command View CLI commands to Command View AE CLI commands

NOTE:

The command options -csv , -sa, -sd, -cmd,-category,-l,-col,|more and /p for the Command View CLI are not supported in the Command View AE CLI and cannot be translated.

See Table 14

if you are manually translating Command View CLI command(s) to equivalent Command

View AE CLI command(s) or if you encounter an error for a valid Command View CLI command during automatic translation.

Table 14

Manual CLI command mapping

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

Command View AE CLI Automatic translation support by the CLI

Migration Tool

LUN/LUSE Management commands

list lun list lun [-port

<portname>] list luse list port list luse

[-cu <cu>] list port list lun

[-port <port…>

-hostGrp

<grp..>] | [-cu

<cu…> -ldev

<ldev…>] list luse [-cu

<cu…> ] [-ldev

<ldev…>] list port

[-hostgrp |

-address

-topology

-security] [

-port

<portname…>]

Hdvmcli

GetStorageArray subtarget=Path

[serialnum=<array serial number> model=<array

type>]

No equivalent command exists in the Command

View AE CLI, but you can get the information you need by using the list ldev equivalent

Command View AE CLI command.

Partially supported.

The CLI Migration Tool does not support

–hostgrp, -port,

-cu and -ldev options for translation.

Not applicable.

Migrate to the list ldev equivalent

Command View AE CLI command.

Hdvmcli

GetStorageArray subtarget=Port

[serialnum=<array serial number> model=<array type> port=<port id>]

Supported.

NOTE:

The output for the Command View AE command contains all port-related data, although you might only need specific data, such as list port

-hostgrp.

38 CLI migration

Table 14

Manual CLI command mapping (continued)

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli

GetStorageArray subtarget=HostStor ageDomain

[serialnum=

<array serial

number> model=<array type> port=<port id> domain=<domain

id>]

Hdvmcli

GetStorageArray subtarget=Port portsubinfo=HostSt orageDomain

[serialnum=

<array serial

number> model=<array type> port=<port id>]

Use this command when using the CLI Migration

Tool to translate.

list cmd_device list ldev list free_ldev list cmd_device list ldev [-cu

<cuNumber>] list free_ldev

[-cu <cuNumber>] refer list ldev

-cmddev list ldev

[-unallocated]

[-emulation

<emulation

type>] [-ldev

<ldev…>] [-cu

<cu…> ] ]

No equivalent command exists in the Command

View AE CLI, but you can get the information you need by using the list ldev equivalent

Command View AE CLI command

Not applicable.

Migrate to the equivalent list ldev

Command View AE CLI command.

Hdvmcli

GetStorageArray subtarget=LogicalU nit [objectID=

<object id of a particular logical unit>serialnum=<ar

ray serial number> model=<array type> lusubinfo=LDev ldevsubinfo=

VolumeConnection lufilter =

<ALL|FREE|ASSIGNED

> lufilterchildid=LD ev]

Partially supported.

The CLI Migration Tool does not support –lu,

-cmddev, and

-emulation options for translation. If the

-cu or –ldev option is used, the CLI Migration

Tool will not perform the migration.

refer list ldev

-unallocated -cu

<cu…>

Hdvmcli

GetStorageArray subtarget=LDEV

[devnum=

<particular ldev

number> serialnum=<array

serial number> model=<array

type>]

Hdvmcli

GetStorageArray subtarget=LogicalU nit lufilter=FREE

[serialnum=<array

serial number> model=<array

type>]

Partially supported. The

CLI Migration Tool does not support the -cu option for migration.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

39

Table 14

Manual CLI command mapping (continued) create lun create host group

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

create lun

[<portname….>],

<scsiId>,

[<lunId>], <cu>,

[<ldev…>] create lun

<portname…>,

<hostgrpnickname

>, <lunid...>,

<cu…>, <ldev…>

A range can be given for either ports or lunids and ldevs, but not both.

Range values have to be specified within square brackets [ ]

Not supported

Specify range values without using square brackets [ ] create host_group

<portname…>,

<hosghrpnickname

.…>

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli AddLUN serialnum=<array

serial number> model=<array type> port=<PortID> lun=<free lun id> devnum=<free ldev id> [scsi=<scsiid> domain=<hoststorag edomain id>]

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

For XP128/XP1024/

XP12000/XP10000 arrays

Hdvmcli AddLUN serialnum=<array

serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id> lun=<free lun id> devnum=<free ldev

id>

[scsi=<scsiid>]

Hdvmcli

AddHostStorageDoma in serialnum=<array

serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id>

[nickname=<host

storage domain

nickname>]

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

40 CLI migration

Table 14

Manual CLI command mapping (continued) expand lun modify command device

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

expand lun

<topCU>,<

topLDev>,

<device ldev>,

<device ldev>,…

-lun

[<portname>],

<scsiId>,

[<lunId>], <cu>,

[<ldev>] create luse

<topCU>,

<topLDev>

-continuous

<offset> |

-disperse

<deviceldevs…>

[-lun <port…>,

<hostgrpnickname

>, < lunid>]

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli AddLUN serialnum=<array serial number> model=<array type> port=<PortID> lun=<free lun id> lusedevnums=<comma separated ldev ids

> [scsi=<scsiid> domain=<hoststorag

edomain id>]

For XP128/XP1024/

XP12000/XP10000 arrays:

Partially Supported. For

XP128/XP1024/

XP12000/XP10000 arrays.

The CLI Migration Tool does not support the

-lun option for multiple

LUN creation for translation.

Hdvmcli AddLUSE serialnum=<array

serial number> model=<array type> devnums=<Comma separated ldev ids>

For XP128/XP1024/

XP12000/XP10000 arrays:

(Expand and also create path to it)

Hdvmcli AddLUN serialnum=<array

serial number> model=<array type> port=<PortID> lun=<free lun id> lusedevnums=<comma separated ldev ids

> domain=<hoststorag

edomain id>

[scsi=<scsiid>] expand lun

<topCU>,<

topLDev>, -limit

<ldevCount> -lun

[<portname>],

<scsiId>,

[<lunId>], <cu>,

[<ldev>]

modify cmd_device

<cu>,< ldev>,

<flag> modify cmd_device -set

<cu…>, <ldev…>

[-security

<switch…>] |

-release <cu..>,

<ldev…>

Hdvmcli

ModifyLogicalUnit serialnum=<array

serial number> model=<array type> devnum=<ldev

number>

[commanddevice=<tr

ue|false> commanddevicesecur ity=<true|false>]

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

41

Table 14

Manual CLI command mapping (continued)

Modify host group

Command View CLI

XP512/XP48

Not supported

Command View CLI

XP128/XP1024/

XP10000/XP12000

modify host_group

<portName>,

<OldHostGrpNickN

ame>,

<NewHostGrpNickN

ame>

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli ModifyPort serialnum=<array serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id> nickname=<host

storage domain

nickname>

Supported modify host mode modify host_mode

<portname>,

<hostmode> modify host_mode

<portName…>,

<HostGrpNickName

>, <HostMode…>

Note that domain id is also required for

XP512/XP48 arrays.

Hdvmcli ModifyPort serialnum=<array serial number> model=<array type> port=<PortID> hostmode=<host

mode value> domain=<hoststorag

edomain id>

Partially supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

NOTE:

For the XP512, the domain has to be specified for modify host mode operations.

You will need to edit the file to pass the domain value. Otherwise, the domain parameter will show

< ***ErrorCode***> in the output file by the

CLI Migration Tool.

modify fibre address modify fibre topology modify fibre_address

<portname>, <

fibreaddress> modify fibre_topology

<portname>, <

fibretopology> modify fibre_address

<portname…>,

<fibreaddress…>

Hdvmcli ModifyPort serialnum=<array

serial number> model=<array type> port=<PortID> fibreaddr=<fibre

address>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

Hdvmcli

ModifyPort serialnum=<array

serial number> model=<array

type> port=<PortID> topology=<topolo

gy value>

Hdvmcli ModifyPort serialnum=<array

serial number> model=<array type> port=<PortID> topology=<topology

value>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

42 CLI migration

Table 14

Manual CLI command mapping (continued) delete lun

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

delete lun

[<portname>],

<scsiId>,

[<lunId>], <cu>,

[<ldev>] delete lun

[<portname…>,

<hostgrpnickname

…>, <lunid…>,

<cu…>, <ldev…>]

| [ -port

<portname…>

-hostgrp

<hostgrp…> | -cu

<cu…> -ldev

<ldev…>]

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli DeleteLUN serialnum=<array

serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id>

devnum=<ldev id>

[deletionoption= lusekeep]

Partially supported. For

XP128/XP1024/

XP12000/XP10000 arrays.

For XP128/XP1024/

XP12000/XP10000 arrays, the CLI

Migration Tool does not support -port,

-hostgrp, -cu and

ldev options for migration.

For XP128/XP1024/

XP12000/XP10000 arrays, the CLI

Migration Tool gives the equivalent Command

View AE CLI command and the option deletionoption=lu sekeep.

NOTE:

For the XP512, the domain has to be specified for modify host mode operations.

You will need to edit the file to pass the domain value. Otherwise, the domain parameter will show

< ***ErrorCode***> in the output file by the

CLI Migration Tool.

Release LUSE Delete Lun releases the luse also.

(If you are deleting the last path to LUSE volume, then delete lun also releases the luse.) delete luse

<topCU…>,

<topLDev…>

Not supported for

XP48/XP512 arrays.

For XP128/XP1024/

XP12000/XP10000 arrays:

Hdvmcli DeleteLUSE serialnum=<array serial number> model=<array type> devnum=<top ldev id>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

43

Table 14

Manual CLI command mapping (continued)

Delete Host

Group

Command View CLI

XP512/XP48

Not supported

Command View CLI

XP128/XP1024/

XP10000/XP12000

delete host_group

<portName…>,

<HostGrpNickName

….>

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli

DeleteHostStorageD omain serialnum=<array

serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

LUN security commands

list lun_security list wwn list lun_group list lun_security

[-port

<portname>] list lun_group

[-port

<portname>

[-group

<groupname>]]

Not supported list wwn [-port

<portname>] list wwn [-port

<portName..>]

[-hostGrp

<HostGrpNickName

…>]

Not supported

For XP512/XP48 arrays

Hdvmcli

Getstoragearray subtarget=path pathsubinfo=<wwn|W

WNgroup>

[serialnum=<array

serial number> model=<array

type>]

Partially supported.

The CLI Migration Tool does not support the

-port option for migration.

Hdvmcli

GetStorageArray subtarget=Port portsubinfo=WWN serialnum=<array

serial number> model=<array type>

[port=<port id>]

Hdvmcli

GetStorageArray subtarget=HostStor ageDomain hsdsubinfo=WWN serialnum=<array

serial number> model=<array type>

[port=<port id> domain=<host

domain id>]

Partially supported.

The CLI Migration Tool does not support the

-hostgrp option without the -port option for migration.

For XP512/XP48 arrays

Hdvmcli

GetStorageArray subtarget=Port portsubinfo=LunGro up serialnum=<array

serial number> model=<array type>

[port=<port id>] lungroupsubinfo=Pa th

Partially supported.

The CLI Migration Tool does not support the

-group option for migration.

44 CLI migration

Table 14

Manual CLI command mapping (continued) list lun_group_ security list wwn_group list security_switch add wwn

Command View CLI

XP512/XP48

list lun_group_securi ty [-port

<portname>

[-group

<groupname>]]

Command View CLI

XP128/XP1024/

XP10000/XP12000

Not supported list wwn_group

[-port

<portname>

[-group

<groupname>]] list security_switch

[-port

<portname>] refer list port

-security add wwn

<portname>,

<wwn>,

<wwnNickname>

[,<wwn>,

<wwnNickname> …]

Not supported create wwn

<portName…>,

<HostGrpNickName

>,

<Wwn~WwnNickName

>

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli

Getstoragearray subtarget=port portsubinfo=LunGro up lungroupsubinfo=Pa th pathsubinfo=WWN|WW

NGroup serialnum=<array

serial number> model=<array type>

[port=<port id>]

Partially supported.

The CLI Migration Tool does not support the

-group option for migration.

For XP512/XP48 arrays

Hdvmcli

GetStorageArray subtarget=Port portsubinfo=WWNGro up serialnum=<array

serial number> model=<array type>

[port=<port id>] wwngroupsubinfo= wwn

Partially supported.

The CLI Migration Tool does not support the

-group option for migration.

No equivalent command exists in the Command

View AE CLI.

Not applicable.

Translate to the equivalent list port

Command View AE CLI command.

For XP512/XP48 arrays Supported.

Hdvmcli

AddHostStorageDoma in serialnum=<array

serial number> model=<array type> port=<PortID> domain=<hoststorag

edomain id> and

Hdvmcli

AddWWNForHostStora geDomain serialnum=<array

serial number> model=<array type> port=<port id> domain=<domain id> wwn=<comma

separated wwns>

NOTE:

For the

XP48/XP512 arrays, the domain has to be specified for an add hoststoragedomain operation before doing an add wwn operation.

You will need to edit the file to pass the domain value. Otherwise, the domain parameter will show

<***ErrorCode***> in the output file by the

CLI Migration Tool.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

45

Table 14

Manual CLI command mapping (continued)

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

add security to lun add security_to_lun

<portname>,

<lun>,

<wwn/wwngrp>

[,<wwn/wwngrp>…]

Not supported

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP128/XP1024

/XP12000XP10000 arrays

Hdvmcli

AddWWNForHostStora geDomain serialnum=<array

serial number> model=<array type> port=<port id> domain=<domain id> wwn=<comma

separated wwns>

Supported for

XP128/XP1024/

XP12000/XP10000 arrays.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

Hdvmcli

AddWWNForLun serialnum=<array

serial number> model=<array type> port=<port id> domain=<domain id> devnum=<ldev id> wwn=<comma

separated wwns>

Partially supported.

NOTE:

For the

XP48/XP512 arrays, the domain has to be specified for an add security to lun operation. You will need to edit the file to pass the domain value.

Otherwise, the domain parameter will show

<***ErrorCode***> in the output file by the

CLI Migration Tool. add security to lun group

Either wwn or wwngrp can be specified, but at least one should be specified add security_to_lun_ group

<portname>,

<lungrpNickname>

, <wwn/wwngrp>

[,<wwn/wwngrp>…]

Not supported For XP512/XP48 arrays

Hdvmcli

AddWWNForLunGroup serialnum=<array serial number> model=<array type> port=<port id> objectID=<lungroup

object id> wwn=<comma

separated wwns>

Supported

Either wwn or wwngrp can be specified, but at least one should be specified

46 CLI migration

Table 14

Manual CLI command mapping (continued) add lun to lun group

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

add lun_to_lun_group

<portname>,

<groupNickname>,

<lunId1>[,<lunId

2>…]

Not supported

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli

ModifyLunGroup serialnum=<array serial number> model=<array type> port=<port id> objectID=<lungroup

object id> groupelements=<

Comma separated list of one or more ObjectIDs of the paths to be added to the Lun

Group >

[nickname=<Lun

group nickname> name=<Lun group

name>]

Partially supported.

NOTE:

For the XP512, the domain has to be specified in the path objectids for value in the add lun to lun group operations. You will need to edit the file to pass the domain value.

Otherwise, the domain

Path object ids parameters will show

<***ErrorCode***> in the output file by the

CLI Migration Tool. add wwn to wwn group add wwn_to_wwn_group

<portname>,

<wwnGrpNickname>

, <wwn>[,<

wwn>…]

Not supported create wwn group create wwn_group

<portname>,

<wwnGrpNickname>

, <wwn1>, <wwn2>

[,<wwn>,…]

Not supported

Hdvmcli

ModifyWWNGroup serialnum=<array

serial number> model=<array type> port=<port id> objectid=<wwngroup

object id> wwn=<Comma separated list of one or more WWNs to be added to the

WWN Group>

[nickname=<WWN

group nickname> name=<WWN group

name>]

Supported

For XP512/XP48 arrays

Hdvmcli

AddWWNGroup serialnum=<array

serial number> model=<array type> port=<port id> wwn=<Comma separated list of one or more WWNs to be added to the

WWN Group> nickname=<WWN

group nickname>

[name=<WWN group

name>]

Supported

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

47

Table 14

Manual CLI command mapping (continued)

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

create lun group create lun_group

<portname>,

<groupNickname>,

<lunid1>,

<lunid2>

[,<lunid3>…]

Not supported

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli

AddLunGroup serialnum=<array serial number> model=<array type> port=<port id> groupelements=<Com ma separated list of one or more

ObjectIDs of the paths to be added to the Lun Group> nickname=<Lun

group nickname>

[name=<Lun group

name>]

Partially supported.

NOTE:

For the XP512 array, the domain has to be specified in the path object ids for an add lun group operation. You will need to edit the file to pass the domain value.

Otherwise, the domain value in the path object ids parameter will show

<***ErrorCode***> in the output file by the

CLI Migration Tool. modify security switch modify security_switch

<portname>,

<switch> modify lun_security

<portname….>,

<switch…> modify lun group nickname modify wwn group nickname modify lun_group_nickna me <portname>,

<oldGrpNickname>

,

<newGrpNickname> modify wwn_group_nickna me <portname>,<

oldGrpNickname>,

<newGrpNickname>

Not supported

Not supported

Hdvmcli ModifyPort serialnum=<array

serial number> model=<array type> port=<PortID> lunsec=<true|false

>

Supported

Hdvmcli

ModifyLunGroup serialnum=<array

serial number> model=<array type> port=<port id> objectID=<lungroup

object id> groupelements=<

Comma separated list of one or more ObjectIDs of the paths to be added to the Lun

Group > nickname=<Lun

group nickname>

[name=<Lun group

name>]

Not supported, because path information cannot be received from the modify lun_group_ nickname command in the Command View

CLI.

Hdvmcli

ModifyWWNGroup serialnum=<array

serial number> model=<array type> port=<port id> objectid=<wwngroup

object id> wwn=<Comma separated list of one or more WWNs to be added to the

WWN Group> nickname=<WWN

group nickname>

[name=<WWN group

name>]

Not supported, because you cannot get wwn information from the modify wwn_group_ nickname command in the Command View CLI.

48 CLI migration

Table 14

Manual CLI command mapping (continued) modify wwn nickname modify wwn

Command View CLI

XP512/XP48

modify wwn_nickname

<portname>,

<oldNickname>,

<newNickname> modify wwn

<portname>,

<oldWwn>,

<newWwn>

Command View CLI

XP128/XP1024/

XP10000/XP12000

refer modify wwn

-nickname

<newWwnNickName> modify wwn

<portName>,

<HostGrpNickName

>,

<oldwwn/oldwwnNi ckName> [-wwn

<newWwn>]

[-nickname

<newWwnNickName>

]

Either wwn and/or nickname can be modified, but one of them has to be given delete lun group delete lun_group

<portname>,

<groupnickname>

Not supported

Command View AE CLI

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

delete lun from lun group delete lun_from_lun_gro up <portname>,

<grpNickname>,

<lunid1>[,<

lunid2>,…]

Not supported

Automatic translation support by the CLI

Migration Tool

Not applicable

Not applicable

For XP512/XP48 arrays

Hdvmcli

DeleteLUNGroup serialnum=<array

serial number> model=<array type> port=<port

id>lungroupid=<obj

ect id of the lun group to be

deleted>

Supported

Hdvmcli

ModifyLunGroup serialnum=<array serial number> model=<array type> port=<port id> objectID=<lungroup

object id> groupelements=<

Comma separated list of one or more ObjectIDs of the paths to be added to the Lun

Group>

[nickname=<Lun

group nickname> name=<Lun group

name>] ?

Partially supported.

NOTE:

For the XP512 the domain has to be specified in the path object ids for a modify lun group operation.

You will need to edit the file to pass the domain value. Otherwise, the domain value in the path object ids parameter will show

<***ErrorCode***> in the output file by the

CLI Migration Tool.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

49

Table 14

Manual CLI command mapping (continued) delete wwn

Command View CLI

XP512/XP48

delete wwn

<portname>,

<wwnnickname>

Command View CLI

XP128/XP1024/

XP10000/XP12000

delete wwn

<portName….>,

<HostGrpNickName

>

<,WwnNickName…/w wn…> delete wwn_group delete wwn_group

<portname>,

<wwnGrpNickname>

Not supported delete wwn from wwn group delete wwn_from_wwn_gro up <portname>,

<wwnGrpNickname>

, <wwn>[,<

wwn>….]

Not supported

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli DeleteWWN serialnum=<array serial number> model=<array type> port=<portid> wwn=<wwn to

delete>

Supported

For XP128/XP1024/

XP12000/XP10000 arrays:

Hdvmcli

DeleteWWNForHostSt orageDomain serialnum=<array

serial number> model=<array type> port=<portid> domain=<domain id> wwn=<wwn to

delete>

For XP512/XP48 arrays

Hdvmcli

DeleteWWNGroup serialnum=<array

serial number> model=<array type> port=<port id> wwngroup=<name of

the wwn group to

be deleted>

Supported

Hdvmcli

ModifyWWNGroup serialnum=<array

serial number> model=<array type> port=<port id> objectid=<wwngroup

object id> wwn=<Comma

separated list of one or more WWNs to be added to the

WWN Group>

[nickname=<WWN

group nickname> name=<WWN group

name>] ?

Supported.

50 CLI migration

Table 14

Manual CLI command mapping (continued) delete security from lun

Command View CLI

XP512/XP48

delete security_from_lu n <portname>,

<lunId>,

<wwn/wwngroup>

[,<wwn/wwngroup>

…]

Command View CLI

XP128/XP1024/

XP10000/XP12000

Not supported

Command View AE CLI Automatic translation support by the CLI

Migration Tool

For XP512/XP48 arrays

Hdvmcli

DeleteWWNForLun serialnum=<array

serial number> model=<array type> port=<port id> domain=<domain id> devnum=<ldev id> wwn=<comma

separated wwns>

Partially supported.

NOTE:

For the XP512 the domain has to be specified to perform a delete wwn for lun operation. You will need to edit the file to pass the domain value.

Otherwise, the domain parameter will be filled with

<***ErrorCode***> in the output file by the

CLI Migration Tool.

delete lun security

Either wwn or wwngrp can be specified, but at least one should be specified delete lun_security

<portname>,

<lunid>

Not supported delete security from lun group delete security_from_lu n_group

<portname>,

<lunGrpNickname>

, <wwn/wwngroup>

[,<wwn/wwngroup>

…]

Not supported

Hdvmcli DeleteWWN serialnum=<array

serial number> model=<array type> port=<portid> wwn=<wwn to

delete>

Not supported.

You cannot get WWN information from the delete lun_security command in the

Command View CLI.

For XP512/XP48 arrays

Hdvmcli

DeleteWWNForLunGro up serialnum=<array

serial number> model=<array type> port=<port

id>objectID=<Lun

Group object id> wwn=<Comma

separated wwns>

Supported

Either wwn or wwngrp can be specified, but at least one should be specified delete lun group security delete lun_group_securi ty <portname>,

<lunGrpNickname>

Not supported It is recommended that you use this command.

Hdvmcli

DeleteWWNForLunGro up serialnum=<array

serial number> model=<array type> port=<port id>objectID=<Lun

Group object id> wwn=<Comma

separated wwns>

Not supported.

You can not get WWN information from the delete lun_group_ security command in the Command View CLI.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

51

Table 14

Manual CLI command mapping (continued)

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

remove wwn group remove wwn_group

<portname>,

<wwnGrpNickname>

Not supported

Command View AE CLI

No equivalent command exists in the Command

View AE CLI.

Automatic translation support by the CLI

Migration Tool

N/A

VSC commands

list parity_group list parity_group list parity_group [

-fs] [

-initializecount

] [-emulation]

[-domain

<Domain…>] [ -pg

<PG…>] [ -vdev

<Vdev…>] [-size]

Hdvmcli

GetStorageArray subtarget=ArrayGro up

[serialnum=<array

serial number> model=<array

type>] list pg_volume_info list ldev_size_info list pg_volume_info

[-pg

<paritygrp>] list ldev_size_info

[-pg

<paritygrp>]

[-cu <cu>] can be gotten from list vsc [

-domain

<Domain…>] [ -pg

<PG…>] [ -vdev

<Vdev…>] same as list vsc [ -pg

<pg…>]

Hdvmcli

GetStorageArray subtarget=ArrayGro up

[serialnum=<array

serial number> model=<array

type>]

Hdvmcli

GetStorageArray subtarget=ArrayGro up

[serialnum=<array

serial number> model=<array

type>] list pg_freespace_inf o list unused_ldev_ids list pg_freespace_inf o [-pg

<paritygrp>] same as list parity_group [

-fs]

Hdvmcli

GetStorageArray subtarget=ArrayGro up

[serialnum=<array

serial number> model=<array

type>] list usable_cus list usable_cus list usable_cus No equivalent command exists in the Command

View AE CLI.

list unused_ldev_ids

[-cu <cu>] same as list vsc

[-unused]

No equivalent command exists in the Command

View AE CLI.

list count_for_volume

_initialize list count_for_volume

_initialize

[-pg

<paritygroup>] same as list parity_group

[-initializecoun t]

No equivalent command exists in the Command

View AE CLI.

Partially supported.

The CLI Migration Tool does not support the -initializecoun t, -emulation,

-domain , -pg,

-vdev and -size options for migration.

Partially supported.

The CLI Migration Tool does not support the

-pg option for migration.

Partially supported.

The CLI Migration Tool does not support the

-pg and –cu options for migration.

Partially supported.

The CLI Migration Tool does not support the

pg option for migration.

Not applicable

Not applicable

No applicable

52 CLI migration

Table 14

Manual CLI command mapping (continued) create custom volumes

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

create custom_volumes

<pgNum1>, <cu1>,

<ldev1>,

<emulType1>,

<ldevSize1>

[<;cu2,ldev2,emu

lType2,ldevSize2

>…] create custom_ldevs

<Domain>,<PG>,

<Vdev>,

<EmulationType>

, <LDevSize>,

<cuID…>,

<ldevID…>

Command View AE CLI Automatic translation support by the CLI

Migration Tool

Hdvmcli

AddLogicalUnit serialnum=<array

serial number> model=<array type> chassis=<chasis

number> groupnum=<array

group number> capacity=<capcaity

in KB> emulation=<emulati

on>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

No equivalent command exists in the Command

View AE CLI.

Not applicable volume initialize delete vsc volumes list vsc make volumes

List openv util volume initialize

<pgNum>, <cu1>,

<ldev1>

[<;cu2,ldev2>…] delete vsc_volumes

<pg>, <cu1>,

<ldev1>

[<;cu2,ldev2>…]

Not supported

Not supported

Not supported initialize vdev

<Domain>,

<PG>,<Vdev>,

<cu(ldev…)...> delete LDevs

<Domain>,

<PG>, <Vdev>,

<cu…>, <ldev…> list vsc [

[-deletable] [

-domain

<Domain…>] [ -pg

<PG…>] [ -vdev

<Vdev…>][-cv |

-nv] ] |

[-unused]

Hdvmcli

DeleteLogicalUnit serialnum=<array

serial number> model=<array type> devnum=<ldev

number>

Supported.

In translations for range commands, the migration is aborted at the first occurrence of an error and the command appears as an error for translation in the output file.

Hdvmcli

GetStorageArray subtarget=ArrayGro up arraygroupsubinfo=

LogicalUnit lusubinfo=LDev

[serialnum=<array

serial number> model=<array

type>]

Partially supported.

The CLI Migration Tool does not support the

–deletable,

-domain, -pg,

-vdev, -cv, -nv and -unused options for translation.

make volumes

<domain>, <pg>,

<vdev>,

<openvsize>,

<openvcount> ,

<cuID…>,

<ldev,…> -fs |

-ts

Hdvmcli

AddLogicalUnit serialnum=<array

serial number> model=<array type> chassis=<chasis number> groupnum=<array

group number> capacity=<capcaity

in KB> emulation=<emulati

on type>

[lusubinfo=Ldev]

Not supported.

list openv_util

<pgname>

-openvsize

<size>

-openvcount

<num> -fs|-ts

No equivalent command exists in the Command

View AE CLI.

Not applicable

Device Health commands

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

53

Table 14

Manual CLI command mapping (continued) list chip_status/cha_ status

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

Command View AE CLI

list chip_status

[-x]

[<chipname…> |

-s <statusType>] list chip_status

[-chip

<chipname…> |

-s <statusType>]

Hdvmcli

GetStorageArray subtarget=PortCont roller

[serialnum=<array

serial number> model=<array

type>] list cha_status

[-x]

[<chaname…> |

-s <statusType>] list cha_status

[-cha <chaname…>

| -s

<statusType>]

Hdvmcli

GetStorageArray subtarget=PortCont roller

[serialnum=<array

serial number> model=<array

type>] list chp_status list chp_status

[-x] [<chpname…>

| -s

<statusType>] list chp_status

[-chp <chpname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list dka_status/acp_s tatus list dka_status

[-x]

[<dkaname…> |

-s <statusType>] list dka_status

[-dka <dkaname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list acp_status

[-x] [<acpname…>

| -s

<statusType>] list acp_status

[-acp <acpname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list drr_status list drr_status

[-x] [<drrname…>

| -s

<statusType>] list drr_status

[-drr <drrname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list dkp_status list dkp_status

[-x] [<dkpname…>

| -s

<statusType>] list dkp_status

[-dkp <dkpname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list csw_status list csw_status

[-x] [<cswname…>

| -s

<statusType>] list csw_status

[-csw <cswname…>

| -s

<statusType>]

No equivalent command exists in the Command

View AE CLI.

list cm_status list cm_status

[-x] [<cmname…>

| -s

<statusType>] list cm_status

[-cm <cmname…> |

-s <statusType>]

No equivalent command exists in the Command

View AE CLI.

list sm_status list sm_status

[-x] [<smname…>

| -s

<statusType>] list sm_status

[-sm <smname…> |

-s <statusType>]

No equivalent command exists in the Command

View AE CLI.

list dkc_status list dkc_status list dkc_status Hdvmcli

GetStorageArray subtarget=Componen t list pg_status list pg_status

[-x] [-s

<statustype>]

[-pg <pgname> |

-domain <domain>

| -dku <dku>]

[-disk | -ldev] list pg_status

[-s

<statustype>]

[-pg <pgname> |

-domain <domain>

| -dku <dku>]

[-disk | -ldev]

No equivalent command exists in the Command

View AE CLI.

Automatic translation support by the CLI

Migration Tool

Partially supported.

The CLI Migration Tool does not support the

-x, -chip and -s options for migration.

Partially supported.

The CLI Migration Tool does not support the

-x, -cha and -s options for migration.

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Supported

Not applicable

54 CLI migration

Table 14

Manual CLI command mapping (continued)

Command View CLI

XP512/XP48

Command View CLI

XP128/XP1024/

XP10000/XP12000

list licencekey_info

[-productname

<productname>] install license_key

<productname…>,< keycode…>

Command View AE CLI

list dku_status list dku_status list dku_status Hdvmcli

GetStorageArray subtarget=Componen t list traps list traps

[-n

<componentnam e>] [-r

<refcode>]

[-s

<statusType>]

[-c

<category>]

Supported list traps

[-n

<componentnam

e>] [-r

<refcode>]

[-s

<statusType>]

[-c

<category>]

Hdvmcli GetAlerts Partially supported.

The CLI Migration Tool does not support

-r -c, –s for migration.

-n,

License Key commands

List licencekey_info

Install License

Key list licencekey_info

[-productname

<productname>]

Not supported

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

Automatic translation support by the CLI

Migration Tool

Not applicable

Not applicable

Un-install

License Key

Not supported uninstall license_key

<productname…>

No equivalent command exists in the Command

View AE CLI.

Not applicable

IP Security commands

List ipaddress list ipaddress not supported Not applicable

Add ipaddress add ipaddress

<ipaddress1> [,<

ipaddress2>…]

Delete ipaddress delete ipaddress

<ipaddr1>

[,<ipaddr2>…]

Not supported

Not supported

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

Not applicable

Not applicable

Session commands

list session list session

<arraySerialNumb

er> list session

<arraySerialNumb

er>

Not applicable

Kill session connect disconnect kill session

<sessionId> connect

<arraySerialNumb

er>

Disconnect kill session

<sessionId> connect

<arrayserialnumb

er> disconnect

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

Not applicable

Not applicable

Not applicable

Device Admin commands

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

55

Table 14

Manual CLI command mapping (continued)

Manage unmanage list device list array config add device

NOTE:

This command is not supported in the

Command View CLI from Command View

2.x and greater.

Command View CLI

XP512/XP48

Not supported unmanage

<arrayserianumbe

r>

Command View CLI

XP128/XP1024/

XP10000/XP12000

manage

<arrayserianumbe

r> unmanage

<arrayserianumbe

r>

Command View AE CLI

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

Hdvmcli

GetStorageArray

Automatic translation support by the CLI

Migration Tool

Not applicable

Not applicable list device list device The CLI Migration Tool does not support the

Device Admin commands for migration.

Lists all devices that can be accessed through Command

View

Lists all devices that can be accessed through the API server list arrayconfig list array_config

-firmware

-allocatedspace

-freespace

-totalspace

-ldevspercu

-ldevsperacp add device

<arraySerialNumb

er>,

<ipAddress>,< location>,

<contactInfo>,

<manage> create device

<ipaddress…>

[,<arrayserialnu

mber…>] [-manage

|-unmanage]

Hdvmcli

GetStorageArray

[serialnum=<array

serial number> model=<array

type>]

The CLI Migration Tool does not support the

Device Admin commands for migration.

For XP512/XP48 arrays

Hdvmcli

AddStorageArray family=<array-fami

ly> ipaddress=<ipaddre

ss>

[displayfamily=<di

splay-family-name> searchcommunity=<c ommunityname>]

The CLI Migration Tool does not support the

Device Admin commands for migration.

delete device

NOTE:

This command is not supported in

Command View CLI for Command View

2.x and greater.

All arguments are mandatory delete device

<arraySerialNumb

er> ipaddress should be specified. The serial number is optional.

One or more ipaddresses can be given.

Number of serial numbers specified should be equal to the number of ipaddresses.

delete device

<arraySerialNumb

er…>

For XP512/XP48 arrays:

Hdvmcli

AddStorageArray family=<array-fami

ly> ipaddress=<ipaddre

ss> userid=<username> arraypasswd=<userp

assword>

[displayfamily=<di

splay-family-name> ipaddress2=<second

ipaddress>]

Hdvmcli

DeleteStorageArray serialnum=<array

serial number> model=<array type>

The CLI Migration Tool does not support the

Device Admin commands for migration.

56 CLI migration

Table 14

Manual CLI command mapping (continued) modify device

NOTE:

This command is not supported in

Command View CLI for Command View

2.x and greater.

Command View CLI

XP512/XP48

modify device

<arraySerialNumb

er>,

<ipAddress>,<

location>,

<contactInfo>

Command View CLI

XP128/XP1024/

XP10000/XP12000

modify device

<arrayserialnumb

er…> [-location

<location…>]

[-contact

<contact…>]

Command View AE CLI Automatic translation support by the CLI

Migration Tool

The CLI Migration Tool does not support the

Device Admin commands for migration.

get refresh status list device_history

Location and/or contact can be given, but at least one must be specified

The number of contacts and/or locations should be one or equal to the number of arrayserialnumbers specified.

get_refresh_stat us

<arraySerialNumb

er> list array_status

<arrayserialnumb

er…> [-lock]

[-refresh]

[-get]

No equivalent command in the Command View

AE CLI

Before connecting to any array, the following commands are valid: list array_status get_refresh_status <arraySerialNumber> list device_history list device_history

No equivalent command exists in the Command

View AE CLI.

Before connecting to any array: list device_history <serialnumber>

Not applicable

Not applicable

General commands

execute abort

Exit help execute

<filename>

Abort

Exit help [<command>

[<modulename>]] execute

<filename>

abort

No equivalent command exists in the Command

View AE CLI.

No equivalent command exists in the Command

View AE CLI.

The CLI Migration Tool does not support this for migration.

Not applicable exit No equivalent command exists in the Command

View AE CLI.

Not applicable help [<command>

[<modulename>]]

? [<command>

[<modulename>]] or

Hdvmcli help [command] The CLI Migration Tool does not support this for migration.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

57

Comparing component display names and component IDs

This section explains the relationship between the various component names and identification numbers.

This information is useful if you are manually mapping the commands.

NOTE:

The

LU ID,CU ID, and LDEV ID values shown in the property file for the

XP48/XP512/XP1024/XP12000/XP10000 arrays are in decimals; these same values are shown in hexadecimals in the Command View CLI.

Port name versus port ID

The Command View CLI uses the port name for all of the CLI operations, whereas the Command View AE

CLI uses port-id. When mapping, supply the port-id wherever applicable. See the table for your array type.

XP12000

Table 15

XP12000 port names and port IDs

CHA name

CHA-1E

CHA-1F

19

20

21

22

15

16

17

18

23

24

25

11

12

13

14

7

8

9

10

5

6

3

4

1

2

Port ID

0

CL7-D

CL1-E

CL3-E

CL5-E

CL7-E

CL1-F

CL3-F

CL5-F

CL7-F

CL1-G

CL3-G

CL7-B

CL1-C

CL3-C

CL5-C

CL7-C

CL1-D

CL3-D

CL5-D

Port name

CL1-A

CL3-A

CL5-A

CL7-A

CL1-B

CL3-B

CL5-B

CHA name

CHA-1G

CHA-1H

51

52

53

54

47

48

49

50

55

56

57

43

44

45

46

39

40

41

42

35

36

37

38

Port ID

32

33

34

CL7-M

CL1-N

CL3-N

CL5-N

CL7-N

CL1-P

CL3-P

CL5-P

CL7-P

CL1-Q

CL3-Q

CL7-K

CL1-L

CL3-L

CL5-L

CL7-L

CL1-M

CL3-M

CL5-M

Port name

CL1-J

CL3-J

CL5-J

CL7-J

CL1-K

CL3-K

CL5-K

58 CLI migration

Table 15

XP12000 port names and port IDs (continued)

CHA-1A

CHA-1B

92

93

94

88

89

90

91

84

85

86

87

80

81

82

83

76

77

78

79

72

73

74

75

68

69

70

71

64

65

66

67

26

27

28

29

30

31

CL9-G

CLB-G

CLD-G

CLF-G

CL9-H

CLB-H

CLD-H

CL9-E

CLB-E

CLD-E

CLF-E

CL9-F

CLB-F

CLD-F

CLF-F

CL9-C

CLB-C

CLD-C

CLF-C

CL9-D

CLB-D

CLD-D

CLF-D

CL9-A

CLB-A

CLD-A

CLF-A

CL9-B

CLB-B

CLD-B

CLF-B

CL5-G

CL7-G

CL1-H

CL3-H

CL5-H

CL7-H

CHA-1L

CHA-1K

CL9-Q

CLB-Q

CLD-Q

CLF-Q

CL9-R

CLB-R

CLD-R

CL9-N

CLB-N

CLD-N

CLF-N

CL9-P

CLB-P

CLD-P

CLF-P

CL9-L

CLB-L

CLD-L

CLF-L

CL9-M

CLB-M

CLD-M

CLF-M

CL9-J

CLB-J

CLD-J

CLF-J

CL9-K

CLB-K

CLD-K

CLF-K

CL5-Q

CL7-Q

CL1-R

CL3-R

CL5-R

CL7-R

120

121

122

123

124

125

126

116

117

118

119

112

113

114

115

108

109

110

111

104

105

106

107

100

101

102

103

96

97

98

99

58

59

60

61

62

63

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

59

Table 15

XP12000 port names and port IDs (continued)

95 CLF-H

CHA-2Q

CHA-2R

156

157

158

159

152

153

154

155

148

149

150

151

144

145

146

147

140

141

142

143

136

137

138

139

132

133

134

135

128

129

130

131

192

193

CL2-G

CL4-G

CL6-G

CL8-G

CL2-H

CL4-H

CL6-H

CL8-H

CL2-E

CL4-E

CL6-E

CL8-E

CL2-F

CL4-F

CL6-F

CL8-F

CL2-C

CL4-C

CL6-C

CL8-C

CL2-D

CL4-D

CL6-D

CL8-D

CL2-A

CL4-A

CL6-A

CL8-A

CL2-B

CL4-B

CL6-B

CL8-B

CLA-A

CLC-A

CHA-2T

CHA-2U

60 CLI migration

127

188

189

190

191

184

185

186

187

180

181

182

183

176

177

178

179

172

173

174

175

168

169

170

171

164

165

166

167

160

161

162

163

224

225

CLF-R

CL2-Q

CL4-Q

CL6-Q

CL8-Q

CL2-R

CL4-R

CL6-R

CL8-R

CL2-N

CL4-N

CL6-N

CL8-N

CL2-P

CL4-P

CL6-P

CL8-P

CL2-L

CL4-L

CL6-L

CL8-L

CL2-M

CL4-M

CL6-M

CL8-M

CL2-J

CL4-J

CL6-J

CL8-J

CL2-K

CL4-K

CL6-K

CL8-K

CLA-J

CLC-J

Table 15

XP12000 port names and port IDs (continued)

CHA-2M

194

195

196

197

198

199

200

CLE-A

CLG-A

CLA-B

CLC-B

CLE-B

CLG-B

CLA-C

CHA-2X

226

227

228

229

230

231

232

CHA-2N

213

214

215

216

209

210

211

212

205

206

207

208

201

202

203

204

217

218

219

220

221

222

223

CLC-E

CLE-E

CLG-E

CLA-F

CLC-F

CLE-F

CLG-F

CLA-G

CLC-C

CLE-C

CLG-C

CLA-D

CLC-D

CLE-D

CLG-D

CLA-E

CLC-G

CLE-G

CLG-G

CLA-H

CLC-H

CLE-H

CLG-H

XP1024

Table 16

XP1024 port names and port IDs

Cluster1

CHA name Port ID Port name

CHA-2W

Cluster2

CHA name Port ID

245

246

247

248

241

242

243

244

237

238

239

240

233

234

235

236

249

250

251

252

253

254

255

Port name

CLC-N

CLE-N

CLG-N

CLA-P

CLC-P

CLE-P

CLG-P

CLA-Q

CLC-L

CLE-L

CLG-L

CLA-M

CLC-M

CLE-M

CLG-M

CLA-N

CLC-Q

CLE-Q

CLG-Q

CLA-R

CLC-R

CLE-R

CLG-R

CLE-J

CLG-J

CLA-K

CLC-K

CLE-K

CLG-K

CLA-L

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

61

Table 16

XP1024 port names and port IDs

(continued)

CHA-1P

CHA-1Q

CHA-1R

CHA-1S

44

45

46

47

12

13

14

15

40

41

42

43

8

9

10

11

36

37

38

39

6

7

4

5

32

33

34

35

2

3

0

1

CL1-N

CL1-P

CL1-Q

CL1-R

CL3-n

CL3-p

CL3-q

CL3-r

CL1-J

CL1-K

CL1-L

CL1-M

CL3-j

CL3-k

CL3-l

CL3-m

CL1-E

CL1-F

CL1-G

CL1-H

CL3-e

CL3-f

CL3-g

CL3-h

CL1-A

CL1-B

CL1-C

CL1-D

CL3-a

CL3-b

CL3-c

CL3-d

XP128

Table 17

XP128 port names and port IDs

Cluster1

CHA name Port ID Port name

62 CLI migration

Cluster2

CHA name

CHA-2V

CHA-2W

CHA-2X

CHA-2Y

60

61

62

63

28

29

30

31

56

57

58

59

24

25

26

27

52

53

54

55

20

21

22

23

48

49

50

51

16

17

18

19

CL2-N

CL2-P

CL2-Q

CL2-R

CL4-n

CL4-p

CL4-q

CL4-r

CL2-J

CL2-K

CL2-L

CL2-M

CL4-j

CL4-k

CL4-l

CL4-m

CL2-E

CL2-F

CL2-G

CL2-H

CL4-e

CL4-f

CL4-g

CL4-h

CL2-A

CL2-B

CL2-C

CL2-D

CL4-a

CL4-b

CL4-c

CL4-d

Port ID Port name

Table 17

XP128 port names and port IDs (continued)

CHA-1C

CHA-1D

CHA-1F

36

37

38

39

6

7

4

5

32

33

34

35

2

3

0

1

40

41

42

43

8

9

10

11

CL1-E

CL1-F

CL1-G

CL1-H

CL3-E

CL3-F

CL3-G

CL3-H

CL1-A

CL1-B

CL1-C

CL1-D

CL3-A

CL3-B

CL3-C

CL3-D

CL1-J

CL1-K

CL1-L

CL1-M

CL3-J

CL3-K

CL3-L

CL3-M

XP512

6

7

4

5

2

3

0

1

Table 18

XP512 port names and port IDs

Cluster 1

Port number CHA package Display name for port

CL1-A

CL1-B

CL1-C

CL1-D

CL1-E

CL1-F

CL1-G

CL1-H

CHA-1P

CHA-1Q

CHA-2G

CHA-2J

CHA-2K

Cluster 2

Port number

20

21

22

23

16

17

18

19

Display name for port

CL2-A

CL2-B

CL2-C

CL2-D

CL2-E

CL2-F

CL2-G

CL2-H

CHA package

CHA-2V

CHA-2W

52

53

54

55

20

21

22

23

48

49

50

51

16

17

18

19

56

57

58

59

24

25

26

27

CL2-E

CL2-F

CL2-G

CL2-H

CL4-E

CL4-F

CL4-G

CL4-H

CL2-A

CL2-B

CL2-C

CL2-D

CL4-A

CL4-B

CL4-C

CL4-D

CL2-J

CL2-K

CL2-L

CL2-M

CL4-J

CL4-K

CL4-L

CL4-M

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

63

Table 18

XP512 port names and port IDs (continued)

12

13

14

15

8

9

10

11

CL1-J

CL1-K

CL1-L

CL1-M

CL1-N

CL1-P

CL1-Q

CL1-R

CHA-1R

CHA-1S 28

29

30

31

24

25

26

27

XP48

Table 19

XP48 port names and port IDs

Cluster1

CHA name

CHA-1C

CHA-1D

CHA-1F

Port ID

6

7

4

5

2

3

0

1

8

9

10

11

Port name

CL1-A

CL1-B

CL1-C

CL1-D

CL1-E

CL1-F

CL1-G

CL1-H

CL1-J

CL1-K

CL1-L

CL1-M

XP10000

Table 20

XP10000 port names and port IDs

CHA name

MIX-1A

Port ID

68

69

70

71

80

64

65

66

67

Port name

CL1-A

CL3-A

CL5-A

CL7-A

CL1-B

CL3-B

CL5-B

CL7-B

CL1-E

Cluster2

CHA name

CHA-2G

CHA-2J

CHA-2K

CHA name

MIX-2F

CL2-J

CL2-K

CL2-L

CL2-M

CL2-N

CL2-P

CL2-Q

CL2-R

Port ID

196

197

198

199

208

192

193

194

195

Port ID

20

21

22

23

16

17

18

19

24

25

26

27

CHA-2X

CHA-2Y

Port name

CL2-A

CL2-B

CL2-C

CL2-D

CL2-E

CL2-F

CL2-G

CL2-H

CL2-J

CL2-K

CL2-L

CL2-M

Port name

CL2-A

CL4-A

CL6-A

CL8-A

CL2-B

CL4-B

CL6-B

CL8-B

CL2-E

64 CLI migration

Table 20

XP10000 port names and port IDs (continued)

CHA-1B

93

94

95

89

90

91

92

85

86

87

88

81

82

83

84

CL3-G

CL5-G

CL7-G

CL1-H

CL3-H

CL5-H

CL7-H

CL3-E

CL5-E

CL7-E

CL1-F

CL3-F

CL5-F

CL7-F

CL1-G

CHA-2E

Fibre address

101

102

103

104

97

98

99

100

105

106

217

218

219

220

221

222

223

213

214

215

216

209

210

211

212

AL-PA

(Loop ID)

3A (60)

39 (61)

36 (62)

35 (63)

34 (64)

33 (65)

32 (66)

31 (67)

2E (68)

2D (69)

CL4-G

CL6-G

CL8-G

CL2-H

CL4-H

CL6-H

CL8-H

CL4-E

CL6-E

CL8-E

CL2-F

CL4-F

CL6-F

CL8-F

CL2-G

Port fibre address values

Port fibre address values differ between the Command View CLI and the Command View AE CLI. Specify the appropriate values based on which version you are operating. If you are manually migrating from the

Command View CLI to the Command View AE CLI, you will need the following information.

Table 21 shows command parameter usage for Command View and Command View AE, and Table 22

provides a list of fibre addresses and respective arbitrated loop IDs.

Table 21

Command parameter usage

Array Type

XP512/XP48

XP128/XP1024/XP10000/XP12000

Command View CLI Uses:

Loop ID (hex)

AL-PA (hex)

Command View AE Uses:

AL-PA (hex)

AL-PA (hex)

Table 22

Fibre Addresses/Arbitrated Loop IDs (all array types)

Fibre address

7

8

5

6

3

4

1

2

9

10

AL-PA

(Loop ID)

EF (0)

E8 (1)

E4 (2)

E2 (3)

E1 (4)

E0 (5)

DC (6)

DA (7)

D9 (8)

D6 (9)

Fibre address

37

38

39

40

33

34

35

36

41

42

AL-PA

(Loop ID)

B2 (20)

B1 (21)

AE (22)

AD (23)

AC (24)

AB (25)

AA (26)

A9 (27)

A7 (28)

A6 (29)

Fibre address

69

70

71

72

65

66

67

68

73

74

AL-PA

(Loop ID)

72 (40)

71 (41)

6E (42)

6D (43)

6C (44)

6B (45)

6A (46)

69 (47)

67 (48)

66 (49)

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

65

Table 22

Fibre Addresses/Arbitrated Loop IDs (all array types)

CB (12)

CA (13)

C9 (14)

C7 (15)

C6 (16)

C5 (17)

C3 (18)

BC (19)

D5 (A)

D4 (B)

D3 (C)

D2 (D)

D1 (E)

CE (F)

CD (10)

CC (11)

BA (1A)

B9 (1B)

B6 (1C)

B5 (1D)

B4 (1E)

B3 (1F)

23

24

25

26

19

20

21

22

15

16

17

18

11

12

13

14

27

28

29

30

31

32

55

56

57

58

51

52

53

54

47

48

49

50

43

44

45

46

59

60

61

62

63

64

90 (32)

8F (33)

88 (34)

84 (35)

82 (36)

81 (37)

80 (38)

7C (39)

A5 (2A)

A3 (2B)

9F (2C)

9E (2D)

9D (2E)

9B (2F)

98 (30)

97 (31)

7A (3A)

79 (3B)

76 (3C)

75 (3D)

74 (3E)

73 (3F)

87

88

89

90

83

84

85

86

79

80

81

82

75

76

77

78

91

92

93

94

95

96

53 (52)

52 (53)

51 (54)

4E (55)

4D (56)

4C (57)

4B (58)

4A (59)

65 (4A)

63 (4B)

5C (4C)

5A (4D)

59 (4E)

56 (4F)

55 (50)

54 (51)

49 (5A)

47 (5B)

46 (5C)

45 (5D)

43 (5E)

3C (5F)

119

120

121

122

115

116

117

118

123

124

125

126

0 (**)

111

112

113

114

107

108

109

110

Fibre topology

Port fibre topology values differ between the Command View CLI and the Command View AE CLI. Specify the appropriate values based on your array type (XP48/XP512/XP128/XP1024/XP10000/XP12000).

See Table 23

if you are manually migrating from the Command View CLI to the Command View AE CLI.

Table 23

Port fibre topology values

3

4

5

Command View CLI

(Fibre Topology)

1

2 (Default)

Command View AE CLI (Fibre Topology)

"Fabric (on), FC-AL"

"Fabric (off), FC-AL"

"Fabric (on), Point-to-Point"

"Fabric (off), Point-to-Point"

"Not Fibre"

Host mode values

Port host mode values differ between the Command View CLI and the Command View AE CLI. Specify the appropriate values based on your array type (XP48/XP512/XP128/XP1024/XP10000/XP12000). See the following table if you are manually migrating from the Command View CLI to the Command View AE

CLI.

1F (72)

1E (73)

1D (74)

1B (75)

18 (76)

17 (77)

10 (78)

0F (79)

2C (6A)

2B (6B)

2A (6C)

29 (6D)

27 (6E)

26 (6F)

25 (70)

23 (71)

-

08 (7A)

04 (7B)

02 (7C)

01 (7D)

66 CLI migration

XP48/XP512

Table 24

XP48/XP512 port host mode values

Command View CLI Host Mode

(hexadecimal)

0x00

0x04

0x05

0x07

0x08

0x09

0x0A

0x0C

0x0E

0x0F

Command View AE

Host Mode

Standard

Sequent

OPEN-VMS

Tru64

HP

Solaris

Netware

Windows

HI-UX

AIX

XP128/XP1024

Table 25

XP128/XP1024 port host mode values

Command View CLI Host Mode

(hexadecimal)

0x00

0x04

0x05

0x07

0x08

0x09

0x0A

0x0C

0x0F

Command View AE

Host Mode

Standard

Sequent

OPEN-VMS

Tru64

HP

Solaris

Netware

Windows

AIX

XP12000

)

Table 26

XP12000/XP10000 port host mode values

Command View CLI Host Mode

(hexadecimal)

0x00

0x04

0x05

0x07

0x08

0x09

0x0A

Command View AE

Host Mode

Standard

Sequent

OPEN-VMS

Tru64

HP

Solaris

Netware

Description

Standard mode

Sequent mode

OPEN-VMS mode

Tru64 mode

HP mode

VxVM-DMP mode

Netware mode

PC Server

HI-UX

AIX mode

Description

Standard mode

Sequent mode

OPEN-VMS mode

Tru64 mode

HP mode

VxVM-DMP mode

Netware mode

MSCS Multi-Path mode

AIX mode

Description

Standard mode

Sequent mode

OPEN-VMS mode

Tru64 mode

HP mode

VxVM-DMP mode

Netware mode

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

67

Table 26

XP12000/XP10000 port host mode values

0x0C

0x0F

Windows

AIX

MSCS Multi-Path mode

AIX mode

Object Id representation in Command View AE CLI

Command View AE uses the object id command to represent lun group, wwn group, path,

and so on. Use this section when using the CLI manual command mapping table ( Table 14 on page 38).

LUN group object ID

LUNGROUP.<model>.<array serial number>.<port id>.<lun group nickname>

Example:

LUNGROUP.XP512.30433.0.mana1

WWN group object ID

WWNGROUP.<model>.<array serial number>.<port id>.<wwn group nickname>

Example:

WWNGROUP.HXP512.30433.3.group1

Path object ID

PATH.<model>.<array serial number>.<port id>.<domain>.<devnum>

Example:

PATH.XP512.30433.3.3.83

Host group object ID

HSDOMAIN.<model>.<array serial number>.<port id>.<domain>

Example:

HSDOMAIN.XP12000.10227.0.0

Logical Unit object ID

LU.<model>.<array serial number>.<devnum>

Example:

LU.XP12000.10227.99

WWN value representation in Command View AE CLI

XX.XX.XX.XX.XX.XX.XX.XX

Example:

12.34.56.78.90.AB.CD.EF

68 CLI migration

A Error codes

This appendix contains lists of error codes and appropriate follow-up actions. These error codes are only for the migration tools.

CLI Migration Tool error/completion messages

If the input file that the user specifies is empty, the following error message appears on the console and the

CLI Migration Tool exits.

File contains no data (empty file)

If the input file that the user specifies is not found, the following error message appears on the console and the CLI Migration Tool exits.

Input File not found. Please type in again.

If the CVCLI command XML file is not found, the following error message appears on the console and the

CLI Migration Tool exits.

Unable to locate CV command XML file.

If error occurs when loading the CVCLI command XML file, the following error message appears on the console and the CLI Migration Tool exits.

Error while loading CV command XML file

If the input file that the user specifies contains more than 2000 lines of commands, and all of the commands up to the limit specified are translated successfully, the following error message appears on the console and the migration tool exits after attempting to translate 2000 lines. This limit can be configured to a higher value in the configuration file cmt.cfg.

The number of lines present in command input file is more than configured value. Partial output saved in file <*_out.bat>

(where “*” is the input file name specified by the user.)

If the input file that the user specifies contains more than 2000 lines of commands, and the commands up to the limit specified are translated with errors, the following error message appears on the console and the migration tool exits after attempting to translate 2000 lines. This limit can be configured to a higher value in the configuration file cmt.cfg.

The number of lines present in command input file is more than configured value. Translation completed with errors. Partial output saved in file

<*_out.bat>

(where “*” is the input file name specified by the user.)

If the input file that the user specifies contains unsupported commands or insufficient data, the following message appears on the console when the translation is completed (with errors).

Translation completed with errors. Output saved in file <*_out.bat>

(where “*” is the input file name specified by the user.)

If the translation process completes without any errors, the following message appears on the console.

Translation completed successfully and output saved in file <*_out.bat>

(where “*” is the input file name specified by the user.)

The following conditions can occur if the cmt tool is run without cmt.cfg file in the working directory:

c. If the translation completes successfully, the following message appears on the console:

Unable to locate config file cmt.cfg. Translation completed successfully and output saved in file <*_out.bat> or <*_out.sh>

(where “*” is the input file name specified by the user.)

d. If the translation completes with errors, the following message appears on the console:

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

69

Unable to locate config file cmt.cfg.Translation completed with errors.

Output saved in file <*_out.bat> or <*_out.sh>>

(where “*” is the input file name specified by the user.)

The following conditions can occur if the cmt tool is run with an edited cmt.cfg file that contains unexpected values:

a. If the translation completes successfully, the following message appears on the console

Unable to read config file cmt.cfg. Translation completed successfully and output saved in file <*_out.bat> or <*_out.sh>>>

(where “*” is the input file name specified by the user.)

b. If the translation completes with errors, the following message appears on the console:

Unable to read config file cmt.cfg.Translation completed with errors.

Output saved in file <*_out.bat> or <*_out.sh>>>

(where “*” is the input file name specified by the user.)

If the value for serial number “-slno” that the user specifies does not match the array serial number in the connect command, the following error message appears on the console:

Mismatch of array serial number in connect command.

CLI Migration Tool error codes

The following is the list of error codes that migration tool generates. They appear in the cmt output file.

Error codes

(int/decimal)

100

Category

Unsupported command

Meaning

Command is unsupported for translation or command are unknown

101-200

201-210

Reserved

Host Group related

Error code

Meaning/Message

Action to be taken

Action to be taken

See

Table 14 on page 38 and attempt

to translate manually if you encountered this in response to a

Command View CLI command.

201 (This error code is for XP128/XP1024/XP10000/XP12000 arrays)

Unable to substitute Host Group ID for Host Group Nickname from the property file

Gather the data by running the Data Collection Tool or by manually editing the property file and then running the cmt again.

202 (This error code is for XP512/XP48 arrays)

Unsupported data field in the Command View CLI

Edit the CLI Migration Tool output file with the data obtained from Command

View AE CLI. Obtain the domain value (host group id) from Command View

AE CLI.

203-210

Reserved

70 Error codes

211-220 WWN related Error code

Meaning/Message

Action to be taken

211

Unable to substitute WWN for WWN Nickname from the property file

Gather the data by running the Data Collection Tool or by manually editing the CLI Migration Tool output file with the data obtained from the Command

View AE CLI. For XP128/XP1024/XP10000/XP12000, you can also manually edit the property file and then run the cmt again.

212-220

Reserved

221-230 Lun ID related Error code

Meaning/Message

Action to be taken

221

Unable to substitute CU:LDev for Lun ID from the property file

Gather the data by running the Data Collection Tool or by manually editing the CLI Migration Tool output file with the data obtained from Command View

AE CLI.

222-230

Reserved

231-240 LunGroup related

Error code

Meaning/Message

Action to be taken

231

Unable to get the LUN Ids for the LUN group from the property file

Gather the data by running the Data Collection Tool or by manually editing the CLI Migration Tool output file with the data obtained from Command View

AE CLI.

232-240

Reserved

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

71

241-250 WWNGroup related

Error code

Meaning/Message

Action to be taken

241

Unable to get the WWNs for the WWN group from the property file

Gather the data by running the Data Collection Tool or by manually editing the Migration Tool CLI output file with the data obtained from the Command

View AE CLI.

242-250

Reserved

251-260 Reserved

Command View CLI Data Collection Tool error/completion messages

(“cmdct”):

If the value for array type “-type” that the user specifies is not a valid array type, the following error message appears on the console:

Specified Array Type is not a valid XP Array Type. Please specify any one from the list (48/512/128/1024/12000/10000)

If “cmdct” tool cannot contact SVP because of communication errors or because SVP is not accessible, the following error message appears on the console:

Could not contact SVP, Please make sure that array is online and SVP is accessible

If the data collection process completes without any errors, the following message appears on the console.

Data collection completed successfully and output saved in file

<arraySerialNo.properties>

72 Error codes

B Sample commands for CLI migration

Because some of the Command View CLI commands cannot be mapped directly to Command View AE CLI commands, most Command View CLI commands are mapped to the closest Command View AE CLI commands. Sometimes different Command View AE CLI commands are required, depending on the option specified by the Command View CLI command.

The following provides sample command descriptions to help you to map the specified commands.

Sample Command View CLI commands versus Command View AE CLI commands

EXPAND LUN

Command View CLI

In the Command View CLI, in a single command create a LUSE and a path to it.

XP48/XP512 arrays:

expand lun <topCU>,< topLDev>, <device ldev>, <device ldev>,… -lun [<portname>],

<scsiId>, [<lunId>], <cu>, [<ldev>] or expand lun <topCU>,< topLDev>, -limit <ldevCount> -lun [<portname>], <scsiId>,

[<lunId>], <cu>, [<ldev>]

XP128/XP1024/XP12000/XP10000 arrays:

create luse <topCU>, <topLDev> -continuous <offset> | -disperse <deviceldevs…>

[-lun <port…>, <hostgrpnickname>, < lunid>]

Command View AE CLI

With Command View AE CLI, use the ADDLUSE or ADDLUN command, depending on the operation (for example, only LUSE creation or LUSE with path creation).

XP48/XP512 arrays

Hdvmcli AddLUN serialnum=<array serial number> model=<array type> port=<PortID> domain=<hoststoragedomain id> lun=<free lun id> lusedevnums=<comma separated ldev ids> scsi=<scsiid>

XP128/XP1024/XP12000/XP10000 arrays

Hdvmcli AddLUSE serialnum=<array serial number> model=<array type> devnums=< comma separated ldev ids> or

Hdvmcli AddLUN serialnum=<array serial number> model=<array type> port=<PortID> domain=<hoststoragedomain id> lun=<free lun id> lusedevnums=<comma separated ldev ids>

Sample Command View CLI versus Command View AE CLI output

Command View CLI

1) list device

CV_CLI> list device

Sending Request to CV server ...

Serial#,IPAddress,Type,Location,Contact,Manage,Ftp,Protocol

10058,15.13.170.120,XP 12000,Cupertino,Wai,manage,noftp,rmi

10033,15.43.212.61,XP 1024,HULKUL,Bangalore,manage,noftp,rmi

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

73

2) list array_config

CV_CLI 10033 (R)> list array_config

Sending Request to CV server ...

10033 : Data retrieval error encountered. Data display is old. Run list array_st atus for more information.

FirmwareRevision Allocatedspace Unallocatedspace Freespace TotalCapacity

RawCapacity TotalCacheSize

21-12-01 1800 Gbytes 490 Gbytes 281 Gbytes 2571 Gbytes 4075 Gbytes 8

192 Mbytes

Number of LDEVs per CU

CU 0 134

Number of LDEVs per ACP pair

ACP Pair 1 183

ACP Pair 2 105

CV_CLI 10033 (R)>

3) list port -l

CV_CLI> list port -l

Sending Request to CV server ...

10033 : Data retrieval error encountered. Data display is old. Run list array_status for more information.

PortNameType Loop-Id (Address) Topology WWN

ChannelSpeed Security

CL1-A Fibre 3 (E2) FCAL with Fabric ON 50060E8003

273100 Auto Mode ON

CL1-B Fibre 120 (10) Point-to-Point with Fabric ON 50060E8003

273101 Auto Mode OFF

CL1-C Fibre 2 (E4) Point-to-Point with Fabric ON 50060E8003

273102 Auto Mode ON

CL2-A Fibre 123 (04) Point-to-Point with Fabric OFF 50060E8003

273110 Auto Mode ON

CL2-B Fibre 17 (CC) Point-to-Point with Fabric ON 50060E8003

273111 Auto Mode ON

CL2-C Fibre 18 (CB) Point-to-Point with Fabric ON 50060E8003

273112 Auto Mode ON

4) list port -hostgrp -l

CV_CLI 10033 (R)> list port -hostgrp -l

Sending Request to CV server ...

10033 : Data retrieval error encountered. Data display is old. Run list array_st atus for more information.

PortNameHostGroupNickname HostMode HostModeName

CL1-A 1A-G00 08 HP mode

CL1-A SC2l 01 Reserved mode

74 Sample commands for CLI migration

5) cat Test.sh

#!/usr/bin/sh

#clear connect 30433 list device list port

C:\cli\cvcli>sh

$ cvcli -p user/user -f Test.sh

Starting the Command View Command Line Utility

#

Version : CV2.1

Loading XML Parser for validation, Please wait.....

Commands Loaded ....

Sending Request to CV server ...

Error encountered while contacting array 30433. Please try again.

Sending Request to CV server ...

Serial#,IPAddress,Type,Location,Contact,Manage,Ftp,Protocol

30433,15.106.211.25,XP 512,Bangalore,Krishna,manage,ftp,snmp

10058,15.13.170.120,XP 12000,Cupertino,Wai,manage,noftp,rmi

10056,15.43.212.61,XP 1024,Roseville R5U,Rob Farmelo,manage,noftp,rmi

10055,15.106.211.41,XP 12000,Bangalore,Krishna,manage,noftp,rmi

PortName,HostMode,Fibre Address,Fibre Topology

CL1-A ,0 ,10 ,3

CL1-B ,c ,2 ,3

CL1-C ,8 ,3 ,3

….

Command View AE CLI

1) Hdvmcli GetStorageArray <equivalent to list device>

C:\Program Files\HiCommand\DeviceManager\Hdvmcli>Hdvmcli.bat

GetStorageArray

Response:

An instance of StorageArray objectID=ARRAY.XP512.30433

[email protected]

description=XP512 (30433) at 15.106.211.25

serialNumber=30433 arrayFamily=XP512/48 arrayType=XP512 microcodeVersion=01-19-44/00 agentVersion=02-01-06/00 freeCapacityInGB=1

......

displayArrayType=XP512 numberOfLUs=136 numberOfAllocatedLUs=135 numberOfUnallocatedLUs=1

2) Hdvmcli GetStorageArray serialnum=10227 model=XP12000 <equivalent to list array_config for 10227>

C:\Program Files\HiCommand\DeviceManager\Hdvmcli>Hdvmcli.bat

GetStorageArray serialnum=10227 model=XP12000

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

75

Response:

An instance of StorageArray

objectID=ARRAY.XP1024.10227

[email protected]

description=XP12000 (10227) at 15.43.212.64

serialNumber=10227

arrayFamily= XP12K/10K

arrayType=XP12000

microcodeVersion=50-03-22/00

agentVersion=04_02_00

productName=XP12000

controllerVersion=50-03-23

numberOfControllers=1

capacityInGB=2,771

cacheInMB=16,384

sharedMemoryInMB=-1

numberOfSpareDrives=-1

freeCapacityInGB=1,875

allocatedCapacityInGB=896

3) Hdvmcli GetStorageArray subtarget=Port portsubinfo=HostStorageDomain serialnum=10227 model=XP12000 <equivalent to list port -l and list port -hostgrp -l for 10227>

C:\Program Files\HiCommand\DeviceManager\Hdvmcli>Hdvmcli GetStorageArray subtarget=Port portsubinfo=HostStorageDomain serialnum=10227 model=XP12000

Response:

An instance of StorageArray

objectID=ARRAY.XP12000.10227

[email protected]

description=XP12000 (10227) at 15.43.212.64

serialNumber=10227

.....

multipathSupport=1

securityStatus=2

sequenceNumber=10227

displayArrayFamily=XP12K/10K

displayArrayType=XP12000

numberOfLUs=430

numberOfAllocatedLUs=134

numberOfUnallocatedLUs=296

List of 1 Port elements:

An instance of Port

objectID=PORT.XP12000.10227.3

serialNumber=10227

arrayType=XP12000

portID=3

portType=Fibre

fibreAddress=E2

topology=Fabric(on), Point-to-Point

displayName=CL7-A

lunSecurityEnabled=true

controllerID=1

worldWidePortName=50.06.0E.80.04.27.F3.60

channelSpeed=0

portRole=Target

List of 2 HostStorageDomain elements:

An instance of HostStorageDomain

76 Sample commands for CLI migration

4) $ pwd

C:/Hdvmcli

$ sh Test.sh

C:\Hdvmcli>cat Test.sh

#!/usr/bin/sh

#clear

Hdvmcli GetStorageArray

STATUS=$?

if( $STATUS = 0) then

echo "Get Port details for portnumber 3 "

Hdvmcli GetStorageArray SubTarget=port port=3 serialnum=30433 model=XP512

5) fi

objectID=HSDOMAIN.XP12000.10227.3.0

portID=3

domainID=0

hostMode=Sequent

displayName=CL7-A-0

nickname=7A-G00

An instance of HostStorageDomain

objectID=HSDOMAIN.XP12000.10227.3.1

portID=3

domainID=1

hostMode=HP

displayName=CL7-A-1

nickname=7A-HP

C:\Hdvmcli>java -Xmx256m -cp Hdvmcli.jar;jsse.jar;jcert.jar;j net.jar;jdom.jar;xerces.jar;log4j-1.2.3.jar;

-Djavax.net.ssl.trustStore="HiComma ndCerts "

-Djava.protocol.handler.pkgs="com.sun.net.ssl.internal.www.protocol" com.hitachi.hds.cli.Hicmd GetStorageArray

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

77

Response:

An instance of StorageArray

objectID=ARRAY.XP512.30433

[email protected]

description=XP512 (30433) at 15.106.211.25

serialNumber=30433

arrayFamily=XP512/48

arrayType=XP512

microcodeVersion=01-19-44/00

agentVersion=02-01-06/00

productName=XP512

controllerVersion=01-19-51

numberOfControllers=1

capacityInGB=249

cacheInMB=2,048

sharedMemoryInMB=-1

numberOfSpareDrives=-1

freeCapacityInGB=1

allocatedCapacityInGB=247 hihsmCapacityInGB=0

…………….

C:\Hdvmcli>java -Xmx256m -cp Hdvmcli.jar;jsse.jar;jcert.jar;j net.jar;jdom.jar;xerces.jar;log4j-1.2.3.jar; -Djavax.net.ssl.trustStore="HiComma ndCerts " -Djava.protocol.handler.pkgs="com.sun.net.ssl.internal.www.protocol" com.hitachi.hds.cli.Hicmd GetStorageArray SubTarget=port port=3 serialnum=30433 model=XP512

Response:

An instance of StorageArray

objectID=ARRAY.XP512.30433

[email protected]

description=XP512 (30433) at 15.106.211.25

serialNumber=30433

arrayFamily=XP512/48

arrayType=XP512

microcodeVersion=01-19-44/00

agentVersion=02-01-06/00

productName=XP512

controllerVersion=01-19-51

numberOfControllers=1

capacityInGB=249

cacheInMB=2,048

sharedMemoryInMB=-1

numberOfSpareDrives=-1

freeCapacityInGB=1

allocatedCapacityInGB=247

hihsmCapacityInGB=0

onDemandCapacityInGB=0

totalFreeSpaceInGB=7

largestFreeSpaceInGB=1

capacityInKB=261,230,400

freeCapacityInKB=1,830,960

78 Sample commands for CLI migration

Sample executions of the CLI Migration Tool

(XP128/XP1024/XP10000/XP12000)

This section provides sample execution of instances where success, failure, and errors (with error#) occurred for the XP128/XP1024/XP10000/XP12000.

Unsupported commands for automatic translation and an insufficient data portion for the Command View

AE CLI are the major causes of failure or error when using the CLI Migration Tool.

Sample execution of the CLI Migration Data Collection Tool

NOTE:

In the following example, you can create host groups by editing the user section of the property file (see the green text in the example for the 10033.properties file) before running the cmt tool. In the cmt tool output, the command will be translated without any errors (see the command in green font in the example for the 10033_out.sh file).

C:\ migrationtool> cmdct -ip 15.43.212.61 -type 1024

Output property file 10033. properties contains the following commands:

# System generated file!.Generated @2005-05-20T12:34:18

# User section

# User editable portion

# NOTE- Each name value pair should start in a new line.

#hostGroupId=portId:HostGrpNickName:HGID:WWN_name:WWN_nickname

# WWN_name and WWN_nickname are optional hostGroupId=2:oapp11C:1

# System section!.

# User should not edit this section.

# example port_name:HostGrpNickName:HGID:WWN_name:WWN_nickname

#hostGroupId=portId:HostGrpNickName:HGID:WWN_name:WWN_nickname hostGroupId=0:1A-G00:0 hostGroupId=0:CVXP:1 hostGroupId=0:16dec1:2

Sample execution of the CLI Migration Tool

C:\ migrationtool> cmt -slno 10033 -f 10033.txt -p 10033.properties -type

1024 cmt.cfg contains the following commands:

#Maximum line for automatic translation

MAX_LINE= 2000

# OS_NAME= WINDOWS/HP-UX

OS_NAME= HP-UX

TRACE_LEVEL=8

Input command file 10033.txt contains the following Command View CLI commands: connect 10033 list lun -o c:\mapdev\data\wpschq4h_10033_listlun.txt

list port -hostgrp -l -o c:\mapdev\data\wpschq4h_10033_listport.txt

list wwn -o c:\mapdev\data\wpschq4h_10033_wwn.txt

modify lun_security 1A,ON create host_group 1A,oapp11A create host_group 1C,oapp11C modify host_mode 1B,oapp11B,08 create lun 1A,oapp11A,00,02,2B

Output command file 10033_out.sh contains the following Command View AE CLI commands:

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

79

# File Generated @2005-05-10T13:23:28

Hdvmcli GetStorageArray subtarget=Path serialnum=10033 model=XP1024 -o c:\mapdev\data\wpschq4h_10033_listlun.txt

Hdvmcli GetStorageArray subtarget=Port portsubinfo=HostStorageDomain serialnum=10033 model=XP1024 -o c:\mapdev\data\wpschq4h_10033_listport.txt

Hdvmcli GetStorageArray subtarget=Port portsubinfo=WWN serialnum=10033 model=XP1024 -o c:\mapdev\data\wpschq4h_10033_wwn.txt

Hdvmcli ModifyPort serialnum=10033 model=XP1024 port=0 lunsec=true

Hdvmcli AddHostStorageDomain serialnum=10033 model=XP1024 port=0 domain=<*** 201 oapp11A ***> nickname=oapp11A

Hdvmcli AddHostStorageDomain serialnum=10033 model=XP1024 port=2 domain=1 nickname=oapp11C

Hdvmcli ModifyPort serialnum=10033 model=XP1024 port=1 domain=2 hostmode=HP

Hdvmcli AddLUN serialnum=10033 model=XP1024 port=0 domain=<*** 201 oapp11A ***> lun=00 devnum=108

Sample execution of the CLI Migration Data Collection Tool (XP48/XP512)

C:\ migrationtool> cmdct -ip 15.43.212.63 -type 512

Property file 30055. properties contains the following commands:

# System generated file!.Generated @2005-06-01T14:37:45

# User should not edit this.

#Lun=portId:lunId:cuId:ldevId

Lun=0:0:0:5

Lun=0:1:1:3

Lun=0:2:0:204

Lun=0:3:0:9

#Lungroup=port:lungroupname:lunId

Lungroup=0:cvros92:5

Lungroup=0:cvros92:6

Lungroup=0:cvros92:7

Lungroup=0:cvros92:9

Lungroup=0:alpha136:16

#WWNGroup = portId:wwn name : wwn nickname : wwngroupname

WWNGroup=0:12.13.14.15.16.17.18.19:mana

WWNGroup=0:12.34.56.78.93.33.44.44:testing

WWNGroup=0:67.89.00.98.76.52.34.58:mana23

WWNGroup=0:10.00.00.00.c9.32.01.2e:wwnsmis

WWNGroup=0:12.34.56.78.90.12.34.56:nick

WWNGroup=1:20.00.00.e0.69.40.0a.e2:pasun

80 Sample commands for CLI migration

Sample execution of the CLI Migration Tool

C:\ migrationtool> Cmt -f 30055.txt -p 30055.properties -type 512 -slno

30055 cmt.cfg contains the following commands:

# Maximum line for automatic translation

MAX_LINE= 2000

# OS_NAME= WINDOWS/HP-UX

OS_NAME= WINDOWS

Input command file 30055.txt contains the following Command View CLI commands: connect 30055 list lun -o c:\mapdev\data\wpschq4h_30055_listlun.txt

list lun_group -port CL1-A -o c:\mapdev\data\wpschq4h_30055_listlungroup.txt

list lun_security -o c:\mapdev\data\wpschq4h_30055_listlunsecurity.txt

create lun_group CL1-A,SAP1A,[0-2] add security_to_lun_group CL1-A,SAP1A,mana,testing add lun_to_lun_group CL1-A,SAP1A,3

Output command file 30055_out.bat contains the following Command View AE CLI commands:

#File generated at : 2005-06-01T18:07:12

Call Hdvmcli GetStorageArray subtarget=Path serialnum=30055 model=XP512 -o c:\mapdev\data\wpschq4h_30055_listlun.txt

Call Hdvmcli GetStorageArray subtarget=Port portsubinfo=LunGroup lungroupsubinfo=Path serialnum=30055 model=XP512 port=0 -o c:\mapdev\data\wpschq4h_30055_listlungroup.txt

Call Hdvmcli GetStorageArray subtarget=Path pathsubinfo=WWN,WWNGroup serialnum=30055 model=XP512 -o c:\mapdev\data\wpschq4h_30055_listlunsecurity.txt

Call Hdvmcli AddLunGroup serialnum=30055 model=XP512 port=0 groupelements=PATH.XP512.30055.0.<*** 202 ***>.5,PATH.XP512.30055.0.<*** 202

***>.259,PATH.XP512.30055.0.<*** 202 ***>.204 nickname=SAP1A

Call Hdvmcli AddWWNForLunGroup serialnum=30055 model=XP512 port=0 objectID=LUNGROUP.XP512.30055.0.SAP1A wwn=12.13.14.15.16.17.18.19,12.34.56.78.93.33.44.44

Call Hdvmcli ModifyLunGroup serialnum=30055 model=XP512 port=0 objectID=LUNGROUP.XP512.30055.0.SAP1A groupelements= <*** 231 SAP1A

***>,PATH.XP512.30055.0.<*** 202 ***>.9 nickname=SAP1A

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

81

82 Sample commands for CLI migration

C FAQ

This chapter contains frequently asked questions regarding the migration procedures and tools.

Questions about the CLI Migration Tool

Does “cmt” communicate with the Command View server?

No, “cmt” is a standalone application/tool. It is not part of the Command View XP portfolio.

Does “cmt” communicate with the Command View AE server and submit translated commands?

No, “cmt” does not talk to Command View AE. “cmt” only translates the command file and generates the output file containing equivalent Command View AE CLI commands.

Does “cmt” communicate with the array SVP?

No, “cmt” does not talk to the SVP.

Does “cmdct” communicate with the Command View server?

No, “cmdct” is a standalone application/tool. It is not part of Command View XP portfolio.

Does “cmdct” communicate with Command View AE to collect data?

No.

Does “cmdct” communicate with the array SVP?

Yes, “cmdct” talks to the SVP and gathers the required data through SNMP/RMI.

How do I find out if data collection from the array is required?

There are two ways of doing this:

You can view the Command View CLI command file and find out if it contains any of the commands (or

its options) shown in Table 14 on page 38. If no such commands are listed, then data collection is

unnecessary and you can proceed with using the migration tool. Otherwise, data collection is necessary before using the migration tool.

You can use the migration tool and then view the output. If the output file contains errors related to the data portion of the commands, the errors will be prefixed with specific strings such as “***”, followed by predefined error codes. Depending on these error codes, you can decide if data collection is necessary. If it is, the migration tool can be used again after data collection.

What will happen if data collection was needed before command file migration but was not done because the array was unavailable or due to some other reason?

The CLI Migration Tool can still be used to translate the Command View CLI command file but the completeness of the translation will be very low. In such cases, the resultant Command View AE CLI file needs manual editing before submitting it to the Command View AE server.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

83

84 FAQ

Can the same property file serve as input for multiple command file migrations?

Yes, if all the command files are intended to be executed on the same disk array. Also, since array configuration is likely to change from time to time, it is suggested that the property file be the latest before using in migration.

Can the property file that is generated by cmdct be manually repaired/edited?

Yes, but only for certain array types.

For XP128/XP1024/XP12000/XP10000, there are some sections reserved which you may have to edit depending on specific conditions. The reserved area contains host group details for the create host group command.

For XP512/XP48, no specific section is reserved for you to edit. Instead, you will need to directly edit the

Command View AE CLI commands in the migration tool’s output file.

Questions about the Device Manager GUI

The host screen for my host does not show some LUNs assigned for that host

Please ensure that you have added all the arrays attached to your host. After you have added all the arrays, perform a LUNSCAN for each newly added arrays and refresh the host by clicking the Refresh button of the host content screen.

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

85

86 FAQ

Glossary

f cmt cmdct

Business Copy

Command View

Command View AE

Continuous Access configuration file

HORC

HORCM_CMD

HORCM_DEV

The batch file that starts the “cmt” application

Command View CLI Migration Data Collection Tool

The HP StorageWorks Business Copy XP software program that maintains up to nine internal copies of logical volumes on the disk array

HP StorageWorks Command View XP, version 2.2 and earlier, unless version is specifically stated.

HP StorageWorks Command View XP Advanced Edition

The HP StorageWorks Continuous Access XP software program that creates and maintains duplicate copies of the data store on a local disk array

A file that defines the pair configurations

Input command file

StorageWorks Continuous Access XP

A section of the RM instance configuration file that defines the disk devices used by RM to communicate with the disk array

A section of the RM instance configuration file that defines the volumes of the instance

host group host mode

LDEV

LUN

LUN p port type

Contains LUs that can only be accessed by hosts within the group. Multiple host groups can exists on a single port and each uses a single host mode

Each port can be configured with various options referred to as host modes. These modes are represented as a 2 digit hexadecimal number. The first hex digit represents special options; currently only number 10 is defined which represents Fast Wide SCSI protocol support. The second hex digit represents behavior for a specific host. These two numbers may be combined. For example, mode 18 represents Fast Wide SCSI protocol support on an HP-UX host.

Logical device

Logical unit number. A LUN results from mapping a SCSI logical unit number, port ID, and LDEV ID to a

RAID group. The size of the LUN is determined by the emulation mode of the LDEV, and the number of

LDEVs associated with the LUN. For example, a LUN associated with two OPEN-3 LDEVs will have a size of 4,693 MB.

logical unit (also called device emulation or device type)

Property file (can be generated using “cmdct” tool)<optional

The number of supported ports on an XP disk array is dependent upon the number of supported I/O slots and the number of ports available per I/O adapter. The XP family of disk arrays supports SCSI, Fibre

Channel (FC/ AL), and ESCON I/O interfaces. I/O support may vary with the selected disk array. Ports are named based upon their port group and port letter. Examples of port names include CL1-A through

CL1-R and CL2-A through CL2-R (letters I and O are skipped).

Type of array (XP48/XP512/XP128/XP1024/XP10000/XP12000)

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

87

88

Index

A

application environments

25

Application Policy Manager integrating

29

supported versions

28

application-related migrations

28

applications, supported

28

audience

7

audit logs, migrating

30

authorized reseller, HP

9

B

batch files, translating

32

C

CLI Migration Data Collection Tool collecting data

37

invoking

33

sample executions

79

CLI Migration Tool component display names

58

component IDs

58

configuration files

37

error codes

69

execution of

36

format of input file

33

format of output fille

35

format of property file

33

frequently asked questions

83

invoking

33

limitations

31

mapping commands

38

overview

31

procedure

32

requirements

31

sample executions

79

setting up the migration tool

36

supported commands

32

supported target environments

31

translating batch files

32

using

32

working with files

36

CLI migration, overview

31

cmdct

37

collecting data

37

command parameter usage

65

Command View AE versus Command View

13

Command View license entitlement migration

30

commands host group object ID

68

logical unit object ID

68

LUN group

68

mapping

38

,

73

object ID

68

path object ID

68

supported

32

WWW group object ID

68

comparing component display names and component

IDs

58

comparing port names with port IDs

58

component display names

58

component IDs

58

configuration files

37

conventions document

8

D

data, collecting

37

document conventions

8

prerequisites

7

related documentation

7

documentation, HP web site

7

E

error codes

69

execution of CLI Migration Tool

36

F

Fast Recovery Solution

28

fibre topology

66

format of input file

33

output file

35

property file

33

FRS see Fast Recovery Solution

28

H

help, obtaining

8

,

9

host group object ID

68

host mode values

66

HP authorized reseller

9

storage web site

9

Subscriber’s choice web site

9

technical support

8

HP Storage Essentials Enterprise Edition integrating

28

,

29

HP System Insight Manager 5.X

29

I

installation scenarios

20

integrating third-party products

30

invoking

CLI Migration Data Collection Tool

33

Migration User Guide for the HP Command View XP Portfolio and HP XP Remote Web Console

89

CLI Migration Tool

33

L

logical unit object ID

68

LUN group object ID

68

M

manual CLI command mapping

38

mapping commands

38

migration application environments

25

Application Policy Manager

29

applications

28

audit logs

30

Command View AE and Command View installed on different management servers

26

Command View AE and Command View installed on same management server

24

Command View and Command View AE

26

Fast Recovery Solution

28

from Command View to Command View with Remote

Web Console

23

licenses

30

overview

11

Path Connectivity

28

Performance Advisor

29

planning

12

procedures

22

requirements

15

scenarios

15

scenarios and requirements

15

standalone Hitachi software

28

Storage Area Manaer

28

supported applications

28

third-party products

30

to Command View AE with Remote Web Console

22

to standalone Remote Web Console

22

O

object ID command

68

OpenView Storage Area Manager

28

P

Path Connectivity-related migrations

28

path object ID

68

Performance Advisor

29

port fibre address values

65

port IDs

58

port names

58

prerequisites

7

R

recommended configurations

12

related documentation

7

Remote Web Console environments

16

overview

15

user group permissions and mapping

17

,

18

S

sample commamds

73

sample executions of migration tools

79

setting up the CLI Migration Tool

36

standalone Hitachi software

28

Subscriber’s choice, HP

9

supported applications

28

supported commands

32

supported target environments

31

System Insight Manager, integrating

28

T

target environments, supported

31

technical support, HP

8

translating batch files

32

U

user administration

16

using, CLI Migration Tool

32

W

web sites

HP documentation

7

HP storage

9

HP Subscriber’s choice

9

working with CLI Migration Tool files

36

WWN group object ID

68

90

Figures

1 HP StorageWorks XP Remote Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2

Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Comparison of Command View AE and Command View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Remote Web Console Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5 Command VIew user groups permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6 Remote Web Console mapping to Command View users (XP10000/XP12000) . . . . . . . . . . . . . . . . . 17

7 Remote Web Console and Command View default users (XP10000/XP12000) . . . . . . . . . . . . . . . . . 17

8 Remote Web Console mapping to Command View users (XP1024/XP128) . . . . . . . . . . . . . . . . . . . . 18

9 Remote Web Console and Command View default users (XP1024/XP128) . . . . . . . . . . . . . . . . . . . . 18

10 Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

11 Application environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

12 Applications supported for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

13 CLI Migration Tool files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

14

Manual CLI command mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

15

XP12000 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

16

XP1024 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

17

XP128 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

18

XP512 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

19

XP48 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

20

XP10000 port names and port IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

21 Command parameter usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

22 Fibre Addresses/Arbitrated Loop IDs (all array types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

23 Port fibre topology values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

24 XP48/XP512 port host mode values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

25 XP128/XP1024 port host mode values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

26 XP12000/XP10000 port host mode values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents