HP - LUNConfig - xp12000UG Rootsan Technologies PVT LTD

HP StorageWorks
LUN Configuration and Security Manager XP

user guide
for the XP12000/XP10000/SVS200
LUN Manager
Volume Manager
Part number: T1714-96008

Fifth edition: June 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.
Compaq Tru64 UNIX is a registered trademark or trademark of Compaq.
LightPulse is a trademark of Emulex Corporation.
AIX, S/390, FICON, ESCON, and z/OS are registered trademarks or trademarks of International Business Machines Corporation.
Java, Java Runtime Environment™ (JRE), Java Virtual Machine (JVM), Solaris and SPARC are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States and other countries.
Microsoft, Internet Explorer, Windows NT, and Windows 2000 are registered trademarks or trademarks of Microsoft Corporation.
UNIX SVR4 MP-RAS is a registered trademark or trademark of NCR Corporation.
NetWare is a registered trademark or trademark of Novell, Inc.
HP-UX is a product name of Hewlett-Packard Company.
Netscape and Netscape Navigator is a registered trademark of Netscape Communications Corporation in the United States and other countries.
LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200
Contents
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part 1: LUN Configuration and Security Manager XP – LUN Manager

1 Overview of LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring LU paths in Fibre Channel environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring LU paths in iSCSI environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring LU paths in NAS environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuring LUN security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring LUs for use by RAID Manager XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Fibre Channel ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Fibre Channel topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Fibre Channel port addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Data transfer speed for Fibre Channel ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Standard, High Speed, and Initiator/External MIX modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
iSCSI port and iSNS server settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Status of connections between hosts and the array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
User authentication (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
User authentication operations and settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Authentication of hosts (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Authentication of Fibre Channel switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Authentication of ports (performing mutual authentication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
User authentication (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
User authentication operations and settings (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Authentication of hosts (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Authentication of iSCSI targets (performing mutual authentication) . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
NAS channel adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2 Preparing to use LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

System requirements . . . . . . . . . . . . ............................................. .. . . 53
Configuring WWW client computers ............................................. .. . . 53
Enabling required software . . . . . . . ............................................. .. . . 53
Notes on using LUN Manager . . . . . ............................................. .. . . 53
3 LUN Manager panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

LUN Manager pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 55
LU Path tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 56
Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 56
NAS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 57
iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 58
LU Path table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 58
Lower-left list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 59
WWN name table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 60
iSCSI name table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . .. .. . .. .. . ........ . 60
LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200 3
LDEV table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 60
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 61
Port pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 62
Package tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 63
Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 64
iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 64
NAS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 64
Port table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 64
iSCSI Function box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 66
Change Port Mode box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 66
CHN list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 67
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 68
Authentication pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 68
Port tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 70
Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 70
iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 71
Port Information list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 71
FC Switch Information list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
Authentication information (Target) list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
Authentication Information (Host) list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 72
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 73
4 LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Starting LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defining LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Creating host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Creating host groups (when configuring Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . 75
Creating iSCSI targets (when configuring iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Registering hosts in host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Registering hosts in host groups (when configuring Fibre Channel environments) . . . . . . . . . . . . . . 79
Registering hosts in iSCSI targets (when configuring iSCSI environments) . . . . . . . . . . . . . . . . . . . . 81
Associating host groups or iSCSI targets to logical volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Changing or viewing LU path settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Deleting LU paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Changing a host group’s name and host mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Changing an iSCSI target’s name and host mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Deleting host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Deleting iSCSI targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Initializing host group 0 (zero) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Initializing iSCSI target 0 (zero). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Changing a host bus adapter’s WWN and nickname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Changing a host bus adapter’s iSCSI name and nickname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Deleting host bus adapters from host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Deleting host bus adapters from iSCSI targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Deleting unneeded WWNs from the WWN name table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Deleting (initializing) unneeded iSCSI names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing a list of concatenated parity groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Defining and viewing alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Copying paths from one Fibre Channel or iSCSI port to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Copying paths from one NAS port to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Copying paths from a Fibre Channel or iSCSI port to a NAS port . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Copying paths from a NAS port to a Fibre Channel or iSCSI port . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Viewing a list of alternate paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Using LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Enabling LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4
Disabling LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring arrays for using RAID Manager XP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Specifying logical devices as command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Protecting logical devices from RAID Manager XP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Defining remote command devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring Fibre Channel ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specifying Fibre Channel topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Addressing Fibre Channel ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specifying a Fibre Channel port’s data transfer speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Switching between Standard, High Speed, and Initiator/External MIX mode. . . . . . . . . . . . . . . . . . . 100
Making settings on iSCSI ports and iSNS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Making settings on iSCSI ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Making settings on iSNS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Checking the status of the connection between hosts and the array (iSCSI environments only) . . . . . . . . . 103
Setting user authentication (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Enabling and disabling authentication of hosts in host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Registering a host’s user information on a host group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Changing a host’s user information (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Deleting a host’s user information (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Specifying a host group’s user information (when performing mutual authentication) . . . . . . . . . . . . . 107
Clearing a host group’s user information (when performing mutual authentication). . . . . . . . . . . . . . . 107
Settings and connection results in authentication of hosts (Fibre Channel environments) . . . . . . . . . . . 107
Settings and connection results in authentication of Fibre Channel switches . . . . . . . . . . . . . . . . . . . . 108
Specifying a Fibre Channel port’s information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Registering a Fibre Channel port’s user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Registering a Fibre Channel switch’s user information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Clearing a Fibre Channel switch’s user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Specifying a Fibre Channel switch’s authentication mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Specifying whether a Fibre Channel switch can perform authentication . . . . . . . . . . . . . . . . . . . . . . 111
Setting user authentication (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Enabling and disabling authentication of hosts on iSCSI targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Registering a host’s user information on an iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Changing a host’s user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Deleting a host’s user information (iSCSI environments). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Specifying an iSCSI target’s user information (when performing mutual authentication). . . . . . . . . . . . 115
Clearing an iSCSI target’s user information (when performing mutual authentication) . . . . . . . . . . . . . 116
Settings and connection results in authentication of hosts (iSCSI environments). . . . . . . . . . . . . . . . . . 116
Operating NAS channel adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Restarting a NAS channel adapter’s OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Stopping a NAS channel adapter’s OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Starting a NAS channel adapter’s OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5 Troubleshooting LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Contacting you HP account support representative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6 Finding an open-system host’s World Wide Name (WWN). . . . . . . . . . . . . . . . . . . . . 121

Finding WWNs in Windows NT or Windows 2000 environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Finding WWNs in Sun Solaris environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Finding WWNs in AIX, SGI Irix, or Sequent environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Finding WWNs in HP-UX environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Part 2: LUN Configuration and Security Manager XP – Volume Manager

7 Overview of Volume Manager and Custom Volume Size. . . . . . . . . . . . . . . . . . . . . . . 127
Overview of Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . .. . .. .. . . . . . . . . . . . . . . . . . . . . .. 127
Volume Manager function. . . . . . . . . . . . . . . . . . . . . . . . . .. . .. .. . . . . . . . . . . . . . . . . . . . . .. 127
Volume Manager guidelines . . . . . . . . . . . . . . . . . . . . . . . .. . .. .. . . . . . . . . . . . . . . . . . . . . .. 128
Volume Manager operations using a path-defined LDEV . .. . .. .. . . . . . . . . . . . . . . . . . . . . .. 129
Overview of Custom Volume Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
CVS function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Parity group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Volume to Space function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Install CV function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Calculating CV capacity for mainframe systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Calculating CV capacity for open systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
If the emulation type is OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
If the emulation type is other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Volume Initialize and Make Volume functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
SSID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Requirements for CU groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8 Preparing to use Volume Manager or Custom Volume Size. . . . . . . . . . . . . . . . . . . . . 141

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 141
Command View XP or XP Remote Web Console requirements . . . . . . . . . . . . . . .. .. . .. .. ...... 141
Installing Volume Manager and CVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 141
Connecting to the array. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 141
Starting Volume Manager and CVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 141
Changing to Modify mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 142
9 Volume Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Volume Manager panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Volume Manager main pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
LDEV Information tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
LDEV Information table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Capacity Unit box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Selected LDEVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Select an LDEV list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Volume Count list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Free LDEVs table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Expanded LDEVs list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Volume Manager operations shortcut menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Set LUSE Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Release LUSE Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Reset LUSE Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Concatenation List pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Volume Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Preparing to use Volume Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Volume Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Viewing LUSE configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Viewing concatenated parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Creating LUSE volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Creating LUSE volumes using the Volume Count list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Creating LUSE volumes using the Select an LDEV list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Creating LUSE volumes using the LDEV information table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Releasing LUSE volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Changing LUSE capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Resetting unregistered LUSE volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10Custom Volume Size operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Custom Volume Size panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Customized Volume pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Parity Group - LDEV tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Capacity Unit list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Parity Group - LDEV table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Progress bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Volume to Space Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6
Install CV pane (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Install CV pane (1) for OPEN-V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Install CV pane (1) for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Install CV pane (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Install CV pane (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Install CV pane (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Make Volume pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Make Volume pane (1) for OPEN-V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Make Volume Pane (1) for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Make Volume pane (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Make Volume pane (3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Make Volume pane (4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Volume Initialize pane (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Concatenation List pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Format All pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Write to Control Blocks pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Performing Custom Volume Size operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Before starting CVS operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CVS operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Viewing current CVS configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Viewing concatenated parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Converting logical volumes to space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Creating CVS volumes (Install CV operation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Deleting CVS volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Converting CVs back to FVs (Volume Initialize operation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Re-creating CVs after initializing the VDEV (Make Volume operation) . . . . . . . . . . . . . . . . . . . . . . . . 185
Formatting LDEVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Making external mainframe volumes usable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
11Troubleshooting Volume Manager and Custom Volume Size . . . . . . . . . . . . . . . . . . . . 191

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figures
1 Array integrating Fibre Channel, iSCSI, and NAS environments . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 LU path configuration in Fibre Channel environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 LU path configuration in iSCSI environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 LU path configuration in NAS environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5 Enabling LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6 Disabling LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7 FC-AL and Point-to-point topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8 Ports in High Speed or Initiator/External MIX mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9 Authentication of hosts (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
10 Example of authentication of hosts (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
11 Authentication of Fibre Channel switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12 Authentication of hosts (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
13 Example of authentication of hosts (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
14 LUN Manager pane (icon under Fibre folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
15 LUN Manager pane (icon under iSCSI folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
16 Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17 NAS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
18 iSCSI folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
19 WWN name table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
20 iSCSI name table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
21 Port pane (icon under Fibre folder selected). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
22 Port pane (icon under iSCSI folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
23 Port pane (icon under NAS folder selected). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
24 Port table (Fibre Channel ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
25 Port table displaying (iSCSI ports and iSNS servers). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
26 iSCSI Function box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
27 Change Port Mode box (Fibre Channel ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
28 Change Port Mode box (iSCSI port and iSNS server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
29 CHN list (NAS channel adapters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
30 Authentication pane (Fibre folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
31 Authentication pane (port icon under Fibre folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
32 Authentication pane (icon under iSCSI folder selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
33 Fibre folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
34 iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
35 Add New Host Group pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
36 Add New Host Group pane (Option selected). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
37 Add New iSCSI Target pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
38 Add New iSCSI Target pane (Option selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
39 Add New WWN dialog box (when registering a host that was previously connected to the array) . . . 80
40 Add New WWN dialog box (registering a host that has never been connected to the array) . . . . . . . 81
41 Add New iSCSI name pane (registering a host that was previously connected to the array) . . . . . . . . 82
42 Add New iSCSI name pane (registering a host that has never been connected to the array) . . . . . . . . 82
43 Information about LU paths to be defined (Fibre Channel environment). . . . . . . . . . . . . . . . . . . . . . . 84
44 Information about LU paths to be defined (iSCSI environment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
45 Information about LU paths to be deleted (Fibre Channel environments) . . . . . . . . . . . . . . . . . . . . . . 85
46 Information about LU paths to be deleted (iSCSI environments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
47 Change Host Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
48 Change Host Group dialog box (Option selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
49 Change iSCSI Target pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
50 Change iSCSI Target pane (Option selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
51 Change WWN & Nickname dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
52 Check WWNs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
53 Change iSCSI name & Nickname pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
54 Check iSCSI names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
55 Concatenation List pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
56 Alternate Paths pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
57 Register Ports to iSNS Server pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
58 Delete Ports from iSNS Server pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
59 Result of Registration to iSNS Server pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
60 Result of Deletion from iSNS Server pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
61 Ping pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
62 Ping Status pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
63 Add New User Information (Host) pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
64 Change User Information (Host) pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
65 Delete Authentication Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
66 Specify Authentication Information pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
67 Set Port Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
68 Default Setting(User Name/Secret) pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
70 Clear Authentication Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
71 Add New User Information (Host) pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
72 Change User Information (Host) pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
73 Delete Authentication Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
75 LightPulse Utility/NT pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
76 Sun Solaris World Wide Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
77 HP-UX World Wide Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
78 LUSE configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
79 Overview of Volume Initialize function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
80 Overview of Make Volume function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
81 Parity group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
82 Virtual CVS volume configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
83 Icons showing Unlocked status and View mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8
84 Mode changing confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
85 Icons showing Locked status and Modify mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
86 Volume Manager pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
87 Volume Manager operations shortcut menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
88 Set LUSE Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
89 Release LUSE Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
90 Reset LUSE Confirmation pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
91 Concatenation List pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
92 Customized Volume pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
93 Volume to Space Confirmation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
94 Install CV pane (1) for OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
95 Install CV pane (1) for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
96 Install CV pane (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
97 Install CV pane (3) for setting SSIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
98 Install CV pane (4) for confirming Install CV settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
99 Make Volume pane (1) for OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
100 Make Volume pane (1) for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
101 Make Volume pane (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
102 Make Volume pane (3) for setting SSIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
103 Make Volume pane (4) for confirming Make Volume settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
104 Volume Initialize pane (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
105 Volume Initialize pane (2) for setting SSIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
106 Volume Initialize pane (3) for confirming Volume Initialize settings . . . . . . . . . . . . . . . . . . . . . . . . 178
107 Concatenation List pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
108 Format All pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
109 Write to Control Blocks pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Tables
1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Available addresses for Fibre Channel ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3 Port serial numbers and names (4-port channel adapters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4 Port serial numbers and names (8-port channel adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Port serial numbers and names (16-port channel adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6 Port serial numbers and names (XP10000/SVS200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7 Fibre Channel port icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8 NAS port icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
9 iSCSI port icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10 LUN status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
11 LDEV status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
12 Channel adapter and port block icons (Fibre folder). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
13 Channel adapter package icons (iSCSI folder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
14 Fibre Channel port and Fibre Channel host group icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
15 iSCSI port and iSCSI target status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
16 Host modes for host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
17 Host mode options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
18 Combinations of port settings and connection results (Fibre Channel environments) . . . . . . . . . . . . . . 109
19 Combinations of Fibre Channel settings and connection results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
20 Combinations of port settings and connection results (iSCSI environments) . . . . . . . . . . . . . . . . . . . . 118
21 Troubleshooting LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
22 Creating CVS volumes using Install CV (for OPEN-V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
23 CVS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
24 CV capacity by emulation type (mainframe systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
25 CV capacity by emulation type (open systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
26 Management area capacity of mainframe volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
27 Management area capacity of open-system volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
28 Boundary value for RAID levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
29 Slot capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
30 Settings for the Make Volume operation (OPEN-V only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
31 SSID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
32 LDEV status icons . . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 145
33 Parity group status icons . . . . . . . . . . . . . . .. . .. .................................. . 158
34 VDEV status icons . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 158
35 LDEV status icons . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 159
36 Volume status . . . . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 159
37 Volume attributes . . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 159
38 Emulation groups . . . . . . . . . . . . . . . . . . . .. . .. .................................. . 165
39 Set SSID tree icons (Install CV) . . . . . . . . . . .. . .. .................................. . 166
40 Set SSID tree icons (Make Volume) . . . . . . . .. . .. .................................. . 173
41 Set SSID tree icons (Volume Initialize). . . . . . .. . .. .................................. . 177
10
About this guide
This guide describes how to set up, use, and troubleshoot two LUN management products:
• LUN Manager (Part 1)
• Volume Manager (Part 2)
Supported storage platforms and firmware

In this guide, the term array refers to the following storage platforms:
• HP StorageWorks XP12000 Disk Array
• HP StorageWorks XP10000 Disk Array
• HP StorageWorks 200 Storage Virtualization System
For information about required firmware versions, see the HP StorageWorks XP Remote Web Console user
guide for XP12000/XP10000/SVS200.
Intended audience
This guide is intended for customers and HP-authorized service providers with knowledge of:
• Disk array hardware and software
• Data processing and RAID storage subsystems and their basic functions
NOTE: The functions described in this manual may be limited, depending on your assigned level of user
access. Some users will have read-only access while others will have limited or full array access. For
additional information on users and user groups, please see the HP StorageWorks XP Remote Web
Console user guide for XP12000/XP10000/SVS200.
Prerequisites
Prerequisites for using this product include:
• Installing the HP StorageWorks disk array(s)
• Installing the license key for this product
Related documentation
The following documents provide related information:
• HP StorageWorks XP glossary
• HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200
• HP StorageWorks External Storage XP user guide
• HP StorageWorks LUN Security XP Extension user guide
• HP StorageWorks Snapshot XP user guide
• 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 1 Document conventions
Convention Element
Blue text: Table 1 Cross-reference links and e-mail addresses
Blue, underlined text: (http://www.hp.com) Web site addresses
Bold text • 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 items, buttons, and check boxes
Italic text Text emphasis
Monospace text • File and directory names

• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text • Code variables
• Command variables
Monospace, bold text Emphasized monospace 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
• Error messages
• Operating system type and revision level
• Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
Subscription service
HP recommends that you register your product at the Subscriber’s Choice for Business web site:
http://www.hp.com/go/e-updates.
12
After registering, you will receive e-mail notification of product enhancements, new driver versions,
firmware updates, and other product resources.
HP web sites
For additional information, see the following HP web sites:
• http://www.hp.com
• http://www.hp.com/go/storage
• http://www.hp.com/service_locator
• http://www.hp.com/support/manuals
• http://www.hp.com/support/downloads
• http://www.hp.com/support/rwc/manuals
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to
[email protected]. All submissions become the property of HP.
14
Part 1: LUN Configuration and Security Manager XP –
LUN Manager
16
1 Overview of LUN Manager
The XP12000/XP10000/SVS200 arrays integrate the following storage environments to provide
advanced storage solutions:
• Fibre Channel: Fibre Channel is a protocol that enables fast data transfers and can be used for
configuring a storage area network (SAN). To use an array as SAN storage, you should attach host
servers to the array’s Fibre Channel ports.
• iSCSI: internet Small Computer System Interface (iSCSI) is a protocol that enables data transfers
between host computers and large-scale storage devices over an Internet Protocol (IP) network and is
suitable for data transfers between remote locations. To use an array as IP storage, you should attach
host servers to the array’s iSCSI ports.
In an iSCSI environment, the array provides mutual user authentication between hosts and ports using
Challenge Handshake Authentication Protocol (CHAP).
NOTE:
• iSCSI environments that you create with LUN Manager support local connections (that is, hosts
in the same domain can communicate with each other), but neither support inter-domain
connections or external LAN connections.
• When configuring iSCSI environments, you must confirm the operating systems used to run
hosts in the IP network. You can configure iSCSI networks only when each host runs on the
Windows Server 2003, Windows 2000®, or HP-UX 11i operating system. However, user
authentication is not available on hosts running on HP-UX 11i.
• You can connect switching hubs to iSCSI ports, but cannot connect other network relay devices
to iSCSI ports.
• NAS: NAS is a type of storage device attached to a LAN. NAS contains an embedded operating
system and file system to enable file sharing by multi-platform host servers. To use an array as a NAS
storage, you should attach host servers to the array’s NAS ports.
Figure 1 Array integrating Fibre Channel, iSCSI, and NAS environments
You can connect the array to open-system server hosts on different platforms (for example, UNIX and PC
servers). To configure a system that includes open-system hosts and an array, you must use LUN Manager
to configure logical volumes and ports.
One of the important tasks with logical volume configuration is to define I/O paths from hosts to logical
volumes. If paths are defined, hosts can send commands and data to logical volumes and receive data
from logical volumes.
After the system begins operating, you might need to modify the system configuration. For example, if you
add hosts or disks, you must add I/O paths. Even when the system is operating, you can use LUN
Manager to modify the system configuration. You do not need to reboot the system when changing the
system configuration.
NOTE: Throughout this user guide, logical volumes are sometimes referred to as logical devices (LDEVs).
Configuring LU paths
Use LUN Manager to make various settings for logical volumes (LUs), including LU path settings. When
you configure a system, you must define LU paths to let hosts transfer data to and from storage.
CAUTION: When defining LU paths, you must not use RAID Manager XP and XP Remote Web Console
at the same time.
Configuring LU paths in Fibre Channel environments

After open-system hosts and the array are physically connected by cables, hubs, and so on, you must use
LUN Manager to establish I/O paths between the hosts and logical volumes. This defines which host can
access which logical volume. Logical volumes that open-system hosts can access are referred to as logical
units (LUs). Paths between open-system hosts and LUs are referred to as LU paths.
Before defining LU paths, you must classify server hosts by host groups. For example, if Linux and
Windows hosts are connected to the array, you must create one host group for Linux hosts and another
host group for Windows hosts. Then you must register the host bus adapters for Linux hosts in the Linux
host group. You must also register the host bus adapters for Windows hosts in the Windows host group.
Host groups can contain only hosts connected to the same port, and cannot contain hosts connected to
different ports. For example, if two Windows hosts are connected to port 1A and three Windows hosts
are connected to port 1B, you cannot register all five Windows hosts in one host group. You must register
the first two Windows hosts in one host group and register the remaining three Windows hosts in another
host group.

After classifying server hosts into host groups, you must associate the host groups to logical volumes. In
Figure 2, the hg-lnx host group is associated with three logical volumes (00:00, 00:01, and 00:02). LU
paths are defined between the two hosts in the hg-lnx host group and the three logical volumes.
Figure 2 LU path configuration in Fibre Channel environments

Use LUN Manager to define paths between a single server host and multiple LUs. In Figure 2, both hosts
in the hg-lnx host group can access the three LUs.
Use LUN Manager to define paths between multiple server hosts and a single LU. In Figure 2, the LU
identified by CU-LDEV number 00:00 is accessible from both hosts belonging to the hg-lnx host group.
In Figure 2, LUs associated with the hg-lnx host group are addressed by numbers 0000 to 0002. The LU’s
address number is referred to as the logical unit number (LUN). When Continuous Access XP and other
optional programs manipulate LUs, the programs use LUNs to specify the LUs to be manipulated.
You can add, change, and delete LU paths when the system is operating. For example, if you add new
disks or server hosts to the array, you can add new LU paths. If you replace an existing server host, you
can delete LU paths corresponding to the host before replacing the host. You do not need to restart the
system when you use LUN Manager to add, change, and delete LU paths.
If a hardware failure (such as a CHA failure) occurs, some LU paths might be disabled and some I/O
operations might be stopped. To avoid this situation, the system administrator can define alternate LU
paths. If one LU path fails, the alternate path takes over the host I/O.
For more information, see:
• ”Defining LU paths” on page 75
• ”Changing or viewing LU path settings” on page 84
• ”Defining and viewing alternate paths” on page 93.
NOTE:
• In Fibre Channel environments, you can define up to 1,024 LU paths for one host group and up to
1,024 LU paths for one port.
• You cannot define LU paths to LUN On-Demand volumes.
• You cannot define LU paths to volumes reserved by Auto LUN XP.
• You can create up to 255 host groups for one Fibre Channel port.
• You cannot define LU paths to journal volumes.
• You cannot define LU paths to pool volumes.
Configuring LU paths in iSCSI environments

After open-system hosts and the array are physically connected by cables, hubs, and so on, you must use
LUN Manager to establish I/O paths between the hosts and logical volumes. This defines which host can
access which logical volume. Logical volumes that open-system hosts can access are referred to as logical
units (LUs). Paths between open-system hosts and LUs are referred to as LU paths.
Before defining LU paths, you must classify server hosts by iSCSI targets. For example, if Linux and
Windows hosts are connected to the array, you must create one iSCSI target for Linux hosts and another
iSCSI target for Windows hosts. Then you must register the host bus adapters for Linux hosts in the Linux
iSCSI target. You must also register the host bus adapters for Windows hosts in the Windows iSCSI
target.
iSCSI targets can contain only hosts connected to the same port, and cannot contain hosts connected to
different ports. For example, if two Windows hosts are connected to port 1A and three Windows hosts
are connected to port 1B, you cannot register all five Windows hosts in one iSCSI target. You must
register the first two Windows hosts in one iSCSI target and register the remaining three Windows hosts
in another iSCSI target.

After classifying server hosts into iSCSI targets, you must associate the iSCSI targets to logical volumes. In
Figure 3, the hg-lnx iSCSI target is associated with three logical volumes (00:00, 00:01, and 00:02). LU
paths are defined between the two hosts in the hg-lnx iSCSI target and the three logical volumes.
Figure 3 LU path configuration in iSCSI environments

Use LUN Manager to define paths between a single server host and multiple LUs. In Figure 3, both hosts in
the hg-lnx iSCSI target can access the three LUs.
Use LUN Manager to define paths between multiple server hosts and a single LU. In Figure 3, the LU
identified by CU-LDEV number 00:00 is accessible from both hosts belonging to the hg-lnx iSCSI target.
In Figure 3, LUs associated with the hg-lnx iSCSI target are addressed by numbers 0 to 2. The LU’s address
number is referred to as a logical unit number (LUN). When Continuous Access XP and other optional
programs manipulate LUs, the programs use LUNs to specify the LUs to be manipulated.
You can add, change, and delete LU paths when the system is operating. For example, if you add new
disks or server hosts to the array, you can add new LU paths. If you replace an existing server host, you
can delete LU paths corresponding to the host before replacing the host. You do not need to restart the
system when you use LUN Manager to add, change, and delete LU paths.
If a hardware failure (such as a CHA failure) occurs, some LU paths might be disabled and some I/O
operations might be stopped. To avoid this situation, the system administrator can define alternate LU
paths. If one LU path fails, the alternate path takes over the host I/O.
• ”Defining LU paths” on page 75
• ”Changing or viewing LU path settings” on page 84
• ”Defining and viewing alternate paths” on page 93
For more information about LUN configuration, see ”Overview of Volume Manager and Custom Volume
Size” on page 127.
NOTE:
• In iSCSI environments, you can define up to 1,024 LU paths for one iSCSI target and up to 1,024 LU
paths for one port.
• You can create up to 64 iSCSI targets for one Fibre Channel port.
• You cannot define LU paths to journal volumes.
• You cannot define LU paths to pool volumes.
• In iSCSI environments, you cannot define LU paths to logical volumes that do not have the Read/Write
access attribute.
• You cannot define LU paths to volumes on which a volume management area (VMA) is set.
Configuring LU paths in NAS environments

In Fibre Channel or iSCSI environments, you must classify hosts into host groups based on the platform. In
NAS environments, however, you do not need to classify hosts. In NAS environments, hosts attached to a
NAS port are automatically registered in a host group named User.
In NAS environments, LUs are classified into system LUs or user LUs. System LUs contain system
information necessary for managing the NAS environment and can be manipulated only by HP service
representatives. User LUs contain data that can be accessed by network users. When configuring NAS
systems, you must define paths between hosts and user LUs.
Figure 4 gives an example of defining paths between hosts and user LUs. In NAS environments, paths are
always defined between a user LU and a group of four ports. Because of this multi-path configuration,
hosts can access the user LU even if one of the paths fails.
NOTE:
• In NAS environments, you can define up to 256 LU paths for one NAS port.
• In NAS environments, you cannot define LU paths to logical volumes that do not have the Read/Write
or Read/Write (S-VOL Disable) access attribute.
• The LUN Manager pane displays two host groups (that is, User and NAS-Sys) below each NAS port.
When defining LU paths, you can use only User; you cannot use NAS-Sys.
• You cannot define LU paths to volumes on which a volume management area (VMA) is set.
• You cannot define LU path to journal volumes.
• You cannot define LU path to virtual volumes.

• You cannot define LU path to pool volumes.
Figure 4 LU path configuration in NAS environments
Configuring LUN security

To protect mission-critical data in the array from illegal access, you must apply security policies to logical
volumes. Use LUN Manager to enable LUN security on ports to safeguard LUs from illegal access.
NOTE:
• You cannot apply LUN security to NAS ports.
• If a port has the External attribute, you cannot apply LUN security to the port.
If LUN security is enabled, host groups affect which host can access which LUs. Hosts can only access LUs
associated with the host group the hosts belong to. Hosts cannot access LUs associated with other host
groups. For example, hosts in the hp-ux host group cannot access LUs associated with the Windows host
group. Also, hosts in the Windows host group cannot access LUs associated with the hp-ux host group.
In Figure 5, LUN security is enabled on port CL1-A. The two hosts in the hp-lnx host group can only access
LUs 00:00, 00:01, and 00:02. The two hosts in the hg-hpux host group can only access LUs 02:01 and
02:02. The two hosts in the hg-solar host group can only access LUs 01:05 and 01:06.
Figure 5 Enabling LUN security

Usually, you do not need to disable LUN security on ports. If LUN security is disabled on a port,
connected hosts can only access LUs associated with host group 0, and cannot access LUs associated
with any other host groups.
Figure 6 Disabling LUN security

Host group 0 is the only host group reserved for each port by default. If you use the LUN Manager pane
to view a list of host groups in a port, host group 0 usually appears at the top of the list and is indicated
by 00 (see Figure 2).
NOTE: By default, the name of host group 0 consists of the port name, a hyphen, and 00. For example,
host group 0 for port 1A is named 1A-G00 by default. You can change the name of host group 0.
By default, LUN security is disabled on each port. When you configure the system, you must enable LUN
security on each port to which hosts are connected.
For more information, see ”Using LUN security” on page 96.

Configuring LUs for use by RAID Manager XP
System administrators can enter RAID Manager XP commands from open-system hosts to perform
Continuous Access XP and Business Copy XP operations on logical devices. For example, administrators
can enter RAID Manager XP commands to create or split pairs. To allow administrators to use RAID
Manager XP commands, you must ensure that at least one logical device is used as a command device. A
command device receives RAID Manager XP commands entered from open-system hosts. When the
administrator enters a RAID Manager XP command from an open-system host, the RAID Manager XP
command is transferred via the command device to the target logical device.
To protect a logical device from RAID Manager XP commands, you must apply command device security
to the logical device. If command device security is applied to a logical device, the device is not affected
by RAID Manager XP commands even when commands are transferred via a command device to that
device.
For more information, see ”Configuring arrays for using RAID Manager XP commands” on page 97.
NOTE: You cannot use the following volumes as command devices:

• Volumes that do not have the Read/Write access attribute
• Volumes reserved by Auto LUN XP
• Continuous Access XP volumes
• Business Copy XP volumes
• External LUs
• Volumes on which a VMA is set
• Virtual volumes
Fibre Channel ports

When configuring Fibre Channel environments, you must configure the Fibre Channel topology and set
addresses to the Fibre Channel ports.
You can optimize system performance by adjusting settings for the Fibre Channel ports. You can improve
system performance by adjusting the data transfer speed at Fibre Channel ports and changing the
channel adapter mode.
Fibre Channel topologies

The term topology indicates how devices are connected to each other. Fibre Channel provides the
following topologies:
• Fabric: Uses a fabric switch to connect a large number of devices (up to 16 million) together. Each
device has the full bandwidth of 100 MB/sec.
• FC-AL (Fibre Channel-Arbitrated Loop): A shared interface that can connect up to 126 devices
(AL-ports) together. The 100 MB/sec bandwidth is shared among devices connected to each other.
• Point-to-point: The simplest fibre topology directly connects two devices together.
Figure 7 FC-AL and Point-to-point topologies

When configuring the system, use the LUN Manager pane to specify whether the hosts and array are
connected by a fabric switch.
If you use a fabric switch, you must specify FC-AL or point-to-point in the LUN Manager pane (by default,
FC-AL is specified). If you use a fabric switch, see the fabric switch’s documentation to learn whether you
should use FC-AL or point-to-point. Some fabric switches require that you specify point-to-point to get the
system running.
If you are not using a fabric switch, you must specify FC-AL. For more information, see ”Specifying Fibre
Channel topologies” on page 99.
Fibre Channel port addresses

When configuring the system, you must set addresses for Fibre Channel ports. When addressing Fibre
Channel ports, you can use the AL-PA (arbitrated-loop physical address) or loop ID as the address (see
Table 2).
For more information, see ”Addressing Fibre Channel ports” on page 99.
Table 2 Available addresses for Fibre Channel ports
Port Loop ID Port Loop ID Port Loop ID Port Loop ID

address address address address
(AL-PA) (AL-PA) (AL-PA) (AL-PA)
EF 0 B2 32 72 64 3A 96
E8 1 B1 33 71 65 39 97
E4 2 AE 34 6E 66 36 98
E2 3 AD 35 6D 67 35 99
E1 4 AC 36 6C 68 34 100

Table 2 Available addresses for Fibre Channel ports (continued)
Port Loop ID Port Loop ID Port Loop ID Port Loop ID

address address address address
(AL-PA) (AL-PA) (AL-PA) (AL-PA)
E0 5 AB 37 6B 69 33 101
DC 6 AA 38 6A 70 32 102
DA 7 A9 39 69 71 31 103
D9 8 A7 40 67 72 2E 104
D6 9 A6 41 66 73 2D 105
D5 10 A5 42 65 74 2C 106
D4 11 A3 43 63 75 2B 107
D3 12 9F 44 5C 76 2A 108
D2 13 9E 45 5A 77 29 109
D1 14 9D 46 59 78 27 110
CE 15 9B 47 56 79 26 111
CD 16 98 48 55 80 25 112
CC 17 97 49 54 81 23 113
CB 18 90 50 53 82 1F 114
CA 19 8F 51 52 83 1E 115
C9 20 88 52 51 84 1D 116
C7 21 84 53 4E 85 1B 117
C6 22 82 54 4D 86 18 118
C5 23 81 55 4C 87 17 119
C3 24 80 56 4B 88 10 120
BC 25 7C 57 4A 89 0F 121
BA 26 7A 58 49 90 08 122
B9 27 79 59 47 91 04 123
B6 28 76 60 46 92 02 124
B5 29 75 61 45 93 01 125
B4 30 74 62 43 94
B3 31 73 63 3C 95
Data transfer speed for Fibre Channel ports

As the system continues operating, you might notice that a larger amount of data is transferred at some
ports, but a smaller amount is transferred at other ports. If you set a faster data transfer speed for ports
where a larger amount of data is transferred, you can optimize system performance. If you set a slower
data transfer speed for ports where a smaller amount of data is transferred, you can also optimize
performance.
For more information, see ”Specifying a Fibre Channel port’s data transfer speed” on page 100.
Standard, High Speed, and Initiator/External MIX modes

Channel adapter boards have built-in ports used for connecting hosts and an array. Ports can be in
Standard, High Speed, or Initiator/External MIX mode, although all ports are in Standard mode by
default. If a port satisfies certain conditions, you can apply High Speed mode to improve port
performance. If a port satisfies certain conditions, you can apply Initiator/External MIX mode so that one
part can be used both as an initiator port for Continuous Access XP or Continuous Access XP Journal and
as an external port applied to a remote command device. For instructions on defining a remote command
device, see the HP StorageWorks External Storage XP user guide.
You must apply High Speed or Initiator/External MIX mode to groups of four ports, not to individual ports.
In LUN Manager terminology, each group of four ports is referred to as a port block. You can apply High
Speed or Initiator/External MIX mode to each port block.
When you apply High Speed or Initiator/External MIX mode, two of the four ports in a port block must
satisfy the following conditions. Also, the other two ports must satisfy the following conditions:
• The two ports have the same Fabric option (Enable or Disable).
• The two ports have FC-AL as the Connection option.
• The two ports use different port addresses and no matching addresses.
• When you apply High Speed mode, the two ports have the same port attribute (Initiator, RCU target,
or Target).
• When you apply Initiator/External MIX mode, one of the two ports takes the initiator attribute and the
other port takes the external attribute.
• Only one of the ports is used for connecting the host.
Figure 8 shows an example of High Speed or Initiator/External MIX mode applied to one or two port
blocks when the channel adapter board has eight ports. If the channel adapter board has 16 ports, you

can apply High Speed or Initiator/External MIX mode in the same way, even though there are four port
blocks.
Figure 8 Ports in High Speed or Initiator/External MIX mode

If High Speed mode is applied to the four ports in a port block, only two of the ports can be used for
connecting the host. These two ports can exclusively use channel processors and fibre optic processors
(FOPs) that would otherwise be reserved for the other two ports. Therefore, system performance improves.
By balancing workloads on processors, you can expect a greater improvement in system performance.
You cannot change Standard mode to High Speed mode or vice versa while you are online to the hosts.
You must reboot the hosts after changing the mode.
To change the configuration of a port being used, you must perform a backup operation before changing
the port configuration.
Port names can differ, depending on whether ports are in Standard, High Speed, or Initiator/External
MIX mode. For more information about port names, see Table 3, Table 4, Table 5, and Table 6.
For more information, see ”Switching between Standard, High Speed, and Initiator/External MIX mode”
on page 100.
NOTE:
• Sometimes Standard, High Speed, and Initiator/External MIX modes are collectively referred to as
Fibre PCB modes. PCB is an acronym for printed circuit board. The array documentation sometimes
uses the term PCB when referring to a channel adapter, which is a printed circuit board used for
connecting hosts and an array.
• Storage partition administrators cannot apply High Speed or Initiator/External MIX mode.
Table 3 Port serial numbers and names (4-port channel adapters)
Port serial Standard High Speed or Port serial Standard High Speed or
number mode1 Initiator/External number mode1 Initiator/External
MIX mode1 MIX mode1
0 CL1-A CL1-A 128 CL2-A CL2-A
1 CL3-A CL3-A [1-A 2nd] 129 CL4-A CL4-A [2-A 2nd]
2 – – 130 – –
3 – – 131 – –
4 – – 132 – –
5 – – 133 – –
6 – – 134 – –
7 – – 135 – –
8 CL1-C CL1-C 136 CL2-C CL2-C
9 CL3-C CL3-C [1-C 2nd] 137 CL4-C CL4-C [2-C 2nd]
10 – – 138 – –
11 – – 139 – –
12 – – 140 – –
13 – – 141 – –
14 – – 142 – –
15 – – 143 – –
16 CL1-E CL1-E 144 CL2-E CL2-E
17 CL3-E CL3-E [1-E 2nd] 145 CL4-E CL4-E [2-E 2nd]
18 – – 146 – –
19 – – 147 – –
20 – – 148 – –
21 – – 149 – –
22 – – 150 – –
23 – – 151 – –
24 CL1-G CL1-G 152 CL2-G CL2-G
25 CL3-G CL3-G [1-G 2nd] 153 CL4-G CL4-G [2-G 2nd]
26 – – 154 – –
27 – – 155 – –
28 – – 156 – –
29 – – 157 – –

Table 3 Port serial numbers and names (4-port channel adapters) (continued)
MIX mode1 MIX mode1
30 – – 158 – –
31 – – 159 – –
32 CL1-J CL1-J 160 CL2-J CL2-J
33 CL3-J CL3-J [1-J 2nd] 161 CL4-J CL4-J [2-J 2nd]
34 – – 162 – –
35 – – 163 – –
36 – – 164 – –
37 – – 165 – –
38 – – 166 – –
39 – – 167 – –
40 CL1-L CL1-L 168 CL2-L CL2-L
41 CL3-L CL3-L [1-L 2nd] 169 CL4-L CL4-L [2-L 2nd]
42 – – 170 – –
43 – – 171 – –
44 – – 172 – –
45 – – 173 – –
46 – – 174 – –
47 – – 175 – –
48 CL1-N CL1-N 176 CL2-N CL2-N
49 CL3-N CL3-N [1-N 2nd] 177 CL4-N CL4-N [2-N 2nd]
50 – – 178 – -
51 – – 179 – -
52 – – 180 – -
53 – – 181 – -
54 – – 182 – -
55 – – 183 – -
56 CL1-Q CL1-Q 184 CL2-Q CL2-Q
57 CL3-Q CL3-Q [1-Q 2nd] 185 CL4-Q CL4-Q [2-Q 2nd]
58 – – 186 – –
59 – – 187 – –
60 – – 188 – –
61 – – 189 – –
62 – – 190 – –
63 – – 191 – –
64 CL9-A CL9-A 192 CLA-A CLA-A
65 CLB-A CLB-A [9-A 2nd] 193 CLC-A CLC-A [A-A 2nd]
MIX mode1 MIX mode1
66 – – 194 – –
67 – – 195 – –
68 – – 196 – –
69 – – 197 – –
70 – – 198 – –
71 – – 199 – –
72 CL9-C CL9-C 200 CLA-C CLA-C
73 CLB-C CLB-C [9-C 2nd] 201 CLC-C CLC-C [A-C 2nd]
74 – – 202 – –
75 – – 203 – –
76 – – 204 – –
77 – – 205 – –
78 – – 206 – –
79 – – 207 – –
80 CL9-E CL9-E 208 CLA-E CLA-E
81 CLB-E CLB-E [9-E 2nd] 209 CLC-E CLC-E [A-E 2nd]
82 – – 210 – –
83 – – 211 – –
84 – – 212 – –
85 – – 213 – –
86 – – 214 – –
87 – – 215 – –
88 CL9-G CL9-G 216 CLA-G CLA-G
89 CLB-G CLB-G [9-G 2nd] 217 CLC-G CLC-G [A-G 2nd]
90 – – 218 – –
91 – – 219 – –
92 – – 220 – –
93 – – 221 – –
94 – – 222 – –
95 – – 223 – –
96 CL9-J CL9-J 224 CLA-J CLA-J
97 CLB-J CLB-J [9-J 2nd] 225 CLC-J CLC-J [A-J 2nd]
98 – – 226 – –
99 – – 227 – –
100 – – 228 – –
101 – – 229 – –

MIX mode1 MIX mode1
102 – – 230 – –
103 – – 231 – –
104 CL9-L CL9-L 232 CLA-L CLA-L
105 CLB-L CLB-L [9-L 2nd] 233 CLC-L CLC-L [A-L 2nd]
106 – – 234 – –
107 – – 235 – –
108 – – 236 – –
109 – – 237 – –
110 – – 238 – –
111 – – 239 – –
112 CL9-N CL9-N 240 CLA-N CLA-N
113 CLB-N CLB-N [9-N 2nd] 241 CLC-N CLC-N [A-N 2nd]
114 – – 242 – –
115 – – 243 – –
116 – – 244 – –
117 – – 245 – –
118 – – 246 – –
119 – – 247 – –
120 CL9-Q CL9-Q 248 CLA-Q CLA-Q
121 CLB-Q CLB-Q [9-Q 2nd] 249 CLC-Q CLC-Q [A-Q 2nd]
122 – – 250 – –
123 – – 251 – –
124 – – 252 – –
125 – – 253 – –
126 – – 254 – –
127 – – 255 – –
1. The hyphen (-) indicates that the port is not available.
Table 4 Port serial numbers and names (8-port channel adapter)
MIX mode1 MIX mode1
4 – – 132 – –
Table 4 Port serial numbers and names (8-port channel adapter) (continued)
MIX mode1 MIX mode1
5 – – 133 – –
6 – – 134 – –
7 – – 135 – –
12 – – 140 – –
13 – – 141 – –
14 – – 142 – –
15 – – 143 – –
20 – – 148 – –
21 – – 149 – –
22 – – 150 – –
23 – – 151 – –
28 – – 156 – –
29 – – 157 – –
30 – – 158 – –
31 – – 159 – –
36 – – 164 – –
37 – – 165 – –
38 – – 166 – –
39 – – 167 – –

MIX mode1 MIX mode1
44 – – 172 – –
45 – – 173 – –
46 – – 174 – –
47 – – 175 – –
52 – – 180 – –
53 – – 181 – –
54 – – 182 – –
55 – – 183 – –
60 – – 188 – –
61 – – 189 – –
62 – – 190 – –
63 – – 191 – –
66 CLD-A CLD-A 194 CLE-A CLE-A
67 CLF-A CLF-A [D-A 2nd] 195 CLG-A CLG-A [E-A 2nd]
68 – – 196 – –
69 – – 197 – –
70 – – 198 – –
71 – – 199 – –
74 CLD-C CLD-C 202 CLE-C CLE-C
75 CLF-C CLF-Q [D-C 2nd] 203 CLG-C CLG-C [E-C 2nd]
76 – – 204 – –
MIX mode1 MIX mode1
77 – – 205 – –
78 – – 206 – –
79 – – 207 – –
82 CLD-E CLD-E 210 CLE-E CLE-E
83 CLF-E CLF-E [D-E 2nd] 211 CLG-E CLG-E [E-E 2nd]
84 – – 212 – –
85 – – 213 – –
86 – – 214 – –
87 – – 215 – –
90 CLD-G CLD-G 218 CLE-G CLE-G
91 CLF-G CLF-G [D-G 2nd] 219 CLG-G CLG-G [E-G 2nd]
92 – – 220 – –
93 – – 221 – –
94 – – 222 – –
95 – – 223 – –
98 CLD-J CLD-J 226 CLE-J CLE-J
99 CLF-J CLF-J [D-J 2nd] 227 CLG-J CLG-J [E-J 2nd]
100 – – 228 – –
101 – – 229 – –
102 – – 230 – –
103 – – 231 – –
106 CLD-L CLD-L 234 CLE-L CLE-L
107 CLF-L CLF-L [D-L 2nd] 235 CLG-L CLG-L [E-L 2nd]
108 – – 236 – –
109 – – 237 – –
110 – – 238 – –
111 – – 239 – –

MIX mode1 MIX mode1
114 CLD-N CLD-N 242 CLE-N CLE-N
115 CLF-N CLF-N [D-N 2nd] 243 CLG-N CLG-N [E-N 2nd]
116 – – 244 – –
117 – – 245 – –
118 – – 246 – –
119 – – 247 – –
122 CLD-Q CLD-Q 250 CLE-Q CLE-Q
123 CLF-Q CLF-Q [D-Q 2nd] 251 CLG-Q CLG-Q [E-Q 2nd]
124 – – 252 – –
125 – – 253 – –
126 – – 254 – –
127 – – 255 – –
1. A hyphen (-) indicates the port is not available.
Table 5 Port serial numbers and names (16-port channel adapter)
number mode Initiator/External number mode Initiator/External
MIX mode MIX mode
4 CL1-B CL1-B 132 CL2-B CL2-B
5 CL3-B CL3-B [1-B 2nd] 133 CL4-B CL4-B [2-B 2nd]
7 CL7-B CL7-B [5-B 2nd] 135 CL8-B CL8-B [6-B 2nd]
12 CL1-D CL1-D 140 CL2-D CL2-D
13 CL3-D CL3-D [1-D 2nd] 141 CL4-D CL4-D [2-D 2nd]
14 CL5-D CL5-D 142 CL6-D CL6-D
15 CL7-D CL7-D [5-D 2nd] 143 CL8-D CL8-D [6-D 2nd]
MIX mode MIX mode
20 CL1-F CL1-F 148 CL2-F CL2-F
21 CL3-F CL3-F [1-F 2nd] 149 CL4-F CL4-F [2-F 2nd]
22 CL5-F CL5-F 150 CL6-F CL6-F
23 CL7-F CL7-F [5-F 2nd] 151 CL8-F CL8-F [6-F 2nd]
28 CL1-H CL1-H 156 CL2-H CL2-H
29 CL3-H CL3-H [1-H 2nd] 157 CL4-H CL4-H [2-H 2nd]
30 CL5-H CL5-H 158 CL6-H CL6-H
31 CL7-H CL7-H [5-H 2nd] 159 CL8-H CL8-H [6-H 2nd]
36 CL1-K CL1-K 164 CL2-K CL2-K
37 CL3-K CL3-K [1-K 2nd] 165 CL4-K CL4-K [2-K 2nd]
38 CL5-K CL5-K 166 CL6-K CL6-K
39 CL7-K CL7-K [5-K 2nd] 167 CL8-K CL8-K [6-K 2nd]
44 CL1-M CL1-M 172 CL2-M CL2-M
45 CL3-M CL3-M [1-M 2nd] 173 CL4-M CL4-M [2-M 2nd]
46 CL5-M CL5-M 174 CL6-M CL6-M
47 CL7-M CL7-M [5-M 2nd] 175 CL8-M CL8-M [6-M 2nd]

MIX mode MIX mode
52 CL1-P CL1-P 180 CL2-P CL2-P
53 CL3-P CL3-P [1-P 2nd] 181 CL4-P CL4-P [2-P 2nd]
54 CL5-P CL5-P 182 CL6-P CL6-P
55 CL7-P CL7-P [5-P 2nd] 183 CL8-P CL8-P [6-P 2nd]
60 CL1-R CL1-R 188 CL2-R CL2-R
61 CL3-R CL3-R [1-R 2nd] 189 CL4-R CL4-R [2-R 2nd]
62 CL5-R CL5-R 190 CL6-R CL6-R
63 CL7-R CL7-R [5-R 2nd] 191 CL8-R CL8-R [6-R 2nd]
66 CLD-A CLD-A 194 CLE-A CLE-A
67 CLF-A CLF-A [D-A 2nd] 195 CLG-A CLG-A [E-A 2nd]
68 CL9-B CL9-B 196 CLA-B CLA-B
69 CLB-B CLB-B [9-B 2nd] 197 CLC-B CLC-B [A-B 2nd]
70 CLD-B CLD-B 198 CLE-B CLE-B
71 CLF-B CLF-B [D-B 2nd] 199 CLG-B CLG-B [E-B 2nd]
74 CLD-C CLD-C 202 CLE-C CLE-C
75 CLF-C CLF-C [D-C 2nd] 203 CLG-C CLG-C [E-C 2nd]
76 CL9-D CL9-D 204 CLA-D CLA-D
77 CLB-D CLB-D [9-D 2nd] 205 CLC-D CLC-D [A-D 2nd]
78 CLD-D CLD-D 206 CLE-D CLE-D
79 CLF-D CLF-D [D-D 2nd] 207 CLG-D CLG-D [E-D 2nd]
82 CLD-E CLD-E 210 CLE-E CLE-E
83 CLF-E CLF-E [D-E 2nd] 211 CLG-E CLG-E [E-E 2nd]
84 CL9-F CL9-F 212 CLA-F CLA-F
85 CLB-F CLB-F [9-F 2nd] 213 CLC-F CLC-F [A-F 2nd]
86 CLD-F CLD-F 214 CLE-F CLE-F
87 CLF-F CLF-F [D-F 2nd] 215 CLG-F CLG-F [E-F 2nd]
MIX mode MIX mode
90 CLD-G CLD-G 218 CLE-G CLE-G
91 CLF-G CLF-G [D-G 2nd] 219 CLG-G CLG-G [E-G 2nd]
92 CL9-H CL9-H 220 CLA-H CLA-H
93 CLB-H CLB-H [9-H 2nd] 221 CLC-H CLC-H [A-H 2nd]
94 CLD-H CLD-H 222 CLE-H CLE-H
95 CLF-H CLF-H [D-H 2nd] 223 CLG-H CLG-H [E-H 2nd]
98 CLD-J CLD-J 226 CLE-J CLE-J
99 CLF-J CLF-J [D-J 2nd] 227 CLG-J CLG-J [E-J 2nd]
100 CL9-K CL9-K 228 CLA-K CLA-K
101 CLB-K CLB-K [9-K 2nd] 229 CLC-K CLC-K [A-K 2nd]
102 CLD-K CLD-K 230 CLE-K CLE-K
103 CLF-K CLF-K [D-K 2nd] 231 CLG-K CLG-K [E-K 2nd]
106 CLD-L CLD-L 234 CLE-L CLE-L
107 CLF-L CLF-L [D-L 2nd] 235 CLG-L CLG-L [E-L 2nd]
108 CL9-M CL9-M 236 CLA-M CLA-M
109 CLB-M CLB-M [9-M 2nd] 237 CLC-M CLC-M [A-M 2nd]
110 CLD-M CLD-M 238 CLE-M CLE-M
111 CLF-M CLF-M [D-M 2nd] 239 CLG-M CLG-M [E-M 2nd]
114 CLD-N CLD-N 242 CLE-N CLE-N
115 CLF-N CLF-N [D-N 2nd] 243 CLG-N CLG-N [E-N 2nd]
116 CL9-P CL9-P 244 CLA-P CLA-P
117 CLB-P CLB-P [9-P 2nd] 245 CLC-P CLC-P [A-P 2nd]
118 CLD-P CLD-P 246 CLE-P CLE-P
119 CLF-P CLF-P [D-P 2nd] 247 CLG-P CLG-P [E-P 2nd]
122 CLD-Q CLD-Q 250 CLE-Q CLE-Q
123 CLF-Q CLF-Q [D-Q 2nd] 251 CLG-Q CLG-Q [E-Q 2nd]

MIX mode MIX mode
124 CL9-R CL9-R 252 CLA-R CLA-R
125 CLB-R CLB-R [9-R 2nd] 253 CLC-R CLC-R [A-R 2nd]
126 CLD-R CLD-R 254 CLE-R CLE-R
127 CLF-R CLF-R [D-R 2nd] 255 CLG-R CLG-R [E-R 2nd]
Table 6 Port serial numbers and names (XP10000/SVS200)
MIX mode MIX mode
65 CL3-A CL3-A[1-A 2nd] 193 CL4-A CL4-A[2-A 2nd]
67 CL7-A CL7-A[5-A 2nd] 195 CL8-A CL8-A[6-A 2nd]
69 CL3-B CL3-B[1-B 2nd] 197 CL4-B CL4-B[2-B 2nd]
71 CL7-B CL7-B[5-B 2nd] 199 CL8-B CL8-B[6-B 2nd]
72 – – 200 – –
73 – – 201 – –
74 – – 202 – –
75 – – 203 – –
76 – – 204 – –
77 – – 205 – –
78 – – 206 – –
79 – – 207 – –
80 CL1-E CL1-E 208 CLA-E CL2-E
81 CL3-E CL3-E[1-E 2nd] 209 CLC-E CL4-E[2-E 2nd]
82 CL5-E CL5-E 210 CLE-E CL6-E
83 CL7-E CL7-E[5-E 2nd] 211 CLG-E CL8-E[6-E 2nd]
84 CL1-F CL1-F 212 CLA-F CL2-F
85 CL3-F CL3-F[1-F 2nd] 213 CLC-F CL4-F[2-F 2nd]
86 CL5-F CL5-F 214 CLE-F CL6-F
87 CL7-F CL7-F[5-F 2nd] 215 CLG-F CL8-F[6-F 2nd]
88 CL1-G CL1-G 216 CLA-G CL2-G
89 CL3-G CL3-G[1-G 2nd] 217 CLC-G CL4-G[2-G 2nd]
90 CL5-G CL5-G 218 CLE-G CL6-G
91 CL7-G CL7-G[5-G 2nd] 219 CLG-G CL8-G[6-G 2nd]
Table 6 Port serial numbers and names (XP10000/SVS200) (continued)
MIX mode MIX mode
92 CL1-H CL1-H 220 CLA-H CL2-H
93 CL3-H CL3-H[1-H 2nd] 221 CLC-H CL4-H[2-H 2nd]
94 CL5-H CL5-H 222 CLE-H CL6-H
95 CL7-H CL7-H[5-H 2nd] 223 CLG-H CL8-H[6-H 2nd]
iSCSI port and iSNS server settings

You must make settings on iSCSI ports (and iSNS servers, if necessary) when configuring iSCSI
environments. Use LUN Manager to specify the following items when configuring iSCSI environments. For
instructions, see ”Defining LU paths” on page 75 and ”Making settings on iSCSI ports and iSNS servers”
on page 101.
• IP address: You must specify the iSCSI port’s IP address when configuring iSCSI environments. In LUN
Manager, the initial value of the iSCSI port’s IP address is 192.168.0.xxx, where xxx is the iSCSI
port’s location.
• Subnet mask: You must specify a subnet mask when configuring iSCSI environments. A subnet mask is
a value used for obtaining a network address from an IP address. In LUN Manager, the subnet mask’s
initial value is 255.255.255.0.
• Gateway address: If a gateway is used, specify the gateway address. A gateway is hardware
connecting networks with different protocols.
• iSCSI name: You must assign iSCSI names to iSCSI ports when configuring iSCSI environments. iSCSI
names are used to uniquely identify each iSCSI node. iSCSI nodes are devices that use the iSCSI
protocol for communication (for example, iSCSI ports in arrays, host bus adapters in host servers, and
switching hubs for network relaying).
iSCSI names must be specified in either of the following formats:
• eui format:
An IEEE 64-bit Extended Unique Identifier used to specify an iSCSI name. The iSCSI name begins
with eui. and is followed by the ID found by the vendor in EUI-64 format similar to the World Wide
Name.
Example: eui.02004567A425678D
• iqn format:
The iSCSI Qualified Name format used to specify an iSCSI name. For more information about
specifying iSCSI names using this format, see the iSCSI-related documentation.
If a host is connected to an iSCSI port, LUN Manager automatically displays the iSCSI name in iqn
format. iSCSI names can include 0 (zero) to 9, and a to f (letters are case-insensitive).
Example: iqn.2006.01.com.hp:iscsi-r500:model-xxx:sn-xxxxxx:lun00
The length of an iSCSI name must be 20 characters in eui format, and up to 223 characters in iqn
format. iSCSI names can include letters, numbers, periods (.), hyphens (-), and colons (:); but cannot
include double-byte characters. iSCSI names are case-insensitive.
• iSCSI alias: An iSCSI alias is a nickname you assign to an iSCSI name. Assigning iSCSI aliases is
optional, but helpful, when managing and identifying iSCSI targets.
It is difficult to identify iSCSI targets by iSCSI names because an iSCSI name consists of numerous
characters and is hard to remember. If you assign an iSCSI alias that is brief and easy to remember,
you can easily and quickly identify iSCSI targets.
The length of an iSCSI alias must be up to 32 characters. iSCSI aliases can include letters, numbers,
periods (.), hyphens (-), and colons (:); but cannot include double-byte characters. iSCSI aliases are
case-sensitive; for example, MyPort and myport are different iSCSI aliases.

• Port number: You must assign part numbers to iSCSI ports when configuring iSCSI environments. Use
LUN Manager to specify a decimal port number within the range of 1 to 65535. A port number’s
initial value is 3260.
• Keep-alive timer: You must specify the Keep-alive timer when configuring iSCSI environments. The
Keep-alive timer is used when there is a connection between an iSCSI port and another iSCSI node.
For example, if the keep-alive timer is set to 60 seconds, the array checks whether packet
communications occurred between an iSCSI port and another iSCSI node (such as a host bus adapter
or switching hub) every 60 seconds.
Use LUN Manager to specify a value within the range of 0 to 64,800 seconds. The Keep-alive timer’s
initial value is 60 seconds.
• Whether to register iSCSI ports in iSNS servers: The iSNS server is a server computer on which an
iSNS service is installed. iSNS is an acronym for Internet Storage Name Service. This server manages
IP addresses and iSCSI names of iSCSI ports. Using iSNS servers is optional. If you configure and use
iSNS servers, iSCSI ports are easily discovered and managed.
NOTE: For more information about configuring iSNS servers, see the iSNS-related
documentation.
• iSNS server’s IP address: To use an iSNS server, you must specify the iSNS server’s IP address.
• iSNS server’s TCP port number: To use an iSNS server, you must specify the iSNS server’s TCP port
number.
NOTE: Specify 3205 as the TCP port number if you use Microsoft® iSNS Server as the iSNS
server. If you specify other than 3205, you cannot register iSCSI ports in the iSNS server.
Status of connections between hosts and the array

Use LUN Manager to issue a ping command from an array iSCSI port to a host. The ping command
checks whether the host and array can communicate with each other. If the host responds to the ping
command, the host and array can communicate with each other. For more information, see ”Checking the
status of the connection between hosts and the array (iSCSI environments only)” on page 103.
User authentication (Fibre Channel environments)

When configuring Fibre Channel environments, you can use LUN Manager to set user authentication
between the array’s ports and hosts. In Fibre Channel environments, ports and hosts use Null DH-CHAP
(Challenge Handshake Authentication Protocol with a Null Diffie-Hellmann algorithm) as the
authentication method. This section provides an overview of user authentication.
NOTE: Throughout this user guide, Null DH-CHAP is sometimes referred to as CHAP.
User authentication operations and settings

User authentication operations in Fibre Channel environments contain the following phases:
1. A host group of the array authenticates a host attempting to connect (authentication of hosts).
2. The host authenticates the connection-target host group of the array (authentication of host groups).
CAUTION: Because host bus adapters currently do not support this function, this authentication
phase is not used in Fibre Channel environments.
3. A target port of the array authenticates a Fibre Channel switch attempting to connect (authentication of
Fibre Channel switches).
The array performs user authentication by host groups. Therefore, host groups and hosts must have their
own user information for performing user authentication.
When a host attempts to connect to the array, the authentication of hosts phase starts. In this phase, it is
determined whether the host group requires authentication of the host. If the host group does not require
authentication of the host, the host connects to the array without authentication. If the host group requires
authentication of the host, authentication is performed for the host. When the host is successfully
authenticated, processing goes to the next phase.
After authentication of the host succeeds, if the host requires user authentication for the host group that is
connection target, the authentication of host groups phase starts. In this way, host groups and hosts
authenticate with each other, that is, mutual authentication. In the authentication of host groups phase. if
the host does not require user authentication for the host group, the host connects to the array without
authentication of the host group.
The following explains the settings required for user authentication. The settings for authentication of host
groups are needed only when performing mutual authentication.
• Settings for authentication of hosts
• On the array:
Use LUN Manager to specify whether authentication of hosts on each host group is performed. On
a host group that performs authentication, register user information (group name, user name, and
secret) of hosts allowed to connect to the host group. A secret is a password used in CHAP
authentication. When registering user information, you can also enable or disable authentication
on a host basis. For more information, see ”Enabling and disabling authentication of hosts in host
groups” on page 104 and ”Registering a host’s user information on a host group” on page 104.
• On hosts:
Configure the operating system and Fibre Channel host bus adapter driver for authentication by
host groups with CHAP. You must specify the host’s user name and secret used for CHAP. For more
information, see the documentation for the operating system and Fibre Channel host bus adapter
driver in your environment.
• Settings for authentication of ports (required if performing mutual authentication)
• On the array:
Use LUN Manager to specify each host group’s user information (user name and secret). For more
information, see ”Specifying a host group’s user information (when performing mutual
authentication)” on page 107.
• On hosts:
Configure the operating system and Fibre Channel host bus adapter driver for authenticating host
groups with CHAP. You must specify the user name and secret of the host group that is the
connection target. For more information, see the documentation for the operating system and Fibre
Channel host bus adapter driver in your environment.
The next section explains authentication of hosts and host groups.

Authentication of hosts (Fibre Channel environments)
When a host attempts to connect to the array, the connection results of the authentication of the host
differs depending on the host group settings. Figure 9 illustrates the relationship between host group
settings and the connection results.
Figure 9 Authentication of hosts (Fibre Channel environments)

Case A to Case D in Figure 9 is explained as follows:
• Case A through Case D: When performing authentication of host groups
• Case A: If the host’s user information is registered on the host group, and authentication of the host
is enabled
The host group authenticates the user information sent from the host. If authentication of the host
succeeds, either of the following actions occur:
• When the host is configured for mutual authentication, processing goes to authentication of the
host group.
• When the host is not configured for mutual authentication, the host connects to the array.
If the host is not configured for authentication by host groups with CHAP, the authentication fails
and the host cannot connect to the array.
• Case B: If the host’s user information is registered on the host group, but authentication of the host
is disabled
The host group does not perform authentication of the host. The host connects to the array without
authentication regardless of whether or not the host is configured for authentication by host groups
with CHAP.
• Case C: If the host’s user information is not registered on the host group
Regardless of the setting on the host, the host group performs authentication of the host, but results
in failure. The host cannot connect to the array.
• Case D: When connecting via a host group that does not perform authentication of hosts
The host connects to the array without authentication of the host regardless of whether or not the host
is configured for authentication by host groups with CHAP.
In this case, although you do not need to register the host’s user information on the host group, you
can register the user information.
NOTE: You should register the user information for all hosts to be connected to a host group that
performs authentication of hosts. To allow a specific host to connect to such a host group without
authentication, configure the host group and the host as follows:
• On the host group:
Register the user information of the host you want to allow to connect without authentication, and then
disable the host authentication setting.
Figure 10 shows an example of authentication of hosts. In this figure, WWNs of host bus adapters (HBAs)
are abbreviated as a, b, and so on.
Figure 10 Example of authentication of hosts (Fibre Channel environments)

In Figure 10, host group 1 performs authentication of hosts, but host group 2 does not.
Host A’s user information is registered on host group 1, and the authentication setting is enabled.
Therefore, if the authentication of the host succeeds, Host A can connect to the array (or processing goes
to the authentication of the host group). As a precondition of successful authentication, configure Host A
for authentication by host groups with CHAP.
Host B’s user information is also registered on host group 1, but the authentication setting is disabled.
Therefore, Host B can connect to the array without authentication.
Host C’s user information is not registered on host group 1. Therefore, when Host C tries to connect to the
array, authentication fails and the connection request is denied regardless of Host C’s setting.

Host D is attached to host group 2, which does not perform authentication of hosts. Therefore, Host D can
connect to the array without authentication.
Authentication of Fibre Channel switches

When a host attempts to connect to the array, the connection results of the authentication of the Fibre
Channel switch differs depending on the Fibre Channel switch setting related to each port. Figure 11
illustrates the relationship between Fibre Channel switch settings and the connection results. The Fibre
Channel switch authentication setting is independent from the host authentication setting.
Figure 11 Authentication of Fibre Channel switches

Case A to Case D in Figure 11 are explained as follows:
• Case A through Case C: When performing authentication of Fibre Channel switches by ports
• Case A: If the Fibre Channel switch’s user information is registered on the port, and authentication
of the Fibre Channel switch is enabled
Each port authenticates the Fibre Channel switch. If the authentication of the Fibre Channel switch
• When the Fibre Channel switch is configured for mutual authentication, processing goes to
authentication of the port.
• When the Fibre Channel switch is not configured for mutual authentication, the Fibre Channel
switch connects to the array.
If the port’s Fibre Channel switch is not configured for authentication with CHAP, the authentication
fails and the Fibre Channel switch cannot connect to the array.
• Case B: If the Fibre Channel switch’s user information is registered on the port, but authentication
of the Fibre Channel switch is disabled
Each port does not perform authentication of the Fibre Channel switch. The Fibre Channel switch
connects to the array without authentication regardless of whether or not the Fibre Channel switch
is configured for authentication with CHAP.
• Case C: If the Fibre Channel switch’s user information is not registered on the port
Regardless of the Fibre Channel switch’s setting, the port performs authentication of the Fibre
Channel switch, but results in failure. The Fibre Channel switch cannot connect to the array.
• Case D: When not performing authentication of Fibre Channel switches by ports
The Fibre Channel switch connects to the array without authentication of the host regardless of whether
or not the Fibre Channel switch is configured for authentication with CHAP.
In this case, although you do not need to register the Fibre Channel switch’s user information on the
port, you can register the user information.
Authentication of ports (performing mutual authentication)

When authentication of a host succeeds, the host performs authentication of the port in reverse if the host
requires (mutual authentication). In authentication of ports, when the user information (user name and
secret) of the port specified on the port side matches the user information stored on the host, the host
allows the host group to connect.
User authentication (iSCSI environments)

When configuring iSCSI environments, use LUN Manager to set user authentication between ports on the
array and hosts. In iSCSI environments, ports and hosts use Challenge Handshake Authentication Protocol
(CHAP) as the authentication method. This section provides an overview of user authentication.
User authentication operations and settings (iSCSI environments)

User authentication operations in iSCSI environments consist of the following phases:
1. An iSCSI target of the array authenticates a host attempting to connect (authentication of hosts).
2. The host authenticates the connection-target iSCSI target of the array (authentication of iSCSI targets).
The array performs user authentication by iSCSI targets. Therefore, iSCSI targets and hosts must have their
own user information for performing user authentication.
When a host attempts to connect to the array, the authentication of hosts phase starts. In this phase, it is
first determined whether or not the iSCSI target requires authentication of the host. If the iSCSI target does
not require authentication of the host, the host connects to the array without authentication. If the iSCSI
target requires authentication of the host, authentication is performed for the host. When the host is
successfully authenticated, processing goes to the next phase.
After authentication of the host succeeds, if the host requires user authentication for the iSCSI target that is
the connection target, the authentication of iSCSI targets phase starts. In this way, iSCSI targets and hosts
authenticate with each other, that is, mutual authentication. In the authentication of iSCSI targets phase, if
the host does not require user authentication for the iSCSI target, the host connects to the array without
authentication of the iSCSI target.
The following explains the settings required for user authentication. The settings for authentication of iSCSI
targets are needed only when performing mutual authentication.
• Settings for authentication of hosts
• On the array:
Use LUN Manager to specify whether authentication of hosts is performed on each iSCSI target.
On an iSCSI target that performs authentication, register user information (iSCSI name, user name,
and secret) of hosts allowed to connect to the iSCSI target. A secret is a password used in CHAP
authentication. When registering user information, you can also enable or disable authentication
on a host basis. For more information about the settings, see ”Enabling and disabling
authentication of hosts on iSCSI targets” on page 112 and ”Registering a host’s user information
on an iSCSI target” on page 112.
• On hosts:

Configure the operating system and iSCSI driver for authentication by iSCSI targets with CHAP.
You must specify the host’s user name and secret used for CHAP. For more information, see the
documentation for the operating system and iSCSI driver in your environment.
• Settings for authentication of ports (required if performing mutual authentication)
• On the array:
Use LUN Manager to specify each iSCSI target’s user information (user name and secret). For more
information about the settings, see ”Specifying an iSCSI target’s user information (when
performing mutual authentication)” on page 115.
• On hosts:
Configure the operating system and iSCSI driver for authenticating iSCSI targets with CHAP. You
must specify the user name and secret of the iSCSI target that is the connection target. For more
information, see the documentation for the operating system and iSCSI driver in your environment.
The next section explains authentication of hosts and iSCSI targets.
Authentication of hosts (iSCSI environments)

When a host attempts to connect to the array, the connection results of the authentication of the host differ
depending on the iSCSI target settings. Figure 12 illustrates the relationship between iSCSI target settings
and the connection results.
Figure 12 Authentication of hosts (iSCSI environments)

Case A to Case D in Figure 12 are explained as follows:
• Case A through Case C: When connecting via an iSCSI target that performs authentication of hosts
• Case A: If the host’s user information is registered on the iSCSI target, and authentication of the
host is enabled
The iSCSI target authenticates the user information sent from the host. If authentication of the host
• When the host is configured for mutual authentication, processing goes to authentication of the
iSCSI target.
• When the host is not configured for mutual authentication, the host connects to the array.
If the host is not configured for authentication by iSCSI targets with CHAP, the authentication fails
and the host cannot connect to the array.
• Case B: If the host’s user information is registered on the iSCSI target, but authentication of the host
is disabled
The iSCSI target does not perform authentication of the host. The host connects to the array without
authentication regardless of whether or not the host is configured for authentication by iSCSI
targets with CHAP.
CAUTION: If a host uses Microsoft iSCSI Initiator and is configured for authentication by iSCSI
targets with CHAP, authentication of the host fails. To allow such a host to connect to the iSCSI
target without authentication, do not configure it for authentication by ports with CHAP.
• Case C: If the host’s user information is not registered on the iSCSI target
Regardless of the setting on the host, the iSCSI target performs authentication of the host, but results
in a failure. The host cannot connect to the array.
• Case D: When connecting via an iSCSI target that does not perform authentication of hosts
The host connects to the array without authentication of the host regardless of whether or not the host
is configured for authentication by iSCSI targets with CHAP.
In this case, although you do not need to register the host’s user information on the iSCSI target, you
can register the user information.
CAUTION: If a host uses Microsoft iSCSI Initiator and is configured for authentication by iSCSI
targets with CHAP, authentication of the host fails. To allow such a host to connect to the port
without authentication, do not configure it for authentication by iSCSI targets with CHAP.
NOTE: You should register the user information for all hosts to be connected to an iSCSI target that
performs authentication of hosts. To allow a specific host to connect to such an iSCSI target without
authentication, configure the iSCSI target and the host as follows:
• On the iSCSI target:
Register the user information of the host you want to allow to connect without authentication, and then
disable the host’s authentication setting.
• On the host:
It does not matter if you configure the host for authentication by ports with CHAP.
However, if the host uses Microsoft iSCSI Initiator, do not configure the host for authentication by ports
with CHAP.

Figure 13 shows an example of authentication of hosts. In this figure, iSCSI names of host bus adapters
(HBAs) are abbreviated as a, b, and so on.
Figure 13 Example of authentication of hosts (iSCSI environments)

In Figure 13, iSCSI target 1 performs authentication of hosts, but iSCSI target 2 does not.
Host A’s user information is registered on iSCSI target 1, and the authentication setting is enabled.
Therefore, if authentication of the host succeeds, Host A can connect to the array (or processing goes to
the authentication of the iSCSI target). As a precondition of successful authentication, configure Host A for
authentication by iSCSI targets with CHAP.
Host B’s user information is also registered on iSCSI target 1, but the authentication setting is disabled.
Therefore, Host B can connect to the array without authentication. (If Host B uses Microsoft iSCSI Initiator,
Host B can connect to the array only when Host B is not configured for authentication by iSCSI targets
with CHAP.)
Host C’s user information is not registered on iSCSI target 1. Therefore, when Host C tries to connect to
the array, authentication fails and the connection request is denied regardless of Host C’s setting.
Host D is attached to iSCSI target 2, which does not perform authentication of hosts. Therefore, Host D
can connect to the array without authentication. In this case, it does not matter whether Host D’s user
information is registered on iSCSI target 2. (If Host D uses Microsoft iSCSI Initiator, Host D can connect to
the array only when Host D is not configured for authentication by iSCSI targets with CHAP.)
• ”Enabling and disabling authentication of hosts on iSCSI targets” on page 112
• ”Registering a host’s user information on an iSCSI target” on page 112
• ”Settings and connection results in authentication of hosts (iSCSI environments)” on page 116.
For more information about configuring hosts, see the documentation for the operating system and iSCSI
Authentication of iSCSI targets (performing mutual authentication)

When authentication of a host succeeds, the host performs authentication of the iSCSI target in reverse if
the host requires (mutual authentication). In authentication of iSCSI targets, when the user information
(user name and secret) of the iSCSI target specified on the iSCSI target side matches the user information
stored on the host, the host allows the iSCSI target to connect.
For more information about iSCSI target settings to perform authentication of iSCSI targets, see
”Specifying an iSCSI target’s user information (when performing mutual authentication)” on page 115.
For more information about configuring hosts, see the documentation for the operating system and iSCSI
NAS channel adapters

You can use LUN Manager to check the running status of the OSs on NAS channel adapters. Also, when
a failure occurs in the OS, you can operate (restart, stop, or start) the OS using LUN Manager without
going to the array’s cabinet. For instructions on checking the OS status on NAS channel adapters and
operating the OSs, see ”Operating NAS channel adapters” on page 117.

2 Preparing to use LUN Manager
System requirements
To use LUN Manager, you need:
• XP12000/XP10000/SVS200 array
• LUN Manager optional program
• WWW client computer connected to the array via a LAN
To use LUN Manager, you must use the WWW client computer to log on to the SVP. When you are
logged on, Command View XP or XP Remote Web Console, which is a Java® applet, is downloaded to
the WWW client computer. You can perform LUN Manager operations in Command View XP or XP
Remote Web Console.
For more information about requirements for WWW client computers, see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user
guide for XP12000/XP10000/SVS200.
Configuring WWW client computers

LUN Manager operations require Command View XP or XP Remote Web Console, which is downloaded
to the WWW client computer. The WWW client computer must be connected to the array via a LAN.
Browser settings are also required on the WWW client computer. For more information, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote
Web Console user guide for XP12000/XP10000/SVS200.
Enabling required software

For more information about enabling LUN Manager, see the HP StorageWorks Command View XP user
guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for
XP12000/XP10000/SVS200.
Notes on using LUN Manager

• If you attempt to apply numerous settings in the LUN Manager panes, the SVP might be unable to
continue processing. HP recommends that you make up to approximately 1,000 settings. Numerous
settings are likely to be made when alternate paths are defined (see ”Copying paths from one Fibre
Channel or iSCSI port to another” on page 93), even though only two commands are required for
defining alternate paths.
• Do not remove LU paths (see ”Deleting LU paths” on page 84) when hosts perform I/O processing.
• Do not disable LUN security (see ”Disabling LUN security” on page 97) when hosts perform I/O
processing.
54 Preparing to use LUN Manager
3 LUN Manager panes
When you start LUN Manager, the Command View XP or XP Remote Web Console main pane displays
the LUN Manager, Port, and Authentication panes.
This chapter describes these panes.
LUN Manager pane

When you click the icon in the Command View XP or XP Remote Web Console main pane, LUN
Manager starts and the LUN Manager pane appears. Use the LUN Manager pane to define LU paths and
apply LUN security to logical volumes.
NOTE: Storage partition administrators can display information or operate only within the allocated
storage management logical partition (SLPR). For more information about SLPRs, see the
HP StorageWorks XP Disk/Cache Partition user guide.
Figure 14 LUN Manager pane (icon under Fibre folder selected)
Figure 15 LUN Manager pane (icon under iSCSI folder selected)
LU Path tree
Use this tree to find information about LU paths. When you select a host group from this tree, the table on
the right displays information about LU paths associated with the selected host group.
The Subsystem folder is located at the top of the tree. The Fibre, NAS, and iSCSI folders appear below the
Subsystem folder.
Fibre folder
If you double-click the Fibre folder, Fibre Channel ports in the array appear as icons. The port name, port
address, LUN security status, and port attribute (that is, whether the port is an initiator, target, RCU target,
or external port) appear on the right of each icon.
NOTE: The Fibre folder does not appear if the array does not contain any Fibre Channel adapters.
Figure 16 Fibre folder
Table 7 Fibre Channel port icons
Icon Status
Port in Standard mode. LUN security is disabled on the port.
Port in Standard mode. LUN security is enabled on the port.
Port in High Speed mode. LUN security is disabled on the port.
56 LUN Manager panes

Table 7 Fibre Channel port icons (continued)
Icon Status
Port in High Speed mode. LUN security is enabled on the port
Port in Initiator/External MIX mode. LUN security is disabled on the port.
Port in Initiator/External MIX mode. LUN security is enabled on the port.
When you double-click a Fibre Channel port in the tree, a list of host groups ( ) appears. The host
group’s group number (G-ID), host group name, and host mode appear on the right of this icon. For more
information about host modes, see Table 16.
When you double-click a host group in the tree, a list of host bus adapters ( ) appears. The host bus
adapter’s nickname and World Wide Name (WWN) appear on the right of this icon. For more
information about WWNs, see ”Finding an open-system host’s World Wide Name (WWN)” on
page 121.
NOTE: Host bus adapters are adapters contained in host computers and are used as ports for
connecting hosts and the array.
When you double-click a port on which LUN security is disabled to display a list of host groups, host
groups except the first host group (that is, host group 0) are grayed out.
NAS folder
If you double-click the NAS folder, NAS ports in the array appear as icons. Four port names appear on
the right of each icon. The channel adapter name appears on the right of the port names. The channel
adapter name is enclosed by parentheses.
NOTE: The NAS folder does not appear if the array does not contain NAS channel adapters.
Figure 17 NAS folder
Table 8 NAS port icons
Icon Status
You can assign paths from this NAS port to logical volumes.
You cannot assign paths from this NAS port to logical volumes because of a hardware failure or another
reasons.
When you double-click a NAS port, the following host groups appear:
• NAS-Sys: When selected, information about paths to system LUs appears in the list on the right. The
list contents are grayed out and cannot be changed.
The group number (G-ID) of this host group is 00.
• User: When selected, information about paths to user LUs appears in the list on the right.
The group number (G-ID) of this host group is 01.
iSCSI folder
If you double-click the iSCSI folder, iSCSI ports in the array appear as icons. The port name and attribute
appear on the right of each icon.
NOTE:
• The iSCSI folder does not appear if the array does not contain iSCSI channel adapters.
• iSCSI ports always have the Target attribute.
Figure 18 iSCSI folder
Table 9 iSCSI port icons
Icon Status
LUN security is not applied to the port.
LUN security is applied to the port
When you double-click an iSCSI port in the tree, a list of iSCSI targets ( ) appears. The iSCSI target’s
group number (G-ID), name, and host mode appear on the right of this icon. For more information about
host modes, see Table 16 on page 77.
When you double-click an iSCSI target in the tree, a list of host bus adapters ( )appears. The host bus
adapter’s nickname and iSCSI name appear on the right of this icon.
NOTE: Host bus adapters are adapters contained in host computers and are used as ports for
connecting hosts and the array.
When you double-click a port to which LUN security is not applied to display a list of iSCSI targets, iSCSI
targets except for the first group (that is, iSCSI target 0) are grayed out.
LU Path table
A table appears on the right side and displays LU path information about the host group selected in the
tree.

• LUN: LUNs assigned to logical volumes. LUNs (logical unit numbers) are addresses assigned to logical
units (LUs), which are logical volumes that open-system hosts can access. If no paths are defined, the
other columns on the right are blank.
Table 10 LUN status icons
Icon Status
Logical volume to which an LU path is defined
Expanded LU
Command device
Command device security
Remote command device
LUN to which no LU path is defined
• CU:LDEV: CU image numbers appear on the left of the colon. LDEV numbers appear on the right of the
colon. The combination of a CU image number and an LDEV number is used to identify a logical
volume.
If an LDEV number ends with #, the logical volume is an external LU.
If an LDEV number ends with V, the logical volume is a virtual volume.
• Emulation: Logical volume’s (or logical device’s) emulation type.
For CV volumes, CVS appears on the right of the emulation type.
For LUSE volumes, an asterisk (*) and a number appear on the right of the emulation type. For
example, OPEN-9*3 indicates that three OPEN-9 volumes are combined.
• Capacity: Logical volume’s size.
• RAID: Logical volume’s RAID level.
If the logical volume is an external or virtual volume, the RAID column displays a hyphen (-) instead of
the RAID level.
• Paths: Number of alternate paths, if any.
• VMA: Access Attribute: Logical volume’s access attribute. If a VMA is set on a logical volume, VMA:
appears at the beginning of the access attribute. If extents are set on a logical volume, VMA(Ext):
appears at the beginning of the access attribute.
The following appear below the table:
• Selected LUNs: Number of LUNs selected in the table.
• Remaining LUNs (Port): Number of LUNs to which no LU path has been defined.
Indicates the number of LU paths you can add to the port specified in the tree.
• Remaining LUNs (GRP): Number of LUNs to which no LU path has been defined.
Indicates the number of LU paths you can add to the host group specified in the tree.
Lower-left list
The WWN name table or iSCSI name table appears at the lower left of the LUN Manager pane. The
WWN name table appears when you select an item related to a Fibre Channel port from the tree. The
iSCSI name table appears when you select an item related to an iSCSI port from the tree.
WWN name table
Lists host bus adapters connected to Fibre Channel ports on the array.
Figure 19 WWN name table

• Port: List of ports. The port’s fibre address appears on the right of the port name.
• Host Group: Host groups that are used to classify server hosts connected to the array. You must create
host groups in the LUN Manager pane.
• Name: Host bus adapter’s nickname. You can specify nicknames in the LUN Manager pane.
• WWN: Host bus adapter’s World Wide Name.
iSCSI name table
Lists host bus adapters connected to the iSCSI ports on the array.
Figure 20 iSCSI name table

• Port: List of ports.
• Target name: iSCSI targets are used to classify server hosts connected to the array. You must create
iSCSI targets in the LUN Manager pane.
• Name: Host bus adapter’s nickname. You can specify nicknames in the LUN Manager pane.
• iSCSI name: Host bus adapter’s iSCSI name.
LDEV table
Lists logical volumes in the array.
• CU: List of CU images.

• LDEV: Logical volumes. The CU image number appears on the left of the colon. The LDEV number
appears on the right of the colon. The combination of a CU image number and an LDEV number
identifies a logical volume.
Table 11 LDEV status icons
Icon Status
Normal logical volume
Expanded LU (that is, a LUSE volume)
Volume the Customized Volume feature is applied to (that is, a CVS volume)
Command device
Command device security
If an LDEV number ends with #, the logical volume is an external LU.

If an LDEV number ends with V, the logical volume is a virtual volume.
• Emulation: Logical volume’s emulation type.
For CV volumes, CVS appears on the right of the emulation type.
For LUSE volumes, an asterisk (*) and a number appear on the right of the emulation type. For
example, OPEN-9*3 indicates that three OPEN-9 volumes are combined.
• Capacity: Logical volume’s size.
• RAID: Logical volume’s RAID level.
If the logical volume is an external LU or virtual volume, the RAID column displays a hyphen (-) instead
of a RAID level.
• Parity Group: Parity group’s name.
If the name begins with E, the group is an external LU group consisting of one or more external LUs.
If the name begins with V, the group is a V-VOL group consisting of one or more virtual volumes.
• Paths: Number of alternate paths, if any.
• VMA:Access Attribute: Logical volume’s access attribute. If a VMA is set on a logical volume, VMA:
appears at the beginning of the access attribute. If extents are set on a logical volume, VMA(Ext):
appears at the beginning of the access attribute.
The number of logical volumes selected in the table appears below the table.
NOTE: The LDEV table does not contain volumes reserved by Auto LUN XP.
Buttons
• Add WWN: Registers host bus adapters in a host group. Before using this button, you must select a
host group in the LU Path tree, and select host bus adapters (WWNs) in the WWN name table.
NOTE: If you select an item related to NAS or iSCSI ports, you cannot use the Add WWN button.
• Add iSCSI name: Registers host bus adapters in an iSCSI target. Before using this button, you must
select an iSCSI target below the iSCSI folder in the LU Path tree, and select host bus adapters (iSCSI
names) in the iSCSI name table.
NOTE: If you select an item related to Fibre Channel or NAS ports, you cannot use the Add iSCSI
name button.
• Add LU Path: Defines LU paths to logical volumes. Before using this button, you must select LUNs in the
LU Path tree and select logical volumes in the LDEV table.
• Apply: Applies settings in the pane to the array.
• Cancel: Cancels settings in the pane.
Port pane
Manager starts. LUN Manager includes the Port pane, which you use to make settings for Fibre Channel
and iSCSI ports. Also, in NAS environments, you can operate the NAS channel adapter’s OS from the
Port pane.
The content of the Port pane changes depending on the selection in the Package tree. If you select an icon
under the Fibre folder, Figure 21 appears. If you select an icon under the iSCSI folder, Figure 22 appears.
If you select an icon under the NAS folder, Figure 23 appears.
NOTE: Storage partition administrators can display ports and operate only within the allocated SLPR.
For more information about SLPRs, see the HP StorageWorks XP Disk/Cache Partition user guide.
Figure 21 Port pane (icon under Fibre folder selected)

Figure 22 Port pane (icon under iSCSI folder selected)
Figure 23 Port pane (icon under NAS folder selected)
Package tree
Use this tree to select the port to be operated on. The Fibre, NAS, and iSCSI folders appear under the
Subsystem folder at the top of the tree.
Fibre folder
When you double-click the Fibre folder, the folder opens and lists Fibre Channel channel adapters
(CHAs). When you double-click a channel adapter, port blocks appear below the channel adapter. The
following icons are used.
Table 12 Channel adapter and port block icons (Fibre folder)
Icon Status
Channel adapter package. All ports in this channel adapter package are in Standard mode.
Channel adapter package. All or some ports in this channel adapter package are in High Speed mode.
Channel adapter package. All or some ports in this channel adapter package are in Initiator/External
MIX mode.
Port block in a channel adapter package. Ports in this port block are in Standard mode.
Port block in a channel adapter package. Ports in this port block are in High Speed mode.
Port block in a channel adapter package. Ports in this port block are in Initiator/External MIX mode.
iSCSI folder
When you double-click the iSCSI folder, the folder opens and lists iSCSI channel adapter packages.
Table 13 Channel adapter package icons (iSCSI folder)
Icon Status
iSCSI channel adapter package.
NAS folder
When you double-click the NAS folder, the folder opens and lists NAS channel adapters ( ). The NAS
channel adapter’s name and NAS channel adapter OS’s running status appear on the right of the icon.
Port table
This table appears when you select an icon under the Fibre folder in the Package tree.
If you select a channel adapter in the tree, the Port table displays all ports on the channel adapter.
If you select a port block, the Port table displays all ports in the port block.
You can use options in the Change Port Mode box to change information in this list.
Information in this list differs depending on the type of channel adapter package selected in the tree.
• If you select a Fibre Channel channel adapter, the list displays information about Fibre Channel ports.
Figure 24 Port table (Fibre Channel ports)

• Port Name: Port name. For more information, see Table 3, Table 4, Table 5, and Table 6.

• Type: Port‘s type. Fibre indicates a Fibre Channel port, which is used for connecting open-system
hosts.
• Host Speed: Fibre Channel port’s data transfer speed. The unit is Gbps (gigabits per second).
• Addr (Loop ID): Port‘s address.
• Fabric: Indicates if a fabric switch is used.
• Connection: Topology. The default is FC-AL. However, you must be aware that some fabric
switches require you to specify the point-to-point topology. If your system uses a fabric switch,
check the fabric switch’s documentation to determine whether the switch requires the point-to-point
topology.
• Attribute: Indicates whether the port is an initiator, target, RCU target, or external port.
• WWN: Host bus adapter’s WWN.
• If you select an iSCSI channel adapter, the list displays information about iSCSI ports and iSNS
servers.
Figure 25 Port table displaying (iSCSI ports and iSNS servers)

• Port Name: iSCSI port’s name. For more information, see Table 3, Table 4, Table 5, and Table 6.
• IP Address: iSCSI port’s IP address.
• Subnet Mask: Subnet mask.
• Gateway: Gateway address.
• Port No.: iSCSI port’s number.
• Keep Alive Timer: Keep-alive timer value. The unit is seconds.
• iSNS Server: Indicates whether you can register the iSCSI port in the iSNS server.
• Enable: You can register the iSCSI port.
• Disable: You cannot register the iSCSI port.
• iSNS IP Address: iSNS server’s IP address.
• iSNS Port No.: iSNS server’s TCP port number.
• MAC Address: iSCSI port’s MAC address (media access control address).
• Attribute: Port’s attribute.
NOTE: iSCSI ports always have the Target attribute.
iSCSI Function box
Use this box to perform iSCSI-related operations.
Figure 26 iSCSI Function box

• Ping: Issues a ping command from an iSCSI port to a host.
• Register: Registers information about iSCSI ports in the iSNS server.
• Delete: Removes information about iSCSI ports from the iSNS server.
Change Port Mode box

This box appears when you select an icon under the Fibre folder in the Package tree.
Use this box to change information in the Port table.
Information in this box differs depending on the type of channel adapter package selected in the tree:
• If you select a Fibre Channel channel adapter, this box displays items related to Fibre Channel ports.
Figure 27 Change Port Mode box (Fibre Channel ports)

• Select a Port: To change settings for a port, select the port from this list.
• Host Speed: The text box on the left displays the selected port’s data transfer speed.
Use the list on the right to specify the selected port’s data transfer speed. If you select Auto, the
array automatically sets the data transfer speed to 1 Gbps or 2 Gbps. Gbps is the acronym for
Gigabits per second.
NOTE: If you are using a 2 Gbps HBA and switch, set the CHF port’s transfer speed to 2 Gbps. If
you are using a 1 Gbps HBA and switch, set the CHF port’s transfer speed to 1 Gbps. If the Auto
Negotiation setting is required, the linkup might be incorrect at server reboot. Check the channel
lamp. If it is blinking, remove and re-insert the cable to perform the signal synchronization and
linkup.
• Fibre Addr.: The text box on the left displays the selected port’s address.
Use the list on the right to specify the selected port’s address.
• Fabric: The text box on the left indicates whether a fabric switch is used. This option must be set to
ON if a fabric switch is used. This option must be set to OFF if a fabric switch is not used.
Use the list on the right to specify whether a fabric switch is used.

• Connection: The text box on the left indicates the topology. This text box can display FC-AL or
P-to-P (point-to-point).
Use the list on the right to specify the topology.
CAUTION: Some fabric switches require you to specify the point-to-point topology. If your system
uses a fabric switch, check the fabric switch’s documentation to determine whether the fabric
switch requires the point-to-point topology.
• Set: Applies settings in the Change Port Mode box to the Port table.
• Clear: Cancels settings in the Change Port Mode box.
• If you select an iSCSI channel adapter, this box displays items related to iSCSI ports and iSNS servers
(for more information, see ”iSCSI port and iSNS server settings” on page 42).
Figure 28 Change Port Mode box (iSCSI port and iSNS server)
• Select a Port: To change a port’s settings, select the port from this list.
• IP Address: Selected port’s IP address.
• Subnet Mask: Subnet mask.
• Gateway: Gateway address.
• Port Number: Port number.
• Keep Alive Timer: Keep-alive timer value. The unit is seconds.
• iSNS Server: Specifies whether to register information about the iSCSI port in the iSNS server.
• Enable: Registers the iSCSI port.
• Disable: Does not register the iSCSI port.
• IP Address of iSNS Server: iSNS server’s IP address.
• Port Number of iSNS Server: iSNS server’s TCP port number.
• Set: Applies settings in the Change Port Mode box to the Port table.
CHN list
This list appears if you select an icon under the NAS folder in the Package tree. CHN is the channel
adapter for NAS.
The CHN list displays all NAS channel adapters. When you select a channel adapter in the Package tree,
the CHN list displays information of the selected channel adapter. Information displayed in the CHN list is
shown in Figure 29.
Figure 29 CHN list (NAS channel adapters)

• CHN Name: NAS channel adapter’s name.
• OS Status: Running status of the NAS channel adapter’s OS. Statuses are:
• NEW: OS is not installed on the channel adapter or is being installed.
• UP: OS is started.
• DOWN: OS stopped normally.
• DOWN (Failure): OS stopped due to a failure.
• BUSY (Boot): OS is being started.
• BUSY (Shutdown): OS is being stopped.
• ERROR: OS is being stopped due to a failure.
• DUMP: Hibernation dump is being collected.
• DUMP SKIP: Hibernation dump collection is skipped.
• HUNG UP: OS is freezing.
• UNKNOWN: OS status collection failed.
If the status is UP, you can use LUN Manager to stop the OS. If the status is DOWN or DOWN
(Failure), you can use LUN Manager to start the OS.
• Setting: Specified operation for the channel adapter’s OS. This column is blank before specifying an
operation. After specifying an operation, Reboot, Boot, or Shut Down appears. If you click Apply, this
column returns to a blank.
Buttons
• Reboot: Appears when select an icon under the NAS folder in the Package tree. Restarts an OS in UP
status selected in the CHN list.
• Shut Down: Appears when you select an icon under the NAS folder in the Package tree. Stops an OS
in UP status selected in the CHN list.
• Boot: Appears when you select an icon under the NAS folder in the Package tree. Starts an OS in
DOWN or DOWN (Failure) status selected in the CHN list.
Authentication pane
Manager starts. The LUN Manager pane includes the Authentication pane, which you can use to make

settings for user authentication. User authentication can be performed in Fibre Channel and iSCSI
environments.
Figure 30 Authentication pane (Fibre folder selected)
Figure 31 Authentication pane (port icon under Fibre folder selected)
Figure 32 Authentication pane (icon under iSCSI folder selected)
Port tree
Use this tree to find information about user authentication on each port. When you select a port from this
tree, the Authentication information (Target) list on the right displays user information for hosts registered
on the port. In addition, the Authentication information (Host) list displays the selected port’s user
information.
The iSCSI folder appears below the Subsystem folder located at the top of the tree.
Fibre folder
If you double-click the Fibre folder, Fibre Channel ports in the array appear as icons. If you double-click a
Fibre Channel port, host groups appear as icons. The host group name appears on the right of each icon.
When the icon appears, the host group performs authentication of hosts. When the icon
appears, the host group does not perform authentication of hosts. By default, the icon appears for all
host group icons.

NOTE: The Fibre folder appears only if the array contains a Fibre Channel adapter.
Figure 33 Fibre folder
Table 14 Fibre Channel port and Fibre Channel host group icons
Icon Status
CLX-Y Fibre channel port.
host group name Host group performs authentication of hosts.
host group name Host group does not perform authentication of hosts.
iSCSI folder
If you double-click the iSCSI folder, iSCSI ports in the array appear as icons. If you double-click an iSCSI
port, iSCSI targets appear as icons. The iSCSI name appears on the right of each icon. When the
icon appears, the iSCSI target performs authentication of hosts. When the icon appears, the iSCSI
target does not perform authentication of hosts. By default, the icon appears for all iSCSI targets.
NOTE: The iSCSI folder appears only if the array contains an iSCSI channel adapter.
Figure 34 iSCSI folder
Table 15 iSCSI port and iSCSI target status icons
Icon Status
CLX-Y iSCSI port.
iSCSI name iSCSI target performs authentication of hosts.
iSCSI name iSCSI target does not perform authentication of hosts.
Port Information list

• Port Name: Fibre Channel port name. For more information, see Table 3, Table 4, Table 5, and
Table 6.
• Time out: Period of time between authentication sessions to the same port. If the previous
authentication session to a port failed, the next authentication session starts after the specified period
of time elapses. The unit is seconds.
• Refusal Intvl.: If authentication fails for the number of times specified in Refusal Freq., connection to the
port fails. Refusal Intvl. is the interval from when connection to a port fails to when the next
authentication session starts. The unit is minutes.
• Refusal Freq.: Number of times of authentication for connecting to a port is allowed. If authentication
fails for the specified number of times, connection to the port fails.
FC Switch Information list

• Port Name: Fibre Channel port name. For more information, see Table 3, Table 4, Table 5, and
Table 6.
• User Name: Fibre Channel switch’s user name.
• Mode: Mode of authentication between ports and Fibre Channel switches. If the authentication mode
is mutual, bi-directional appears. If the authentication mode is not mutual, unidirectional appears.
• Authentication: Specifies if authentication for the Fibre Channel switch is performed. If the Fibre
Channel switch is a target of user authentication, Enable appears. If the host is not a target of user
authentication, Disable appears.
Authentication information (Target) list

Fibre folder
Displays user information for host groups allowed to connect to the port or host group selected in the tree.
• Group Name: Host group name.
• User Name: Host group’s user name. When a user name is not defined for a host group, this column is
blank.
• Authentication: Specifies if authentication for the host is performed. If the host is a target of user
authentication, Enable appears. If the host is not a target of user authentication, Disable appears.
iSCSI folder
Displays user information for iSCSI targets allowed to connect to the port or iSCSI target selected in the
tree.
• Target Name: iSCSI target’s iSCSI name.
• User Name: iSCSI target’s user name. When a user name is not defined for an iSCSI target, this
column is blank.
• Authentication: Indicates whether authentication of the host is performed. If the host is a target of user
authentication, Enable appears. If the host is not a target of user authentication, Disable appears.
Authentication Information (Host) list

Fibre folder
Displays host user information for the port or host group selected in the tree.
In this list, you can register up to 64 user information items.
• Group Name: Host group name.
• User Name: Host’s user names. When a user name is not defined for a host, this column is blank.
• Protocol: Protocol used in the user authentication.
iSCSI folder
Displays host user information for the port or iSCSI target selected in the tree.
In this list, you can register up to 64 user information items.
• Target Name: Host bus adapter’s iSCSI name.
• User Name: Host’s user name. When a user name is not defined for a host, this column is blank.
• Protocol: Protocol used in the user authentication.

Buttons
4 LUN Manager operations
This chapter describes how to start LUN Manager and various LUN Manager operations, such as defining
LU paths.
Starting LUN Manager

1. Start the Web browser.
2. Enter the following URL in the Web browser, and press Enter. The Storage Device List appears.
http://IP-address-of-main-SVP (Web server)/cgi-bin/utility/sjc0000.cgi
NOTE: If you are unsure of the IP address of the main SVP (Web server), ask the system
administrator.
3. In the Storage Device List, click the SVP to log onto. The Command View XP or XP Remote Web
Console login pane appears.
4. Enter the user name and password, and click OK. The Command View XP or XP Remote Web Console
main pane appears.
5. Click the LUN Manager button ( ). LUN Manager starts, and the LUN Manager pane appears.
You must change Command View XP or XP Remote Web Console to Modify mode to use LUN Manager.
When the background color of the icon on the right of the pane is light yellow ( ), the pane is in Modify
mode. When the background color is gray ( ), it is in View mode. If you click the ( ) icon when the
Unlocked icon ( ) appears, the icon changes to ( ), and the mode changes to Modify. For more
information about changing modes, see the HP StorageWorks Command View XP user guide for XP Disk
Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
Defining LU paths
If you are configuring a Fibre Channel environment, complete the following major steps:
1. ”Finding an open-system host’s World Wide Name (WWN)” on page 121
2. ”Creating host groups” on page 75
3. ”Registering hosts in host groups” on page 79
4. ”Associating host groups or iSCSI targets to logical volumes” on page 83
If you are configuring an iSCSI environment, complete the following major steps:
1. ”Creating host groups” on page 75
2. ”Registering hosts in host groups” on page 79
3. ”Associating host groups or iSCSI targets to logical volumes” on page 83
If you are configuring a NAS environment, complete the procedure described in ”Associating host groups
or iSCSI targets to logical volumes” on page 83.
Creating host groups
NOTE: If you are configuring a NAS environment, you do not need to follow the procedures described
in this section. For instructions on defining LU paths in NAS environments, see ”Associating host groups or
iSCSI targets to logical volumes” on page 83.
Creating host groups (when configuring Fibre Channel environments)

You can connect multiple server hosts of different platforms to one port on the array. When configuring
the system, you must group server hosts connected to the array by host groups. For example, if HP-UX and
Windows hosts are connected to a port, you must create one host group for HP-UX hosts and another host
group for Windows hosts. Next, you must register HP-UX hosts to the corresponding host group and
register Windows hosts to the other host group.
The following procedure describes how to create host groups. The procedure for registering hosts to a
host group is described in ”Registering hosts in host groups” on page 79.
1. Start LUN Manager. The LUN Manager pane (Figure 14) appears.
2. Right-click the port for which you want to create a host group, and select Add New Host Group. The
Add New Host Group pane appears.
NOTE: If you right-click an initiator port, you cannot select Add New Host Group. You cannot
create host groups for initiator ports.
Figure 35 Add New Host Group pane

3. In the Group Name box, enter the host group name.
It is convenient if you name each host group after the host platform. For example, when creating a host
group to register Windows NT® hosts in, the host group name can be wnt.
A host group name can consist of up to 32 ASCII characters (letters, numerals, and symbols).
However, you cannot use the following symbols for host group names:
\ / : , ; * ? " < > |
You cannot use spaces for the first and last characters in host group names.
Host group names are case-sensitive. For example, host group names wnt and Wnt represent different
host groups.
4. In the Host Mode list, select a host mode. When selecting a host mode, you must consider the platform
and other factors (see Table 16).
CAUTION: Do not select Reserve from the list. Reserve indicates that the host mode is not currently
supported.
5. If necessary, click Option, and select the host mode options. For more information about host mode
options, see Table 17 on page 77.
Figure 36 Add New Host Group pane (Option selected)

6. Click OK. If a message appears, click OK. The host group name and host mode appear in blue.
7. Click Apply. A confirmation message appears.
8. Click OK. Settings are applied to the array.
Table 16 Host modes for host groups
Host mode1 When to select this mode

00 Standard When registering Red Hat Linux or IRIX server hosts in the host group
03 HP When registering HP-UX server hosts in the host group
04 Sequest When registering DYNIX/ptx server hosts in the host group
05 OpenVMS When registering OpenVMS server hosts in the host group
07 Tru64 When registering Tru64® server hosts in the host group
09 Solaris When registering Solaris® server hosts in the host group
0A NetWare When registering NetWare® server hosts in the host group
0C Windows When registering Windows server hosts in the host group2
0F AIX When registering AIX® server hosts in the host group
2C Windows Extension When registering Windows server hosts in the host group2
4C UVM When registering another array in the host group for mapping by External Storage XP.
(Use this mode to map logical volumes in the array on which LUN manager is installed
to another array on which External Storage XP is installed as the data is succeeded
with the same emulation type.)
1. Besides the host modes mentioned here, the Host Mode list displays the Reserve mode. Do not select this host mode.
2. If you register Windows server hosts in a host group, ensure that the host group’s host mode is 0C Windows or 2C Windows
Extension. If you are thinking about creating LUSE volumes (that is, expanded LUs), consider setting the host group’s host mode
to 2C Windows Extension.
If the host group’s host mode is 0C Windows and an LU path is defined between the host group and a logical volume, you
cannot combine the logical volume with other logical volumes to form a LUSE volume (that is, an expanded LU). For more
information about LUSE, see ”Overview of Volume Manager and Custom Volume Size” on page 127.
Table 17 Host mode options
No. Host mode option When to select this option

2 VERITAS Database When VERITAS Database Edition/Advanced Cluster for Real Application Clusters
Edition/Advanced or VERITAS Cluster Server 4.0 (I/O fencing function) is used
Cluster
6 TPRLO When all the following conditions are satisfied:

• Host mode 0C Windows or 2C Windows Extension is used
• Emulex host bus adapters are used
• Mini-port drivers are used
• TPRLO=2 is specified for the host bus adapter’s mini-port driver parameter
7 Automatic When all the following conditions are satisfied:

recognition function
• Host mode 00 Standard or 09 Solaris is used
of LUN
• SUN StorEdge SAN Foundation Software Version 4.2 or later is used
• You want to automate recognition of increase and decrease of devices when
a genuine SUN HBA is connected
12 Undisplay function of When all the following conditions are satisfied:

ghost LUN
• Host mode 03 HP is used
• You want to suppress creation of device files for devices to which paths are
not defined
Table 17 Host mode options (continued)
No. Host mode option When to select this option

13 SIM report at link When you want to be informed by service information message (SIM) that the
failure number of link failures detected between ports exceeds the threshold.
14 HP TruCluster with When all the following conditions are satisfied:

Continuous Access
• Host mode 07 Tru64 is used
XP function
• You want to use TruCluster to set a cluster to the Continuous Access XP P-VOL
and S-VOL, respectively
Creating iSCSI targets (when configuring iSCSI environments)

You can connect multiple server hosts on different platforms to one port on the array. When configuring
the system, you must group server hosts connected to the array by iSCSI targets. For example, if HP-UX
and Windows hosts are connected to a port, you must create one iSCSI target for HP-UX hosts and
another iSCSI target for Windows hosts. Next, you must register HP-UX hosts to the corresponding iSCSI
target and register Windows hosts to the other iSCSI target.
The following procedure describes how to create iSCSI targets. The procedure for registering hosts to an
iSCSI target is described in ”Registering hosts in host groups” on page 79.
2. Right-click the port for which you want to create an iSCSI target, and select Add New iSCSI Target. The
Add New iSCSI Target pane appears.
Figure 37 Add New iSCSI Target pane

3. In the Target name box, enter the iSCSI target name.
In the Target name box, the initial value in iqn format appears as a default value. iSCSI target names
must be specified in either of the following formats:
• eui format:
An IEEE 64-bit Extended Unique Identifier used to specify an iSCSI name. The iSCSI name begins
with eui. and is followed by the ID found by the vendor in EUI-64 format similar to the World Wide
Name.
Example: eui.02004567A425678D
• iqn format:
The iSCSI Qualified Name format used to specify an iSCSI name. For more information about
specifying iSCSI names using this format, see the iSCSI-related documentation.
If a host is connected to an iSCSI port, LUN Manager automatically displays the iSCSI name in iqn
format. iSCSI names can include 0 (zero) to 9, and a to f (letters are case-insensitive).
Example: iqn.2006.01.com.hp:iscsi-r500:model-xxx:sn-xxxxxx:lun00
The length of an iSCSI name must be 20 characters in eui format, and up to 223 characters in iqn
format. iSCSI names can include letters, numbers, periods (.), hyphens (-), and colons (:); but cannot
include double-byte characters. iSCSI names are case-insensitive.
4. In the Target alias box, enter the iSCSI target’s alias.

iSCSI target aliases can include letters, numbers, periods (.), hyphens (-), and colons (:); but cannot
include double-byte characters. iSCSI target aliases are case-sensitive. An iSCSI target alias can
consist of up to 32 characters
5. In the Host Mode list, select a host mode. When selecting a host mode, you must consider the platform
and other factors (for more information, see Table 16).
CAUTION: Do not select Reserve from the list. Reserve indicates that the host mode is not currently
supported.
6. If necessary, click Option, and select host mode options. For more information about host mode
Figure 38 Add New iSCSI Target pane (Option selected)
NOTE: After you click Option, the pane expands to display a list of host mode options. The No.
column indicates option numbers. Select the check box for the option you want to specify.
7. Click OK. If a message appears, click OK. The iSCSI target name and host mode appear in blue.
Registering hosts in host groups
NOTE: If you are configuring a NAS environment, you do not need to follow the procedures described
in this section. For instructions, see ”Associating host groups or iSCSI targets to logical volumes” on
page 83.
To set LU paths, you must register hosts in host groups. For example, if HP-UX and Windows hosts are
connected to a port, you must register the HP-UX and Windows hosts separately in two different host
groups.
If you are configuring a Fibre Channel environment, follow the instructions in ”Registering hosts in host
groups (when configuring Fibre Channel environments)” on page 79. If you are configuring an iSCSI
environment, follow the instructions in ”Registering hosts in iSCSI targets (when configuring iSCSI
environments)” on page 81.
Registering hosts in host groups (when configuring Fibre Channel environments)
When registering a host, you must specify the host bus adapter’s WWN. If you are unsure of the host bus
adapter’s WWN, see ”Finding an open-system host’s World Wide Name (WWN)” on page 121.
When registering a host, you can assign a nickname to the host bus adapter. If you assign a nickname,
you can easily identify each host bus adapter in the LUN Manager pane. Although WWNs are also used
to identify host bus adapters, the nickname you assign is more helpful because you can name host bus
adapters after the host installation site or the host owners.
NOTE:
• A nickname can consist of up to 32 ASCII characters (letters, numerals, and symbols). However, you
cannot use the following characters for nicknames:
\ / : , ; * ? " < > |
• You cannot use spaces for the first or last character in nicknames.
• Nicknames are case-sensitive. For example, hp and HP are different nicknames.
2. If the desired host has previously been connected via a cable to another port in the array, take the
following steps:
a. In the WWN name table, select the port to which the host is connected from the Port list.
b. In the WWN name table, select the host bus adapter. From the tree, select a host group, and click
Add WWN.
NOTE: If you are using Windows, you can drag the host bus adapter from the WWN name table
to the host group in the tree. To drag two or more host bus adapters, see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web
Console user guide for XP12000/XP10000/SVS200 for instructions.
Figure 39 Add New WWN dialog box (when registering a host that was previously connected to the
array)
c. To assign a nickname to the host bus adapter, enter the nickname in the Nickname box, and click
OK.
NOTE: If you select two or more host bus adapters, Add New WWN dialog boxes (Figure 39)
appear one after another to let you assign a nickname to each selected HBA. If you do not need to
assign nicknames to HBAs, you can select The remaining WWNs do not need names, and click
OK. If you select this option, the Add New WWN dialog box (Figure 39) no longer appears to
prompt you to assign nicknames.
If the desired host has never been connected via a cable to any port in the array, take the following
steps:
a. In the tree, right-click the host group, and select Add New WWN. The Add New WWN pane
appears.

NOTE: You cannot add WWNs to host groups for initiator ports.
Figure 40 Add New WWN dialog box (registering a host that has never been connected to the array)
b. In the WWN list, select the host bus adapter. If the list does not include the host bus adapter, enter
the WWN in the WWN box.
c. If necessary, enter a nickname for the host bus adapter.
d. Click OK. If a message appears, click OK. The specified WWN and nickname appear below the
selected host group.
4. Click OK. Settings are applied to the array, and the specified host is registered in the host group.
NOTE: If the WWN name table (located in the lower-left corner of the pane) includes the host you want
to register, you can register the host by dragging the host from the WWN name table to the host group in
the tree.
Registering hosts in iSCSI targets (when configuring iSCSI environments)

When registering a host, you must specify the host bus adapter’s iSCSI name.
When registering a host, you can assign a nickname for the host bus adapter. If you assign a nickname,
you can easily identify each host bus adapter in the LUN Manager pane. Although iSCSI names are also
used to identify each host bus adapter, the nickname you assign is more helpful because you can name
host bus adapters after the host installation site or host owners.
NOTE:
• A nickname can consist of up to 32 ASCII characters (letters, numerals, and symbols). However, you
cannot use the following characters for nicknames:
\ / : , ; * ? " < > |
• You cannot use spaces for the first and last characters in nicknames.
• Nicknames are case-sensitive. For example, hp and HP are different nicknames.
2. If the host was previously connected via a cable to another port in the array, take the following steps:
a. In the iSCSI name table, select the port to which the host is connected from the Port list.
b. In the iSCSI name list, select the host bus adapter. From the tree, select an iSCSI target, and click
Add iSCSI name.
Figure 41 Add New iSCSI name pane (registering a host that was previously connected to the array)
• In this list, only iSCSI names of hosts that issued login commands to ports appear. Regardless of
the sessions (Discovery or Normal) or results (Accept or Reject), up to 64 iSCSI names of hosts
that recently issued login commands to each port appear. However, if a host issues more than
one instance of the login command to the same port, the host’s iSCSI name appears only once
in the list.
To register iSCSI names using this list and register multiple hosts collectively to one port, you
must register the iSCSI names to the port before the iSCSI names are deleted from this list. If the
iSCSI names are deleted and you want to redisplay the iSCSI names in this list, you must
reissue the login command from the hosts. In this case, you should operate the hosts that need
to log in, and should not add unnecessary iSCSI names to this list.
• If you are using Windows, you can drag the host bus adapter from the iSCSI name table to the
iSCSI target in the tree. To drag two or more host bus adapters, see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web
Console user guide for XP12000/XP10000/SVS200 for instructions.
c. To assign a nickname to the host bus adapter, enter the nickname in the Nickname box, and click
OK.
NOTE: If you select two or more host bus adapters, Add New iSCSI name panes (Figure 41)
appear one after another to let you assign nicknames to the selected HBAs. If you do not need to
assign nicknames to HBAs, you can select The remaining iSCSI names do not need names, and
click OK. If you select this option, the Add New iSCSI name pane (Figure 41) no longer appears to
prompt you to assign nicknames.
If the host has never been connected via a cable to any port in the array, take the following steps:
a. In the tree, right-click the iSCSI target, and select Add New iSCSI name. The Add New iSCSI name
pane appears.
Figure 42 Add New iSCSI name pane (registering a host that has never been connected to the array)
b. In the iSCSI name list, select the host bus adapter. If the list does not include the host bus adapter,
enter the iSCSI name in the iSCSI name box.
c. If necessary, enter a nickname for the host bus adapter.

d. Click OK. The specified iSCSI name and nickname appear below the selected iSCSI target.
4. Click OK. Settings are applied to the array, and the specified host is registered in the iSCSI target.
Associating host groups or iSCSI targets to logical volumes

Use LUN Manager to define LU paths by associating host groups or iSCSI targets to logical volumes. For
example, if you associate a host group or iSCSI target consisting of three hosts with logical volumes, LU
paths are defined between the three hosts and the logical volumes.
1. Start LUN Manager. The LUN Manager pane (Figure 14 or Figure 15) appears.
2. In the tree, select a host group or iSCSI target.
NOTE: If you are configuring a NAS environment, you must select the User host group.
3. In the CU list above the LDEV table, select a CU number. The LDEV table shows LDEVs in the specified
CU image.
4. In the LDEV table, select a logical volume. In the LU Path table, select LUNs indicated by the icon
(this icon indicates a LUN to which no LU path is defined). Click Add LU Path.
A message appears displaying information about LU paths to be defined.
NOTE:
• If you are using Windows, you can drag a logical volume from the LDEV table to a LUN ( ) in
the LU Path tree. To drag more than one logical volume, see the HP StorageWorks Command
View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user
guide for XP12000/XP10000/SVS200 for instructions.
• When you use the LU Path tree, you can use the CU list to switch between CU images.
Figure 43 Information about LU paths to be defined (Fibre Channel environment)
Figure 44 Information about LU paths to be defined (iSCSI environment)

5. Click OK. Settings are shown in the LU Path table, but not applied to the array yet.
7. Click OK. Settings are applied to the array, and LU paths are defined.
Changing or viewing LU path settings

Deleting LU paths
CAUTION:
• Do not remove LU paths when host I/O is in progress.
• Before deleting a path to a NAS user LU, you must release the device file for the user LU if the device
file is already reserved as the copy destination of a file system. For more information about releasing
and reserving a device file, see the NAS Backup Restore User’s Guide.
2. In the tree, double-click a port. Host groups or iSCSI targets corresponding to that port appear.
3. In the tree, select a host group or iSCSI target. The LU Path table displays information about LU paths
associated with the selected host group or iSCSI target.

4. In the LU Path table, select one or more LUNs to which volumes are assigned. (If a volume is assigned
to a LUN, columns on the right of the LUN column are not empty.)
5. Right-click the selection, and select Release LU Path. A confirmation message appears.
Figure 45 Information about LU paths to be deleted (Fibre Channel environments)
Figure 46 Information about LU paths to be deleted (iSCSI environments)

6. Click OK. The selected LU path is removed from the table.
8. Click OK. Settings are applied to the array, and the specified LU paths are deleted.
NOTE: If you delete numerous paths at one time, the deletion process might take time and the
pane might seem to hang temporarily.
Changing a host group’s name and host mode
NOTE:
• You cannot perform this operation on host groups for initiator ports.
• You cannot perform this operation on host groups for NAS ports.
CAUTION: Before changing a host group’s host mode, HP recommends that you first back up data on
the port the host group belongs to. The operation for changing the host mode should not be destructive,
but data integrity cannot be guaranteed without a backup.
2. In the tree, right-click the host group, and select Change Host Group. The Change Host Group dialog
box appears.
Figure 47 Change Host Group dialog box

3. To change the name of the host group, enter a new name in the Group Name box.
To change the host mode (Table 16), select the new host mode from the Host Mode list.
4. If necessary, click Option, and select host mode options. For more information about host mode
Figure 48 Change Host Group dialog box (Option selected)
column indicates option numbers. Select the check box for the option you want to specify.
5. Click OK. Changes are indicated in blue in the table.

7. Click OK. Changes to the host group name and host mode are applied to the array.
Changing an iSCSI target’s name and host mode
NOTE: You cannot perform this operation on iSCSI targets for initiator ports.

CAUTION: Before changing an iSCSI target’s host mode, HP recommends that you first back up data on
the port the iSCSI target belongs to. The operation for setting the host mode should not be destructive, but
data integrity cannot be guaranteed without a backup.
2. In the tree, right-click the iSCSI target, and select Change iSCSI Target. The Change iSCSI Target pane
appears.
Figure 49 Change iSCSI Target pane

3. To change the iSCSI target’s name, enter a new name in the Target name box.
To change the alias, enter a new alias in the Target alias box. iSCSI target aliases can include letters,
numbers, periods (.), hyphens (-), and colons (:); but cannot include double-byte characters. iSCSI
target aliases are case-sensitive. An iSCSI target alias can consist of up to 32 characters
To change the host mode (see Table 16), select the new host mode from the Host Mode list.
4. If necessary, click Option, and select the host mode options. For more information about host mode
Figure 50 Change iSCSI Target pane (Option selected)
column indicates option numbers. Select the check box of the option you want to specify.
5. Click OK. Changes are indicated in blue in the tree.

7. Click OK. Changes to the iSCSI target name and host mode are applied to the array.
Deleting host groups
NOTE:
• You cannot perform this operation on host groups for NAS ports.
• You cannot delete host group 0 (zero). To remove all WWNs and LU paths from host group 0, you
must initialize host group 0 (for more information, see ”Initializing host group 0 (zero)” on page 88).
2. In the tree, right-click the desired group, and select Delete Host Group. A confirmation message
appears.
3. Do either of the following:
• To delete all WWNs and the host group, click Yes.
• To delete the host group but not the WWNs in the host group, click No.
Deleting iSCSI targets
NOTE: You cannot delete iSCSI target 0 (zero). To remove all iSCSI names and LU paths from iSCSI
group 0, you must initialize iSCSI group 0 (for more information, see ”Initializing iSCSI target 0 (zero)”
on page 88).
2. In the tree, right-click the iSCSI target, and select Delete iSCSI Target. A confirmation message
appears.
• To delete all iSCSI names and the iSCSI target, click Yes.
• To delete the iSCSI target but not the iSCSI names in the iSCSI target, click No.
Initializing host group 0 (zero)

If you follow the procedure below, host group 0 (zero) is set to its initial state. This procedure removes all
WWNs from host group 0 and also removes all LU paths related to host group 0. This procedure also
changes host group 0’s host mode to Standard and initializes the host group name. For example, if you
initialize host group 0 for port CL1-A, host group 0’s name changes to 1A-G00.
NOTE: You cannot perform this operation on host groups for NAS ports.
2. In the tree, right-click host group 0, which is preceded by 00, and select Clear Host Group. A
confirmation message appears.
3. Click Yes.
Host group 0’s host mode and host group name change in the tree. WWNs are also removed from
host group 0.
LU paths are removed from the table on the right of the tree. LUNs corresponding to the removed LU
paths appear in blue.
Initializing iSCSI target 0 (zero)

If you follow the procedure below, iSCSI target 0 (zero) is set to its initial state. This procedure removes all
LU paths related to iSCSI target 0. This procedure also changes iSCSI target 0’s host mode to Standard
and initializes the iSCSI target name. After this procedure, the iSCSI target’s name changes to its default
name.

2. In the tree, right-click iSCSI target 0, which is preceded by 00, and select Clear Host Group. A
confirmation message appears.
3. Click YES.
iSCSI target 0’s host mode and host group name are changed in the tree. iSCSI names are also
removed from iSCSI target 0.
LU paths are removed from the table on the right of the tree. LUNs corresponding to removed LU paths
appear in blue.
5. Click OK. Changes are applied to the array.
Changing a host bus adapter’s WWN and nickname

In Fibre Channel environments, you can identify host bus adapters by WWNs or nicknames.
2. In the tree, double-click the Fibre folder. A list of Fibre Channel ports appears.
3. In the tree, double-click the Fibre Channel port to which the host bus adapter is connected.
4. In the tree, right-click a host bus adapter ( ), and select Change WWN & Nickname. The Change
WWN & Nickname dialog box appears.
Figure 51 Change WWN & Nickname dialog box

5. To change the WWN, enter a new WWN or select another WWN from the WWN list.
To change the nickname, enter a new nickname In the Nickname box.
6. If necessary, select Apply this change to other ports, too.
If this check box is selected, the change in the pane also affects other ports. For example, suppose that
the same host bus adapter (that is, the same WWN) is located below ports CL1-A and CL2-A in the
tree. If you select the host bus adapter (or WWN) from below one of the ports and change the
nickname to hba1, the host bus adapter below the other port is also renamed to hba1.
NOTE: The change in the pane does not affect any port that satisfies one of the following
conditions:
• The resulting nickname is already used as the nickname of a host bus adapter connected to the
port.
• The resulting WWN exists in the port.
7. Click OK. If a confirmation message appears, click OK. Changes appear in blue in the tree.
NOTE: If you select Apply this change to other ports, too, and click OK, the Check WWNs dialog
box appears and lists the host bus adapters to be changed. To make the changes, click OK. If not,
click Cancel.
Figure 52 Check WWNs dialog box

Changing a host bus adapter’s iSCSI name and nickname

In iSCSI environments, host bus adapters can be identified by iSCSI names or nicknames.
2. In the tree, double-click the iSCSI folder. A list of iSCSI ports appears.
3. In the tree, right-click a host bus adapter ( ), and select Change iSCSI name & Nickname. The
Change iSCSI name & Nickname pane appears.
Figure 53 Change iSCSI name & Nickname pane

4. To change the iSCSI name, enter a new iSCSI name or select another iSCSI name in the iSCSI name
list.
To change the nickname, enter a new nickname in the Nickname box.
5. If necessary, select Apply this change to other ports, too.
If this check box is selected, the change in the pane also affects other ports. For example, suppose the
same host bus adapter (that is, the same iSCSI name) is located below ports CL1-A and CL2-A in the
tree. If you select the host bus adapter (or iSCSI name) from below one of the ports and change the
nickname to hba1, the host bus adapter below the other port is also renamed to hba1.
NOTE: The change in the pane does not affect any port that satisfies one of the following
conditions:
• The resulting nickname is already used as the nickname of a host bus adapter connected to the
iSCSI target.

• The resulting iSCSI name exists in the port.
6. Click OK. If a confirmation message appears, click OK. Changes appear in blue in the tree.
NOTE: If you select Apply this change to other ports, too and click OK, a pane appears
(Figure 54) listing the host bus adapters to be changed. To make changes, click OK. If not, click
Cancel.
Figure 54 Check iSCSI names dialog box

8. Click OK. Changes are applied to the array.
Deleting host bus adapters from host groups
2. In the tree, right-click a host bus adapter ( ), and select Delete WWN. A confirmation message
appears.
3. Click Yes.
Deleting host bus adapters from iSCSI targets
2. In the tree, right-click a host bus adapter ( ), and select Delete iSCSI Name. A confirmation message
appears.
3. Click YES.
Deleting unneeded WWNs from the WWN name table
If you disconnect a host that was connected via a cable to the array, the host’s WWN remains in the
WWN name table on the LUN Manager pane.
2. In the WWN name table, locate WWNs that are not registered in any host group. (If the Host Group
column is blank, the WWN is not registered in any host group.) From these WWNs, right-click the
WWN you want to delete, and select Erase WWN.
Deleting (initializing) unneeded iSCSI names

If you disconnect a host that was connected via a cable to the array, the host’s iSCSI name remains in the
iSCSI name list on the LUN Manager pane.
2. In the LU Path tree, right-click the iSCSI folder, and select Initialize iSCSI name.
NOTE: If there are no unneeded iSCSI names, the shortcut menu does not appear.

Viewing a list of concatenated parity groups

The array supports concatenation of parity groups. If parity groups are concatenated, a logical volume
can be dispersed across the concatenated parity groups. Dispersal of logical volumes can provide faster
access to data (particularly faster sequential access to data).
NOTE: Only HP maintenance personnel can concatenate parity groups. If you have questions about
concatenation of parity groups, contact you HP account support representative.
You can confirm whether a logical volume is dispersed across two or more parity groups. If the logical
volume is dispersed across parity groups, a pane appears and displays a list of the parity groups.
2. In the LDEV table, right-click a logical volume (that is, an LDEV).
3. Check to see if Concatenation List appears in the shortcut menu.

• If Concatenation List appears, the logical volume is dispersed across parity groups. Select
Concatenation List to view a list of the parity groups.
Figure 55 Concatenation List pane

• If the Concatenation List command does not appear, the logical volume is not dispersed across
parity groups.
Defining and viewing alternate paths

Use LUN Manager to define alternate paths. If an LU path fails, you can switch to its alternate path.
To create an alternate path, you must copy the original path from one port to another. For example, to
define an alternative for the LU path from port CL1-A to logical volume 00:01, you must copy the LU path
from port CL1-A to another port.
Copying paths from one Fibre Channel or iSCSI port to another

To use alternate paths, you must copy LU paths from one port to another.
CAUTION: Before performing the following steps, see ”Notes on using LUN Manager” on page 53 for
important information.
CAUTION: To define alternate paths when LUN security is disabled, you must redefine the LU path.
2. In the tree, double-click the copy source port to display host groups or iSCSI targets below the port.
3. To copy all LU paths defined to a host group, complete the following steps to copy the host group or
iSCSI target:
a. In the tree, right-click the host group, and select Copy. The selected host group or iSCSI target turns
green.
NOTE: If you right-click a host group or iSCSI target for an initiator port, you cannot copy paths.
b. Right-click the copy destination port, and select Paste. If a confirmation message appears, click
OK.
NOTE: You cannot paste paths to initiator port.
To copy one or more (but not all) LU paths defined to a host group or iSCSI target, complete the
following steps:
a. In the tree, select the host group or iSCSI target.
b. In the LU Path table, select one or more LUNs to which volumes are assigned. (If a volume is
assigned to a LUN, columns on the right of the LUN column are not empty.)
c. Right-click the selection, and select Copy Paths. The selected LUNs turn green.
d. Double-click the copy destination port to display host groups or iSCSI targets below the port.
e. Right-click the host group to which you want to paste paths, and select Paste Paths. If a
confirmation message appears, click OK.
NOTE: You cannot paste paths to host groups or iSCSI targets for initiator ports.

Copying paths from one NAS port to another
CAUTION: Before taking the following steps, see ”Notes on using LUN Manager” on page 53 for
1. Start LUN Manager, and display the LUN Manager pane (Figure 14).
2. To specify the LU paths you want to copy:
a. In the tree, double-click a NAS port (copy source port), and select the User host group.
b. From the LU Path list, select one or more LUNs to which volumes are assigned. If a volume is
assigned to a LUN, columns on the right of the LUN column are not empty.
3. To paste the LU paths:
a. In the tree, double-click the copy destination port (NAS port). The User host group appears below
the port.
b. Right-click the User host group, and select Paste Paths.
Copying paths from a Fibre Channel or iSCSI port to a NAS port
1. Start LUN Manager, and display the LUN Manager pane (Figure 14 or Figure 15).
a. In the tree, double-click a Fibre Channel or iSCSI port (copy source port), and select a host group
or iSCSI target. The LU Path list displays information about LU paths.
b. In the list, select one or more LUNs to which volumes are assigned. If a volume is assigned to a
LUN, columns on the right of the LUN column are not empty.
a. In the tree, double-click a NAS port (copy destination port). The User host group appears below
the port.
b. Right-click the User host group, and select Paste Paths.

Copying paths from a NAS port to a Fibre Channel or iSCSI port
1. Start LUN Manager, and display the LUN Manager pane (Figure 14 or Figure 15).
a. In the tree, double-click a NAS port (copy source port), and select the User host group.
b. From the LU Path list, select one or more LUNs to which volumes are assigned. If a volume is
assigned to a LUN, columns on the right of the LUN column are not empty.
a. Double-click the Fibre Channel or iSCSI port (copy destination port). Host groups or iSCSI targets
appear below the port.
b. Right-click the host group or iSCSI target to which you want to paste paths, and select Paste Paths.
If a confirmation message appears, click OK.
NOTE: You cannot paste paths to host groups or iSCSI targets for initiator ports.

Viewing a list of alternate paths

• In the LU Path list, right-click a LUN, and select Alternate Paths.
NOTE: If nothing appears in the table cells to the right of a LUN, no path is defined to the LU.
Therefore, no alternative path is defined to the LU.
• In the LDEV table, right-click a logical volume (that is, an LDEV), and select Alternate Paths.
NOTE: If nothing appears in the Paths column for a row in the LDEV list, no alternate paths are
defined to the LDEV corresponding to that table row.
When you finish the operation, the Alternate Paths pane appears and displays a list of alternate paths.
In the Alternate Paths pane, each table row indicates an alternate path.
Figure 56 Alternate Paths pane
NOTE: The Group ID column indicates the host group’s group numbers (G-IDs).
Using LUN security

To protect mission-critical data in the array from illegal access, you must secure the logical volumes in the
array. Use LUN Manager to secure LUs from illegal access by enabling LUN security on ports. For more
information, see ”Configuring LUN security” on page 23.
By default, LUN security is disabled on each port. When configuring the system, you must enable LUN
security on ports.
NOTE:
Enabling LUN security
NOTE:
2. In the tree, locate the port.
3. See the text on the right of the port name to find the LUN security status.
• If LUN security is enabled, you do not need to perform the remaining steps.
• If LUN security is disabled, go to step 4.
4. Right-click the port, and select LUN Security: Disable->Enable. A confirmation message appears.
5. Click Yes. A key is added to the port icon.

7. Click OK. Changes in the security settings are applied to the array.
Disabling LUN security
CAUTION: Do not disable LUN security on ports when host I/O is in progress.
2. In the tree, locate the port.
3. See the text to the right of the port name to find the LUN security status.
• If LUN security is disabled, you do not need to perform the remaining steps.
• If LUN security is enabled, go to step 4.
4. Right-click the port, and select LUN Security: Enable -> Disable. A confirmation message appears.
5. Click YES. The key is removed from the port icon.
7. Click OK. Changes in the security settings are applied to the array.
NOTE: If LUN security is disabled on a port, host groups corresponding to that port are grayed out in the
tree (except for host group 0).
Configuring arrays for using RAID Manager XP commands

The system administrator can enter RAID Manager XP commands from open-system hosts to perform
Continuous Access XP and Business Copy XP operations on logical devices. For example, use RAID
Manager XP commands to create and split pairs. To enable the system administrator to enter RAID
Manager XP commands from open-system hosts, you must specify at least one logical device as the
command device. If desired, you must also apply command device security to other logical devices in the
array.
NOTE: If an array is divided into SLPRs and you want to prevent RAID Manager XP commands from
affecting multiple SLPRs, you must apply command device security to the logical volumes.
Specifying logical devices as command devices

To enable the system administrator to execute RAID Manager XP commands from an open-system host,
you must select at least one logical device that will not be manipulated by Continuous Access XP or
Business Copy XP, and then specify the devices as the command devices. When a RAID Manager XP
command is issued from a host, the command device receives the command. The command device
transfers the command to another logical device. Then, the command performs a Continuous Access XP or
Business Copy XP operation on that logical device.
2. In the LU Path or LDEV table, right-click the logical device.
NOTE:
• If nothing appears in the LU Path table, select a host group in the tree.
• The and icons indicate command devices.
• The icon does not indicate any logical device.
3. Select Command Device: Disable->Enable. A confirmation message appears.

4. Click Yes.
NOTE: If you do not want to use a device as a command device any longer, right-click the command
device ( or ) in the LU Path or LDEV table, and select Command Device: Enable -> Disable.
Protecting logical devices from RAID Manager XP commands

To protect logical volumes from RAID Manager XP commands, you must apply command device security
to the logical volumes. If command device security is applied to a logical device, the logical device is not
affected by RAID Manager XP commands issued via command devices from hosts.
2. In the LU Path or LDEV table, right-click the command device.
NOTE:
• If nothing appears in the LU Path table, select a host group ( ) in the tree.
• The icon indicates a logical volume to which command device security is already applied.
• The icon does not indicate any logical device.
3. Select Cmd. Dev. Security: Disable -> Enable. A confirmation message appears.
4. Click OK.
NOTE: To remove command device security from a logical device, right-click the logical device ( ) in
the LU Path or LDEV table, and select Cmd. Dev. Security: Enable -> Disable.
Defining remote command devices

A remote command device is a device in the array to which a command device in the external array is
mapped.
As you send RAID Manager XP commands to the remote command device, these RAID Manager XP
commands are sent to the external array’s command device to perform RAID Manager XP operations on
the external array.
You can map a command device as a remote command device when one of the following arrays is
connected as an external array:
• XP12000 Disk Array
• XP10000 Disk Array
• HP 200 Storage Virtualization System
• XP1024/XP128 Disk Array
• TagmaStore Universal Storage Platform subsystem
• TagmaStore Network Storage Controller subsystem
• TagmaStore Adaptable Modular Storage subsystem
• TagmaStore Workgroup Modular Storage subsystem
• Lightning 9900V series subsystem
• Thunder 9500V series subsystem
For more information about defining remote command devices, see the HP StorageWorks External
Storage XP user guide.

Configuring Fibre Channel ports
Use the Port pane (Figure 21) to configure Fibre Channel ports in the array. You can also use this pane to
modify the port configuration when the system is operating.
NOTE: You cannot configure Fibre Channel ports and perform operations related to NAS channel
adapters at the same time. Therefore, when you perform operations on a NAS channel adapter first in the
Port pane, you cannot configure Fibre Channel ports. Click Apply once to apply changes to the array,
and then configure the Fibre Channel port.
Specifying Fibre Channel topologies

The term topology refers to how devices are connected to each other. For more information, see ”Fibre
Channel topologies” on page 25.
1. Start LUN Manager, and display the Port pane (Figure 21).
2. In the Package tree, select the Fibre folder or a Fibre Channel channel adapter.
• If you select the Fibre folder, the Port table displays a list of Fibre Channel ports in the array.
• If you select a channel adapter, the Port table displays a list of Fibre Channel ports on the channel
adapter.
3. In the Port table or Select a Port list, select a port. The Change Port Mode box displays information
about the selected port.
4. If you are using a fabric switch, select Enable in the Fabric list.
If you are not using a fabric switch, select Disable in the Fabric list.
5. In the Connection list, select FC-AL or P-to-P.
NOTE: If you are using a fabric switch, see the fabric switch’s documentation to check if the
fabric switch requires the point-to-point topology. Some fabric switches require the point-to-point
topology to get the system running. To specify the point-to-point topology, select P-to-P.
6. Click Set. A confirmation message appears.

7. Click OK. Settings are applied to the Port table, but not to the array. Changes are indicated in blue.
Addressing Fibre Channel ports

When configuring a system, you must assign addresses to Fibre Channel ports. For more information, see
”Fibre Channel port addresses” on page 26.
NOTE: For more information about Fibre Channel device addressing, see the array’s documentation.
2. In the Package tree, select the Fibre folder or select a Fibre Channel channel adapter.
adapter.
about the selected port.
4. In the Fibre Addr. list, select an address.
Specifying a Fibre Channel port’s data transfer speed

You can adjust the data transfer speed for Fibre Channel ports to optimize system performance. For more
information, see ”Data transfer speed for Fibre Channel ports” on page 27.
2. In the Package tree, select the Fibre folder or a Fibre Channel channel adapter.
adapter.
about the selected ports.
4. In the Host Speed list, select the data transfer speed.
Switching between Standard, High Speed, and Initiator/External MIX mode

Channel adapter boards (PCB: printed circuit board) take Standard, High Speed, or Initiator/External
MIX mode. You can apply High Speed mode to channel adapters to improve system performance. Or you
can apply Initiator/External MIX mode so that one port can be used both as an initiator port for
Continuous Access XP or Continuous Access XP Journal and as an external port applied to a remote
command device. Be aware that you can only apply High Speed or Initiator/External MIX mode to
channel adapters that satisfy certain requirements. For more information, see ”Standard, High Speed,
and Initiator/External MIX modes” on page 27. For instructions on defining remote command devices,
see the HP StorageWorks External Storage XP user guide.
2. In the Package tree, double-click the Fibre folder. The tree displays a list of CHA (Fibre Channel
channel adapter) packages.
3. Double-click a channel adapter icon ( , , or ) to display port blocks.
• The icon indicates a block of ports in Standard mode.
• The icon indicates a block of ports in High Speed mode.
• The icon indicates a block of ports in Initiator/External MIX mode.
4. Do one of the following:
• To change the mode of a block of ports from Standard to High Speed or Initiator/External MIX,
right-click the icon, and select High Speed Mode/MIX Mode.
• To change the mode of a block of ports from High Speed to Standard, right-click the icon, and
select Standard Mode.
• To change the mode of a block of ports from Initiator/External MIX mode to Standard, right-click
the icon, and select Standard Mode.
A confirmation message appears.
5. Click OK.
NOTE: Storage partition administrators cannot apply High Speed or Initiator/External MIX mode.

Making settings on iSCSI ports and iSNS servers
Use the Port pane (Figure 22) to configure iSCSI ports in the array. You can also use this pane to make
settings on iSNS servers and modify settings when the system is operating.
Making settings on iSCSI ports

2. In the Package tree, select the iSCSI folder. The Port table displays a list of iSCSI ports in the array.
NOTE: If you specify a channel adapter in the Package tree, the Port table displays only ports in
the specified channel adapter.
3. In the Port table or Select a Port list, select an iSCSI port. The iSCSI port’s current configuration
appears below the Select a Port list.
4. To make settings on the iSCSI port, edit items below the list. For more information about the items, see
”iSCSI port and iSNS server settings” on page 42.
NOTE: Use the vertical scroll bar to view all items.

6. Click OK. Settings are applied to the Port table, but not to the array. Changes appear in blue.
Making settings on iSNS servers

You can register iSCSI ports to the iSNS server by clicking Register or delete iSCSI ports from the iSNS
server by clicking Delete.
2. In the iSCSI Function box, click Register or Delete. The Register Ports to iSNS Server or Delete Ports
from ISNS Server pane appears.
Figure 57 Register Ports to iSNS Server pane
Figure 58 Delete Ports from iSNS Server pane
3. From the iSCSI Ports list, select an iSCSI port. iSCSI port information appears in the Ports to be
Registered or Ports to iSNS Deleted list.
Use Add or Delete to move information between the lower and upper lists.
4. Click OK. The Result of Registration to iSNS Server or Result of Deletion from iSNS Server pane
appears. Information about the iSCSI port is removed from the iSNS server; the iSCSI port is
unregistered from the iSNS server.
Figure 59 Result of Registration to iSNS Server pane
Figure 60 Result of Deletion from iSNS Server pane

Checking the status of the connection between hosts and the array
(iSCSI environments only)
In iSCSI environments, use LUN Manager to issue a ping command from an array port to a host. The ping
command checks whether the host and array can communicate with each other. If the host responds to the
ping command, the host and array can communicate with each other.
2. Click Ping below the Package tree. The Ping pane appears.
Figure 61 Ping pane

3. From the From (Subsystem Port) list, select an iSCSI port.
4. In To (IP Address) box, enter the host’s IP address.
5. Click OK.
A ping command is issued from the iSCSI port to the host five times. After the ping command is issued
five times, the Ping Status pane appears and displays the results of the first to fifth attempts at issuing
the ping command. The results appear in the order attempts were made.
Figure 62 Ping Status pane

6. On the Ping Status pane, check the results of the ping command.
• If the host responded to the ping command, the Status column displays Success.
• If the host did not respond to the ping command, the Status column displays Error.
• The Success Rate field displays the ping command’s success rate. If the host responds to each of the
five ping attempts, the success rate is 100 percent. If the host responds three times out of five ping
attempts, the success rate is 60 percent.
7. Click OK.
8. To issue a ping command, return to step 3.
Otherwise, click Cancel.
TIP: You can issue a ping command from an iSCSI port to an iSNS server. To verify connectivity
between an iSNS server and the array, issue a ping command to the iSNS server. If the iSNS responds to
the ping command, the iSNS server and array can communicate with each other.
Setting user authentication (Fibre Channel environments)
When configuring Fibre Channel environments, use the Authentication pane (Figure 30 and Figure 31) to
set user authentication on host groups, Fibre Channel ports, and Fibre Channel switches of the array.
For an overview of user authentication, see ”User authentication (Fibre Channel environments)” on
page 43.
NOTE: The hosts to be connected must also be configured for authentication by host groups (and for
authentication of host groups by the host, if required). For more information about configuring the host for
CHAP authentication, see the documentation for the operating system and Fibre Channel driver in your
environment.
Enabling and disabling authentication of hosts in host groups

You can specify whether to perform authentication of hosts on each host group. Switch the user
authentication settings of host groups to enable or disable authentication of hosts. By default, user
authentication is disabled.
To enable authentication of hosts on a host group:
1. Start LUN Manager, and display the Authentication pane (Figure 31).
2. In the Port tree, double-click the Subsystem folder. If the array contains Fibre Channel adapters, the
Fibre folder appears below the Subsystem folder.
3. Under the Fibre folder, double-click the Fibre folder and Fibre Channel port icon.
If you double-click the Fibre folder, Fibre Channel ports in the array appear as icons.
If you double-click a Fibre Channel port, host groups appear as icons. The host group name appears
on the right of each icon. When appears, the host group performs authentication of hosts. When
appears, the host group does not perform authentication of hosts. By default, appears for all
host group icons.
4. Right-click a host group displayed with , and select Authentication : Disable -> Enable. The host
groups icon changes to , and the port name appears in blue.
To return the host group setting to , perform the same operation, except select Authentication : Enable
-> Disable in step 4.
Registering a host’s user information on a host group

On a host group that performs authentication of hosts, register the user information for all hosts you allow
to connect.
2. In the Port tree, select the port or host group on which you want to register a host’s user information.
The user information for hosts currently registered on the selected port or host group appears in the
Authentication Information (Host) list.
You can register a host’s user information even if the port status is . In this case, however, the host’s
registered user information is ignored.

3. Right-click any point in the Authentication Information (Host) list, and select Add New User
Information. The Add New User Information (Host) pane appears.
Figure 63 Add New User Information (Host) pane

Specify the following user information for the host you want to allow to connect:
• Group Name: Host bus adapter’s group name. Select one from the list. All group names of host bus
adapters connected to the selected port by the cable appear in the list.
• User Name: Host bus adapter’s WWN, up to 16 characters. You can use alphanumeric characters
in a user name.
• Secret: Secret (that is, a password used in CHAP authentication) between 12 to 32 characters. You
can use alphanumeric characters, spaces, and the following symbols in a secret:
. - + @ _ = : / [ ] , ~
• Re-enter Secret: Specify the secret, again, for confirmation.
• Protocol: Protocol used in the user authentication. This protocol is fixed to CHAP.
4. Click OK. The specified host user information appears in blue in the Authentication Information (Host)
list.
NOTE: You should register user information for all hosts to be connected to a host group that performs
authentication of hosts. To allow a specific host to connect to such a host group without authentication,
configure the host group and the host as follows.
• On the host:
It does not matter if you configure the host for authentication by ports with CHAP.
Changing a host’s user information (Fibre Channel environments)

You can change the host’s registered user name or secret, and switch authentication settings between
Enable and Disable after registration.
NOTE: You cannot change the WWN when you change user information.
2. In the Port tree, expand the Fibre folder, and select a port or host group on which the user information
you want to change is registered. All user information for hosts registered on the selected port or host
group appears in the Authentication Information (Host) list.
3. In the User Information (Host) list, right-click the user information item you want to change, and select
Change User Information. The Change User Information (Host) pane appears.
Figure 64 Change User Information (Host) pane

4. Change the host’s user information.
You can change the User Name and Secret. For more information about available characters and
length in the user name or secret, see ”Registering a host’s user information on a host group” on
page 104.
5. Click OK. The host’s user information appears in blue in the Authentication Information (Host) list.
Deleting a host’s user information (Fibre Channel environments)

2. In the Port tree, expand the Fibre folder, and select the port or host group on which the user
information you want to delete is registered. The user information for hosts currently registered on the
selected port or host group appears in the Authentication Information (Host) list.
3. In the Authentication Information (Host) list, right-click the user information item you want to delete,
and select Delete User Information. The Delete Authentication Information pane appears.
Figure 65 Delete Authentication Information pane

4. Click OK.

Specifying a host group’s user information (when performing mutual
authentication)
To perform mutual authentication, you must specify user information for host groups on array’s ports.
Specify unique user information for each host group. You can change the specified user information for
host groups the same way you specified them initially.
1. Start LUN Manager and display the Authentication pane (Figure 31).
2. In the Port tree, select the port or host group whose user information you want to specify. Currently
registered user information for the selected port or host group appears in the Authentication
Information (Target) list.
3. Right-click any point in the Authentication Information (Target) list, and select Specify Authentication
Information. The Specify Authentication Information pane appears.
Figure 66 Specify Authentication Information pane

Specify the following user information for the port or host group selected in the Port tree:
• Port Name: Selected port’s port name. You cannot change the port name.
• User Name: Host group’s user name, up to 16 characters. You can use specified alphanumeric
characters. User names are case-sensitive.
can use alphanumeric characters, spaces, and the following symbols in a secret:
. - + @ _ = : / [ ] , ~
4. Click OK. The specified user information for the port appears in blue in the Authentication Information
(Target) list.
Clearing a host group’s user information (when performing mutual authentication)

2. In the Port tree, expand the Fibre folder, and select the port or host group whose user information you
want to clear. The currently registered user information for the port or host group appears in the
Authentication Information (Target) list.
3. Right-click any point in the Authentication Information (Target) list, and select Clear Authentication
information. The Clear Authentication Information pane appears.
4. Click OK. The selected host group’s user information disappears from the Authentication Information
(Target) list.
Settings and connection results in authentication of hosts (Fibre Channel

environments)
During authentication of hosts, the connection result is determined based on the combination of the
following host group settings:
• Host group’s setting in the Port tree: enable ( ) or disable ( )
• Whether or not the user information for the host that attempts to connect is registered on the host group
Table 18 shows the relationship between combinations of host group settings and connection results in
authentication of hosts. Regardless of whether or not the host is configured for authentication by ports with
CHAP, the connection results are as follows, unless otherwise noted.
Table 18 Combinations of port settings and connection results (Fibre Channel environments)
Port settings Host settings Connection results

Authentication: at host Host’s user information
group
Enable Registered Registered Connected if the authentication of
the host succeeded
Enable Registered Not registered Failed to be authenticated and

cannot be connected
Enable Not registered Registered Failed to be authenticated and

cannot be connected
Disable —1 —1 Connected without authentication
of the host2
1. This item does not affect the connection results, or cannot be specified.
2. If a host is configured for authentication by ports with CHAP, authentication of the host fails. To allow such a host to connect to
the port without authentication, do not configure it for authentication by ports with CHAP.
For more information about authentication of hosts, see ”Authentication of hosts (Fibre Channel
environments)” on page 45.
Settings and connection results in authentication of Fibre Channel switches

following port settings:
• Port’s setting in the Port tree: enable ( ) or disable ( )
• Whether or not the user information for the Fibre Channel switch that attempts to connect is registered
on the port
Table 19 shows the relationship between combinations of port settings and connection results in
authentication of Fibre Channel switches. Regardless of whether or not the host is configured for
authentication by Fibre Channel switches with CHAP, the connection results are as follows, unless
otherwise noted.
Table 19 Combinations of Fibre Channel settings and connection results
Port settings Fibre Channel Connection results

switch settings
Authentication: at Fibre Fibre Channel switch’s
Channel switch user information
the Fibre Channel switch succeeded

cannot be connected

cannot be connected
Disable —1 —1 Connected without authentication of

the Fibre Channel switch2
2. If a Fibre Channel switch is configured for authentication by ports with CHAP, authentication of the host fails. To allow such a
Fibre Channel switch to connect to the port without authentication, do not configure it for authentication by ports with CHAP.

For more information about authentication of hosts, see ”Authentication of Fibre Channel switches” on
page 47.
Specifying a Fibre Channel port’s information

To perform user authentication in Fibre Channel environments, you must specify information for the Fibre
Channel ports of the array.
Fibre folder appears below the Subsystem folder. The port’s information appears in the Port
Information list.
3. Right-click any point in the Port Information list, and select Port Information. The Set Port Information
pane appears.
Figure 67 Set Port Information pane

Specify the following port information:
• Time out: Time period starting when authentication fails and ending when the next authentication
session ends. This time period is between 15 to 60 seconds. The initial value is 45 seconds.
• Refusal Interval: Interval beginning when the connection to a port fails and ending when the next
authentication session starts, up to 60 minutes. The initial value is 3 minutes.
• Refusal Frequency: Number of times authentication for connection to a port is allowed, up to 10
times. The initial value is 3 times.
4. Click OK.
Registering a Fibre Channel port’s user information

3. In the Port tree, double-click the Fibre folder. Information about the port appears in the tree.
4. Right-click any port icon in the Port tree, and select Default Setting(User Name / Secret). The Default
Setting(User Name/Secret) pane appears.
Figure 68 Default Setting(User Name/Secret) pane

Specify the following user information:
• User Name: Fiber Channel’s user name, up to 16 characters. You can use alphanumeric
characters in a user name. User names are case-sensitive.
can use alphanumeric characters.
5. Click OK.
Registering a Fibre Channel switch’s user information

3. In the Port tree, double-click the Fibre folder. Information about the Fibre Channel switch appears in
the FC Switch Information list.
4. Right-click any point in the FC Switch Information list, and select Specify User Information. The Specify
Authentication Information pane appears.

• User Name: Fibre Channel switch’s user name, up to 16 characters. You can use alphanumeric
characters in a user name.
can use alphanumeric characters.

5. Click OK.
Clearing a Fibre Channel switch’s user information

4. Right-click any point in the FC Switch Information list, and select Clear User information. The Clear
Authentication Information pane appears.
Figure 70 Clear Authentication Information pane

5. Click OK.
Specifying a Fibre Channel switch’s authentication mode

4. Right-click any point in the FC Switch Information list, and select Authentication
unidirectional->bi-directional.
To return the Fibre Channel setting, perform the same operation, except select Authentication
bi-directional->unidirectional in step 4.
Specifying whether a Fibre Channel switch can perform authentication

To enable Fibre Channel switches to authenticate hosts, you must enable the Fibre Channel switch’s user
authentication settings. By default, Fibre Channel switch authentication is disabled.
To enable a Fibre Channel switch to authenticate hosts:
4. Right-click any point in the FC Switch Information list, and select Authentication Disable->Enable.
To return the Fibre Channel switch setting so the switch cannot authenticate hosts, perform the same
operation, except select Authentication Enable->Disable in step 4.
Setting user authentication (iSCSI environments)

When configuring iSCSI environments, use the Authentication pane (Figure 30) to set user authentication
on iSCSI targets of the array. First, specify whether or not each iSCSI target performs authentication of
hosts, and then register the hosts’ user information on the iSCSI targets that perform authentication.
According to this setting, iSCSI targets can authenticate hosts that request a connection and restrict the
connections. In addition, to implement mutual authentication, specify the iSCSI targets’ user information
on each iSCSI target of the array.
This section describes the iSCSI target setting operations for user authentication.
For an overview of user authentication, see ”User authentication (iSCSI environments)” on page 48.
NOTE: The hosts to be connected must also be configured for authentication by iSCSI targets (and for
authentication of iSCSI targets by the host, if required). For more information about configuring the host
for CHAP authentication, see the documentation for the operating system and iSCSI driver in your
environment.
Enabling and disabling authentication of hosts on iSCSI targets

You can specify whether to perform authentication of hosts on each iSCSI target. Switch the user
authentication settings of iSCSI targets to enable or disable authentication of hosts. By default, user
authentication is disabled.
To enable authentication of hosts on an iSCSI target:
2. In the Port tree, double-click the Subsystem folder. If the array contains iSCSI channel adapters, the
iSCSI folder appears below the Subsystem folder.
3. Under the iSCSI folder, double-click the iSCSI folder or iSCSI port icon.
If you double-click the iSCSI folder, iSCSI ports in the array appear as icons.
If you double-click an iSCSI port, iSCSI target appears as an icon. The iSCSI name appears on the
right of each icon. When appears, the iSCSI target performs authentication of hosts. When
appears, the iSCSI target does not perform authentication of hosts. By default, appears for all
iSCSI targets.
4. Right-click an iSCSI target displayed with , and select Authentication Disable -> Enable. The iSCSI
target’s icon changes to , and the port name appears in blue.
To return the iSCSI target setting to , perform the same operation, except select Authentication Enable
-> Disable in step 4.
Registering a host’s user information on an iSCSI target

On an iSCSI target that performs authentication of hosts, register the user information for all hosts that you
allow to connect.

2. In the Port tree, select the port or iSCSI target on which you want to register a host’s user information.
The user information for hosts currently registered on the selected port or iSCSI target appears in the
Authentication information (Target) list.
You can register a host’s user information even if the port status is . In this case, however, the host’s
registered user information is ignored.
3. Right-click any point in the Authentication information (Host) list, and select Add New User Information
(Host). The Add New User Information (Host) pane appears.
Figure 71 Add New User Information (Host) pane
NOTE: You should register user information for all hosts to be connected to an iSCSI target that
performs authentication of hosts. To allow a specific host to connect to such an iSCSI target without
authentication, configure the iSCSI target and the host as follows:
• On the host:
It does not matter whether or not you configure the host for authentication by ports with CHAP.
However, if the host uses Microsoft iSCSI Initiator, do not configure the host for authentication
by ports with CHAP.
• Target Name: Host bus adapter’s iSCSI name. Select one from the list or enter the name directly. In
the list, all iSCSI names of host bus adapters connected to the selected port by the cable appear.
For more information about the characters and length you can specify as an iSCSI name, see
”iSCSI port and iSNS server settings” on page 42.
• User Name: Host’s user name of the host up to 128 characters.
You can use alphanumeric characters, spaces, and the following symbols in a user name:
. - + @ _ = : / [ ] , ~
User names are case-sensitive. For example, host1 and Host1 represent different users.
• Secret: Secret (that is, a password used in CHAP authentication) between 12 to 32 characters.
You can use the same characters and symbols as a user name in a secret.
• Re-enter Secret: Specify the secret again for confirmation.
• Protocol: Protocol used in user authentication. This protocol is fixed to CHAP.
4. Click OK. The host’s specified user information appears in blue in the Authentication Information
(Host) list.
Changing a host’s user information

You can change a host’s registered user name or secret and switch authentication settings between
Enable and Disable after registration.
NOTE: You cannot change iSCSI names when you change user information.
2. In the Port tree, double-click the iSCSI folder, and select the port or iSCSI target on which the user
information you want to change is registered. All user information for hosts registered on the selected
port appears in the Authentication information (Host) list.
3. In the Authentication information (Host) list, right-click the user information item you want to change,
and select Change User Information (Host). The Change User Information (Host) pane appears.
Figure 72 Change User Information (Host) pane

4. Change the host’s user information.
You can change the specifications of User Name and Secret. For more information about available
characters and length in the user name or secret, see ”Registering a host’s user information on an
iSCSI target” on page 112.
5. Click OK. The host’s user information appears in blue in the Authentication information (Host) list.
Deleting a host’s user information (iSCSI environments)

2. In the Port tree, double-click the iSCSI folder, and select the port or iSCSI target on which the user
information you want to delete is registered. The user information of hosts currently registered on the
selected port or iSCSI target appears in the Authentication information (Host) list.

3. In the Authentication information (Host) list, right-click the user information item you want to delete,
and select Delete User Information (Host). The Delete Authentication Information pane appears.
Figure 73 Delete Authentication Information pane

4. Click OK.
Specifying an iSCSI target’s user information (when performing mutual

authentication)
To perform mutual authentication, you must specify user information for iSCSI targets on the array’s ports.
Specify unique user information for each iSCSI target. You can change the specified user information for
iSCSI targets the same way you specified them initially.
2. In the Port tree, select the port or iSCSI target whose user information you want to specify. The
currently registered user information for the selected port or iSCSI target appears in the Authentication
information (Target) list.
3. Right-click any point in the Authentication information (Target) list, and select Specify Authentication
Information. The Specify Authentication Information pane appears.

Specify the following user information for the port or iSCSI target selected in the Port tree:
• Target Name: Selected port’s iSCSI name. You cannot change the iSCSI name.
• User Name: iSCSI target’s user name up to 128 characters. You can use alphanumeric characters,
spaces, and the following symbols in a user name:
. - + @ _ = : / [ ] , ~
User names are case-sensitive. For example, port1 and Port1 represent different user names.
can use the same characters and symbols as a user name.
• Re-enter Secret: Specify the secret again for confirmation.
4. Click OK. The specified user information for the port appears in blue in the Authentication information
(Target) list.
Clearing an iSCSI target’s user information (when performing mutual

authentication)
2. In the Port tree, expand the iSCSI folder, and select the port or iSCSI target whose user information you
want to clear. The currently registered user information for the port or iSCSI target appears in the
Authentication Information (Target) list on the right of the tree.
3. Right-click any point in the Authentication information (Target) list, and select Clear Authentication
Information. The Clear Authentication Information pane appears.
4. Click OK. The selected iSCSI target’s user information disappears from the Authentication information
(Target) list.
Settings and connection results in authentication of hosts (iSCSI environments)

following iSCSI target settings:
• iSCSI target’s setting in the Port tree: enable ( ) or disable ( )
• Whether or not the user information for the host that attempts to connect is registered on the iSCSI
target
Table 20 shows the relationship between combinations of iSCSI target settings and connection results in
authentication of hosts. Regardless of whether or not the host is configured for authentication by ports with
CHAP, the connection results are as follows, unless otherwise noted.
Table 20 Combinations of port settings and connection results (iSCSI environments)
Port settings Host settings Connection results

Authentication: at target Host user information
the host succeeded1

cannot be connected

cannot be connected
Disable —2 —2 Connected without authentication of

the host3
1. If a host is not configured for authentication by ports with CHAP, the host cannot connect to the array.
3. If a host uses Microsoft iSCSI Initiator and is configured for authentication by ports with CHAP, authentication of the host fails.
To allow such a host to connect to the port without authentication, do not configure it for authentication by ports with CHAP.

For more information about authentication of hosts, see ”User authentication (iSCSI environments)” on
page 48.
Operating NAS channel adapters

You can use LUN Manager to check the running status of OSs on NAS channel adapters. Also, when a
failure occurs on the OS, you can operate (restart, stop, or start) the OS using LUN Manager without
going to the array’s cabinet.
NOTE: You cannot perform operations related to NAS channel adapters and set Fibre Channel ports at
the same time. Therefore, if you change a Fibre Channel port setting first in the Port pane, you cannot
operate the NAS channel adapter. Click Apply once to apply the change to the array, and then operate
the NAS channel adapter’s OS.
Restarting a NAS channel adapter’s OS

2. In the Package tree, select the NAS folder or a NAS channel adapter.
• If you select the NAS folder, the CHN list displays the NAS channel adapters in the array.
• If you select a channel adapter, the CHN list displays information about that channel adapter.
3. In the CHN list, select the channel adapter whose OS Status column contains UP. The Reboot and Shut
Down buttons are activated.
4. Click Reboot. A confirmation message appears.
5. Click OK. The row selected in the CHN list appears in blue and the operation (Reboot) appears in the
Setting column. Also, the channel adapter name to be operated appears in blue in the Package tree.
7. Click OK. The selected NAS channel adapter’s OS restarts.
When the reboot starts, BUSY (Shutdown) appears in the OS Status column. If the OS restarted, UP
appears.
NOTE: You can stop the OS by right-clicking the channel adapter in the Package list and selecting
Reboot instead of using the Reboot button.
Stopping a NAS channel adapter’s OS

3. In the CHN list, select the channel adapter whose OS Status column contains UP. The Reboot and Shut
Down buttons are activated.
4. Click Shut Down. A confirmation message appears.
5. Click OK. The row selected in the CHN list appears in blue and the operation (Shut Down) appears in
the Setting column. Also, the channel adapter name to be stopped appears in blue in the Package
tree.
7. Click OK. The selected NAS channel adapter’s OS stops.
During stop processing, BUSY (Shutdown) appears in OS Status column. If the OS stops, DOWN
appears.
NOTE: You can stop the OS by right-clicking the channel adapter in the Package list and selecting Shut
Down instead of using the Shut Down button.
Starting a NAS channel adapter’s OS

3. In the CHN list, select the channel adapter whose OS Status column contains DOWN or DOWN
(Failure). The Boot button is activated.
4. Click Boot. A confirmation message appears.
5. Click OK. The row selected in the CHN list appears in blue and the operation (Boot) appears in the
Setting column. Also, the channel adapter name to be started appears in blue in the Package tree.
7. Click OK. The selected NAS channel adapter’s OS starts.
During start processing, BUSY (Boot) appears in the OS Status column. If the OS starts, UP appears.
NOTE: You can start the OS by right-clicking the channel adapter in the Package list and selecting Boot
instead of using the Boot button.

5 Troubleshooting LUN Manager
Troubleshooting
For troubleshooting information on the array, see the array’s documentation.
You are responsible for the operation and normal maintenance of the Command View XP computer or XP
Remote Web Console. The following are some guidelines for troubleshooting the Command View XP
computer or XP Remote Web Console:
• Check the cabling and LAN: Verify that both the computer and LAN cabling are firmly attached, and
the LAN is operating properly.
• Reboot the computer: Close any programs that are not responding. If necessary, reboot the computer
and restart the Command View XP Java applet program.
• Check for any general error conditions: Table 21 describes general error conditions and the
recommended resolution for each item. If you still cannot resolve an error condition, call you
HP account support representative for assistance (see ”Contacting you HP account support
representative” on page 120 for contact information).
• Check the status lamp on the Command View XP or XP Remote Web Console main pane: If the color of
the lamp is yellow ( ) or red ( ), confirm the severity level of the DKC and DKU on the Status pane
(see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks
XP Remote Web Console user guide for XP12000/XP10000/SVS200). If you cannot resolve an error
condition, contact you HP account support representative.
• Download the Command View XP or XP Remote Web Console trace files using the FD Dump Tool: If
you cannot resolve an error condition, copy the Command View XP or XP Remote Web Console
configuration information onto floppy disks using the FD Dump Tool (see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console
user guide for XP12000/XP10000/SVS200). Contact your HP account support representative (see
”Contacting you HP account support representative” on page 120), and give the information on the
floppy disks to the HP personnel.
Table 21 Troubleshooting LUN Manager
Error Condition Recommended Action

The program on the SVP is updated. Exit all Web browsers on the Command View XP
computer, and restart the browsers. If in doubt, exit and
restart the browsers.
The Command View XP computer experiences an error. Save the Java log file on the Command View XP
computer, and report to your HP account support
representative.
For Windows 2000, the Java log file is in the following
place:
c:\Documents and Settings\login
user ID\plugin131.trace
Restart the Command View XP computer.
A network error occurred. Restart the Command View XP computer.
Only the Exit and Refresh buttons are effective when The SVP might not be ready or might be performing
accessing the SVP from the Command View XP write processes from another system. Wait for a while,
computer. and click the Refresh button.
After dragging and dropping objects to another Close all panes, including the Storage Device List pane,
location or area, the scroll bar on that location is and log on to Command View XP or XP Remote Web
unusable. Console again.
A focus disappears from the edit box. Close all panes, including the Storage Device List pane,
and log on to Command View XP or XP Remote Web
Console again.
Table 21 Troubleshooting LUN Manager (continued)
Error Condition Recommended Action

A Command View XP or XP Remote Web Console pane Wait for an RMI time-out (default is 1 minute), and
is closed by one of the following: restart Command View XP or XP Remote Web Console.
• Clicking the button on the pane.
• Using commands such as File and Exit on the Web
browser.
• Pressing the Alt and F4 keys.
An internal error occurred, or a Web browser ended Close all panes, including the Storage Device List pane,
abnormally (forcibly). and log on to Command View XP or XP Remote Web
Console again. If the same error occurs, restart the
Command View XP computer.
If you cannot resolve an error condition. Copy the Command View XP or XP Remote Web
Console configuration information onto floppy disks
using the FD Dump Tool (see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the
HP StorageWorks XP Remote Web Console user guide
for XP12000/XP10000/SVS200), and contact your
HP account support representative.
Contacting you HP account support representative

If you need to contact your HP account support representative, be sure to provide as much information
about the problem as possible, including the circumstances surrounding the error or failure, exact content
of messages displayed on the Command View XP computer, and severity levels and reference codes of
the R-SIMs on the R-SIM pane.
120 Troubleshooting LUN Manager

6 Finding an open-system host’s World Wide Name
(WWN)
If you are configuring a Fibre Channel environment, you must verify that the fibre adapters and Fibre
Channel device drivers are installed on the open-system hosts. Next, you must find the World Wide Name
(WWN) of the host bus adapter used in each open-system host. The WWN is a unique identifier for a host
bus adapter in a open-system host, consisting of 16 hexadecimal digits.
This appendix describes how to find a host’s WWN. HP recommends that you make a record of WWNs
of the hosts in your system, because you will need to enter WWNs in LUN Manager panes to specify the
hosts used in your system.
Finding WWNs in Windows NT or Windows 2000 environments

HP currently supports the Emulex Fibre Channel adapter in Windows NT or Windows 2000 environments,
and will support other adapters in the future. For more information about Fibre Channel adapter support,
or if you are using a Fibre Channel adapter other than Emulex, contact you HP account support
representative for instructions on finding the WWN.
NOTE: Although these instructions are written for a Windows NT environment, similar instructions apply
in a Windows 2000 environment.
1. Verify that the fibre adapters and the Fibre Channel device drivers are installed.
2. Log in to the Windows NT or Windows 2000 host with administrator access.
3. Go to the LightPulse™ Utility to open the LightPulse Utility/NT pane.
Figure 75 LightPulse Utility/NT pane

If you do not have a shortcut to the Utility, do the following:
a. Go to the Start menu, select Find, and choose Files and Folders. The Find pane opens.
b. In the Named field, enter lputilnt.exe.
In the Look in box, choose the hard drive containing the Emulex mini-port driver.
c. Click Find Now to search for the LightPulse Utility.
NOTE: If you cannot find the LightPulse Utility, contact Emulex technical support.
d. In the Find: Files named list box, select lputilnt.exe, and press Enter. The LightPulse Utility/NT pane
appears.
4. In the list on the left of the pane, verify that the installed adapters appear.
5. In the Category list, select Configuration Data. In the Region list, select 16 World-Wide Name. The
selected adapter’s WWN appears in the list on the right of the pane.
Finding WWNs in Sun Solaris environments

HP currently supports the JNI Fibre Channel adapter in Sun Solaris environments. This information will be
updated as needed to cover future adapter-specific information as those adapters are supported. For
more information about Fibre Channel adapter support, or if you are using a Fibre Channel adapter other
than JNI, contact you HP account support representative for instructions for finding the WWN.
1. Verify that the fibre adapters and Fibre Channel device drivers are installed.
2. Login to the Sun Solaris host with root access.
3. Enter dmesg |grep Fibre. A list of installed Fibre Channel devices and their WWNs appears.
# dmesg |grep Fibre ← Enter the dmesg command.

:
fcaw1: JNI Fibre Channel Adapter model FCW
fcaw1: Fibre Channel WWN: 200000e0694011a4 ← Record the WWN.
fcaw2: JNI Fibre Channel Adapter model FCW
fcaw2: Fibre Channel WWN: 200000e06940121e ← Record the WWN.
Figure 76 Sun Solaris World Wide Name

4. Verify that the listed Fibre Channel adapters are correct, and record the listed WWNs.
Finding WWNs in AIX, SGI Irix, or Sequent environments

To find WWNs in AIX, SGI Irix, or Sequent environments, use the fibre switch connected to the host. The
method for finding the WWN of the connected server on each port using the fibre switch depends on the
type of switch. For instructions on finding the WWN, see the fibre switch’s documentation.
Finding WWNs in HP-UX environments

1. Verify that the fibre adapters and Fibre Channel device drivers are installed.
2. Log in to the HP-UX host with root access.
3. At the command line prompt, enter:
/usr/sbin/ioscan -fnC lan
122 Finding an open-system host’s World Wide Name (WWN)

4. A list of attached Fibre Channel devices and their device file names appears.
# /usr/sbin/ioscan -fnC lan ← Enter the ioscan command.

Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 0 8/0.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl
/dev/fcms0 ←Device file name.
/dev/fcms4 ← Device file name.
lan 1 10/8/1/0 btlan4 CLAIMED INTERFACE PCI(10110009) -- Built-in #1
lan 2 10/8/2/0 btlan4 CLAIMED INTERFACE PCI(10110009) -- Built-in #2
lan 3 10/12/6 lan2 CLAIMED INTERFACE Built-in LAN
/dev/diag/lan3 /dev/ether3 /dev/lan3
# # fcmsutil /dev/fcms0 ← Enter the fcmsutil command.
Local N_Port_ID is = 0x000001
N_Port Node World Wide Name = 0x10000060B0C08294
N_Port Port World Wide Name = 0x10000060B0C08294 ← Record the WWN.
Topology = IN_LOOP
Speed = 1062500000 (bps)
HPA of card = 0xFFB40000
EIM of card = 0xFFFA000D
Driver state = READY
Number of EDB's in use = 0
Number of OIB's in use = 0
Number of Active Outbound Exchanges = 1
Number of Active Login Sessions = 2
#
Figure 77 HP-UX World Wide Name

Record the Fibre Channel device file name (for example, /dev/fcms0).
5. Use the fcmsutil command with the Fibre Channel device name to list the WWN for that Fibre
Channel device. For example, to list the WWN for the device with the device file name /dev/fcms0,
enter:
/opt/fcms/bin/fcmsutil /dev/fcms0
NOTE: When an A5158 Fibre Channel adapter is used, enter the following for the device name
at the command line prompt:
/usr/sbin/ioscan -fnC fc
6. Record the Fibre Channel device file name (for example, /dev/td0).
NOTE: When the A5158 Fibre Channel adapter is used, enter the following to list the WWN for
the device with the device file name:
/opt/fcms/bin/fcmsutil <device file name>
7. Record the WWN and repeat the above steps for each Fibre Channel device you want to use.
124 Finding an open-system host’s World Wide Name (WWN)
Part 2: LUN Configuration and Security Manager XP –
Volume Manager
126
7 Overview of Volume Manager and Custom Volume
Size
Volume Manager and Custom Volume Size (CVS) are functions for open systems and mainframe systems.
To use these functions, you need the software called HP StorageWorks LUN Configuration and Security
Manager XP.
This chapter describes Volume Manager and CVS.
Overview of Volume Manager

This section describes the Volume Manager function and configuration of LUSE volumes (expanded LUs).
Volume Manager operations include the following:
• ”Viewing concatenated parity groups” on page 151
• ”Creating LUSE volumes” on page 151
• ”Releasing LUSE volumes” on page 153
• ”Changing LUSE capacities” on page 153
Volume Manager function

The Volume Manager function is applied to open-system logical volumes and enables you to configure
one large logical volume by combining several small LDEVs. The Volume Manager function allows hosts
that can only use a limited number of logical units (LUs) per fibre interface to access larger amounts of
data using expanded LUs.
Figure 78 shows the LUSE configuration. By using the Volume Manager function, you can combine
several logical devices (LDEVs) or volumes into one large logical volume. The configured LDEV’s size can
be expanded up to 36 times the size of the original LDEV. The ID of the logical volume defined as the
large logical volume is represented by the smallest LDEV ID (assigned to the top LDEV). The host
recognizes the expanded logical volume as one representative LDEV. As long as the number of LDEVs
combined into one large logical volume does not exceed the specified limit (see ”Volume Manager
guidelines” on page 128), you can arbitrarily select any LDEVs as the volumes to combine, regardless of
their size (or capacity) or whether or not they are on the same Control Unit (CU). The Volume Manager
function also allows you to combine several LDEVs and a LUSE volume (combined LDEVs) into one LUSE
volume, or combine LUSE volumes together into one LUSE volume.
Before the host can access each LDEV composing an expanded LU (LUSE volume), you must release the
expanded LU.
Figure 78 LUSE configuration
Volume Manager guidelines

The following are the specifications and restrictions on LDEVs used to configure a LUSE volume:
• Open volumes (OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, and OPEN-V) are supported.
• The number of LDEVs combined into a LUSE volume must be within the range of 2 to 36.
NOTE: The number of expanded LUs (LDEVs) should not exceed 36, even if the LUSE volume
contains another LUSE volume.
• The emulation type of LDEVs combined into a LUSE volume must be the same.
• The RAID level of LDEVs that are to be combined into LUSE volumes should be the same.
(Recommended).
NOTE: Combining RAID-1 and RAID-5 volumes into the same LUSE volume is supported, but not
recommended.
• LDEVs or LUSE volumes to be combined must not have assigned path definitions. For this reason,
TrueCopy for z/OS®, Continuous Access XP, ShadowImage for z/OS, Business Copy XP, and
Continuous Access XP Journal pair volumes cannot be targets of Volume Manager operations (see
”Volume Manager operations using a path-defined LDEV” on page 129).
• LDEVs to be combined into LUSE volumes must not be reserved for Auto LUN XP.
• When combining a LUSE volume with another LUSE volume, the range of LDEVs should not overlap.
NOTE: If you combine LDEV00, LDEV03, and LDEV05 into LUSE 1, combine LDEV02 and
LDEV04 into LUSE 2,and combine LDEV06 and LDEV07 into LUSE 3, you can also combine
LUSE 1 and LUSE 3. However, you cannot combine LUSE 1 and LUSE 2, because the LDEV range
in LUSE 1 and LUSE 2 overlap.
• The maximum capacity of a LUSE volume is 60 TB.
128 Overview of Volume Manager and Custom Volume Size

NOTE: When a host accesses a LUSE volume, the host can only access less than 2 TB of the LUSE
volume’s address area.
• Combining command devices and Just In Time volumes into a LUSE volume is not supported.
• The access attribute must be set to Read/Write.
• Combining internal LUs, external LUs, and virtual volumes (V-VOLs) is not supported.
• During online, the host mode must not be 0x0C [Windows].
• The I/O suppression mode and cache mode settings of LDEVs combined into a LUSE volume must be
the same.
• All LDEVs combined into a LUSE volume must be of the same drive type (either SATA drive or
non-SATA drive).
• VMAs are not set to LDEVs.
NOTE: For more information about volume management areas (VMAs), see the HP StorageWorks
LUN Security XP Extension user guide.
• LDEVs are not pool volumes (pool-VOLs).

• LDEVs are not journal volumes.
The following are the specifications and restrictions on LDEVs released from a LUSE volume:
• The LUSE volume must not have a defined path.
• The access attribute must be set to Read/Write.
Volume Manager operations using a path-defined LDEV
When you create a LUSE volume, the top LUSE volume can be either an LDEV or LUSE volume that has
one or more paths defined to it. Only the top volume in the LUSE volume to be created can have any
paths. Other volumes in the LUSE volume to be created must not have any paths.
NOTE: You can perform a Volume Manager operation using a path-defined LDEV regardless of how
many paths are defined to the LDEV.
NOTE: You cannot combine a path-defined LDEV or LUSE volume with another path-defined LDEV or
LUSE volume.
NOTE: When you start the Volume Manager operation to combine a path-defined LDEV or LUSE volume
with another path-defined LDEV or LUSE volume, a confirmation pane appears. Click OK if you want to
continue or Cancel if you do not.
CAUTION: Note the following points when you perform a Volume Manager operation using a
path-defined LDEV:
• If a path is defined from a Windows 2000, Windows Server 2003, or AIX 5.2 host to an LDEV, you
can use the LDEV for Volume Manager operations using a path-defined LDEV. However, if a path is
defined from a host running another operating system to an LDEV, you cannot use the LDEV for Volume
Manager operations using a path-defined LDEV.
• If a path is defined from a Windows 2000 or Windows Server 2003 host to an LDEV and you want to
perform a Volume Manager operation that handles this path-defined LDEV, ensure that the Windows
host’s host mode is 2C (Windows Extension). If the host mode is not 2C, change the host mode to 2C
before performing the Volume Manager operation.
Overview of Custom Volume Size

This section describes the Custom Volume Size (CVS) function, configuring CVS, and requirements of the
storage subsystem ID (SSID). CVS operations include:
• ”Viewing concatenated parity groups” on page 180
• ”Converting logical volumes to space” on page 180
• ”Creating CVS volumes (Install CV operation)” on page 181
• ”Deleting CVS volumes” on page 183
• ”Converting CVs back to FVs (Volume Initialize operation)” on page 183
• ”Re-creating CVs after initializing the VDEV (Make Volume operation)” on page 185
CVS function
CVS works on each VDEV that consists of a group of logical volumes (LDEVs or LUs) in a parity group.
Usually, one VDEV consists of some fixed volumes (FV) and some free space. The emulation type
determines the number of fixed volumes. A CVS volume usually consists of at least one fixed volume (FV),
one or more customized volumes (CVs), and some free space. CVS allows you to configure variable-size
volumes, which are usually smaller than normal (fixed-size) volumes. Therefore, if several frequently
accessed files are located in the same logical volume, use CVS to reduce conflicts by splitting the logical
volumes and scattering the files, although there are some instances where access is delayed while a file is
being accessed. This can improve data accessing performance. CVS can also divide a logical volume
into smaller ones for a command device, which efficiently exploits the disk’s capacity.
CVS operations include: Volume to Space, Install CV, Volume Initialize, and Make Volume. The Volume to
Space function formats one or more LDEVs on a selected Virtual Device (VDEV) into free space. That free
space can either be used to install one or more variable-sized volumes (CVs) using the Install CV function,
or left as free space for future use. The Volume Initialize function de-installs all variable sized volumes
(CVs) under a CVS volume, and reformats the CVS volume as a normal volume (VDEV). The Make Volume
function clears all variable-sized volumes (CVs) under a CVS volume and creates an initial volume (VDEV)
consisting of the new user-defined CVs.
For an overview of how the Volume Initialize function works, see Figure 79. For an overview of how the
Make Volume function works, see Figure 80.
Figure 79 Overview of Volume Initialize function

Figure 80 Overview of Make Volume function
Parity group configuration

One parity group consists of a maximum of 16 VDEVs. For RAID-5 (7D + 1P) or RAID-6 (6D + 2P) levels,
a maximum of 512 fixed-size volumes (FVs) and a certain amount of free space are available in one
VDEV. For other RAID levels, a maximum of 256 FVs and a certain amount of space are available in one
VDEV. Each VDEV in a parity group has the same configuration, and is assigned the same FVs of the
same size and RAID level.
CVS functions (Volume to Space, Install CV, Volume Initialize, and Make Volume) are performed on each
VDEV. VDEVs are also separated from each other by the boundary limitation. Therefore, you cannot
define a volume across two or more VDEVs beyond the boundaries.
Figure 81 Parity group configuration
As the result of CVS operations, a VDEV contains FVs, CVs, and free spaces that are delimited in logical
cylinders. Sequential free spaces are combined into a single free space (see Figure 82).
Figure 82 Virtual CVS volume configuration
Volume to Space function

This function converts one or more LDEVs (FVs or CVs) into free space, which deletes the selected LDEVs
from that VDEV.
The following are the restrictions on LDEVs and LUSE volumes for the Volume to Space operation:
• The LDEV must not be path-defined (including TrueCopy for z/OS, Continuous Access XP,
ShadowImage for z/OS, Business Copy XP, and Continuous Access XP Journal pair volumes).
• The LDEV must not be a component of a LUSE volume.
• The LDEV must not be reserved for Auto LUN XP.
• The LDEV must be read/write-enabled.
• The LDEV or LUSE volume must not be a pool volume (pool-VOL).
• The LDEV must not be a journal volume.
• The LDEV must not be a remote command device.
• The LDEV must not contain extents.
Install CV function
This function defines and installs one or more CVS volumes under an existing volume (free space in a
VDEV). You can assign a specific number of physical cylinders (for mainframe systems) or MBs (for open
systems) to each CVS volume for maximum control over the volume size. When you specify the capacity
and an emulation type other than OPEN-V for a CVS volume to be created, the Install CV function
automatically creates and formats the CVS volume in sufficient free space. You must specify new CU and
LDEV numbers for the created CVS volume. The created CVS volume contains the user-specified number of
user cylinders and a predetermined number of control cylinders according to the emulation type.
NOTE: If you select free space and perform an Install CV operation, CVS volumes are created only in the
selected free space.

For OPEN-V volumes, there are four ways to create CVS volumes (Table 22). You can specify from 46 MB
(50 cylinders) up to the VDEV’s maximum capacity for a CVS volume’s capacity.
Table 22 Creating CVS volumes using Install CV (for OPEN-V)
Install CV method Description

Specify size and number Used to specify the capacity and number of CVs in the CVS volume you want
to create.
Divide free space by number Used to create CVS volumes by specifying the number of CVs in the CVS
volume to be created.
Divide free space by size Used to create CVS volumes by specifying the capacity of CVs in the CVS
Set remaining space as volume Used to create a CVS volume using the remaining space on the VDEV.
NOTE: CVS functions are not available for OPEN-L and OPEN-M volumes.
NOTE: The install CV function allocates CVS volumes in the order in which the function finds sufficient
free space for the CVS volumes. For optimum space allocation, allocate CVS volumes in descending order
of capacity.
Table 23 lists the CVS specifications and the minimum and maximum CVS volume capacities for
mainframe and open systems.
Table 23 CVS specifications
Parameter Mainframe systems Open systems

Track format 3380, 3390 OPEN-3, OPEN-8, OPEN-V
OPEN-9, OPEN-E
Emulation type 3380-3, 3380-3A, OPEN-3, OPEN-8, OPEN-V

3380-3B, 3380-3C, OPEN-9, OPEN-E
3380-F*, 3380-K*,
NOTE: Emulation types 3380-KA*, 3380-KB*,
followed by an asterisk 3380-KC*
(*) can be used only with
Fujitsu mainframe 3390-3, 3390-3A,
systems. Do not use these 3390-3B, 3390-3C,
emulation types if you are 3390-3R, 3390-9,
not using Fujitsu 3390-9A, 3390-9B,
mainframe systems. 3390-9C, 3390-L,
3390-LA, 3390-LB,
3390-LC, 3390-M,
3390-MA, 3390-MB,
3390-MC
NF80-F*, NF80-K*,
NF80-KA*, NF80-KB*,
NF80-KC*
Ability to intermix Depends on the track Depends on the track Depends on the track
emulation types geometry geometry geometry
Maximum number of 512 for RAID5 (7D+1P) or 512 for RAID5 (7D+1P) or 512 for RAID5 (7D+1P) or
volumes (normal and RAID6 (6D + 2P) RAID6 (6D + 2P) RAID6 (6D + 2P)
CVS) per VDEV
256 for other RAID levels 256 for other RAID levels 256 for other RAID levels
Table 23 CVS specifications (continued)
Parameter Mainframe systems Open systems

Maximum number of 16,384 16,384 16,384
volumes (normal and
CVS) per array
Minimum size for one 1 user cylinder (+ control 36,000 KB (+ control 48,000 KB (50 cylinders)
CVS volume cylinders) cylinders)
Maximum size for one See Table 24 See Table 25 See Table 25
CVS volume
Size increment 1 user cylinder 1 MB 1 MB (1 user cylinder)
Disk location for CVS Anywhere Anywhere Anywhere

volumes
Table 24 CV capacity by emulation type (mainframe systems)
Emulation type Minimum CV capacity Maximum CV capacity Number of control

(Cyl) (Cyl) cylinders (Cyl)
3380-3 1 3,339 7
3380-3A 1 3,339 7
3380-3B 1 3,339 7
3380-3C 1 3,339 7
3380-F 1 3,983 22
3380-K 1 2,655 7
3380-KA 1 2,655 7
3380-KB 1 2,655 7
3380-KC 1 2,655 7
3390-3 1 3,339 6
3390-3A 1 3,339 6
3390-3B 1 3,339 6
3390-3C 1 3,339 6
3390-3R 1 3,339 6
3390-9 1 10,017 25
3390-9A 1 10,017 25
3390-9B 1 10,017 25
3390-9C 1 10,017 25
3390-L 1 32,760 23
3390-LA 1 32,760 23
3390-LB 1 32,760 23
3390-LC 1 32,760 23
3390-M 1 65,520 53
3390-MA 1 65,520 53
3390-MB 1 65,520 53
3390-MC 1 65,520 53

Table 24 CV capacity by emulation type (mainframe systems) (continued)
Emulation type Minimum CV capacity Maximum CV capacity Number of control

(Cyl) (Cyl) cylinders (Cyl)
NF80-F 1 3,983 22
NF80-K 1 2,655 7
NF80-KA 1 2,655 7
NF80-KB 1 2,655 7
NF80-KC 1 2,655 7
Table 25 CV capacity by emulation type (open systems)
Emulation type Minimum CV capacity Maximum CV capacity (CYL) Number of control

(CYL) cylinders (Cyl)
OPEN-V 48,000 KB 3,019,898,880 KB (2.8125 TB) 0 KB (0 Cyl)
OPEN-3 36,000 KB (50 Cyl) 2,403,360 KB 5,760 KB (8 Cyl)
OPEN-E 36,000 KB (50 Cyl) 14,226,480 KB 13,680 KB (19 Cyl)
NOTE: CVS functions are not applicable to OPEN-L and OPEN-M volumes.
Calculating CV capacity for mainframe systems

When creating a CV, you can specify the CV’s capacity. However, there is a margin of error between the
user-specified CV capacity and the actual CV capacity. To estimate the actual CV capacity, use the
following formula. The resulting CV capacity is expressed in megabytes.
↑ (user-specified-CV-capacity + management-area-capacity) × 15 × capacity-of-a-slot ÷
boundary-value ↑ × boundary-value ÷ 1024
NOTE:
• Round up the value enclosed by two up arrows (↑ ) to the nearest whole number.
• The user-specified CV capacity is expressed in cylinders.
• The management area capacity is expressed in cylinders (see Table 26 on page 138).
• The boundary value is expressed in kilobytes. The boundary value depends on volume emulation types
and RAID levels (see Table 28 on page 138).
• The slot capacity is expressed in kilobytes. The slot capacity depends on the volume emulation types
(see Table 29 on page 139).
Calculating CV capacity for open systems

When creating a CV, you can specify the CV’s capacity. However, there is a margin of error between the
user-specified CV capacity and the actual CV capacity.
This section explains how to calculate the user area capacity and the entire capacity. The term “user area
capacity” refers to the capacity of areas in a CV that can contain user data.
If the emulation type is OPEN-V
The methods for calculating the CV’s user area capacity and the entire capacity vary depending on the
CV capacity unit specified when creating the CV.
• If the CV capacity unit is megabytes (MB):
To calculate the CV’s user area capacity, use the following formula. The resulting user area capacity is
expressed in kilobytes.
↑ ↑ user-specified-CV-capacity × 1024 ÷ 64 ↑ ÷ 15 ↑ × 64 × 15
NOTE:
• The user-specified CV capacity is expressed in megabytes.
To calculate the CV’s entire capacity, use the following formula. The resulting entire capacity is
expressed in megabytes:
↑ user-area-capacity ÷ boundary-value ↑ × boundary-value ÷ 1024
NOTE:
• The user area capacity is expressed in kilobytes.
• The boundary value is expressed in kilobytes. The boundary value depends on volume
emulation types and RAID levels (see Table 28 on page 138).
• If the CV capacity unit is cylinders (Cyl):

user-specified-CV-capacity × 64 × 15
NOTE: The user-specified CV capacity is expressed in cylinders.
expressed in megabytes.
↑ user-area-capacity ÷ boundary-value ↑ × boundary-value ÷ 1024
NOTE:
• If the CV capacity unit is blocks:

user-specified-CV-capacity ÷ 2
NOTE: The user-specified CV capacity is expressed in blocks.
expressed in blocks. To convert the resulting entire capacity into megabytes, divide this capacity by
2,048.
↑ user-specified-CV-capacity ÷ (boundary-value × 2) ↑ × (boundary-value × 2)

NOTE:
• The user-specified CV capacity is expressed in blocks.
If the emulation type is other than OPEN-V

• If the CV capacity unit is MB (megabytes):
↑ ↑ user-specified-CV-capacity × 1024 ÷ capacity-of-a-slot ↑ ÷ 15 ↑ × capacity-of-a-slot × 15
NOTE:
• The user-specified CV capacity is expressed in megabytes.
• The slot capacity is expressed in kilobytes. The slot capacity depends on volume emulation
types (see Table 29 on page 139).
expressed in megabytes.
↑ (user-area-capacity + management-area-capacity) ÷ boundary-value ↑ × boundary-value ÷ 1024
NOTE:
• The management area capacity is expressed in kilobytes. The management area capacity
depends on volume emulation types (see Table 27 on page 138).
• If the CV capacity unit is blocks:

user-specified-CV-capacity ÷ 2
NOTE: The user-specified CV capacity is expressed in blocks.
expressed in blocks. To convert the resulting entire capacity into megabytes, divide this capacity by
2,048.
↑ (user-specified-CV-capacity + management-area-capacity × 2) ÷ (boundary-value × 2) ↑ ×
(boundary-value × 2)
NOTE:
• The user-specified CV capacity is expressed in blocks.
• The management area capacity is expressed in kilobytes. The management area capacity
depends on volume emulation types (see Table 27 on page 138).
Table 26 Management area capacity of mainframe volumes
Emulation type Management area capacity

3380-3, 3380-3A, 3380-3B, 3380-3C, 7
3380-K, 3380-KA, 3380-KB, 3380-KC,
NF80-K, NF80-KA, NF80-KB, NF80-KC
3390-3, 3390-3R, 3390-3A, 3390-3B, 3390-3C 6
3390-9, 3390-9A, 3390-9B, 3390-9C 25
3390-L, 3390-LA, 3390-LB, 3390-LC 23
3390-M, 3390-MA, 3390-MB, 3390-MC 53
3380-F, NF80-F 22
NOTE: A mainframe volume’s management area capacity is expressed in cylinders.
Table 27 Management area capacity of open-system volumes
Emulation type Management area capacity

OPEN-V 0
OPEN-3 5,760
OPEN-8 19,440
OPEN-9 19,440
OPEN-E 13,680
NOTE: An open-system volume’s management area capacity is expressed in kilobytes.
Table 28 Boundary value for RAID levels
Emulation type Boundary value Boundary value Boundary value Boundary value
for RAID1 (2D+2D) for RAID5 (3D+1P) for RAID5 (7D+1P) for RAID6 (6D+2P)
3380-xx 768 1,152 2,688 2,304
3390-xx 928 1,392 3,248 2,784
OPEN-xx (except for 768 1,152 2,688 2,304

OPEN-V)
OPEN-V 1,024 1,536 3,584 3,072
NOTE:
• The xx is a variable indicating one or more numbers or letters.
• Boundary values are expressed in kilobytes.

• Boundary values of external LUs are always one kilobyte, regardless of RAID levels.
Table 29 Slot capacities
Emulation type Slot capacity

3380-xx, NF80-xx 48
3390-xx 58
OPEN-xx (except for OPEN-V) 48
OPEN-V 256
NOTE:
• The xx is a variable indicating one or more numbers or letters.
• Slot capacity is expressed in kilobytes.
Volume Initialize and Make Volume functions

You can initialize a CVS volume using one of the following functions: Volume Initialize or Make Volume.
The Volume Initialize operation de-installs all variable-sized volumes under a CVS volume, and reformats
the CVS volume as a normal volume (FV). You must assign CU and LDEV numbers to the new formatted
FV. Any existing FVs on the original VDEV are not reformatted.
The Make Volume operation deletes all volumes in a VDEV, and creates new variable-sized volumes (CVs)
according to the specified settings. You can specify the following settings (see Table 30).
Table 30 Settings for the Make Volume operation (OPEN-V only)
No. Setting CVS volumes to be created

1 Specify the capacity and number of A CVS volume that has the specified number of CVs of the specified
variable-sized volumes (CVs) under a capacity is created. This is the same as the Install CV operation.
CVS volume.
2 Specify the number of variable-sized A CVS volume that has the specified number of CVs is created (the
volumes (CVs). VDEV is divided by the specified number).
3 Specify the capacity of a A CVS volume that has CVs of the specified capacity is created (the
variable-sized volume (CV). VDEV is divided by the specified capacity).
4 Specify the remaining capacity for a If some space remains in the VDEV after CVS volumes are created
CVS volume. by settings 1through 3, that remaining space can also be converted
into a CVS volume.
The following are the restrictions on CVs for the Volume Initialize function (other than OPEN-V):
• The CV must not be path-defined (including TrueCopy for z/OS, Continuous Access XP, ShadowImage
for z/OS, Business Copy XP, and Continuous Access XP Journal pair volumes).
• The CV must not be a component of a LUSE volume.
• The CV must not be reserved for Auto LUN XP.
• The CV must be read/write-enabled.
• The CV must not be a pool volume (pool-VOL)
• The CV must not be a journal volume.
• The CV must not be remote command device.
• The CV must not contain extents.
The following are the restrictions on CVs for the Make Volume function:
• The CV must not be path-defined (including TrueCopy for z/OS, Continuous Access XP, ShadowImage
for z/OS, Business Copy XP, and Continuous Access XP Journal pair volumes).
• The CV must not be reserved for Auto LUN XP.
• LUSE volumes concatenated with one or more LDEVs belonging to a different VDEV must not exist.
• The CV must be read/write-enabled.
• The CV must not be a pool volume (pool-VOL)
• The CV must not be a journal volume.
• The CV must not be a remote command device.
• The CV must not contain extents.
If the VDEV contains a CV that violates any of the restrictions, the Volume Initialize and Make Volume
functions are disabled. You must eliminate invalid CVs before performing the Volume Initialize and Make
Volume functions.
SSID requirements
The array is configured with one SSID for each of 256 devices and up to four SSIDs per CU image. Each
SSID must be unique within each host system. Table 31 shows the relationship between emulation types of
controllers and SSIDs.
Table 31 SSID requirements
Controller emulation type SSID requirement CVS support

3990-6, 3990-6E (0104)x - (FFFD)x 3390-3, 3390-3A, 3390-3B, 3390-3C,
3390-9, 3390-9A, 3390-9B, 3390-9C,
OPEN-3, OPEN-8, OPEN-9, OPEN-E, and OPEN-V volumes
2105-F20 (0104)x - (FFFD)x 3380-3, 3380-3A, 3380-3B, 3380-3C,

3390-3, 3390-3A, 3390-3B, 3390-3C, 3390-3R,
3390-9, 3390-9A, 3390-9B, 3390-9C,
3390-L, 3390-LA, 3390-LB, 3390-LC,
3390-M, 3390-MA, 3390-MB, 3390-MC,
OPEN-3, OPEN-8, OPEN-9, OPEN-E, and OPEN-V volumes
Requirements for CU groups

If you are using HP StorageWorks LUN Configuration and Security Manager XP, you can apply Volume
Manager functions to open-systems volumes belonging to CU group 0 (zero), but not to volumes in other
CU groups. If you are using Custom Volume Size (CVS), you can apply Volume Manager functions to
mainframe volumes, regardless of which CU group the volumes belong to. For more information about CU
groups, see the HP StorageWorks XP Remote Web Console user guide for Xp12000/XP10000/SVS200.

8 Preparing to use Volume Manager or Custom Volume
Size
This chapter describes the environment you must prepare to operate Volume Manager or Custom Volume
Size (CVS).
System requirements
To operate Volume Manager or CVS, you need the following:
• XP12000/XP10000/SVS200 array
• Command View XP computer or XP Remote Web Console
• Licensed Volume Manager and/or CVS software
NOTE: To use the Volume Manager or CVS function, you need the software called HP StorageWorks
LUN Configuration and Security Manager XP.
Command View XP or XP Remote Web Console requirements

For more information about the environment necessary for the Command View XP PC, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays. You must use a Command View XP
PC adapted to the PC environment. Connect the Command View XP PC to be used for arrays via a TCP/IP
network.
Installing Volume Manager and CVS

Install the software necessary to operate Volume Manager and CVS. For instructions, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote
Web Console user guide for XP12000/XP10000/SVS200.
Connecting to the array

To connect the Command View XP PC to the array, take the following steps:
1. Enter the URL of the primary SVP in the Web browser to access the primary SVP. The Storage Device
List pane appears.
2. Select the desired array.
3. Enter the user ID and password, and click OK. The Command View XP PC is connected to the array,
and the Command View XP main pane appears.
For more information about using the Command View XP PC, see the HP StorageWorks Command View
XP user guide for XP Disk Arrays.
Starting Volume Manager and CVS

1. Connect the Command View XP PC to the array, and open the Command View XP or XP Remote Web
Console main pane. For instructions, see the HP StorageWorks Command View XP user guide for XP
Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for
XP12000/XP10000/SVS200.
2. From the option buttons on the left of the Command View XP or XP Remote Web Console main pane
for activating the array’s features, click the Volume Manager button ( ). The Volume
Manager main pane appears and enables you to operate Volume Manager or CVS.
3. The Volume Manager pane is the initial pane that appears. To operate CVS, click the Customized
Volume tab.
NOTE:
• To exit Volume Manager, click the button (Exit) on the upper right of the Command View XP or XP
Remote Web Console main pane or end the Web browser.
• The initial Command View XP or XP Remote Web Console main pane appears in View mode. To
implement any changes for Volume Manager or CVS, you must change the operation mode to Modify
mode. For more information, see ”Changing to Modify mode” on page 142.
Changing to Modify mode

To implement any changes for Volume Manager or CVS, you must be in Modify mode. The array
information icons (Figure 83 and Figure 85) are on the upper right of the pane. These icons are described
in detail in the HP StorageWorks Command View XP user guide for XP Disk Arrays or the
HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200. To change
from View mode to Modify mode and back, two icons are important.
• Exclusive lock icons indicate the operation mode of all currently logged-in users. If all users are
operating in View mode, the Unlocked icon ( ) appears. If a user is operating in Modify mode, or if
array maintenance or SNMP operations are being performed, the Locked icon ( ) appears.
• Mode Changing icons allow users to change the operation mode between View mode ( ) and
Modify mode ( ).
NOTE: Only one user at a time can be in Modify mode.
1. You must have write permission for Volume Manager. For more information about assigning write
permission to a user ID, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or
the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
2. Verify that the array is unlocked. If all users are operating in View mode, the Unlocked ( ) and View
Mode ( ) icons appear (Figure 83). If a user is operating in Modify mode or if array maintenance is
being performed, the Locked icon ( ) appears and you cannot change to Modify mode.
3. Select the Mode Changing icon ( ), which should be in View mode. A confirmation message
appears (Figure 84). Click OK.
The Mode Changing icon changes from View mode to Modify mode ( ), and the Unlocked icon ( )
changes to the Locked icon ( ) (Figure 85).
Change back to View mode once you have applied the necessary changes. To go back to the View
mode, select the Mode Changing icon ( ). If a confirmation message appears (Figure 84), click OK. You
are back to View mode.
Figure 83 Icons showing Unlocked status and View mode
Figure 84 Mode changing confirmation message
Figure 85 Icons showing Locked status and Modify mode
142 Preparing to use Volume Manager or Custom Volume Size

9 Volume Manager operations
This chapter describes Volume Manager operations.
Volume Manager panes

This section describes components of the Volume Manager panes.
Volume Manager main pane

To open the Volume Manager pane, click the Volume Manager button ( ).
Figure 86 Volume Manager pane

The Volume Manager pane has the following features.
LDEV Information tree
This tree is on the upper-left of the Volume Manager pane. The LDEV Information tree displays an outline
view of the CU and LDEV numbers installed on the array (for example, CU 01 has a number of LDEVs,
including 01:00). The LDEV number’s format changes if the LDEV is an expanded (LUSE) volume (for
example, if LDEV volume 01:00 consists of five concatenated LDEVs, its number is 01:00*5). One of the
following icons appear.
Icon LDEV status

Normal LDEV
Variable-sized volume (CV)
Expanded (LUSE) volume
LDEV Information table

This table is in the upper-right of the Volume Manager pane, and displays data for the LDEV you select in
the LDEV Information tree.
The LDEV Information table displays detailed information for all open-system LDEVs in the selected CU. If
you select a normal LDEV, the information in this table is for the top LDEV. If you select a LUSE volume, the
information in this table is for all LDEVs in the LUSE volume. The table displays the following information:
• LDEV: LDEV status icon (Table 32) and the CU and LDEV numbers. If the selected LDEV is a LUSE
volume, the LDEV number of the top LDEV in the LUSE volume appears.
NOTE: If an LDEV number ends with # (for example, 00:01#), the LDEV is an external LU. For
more information about external LUs, see the HP StorageWorks External Storage XP user guide.
NOTE: If an LDEV number ends with V (for example, 00:01V), the LDEV is a virtual volume
(V-VOL). For more information about V-VOLs, see the HP StorageWorks Snapshot XP user guide.
• Emulation: Emulation type. If the selected LDEV is a LUSE volume, the emulation type appears with an
asterisk and the number of volumes in the LUSE volume (for example, OPEN-E*5). If the selected LDEV
is a CVS volume, the emulation type appears with CVS (for example, OPEN-3 CVS).
• Capacity: LDEV capacity in either MB or GB, depending on the unit selected in the Capacity Unit box.
• RAID: LDEV’s RAID level.
NOTE: The RAID level is left unspecified with a hyphen (-) when the LDEV is an external LU or
virtual volume (V-VOL).
• PG: Combination of the disk group and parity group. If the LDEV extends over two or more parity
groups, the smaller parity group number appears.
NOTE: If a parity group number starts with E (for example, E1-1), the parity group consists of one
or more external LUs.
NOTE: If a parity group number starts with V (for example, V1-1), the parity group consists of one
or more virtual volumes (V-VOLs).
• Paths: Number of paths set for the LDEV. If this column displays the number of paths for an LDEV, you
can use the LDEV as the top LDEV of a LUSE volume (see ”Volume Manager operations using a
path-defined LDEV” on page 129).
• Access Attribute: Access attribute set for the LDEV.
• IO Suppression Mode: Displays Disable when I/O requests from hosts are suppressed, or Enable if
I/O requests from hosts are not suppressed.
• Cache Mode: Displays Disable when cache is set to be unused for responding to I/O requests from
hosts, or Enable when cache is set to be used for responding to I/O requests from hosts.
• Ex-Dev Info.: Displays the LDEV’s drive type. Displays an asterisk (*) when the drive type is SATA.
Displays nothing when the drive type is not SATA.
• CLPR: ID of the cache logical partition (CLPR) to which the displayed volumes belong. The CLPR ID is
composed of a CLPR number (two-digit) and a CLPR name (maximum of 16 characters)
Capacity Unit box
Capacity of the LDEV displayed in the Capacity column, in either GB (default) or MB.
Selected LDEVs
Number of LDEVs selected in the LDEV Information table.

Select an LDEV list
Displays the selected CU’s LDEVs, CVS volumes, and LUSE volumes that are eligible to become part of a
LUSE volume. The selected LDEV number becomes the top LDEV number of a LUSE volume.
Volume Count list
Number of LDEVs forming a LUSE volume.
For example, if you select 3 in the Volume Count list, three LDEVs are expected to form a LUSE volume
and three LDEVs are added to the Expanded LDEVs list.
NOTE: You can select only LDEVs from the Volume Count list. You cannot select LUSE volumes.
Free LDEVs table

Displays the LDEVs, CVS volumes, or LUSE volumes selected in the Select an LDEV list that are eligible to
become part of a LUSE volume.
• LDEV: LDEV status icon (Table 32) and CU and LDEV numbers. If the selected LDEV is a LUSE volume,
the LDEV number of the top LDEV in the LUSE volume appears.
• RAID: LDEV’s RAID level.
NOTE: The RAID level is left unspecified with a hyphen (-) when the LDEV is an external LU or
virtual volume (V-VOL).
• PG: Combination of the disk group and parity group. If the LDEV extends over two or more parity
groups, the smaller parity group number appears.
NOTE: If a parity group number starts with V (for example, V1-1), the parity group consists of one
or more virtual volumes (V-VOLs).
• CLPR: CLPR number and name. The CLPR number consists of two digits. The CLPR name consists of up
to six characters. For more information about cache logical partitions (CLPRs), see the
HP StorageWorks XP Disk/Cache Partition user guide.
• Selected LDEVs: Number of LDEVs selected in the Free LDEVs table.
Expanded LDEVs list
Displays LDEVs selected as LUSE volume components. An LDEV is added to this list by clicking Add.
• Selected LDEVs: Number of LDEVs selected in the Expanded LDEVs list.
• Number of LDEVs: Number of LDEVs displayed in the Expanded LDEVs list.
• Size: Total capacity of LDEVs displayed in the Expanded LDEVs list, in either GB or MG.
Buttons
• Add: Moves the selected LDEV from the Free LDEVs table to the Expanded LDEVs list.
• Delete: Move the selected LDEV from the Expanded LDEVs list to the Free LDEVs table.
• Set: Creates a LUSE volume consisting of the volumes currently in the Expanded LDEVs list. The new
LUSE appears in blue bold italics on the LDEV Information table, but is not actually created until you
click Apply.
• Apply: Implements settings on the array.
• Cancel: Cancels settings.
Volume Manager operations shortcut menu

When you right-click one of the LDEVs in the LDEV Information table on the Volume Manager pane, a
shortcut menu listing commands for Volume Manager operations appears.
Figure 87 Volume Manager operations shortcut menu

• Set LUSE Volume
Displays the Set LUSE confirmation pane (Figure 88). You can confirm whether or not you want to
continue the operation to create a LUSE volume. For more information, see ”Creating LUSE volumes”
on page 151.
• Release LUSE Volume
Displays the Release LUSE confirmation pane (Figure 89). You can confirm whether or not you want to
continue the operation to release a LUSE volume. For more information, see ”Releasing LUSE volumes”
on page 153.
• Reset LUSE Volume
Displays the Reset LUSE confirmation pane (Figure 90). You can confirm whether or not you want to
continue the operation to release an unregistered LUSE volume. For more information, see Resetting
unregistered LUSE volumes, page 154.
• Concatenation List
Displays the Concatenation List pane (Figure 91). For more information, see ”Viewing concatenated
parity groups” on page 151.

Set LUSE Confirmation pane
When you right-click the free LDEVs you want to form the LUSE volume in the LDEV Information table, and
select Set LUSE Volume, the Set LUSE Confirmation pane appears. You can verify that the LDEVs listed in
the confirmation pane are the ones you want to create a LUSE volume.
Figure 88 Set LUSE Confirmation pane

• LUSE components list
Displays information about LDEVs that constitute the LUSE volume.
• LDEV: LDEV icon, CU number, and LDEV number.
• Emulation: LDEV’s emulation type.

• Capacity: LDEV’s capacity.
• OK: Creates the LUSE volume and sets the LUSE volume configuration to have LDEVs in the LUSE
components list. LDEVs registered as components of the LUSE volume appear in blue bold italics in the
LDEV Information table.
• Cancel: Cancels the operation to create a LUSE volume using LDEVs in the list.
Release LUSE Confirmation pane

When you select Release LUSE Volume, the Release LUSE Confirmation pane appears. You can verify that
the LUSE volumes listed in the confirmation pane are the ones you want released.
NOTE: If the selected LUSE volume has a path or if you selected anything other than a LUSE volume, this
pane lists only LDEVs containing a LUSE volume to be released.
Figure 89 Release LUSE Confirmation pane

• LDEVs containing a LUSE volume to be released
Displays LDEVs containing LUSE volumes to be released.

• OK: Releases the LUSE volume configuration in the release list. Released LDEVs appear in blue bold
italics in the LDEV Information table.
• Cancel: Cancels the release Volume Manager operation.

Reset LUSE Confirmation pane
When you select Reset LUSE Volume from the Volume Manager operation shortcut menu, the following
pane appears. You can confirm the LDEV that is still not registered to the array as a LUSE volume and
whether or not you want to reset this unregistered LUSE volume to the state it was in before it was created.
Figure 90 Reset LUSE Confirmation pane

• Unregistered LUSE volume list
Displays LDEVs created into a LUSE volume but not yet registered to the array that you can reset to the
state they were in before they were created.

• OK: Resets the unregistered LUSE volume to the state it was in before it was created.
• Cancel: Cancels the reset LUSE operation.
Concatenation List pane

In the array, data can be written to an LDEV that extends over concatenated parity groups. Concatenation
of parity groups enables faster access to data.
To view a concatenated parity group, right-click the free LDEVs you want to form the LUSE volume in the
LDEV Information table. If parity groups are concatenated, a shortcut menu appears. Select Concatenation
List to display the Concatenation List pane.
NOTE: If a parity group number starts with E (for example, E1-1), the parity group consists of one or
more external LUs.
Volume Manager operations

This section provides instructions for performing Volume Manager operations.
Preparing to use Volume Manager

Before starting a Volume Manager operation on a selected array, unmount the open system volumes, and
remove the LU paths to the open volumes. For instructions, see ”Deleting LU paths” on page 84.
Volume Manager operations

If you are going to implement changes for Volume Manager, you must have write permission for Volume
Manager, and must be in Modify mode. The array information icons are on the upper right corner. These
icons are described in detail in the HP StorageWorks Command View XP user guide for XP Disk Arrays or
the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
Viewing LUSE configuration information

You can view the current LUSE configuration on the Volume Manager pane (Figure 86).
• The LDEV Information tree displays an outline view of CU and LDEV numbers installed on the array in
a hierarchical structure.
• The LDEV Information table displays detailed information for all open-system LDEVs in the selected CU.
If you select a normal LDEV, information in this table is for the top LDEV. If you select a LUSE volume,
information in this table is for all the LDEVs in the LUSE volume.

Viewing concatenated parity groups

1. From the Volume Manager pane, select a CU number in the LDEV Information tree. The LDEV
Information table displays all LDEVs in the selected CU.
2. In the LDEV Information table, right-click the free LDEVs you want to form the LUSE volume. If parity
groups are concatenated, a shortcut menu appears.
NOTE: Concatenation List does not appear if the selected LDEV does not extend over
concatenated parity groups.
3. Select Concatenation List. The Concatenation List pane (Figure 91) appears.
4. When you are finished viewing the list, click OK (or Cancel).
Creating LUSE volumes
CAUTION: LUSE creation is a destructive operation. Move and/or back up your data before
proceeding.
There are three ways to create a LUSE volume:

• ”Creating LUSE volumes using the Volume Count list” on page 151) (recommended)
• ”Creating LUSE volumes using the Select an LDEV list” on page 152)
• ”Creating LUSE volumes using the LDEV information table” on page 153)
Creating LUSE volumes using the Volume Count list
1. From the Volume Manager pane, select a CU number to create a LUSE volume from the LDEV
Information tree.
2. In the Select an LDEV list, select a top LDEV of the LUSE volume.
The selected top volume appears in the Expanded LDEVs list. Normal LDEVs, CVS volumes, and LUSE
volumes that can be used for a LUSE volume appear in the Free LDEVs table.
3. In the Volume Count list, select the number of LDEVs needed to form a LUSE volume.
The Expanded LDEVs list displays as many LDEVs as specified in the Volume Count list. For example, if
you select 3 in the Volume Count list, three LDEVS appear in the Expanded LDEVs list.
NOTE: You cannot select LUSE volumes in the Volume Count list. To select LUSE volumes, select
LDEVs from the Free LDEVs table, and click Add.
a. To add more LDEVs to the Expanded LDEVs list, select normal LDEVs, CVS volumes, or LUSE
volumes in the Free LDEVs table, and click Add.
b. To delete LDEVs from the Expanded LDEVs list, select the LDEVs in the Expanded LDEVs list, and
click Delete.
4. Click Set.
A pane appears. If the displayed pane asks whether you want to perform a Volume Manager
operation on a volume that has a path definition (see ”Volume Manager operations using a
path-defined LDEV” on page 129 for more information about this operation), follow step 4a. If the Set
LUSE Confirmation pane appears, follow step 4b.
a. If the displayed pane asks whether you want to perform a Volume Manager operation on a volume
that has a path definition, click OK. A confirmation message appears. Go to step 5.
To cancel the Volume Manager operation, click Cancel. The previous pane appears, and you can
retry the operation.
b. If the Set LUSE Confirmation pane appears, go to step 5.
5. To create the LUSE, click OK. The selected top LDEV appears (in blue bold italics) as a LUSE volume in
the LDEV Information table.
NOTE: You can reset LUSE volumes that have been created but not yet registered to the array
(those in blue bold italics) to the state they were in before they were created (see ”Resetting
unregistered LUSE volumes” on page 154).
6. Click Apply.
7. Click OK (or Cancel). Settings for this Volume Manager operation are registered for the array.
Creating LUSE volumes using the Select an LDEV list
CAUTION: Creating a LUSE volume destroys existing data. To protect the data, make a backup copy of
the existing data before starting the LUSE creation operation.
1. In the Volume Manager pane, select a CU number in the LDEV Information tree.
2. In the Select an LDEV list, select the first LDEV for the LUSE from the Free LDEVs table that displays
available LDEVs.
3. Select one or more additional normal LDEVs, CVS volumes, or LUSE volumes for the LUSE volume.
Click Add to move selected LDEVs from the Free LDEVs table to the Expanded LDEVs list.
4. To delete an LDEV from the Expanded LDEVs list and move it back to the Free LDEVs table, select one
or more volumes, and click Delete.
5. Click Set.
operation on a volume that has a path definition (see Figure 87), follow step 5a. If the displayed pane
asks whether you want to perform an Volume Manager operation that affects more than one SLPR or
CLPR, follow step 5b. If the Set LUSE Confirmation pane appears, follow step 5c.
a. To perform a Volume Manager operation on a volume that has a path definition (see Figure 87),
click OK. If a message appears asking whether you want to perform a Volume Manager operation
that affects more than one SLPR or CLPR, go to step 5b. If such a message does not appear, go to
step 6.
If you do not want to perform a Volume Manager operation on a volume that has a path definition,
click Cancel. The previous pane appears, and you can retry the operation.
b. To perform a Volume Manager operation that affects more than one SLPR or CLPR, click OK. A
confirmation pane appears. Go to step 6.
If you do not want to perform a Volume Manager operation that affects more than one SLPR or
CLPR, click Cancel. The previous pane appears, and you can retry the operation.
c. If the Set LUSE Confirmation pane appears, go to step 6.
6. Click OK (or Cancel).
NOTE: New settings appear on the pane in blue bold italics are not yet registered to the array.
You cannot reset LUSE volumes that have been created but not yet registered to the array (those in
blue bold italics) to the state they were in before they were created (see ”Resetting unregistered
LUSE volumes” on page 154).
7. Click Apply (or Cancel).

8. Click OK.

Creating LUSE volumes using the LDEV information table
1. In the Volume Manager pane, select a CU number in the LDEV Information tree. The LDEV Information
table displays all LDEVs in the selected CU.
2. In the LDEV Information table, right-click the normal LDEVs, CVS volumes, or LUSE volumes you want to
form the LUSE volume, and select Set LUSE Volume.
operation on a volume that has a path definition (see Figure 87), follow step 2a. If the displayed pane
asks whether you want to perform a Volume Manager operation that affects more than one SLPR or
CLPR, follow step 2b. If the Set LUSE Confirmation pane appears, follow step 2c.
a. To perform a Volume Manager operation on a volume that has a path definition (see Figure 87),
click OK. If a message appears asking whether you want to perform a Volume Manager operation
that affects more than one SLPR or CLPR, go to step 2b. If such a message does not appear, go to
step 3.
If you do not want to perform a Volume Manager operation on a volume that has a path definition,
click Cancel. The previous pane appears, and you can retry the operation.
b. To perform a Volume Manager operation that affects more than one SLPR or CLPR, click OK. A
confirmation pane appears. Go to step 3.
If you do not want to perform a Volume Manager operation that affects more than one SLPR or
CLPR, click Cancel. The previous pane appears, and you can retry the operation.
c. If the Set LUSE Confirmation pane appears, go to step 3.
3. Click OK to create the LUSE volume (or Cancel).
NOTE: New settings appearing on the pane in blue bold italics are not yet registered to the
array. You can reset LUSE volumes that have been created but not yet registered to the array (in
blue bold italics) to the state they were in before they were created (see ”Resetting unregistered
LUSE volumes” on page 154).

Releasing LUSE volumes
CAUTION: Releasing LUSE volumes is a destructive operation. Move and/or back up data before
proceeding. Delete all SCSI paths to the LUSE volume you want released.
1. In the Volume Manager pane, select the CU number from the LDEV Information tree. The LDEV
2. In the LDEV Information table, right-click a LUSE volume, and select Release LUSE Volume. The Release
LUSE Confirmation pane appears.
3. Verify that the LUSE volumes listed in the confirmation pane are the ones you want released.
NOTE: New settings appear on the Volume Manager pane in blue bold italics, but are not yet
implemented.

Changing LUSE capacities

There are two ways to change a LUSE volume’s capacity:
• Expanding LUSE capacities
To expand a LUSE volume’s capacity, select the LUSE volume you want to expand, and add LDEVs or
LUSE volumes; or first select the LDEVs or LUSE volumes you want to add, and select a LUSE volume to
be expanded. For more information, see ”Creating LUSE volumes” on page 151.
• Reducing LUSE capacities
You cannot reduce an existing LUSE volume’s capacity. If you want a LUSE volume to have a smaller
capacity, you must first release the LUSE volume (see ”Releasing LUSE volumes” on page 153), and
redefine the LUSE volume (see ”Creating LUSE volumes” on page 151).
Resetting unregistered LUSE volumes

When you create a LUSE volume, it remains highlighted in blue bold italics until you register it into the
array by clicking Apply. A LUSE volume in blue bold italics indicates you can reset this LUSE volume to the
state it was in before it was created.
NOTE: You can use this function to reset an unregistered LUSE volume to the state it was in before it was
created. However, you cannot recover LUSE volumes that have already been released to the state they
were in when they were created. Therefore, if the LUSE volume you created consists of any LDEVs (those
in blue bold italics) that have been released from a different LUSE volume, you can only reset the LUSE
volume to the state it was in when the constituting LDEVs were released from the other LUSE volume.
1. In the Volume Manager pane, select a CU number from the LDEV Information tree. The LDEV
2. In the LDEV Information table, right-click an unregistered LUSE volume (in blue bold italics), and select
Reset Selected Volume. The Reset LUSE Confirmation pane appears.
3. Click OK.
The setting of the selected LUSE volume that is not registered yet is reset to the state it was in before this
LUSE volume was created, and the LUSE volumes or LDEVs constituting the selected LUSE volume that
has just been reset appear in the LDEV Information table.

10 Custom Volume Size operations
This chapter describes Custom Volume Size (CVS) operations.
Custom Volume Size panes

This section describes components of the Customized Volume pane.
Customized Volume pane

To open the Customized Volume pane:
1. Click the Volume Manager button ( ). The Volume Manager pane appears.
2. Click the Customized Volume tab. The Customized Volume pane appears.
Figure 92 Customized Volume pane

Parity Group - LDEV tree
Displays the hierarchical structure of an array. For example, a disk group number (Box 1), parity group
number (1-1), RAID level (RAID1(2D +2D)), and VDEV number (1-1-(1)) appear.
NOTE: If a parity group number begins with E (for example, E1-1), the parity group consists of one or
more external LUs.
NOTE: If a parity group number starts with V (for example, V1-1), the parity group consists of one or
more virtual volumes (V-VOLs).
NOTE: If an LDEV number ends with # (for example, 00:01#), the LDEV is an external LU. For more
information about external LUs, see the HP StorageWorks External Storage XP user guide.
NOTE: The RAID level is left unspecified with a hyphen (-) when the LDEV is an external LU.
The following icons indicate parity group status.
Table 33 Parity group status icons
Icon Status
Parity group.
Set of parity groups that are concatenated into one. Each LDEV in this set of parity groups usually
extends over more than one parity group.
The following icons indicate VDEV status.
Table 34 VDEV status icons
Icon Status
No pending CVS actions.
NOTE: This icon appears immediately after you click Apply.
CVS actions have been stored, but not yet implemented on the array.
NOTE: This icon appears before you click Apply.
Capacity Unit list

Used to select the unit for displaying the volume capacity: MB, Cyl, or block.
When you manipulate mainframe volumes, you can only select Cyl.
Parity Group - LDEV table
Displays information about logical volumes in the selected VDEV.
• No.: Volume number.
• CU:LDEV: Icon and CU:LDEV number. Free indicates a free space.
NOTE: When free spaces appear in the Parity Group - LDEV table, you can convert any of them
into a customized volume (CV). To convert free spaces, right-click a free space, and select Install
CV. For more information, see ”Creating CVS volumes (Install CV operation)” on page 181.
NOTE: If an LDEV number ends with V (for example, 00:00V), the LDEV is a virtual volume. For
more information about virtual volumes, see the HP StorageWorks Snapshot XP user guide.

The following icons indicate the LDEV’s status.
Icon LDEV status

Normal LDEV
LUSE volume
LDEV reserved for Auto LUN XP
CVS volume
CVS volume reserved for Auto LUN XP
Free space
LDEV secured by Hitachi SANtinel - S/390®
• Emulation: Emulation type.

• Capacity: Volume’s capacity displayed in the unit selected from the Capacity Unit list.
• Paths: Number of LU paths. Blank indicates no LU paths.
• Access Attribute: Volume’s access attribute.
• Status: Volume’s status. You must click LDEV Status to display the volume’s status.
Table 36 Volume status
Status Description
Normal Volume is in a normal status.
Blocked Volume is in a blocked status. Hosts cannot access the blocked volume.
Warning Volume has a problem.
Format Volume is being formatted.
Correction Access Volume’s access attribute is being changed.
Copying Volume’s data is being copied.
Read Only Hosts can only read the volume. Hosts cannot write data to a volume in Read Only
status.
Shredding Shredding operation is in progress.
Unknown System does not recognize the volume’s status.
• Attribute: Volume’s attribute.

Table 37 Volume attributes
Attribute Description
Pool (pool-id) Volume is a pool volume (pool-VOL). The pool ID is enclosed by parentheses.
JNL Volume Volume is a journal volume.
Progress bar
Displays the operation’s progress.
Buttons
• LDEV Status: Displays the current volume status.
• Shredding Param: Displays the Shredding Param (Parameter) pane. You can define shredding settings
in the Shredding Param pane.
• Download: Downloads the file containing Shredding operation results.
• Apply: Implements settings made in this pane.
• Cancel: Cancels settings made in this pane.
Volume to Space Confirmation pane

This pane appears before the Volume to Space function starts. Confirm the volumes you want to initialize
to spaces.
NOTE: An error occurs if volumes selected as targets of the Volume to Space function include a volume
that cannot be processed by the Volume to Space function (see ”Volume Manager guidelines” on
page 128).
Figure 93 Volume to Space Confirmation pane

• VDEV information table: Displays information about volumes that will be converted to space areas.
• VDEV: Set of a disk group, parity group, and VDEV number.
NOTE: If a VDEV number starts with E (for example, E1-1-(1)), the parity group consists of one or
more external LUs.
• CU:LDEV: CU and LDEV numbers.

• Capacity: Volume capacity in the unit selected from the Capacity Unit list in the Customized Volume
pane (Figure 92).
• OK: Registers information about volumes in the setting list as data for the Volume to Space operation.
• Cancel: Cancels the Volume to Space operation.
Install CV pane (1)

Use this pane to define and install one or more CVS volumes under an existing volume. You can specify
the emulation type and capacity of the CVS volume you want to create.
NOTE: Different panes are used for OPEN-V and other emulation types (see ”Install CV pane (1) for
OPEN-V” on page 159 and ”Install CV pane (1) for other than OPEN-V” on page 160).

Install CV pane (1) for OPEN-V
Figure 94 shows the first Install CV pane that appears when the selected emulation type is OPEN-V.
Figure 94 Install CV pane (1) for OPEN-V

The Install CV pane (1) has the following features:
• Parity Group: Selected free space’s VDEV number. The VDEV number indicates the parity group where
the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV belongs to parity group
number 1-1.
NOTE: If a VDEV number starts with E (for example, E1-1-(1)), the VDEV belongs to a parity group
that consists of one or more external LUs.
NOTE: If a VDEV number starts with V (for example, V1-1-(1)), the VDEV belongs to a parity
group that consists of one or more virtual volumes (V-VOLs).
• Emulation: CVS volume’s emulation type (OPEN-V).

• LDEV information table: Displays the following information about the CVS volume settings:
• No.: CVS volume’s setting number.
• Capacity: CVS volume’s capacity displayed in the unit selected from the Capacity Unit list.
• available LDEVs: Number of LDEVs that can be created in the VDEV. The maximum is 512 LDEVs for
RAID5 (7D+1P) or RAID6 (6D+2P), and 256 LDEVs for other RAID levels.
• Capacity Unit: Unit the CVS volume’s capacity is displayed in.
• MB: Megabytes (MB). This unit is used for specifying the capacity of open-system volumes.
• Cyl: Cylinders (Cyl). This unit is used for specifying the capacity of mainframe volumes.
NOTE: This unit can also be used for specifying the capacity of OPEN-V volumes.
• Block: Blocks. This unit is used for specifying the capacity of external LUs. For more information
about external LUs, see the HP StorageWorks External Storage XP user guide.
• Specify capacity and number: Capacity and number of CVs in the CVS volume you want to create.
• Capacity: CVS volume’s capacity in the unit selected in the Capacity Unit list. The available
capacity range (minimum - maximum) is shown on the right (for example, 46 - 6720 MB,
50 - 7168 Cyl, or 315 - 8513 blocks). The value can be incremented by 1 MB, cylinder, or block.
• Number: Number of volumes of that size. The available range is shown on the right (for example,
1 - 489).
• Divide free space by number: Used to create CVS volumes by specifying the number of CVs in the CVS
• Number: Number of CVs in the CVS volume. If you select this option, the available range is shown
on the right (for example, 1 - 47).
• Divide free space by capacity: Used to create CVS volumes by specifying the capacity of CVs in the
CVS volume to be created.
• Capacity: Capacity of the CVS volumes to be created. The available capacity range (minimum -
maximum) is shown below Capacity (for example, 46 - 6720 MB, 50 - 7168 Cyl, or
315 - 8513 blocks).
• Set remaining space as volume: Used to create a CVS volume using the remaining space in the VDEV.
• Set: Displays the selected settings in the LDEV information table on the left.
• Delete: Deletes the settings for CVS volumes selected in the LDEV information table.
• Clear: Deletes all the settings in the LDEV information table.
• Next: Displays the Install CV pane (2).
• Cancel: Cancels the selected settings, and returns to the Customized Volume pane.
Install CV pane (1) for other than OPEN-V
Figure 95 shows the Install CV pane (1) for emulation types other than OPEN-V.
Figure 95 Install CV pane (1) for other than OPEN-V

This pane has the following features:
• Parity Group: Selected free space’s VDEV number.

• Emulation Type: Emulation type.

• Capacity Unit: Unit (MB, Cyl, or block) in which the volume capacity is displayed.
• Capacity: CVS volume’s capacity in the unit selected in the Capacity Unit list. The available capacity
range (minimum - maximum) is shown on the right (for example, 46 - 6720 MB, 50 - 7168 Cyl, or
315 - 8513 blocks). The value can be incremented by 1 MB, cylinder, or block.
• Delete: Deletes the settings for the CVS volumes selected in the LDEV information table.
• Emulation: CVS volume’s emulation type.
• Available LDEVs: Number of LDEVs that can be created in the VDEV. The maximum is 512 LDEVs for
RAID5 (7D+1P) or RAID6 (6D+2P), and 256 LDEVs for other RAID levels.
• Next: Displays the Install CV pane (2).
• Cancel: Cancels the selected settings and returns to the Customized Volume pane.
Install CV pane (2)

This pane displays the CVS volumes to be created in the table on the top. You can specify the CVS
volume’s CU and LDEV numbers.
Figure 96 Install CV pane (2)
• CVS volume-setting information table: On the upper right of the pane, displays detailed information
about the CVS volumes to be created.
• Parity Group: Number of the VDEV to which the CVS volume belongs. The VDEV number indicates
the parity group where the VDEV belongs. For example, if the VDEV number 1-1-(1) appears, the
VDEV belongs to parity group number 1-1.

• Capacity: CVS volume’s capacity displayed in the unit selected from the Capacity Unit list on the
Install CV pane (1).
• CU:LDEV: CU and LDEV numbers for the CVS volume to be created. The default is blank.
• Select LDEV No. area: Used to set LDEV numbers for the CVS volumes you are creating.
• Select CU No.: Select a CU number from the drop-down list. The default is CU 00.LDEV number
settings for the selected CU number appear in the Select LDEV No. table.
• Interval: When selecting more than one volume, use this list to set the interval between the LDEV
numbers to be assigned to the newly created volumes. The default value is 0. When you select 0,
consecutive LDEV numbers are assigned.
NOTE: The value you specify as the interval between LDEV numbers counts only available LDEV
numbers and skips those that are not selectable.
• Select LDEV No. table: Displays LDEV numbers for the CU number selected from the Select CU No.
list. Gray indicates LDEV numbers that are not selectable, white indicates unused LDEV numbers,
and blue indicates available LDEV numbers. You can select an LDEV number from the white LDEV
numbers in the table. When you set the LDEV number, that LDEV number becomes available and
changes to blue.
NOTE: LDEV numbers that are not selectable might already be in use or assigned to another
emulation group (grouped by 32 LDEV numbers) (see Table 38).

Table 38 Emulation groups
Emulation group D-type (overseas PCM) emulation type

Group 1 3390-3, 3390-3A, 3390-3B, 3390-3C, 3390-9, 3390-9A,
3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, 3390-LC,
3390-M, 3390-MA, 3390-MB, 3390-MC
Group 2 3390-3R
Group 4 OPEN-3, OPEN-8, OPEN-9, OPEN-E
Group 6 OPEN-V
• CU number of another SLPR is used: When selected, you can select the number of an LDEV that does
not exist in the SLPR to which the parity group does not belong. When cleared, you can only select the
number of the LDEV in the SLPR to which the parity group belongs.
NOTE: The CU number of another SLPR is used check box appears only when you log in as a
storage administrator and when there are two or more SLPRs.
• Back: Returns to Install CV pane (1).

• Next: Opens one of the following panes:
• If the selected LDEV number’s boundary area does not have an SSID, the Install CV pane (3) for
setting an SSID appears.
• If the selected LDEV’s boundary area has an SSID, the Install CV pane (4) appears.
• Cancel: Cancels the LDEV’s settings, and returns to the Customized Volume pane.
• Clear: Removes a CU:LDEV number that is already assigned. To remove a CU:LDEV number, right-click
the CVS volume number corresponding to the CU:LDEV number you want to remove, and select Clear.
Install CV pane (3)
This pane appears when you create CVS volumes if the selected LDEV number’s boundary area does not
have an SSID. You can set an SSID on the Install CV pane (3).
Figure 97 Install CV pane (3) for setting SSIDs

• Set SSID tree: Displays a hierarchical structure of SSID setting information containing CU numbers (for
example, CU 00), SSID boundary areas (for example, 00-3F), and SSIDs (for example, 0004). When
the selected LDEV number’s SSID boundary area has no SSID, the following icons appear before the
related CU number and LDEV boundary area. The SSID of a boundary area having no SSID is ----.
Table 39 Set SSID tree icons (Install CV)
Icon Description
CU number is not extracted.
CU number is extracted.
LDEV boundary area.
• Set SSID table: Used to set the SSID boundary area.

• CU: CU number containing an LDEV boundary with no SSID.
• LDEV Boundary: Boundary area of an LDEV number with no SSID.
• SSID: Specified SSID. The default is blank.
• Input SSID: Used to select or enter the desired SSID. You can enter the SSID only when you log in as a
storage administrator.
• SSID number of another SLPR is used: When selected, you can select the number of an SSID that does
number of an SSID in the SLPR to which the parity group belongs.
NOTE: The SSID number of another SLPR is used check box appears only when you log in as a

NOTE: You cannot enter a number in the Input SSID list when the SSID number of another SLPR is
used check box is cleared.
• Set: Sets the SSID you select or enter in the Input SSID list to the table. The Set SSID table displays the
new SSID.
• Back: Returns to Install CV pane (2).
• Next: Opens the Install CV pane (4) (confirmation pane).
• Cancel: Cancels the SSID setting, and returns to the Customized Volume pane.
Install CV pane (4)

Use this pane to confirm the settings of the CVS volumes to be created.
Figure 98 Install CV pane (4) for confirming Install CV settings

• CVS volume setting information table: Displays a list of CVS volumes to be created.
• VDEV: VDEV number for the CVS volume to be created.
• Emulation: Emulation type of the CVS volume to be created.

• Capacity: CVS volume’s capacity displayed in the unit selected from the Capacity Unit list in the
Install CV pane (1).
• CU:LDEV: CU:LDEV number of the CVS volume to be created.
(V-VOL). For more information about virtual volumes, see the HP StorageWorks Snapshot XP user
guide.
• Back: Returns to the Install CV pane (2) or Install CV pane (3).

• OK: Registers the Install CV settings, and returns to the Customized Volume pane.
• Cancel: Cancels the Install CV settings, and returns to the Customized Volume pane.
Make Volume pane

Make Volume pane (1) for OPEN-V
Figure 99 shows the first Make Volume pane that appears when the selected emulation type is OPEN-V.
Figure 99 Make Volume pane (1) for OPEN-V

• Parity Group: VDEV number of the CVS volume to be initialized. The VDEV number indicates the
parity group where the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV
belongs to parity group number 1-1.


• available LDEVs: Number of LDEVs that can be created in the VDEV. The maximum is 512 LDEVs
for RAID5 (7D+1P), and 256 LDEVs for other RAID levels.
• Capacity Unit: Unit the CVS volume’s capacity is displayed in.
• MB: Megabytes (MB). This unit is used for specifying the capacity of open-system volumes.
• Cyl: Cylinders (Cyl). This unit is used for specifying the capacity of mainframe volumes.
NOTE: This unit can also be used for specifying the capacity of OPEN-V volumes.
• Block: Blocks. This unit is used for specifying the capacity of external LUs. For more information
about external LUs, see the HP StorageWorks External Storage XP user guide.
• Specify capacity and number: Used to specify the capacity and the number of CVs in the CVS volume
you want to create.
• Capacity: CVS volume’s capacity in the unit selected in the Capacity Unit list. The available
capacity range (minimum - maximum) is shown below Capacity Unit (for example, 46 - 6720 MB,
50 - 7168 Cyl, or 315 - 8513 blocks).
• Number: Number of volumes of that size. The available range is shown on the right to the box (for
example, 1 - 489).
• Divide free space by number: Used to create CVS volumes by specifying the number of CVs in the CVS
• Number: Number of CVs in the CVS volume. If you select this option, the available range is shown
on the right to the box (for example, 1 - 47).
• Divide free space by capacity: Used to create CVS volumes by specifying the capacity of CVs in the
CVS volume to be created.
• Capacity: Capacity of the CVS volumes to be created. The available capacity range (minimum -
maximum) is shown below Capacity (for example, 46 - 6720 MB, 50 - 7168 Cyl, or
315 - 8513 blocks).
• Set remaining space as volume: Used to create a CVS volume using the remaining space in the VDEV.
NOTE: This option is greyed out when there are two or more free spaces in the VDEV.
• Delete: Deletes the settings from a the CVS volume selected in the LDEV information table.
• Clear: Deletes all the settings in the LDEV information table.
• Next: Opens the Make Volume pane (2). When no CV is set, no volume is made in the VDEV by the
Make Volume operation. In this case, this button displays a message, and returns to the Customized
Volume pane.
Make Volume Pane (1) for other than OPEN-V
Figure 100 shows the Make Volume pane (1) for emulation types other than OPEN-V.
Figure 100 Make Volume pane (1) for other than OPEN-V
• Parity Group: Selected free space’s VDEV number. The VDEV number indicates the parity group where
the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV belongs to parity group
number 1-1.
• Emulation Type: Emulation type.

• Capacity Unit: Unit (MB, Cyl, or block) used to display the volume capacity.
• Capacity: Capacity of the CVS volume in the unit selected in the Capacity Unit list. The available
capacity range (minimum - maximum) is shown on the right (for example, 46 - 6720 MB,
50 - 7168 Cyl, or 315 - 8513 blocks). The value can be incremented by 1 MB, cylinder, or block.
• Delete: Deletes the settings of CVS volumes selected in the LDEV information table.
• Available LDEVs: Number of LDEVs that can be created in the VDEV. The maximum is 512 LDEVs for
RAID5 (7D+1P), and 256 LDEVs for other RAID levels.

• Next: Displays the Make Volume pane (2). When no CV is set, no volume is made in the VDEV by the
Make Volume operation. In this case, this button displays a message, and returns to the Customized
Volume pane.
Make Volume pane (2)

Use this pane to assign CU and LDEV numbers for the CVS volumes to be created.
Figure 101 Make Volume pane (2)

• CVS volume-setting information table: On the upper right of the pane, displays detailed information
about the CVS volumes to be created.
• Parity Group: Number of the VDEV to be initialized. The VDEV number indicates the parity group
where the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV belongs to
parity group number 1-1.

• Capacity: CVS volume’s capacity displayed in the capacity unit selected from the Capacity Unit list
on the Make Volume pane (1).
• CU:LDEV: CU and LDEV numbers for the CVS volume to be created. The default is blank.
guide.
• Select LDEV No. area: Used to set LDEV numbers for the CVS volumes you are creating.
• Select CU No.: CU number. The default is CU 00. The settings of LDEV numbers for the selected CU
number appear in the Select LDEV No. table.
• Interval: When you select more than one volume, used to set the interval between the LDEV
numbers that need to be assigned to the newly created volumes. The default value is 0. When you
select 0, consecutive LDEV numbers are assigned.
• Select LDEV No. table: Displays the settings of LDEV numbers for the CU number selected from the
Select CU No. list. Gray indicates the LDEV numbers that are not selectable, white indicates unused
LDEV numbers, and blue indicates available LDEV numbers. You can select an LDEV number from
the white LDEV numbers in the table. When you set the LDEV number, that LDEV number becomes
available and changes to blue.
NOTE: LDEV numbers that are not selectable may be already in use or already assigned to
another emulation group (grouped by 32 LDEV numbers) (see Table 38).
guide.
number of an LDEV in the SLPR to which the parity group belongs.
• Back: Returns to Make Volume pane (1).

• If the selected LDEV number’s boundary area does not have an SSID, the Make Volume pane (3)
for setting an SSID appears.
• If the selected LDEV number’s boundary area has an SSID, the Make Volume pane (4) appears.
• Cancel: Cancels the settings for the LDEV, and returns to the Customized Volume pane.

a CVS volume number corresponding to the CU:LDEV number you want to remove, and select Clear.

This pane appears when you create CVS volumes if the selected LDEV number’s boundary area does not
have an SSID. You can set an SSID on the Make Volume pane (3).
Figure 102 Make Volume pane (3) for setting SSIDs

• Set SSID information tree: Displays a hierarchical structure of SSID setting information that contains CU
numbers (for example, CU 00), SSID boundary areas (for example, 00-3F), and SSID (for example,
0004). When the selected LDEV number’s SSID boundary area has no SSID, the following icon
appears before the related CU number and the related LDEV boundary area. The SSID of the
boundary area having no SSID is ----.
Table 40 Set SSID tree icons (Make Volume)
Icon Description
LDEV boundary area.
• Set SSID table: Used set the SSID boundary area.

• Input SSID: Used to select or enter the SSID. You can enter the SSID only when you log in as a storage
administrator.
not exist in the SLPR to which the parity group does not belong. When cleared, you can select only the
number of an SSID in the SLPR to which the parity group belongs.
NOTE: You cannot enter the number in the Input SSID list when the SSID number of another SLPR
is used check box is cleared.
• Set: Sets the SSID you select or enter in Input SSID list to the table. The Set SSID table displays the new
SSID.
• Back: Cancels the SSID setting, and returns to the Make Volume pane (2).
• Next: Displays the Make Volume pane (4) (confirmation pane).
• Cancel: Returns to the Customized Volume pane.

Use this pane to confirm the settings of the CVS volumes to be created.
Figure 103 Make Volume pane (4) for confirming Make Volume settings
• CVS volume-setting information table: Displays a list of CVS volumes to be created.
• VDEV: VDEV number for the CVS volume to be created. The VDEV number indicates the parity
group where the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV belongs
to parity group number 1-1.
• Emulation: Emulation type of the CVS volume to be created (OPEN-V).

• Capacity: CVS volume’s capacity displayed in the unit selected from the Capacity Unit list in the
Make Volume pane (1).

• CU:LDEV: CU:LDEV number of the CVS volume to be created.
guide.
• Back: Returns to the Make Volume pane (2) or Make Volume pane (3).
• OK: Registers the Make Volume settings, and returns to the Customized Volume pane.
• Cancel: Cancels the Make Volume settings, and returns to the Customized Volume pane.
Volume Initialize pane (1)

Use this pane to initialize CVS volumes other than OPEN-V.
Figure 104 Volume Initialize pane (1)

• Normal volume-setting information table: On the upper right of the pane, displays detailed information
about the CVS volumes to be initialized.
• Parity Group: Number of the VDEV to be initialized. The VDEV number indicates the parity group
where the VDEV belongs. For example, if VDEV number 1-1-(1) appears, the VDEV belongs to
parity group number 1-1.
• No.: Setting number of the CVS volume to be initialized.

• Emulation: Emulation type of the CVS volume to be initialized.
• Capacity: Capacity of the CVS volume to be initialized in either MB for open-system volumes or
cylinders (Cyl) for mainframe volumes.
• CU:LDEV: CU and LDEV numbers for the CVS volume to be initialized. The default is blank.
• Select LDEV No. area: Used to set LDEV numbers for the CVS volume to be initialized.
• Select CU No.: CU number. The default is CU 00. The LDEV number settings for the selected CU
number appear in the Select LDEV No. table.
• Interval: When selecting more than one volume, used to set the interval between the LDEV numbers
to be assigned to the newly created volumes. The default value is 0. When you select 0,
consecutive LDEV numbers are assigned.
• Select LDEV No. table: Displays the LDEV number settings for the CU number selected in Select CU
No. Gray indicates LDEV numbers that are not selectable, white indicates unused LDEV numbers,
and blue indicates available LDEV numbers. You can select an LDEV number from the white LDEV
numbers in the table. When you set the LDEV number, that LDEV number becomes available and
changes to blue.
NOTE: LDEV numbers that are not selectable may be already in use or already assigned to the
other emulation group (grouped by 32 LDEV numbers) (see Table 38).
number of an LDEV in the SLPR to which the parity group belongs.

• If the selected LDEV number’s boundary area does not have an SSID, the Volume Initialize pane (2)
for setting an SSID appears.
• If the selected LDEV number’s boundary area has an SSID, the Volume Initialize pane (3) appears.
• Cancel: Cancels the settings for the LDEV, and returns to the Customized Volume pane.
a CVS volume number corresponding to the CU:LDEV number you want to remove, and select Clear.

This pane appears during the initialization of CVS volumes if the selected LDEV number’s boundary area
does not have an SSID. You can set an SSID on the Volume Initialize pane (2).
Figure 105 Volume Initialize pane (2) for setting SSIDs

• Set SSID tree: Displays a hierarchical structure of SSID setting information containing CU numbers (for
example, CU 00), SSID boundary areas (for example, 00-3F), and SSID (for example, 0004). When a
selected LDEV number’s SSID boundary area has no SSID, the following icon appears before the
related CU number and LDEV boundary area. The SSID of a boundary area having no SSID is ----.
Table 41 Set SSID tree icons (Volume Initialize)
Icon Description
LDEV boundary area.
• Set SSID table: Used to set the SSID boundary area.

• Input SSID: Used to select or enter the SSID. You can enter the SSID only when you log in as a storage
administrator.
not exist in the SLPR to which the parity group does not belong. When cleared, you can select only the
number of the SSID in the SLPR to which the parity group belongs.
NOTE: You cannot enter the number in the Input SSID list when the SSID number of another SLPR
is used check box is cleared.
• Set: Sets the SSID you select or enter in the Input SSID list to the Set SSID table. The Set SSID table
displays the new SSID.
• Back: Cancels the SSID setting, and returns to the Volume Initialize pane (1).
• Next: Opens the Volume Initialize pane (3) (confirmation pane).
• Cancel: Returns to the Customized Volume pane.

Use this pane to confirm the settings of the CVS volumes to be initialized.
Figure 106 Volume Initialize pane (3) for confirming Volume Initialize settings
• CVS volume-setting information table: Displays a list of the CVS volumes to be initialized.
• VDEV: VDEV number for the CVS volume to be initialized.
• Emulation: Emulation type of the CVS volume to be initialized.

• Capacity: Capacity of the CVS volume to be initialized, either in MB for open-system volumes or
cylinders (Cyl) for mainframe volumes.
• CU:LDEV: CU:LDEV number of the CVS volume to be initialized.

guide.
• Back: Returns to the Volume Initialize pane (1) or Volume Initialize pane (2).
• OK: Registers the Volume Initialize settings, and returns to the Customized Volume pane.
• Cancel: Cancels the Volume Initialize settings, and returns to the Customized Volume pane.
Concatenation List pane

In the array, data can be written to an LDEV that extends over concatenated parity groups. Concatenation
of parity groups enables faster access to data. The Concatenation List pane displays concatenated parity
groups.

• Parity Group: Displays concatenated parity groups.
• OK: Closes the Concatenation List pane.
Format All pane

Use this pane to format all blocked volumes in parity groups in the local and/or external array.
CAUTION: You cannot format virtual volumes.
Figure 108 Format All pane

• Parity Group Type: Used to specify volumes to be formatted.
• All Type: Blocked volumes in all parity groups in the local and external arrays are formatted.
• Internal PG: Blocked volumes in all parity groups in the local array are formatted.
• External PG: Blocked volumes in all parity groups in the external array are formatted.
• List: Displays information about volumes to be formatted.
• PG: Parity groups containing the volumes to be formatted.
• Blocked Count: Number of blocked volumes to be formatted.
• OK: Applies the Format All pane settings to the Customized Volume pane, and closes the Format All
pane.
NOTE: After you click OK, the tree in the Customized Volume pane displays VDEVs immediately
below parity groups containing volumes to be formatted.
• Cancel: Cancels the settings, and closes the Format All pane.
Write to Control Blocks pane

Use this pane to make external mainframe volumes usable. This pane overwrites control blocks in external
LU in the specified external LU group. Control blocks contain information used for managing volumes.

CAUTION: Operations in this pane must be performed only on external LUs with data areas that are
zero-formatted.
Figure 109 Write to Control Blocks pane

• Target ExG: External LU groups containing volumes to be made usable.
• ExG: External LU group numbers.
• External Storage: Information about external arrays.
• Add: Moves external LU groups selected in the Candidate ExG list to the Target ExG list.
• Delete: Moves external LU groups selected in the Target ExG list to the Candidate ExG list.
• Candidate ExG: List of external LU groups.
• ExG: External LU group numbers.
• External Storage: Information about external arrays.
• OK: Applies settings in the Write to Control Blocks pane to the Volume Manager pane, and closes the
Write to Control Blocks pane.
• Cancel: Cancels settings in the Write to Control Blocks pane, and closes the pane.
Performing Custom Volume Size operations

This section describes procedures for performing Custom Volume Size (CVS) operations.
Before starting CVS operations

Before starting a CVS operation on a selected array, ensure that mainframe volumes are disconnected
from the host, and remove LU paths to the open volumes. For instructions, see ”Deleting LU paths” on
page 84.
CVS operations
You must have write permission for CVS operations, and must be in Modify mode. For more information
about assigning user access, see the HP StorageWorks Command View XP user guide for XP Disk Arrays
or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
Viewing current CVS configuration information

You can view current CVS configuration information on the Customized Volume pane.
• Viewing VDEV and LDEV configuration information
You can view configuration information for VDEVs and LDEVs on the Customized Volume pane
(Figure 92). This pane shows an outline of group numbers, parity group numbers, RAID levels, and
VDEV numbers and a table of CU:LDEV numbers, emulation types, LDEV capacities, and path settings
of VDEVs selected in the tree.
• Viewing LDEV number setting information
You can view setting information for LDEV numbers for a CU number in a selected parity group on the
Install CV pane (2) (Figure 96), Make Volume pane (2) (Figure 101), and Volume Initialize pane (1)
(Figure 104).
In the table, gray indicates LDEV numbers that are already in use, white indicates unused LDEV
numbers, and blue indicates available LDEV numbers.
Viewing concatenated parity groups

1. From the Customized Volume pane, right-click a set of parity groups ( ) from the Parity Group - LDEV
tree. If there are concatenated parity groups, a shortcut menu appears.
NOTE: If you select a parity group icon that does not indicate concatenated parity groups ( ),
the shortcut menu does not appear.
2. Select Concatenation List. The Concatenation List dialog box appears.

3. Click OK.
Converting logical volumes to space
CAUTION: The Volume to Space function is a destructive operation. Data on the logical volumes being
converted is lost when the operation is complete. You are responsible for backing up data as needed
before performing this operation.
Use the Volume to Space function to convert one or more logical volumes (LDEVs) to space, which deletes
the selected LDEVs from that VDEV. In other words, the Volume to Space function converts one or more
selected LDEVs (FVs or CVs) in a VDEV into spaces. For more information, see ”Volume to Space function”
on page 132.
1. On the upper right of the XP Remote Web Console main pane, select a CU group from the drop-down
list.
2. From the Customized Volume pane, select the LDEV folder in the Parity Group - LDEV tree to open a list
of VDEVs.
3. In the LDEV Information table, select a VDEV to display detailed information about the LDEVs of the
selected VDEV.
4. From the CU:LDEV list, select one or more LDEVs.
NOTE: For the OPEN-V emulation type, you can also convert LUSE volumes into free space. If the
available LDEV is a LUSE volume, the emulation type appears with an asterisk and the number of
volumes in the LUSE volume (for example, OPEN-V*3) in the Emulation column of the table.
NOTE: To select two or more adjacent LDEVs, select the LDEVs while pressing the Shift key. To
select two or more discrete LDEVs, select the LDEVs while pressing the Ctrl key.
5. Right-click the selected LDEVs, and select Volume to Space. The Volume to Space Confirmation dialog
box appears.
6. If the listed volumes are correct, click OK.

The change is not yet implemented in the array, but the following changes appear on the Customized
Volume pane:
• Selected LDEVs are listed as Free.
• Figures in the Capacity column are not yet updated
• The color of the VDEV icon you manipulated in the Parity Group - LDEV tree changes from red to
blue. You cannot manipulate blue VDEVs until you click Apply or Cancel, but you can perform
additional Volume to Space operations on VDEVs with red icons.
NOTE: A notation appears across the bottom of the pane indicating the change is in process (for
example, LDEVs >> Free Spaces and Array is Refreshing) or the operation is complete (for
example, Complete).
Creating CVS volumes (Install CV operation)

Use the Install CV function to define and install one or more CVS volumes (CVs) in spaces created with the
Volume to Space operation or define and install one or more CVS volumes (CVs) in free spaces created
as a result of creating volumes in VDEVs.
NOTE: The Install CV function allocates CVS volumes in the order in which the function finds sufficient
free space for the CVS volumes. For optimum space allocation, allocate CVS volumes in descending order
of capacity.
list.
2. From the Customized Volume pane, select the LDEV folder in the Parity Group - LDEV tree to display a
list of Control Units. From the LDEV Information table, select a VDEV to display detailed information
about LDEVs in the selected VDEV.
3. Right-click any part of the Parity Group - LDEV tree, and select Install CV.
If the selected VDEV is an OPEN-V volume, the Install CV pane (1) for OPEN-V appears (Figure 94).
Go to step 4.
If the selected VDEV is a volume other than OPEN-V, the Install CV pane (1) for other than OPEN-V
appears (Figure 95). Go to step 5.
4. From the Install CV pane (1) for OPEN-V, do the following:
a. In the Capacity Unit list, select the capacity unit for the selected volume from the following options:
MB, Cyl, or block.
b. Select one of the following CVS volume creation methods:
• Specify capacity and number
• Divide free space by number
• Divide free space by capacity
• Set remaining space as volume.
NOTE: If there are two or more free spaces in the VDEV, Divide free space by number, Divide free
space by capacity, and Set remaining space as volume are not available.
c. Specify the CVS volume’s capacity or the number of CVs according to the selected method. For
example:
• If you select Specify capacity and number, enter the capacity (either in MB, Cyl, or blocks)
selected in the Capacity Unit list and the number of CVs in Capacity and Number, respectively.
• If you select Divide free space by number, enter the number of CVs in the Number box.
• If you select Divide free space by capacity, enter the capacity in the Capacity box.
• If you select Set remaining space as volume, go to step 6.
NOTE: The Install CV function allocates CVS volumes in the order in which the function finds
sufficient free space for the CVS volumes. For optimum space allocation, allocate CVS volumes in
descending order of capacity.
d. Click Set to display the setting in the LDEV Information table. To remove CVS volume settings
displayed in the LDEV Information table, do the following:
• To remove a setting, select the CVS volume, and click Delete. When a confirmation message
appears, click OK.
• To remove all settings, click Clear. When a confirmation message appears, click OK.
e. To create other CVS volumes, repeat step 4a through step 4d. After setting all CVS volumes, go to
step 6.
5. From the Install CV pane (1) for other than OPEN-V, do the following:
a. In the Emulation Type list, select the emulation type.
b. In the Capacity box, enter the capacity of the CVS volume you want to create, either in MB or
blocks for open systems or in cylinders (Cyl) for mainframe volumes. The available capacity range
(minimum - maximum) appears on the right of the Capacity box. The value can be incremented by
1 MB or block for open systems or by 1 Cyl for mainframe systems.
NOTE: The Install CV function allocates CVS volumes in the order in which the function finds
sufficient free space for the CVS volumes. For optimum space allocation, allocate CVS volumes in
descending order of capacity.
c. Click Set to display the setting in the LDEV Information table. To remove CVS volume settings
appears, click OK.
d. To create other CVS volumes, repeat step 5a through step 5c. After setting all CVS volumes, go to
step 6.
6. Click Next. The Install CV pane (2) appears.
7. Select one or more CVS volume numbers to assign CU and LDEV numbers.
8. In the Select CU No. list, select a CU number.
9. In the Select LDEV No. table, select an LDEV number from the white LDEV numbers. Gray indicates
LDEV numbers that are not selectable, white indicates unused LDEV numbers, and blue indicates
available LDEV numbers. The CU and LDEV numbers appear in the CU:LDEV field of the CVS
volume-setting information table.
NOTE: You cannot specify an LDEV number if free LDEV numbers in LUSE configuration are not
available in the selected CU.
10.To set other CVS volumes, repeat step 7 through step 9. To remove a CU:LDEV number that is already
assigned, select one or more CVS volume numbers corresponding to the CU:LDEV numbers you want
to remove, right-click, and select Clear.

11.After setting all CU and LDEV numbers, click Next. If the selected LDEV number’s boundary area does
not have an SSID, the SSID setting pane appears. Go to step 12. If the selected LDEV number’s
boundary area has an SSID, go to step 16.
12.On the SSID setting pane, select the CU number.
13.In the Input SSID list, select a new SSID.
NOTE: When you log in as a storage administrator and the SSID number of another SLPR is used
check box is selected, you can also enter an SSID in the Input SSID list.
14.Click Set. The SSID appears in the SSID box of the SSID setting area.
15.To set two or more SSIDs, repeat step 12 through step 14.
16.After setting all SSIDs, click Next. The Install CV confirmation dialog box appears.
17. Verify that the information displayed in the Install CV confirmation dialog box is correct, and click OK.
New settings appear in blue bold italics in the LDEV Information table on the Customized Volume
pane.
NOTE: Setting changes are not yet implemented in the array. You cannot manipulate blue VDEVs
until you click Apply to apply the changes to the array or Cancel to cancel them, but you can install
additional CVs in VDEVs with red icons.
18.To apply the changes to the array, click Apply (or Cancel to cancel them).
19. Click OK.
NOTE: When the Install CV operation starts, a notation appears across the bottom of the pane
indicating the progress and completion at the end of operation.
Deleting CVS volumes

To delete an individual CVS volume within a VDEV, use the Volume to Space operation (see ”Converting
logical volumes to space” on page 180).
Converting CVs back to FVs (Volume Initialize operation)
CAUTION: The Volume Initialize function is a destructive operation. Data on the CVS volume being
Use the Volume Initialize function to convert a CVS volume back to a fixed volume. This operation
de-installs all variable-sized volumes under a CVS volume, and reformats the CVS volume as a normal FV
(fixed volume).
CAUTION: An error message might appear if a Volume Initialize and Make Volume operation are
performed concurrently. For this error message, the part code is 0003 and the error number is 1041. If
this message appears, ensure that these operations are performed separately.
list.
2. From the Customized Volume pane, select the LDEV folder on the Parity Group - LDEV tree to display a
list of VDEVs, and select a VDEV. The LDEV Information table displays detailed information about the
LDEVs.
NOTE: If the selected VDEV contains one or more CVs that violate any restriction for the Volume
Initialize operations (see ”Volume Manager guidelines” on page 128), you cannot perform
Volume Initialize operations. Remove all invalid CVs before performing Volume Initialize
operation.
3. Right-click any part of the Parity Group - LDEV tree, and select Volume Initialize. The Volume Initialize
pane (1) appears.
4. On the Volume Initialize pane (1):
a. Select one or more CVS volume numbers.
b. In the Select CU No. list, select a CU number.
c. In the Select LDEV Number table, select an LDEV number from the white LDEV numbers. The CU
and LDEV number appear in the CU:LDEV field.
d. To change a CU:LDEV number that is already assigned, select one or more volume numbers
corresponding to the CU:LDEV numbers you want to remove, right-click, and select Clear.
5. After setting all CU and LDEV numbers, click Next.
If the selected LDEV number’s boundary area does not have an SSID, the SSID setting pane appears.
Go to step 8. If the selected LDEV number’s boundary area has an SSID, go to step 10.
6. On the SSID setting pane, select the CU number.
7. In the Input SSID list, select a new SSID.
NOTE: When you log in as a storage administrator and the SSID number of another SLPR is used
check box is selected, you can also enter an SSID in the Input SSID list.
8. Click Set. The SSID appears in the SSID field of the SSID setting area.
9. To set two or more SSIDs, repeat step 6 through step 8.
10.After setting all SSIDs, click Next. The Volume Initialize confirmation pane appears.
11.Verify that the information in the Volume Initialize confirmation pane is correct, and click OK.
A notation appears across the top of the pane indicating the volume has been initialized. The color of
the VDEV icon you manipulated in the Parity Group - LDEV tree changes from red to blue.
NOTE: Setting changes are not yet implemented in the array. You cannot manipulate VDEVs
denoted by blue icons until you either apply the changes to the array or cancel them, but you can
initialize additional CVS volumes in VDEVs denoted by red icons.
12.To apply changes to the array, click Apply (or Cancel to cancel them).
NOTE: If desired, you can make settings on the Make Volume function (see ”Re-creating CVs after
initializing the VDEV (Make Volume operation)” on page 185) before clicking Apply. If you click
Apply after making settings on the Volume Initialize and Make Volume functions, settings on these
functions are applied simultaneously to the array.
13.Click OK.

NOTE: When the Volume Initialize operation starts, a notation appears across the bottom of the
pane indicating the progress and completion at the end of the operation.
Re-creating CVs after initializing the VDEV (Make Volume operation)
CAUTION: The Make Volume function is a destructive operation. Data on the CVS volume being
CAUTION: An error message might appear if Volume Initialize and Make Volume operations are
performed concurrently. For this error message, the part code is 0003 and the error number is 1041. If
this message appears, ensure that these operations are performed separately.
list.
2. From the Customized Volume pane, select the LDEV folder in the Parity Group - LDEV tree to display a
list of VDEVs, and select a VDEV for OPEN-V. The LDEV Information table displays detailed
information about the LDEVs.
NOTE: If the selected VDEV contains one or more CVs that violate any restriction for the Make
Volume function (see ”Volume Initialize and Make Volume functions” on page 139), you cannot
perform the Make Volume operation. Remove all invalid CVs before performing the Make Volume
operation.
3. Right-click any part of the Parity Group - LDEV tree, and select Make Volume. If the selected VDEV is
an OPEN-V volume, the Make Volume pane (1) for OPEN-V appears (Figure 99). Go to step 4. If the
selected VDEV is a volume other than OPEN-V, the Make Volume CV pane (1) for other than OPEN-V
appears (Figure 100). Go to step 5.
4. On the Make Volume pane (1) for OPEN-V, do the following:
a. In the Capacity Unit list, select the capacity unit for the selected volume from the following options:
MB, Cyl, or block.
b. Select one of the following CVS volume creation methods:
• Specify capacity and number
• Divide free space by number
• Divide free space by capacity
• Set remaining space as volume
NOTE: If there are two or more free spaces in the VDEV, Divide free space by number, Divide free
space by capacity, and Set remaining space as volume are not available.
c. Specify the CVS volume’s capacity and number of CVs according to the selected method. For
example:
• If you select Specify capacity and number, enter the capacity, either in MB or Cyl, selected in
the Capacity Unit list, and the number of CVs in the Capacity and Number boxes.
• If you select Divide free space by number, enter the number of CVs in the Number box.
• If you select Divide free space by capacity, enter the capacity in the Capacity box.
• If you select Set remaining space as volume, go to step 6.
d. Click Set to display the setting in the LDEV Information table. To remove CVS volume settings
appears, click OK.
e. To set other CVS volumes, repeat steps step 4a through step 4d. After setting all CVS volumes, go
to step 6.
5. On the Make Volume pane (1) for other than OPEN-V, do the following:
a. In the Emulation Type list, select the emulation type.
b. In the Capacity field, enter the capacity of the CVS volume you want to create, either in MB or
block for open systems or in cylinders (Cyl) for mainframe volumes. The available capacity range
(minimum - maximum) is shown on the right of the Capacity field. The value can be incremented by
1 MB or block for open systems or 1 Cyl for mainframe systems.
c. Click Set to display the setting in the LDEV information table. To remove CVS volume settings
displayed in the LDEV information table, do the following:
appears, select OK.
• To remove all settings, click Clear. When a confirmation message displays, click OK.
d. To create other CVS volumes, repeat step 5a through step 5c. After setting all CVS volumes, go to
step 6.
6. Click Next. The Make Volume pane (2) appears.
7. Select one or more CVS volume numbers to assign CU and LDEV numbers.
8. In the Select CU No. list, select a CU number.
9. In the Select LDEV No. table, select an LDEV number from the white LDEV numbers. Gray indicates
LDEV numbers that are not selectable, white indicates LDEV numbers, and blue indicates available
LDEV numbers. The CU and LDEV number appear in the CU:LDEV field of the CVS volume-setting
information table.
NOTE: You cannot specify an LDEV number if free LDEV numbers in the LUSE configuration are
not available in either of the following CUs:
• The CU displayed in the Select CU No. list.
• A CU whose CU number is larger than the CU number displayed in the Select CU No. list.
10.Repeat step 7 through step 9 to set other CVS volumes. To remove a CU:LDEV number that is already
assigned, select one or more CVS volume numbers corresponding to the CU:LDEV numbers you want
to remove, right-click, and select Clear.
11.After setting all CU and LDEV numbers, click Next. If the selected LDEV number’s boundary area does
not have an SSID, the SSID setting pane appears. Go to step 12. If the selected LDEV number’s
boundary area has an SSID, go to step 17.
12.On the SSID setting pane, select the CU number
13.In the Input SSID box, select a new SSID.
NOTE: When you are logged in as a storage administrator and the SSID number of another SLPR
is used check box is selected, you can also enter an SSID in the Input SSID list.
14.Click Set. The SSID appears in the SSID box of the SSID setting area.
15.To set two or more SSIDs, repeat step 12 through step 14.

16.After setting all SSIDs, click Next. The Make Volume confirmation pane appears.
17. Verify that the information is correct, and click OK.
The created CVS volumes appear in blue bold italic in the LDEV Information table on the Customized
Volume pane.
NOTE: Setting changes are not yet implemented in the array. You cannot manipulate VDEVs
denoted by blue icons until you click Apply to apply the changes to the array or Cancel to cancel
them, but you can initialize additional CVS volumes in VDEVs denoted by red icons.
18.To apply changes to the array, click Apply (or Cancel to cancel them).
NOTE: If desired, you can make settings on the Volume Initialize function (see ”Converting CVs
back to FVs (Volume Initialize operation)” on page 183) before clicking Apply. If you click Apply
after making settings on the Make Volume and Volume Initialize functions, settings on these
functions are applied simultaneously to the array.
19. Click OK.
NOTE: When the Make Volume operation starts, a notation appears across the bottom of the
pane indicating the progress and completion at the end of the operation.
Formatting LDEVs
Use the LDEV Format feature to format volumes, including external LUs. To format volumes, ensure that the
volumes are in blocked status, as explained in the following procedure.
NOTE: For more information about external LUs, see the HP StorageWorks External Storage XP user
guide.
NOTE: You cannot format virtual volumes.
list.
2. From the Customized Volume pane, click LDEV Status.
3. Confirm that the current status of the desired volume (external mainframe volume) is Normal in the
Status column of the Parity Group - LDEV table.
4. Right-click the selected volume, and select Blockade.
5. Confirm that the status of the volume in the Status column of the LDEV Information table changed to
Blocked, and all of the volume’s information appears in blue bold italics.
6. Click Apply. In the confirmation pane, click OK. The new setting is implemented into the array and a
notification pane appears notifying you that the implementation is complete. Click OK.
7. Confirm that the volume is Blocked in the Status column of the LDEV Information table on the
Customized Volume pane.
8. To specify the blocked volumes you want to format, do one of the following:
• Right-click the volume with Blocked status in the LDEV Information table, and select Format.
• To format all blocked internal and external LUs, right-click LDEV at the top of the tree, and select
Format All. In the Format All pane, select All Type from the Parity Group Type list. Confirm that the
list displays internal and external LUs to be formatted, and click OK.
• To format all blocked internal LUs, right-click LDEV at the top of the tree, and select Format All. In
the Format All pane, select Internal PG from the Parity Group Type list. Confirm that the list displays
internal LUs to be formatted, and click OK.
• To format all blocked external LUs, right-click LDEV at the top of the tree, and select Format All. In
the Format All pane, select External PG from the Parity Group Type list. Confirm that the list
displays external LUs to be formatted, and click OK.
9. Confirm that the status of the specified volumes in the Status column of the LDEV Information table on
the Customized Volume pane changed to Format, and all of the volume’s information appears in bold
blue italics.
10.Click Apply. In the confirmation pane, click OK. The words Format in progress appear next to the
Progress Bar on the Customized Volume pane with the percentage of completion.
11.When the percentage shown on the Progress Bar reaches 100%, a notification pane appears
notifying you that the formatting is complete. Click OK.
12.Confirm that the status of the volumes in the Status column of the LDEV Information table on the
Customized Volume pane is Normal.
Making external mainframe volumes usable

To use external LUs with the array, you must usually use External Storage XP to perform external LU
mapping, and then use Volume Manager’s Format or Format All command to format the volumes (see
”Formatting LDEVs” on page 187). However, when you format external mainframe volumes in this way,
the formatting operation might take a long time.
Use the following procedure to make external mainframe volumes usable more quickly.
CAUTION: Only storage administrators can perform the following operation. Storage partition
administrators cannot perform this operation.
1. Zero-format the external mainframe volumes.
NOTE: The term “zero-formatting” refers to a formatting operation that writes the number 0 (zero)
to the entire disk area. For more information about zero-formatting volumes, see the documentation
for the mainframe system or external array you are using.
2. Use External Storage XP to map the zero-formatted external LUs and register the volumes in an
external LU group. For more information, see the HP StorageWorks External Storage XP Users Guide.
CAUTION: Ensure that the external LU group does not include volumes that are not
zero-formatted. If an external LU group includes volumes that are not zero-formatted, the volumes
are blocked when you perform the operation described in step 3. Therefore, hosts cannot read
from or write to the volumes. If you have not zero-formatted external LUs but you want to make the
external LUs usable with the array, use CVS’s Format or Format All command.
3. Use Volume Manager to specify the external LU group, and overwrite control blocks in the volumes in
the specified external LU groups. After overwriting finishes, the external LUs are usable with the array.
NOTE: Control blocks are a type of area in a volume that contains information other than user
data. Information required for managing a volume is recorded in control blocks.
To overwrite control blocks in volumes in an external LU group:

list.

2. From the Customized Volume pane, right-click the LDEV folder at the top of the tree, and select Write to
Control Blocks.
3. In the Write to Control Blocks pane, select the desired external LU group from the Candidate ExG list,
and click Add. The selected external LU group moves to the Target ExG list.
NOTE:
• You can select one or more external LU groups.
• To remove external LU groups from the Target ExG list, select the external LU groups from the
list, and click Delete. The external LU groups move to the Candidate ExG list.
4. Click OK.
CAUTION: Cancel the operation if the external LU group includes volumes that are not
zero-formatted. If you continue the operation, hosts cannot access the volumes.
6. Click OK. Volume Manager starts overwriting the control blocks.
11 Troubleshooting Volume Manager and Custom
Volume Size
• For troubleshooting information about an array, see the array’s documentation.
• For troubleshooting information about Command View XP or XP Remote Web Console, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP
Remote Web Console user guide for XP12000/XP10000/SVS200.
192 Troubleshooting Volume Manager and Custom Volume Size
Index
Numerics copying paths 93

16-port channel adapters, serial numbers and names 37 customer support 12
4-port channel adapters, serial numbers and names 30 Customized Volume pane 155
8-port channel adapters, serial numbers and names 33 CVS operations
capacities 134, 135
A concatenated parity groups, viewing 180
configuration information, viewing 179
Add iSCSI name button 61
Customized Volume pane 155
Add LU Path button 62
deleting volumes 183
Add WWN button 61
emulation types 133
addresses, Fibre Channel ports 26, 99
functions 130
AIX environments
Install Custom Volume function 132
server host modes 77
Install CV function 181
WWNs, findings 122
Install CV pane (1) 158
AL-PA addresses 26
alternate paths
defining 93
limitations 53
installing software 141
viewing 95
Make Volume function 139, 185
arbitrated loop physical address (AL-PA) 26
Make Volume pane (1) 166
audience, documentation 11
authentication
Port Information list 71
switches, Fibre Channel environments 47, 72, 108,
management area capacities 138
110
Modify mode 142
Target list 72
permissions 179
Authentication pane 68
samples 130
authentication, host
slot capacities 139
Fibre Channel environments 45, 70, 104
SSID requirements 140
iSCSI environments 49, 71, 72, 112, 116
starting software 141, 179
list 72
system requirements 141
authentication, mutual
troubleshooting 191
Fibre Channel environments 48
Volume Initialize function 139, 183
iSCSI environments 52, 115
Volume Initialize pane (1) 173
authentication, user
Fibre Channel environments 43, 104
Volume to Space Confirmation pane 158
Volume to Space function 132, 180
B
block volumes, formatting 177 D
Blockade function 187
data transfer speed, Fibre Channel ports 27, 100
boundary values for RAID levels 138
deleting
CVS volumes 183
C
host bus adapters 91
Capacity Unit list 156 host groups 87
Change Port Mode box 66 iSCSI names 92
channel adapters (CHAs) package status icons 63 iSCSI targets 88
CHN list 67 LU paths 84
command devices 25, 97 WWNs 92
Command View XP PC 141 disabling LUN security 23, 97
concatenated parity groups 92, 151, 180 document
Concatenation List pane 149, 177 conventions 12
control blocks 188 feedback 13
conventions, document 12
prerequisites 11 H
related documentation 11 help, obtaining 12, 13
DYNIX host modes 77 high-speed mode
16-port channel adapter serial numbers 37
E 4-port channel adapter serial numbers 30
emulation types 8-port channel adapter serial numbers 33
CV capacities 134 applying 27, 100
CVS specifications 133 Change Port Mode box 66
groups 163 XP10000/SVS200 serial numbers 41
management area capacities 138 host authentication
slot capacities 139 Fibre Channel environments 45, 70, 104
SSID requirements 140 iSCSI environments 49, 71, 72, 112, 116
enabling Target list 72
LUN Manager 53 host bus adapters
LUN security 23, 96 deleting 91
expanded LDEVs 145, 151, 152, 153 names, changing 89, 90
external LU groups 188 host groups
external mainframe volumes associating to logical volumes 83
making usable 188 authentication, enabling and disabling 104
writing to control blocks 178 clearing user information 107
configuring 18
F creating 75
fabric topology 26 deleting 87
FC Switch Information list 72 deleting host bus adapters 91
FC-AL topology 26 initializing group 0 88
feedback, documentation 13 mode, changing 85
Fibre Channel environments name, changing 85
Change Port Mode box 66 registering hosts in 79
changing WWN names 89 registering user information 104
copying paths 93 Host list 72
creating host groups 75 host user information, Fibre Channel environments
data transfer speed 27, 100 changing 105
defined 17 deleting 106
finding WWNs 121 specifying 107
host authentication 45, 70, 104 host user information, iSCSI environments
host information 105 changing 113
host settings and connection results 107 clearing 116
LU paths 18, 75 deleting 114
LUN Path tree 56 registering on a target 112
mutual authentication 48 specifying 115
Package tree 63 hosts
port addresses 26, 99 finding WWNs 121
Port Information list 71 modes 77
port information, specifying 109 registering in host groups 79
Port pane 62 registering user information 104
port status 56 settings and connection results 107
Port table 64 HP
registering hosts in host groups 79 storage web site 13
registering port user information 109 Subscriber’s choice web site 12
switch authentication 47, 72, 108, 110 technical support 12
topology 25, 99 HP-UX environments, finding WWNs 122
user authentication 43, 68, 104
firmware, supported 11 I
Format All pane 177 Initiator/External MIX modes
formatting LDEVs 187 16-port channel adapter serial numbers 37
free LDEVs 145, 151, 152, 153 4-port channel adapter serial numbers 30
applying 27, 100
194
XP10000/SVS200 serial numbers 41 LDEV Information table 153
Install CV function 130, 132, 181 Select an LDEV list 152
Install CV pane Volume Count list 151
(1) 158 parity group tree 155
(2) 161 path-defined 129
(3) 164 releasing a LUSE volume 153
(4) 165 resetting an unregistered volume 154
installing Volume Manager and CVS 141 restrictions 128
iSCSI environments Set LUSE Confirmation pane 147
Add button 61 status icons 157
Change Port Mode box 67 status table 60
channel adapter packages 64 Volume to Space function 132
configuring 17 limitations
connection results 116 LUN Manager 53
copying paths 93 Volume Manager 128
host authentication 49, 71, 72 Linux host modes 77
host groups, registering hosts in 81 logging in to LUN Manager 75
LU paths 20, 75 logical volumes, associating host groups 83
mutual authentication 52, 115 loop IDs 26
names, changing 90 LU Path table 58
Package tree 63 LU Path tree 56
Port pane 62 LU paths
port status 58 Add button 62
Port table 64 associating host groups to logical volumes 83
settings 42, 101 copying 93
status, connection 43, 103 defining 75
user authentication 48, 68, 112 deleting 84
iSCSI folder 58 Fibre Channel environment 18
iSCSI Function box 66 iSCSI environment 20
iSCSI name table 59, 60 limitations 18
iSCSI names, deleting 92 NAS environment 22
iSCSI targets LU paths, alternate
associating to logical volumes 83 defining 93
creating 78 viewing 95
deleting 88 LUN Manager pane 55
host authentication, enabling and disabling 112 LUN Manager, starting 55, 75
host bus adapters, deleting 91 LUN security
host mode, changing 86 disabling 23, 97
initializing 88 enabling 23, 96
mutual authentication 115 LUN status icons 59
registering host user information 112 LUSE volumes
settings and connection results 116 capacities, changing 153
iSNS server settings 42, 101 concatenated parity groups 151
creating with
L LDEV Information table 153
LDEV Information table 153 Select an LDEV list 152
LDEV table 156 Volume Count list 151
LDEVs guidelines 128
associating host groups to logical volumes 83 releasing 147, 153
command devices 25, 97 reset confirmation pane 149
Concatenation List pane 149, 177 resetting unregistered 154
expanded 145, 151, 152, 153 setting 147
formatting 187 viewing configuration information 150
free 145, 151, 152, 153
Information table 143 M
Information tree 143 Make Volume function 130, 139, 185
LUN Path table 59 Make Volume pane
LUSE volume capacity, changing 153 (1) 166
LUSE volumes, creating with (2) 169
(3) 171 XP10000/SVS200 41
(4) 172 port statuses
management area capacity 138 Fibre Channel 56
Modify mode 142 iSCSI 58
mutual authentication NAS 57
Fibre Channel environments 48, 107 Port table 64
iSCSI environments 52, 115, 116 ports
alternate paths, defining 93
N Change Port Mode box 66
NAS environments channel adapter packages 64
channel adapter status 52 copying paths 93
channel adapters 117 Fibre Channel switch authentication 47, 72, 108,
CHN list 67 110
configuring 17 Fibre Channel, specifying information 109
copying paths 94 iSCSI settings 42, 101
host groups, registering hosts in 79 iSCSI targets, creating 78
LU paths 22 LU paths 75
Package tree 63 LUN security 96
Port pane 62 mutual authentication 48
port status 57 security 23
NAS folder 57, 64 speed modes 27, 100
NetWare host modes 77 WWN name table 60
nicknames, changing 89, 90 prerequisites 11
Novell NetWare host modes 77
R
O RAID levels, boundary values 138
OPEN volumes, LUSE guidelines 128 RAID Manager XP command devices 25, 97
open-system hosts 18 RAID parity group status 155
OPEN-V RAID volumes status table 61
CV capacity 135 related documentation 11
Install Custom Volume function 132 Release LUSE Confirmation pane 147
Install CV pane (1) 159 releasing a LUSE volume 153
Make Volume function 185 remote command devices 98
Make Volume operation 139 Reset LUSE Confirmation pane 149
Make Volume pane (1) 166 resetting unregistered LUSE volumes 154
management area capacity 138 restrictions
parity group configuration 131 LUN Manager 53
OpenVMS host modes 77 Volume Manager 128
overwriting control blocks 188
S
P security
Package tree 63 disabling 97
parity groups enabling 96
concatenated 92, 151, 180 ports 23
Concatenation List pane 149, 177 RAID Manager XP 25
configuration 131 Select an LDEV list 152
Format All pane 177 Sequent environments
status icons 155 finding WWNs 122
phone support 12 host modes 77
pinging iSCSI hosts 43, 66 serial numbers, ports
platforms supported 11 16-port channel adapters 37
point-to-point topology 26 4-port channel adapters 30
Port Information list 71 8-port channel adapters 33
Port pane 62 XP10000/SVS200 41
port serial numbers Set LUSE Confirmation pane 147
16-port channel adapters 37 Set SSID
4-port channel adapters 30 Install CV 164
8-port channel adapters 33 Make Volume 171
Volume Initialize 175
196
settings T
connection results 107 Target list, authentication 72
iSCSI ports 101 targets, creating iSCSI 78
iSCSI targets and connection results 116 technical support, HP 12
limitations 53 telephone support 12
SGI IRIX, finding WWNs 122 text symbols 12
slot capacity 139 troubleshooting
software, enabling 53 CVS 191
Solaris host modes 77 LUN Manager 119
speed Volume Manager 191
16-port channel adapter serial numbers 37 Tru64 host modes 77
8-port channel adapter serial numbers 33 U
Change Port Mode box 66
unregistered LUSE volumes, resetting 154
Fibre Channel ports data transfer 27, 100
user authentication
modes 27
Authentication pane 68
XP10000/SVS200 channel adapter serial numbers
Fibre Channel environments 43, 104
41
SSID
Install CV 164
V
Make Volume 171
requirements 140 VDEVs
Volume Initialize 175 parity group tree 155
standard speed mode recreating CVs 185
16-port channel adapter serial numbers 37 status 156
4-port channel adapter serial numbers 30 Volume Count list 145, 151
8-port channel adapter serial numbers 33 Volume Initialize function 130, 139, 183
applying 27, 100 Volume Initialize pane
Change Port Mode box 66 (1) 173
XP10000/SVS200 serial numbers 41 (2) 175
starting (3) 176
CVS 141 Volume Manager
LUN Manager 55, 75 concatenated parity groups, viewing 151
Volume Manager 141, 143 Concatenation List pane 149
status creating LUSE volumes with
channel adapter packages 64 LDEV Information table 153
Fibre Channel ports 56 Select an LDEV list 152
iSCSI connection 43, 103 Volume Count list 151
iSCSI ports 58 function 127
LDEVs 60, 157 installing 141
LUN icons 59 LUSE capacities, changing 153
NAS channel adapters 52 Modify mode 142
NAS ports 57 path-defined LDEVs 129
parity groups 156 permissions 150
VDEV 156 Release LUSE Confirmation pane 147
volume 157 releasing LUSE volumes 153
storage platforms, supported 11 Reset LUSE Confirmation pane 149
Subscriber’s choice, HP 12 resetting unregister LUSE volumes 154
Sun Solaris, finding WWNs 122 restrictions 128
support, technical 12 Set LUSE Confirmation pane 147
supported storage platforms and firmware 11 shortcut menu 146
switch authentication, Fibre Channel environments 47, starting 141, 143
72, 108, 110 system requirements 141
symbols in text 12 troubleshooting 191
system requirements viewing LUSE configuration 150
CVS and Volume Manager 141 Volume Manager pane 143
LUN Manager 53 volume status 157
Volume to Space Confirmation pane 158
Volume to Space function 130, 132, 180
W
web sites
HP documentation 11, 13
HP storage 13
HP Subscriber’s choice 12
Windows
server host modes 77
WWNs, finding 121
writing to control blocks 178
WWNs
Add button 61
deleting 92
finding 121
name table 59, 60
names, changing 89
WWW client computers 53
X
XP10000/SVS200, serial numbers and names 41
198

HP - LUNConfig - xp12000UG Rootsan Technologies PVT LTD

Uploaded by

Copyright:

Available Formats

HP - LUNConfig - xp12000UG Rootsan Technologies PVT LTD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP - LUNConfig - xp12000UG Rootsan Technologies PVT LTD

Uploaded by

Copyright:

Available Formats

HP StorageWorks

LUN Configuration and Security Manager XP

Part number: T1714-96008

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Part 1: LUN Configuration and Security Manager XP – LUN Manager

2 Preparing to use LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3 LUN Manager panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4 LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5 Troubleshooting LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

6 Finding an open-system host’s World Wide Name (WWN). . . . . . . . . . . . . . . . . . . . . 121

Part 2: LUN Configuration and Security Manager XP – Volume Manager

8 Preparing to use Volume Manager or Custom Volume Size. . . . . . . . . . . . . . . . . . . . . 141

9 Volume Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

10Custom Volume Size operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

11Troubleshooting Volume Manager and Custom Volume Size . . . . . . . . . . . . . . . . . . . . 191

Supported storage platforms and firmware

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

Bold text • Keys that are pressed

Italic text Text emphasis

Monospace text • File and directory names

Monospace, bold text Emphasized monospace text

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

Figure 1 Array integrating Fibre Channel, iSCSI, and NAS environments

Configuring LU paths in Fibre Channel environments

18 Overview of LUN Manager

Figure 2 LU path configuration in Fibre Channel environments

Configuring LU paths in iSCSI environments

20 Overview of LUN Manager

Figure 3 LU path configuration in iSCSI environments

Configuring LU paths in NAS environments

22 Overview of LUN Manager

Figure 4 LU path configuration in NAS environments

Configuring LUN security

Figure 5 Enabling LUN security

Figure 6 Disabling LUN security

24 Overview of LUN Manager

NOTE: You cannot use the following volumes as command devices:

Fibre Channel ports

Fibre Channel topologies

Figure 7 FC-AL and Point-to-point topologies

Fibre Channel port addresses

Table 2 Available addresses for Fibre Channel ports

Port Loop ID Port Loop ID Port Loop ID Port Loop ID

26 Overview of LUN Manager

Port Loop ID Port Loop ID Port Loop ID Port Loop ID

Data transfer speed for Fibre Channel ports

Standard, High Speed, and Initiator/External MIX modes

28 Overview of LUN Manager

Figure 8 Ports in High Speed or Initiator/External MIX mode

Table 3 Port serial numbers and names (4-port channel adapters)

1 CL3-A CL3-A [1-A 2nd] 129 CL4-A CL4-A [2-A 2nd]

8 CL1-C CL1-C 136 CL2-C CL2-C

9 CL3-C CL3-C [1-C 2nd] 137 CL4-C CL4-C [2-C 2nd]

16 CL1-E CL1-E 144 CL2-E CL2-E

17 CL3-E CL3-E [1-E 2nd] 145 CL4-E CL4-E [2-E 2nd]

24 CL1-G CL1-G 152 CL2-G CL2-G

25 CL3-G CL3-G [1-G 2nd] 153 CL4-G CL4-G [2-G 2nd]