HP XP Auto LUN Software User Manual

HP StorageWorks
Auto LUN XP user guide

for the XP1024/XP128

Part number: T1615-96003
Third edition: March 2006

Legal and notice information

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

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government
under vendor’s standard commercial license.

The information contained herein 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.

ESCON and S/390 are registered trademarks or trademarks of International Business Machines Corporation (IBM).

HP-UX is a product name of Hewlett-Packard Company.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.

Netscape Navigator is a registered trademark of Netscape Communications Corporation in the United States and other countries.

Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.

UNIX is a registered trademark of X/Open Company Limited in the United States and other countries and is licensed exclusively through X/Open
Company Limited.

Windows and Windows NT are registered trademarks of Microsoft Corporation.

All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective
owners.

Auto LUN XP user guide for the XP1024/XP128

Contents

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

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

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

Firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

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

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

Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Auto LUN XP for the XP1024/XP128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Auto LUN XP features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Auto LUN XP tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Reserve volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Volume migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Estimating usage rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Automatic migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Storage management by maximum disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Keep reserved volumes in high HDD classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Auto migration sequence of events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Manual migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Requirements and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Logical volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Source volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

LUSE source volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Target volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Number of volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Auto migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Auto migration execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Manual migration execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Auto migration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Powering off disk arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

iSCSI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Starting Auto LUN XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Auto LUN pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Tabs and selection trees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Monitoring Term section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Monitoring Data section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Graph section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

WWN, Port-LUN, LDEV, and Physical tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

WWN tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Port-LUN tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

LDEV tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Physical tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Creating and executing migration plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Manual Migration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Pane contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Tree view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Migrating volumes manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Deleting manual migration plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Auto LUN XP user guide for the XP1024/XP128 3

Auto Migration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Pane contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Auto Migration Plans section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Auto Plan Parameter section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Setting auto migration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deleting auto migration plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Remaking auto migration plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Attribute tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Pane contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Reserving target volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Setting (fixing) parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Releasing (unfixing) parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Changing maximum disk usage rates for HDD classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

History tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Pane contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Viewing migration history logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Troubleshooting Auto LUN XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2 Auto LUN/Performance Control Base Monitor for the XP1024/XP128. . . . . . . . . . . . . . 37

Auto LUN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Auto LUN Monitoring Options pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

XP1024/XP128 disk arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Usage statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Collecting usage statistics about disk array resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Viewing parity group usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Viewing logical volume usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Viewing channel adapter (CHA) usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Viewing channel processor (CHP) usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Viewing disk adapter (DKA) usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Viewing disk processor (DKP) usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Viewing data recovery and reconstruction processor (DRR) usage statistics . . . . . . . . . . . . . . . . . . . . . 44

Viewing write pending rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Viewing access path usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Workload and traffic statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Collecting workload and traffic statistics about disk drives, ports, and LU paths. . . . . . . . . . . . . . . . . . 46

Viewing disk drive workload statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Viewing disk array port traffic statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Viewing HBA/port traffic statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figures

1 Moving volumes to another class based on usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Auto migration function example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Auto migration function example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 Auto LUN pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 WWN, Port-LUN, LDEV, and Physical tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6 Manual Migration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7 Auto Migration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

8 Attribute pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9 Class table boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

10 Parity group table boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

11 Attribute tab tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

12 History tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

13 Auto LUN Monitoring Options pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

14 Parity group usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

15 Logical volume usage statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

16 CHA usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

17 CHP usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

18 DKA usage statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4

19 DKP usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

20 DRR usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

21 Write pending rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

22 Usage statistics about paths between adapters and the cache switch . . . . . . . . . . . . . . . . . . . . . . . . 45

23 Usage statistics about paths between adapters and shared memory. . . . . . . . . . . . . . . . . . . . . . . . . 45

24 Usage statistics about paths between cache switches and cache memory . . . . . . . . . . . . . . . . . . . . . 45

25 Workload statistics for all parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

26 Workload statistics for a specific parity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

27 Workload statistics for logical volumes in a parity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

28 Traffic statistics about ports in a disk array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

29 Traffic statistics about host ports to which a disk array port is connected. . . . . . . . . . . . . . . . . . . . . . 48

30 Traffic statistics about host ports in a host group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

31 Traffic statistics about LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

32 Traffic statistics for host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

33 Traffic statistics for each PFC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

34 Traffic statistics for each port connected to a specified HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Tables

1 Recommended and minimum firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Movability of volumes in pairs consisting of CV and normal values . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Non-cascaded volumes that can be used as source volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5 Cascaded volumes that can be used as source volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 Graph contents based on list selection (Port-LUN tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7 Auto LUN pane, Port-LUN tab icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

8 Auto LUN pane, Physical tab icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9 Migration log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Auto LUN XP user guide for the XP1024/XP128 5

6

About this guide

This guide provides information about the following:

• ”Auto LUN XP for the XP1024/XP128”

•”Auto LUN XP features” on page 11

•”Auto LUN XP tasks” on page 11

•”Reserve volumes” on page 12

•”Volume migration” on page 12

•”Estimating usage rates” on page 12

•”Automatic migration” on page 13

•”Manual migration” on page 15

•”Requirements and restrictions” on page 15

•”Starting Auto LUN XP” on page 18

•”Creating and executing migration plans” on page 23

•”Troubleshooting Auto LUN XP” on page 36

• ”Auto LUN/Performance Control Base Monitor for the XP1024/XP128”

•”Auto LUN statistics” on page 37

•”Usage statistics” on page 40

•”Workload and traffic statistics” on page 46

Intended audience

This guide is intended for customers and HP-authorized service providers with knowledge of the following:

• Disk array hardware and software

• Data processing and RAID storage subsystems and their basic functions

Prerequisites

Prerequisites for using this product include:

• Installation of the HP StorageWorks disk array(s)

• Installation of the license key for this product

Firmware versions

The recommended firmware versions shown below provide the optimal level of support for the features
provided with this product. Older firmware versions can be used; however, product features enabled with
newer firmware will not appear.

Table 1 Recommended and minimum firmware versions

XP disk array Minimum Recommended

XP1024/XP128 21-14-14-00/00 or later 21-14-18-00/00 or later

Related documentation

In addition to this guide, please refer to other documents for this product:

• HP StorageWorks Command View XP User Guide for XP Disk Arrays

• HP StorageWorks XP Remote Web Console User Guide for XP1024/XP128

• HP StorageWorks Continuous Access XP Journal User Guide

• HP StorageWorks Performance Control XP User Guide

Auto LUN XP user guide for the XP1024/XP128 7

• HP StorageWorks XP Disk/Cache Partition User Guide

You can find these documents at http://www.hp.com/support/rwc/manuals

Document conventions and symbols

Table 2 Document conventions

Convention Element

Blue text: Table 1

Blue, underlined text:
(http://www.hp.com)

Bold text

Italic text

Monospace text

Monospace, italic text

Cross-reference links and e-mail addresses

Web site addresses

• Keys that are pressed

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

• GUI elements that are clicked or selected, such as menu and list

Text emphasis

• File and directory names

• System output

• Code

• Commands, their arguments, and argument values

• Code variables

• Command variables

.

items, buttons, and check boxes

Monospace, bold text

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.

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

Emphasized monospace text

.

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

8

Subscription service

HP strongly recommends that customers register online using the Subscriber's choice web site:

http://www.hp.com/go/e-updates

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

After subscribing, locate your products by selecting Business support and then Storage under Product
Category.

Helpful web sites

For additional information, see the following HP web sites:

• h

ttp://www.hp.com

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

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

• http://www.hp.com/support/rwc/manuals

.

Auto LUN XP user guide for the XP1024/XP128 9

10

1 Auto LUN XP for the XP1024/XP128

HP StorageWorks Auto LUN XP monitors resources in disk arrays and hosts connected to disk arrays. Auto
LUN XP works with open system and mainframe volumes. You can analyze the information Auto LUN XP
provides to optimize data storage and retrieval on disk arrays, resolve activity bottlenecks, and optimize
volume allocation.

Auto LUN XP features

Auto LUN XP provides the following features:

• When a migration plan (set of detailed user-specified parameters) is in place, Auto LUN XP

automatically migrates logical volumes in disk arrays.

• Auto LUN XP operations are completely non-disruptive. Data being migrated remains online to all hosts

for read and write I/O operations throughout the volume migration process.

• Auto LUN XP supports manual volume migration operations and estimates performance improvements

prior to migration.

Auto LUN XP begins by obtaining usage statistics about physical hard disk drives, logical volumes,
processors, and other resources in disk arrays. Then, using manual or automatic migration, Auto LUN XP
balances the workload among hard disk drives, logical volumes, and processors to improve system
performance.

Use HP Performance Control XP to ensure that I/O operations requiring high performance receive higher
priority than I/O operations from other, lower-priority hosts. You can set the priority of disk arrays, monitor
I/O and transfer rates, and limit performance of less-critical arrays when necessary to maintain
performance of high-priority arrays.

NOTE: Partition-level users in the StorageAdmins group cannot use Auto LUN XP, but users with full array

access can use Auto LUN XP.

For users in the StorageAdmins group, the functions you can use are limited. For more information about
these limitations, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the

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

Auto LUN XP tasks

• Load balance disk array resources to improve performance. Balancing resource usage can significantly

improve disk array performance. Use Auto LUN XP data to optimize several areas of performance,
including front-end and back-end processor usage and allocation of logical volumes to physical disk
drives and RAID level.

• Optimize disk drive access patterns. Auto LUN XP collects and analyzes information about disk drive

access patterns and can migrate volumes to optimize host access to data. For example, RAID-1
technology might provide better performance than RAID-5 under certain conditions, and one disk drive
type might provide better performance than another for certain types of access. Auto LUN XP fine-tunes
logical volume allocation.

• Analyze disk array usage. Auto LUN XP displays performance data graphically to highlight peaks and

trends. Use the graph to identify activity bottlenecks.

• Better utilize RAID levels and HDD types. The XP1024/XP128 supports both RAID-1 and RAID-5

technologies and a mixture of RAID-1 and RAID-5 parity groups. The XP1024/XP128 also supports
several types of hard disk drives (HDDs) and allows a mixture of HDD types within each disk array
domain to provide maximum flexibility in configuration. Auto LUN XP takes into account RAID level and
physical HDD performance of each parity group, enabling reallocation of logical volumes and
optimization with respect to both RAID level and HDD type. The proper combination of RAID level and
HDD type for logical volumes can significantly improve disk array performance.

Auto LUN XP user guide for the XP1024/XP128 11

Reserve volumes

The reserve volume function reserves target volumes for automatic and manual migration operations. After
you reserve a number of target volumes, Auto LUN XP maintains this number of reserved volumes by
swapping the reserve attribute after each migration operation (following the migration operation, the
original source volume becomes a reserved volume).

Volume migration

Auto LUN XP volume migration operations consist of two steps:

• Copy the data on the Auto LUN XP source volume to the Auto LUN XP target volume

• Transfer host access to the target volume to complete the migration

The Auto LUN XP source volume can be online to hosts during migration. The target volume is reserved
prior to migration to prevent host access during migration. The source and target volumes can be
anywhere in the disk array.

The Auto LUN XP copy operation copies the entire contents of the source volume to the target volume. If
write I/Os update the source volume during the copy operation, the XP1024/XP128 uses a cylinder map
to track updates and performs additional copy operations after the initial copy is complete to duplicate the
updates at the target volume.

When volumes are fully synchronized (no differential data on source volume), the XP1024/XP128
completes the migration by swapping the reserve attribute (target becomes normal and source becomes
reserved) and redirecting host access to the target volume. Auto LUN XP performs all migration operations
sequentially (one volume migration at a time).

Typical copy times for open system volumes (with no other I/O activity) are:

• OPEN-3: 1.5 minutes

• OPEN-8/9: 4.5 minutes

• OPEN-E: 9 minutes

• OPEN-V: variable

For automatic and manual migration operations, Auto LUN XP checks the current write pending rate. If the
write pending rate is higher than 60%, Auto LUN XP cancels the migration. For auto migration, Auto LUN
XP also checks current disk usage of source volumes and source and target parity groups. If current disk
usage is higher than the user-specified maximum for auto migration, Auto LUN XP cancels the migration.

Estimating usage rates

The estimate function calculates expected usage of source and target parity groups after a proposed
volume migration. The estimate function uses subsystem usage data collected by the monitor function, HDD
performance characteristics, and RAID level to estimate expected usage rates. The automatic and manual
migration functions use these estimated values to verify proposed migrations.

For each proposed migration operation, Auto LUN XP automatically estimates expected usage rates for
source and target parity groups. The estimate function calculates expected results of a proposed volume
migration based on XP1024/XP128 monitor data collected during the user-specified monitor data term.
The estimate function considers RAID level and HDD type when estimating expected usage rates (RAID-1
and RAID-5 have different access characteristics).

The estimate function is a critical component of the auto migration function. The estimate function calculates
expected parity group usage for source and target parity groups, and the auto migration function uses
these estimates to verify proposed migrations. If any condition prevents Auto LUN XP from estimating an
expected usage rate (for example, invalid monitor data), the auto migration function will not schedule the
migration operation.

For manual migration operations, when you select the source volume, Auto LUN XP displays expected
usage rates for the source parity group, so you can see the predicted effect of migrating the selected
volume out of its group. When you select the target volume, Auto LUN XP displays expected usage rates for
the target parity group, so you can see the predicted effect of adding the selected source volume to the
selected parity group.

12 Auto LUN XP for the XP1024/XP128

Auto LUN XP does not estimate processor or access path usage. You can use Auto LUN XP migration
operations to improve DKP and DRR usage, but cannot use them to address CHP or access path usage.

Perform Auto LUN XP migration only when you expect a large improvement in disk array performance.
Auto LUN XP migration might not provide significant improvement if parity group or volume usage varies
only slightly or if overall DKP or DRR usage is relatively high. Also keep in mind that disk array tuning
operations might improve performance in one area while decreasing performance in another. For
example, suppose parity groups A and B have average usage values of 20% and 90%, respectively. Auto
LUN XP estimates that if one logical volume is migrated from parity group B to parity group A, the usage
values will become 55% and 55%. If you perform this migration operation, I/O response time for parity
group B will probably decrease and I/O response time for parity group A might increase, while the overall
throughput might increase or decrease.

Automatic migration

Auto migration is the primary tuning method for disk arrays. Auto migration analyzes data and executes
migration plans automatically based on user-specified parameters. Use Auto LUN XP to schedule auto
migration operations, select data to be analyzed, and specify maximum time and performance impact of
auto migration operations. Auto LUN XP displays a detailed log of auto migration activities.

Auto migration operations are based on the following major parameters:

• Hierarchy of parity groups. Auto LUN XP arranges parity groups in the XP1024/XP128 in a hierarchy

based on HDD type, and assigns each parity group to a class based on performance of its HDD type.
Classes are ordered from highest performance drive (class A) to lowest performance drive (class B, C,
or higher depending on number of HDD types available). The auto migration function uses this
hierarchy to identify target volumes for auto migration operations.

The auto migration function can also specify “fixed” parity groups that are excluded from auto
migration operations.

• Maximum disk usage. The auto migration function specifies the maximum disk usage rate for each

HDD class in the XP1024/XP128, and uses these limits to identify source volumes for auto migration
operations.

You must identify and specify disk usage limits for your environment. When you use the same maximum
disk usage rate for all HDD classes, HDD performance is the only factor used in determining auto
migration plans. When you specify different usage limits for HDD classes, you can bias the auto
migration function to favor (or avoid) certain HDD types. Migrating high-usage volumes to higher HDD
classes should significantly improve host access to volumes, which can also have a large effect on disk
array performance.

The auto migration function also specifies the maximum disk usage rate during auto migration
operations, so you can control the impact of Auto LUN XP copy operations on disk array performance.
If source or target parity group usage exceeds the specified limit during migration, the auto migration
operation is canceled.

Do not perform manual migration operations while the auto migration function is active. Always turn off the
auto migration function and cancel any existing auto migration plan before performing manual migration
operations.

Storage management by maximum disk usage

Use the auto migration function to specify maximum usage rate for each HDD class in an XP1024/XP128.
When a parity group exceeds this limit, the auto migration function makes a plan to migrate one or more
volumes in this parity group to a parity group in a higher HDD class or to a parity group in the same HDD
class with lower usage.

This storage tuning method addresses and can eliminate disk drive activity bottlenecks. Auto LUN XP uses
its estimated usage rates to verify each proposed auto migration, and will not perform a migration
operation that might result in a target parity group exceeding the user-specified maximum disk usage rate.

The auto migration function identifies parity groups that exceed the user-specified usage limit, and selects
high-usage volumes as source volumes to be migrated to parity groups in higher HDD classes or to other
parity groups in the same HDD class with lower usage.

Auto LUN XP user guide for the XP1024/XP128 13

Keep reserved volumes in high HDD classes

When parity groups in the highest HDD classes start to run out of reserved (empty) volumes, Auto LUN XP
maintains available reserve volumes by automatically migrating low-usage volumes from higher HDD class
groups to lower HDD class groups.

Figure 1 Moving volumes to another class based on usage

The auto migration function can move a high-usage volume to a higher HDD class group, forcing a
low-usage volume out of that HDD class group. To do so, the auto migration function requires a minimum of
5% difference in estimated disk usage between the two volumes. If the difference is less than 5%, this
migration is considered ineffective and the volume is not moved.

Figure 2 Auto migration function example 1

The auto migration function can also move a volume from one parity group to another group of the same
HDD class, forcing another volume out of the destination parity group. To do so, the auto migration
function requires a minimum of 20% difference in estimated disk usage between the two volumes. If the
difference is less than 20%, this migration is considered ineffective and the volume is not moved.

Figure 3 Auto migration function example 2

Auto migration sequence of events

The following are the typical steps to set up an auto migration plan:

1. Analyze monitor data. You specify the monitor data term to be analyzed.

2. Make auto migration plan. You specify the auto migration plan’s parameters.

3. Perform auto migration plan. You specify when the auto migration plan is executed.

14 Auto LUN XP for the XP1024/XP128

4. Analyze monitor data to confirm tuning results.

Manual migration

Use manual migration to select and migrate logical volumes under direct, manual control. The manual
migration function displays estimated results of proposed migration operations, which you can use to
determine expected performance improvements prior to the actual migration.

While auto migration operations are based on disk usage and hierarchy of parity groups, you can use
manual migration operations to address back-end processor usage (DKPs and DRRs) and volume and
parity group usage. If monitoring shows high or unbalanced processor usage, use manual migration
operations to tune the processor performance of the XP1024/XP128.

Requirements and restrictions

Logical volumes

Source and target volumes must be in the same XP1024/XP128 and have the same emulation type and
capacity.

NOTE: For users in the StorageAdmins group, the function you can use are limited. For more information

about these limitations, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the
HP StorageWorks XP Remote Web Console User Guide for XP1024/XP128.

Whether you can or cannot perform volume migration with a pair consisting of customized volumes (CVs)
and normal volumes depends on the volumes’ emulation type. For details, see Table 3.

Table 3 Movability of volumes in pairs consisting of CV and normal values

Source volume Target volume

Normal volume
(not OPEN-V)

Normal volume
(OPEN-V)

CV
(not OPEN_V)

CV
(OPEN-V)

You cannot make pairs of the volumes.

Source volumes

The following describes whether volumes can be used as source volumes:

• Volumes set as command devices (reserved for use by hosts) cannot be used as source volumes.

• Volumes in an abnormal or inaccessible condition (for example, fenced) cannot be used as source

volumes.

• Volumes with Cache LUN data stored in cache cannot be used as source volumes.

• iSCSI volumes (volumes to which paths are defined from iSCSI ports) cannot be used as source

volumes.

• Volumes that HP StorageWorks Continuous Access XP Journal or Universal Replicator for z/OS uses as

a data or journal volume cannot be used as source volumes.

• Volumes reserved by a migration program other than Volume Migration cannot be used as source

volumes.

Normal volume
(not OPEN-V)

Movable — Not movable —

— Movable — Movable

Not movable — Movable —

— Movable — Movable

Normal volume
(OPEN-V)

CV
(not OPEN-V)

CV
(OPEN-V)

Auto LUN XP user guide for the XP1024/XP128 15

• Continuous Access. If the status of a HP StorageWorks Continuous Access XP volume is PSUS, PSUE, or

SMPL, the volume can be used as a source volume. If not, the volume cannot be used as a source
volume. When a Continuous Access XP pair is deleted from the main control unit (MCU), the status of
both volumes changes to SMPL, and both volumes can be used as source volumes. When a Continuous
Access XP pair is deleted from the remote control unit (RCU), the status of the P-VOL changes to PSUS,
the status of the S-VOL changes to SMPL, and both volumes can be used as source volumes.

• Business Copy. Using a BC volume as a source volume depends on the status and cascade

configuration of the volume. If the status of a BC volume is not split-pending COPY(SP) or PSUS(SP), the
volume can be used as a source volume. If the status is COPY(SP) or PSUS(SP), the volume cannot be
used as a source volume. This applies to cascaded and non-cascaded volumes.

Table 4 shows which non-cascaded volumes can be used as source volumes.

Table 4 Non-cascaded volumes that can be used as source volumes

Pair configuration Use P-VOL as source volume Use S-VOLs as source volumes

Ratio of P-VOL to S-VOLs is 1:1 Yes Yes

Ratio of P-VOL to S-VOLs is 1:2 Yes Yes

Ratio of P-VOL to S-VOLs is 1:3 No Yes

Table 5 shows which cascaded volumes can be used as source volumes.

Table 5 Cascaded volumes that can be used as source volumes

Pair Configuration Use P-VOL as source volume Use S-VOLs as source volumes

L1 pair, ratio of P-VOL to S-VOLs is 1:1 Yes Yes

L1 pair, ratio of P-VOL to S-VOLs is 1:2 Yes Yes

L1 pair, ratio of P-VOL to S-VOLs is 1:3 No Yes

L2 pair, ratio of P-VOL to S-VOLs is 1:1 Yes No

L2 pair, ratio of P-VOL to S-VOLs is 1:2 No No

If any of the following operations are performed on an Auto LUN XP source volume during migration, the
Auto LUN XP volume migration process stops:

• Continuous Access XP operations that change the volume status to something other than PSUS, PSUE, or

SMPL

• BC operations that change the volume status to COPY(SP) or PSUS(SP)

• Continuous Access XP Journal operations

LUSE source volumes

To specify a LUSE source volume for migration, specify individual LDEVs within the LUSE volume (for
example, LDEVs with high usage). Auto LUN XP migrates only specified LDEVs. If needed, specify all LDEVs
of the LUSE volume to relocate the entire LUSE volume. In this case, ensure that the required reserved target
LDEVs are available.

Target volumes

Target volumes must be reserved prior to migration. Hosts cannot access reserved volumes. The following
volumes cannot be reserved:

• Logical Unit Size Expansion (LUSE) volumes

• Volumes set as command devices

• Volumes assigned to BC or Continuous Access XP pairs

• Volumes reserved for BC operations

• Volumes with Cache LUN data stored in cache

• iSCSI volumes (for example, volumes to which paths are defined from iSCSI ports)

• Volumes in abnormal or inaccessible conditions (for example, fenced)

16 Auto LUN XP for the XP1024/XP128

• Volumes Continuous Access XP Journal uses

• Volumes specified with the Read Only or Protect attribute

• Volumes that Volume Security disabled for use as secondary volumes

• Volumes that LUN Security XP Extension specified as Read Only or Protect or disabled for use as

secondary volumes

• Volumes reserved by a migration program other than Volume Migration

Number of volumes

In manual migrations, the number of migration plans that can be executed concurrently might be restricted,
depending on use of other Command View XP or XP Remote Web Console programs and emulation types
and sizes of migrated volumes. Therefore, the number of migration plans that can be executed concurrently
is not constant.

A maximum of 36 Auto LUN XP copy operations can be requested at the same time. Auto LUN XP performs
migration operations sequentially (one volume at a time).

The maximum number of Auto LUN XP copy operations plus BC pairs is 1024.

Auto migration planning

Auto LUN XP will not plan an auto migration when:

• There is no reserve volume with the same emulation type and capacity as the source volume in the

same or next higher/lower HDD class (auto migration is performed only between consecutive classes or
within the same class)

• Auto LUN XP cannot estimate the usage rate for the target parity group because of some condition (for

example, invalid monitor data)

• The estimated usage of the target parity group or volume is over the user-specified maximum disk usage

value for that HDD class

• The estimated performance improvement is not large enough

Auto migration execution

Auto LUN XP will not execute an auto migration operation when:

• The current usage (last 15 minutes) of the source or target parity group or volume is over the maximum

disk usage rate for auto migration

• The current write pending rate for the disk array is 60% or higher

Manual migration execution

Auto LUN XP will execute a manual migration operation when the current write pending rate for the disk
array is 60% or higher.

Maintenance

Do not perform Auto LUN XP migration operations during disk array maintenance activities (for example,
cache or drive installation, replacement, or de-installation).

Auto migration parameters

Auto migration parameters are initialized when the disk array configuration is changed (for example,
when new drives or LDEVs are installed). Parameters include disk usage limit and migration time. After a
change is made to the subsystem configuration, you must specify auto migration parameters again.

Powering off disk arrays

To turn the power off at the disk array, ensure that volume migration is finished. If migration is not finished,
HP strongly recommends that you do not turn off the power until the migration is finished.

If you turn the power off while migration is in progress, data migration stops and some of the data are not
migrated. If you turn the power on later, Auto LUN XP resumes data migration. If data remains in shared
memory, which is volatile memory, Auto LUN XP attempts to copy only data that have not been migrated to
the migration destination. However, if data is lost from shared memory, Auto LUN XP attempts to copy all

Auto LUN XP user guide for the XP1024/XP128 17