HP XP128 Operation & User’s Manual

guide for the XP128/XP1024 Part number: T1614-96001 First edition: July 2005

© Copyright 2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Compaq Tru64 UNIX is a registered trademark or trademark of Compaq. LightPulse is a trademark of Emulex Corporation. S/390, z/OS, and AIX are registered trademarks or trademarks of International Business Machines Corporation. Microsoft, 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. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. HP-UX is a product name of Hewlett-Packard Company. Netscape Navigator is a registered trademark of Netscape Communications Corporation in the United States and other countries. AIX, FICON, ESCON, and z/OS are registered trademarks of International Business Machines Corporation. Internet Explorer, Windows 2000, and Windows NT are trademarks or registered trademarks of Microsoft Corporation. Java, Java Runtime Environment™ (JRE), Java Virtual Machine (JVM), Solaris and SPARC are trademarks or registered trademarks of Sun Microsystems, Inc. All other brand or product names are or may be registered trademarks, trademarks or service marks, and are used to identify products or services of their respective owners. LUN Configuration and Security Manager XP user guide for the XP128/XP1024

3 About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1 LUN Manager for the XP128/XP1024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 LU configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Fibre Channel environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 iSCSI environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 NAS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Supported emulation types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Configuring LU paths in a Fibre Channel environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Host storage domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Configuring LU paths in a NAS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 16-Port FC/CA CHIP product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Host modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 LUN Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 RAID Manager command devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Fibre Channel port attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Fibre Channel topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Arbitrated loop physical addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Data transfer speed for Fibre Channel ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Standard, high-speed, and high-speed (2 port) modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 iSCSI environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Configuring an iSCSI environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 iSCSI port settings and iSNS server settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Checking the status of the connection between hosts and the disk subsystem . . . . . . . . . . . . . . . . . . . . 24 User authentication (iSCSI environments only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 User authentication operations and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Host authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Port authentication (performing mutual authentication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 LUN Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Starting LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 LUN Manager main pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 LU Path tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Fibre Channel folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 NAS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 iSCSI folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 LU Path table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 WWN or iSCSI name table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 LDEV table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Defining LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Creating host groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Registering hosts in host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Associating host groups to logical volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Contents

Deleting LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Changing the name and host mode of a host group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Deleting host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Initializing the host group 0 (zero) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Changing WWNs, iSCSI names, and nicknames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Deleting HBAs from host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Deleting unneeded WWNs from the WWN table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Viewing a list of concatenated parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Defining alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Copying paths from one Fibre Channel or iSCSI port to another. . . . . . . . . . . . . . . . . . . . . . . . . . 41 Copying paths from one NAS port to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Copying paths from a Fibre Channel or iSCSI port to a NAS port. . . . . . . . . . . . . . . . . . . . . . . . . 42 Copying paths from a NAS port to a Fibre Channel or iSCSI port. . . . . . . . . . . . . . . . . . . . . . . . . 42 Viewing alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Deleting WWNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Applying and removing LUN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Creating RAID Manager Command Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Setting an LU as a command device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Stopping the use of an LU as a command device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Applying command device security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Removing command device security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Port Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Starting Port Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Port tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Package tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Port table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 iSCSI Function box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Change Port Mode box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Setting the Fibre Channel Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Setting Fibre Channel Port Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Setting the Data Transfer Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Switching to standard, high-speed, or high-speed (2 port) mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Configuring iSCSI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Making settings on iSCSI ports and iSNS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Removing information about an iSCSI port from an iSNS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Checking the status of connection between hosts and the disk array (iSCSI environment only) . . . . . . . . . . 48 Issuing a ping command from an iSCSI port to a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Setting user authentication (iSCSI environments only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Starting User Authentication Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 User Authentication tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Port tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 User Information (Host) table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 User Information (Port) table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Specifying whether to enable or disable host authentication on a port . . . . . . . . . . . . . . . . . . . . . . . . 50 Registering user information of hosts on a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Changing user information of hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Deleting user information of hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Specifying user information of ports (when performing mutual authentication) . . . . . . . . . . . . . . . . . . . 52 Clearing user information of ports (when performing mutual authentication) . . . . . . . . . . . . . . . . . . . . 53 Relationship between port settings and connection results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Operational restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Restrictions on LUN Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Restrictions on port operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2 Volume Management for the XP128/XP1024. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Volume Management (LU Size Expansion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Drawbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5 LUSE rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 LUSE operations that handle a path-defined LDEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Volume Size Configuration (VSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 VSC operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Parity group configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Volume to Space operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Install Custom Volume (CV) operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Volume Initialize and Make Volume operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 LUSE operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Starting LUSE operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Volume Management pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 LDEV Information tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 LDEV Information table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Select an LDEV list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Volume Count list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Free LDEVs table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Expanded LDEVs list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Viewing LUSE configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Viewing concatenated parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Creating a LUSE volume using the Volume Count list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Creating a LUSE volume using the Select an LDEV list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating a LUSE volume using the LDEV information table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Releasing a LUSE volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Changing LUSE capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Resetting an unregistered LUSE volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 VSC Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Starting VSC operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Customized volume pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Parity Group - LDEV tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Parity Group - LDEV table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Capacity unit list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Viewing VSC configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Viewing concatenated parity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Converting volumes to space (Volume to Space) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Creating custom volumes (Install CV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Deleting custom volumes (Volume to Space) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Creating initial custom volumes for OPEN-V (Make Volume) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Initializing custom volumes for other than OPEN-V (Volume Initialize) . . . . . . . . . . . . . . . . . . . . . . . . . 84 Formatting LDEVs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Formatting all blocked volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Operational restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Restrictions on VSC and LUSE operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Figures 1 LU paths configuration in a Fibre Channel environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2 LU paths configuration in a NAS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3 16-Port CHIP pair labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 Host group example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5 Host group example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6 Host group example 3 (LUN security) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7 Differences between high-speed and high-speed (2 port) modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8 Flow of port authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 9 Overview of user authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

11 NAS folder in LU path tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 12 iSCSI folder in LU path tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 13 WWN and iSCSI name tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 14 Add New Host Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 15 Add New WWN dialog box (Fibre Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 16 Add New iSCSI Name dialog box (iSCSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 17 Add New WWN dialog box (when registering a host that has previously been connected to the disk array). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 18 Add New iSCSI Name dialog box (when registering a host that has previously been connected to the disk array) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 19 Change Host Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 20 Change WWN & Nickname dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 21 Change iSCSI Name & Nickname dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 22 Check WWNs / Check iSCSI names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 23 Port pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 24 User Authentication tab (LUN Manager pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 25 Add New User Information dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 26 Change User Information (Host) dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 27 Specify User Information (Port) dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 28 LUSE configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 29 VSC process (all supported emulation types except for OPEN-V) . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 30 VSC process (OPEN-V). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 31 Parity group configuration for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 32 Virtual VSC volume configuration for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 33 Volume Management pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 34 Customized Volume pane (Volume Management screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 35 Install CV pane (1) for OPEN-V (when two or more free spaces are available) . . . . . . . . . . . . . . . . . 73 36 Install CV pane (1) for other than OPEN-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 37 Install CV pane (1) for OPEN-V after clicking Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 38 Install CV pane (1) for other than OPEN-V after clicking Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 39 Install CV pane (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 40 Select an LDEV number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 41 Setting the SSID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 42 Customized volume screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 43 Make Volume pane (1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 44 Make Volume pane (1) after clicking Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 45 Make Volume pane (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 46 Select an LDEV number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 47 Volume Initialize pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 48 Select an LDEV number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Tables 1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2 Host modes for host operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3 AL-PA and loop IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4 LUN Manager tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5 Fibre Channel port icons for LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6 NAS port icons for LUN Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7 iSCSI port icons for LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 8 LUN icons for LUN Manager operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 9 LDEV icons for LUN Manager operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10 Host mode options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 11 Copying LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 12 Channel adapter package icons for Port operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 13 iSCSI port icons for User Authentication operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 14 Combinations of iSCSI port settings and connection results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 15 LUN Manager operation restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 16 Port operation restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7 17 Creating VSC volumes by Install CV (for OPEN-V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 18 VSC supported emulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 19 Install Custom Volume operation parameters for mainframe and open system volumes . . . . . . . . . . . . . 62 20 Capacities of open system custom volume sizes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 21 Settings for the Make Volume operation (OPEN-V only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 22 LDEV status icons for LUSE operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 23 Parity group status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 24 VDEV status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 25 LDEV status icons for VSC operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 26 Volume status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 27 VSC and LUSE operation restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

9 About this guide This guide provides information about: • ”LUN Manager for the XP128/XP1024” on page 13 • ”LU configuration overview” on page 13” • ”Supported emulation types” on page 13 • ”LU paths” on page 13 • ”Configuring LU paths in a Fibre Channel environment” on page 14 • ”Configuring LU paths in a NAS environment” on page 15 • ”16-Port FC/CA CHIP product” on page 16 • ”Host groups” on page 17 • ”Host modes” on page 18 • ”LUN Security” on page 19 • ”RAID Manager command devices” on page 20 • ”Fibre Channel port attributes” on page 20 • ”iSCSI environments” on page 23 • ”LUN Manager operations” on page 28 • ”Port Operations” on page 44 • ”Making settings on iSCSI ports and iSNS servers” on page 47 • ”Checking the status of connection between hosts and the disk array (iSCSI environment only)” on page 48 • ”Setting user authentication (iSCSI environments only)” on page 48 • ”Operational restrictions” on page 54 • ”Volume Management for the XP128/XP1024” on page 57 • ”Volume Management (LU Size Expansion)” on page 57 • ”Volume Size Configuration (VSC)” on page 58 • ”LUSE operations” on page 64 • ”VSC Operations” on page 69 • ”Operational restrictions” on page 88 Intended audience This guide is intended for customers and HP authorized service providers experienced with the following: • Disk array hardware and software • Storage systems Prerequisites Prerequisites for using this product include: • XP1024/XP128 firmware version • Minimum: 21-10-10 • Recommended: 21-14-02 or later • Set up the HP StorageWorks XP disk arrays • See the readme.txt file on the product CD for last-minute announcements

• HP StorageWorks Command View XP User Guide for XP Disk Arrays • HP StorageWorks XP Remote Web Console User Guide for XP1024/XP128 • HP StorageWorks XP Disk/Cache Partition User Guide These and other HP documents can be found on an HP web site: http://www.hp.com/support/. Document conventions and symbols 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 web site: http://www.hp.com/support/. Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers Table 1 Document conventions Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.com) Web site addresses Bold font • Key names • Text typed into a GUI element, such as into a box • GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes Italics font Text emphasis Monospace font • File and directory names • System output • Code • Text typed at the command-line Monospace, italic font • Code variables • Command-line variables Monospace, bold font Emphasis of file and directory names, system output, code, and text typed at the command-line

11 • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored. HP strongly recommends that customers sign-up online using the Subscriber’s choice web site at http://www.hp.com/go/e-updates. • Subscribing to this service provides you with email updates on the latest product enhancements, newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources. • After signing-up, you can quickly locate your products by selecting Business support and then Storage under Product Category. HP-authorized reseller For the name of your nearest HP-authorized reseller: • In the United States, call 1-800-345-1518 • Elsewhere, visit http://www.hp.com and click Contact HP to find locations and telephone numbers Helpful web sites For third-party product information, see the following vendor web sites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/support

13 1 LUN Manager for the XP128/XP1024 You can connect XP arrays to open system and mainframe hosts using iSCSI (Internet Small Computer System Interface), Fibre Channel, and Network Attached Storage (NAS). Use LUN Manager to configure host groups, logical units (LUs), and Fibre Channel and NAS ports. You can also configure NAS cache settings. LU configuration overview One of the important tasks in logical unit (LU) configuration is to define I/O paths from hosts to LUs. After the paths are defined, the hosts can send commands and data to the LUs and can receive data from them. LUN Manager can also configure security policies to protect LUs from unauthorized access. Fibre Channel environment In a Fibre Channel environment, you must configure the Fibre Channel ports on the disk array. With LUN Manager, you can set addresses and speed, and specify topology for Fibre Channel ports. iSCSI environment In an iSCSI environment, the XP disk array provides mutual user authentication between hosts and ports by using Challenge Handshake Authentication Protocol (CHAP). NAS environment There are two types of LUs in a NAS environment: • System LUs • User LUs When configuring a NAS system, you must define paths between hosts and user LUs. You cannot define paths to system LUs, and you cannot define any LU paths to external volumes. Supported emulation types LUN Manager supports the following device emulation types: • OPEN-3, OPEN-9, OPEN-8 (XP128/XP1024 only), OPEN-E, OPEN-L, and OPEN-V for open systems • 3390-3A/B/C and 3380-KA/B/C for mainframe systems LU paths After hosts and the disk array are physically connected by cables, switches, and so on, use LUN Manager to establish paths between the hosts and LUs. These paths are called LU paths and they determine which host can access which LU. • Up to 256 LU paths can be defined for a host group in a Fibre Channel or iSCSI environment • Up to 512 LU paths can be defined for a Fibre Channel port for the XP128/XP1024 arrays • Up to 256 LU paths can be defined for a NAS port • Up to 128 host groups can be defined for a Fibre Channel port for the XP128/XP1024 arrays • In an iSCSI environment, you can define: • Up to 16 initiators per port • Up to 16 host groups per port • Up to 16 initiators per host group NOTE: In an iSCSI environment, the number of initiators per host group multiplied by the number of host groups must be less than or equal to 16. • Up to 65,536 host groups can be defined for one disk array (256 x 256)

• Up to 255 hosts can be included in all the host groups for one Fibre Channel port • Up to 16 hosts can be included in all the host groups for one iSCSI port Configuring LU paths in a Fibre Channel environment Before defining LU paths, you must classify server hosts by host storage domains. For example, if Linux and Windows® hosts are connected to the disk array, you must create a separate host storage domain for each host type. When this is done, register the host bus adapters for each host type in the appropriate host storage domain. Host storage domains A host storage domain can contain only hosts that are connected to the same port and cannot contain hosts that are 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 storage domain. You must register the first two Windows hosts in one host storage domain and the remaining three Windows hosts in another host storage domain. After server hosts are classified into host storage domains, you must associate host storage domains to logical volumes. In Figure 1, the host storage domain hg-lnx is associated with the logical volumes 00:00, 00:01, and 00:02. LU paths are defined between the two hosts in the hg-lnx group and the three logical volumes. Figure 1 LU paths configuration in a Fibre Channel environment LUN Manager lets you define paths between a single server host and multiple LUs. In Figure 1, both hosts in the hg-lnx host storage domain can access the three available LUs. LUN Manager lets you define paths between multiple server hosts and a single LU. In Figure 1, the LU identified as CU-LDEV 00:00 is accessible to the two hosts in the hg-lnx host storage domain. Port Host Storage Domain Host Groups

15 In Figure 1, the LUs associated with the hg-lnx domain are addressed by numbers 0 to 2. The address number of an LU is referred to as the logical unit number (LUN). When HP StorageWorks Continuous Access XP and other optional features manipulate LUs, they use LUNs to specify the LUs to be manipulated. You can add, change, and delete LU paths when the system is operational. For example, if new disks or server hosts are added to your disk array, you can add new LU paths. If an existing server host is to be replaced, you can delete the corresponding LU paths before replacing the host. You do not need to restart the system when you add, change, and delete LU paths. If a hardware failure (such as a CHA failure) occurs, there is a chance that some LU paths are disabled and some I/O operations are stopped. To avoid this, the system administrator can define alternate LU paths. If one LU path fails, the alternate path takes over the host I/O. In a Fibre Channel environment, up to 1,024 LU paths can be defined for one host storage domain. Up to 1,024 LU paths can be defined for one port. NOTE: You cannot define an LU path to LUN On Demand volumes or volumes reserved by Auto LUN XP. • Up to 256 host storage domains can be created for one Fibre Channel port. Up to 57,344 host storage domains can be created for one disk subsystem. The maximum number of ports per subsystem is 224. • Up to 255 host groups can be created for one Fibre Channel port. Configuring LU paths in a NAS environment In a Fibre Channel or iSCSI environment, hosts are classified into platform-based host groups (host storage domains). This is not required in a NAS environment. Hosts attached to a NAS port are registered automatically in a host group (host storage domain) called User. In a NAS environment, LUs are classified into system LUs and user LUs. System LUs contain system information necessary for managing the NAS environment and can only be manipulated by your HP account support representative. User LUs contain data that can be accessed by ordinary network users. When configuring a NAS system, you need to define paths between hosts and user LUs. Figure 2 shows an example of defined paths between hosts and user LUs. In a NAS environment, paths are always defined between a user LU and a group of four ports. In Figure 2, two paths are defined to the user

LU 00:00 (LUN 00). One path comes from the CL1-N port and the other path comes from the CL1-Q port. Thanks to this two path configuration, hosts can access the user LU even if one of the paths fails. Figure 2 LU paths configuration in a NAS environment Notes: • In a NAS environment, up to 256 LU paths can be defined for one NAS port. • In a NAS environment, you cannot define LU paths to logical volumes unless they have the Read/Write access attribute. • The LUN Manager pane displays two host groups (User and NAS-Sys) below each NAS port. When you define LU paths, you can use only the User host group; you cannot use the NAS-Sys host group. 16-Port FC/CA CHIP product Although there is not a significant performance gain compared to the 8-port FC/CA CHIP product, the primary advantage of the 16-port FC/CA CHIP product is its increased FC connectivity (or port count). High-speed mode is currently unavailable on the 16-port FC/CA CHIP product. Odd/even LUN data path handling through the processor does not exist on the XP128/XP1024. There is no odd/even LUN mapping issue associated with this product. Each processor of the 16-port CHIP product handles the data flow of two ports (eight total processors for 16 total ports = two ports per processor). For load balancing, the two ports serviced by a processor should be considered as one port. Although volumes can be mapped to both ports handled by a processor, the I/O will go through one processor. For redundancy and performance reasons, consider distributing the load across multiple CHIPs. When deciding whether to map volumes to ports (LUN mapping) for host connectivity, after considering load balancing across processors, there is no reason to not use all 16 ports immediately. After considering

17 load balancing among processors, there is no reason not to use both ports in the I/O path of one processor or to use both ports in the I/O path of a processor. Figure 3 16-Port CHIP pair labeling Port numbering is as follows: Cluster 1 uses CL1-* and CL3-*, while Cluster 2 uses CL2-* and CL4-*, where * is an alphabetical character designation of the port such as A, B, C, and so on. Ports A, for example, CL1-A and CL3-A, share the same processor for I/O purposes. Host groups Begin by grouping server hosts into host groups. For example, if HP-UX® and Windows hosts are connected to the disk array, you must create a separate host group for each host type. When this is done, register the hosts in their corresponding host groups. After hosts are classified into host groups, associate the host groups with LUs. In Figure 4, the host group hpux01 is associated with six LUs. LU paths are defined between the three hosts in the hpux01 group (WWN_1, WWN_2, WWN_3) and the six logical units LUN00-LUN05. Figure 4 Host group example 1

Figure 5 Host group example 2 LUN Manager can define paths between a single host and multiple LUs. In Figure 5, each of the three hosts in the host group hpux01 can access the six LUs. LUN Manager can also define paths between multiple hosts and a single LU. Hosts can be members of only one host group for a given port. Host group definitions and members apply only to the port that they are defined for. Host modes As part of registering hosts in host groups, you will be asked for the host mode. Use Table 2 to determine the host mode. Table 2 Host modes for host operating systems Host mode Host operating system 00 Red Hat Linux, IRIX, or Windows1 (Standard) 01 - 03 Reserve 04 DYNIX/ptx (Sequent) 05 OpenVMS 06 Reserve 07 Tru64 08 HP-UX or Windows2 09 Solaris® 0A NetWare® 0B Reserve 0C Windows 3, 4 0D, 0E Reserve 0F AIX® 10 - 19 Reserve

19 LUN Security To protect data from unauthorized access, apply security policies to LUNs. LUN Manager can apply LUN security to ports to safeguard LUs. If a port has the External attribute, you cannot apply LUN security to the port. NOTE: You cannot apply LUN security to NAS ports. If LUN security is applied, it limits which host can access which LUs. A host can only access LUs associated with its host group. Hosts cannot access LUs associated with other host groups. In Figure 6, the hosts in the hpux-G01 group can access LUN0 and LUN1 associated with the same host group, but cannot access LUN0 and LUN1 in the winG02 host group. The hosts in hpuxG01 can only access the two LUs, identified by 01:05 and 02:01; the hosts cannot access the LUs 02:00 and 02:02. Figure 6 Host group example 3 (LUN security) 1A - 1F Reserve 20 - 29 Reserve 2A, 2B Reserve 2C Windows Extension 3, 4 2D - 2F Reserve 29 Solaris5 1. For Windows with any FC HBAs when MSCS is not needed. 2. For Windows with D8602 FC HBAs with or without MSCS. 3. For Windows with Emulex or QLogic FC HBAs with or without MSCS. 4. If you register Windows server hosts in a host group, verify that the host mode of the host group is 0C: Windows or 2C: Windows Extension. If you are thinking about creating LUSE volumes, such as expanded LUs, consider setting the host mode 2C: Windows Extension to the host group. If the host mode is 0C: Windows and an LU path is defined for a volume, you cannot execute LUSE operations on the volume without unmapping the volume first. 5. When registering Sun Cluster server hosts in the host group (Use this host mode both VERITAS Cluster Server and Sun Cluster are used). Table 2 Host modes for host operating systems (continued) Host mode Host operating system

If LUN security is disabled, the hosts will not be able to access most of the LUs. Hosts will have access to only those LUs defined in host group 0. By default, LUN security is disabled on a port, so host group 0 is the only accessible host group reserved for the port. Initially it contains no LUs or WWNs. When security is disabled, only LUs defined in host group 0 are accessible to hosts connected to the port, regardless of any WWNs that may be defined for a host group. After security is enabled, WWNs are used, permitting or restricting access based on WWN. If you have more than one host group defined on a port, you can locate host group 0 by disabling LUN security from the port. When done, the tree display will “gray” out all host groups except host group 0. RAID Manager command devices To use RAID Manager commands for Business Copy XP and Continuous Access XP operations, you must designate at least one LDEV on the disk array as a command device. A command device receives RAID Manager commands entered from hosts. When you enter a RAID Manager command from a host, the command is transferred to the target device via the command device. If you want to restrict access to LUs and by RAID Manager, you can apply command device security in LUN Manager. Restrictions You cannot use the following LDEVs as command devices: • Volumes that do not have read/write access • Volumes reserved by Auto LUN XP • Continuous Access XP volumes • BC volumes • External LUs • iSCSI volumes (volumes to which paths are defined from iSCSI ports) • Flex Copy XP volumes You cannot use an LDEV as a command device if a path is defined between an iSCSI port and the LDEV. If you want to use a LUSE volume as a command device, you must specify only the first LU as the command device. Fibre Channel port attributes In Fibre Channel environments, you must configure the Fibre Channel topology and set addresses for the Fibre Channel ports. You can enhance system performance by adjusting the data transfer speed at the Fibre Channel ports and changing the channel adapter mode. Fibre Channel topologies Fibre Channel provides the following topologies: • Fabric: Uses a fabric switch to connect a large number of devices. Each device has the full bandwidth of 100 MB/sec. • FC-AL (Fibre Channel-Arbitrated Loop): A shared-bandwidth topology that can connect up to 126 devices (AL ports). • Point-to-point: A simple Fibre Channel topology in which two devices are connected directly. When configuring the disk array, use LUN Manager to specify whether the hosts and the disk array are connected by a fabric switch. Also, you must specify FC-AL or point-to-point in the LUN Manager pane. The default is FC-AL. If you are using a fabric switch, consult the switch’s documentation to learn whether FC-AL or point-to-point should be used. Some fabric switches require that you specify point-to-point to get the system running.

21 Arbitrated loop physical addresses You will need to set addresses for Fibre Channel ports. When addressing Fibre Channel ports, you can use AL-PA (arbitrated loop physical address) or loop IDs as the addresses (see Table 3). Table 3 AL-PA and loop IDs AL-PA Loop ID AL-PA Loop ID AL-PA Loop ID AL-PA Loop ID 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 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 disk array operation continues, you may notice that a larger amount of data is transferred at some ports and a smaller amount is transferred at other ports. To improve system performance, set a faster data transfer speed for ports where a larger amount of data is transferred, and a slower data transfer speed for ports where a smaller amount of data is transferred. Standard, high-speed, and high-speed (2 port) modes The channel adapter boards can operate in standard, high-speed, or high-speed (2-port) mode. Standard mode is the default. If a channel adapter board satisfies certain conditions, you can set it to high-speed or high-speed (2 port) mode to improve port performance. NOTE: High-speed (2 port) mode is available only if firmware version 21.06.22 or later is installed on the disk array. High-speed mode can be applied to channel adapter boards that satisfy the following conditions: • Only one port is planned for use. • All ports take the same Fibre topology option (on or off). • All ports take FC-AL as the Connection option. • All ports use different port addresses and no matching addresses. • All ports take the same port attribute (Initiator, RCU target, or Target). If high-speed mode is applied to a channel adapter board, only one of the ports on the channel adapter board can be used. This port can exclusively use channel processors and fibre optic processors (FOPs) that would otherwise be reserved for the other ports. Balancing the workload on the processors can improve system performance. If high-speed (2 port) mode is applied to a four-port channel adapter board, two ports out of the four ports cannot be used. The remaining two ports can exclusively use channel processors and FOPs that would otherwise be reserved for the other two ports. Figure 7 Differences between high-speed and high-speed (2 port) modes Before changing the configuration of a port that is being used, perform a backup operation. You cannot switch between standard and high-speed while you are online to the hosts.

23 iSCSI environments iSCSI (Internet Small Computer System Interface) is a protocol that enables data transfers between host computers and large-scale storage devices over an IP (Internet Protocol) network. If you want to use the disk array as an IP storage device, host servers should be attached to disk array’s iSCSI ports. iSCSI environments that can be created with LUN Manager support local connections (that is, hosts in the same domain can communicate with each other), but do not support inter-domain connections or external LAN connections. Configuring an iSCSI environment When configuring an iSCSI environment: • Confirm what operating systems are used to run hosts in your IP network. To configure an iSCSI network, each of the hosts must run under the Windows Server 2003, Windows 2000®, or HP-UX 11i operating system. However, user authentication is not available on hosts running under HP-UX 11i. • You can set ports to perform user authentication. The ports use CHAP (Challenge Handshake Authentication Protocol) as the authentication method. • Switching hubs can be connected to iSCSI ports, but other network relay devices cannot be connected to iSCSI ports. iSCSI port settings and iSNS server settings You must configure iSCSI ports and iSNS servers, if necessary, when configuring an iSCSI environment. Specify the following items when configuring an iSCSI environment. (See ”Configuring iSCSI Ports” on page 47). • IP: (Mandatory). The IP addresses of iSCSI ports. In LUN Manager, the default value of an iSCSI port IP address is 192.168.0.xxx, where xxx is the location of the iSCSI port. • Subnet mask: (Mandatory). The subnet mask is the value that is used to obtain a network address from an IP address. In LUN Manager, the default subnet mask is 255.255.255.0. • Gateway address: (Mandatory if a gateway is used). A gateway is hardware that connects networks of different protocols. • iSCSI name: (Mandatory). You must assign iSCSI names to iSCSI ports. iSCSI names are used to uniquely identify each iSCSI node. iSCSI nodes are devices that use the iSCSI protocol for communication, such as iSCSI ports in the disk array, host bus adapters in host servers, and switching hubs for network relaying. iSCSI names must be specified in one of the following formats: • eui format: An IEEE 64-bit Extended Unique Identifier is used to specify the iSCSI name. The iSCSI name begins with eui., which is followed by a WWN (world wide name) of an iSCSI port. If a host is connected to an iSCSI port, LUN Manager automatically displays the iSCSI name in eui format. Example: EUI.02004567A425678D • iqn format: The iSCSI Qualified Name format is used to specify an iSCSI name. For information on specifying iSCSI names in this format, refer to iSCSI-related documentation. Example: iqn.2003.09.com.hp:iscsi-r450:model-xxx:sn-xxxxxx:lun00 The length of an iSCSI name must be exactly 20 characters in eui format, and up to 223 characters in iqn format. iSCSI names can include letters, numbers, periods (.), hyphens (-), and colons (:), but they cannot include double-byte characters. iSCSI names are not case-sensitive. • iSCSI alias: (Optional). An iSCSI alias is a nickname you can assign to an iSCSI name. iSCSI aliases are helpful for managing and identifying iSCSI ports. It can be difficult to identify iSCSI ports by iSCSI names because an iSCSI name contains many characters and can be difficult to remember. Assigning a short, easy-to-remember iSCSI alias allows you to identify iSCSI ports easily and quickly.

An iSCSI alias can contain up to 32 characters. iSCSI aliases can include letters, numbers, periods (.), hyphens (-), and colons (:), and cannot include double-byte characters. iSCSI aliases are case sensitive; for example, MyPort and myport are different iSCSI aliases. • Port number: (Mandatory). LUN Manager allows you to specify a port number as an integer from 1 to 65535. The initial value of a port number is 3260. • Keep-alive timer: (Mandatory). This 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 disk array checks whether a communication packet was sent between an iSCSI port and another iSCSI node (such as a host bus adapter or a switching hub) every 60 seconds. You can specify a value from 0 to 64800 seconds. The initial value for the keep-alive timer is 60 seconds. • Whether to register iSCSI ports in iSNS servers: The iSNS server is a server computer on which an Internet Storage Name Service (iSNS) service is installed. This server is used to manage IP addresses and iSCSI names of iSCSI ports. Using iSNS servers is optional. If iSNS servers are configured and used, iSCSI ports are easily discovered and managed. NOTE: For detailed information about configuring iSNS servers, see the iSNS-related documentation. • IP address of iSNS server: To use an iSNS server, specify the IP address of the iSNS server. • TCP port number of iSNS server: To use an iSNS server, specify a TCP port number of the iSNS server. 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 iSNS server. Checking the status of the connection between hosts and the disk subsystem Use LUN Manager to issue a ping command from an XP128/XP1024 iSCSI port to a host. The ping command checks whether the host and the XP128/XP1024 can communicate with each other. If the host responds to the ping command, the host and the XP128/XP1024 can communicate with each other. See ”Checking the status of connection between hosts and the disk array (iSCSI environment only)” on page 48. User authentication (iSCSI environments only) When configuring an iSCSI environment, you can use LUN Manager to set ports of the disk array to authenticate hosts. In an iSCSI environment, the ports use CHAP as the authentication method. User authentication operations and settings User authentication involves two phases: 1. Host authentication: A disk array port authenticates a host when it attempts to connect to the array 2. Port authentication: The host authenticates the connection-target port of the disk array The disk array performs user authentication by ports. Therefore, the ports and hosts need to have their own user information in order to perform user authentication. When a host attempts to connect to the disk array, the host authentication phase starts. In this phase, the array determines whether the port requires host authentication. If the port does not require host authentication, the host will connect to the disk array without authentication; otherwise authentication is performed for the host. When the host is authenticated successfully, the next phase begins. This port authentication phase starts if the host requires user authentication for the connection target port. Thus the ports and hosts perform mutual authentication. If the host does not require user authentication for the port, the host will connect to the disk array without port authentication. The following section explains the required settings for user authentication. Port authentication settings are needed only if you want to perform mutual authentication.

25 • Host authentication settings • On the disk array: Use LUN Manager to specify whether to perform host authentication on each port. On a port that performs authentication, register the user information (iSCSI name, user name, and secret) for the hosts that are allowed to connect to the port. NOTE: A secret is a password used in CHAP authentication. When registering user information, you can also specify whether to enable or disable host authentication. For details, see ”Specifying whether to enable or disable host authentication on a port” on page 50 and ”Registering user information of hosts on a port” on page 50. • On hosts: Configure the operating system and iSCSI driver for port authentication using CHAP. Specify the user name and secret of the host used for CHAP. For details, refer to your operating system and iSCSI driver documentation. • Port authentication settings (required for mutual authentication) • On the disk array: Use LUN Manager to specify user information (user name and secret) of each port. For details, see ”Specifying user information of ports (when performing mutual authentication)” on page 52. • On hosts: Configure the operating system and iSCSI driver for CHAP port authentication. Specify the user name and secret of the port that is the connection target. For details, refer to your operating system and iSCSI driver documentation. Host authentication When a host attempts to connect to the disk array, the connection results of the host’s authentication depend on the port settings. Figure 8 illustrates the relationship between port settings and the connection results. Figure 8 Flow of port authentication

Each case in Figure 8 is explained below. • When connecting via a port that performs host authentication: • If the user information of the host is registered on the port and host authentication is enabled (Case A): The port authenticates the user information sent from the host. If the host authentication is successful, then: If the host is configured for mutual authentication, processing continues with port authentication. If the host is not configured for port authentication using CHAP, the authentication fails and the host cannot connect to the disk array. If the host is not configured for mutual authentication, the host connects to the disk array. • If the user information of the host is registered on the port but host authentication is disabled (Case B): The port does not perform host authentication. Irrespective of whether the host is configured for port authentication using CHAP, the host connects to the disk array. CAUTION: If a host uses Microsoft iSCSI Initiator and is configured for port authentication using CHAP, host authentication will fail. To allow such a host to connect to the port without authentication, do not configure it for port authentication using CHAP. • If the user information of the host is not registered on the port (Case C): Irrespective of the setting on the host, the port performs host authentication and it fails. The host cannot connect to the disk array. • When connecting via a port that does not perform host authentication (Case D): The host can connect to the disk array without host authentication irrespective of whether the host is configured for port authentication using CHAP. In this case, registering the user information of the host on the port is not required. CAUTION: If a host uses Microsoft iSCSI Initiator and is configured for port authentication using CHAP, host authentication will fail. To allow such a host to connect to the port without authentication, do not configure it for port authentication using CHAP. NOTE: You must register user information of all the hosts to be connected to a port on which host authentication is performed. If you want to allow a specific host to connect to a port without authentication, configure the port and the host as follows: • On the port: Register the user information of the host you want to allow to connect without authentication, then clear the Enable authentication check box. • On the host: It does not matter whether you configure the host for port authentication using CHAP. If the host uses Microsoft iSCSI Initiator, do not configure the host for port authentication using CHAP.

27 Figure 9 provides an overview of user authentication. In this figure, iSCSI names of host bus adapters (HBAs) are abbreviated as a, b, and so on. Figure 9 Overview of user authentication In this example, port 1 performs host authentication while port 2 does not. The user information of Host A is registered on port 1, and the authentication setting is enabled. If the host authentication is successful, Host A can connect to the disk array (or the processing continues with port authentication). In order for host authentication to succeed, Host A must be configured for port authentication using CHAP. The user information of Host B is also registered on port 1, but the authentication setting is disabled, and Host B can connect to the disk array without authentication. If Host B uses Microsoft iSCSI Initiator, it can connect to the disk array only when Host B is not configured for port authentication using CHAP. The user information of Host C is not registered on port 1. When Host C tries to connect to the disk array, authentication fails and the connection request is denied. Host D is attached to port 2, which does not authenticate hosts, so Host D can connect to the disk array without authentication. In this case, it does not matter whether the user information of Host D is registered on port 2. If Host D uses Microsoft iSCSI Initiator, Host D can connect to the disk array only when Host D is not configured for port authentication using CHAP. For more information about port settings, see ”Specifying whether to enable or disable host authentication on a port” on page 50 and ”Registering user information of hosts on a port” on page 50. For host configuration details, refer to your operating system and iSCSI driver documentation. Port authentication (performing mutual authentication) When host authentication is successful, the host performs port authentication if required (mutual authentication). During port authentication, if the user information specified on the port side matches the information on the host, the host allows the port to connect.

For more information about port authentication settings, see ”Specifying user information of ports (when performing mutual authentication)” on page 52. For details on how to configure a host, refer to your operating system and iSCSI driver documentation. LUN Manager operations This section includes procedures for performing the most common LUN Manager operations. Starting LUN Manager 1. Click LUN Manager in the left pane. The LUN Manager pane appears. S Figure 10 LUN Manager main pane LUN Manager main pane The LUN Manager main pane contains the tabs listed in Table 4. LU Path tree The LU Path tree on the upper left of the LUN Manager tab lists the Fibre Channel and NAS ports in the disk array and hosts connected to them. Hosts are identified by nicknames and WWNs and are classified by host groups. The LU Path tree may contain different folders: Fibre Channel, NAS, iSCSI, and so on. Table 4 LUN Manager tabs Tab Use this tab to... LUN Manager Define LU paths and apply LUN security for logical volumes. Port Configure ports by setting the topology and port addresses (”Starting Port Operations” on page 44). User Authentication Enable or disable authentication settings and register user information on hosts and ports (”User Authentication tab” on page 49).

29 Fibre Channel folder The following Fibre Channel port icons are used in the LU Path tree: NOTE: High-speed (2 port) mode is available only if the XP disk array has firmware version 21.06.22 or later installed. NAS folder Figure 11 NAS folder in LU path tree In a NAS environment, if you double-click the NAS folder, NAS ports in the disk array appear as icons. Two port names appear to the right of each icon, followed by the channel adapter name in parentheses. NOTE: The NAS folder appears only if the disk array contains one or more NAS channel adapters. The following are the NAS port icons used in the LU Path tree: Table 5 Fibre Channel port icons for LUN Manager operations Icon Status A short-wave port in standard mode without LUN security A short-wave port in standard mode with LUN security A long-wave port in standard mode without LUN security A long-wave port in standard mode with LUN security A short-wave port in high-speed mode without LUN security A short-wave port in high-speed mode with LUN security A long-wave port in high-speed mode without LUN security A long-wave port in high-speed mode with LUN security Table 6 NAS port icons for LUN Manager operations Icon Status Indicates that you can assign paths from this NAS port to logical volumes Represents a short-wave port in standard mode with LUN security

When you double-click a NAS port, the following host groups appear: • NAS-Sys • If you select NAS-Sys, the table on the right displays information about paths to system LUs. The table contents are dimmed and cannot be changed. • This host group number is 00. • User • If you select User, the table on the right displays information about paths to user LUs. • This host group number is 01. iSCSI folder Figure 12 iSCSI folder in LU path tree When you double-click the iSCSI folder, iSCSI ports in the disk array appear as icons. The port name and port attribute appear to the right of each icon. NOTE: • The iSCSI folder is available if the disk array has an iSCSI channel adapter • iSCSI ports always have the Target attribute The following iSCSI port icons are used in the LU Path tree: • When you double-click an iSCSI port in the tree, a list of host groups appears represented by the following icon: . The host group number, host group name, and host mode appear to the right of the icon. For more information about host modes, see Table 2. • When you double-click a host group in the tree, a list of host bus adapters appears represented by the following icon: . The nickname and the iSCSI name of the host bus adapter appear to the right of this icon. NOTE: Host bus adapters are adapters in host computers and are used as ports for connecting hosts and the disk array. • When you double-click a port to which LUN security is not applied, the host groups except for the first group (host group 0) are dimmed. If you double-click a dimmed host group, the contents of the LU Path table (”LU Path table” on page 31) are dimmed. Table 7 iSCSI port icons for LUN Manager operations Icon Meaning LUN security is not applied to the port. LUN security is applied to the port.

31 LU Path table On the right side of the LU Path tree is a table that displays LU Path information about the hosts in the tree. The table contains the following information: • LUN: LUNs (address numbers) assigned to LUs, which are LDEVs that can be accessed by hosts. If no paths are defined, the other table columns are blank. The following icons indicate status. • CU:LDEV: The CU image and LDEV numbers. If an LDEV number ends with the sharp symbol (#), the logical volume is an external LU. • Emulation: Emulation type for each LDEV • Capacity: Size of each LDEV • RAID: RAID level for each LDEV. If the logical volume is an external LU, the RAID column displays a hyphen (-) instead of a RAID level. • Array Group: Names of the array groups. If an array group name begins with the letter E, the group includes one or more Flex Copy XP LDEVs. • Paths: Number of alternate paths, if any • Access Attribute: Access attribute of each LDEV • Ex-Dev. Info: The array where the LDEVs exist. WWN or iSCSI name table Figure 13 WWN and iSCSI name tables The lower-left corner of the LUN Manager tab displays the WWN or iSCSI Name table. If you selected a Fibre Channel port in the LU Path tree, the WWN table appears. If you selected an iSCSI port, the iSCSI Name table appears. The WWN table lists host bus adapters that are connected to Fibre Channel ports on the disk array and the iSCSI Name table lists host bus adapters that are connected to iSCSI ports on the disk array. Table 8 LUN icons for LUN Manager operations Icon Status A logical volume to which an LU path is defined An expanded LU A command device A command device with security enabled A LUN to which no LU path is defined

The tables contain the following information: • A list of ports • Host Group: Host groups are used to classify servers (hosts) connected to the disk array. You can create host groups in the LUN Manager pane. • Name (Nick Name in iSCSI Name table): Indicates nicknames for hosts. Nicknames can be specified in the LUN Manager pane. • The WWN (WWN table only). Each worldwide name represents one host. • The iSCSI Name (iSCSI Name table only) LDEV table The LDEV table in the lower-left corner of the LUN Manager tab lists LDEVs in the disk array. The LDEV table does not list Auto LUN-reserved LDEVs. The table contains the following information: • A list of CU images • LDEV: A combination of the CU image number and LDEV number that identifies an LDEV. If an LDEV number ends with the sharp symbol (#), the logical volume is an external LU. The following icons indicate LDEV status: • Emulation: Emulation type for each LDEV • Capacity: Size of each LDEV • RAID: RAID level for each LDEV. If the logical volume is an external LU, the RAID column displays a hyphen (-) instead of a RAID level. • PG: Displays names of parity groups. If a parity group name begins with the letter E, the parity group consists of one or more external LUs. • Paths: The number of alternate paths, if any • Access Attribute: Provided for each logical volume Buttons • Apply: Applies settings in the pane to the disk array • Cancel: Cancels settings in the pane • Add LU Path: Adds LUs to LU Path table • Add WWN (WWN table only): Registers host bus adapters in a host group. Applies to Fibre Channel ports only. • Add iSCSI Name (iSCSI Name table only): Registers host bus adapters in a host group. Applies to iSCSI ports only. Defining LU paths To configure a Fibre Channel or iSCSI environment, complete the following major steps: 1. Find the WWNs of the host bus adapters connected to the Fibre Channel ports (Fibre Channel only). Table 9 LDEV icons for LUN Manager operations Icon Status Normal logical volume Expanded LU A VSC volume A command device. A command device with security enabled

33 2. Create host groups (”Creating host groups” on page 33). 3. Register hosts in host groups (”Registering hosts in host groups” on page 34). 4. Associate host groups to logical volumes (”Associating host groups to logical volumes” on page 36). NOTE: If you are configuring a NAS environment, skip steps step 1 through step 3 and follow the procedure in ”Associating host groups to logical volumes” on page 36. Creating host groups NOTE: If you are configuring a NAS environment, skip this section. You can connect multiple server hosts of different platforms to one port of your disk array. When configuring the system, you must group server hosts connected to the disk array by host groups. For example, if HP-UX and Windows hosts are connected to a port, create a host group for each host type. 1. In the LU Path tree, locate the port and verify that LUN security is enabled. NOTE: If the port icon has a key ( ), LUN security is enabled. If LUN security is not enabled, right-click the port and select LUN Security: OFF->ON in the shortcut menu. 2. After LUN security is enabled, right-click the port in the LU Path tree and select Add New Host Group. The Add New Host Group dialog box appears. Figure 14 Add New Host Group dialog box 3. In the Group Name box, enter the host group name. NOTE: It is convenient to name each host group after the host platform. For example, if you are creating a host group for Windows NT® hosts, the host group name could be WNT or WinNT. Host group names are case sensitive and can have up to eight characters. 4. In the Host Mode list, select a host mode. Host groups on the same port can have different host modes. 5. If necessary, select Option, and select the host mode options. For detailed information about host mode options, see Table 10. NOTE: After you select Option, the pane expands to display check boxes. The check boxes are numbered sequentially from left to right. The left-most check box on the upper row is #0, and the check box immediately to the right is #1, and so on. The numbers indicate option numbers; select check box #0 to select option #0. 6. Click OK. The host group name and the host mode appear in blue in the LU Path tree.

7. In the LUN Manager main pane, click Apply. A confirmation message appears. 8. Click OK. The settings are applied to the disk array. The next step is to register hosts to the appropriate host group. CAUTION: Do not select options other than those listed in Table 10. Registering hosts in host groups NOTE: If you are configuring a NAS environment, skip this section. Before you can 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 them separately in two different host groups. When registering a host, you can assign a nickname to the host bus adapter. If you assign a nickname, you will be able to easily identify each host bus adapter in the LUN Manager main pane. Although WWNs (or iSCSI names) are also used to identify each host bus adapter, a nickname is more helpful because you can name host bus adapters after the host installation site or the host owners. When using nicknames, note the following: • A nickname can consist of up to eight ASCII characters (letters, numerals, and symbols). You cannot use the following characters for nicknames: \ / : , ; * ? " < > | ~ • You cannot use the space character for the first or the last nickname character. • Nicknames are case sensitive. For example, hp and HP are different nicknames. To register hosts in a host group: 1. In the LU Path tree, locate the port the host group belongs to and verify that LUN security is enabled. NOTE: If the port icon has a key ( ), LUN security is enabled. If LUN security is not enabled, right-click the port and select LUN Security: OFF->ON in the shortcut menu. Table 10 Host mode options Host mode option When to select option 2 When VERITAS Database Edition/Advanced Cluster for Real Application Clusters or VERITAS Cluster Server 4.0 (I/O fencing function) is used 7 When all the following conditions are satisfied: • The host mode 00 Standard or 09 Solaris is used • 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 When all the following conditions are satisfied: • The host mode 03 HP is used • You want to suppress creation of device files for devices to which the paths are not defined 14 When all the following conditions are satisfied: • The host mode 07 Tru64 is used • You want to use TruCluster to set a cluster to Continuous Access XP P-VOL and S-VOL, respectively

35 2. If the desired host has never been connected via a cable to another port in the disk array, skip to step 8. 3. In the Port list on the upper right corner of the WWN table (Fibre Channel) or the iSCSI name table (iSCSI environment), select the port to which the desired host is connected. 4. Select the desired host bus adapter from the WWN (or iSCSI Name) table. 5. Select a host group from the tree and click the Add WWN (or Add iSCSI Name) button. The Add New WWN (Fibre Channel) or Add New iSCSI Name (iSCSI) dialog box appears. Figure 15 Add New WWN dialog box (Fibre Channel) Figure 16 Add New iSCSI Name dialog box (iSCSI) 6. To assign a nickname to the host bus adapter, enter the nickname in the Nickname box and click OK. NOTE: If two or more host bus adapters are selected, the Add New WWN (or Add New iSCSI) dialog box displays repeatedly to let you assign a nickname to each selected HBA (see Figure 17 and Figure 18). If you do not need to assign nicknames to HBAs, enable the The remaining WWNs (iSCSI Names) do not need names check box and click OK. If you select this option, the Add New WWN (Add New iSCSI Name) dialog box will not prompt you for additional nicknames. Figure 17 Add New WWN dialog box (when registering a host that has previously been connected to the disk array)

Figure 18 Add New iSCSI Name dialog box (when registering a host that has previously been connected to the disk array) 7. Skip to step 11. If the desired host has never been connected via a cable to any port in the array, only step 8 through step 10 apply. 8. Right-click the host group and select Add New WWN (Fibre Channel) or Add New iSCSI Name (iSCSI environment). The Add New WWN (or Add New iSCSI Name) dialog box appears (Figure 15 for Fibre Channel and Figure 16 for iSCSI). 9. Select the desired host bus adapter from the WWN/iSCSI name list. If the host bus adapter is not in the list, enter the WWN (iSCSI name) in the box. 10.If necessary, enter a nickname for the host bus adapter. 11.Click OK. The new WWN (iSCSI Name) and nickname appear below the selected host group in the LU Path tree. 12.Click Apply in the LUN Manager main pane. A confirmation message appears. 13.Click OK. The settings are applied to the disk array. NOTE: For Fibre Channel environments only: If the WWN table (located in the lower-left corner of the pane) includes a host that you want to register, you can register the host by selecting the host group in the LU Path tree, selecting the host from the WWN table, and then clicking Add WWN. Associating host groups to logical volumes You can use LUN Manager to define LU paths by associating host groups to logical volumes. For example, if you associate a group of three hosts with logical volumes, LU paths are defined between the three hosts and the logical volumes. 1. In the LU Path tree on the LUN Manager main pane, select a host group. NOTE: If you are configuring a NAS environment, you must select the User host group. 2. In the CU list above the LDEV table, select a CU number. The LDEV table shows LDEVs in the CU. 3. In the LDEV table, select one or more LDEVs. Press the Ctrl key to select multiple LDEVs. 4. In the LU Path table, select the LUs. 5. Click Add LU Path. A dialog box prompts you to confirm the LU Paths to be defined. 6. Click OK. The settings are shown in blue in the LU Path table. 7. Click Apply in the LUN Manager main pane. A confirmation message appears. 8. Click OK. The settings are applied to the disk array. Changing or viewing LU path settings Deleting LU paths 1. In the LU Path tree on the LUN Manager main pane, select a port.

37 2. In the LU Path table, select one or more LUNs to which LDEVs are assigned (If an LDEV is assigned to a LUN, the columns to the right of the LUN column are not empty). 3. Right-click the selected port and select Release LU Path. A dialog box displays information about the LU paths to be deleted. 4. Click OK. The settings are shown in blue in the LU Path table. 5. Click Apply in the LUN Manager main pane. A confirmation message appears. 6. Click OK. The settings are applied to the disk array. Changing the name and host mode of a host group Before changing the host mode of a host group, back up the data on the host group’s port. The operation for changing host mode should not be destructive, but data integrity cannot be guaranteed without a backup. To change the host mode for host group 0, port security can be enabled or disabled. For all other host groups, you must enable port security before changing the host mode. NOTE: You cannot perform this operation on host groups for NAS ports. 1. In the LU Path tree on the LUN Manager main pane, right-click the host group and select Change Host Group. The Change Host Group dialog box appears. Figure 19 Change Host Group dialog box NOTE: After you select the Option button, the pane expands to display check boxes. The check boxes are numbered sequentially from left to right. The left-most check box on the upper row is #0, and the check box immediately to the right is #1, and so on. The numbers indicate option numbers; select check box #0 to select option #0. 2. To change the name of the host group, enter a new name in the Group Name box. 3. To change the host mode, select the new host mode from the Host Mode list. 4. If necessary, select Option, and select the host mode options. For detailed information about host mode options, see Table 10 on page 34. 5. Click OK. The settings are shown in blue in the LU Path table. 6. Click Apply in the LUN Manager main pane. A confirmation message appears. 7. Click OK. The settings are applied to the disk array. Deleting host groups You cannot delete the host group 0 (zero). If you want to remove all the WWNs and LU paths from the host group 0, you must initialize the host group 0 (”Initializing the host group 0 (zero)” on page 38). NOTE: You cannot perform this operation on host groups for NAS ports.

1. In the LU Path tree on the LUN Manager main pane, right-click a host group and select Delete Host Group. A confirmation message appears. 2. Click Yes to delete the host group. The host group you specified is removed from the LU Path tree. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Initializing the host group 0 (zero) Initializing the host group 0 sets the group to its default state. This process: • Removes all the WWNs from the host group 0 and all the LU paths related to the host group 0. • Changes the host mode of the host group 0 to Standard and initializes the host group name. For example, if you initialize the host group 0 for the port CL1-A, the name of the host group 0 will change to 1A-G00. NOTE: You cannot perform this operation on host groups for NAS ports. 1. In the LU Path tree on the LUN Manager main pane, right-click the host group 0 and select Clear Host Group. A confirmation message appears. 2. Click Yes. • The host mode and host group name are changed in the LU Path tree. • WWNs are removed from host group 0. • LU paths are removed from the LU Path table. • The LUNs corresponding to the removed LU paths are shown in blue. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Changing WWNs, iSCSI names, and nicknames 1. In the LU Path tree, locate the port the HBA is connected to and verify that LUN security is enabled. NOTE: If the port icon has a key ( ), LUN security is enabled. If LUN security is not enabled, right-click the port and select LUN Security: OFF->ON in the shortcut menu. 2. In the LU Path tree, right-click the WWN or iSCSI Name and select Change WWN & Nickname or Change iSCSI Name & Nickname. The Change WWN & Nickname or Change iSCSI Name & Nickname dialog box appears. Figure 20 Change WWN & Nickname dialog box

39 \ Figure 21 Change iSCSI Name & Nickname dialog box If the selected WWN or iSCSI name is not registered in a host group, Figure 20 or Figure 21 is not displayed. 3. Enter the WWN or iSCSI appropriate box, or select it from the list. 4. In the Nickname box, enter the new nickname. 5. If necessary, select the Apply this change to other ports, too check box. If this check box is selected, the change will affect other ports. For example, if you select a host bus adapter located beneath ports CL1-A and CL2-A in the tree, and you change the host bus adapter name under port CL1-A, the host bus adapter will also be renamed under port CL2-A. NOTE: The change in the pane will not affect any port that satisfies at least one of the following conditions: • LUN security is OFF. • The resulting nickname is already used as the nickname of a host bus adapter connected to the port. • The resulting nickname is already used as the name of a host group (that is, a host storage domain) in the port. • The resulting WWN or iSCSI name exists in the port. 6. Click OK. The changes you made are shown in blue. If you selected the Apply this change to other ports, too check box, the Check WWNs (or Check iSCSI names) dialog box appears. To accept the changes to the other ports, click OK. Figure 22 Check WWNs / Check iSCSI names 7. Click Apply in the LUN Manager main pane. A confirmation message appears. 8. Click OK. The settings are applied to the disk array.

Deleting HBAs from host groups NOTE: You cannot perform this operation on host groups for NAS ports. 1. In the LU Path tree, right-click the HBA and select Delete WWN (or Delete iSCSI Name). A confirmation message appears. 2. Click Yes. The WWN or (iSCSI name) you specified is removed from the LU Path tree. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Deleting unneeded WWNs from the WWN table If you disconnect a host that has been connected through a cable to your disk array, the WWN for the host remains in the WWN table until you remove it. 1. In the WWN table, locate the WWN that is not registered in any host group. NOTE: If the Host Group column is blank, the WWN is not registered in any host group. 2. Right-click the WWN and select Erase WWN. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Viewing a list of concatenated parity groups The XP128/XP1024 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). 1. In the LDEV table, right-click a logical volume (an LDEV). If the parity groups are concatenated, the Concatenation List command is available in the shortcut menu. 2. Select Concatenation List. The Concatenation List dialog box appears. 3. Click OK to return to the LUN Manager main pane. Defining alternate paths LUN Manager can define alternate paths. If an LU path fails, you can switch to its alternate path. To create an alternate path, copy the original path from one port to another. For example, to define an alternate for the LU path between the CL1-A port and logical volume 00:01, copy the LU path from the CL1-A port to another port. If you want to define alternate paths when LUN security is removed, you must redefine the LU path. Table 11 Copying LU paths To copy paths… See… from one iSCSI or Fibre Channel port to another ”Copying paths from one Fibre Channel or iSCSI port to another” on page 41 from one NAS port to another ”Copying paths from one NAS port to another” on page 41 from a Fibre Channel or iSCSI port to a NAS Port ”Copying paths from a Fibre Channel or iSCSI port to a NAS port” on page 42 from a NAS Port to a Fibre Channel or iSCSI Port ”Copying paths from a NAS port to a Fibre Channel or iSCSI port” on page 42

41 Copying paths from one Fibre Channel or iSCSI port to another CAUTION: Before performing the following steps, see ”Restrictions on port operations” on page 55 for important information. 1. In the LU Path tree, locate the port that you want to use as the copy destination and verify that LUN security is enabled. NOTE: If the port icon has a key ( ), LUN security is enabled. If LUN security is not enabled, right-click the port and select LUN Security: OFF->ON in the shortcut menu. 2. To copy all the LU paths defined to a host group, complete the following steps. To copy some LU paths, skip to step 3. a. Right-click a host group in the tree and select Copy. The selected host group turns green. b. Right-click the copy destination port and select Paste. 3. To copy some, but not all of the LU paths defined to a host group, complete the following steps. To copy all LU paths, see step 2. a. Select a host group in the LU Path tree. b. In the LU Path table, select one or more LUNs to which volumes are assigned. c. Right-click the selection and select Copy Paths in the shortcut menu. The selected LUNs turn green. d. Double-click the copy destination port. e. Right-click the copy destination host group and select Paste Paths. 4. Click Apply in the LUN Manager main pane. A confirmation message appears. 5. Click OK. The settings are applied to the disk array. Copying paths from one NAS port to another CAUTION: Before performing the following steps, see ”Restrictions on port operations” on page 55 for important information. 1. Specify the LU paths to copy: a. In the LU Path tree, double-click a NAS port (the copy source port) and select the User host group. b. In the LU Path table, select one or more LUNs to which volumes are assigned. NOTE: If a volume is assigned to a LUN, the columns on the right of the LUN column are not empty. c. Right-click the selected LUNs and select Copy Paths. The selected LUNs turn green. 2. Paste the LU paths: a. In the LU Path tree, double-click the copy destination port (a NAS port) to display the User host group below the port. b. Right-click the User host group and select Paste Paths. 3. Click Apply in the LUN Manager tab. A confirmation message appears. 4. Click OK. The settings are applied to the disk array.

Copying paths from a Fibre Channel or iSCSI port to a NAS port CAUTION: Before performing the following steps, see ”Restrictions on port operations” on page 55 for important information. 1. Specify the LU paths to copy: a. In the LU Path tree, double-click a Fibre Channel or iSCSI port (the copy source port) and then select a host group. The LU Path table displays LU path information. b. In the table, select one or more LUNs to which volumes are assigned. NOTE: If a volume is assigned to a LUN, the columns on the right of the LUN column are not empty. c. Right-click the selected LUNs and select Copy Paths. The selected LUNs turn green. 2. Paste the LU paths: a. In the LU Path tree, double-click a NAS port (the copy destination port) to display the User host group. b. Right-click the User host group and select Paste Paths. 3. Click Apply in the LUN Manager tab. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Copying paths from a NAS port to a Fibre Channel or iSCSI port CAUTION: Before performing the following steps, see ”Restrictions on port operations” on page 55 for important information. 1. Specify the LU paths to copy: a. In the LU Path tree, double-click a NAS port (the copy source port) and select the User host group. b. In the LU Path table, select one or more LUNs to which volumes are assigned. NOTE: If a volume is assigned to a LUN, the columns on the right of the LUN column are not empty. c. Right-click the selected LUNs and select Copy Paths. The selected LUNs turn green. 2. In the LU Path tree, locate the Fibre Channel or iSCSI port that you want to use as the copy destination and verify that LUN security is enabled on the port. NOTE: If the port icon has a key ( ), LUN security is enabled. If LUN security is not enabled, right-click the port and select LUN Security: OFF->ON in the shortcut menu. 3. Paste the LU paths: a. Double-click the Fibre Channel or iSCSI port (the copy destination port) to display host groups below the port. b. Right-click the host group to which you want to paste paths and select Paste Paths. 4. Click Apply in the LUN Manager tab. A confirmation message appears. 5. Click OK. The settings are applied to the disk array.

43 Viewing alternate paths 1. From the LUN Manager main pane, do one of the following: • In the LU Path table, select a LUN containing one or more paths. • In the LDEV table, select an LDEV containing one or more paths. 2. Right-click the selection and select Alternate Paths.The Alternate Paths dialog box appears. 3. Click OK. Deleting WWNs 1. In the LU Path tree, right-click a WWN and select Delete WWN. A confirmation message appears. NOTE: If the selected WWN is not registered in a host group, the Delete WWN command is not available. 2. Click Yes. The selected WWN is no longer listed in the LU Path tree. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Applying and removing LUN security By default, LUN security is not applied to any ports. When configuring your system, you must apply LUN security to the ports. If a port has the External attribute, you cannot apply LUN security to the port. The icon indicates a port without LUN security and changes to the icon when LUN security is applied. NOTE: You cannot apply LUN security to NAS ports. 1. Right-click a port in the LU Path tree. a. To apply LUN security, select LUN Security: OFF->ON. b. To remove LUN security, select LUN Security: ON->OFF. A confirmation message appears. 2. Click Yes. The changes are shown in blue. 3. Click Apply in the LUN Manager main pane. A confirmation message appears. 4. Click OK. The settings are applied to the disk array. Creating RAID Manager Command Devices To enter RAID Manager commands, set up at least one LU as a command device. The icon indicates an LDEV that is not a command device and changes to the icon when set to a command device. When security is enabled, the icon changes to . CAUTION: • If a path is defined between an iSCSI port and a logical device, you cannot use the logical device as a command device. • You cannot define paths between iSCSI ports and command devices. Setting an LU as a command device 1. In the LU Path tree, double-click a port and then select a host group. 2. In the LU Path or LDEV table, right-click the LUN and select Command Device: OFF->ON. A confirmation message appears.

NOTE: If the shortcut menu includes the item Command Device: ON->OFF, the logical device is already specified as a command device and you do not need to complete this procedure. 3. Click Yes. The changes are shown in blue. 4. Click Apply in the LUN Manager main pane. A confirmation message appears. 5. Click OK. The settings are applied to the disk array. Stopping the use of an LU as a command device Right-click the command device and select Command Device: ON->OFF. Applying command device security Right-click the command device and select Cmd. Dev. Security: OFF->ON. Removing command device security Right-click the command device and select Cmd. Dev. Security: ON->OFF. Port Operations Use the Port tab in the LUN Manager pane to configure Fibre Channel and iSCSI ports in your disk array. You can also use this pane to modify the port configuration when the disk array is operating. NOTE: You cannot use the Port tab to make settings on NAS ports. Starting Port Operations 1. Click LUN Manager in the left pane. The LUN Manager pane appears. 2. Click the Port tab. The Port pane appears. Figure 23 Port pane Port tab The Port tab includes the package tree, port table, and change port mode box. Package tree The Package tree lists all Fibre Channel and iSCSI channel adapter (CHA) packages. When you right-click a CHA package, you can choose standard mode, high-speed mode, or high-speed (2 port) mode.

45 NOTE: High-speed (2 port) mode is available only if the XP disk array has firmware version 21.06.22 or later installed. The following icons are used to indicate status: Port table The Port table displays information about the ports in the selected CHA packages. The information in this table differs depending on the type of channel adapter package selected in the tree. The table lists the following for Fibre Channel CHA packages: • Port Name: Displays port names • Type: Fibre indicates a Fibre Channel port, used for connecting open system hosts. MF-Serial indicates an ESCON® port, used for connecting mainframe hosts. • Host Speed: Specifies the data transfer speed for Fibre Channel ports. If Auto is selected, the disk array automatically sets the data transfer speed to 1 GB/sec or 2 GB/sec. • Addr (Loop ID): Displays addresses of ports. You can change port addresses. • Fabric: Specify ON if a fabric switch is used, or OFF if no fabric switch is used • Connection: Specifies the topology. The default is FC-AL. Some fabric switches require you to specify point-to-point topology. Check the switch’s documentation. • Attribute: Indicates whether the port is an initiator port, target port, RCU target port, or external port • WWN: Displays WWNs of ports. The table lists the following for iSCSI CHA packages: • Port Name: Displays iSCSI port names • IP Address: Displays the iSCSI port IP addresses • Subnet Mask: Displays subnet masks • Gateway: Displays gateway addresses • iSCSI Name: Displays iSCSI port names • iSCSI Alias: Displays iSCSI port aliases • Port Number: Displays iSCSI port numbers • Keep Alive Timer: Displays the keep-alive timer values in seconds • INS 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: Displays the IP address of the ISNS server • iSNS Port No: Displays the TCP port number of the iSNS server • MAC Address: Displays the iSCSI port media access control (MAC) addresses Table 12 Channel adapter package icons for Port operations Icon Status A short-wave CHA package in standard mode (Fibre Channel) or A short-wave iSCSI CHA package A long-wave CHA package in standard mode A short-wave CHA package in high-speed or high-speed (2 port) mode A long-wave CHA package in high-speed or high-speed (2 port) mode

• Attribute: Indicates the port attribute (always set to Target for iSCSI ports) • iSCSI Function box: Enables you to perform iSCSI-related operations iSCSI Function box Use this box to perform iSCSI-related operations. • Ping: Issues a ping command from an iSCSI port to a host • Register: Registers iSCSI port information (such as IP addresses and iSCSI names) in the iSNS server • Delete: Removes iSCSI port information (such as IP addresses and iSCSI names) from the iSNS server Change Port Mode box Use this box to change information in the Port table. Setting the Fibre Channel Topology 1. In the Port table or the Select a Port list, select a Fibre Channel port. 2. If a fabric switch is used, select ON in the Fabric list in the Mode area. If a fabric switch is not used, select OFF in the Fabric list. 3. In the Connection list, select FC-AL or P-to-P. If a fabric switch is used, consult the switch documentation to check if it requires point-to-point topology. 4. Click Set. A confirmation message appears. 5. Click OK. The settings are applied to the Port table (shown in blue), but not to the disk array. 6. Click Apply. A confirmation message appears. 7. Click OK. The settings are applied to the disk array. Setting Fibre Channel Port Addresses 1. In the Port table or the Select a Port list, select a Fibre Channel port. 2. In the Fibre Address list in the Mode area, select an address. 3. Click Set. A confirmation message appears. 4. Click OK. The settings are applied to the Port table (shown in blue), but not to the disk array. 5. Click Apply. A confirmation message appears. 6. Click OK. The settings are applied to the disk array. Setting the Data Transfer Speed 1. In the Port table or the Select a Port list, select a Fibre Channel port. 2. In the Host Speed list in the Mode area, select a data transfer speed. 3. Click Set. A confirmation message appears. 4. Click OK. The settings are applied to the Port table (shown in blue), but not to the disk array. 5. Click Apply. A confirmation message appears. 6. Click OK. The settings are applied to the disk array. Switching to standard, high-speed, or high-speed (2 port) mode Channel adapter boards can be set for standard mode, high-speed, or high-speed (2 port) mode. If possible, apply high-speed mode to channel adapters to improve the system performance. Be aware that you can only apply high-speed or high-speed (2 port) mode to channel adapters that satisfy certain requirements. NOTE: High-speed (2 port) mode is available only if the XP disk array has firmware version 21.06.22 or later installed. 1. In the Package tree on the Port pane, right-click a channel adapter (CHA) package. A shortcut menu appears. The current mode is preceded by a bullet. 2. Select the mode that you want. A confirmation message appears.

47 3. Click OK. 4. Click Apply. A confirmation message appears. 5. Click OK. The settings are applied to the disk array. Configuring iSCSI Ports 1. In the Port table or the Select a Port list on the Port pane, select an iSCSI port. The current configuration of the iSCSI port appears below the Select a Port list. 2. To configure the port, edit the items below the list. For detailed information about the items, see ”iSCSI port settings and iSNS server settings” on page 23. NOTE: Use the vertical scroll bar to view all the items (some of the items are hidden). 3. Click Set. A confirmation message appears. 4. Click OK. The settings are applied to the Port table (shown in blue), but not to the disk array. 5. Click Apply. A confirmation message appears. 6. Click OK. The settings are applied to the disk array. Making settings on iSCSI ports and iSNS servers Use the Port tab of the LUN Manager pane to configure iSCSI ports in your disk array, make settings on iSNS servers, and modify settings when the system is in operation. 1. Ensure that the Command View XP or XP Remote Web Console main pane is in Modify mode. 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 XP1024/XP128. 2. In the LUN Manager pane, select the Port tab. 3. In the Package tree view, click the iSCSI folder. The Port table displays a list of iSCSI ports in the disk array. TIP: If you specify a channel adapter in the Package tree view, the Port table displays only the ports in the specified channel adapter. 4. Select an iSCSI port from the Port table or the Select a Port drop-down list. The current configuration of the iSCSI port is displayed below the Select a Port drop down list. NOTE: Use the vertical scroll bar to view all the items. 5. Edit the items below the drop-down list. 6. Click Set. A message appears asking if you want to change the port settings. 7. Click OK to close the message. Settings are applied to the Port table, but not to the disk array. 8. Click Apply. A message appears asking if you want to apply the setting to the disk array. 9. Click OK to close the message. Settings are applied to the disk array. NOTE: If a message appears prompting you to register the iSCSI port, click Yes. If the registration process finishes, a pane appears indicating if the registration ended successfully. If the registration ended successfully, the pane displays Success. If the registration failed, the pane displays the error code and error message. Resolve the error and retry registration by clicking Register in the iSCSI Function box in the Port tab. Removing information about an iSCSI port from an iSNS server 1. In the Port tab, click Delete in the iSCSI Function box. The Delete iSNS Information pane appears.

2. Select an iSCSI port from the Subsystem Port Name. The IP address of the iSNS server appears in the iSNS Server IP Address. Also, the port number of the iSNS server appears in the iSNS Server Port Number. 3. Click OK. Information about the iSCSI port is removed from the iSNS server, and the iSCSI port is unregistered from the iSNS server. Checking the status of connection between hosts and the disk array (iSCSI environment only) In an iSCSI environment, use LUN Manager to issue a ping command from a disk array port to a host. The ping command checks whether the host and disk array can communicate with each other. If the host responds to the ping command, the host and disk array can communicate with each other. Issuing a ping command from an iSCSI port to a host 1. Ensure that the Port tab is displayed in the pane. 2. Click Ping below the Package tree view. The Ping pane appears. 3. Select an iSCSI port from From (Subsystem Port). 4. Enter the IP address of the host in To (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 Result pane appears and displays the results in the order attempts were made. • 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 success rate of the ping command. 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. 6. Click OK to close the Ping Result pane. 7. To issue a ping command, return to step 3. Otherwise, click Cancel to close the Ping window. TIP: You can issue a ping command from an iSCSI port to an iSNS server. To verify connectivity between an iSNS server and disk array, issue a ping command to the iSNS server. If the iSNS responds to the ping command, the iSNS server and disk array can communicate with each other. Setting user authentication (iSCSI environments only) When configuring an iSCSI environment, you can use the User Authentication tab to set the user authentication on disk array ports. First specify whether to perform authentication of hosts for each port. Then register user information of hosts on the ports that perform authentication. This setting determines whether ports can authenticate hosts that request to connect, and can restrict the connections. In addition, if you want to implement mutual authentication, specify user information about each disk array port. NOTE: The hosts to be connected must also be configured for authentication by ports (and for port authentication by the host, if required). For details on how to configure the host for CHAP authentication, refer to your operating system and iSCSI driver documentation. Starting User Authentication Operations NOTE: User authentication can be performed in an iSCSI environment only. 1. Click the LUN and Volume Mgmt tab, and then click the LUN Manager button ( ). The LUN Manager main pane appears.

49 2. Click the User Authentication tab. The User Authentication pane appears. Figure 24 User Authentication tab (LUN Manager pane) User Authentication tab The User Authentication tab includes the port tree and User Information (Host) table. Port tree This tree displays information about user authentication on each port. When you select a port from this tree, the User Information (Host) table on the right displays user information of hosts registered on the port. In addition, the User Information (Port) table below the User Information (Host) table displays user information of the selected port. The iSCSI folder appears below the Subsystem folder located at the top of the tree. If you double-click the iSCSI folder, iSCSI ports in the disk array appear as icons. The port name and user authentication status to the right of each icon: • (Authentication:ON): The port performs host authentication. • (Authentication:OFF): The port does not perform host authentication. This is the default value. NOTE: The iSCSI folder is displayed only if the disk array contains an iSCSI channel adapter. The following icons are used to indicate the port’s user authentication status. User Information (Host) table The User Information (Host) table, on the top right of the User Authentication tab, displays user information of hosts that are allowed to connect to the iSCSI port specified in the tree. You can register up to 64 user information items in this table. Table 13 iSCSI port icons for User Authentication operations Icon Status CLX-Y (Authentication:ON) The port authenticates hosts CLX-Y (Authentication:OFF) The port does not authenticate hosts

The table contains the following columns: • iSCSI Name: Displays iSCSI names of host bus adapters. • Protocol: Indicates the user authentication protocol. This is always CHAP. • User: Indicates user names of hosts. When no user name is defined, this column is blank. • Authentication: Indicates whether to perform authentication for the host. If the host is a target of user authentication, Enable appears. If the host is not a target of user authentication, Disable appears. User Information (Port) table The User Information (Port) table, on the bottom right of the User Authentication tab, displays user information of the port selected in the tree. The table contains the following columns: • iSCSI Name: Displays the iSCSI name of the port. • User: Indicates the user name of the port. When the user name is not defined for a port, this column is left blank. If you use upgraded LUN Manager and the port performed host authentication before upgrading, Administrator appears as the default. Buttons • Apply: Applies settings in the pane to the disk array. • Cancel: Cancels settings in the pane. Specifying whether to enable or disable host authentication on a port You can specify whether to perform host authentication on each port. By default, user authentication is disabled. 1. In the Port tree on the User Authentication tab, double-click the Subsystem folder. If the disk array contains any iSCSI channel adapters, the iSCSI folder appears below the Subsystem folder. 2. Double-click the iSCSI folder. 3. Right-click an iSCSI port that is displayed with (Authentication:OFF). 4. Select Authentication: OFF -> ON. The (Authentication:OFF) displayed on the right of the port name changes to (Authentication:ON), and the port name and (Authentication:ON) are displayed in blue. 5. Click Apply. A confirmation message appears. 6. Click OK. The setting is applied to the disk array. NOTE: To disable authentication on a port (return the port setting to (Authentication:OFF), perform the same operation, but select Authentication: ON -> OFF in step 4. Registering user information of hosts on a port On iSCSI ports that authenticate hosts, you must register user information for all the hosts that you allow to connect. 1. In the Port tree, select a port for which you want to register user information of a host. The user information of hosts currently registered on the selected port appears in the User Information (Host) table to the right of the Port tree. NOTE: You can register user information of a host even if the port status is (Authentication:OFF). In this case, however, the registered user information of the host is ignored. 2. Do one of the following: a. In the Port tree, right-click a port on which you want to register user information of a host.

51 b. Right-click any point in the User Information (Host) table. 3. Select Add New User Information (Host) from the shortcut menu. The Add New User Information (Host) dialog box appears. Figure 25 Add New User Information dialog box In this dialog box, specify the following user information for the host you want to allow to connect: • iSCSI Name: Specify the iSCSI name of the host bus adapter by selecting an HBA from the list or entering it directly. The list displays all the iSCSI names of host bus adapters connected to the selected port by the cable. For details on the characters and length you can specify as an iSCSI name, see ”iSCSI port settings and iSNS server settings” on page 23. • Protocol: Specify the protocol used in the user authentication. The required value is CHAP. • User: Specify the user name of the host (up to 64 characters). If you select the Enable authentication check box on the bottom-left, the user name is mandatory. You can use alphanumeric characters, spaces, and the following symbols in a user name: . - + @ _ = : / [ ] , ~ User names are case sensitive. For example, the user names host1 and Host1 represent different users. • Secret: Specify the secret (a password used in CHAP authentication). The secret can be between 12 and 32 characters. If you select the Enable authentication check box, the secret is mandatory. You can use same characters and symbols as in a user name. • Re-enter Secret: Specify the secret, again, for confirmation. • Enable authentication: Select this check box when you want to perform user authentication of the registered host. By default, this check box is selected. If you clear this check box, the host connects to the disk array without authentication. When the Enable authentication check box is deselected, you do not need to specify the User, Secret, and Re-enter Secret boxes. NOTE: If a host uses Microsoft iSCSI Initiator and is configured for port authentication using CHAP, the host cannot connect to the disk array even if you clear the Enable authentication check box. 4. Click OK. The specified user information is added in blue in the User Information (Host) table. 5. Click Apply. A confirmation message appears. 6. Click OK. The setting is applied to the disk array. NOTE: If you want to allow a specific host to connect to a port without user authentication, see the information in ”Host authentication” on page 25.

Changing user information of hosts You can change the registered user name or secret of a host, and toggle switch authentication settings between enable and disable after registration. NOTE: You cannot change iSCSI names when you change user information. 1. In the Port tree, expand the iSCSI folder and select a port on which the user information you want to change is registered. All the user information of the hosts registered on the selected port appears in the User Information (Host) table. 2. In the User Information (Host) table, right-click a user information item that you want to change and select Change User Information (Host). The Change User Information (Host) dialog box appears. Figure 26 Change User Information (Host) dialog box 3. Change the user information of the host as required in the Change User Information (Host) dialog box. You can change the contents of User, Secret, and Enable authentication check box. For details on characters and length you can use in the user name or secret, see ”Registering user information of hosts on a port” on page 50. 4. Click OK. The specified user information is added in blue in the User Information (Host) table. 5. Click Apply. A confirmation message appears. 6. Click OK. The setting is applied to the disk array. Deleting user information of hosts 1. In the Port tree, expand the iSCSI folder and select a port on which the user information you want to delete is registered. The user information of hosts currently registered on the selected port appears in the User Information (Host) table. 2. In the User Information (Host) table, right-click a user information item that you want to delete and select Delete User Information (Host). A confirmation message appears. 3. Click OK. 4. Click Apply. A confirmation message appears. 5. Click OK. The user information is deleted from the disk array. Specifying user information of ports (when performing mutual authentication) To perform mutual authentication, you need to specify user information on the disk array ports. You must provide unique user information for each port. You can change the specified user information of ports the same way you specified them initially. 1. In the Port tree on the User Authentication tab, select a port whose user information you want to specify. The currently registered user information for the selected port appears in the User Information (Port) table below the User Information (Host) table.

53 2. Right-click any point in the User Information (Port) table and select Specify User Information (Port). The Specify User Information (Host) dialog box appears. Figure 27 Specify User Information (Port) dialog box The following items are entered automatically and cannot be changed. • iSCSI Name of the selected port appears. You cannot change the iSCSI name. • Protocol used in the user authentication appears. This protocol is set to CHAP and you cannot change it. Specify the following user information for the selected port. • User. Enter the user name of the port up to 64 characters. You can use alphanumeric characters, spaces, and the following symbols in a user name: . - + @ _ = : / [ ] , ~ User names are case sensitive. For example, the user names port1 and Port1 represent different users. If you use the upgraded LUN Manager and the port performed authentication of hosts before upgrading, Administrator appears as the default. To perform mutual authentication on such a port, rename the user name of the port. • Secret. Specify the secret (a password used in CHAP authentication) between 12 to 32 characters. You can use same characters and symbols as a user name. • Re-enter Secret. Specify the secret again for confirmation. 3. Click OK. The specified user information of the port appears in blue in the User Information (Port) table. 4. Click Apply. A confirmation message appears. 5. Click OK. The setting is applied to the disk array. Clearing user information of ports (when performing mutual authentication) 1. In the Port tree on the User Authentication tab, expand the iSCSI folder and select a port whose user information you want to clear. The currently registered user information of the port appears in the User Information (Port) table below the User Information (Host) table. 2. Right-click any point in the User Information (Port) table and select Clear User Information (Port). A confirmation message appears. 3. Click OK. The user information of the selected port disappears from the User Information (Port) table. 4. Click Apply. A confirmation message appears. 5. Click OK. The setting is applied to the disk array. Relationship between port settings and connection results During host authentication, the connection result is determined by the combination of the following port settings: • Port settings in the Port tree: Authentication:ON or Authentication:OFF • Whether the user information of the host that is trying to connect is registered on the host • Whether the Enable authentication check box is selected for the user information of the host to be connected

Table 14 shows the relationship between the combinations of port settings and the connection results. Irrespective of whether a host is configured for port authentication using CHAP, the connection results are as follows, unless otherwise noted. . For additional information on user authentication, see ”User authentication (iSCSI environments only)” on page 24. Operational restrictions The success of some LUN Manager activities depends on the status of the security switch and whether I/O is active or inactive to the port or LUN. The following tables describe those restrictions. NOTE: • If you attempt to apply a large number of the settings in the LUN Manager panels in a single session, the XP128/XP1024 might be unable to continue processing. It is recommended that you apply no more than 1,000 settings per session. Note that a large number of settings are likely to be applied when you define alternate paths (see ”Defining alternate paths” on page 40), even though only two commands are required to define alternate paths. • Do not remove LU paths (see ”Changing or viewing LU path settings” on page 36) when the hosts are performing I/O processing. • Do not remove LUN security (see ”Applying and removing LUN security” on page 43) when the hosts are performing I/O processing. Restrictions on LUN Manager operations Table 14 Combinations of iSCSI port settings and connection results Port settings Connection results Authentication: at port User information registered on host? Enable authentication ON Yes Selected Connected if the host authentication was successful (processing will continue to port authentication)1 1. If a host is not configured for port authentication using CHAP, the host cannot connect to the disk array. ON Yes Not selected Connected without host authentication ON No —2 2. ---: This item does not affect the connection results, or cannot be specified. Authentication failed to be authenticated and cannot be connected OFF — — Connected without host authentication3 3. If a host uses Microsoft iSCSI Initiator and is configured for port authentication using CHAP, host authentication will fail. To allow such a host to connect to the port without authentication, do not configure it for CHAP port authentication. Table 15 LUN Manager operation restrictions Activity Security switch OFF Security switch ON Host group 0 Host group 01-7F Host group 0 Host group 01-7F Setting the LUN Security Switch ON With active I/O on port Permitted with confirmation message Invalid operation Invalid operation With no active I/O on port

55 Restrictions on port operations Setting the LUN Security Switch OFF With active I/O on port Invalid operation Permitted with confirmation message With no active I/O on port Adding a host group With active I/O on port Default host group Not permitted Default host group Permitted With no active I/O on port Adding a WWN or iSCSI name With active I/O on port Invalid operation Permitted With no active I/O on port Adding a LUN With active I/O on port Permitted Invalid operation Permitted With no active I/O on port Deleting a WWN or iSCSI name With active I/O on port Invalid operation Permitted with confirmation message With no active I/O on port Deleting a LUN With active I/O to deleted LUN Not permitted Invalid operation Not permitted With no active I/O on LUN Permitted Permitted Deleting a command device With active I/O on LUN Not permitted Invalid operation Not permitted With no active I/O on LUN Permitted Permitted Deleting a host group With active I/O on LUN Not permitted Invalid operation Not permitted With no active I/O on LUN Not permitted Permitted Table 15 LUN Manager operation restrictions (continued) Activity Security switch OFF Security switch ON Host group 0 Host group 01-7F Host group 0 Host group 01-7F Table 16 Port operation restrictions Activity Changing topology With active I/O on LUN Not permitted With no active I/O on LUN Permitted Changing fibre address With active I/O on LUN Not permitted With no active I/O on LUN Permitted Changing host speed With active I/O on LUN Not permitted With no active I/O on LUN Permitted

Changing PCB mode With active I/O on LUN Not permitted With no active I/O on LUN Permitted Changing host mode With active I/O on LUN Not permitted With no active I/O on LUN Permitted Table 16 Port operation restrictions (continued) Activity

57 2 Volume Management for the XP128/XP1024 Use Volume Management to perform the following tasks: • ”Volume Management (LU Size Expansion)” on page 57) • ”Volume Size Configuration (VSC)” on page 58) Volume Management (LU Size Expansion) Volume Management (LU Size Expansion or LUSE) combines two or more LDEVs to function as a larger LDEV. As a result, a host can access a greater amount of storage with a smaller number of LDEVs. Figure 28 shows the effect of a LUSE configuration. Figure 28 LUSE configuration LUSE can combine up to 36 LDEVs into a LUSE volume. The LDEV number of the LUSE volume is the first or lowest number of the LDEVs making up the LUSE volume. This is the top LDEV, and is the number the host will recognize. Drawbacks • Some operating systems may experience slow disk access times with large logical units, if they contain a large number of high-use files. • The size of a LUSE volume can increase the amount of time required to perform backups. LUSE rules • Open volume emulation types OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, or OPEN-V are supported. • The maximum number of LDEVs that can be used to create a LUSE is 36. • LDEVs must be of the same emulation type. • LDEVs must be at the same RAID level. 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 have no assigned path definitions. These are known as free (or available) LDEVs. For this reason, Business Copy XP, Continuous Access XP, TrueCopy (TC390), ShadowImage (SI390), and Continuous Access XP Journal pair volumes cannot be targets of LUSE operations. For more information, see ”LUSE operations that handle a path-defined LDEV” on page 58. • LDEVs that are to be combined into LUSE volumes must not be reserved for Auto LUN. • When you combine a LUSE volume with another LUSE volume, the range of LDEVs should not be overlapped.

For example, if you combine LDEV00, LDEV03 and LDEV05 into LUSE 1, LDEV02 and LDEV04 into LUSE 2, and 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 is overlapped. • A maximum of 256 expanded logical units (LUs) can be configured on the same port. • The maximum capacity of a LUSE volume is 2 TB for XP128/XP1024 arrays. • The access attribute must be set to read/write when creating or releasing a LUSE volume. • When releasing a LUSE volume, the volume should have no path definitions. • Combining internal and external volumes is not supported. • The IO suppression mode and cache mode settings of the LDEVs combined into a LUSE volume must be the same. • All the LDEVs combined into a LUSE volume must be of the same drive type (either the SATA drive or non-SATA drive). LUSE operations that handle a path-defined LDEV You can use an LDEV or another LUSE volume that has path definitions as the top LDEV of the resulting LUSE volume, and can combine the top LDEV with other LDEVs or LUSEs that have no path definitions. Creating this type of LUSE volume is referred to as “a LUSE operation that handles a path-defined LDEV.” When creating a LUSE volume in this manner, the following rules apply: • You can combine an LDEV or LUSE volume having no path definitions with another LDEV or LUSE volume having no path definitions. • You can perform a LUSE operation that handles a path-defined LDEV regardless of how many paths are defined to the LDEV. • If you want to use an LDEV or a LUSE volume having no path definitions as the top LDEV of the resulting LUSE volume, you cannot combine this LDEV or LUSE volume with other LDEVs or LUSE volumes having path definitions. When performing a LUSE operation that handles a path-defined LDEV: • If a path is defined from a Windows 2000 host, a Windows Server 2003 host, or an AIX 5.2 host to an LDEV, the LDEV can be used for LUSE operations that handle a path-defined LDEV. However, if a path is defined from a host running another operating system to an LDEV, the LDEV cannot be used for LUSE operations that handle a path-defined LDEV. • If a path is defined from a Windows 2000 host or a Windows Server 2003 host to an LDEV and you want to perform a LUSE operation that handles this path-defined LDEV, verify that the host mode of the Windows host is 2C (Windows Extension). If the host mode is not 2C, change the host mode to 2C before performing the LUSE operation. • If the host mode is 0C (Windows Extension) and an LU path is defined for a volume, you cannot perform LUSE operations on the volume without unmapping the volume first. Volume Size Configuration (VSC) The Volume Size Configuration (VSC) process configures custom volumes (CVs) that are smaller than normal volumes. Custom volumes improve data access performance by reducing logical device contention as well as host I/O queue times, which can occur when several frequently-accessed files are located on the same volume. If several frequently-accessed files are on the same LDEV, using VSC to set up smaller, separate custom volumes for them can reduce conflicts and improve performance. A small custom volume can be used as a command device. This leaves the rest of the LDEV free for other uses. VSC operations VSC operations include the following: • Volume to Space: Formats one or more LDEVs on a selected VDEV into free space, which can be used to install one or more custom volumes using the Install CV function, or left as free space for future use.

59 • Install CV: Creates custom volumes from free space. • Make Volume: Converts a custom volume back to a normal volume (VDEV). The Make Volume function clears all custom volumes under a VSC volume and creates an initial volume (VDEV) that consists of new user-defined custom volumes. The Volume Initialize function uninstalls all custom volumes under a VSC volume, and reformats the VSC volume as a normal volume (VDEV). Compared to other emulation types, use OPEN-V to easily create volumes of any size. OPEN-V volumes always consist of custom volumes, instead of fixed-size volumes. CAUTION: VSC operations are destructive. Back up your data before performing VSC operations. Figure 29 and Figure 30 show a sample VDEV (whose components are LDEVs) in its initial condition and the VDEV after custom volumes are created. Figure 29 VSC process (all supported emulation types except for OPEN-V) Figure 30 VSC process (OPEN-V) Parity group configuration This section explains the parity group configuration of emulation types other than OPEN-V. OPEN-V volumes always consist of variable sized volumes instead of fixed-size volumes (FVs). To use OPEN-V, parity groups must be enabled to support the OPEN-V emulation type. To enable OPEN-V, contact your HP account support representative. For emulation types other than OPEN-V, one parity group consists of a maximum of 16 VDEVs. For RAID-5 (7D + 1P) level 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. Each VDEV in a parity group has the same configuration, and is assigned the same FVs of the same size and RAID level. VSC 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. You cannot define a volume across two or more VDEVs beyond the boundaries. Figure 31 Parity group configuration for other than OPEN-V As the result of VSC operations, a VDEV contains fixed volumes, custom volumes, and free spaces that are delimited in logical cylinders. Sequential free spaces are combined into a single free space. Figure 32 Virtual VSC volume configuration for other than OPEN-V Before changing ordinary target ports or RCU target ports to initiator ports, make sure that no I/Os (such as Extended Copy commands) are being performed from the host server to the affected ports. You can change the port type of free ports only. Volume to Space operation The Volume to Space function converts one or more LDEVs (fixed or custom volumes) into free space, which deletes the selected LDEVs from that volume.

61 Restrictions • The LDEV must not have a path definition, including TrueCopy (TC390), Continuous Access XP, ShadowImage (SI390), Business Copy (BC), and Continuous Access XP Journal pair volumes. • The LDEV must not be a component of a LUSE volume. This applies to all supported emulation types except for OPEN-V. • The LDEV must not be reserved for Auto LUN. • The access attribute must be set to Read/Write. Install Custom Volume (CV) operation The Install CV function defines and installs one or more VSC volumes under an existing volume (free space in a VDEV). You can assign a specific number of physical cylinders (for mainframe systems) or MB (for open systems) to each VSC volume for maximum control over the volume size. When you specify the capacity and the emulation type other than OPEN-V for a VSC volume to be created, the Install CV function automatically creates and formats the VSC volume in sufficient free space. You must specify a new CU number and LDEV number for the created VSC volume. The created VSC volume contains the user-specified number of user cylinders and a predetermined number of control cylinders by the emulation type. If you select free space and perform an Install CV operation, VSC volumes will be created only in the selected free space. For OPEN-V volumes, there are four ways to create VSC volumes (Table 17). You can specify from 46 MB (50 cylinders) up to the maximum capacity of VDEV for the capacity of a volume. If the specified capacity exceeds 60 gigabytes (65,535 cylinders), the Install CV function creates the volume in LUSE configuration automatically. When there is only one free space in the VDEV, you can use any method to create VSC volumes. When there are two or more free spaces, you can use the first method only. The other methods are not available. NOTE: Virtual LUN operations are not available for OPEN-L volumes. NOTE: Volume Management functions are not available for OPEN-L and OPEN-M volumes. NOTE: Allocating custom volumes in descending order of capacity optimizes custom volume allocation during the Install CV process. Table 17 Creating VSC volumes by Install CV (for OPEN-V) No. Install CV method Description 1 Specify size and number Used to specify the capacity and the number of custom volumes in the VSC volume that you want to create. 2 Divide free space by number Used to create VSC volumes by specifying the number of custom volumes in the VSC volume to be created. 3 Divide free space by size Used to create VSC volumes by specifying the capacity of custom volumes in the VSC volume to be created. 4 Set remaining space as volume Used to create a VSC volume using the remaining space on the VDEV.

As defined in Table 18, VSC does not work with OPEN-L and OPEN-M emulation types. VSC supports OPEN-3, OPEN-8, OPEN-9, OPEN-E, and OPEN-V emulations. Table 19 lists specifications and the minimum and maximum volume capacities for mainframe and open systems. Table 20 shows specified and actual capacities of various open system custom volume sizes. Table 18 VSC supported emulations Emulation Can create these volume size configurations OPEN-3 3, 8, 9, E OPEN-8 3, 8, 9, E OPEN-9 3, 8, 9, E OPEN-E 3, 8, 9, E OPEN-V V Table 19 Install Custom Volume operation parameters for mainframe and open system volumes Item Mainframe system volumes Open system volumes Track format 3380 or 3390 OPEN-3, OPEN-8, OPEN-9, OPEN-E OPEN-V Emulation type 3380-E, -F, -J, -K, -KA/KB/KC; 3390-1,-2,-3,-3R, -3A/3B/3C, -9 OPEN-3, OPEN-8, OPEN-9, OPEN-E OPEN-V Maximum number of LDEVs (fixed and custom volumes) per VDEV 512 for RAID5 (7D+1P) or RAID6 (6D + 2P) 256 for other RAID levels 512 for RAID5 (7D+1P) or RAID6 (6D + 2P) 256 for other RAID levels 512 for RAID5 (7D+1P) or RAID6 (6D + 2P) 256 for other RAID levels Maximum number of LDEVs (fixed and custom volumes) per disk array1 1. The value for the maximum number of LDEVs per disk array depends on the installed firmware version. 8192 8192 8192 Minimum custom volume capacity 1 cylinder (+ control cylinders) 36 MB (+ control cylinders) 48 MB (50 cylinders) Maximum custom volume capacity Emulation volume size Emulation volume size Emulation volume size Increment of custom volume capacity 1 cylinder 1 MB 1 MB (1 cylinder) Custom volume disk location Anywhere Anywhere Anywhere Table 20 Capacities of open system custom volume sizes Setting size (MB) User size (MG)1 Notes 36 36.15625 Minimum custom volume size (other than OPEN-V) 46 48.875 Minimum custom volume size (OPEN-V) 500 500.625 1000 1000.546875 2000 2000.390625

63 Volume Initialize and Make Volume operations The Volume Initialize and the Make Volume functions reset a VDEV to its original configuration. If you are not using OPEN-V, use the Volume Initialize function. The Volume Initialize function removes all custom volume areas and free spaces on the VDEV and regenerates and formats initial fixed volumes. The newly-formatted fixed volumes must be assigned CU and LDEV numbers. Existing fixed volumes on the VDEV are not reformatted. If you are using OPEN-V, use the Make Volume function. The Make Volume function deletes all volumes in a VDEV, and creates new custom volumes according to the specified settings. Table 21 shows the available settings. If the specified capacity exceeds 60 gigabytes (65,535 cylinders), the Make Volume function automatically creates the VSC volume in LUSE configuration. Restrictions If the VDEV contains a custom volume that violates any of the restrictions, the Volume Initialize and Make Volume functions are disabled. You must eliminate invalid custom volumes before performing the Volume Initialize and Make Volume functions. • The LDEV must not have a path definition, including TrueCopy (TC390), Continuous Access XP, ShadowImage (SI390), Business Copy (BC), and Continuous Access XP Journal pair volumes. • The LDEV must not be a component of a LUSE volume (Volume Initialize only). • The LDEV must not be reserved for Auto LUN XP. • The access attribute must be set to Read/Write (Volume Initialize only). 2347 2347.03125 Maximum OPEN-3 volume size 7007 7007.34375 Maximum OPEN-8 volume size 7042 7042.5 Maximum OPEN-9 volume size 13893 13893.04688 Maximum OPEN-E volume size 737256 737256.09375 Maximum OPEN-V volume size (maximum VDEV volume size) 1. The term user size refers to capacity available to users. User size does not include the number of control cylinders and the number of cylinders for volume boundary control. Table 20 Capacities of open system custom volume sizes (continued) Setting size (MB) User size (MG)1 Notes Table 21 Settings for the Make Volume operation (OPEN-V only) No. Specifies… VSC volumes to be created 1 The capacity and number of custom volumes under a VSC volume. A VSC volume with the specified number of custom volumes of the specified capacity is created. This is the same as the Install CV operation. 2 The number of custom volumes. A VSC volume with the specified number of custom volumes is created. The VDEV is divided by the specified number. 3 The capacity of custom volumes. A VSC volume with custom volumes of the specified capacity is created. The VDEV is divided by the specified capacity. 4 The remaining capacity for a VSC volume. If some space remains in the VDEV after VSC volumes are created by settings 1 - 3, the remaining space can be converted into a VSC volume.

LUSE operations Users belonging to the Administrator and StorageAdmin groups can perform Modify VSC and Modify LUSE operations. Starting LUSE operations 1. Click the Volume Management button ( ). The Volume Management pane appears. Figure 33 Volume Management pane Volume Management pane The Volume Management pane includes the following sections. LDEV Information tree The top of the pane shows a tree and list of CU numbers (CUxx) and LDEV numbers (xx:xx). When an LDEV is made up of LUSE volumes, the top LUSE number is displayed with the number of members preceded by an asterisk (*n). The number is the number of LDEVs that the LUSE volume contains, such as 00:02*2. LDEV Information table The status of each LDEV is indicated by one of the following icons. When you select a CU in the LDEV Information tree, this table shows information about all LDEVs in the CU. When you select an LDEV, the table shows detailed information about the LDEV. When you select a LUSE volume, the table shows detailed information about all LDEVs in the LUSE volume. The table contains the following information: • LDEV: An LDEV status icon (Table 22), a CU number, and an LDEV number. If the selected LDEV is a LUSE volume, the LDEV number of the top LDEV in the LUSE volume is displayed. An LDEV number that ends with a # indicates that the LDEV is an external LU (for example, 00:01#). Table 22 LDEV status icons for LUSE operations Icon LDEV status Normal LDEV Custom volume LUSE volume

65 • Emulation: The emulation type of the LDEV. If the selected LDEV is a VSC volume, the emulation type is displayed together with CVS (for example, OPEN-3 CVS). If the selected LDEV is a LUSE volume, the emulation type is displayed with an asterisk and the number of volumes in the LUSE volume (for example, OPEN-E*5). If the LDEVs that comprise a LUSE volume extend over two or more VDEVs, the emulation type is not displayed with an asterisk and the number of volumes (*n), and each LDEV in the LUSE volume is displayed. • Capacity: The capacity of the LDEV in either MB or GV, depending on which unit you selected in the Capacity Unit box. • RAID: The RAID level of the LDEV. The RAID level column contains a hyphen (-) when the LDEV is an external LU. • PG: A combination of a disk group and a parity group. If the LDEV extends over two or more parity groups, the PG column displays the smaller parity group number. A parity group number that starts with a letter E indicates that the parity group consists of one or more external LUs (for example, E1-1). • Paths: The number of paths that is 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. For more information, see ”LUSE operations that handle a path-defined LDEV” on page 58. • Access Attribute: The access attribute that is set for the LDEV • IO Suppression: Displays Disable when the I/O request from the host is suppressed, or Enable if the I/O request from the host is not suppressed • Cache mode: Displays Disable when the cache is not set to be used for responding to the I/O request from the host, or Enable when the cache is set to be used for responding to the I/O request from the host • Ex-Dev Info.: Displays the drive type of the LDEV. Displays an asterisk (*) when the drive type is SATA. Nothing is displayed when the drive type is not SATA. • CLPR: The ID of the CLPR (cache logical partition) to which the displayed volumes belong. The CLPR ID is a CLPR number (two-digit) and a CLPR name (16 characters maximum) • Selected LDEVs: The number of LDEVs selected in the LDEV Information table • Capacity Unit button: Select a capacity unit (GB or MB) to describe LDEVs Select an LDEV list Displays the LDEVs, VSC volumes, and LUSE volumes of the selected CU that are eligible to become part of a LUSE volume. The selected LDEV number becomes the top LDEV number of a LUSE volume. NOTE: On an XP128 array, a selected LDEV in the Information Tree does not appear in the Select an LDEV list. Volume Count list Specifies the number of LDEVs that should form a LUSE volume. For example, if you select 3 in the Volume Count list, three LDEVs are expected to form a LUSE volume and then three LDEVs are added to the Expanded LDEVs list. You can select an LDEV only from the Volume Count list. You cannot select a LUSE volume. Free LDEVs table Lists the LDEVs, VSC volumes, and LUSE volumes that can constitute a LUSE volume in combination with the LDEV selected as a top LDEV in the Select an LDEV list. The table contains the following information: • LDEV: An LDEV status icon (Table 22), a CU number, and an LDEV number. If the selected LDEV is a LUSE volume, the LDEV number of the top LDEV in the LUSE volume is displayed. An LDEV number that ends with a # indicates that the LDEV is an external LU (for example, 00:01#). • Capacity: Capacity of the LDEV represented in units (GB or MB), based on the capacity you indicate with the Capacity Unit box. • RAID: RAID level of the LDEV. The RAID level column contains a hyphen (-) when the LDEV is an external LU.

• PG: A combination of the disk group and the parity group. If the LDEV extends over two or more parity groups, the PG column displays the smaller parity group number. A parity group number that starts with a letter E indicates that the parity group consists of one or more external LUs (for example, E1-1). • CLPR: The cache logical partition (CLPR) number and name. The CLPR number consists of two digits. The CLPR name consists of up to six characters. For detailed information about CLPRs, see the HP StorageWorks XP Disk/Cache Partition User Guide. • Selected LDEVs: The number of LDEVs selected in the Free LDEVs table Expanded LDEVs list Lists the LDEVs that are selected as LUSE volume components. An LDEV from the Free LDEVs table is added to this list by clicking Add. The Expanded LDEVs list contains the following information: • Selected LDEVs: Number of LDEVs selected in the Expanded LDEVs list • Number of LDEVs: Number of LDEVs contained in a LUSE volume • Capacity: The capacity of a LUSE volume. The number is displayed in GB or MB depending on the selected capacity unit. Buttons • Add: Adds the selected LDEVs from the Free LDEVs table to the Expanded LDEVs list • Delete: Removes the selected LDEVs from the Expanded LDEVs list and moves it back to the Free LDEVs table • Set: Creates a LUSE volume consisting of the volumes in the Expanded LDEVs list. The LDEVs that are set as LUSE volume components are shown in blue in the LDEV Information table and the free LDEVs are deleted from the table. • Apply: Registers the LUSE settings with the disk array • Cancel: Cancels the LUSE settings Viewing LUSE configuration information • The LDEV Information tree displays an outline view of the CU and LDEV numbers installed on the disk 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, the information in this section is for the top LDEV. If you select a LUSE volume, the information in this table is for all of the LDEVs in the LUSE volume. An LDEV number that ends with a # indicates that the LDEV is an external LU (for example, 00:01#). Viewing concatenated parity groups 1. From the Volume Management pane, select a CU number in the LDEV Information tree. The LDEV Information table displays all the LDEVs in the selected CU. 2. In the LDEV Information table, select the free LDEVs for the LUSE volume and right-click. If the parity groups are concatenated, the Concatenation List command is available in the shortcut menu. 3. Select Concatenation List. The Concatenation List dialog box appears. 4. Click OK to return to the Volume Management pane. Creating a LUSE volume using the Volume Count list CAUTION: Creating a LUSE volume destroys existing data. To protect your data, make a backup copy of the existing data before starting the LUSE creation operation. 1. From the Volume Management pane, select a CU number in the LDEV Information tree. 2. In the Select an LDEV list, select a top LDEV of the LUSE volume. The Expanded LDEVs list displays the selected volume. The Free LDEVs table displays normal LDEVs, allocated LDEVs, VSC volumes, and LUSE volumes that can be used for a LUSE volume.

67 If you select a LUSE volume as the top LDEV, the Volume Count list is unavailable, and step 3 cannot be performed. In this case, select the LDEVs in the Free LDEVs table and click Add. To delete LDEVs, select the LDEVs in the Expanded LDEVs list and click Delete. 3. In the Volume Count list, select the number of LDEVs that should form a LUSE volume. The Expanded LDEVs list displays as many LDEVs as specified in the Volume Count list. For example, if 3 is specified, the Expanded LDEVs list displays three LDEVs. NOTE: You cannot select the LUSE volumes in the Volume Count list. To select LUSE volumes, select the LDEVs in the Free LDEVs table and click Add. • To add more LDEVs to the Expanded LDEVs list, select one or more LDEVs in the Free LDEVs table and click Add. • To delete LDEVs from the Expanded LDEVs list, select one or more LDEVs in the Expanded LDEVs list and click Delete. 4. Click Set. A confirmation message appears. • If you are performing a LUSE operation on a path-defined volume, a confirmation message appears. Click OK to confirm. Another confirmation message appears. Go to step 5. • If you are performing a LUSE operation on a volume that does not have a path definition, a confirmation message appears. 5. To create a LUSE volume, click OK. The changes are shown in blue in the LDEV Information table. 6. Click Apply. A confirmation message appears. 7. Click OK. The LUSE settings are registered with the disk array. A dialog box appears when the requested action is complete. 8. Click OK. Creating a LUSE volume using the Select an LDEV list CAUTION: Creating a LUSE volume destroys existing data. To protect your data, make a backup copy of the existing data before starting the LUSE creation operation. 1. In the Volume Management pane, select a CU number in the LDEV Information tree. 2. In the Select an LDEV list, select a top LDEV of the LUSE volume. The Expanded LDEVs list displays the selected volume. The Free LDEVs table displays normal LDEVs, allocated LDEVs, VSC volumes, and LUSE volumes that can be used for a LUSE volume. • To add LDEVs to the Expanded LDEVs list, select one or more LDEVs in the Free LDEVs table and click Add. The selected LDEVs are added to the Expanded LDEVs list and deleted from the Free LDEVs table. • To delete LDEVs from the Expanded LDEVs list, select one or more LDEVs in the Expanded LDEVs list and click Delete. The selected LDEVs are deleted from the Expanded LDEVs list and displayed in the Free LDEVs table. 3. Click Set. A confirmation message appears. 4. To perform a LUSE operation on a volume that has a path definition, click OK. If a message appears asking if you want to perform a LUSE operation that will affect more than one SLPR or CLPR, go to step 5. Otherwise, go to step 6. 5. To perform a LUSE operation that will affect more than one SLPR or CLPR, click OK. A confirmation message appears. 6. Click OK. The changes are shown in blue in the LDEV Information table. 7. Click Apply. A confirmation message appears. 8. Click OK. The LUSE settings are registered with the disk array. A dialog box appears when the requested action is complete. 9. Click OK.

Creating a LUSE volume using the LDEV information table CAUTION: Creating a LUSE volume destroys existing data. To protect your data, make a backup copy of the existing data before starting the LUSE creation operation. 1. In the Volume Management pane, select a CU number in the LDEV Information tree. 2. In the LDEV Information table, select the normal LDEVs, VSC volumes, or LUSE volumes. Right-click the selection and select Set LUSE Volume. a. To perform a LUSE operation on a volume that has a path definition, click OK. If a message appears asking if you want to perform a LUSE operation that will affect more than one SLPR or CLPR, go to step 2. Otherwise, go to step 3. b. To perform a LUSE operation on a volume that will affect more than one SLPR or CLPR, click OK. A confirmation message appears. 3. Verify the information in the dialog box and click OK. The LUSE creation starts. The changes are shown in blue in the LDEV Information table. 4. Click Apply. A confirmation message appears. 5. Click OK. The LUSE setting is registered. A dialog box appears when the requested action is complete. 6. Click OK. Releasing a LUSE volume CAUTION: This operation destroys data. To protect data, be sure to make a backup copy before starting the LUSE releasing operation. 1. In the Volume Management pane, select the CU number from which you want to release a LUSE volume. The LDEV Information table shows all LDEVs that the selected CU contains. 2. In the LDEV Information table, right-click the desired LUSE volume and select Release LUSE Volume. A LUSE release confirmation message appears. 3. Verify that the information is correct and click OK. The LUSE release starts. The changes are shown in blue in the LDEV Information table. 4. Click Apply. A confirmation message appears. 5. Click OK. The LUSE volume is released. A dialog box appears when the requested action is complete. 6. Click OK. Changing LUSE capacities • Expanding LUSE capacities To expand the capacity of a LUSE volume, select the LUSE volume you want to expand, and then add LDEVs or LUSE volumes, or first select the LDEVs or LUSE volumes you want to add, and then select a LUSE volume to be expanded. For more information, see ”Creating a LUSE volume using the Volume Count list” on page 66, ”Creating a LUSE volume using the Select an LDEV list” on page 67, or ”Creating a LUSE volume using the LDEV information table” on page 68. Each LDEV or LUSE volume that you want to add must have the same capacity as each LDEV in a LUSE volume to be expanded. • Reducing LUSE capacities You may not reduce the capacity of an existing LUSE volume. If you want a LUSE volume to have a smaller capacity, you must release and then redefine the LUSE volume. Resetting an unregistered LUSE volume When you create a LUSE volume, the screen shows the changes in blue bold italics until you register the volume into the disk array by clicking Apply. The LUSE volume in blue bold italics indicates that you can reset this LUSE volume to the state before it was created.

69 If the XP disk array has firmware version 21.06.22 or later installed, you can reset an unregistered LUSE volume to the state before it was created. However, you cannot recover any LUSE volumes that have been released already to the state when they were created. If the LUSE volume that you have created consists of any LDEVs (those in blue bold italics) that have once been released from a different LUSE volume, you can only reset your LUSE volume to the state when the constituting LDEVs were released from the other LUSE volume. 1. In the Volume Management pane, select the CU number from which you want to reset an unregistered LUSE volume. The LDEV Information table shows all LDEVs that the selected CU contains. 2. In the LDEV Information table, right-click an unregistered LUSE volume (displayed in blue bold italics) and select Reset Selected Volume. A confirmation message appears. 3. Verify the information in the dialog box and click OK. The unregistered LUSE volume will be reset to the state before this LUSE volume was created. The LDEV Information table displays the LUSE volumes or the LDEVs constituting the selected LUSE volume that has just been reset. VSC Operations Before beginning VSC operations, put the volumes in an offline state or unmount them (deallocate LUN paths). Users belonging to the Administrator and StorageAdmin groups can perform VSC operations. Starting VSC operations 1. Click the Volume Management button ( ). The Volume Management pane appears. 2. Click the Customized Volume tab. The Customized Volume pane appears. Figure 34 Customized Volume pane (Volume Management screen) Customized volume pane Parity Group - LDEV tree This tree shows a hierarchical structure of a disk group number (Box 1), parity group numbers (for example, 1-1), RAID levels (for example, 3D+1P), and VDEV numbers (for example, 1-1-1). An LDEV number that ends with a # indicates that the LDEV is an external LU (for example, 00:01#). The RAID level is left unspecified with a hyphen (-) when the LDEV is an external LU.

The status of each parity group is indicated by one of the following icons. The status of each VDEV is indicated by one of the following icons. Parity Group - LDEV table This table shows information about volumes in a VDEV selected in the Parity Group - LDEV tree. The status of each LDEV is indicated by one of the following icons. The table contains the following information: • No.: The number of a volume in the VDEV • CU:LDEV: A CU number/LDEV number combination. Free indicates a free space. An LDEV number that ends with a # indicates that the LDEV is an external LU (for example, 00:01#). • Emulation: Emulation type of the volume • Capacity: Capacity of the volume represented in the selected unit (MB, Cyl, or block) • Paths: Number of LU paths that the volume has. This box is blank when the volume has no LU paths. • Access Attribute: Access attribute of the volume • Status: Status of the volume. You must click LDEV Status to display the volume status. Table 26 describes the volume status displayed in the Status column. Table 23 Parity group status icons Icon Status Parity group Set of concatenated parity groups Table 24 VDEV status icons Icon Status No pending VSC actions VSC actions have been stored, but not yet implemented on the subsystem Table 25 LDEV status icons for VSC operations Icon Status Normal LDEV LUSE volume LDEV reserved for Auto LUN VSC volume VSC volume reserved for Auto LUN Free space Table 26 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.

71 Capacity unit list The Capacity Unit list allows you to select the unit (MB, Cyl, or block) to display for volume capacity. When you manipulate mainframe volumes, you can only select Cyl. Buttons • Apply: Registers the VSC settings • Cancel: Cancels the VSC settings • LDEV Status: Displays the current volume status NOTE: Currently, the Shredding Param and Download buttons are not supported. Viewing VSC configuration information Use the Customized Volume pane and its associated panes to view the current VSC configuration information: • View the VDEV and LDEV configuration information on the Customized Volume pane. 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 outline. • View the LDEV number setting information from the Install CV, Make Volume, and Volume Initialize panes. 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. In the Customized Volume pane, select a set of parity groups from the Parity Group - LDEV tree and right-click. If the parity groups are concatenated, the Concatenation List command is available in the shortcut menu. 2. Select Concatenation List. The Concatenation List dialog box appears. 3. Click OK. Converting volumes to space (Volume to Space) Use the Volume to Space function to convert logical volumes to space (free areas). CAUTION: The Volume to Space operation destroys data on the logical volumes that are converted. 1. From the Customized Volume pane, select a disk group, a parity group, and a VDEV in the Parity Group - LDEV tree. The Parity Group - LDEV table displays information about LDEVs in the selected VDEV. 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 any data to the volume. Unknown System does not recognize the volume’s status. Table 26 Volume status (continued) Status Description

2. Select one or more LDEVs (normal or custom volumes) you want to convert to space. For the OPEN-V emulation type, LUSE volumes can also be converted into free space. If the available LDEV is a LUSE volume, the emulation type is displayed together with an asterisk and the number of volumes in the LUSE volume (for example, OPEN-V*3) in the Emulation column of the table. To select two or more consecutive LDEVs, click the LDEVs while pressing the Shift key. To select two or more non-consecutive LDEVs, click the LDEVs while pressing the Ctrl key. NOTE: You cannot change all LDEVs in the selected VDEV into space. You cannot select the last normal or custom volume. 3. Right-click the selected LDEV and select Volume to Space. A volume confirmation dialog box is displayed. 4. Click OK. The Parity Group - LDEV table is displayed and the selected LDEVs are marked Free. The figures in the Capacity column are not yet updated, and the color of the VDEV icon that you manipulated changes from red to blue. You cannot manipulate blue VDEVs until you click Apply or Cancel. 5. Click Apply. a confirmation message appears. 6. Click OK. The LDEVs are converted to space. A dialog box appears when the requested action is complete. 7. Click OK. Creating custom volumes (Install CV) Use the Install CV function to create and install one or more custom volumes in the free space that is prepared by the Volume to Space function. The Install CV function can define (install) one or more new custom volumes in the free space prepared when volumes are created in VDEVs. 1. In the Customized Volume pane, click the LDEV folder in the Parity Group - LDEV tree to open a list of CUs, and then select a VDEV. The Parity Group - LDEV table displays information about LDEVs in the selected VDEV. 2. 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 35). Go to step 3.

73 If the VDEV you selected is not an OPEN-V volume, the Install CV pane (1) for non-OPEN-V appears (Figure 36). Go to step 4. Figure 35 Install CV pane (1) for OPEN-V (when two or more free spaces are available) Figure 36 Install CV pane (1) for other than OPEN-V 3. From the Install CV pane (1) for OPEN-V, do the following: a. In the Capacity Unit area, select MB, Cyl, or block for the capacity unit.

b. Select one of methods by clicking Specify capacity and number, Divide free space by number, Divide free space by capacity, or Set remaining space as volume. NOTE: If there are two or more free spaces in the VDEV, only the Specify capacity and number option is available. c. Specify the capacity of the volume and/or the number of volumes according to the selected method. For example: • If you selected Specify capacity and number, enter the capacity, either in MB, Cyl, or blocks, in the Capacity box and the number of custom volumes in the Number box. • If you selected Divide free space by number, enter the number of custom volumes in the Number box. • If you selected Divide free space by capacity, enter the capacity in the Capacity box. • If you selected Set remaining space as volume, go to step 3d. The Install CV Volume function allocates custom volumes in the order in which the function finds sufficient free space for the custom volumes, so for optimum space allocation you should allocate custom volumes in descending order of capacity. d. Click Set. The pane displays the selected custom volumes. Figure 37 Install CV pane (1) for OPEN-V after clicking Set e. To create other custom volumes, repeat step 3a through step 3d. f. To delete a custom volume, select the custom volume, click Delete, and then click OK to the confirmation message. To delete all custom volumes, click Clear, and then click OK. Go to step 5. 4. 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 custom volume you want to create. Use MB or blocks for open systems and cylinders (Cyl) for mainframe volumes. The available capacity range (minimum - maximum) appears to the right of the Capacity box. The value can be increased incrementally by one MB or block (open systems) or by one cylinder (mainframe systems).

75 The Install CV function allocates custom volumes in the order in which the function finds free space sufficient enough to hold them. Allocate custom volumes in descending order of capacity for optimum space allocation. c. Click Set. The pane displays the selected custom volumes. Figure 38 Install CV pane (1) for other than OPEN-V after clicking Set d. Repeat step 4a through step 4c to create additional custom volumes. e. To delete a custom volume, click the custom volume, click Delete, and then click OK.

5. After configuring custom volumes, click Next. The Install CV pane (2) is displayed. Figure 39 Install CV pane (2) Use this pane to assign the CU and LDEV numbers of a custom volume to be created. The top area is the CV setting information area and shows detailed information about the custom volumes to be created. The bottom area is the LDEV number setting area and is used to set the CU and LDEV numbers for the custom volume to be created. 6. In the CV setting information area, select one or more custom volumes. 7. In the Select CU No. list, select a CU number. The LDEV number setting area is updated to reflect the selected CU number. 8. If you selected multiple custom volumes, select an interval from the Interval list. This value specifies the interval between the LDEV numbers that need to be assigned to the new volumes. The default value is 0. When you select 0, consecutive LDEV numbers are assigned. The value you specify as the interval between LDEV numbers counts only the available LDEV numbers. 9. In the LDEV number setting area, select an LDEV number by clicking the appropriate white box. For example, to select an LDEV number of 96, click the +90/+6 box as shown in Figure 40.

77 NOTE: The CU number of another SLPR is used check box is displayed only when you logged in as a user in the StorageAdmin group with full array access and when there are two or more SLPRs. When the CU number of another SLPR is used check box is selected, you can select the number of an LDEV that does not exist in an SLPR to which the priority group does not belong. When the check box is cleared, you can only select the number of an LDEV in the SLPR to which the parity group belongs. Figure 40 Select an LDEV number The CU:LDEV number in the CV setting information area is updated. NOTE: If you specify an LDEV number in the selected CU, free sequential LDEV numbers in LUSE configuration are automatically assigned. You cannot specify an LDEV number, if free LDEV numbers in 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 6 - step 9 to set additional custom volumes. 11.To change a set volume, right-click the volume in the CV setting information area, and select Clear. 12.After setting all CU and LDEV numbers, click Next. If the boundary area of the selected LDEV number does not have an SSID, a dialog box is displayed for setting the SSID (Figure 41). Go to step 13.

If the boundary area of the selected LDEV number has an SSID, the Install CV confirmation dialog box is displayed. Go to step 15. Figure 41 Setting the SSID 13.In the SSID setting area, select a CU number to assign an SSID to, enter a new SSID in the Input SSID box, and click Set. The SSID is displayed in the SSID box of the SSID setting area. Repeat this step until all the SSIDs are set. NOTE: You can enter the SSID only when logged in as a user in the StorageAdmin group with full array access. NOTE: The SSID of another SLPR is used check box is displayed only when you logged in as a user in the StorageAdmin group with full array access and when there are two or more SLPRs. When the SSID of another SLPR is used check box is selected, you can select the number of an SSID that does not exist in an SLPR to which the parity group does not belong. When the check box is cleared, you can only select the number of the SSID in the SLPR to which the parity group belongs. You cannot enter the number in the Input SSID box when the SSID number of another SLPR is used check box is cleared. 14.After setting all the SSIDs, click Next. The Install CV confirmation dialog box is displayed.

79 15.Verify that the information in the Install CV confirmation dialog box is correct, and click OK. The Customized Volume screen is displayed with the new settings in blue. Figure 42 Customized volume screen 16.Click Apply. a confirmation message appears. 17. Click OK. The custom volume is created. A dialog box appears when the requested action is complete. 18.Click OK. Deleting custom volumes (Volume to Space) To delete a custom volume from a VDEV, convert the custom volume into free space with the Volume to Space function (see ”Converting volumes to space (Volume to Space)” on page 71). Creating initial custom volumes for OPEN-V (Make Volume) Use the Make Volume function to clear all custom volumes under a VSC volume and create an initial volume (VDEV) that consists of new user-defined custom volumes. CAUTION: The Make Volume function is a destructive operation and destroys the data on selected custom volumes. Back up the data as needed before performing this operation. 1. From the Customized Volume pane, click the LDEV folder in the Parity Group - LDEV tree to open a list of CUs, and then select a VDEV. The Parity Group - LDEV table displays information of LDEVs in the selected VDEV. NOTE: If the selected VDEV contains one or more custom volumes that violates any restriction for the Make Volume function (see ”Volume to Space operation” on page 60), you cannot perform the Make Volume function. Remove all invalid custom volumes before performing the Make Volume function.

2. Right-click any part of the Parity Group - LDEV tree and select Make Volume. The Make Volume pane (1) appears. Figure 43 Make Volume pane (1) 3. From the Make Volume pane (1), do the following: a. In the Capacity Unit list, select MB, Cyl, or block for the capacity unit. b. Select one of methods by clicking Specify capacity and number, Divide free space by number, Divide free space by capacity, or Set remaining space as volume. NOTE: If there are two or more free spaces in the VDEV, only the Specify capacity and number option is available. c. Specify the capacity of the custom volume and/or the number of custom volumes according to the selected method. For example: • If you selected Specify capacity and number, enter the capacity, in MB, Cyl, or blocks, in the Capacity box and the number of custom volumes in the Number box. • If you selected Divide free space by number, enter the number of custom volumes in the Number box. • If you selected Divide free space by capacity, enter the capacity in the Capacity box. • If you selected Set remaining space as volume, go to the next step.

81 d. Click Set. The pane displays the setting in the table. Figure 44 Make Volume pane (1) after clicking Set e. To set other custom volumes, repeat step 3a through step 3d. f. To remove a setting, select the custom volume, click Delete, and then click OK. To remove all settings, click Clear, and then click OK. 4. After setting all custom volumes, click Next. The Make Volume pane (2) appears.

NOTE: If no CV is set, the Make Volume operation does not create a volume in the VDEV. In this case, a message appears and the Volume Management pane appears. Figure 45 Make Volume pane (2) Use this pane to assign CU and LDEV numbers to the custom volumes to be created. The top area is the CV setting information area and shows detailed information about the custom volumes to be initialized. The bottom area is the LDEV number setting area and is used to set the CU and LDEV numbers for the custom volume to be initialized. 5. In the CV setting information area, select one or more custom volumes. 6. In the Select CU No. list, select a CU number. 7. If you selected multiple custom volumes, select an interval from the Interval list. This value specifies the interval between the LDEV numbers that need to be assigned to the new volumes. The default value is 0. When you select 0, consecutive LDEV numbers are assigned. The value you specify as the interval between LDEV numbers counts only the available LDEV numbers. 8. In the LDEV number setting area, select an LDEV number by clicking the appropriate white box. For example, to select an LDEV number of 97, click the +90/+7 box as shown in Figure 46.

83 NOTE: The CU number of another SLPR is used check box is displayed only when you logged in as a user in the StorageAdmin group with full array access and when there are two or more SLPRs. When the CU number of another SLPR is used check box is selected, you can select the number of an LDEV that does not exist in an SLPR to which the parity group does not belong. When the check box is cleared, you can only select the number of an LDEV in an SLPR to which the parity group belongs. Figure 46 Select an LDEV number The CU:LDEV number in the CV setting information area is updated. NOTE: If you specify an LDEV number in the selected CU, free sequential LDEV numbers in LUSE configuration are automatically assigned. You cannot specify an LDEV number if free LDEV numbers in 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. 9. Repeat step 5 - step 8 to set additional volumes. 10.To change a set volume, right-click the volume and select Clear from the shortcut menu. 11.After setting all CU and LDEV numbers, click Next. If the boundary area of the selected LDEV number does not have an SSID, a dialog box is displayed for setting the SSID. Go to step 12. If the boundary area of the selected LDEV number has an SSID, the Make Volume confirmation dialog box is displayed. Go to step 14. 12.In the SSID setting area, select a CU number to assign an SSID to it, enter a new SSID in the Input SSID box, and click Set. The SSID is displayed in the SSID box of the SSID setting area. Repeat this step until all the SSIDs are set. 13.After setting all the SSIDs, click Next. The Make Volume confirmation pane is displayed.

14.Verify that the information is correct and click OK. The Customized Volume pane is displayed. The created custom volumes are shown in blue. NOTE: You cannot manipulate the VDEVs denoted by blue icons until you apply the changes to the disk array or cancel them, but you can initialize additional custom volumes in VDEVs denoted by red icons. 15.Click Apply. A confirmation message appears. 16.Click OK. The Make Volume operation begins. When LDEV formatting is in progress and at completion, a notation is displayed across the bottom of the screen to indicate the progress. A dialog box is displayed when the requested action is complete. 17. Click OK. Initializing custom volumes for other than OPEN-V (Volume Initialize) Use the Volume Initialize function to uninstall all custom volumes under a VSC volume, and reformat the VSC volume as a normal volume (VDEV). CAUTION: The Volume Initialize function is a destructive operation and destroys the data on selected custom volumes. Back up the data as needed before performing this operation. 1. From the Customized Volume pane, click the LDEV folder in the Parity Group - LDEV tree to open a list of CUs, and then select a VDEV. The Parity Group - LDEV table displays information about the LDEVs in the selected VDEV. NOTE: If the selected VDEV contains one or more custom volumes that violates any restriction for the Volume Initialize function (see ”Volume to Space operation” on page 60), you cannot perform the Volume Initialize function. Remove all invalid custom volumes before performing the Volume Initialize function.

85 2. Right-click any part of the Parity Group - LDEV tree and select Volume Initialize. The Volume Initialize pane is displayed. Figure 47 Volume Initialize pane Use this pane to initialize custom volumes other than OPEN-V. The top area is the CV setting information area and shows detailed information about the custom volumes to be initialized. The bottom area is the LDEV number setting area and is used to set the CU and LDEV numbers for the custom volume to be initialized. 3. In the CV setting information area at the top of the pane, select one or more custom volume numbers. 4. In the Select CU No. list, select a CU number. The LDEV number setting area is updated to reflect the selected CU number. 5. In the LDEV number setting area, select an LDEV number by clicking the appropriate white box. For example, to select an LDEV number of 16, click the +10/+6 box as shown in Figure 48.

NOTE: The CU number of another SLPR is used check box is displayed only when you logged in as a user in the StorageAdmin group with full array access and when there are two or more SLPRs. When the CU number of another SLPR is used check box is selected, you can select the number of an LDEV that does not exist in an SLPR to which the parity group does not belong. When the check box is cleared, you can only select the number of an LDEV in an SLPR to which the parity group belongs. Figure 48 Select an LDEV number The CU:LDEV number in the CV setting information area is updated. 6. To set additional volumes, repeat step 3 - step 5. 7. To change a set volume, right-click the volume and select Clear from the shortcut menu. 8. After setting all CU and LDEV numbers, click Next. If the boundary area of the selected LDEV number does not have an SSID, a dialog box is displayed for setting the SSID. Go to step 9. If the boundary area of the selected LDEV number has an SSID, the Volume Initialize confirmation dialog box is displayed. Go to step 11. 9. In the SSID setting area, click a CU number to assign an SSID to it, select or enter a new SSID in the Input SSID box, and click Set. The SSID is displayed in the SSID box of the SSID setting area. Repeat this step until all the SSIDs are set. NOTE: You can enter the SSID in the Input SSID box only when logged in as a user in the StorageAdmin group with full array access.

87 NOTE: The SSID of another SLPR is used check box is displayed only when you logged in as a user in the StorageAdmin group with full array access and when there are two or more SLPRs. When the SSID of another SLPR is used check box is selected, you can select the number of an SSID that does not exist in an SLPR to which the parity group does not belong. When the check box is cleared, you can only select the number of the SSID in the SLPR to which the parity group belongs. You cannot enter the number in the Input SSID box when the SSID number of another SLPR is used check box is cleared. 10.After setting all the SSIDs, click Next. The Volume Initialize confirmation pane is displayed. 11.Verify that the information in the Volume Initialize pane is correct and click OK. The Customized Volume pane is displayed. A notation is displayed across the top of the screen to indicate that the volume has been initialized, and the color of the VDEV icon that you manipulated in the Parity Group - LDEV outline view changes from red to blue. NOTE: You cannot manipulate VDEVs with blue icons until you apply the changes to the subsystem or cancel them, but you can initialize additional custom volumes in VDEVs with red icons. 12.Click Apply. a confirmation message appears. 13.Click OK. The Volume Initialize operation begins. When LDEV formatting is in progress and at completion, a notation is displayed across the bottom of the screen to indicate the progress. Formatting LDEVs The LDEV Format feature allows you to format external volumes (including external volumes). To format volumes, use the following procedure to ensure that the volumes are in block status: 1. Click the LDEV Status button in the Customized Volume pane. 2. Confirm that the current status of the desired external mainframe volume is displayed as Normal in the Status column of the Parity Group - LDEV table. 3. Right-click an external mainframe volume and select Blockade from the shortcut menu. A confirmation message appears. Click OK. 4. The status of the volume in the Parity Group - LDEV table changes to Blocked, and the selected volume is displayed in blue. 5. Click Apply. When prompted to confirm the changes, click OK. The new setting is implemented into the subsystem and a message notifies you that the implementation is complete. Click OK. 6. Confirm that the volume is listed as Blocked in the Status column of the Parity Group - LDEV table. 7. To specify blocked volumes to format, do one of the following: • Select the volume with Blocked status in the LDEV Information table, right-click, and select Format. • To format all blocked internal and external volumes, right-click LDEV at the top of the tree, and select All Format. In the All Format pane, select All Type from the Parity Group Type list. Confirm that the list displays internal and external volumes to be formatted, and click OK to close the All Format pane. • To format all blocked internal volumes, right-click LDEV at the top of the tree, and select All Format. In the All Format pane, select Internal PG from the Parity Group Type list. Confirm that the list displays internal volumes to be formatted, and click OK to close the All Format pane. 8. Confirm that the volume is listed in blue with a status of Format in the Parity Group - LDEV table. 9. Click the Apply button in the Customized Volume pane. When prompted for confirmation, click OK. The words Format in progress appear next to the Progress Bar. 10.When the percentage shown on the Progress Bar reaches 100%, a message informs you that the format operation is complete. Click OK. 11.Confirm that the status of the volume is Normal.

Formatting all blocked volumes Use the All Format pane to format all blocked volumes in parity groups in the local disk array and/or external disk array. This pane contains the following: • Parity Group Type: Volumes to be formatted. • All Type: Formats blocked volumes in all parity groups in the local and external disk arrays. • Internal PG: Formats blocked volumes in all parity groups in the local disk array. • External PG: Formats block volumes in all parity groups in the external disk array. • List: Information about volumes to be formatted. • PG: Parity groups containing volumes to be formatted. • Blocked Count: Number of blocked volumes to be formatted. • OK: Applies settings to the Volume Management pane, and closes the All Format pane. • Cancel: Cancels settings, and closes the All Format pane. Operational restrictions The success of some volume management activities depends on the status of the security switch and whether I/O is active or inactive to the port or LUN. The following tables describe those restrictions. Restrictions on VSC and LUSE operations Table 27 VSC and LUSE operation restrictions Activity Security switch OFF Security switch ON Host group 0 Host group 01-7F Host group 0 Host group 01-7F Volume to Space (VSC operation) With active I/O on LUN Not permitted Invalid operation Not permitted With no active I/O on LUN Permitted Permitted Make Volume/ Volume Initialize (VSC operation) With active I/O on LUN Not permitted Invalid operation Not permitted With no active I/O on LUN Permitted Permitted Deleting a LUSE volume With active I/O on Not permitted Invalid operation Not permitted With no active I/O on Permitted Permitted

89 Index Numerics 16-Port FC/CA CHIP 16 2 port mode 22, 46 A addresses Fibre Channel ports 21, 46 iSCSI ports 23 AIX host modes 18 AL-PA addresses 21 alternate paths defining 40 viewing 43 arbitrated loop physical address (AL-PA) 21 audience, documentation 9 authentication host 25, 50 mutual 52 user 24, 48 authorized resellers, HP 11 B Blockade function 87 Business Copy XP 20 C capacities, changing LUSE 68 Capacity Unit list 71 Change Port Mode box 46 channel adapters (CHAs) package status 44 CHAP authentication 24, 48 CHAs (channel adapters) package status 44 command devices creating with RAID Manager 43 restrictions on 20, 55 concatenated parity groups 40, 66 connection results, iSCSI environment 53 Continuous Access XP 20 conventions, document 10 copying paths 41, 42 custom volumes configuration information, viewing 71 Customized Volume pane 69 defined 58 Install CV function 61, 72 Make Volume function 63, 79 restrictions 88 samples 59 starting VSC operations 69 Volume Initialize function 63, 84 Volume to Space function 60, 71 customer support 10 Customized Volume pane 69 D data transfer speed, Fibre Channel ports 22, 46 deleting HBAs from host groups 40 host groups 37 LU paths 36 restrictions on 55 user information of hosts 52 WWNs 40, 43 document conventions 10 documentation, related 10 DYNIX host modes 18 E emulation types supported 13 expanded LDEVs 66 F fabric topology 20 FC-AL topology 20 features 13 Fibre Channel ports addresses 21, 46 attributes 20 configuring 44 copying paths 41, 42 data transfer speed 22, 46 LU paths 14, 32 Package tree 44 path tree 28 restrictions on 55 status 29 topology 20, 46 formatting LDEVs 87 free LDEVs 65, 66 H HBAs, deleting from host groups 40 help HP technical support 10 high-speed modes 22, 46 host bus adapters (HBAs), deleting from host groups 40 host groups associating to logical volumes 36 creating 17, 33 deleting 37 deleting HBAs 40 initializing group 0 38 mode, changing 37 name, changing 37 registering hosts 34 restrictions 55

iSCSI status, checking 24 modes 18 mutual authentication 52 pinging in iSCSI environment 48 registering in host groups 34 registering user information 50 storage domains 14 user information, changing 52 user information, deleting 52 HP authorized resellers 11 storage web site 11 Subscriber’s choice web site 11 technical support 10 HP-UX host modes 18 I IBM AIX host modes 18 Install CV function 59, 61, 72 IP addresses, iSCSI ports 23 iSCSI environment connection results 53 connections supported 23 host authentication 25 LU paths copying 41, 42 defining 32 limitations 13 mutual authentication 52 Name table 31 names, changing 38 Package Tree 44 path tree 28 pinging host 48 ports configuring 23, 44, 47 status 30 registering user information on host 50 restrictions 55 status connection 24 ports 30 user authentication 24, 48 user information changing 52 deleting 52 iSCSI Function box 46 iSCSI names 23 iSNS servers 23, 48 L LDEVs associating host groups to logical volumes 36 combining 57 command devices 20, 43 expanded 66 formatting 87 free 65, 66 Information table 64, 68 Information tree 64 LU Path table 31 LUSE volume capacity, changing 68 LUSE volumes, creating 66 parity group tree 69 releasing a LUSE volume 68 resetting an unregistered volume 68 status table 32 Volume to Space function 60 Linux host modes 18 logical volumes, associating host groups 36 loop IDs 21 LU Path table 31 LU Path tree 28 LU paths alternate, defining 40 alternate, viewing 43 associating host groups to logical volumes 36 copying 41, 42 defining 32 deleting 36 Fibre Channel environment 14 limitations 13 NAS environment 13, 15 table 31 LUN Manager main pane 28 LUN mapping, 16-Port FC/CA CHIP product 16 LUN security applying to ports 43 enabling and disabling 19 removing 43 LUSE operations capacities, changing 68 combining LDEVs 57 concatenated parity groups 66 creating a LUSE volume 66, 67, 68 path-defined LDEVs 58 releasing a volume 68 resetting an unregistered volume 68 restrictions 88 rules 57 starting 64 viewing configuration information 66 M main pane, LUN Manager 28 Make Volume function 59, 63, 79, 88 mutual authentication 52

91 N NAS environment configuring LU paths 15 copying paths 41, 42 LU types 13 path tree 28 status, ports 29 NetWare host modes 18 nicknames, changing 38 Novell NetWare host modes 18 O OPEN volumes, LUSE rules 57 OPEN-V Install Custom Volume function 61 LUSE rules 57 Make Volume function 79 Make Volume operation 63 parity group configuration 59 size, volume 59 OpenVMS host modes 18 P Package tree 44 parity groups concatenated 40, 66 configuration 59 status icons 69 paths. See LU paths ping commands, iSCSI port to host 48 point-to-point topology 20 Port tab 44 Port table 45 Port tree (user authentication) 49 ports See also Fibre Channel ports 16-Port FC/CA CHIP product 16 alternate paths, defining 40 Change Port Mode box 46 configuring 44 connection results 53 copying paths 41, 42 host authentication 25, 50 iSCSI, configuring 23, 44, 47 LU paths, defining 32 LUN security 43 mutual authentication 52 name tables 31 names, changing 38 Package tree 44 path tree 28 restrictions 55 security 19 speed modes 22, 46 status 29 user authentication 24, 48 user information 50, 52 prerequisites 9 R RAID levels combining LDEVs 57 parity groups 69 RAID Manager command devices 20, 43 releasing a LUSE volume 68 resetting unregistered volumes 68 restrictions LUN Manager 54 LUSE operations 88 VSC operations 88 S security applying to ports 43 host authentication 25, 50 mutual authentication 52 ports 19 RAID manager 20 restrictions 54 user authentication 24, 48 Select an LDEV list 67 Sequent host modes 18 Solaris host modes 18 speed, Fibre Channel ports data transfer 22, 46 standard speed mode 22, 46 starting LUN Manager 28 LUSE operations 64 VSC operations 69 status Fibre Channel ports 29 iSCSI host and disk subsystem 24 iSCSI ports 30 LDEVs 32 NAS ports 29 parity groups 69 VDEV 69 subnet mask, default 23 Subscriber’s choice, HP 11 T technical support, HP 10 topologies, Fibre Channel ports 20, 46 Tru64 host modes 18 U unregistered volumes, resetting 68 user authentication mutual 52 settings 24, 48 User Authentication tab 49 user information changing 52 deleting 52 registering on host 50 User Information (Host) table 49 User Information (Port) table 50

Volume Count list 65, 66 Volume Initialize function 63, 84, 88 Volume Management 57 Volume Management pane 64 Volume to Space function 58, 60, 71, 88 VSC operations configuration information, viewing 71 Customized Volume pane 69 defined 58 Install CV function 61, 72 Make Volume function 63, 79 restrictions 88 samples 59 starting 69 Volume Initialize function 63, 84 Volume to Space function 60, 71 W web sites HP documentation 10 HP storage 11 HP Subscriber’s choice 11 Windows host modes 18 WWNs deleting 40, 43 Name table 31 names, changing 38 restrictions 55 security 20